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.
Related
As a desktop user, I always do a clean install when upgrading to a new version of an OS (ex. Windows 7 - Windows 8) since the update process can cause a few kinks in performance and compatibility and a clean install will keep the system operating optimally. I do this by formatting my drive and reinstalling a fresh new version of the OS. With the upcoming Android L update, I was wondering if there was a way for owners of Nexus, GPE, or Motorola devices to do something equivalent to a clean install since they will most likely be getting the update first. Does an Android OTA update run as a Delta update or does it essentially reinstall the entire OS? Would simply running the OTA update and doing a factory reset be equivalent to a clean install?
A true clean install would involve flashing the stock image through fastboot, which would erase all partitions, including your SD card also I believe. Android OTA's work as delta updates, replacing only files that need to be erased. Installing the OTA and then doing a factory reset is as clean of an install as you can get without a custom recovery and completely wiping all your partitions through fastboot (The cleanest install you can get).
Sent from my Nexus 4 using XDA Free mobile app
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.
Hello,
Can we update CM Firmware without reinstalling OS?
I have recently install Nitrogen OS with the given firmware. But I have noticed there is a new firmware released with some bug fixes
Can I install the latest firmware without reinstalling the OS??
Jseven123 said:
Hello,
Can we update CM Firmware without reinstalling OS?
I have recently install Nitrogen OS with the given firmware. But I have noticed there is a new firmware released with some bug fixes
Can I install the latest firmware without reinstalling the OS??
Click to expand...
Click to collapse
If you want to switch to a completely different ROM, you will have to do the wipes in recovery then flash the new ROM. If you want to flash an update of the same ROM you have then you don't need the wipes, you can just flash the update without wiping, this is called "dirty flashing". Dirty flash usually only works when flashing an update of the same ROM that you have.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hello ,
I am talking about the cm14.1 latest firmware and not about the custom room updates. Is it possible to install without any issues
Thanks in advance
Jseven123 said:
Hello ,
I am talking about the cm14.1 latest firmware and not about the custom room updates. Is it possible to install without any issues
Thanks in advance
Click to expand...
Click to collapse
What do you mean the latest CM14.1 update?
NitrogenOS and CM 14.1 ARE BOTH custom ROMs, they are NOT firmwares. Some devices were manufactured and sold with CyanogenMod as the stock firmware but CM is still predominately a custom android operating system.
And, as I said, if the update is an update to the exact same ROM as what is already installed, then all you have to do is flash it without doing any kind of wipes(this can even be done when updating stock via OTA, it's actually recommended to not do the wipes when updating stock via OTA). For example, if you have CM13 and want to update to CM14, or if you have CM14 and want to update to CM14.1 or if you have CM14.1 but want to flash a newer CM14.1 update, understand yet?
BUT!!!!
If you have some other ROM(something other than a version CM) currently installed but want to update to CM instead of what you have then you would have to factory reset, wipe cache and dalvik cache before flashing.
Let's make this simple since you can't seem to make sense of what I'm telling you. Tell me what you currently have installed and what you want to update to.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hello,
I am currently using Nitrogen OS for Redmi note 3. I have flashed the firmware and installed the OS according to the procedures. I run nougat(7.1.2) on my Mob
Check this link : https://forum.xda-developers.com/redmi-note-3/how-to/cm14-14-1-aosp-n-firmware-kenzo-kate-t3507789
Jseven123 said:
Hello,
I am currently using Nitrogen OS for Redmi note 3. I have flashed the firmware and installed the OS according to the procedures. I run nougat(7.1.2) on my Mob
Check this link : https://forum.xda-developers.com/redmi-note-3/how-to/cm14-14-1-aosp-n-firmware-kenzo-kate-t3507789
Click to expand...
Click to collapse
You have nitrogen OS installed on your android and if you want to install update of nitrogen OS then no need of wiping.
If you want to change to different rom ( nitrogenOS to CM) then you need to first wiping/factory resetting or clearing dalvik and cache.
So, you are changing your rom then wipe/factory reset first and then flash CM. That what @Droidriven trying to say you.
Again you are confused. ROMs like Nitrogen runs on CM firmware ( or you can call it architecture). It's not the OS again, It regarding firmware. please someone help me on this I dont want my phone to get bootlooped or any other sort of issue. FYI : I don't want CM ROM/OS. I want Nitrogen itself but want to upgrade to the latest firmware. Please check the link i had provide before replying
Jseven123 said:
Again you are confused. ROMs like Nitrogen runs on CM firmware ( or you can call it architecture). It's not the OS again, It regarding firmware. please someone help me on this I dont want my phone to get bootlooped or any other sort of issue. FYI : I don't want CM ROM/OS. I want Nitrogen itself but want to upgrade to the latest firmware. Please check the link i had provide before replying
Click to expand...
Click to collapse
This is making sense now. You see, you are the one confused. You aren't asking the right question because you don't understand the difference.
You aren't looking for the "CM firmware", this does not even exist. This implies that the firmware was created by CM. It wasn't made by CM, it does not contain CM in it so it can't be called "CM FIRMWARE", it's a STOCK FIRMWARE that is COMPATIBLE with USING CM and other custom ROMs.
What you are looking for is the "stock firmware" that needs to be on your device BEFORE using CM13/14/14.1/AOSP Nougat ROMs.
The thread that you linked basically explains that if you want to use any kind of custom 7.0/7.1/7.1.1 Nougat ROMS then you need to flash this updated STOCK FIRMWARE in order for the device to be able to use those custom ROMs. It is not "CM FIRMWARE"
You're looking for the STOCK FIRMWARE that is compatible with CM and other nougat ROMs.
The thread that you linked explains what you need to know and how to do it, it says that you flash the updated firmware via TWRP and factory reset, wipe cache and dalvik when you flash it.
If you are looking for a newer update than the one in that thread then you'll have to find it in a TWRP flashable .zip. If there is not a TWRP flashable zip to apply the new update then the only way to flash the new update is to flash it via PC then root the device again, install TWRP again and then flash your NitrogenOS ROM again.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
thank for the prompt response! so can i flash the latest firmware with the OS installed?
Jseven123 said:
thank for the prompt response! so can i flash the latest firmware with the OS installed?
Click to expand...
Click to collapse
I just explained what you needed to do, did you read it? It is simple, are you even reading the thread that you linked? What you are asking is irrelevant, just do what it says to do in the steps below.
1) Boot to TWRP
2) Flash the updated firmware via TWRP
3) Factory reset, wipe cache and dalvik
4) Flash NitrogenOS
5)reboot, enjoy.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hello community!
Hope you are doing awesome, I am trying to install specifically the update from the 18 th of May (latest while doing this post) so when I downloaded it I go to TWRP and this is what I done
1)Place my pin and decrypt the device
2) Perform a format Data > Yes
3) Wipe cache, dalvik, internal
4) Restart to Recovery
5) Install the update all seems to be fine and reboot to system
The Phone boots to Poco screen and then vibrates and then gets me back to TWRP. I manage one time to get it worked and got in the config page from the customer rom a UI unresponsive message and is unable to connect to my Wifi so I have to use the Data 4G to make it work and I rolledback to April version of Arrow OS that seems to be the one working now.
The Miui stock that I am using to install the customer Rom is surya_global_images_V12.0.8.0.QJGMIXM_20210222.0000.00_10.0_global
Could you please provide some hints and tips what I am doing wrong so I can get this updates up to date? Because I love the Arrow OS Rom and I want to keep the firmware updated correclty on my side.
Thank you!
I am very interested, too. Got the same problem. After latest OTA-Update I'm stuck in a recovery bootloop as well.
Sadly even the attempt to flash back an older version or a MIUI Stock rom is failing for me now. Always recovery bootloop, even after a successfull flash without errors (and format data of course) .
Is the stock rom or an older arrow os version working for you, after the 18th May update?
@koelbche I was able to make a stock based on the stock fw shown on my post. then I installed old version of arrow OS April update and it was restarting bootloop.
I had to delete data, factory reset and select de wipe options so super clean flash and manage to boot it up.
I am waiting for any updates from others that manage to install the updates because I was not able to do it.
Flash ArrowOS custom recovery for ota update to work. After update you can flash recovery back to TWRP for root and backup, your choice.
I was able to make it worked in another post.
All I have to do was to update the version of the stock with Oss vendor (I think) and then all worked like a charm!.
Thanks for the replies though