Database Info

device not found via adb

question.. i was told i need a late firmware version in order to use ics roms so i decided to do it but idk why my device cant be found via cmd
i have s off
and hboot 1.27.1100
eMMC boot
i think i bricked my phone cause w.e. rom i install it just keeps looping. idk what to do?
there is no way my phone is being recognized by windows the device is not found and i cant even find a way to put it back to stock someone please help :/
at least i need to put s-on and remove recovery so i can send it back to t-mo but i cant do anything via adb. please im really willing to donate the person that helps me please

You're phone isn't bricked if it still turns on. If you can still access recovery why don't you just perform a full wipe then flash a new rom

lileddy305 said:
question.. i was told i need a late firmware version in order to use ics roms so i decided to do it but idk why my device cant be found via cmd
i have s off
and hboot 1.27.1100
eMMC boot
i think i bricked my phone cause w.e. rom i install it just keeps looping. idk what to do?
there is no way my phone is being recognized by windows the device is not found and i cant even find a way to put it back to stock someone please help :/
at least i need to put s-on and remove recovery so i can send it back to t-mo but i cant do anything via adb. please im really willing to donate the person that helps me please
Click to expand...
Click to collapse
Your device is boot looping because the fermware version is not compatible with the ROM you flashed. To get ADB to detect your device you need to boot into Hboot and the select fastboot, then you can use ADB or fastboot commands.
It would be very helpful to post what ROM you flashed. Also you have Hboot 1.27.1100 which is part of the the firmware you need to use ICS so why you were told you need a later version is kind of confusing to me, unless you were wanting to go back to Gingerbread. Please run the following command and post back everything except your IMEI number.
Code:
fastboot getvar all

Have you tried any of the other methods
There are two things you need to look at
1) Is the device in usb debugging enabled?
2) other than using the standard ADB method there are a few other easier methods
a) Droid explorer
i can supply a link if needed
b) The sensation all in one toolkit
http://forum.xda-developers.com/showthread.php?t=1497404
if you have any other ? feel free to contact me as i have been there

kampj007 said:
There are two things you need to look at
1) Is the device in usb debugging enabled?=Invalid the OP can not currently boot to OS.
2) other than using the standard ADB method there are a few other easier methods=Invalid the OP can not currently boot to OS.
a) Droid explorer
i can supply a link if needed=Invalid the OP can not currently boot to OS.
b) The sensation all in one toolkit
http://forum.xda-developers.com/showthread.php?t=1497404=Invalid because the only tool needed by the OP from the toolkit is boot to recovery, but it uses ADB to do this and without being booted into the OS and having USB debugging enabled this will not work
if you have any other ? feel free to contact me as i have been there=Thanks for your willingness to help
Click to expand...
Click to collapse
Also about the toolkit, seeing as they will have to boot to Hboot and then select fastboot to be able to use ADB and fastboot commands. So the toolkit is not going to do the OP any good. The OP will have to either change firmware versions or flash a ROM that is compatible with the firmware version they have to solve the problem.

Wait a minute...
I have been in same situation and what i did was connect the phone via Usb and turn it on. Went into fastboot and then using the programs i talked about it allowed me to load software and change items as needed. I was able to connect through droid explorer as soon as it turned on and it helps u load into recovery and fastboot so that u can adjust as needed.

kampj007 said:
Wait a minute...
I have been in same situation and what i did was connect the phone via Usb and turn it on. Went into fastboot and then using the programs i talked about it allowed me to load software and change items as needed. I was able to connect through droid explorer as soon as it turned on and it helps u load into recovery and fastboot so that u can adjust as needed.
Click to expand...
Click to collapse
Exactly you had to boot to the Hboot and then choose fastboot for them to use the programs. Plus the OP is already S-off and can manually boot into Hboot then to recovery. So the tool kit has nothing to offer the OP at all. Yes they can be in fastboot and use Droid Explorer to copy any needed .zip be it a PG58IMG.zip or a ROM.zip, but they can also do this within their recovery by USB mass storage in recovery.
I do not mean to offend but I just do not want to see this made more complicated than it is for the OP. It is really a very simple problem and has a very simple fix.

