i mean... the source are not the same?
I thought so, too. If I remember correctly there is also the possibility to boot the bonito kernel on sargo ...
Just noticed the new TWRP for Bonito. Perhaps we'll get one down the road too.
If you look at the download page for TWRP 3.5.0 for Bonito, it says it's for Android 9. Sargo got the 3.5.0 update on January 25, but again, based on Android 9. Don't try to download it on Android 10 or 11.
If we can't use TWRP with A11, is there a different manager for making nandroid backups / installing zips etc that does?
Unfortunately not ... at least I am not aware of any. You need to find different backup / restore methods for your device.
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.
Good afternoon XDA.
I'm trying to get Magisk installed on my phone, but I'm really struggling.
Any hints/tips? I've followed instructions to every forum post and every Youtube video I've tried.
AFAIK, I have managed to install TWRP without issue, although after I've rebooted my phone into recovery, it encrypts the data folder, meaning if I patch any zips in TWRP, I have to first format the data to EXT2 and back to EXT4 for me to be able to mount the folder, which I think is where my problems lie.
After this, TWRP seems to look like it's installed the Magisk.zip without any issues, but when I install the magisk apk once I've booted back into Android, it says it is not installed, and is asking me to either download the zip again, or find a boot image to patch.
The ROM I have installed is also custom as far as I'm aware, as the kernel says "[email protected] #2'
Android version: 8.0.0 (I don't mind using an older ROM, like 7 if it means I can get Magisk working.
Build: 41.3.A.2.157
Thanks
Try this, download flash tool, use Xperiafirm to ? get the latest firmware for your region which is currently 171, check all the wipes, flash, then look down a few post to YasaHamed thread, follow his instructions and make use you use the correct kernel..
madladfromhalifax said:
I'm trying to get Magisk installed on my phone, ...
Click to expand...
Click to collapse
I had no problems with a patched stock kernel as described in my [Guide].
Updates of kernels and Magisk, whatever ...
I used latest TWRP, several versions
The encryption only forces you to wipe data if you set up a patched kernel the first time.
I will see how this works with a XZ1 (no TA-backup) since my XZ got stolen last week.
use AdrianDC's twrp, not the twrp official one
madladfromhalifax said:
Good afternoon XDA.
I'm trying to get Magisk installed on my phone, but I'm really struggling.
Any hints/tips? I've followed instructions to every forum post and every Youtube video I've tried.
AFAIK, I have managed to install TWRP without issue, although after I've rebooted my phone into recovery, it encrypts the data folder, meaning if I patch any zips in TWRP, I have to first format the data to EXT2 and back to EXT4 for me to be able to mount the folder, which I think is where my problems lie.
After this, TWRP seems to look like it's installed the Magisk.zip without any issues, but when I install the magisk apk once I've booted back into Android, it says it is not installed, and is asking me to either download the zip again, or find a boot image to patch.
The ROM I have installed is also custom as far as I'm aware, as the kernel says "[email protected] #2'
Android version: 8.0.0 (I don't mind using an older ROM, like 7 if it means I can get Magisk working.
Build: 41.3.A.2.157
Thanks
Click to expand...
Click to collapse
simplyfied!!!! https://forum.xda-developers.com/xperia-xz/how-to/rooted-kernels-f8332-41-3-2-588-0-t3748987
TLDR
anyone get twrp 3.4 working with android 10? twrp released version 3.4 which supposedly supports android 10 and pixel 3a is a supported device. i flashed twrp and now twrp boots but nothing else does. its not a problem i can give it a try again just wondering how other people flashed it and got it to work.
long version:
TWRP released version 3.4 which supports android 10! yay im all happy and crap because pixel 3a is supported so i flash a kernel that supports LZMA compression. (i installed elemental x for android 10) and now i meet all the requirements. go to boot the .img file like they say using fastboot. i typed into ubuntu terminal "fastboot boot twrp3.4sargo.img" i get "error verifying the received boot.img: invalid parameter" this is the same exact error when booting older twrp recoveries because they arent compatible with android 10. not a problem though i thought! i have ex kernel manager so i can flash the twrp zip file through there! (thats what twrp website tells you to do if twrp had booted anyways so i thought well maybe i can skip that step since it isnt booting anyway and just flash the damn file) so i open ex kernel manager and flash the zip file! twrp boots im all happy and then i go to reboot and S#!+. nothing boots except twrp. anyone have any ideas on getting this to work since supposedly pixel3a android 10 is supported now?
Whenever Ive seen that error it means its not recognizing the partition youre trying to flash. Try adding the "a" or "b" after boot. So fastboot boot boot_a or boot_b depending on which is the active partition.
All this said, what are you trying to flash? A patched boot image or TWRP? If TWRP then you dont want to flash it to the boot partition, that goes to recovery.
Have you ever had to flash a full factory image of Android 10 (not just an OTA update)? TWRP will only work on Android 10 if the device was updated from Android 9 and still retains it's Android 9 file structure. I'm wondering if the file structure gets changed to the regular Android 10 file structure when you flash a full factory image vs an OTA update from Android 9 to Android 10 - I'm betting that it does. This would mean that TWRP would not work.
I honestly didn't even know this was released and I will try to install it on my 3A XL later today. I have flashed an Android 10 factory image since I moved from 9 to 10 via an OTA update, so I guess I will be able to test my hypothesis.
ctfrommn said:
Whenever Ive seen that error it means its not recognizing the partition youre trying to flash. Try adding the "a" or "b" after boot. So fastboot boot boot_a or boot_b depending on which is the active partition.
All this said, what are you trying to flash? A patched boot image or TWRP? If TWRP then you dont want to flash it to the boot partition, that goes to recovery.
Click to expand...
Click to collapse
Sorry been busy didn't have time to check this. I did try to flash to recovery. Flashing to boot was a typo. Same error result though. I'll try the a b partition thing later.
sic0048 said:
Have you ever had to flash a full factory image of Android 10 (not just an OTA update)? TWRP will only work on Android 10 if the device was updated from Android 9 and still retains it's Android 9 file structure. I'm wondering if the file structure gets changed to the regular Android 10 file structure when you flash a full factory image vs an OTA update from Android 9 to Android 10 - I'm betting that it does. This would mean that TWRP would not work.
I honestly didn't even know this was released and I will try to install it on my 3A XL later today. I have flashed an Android 10 factory image since I moved from 9 to 10 via an OTA update, so I guess I will be able to test my hypothesis.
Click to expand...
Click to collapse
Did you ever get it to work?
AudibleDruid said:
Did you ever get it to work?
Click to expand...
Click to collapse
I haven't tried yet. Honestly I'm not very motivated either. I'm 99.9% sure it won't work (because I have flashed a full factory image of Android 10 since taking the OTA update) and I don't feel like getting myself into a situation where I might have to reset my phone. I realize it shouldn't go that far, but the "reward" simply isn't worth the risk for me right now.
The Pixel-3a partition scheme was updated when upgraded to Android 10, i.e. the Pixel-3a is an exception to the rule that a device launched with Android 9 is compatible with TWRP 3.4. The Pixel-3a having Android 10 has the same structure like a device directly launched with Android 10 and so TWRP 3.4 will not work.
I installed LineageOS 18.1 (Android 11) on my OP7P and want to boot (or flash) TWRP.
There is a lot of different information about the state of TWRP on Android 11.
I hope someone could clearify the following questions:
1. Does TWRP [3.5.2] support Android 11?
the release notes of 3.5.1 state that they "prepared a mini release before Android-11 support."
The release notes of 3.5.2 don't mention android 11 at all.
There are various people in the LOS18.1 thread that can boot twrp, so I assume there is some kind of (partial) support.
2. What if 'fastboot boot twrp.img' doesn't work?
For me I can't boot (or flash) TWRP (on LOS18.1).
So as the twrp/lineage os guide says I do:
fastboot boot twrp.img
Click to expand...
Click to collapse
It finished succesfull, but my phone stays in fastboot and doesn't reboot.
The TWRP guide says the following:
If fastboot boot command doesn't work you need to root your device and flash the TWRP installer (remember that flashing the TWRP installer you will lose the root).
Click to expand...
Click to collapse
I find this a very vague description; what do they mean with "doesn't work"?
(when I flash twrp it results in an unbootable phone, might be related to a/b partitions, but I have not enough knowledge of that)
3. Does TWRP work on encrypted phones?
I found various posts that suggest that TWRP doesn't work on encrypted phones.
I can't find any reliable source that supports that statement.
Twrp says this, but that doesn't clearify things at all.
I hope someone could give me some answers, or guide me to some reliable source so I can find it myself.
I find the documentation of LineageOS and TWRP lacking in that perspective.
For question 1, there's no official TWRP for 11.... YET.
Question 2 - I'm thinking cause TWRP doesn't work for 11, that's your issue.
Besides that, if your trying Android 10(because you don't mention what version your using in question 2), I would suggest re downloading, as that process works fine for this phone I'm typing this reply to you on.
Question 3 - I'm sorry, I've got ideas, but it's above my pay grade... So no hard knowledge I'm comfortable calling advice, to give a fellow OP7P owner.
lenigma1too said:
For question 1, there's no official TWRP for 11.... YET.
Question 2 - I'm thinking cause TWRP doesn't work for 11, that's your issue.
Besides that, if your trying Android 10(because you don't mention what version your using in question 2), I would suggest re downloading, as that process works fine for this phone I'm typing this reply to you on.
Question 3 - I'm sorry, I've got ideas, but it's above my pay grade... So no hard knowledge I'm comfortable calling advice, to give a fellow OP7P owner.
Click to expand...
Click to collapse
I also think there is no official TWRP for android 11, but twrp doesn't make this very clear in their docs.
Multiple people are claiming they are able to (at least) boot twrp on Android 11.
LineageOS 18.1 is Android 11 (but I will clearify the post).
Thank you for your reply
there is now a working TWRP version for Android 11.
Nebrassy version: https://forum.xda-developers.com/t/recovery-11-unofficial-teamwin-recovery-project.4289455/
worked for me with 'fastboot boot TWRP-3.5.1-guacamole-Nebrassy-3.img'
Since oneplus 6 nas no security updates i decide to install custom ROM LineageOS 19.1 the newest build from official website.
Before installing this ROM i do all steps gently from Funky Wizard guide.
I have ADB drivers, unlock bootloader, installed magisk (rootet phone) backup my OOS and EFS, and installed twrp.
All basic stuff. Now i was ready to go to installed lineageOS.
I install lineage and i do all steps by their official website but with twrp. ( only what i dont flash copy partition zip file i wasnt sure if that will be work with twrp ).
After restart to recovery i must install gapps. Unfortunely the recovery was replaced i was assumed istead of twrp.
I installed gapps with their recovery and all work fine until i want to replace to twrp.
Now when i boot temporarly from img to install it perm. I have weird folder names wihtout any possibility to add ZIP file.
With some research i guess that folders are somehow encrypted.
Could you help me to install twrp with lineageOS when i have still access to this files? I need it for ex. recovery to stock if something in future goes wrong.
And i am currently on android 12 for sure.
Thank you from feedback!
first of all, you'd be better of if you posted this in the right area ==> https://forum.xda-developers.com/t/rom-official-enchilada-12-lineageos-19.4437321/ ==> more chance to get help related to LOS 19 questions (it's pure chance I saw your post here)
second: make sure to follow the instructions given at the LOS instructions pages ==> https://wiki.lineageos.org/devices/enchilada/
Mostly it is important that you have latest OOS 11 firmware installed in both slots before you start with LOS.
For the first steps never mind which recovery you have, just follow the instructions using LOS recovery. Reason is that TWRP is having problems wiping data / performing factory reset, at least it never worked for me. Then later on you can switch to TWRP
Back in May this year I wrote an instruction set here: https://forum.xda-developers.com/t/rom-official-enchilada-12-lineageos-19.4437321/post-86879331
Interesting for you right now is everything below 1.x
2.x is a separate instructiopn set for OTA updates coming later on
Good luck!
Thank you for response. You have right its better to install it directly from dedicated recovery (lineage) and than replace with twrp. Also i fill missing steps (install recovery again and flash parition integration file) and also wipe all data as instruction says. Now after reinstall lineageos and then install twrp i have all normal structure files as before. Thanks again