Database Users

[Q] Trying to go back from CM12 to Touchwiz

Hi all,
Here's my story. I have a US T-Mobile Galaxy S5. I wanted to try Lollipop as the new Touchwiz wasn't available yet for my device in early April. So hearing that it is very fast I chose CM12 and used their guide for the S5. I had a little trouble (Heimdall didn't work for some reason), but I successfully used Odin to install the custom recovery (TWRP). Then I was able to wipe and install the CM12 nightly image just fine using TWRP.
Since then I realized that my Gear 2 is only partially compatible with CM12. I've yet to find a thread that shows specific steps to get it working well with CM12, only partially, and many have had trouble even getting partial functionality. And now that Lollipop Touchwiz is available for my phone, I'd like to switch to that.
Last weekend I tried just that. I took a second backup of my CM12 build, then restored my backup from touchwiz 4.4. When I booted to it, the phone was severely crippled. The menu bar and navigation drawer were missing, and the home button did not work at all. I performed a factory reset, and it seemed to be working fine again. Next, I tried an OTA update to 5.0. That didn't work: the phone realized it had been tampered with and told me to use Kies. So I installed Kies, and attempted the update there. After some wrestling with it, I finally got the update to 5.0 started. It finished successfully (so it said anyway) but the phone failed to boot up. It was stuck on the Samsung logo screen for quite a long time. There was some blue text about recovery and I was panicking thinking somehow TWRP screwed up my ability to update w/ Kies. I tried rebooting and could not get into recovery or the OS no matter what. I tried Kies' emergency options only to have it not recognize my phone as compatible. So I went to download mode and installed TWRP again using Odin. Then I was able to boot into recovery, and I restored the backup of CM12 I took before I started all this (thank God I did that).
So now I'm back on CM12 with everything working fine, except of course my watch. I did not expect the restore back to Samsung software to be more difficult than going to CM12.
Can anyone see what I did wrong?
I gather I can install a stock rom with Odin. But all the links I find for this download take me to some sketchy download site that crawls at 50 K/s unless you pay. Am I missing something? Kies downloaded the update in a matter of minutes. Maybe that is still somewhere on my system, and I can use that w/ Odin?

bump

Have a look here for a stock ROM for your model S5 (Example, mine is the G900F)
http://forum.xda-developers.com/showthread.php?t=2715487
If there isn't one, you'll need to do the slow-ass download from sammobile dot com, then use ODIN to flash it

*Detection* said:
Have a look here for a stock ROM for your model S5 (Example, mine is the G900F)
http://forum.xda-developers.com/showthread.php?t=2715487
If there isn't one, you'll need to do the slow-ass download from sammobile dot com, then use ODIN to flash it
Click to expand...
Click to collapse
Thanks. That thread is such a mess. I searched for "G900T" and "T-mobile" but couldn't find it. I will use sammobile then. I wasn't sure before whether to trust it. Having a senior member here vouch for it helps a little.

pianowow said:
Thanks. That thread is such a mess. I searched for "G900T" and "T-mobile" but couldn't find it. I will use sammobile then. I wasn't sure before whether to trust it. Having a senior member here vouch for it helps a little.
Click to expand...
Click to collapse
That's where everyone gets them from, there and samsung - updates dot com
Both sites are banned here for linking to, but not because they are dodgy, just because the owners refused to adhere to XDA rules
They are safe to download from

so frustrating
I downloaded the lollipop stock image from sammobile, and installed with Odin. Odin reported success just like Kies did, and also just like the Kies process, my phone is still stuck in the recovery boot loop. It says RECOVERY BOOTING... in blue at the top and shows the Samsung logo powered by android. What a mess.
Is there something I can do from here to fix this?

Try flashing the PIT file along with the stock ROM, that will repartition the phone then flash the ROM, sounds like something got corrupted using KIES maybe
Double check that this is in-fact the exact model phones PIT file first or you could end up with an even worse brick
http://forum.xda-developers.com/showpost.php?p=52767244&postcount=16
More PIT files here
http://forum.xda-developers.com/showthread.php?t=2737448
There's a video of someone using PIT with ODIN on a different phone, but steps are the same
https://www.youtube.com/watch?v=4qtbEevn1VA
Basically you want it looking like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thanks again for your help. I think for now I will stick with 4.4 touchwiz. I hear bad things about the touchwiz 5.0 battery life. I simply restored from the TWRP backup I used when I started all this lollipop experimentation, then did a factory reset. I should have my watch working again later tonight.

[I337M] Samsung S4 Nand Reset Failure. [Thanks Samsung]

Okay, so here's my predicament:
Updating my S4 to 5.0.1 failed, so I flashed it with the proper one, but I accidentally clicked Nand Reset All, and now, this get's funny, I can't write or flash any official updates or anything, it get's to this:
Nand Reat/Write failed.
BUT HOLD THE HORSES, THERE'S MORE:
My phone says: There as a problem with the firmware, please use recovery in Kies and try again.
And it says a bunch of stuff on the top left.
If you need screenies, I am happy to provide a full video.
EDIT:
So, I got this little error now:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I never tried repartitioning, but I'm going to do some more research on this error, and see if I can't find a solution

Predated said:
Okay, so here's my predicament:
Updating my S4 to 5.0.1 failed, so I flashed it with the proper one, but I accidentally clicked Nand Reset All, and now, this get's funny, I can't write or flash any official updates or anything, it get's to this:
Nand Reat/Write failed.
BUT HOLD THE HORSES, THERE'S MORE:
My phone says: There as a problem with the firmware, please use recovery in Kies and try again.
And it says a bunch of stuff on the top left.
If you need screenies, I am happy to provide a full video.
EDIT:
So, I got this little error now:
I never tried repartitioning, but I'm going to do some more research on this error, and see if I can't find a solution
Click to expand...
Click to collapse
For Re-Partition you require a PIT file. The PIT file has to be specific to the internal storage of your phone.
So the first flash (the one with nand erase all) was successful and any subsequent flash failed?

GDReaper said:
For Re-Partition you require a PIT file. The PIT file has to be specific to the internal storage of your phone.
So the first flash (the one with nand erase all) was successful and any subsequent flash failed?
Click to expand...
Click to collapse
Really? Damn, well, I guess I could grab it, but I now don't see the firmware issue and now see the S4 Bottscreen, but now I can't boot anymore, I'm thinking of reinstalling adb toget rid of this pesky libsub error.
I'll update soon.
I don't know wht I did, but it works, and it's updating now to the newest firmware. I'll update when I wake up on how I fixed it.
This is what I used to restore it to it's normal capacities:
Guys, Kies 3 has a way of re-flashing your device to the latest official firmware for a certain model with a certain Samsung serial number, i.e. even if your device is bricked and Kies 3 cannot detect it, you enter it's model and Samsung serial number and Kies 3 will download and flash the firmware for you, all you need to do is open Kies 3, power up your device and connect it to your PC, you will then open Tools menu and select Firmware Upgrade and Initialization, if Kies 3 can detect your phone it will show you the version of the firmware that will be downloaded and flashed then you will proceed as instructed (very simple procedures), if not you will be asked to enter just your model (for example GT-N8000) and your Samsung Serial Number (usually starts with R can be found on the sticker under the battery) then it will show you the latest official firmware for your device and if you proceed it will download and flash it for you, but be careful (this will be noted by Kies 3 too) you should get a full backup of your phone as it may wipe out everything on the internal storage in the process if it's required (i.e. a bricked phone to the extent of wrong partitioning that lead to loss of imei), needless to say this process depends on your internet connection (it downloads prerequisite files and firmware files which are relatively large), from little experience I have, it's best that you use the conventional official method for any product rather than unconventional ways at the beginning to solve any problem related to any product, if it doesn't help then try your best with any other method that might help you (by the way I tried this with more than one model of Samsung smart phones, tablets and notes and it always ends up solving the problem, in some cases with my friends devices reviving the device again after being totally bricked), hope this helps .
Note: all devices I used this method with were original devices straight from Samsung (International Versions, Unbranded & Unlocked), so the firmware comes straight from Samsung (no modifications done by operators / carriers) so I'm not sure if it will work for other devices (Fake Cloned, Locked or Branded devices with carriers specific settings)
Link at:
Cant post yet.

It's good to know this.
Unfortunately there are a lot of Frankenstein S4s out there. What this means is that the phone has been repaired with mismatched parts from other S4 models, and this may lead to apps reporting a wrong phone model and other errors.

GDReaper said:
It's good to know this.
Unfortunately there are a lot of Frankenstein S4s out there. What this means is that the phone has been repaired with mismatched parts from other S4 models, and this may lead to apps reporting a wrong phone model and other errors.
Click to expand...
Click to collapse
Yeah, but mine's bought from my phone company and never broke internally, no hardware damage or anything like that, but it now bricked itself again, so I ran into another problem, it doen't show up in emergency recovery in Kies, I don't see the phone. Hmm, 'll keep trying and update the thread when I've figured this out.

Predated said:
Yeah, but mine's bought from my phone company and never broke internally, no hardware damage or anything like that, but it now bricked itself again, so I ran into another problem, it doen't show up in emergency recovery in Kies, I don't see the phone. Hmm, 'll keep trying and update the thread when I've figured this out.
Click to expand...
Click to collapse
Why are you trying to flash a 4.4.2 rom? You said you were on 5.0.1 (or at least your tried to flash that) so you probably can't flash a 4.4.2. rom.
Download a Lollipop rom and try flashing it again.

Lennyz1988 said:
Why are you trying to flash a 4.4.2 rom? You said you were on 5.0.1 (or at least your tried to flash that) so you probably can't flash a 4.4.2. rom.
Download a Lollipop rom and try flashing it again.
Click to expand...
Click to collapse
I was on 4.4.3 for a while, but it's fixed guys, I got it, with 5.0.1 rom, thanks guys!

Anyone installed B352 update successfully?

I'm using a MediaPad M3 (Wifi only) bought from amazon.com (model: BTV-W09C128) and I discovered by chance, through firmware finder, that there's an update that ends with B352 (my current firmware ends with B351) and I wished I can download this update because it has lots of nice optimizations with battery and touch sensitivity...etc but trying to do so was not successful because it says that "my connection is unstable...blah" and I'm also afraid of the fact that this update is not approved by Huawei (!) with my IMEI sent.
My question is: Why Firmware finder shows this update even though it's not approved yet by Huawei? and Does anyone had any success with downloading this update without messing up his tablet?
P.S. I'm not living in the US so if I bricked my tablet, I won't have any chance of fixing because it's not sold officially in my country, so your advices are much appreciated.
P.S. Attached is a screenshot of the changelog of this update.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

magoooood said:
I'm using a MediaPad M3 (Wifi only) bought from amazon.com (model: BTV-W09C128) and I discovered by chance, through firmware finder, that there's an update that ends with B352 (my current firmware ends with B351) and I wished I can download this update because it has lots of nice optimizations with battery and touch sensitivity...etc but trying to do so was not successful because it says that "my connection is unstable...blah" and I'm also afraid of the fact that this update is not approved by Huawei (!) with my IMEI sent.
My question is: Why Firmware finder shows this update even though it's not approved yet by Huawei? and Does anyone had any success with downloading this update without messing up his tablet?
P.S. I'm not living in the US so if I bricked my tablet, I won't have any chance of fixing because it's not sold officially in my country, so your advices are much appreciated.
P.S. Attached is a screenshot of the changelog of this update.
Click to expand...
Click to collapse
Yes, like a lot of folks I got the 352 update yesterday OTA. I had previously updated to 351 (Android 7/EMUI 5) from the stock version via FF last month.

drb48 said:
Yes, like a lot of folks I got the 352 update yesterday OTA. I had previously updated to 351 (Android 7/EMUI 5) from the stock version via FF last month.
Click to expand...
Click to collapse
Thanks for the prompt reply however I'm stuck with the boring message "unstable network, trying to connect" when trying to download using the proxy method. Is there any alternative way of applying this update? otherwise, how to circumvent this fake message (as my network is indeed stable)

Mine worked fine. 352 Mb download in 5 minutes, 5 more to update. Working very well, improved battery life.
Enviado de meu BTV-W09 usando Tapatalk

PHP:
apeinej said:
Mine worked fine. 352 Mb download in 5 minutes, 5 more to update. Working very well, improved battery life.
Enviado de meu BTV-W09 usando Tapatalk
Click to expand...
Click to collapse
Could you please share with me your update method? trying to download through firmware finder as a proxy wasn't successful because it said "my connection is unstable...blah". When I stopped the proxy and removed the proxy settings from my wifi connection, I found out that the download begins nomrally but at the end, a verification happens to that update which ended up being deleted because it is not authorized to install (I don't know why!).
I'll appreciate if anyone knows a download link to that update with instructions because I have an SDCard installed to use for this purpose.