Hello,
I am in similar situation. I cannot get my device to be recognized either. Here is what getvar all showed me:
"C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.29.0000
INFOversion-baseband: 11.24A.3504.31_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.33.401.106
INFOserialno: SH164T500176
INFOimei: 355066045001866
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5810000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 3905mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 705f86f6
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.497s"
Any help would be appreciated. Thanks!
C:\adb>

twocrows said:
Hello,
I am in similar situation. I cannot get my device to be recognized either. Here is what getvar all showed me:
"C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.29.0000
INFOversion-baseband: 11.24A.3504.31_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.33.401.106
INFOserialno: SH164T500176
INFOimei: 355066045001866
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5810000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 3905mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 705f86f6
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.497s"
Any help would be appreciated. Thanks!
C:\adb>
Click to expand...
Click to collapse
do you have enabled usb debugging mode from settings?
do you have installed htc drivers?
use also usb 2.0 ports not 3.0

just install htc sync and do again

rzr86 said:
do you have enabled usb debugging mode from settings?
do you have installed htc drivers?
use also usb 2.0 ports not 3.0
Click to expand...
Click to collapse
No to usb debugging mode
Yes to installed htc drivers
will make sure to use usb 3.0

twocrows said:
No to usb debugging mode
Yes to installed htc drivers
will make sure to use usb 3.0
Click to expand...
Click to collapse
wait not 3.0 use 2.0 ports

T-Macgnolia said:
Your device is boot looping because the fermware version is not compatible with the ROM you flashed. To get ADB to detect your device you need to boot into Hboot and the select fastboot, then you can use ADB or fastboot commands.
It would be very helpful to post what ROM you flashed. Also you have Hboot 1.27.1100 which is part of the the firmware you need to use ICS so why you were told you need a later version is kind of confusing to me, unless you were wanting to go back to Gingerbread. Please run the following command and post back everything except your IMEI number.
Code:
fastboot getvar all
Click to expand...
Click to collapse
Adb will recognize device while in fastboot?
I always thought fastboot cmds were for while in fastboot, and adb was for while booted to android?
Sent from my EVO using xda premium

scottspa74 said:
Adb will recognize device while in fastboot?
I always thought fastboot cmds were for while in fastboot, and adb was for while booted to android?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
No fastboot mode is a developer tool first and secondly a fail safe to be able to communicate with ADB and fastboot if something goes drastically wrong such as not being able to boot to recovery or boot to the OS either one with the device and it needs to have the OS re installed. Try booting to fastboot mode and then connect your device to your computer with working ADB and type in adb devices it will show you the device ID.

miillaaad said:
just install htc sync and do again
Click to expand...
Click to collapse
Did that, no dice
Still not seeing via adb and for whatever reason that means unable to flash new boot.img
---------- Post added at 12:52 PM ---------- Previous post was at 12:47 PM ----------
So ended up going back to stock ruu.
Got bootloader unlocked, but adb still says device not found!!
I flash new (4EXT) recovery and it says it flashes ok, but never ever works.
Tried different laptops, usb cords, and installing htc sync, uninstalling htc sync, htc sync manager, etc
All have made no difference
USB debugging is enabled
Any ideas?!?

twocrows said:
Did that, no dice
Still not seeing via adb and for whatever reason that means unable to flash new boot.img
---------- Post added at 12:52 PM ---------- Previous post was at 12:47 PM ----------
So ended up going back to stock ruu.
Got bootloader unlocked, but adb still says device not found!!
I flash new (4EXT) recovery and it says it flashes ok, but never ever works.
Tried different laptops, usb cords, and installing htc sync, uninstalling htc sync, htc sync manager, etc
All have made no difference
USB debugging is enabled
Any ideas?!?
Click to expand...
Click to collapse
Funnily enough, I never got adb recognized on stock rom.
After custom rom, it does.

