Related
So I received a notification to download the 5.1 update this morning on my rooted Nexus 6. I proceeded to click download and then install.
However, due to that I had TeamWin recovery installed the update failed on reboot. (didn't even try to install)
Now when I click on "Check for updates" in About in System Settings menu. It says that there are no new updates??? Even though it failed to install.
Does anyone know where the update is stored on the device before installation? Maybe i need to remove it before it will try and update again? (now that i have flashed stock recovery)
Any help would be very appreciated.
You need to unroot too.
Ota can be downloaded online.
d1wepn said:
So I received a notification to download the 5.1 update this morning on my rooted Nexus 6. I proceeded to click download and then install.
However, due to that I had TeamWin recovery installed the update failed on reboot. (didn't even try to install)
Now when I click on "Check for updates" in About in System Settings menu. It says that there are no new updates??? Even though it failed to install.
Does anyone know where the update is stored on the device before installation? Maybe i need to remove it before it will try and update again? (now that i have flashed stock recovery)
Any help would be very appreciated.
Click to expand...
Click to collapse
Once you remove root, try pulling your Sim and rebooting. Let the phone sit, without Sim, and see if update reappears.
rootSU said:
You need to unroot too.
Ota can be downloaded online.
Click to expand...
Click to collapse
I was hoping to use the factory OTA update method for a change. (Always manually update) But might just be easier.
Downloading OTA now. Thanks for the advice rootSU
Evolution_Freak said:
Once you remove root, try pulling your Sim and rebooting. Let the phone sit, without Sim, and see if update reappears.
Click to expand...
Click to collapse
Might give this a try first. Worth a shot. Cheers mate.
OTA update downloads to system/cache folder ... It may get deleted soon after you try installing and restart the phone. You need rooted phone and a file explorer like es file explorer for accessing system folder.
Sent from android one lollypop 5.1
---------- Post added at 12:47 AM ---------- Previous post was at 12:38 AM ----------
Check first whether you have it in your phone already. Rooted phone go to /cache folder you'll find something.Zip there.
Ok so i managed to get the phone to download the OTA again and attempted to install it again. This time with stock recovery.
Everything was looking good but it fails with "error" below the android logo.
Any ideas?
Sorry I can't help you. I don't want that AT&T 5.1 update. So I did what you did and hit install. It of course didn't. I use TWRP also. But the damn 5.1 update is back!
Tappin from my Nexus 6
Any reason you want the OTA? you can install the factory image from here and get the same result without mucking around...
https://developers.google.com/android/nexus/images
Gage_Hero said:
Any reason you want the OTA? you can install the factory image from here and get the same result without mucking around...
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
You only need to flash the system.img file within the Google image using fastboot.
After that, boot into TWRP and reflash SuperSU, XPosed, and anything else you've flashed that resides in /system.
Wipe caches and reboot. Easy, and no app or data loss.
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
um.. you are quite a bit late. this is an old thread, look at the dates. you responded to a question thats 6 month old.
liquidzoo said:
You only need to flash the system.img file within the Google image using fastboot.
After that, boot into TWRP and reflash SuperSU, XPosed, and anything else you've flashed that resides in /system.
Wipe caches and reboot. Easy, and no app or data loss.
Click to expand...
Click to collapse
Except, to be more complete, it might be a good idea to flash everything except data and boot - that is, in case changes are made to radio or anything else, but if changes are done to boot and are required for system or kernel and you don't put stock boot, you're kinda screwed (you'd need a different version of twrp in this case and it probably won't be out).
My point, there really is no complete way to know if flashing just system is enough to get all the security updates unless you look at what the update replaces. That's why I'm looking for the ota.zip
Rocky1988 said:
Except, to be more complete, it might be a good idea to flash everything except data and boot - that is, in case changes are made to radio or anything else, but if changes are done to boot and are required for system or kernel and you don't put stock boot, you're kinda screwed (you'd need a different version of twrp in this case and it probably won't be out).
My point, there really is no complete way to know if flashing just system is enough to get all the security updates unless you look at what the update replaces. That's why I'm looking for the ota.zip
Click to expand...
Click to collapse
And thankfully Google put version numbers to the other files so takes about 15 seconds to realise you only need to flash system. If a change was made to radio you can still flash in exactly the same way as the system and not lose data...
Amos91 said:
And thankfully Google put version numbers to the other files so takes about 15 seconds to realise you only need to flash system. If a change was made to radio you can still flash in exactly the same way as the system and not lose data...
Click to expand...
Click to collapse
How do you check version numbers for the other files? This may be what I'm after!
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
I'm unable to find the latest update in the /system folder (/system/cache doesn't exist on my device) or the /cache folder either.
/data/data/com.google.android.gms/app_download/update.zip
d1wepn said:
Ok so i managed to get the phone to download the OTA again and attempted to install it again. This time with stock recovery.
Everything was looking good but it fails with "error" below the android logo.
Any ideas?
Click to expand...
Click to collapse
Use Flashify to install OTA updates instead.
At last i found it
I have clock work recovery installed on my phone. It refuses to update my OTA factory software update, i searched for it and installed it manually. It was in /data/data/com.tinno.systemupdate/files/googleota/0/update.zip
Hey folks,
NOTE: SOLVED, update below
On my VTR-L09 Single Sim, I flashed TWRP to edit /vendor/etc/hosts and then flashed recovery again. I went a wrong path there and had to flash the original recovery in order to do a factory reset & wipe. My /data-Partition was broken during the process, too, because I was accidentally wiped it
After the fresh wipe, I started the phone again and after it loaded, configured it (without restoring from my backup) and after a couple of seconds my camera app disappeared from the home screen. Dafuq? Since then, I tried to recover it a couple of times.
I am now hoping that the B126-Update brings my camera app back when it arrives via OTA, but until then:
Does anyone have an Idea where my camera app went, and how I can get it back?
Obviously, I checked under the disabled apps.
Thanks for sharing your thoughts
I am on VTR-L09C432B123
UPDATE: I worked out a way of re-flashing an official update without funkyhuawei, check out https://forum.xda-developers.com/p10/development/dev-introducing-redlotus-source-huawei-t3601493
Did you try to install another camera app to see if the camera turn on? it's possible that the data folder of camera to be erased.
Lukx said:
Hey folks,
On my VTR-L09 Single Sim, I flashed TWRP to edit /vendor/etc/hosts and then flashed recovery again. I went a wrong path there and had to flash the original recovery in order to do a factory reset & wipe. My /data-Partition was broken during the process, too, because I was accidentally wiped it
After the fresh wipe, I started the phone again and after it loaded, configured it (without restoring from my backup) and after a couple of seconds my camera app disappeared from the home screen. Dafuq? Since then, I tried to recover it a couple of times.
I am now hoping that the B126-Update brings my camera app back when it arrives via OTA, but until then:
Does anyone have an Idea where my camera app went, and how I can get it back?
Obviously, I checked under the disabled apps.
Thanks for sharing your thoughts
I am on VTR-L09C432B123
Click to expand...
Click to collapse
Have you tried the HiSuite system restore option. I never used it. But if it works like the restore option from Samsung and Sony. You should restart your phone in recovery mode and the original firmware will be flashed?
Hey
thanks for your answers.
The hisuite does not support my model yet (argh).
OpenCamera works fine, whatsapp's camera feature as well....
The Gallery App is still there, by the way.
I'm having the same issue too after an unsuccessful root which required me to factory reset my P10. After factory rest the stock camera app is missing..
Could someone upload their stock camera backup file? It would be much appreciated.
I attached the HwCamera2 folder with apk, lib and oat folder from /system/priv-app.
I'm on VTR-L29C432B123.
Jannomag said:
I attached the HwCamera2 folder with apk, lib and oat folder from /system/priv-app.
I'm on VTR-L29C432B123.
Click to expand...
Click to collapse
Thanks for the file. May I know how do I get it installed?
I navigated through the same directory and found the same files as yours. I tried installing the apk file from both my own and yours but it says it is corrupted.
Thanks, @Jannomag. I have found that most other Huawei-Apps in that priv-app folder are also missing (except I am not entirely sad about many of those). I'll keep digging a bit.
*Update* I just found in my /etc/whitelistedapps.xml points to /vendor/etc/whitelistedapps.xml, which in turn does not exist.
could somebody with a working Camera app please check whether that file /vendor/etc/whitelistedapps.xml exists, and what is written in there?
This is just a straw I am holding on to, not a real trace or hint, though.
Lukx said:
Thanks, @Jannomag. I have found that most other Huawei-Apps in that priv-app folder are also missing (except I am not entirely sad about many of those). I'll keep digging a bit.
*Update* I just found in my /etc/whitelistedapps.xml points to /vendor/etc/whitelistedapps.xml, which in turn does not exist.
could somebody with a working Camera app please check whether that file /vendor/etc/whitelistedapps.xml exists, and what is written in there?
This is just a straw I am holding on to, not a real trace or hint, though.
Click to expand...
Click to collapse
Hy Lukx, i have exactly the same problem. Wanted to root my phone, but I couldnt see the zip file in twrp, so i wiped whole data and did formatting the whole phone. after reboot my camera app was gone, also the themes were disappeared. I tried installing the firmware for my huawei (from a russian site but I dont know if its the right firmware) but it stopped at 5%.
My Phones Build Number is: VTR-L09C432B113
Thanks
stilla98
Funny thing... I am suspecting that some version mismatch of the recovery or boot partition during the Wipe might be the cause, although I do not have any proof of that.
I am currently trying to write a free alternative to funkyhuawei, so we can flash the full firmware easily again. I think i won't be done with that before mid next week, though...
I am using the OpenCamera app in the meantime.
Lukx said:
Funny thing... I am suspecting that some version mismatch of the recovery or boot partition during the Wipe might be the cause, although I do not have any proof of that.
I am currently trying to write a free alternative to funkyhuawei, so we can flash the full firmware easily again. I think i won't be done with that before mid next week, though...
I am using the OpenCamera app in the meantime.
Click to expand...
Click to collapse
So you are telling me, that the funkyhuawei method works? I saw that my Version is supported. Should I try it?
Thanks
stilla98 said:
So you are telling me, that the funkyhuawei method works? I saw that my Version is supported. Should I try it?
Thanks
Click to expand...
Click to collapse
I didn't say that
But as FH reflashes your phone fully, it should do a full recovery. If you feel like investing money into that, why not try? Otherwise, I recommend you wait along with me for another week and see how far I get with my approach, which I promise to release for free...
Lukx said:
I didn't say that
But as FH reflashes your phone fully, it should do a full recovery. If you feel like investing money into that, why not try? Otherwise, I recommend you wait along with me for another week and see how far I get with my approach, which I promise to release for free...
Click to expand...
Click to collapse
Okay , i will wait for it. I will also install the opencamera app.. by the way, do you also have problems with the design? im having only one design and i cannot add more..
stilla98 said:
im having only one design and i cannot add more..
Click to expand...
Click to collapse
I never really use the theme feature, as I have found "my" favorite theme initially and it's now in the Huawei Backup I carry around through reflashes (highly recommended, it stores on SD card). But the "Designs" app seems to show me a couple of designs, yes. I don't want to try downloading them right now, though.
Lukx said:
I never really use the theme feature, as I have found "my" favorite theme initially and it's now in the Huawei Backup I carry around through reflashes (highly recommended, it stores on SD card). But the "Designs" app seems to show me a couple of designs, yes. I don't want to try downloading them right now, though.
Click to expand...
Click to collapse
okay, i hadnt a microsd card since yesterday, i also backed up my phone before wiping and formatting but there are still no themes, i will try installing them on sd card.. thank you for your help
just install via fastboot boot.img recovery.img cust.img system.img
i have same problem but i can fix it
Same problem
Lukx said:
Hey folks,
NOTE: SOLVED, update below
On my VTR-L09 Single Sim, I flashed TWRP to edit /vendor/etc/hosts and then flashed recovery again. I went a wrong path there and had to flash the original recovery in order to do a factory reset & wipe. My /data-Partition was broken during the process, too, because I was accidentally wiped it
After the fresh wipe, I started the phone again and after it loaded, configured it (without restoring from my backup) and after a couple of seconds my camera app disappeared from the home screen. Dafuq? Since then, I tried to recover it a couple of times.
I am now hoping that the B126-Update brings my camera app back when it arrives via OTA, but until then:
Does anyone have an Idea where my camera app went, and how I can get it back?
Obviously, I checked under the disabled apps.
Thanks for sharing your thoughts
I am on VTR-L09C432B123
UPDATE: I worked out a way of re-flashing an official update without funkyhuawei, check out https://forum.xda-developers.com/p10/development/dev-introducing-redlotus-source-huawei-t3601493
Click to expand...
Click to collapse
I have the same problem with my Huawei p10, don't have the camera apk but I can use with the open camera. did you fix the problem? Thank you
been there done that
Guy all you need is follow step on this link to restock rom and start unlock bootloader again
You can try to restore factory settings.
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.
My phone knows there's an update waiting,I know I can't stop it only delay it.
Says its bootloader 7 which may derail option to root in the near future?
If I root and flash a custom rom now before it's to late.........
Doesn't the auto update system toggle enable and disable this feature?
Delgoth said:
Doesn't the auto update system toggle enable and disable this feature?
Click to expand...
Click to collapse
Not really no.
MystaMagoo said:
Not really no.
Click to expand...
Click to collapse
I remember when I first got my device, that toggle comes default switched to ON. That's why my device updated from BL rev4 to rev5 while just sitting there by itself.
That never happened for me again after turning that toggle off. I also set it to not download updates automatically.
So now, it just asks me on every reboot to download the OTAs, but as long as I hit cancel I've never had it update itself without me first hitting the button to initiate. So IDK. It only happened the one time, and it hasn't happened since.
So I feel both options need to be disabled then. And I've had my device since the beginning of this year. If it does start downloading the update hard reboot the device during download and then wipe your cache from recovery. That reset the Download toggle for me when I accidentally pushed download.
Wiping the cache should erase the downloaded OTA anyways. And after it's gone it will just ask you to either download or download/install again.
Delgoth said:
Doesn't the auto update system toggle enable and disable this feature?
Click to expand...
Click to collapse
Delgoth said:
I remember when I first got my device, that toggle comes default switched to ON. That's why my device updated from BL rev4 to rev5 while just sitting there by itself.
That never happened for me again after turning that toggle off. I also set it to not download updates automatically.
So now, it just asks me on every reboot to download the OTAs, but as long as I hit cancel I've never had it update itself without me first hitting the button to initiate. So IDK. It only happened the one time, and it hasn't happened since.
So I feel both options need to be disabled then. And I've had my device since the beginning of this year. If it does start downloading the update hard reboot the device during download and then wipe your cache from recovery. That reset the Download toggle for me when I accidentally pushed download.
Wiping the cache should erase the downloaded OTA anyways. And after it's gone it will just ask you to either download or download/install again.
Click to expand...
Click to collapse
Hi
Ye I do those also.
I read recently you can only put it off only so many times?
I'll do the cache clean if it tries to download itself.
MystaMagoo said:
Hi
Ye I do those also.
I read recently you can only put it off only so many times?
I'll do the cache clean if it tries to download itself.
Click to expand...
Click to collapse
Maybe it has to do with the Installed security policy then? Because you can update your security policy independently of your Build. A newer build will naturally comes with a newer policy, but there is normally an option to update the Security Policy without just downloading a new build.
I can't say I've had entirely the same issue though so I don't know.
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