OTA LH9 and Google Wallet - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

Has anyone who updated to LH9 get Google Wallet to work? I have tried all the fixes and the NFC does not communicate with the paypass terminals. Wallet opens and my CC is there. I can see my transactions prior to my update on Sunday. It does not want to create new transactions.

I'd recommend you go back to LH1 rom or earlier. I am on LG1 Wanamlite and it's working fine.

I tried with my phone as well on LH9 at Home Depot, and as you said, it didn't work... Since I never tried it on LH1, don't know whether that is the issue.
I will try at a McDonalds with LH9 and if it doesn't work, revert back to LH1 and try again... I will report with results...

Anybody with LH9 been able to get it to work at all? I've been holding off specifically for this reason
Sent from my Nexus 7 using Tapatalk 2

Im not sure about google wallet but this LH9 update adds support for the multicarrier venture in mobile payments called ISIS which is coming very soon. http://www.att.com/att/isis/#fbid=a4l-V1l4FYs

Yeah I know about Isis but that's still a while away, they haven't even started the pilot yet.
Sent from my Nexus 7 using Tapatalk 2

Have you tried this? Not sure if this is for you or if you tried it.
http://forum.xda-developers.com/showthread.php?t=1769083

greenglue said:
Have you tried this? Not sure if this is for you or if you tried it.
http://forum.xda-developers.com/showthread.php?t=1769083
Click to expand...
Click to collapse
Yes, otherwise you cannot even set up Google Wallet... Issue is, although everything looks fine on the surface (setup OK, wallet starts fine), doesn't communicate with the terminal when it is time to pay...
Btw, I went back to LH1 and tried wallet back at McDonalds yesterday, and it worked again like charm. So the issue is LH9... Don't know what they changed...

I did some digging in the LH9 OTA, and these are the NFC files that were replaced or patched:
/system
/app
Nfc.apk
NfcTest.apk
/etc
nfcee_access.xml
/framework
SecProductFeature_NFC.jar
com.android.nfc_extras.jar
/lib
libnfc.so
libnfc_jni.so
Click to expand...
Click to collapse
That being said, all of those are overwritten with "fixed" files during the Google Wallet installation -- with the exception of those located in /framework. So, it's reasonable to assume that whatever has "broken" in the LH9 update is in those files. I've included a flashable package that includes the LH1 versions of those files as well as incorporates the necessary "fixed" files (eg. SGS3-TW-US_variants-lib_nfc-fix.zip).
I haven't a chance to test this myself, however, I figured someone here may be visiting a PayPass location before I get a chance to. So, if you're interested, I've attached the package below -- please let me know your results!
As always, please make a backup before flashing this or any CMW package!

magn2o said:
I did some digging in the LH9 OTA, and these are the NFC files that were replaced or patched:
That being said, all of those are overwritten with "fixed" files during the Google Wallet installation -- with the exception of those located in /framework. So, it's reasonable to assume that whatever has "broken" in the LH9 update is in those files. I've included a flashable package that includes the LH1 versions of those files as well as incorporates the necessary "fixed" files (eg. SGS3-TW-US_variants-lib_nfc-fix.zip).
I haven't a chance to test this myself, however, I figured someone here may be visiting a PayPass location before I get a chance to. So, if you're interested, I've attached the package below -- please let me know your results!
As always, please make a backup before flashing this or any CMW package!
Click to expand...
Click to collapse
Anybody on LH9 tried this rollback file? Does it work?
Sent from my Nexus 7 using Tapatalk 2

magn2o said:
I did some digging in the LH9 OTA, and these are the NFC files that were replaced or patched:
That being said, all of those are overwritten with "fixed" files during the Google Wallet installation -- with the exception of those located in /framework. So, it's reasonable to assume that whatever has "broken" in the LH9 update is in those files. I've included a flashable package that includes the LH1 versions of those files as well as incorporates the necessary "fixed" files (eg. SGS3-TW-US_variants-lib_nfc-fix.zip).
I haven't a chance to test this myself, however, I figured someone here may be visiting a PayPass location before I get a chance to. So, if you're interested, I've attached the package below -- please let me know your results!
As always, please make a backup before flashing this or any CMW package!
Click to expand...
Click to collapse
For those of us not too savvy, can you explain how to flash this? Did it work for you?