twocrows said:
Did that, no dice
Still not seeing via adb and for whatever reason that means unable to flash new boot.img
---------- Post added at 12:52 PM ---------- Previous post was at 12:47 PM ----------
So ended up going back to stock ruu.
Got bootloader unlocked, but adb still says device not found!!
I flash new (4EXT) recovery and it says it flashes ok, but never ever works.
Tried different laptops, usb cords, and installing htc sync, uninstalling htc sync, htc sync manager, etc
All have made no difference
USB debugging is enabled
Any ideas?!?
Click to expand...
Click to collapse
use adb toggle app from play store
see how it goes

twocrows said:
Did that, no dice
Still not seeing via adb and for whatever reason that means unable to flash new boot.img
---------- Post added at 12:52 PM ---------- Previous post was at 12:47 PM ----------
So ended up going back to stock ruu.
Got bootloader unlocked, but adb still says device not found!!
I flash new (4EXT) recovery and it says it flashes ok, but never ever works.
Tried different laptops, usb cords, and installing htc sync, uninstalling htc sync, htc sync manager, etc
All have made no difference
USB debugging is enabled
Any ideas?!?
Click to expand...
Click to collapse
Maybe you should check everything is in order on low level, when your phone is connected to your computer, use lsusb under linux (usbview under windows) to check if the device is recognized by the OS.

OK, so I am a bit embarrassed on two counts:
1) when phone was booted up into ROM adb finally recognized it! I had a big duh moment.
2) it seems that at the root of the problem was a syntax error.
I was not renaming the recovery.img file properly. I was typing the command "fastboot flash recovery 4ext.img" and didn't rename file 4ext.img to "recovery.img" Cause when I renamed the file to "recovery.img" and then typed command "fastboot flash recovery recovery.img" I could finally boot back into recovery!
I did however have to flash boot.img after installing the newest Viper ROM. But here I am back on a great custom ROM! Thank you for all your help even if it didn't work it gave me the encouragement to keep trying.
Peace!
Sent from my HTC Sensation 4G using xda premium

[FIXED] HTC One S Soft Bricked

Hello all,
So I have done tons of reading, wiki'ing, researching, googling and I have found things and I have come to my end here. Things started off yesterday when I saw that Google has now released a new version of Google Calendar. I have been waiting years for an upgrade of this magnitude. Unfortuntely I could not install it because my phone no longer had space on the partition. I tried to find a way to transfer files to my SD card but apparently the ROM I was running at the time (MIUI V4) did not support this kind of feature, shockingly.
So I decided to do some digging to find my next rom as being this is an old phone, I was hesitant to find anything new. I came across CM11 (Android 4.4.4) and noticed it was fairly stable and this got me very excited. Noticed CM12 aswell with the new Lolipop but I will hold off. I was running an old version of TWRP recovery and I assumed it would be a simple, "Drop the .zip rom in your SD card and fire away".
I apparently had the wrong version hboot 2.16 instead of 2.15. So I had to upgrade my TWRP. I upgraded to twrp-2.8.1.1-ville but that wasn't compatible with my phone for some reason. I downgraded back down to twrp-2.8.0.1-ville-dm and attempted to install the CyanogenMod_11S_ville_hboot-2.15_v2 rom.
Low and behold I get a "can't mount the /sdcard directory" in my recovery. So I switch over to CWM recovery-clockwork-6.0.4.8-ville and same /sdcard error. I wiped everything and didnt realize it would reformat my internal SD card. Every here knows opening the HTC One S is also no joy ride. I wanted to hold off as long as possible.
From there I feared the worst and attempted to RELOCK the phone and install RUU OTA_Ville_U_JB_45_S_Globalive_WWE_3.16.1500.7_1.11.50.05.28_10.27.50.08L_release_3049068z393w1fez9cc9lt.zip as my CID was GLOBA001 [WIND MOBILE in Canada].
That did not install correctly either. Right now I am staring at my phone, it is RELOCKED, no recovery, I have no idea if it's rooted, and I can't get past the fastboot menu.
I know I made a small stupid mistake somewhere and would appreciate some help with any of this.
My "fastboot getvar all":
version: 0.5
version-bootloader: 2.15.0000
version-baseband: 1.11.50.05.28
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA28RW402816
imei: xxxxxxxxxxxxxxx
product: vle
platform: HBOOT-8960
modelid: PJ4011000
cidnum: GLOBA001
battery-status: good
battery-voltage: 4169mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-64bedd38
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
My goal is to install either CWM or TWRP and CyanogenMod_11S_ville_hboot-2.15_v2. Hope this all helps!
EDIT 1: My bootloader is now UNLOCKED again. And I have ClockworkMod Recovery 6.0.4.8. I will try sideload adb. If anyone has suggestions help me have em
EDIT 2: When I try to select a zip from /storage/sdcard0 CWM tells me "E: Can't mount /storage/sdcard0" should I reformat it via the Recovery?
EDIT 3: I sideloaded CM11S via CWM (6.0.4.8) through CMD and it appeared to install but the install process moved WAY faster than it should have. Rebooted phone to black screen and no OS. Might try another recovery...

