Develop Bugs

Help installing a "generic" ROM

Long story short, I purchased a One X from Amazon that was supposed to be an unlocked international version. Turns out it's a T-Mobile Germany version.
Everything works fine, but it has bloat on it and it's on a slightly older software version (1.28.111.10) and I'd like to make it a generic version that I can install updates on when they come out.
Can someone point me in the right direction? Where can I get a stock Generic rom for the Tegra 3 version?
I'm assuming my first steps are:
Unlock at HTC Dev
Install Clockwork Mod Recovery
I'm kind of a noob at this, or at least a novice, so any help would be appreciated. I was going to send the phone back, but it seems a shame if I can basically get it to be the way I want anyway.

For what i understand you want to be able to recieve OTAs, right?
You need stock recovery to update the phone, and i dont know if changing your CID will make the device recieve the different updates.
Why not try some stock roms?
http://forum.xda-developers.com/showthread.php?t=1546970
http://forum.xda-developers.com/showthread.php?t=1648527
that wont be able to receive OTAs but hey its updated.
I never used any of those 2 but mike is doing a good work with ARHD which might be an option.

fredfb said:
For what i understand you want to be able to recieve OTAs, right?
You need stock recovery to update the phone, and i dont know if changing your CID will make the device recieve the different updates.
Why not try some stock roms?
http://forum.xda-developers.com/showthread.php?t=1546970
http://forum.xda-developers.com/showthread.php?t=1648527
that wont be able to receive OTAs but hey its updated.
I never used any of those 2 but mike is doing a good work with ARHD which might be an option.
Click to expand...
Click to collapse
Okay, so to flash one of those stock ROMs, I have to flash Clockwork first, flash the rom, then flash stock recovery again to be able to get updates, correct? I suppose I could just leave it Clockwork and then flash the updates manually.

Once you flash a custom ROM, even based off of stock, you do not want to receive OTA's as that could mess up with the Dev did and cause you issues. The Devs will keep their ROMs up to date so you just flash their updates manually with Clockworkmod.

greyhulk said:
Okay, so to flash one of those stock ROMs, I have to flash Clockwork first, flash the rom, then flash stock recovery again to be able to get updates, correct? I suppose I could just leave it Clockwork and then flash the updates manually.
Click to expand...
Click to collapse
You see, i never tried that. I dont know if those stock roms are able to recieve the update, but you could flash them using CWR.
And the devs will most likely update the stock roms. its not really be a big issue. You can always use something like titanium backup to save everything you want, even tho flashing an updated version of stock rom shouldnt mess anything up.

greyhulk said:
Long story short, I purchased a One X from Amazon that was supposed to be an unlocked international version. Turns out it's a T-Mobile Germany version.
Everything works fine, but it has bloat on it and it's on a slightly older software version (1.28.111.10) and I'd like to make it a generic version that I can install updates on when they come out.
Can someone point me in the right direction? Where can I get a stock Generic rom for the Tegra 3 version?
I'm assuming my first steps are:
Unlock at HTC Dev
Install Clockwork Mod Recovery
I'm kind of a noob at this, or at least a novice, so any help would be appreciated. I was going to send the phone back, but it seems a shame if I can basically get it to be the way I want anyway.
Click to expand...
Click to collapse
If I were you I would send the phone back and demand the version you ordered.
You wont be able to flash a WWE RUU because we don't have S-Off yet however as everyone has mentioned above you can Unlock via HTCDev, flash Clockwork and then flash away with your desired custom rom.

[Q] And the troubles begin again... Help! (stuck at boot)

I was trying to update my firmware in the hope of using one of the custom roms available, and my M8 is now stuck on the boot screen and will not go further. Here is what I did:
Currently have a GPE M8. It is S-Off, SuperCID, Unlocked, and converted to T-Mobile (Sense) stock rom.
Was on 1.54.401.5 firmware attempting to update to a 2.22.xxx firmware.
The exact process I used was:
Boot into fastboot
fastboot oem rebootRUU
fastboot flash zip firmware.zip twice (successful after 2nd time)
fastboot reboot
After this, it will not go past the default boot screen.
I then tried to revert back to 1.54.401.5 firmware using the same process. This time, it will reboot once after the stock boot screen and go into recovery. Still unable to get back to the OS.
What am I doing wrong and how do I get out of it? :crying:
[edit] I tried to install a newer firmware again, as well as a couple of different roms. No luck, still getting stuck at the boot screen or automatically rebooting into recovery. Had to resort to using the T-Mobile RUU to get back a working phone. I still don't know what went wrong with my attempt at trying to install a new firmware or rom. [/edit]

