Database Develop

My HTC One is soft-bricked(?) and i have no idea what to do

Hello,
My phone is not rooted. It was still on factory setting, with no custom roms. I've been keeping up w/ the updates and i don't recall anything "special" happening before it was bricked yesterday night.
I tried accessing the fastboot screen (vol down + power button), and tried recovering, rebooting, and factory resetting, and they all sent it back to a freezing boot screen.
Using Hasoon2000's HTC One All-In-One Toolkit, I tried to boot it into bootloader, after a couple of hours, I saw a black screen w/ a red triangle in the middle, and after that, it just went back to being frozen at the Htc boot screen.
I have no idea what to do, any suggestions would help.
Thank You
-George Kayogre
Edit: Some specs in HBOOT:
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000

George Kayogre said:
Hello,
My phone is not rooted. It was still on factory setting, with no custom roms. I've been keeping up w/ the updates and i don't recall anything "special" happening before it was bricked yesterday night.
I tried accessing the fastboot screen (vol down + power button), and tried recovering, rebooting, and factory resetting, and they all sent it back to a freezing boot screen.
Using Hasoon2000's HTC One All-In-One Toolkit, I tried to boot it into bootloader, after a couple of hours, I saw a black screen w/ a red triangle in the middle, and after that, it just went back to being frozen at the Htc boot screen.
I have no idea what to do, any suggestions would help.
Thank You
-George Kayogre
Edit: Some specs in HBOOT:
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
Click to expand...
Click to collapse
Since, it is completely stock and you didn't change anything, it might be a hardware issue. I would return it to HTC or your carrier for repair. The black screen with the red triangle is the stock recovery screen. The other thing you might try is run a RUU if available. Can you post a fastboot getvar all with the imei and serialno removed?

George Kayogre said:
Hello,
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
Click to expand...
Click to collapse
don't make duplicate posts
I answered you here >> http://forum.xda-developers.com/htc-one/help/htc-one-soft-bricked-idea-to-t2851592

clsA said:
don't make duplicate posts
I answered you here >> http://forum.xda-developers.com/htc-one/help/htc-one-soft-bricked-idea-to-t2851592
Click to expand...
Click to collapse
Sorry about the other thread, i was instructed to make another one in the correct section, but then a mod also moved my old post to this section...making it 2...
Anyway, I'm unable to get my device recognized, all it shows is "waiting for device" for ever.
majmoz said:
Since, it is completely stock and you didn't change anything, it might be a hardware issue. I would return it to HTC or your carrier for repair. The black screen with the red triangle is the stock recovery screen. The other thing you might try is run a RUU if available. Can you post a fastboot getvar all with the imei and serialno removed?
Click to expand...
Click to collapse
I'm trying to get the fastboot getvar from Hasoon's program, but it's returning an "error: device not found".

George Kayogre said:
Sorry about the other thread, i was instructed to make another one in the correct section, but then a mod also moved my old post to this section...making it 2...
Anyway, I'm unable to get my device recognized, all it shows is "waiting for device" for ever.
I'm trying to get the fastboot getvar from Hasoon's program, but it's returning an "error: device not found".
Click to expand...
Click to collapse
first of all, if you are not returning your device to your carrier or htc like majmoz suggested above and you want to troubleshoot it yourself, you will need to get rid of that toolkit and learn how to use ADB and FASTBOOT from a command window. Toolkits aren't the best thing when troubleshooting. They often comes with outdated stuff.
Install your HTC drivers correctly on your computer
download and install the Android SDK or Minimal ADB and FASTBOOT
do the commands cIsA told you on your other thread and post the results. The output of "fastboot getval all" could also be useful

alray said:
first of all, if you are not returning your device to your carrier or htc like majmoz suggested above and you want to troubleshoot it yourself, you will need to get rid of that toolkit and learn how to use ADB and FASTBOOT from a command window. Toolkits aren't the best thing when troubleshooting. They often comes with outdated stuff.
Install your HTC drivers correctly on your computer
download and install the Android SDK or Minimal ADB and FASTBOOT
do the commands cIsA told you on your other thread and post the results. The output of "fastboot getval all" could also be useful
Click to expand...
Click to collapse
Tried that, but still can't get my pc to recognize the device in bootloader, althought HTC sync does pop up every time i connect it.
When i type "fastboot devices" in the command prompt, nothing happens, then "fastboot clear cache" just shows "waiting for device".
I have downloaded the latest drivers, currently updating HTC Sync, hoping it'd affect something

