Related
Since it's uncertain at this point if and when T-Mobile will be getting the 32Gb version of the Galaxy S4, I decided to buy the AT&T variant and use it on T-Mobile. I've had a few concerns (see below), all of which have been addressed except for a couple (highlighted below).
1. SIM unlocking - shouldn't be a problem as far as I can tell.
2. Rooting and Flashing new ROMs - I know that the AT&T S4 has the locked bootloader, does this mean I'll have problems with rooting and flshing new ROMs?
3. Enabling all T-Mobile bands (e.g AWS) - possible per this thread.
4. Enabling WiFi calling - possible if a T-Mobile ROM is installed (at least this was the case with the S3).
5. Installing a T-Mobile ROM (ROM based on 16Gb T-Mobile stock) on a 32Gb Galaxy S4 - Possible? Any problems with partitioning?
I will appreciate any input form the knowledgeable forum participants. Thanks.
re: questions
ferganer said:
Since it's uncertain at this point if and when T-Mobile will be getting the 32Gb version of the Galaxy S4, I decided to buy the AT&T variant and use it on T-Mobile. I've had a few concerns (see below), all of which have been addressed except for a couple (highlighted below).
1. SIM unlocking - shouldn't be a problem as far as I can tell.
2. Rooting and Flashing new ROMs - I know that the AT&T S4 has the locked bootloader, does this mean I'll have problems with rooting and flshing new ROMs?
3. Enabling all T-Mobile bands (e.g AWS) - possible per this thread.
4. Enabling WiFi calling - possible if a T-Mobile ROM is installed (at least this was the case with the S3).
5. Installing a T-Mobile ROM (ROM based on 16Gb T-Mobile stock) on a 32Gb Galaxy S4 - Possible? Any problems with partitioning?
I will appreciate any input form the knowledgeable forum participants. Thanks.
Click to expand...
Click to collapse
You will have no problems rooting and flashing new roms with the AT&T S4.
The 32GB MicroSD card works perfectly in ALL the Galaxy S4 varients including the AT&T.
If you purchase your phone from AT&T outright they will Unlock it for you for free.
(there are many other ways to unlock the phone)
Good luck
Misterjunky said:
You will have no problems rooting and flashing new roms with the AT&T S4.
Click to expand...
Click to collapse
Thanks for the quick response. So what does locked bootloader mean?
Misterjunky said:
The 32GB MicroSD card works perfectly in ALL the Galaxy S4 varients including the AT&T.
Click to expand...
Click to collapse
My question was not about the 32Gb SD crad. I was wondering if I can install a T-Mobile ROM on a 32Gb (internal RAM) AT&T S4. Since a T-Mobile stock ROM will most probably come from and will be designed for (partition size-wise?) for 16Gb of internal memory, I was wondering if it will be difficult/possible to install such a ROM on a 32Gb S4 and make use of the larger internal storage.
Thanks again.
AT&T on T-Mobile?
ferganer said:
Thanks for the quick response. So what does locked bootloader mean?
Click to expand...
Click to collapse
Probably should start here with rooting.
And with this recovery you should be able to flash any ROM for the most part that runs the Snapdragon quad-core model (att/canadia-variants, tmo, even the international variant (GT-i9505 only)).
Lastly, if you are needing to utilize the AWS aspect of your phone, you should probably stop off here.
As far as the storage, I've not seen anything regarding seperate ROMs for 16/32/64 GB models, so I don't know why you'd need to worry too much about that.. but I could be wrong.
I'm not all up to date on whether the T-Mobile ROMs are auto-loki'd, but since you're using the AT&T variant, you would have to make certain the ROMs you flash have been made to use djrbliss' bootloader workaround.
re: external sdcard
ferganer said:
Thanks for the quick response. So what does locked bootloader mean?
My question was not about the 32Gb SD crad. I was wondering if I can install a T-Mobile ROM on a 32Gb (internal RAM) AT&T S4. Since a T-Mobile stock ROM will most probably come from and will be designed for (partition size-wise?) for 16Gb of internal memory, I was wondering if it will be difficult/possible to install such a ROM on a 32Gb S4 and make use of the larger internal storage.
Thanks again.
Click to expand...
Click to collapse
Any and all roms which you will be flashing reside in the protected ROOT of the phone,
whether you have NO external sdcard or a 16GB or 64GB external sdcard the actual
rom, radio, kernel, bootloader and all other files required for the rom are all flashed
into that protected ROOT partition of the phone.
So the size of the external sdcard makes no difference at all as far as roms go.
But the bigger it is the more space you will have for your videos, music, pictures,
nandroid backups and, custom roms you will be flashing or anything else which
you might want to keep on the external sdcard.
Misterjunky said:
So the size of the external sdcard makes no difference at all as far as roms go.
Click to expand...
Click to collapse
Thanks, but my concern is INTERNAL not external memory differences.
I hope that the size of the INTERNAL storage also makes no difference at all as far as ROMs go.
ferganer said:
Since it's uncertain at this point if and when T-Mobile will be getting the 32Gb version of the Galaxy S4, I decided to buy the AT&T variant and use it on T-Mobile. I've had a few concerns (see below), all of which have been addressed except for a couple (highlighted below).
1. SIM unlocking - shouldn't be a problem as far as I can tell.
2. Rooting and Flashing new ROMs - I know that the AT&T S4 has the locked bootloader, does this mean I'll have problems with rooting and flshing new ROMs?
3. Enabling all T-Mobile bands (e.g AWS) - possible per this thread.
4. Enabling WiFi calling - possible if a T-Mobile ROM is installed (at least this was the case with the S3).
5. Installing a T-Mobile ROM (ROM based on 16Gb T-Mobile stock) on a 32Gb Galaxy S4 - Possible? Any problems with partitioning?
I will appreciate any input form the knowledgeable forum participants. Thanks.
Click to expand...
Click to collapse
Its your prerogative, but Its just my opinion...I wouldn't have waisted money on anothr carriers model just to have the 32g version so soon.
Even tho att and tmo... have become so compatible on data bands and you can make both sims work on either carriers phone, it still is a downside ... what about legit insurance . Unless you need it or have a 3rd party insurer, I doubt you can ever claim a att phone with t mobile.
Wifi calling is gone for you, unless you catch a rom that' has it incorporated...etc
Sent from my SGH-M919 using xda premium
---------- Post added at 07:28 AM ---------- Previous post was at 07:24 AM ----------
ferganer said:
Thanks for the quick response. So what does locked bootloader mean?
My question was not about the 32Gb SD crad. I was wondering if I can install a T-Mobile ROM on a 32Gb (internal RAM) AT&T S4. Since a T-Mobile stock ROM will most probably come from and will be designed for (partition size-wise?) for 16Gb of internal memory, I was wondering if it will be difficult/possible to install such a ROM on a 32Gb S4 and make use of the larger internal storage.
I can tell you one thing for sure... I flashed a t mobile 4.1.2 tar right onto my brother's att s3 , so wether development is same or up to date with the s4 being so new in that manner i dunno, but I can say for the s3 you can flash t mobile tar files and some roms ,for instance t motion is a tmo based rom that works for att s3b if that helps.
Look into this further
Thanks again.
Click to expand...
Click to collapse
Sent from my SGH-M919 using xda premium
ferganer said:
Since it's uncertain at this point if and when T-Mobile will be getting the 32Gb version of the Galaxy S4, I decided to buy the AT&T variant and use it on T-Mobile. I've had a few concerns (see below), all of which have been addressed except for a couple (highlighted below).
1. SIM unlocking - shouldn't be a problem as far as I can tell.
2. Rooting and Flashing new ROMs - I know that the AT&T S4 has the locked bootloader, does this mean I'll have problems with rooting and flshing new ROMs?
3. Enabling all T-Mobile bands (e.g AWS) - possible per this thread.
4. Enabling WiFi calling - possible if a T-Mobile ROM is installed (at least this was the case with the S3).
5. Installing a T-Mobile ROM (ROM based on 16Gb T-Mobile stock) on a 32Gb Galaxy S4 - Possible? Any problems with partitioning?
I will appreciate any input form the knowledgeable forum participants. Thanks.
Click to expand...
Click to collapse
As someone who has done it
1.) Works fine, performs as expected
2.) Yes.... yes you will... limits you a bit. YOu can't just dump a TMO rom on, you have to make sure to use LOKI_DOKI after flashing (DONT REBOOT) and you can't use ODIN for the flash. (I use complete stock... now I cant #&%)(#*%)
3.) It works 100%, I haven't noticed a single problem. Battery usage is normal unlike the conversion on the GS2 and GS3.
4.) Have to use a TMO rom
5.) Yes possible, you leave the partitioning alone. DO NOT EVER REPARTITION UNLESS YOU WISH DEATH TO THE PHONE.
Note: The PIT prevents the death, there isnt one for the S4 yet...
Haxel said:
As someone who has done it
1.) Works fine, performs as expected
2.) Yes.... yes you will... limits you a bit. YOu can't just dump a TMO rom on, you have to make sure to use LOKI_DOKI after flashing (DONT REBOOT) and you can't use ODIN for the flash. (I use complete stock... now I cant #&%)(#*%)
3.) It works 100%, I haven't noticed a single problem. Battery usage is normal unlike the conversion on the GS2 and GS3.
4.) Have to use a TMO rom
5.) Yes possible, you leave the partitioning alone. DO NOT EVER REPARTITION UNLESS YOU WISH DEATH TO THE PHONE.
Note: The PIT prevents the death, there isnt one for the S4 yet...
Click to expand...
Click to collapse
Thanks a lot for the answers. I got everything except for "now I cant #&%)(#*%)".
Tethering
ferganer said:
Thanks a lot for the answers. I got everything except for "now I cant #&%)(#*%)".
Click to expand...
Click to collapse
I have the AWS booted and it works great.
What do I have to do to get tethering (ATT 32gb now on tmobile)?
Hey guys, this is my first HTC device. I've been reading through the threads here and in the intl forum and I just wanted to get a little info in one place as to what we can flash for this device. I sent mine off to someone with a Java Card, so now that I'm good to go, I wanted to see what all I (and other VZW users) can do at this early stage in the game. I know that until there is an easier way to S-Off/root/etc than sending your device to someone it is still kinda rocky as to development on this particular device, but I've heard mixed reviews on what ROMs/kernels are good to flash.
I assume that as long as I've got a custom recovery, flashing ROMs on this device would be the same as the other devices I've used... just pick the file in TWRP and flash, right?
As far as ROMs go, I've read that ViperOne works, along with InsertCoin with nothing extra.. just flash and go apparently. As for other ROMs, a little editing and some files from the stock VZW ROM should make them work, right? What files exactly would be needed?
Basically, if you've flashed anything, post your results here. What works, what doesn't, anything I should do before I start flashing myself. Any good threads I should read before I jump in. Thanks guys!
I have a thread about the roms in this forum named VZW M9 roms.
Basically the ones you've named I've tried with success. Also LeeDrOiD rom added Verizon support today. Build 7.5.
jtommyj said:
I have a thread about the roms in this forum named VZW M9 roms.
Basically the ones you've named I've tried with success. Also LeeDrOiD rom added Verizon support today. Build 7.5.
Click to expand...
Click to collapse
I never claimed to be a genius I've read through your thread, that's where I got the ROMs that worked... My brain wasn't working at full capacity when I made the thread. Thanks.
That being said though, lets assume that a soft-brick occurs. How would one go about fixing that? In my experience with the S4 and the device I had previous to that, it was simple to fix a soft-brick as long as I still had recovery access. Would the same be true for the M9? What about reverting to stock.. as in stock recovery, firmware, etc. Also, from what I've seen, adb tends to be used a bit more for this device than others that I'm used to. Not that I have a problem with it, I just haven't used it very much and will likely have to brush up a little bit on the nuances of it. I just don't want to create a $650 paperweight so I want to be absolutely sure that what I'm doing can be fixed, and that I avoid doing things that CAN'T be fixed.
lordcheeto03 said:
I never claimed to be a genius I've read through your thread, that's where I got the ROMs that worked... My brain wasn't working at full capacity when I made the thread. Thanks.
That being said though, lets assume that a soft-brick occurs. How would one go about fixing that? In my experience with the S4 and the device I had previous to that, it was simple to fix a soft-brick as long as I still had recovery access. Would the same be true for the M9? What about reverting to stock.. as in stock recovery, firmware, etc. Also, from what I've seen, adb tends to be used a bit more for this device than others that I'm used to. Not that I have a problem with it, I just haven't used it very much and will likely have to brush up a little bit on the nuances of it. I just don't want to create a $650 paperweight so I want to be absolutely sure that what I'm doing can be fixed, and that I avoid doing things that CAN'T be fixed.
Click to expand...
Click to collapse
Well first thing you need to have a custom recovery flashed.
Then you would need to backup your stock system. If you are in a soft brick then volume up and power being held at the same time should get you out of it.
There should not be a need to refresh firmware since the original firmware is all we have. I do believe an Ruu is being worked on currently.
Final word- if you're unsure,don't!!
I want the buy it from Amazon. But there are so many different versions that I confused. I'm looking for the 32 GB/3 GB RAM version. Would you kindly provide me a link?
D855 32 GB Is The MOst Supported Variant OF The G3 Right now
depends what rom you want most variants have cyanogenmod but custom roms differ alot of the most popular roms support all variants but he's right d855 is most supported. i have a d852 cuz i'm from canada eh.
edit was adding a s to the word custom lol i wrote it cutom first.
SirDarknight said:
I want the buy it from Amazon. But there are so many different versions that I confused. I'm looking for the 32 GB/3 GB RAM version. Would you kindly provide me a link?
Click to expand...
Click to collapse
D855 if you don't care about LTE. I'm on AT&T and had the 850 last year but hated the PMA wireless charging. Sold it and have had at least 5 different phones, 2 S6s and a G4 and now I'm back to a G3 D851. I chose this because of the unlocked bootloader and standard QI wireless charging as well as LTE with AT&T. It's not the fastest but it's hard to beat for a great all around daily driver as IR and QI are must haves for me.
KronicSkillz said:
depends what rom you want most variants have cyanogenmod but custom roms differ alot of the most popular roms support all variants but he's right d855 is most supported. i have a d852 cuz i'm from canada eh.
edit was adding a s to the word custom lol i wrote it cutom first.
Click to expand...
Click to collapse
I saw in your signature : dual boot. How did you do that and does it affect your boot time and performance?
Go for d855
SirDarknight said:
I saw in your signature : dual boot. How did you do that and does it affect your boot time and performance?
Click to expand...
Click to collapse
that sig was really old but thanks for reminding me to update it, i honestly can't remember my old dual boot setup but i think it's still possible.
An easy way is to keep updated twrp backups of both roms you want to use on your internal sdcard (because it's way faster then external (generally unless you have a pricey external)) then whenever you want to swap just boot to recovery and restore the other rom and boot. Make sure your backups include the cache partition (this will prevent android is updating after you restore the rom) and it will boot like normal right away.
believe it or not using this method you can swap back and fourth from roms in about 3-4 minutes and your boot times will be normal other then the 3-4 min it takes to restore the rom. This isn't very practical if you are switching all the time but if you only use your backup rom once and a while its good. the part that takes a long time is keeping both rom backups up to date.
I can't remember my dual boot setup though sorry to disappoint.
Maybe I'll skip that hassle!
Just ordered my HTC 10, excited...and nervous as I've not had a new device (like long term) in... like over 1.5 years. :S I'm mainly hoping the microSD card slot likes my 128GB U1 x633 card so I can finally have enough space for all my vinyl rips, and then I hope the DAC is as good as they say.
So anyway, I've been reading all of this stuff about rooting and loosing the radio connection and something about the data encryption breaking everything O.O!!! Holy crap. I just wanna root it, find a good rom and dev to support and enjoy it. This is what I do on my current daily driver, my old OPO. I've been trying to look around, search, and read to make sure that I avoid all of these issues mentioned but so far I've not found a concrete explanation of why said issues happen. Not new to rooting/flashing at all, but HTC devices always seemed to of been touchy when it came to custom stuff, and I don't want to explode this thing. My main problem is that I've been away from HTC for.... well since early 2014.
My current knowledge of android stuffz tells me to:
1) Unlock Bootloader via ADB
2) Flash TWRP/Other Customer Recovery
3) Find sweet rom, flash and spend hours customizing
4) Flash xposed and go crazy with modules until the phone explodes and then scale it back to a realistic level
5) Enjoy Phone
6) Cake
HOWEVER... I remember HTC devices having a bit more complication due to things like... RUU and firmware.. I don't even remember what RUU means lol... But I remember when I had my M8 I was always fighting these dang firmware issues. While I ended up with a fantastic experience, I remember fighting for almost 2 months or so to get it to behave. Battery was out of control, phone was crashing, camera exploding. Oh man it sucked, but finally someone really cool was like... "Yo dude I had these issues, this is what you have to do with HTC stuff" , and after a full hour of flashing shiz I had the phone running smoothly and behaving correctly. Something about... you had to flash each level of the firmware and then reboot and...something. Like you couldn't just skip to the latest firmware? I don't remember exactly.
So anyway, the main question I have is. Could someone either
A.) Point me in the direction of a post or something to study to understand what to do and not do. I've searched but not really found anything solid. Something for folks who've been off the HTC scene for a while.
B.) If there isn't really a single post on this, perhaps if someone doesn't mind explaining this (even pm is fine) to me so I don't explord this expensive mofo and cry.
C.) Give me a hug, because I am nervous about having a new device O.O , it's been so long and I'm so used to Cm13 and xposed and all that jazz. I is be scared.
I would be grateful to any and all help/support.
Anyway, thanks in advanced guys and gals. :3
Locklear308 said:
Just ordered my HTC 10, excited...and nervous as I've not had a new device (like long term) in... like over 1.5 years. :S I'm mainly hoping the microSD card slot likes my 128GB U1 x633 card so I can finally have enough space for all my vinyl rips, and then I hope the DAC is as good as they say.
So anyway, I've been reading all of this stuff about rooting and loosing the radio connection and something about the data encryption breaking everything O.O!!! Holy crap. I just wanna root it, find a good rom and dev to support and enjoy it. This is what I do on my current daily driver, my old OPO. I've been trying to look around, search, and read to make sure that I avoid all of these issues mentioned but so far I've not found a concrete explanation of why said issues happen. Not new to rooting/flashing at all, but HTC devices always seemed to of been touchy when it came to custom stuff, and I don't want to explode this thing. My main problem is that I've been away from HTC for.... well since early 2014.
My current knowledge of android stuffz tells me to:
1) Unlock Bootloader via ADB
2) Flash TWRP/Other Customer Recovery
3) Find sweet rom, flash and spend hours customizing
4) Flash xposed and go crazy with modules until the phone explodes and then scale it back to a realistic level
5) Enjoy Phone
6) Cake
HOWEVER... I remember HTC devices having a bit more complication due to things like... RUU and firmware.. I don't even remember what RUU means lol... But I remember when I had my M8 I was always fighting these dang firmware issues. While I ended up with a fantastic experience, I remember fighting for almost 2 months or so to get it to behave. Battery was out of control, phone was crashing, camera exploding. Oh man it sucked, but finally someone really cool was like... "Yo dude I had these issues, this is what you have to do with HTC stuff" , and after a full hour of flashing shiz I had the phone running smoothly and behaving correctly. Something about... you had to flash each level of the firmware and then reboot and...something. Like you couldn't just skip to the latest firmware? I don't remember exactly.
So anyway, the main question I have is. Could someone either
A.) Point me in the direction of a post or something to study to understand what to do and not do. I've searched but not really found anything solid. Something for folks who've been off the HTC scene for a while.
B.) If there isn't really a single post on this, perhaps if someone doesn't mind explaining this (even pm is fine) to me so I don't explord this expensive mofo and cry.
C.) Give me a hug, because I am nervous about having a new device O.O , it's been so long and I'm so used to Cm13 and xposed and all that jazz. I is be scared.
I would be grateful to any and all help/support.
Anyway, thanks in advanced guys and gals. :3
Click to expand...
Click to collapse
I was in the same boat haven't owed an HTC since the Fuze running Windows lol and have been a loyal Samsung user since the S1 so the whole adb fastboot thing was a little overwhelming. I followed the guide in the forum and had a few hiccups but overall went pretty smooth. Adb is definitely not as user friendly as Odin on a Sammy device but not to difficult. My only tips would be make sure you have all the latest drivers, twrp, and adb installed. It seems pretty hard to permanently brick a device these days from my experience so I wouldn't worry to much. As far as the radio not working, as long as you keep your device encrypted you won't lose your radio. I'm sure the devs will find a fix for this soon enough. Enjoy your new 10!
Edit: I'm using a lexar 128gb 633x U1 micro sd and all is well. Worked with adoptable storage also but felt a little sluggish so I went back to using it as external storage.
AndroiderM said:
I was in the same boat haven't owed an HTC since the Fuze running Windows lol and have been a loyal Samsung user since the S1 so the whole adb fastboot thing was a little overwhelming. I followed the guide in the forum and had a few hiccups but overall went pretty smooth. Adb is definitely not as user friendly as Odin on a Sammy device but not to difficult. My only tips would be make sure you have all the latest drivers, twrp, and adb installed. It seems pretty hard to permanently brick a device these days from my experience so I wouldn't worry to much. As far as the radio not working, as long as you keep your device encrypted you won't lose your radio. I'm sure the devs will find a fix for this soon enough. Enjoy your new 10!
Click to expand...
Click to collapse
Well I am comfortable in adb :3 so that's not a worry. So un-enecrypting it is just an option, and I should just avoid it for now? What is the advantage of un-encrypting it?
What guide did you use? Also, what about all this firmware and ruu stuff?
Sorry for so many questions... Lol this thing wasn't cheap and I am nervous , BTW what setup do you have? Root? ROM?
Thanks for replying :3
Locklear308 said:
Well I am comfortable in adb :3 so that's not a worry. So un-enecrypting it is just an option, and I should just avoid it for now? What is the advantage of un-encrypting it?
What guide did you use? Also, what about all this firmware and ruu stuff?
Sorry for so many questions... Lol this thing wasn't cheap and I am nervous , BTW what setup do you have? Root? ROM?
Thanks for replying :3
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-10/how-to/guide-root-optionally-s-off-radio-t3373025
From what I understand unencrypting breaks the radio. With it unencrypted you would get slightly better performance and boot times I think. I would definitely avoid it for now. I'm currently using twrp with Viper 10 rom. I've also used leedroid and still trying to find which one I prefer. I've only had my 10 for 3 days lol so I haven't found my sweet setup just yet. I left s-on for now as I don't really need it off.
No idea about the firmware and ruu stuff. I made a backup of stock rom before I started flashing. I'm pretty sure there is or will be a repo with factory firmware, radios, etc. I don't know what ruu stands for either lol.
---------- Post added at 06:56 AM ---------- Previous post was at 06:51 AM ----------
Did you get carrier or unlocked version
AndroiderM said:
http://forum.xda-developers.com/htc-10/how-to/guide-root-optionally-s-off-radio-t3373025
From what I understand unencrypting breaks the radio. With it unencrypted you would get slightly better performance and boot times I think. I would definitely avoid it for now. I'm currently using twrp with Viper 10 rom. I've also used leedroid and still trying to find which one I prefer. I've only had my 10 for 3 days lol so I haven't found my sweet setup just yet. I left s-on for now as I don't really need it off.
No idea about the firmware and ruu stuff. I made a backup of stock rom before I started flashing. I'm pretty sure there is or will be a repo with factory firmware, radios, etc. I don't know what ruu stands for either lol.
---------- Post added at 06:56 AM ---------- Previous post was at 06:51 AM ----------
Did you get carrier or unlocked version
Click to expand...
Click to collapse
Unlocked, at least that's what the guy on Swappa marked it as. *fingers crossed*
Got it for 510. One scratch on the metal
Alright so I will back things up and avoid the radio breaking stuff. I will check that link, thanks man
Locklear308 said:
Unlocked, at least that's what the guy on Swappa marked it as. *fingers crossed*
Got it for 510. One scratch on the metal
Alright so I will back things up and avoid the radio breaking stuff. I will check that link, thanks man
Click to expand...
Click to collapse
No problem, mine has two scratches on metal too lol but guy gave me $200 and unlocked htc 10 w uh oh protection and original receipt for my s7e at&t branded locked bootloader ?. Was a no brainer for me
Locklear308 said:
Just ordered my HTC 10, excited...and nervous as I've not had a new device (like long term) in... like over 1.5 years. :S I'm mainly hoping the microSD card slot likes my 128GB U1 x633 card so I can finally have enough space for all my vinyl rips, and then I hope the DAC is as good as they say.
So anyway, I've been reading all of this stuff about rooting and loosing the radio connection and something about the data encryption breaking everything O.O!!! Holy crap. I just wanna root it, find a good rom and dev to support and enjoy it. This is what I do on my current daily driver, my old OPO. I've been trying to look around, search, and read to make sure that I avoid all of these issues mentioned but so far I've not found a concrete explanation of why said issues happen. Not new to rooting/flashing at all, but HTC devices always seemed to of been touchy when it came to custom stuff, and I don't want to explode this thing. My main problem is that I've been away from HTC for.... well since early 2014.
My current knowledge of android stuffz tells me to:
1) Unlock Bootloader via ADB
2) Flash TWRP/Other Customer Recovery
3) Find sweet rom, flash and spend hours customizing
4) Flash xposed and go crazy with modules until the phone explodes and then scale it back to a realistic level
5) Enjoy Phone
6) Cake
HOWEVER... I remember HTC devices having a bit more complication due to things like... RUU and firmware.. I don't even remember what RUU means lol... But I remember when I had my M8 I was always fighting these dang firmware issues. While I ended up with a fantastic experience, I remember fighting for almost 2 months or so to get it to behave. Battery was out of control, phone was crashing, camera exploding. Oh man it sucked, but finally someone really cool was like... "Yo dude I had these issues, this is what you have to do with HTC stuff" , and after a full hour of flashing shiz I had the phone running smoothly and behaving correctly. Something about... you had to flash each level of the firmware and then reboot and...something. Like you couldn't just skip to the latest firmware? I don't remember exactly.
So anyway, the main question I have is. Could someone either
A.) Point me in the direction of a post or something to study to understand what to do and not do. I've searched but not really found anything solid. Something for folks who've been off the HTC scene for a while.
B.) If there isn't really a single post on this, perhaps if someone doesn't mind explaining this (even pm is fine) to me so I don't explord this expensive mofo and cry.
C.) Give me a hug, because I am nervous about having a new device O.O , it's been so long and I'm so used to Cm13 and xposed and all that jazz. I is be scared.
I would be grateful to any and all help/support.
Anyway, thanks in advanced guys and gals. :3
Click to expand...
Click to collapse
I'm on my third htc10. Exploded last two after rooting haha. Really not hard mate. Just read the guides provided and ask any questions you need. Most ppl on XDA will be helpful, and some will reply like me lol.
BTW, simple answer, unlock phone via HTC Dev, then flash Viper. Done.
purple patch said:
I'm on my third htc10. Exploded last two after rooting haha. Really not hard mate. Just read the guides provided and ask any questions you need. Most ppl on XDA will be helpful, and some will reply like me lol.
BTW, simple answer, unlock phone via HTC Dev, then flash Viper. Done.
Click to expand...
Click to collapse
Alright neato, so do I need to ensure I let it download any and all OTA's for the firmware before doing anything? Is s-off safe to get as well in regards to the issues I referred to in my OP above?
And his is this viper? Does it allow things like settings similar to cm and also allow for xposed?
Thanks for replying man, I feel more comfortable now as it sounds like there isn't anything crazy required to safely root this thing . Phew!!
Locklear308 said:
Alright neato, so do I need to ensure I let it download any and all OTA's for the firmware before doing anything? Is s-off safe to get as well in regards to the issues I referred to in my OP above?
And his is this viper? Does it allow things like settings similar to cm and also allow for xposed?
Thanks for replying man, I feel more comfortable now as it sounds like there isn't anything crazy required to safely root this thing . Phew!!
Click to expand...
Click to collapse
I got an M9 for my wife not that long ago and just had my 10 show up today and gonna root. Just do like the other dude said. Find a guide that says how to use HTC dev to unlock the bootloader. You can't just enter a command in adb like "unlock bootloader" and have it work. Go to the HTC dev website, make an account, pick your device and it walks you through the steps of unlocking the bootloader. That's really the only semi-difficult part IMO. Then proceed as normal. Download twrp, make a stock nand, download ROM, su binaries, kernel, etc. etc. go to recovery and flash. I'm sure there's a couple other steps in their but that's the basics.
As for Viper, it tends to come with so many mods built in, I'd personally be kind of reluctant to use xposed with it to to much modifying. It's a great ROM, but so is leedroid You can try each and see what you like, but if you want to more safely use xposed I'd personally go with leedroid.
DroidIt! said:
I got an M9 for my wife not that long ago and just had my 10 show up today and gonna root. Just do like the other dude said. Find a guide that says how to use HTC dev to unlock the bootloader. You can't just enter a command in adb like "unlock bootloader" and have it work. Go to the HTC dev website, make an account, pick your device and it walks you through the steps of unlocking the bootloader. That's really the only semi-difficult part IMO. Then proceed as normal. Download twrp, make a stock nand, download ROM, su binaries, kernel, etc. etc. go to recovery and flash. I'm sure there's a couple other steps in their but that's the basics.
As for Viper, it tends to come with so many mods built in, I'd personally be kind of reluctant to use xposed with it to to much modifying. It's a great ROM, but so is leedroid You can try each and see what you like, but if you want to more safely use xposed I'd personally go with leedroid.
Click to expand...
Click to collapse
Oh right, I do remember about the whole HTC dev website thing. I was mainly just concerned with the firmware issues and stuff that I had before.
Is there any kind of limitations for reasons not to upgrade to the highest available firmware? Something like, maybe the highest one can't be rooted yet or something like that. I just want to make sure that I don't shoot myself in the foot haha.
Thank you all for your help
Locklear308 said:
Oh right, I do remember about the whole HTC dev website thing. I was mainly just concerned with the firmware issues and stuff that I had before.
Is there any kind of limitations for reasons not to upgrade to the highest available firmware? Something like, maybe the highest one can't be rooted yet or something like that. I just want to make sure that I don't shoot myself in the foot haha.
Thank you all for your help
Click to expand...
Click to collapse
Hey, I'm not sure about firmware not being able to be rooted but the best way to go about it (what I did anyway) is to unlock the phone via htcdev.com, flash a custom recovery (Latest TWRP which has also worked around the encryption stuff?) and then back up everything other than the data partition. That way, no matter what you do, you always have something to revert back to. The reason for not backing up data is due to the encryption. From my understanding, restoring an encrypted data partition would break things. Once you have the phone unlocked and recovery sorted, you are free to flash viper etc. and root the phone using SuperSU. I'm sure you are aware unlocked devices are quite easy to root so whatever you flash will most likely be on latest firmware, already rooted.
As for installing OTAs etc., you need unmodified system and recovery which is where the backups kick in. Simply back up your data on an SD card (pictures etc. not the actual partition) and restore the system-image and recovery. This should reset the phone although I'm not sure if it'll wipe anything and allow you to do OTA updates. Alternatively, get the latest firmware for your device from htcdev (again, not sure if they have firmware on there) and use that instead.
If any of the information above is incorrect or missing steps, someone feel free to correct me.
Hi guys,
I really liked that phone, when I've seen the specification and devs support on xda!
However... I'd like you to tell me what about modding the phone directly from you. I noticed, that unlocking bootloader can be done in official way, so it's probably easy. What about the rest, what should I know?
Now I have LG G2 mini and I'm already tired of it. After unlocking bootloader in unofficial way (there's no official) - one bad step and you have hardbrick (I did that once).
So... tell me what you know! About jumping between ROMs, possibility of hardbrick when flashing ROMs, going back to stock, etc, etc... You know
Hey guys, I just want to hear the brief story about - how easy is to mod this phone (or if you prefer - how easy is to hardbrick it comparing to other phones).
bump ;]
Buy a heat glove to hold it with.
unexpected0ne said:
(or if you prefer - how easy is to hardbrick it comparing to other phones).]
Click to expand...
Click to collapse
Virtually impossible to hard brick: as soon as you're close to fυckιng everything up you can perform a full flash of all partitions that will wipe any changes. They're called RUU packages, are provided by HTC themselves, are total lifesavers.
I've had a hd2 a nexus 5 a samsung 4 and this phone is the most difficult to root and install a custom rom on it. I would avoid it unless it was a free gift.