It won't be of much help, as I opened the tablet's cover and it was already requesting the update. I just accepted it.
But you can try to force an update search on tablet's config.
Enviado de meu BTV-W09 usando Tapatalk

apeinej said:
It won't be of much help, as I opened the tablet's cover and it was already requesting the update. I just accepted it.
But you can try to force an update search on tablet's config.
Enviado de meu BTV-W09 usando Tapatalk
Click to expand...
Click to collapse
I never got any update from the system updater without the help of firmware finder which helped me go from Android M to Android N with EMUI 5. After that, it's not able to help anymore!
Do you have your huawei account registered on the device? (I tend to beleive that a Huawei account may help in getting the updates directly from Huawei through the updater without the need for buggy 3rd party apps)

Nope, just google account. From moment one it already askes for update - M to N - and the new one from a couple of days ago.

I see that this update is available using the firmware finder app. Can somebody tell me the best way to update on a rooted tablet?

magoooood said:
Thanks for the prompt reply however I'm stuck with the boring message "unstable network, trying to connect" when trying to download using the proxy method. Is there any alternative way of applying this update? otherwise, how to circumvent this fake message (as my network is indeed stable)
Click to expand...
Click to collapse
Not sure since I didn't encounter any problem upgrading to 351 using the proxy method and FF. When I was researching methods at the time, some other folks had upgraded to 351 another way - involved using an SD card as I recall. You could look around for that or continue to see if you can figure out what the issue is with your setup (I'm assuming it's not FF since that worked for me). Did you try using HiSuite to update? That may work as well now since they're pushing the latest update OTA. But the OTA push seems to be country by country and since I'm in the US and you're not your experience may differ. Sorry I can't be more helpful. Good luck.