I fixed it! I went into the rom's zip file and extracted the boot.img file and flashed the boot file using "fastboot flash boot boot.img". I restarted the phone and VOILA, like magic the CM loading wheel showed up.

Reserved

Need help restoring HTC One S. Or flash a working Rom!?

( Text below is just an explanation to my issues and why I need help! )
Hallo dear XDA forum people I ahve many times read posts and fixes about my cellphone here and managed to unlock, root and install Super SU on my HTC One S. It still has the stock rom, given it's now unlocked and rooted etc. Last weeks I've been having problems with calling out or receiving phone calls. Due to the cellphone hangs every time. So factory reset it to default. The problem persisted somewhat. It now just gets sluggish and I can't hear the other one speaking. Even though the cellphone actually made the connection. So thought about downloading a RUU or flash to another ROM to see if it's cleaner and more stable.
What I done so far!
Before tampering with the cellphone I took backup .img files of my ROM. I even took a manual ''Copy everything on the cellphone to my PC'' in case this would happen. So....
I have installed Universal ADB Drivers, JDK for Java, Android Studio bundle, The HTC One Toolkit - Squabbi - 3.1.2 version. Not that it done any good so far.
The BIG problem is that the cellphone can't mount it's memory card. So I can't put any ROMS, FLASH FILES, .zips or anything on it. I failed at forcing data into the ''data'' folder to.
And when I try to flash a file directly using ''Fastboot'' the device hangs at:
sending 'zip' (632094 KB)...
OKAY [ 27.661s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 27.691s
Other problems when working with the ''ADB commands'' gives me the ''Device not found'' response.
I downloaded the RUU for my device as a .zip as there's no existing .exe version to be found. With no luck flashing it I might say. Due to the constant hanging when the file is ''Sending''.
( This is the RUU I downloaded: OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.zip )
And for 2 days with applying fix after fix and trial and error I'm coming nowhere! I'm thinking on formatting the whole cellphone and copy my ''manual copy of my cellphone'' into the formatted cellphone drive.
In the bootloader this information can be seen:
*** TAMPERED ***
*** RELOCKED *** (Along the lines of guides this happen. No idea how though
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.11.50.05.28
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012,17:10:57:-1
My cellphone has: Philz touch 5 CWM Base version 6.0,3,2 on it.
NOW! This is what actually works on my cellphone:
1. I can get into BootLoader on my HTC One S!
2. I can get into Fastboot on my HTC One S!
3. The Fastboot on my HTC One S recognizes as ''Fastboot USB'' on when I plug it into my computer.
4. My computer recognizes the cellphone as a ''removable disk''. And using the command ''Fastboot Devices'' in CMD lets me see the ''SH32HW401164'' number. Using the command ''Fastboot getvar all'' gives me this information:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4150mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
----
My plan was to flash this ROM into my phone if the stock one still showed issues: http://forum.xda-developers.com/showthread.php?t=2531065
This being said and again: My HTC One S is NOT flashed with a custom ROM! It has the same ROM it came with, all though, it has been unlocked -> Rooted. And never been S-off. it is still S-On.
Any help with this issues would be appreciated and thanks for this great forum

SOLVED flashed working ROM and fixed SD card mounting error.
After 3 weeks of frustration and trying I finally got my phone booting with a ROM. As I couldn't find any RUU.exe files for my phone and the RUU.zips didn't work either I had to go custom ROMing. I'll explain the whole process with steps I did so that others can read easily
1. Go into Bootloader, choose Fastboot and connect your phone with the USB cable. Open up CMD in your Fastboot/ADB folder by holding SHIFT+Right Click and type: ''Fastboot devices'' without the quotas, to see if your phone appear like SH32HW.... etc. You can also use the command: ''Fastboot getvar all'' to pull a few lines of comparable information.
2. Download the stock recovery file here: http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img , place it in the Fastboot/ADB folder and open CMD again, if you haven't already, in the Fastboot/ADB folder and type ''Fastboot flash recovery ville_recovery_signed.img''
Let the file flash and when it's done type ''Fastboot reboot-bootloader''
3. After the short reboot choose Clear Storage. Your phone might try to boot after this. just hold the power button + volume down to restart it into bootloader again. Then choose Factory Reset from bootloader menu. The phone might try to boot again after this but restart it manually into bootloader if it gets stuck.
4. After clearing storage and factory resetting go into Fastboot USB mode again and use CMD in the Fastboot/ADB folder again to flash your custom recovery file. I used TWRP 2.8.7.0.zip. This TWRP recovery is signed for HTC One S S4. The guide for the Viper ROM recommends the TWRP2.6.3.0 for phones with HBoot 2.15, and TWRP2.6.1.0 for Hboot 2.16 phones.
The command for flashing this file is ''Fastboot flash recovery twrp-2.8.7.0-ville.img''
5. After flashing the custom recovery reboot bootloader with the command ''Fastboot reboot-bootloader''. Then after the short reboot go into recovery from bootloader.
6. At this time your SD card should work. Choose to mount USB from the ''Mount'' menu in TWRP. Attach the USB cable if you haven't already. Transfer your ROM.zip file to your SD card with this method.
( I used the Viper ROM found here: http://venomroms.com/htc-one-s/ )
7. After the transfer is complete choose ''install from zip'' in TWRP and choose the ROM.zip of your choice.
( I choose the Viper_One_S_3.2.0.zip file and chose the ''full wipe'' option, removing apps I didn't want etc. )
8. After installation let the phone work it's magic for like 10-15 minutes if necessary. It'll hopefully boot into the new system in time and you can complete the setup
---
The importance is that the stock recovery steps up til I flashed TWRP again fixed the SD card error. There's more fixes you could try if this didn't work and they can be found here: http://forum.xda-developers.com/showthread.php?t=2086156

I told you to flash the stock recovery and make a factory reset from bootloader from the beginning. Glad you've sorted out finally
Sent from nowhere over the air...

Rapier said:
I told you to flash the stock recovery and make a factory reset from bootloader from the beginning. Glad you've sorted out finally
Sent from nowhere over the air...
Click to expand...
Click to collapse
Yes but it was hard finding a stock recovery. And the recovery that came with the phone did not work. So had to try lot of different ''what was supposed to be stock'' recoveries before I found one that worked Thanks by the way ^^

HTC-One-User said:
Yes but it was hard finding a stock recovery. And the recovery that came with the phone did not work. So had to try lot of different ''what was supposed to be stock'' recoveries before I found one that worked [emoji14] Thanks by the way ^^
Click to expand...
Click to collapse
I didn't have a link for it either. I had to do that only once (messed my sdcard) and I remember someone posted a link from MoDaCo where Paul O'Brian had it uploaded...if I remember right. But that was long time ago and I didn't have the link anymore
Sent from nowhere over the air...

Rapier said:
I didn't have a link for it either. I had to do that only once (messed my sdcard) and I remember someone posted a link from MoDaCo where Paul O'Brian had it uploaded...if I remember right. But that was long time ago and I didn't have the link anymore
Sent from nowhere over the air...
Click to expand...
Click to collapse
Hmm... My SD card actually got un-mountable and messed up after having stock ROM and just choosing to do a factory reset in the bootloader. That is when my problems started! But now after testing just this recovery and clearing storage, factory rest, flash new TWRP in exact that order fixd my issue. If I would factory reset before clearing storage and cache it would do nothing for me. It's weird but now it's ok and works ^^
Should have made a video of me restoring my phone to youtube so others can see to O.O
Edit: Made one here. it's not in awesome quality but it shows the whole process https://www.youtube.com/watch?v=_emclhywhlw

HTC One S ville c2 - NEED Help

So guys, i've got my HTC One S ville c2 ( S-ON, hboot 2.09 ) and i somehow soft-bricked it. I found the RUU for me but it's stuck at sending every time, in any USB port. I tried before to flash a custom rom, actually i tried to flash like 6 custom roms unfortunatelly it didn't work. An by didn't work i mean i was able to install the soft with no errors but when i restarted the phone, it was frozen at logo. I flashed boot.img so it's not that. I really don't know what else i could do. I think my phone does not support any custom rom. I am able to get to recovery and bootloader so any help would be greatly apreciated. At this very moment i'm watching my phone's screen and it has the grey HTC simple logo because i am giving the RUU another shot. Probably it won't work, as always. Thank in advance !!!

Relock your bootloader and try the RUU for you specify CID. I recomend use a Windows 7 pc and usb 2.0

JavierG123 said:
Relock your bootloader and try the RUU for you specify CID. I recomend use a Windows 7 pc and usb 2.0
Click to expand...
Click to collapse
i tried to flash the ruu but it just stays on sending 4ever. i used usb 2.0 and the version of the Ruu is corect. i check it before with fastboot getvar all. I just can't understand what's the problem. The checking is all fine but it just doesn't send the damn package to the phone. If someone could give me a working ROM for
"version: 0.5
version-bootloader: 2.09.0001
version-baseband: 16.05.20.16_M2
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT25NW410827
imei: 352762050257350
product: villec2
platform: HBOOT-8260
modelid: PJ4020000
cidnum: HTC__032
battery-status: good
battery-voltage: 3664mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: f616909f
hbootpreupdate: 11
gencheckpt: 0"
that would be great ...

Your pc recognize the phone in fastboot mode?

JavierG123 said:
Your pc recognize the phone in fastboot mode?
Click to expand...
Click to collapse
yes i said it can. otherwise how could i run "fastboot getvar all" ? anyway i managed to update the hboot version to 2.11.000. Now everything seems diferent. Even the well-know htc red message from boot "this build is for development purpuses only ... bla bla" has the row-spacing way smaller and when i enter recovery there is a message at the logo in the upper part "Entering recovery..." Maybe i am able to install some CM but i still have the flash the boot.img trough fastboot because i am S-ON.

JavierG123 said:
Your pc recognize the phone in fastboot mode?
Click to expand...
Click to collapse
ok. so i flash a CM 10.1 everything went fine. I flashed the boot.img from the zip and when i restart the phone It boots and instead of logo animation is just shows random green or red strips. What's going on?

Well... You should try search the SaM Rom thread, in this Forum (One S C2 develpment) install his recovery and his rom. Its based on stock rom
---------- Post added at 03:16 PM ---------- Previous post was at 03:09 PM ----------
@juganarucaliner steps to use a ruu
1)plug your phone to the PC and set it to charge only.
2)go to settings>applications>development>check USB Debugging.
3)go to settings>power>uncheck "fastboot".
4)remove your phone from the USB (charge).
5)hold the power button and shutdown your phone.
6)hold volume down button and hold down the power button,a white screen with options should appear.
7)select the first option (fastboot).
8)when in fastboot plug your USB cable into the phone and PC,you should see "fastboot USB".
9) now move to your PC and start the RUU setup,proceed normally with the wizard and hopefully the setup will run successfully.
note:do not run htc sync while updating,simply go to the HTC website and download the latest HTC sync,install it and make sure it installs the drivers and then shut it down.