Please read forum rules before posting
Questions go in Q&A
Thread Moved
Friendly Neighborhood Moderator

Related

New Verizon Xperia Play owner - Questions

I have rooted my Xperia Play and used Titanium Backup to remove the bloat. I've got a backup of the System Apps folder so I can reinstall manually if needed. Is there any sort of Recovery that I can use to make a Nandroid, or is there some file somewhere I can download to restore back to factory when/if ICS is released for Verizon customers? And how do I know if I have an I, X, A, or whatever?
I've tried searching here in the forum, but with all the UK vs US, Orange, Rogers, Verizon, [Insert Your Carrier Here], locked BL vs unlocked BL posts, I can't seem to find answers to those 2 simple questions.
Thanks for your help and your patience. I'm new to this phone, but not new to rooting or Android.
I will help as much as I can
In order for us VZW Plays to have a custom recovery(to create a Nandroid), we have to unlock our bootloader. Which sadly for us VZW users, we have to pay to get ours unlocked by members here on the forum. From what I have read and heard they are great at it and don't leave you hanging. I personally think that VZW will release ICS for us, don't know when, later on Hope I helped.
Well I did read something about FTF (whatever that is) and stock firmware in the development thread, but I don't know which phone they are for. Also, I can't seem to download anything from a DropBox link. I always get a 404 page.
I did figure out if I go into about phone I can find my model (800x) and firmware version information. So that's progress, sort of.
netizenmt said:
Well I did read something about FTF (whatever that is) and stock firmware in the development thread, but I don't know which phone they are for. Also, I can't seem to download anything from a DropBox link. I always get a 404 page.
I did figure out if I go into about phone I can find my model (800x) and firmware version information. So that's progress, sort of.
Click to expand...
Click to collapse
You are on the right track. The R800x State of Development thread is for us Verizon users. The FTF files will get you completely back to stock and does not require an unlocked bootloader. You use a program called Flashtool.
Sent from my R800x using XDA App
I thought so, but I haven't been on this site long enough to post my question there. I tried to download the necessary files, but for some reason, I always get a 404 page when I try to download anything from DropBox.
If I were to delete the bloatware apps and a system update rolls around, I just need to reinstall the removed apps and the update should run, right?
maddog00 said:
If I were to delete the bloatware apps and a system update rolls around, I just need to reinstall the removed apps and the update should run, right?
Click to expand...
Click to collapse
Correct BUT it can be a PIA to remember which ones you removed.
I would either just freeze them with Titanium Backup or flash the FTF files when an update comes out.
HotShotAzn said:
Correct BUT it can be a PIA to remember which ones you removed.
I would either just freeze them with Titanium Backup or flash the FTF files when an update comes out.
Click to expand...
Click to collapse
Yeah, in retrospect, I should have thought to write down what I removed before I did so, but...
Once a noob, always a noob, I guess.

Hotspot enabling

Okay, I know there are apps that let you hotspot without a plan but a while back, and I kick my self for this, I came across a zip file that bypassed the Verizon check when you turned on tethering but I never saved it. Since then I have flashed a few Roms and somehow I deleted the zip in my downloads folder and now I can't find the zip anywhere online. Again, I know there are apps and threads talking about this app and that app for tethering but what I am looking for is the zip to flash in recovery. It worked for both CDMA and GSM Gnexs. Somebody please help, need that zip again. Thanks for the time and feed back.
dliontis28 said:
Okay, I know there are apps that let you hotspot without a plan but a while back, and I kick my self for this, I came across a zip file that bypassed the Verizon check when you turned on tethering but I never saved it. Since then I have flashed a few Roms and somehow I deleted the zip in my downloads folder and now I can't find the zip anywhere online. Again, I know there are apps and threads talking about this app and that app for tethering but what I am looking for is the zip to flash in recovery. It worked for both CDMA and GSM Gnexs. Somebody please help, need that zip again. Thanks for the time and feed back.
Click to expand...
Click to collapse
What rom are you running? I think pretty much all of them have the carrier check bypass built in.
pharpe said:
What rom are you running? I think pretty much all of them have the carrier check bypass built in.
Click to expand...
Click to collapse
There is no bypass, because AOSP doesn't have the limitation. The tethering limitation is imposed on software by carriers, not by Google. Makes sense?
Im running stock root. Kinda like it that way. Plain and simple
Thanks to DR3W5K1 over at rootzwiki. This is the zip I was looking for.
http://www.sendspace.com/file/d9k0zj

