I have TWRP on my phone already, and everything is backed up. I am currently using the older Sprint Hybrid-X 4.4.4 version of the Rom found in this post.
I recently got the Samsung Gear VR for the Note 4 from Amazon and I have enjoyed it. Unfortunately, 5.0.1+ is needed for Netflix on the Oculus VR app so I assume it will limit other things staying on 4.4.4.
Long story short, I would like to update to the 5.1.1 version of this Rom in the link above. I'm guessing since I have everything backed up all I need to do is put the Rom on my Micro SD, Wipe everything x3, and flash the new Rom, correct? I know this is a simple question, but I just wanted to double check that I don't have to do anything else before jumping in. Thanks in advance to those who may reply.
Confirm your device is rooted. Clear dalvik and other caches and then flash the zip..
Nikhilrj said:
Confirm your device is rooted. Clear dalvik and other caches and then flash the zip..
Click to expand...
Click to collapse
Thank you for your post. My device is rooted, and I will make sure to clear; however, it seems I may need to update TWRP to the latest version for Lollipop support. I am currently on v2.8.1.1 with the latest being 2.8.7.0 of TWRP.
Does this seem necessary, and if so would I be able to flash the latest update within the older version of TWRP or should I just do it via Odin?
Note: I guess TWRP says TWRP Install (Requires TWRP 2.8.4 or higher already installed) but I may be able to update with TWRP app.
Update: For those who do want to flash a lollipop ROM you need to upgrade your TWRP if on an older revision below 2.8.4 I believe. I used the TWRP app on google play store. Easy as pie, but you will need your phone to be rooted + have an unlocked bootloader.
- Download TWRP Manager from Google Play Store
- Select Install TWRP from Menu
- Select Your exact phone (make sure you've got this right or you could soft brick your device make/model) as well as latest TWRP version (may need to install at least TWRP v2.7 first via Odin)
- Hit install and on reboot Wipe Dalvik Cache + Cache then reboot system and wait for the update to finish.
Now that I've got that updated I believe I can install the new Rom, I will update my post when I do so if all goes well.
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 a Moto g3 (osprey) with Android 6.0.1 and CyanogenMod version 13.0-20160927-NIGHTLY-osprey.
Obviously previous owner did not keep up to date installing the received updates.
When I attempt to install the oldest update it does not complete successfully. I get the Android character with red in stomach
.Upon rebooting it does so to current version.
What would be the best way with fewest steps to bring this phone's cyanogenMod up to date?
Thanks in advance
Jerry
That version is almost a year old... and it sounds like you don't have TWRP installed.
Install TWRP via fastboot, download latest LOS ROM and gapps, start TWRP, wipe system and caches, flash ROM and gapps.
Be aware that such a large jump might require a clean install, meaning you need to wipe all your data and installed applications.
I rooted my ZenFone 4 max and installed Xposed. Ended up installing an Xposed module that caused the system UI to crash on boot. So I did a factory reset from TWRP, which fixed the UI. But now most of my apps crash and force-close. Anyone have an idea how to fix this? Would flashing stock firmware work? And if so, where can I get the stock recovery? (I already downloaded the stock firmware from Asus website)
Mc10538 said:
I rooted my ZenFone 4 max and installed Xposed. Ended up installing an Xposed module that caused the system UI to crash on boot. So I did a factory reset from TWRP, which fixed the UI. But now most of my apps crash and force-close. Anyone have an idea how to fix this? Would flashing stock firmware work? And if so, where can I get the stock recovery? (I already downloaded the stock firmware from Asus website)
Click to expand...
Click to collapse
Whats your Android version. Try flashing gapps. Hope it will work. Use the stock gapps package.
7.1.1
Android 7.1.1. I tried gapps, it didn't help, and most of the gapps crash as well
solved(ish)
Mc10538 said:
I rooted my ZenFone 4 max and installed Xposed. Ended up installing an Xposed module that caused the system UI to crash on boot. So I did a factory reset from TWRP, which fixed the UI. But now most of my apps crash and force-close. Anyone have an idea how to fix this? Would flashing stock firmware work? And if so, where can I get the stock recovery? (I already downloaded the stock firmware from Asus website)
Click to expand...
Click to collapse
I got a notification for an ota system update, figured I didn't have much to loose, so I went ahead and told it to install. It started installing, then booted to recovery (twrp) and then crashed, and wouldn't load the operating system, would only boot to twrp. I restored a (bad [backed up after problems started]) twrp backup I had, and now everything seems to be working just fine. So the ota update must have fixed whatever was causing app crashes. At this point with everything I have done, the code probably looks like Frankenstein's monster, but everything works, so I'm happy and am going to leave everything the way it is. Hope this might help if someone is having similar problems!
Mc10538 said:
Android 7.1.1. I tried gapps, it didn't help, and most of the gapps crash as well
Click to expand...
Click to collapse
Ohh.. flash to stock os again
Go to twrp> wipe > wipe everything (system,data,cache ,dal cache)
Back to install select the stock os
Install it..
( Is the installation fail. Go to fastboot and flash the stock recovery and flash the stock os through it)
Then reboot.
Install magisk manager
After opening it it will pop up "install "
Hit install and locate the stock os "boot.img" file.
It will download and flash some files.and will create a patched-boot.img file in your internal storage
After that copy it to your pc and flash it
( Fastboot flash boot "file.img" )
Reboot!!!
Install Xposed from magisk module. Its the stable one.
Twrp
https://goo.gl/v17ZgR
Stock
https://goo.gl/S75Dpr
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