Develop Bugs

couldn't boot to twrp recovery after flashing cm14

hi'
i have flashed cm14 nightly with aroma (gapps) on cm13 on my oneplus 3
now i couldn't go neither to recovery mode nor to current cm 14 rom to change my rom
i am out of ideas i tried in every possible way to my knowledge pleasee help me ........................

Flash the modified twrp 3.0.2-22 via fastboot.

Get modified twrp here i asume that you know how to flash it?
Boot in fastboot > fastboot flash recovery Recovery filename.img

I had the same problem. Flashing modified twrp worked for me, thanks! But now if I to flash stock recovery (to install otas), I can't boot to recovery. E: oxygenos otas can be installed with twrp, so no problem anymore

plz send me the link of modified twrp
i coudnt find it on google properly plz

Try the link given by Demian3112. It works

THQ thq soon much.. Its working
Demian3112 said:
Get modified twrp here i asume that you know how to flash it?
Boot in fastboot > fastboot flash recovery Recovery filename.img
Click to expand...
Click to collapse
Yes its working
Thank q very much

THQ thq soon much.. Its working
AJay27 said:
Try the link given by Demian3112. It works
Click to expand...
Click to collapse
THQ for ur valuable suggestion
My killer is back

Demian3112 said:
Get modified twrp here i asume that you know how to flash it?
Boot in fastboot > fastboot flash recovery Recovery filename.img
Click to expand...
Click to collapse
Hii,
Still the problem remains same I will explain in detail
I am back to cm14.1 when I flashed twrp from the above link
When I tried to flash some other ROMs they are flashed but screen goes blank after oneplus boot animation,
If I flash 14.1 ROM it is working fine
From cmd non of the recovery where flashed only the above is working
Plz help me
I want to go back to stock soon

It's because of the system partition rewriting issue. People in the cm and other communities are already working on it. Basically the boot partitions get rewritten when we install the cm 14.1 . It happens to some variants while others works fine. Just the issue because of not enough testing. Will be sorted out within time.
What you can do is. Use flashify app or fastboot from your pc and flash your twrp back after installing and booting into the cm 14.1. You can use any twrp no modified versions needed as far as it is supported by your device model. Ciao. Hit thanks if i helped.

sanjumalik720 said:
It's because of the system partition rewriting issue. People in the cm and other communities are already working on it. Basically the boot partitions get rewritten when we install the cm 14.1 . It happens to some variants while others works fine. Just the issue because of not enough testing. Will be sorted out within time.
What you can do is. Use flashify app or fastboot from your pc and flash your twrp back after installing and booting into the cm 14.1. You can use any twrp no modified versions needed as far as it is supported by your device model. Ciao. Hit thanks if i helped.
Click to expand...
Click to collapse
ohhh
then what is the solution ?????

Thank you very much
Demian3112 said:
Get modified twrp here i assume that you know how to flash it?
Boot in fastboot > fastboot flash recovery Recovery filename.img
Click to expand...
Click to collapse
I had the same problem as OP, got stuck with the CM 14 and did not like it (to early, to many bugs)
Wanted to go back to CM 13 but was unable to get into TWRP, and unable to flash CM13 back. Tried with fastboot and adb sideload, nothing worked.
The modified TWRP let me do i full wipe of the phone, (wiped Data, Dalik/ART, and system.) then copied the CM13 Stable release from here onto the phone, together with Gapps, and now everything is back to normal.
Again thank you, and thanks XDA! Somehow you always manage to save my ass after i messed with my device

Balaji Dasari said:
ohhh
then what is the solution ?????
Click to expand...
Click to collapse
Just flash the twrp image file again. The one you used before. Just flash it again. The same way you did back then.

Root for OxygenOS 4.1.6

Hello everyone, I am using OOS 4.1.6 on my new 3T, however I am unable to get root even though I have already tried with latest TWRP, magisk 12, and SuperSU 2.82. Nothing worked everytime I've got not rooted on root checker.

Please describe in steps what you did.

AcidNoteZ said:
Please describe in steps what you did.
Click to expand...
Click to collapse
Hi,
We unclocked the bootloader, then we did flash with twrp 3.1.0 and installed SU 2.82.
After doing all this, the phone was not restarting.

mittal.bti said:
Hi,
We unclocked the bootloader, then we did flash with twrp 3.1.0 and installed SU 2.82.
After doing all this, the phone was not restarting.
Click to expand...
Click to collapse
Well first of all, format your whole phone over TWRP. (System too, but make sure you have the full Oxygen OS zip on a computer.)
After formating all partitions, move the full OOS zip and Magisk 12.0 on your phone. Flash the OOS zip, restart your recovery and flash Magisk after it.
That worked 100% for me all the time.
If you still need assistance with that, we can setup Teamviewer so I can guide you through this.

