Develop Bugs

im new here!

guys im fixing to buy a white galaxy s2, what should i be concern about? is the root method easy, kernels, roms, is there anything hiding from samsung? like im coming from the amaze, htc havent released the wifi drivers for it and have no s-off, just wondering if you guys has had any problems with this phone, and how is the development here is, is it dead or alive?

Well look around lol. Rooting is easy as pie, everything else is based on your preference. Many solid gingerbread roms and kernels here
Were on the brink of some great releases...thanks to a recent ics leak there are all kinds of rooms being cooked up. I'd say its a great time to buy one within a few weeks we should have some great ics roms.
Sent from my SAMSUNG-SGH-T989 using XDA

gypsy214 said:
Guys, I'm fixing to buy a white Galaxy S2; what should I be concerned about? Is the root method easy, kernels, roms? Is there anything hiding from samsung? I'm coming from the Amaze, and HTC hasn't released the wifi drivers or (an engineering?) s-off; furthermore, I am wondering if you guys have had any problems with this phone? How is the development here, is it dead or alive?
Click to expand...
Click to collapse
You don't need to worry about s-off like HTC phones. Just put the phone in download mode and flash clockworkmod, then install whatever ROM you want. It is much to root easier than any HTC phone I have rooted. Samsung also has released all source code up to the latest update. No one has had problems besides the same that exist with all phones. As for development with the skyrocket leak of ICS it is heating up faster than a junkies spoon (see thread below)
http://forum.xda-developers.com/showthread.php?t=1577041

thank you guys i just got the phone, love it so far, i think more than the amaze..
im new to samsung though, i know its totally different on rooting and such,
ill start downloading drivers and start rooting!

As someone previously said, development is on the cusp of being current with every other major device. The ICS leak for the AT&T SkyRocket is very crucial for us because the phones are nearly identical.
With that said, the GB roms are all solid but not AOSP with the exception of a couple Kanged CM7's. Not sure if they're working entirely however. There is an AOSP ICS which is what we all crave, but it's only partially working. The TouchWiz (Samsung stock/themed) ICS leak is almost perfect. We just need a native kernel to fix auto-rotation and the little bugs.
The phone's specs are among the best in the world right now lol. YOU WILL LOVE THIS PHONE, I have no doubt about it.
Also, feel free to PM me about any other questions you may have that aren't being answered.

gypsy214 said:
thank you guys i just got the phone, love it so far, i think more than the amaze..
im new to samsung though, i know its totally different on rooting and such,
ill start downloading drivers and start rooting!
Click to expand...
Click to collapse
to start..check youtube... how to root tmobile galaxy s2[sgh] T989 galaxy s2 root...enjoy your new phone..

or just look at the stickies in the general section
Sent from my SGH-T989 using XDA

Flashing Kernels
is there a guide somewhere to flashing kernels for SGS2?

gypsy214 said:
guys im fixing to buy a white galaxy s2, what should i be concern about? is the root method easy, kernels, roms, is there anything hiding from samsung? like im coming from the amaze, htc havent released the wifi drivers for it and have no s-off, just wondering if you guys has had any problems with this phone, and how is the development here is, is it dead or alive?
Click to expand...
Click to collapse
Root and ROMs are great. However we don't have any good ICS kernels because we're still waiting on samsung

ok guys been playing around with some roms and stuff, like some of you said rooting this device was a peace of cake,
loved the megamix ICS rom, the only problem was roration and the calling echo witch you already know.
some of the fixes that i seen for the echo issue dont seen to help mine though,
now i have a question, why do we need a blaze modem?
this phone suppost to be one of the 42mgp of tmobile, if i recall the amaze, the galaxy s2, and now the blaze.

gypsy214 said:
ok guys been playing around with some roms and stuff, like some of you said rooting this device was a peace of cake,
loved the megamix ICS rom, the only problem was roration and the calling echo witch you already know.
some of the fixes that i seen for the echo issue dont seen to help mine though,
now i have a question, why do we need a blaze modem?
this phone suppost to be one of the 42mgp of tmobile, if i recall the amaze, the galaxy s2, and now the blaze.
Click to expand...
Click to collapse
not sure if this has been said, but only flash t989 and i727 skyrocket stuff.
the blaze's modem is just another modem.... rado for HTC that may or may not strengthen your phone's signal. It all depends on your phone and location. I got spotty service here in socal with but when I do have reception.. it is faster. Just too spotty.

Are you a real gypsy?
Sent from my SGH-T989 using Tapatalk

tdizzle404 said:
Are you a real gypsy?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
yes i am

Cool welcome
Sent from my SGH-T989 using Tapatalk

HTC One V Dead