JavierG123 said:
Well... You should try search the SaM Rom thread, in this Forum (One S C2 develpment) install his recovery and his rom. Its based on stock rom
Click to expand...
Click to collapse
I managed to install with aroma etc etc and then i flashed the boot.img inside /kernel/one s c2 but i am still stuck at logo. :crying::crying:

juganarucaliner said:
I managed to install with aroma etc etc and then i flashed the boot.img inside /kernel/one s c2 but i am still stuck at logo. :crying::crying:
Click to expand...
Click to collapse
So finally i was able to flash RUU from http://androidruu.com/index.php?developer=VilleC2
Follow these steps if you run into the problem i had:
1. install the ADB files. I had them before but it seems like they were corrupt or something. I am running Windows 10 now so for who is trying to do this on Windows 8, 8.1, 10 make sure you have the registry fix that can be found here http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337.
2. After you have succesfully managed to install all of this give the PC a restart
3. Try to flash the RUU for your device
4. After it completes unlock the bootloader and flash your recovery
5. Now you can update your firmware from 2.11 to 3.01 by following this guide here http://forum.xda-developers.com/showthread.php?t=2234559
6. Now it's your time to shine! Choose whatever Rom you want. but just don't forget to flash the boot.img after installation.
:fingers-crossed::fingers-crossed:Happy flashing !