I'm in the US. Downloaded the OTA but it wouldn't install, since I've got TWRP installed as my recovery.
I used Firmware Finder to download the full update (two .zip files). These do flash with no problem; unfortunately, they reinstalled stock recovery and locked my bootloader. So I had to unlock and then restore the device from backup (along with all the email account setup, etc. which doesn't get restored from backup).

Sounds like those of us who are rooted need to wait until somebody creates an image that can be flashed with TWRP without wiping everything out. Were you able to use the original code to unlock your bootloader again?

woody1 said:
Sounds like those of us who are rooted need to wait until somebody creates an image that can be flashed with TWRP without wiping everything out. Were you able to use the original code to unlock your bootloader again?
Click to expand...
Click to collapse
Yes, fortunately the same bootloader unlock code worked again.

CCarson said:
I'm in the US. Downloaded the OTA but it wouldn't install, since I've got TWRP installed as my recovery.
I used Firmware Finder to download the full update (two .zip files). These do flash with no problem; unfortunately, they reinstalled stock recovery and locked my bootloader. So I had to unlock and then restore the device from backup (along with all the email account setup, etc. which doesn't get restored from backup).[/Q
Love the tablet but its weird, this is my second one after bricking the first, immediately unlocked, twrp installed rooted then enabled 5g which was harder then the first tab I had. The other weird thing is on the first tablet I had to change wifi settings for firmware finder to download with the new one no setting change just clicked download and it did.
Anyway the question is just to verify, so you check both zip files on ota update? I only clicked usa full update and in recovery it failed at 5%, any ideas?
Click to expand...
Click to collapse

Worked fine for me. I use FF method.

chpimentelpr said:
Worked fine for me. I use FF method.
Click to expand...
Click to collapse
Bootloader unlocked and rooted before?

jionny said:
Bootloader unlocked and rooted before?
Click to expand...
Click to collapse
No Root No Bootloader, factory setup. It worked without any issues, No need to root at the moment. I'm using DNS66 to block most of the ads.

BTW Bluetooth works fine...

CCarson said:
I'm in the US. Downloaded the OTA but it wouldn't install, since I've got TWRP installed as my recovery.
I used Firmware Finder to download the full update (two .zip files). These do flash with no problem; unfortunately, they reinstalled stock recovery and locked my bootloader. So I had to unlock and then restore the device from backup (along with all the email account setup, etc. which doesn't get restored from backup).
Click to expand...
Click to collapse
I too could download but not install because I have twrp installed.... How did you flash?

OTA is now downloading b352 for me. U
Not using FF.

New OTA update

Just letting everyone know. OTA security patch update is available
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

The unlocked version is at 29.105-25-13. Do you know where we can download the firmware besides OTA?

Possibly https://support.lenovo.com/au/en/solutions/ht117028
I actually used that to fix my vzw Moto z4. Was stuck in a bootloop. Verizon tech support was going to send me a new phone. But the Lenovo tool allowed me to fix it. Reflash the entire firmware bootloader and all partitions. Try running the tool and try to download software. May or may not work for you

ahalol said:
The unlocked version is at 29.105-25-13. Do you know where we can download the firmware besides OTA?
Click to expand...
Click to collapse
silver03wrx said:
Possibly https://support.lenovo.com/au/en/solutions/ht117028
I actually used that to fix my vzw Moto z4. Was stuck in a bootloop. Verizon tech support was going to send me a new phone. But the Lenovo tool allowed me to fix it. Reflash the entire firmware bootloader and all partitions. Try running the tool and try to download software. May or may not work for you
Click to expand...
Click to collapse
I downloaded software using the Lenovo Moto tool. I wanted to keep track of the software versions, in case I need to try to revert back for any reason. The software that was downloaded for me was:
"FOLES_PPF29.105_44_subsidy_DEFAULT_regulatory_DEFAULT_CFC_xml.zip"
Is this this same version that others received? or what versions do you guys have?
I am still on on PPF29.105-25 (Android security patch level April 1, 2019).
I have the prompt for a pending OTA download/install to PPF29.105-25-13, Android security patch level July 1, 2019.
Judging from the file name of my downloaded image, is there another OTA to "PPF29.105-44"? or is the file name not coinciding with the actual software version (i.e. no such thing as "-44")?

Mangu said:
I downloaded software using the Lenovo Moto tool. I wanted to keep track of the software versions, in case I need to try to revert back for any reason. The software that was downloaded for me was:
"FOLES_PPF29.105_44_subsidy_DEFAULT_regulatory_DEFAULT_CFC_xml.zip"
Is this this same version that others received? or what versions do you guys have?
I am still on on PPF29.105-25 (Android security patch level April 1, 2019).
I have the prompt for a pending OTA download/install to PPF29.105-25-13, Android security patch level July 1, 2019.
Judging from the file name of my downloaded image, is there another OTA to "PPF29.105-44"? or is the file name not coinciding with the actual software version (i.e. no such thing as "-44")?
Click to expand...
Click to collapse
I would also like to know.

ahalol said:
I would also like to know.
Click to expand...
Click to collapse
@ahalol did you try the LMSA tool?, what is the name of the file for the firmware that it let you download?
Also, since I now, at the very least, have the unknown image from the tool (file name FOLES_PPF29.105_44), and what I believe is stock image (file name FOLES_PPF29.105-25) from getdroidtips.com webpage https://www.getdroidtips.com/motoro...e-and-firmware-collections-back-to-stock-rom/
to revert to, if necessary.....I installed the PPF29.105-25-13 OTA.
Just now I also received notification that another OTA is available. See screenshot below. I will do a little research as to what it is before I install..

Mangu said:
@ahalol did you try the LMSA tool?, what is the name of the file for the firmware that it let you download?
Also, since I now, at the very least, have the unknown image from the tool (file name FOLES_PPF29.105_44), and what I believe is stock image (file name FOLES_PPF29.105-25) from getdroidtips.com webpage https://www.getdroidtips.com/motoro...e-and-firmware-collections-back-to-stock-rom/
to revert to, if necessary.....I installed the PPF29.105-25-13 OTA.
Just now I also received notification that another OTA is available. See screenshot below. I will do a little research as to what it is before I install..
Click to expand...
Click to collapse
It is asking me to download FOLES_PPF29.105_44. I guess I will go with this one. My system is rooted and the /system partition was modified (host file). I will manually sideload it.

ahalol said:
I would also like to know.
Click to expand...
Click to collapse
ahalol said:
It is asking me to download FOLES_PPF29.105_44. I guess I will go with this one. My system is rooted and the /system partition was modified (host file). I will manually sideload it.
Click to expand...
Click to collapse
Ok, cool. Let me know after install what Build Number that download corresponds with.
I am not rooted (yet) as I only absolutely care about native hotspot, so I will continue accepting OTAs until the Native hotspot is ever broken.

Mangu said:
Ok, cool. Let me know after install what Build Number that download corresponds with.
I am not rooted (yet) as I only absolutely care about native hotspot, so I will continue accepting OTAs until the Native hotspot is ever broken.
Click to expand...
Click to collapse
It doesn't want me to install. Most likely due to my modification on the Host file. I think I will not update and flash all new when Q comes out.

New OTA available for unlocked Z4
New OTA, software PPFS29.105-25-13-2, provides August 1, 2019 security patch (screenshot below).
Have not noticed any changes. Here is link to Maintenance Release Notes for this software update:
https://support.motorola.com/us/en/solution/MS142802

Strange... I'm with unlocked Z4, too, but with June patch it says it already has current updates...

Maheshwara said:
Strange... I'm with unlocked Z4, too, but with June patch it says it already has current updates...
Click to expand...
Click to collapse
Try rebooting your phone, then check for update.....or check for update at diff times of the day (i.e. after 9pm or if possible around 3-4am)...with a combination of also rebooting and checking again, if no update upon initial try.

I have an unlocked z4 and it also says I'm up to date on June 2019. When I used the LMSA it downloads the -44 file but when it flashes it and fastboots nothing happens. To those of you who are getting updates on the unlocked Z4, which carrier are you using it on? Mine is using a roaming SIM and not a US carrier but even when I swapped out it still didn't work.

kingstu said:
I have an unlocked z4 and it also says I'm up to date on June 2019. When I used the LMSA it downloads the -44 file but when it flashes it and fastboots nothing happens. To those of you who are getting updates on the unlocked Z4, which carrier are you using it on? Mine is using a roaming SIM and not a US carrier but even when I swapped out it still didn't work.
Click to expand...
Click to collapse
I have unlocked version(XT1980-3) on US verizon as carrier.
However, not entirely sure if that matters. I had gotten notification of the previous update (PPF29.105-25-13, June 1st security patch) connected to wifi, before I had ever inserted a SIM into the phone.
Now def on Aug 1st security patch (see screenshot).

New OTA update came through today. Looks to be just the Sept 1 security patch.
Unlocked Z4 on vzw network.

The Amazon version used in Europe is on August patch. When I set it up a initially here, I did get a few updates. Was curious if there will be a difference compared to retail. Seems there is.

Mine is also 105-71
Rooted

Only having bootloader unlocked and running bone stock XT1980-3, while randomly checking for updates, I started getting the message "System Integrity Compromised" and indication that I was not eligible for updates and need to contact customer service.
I ended up patching boot.img with magisk method, and now SafetyNet check passes and a check for update is back to saying "Your device is up to date" (I never even checked anything off under the magisk hide feature, and root checker says I'm rooted).
Best of all, it looks like there is a method for continuing to accept OTAs while retaining root using magisk.

New OTA for unlocked Z4... Oct 1 Security patch:
PPF29.105-75
Stock Rom/Boot (no TWRP), unlocked BL, rooted with Magisk.
Followed instructions for taking OTA while retaining root with Magisk. No issues. Flawless.

Sooo..... I have XT1980-3 with bootloader unlocked purchased directly from Motorola and using T-Mobile. Original Stock, did not flash any other stock FW on top. I was also getting the warnings that I was not able to install a system update because my device was not secure because I unlocked the bootloader........then all of the sudden out of the blue I was able to download and install the update today without doing anything. And now I have the same October Security update that we were probably suppose to get two months ago. LOL! Not complaining I guess, it's just weird.
Hopefully one day we will get some TWRP and Custom Rom love. Sending Positive Energy For This ?

Update not listed in software - "n910cxxu2dvh2"

Recently I reinstalled the system and I did not have time to install SU and an update popped out. Unfortunately, I can't download this version anywhere, either there is a problem or this version does not exist. Can anyone help me with this? The phone is SM-N910C / XEO.
Log from SAMFIRM:
SamFirm v0.5.0
Checking firmware for SM-N910C/XEO/N910CXXU2DVH2/N910COXA2DVH2/N910CXXU2DVH2/N910CXXU2DVH2
Error: Could not send BinaryInform. Status code 200/400
Request was invalid. Are you sure the input data is correct?
Checking firmware for SM-N910C/XEO/N910CXXS2DRI2/N910COXA2DQK1/N910CXXU1DQG1/N910CXXS2DRI2
Model: SM-N910C
Version: N910CXXS2DRI2/N910COXA2DQK1/N910CXXU1DQG1/N910CXXS2DRI2
OS: Marshmallow(Android 6.0.1)
Filename: SM-N910C_1_20181115200627_9ug633aafa.zip.enc4
Size: 2228227696 bytes
LogicValue: iekgyc5u90o1sh58
Click to expand...
Click to collapse
Photos of the version from the phone:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How can you download 1 and 4 files soft for this?

@Tomasz Dulak did you try with old samfirm version?
That doesn't work any longer as Samsung changed its server addresses afaik.
Try SamFirm_Reborn_0.3.6.3.

Still the same :/

Tomasz Dulak said:
Still the same :/
Click to expand...
Click to collapse
May work when you switch to manual and fill the fields below with entries needed.
Had that on a VZW phone as well.
But afaik that will only work if it's the latest stock and for me it seems there's a later one:
XEO-N910CXXS2DRI2-20181204144801.

I also fail to enter manually.
Well, mine isn't there at all, and it's dated August 12, 2022, looking at the kernel version after the update. It's just that someone posted an update after 4 years.
The last one available for today is: "N910CXXS2DRI2", but when you install it, you get the update to "N910CXXS2DVH2".

@Tomasz Dulak How's the progress? Did you flash it with DRI2, or stays with DVH2?

I haven't installed N910CXXU2DVH2 patch yet.
I'm trying to add a Samsung account and receive an error like:
Code:
403
Sorry, the resource you want to access is forbidden, so this request has been refused. If you have any questions, please contact the administrator.
*
WIPV2nullnull_XXXXXXXXXXXXXX_99999-YYYYYYYYYYY.999.
I can easily log in via a web browser.
Can anyone log into Samsung account without this fix?

@ze7zez
I have N910H here and flashed system.img, boot.img, and csc_sec.zip from XEO DRI2 N910C firmware. There's no problem in adding Samsung account.
The problem that I'm facing is that, I couldn't get the DVH2 OTA update, since it will throws me the message of "The operating system on your device has been modified in an unauthorized way..."
It may be fixed if I also flash the bootloader from N910C or might also tweak it, but that's such a painful thing to recover if it went brick, I don't want to risk it yet.

UnknownPlanet said:
@ze7zez
I have N910H here and flashed system.img, boot.img, and csc_sec.zip from XEO DRI2 N910C firmware. There's no problem in adding Samsung account.
The problem that I'm facing is that, I couldn't get the DVH2 OTA update, since it will throws me the message of "The operating system on your device has been modified in an unauthorized way..."
It may be fixed if I also flash the bootloader from N910C or might also tweak it, but that's such a painful thing to recover if it went brick, I don't want to risk it yet.
Click to expand...
Click to collapse
Thanks for the information.
I will insert the SIM card and check again.
I wouldn't risk flashing the bootloader from the N910C to the N910H. Are you sure the system will boot?

@ze7zez
No I'm not sure, I've done a hex compare and they are different. There are 90 out of 1,034,240 bytes of param.bin and 9487 out of 1,632,800 bytes of sboot.bin that is different from N910H bootloader.
That would be tedious trying to decode what makes it differs and thus tweak it..
In the end, I'm stuck with DRI2 firmware. I'd like to try DVH2, but there's no software available that I know at the moment that is able to download it.
Just ask help here again if you need help on your Samsung account.

ze7zez said:
I haven't installed N910CXXU2DVH2 patch yet.
I'm trying to add a Samsung account and receive an error like:
Code:
403
Sorry, the resource you want to access is forbidden, so this request has been refused. If you have any questions, please contact the administrator.
*
WIPV2nullnull_XXXXXXXXXXXXXX_99999-YYYYYYYYYYY.999.
I can easily log in via a web browser.
Can anyone log into Samsung account without this fix?
Click to expand...
Click to collapse
Got that issue on a S8 and 2 S7 Edges. had to send them back

dave678 said:
Got that issue on a S8 and 2 S7 Edges. had to send them back
Click to expand...
Click to collapse
I solved the problem and described in the thread.
dave678 said:
Got that issue on a S8 and 2 S7 Edges. had to send them back
Click to expand...
Click to collapse
I solved the problem and described in the thread.
[STOCK ROM][NO ROOT][Android 4] Correct login to Google account after phone reset
There are devices with android 4 in which after a reset to factory settings or very long ago not updated, there is no way to log in to a Google or Samsung account. Here is a proven repair method. Before you proceed with the repair, you need to...
forum.xda-developers.com

ze7zez said:
I solved the problem and described in the thread.
I solved the problem and described in the thread.
[STOCK ROM][NO ROOT][Android 4] Correct login to Google account after phone reset
There are devices with android 4 in which after a reset to factory settings or very long ago not updated, there is no way to log in to a Google or Samsung account. Here is a proven repair method. Before you proceed with the repair, you need to...
forum.xda-developers.com
Click to expand...
Click to collapse
Too bad your post came way too late as I already returned the devices mentioned. Those devices were running Android 7.0.

ze7zez said:
I solved the problem and described in the thread.
I solved the problem and described in the thread.
[STOCK ROM][NO ROOT][Android 4] Correct login to Google account after phone reset
There are devices with android 4 in which after a reset to factory settings or very long ago not updated, there is no way to log in to a Google or Samsung account. Here is a proven repair method. Before you proceed with the repair, you need to...
forum.xda-developers.com
Click to expand...
Click to collapse
I had this same issue on a Tab S I bought off Ebay and it was luckily solved by downgrading to 5.0.2 Lollipop.