I tried to update my phone but unfortunately during the installation the one with Red magic logo saying
"Dont operate in system update" it stops at 25%.
Formerly my phone has root access to I reflashed almost all the necessary files such as recovery, boot and system and locked my bootloader again but still the update install fails
Any tips to successfully install updates?
leipnacht said:
I tried to update my phone but unfortunately during the installation the one with Red magic logo saying
"Dont operate in system update" it stops at 25%.
Formerly my phone has root access to I reflashed almost all the necessary files such as recovery, boot and system and locked my bootloader again but still the update install fails
Any tips to successfully install updates?[/QUOTE
You have to uninstall magisk using TWRP recovery
There is magisk_uninstall.zip you have to download from the official magisk site
Download and flash it using TWRP recovery
And then you can easily update
Click to expand...
Click to collapse
em902566 said:
leipnacht said:
I tried to update my phone but unfortunately during the installation the one with Red magic logo saying
"Dont operate in system update" it stops at 25%.
Formerly my phone has root access to I reflashed almost all the necessary files such as recovery, boot and system and locked my bootloader again but still the update install fails
Any tips to successfully install updates?[/QUOTE
You have to uninstall magisk using TWRP recovery
There is magisk_uninstall.zip you have to download from the official magisk site
Download and flash it using TWRP recovery
And then you can easily update
Click to expand...
Click to collapse
I already did that. Some users say that the update fails for them too. I guess the OTA update from Nubia is a bad copy.
We'll wait for Nubia to upload the version 2.31 update on their site.
Click to expand...
Click to collapse
Hello i have the same problem did you resolve it?
Related
Hi all.
This is a moment that I'm disconnected hacks because I am in stock (6.0.401.11) and satisfied. I had OTA updates without problems until this kitkat version but today after receiving and downloading 2 times the OTA lollipop I can not install it because installation starts well and some moments later, the screen is stuck on the phone with red triangle and I have this in the recovery:
Verifying current system ...
"/ System / bin / reboot" has unexpected content
Installation aborted
Even when I do it manually, it's the same. Yet I have just manually switch successfully 6.0.401.12 that I missed somehow.
What's the trouble?
kamso said:
Hi all.
This is a moment that I'm disconnected hacks because I am in stock (6.0.401.11) and satisfied. I had OTA updates without problems until this kitkat version but today after receiving and downloading 2 times the OTA lollipop I can not install it because installation starts well and some moments later, the screen is stuck on the phone with red triangle and I have this in the recovery:
Verifying current system ...
"/ System / bin / reboot" has unexpected content
Installation aborted
Even when I do it manually, it's the same. Yet I have just manually switch successfully 6.0.401.12 that I missed somehow.
What's the trouble?
Click to expand...
Click to collapse
this says to me, in system/bin you have modified files, you must be 100% stock so flash TWRP recovery then use this: https://www.androidfilehost.com/?fid=95864024717072880 to retore full stock rom.
DO NOT try and root or anything, 100% pure stock required.
Full Reboot into android
boot back to recovery and flash this pre-load data here: https://www.androidfilehost.com/?fid=95864024717072879
Full reboot into android
You will need TWRP recovery for both of the above files, but you will also need to flash stock recovery afterwards to update which is here: https://www.androidfilehost.com/?fid=95864024717072472
fastboot flash recovery
fastboot erase cache
fastboot reboot-bootloader
full reboot into android, then update.
DO NOT try and root or anything, 100% pure stock required.
Seanie280672 said:
this says to me, in system/bin you have modified files, you must be 100% stock so flash TWRP recovery then use this: https://www.androidfilehost.com/?fid=95864024717072880 to retore full stock rom.
DO NOT try and root or anything, 100% pure stock required.
Full Reboot into android
boot back to recovery and flash this pre-load data here: https://www.androidfilehost.com/?fid=95864024717072879
Full reboot into android
You will need TWRP recovery for both of the above files, but you will also need to flash stock recovery afterwards to update which is here: https://www.androidfilehost.com/?fid=95864024717072472
fastboot flash recovery
fastboot erase cache
fastboot reboot-bootloader
full reboot into android, then update.
DO NOT try and root or anything, 100% pure stock required.
Click to expand...
Click to collapse
Ok, thank you. But what I don't understand is that there's a long time I'm no more root, I'm full stock (Rom, recovery...), only S-off and Unlocked. So Why for previous OTA updates I have not had this problem? Why I have to manually update successfully from 6.09.401.11 version to 6.09.401.12 one? Why it is only the upgrade to the Lollipop which has problem?
What is the preload data? I already have this: https://www.androidfilehost.com/?w=...0f40a2a319761577a4c3f1e723594b05669cb009e9d00
Can I flash it and the stock recovery only?
Your problem is the lack or corruption of the file /bin/reboot
2 solutions:
Flash a custom recovery and reflash the rom
Flash a custom recovery and replace the file
migascalp said:
Your problem is the lack or corruption of the file /bin/reboot
2 solutions:
Flash a custom recovery and reflash the rom
Flash a custom recovery and replace the file
Click to expand...
Click to collapse
Ok thanks. I'm downloading the Rom and I have to flash it through TWRP, flash stock recovery and try OTA update again.
kamso said:
Ok thanks. I'm downloading the Rom and I have to flash it through TWRP, flash stock recovery and try OTA update again.
Click to expand...
Click to collapse
preload data is HTC's little hidden way of stopping you getting OTA's if you unlock your bootloader, and yes it is required to update, without it, updates will fail.
Seanie280672 said:
preload data is HTC's little hidden way of stopping you getting OTA's if you unlock your bootloader, and yes it is required to update, without it, updates will fail.
Click to expand...
Click to collapse
Ah Ok I understand. These are applications that disappear when we unlock the bootloader. I had already installed them there's a long time. As I said my OTA updates passed without problem.
Problem flashing stock Rom in TWRP:
"- Zip signature verification failed
- Error flashing zip"
I don't understand anything, what's happen?
Problem solved and phone updated. Thank you!!!
Hello
I downloaded the ota and tried to install it normally through the settings. Keep in mind i have been rooted, unlocked my bootloader, and flashed twrp (i flashed stock recovery prior to updating). It goes through the update screen halfway and gives me an error screen, phone with a red exclamation mark. I have the ota.zip backed up and tried flashing it with FlashFire, but it doesn't work. Any help?
RandomTalkingPhone said:
Hello
I downloaded the ota and tried to install it normally through the settings. Keep in mind i have been rooted, unlocked my bootloader, and flashed twrp (i flashed stock recovery prior to updating). It goes through the update screen halfway and gives me an error screen, phone with a red exclamation mark. I have the ota.zip backed up and tried flashing it with FlashFire, but it doesn't work. Any help?
Click to expand...
Click to collapse
Mine too! Root kills install system update. Unless this app developer finds fix to allow.
I deleted memory cache for system app update and update manager. To stop the Notification Bar from staying on. Disable auto system update in Settings. With luck they will find HTC support.
Or restore factory image from backup. Try system update. And root again to preferred image. May work.
So I connected my LG-H811 running stock ROM 20p to my PC successfully and ran adb and fastboot to transfer twrp and supersu over to the phone internal drive. So far so good. I couldn't get twrp to flash properly, so I simply did a temporary boot and got twrp to run without flashing it as a recovery. Then I used twrp to flash supersu (SuperSU-v1.94.zip). The problem is that when I try to reboot, it says the superSU binary is not installed. So I tried newer versions of supersu (SuperSU-v2.76-20160630161323.zip and SuperSU-v2.48.zip). Each time with these newer versions it soft bricked the phone again and required a full stock ROM restore. Specifically, it hangs either on the black LG screen or the white T-mobile screen, while the blue LED flashes on and off every few seconds. To unbrick it each time, I did a restore with stock ROM H811V20p_00_0913.kdz with LGUP. That got it working again with stock ROM, but no root. There must be a way to get superSU to install on 20p (and even get the twrp recovery to flash). I unlocked the bootloader, and it seems to load, so apparently that's not the issue. Thanks.
theprof7 said:
So I connected my LG-H811 running stock ROM 20p to my PC successfully and ran adb and fastboot to transfer twrp and supersu over to the phone internal drive. So far so good. I couldn't get twrp to flash properly, so I simply did a temporary boot and got twrp to run without flashing it as a recovery. Then I used twrp to flash supersu (SuperSU-v1.94.zip). The problem is that when I try to reboot, it says the superSU binary is not installed. So I tried newer versions of supersu (SuperSU-v2.76-20160630161323.zip and SuperSU-v2.48.zip). Each time with these newer versions it soft bricked the phone again and required a full stock ROM restore. Specifically, it hangs either on the black LG screen or the white T-mobile screen, while the blue LED flashes on and off every few seconds. To unbrick it each time, I did a restore with stock ROM H811V20p_00_0913.kdz with LGUP. That got it working again with stock ROM, but no root. There must be a way to get superSU to install on 20p (and even get the twrp recovery to flash). I unlocked the bootloader, and it seems to load, so apparently that's not the issue. Thanks.
Click to expand...
Click to collapse
have twrp .img in sd card and install click on image tab.. then select recovery and flash it.
once it flashes i just flash superSU and get root.
raptorddd said:
have twrp .img in sd card and install click on image tab.. then select recovery and flash it.
once it flashes i just flash superSU and get root.
Click to expand...
Click to collapse
Thanks raptorddd, but that's exactly the problem. I did flash superSU using twrp, and it seemed to install fine. I expected that I would simply get root as you say, but that's not what happened. The first time with SuperSU v1.94 newly installed, the phone rebooted normally, and the superSU app showed up, but it didn't work because it said there was no binary installed. The newer versions of superSU simply soft-bricked the phone. So I need a way to get superSU to work and not soft-brick the phone. Is there a preferred version of superSU for LG-H811 ROM 20p, or some obscure setting that makes it work?
theprof7 said:
Thanks raptorddd, but that's exactly the problem. I did flash superSU using twrp, and it seemed to install fine. I expected that I would simply get root as you say, but that's not what happened. The first time with SuperSU v1.94 newly installed, the phone rebooted normally, and the superSU app showed up, but it didn't work because it said there was no binary installed. The newer versions of superSU simply soft-bricked the phone. So I need a way to get superSU to work and not soft-brick the phone. Is there a preferred version of superSU for LG-H811 ROM 20p, or some obscure setting that makes it work?
Click to expand...
Click to collapse
did you open the app and clicked on update binaries.? if it asks to.?
here mine try this. then update from PS.
https://drive.google.com/file/d/0B90RfjoH13UEbDFBSG5XWVA0ME0/view?usp=sharing
raptorddd said:
did you open the app and clicked on update binaries.? if it asks to.?
here mine try this. then update from PS.
Thanks -- that's the the exact same version of superSU I used earlier (I even ran a diff, and the files are identical). After I flashed this version of superSU on the p20 stock ROM with twrp, it soft-bricked my phone. By that I mean it got to the boot page, and the blue LED pulsed on and off every few seconds, and it never got beyond that. When I flashed superSU v1.94, at least it booted afterward, but when I opened the superSU app, it didn't even give me the option to update binaries -- it just said the binary isn't installed, and so superSU can't run, it exited.
Maybe I'll try flashing an earlier stock ROM and see if that allows superSU to flash and run properly -- not sure which ones are compatible given the anti-rollback versioning.
Click to expand...
Click to collapse
theprof7 said:
raptorddd said:
did you open the app and clicked on update binaries.? if it asks to.?
here mine try this. then update from PS.
Thanks -- that's the the exact same version of superSU I used earlier (I even ran a diff, and the files are identical). After I flashed this version of superSU on the p20 stock ROM with twrp, it soft-bricked my phone. By that I mean it got to the boot page, and the blue LED pulsed on and off every few seconds, and it never got beyond that. When I flashed superSU v1.94, at least it booted afterward, but when I opened the superSU app, it didn't even give me the option to update binaries -- it just said the binary isn't installed, and so superSU can't run, it exited.
Maybe I'll try flashing an earlier stock ROM and see if that allows superSU to flash and run properly -- not sure which ones are compatible given the anti-rollback versioning.
Click to expand...
Click to collapse
try a custom kernel it has superSU installed.. i say imperium kernel.
try first the custom kernel.. if not you can only downgrade to 20o. no lower or youll hard brick phone.
Click to expand...
Click to collapse
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
can you please share what guide you used to unlock and root this phone? I'm having issues on finding it, im on the newest update
theprof7 said:
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
Click to expand...
Click to collapse
Please, can you share what guide you used to unlock and root this phone (20p)? Can not find any complex info anywhere.
Thank you.
theprof7 said:
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
Click to expand...
Click to collapse
May I ask where you downloaded the Imperium_Kernel_G4_H811_v4.8a.zip
Did "fastboot boot twrp-3.0.2-0-h811.img" work?
What version of SuperSu did you install? I am planning on using "SR1-SuperSU-v2.78-SR1-20160915123031.zip"
king200 said:
May I ask where you downloaded the Imperium_Kernel_G4_H811_v4.8a.zip
Did "fastboot boot twrp-3.0.2-0-h811.img" work?
What version of SuperSu did you install? I am planning on using "SR1-SuperSU-v2.78-SR1-20160915123031.zip"
Click to expand...
Click to collapse
You can get the latest Imperium kernel (5.0 currently) from: http://forum.xda-developers.com/g4/orig-development/kernel-imperium-kernel-g4-v1-0-t3282915
Yes, fastboot boot from the twrp image was kind of a hack, but it worked. As for SuperSU, I tried v1.94 and SuperSU-v2.76-20160630161323.zip. Both soft-bricked the phone. Maybe the newest SuperSU will work, but I wouldn't count on it given that several previous versions didn't.
theprof7 said:
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
Click to expand...
Click to collapse
I need to flash twrp and root from 20p also. One question to clarify exactly what you did,
Did you originally try flashing TWRP from TWRP? You said you flashed root from TWRP but I want to verify if you tried flashing TWRP from TWRP like:
> adb reboot bootloader
> fastboot boot twrp-3.0.2-0-h811.img
then in TWRP:
> install click on image tab.. then select twrp-3.0.2-0-h811.img recovery and flash it.
> reboot recovery (should reboot to TWRP you just flashed)
Just to be totally clear doing > fastboot boot twrp-3.0.2-0-h811.img leaves your stock recovery intact and just loads TWRP temporarily.
Or did you actually flash TWRP from TWRP and it didn't flash properly?
Thanks!
emailej said:
Just to be totally clear doing > fastboot boot twrp-3.0.2-0-h811.img leaves your stock recovery intact and just loads TWRP temporarily.
Or did you actually flash TWRP from TWRP and it didn't flash properly?
Thanks!
Click to expand...
Click to collapse
Yes, just loads TWRP temporarily. Later I installed some apps that flashed the recovery successfully, either rashr or flashify (I don't remember which)
I hope you have all the files and pc is reading your phone in adb.
Keep the downloaded twrp file in your adb folder with dwonloaded name (Ex:1234twrp.img)
Copy the file and keep in phone internal storage with names recovery.img
adb reboot bootloader (wait for phone to boot in bootloader ofcourse)
fastboot boot 1234twrp.img (whatever your twrp img file name would be)
Now you are in twrp recovery page in the phone.
Tap Install > Images (bottom right) > select recovery.img >
Now you are in next screen where options to slect recovery or boot
Tap recovery and swipe you will see [image flash complete]
Now twrp is permeant. You can restart in recovery without PC. (Tested)
I have flashed more than 6 methods to install supersu. Keep trying and reply.
I am trying to install the latest Pie Update, but unable to do so, tried local upgrade/install from internal storage, recovery mode, and ADB Sideload, every time same error "Installation failed", I wiped data, erase everything, reset and wipe cache as well, no success. My device is not rooted, it is reset to Oreo Oxygen OS 5.02. Please help
mnaceem said:
I am trying to install the latest Pie Update, but unable to do so, tried local upgrade/install from internal storage, recovery mode, and ADB Sideload, every time same error "Installation failed", I wiped data, erase everything, reset and wipe cache as well, no success. My device is not rooted, it is reset to Oreo Oxygen OS 5.02. Please help
Click to expand...
Click to collapse
maybe a bad/corrupted download
Same issue here, I am unable to update my phone
Sent from my [device_name] using XDA-Developers Legacy app
I just got the same error too.
I also got a warning while i boot back to the old version.
System update failed
Update failed, tap to enter repair mode to try again.
guys, i had the same issue too.
Download the full rom via xda link, installation failed. Same goes for the OTA.
However, I managed to update to stock PIE.
My bootloader was unlocked when using stock OREO.
So what I did was, I RE-LOCKED the bootloader, and reboot the OP3T. (BE WARNED,IT RESET THE WHOLE PHONE)
After fresh installation, i was able to update to PIE via OTA. (Should work with local upgrade too)
So for my case, that helps.
vinoxflame said:
maybe a bad/corrupted download
Click to expand...
Click to collapse
NOPE no bad/corrupted download...
---------- Post added at 09:01 AM ---------- Previous post was at 08:52 AM ----------
Well I was upgraded to the pie with locked bootloader and after that, I had flashed official twrp and magisk but I flashed oreo rom to check if this problem is there when the bootloader is unlocked well yes the one plus detects that your bootloader is unlocked and doesn't deliver the ota so what you can do is click on download upgrade read carefully bro DOWNLOAD not INSTALL just DOWNLOAD it and then you will find it in .ota directory in File Manager now what you have to do is backup your all data via your prefered backup method from which you can restore things after the update I am going to give you a spoiler all data will be corrupted when you will flash the update file via twrp that's why the one plus package updater doesn't update and says installation failed... The pie update will be successfully installed but you have to factory reset your phone to use it that's why I told You to take a backup and after this restore your data...
***I have experienced all this by downgrading and then again upgrading with an unlocked bootloader so I would be honored if you thank me***
I was on stock Pie. I was facing some battery drain issue so I decided to install Oreo official stock which was already downloaded last month. I installed it through local upgrade and rom is still in internal memory. Now I am stuck in Recovery. It tries to boot but every time after few minutes it comes back to recovery. Please help me. It installs Oreo through recovery but unable to boot.
I think Pie can be installed through sideload but I could not find exact links for installation through sideload. Or if there is any option to copy Pie Rom in my internal memory to try installing back latest rom.
If anyone could help me It will be highly appreciated. My bootloader is still locked.
Hello colleagues, I have a mi9 for months and since I installed TWRP with Magisk it is impossible for me to update ...
Neither by OTA nor by recovery or in any way ...
With TWRP I download the OTA, ask for a restart and skip recovery but nothing is installed.
I download the OTA again and go to downloaded_rom I move it to the root of the memory, I start it in TWRP I install it as zip and it only starts me in recovery ...
I tried to remove TWRP and install the recovery stock, I download the OTA it asks me to restart to install, it starts and starts the bar with% of the installation, before 10% it restarts and returns to the system and gives me an error that does not has been able to install the rom, download it again and install ... a thousand times I have done it and the same.
I have tried to remove magisk and the same, I have formatted everything and the same, I have installed the rom by fastboot and more of the same ...
I don't even know what to do ...
What am I doing wrong ??? out there I read and I have not seen anything like it, at most when updating they lose root and recovery and already ...
Can somebody help me??