Hi all,
I have refrained from posting because I thought I would just read, but now I'm at the end of my rope. I just got my ATT htc one m8. I am on T-Mobile, but the price was right for this one.
Anyway I converted my phone right out of the box literally to GPE. I also used sunshine to unlock, and s-off. Both of these seemed to go off with little trouble.
BTW: ADB fastboot, drivers and such are installed correctly.
Things were fine, so I decided to play around some more. I preceded to revert back to sense so, I could play with more roms.
Needless to say I have done a lot of trial and error, so I will tell you what's going on now. Hopefully I didn't brick anything, and hopefully it's an easy fix.
I am s-off
Here is a Getvar all. My phone is no longer seen by adb, so commands do nothing I got this read out by using the toolkit, but prefer manual.
Also I have absolutely no ROM installed so I can not enable debugging mode, I cant do anything. Is there an easy way to re-unlock the boot loader? I don't want to go through htcdev seeing as I went with sunshine.
Sorry if this is noob, but I have struggled for like the last 20 hours trying to figure this out on my own.
Bootloader says relocked (relocked due to trying to go back)
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA43SWM04814
(bootloader) imei: 358718050247696
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.015s
>
This should be in Q&A thread....
TireIron431 said:
Here is a Getvar all. My phone is no longer seen by adb, so commands do nothing I got this read out by using the toolkit, but prefer manual.
Also I have absolutely no ROM installed so I can not enable debugging mode, I cant do anything. Is there an easy way to re-unlock the boot loader? I don't want to go through htcdev seeing as I went with sunshine.
>
Click to expand...
Click to collapse
fastboot oem unlock
Sorry I messed up. If you just updated your firmware, then you will need to get new token from HTCdev. The /fastboot oem unlock/ only works with GPE hboot. My guess is that each hboot version comes with different unlocktoken. I just updated my firmware and had to grab a new unlock token as well (coming back from GPE).
:fingers-crossed:
TireIron431 said:
Hi all,
I have refrained from posting because I thought I would just read, but now I'm at the end of my rope. I just got my ATT htc one m8. I am on T-Mobile, but the price was right for this one.
Anyway I converted my phone right out of the box literally to GPE. I also used sunshine to unlock, and s-off. Both of these seemed to go off with little trouble.
BTW: ADB fastboot, drivers and such are installed correctly.
Things were fine, so I decided to play around some more. I preceded to revert back to sense so, I could play with more roms.
Needless to say I have done a lot of trial and error, so I will tell you what's going on now. Hopefully I didn't brick anything, and hopefully it's an easy fix.
I am s-off
Here is a Getvar all. My phone is no longer seen by adb, so commands do nothing I got this read out by using the toolkit, but prefer manual.
Also I have absolutely no ROM installed so I can not enable debugging mode, I cant do anything. Is there an easy way to re-unlock the boot loader? I don't want to go through htcdev seeing as I went with sunshine.
Sorry if this is noob, but I have struggled for like the last 20 hours trying to figure this out on my own.
Bootloader says relocked (relocked due to trying to go back)
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA43SWM04814
(bootloader) imei: 358718050247696
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.015s
>
Click to expand...
Click to collapse
I can help you with this...don't try anything else to your phone you will just make it harder to fix. question how did you try to convert back I need to know what all u did?
I don't remember everything I don't think.. All I did was chamge the cid a few times. I tried to install stock recoveries, I tried install anything I could. Everything seemed to fail. After I changed the cid to stock the pc stopped seeing it from what I remember. Right now all I know is that these is no recovery on it, so no twrp, and no os...and I cant get the pc to see it. I will try to get it recognized by the pc but that's all til I hear back.
abd will not work in fastboot environment. As long as your phone says "Fastboot USB connected," you are still good to go. You must grab a new unlock token from htcdev and then proceed, because it seems that each new hboot has new unlock token. Otherwise you could unlock bootloader the S-off way, which I am not aware of (my phone is S-on) :fingers-crossed:
TireIron431 said:
I don't remember everything I don't think.. All I did was chamge the cid a few times. I tried to install stock recoveries, I tried install anything I could. Everything seemed to fail. After I changed the cid to stock the pc stopped seeing it from what I remember. Right now all I know is that these is no recovery on it, so no twrp, and no os...and I cant get the pc to see it. I will try to get it recognized by the pc but that's all til I hear back.
Click to expand...
Click to collapse
I have s-off through sunshine, do I have to go through htc, or is there a way to do it again with sunshine? My phone still says fastboot usb, but commands don't work.
TireIron431 said:
I have s-off through sunshine, do I have to go through htc, or is there a way to do it again with sunshine? My phone still says fastboot usb, but commands don't work.
Click to expand...
Click to collapse
You got sdcard an can boot to bootloader rt ? If so we will install twrp like that first off
Yes I have sd card, and am at the fastboot usb screen
TireIron431 said:
Yes I have sd card, and am at the fastboot usb screen
Click to expand...
Click to collapse
Perfect. Hit me up on hangouts I should be able to get u up an running might be a very a long process. Did one last night took 4 hours. But dude is up an running. I'm going to pm you my hangouts email now.
Got it all sorted out thanks to Tigerstown. Man that was a mess lol. I appreciate the assist.
Now to try some not so stupid things. lol
TireIron431 said:
Got it all sorted out thanks to Tigerstown. Man that was a mess lol. I appreciate the assist.
Now to try some not so stupid things. lol
Click to expand...
Click to collapse
Just glad to help an glad your phone is backing in working order
Related
okay,
I've unlocked the bootloader, rooted it, it's s-on and installed cm11. After less than a day, I've decided to go back to stock. Unfortunately, because cm11 is kitkat 4.4 it seems I can't even use an ruu, as they'll only go to 4.3 (which it seems i can't use because with s-on, I can't downgrade firmwares).
I've used Twrp 2.6.3.3 for recovery.
i've tried to use moonshine and rum runner, but they both fail, presumably because i've got cm11 installed. Also, when I connect to the pc, it only comes up as a media player or camera (depending on the settings in cyanogenmod), I've got debugging on and i believe everything else I should have.
In device manager, it calls itself "My HTC", yet in utorrent "HTC Aria"
When running (in cmd) "adb devices" it shows my phone, but when I do "fastboot devices" nothing comes up.
i've tried installing htc drivers, but nothing seems to change it. Some have mentioned forcing drivers but I don't know where to get the specific htc one driver.
in the bootloader this is what comes up:
hboot 1.44
m7ul pvt ship s-on rh
radio 4A.12.3750.20
open dsp v31.120.274.0617
eMMC-boot
what are my next steps/options?
damiancds said:
okay,
I've unlocked the bootloader, rooted it, it's s-on and installed cm11. After less than a day, I've decided to go back to stock. Unfortunately, because cm11 is kitkat 4.4 it seems I can't even use an ruu, as they'll only go to 4.3 (which it seems i can't use because with s-on, I can't downgrade firmwares).
I've used Twrp 2.6.3.3 for recovery.
i've tried to use moonshine and rum runner, but they both fail, presumably because i've got cm11 installed. Also, when I connect to the pc, it only comes up as a media player or camera (depending on the settings in cyanogenmod), I've got debugging on and i believe everything else I should have.
In device manager, it calls itself "My HTC", yet in utorrent "HTC Aria"
When running (in cmd) "adb devices" it shows my phone, but when I do "fastboot devices" nothing comes up.
i've tried installing htc drivers, but nothing seems to change it. Some have mentioned forcing drivers but I don't know where to get the specific htc one driver.
in the bootloader this is what comes up:
hboot 1.44
m7ul pvt ship s-on rh
radio 4A.12.3750.20
open dsp v31.120.274.0617
eMMC-boot
what are my next steps/options?
Click to expand...
Click to collapse
cm 11 did'nt update your firmware
what's your results for fastboot getvar all
run it from the bootloader screen / fastboot usb (remove your serial no and iemi)
all it says is "< waiting for device >"
this leads me to believe there's a driver error?
Sorry, I'm an idiot
C:\OneDrivers_Fastboot\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4315mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.056s
damiancds said:
all it says is "< waiting for device >"
this leads me to believe there's a driver error?
Sorry, I'm an idiot
C:\OneDrivers_Fastboot\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4315mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.056s
Click to expand...
Click to collapse
this is the last AT&T RUU it will update you to android 4.3 >>
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
if that link is slow you can get it directly from HTC here >>
http://www.htc.com/us/support/htc-one-att/news/
you'll have to relock your bootloader
fastboot oem lock
then run the RUU with your phone sitting at the fastboot usb screen
Worked beautifully. Thank You.
there's only two niggling things. when you pull down for your notifications, in the top right used to be settings, now it's quick tiles like cm11.
Also, in my computer, the device shows up as portable media player, where it used to just show up as htc one and an icon that looked like it. (from quick reading, it seems this is normal.)
Thanks again for all your help
damiancds said:
Worked beautifully. Thank You.
there's only two niggling things. when you pull down for your notifications, in the top right used to be settings, now it's quick tiles like cm11.
Also, in my computer, the device shows up as portable media player, where it used to just show up as htc one and an icon that looked like it. (from quick reading, it seems this is normal.)
Thanks again for all your help
Click to expand...
Click to collapse
yeah welcome to android 4.3 .. it's different, wait till you get sense 5.5 in the kitkat update
clsA said:
yeah welcome to android 4.3 .. it's different, wait till you get sense 5.5 in the kitkat update
Click to expand...
Click to collapse
I know now, a rough search turned up the same....
One last question,
I'm sticking with stock, but i want to root it, everything i've done has been unsuccessful, where before first time and it was done, I was reading the guide over here, http://forum.xda-developers.com/showthread.php?t=2273376&page=2 , and it mentions that I can't root a stock rom? that means I would need to grab one of the rooted ones then, correct? I know I've seen a link to them around here, but can't seem to find it, let alone which one I should use.
damiancds said:
I know now, a rough search turned up the same....
One last question,
I'm sticking with stock, but i want to root it, everything i've done has been unsuccessful, where before first time and it was done, I was reading the guide over here, http://forum.xda-developers.com/showthread.php?t=2273376&page=2 , and it mentions that I can't root a stock rom? that means I would need to grab one of the rooted ones then, correct? I know I've seen a link to them around here, but can't seem to find it, let alone which one I should use.
Click to expand...
Click to collapse
after running the RUU your starting from scratch
1.unlock bootloader at HTCDEV.com
2. Flash custom recovery I recommend TWRP 2.6.3.3
How to flash?
1) Download your recovery
2) Put it on your adb/fastboot folder
3) Rename it to recovery.img
4) Open a CMD/Teminal windows on adb folder
5) Put your phone in fastboot
6) Flash the recovery with the command:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
3. flash custom rom 3.17.502.3 Stock Rooted
That should do it if your Root needs updated
download and flash this same as a rom
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
i'd installed cm11 via installer but now i wanna go back to sense
i'd installed cm11 via cm installer but now i wanna go back to stock sense,sadly i couldnt find the suitable RUU for my device.Since im really new to this android system i dont have any ideas bout flashing or locking the devices,could u guys please help me out?
i'd tried turning S off with rumrunner but at the end i was struck on an error.
here are my devices details.
m7_U S on
Hboot 1.56
CID : htc__038
version : 4.20.707.7
THANKS.
Okay! SOoooo Im going to apolagize if this is the wrong sport for this! I couldnt quite find a spot that hit everything i was trying to figure out!
SO heres the deal, was looking to upgade my phone! Found an HTC one on ebay SUPER cheap guy selling it tried to root it and got it stuck in a boot cycle..... Easy enough to fix right?! *or so it would have been on a Samsung! thats what im used to working with*
so i get the phone and play a little bit, I load into the bootloader and do a factory reset! the phone restarted and went right to the main set up page! as soon as i get to the end it says Unfortunatly Set up has stopped. *UGH* still im thinking super easy to fix! Just gotta flash Stock rom! so i head in that direction everything im finding says need to S-off the phone. so i start researching! ThinI started with the boot loader, got it unlocked *thats what all the post were saying to do* then went to move on to S-off, heres where it gets messy.... long story short..... the program freaks out gives me some error then starts in to loading CWM and then everything just crashes! Phone, Computer..... everything!
I get the phone back into boot mode, NOW it sats Tampered on the top, I cant get back to the set, Recovery doent work, factory reset doent work..... again long story short after researching it turns out i wiped EVERYTHING.
I can still get to the phone VIA command promts, I can get it to load in to the black HTC screen hell i can even relock and unlock the phone..... But I think where the issue is, the phone is still S-on..... when following all the step to fix this I cant get the ADB to see that my device is connected I can- But i can acces it through other commands..... Hopefully I havent lost everyone!!
Please tell me im not completely screwed....
Post fastboot getvar all - minus your imei and serial no
Sent from my HTC One_M8 using Tapatalk
clsA said:
Post fastboot getvar all - minus your imei and serial no
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Sorry, while im not a complete noob with this stuff im still learning. what do you want me to do?
clsA said:
Post fastboot getvar all - minus your imei and serial no
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Never mind! figured it out haha
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4248mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.060s
GNote4Ever said:
Never mind! figured it out haha
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4248mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.060s
Click to expand...
Click to collapse
You can run a RUU to get you phone working
lock the bootloader
fastboot oem lock
then run this RUU to get up to android 4.3
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
if you having problems with your drivers install these
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
clsA said:
You can run a RUU to get you phone working
lock the bootloader
fastboot oem lock
then run this RUU to get up to android 4.3
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
if you having problems with your drivers install these
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
Click to expand...
Click to collapse
The RUU wont work in this case. I did as you said*just to be sure.* But the RUU can cacess the phone in boot mode and because the phone get stuck on the "HTC quietly brilliant" screen its not loaded far enough to engage the USB connection. All I get is USB Connection Error when running the RUU
clsA said:
You can run a RUU to get you phone working
lock the bootloader
fastboot oem lock
then run this RUU to get up to android 4.3
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
if you having problems with your drivers install these
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
Click to expand...
Click to collapse
think I got it. Loaded to the Black HTC screen using fastboot oem rebootRUU- then ran the RUU it is "updating boot" as we speak.
GNote4Ever said:
think I got it. Loaded to the Black HTC screen using fastboot oem rebootRUU- then ran the RUU it is "updating boot" as we speak.
Click to expand...
Click to collapse
Next time, an easier method would be to flash a custom recovery (fastboot flash recovery *recovery of your choice*) and then install a new ROM. You put the ROM on an external USB and flash it, or you can ADB push the ROM into the phone.
When running S-Off (rumrunner or firewater) I recommend to always run it from a stock ROM.
So if I get these drivers, and my computer WILL NOT recognize my device, how am I supposed to reapply them to the phone?
I just need to get the drivers back on my phone so I can work on the recovery. I'll probably have more questions about that later.. lol
I hope not to make a duplicate thread but sorry if I do.
I took on this project trying to help a friend out. This is the first VZW phone I've operated on. I've been to multiple threads on different websites and tried various procedures all to no avail.
This phone was all stock b4 the update....tried to take the update and has been in a bootloop ever since.....phone gets stuck at the white HTC quite briliant screen.
I've tried unlocking the bootloader via revone but for some reason adb will not recognize the phone....although fastboot commands are not a problem....
I'm almost at the point of installing some linux distro just so I can try moonshine..
I've tried 2 different RUU's for this phone....both fail....
HTCdev failed me also.....couldnt get the token....smh
Turning the phone back in to VZW wasnt an option because is was opened previously...warranty voided.
any help would be good help as far as I'm concerned.
I'm still trying to figure out how to find out what firmware is on the phone....and I take it "fastboot getvar all" doesnt tell you that...
On both RUU's that I have...they tell me that I have image 4.09.(xxx) <---I cant remember the last digits right now
**SOLVED** HERE'S THE THREAD THAT HELPED ME. https://forum.xda-developers.com/droid-dna/general/official-exe-ruus-s-t2935556
MUCH THANKS TO @dottat :good::good:
DuceTheTruth said:
I hope not to make a duplicate thread but sorry if I do.
I took on this project trying to help a friend out. This is the first VZW phone I've operated on. I've been to multiple threads on different websites and tried various procedures all to no avail.
This phone was all stock b4 the update....tried to take the update and has been in a bootloop ever since.....phone gets stuck at the white HTC quite briliant screen.
I've tried unlocking the bootloader via revone but for some reason adb will not recognize the phone....although fastboot commands are not a problem....
I'm almost at the point of installing some linux distro just so I can try moonshine..
I've tried 2 different RUU's for this phone....both fail....
HTCdev failed me also.....couldnt get the token....smh
Turning the phone back in to VZW wasnt an option because is was opened previously...warranty voided.
any help would be good help as far as I'm concerned.
I'm still trying to figure out how to find out what firmware is on the phone....and I take it "fastboot getvar all" doesnt tell you that...
On both RUU's that I have...they tell me that I have image 4.09.(xxx) <---I cant remember the last digits right now
Click to expand...
Click to collapse
We will need the info on the bootloader screen, all of it please. It will provide info which can be useful
.torrented said:
We will need the info on the bootloader screen, all of it please. It will provide info which can be useful
Click to expand...
Click to collapse
Thanks for replying....
***LOCKED*****
MONARUDO PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-1.01.01.1112
OpenDSP-v-10.120.274.0520
OS-4.09.605.1
eMMC-boot 2048MB
Mar 13 2014, 19:19:14.0
C:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.01.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA2BPS501936
(bootloader) imei: 990000671822338
(bootloader) meid: 99000067182233
(bootloader) product: monarudo
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL8320000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4225mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.060s
DuceTheTruth said:
Thanks for replying....
***LOCKED*****
MONARUDO PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-1.01.01.1112
OpenDSP-v-10.120.274.0520
OS-4.09.605.1
eMMC-boot 2048MB
Mar 13 2014, 19:19:14.0
C:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.01.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA2BPS501936
(bootloader) imei: 990000671822338
(bootloader) meid: 99000067182233
(bootloader) product: monarudo
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL8320000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4225mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.060s
Click to expand...
Click to collapse
I can tell you that the phone is indeed on the latest update, bootloader, baseband, and version-main all indicate that it is on the 4.09.605.1 update, have you tried to do a factory reset from within the bootloader/stock recovery?
That may help, may not. since you are locked and s-on, there really isnt much else to do.
Just for the heck of it, have you tried to flash the flashable RUU-ROM.zip from my firmware thread? Probably wont work but idk what else there is to do, being as you are still stock and locked.
.torrented said:
I can tell you that the phone is indeed on the latest update, bootloader, baseband, and version-main all indicate that it is on the 4.09.605.1 update, have you tried to do a factory reset from within the bootloader/stock recovery?
That may help, may not. since you are locked and s-on, there really isnt much else to do.
Just for the heck of it, have you tried to flash the flashable RUU-ROM.zip from my firmware thread? Probably wont work but idk what else there is to do, being as you are still stock and locked.
Click to expand...
Click to collapse
Interesting.....
I have tried the factory reset in the bootloader and it just goes to a picture of a green down arrow with two green arrows in a circle facing clockwise.... Then goes back to white HTC screen...
And I did try the flashable RUU zip.... And I will try it again..
Is it true that have to unlock the bootloader before anything else?
I'm searching for ways to do that while in this bootloop state....
And then possibly downgrading?
And if this phone really is stuck I feel that Verizon is at fault here.. . Even if it was dropped and the back came off....
My friend told me that at the time the update came through he had very little memory....
And I've read elsewhere that the exact same issue caused similar problems on some phones....
I'm surprised there's no class action on the horizon.
Htc black screen with four triangles
Man I really need help. ...I tried to flash and something went wrong to where I erased the entire os and I continued to fix this issue because all I had access to was twrp(custom rom) and bootloader. then what was crazy is that it appeared that based on the fact that I was on 4.4.2 kit kat that I was unable to fix it. after researching I found a ruu that didn't have the boot image so I flashed the factory ruu with no boot image and my htc scrren with the status bar filled all the way up but it never moved off of that screen I assume because that ruu didn't have the boot image so I thought that common sense would be to at one of the boot images that I had to the zip file of the ruu without the boot image....that's when I made things worst and now im stuck on this htc screen with the four triangles...my pc wont detect my device and im in need of some serious help....can you help? can anybody help?
I believe i can help!!!
ducethetruth said:
interesting.....
I have tried the factory reset in the bootloader and it just goes to a picture of a green down arrow with two green arrows in a circle facing clockwise.... Then goes back to white htc screen...
And i did try the flashable ruu zip.... And i will try it again..
Is it true that have to unlock the bootloader before anything else?
I'm searching for ways to do that while in this bootloop state....
And then possibly downgrading?
And if this phone really is stuck i feel that verizon is at fault here.. . Even if it was dropped and the back came off....
My friend told me that at the time the update came through he had very little memory....
And i've read elsewhere that the exact same issue caused similar problems on some phones....
I'm surprised there's no class action on the horizon.
Click to expand...
Click to collapse
whats your current status? I just got myself out of a very bad situation with my htc dna just read some of the stuff ive posted in your thread.....are you s-off or s-on?
CHRIST STARZ said:
whats your current status? I just got myself out of a very bad situation with my htc dna just read some of the stuff ive posted in your thread.....are you s-off or s-on?
Click to expand...
Click to collapse
it is s-on
I'm in the same boat. OTA update crashed and now phone wont boot. It's S-ON with the latest radio and hboot. Apparently you can't downgrade with an older RUU. I cannot seem to find a 4.09.605.5 RUU anywhere. Any suggestions?
Thanks
-CMY
cmylxgo said:
I'm in the same boat. OTA update crashed and now phone wont boot. It's S-ON with the latest radio and hboot. Apparently you can't downgrade with an older RUU. I cannot seem to find a 4.09.605.5 RUU anywhere. Any suggestions?
Thanks
-CMY
Click to expand...
Click to collapse
probably way late
https://www.androidfilehost.com/?fid=95747613655040155
carl1961 said:
probably way late
https://www.androidfilehost.com/?fid=95747613655040155
Click to expand...
Click to collapse
Yah...I was able to recover with some other files. But I have downloaded this and archived it just in case I run into problems in the future. Thanks!
-CMY
---------- Post added at 08:39 AM ---------- Previous post was at 08:36 AM ----------
Here is what I used to resolve my issues back in Nov...
http://forum.xda-developers.com/showpost.php?p=56405268&postcount=4
-CMY
carl1961 said:
probably way late
https://www.androidfilehost.com/?fid=95747613655040155
Click to expand...
Click to collapse
That's a rom BTW, and won't flash on an S-on phone. S-on requires encrypted and signed images to restore.
Hence ruu
carl1961 said:
probably way late
https://www.androidfilehost.com/?fid=95747613655040155
Click to expand...
Click to collapse
man....i just pulled this phone out the drawer and wiped the dust off lol.....
now im trying to figure out how to make this work
thanks for the post by the way
I recently found out that the only way to obtain S-Off now is to pay $25. Before I do this I'm curious to know if I even need to do that before I flash a ROM. I'm already rooted. Can't I just load the ROM onto my phone, go into recovery and flash from their? Do I really need to pay the $25?
sock00 said:
I recently found out that the only way to obtain S-Off now is to pay $25. Before I do this I'm curious to know if I even need to do that before I flash a ROM. I'm already rooted. Can't I just load the ROM onto my phone, go into recovery and flash from their? Do I really need to pay the $25?
Click to expand...
Click to collapse
You dont have to pay to obtain S-Off unless youre already on 4.4.3 in which case you'd need sunshine, just read around the forum and you can figure out how to with firewater. Its not hard you just have to do a little research. But to answer the question, yes you have to be S-Off to install custom ROMs. Here is a link to firewater http://forum.xda-developers.com/showthread.php?t=2708464
S-ON and Custom ROM's
CavyS said:
You dont have to pay to obtain S-Off unless youre already on 4.4.3 in which case you'd need sunshine, just read around the forum and you can figure out how to with firewater. Its not hard you just have to do a little research. But to answer the question, yes you have to be S-Off to install custom ROMs. Here is a link to firewater http://forum.xda-developers.com/showthread.php?t=2708464
Click to expand...
Click to collapse
I'm new to modding, and definitely still learning but am unclear on your above statement, I have HTC One (M8) 2014. Rooted SuperSu running Android Revolution HD 8.1 custom ROM. It seems I am S-ON because I am not able to flash my hboot (to remove red development text). I receive FAILED (remote: 99 unknown fail). Based on what I'm reading I am S-ON and running a custom ROM. AR HD 8.1 is based on kitkat 4.4.2. Joined today and searching for more answers. Thanks and Cheers!
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
shadowsports said:
I'm new to modding, and definitely still learning but am unclear on your above statement, I have HTC One (M8) 2014. Rooted SuperSu running Android Revolution HD 8.1 custom ROM. It seems I am S-ON because I am not able to flash my hboot (to remove red development text). I receive FAILED (remote: 99 unknown fail). Based on what I'm reading I am S-ON and running a custom ROM. AR HD 8.1 is based on kitkat 4.4.2. Joined today and searching for more answers. Thanks and Cheers!
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
Click to expand...
Click to collapse
You have to be S-Off to flash hboot. Also make sure your modid and cid match up to the hboot you are flashing.
CavyS said:
You have to be S-Off to flash hboot. Also make sure your modid and cid match up to the hboot you are flashing.
Click to expand...
Click to collapse
My mod and cid both match. My issue is indeed my S-ON status. My comment was in regards to your statement that you must be S-OFF to flash custom ROMs which does not appear to be true.
I unlocked my device using HTCdev unlock. I'm still running stock FW which is why (I believe) I am S-ON. I thought unlocking my device would provide S-OFF but that does not appear to be the case as "get var" tells the story. Thanks for the reply.
shadowsports said:
My mod and cid both match. My issue is indeed my S-ON status. My comment was in regards to your statement that you must be S-OFF to flash custom ROMs which does not appear to be true.
I unlocked my device using HTCdev unlock. I'm still running stock FW which is why (I believe) I am S-ON. I thought unlocking my device would provide S-OFF but that does not appear to be the case as "get var" tells the story. Thanks for the reply.
Click to expand...
Click to collapse
Ah, yeah I was wrong in that case. I though I read while flashing VenomOne that you had to be S-Off to use it. Now that I look at it though, its only certain ROMs you have to S-Off for since when you flash VenomOne it also flashes HBoot.
CavyS said:
Now that I look at it though, its only certain ROMs you have to S-Off for since when you flash VenomOne it also flashes HBoot.
Click to expand...
Click to collapse
You sure about that? It would be highly unusual (and actually a little scary) for any ROM to touch hboot. I don't follow ViperOne closely (Venom is the team, Viper is the ROM) so maybe I'm missing something. Can you link where you see that ViperOne does something to hboot?
---------- Post added at 10:01 AM ---------- Previous post was at 09:54 AM ----------
shadowsports said:
I unlocked my device using HTCdev unlock. I'm still running stock FW which is why (I believe) I am S-ON. I thought unlocking my device would provide S-OFF but that does not appear to be the case as "get var" tells the story.
Click to expand...
Click to collapse
Bootloader unlock has nothing to do with s-off. They are completely different things. Bootloader unlock allows install of custom recovery, flashing ROMs, kernels, root, and some other things.
S-off is needed to modify hboot, radio, and some other partitions. It means "all security off" so in many cases it also bypasses bootloader unlock, and other checks. You need to either use firewater or sunshine methods to get s-off. Most likely sunshine, as most folks have not had success with firewater; except mostly on older M8's (where fireware still worked fine). Although there have been some isolated cases of newer devices working with firewater, which is free so its worth a try (and it takes about 5 or 10 minutes to try if you are already rooted and have adb setup).
You don't need s-off to flash custom ROMs. Meaning the ROMs will still flash fine. But there is a slight caveat, in that if you are on old firmware (hboot, radio, plus other modules like WiFi, Bluetooth, media and others) from 1.xx based OS software, and try to use a 2.xx based ROM, they will not play together well and you will suffer some serious issues including long boot times (5-10 min), or broken WiFi or Bluetooth.
So while a 2.xx ROM will flash fine with s-on (in literal terms), you most likely will get some issues (maybe even making the ROM not usable) unless you update the firmware (which does require s-off).
You can update the firmware either by "unofficial" means with s-off and flashing an updated firmware. Or you with s-on, you can install the 2.23 AT&T OTA or RUU.
Hello all,
I've been browsing the forums for a few days now trying to fix my issue, but nothing I have found seems to be of much help, so I have decided to register here myself and get some assistance directly.
So, I rooted my phone and flashed twrp and cyanogenmod. After several bugs and overall irritation, I have decided to just go back to stock recovery, ROM, etc. (After all, I am a mechanical engineer - software is not my forté.)
In attempting to unroot my device, however, it seems that I just messed things up even further.
Steps taken:
1) Rebooted device into fastboot
2) fastboot oem lock
3) Reboot into RUU mode (black screen w/ htc logo)
4) Ran RUU.exe
5) (bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 35.173s
At this point, I thought that maybe it was because I was still S-ON so I was going to place rumrunner on the virtual SD. Now my PC won't recognize my phone, so I don't know how to flash rumrunner to go to S-OFF or if that's even the correct next step. So basically, I have bootloader and twrp, and that's it.
>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35ZW915640
(bootloader) imei: 354439051027912
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3658mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
Ok so I got into twrp to try and flash any ROM but data wouldn't mount.
I wiped data through twrp, which allowed me to mount data
From here I could have copied a ROM to my virtual SD and flashed through twrp, but decided to give the RUU a try again.
This time I got ERROR [155].
Checked to make sure I had the right RUU for my CID, which I do, but I'm going to try an older RUU instead.
Since RUU wasn't working, I decided just to place the CM ROM onto the virtual SD and flash it. Finally have a phone that boots up and is running CM. Better than a paper weight, but still not a stock HTC One...
MJGiuffre said:
Ok so I got into twrp to try and flash any ROM but data wouldn't mount.
I wiped data through twrp, which allowed me to mount data
From here I could have copied a ROM to my virtual SD and flashed through twrp, but decided to give the RUU a try again.
This time I got ERROR [155].
Checked to make sure I had the right RUU for my CID, which I do, but I'm going to try an older RUU instead.
Click to expand...
Click to collapse
wrong way
MJGiuffre said:
Since RUU wasn't working, I decided just to place the CM ROM onto the virtual SD and flash it. Finally have a phone that boots up and is running CM. Better than a paper weight, but still not a stock HTC One...
Click to expand...
Click to collapse
there is no ruu for your sofware, older one will not work its just how htc are made, try this ruu its the latest.( make sure you are not supercid before running it, it can mess up the phone) from your first post it looks like you are fine unless u changed it to supercid.
http://dl3.htc.com/application/RUU_...06_10.46.1718.01L_release_424933_signed_2.exe
it should work at least it worked on mine
---------- Post added at 03:07 PM ---------- Previous post was at 03:00 PM ----------
MJGiuffre said:
Since RUU wasn't working, I decided just to place the CM ROM onto the virtual SD and flash it. Finally have a phone that boots up and is running CM. Better than a paper weight, but still not a stock HTC One...
Click to expand...
Click to collapse
also u can try one of the guru resets that matches your software , or look for a stock unrooted nandroid for att htc one , u need the 5,12 sofware , older one may not work properly. also before runing a ruu make sure your bootloader is loked or relocked. good luck.