The firmware includes an incompatible kernel, just flash a different kernel or re-install the rom and you should be alright

thom109 said:
The firmware includes an incompatible kernel, just flash a different kernel or re-install the rom and you should be alright
Click to expand...
Click to collapse
I did try to install a couple different roms after installing the firmware, but either the rom fails to install, or even if it appears to install, it still gets stuck at the white boot screen.
I also don't understand how the kernal can be incompatible. In all the threads I've gone through of the custom roms (mainly ARHD), it's always the same story. "Just flash the 2.22.xxxx firmware and you'll be fine". In the threads specifically related to the updated roms, it's the same thing, just flash and go, regardless if you are on stock and some other rom. I, and only a few others, seem to have no luck actually flashing the 2.22.xxxx firmware.

Mpegger said:
I did try to install a could different roms after installing the firmware, but either the rom fails to install, or even if it appears to install, it still gets stuck at the white boot screen.
I also don't understand how the kernal can be incompatible. In all the threads I've gone through of the custom roms (mainly ARHD), it's always the same story. "Just flash the 2.22.xxxx firmware and you'll be fine". In the threads specifically related to the updated roms, it's the same thing, just flash and go, regardless if you are on stock and some other rom. I, and only a few others, seem to have no luck actually flashing the 2.22.xxxx firmware.
Click to expand...
Click to collapse
hmm weird, I have no idea what's going on here ... I had some issues after flashing firmware but new kernel and it worked just fine.
Maybe something in this thread could help you? http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048

thom109 said:
hmm weird, I have no idea what's going on here ... I had some issues after flashing firmware but new kernel and it worked just fine.
Maybe something in this thread could help you? http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
Click to expand...
Click to collapse
Tried that too, same issue. Tried with the phone locked and unlocked, manually with fastboot and automatically via external SDcard (as in that thread), installed SkyDragon, ARHD, and stock after installing the firmware, and it still fails with the same issue. Even trying to revert back to the current firmware after trying to install 2.22.xxx results in the same problem, and the only way to fix it is with the RUU.
I think what I'll try next is to install the rom first, then try to install the firmware. Maybe in that order it will work. But it still doesn't make much sense that I can't install the newer firmware when so many others have had no problems.

Mpegger said:
Tried that too, same issue. Tried with the phone locked and unlocked, manually with fastboot and automatically via external SDcard (as in that thread), installed SkyDragon, ARHD, and stock after installing the firmware, and it still fails with the same issue. Even trying to revert back to the current firmware after trying to install 2.22.xxx results in the same problem, and the only way to fix it is with the RUU.
I think what I'll try next is to install the rom first, then try to install the firmware. Maybe in that order it will work. But it still doesn't make much sense that I can't install the newer firmware when so many others have had no problems.
Click to expand...
Click to collapse
always install rom first then firmware

(Q) OTA update breaks my wifi!?

Right so here goes, story so far, HTC m8, ORANG001 cid, bootloader unlocked and rooted but s-on. Flashed ARHD 11.2 all working happy days. I then saw ARHD 20.1 is out but seeing as it needs a 3.***** based firmware i was unable to flash it. So I thought i will use a stock nandroid for my carrier from this thread http://forum.xda-developers.com/showthread.php?t=2701376 re flash the corresponding stock recovery and then do s-off with Sunshine. Well even thou i am back to stock sunshine still wouldn't work :crying: I had a notification that a OTA was available, and I thought maybe that will make a difference, so it installed fine but then i noticed my WiFi wont work, ie the actual toggle in settings will not flick over it just goes grey. I fastbooted getvar-all and noticed that i am still on a 2.26.61.1 base which is what ARHD 11.2 was working on, Is this where my problems are??
If i download the OTA (1.70.61.3 i presume) and then before installing it extract the firmware , then install the OTA , then manually flash the firmware would this help/solve my problems or am i way off?
I have literary been through post after post trying to figure this mess out, i am basically stuck at the moment, can't upgrade, can't downgrade, can't s-off
Any guiance would be amazing guys, thank so much in advance
Gareth

