Related
LOOKS LIKE S-OFF FOR 1.54 HAS HAPPENED. NO NEED TO DOWNGRADE CHECK THE POST HERE
MODS Lock This One Up!!!
I was about to give up on s-off since I got the OTA update but there is hope.
I got s-off doing the following:
1.) Unlock your device via HTCDev
2.) Download and flash CWM Recovery
3.) Flash the stock nandroid for your phone...
a. TWRP Nandroid AT&T Thanks JEANRIVERA
b. TWRP Nandroid AT&T Thanks JEANRIVERA
c. TWRP Nandroid AT&T Thanks cschmittIf any one has other links to other devices let me know... I think this will work on all of the variants.:laugh:
Please note that this nandroid was made with TWRP and may need to be restored with TWRP.
On a side note... The original nandroid that I had linked was also created with TWRP and as I was unable to locate the restore function in my TWRP I did restore with CWM.
4.) then relock your device
Code:
fastboot oem lock
5.) grab 1847-ruu-m7-ul-jb-50-cingular-12650212.exe here and run it... Thanks cschmitt
6.) goto the tutorial here... and follow the directions...
This has worked for me... and I hope this will help someone else. All the information came from other people, I just happened to put it in the right order.
If this did not work for you there are New instructions here... Thanks domohan
IT IS IMPORTANT TO DO ALL THE STEPS IN ORDER...
I take no responsibility for anything you do with this information.
If I forgot to mention your name specifically... I'm Sorry and Thanks!
If I helped you hit the thank you button.
I see, new hboot. Downgrading it is then. Interesting that they haven't forced htc to shut off the unlocking service.
worked as advertised
Thanks a lot. A process for sure but worked for me following the ATT OTA update to .15. Although, I went on to follow the guide at wonderhowto dot com for installing the ASOP Google Edition. Thanks again.
Yeah that was the update that got me ... I am really glad that it worked for someone else... :laugh:
I am having trouble flashing the nandroid. I have tried to both flash the zip as well as unpack it and try to do a restore. Any thoughts?
---------- Post added at 06:33 PM ---------- Previous post was at 05:38 PM ----------
Ok, I actually flashed this one http://forum.xda-developers.com/showthread.php?t=2252959
Then ran the .12 RUU and am now S-OFF. Thanks for this!
well i am glad you got that working... The way i did the nandroid was by extracting the zip to clockworkmod\backups ... then choosing restore... I had TWRP but could not find the restore Nandroid option.
The only way I see this actually working is that the RUU just checks the HBOOT version, and not the build date. Otherwise, the .12 RUU would fail to install because the OTA HBOOT has a newer build date.
If this is true, then all AT&T users better get S-OFF now (if they know what S-OFF does). I have a feeling the 4.2.2 update will come out with a newer HBOOT with a higher number. Then surely, any 4.1.2 RUU will not work.
In any case, it seems to be working for those of us who weren't paying attention and downloaded the OTA... But the message is still S-OFF now while you can, 'cause they will patch the thing eventually.
I was getting Error = -6 codes and this method worked perfectly for me! Thanks so much!
This did not work for my situation...
I had S-OFF, set my CID to 11111111 and installed the latest GE rom. I decided to go back to stock, and made the mistake of S locking without knowing that I could not go back on HBOOT 1.54. Now I'm S-ON with CID 11111111, HBOOT 1.54 and Radio 4A.18
I tried this fix... I get stuck on the RUU, it show sending... but after about 5min it errors out...
Is there any hope for my situation?
This was what in my RUU log...
<T171817><DEBUG><OUT>sending 'zip'... (1029872 KB) FAILED (data transfer failure (Too many links))</OUT>
i used this and it worked flawlessly for me, great looking out man. im now s-off with tampered removed
TabascoJoe said:
This did not work for my situation...
I had S-OFF, set my CID to 11111111 and installed the latest GE rom. I decided to go back to stock, and made the mistake of S locking without knowing that I could not go back on HBOOT 1.54. Now I'm S-ON with CID 11111111, HBOOT 1.54 and Radio 4A.18
I tried this fix... I get stuck on the RUU, it show sending... but after about 5min it errors out...
Is there any hope for my situation?
This was what in my RUU log...
<T171817><DEBUG><OUT>sending 'zip'... (1029872 KB) FAILED (data transfer failure (Too many links))</OUT>
Click to expand...
Click to collapse
I'm not totally sure...
1.) do you have unlock from htcdev?
2.) can you flash a recovery?
a. if so there is hope to get back to at least a working phone till a new exploit for 1.54 is found.
b. Are you sure you re-locked your phone...
Code:
fastboot oem lock
c. SUPER CID - (allows you to flash ANY ROM to the device regardless of the carrier. Just click RUU.EXE) So make sure the phone is locked and flash an older RUU. Then revone and you should be good to go my friend.
let me know if this works!
...and remember to hit the thank you button!
INeFFeCTiVE said:
I'm not totally sure...
1.) do you have unlock from htcdev?
2.) can you flash a recovery?
a. if so there is hope to get back to at least a working phone till a new exploit for 1.54 is found.
b. Are you sure you re-locked your phone...
Code:
fastboot oem lock
c. SUPER CID - (allows you to flash ANY ROM to the device regardless of the carrier. Just click RUU.EXE) So make sure the phone is locked and flash an older RUU. Then revone and you should be good to go my friend.
let me know if this works!
...and remember to hit the thank you button!
Click to expand...
Click to collapse
I have a working phone. I have an unlock from htcdev. i have locked it, i can flash roms and recovery in twrp.
Its when I try an RUU it get suck on sending.... and errors out
Could it be my Main Version? I used misc tool to try to get back to 1.26.502.10, but can never get it to write the last digit correctly. Here is my getvar output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.010
(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: 3999mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I guess I was wrong on being SuperCID. Using the misctool what should I change my main version to, and how?
Thanks
Here are the steps I did to unlock bootloader, root and acquire s-off:
I went back to fully stock unrooted s-on to get the OTA just to b on the safe side. This is where I knew the update screwed up the current s-off method so I unlocked the bootloader using HTCDev. Then proceed to root and pushed the revone file to the appropriate folder location. I followed all the commands from revone up to where u Chmod 755 revone. After that since I already had root, I simply type su then proceeded with the s-off and unlock command. Removed tampered label and voila!!! Back in business with latest software.
Sent from my HTC One using xda premium
---------- Post added at 07:50 PM ---------- Previous post was at 07:48 PM ----------
I think what happened was the new update screwed up the motochopper temp root exploit and that's y I think u can't s-off with the updated software. But there is always a way...
Sent from my HTC One using xda premium
TabascoJoe said:
I have a working phone. I have an unlock from htcdev. i have locked it, i can flash roms and recovery in twrp.
Its when I try an RUU it get suck on sending.... and errors out
Could it be my Main Version? I used misc tool to try to get back to 1.26.502.10, but can never get it to write the last digit correctly. Here is my getvar output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.010
(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: 3999mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I guess I was wrong on being SuperCID. Using the misctool what should I change my main version to, and how?
Thanks
Click to expand...
Click to collapse
You can't use the AT&T RUU because your HBOOT is higher than the one in the RUU. S-ON is preventing any older HBOOT to be flashed.
Hi guys, will this work on T-Mobile HTC ONE? I updated not knowing they blocked from s-off.
Thanx,
Vinny
It would certainly be worth a try. The hardware is the same, so I don't see why not... as long as your boot loader is 1.44.00000 (not sure on the amount of zero's) this should work.
I'm pretty sure there are nandroid images for TMO out there so give it a try.
vinny.1967 said:
Hi guys, will this work on T-Mobile HTC ONE? I updated not knowing they blocked from s-off.
Thanx,
Vinny
Click to expand...
Click to collapse
let me know if it's work with you
me_rashad said:
let me know if it's work with you
Click to expand...
Click to collapse
Hey me_rashad, it's a no go. I also flash tmobile nand still no go. from what i research on difference forum is because tmobile update did a patch to the 1.44 HBoot so i guess we have to wait till revone or monshine dev find the way.
vinny.1967 said:
Hey me_rashad, it's a no go. I also flash tmobile nand still no go. from what i research on difference forum is because tmobile update did a patch to the 1.44 HBoot so i guess we have to wait till revone or monshine dev find the way.
Click to expand...
Click to collapse
I did get the OTA too and having the same pesky error -6. The bootloader version still says 1.44.0000, how do we know if its patched or not? Shouldn't the version number increase? What is your version?
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!
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 had someone inexperienced bring me this phone which they botched. They were able to use htcdev and unlock the bootloader and install TWRP, but that is all. No s-off. They must have wiped it because there is no OS on it and they want it back to stock now. So, I figured I would relock the bootloader and flash the most current ota. Nope. It isn't having it. I tried the 3.28 ota but after the check in hboot, it reads "checking" with "press power to reboot" over the top of the text. I have tried other ruu's and zips only to get checksum errors or signature verification errors. I forgot to mention that when twrp was installed, not a single custom rom would intall. They all failed. The person that brought it to me did mention something about trying to get to the google play edition firmware but they didn't know much about it. Does anyone have any ideas on where I can go from here? Anything would be very helpful. Thank you!
adb getvar all, and tell us hboot number, radio, verify it is s-on, and also what is CID?
What RUUs did you try?
Which 3.28 OTA did you try? One hasn't been released by AT&T yet.
redpoint73 said:
adb getvar all, and tell us hboot number, radio, verify it is s-on, and also what is CID?
What RUUs did you try?
Which 3.28 OTA did you try? One hasn't been released by AT&T yet.
Click to expand...
Click to collapse
C:\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.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: FA45FWM10802
(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: FASTBOOT
(bootloader) commitno-bootloader: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.065s
I have tried all the att ruu's and the unbranded 3.28. In twrp I tried sense and non sense roms, all of which failed.
Delete your IMEI from the post, as this is private info.
Sorry, I should have mentioned to delete the IMEI. Although I did not request to cut and paste all the getvar data.
EDIT: Reported to mods, and they deleted the IMEI.
---------- Post added at 03:35 PM ---------- Previous post was at 03:30 PM ----------
In bootloader, you've verified the bootloader is relocked?
Also, you tried the 2.23 RUU? I know you said you tried "all" the RUUs (it helps to be specific and list everything individually). But I ask because this RUU was released, but now its not listed on HTC's support site (as the OTA was pulled due to battery drain issues) so some people think the RUU itself was also "pulled". Although the direct RUU download still exists and works:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Also, you can try the bootable RUU, which some folks have had better luck with: http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
Or another approach: What version of TWRP? Some older versions were known to have some flashing issues for some folks. Any specific error messages?
With bootloader unlocked, try to fastboot erase cache, and fastboot flash the latest TWRP. Or try Philz recovery. Then try again to flash a ROM.
whoops, I forgot about the imei. Thanks. Yes, I tried 2.23 and it read no image or wrong image. I will unlock the bootloader again and install the most current twrp and give it a try. anything helps. thanks!
iRootAll said:
I tried 2.23 and it read no image or wrong image.
Click to expand...
Click to collapse
Did you try the bootable version I linked?
Have you tried installing the latest TWRP, wipe the phone and flash a nandroid backup?
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.