So I bought my gf a one v and she loves it. One month after using it (stock, unrooted) it just went dead. Doesn't charge and doesn't get into bootloader (but not the QHSUSB_DLOAD and Blank Screen issue). Guy at repair told me that this was an issue with the ICS kernel causing a hard brick. Now, I naturally sent phone for repair since it is a warranty case. So far so good, lets just hope they get it done fast.
My question is though: should I root device and flash another ROM with presumably no such issues so I can avoid a future brick? I mean, I'm using a rooted desire and have no issues for over 2 years, now just didn't want to mess with the new phone of my gf and thought 'hey, lets keep it stock'... But the thought that it would die again after having it repaired is really discouraging. My gf is kind of frustraded and I don't want this to happen again. But are there such issues with custom ROMs for the One V? Like I said, I'm using the good old desire and don't know much about the one v, so I would really apreciate if you can tell me - because if such an issue is possible on custom roms, there is no point to bother flashing and voiding warranty.
Thanks for your time guys!

Well at the moment we have only modified stock ROM for this device and one custom kernel (in beta state) which is still an ICS kernel.
However you''ll never know whether this happens again or not. But one thing you can know for sure is that if you unlock the bootloader and install a custom kernel and ROM and it happens again then your are screwed because you lost your warranty.
Maybe you should wait a bit for some stable custom rom. Because an unstable and buggy ROM would make your gf even more frustrated and andgry

Oh well, thanks for the insight my friend..So, If I got this right, if I root and flash one of the current roms and it bricks again, I will still not be able to acces bootloader? And is this really a kernel issue with ICS? I'm willing to even flash a GB rom, if it is possible, in order to avoid this...gf won't mind for sure lol, if this delivers a stable phone in the future
P.S. Does this even happen with other ICS roms/on other stock ICS devices? Or did HTC just screw up on this one? I can understand a phone bricking when changing hboots or other tinkering, but just dieing like that is pretty damn stupid. And from what I read it happens to quite a few other one v users...Hope noone of you guys gets to experience this crap

falconyx said:
Oh well, thanks for the insight my friend..So, If I got this right, if I root and flash one of the current roms and it bricks again, I will still not be able to acces bootloader? And is this really a kernel issue with ICS? I'm willing to even flash a GB rom, if it is possible, in order to avoid this...gf won't mind for sure lol, if this delivers a stable phone in the future
P.S. Does this even happen with other ICS roms/on other stock ICS devices? Or did HTC just screw up on this one? I can understand a phone bricking when changing hboots or other tinkering, but just dieing like that is pretty damn stupid. And from what I read it happens to quite a few other one v users...Hope noone of you guys gets to experience this crap
Click to expand...
Click to collapse
1. In no other galaxy, no other planet... IT IS NOT A KERNEL FAULT! it may at well be a piece of poorly made phone. you should get another one from the warranty. I can 100% say that you will not have any problems. The kernel doesn't suddenly causes hard brick to your phone. If it does, do you know how many phones running ICS are there? Or One V's...
I have flashed alpha/beta/final kernels/roms for millions of times, no problems whatsoever.
in no way this is a kernel/soft problem. more likely the flash drive from your gf's phone, died!

1ceb0x said:
1. In no other galaxy, no other planet... IT IS NOT A KERNEL FAULT! it may at well be a piece of poorly made phone. you should get another one from the warranty. I can 100% say that you will not have any problems. The kernel doesn't suddenly causes hard brick to your phone. If it does, do you know how many phones running ICS are there? Or One V's...
I have flashed alpha/beta/final kernels/roms for millions of times, no problems whatsoever.
in no way this is a kernel/soft problem. more likely the flash drive from your gf's phone, died!
Click to expand...
Click to collapse
Thx dude, I was sort of wondering how this could really be a kernel problem, since the guy over at the repair told me so - 'Its a kernel issue with ICS'... well, I hope he was really wrong and the device we receive (hopefully soon) will be proper

falconyx said:
Thx dude, I was sort of wondering how this could really be a kernel problem, since the guy over at the repair told me so - 'Its a kernel issue with ICS'... well, I hope he was really wrong and the device we receive (hopefully soon) will be proper
Click to expand...
Click to collapse
That guy should really make his homework. In no way a kernel can brick the phone. If this was true, the phone will not boot and work for weeks in the first place. Its not like the kernel has a "time-bomb" inside and it triggers when it is set.
As I said, it is a phone problem, something hardware has failed.
Hopefully it will be fixed for you gf and she will not have any problems in the future.

It happens in India too
My htc one v got bricked suddenly while using it. Forums at internet says it happens if battery charge goes below certain limit. Mine it went down to 24%

It happened to me when my battery level was 14%. now I have to pay 200$ for repairs. (because I live in Iran.)