ARHD 21 is based on 3.28.401.7 and if you don't have that same Firmware (3.28.401.6 or 3.28.401.7) your wifi don't work.
If you flash a 4.4.3 Rom (3.28.401.5) your Wifi will work with that Rom.

jkolner said:
ARHD 21 is based on 3.28.401.7 and if you don't have that same Firmware (3.28.401.6 or 3.28.401.7) your wifi don't work.
If you flash a 4.4.3 Rom (3.28.401.5) your Wifi will work with that Rom.
Click to expand...
Click to collapse
Yeah I understand that, thats why I haven't attempted to use arhd 21 yet. My WiFi breaks after I use a stock ROM and do the first ota that I am prompted to do. So from a stock ROM not custom anything, recovery is stock as well
Sent from my HTC One (M8)

Peggy1104 said:
Yeah I understand that, thats why I haven't attempted to use arhd 21 yet. My WiFi breaks after I use a stock ROM and do the first ota that I am prompted to do. So from a stock ROM not custom anything, recovery is stock as well
Sent from my HTC One (M8)
Click to expand...
Click to collapse
Hey. I know this is from a long time ago but did you manage to find a solution? I'm having the same problem just now. Went back to stock NAND from that thread and first OTA kills wifi.
Downloading the next OTA via internet pass-through so hopefully that sorts it.
Thanks
Edit - Fixed it by downloading OTA's via internet pass-through

Azzabear said:
Went back to stock NAND from that thread and first OTA kills wifi.
Click to expand...
Click to collapse
Are you sure the stock nandroid matched the firmware previously on the phone (before OTA)? Did WiFi work after you restored the stock nandroid?

redpoint73 said:
Are you sure the stock nandroid matched the firmware previously on the phone (before OTA)? Did WiFi work after you restored the stock nandroid?
Click to expand...
Click to collapse
The firmware matched. The Wifi worked after restoring but after doing the first update it stopped. I left my phone to download the next few OTA's via internet pass-through and the Android 4.4.4 update fixed the Wifi again.
I'm guessing that update changed something to do with the radio that a nandroid restore can't change with S-On.
If anyone else is having this problem, restore the stock nandroid backup from here, once finished flash the stock recovery, and let the OTA's do their thing. The first can use Wifi, the 2nd and 3rd will need internet pass-through (found in Mobile Network Sharing in settings), and the 4th can use Wifi again.

Azzabear said:
I'm guessing that update changed something to do with the radio that a nandroid restore can't change with S-On.
Click to expand...
Click to collapse
Each OTA will typically deploy a WiFi firmware module that corresponds to the software in that OTA. If not, than something was wrong with that OTA. Its not unheard of, I've seen a few reports of full stock M8's losing WiFi after an OTA.
A nandroid restore only effects the partitions that you specify (system, boot.img, cache, data). That's only 4 partitions, and this phone has something like 40 partitions.
These comments are just academic, than anything. I'm glad to see your issue was fixed by the subsequent OTAs.

redpoint73 said:
Each OTA will typically deploy a WiFi firmware module that corresponds to the software in that OTA. If not, than something was wrong with that OTA. Its not unheard of, I've seen a few reports of full stock M8's losing WiFi after an OTA.
A nandroid restore only effects the partitions that you specify (system, boot.img, cache, data). That's only 4 partitions, and this phone has something like 40 partitions.
These comments are just academic, than anything. I'm glad to see your issue was fixed by the subsequent OTAs.
Click to expand...
Click to collapse
RUU THE B*TCH! is always the right answer.

Stupid question: Can the firmware be updated when running a custom ROM?

I've been reading on one of the other threads here that if you take an OTA while running stock + twrp, the firmware won't update, but you can then update it using fastboot.
Is it possible to update the firmware (not system) on a device using fastboot if it's running a custom ROM, or is it still required to restore to stock prior to taking the update?
Thank you.