mittal.bti said:
Hi,
We unclocked the bootloader, then we did flash with twrp 3.1.0 and installed SU 2.82.
After doing all this, the phone was not restarting.
Click to expand...
Click to collapse
Same here! The phone freezes in boot animation screen. Even the animation stopped!

Guessing it's about the f2fs file system. I used to have a situation like this with Oneplus 2. My step was to format data and cache partitions back to ext4, and that worked.
Using 3t now, still not rooted. Don't want to start over after bootloader unlocking
Sent from my ONEPLUS A3003 using Tapatalk

I had the same problem and was solved with twrp 3.0.4-1 and SuperSU-v2.82.

AcidNoteZ said:
Well first of all, format your whole phone over TWRP. (System too, but make sure you have the full Oxygen OS zip on a computer.)
After formating all partitions, move the full OOS zip and Magisk 12.0 on your phone. Flash the OOS zip, restart your recovery and flash Magisk after it.
That worked 100% for me all the time.
If you still need assistance with that, we can setup Teamviewer so I can guide you through this.
Click to expand...
Click to collapse
Should I flash whole os using twrp. Or should I flash Via adb sideload?

ajsonofgod said:
Should I flash whole os using twrp. Or should I flash Via adb sideload?
Click to expand...
Click to collapse
If you still want root, twrp, if dont flash it over adb

AcidNoteZ said:
If you still want root, twrp, if dont flash it over adb
Click to expand...
Click to collapse
Ok, I will try and update here then.

I'd say wipe everything possible in TWRP except for system partition, then boot the system and then eventually flash some kind of a root package - either Magisk or SuperSU. I always do it that way and it works. I am not really sure but otherwise it might have something to do with the data encryption.

Use following and you should be all set (just did it 2 days ago):
1st Flash Stock Recovery (go back to stock - https://forums.oneplus.net/threads/...-3-3t-and-go-back-completely-to-stock.456232/
Flash TWRP after you achieve STOCK OS 4.1.6.
Use this TWRP version for now (there is some issue with 3.1.1-2 i saw on forums):
twrp-3.1.1-0-oneplus3t.img
To Root just use Magisk-v13.3.zip (IMO way better than SuperSu + has MagiskHide for AndroidPay/Snapchat/SafetyNet checks):
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
That is it, done!

Showbiz81 said:
I had the same problem and was solved with twrp 3.0.4-1 and SuperSU-v2.82.
Click to expand...
Click to collapse
Thanks you are a life saver

I had the same problem and was solved with twrp 3.0.4-1 and Magisk-v13.3

Normal boot always ends up in TWRP

Hello everyone,
I have a problem regarding the start-up of my phone. Yesterday I unlocked my bootloader and flashed TWRP (twrp-3.1.1-0-addison.img) with the help of the thread located here.
Everything worked fine, I could boot into TWRP afterwards. I continued by wiping the needed partitions and flashing the newest Lineage OS ZIP alongside with the GApps Nano ZIP.
The problem I face now is that when I reboot in TWRP by selecting the “System” option, I end up again in TWRP (same happens if I shut down the phone and make a normal boot).
However, if I boot to the bootloader and select there the normal “start” option, the phone boots up just fine using the installed ROM.
Any ideas what’s wrong here and how I cloud fix that?

This happens with me, i don't know If its gonna work with you but works for me, i just flash a older twrp image from the same thread you use, ( i install from bootloader, not flashing a img in twrp), then you boot on twrp, and then you install the latest recovery
Note: This works for me, i don't know if its work for you
{Sorry for my poor english, my native language is porruguese }

jst98 said:
This happens with me, i don't know If its gonna work with you but works for me, i just flash a older twrp image from the same thread you use, ( i install from bootloader, not flashing a img in twrp), then you boot on twrp, and then you install the latest recovery
Note: This works for me, i don't know if its work for you
{Sorry for my poor english, my native language is porruguese }
Click to expand...
Click to collapse
Thanks a lot, I will give it a try!
and then you install the latest recovery
Click to expand...
Click to collapse
Do you mean TWRP or a recovery image of the OS?

When i say to intall the latest version is for twrp

Unfortunately, it did not work ....
I flashed twrp-3.0.2-0-addison.img via fastboot, booted to TWRP and installed the newest image with the 'install' option from TWRP.
Phone is still booting to the recovery if I restart ....

_Hope_ said:
Unfortunately, it did not work ....
I flashed twrp-3.0.2-0-addison.img via fastboot, booted to TWRP and installed the newest image with the 'install' option from TWRP.
Phone is still booting to the recovery if I restart ....
Click to expand...
Click to collapse
Aww ! It's just a simple thing. Use this simple command "fastboot oem fb_mode_clear" and it will boot to normal system.

I was also facing this in my previous htc device.
That was tha problem of tge twrp version that i was using.
Try using the different twrp.

Do i need to format data from twrp before flashing magisk in miui ?

I'm on 9.5.13 stable and i'm waiting for unlocking my bootloader, i heared that miui by default encrypt the phone, and after flashing magisk to get root, it will not boot unless i do format data from twrp to decrypt it, it that true or i'm missing something ?
I'm just want to get root on current build 9.5.13 to get some mods and enable camera2api without loosing all stock camera features.
Thanks in advance

Not true!
What your confusing things with, is when you flash TWRP, you need to flash lazyflasher to allow the device to boot. Or use a TWRP that includes a script to do so.
You can run the device encrypted if you want, but formatting data will let it run decrypted if magisk is flashed before booting rom.
Unlocking your bootloader will wipe data, so backup beforehand!

corkiejp said:
Not true!
What your confusing things with, is when you flash TWRP, you need to flash lazyflasher to allow the device to boot. Or use a TWRP that includes a script to do so.
You can run the device encrypted if you want, but formatting data will let it run decrypted if magisk is flashed before booting rom.
Unlocking your bootloader will wipe data, so backup beforehand!
Click to expand...
Click to collapse
Thanks for your help, unlocked my bootloader yesterday and flashed twrp, lazyflasher and magisk and everything is ok, no issues with booting, thanks again.

corkiejp said:
Not true!
What your confusing things with, is when you flash TWRP, you need to flash lazyflasher to allow the device to boot. Or use a TWRP that includes a script to do so.
You can run the device encrypted if you want, but formatting data will let it run decrypted if magisk is flashed before booting rom.
Unlocking your bootloader will wipe data, so backup beforehand!
Click to expand...
Click to collapse
I am new to Custom ROM installer. I had unlocked refmi note 5 pro using miui tool and flashed twrp recovery. But I could nt flash lazyflasher through twrp.
Now my mobile works fine in miui 10 . But I couldn't root it. I need to flash resurrection remix ROM .
Please help me

@sathishob you don't need root to flash a custom rom. Check the rom thread you want to flash for instructions and further assistance.

corkiejp said:
@sathishob you don't need root to flash a custom rom. Check the rom thread you want to flash for instructions and further assistance.
Click to expand...
Click to collapse
@corkiejpThank you for the support corkiejp... Successfully i flashed a custom ROM (Resurrection remix 7 ) but I couldn't use the banking apps and camera doesn't open . I tried to solve it without root. But I couldn't . So I installed magisik now everything works fine . ( I couldn't install magisik easily. It took several times to success. Most probably it says error 1 . Installed magisik uninstall then every thing went smoothly.)
Installing Aosp extended ROM I fixed camera issue and by flashing magisik banking apps are working
Thanks a lot for your valuable reply...

