Hey, I just came back to stock rom in my zuk z2 plus. And the stock zui was marshmallow version. So, I decided to upgrade it normally from system update. But!!!! When I clicked on system updated option, it says your system has been root. We are unable to provide you the latest version of the system.
Fix will be appreciated.
Thanks in advance
Edit:- I think it's due to bootloader unlocked
Zukker said:
Hey, I just came back to stock rom in my zuk z2 plus. And the stock zui was marshmallow version. So, I decided to upgrade it normally from system update. But!!!! When I clicked on system updated option, it says your system has been root. We are unable to provide you the latest version of the system.
Fix will be appreciated.
Thanks in advance
Edit:- I think it's due to bootloader unlocked
Click to expand...
Click to collapse
Flash stock via QFIL
Related
I Just received the ota system update for my T-Mobile LG G3, but I am worried about what will happen if I update. Last time I updated my phone with a system update, it bricked my phone completely. Let me know if there's anything that can go wrong. Thanks!
I am running "SR REMiX G3 4.4.2" which is stock based 10r ROM. With the "Furnance Kernel".
I'm not completely sure but I'm pretty sure updating will brick your phone. Just wait until someone here puts out something to flash
As long as you do not have a custom bootloader installed you can update then re-root with http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951 It works fine. I used it without any problems.
Phantisy said:
As long as you do not have a custom bootloader installed you can update then re-root with http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951 It works fine. I used it without any problems.
Click to expand...
Click to collapse
How do i go back to original stock? Can i restore with the backup i did of the original stock thru TWRP and then update?
Sent from my LG-D851 using XDA Free mobile app
I forgot I had TWRP and got stuck in a bootloop of TWRP. I flashed the stock recovery and it booted normally again. Still on 4.4.2 now I no longer see the Lollipop update again. Probably going to have to wait until I get the push from T-Mo again?
I went to check for updates and nothing came through there.
Which stock recovery did you use? And did you only revert to stock recovery ? or did you also revert to stock ROM?
k000 said:
Which stock recovery did you use? And did you only revert to stock recovery ? or did you also revert to stock ROM?
Click to expand...
Click to collapse
I had my stock rom and used this recovery:
http://downloads.codefi.re/d/YbSPSu...LG_G3/flash2/LG_G3_Flash2FixStuckRecovery.zip
Have run into trouble. Was on KDZ 20b andwent back to KDZ 10r, got system update message, downloaded and installed but ran into System UIDs inconsistent message, totally unstable. Do not know what to do now but if nothing works, will try to go back to KDZ 20b because at least my phone was working. Any help appreciated and thnaks much.
I recieved an upgrade notification, I clicked on it but now my phone is stuck in TWRP menu help me please,
http://forum.xda-developers.com/tmobile-lg-g3/help/help-upgraded-t-mobile-ota-lolipop-t3082812
shevin said:
I recieved an upgrade notification, I clicked on it but now my phone is stuck in TWRP menu help me please,
http://forum.xda-developers.com/tmobile-lg-g3/help/help-upgraded-t-mobile-ota-lolipop-t3082812
Click to expand...
Click to collapse
You cannot take OTAs with a custom recovery. Can you use the menu and do you have a backup? You will have to somehow revert to stock or try this http://forum.xda-developers.com/tmobile-lg-g3/general/t-mobile-usa-lp-ota-t3020967/page83. (mjfrank posted "This has been floating around
(@inshadesofgrey gets the credit,") I always recommend downloading and keeping the stock rom on your sd and a clean backup-- after rooting and installing a custom bootloader for the first time-- and saving to pc. Keep us updated
shevin said:
I recieved an upgrade notification, I clicked on it but now my phone is stuck in TWRP menu help me please,
http://forum.xda-developers.com/tmobile-lg-g3/help/help-upgraded-t-mobile-ota-lolipop-t3082812
Click to expand...
Click to collapse
Check this http://forum.xda-developers.com/showthread.php?p=60117595
Just a question that jumped out of curiosity.
Why does the Zenfone bootloop on applying OTA on rooted firmware??
The 2.18 OTA zip has patch files to system apps. I dont see why it should cause bootloop on a rooted device which has all the system apps intact?
And on unrooting, OTA works perfectly. What is the reason?? How does the OTA zip understand that the device has been rooted even if no system apps have been tampered with?
Anyone with knowledge on this please post your reply.
Thank you in advance.
black.pearl said:
Just a question that jumped out of curiosity.
Why does the Zenfone bootloop on applying OTA on rooted firmware??
The 2.18 OTA zip has patch files to system apps. I dont see why it should cause bootloop on a rooted device which has all the system apps intact?
And on unrooting, OTA works perfectly. What is the reason?? How does the OTA zip understand that the device has been rooted even if no system apps have been tampered with?
Anyone with knowledge on this please post your reply.
Thank you in advance.
Click to expand...
Click to collapse
Its probably an OEM root check at runtime, if runtime detects an SU binary the zygote runtime will halt, this could be confirmed with a logcat while booting, its a guess here but im pretty sure thats whats going on.
does this always happen? i mean, is there a way to root the device without getting a boot loop after applying OTA?
SquallDNA said:
does this always happen? i mean, is there a way to root the device without getting a boot loop after applying OTA?
Click to expand...
Click to collapse
I think the other question to be asked is why a fresh install of the pre-rooted firmware allows an OTA to go through with no problems...
I have installed a pre-rooted image on 2 phones now and then done the OTA update.
It seems to check for something altering the system AFTER the firmware is flashed as a pre-rooted firmware does in fact have supersu already installed and will allow the OTA update to work (or at least that has been my experience with 2.18.40.X and 2.19.40.18.).
ultramag69 said:
I think the other question to be asked is why a fresh install of the pre-rooted firmware allows an OTA to go through with no problems...
I have installed a pre-rooted image on 2 phones now and then done the OTA update.
It seems to check for something altering the system AFTER the firmware is flashed as a pre-rooted firmware does in fact have supersu already installed and will allow the OTA update to work (or at least that has been my experience with 2.18.40.X and 2.19.40.18.).
Click to expand...
Click to collapse
what happened after OTA update? did it went boot looping?
asus obviously doesn't want thier devices rooted.
Booted fine, no bootloop or other problems and updated to latest firmware. Either I lucked out and got 2 aberrant Zenfone 2's that update fine with the pre-rooted image or there is some other factor involved.
Just a quick note, I re-flashed a pre-rooted image over the old system. It was the same firmware version, 19.40.18 over 19.40.18 so it essentially just reset to how the pre-rooted image was before supersu was updated. OTA worked fine like this.
ultramag69 said:
Booted fine, no bootloop or other problems and updated to latest firmware. Either I lucked out and got 2 aberrant Zenfone 2's that update fine with the pre-rooted image or there is some other factor involved.
Just a quick note, I re-flashed a pre-rooted image over the old system. It was the same firmware version, 19.40.18 over 19.40.18 so it essentially just reset to how the pre-rooted image was before supersu was updated. OTA worked fine like this.
Click to expand...
Click to collapse
that's awesome. which variant of zf2 do you have? i'm using 551 2gb 1.8ghhz variant under 2.19.40.22.. if you dont mind, can i have the exact same root tutorial you followed?
SquallDNA said:
that's awesome. which variant of zf2 do you have? i'm using 551 2gb 1.8ghhz variant under 2.19.40.22.. if you dont mind, can i have the exact same root tutorial you followed?
Click to expand...
Click to collapse
I have a 4gb 64gb 2.3ghz and a 4gb 32gb 1.8ghz zenfone 2. Both work fine. As I said though I have unlocked the bootloader and rooted prior to doing it this way. It may be the bootloader goes through a check.
Way I rooted was to install the pre-rooted image a long time ago but when I have OTA'd I used the temporary CWM to reroot with latest supersu.
Once I found we could put TWRP on the Zenfone 2 I unlocked the bootloader and then installed TWRP 2.8.7.0(?) though I believe reflashing the pre-rooted image back on may have removed this.
I was using this for a while when the new OTA came out. As I had updated SuperSU I reflashed the pre-root image for the firmware installed (I believe it was 2.19.40.18) then installed the OTA from settings.
When the OTA came out for 2.19.40.22 I reflashed the pre-rooted image on again (2.19.40.20 this time) and then ran the OTA update from the settings again. No boot-loops or anything else wrong... Been running fine since on both though I got the flashing bug and flashed the custom rom SuperZen on my 1.8ghz 32gb Zenfone 2. Again no problems but I haven't tried reverting that back yet...
ultramag69 said:
I have a 4gb 64gb 2.3ghz and a 4gb 32gb 1.8ghz zenfone 2. Both work fine. As I said though I have unlocked the bootloader and rooted prior to doing it this way. It may be the bootloader goes through a check.
Way I rooted was to install the pre-rooted image a long time ago but when I have OTA'd I used the temporary CWM to reroot with latest supersu.
Once I found we could put TWRP on the Zenfone 2 I unlocked the bootloader and then installed TWRP 2.8.7.0(?) though I believe reflashing the pre-rooted image back on may have removed this.
I was using this for a while when the new OTA came out. As I had updated SuperSU I reflashed the pre-root image for the firmware installed (I believe it was 2.19.40.18) then installed the OTA from settings.
When the OTA came out for 2.19.40.22 I reflashed the pre-rooted image on again (2.19.40.20 this time) and then ran the OTA update from the settings again. No boot-loops or anything else wrong... Been running fine since on both though I got the flashing bug and flashed the custom rom SuperZen on my 1.8ghz 32gb Zenfone 2. Again no problems but I haven't tried reverting that back yet...
Click to expand...
Click to collapse
thanks man. i found this, http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596, and i believe you used the 1st method of rooting. i prefer using the 3rd method.
SquallDNA said:
thanks man. i found this, http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596, and i believe you used the 1st method of rooting. i prefer using the 3rd method.
Click to expand...
Click to collapse
I used both 1 and 3... Flashed pre-rooted image then downloaded OTA using system settings and flashed with system update. Didn't download the OTA and copy tophone as system update did this for me...
SquallDNA said:
what happened after OTA update? did it went boot looping?
asus obviously doesn't want their devices rooted.
Click to expand...
Click to collapse
I do not think so.
Why would Asus bother with what YOU do with YOUR phone.
Bootloops are caused if you delete something from the /system directory or modify something on which the system depends upon (e.g. v4a, busybox, etc)
As long as you do not touch any system stuff, Asus wouldn't bother. If they wanted their phones to strictly remain untouched, they wouldn't have released bootloader unlocking tools for the previous gen devices.
[email protected] said:
I do not think so.
Why would Asus bother with what YOU do with YOUR phone.
Bootloops are caused if you delete something from the /system directory or modify something on which the system depends upon (e.g. v4a, busybox, etc)
As long as you do not touch any system stuff, Asus wouldn't bother. If they wanted their phones to strictly remain untouched, they wouldn't have released bootloader unlocking tools for the previous gen devices.
Click to expand...
Click to collapse
They haven't released bootloader unlock tool for the Zenfone 2. By your logic they do care until they release that, then it should no longer matter...
I have a HTC 10 (T-MObile)
Unlocked S-ON
OS 2.51.531.32
I installed successfuly TWRP 3.2.2-0
I have a backup as instructed.
I have system partition mounted and with the option for changes.
WhenI flash this ROM the device went to boot loop.
When I flash the SU with encryption, the device goes to boot loop
Sorry, if I am posting this in the wrong place, I have not been here since I got my M8 long ago.
mpitalua said:
I have a HTC 10 (T-MObile)
Unlocked S-ON
OS 2.51.531.32
I installed successfuly TWRP 3.2.2-0
I have a backup as instructed.
I have system partition mounted and with the option for changes.
WhenI flash this ROM the device went to boot loop.
When I flash the SU with encryption, the device goes to boot loop
Sorry, if I am posting this in the wrong place, I have not been here since I got my M8 long ago.
Click to expand...
Click to collapse
Update your firmware to an oreo firmware, simple as that. Oreo roms do not work on nougat firmwares
Perhaps
Mr Hofs said:
Update your firmware to an oreo firmware, simple as that. Oreo roms do not work on nougat firmwares
Click to expand...
Click to collapse
Thanks for the respond,
but for that I need root, which it is the problem with supersu.
I need root for Sunshine, so I can place oreo on the phone.
Do someone remember which version of Viper works with Nougat and if I need to have the phone root first before flashing the ROM.
mpitalua said:
Thanks for the respond,
but for that I need root, which it is the problem with supersu.
I need root for Sunshine, so I can place oreo on the phone.
Do someone remember which version of Viper works with Nougat and if I need to have the phone root first before flashing the ROM.
Click to expand...
Click to collapse
Alright, i will ask this question.
Why do you need root? Why do you need s-off. Why can't you go back to stock and take the OTA to oreo first, hasn't t mobile released the oreo update yet?
Edit:
At least i found a ruu.exe here
https://androidfilehost.com/?fid=746010030569947237
Thanks to @ziand
That file will bring the phone to box stock and at that time you will be able to update to oreo.
Hi everyone. I've tried multiple times to update my phone to the latest oxygen 9.0.3 version both via OTA and recovery. All the times I've got a failed update message. The phone have unlocked bootloader, the recovery I'm using is twrp 3.2.1 and the oxygen version is the 5.0.8
I don't know if I'm missing something or making mistakes. If someone can help me it will be really appreciate. Thanks in advance
Cricius said:
Hi everyone. I've tried multiple times to update my phone to the latest oxygen 9.0.3 version both via OTA and recovery. All the times I've got a failed update message. The phone have unlocked bootloader, the recovery I'm using is twrp 3.2.1 and the oxygen version is the 5.0.8
I don't know if I'm missing something or making mistakes. If someone can help me it will be really appreciate. Thanks in advance
Click to expand...
Click to collapse
I had the same problem. Locked bootloader and downloaded ota update. Now all is good :good:
Follow this
Cricius said:
Hi everyone. I've tried multiple times to update my phone to the latest oxygen 9.0.3 version both via OTA and recovery. All the times I've got a failed update message. The phone have unlocked bootloader, the recovery I'm using is twrp 3.2.1 and the oxygen version is the 5.0.8
I don't know if I'm missing something or making mistakes. If someone can help me it will be really appreciate. Thanks in advance
Click to expand...
Click to collapse
Unlocked bootloader ...it will erase your storage completely ....as there is a encryption error which they have not yet resolved...
so any way you need to backup ur datas... then use the latest TWRP 3.3 or flash the stock recovery which you can download from oneplus support ....
then install the full rom it will be updated ...
Hi I have a virgin mobile Moto g6 play. I recently rooted it with magisk and installed twrp. I just got a notification that pie OTA is ready however I know it might brick if I install the OTA. What is the best way to go about installing it. Do I have to manually reflash stock Oreo in order to update or is there another way? Thanks for your help.
Uses the Lenovo Moto Assistant. Remembering that the G6 Play stock rom will be installed on your device. That way, there will be no more root (however you can install later) and the memory will be formatted
https:// support.lenovo.com/br/pt/downloads/ds101291
Remove space after two bars
synaethe said:
Hi I have a virgin mobile Moto g6 play. I recently rooted it with magisk and installed twrp. I just got a notification that pie OTA is ready however I know it might brick if I install the OTA. What is the best way to go about installing it. Do I have to manually reflash stock Oreo in order to update or is there another way? Thanks for your help.
Click to expand...
Click to collapse
Just reflash stock firmware and don't root. You cannot install updates from ota once you root
synaethe said:
Hi I have a virgin mobile Moto g6 play. I recently rooted it with magisk and installed twrp. I just got a notification that pie OTA is ready however I know it might brick if I install the OTA. What is the best way to go about installing it. Do I have to manually reflash stock Oreo in order to update or is there another way? Thanks for your help.
Click to expand...
Click to collapse
I just downloaded the full pie firmware from mirrors, flashed with RSDlite (servicefile). Rebooted bootloader, flashed TWRP. Boot to TWRP, flash encryption disabler and magisk.
Still unencrypted, all is well.
Just download the updated firmware from Lolinet and Flash it without erasing data