HTC ONE V dead
falconyx said:
Oh well, thanks for the insight my friend..So, If I got this right, if I root and flash one of the current roms and it bricks again, I will still not be able to acces bootloader? And is this really a kernel issue with ICS? I'm willing to even flash a GB rom, if it is possible, in order to avoid this...gf won't mind for sure lol, if this delivers a stable phone in the future
P.S. Does this even happen with other ICS roms/on other stock ICS devices? Or did HTC just screw up on this one? I can understand a phone bricking when changing hboots or other tinkering, but just dieing like that is pretty damn stupid. And from what I read it happens to quite a few other one v users...Hope noone of you guys gets to experience this crap
Click to expand...
Click to collapse
Hi My HTC one V just died , I didn't know how it was happened . 10 minutes before I made I call and just after sometime It stopped working .
Even it is not charging at all, mobile is out of warranty. don't really know what to do ..
Any suggestion would be appreciated .
Regards
Manoj

Is the One X still a decent phone?

I'm upgrading from an old Gingerbread phone (ZTE Skate), on a budget of about 200€. The Nexus 4 unfortunately isn't an option, as it isn't available here and re-sellers are asking way too much for it.
Is the One X still a good option at that price?

omegavesko said:
I'm upgrading from an old Gingerbread phone (ZTE Skate), on a budget of about 200€. The Nexus 4 unfortunately isn't an option, as it isn't available here and re-sellers are asking way too much for it.
Is the One X still a good option at that price?
Click to expand...
Click to collapse
I'd say that was a fair price, I paid £185 (about 220 euro) for my second hox 6 months ago and it is still an excellent phone

Thanks! I'm really just worried about UI performance at this point. I'm aware of the issues with some games due to the Tegra chipset, but I'm not a big mobile gamer (maybe just Temple Run, some emulators etc.) so no problem there. On a custom ROM (or even stock), do you ever get lag or stutters in the UI? Things like scrolling through apps, pulling down the notification bar, and such.

you're always gonna get lag to a certain degree on any phone, I also use a nexus 7, an htc one and, dare I say it, an iphone 5s. I get a little lag on all of them sometimes and my hox is no better or worse than the others. as for roms, again, they all have the ups and downs. the best way is to try them or read the threads before you try and decide for yourself.

Sounds good to me. Thanks for the help. I'm fine with UI stutters if they're just an occasional thing like pretty much all other phones.

With sense5 the hox has became really competitive. The camera isn't as good as the sensation but for the price you get one of the best display out there. For 200€ definitively worth the money
Sent from my HTC One X using xda app-developers app

I am satisfied with my hox performance is very good.
Sent from my HTC One X using xda premium

i think it's still a wonderful phone... and with custom rom it's better

Thanks for the replies! I guess I'm on the right track, then.
Oh, also, what's the situation with CID, HBOOT, locked bootloaders etc.? I haven't used an HTC phone before, so could some combination of those prevent me from flashing a ROM for some reason? I know you can only run a RUU if the CID matches, is that all?

omegavesko said:
Thanks for the replies! I guess I'm on the right track, then.
Oh, also, what's the situation with CID, HBOOT, locked bootloaders etc.? I haven't used an HTC phone before, so could some combination of those prevent me from flashing a ROM for some reason? I know you can only run a RUU if the CID matches, is that all?
Click to expand...
Click to collapse
cid and main version also. and you can only run an ruu that matches or is higher than your main version. but you can flash a nandroid backup that is older, then ota up to the latest. if you are gonna try anything, first make sure you are on the highest possible version for your cid then make a nandroid backup in recovery and copy it to your pc when it's done.

Thanks! That's pretty much what I do with my devices anyway. There's no way I would do something major to my phone without making a nandroid first.
I'm just worried about getting a phone that's not hackable, incompatible with ROMs etc. for some reason. Is that something that can happen?

omegavesko said:
Thanks! That's pretty much what I do with my devices anyway. There's no way I would do something major to my phone without making a nandroid first.
I'm just worried about getting a phone that's not hackable, incompatible with ROMs etc. for some reason. Is that something that can happen?
Click to expand...
Click to collapse
well, it's not so difficult to install custom roms on HOX and there are many roms (in each thread you will find the instructions for flashing)

omegavesko said:
Thanks! That's pretty much what I do with my devices anyway. There's no way I would do something major to my phone without making a nandroid first.
I'm just worried about getting a phone that's not hackable, incompatible with ROMs etc. for some reason. Is that something that can happen?
Click to expand...
Click to collapse
the hox, because it is s-on, is pretty near impossible to brick provided you are using stuff from the right forum, IE: this one. and there is an abundance of help available if you get stuck.