George Kayogre said:
Tried that, but still can't get my pc to recognize the device in bootloader, althought HTC sync does pop up every time i connect it.
When i type "fastboot devices" in the command prompt, nothing happens, then "fastboot clear cache" just shows "waiting for device".
I have downloaded the latest drivers, currently updating HTC Sync, hoping it'd affect something
Click to expand...
Click to collapse
uninstall htc sync and try again

alray said:
uninstall htc sync and try again
Click to expand...
Click to collapse
Tried w/ and w/o HTC sync, ensured drivers were installed...and "fastboot devices" still has no effect.

George Kayogre said:
Tried w/ and w/o HTC sync, ensured drivers were installed...and "fastboot devices" still has no effect.
Click to expand...
Click to collapse
try another usb cable, another usb port. If the drivers are correctly installed, and the usb port/cable are ok and you still can't use fastboot commands from bootloader, it might be an hardware issue.

alray said:
try another usb cable, another usb port. If the drivers are correctly installed, and the usb port/cable are ok and you still can't use fastboot commands from bootloader, it might be an hardware issue.
Click to expand...
Click to collapse
Finally got my device to be recognized, all I did was plug in my phone, boot in into bootloader...again and again...till it was recognized
majmoz said:
Since, it is completely stock and you didn't change anything, it might be a hardware issue. I would return it to HTC or your carrier for repair. The black screen with the red triangle is the stock recovery screen. The other thing you might try is run a RUU if available. Can you post a fastboot getvar all with the imei and serialno removed?
Click to expand...
Click to collapse
This is what "fastboot getvar all" returned:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.110
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *erased*
(bootloader) imei: *erased*
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4078mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
clsA said:
Unzip this to your desktop and open a command window from it's folder (right click - command prompt here)
plug in your phone to the pc boot to the bootloader with power + volume down
type fastboot devices
your phone serial number should be listed
now type fastboot erase cache
it should say something about formatting cache
now fastboot reboot
hopefully your phone will boot back up
Click to expand...
Click to collapse
I did run these commands, they were performed successfully, but my phone is still getting frozen on the boot screen

George Kayogre said:
Finally got my device to be recognized, all I did was plug in my phone, boot in into bootloader...again and again...till it was recognized
This is what "fastboot getvar all" returned:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.110
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *erased*
(bootloader) imei: *erased*
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4078mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I did run these commands, they were performed successfully, but my phone is still getting frozen on the boot screen
Click to expand...
Click to collapse
have you tried to perform a factory reset from the bootloader?

alray said:
have you tried to perform a factory reset from the bootloader?
Click to expand...
Click to collapse
Yep, that was the first thing i tried to do, but i was still stuck w/ the same problem.

George Kayogre said:
Yep, that was the first thing i tried to do, but i was still stuck w/ the same problem.
Click to expand...
Click to collapse
if your phone is still under warranty, send it for repair because the next actions will void the warranty:
You'll probably have to unlock the bootloader, flash a custom recovery and flash a rom.
Not sure why this happened on a 100% stock phone. Normally, users get in this situation when flashing custom roms

alray said:
if your phone is still under warranty, send it for repair because the next actions will void the warranty:
You'll probably have to unlock the bootloader, flash a custom recovery and flash a rom.
Not sure why this happened on a 100% stock phone. Normally, users get in this situation when flashing custom roms
Click to expand...
Click to collapse
Here's something new: after unlocking my phone, and having confirmed that i wanted all my "personal data erased", it just booted up normally and it worked, but then, while using it, t=it simply crashed...and got stuck in the bootloop again, which kinda points in the arrow of hardware issue again. I'm gonna try installing a rom (after i figure out how) and see where that leads me.
Update: Flashed CM11, phone still on boot loop, sending to repair soon.
Everyone, thanks for the help anyway, I really appreciate it.

