Develop Bugs

GSM Google Nexus coming tomorrow, what should I do immediately?

Hey everyone,
Im relatively confused about this phone since there are so many threads that are for the other versions(VZW/Sprint/Intnl).
What Im looking for is any help(direction?) as to what I should do first on my Nexus that I ordered from Google Play.
What is the first thing I should do(root or unlock bootloader?) and what should I download(Roms or kernals?). Any links to said advice would be much appreciated also.
Many thanks in advance.

Put sim in . Then battery then back cover . Then best of all turn it on
Sent from my Galaxy Nexus using xda premium

stewartk said:
Put sim in . Then battery then back cover . Then best of all turn it on
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Touche...
Thank you for the obvious and the laugh. However, I really am looking to get past the two weeks of thread reading, and get guidance from those who have this Google Play version with working roms and stuff.

unlock the bootloader, you can decide to root or flash whatever later. unlocking the bootloader does a factory reset which is why you want to do it before you do any setup or add anything to the phone

http://forum.xda-developers.com/showthread.php?t=1529058
This has everything you need to know.

nodstuff said:
http://forum.xda-developers.com/showthread.php?t=1529058
This has everything you need to know.
Click to expand...
Click to collapse
Ok, now I saw this, and I might sound newbish here, but the title of that thread is for the VZA/Sprint/GSM versions of the phone. To my understanding, even the unlocked GSM version originally sold is not the same as the current one in the Google Play store.
If the link above will work for all the phones including mine then that is what I was looking for.

HyperM3 said:
Ok, now I saw this, and I might sound newbish here, but the title of that thread is for the VZA/Sprint/GSM versions of the phone. To my understanding, even the unlocked GSM version originally sold is not the same as the current one in the Google Play store.
If the link above will work for all the phones including mine then that is what I was looking for.
Click to expand...
Click to collapse
Lucky for you even if u unlock the boot loader after u sign in and sync all ur stuff your data won't be erased... something about the Takju version that allows users to unlock boot loader without wiping any data =P
- Google

HyperM3 said:
Ok, now I saw this, and I might sound newbish here, but the title of that thread is for the VZA/Sprint/GSM versions of the phone. To my understanding, even the unlocked GSM version originally sold is not the same as the current one in the Google Play store.
If the link above will work for all the phones including mine then that is what I was looking for.
Click to expand...
Click to collapse
It will work. Yours is still GSM, yakju, takju, yakjuux, whatever. Its still GSM.

first thing you should is jump up and down, and pat yourself on the back for being tied to your carrier for a phone upgrade