Oh, I get that. I'm just asking if there's something about a device that can make it completely incompatible with ROMs, due to an incompabitle HBOOT or whatever. Mainly because I see a lot of ROMs are only compatible with certain HBOOT values.

omegavesko said:
Oh, I get that. I'm just asking if there's something about a device that can make it completely incompatible with ROMs, due to an incompabitle HBOOT or whatever. Mainly because I see a lot of ROMs are only compatible with certain HBOOT values.
Click to expand...
Click to collapse
at the minute hboot 1.72 is causing some people problems, but only because they don't read and search properly. it causes a problem with touch but the simple solution is to flash a compatible recovery like the newest or repacked twrp or philz touch recovery, and cm10.2 needs a line edited or deleted to make it compatible with the hboot. so if you get one take note of that. apart from that everything else runs as you would expect. simple rule is read, read again and read a third time just in case you missed something. have fun

Great, thanks for all the help. Looks like I'll be joining you guys as soon as I manage to sell my current phone.

omegavesko said:
Great, thanks for all the help. Looks like I'll be joining you guys as soon as I manage to sell my current phone.
Click to expand...
Click to collapse
:highfive:

[Q] Non-carrier firmware vs carrier firmware

Hello all,
I'm just wondering, do you guys notice or know of any real difference b/t the unlocked/non-carrier firmware that's out there and the carrier-specific firmware from T-Mobile for the M8? Is one considered better than the other?
Please share your thoughts with us!
Thank You,
RockStar2005

RockStar2005 said:
Hello all,
I'm just wondering, do you guys notice or know of any real difference b/t the unlocked/non-carrier firmware that's out there and the carrier-specific firmware from T-Mobile for the M8? Is one considered better than the other?
Please share your thoughts with us!
Thank You,
RockStar2005
Click to expand...
Click to collapse
I know my experience with the M7 (yes i know its an M8 forum but still somewhat relevant) is Yes, the carrier firmware was better.
I had a Stock TMO branded M7. I did the full conversion to make it a GPe unit. It was nice but i had some signal issues. It was better with the TMO radios but ultimately i put it back to stock TMO and for me i got the best results like that.

IAmSixNine said:
I know my experience with the M7 (yes i know its an M8 forum but still somewhat relevant) is Yes, the carrier firmware was better.
I had a Stock TMO branded M7. I did the full conversion to make it a GPe unit. It was nice but i had some signal issues. It was better with the TMO radios but ultimately i put it back to stock TMO and for me i got the best results like that.
Click to expand...
Click to collapse
No I think the M7 experience is definitely still relevant!
Ok, you're the first one so far here to say that. So the radios change based on the firmware? Why is that? I mean, why would the radios be affected by the firmware? Seems to me it'd be better to leave the radios alone and let them remain how they came.
My previous OTA was from T-Mobile, but in order to get updated ViperOne M8, I had to get the firmware for 2.22 and T-Mo wasn't deploying it. They apparently just approved it on the 18th, but as u prob read above, I'm not even sure if they've deployed it, and what it contains. I seem to have as much signal quality as before. I just wish they'd have VoLTE deployed for the M8s. That would be great.
RockStar2005

I have been with T-Mobile less then 2 years. Prior to that i was with sprint over 10 years. I got most of my "radio" experience flashing different radios for the Samsung GS2.
That device was super finikey when it came to radios. I also found at the time that 3 different network vendors set up most of the CDMA network in the USA for Sprint. So for me having a specific radio work well meant that same one might not work so well up north. Samsung was also known to not have very good hardware / antennas (when i say radios i am referring to the firmware for the specific device.) So while my devices hardware stayed the same Samsung was making software tweaks during each revision of software.
But to keep it simple, Yes, different versions of radios can work differently in each device. Thats even with stock radios. Then if you add stuff like a GPe radio to a stock unit, or what i had with my M7 using a GPe ROM with a TMO radio. It always pains me to see people who post about using carrier A phone unlocked with carrier B network. Those people will never get the most out of their hardware network wise because carrier B has worked with the manufacturer to make sure their device is created to be specific to their network. Sure an unlocked will work but not at 100% efficiency. It could be a hardware limitation, could be some software that is baked into the ROM to make it work better, or even as simple as TMO baking in WiFi calling with their network.
I mean look what happened to the Note 3 for TMO. Originally it shipped with LTE not even enabled. The hardware was there then BAM, with an OTA LTE was enabled. Flash forward to the last few months, 2 separate updates for VoLTE. Those are radios updates that are specific to the hardware in the Note 3.
Hopefully someone else can chime in as well. Id hate to think im the only one.