Am I safe to update to Kitkat?

I Got this phone in the mail off Ebay today. And within the first hour I updated it to 4.3 and rooted it. And now I'm getting another OTA update notification. I'm not new to rooting and stuff but I am new to Samsung. So I'm a little worried if I should do the update or not. I don't wanna get stuck in a bootloop or anything.
I'm rooted
I'm running 4.3
I have Clockwork flashed
Rom is stock
All I'd like to know is if I am safe to update? I heard you are and then I've heard you're not.
not sure but if you can unroot you can allways re root in 4.4
If no one else has done so yet, ive got a modded ota that should allow you to flash via cwm or twrp, and should preserve root.
Its uploading now.
DocHoliday77 said:
If no one else has done so yet, ive got a modded ota that should allow you to flash via cwm or twrp, and should preserve root.
Its uploading now.
Click to expand...
Click to collapse
Alright thanks! let me know when it's up. And are you from Huntsville Alabama too?
Ok, here is the modded OTA!
It should allow you to flash via TWRP or CWM recoveries, and it should also preserve root!
You will still need to be full stock for it to work as it still will go through its checks before flashing. It is not recommended to remove these checks because it could cause problems when patching files. Especially if the files being patched have been modded.
THIS IS UNTESTED! I do not have a working device at the moment, (dont have the I747 anyway), so I am unable to test on my own before releasing. I do not foresee any problems, but there just is no way to be positive until its been tried. If there is an issue, it should still just fail before the flash like it always has been supposed to do.
Please post back ASAP after trying this out so we know if it is working or not.
Modded_OTA_UCUEMJB-UCUFNE4.zip
Hope this proves helpful for some of you!
Doc
DocHoliday77 said:
Ok, here is the modded OTA!
It should allow you to flash via TWRP or CWM recoveries, and it should also preserve root!
You will still need to be full stock for it to work as it still will go through its checks before flashing. It is not recommended to remove these checks because it could cause problems when patching files. Especially if the files being patched have been modded.
THIS IS UNTESTED! I do not have a working device at the moment, (dont have the I747 anyway), so I am unable to test on my own before releasing. I do not foresee any problems, but there just is no way to be positive until its been tried. If there is an issue, it should still just fail before the flash like it always has been supposed to do.
Please post back ASAP after trying this out so we know if it is working or not.
Modded_OTA_UCUEMJB-UCUFNE4.zip
Hope this proves helpful for some of you!
Doc
Click to expand...
Click to collapse
I would test it but I just can't. I'm pretty sure it wouldn't break anything. But I haven't had this phone for 24 hours yet, I just bought it and it's the only one I got. I even paid my bill today too. And I'm looking for another job and you have to have a phone for that lol. Post it up on the forum and let someone who knows more than I do test it because I'm just gonna have to wuss out on this one. I appreciate it though!:good::good:
No sweat. I completely understand! I may go ahead and make a thread for it, but was hoping to verify it works first. Ill post it in the other ota thread for now.
And yes, I am close to Huntsville. Good luck on your job hunt!
Questions and Help issues belong in Q&A and Help section..thanks
Thread moved
FNSM

Going from CM11 To Stock? (Model: Sghi747)