Please help i bricked my htc vivid and now it cant enter recover

i unlocked the bootloader with unlocker v2 by Fenguepay after that it was partially rooted so after that i rebooted and everything was fine then i tried to flash rom with cm-11-20140628-unofficial-pyramid.zip and gapps it got stuck on the htc white screen, so i downloaded yet another rom: resurrection remix - kk- v5. 1.2-20140521-holiday.zip and pa gapps modular mini 4.4.2-20131230-signed.zip yet it still got stucked on d htc white screen. That was when i used vivid all in one kit v3.0 to relock so i could try flahing factory RUU but no way. The worst now is that the phone just cant turn off once any usb is connected on d pc it turns to fastboot usb and on charger it turns to fastboot ac automatically enters hboot and stays there heating up like cray cray and it cant enter recovery. i have s-on and the boot loader is on relocked. please i really need help. my one and only phone is dying.. Thanks in Anticipation

kingsolo said:
i unlocked the bootloader with unlocker v2 by Fenguepay after that it was partially rooted so after that i rebooted and everything was fine then i tried to flash rom with cm-11-20140628-unofficial-pyramid.zip and gapps it got stuck on the htc white screen, so i downloaded yet another rom: resurrection remix - kk- v5. 1.2-20140521-holiday.zip and pa gapps modular mini 4.4.2-20131230-signed.zip yet it still got stucked on d htc white screen. That was when i used vivid all in one kit v3.0 to relock so i could try flahing factory RUU but no way. The worst now is that the phone just cant turn off once any usb is connected on d pc it turns to fastboot usb and on charger it turns to fastboot ac automatically enters hboot and stays there heating up like cray cray and it cant enter recovery. i have s-on and the boot loader is on relocked. please i really need help. my one and only phone is dying.. Thanks in Anticipation
Click to expand...
Click to collapse
.....
Pyramid is the HTC Sensation...
Holiday is the Vivid, Raider, Velocity...
Hopefully... When you find the right ROM... You can save your phone...
When you do... Just flash the ROM... See if it boots

Thanks
rignfool said:
.....
Pyramid is the HTC Sensation...
Holiday is the Vivid, Raider, Velocity...
Hopefully... When you find the right ROM... You can save your phone...
When you do... Just flash the ROM... See if it boots
Click to expand...
Click to collapse
ok bro. downloaded htc_vivid_att_RUU_3.26.502.56_R23_US from htc dev but got error 115 dont know where else to download from. would appreciate any sure link to download from
i really do appreciate your concern. Big ups

i just downloaded this too from htc dev but couldnt use it bcos i dont know how i can use it.holiday-2.6.35-gb-30-crc-c1166ee.tar.gz, still very much confused

Help oooooooooooo
this is what i see when i enter Hboot
**** UNLOCKED****
HOLIDAY PVT SHIP S-ON RL
HBOOT-1.85.0025
MICROP-0360
eMMC-boot
Mar 1 2012,17:09:49
HBOOT USB (highlighted in BLUE)
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT (its highlighted in blue)
RECOVERY (its highlighted in green)
FACTORY RESET (its highlighted in red)
CLEAR STORAGE (its highlighted in black)
SIMLOCK (its highlighted in blue)
IMAGE CRC (its highlighted in black)
with three anoying androd image on a skate board dancing and waving hands
Using Vivid_All-In-One_Kit_v3.0 this is wat i see on my screen
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.85.0025
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: 0360
(bootloader) version-main:
(bootloader) serialno: HT1AJVJ00491
(bootloader) imei: 356298040317380
(bootloader) product: holiday
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH3910000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3930mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: b215ac78
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.502s
C:\Users\user\Desktop\Vivid_All-In-One_Kit_v3.0\data>.
please i would really really appreiate a guide to how i can solve this myterious nightmare. THANKS

help a confused dude
what i might have read doesnt matter. i am willing to start afresh if guided. your well appreciated guide is what i crave for

Relock your boot loader...
Run ruu...
Should solve it

