[Q] 100% stock - One (M8) Q&A, Help & Troubleshooting

Before I begin and before anyone tells me I should read other threads, Id like to say that i HAVE already done that, and happened to find no proper solution.
So to the point: I had my HTC One M8 and flashed the GPE edition RUU but didn't like it, so i followed the thread linked on how to return to sense. that had my phone continuously crashing etc etc with all sorts of problems.
I then found another thread with a guide to flash a stock rom, then unroot, then flash firmware etc etc. I have successfully done that, but OTA updates have verification problems, it says that my phone is running something custom. When I boot into the bootloader, the OS section is also blank.
I have yet to find a full RUU for the International m8 as of posting, but there are ones out for at&t , t-mobile and sprint
So, my main question for all you experts out there: Is it possible to flash an at&t or tmobile ruu without having any problems, since international, at&t and tmobile are all the gsm versions? If not, is there any other possible way to return to stock, with bootloader locked, ota updates working?
My current phone status:
S-OFF, unlocked bootloader, (HTC__001 cid), european mid, stock recovery.
Any answers greatly appreciated.
George

Related

[Q] Questions on rooting, recovery and ROM's (ex-Samsung user)

OK. I'm a little bit lost in the HTC world!
I've had a Samsung Galaxy Note II for the last year and have just replaced it with the HTC ONE (M8). I found the whole rooting and ROM procedure relatively straight forward with the Note II. In a nutshell you:
1) Rooted with a Windows based application
2) Installed / Flashed a recovery system
3) Flashed a custom ROM using a Windows based application called ODIN
And that was that. Pretty straightforward. Having had a nose around the HTC forum it's awash with clever folk using abbreviations and acronyms like CID, RUU and S-OFF...!
My M8 is on EE network in the UK which I know is CID ORANG001. What I would like though is to convert my M8 to a generic European M8 so I can receive the latest HTC updates rather then await EE to push out their version. This therefore prompts me to ask the following questions:
1) Is this something we will be able to achieve?
2) What is the (potential) process to achieve this (assuming something similar for the M7 already exists)?
2) Will over the air updates work?
I've read numerous posts which seem contradicting. Some talk about a simple change of the CID others mention S-OFF as the GOD of everything related to the subject. If I were to guess, changing the CID seems too simple, but I'm guessing once changed to a generic EU CID it's possible to receive HTC's OTA updates? Or am I wrong there? Or having another guess I would assume I'd need to go down the lines similar to Samsung process of rooting or S-OFF (security off?) and flashing a generic stock EU ROM?
So what CAN currently be achieved and what CAN'T currently be achieved?
I guess I could do with a little background on these processes and the terminology used.
Any help, greatly appreciated.
Can :
Unlock the bootloader and flash a custom recovery to install a custom rom based on the latest firmware. You are depending on rom updates from the dev if he updates it to the latest software/firmware
Can't :
S-off
Change cid
Get ota via another rom
Run a ruu because they are simply not available
So to receive ota you need your original stock rom. And before you start messing around please make a stock nandroid backup and store it !
http://forum.xda-developers.com/showthread.php?t=2701376
Chris_c81 said:
OK. I'm a little bit lost in the HTC world!
I've had a Samsung Galaxy Note II for the last year and have just replaced it with the HTC ONE (M8). I found the whole rooting and ROM procedure relatively straight forward with the Note II. In a nutshell you:
1) Rooted with a Windows based application
2) Installed / Flashed a recovery system
3) Flashed a custom ROM using a Windows based application called ODIN
And that was that. Pretty straightforward. Having had a nose around the HTC forum it's awash with clever folk using abbreviations and acronyms like CID, RUU and S-OFF...!
My M8 is on EE network in the UK which I know is CID ORANG001. What I would like though is to convert my M8 to a generic European M8 so I can receive the latest HTC updates rather then await EE to push out their version. This therefore prompts me to ask the following questions:
1) Is this something we will be able to achieve?
2) What is the (potential) process to achieve this (assuming something similar for the M7 already exists)?
2) Will over the air updates work?
I've read numerous posts which seem contradicting. Some talk about a simple change of the CID others mention S-OFF as the GOD of everything related to the subject. If I were to guess, changing the CID seems too simple, but I'm guessing once changed to a generic EU CID it's possible to receive HTC's OTA updates? Or am I wrong there? Or having another guess I would assume I'd need to go down the lines similar to Samsung process of rooting or S-OFF (security off?) and flashing a generic stock EU ROM?
So what CAN currently be achieved and what CAN'T currently be achieved?
I guess I could do with a little background on these processes and the terminology used.
Any help, greatly appreciated.
Click to expand...
Click to collapse
Also not familiar anymore with HTC. After reading and reading and still not finding the exact answers to my questions, so I simply (after unlocking and flash TWRP recovery and backing up) tried to flash Virtuous ROM (1.54.401.5) over my German o2 device (1.12.206.17, CID O2___001). Everything worked except WiFi, so I tried a last call with mikes ARHD Rom 3.1, before going back to stock. And this ROM works brilliantly!
But I would also be happy if the OP questions could be answered...
@Mr Hofs
1. the WiFi problem discribed above could be firmware related?
2. When my Provider o2 brings out an update with firmware, can I simply relock bootloader and push the (perhaps) available firmware.zip it to the device via fastboot like mike explains in his firmware thread?
Edit :
Well that would be weird as both roms the OP flashed are based on 1.54.401 so i would say no.....
Mr Hofs said:
Can :
Unlock the bootloader and flash a custom recovery to install a custom rom based on the latest firmware. You are depending on rom updates from the dev if he updates it to the latest software/firmware
Can't :
S-off
Change cid
Get ota via another rom
Run a ruu because they are simply not available
So to receive ota you need your original stock rom. And before you start messing around please make a stock nandroid backup and store it !
http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
OK thanks. Few more questions if I may.
So from the "can't" list, IF we can get the ability to change CID and have S-OFF in the future, would it provide the ability to receive OTA updates when HTC push them out, or are OTA updates simply out of the game entirely?
Sent from my HTC One_M8 using Tapatalk
Yes that should be possible , all you need then is
Changed cid
Stock rom
Stock kernel
Stock recovery
Or the ruu (if available)
Then the phone is ready for ota updates.
Mr Hofs said:
Yes that should be possible , all you need then is
Changed cid
Stock rom
Stock kernel
Stock recovery
Or the ruu (if available)
Then the phone is ready for ota updates.
Click to expand...
Click to collapse
Great thanks. Last question then, what is RUU?
I'll keep your thread bookmarked and attempt to get a backup in there.
Sent from my HTC One_M8 using Tapatalk
A ruu is a Rom Update Utility and it contains the rom, kernel, firmware, recovery (and some more stuff). When a ruu is installed its like the phone is factory stock.
Mr Hofs said:
A ruu is a Rom Update Utility and it contains the rom, kernel, firmware, recovery (and some more stuff). When a ruu is installed its like the phone is factory stock.
Click to expand...
Click to collapse
OK brilliant thanks. Really appreciate your help.
Sent from my HTC One_M8 using Tapatalk

