Database Develop

No August update?

A lot of users are saying they got an update with August security patches and other improvements.
But now it's almost the end of August and I haven't have got any update after the July update.
Build number: LLD-AL10 8.0.0.170(C675)
Varient:Indian
Any help?

1.) Is your boot-loader unlocked ?
2.) Do you have a Custom Kernel or Recovery Installed?
3.) Are you Rooted?
If the answer is yes to any of them then thats why your not getting any OTA's, If Yes is on 1.) then simply issue the fastboot command to relock the device "fastboot oem relock <bootloader-code>" If its yes to 2.) / 3.) Then your going to need to flash the phone back to stock before then relocking the bootloader.

hacktrix2006 said:
1.) Is your boot-loader unlocked ?
2.) Do you have a Custom Kernel or Recovery Installed?
3.) Are you Rooted?
If the answer is yes to any of them then thats why your not getting any OTA's, If Yes is on 1.) then simply issue the fastboot command to relock the device "fastboot oem relock <bootloader-code>" If its yes to 2.) / 3.) Then your going to need to flash the phone back to stock before then relocking the bootloader.
Click to expand...
Click to collapse
1) Was unlocked
2)Had TWRP
3)Was rooted
I switched back to stock because of constant bugs especially the camera(what's the use of keeping a camera oriented phone in the pocket if it's camera is of no use?)
I'd used HuRupdater to flash the firmware. Now bootloader's relocked and everything's working fine except updates.
I think I flashed the wrong firmware maybe ( I forgot the build number so had to guess. I was sure I had an LLD-AL10 and that there was a C675 and 8.0 in the build number. I matched the changelog with that of the last update I got and then I kinda found out that everything matched to LLD-AL10 8.0.0.170(C675) )
Would one stop getting updates if they installed wrong firmware?
Everything works fine except updates.( And the bootloader 'relocked' status in fastboot).
Should I just flash the August update with HuRupdater( that's gonna be a lot of hassle as I have to unlock bootloader and do all those stuff) or can I update via any other method?

Right you can use Firmware finder on your phone which is a good start.
So using FF select then next version up from your current and only select a OTA-MF, then make sure its for your phone by clicking check firmware access.
If its for your phone then simply use the in-app proxie and connect to a wifi point. Once you have done this edit that Wifi via Settings and change the Proxie to Localhost port 8080. Then go the System and Update.
Now it should download the small version OTA to your phone and reboot to try to install it, it it goes thought and installs without error then great, if it errors out when you boot back into android it will offer the Full OTA without using FF to which will then flash proper without losing data then see if OTA's work after that.

hacktrix2006 said:
Right you can use Firmware finder on your phone which is a good start.
So using FF select then next version up from your current and only select a OTA-MF, then make sure its for your phone by clicking check firmware access.
If its for your phone then simply use the in-app proxie and connect to a wifi point. Once you have done this edit that Wifi via Settings and change the Proxie to Localhost port 8080. Then go the System and Update.
Now it should download the small version OTA to your phone and reboot to try to install it, it it goes thought and installs without error then great, if it errors out when you boot back into android it will offer the Full OTA without using FF to which will then flash proper without losing data then see if OTA's work after that.
Click to expand...
Click to collapse
I checked and this is what happened.
FF detected my phone as LLD-AL10C675
The latest update that's is approved is
LLD-AL10 8.0.0.181(C675CUSTC675D1)
It is B181
But that update is from June. So I searched for LLD-AL10 and pressed ok , so that it shows all firmwares for lld al10.
And I think I found the one I have currently installed(build number and changelog matches) LLD-AL10 8.0.0.170(C675CUSTC675D1). It is from 11/7/2018. Everything above says either firmware not approved or has a wierd term cn in the available models section.
This is something I quite don't understand. When I check firmware access it says lld-al10:all-cn.
I think cn stands for China.( Uploading screenshot)
Would it be safe for me to install the update?
Also is it necessary to download the update just above the one I have installed now or can I skip to the latest one?
Sorry if that's a lot of questions.

I'm in a tight corner now.
I can't get any updates using the dns method or the in app proxy method.
This sucks as I was able to get an update using the dns method 3 weeks back. I didn't install it. I checked for updates, it showed updates, then I stopped dns and things went back to how it was(no updates ?). Today I tried again and nothing happened.
Crazy phone?

Are you selecting the smaller updates as it will not work with full ota's any more.
Sent from my LLD-L31 using Tapatalk

hacktrix2006 said:
Are you selecting the smaller updates as it will not work with full ota's any more.
Sent from my LLD-L31 using Tapatalk
Click to expand...
Click to collapse
I tried it with both the small one and full ota update

Well it worked for me from going from LLD-L31c432b133 to LLD-L31c432b136 as the small OTA came down failed to install so then it downloaded the full version are you sure your setting the WiFi to use the proxies using localhost and port 8080?
Sent from my LLD-L31 using Tapatalk

hacktrix2006 said:
Well it worked for me from going from LLD-L31c432b133 to LLD-L31c432b136 as the small OTA came down failed to install so then it downloaded the full version are you sure your setting the WiFi to use the proxies using localhost and port 8080?
Sent from my LLD-L31 using Tapatalk
Click to expand...
Click to collapse
Yup I'm sure I did those right. I tried both the VPN and proxy methods. As I told VPN used to work.
Anyways I'm gonna wait and try it a few more times. Then I might use HuRupdater.
Thanks for your replies man ?

hacktrix2006 said:
Well it worked for me from going from LLD-L31c432b133 to LLD-L31c432b136 as the small OTA came down failed to install so then it downloaded the full version are you sure your setting the WiFi to use the proxies using localhost and port 8080?
Sent from my LLD-L31 using Tapatalk
Click to expand...
Click to collapse
OMFG bro I fixed it.
You see Huawei had rolled out an update for the 'system update' app through playstore. I had updated it. And after I uninstalled the update for it, things are starting to work again ?.
Only 3 questions remains.
1) Can I install firmware that is not approved?
2)Is it necessary to install the update just above the version I
have currently installed?
3)Is it okay if FF says it's approved but has the part LLD-AL10-
all-cn:all ?
Does the cn part matter ?
Would be very grateful if you could help

