Related
i used odin to try and root my phone...now all i get is the screen where you touch the andriod to begin and it keeps saying...the application google services framework(process com.google.process.gapps)has stopped unexpectedly.please try again..force close...someone please help..im lost..and i can find nothing on this..
Deleted
johnb380 said:
Deleted
Click to expand...
Click to collapse
Your not a moderator in the first place so you can't just say deleted.
Sent from my SGH-T769 using xda premium
---------- Post added at 06:27 AM ---------- Previous post was at 06:25 AM ----------
Did you try rebooting the phone? If the problem still consists try factory resetting to stock and the root it again.
Sent from my SGH-T769 using xda premium
im_awesome_right? said:
Your not a moderator in the first place so you can't just say deleted.
Sent from my SGH-T769 using xda premium
---------- Post added at 06:27 AM ---------- Previous post was at 06:25 AM ----------
Did you try rebooting the phone? If the problem still consists try factory resetting to stock and the root it again.
Sent from my SGH-T769 using xda premium
Click to expand...
Click to collapse
Don't got to be a moderator to delete my own post... Lol
I had responded but deleted it it hence the "DELETED" IN MY POST
- - - - - - I'm not a Dev, I just flash ALOT!- - - - - - - - - If I've helped you the THANX button is - - - - - - - - - - - - - - only 2 clicks away! - - - - - - - - - -
nmadrid said:
i used odin to try and root my phone...now all i get is the screen where you touch the andriod to begin and it keeps saying...the application google services framework(process com.google.process.gapps)has stopped unexpectedly.please try again..force close...someone please help..im lost..and i can find nothing on this..
Click to expand...
Click to collapse
What gapps did you use? Sounds like a compatibility issue. Use the one from the Blaze Bible. After you flash the zip, factory reset. That should solve your problem. Still stuck? Boot cwm fix permissions, reboot. Last resort, start over from scratch and read very carefully each step....
If it helped hit thx
Same thing
I am having the same issue. It was after I installed cwm. the next step was to reboot into recovery mode, but I can't find anywhere that tells me to do it manually. I have also tried via ADB w/o success. I have tried various USB drivers in download mode and regular mode.
Any idea how to get into cwm and push .zips via USB from this state? Or, if I could install gapps from Odin, but I can't find a .tar for gapps.
heftykins said:
I am having the same issue. It was after I installed cwm. the next step was to reboot into recovery mode, but I can't find anywhere that tells me to do it manually. I have also tried via ADB w/o success. I have tried various USB drivers in download mode and regular mode.
Any idea how to get into cwm and push .zips via USB from this state? Or, if I could install gapps from Odin, but I can't find a .tar for gapps.
Click to expand...
Click to collapse
Must be rooted for this method.
Download terminal emulator from play store. Open and type su press enter. Then type reboot recovery and press enter.
Sent from my SGH-T769 using xda app-developers app
xWolf13 said:
Your not a moderator in the first place so you can't just say deleted.
Sent from my SGH-T769 using xda premium
---------- Post added at 06:27 AM ---------- Previous post was at 06:25 AM ----------
Did you try rebooting the phone? If the problem still consists try factory resetting to stock and the root it again.
Sent from my SGH-T769 using xda premium
Click to expand...
Click to collapse
Off topic.. I remember when I was all noobish hahaha. This post makes me looks stupid lol..
Wipe data/factory reset. from the stock recovery only works if you're on ics.
have you tried installing/ reinstalling the right gaaps?
Just clear cache and Dalvik.
Worst Case Scenario!
Hm, if none of the above comments help you try this:
Flash back to Official Stock GB using this thread.
(I know this thread has NOTHING to do with your problem, but it has a link to Stock GB AND a guide on how to flash it.)
After you flashed that, root your phone using this thread
Be careful and READ EVERYTHING before following either of those two threads, you could potentially end up destroying your device, if you do you'll have no one to yell at but yourself!
same problem here. haven't successfully fixed my friend's device. HELP!!
FroBreadCreamJellyPie said:
Hm, if none of the above comments help you try this:
Flash back to Official Stock GB using this thread.
(I know this thread has NOTHING to do with your problem, but it has a link to Stock GB AND a guide on how to flash it.)
After you flashed that, root your phone using this thread
Be careful and READ EVERYTHING before following either of those two threads, you could potentially end up destroying your device, if you do you'll have no one to yell at but yourself!
Click to expand...
Click to collapse
google services stopping unexpectedly after flashing - HELP SOS
Quote:
Originally Posted by AndyAZ1000 View Post
after i did this, it keeps saying
screen "Welcome to SGH-T769, TOUCH THE ANDROID TO BEGIN" but whenever i touch the android, it gives me and error "GOOGLE SERVICES FRAMEWORK HAS STOPPED UNEXPECTEDLY"
is this suppose to happen?
HELP!
I am having the same problem here. I was trying to root my friend's phone using the link with the odin and then install the newest CM (which btw is JUST AWESOME). On download mode, I'm seeing like 10 counts and custom binary. I also tried odin with this T769UVLB7_T769TMBLB7_TMB that I found in another post.
I erased everything in the 1.4 gb rom, I've tried it all for hours. I saw this post and somebody else with the same problem but it looks like they couldn't solve it. I don't think it's a driver issue because the roms get flashed but the problems occur on the welcome start page. Then all the processes and services start stopping unexpectedly and I can't go any further. please somebody help!!!
Also installed Samsung Kies to see if it could change the firmware or fix it or anything. That's what I used to erase everything on the ROM (because I thought that could be the issue). But no, kies says my firmware can't be recognized or sth like that.
I have flashed on my own blaze thousands of ROMS form xda, but this is the first time I see something like this.
---------- Post added at 04:01 AM ---------- Previous post was at 03:38 AM ----------
Quote:
Originally Posted by jparnell8839 View Post
wipe data/erase cache. sometimes, things go borky. thing is, if you followed the guide to a T, you should be 100% stock, but you've got things going wrong. if that doesnt work, reflash with odin again
How do I wipe and erase that on odin mode??
I'm having the same issues and no success. Guys, I will definitely appreciate this one. Please HELP!!
I rooted me One SV when it was 4.1.2, Sense4+ I had CWM 6.0.3.2 on it. Then my device said an OTA is available for my device. So I *RELOCKED* the bootloader and applied the OTA by following instructions from here, which went perfectly fine!
Then I went and unlocked the bootloader again, using the HTCDev site, then went fine too.
Now after rebooting, I seem to have lost the root. So in the link above I went ahead to do Step 4, I got the lastest TWRP for and flashed it with fastboot, flashing went fine.:good:
Now went I go to HBOOT Menu and select 'Recovery', all I get is the HTC Splash screen and 'Entering Recovery...' written on top.
I don't know if it actually flashed any recovery or not, as far as fastboot command was concerned it didn't return with any error!
Any help will be greatly appreciated!!!
It seems, you have k2u which has a new hboot with the OTA update.
You need a new recovery for that, which you can find here.
old.splatterhand said:
It seems, you have k2u which has a new hboot with the OTA update.
You need a new recovery for that, which you can find here.
Click to expand...
Click to collapse
Thanks for reply. But, I've got K2_UL instead, any clue for that one?
My bad! I found the one
Recovery_TWRP_2.6.3.2_K2_UL.img
Click to expand...
Click to collapse
that does the trick for me! Back to the rooted state now Thanks a ton!
Btw, how can I remove bloatware from the new OTA? NoBloat Free app can't recognise that device is rooted, so can't remove anything really. (Hope this doesn't require me to open a new thread)
Also before 4.2.2 update I had real trouble permanently removing the system apps like 'Best Deals' etc. NoBloat Free removed them but they always came back as soon as I rebooted the device
Any other bloatware removal app that you know that can do the trick for me? Thanks in anticipation!
Kernel has system write protection, which means you either need a custom kernel with write protection removed (which actually don't exist) or you must be S-off.
old.splatterhand said:
Kernel has system write protection, which means you either need a custom kernel with write protection removed (which actually don't exist) or you must be S-off.
Click to expand...
Click to collapse
So I must be S-OFF to be able to persist whatever I change between the reboots. Also another thing I noticed which is VERY annoying, after a while I loose the root 'state'!!!! Any reason why is that? Am I missing something?
Don't know about your root problem. But S-off is not wrong in my opinion.
If you are losing root then it sounds like it is temporary vice permanent... Interesting lol.
Sent from my HTC One SV using XDA Premium 4 mobile app
KunalAPatel said:
So I must be S-OFF to be able to persist whatever I change between the reboots. Also another thing I noticed which is VERY annoying, after a while I loose the root 'state'!!!! Any reason why is that? Am I missing something?
Click to expand...
Click to collapse
If your installing superSU as a system app, then every reboot the secure kernel is gonna kick it out......meaning lose root
Just keep superSU as a user app you'll be fine on reboots(with keeping root that is)
!#quote my post if you want to get my attention more quickly
russellvone said:
If your installing superSU as a system app, then every reboot the secure kernel is gonna kick it out......meaning lose root
Just keep superSU as a user app you'll be fine on reboots(with keeping root that is)
!#quote my post if you want to get my attention more quickly
Click to expand...
Click to collapse
I've got Superuser (from ClockWorkMod) installed as a system app and its not that it doesn't ever get root access. It DOES get the root access once booted up. The access stays for a while, and then after a while when try to do something that requires root, it fails!
What I did, after reading your post, was uninstalled the Superuser app using Titanium Backup. And without rebooting, installed it again from the market. And after reboot is comes back as system app! Grrrr.... Please help!!!
My problem is almost like this the one described here.
KunalAPatel said:
I've got Superuser (from ClockWorkMod) installed as a system app and its not that it doesn't ever get root access. It DOES get the root access once booted up. The access stays for a while, and then after a while when try to do something that requires root, it fails!
What I did, after reading your post, was uninstalled the Superuser app using Titanium Backup. And without rebooting, installed it again from the market. And after reboot is comes back as system app! Grrrr.... Please help!!!
My problem is almost like this the one described here.
Click to expand...
Click to collapse
I can write up a flashable zip that will remove the system superuser app and install it again straight to your user app location if you want. It will resolve the issue for you. Let me know. Won't take me long at all. I already have one done up. I would just have to make some slight changes in the updater-script.
Edit: I'm just gonna do it anyways, and I will come back with the link for you to download it. If you don't need it later then maybe someone else will down the road.
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 08:37 PM ---------- Previous post was at 08:14 PM ----------
Here it is
Just download, place on either root of internal or external sdcard and flash, then reboot device.
SUPERSU 1.75 AND BUSYBOX 1.21.1 FLASHABLE ZIP
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 08:41 PM ---------- Previous post was at 08:37 PM ----------
That will install su as a user app. it will also install and symlink Busybox and the su binary. When you open up SuperSU it won't ask for you to install the su binary. This is because I have taken care of that in the script. If you update through Google play then you will be given that request .
Sent from my C525c using XDA Premium 4 mobile app
KunalAPatel said:
I've got Superuser (from ClockWorkMod) installed as a system app and its not that it doesn't ever get root access. It DOES get the root access once booted up. The access stays for a while, and then after a while when try to do something that requires root, it fails!
What I did, after reading your post, was uninstalled the Superuser app using Titanium Backup. And without rebooting, installed it again from the market. And after reboot is comes back as system app! Grrrr.... Please help!!!
My problem is almost like this the one described here.
Click to expand...
Click to collapse
it'd be in your best interest to flash an unsecure kernel, being S-ON is gonna annoy you on every reboot if you use stock secure kernel.
Sent from my C525c using Tapatalk
I agree with @russellvone lol. Go S-Off though and it shouldn't be an issue anymore
Sent from my C525c using XDA Premium 4 mobile app
Modding.MyMind said:
I can write up a flashable zip that will remove the system superuser app and install it again straight to your user app location if you want. It will resolve the issue for you. Let me know. Won't take me long at all. I already have one done up. I would just have to make some slight changes in the updater-script.
Edit: I'm just gonna do it anyways, and I will come back with the link for you to download it. If you don't need it later then maybe someone else will down the road.
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 08:37 PM ---------- Previous post was at 08:14 PM ----------
Here it is
Just download, place on either root of internal or external sdcard and flash, then reboot device.
SUPERSU 1.75 AND BUSYBOX 1.21.1 FLASHABLE ZIP
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 08:41 PM ---------- Previous post was at 08:37 PM ----------
That will install su as a user app. it will also install and symlink Busybox and the su binary. When you open up SuperSU it won't ask for you to install the su binary. This is because I have taken care of that in the script. If you update through Google play then you will be given that request .
Sent from my C525c using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Firstly, thanks a lot that you promptly dished out the fix! I had SuperSU before Superuser but I wanted the one that could allow PIN protection thus Superuser. As in my previous post I tried to uninstalled it as a system app using Titanium Backup, and it was unsuccessful as the app is listed as system app under 'system/app/'. Though this, it seems to have fixed the problem of loosing
temporary vice permanent
Click to expand...
Click to collapse
root access. And thus I haven't applied your fixed yet (still, thank you for making the fix!).
However, I'd like to apply that fix of yours, but with Superuser app, and not SuperSU. Please let me know if I could (and how to) change your fix without bothering you to do it yourself, that way learning a bit myself on doing these things
russellvone said:
it'd be in your best interest to flash an unsecure kernel, being S-ON is gonna annoy you on every reboot if you use stock secure kernel.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Ok, thanks. Though, will it change anything in regards of the recovery or 4.2.2 & Sense 5 update? Where can I get one for K2_UL (T-Mobile UK)? Thanks again.:good:
KunalAPatel said:
Ok, thanks. Though, will it change anything in regards of the recovery or 4.2.2 & Sense 5 update? Where can I get one for K2_UL (T-Mobile UK)? Thanks again.:good:
Click to expand...
Click to collapse
hasn't been released yet, sometimes I forget who I'm speaking with, my apologies.
Sent from my C525c using Tapatalk
KunalAPatel said:
Firstly, thanks a lot that you promptly dished out the fix! I had SuperSU before Superuser but I wanted the one that could allow PIN protection thus Superuser. As in my previous post I tried to uninstalled it as a system app using Titanium Backup, and it was unsuccessful as the app is listed as system app under 'system/app/'. Though this, it seems to have fixed the problem of loosing root access. And thus I haven't applied your fixed yet (still, thank you for making the fix!).
However, I'd like to apply that fix of yours, but with Superuser app, and not SuperSU. Please let me know if I could (and how to) change your fix without bothering you to do it yourself, that way learning a bit myself on doing these things
Click to expand...
Click to collapse
I could do that, but it would be easier for you to flash the zip I did and then go in to the superSU app >> settings >> switch superuser app.
That will basically clean your device of SuperSU so you can go on the Google play store and install a different superuser app of your choosing.
Sent from my K2_CL using Tapatalk
Modding.MyMind said:
I could do that, but it would be easier for you to flash the zip I did and then go in to the superSU app >> settings >> switch superuser app.
That will basically clean your device of SuperSU so you can go on the Google play store and install a different superuser app of your choosing.
Sent from my K2_CL using Tapatalk
Click to expand...
Click to collapse
Cheers, I just did that. Switched the app to Superuser that I was using before. After flashing your zip I checked that Superuser is no longer a system app, which is partly what I wanted to do and thus achieved, so thank you. Though, I'd like to make a note that Superuser app asks for updating the su binary, as usual. I thought that was been taken care-of by your zip, or was it just for SuperSU? However, it remains to be seen if I loose the root again, between reboots.
Thanks again a lot.
It was just for SuperSu.
Sent from my K2_CL using Tapatalk
---------- Post added at 07:11 PM ---------- Previous post was at 07:09 PM ----------
Glad to help.
Sent from my K2_CL using Tapatalk
Modding.MyMind said:
It was just for SuperSu.
Sent from my K2_CL using Tapatalk
---------- Post added at 07:11 PM ---------- Previous post was at 07:09 PM ----------
Glad to help.
Sent from my K2_CL using Tapatalk
Click to expand...
Click to collapse
I'm STILL loosing my root access after a while! I'm going for S-Off but I can't seem to find and S-Off for JB 4.2.2 update, also ROM version 3.11* is not listed on Moonshine. Do you know of any? Thanks in advance.
Hello, I am looking for a custom ROM which has not been rooted and has lots of customizable options. Does such a thing exist?
The only reason I do not want a rooted version is because my barclays banking does not work with root. Ive been using Purity for the past year but after checking out stock 4.4.3 I decided to try the banking app as I had chance. It makes life so much easier
So yeah basically, is there a none root custom rom with all the features for customizing ect...
You can remove root from any rom. /system/bin/su or system/xbin/su
ROMs like Slimkat can turn root on and off.
There are also other options to hide root. Root cloak for example
Sent from my Nexus 5 using Tapatalk
there are also many custom roms that you also have to flash su with. if you dont flash su, then you use the rom without root. its actually a fallacy that you need root to use custom roms/kernels. you dont need root to flash things in a custom recovery as well.
---------- Post added at 05:33 PM ---------- Previous post was at 05:22 PM ----------
only thing is that you wont be able to use functions that need root, like changing your cpu speed amoung some things..
simms22 said:
there are also many custom roms that you also have to flash su with. if you dont flash su, then you use the rom without root. its actually a fallacy that you need root to use custom roms/kernels. you dont need root to flash things in a custom recovery as well.
---------- Post added at 05:33 PM ---------- Previous post was at 05:22 PM ----------
only thing is that you wont be able to use functions that need root, like changing your cpu speed amoung some things..
Click to expand...
Click to collapse
Also if you are using SuperSU there's also the full unroot option. :silly:
Lethargy said:
Also if you are using SuperSU there's also the full unroot option. :silly:
Click to expand...
Click to collapse
right, you can unroot. or just not flash supersu
simms22 said:
right, you can unroot. or just not flash supersu
Click to expand...
Click to collapse
On the odd chance that a ROM comes with SuperSU instead of SuperUser
Lethargy said:
On the odd chance that a ROM comes with SuperSU instead of SuperUser
Click to expand...
Click to collapse
If superuser is compiled in, you can only really remove the su binary, unless developer options has an off switch
Sent from my Nexus 5 using Tapatalk
dandwhelan said:
Hello, I am looking for a custom ROM which has not been rooted and has lots of customizable options. Does such a thing exist?
The only reason I do not want a rooted version is because my barclays banking does not work with root. Ive been using Purity for the past year but after checking out stock 4.4.3 I decided to try the banking app as I had chance. It makes life so much easier
So yeah basically, is there a none root custom rom with all the features for customizing ect...
Click to expand...
Click to collapse
Like @rootSU already said, there are other options than choosing a rom without SuperUser. There are Xposed and Cydia Modules to hide Root for some apps. RootCloak.
http://repo.xposed.info/module/com.devadvance.rootcloak
http://forum.xda-developers.com/showthread.php?t=2607273
rootSU said:
You can remove root from any rom. /system/bin/su or system/xbin/su
ROMs like Slimkat can turn root on and off.
There are also other options to hide root. Root cloak for example
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Cheers for the reply. I have used Root Claok before but this no longer supports the Barclays Pingit and Banking App. Im not going start rambling on about how its re-dic (I know) I might try out Slimkat, checked out these locations on my phone and I cannot find them. The only reason I'm currently on root is because when on TWRP I was half asleep and agreed to root instead of reboot. Anyway I have managed to remove root from the superuser app. cheers for the tips. Might go back to purity and un-root it
dandwhelan said:
Cheers for the reply. I have used Root Claok before but this no longer supports the Barclays Pingit and Banking App. Im not going start rambling on about how its re-dic (I know) I might try out Slimkat, checked out these locations on my phone and I cannot find them. The only reason I'm currently on root is because when on TWRP I was half asleep and agreed to root instead of reboot. Anyway I have managed to remove root from the superuser app. cheers for the tips. Might go back to purity and un-root it
Click to expand...
Click to collapse
You can only see inside /system with a file manager with root access
Sent from my Nexus 5 using Tapatalk
Probably easier to unroot through super su
Sent from my Nexus 5 using Tapatalk
So yeh i wiped and thought i had a rom to install, didnt though. mistake on my part i know. can someone link or help me install the correct drivers so i can get adb working to push a rom so i can my phone up and running again?
when i boot into recovery it is only showing up as 'AOSP ON HAMMERHEAD' with the little yellow error triangle in device manager.
like i said i just need help getting a rom pushed on my phone
EDIT: im thinking about just restore stock unroot cause you can just do it from fastboot. is there anyway to get my data off before that or would you suggest just pushing a rom?
Google 15 second adb install xda. Should be everything you need. Then push a rom onto your device.
Sent from my Nexus 5 using XDA Free mobile app
---------- Post added at 05:14 PM ---------- Previous post was at 05:08 PM ----------
jd1639 said:
Google 15 second adb install xda. Should be everything you need. Then push a rom onto your device.
Edit, if you get adb working you could pull your sdcard. Personally I think it's easier to get a rom working and then using mtp to drag and drop what you want off your sdcard to your pc
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Google 15 second adb install xda. Should be everything you need. Then push a rom onto your device.
Sent from my Nexus 5 using XDA Free mobile app
---------- Post added at 05:14 PM ---------- Previous post was at 05:08 PM ----------
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
yeah i used that but it still says 'AOSP ON HAMMERHEAD' in device manager when im in recovery. will that matter at all?
they all also explainhow to use adb and get it running with a rom. is there anything special i need to do for my situation?
fergdizzle9090 said:
yeah i used that but it still says 'AOSP ON HAMMERHEAD' in device manager when im in recovery. will that matter at all?
they all also explainhow to use adb and get it running with a rom. is there anything special i need to do for my situation?
Click to expand...
Click to collapse
Right click on that>update driver software>browse my pc>let me pick from the list of drivers>android adb interface
varuntis1993 said:
Right click on that>update driver software>browse my pc>let me pick from the list of drivers>android adb interface
Click to expand...
Click to collapse
yeah everytime i try and do that it says it doesnt work. the 15 second tool worked for when it was booted in a rom but now its in recovery and the driver isnt correct. might just completely wipe and unroot and go back stock...
fergdizzle9090 said:
yeah everytime i try and do that it says it doesnt work. the 15 second tool worked for when it was booted in a rom but now its in recovery and the driver isnt correct. might just completely wipe and unroot and go back stock...
Click to expand...
Click to collapse
Restart both the devices and try again. If that doesn't work again then
download the latest google drivers and try with them.
edit-http://developer.android.com/sdk/win-usb.html
But since its working for you when android is booted I see no reason for it not working in recovery mode. obv it needs to be installed correctly. Btw what recovery r u using?
varuntis1993 said:
Restart both the devices and try again. If that doesn't work again then
download the latest google drivers and try with them.
edit-http://developer.android.com/sdk/win-usb.html
But since its working for you when android is booted I see no reason for it not working in recovery mode. obv it needs to be installed correctly. Btw what recovery r u using?
Click to expand...
Click to collapse
TWRP. i updated to the latest one to install 4.4.4 and now when i try to install catcalysm it fails. im thinking it may be a source of some other issues
ended up using a toolkit to install a universal driver and wipe out all others. recognized it from there. thanks! now back to my original issues..
fergdizzle9090 said:
ended up using a toolkit to install a universal driver and wipe out all others. recognized it from there. thanks! now back to my original issues..
Click to expand...
Click to collapse
When you type
Code:
adb devices
does it list your device?
theesotericone said:
When you type
Code:
adb devices
does it list your device?
Click to expand...
Click to collapse
yep it does now after i tried several different drivers. that was my problem initially is that wasnt showing up when in recovery. now im onto my next problem to figure out why i cant make outgoing calls... i think its a sprint/4.4.4 issue...
fergdizzle9090 said:
Wiped with no rom to install, only have recovery now...
Click to expand...
Click to collapse
A clean slate. I love it. A little too much some times, I think.
nice
Just wondering if anyone had any luck with the workarounds for our device? If so please post what ROM's work and which workaround worked. Also post whether the boot loader needed to be locked or not. I have been working since I found the official app last night, but So far no luck. I'm trying many custom ROMS as I don't really want another stock ROM, Hence why I am rooted. Anyway, any help would be boss! Thanks!
For me, it just has Google Play Services crashing whenever I try to add a card. This was after disabling SuperSU.
walkwithdeath said:
Just wondering if anyone had any luck with the workarounds for our device? If so please post what ROM's work and which workaround worked. Also post whether the boot loader needed to be locked or not. I have been working since I found the official app last night, but So far no luck. I'm trying many custom ROMS as I don't really want another stock ROM, Hence why I am rooted. Anyway, any help would be boss! Thanks!
Click to expand...
Click to collapse
did you try stock rooted thats my next attempt after I charge phone up a little. I been reading up and it seems stock rooted with supersu removing stock or xposed rootcloak work. Just nandroid and try it out nobody says you have to use it but if that works it may give us an insight on what to target for getting it to work
Yes, so far I believe thats what I read. At this point I have read a lot. The two methods involve unchecking enable superuser in supersu and then the root cloak method via xposed. Neither have worked in every custom ROM so far. I may try CM nightlies tho.
just an fyi i tried stock for the hell of it and it worked with just unchecking supersu root option. Maybe a buildprop edit to trick it to think its a basic stock rom may work
http://forum.xda-developers.com/oneplus-one/development/rom-cyanogen-os-12-1-rooted-cleaned-t3187016
Update. I have found a mothod that works, haven't tried the "pay" part, but I have Android Pay activated and working. The above link is the a rooted ROM with some mods that works. Its CM OS 12.1 and seems pretty stable, etc.
The method I used
1 Bootloader is locked. Just so you know. But all operations will function that you need.
1 Install ROM (use the link above for details, NO GAPPS NEEDED)
2 DENY ROOT/SUPERSU installation.
3 Boot ROM as normal
4 Open SuperSU
5 Click Enable SuperSU (This disables it/Unchecks the box. You will see a prompt saying uninstalling SuperSU)
6 Reboot
7 Install Google Play Services then Android Pay (APK's found on the web, GPS is 8.1.13)
8 Open Android Pay and follow prompts to install cards
9 Open SuperSU and recheck Enable SuperSU
At this point the phone is rooted and Android Pay is set up. I tried to do another card but got the same old error "cannot verify Android bs."
My conclusions:
If the ROM has a root option under developer settings, then Android Pay will not work. This ROM does NOT have that but instead has SuperSU installed. ROMS that have both will NOT function, I tried 3 or 4 today that did not work. I imagine they need to be CM based at this time as well. I bet someone better than me will come up with a better solution. This combination works for me. If anyone needs help, PM me. Also, If anyone has anything to add, Please do! Thanks!!!
walkwithdeath said:
http://forum.xda-developers.com/oneplus-one/development/rom-cyanogen-os-12-1-rooted-cleaned-t3187016
Update. I have found a mothod that works, haven't tried the "pay" part, but I have Android Pay activated and working. The above link is the a rooted ROM with some mods that works. Its CM OS 12.1 and seems pretty stable, etc.
The method I used
1 Bootloader is locked. Just so you know. But all operations will function that you need.
1 Install ROM (use the link above for details, NO GAPPS NEEDED)
2 DENY ROOT/SUPERSU installation.
3 Boot ROM as normal
4 Open SuperSU
5 Click Enable SuperSU (This disables it/Unchecks the box. You will see a prompt saying uninstalling SuperSU)
6 Reboot
7 Install Google Play Services then Android Pay (APK's found on the web, GPS is 8.1.13)
8 Open Android Pay and follow prompts to install cards
9 Open SuperSU and recheck Enable SuperSU
At this point the phone is rooted and Android Pay is set up. I tried to do another card but got the same old error "cannot verify Android bs."
My conclusions:
If the ROM has a root option under developer settings, then Android Pay will not work. This ROM does NOT have that but instead has SuperSU installed. ROMS that have both will NOT function, I tried 3 or 4 today that did not work. I imagine they need to be CM based at this time as well. I bet someone better than me will come up with a better solution. This combination works for me. If anyone needs help, PM me. Also, If anyone has anything to add, Please do! Thanks!!!
Click to expand...
Click to collapse
basicaly what I was saying it works on stock ONEPlus roms only it seems and you just have to deny root when adding cards. I tried to use lil while ago but it said my cards were not available yet to use with Android Pay
Just wanted to chime in with my post from another thread to consolidate threads:
I am running COS 12.1, rooted, with an unlocked bootloader. I recently upgraded to Android Pay after using Google Wallet for NFC payments for years on my old GS4 and my OnePlus One.
At first, I was unable to add my payment card due to being rooted. Easily fixed, I unrooted using SuperSU to do a full unroot and was able to add my card and complete the app setup.
The showstopper is that whenever I try to use it at a merchant, I end up with a screen that says Confirm your password - you must unlock to use Android Pay. No matter how many times I enter my password it just keeps asking over and over. I disabled the quick unlock feature under lock screen settings just in case that was the issue, but it made no difference. An ongoing support case with Google just came back with the following:
"The specific error message that you saw means that your device can't support Android Pay's advanced security. It seems that the phone manufacturer has modified the operating system to the point where it is no longer compatible with our software. You may want to use Android Pay on a different device for the most secure payments."
just as an update i re-flashed stock rom and realized using xposed and make any additional changes to the system folder causes it not to work whether I have supersu checked off or not. Now with that said i have it working fine with stock and having supersu loaded from twrp and play store nothing else. I also set up a tasker command to uncheck supersu prior to me using Android Pay. 1 click I guess I waas being lazy
Is your bootloader unlocked?
Sent from my Nexus 10 using XDA Premium 4 mobile app
playya said:
just an fyi i tried stock for the hell of it and it worked with just unchecking supersu root option. Maybe a buildprop edit to trick it to think its a basic stock rom may work
Click to expand...
Click to collapse
I have tried disabling root and root cloak. I am on Exodus rom and it has "morph mode" where I tried both methods in Exodus mode and AOSP mode. If this helps narrow down the problem.
For me on Exodus (haven't tried any of the morph modes), the unlocked bootloader seems to be the culprit. Hopefully someone figures out a workaround.
Hurricane Andrew said:
Is your bootloader unlocked?
Sent from my Nexus 10 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes... if you are asking me
---------- Post added at 02:29 PM ---------- Previous post was at 02:27 PM ----------
Digil said:
For me on Exodus (haven't tried any of the morph modes), the unlocked bootloader seems to be the culprit. Hopefully someone figures out a workaround.
Click to expand...
Click to collapse
bootloader is not the problem. Android Pay is looking for more than likely specific files in your system that are missing in AOSP or custom roms. I flashed stock and as long as I uncheck SuperSu its been working fine for me. I have added several cards over the past week
Deleted
---------- Post added at 10:57 PM ---------- Previous post was at 10:56 PM ----------
playya said:
yes... if you are asking me
---------- Post added at 02:29 PM ---------- Previous post was at 02:27 PM ----------
bootloader is not the problem. Android Pay is looking for more than likely specific files in your system that are missing in AOSP or custom roms. I flashed stock and as long as I uncheck SuperSu its been working fine for me. I have added several cards over the past week
Click to expand...
Click to collapse
What Rom are you Using ?!?
Hurricane Andrew said:
Is your bootloader unlocked?
Sent from my Nexus 10 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No need for a locked bootloader on 1+ it works fine but strictly with stock
Skitts said:
Deleted
---------- Post added at 10:57 PM ---------- Previous post was at 10:56 PM ----------
What Rom are you Using ?!?
Click to expand...
Click to collapse
I am running a stock rooted rom I found here. I tried to do it with Calkulins rom but it failed install for me. also no xposed or anything extra in system that may not need to be there. Its been working fine like this for a week now. I just used it again last night. I turn off SuperSu prior to using just for good measure
playya said:
I am running a stock rooted rom I found here. I tried to do it with Calkulins rom but it failed install for me. also no xposed or anything extra in system that may not need to be there. Its been working fine like this for a week now. I just used it again last night. I turn off SuperSu prior to using just for good measure
Click to expand...
Click to collapse
Thank Man I'll Give it A try see if I get the same results. As Of right now I'm Running Blisspop And I keep On getting the error.
Skitts said:
Thank Man I'll Give it A try see if I get the same results. As Of right now I'm Running Blisspop And I keep On getting the error.
Click to expand...
Click to collapse
So was I and I left them for crdroid which has a lot less issues. But I flashed stock to try out Android Pay and I have been surprisingly pleased. It will work just don't flash SuperSU but use built in version or update via TWRP option if asked after flashing rom
Does anyone have the apk for the version of Google Wallet right before the update to Android Pay? I'd like to at least have something that works.
rbrugman said:
Does anyone have the apk for the version of Google Wallet right before the update to Android Pay? I'd like to at least have something that works.
Click to expand...
Click to collapse
android authority has it and if you do a google search for it you will find it. also know that you have to un-tick auto updates in Google Play. I wiped data in Google play, Google Play Services prior to installing the now outdated version. I had to do this so that when I loaded the older version it will try and update the moment you try and set it up.