[Q] Update AT&T or Flash?

Hello Guys, i bought my htc one m8 some months ago and now i'm missing the updates.
My m8 is from US by AT&T with android 4.4.2 and now i live in brazil and it does not show new updates.
I don't know if it is some error or if it is normal from non-us.
So, should I flash a custom ROM or something? I Already have experience with previous android versions but with my htc i'm lost...
What should I do step by step? Unlock boot, S-OFF and flash?
Anyone? I really want to update mu phone...
You will only receive updates for an AT&T device while connected to AT&T's network. Most carriers in the world don't work this way (you will normally get OTAs on most other Android devices) but you can "thank" AT&T for this one. So for AT&T devices, yes this is "normal" and you will never receive an OTA with the phone in its current condition.
You can RUU to the latest AT&T software (which is currently Android 4.4.3): http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Then wait for the Android 4.4.4 RUU to be released (hopefully soon). Backup any personal data before RUU, as your phone will be wiped with this process.
Alternately, you can unlock the bootloader (root, s-off, etc.) as you mentioned, and from there either:
- Install custom ROMs
- Or "convert" your phone to another version so that it can then receive "official" OTAs.
redpoint73 said:
- Or "convert" your phone to another version so that it can then receive "official" OTAs.
Click to expand...
Click to collapse
Oh, thanks for response, but how can i "convert" my phone?
I just install 4.4.3 from your link, and I did not realize the work that would have to rearrange everything again ...
guire01 said:
Oh, thanks for response, but how can i "convert" my phone?
I just install 4.4.3 from your link, and I did not realize the work that would have to rearrange everything again ...
Click to expand...
Click to collapse
Easiest way would probably be to use the Developer's Edition or GPE RUU. S-off or changing the CID may be required (and changing CID requires unlocking the bootloader and root). Either DE or GPE is not carrier branded, so will be better than stock AT&T software to most folks (for whom AT&T is not their carrier). But again with most RUUs, the phone will be wiped.
You may be able to do it piece by piece, although I'm not sure. Unlock the bootloader, install custom recovery, then flash a stock nandroid for the carrier version you want. Change CID (and possibly may need to change MID) and flash the stock recovery for your version. You may need to s-off and also change your firmware (bootloader, radio, etc.). Doing it this way is complex, might not even be possible. Although in theory it should work if you have all the pieces and s-off.
None of these approaches are trivial, and you should expect that your data will be wiped (backup anything important) regardless of the approach.

