Whoever gets the update tomorrow. PULL THE UPDATE ZIP!
If I get it I will and post it, for the flat variant. I have ready done this from my wife's sprint edge variant.
Here is how you do it:
You have to be on the latest firmware and not rooted.
If you get the update notification.
Download it, but do not install it.
Then root your device. DO NOT WIPE IT
The update.zip is located in /data/fota/update.zip
Pull it using adb or use root Explorer to move it to the root of your SDCard and then your pc.
Please wait for someone to verify it works before flashing the update or unroot.
Come on people, support the community!
billydroid said:
Whoever gets the update tomorrow. PULL THE UPDATE ZIP!
If I get it I will and post it, for the flat variant. I have ready done this from my wife's sprint edge variant.
Here is how you do it:
You have to be on the latest firmware and not rooted.
If you get the update notification.
Download it, but do not install it.
Then root your device. DO NOT WIPE IT
The update.zip is located in /data/fota/update.zip
Pull it using adb or use root Explorer to move it to the root of your SDCard and then your pc.
Please wait for someone to verify it works before flashing the update or unroot.
Come on people, support the community!
Click to expand...
Click to collapse
what is the root of the sd card?
I will if I get
Sent from my Samsung SM-G935T using XDA Labs
comptonhubbard said:
what is the root of the sd card?
Click to expand...
Click to collapse
Jsut not in a folder. But that really doesn't matter unless you are trying to flash it from your SDCard
billydroid said:
Jsut not in a folder. But that really doesn't matter unless you are trying to flash it from your SDCard
Click to expand...
Click to collapse
Since it tried to register too late, I cant do this (would have done so otherwise - I have restored to stock and re-rooted so many times I could do it in my sleep).
Now I will be looking forward to getting my hands on the ODINable download. I will test it right off and contribute feedback here after.
PS - just looked at the terms and conditions - they wouldn't like this at all lol.
PS2 - maybe they have seen these posts and pulled the plug - server down and Beta call in number down also - have bad feeling about this - could that inadvertently been sending out unlocked bootloaders??
I'm waiting for this too.
Sent from my SM-G935U using XDA-Developers mobile app
gaww said:
Since it tried to register too late, I cant do this (would have done so otherwise - I have restored to stock and re-rooted so many times I could do it in my sleep).
Now I will be looking forward to getting my hands on the ODINable download. I will test it right off and contribute feedback here after.
PS - just looked at the terms and conditions - they wouldn't like this at all lol.
PS2 - maybe they have seen these posts and pulled the plug - server down and Beta call in number down also - have bad feeling about this - could that inadvertently been sending out unlocked bootloaders??
Click to expand...
Click to collapse
Yeah no one has got it today. This is starting to look bad
I tweeted at @TmobileHelp, they say it's coming.
billydroid said:
Yeah no one has got it today. This is starting to look bad
I tweeted at @TmobileHelp, they say it's coming.
Click to expand...
Click to collapse
just got through to the galaxy beta program number 1-866-609-3271, currently on hold, all the representatives are currently assisting other customers guess everyone is calling lol ill post any information i get *fingers crossed*
---------- Post added at 09:01 PM ---------- Previous post was at 08:48 PM ----------
Dennis Frogman said:
just got through to the galaxy beta program number 1-866-609-3271, currently on hold, all the representatives are currently assisting other customers guess everyone is calling lol ill post any information i get *fingers crossed*
Click to expand...
Click to collapse
Alright just got off the phone with the customer service representative, they said that they are working with t-mobile as i type this message to get this issue resolved and yes we arev still getting the update. They also said that it's not an issue on Samsung side but rather a problem with t-mobile's server's so guess were gonna have to wait till they get thing's resolved. I asked if it would be fixed today and he said he can't give me a timeline of how or when it will be fixed so stay confident people we are getting it. If you'd like to hear this information with your own ears call the number your selves !!! 1-866-609-3271
gaww said:
Since it tried to register too late, I cant do this (would have done so otherwise - I have restored to stock and re-rooted so many times I could do it in my sleep).
Now I will be looking forward to getting my hands on the ODINable download. I will test it right off and contribute feedback here after.
PS - just looked at the terms and conditions - they wouldn't like this at all lol.
PS2 - maybe they have seen these posts and pulled the plug - server down and Beta call in number down also - have bad feeling about this - could that inadvertently been sending out unlocked bootloaders??
Click to expand...
Click to collapse
this exact post is in the Verizon variants xda page. they uploaded the package.zip file before the install. I don't see it being a problem on here. If it was leaked or something and Samsung didn't release it, then I could see someone being very upset
billydroid said:
Whoever gets the update tomorrow. PULL THE UPDATE ZIP!
If I get it I will and post it, for the flat variant. I have ready done this from my wife's sprint edge variant.
Here is how you do it:
You have to be on the latest firmware and not rooted.
If you get the update notification.
Download it, but do not install it.
Then root your device. DO NOT WIPE IT
The update.zip is located in /data/fota/update.zip
Pull it using adb or use root Explorer to move it to the root of your SDCard and then your pc.
Please wait for someone to verify it works before flashing the update or unroot.
Come on people, support the community!
Click to expand...
Click to collapse
I pull it and I followed the instructions but when I copy the file over to my SD card it shows 0 bytes any suggestions
Sent from my Samsung SM-G935T using XDA Labs
besttech1450 said:
I pull it and I followed the instructions but when I copy the file over to my SD card it shows 0 bytes any suggestions
Click to expand...
Click to collapse
Copy over to your external/internal SD card and move it to your pc. That is what I've done for the tmo flat s7
I was having the same issue. Maybe because the it's encrypted?
billydroid said:
Copy over to your external/internal SD card and move it to your pc. That is what I've done for the tmo flat s7
I was having the same issue. Maybe because the it's encrypted?
Click to expand...
Click to collapse
Ok I try thanks
Sent from my Samsung SM-G935T using XDA Labs
Based on what people from the nouget thread are saying.....we're SOL on getting a .zip file
So it looks like Samsung figured out everyone was sharing the files. For some reason the saved update.zip is failing to update the firmware when it is flashed. No fix yet.
Also I got the beta software so far you aren't missing out on much. It's still not as good as the Note 7s firmware was.
ShrekOpher said:
Also I got the beta software so far you aren't missing out on much. It's still not as good as the Note 7s firmware was.
Click to expand...
Click to collapse
Opinion
ShrekOpher said:
So it looks like Samsung figured out everyone was sharing the files. For some reason the saved update.zip is failing to update the firmware when it is flashed. No fix yet.
Also I got the beta software so far you aren't missing out on much. It's still not as good as the Note 7s firmware was.
Click to expand...
Click to collapse
Do you know for sure or are you just speculating wrong info?
Sent from my SM-G935U using Tapatalk
tengtengvn said:
Do you know for sure or are you just speculating wrong info?
Sent from my SM-G935U using Tapatalk
Click to expand...
Click to collapse
There are people in the beta forums talking about it and Samsung has referred to the Terms of Service saying users are "not supposed to share the beta software". My guess is that they don't have the servers setup to have TONS of people using the software and it feeding them log files etc. That's why they limited the beta to a set number of users. Also the Beta forums that you get access to as a part of the firmware are getting loaded up with comments from people, way more than Samsung staffed to handle.
Its not an assumption that they don't want everyone using it. It is an assumption that they changed the Tmobile firmware to make it so it couldn't be shared. Its a closed beta not open to all users restricting access is a part of a closed beta.
As for the next beta update. They will be making multiple changes over the coarse of the next month and there will be multiple firmware updates pushed out, per the text you receive when you look for a beta update. There is an additional beta setting to help users schedule the installations so they don't use up all their data. Since the tmobile firmware is locked down to specific devices that are a part of the beta program that practice will most likely continue in future beta updates.
If I had to take a wild guess my bet would be that if you are not a registered beta tester you won't get the next update at all and you won't be able to side load/flash it.
ShrekOpher said:
There are people in the beta forums talking about it and Samsung has referred to the Terms of Service saying users are "not supposed to share the beta software". My guess is that they don't have the servers setup to have TONS of people using the software and it feeding them log files etc. That's why they limited the beta to a set number of users. Also the Beta forums that you get access to as a part of the firmware are getting loaded up with comments from people, way more than Samsung staffed to handle.
Its not an assumption that they don't want everyone using it. It is an assumption that they changed the Tmobile firmware to make it so it couldn't be shared. Its a closed beta not open to all users restricting access is a part of a closed beta.
As for the next beta update. They will be making multiple changes over the coarse of the next month and there will be multiple firmware updates pushed out, per the text you receive when you look for a beta update. There is an additional beta setting to help users schedule the installations so they don't use up all their data. Since the tmobile firmware is locked down to specific devices that are a part of the beta program that practice will most likely continue in future beta updates.
If I had to take a wild guess my bet would be that if you are not a registered beta tester you won't get the next update at all and you won't be able to side load/flash it.
Click to expand...
Click to collapse
Its more than that. I got the beta. But i cant even flash the pulled update.zip from my own device. They did something that corrupts if trying to copy it.
Sounds like this is dead for TMo at this point ?
@billydroid and whoever has the update.zip and is rooted
Sounds like the nougat zip needs to be adb pulled from device instead of copying it that might make a differnce because your not copying it directly to sdcard or internal its getting pullled directly to pc thus it should stop it from getting corrupted but you will still need root to pull it from fota.
Sent from my SM-G935U using XDA-Developers mobile app
Related
Hello, today I've noticed that my phone (Samsung Galaxy S2 Skyrocket) had received the updated ATT ICS (US). It downloaded successfully without any issues. At the current point, my phone is rooted with the stock ATT Gingerbread OS, with clockwork touch 5.8.1.3-hercules.tar. I never bothered to install any 3rd party unofficial ROMS because I was waiting for the official ATT ICS which apparently released today. Anyway once the download completed, my phone restarted normally and went automatically in to CWM which was expected. From there, I chose "install from zip", apply /sdcard/update.zip. Right after that I get an error message "Can't mount /sdcard/update.zip", so I click "Go Back", I then select "Mounts and storage" > mount /sdcard, and get "Error mounting /sdcard!".
I've tried doing this also with a prior version of CWM (prior to 5.8.1.3), but I've got the same issue. I've also tried to plugin my phone to my PC and looking for the update.zip, so I can manually transfer it to the root of the phone's file system, but it was not there although it downloaded. I do not have any additional external SDCARD installed.
Could I possibly get the update.zip from an official ATT hyperlink for my phone so I can manually download it on my PC and transfer it to the phone's root file system?
Is there a Fix for "Can't mount / sdcard"? I looked around but could not find an answer.
Please advise.
wait...what? release today?!?
Are you sure it's ICS and not UCLA3 yet again??
Also, I'm pretty sure you need to be on stock recovery in order for the update to work.
jarus323 said:
Hello, today I've noticed that my phone (Samsung Galaxy S2 Skyrocket) had received the updated ATT ICS (US). It downloaded successfully without any issues. At the current point, my phone is rooted with the stock ATT Gingerbread OS, with clockwork touch 5.8.1.3-hercules.tar. I never bothered to install any 3rd party unofficial ROMS because I was waiting for the official ATT ICS which apparently released today. Anyway once the download completed, my phone restarted normally and went automatically in to CWM which was expected. From there, I chose "install from zip", apply /sdcard/update.zip. Right after that I get an error message "Can't mount /sdcard/update.zip", so I click "Go Back", I then select "Mounts and storage" > mount /sdcard, and get "Error mounting /sdcard!".
I've tried doing this also with a prior version of CWM (prior to 5.8.1.3), but I've got the same issue. I've also tried to plugin my phone to my PC and looking for the update.zip, so I can manually transfer it to the root of the phone's file system, but it was not there although it downloaded. I do not have any additional external SDCARD installed.
Could I possibly get the update.zip from an official ATT hyperlink for my phone so I can manually download it on my PC and transfer it to the phone's root file system?
Is there a Fix for "Can't mount / sdcard"? I looked around but could not find an answer.
Please advise.
Click to expand...
Click to collapse
O.K., your join date is May 2012, you only have 1 post and I'm to believe you have a rooted device, ready to upgrade to ICS, yet what really sticks out is that this is the only time you've posted.
Well, the file that downloaded file was way over 200megs, probably 250-280 and right after, the the download, my phone restarted going to CWM. I may just backup my data and restore everything to factory so see the update complete. Not sure if anyone had the download available. Not sure if the location matters, I'm located in South Florida.
Thanks for the prompt reply's btw.
Yea regardless, as skrambled said, nothing is going to work unless you're on the stock recovery. Think about it, its an official update and cwm is a custom (unofficial) recovery.
Sent from my SAMSUNG-SGH-I727 using XDA
I got a prompt for an update was well today, it took a while to download and same thing happened, it went to CW on restart, I am also just rooted, no custom rom installed.
upload the update.zip and post here? i'm sure someone can verify the build it is and would be good info to have.
I'm doubting soooo much right now. When a reliable source confirms, or u post a screen shot with a different build number, then ill believe
just checked....
i have no update on my skyrocket...Boston mass area....
dlpatter said:
O.K., your join date is May 2012, you only have 1 post and I'm to believe you have a rooted device, ready to upgrade to ICS, yet what really sticks out is that this is the only time you've posted.
Click to expand...
Click to collapse
I decided to join because of the issue I'm having. Most of the time I read what others had to say on this forum and others.. I'm not too big on phone "tweaking" etc..., but I would surly like to get this update to work which is why I have joined. There are plenty of threads and other sites that offer step by step instructions of how to root a phone etc...So I would not be surprised if a member of one post has a rooted phone. Just Google "Root ATT Skyrocket".
my brothers completely stock skyrocket (no root, no nothing) received a notification of an update today.. it was just 2.3.6
Decer said:
my brothers completely stock skyrocket (no root, no nothing) received a notification of an update today.. it was just 2.3.6
Click to expand...
Click to collapse
That would make sense.
Decer said:
my brothers completely stock skyrocket (no root, no nothing) received a notification of an update today.. it was just 2.3.6
Click to expand...
Click to collapse
Was it between 250-280megs?
If it was, maybe it'll be good to delete this entire posting to not cause too much confusion.
jarus323 said:
I decided to join because of the issue I'm having. Most of the time I read what others had to say on this forum and others.. I'm not too big on phone "tweaking" etc..., but I would surly like to get this update to work which is why I have joined. There are plenty of threads and other sites that offer step by step instructions of how to root a phone etc...So I would not be surprised if a member of one post has a rooted phone. Just Google "Root ATT Skyrocket".
Click to expand...
Click to collapse
2.3.6 verified, My most humble apologies to you sir....
---------- Post added at 01:20 PM ---------- Previous post was at 01:16 PM ----------
jarus323 said:
I decided to join because of the issue I'm having. Most of the time I read what others had to say on this forum and others.. I'm not too big on phone "tweaking" etc..., but I would surly like to get this update to work which is why I have joined. There are plenty of threads and other sites that offer step by step instructions of how to root a phone etc...So I would not be surprised if a member of one post has a rooted phone. Just Google "Root ATT Skyrocket".
Click to expand...
Click to collapse
There have been so many false sightings and ICS treads started that it makes one leery of any mention of a OTA update. I want it sooooooooooo bad, because I know that once it's released, the devs will take it and pimp it out for me.....
dlpatter said:
2.3.6 verified, My most humble apologies to you sir....
---------- Post added at 01:20 PM ---------- Previous post was at 01:16 PM ----------
There have been so many false sightings and ICS treads started that it makes one leery of any mention of a OTA update. I want it sooooooooooo bad, because I know that once it's released, the devs will take it and pimp it out for me.....
Click to expand...
Click to collapse
Same here man.
dlpatter said:
O.K., your join date is May 2012, you only have 1 post and I'm to believe you have a rooted device, ready to upgrade to ICS, yet what really sticks out is that this is the only time you've posted.
Click to expand...
Click to collapse
what does any of that have to do with him receiving the update notice? and I got one too.
jarus323 said:
Was it between 250-280megs?
If it was, maybe it'll be good to delete this entire posting to not cause too much confusion.
Click to expand...
Click to collapse
Was at 98% completed installation before i saw it, so my brother is probably the only person who could answer that question.. and i highly doubt he even cared enough to look.
InSaiyanone said:
what does any of that have to do with him receiving the update notice? and I got one too.
Click to expand...
Click to collapse
I did apologize for my rushed opinion, I now apologize to you my friend....
Originally, I got hyped up about this update because I knew that around this time, we all should be expecting the official ATT ICS, and since my friend T has a huuuuuuge hard-on for Android phones, he was sure that the updated that downloaded on my phone was ICS, so I blame HIM for giving me a false positive! If you are reading this T, it's ALL YOUR FAULT! See how many people had to click on this pointless thread!
I was supposed to be part of the soak but for some reason my phone is invisible to the Moto update servers and they cannot push the update to me. I have the update file someone gave me a link to download. I have two questions about how to install it.
1. Since I am rooted can I just put it where Moto would have downloaded it to and then my phone will update it like it got the OTA?
or
2. If I install it off the SD card will it just do recovery first and then display injured android man, and then have to reselect the zip package again to finish instlling the update?
I would prefer method 1 if possible. If one of the devs or a knowledgeable person could respond I would appreciate it. I'll give Moto about six more hours to get this straightened out, otherwise I am tired of waiting to get my Atrix 2 onto ICS.
Hi. I don't suppose the end result would be different, whatever method you choose.
athani said:
Hi. I don't suppose the end result would be different, whatever method you choose.
Click to expand...
Click to collapse
Where does moto put the zip file so I can try putting it where the OTA would have downloaded to? Then when I go to check for update it should say an update is ready for installing. Do they put it in the cache directory? Someone who knows please let me know. Thanks.
athani said:
Hi. I don't suppose the end result would be different, whatever method you choose.
Click to expand...
Click to collapse
AFAICT this seems true, you I could run a leak#2/soak based ROM as a second system (first system too?) with boot menu manager by following the guides:
http://forum.xda-developers.com/showthread.php?t=1779968
http://forum.xda-developers.com/showthread.php?t=1882335
jboxer said:
Where does moto put the zip file so I can try putting it where the OTA would have downloaded to? Then when I go to check for update it should say an update is ready for installing. Do they put it in the cache directory? Someone who knows please let me know. Thanks.
Click to expand...
Click to collapse
Yes, it is /cache... but I think you also need the .crc file of the same name along with the actual .zip - not positive though. And, it can take a little while for it to recognize it - but I have done it that way, by putting it in the cache folder - also, it will disappear if you reboot.
But, you do know what you are doing, right? There is no fxz yet...
---------- Post added at 08:17 AM ---------- Previous post was at 08:12 AM ----------
Edit.. since it's the same files as leak#2.. for the .crc file, you could just make your own if you don't have it:
-Just create a new blank file with notepad++
-Add this as the first and only line (no blank lines after)
Code:
3114145323
-Then, save it as Blur_Version.55.13.25.MB865.ATT.en.US.crc
alteredlikeness said:
Yes, it is /cache... but I think you also need the .crc file of the same name along with the actual .zip - not positive though. And, it can take a little while for it to recognize it - but I have done it that way, by putting it in the cache folder - also, it will disappear if you reboot.
But, you do know what you are doing, right? There is no fxz yet...
---------- Post added at 08:17 AM ---------- Previous post was at 08:12 AM ----------
Edit.. since it's the same files as leak#2.. for the .crc file, you could just make your own if you don't have it:
-Just create a new blank file with notepad++
-Add this as the first and only line (no blank lines after)
Code:
3114145323
-Then, save it as Blur_Version.55.13.25.MB865.ATT.en.US.crc
Click to expand...
Click to collapse
Yes, I know what I am doing. I used to develop roms for LG P999 but have not played around with my Atrix much. LG does their OTA updates very differently and downloads them in pieces all over the place so no way to use the method I am suggesting for the Atrix. I don't care about being able to fxz back as I just want the phone on official ICS; but I do appreciate your caveat. Thanks for the reply.
If anyone has the .crc file please upload somewhere so I can grab it. Thanks.
jboxer said:
Yes, I know what I am doing. I used to develop roms for LG P999 but have not played around with my Atrix much. LG does their OTA updates very differently and downloads them in pieces all over the place so no way to use the method I am suggesting for the Atrix. I don't care about being able to fxz back as I just want the phone on official ICS; but I do appreciate your caveat. Thanks for the reply.
If anyone has the .crc file please upload somewhere so I can grab it. Thanks.
Click to expand...
Click to collapse
I know you know what you are doing.. just had to throw that in there..
Here's the .crc file from the last leak from 9/5/12... should be the same as the soak one: https://dl.dropbox.com/u/61960599/Leak_09.05.12/Blur_Version.55.13.25.MB865.ATT.en.US.crc
alteredlikeness said:
I know you know what you are doing.. just had to throw that in there..
Here's the .crc file from the last leak from 9/5/12... should be the same as the soak one: https://dl.dropbox.com/u/61960599/Leak_09.05.12/Blur_Version.55.13.25.MB865.ATT.en.US.crc
Click to expand...
Click to collapse
Thanks. I will give them a few hours to get to work and see if my phone is visible to the update servers now that I have done an FDR as they requested. If so, I will just let the OTA do its thing. If not I will manually update my phone.
Also I do not think you can be rooted to update the check will prevent you from updating, also you have to be as close as stock as you can..... Meaning all bloat must be unfroze.....
One more note there is a Q&A section now so try to post questions there.....
jboxer said:
I was supposed to be part of the soak but for some reason my phone is invisible to the Moto update servers and they cannot push the update to me. I have the update file someone gave me a link to download. I have two questions about how to install it.
1. Since I am rooted can I just put it where Moto would have downloaded it to and then my phone will update it like it got the OTA?
or
2. If I install it off the SD card will it just do recovery first and then display injured android man, and then have to reselect the zip package again to finish instlling the update?
I would prefer method 1 if possible. If one of the devs or a knowledgeable person could respond I would appreciate it. I'll give Moto about six more hours to get this straightened out, otherwise I am tired of waiting to get my Atrix 2 onto ICS.
Click to expand...
Click to collapse
Can you share the link of the update file?
Thanks
jboxer said:
Thanks. I will give them a few hours to get to work and see if my phone is visible to the update servers now that I have done an FDR as they requested. If so, I will just let the OTA do its thing. If not I will manually update my phone.
Click to expand...
Click to collapse
Could the fact that you're not in the US, are now unlocked and on another network have something with failure to get the OTA!?
You can be rooted. The update asserts only check for the original system files to make sure they have not been modified or deleted. It does not check for extra files like superuser.apk or busybox. Rooting is not a problem. I set superuser to OTA protect and it worked. After the update my ICS was still rooted without me having to root it.
For the person that wants the leak the OTA is leak # 2. It is exactly the same. Just find thread with download link for leak # 2 and you are good to go.
Would installing beats audio drivers using the app be considered tampering with system files? And would it prevent me from receiving a ota?
Sent from my MB865 using xda premium
athani said:
Could the fact that you're not in the US, are now unlocked and on another network have something with failure to get the OTA!?
Click to expand...
Click to collapse
No, they wanted people like that to make sure it worked. Just had to do an FDR and then was good to go. Got the OTA and on ICS now.
ramosquera said:
Can you share the link of the update file?
Thanks
Click to expand...
Click to collapse
The devs have confirmed that the soak test OTA is identical to ICS leak #2.
jboxer said:
No, they wanted people like that to make sure it worked. Just had to do an FDR and then was good to go. Got the OTA and on ICS now.
Click to expand...
Click to collapse
Sorrry but what mean FDR? because I'm in that situation: Im not in US and I have the phone unlocked, and I'm using it with other operator... Is just ended the soak test?... because the phone say me "Your phone is updated, Is not required a update in this moment" (Translated from Spanish) when I look in Settings -> About the phone -> Update, and I'm have the system version 55.13.25.MB865.ATT.en.US.
nelsonalfo said:
Sorrry but what mean FDR? because I'm in that situation: Im not in US and I have the phone unlocked, and I'm using it with other operator... Is just ended the soak test?... because the phone say me "Your phone is updated, Is not required a update in this moment" (Translated from Spanish) when I look in Settings -> About the phone -> Update, and I'm have the system version 55.13.25.MB865.ATT.en.US.
Click to expand...
Click to collapse
You have to be someone that was invited and filled out a survey about six weeks ago. If you are you need to go to the Motorola Private forum. Go see how others are requesting it (not allowed to really talk about it). FDR means Factory Data Reset and it is an option in Privacy in Settings. It erases all your user settings, app data and you are back to square one like when the phone came out of the box. For many people it was required to get what they wanted.
If you were not invited don't worry. Usually the official rollout of the OTA will come within a week of a soak test if no problems are found. It is the same as leak # 2 so just look on this forum and you can install that manually. The release is solid so I see no reason the OTA won't be going live to all AT&T Atrix 2 devices very soon.
nelsonalfo said:
Sorrry but what mean FDR? because I'm in that situation: Im not in US and I have the phone unlocked, and I'm using it with other operator... Is just ended the soak test?... because the phone say me "Your phone is updated, Is not required a update in this moment" (Translated from Spanish) when I look in Settings -> About the phone -> Update, and I'm have the system version 55.13.25.MB865.ATT.en.US.
Click to expand...
Click to collapse
I think he means Factory Data Reset.. found in settings>backup & reset (?) forgot where it was on GB, but it's in the settings.
Edit: Lol.. jboxer - I've been too slow a lot recently
alteredlikeness said:
I think he means Factory Data Reset.. found in settings>backup & reset (?) forgot where it was on GB, but it's in the settings.
Edit: Lol.. jboxer - I've been too slow a lot recently
Click to expand...
Click to collapse
I hated doing it but it was necessary for some reason. Before it my phone was invisible to the update servers. After it was and I got a push notification to begin the download. Loving ICS.
I have been notified of an update for my EK-GC120 (6ca5626c77cd.update_EK-GC120_GC120VRALL2_To_GC120VRAMC4_FWD-1.zip) is the file i pulled from the cache folder but it refuses to apply to my camera. Is there an alternate recovery available anywhere for this device? TWRP or CWM? I have posted the update here I am hoping it includes the remote viewfinder functionality that was originally missing from this version.
http://d-h.st/users/swjpilot/?fld_id=16995#files
Update: I had changed the GmsCore.apk file...luckily i had backed it up. After restoring the original file the update applied is applying....Hopefully Root will remain will post update as soon as it completes.
Update: SuperSU says it was able to restore Root Access whoohoo!
Last Update: This does finally bring the Remote Viewfinder capability to the stock camera app.
swjpilot said:
I have been notified of an update for my EK-GC120 (6ca5626c77cd.update_EK-GC120_GC120VRALL2_To_GC120VRAMC4_FWD-1.zip) is the file i pulled from the cache folder but it refuses to apply to my camera. Is there an alternate recovery available anywhere for this device? TWRP or CWM? I have posted the update here I am hoping it includes the remote viewfinder functionality that was originally missing from this version.
http://d-h.st/users/swjpilot/?fld_id=16995#files
Update: I had changed the GmsCore.apk file...luckily i had backed it up. After restoring the original file the update applied is applying....Hopefully Root will remain will post update as soon as it completes.
Update: SuperSU says it was able to restore Root Access whoohoo!
Last Update: This does finally bring the Remote Viewfinder capability to the stock camera app.
Click to expand...
Click to collapse
I give up. How did you root this device in the first place?
perlmane said:
I give up. How did you root this device in the first place?
Click to expand...
Click to collapse
ExynosAbuseAPK before the first update. You may be able to ODIN back to 4.1.1, run that tool then keep your root through the subsequent OTA's.
Where does one find 4.1.1
Sent from my SCH-I605 using XDA Premium HD app
perlmane said:
Where does one find 4.1.1
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I would try installing Kies and having it restore the firmware. It will most likely put you back on the original firmware but i don't know that for sure. Worst thing that could happen is a factory reset of your device and you stay on your current code level.
swjpilot said:
I would try installing Kies and having it restore the firmware. It will most likely put you back on the original firmware but i don't know that for sure. Worst thing that could happen is a factory reset of your device and you stay on your current code level.
Click to expand...
Click to collapse
VZW products do not support Kies firmware updates. 4.1.1 does not seem to be available anywhere for this device.
perlmane said:
VZW products do not support Kies firmware updates. 4.1.1 does not seem to be available anywhere for this device.
Click to expand...
Click to collapse
Well i saw this post as well not sure if you have been through it or not..... but this is the last thing i got for you. I have not been able to find the original firmware anywhere either myself.
http://forum.xda-developers.com/showthread.php?t=2086636
Sorry......
swjpilot said:
Well i saw this post as well not sure if you have been through it or not..... but this is the last thing i got for you. I have not been able to find the original firmware anywhere either myself.
http://forum.xda-developers.com/showthread.php?t=2086636
Sorry......
Click to expand...
Click to collapse
Since VZW does not support Kies firmware updates, I am afraid to try it. I will have to wait until someone finds the 4.1.1 release of this device and ODIN it.
Anyone still have the boot.img for the latest verizon? Even the full update will work to extract it. This is the only missing piece to extending the custom kernel to all variants.
perlmane said:
I give up. How did you root this device in the first place?
Click to expand...
Click to collapse
swjpilot said:
ExynosAbuseAPK before the first update. You may be able to ODIN back to 4.1.1, run that tool then keep your root through the subsequent OTA's.
Click to expand...
Click to collapse
If you are still around can you confirm you used the "Exynos" Abuse apk to root your Verizon GC120. The Samsung specs page for it aren't clear about whether it's an Exynos quad core using a qualcomm board or an entire qualcomm chipset/board. Thanks!
And if anyone Verizon has found a way to root the current Verizon version and/or the odin file for 4.1.1 please reply here or let me know! Thanks!
swjpilot said:
I have been notified of an update for my EK-GC120 (6ca5626c77cd.update_EK-GC120_GC120VRALL2_To_GC120VRAMC4_FWD-1.zip) is the file i pulled from the cache folder but it refuses to apply to my camera.
http://d-h.st/users/swjpilot/?fld_id=16995#files
Click to expand...
Click to collapse
That link is dead end. Can you please repost that firmware update?
Another thing I learned while I had my ATT galaxy tab 8.9 was that Samsung likes to use the same hardware in their South Korean version of their devices with cellular and in their US devices with cellular. It's almost certainly because of the LTE requirement. Wouldn't you know that such is the case with the Galaxy Camera. The South Korean version of the camera has a Qualcomm board just like the Verizon one. Maybe the firmware for it, which can be found on Sammobile at the link below, can be helpful.
http://www.sammobile.com/firmwares/1/?model=EK-KC120S&pcode=0
EDIT: To clarify more, the Korean version uses a Qualcomm 9215 baseband board with Exynos 4412 while the Verizon version (based on Samsung own specs page) uses a Qualcomm 9615 which has it's own applications processor.
CPU Z says the Verizon GC120 DOES use the Exynos 4412 (smdk4x12). It makes no mention of the Qualcomm board on Samsungs' own specs page. They don't make this easy...
Still need any Verizon build anyone has (original 4.1.1 or 4.1.2 update which should be found in /cache).
Newest JZO54K.GC120VRAMC4
Previous JZO54K.GC120VRALL2
The one in the op should then be the 4.1.2 update
twistedumbrella said:
Newest JZO54K.GC120VRAMC4
Previous JZO54K.GC120VRALL2
The one in the op should then be the 4.1.2 update
Click to expand...
Click to collapse
I know you think no one else could possibly know better than you but the link in the op leads to nothing.
Jiggity Janx said:
I know you think no one else could possibly know better than you but the link in the op leads to nothing.
Click to expand...
Click to collapse
E:V:A said that a few posts up. I dunno what your problem is, but the more specific the file name, the better chance of finding the right file. If this section were labelled "Jiggity Janx" and not "Galaxy Camera Android Development" I would be directing every post to you. It isn't, and I'm not.
Edit: Did you try editing the build.prop with the values for the old version and attempting to do a system update? I have not researched how FOTA determines eligibility, but if it is like any normal system app, it uses the system properties.
twistedumbrella said:
E:V:A said that a few posts up. I dunno what your problem is, but the more specific the file name, the better chance of finding the right file. If this section were labelled "Jiggity Janx" and not "Galaxy Camera Android Development" I would be directing every post to you. It isn't, and I'm not.
Click to expand...
Click to collapse
edited out...
You can still likely see what was written in your thread quote notification but it doesnt need to be hashed out here.
Jiggity Janx said:
My problem here starts and ends with you. You cant expect to come across the way you do belittleing or correcting everyone every chance you get and then wonder why someone responds that way to something that appears to be a comment directed at the very last thing stated in the post immediately before yours. You dont get to have it both ways and then act innocent and deflect when you are called out on it.
Click to expand...
Click to collapse
It isn't about feelings, its about development.
Did you try editing the build.prop with the values for the old version and attempting to do a system update? I have not researched how FOTA determines eligibility, but if it is like any normal system app, it uses the system properties.
twistedumbrella said:
It isn't about feelings, its about development.
Did you try editing the build.prop with the values for the old version and attempting to do a system update? I have not researched how FOTA determines eligibility, but if it is like any normal system app, it uses the system properties.
Click to expand...
Click to collapse
Github/Sourcforge - post technical information for development, no interaction or FEELINGS required
XDA - development FORUM that requires HUMAN interaction
Now....
I appreciate the robotic side of you not taking anything to heart and continuing to want to assist. Unfortunately I have to return the model I received as I immediately noticed it had the vzw demo app on it and that the screen wouldn't time out. That means it was a verizon floor model and is unusable as intended. I am returning that one for a full refund but already have another on the way that I have been guaranteed does not have that problem (for $25 less even).
So long story short I am only willing to mess with the files so much. I know one wrong move with the build.prop could cause it not to boot and without a way to restore am not willing to take that chance with one I have to return. I will be able to do more than pull files from the other one once I receive it (and have time).
Thank you again for assisting us all with development on this device.
Jiggity Janx said:
Github/Sourcforge - post technical information for development, no interaction or FEELINGS required
XDA - development FORUM that requires HUMAN interaction
Now....
I appreciate the robotic side of you not taking anything to heart and continuing to want to assist. Unfortunately I have to return the model I received as I immediately noticed it had the vzw demo app on it and that the screen wouldn't time out. That means it was a verizon floor model and is unusable as intended. I am returning that one for a full refund but already have another on the way that I have been guaranteed does not have that problem (for $25 less even).
So long story short I am only willing to mess with the files so much. I know one wrong move with the build.prop could cause it not to boot and without a way to restore am not willing to take that chance with one I have to return. I will be able to do more than pull files from the other one once I receive it (and have time).
Thank you again for assisting us all with development on this device.
Click to expand...
Click to collapse
Look at the number of developers who have left xda butt-hurt about some comment a nameless, faceless text blob made about them because of how they read it. The device suffers, the users suffer, and some kid is up in his room crying about a hobby gone wrong.
As for the rollback, it was only theory anyway so if there is any doubt about what to change its better to find an alternative. If you could get images of the partitions from stock condition, it is possible to build the install. At least that is all done off the device where it won't corrupt anything. You could root, get the system, data, cache, and boot then merge those with the Korean release to fill in the missing parts. To the best of my knowledge, the bootloader and such are not region specific. That should be verified first, though, because you can't go back later.
Did anyone else get a pop-up for a new OTA update today? I'm running NI2 and the new one looks to be NK2. Google doesn't return much in the way of results for something coming today/recently. There's not much on Verizon's site either: http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-galaxy-s5-12-16-14.pdf All it lists is a VPN fix, SD card fix, and replacing ISIS with Softcard. It does not appear to be Lollipop
Hopefully flashing the kernel to NCG rooting and then returning to the current kernel still will work. I can download the files if someone can explain how to extract the kernel.
I too just received this update. Going to wait don't want to lose root
I got the update and applied it. Lost root (knew I would), but everything else seems fine.
I don't know how to extract the kernel though. Hopefully others take notice and help you or just provide the process and files for the masses.
firestorm126 said:
Did anyone else get a pop-up for a new OTA update today? I'm running NI2 and the new one looks to be NK2. Google doesn't return much in the way of results for something coming today/recently. There's not much on Verizon's site either: http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-galaxy-s5-12-16-14.pdf All it lists is a VPN fix, SD card fix, and replacing ISIS with Softcard. It does not appear to be Lollipop
Hopefully flashing the kernel to NCG rooting and then returning to the current kernel still will work. I can download the files if someone can explain how to extract the kernel.
Click to expand...
Click to collapse
Also just got the update on my Verizon GS5.
Appears to be a small update as the download and install did not take as long as other major updates.
Verizon still at 4.4.4
Unable to find any reference to the change log via a google search.
Anyone have a change log?
TL
Still amazes me after all these years how quick people are to install updates. I don't touch them with a ten foot pole till i find out 100% what's in them lol.
gnader said:
I got the update and applied it. Lost root (knew I would), but everything else seems fine.
I don't know how to extract the kernel though. Hopefully others take notice and help you or just provide the process and files for the masses.
Click to expand...
Click to collapse
use terminal emulator or adb (just need root) - for system and kernel dump
Code:
su
dd if=dev/block/mmcblk0p15 of=/mnt/sdcard/boot.img
dd if=dev/block/mmcblk0p23 of=/mnt/sdcard/system.img
Seems to be a small and non-critical update. I'll probably skip on this and wait for lollipop.
Does it finally fix BT bugs?
radpp16 said:
Does it finally fix BT bugs?
Click to expand...
Click to collapse
i never had a "BT" bug lol
elliwigy said:
i never had a "BT" bug lol
Click to expand...
Click to collapse
Probably not as its not mentioned.
radpp16 said:
Does it finally fix BT bugs?
Click to expand...
Click to collapse
I've had a few skips here and there, but occurances vary greatly depending on the app, BT device, and distance. 90%, though, is problem free.
I just updated lost root of course, used the towleroot/odin flash method and put the NI2 kernal back on, phone says I am still up to date with NK2, and finds no new updates. Not sure if this is actually the case, I am still new to all of this. But I do have root access back now so..
you would have to odin back to ncg kernal, root then odin nk2 kernel back once and if its available
---------- Post added at 08:40 PM ---------- Previous post was at 08:37 PM ----------
if u odin ni2 and still shows nk2 then it probably didnt work.. either way, you need to wait until someone puts out the kernal for nk2 or else u might as well stay on nk2 or just go back to ncg root install ss then flash rom of choice and then kernal of choice lol. im content where im at especially when theres no big changes at all
been waiting for this just for the SD card fix ever since the verizon tech's told me it was coming, hopefully they really did fix it.
Now the anxious waiting for it to get posted since I can't do OTA from Canada.
I will wait for it to be rootable, as I'm not willing to lose that.
That said, I've been waiting to be able to use OpenVPN over 4G/3G since I got the phone, so if this fixes the issue, it's definitely worth the update for me. I still can't believe it's taken them this long to fix the freaking issue...
BigBot96 said:
Probably not as its not mentioned.
I've had a few skips here and there, but occurances vary greatly depending on the app, BT device, and distance. 90%, though, is problem free.
Click to expand...
Click to collapse
I have not lost any BT connection, and I am running NI2 4.4.4 and a Gear 2 Neo.
I too will also likely skip this until Lollipop, and then I will only upgrade to Lollipop if/when it is launched/rootable.
BeefJerky9 said:
I will wait for it to be rootable, as I'm not willing to lose that.
Click to expand...
Click to collapse
It won't be rootable, as the past 2 updates haven't been rootable. As long as you can downgrade to NCG, that's your root method right there. You won't be able to root the new updates as they stand.
Chainfire's Super Su survival mode works great on new update.
Nevermind lost root
jodiejohn3177 said:
Sure its a paid add on but just click save root and update. Reboot update binaries and done
Click to expand...
Click to collapse
Did you do that, and keep root on NK2?
Any rooted users out there want to pull me the OTA zip file from /cache folder once it's downloaded? I'll make you guys a flashable NK2 kernel so you can do the same method as before.
http://forum.xda-developers.com/showpost.php?p=55347753&postcount=19
Sidenote: I would get it myself but I no longer have the device.
open1your1eyes0 said:
Sidenote: I would get it myself but I no longer have the device.
Click to expand...
Click to collapse
Noooooooooooo!!!!!!!!!!!!!!
Computerfreek274 Turbopop Android Pay
11/07/2015 Update This Android pay build has been updated to the newest tweaks it is running clean and wifi tether is working great. Android pay is also working 100% I just tested it at 3 stores today. Please remember this IMG has no root! however it is clean of junk and tweaked for speed with WIFI tether. For most users looking to root it was just to get wifi tether for the unlimited users. This rom is great if you like an clean stock android phone with working android pay and wifi tether.
Please ReadThis is an un-rooted Img to Support for android pay.This system image Is for users looking for a tweaked system better battery life and boosted audio and removed bloatware and Android Pay!
So if you looking to still have a tweaked and clean phone but still you like to use android pay then this img is for you. Google android pay is checking for root all the time and unlocked boot loaders. So we can only hope to get an patched ver of android pay one day for rooted phones. So for now I am going to work on this IMG it will be lean and clean with some great tweaks and boosted audio.
Whats in this IMG ?
. (SU4TL-44) Please Update the IMG files read the readme file in zip on an how to.
. Wifi Tether HotSpot
. Ios emoji REMOVED!
. Removed Junk AKA bloatware
. Internet Tweaks
. Battery Tweaks
. Android Pay Support
. Boosted Audio Boosted phone audio.
. Faster Ring time on outgoing calls
. Ad blocking Coming soon.
Whats not in this IMG ?
Root
V4A
What is next for this IMG ?
Advanced Power menu.
Better Audio
And more.
Download 1.1 Of Computerfreek274_TurboPOP_AndroidPay Here
Uploading now 11/07/2015 @ 10:15 AM Please give it an hour or so to show up on the server.
Help And Support
Please Backup data! Photos and stuff you need just in case! I am not to be help responsible for data loss or if your phone dies.
This IMG has been tested on 4 phones today 2 of them needed a full wipe to get it it boot so please keep this in mine that you may have to do a full data wipe.
Please read the readme file to upgrade your modem and kernel to the newest ver.
Preparing to install this img when coming from an img with root xposed stuff like this. 1. Uninstall xposed and any mods reboot when done. Step 2 Flash via mofo let it try and boot if it hangs on the moto screen. Hold down power enter recovery and wipe cache and reboot. 3. Download android pay and update android services VIA google market setup android pay update remove cards it will not matter at this point. Just remember android pay only supports some cards and the ones you already have on your account. Also you now have to add you google wallet credit card to android pay as wallet and android pay are split up now.
If you can not boot no matter what you do and you forgot to backup your data then flash back the img you where on and boot BACK UP YOU DATA! Then start over with step 1. and when you get to step 2. Wipe cache and data.
ill be first to jump on this, can we add cards?
Michaelmansour1997 said:
ill be first to jump on this, can we add cards?
Click to expand...
Click to collapse
Yeah supported card and cards that you already had on your account also you google wallet card can be added. Wifi tether will also still work for users that need this. Just remember there will be no root so what i add is what you get.
Would you be willing to drop in the latest AdAway host file, and then I'm personally at 98% of why I run root on my phone?
Thanks again for all the hard work!!!
Anybody else getting an "Access Denied" when clicking on the link?
GeoFX said:
Anybody else getting an "Access Denied" when clicking on the link?
Click to expand...
Click to collapse
Yes, looks like he didn't switch the permissions on the folder yet
GeoFX said:
Anybody else getting an "Access Denied" when clicking on the link?
Click to expand...
Click to collapse
i put the 30th on the forum as I am still testing. I will release soon maybe in a bit ran into a bug I had to fix.
rgerrans said:
Would you be willing to drop in the latest AdAway host file, and then I'm personally at 98% of why I run root on my phone?
Thanks again for all the hard work!!!
Click to expand...
Click to collapse
Already done will work with adaway just as you did with my rooted img's.
computerfreek274 said:
Already done will work with adaway just as you did with my rooted img's.
Click to expand...
Click to collapse
Great news, thanks!!
So now I have to choose between gravitybox and Android Pay?
gqskrub said:
So now I have to choose between gravitybox and Android Pay?
Click to expand...
Click to collapse
For me it is easy as soon as I am done testing and tweaking this build I will be back on my rooted 493 img. I can always pull out a credit card to pay for somthing not like any of us walk around with your phone only and not you real wallet.
Help and Support Update
For android Pay I will post updates on my website and on XDA and remember android pay is an unrooted tweaked img with ad blocking and more.
On my website Computerfreek.com Now has updated help and support how to setup stuff like adaway,Boot anamation, Dpi and more.
I will also be posting Pre-Release images there days before there on XDA for testing. There will also be images some custom images that will not ever be listed on here on XDA. So please check out the site it is still a work in progress but it is getting there. As of right now I did not get custom IMG listed and the newest ver is still 1.6 and it is listed below. I hope to clean up OP this week with some of the same info found on my website. I maybe doing an order page where you can order an custom IMG for a fee with 3 free Updates per IMG.
I have tried everything and cannot get audio to work at all. Is anyone else having this issue or know of a fix?
Anybody using this ROM verify it still works since the security net update?
mrkhigh said:
Anybody using this ROM verify it still works since the security net update?
Click to expand...
Click to collapse
Dude this is a old image from before we had bootloader unlock and real root. This is useless now.. do your research
Sent from my DROID Turbo using Tapatalk
computerfreek274 said:
For me it is easy as soon as I am done testing and tweaking this build I will be back on my rooted 493 img. I can always pull out a credit card to pay for somthing not like any of us walk around with your phone only and not you real wallet.
Click to expand...
Click to collapse
Right. You have to pull out SOMETHING -- whether your phone or your credit card. It's the same action. Using the phone is not really any easier.
And in the real world, no one leaves the house without their wallet. Occasionally going to work, I have left my phone at the house, but I've never left my wallet.
---------- Post added at 09:10 AM ---------- Previous post was at 09:08 AM ----------
PILLMUZIK3600 said:
Dude this is a old image from before we had bootloader unlock and real root. This is useless now.. do your research
Sent from my DROID Turbo using Tapatalk
Click to expand...
Click to collapse
Argghhh. I wish people would STOP digging up old threads. STOP IT. THIS is from September 2015! NOTHING from back then for the XT1254 is relevant for now. And Safety Net has been updated many, many times since then to block people. Anything that worked over a year ago sure wouldn't work now.
However, usually it's people who won't believe you need to pay for Sunshine to unlock their XT1254 bootloader. They dig up year old threads to ask the same question over and over like they are going to get a different answer.
Wow, you are really upset there buddy. Sorry that it bothers you. But to me, this is relevant. I have mofo root not sunshine, and i dont see the point in going through all the effort of sunshine and new roms, when moforoot works perfect. Furthermore i surely might be wrong, but i didn't see a lollipop or marshmallow ROM with these features (tweaked, tether, android pay).
I was simply asking if there was anyone who know how to get the audio working with this ROM. If you don't know, then just don't reply. What's the point in posting just to complain?
ChazzMatt said:
Right. You have to pull out SOMETHING -- whether your phone or your credit card. It's the same action. Using the phone is not really any easier.
And in the real world, no one leaves the house without their wallet. Occasionally going to work, I have left my phone at the house, but I've never left my wallet.
---------- Post added at 09:10 AM ---------- Previous post was at 09:08 AM ----------
Argghhh. I wish people would STOP digging up old threads. STOP IT. THIS is from September 2015! NOTHING from back then for the XT1254 is relevant for now. And Safety Net has been updated many, many times since then to block people. Anything that worked over a year ago sure wouldn't work now.
However, usually it's people who won't believe you need to pay for Sunshine to unlock their XT1254 bootloader. They dig up year old threads to ask the same question over and over like they are going to get a different answer.
Click to expand...
Click to collapse
BriCo84 said:
Wow, you are really upset there buddy. Sorry that it bothers you. But to me, this is relevant. I have mofo root not sunshine, and i dont see the point in going through all the effort of sunshine and new roms, when moforoot works perfect. Furthermore i surely might be wrong, but i didn't see a lollipop or marshmallow ROM with these features (tweaked, tether, android pay).
I was simply asking if there was anyone who know how to get the audio working with this ROM. If you don't know, then just don't reply. What's the point in posting just to complain?
Click to expand...
Click to collapse
If you are still on Moforoot (with Kitakat 4.4.4 base installing a "Lollipop" image), you are 1 in a million. You're a year behind all the dev work.
And the ROM will NOT work with Android Pay -- due to all the Android Pay/Safety Net updates the past year. SafetyNet will detect Moforoot. It's obsolete, out of date ROM that will no longer work.
5th May 2016, 02:43 PM
TheSt33v said:
Getting Android Pay to work on a modified device is a constant cat and mouse game. A few workarounds were found and promptly patched by Google in Android Pay/Google Play Services/ Google App updates. If you use it frequently, unlocking is a bad idea. Android Pay might still work on an unlocked device, but any change that you make to any system files will cause it to not work, so there's no point in unlocking.
Even if you managed to root without unlocking (via moforoot or through the terrible kingroot method), you would break Android Pay because root is one of the first things that it looks for, and none of the apps/xposed modules designed to fool it are successful at doing so.
Click to expand...
Click to collapse
It isn't a miracle..
If this is a very stock ROM it should still make it past safety net.
mrkhigh said:
It isn't a miracle..
If this is a very stock ROM it should still make it past safety net.
Click to expand...
Click to collapse
It won't. Please let the year old thread die. It was dead for a reason.
This was back 6 months ago and Safetynet has been updated several times since then.
5th May 2016, 02:43 PM
TheSt33v said:
Getting Android Pay to work on a modified device is a constant cat and mouse game. A few workarounds were found and promptly patched by Google in Android Pay/Google Play Services/ Google App updates. If you use it frequently, unlocking is a bad idea. Android Pay might still work on an unlocked device, but any change that you make to any system files will cause it to not work, so there's no point in unlocking.
Even if you managed to root without unlocking (via moforoot or through the terrible kingroot method), you would break Android Pay because root is one of the first things that it looks for, and none of the apps/xposed modules designed to fool it are successful at doing so.
Click to expand...
Click to collapse