Looking around and the support seems iffy. I see the thread that shows how to get pay working with android root using systemless SU. But do any of the current ROMs have support for pay on a fresh install? Or will re-flashing systemless SU work with those roms.
Pure nexus
Ah, I am running that and I get the message that it cannot be verified. Are there any steps needed to be taken? I looked through their thread and couldn't find anything other than others asking if it worked as well.
luckysmack said:
Ah, I am running that and I get the message that it cannot be verified. Are there any steps needed to be taken? I looked through their thread and couldn't find anything other than others asking if it worked as well.
Click to expand...
Click to collapse
There's a link to the FAQ in post 2. Then the FAQ has a link to the steps to get Android Pay working. I haven't checked recently but I think you'll have to use an older set of gapps to get it working.
Sent from my Nexus 5X using XDA-Developers mobile app
Hrmm, I followed that and tried clean install as well. Everything seemed to be fine, changed permissions on /su/bin as well. Pay still doesnt allow me to add cards.
Something had to have changed in the past two weeks or so. I can't get Android Pay working on any ROMs any more. I follow the same steps as before but nothing. Hopefully with AP being released in the UK someone can figure out a work around.
Pure nexus plus Elemental kernel works fine
Sent from my Nexus 5X using Tapatalk
Android pay should work if you are using SU 2.71 or 2.72. I tried this on a different device as well. Works on stock rooted, and elemental kernel;as mentioned above.
its on 2.74 now; cannot confirm or deny working with it.
forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Best Regards
Related
Hi folks,
I rooted my phone but no applications that require root access work.
I am currently running the 40.2 update on my verizon nexus.
I tried wifi_tether_v3_1-pre111.apk, rom tool box, root checker and root toolbox.
Rooted applications always say that my phone doesn't have root access or a kernel is missing.
When I do a fastboot oem lock, it shows that my phone is unlocked. I am quite confused as to why no programs that require root work for this phone.
Is their any programs out there that can verify that phone is rooted. Is their any technique other then what I tried that can verify it.
I am stuck and I dont know what else to do.
Is anyone else experiencing this issue? I cannot be the only one.
Simply unlocking the boot loader does not give you root. Check the stickies in the dev forum a guide
Sent from my Galaxy Nexus using Tapatalk
I have checked. If you could "simply" provide a link to even one sticky with this information other than the "obvious" answer you provided I'd be quite appreciative.
If you don't know that is fine to. Don't be the guy/gal who gives driving directions but has no idea.
Thanks!
vastcomm said:
I have checked. If you could "simply" provide a link to even one sticky with this information other than the "obvious" answer you provided I'd be quite appreciative.
If you don't know that is fine to. Don't be the guy/gal who gives driving directions but has no idea.
Thanks!
Click to expand...
Click to collapse
Check my sig
Sent from my Galaxy Nexus using Tapatalk
vastcomm said:
I have checked. If you could "simply" provide a link to even one sticky with this information other than the "obvious" answer you provided I'd be quite appreciative.
If you don't know that is fine to. Don't be the guy/gal who gives driving directions but has no idea.
Thanks!
Click to expand...
Click to collapse
I normally would of, or but I answered your question on mobile as i was leaving the house this morning
Sent from a phone that is not running ICS
You need to install the root binaries to achieve root, look in the general thread and theirs a guide to show you how to root with superboot r3. Once you run it in adb, it will install the binaries and superuser apk. Then after go to the market and search busybox, install the app and let it install the busy box file.
It is impossible that your missing a kernel if your phone can boot. The programs you installed to check "root" are not compatible with the phone. For future reference, check the stickies in the general thread.
Sent from my Galaxy Nexus using xda premium
Hello all. I just ordered a Note 2 which I've yet to receive. My goal is to have a rooted, stable running phone. I've read through LOTS of threads and am trying to figure out where to start.
Is this the best method to root or should I not accept the latest update and go another method? http://forum.xda-developers.com/showthread.php?t=2118348
Should I flash a ROM or just run stock. If ROM, any recommendations?
Sorry for the noob questions...
First of all which Note 2 do you have? N7100 (international) or the carrier ones?
Thank you for your reply. I bought the Verizon model.
Sent from my GT-N8013 using Tapatalk 2
I would not recommend you to flash a rom if you need a stable phone.
My Note 2 is the only Android device I've owned that I didn't feel compelled to root.
My suggestion is that you run in bone stock a couple of weeks, and then see if you feel you really need to root.
Regards,
Dave
Sent from my GT-N7100 using Tapatalk 2
gsjjiq said:
I would not recommend you to flash a rom if you need a stable phone.
Click to expand...
Click to collapse
Flashed my Note 2 within 30 mins of buying it. Stable as a rock, no problems whatsoever.
Flashing roms doesn't lead to instability. Over tweaking perhaps does. Personally I like to run ad blockers, change my dpi and personalise my interface and remove bloatware...
sent from somewhere
liquidguru said:
Flashed my Note 2 within 30 mins of buying it. Stable as a rock, no problems whatsoever.
Flashing roms doesn't lead to instability. Over tweaking perhaps does. Personally I like to run ad blockers, change my dpi and personalise my interface and remove bloatware...
sent from somewhere
Click to expand...
Click to collapse
That sounds good. What did/do you use?
grimloktt said:
That sounds good. What did/do you use?
Click to expand...
Click to collapse
I use monx's Rom.. you need to root first. Look up the necessary posts on rooting, read them then read them again. Backup. Read some more.... the process can seem intimidating at first, but you can get plenty of help on these forums. And go slowly and don't forget to backup frequently, so if anything goes wrong you can get back to a state where it was working.
sent from somewhere
liquidguru said:
I use monx's Rom.. you need to root first. Look up the necessary posts on rooting, read them then read them again. Backup. Read some more.... the process can seem intimidating at first, but you can get plenty of help on these forums. And go slowly and don't forget to backup frequently, so if anything goes wrong you can get back to a state where it was working.
sent from somewhere
Click to expand...
Click to collapse
Thank you. I've now rooted a couple phones but was wondering what's the best way forward considering the latest updates and locked boot loader? Is the link I posted above the recommended course of action or should I use CF-auto root or other?
yeah flashing means you will most likely void your warranty. not a smart act for a noob like me, at least!
liquidguru said:
I use monx's Rom.. you need to root first. Look up the necessary posts on rooting, read them then read them again. Backup. Read some more.... the process can seem intimidating at first, but you can get plenty of help on these forums. And go slowly and don't forget to backup frequently, so if anything goes wrong you can get back to a state where it was working.
sent from somewhere
Click to expand...
Click to collapse
Also, what recovery is working for you/this phone to flash ROM?
grimloktt said:
Also, what recovery is working for you/this phone to flash ROM?
Click to expand...
Click to collapse
Personally I use PhilZ Touch 3 Recovery, which works perfectly for me, the roms I've flashed and all the zip files I've used. Instructions for rooting are in post 2. It also works with exFat, so my 64GB SDcard has no problems.
I also use the Perseus kernel, which works well for me.
As was mentioned a couple of posts back, all this does indeed void your warranty. Again for me, this is a non-issue. I'm a brit, living in Indonesia, bought the phone in HK, so any warranty is pretty useless to me.
Have fun
I'm a new user as well and have been fiddling with my n1700 for a few weeks now. Personally I think I know what I'm doing but like the guy said you have to keep on reading on the forums. I flashed Android Revolution HD on my phone 2 days ago. Pretty happy with it. I might flash it again cause im tweaking my battery but it's a pretty stable rom.
liquidguru said:
Personally I use PhilZ Touch 3 Recovery, which works perfectly for me, the roms I've flashed and all the zip files I've used. Instructions for rooting are in post 2. It also works with exFat, so my 64GB SDcard has no problems.
I also use the Perseus kernel, which works well for me.
As was mentioned a couple of posts back, all this does indeed void your warranty. Again for me, this is a non-issue. I'm a brit, living in Indonesia, bought the phone in HK, so any warranty is pretty useless to me.
Have fun
Click to expand...
Click to collapse
Thnx! I looked at that thread and wonder what this means: "TL;DR: before flashing aside from known issues in the second post.?" Also, I looked through post 2 and didn't see where the install instructions were located. I see there are zip and tar files; I'm assuming the user can choose between flashing it with ODIN or CWM?
LiquidGuru,
Any chance you could point me to DPI thread? My initial browsing and searches have turned up empty.
Thnx!
grimloktt said:
LiquidGuru,
Any chance you could point me to DPI thread? My initial browsing and searches have turned up empty.
Thnx!
Click to expand...
Click to collapse
Changing the DPI on a stock based ROM takes a little work. Initially it's very easy. You edit the build.prop (I use ROM Toolbox Pro). Look for the two instances of ro.sf.lcd_density and change them to your desired DPI (I use 240) and reboot...that's it!! (if only is was that simple...)
Unfortunately not everything likes to play nice at 240DPI, especially the sammy keyboard, camera, multiwindow and dialer. Sooooo..... bala_gamer has made some mods of these apps that you can flash (see this post). I also use the Xposed Framework with the Xposed App Settings mod which allows you to set the DPI for individual apps (there are also many other useful apps that work with the Xposed Framework)...
I worked it all out from reading those threads, asking a few questions. Everything is pretty straightforward, just take your time, backup and make sure your battery is fairly well charged before you started flashing I love my N2, love being at 240DPI and everything set up the way I need it.
Liquid,
Is this the ROM you went with? http://forum.xda-developers.com/showthread.php?t=2070459
grimloktt said:
Liquid,
Is this the ROM you went with? http://forum.xda-developers.com/showthread.php?t=2070459
Click to expand...
Click to collapse
No, that's the CM10 one. [I went with this http://forum.xda-developers.com/showthread.php?p=33577075 one, the TW based one, which retains all the s-pen etc functionality
sent from somewhere
liquidguru said:
No, that's the CM10 one. [I went with this http://forum.xda-developers.com/showthread.php?p=33577075 one, the TW based one, which retains all the s-pen etc functionality
sent from somewhere
Click to expand...
Click to collapse
Have you compared against the following ROMs and noted any key differences?
http://forum.xda-developers.com/showthread.php?t=1915036
http://forum.xda-developers.com/showthread.php?t=2060389
I use stock ROM + root + perseus kernel + XposedFramework.
I don't recommend stock based custom ROMs because most of the time the same features can be archieved with more flexibility using XposedFramework plugins.
As for AOSP-based ROMs such as CyanogenMod, I didn't try these on my Note 2 because it means losing many Samsung features that I like. Also, CyanogenMod for Note 2 is still in development.
Hello everybody!!
My friend gave me his Virgin mobile Samsung Galaxy S3 to root and install a custom ROM on. I have install the latest TWRP recovery, and flashed the Super SU. I am not rooted on stock. I was wondering how to go about installing a custom ROM. I think that the Virgin Mobile and the Sprint are very similar, but I noticed something on the ROMs posted in the development forum. For example, http://forum.xda-developers.com/showthread.php?t=2750674 shows that it is meant to work on versions with NJ2 and ND8. My S3 here has NJ3. I am wondering what this means. I have NJ3 on my S3, and I was wondering that meant. Does it mean that it is different version completely, or does it mean that it simply says that because it is Virgin Mobile and is still pretty much the same thing? That being said, would that ROM work on my S3 with NJ3?
Thanks everybody for your help and development to make this community awesome!
Okay, well I installed it anyways. It works great, but I need to find the APNs for Virgin Mobile. If someone can point that out to me, I would really appreciate it. Virgin Mobile US internet.
Jayfeather787 said:
Okay, well I installed it anyways. It works great, but I need to find the APNs for Virgin Mobile. If someone can point that out to me, I would really appreciate it. Virgin Mobile US internet.
Click to expand...
Click to collapse
Here's the APN fix. You flash the zip in a custom recovery: http://androidforums.com/threads/vi...rgin-mobile-apn-fix-wip-cm-aosp-4-4-x.840298/ My Virgin Mobile SIII is on NJ3, and the APNs work fine. NJ3, ND8, etc is just the modem. AFAIK it allows for connecting to the network, and newer modems have better connections. Any d2spr ROM should work fine on Virgin Mobile SPH-L710 (NOT SPH-L710T, be careful) if you flash the APN fix.
---------- Post added at 09:40 PM ---------- Previous post was at 09:37 PM ----------
Jayfeather787 said:
Hello everybody!!
I have install the latest TWRP recovery, and flashed the Super SU.
Click to expand...
Click to collapse
Did you use some modified version of TWRP? The normal official version can't mount partitions properly. I tried installing it and sh*t hit the fan. I had to use a gummified version of TWRP 2.8.0.0.
Thanks for the reply! I found the same problem, and I installed CWM. I did the APN fix, but mobile data won't work. Do I now have to put the APNs for the data to work?
No, after you flash the fix in recovery, everything should be taken care of. Sometimes you might have to flash it a few times to get it to stick, I suppose. The only thing I can think of to recommend is to make sure you follow the instructions and give the FAQs a read. That should explain evertything you need to do.
As a side note, here's a link to the Gummified TWRP that I'm using, in case you want TWRP (I personally prefer TWRP over CWM/PhilZ). You can just install it using the dd method with a terminal emulator on your phone using the instructions on the TWRP site. It's the TWRP 2.8.0.0.img. https://drive.google.com/folderview?id=0B1mtB5XM-ndHQThQX08xRWFVSzQ#
Thanks for the APN fix for Virgin Mobile. I just updated to CM12.1 on my S3 and had no data until I applied this fix.
Thanks so much, I will give that a try! I flashed it once, and it did not work. I will try flashing it a couple times in order to get it to work.
Are you trying to flash an android 5.1 ROM? Sh*t hit the fan on cm12.1 and all ROMs using cm as a base, and the APN fix doesn't have LTE on 5.1. If you want stability, I'd just go with a kitkat d2lte ROM. This bug is getting worked out, though. They just fixed it on cm, I think
Yep, I found that out the hard way lol. Thanks anyways, I will let my friend back it up, and I will just install kitkat on it. Thanks for your help.
You could also install a touchwiz ROM like wicked s5 for stability, but if you ask me, half the reason to root is to get away from touchwiz
Touchwiz must die.
Hi, guys!
I have a friend who also has a VM S3, and, of course, I told him he could have a way better Android experience if he let me help him put Cyanogenmod on it. He agreed to it, liking the idea of revitalizing his phone, and I went right ahead to the XDA forums to do some research. I came across this thread (obviously), and while it was immensely helpful (thank you everyone who contributed and provided links), it has got some out of date information and a few things gone unmentioned. So, I'll briefly compile a list of everything I know here to save future VM S3 modders some trouble and headache.
1) The latest TWRP (as of right now, it's 3.0.2-0) does work on the VM S3. Whatever issue was there in older versions is taken care of.
2) It is true that one will need to flash the APN fix linked in previous comments. That will get mobile data working.
3) However, in the very article linked, one will also see a Stock MMS fix, because even with the APN fix, the stock AOSP messaging app (in our case, that of Cyanogenmod 12.1) will not receive MMS. However, as users have commented in that forum, DO NOT flash that Stock MMS fix on anything above Android 4.4.4. As I discovered the hard way, it will only result in bootloop, as well as much headache and angst.
4) So, how do we fix the MMS glitch? Directly, there's no way (that I know of/can find). What I ended up doing for my friend was, when installing GAapps, I used the Aroma installer (because why wouldn't I?), and I had it install Google's Messenger app (in Aroma, it's labeled as just "Messenger"), and I had it block the installation of the Stock CM Messenger app. MMS now works fine.
5) Not a fan of Google Apps, or specifically Google's Messenger? Well, I hear Textra is good too. :fingers-crossed:
6) For the comment by @Powered_By_Linux on the issue concerning not getting LTE, I cannot say for certain as I no longer have my friend's phone with me, and I didn't think to test it. However, I know this: the comment was made in April 2015, and the snapshot release of CM12.1 is dated for November 2015, so I imagine it's possible something got fixed in between, as he said. Also, my friend hasn't complained to me yet about any sort of service problems (only praise for his rejuvenated phone), so I'm going to assume everything's working as it should. Also, there are other users in the linked APN fix article also saying their 4G/LTE works.
Again, thank you everyone who commented and provided links, as this thread was of great help to me. Here's to keeping those S3s alive and going strong!
Howdy, I'm currently playing with bigsupersquid's unofficial cyanogenmod 13.1 rom for the Virgin Mobile variant of this phone. Everything on it works great except for the wifi which seems not to activate at all - also preventing me from using my tethering. I was forwarded to update the firmware for this device to Lollipop, but outside of the "A5-DUG" variant, I seem to be having trouble finding it. Can anyone provide me the right directions or place to start for this? Any help would be appreciated, thanks!
davidw.roggenkamp said:
Howdy, I'm currently playing with bigsupersquid's unofficial cyanogenmod 13.1 rom for the Virgin Mobile variant of this phone. Everything on it works great except for the wifi which seems not to activate at all - also preventing me from using my tethering. I was forwarded to update the firmware for this device to Lollipop, but outside of the "A5-DUG" variant, I seem to be having trouble finding it. Can anyone provide me the right directions or place to start for this? Any help would be appreciated, thanks!
Click to expand...
Click to collapse
yer lucky, I don't often browse the regular forum, just the threads I've already posted in.
however, I obviously need to add this link to the OP for cm13 (and maybe cm12 as well.)
http://www.htc.com/us/support/htc-desire-816-virgin-mobile/news/
straight from the horse's mouth (htc,) that link.
getting it installed without M$ windows is challenging but can be done, requires some searching. with window$ it's relatively painless after downloading the 2+GB file and installing drivers and such.
I know some people are picky about questions in dev threads but I've always welcomed discussion there, so feel free to ask anything else in the ROM threads.
bigsupersquid said:
yer lucky, I don't often browse the regular forum, just the threads I've already posted in.
however, I obviously need to add this link to the OP for cm13 (and maybe cm12 as well.)
http://www.htc.com/us/support/htc-desire-816-virgin-mobile/news/
straight from the horse's mouth (htc,) that link.
getting it installed without M$ windows is challenging but can be done, requires some searching. with window$ it's relatively painless after downloading the 2+GB file and installing drivers and such.
I know some people are picky about questions in dev threads but I've always welcomed discussion there, so feel free to ask anything else in the ROM threads.
Click to expand...
Click to collapse
I'm guessing that this is the process to use a RUU and revert back to stock to get the OTA update? I went through a huge debacle trying to find just this and managed to get it to work with a stroke of luck. I'm actually using your Cyanogenmod 13.1 without much issues. I'll leave a bug report in your thread. Thanks again!
davidw.roggenkamp said:
I'm guessing that this is the process to use a RUU and revert back to stock to get the OTA update? I went through a huge debacle trying to find just this and managed to get it to work with a stroke of luck. I'm actually using your Cyanogenmod 13.1 without much issues. I'll leave a bug report in your thread. Thanks again!
Click to expand...
Click to collapse
How do you get lucky? I am on CM 13.1 and still can't get wifi. I have the RUU and tried through windows and just got errors.
tucker1003 said:
How do you get lucky? I am on CM 13.1 and still can't get wifi. I have the RUU and tried through windows and just got errors.
Click to expand...
Click to collapse
Here, for everyone having firmware issues on chl, I spent all day uploading the zip RUU.
Make sure your phone is charged first. Very bad juju for it to die during firmware flashes.
I'm not sure if it needs stock recovery installed to use it or not. May not install without it and that'd be a hassle. Follow the instructions linked in my cm13 first post for installing stock recovery if you're wanting to play it safe.
Definitely
fastboot oem lock
before putting the 0P9CIMG.zip on external SD and rebooting into HBOOT. Or it won't flash.
Then remove the sd card after it is finally done. It'll take a few reboots to finish.
Having trouble installing. Keep's asking me to install the drivers and reboot each time I open it. Maybe it doesn't like my busybox install I don't know. Hope someone here can figure it out. I was going off these instructions on the pixel board. Seems like they're concerned about passing safetynet so I can't tell if what they're doing is necessary for our device but I really don't care about safetynet (though I guess it might be nice if possible but I don't really use it) I just want better sound.
https://forum.xda-developers.com/pixel-xl/help/viper4android-oreo-t3660690
Anyone want to attempt and try to translate them for the nexus 5x? Let us know how you get it working if you do
I installed V4A magisk module and setenforce to 0. And V4A is working 100% fine with safety net pass. Sometimes it turn itself off but after a sec is fine again.
just install ARISE+Magnum+Opus+20170811
I'm not sure I understand these replies. Can someone give me a step by step with links to the files I would need to use? Keep in mind I'm currently rooted with standard su methods, would I need to unroot first?
colonelcack said:
I'm not sure I understand these replies. Can someone give me a step by step with links to the files I would need to use? Keep in mind I'm currently rooted with standard su methods, would I need to unroot first?
Click to expand...
Click to collapse
No need to unroot.
https://mega.nz/#!eBdhEQxR!upaXox94LqJvjHNVBE5FNcd1y-SFck1uwSeQ0McFArg
https://mega.nz/#!yV0gWIpK!DoWzQn0KHp2F_2JaiS7Az7EvrU9n7s1q9JL87-W17k0
The second file put in internal storage, flash via twrp the first file.
If not works for you dirty flash your rom over and sorry. It works for me but I'm still on nougat.
Sent from my Nexus 5X using Tapatalk
On my nexus 5x with oreo I installed the latest version of ARISE but when I go to "Driver Status" it says: "Abnormal" and "Unsupported".
Any help for this error?
Thanks
_____________________________________________________________________________________________________________
After reading very well the instructions from ARISE topic...now works perfectly