Phone Not Detecting OTA Updates

Hey everybody! So some quick background info, I just got an M8 and was excited to start playing with it. I unlocked the bootloader, flashed TWRP, and set off to try out some roms. Something I quickly realized was that without updating my phones firmware, I wouldn't be able to make the change from 4.4.2 based roms without encountering some issues. It seems the two ways to do that are an OTA update or s-off and flash it yourself.
So I restored the original rom backup I made, flashed the stock recovery back on (tried 1.58.502.1 and 1.12.502 when the first didn't work) and relocked the bootloader. It still doesn't detect any updates from AT&T's software updater.
The phone is from AT&T and I'm on Cricket's network.
Software number 1.58.502.1
CID: CWS__001
Any help or suggestions are much appreciated. If there's any pertinent information that I didn't include let me know. Thanks in advance.
You need to be connected to AT&T's network to get OTAs. Some folks on here that aren't specifically familiar with AT&T (and don't use them as a carrier) will say that isn't true, that you can OTA on WiFi or on another carrier. But AT&T is the oddball in this regard (at least compared to "international" version owners - not that sure about other US carriers).
You can update to 4.4.3 or 4.4.4 by official RUU (need to relock the bootloader to RUU since you are s-on). But you won't be able to update to 5.0 firmware unless you s-off at this time, since AT&T hasn't released Lollipop yet. Rumor says end of this month, but its just a rumor.
RUUs are linked on my AT&T-specific Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
If you want to s-off (sunshine is the only method) you can then manually update the firmware (including LP firmware). Or even "convert" to another carrier version (such as US Developer's Edition) and then get OTAs.
Thanks for the information! I'll go give that a try now.

Process for converting from one image to another.

I've got an older HTC m8 that I've acquired, however the issue is, that it has the factory AT&T image on it. Originally, it had version 4.28 on it and wasn't showing any available updates. I was able to get the ROM updated to 6.2, however it's still the AT&T based image. Processed used:
1. Got AT&T RUU (Rom Update Urility) from the AT&T site.
2. Ensured the bootloader was locked and ran the utility. New Image was included in the download, so everything worked fine.
I want to remove the AT&T factory image and replace it with an unlocked "Global HTC" image. Can someone please explain the process in a concise manner. I have read so many conflicting efforts out there (most with broken links to image files). Any and all direction would be greatly appreciated. I have yet to figure out how to do a "fastboot getver all".
If the intent is to simply get a Euro ROM on the phone, the easiest way is to unlock the bootloader using HTCDev.com process. Then install custom recovery TWRP 3.0.2, and flash a stock ROM or custom ROM close to unbranded Euro ROM.
Getting the phone to complete stock Euro image (such as RUU) is more complicated. You would need to s-off the phone using sunshine app, which costs $25 US. Then change phone's CID (carrier ID) and MID (model ID) with adb commands. Only then, can you run the official Euro RUU.
But its not worth the cost and effort to do so, my opinion it doesn't gain anything; except the proper Euro radio baseband firmware. But if the radio is already working fine for you carrier, I wouldn't mess with any of that. Just unlock bootloader, install custom recovery and flash a ROM that meets your needs and preferences.
Future Euro OTA updates would be another benefit of "fully converting" to Euro stock by RUU. But unfortunately at this point, we will not be getting any major OTA updates on this phone.

Soft-Bricked HTC One M9 - Missing IMEI/SIM/Device Information after flash.

Hi all,
I've been spending the last couple of days on these forums and google trying to resolve the issues I have been having nonstop since I decided to unlock and flash my HTC One M9 but I've run into a wall and don't know what else I can do to fix my phone. Stupidly I did not create a backup before flashing so I think I am up **** creek as I cannot install stock roms either. I've have been following the guides but having issues the whole time through with the M9 for some reason.
HTC One M9 - Telstra (Australia) S-ON
After lots of ****ing around I have successfully managed to Unlock, Install TWPR, Flash SuperSU, Flash Android Revolution custom rom. This has wiped all my IMEI/SIM settings etc. I managed to find the stock telstra RUU to got back to stock rom as this is how to fix this problem, except when I try to install I get errors saying 'Device id/information not found'
Does anyone have any similiar experiences or know of anyway to fix this? Any and all help is appreciated.
It's impossible to help without knowing your current firmware and the firmware of the RUU you wanted to flash.
Be aware that there is not "the stock telstra RUU". RUUs are always stock and normally HTC creates one for each firmware version of their phones. The catch is that they don't get distributed officially (unless they're made for US carriers) but leaked by insiders.
However, the problem with the IMEI is explained in the ReadMe thread.

Categories

Resources