Hello guys
I had unlocked my whyred and flashed twrp recovery by fastboot. First time it went smoothly . after reboot phone went to stock mi recovery . I searched and found that to resolve this i have to install lazyflasher zip file . so i tried to flash that file through twrp. I could nt flash that file because it showed some error message . some how i tried two or more times to flash it with some other lazyflasher files . It did nothing . Then i installed twrp image file from twrp recovery suddenly issue was solved . properly phone booted on twrp recovery .
Then i tried to flash magisik but i couldnt flash it because it says error 1 as a reason . I tried some more ways to flash it but i can't find any solution . from the help of corkiejp i flashed the resurrection remix 7 successfully without flashing magisik. But my camera was not worked and banking apps are not worked .
So i flashed the aosp extended pie rom and the camera worked fine . but i could nt use banking apps. I searched for a way and landed on flashing magisik manager . again the error 1 prevented me to flash magisik . I flashed magisik uninstall zip and everything went smoothly.
Now my phone was properly rooted and working fine.
But my question is if until now i could nt flash lazy flashers prooerlybon my phone . is this make any harm to my phone ? Please help me
Thanks in advance ...

TWRP+ Magisk issues. HELP?

Hi! I have a moto z2 play with the Pie stock rom flashed. Bootloader is unlocked but when I try to flash TWRP (used twrp_albus_treble_3.2.2_r23_64) via fastboot after the first system reboot it is always overwritten by default recovery. I tried to boot first to bootloader and than to TWRP, also tried booting the TWRP image and installing TWRP from phone storage, nothing works after system reboot it is always replaced by stock recovery. What am I doing wrong?
I also tried to install Magisk but it wont install, tried flashing through TWRP and also by patching the boot.img than flashing that.
Could use your input!
Thanks!

I have the same problem
I have the same problem

L7noop said:
I have the same problem
Click to expand...
Click to collapse
Did you find a working solution?