I cant seem to find the right ruu for my htc vivid att
rignfool said:
Relock your boot loader...
Run ruu...
Should solve it[/QUOTE
I RELOC KED BOOTLOADER JUST LIKE U ADVISED, RAN RUU WITH Gingerbread_De-Sensified_v0.2 AND GOT THIS ERROR TEXT
sending 'zip' (203059 KB)...
OKAY [ 20.431s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 25.222s
C:\Users\user\Desktop\Vivid_All-In-One_Kit_v3.0\data>
THANKS FOR LEADING ME THUS FAR.... I AM BEGINNING TO SEE A LIGHT AT THE END OF THIS MISERY OF SLEEPLESS NIGHTS . YOU ARE TRULY GOD SENT. MORE GREASE TO YOUR ELBOW:good::good:
Click to expand...
Click to collapse

Nothing seems to be working
I REMOVED MY SD CARD AND COPIED Gingerbread_De-Sensified_v0.2 TO THE ROOT FOLDER OF SD CARD, INSERTED IT AND BOTTED TO H BOOT AND I GOT THIS SAME ERROR
RUU
PARSING ANDROID-INFO FAIL!
UPDATE FAIL!

Sthap
An ruu is a whole rom and everything...
You just run the ruu and boot...
And...
Your on ICS boot loader...
The gingerbread thing won't work

pls wat will work for me? thanks for ur time

Weird black screen problem

Hello guys,
I have a weird problem that happened not to my phone but a friend of mine... I'll try to make the details as good as possible but it may be different since I did not own the phone, but as I said, a friend did.
She says it was Sense6.0 4.4.2 and that one day the phone booted, showed the HTC logo like 3 times (between bootloop) and it went down (power off), so she charged it for like 1 days but it didn't turn the display on... Now, it had pattern lock so getting adb to work was a complete PITA but we figured that the phone wasn't dead when we tried to call her and she swept the screen to answer and she did, so, after a lot of pain, we managed to unlock it blindly and accept the recogniztion so we could have adb...
Now, we rebooted into fastboot, unlocked bootloader (which wiped the system to factory reset) and installed a custom kernel/recovery (via fastboot)
The phone has 1.57 HBOOT and I understand firewater works, but here is the major problem: I don't have access to Wireless because I cant see a damn thing so were screwed there... 3G connection doesn't work at all and I go and ping and it says failed...
ALTHOUGH I tried rumrunner (before I knew HBOOT was 1.57) and somehow it rebooted and the screen turned on so I figured the screen wasnt dead, but as soon as it finished booting, the screen went off again forever...
The phone has CID: HTC__332 (Latin American variant) so I cant find a suitable RUU so I can flash without S-OFF
I am really screwed but maybe anyone here with some experience can shed a light here and save an M7
PD: I have working adb and fastboot but just through command line

Poesini said:
Hello guys,
I have a weird problem that happened not to my phone but a friend of mine... I'll try to make the details as good as possible but it may be different since I did not own the phone, but as I said, a friend did.
She says it was Sense6.0 4.4.2 and that one day the phone booted, showed the HTC logo like 3 times (between bootloop) and it went down (power off), so she charged it for like 1 days but it didn't turn the display on... Now, it had pattern lock so getting adb to work was a complete PITA but we figured that the phone wasn't dead when we tried to call her and she swept the screen to answer and she did, so, after a lot of pain, we managed to unlock it blindly and accept the recogniztion so we could have adb...
Now, we rebooted into fastboot, unlocked bootloader (which wiped the system to factory reset) and installed a custom kernel/recovery (via fastboot)
The phone has 1.57 HBOOT and I understand firewater works, but here is the major problem: I don't have access to Wireless because I cant see a damn thing so were screwed there... 3G connection doesn't work at all and I go and ping and it says failed...
ALTHOUGH I tried rumrunner (before I knew HBOOT was 1.57) and somehow it rebooted and the screen turned on so I figured the screen wasnt dead, but as soon as it finished booting, the screen went off again forever...
The phone has CID: HTC__332 (Latin American variant) so I cant find a suitable RUU so I can flash without S-OFF
I am really screwed but maybe anyone here with some experience can shed a light here and save an M7
PD: I have working adb and fastboot but just through command line
Click to expand...
Click to collapse
So does the screen come on when the phone is booted to the bootloader and recovery?
Can you post fastboot getvar all?
Code:
fastboot getvar all
Post the output here but remove imei and serial numbers before posting.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
So does the screen come on when the phone is booted to the bootloader and recovery?
Can you post fastboot getvar all?
Code:
fastboot getvar all
Post the output here but remove imei and serial numbers before posting.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
No, the screen never turn on... It did only when trying the first time rumrunner but not anymore (But so, I know the screen isn't dead)
Here is the getvar all
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.15.599.101
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__332
(bootloader) battery-status: good
(bootloader) battery-voltage: 3854mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s

Poesini said:
No, the screen never turn on... It did only when trying the first time rumrunner but not anymore (But so, I know the screen isn't dead)
Here is the getvar all
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.15.599.101
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__332
(bootloader) battery-status: good
(bootloader) battery-voltage: 3854mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Click to expand...
Click to collapse
It does sound like a dead LCD to me. Weird how it came on once while running rumrunner though. Try powering off the device then hold a it under a bright light hold power on + volume down for 90+ seconds. Maybe a fault with proximity sensor.
There is no ruu you can use while s-on and I can't even find a firmware you can try to flash. So if that doesn't work I don't know what else to try
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
It does sound like a dead LCD to me. Weird how it came on once while running rumrunner though. Try powering off the device then hold a it under a bright light hold power on + volume down for 90+ seconds. Maybe a fault with proximity sensor.
There is no ruu you can use while s-on and I can't even find a firmware you can try to flash. So if that doesn't work I don't know what else to try
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Holding the device under a bright light seems to power on the device SOMETIMES with the HTC logo visible and then it gets past that (with a little backlight movement meanwhile -dimmer- or -brighter-) and then back to desktop with no light
Is there any way to disable the proximity sensor or maybe flash a custom ROM via adb commands to flash it into recovery inside OS (TWRP 2.8.1.0 right now) or something?

Poesini said:
Holding the device under a bright light seems to power on the device SOMETIMES with the HTC logo visible and then it gets past that (with a little backlight movement meanwhile -dimmer- or -brighter-) and then back to desktop with no light
Is there any way to disable the proximity sensor or maybe flash a custom ROM via adb commands to flash it into recovery inside OS (TWRP 2.8.1.0 right now) or something?
Click to expand...
Click to collapse
Well that's promising. You can push a Rom with adb but you need the recovery menu to install it which may prove difficult if you can't see it.
To push the Rom put it in your fastboot folder and rename it rom.zip. connect the usb with the phone for adb and type in the command window
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push completes.
You may be better to use TWRP 2.6.3.3 to avoid install problems. Remember to
Code:
fastboot erase cache
when you flash a new recovery.
And keep using the bright light power on trick. May be give the sensors a clean (top left of the phone).
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
Well that's promising. You can push a Rom with adb but you need the recovery menu to install it which may prove difficult if you can't see it.
To push the Rom put it in your fastboot folder and rename it rom.zip. connect the usb with the phone for adb and type in the command window
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push completes.
You may be better to use TWRP 2.6.3.3 to avoid install problems. Remember to
Code:
fastboot erase cache
when you flash a new recovery.
And keep using the bright light power on trick. May be give the sensors a clean (top left of the phone).
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
I know my ways to push files via ADB, but I am saying like SuperSU does when it asks if you want to update it via TWRP option where it reboots directly to recovery and flashes a zip without you doing anything
I could push many files via ADB, but I couldn't flash them correctly (and I don't want to screw this phone) without seeing the screen

Poesini said:
I know my ways to push files via ADB, but I am saying like SuperSU does when it asks if you want to update it via TWRP option where it reboots directly to recovery and flashes a zip without you doing anything
I could push many files via ADB, but I couldn't flash them correctly (and I don't want to screw this phone) without seeing the screen
Click to expand...
Click to collapse
Flash twrp 2.6.3.3 newer versions of twrp can be temperamental and probably why your having trouble flashing roms
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
---------- Post added at 07:26 PM ---------- Previous post was at 07:07 PM ----------
Try the bright light trick again but this time power off the device. Hold the sensors close to the light
Hold volume up and down +power for 60 secs the phone will bootloop while your holding the buttons. Hopefully that will be enough to reset the sensor. :fingers-crossed:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

[Q] HTC ONE (M7UL) imei problems + rebooting + s-on

Hi you all,
So to start things off i might say i tried alot of things to revive my htc one.
What happenend?
I wanted to give my htc one some new life so I thought lets factory reset it. All worked well but then the horror just began. My One began rebooting and rebooting itself over and over. So what i did next was enabled flight mode throught the power button and restarted the phone. So from then on it was running for about 30 seconds untill it starts rebooting again.
So what I did is unlock the phone and tried several Custom Roms. The only ones working are old cm11 roms, but I can not get S-Off to reflash the firmware because I am stuck with an eMMC 9001xxxxx... chip, so I guess bad luck for me.
So now my phone will not detect ANY SIM Card and will not show any imei number or baseband in the os. In the bootloader however they are still there, both of them.
RUU's will not work for me as I am S-ON and stuck on hboot 1.57
SunShine is not working either as my phone shuts down after aprox. 30 seconds on sense rom.
Firewater is not working either as it has an 9001.... eMMC chip.
my getvar stats:
PHP:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3972mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
So my question is are there still any suggestions for me, that I didn't do or just overlooked?
So I would appreciate anything, before tearing it apart..
Cheers

shieldeverything said:
Hi you all,
So to start things off i might say i tried alot of things to revive my htc one.
What happenend?
I wanted to give my htc one some new life so I thought lets factory reset it. All worked well but then the horror just began. My One began rebooting and rebooting itself over and over. So what i did next was enabled flight mode throught the power button and restarted the phone. So from then on it was running for about 30 seconds untill it starts rebooting again.
So what I did is unlock the phone and tried several Custom Roms. The only ones working are old cm11 roms, but I can not get S-Off to reflash the firmware because I am stuck with an eMMC 9001xxxxx... chip, so I guess bad luck for me.
So now my phone will not detect ANY SIM Card and will not show any imei number or baseband in the os. In the bootloader however they are still there, both of them.
RUU's will not work for me as I am S-ON and stuck on hboot 1.57
SunShine is not working either as my phone shuts down after aprox. 30 seconds on sense rom.
Firewater is not working either as it has an 9001.... eMMC chip.
my getvar stats:
PHP:
(bootloader) version: 0.5(bootloader) version-bootloader: 1.57.0000(bootloader) version-baseband: 4A.21.3263.04(bootloader) version-cpld: None(bootloader) version-microp: None(bootloader) version-main: 6.09.401.10(bootloader) version-misc: PVT SHIP S-ON(bootloader) serialno: (bootloader) imei: (bootloader) meid: 00000000000000(bootloader) product: m7_ul(bootloader) platform: HBOOT-8064(bootloader) modelid: PN0710000(bootloader) cidnum: HTC__102(bootloader) battery-status: good(bootloader) battery-voltage: 3972mV(bootloader) partition-layout: Generic(bootloader) security: on(bootloader) build-mode: SHIP(bootloader) boot-mode: FASTBOOT(bootloader) commitno-bootloader: dirty-6d8a0b9b(bootloader) hbootpreupdate: 11(bootloader) gencheckpt: 0
So my question is are there still any suggestions for me, that I didn't do or just overlooked?
So I would appreciate anything, before tearing it apart..
Cheers
Click to expand...
Click to collapse
You don't need s-off to flash firmware. You only need s-off to downgrade or to use custom firmware. You will however need to relock your bootloader. Although I should tell you Unknown imei & Baseband often turns out to be a hardware problem.
You can flash this firmware with a relocked bootloader. You will need to 're flash custom recovery and Rom to boot the phone afterwards. Unless you flash a stock Rom first, Stock Rom can be downloaded here http://forum.xda-developers.com/htc-one/development/rom-4-4-3-sense-6-6-09-401-5-100-stock-t2854300
Firmware download
http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/6.09.401.10.zip
Download it and put it in your fastboot folder and rename it firmware.zip.
Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Code:
fastboot oem rebootRUU
--- case sensitive. ---^^^
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip firmware.zip
The second flash will take a little longer and this time it will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.
Code:
fastboot reboot-bootloader
If you found my posts helpful, no need to say thanks. There's a button for that

Danny201281 said:
You don't need s-off to flash firmware. You only need s-off to downgrade or to use custom firmware. You will however need to relock your bootloader. Although I should tell you Unknown imei & Baseband often turns out to be a hardware problem.
You can flash this firmware with a relocked bootloader. You will need to 're flash custom recovery and Rom to boot the phone afterwards. Unless you flash a stock Rom first, Stock Rom can be downloaded here http://forum.xda-developers.com/htc-one/development/rom-4-4-3-sense-6-6-09-401-5-100-stock-t2854300
Firmware download
http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/6.09.401.10.zip
Download it and put it in your fastboot folder and rename it firmware.zip.
Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Code:
fastboot oem rebootRUU
--- case sensitive. ---^^^
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip firmware.zip
The second flash will take a little longer and this time it will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.
Code:
fastboot reboot-bootloader
If you found my posts helpful, no need to say thanks. There's a button for that
Click to expand...
Click to collapse
Ok cheers m8!
I am gonna try it right now. Yeah I heard about the hardware problem, but I was thinking mine might be not because it happened after a factory reset (done in the os itself). I once was able to bring back baseband and imei but I just can't remember what exactely I did.
So I am going to report back as soon as I tried. I am wondering.
Btw you know what hardware defect actually would cause it (just wondering)
Thx!

shieldeverything said:
Ok cheers m8!
I am gonna try it right now. Yeah I heard about the hardware problem, but I was thinking mine might be not because it happened after a factory reset (done in the os itself). I once was able to bring back baseband and imei but I just can't remember what exactely I did.
So I am going to report back as soon as I tried. I am wondering.
Btw you know what hardware defect actually would cause it (just wondering)
Thx!
Click to expand...
Click to collapse
With your phone s-on and on the latest firmware there's not much else you can do but flash the firmware package I linked. If you can get s-off you can try an ruu.
From a hardware perspective It's the antenna connector pin that causes the issue as far as I'm aware. I only know of one that was repaired without returning to HTC and the antenna connector pin was the cause. Replacing it solved the problem.
If you found my posts helpful, no need to say thanks. There's a button for that

Danny201281 said:
With your phone s-on and on the latest firmware there's not much else you can do but flash the firmware package I linked. If you can get s-off you can try an ruu.
From a hardware perspective It's the antenna connector pin that causes the issue as far as I'm aware. I only know of one that was repaired without returning to HTC and the antenna connector pin was the cause. Replacing it solved the problem.
If you found my posts helpful, no need to say thanks. There's a button for that
Click to expand...
Click to collapse
So I did everything and it worked. But only for 5-10 minutes and then it startet rebooting again and again. So I guess this is a hardware problem too and as I don't have any warranty or something there my m7ul goes...
Thx for your help anyways!

"Active cmdline overflow!"

Hi there, I must have flashed the wrong sense ROM. I am extremely noobish, so bare with me.
I tried following this amazing guide: http://forum.xda-developers.com/showthread.php?t=2739126 but have had no luck when it comes to flashing the recovery indicated.
"C:\adb>fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img
error: cannot load 'twrp-recovery-2.7-m7-nobcb.img'"
It looks like I entered it right...
My phone will power on and function OK with data and text, but cannot make calls. Sometimes it'll reboot into hboot when I plug it into USB/AC. I have access to fastboot, but not adb, nor recovery.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: `
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35...
(bootloader) imei: 3559...
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4118mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-331585dd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thank you for your time, XDA!

Have you selected the Fastboot option in bootloader before you flash that?
Sent from my HTC One using Tapatalk

cyrusct82 said:
Have you selected the Fastboot option in bootloader before you flash that?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Yes and it shows under "fastboot devices"

It's now managed to have gotten worse and will only boot into the spash screen, then Fastboot (not Hboot).
If I remove the sim card, it will boot up normally (unless it's plugged into USB/AC). If I insert the sim, or plug in the microUSB, it will shortly thereafter crash into fastboot.

1- error: cannot load -> means the filename is wrong
2- Are you able to get to any kind of stable (or at least semi-stable) part; ROM or TWRP?
3- can you please provide the link (thread and file please) of what you flashed; so that we can look what was corrupted

nkk71 said:
1- error: cannot load -> means the filename is wrong
2- Are you able to get to any kind of stable (or at least semi-stable) part; ROM or TWRP?
3- can you please provide the link (thread and file please) of what you flashed; so that we can look what was corrupted
Click to expand...
Click to collapse
1) I tried simplifying the name to TWRPnbc.img and it's still says failed
2) I was able to boot into the ROM, make texts and use data reliably for a bit, once this issue started, but now it is so bad I can only access fastboot (including presence in "fastboot devices" of fastboot commands). Hboot does not acknowledge USB, adb devices shows nothing (device manager shows nothing in Hboot mode) and attempting to load the ROM kicks me back to Fastboot (not Hboot). Recovery kicks me back to Fastboot as well :crying:
3)It was a while ago that I flashed this ROM and it WAS stable for nearly 6 months, but I think it was just the first ROM of the list for the GURU resets, here:
http://www.htc1guru.com/downloads/stock-rom-downloads/
The version of TWRP I was trying to flash, if you are interested, is in the guide/link in the OP.
Thank you for your time and attention, nkk71!