1) Yes
2) No
3) CN= China. Personally I wouldn't, plus I don't speak Chinese , why would you want to ? I also like having full access to Google playstore.
On an aside, I'm beginning to get the impression you won't be happy till you really brick your phone . :laugh::laugh:

hacktrix2006 said:
Well it worked for me from going from LLD-L31c432b133 to LLD-L31c432b136 as the small OTA came down failed to install so then it downloaded the full version are you sure your setting the WiFi to use the proxies using localhost and port 8080?
Sent from my LLD-L31 using Tapatalk
Click to expand...
Click to collapse
Sparkrite said:
1) Yes
2) No
3) CN= China. Personally I wouldn't, plus I don't speak Chinese , why would you want to ? I also like having full access to Google playstore.
On an aside, I'm beginning to get the impression you won't be happy till you really brick your phone . :laugh::laugh:
Click to expand...
Click to collapse
?That's kinda my thing (I desperately break stuff then fix them)?
Thans ?

hacktrix2006 said:
Well it worked for me from going from LLD-L31c432b133 to LLD-L31c432b136 as the small OTA came down failed to install so then it downloaded the full version are you sure your setting the WiFi to use the proxies using localhost and port 8080?
Sent from my LLD-L31 using Tapatalk
Click to expand...
Click to collapse
I have tried this procedure more than three times and it just doesn't work. I have the same model version C432 and the same firmware B133. I even downloaded the full Ota file and tried through SD card update ("#" #2846579#"#"), still nothing. When I connect it to Hisuite it says that I have the last official version. Any suggestions?

rostropol said:
I have tried this procedure more than three times and it just doesn't work. I have the same model version C432 and the same firmware B133. I even downloaded the full Ota file and tried through SD card update ("#" #2846579#"#"), still nothing. When I connect it to Hisuite it says that I have the last official version. Any suggestions?
Click to expand...
Click to collapse
I used the FF app on mobile then used in app proxie connected to a wifi point and edited the connection to enable proxie on localhost port 8080. I also only downloaded only the small OTA, however it will fail to install then once you rebooted back into android go system update and then press the 3 dots and go for Full Download that will fix it.
Just a point you may have the same Firmware even the same model but they are not made equal.
Also check Google play store app for Huawei System Update it should look like the picture that's attached then click uninstall and reinstall install the app too before starting as reinstalling that app can help alot.

hacktrix2006 said:
I used the FF app on mobile then used in app proxie connected to a wifi point and edited the connection to enable proxie on localhost port 8080. I also only downloaded only the small OTA, however it will fail to install then once you rebooted back into android go system update and then press the 3 dots and go for Full Download that will fix it.
Just a point you may have the same Firmware even the same model but they are not made equal.
Also check Google play store app for Huawei System Update it should look like the picture that's attached then click uninstall and reinstall install the app too before starting as reinstalling that app can help alot.
Click to expand...
Click to collapse
Many thanks for your prompt reply.
So Ive already done all this because it may be related but no luck.Last time I used FF was to get the B133 which already didnt work on the 7th August,I then uninstalled the FF app,stopped the proxy localhost etc. and right after that I did the update check through system update and the B133 FULL was offered to download,so the B133 was made properly through system update right after all the procedure with the FF.

