I'm on nightly 3/21, which I installed clean yesterday. I want to update to 3/22, but the update will not work automatically in TWRP. (TWRP cannot mount e:, which is a problem I encountered several times while trying to install CM, and ended in me having to reflash to stock several times before it would work again.... Anyways, that's a separate issue.) I selected the option in Dev options to automatically update CM recovery, but this option does not seem to be working. After having selected that option, then downloading the update and selecting update, the tablet still reboots into TWRP and does nothing.
Which brings me to my question. Can I get the CM recovery img from somewhere and flash it myself in order to get the updates to work? I haven't been able to find it, and TWRP has just been a pain in the neck anyways.
Thanks!
Related
I have Samsung Vibrant T959. Currently has clockworkmod 6.0.3.6 .
I'm trying to install the latest unofficial cyanogenmod 11, which will install kitkat 4.4.4, however I run into the error message "set_metadata_recursive: some changes failed" . According to my research all I need to do to solve it is update clockworkmod to a version of at least 6.0.4.5 .
I've searched all over, most sources point towards using rom manager, but this is not working. Rom manager seems to think the latest version is 2.5.1.2. The official clockworkmod site also lists 2.5.1.2 as the latest version for my phone.
So how do I upgrade this clockworkmod so that I can install kitkat? I know others have done it, but I can't find any info how.
Thanks.
I just installed Sada's 4.4.4 today (coming from the official CM 11 [4.4.2]) and what I did was go into CWM and install the rom (which will fail). During the process it will install CWM 6.0.4.9. Reboot. Now you will have 6.0.4.9.
FYI - I had to reformat the internal SD card to get the 4.4.4 install to stick. (factory reset and clearing caches wasn't enough and would throw errors on first boot)
-Mike
Thanks for the advice. Thats the exact thing I was doing. Coming from latest official Cyanogenmod, to the latest unofficial.
So I did exactly what you said, tried to install, it failed, rebooted straight from recovery back into recovery, and I indeed had clockworkmod 6.0.4.9.
So I did the install again, it worked, installed the minimal gapps, but I did not format the SD card. I figured I would try without it first.
Well upon booting I couldn't get past the first screen of the setup wizard, it would just crash. Had a very difficult time getting back into recovery mode, as the typical 3 button combo wouldnt work, but finally figured out a way by sheer luck and experimentation (hold volume down, and power, and plug in a usb cord. Keep the buttons held for about 30 seconds, then release the power button while still holding volume down, after 10 seconds it would go to recovery)
So I did the format of the internal SD card as well, but no luck, the wizard still crashes. Ended up just restoring my old nandroid. I wonder if there was anything else you did different than me. Perhaps different Gapps?
Hi so after updating from the stock zv6 to lollipop update my phone won't install a custom ROM. Every time I try to turn it on it goes straight to TWRP and went I install a ROM or try to load a backup as soon as I hit reboot it goes back to the TWRP page. Amy ideas?
You must flash back, using Flashtool, to zv4, then reroot, then flash newest TWRP. OTA software not included, because they flash every partition of the phone, including the boot loader. Stock roms like zv6 and zv8(lollipop)or AOSP, must be flashed from xda from here on out, because they've been modified to work correctly on zv4 boot loader. TWRP and root access only work correctly with zv4 boot loader.
sent from my LG G3
It sounds like there is no OS installed or it is stuck a reboot-loop. Try pulling the battery out for 10 seconds and if it still goes into twrp you know that it isn't a reboot-loop. When you go to restore a rom and it has the bar that shows the amount of storage does it say "0 MB"? If it does it means that twrp can't mount the storage on the phone thus causing it to not install/reboot. Have you tried side loading a rom via adb? Are you trying to install a rom off of a sdcard? I have seen many issues in the past sdcard related.
If you can please answer the following:
1) What is the message you are getting from twrp (if there is any)?
2) Have you installed a custom kernel and if so witch one?
3) What twrp are you running (the bumped one from xda or from the official twrp site) and what version is it?
4) Have you tried adb and pulling the battery?
If you answer these questions they should be able to tell us all that we need to know in order to help you out.
Hello,
These past two days have not been a good day for my phone lol. Some background:
BEFORE:
I had a 4.4.4 Custom ROM [Forgot the name...]
TWRP: 2.5.0.2
AFTER:
I clean flashed http://forum.xda-developers.com/gal...m-cyanogenmod-12-0-nightlies-verizon-t2998057
I cleared cache + Dalvik after the flash and it asked me if I wanted to fix root (From what I read before, you're never supposed to press Fix, rather you're supposed to prses Do not Fix and you'll still keep your root.
However, I accidentally pressed Fix Root and Now I lost my root. The ROM I flashed is glitchy because from what I read is because I have TWRP 2.5.0.2.
Now I'm stuck on this ROM, I have no idea how to upgrade to the latest TWRP and don't know how to get my root back . [Can't get TWRP Manager because I don't have Google apps (I tried flashing the GAPPS by Paranoid but it keeps crashing because I think it's the outdated TWRP)]. I tried to download TWRP manager on my phone via another site, but it doesn't install on my phone for some weird reason.
Thank you,
Jerry
Download, install and run the towelroot.apk file. This will root your phone, takes about 2 minutes
I know this has been mentioned elsewhere for other Xperia Models, typically newer than the Z U, but I am running in to an issue where my two z ultras are trying to use the same mac address.
I wondered if there was a device specific work around for the z ultra and / if this is being addressed.
Running the latest nightly CM12 builds.
Cheers in advance.
http://d-h.st/agR
Download this zip and flash, it is a fix for when the mac address changes after flashing a custom rom.
Regards
Hi,
Thanks for the post, but unfortunately I am getting a package verification error and a footer error when I attempt to flash the package in recovery.
You are using cyanogenmod recovery, right? If so, you have to use TWRP or CWM to flash it, cm recovery have signature check and you can't turn it off, all custom recoveries have it disabled by default.
Regards
Thanks for the heads up teddy. I was using CM recovery. Installed TWRP and flashed the zip/update. However, CM12 goes tits up with TWRP every time I update CM12 and only seems to play nice with CM recovery. Gapps seems to be the issue with none stop force stops. Seems in order for this to work I have to flash TWRP, flash the mac address zip and then flash CM recovery back every time I want to update via nightly.
You can flash TWRP to the FOTAKernel partition if you don't want to flash it everytime you update rom and if you flash it, it should work like CM recovery and it will be booting instead of CM recovery. Just download an app called Rashr and install TWRP from the app I assume the fix is working for you, isn't it?
Regards
I did use rashr to install TWRP and that's when the issues arose.
Unfortunately the nightly update came through after installing TWRP so I did the update for 30th and the phone was in an unusable state via gapps force closes as mentioned. So I flashed back to CMr via the update and haven't installed the update yet.
Until I have a workable solution to the recovery issue I won't be proceeding. It will be too much hassle each time the updates arrive.
I don't think that gapps are force closing because of the recovery installed, that would be weird. Have you tried flashing another gapps? Because I have also used CM12 with TWRP and gapps and I haven't got that sort of problems, even now I am using CyanideL (CM12-based) with TWRP and on my configuration it is OK. I will try using CM12 nightlies with TWRP tomorrow and I will write you back if I found a solution
Regards
Yes, I was using the signed gapps dated late last year, but when I came across the issue I reflashed the whole of CM12 with the more recent ones dated April I think. I still had the same problem, which is when I read up and saw it was attributed to using a non-CM recovery and reset everything back to CM12 nightly + CMr, I did however keep the most recent gapps. Let me know how you get on.
When I updated Cyanogenmod to CM13 my recovery stopped working (I turned on "update recovery with system"). I didn't can apply ANY updates from SD card and from PHONE STORAGE too.
To fix it I tried to update CM to 13 from 10-02-2016 to 13-02-2016. But... It didnt ANYTHING happened! It was only black screen. But now I can't turn on my phone! Recovery mode is not turning on too! I have only not working phone with not working recovery when it will turn on too!
I need my phone tomorrow, please, HELP ME! What can I do?!
Recovery: CM13 recovery.
It is not bootloop, I have:
BLACK SCREEN
After Samsung logo.
It is very important, does somebody know what to do?
I have new news:
After turning on I have samsung logo and for about one second Updating System message! Without loading bar . After it of course black screen!
I didn't do any backups of my phone, but I can wipe all data, but I NEED WORKING PHONE!
@tom790
Try flashing this kernel I attached with odin. Next try rebooting to recovery. If you get a working TWRP recovery, then flash the rom you want to use as normal. Please read this guide if you want to use CM13 and avoid common issues.
Same problem here after trying to update to the newest nightly (also with "update recovery with system" on in developer settings) I assume that this function isn't working correctly. The only alternative is as mentioned above - flash kernel+recovery with Odin and make changes afterwards.
I have same problem. I tried to install this kernel above with ODIN but no luck, after sucessful flash logo and black screen. Any other advice or tips? Is there any chance to recover some data from internal card?
And exactly the same issue here. Will try the workaround from the first answer by noppy22.
OK, succeeded. I used ODIN with the kernel tar file from noppy22, put the S2 into download mode (that was still possible, recovery mode couldn't be accessed), flashed the kernel. Phone rebooted automatically into recovery and started (continued?!) with the installation of CM 13.0. And here I realize the issue. The OTA was the nightly of CM 13.0 which I inadvertently chose to be flashed over the running CM 12.1. Bad idea!
Caveats: I see the yellow triangle now which didn't show up before. No problem for me - it's more than 4.5 years old. And there is still the error that "Google play service was terminated" which showed before I triggered the OTA update of CM 12.1.