Related
As of right now, the roms for your S3 are not meant to be used on other S3 variants. Bricks might happens or a soft one might happen. Before flashing a Rom make sure you are in the right development section an you read the entire op, twice. Until other devs or experienced users find a way to make them cross compatible, please refrain from using other carriers S3 roms.
Also wind mobile an Tmobile are interchangeable, just don't flash the modems.
ONLY FLASH THE ROMS IN THIS FORUM!
Mr.Highway said:
As of right now, the roms for your S3 are not meant to be used on other S3 variants. Bricks might happens or a soft one might happen. Before flashing a Rom make sure you are in the right development section an you read the entire op, twice. Until other devs or experienced users find a way to make them cross compatible, please refrain from using other carriers S3 roms.
Click to expand...
Click to collapse
I second this, guys PLEASE don't risk it. It is not worth it. Right now I think most devs are working on their own ROMs, but we should have a patch soon to allow cross-compatibility.
think some peeps are confused by whats before tmo development. (AT&T, T-Mobile, Sprint, Verizon Samsung Galaxy S III) just my opinion but good idea on thread.
Mr Highway:
Could you start another thread for Windmobile Android Development?
In the past all Windmobile phones are just T-mobile phone rebadge.
In this case, it does not in terms of kernels....(and may be baseband)
I am working on this so that all roms will work on all carriers
http://forum.xda-developers.com/showthread.php?t=1735482
Mr.Highway said:
As of right now, the roms for your S3 are not meant to be used on other S3 variants. Bricks might happens or a soft one might happen. Before flashing a Rom make sure you are in the right development section an you read the entire op, twice. Until other devs or experienced users find a way to make them cross compatible, please refrain from using other carriers S3 roms.
Click to expand...
Click to collapse
AMEN!! Some fool I know ALREADY called me with a bricked gs3! I'm gonna sit back and let the pros do their thing, and that's DEFINITELY the safest bet!
thanks for the reminder and jsut to make sure ....
i have rogers sgh-i747
i want to be in this AT&T, T-Mobile, Sprint, Verizon Samsung Galaxy S III - xda-developers thread for everything correct ?
and not in the Samsung Galaxy S III I9300 thread ?
I keep seeing posts about ROMs that can work on these variants of galaxy S3s. Now correct me if I'm wrong, but aren't the ROMs supposed to be specific to GSM or CDMA? When I flashed windows based roms on my touch pro II, that was one of the things to look out for. Is it possible to create a ROM for all carriers?
Alik4041 said:
I keep seeing posts about ROMs that can work on these variants of galaxy S3s. Now correct me if I'm wrong, but aren't the ROMs supposed to be specific to GSM or CDMA? When I flashed windows based roms on my touch pro II, that was one of the things to look out for. Is it possible to create a ROM for all carriers?
Click to expand...
Click to collapse
Yes and no.
With the use of aroma-installer, we could set it up to detect your phone type (well, not we....I don't know that much about it but I saw the thread discussing this) and aroma would be able to install the necessary files based on your phone.
As of now, for instance, mine works across all GSM carriers. clark44 is current working to get everything switched up so it also works for Sprint (mostly appears to be the apk files and XML files) that are specific to the phone. As of now, he has it booting and working fine except there is a large rush of FCs on initial bootup but then everything runs fine.
I wasn't even aware you could make a patch to allow cross-compatibility! XDA never fails to surprise
Just a thought, but maybe they could do it like the SlimROM on multiple devices. He has a common base ROM and another flashable for each device supported. It works out perfectly and multiple ROMs for multiple carriers.
I figure it will be easier than doing it for different devices since I read that all the US variants are essentially the same. Not sure but worth a look.
link to the ROM: http://www.slimroms.com/
I use it for the Vibrant
Sent from my SGH-T959 using Tapatalk 2
Will there ever be any SGH-T999V development?
Does anyone think that someone with a SGH-T999V Wind Mobile variant will ever be able to root their phone so they can overclock the cpu, etc?
Why not? I am using a custom rom and overclocked to 1890 at the moment.
Just use the windows way to root. I knbow it works
I have not tried the toolkit.
If you are going to flash a custom rom just make sure it does not contain the boot, modem and amss file in the rom that you are flashing.
LXXIII said:
Does anyone think that someone with a SGH-T999V Wind Mobile variant will ever be able to root their phone so they can overclock the cpu, etc?
Click to expand...
Click to collapse
What about using i9300 themes and mods? Will this cause constant FCs or other issues?
LXXIII said:
Does anyone think that someone with a SGH-T999V Wind Mobile variant will ever be able to root their phone so they can overclock the cpu, etc?
Click to expand...
Click to collapse
I am curious of this too. I have the wind mobile galaxy s 3 and I was hoping to put cyanogenmod on it. Is this possible? Let me know, any help would be appreciated.
Sent from my SGH-T999V using Tapatalk 2
I'm more curious as to what exactly the differences are between the 2 variants (i.e. t999 vs t999v). What could possibly make them so different from each other that ROMs from tmobile wouldn't work on wind GS3?
What if you accidentally tried to flash i9300 rom and your phone is not turning on.
With the forums changed I accidentally flashed the wrong version rom on my phone. :crying:
TheLegace said:
What if you accidentally tried to flash i9300 rom and your phone is not turning on.
With the forums changed I accidentally flashed the wrong version rom on my phone. :crying:
Click to expand...
Click to collapse
Try to use odin to go back to stock, that's what I'm thinking, but I don't own the S3
Mr.Highway said:
Try to use odin to go back to stock, that's what I'm thinking, but I don't own the S3
Click to expand...
Click to collapse
correct and theres a thread about just that mistake.
http://forum.xda-developers.com/showthread.php?t=1727401
darren.wlsn1 said:
correct and theres a thread about just that mistake.
http://forum.xda-developers.com/showthread.php?t=1727401
Click to expand...
Click to collapse
Thanks for the link, unfortunately the phone will not go into download mode for odin, it won't even turn on.
After doing some research it looks like I have to fix it through jtag.
I think I could do it, but you need some expensive jtag box that connects to the computer(It's called the Riff Box), but it would be cheaper if I just sent my phone into here it costs $60. Not ideal, but not a complete disaster either. Unless there is some other way to JTAG I am out of options.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
Thanks.
All you pesky non American's I need some info from you.
Device (i.e tellus/rogers/korean S)
ro.lge.swversion=
Does current freegee boot.img work fine for you?
If the answer to #3 is no, please upload a boot.img for me.
For you e975 folks, support is coming, I'm reworking the entire backed to make future new device and version easier. Right now though I just need this info.
Thanks in advance.
Device: F180L
swversion: F180L20L
FreeGee does not work. Device is successfully rooted. Attempted using latest version from Play Store. Please post terminal command to extract boot.img
EDIT:
https://www.dropbox.com/s/rlkhkdi97ar6h9i/F180L20Lboot_img.zip
Sent from my LG-F180L using xda app-developers app
Sent from my LG-F180L using xda app-developers app
Works only on stock ROM right? Like the info that you want? Because I'm running SnowJB right now, which is an AT&T ROM.
Shellnutt said FG doesnt support korean 4.1.2 boot yet.
Also he said he can provide a steps (if really needed) and promised the support will be added in a week.
That was almost 1.5 month ago
Tim4 said:
Shellnutt said FG doesnt support korean 4.1.2 boot yet.
Also he said he can provide a steps (if really needed) and promised the support will be added in a week.
That was almost 1.5 month ago
Click to expand...
Click to collapse
How do you think we got the Korean firmware ported then?
LG Optimus G E971/3/5
1. F180K (Korean K)
2. F180K20g
3. No (ttp://dvl.kr/lg/Optimus%20G/F180K20G.zip)
chevro1et said:
Device: F180L
swversion: F180L20L
FreeGee does not work. Device is successfully rooted. Attempted using latest version from Play Store. Please post terminal command to extract boot.img
EDIT:
https://www.dropbox.com/s/rlkhkdi97ar6h9i/F180L20Lboot_img.zip
Sent from my LG-F180L using xda app-developers app
Click to expand...
Click to collapse
1: F180K
2: F180K20g
3: No
@chevro1et : how to extract the boot.img?
Thanks.
How do you think we got the Korean firmware ported then?
Click to expand...
Click to collapse
How is rom porting related to korean JB support in the freegee?
Ah, probably found the reason of misunderstood: I bought the freegee app (donate), the app still doesnt support korean JB at the moment.
I was talking about the app
benseoul said:
@chevro1et : how to extract the boot.img?
Thanks.
Click to expand...
Click to collapse
PM sent.
1: F180K
2: F180K20g
3: No.
boot.img: http://www.mediafire.com/?x2te7ydyszu5k4w
Thanks Shelnutt2 and chevro1et ^^
Okay please read this carefully.
Freegee has gone under a near complete rewrite in order to make it easier to add support for new varients and software versions. It's now a very simply process for me and doesn't involve updating the app anymore. This also will allow me to add newer and better recovories.
That said this is a highly beta version. Lot of debugging code is still in there, I just need more people to test it. I've used it fine, but someone else soft bricked. I've tried to get people on irc to test so I can help in real time but alas I didn't get many offers at all. So I'm posting this here. Please though don't use this unless you know how to kdz/lgnpst back to stock. This might blow up your phone, until I get people to actually test it more than myself and skdubg did I can't know.
http://downloads.codefi.re/shelnutt2/optimusg/freegee/FreeGee-beta.apk
EU and Korean kt_kr (180k) support is added! Candians are left out cause no one would give me your lgswverion build props
edit: Also is F180L20L lgu_kr or skt_kr? I'm guessing lgu, but just want to verify.
Shelnutt2 said:
Okay please read this carefully.
Freegee has gone under a near complete rewrite in order to make it easier to add support for new varients and software versions. It's now a very simply process for me and doesn't involve updating the app anymore. This also will allow me to add newer and better recovories.
That said this is a highly beta version. Lot of debugging code is still in there, I just need more people to test it. I've used it fine, but someone else soft bricked. I've tried to get people on irc to test so I can help in real time but alas I didn't get many offers at all. So I'm posting this here. Please though don't use this unless you know how to kdz/lgnpst back to stock. This might blow up your phone, until I get people to actually test it more than myself and skdubg did I can't know.
http://downloads.codefi.re/shelnutt2/optimusg/freegee/FreeGee-beta.apk
EU and Korean kt_kr (180k) support is added! Candians are left out cause no one would give me your lgswverion build props
edit: Also is F180L20L lgu_kr or skt_kr? I'm guessing lgu, but just want to verify.
Click to expand...
Click to collapse
F180L=LGU+
F180S=SKT
F180K=KT Olleh
Edit: after unlock and reboot device the phone stay on LG Logo... I can not go into the recovery, F180K.
Thank you again!
benseoul said:
F180L=LGU+
F180S=SKT
F180K=KT Olleh
Edit: after unlock and reboot device the phone stay on LG Logo... I can not go into the recovery, F180K.
Thank you again!
Click to expand...
Click to collapse
Thank you for specifying, 180L now has initial support for version F180L20L.
As far as not being able to unlock, I'd like to get a few more people to test it to make sure you aren't one of the special ones that need the sbl stack in addtion to new bootloader. That is what skdubg for his eu E975 needed.
Ok I'll wait for the next version.
if you need I will test again with the new version
Shelnutt2 said:
Okay please read this carefully.
Freegee has gone under a near complete rewrite in order to make it easier to add support for new varients and software versions. It's now a very simply process for me and doesn't involve updating the app anymore. This also will allow me to add newer and better recovories.
That said this is a highly beta version. Lot of debugging code is still in there, I just need more people to test it. I've used it fine, but someone else soft bricked. I've tried to get people on irc to test so I can help in real time but alas I didn't get many offers at all. So I'm posting this here. Please though don't use this unless you know how to kdz/lgnpst back to stock. This might blow up your phone, until I get people to actually test it more than myself and skdubg did I can't know.
http://downloads.codefi.re/shelnutt2/optimusg/freegee/FreeGee-beta.apk
EU and Korean kt_kr (180k) support is added! Candians are left out cause no one would give me your lgswverion build props
edit: Also is F180L20L lgu_kr or skt_kr? I'm guessing lgu, but just want to verify.
Click to expand...
Click to collapse
How can I give you what you need when you didn't answer my question?
geokilla said:
Works only on stock ROM right? Like the info that you want? Because I'm running SnowJB right now, which is an AT&T ROM.
Click to expand...
Click to collapse
geokilla said:
How can I give you what you need when you didn't answer my question?
Click to expand...
Click to collapse
I got a question for you, why would you want to use freegee if you already have bootloader unlocked ? Plus he clearly say non american in the OP, from what I know, AT&T is american. So, to answer clearly your question, NO, he doesnt need your info.
chadouming said:
I got a question for you, why would you want to use freegee if you already have bootloader unlocked ? Plus he clearly say non american in the OP, from what I know, AT&T is american. So, to answer clearly your question, NO, he doesnt need your info.
Click to expand...
Click to collapse
I can always flash back to Canadian ROM for an hour just for him? I still have stock Rogers ICS in my computer.
geokilla said:
I can always flash back to Canadian ROM for an hour just for him? I still have stock Rogers ICS in my computer.
Click to expand...
Click to collapse
ICS firmware is already unlocked, this thread was created to unlock the JB firmware...
benseoul said:
ICS firmware is already unlocked, this thread was created to unlock the JB firmware...
Click to expand...
Click to collapse
I believe shelnutt also need info for our Canadian ICS since we don't have jb.
Sent from my Galaxy Nexus using xda premium
Hello all,
I did a search and was not able to find what I'm looking for. All I need/want is stock AT&T JB 4.1.2 with tethering (Carrier unlock would be nice too).
Is there one available? If yes, would someone point it out to me. If not, what is the closest I can come to this? I just do not want any bloatware or an unstable OS.
Thank you in advance,
-NJ
njdevils28 said:
Hello all,
I did a search and was not able to find what I'm looking for. All I need/want is stock AT&T JB 4.1.2 with tethering (Carrier unlock would be nice too).
Is there one available? If yes, would someone point it out to me. If not, what is the closest I can come to this? I just do not want any bloatware or an unstable OS.
Thank you in advance,
-NJ
Click to expand...
Click to collapse
Well first off we don't have a "stock" AT&T JB 4.1.2 because they have not released it. You would not be able to get "Carrier unlock unlock," unless you mean that you want to change the carrier name not actually unlock your phone to be used on another network. But if you want to actually unlock your device to be used for another carrier you need to get the sim unlock way. You can find that information in this forum.
And the closest thing that you can have bloat removed and tethering is to Go Into the Forum that says Android Developemnt (not Original Development.) to find ROM's that can be installed. Be sure to read the Original Post (OP) found on the first page of the thread, make sure you are rooted and to follow all directions there...you can also find the description of the ROM contents in the Change Log..
Hope this answers your question.
Best wishes.
I'm pretty sure 4.1.1 stock work with tethering really well and there is no 4.1.2 release yet, I can't believe how slow carrier/Samsung can be Lol...
Sent from my SGH-I747 using Tapatalk 2
See post 96 of this thread http://forum.xda-developers.com/show...732262&page=10
step 1: root via this process http://forum.xda-developers.com/showthread.php?t=1963790&highlight=chainfire
step 2: use either of the methods in tbis post to enable tethering: http://forum.xda-developers.com/showpost.php?p=41202184&postcount=28
Note 4 owners over in the Verizon section are putting together a fair effort to investigate rooting themselves. We AT&T users should have a similar thread.
The Verizon thread, for reference:
http://forum.xda-developers.com/note-4-verizon/general/talk-root-t2908919
T-Mobile and Sprint have CF-Autoroot but not yet for AT&T and Verizon. So (I think) a new root should work for either, all the more reason to work together.
In the Verizon thread the general process was posted:
Surge1223 said:
I have no vested interest in this (other than seeing vzw get screwed over) but someone needs to get the ball rolling here:
1. Grab the Odin tar then boot.img to get kallsyms
2. Post partition info
3. Grab kernel source and confirm latest Linux kernel cves are patched/not patched
4. Find PoC for Linux exploits for 2014 Linux kernel cves and port them to android and test
If you have to ask what any of the above are/do Google is your friend.
Click to expand...
Click to collapse
Feel free to read through the other thread for info on CVEs and stuff.
The Verizon owners have to wait for kernel source but I guess our's is already posted (N910A):
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=Sm-n910
SHA1 and SHA256 for the kernel source zip that I downloaded, for reference:
99e00529ce613548664f3c986cd7df886b54caa0 SM-N910A_NA_KK_Opensource.zip
9a5dfcbcd1b77367507b9374afd4f1e1afd505255ff48b4d3779b235974650c0 SM-N910A_NA_KK_Opensource.zip
This might not be necessary as someone like Chainfire may already be working on a rooting method, but we might make it slightly easier.
Any contributions by more knowledgeable people are greatly appreciated.
Anyone want to post their kallsyms, boot, or full image of an AT&T phone?
I'll try to post myself if I can figure out of I'm supposed to use Odin or if the way the Verizon owners got their's was with some Verizon-only tool.
We have firmware here:
http://forum.xda-developers.com/note-4-att/general/stock-to-stock-odin-flashable-tested-t2915915
The kernel source is here:
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=Sm-n910a
That should get us started.
Tikerz said:
We have firmware here:
http://forum.xda-developers.com/note-4-att/general/stock-to-stock-odin-flashable-tested-t2915915
The kernel source is here:
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=Sm-n910a
That should get us started.
Click to expand...
Click to collapse
Nice! Yeah the kallsyms should definitely be in there.
Here are the kallsyms from the ATT image.
I've been googling but I can't figure it out
How do you get partition info from kallysyms?
v3ngence said:
I've been googling but I can't figure it out
How do you get partition info from kallysyms?
Click to expand...
Click to collapse
You don't. The kallsyms are information about the internal kernel functions, useful for writing code which gets you root access.
Partition information sits in a .PIT file inside the factory image (if it's available), or you can dump it from a running phone.
SirAthos said:
Here are the kallsyms from the ATT image.
They match the Verizon kallsyms. Good sign for finding a root method that works on both. :good:
Click to expand...
Click to collapse
They shouldn't match the Verizon n4 kallsyms... They should be different, if not then someone odd is happening..
Surge1223 said:
They shouldn't match the Verizon n4 kallsyms... They should be different, if not then someone odd is happening..
Click to expand...
Click to collapse
I'll extract them again, maybe I missed something...
Edit: Gah, still had kernel.Image extacted from the Verizon image, and didn't notice the message saying "kernel.Image: already exists; not overwritten". The attachment above has been updated. My apologies, and thanks for catching it.
This may be interesting though. The nexus devices have a check box in the developer settings to OEM unlock the phone. Basically you just check a box and it's boot loader is unlocked.
http://www.androidpolice.com/2014/1...-6-9-requires-checking-box-developer-options/
Maybe this can be used to find a loop hole on lollipop for this device. I think there could b be a small chance this device could get unlocked after the update. It might actually be easier.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
ShrekOpher said:
This may be interesting though. The nexus devices have a check box in the developer settings to OEM unlock the phone. Basically you just check a box and it's boot loader is unlocked.
http://www.androidpolice.com/2014/1...-6-9-requires-checking-box-developer-options/
Maybe this can be used to find a loop hole on lollipop for this device. I think there could b be a small chance this device could get unlocked after the update. It might actually be easier.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
Click to expand...
Click to collapse
While I appreciate the speculation, that's all this is, and at the moment we don't have Lollipop. I believe the OP specified good steps that should be looked into. I have downloaded the source code but am not exactly sure how to be looking for other then doing the steps as outlined: Finding the build date of the kernel then looking up know vulnerabilities in it. Obviously this is going to take a while and makes sense on where to look. Why focus on something we don't have when we could focus on what we do.
tl;dr We need to stay focused on the current task at hand. Also it'd be nice if this thread didn't get derailed with speculations.
ShrekOpher said:
This may be interesting though. The nexus devices have a check box in the developer settings to OEM unlock the phone. Basically you just check a box and it's boot loader is unlocked.
http://www.androidpolice.com/2014/1...-6-9-requires-checking-box-developer-options/
Maybe this can be used to find a loop hole on lollipop for this device. I think there could b be a small chance this device could get unlocked after the update. It might actually be easier.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
Click to expand...
Click to collapse
Didn't you get rid of your AT&T Note 4 for T-Mobile Note 4?
Tikerz said:
Didn't you get rid of your AT&T Note 4 for T-Mobile Note 4?
Click to expand...
Click to collapse
I write custom enterprise software for phones. I own many including 2 different Note 4s. Most provided to me by my company. So no I still have the AT&T Note 4, I also have a T-Mobile variant for the time being. My team also has a sprint model as well.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
Srsroot
Has anyone heard if this actually works? I've been searching forums and the Internet in general looking for a possible root for the AT&T note 4
#SRSRoot: samsung SAMSUNG-SM-N910A (Build: KTU84P.N910AUCU1ANIE) #Android 4.4.4 Now Supported for #Root at SRSRoot.com (copied this from their twitter)
Drewsdad said:
Has anyone heard if this actually works? I've been searching forums and the Internet in general looking for a possible root for the AT&T note 4
#SRSRoot: samsung SAMSUNG-SM-N910A (Build: KTU84P.N910AUCU1ANIE) #Android 4.4.4 Now Supported for #Root at SRSRoot.com (copied this from their twitter)
Click to expand...
Click to collapse
wonder if we can get a dev to dl and take a look???
i looked through there list and i dont see our phone listed
Drewsdad said:
Has anyone heard if this actually works? I've been searching forums and the Internet in general looking for a possible root for the AT&T note 4
#SRSRoot: samsung SAMSUNG-SM-N910A (Build: KTU84P.N910AUCU1ANIE) #Android 4.4.4 Now Supported for #Root at SRSRoot.com (copied this from their twitter)
Click to expand...
Click to collapse
Just verified the tweet from October 26. I'm not sure, maybe this will be a pleasant surprise?
Mmm looking at the supported devices in their page I found the 910v and 910t... But no 910a
Monsi said:
Mmm looking at the supported devices in their page I found the 910v and 910t... But no 910a
Click to expand...
Click to collapse
I don't see it either. Their tweet says our phone specifically has been added. Not sure of the supported devices hasn't been updated or what. I'm kinda sketchy about trying stuff that I haven't seen discussed on here. Does anyone know if the stock firmware is available yet.? At least that way if someone ends up with a brick we can at least Flash it back to normal
Monsi said:
Mmm looking at the supported devices in their page I found the 910v and 910t... But no 910a
Click to expand...
Click to collapse
Pretty sure the Verizon crowd already dismissed this method. Likely a hoax.
Tried to find something in their forum but nothing... Something tell me that this is fake
Tried it and didn't get root.
Hey guys, here is the long awaited LTE fix for perry and owens users.
Please do a clean install of your custom rom of choice before immediately flashing this before the first boot for best results. (I prefer to use squid2's lineage build)
If you don't do this, you may have to reset your apns to default in settings. Preferred network mode should be set to Global.
Steps for installation:
Download the apns-conf for your carrier and blobs.zip (apns-conf.sprint.zip for Sprint, apns-conf.boost.zip for Boost, and apns-conf.stock.00modified.zip for everything else)
Stick them on your phone's SD card
Flash the two zip files you downloaded
apns-conf.stock.00modified.zip Download
apns-conf.sprint.zip Download
apns-conf.boost.zip Download
blobs.zip Download
EDIT: Apparently the apn's are only working in the condensed versions for Sprint/Boost, so I've uploaded apns-conf for both of those.
EDIT2: Yea, it actually looks like they are working, you just have to be sure to flash stock firmware for your device prior to clean installing rom and the fix. Otherwise no guarantees any of it will work.
So you think it will work with virgin mobile too? Just flash rom and your 2 zips?
madbat99 said:
So you think it will work with virgin mobile too? Just flash rom and your 2 zips?
Click to expand...
Click to collapse
Possibly. It's not confirmed, and kinda hard to tell since your telephony.db didn't have any obvious missing internet apn's, but this has the sprint internet apn added to it and the 310 00 modifications, so it has the best chance of working of anything that has been released. Especially since I fixed the blobs.. and yes, you just flash the rom and 2 zips.
Now is there a way to incorporate this fix automatically in ROMs, be it via cherry-picking a commit or including the zip file to auto flash during a rom installation?
fireball0093 said:
Now is there a way to incorporate this fix automatically in ROMs, be it via cherry-picking a commit or including the zip file to auto flash during a rom installation?
Click to expand...
Click to collapse
This is the fix for the blobs in the vendor files:
https://github.com/MotoOwensDevel/p...mmit/e8c74378e816d9940d34544f85c08dc45145a694
As for the APNs, I have a release tools script for the owens device tree that installs my modified stock APNs
https://github.com/MotoOwensDevel/android_device_motorola_owens/blob/cm-14.1/releasetools.py
You'll have to kinda look at https://github.com/MotoOwensDevel/android_device_motorola_owens to see how it works completely, but this is already incorporated in my lineage build for the Moto E4 Plus.
EDIT: I'm going to have to change the release tools script a bit more, because apparently the apns only like to work in the condensed forms for Sprint/Boost.
EDIT2: I've implemented the fix in the owens device tree.
EDIT3: Reverted the fix, looks like the reports of it not working are wrong. I just got confirmation that installing completely stock firmware and then installing the rom and the 00modified stock apns and blobs should work on Sprint/Boost just fine. They don't need to be separated out.
So after a few days of going step by step from the instructions and trying every thing else I could think of nothing works to get working lte... Even the 1x and 3g were spotty I'm on Virgin Mobile and if any one needs any files to help get the lte working let me know .....I know that after flashing the blobs and other files it says on lte but refuses to connect
After flashing both zips I get 1 X and all my APN settings are erased when I flash just the blobs I can get a solid 3-g and I have all my APN settings but still can't get LTE no matter what I put
Well i finally managed to get lte but working on trying to get mms
neojpl said:
After flashing both zips I get 1 X and all my APN settings are erased when I flash just the blobs I can get a solid 3-g and I have all my APN settings but still can't get LTE no matter what I put
Well i finally managed to get lte but working on trying to get mms
Click to expand...
Click to collapse
How did you get lte to work?
frederickrl said:
How did you get lte to work?
Click to expand...
Click to collapse
So far I've been able to get LTE and MMS working on only the Android ice cold project ROM. I flashed the Boost APN zip and the blob zip. Then I created a boost APN setting. I got these settings from a couple of guys on XDA who helped me out. Just follow the screenshots. hope this helps
Hi @SeanStar, I just wanted to touch base with you to let you know, despite my persistence, Motorola Mobility has declined to grant me access to carrier specific manifests on the perry xt1766, citing that "disclosure of such documentation would potentially violate contractual clauses regarding internal security protocols...between Lenovo, Motorola Mobility, and mvno subsidiaries of Sprint..." So on and so forth, etcetera, etcetera. Ironically I had another request denied last week for access to blankflash files for certain Motorola devices, which could be used to unbrick devices using Qualcomm's emergency recovery mode. The company is getting super tight on such info. They had no problem releasing the same manifests back in 2016 for the xr1526 surnia Moto E LTE. Interestingly, both of my recent requests were denied directly by Motorola Mobility's Office of General Counsel. The lawdogs themselves told me no.
neojpl said:
So far I've been able to get LTE and MMS working on only the Android ice cold project ROM. I flashed the Boost APN zip and the blob zip. Then I created a boost APN setting. I got these settings from a couple of guys on XDA who helped me out. Just follow the screenshots. hope this helps
Click to expand...
Click to collapse
I LOVE YOU!!! THANK YOU SO MUCH! I didn't attempt to this I installed this ROM and it's amazing, everything I may want from a custom rom is here, and the settings worked BEUTIFULLY, I can't tell you how much I appreciate this!
frederickrl said:
I LOVE YOU!!! THANK YOU SO MUCH! I didn't attempt to this I installed this ROM and it's amazing, everything I may want from a custom rom is here, and the settings worked BEUTIFULLY, I can't tell you how much I appreciate this!
Click to expand...
Click to collapse
No problem bro! everything I've learned and continue to learn has been on this site, so if I can help anybody here, with my limited knowledge base, awesome! you're very welcome ?
neojpl said:
So far I've been able to get LTE and MMS working on only the Android ice cold project ROM. I flashed the Boost APN zip and the blob zip. Then I created a boost APN setting. I got these settings from a couple of guys on XDA who helped me out. Just follow the screenshots. hope this helps
Click to expand...
Click to collapse
worked absolutely great.
Thexmastermind said:
worked absolutely great.
Click to expand...
Click to collapse
Cool! I'm happy to help
I found a link to a VM apn fix,
https://forum.xda-developers.com/devdb/project/?id=21002#downloads
Idk if this helps I'm about to try it
bakerd62 said:
I found a link to a VM apn fix,
https://forum.xda-developers.com/devdb/project/?id=21002#downloads
Idk if this helps I'm about to try it
Click to expand...
Click to collapse
I don't know where that came from. But it doesn't have blobs in it. What thread did that link come from?
I have the right one for virgin mobile if you want it. Lte, MMS, all of it works.
Honestly I searched VM APK fix for Android 7.0, and that was the top link to the XDA search tab
---------- Post added at 03:20 AM ---------- Previous post was at 03:18 AM ----------
But that would be great if you could give me the fix
bakerd62 said:
Honestly I searched VM APK fix for Android 7.0, and that was the top link to the XDA search tab
---------- Post added at 03:20 AM ---------- Previous post was at 03:18 AM ----------
But that would be great if you could give me the fix
Click to expand...
Click to collapse
I have one for virgin mobile that worked for me on aokp and aicp. Haven't tested others. I did not make it. One of the members in the telegram group did. Not sure what his xda username is. I'll find out and give credit.
madbat99 said:
I have one for virgin mobile that worked for me on aokp and aicp. Haven't tested others. I did not make it. One of the members in the telegram group did. Not sure what his xda username is. I'll find out and give credit.
Click to expand...
Click to collapse
Pretty sure it was @PimpMy5Ton
I cannot for the life of me....find stock firmware for the Moto E 2015 LTE XT1526 model anywhere. Can some one point me to same? I am running official Lineage OS 14.1 nightlies and not having LTE is a reall deal breaker.