Six,
No you explained that rather well! My cousin has the Note 3 so I know what u said about the last part (on VoLTE) is def true. I wish HTC would hurry the F up and give us M8 ppl VoLTE. Would be nice. And make it available everywhere, not just major cities (it's avail in Chicago, but I live 25-30 min away).
I have a buddy who works for U.S. Cellular corporate, and he said the same thing. Unlocked phones, esp ones sold by one carrier but used on another's network, don't work AS well as when the phone is made for your carrier's network. International phones at least I believe work fine if released OFFICIALLY in the U.S. (i.e., Sony's Xperia Z2, which is ONLY avail that way in the U.S.), because they've been tested on ALL carrier networks/bands, but that's diff than using say a Sprint phone on T-Mobile's network, I believe. (Or using a phone that wasn't approved for all the major U.S. carriers.)
So far you're the only who seems pro-carrier firmware/OTAs, but that's ok. That's why I started this thread, so I can get all sides of the story. But if you read the previous posts, the other posters make a compelling argument that's pro-noncarrier. It sounds like in my situation I'm fine, b/c I'm pretty sure the int't M8 was tested on T-Mo's bands already. The firmware would just go along with that same data, so I don't think I'm having any loss of quality. Now if I carrier-unlocked my phone and tried it on Sprint or Verizon, or even AT&T......... then I would expect a loss of quality at some level.
Thanks,
RockStar2005

Agreed. I see merits in both custom roms, stock roms, GPe Roms and Cyanogen.
Back in the GS2 days i was a big fan of using some of those custom ROMS guys would cook up. It fixed a lot of issues with Android.
But for ME, since 4.2.2 and up, i have been happy with stock ROMs.
In fact i almost always ran custom roms on my older devices and only recently started to leave them stock.
The last thing was when TMO gave me 3 GB free tethering, that was the last thing i might have rooted for.
My note 3 is stock, my M8 is still stock. and my back up M7 is stock (after putting GPe on it for a few weeks and testing stuff out).
I for one use my M8 as my daily phone and my Note 3 as my back up / game device.
For example, today at lunch i had local news streaming on my M8 while my Note 3 was tethered to my M8. On my Note 3 i was playing a few games while i waited for my food then answered a few emails and chatted with a friend on Hangouts.
With TMOs recent 4.4.3 update my M8 seems to run better then before and i feel im getting better battery life out of it.
Cant wait for my Note 3 to get 4.4.3 or 4.4.4. Also really looking forward to Android L on both of the units.
The way i look at it is what are YOUR pros and cons. LOL.

IAmSixNine said:
Agreed. I see merits in both custom roms, stock roms, GPe Roms and Cyanogen.
Back in the GS2 days i was a big fan of using some of those custom ROMS guys would cook up. It fixed a lot of issues with Android.
But for ME, since 4.2.2 and up, i have been happy with stock ROMs.
In fact i almost always ran custom roms on my older devices and only recently started to leave them stock.
The last thing was when TMO gave me 3 GB free tethering, that was the last thing i might have rooted for.
My note 3 is stock, my M8 is still stock. and my back up M7 is stock (after putting GPe on it for a few weeks and testing stuff out).
I for one use my M8 as my daily phone and my Note 3 as my back up / game device.
For example, today at lunch i had local news streaming on my M8 while my Note 3 was tethered to my M8. On my Note 3 i was playing a few games while i waited for my food then answered a few emails and chatted with a friend on Hangouts.
With TMOs recent 4.4.3 update my M8 seems to run better then before and i feel im getting better battery life out of it.
Cant wait for my Note 3 to get 4.4.3 or 4.4.4. Also really looking forward to Android L on both of the units.
The way i look at it is what are YOUR pros and cons. LOL.
Click to expand...
Click to collapse
My "pros and cons" list involves having all pros and NO cons! lol
I think I'll prob just wait for the T-Mo OTAs from now on, but then again, b/c I have ViperOne, I won't know when they get deployed unless I constantly revert back to stock. Ughh! I guess so far I haven't really noticed a difference in signal and call quality since installing a non-carrier firmware, though it's only been like not even 2 weeks yet since I did it.
That's cool though that you're so happy with it. Perhaps your posts are an indication that T-Mobile has gotten better with their overall quality, and so that's something to look forward to for when I do go back to stock (whenever that is lol).
Thank You,
RockStar2005

Most people make a big deal about carrier OTAs. So you really dont need to revert back to check for them. As long as your active on the boards you will know when a device gets an OTA.
I failed to mention that part of why im happy with stock is because devices are now getting to the point where they are so fast that having bloat ware on them doesnt noticeably slow down the devices like they used to. At least i dont notice it. Pluse with 4.2.2 they allow you to "disable" most apps you dont want to use. So thats another plus.
Back in the day i used to root and do the custom ROM for extra battery life, or tethering, or to make the device snappier.
I honestly would have thought that someone else might have chimed in by now and added their 2 cents.

