Recently updated to 10.3.4 but having an issue with one of my games. I've tried everything I can think of to fixing it, including resetting the device and starting fresh. Only thing left for me to do would be to downgrade to the previous update.
I am rooted, with xXx and Renovice ICE running, would like to continue using them.
Would the easiest way to downgrade be to download 10.3.3 full OTA, wipe everything in TWRP, flash the OTA, then flash magisk?
If going to an older security patch you might need to format /data and start over.
Related
Hello everybody, I hope to find help here.
My phone is the HTC One A9, Europe Version ("hiaeuhl"). Recovery is TWRP 3.0.2-0.
The background story is that I already managed to install Cyanogenmod after downgrading the original ROM to Version 1.10 and unlocked the bootloader with the HTC Unlock tool. I also managed to decrypt the device.
I'd like to update my system regularly, but unfortunately the last running version is the cm-13.0-20160904-NIGHTLY-hiaeuhl.zip from September 4th.
If I try to install the latest versions of Cyanogenmod (for example from September 9th) I always get the error
hiae.veryfy.trustzone() failed to read current TZ version: -2
Updater process ended with ERROR 7
I already tried to remove the lines that check this in the file updater_script inside the ROM's zip, then I could install the update, but afterwards I was stuck in a boot loop.
The error has nothing to do with the encryption, it apears with and without device encryption, and it has nothing to do which system (original or custom) is installed before flashing. It is also indifferent if I try the update via the system's update function or directly in TWRP. It's the fact that the Cyanogenmod version from September 4th is the last working for me. I definetly chose the right one for hiaeuhl, but it seems the developers have added a feature that makey my device incompatible to this ROM.
If there is anything I can do to update my system again, please let me know.
Have the same issue.
We need to update it, but I don't know how
jira.cyanogenmod.org/browse/NIGHTLIES-3351
Here is how I could solve the issue:
- flashing the latest stock firmware (and let it possibly completely update)
- install TWRP via fastboot
- from TWRP a factory reset
- install new version of the Cyanogenmod from TWRP
It worked for me, now I can use my beloved custom Rom
The Same Problem
I have exactly the same Problem, last working CM-Update was the 3rd September
Did you try my solution? With the older CM Rom versions for the HTC A9 you had to downgrade the stock rom, otherwise the CM wouldn't have started after the installation. Now it seems that the stock rom has to be the latest one (for me the 1.56) that you are able to flash the latest CM versions.
I do not have the latest stock Rom, my os is 1.27.161.6, seems actually cm needs 1.57, i am unlocked and s-off
You should probably find the right version for your phone here:
http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
You should take the one with the right cid for your phone (which you can find with "fastboot getvar all" in the fastboot mode)
Thanks, i will try it and report
The last build i found for my version is 1.27. this is what i have
Hmmm... then I guess you have to wait until the new version appears in the forum. Seems that you have a device with vodafone branding. Since you already set S-off you also have the possibility to change your cid to one of the existing newer firmwares.
Is there a solution without going back to stock?
I'm not an expert, but I don't think so. It seems that the version number of the stock rom is stored somewhere even after changing the system to Cyanogenmod, and this version has to be the latest one. So unfortunately, as far as I know, you'll have to do the flashing procedure again...
thanks Silberhase, now i am on CM 13 again. Thats what i did: wrote Supdercid, searched a ruu-version for my build, found a 1.56.401.70 version, flashed this, then flashed twrp 3.0.2.0 again, factory reset - without factory reset i was not able to install cm, format data, recovery, latest cm update, flash gapps, restore my other data with titanium, done....
I'm glad to hear it worked for you!
Yes, but next Problem or better i actually do not know what problems will raise. After updating today successfully to last cm build phone is encrypted... TWRP requires password for decryption. Problem all over forums. Today i habe no fun to Format data again and restore all.
That's also what I experienced. Other users reported that the current TWRP version 3.0.2.0 can't handle the encryption of the HTC One A9. And every update will encrypt the device again. As a workaround you can do this:
- copy the downloaded update from /sdcard/cmupdater to the external memory card
- boot to the recovery (when asked for password push the cancel button) and install both the update and the gapps again (without wiping anything) from the memory card.
Its a pity, all worked perfectly. Installed last cm.. Which encrypted phone. Restored my backup. All Working. Updated apps, want backup again.... .... Error opening /system/addon.d (not a directory)..error in generating tarlist......Create tarfork()
Process Ended with error 255
I'm trying to help as much as I can even though I have no experience with all this. I never did a backup
Maybe you find the answer here:
http://forum.xda-developers.com/nexus-6/help/e-createtarfork-process-error255-t3302462
Maybe it helps to mount "system" in TWRP and then delete /system/addon.d. But it seems that this step has to be repeated before every backup.
Any news to this theme? Is Twrp able to handle A9 again in new Version?
The recent version 3.0.2.0 of TWRP is available for the A9 but can't handle it's encryption. It works anyway if you are willing to use some workarounds.
I have the original Android 8.0 system and software version 2.33.401.19. Two days ago, my HTC announced that there is a new update to android 9.0. It downloads it and tries to install it. After reboot, TWRP starts and I choose to restart the system. Nothing is updated, and after a while I see a message that the update file is damaged.
A few weeks ago I unlocked the bootloader, ripped the phone and installed TWRP and MagiskManager. I suspect that the unlocked bootloader causes these problems. What should I do to install this update?
Szturwal said:
I have the original Android 8.0 system and software version 2.33.401.19. Two days ago, my HTC announced that there is a new update to android 9.0. It downloads it and tries to install it. After reboot, TWRP starts and I choose to restart the system. Nothing is updated, and after a while I see a message that the update file is damaged.
A few weeks ago I unlocked the bootloader, ripped the phone and installed TWRP and MagiskManager. I suspect that the unlocked bootloader causes these problems. What should I do to install this update?
Click to expand...
Click to collapse
not the unlocked boot loader, it's because you have twrp installed. you need stock recovery(and what ever you do don't relock your bootloader)you can get back to stock by flashing the oreo ruu, then you'll recieve the ota and it will install.you need the ruu for your phone.that's it.
this will wipe your internal, so if you have something on there you want to keep, back it up to your pc, then you can restore, also, you'll need to reinstall twrp and magisk after you install the ota.
Thanks for answer. I'm going to do this ....
Hi,
Is there a way I can just flash the stock recovery and try to OTA? Really don't want to backup 80GB and restore back.
I'm currently on stock Android 10, unlocked bootloader, rooted with Magisk. There's an available update (12.7 MB) but it always gives an error message of "Couldn't update / Installation problem". Uninstalling Magisk didn't fix the issue, so I'm assuming it's due to unlocked bootloader.
If I want to downgrade to 9, is it a simple case of flashing the factory image of Android 9, or does Android 10 need to be fully up to date first? Do I need to re-lock the bootloader?
Any advice much appreciated!
ichigodango said:
I'm currently on stock Android 10, unlocked bootloader, rooted with Magisk. There's an available update (12.7 MB) but it always gives an error message of "Couldn't update / Installation problem". Uninstalling Magisk didn't fix the issue, so I'm assuming it's due to unlocked bootloader.
If I want to downgrade to 9, is it a simple case of flashing the factory image of Android 9, or does Android 10 need to be fully up to date first? Do I need to re-lock the bootloader?
Any advice much appreciated!
Click to expand...
Click to collapse
You can downgrade to 9 but you'll need to do a full wipe. Instead download the full factory image for the latest update and edit the flash-all batch file you'll find in it to remove the -w. Then run the batch file. You'll need to copy the boot.img file in the factory image to your device and then patch it with magisk to root. That patched image will need to be flashed to your device using fastboot from your pc.
I ran into the same issue as you when trying to update with the ota.
ichigodango said:
I'm currently on stock Android 10, unlocked bootloader, rooted with Magisk. There's an available update (12.7 MB) but it always gives an error message of "Couldn't update / Installation problem". Uninstalling Magisk didn't fix the issue, so I'm assuming it's due to unlocked bootloader.
If I want to downgrade to 9, is it a simple case of flashing the factory image of Android 9, or does Android 10 need to be fully up to date first? Do I need to re-lock the bootloader?
Any advice much appreciated!
Click to expand...
Click to collapse
Your problem is not due to an unlocked bootloader. I had no problems with that update following this procedure. https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
You would have to reinstall Magisk to follow that procedure.
You should be able to flash the full factory image of either 9 or 10, but that will wipe your phone. Here is a link to a thread regarding downgrading from 10 to 9. That thread is for an XL, but it is still applicable.
https://forum.xda-developers.com/showpost.php?p=80206785&postcount=31
Complete flashing instructions are here: https://developers.google.com/android/images#instructions
You can flash the factory image without wiping your phone by editing flash-all.bat, and removing -w from the last line. That may not fix your problem, though. You may need a wipe to fix it.
Make sure to download the latest platform tools if you decide to flash. https://developer.android.com/studio/releases/platform-tools
I would not relock the bootloader. It may be impossible to recover from a bricked phone with a locked bootloader, and the relocking process may brick the phone. You must be on a stock image to relock the bootloader.
jd1639 said:
You can downgrade to 9 but you'll need to do a full wipe. Instead download the full factory image for the latest update and edit the flash-all batch file you'll find in it to remove the -w. Then run the batch file. You'll need to copy the boot.img file in the factory image to your device and then patch it with magisk to root. That patched image will need to be flashed to your device using fastboot from your pc.
I ran into the same issue as you when trying to update with the ota.
Click to expand...
Click to collapse
I managed to figure it out, updated ota and am now back on 9 with no problems I used flash-all without removing -w but didn't lose anything important so it's all good!
dcarvil said:
Your problem is not due to an unlocked bootloader. I had no problems with that update following this procedure. https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
You would have to reinstall Magisk to follow that procedure.
You should be able to flash the full factory image of either 9 or 10, but that will wipe your phone. Here is a link to a thread regarding downgrading from 10 to 9. That thread is for an XL, but it is still applicable.
https://forum.xda-developers.com/showpost.php?p=80206785&postcount=31
Complete flashing instructions are here: https://developers.google.com/android/images#instructions
You can flash the factory image without wiping your phone by editing flash-all.bat, and removing -w from the last line. That may not fix your problem, though. You may need a wipe to fix it.
Make sure to download the latest platform tools if you decide to flash. https://developer.android.com/studio/releases/platform-tools
I would not relock the bootloader. It may be impossible to recover from a bricked phone with a locked bootloader, and the relocking process may brick the phone. You must be on a stock image to relock the bootloader.
Click to expand...
Click to collapse
You're totally right that my problem had nothing to do with bootloader. I realised that by rooting with Magisk, the boot.img was modified, so I downloaded the image of the version that I had, extracted boot.img, flashed it to my phone, which got ota working.
I then updated ota to the latest Android 10 just in case, before flashing Android 9 followed by root - this was probabaly more complicated than necessary and I probabaly could have skipped the ota update, but everything is working as intended
dcarvil said:
Your problem is not due to an unlocked bootloader. I had no problems with that update following this procedure. https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
You would have to reinstall Magisk to follow that procedure.
Click to expand...
Click to collapse
What's the difference between this method and simply flashing the phone with the stock boot.img? I just flashed stock boot.img, got ota working on 10, updated, before downgrading to 9. Will I run into any issues because I didn't use Magisk's restore image?
ichigodango said:
What's the difference between this method and simply flashing the phone with the stock boot.img? I just flashed stock boot.img, got ota working on 10, updated, before downgrading to 9. Will I run into any issues because I didn't use Magisk's restore image?
Click to expand...
Click to collapse
Flashing the stock boot image removes root, so you must re-root the phone after updating. This method removes root from the active slot, but preserves it on the alternate slot. After the OTA root is restored from the alternate slot.
The end result is the same for both cases, but following the OTA procedure is simpler and faster.
dcarvil said:
Flashing the stock boot image removes root, so you must re-root the phone after updating. This method removes root from the active slot, but preserves it on the alternate slot. After the OTA root is restored from the alternate slot.
The end result is the same for both cases, but following the OTA procedure is simpler and faster.
Click to expand...
Click to collapse
That makes sense, thanks!
So, when I updated from OOS 9 to 10 I forgot to remove magisk and it's modules and completely forgot about it.
When I finished the update I noticed all the emojis where gone and from other posts here I found that it was because of a problem with the reserve partition that could be solved flashing a magisk module. Well, to my surprise, when I tried flashing magisk again on OOS 10 I always got stuck on a bootloop, I tried everything, removing the old modules that where still installed, using different twrp versions, using bluspark kernel, flashing a patched img through adb... But I always got a bootlop after installing magisk.
Since I couldn't get magisk on and was getting frustrated I decided to wait for the next OTA to see if it might fix it, but now that I tried installing it, I get stuck at 89% installation and don't know what to do. It's probably because of the reserve partition where the emoji should be, but since I can't use magisk idk how to fix it.
Is there another way to fix the reserve partition? Maybe a patch through twrp? Will a clean install of some sort help me or will it also get stuck at installation and brick my device?
Any help is welcome!
EDIT: Since noone replied I tried to fix it myself by trying to flash magisk a couple of times again (which gave me bootlops as expected), so I ended up flashing an OOS 5.1 downgrade build (which factory resets your phone so back up your stuff) and updating all the way to 10.3.1 through OTA updates. This fixed both my emoji and stuck update problem, so If you have similar problems and have not had any luck with other solutions I suggest you to downgrade like I did. If you back everything up on the cloud you should be back up and running in under an hour.
How did you flash the downgrade rom since your system updater is stuck?
Go twrp recovery, look for .Ota, flash the downloaded update zip and reboot.(Must be patient for step 2 to complete)
If can't find .Ota, go to File manager app, click storage below, click 3 dot on top right coner, settings, turn Show hidden file switch on
I have been trying to figure out whether it is possible to update my OP7P that is running a patched 10.3.0 magisk IMG to 10.3.1 without twrp and without erasing the phone? I would like to retain all of my data and upgrade to new version. I have already patched a new image of 10.3.1GM21AA,but have no upgraded yet because I'd like so see if I am able to retain all data while at the same time upgrading
On a side note, if I am unable to install new upgrade without having to erase device what is my best option to make a backup of my device(without twrp)? I know about Google backup, but that doesn't back everything up.
Edit: just to be clear I know how to update to new patched boot img, but not without losing data. I would just like to know whether it's possible to update with only magisk and not lose any data.