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
Related
Hi,
I am sorry if this has been answered but I have no idea what to even search on. Been looking for different terms with no luck.
I have been on Optimus G Pro for a while and forgot how to modify a phone.
Anyways, I exchanged it with this guy who said it's DE HTC One.
What's weird is that when I reboot, I get AT&T animation and logo. I get AT&T Icons and it's AT&T Rom from what I can tell with 4.1.2.
He was a 47 year old man and never messed with anything and paid $600 for this phone.
This is what I see on my HBOOT screen:
HBOOT Screen Info
*** LOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.44.0000
RADIO-4A.17.3250.20
OpenDSP-v31.120.274.0617
eMMC-boot
Jul 5 2013, 16:04L18-1
Does anyone know if it's really a DE phone and he just ran AT&T RUU on it or something? If he did the S-OFF, shouldn't it say UNLOCKED?
I'm trying to root and all to install 4.3 but don't want to end up bricking since it's a weird S-OFF locked phone and I haven't been on HTC One forum in a while so not really sure what's going on.
Thanks in advance and sorry for the long post.
TL;DR: I just got HTC One which user claims is DE and I don't know if it is..just want to get 4.3 on it
noobsquared said:
Hi,
I am sorry if this has been answered but I have no idea what to even search on. Been looking for different terms with no luck.
I have been on Optimus G Pro for a while and forgot how to modify a phone.
Anyways, I exchanged it with this guy who said it's DE HTC One.
What's weird is that when I reboot, I get AT&T animation and logo. I get AT&T Icons and it's AT&T Rom from what I can tell with 4.1.2.
He was a 47 year old man and never messed with anything and paid $600 for this phone.
This is what I see on my HBOOT screen:
HBOOT Screen Info
*** LOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.44.0000
RADIO-4A.17.3250.20
OpenDSP-v31.120.274.0617
eMMC-boot
Jul 5 2013, 16:04L18-1
Does anyone know if it's really a DE phone and he just ran AT&T RUU on it or something? If he did the S-OFF, shouldn't it say UNLOCKED?
I'm trying to root and all to install 4.3 but don't want to end up bricking since it's a weird S-OFF locked phone and I haven't been on HTC One forum in a while so not really sure what's going on.
Thanks in advance and sorry for the long post.
TL;DR: I just got HTC One which user claims is DE and I don't know if it is..just want to get 4.3 on it
Click to expand...
Click to collapse
Looking at this the CID of eight 1's means he changed it to a supercid. Also S-OFF can be achieved by using REVONE/MOONSHINE without messing with the LOCKED/TAMPERED/UNLOCKED messages so you can always turn S-ON and you would never know. If you are in fastboot can you run "fastboot getvar all" and see what MID you have. Also check what version of the software you are running. I don't own a developer edition so I am not sure if it would have the AT&T boot and logo.
Look at the back, does it have an AT&T globe logo?
Either way, with s-off you can flash DE ruu, or anything you want.
Thanks guys.
Here is what I get when I do fastboot getvar all:
X:\Downloads\htcone>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-OFF
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: xxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3851mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.085s
It does have the AT&T logo in the back as well.
I guess he lied to me but either way I think I got a good deal considering that OGPro is selling for much lower price than HTC One.
I guess I just didn't know that you could change CID and do the S-Off and still say locked on HBOOT screen. I've always had TEMPERED or UNLOCKED on my HTC phones so its just hard to remember.
I guess I will unlock it using htc site and install CWM...CleanROM 4.3..here I come
Thanks a bunch once again guys.
I was simply able to flash the ruu.zip file using the following commands on my Mac:
./fastboot oem rebootRUU
./fastboot flash zip rom.zip
./fastboot reboot
Thanks everyone for your help. It seems like the update worked just fine.
I got the error: RUU: "FAILED (remote: 90 hboot pre-update! please flush image again immediately)" the first time I ran it, I just re-ran the command and it worked like a charm and it seems like I am on 4.3 now.
Thanks a bunch everyone
Yes, just flash RUU twice in a row to get hboot to take.
DE and AT&T versions are exact same hardware, so no real loss. If you need sim unlock that's $3.50 on eBay.
Might want to remove serialno and IMEI from previous post...
Hello all, I've been using these forums for information frequently, but this is the first time I've run into trouble. I updated my AT&T HTC One to the GPE, but decided I wanted to go back to stock with the impending HTC Sense 5.5 update around the corner. I had gotten GPE via rumrunner and the methods at htc-one.wonderhowto.com (I can't post the direct link).
I had then reverted back to a rooted stock ROM, but it would not perform OTA updates. So, my next step was to get S-ON and re-lock the device. I accomplished those, but somehow I now have no OS - I can get into recovery (stock), but cannot perform anything from there. Factory resets and wipes do nothing for me. I have access to fastboot, and have attempted running various RUUs but all of them give me error code 155, which appears to be due to the wrong version. However, I have tried all of the AT&T US RUUs I can find, so I'm sort of at a loss there.
I thought maybe I could get unlocked again so that I could load TWRP again, but running the HTCDev unlocktoken command does nothing, other than tell me it was successful - it stays on the fastboot screen instead of showing the option to choose Yes/No to unlock.
So, after hours of attempts, I'm sort of stuck. Could anyone help point me in the right direction? By the way, my device reads TAMPERED and RELOCKED in the bootloader, and S-ON. Below is the output of my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(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: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
Please remove serial number and imei from the report.
Sent from my HTC One using xda app-developers app
TopoX84 said:
Please remove serial number and imei from the report.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I did just as you posted this, thanks!
codejunkie83 said:
Hello all, I've been using these forums for information frequently, but this is the first time I've run into trouble. I updated my AT&T HTC One to the GPE, but decided I wanted to go back to stock with the impending HTC Sense 5.5 update around the corner. I had gotten GPE via rumrunner and the methods at htc-one.wonderhowto.com (I can't post the direct link).
I had then reverted back to a rooted stock ROM, but it would not perform OTA updates. So, my next step was to get S-ON and re-lock the device. I accomplished those, but somehow I now have no OS - I can get into recovery (stock), but cannot perform anything from there. Factory resets and wipes do nothing for me. I have access to fastboot, and have attempted running various RUUs but all of them give me error code 155, which appears to be due to the wrong version. However, I have tried all of the AT&T US RUUs I can find, so I'm sort of at a loss there.
I thought maybe I could get unlocked again so that I could load TWRP again, but running the HTCDev unlocktoken command does nothing, other than tell me it was successful - it stays on the fastboot screen instead of showing the option to choose Yes/No to unlock.
So, after hours of attempts, I'm sort of stuck. Could anyone help point me in the right direction? By the way, my device reads TAMPERED and RELOCKED in the bootloader, and S-ON. Below is the output of my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(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: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
Click to expand...
Click to collapse
Did you try ruu ?
RUU M7 UL JB 50 Cingular US 1.26.502.15 Radio 4A.17.3250.20 10.40.1150.04 Release 326691 Signed 2
http://www.htc1guru.com/dld/ruu_m7_...13_10-33-1150-01_release_318450_signed_2-exe/
or you could try this which is supposed to be the latest version that at&t has gotten out
http://androidromupdate.com/2013/10/09/att-htc-one-official-4-3-ota-update-stock-ruu-3175023/
Sent from my HTC One using xda app-developers app
TopoX84 said:
Did you try ruu ?
RUU M7 UL JB 50 Cingular US 1.26.502.15 Radio 4A.17.3250.20 10.40.1150.04 Release 326691 Signed 2
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yes, I tried all of the Cingular ones on that page, to no avail. They all fail with the 155 error code.
EDIT: I also tried that latest AT&T version from androidromupdate, but it failed the same
codejunkie83 said:
Yes, I tried all of the Cingular ones on that page, to no avail. They all fail with the 155 error code.
Click to expand...
Click to collapse
http://androidforums.com/incredible...or-155-using-htc-rom-utility.html#post4767526
http://forum.xda-developers.com/showthread.php?t=2257921
Okay, seems like I've followed all of those steps. I ran fastboot oem lock, but each time I try the RUU I get the 155 message. I had just installed the latest HTC drivers last week, as that was when I went to the GPE. I'm using the same USB port that I had been using then, so no differences there.
Thank you for your responses - if you need any more information I'll be glad to give it.
TopoX84 said:
http://androidforums.com/incredible...or-155-using-htc-rom-utility.html#post4767526
http://forum.xda-developers.com/showthread.php?t=2257921
Click to expand...
Click to collapse
Okay, so one thing that I have noticed - my main versions seems to be X.XX.1540.X, which as best I can tell is the US Dev Edition. However, my CID is CWS_001, which should have X.XX.502.X as the main version. Unfortunately, I think the conflict here is causing my RUUs to fail. Any suggestions?
So, after a long night and morning of fighting with this, I've concluded that I'm completely hosed. Here is how I stand at this time:
My CID is correct, CWS__001, which matches my carrier (AT&T)
My OS version, however, is 4.06.1540.2. This marks it as being a developer edition.
There does not exist an RUU for the OS I have currently. Also, if one did exist, I'm not certain that it would work, as that would require my CID to be different (not sure on that last bit)
All AT&T RUUs fail - this is due to low main version.
I do not have access to Android at all, only bootloader and fastboot.
I am S-ON
I am RELOCKED/TAMPERED
Because of these, I cannot flash a custom recovery to be able to load a new system of ANY version.
Because I can only access bootloader, I cannot achieve S-OFF.
And the final nail, HTC Dev unlock feature does not work. It says it is successful, but the splash screen is never displayed, and I receive the message that the splash screen could not load on my next fastboot command (no matter what command it is)
So, from this criteria, I think I'm stuck with an expensive piece of dead technology. I'm posting all of this information in hopes that someone else may get stuck in the same manner and have a miracle cure.
codejunkie83 said:
So, after a long night and morning of fighting with this, I've concluded that I'm completely hosed. Here is how I stand at this time:
My CID is correct, CWS__001, which matches my carrier (AT&T)
My OS version, however, is 4.06.1540.2. This marks it as being a developer edition.
There does not exist an RUU for the OS I have currently. Also, if one did exist, I'm not certain that it would work, as that would require my CID to be different (not sure on that last bit)
All AT&T RUUs fail - this is due to low main version.
I do not have access to Android at all, only bootloader and fastboot.
I am S-ON
I am RELOCKED/TAMPERED
Because of these, I cannot flash a custom recovery to be able to load a new system of ANY version.
Because I can only access bootloader, I cannot achieve S-OFF.
And the final nail, HTC Dev unlock feature does not work. It says it is successful, but the splash screen is never displayed, and I receive the message that the splash screen could not load on my next fastboot command (no matter what command it is)
So, from this criteria, I think I'm stuck with an expensive piece of dead technology. I'm posting all of this information in hopes that someone else may get stuck in the same manner and have a miracle cure.
Click to expand...
Click to collapse
Have you worked through this article??
http://forum.xda-developers.com/showthread.php?t=2358738
mb_guy said:
Have you worked through this article??
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
I've tried - how would I go about restoring the stock rom/recovery? Just flash the individual images from that zip? Also, would I need to do the X.XX.502.X version (my carrier), or the X.XX.1540.X version (the currently loaded firmware)?
EDIT: No dice. I tried both, but continue to receive the message that the signature verify is failing.
codejunkie83 said:
I've tried - how would I go about restoring the stock rom/recovery? Just flash the individual images from that zip? Also, would I need to do the X.XX.502.X version (my carrier), or the X.XX.1540.X version (the currently loaded firmware)?
EDIT: No dice. I tried both, but continue to receive the message that the signature verify is failing.
Click to expand...
Click to collapse
I think your issue may be that you went back to S-on before going to stock and now firmware is wrong. I would follow the article to regain s-off then you can likely move ahead. There are also several articles saying going to s-on after being s-off can cause issues.
mb_guy said:
I think your issue may be that you went back to S-on before going to stock and now firmware is wrong. I would follow the article to regain s-off then you can likely move ahead. There are also several articles saying going to s-on after being s-off can cause issues.
Click to expand...
Click to collapse
The problem is that I cannot access my phone's storage to push revone, or to use rumrunner. I cannot unlock the device because unlocktoken does not work - it applies the token, but nothing happens.
I wonder - can I flash the splash screen that it is missing? I think it's due to me missing the piece where it asks me to confirm I want to unlock the phone.
codejunkie83 said:
The problem is that I cannot access my phone's storage to push revone, or to use rumrunner. I cannot unlock the device because unlocktoken does not work - it applies the token, but nothing happens.
I wonder - can I flash the splash screen that it is missing? I think it's due to me missing the piece where it asks me to confirm I want to unlock the phone.
Click to expand...
Click to collapse
I would try posting here in the main htc one forum
http://forum.xda-developers.com/htc-one/help
Lots of smart guys hang out there.
BTW: have you tried "fastboot oem unlock" again
mb_guy said:
I would try posting here in the main htc one forum
http://forum.xda-developers.com/htc-one/help
Lots of smart guys hang out there.
Click to expand...
Click to collapse
Thanks, will do!
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
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *removed*
(bootloader) imei: *removed*
(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: FASTBOOT
(bootloader) commitno-bootloader: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.058s
I am stuck, I can't see to get my phone to boot. You would think that I would be able to do something to fix this if I can get into recovery and bootload, but I can't get a proper system boot. I am hoping that buying a new phone isn't my only option at this point. If anyone can help me I am willing to pay if you can help me get a working phone again.
@Jameskhunter
You should edit your IMEI number out of your getvar
What exactly happened when you flashed the firmware ,any specific message that came across that you can remember
According to the getvar it looks like you flashed the GPE lollipop firmware/ruu without
S-OFF.
---------- Post added at 03:47 AM ---------- Previous post was at 03:37 AM ----------
Try this .exe of the stock ruu sense your At&t
http://forum.xda-developers.com/showthread.php?t=2860423
GPE firmware
jball said:
@Jameskhunter
You should edit your IMEI number out of your getvar
What exactly happened when you flashed the firmware ,any specific message that came across that you can remember
According to the getvar it looks like you flashed the GPE lollipop firmware/ruu without
S-OFF.
---------- Post added at 03:47 AM ---------- Previous post was at 03:37 AM ----------
Try this .exe of the stock ruu sense your At&t
http://forum.xda-developers.com/showthread.php?t=2860423
Click to expand...
Click to collapse
That is what I have been told although I didn't realize that it was GPE and I don't really understand why it let me get my phone in an usable/unrecoverable state if I had s-on. I thought that was a safety net, but the more I read I wish it was s-off. I think it would be fixable then, but in the current state I don't know how to get s-off. I did the firmware command twice and it seemed to work after the second attempt as the article noted that it would. I have never flashed a rom, before so other than reading the article and attempting to follow along didn't really know what to expect. The article had me do a fastboot oem lock and then a fastboot oem ruu as I recall. then it was something like fastboot flash zip .....zip. The problem is the roms that I have attempted to install now don't seem to install maybe if I could find the right one it would install and work good enough to allow me to become s-off and get back to more of a working state. I should of done a lot more reading before attempting this... I made some invalid assumptions about being able to recover which is my fault. I would think something is possible in this state.
I think part of the problem is that I am s-on and my main ver is higher than the RUU for my carrier version and my cid. I think I could edit those if I was s-off or do something, but I can't do that since I am s-on.
Hi
Jameskhunter said:
That is what I have been told although I didn't realize that it was GPE and I don't really understand why it let me get my phone in an usable/unrecoverable state if I had s-on. I thought that was a safety net, but the more I read I wish it was s-off. I think it would be fixable then, but in the current state I don't know how to get s-off. I did the firmware command twice and it seemed to work after the second attempt as the article noted that it would. I have never flashed a rom, before so other than reading the article and attempting to follow along didn't really know what to expect. The article had me do a fastboot oem lock and then a fastboot oem ruu as I recall. then it was something like fastboot flash zip .....zip. The problem is the roms that I have attempted to install now don't seem to install maybe if I could find the right one it would install and work good enough to allow me to become s-off and get back to more of a working state. I should of done a lot more reading before attempting this... I made some invalid assumptions about being able to recover which is my fault. I would think something is possible in this state.
I think part of the problem is that I am s-on and my main ver is higher than the RUU for my carrier version and my cid. I think I could edit those if I was s-off or do something, but I can't do that since I am s-on.
Click to expand...
Click to collapse
I have tried that RUU and it fails, I think because its main version number is lower than mine now... Which I also didn't realize was a limitation. I think the lesson here is to never flash firmware that isn't directly from the htc site although its suppose to be signed, that's a little confusing to me.
I to thought S-ON was supposed to be a safety net
What Roms have you tried sense then
If you hold power+up your phone hard restarts. then quickly hold power+down. then go to recovery. If have TWRP and this way you accessed it. you got some chance. go to https://download.cyanogenmod.org/?device=m8 and download latest nightly and see if you can flash it. That worked for me. Until I find a signed firmware/radio that is version 4.+ I am stuck with cm12.
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