Enigmatic Fart said:
1) I tried simplifying the name to TWRPnbc.img and it's still says failed
2) I was able to boot into the ROM, make texts and use data reliably for a bit, once this issue started, but now it is so bad I can only access fastboot (including presence in "fastboot devices" of fastboot commands). Hboot does not acknowledge USB, adb devices shows nothing (device manager shows nothing in Hboot mode) and attempting to load the ROM kicks me back to Fastboot (not Hboot). Recovery kicks me back to Fastboot as well :crying:
3)It was a while ago that I flashed this ROM and it WAS stable for nearly 6 months, but I think it was just the first ROM of the list for the GURU resets, here:
http://www.htc1guru.com/downloads/stock-rom-downloads/
The version of TWRP I was trying to flash, if you are interested, is in the guide/link in the OP.
Thank you for your time and attention, nkk71!
Click to expand...
Click to collapse
1- renaming the file is no problem, but you probably ended up with <NAME>.img.img (double extension due to Windows hiding known extensions), hence the use for Windows Command Prompt - DIR command and TAB-completion
2- you being able to boot (to some extent is good-ish)
3- the htc1guru files are meant for the HTC One M7, so nothing wrong there
i'll need to catch up with you tomorrow, as i'm off for tonight, take it easy

nkk71 said:
1- renaming the file is no problem, but you probably ended up with <NAME>.img.img (double extension due to Windows hiding known extensions), hence the use for Windows Command Prompt - DIR command and TAB-completion
2- you being able to boot (to some extent is good-ish)
3- the htc1guru files are meant for the HTC One M7, so nothing wrong there
i'll need to catch up with you tomorrow, as i'm off for tonight, take it easy
Click to expand...
Click to collapse
Cool man, I'll run through and try to flash it again in the meantime and edit this post with results.
Thanks again for your help! Peace!
EDIT: OK, I see what the issue was, but a new one popped up. So I was attempting to flash the recovery I placed in my phone's storage. I now have "TWRP.img" (latest TWRP) and "TWRPnbcb.img" (the no bcb one from that guide) in my adb folder (where fastboot is) on my PC and have attempted to flash both recoveries for S&Gs.
Here are the results:
"C:\Windows\system32>cd C:\adb
C:\adb>fastboot devices
HT35xxxxxx... fastboot
C:\adb>fastboot flash recovery TWRPnbcb.img
sending 'recovery' (11278 KB)...
FAILED (command write failed (No such device or address))
finished. total time: -0.000s
C:\adb>fastboot flash recovery TWRP.img
sending 'recovery' (12534 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.016s"

Last ditch bump! I don't want my phone retire in a junk drawer!

Enigmatic Fart said:
Last ditch bump! I don't want my phone retire in a junk drawer!
Click to expand...
Click to collapse
please post a "fastboot oem last_dmesg", after trying to flash something
@alray, might be able to decipher that
(sorry for the ping)