Develop Bugs

How to convert cyanogen recovery in twrp

Hi,
I have tried installing LineageOs 13 from guide on this forum but i had problem with gapps.
I had CWM 6.x installed....
After many attempts, I don't know why, on reboot, I found "cyanogenmod recovery" instead of CWR.
I used a wrong option and wiped all , also rom and gapps file.
After many test on many pc (usb driver problem) I was able to install again lineageOS using "adb sideload"
On my pc adb devices works (and i see phone id and sideload label) but fastboot devices not work.
Now I tried to install twrp but the recovery tell me that can't verify the signature (CWM instead ask about ignore warning)
Also gapps i can't install for the same reason.
LineageOs is a signed package and works.
So my question is
1) how i can now replace cyanogenmod recovery with twrp using what i have now? I can only (in this moment) update .zip signed (or tell me how fix this problem)
2) install gapps (are not signed but if i solve previous item i can be able to fix also this)
3) why fastboot don't work? need a recovery more powerfull?
Best reagards

root problem after update to beta 19

hi,
my oneplus 3 has been rote since i got it (i bought it on launch day) but since i updated it to the beta 19, my phone is no longer rooted : when i put the phone in fastboot it says that my bootloader it unlocked but all the apps who requier root are saying that the phne is not rooted and i cant get twrp to work. i tryied with the official app on my phone and with a program called "tool all in one" (https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3398993) and when i flash twrp from the program, i can boot into twrp but then i can't access my files and after i boot the phone, i can no longer boot to twrp
does anyone have a solution that doesn't involve me wiping the phone?

You loose root after updating. Try installing twrp again and then rooting it. Use the toolkit for oneplus 3. Simplifies the process

what do you mean by "then rooting it" ?
the program i use does the same thing as the toolkit and when i install twrp, as i said, it can boot on twrp one time and in twrp i can't access my files and after i boot the phone i can't get back to twrp ,i get the stock recovery

Unless your ROM has built-in root, after flashing TWRP, you have to flash SuperSU or Magisk to obtain root. Mere flashing of TWRP will not give you root.

I know but i can't get to the folder when the magisk file is : when in boot into twrp i cant see my files

Few details... it's quite difficult to help you.
What's the root method? Magisk, SuperSU or Kingroot? Which version?
Ps TWRP recovery is not depending by root, you just need to unlock bootloader (surely it's already unlocked) and flash the same recovery, from PC, via the command "fastboot flash recovery filename.img".
Now enter in TWRP:
1) Wipe /system and /cache;
2) Flash another time Open Beta 19;
3) Flash Magisk or SuperSU (be sure to have latest release);
4) Move TWRP img file from computer to device, then flash it another time (because firmware provides the OOS stock recovery);
5) Reboot and wait 5-10 minutes, because of cache rebuilding.
Tell me if you solve

I am using magisk
Yes my bootloader is unlocked
My problem is that when i flash twrp i cant access my files so i don't want to wipe system if i cant reflash something after
I think that I'll wait for the next update, maybe then it will work
But thank you for your help

Which version of TWRP do you have? Try eng.stk's latest version.

I tryied 3.1.1-2
The eng.stk is not available anymore

Your phone is encrypted, so you have to format data ( but your internal storage wiped by formating data, so back it up ,then only twrp read files in your storage)and flash custom kernel then boot restore backup .

how do you know that my phone is encrypted? i never encrypted it
i use titanium backup so i can't back my phone up until i get rot back

Whenever you flash stock ROM it encrypt if you boot into system directly . So twrp could not read internal storage. Whenever you flash stock ROM you must flash custom kernel or any other method to avoid encryption. This is happened to me and what I'd done is flash custom kernel before boot into rom
To save your data try this
https://forum.xda-developers.com/oneplus-3/how-to/unencrypt-oxygenos-loosing-data-t3412228

Who said that? Check this: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Edit: If you want to save items in internal storage, you can use ADB commands instead of TWRP. You can also simply copy and paste if your PC recognises the internal storage of your phone.

I succeeded but i had to clean everything and use the last backup i made a week ago
Thank you all for your help

Google pixel XL - Lineageos 15.1 " NO os installed "

Hello
i would like try Lineageos, I went from BenzoRom To lineage-15.1-20181114-nightly-marlin-signed
I follow this link
https://www.xda-developers.com/google-pixel-xl-lineageos-15-1/
but when a reboot twrp 3.2.3-1 ( marlin in the slot A ) it say
" NO os installed ! ..... "
Where am i wrong?
Lele
Ps I can see lineage recovery mode

Which benzo room did you come from?
If you came from a 9.0 rom you may have to flash factory 8.1 before going to lineage 15.1.
Download lineage 16, wipe system/cache/data, install lineage 16 and twrp, reboot to recovery, install gapps, reboot, profit

It says that, doesn't mean it's true. Happens to me as well.

Sorry I did not get the notification!!!
Thank i will try
Leel

