Related
I don't own a Defy but I do own a Milestone. It looks like, from all the chatter I've read, there is still no T-Mo US firmware SBF yet. Some Americans seem to have become trapped with a foreign firmware on their handset which does not support American 3G bands.
In Milestone-land we have all the SBFs we need, but we also found a workaround to enable proper 3G on devices mis-flashed with ROMs that were meant for Euro frequencies. Maybe you guys can tell me if the Defy is similarly designed.
On the Milestone, the folder /etc/motorola/bp_nvm_default contains a number of files including these:
File_Audio
File_Audio2
File_GSM
File_Seem_Flex_Tables
generic_pds_init
If you back up these files from your original ROM (e.g. using Root Explorer), and then restore them on the new ROM after rooting, and reboot, the correct 3G behaviour returns to the Milestone.
Does this folder exist on the Defy? Do these files exist? If so, maybe one of you on the stock T-Mo US ROM could back up this whole folder to a ZIP file; then see if the folks stuck on Euro ROMs are able to use this to fix their 3G.
cmstlist said:
Does this folder exist on the Defy? Do these files exist? If so, maybe one of you on the stock T-Mo US ROM could back up this whole folder to a ZIP file; then see if the folks stuck on Euro ROMs are able to use this to fix their 3G.
Click to expand...
Click to collapse
folder exist, I have this files on my defy (Europe/CH):
File_GPRS
File_Seem_Flex_Tables
File_Audio
File_Audio6
File_Audio8
File_Logger
File_Audio4
File_Audio5_AMR_WB
File_Audio5
File_Audio7
File_Audio3
File_UMA
File_Audio2_AMR_WB
File_Audio2
File_Audio4_AMR_WB
File_Audio1_AMR_WB
File_Audio3_AMR_WB
File_GSM
Well isn't that interesting... there's a file related to UMA (wi-fi calling) even on your European Defy.
So anyway - great! - now if a T-Mo US Defy user can post a .zip of these files backed up from their stock ROM, then it would be of great value to anyone stuck with the wrong SBF on their US Defy. I don't know if it's harmful to replace more than just the 5 filenames listed above. Or for that matter I don't know if replacing any of them is harmful, so please back up whatever you are replacing as well
Confirmed, this works. See simply-android or Modmymobile for threads on this.
Seems there is a specific 3.70 update for hw 002. http://www.androidcentral.com/evo-4g-update-continues-new-file-other-hardware-models#comments I wonder what the differences are?
I'm curious as well... does anybody have the build numbers for the different versions? I have hw 0003 and already used one of the available roms to update since I'm rooted. Want to know if I got the 'wrong' rom if it's worth going through the process of installing the 'right' one.
I have 0002, where did have get great update rom from?
Sent from my PC36100 using XDA App
i don't think is out for 0002 yet because i been waiting for this
verse187 said:
i don't think is out for 0002 yet because i been waiting for this
Click to expand...
Click to collapse
If you read the link it clearly is out.
IF it were actually a different rom, don't you think it would NOT have been 3.70.651.1 like they did the change for the 004's???? All they say for sure is it has a different file name. Unless someone compares the files, I wouldn't put any money on it being "different"
May be a different update process but the firmware should be the same. I highly doubt HTC is going to release two different version that have the exact same version number.
xHausx said:
May be a different update process but the firmware should be the same. I highly doubt HTC is going to release two different version that have the exact same version number.
Click to expand...
Click to collapse
This.
Just because you got it later than the newer evos doesn't mean it's for the older hardware versions.
It just means the sprint service in your area was slow to push the update to you, its customer, for that region.
I find that alot of times androidcentral can actually jack up information just as bad as the rumors that are out there.
The author even said they had a hw002 evo and "finally" got the new ota. It doesn't mean squat about it being specific to that hardware. It just means the author is one of the many customers who are in a region that gets otas slower than others.
I downloaded that file and ripped it apart in dsixdas kitchen and it even has the same kernel as the supposed "hw004 3.70".
Bottom line is if it was really hardware specific it would at least have a different kernel version.
I flashed the 3.7 rom on this forum on my version 002 and no problems that I can see so far
Spoken from my Evo using Ultra Keyboard and XDA App
lovethyEVO said:
This.
Just because you got it later than the newer evos doesn't mean it's for the older hardware versions.
It just means the sprint service in your area was slow to push the update to you, its customer, for that region.
I find that alot of times androidcentral can actually jack up information just as bad as the rumors that are out there.
The author even said they had a hw002 evo and "finally" got the new ota. It doesn't mean squat about it being specific to that hardware. It just means the author is one of the many customers who are in a region that gets otas slower than others.
I downloaded that file and ripped it apart in dsixdas kitchen and it even has the same kernel as the supposed "hw004 3.70".
Bottom line is if it was really hardware specific it would at least have a different kernel version.
Click to expand...
Click to collapse
Sorry, but you are wrong. Bad info.
There are two different versions, but both update you to the same end result. They are different because they are updating from different software revisions. If you bother to look at the contents of the two updates, you would see that they are indeed different.
The two OTA updates are:
OTA_Supersonic_3.70.651.1-3.29.651.5_releasezq9ss6wyobuo26b5.zip
OTA_Supersonic_3.70.651.1-3.30.651.3_releasekobxwrvtv9q86pp0.zip
indagroove said:
Sorry, but you are wrong. Bad info.
There are two different versions, but both update you to the same end result. They are different because they are updating from different software revisions. If you bother to look at the contents of the two updates, you would see that they are indeed different.
The two OTA updates are:
OTA_Supersonic_3.70.651.1-3.29.651.5_releasezq9ss6wyobuo26b5.zip
OTA_Supersonic_3.70.651.1-3.30.651.3_releasekobxwrvtv9q86pp0.zip
Click to expand...
Click to collapse
I stand corrected and Im not afraid to admit I was wrong. Like you said the end result is the same so it really doesnt make sense to push two different otas just to get to the same end.
In any case people here are going to get what they want on their device anyways regardless of hardware/version compatibilities.
indagroove said:
Sorry, but you are wrong. Bad info.
There are two different versions, but both update you to the same end result. They are different because they are updating from different software revisions. If you bother to look at the contents of the two updates, you would see that they are indeed different.
The two OTA updates are:
OTA_Supersonic_3.70.651.1-3.29.651.5_releasezq9ss6wyobuo26b5.zip
OTA_Supersonic_3.70.651.1-3.30.651.3_releasekobxwrvtv9q86pp0.zip
Click to expand...
Click to collapse
I wonder what version JoeyKrim used in his 5.1 Rom. I hope he used the 3.29 and if not, hopefully he can make it.
Sent From My HTC Evo 4G Using Tapa Talk Pro!
lovethyEVO said:
I stand corrected and Im not afraid to admit I was wrong. Like you said the end result is the same so it really doesnt make sense to push two different otas just to get to the same end.
In any case people here are going to get what they want on their device anyways regardless of hardware/version compatibilities.
Click to expand...
Click to collapse
It makes sense to have 2 different OTAs for the same end result, because you are updating 2 different ROMs.
Rydah805 said:
I wonder what version JoeyKrim used in his 5.1 Rom. I hope he used the 3.29 and if not, hopefully he can make it.
Click to expand...
Click to collapse
It doesn't work like that. You can't really make roms directly from OTA updates. Since the RUU was released, all chefs will be working from that. In case you don't know, an OTA ("Over The Air" update) is really just a patch for a current rom, and only contains the updated files -- which is why you can't update OTA from a rom like CM6.X. What's referred to as an "RUU" (which really means rom update utility), contains the full rom with ALL the files -- NOT just the updated files.
If chefs didn't have the ruu, then there may be some concern as to which update was used. Basically to make a full rom from an OTA, you have to flash the OTA which updates your current rom, and then do a nandroid backup of the newly updated rom on your device, and then dump it and rebuild in the kitchen. But, like I say since we have the RUU (thanks to 911sniper, I think), all roms will be based on that.
This is finally the end of having to worry about which rom for which HW version. As I see it, the biggest issue is going to be people not wanting to update their radio, pri, and hboot versions for whatever reason, and causing issues with the latest software as a result.
indagroove said:
It makes sense to have 2 different OTAs for the same end result, because you are updating 2 different ROMs.
It doesn't work like that. You can't really make roms directly from OTA updates. Since the RUU was released, all chefs will be working from that. In case you don't know, an OTA ("Over The Air" update) is really just a patch for a current rom, and only contains the updated files -- which is why you can't update OTA from a rom like CM6.X. What's referred to as an "RUU" (which really means rom update utility), contains the full rom with ALL the files -- NOT just the updated files.
If chefs didn't have the ruu, then there may be some concern as to which update was used. Basically to make a full rom from an OTA, you have to flash the OTA which updates your current rom, and then do a nandroid backup of the newly updated rom on your device, and then dump it and rebuild in the kitchen. But, like I say since we have the RUU (thanks to 911sniper, I think), all roms will be based on that.
This is finally the end of having to worry about which rom for which HW version. As I see it, the biggest issue is going to be people not wanting to update their radio, pri, and hboot versions for whatever reason, and causing issues with the latest software as a result.
Click to expand...
Click to collapse
So do you suggest everyone should be updating their radios, etc?
billyapd21 said:
So do you suggest everyone should be updating their radios, etc?
Click to expand...
Click to collapse
Unless you are a developer and need the bootloader (hboot) version which supports fastboot commands via adb, I would personally update all radio, pri, nv, hboot, kernel, rom etc.. IF you have Unrevoked Forever installed.
indagroove said:
Unless you are a developer and need the bootloader (hboot) version which supports fastboot commands via adb, I would personally update all radio, pri, nv, hboot, kernel, rom etc.. IF you have Unrevoked Forever installed.
Click to expand...
Click to collapse
I would agree with this with the exception of the hboot.
Fastboot commands can come in handy to do things that can't be done any other way. Like say you break your 4G, with the only public solutions out there you'll need fastboot to fix it
indagroove, do you know if there are any specific benefits an updated hboot provides?
Alright guys, I'm posting this here because it's the closest forum to the SCH-R760x I can find (CDMA SGSII) I think you guys are the D710 but I suppose the modem works about the same.
Anyway, in a fit of despair I odined the stock files for the USCelluar Varient of the SGSII which yes... is different.
So here's my problem, it may be more than this, but this is what I've noticed.
-After odining the USCC stock files, under About Phone>Status the "user name" field showed (phonenumber)@uscc.net
-So I odined the Generic stock files ( like I should have done in the first place) with Phone EFS Clear checked and now the same field shows (phonenumber)@carrier.com
-Opened modem.bin from the stock files .tar in a hex editor and found in offset 0822A0 "@carrier.com"
-Tried editing modem.bin to @awcc.com but after saving the file and trying to odin I get a failed. (replaced character spaces with hex 00) @carrier.com=12 characters @awcc.com=9 characters
http://dl.dropbox.com/u/21311280/modem.bin <--- modem.bin file if anyone wants to give editing a shot.
I don't know if anything else beyond this needs to be changed but I'm pretty sure this is at least one of my problems (besides stupidity)
It's almost like my phone is back in the generic state and needs to be programmed for Alltel so if anyone know anything about the initial programming needed for a smartphone at Alltel that may work as well.
No I'm not Verizon, this is still Alltel now owned by Allied Wireless Communications
So anyway, any help or ideas would be greatly appreciated. Also if this would be better suited in a different section please advise.
Thanks xda, you guys have always been great and hopefully can get me through this as well.
191 said:
It's almost like my phone is back in the generic state and needs to be programmed for Alltel so if anyone know anything about the initial programming needed for a smartphone at Alltel that may work as well.
Click to expand...
Click to collapse
My first endeavor would be to look up alltel phone programming, if that wasn't possible, but could still be the fix, I'd take it in to the store and see what they know. I would say this just happened and you don't know what happened.
Sent from my SPH-D710 using XDA
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:
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.