IAmSixNine said:
Most people make a big deal about carrier OTAs. So you really dont need to revert back to check for them. As long as your active on the boards you will know when a device gets an OTA.
I failed to mention that part of why im happy with stock is because devices are now getting to the point where they are so fast that having bloat ware on them doesnt noticeably slow down the devices like they used to. At least i dont notice it. Pluse with 4.2.2 they allow you to "disable" most apps you dont want to use. So thats another plus.
Back in the day i used to root and do the custom ROM for extra battery life, or tethering, or to make the device snappier.
I honestly would have thought that someone else might have chimed in by now and added their 2 cents.
Click to expand...
Click to collapse
Six,
Yeah, that's true. Or I can check on T-Mobile's update site, though there may still be some delay b/c of how they deploy OTAs: http://support.t-mobile.com/docs/DOC-10366
I've noticed that too, and before I got ViperOne and also Titanium Backup, I was disabling several apps too. Though I prefer to just uninstall them.
RockStar2005

Six,
I talked to one of the ppl at Team Venom, and he said he has T-Mobile and recommends just taking T-Mobile's firmware updates for better cell reception. I'll do that from now on. But for now, if anyone is interested, I have here a link to the latest radio image file for the M8 (as of 8/27). Just download and "install flash" in TWRP.
And if you're rooted and want to get rid of the "red splash" screen during boot-up, try flashing the attached mod! :victory:
http://www.mediafire.com/download/beucjivbc4i9y3u/RadioUpdate_2.22.531.5_1.19.213311491.03G.zip
Thank You,
RockStar2005

So... My question now.. I'm one of those buy vzw m8 take over to T-Mobile. I'm running viper 2.3. It runs great. But vzw never updated to newest firmware.so my question I guess is... Can I flash a T-Mobile radio or firmware to my vzw phone? I kinda know the answer, but I'd rather ask. So if I can.. that'll be great!
Sent from my HTC One_M8 using XDA Free mobile app

I know on the M7 that would brick the unit.
The CDMA and GSM units had different hardware and flashing any GSM ROM into a CDMA unit bricked them.
I want to say the same holds for the M8.
Can someone else confirm that for me?

IAmSixNine said:
I know on the M7 that would brick the unit.
The CDMA and GSM units had different hardware and flashing any GSM ROM into a CDMA unit bricked them.
I want to say the same holds for the M8.
Can someone else confirm that for me?
Click to expand...
Click to collapse
Yeah thanks I kinda figured that, but you know it never hurts to ask, especially if it has the potential to maybe work out.
Sent from my HTC One_M8 using XDA Free mobile app
---------- Post added at 08:23 AM ---------- Previous post was at 08:20 AM ----------
Then maybe would it be better for me when Verizon gets the ota for 4.4.3.... I should implement that, and then.... Redo my rom?
Sent from my HTC One_M8 using XDA Free mobile app

Brand new with HTC

Well i recently recieved an upgrade with my provider and I opted for the M9. This is because for the last 4 years ive had samsung and although I havent a bad word to say for them, I just fancied a change. So here I am.
Quite a difference in the way you can obtain certain things like unlocking, rooting etc. To be honest, though it was a bit worrying at first, I soon managed to get things done and It sort of makes you feel like you're more involved with your phone. Rather than just letting a .zip do all the work or a full firmware file through odin do the business.
Ive only had it 2 days and managed to root, unlock and s-off, Flashed a new firmware and rom and very happy with it. I have noticed despite the camera being a higher pixel count it isnt quite as sharp as the samsung camera, still good though. The front camera is definately better.
Having only had it 2 days though i cant really comment on performance etc etc. I need it longer but i'm relatively happy with how its going.
I do have a couple of concerns. 1 being the temperature it reaches when flashing etc.My samsung used to feel very warm but obviously its more noticable with the HTC due to it being all metal and I guess thats good as it sucks all the heat into the shell and away from the cpu's.
Anyway, this was just to say hi, and that I hope to continue to enjoy my htc experience, its definately come on a lot since my last HTC many years ago (Wildfire S).
Any tips / tricks / must haves that I should know about?
Thanks and HI! =)

