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)?
I made a big (rookie) mistake rushing through the reading on the Android Revolution HD ROM site.
My device model is SGH-i747 and the ROM I tried to flash was only intended for the international version of the S3 (i9300).
Now my device is hard bricked and I cant seem to find any solutions on recovering my device. Can someone help?
I believe i was running 4.1 before i tried upgrading to 4.3 (my phone hard-bricked once i completed the 4.3 installation) so I'm not sure exactly what image file i will need. Hope you can assist me with that as well.
I appreciate any and all advice.
You were running stock 4.1, loaded the international ROM, then tried to load stock 4.3? Is this correct?
If ypu can link to everything you flashed it would help. First it sounds like you bricked by flashing the wrong rom, but then it sounds like you bricked when updating your firmware.
Sent from my SGH-T999 using Tapatalk
audit13 said:
You were running stock 4.1, loaded the international ROM, then tried to load stock 4.3? Is this correct?
Click to expand...
Click to collapse
DocHoliday77 said:
If ypu can link to everything you flashed it would help. First it sounds like you bricked by flashing the wrong rom, but then it sounds like you bricked when updating your firmware.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yes i bricked the device while installing the Android Revolution HD ROM. Previously in was running the stock 4.1.2 Android system. Sorry but I cannot link the site to the Android Revolution HD ROM but I did notice it was for international versions of the S3 only. My current S3 model is the i-747 At&t.
Hope this was enough information to provide a helpful response. If not you can pm me and I'll share the needed info.
Thanks
audit13 said:
You were running stock 4.1, loaded the international ROM, then tried to load stock 4.3? Is this correct?
Click to expand...
Click to collapse
I loaded the international ROM by flashing with ROM Manager, once the installation was complete my device asked to reboot, once I selected yes my phone shutdown with no signs of life....hardbricked.
I never got the chance to bootup Android Revolution HD
Hope this info helps.
Can you remember if you ever took any ota updates or did you ever update by flashing firmware with Odin? Was the 4.1.2 you were running the official build or was it a ROM?
Better to discuss everything here rather than PM btw. Not only does it allow more people to try to help, reducing your wait time for answers, but it can also help others in the future.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
DocHoliday77 said:
Can you remember if you ever took any ota updates or did you ever update by flashing firmware with Odin? Was the 4.1.2 you were running the official build or was it a ROM?
Better to discuss everything here rather than PM btw. Not only does it allow more people to try to help, reducing your wait time for answers, but it can also help others in the future.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I had my device rooted with 4.4.4 CM firmware installed. I then flashed Slimkat 4.4 rom for a littlw while. After that I used the unroot process to unroot my device and flashed the stock 4.1 firmware using Kies. After Kies I decided I wanted to root device once more and install Android Revolution HD... I unrooted my device (still on 4.1 here) then began the process of flashing the 4.3 Revolution ROM. After that it died.
The debrick sdcard process should work fine for you then.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
DocHoliday77 said:
The debrick sdcard process should work fine for you then.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Just went out and bought a Samsung 16gb class 10 card. Hope it works well.
Do you by any chance have a link to the debrick image I should use for this process?
Hey I've tried doing the sd card method with a few different debrick files with no avail.
Am I missing something here?
Sometimes it takes several tries with the correct image before it'll work. Sometimes some SD cards just won't work. Are you sure its a genuine card? Sammy cards are very often found to be fakes.
Not saying it is, just a possibility. Try other SD cards too if you can. Even good ones just won't do the job sometimes.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
DocHoliday77 said:
Sometimes it takes several tries with the correct image before it'll work. Sometimes some SD cards just won't work. Are you sure its a genuine card? Sammy cards are very often found to be fakes.
Not saying it is, just a possibility. Try other SD cards too if you can. Even good ones just won't do the job sometimes.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
It's a card that I purchased from Wal-Mart, I assume it's legit.
Can you anyway direct me or post links to debrick images that are known to work?
p.s.- by try several times do you mean, Formatting sdcard, using win32 to write debrick image then putting it back into the phone?
If you were on 4.1.2 firmware, the 4.3 image in the op should work. Its been proven before.
Yes. Remake the sdcard. Can't recall if its in this forums op, but I personally used and prefer the Linux method of creating the sdcard. If its not here, go to the thread in the development section in T-Mobiles S3 forums. Its stickied at the top so you can't miss it. It has instructions for using both windows and a Linux LiveCD. Just don't use any Debrick.imgs from there.
As for the card itself, I hope things have gotten better about it, but in the past, faked sdcards have come from places like Walmart, best buy, radio shack, etc. The only way to truly know before buying is to make sure they are an authorized retailer. This means they buy direct from the manufacturer. Otherwise there could be multiple parties between the two which is where the problems occur. If you want to know more about it, there's tons of info and advice all over the net about this stuff. There are tools you can use to determine yours is the real deal, or a cheap knock off too. I can't remember what they are or what you have to look for when using them, but the info is out there.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
DocHoliday77 said:
If you were on 4.1.2 firmware, the 4.3 image in the op should work. Its been proven before.
Yes. Remake the sdcard. Can't recall if its in this forums op, but I personally used and prefer the Linux method of creating the sdcard. If its not here, go to the thread in the development section in T-Mobiles S3 forums. Its stickied at the top so you can't miss it. It has instructions for using both windows and a Linux LiveCD. Just don't use any Debrick.imgs from there.
As for the card itself, I hope things have gotten better about it, but in the past, faked sdcards have come from places like Walmart, best buy, radio shack, etc. The only way to truly know before buying is to make sure they are an authorized retailer. This means they buy direct from the manufacturer. Otherwise there could be multiple parties between the two which is where the problems occur. If you want to know more about it, there's tons of info and advice all over the net about this stuff. There are tools you can use to determine yours is the real deal, or a cheap knock off too. I can't remember what they are or what you have to look for when using them, but the info is out there.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
The SD card is good. I used Mini Tool Partition Wizard to verify that files were being transferred between my computer and the sd card.
Is this method verified to work if you flash an International rom onto a US device ?
I'm running low on options. I've tried 7 different debrick.img's with no luck.
Is there a link to numerous debrick imgaes for my issuse?
jabbaravila said:
The SD card is good. I used Mini Tool Partition Wizard to verify that files were being transferred between my computer and the sd card.
Is this method verified to work if you flash an International rom onto a US device ?
Click to expand...
Click to collapse
Yes its worked for this situation before. Maybe try creating it using Linux. Could also be that SD card just isn't going to work. There's no way to tell which ones will or won't. I've seen high quality class 10 cards fail where a generic class 4 worked. That's not usually the case but it does happen.
How many times are you trying with each image? Just use a known good one from the OP. Back when I did this I probably ended up with close to 15 attempts before it finally worked for me.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Unfortunately the same fate has befallen me! I have an SGH-I747U, and I used the CWM Bootloader to flash the Android Revolution version that's meant for i9300.
Did you ever get this working? Tried last night with an 8 GB SD card because it was all I had, but I'm going to get a 16 GB one today. Trying to use the debrick-SGH-I747U-CUEMJB3.img debrick image and I747UCUEMJB_2024954_REV04_user_low_ship.tar.rar stock ROM.
Is this the way to go? Any advice is really appreciated!
Hello there! Newb here so please be patient.
Currently running the UnSense ROM posted in these forums with no problem.
What I'd like to now do is change it to a purely Google Play (KitKat) edition phone, yet I want it to be able to receive immediate updates much like Nexus devices (I have a Nexus 7 and love the immediate updates).
OR
I'd like to be able to run Android L (Stock version not Sense/HTC) that I could eventually update to Lemon Miringue Pie or whatever it is that Google names the full version. Essentially I'm asking the same as above but I wanna do it from Android L.
Side Question:
What do I do before I run this ROM to keep all the current data on my phone? Apps, phone numbers, where the apps are, etc. Backup? nandroid? I need a decent explanation of the process so I can do it on my first shot.
Finally, THANK YOU! Seriously, I appreciate this help I love this forum.
Your best bet is to just run the GPE roms from the development section. The GSM versions have different mount points and radios than the Verizon variant. I think superCID to GPE and ruu could permanently brick this device. Only time that works is for some of the GSM variants.
Someone chime in if I am wrong. I just know our device is different and I don't want the OP to have a pretty paperweight on his hands.
Sent from my HTC6500LVW using XDA Free mobile app
You will need a backup program like titanium backup. As when you flash a new ROM you have to wipe everything but internal storage. Your phone numbers should be automatically to your Google account.
For titanium backup just select backup app and app data. Its worth the money to have if you don't like to reenter and download all your apps and enter the info.
Uzephi said:
I think superCID to GPE and ruu could permanently brick this device. Only time that works is for some of the GSM variants.
Click to expand...
Click to collapse
Is there not a Verion/CDMA version of the GPE ROM that I could run that wouldn't brick the device.
danregueira said:
Is there not a Verion/CDMA version of the GPE ROM that I could run that wouldn't brick the device.
Click to expand...
Click to collapse
Verizon believes heavily on locking down their devices. Last phone we had that ran AOSP/GPE was the galaxy nexus. Your only hope is use the GPE roms in development section. They are updated frequently.
Edit: try Santod's GPE. Once updates come from the GPE m7 or m8, he usually has a port of it released within a couple weeks max. http://forum.xda-developers.com/showthread.php?t=2531235
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
Your best bet is to just run the GPE roms from the development section. The GSM versions have different mount points and radios than the Verizon variant. I think superCID to GPE and ruu could permanently brick this device. Only time that works is for some of the GSM variants.
Someone chime in if I am wrong. I just know our device is different and I don't want the OP to have a pretty paperweight on his hands.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
agree 100%, the stock GPE is GSM and will not go well flashing on a CDMA phone. Stick to a GPE rom in our forum. A lot easier to flash
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.
I would like to use the leedroid 7.0 roms on my verizon htc 10. the main issue that i'm having is that , when I flash the rom my data isn't working right , right on the first boot up. this is where the problem mainly effects me. i have 2 step verification on my google account and i need my data and sms to work in order to finish the login process. i am not able to get code/email because network not activated. is there a zip i can flash after i flash rom in twrp , so that i can have the verizon apns and all that good stuff , .i love the leedroid roms . this is the only problem that keeps me from using it. would we be able to add the verizon option in aroma installer under network options to make it more easy to install? Would be a amazing implement and helpful to all us verizon devices. thanks leedroid.
You need to format your data. There is a problem with roms and encrpytion that stops the radios from working, and the only way to fix it is to format your data. I would suggest going into twrp, backing up your internal storage and then wiping your data.
I may be wrong, but im assuming you flashed the rom with no encryption, rather than WITH encryption (which is recommended).
Possibly the cause of your problem.
Its also worth making sure you know what firmware your phone has (MM or Nougat) and flashed the rom with the correct firmware setting. MM firmware is 1.95.401.X and Nougat for US is currently 2.28.XXX.X (it may be slightly different, but it will be around here somewhere)
I have tried encrypted and unencrypted , I do full wipes as i think its better than doing a dirty flash. I also format data and flash leedroid rom. The only way I could get it up and running was to bypass the setup initialization by modifying/deleting the apk from the zip file (Rom) completely. I have no issue with the radio not working , due to encryption status. Once I get in the rom with the modified zip . I can go straight to network and change it to ( global ) and the radios work , but it had slow network speed ( I do not have poor reception in my area) and numerous sms delivery errors. I am mainly trying to find a way to flash a zip in twrp to have radio working with verizon network upon (startup). Or the best option would be to have leedroid incorporate it in the aroma wizard in recovery for when all verizon users flash the new nougat roms on their devices, it fixes this no data on startup problem. All help and replies are much appreciated . Thank you
I've been trying various ROMs over the last few days on my VZW HTC 10. I only tried LeeDroid once (with the US Unlocked provider selected) but was unable to get any signal at all. I would love to get on LeeDroid, but i can't seem to get it to work on Verizon.
Just out of curiosity would the Viper10 Verizon script work on LeeDroid? I'm running Viper10 5.3.0 with the Verizon provider selected and all the features seem to be working, including Advanced Calling.
I will look into viper ROM and see if I can grab the Verizon data from it and use it in leedroid , just to see if it works . Thanks guys for your help
I have looked into viper rom but i could not figure out what to extract and put in leedroid rom. not that advanced yet lol
Justingaribay7 said:
I have looked into viper rom but i could not figure out what to extract and put in leedroid rom. not that advanced yet lol
Click to expand...
Click to collapse
Viper ROM is completely independent of Lee's ROM. With Viper you would place the zip file you downloaded into the root of your SD Card, boot into TWRP, wipe, then install the Viper ROM.
I played around with LeeDroid on my VZW HTC 10 today and actually got everything except Advanced Calling to work. In fact I can't even find those settings in the ROM. I had to select Sprint as my provider and I was able to get both Cell & Data signals. My bet is that the Advanced Calling features are part of the build.prop changes, but I could be wrong and will probably dig in deeper tonight.
I'm still very new to this kind of development, but hopefully can leverage my comp sci/dev background to figure something out.
I would suggest going to the verizon thread and using this rom
https://forum.xda-developers.com/ve...m-perfumewl-m60-dev-edition-unlocked-t3442969
Not as fancy as leedroid, but its a nougat rom, specific for verizon, and our current MM Firmware. We will get nougat one of these days.
Maybe @LeeDroid can bake in the verizon parts in his next nightly
Still waiting on my VZW guys pulling a patch together unfortunately, would love to support you guys!
You could try the US Unlocked option & change to.telephony.default_network to 10 in build.prop
aer0zer0 said:
I would suggest going to the verizon thread and using this rom
https://forum.xda-developers.com/ve...m-perfumewl-m60-dev-edition-unlocked-t3442969
Not as fancy as leedroid, but its a nougat rom, specific for verizon, and our current MM Firmware. We will get nougat one of these days.
Maybe @LeeDroid can bake in the verizon parts in his next nightly
Click to expand...
Click to collapse
Yeah, i played with that ROM a bit yesterday. Its nice if you want Stock, but Stock is boring. Also Viper10 is fully functional on VZW, like I said above.
LeeDroid said:
Still waiting on my VZW guys pulling a patch together unfortunately, would love to support you guys!
You could try the US Unlocked option & change to.telephony.default_network to 10 in build.prop
Click to expand...
Click to collapse
Thanks for the support @LeeDroid. I'm gonna do some analysis between various build.prop files in both LeeDroid & Viper10 to see if I stumble across anything interesting. I might try to peek at the various Verizon specific stuff that Viper10 has to see if anything there might be useful too. Once I can post in the Dev Threads I'll move my findings there, but until then I'll be posting anything I find here.
Guys.. I have just added Verizon support to my SVN for testing, Its R62.
If you want to give it a blast, you can manually check out or use one of my SVN zippers..
Let me know how it goes, more at www.leedroid.co.uk
LeeDroid said:
Guys.. I have just added Verizon support to my SVN for testing, Its R62.
If you want to give it a blast, you can manually check out or use one of my SVN zippers..
Let me know how it goes, more at www.leedroid.co.uk
Click to expand...
Click to collapse
I'm excited! Gonna try using one of the SVN Zippers. Gonna flash when I get home from work.
I guess I'll post the little bit of info I found while poking around in the build.prop files.
The only interesting settings I could find that seemed to relate to VZW Features that are missing from LeeDroid are the following:
ro.ril.vzw.feature=1
ro.config.svlte1x=true