HTC One M8 Softbricked and Unable to Flash

Hi, A friend gave me a Verizon HTC One M8 that was softbricked by a failed attempt to root or modify the device. I am unable to find out what the original owner did to the phone.
The phone will get stuck on the HTC logo for approximately two minutes and then reboot. I can get into the bootloader no problem, but the recovery and the factory wipe options go to the HTC logo and then get stuck at a black screen with the backlight on for approximately two minutes before rebooting. The command "fastboot oem rebootRUU" goes to the same HTC logo for approximately two minutes before rebooting, fastboot is unable to see the phone in this mode.
Because the bootloader is locked and cannot be unlocked because it is a Verizon, and the phone is S-ON, I am unsure how to fix the phone.
I have attempted to use RUU from a microsd card numerous times with the RUU images from here: http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845. the 4.4.4 one appears to complete successfully, but still bootloops after restarting.
Thank you in advance for your help.

I think (a redacted version of) the output from getvar-all would likely be helpful to see what state your phone is in and determine how to best resolve it.

Thank you for your quick reply. I have attached the "fastboot getvar all" output:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0926
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.605.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: <<SERIAL>>
(bootloader) imei: <<IMEI>>
(bootloader) imei2: Not Support
(bootloader) meid: <<MEID>>
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Well.....if you send that puppy to me I can s-off an attempt to reflash it for you. Not sure what else you can do with an s-on phone that you cant talk to in ruu mode.
Sent from my Nexus 6 using Tapatalk

