I backed up my phone and have had troubles restoring a rom, although I don't have access to it at the moment, if I restore a backup I made with htc sync manager will it restore the rom I had? and if not, I've had troubles installing a rom with a .zip, because every rom I find is for a different bootloader (I have 1.6) and .exe's fail because my bootloader is unlocked. if I relock it should the .exe work regardless of the bootloader version. if neither of these would work, what do you suggest I do? I'd send it in to htc but they estimated $220, then another person said $290 is average, but it could be up to $350 just to fix it, and at that price I could almost buy another (sorry if these are easy questions)
In order for someone to help, you should post the rom your on, whether your s-on or s-off, and what recovery you're using.
Evan092 said:
I've had troubles installing a rom with a .zip, because every rom I find is for a different bootloader (I have 1.6)
Click to expand...
Click to collapse
I think you mean hboot 3.16, as "1.6" is not a valid hboot number for this device.
There are ROMs for every hboot number.
Evan092 said:
.exe's fail because my bootloader is unlocked. if I relock it should the .exe work regardless of the bootloader version.
Click to expand...
Click to collapse
If you are s-on, the RUU will always fail with an unlocked bootloader.
Will it work regardless of hboot number? Technically no (although in your specific case, its sort of "yes"). The hboot number of the RUU needs to be equal and greater than what is on the phone. But as it appears you have hboot 3.16 on the phone, any correct RUU for AT&T will meet this requirement, as all official AT&T RUUs are that version or newer. But it must be an RUU for your version (AT&T) of the M8.
Evan092 said:
I'd send it in to htc but they estimated $220, then another person said $290 is average, but it could be up to $350 just to fix it, and at that price I could almost buy another (sorry if these are easy questions)
Click to expand...
Click to collapse
If the phone simply isn't working/booting due to attempted mods; I'd say its not necessary to send in for repairs. I think we can get the phone up and running again. It just sounds like you tried some mods, and not completely familiar with the processes, concepts, etc.
In addition to the info posted in the reply above, also explain in detail what you have done to get to this point. Its not even clear what state the phone is in. But if you are considering sending in for repair, I assume this means the phone won't boot.
redpoint73 said:
I think you mean hboot 3.16, as "1.6" is not a valid hboot number for this device.
There are ROMs for every hboot number.
If you are s-on, the RUU will always fail with an unlocked bootloader.
Will it work regardless of hboot number? Technically no (although in your specific case, its sort of "yes"). The hboot number of the RUU needs to be equal and greater than what is on the phone. But as it appears you have hboot 3.16 on the phone, any correct RUU for AT&T will meet this requirement, as all official AT&T RUUs are that version or newer. But it must be an RUU for your version (AT&T) of the M8.
If the phone simply isn't working/booting due to attempted mods; I'd say its not necessary to send in for repairs. I think we can get the phone up and running again. It just sounds like you tried some mods, and not completely familiar with the processes, concepts, etc.
In addition to the info posted in the reply above, also explain in detail what you have done to get to this point. Its not even clear what state the phone is in. But if you are considering sending in for repair, I assume this means the phone won't boot.
Click to expand...
Click to collapse
I relocked the bootloader and ran the RUU I downloaded right off of the htc website and it worked, thanks for the help
Evan092 said:
thanks for the help
Click to expand...
Click to collapse
You're welcome, and there's a button for that.
Related
Hey all,
So I'm sending my Rezound back to Verizon as a warranty replacement, and today I tried to revert it to stock. It was rooted, S-OFF, with Infected ROM installed (based off CM10.1.2). However, the re-lock process didn't work correctly. I received the below error in the command prompt when I tried to relock it with fastboot oem lock:
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
FAILED (status read failed (Too many links))
The steps I took are as follows:
1) Re-installed RUU using this file: Rezound_Global_ICS_4.03.605.2_Full_RUU_PH98IMG (renamed to PH98IMG and done through bootloader)
2) Attempted fastboot oem lock (and got the above error)
This process worked on a different Rezound that I also received as a warranty replacement which itself was also defective, but in that case I locked the phone first and THEN flashed the RUU. In my haste today I accidentally flipped the order to what you see above.
Now, the phone will not go back to ***LOCKED*** up at the top. Instead, it says ***RELOCKED*** which is not what I want here. I am afraid to set the S-OFF flag back to ON while the phone is displaying "relocked". The RUU did work, as the phone has stock firmware on it once again and boots up fine. I attempted to relock it again and RUU it again with the same results, still got the above error and still showing ***RELOCKED***.
I did some research but couldn't find anything specific to the Rezound; the nearest thing I was able to find was some info about how CleanROM can cause this on a different device, and something about mainver, which I'm not familiar with. I did use CleanROM for nearly a year before going S-OFF and moving to CM10. If anyone has an idea on how to fix it I would be eternally grateful.
tigerxchaos said:
Hey all,
So I'm sending my Rezound back to Verizon as a warranty replacement, and today I tried to revert it to stock. It was rooted, S-OFF, with Infected ROM installed (based off CM10.1.2). However, the re-lock process didn't work correctly. I received the below error in the command prompt when I tried to relock it with fastboot oem lock:
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
FAILED (status read failed (Too many links))
The steps I took are as follows:
1) Re-installed RUU using this file: Rezound_Global_ICS_4.03.605.2_Full_RUU_PH98IMG (renamed to PH98IMG and done through bootloader)
2) Attempted fastboot oem lock (and got the above error)
This process worked on a different Rezound that I also received as a warranty replacement which itself was also defective, but in that case I locked the phone first and THEN flashed the RUU. In my haste today I accidentally flipped the order to what you see above.
Now, the phone will not go back to ***LOCKED*** up at the top. Instead, it says ***RELOCKED*** which is not what I want here. I am afraid to set the S-OFF flag back to ON while the phone is displaying "relocked". The RUU did work, as the phone has stock firmware on it once again and boots up fine. I attempted to relock it again and RUU it again with the same results, still got the above error and still showing ***RELOCKED***.
I did some research but couldn't find anything specific to the Rezound; the nearest thing I was able to find was some info about how CleanROM can cause this on a different device, and something about mainver, which I'm not familiar with. I did use CleanROM for nearly a year before going S-OFF and moving to CM10. If anyone has an idea on how to fix it I would be eternally grateful.
Click to expand...
Click to collapse
You need to get ahold of either the ph98img.zip for 3.14.605.12 like HERE and put it on your sd card and run that at hboot after renaming it ph98img.zip or get a copy of the full RUU (RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe) for 3.14.605.12 at ONE OF THESE LINKS and run this on your pc with the phone connected by the USB cable. Make sure on the exe version that you have USB debugging enabled. The RUU you used is a leak and not an "official" full RUU. You need to run a full official RUU to accomplish what you want and the full RUU for 4.05.605.14 has not been released yet. If you use either of the ones I provided links for, the hboot will show "locked" but an earlier version. Then if you want it to show the latest version, leave your SIM card in the phone, let it bootup, when the setup starts, just press the home key and it will bypass setup. The get into settings and into the software update and run that. It will update to the next version. Let it reboot and again bypassing the setup. Then run software update one more time and you will have 4.05.605.14 which is the latest version and your hboot will now show locked. Now you can go ahead and re S-on the phone.
However, I have heard over and over that Verizon never checks the software on the phones and you could just send it back the way it is now. But I'm sure that you are paranoid about this like I am and want it fully stock again so there are no red flags...
mikeyk101 said:
You need to get ahold of either the ph98img.zip for 3.14.605.12 like HERE and put it on your sd card and run that at hboot after renaming it ph98img.zip or get a copy of the full RUU (RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe) for 3.14.605.12 at ONE OF THESE LINKS and run this on your pc with the phone connected by the USB cable. Make sure on the exe version that you have USB debugging enabled. The RUU you used is a leak and not an "official" full RUU. You need to run a full official RUU to accomplish what you want and the full RUU for 4.05.605.14 has not been released yet. If you use either of the ones I provided links for, the hboot will show "locked" but an earlier version. Then if you want it to show the latest version, leave your SIM card in the phone, let it bootup, when the setup starts, just press the home key and it will bypass setup. The get into settings and into the software update and run that. It will update to the next version. Let it reboot and again bypassing the setup. Then run software update one more time and you will have 4.05.605.14 which is the latest version and your hboot will now show locked. Now you can go ahead and re S-on the phone.
However, I have heard over and over that Verizon never checks the software on the phones and you could just send it back the way it is now. But I'm sure that you are paranoid about this like I am and want it fully stock again so there are no red flags...
Click to expand...
Click to collapse
Thanks very much for the suggestion. I'll give this a try shortly.
It's just weird that this RUU successfully took another phone back to fully stock. The only difference between the two is that the other phone never had CleanROM installed on it.
EDIT: Just realized one other thing, at one point I manually updated the radios on the first phone (the one that is now giving me trouble) but didn't do this on the one that went back to stock properly. I'm going to give the PC method a try since it mentions the radios in the file name.
Sent from my SCH-I535 using xda app-developers app
Went ahead and ran the full RUU from my PC as suggested above. Unfortunately it didn't accomplish the goal. The RUU completed successfully, but HBOOT still says ***RELOCKED***. I tried unlocking and then relocking again, and got the same error:
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
FAILED (status read failed (Too many links))
finished. total time: 0.958s
Not sure where to go from here.
With S-off, the radios shouldnt matter. Seems to me when I s-offed this latest phone, it was on 4.05.605.14 and I had to unlock the bootloader to do the s-off. After I achieved s-off, I dont remember relocking, I just ran that ph98img from android police. The bootloader then displayed that it was locked. Maybe try to run either of those RUUs after unlocking the bootloader.
mikeyk101 said:
With S-off, the radios shouldnt matter. Seems to me when I s-offed this latest phone, it was on 4.05.605.14 and I had to unlock the bootloader to do the s-off. After I achieved s-off, I dont remember relocking, I just ran that ph98img from android police. The bootloader then displayed that it was locked. Maybe try to run either of those RUUs after unlocking the bootloader.
Click to expand...
Click to collapse
I think the key is this error I'm getting via the command line. I didn't get it with the other phone and on that one, after I relocked, it said **TAMPERED** across the top; after the RUU, it just said **LOCKED**. This one is saying **RELOCKED** instead of **TAMPERED** and it's the one that won't go back to locked after a RUU. If we can figure out what's causing this error, might be the key to solving the issue. However, that's where I'm falling short in my research.
tigerxchaos said:
I think the key is this error I'm getting via the command line. I didn't get it with the other phone and on that one, after I relocked, it said **TAMPERED** across the top; after the RUU, it just said **LOCKED**. This one is saying **RELOCKED** instead of **TAMPERED** and it's the one that won't go back to locked after a RUU. If we can figure out what's causing this error, might be the key to solving the issue. However, that's where I'm falling short in my research.
Click to expand...
Click to collapse
IIRC, when it says Tampered across the top of the bootloader, it just means that the bootloader is unlocked and that a other than factory recovery has been installed such as TWRP or AmonRa. Relocked means that the bootloader had originally been unlocked at some point and then locked again. If it were me, I would
1. Try to unlock the bootloader again,
2. Reinstall either AmonRa or TWRP if either is not there, then
3. Wipe everything such as cache, dalvik cache, wipe ALL data/factory reset, and possibly even wipe system.
(Normally you would not want to wipe system because pretty much everything is then gone but since you have the RUU.exe, you have the means to reinstall the original OS.)
4. After wiping everything above, reboot from recovery to bootloader and try running that RUU again.
You are right though and this is weird. Normally when you run a full factory RUU, it should reset EVERYTHING back to factory original condition.
BTW, I have just been trying to come up with a workable solution. I was kind of hoping that someone with more experience would pipe in. Unfortunately it looks like the Rezound and development is dying a slow but sure death and many have moved on...
Just trying to think of alternate solutions again, I know that it is possible to change just the hboots by using the proper ph98img.zip files. I remember using one awhile back when I was unlocked that changed the hboot from tampered to read locked. I cant find the thread but I think it came from Vinylfreak . I attached it in this post but it will read 2.27.0000 as the version. I have also included the factory 2.28.0000 in a separate ph98img file below. Maybe try one of these and it might take care of it. Put these on your sd card, change the name of the first one to ph98img.zip and get into the bootloader hboot and let it update. If that doesn't work, try the second one.
If needed, I could also probably make one for the 3.05.605.12 and upload that as well. I just need to check the hboot version it came with.
ETA, I think the first one came from THIS THREAD and it is just renamed by me so I could keep track of what it was...
mikeyk101 said:
Just trying to think of alternate solutions again, I know that it is possible to change just the hboots by using the proper ph98img.zip files. I remember using one awhile back when I was unlocked that changed the hboot from tampered to read locked. I cant find the thread but I think it came from Vinylfreak . I attached it in this post but it will read 2.27.0000 as the version. I have also included the factory 2.28.0000 in a separate ph98img file below. Maybe try one of these and it might take care of it. Put these on your sd card, change the name of the first one to ph98img.zip and get into the bootloader hboot and let it update. If that doesn't work, try the second one.
If needed, I could also probably make one for the 3.05.605.12 and upload that as well. I just need to check the hboot version it came with.
ETA, I think the first one came from THIS THREAD and it is just renamed by me so I could keep track of what it was...
Click to expand...
Click to collapse
Thanks again for all your suggestions, you've been REALLY helpful.
I'll try out the hboot method you listed above and see what I can come up with. My concern there is that I think vinylfreak's hboot was an engineering hboot, which will brick the phone if I try to go back to S-ON with it installed.
Rezound development is actually still alive and well, among several dedicated developers who are working on some great software for the phone. @Flyhalf205 has been releasing regular updates to his Rezound build of CyanogenMod 10.1 and as I understand it, is responsible for a ton of the recent progress made on bringing Jellybean to the Rezound. @IAmTheOneTheyCallNeo has a fantastic ROM based off of CM called Infection, and a variant of it based on PACMan called Tron. @iHateWebOS has a great kernel called HIRO, @Snuzzo has another one called Funky Kernel, and there are other devs that I'm less familiar with working on other projects. Check out their work, it breathed new life into my phone.
tigerxchaos said:
Thanks again for all your suggestions, you've been REALLY helpful.
I'll try out the hboot method you listed above and see what I can come up with. My concern there is that I think vinylfreak's hboot was an engineering hboot, which will brick the phone if I try to go back to S-ON with it installed.
Rezound development is actually still alive and well, among several dedicated developers who are working on some great software for the phone. @Flyhalf205 has been releasing regular updates to his Rezound build of CyanogenMod 10.1 and as I understand it, is responsible for a ton of the recent progress made on bringing Jellybean to the Rezound. @IAmTheOneTheyCallNeo has a fantastic ROM based off of CM called Infection, and a variant of it based on PACMan called Tron. @iHateWebOS has a great kernel called HIRO, @Snuzzo has another one called Funky Kernel, and there are other devs that I'm less familiar with working on other projects. Check out their work, it breathed new life into my phone.
Click to expand...
Click to collapse
I didn't quite elaborate on what I was thinking. But you are absolutely correct about doing S-on with an engineered hboot and that it would brick it. However, since it is going back as a warranty replacement, maybe bricking it might not be such a bad idea. LOL. I should have added that by using the fake locked hboot, it may trick the phone into thinking it really was locked. And then flash the second one and the banner just might stay showing locked. I have actually gone back and forth between the two but have always been locked so I am not sure how yours would work out. BTW, that second one is the original factory hboot extracted off the full OTApkg.zip for 4.05.605.14 and packaged in a ph98img file. I extracted it in the event that I might have to S-on again sometime in the future. I also extracted the original factory recovery and packaged that in a ph98img file as well in case I ever had to revert back to stock for the same reason. I just have to unroot (I am using supersu), reinstall the factory recovery, reinstall the factory hboot, do a factory wipe in recovery and finally do the write secure flag command and I am golden. I know that there are still many very cool roms out there. I used to be a big fan of CleanROM but that is no longer supported by the developer. Since then I have gotten kind of used to using a rooted stock rom. I know I may be missing some bells and whistles but I mostly rooted and S-offed just because I could and have a few more choices available to me. I hope you are able to find a solution.
I had this happen a wile ago what worked for me was that I ran the ruu to back to stock, then go through the unlock process, once unlocked s-off. Once s-off run ruu, then follow directions in this link http://forum.xda-developers.com/showthread.php?t=1612937
Sent from my Infected Rezound using xda app-developers app
If the bootloader is locked, htc stock recovery is installed, and phone is not rooted but it is s-off, will the phone function normally? Like receive Ota from htc and behave like a brand new out of the box unmodified htc one m8? Planning on selling it so I want to know.
Sent from my Oneplus One using XDA Free mobile app
Shouldnt be an issue as long as completely stock rom/recovery
If any system files were altered with root, they need to be restored to stock to get OTA. RUU (available for AT&T version) back to stock is probably the best way to get it close to stock as possible.
Also, you need to tell the buyer the phone is s-off, as selling an s-off phone to an unsuspecting buyer is not a good idea (also that it was bootloader unlocked, even if returned to LOCKED).
redpoint73 said:
If any system files were altered with root, they need to be restored to stock to get OTA. RUU (available for AT&T version) back to stock is probably the best way to get it close to stock as possible.
Also, you need to tell the buyer the phone is s-off, as selling an s-off phone to an unsuspecting buyer is not a good idea (also that it was bootloader unlocked, even if returned to LOCKED).
Click to expand...
Click to collapse
Well I restored to htc sense nandroid and reset the phone. Only thing is the software buttons are stock android and not htc. It is unrooted and the bootloader saids locked not relocked. It is still s-off I didn't want to do ruu because if everything is not 100% stock the phone could brick
Sent from my Oneplus One using XDA Free mobile app.
patstar5 said:
It is still s-off I didn't want to do ruu because if everything is not 100% stock the phone could brick
Click to expand...
Click to collapse
Where did you hear that? I do not think that is true.
redpoint73 said:
Where did you hear that? I do not think that is true.
Click to expand...
Click to collapse
I heard that if it was not 100% stock it would through a red flag..... Or maybe that was turning it s-on? Well I have it listed on eBay already. Everything is stock except software buttons for some reason
Sent from my Oneplus One using XDA Free mobile app.
patstar5 said:
I heard that if it was not 100% stock it would through a red flag..... Or maybe that was turning it s-on?
Click to expand...
Click to collapse
Its not true. You can RUU away. It returns everything to stock except S-off, and UNLOCKED, RELOCKED banner.
redpoint73 said:
Its not true. You can RUU away. It returns everything to stock except S-off, and UNLOCKED, RELOCKED banner.
Click to expand...
Click to collapse
Cam you do ruu rooted and unrooted? The bootloader is locked.
Sent from my Oneplus One using XDA Free mobile app.
patstar5 said:
Cam you do ruu rooted and unrooted? The bootloader is locked.
Click to expand...
Click to collapse
Doesn't matter if the phone is rooted or not, the RUU will still run.
Bootloader needs to be locked or relocked for the RUU to run, unless you are s-off (RUU will not run with bootloader unlocked).
Of course, the RUU also needs to be the right carrier version (CID), and you can't "downgrade" or run a former RUU version than is on the phone (these restrictions are also bypassed by s-off).
Those are basically the only restrictions on running RUU.
There have been some isolated incidents on other devices where mods caused issues with RUU; so this may be what you have read. For instance, on the One X (EVITA) the Jellybean RUU bricked the device if SuperCID was present and S-on. But this was a bug, and not typical of how RUU works (basically a rare exception to the rule). I haven't heard of any such thing on the M8.
Or you may be thinking of OTA, which is a completely different case. For OTA, stock recovery needs to be present, and if any system files were altered by root, OTA will not install (although presence of root itself will not cause it to fail). AFAIK from reports here, OTA will install whether the bootloader is locked or not.
redpoint73 said:
Doesn't matter if the phone is rooted or not, the RUU will still run.
Bootloader needs to be locked or relocked for the RUU to run, unless you are s-off (RUU will not run with bootloader unlocked).
Of course, the RUU also needs to be the right carrier version (CID), and you can't "downgrade" or run a former RUU version than is on the phone (these restrictions are also bypassed by s-off).
Those are basically the only restrictions on running RUU.
There have been some isolated incidents on other devices where mods caused issues with RUU; so this may be what you have read. For instance, on the One X (EVITA) the Jellybean RUU bricked the device if SuperCID was present and S-on. But this was a bug, and not typical of how RUU works (basically a rare exception to the rule). I haven't heard of any such thing on the M8.
Or you may be thinking of OTA, which is a completely different case. For OTA, stock recovery needs to be present, and if any system files were altered by root, OTA will not install (although presence of root itself will not cause it to fail). AFAIK from reports here, OTA will install whether the bootloader is locked or not.
Click to expand...
Click to collapse
OK, where do I get the ruu at? From htc's site? Att m8 also how do I run it?
Sent from my Oneplus One using XDA Free mobile app.
patstar5 said:
OK, where do I get the ruu at? From htc's site? Att m8 also how do I run it?
Click to expand...
Click to collapse
RUU is here, near the bottom of the page, see "Manual system update instructions": http://www.htc.com/us/support/htc-one-m8-att/news/
The link gives step-by-step instructions, but RUU is just a .exe program (PC required) you run with the phone connected, the application will pretty much walk you through after that.
Although it was reported by several users last week, the file would not download to completion. One XDA user contacted HTC, who said they would look into it, so hopefully the issue has been fixed. I believe another XDA user posted the file for download, if you search around (if the official download is still broken).
Or you can also try the bootable RUU posted here, which does not require PC: http://forum.xda-developers.com/att-htc-one-m8/general/att-1-58-501-1-bootable-ruu-hboot-t2818556
I'm rooted and have an unlocked bootloader, but cannot s-off. Are there any roms out there that I can flash and still have s-on? If so, can you list them for me please or better yet can you give me the best one so I can be on my way?
RBrown1093 said:
I'm rooted and have an unlocked bootloader, but cannot s-off. Are there any roms out there that I can flash and still have s-on? If so, can you list them for me please or better yet can you give me the best one so I can be on my way?
Click to expand...
Click to collapse
What are your hboot and radio numbers?
If you tried firewater to s-off, make sure you are on stock ROM and kernel, and try a few times. But you will most like need sunshine to s-off, and it should work with the AT&T version.
Hboot: 3.16.0.0000
Radio: 1.16.21331931
RBrown1093 said:
Hboot: 3.16.0.0000
Radio: 1.16.21331931
Click to expand...
Click to collapse
You can use Sense ROMs that are based on 1.x software, and probably most or all AOSP ROMs (but probably not GPE).
Alternately, you can s-off, update your firmware and flash anything (meant for the M8).
Another option, you can update to software 2.x by OTA or RUU, which will also update your firmware to be able to run any Sense software 2.x ROMs. And you can wait for the official 3.x OTA or RUU (mid-December) which will similarly update your to current firmware, and allow you to flash anything (meant for the M8).
I tried to s-off, but after I do the adb reboot my laptop doesn't latch back onto the phone after I enter the second command in. Something has to be wrong, and I don't know what.....
RBrown1093 said:
I tried to s-off, but after I do the adb reboot my laptop doesn't latch back onto the phone after I enter the second command in. Something has to be wrong, and I don't know what.....
Click to expand...
Click to collapse
Any response if you type the command:
adb devices
This should return your unique device ID (which I think is your serial number, so don't post it). I don't need to know what it is, just that you got a response and not a blank space.
I've gotten as far as pushing the firewater file to my device, and when it started chugging water, I later got the message saying no matter how many times you reflash or ruu, it won't s-off..... Wtf
RBrown1093 said:
I've gotten as far as pushing the firewater file to my device, and when it started chugging water, I later got the message saying no matter how many times you reflash or ruu, it won't s-off..... Wtf
Click to expand...
Click to collapse
Just get sunshine, it's free to download, and if the compatability test says it will work, pay the $25 to get it. If not, you can't s-off. Firewater and sunshine are the only way to s-off.
RBrown1093 said:
I've gotten as far as pushing the firewater file to my device, and when it started chugging water, I later got the message saying no matter how many times you reflash or ruu, it won't s-off..... Wtf
Click to expand...
Click to collapse
If it doesn't work, it doesn't work. I said try it a few times, and if it still fails, use sunshine.
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.
OK. So I have no idea how I did it but I have succeeded in bricking my M8. Here are the basics:
- Rooted, was running Cyanogen 12
- TWRP is installed and I can get access to it.
- S-On....seems that I cannot get to S-Off at this point
- Have read thru multiple threads, downloaded an RUU that purports to be GPE, but I have not been able to get it to run.
- Am in the process of downloading a stock Lollipop 5.1 OS.
At this point I am at a loss on how to get an OS installed and running. Suggestions would be appreciated.
Many thanks
hillsboro said:
OK. So I have no idea how I did it but I have succeeded in bricking my M8.
Click to expand...
Click to collapse
The screen comes on, so the phone is not truly bricked, and is recovable. Brick means the phone is not recoverable without opening it up (and either JTAG or new motherboard) and this thread would have no purpose.
What you have here is simply a failure to know how to properly recover.
You say you don't know how you got to this condition. But there must have been some step/events which led to no OS. Recall them and tell us, as best you can. Its much harder for folks to help, if we can't determine what you did to the phone.
hillsboro said:
- S-On....seems that I cannot get to S-Off at this point
Click to expand...
Click to collapse
True, the only working s-off method is sunshine, which requires a working OS. But you don't need to s-off to recover.
hillsboro said:
- Have read thru multiple threads, downloaded an RUU that purports to be GPE, but I have not been able to get it to run.
Click to expand...
Click to collapse
You can't just run any RUU. With s-on, you can only run an AT&T RUU. And it needs to be equal or greater firmware number (hboot, radio, etc.) than what is on the phone (no "downgrading").
If you downloaded the GPE ROM from the XDA thread, it clearly indicates that s-off is needed. So of course it won't work.