I am having a huge issue with getting data to work on my HTC One X international. Any rom i try, aosp or sense, as long as its based on android 4.0.3 can get data to work.
But any rom, aosp or sense, based on android 4.0.4 and all 4.1 roms except 1 ( http://forum.xda-developers.com/showthread.php?t=1784185 ), i cannot get data to work.
I do know how to manually input my apn because every rom i use except 1 jellybean rom, i have to manually provision data. the one jellybean rom from tripnraver just works. i flash the rom, reboot, and data works.
the newer sense based roms using android 4.0.4 that i really want to use, there is nothing i can do that will make data work. i have posted a thread on xda about a month ago and it didnt get much attention. few guys gave some ideas but most was stuff i already tried.
if someone could look at the jellybean rom and see how the apns are tied into it and maybe tell me how to incorporate the file into a sense rom i would just be so excited. thanks for reading
dan.kels.r said:
I am having a huge issue with getting data to work on my HTC One X international. Any rom i try, aosp or sense, as long as its based on android 4.0.3 can get data to work.
But any rom, aosp or sense, based on android 4.0.4 and all 4.1 roms except 1 ( http://forum.xda-developers.com/showthread.php?t=1784185 ), i cannot get data to work.
I do know how to manually input my apn because every rom i use except 1 jellybean rom, i have to manually provision data. the one jellybean rom from tripnraver just works. i flash the rom, reboot, and data works.
the newer sense based roms using android 4.0.4 that i really want to use, there is nothing i can do that will make data work. i have posted a thread on xda about a month ago and it didnt get much attention. few guys gave some ideas but most was stuff i already tried.
if someone could look at the jellybean rom and see how the apns are tied into it and maybe tell me how to incorporate the file into a sense rom i would just be so excited. thanks for reading
Click to expand...
Click to collapse
Are you sure that your antennas are working fine? Might be a hardware defect.
First you'd probably want to relock the bootloader and run the RUU to eliminate software issues.
thanks for replying i appreciate the help. i know its not hardware cuz of all the roms based on android 4.0.3 that do work and the one 4.1 rom that works. as far as the ruu. im on softbank in okinawa japan. should i use one from asia or similar? and when you flash an ruu do you loose root?
edit: duh you loose root. my bad. relock the bootloader and run ruu. you think thats my best bet huh? im a custom rom junkie and this is really being a thorn in my side! lol.
Hunt3r.j2 said:
Are you sure that your antennas are working fine? Might be a hardware defect.
First you'd probably want to relock the bootloader and run the RUU to eliminate software issues.
Click to expand...
Click to collapse
You will lose root when you run an RUU, it is a way of completely wiping and reflashing the device to stock configuration to try and eliminate any possible changes that a custom ROM might have done to the phone's software that is otherwise inaccessible. Once you run an RUU, you can easily unlock again and then flash a custom recovery, then flash a ROM to test if data works.
I'm not sure about the specifics of Softbank, but as long as they use standard GSM/UMTS/HSPA+ protocols you should just need to put in the proper APN (Make sure it's also the right MNC and MCC, I believe those affect your ability to connect.)
do you think my issue has something to do with my CID? i was over reading throught the ruu thread and saw people having issue with certains roms or ruus and it was pertaining to cid. maybe 4.0.4 hasnt been officially released my my hox and just am stuck on 4.0.3 for now? im definitely shooting from the hip here
Hunt3r.j2 said:
You will lose root when you run an RUU, it is a way of completely wiping and reflashing the device to stock configuration to try and eliminate any possible changes that a custom ROM might have done to the phone's software that is otherwise inaccessible. Once you run an RUU, you can easily unlock again and then flash a custom recovery, then flash a ROM to test if data works.
I'm not sure about the specifics of Softbank, but as long as they use standard GSM/UMTS/HSPA+ protocols you should just need to put in the proper APN (Make sure it's also the right MNC and MCC, I believe those affect your ability to connect.)
Click to expand...
Click to collapse
Related
ok so i need some help i had the evo 4g and i just upgraded to the evo 3d the 4g was rooted and has a custom rom on it now i tried to change lines so my grandpa can use the evo instead of his crapberry now when i tried activating it they wanted me to enter ##45789 and when i press the last# it would freeze the phone keys and cant enter any numbers i need help please!
spitfire209 said:
ok so i need some help i had the evo 4g and i just upgraded to the evo 3d the 4g was rooted and has a custom rom on it now i tried to change lines so my grandpa can use the evo instead of his crapberry now when i tried activating it they wanted me to enter ##45789 and when i press the last# it would freeze the phone keys and cant enter any numbers i need help please!
Click to expand...
Click to collapse
Are you on a stock ROM. Custom roms can cause problems when trying to change numbers ect. So flash a stock rooted rom and see if the problem occurs again
Sent from my PC36100 using XDA App
so i tried to find one but still didn't work do u know of a good completely stock rom w root i think the correct problem im having is the epst codes correct me if im wrong
The codes, if I recall correctly, only work on Sense based ROMs. Custom ROMs CAN cause issues but for the most part they SHOULD work fine. If you are having problems on a sense based ROM then you can flash the latest stock rooted ROM and you should be good to go. If worse comes to worse you can RUU back to stock and then run the code. I am pretty sure that your grandfather isn't going to care if the phone is rooted or not.
Concordium said:
The codes, if I recall correctly, only work on Sense based ROMs. Custom ROMs CAN cause issues but for the most part they SHOULD work fine. If you are having problems on a sense based ROM then you can flash the latest stock rooted ROM and you should be good to go. If worse comes to worse you can RUU back to stock and then run the code. I am pretty sure that your grandfather isn't going to care if the phone is rooted or not.
Click to expand...
Click to collapse
thats all i been trying to put on i always use sense roms and when i tryed to find a almost stock sense rom it still didnt work where can i find the latest stock rooted ROM ill try it
Download the classic by tommytomatoe it has the downgraded epst.apk u need to use dialer codes or brads stock updated both are in the dev subforum or u can get Tommy's classic at classictomoatoe.net or .com forget which cuz I have it set as a speed dial page on opera mini
Edit: .net is the correct extension
We are legion, for we are many
Hi guys.
I flash the fullscreen mode with cmw recovery, and when the system was reebot it stop to a boot screen (white with HTC One written).
I tried to lock bootloader and installing RUU, but it say me who phone is not plug on the pc.
I tried to wipe cache/dalvik/etc etc but I'm not able to restart my phone.
Anyone can help me?
I just try to "fastboot erase cache" and "fastboot reboot-bootloader"...but nothing.
..you need to learn to make a backup in recovery first, when you dont have that much experience yet.
Which rom you was using? The stock or a custom one?
relocking bootloader and try flashing a RUU was completly overkill.
You just need the original android.policy, which was overwritten by flashing the mod you tried to get running.
I'm sure someone can provide a flashable zip for that...just ask in teh thread of the mod.
If you got your rom runnning again, esnure to make a backup in recovery. On that way you can always restore your working rom.
...and btw: brick = cant turn device on
j4n87 said:
..you need to learn to make a backup in recovery first, when you dont have that much experience yet.
Click to expand...
Click to collapse
I learn it yesterday evening, I don't forget to do it next time.
Now I'm trying to flash the RUU, before I didn't enter in fastboot.
Installing complete.........
anxiety....
...it work.
Yeah I had the same issue after installing the full screen patch too. Thankfully I'd done a Nandroid backup just after I rooted so I just did that. Would have installed a custom Rom otherwise
Sent from my Desire HD running Virtuous Affinity Sense 3.5
j4n87 said:
..you need to learn to make a backup in recovery first, when you dont have that much experience yet.
Which rom you was using? The stock or a custom one?
relocking bootloader and try flashing a RUU was completly overkill.
You just need the original android.policy, which was overwritten by flashing the mod you tried to get running.
I'm sure someone can provide a flashable zip for that...just ask in teh thread of the mod.
If you got your rom runnning again, esnure to make a backup in recovery. On that way you can always restore your working rom.
...and btw: brick = cant turn device on
Click to expand...
Click to collapse
Hi, I'm completely new to Android and just upgraded myself from my 3GS to the One X (and what an upgrade at that!). However I'm a bit dissatisfied with the Sense interface and would like to flash it with either vanilla or some cool unofficial rom.
The problem is I'm scared to death of bricking it. Especially since a friend of mine had told me the usual method of being sure you won't get a bricked phone is to simple change the rom on your SD-card. It would seem things get a little trickier when you don't have an SD though.
How does this backup in recovery work? Will it be making a backup of everything on my phone now and place it in backup? Will this ensure a corrupt rom image or whatever won't brick my phone?
From what I understand a launch from recovery is completely separate from the rest of the system, so unless you've broken the memory card (in which case I guess your screwed anyway) it shouldn't be possible to brick the phone should it?
kaminix said:
Hi, I'm completely new to Android and just upgraded myself from my 3GS to the One X (and what an upgrade at that!). However I'm a bit dissatisfied with the Sense interface and would like to flash it with either vanilla or some cool unofficial rom.
The problem is I'm scared to death of bricking it. Especially since a friend of mine had told me the usual method of being sure you won't get a bricked phone is to simple change the rom on your SD-card. It would seem things get a little trickier when you don't have an SD though.
How does this backup in recovery work? Will it be making a backup of everything on my phone now and place it in backup? Will this ensure a corrupt rom image or whatever won't brick my phone?
From what I understand a launch from recovery is completely separate from the rest of the system, so unless you've broken the memory card (in which case I guess your screwed anyway) it shouldn't be possible to brick the phone should it?
Click to expand...
Click to collapse
what you are looking to flash would be called "aosp"...android open source project, this means pure, unadulterated android from Google. At present time there are no aosp roms for the hox. They all have the HTC sense interface. Be patient. I'm sure this device will get a lot of attention from the dev community and we will have plenty of aosp roms to choose from in the near future.
Sent from my Xoom using xda premium
nooomoto said:
what you are looking to flash would be called "aosp"...android open source project, this means pure, unadulterated android from Google. At present time there are no aosp roms for the hox. They all have the HTC sense interface. Be patient. I'm sure this device will get a lot of attention from the dev community and we will have plenty of aosp roms to choose from in the near future.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Ah, yes. This is indeed what I'm looking for. Thanks, guess I'll just wait a little longer then.
my too sgs2 hard bricked becuase one for wrong bootloader and other for synah rc 3.6 kernal, so i bought one x and now lets see......will this work or not?
You have to make sure your RUU is for the same network and country and is newer then your current RUU or the CID will block it
Hello
I have an international version of the HTC one m8, specifically the ones in Asia. Before rooting and/or applying a custom rom, I used to have 4G capabilities but now the phone just refuses to connect to the 4G network. My 3G works fine with normal speeds as per before, I have applied a custon rom and a kernel and I am s-off so I couldn't have tempered with the radio. Please help as this is affecting me and wasting the capabilities of such an amazing phone.
thanks in advance
wasdapple said:
I am s-off so I couldn't have tempered with the radio.
Click to expand...
Click to collapse
I think you mean you are s-on. If you were s-off, that would mean you can tamper with the radio partition.
In any case, flashing a ROM or kernel won't "typically" affect LTE. But certain ROMs don't play well with some networks as reported by some folks (Euro ROMs + US AT&T network is the one example I can think of).
But before we get needlessly complex, did you check your APN?
redpoint73 said:
I think you mean you are s-on. If you were s-off, that would mean you can tamper with the radio partition.
In any case, flashing a ROM or kernel won't "typically" affect LTE. But certain ROMs don't play well with some networks as reported by some folks (Euro ROMs + US AT&T network is the one example I can think of).
But before we get needlessly complex, did you check your APN?
Click to expand...
Click to collapse
oops sorry yes I meant s-on. I have checked my apn, matched it with online the website of my carrier. I am currently in Singapore and I am running ARHD for my phone now. The rom was flashed was the international version that I got from the xda thread. Other than the 4G problem, the phone works fine and as mentioned my 3G still works fine.
wasdapple said:
oops sorry yes I meant s-on. I have checked my apn, matched it with online the website of my carrier. I am currently in Singapore and I am running ARHD for my phone now. The rom was flashed was the international version that I got from the xda thread. Other than the 4G problem, the phone works fine and as mentioned my 3G still works fine.
Click to expand...
Click to collapse
You might flash another ROM to see if it has any effect on LTE. I'm also guessing that returning to the stock ROM for your version will also get LTE back.
redpoint73 said:
You might flash another ROM to see if it has any effect on LTE. I'm also guessing that returning to the stock ROM for your version will also get LTE back.
Click to expand...
Click to collapse
Is there no way for me to keep my current rom and perhaps edit or flash some form of file. If I were to switch a rom it would really be a pain to transfer all of my data too, would you recommend any apps or procedures. Im currently using titanium backup only. Thanks for the help too.
wasdapple said:
Is there no way for me to keep my current rom and perhaps edit or flash some form of file.
Click to expand...
Click to collapse
I don't actually now exactly what is causing you to have lost LTE, so therefore its impossible to know specifically what to edit or change.
wasdapple said:
If I were to switch a rom it would really be a pain to transfer all of my data too, would you recommend any apps or procedures. Im currently using titanium backup only. .
Click to expand...
Click to collapse
Couple thoughts/suggestions:
1) If you flash a ROM of the same "base" (i.e. Lollipop Sense) you might be able to get away with a "dirty flash" meaning you keep user data, and just wipe cache and Dalvik before you flash. But if you run into some random issues, you may need to wipe user data.
2) You can make a nandroid in TWRP of your current setup. Than if you try a new ROM and it doesn't help the LTE issue, you can just restore the nandroid and revert to where you are now, with all the same user data.
3) To migrate data between ROMs, I just use Titanium Backup myself (with the Pro key to enable batch functions). Everyone's setup is different. But for me, I keep my contacts and email on Gmail. Than I just backup my apps, app data, and text messages on Titanium. So when moving to a new ROM (after wiping user data) I batch restore apps with Titanium, and just manually setup the home screens and Settings. Takes me maybe 20-30 minutes tops. May take folks longer if they have a lot of customized settings (lots of WiFi networks, Bluetooth devices, etc.) but I think even some of those things can be backed up by various methods, as well.
Wiping user data is basically just a necessary evil if you want to flash ROMs with any degree of frequency, IMO. Its nice when you can dirty flash, but I never outright count on it.
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