Hey guys, I am new to this forum here but before anyone flames me, I did read the faqs and tried to uninstall from there but it did not work out. Apparently I dont think you can get rid of CM11 since you cant install any stock firmware older than it? Before I installed CM11, I was on jellybean. I had tried to find the latest kitkat update for the s3 (att) and there is no file of it found online (tried sammobile). When I tried flashing an older firmware with ODIN, it just fails at "NAND!". Any help would be appreciated. I am COMPELETELY new at this so specific directions would be appreciated!
I really do love cyanogenmod but there are simply too many glitches and not enough guidance on how to fix em. I am, however, currently using it on my HP touchpad, if anyone remembers what it is . Maybe ill go back to using it in the future.
thanks!
Your rom (cm) has nothing to do with what firmware you can or cannot flash. Once you have updated to 4.3 firmware or newer, you can only flash the same or newer firmware in odin from now on. (Regardless of firmware you can still flash older roms btw)
Using terminal emulator, enter this to find your current firmware build:
getprop ro.bootloader
I suspect you are on a 4.3 build. So odin flash that same firmware. You can find it in these forums. After that you can get the ota to update fully to kk.
There are other methods of updating. Just check the General section. (enewman17 has a few threads that will help)
Note: anytime you go between touchwiz and non touchwiz roms, you will have to factory reset or it'll hang at boot.
DocHoliday77 said:
Your rom (cm) has nothing to do with what firmware you can or cannot flash. Once you have updated to 4.3 firmware or newer, you can only flash the same or newer firmware in odin from now on. (Regardless of firmware you can still flash older roms btw)
Using terminal emulator, enter this to find your current firmware build:
getprop ro.bootloader
I suspect you are on a 4.3 build. So odin flash that same firmware. You can find it in these forums. After that you can get the ota to update fully to kk.
There are other methods of updating. Just check the General section. (enewman17 has a few threads that will help)
Note: anytime you go between touchwiz and non touchwiz roms, you will have to factory reset or it'll hang at boot.
Click to expand...
Click to collapse
..
I am on "I747UCUEMJB"
and i am not sure what build i am on but according to my "build number"this is what it says: "cm_d2att-userbug 4.4.2 KOT49H"
The main issue is, I cannot find 4.3 update anywhere on the internet
The MJB is your current firmware/bootloader build/version.
The build number displayed in settings only represents the rom, which is often different, and doesnt really matter to much.
From this post/thread
http://forum.xda-developers.com/showthread.php?p=52341560
Direct link to MJB firmware
http://www.androidfilehost.com/?fid=23329332407590581
DocHoliday77 said:
The MJB is your current firmware/bootloader build/version.
The build number displayed in settings only represents the rom, which is often different, and doesnt really matter to much.
From this post/thread
http://forum.xda-developers.com/showthread.php?p=52341560
Direct link to MJB firmware
http://www.androidfilehost.com/?fid=23329332407590581
Click to expand...
Click to collapse
i have no idea what MJB means (i google'd it) and i just found out what my bootloader version is via download mode (its at the very bottom) and i have version 2.0?
ok downloading the giant file now. will report details. just follow instructions in the first link?
[sorry, like i said, im a noob so i really apologize for the lack of terms here]
MJB is just short for I747UCUEMJB. Sorry if I confused you. And the S/W revision being 2.0 is what Odin uses to know what firmware it is allowed to flash. In this case 2.0 tells odin it can flash the MJB firmware, or anything newer.
And yes, follow the instructions he posted and you should be fine.
Oh, and if you did not run the getprop command I posted before, please do so before flashing....just to be on the safe side. If it returns I747UCUEMJB, you are good to go. If it returns anything else, let me know before flashing.
DocHoliday77 said:
MJB is just short for I747UCUEMJB. Sorry if I confused you. And the S/W revision being 2.0 is what Odin uses to know what firmware it is allowed to flash. In this case 2.0 tells odin it can flash the MJB firmware, or anything newer.
And yes, follow the instructions he posted and you should be fine.
Oh, and if you did not run the getprop command I posted before, please do so before flashing....just to be on the safe side. If it returns I747UCUEMJB, you are good to go. If it returns anything else, let me know before flashing.
Click to expand...
Click to collapse
Cool! Got it. I think that was my main problem. I could only find 4.0 (or 4.1) and have been trying to use that on ODIN. Perhaps that was the main issue....
Oh already ran it and got "I747UCUEMJB", sorry if didnt say it properly.
Really appreciate the help! Ive at this for days and no solutions. Sometimes the hacking/custom firmware isnt for everybody
Ill update what happens. Download is taking forever.
EDIT: BTW, for the first link, which poster am I gonna have to follow? im assuming "garbage guy"?
I though you did run the command already, but just wanted to be certain is all. For some reason AT&T stopped releasing their firmware, which has been causing all kinds of problems for people.
Anyway, it sounds like you are good to go! Good luck!
Oh, and if the firmware you're downloading is a .zip or .7z file, make sure you extract it first. Odin only flashes .tar and .tar.md5 files.
DocHoliday77 said:
I though you did run the command already, but just wanted to be certain is all. For some reason AT&T stopped releasing their firmware, which has been causing all kinds of problems for people.
Anyway, it sounds like you are good to go! Good luck!
Oh, and if the firmware you're downloading is a .zip or .7z file, make sure you extract it first. Odin only flashes .tar and .tar.md5 files.
Click to expand...
Click to collapse
Thank you so much! It finally worked! I got the reset notification and I am now back on JB
Thank you! should I take any more steps to ensure I made a clean installation or am I good after flashing it?
david12795 said:
Thank you so much! It finally worked! I got the reset notification and I am now back on JB
Thank you! should I take any more steps to ensure I made a clean installation or am I good after flashing it?
Click to expand...
Click to collapse
Weird, I went straight to update phone and it said my phone is up to date? I thought the official 4.4 update came out for the S3?
david12795 said:
Thank you so much! It finally worked! I got the reset notification and I am now back on JB
Thank you! should I take any more steps to ensure I made a clean installation or am I good after flashing it?
Click to expand...
Click to collapse
Awesome!
really glad to hear that! The only thing I can think of thst you might want to do next is backing up your nv data. The following is a copy/past from a post I made a few min ago... root is required to fo this btw, just so you know.
(Since you are looking to update though, I recommend waiting till you have updated before rooting and running this backup)
It's a super simple procedure and will create an on device backup of your nv data. The backup will be stored on a couple of partitions we never touch, not even with firmware flashes. This essentially makes it a permanent backup. The cool thing about it is every time you reboot, the system checks for any corruption, and if detected, it will automatically restore from this backup. So if it were to ever happen, you probably wouldn't ever even notice it!
Install the Terminal Emulator from the play store. Open and enter this:
su
reboot nvbackup
Thats it! Device will reboot and create your backup. This should prevent you from ever suffering from a lost IMEI!
david12795 said:
Weird, I went straight to update phone and it said my phone is up to date? I thought the official 4.4 update came out for the S3?
Click to expand...
Click to collapse
That has been released, but OTA's are generally rolled out in stages over several weeks. Usually done by region. So it msy not have started in your area just yet.
Two alternatives you can try though, install kies on your computer and update through that. Or there are a couple if threads in the General section that provide the ota for download.
Enewman17 has a few threads helping folks to update so I recommend checking them out as well.
Ive heard that some people have gone to best buy and they were able to initiate the update there. I dont know much more about this though.
DocHoliday77 said:
Awesome!
really glad to hear that! The only thing I can think of thst you might want to do next is backing up your nv data. The following is a copy/past from a post I made a few min ago... root is required to fo this btw, just so you know.
(Since you are looking to update though, I recommend waiting till you have updated before rooting and running this backup)
It's a super simple procedure and will create an on device backup of your nv data. The backup will be stored on a couple of partitions we never touch, not even with firmware flashes. This essentially makes it a permanent backup. The cool thing about it is every time you reboot, the system checks for any corruption, and if detected, it will automatically restore from this backup. So if it were to ever happen, you probably wouldn't ever even notice it!
Install the Terminal Emulator from the play store. Open and enter this:
su
reboot nvbackup
Thats it! Device will reboot and create your backup. This should prevent you from ever suffering from a lost IMEI!
Click to expand...
Click to collapse
Thank you! I will look into this. I just figured for some reason...I would have some data left from cyanogenmod, if that makes sense. In other words, i want my phone to be as fresh as possible. I only ask this because when I had CM, i accidentally made a backup of it through rom manager (or clockwork) and I am not sure if its in my partition somewhere.
That has been released, but OTA's are generally rolled out in stages over several weeks. Usually done by region. So it msy not have started in your area just yet.
Two alternatives you can try though, install kies on your computer and update through that. Or there are a couple if threads in the General section that provide the ota for download.
Enewman17 has a few threads helping folks to update so I recommend checking them out as well.
Ive heard that some people have gone to best buy and they were able to initiate the update there. I dont know much more about this though.
Click to expand...
Click to collapse
TIL that OTA arent as fast. Ill download KIES and give it a try.
Just installed KIES and it said my phone has the latest firmware?
david12795 said:
Thank you! I will look into this. I just figured for some reason...I would have some data left from cyanogenmod, if that makes sense. In other words, i want my phone to be as fresh as possible. I only ask this because when I had CM, i accidentally made a backup of it through rom manager (or clockwork) and I am not sure if its in my partition somewhere.
TIL that OTA arent as fast. Ill download KIES and give it a try.
Click to expand...
Click to collapse
Factory resetting with stock recovery installed wipes all data except the external sdcard. I am so sorry I should've mentioned this before. I was thinking you had already done one at some point and didn't have anything left to worry about. Still, I should have asked and I do apologize for that. Hopefully if it was really important it was saved to the external sdcard....
david12795 said:
Just installed KIES and it said my phone has the latest firmware?
Click to expand...
Click to collapse
Ok, I wasn't sure about that. I personally never need or use kies so I didn't know if it was tied to the staged rollouts. It would appear that it is though.
Give me a few min and ill post links to the threads where you can download the ota or update via a different method.
---------- Post added at 03:56 AM ---------- Previous post was at 03:40 AM ----------
UCUEMJB to UCUFNE4 firmware update - thread by enewman17
http://forum.xda-developers.com/showthread.php?t=2808654.
How to update SGH-I747 yo UCUFNE4_4.4.2 - thread by enewman17
http://forum.xda-developers.com/showthread.php?t=2789917
[Download] AT&T Kitkat OTA file - thread by bkong
http://forum.xda-developers.com/showthread.php?t=2788012
I suggest trying the third one by bkong first. He posted a pure OTA file you can try to update with.
The first option is a recovery flashable firmware, but does not include the /system (ROM) portion. To fully update using this you'll flash the firmware per his instructions and then go to his development thread for the stock rom. It is here: http://forum.xda-developers.com/showthread.php?t=2788357
The second option is the OTA file, but it has been slightly modified to skip certain file checks. If the original OTA doesnt work, theres a good chance this will. (Since you are full stock now either one should flash without issue).
Hope those help! I recommend doing a bit of reading about each one (at least the OP and last few pages) and start with whichever you are most comfortable with.
Or, you could always use that most valuable tool, patience, and wait for the OTA to roll out for your area.
Good luck!
DocHoliday77 said:
Factory resetting with stock recovery installed wipes all data except the external sdcard. I am so sorry I should've mentioned this before. I was thinking you had already done one at some point and didn't have anything left to worry about. Still, I should have asked and I do apologize for that. Hopefully if it was really important it was saved to the external sdcard....
Ok, I wasn't sure about that. I personally never need or use kies so I didn't know if it was tied to the staged rollouts. It would appear that it is though.
Give me a few min and ill post links to the threads where you can download the ota or update via a different method.
---------- Post added at 03:56 AM ---------- Previous post was at 03:40 AM ----------
UCUEMJB to UCUFNE4 firmware update - thread by enewman17
http://forum.xda-developers.com/showthread.php?t=2808654.
How to update SGH-I747 yo UCUFNE4_4.4.2 - thread by enewman17
http://forum.xda-developers.com/showthread.php?t=2789917
[Download] AT&T Kitkat OTA file - thread by bkong
http://forum.xda-developers.com/showthread.php?t=2788012
I suggest trying the third one by bkong first. He posted a pure OTA file you can try to update with.
The first option is a recovery flashable firmware, but does not include the /system (ROM) portion. To fully update using this you'll flash the firmware per his instructions and then go to his development thread for the stock rom. It is here: http://forum.xda-developers.com/showthread.php?t=2788357
The second option is the OTA file, but it has been slightly modified to skip certain file checks. If the original OTA doesnt work, theres a good chance this will. (Since you are full stock now either one should flash without issue).
Hope those help! I recommend doing a bit of reading about each one (at least the OP and last few pages) and start with whichever you are most comfortable with.
Or, you could always use that most valuable tool, patience, and wait for the OTA to roll out for your area.
Good luck!
Click to expand...
Click to collapse
No no! Its fine, I wasnt planning using it or anything, I just wanted to get rid of it since I have no use for it, no need to apologize. , I was fully aware that I would lose all files, other than SD ext drive. I just wanted to make sure that all files are in the right place and none of the unnecessary files are taking up space (e.g. files from cyanogenmod)
As for the update, I talked to a samsung representative and they said one can go to Best Buy and get it updated there through a technician, so Ill try that later since I am close to it ATM. If it back fires, Ill try your suggestions.
I really do appreciate for the help , I have been completely lost for days but it turns out I was just using the wrong firmware. Thanks for pointing it out. Good karma is coming your way . Hopefully one day, I will be here again and trying out a new custom firmware.
Glad I could help!
If I remember right, someone who mentioned the best buy thing had said at the time that the first store they went to did not have the update yet. But I think they found another in their area did. So if they say its up to date and cant help, you might find another store close by can. (If there is one of course!)
Just fyi so you're not too surprised if that happens.
DocHoliday77 said:
Glad I could help!
If I remember right, someone who mentioned the best buy thing had said at the time that the first store they went to did not have the update yet. But I think they found another in their area did. So if they say its up to date and cant help, you might find another store close by can. (If there is one of course!)
Just fyi so you're not too surprised if that happens.
Click to expand...
Click to collapse
Ill hope for the best and prepare for the worst.
Of course, if the worst happens, I can just use one of your links you mentioned. :good::good:

Where do the factory images come from?

Yes, yes, I know... from the factory!
No, what I really mean is, these RETEU, RETIN, RETLA, etc. zip files hosted on lolinet, or passed around in other forum threads. Are they all just leaked by helpful Moto/Lenovo employees? Or is there some way to extract the firmware
1) off of a pristine Moto Z Play, or
2) by intercepting the OTA process somehow?
The question is relevant because I have a brand-new Z Play that I'd like to unlock and flash LineageOS on. But obviously, I'd like to preserve the option of wiping everything clean and going back to stock, including OTAs, if I change my mind later. (I know that the bootloader cannot be re-locked; that's ok.) After spending almost a whole day slogging through the MANY threads here, I think I have a pretty good understanding of how to restore stock from a factory image file---the ones with all of the sparsechunks. But my phone is RETUS, and most of what you can find online is from other world regions. Of course there is also RETAIL, but nobody has ever explained (and perhaps nobody knows) how that differs from the region-specific images, and what consequences there could be to using RETAIL instead of a proper RETUS image. Random "it works for me" testimonials are always encouraging to hear, but hardly the basis for real confidence! So, obviously, it would be great if there were some way to extract the firmware off of my own phone prior to unlocking. Otherwise, it does seem a little bit crazy to be flashing factory images provided by strangers on dodgy file-sharing sites.
(There are NANDroid backups, of course, but if I am understanding the situation correctly, you need much lower level than that for a proper reversion to stock. I.e. you need to replace the original recovery, and probably other stuff too.)
Please, enlighten me
https://motoota.lolinet.com/index.php?model=XT1635-02&sv=Blur_Version.26.201.1.addison.retail.en.US&carrier=retin&sn=
it come from motorola rsdsecure, for instance : https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip (it is not the last version)
Seems to be an IP filter, and some countries are not able to download the same last versions than others. so there is some shared files on afh or others to help, but for me i prefer to DL directly from motorola
Interesting.
After the OTA updater has downloaded an update, but before the upgrade process is started, does the zip file exist "in the clear" on the phone? And could it be retrieved with adb pull before saying yes to the update?
Ok, I think I answered my own question. There is a difference between the OTA update files and factory image files. OTA updates are the ones with "Blur" at the beginning... maybe an acronym for something-something-update-something? So @talktosam, your link is not applicable because those are OTA files; you can try to sideload them if your phone is already running stock firmware, but you can't use them to restore a fully wiped phone back to stock. The factory images I'm asking about are the ones with all of those "sparsechunk" files inside. (Please correct me if any of this is wrong.)
So that Motorola rsdsecure site probably does not exist for the OTA updater, as I'd initially thought, but for service personnel?
mark04 said:
Interesting.
After the OTA updater has downloaded an update, but before the upgrade process is started, does the zip file exist "in the clear" on the phone?
Click to expand...
Click to collapse
Yes, somewhere in /cache.
mark04 said:
And could it be retrieved with adb pull before saying yes to the update?
Click to expand...
Click to collapse
Of course. It is for instance easily possible to move away or rename before installation using eg total Commander if it has root rights.
Blur...something...zip is right.
yes u are correct, but any way to download factory image, its a life saver for some users also (mine search these files bcz am on stock bootloader unlocked)
tag68 said:
Blur...something...zip is right.
Click to expand...
Click to collapse
But just to confirm, those zips you can only use with adb sideload; you cannot use them to flash over a different ROM and return to stock. Correct?
I never sideload. There is the possibility to apply it to the wrong channel. You can put it to the original place to apply and let OTA do its work.
Afaik you also can sideload that blur.

Categories

Resources