tomorio said:
Well i recently recieved an upgrade with my provider and I opted for the M9. This is because for the last 4 years ive had samsung and although I havent a bad word to say for them, I just fancied a change. So here I am.
Quite a difference in the way you can obtain certain things like unlocking, rooting etc. To be honest, though it was a bit worrying at first, I soon managed to get things done and It sort of makes you feel like you're more involved with your phone. Rather than just letting a .zip do all the work or a full firmware file through odin do the business.
Ive only had it 2 days and managed to root, unlock and s-off, Flashed a new firmware and rom and very happy with it. I have noticed despite the camera being a higher pixel count it isnt quite as sharp as the samsung camera, still good though. The front camera is definately better.
Having only had it 2 days though i cant really comment on performance etc etc. I need it longer but i'm relatively happy with how its going.
I do have a couple of concerns. 1 being the temperature it reaches when flashing etc.My samsung used to feel very warm but obviously its more noticable with the HTC due to it being all metal and I guess thats good as it sucks all the heat into the shell and away from the cpu's.
Anyway, this was just to say hi, and that I hope to continue to enjoy my htc experience, its definately come on a lot since my last HTC many years ago (Wildfire S).
Any tips / tricks / must haves that I should know about?
Thanks and HI! =)
Click to expand...
Click to collapse
Hello. Welcome. I hope you enjoy your M9 experience.
Yeah, they heat up a little bit when flashing, but I think you're assumption on the metal body is correct.
I think the camera is not awesome in lower light situations. outside, it's fantastic. There's a thread on the camera in this forum you should check out, but some people who have used both the S6 and M9 say that the S6 is better in low light situations, but the M9 is better outside. You can probably get some tips in that that thread (http://forum.xda-developers.com/one-m9/general/pictures-m9-t3044267). A lot of people like shooting in manual mode with this phone and can produce some pretty nice results.

jollywhitefoot said:
Hello. Welcome. I hope you enjoy your M9 experience.
Yeah, they heat up a little bit when flashing, but I think you're assumption on the metal body is correct.
I think the camera is not awesome in lower light situations. outside, it's fantastic. There's a thread on the camera in this forum you should check out, but some people who have used both the S6 and M9 say that the S6 is better in low light situations, but the M9 is better outside. You can probably get some tips in that that thread (http://forum.xda-developers.com/one-m9/general/pictures-m9-t3044267). A lot of people like shooting in manual mode with this phone and can produce some pretty nice results.
Click to expand...
Click to collapse
Excellent thank you. I'll take a look and see if I can get any tips for improving my pictures. When I was in store chosing my next phone they did mention that it isn't the best in low light, probably due to the smaller aperture but I use take most of my pictures outside or in decent lighting anyway so I suppose it's not an issue as such. I'll definately have a look at that thread though and see if using manual mode will help me out more.
Thanks.
edit - I do have a quick question about firmwares. I have just flashed the 1.40.401.x but also noticed their are some 2.xx.xx something. Which are newer and why the huge difference? lol sorry to ask what is probably a very nooby question.

tomorio said:
Excellent thank you. I'll take a look and see if I can get any tips for improving my pictures. When I was in store chosing my next phone they did mention that it isn't the best in low light, probably due to the smaller aperture but I use take most of my pictures outside or in decent lighting anyway so I suppose it's not an issue as such. I'll definately have a look at that thread though and see if using manual mode will help me out more.
Thanks.
edit - I do have a quick question about firmwares. I have just flashed the 1.40.401.x but also noticed their are some 2.xx.xx something. Which are newer and why the huge difference? lol sorry to ask what is probably a very nooby question.
Click to expand...
Click to collapse
I find it takes pretty decent still life photos in low light, but not great snapshots of people/pets (things that move). I think on auto, the camera isn't aggressive enough in bumping ISO, so it has to use too slow a shutter speed to completely stop movement.
I think 1.40 was kind of a temporary release to quickly address some issues in 1.32 (camera and CPU management mostly)...I don't think it was ever officially released in the US. But 1.40 has issue of it's own, mainly that charging the phone can be extremely slow at times. I don't know how HTC comes up with firmware numbering, but I would guess that part of the big number jump has to do with the fact that 1.xx firmware was for Android 5.0.2 while the 2.7 firmware runs on Android 5.1. I flashed the 2.7 firmware last night and the 1.40 base rom that I use works fine with it so far...I can't say with certainty that your ROM will work with it though. FYI, I'm on InsertCoin.

jollywhitefoot said:
I find it takes pretty decent still life photos in low light, but not great snapshots of people/pets (things that move). I think on auto, the camera isn't aggressive enough in bumping ISO, so it has to use too slow a shutter speed to completely stop movement.
I think 1.40 was kind of a temporary release to quickly address some issues in 1.32 (camera and CPU management mostly)...I don't think it was ever officially released in the US. But 1.40 has issue of it's own, mainly that charging the phone can be extremely slow at times. I don't know how HTC comes up with firmware numbering, but I would guess that part of the big number jump has to do with the fact that 1.xx firmware was for Android 5.0.2 while the 2.7 firmware runs on Android 5.1. I flashed the 2.7 firmware last night and the 1.40 base rom that I use works fine with it so far...I can't say with certainty that your ROM will work with it though. FYI, I'm on InsertCoin.
Click to expand...
Click to collapse
Ah I see. I just noticed that most of the roms out at the moment recommend using the 1.40 firmware which is why I flashed that one. I'm currently using Viper which seems good so far, only had it a day. As I was new to everything I thought it best to stick with what is suggested as unlike with my Galaxy s4 the flashing of firmwares and roms seems quite specific. I had noticed it is quite a slow charge process, but I tend to charge overnight if I can and make the phone last the full day so it's not that much of a downer, unless i've had a lot of usage and need a "quick boost" >< then its not so great lol

tomorio said:
Ah I see. I just noticed that most of the roms out at the moment recommend using the 1.40 firmware which is why I flashed that one. I'm currently using Viper which seems good so far, only had it a day. As I was new to everything I thought it best to stick with what is suggested as unlike with my Galaxy s4 the flashing of firmwares and roms seems quite specific. I had noticed it is quite a slow charge process, but I tend to charge overnight if I can and make the phone last the full day so it's not that much of a downer, unless i've had a lot of usage and need a "quick boost" >< then its not so great lol
Click to expand...
Click to collapse
Many people have reported that rebooting temporarily fixes the slow charge issue.
MaximusHD is the only rom that uses the new firmware currently. I bet others will be updating soon. The Viper guys have been chatting about Viper 3.0 being released soon and I assume it will be 5.1 based.

Thats good. I'll keep checking any updates and see what happens.
I can't wait for a few more roms to be up and about. I'm used to the countless available for the S4 and forget that device is 2 years old now so there was plenty of time to get things going. I shall just have to be patient.
Thanks for all the help mate.

tomorio said:
Thats good. I'll keep checking any updates and see what happens.
I can't wait for a few more roms to be up and about. I'm used to the countless available for the S4 and forget that device is 2 years old now so there was plenty of time to get things going. I shall just have to be patient.
Thanks for all the help mate.
Click to expand...
Click to collapse
Not a problem. Enjoy the device.

Not to hijack your thread tomorio, but how did you decide on which phone? I have the Galaxy S5 now, but I'm torn between HTC M8, M9, or LG G4. Pros and cons to all. My biggest thing is ease of root as I have a couple of frequent use apps that require it. Thanks in advance for any tips on how you decided!
~Vol

Vol4Ever said:
Not to hijack your thread tomorio, but how did you decide on which phone? I have the Galaxy S5 now, but I'm torn between HTC M8, M9, or LG G4. Pros and cons to all. My biggest thing is ease of root as I have a couple of frequent use apps that require it. Thanks in advance for any tips on how you decided!
~Vol
Click to expand...
Click to collapse
Hijack away my friend.
I too was torn but between the S6, LG G4 and htc m9. I was leaning away from the S6 as I really fancied a change, however I think it will always have more options available to it (for custom roms etc) due to the larger fan base and it is much simpler to get to grips with for rooting etc.
the G4 my Partner already has and something about it when I used it I just didn't enjoy, and its nowhere near as pretty as the M9 lol. Try one out if you can just to see for yourself. Unfortunately I have no more experience of it than having a little play of her phone so unsure on the rooting processes etc but imagine it to be similar to the Samsung way.
The HTC M9 was a tough choice. Especially when I looked at how rooting etc is done (this is one of the first things i check with phones flash-a-holic you see lol). Anyway, once i'd read over all the advice given in this forum, the how to's etc and got a small amount of knowledge of the process of rooting using fastboot etc i pushed myself to make the choice. As far as user friendly goes, I think for simpler flashing the Sammy will always win again, as it's processes are far simpler (flashing via odin etc and all the files being ready to flash straight off the bat). However if you're keen for a change then I would recommend the M9. I've only had it a few days really but already i'm glad I did.
Just be sure to look through all the ways of rooting so that you get a better understanding of how its done. I think once the initial unlocking bootloader, rooting and flashing custom recovery is done it;s pretty simple after that. I've got to grips with it already.
One of the main benefits I found with the sammy phones was I was never worried about bricking because there were many different ways to get it back up and running. I dont know how that fares with the M9 but as long as you follow the instructions step by step and have backups available you should be ok.
Sorry for the wall of text, if you need anything else let me know.
Hope that helps.
- edit- also i may have touched on it in a previous post, but i think as far as customizing your phone goes and making it your own, I feel that HTC as a company are much more in tune with "our world" of people who like to change the stock features and put their own touch on things.

Walls of text don't bother me. I'd rather have too much information than not enough. It's going to be the M9 if we can work out the AT&T issues I mentioned in my other thread. I went to the store last night expecting a simple transaction like the bazillion other phone upgrades I've done over the years. Walked out steaming, to say the least. The worst part was the lady helping me majorly projected a "couldn't care less" attitude that is a major pet peeve of mine!