Hello, I rooted my phone a while back and have not kept up with updates. Now it seems I am unable to make outgoing phone calls. After trying to troubleshoot it seems I'm super behind on Android version (4.28.502.1). It has been a while since I've done anything root related. Can I just download the kernel from HTCDEV (.zip) and flash in recovery? Sorry for the newb question. Thank you.
Mike
Dazedstate said:
Can I just download the kernel from HTCDEV (.zip) and flash in recovery?
Click to expand...
Click to collapse
NO NO NO NO NO
And did I mention . . . . NO!!!!
First off, those aren't kernels, they are kernel source codes. And if you don't know what that means, you shouldn't and needn't mess with them.
Second, its not something you can flash it recovery , and its not an update of any sort.
Third, even if it was a kernel, understand a kernel does not update the ROM, firmware, etc. While important, the kernel is like 2% of what is needed to make a phone run correctly. So even if it was a kernel, flashing it would not do what you wanted; and would likely cause more problems than anything.
Go to my Index thread, go to RUU, and follow the link for the 5.0.2 RUU, and download it: http://forum.xda-developers.com/showthread.php?t=2751432
Then relock the bootloader and run the RUU to update your phone to "official" AT&T Lollipop. Backup any personal data you want to preserve before RUU; as RUU will wipe the phone.
redpoint73 said:
NO NO NO NO NO
And did I mention . . . . NO!!!!
First off, those aren't kernels, they are kernel source codes. And if you don't know what that means, you shouldn't and needn't mess with them.
Second, its not something you can flash it recovery , and its not an update of any sort.
Third, even if it was a kernel, understand a kernel does not update the ROM, firmware, etc. While important, the kernel is like 2% of what is needed to make a phone run correctly. So even if it was a kernel, flashing it would not do what you wanted; and would likely cause more problems than anything.
Go to my Index thread, go to RUU, and follow the link for the 5.0.2 RUU, and download it: http://forum.xda-developers.com/showthread.php?t=2751432
Then relock the bootloader and run the RUU to update your phone to "official" AT&T Lollipop. Backup any personal data you want to preserve before RUU; as RUU will wipe the phone.
Click to expand...
Click to collapse
Thank you for your help. You probably saved me a lot of heartache.
Related
Hi all, back when the unlock was released for this phone I installed a custom GB rom on my brother's phone. I am very experienced.with flashing and rooting etc so this wasn't a problem. Now with S-Off things have gotten a bit more complicated, not to mention the mainver nonsense I've been reading about. To make matters worse I haven't found a good thread outlining all these details on what needs to be done for the transition from GB to ICS; everyone basically assumes you're already on ICS and either S-On or S-Off.
So I have a few questions I'm hoping someone can answer.
1. I want to keep my brother's phone S-On. I have reviewed the S-Off method and deem it too risky for hardware that is not my own. That said, what's the best path to getting to a custom ICS OTA based rom from GB firmware?
a. Should I flash stock GB, relock phone, install OTA, unlock phone, install custom ICS rom?
b. Should I directly install a certain firmware from the boot loader along with a custom ICS OTA based rom from recovery? If so, which firmware should I flash? Is there any mainver stuff I need to tweak?
c. Or something else?
2. I always perform backups before flashing a new rom to ensure if something goes wrong I can restore to the previous rom image. However, if I backup a GB rom that runs on an older firmware and install ICS based on a newer firmware, would restoring to GB be as simple as going into recovery and restoring his old GB rom? Or would I have to flash the old firmware first?
3. I've noticed some roms like Viper use aroma installer which can handle multiple situations of installation. Would the situation I am describing (GB firmware, S-On) be handled? I am unsure how many different firmware versions there are out there. I don't know if referring to the "old firmware" means an older ICS firmware or GB firmware.
Thank you all for your help. It is frustrating for me to be this confused about how to upgrade a phone considering the amount of times I've done it in the past. I appreciate any responses or links that could help me better understand what I must do.
so your s-on and unlocked? or locked either way
re-lock if you are unlocked and then run
the ics offical .exe RUU from
here
http://forum.xda-developers.com/showpost.php?p=29979907&postcount=133
after you do that then unlock and flash a custom recovery then flash a ics rom of your choice
Div033 said:
Hi all, back when the unlock was released for this phone I installed a custom GB rom on my brother's phone. I am very experienced.with flashing and rooting etc so this wasn't a problem. Now with S-Off things have gotten a bit more complicated, not to mention the mainver nonsense I've been reading about. To make matters worse I haven't found a good thread outlining all these details on what needs to be done for the transition from GB to ICS; everyone basically assumes you're already on ICS and either S-On or S-Off.
So I have a few questions I'm hoping someone can answer.
1. I want to keep my brother's phone S-On. I have reviewed the S-Off method and deem it too risky for hardware that is not my own. That said, what's the best path to getting to a custom ICS OTA based rom from GB firmware?
a. Should I flash stock GB, relock phone, install OTA, unlock phone, install custom ICS rom?
b. Should I directly install a certain firmware from the boot loader along with a custom ICS OTA based rom from recovery? If so, which firmware should I flash? Is there any mainver stuff I need to tweak?
c. Or something else?
2. I always perform backups before flashing a new rom to ensure if something goes wrong I can restore to the previous rom image. However, if I backup a GB rom that runs on an older firmware and install ICS based on a newer firmware, would restoring to GB be as simple as going into recovery and restoring his old GB rom? Or would I have to flash the old firmware first?
3. I've noticed some roms like Viper use aroma installer which can handle multiple situations of installation. Would the situation I am describing (GB firmware, S-On) be handled? I am unsure how many different firmware versions there are out there. I don't know if referring to the "old firmware" means an older ICS firmware or GB firmware.
Thank you all for your help. It is frustrating for me to be this confused about how to upgrade a phone considering the amount of times I've done it in the past. I appreciate any responses or links that could help me better understand what I must do.
Click to expand...
Click to collapse
Try CleanROM, I've been using it since I got it. Very easy to install with S-On.
nstallation for S-ON Devices on Gingerbread firmware
Copy ROM to SD Card AND PH98IMG.zip AND GB Firmware Patch to ROOT of SD Card
Reboot to recovery
wipe data / Factory Reset
Flash ROM
Flash GB Fimrware Patch
Use Developer Menu to reboot to bootloader and flash the boot.img file in the PH98IMG.zip
Reboot
Profit!
Click to expand...
Click to collapse
The phone might say something about the SD card not working, so make sure you download the Gingerbread Firmware patch. Just Flash it like a rom and you're all god
Thread Ended, Forum Master Please Delete it, TQ for all the support
My responses below in red font.
vtkm831125 said:
hi there to all experts,
recently i have got a 2nd hand flyer(bought from singapore, due to a sticker name "singtel") for my parents as a gift(it's free, so...)
what i want to do now is:
1. to erase all apps and data, just to make it look like newly bought Just do a factory reset. I'd be surprised if this was not already done by the previous owner, all their user data would still be intact!
2. to root What hboot version are you on? As long as your hboot version is compatible, you should be able to do this: http://forum.xda-developers.com/showthread.php?t=1194709
Downgrade to GB required if you are on stock HC.
3. to install a custom rom on to it, i got a recommandation rom --- LeeDrOiD_Flyer_HC_V4.3.0.zip, already downloaded
i have run through the forum for advice and tutorial,
but i'm not expert to programing, so don't understand many programing language, No programming language is needed. Usually anyone that can follow directions, and has some familiarity with computers can get S-off and root. But some of the terms (jargon) may be new to you.
1.i'm in hc flyer 3g+wifi, do i need to downgrade to gb to gain root and flash custom rom? Yes. You need to do this: http://forum.xda-developers.com/showthread.php?t=1307759
Then this: http://forum.xda-developers.com/showthread.php?t=1194709
2.can i flash a custom rom on stock hc after i have root it? You need to have S-Off or unlocked bootloader
3.what is s-off? and how do i get it? S-Off means all security is off. It means you can flash ROMs, kernels, radios. With an unlocked bootloader, you can flash ROMs, but not kernels and radios.
4.can flyer do a phone call? i see some treat say it can but some say no Should be able to just fine. There are custom ROMs that support it, and I believe a separate mod for it in Development. But I've never used this function myself.
5.which steps should i take the best to install a custom rom:
----i'm in hc flyer---->s-off----->root----->install cwm----->install custom rom?
or
----i'm in hc flyer----->s-off----->root----->downgarde to gb----->install cwm----->install custom rom?
Neither. You can't S-Off from HC.
Downgrade to GB>S-Off>Install CWM>root>install custom ROM.
6.is hc like ics, which mean if u do a full wipe, u'll brick ur device? What do you mean by "full wipe"? You can wipe data, cache, Dalvik and system just fine on HC or ICS. Altering hboot may brick the device, but that goes with any Android version.
Click to expand...
Click to collapse
Thread Ended, Forum Master Please Delete it, TQ for all the support
Your hboot versions is unfortunately not supported by globatron's S-Off method that I linked.
You can take a look at this: http://forum.xda-developers.com/showthread.php?t=1881748
But I personally have no experience with it.
In short, you should be able to unlock the bootloader via HTCDev.com, install CWM, and flash SU to get root.
[Thread Ended, Forum Master Please Delete it, TQ for all the support
With the bootloader unlocked and custom recovery (CWM) installed, you can flash custom ROMs. Only difference with unlocked bootloader versus true S-Off, is that you have to extract the boot.img file from the ROM zip, and flash it separately using fastboot (Flyer connected to your PC).
Thread Ended, Forum Master Please Delete it, TQ for all the support
That all sounds right.
With the addition of:
5) Extract boot.img from custom ROM zip file.
6) Flash boot.img using fastboot
As already mentioned, I didn't have to go the bootloader unlock method, as I have full S-Off. But this is my understanding from what I've read, and flashing ROMs on my HTC One X phone is similar.
Thread Ended, Forum Master Please Delete it, TQ for all the support
vtkm831125 said:
Thread Ended, Forum Master Please Delete it, TQ for all the support
Click to expand...
Click to collapse
NOOOOO. It doesn't work that way. Just because you had your question answered, does not mean that you delete all the content and ask the mods to delete the thread.
Others may have the same question, and might benefit from your thread. This way, people can just look for an existing answer, instead of having to post new threads to ask the same questions over and over again.
What could have been a useful post for others, is now useless.
Really, WTF???? Why did you do this???? Its not just about you, dude.
FOUND THE RECOVERY (See below)
Right now my goal is to go back to stock to flash the OTA Update. I am running my nandroid back up I first made when which is the 4.4.4 w/ Software # 1.58.502.1. and right now I have TWRP as my recovery.
Also can someone confirm something for me. This nandroid I am running is rooted obviously and has SuperUser on it. If I go back to the stock recovery can I still do the OTA update even though SuperUser is there and the phone is unlocked?
Also in order to get the stock recovery back on the phone I need to use ABD and the windows command prompt method correct?
Thanks
found this link and was able to find the stock recovery finally. I clicked "Non-WWE- Recovery Images" Ten on the site it opens I clicked the more recoveries folder at the top and 1.58.502.1 was the first one.
http://forum.xda-developers.com/showthread.php?t=2701376
Now the only thing I need to know is if going back to stock recovery will allow me to update to OTA even though there is SuperUser on my device and even though I am rooted and unlock (S-on)
magicbumm328 said:
found this link and was able to find the stock recovery finally. I clicked "Non-WWE- Recovery Images" Ten on the site it opens I clicked the more recoveries folder at the top and 1.58.502.1 was the first one.
http://forum.xda-developers.com/showthread.php?t=2701376
Now the only thing I need to know is if going back to stock recovery will allow me to update to OTA even though there is SuperUser on my device and even though I am rooted and unlock (S-on)
Click to expand...
Click to collapse
As long as the ROM is stock (nothing modified by root) and stock recovery, you can update by OTA (root okay, unlocked bootloader okay).
Another option, just relock the bootloader and run the 4.4.4 RUU. It saves you from all the hassle (finding stock ROM and stock recovery), plus installing 2 OTAs. Only reason to do it the way you are, is to keep user data (RUU wipes phone) and it also saves you from having to relock.
redpoint73 said:
As long as the ROM is stock (nothing modified by root) and stock recovery, you can update by OTA (root okay, unlocked bootloader okay).
Another option, just relock the bootloader and run the 4.4.4 RUU. It saves you from all the hassle (finding stock ROM and stock recovery), plus installing 2 OTAs. Only reason to do it the way you are, is to keep user data (RUU wipes phone) and it also saves you from having to relock.
Click to expand...
Click to collapse
Well I do have the stock ROM. Idk if it having super user on it counts as being modified by root though? If not then its fine. And as mentioned I found the stock recovery as well.
The only reason I was looking to do it this way was because I do not really know what RUU is or how to do any of it. Idk how difficult it would be to relock the boot loader then figure out the RUU thing. Idk what the differences are between that and my phone being rooted as it is now are. I'll have to see if there is a thread that explains this RUU thing to me.
Thanks for the help and suggestion too btw
magicbumm328 said:
Well I do have the stock ROM. Idk if it having super user on it counts as being modified by root though? If not then its fine.
Click to expand...
Click to collapse
SuperUser is same as root, and is fine.
When I say "modifed by root" that often is when a user deletes "bloatware" they don't want, or adds apps, or modifies apps in the system partition.
If you didn't explicitly do any of those things, you should be fine. You will know this is the problem when you install the OTA, as the install will fail with the error message that the "system has been modified".
magicbumm328 said:
The only reason I was looking to do it this way was because I do not really know what RUU is or how to do any of it. Idk how difficult it would be to relock the boot loader then figure out the RUU thing. Idk what the differences are between that and my phone being rooted as it is now are. I'll have to see if there is a thread that explains this RUU thing to me.
Click to expand...
Click to collapse
RUU = ROM update utility
RUU is super easy, you don't really need much guidance to use it. LOCKED or RELOCKED bootloader is required to run it (UNLOCKED if okay if you have s-off). PC required, and the RUU will wipe the phone (so backup any personal data you want to keep, into your PC, cloud, etc.). Aside from those points, RUU is a self-explanatory executable (.exe) program that runs from your PC, and simple to use.
Relocking the bootloader is accomplished easily with a single fastboot command (after connecting phone to PC and booting into fastboot mode): fastboot oem lock
This is also assuming you did the bootloader unlock yourself, and therefore have fastboot/adb setup on your computer.
Running the RUU itself (after relocking the bootloader) is very easy. Boot into OS (some folks have better success being booted into fastboot mode, but I think the RUU is designed to run when booted into OS), connect to PC, then just run the RUU executable on your PC. The RUU executable will then just guide you what you need to do. Its mostly automated, you just need to confirm a few dialogue screens, etc. The RUU will reboot the phone a couple times, install the needed files automatically, and that's really it.
However, since you seem confidant you already have a stock ROM and corresponding stock recovery, I suppose the RUU doesn't gain you too much. But if you hadn't done those steps already, it often saves folks the hassle of tracking down the right stock ROM and recovery for their CID and current firmware. RUU in my opinion is a cleaner install, as it installs a complete stock image (not just updating piecemeal, like an OTA often does).
Also, since OTAs typically need to be installed in sequence, you will probably need to OTA to 2.23 software, than another OTA to 3.42 software. As RUU is a complete image, it would get you to 3.42 software in one fell swoop.
One other thing to note, is that if you are for some reason not connected to AT&T's network (using another carrier, another country, etc.) you will not get any OTAs on the AT&T branded device. AT&T oddity here, most other version will still OTA, even when not connected to a specific carrier. In contrast the AT&T RUU is able to be downloaded and run by anyone with an internet connection and PC (regardless of country, carrier, etc.). I'm under the assumption that most folks on this forum section are on AT&T's network, although I know that some are not (you haven't stated either way).
RUU links are included on my Index thread under heading "RUUs": http://forum.xda-developers.com/showthread.php?t=2751432
Aside from wiping the phone (OTA keeps user data, but you may end up wiping anyway if you run into bugs after OTA), the other downside to RUU is that you need to relock the bootloader. Then you need to unlock the bootloader again (via the HTCDev.com site, or alternately sunshine) if you want to install custom recovery, install custom ROMs, root, etc.
So the choice is really yours (RUU versus OTA). I'm just giving it as an alternative.
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