Hi All,
So need some help. I have an ATT m8 that I did a GPE conversation following the tutorial at
http://sakitechonline.com/fully-convert-your-htc-one-m8-to-google-play-edition-w-ota-updates/
as well as a youtube video.
So there's a section about CID's and in the tutorial link, it says if my CID matches one of the ones listed, I can skip down to step #6 and install the GPE (which it did match, so I didn't change my CID to GOOGL001.) My question is, will I have issues with future OTA's? If so, do I have to start from scratch to change my CID, or can I do it as my phone currently sits right now? Also, if I do it as my phone currently sits, will it wipe my phone? Lastly, how do I go about changing my CID at this time? I know there are a few tutorials out there, but I'm not sure if I can follow them since most of the instructions to change CID's are midway through a tutorial and I'm already converted. I just don't want to brick my phone, and I've had bad luck and what not.
Any help would be great as I'm now using this phone as my primary and I don't wan't to have issues when android L finally decides to roll out. Thank you in advance!
jm0327 said:
Hi All,
So need some help. I have an ATT m8 that I did a GPE conversation following the tutorial at
http://sakitechonline.com/fully-convert-your-htc-one-m8-to-google-play-edition-w-ota-updates/
as well as a youtube video.
So there's a section about CID's and in the tutorial link, it says if my CID matches one of the ones listed, I can skip down to step #6 and install the GPE (which it did match, so I didn't change my CID to GOOGL001.) My question is, will I have issues with future OTA's? If so, do I have to start from scratch to change my CID, or can I do it as my phone currently sits right now? Also, if I do it as my phone currently sits, will it wipe my phone? Lastly, how do I go about changing my CID at this time? I know there are a few tutorials out there, but I'm not sure if I can follow them since most of the instructions to change CID's are midway through a tutorial and I'm already converted. I just don't want to brick my phone, and I've had bad luck and what not.
Any help would be great as I'm now using this phone as my primary and I don't wan't to have issues when android L finally decides to roll out. Thank you in advance!
Click to expand...
Click to collapse
So I ended up changing my CID to GOOGL001 from CWW__1 (or something). Is there any "prep" work I need to do to my phone besides having S-OFF before changing my CID so as not to brick it later or have issues with OTA's? Again, just don't want issues down the line that I may not foresee and wasn't sure if I can just freely change my CID without doing anything beforehand.
jm0327 said:
So I ended up changing my CID to GOOGL001 from CWW__1 (or something). Is there any "prep" work I need to do to my phone besides having S-OFF before changing my CID so as not to brick it later or have issues with OTA's? Again, just don't want issues down the line that I may not foresee and wasn't sure if I can just freely change my CID without doing anything beforehand.
Click to expand...
Click to collapse
Dude, fire is going to rain down from the skies onto your phone. JK, if I remember correctly, the only thing I did was make sure that I had the GPE recovery installed and relock bootloader and got OTA's just fine. I am thinking about playing with the GPE again too.
hack14u said:
Dude, fire is going to rain down from the skies onto your phone. JK, if I remember correctly, the only thing I did was make sure that I had the GPE recovery installed and relock bootloader and got OTA's just fine. I am thinking about playing with the GPE again too.
Click to expand...
Click to collapse
haha,, i wouldn't be surprised if my phone spontaneously combusted. Hmm, I haven't read anything about relocating the boot loader to make it work with OTA's. I only remember the CID thing. Thanks for the tip, I'll look into it.
jm0327 said:
Hmm, I haven't read anything about relocating the boot loader to make it work with OTA's. I only remember the CID thing.
Click to expand...
Click to collapse
That's because its not correct. You don't need to relock the bootloader to get or install OTAs. You do need stock recovery, and all system files need to be intact (if any are modified/deleted/frozen by root, they need to be restored to stock condition).
redpoint73 said:
That's because its not correct. You don't need to relock the bootloader to get or install OTAs. You do need stock recovery, and all system files need to be intact (if any are modified/deleted/frozen by root, they need to be restored to stock condition).
Click to expand...
Click to collapse
Sounds like I'm good to go now. I used the Stock Non-Rooted 4.4.4 2.12.1700.1 RUU Zip. Thanks for the heads up!
Related
I have a rooted HTC One from Telus.
I know you cannot OTA update the phone when its rooted it keeps giving an error during the update.
I want to unroot and return to stock.
I found found a Nandroid backup for TELUS as the RUU is not available.
Can someone please help with steps on how to restore the device so I can do the carrier updates on the device.... I don't care about the tamper stuff...
I know Telus will be releasing the KIT KAT update shortly and I want to do the carrier update.
Please help!!!
I am really sorry if this has already been discussed in a thread but I have searched high and low and I can't find any clear information for the Telus device.
Please if we can keep this just to the TELUS variant I will really appreciate it as I see so many threads go sideways!
Thank you for any help anyone can shed!!
CMD line is just fastboot oem lock. If you are looking at Nandroids, I am guessing you have installed custom recovery, maybe a custom ROM? If not, re-locking will give OTA updates, I am pretty sure of. I also think that the AIO toolkit works on TELUS http://forum.xda-developers.com/showthread.php?t=2183942. Worth a shot. Maybe someone else who has tried can chime in.
Hey Thanks for the reply I actually figured it out... long process but easy...
http://forum.xda-developers.com/showthread.php?t=2383992&page=6
I left out a few steps listed in the original thread... worked like a charm.. i didn't care for the tamper .. I left S off and was able to do all of the OTAs..... if anyone else needing help this is what I did... if not refer to the original thread to reset the tamper and re-lock....
1. changed CID back to ATT (CWS__001)
2. re-ran ATT RUU
3. changed CID back to TELUS001
4. booted TWRP
5. ran a simple backup so I could know the correct location to copy the TWRP stock nandroid
6. booted the phone
7. copied the stock twrp nandroid to the right location ( /TWRP/BACKUPS/XXXX/...
8. booted twrp
9. restored backup
hack14u said:
CMD line is just fastboot oem lock. If you are looking at Nandroids, I am guessing you have installed custom recovery, maybe a custom ROM? If not, re-locking will give OTA updates, I am pretty sure of. I also think that the AIO toolkit works on TELUS http://forum.xda-developers.com/showthread.php?t=2183942. Worth a shot. Maybe someone else who has tried can chime in.
Click to expand...
Click to collapse
software update
hello here I have a TELUS HTC ONE here are the details:
LOCKED
S-ON
H-BOOT 1.55.0000
M7-UL-PUT
September 17.2013
CID TELUS001
then here I would like to have the latest international day is that I have to change a SUPER CID glass but I do not how it is.
then here if you could help me thank you
I've posted in 2 Dev threads, and its like everyone passed right over them w/o any kind of answer of any sorts. What I've included below is a copy of my build.prop I've pulled. If you notice I am on 2.12.1700.1...I ran a ruu to GPE convert, but now that 5.0 is dropping like wildfire. I believe I've come across an issue. You see, I do not have access to a computer so everything I do must be done through my phone or my galaxy tab 4 tablet. I've superCID my device;however, the build.prop line ro.aa.cidlist gibes multiple cid's. These "other" cids don't show in bootloader.
In order to receive OTA..you must be
1. GPE cid (mid-im not sure)
2. On the appropriate firmware
3. Stock recovery
Right now, as it sits I'm on 2.12.1700.1 with philz recovery. I'll make the change to stock when the 5.0 OTA drops...
All I'm trying to figure out is:
Does anyone think I'll have problems based off what my build.prop is displaying ?
I can not change my CID (Unless you/someone knows of a way without a computer can do so)
ro.aa.romver=2.12.1700.1
ro.aa.maincid=GOOGL001
ro.aa.modelid=0P6B10000,0P6B50000,0P6B60000,0P6B12000,0P6B13000,0P6B11000,0P6B15000,0P6B16000,0P6B17000
ro.aa.cidlist=GOOGL001,11111111,T-MOB010,CWS__001,HTC__001,HTC__102,HTC__203,HTC__E11,HTC__405,HTC__Y13,HTC__304,HTC__A07,HTC__032,HTC__J15,HTC__016,HTC__M27,HTC__K18,HTC__A48,HTC__002,BS_US001,BS_US002,ROGER001
Some lines I've copied from my build.prop...my bootloader says superCID (1111111);however, this build prop seems to tell me that it looks like I'd be ready for the 5.0 OTA (When I flash stock recovery,which I'm still using philz)...I've asked entirely too much, even helped a few users with the things I understand, but I haven't received a complete answer...I'm s-off, GPE converted, 2.12.1700.1, rooted, superCID..I can not change my cid (no computer-no access to fastboot commands)...
Bump
Well now I can add some insight.
If in fact your completely converted than you must have the matching "CID"/" MID" as the out of box GPE HTC one m8 .no solid facts as far as the MID but I changed mine to match as I'm ready for the official GPE update. I'll just have to flash the stock recovery back when it's time.also I wouldn't use Xposed framework or anything like it just in case 5.0 rejects it.
I will add that the MID didn't matter for past OTA .I uses the 4.4.3 ruu so I could take the official 4.4.4 update
(easy as pie)
Well I believe I have completely converted to GPE...I followed graffixnyc thread for doing so, and got insight from HolyAngel. I'm still not even a 100% sure if I'm all good to go. I understand that I need to flash stock recovery, but I wasn't planning on doing so til the 5.0 OTA drops. I have searched everywhere for info about changing CIDs w/o the use of a computer,but to no avail...
Currently as it sits..I'm still on 2.12.1700.1, still superCID with philz recovery and bliss ROM...I'm switching back to skydragon 3.0.1 because the battery life is much better
Ultimately your going to need a computer at some point or wait till the ruu is released .
There needs to be more organization in this thread though. I'm not entirely stupid nor am I new to android. The reason I wanted GPE...I never used Sense based ROMs anyways. Partition is smaller with GPE too...
GOOGL001 is the CID, 0P6B17000 is MID for outta box GPE M8...I'm superCID, but never have done anything with MIDs as I let the RUU 2.12.1700.1 flash the MIDs included with the android info text of the RUU zip
I agree to e certain degree but with people making new threads about things that have already been covered definitely don't help.I'm in and out of all kinds of device forums to help because I like the challenges thrown out by all kinds of users.I realize you know what needs to be done and also realize your without a computer to get were you need to be.I hope I've not come off offensive in any way cause I am trying to help.
You didn't come off as offensive...I've gone against the grain of how things are done because after a few days of researching thread after thread after thread. I never found what I was looking for, and I still haven't...I guess I'll just wait til I get a computer to rewrite the CID. I'll just wait til 5.0 ota drops, flash the 3.09.1700.2 fw and see what happens..if anything I'll just reRUU to 2.12.1700.1...it seems to me that my phones ready for the ota anyways considering my build.prop suggests I have 1111111 and GOOGL001..
Am sure I'll see you around.good luck
I'm not going anywhere...nychitman quit supporting DU, so I'm looking into taking over in the near future...my computers still screwed til I get another hard drive put in it
@jxcorex28
Here you go man,I only hope GPE is a choice in aroma.
This is what found
http://www.droidviews.com/change-cid-mid-htc-one-devices/
MID tool zip below
http://d-h.st/w9V
I wonder if cid matters than ? I appreciate it, as it sits my mid is 0PB6B12000..Ill switch to whatever GPE MID is needed
jxcorex28 said:
I wonder if cid matters than ? I appreciate it, as it sits my mid is 0PB6B12000..Ill switch to whatever GPE MID is needed
Click to expand...
Click to collapse
Yes cid matters
So do you think superCID matters. From what I understand it doesn't because of being able to flash any ROM neantvfor any HTC m8 (as long as its GSM)
jxcorex28 said:
So do you think superCID matters. From what I understand it doesn't because of being able to flash any ROM neantvfor any HTC m8 (as long as its GSM)
Click to expand...
Click to collapse
Yes but what I've read 5.0 will check for everything. It's not worth the risk if you ask me.
To make 100% sure everything goes right just change everything to match.
Like I said all I have to do is flash stock recovery and except the OTA
I got this phone off a friend, and I have a opportunity to trade my M8 for a M9 plus cash. The problem is that the guy won't trade without the phone being completely stock with no root or any signs.
I've searched quite a bit on this forum for answers and everything is for older versions of Android. I can't find what RUU I would need or if it's even available. I seen a guide and tutorial from theunlckr, but it's from mid 2014.
I'm looking for a complete guide from start to end that will put this phone back to stock. This would be my first time and I don't know jack about what to do when it comes to this stuff. I'm very computer savvy so it shouldn't be a issue.
The info is following when I boot into recovery:
First off, the HTC logo will appear saying it's property of HTC and something about developers in red.
Software Status : Modified
Unlocked
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.0000
[email protected]
OPENDSP-v47.2.2-00564-M8974_FO.1024
OS-4.28.502.1
eMMC-boot 2048MB
4/20/15
There is also a Team Win application or recovery when I choose to do a factory reset.
Please if someone can help, I need to do this soon.
rlockwich said:
I've searched quite a bit on this forum for answers and everything is for older versions of Android. I can't find what RUU I would need or if it's even available.
Click to expand...
Click to collapse
You want the Lollipop (Android 5.0.2) AT&T RUU (software number 4.28) which is linked on my Index thread at the top of the General AT&T M8 forum section: http://forum.xda-developers.com/showthread.php?t=2751432
Relock the bootloader (command: fastboot oem lock) then just run the RUU (Windows executable).
rlockwich said:
I got this phone off a friend, and I have a opportunity to trade my M8 for a M9 plus cash. The problem is that the guy won't trade without the phone being completely stock with no root or any signs.
Click to expand...
Click to collapse
What "completely" stock means is a bit complicated (and may vary depending on the person). You can relock the bootloader and run the RUU. Everything will be stock, except that the phone will say RELOCKED in bootloader instead of UNLOCKED (which is the factory condition).
The only way to make it say LOCKED is to s-off by sunshine ($25) then change the flag to LOCKED. Then go back to s-on. But IMO, its not worthwhile to spend money to sell/trade a phone; and not worth the money, time and effort for something that is very minor.
Functionally, there is no difference between RELOCKED and LOCKED. The only reason anyone would care, is if they want to make a warranty claim with HTC. In that case, they may deny any claim anyway, since there is already a record of the bootloader being unlocked via HTCDev.com (tracked by the phone's IMEI). Not even sure if the warranty (1 year from purchase) would be valid, anyway for a device that has changed hands 2 times.
I would recommend you ask the buy/trade partner if RELOCKED bootloader is okay. Otherwise, find someone else to trade with.
rlockwich said:
First off, the HTC logo will appear saying it's property of HTC and something about developers in red.
Click to expand...
Click to collapse
This, and TWRP recovery will be gone once you RUU.
RUU will re-image the entire phone to stock factory (Lollipop) condition. So it will be stock ROM, stock recovery, no root, etc.
You should also remove your SD card (if one is inserted), then go into phone settings and wipe all storage, to make sure the internal storage/virtual SD is wiped of your personal data.
Will this make him be able to do OTA updates for when 5.1 comes?
rlockwich said:
Will this make him be able to do OTA updates for when 5.1 comes?
Click to expand...
Click to collapse
Yes. The only requirements for OTA are stock ROM and stock recovery, which post-RUU state satisfies both.
Note that OTA updates for the AT&T version are only available when connected to AT&T's network. So if the buyer is asking if he will get OTAs, and he happens to be using another carrier, the answer is NO. And in that case, the RUU for the next update is his best option.
It was a success! Thank you for taking the time to help me out. I really appreciate everything you've done!
Do you think it's necessary to wipe from the settings in backup/restore after doing the RUU?
I read somewhere that there are files left behind from the root, after unrooting....does the RUU wipe all of this away, so there won't be a need to do a 2nd reset after the RUU completes?
rlockwich said:
Do you think it's necessary to wipe from the settings in backup/restore after doing the RUU?
I read somewhere that there are files left behind from the root, after unrooting....does the RUU wipe all of this away, so there won't be a need to do a 2nd reset after the RUU completes?
Click to expand...
Click to collapse
Can never remember for certain; but I think RUU just wipes user data, and normally leaves internal storage intact. Not just files used for root, but personal files, too. So you will want to make sure internal storage is wiped.
Therefore, I do recommend going to Backup & Reset in Settings, pick Reset phone in order to make sure internal storage is wiped.
Please bear with me since I'm not too experienced on this and did research on XDA to the best I could before asking. I'm planning on returning my device to stock, but I'm worried I might brick it. I'm currently running the Skydragon 9.0 rom (http://forum.xda-developers.com/att-htc-one-m8/development/rom-sd-4-0-sense7-port-sdkernel-t3062367) and toggled on quite a lot of things. Mainly, I remember allowing it to overwrite my current kernel.
My device has S-ON from what I saw on HBOOT, is using the Skydragon custom kernel, and I'm using TWRP custom recovery. I still have the RUU I downloaded from AT&T to return my device to stock 5.0.2 firmware. My question is, shall I just run the RUU and it will all be back to stock? Should I flash the stock recovery first? Should I relock the bootloader first? and if any of those are true, in what order?
The guide which seemed the most similar to me was this one http://forum.xda-developers.com/showthread.php?t=2751011 but that required S-OFF which I don't have and don't think it's a good thing to have. Could anyone point me in the right direciton? thanks!
First of all, what is your intent in returning to stock: to sell or give away the phone? Or return for warranty service?
sarxion said:
Please bear with me since I'm not too experienced on this and did research on XDA to the best I could before asking. I'm planning on returning my device to stock, but I'm worried I might brick it.
Click to expand...
Click to collapse
You won't brick the phone with s-on. You just won't.
You might screw something up, and temporarily render the phone unable to boot. But that can easily be fixed with the right knowledge; and that is not a brick.
sarxion said:
I'm currently running the Skydragon 9.0 rom (http://forum.xda-developers.com/att-htc-one-m8/development/rom-sd-4-0-sense7-port-sdkernel-t3062367) and toggled on quite a lot of things. Mainly, I remember allowing it to overwrite my current kernel.
Click to expand...
Click to collapse
On this device, flashing a custom ROM always overwrites the kernel. What you selected when you flashed the ROM, is to flash the custom SD kernel instead of flashing the "stock" HTC kernel that came with the ROM base (that Skydragon 9 is based on).
None of that matters, once you return to stock, the custom ROM (including kernel) and any other settings, tweaks, etc. will be returned to their "stock" condition.
sarxion said:
My question is, shall I just run the RUU and it will all be back to stock?
Click to expand...
Click to collapse
Will "all" be back to stock? No. The bootloader will still say RELOCKED instead of the original LOCKED condition. You need s-off to make it say LOCKED.
Also bear in mind that HTC has a record of you unlocking the bootloader, if you did it via HTCDev.com (which is most likely the case). Nothing will change that fact, and it should be disclosed to potential buyers if selling/trading the phone (that it was bootloader unlocked and modded, then returned to near-stock condition).
But everything else will be back to stock after RUU: Stock ROM, stock kernel, stock recovery, and the user data will be wiped.
sarxion said:
Should I flash the stock recovery first? Should I relock the bootloader first? and if any of those are true, in what order?
Click to expand...
Click to collapse
No need to flash stock recovery.
You will need to relock the bootloader to RUU.
Backup (move) anything you want to keep (personal photos, etc.) to your computer, etc. before RUU, as RUU will wipe the phone.
sarxion said:
The guide which seemed the most similar to me was this one http://forum.xda-developers.com/showthread.php?t=2751011 but that required S-OFF which I don't have and don't think it's a good thing to have.
Click to expand...
Click to collapse
As I've mentioned, s-off is only needed if you want to return the phone to LOCKED (instead of RELOCKED). I will agree its probably not necessary to spend $25 for s-off just to do that.
Further, the guide is very old (May 2014 - right after the phone was released) and probably before any RUU was available. It follows a much more complicated path to "return to stock" and needlessly so.
Just relock the bootloader and run the RUU, is my recommendation.
redpoint73 said:
First of all, what is your intent in returning to stock: to sell or give away the phone? Or return for warranty service?
You won't brick the phone with s-on. You just won't.
You might screw something up, and temporarily render the phone unable to boot. But that can easily be fixed with the right knowledge; and that is not a brick.
On this device, flashing a custom ROM always overwrites the kernel. What you selected when you flashed the ROM, is to flash the custom SD kernel instead of flashing the "stock" HTC kernel that came with the ROM base (that Skydragon 9 is based on).
None of that matters, once you return to stock, the custom ROM (including kernel) and any other settings, tweaks, etc. will be returned to their "stock" condition.
Will "all" be back to stock? No. The bootloader will still say RELOCKED instead of the original LOCKED condition. You need s-off to make it say LOCKED.
Also bear in mind that HTC has a record of you unlocking the bootloader, if you did it via HTCDev.com (which is most likely the case). Nothing will change that fact, and it should be disclosed to potential buyers if selling/trading the phone (that it was bootloader unlocked and modded, then returned to near-stock condition).
But everything else will be back to stock after RUU: Stock ROM, stock kernel, stock recovery, and the user data will be wiped.
No need to flash stock recovery.
You will need to relock the bootloader to RUU.
Backup (move) anything you want to keep (personal photos, etc.) to your computer, etc. before RUU, as RUU will wipe the phone.
As I've mentioned, s-off is only needed if you want to return the phone to LOCKED (instead of RELOCKED). I will agree its probably not necessary to spend $25 for s-off just to do that.
Further, the guide is very old (May 2014 - right after the phone was released) and probably before any RUU was available. It follows a much more complicated path to "return to stock" and needlessly so.
Just relock the bootloader and run the RUU, is my recommendation.
Click to expand...
Click to collapse
Thank you very much for your quick answer. I'm returning it to stock firmware to sell the device. Is it safe to lock the bootloader while Skydragon is on my device? and after that, just run the AT&T RUU and I'm done, right?
Also, do you by any chance have any resource on how to relock the bootloader? I've searched for guides on this but I the guides I find don't look very trustworthy, or don't apply, such as this one that requires S-OFF http://forum.xda-developers.com/showthread.php?t=2708571
sarxion said:
Thank you very much for your quick answer. I'm returning it to stock firmware to sell the device. Is it safe to lock the bootloader while Skydragon is on my device? and after that, just run the AT&T RUU and I'm done, right?
Click to expand...
Click to collapse
Correct. It doesn't matter what ROM is on the device when you relock the bootloader. The phone will be rendered unable to boot (may even wipe OS) when you relock.
sarxion said:
Also, do you by any chance have any resource on how to relock the bootloader? I've searched for guides on this but I the guides I find don't look very trustworthy
Click to expand...
Click to collapse
I don't know what you mean by "trustworthy". But you won't fine a "guide" because its a single fastboot command: fastboot oem lock
redpoint73 said:
Correct. It doesn't matter what ROM is on the device when you relock the bootloader. The phone will be rendered unable to boot (may even wipe OS) when you relock.
I don't know what you mean by "trustworthy". But you won't fine a "guide" because its a single fastboot command: fastboot oem lock
Click to expand...
Click to collapse
Thank you very much. So I can run the RUU with my M8 on bootloader mode? Because after relocking the bootloader, I'm asuming it probably won't even boot since it's running a custom ROM and kernel. (I'll be running the exact same RUU version I ran before installing the custom rom)
sarxion said:
So I can run the RUU with my M8 on bootloader mode?
Click to expand...
Click to collapse
The RUU will run with the phone in bootloader-fastboot mode, yes.
sarxion said:
Because after relocking the bootloader, I'm asuming it probably won't even boot since it's running a custom ROM and kernel.
Click to expand...
Click to collapse
That is correct. And in fact, as far as I know, the phone is rendered unable to boot into OS after relocking the bootloader, even if you were on the stock ROM.
OP,
Were you able to go back to stock?
"Unfortunately, AT&T Ready2Go has stopped." Is stuck looping on my phone.
About a year ago I rooted my phone, following these directions. (I can't yet post a link, but the first option on google when searching "how to root m8" is the site, htconeroot.com, that I used.)
This morning I noticed that my phone was not vibrating anymore no matter if I restarted the phone or what settings were applied. So I checked online to see if there was a fix, and a factory reset was recommended.
So when I got back from work today, I thought I had successfully uninstalled the root using SuperSU. Then I performed a factory reset. My phone then went into TWRP recovery which was alarming. So I rebooted the system from TWRP , then the message in the title kept popping up over and over again, so I am in a bit of a pickle. I can message and call at the moment but that is about it.
I'm thinking the problem is similar to this one someone had on a note 3, except I was trying to factory reset rather than update. http://forum.xda-developers.com/showthread.php?t=2663120
Has this happened to anyone else, and do you have any suggested fixes for resetting this phone???
Thanks in advance.
I've seen a number of cases on the M8 forums of various processes stopping with message "XXX has stopped" after a factory reset. Not sure what is causing this. But there are a variety of ways to recover.
Since you have TWRP, you can try to restore a TWRP backup of your own (if you made one) or install a stockish ROM. Those methods may be helpful if you want to retain or retrieve any personal data.
Otherwise, relock the bootloader and RUU back to full stock (RUU will wipe the phone).
redpoint73 said:
Otherwise, relock the bootloader and RUU back to full stock (RUU will wipe the phone).
Click to expand...
Click to collapse
Honestly I'd be fine returning to full stock, at least for the time being, to see if the vibration problem would fix itself. But do I need to be S-OFF for RUU?
eaflook said:
But do I need to be S-OFF for RUU?
Click to expand...
Click to collapse
No, and I wish folks would stop saying you need s-off to RUU (not you, but I assume you got this notion from another post/thread).
You can run the an RUU made for the AT&T M8, as long as you aren't "downgrading" to a previous version (such as Lollipop to Kitkat). For that, you need s-off; or to change the CID and run another carrier version RUU.
You do need to relock the bootloader to run RUU while s-on, with command: fastboot oem lock
Are you currently on LP or MM (what does it say for OS number on the bootloader screen)?
redpoint73 said:
No, and I wish folks would stop saying you need s-off to RUU (not you, but I assume you got this notion from another post/thread).
You can run the an RUU made for the AT&T M8, as long as you aren't "downgrading" to a previous version (such as Lollipop to Kitkat). For that, you need s-off; or to change the CID and run another carrier version RUU.
You do need to relock the bootloader to run RUU while s-on, with command: fastboot oem lock
Are you currently on LP or MM (what does it say for OS number on the bootloader screen)?
Click to expand...
Click to collapse
Um... the OS line on the bootloader screen looks blank, unless I'm looking in the wrong place.
Should I do this? http://forum.xda-developers.com/htc-one-m8/help/guide-how-to-solve-soft-brick-phone-t2824193
eaflook said:
Um... the OS line on the bootloader screen looks blank, unless I'm looking in the wrong place.
Click to expand...
Click to collapse
No, you're looking in the right place. Its somewhat common for OS number to be blank, its a known bug in older TWRP versions that it deletes the OS number.
What does it say for hboot number and radio number?
If the phone still on the stock ROM you originally rooted on? If so, is it Lollipop, Kitkat, etc.?
eaflook said:
U
Should I do this? http://forum.xda-developers.com/htc-one-m8/help/guide-how-to-solve-soft-brick-phone-t2824193
Click to expand...
Click to collapse
You can do that. All that "guide" describes is one way to get a ROM on an SD and flash it, which is one of the options I already suggested in Post #2 above.
But what ROM will work, somewhat depends on the info I requested above.
redpoint73 said:
What does it say for hboot number and radio number?
Click to expand...
Click to collapse
hboot number-3.19.0.0000
radio [email protected]
redpoint73 said:
If the phone still on the stock ROM you originally rooted on? If so, is it Lollipop, Kitkat, etc.?
Click to expand...
Click to collapse
Yes it is still on the stock root ROM. I am running Lollipop 5.0.2.
eaflook said:
hboot number-3.19.0.0000
radio [email protected]
Yes it is still on the stock root ROM. I am running Lollipop 5.0.2.
Click to expand...
Click to collapse
You should be fine flashing most any ROM on the AT&T or "international" M8 development forums. Just avoid other dev sections for variants, such as the Sprint or Verizon dev sections.
Before flashing a ROM, you may want to update your TWRP version to 3.0.whatever.
Although I have to admit, I'm still on TWRP 2.8.4, and its worked fine flashing LP and MM custom ROMs. Any older than 2.8.something may cause issues.
Alternately, relock bootloader and run RUU 4.28.502.2 (Lollipop). If you want to run the Marshmallow RUU (6.20.502.5), you'll need to flash the MM firmware first, then RUU. Link that describes that process, as well as all ATT RUUs is on my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
redpoint73 said:
You should be fine flashing most any ROM on the AT&T or "international" M8 development forums. Just avoid other dev sections for variants, such as the Sprint or Verizon dev sections.
Before flashing a ROM, you may want to update your TWRP version to 3.0.whatever.
Although I have to admit, I'm still on TWRP 2.8.4, and its worked fine flashing LP and MM custom ROMs. Any older than 2.8.something may cause issues.
Alternately, relock bootloader and run RUU 4.28.502.2 (Lollipop). If you want to run the Marshmallow RUU (6.20.502.5), you'll need to flash the MM firmware first, then RUU. Link that describes that process, as well as all ATT RUUs is on my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
Click to expand...
Click to collapse
Do you know how I might update TWRP from 2.7.0.2?-----Nevermind, I got it.
eaflook said:
Do you know how I might update TWRP from 2.7.0.2?-----Nevermind, I got it.
Click to expand...
Click to collapse
Good practice is to post what you did (or going to do) for the benefit of others that may have the same question; or so we can verify you are on the right track.
In case others may have the same question (or you get stuck again), all TWRP versions, and instructions (recommend install with fastboot method) are here: https://twrp.me/devices/htconem8gsm.html