Yes.
If you flash a firmware pulled straight from an OTA it will replace twrp with the stock recovery. Also flashing firmware may brake cell service on custom roms. If its a custom firmware zip that has boot, recovery, rcdata etc removed than you should be okay.
For example I'm using MaximusHD rom which is based on .401 (WWE/Europe) firmware. If i flash the US T-Mobile firmware I will loose cell service since the actual firmware files within /system are not made to work with that particular radio/firmware. I'll then have to flash the firmware/radio that was released for .401 or switch to a rom made with the T-mobile firmware.
BEWARE flashing firmware is a risky business. I've had HTC phones for years and the M9 i had kicked the bucket when i flashed a firmware package like i had done hundreds of times before. A random fluke bricked it.
So be careful what you do and accept possibly braking the phone before you even attempt something.

Android 6 update w/ TWRP?

Hello,
I have rooted my HTC One m8(No S-OFF). It also has TWRP and it's on Android 5.0.1/HTC Sense 6
I googled and read about reverting to stock recovery and then doing an OTA upgrade of the OS. But I'd rather not go back to stock and then TWRP back again.
Is there any way or instructional to follow that can enable me to update to Android 6 whilst keeping TWRP and my root settings on.
Any help is appreciated

My experience, is that Marshmallow ROMs work fine on Lollipop firmware. I've been doing so since December, for no better reason than I've been too lazy to update my firmware.
So that means you should be able to just restore the proper Marshmallow TWRP backup for your version, and just run that without updating anything else. Although, be sure to leave yourself an escape plan, just in case it doesn't work (either your own LP backup, or be prepared to use one from the collection).
However, for best compatibility, you should really update your firmware. And doing so, either by flashing stock firmware, OTA, or RUU by "official" means (and official/signed means are what you need to use, since you are s-on) will by definition wipe out TWRP.
But honestly, flashing TWRP back to the phone is easy. You just download the .img file to your computer, than flash with a single fastboot command, with the phone connected. This is actually a fast and simple process, when compared to the other stuff you are talking about doing (restoring stock backup and recovery, OTA update).
Plus, since you are updating to Marshmallow, you'll also want to update to TWRP 3.0.2 anyway.

redpoint73 said:
My experience, is that Marshmallow ROMs work fine on Lollipop firmware. I've been doing so since December, for no better reason than I've been too lazy to update my firmware.
So that means you should be able to just restore the proper Marshmallow TWRP backup for your version, and just run that without updating anything else. Although, be sure to leave yourself an escape plan, just in case it doesn't work (either your own LP backup, or be prepared to use one from the collection).
However, for best compatibility, you should really update your firmware. And doing so, either by flashing stock firmware, OTA, or RUU by "official" means (and official/signed means are what you need to use, since you are s-on) will by definition wipe out TWRP.
But honestly, flashing TWRP back to the phone is easy. You just download the .img file to your computer, than flash with a single fastboot command, with the phone connected. This is actually a fast and simple process, when compared to the other stuff you are talking about doing (restoring stock backup and recovery, OTA update).
Plus, since you are updating to Marshmallow, you'll also want to update to TWRP 3.0.2 anyway.
Click to expand...
Click to collapse
Thanks redpoint73.
My chief motivation behind moving to Android 6 is a sound problem I've been having lately. I installed the AcousticX sound mod but when I listen to audiobooks, I hear a clipping sound sometimes.
The developer over @ AcousticX suggested a few things and one of which was making the switch to marshmallow.
thread: http://forum.xda-developers.com/showthread.php?p=68881108#post68881108
From some reading and your suggestions, I gathered the right way to go about this is, is to flash stock recovery(overriding twrp). Do an OTA upgrade(1.6 gb download/install) and afterwards reinstall TWRP and whatever else was previously done.
Am I correct in surmising this?
Thanks

AadilK said:
From some reading and your suggestions, I gathered the right way to go about this is, is to flash stock recovery(overriding twrp). Do an OTA upgrade(1.6 gb download/install) and afterwards reinstall TWRP and whatever else was previously done.
Am I correct in surmising this?
Click to expand...
Click to collapse
Not only the stock recovery, but you also need to restore the unrooted TWRP backup (never rooted ROM, "unrooting" doesn't work). Since having root will prevent OTA.
The full process is described here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
The other option, depending on what M8 version you have, may be to RUU to Marshmallow. That allows you skip a lot of the steps needed in the previous method (restoring a never rooted TWRP backup, restoring stock recovery, OTA updated) but adds a couple other steps (relock bootloader to RUU, unlock it again after RUU to flash TWRP); plus the RUU will wipe all user data on the device.
So its a judgment call for you (if your version has RUU) what path is preferred.