rostropol said:
I have tried this procedure more than three times and it just doesn't work. I have the same model version C432 and the same firmware B133. I even downloaded the full Ota file and tried through SD card update ("#" #2846579#"#"), still nothing. When I connect it to Hisuite it says that I have the last official version. Any suggestions?
Click to expand...
Click to collapse
Try uninstalling the update for the system update app then use the VPN or proxy method.
Maybe the update just hasn't reached you like me.

Fredin_ said:
Try uninstalling the update for the system update app then use the VPN or proxy method.
Maybe the update just hasn't reached you like me.
Click to expand...
Click to collapse
"Maybe the update just hasn't reached you like me"...I will keep that and just have patience. Ive tried everything but there is no update yet....
Many thanks once again for your reply

rostropol said:
I have tried this procedure more than three times and it just doesn't work. I have the same model version C432 and the same firmware B133. I even downloaded the full Ota file and tried through SD card update ("#" #2846579#"#"), still nothing. When I connect it to Hisuite it says that I have the last official version. Any suggestions?
Click to expand...
Click to collapse
rostropol said:
"Maybe the update just hasn't reached you like me"...I will keep that and just have patience. Ive tried everything but there is no update yet....
Many thanks once again for your reply
Click to expand...
Click to collapse
?.

[SOLVED] Pie october update failed

I have TA-1046 with unlocked bootloader (and uninstalled Magisk before try Pie update)...
Pie stable i installed before using adb sideload OTA file (B2N-322C-0-00WW-B01-update.zip) from this thread
Before some days i have notification with OTA October update, but instalation after download failed(screenshot), tryed several times and on more different wifi connection...
Then i also try adb sideload file B2N-322D-0-00WW-B01-update.zip (from same thread as before install Pie stable) and too failed, this method show more info(screenshot):
"Package is for source build 00WW_3_22C but expected 0001_3_22C
Installation aborted"
In Settings/System/AboutPhone/AndroidVersion i have right build_number: 00WW_3_22C (screenshot)
I read in some other threads that someone have same problem, but without reaction, then a create rather this dedicated thread...
Anyone have same problem? And anyone have please sollution for this?
Please don't write if don't have this problem or tips for sollution, keep this thread clean for finding sollution, thanks
UPDATE: Thanks to TomThePhysicist is problem solved, here is howto...

Same problem and I didn't find any solution yet.

Try this : (works for a similar error in 6.1+):
Rename the package to B2N-322D-0-00WW-B01-322C-0-00WW-B01-update.zip
Put in root of internal storage, go to dialer and dial *#*#874#*#*
If it can't find the file, use the original name and re-dial.
I hope it works, please confirm so others can use it.
Broadcasted from Zeta Reticuli

It worked for me mate! Thank you

k3dar7 said:
I have TA-1046 with unlocked bootloader (and uninstalled Magisk before try Pie update)...
Pie stable i installed before using adb sideload OTA file (B2N-322C-0-00WW-B01-update.zip) from this thread
Before some days i have notification with OTA October update, but instalation after download failed(screenshot), tryed several times and on more different wifi connection...
Then i also try adb sideload file B2N-322D-0-00WW-B01-update.zip (from same thread as before install Pie stable) and too failed, this method show more info(screenshot):
"Package is for source build 00WW_3_22C but expected 0001_3_22C
Installation aborted"
In Settings/System/AboutPhone/AndroidVersion i have right build_number: 00WW_3_22C (screenshot)
I read in some other threads that someone have same problem, but without reaction, then a create rather this dedicated thread...
Anyone have same problem? And anyone have please sollution for this?
Please don't write if don't have this problem or tips for sollution, keep this thread clean for finding sollution, thanks
Click to expand...
Click to collapse
It happened with me but at that time my device was restoring applications after hard reset. Once the restoration was completed, it auto installed.

Gravemind2015 said:
Try this : (works for a similar error in 6.1+):
Rename the package to B2N-322D-0-00WW-B01-322C-0-00WW-B01-update.zip
Put in root of internal storage, go to dialer and dial *#*#874#*#*
Click to expand...
Click to collapse
thanks, tried but not success...
update file is found and update process is starting, but after small wait in 17% is stoped and show error window...
tried with dialing and also keep on root of internal storage and reboot, this show notify about system update (not ota notify) with same behavior as dialer method...

