Related
Hey guys so this was brought to my attention by another user, @daftlush . Dating back to my OGEvo4g we were conditioned to believe Update PRL/Profile could not be done in AOSP, specifically on Sprint. This was somewhat debunked when the Nexus came out to Sprint because it had this feature in AOSP. @daftlush brought up in another thread asking about this and I assumed like before it just wasnt in AOSP, except Google has it working. So I wanted to compile a list of roms that are fully Sprint functional that include Update PRL/Profile.
First, I noticed on roms where it does work it will finish Activating Data you dont have to press skip. I dont know if it is just a coincidence but the one rom I found this feature actually working, I did not have to hit skip once i saw LTE instead it finished and moved onto the next step.
If you know of a rom where this does work, please list it and I will update the list. I am hoping we can track down the necessary code to get this fully working on all AOSP roms.
UPDATE: 01/11/14
I was able to get the fix from team slim it is located in the second post
UPDATE 01/09/14
Newest Slimkat build has the feature confirmed working. (http://forum.xda-developers.com/showpost.php?p=49278373&postcount=3240)
I have sent a PM to the OP of the AOSPA thread to see if they can work on getting this going as well. Still waiting to hear back from AOKP since the first conversation. Lets help spread this info so we can enjoy our hammerhead! If you can help find the code needed on gerrit please let me know I have been looking but I dont have much experience in reviewing code, if it is found I can update post #2 with the detail for all devs to utilize.
UPDATE 01/06/14
I have passed on this information to a few days and so far, AOKP, SLIM, CNA have stated they will look into the code from Vanir and Cyanogenmod to see what they did in order to get these options working. Slim says it is a current WIP for them and last I talked to someone from AOKP they said they would look into it and we should have it working. CNA also said they would look into it.
Unfortunately OMNI doesnt look to be working on it, I did not get this info from someone on team omni but many posts have stated they dont want to include any closed source items from stock, i didnt know sprint hidden menu and prl/profile updates were closed source but that is unfortunate as I know a lot of us Sprint users would love to run OMNI, but for me no prl/profile updates make it hard to run as a DD (fellow Sprint users probably understand as prl updates sometimes fix our data issue)
Full working on Sprint (Activate data works, Update PRL/Profile works):
Vanir
Cataclysm
Stock Google
Anything based off Stock Image
Cyanogenmod
CM Based Variants
Slimkat (fixed per dev http://forum.xda-developers.com/showpost.php?p=49226687&postcount=3155) / now confirmed working as of 1/9 (http://forum.xda-developers.com/showpost.php?p=49278373&postcount=3240)
BobcatRom - confirmed working (http://forum.xda-developers.com/showpost.php?p=49284722&postcount=18)
AOKP 1/12/14 (http://forum.xda-developers.com/showpost.php?p=49340913&postcount=306)
AOSPA - the fix has been merged but no build put out since then, this is as of 1/11/14 future builds after this date should work (http://forum.xda-developers.com/showpost.php?p=49343381&postcount=303) (http://forum.xda-developers.com/showpost.php?p=49346234&postcount=313 confirmed Update PRL/Profile works as well)
Custom Raskat by @soccerfan6768 (http://forum.xda-developers.com/showpost.php?p=49412543&postcount=2624) he said hell pass on the fix to the raskatdevs for officials
Purity
Sprint data works w/o APN hack, but no update PRL/Profile(once you see LTE icon you must hit skip on activating data):
OMNI
Codename Android
Sprint data works with APN hack only:
PSX
First and foremost I want to give a very big THANK YOU to @cordell12 for putting up with my constant nagging surrounding this subject and to @kufikugel from slimteam for figuring it out. I hope cordell12 doesnt mind me posting their fix.
Per cordell12 "yes, it is blobs. those who do not have it(prl/profile update) working are using blobs from google website. those who do(prl/profile update) are using extracted blobs from stock build/device"
here is a link to the slimteams gerrit with the fix that made it work on their rom: https://gerrit.slimroms.net/#/c/1714/
i was told by another member that this fix also needed to be implemented https://gerrit.slimroms.net/#/c/1717/
Help me spread the word to the devs of non-fully functional roms on sprint.
So i have updated the list again today, CM has it working as do a few others. I am not good with git or code, does anyone know what the commit is that fixes this so i can help spread the word to other devs?
whats the sprint hack?? im on sprint and i always wanted to try rastakat rom
P.Mobile said:
whats the sprint hack?? im on sprint and i always wanted to try rastakat rom
Click to expand...
Click to collapse
The sprint. Zip file that allows you to get past the welcome screen on some roms and have data connection enabled, i few roms will be unusable if you don't flash this after the rom and the gapps,i think
Sent from my Nexus 5 using Tapatalk
On the fully compatible ROMs are you also able to access the Sprint Hidden Dialer Menu(*#*#3282#*#*)? I really hope Sprint users can get full compatibility across all ROMs.
AndrasLOHF said:
On the fully compatible ROMs are you also able to access the Sprint Hidden Dialer Menu(*#*#3282#*#*)? I really hope Sprint users can get full compatibility across all ROMs.
Click to expand...
Click to collapse
The roms that are fully working, have the hidden menu. I just checked for you and it does work, this is only tested on those that PRL/Profile update work!
MY goal of this thread is to figure out what code is missing from the roms so we(sprint users) can enjoy all the goodies.
P.Mobile said:
whats the sprint hack?? im on sprint and i always wanted to try rastakat rom
Click to expand...
Click to collapse
The Sprint hack enables the correct APNs for Sprint so you can have data, otherwise you get no data which makes our phones useless
Just a heads up, Update PRL/Profile is FIXED on SlimKat and will be included in our next Official build :good:
cordell12 said:
Just a heads up, Update PRL/Profile is FIXED on SlimKat and will be included in our next Official build :good:
Click to expand...
Click to collapse
That's great, Thanks. I have a Sprint-purchased Nexus 5 and I haven't ran into any problems so far, which is amazing. I'm glad it's the same phone hardware-wise as the unlocked version.
nerv8765 said:
That's great, Thanks. I have a Sprint-purchased Nexus 5 and I haven't ran into any problems so far, which is amazing. I'm glad it's the same phone hardware-wise as the unlocked version.
Click to expand...
Click to collapse
I really hope this catches on, one device = all providers.
cordell12 said:
I really hope this catches on, one device = all providers.
Click to expand...
Click to collapse
I do too, it's so nice to know that I have the option of going with a prepaid service like T-Mobile or At&t. Basically, anything except Verizon will fully work (and I don't really miss Verizon any.)
thanks to this thread i found about Vanir and will never turn back to anything else!
Tons of great info here, thanks OP!
Thank you cordell for giving us an update!!
I have sent a message to the hammerhead maintainer of AOSPA to see if they will also implement this "fix"
Has anyone been able to see the code from either CM, Slim, or Vanir? I want to update post #2 with that info so the other devs can easily access them.
BobcatRom works flawlessly on sprint, and is an amazing ROM. I highly recommend people to check it out. Its beautiful.
sent from my Hammerhead Nexus
CRIME INC. said:
BobcatRom works flawlessly on sprint, and is an amazing ROM. I highly recommend people to check it out. Its beautiful.
sent from my Hammerhead Nexus
Click to expand...
Click to collapse
can you confirm Update PRL/Profile work?
Circaflex said:
can you confirm Update PRL/Profile work?
Click to expand...
Click to collapse
Yes I can:thumbup:
sent from my Hammerhead Nexus
CRIME INC. said:
Yes I can:thumbup:
sent from my Hammerhead Nexus
Click to expand...
Click to collapse
thanks added to the list
cordell12 said:
I really hope this catches on, one device = all providers.
Click to expand...
Click to collapse
@cordell12: is it at all possible for you to link me to the changes on gerrit that were made to get this feature working, i have receieved answers from a few other rom devs asking me for the code, i tried looking on slimsgerrit but i have no experience in reviewing code and i am not sure what i am looking for exactly. thank you for any help you can provide.
Hi all,
Today, I proudly present GomdoLight KitKat for KOREAN LG G / G2 / G3 / G3A / G3cat6 / Gflex / GK / Gpro / Gpro2 / LTE3 / Vu2 / Vu3 / Gpad7LTE, one of the most widely used (with 20,000+ users approximately) stock-based custom firmware in South Korea.
GomdoLight is more than 3 year old already (first version released on 19th December 2012), and is very mature.
Technically speaking GomdoLight is NOT a complete ROM, but rather a large-scale patch, which modifies official stock firmware to remove all the unnecessary components preloaded by operator/manufacturer, and reorganizes key system parts to 'basic' Android OS with manufacturer's flavor. For some devices GomdoLight's own specialized tool 'GomdoLight Sideloader' can make it possible to install GomdoLight directly over the stock firmware, even without rooting or flashing custom recovery!
GomdoLight is compatible with the following devices (BOLD indicates GomdoLight Sideloader support - no root required)
LG Optimus G: LG-F180S, LG-F180K, LG-F180L ("G")
LG G2: LG-F320S, LG-F320K, LG-F320L ("G2")
LG G3: LG-F400S, LG-F400K, LG-F400L ("G3")
LG G3A: LG-F410S ("G3A")
LG G3 Cat.6: LG-F460S, LG-F460K, LG-F460L ("G3")
LG G Flex: LG-F340S, LG-F340K, LG-F340L ("Gflex")
LG GK: LG-F220K ("GK")
LG G Pro: LG-F240S, LG-F240K, LG-F240L ("Gpro")
LG G Pro 2: LG-F350S, LG-F350K, LG-F350L ("Gpro2")
LG Gx: LG-F310L, LG-F310LR ("Gx")
LG Optimus LTE3: LG-F260S ("LTE3")
LG Optimus Vu2: LG-F200S, LG-F200K, LG-F200L ("Vu2")
LG Vu 3: LG-F300S, LG-F300K, LG-F300L ("Vu3")
LG G Pad 7.0 LTE: LG-V410 ("Gpad7LTE")
A very thorough and extensive (probably, the most extensive on entire xda) manual is provided at the download page, which contains literally everything you need to know to install GomdoLight. FAILURE TO READ THIS DOCUMENT BEFORE INSTALLING WILL ALWAYS LEAD TO VARIOUS UNEXPECTED PROBLEMS. PLEASE READ CAREFULLY. Needless to say, I WILL NOT ANSWER ANY QUESTIONS ALREADY ADDRESSED IN THIS DOCUMENT.
Due to xda forum's limits (in functionality) I am posting a link to the separate (external) DOWNLOAD PAGE. There is no way I can link to each section in the document in xda posts, since xda does not support HTML tag. However some portions of the document are also introduced here.
▶ GomdoLight Download / Manual Page
GomdoLight TUTORIALS:
Want to read the built-in user manual again?
Need help using GomdoLight Flag functions?
Installing an EasyMod package? (Sorry the tutorial is in Korean, but screenshots will help)
XDA:DevDB Information
GomdoLight KitKat, ROM for various LGE devices
Contributors
juniecho
ROM OS Version: 4.4.x KitKat
ROM Firmware Required: STOCK FIRMWARE (Firmware compatibility table available)
Based On: STOCK FIRMWARE
Version Information
Status: Stable
Current Stable Version: 4.0
Created 2015-02-26
Last Updated 2015-12-31
CHANGELOG for older versions
Version History:
2015. 12. 31. - Wave 4, initial release
UPDATE LEVEL: MAJOR / IMPORTANCE: VERY HIGH
CHANGELOG:
Oh god, have I abandoned this thread this long? So many changes, sorry, I can't list them all.
A lot of things are now even better than ever. Trust me.
[#GLKITKATCOMMONUPDATE]
EMERGENCY NOTICE, etc.
For some unknown reason I cannot access my DevDB variables at this time. Though G Flex is not on the list of supported devices right now, it IS supported.
* For those who have waited for a long time, sorry for being late, and thank you very much.
Will we see a port to d959 ever? If so and you need a tester pm me!
EDIT: For those wanting to try it did install, but very few bloat was actually removed and no gomdo apps were installed.
dmifsud44 said:
Will we see a port to d959 ever? If so and you need a tester pm me!
Click to expand...
Click to collapse
I'm not sure yet, but it may not be necessary. Because gomdolight is a large-scale patch mainly focusing on script-driven features, just three of system apks are overwritten:
- /system/framework/framework-res.apk
- /system/priv-app/LGSystemUI.apk
- /system/priv-app/LGCameraApp.apk
Camera should be compatible for all variants, and only the FRAMEWORK RESOURCE and the SYSTEM UI might have compatibility issue.
You can first take a Nandroid backup, and try installing GomdoLight all the way to the end over your stock firmware, and see if it boots (and operates without crashes)
For model selection just choose LG-F340K.
1) If it works well: CONGRATULATIONS! You have fully-working GomdoLight.
2) If it fails: Restore Nandroid, and reinstall GomdoLight. However this time choose the 4TH option for battery percentage indicator. (Do not change) This options leaves both framework-res and SystemUI unchanged, so it will work 100%.
juniecho said:
I'm not sure yet, but it may not be necessary. Because gomdolight is a large-scale patch mainly focusing on script-driven features, just three of system apks are overwritten:
- /system/framework/framework-res.apk
- /system/priv-app/LGSystemUI.apk
- /system/priv-app/LGCameraApp.apk
Camera should be compatible for all variants, and only the FRAMEWORK RESOURCE and the SYSTEM UI might have compatibility issue.
You can first take a Nandroid backup, and try installing GomdoLight all the way to the end over your stock firmware, and see if it boots (and operates without crashes)
For model selection just choose LG-F340K.
1) If it works well: CONGRATULATIONS! You have fully-working GomdoLight.
2) If it fails: Restore Nandroid, and reinstall GomdoLight. However this time choose the 4TH option for battery percentage indicator. (Do not change) This options leaves both framework-res and SystemUI unchanged, so it will work 100%.
Click to expand...
Click to collapse
Wheres the download?
podagee said:
Wheres the download?
Click to expand...
Click to collapse
in the download/manual page. section 10. (see the first post) be sure to read the installation guide.
I installed in my d-958, well, some force closes in the settings, app manager and gallery sometimes, but everything else, at least the main functions, works well
Maikeu Locatelli said:
I installed in my d-958, well, some force closes in the settings, app manager and gallery sometimes, but everything else, at least the main functions, works well
Click to expand...
Click to collapse
do they CONSISTENTLY force close by certain actions? or just randomly?
I'm downloading now and will test it for the D95920s firmware. T-Mobile D959 on the latest KitKat 4.4.2 D95920s. Will report back later. I need my phone till at least 4pm central time so I can reach my son but I'll flash after that.
This intrigues me. Sprint supported? I don't feel like dealing with force closes mentioned in previous post in different variant.
Sent from my LG-LS995 using Tapatalk
mattwheat said:
I'm downloading now and will test it for the D95920s firmware. T-Mobile D959 on the latest KitKat 4.4.2 D95920s. Will report back later. I need my phone till at least 4pm central time so I can reach my son but I'll flash after that.
Click to expand...
Click to collapse
good luck. if it crashes revert to stock via nandroid backup and reinstall gomdolight, this time choosing the 4th option (do not overwrite the status bar) with battery percentage indicator.
felacio said:
This intrigues me. Sprint supported? I don't feel like dealing with force closes mentioned in previous post in different variant.
Sent from my LG-LS995 using Tapatalk
Click to expand...
Click to collapse
probably. the script set is practically compatible with all current LGE devices with JB or KK. only few apks should be troublesome.
if not sure, choose not to change the status bar during installation. then it will not overwrite both framework-res and systemui.
Gonna try it on my d950
---------- Post added at 01:31 AM ---------- Previous post was at 01:17 AM ----------
Mahh nothing different.... install went perfect,so far no force closes. What is this supposed to be? I dont see any difference. I used the f340u+. Nothing special going on with this. Restoring my back up now.
podagee said:
Gonna try it on my d950
---------- Post added at 01:31 AM ---------- Previous post was at 01:17 AM ----------
Mahh nothing different.... install went perfect,so far no force closes. What is this supposed to be? I dont see any difference. I used the f340u+. Nothing special going on with this. Restoring my back up now.
Click to expand...
Click to collapse
Don't you see messages like 'GomdoLight: System starting up'?
You usually don't see visible differences after installing GomdoLight, especially on non-Korean firmware, since it does not know what apps to debloat. You would have to debloat the system yourself. However its extensive startup script set provides very unique and useful functions. These functions are explained in the simplified user manual that is automatically displayed after installing. If you did not see the manual opening, and if you do not see the startup messages either, probably something is wrong.
juniecho said:
Don't you see messages like 'GomdoLight: System starting up'?
You usually don't see visible differences after installing GomdoLight, especially on non-Korean firmware, since it does not know what apps to debloat. You would have to debloat the system yourself. However its extensive startup script set provides very unique and useful functions. These functions are explained in the simplified user manual that is automatically displayed after installing. If you did not see the manual opening, and if you do not see the startup messages either, probably something is wrong.
Click to expand...
Click to collapse
I seen all the startups and everything. Gomdo warning of superuser, a major lag on my phone for abot 3-5 minutes of lag. It only uninstalled vutalj. I honestly havent noticed anything special. I even tried it with that status bar selection and it went through fine.
podagee said:
I seen all the startups and everything. Gomdo warning of superuser, a major lag on my phone for abot 3-5 minutes of lag. It only uninstalled vutalj. I honestly havent noticed anything special. I even tried it with that status bar selection and it went through fine.
Click to expand...
Click to collapse
gomdolight's optimizations are not much visually noticable, without drastic changes. if you expect a whole new experience this is not your type of rom.
or, you could install another stock-based rom that will bring significant changes, and install gomdolight over it (without status bar selection) to further aid with its performance.
think gomdolight as a special tool to streamline and 'properly' reorganize the stock firmware (or, stock-based roms). changes are not noticable at first sight, but they surely benefit the user somehow in the long run, and give you better control and (sometimes) superior disaster handling capabilities.
anyway, thank you for letting me know that selecting LGU+ model increases compatibility with non-Korean firmwares.
juniecho said:
gomdolight's optimizations are not much visually noticable, without drastic changes. if you expect a whole new experience this is not your type of rom.
or, you could install another stock-based rom that will bring significant changes, and install gomdolight over it (without status bar selection) to further aid with its performance.
think gomdolight as a special tool to streamline and 'properly' reorganize the stock firmware (or, stock-based roms). changes are not noticable at first sight, but they surely benefit the user somehow in the long run, and give you better control and (sometimes) superior disaster handling capabilities.
anyway, thank you for letting me know that selecting LGU+ model increases compatibility with non-Korean firmwares.
Click to expand...
Click to collapse
Okay. I will reinstall again and run it for a while to see its benefits. Thanks
podagee said:
Okay. I will reinstall again and run it for a while to see its benefits. Thanks
Click to expand...
Click to collapse
the built-in user manual explains some of its advantages... take a look at it, especially the section for what is called gomdolight flags.
UPDATE - Wave 2, revision 3
UPDATE LEVEL: MEDIUM / IMPORTANCE: HIGH
UPGRADE INSTRUCTIONS:
One-touch upgrade via 'Upgrade/Repair' option
CHANGELOG:
Improved GomdoLight Engine scripts
Faster boot time, reduced processor load during boot
Improved GomdoLight operational status notifications
Slightly improved battery efficiency
'Update Center' components updated
Since the bootloader just got unlocked, does anybody know if the moto maxx roms work on the turbo yet and if they don't how can we get them up and working?
Sent from my XT1254 using Tapatalk
I know CM is not working yet, but I can't vouch for any of the stock modified ROMs.
Sent from my XT1254 using Tapatalk
Just tried flashing XT1225 5.0.2 system. It boots up, but fails to set up. Reboots at the first setup screen.
I guess XT1250 4.4.4 will work since it has same FCC ID.
CM 12.1 s being worked on right now. See this page. Looks like it's been solved. You will probably get it in the next day or so with a new nightly.
Or workaround instructions may be posted before then.
http://forum.xda-developers.com/mot...axx-xt1225-cm12-0-pre-release-t3060089/page85
Once CM 12.1 is sorted, then the other ROMs, especially Resurrection Remix will adopt the same procedure. @Skrilax_CZ, the CM dev and @baybutcher27, the Resurrection Remix and Mokee dev, are helping each other on this. @baybutcher27 also has a custom kernel with lots of neat features, in addition to CM base kernel, so they both want this to work for ALL Quarks.
several trials and errors I did.
XT1250 KK -> XT1254 DOES Work without any FCs. Since it is an identical device, it should work fine. However, it needs LP stock rom which is unavailable I think.
XT1225 LP -> XT1254 DOES NOT Work.
- With XT1225 boot.img : Reboot after choosing language from Setup Wizard
- With XT1254 boot.img : Constant Telephone FC. Device seems to be working I guess
What are the odds of the quark forums being put back together now that we are unlocked? Rather than monitoring 3 diff forums? Not sure how it was before but making it similar to the G2 forums, where you had a general G2 dev forum, then a sub-forum for each specific carrier.
Anybody on XT1254, can you open adb and do "getprop ro.boot.radio" and "getprop ro.boot.carrier" and post the output?
Skrilax_CZ said:
Anybody on XT1254, can you open adb and do "getprop ro.boot.radio" and "getprop ro.boot.carrier" and post the output?
Click to expand...
Click to collapse
Code:
[email protected]:/ $ getprop ro.boot.radio
0x4
[email protected]:/ $ getprop ro.boot.carrier
[email protected]:/ $
Skrilax_CZ said:
Anybody on XT1254, can you open adb and do "getprop ro.boot.radio" and "getprop ro.boot.carrier" and post the output?
Click to expand...
Click to collapse
I attached a screen of my ADB screen
mbarry55 said:
What are the odds of the quark forums being put back together now that we are unlocked? Rather than monitoring 3 diff forums? Not sure how it was before but making it similar to the G2 forums, where you had a general G2 dev forum, then a sub-forum for each specific carrier.
Click to expand...
Click to collapse
That was what some of us suggested -- but the the Droid Turbo owners wanted us far, far away. Now they need us.
I suppose it might have been confusing at the time
I came from a razrm and while I shared a cm11 rom with several phones specs were different on the devices.
Personally I would like to see the forums merged as well. If it didn't make sense then. It does make sense now.
Sent from my XT1254 using XDA Free mobile app
mrkhigh said:
I suppose it might have been confusing at the time
I came from a razrm and while I shared a cm11 rom with several phones specs were different on the devices.
Personally I would like to see the forums merged as well. If it didn't make sense then. It does make sense now.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Perhaps the same people who petitioned for the divide need to petition for a merger?
I'm not sure who finally approved the Quark forum split, but @TonyStark was very helpful in making it go smoothly. Some stuff got put in wrong forum and he fixed it promptly.
Now with bootloader unlock and common kernels, ROMs, there's no reason to be divided anymore. Everything now works on all QUARKS.
I can see this being an issue. It seems as though a maxx dev put out a kernel for the Turbo that will run RR and CM12.1. Would that dev post it here as well, or link it with flashing instructions?
A lot of us have been sitting idle waiting for the bootloader unlock to happen, and haven't had to delve very deep into the inner workings of lollipop. I personally haven't had a bootloader unlocked phone since 2011 or so, so I m trying to be very cautious in what/how I flash. Having to bounce between forums and even devices is quite worrysome when you haven't been actively flashing for some time.
boomslick08 said:
I can see this being an issue. It seems as though a maxx dev put out a kernel for the Turbo that will run RR and CM12.1. Would that dev post it here as well, or link it with flashing instructions?
Click to expand...
Click to collapse
You are referring to @baybutcher27, who is also the Resurrection Remix dev and OFFICIAL TWRP QUARK dev. And yes he also has his own kernel, based on CM kernel but with additional options.
CM dev @Skrilax_CZ made CM kernel work for XT1254. But that will show up in tomorrow's "nightly".
You can find links to everything here:
Moto Maxx Original Android Development
http://forum.xda-developers.com/moto-maxx/orig-development
Moto Maxx Android Development
http://forum.xda-developers.com/moto-maxx/development
Moto Maxx Themes and Apps
http://forum.xda-developers.com/moto-maxx/themes-apps
Once you go to those links, read the first post and the last few posts. There's plenty of instructions.
Now that the XT2254 bootloader is unlocked, it's just another Quark. Everything will work.
Whether they duplicate those threads over here is up to the devs. That's double work to maintain two threads for the exact same releases.
If they decide to keep the devices separated it really just needs a post with a link saying "go here" in the droid rom section
Sent from my XT1254 using XDA Free mobile app
Has anyone got CM12 to work properly? I did a FDR, flashed the rom, and then butchers updated kernel. I can get it to boot, but it won't update/install any of my apps from the play store.
EDIT: OOps, i flashed one of the radio images in skrilax's CM12 thread. Not i can't get any signal. Anyone have the radio.img from SU4TL-44?
Wouldn't the download for 10/10/15 have what you need?
http://forum.xda-developers.com/showthread.php?p=61752986
Sent from my XT1254 using XDA Free mobile app
mrkhigh said:
Wouldn't the download for 10/10/15 have what you need?
http://forum.xda-developers.com/showthread.php?p=61752986
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Thought it did, i found it elsewhere. Got it to connect to cell when it loads up, still having the play store issue on RR as well as CM12.
I think it has something to do with the 'Storage space running out' message i'm getting. Not sure why thats there, never had it on any other rom/phone.
I have RR running without a hitch it seems. Calls, sms, mobile data all working normally. Havent had any google play issues yet either and ive installed quite a few apps. So far, so good here.
brennam7 said:
Thought it did, i found it elsewhere. Got it to connect to cell when it loads up, still having the play store issue on RR as well as CM12.
I think it has something to do with the 'Storage space running out' message i'm getting. Not sure why thats there, never had it on any other rom/phone.
Click to expand...
Click to collapse
I had that happen when I first flashed it this morning. I had done just a factory reset in twrp. When I mounted system and wiped the partition than reinstalled RR I didn't have a single problem. It shouldn't be doing that anyways seeing that the system partition is 5GB
Hello.
My phone is a SM-G903F with an android version of 6.0.1 and with an architecture of armeabi-v7a.
After flashing the xposed-v76-sdk23-arm.zip into my phone using TWRP (I also tried newer versions of the xposed framework) I end up getting a blue light and the samsung logo breathing constantly in a loop.
I can flash the xposed unistaller zip using the TWRP in the recovery mode and the phone works okay. But I would like to be able to install the xposed framework and make it work.
Can anyone help me or suggest anything I can do?
Thank you very much for your time,
Enrique
Try latest v86. It should works....
Samsung devices running TouchWiz have a tendency to bootloop when installing Rovo89's version of Xposed because it is developed for AOSP/Google Edition ROM's and their respective version of ART, whereas Samsung has made several changes in 5.0/5.1 that put it's functionality and code structure somewhere between 5.0/5.1 & 6.0, Vanilla Xposed v86 will likely not solve this issue, instead try flashing arter97's Xposed v79 (or v85 if you prefer, however I have not tested that version) of Xposed for Deodexed TouchWiz ROMs running on 5.0/5.1 (API21/22). If you are running 6.0 (API23) I am fairly certain you are out of luck as I don't believe a version of Xposed for TouchWiz 6.0 exists yet.
tiaxdaun said:
Samsung devices running TouchWiz have a tendency to bootloop when installing Rovo89's version of Xposed because it is developed for AOSP/Google Edition ROM's and their respective version of ART, whereas Samsung has made several changes in 5.0/5.1 that put it's functionality and code structure somewhere between 5.0/5.1 & 6.0, Vanilla Xposed v86 will likely not solve this issue, instead try flashing arter97's Xposed v79 (or v85 if you prefer, however I have not tested that version) of Xposed for Deodexed TouchWiz ROMs running on 5.0/5.1 (API21/22). If you are running 6.0 (API23) I am fairly certain you are out of luck as I don't believe a version of Xposed for TouchWiz 6.0 exists yet.
Click to expand...
Click to collapse
Hello.
I'm going to try these solutions and I will inform here on any feedback. Thank you very much!
Enrique
Just to expand on this
Arter xPosed for 5.0.x
Wanam xPosed for 5.1 and (yes) 6.0'x so you want a deodexed ROM and wanam's build of xPosed
Nergal di Cuthah said:
Just to expand on this
Arter xPosed for 5.0.x
Wanam xPosed for 5.1 and (yes) 6.0'x so you want a deodexed ROM and wanam's build of xPosed
Click to expand...
Click to collapse
I apologize but I didn't understand your answer. I have 6.0, so I must use 'wanam's build of xPosed' but what is a 'deodexed ROM' ?
Thank you and sorry but I'm new here.
Enrique
Go to your device's board and search deodex (odex is a android function that creates executables out of app files)
Read this
http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
It's not so important to understand the hows of it, you just need to find a ROM (there are many) that is deodexed. There are likely even a few completely stock touchwiz which have been deodexed. You should go to the XDA board for your device and should be able to find a working ROM
When a ROM is Odexed it means that a system application's cache files will be compressed in a separate odex file, so /system/priv-app/Email/Email.apk would also be accompanied by Email.odex in the same folder. The advantage of this was back when the Dalvik interpreter was used, it would speed up boot times. Deodexed on the other hand is the opposite, it stored the cache files inside an application's APK file, so Email cache would be in Email.apk/cache/com/google/android/Email.dex. Again back when the Dalvik interpreter was used this would slow down boot times significantly. However I believe that since ART became the new runtime the only time boot is slowed down is the very first one after a ROM is installed (albeit by about 15 minutes). If you aren't familiar with modifying ROMs (assuming you want to keep TouchWiz) I would recommend finding a Stock TouchWiz ROM that comes Deodexed, and pre-rooted with SuperSU already installed, make sure you backed up your data (either through google or manually) and install the Deodexed TouchWiz ROM, wait a while, as I said first boot with Deodexed ROMs are about 15 minutes slower than normal, and restore your data. After that you should be good to install Xposed for TouchWiz (beit Wanam or Arter97's is dependent on your OS version and what recovery you're using.) ?
just a question i got the same problem but i flashed my s6 with TYRANNUS ROM v28.1 and keep getting a bootloop when i try to flash xposed-v86-sdk23-arm64
Recovery is twrp-3.0.2-1-zeroflte
I did all the same like in the tutorial shown
and i dont know why can someone help me ? just want that xposed framework works and im stucking since hours of trying :/
As I mentioned before if you are running TouchWiz 5.0/5.1 you will have to use Arter97's Xposed for TouchWiz v79, API 21 if 5.0, API 22 if 5.1, Wanam Xposed for TouchWiz v79, API 23 if 6.0. ROM has to be Deodexed either way, use FlashFire version 0.24+ if flashing Arter97's Xposed, use TWRP 2.8.4.0+ if Wanam Xposed. Do keep in mind Rovo89's Xposed will not work with TouchWiz on 5.0+, you will have to use one of the above two alternatives.
tiaxdaun said:
... I would recommend finding a Stock TouchWiz ROM that comes Deodexed, and pre-rooted with SuperSU already installed ...
Click to expand...
Click to collapse
Would you have any suggestions on where I can find ROMs like that? Is there a main thread or a portal somewhere that lists all the popular ones?
And I have another side question if you don't mind me asking: The device I'm playing around with is a Canadian Galaxy S4 [SGH-I337M], does that mean the ROM I use needs to be compatible with that model specifically? Or are ROMs inconsiderate of the exact model and would work on all Galaxy S4's?
(There's also the different processor issue that depends on the S4's model; Snapdragon 600 vs. Exynos 5 Octa).
Thanks for the descriptive difference between the odexed and deodexed btw, yours is the best I've read so far
RaniKheir said:
Canadian Galaxy S4 [SGH-I337M],
Click to expand...
Click to collapse
Start here
http://forum.xda-developers.com/galaxy-s4-att
Nergal di Cuthah said:
Start here
http://forum.xda-developers.com/galaxy-s4-att
Click to expand...
Click to collapse
Hmmm, seemed a bit off at first since I see the American AT&T everywhere, but then I noticed the thread [SGH-I337M] CF-Auto-Root there and realized the I337 and I337M models are put together.
So I see ROMs under all of the following:
AT&T SAMSUNG GALAXY S 4 ANDROID DEVELOPMENT
AT&T SAMSUNG GALAXY S 4 ORIGINAL ANDROID DEVELOPMENT
SAMSUNG GALAXY S 4 UNIFIED DEVELOPMENT
Does that mean there's no main thread which keeps track of all the popular ROMs?
Also, since you linked me to that portal, does that also mean (for my second question) that the ROMs need to be designed for a specific model? It's not generic that any S4 can use any ROM designed for S4?
Thanks!
RaniKheir said:
Hmmm, seemed a bit off at first since I see the American AT&T everywhere, but then I noticed the thread [SGH-I337M] CF-Auto-Root there and realized the I337 and I337M models are put together.
So I see ROMs under all of the following:
AT&T SAMSUNG GALAXY S 4 ANDROID DEVELOPMENT
AT&T SAMSUNG GALAXY S 4 ORIGINAL ANDROID DEVELOPMENT
SAMSUNG GALAXY S 4 UNIFIED DEVELOPMENT
Does that mean there's no main thread which keeps track of all the popular ROMs?
Also, since you linked me to that portal, does that also mean (for my second question) that the ROMs need to be designed for a specific model? It's not generic that any S4 can use any ROM designed for S4?
Thanks!
Click to expand...
Click to collapse
Correct, as far as I remember the s4 was carrier dependent. My s4 for vzw was cdma only so only vzw roms/mods would have worked. Your device is GSM and Canadian GSM followed the AT&T device build (as far as I could tell). What I did was (on the XDA website) type I337 into device search and only that device shows. The name of that top board was AT&T, Canadian, Rogers thus it confirmed for me this was your phone. There is usually in one of those boards a curated index. There are dozens of ROMs, you just need to read, nobody here (worth a salt) will be able to just give you "the best" answer. You need to read, and understand what you are doing. If you do anything wrong, especially with Samsung touchwiz devices, you will void your warranty (samsungs have a hardware fuse that burns out if you Root or modify incorrectly) and could even hardbrick your phone. But if you just use search while in the forum I pointed to you should easily find what you need. (Hint, type xPosed into the searchbox on the website I should limit the search to your device's forum if you are already on the page I posted)
---------- Post added at 12:16 AM ---------- Previous post was at 12:10 AM ----------
Arrrgggg I promised myself not to spoon feed you but
http://forum.xda-developers.com/xposed/b-how-to-install-xposed-att-samsung-t3162866/post61985162
---------- Post added at 12:19 AM ---------- Previous post was at 12:16 AM ----------
And here's an index http://forum.xda-developers.com/showthread.php?t=2616221&highlight=xposed
Please though learn from this then you too can help others
---------- Post added at 12:24 AM ---------- Previous post was at 12:19 AM ----------
And I understand it's not appealing to read 450+pages on threads but just skim through threads, 99 percent of problems you'll encounter will have been previously reported and likely solved. I lurked on XDA for at least a year before I spoke and read (at least topic titles of) every topic for both the devices I've had and read/subscribed to topics for every xPosed module I use.
Ok done preaching....sorry
Nergal di Cuthah said:
Correct, as far as I remember the s4 was carrier dependent. My s4 for vzw was cdma only so only vzw roms/mods would have worked. Your device is GSM and Canadian GSM followed the AT&T device build (as far as I could tell). What I did was (on the XDA website) type I337 into device search and only that device shows. The name of that top board was AT&T, Canadian, Rogers thus it confirmed for me this was your phone. There is usually in one of those boards a curated index. There are dozens of ROMs, you just need to read, nobody here (worth a salt) will be able to just give you "the best" answer. You need to read, and understand what you are doing. If you do anything wrong, especially with Samsung touchwiz devices, you will void your warranty (samsungs have a hardware fuse that burns out if you Root or modify incorrectly) and could even hardbrick your phone. But if you just use search while in the forum I pointed to you should easily find what you need. (Hint, type xPosed into the searchbox on the website I should limit the search to your device's forum if you are already on the page I posted)
Click to expand...
Click to collapse
I'm not looking for the "best" answer, most likely there isn't one "best" ROM anyway I was just wondering if there's a portal somewhere for all the popular ones where I can browse through them, maybe with a description for each with links to the original posts.
Reading and understanding is what I've been doing, to some extent at least, if someone wants to dig into the details it could take months of testing and source code reading to understand everything that's going on under the hood
Thanks for the warnings and hints
---------- Post added at 12:42 AM ---------- Previous post was at 12:36 AM ----------
Nergal di Cuthah said:
http://forum.xda-developers.com/xposed/b-how-to-install-xposed-att-samsung-t3162866/post61985162
And here's an index http://forum.xda-developers.com/showthread.php?t=2616221&highlight=xposed
Click to expand...
Click to collapse
I've seen both of those, they're both for AT&T [I337], which have a locked bootloader. Mine is an I337M, which has an unlocked bootloader, so the steps probably differ a little
But thanks for the links! All appreciated
RaniKheir said:
Would you have any suggestions on where I can find ROMs like that? Is there a main thread or a portal somewhere that lists all the popular ones?
And I have another side question if you don't mind me asking: The device I'm playing around with is a Canadian Galaxy S4 [SGH-I337M], does that mean the ROM I use needs to be compatible with that model specifically? Or are ROMs inconsiderate of the exact model and would work on all Galaxy S4's?
(There's also the different processor issue that depends on the S4's model; Snapdragon 600 vs. Exynos 5 Octa).
Thanks for the descriptive difference between the odexed and deodexed btw, yours is the best I've read so far
Click to expand...
Click to collapse
I do indeed have a recommendation, assuming you want stock TouchWiz (newer versions are growing more like Google edition) I have the SGH-I337 and am running Albe95 ROM (the port of S6's stock 5.1 firmware), now I have a unique copy of the NB1 bootloader but for that reason this OS should also work for you, it comes with all S6 features (theme engine included, but don't change your model number from SM-G920A or you wont be able to connect), can be installed from flash fire, is Deodexed, comes pre rooted with SuperSU installed, is fully compatible with the API21 version of Arter97's Xposed, and wont delete any user data during the pre-install wipe. As a bonus its also compatible with most AOSP tweaks and root modules including Android-Nify (so you can use some Nougat features before its released, though we obviously already have multiwindow and single row quick toggles, but still ).
BTW I do believe its for both SGH-I337 and SGH-I337M, or at the very least there is a port for it, however I do believe it works on both (again, it is Stock TouchWiz so locked or unlocked bootloader doesn't matter and it expects Flash Fire rather than a custom recovery either way as well ;P).
tiaxdaun said:
I do indeed have a recommendation, assuming you want stock TouchWiz (newer versions are growing more like Google edition) I have the SGH-I337 and am running Albe95 ROM (the port of S6's stock 5.1 firmware), now I have a unique copy of the NB1 bootloader but for that reason this OS should also work for you, it comes with all S6 features (theme engine included, but don't change your model number from SM-G920A or you wont be able to connect), can be installed from flash fire, is Deodexed, comes pre rooted with SuperSU installed, is fully compatible with the API21 version of Arter97's Xposed, and wont delete any user data during the pre-install wipe. As a bonus its also compatible with most AOSP tweaks and root modules including Android-Nify (so you can use some Nougat features before its released, though we obviously already have multiwindow and single row quick toggles, but still ).
BTW I do believe its for both SGH-I337 and SGH-I337M, or at the very least there is a port for it, however I do believe it works on both (again, it is Stock TouchWiz so locked or unlocked bootloader doesn't matter and it expects Flash Fire rather than a custom recovery either way as well ;P).
Click to expand...
Click to collapse
Albe95 sounds really good! Will give it a try, thanks
I have never used or read much on Flash Fire, so that will probably be another whole day of experimenting and hoping my device doesn't brick lol. Will make a nandroid backup and give it a shot, thanks again!
Question for Kernel Devs, Re: Hotspot, DUN, "Carrier does not allow type 'dun'."
Devs of kernels, ever since Android O, attempting to add dun to APN, results in error "Carrier does not allow type 'dun.'", ever since Google baked it in for the benefit of carriers (in this particular case, T-mobile) to prevent hotspot tethering.
That's very nice of them, but not helpful for me, who must stay on Android N for my hotspot to work properly.
Can one of you kernel devs modify this so that hotspot will once again work properly, or tell me of a kernel or ROM on which it already works the way it used to?
You can let me know via DM if you don't want to reply here.
pbergonzi said:
Devs of kernels, ever since Android O, attempting to add dun to APN, results in error "Carrier does not allow type 'dun.'", ever since Google baked it in for the benefit of carriers (in this particular case, T-mobile) to prevent hotspot tethering.
That's very nice of them, but not helpful for me, who must stay on Android N for my hotspot to work properly.
Can one of you kernel devs modify this so that hotspot will once again work properly, or tell me of a kernel or ROM on which it already works the way it used to?
You can let me know via DM if you don't want to reply here.
Click to expand...
Click to collapse
There has been work on this in LOS. Particularly @nvertigo67 has got a good understanding of the issue and has been endeavoring to enable the functionality on a case by case basis. I'd begin there if i were you.
Dirk said:
There has been work on this in LOS. Particularly @nvertigo67 has got a good understanding of the issue and has been endeavoring to enable the functionality on a case by case basis. I'd begin there if i were you.
Click to expand...
Click to collapse
Thank you.
@nvertigo67 made a custom confs file that we tested on LOS 16--while it did indeed install dun parameter, the result was still non-functional.
He is still researching, however we both believe google baked in the functionality, and it needs a kernel dev to find it. There were articles a while back (the advent of Oreo?) that refer to google having done so.
pbergonzi said:
Thank you.
@nvertigo67 made a custom confs file that we tested on LOS 16--while it did indeed install dun parameter, the result was still non-functional.
He is still researching, however we both believe google baked in the functionality, and it needs a kernel dev to find it. There were articles a while back (the advent of Oreo?) that refer to google having done so.
Click to expand...
Click to collapse
I've stated it's "more complecated" then adding dun - I've never stated it's kernel related, and I don't think it's kernel related!
I've stoped dealing with this, because I'm tired of begging for information. When we tried the modified apns-conf.xml, you told me it's not not working, but it's working unusable slowly ("like before without the modified apns-conf.xml")...
Again: this is NOT related to the kernel.
nvertigo67 said:
I've stated it's "more complecated" then adding dun - I've never stated it's kernel related, and I don't think it's kernel related!
I've stoped dealing with this, because I'm tired of begging for information. When we tried the modified apns-conf.xml, you told me it's not not working, but it's working unusable slowly ("like before without the modified apns-conf.xml")...
Again: this is NOT related to the kernel.
Click to expand...
Click to collapse
I apologize for misunderstanding.
Thank you for the clarification and your efforts.
nvertigo67 said:
I've stated it's "more complecated"
Click to expand...
Click to collapse
Found another solution--sold OP3T and got OP6T. Surprisingly, it connects properly with pie, using stock or modded ROMs.
Phew.
pbergonzi said:
Found another solution--sold OP3T and got OP6T. Surprisingly, it connects properly with pie, using stock or modded ROMs.
Phew.
Click to expand...
Click to collapse
Which proofes, you were wrong with the dun change you've ask me to do - on los op6t and op3/t use the very same apns-conf.xml file... Perhaps because it's more complecated... *lol*
nvertigo67 said:
Which proofes, you were wrong with the dun change you've ask me to do - on los op6t and op3/t use the very same apns-conf.xml file... Perhaps because it's more complecated... *lol*
Click to expand...
Click to collapse
Yes, thank you.