I would unlock the bootloader before anything else...
Then if you're feeling brave (and before you start configuring the device to your liking) flash a third-party ROM based on 4.0.3/4 (The most recent ICS versions):
l'd recommended Cyanogenmod 9 nightlies if you like to be on the bleeding edge (Although you might have to get used to flashing EVERY day, which isn't so bad once you get used to it)
Or, moving to something like LiquidSmooth (http://forum.xda-developers.com/showthread.php?t=1555667)
or
EaglesBlood ROM (http://forum.xda-developers.com/showthread.php?t=1388728).
Each of which will bring different things to the table, you'll have to do your research as to which one you'd like if you go that way.
Alternatively, just stay on stock ROM and enjoy your phone the way they intended you to...

^ Thank you for that. I was actually confused as to what order Im supposed to do things(root, unlock bootloader...Rom...Kernal??)
Ive seen a lot of positive reviews for an AOKP rom and a Frances(?) Kernal. Anyone agree they make a good match?

HyperM3 said:
^ Thank you for that. I was actually confused as to what order Im supposed to do things(root, unlock bootloader...Rom...Kernal??)
Ive seen a lot of positive reviews for an AOKP rom and a Frances(?) Kernal. Anyone agree they make a good match?
Click to expand...
Click to collapse
You unlock the bootloader first because it wipes your phone, SD card as well.
Flash clockwork mod recovery.
Flash a custom rom and kernel.
Sorted.

The guide I wrote (previously linked) details how you can also back up your applications (not that you'll really have any to begin with...but if you decide to wait) without root.
Then unlock and restore...and backup again with titanium for all future restorations.

nodstuff said:
It will work. Yours is still GSM, yakju, takju, yakjuux, whatever. Its still GSM.
Click to expand...
Click to collapse
This is true and if you use the toolkit i linked below you will need to know that your phone is specifically the takju or its also labeled as the gsm version with google wallet
GNex TOOLKIT V6.2:
http://forum.xda-developers.com/showthread.php?t=1392310

HyperM3 said:
^ Thank you for that. I was actually confused as to what order Im supposed to do things(root, unlock bootloader...Rom...Kernal??)
Ive seen a lot of positive reviews for an AOKP rom and a Frances(?) Kernal. Anyone agree they make a good match?
Click to expand...
Click to collapse
it's fanco kernel

[Q] Rooting Questions

Hi, I have looked around for a while, but have not received direct answers to these questions, any help would be appreciated. I am not new to rooting since I have rooted and flashed my previous phone (HTC Wildfire S), but these questions were unanswered to me, irregardless of where I looked.
-First, I know that when you gain root access you may toy around with your phone, but by rooting your device do you damage it? I am concerned about this because when I had a Wildfire S I rooted it and within a week it had MAJOR bugs, without flashing or moving any setting.
-Second, how do you perform a nandroid backup? I know that this is kind of a safety net to your device if it ever gets soft-bricked, but how do you do it? I have not had a clear explanation on how to do it.
-Third, I know that CyanogenMod is one of the most stable custom ROMS that there is out there, but does it offer Pure Android?
-Fourth, if any of you know any good (and stable) custom ROMS for the T-Mobile Galaxy S3, could you send them to me please?
-Fifth, I know that with some ROMS you lose certain features (such as video playback in some ROMS, yeah I know sounds terrible) but if I flash a ROM that does support this, do I gain the feature back or do I lose the feature forever?

Going through the same process
amezcuaesteban said:
Hi, I have looked around for a while, but have not received direct answers to these questions, any help would be appreciated. I am not new to rooting since I have rooted and flashed my previous phone (HTC Wildfire S), but these questions were unanswered to me, irregardless of where I looked.
-First, I know that when you gain root access you may toy around with your phone, but by rooting your device do you damage it? I am concerned about this because when I had a Wildfire S I rooted it and within a week it had MAJOR bugs, without flashing or moving any setting.
-Second, how do you perform a nandroid backup? I know that this is kind of a safety net to your device if it ever gets soft-bricked, but how do you do it? I have not had a clear explanation on how to do it.
-Third, I know that CyanogenMod is one of the most stable custom ROMS that there is out there, but does it offer Pure Android?
-Fourth, if any of you know any good (and stable) custom ROMS for the T-Mobile Galaxy S3, could you send them to me please?
-Fifth, I know that with some ROMS you lose certain features (such as video playback in some ROMS, yeah I know sounds terrible) but if I flash a ROM that does support this, do I gain the feature back or do I lose the feature forever?
Click to expand...
Click to collapse
I'm going through this same process now, and am new also--I rooted an old mytouch 3g slide and flashed CM7 on it. Afterwards it was bit buggy, but it was a bit buggy before too, hardware issues I think.
I think rooting in and of itself shouldn't mess up your phone, but if you don't do it correctly it could surely screw things up.
Do you have the T999 or T999L? which version will matter in terms of ROM flashing details (for example, I have the T999L, which is the LTE version)
Let me know of the progress you have on these questions!

I'm going through this same process now, and am new also--I rooted an old mytouch 3g slide and flashed CM7 on it. Afterwards it was bit buggy, but it was a bit buggy before too, hardware issues I think.
I think rooting in and of itself shouldn't mess up your phone, but if you don't do it correctly it could surely screw things up.
Do you have the T999 or T999L? which version will matter in terms of ROM flashing details (for example, I have the T999L, which is the LTE version)
Let me know of the progress you have on these questions!
Click to expand...
Click to collapse
I unfortunately have the T999. I know that mine won't be able to get LTE which is sad, but is this something that I MUST look into before flashing a ROM? Like are the t999 and T999L that different, I mean it is ONE chip.

amezcuaesteban said:
I unfortunately have the T999. I know that mine won't be able to get LTE which is sad, but is this something that I MUST look into before flashing a ROM? Like are the t999 and T999L that different, I mean it is ONE chip.
Click to expand...
Click to collapse
It's something to be aware of. I believe most of the T-mobile gs3 ROMS are built with the T999 in mind though, so you shouldn't really worry too much.
DocHOliday77's thread [INFO] [FAQ] Galaxy S3 w/ LTE - SGH-T999L & SGH-T999N points to some discrepancies between the T999 and T999L though
If you find my answers useful, push my thanks button! I need 10 to get full xda credentials

amezcuaesteban said:
Hi, I have looked around for a while, but have not received direct answers to these questions, any help would be appreciated. I am not new to rooting since I have rooted and flashed my previous phone (HTC Wildfire S), but these questions were unanswered to me, irregardless of where I looked.
-First, I know that when you gain root access you may toy around with your phone, but by rooting your device do you damage it? I am concerned about this because when I had a Wildfire S I rooted it and within a week it had MAJOR bugs, without flashing or moving any setting.
Rooting does nothing but give you SuperUser access to your phone. That is literally all it does. Now what you do with it can cause major headaches.
-Second, how do you perform a nandroid backup? I know that this is kind of a safety net to your device if it ever gets soft-bricked, but how do you do it? I have not had a clear explanation on how to do it.
Install a custom recovery such as TWRP or Clockwork (CWR), then boot into recovery via key combo (Power+VolDown+Home, see blue light at top left and release the keys). From there you will see how Back Up/Restore options.
-Third, I know that CyanogenMod is one of the most stable custom ROMS that there is out there, but does it offer Pure Android?
Many ROMs out there. Just need to read the OPs for what you want.
-Fourth, if any of you know any good (and stable) custom ROMS for the T-Mobile Galaxy S3, could you send them to me please?
Not allowed and don't ask this type of question. All it ever turns into is an EPeen contest and will surely get the thread closed down.
-Fifth, I know that with some ROMS you lose certain features (such as video playback in some ROMS, yeah I know sounds terrible) but if I flash a ROM that does support this, do I gain the feature back or do I lose the feature forever?
This is exactly what a Nandroid backup is for. Something that you don't like or something borks, then just boot into recovery and restore your last working ROM backup. Kind of the point. Not sure I have ever heard of a ROM losing video playback as all are pretty much optimized nowadays.
Click to expand...
Click to collapse
See my edits in Red.
el_garicimo said:
I'm going through this same process now, and am new also--I rooted an old mytouch 3g slide and flashed CM7 on it. Afterwards it was bit buggy, but it was a bit buggy before too, hardware issues I think.
I think rooting in and of itself shouldn't mess up your phone, but if you don't do it correctly it could surely screw things up.
Do you have the T999 or T999L? which version will matter in terms of ROM flashing details (for example, I have the T999L, which is the LTE version)
Let me know of the progress you have on these questions!
Click to expand...
Click to collapse
See my part above about Rooting. You are correct in that it doesn't affect anything whatsoever. It is what you do with it.
I am pretty sure that most are based off T999 code and in order to have the LTE, you have to flash the LTE modem. Might want to ask Doc about that as he has/had the T999L.
Also, CM7 was a long time ago and things have massively progress since then.
amezcuaesteban said:
I unfortunately have the T999. I know that mine won't be able to get LTE which is sad, but is this something that I MUST look into before flashing a ROM? Like are the t999 and T999L that different, I mean it is ONE chip.
Click to expand...
Click to collapse
See my reply above.
el_garicimo said:
It's something to be aware of. I believe most of the T-mobile gs3 ROMS are built with the T999 in mind though, so you shouldn't really worry too much.
DocHOliday77's thread [INFO] [FAQ] Galaxy S3 w/ LTE - SGH-T999L & SGH-T999N points to some discrepancies between the T999 and T999L though
If you find my answers useful, push my thanks button! I need 10 to get full xda credentials
Click to expand...
Click to collapse
This is false. You don't need 10 Thanks to get your credentials. You need 10 posts in order to lose the Captcha and be able to post in the Development threads. Please do not post a question in the Dev thread or even worse a "Thanks". This link should explain it all for you.

Differences between m8_ul and m8_wl

Hey guys,
I saw these two codenames flying around here and I just wanted to know what the difference is.
Greetz.

forgiveMySin said:
Hey guys,
I saw these two codenames flying around here and I just wanted to know what the difference is.
Greetz.
Click to expand...
Click to collapse
These are product numbers, the m8_ul is the sim unlocked/unbranded model, whereas the m8_wl is the Verizon carrier model
More info and how to check your number below:
http://droider.eu/2014/09/20/htc-one-m8-models/

gsmyth said:
whereas the m8_wl is the Verizon carrier model
Click to expand...
Click to collapse
Some additional observations: Based on your link, codenames with wl, wlv or whl are for CDMA variants (Sprint, Verizon).
While all GSM variants are essentially the same hardware (only some minor cosmetic differences on some carrier branded versions) the CDMA variant is actually different hardware and should be avoided unless your carrier uses CDMA (probably want to avoid unless you are on US Sprint or Verizon).
Additionally, you should not flash any mods on a GSM variant that are intended for CDMA versions; or vice versa. Doing so may result in a brick!

Thanks you two,
I already knew that with CDMA, but thanks anyway

redpoint73 said:
Some additional observations: Based on your link, codenames with wl, wlv or whl are for CDMA variants (Sprint, Verizon).
While all GSM variants are essentially the same hardware (only some minor cosmetic differences on some carrier branded versions) the CDMA variant is actually different hardware and should be avoided unless your carrier uses CDMA (probably want to avoid unless you are on US Sprint or Verizon).
Additionally, you should not flash any mods on a GSM variant that are intended for CDMA versions; or vice versa. Doing so may result in a brick!
Click to expand...
Click to collapse
What hardware is different? This is news to me . . . How are all the AOSP ROMs unified then? How is the HK adsp flashable on all variants?

Captain_Throwback said:
What hardware is different? This is news to me . . . How are all the AOSP ROMs unified then? How is the HK adsp flashable on all variants?
Click to expand...
Click to collapse
Would have been nice if we actually had service manuals to make these types of comparisons without having to disassemble the phone just to take a look at actual hardware differences.
But it's not like they'd put in something like that seeing as the phone only costs $700 At least they could have a service manual book that they can sell seperately.
http://provinspc2.free.fr/ftpSM/index.php/HTC/
...

Captain_Throwback said:
What hardware is different? This is news to me . . . How are all the AOSP ROMs unified then? How is the HK adsp flashable on all variants?
Click to expand...
Click to collapse
I was told over and over when I first started messing with my phone that I couldn't flash an international version of a ROM on my VZW phone but I thought really, how different can they be?
I live outside the US and don't use CDMA at all and couldn't get my ****ty MVNO provider to work for data no matter how many APN settings I tried. I flashed a int'l version of the ROM and then the stock VZW kernel.
It works 100% fine, I have none of the verizon crap on my phone including perpetual roaming notifications. LTE hasn't worked (I think there's a band difference with my type of phone) but I don't really want to pay a bunch extra for it anyway so I don't care; i'll stick with 3G and wifi.
I'm not going to go flash some non-VZW firmware or anything but you're not going to brick your phone with a non-CDMA ROM. You just might have a phone that doesn't want to connect to the network or access wifi.

AmbitiousDonut said:
I'm not going to go flash some non-VZW firmware or anything but you're not going to brick your phone with a non-CDMA ROM. You just might have a phone that doesn't want to connect to the network or access wifi.
Click to expand...
Click to collapse
I'd tread carefully about doing any such thing. I've seen at least 1 or 2 folks on here that bricked their CDMA M8 after flashing a GSM ROM or recovery (can't remember precisely which).
---------- Post added at 10:39 AM ---------- Previous post was at 10:33 AM ----------
Captain_Throwback said:
What hardware is different? This is news to me . . . How are all the AOSP ROMs unified then? How is the HK adsp flashable on all variants?
Click to expand...
Click to collapse
Maybe I've got the details wrong. But that was my understanding based on post by others. And as just mentioned, I've seen at least a report or 2 of bricking after flashing a GSM mod on a CDMA phone.
I just saw it mentioned on another thread that CM11 supports CDMA variants, so I'm curious about that as well. But if the hardware is the same, why are the recoveries (at least TWRP) different? I'm asking as much as making a point here, as again I'm curious.
I'd still maintain folks should not flash ROMs not meant for their type (GSM versus CDMA); or at a minimum to tread very carefully if you decide you want to. It should go without saying, if a ROM is not stated to support your carrier version, you should proceed with caution and at least do some research before proceeding.
And not sure what the intent of the OP is; but if they are looking to make a purchase, I also do not recommend any of the CDMA variants unless your carrier has a CDMA network (which is very unlikely unless you are on Verizon or Sprint in the US).

redpoint73 said:
I'd tread carefully about doing any such thing. I've seen at least 1 or 2 folks on here that bricked their CDMA M8 after flashing a GSM ROM or recovery (can't remember precisely which).
---------- Post added at 10:39 AM ---------- Previous post was at 10:33 AM ----------
Maybe I've got the details wrong. But that was my understanding based on post by others. And as just mentioned, I've seen at least a report or 2 of bricking after flashing a GSM mod on a CDMA phone.
I just saw it mentioned on another thread that CM11 supports CDMA variants, so I'm curious about that as well. But if the hardware is the same, why are the recoveries (at least TWRP) different? I'm asking as much as making a point here, as again I'm curious.
I'd still maintain folks should not flash ROMs not meant for their type (GSM versus CDMA); or at a minimum to tread very carefully if you decide you want to. It should go without saying, if a ROM is not stated to support your carrier version, you should proceed with caution and at least do some research before proceeding.
And not sure what the intent of the OP is; but if they are looking to make a purchase, I also do not recommend any of the CDMA variants unless your carrier has a CDMA network (which is very unlikely unless you are on Verizon or Sprint in the US).
Click to expand...
Click to collapse
The recoveries aren't different (anymore) - at least not TWRP.
The hardware is the same on all M8 variants (besides Dual SIM). The radios differ, and there is some carrier customization in the ramdisk and build.prop. But that's it.

redpoint73 said:
I'd tread carefully about doing any such thing. I've seen at least 1 or 2 folks on here that bricked their CDMA M8 after flashing a GSM ROM or recovery (can't remember precisely which).
---------- Post added at 10:39 AM ---------- Previous post was at 10:33 AM ----------
Maybe I've got the details wrong. But that was my understanding based on post by others. And as just mentioned, I've seen at least a report or 2 of bricking after flashing a GSM mod on a CDMA phone.
I just saw it mentioned on another thread that CM11 supports CDMA variants, so I'm curious about that as well. But if the hardware is the same, why are the recoveries (at least TWRP) different? I'm asking as much as making a point here, as again I'm curious.
I'd still maintain folks should not flash ROMs not meant for their type (GSM versus CDMA); or at a minimum to tread very carefully if you decide you want to. It should go without saying, if a ROM is not stated to support your carrier version, you should proceed with caution and at least do some research before proceeding.
And not sure what the intent of the OP is; but if they are looking to make a purchase, I also do not recommend any of the CDMA variants unless your carrier has a CDMA network (which is very unlikely unless you are on Verizon or Sprint in the US).
Click to expand...
Click to collapse
I would bet 99% they bricked it from installing the wrong recovery and not the wrong ROM. Or it was for a totally different phone, not just the GSM version of the ROM for their phone.
Correct me if I'm wrong (still new to this), but I didn't think the ROMs changed enough (like partitions and such) to actually brick the phone if you say, select the wrong one in aroma on install. If you were to flash a different recovery, or hboot, or....pretty much anything other than a ROM, I could see there being issues. Or flashing anything (ROM included) for a totally different phone (like the m7), as opposed to the other cell provider variant of the same phone.
But, like you said, I wouldn't get a CDMA phone unless I absolutely had to....and in my case it was $100 for a brand new CDMA m8 as opposed to the $600 for the int'l version I ideally wanted. Opportunity cost of $500 and CDMA phone was worth it to me. At least now I can help people traveling to Europe with their Verizon phone and whether or not certain things will work....

AmbitiousDonut said:
I would bet 99% they bricked it from installing the wrong recovery and not the wrong ROM. Or it was for a totally different phone, not just the GSM version of the ROM for their phone.
Correct me if I'm wrong (still new to this), but I didn't think the ROMs changed enough (like partitions and such) to actually brick the phone if you say, select the wrong one in aroma on install. If you were to flash a different recovery, or hboot, or....pretty much anything other than a ROM, I could see there being issues. Or flashing anything (ROM included) for a totally different phone (like the m7), as opposed to the other cell provider variant of the same phone.
But, like you said, I wouldn't get a CDMA phone unless I absolutely had to....and in my case it was $100 for a brand new CDMA m8 as opposed to the $600 for the int'l version I ideally wanted. Opportunity cost of $500 and CDMA phone was worth it to me. At least now I can help people traveling to Europe with their Verizon phone and whether or not certain things will work....
Click to expand...
Click to collapse
This isn't necessarily true. While most of the variants share the same partition layout, the Verizon variant has an extra partition, shifting out the number of the block devices by one when compared to the other variants. If the ROM zip flashed uses the block device number for flashing, this can indeed "soft brick" a device.
NOTE: This is NOT a hardware difference. It's the same nand/emmc, just partitioned slightly differently for Verizon.

Captain_Throwback said:
This isn't necessarily true. While most of the variants share the same partition layout, the Verizon variant has an extra partition, shifting out the number of the block devices by one when compared to the other variants. If the ROM zip flashed uses the block device number for flashing, this can indeed "soft brick" a device.
NOTE: This is NOT a hardware difference. It's the same nand/emmc, just partitioned slightly differently for Verizon.
Click to expand...
Click to collapse
I don't have a dog in this hunt, since I've got a GSM M8, so this is just out of curiosity.
Couldn't you S-off, switch your CID/MID to Sprint, and run a Sprint RUU to "fix" that, then reload the Verizon radio to recover network function? That assumes that both Sprint and Verizon phones use the same radio hardware, of course.

jshamlet said:
I don't have a dog in this hunt, since I've got a GSM M8, so this is just out of curiosity.
Couldn't you S-off, switch your CID/MID to Sprint, and run a Sprint RUU to "fix" that, then reload the Verizon radio to recover network function? That assumes that both Sprint and Verizon phones use the same radio hardware, of course.
Click to expand...
Click to collapse
I refuse to speculate about the effects of doing something like this. As this goes beyond the purview of this thread, I will digress.

Captain_Throwback said:
This isn't necessarily true. While most of the variants share the same partition layout, the Verizon variant has an extra partition, shifting out the number of the block devices by one when compared to the other variants. If the ROM zip flashed uses the block device number for flashing, this can indeed "soft brick" a device.
NOTE: This is NOT a hardware difference. It's the same nand/emmc, just partitioned slightly differently for Verizon.
Click to expand...
Click to collapse
Interesting, didn't know that. Thanks.
I guess since I learned how to use adb/fastboot for things instead of relying on an app like Flashify I've gotten a bit more fearless about potentially soft-bricking it. I figure worst case I'll learn something new and be using my old N4 until I get it fixed.

AmbitiousDonut said:
Interesting, didn't know that. Thanks.
I guess since I learned how to use adb/fastboot for things instead of relying on an app like Flashify I've gotten a bit more fearless about potentially soft-bricking it. I figure worst case I'll learn something new and be using my old N4 until I get it fixed.
Click to expand...
Click to collapse
Yeah partition is out by one which is why some Verizon users had a bootloop when flashing TWRP.
TWRP developers place the command as
Code:
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43
instead of
Code:
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p44
As the recovery on the GSM is in block43 but block 43 on the Verizon was the boot partition. :laugh:

BerndM14 said:
Yeah partition is out by one which is why some Verizon users had a bootloop when flashing TWRP.
TWRP developers place the command as
Code:
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43
instead of
Code:
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p44
As the recovery on the GSM is in block43 but block 43 on the Verizon was the boot partition. :laugh:
Click to expand...
Click to collapse
That's been updated for a while now, though . . .

Captain_Throwback said:
That's been updated for a while now, though . . .
Click to expand...
Click to collapse
Yeah I know, just adding to your post about the 1 extra partition on Verizon and how it caused some "fun" early on by having them "flash" recovery to boot partition because the partition block was out by 1.

AmbitiousDonut said:
I would bet 99% they bricked it from installing the wrong recovery and not the wrong ROM. Or it was for a totally different phone, not just the GSM version of the ROM for their phone.
Click to expand...
Click to collapse
That could be. I'm just throwing out what I can remember reading.
I'll still maintain that one should take care flashing anything that doesn't specifically support the CDMA variant, or verified to work by others. Even if a brick is not possible when flashing a GSM ROM, other issues can still occur. I'm seeing a couple other posts right now where the Sprint/Verizon GPS files are apparently different, causing GPS to be broken after flashing some ROMs.
Like Post #12 put well, I don't have a dog in this myself either. Just mentioning what I've see reported as FYI to others.
---------- Post added at 12:49 PM ---------- Previous post was at 12:41 PM ----------
Captain_Throwback said:
this goes beyond the purview of this thread
Click to expand...
Click to collapse
In think much of this discussion has gone far beyond what the OP intended. But interesting, nonetheless!
---------- Post added at 12:52 PM ---------- Previous post was at 12:49 PM ----------
Captain_Throwback said:
The hardware is the same on all M8 variants (besides Dual SIM). The radios differ, and there is some carrier customization in the ramdisk and build.prop. But that's it.
Click to expand...
Click to collapse
I stand corrected. I've seen more than a few posts about not flashing ROMs and other things between the versions (GSM vs. CDMA), and there being a hardware difference. So I was just relaying what I read.
Thanks for setting me straight.

redpoint73 said:
That could be. I'm just throwing out what I can remember reading.
I'll still maintain that one should take care flashing anything that doesn't specifically support the CDMA variant, or verified to work by others. Even if a brick is not possible when flashing a GSM ROM, other issues can still occur. I'm seeing a couple other posts right now where the Sprint/Verizon GPS files are apparently different, causing GPS to be broken after flashing some ROMs.
Like Post #12 put well, I don't have a dog in this myself either. Just mentioning what I've see reported as FYI to others.
---------- Post added at 12:49 PM ---------- Previous post was at 12:41 PM ----------
In think much of this discussion has gone far beyond what the OP intended. But interesting, nonetheless!
---------- Post added at 12:52 PM ---------- Previous post was at 12:49 PM ----------
I stand corrected. I've seen more than a few posts about not flashing ROMs and other things between the versions (GSM vs. CDMA), and there being a hardware difference. So I was just relaying what I read.
Thanks for setting me straight.
Click to expand...
Click to collapse
I have tried weaksauce and it won't open. I'm on 5.0. how is this puppy rooted? I tried kingroot but I keep getting root auth error

jerryspring said:
I have tried weaksauce and it won't open. I'm on 5.0. how is this puppy rooted? I tried kingroot but I keep getting root auth error
Click to expand...
Click to collapse
Which "puppy" would that be? This thread refers to two different variants (m8_ul versus m8_wl) which also have different root methods.
For most M8 versions (m8_ul) root method is to unlock bootloader, flash custom recovery and flash SuperSU.

[Q] Flashing Verizon Rom on non-Verizon phone

Hello!
Quick question: I'm in Britain and have an unlocked s-off M8. What would happen if I flashed a Verizon/Sprint One (for example) M8 rom on my phone? Would it simply not make calls? Would it brick the phone? I'm intrigued to know.
Cheers.
Em

Might be risky. I don't know if anyone here has tried.
The hardware may even be different (for Sprint and Verizon CDMA variants vs. GSM versions). Some claim yes, others say no. And I haven't seen definitive evidence either way, so that part is not clear either.
I think a couple folks here bricked mixing the variants when flashing TWRP recovery (GSM recovery on a CDMA variant)? But from what I understand that is something that was fixed in TWRP.
I wouldn't risk it, unless you have a compelling reason to do so. May I ask why? I figured there was more development on the GSM version, anyway. Or just asking academically?

redpoint73 said:
Might be risky. I don't know if anyone here has tried.
The hardware may even be different (for Sprint and Verizon CDMA variants vs. GSM versions). Some claim yes, others say no. And I haven't seen definitive evidence either way, so that part is not clear either.
I think a couple folks here bricked mixing the variants when flashing TWRP recovery (GSM recovery on a CDMA variant)? But from what I understand that is something that was fixed in TWRP.
I wouldn't risk it, unless you have a compelling reason to do so. May I ask why? I figured there was more development on the GSM version, anyway. Or just asking academically?
Click to expand...
Click to collapse
Thanks for the fullness of your reply. Much appreciated.
As for your question: I've been wondering since got my M8. I've mainly had a Nexus 5 for the past few months and there's never been alternate versions. I noticed that there's a CM12 ROM flying around, and I'm a flash addict, so the hypothetical became slightly more actual.
Although if there's a chance of a brick, then it can stay in the land of hypotheticals

New thread, new question. Wifi or service, not both.

Ok, same phone, AT&T HTC M9, now S-Off, TWRP 3.0.2.0, 3.38.502.41 firmware. Tried ARHD 20.0, had no service, flashed boot.img, got service but lost wifi. Tried Viperone M9 4.3, same issue. ICE, same issue. If I have Wifi, I have no service. If I flash boot.img, I get service, but lose Wifi. I'm pulling my hair out right now, as I've searched high and low and I've been looking at my PC and M9 for about 14 hours now. Anyone have any insight?

Does the rom match your firmware version?
Edit: just read your other thread and replied.
The firmware versions are off so I wouldn't trust it. Htc's are crap when it comes to recovery so be careful.
I have stayed on 6.0 with root and s-off, without xposed for a very good reason!.
If I were you, as I said in your other thread, would be going back to stock at this point and hoping for the best that the damage isn't permanent.
Its too risky to mess with htc devices. They don't have an app like odin or one even half as good.
You have a beast of a phone as is. You don't need to beef it up any more than it is.
Beamed in by telepathy.

shivadow said:
Does the rom match your firmware version?
Edit: just read your other thread and replied.
The firmware versions are off so I wouldn't trust it. Htc's are crap when it comes to recovery so be careful.
I have stayed on 6.0 with root and s-off, without xposed for a very good reason!.
If I were you, as I said in your other thread, would be going back to stock at this point and hoping for the best that the damage isn't permanent.
Its too risky to mess with htc devices. They don't have an app like odin or one even half as good.
You have a beast of a phone as is. You don't need to beef it up any more than it is.
Beamed in by telepathy.
Click to expand...
Click to collapse
It's a bit of a long story as to why I decided to root. It's not damaged by any means, if I flash the ROM posted here (https://forum.xda-developers.com/at...ficial-att-3-38-502-12-rom-7-01-2016-t3409354), Wifi and data both work flawlessly, despite it having a different firmware number. The whole ROM is actually decent, but lacks all the customization I want, and for some reason, headphones only work on one side. I hoped this fix would be simple, as so many people seem to run custom ROMs and I'm just over here yelling at my inanimate object

shivadow said:
Does the rom match your firmware version?
Edit: just read your other thread and replied.
The firmware versions are off so I wouldn't trust it.
I have stayed on 6.0 with root and s-off, without xposed for a very good reason!.
If I were you, as I said in your other thread, would be going back to stock at this point and hoping for the best that the damage isn't permanent.
Its too risky to mess with htc devices.
You have a beast of a phone as is. You don't need to beef it up any more than it is.
Beamed in by telepathy.
Click to expand...
Click to collapse
None of the things manlavi did, so far, was risky. The phone didn't take any damage. All he did was flashing a rom that is incompatible with his firmware like many did before him. The only difference is that HTC seems to have changed some more parts of the firmware with the latest AT&T update so that not only the boot image is incompatible. But that only makes it harder to make the rom compatible. The phone doesn't get damaged in any kind.
If he had flashed a firmware that is incompatible with his phone that would be a whole different story. However, before he opened this thread his phone wasn't S-OFF so he wouldn't have been able to do so even if he wanted.
manlavi95 said:
It's a bit of a long story as to why I decided to root. It's not damaged by any means, if I flash the ROM posted here (https://forum.xda-developers.com/at...ficial-att-3-38-502-12-rom-7-01-2016-t3409354), Wifi and data both work flawlessly, despite it having a different firmware number. The whole ROM is actually decent, but lacks all the customization I want, and for some reason, headphones only work on one side. I hoped this fix would be simple, as so many people seem to run custom ROMs and I'm just over here yelling at my inanimate object
Click to expand...
Click to collapse
The headphones might be broken. Did you check whether they work correctly with a different device?
As already said in the other thread you could convert your phone to another GSM variant of the M9. You would need to change your CID and your MID and then you could flash a RUU with a different SKU. However, you need to be aware that you'll lose every AT&T specific tweaks and functions by doing so. Instructions for converting for example to the US dev edition of the M9 are linked in the readme thread.
Alternatively you could try xposed and the sense tool box on a rooted stock rom. This way you could enable many customisations without having to change your firmware. If you choose this option you should get back to the correct stock rom for your firmware by flashing the RUU I linked in your other thread.

Flippy498 said:
None of the things manlavi did, so far, was risky. The phone didn't take any damage. All he did was flashing a rom that is incompatible with his firmware like many did before him. The only difference is that HTC seems to have changed some more parts of the firmware with the latest AT&T update so that not only the boot image is incompatible. But that only makes it harder to make the rom compatible. The phone doesn't get damaged in any kind.
If he had flashed a firmware that is incompatible with his phone that would be a whole different story. However, before he opened this thread his phone wasn't S-OFF so he wouldn't have been able to do so even if he wanted.
The headphones might be broken. Did you check whether they work correctly with a different device?
As already said in the other thread you could convert your phone to another GSM variant of the M9. You would need to change your CID and your MID and then you could flash a RUU with a different SKU. However, you need to be aware that you'll lose every AT&T specific tweaks and functions by doing so. Instructions for converting for example to the US dev edition of the M9 are linked in the readme thread.
Alternatively you could try xposed and the sense tool box on a rooted stock rom. This way you could enable many customisations without having to change your firmware. If you choose this option you should get back to the correct stock rom for your firmware by flashing the RUU I linked in your other thread.
Click to expand...
Click to collapse
I tested the headphones on another rom and my computer, they had no issues with that. I'm working on converting it to the dev edition. I've changed my CID, but I'm a little afraid that this write-up is a bit out of date, so I'm currently searching for the right RUU.

manlavi95 said:
I tested the headphones on another rom and my computer, they had no issues with that. I'm working on converting it to the dev edition. I've changed my CID, but I'm a little afraid that this write-up is a bit out of date, so I'm currently searching for the right RUU.
Click to expand...
Click to collapse
It's linked in my thread, as well. Directly behind the link to the newer version of the conversion guide. However, it doesn't matter whether you use that old 3.x RUU or a newer one. You just need to install some OTAs while being on stock rom, afterwards, if you choose to use the old one. Be aware that most of the custom roms aren't compatible, yet, with the new 4.x firmware. So only update until your device suggests you to install the 4.x OTA.

Flippy498 said:
It's linked in my thread, as well. Directly behind the link to the newer version of the conversion guide. However, it doesn't matter whether you use that old 3.x RUU or a newer one. You just need to install some OTAs while being on stock rom, afterwards, if you choose to use the old one. Be aware that most of the custom roms aren't compatible, yet, with the new 4.x firmware. So only update until your device suggests you to install the 4.x OTA.
Click to expand...
Click to collapse
Currently downloading the 3.35.617.12 RUU and the HTC Fastboot as I don't have an SD smaller than 32GB. I don't know how I've read that entire Q&A a few times over and didn't see that, so thanks as always

manlavi95 said:
Currently downloading the 3.35.617.12 RUU and the HTC Fastboot as I don't have an SD smaller than 32GB. I don't know how I've read that entire Q&A a few times over and didn't see that, so thanks as always
Click to expand...
Click to collapse
You don't need an SD card with less than 32gb if you're on firmware 3.x (and that is what you currently are). With firmware 3.x and above HTC enabled the usage of exfat formatted SD cards for RUU flashing.

Used the SD method, my phone is now running developer edition. Speaking technically once again, I should be able to use ROMs and have them work now, I imagine. Wifi and cellular both work after flashing dev edition.j

manlavi95 said:
Used the SD method, my phone is now running developer edition. Speaking technically once again, I should be able to use ROMs and have them work now, I imagine. Wifi and cellular both work after flashing dev edition.j
Click to expand...
Click to collapse
Correct.

IT WORKS. IT WOOOOOORKS. Thank you so much.