jaskiratsingh said:
It happened with me but at that time my device was restoring applications after hard reset. Once the restoration was completed, it auto installed.
Click to expand...
Click to collapse
thanks, i not yet try hard reset now, only before ~month while sideload Pie 3.22C, try wait ~week if find or someone sollution without HR...

proteus119 said:
It worked for me mate! Thank you
Click to expand...
Click to collapse
you have unlocked bootloader?

Worked for me too, thanks!

k3dar7 said:
you have unlocked bootloader?
Click to expand...
Click to collapse
Are you rooted? It's weird, it works for some people but not for others.
I'm trying to guess it it's variant specific or maybe having root is the issue (it's expected on a rooted system).
Broadcasted from Zeta Reticuli

Gravemind2015 said:
Are you rooted? It's weird, it works for some people but not for others.
I'm trying to guess it it's variant specific or maybe having root is the issue (it's expected on a rooted system).
Click to expand...
Click to collapse
i have rooted (using install official Magisk zip release in only booted TWRP) before, when i see first OTA update notification, then i unroot using MagiskManager Uninstall Complete...
then all update i trying (OTA wireless, adb sideload, dial and reboot with file in root with your filename) is without Magisk/MagiskManager installed, "only" with unlocked bootloader

wriggler_ said:
Worked for me too, thanks!
Click to expand...
Click to collapse
you have unlocked bootloader?

k3dar7 said:
you have unlocked bootloader?
Click to expand...
Click to collapse
Nope.

Hard reset won't solve it. Do not bother
k3dar7 said:
thanks, i not yet try hard reset now, only before ~month while sideload Pie 3.22C, try wait ~week if find or someone sollution without HR...
Click to expand...
Click to collapse

I might have a clue on this. I upgraded to Pie from a rooted state (the OTA allowed me exceptionally to upgrade from Oreo to Pie and I said why not!). Now after installing Magisk Manager I noticed that Magisk is already installed! This might be the reason behind this annoying error.

whoknowshimself said:
I might have a clue on this. I upgraded to Pie from a rooted state (the OTA allowed me exceptionally to upgrade from Oreo to Pie and I said why not!). Now after installing Magisk Manager I noticed that Magisk is already installed! This might be the reason behind this annoying error.
Click to expand...
Click to collapse
ok, i go try OTA dial update after install Magisk
edit: same as without Magisk, failed at 17%...

Of course it should fail. What I mean is it fails because we don't have stock boot. Like in Oreo when it was not possible to use OTA with patched boot, it is not available for Pie. They just made it available for Oreo to Pie update and that has messed everything up.
k3dar7 said:
ok, i go try OTA dial update after install Magisk
edit: same as without Magisk, failed at 17%...
Click to expand...
Click to collapse

I was on an unlocked bootloader with Magisk installed and encountered the same update failed error. I tried uninstalling Magisk via total uninstall and ended up soft bricking the phone, unable to apply any OTA update. The firmware flashing tool also did not work. The good news was I was still able to access Download Mode and Fastboot mode. I ended up sending it to the service center after relocking the bootloader and they flashed the official firmware at no charge. The phone then updated to Pie on first boot after downloading the update, and then wanted to update to the October update after a restart. The weird thing is the October update failed again, inspite of locked bootloader and no root! However, when I checked the phone few hours later, the update seems to have gone thru just fine. Not sure why this October update is a bit wonky. I agree with the above poster; not having patched boot is the issue here. However, we should be able to get this by extracting payload.bin and using magisk to patch the file.
For now, I am back on a locked bootloader and no root. Awaiting more stability in the unlocking/rooting scene before I try again. Unless Nokia releases official bootloader unlock, I will have to firmware flash back to Oreo, as both A/B partitions are occupied by Pie and the hack used to unlock the bootloader has already been patched on Pie.

Hi. Thanks for the input and your detailed comment. The thing is there is no service centre here in my country! So I should do everything my own. But may I ask how you relocked the bootloader?
ganja_guru said:
I was on an unlocked bootloader with Magisk installed and encountered the same update failed error. I tried uninstalling Magisk via total uninstall and ended up soft bricking the phone, unable to apply any OTA update. The firmware flashing tool also did not work. The good news was I was still able to access Download Mode and Fastboot mode. I ended up sending it to the service center after relocking the bootloader and they flashed the official firmware at no charge. The phone then updated to Pie on first boot after downloading the update, and then wanted to update to the October update after a restart. The weird thing is the October update failed again, inspite of locked bootloader and no root! However, when I checked the phone few hours later, the update seems to have gone thru just fine. Not sure why this October update is a bit wonky. I agree with the above poster; not having patched boot is the issue here. However, we should be able to get this by extracting payload.bin and using magisk to patch the file.
For now, I am back on a locked bootloader and no root. Awaiting more stability in the unlocking/rooting scene before I try again. Unless Nokia releases official bootloader unlock, I will have to firmware flash back to Oreo, as both A/B partitions are occupied by Pie and the hack used to unlock the bootloader has already been patched on Pie.
Click to expand...
Click to collapse

whoknowshimself said:
Hi. Thanks for the input and your detailed comment. The thing is there is no service centre here in my country! So I should do everything my own. But may I ask how you relocked the bootloader?
Click to expand...
Click to collapse
Sure, I followed the instructions here https://www.techmesto.com/lock-nokia-android-bootloader/ . However, if there is no service center in your country and you don't plan to do a warranty claim, I've read that relocking the bootloader will prevent you from using the firmware flashing tool.

Note 8 T-Mob downgrade after update to Pie Beta

Hey All, any chance of getting a step by step to downgrade back to CRK1 or latest Oreo build. I attempted to do so, using the firmware from SamMobile, and it failed during the "Updating System" step with an "Error!" message at 32%. Odin had registered a pass. I installed the Ap, Bl, Cp, and the clean CSC. There was only 30ish percent of battery remaining if that would make a difference. I also had the December update installed when I updated to the DLR6 version.

pzzamakr1999 said:
Hey All, any chance of getting a step by step to downgrade back to CRK1 or latest Oreo build. I attempted to do so, using the firmware from SamMobile, and it failed during the "Updating System" step with an "Error!" message at 32%. Odin had registered a pass. I installed the Ap, Bl, Cp, and the clean CSC. There was only 30ish percent of battery remaining if that would make a difference. I also had the December update installed when I updated to the DLR6 version.
Click to expand...
Click to collapse
logs from odin? Or any error code or anything?

Nothing from Odin at all. Odin registered it as a Pass. And I'm unsure how I would pull logs from the phone. Once the "Error!" appears during update, the phone will enter a bootloop unless I hold down the power button to enter Recovery. I was able to successfully enter Recovery, reinstall the Pie Beta Update from my SD card, and the phone works fine again. However, I do use Samsung Pay, and I've noticed that service has suffered considerably, so I'd like to go back to Oreo for the moment.

pzzamakr1999 said:
Nothing from Odin at all. Odin registered it as a Pass. And I'm unsure how I would pull logs from the phone. Once the "Error!" appears during update, the phone will enter a bootloop unless I hold down the power button to enter Recovery. I was able to successfully enter Recovery, reinstall the Pie Beta Update from my SD card, and the phone works fine again. However, I do use Samsung Pay, and I've noticed that service has suffered considerably, so I'd like to go back to Oreo for the moment.
Click to expand...
Click to collapse
I wouldnt be suprised if samsung locked going back same what they did with nougat/oreo . I cant help u, sry

pzzamakr1999 said:
Hey All, any chance of getting a step by step to downgrade back to CRK1 or latest Oreo build. I attempted to do so, using the firmware from SamMobile, and it failed during the "Updating System" step with an "Error!" message at 32%. Odin had registered a pass. I installed the Ap, Bl, Cp, and the clean CSC. There was only 30ish percent of battery remaining if that would make a difference. I also had the December update installed when I updated to the DLR6 version.
Click to expand...
Click to collapse
Which ODIN are you using? Make sure you're using the modded 3.13.1. Try this: Uncheck the auto-reboot option on ODIN. Flash the Oreo firmware and let it finish. Once it's done, manually reboot into recovery and perform a factory reset. Then boot into the OS.
ScaleneVirus288 said:
I wouldnt be suprised if samsung locked going back same what they did with nougat/oreo . I cant help u, sry
Click to expand...
Click to collapse
That only happens when they update the bootloader version. It has nothing to do with the OS version. The Pie leaks are still on the v5 bootloader.

Ok, I will give that a try. I will admit, I'm really enjoying Pie, and its user interface tweaks. I just may forego Samsung Pay and wait until Pie is out of Beta.
On that note, is there any way to install the old radio and use the Oreo radio rather than the one bundled with Pie, assuming that Pie has a new radio bundled. Because that is kinda the Beta killer.
And last comment, once Pie is out of Beta, what will I have to do to upgrade to the "Release" version. Will it be an Odin install, or should an OTA take care of it?

pzzamakr1999 said:
Ok, I will give that a try. I will admit, I'm really enjoying Pie, and its user interface tweaks. I just may forego Samsung Pay and wait until Pie is out of Beta.
On that note, is there any way to install the old radio and use the Oreo radio rather than the one bundled with Pie, assuming that Pie has a new radio bundled. Because that is kinda the Beta killer.
And last comment, once Pie is out of Beta, what will I have to do to upgrade to the "Release" version. Will it be an Odin install, or should an OTA take care of it?
Click to expand...
Click to collapse
Also check the USB port, use the older USB port this has happened to me or PC and see the phone is probably not compatible with newest USB port....
Sent from my SM-N960U using Tapatalk

pzzamakr1999 said:
Ok, I will give that a try. I will admit, I'm really enjoying Pie, and its user interface tweaks. I just may forego Samsung Pay and wait until Pie is out of Beta.
On that note, is there any way to install the old radio and use the Oreo radio rather than the one bundled with Pie, assuming that Pie has a new radio bundled. Because that is kinda the Beta killer.
And last comment, once Pie is out of Beta, what will I have to do to upgrade to the "Release" version. Will it be an Odin install, or should an OTA take care of it?
Click to expand...
Click to collapse
What issues are you having with Spay? It seems to work for everyone else, me included.
No, you can't flash a different radio.
Not sure yet what will be required when when the official drops. Won't know until it drops.

So the Pay app opens fine, and it authenticates the card without issue. It will also allow me to put my fingerprint in, and then have the countdown start. However, it doesn't seem to enable the mag spoofer or the nfc chip, and when put next to a mag reader or Pay system, nothing happens. The countdown will continue, and will restart if I ask it to. But again, the phone doesnt seem to do anything.

pzzamakr1999 said:
So the Pay app opens fine, and it authenticates the card without issue. It will also allow me to put my fingerprint in, and then have the countdown start. However, it doesn't seem to enable the mag spoofer or the nfc chip, and when put next to a mag reader or Pay system, nothing happens. The countdown will continue, and will restart if I ask it to. But again, the phone doesnt seem to do anything.
Click to expand...
Click to collapse
Weird. I'll have to try it. I thought it was working, but now I'm not sure. I use my Gear S3 so often to pay, now I'm not sure LOL.

Update on the effort to revert back to CRK1.
Used the modified Odin, and un-checked auto-reboot. Phone remained in Download mode.
I could not figure out a way to go from Download mode to recovery mode directly. If someone knows how to do this, it would be appreciated if you could let me know.
However, rather than the "Error!" message, I received a "Erasing" message. Than the phone rebooted, and just kept rebooting, going from T-Mobile splash screen to Samsung and back over and over, with some optimizing apps screens thrown in for good measure.
So I tried again with auto-reboot on, and this time received the "Error!" message, and was able to go into recovery once that happened.
The odd thing is, nothing on my phone was changed, other than having to redo the Samsung biometrics for security. All of my apps and accounts and emails were already there, undeleted.

One more update on the S-Pay. After reinstalling the Update.zip from my SD card in Recovery, iIt does seem like there may have been a change. It is now doing the vibrate thing, which I don't think it was doing before. I will put it to the test later this week.

Downgrade Successful
Performed Factory Reset from Phone menus. (not doing so kept resulting in an unauthorized factory reset prompt)
Performed Factory Reset from Recovery Menu.
Cleared Cache through Recovery Menu
Used Patched Odin
Kept Auto-Restart Checked
Used SamMobile CRK1
Phone restarted successfully.

pzzamakr1999 said:
Performed Factory Reset from Phone menus. (not doing so kept resulting in an unauthorized factory reset prompt)
Performed Factory Reset from Recovery Menu.
Cleared Cache through Recovery Menu
Used Patched Odin
Kept Auto-Restart Checked
Used SamMobile CRK1
Phone restarted successfully.
Click to expand...
Click to collapse
Yes! I'm sorry I thought I told you to try a factory reset. You have to factory reset when downgrading. Otherwise bootloop city. Sorry I wasn't more clear, I could've saved you some frustration.
---------- Post added at 11:18 AM ---------- Previous post was at 11:17 AM ----------
I just went back and re-read my posts. I never said try a factroy reset first. Grrr...I'm so sorry!

Mr. Orange 645 said:
Yes! I'm sorry I thought I told you to try a factory reset. You have to factory reset when downgrading. Otherwise bootloop city. Sorry I wasn't more clear, I could've saved you some frustration.
---------- Post added at 11:18 AM ---------- Previous post was at 11:17 AM ----------
I just went back and re-read my posts. I never said try a factroy reset first. Grrr...I'm so sorry!
Click to expand...
Click to collapse
No worries, and I did very much appreciate the help. I should have realized that that should come first. I was a bit frustrated and wasn't thinking logically. It was actually the "fixing apps" message you get when you upgrade that clued me in I wasn't properly resetting the phone prior to install.
Regardless, its all good, and now that I know how to do it, I'll be more inclined to try these out in the future.

Any specific reason for the downgrade? Anything not working?

Camera issues on pie beta
My ar emoji not working on this pie update and sometimes force closes any1 else having this issue

Fitted2 said:
My ar emoji not working on this pie update and sometimes force closes any1 else having this issue
Click to expand...
Click to collapse
Yes

Mr. Orange 645 said:
Yes
Click to expand...
Click to collapse
You downgraded because no AR emoji? And what force closes are you having?

dami00976 said:
You downgraded because no AR emoji? And what force closes are you having?
Click to expand...
Click to collapse
I never said I downgraded.

Can't update to WW1908 from WW1907

On PKQ1.19041.001.WW_Phone-16.0622.1907.33-0
Copied this file ( UL-ASUS_I001_1-ASUS-16.0631.1908.12-1.1.3-user.zip ) from ASUS update server to my ASUS phone to the root folder (internal storage) it sees the file and I get a message saying that my phone can be updated. But when I click ok to upgrade, it fails.
Anyone try this and successful? Any ideas what the heck I am missing here?!
TY

Maybe corrupted download? Try downloading again.
I had a corrupted download and ended up bricking my phone. Had to flash the Raw 1906 then incrementally update to 1908

stealthj said:
Maybe corrupted download? Try downloading again.
I had a corrupted download and ended up bricking my phone. Had to flash the Raw 1906 then incrementally update to 1908
Click to expand...
Click to collapse
Let me download it again. Hope it works. If this does work, I will feel a lot better about updating my awesome phone in the future. Coming from Samsung on AT&T hopefully ASUS keeps the updates fairly regular.

Nope, still not working. Oh well, guess I can wait for the raw version.
But if anyone has any ideas on what I am missing, please chime in.

jkeener88 said:
On PKQ1.19041.001.WW_Phone-16.0622.1907.33-0
Copied this file ( UL-ASUS_I001_1-ASUS-16.0631.1908.12-1.1.3-user.zip ) from ASUS update server to my ASUS phone to the root folder (internal storage) it sees the file and I get a message saying that my phone can be updated. But when I click ok to upgrade, it fails.
Anyone try this and successful? Any ideas what the heck I am missing here?!
TY
Click to expand...
Click to collapse
If you haven't changed the fingerprint to WW yet, the OTA file will be recognized and fail. Change fingerprint and you should be good

xxBrun0xx said:
If you haven't changed the fingerprint to WW yet, the OTA file will be recognized and fail. Change fingerprint and you should be good
Click to expand...
Click to collapse
I never set a fingerprint. so if I set one now, and then try the update it might work? I guess I will try that and see what happens.

jkeener88 said:
I never set a fingerprint. so if I set one now, and then try the update it might work? I guess I will try that and see what happens.
Click to expand...
Click to collapse
It's not a physical fingerprint, it's how the phone identifies itself. Follow this guide: https://forum.xda-developers.com/ro...w-rom-changing-cn-fingerprint-t3969765/page12

jkeener88 said:
I never set a fingerprint. so if I set one now, and then try the update it might work? I guess I will try that and see what happens.
Click to expand...
Click to collapse
you probably got a Chinese 8gb version with flashed WW firmware, which means no OTA anymore. You gotta flash manually after unlocking the bootloader, rooting and so on.

skromnia said:
you probably got a Chinese 8gb version with flashed WW firmware, which means no OTA anymore. You gotta flash manually after unlocking the bootloader, rooting and so on.
Click to expand...
Click to collapse
Thanks, ya learning a lot on this phone. Just got figure it all out without bricking my ROG!

xxBrun0xx said:
It's not a physical fingerprint, it's how the phone identifies itself. Follow this guide: https://forum.xda-developers.com/ro...w-rom-changing-cn-fingerprint-t3969765/page12
Click to expand...
Click to collapse
Thank you so much for pointing me in the right decision, and also although I don't see that many Subaru vehicles in Houston, I plan on getting one this year or maybe next year. Thanks again, up to 1908 now. :good:

Chinese 8gb Tencent q
I'm on 1906 ww. I understand this phone needs a manual flash each time, do I need to flash with every update using raw files and will this also wipe the phone so every update means a wipe?
Can I root, install twrp and simply update the firmware no issue or is it bs?

How do I actually manually update to this? When I hold down on the options button and choose "more options", it still only says Auto-Download System Update
Do I need to flash through fastboot?
Edit: Nevermind, I restarted my phone and it gave me a pop up saying it sees the update

viper98 said:
How do I actually manually update to this? When I hold down on the options button and choose "more options", it still only says Auto-Download System Update
Do I need to flash through fastboot?
Edit: Nevermind, I restarted my phone and it gave me a pop up saying it sees the update
Click to expand...
Click to collapse
i just update to to latest one
u need twrp
put twrp and magisk and the update on root of ur device
flash twrp it will crash first time the next restart will work without any problem
flash and select the latest ota update that u downloaded from asus it take some time
then flash twrp again then flash magisk after all done reboot
work for me no problem

Question System Update Issue (Fixed)

Last night I did the system update and left it overnight. This morning the update wasn't installed and asked me to update again. So I started it again 3 hours ago and it's still not done. Anyone else's update taking this long?
Update: I attempted the system update again and left it overnight. This morning it's still stuck on the same installing screen.
Can someone share the Android Version screen of an unlocked Pixel 7. I think I might be updated and the update is just a bug?
Update: I determined I had an OTA update failure. So I just adb sideloaded the OTA file and it's fixed now.

KillerDroid96 said:
Last night I did the system update and left it overnight. This morning the update wasn't installed and asked me to update again. So I started it again 3 hours ago and it's still not done. Anyone else's update taking this long?
Click to expand...
Click to collapse
I saw your previous post about wifi not staying on. So if that happening while dl. It my screw it. Because it's jumping back to network data and the setting maybe set to only update over wifi.

ern88 said:
I saw your previous post about wifi not staying on. So if that happening while dl. It my screw it. Because it's jumping back to network data and the setting maybe set to only update over wifi.
Click to expand...
Click to collapse
It's set to mobile data and that should only impact the downloading not installing. 4 hours now and still stuck. I'm considering rebooting at this point.

I had the same problem, i rebooted and it all seems gone. But I checked the factory images and everything is up to date.

Giovanni9518 said:
I had the same problem, i rebooted and it all seems gone. But I checked the factory images and everything is up to date.
Click to expand...
Click to collapse
That didn't work. I'm back at the same screen as before after hitting restart now. I also noticed that Google play system update is on July.

KillerDroid96 said:
That didn't work. I'm back at the same screen as before after hitting restart now. I also noticed that Google play system update is on July.
Click to expand...
Click to collapse
My Google play system also states that too.

Well I give up. I restarted and I'm just not going to update for the time being.

ern88 said:
My Google play system also states that too.
Click to expand...
Click to collapse
I think I'm actually fully updated and its just a bug?

@ern88 can you share a screenshot of your Android Version screen please. I'm trying to determine if I'm fully updated and its just a bug.

KillerDroid96 said:
@ern88 can you share a screenshot of your Android Version screen please. I'm trying to determine if I'm fully updated and its just a bug.
Click to expand...
Click to collapse
Here is the ver I'm on. I see you still are on the factory version. Not the Oct update. By chance. Did your carrier give you a new sim card with your phone? Telus have me a new sim card when I bought the phone.

ern88 said:
Here is the ver I'm on. I see you still are on the factory version. Not the Oct update. By chance. Did your carrier give you a new sim card with your phone? Telus have me a new sim card when I bought the phone.
Click to expand...
Click to collapse
Thanks! I determined I had an OTA
update failure. So I just adb sideloaded the OTA file and it's fixed now.

So I'm having the same issue, but potentially for a different reason.
I'm rooted. Typically to resolve this issue, you
1 - select Uninstall Magisk/Restore Image. This restores your stock boot image
2 - Install OTA update
3 - You then install Magisk again once the update completes and select "flash to inactive slot" prior to reboot.
The Uninstall/image restore in Magisk is not removing Magisk and the update still fails.
I'm wondering if it is restoring the boot.img, when it is the initboot.img that has been modified.
I could be wrong, just thought I'd note my issue.

gorilla p said:
So I'm having the same issue, but potentially for a different reason.
I'm rooted. Typically to resolve this issue, you
1 - select Uninstall Magisk/Restore Image. This restores your stock boot image
2 - Install OTA update
3 - You then install Magisk again once the update completes and select "flash to inactive slot" prior to reboot.
The Uninstall/image restore in Magisk is not removing Magisk and the update still fails.
I'm wondering if it is restoring the boot.img, when it is the initboot.img that has been modified.
I could be wrong, just thought I'd note my issue.
Click to expand...
Click to collapse
They've covered this in the two big threads regarding unlocking / rooting in the 7 Pro-forum.