So, my HTC One M8 is still on CM11, with S-On and rooted with TWRP installed. I have tried to update CM and it fails every time. I tried to revert back to stock by using HTC's RUU, but it fails every time and when it does I lose cell service and WiFi capability. I have Factory reset, which has restored my Cell service and WiFi, but I am still runing CM11. I have watched countless videos and tried to follow guides on how to revert but I simply cannot find one that's up to date, and on XDA I can't find the one pertanent to my CID Num, CWS__001. I am desperate and I really would just like to be on stock Rom again, is there anything that I can do? Does anyone have an idea of what can be done to revert?
You can't just run any RUU. The RUU has to match your CID and MID. In your case, it needs to be the AT&T RUU. If s-on, you also have to relock the bootloader to run the RUU. Also, the RUU needs to be greater or equal firmware version than what is currently on the phone (no "downgrading" allowed with s-on).
Find the AT&T RUUs in my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432&page=6
Also, CM12 requires a certain hboot (I believe 3.19) in order to install. So if your hboot is older, that is probably why CM12 is not installing. The RUU will fix that. But you will then need to unlock the bootloader again, and re-install custom recovery, in order to be able to flash CM12.
Related
i've been wondering if anyone else has been having any issues with mean rom ics, i've flashed it twice, and even done a full wipe and everything. but it seems every time i restart (or the phone powers down) i go through about 6 - 10 crashes before it can run stable enough for me to use it at all. has anyone else had this issue or have this issue and can shed any light on what could be causing it?
Strange. Are you s-on or s-off?
Read, Search, Read again, ... Then Ask with Tapatalk 2
Im s-off via Juopunutbear. My phone came with bootloader 1.50 but I updated for ics using what was posted Here, so I could retain s-off
I was having some odd things happen when I first moved to MeanROM 2.6 as well so I flashed the 2.89 RUU when it became available to make sure that the software and firmware were completely in sync. That's pretty easy to do if you are S-OFF since all you have to do is connect your phone to a Windows PC and run the RUU.exe, then flash a custom recovery and optionally a different bootloader.
Things seem to be a little smoother for me after flashing the 2.89 RUU as a base.
ramjet73
ramjet73 said:
I was having some odd things happen when I first moved to MeanROM 2.6 as well so I flashed the 2.89 RUU when it became available to make sure that the software and firmware were completely in sync. That's pretty easy to do if you are S-OFF since all you have to do is connect your phone to a Windows PC and run the RUU.exe, then flash a custom recovery and optionally a different bootloader.
Things seem to be a little smoother for me after flashing the 2.89 RUU as a base.
ramjet73
Click to expand...
Click to collapse
but isn't flashing via bootloader the firmware bits doing (the long-ish way) the same thing as what the RUU would do? I'm still on the stock HTC bootloader for 1.58 because i was updated to it from the firmware bits, but if the RUU does something extra then maybe i would benefit from flashing with it. but i mean i also have MIUI 2.8.17 and i installed it (after i was able to use my phone) through boot manager a few weeks after installing MeanROM and booting to it yields me no issues of crashing or anything. do note its based off (supposedly) the GSM port for the E3D as well as files from the sprint/htc ICS release
AlexxSeven said:
but isn't flashing via bootloader the firmware bits doing (the long-ish way) the same thing as what the RUU would do? I'm still on the stock HTC bootloader for 1.58 because i was updated to it from the firmware bits, but if the RUU does something extra then maybe i would benefit from flashing with it. but i mean i also have MIUI 2.8.17 and i installed it (after i was able to use my phone) through boot manager a few weeks after installing MeanROM and booting to it yields me no issues of crashing or anything. do note its based off (supposedly) the GSM port for the E3D as well as files from the sprint/htc ICS release
Click to expand...
Click to collapse
There's no guaranty that flashing the RUU will fix anything but it did seem to help on my phone. The RUU flashes both the stock ROM and all the firmware, including the bootloader, so it makes your phone 100% stock except for the S-ON/S-OFF radio security and bootloader locked/unlocked status. It won't change either of those, but you must have your bootloader locked (or relocked) to run the RUU if S-ON.
After running the RUU.exe you can flash a custom recovery and bootloader if you want. It should be the same as returning to stock and taking the OTA update, but flashing the RUU.exe is faster and easier.
ramjet73
Hboot 1.5 s-on and I'm running meanrom ICS 2.6 .
I did the HTC unlock. Then installed Su zip from this site. Then I installed 4ext and rebooted into recovery...flashed the meanrom zip (it flashed the kernel that comes w the Rom ) and that was it. Now I'm on sw 2.89 build w the 3.0.16 kernel and like I said still s off and hboot 1.5
If anyone knows any where to get a kernel to overclock please let me know
Sent from my PG86100 using xda app-developers app
ramjet73 said:
There's no guaranty that flashing the RUU will fix anything but it did seem to help on my phone. The RUU flashes both the stock ROM and all the firmware, including the bootloader, so it makes your phone 100% stock except for the S-ON/S-OFF radio security and bootloader locked/unlocked status. It won't change either of those, but you must have your bootloader locked (or relocked) to run the RUU if S-ON.
After running the RUU.exe you can flash a custom recovery and bootloader if you want. It should be the same as returning to stock and taking the OTA update, but flashing the RUU.exe is faster and easier.
ramjet73
Click to expand...
Click to collapse
i actually decided to give it a try after making a nand backup ofc, and still had the same issues :s after re-flashing from my backup though it seems to boot fairly stable now. even between switching roms im not sure exactly why but could it have been an issue with anything that is permanent between any rom?
OK so I've tried googling and all that but this problem doesn't seem to be as common as the mainver is older issue.
Background:
Just sold the phone on swappa but I need to return to stock before I send it, hopefully tomorrow. I was s on running neo 1.7 before I got into this mess.
Issue:
I booted into recovery and did a factory reset. I then booted into hboot and did a factory reset there also. I think I then selected the wipe internal storage option. I then proceeded to relock the bootloader which I believe was successful since it says relocked now.
I have downloaded and tried flashing 3 different ICS RUUs by renaming them to the appropriate phxxx name and flashing them in hboot. It goes thru the process a little ways and then all of a sudden I get the "hboot is older" error and "update failed" message. My Hboot version is showing 2.27 which i believe is the newest one. I can't do anything and can't find a solution. I really need to figure out how to fix this asap so I can get the buyer his phone. All help is greatly appreciated!
It is impossible to downgrade HBoot without S-Off, so you will only be able to run an RUU with HBoot version 2.27 or higher (I believe that's either the ICS OTA or the Global leak - correct me if I'm wrong).
To get completely stock, i.e., stock firmware and Locked (as opposed to Relocked), you will need to get S-Off, then flash whatever RUU you want, then get S-On again.
However, just flashing any RUU - either the ICS OTA or the Global leak, and staying Relocked should be fine - many people receive used phones with custom ROMs and all, so an RUU would be a big step up from that (in terms of being as stock as possible).
EDIT: as LOBBS said (below), you will need to run the Global Leak RUU. That will get you on the latest leaked firmware / radios, which is probably the best anyway if you are selling the phone to the 'average', uninformed user (or to the informed user, for that matter). You will have Relocked bootloader.
Alternatively, you could get S-Off and then get on stock firmware / radios, Locked bootloader, and back to S-On, but I assume you won't want to bother to do all that just to sell the phone.
Hboot 2.27 is the global leak RUU 4.03.605.
Sent from my ADR6425LVW using xda app-developers app
Thanks fellas. I will try that one. I thought I had already but maybe I haven't. Let ya know what happens!
I flashed the global leak and all went well. Thanks for the quick help!
Hi everyone,
I used RegawMod to unlock the bootloader, get root, and installed TWRP flash recovery. Phone is "S-ON". The phone was having issues with repeated SMS and I couldn't take the OTA. So I was told to relock the bootloader and install stock RUU file.
Ok so I did just that, relocked bootloader and then went to reinstall the RUU. When I went to download the RUU's I saw that the latest version was:
"RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed.exe"
I figured it would be ok to flash this and this would give me Jelly Bean all in one shot. My phone was running the stock rom which was software version "1.13.651.1"
So I installed the RUU and everything seemed to work properly until the phone rebooted. I noticed that none of the settings had been reset and the email account was still there etc. Typically when you flash an RUU everything goes back to configure mode on reboot. So I went into the settings software version etc and sure enough the software was the old software.
Looks like the RUU only changed my boot loader! When I checked originally I had bootloader 1.12.0000 after flashing the latest RUU file my bootloader was now 2.09.0000.
I then downloaded the "1.13.651.1" RUU to try and install it but it said not compatible with the bootloader.
Any advice on why the rom didn't update? What can I do now?
http://forum.xda-developers.com/showthread.php?p=36308826#post36308826
Welcome to the machine, where have you been? It's alright, we know where you've been.
Got a pretty lengthy thread, it seems the more people that run the new RUU are having the same exact issue. My radio is stuck on 1.05 and hboot 2.09 after running that thing. Should have known not to trust anything stock. Always thought those RUUs were safe.
Anyways, a bunch of us are subscribed to the thread I posted at the top of this post, I recommend you subscribe to it to keep things clean.
I've already unlocked bootloader and rooted device, following which I realized that there is no s-off option for me on the current hboot I have (1.44 after May) and not realizing that s-off is available for the latest AT&T release with 4.3. This is my second HTC device but it is my first go at s-off. I've been doing a lot of research but keep hitting dead ends it seems. Ideally, I would like to flash back to stock recovery and unroot by flashing stock 1.26.502.15 RUU (which is what I am currently on) so I can get OTA then use rumrunner to obtain s-off. I've also looked into downgrading/upgrading the current software number from 1.26.502.15 to 1.26.502.12/3.17.502.3 so I can use revone/rumrunner but I can't confirm whether or not I can flash RUU without being s-off'ed. If anyone can provide any advise I would greatly appreciate it. I'm also not sure if I'm using the terminologies correctly or if this is even posted in the right section.. Thanks in advance!
If you are currently on .12 firmware then you should still have 1.44 HBoot. If so, all you need is REVONE to S-Off. Doing anything else will make it even more of a chore. I believe if you update after then it is S-On again unless you flash one of the other ROM's that are available. You can also run the current RUU from the HTC website to give you the 4.3 update, but you will have 1.55, thus having to use Rumrunner. To run the current RUU, I think you have to relock it too, and unlock it again, at least I did with AIO. You can run any RUU without S-Off that is compatible with ATT. If you want the Brightstar GPE RUU, then yes, you must have S-Off, and change the CID to match that version, and etc for other versions.
hack14u said:
If you are currently on .12 firmware then you should still have 1.44 HBoot. If so, all you need is REVONE to S-Off. Doing anything else will make it even more of a chore. I believe if you update after then it is S-On again unless you flash one of the other ROM's that are available. You can also run the current RUU from the HTC website to give you the 4.3 update, but you will have 1.55, thus having to use Rumrunner. To run the current RUU, I think you have to relock it too, and unlock it again, at least I did with AIO. You can run any RUU without S-Off that is compatible with ATT. If you want the Brightstar GPE RUU, then yes, you must have S-Off, and change the CID to match that version, and etc for other versions.
Click to expand...
Click to collapse
I'm on .15 right now but didn't know if I could update to HTC website 4.3 because I am currently unlocked and rooted and do not have s-off. When I relocked bootloader and tried OTA I had to reboot and it just kept rebooting to TWRP and would not update successfully. So I didn't think the manual update would work?
The manual update will work, but it will WIPE everything. Been there done that, not a big deal though. Went through it, re-unlocked, re-flashed CWM, and that was that. I was going to do S-Off to get the GPE RUU, but heck, with the ATT Remove Bloat script, don't see the need anymore. Got 4.3 running as smooth as it can be, no ATT bloat, and GREAT battery life.
So even though I do NOT have S-off, I can still use the HTC released update to flash onto my phone with the current modifications that I've made already (Unlock and root on JB 4.1.2, software 1.26.502.15, hboot 1.44)? I was under the impression that with S-ON you cannot flash RUU, is that not correct? In the current state, I have to just re-lock bootloader and I can install the official HTC released update? And after which all my data will be wiped, including the custom recovery (TWRP) and root, all of this will be gone? (which is fine) I just have been researching and see that bricking the device is more likely to happen if the device is S-ON and you attempt to flash.
Rumrummer actually has a version available for 1.26.502.15, I used it on Sunday successfully to gain s-off with my mom's phone.
LightSpeedIII said:
Rumrummer actually has a version available for 1.26.502.15, I used it on Sunday successfully to gain s-off with my mom's phone.
Click to expand...
Click to collapse
are you shure? i have a htc one at&t on my hands with 1.26.502.15 firmware and it can not be done. I think you are very confused, 1.26.502.12 firmware is not the same!
---------- Post added at 12:03 PM ---------- Previous post was at 11:55 AM ----------
merck3d said:
So even though I do NOT have S-off, I can still use the HTC released update to flash onto my phone with the current modifications that I've made already (Unlock and root on JB 4.1.2, software 1.26.502.15, hboot 1.44)? I was under the impression that with S-ON you cannot flash RUU, is that not correct? In the current state, I have to just re-lock bootloader and I can install the official HTC released update? And after which all my data will be wiped, including the custom recovery (TWRP) and root, all of this will be gone? (which is fine) I just have been researching and see that bricking the device is more likely to happen if the device is S-ON and you attempt to flash.
Click to expand...
Click to collapse
With S-ON
As far as i have read, you can:
Update to a newer firmware. (but i don't really know if you can flash another htc one rom model, eg. flash an m7 rom into a m7att phone)
Reflash the same stock firmware via recovery (http://www.htc1guru.com/downloads)
YOU CAN NOT DOWNGRADE.
Install CWM Recovery or TWRP Recovery.
Root.
mpjoe2000 said:
-snip-
Click to expand...
Click to collapse
I am very sure, I still have the zip in my downloads folder, however, Rumrunner has been updated to be universal across most firmwares, this should include 1.26.502.15 because there was a version of rumrunner for it previously. Just go to rumrunner.us and follow their instructions.
LightSpeedIII said:
I am very sure, I still have the zip in my downloads folder, however, Rumrunner has been updated to be universal across most firmwares, this should include 1.26.502.15 because there was a version of rumrunner for it previously. Just go to rumrunner.us and follow their instructions.
Click to expand...
Click to collapse
you are right!!! i have a linux firewall old pc at home + a tplink open-wrt firmware, and i had to connect my modem's internet device directly to my pc to allow rumrunner to work properly!
No problem, glad I could help
hey, ihave a htc one m7 on 4.2.2 android ice cold project rom and ive been trying to go back to stock htc sense rom but downgrade from stock 5.0.2 and I cant seem to do it, ive tried ota update zip files, stock odexed rom but nothing seems to work, I got the stock rom on but then the touch screen didn't work so had to go back to aicp. I also cant get s-off as ive got hboot 1.61 and cant afford to buy sunshine.
any help would be much appreciated thanks.
You need the RUU then. The reason touch won't work is because the firmware is not matched to the OS. This is a common HTC thing. You have to find the RUU that corresponds to your carrier or region as well as being the same or newer than the firmware you are on now since you are S-On. You must relock your bootloader to install the RUU while being S-On as well.
es0tericcha0s said:
You need the RUU then. The reason touch won't work is because the firmware is not matched to the OS. This is a common HTC thing. You have to find the RUU that corresponds to your carrier or region as well as being the same or newer than the firmware you are on now since you are S-On. You must relock your bootloader to install the RUU while being S-On as well.
Click to expand...
Click to collapse
could you help me find then compatible RUU please? I don't know what one id use. I was hoping to downgrade from lollipop but I don't think ill be able to.
ive went back to the os that didn't work with touch and am going to do and ota update, but how would I get my device to allow ota updates again? do I have to put the recovery back to stock as well as relock bootloader or is there more to it?
You'll need fastboot to make sure you are getting the correct version. If you do not have it, get it from here: http://forum.xda-developers.com/showthread.php?t=2317790 then boot to the bootloader and run this command:
fastboot getvar all
Post results but remove your IMEI and serial number.
You definitely can not downgrade while S-On. You won't need to worry about OTAs as the RUU will do everything for you. If you do want to enable OTAs after you get everything matched up, then yes, you would need to leave the system and the recovery stock.
would there be anyway for me to downgrade then? ive tried flashing other firmware and so far I might have got it, I just need to wait for my phone to charge till I know
You can flash an older rom, but a true downgrade with everything matched is not possible while being S-On.
es0tericcha0s said:
You can flash an older rom, but a true downgrade with everything matched is not possible while being S-On.
Click to expand...
Click to collapse
what rom could I flash?
How could I know without knowing which M7 you are using and what firmware is on it? I've already provided instructions for what was needed for additional info.