Replacing Cyanogen Recovery with TWRP using TWRP's App - Galaxy S 5 Q&A, Help & Troubleshooting

Hello!
I have an S5 that was running CM 14.1. I had moved from 13.0 to 14.1 with out whipping everything, so things were not perfect.
I wanted to move to Lineage 14.1 with a clean install.
I booted in recovery (Cyanogenmod Recovery) and whipped as much as possible.
When trying to Apply Update with the Lineage OS 14.1 nightly .zip, I got the "failed to verify signature" error. I have redownloaded the rom a second time to make sure I did not have a corrupted .zip.
I ended up reinstalling CM 13 because that is what I had not to far and needed a working phone.
So my question is about the recovery and the error I got with the Lineage rom.
Do I get the error because the type of recovery I have or does the Lineage OS .zip is known for generating this error (since it's still all very new)?
If the recovery is the problem, can I use the Official TWRP App to switch from Cyanogenmod recovery to TWRP ?
I have already tried to replace the recovery in download mode but Heimdall 1.4 generated an error as well regarding the "PIT file" so the process got interrupted.
Thank you in advance for any input!

bump!
Surely someone can answer this simple question!
thanks!

Related

[Q] CM 11 Issues a plenty

Verizon VS980, TWRP 2.6.3.3
Finally, upgraded to the above TWRP, and was able to flash a CM 11 nightly. and Gapps for 4.3.0, 20130813 and to have that finally flash successfully is great! BUT it's not, when I boot into it I get an android system error and the keyboard AOSP error every time, I can't make it past the screen where I enter in my account.
I have wiped and tried again, and again, I have installed the ROM and gapps and then wiped dalvik and cache and same result...
It seems so close.
I have installed ROM Manager as well and it says that CWM is installed yet I cannot seem to boot into it, I have flashed it from the ROM Manager many times and no love. I was able to flash a zip of twrp, is there a zip of CWM that is flashable from twrp, I have heard that cwm works better with CM 11
Please help, I have no idea why going to CM 11 should be such a pain in the..
Thanks!!!
SO i figured it out
I was following/using rootz wiki for my reference of which gapps to use and it is not updated right now
got the right gapps here, and all is good now
http://d-h.st/mDt

[GUIDE] How to get CM 14.1 working.

Hi,
So I have created this thread just because I can see many people creating new threads as after flashing CM 14.1, their phone doesn't boot up. So for all those who are going to flash CM 14.1 or have already flashed it and can't get it working, this thread is for you.
What you will need:
1. Rooted OnePlus X (Obviously)
2. Custom Recovery (TWRP recommended)
3. Latest CM 14.1 build
4. Arsenic Kernel or BlackReactor Kernel
So this is how you get CM 14.1 working on your OPX (make sure your battery is above 80% just to be sure that nothing will go wrong considering battery's point of view)
Make sure you have backed up everything before performing the following steps as the process will wipe your data completely. (I would recommend to take a Titanium backup of all user apps and then taking a nandroid backup of system and data)
1. Download the required files and place them in your SD Card or internal storage
2. Reboot your device into recovery
3. Go to wipe, and swipe to factory reset (Note! This will completely wipe all the data from your device including app data and SMS! This won't wipe the contacts but just to be safe, have a backup of all your contacts)
4. Go to Wipe again, and go to Advanced wipe, select the following partitions - System, Cache, Dalvik cache. Swipe to wipe (Note! Make sure you have a backup of the System as this will wipe the Operating System from your phone!) Although this step isn't necessary, I like to do it.
5. Go to install, and direct to the location where you have saved the CM 14.1 zip file and the kernel. Select the files, and swipe to flash.
6. If you want anything else in your system, direct to that location, select the zip file, and swipe to flash. (Note! You need not flash the SuperSU zip file as CM offers Root access in developer options)
7. Reboot your system and wait for it to boot.
Viola! Your device is now running official CM 14.1 nightly.
Hope this helps! ?
Downloads:
1. Latest CyanogenMod nightly - found here https://download.cyanogenmod.org/?device=onyx
You can have any version of the nightly as long as it is CM 14.1
2. Arsenic Kernel R32 (or R31) - http://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
Open the above thread and follow the guide
OR
Black Reactor kernel v1.0 - http://forum.xda-developers.com/oneplus-x/development/kernel-blackreactor-kernel-oneplus-x-t3460989
-Reserved-
Good Evening, @aamodjoshi23 THX a Lot. You are my Hero. Finally it works.
greetings
If you're facing some Error 7 while trying to flash cm 14.1, you can try updating the bootloader following this
http://forum.xda-developers.com/showpost.php?p=69267239&postcount=2560
I used the Oxygen OS 3.13 full ROM as recommended, edited updater-script (following those instructions)
Immediately after flashing the OOS 3.13 rom, you don't have to reboot.
I immediately flashed twrp 3.0.3 original from https://dl.twrp.me/onyx/
I then rebooted into twrp 3.0.3 (using the reboot button in twrp, then bootloader)
Then I installed (in this order):
cm 14.1 (https://download.cyanogenmod.org/?device=onyx)
arsenic kernel (as recommended above)
opengapps
Not sure if this step is necessary, but I wanted to let twrp patch the rom to not overwrite twrp so I rebooted into twrp again (using reboot --> bootloader in twrp)
Then I used reboot --> system
First boot took a while, but now I have nougat!!
kenel zip every time
Do i need to flash the kenel zip every time I update the the cm 14.1 zip file?
allons-y said:
Do i need to flash the kenel zip every time I update the the cm 14.1 zip file?
Click to expand...
Click to collapse
Yes, as when you flash the CM 14.1 build, the kernel that is provided with the build is also flashed, and that is not supported. So you need to flash it every time you flash a CM 14.1 build, but if you want to flash any other build, something like CM 13.0, then you need not as the kernels provided in those are supported.
aamodjoshi23 said:
Yes, as when you flash the CM 14.1 build, the kernel that is provided with the build is also flashed, and that is not supported. So you need to flash it every time you flash a CM 14.1 build, but if you want to flash any other build, something like CM 13.0, then you need not as the kernels provided in those are supported.
Click to expand...
Click to collapse
Hi,
I have a very specific problem. I rooted my Oneplus x few months back and everything was fine. I use to get update notifications and after downloading it use to update automatically. But since last 2 months i download the update files but it takes me to recovery and then i cant find the zip file to flash/install. (i also started using external sd card two months back, but not sure if it has to do anything with this). I tried searching a solution on web - tried checking 'system' under Mount tab, installed an app for auto update and some more but no use. I even connected my phone in recovery mode to laptop and copied the zip file to internal memory but while flashing it gave error.
Now i am not sure what the problem is. Do i need to update my recovery or something else. Pls help.
shashanksachdeva said:
Hi,
I have a very specific problem. I rooted my Oneplus x few months back and everything was fine. I use to get update notifications and after downloading it use to update automatically. But since last 2 months i download the update files but it takes me to recovery and then i cant find the zip file to flash/install. (i also started using external sd card two months back, but not sure if it has to do anything with this). I tried searching a solution on web - tried checking 'system' under Mount tab, installed an app for auto update and some more but no use. I even connected my phone in recovery mode to laptop and copied the zip file to internal memory but while flashing it gave error.
Now i am not sure what the problem is. Do i need to update my recovery or something else. Pls help.
Click to expand...
Click to collapse
First of all we need more info about your current ROM recovery etc.
Fap4k said:
First of all we need more info about your current ROM recovery etc.
Click to expand...
Click to collapse
I installed CM 13.0-20160928-NIGHTLY-onyx and the recovery is: TWRP v2.8.7.0 | blu_spark r8
I'll be grateful for a solution.
shashanksachdeva said:
I installed CM 13.0-20160928-NIGHTLY-onyx and the recovery is: TWRP v2.8.7.0 | blu_spark r8
I'll be grateful for a solution.
Click to expand...
Click to collapse
In October oneplus updated to 6.0.1 officially i.e OOS 3 it brings new bootloader to the device as you are using old recovery you can't flash new update..so you need to upgrade to latest bootloader by following thread available in general section or you can flash stock recovery and upgrade to latest OOS and flash whatever you want to flash..I recommend you to see how to upgrade bootloader in general section if you are planning to flash custom ROMs or if want to flash latest OOS then simply flash stock recovery and upgrade. onece you updated to OOS 3 after that you can flash new official twrp 3.0.3.0 from its official page.
Edit: for old bootloader you need stock 5.1.1 recovery..which is not available in official oneplus download page..so just follow below link
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Fap4k said:
In October oneplus updated to 6.0.1 officially i.e OOS 3 it brings new bootloader to the device as you are using old recovery you can't flash new update..so you need to upgrade to latest bootloader by following thread available in general section or you can flash stock recovery and upgrade to latest OOS and flash whatever you want to flash..I recommend you to see how to upgrade bootloader in general section if you are planning to flash custom ROMs or if want to flash latest OOS then simply flash stock recovery and upgrade. onece you updated to OOS 3 after that you can flash new official twrp 3.0.3.0 from its official page.
Edit: for old bootloader you need stock 5.1.1 recovery..which is not available in official oneplus download page..so just follow below link
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
shashanksachdeva said:
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
Click to expand...
Click to collapse
This is because you flashed wrong recovery twrp 3.0.3 is for new bootloader and you are on old bootloader..that's why it all happened..so you just need to flash old recovery..then follow given link to upgrade bootloader and recovery.
shashanksachdeva said:
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
Click to expand...
Click to collapse
I've got a good news and bad news for you.
The bad news is, no one has the older 2.8.x TWRP image files and there are no threads that have the download links for the older version of TWRP. So you're stuck and you have lost your recovery. You have lost everything... Having no recovery means you can't do a lot of things like factory reset, any wipe of a partition, you won't be able to update your system, you won't be able to flash zip files to enhance your experience and many more... I'm sorry my friend...
The good news is, I've got you covered. I had saved the older TWRP so that if anyone one day would need that recovery image, I would be able to help them.
Download the older TWRP from here : https://drive.google.com/file/d/0B2Ms-zaNd3SiTmpxX0UtYUV2R1k/view?usp=drivesdk
Flash it. You should get back your recovery.
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Plush suthar said:
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Click to expand...
Click to collapse
Which ROM you are on currently?
If possible post screenshot of about device in setting.
Fap4k said:
Which ROM you are on currently?
If possible post screenshot of about device in setting.
Click to expand...
Click to collapse
using resurrection remix marshmallow 6.0...
Plush suthar said:
using resurrection remix marshmallow 6.0...
Click to expand...
Click to collapse
Did you ever updated bootloader?
If not than update your bootloader and install latest recovery!!
Plush suthar said:
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Click to expand...
Click to collapse
By stuck on boot, I didn't know you meant that it showed only the OnePlus logo and not even powered by Android.
In that case, follow this guide to update your bootloader :
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917

[OP2] Can't boot into custom Rom's

Hello guys,
i'm having the problem that whatever custom rom i'm trying to install with TWRP it will boot forever(>15min).
The stock OxygenOS boots just fine.
Rom's i've tried LineageOS 14.1, Resurrection Remix 5.8.3, ViperOS and some inofficial CM/LOS 13 versions.
Of course i tried to install all of them cleanly.
Once the installation failed or was corrupted and I had to use this unbrick guid to get access to my phone again: https://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Things i've tried so far: Reinstall TWRP, try different versions of each ROM and TWRP
Do you have any suggestions? Thanks in advance!
UPDATE: With clean install of newest OxygenOS(3.5.8) SimCard isnt being recognized.
bump

[OP5] Error 7 when Installing LineageOS in TWRP

Hello,
Long story short. Moving from OP3T -> OP5, and I'd like to install LineageOS, or more preferably, the "new" MicroG (https://lineage.microg.org/).
Installed the latest TWRP according to the steps in this guide; https://wiki.lineageos.org/devices/cheeseburger/install
TWRP installed and everything transferred to the phone. Wiped the Cache, system and data. But trying to install i get an "Error 7" or more specifically: "Updater process Ended with ERROR: 7".
I have tried two versions of microG from (https://download.lineage.microg.org/cheeseburger/) and the latest "Normal" LineageOS. Same result. Also tried wiping the Dalvik Cache. Same error.
Any ideas?
Thanks for any help!
Update:
Downladed the latest OxygenOS from: https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
and that installed fine in TWRP. Still would like microG Lineage Though...
try multirom twrp
more_than_hater said:
try multirom twrp
Click to expand...
Click to collapse
Tried. Same Error.
You need to flash latest firmware
So this is strange....
I tried installing the latest AISOP, just for trying. And the installation process worked fine, but I got all sort of errors when android was starting - so i did a complete wipe and tried microG again... and it worked. So microG is installed now with "normal" TWRP.
This was happening to me while updating from OOS 5.0.0 to OOS 5.0.2, the culprit was twrp bluespark. Flashed the other twrp latest version and it resolved my issue.

Can't install any ROM.

Hi,
I used Lineage OS 17.1 Lavender on my Xiaomi Redmi Note 7. I used their recovery to install the ROM and open gapps. Recently I downloaded the Brave Browser and I wanted to enable rewards. I than googled, that Brave doesn't allow rewards on rooted phones. I decided to wipe the entire phone, since I don't use the root functionality and to re-flash Lineage OS 17.1. I factory reseted the phone and wiped everything, just like I did, when I installed Lineage for the first time. I clicked on "Yes" when prompted that the ISO couldn't be verified, and waited for the flash. After a while I was "greeted" with Updater process ended with Error 7. I did some research and found out that it is something to do with the updater file verification and that I should try and delete some lines. I did that, but the error persisted. I than decided to try another ROM. I used Pixel Experience since it was working on my device before. Unfortunatly I had no luck. Same error message. I than tried to flash TWRP with fastboot, which worked. Wiped my device, just like they say it in all the guides (Dalvik, Data, Cache) and tried to flash Lineage (still no luck), than PixelExperience (still no luck) and Magisk worked. After I flashed Magisk I tried Lineage and Pixel once again, but still the same error.
If you know, how to fix that error I will be so glad. Is it possible that my device is bricked and beyond recovery? Thank you in advance.
update your tvvrp
Which firmware do you have installed? Use stable to maximum compatibility, on some ROMs if you have latest you gonna get that error. Also, use the latest TWRP or Orange Fox.
As Tatoh said, this error occurs when you have old firmware flashed on your RN7, some roms require specific version but usually flashing latest stable will give you best compatibility, here you have xda links to latest xiaomi firmware files: https://forum.xda-developers.com/redmi-note-7/development/firmware-xiaomi-redmi-note-7-t3925871

Categories

Resources