I am having a very similar problem with my Google Pixel (model G-2PW4100, not XL). After spending many hours attempting to install LineageOS 15.1 (LOS) and executing just about every possible permutation of installation steps, I am at a loss for why it is failing. I get the "No OS installed", yet sometimes when I reboot after installing the LOS zip file via TWRP I am able to boot to the LOS 15.1 recovery; however, a subsequent reboot always takes me back to the bootloader menu.
I am using the following files:
(Google OTA stock 8.1.0 (OPM4.171019.021.P1, Jul 2018)): sailfish-ota-opm4.171019.021.p1-9fe2c539.zip
(LOS-zip): lineage-15.1-20181229-nightly-sailfish-signed.zip
(TWRP-img): twrp-3.2.3-1-sailfish.img
I start by booting to the bootloader menu (POWER+VOLUME DOWN from OFF). With the phone connected to USB, on the host machine I execute
Code:
fastboot boot twrp-3.2.3-1-sailfish.img
which boots into TWRP recovery. There I use
Code:
adb push sailfish-ota-opm4.171019.021.p1-9fe2c539.zip /sdcard/
to push the stock Google image, and then I use TWRP's install from zip file. It successfully reboots to the stock Android and I can go through the phone setup and everything works fine. Next, I power off the phone and then boot to the bootloader menu. I repeat the fastboot command above to load TWRP recovery. In TWRP, I use adb push to push the LOS zip file. I follow the LOS wiki "sailfish" installation instructions precisely from that point, but I am never able to boot into a working LOS system. It either loads the custom LOS 15.1 recovery one time, after which it reboots to the bootloader, or it just reboots to the bootloader. I have tried repeating these steps in an attempt to install the same software on both slots A and B in case that is an issue, but it does not make any difference.
Can someone help me figure out what I am doing wrong?

i tried some stuff to change the rom i am lost please help

software status modified i wand to use linieageos with gapps and recovery TWRP somone to help me stap by step and save my life!!!!
love you all

You need to download the latest twrp for the Z2F/Nash from the TWRP site. One of the files is the twrp installer, which should be moved to your z2's sdcard. The img file stays on a PC.
Before you do anything, the Android platform tools should be present. Or you can instead install minimal adb/fastboot from XDA. Once you boot twrp you have to format data and type yes, so the rom and other files should be on an SD card. Alternatively, one may opt for adb sideload.
1.Flash LOS. Without rebooting, flash the twrp installer otherwise it won't stick.
2.Reboot recovery and flash gapps, then reboot recovery again
3. Reboot system

Desperate cry for help

The title might sound a bit extreme but hear me out. Earlier I was updating Havoc-OS to the latest June 12th, 2019 build. Upon flashing it within the TWRP recovery it asked to update the firmware. The firmware that it required was V10.3.1.0.PEIMIXM. I flashed fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d2c9f2aa_9.0 from the website where all of the firmwares are managed, but ever since I did this my recovery has then broken itself (ARB as well? Give me a second..). Every time I go into TWRP and want to transfer files, there is no way for me to transfer files from my phone to the computer and vice versa. MTP is enabled but I just cannot transfer files what so ever. I tried to reflash TWRP, update to the latest version and it still has not worked. One thing I have noticed while flashing TWRP within Fastboot was that it didn't require me to use the dummy.img in order to flash via fastboot which I thought was strange, knowing that my phone has ARB Level: 4. I have since then used Mi Flash tool to get the phone working again but every time I try to flash TWRP, MTP still will not enable and I have no idea what to do. I'm so scared as to what to do next because I don't know what to do. Please any help or suggestions?

BlackHawk580 said:
The title might sound a bit extreme but hear me out. Earlier I was updating Havoc-OS to the latest June 12th, 2019 build. Upon flashing it within the TWRP recovery it asked to update the firmware. The firmware that it required was V10.3.1.0.PEIMIXM. I flashed fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d2c9f2aa_9.0 from the website where all of the firmwares are managed, but ever since I did this my recovery has then broken itself (ARB as well? Give me a second..). Every time I go into TWRP and want to transfer files, there is no way for me to transfer files from my phone to the computer and vice versa. MTP is enabled but I just cannot transfer files what so ever. I tried to reflash TWRP, update to the latest version and it still has not worked. One thing I have noticed while flashing TWRP within Fastboot was that it didn't require me to use the dummy.img in order to flash via fastboot which I thought was strange, knowing that my phone has ARB Level: 4. I have since then used Mi Flash tool to get the phone working again but every time I try to flash TWRP, MTP still will not enable and I have no idea what to do. I'm so scared as to what to do next because I don't know what to do. Please any help or suggestions?
Click to expand...
Click to collapse
Go to developer options, disable USB debugging and then enable it again connected to pc and wait that a pop-up appears on device screen, tap on always allow, then within adb/fastboot folder try to send device to recovery with "adb reboot recovery" see if was solved, if not then try erasing recovery partition through fastboot with "fastboot erase recovery" then flash TWRP again as usually, disconnect from pc before to boot to it, then in TWRP connect to pc and wait that pc recognice it.
If the issue persists you can uninstall and delete all the files related with drivers on pc directories and then make again a clean install also wiping cache/dalvik onto your device.

It's because u used the twrp meant for oreo firmware. It is incompatibile with new pie fw, you must flash latest twrp for example twrp 3.3.1 using fastboot. Use adb commands: 1.adb,2.adb shell,3.adb fastboot boot (location of the twrp 3.3.1) for example C:\twrp.... .img and then from the recovery flash twrp 3.3.1 as recovery.

i had same problem.
i installed latest global stable miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d 2c9f2aa_9.0 rom from sd card.
MTP is working properly.
but there is problem for me after that.
This is strange problem.
after installing miui rom twrp recovery uninstalls automatically after reboot,when install twrp via boot it encrypts twrp.
can anyone help me?
my problem is-
after all this if i try to install custom rom(from sd card) it says corrupt file or error 7 ,i tried to flash 3-4 different rom.
EDIT: my problem solved after installing this twrp https://androidfilehost.com/?fid=6006931924117884758 (from AOSP ext pie rom thread)