Hello everyone,
I have a SIM unlocked AT&T HTC One (M7) that I am using on T-Mobile.
I am not rooted (I do not wish to be rooted at this time), and I have managed to get up to version 4.3 by use of the HTC RUU, but when I try to get to android version 4.4, the RUU shows error 155. How would I fix this?
Help Please
-TR3Y
TR3Y said:
Hello everyone,
I have an unlocked AT&T HTC One (M7) that I am using on T-Mobile.
I am not rooted (I do not wish to be rooted at this time), and I have managed to get up to version 4.3 by use of the HTC RUU, but when I try to get to android version 4.4, the RUU shows error 155. How would I fix this?
Help Please
-TR3Y
Click to expand...
Click to collapse
try this one
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
clsA said:
try this one
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
Click to expand...
Click to collapse
Thank you for replying. I have tried that one already, as well as the one from HTC1Guru. Both of them read the build number as 4.20.502.1 instead of 4.18.502.7 . I believe the error keeps happening because the build number does not match and pretty much my laptop won't allow it to upgrade as long as the build numbers don't match. I will try it again though.
Thanks,
-TR3Y
P.S. has this happened with anyone else?
Update: I have re-tried the update now. At 5% and checking header. I will give it over night to update.
clsA said:
try this one
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
Click to expand...
Click to collapse
clsA, is this an official RUU from HTC? Every time I try do it, it hangs at 5% (checking header...). I just want to make sure there is no virus/malware here. and androidruu.com is blocked at the location I am at. It says that there was malware found on AndroidRUU. Can you confirm any of this?
-Malware on AndroidRUU and
-official RUU from HTC
-TR3Y
Well I'm going to say the files work for smorgasbord and not others
Malware no I've never seen any infections RUU
Sent from my HTC One_M8 using Tapatalk
clsA said:
Well I'm going to say the files work for smorgasbord and not others
Malware no I've never seen any infections RUU
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
So, are the RUU files are official from HTC? Also HTC1GURU was not blocked at the location I was at. I got the RUU from there. I am guessing both of the RUU files from both websites are the same?
Yeah their the same file
And no their not on the HTC site
I'm not really sure where they originated from
Sent from my HTC One_M8 using Tapatalk
clsA said:
Yeah their the same file
And no their not on the HTC site
I'm not really sure where they originated from
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Oh ok... Well, now I have a new error when I try from a last resort computer. When I try and run the RUU an error box comes up that says "htc_fastboot.exe has stopped" and then everything crashes. This is an error I have not had anywhere else. Any suggestions?
clsA said:
Yeah their the same file
And no their not on the HTC site
I'm not really sure where they originated from
Click to expand...
Click to collapse
I'm pretty sure the 4.18.502.7 RUU on androidRUU was leaked from some member of the HTC elevate program, that's why it changes the build version to 4.20.502.1, so that it's clear its not the GA release (and possibly to prevent downgrading once its installed.) Also, several reports of that RUU failing to install, possibly it has different signature-- I don't really know.
cschmitt said:
I'm pretty sure the 4.18.502.7 RUU on androidRUU was leaked from some member of the HTC elevate program, that's why it changes the build version to 4.20.502.1, so that it's clear it not the GA release (and possibly to prevent user's from downgrading once they've installed it.) Also, several reports of that RUU failing to install, possibly it has different signature-- I don't really know.
Click to expand...
Click to collapse
Are you recommending that people not install that RUU and just wait for HTC to release it?
TR3Y said:
Are you recommending that people not install that RUU and just wait for HTC to release it?
Click to expand...
Click to collapse
Just sharing my observations. If you're trying to stay 100% stock and are currently on 3.17.502.3 then download the 4.18.502.7 OTA and flash it in stock recovery.
@clsA posted it here.
cschmitt said:
I'm pretty sure the 4.18.502.7 RUU on androidRUU was leaked from some member of the HTC elevate program, that's why it changes the build version to 4.20.502.1, so that it's clear it not the GA release (and possibly to prevent downgrading once its installed.) Also, several reports of that RUU failing to install, possibly it has different signature-- I don't really know.
Click to expand...
Click to collapse
Thanks for the info ... I know I downloaded the RUU when it first come out and had @nkk71 decrypt the rom zip for me ... he mentioned that it had errors during the decrypting but nothing specific, just that he fixed it. Flashing the rom.zip alone fails on all attempts. I was s-off when i flashed the RUU.exe so i don't really know if it's a signature problem or not. The Decrypted version i uploaded worked fine on my 2nd One (s-off of coarse). But I have had reports of it not flashing also ...so I'm really not sure what to think.
cschmitt said:
Just sharing my observations. If you're trying to stay 100% stock and are currently on 3.17.502.3 then download the 4.18.502.7 OTA and flash it in stock recovery.
@clsA posted it here.
Click to expand...
Click to collapse
I have tried going into the current recovery already. The OTA is on the root of internal storage. I went into the recovery and went install from phone storage, and it had an error and just restarted my One. If you have a few minutes. I will do it again and say what the error was.
clsA said:
Thanks for the info ... I know I downloaded the RUU when it first come out and had @nkk71 decrypt the rom zip for me ... he mentioned that it had errors during the decrypting but nothing specific, just that he fixed it. Flashing the rom.zip alone fails on all attempts. I was s-off when i flashed the RUU.exe so i don't really know if it's a signature problem or not. The Decrypted version i uploaded worked fine on my 2nd One (s-off of coarse). But I have had reports of it not flashing also ...so I'm really not sure what to think.
Click to expand...
Click to collapse
I've decrypted the RUUs as well and the format has changed in KK RUUs (due to the size) so now the encrypted rom.zip contains 5 zip files: firmware.zip, system1.zip, system2.zip, system3.zip, and userdata.zip. That's why we see messages like "checking 1/5" when it's flashing, it's verifying each of the 5 zips.
I haven't attempted to flash that RUU (or any RUU for that matter), been on CM builds for the last year.
---------- Post added at 03:05 PM ---------- Previous post was at 03:03 PM ----------
TR3Y said:
I have tried going into the current recovery already. The OTA is on the root of internal storage. I went into the recovery and went install from phone storage, and it had an error and just restarted my One. If you have a few minutes. I will do it again and say what the error was.
Click to expand...
Click to collapse
Give it a try, let's see what happens. There's also a means to flash the OTA in TWRP that worked for at least a couple of people: here
cschmitt said:
I've decrypted the RUUs as well and the format has changed in KK RUUs (due to the size) so now the encrypted rom.zip contains 5 zip files: firmware.zip, system1.zip, system2.zip, system3.zip, and userdata.zip. That's why we see messages like "checking 1/5" when it's flashing, it's verifying each of the 5 zips.
I haven't attempted to flash that RUU (or any RUU for that matter), been on CM builds for the last year.
Click to expand...
Click to collapse
@clsA ... @cschmitt ...
can either of you tell me how to fix this error? http://ow.ly/w0iCY
TR3Y said:
@clsA ... @cschmitt ...
can either of you tell me how to fix this error? http://ow.ly/w0iCY
Click to expand...
Click to collapse
it says check cid failed .. have you changed your cid to something else ?
change it back
fastboot oem writecid CWS__001
TR3Y said:
can either of you tell me how to fix this error?
Click to expand...
Click to collapse
Other's have reported that, it's seems to be an issue with the update script checking the CID.
Does your fastboot screen show CID CWS__001 and OS 3.17.502.3 ?
clsA said:
it says check cid failed .. have you changed your cid to something else ?
change it back
fastboot oem writecid CWS__001
Click to expand...
Click to collapse
I don't remember changing the CID, unless unlocking it did that. That won't wipe my phone if I do that, right?
cschmitt said:
Other's have reported that, it's seems to be an issue with the update script checking the CID.
Does your fastboot screen show CID CWS__001 and OS 3.17.502.3 ?
Click to expand...
Click to collapse
it doesn't appear to.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
cschmitt said:
Other's have reported that, it's seems to be an issue with the update script checking the CID.
Does your fastboot screen show CID CWS__001 and OS 3.17.502.3 ?
Click to expand...
Click to collapse
TR3Y said:
I don't remember changing the CID, unless unlocking it did that. That won't wipe my phone if I do that, right?
Click to expand...
Click to collapse
sorry for the confusion, you seem to be in really good hands try the fix @cschmitt posted above
Related
I have done a foolish work hence my phone not running beyond the boot screen htc logo. rebooting there itself.
As i was unable to flash the OTApkg.zip, i tried fastboot method. There i stuck with the signature error.
With curiosity i opened the OTApkg.zip and found firmware zip there. I flashed the firmware zip. it went fine in fastboot mode.
(fastboot oem rebootRUU, fastboot flash zip firmware.zip).
after this my phone status as below.
After flashing the latest firmware came with First OTApkg.zip Second OTApkg.zip)
*****LOCKED*******
MONARUDO PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-1.02.01.0207
OpenDSP-v12.120.274.0909
OS-4.09.605.1
eMMC-BOOT 4048MB
Mar 13 201,19:19:14.0
I hope no OS in my mobile. Mobile is not at all usable. Anyone kindly help how to get back my to work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You may be out of luck, due to the process you decided to do.
But out of curiosity, have you tried selecting apply from phone storage?
I don't recall if the stock recovery looks there for the emulated sd/internal storage files or not.
It may be that is the case and it's looking for a physical sd card when you select sd card from the menu.
If that isn't the case or doesn't help, I'm sorry.
Just thought it's worth trying if you haven't.
santod040 said:
You may be out of luck, due to the process you decided to do.
But out of curiosity, have you tried selecting apply from phone storage?
I don't recall if the stock recovery looks there for the emulated sd/internal storage files or not.
It may be that is the case and it's looking for a physical sd card when you select sd card from the menu.
If that isn't the case or doesn't help, I'm sorry.
Just thought it's worth trying if you haven't.
Click to expand...
Click to collapse
I tried everything, and nothing yet!
I got this message when i try apply from phone storage!!
check cid failed
invalid operation
rebooting phone!
I never change the cid, so...
thanks anyway
santod040 said:
You may be out of luck, due to the process you decided to do.
But out of curiosity, have you tried selecting apply from phone storage?
I don't recall if the stock recovery looks there for the emulated sd/internal storage files or not.
It may be that is the case and it's looking for a physical sd card when you select sd card from the menu.
If that isn't the case or doesn't help, I'm sorry.
Just thought it's worth trying if you haven't.
Click to expand...
Click to collapse
I hope somebody can make a process like this one:
[Latest OTA: 3.06.605.4] [Collection] HTC Droid DNA Firmware [Radio] [hboot] [RUU]
Epiel said:
I hope somebody can make a process like this one:
[Latest OTA: 3.06.605.4] [Collection] HTC Droid DNA Firmware [Radio] [hboot] [RUU]
Click to expand...
Click to collapse
yesterday i was in a similar situation like you, i had no OS, it didnt boot beyond HTC screen :crying: i panic for like 30 mins. then i follow instructions on this thread http://forum.xda-developers.com/showthread.php?t=2131284
i install install viper ROM, the i decided to wipe date, dalvik cache & flashed @santod040 http://forum.xda-developers.com/showthread.php?t=2560010
since yesterday im running kitkat 4.4.2. thanks to santod040 :good:
toolsoldier said:
yesterday i was in a similar situation like you, i had no OS, it didnt boot beyond HTC screen :crying: i panic for like 30 mins. then i follow instructions on this thread http://forum.xda-developers.com/showthread.php?t=2131284
i install install viper ROM, the i decided to wipe date, dalvik cache & flashed @santod040 http://forum.xda-developers.com/showthread.php?t=2560010
since yesterday im running kitkat 4.4.2. thanks to santod040 :good:
Click to expand...
Click to collapse
hey I need your help to do this can u email to [email protected]
thanks
Check this out
http://forum.xda-developers.com/showthread.php?t=2293919
[How-To] From S-OFF to 100% Stock S-ON [Facepalm/JTAG/RevOne/Moonshine/Rumrunner] and checkout firewater root methodchoose the pertinent parts that apply to you. But remember to stay on 3.06 to be able to root.
After that you can update to whatever you want. (Stock or custom rom)
Sent from my HTC6435LVW using Tapatalk
mobitote said:
Check this out
http://forum.xda-developers.com/showthread.php?t=2293919
[How-To] From S-OFF to 100% Stock S-ON [Facepalm/JTAG/RevOne/Moonshine/Rumrunner] and checkout firewater root methodchoose the pertinent parts that apply to you. But remember to stay on 3.06 to be able to root.
After that you can update to whatever you want. (Stock or custom rom)
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
thanks but Im already on HBOOT 1.57 S-On so I can not downgrade!
I suggest you unlock your phone through fastboot usb. then, you install custom recovery. in that manner you can flash again the KK update
Sent from my SM-T210 using XDA Premium 4 mobile app
smartz_24 said:
I suggest you unlock your phone through fastboot usb. then, you install custom recovery. in that manner you can flash again the KK update
Sent from my SM-T210 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
How to unlock the phone through fastboot?
htc dev unlock method is not working anymore.. is there any other unlock method which doesn't need abd and works on fastboot connection?
use rumrunner or moonshine. its your call..
theres no other way. all exploits run through adb and fastboot mode.
Sent from my SM-T210 using XDA Premium 4 mobile app
Try weaksauce and firewater... Else sell phone
Sent from my HTC6435LVW using Tapatalk
See if you can fastboot flash update update.zip
Use this Rom from this thread
http://forum.xda-developers.com/droid-dna/development
any solution?
Epiel said:
any solution?
Click to expand...
Click to collapse
Have you tried the ruu in this thread? http://forum.xda-developers.com/showthread.php?p=49480720
You still have fastboot working, which is all you need for that. Just use the latest ruu posted there and follow the instructions. That should at least get you a usable phone.
After that, if you want to unlock it use firewater s-off. I haven't used it, so I couldn't walk you through it, but the instructions are on the website.
Sent from my Droid DNA using Tapatalk
jamiethemorris said:
Have you tried the ruu in this thread? http://forum.xda-developers.com/showthread.php?p=49480720
You still have fastboot working, which is all you need for that. Just use the latest ruu posted there and follow the instructions. That should at least get you a usable phone.
After that, if you want to unlock it use firewater s-off. I haven't used it, so I couldn't walk you through it, but the instructions are on the website.
Sent from my Droid DNA using Tapatalk
Click to expand...
Click to collapse
Problem is Im locked and S-on too!! I can not downgrade HBOOT and I have the latest one!
thanks anyway
Arjun89 said:
How to unlock the phone through fastboot?
htc dev unlock method is not working anymore.. is there any other unlock method which doesn't need abd and works on fastboot connection?
Click to expand...
Click to collapse
have you tried to unlock bootloader through the zip in this thread yet? http://forum.xda-developers.com/showthread.php?t=2160677
here is the zip from the thread ... http://www.mediafire.com/download.php?il51rl2j1m8417b
Hello, I have been doing some firmware updates and just wanted to check if HTC posted any AT&T RUU's for backup purposes - good news 1.58.502.1 full RUU is posted here -- http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe
At least now some of us will have easier and less time consuming rollback to AT&T stock! ))
Dottcent said:
Hello, I have been doing some firmware updates and just wanted to check if HTC posted any AT&T RUU's for backup purposes - good news 1.58.502.1 full RUU is posted here -- http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe
At least now some of us will have easier and less time consuming rollback to AT&T stock! ))
Click to expand...
Click to collapse
Sweet this is nice to have!
thanks for posting, that will be nice to have.
Dottcent said:
Hello, I have been doing some firmware updates and just wanted to check if HTC posted any AT&T RUU's for backup purposes - good news 1.58.502.1 full RUU is posted here -- http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe
At least now some of us will have easier and less time consuming rollback to AT&T stock! ))
Click to expand...
Click to collapse
Wow. Not sure how you found this. When I'm looking on the HTCdev site, I can't get this to pull up...but I'm extremely grateful...
Thanks you!!
Mark
Finally! Thanks for posting.
I can confirm this works. Used it to return to stock, used the guides here http://forum.xda-developers.com/showthread.php?t=2751011 to remove the tampered flag and relock the bootloader with out tripping the relocked flag, then ran this RUU, everything is 100% back to stock, except for S-Off.
zacharyt86 said:
I can confirm this works. Used it to return to stock, used the guides here http://forum.xda-developers.com/showthread.php?t=2751011 to remove the tampered flag and relock the bootloader with out tripping the relocked flag, then ran this RUU, everything is 100% back to stock, except for S-Off.
Click to expand...
Click to collapse
Glad it worked I haven't had a chance to try it. I'm still running GPE ruu but glad to see there is a easier way to return to stock.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
issue
RUU wont run for me no matter what I do. I have tried locking, CWS__001, wiping everything and putting in RUU mode and the .exe wont run past the EULA acceptance
orvon.freeman said:
RUU wont run for me no matter what I do. I have tried locking, CWS__001, wiping everything and putting in RUU mode and the .exe wont run past the EULA acceptance
Click to expand...
Click to collapse
same here. pissing me off lol. i think its actually corrupted. because by pulling the rom.zip file if you open it . it doesnt even look like all the files are there
daddioj said:
same here. pissing me off lol. i think its actually corrupted. because by pulling the rom.zip file if you open it . it doesnt even look like all the files are there
Click to expand...
Click to collapse
If you feel the file is corrupt, you can download the RUU from the HTC's website, you will find it under device support (ATT HTC ONE M8). I think your bootloader has to be locked to be able to install the RUU.
wurldfamuz said:
If you feel the file is corrupt, you can download the RUU from the HTC's website, you will find it under device support (ATT HTC ONE M8). I think your bootloader has to be locked to be able to install the RUU.
Click to expand...
Click to collapse
i know i been doin HTC for years . ok bad choice of words lol. isnt that what the original link is? i never checked
downloaded from the source and still wont run
---------- Post added at 04:11 PM ---------- Previous post was at 04:10 PM ----------
as a not I did do the google edition con
wurldfamuz said:
If you feel the file is corrupt, you can download the RUU from the HTC's website, you will find it under device support (ATT HTC ONE M8).
Click to expand...
Click to collapse
The link in the OP is the HTC link. Same link as given on AT&T's support page: http://www.htc.com/us/support/htc-one-m8-att/news/
---------- Post added at 04:27 PM ---------- Previous post was at 04:25 PM ----------
For folks having trouble running RUU, do you have HTC drivers installed, and is adb/fastboot able to see the phone?
Bootloader typically needs to be locked or relocked to run RUU on past HTC devices. But S-off bypasses this requirement.
---------- Post added at 04:29 PM ---------- Previous post was at 04:27 PM ----------
redpoint73 said:
Finally! Thanks for posting.
Click to expand...
Click to collapse
Actually, when I said "Finally" it was more in regard to the fact we haven't had any official RUU for this device yet.
Its actually quite fast for HTC to have the RUU so fast (1 week) after rolling out the OTA.
zacharyt86 said:
I can confirm this works. Used it to return to stock, used the guides here http://forum.xda-developers.com/showthread.php?t=2751011 to remove the tampered flag and relock the bootloader with out tripping the relocked flag, then ran this RUU, everything is 100% back to stock, except for S-Off.
Click to expand...
Click to collapse
... hummmm? i thought relocking the bootloader and then flashing with a RUU will clear the Tampered/Locked flag. Thoughts?
cortez.i said:
... hummmm? i thought relocking the bootloader and then flashing with a RUU will clear the Tampered/Locked flag. Thoughts?
Click to expand...
Click to collapse
No I tried that the first time and it flashed the ruu fine but the flag stayed at relocked and tampered, then I re-unlocked the bootloader and folled the links in that post to remove them, then flashed the ruu, now it all shows as normal, except for s-off, which isn't that obvious.
cortez.i said:
... hummmm? i thought relocking the bootloader and then flashing with a RUU will clear the Tampered/Locked flag. Thoughts?
Click to expand...
Click to collapse
Tampered yes, Relocked no
Tampered just appears when you install a custom recovery. So since the RUU re-installs stock recovery, the Tampered flag is removed.
The bootloader lock flag is intended to always say either Unlocked or Relocked, once its been initially unlocked. Its intended to never be returned to Locked (once unlocked). But hboot can be hacked to make it so. An official RUU will never do this.
Success! I was s-off rooted and had twrp, all I did was followed the directions. I also took out my sim card and SD card.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 7 using Tapatalk
redpoint73 said:
Finally! Thanks for posting.
Click to expand...
Click to collapse
Exactly my thought, finally! ?
Those who ran RUU - thanks for your success confirmation! ?
Sent from my HTC One_M8 using Tapatalk
zacharyt86 said:
No I tried that the first time and it flashed the ruu fine but the flag stayed at relocked and tampered, then I re-unlocked the bootloader and folled the links in that post to remove them, then flashed the ruu, now it all shows as normal, except for s-off, which isn't that obvious.
Click to expand...
Click to collapse
appreciate you reconfirming steps to return to "stock".:good:
redpoint73 said:
Tampered yes, Relocked no
Tampered just appears when you install a custom recovery. So since the RUU re-installs stock recovery, the Tampered flag is removed.
The bootloader lock flag is intended to always say either Unlocked or Relocked, once its been initially unlocked. Its intended to never be returned to Locked (once unlocked). But hboot can be hacked to make it so. An official RUU will never do this.
Click to expand...
Click to collapse
thank you for the clarification... i feel "slightly safer" experimenting with M8. :good:
does anyone know how to make this a flashable zip to use with rebootRUU?
Pretty much this is what happened. I wanted to convert my version to the GPE. It was working fine, but as soon as I did the 4.4.4 OTA, I got stuck in boot loop. So, I looked up some guides and I somehow wound up flashing something I wasn't supposed to. Now I have the GPE bootloader, and for some reason, no matter what recovery I use, the installation of any sense based rom fails. I have no idea how I manged to do what I did, considering I was never able to get s-off. So now, I've finally given up trying to figure it out myself. I was wondering if anybody has had experience with this. I have no idea what to do. I would like to have the option to be able to install sense roms too. Not sure what information I can give to help, but please ask me if you can. Thank you.
Edit: getvar.
version: 0.5
version-bootloader: 3.18.0.0000
version-baseband: 1.16.21331931.LA11G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
imei2: Not Support
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 6e0f5a3d
hbootpreupdate: 11
gencheckpt: 0
The full GPE conversion changes the partitioning on the memory, which is not compatible with Sense ROMs. But as you mentioned, AFAIK you need s-off to do the full conversion. So not sure what's going on.
Do adb getvar all to confirm hboot, CID and S-off (remove serial number and IMEI if you cut/paste getvar output, as these are sensitive personal info).
Have you tried flashing a GPE ROM?
Is your ultimate intent to stay on GPE (and get OTAs) or go back to Sense ROMs?
My recommendation would be to just run the RUU and start over to stock Sense hboot, ROM, recovery, etc. But it somewhat depends on your final intent. Since you are s-on, you will need to relock the bootloader to RUU. Also, CID will need to be AT&T's or SuperCID; and you can't "downgrade" hboot version with s-on (RUU hboot has to be equal or greater than what is installed on the device).
redpoint73 said:
The full GPE conversion changes the partitioning on the memory, which is not compatible with Sense ROMs. But as you mentioned, AFAIK you need s-off to do the full conversion. So not sure what's going on.
Do adb getvar all to confirm hboot, CID and S-off (remove serial number and IMEI if you cut/paste getvar output, as these are sensitive personal info).
Have you tried flashing a GPE ROM?
Is your ultimate intent to stay on GPE (and get OTAs) or go back to Sense ROMs?
My recommendation would be to just run the RUU and start over to stock Sense hboot, ROM, recovery, etc. But it somewhat depends on your final intent. Since you are s-on, you will need to relock the bootloader to RUU. Also, CID will need to be AT&T's or SuperCID; and you can't "downgrade" hboot version with s-on (RUU hboot has to be equal or greater than what is installed on the device).
Click to expand...
Click to collapse
Right now my goal is to go back to sense if I can't get gpe to work properly with functioning OTA. I tried an RUU but it gave me an error. I've been trying to s-off using firewater, but I've had no luck. I'm at work at the moment but I will try to do what you suggested when I get home. Thank you for your response.
deviousconundrum said:
I tried an RUU but it gave me an error.
Click to expand...
Click to collapse
It would be useful to know what error message it gave you. And which RUU you tried.
With S-on, you can't run an RUU with an hboot version that is older than what is on the phone (fails version check). I can tell you more (which RUU should work) once you've had a chance to supply the getvar info requested previously.
Also, if you happened to change the CID and/or MID to convert to GPE, it might cause those checks to fail.
Or you might just have a general USB connectivity issue, or a corrupt RUU file. Its impossible to know if you aren't specific. Be sure to check if the command "adb devices" works to make sure there isn't a general USB connection issue.
redpoint73 said:
It would be useful to know what error message it gave you. And which RUU you tried.
With S-on, you can't run an RUU with an hboot version that is older than what is on the phone (fails version check). I can tell you more (which RUU should work) once you've had a chance to supply the getvar info requested previously.
Also, if you happened to change the CID and/or MID to convert to GPE, it might cause those checks to fail.
Or you might just have a general USB connectivity issue, or a corrupt RUU file. Its impossible to know if you aren't specific. Be sure to check if the command "adb devices" works to make sure there isn't a general USB connection issue.
Click to expand...
Click to collapse
I'm going to try to install GPE and see what happens. I will post what happens afterwards. I also noticed that in my recovery. /data keeps failing to mount. At the moment I'm running Pacman Rom.
Edit: I got the error executing updater binary in zip 'extenrnal_sd/Downloads/GPE4.4.3_m8.zip message when I tried flashing it.
It appears I have a gpe image on my m8 phone??? Do I flash firmware?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
deviousconundrum said:
I also noticed that in my recovery. /data keeps failing to mount.
Click to expand...
Click to collapse
This is a known issue for some folks, particularly with TWRP. It will cause a lot of other things to fail, like ROM flashing. You may need to format your internal memory. But RUU should have sorted this out, so RUU failing is probably a separate issue. Need more details before I can give more help.
redpoint73 said:
This is a known issue for some folks, particularly with TWRP. It will cause a lot of other things to fail, like ROM flashing. You may need to format your internal memory. But RUU should have sorted this out, so RUU failing is probably a separate issue. Need more details before I can give more help.
Click to expand...
Click to collapse
Which RUU are you talking about though? The actual executable one? or the one invoked through adb/fastboot? I tried the exe and when it got to the current version, it was blank, and only option was update. I did that, but then that's when it failed because of a mismatch I think.
deviousconundrum said:
Which RUU are you talking about though? The actual executable one? or the one invoked through adb/fastboot? I tried the exe and when it got to the current version, it was blank, and only option was update. I did that, but then that's when it failed because of a mismatch I think.
Click to expand...
Click to collapse
I'm talking about the exe one, or the bootable one here (which you should try, if you haven't): http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
You also haven't stated which RUU you tried, which I asked for previously. Was it the 1.58 or 2.23 RUU?
Not sure, but I don't think main version being blank would cause RUU to fail. The number just can't be higher than the main version of the RUU. Blank should be okay, I think. But if that is the issue, I wonder if there is a way to change main version using an adb command? There must be a way, I just don't know it.
redpoint73 said:
I'm talking about the exe one, or the bootable one here (which you should try, if you haven't): http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
You also haven't stated which RUU you tried, which I asked for previously. Was it the 1.58 or 2.23 RUU?
Not sure, but I don't think main version being blank would cause RUU to fail. The number just can't be higher than the main version of the RUU. Blank should be okay, I think. But if that is the issue, I wonder if there is a way to change main version using an adb command? There must be a way, I just don't know it.
Click to expand...
Click to collapse
It was the one to update from 4.4.2 to 4.4.3 I believe. And thank you, I will try the bootable one.
Edit: I tried it and I got the error wrong zipped image. Seriously don't know what else to do.
Even though for some reason I can't get the GPE version to install anymore. SkyDragon GPE edition works for me. But, no matter what I try I can't s-off. Both firewater and sunshine don't work for me. Firewater fives me that message after the first chug, that says firewater doesn't work on my version, sorry. What can I do as S-on to get back to sense? Is it even possible? Nandroid back ups? Hehe, I have no idea. Maybe there's something I'm not seeing here. Anyways,thank you for your help, I see I'm going to have to do a bit more research to maybe find the answer I seek.
deviousconundrum said:
Even though for some reason I can't get the GPE version to install anymore. SkyDragon GPE edition works for me. But, no matter what I try I can't s-off. Both firewater and sunshine don't work for me. Firewater gives me that message after the first chug, that says firewater doesn't work on my version, sorry. What can I do as soon to get back to sense? Is it even possible? Nandroid back ups? Hehe, I have no idea. Maybe there's something I'm not seeing here. Anyways, thank you for your help, I see I'm going to have to do a bit more research to maybe find the answer I seek.
Click to expand...
Click to collapse
I had a similar problem a while back ago. I had to install a stock recovery and do a factory reset. It fixed my problems and I went back to flashing.
BR7fan said:
I had a similar problem a while back ago. I had to install a stock recovery and do a factory reset. It fixed my problems and I went back to flashing.
Click to expand...
Click to collapse
Which stock recovery should I download though? The stock sense one or the gpe one? Are recoveries independent from the rom itself?
same
I am having the same problem, i have a converted GPE skydragon m8 with s-on, firewater hasnt worked. i want to return to stock sense but im having trouble finding the solution.
Mirzatron said:
I am having the same problem, i have a converted GPE skydragon m8 with s-on, firewater hasnt worked. i want to return to stock sense but im having trouble finding the solution.
Click to expand...
Click to collapse
Yeah, I've tried everything. Unfortunately I don't remember the steps I took to get into this sort of situation. I know I did flash a lot of things. Thus explaining why my bootloader is different. It's black with an android in the bottom instead of the stock one I had that was 3 of them on skateboards, also, the HTC boot screen, has a little pic of an open lock. Before it just had red words in the bottom. Do you also have those same things I described?
Mirzatron said:
I am having the same problem, i have a converted GPE skydragon m8 with s-on, firewater hasnt worked. i want to return to stock sense but im having trouble finding the solution.
Click to expand...
Click to collapse
I used the sense one.
BR7fan said:
I used the sense one.
Click to expand...
Click to collapse
what do you mean?
Mirzatron said:
what do you mean?
Click to expand...
Click to collapse
Stock recovery. Find one,flash it and do a factory reset
BR7fan said:
Stock recovery. Find one,flash it and do a factory reset
Click to expand...
Click to collapse
I read that flashing sense wouldn't work since the gpe partition is smaller.
Mirzatron said:
I read that flashing sense wouldn't work since the gpe partition is smaller.
Click to expand...
Click to collapse
Useca gpe stock recovery
BR7fan said:
Useca gpe stock recovery
Click to expand...
Click to collapse
Do you think by using the stock gpe recovery, i will be able to s-off?
I have packaged up the last two official RUUs into exe form for use on the DNA. I have tested these on my own DNA. They will work with locked/s-on phones.
DO NOT LOCK OR S-ON for the purpose of flashing these. It's not necessary.
Below you will find both 4.09.605.1 and 4.09.605.5
Intructions:
Extract to folder. Double click ARUwizard.exe. Follow prompts. When complete phone will reboot. If attempting on a non bootable phone connect the phone in fastboot mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Downloads
4.09.605.1 link
- https://www.androidfilehost.com/?fid=312968873555011856
4.09.605.5 link
- https://www.androidfilehost.com/?fid=312978532265371239
Very nice work. Haven't tested, but if I ever need to this is available. Thanks
MicroMod777 said:
Very nice work. Haven't tested, but if I ever need to this is available. Thanks
Click to expand...
Click to collapse
These ones are great too because they don't phone home and they don't care what custom rom you had been on. We had a problem for a while on htc phones that didn't have external SD cards failing signature checks when flashing via fastboot.. With these that problem is no more.
I have a couple of questions.;
1) does it matter what firmware you are on to flash any of these 2 firmwares?
2) if I wanted to RUU to complete 100% stock, I can use either of these?
3) Can I flash these if I am currently using a modified hboot?
4) will my deivce stay S-OFF after flashing either of these?
50 Will my HBOOT stay Unlocked after flashing either of these?
Thanks....
ThePunisher said:
I have a couple of questions.;
1) does it matter what firmware you are on to flash any of these 2 firmwares?
2) if I wanted to RUU to complete 100% stock, I can use either of these?
3) Can I flash these if I am currently using a modified hboot?
4) will my deivce stay S-OFF after flashing either of these?
50 Will my HBOOT stay Unlocked after flashing either of these?
Thanks....
Click to expand...
Click to collapse
1)Firmware version depends. If you want the latest one and you are not current on firmware I would suggest flashing the hboot separately.
2) yes either will do. Either will also flash on a locked and s-on phone as well.
3)there's a good chance your hboot will get over-written with a stock one. Are you aware of what can happen if you ever try to s on using a modified boot?
4+5) these will not affect your unlock or s status.
there's a good chance your hboot will get over-written with a stock one. Are you aware of what can happen if you ever try to s on using a modified boot?
Click to expand...
Click to collapse
my main concern was if I could use your RUU to flash my DNA. I could care less whether it overrides my current hboot, as long as it does not during the flashing process lock and s-on my device
thanks for your reply....
This will not make a connection to my Device. However, ADB and Fastboot works, but this RUU/FUU still gives an error....
Current setup:
Unlocked
S-Off
hboot 1.57
Stock (Rooted) 4.4.2/Sense 5.5 Rom
ThePunisher said:
This will not make a connection to my Device. However, ADB and Fastboot works, but this RUU/FUU still gives an error....
Current setup:
Unlocked
S-Off
hboot 1.57
Stock (Rooted) 4.4.2/Sense 5.5 Rom
Click to expand...
Click to collapse
What mode are you starting it in ? The phone that is..
dottat said:
What mode are you starting it in ? The phone that is..
Click to expand...
Click to collapse
I have tried from the Android Homescreen, ADB, Fastboot, and from the RebootRUU downloader/installer. Neither of those work. I have also tried usb 2 and 3 ports. I have tried with and without usb debugging enabled. HTC Sync loads the the device without issues.
ThePunisher said:
I have tried from the Android Homescreen, ADB, Fastboot, and from the RebootRUU downloader/installer. Neither of those work. I have also tried usb 2 and 3 ports. I have tried with and without usb debugging enabled. HTC Sync loads the the device without issues.
Click to expand...
Click to collapse
It never even reboots the phone? What os do you have?
ThePunisher said:
my main concern was if I could use your RUU to flash my DNA. I could care less whether it overrides my current hboot, as long as it does not during the flashing process lock and s-on my device
thanks for your reply....
Click to expand...
Click to collapse
Thank you So Much to the person(s) that made this possible, I've been patiently waiting for this fix and it finally paid off - I can confirm that this 100% works - I had previously all but bricked my phone, it was Re-Locked and S-On along with Tampered - I could only get Hboot to come on and Fastboot. Now it has been completely restored to stock firmware - It still says RELOCKED when in hboot mode but I'm ok with that -
Android Version 4.4.2
HTC Sense Version 5.5
Software Number 4.09.605.1
tat2me2 said:
Thank you So Much to the person(s) that made this possible, I've been patiently waiting for this fix and it finally paid off - I can confirm that this 100% works - I had previously all but bricked my phone, it was Re-Locked and S-On along with Tampered - I could only get Hboot to come on and Fastboot. Now it has been completely restored to stock firmware - It still says RELOCKED when in hboot mode but I'm ok with that -
Android Version 4.4.2
HTC Sense Version 5.5
Software Number 4.09.605.1
Click to expand...
Click to collapse
You are welcome.....DNA crowd has not been forgotten!?
dottat said:
It never even reboots the phone? What os do you have?
Click to expand...
Click to collapse
no, it reboots everytime to the RUU Downloader/Installer on the phone but then gives that error after trying to send the first packet. It never gets past the "Updating 0 of 5" . As I posted. i am running stock rooted 4.4.2/Sense 5.5. I was just wanting to test this ruu out and give feed back.
ThePunisher said:
no, it reboots everytime to the RUU Downloader/Installer on the phone but then gives that error after trying to send the first packet. It never gets past the "Updating 0 of 5" . As I posted. i am running stock rooted 4.4.2/Sense 5.5. I was just wanting to test this ruu out and give feed back.
Click to expand...
Click to collapse
When it gets to the ruu mode it starts a 60 second time out. Quickly unplug the phone and reconnect it to another port.
dottat said:
When it gets to the ruu mode it starts a 60 second time out. Quickly unplug the phone and reconnect it to another port.
Click to expand...
Click to collapse
This is where is gets stuck before is says unable to make a connection. i also tried disabling my av and firewall with no further progress.
ThePunisher said:
This is where is gets stuck before is says unable to make a connection. i also tried disabling my av and firewall with no further progress.
Click to expand...
Click to collapse
How long did you leave it sitting? Until it timed out? Also, open task manager and tell me how much free ram you have.
dottat said:
How long did you leave it sitting? Until it timed out? Also, open task manager and tell me how much free ram you have.
Click to expand...
Click to collapse
yes, until it timed out approximately 3-5mins. i tried what you recommended but it did not work. I have a custom built win 8 x64 with 16gb of ram. trust me, im not using even a 1/3 of that, lol
ThePunisher said:
yes, until it timed out approximately 3-5mins. i tried what you recommended but it did not work. I have a custom built win 8 x64 with 16gb of ram. trust me, im not using even a 1/3 of that, lol
Click to expand...
Click to collapse
Try running the app in windows 7 compatibility mode and as admin.
You would be surprised what an x64 system can consume. To send the ruu over usb the system has to have enough free ram for the 1.x gig file to fit in the free ram.
dottat said:
Try running the app in windows 7 compatibility mode and as admin.
You would be surprised what an x64 system can consume. To send the ruu over usb the system has to have enough free ram for the 1.x gig file to fit in the free ram.
Click to expand...
Click to collapse
says im using 11% of my installed ram i tried running as an admin previously. I tried Win7 Compat mode, still no progress. I guess the RUU is not meant to work for me lol
ThePunisher said:
says im using 11% of my installed ram i tried running as an admin previously. I tried Win7 Compat mode, still no progress. I guess the RUU is not meant to work for me lol
Click to expand...
Click to collapse
Can you install team viewer and screen share with me? If that's ok pm me your login info
As many of you are aware, flashing roms to our phone comes with risk. That risk is dimished by the availability of an RUU for our phone.
I have made this available as a standalone APP (.exe) for PC use as well as a SINGLE zip file for SD card loading.
This is for s-off users only. I repeat...s-off only.
This WILL wipe your phone (internal memory). IF you are able...backup data prior to using this. This works EXACTLY like an RUU for s-off users. Two options exist for using this zip. This will land you on STOCK Lollipop 5.0.2 or Kitkat 4.4.4 pre-rooted with stock recovery.
Option 1
Download the RUU.zip for the OS you would like to land on and Rename file to 0P6BIMG.zip and Copy 0P6BIMG.zip to root of a physical SD. Not internal storage! If you have issues with it getting stuck while loaded simply flash the hboot zip below first using the above method.
Reboot phone to bootloader and follow prompts once RUU is detected by phone.
Option 2 (App/EXE)
For Lollipop, this will be a single EXE with no need to extract. The EXE will install any/all dependencies your pc needs to in order to flash. Simply download the Lollipop exe and run it!
For Kit Kat exe-
Download DOTTAT_ATTM8_4.4.4_S_off_FUU.zip from below. Extract files to folder. Double click ARUwizard.exe. Proceed with prompts until phone reboots (complete).
## expect a good 5 minute plus first boot!
### if you get a side by side application error install this and the fuu again.
- https://www.androidfilehost.com/?fid=95916177934538674
Downloads Do NOT mirror these elsewhere.
SD card method zip
Lollipop
- https://www.androidfilehost.com/?fid=95916177934552416
KitKat
- https://www.androidfilehost.com/?fid=95916177934519267
FUU/EXE method
Lollipop
- https://www.androidfilehost.com/?fid=95916177934552420
Kitkat
- https://www.androidfilehost.com/?fid=95916177934519268
4.4.4 HBOOT zip (SD card flashable)
- https://www.androidfilehost.com/?fid=95916177934519892
Links are live....mine.
Thank you for the RUU. What radio version and hboot will it update the phone to?
devbro said:
Thank you for the RUU. What radio version and hboot will it update the phone to?
Click to expand...
Click to collapse
Baseband here. I honestly forgot to check hboot but it's likely 3.19 like the other m8's.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This looks like the OTA that came down from AT&T this past week? If so it comes with a new radio that switches the AT&T APN to something called "nxtgenphone". This has been found to have issues with ROMS like CM12, in which no data signal is present and you are not able to set a new APN to resolve the issue. As far as I know it's actively being worked on by the CM team, but I haven't seen any updates in the past 24 hours or so. I do not know if this new radio has adverse affects on other ROMs.
Ajax1885 said:
This looks like the OTA that came down from AT&T this past week? If so it comes with a new radio that switches the AT&T APN to something called "nxtgenphone". This has been found to have issues with ROMS like CM12, in which no data signal is present and you are not able to set a new APN to resolve the issue. As far as I know it's actively being worked on by the CM team, but I haven't seen any updates in the past 24 hours or so. I do not know if this new radio has adverse affects on other ROMs.
Click to expand...
Click to collapse
thanks for the heads up! Sounds like the same crap we have been going through over on the VZW devices for some time. We have sim card unlocked phones from the factory but the APN selection has become a huge pain in the arse. You cannot edit them and have to use what shows up (which varies based on the sim card used and they only ALL show when a vzw sim card is inserted!)
Do we need stock recovery installed in order to run these?
DanGeorges said:
Do we need stock recovery installed in order to run these?
Click to expand...
Click to collapse
Nope!
dottat said:
Nope!
Click to expand...
Click to collapse
So is this an RUU or an FUU? The two are pretty different and I'm not sure if I should use this or not?
CavyS said:
So is this an RUU or an FUU? The two are pretty different and I'm not sure if I should use this or not?
Click to expand...
Click to collapse
Both are full RUU. One is just the zip version and one is the EXE. Both are pre-rooted.
I am currently on a stock custom rom that's on 4.4.2 with Philz recovery. Can I just run this ruu to update? I realize I may lose data but I've got that backed up.
johnnyutah22 said:
I am currently on a stock custom rom that's on 4.4.2 with Philz recovery. Can I just run this ruu to update? I realize I may lose data but I've got that backed up.
Click to expand...
Click to collapse
Yes. You may need to separately flash the hboot if you do the SD card method.
@dottat
Nice to see you over here bud.
Just an FYI for those coming from 4.4.2. I was on Skyfall's custom stock 4.4.2 with a ton of xposed mods. I followed the sd card method for install and then did a data only restore from a twrp nandroid. Everything restored fine except for my notification ringtones which I had pushed to system. You will have to reinstall the xposed framework for the modules to kick back in.
Question, does one have to be CID specific to flash this? I am currently SuperCID and don't have a computer with HTC drivers at my disposal right now.
Chargerdude70 said:
Question, does one have to be CID specific to flash this? I am currently SuperCID and don't have a computer with HTC drivers at my disposal right now.
Click to expand...
Click to collapse
Super cid should be ok as long as your mid matches.
took me two tries but the 0p6bimg.zip method worked for me to revert from GPE conversion. The first time it said it failed, booted to a red triangle screen. Manually booted back to hboot and that had reverted. let it update again and it was fine.
Thanks for this.
Straight outta York yo!
Duffman14 said:
took me two tries but the 0p6bimg.zip method worked for me to revert from GPE conversion. The first time it said it failed, booted to a red triangle screen. Manually booted back to hboot and that had reverted. let it update again and it was fine.
Thanks for this.
Straight outta York yo!
Click to expand...
Click to collapse
I can tell you why the first time failed if you want to know.
sure, I would like to. I'm sure it might be good information for others also
Duffman14 said:
sure, I would like to. I'm sure it might be good information for others also
Click to expand...
Click to collapse
Gpe uses a much smaller system partition. When converting back to sense the best method is to flash the latest sense firmware and factory reset from hboot or recovery. That format puts your system partition back to the stock size of around 2.6 gigs vs the 1.2gigs of gpe.