While I appreciate your offer, I would like to try and resolve this without sending it out unless I really have to. Is there anything that you can think of that might work for me?
While I am unable to get the phone to boot into RUU mode for fastboot, I can get it to flash the RUU from microsd. For some reason it is still unable to boot after this. Is there another image or something I am doing wrong?
Thanks again for the help.

After you ran the ruu from SD did you attempt a factory reset? BTW, not sure if this helps your comfort level or not if it comes down to it but I have s-offed more vzw m9 than anyone. All done via mail.
Edit...and I would be more than willing to take a look remotely using team viewer.
Sent from my Nexus 6 using Tapatalk

When I attempt to do a factory reset, the HTC logo comes up and goes to a black screen for about 2 minutes and then bootloops. I am unable to format any partitions using fastboot and the only one that erases is cache. The big issue is that it is bootloader locked, otherwise I would have just flashed TWRP. I will contact you in private about that teamviewer help when I am at my computer. Thank you for the offer.

I thank dottat for all of his help over teamviewer.
Unfortunately, the phone has a locked emmc and is completely bricked.
Thank you everyone on this forum for your help.

So I'm having an eerily similar problem. The thing is I wasn't trying to do anything to my phone, it just randomly got stuck in a bootloop. I haven't tried anything with the RUU because I assumed it wouldn't work with verizon (I'm very new to all this) so I'm going to try later when I get the chance. What's the process to find out if the emmc is locked?

When I flashed a RUU with a newer version number then the one on it, after a reboot it would still be the old version number as if the flash did not take.

Which version number am I looking at? I know how to flash the RUU but I don't know exactly what I'm looking for there
---------- Post added at 08:46 PM ---------- Previous post was at 08:21 PM ----------
I tried a couple different files listed, and one seemed to flash correctly. I hit the update now option and now my phone won't turn on at all, no bootloader, no nothing. Bricked completely or am I waiting for something to happen??

Try charging up the phone for a bit. If that doesn't work you may have bricked it

yup, got bricked. oh well.

wmitchell2014 said:
yup, got bricked. oh well.
Click to expand...
Click to collapse
You left it on a charger? Does the light light up at all?
Sent from my SM-T320 using Tapatalk

nope, there is absolutely no response from the phone. Tried the battery recalibration thing and every other combination of things I can think of. I will leave it plugged in over night to see what happens but it was plugged in for a few hours today and nothing happened.

Attempted GPE conversion from VZW M8, no bootloader, no root, no adb, etc.
Not sure what to do at this point, have been to 10 different posts on ways to get this back to stock, or even usable and I cannot come out of this alive.
When I start up the Phone, it goes to the HTC One splash screen, then restarts, goes to it again, then goes to the Stock Recovery Screen with the Red Triangle.
I have tried to flash a rom etc using a sd card, but says this;
Install /sdcard...
Finding update package...
(waits about 2 minutes while loading)
Verifying update package...
Installation Aborted
Write host_mode:0 done
I get the red triangle recovery screen and can choose reboot system now, apply sd card, etc. as normal.
if I reboot it does the same thing.
Somehow in the conversion, my MID ended up as 0P6B17000, it used to be 0P6B20000
Cid is now 11111111, was VZW__001
I cannot access the bootloader screen so I cannot try to load using 0P6BIMG.zip
Can anyone put me out of my misery?

Connect it to a pc with adb and try "fastboot reboot-bootloader" to get from recovery to bootloader
Sent from my Nexus 5 using Tapatalk

pattafurr02 said:
Not sure what to do at this point, have been to 10 different posts on ways to get this back to stock, or even usable and I cannot come out of this alive.
When I start up the Phone, it goes to the HTC One splash screen, then restarts, goes to it again, then goes to the Stock Recovery Screen with the Red Triangle.
I have tried to flash a rom etc using a sd card, but says this;
Install /sdcard...
Finding update package...
(waits about 2 minutes while loading)
Verifying update package...
Installation Aborted
Write host_mode:0 done
I get the red triangle recovery screen and can choose reboot system now, apply sd card, etc. as normal.
if I reboot it does the same thing.
Somehow in the conversion, my MID ended up as 0P6B17000, it used to be 0P6B20000
Cid is now 11111111, was VZW__001
I cannot access the bootloader screen so I cannot try to load using 0P6BIMG.zip
Can anyone put me out of my misery?
Click to expand...
Click to collapse
If you are still s-off I can fix it. A team viewer session would help since your mid/cid are no longer standard.
Sent from my Nexus 6 using Tapatalk

dottat said:
If you are still s-off I can fix it. A team viewer session would help since your mid/cid are no longer standard.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
How do I go about doing that ?
Thank you !

pattafurr02 said:
How do I go about doing that ?
Thank you !
Click to expand...
Click to collapse
on PC,
https://www.teamviewer.com/en/download/windows.aspx