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?
Related
First off, my question is whether im stuck with hboot 2.09 until they release a RUU, or is there a magical way to downgrade?
Sorry, I've got quite the situation to explain.
I was running 2.13.651.1 rooted stock rom + TWRP 2.3, (had hboot 1.12) but I wanted to bust out the new jellybean update. So, I unrooted and attempted to install but it kept booting into twrp and if I used twrp, it gave me an error of assert failed status 7(couldnt find a cid or something) So i flashed over the stock recovery and attempted to upgrade but it failed with a red triangle(!). I then figured it was because it was upset about the build, so I RUU'd down to 1.13.651.1 and the updates worked great. I stopped at 2.13.651.1 and was going to dirtyracun to s-off but i first decided to test the jellybean update. Well I soon realized that i had really screwed up because now Im stuck with hboot 2.09, and there doesnt appear to be anyway to flash an older version. Am i mistaken ?
Its pretty messed up right now. bootloops into the bootloader when its relocked, and carries a security warning. But if i unlock it, it boots up to the os fine.
Also, I noticed that if I try and use the 1.13 RUU , while its unlocked ( i know it doesnt work) , it detects that the firmware version is 2.13. However, if i start the ruu from the bootloader, it detects the firmware as 3.15.. interesting. I wasnt sure if the hboot was skewing the version detection or not.
If any of you geniuses can provide any shed of light, please do.
-Thanks.
P.S , I have a android backup from twrp, but it cant seem to boot after and it fails to mount the sdcard ? When it did complete successfully(once), it wouldnt boot, the screen went black. Even a factory reset didnt seem to fix it, but for some reason it works now if unlocked.
Jessman123 said:
First off, my question is whether im stuck with hboot 2.09 until they release a RUU, or is there a magical way to downgrade?
Sorry, I've got quite the situation to explain.
I was running 2.13.651.1 rooted stock rom + TWRP 2.3, (had hboot 1.12) but I wanted to bust out the new jellybean update. So, I unrooted and attempted to install but it kept booting into twrp and if I used twrp, it gave me an error of assert failed status 7(couldnt find a cid or something) So i flashed over the stock recovery and attempted to upgrade but it failed with a red triangle(!). I then figured it was because it was upset about the build, so I RUU'd down to 1.13.651.1 and the updates worked great. I stopped at 2.13.651.1 and was going to dirtyracun to s-off but i first decided to test the jellybean update. Well I soon realized that i had really screwed up because now Im stuck with hboot 2.09, and there doesnt appear to be anyway to flash an older version. Am i mistaken ?
Its pretty messed up right now. bootloops into the bootloader when its relocked, and carries a security warning. But if i unlock it, it boots up to the os fine.
Also, I noticed that if I try and use the 1.13 RUU , while its unlocked ( i know it doesnt work) , it detects that the firmware version is 2.13. However, if i start the ruu from the bootloader, it detects the firmware as 3.15.. interesting. I wasnt sure if the hboot was skewing the version detection or not.
If any of you geniuses can provide any shed of light, please do.
-Thanks.
P.S , I have a android backup from twrp, but it cant seem to boot after and it fails to mount the sdcard ? When it did complete successfully(once), it wouldnt boot, the screen went black. Even a factory reset didnt seem to fix it, but for some reason it works now if unlocked.
Click to expand...
Click to collapse
yes, i am sorry to say that you are stuck with hboot 2.09.
tekno4ever said:
yes, i am sorry to say that you are stuck with hboot 2.09.
Click to expand...
Click to collapse
Dang. Well , thanks. Nice to know. Does it take them very long to make a RUU ?
Jessman123 said:
Dang. Well , thanks. Nice to know. Does it take them very long to make a RUU ?
Click to expand...
Click to collapse
not sure, but i know its coming down the pipe.
Same here
***Tampered***
***Relocked***
Jewel PVT Ship S-Off Rl
CID-SPCS_001
HBoot-2.09.0000
Radio-1.12.11.1119
OpebDSP-V31.1.0.45.0815
eMMC-boot
Oct 18 2012
So far after having the dirty racun take the tamper away when i was @ HBoot 1.12. But being stupid i downloaded the full zip PJ with recovery etc.
I was also panicking.
So here is the deal
The phone is now relocked and has stock recovery which is useless.
What i did was the following.
download the latest recovery file. Open the cmnd window and follow the instructions of how to unlock the bootloader. after you have unlocked the bootloader, restart, and go back into bootloader, it should say unlocked. now in fastboot usb run the (flash) the recovery. Reboot. Then install the rom...
if you need help let me know... but as of now we are stuck with the ***TAMPERED*** ***UNLOCKED**** until someone does a RUU
Jessman123 said:
Dang. Well , thanks. Nice to know. Does it take them very long to make a RUU ?
Click to expand...
Click to collapse
Are you familiar with linux os? A few of us on here a couple months ago worked on a way to downgrade from 1.15 and 1.19 to 1.12. If you're up for it, I believe I have something that may help you. But it can get very in depth if you don't do it correctly.
Sent from my Jelly Bean'd EVO LTE
Look at your bootloader. Its s-off. Flash your favorite recovery and then your favorite Rom. Or wait for the newest ruu
You should still be s-off so your hboot shouldn't matter too much
Sent from my EVO using xda premium
Well, I was able to get it to re-install my backup successfully. So I am now back where I started before my tampering, just with hboot 2.09. Its fully functional now, I was just eager to get Jellybean .
There is something I've never understood. I *thought* I had unlocked my bootloader when I first got my phone by using HTC's instructions. When I used theirs, it shows Unlocked, however, right below it states S-ON still. I am able to flash whatever I want when it says unlocked, so I assumed it had done its job. But I wasn't sure, so this is why I was going to do the Dirty Racun in the first place.
My goal was simply to achieve the update but keep my precious root, and with all my things left untouched like the typical OTA.
@EVOMIKE025 - I haven't had much time to play directly with Linux, but I have dealt with other Linux devices, so I'm sure I might be competent enough to handle your secrets, but there is only one way to find out! However, I'm kinda nervous of messing with the phone without a RUU available right now. I just couldn't get the OTA to function, and I think it was because of TWRP getting in the way of its reboot. If I have to bite the bullet and re-install everything and my root access, I may do it. I haven't had much time though, this all happened on a sunny day with spare time. Unfortunately a simple upgrade turned into this.
EVOMIKE025 said:
Are you familiar with linux os? A few of us on here a couple months ago worked on a way to downgrade from 1.15 and 1.19 to 1.12. If you're up for it, I believe I have something that may help you. But it can get very in depth if you don't do it correctly.
Sent from my Jelly Bean'd EVO LTE
Click to expand...
Click to collapse
how did you unlock 2.09 hboot with s-off? I accidently hit the install and couldnt stop it from rebooting and installing persistently. Didnt want to brick the phone so i let it go. Now im "dev rooted" and i cant do ****. Can you help me out?
how did you unlock 2.09 hboot with s-off? I accidently hit the install and couldnt stop it from rebooting and installing persistently. Didnt want to brick the phone so i let it go. Now im "dev rooted" and i cant do ****. Can you help me out?
Click to expand...
Click to collapse
Personally, when I wanted to re-lock it, I used "fastboot flash oem-lock" and when I wanted to unlock it again, I flashed the "Unlock_Code.bin" back over that I got from the HTC Dev. That's how i was able to flop around on the locking and re-locking. Don't know if that helps? :fingers-crossed:
guess I'm stuck!
Ok. First time to post so go easy! I got mine unlocked, 2.09. But unable to root. I guess that's the deal till someone comes out with an ruu??
My phone says unlocked, S-on.
It will not load the twrp recovery. IDK if it is me or just not available. The phone is working fine. So I will roll with it but would love some insight!
bradhary said:
Ok. First time to post so go easy! I got mine unlocked, 2.09. But unable to root. I guess that's the deal till someone comes out with an ruu??
My phone says unlocked, S-on.
It will not load the twrp recovery. IDK if it is me or just not available. The phone is working fine. So I will roll with it but would love some insight!
Click to expand...
Click to collapse
Unless I've misunderstood android the last 3yrs, RUU has nothing to do with root. (Unless I'm misinterpreting your meaning in 1st paragraph. where it seems you're associating the 2). RUU will not help with root.
Once you're unlocked thru HTC dev, you can fastboot flash custom recovery (TWRP). With custom recovery installed, you can flash superuser (root) binaries and install superuser or superSU.
Check the thread in development by regaw_lienad for more info and file links. Or you can Google chainsDD superuser for his website with the binaries zip (while I'm at it, wow, all us android users have a lot of thanking to do to chainsDD).
Sent from my EVO using xda premium
bradhary said:
Ok. First time to post so go easy! I got mine unlocked, 2.09. But unable to root. I guess that's the deal till someone comes out with an ruu??
My phone says unlocked, S-on.
It will not load the twrp recovery. IDK if it is me or just not available. The phone is working fine. So I will roll with it but would love some insight!
Click to expand...
Click to collapse
Everything you need to flash recovery and SU is here
Thank you
bigdaddy619 said:
Everything you need to flash recovery and SU is here
Click to expand...
Click to collapse
Got it done! Thanks to all! Especially you my friend, hope I don't leave anyone out! Should I update the superSu? I clicked on it to see if it would open and it did, just asked iff I wanted to update..I really don't want to mess it up allready!
Thanks again, Brad.
PS, It was the new 2.3.3.0 that did it!
SU binary needs to be updated. continue?
bradhary said:
Got it done! Thanks to all! Especially you my friend, hope I don't leave anyone out! Should I update the superSu? I clicked on it to see if it would open and it did, just asked iff I wanted to update..I really don't want to mess it up allready!
Thanks again, Brad.
PS, It was the new 2.3.3.0 that did it!
Click to expand...
Click to collapse
when I hit continue, my phone just does a reboot... Any one..
I think I got it???
Sorry to be a pain! And sorry to the OP for hijacking! Got the wifi to work, phone says it's rooted but the supersu is still out of date and will reboot if I try to update. If anyone has any ideas as to what I could try next, thank you in advance! I will roll like it is as it seems to be working. :good:
bradhary said:
when I hit continue, my phone just does a reboot... Any one..
Click to expand...
Click to collapse
The reboot when updating super user binaries is a known issue introduced in hboot 2.09.....its basically HTC messing with the developers' capabilities of customizing etc....
{
"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"
}
http://www.pocketables.com/2012/12/...rs.html?utm_source=dlvr.it&utm_medium=twitter
Sent from my EVO using xda app-developers app
EVOMIKE025 said:
Are you familiar with linux os? A few of us on here a couple months ago worked on a way to downgrade from 1.15 and 1.19 to 1.12. If you're up for it, I believe I have something that may help you. But it can get very in depth if you don't do it correctly.
Sent from my Jelly Bean'd EVO LTE
Click to expand...
Click to collapse
Downgrading the bootloader is one of the few ways to make your phone completely, unusably bricked right? If anyone has a way to downgrade 2.09 to 1.19 SAFELY AND WITHOUT MAKING THE PHONE A PERMANENT PAPERWEIGHT or and preferably, not to mention unlikely, s-off 2.0.9, please share and I will be more pleased than a person who won a million bucks.
got it done!
Thanks to everyone I figured it out! I reflashed with the newer superSu, 3.2. all is good, shows good root, backed up and ready to start geeking!
I have a question that searching around and reading some of the stickied posts hasn't solved.
I have a wind mobile amaze, and recently my camera broke (99% sure it's a hardware problem). I've been using this Energy stock rom for a while now but I want to go to a stock rom before I send it to get repaired. I'm S-on and don't have superCID, so I can't load another carriers RUU, it has to be one from wind. But unfortunately the baseband version was somehow updated when I used the energy ROM:
Baseband: 1.14.550L.17DC_30.78.550L.150
Whenever I use a wind RUU that I got from various locations:
http://www.androidruu.com/?developer=Ruby
http://forum.xda-developers.com/showthread.php?t=1617644&highlight=search+this+forum
forum.xda-developers.com/wiki/HTC_Amaze_4G/ROMs
It always fails the signature check:
Sending OTA_RUBY_ICS_35_S_Globalive_WWE_2.14.1500.6-1.46.1500.3_release_263096ebhdlebyr7k06p6u.zip (renamed as ruu.zip):
Code:
sending 'zip' (133793 KB)...
OKAY [ 14.125s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 33.406s
I made sure the bootloader was relocked, using the amaze all-in-one kit to flash the zip.
Sending the tmobile one with the same baseband version got a lot further:
Sending RUBY_ICS_35_S_TMOUS_2.14.531.3_R2_Radio_1.14.550L.17DC_30.78.550L.15_release_262141_signed.zip (renamed as RUU.zip):
Code:
sending 'zip' (498144 KB)...
OKAY [ 50.458s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 120.731s
But since I don't have superCID it's not going to get past there...
Anyone have any ideas? How did I update the baseband fw originally?
I think I'm in the same boat as you. Trying to get back to stock with a telus amaze. Think I get the same error as you when I try to write it with the all in one tool and when I rename it as PH85IMG or whatever it is the bootloader loads the file, checks it, and then....nothing. I installed a debloated T mobile stock rom a while ago and think that it may have inadvertantly messed with the raidio. If anyone knows if I can just flash the radio .img from recovery and then flash the whole Telus Zip afterward that would be music to my ears. Have already flashed stock Telus recovery but that didn't seem to do anything. Also tried to use the gingerbread executable install but it won't let me install over the hboot as it is too current (Telus ICS hBoot).
you wont have any problems if you're S Off
ravike14 said:
you wont have any problems if you're S Off
Click to expand...
Click to collapse
I was under the impression that I needed to be on stock RUU to s-off properly. Is that not the case? I really don't understand why my bootloader will not install the telus ICS zip to a telus amaze. I have no idea what I'm doing wrong. Again when I to and use flash stock RUU through all in one I get a signature error. So confused. Don't even know where to start now and am not sure what part of my phone has changed that causes the signature failure. Maybe running the mainver Error Fix is the cause of my problems but I have no idea. Right now, I would like to S-off but from what I have read I need to be on stock RUU. So frustrating.
There's a guy in another thread who apparently got S-off while on android revolution. He also has a telus amaze and couldn't get back to stock like me. I pmed him a little while ago for details so I think its doable to s-off even without being on stock ruu. Will update if he responds with an elaboration of exactly what he did. Seems like he was able to s-off and then flash hboot and radio and then ran gingerbread executable and he was back to stock telus. Don't know what you'd have to do to get back to stock wind. If he doesn't respond I'll get you to pm him as well.
If you're S-off then you should be able to go back if you relock your bootloader. Once relocked you should be able to flash the stock image by placing the renamed ruu in the root of your external SD-card and executing fastboot from the bootloader.
My suggestion is to go to the HTC website and search for the latest image. When I downloaded mine the tool there asked for my imei then downloaded the correct image for my phone. I downloaded directly to the external SD-card in my phone to avoid potential checksum errors using my laptop.
I hope this helped
Ciao
mdrv500 said:
There's a guy in another thread who apparently got S-off while on android revolution. He also has a telus amaze and couldn't get back to stock like me. I pmed him a little while ago for details so I think its doable to s-off even without being on stock ruu. Will update if he responds with an elaboration of exactly what he did. Seems like he was able to s-off and then flash hboot and radio and then ran gingerbread executable and he was back to stock telus. Don't know what you'd have to do to get back to stock wind. If he doesn't respond I'll get you to pm him as well.
Click to expand...
Click to collapse
it's because ARHD is a stock based rom by stock they mean one of their official systems they released so you cannot use CM AOSP sense 4 or any kinda rom..but ruu arhd energy should work fine....
Odysseus1962 said:
If you're S-off then you should be able to go back if you relock your bootloader. Once relocked you should be able to flash the stock image by placing the renamed ruu in the root of your external SD-card and executing fastboot from the bootloader.
My suggestion is to go to the HTC website and search for the latest image. When I downloaded mine the tool there asked for my imei then downloaded the correct image for my phone. I downloaded directly to the external SD-card in my phone to avoid potential checksum errors using my laptop.
I hope this helped
Ciao
Click to expand...
Click to collapse
whats from htc? :/
Odysseus1962 said:
If you're S-off then you should be able to go back if you relock your bootloader. Once relocked you should be able to flash the stock image by placing the renamed ruu in the root of your external SD-card and executing fastboot from the bootloader.
My suggestion is to go to the HTC website and search for the latest image. When I downloaded mine the tool there asked for my imei then downloaded the correct image for my phone. I downloaded directly to the external SD-card in my phone to avoid potential checksum errors using my laptop.
I hope this helped
Ciao
Click to expand...
Click to collapse
So the guy got back to me and he was never able to get back to stock. The telus ICS zip does not install from bootloader period as far as we can tell. It seems to require stock telus gingerbread which can only be installed via executable from a pc. Problem is it checks the hboot version (at the very least, never got past this) and will see a newer hboot (from telus OTA ics update) and give an error. So it seems to get back to telus stock you have to S-OFF. Flash older hboot, maybe radio too, and who knows what else. Run gingerbread executable install. Hope it only checks hboot. And the update OTA to telus ICS. I just wanted to get back to stock radio and Rom as I was having problems with earpiece volume. I was pointed to a stock but rooted and deodexed telus ICS Rom which I plan on trying. I'm currently on t mobile stock debloated and its great but the earpiece volume isn't quite where it should be. Pretty close. As for wind guy I'm waiting for him to confirm that you can S-OFF from android revolution and then that may be a path you can take in order to flash radios, hboot, other carrier RUUs. Good luck.
---------- Post added at 11:26 PM ---------- Previous post was at 11:18 PM ----------
To the wind guy as well. If you're sending your phone back to wind I'm pretty sure they will see that you've unlocked the bootloader at some point and that may mean you're warranty is void. Just an fyi. Not sure if unlocking voids your warranty with htc, carrier or both depending on what has gone wrong with the phone.
Also to the guy who suggested I go to the HTC sight I will check that out tomorrow thanks for the tip.
Thanks everyone, since I am on a stock-like ROM I'll trying getting my phone s-off tonight. At that point it shouldn't be too difficult to get back to stock, as the radio FW was my only blocker.
I'll also check out the HTC website, see if there is anything for Wind directly from them.
Have any of you with this issue tried the methods in this thread (first two posts) http://forum.xda-developers.com/showthread.php?t=2167596 or visited the Amaze 4g bible thread here http://forum.xda-developers.com/showthread.php?t=1679486 or the external Amaze bible thread site https://docs.google.com/document/d/...iDtKBuAC9jc/edit?pli=1#heading=h.pb4km6oys1ex ? There is also plenty of useful info on the XDA wiki.
Sorry guys for steering you wrong about the HTC website on one of my previous posts. Unfortunately, my experience has been with the US HTC site going back to my old HD2. I personally went back there to see if I could download the image(s) for your devices and discovered only the US T-Mobile version. Then I went to the Canadian site and found it's set up differently. I could find links for the different Amaze versions that were sold there but I couldn't find links to the respective images like I could on the US site.
On the US site when you click to download the latest ICS image you get taken to a widget that asks for your IEMI (I guess it searches through a database to see if you're legit) then after a few moments the download proceeds as expected. I could find nothing similar after looking around the Canadian site. I'm going to try searching the Int'l site to see if I have better luck.
{
"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"
}
Good news everyone!
I found some time this morning to mess with my phone. Because I was on the energy stock ROM I was able to successfully perform S-off and superCID my amaze. I'm now re-downloading the RUU file for wind stock and going to attempt to flash it again.
Hopefully everything works out. The ideal situation is that this will fix my totally broken camera but I highly doubt that as it appears to be a HW issue. Otherwise going back to stock I should be able to get my phone fixed via warranty (let's hope) and not have too much hassle over that.
Thanks for the help everyone.
Hmm, didn't seem to get anywhere...
I am now S-off (says so in the bootloader), superCID (set to 11111111), and relocked to flash a factory RUU. Unfortunately I'm stuck, my phone displays this warning:
Code:
sending 'zip' (20542 KB)...
OKAY [ 3.154s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 4.011s
I've only tried the wind RUU at this point, I guess I can try a T-mobile one and see if it gives me the same issue.
I`m using the 1.93.0002 HBOOT.
Also I moved the RUU to the ext_sd and renamed to PH85IMG.zip, the bootloader will parse the file but it won`t ask to install it. It just goes back to the main bootloader screen. Not sure what`s up with that, but I`m guessing it`s getting the same error as when I flash using the all-in-one-toolkit...
EDIT:
Ok, ignore that, got it working!
For wind there is NO RUU zip file, there are only RUU exe files and OTA (over the air) update zip files. I was trying to flash a OTA because some other people on this forum said it was possible I think T-mobile is the only carrier that has an actual RUU zip file you can use.
Eventually I took a fairly round-about way to flash the software, but I think all you have to do is:
Make sure you are S-off and superCID.
Run the RUU exe file
Use the 'About Phone>Software Updates' settings menu to get the OTA updates from Wind
Some things to note:
There is only one way to use the OTA zip files: read here
When in superCID you can't unlock your phone again, since you will get a signature check error or something like that. You must load your carrier's CID before unlocking again.
S-off makes everything so much easier!
Some links that helped:
Order in which to get S-off/superCID
SuperCID instructions
[URL="http://forum.xda-developers.com/showthread.php?t=1647728&highlight=return+to+stock]Returning to stock and S-on[/URL]
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
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
Ok I unlocked my loader, then i think what happend was clockwerk installed its self to the boot partition so i was stuck in a loop. I used One_M8_All-In-One_Kit_v to flash a new recovery lower version at that and now i do have a bootable recovery. Problem is now i didn't backup like a dumb arse my working OS and flashed a bad one or maybe the radio or some crap needed to be done first since it was going from 4.4.2 to 5+. In short all i have is recovery and sideload and every rom i download fails to sideload on the phone side and says sucessful on the pc cmd window. Need help with this please
Darthdiddy said:
Ok I unlocked my loader, then i think what happend was clockwerk installed its self to the boot partition so i was stuck in a loop. I used One_M8_All-In-One_Kit_v to flash a new recovery lower version at that and now i do have a bootable recovery. Problem is now i didn't backup like a dumb arse my working OS and flashed a bad one or maybe the radio or some crap needed to be done first since it was going from 4.4.2 to 5+. In short all i have is recovery and sideload and every rom i download fails to sideload on the phone side and says sucessful on the pc cmd window. Need help with this please
Click to expand...
Click to collapse
Wipe data, cache, dalvik, put the appropriate ROM for your carrier/build on SD card or root of internal storage and flash. All else fails run an RUU, bring you back to 100% stock then you can properly reinstall the custom recovery of your choice.
CavyS said:
Wipe data, cache, dalvik, put the appropriate ROM for your carrier/build on SD card or root of internal storage and flash. All else fails run an RUU, bring you back to 100% stock then you can properly reinstall the custom recovery of your choice.
Click to expand...
Click to collapse
I do the proper wipe before flashing my new rom, i'm under the AT&T HTC One M8 section i believe my phone was only @ 4.4.2 before this and here is the bootloader info is :
***Tampered***
***Unlocked***
M8_UL_CA_ PVT SHIP S-On
HBOOT-3.16.0.0000
RADIO-1.16.21331931.LA11G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Apr 18 2014,16:06:33.22985
Tried cm-12-20150131-NIGHTLY-m8 it fails to flash and its on the sd and internal. SkyDragon M8 Sense Rom installs but doesn't boot (tried 2 versions of this rom 700mb and a 1.6gb), believe i tried a couple other roms in my phones section there's only like 9 of them there. I have the stock RUU but fails to detect the phone and fails i think it's meant to sense a turned on functional phone i don't see any kind of recovery method with the stock ruu. All i want is a rom to work with Straight talk the stock os even being unlocked and rooted with su still shoved the default APN down my throat(I even paid 2.99$ for the SQLlite and deleted all other APNs still won't let me check off a APN profile i created as default) making my signal on ST flakey and couldn't get mms to work just picture txting wasn't working. So i went full on like my old HTC One X but dived head first too fast didn't backup my old OS and didn't know firewater was gone till i was at that step of the procedure and it was too late Oh and using TWRP 2.7.1.0 it's the highest i can use before it won't boot.
Darthdiddy said:
I do the proper wipe before flashing my new rom, i'm under the AT&T HTC One M8 section i believe my phone was only @ 4.4.2 before this and here is the bootloader info is :
***Tampered***
***Unlocked***
M8_UL_CA_ PVT SHIP S-On
HBOOT-3.16.0.0000
RADIO-1.16.21331931.LA11G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Apr 18 2014,16:06:33.22985
Tried cm-12-20150131-NIGHTLY-m8 it fails to flash and its on the sd and internal. SkyDragon M8 Sense Rom installs but doesn't boot (tried 2 versions of this rom 700mb and a 1.6gb), believe i tried a couple other roms in my phones section there's only like 9 of them there. I have the stock RUU but fails to detect the phone and fails i think it's meant to sense a turned on functional phone i don't see any kind of recovery method with the stock ruu. All i want is a rom to work with Straight talk the stock os even being unlocked and rooted with su still shoved the default APN down my throat(I even paid 2.99$ for the SQLlite and deleted all other APNs still won't let me check off a APN profile i created as default) making my signal on ST flakey and couldn't get mms to work just picture txting wasn't working. So i went full on like my old HTC One X but dived head first too fast didn't backup my old OS and didn't know firewater was gone till i was at that step of the procedure and it was too late Oh and using TWRP 2.7.1.0 it's the highest i can use before it won't boot.
Click to expand...
Click to collapse
Boot into fastboot, check device manager (if youre on windows) for any unknown drivers and install them if you can. Then run the RUU I posted here http://forum.xda-developers.com/att-htc-one-m8/help/100-stock-4-4-4-ruu-t3017594 which would update you to 4.4.4.
CavyS said:
Boot into fastboot, check device manager (if youre on windows) for any unknown drivers and install them if you can. Then run the RUU I posted here http://forum.xda-developers.com/att-htc-one-m8/help/100-stock-4-4-4-ruu-t3017594 which would update you to 4.4.4.
Click to expand...
Click to collapse
Ok TY i'll try that soon as it downloads, i did finally get RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2
To see the phone and no progress bar shows up on the phone and the program errors out, i even did a full system wipe before i tried it again still to no avail.
CavyS said:
Boot into fastboot, check device manager (if youre on windows) for any unknown drivers and install them if you can. Then run the RUU I posted here http://forum.xda-developers.com/att-htc-one-m8/help/100-stock-4-4-4-ruu-t3017594 which would update you to 4.4.4.
Click to expand...
Click to collapse
Ok tried that stock ruu and it failed i did finally get the phone running on a badseed rom based on 4.4.2 all seems to be working now except i can't send pictures in texts but regular text, calls, and internet work seems to be a common problem with straight talk. So new problem probably a thread somewhere on here about it i'll take a look, thank you for the help
Darthdiddy said:
Ok tried that stock ruu and it failed i did finally get the phone running on a badseed rom based on 4.4.2 all seems to be working now except i can't send pictures in texts but regular text, calls, and internet work seems to be a common problem with straight talk. So new problem probably a thread somewhere on here about it i'll take a look, thank you for the help
Click to expand...
Click to collapse
You'll have to setup your APN and mms message size settings for straight talk, that should fix the text messaging problems.
CavyS said:
You'll have to setup your APN and mms message size settings for straight talk, that should fix the text messaging problems.
Click to expand...
Click to collapse
No matter what message app i try i can't send pictures or large txts my mms is borked and to make matters worse when i installed this rom i must of removed the stock HTC messaging app so i can't find any settings to set the mms size limits. I'd like to figure out how to put the stock messaging app back on the phone without redoing the whole OS
Using Handcent and hangouts and i see no size limit options within the apps or anywhere in the phone settings. Looked up my phone specifically and where the option/s is supposed to be the said section of options is not even there.
If you've got a stock rom downloaded to your computer or sd card you can unzip it and look in system app folder and find the htc messaging apks. Then just install them as system apps and fix permissions.
Sent from my HTC One_M8 using XDA Free mobile app
Before i try and fix my obvious other problems does anyone know how to fix a bad flash of TWRP? I'm used to just adb command line flashing it and never had a issue before on my HTC One X, but seems it a was bad idea and it landed on boot partition and is causing glitches. is there a stock boot i can flash or what do i need?
Darthdiddy said:
but seems it a was bad idea and it landed on boot partition and is causing glitches.?
Click to expand...
Click to collapse
Why do you think that partition, in particular? If you are talking about boot.img, that gets re-flashed any time your flash a ROM.
Try fastboot erase cache, and flash recovery by fastboot. If Clockwork doesn't work, try TWRP.
If you indeed have some corrupted partition(s), your best bet is to RUU. You are non-specific about what error codes, so its hard to help you troubleshoot why the RUU failed. Try a more updated RUU, such as 2.23.
redpoint73 said:
Why do you think that partition, in particular? If you are talking about boot.img, that gets re-flashed any time your flash a ROM.
Try fastboot erase cache, and flash recovery by fastboot. If Clockwork doesn't work, try TWRP.
If you indeed have some corrupted partition(s), your best bet is to RUU. You are non-specific about what error codes, so its hard to help you troubleshoot why the RUU failed. Try a more updated RUU, such as 2.23.
Click to expand...
Click to collapse
Error 155 Unknown Error it says, do i need to relock the bootloader? I could never find a way to S-Off the device so idk if its that or corrupted partition like you said but all my services on my phone crash constantly. But that's better then aokp_task650_m8_kitkat_5.13.2014 that one won't even make it through setup the services crash so often the badseed rom is the only other rom i found that is actually usable. Oh my RUU is 2.0.16 how can i find the newest one for my HTC One M8?
Darthdiddy said:
Error 155 Unknown Error it says, do i need to relock the bootloader?
Oh my RUU is 2.0.16 how can i find the newest one for my HTC One M8?
Click to expand...
Click to collapse
You always need to relock the bootloader to run RUU with s-on. No exceptions.
Hopefully this will clear up your RUU problem, although the RUU number you just supplied above doesn't make any sense (doesn't correspond to any RUU for this device) Where did you find it, and its not what you referenced in Post #5 above.
CavyS already supplied a link for the "latest" AT&T RUU in Post #4 above. Although be aware, that if you are successful in running the latest RUU, it will render sunshine unable to achieve s-off. I suggest RUU to 1.58 or 2.23 (if you want s-off), as those should still be supported by sunshine.
Darthdiddy said:
I could never find a way to S-Off the device
Click to expand...
Click to collapse
Did you try sunshine? Its the only way to s-off at this time.
redpoint73 said:
You always need to relock the bootloader to run RUU with s-on. No exceptions.
Hopefully this will clear up your RUU problem, although the RUU number you just supplied above doesn't make any sense (doesn't correspond to any RUU for this device) Where did you find it, and its not what you referenced in Post #5 above.
CavyS already supplied a link for the "latest" AT&T RUU in Post #4 above. Although be aware, that if you are successful in running the latest RUU, it will render sunshine unable to achieve s-off. I suggest RUU to 1.58 or 2.23 (if you want s-off), as those should still be supported by sunshine.
Did you try sunshine? Its the only way to s-off at this time.
Click to expand...
Click to collapse
Relocked and flashed the ruu utility version said 2.0.16.2014 and is KK 4.4, idk about sunshine as to reading about people with my phone and it not working so for a 25$ leap of faith not sure what to do about that. My phone is running perfect now in a locked down carrier branded and bloatware way lol. Thanks guys, anyway i can tell if sunshine will work on my phone?
Darthdiddy said:
Relocked and flashed the ruu utility version said 2.0.16.2014 and is KK 4.4
Click to expand...
Click to collapse
I think that is the version of the actual installer software (.exe) not the ROM version it will install on your phone. Kitkat for AT&T would be either 1.58 or 2.23. That number will be in the actual file name of the RUU, so just look there (actually a much longer string of numbers starting with 1.58 or 2.23, but I've abbreviated them for convenience).
Darthdiddy said:
idk about sunshine as to reading about people with my phone and it not working so for a 25$ leap of faith not sure what to do about that. My phone is running perfect now in a locked down carrier branded and bloatware way lol. Thanks guys, anyway i can tell if sunshine will work on my phone?
Click to expand...
Click to collapse
You install the sunshine APK, run it, and sunshine will tell you whether it can s-off the phone or not. You won't be charged unless it can successfully s-off the phone. I haven't heard of any folks here that got charged, and sunshine couldn't s-off the device.
redpoint73 said:
I think that is the version of the actual installer software (.exe) not the ROM version it will install on your phone. Kitkat for AT&T would be either 1.58 or 2.23. That number will be in the actual file name of the RUU, so just look there (actually a much longer string of numbers starting with 1.58 or 2.23, but I've abbreviated them for convenience).
You install the sunshine APK, run it, and sunshine will tell you whether it can s-off the phone or not. You won't be charged unless it can successfully s-off the phone. I haven't heard of any folks here that got charged, and sunshine couldn't s-off the device.
Click to expand...
Click to collapse
Wow thanks for the info! Before i try this can after S-OFF/rooting/SU can i install the unlocked/developer ruu from HTC and get HTC OTA and get away from this bloated carrier branded crap? So much in the forums and i can't find a answer to this question anywhere.