Develop Bugs

Recovery not working.

EDIT: Resolved by following Naman Bhalla's Unbrick Guide.
I'm on latest Freedom OS community build right now. I have this problem where my OP3 won't boot into recovery at all. Trying to do it just kills it and only a very long power button press is able to revive it.
I have tried flashing the recovery via fastboot but that also doesn't work. Is there a way out of it? I can't flash zips. Are there factory images I can flash via fastboot that can replace everything? I don't care about the data. Any help would be appreciated.

flash modified recovery via fastboot
Sent from my ONEPLUS A3003 using Tapatalk

I have tried Garak's TWRP and the other TWRP. It doesn't change anything. Are there factory images like Google provides which can be flashed using fastboot?

i have the same problem, flashed the previouse version of Oxygen OS. But now i can't get in to recovery.. when i flash it trough fastboot everything goes ok, but when i want to go into recovery the screen is blank and the device does nothing.

Maybe read the OP of FreedomOS rom.

NevaX1 said:
Maybe read the OP of FreedomOS rom.
Click to expand...
Click to collapse
I have read the OP of Freedom OS. I understand that obviously I overlooked something because of which I ended up where I am but I am looking for solutions here. I did not dirty flash the community build if that's what you mean.

n33raj18 said:
I have read the OP of Freedom OS. I understand that obviously I overlooked something because of which I ended up where I am but I am looking for solutions here. I did not dirty flash the community build if that's what you mean.
Click to expand...
Click to collapse
You need the modified twrp version, the only way to recognize it, it has a mouse cursor in the middle of your screen.

n33raj18 said:
I'm on latest Freedom OS community build right now. I have this problem where my OP3 won't boot into recovery at all. Trying to do it just kills it and only a very long power button press is able to revive it.
I have tried flashing the recovery via fastboot but that also doesn't work. Is there a way out of it? I can't flash zips. Are there factory images I can flash via fastboot that can replace everything? I don't care about the data. Any help would be appreciated.
Click to expand...
Click to collapse
I tried that I got the same error and wipe everything even internal then got a thread in unbrick oneplus 3 and it worked try method 2 link (http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700)

NevaX1 said:
You need the modified twrp version, the only way to recognize it, it has a mouse cursor in the middle of your screen.
Click to expand...
Click to collapse
I had the same problem with 'no recovery' and this helped!
Thanks!
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56

vvverma said:
I tried that I got the same error and wipe everything even internal then got a thread in unbrick oneplus 3 and it worked try method 2 link (http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700)
Click to expand...
Click to collapse
Yea, I used exactly the same thing to get back my device working correctly again. I missed the crucial information that modified TWRP was required.

Can't boot into recovery after cm14.1 nightly official

So as the title says, after flashing cm14. 1 can't go into recovery anymore, it just a black screen. I tried to use flashify but nothing, a couple of apps show that I have twrp 3.0.2.1 but can't get into it... Help?
Cheers

Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get

JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Which thread is this from please?

JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Yeah man im in the same boat, if i get time ill try this twrp recovery. Where did that recovery come from?, it seems like the CM recovery for 14.1 nightly high jacks the recovery partition (i call it that,i dont know the term for it)
Sent from my ONEPLUS A3000 using Tapatalk

I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.

Hw4ng3r said:
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Click to expand...
Click to collapse
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.

Thanks a lot guys, that did the trick, and done with flashify

JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
@JKMB888 it does work 100% is as simple as flashing the TWRP. Actually, i installed it with CM 14.1 running just fine
Sent from my ONEPLUS A3000 using Tapatalk

Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.

Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Edit: I found the solution, i had a pattern lock screen and i removed it!

HC4Life said:
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Click to expand...
Click to collapse
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.

GrandMasterB said:
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
Click to expand...
Click to collapse
Look at my edited reply...

m4manusraj said:
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Click to expand...
Click to collapse
actually flashify did the trick for me as I had no access to a pc for the time

http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me

JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
i am facing just the same situation with cm14.1 nightly and can't boot into recovery
i tried flashing the recovery image provided by you i.e. twrp-3.0.2-22-oneplus3.img but i face the same problem again
when i go into the recovery all i see is a black screen with a white notification light on and it remains there untill i switch off my phone manually using the power button
i tried facing the problem when i installed the cm14.1 nightly
i was unable to login snapchat as i device was rooted as said by the message on snapchat
so i decided to unroot my device via supersu FULL UNROOT option
after a reboot i successfully logged into snapchat
then i tried to root it again
i went into recovery to flash the supersu zip
and since then i have been unable to see the twrp recovey
please help me

This thread is a life save. Tried everything and it drove me nuts not getting into recovery.
THANK YOU!

gangangan2 said:
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
Click to expand...
Click to collapse
Thank you so much it's work for me now..

After I got the recovery back, I flashed CM13 again and ARM64 6.0 Nano Gapps for my Oneplus 3, but I'm getting an error after the "preparing apps' screen is loaded saying that - unfortunately the process android.process.media has stopped one plus 3 boot and then the phone switches off.
Any solution to this? I've already tried flashing different versions of CM13.

Thank you!! I was looking for hours.
This link fixed the problem!
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse

Hey, guys. I'm pretty sure I bricked my phone and there's no way to get out.
So I was on CM13 official builds on my OP3. Then, on the OTA update system they have, I got moved onto the CM14.1. I downloaded from here and went into my twrp recovery to flash. I made a clean flash and then proceeded to go back to system. I thought everything was ok until I realised I hadn't flashed a gapps package which I pretty much need to survive as all my contacts backups etc. are on there. I powered off my phone and went to go back into the recovery after downloading gapps 7.1 micro. It went past the *You're device can not be trusted'* and then went to the oneplus screen. After that, it stayed like that for about 30 secs and powered off. At first, I thought I messed something up and tried again. I repeated that for about 3 times and it didn't work. I tried going into the normal system and coming back to recovery and it didn't work still. In fact, now I can't even get into system. Now, i can only boot up to fastboot, where my computer still doesn't realise my phone is plugged in.
Anyone got any ideas on how to fix this? I wouldn't say I'm a noob at this because I have flashed many times before but I'm relatively new to the scene. I didn't see this thread before i ripped my hair out and i think wrecked my phone @JKMB888
EDIT: I sorted it out with help from Naman Bhalla's unbrick thread and this. A certain combo works and now I'm on CM14.1 enjoying life

OP3 TWRP not Booting

Hello there,
This is my first XDA thread! This is an issue I ran into.
I just installed CM 14.1 on my OP3. I downloaded the latest TWRP from the official website before flashing it.
Here is the problem. After setting up my ROM, like installing all the required apps, I'm not able to boot into recovery. I tried flashing TWRP again, I downloaded the oneplus recovery from your website and I flashed that one too.
I erased recovery partition and installed both of them again (erasing each time). What happens is, after booting into the bootloader, I select recovery to go to the recovery and it stays blank, unless I reset it by holding the buttons.
Please let me know what I can do.

Same happened to me also. But somehow I fixed it by installing TWRP again by using OnrPlus 3 toolkit. Here is the toolkit forum.xda-developers.com/oneplus-3/development/tool-tool-one-driversunlocktwrpfactory-t3398993. Can't post links. Don't forget to put http:// front of it

SillyPython said:
Same happened to me also. But somehow I fixed it by installing TWRP again by using OnrPlus 3 toolkit. Here is the toolkit forum.xda-developers.com/oneplus-3/development/tool-tool-one-driversunlocktwrpfactory-t3398993. Can't post links. Don't forget to put http:// front of it
Click to expand...
Click to collapse
Thanks for the reply.
Are you sure what happened to is exactly what happened to you? Because I tried the ToolKit and it is not working. I tried both the versions of the TWRP and Stock recovery.
If you know anything else about this issue that would help me. I'd love to hear it.

SillyPython said:
Same happened to me also. But somehow I fixed it by installing TWRP again by using OnrPlus 3 toolkit. Here is the toolkit forum.xda-developers.com/oneplus-3/development/tool-tool-one-driversunlocktwrpfactory-t3398993. Can't post links. Don't forget to put http:// front of it
Click to expand...
Click to collapse
Also. Does encryption affect this in anyway, because I did it. I don't want to factory reset my phone because this is my primary phone and I don't have another phone. And I don't want to risk it, at least for a few days.

malachiseelam said:
Hello there,
This is my first XDA thread! This is an issue I ran into.
I just installed CM 14.1 on my OP3. I downloaded the latest TWRP from the official website before flashing it.
Here is the problem. After setting up my ROM, like installing all the required apps, I'm not able to boot into recovery. I tried flashing TWRP again, I downloaded the oneplus recovery from your website and I flashed that one too.
I erased recovery partition and installed both of them again (erasing each time). What happens is, after booting into the bootloader, I select recovery to go to the recovery and it stays blank, unless I reset it by holding the buttons.
Please let me know what I can do.
Click to expand...
Click to collapse
Modified TWRP version should do it

Same, when I flashed cm 14.1 I also got blank TWRP.

michielokt said:
Same, when I flashed cm 14.1 I also got blank TWRP.
Click to expand...
Click to collapse
Then, what did you do?

LS.xD said:
Modified TWRP version should do it
Click to expand...
Click to collapse
Thanks LS.xD. You are awesome. I completely messed up my old Moto X and I didn't have a smartphone until now. I hesitated a lot before installing all custom stuff until I gave in. And this problem made me worry a lot.
Thanks a lot.
michielokt said:
Same, when I flashed cm 14.1 I also got blank TWRP.
Click to expand...
Click to collapse
Michielokt, you should try flash the recovery LS.xD gave the link to, it booted.

malachiseelam said:
Thanks LS.xD. You are awesome. I completely messed up my old Moto X and I didn't have a smartphone until now. I hesitated a lot before installing all custom stuff until I gave in. And this problem made me worry a lot.
Thanks a lot.
Michielokt, you should try flash the recovery LS.xD gave the link to, it booted.
Click to expand...
Click to collapse
Thanks it worked!

Please try the modified TWRP, 3.0.2-22

[FIX] No More annoying Red | Blue Blink on Status Bar

ColorOS users with device decrypted or rooted should have Red blinking on status bar which is quite annoying. So here is the solution, I have patched SystemUI.apk which shouldn't display red blink.
Bonus: Upon request by few users I have also removed Blue Blink too which was supposed to be triggered when Hotspot is enabled.​
The below zip file works for A20, A21 & A22. Download, reboot to recovery & flash. Enjoy
SystemUI_R2Pro_Patched.zip​​
Thanks @gt_ablaze for testing​

@4j17h
Make for A21 version

Meraj018 said:
@4j17h
Make for A21 version
Click to expand...
Click to collapse
Sorry, I didn't update the post. But yeah it should work for A21 too.

awesome..
it work on A21..

Great..
it work. Lite v2
Thanks

Hi @4j17h, I was using xposed module to hide root notification, I uninstalled it before flashing this zip, I've tried flashing multiple times. It seems that it doesn't work. Is there any other way?

victor_chan777 said:
Hi @4j17h, I was using xposed module to hide root notification, I uninstalled it before flashing this zip, I've tried flashing multiple times. It seems that it doesn't work. Is there any other way?
Click to expand...
Click to collapse
There seems to be issues with the custom recovery, zip isn't getting installed. Only way to confirm that the zip is installed is to check /system/priv-app/SystemUI/ oat folder shouldn't be there.
Follow this, freshly boot into recovery then flash firmware, then install zip & flash magisk reboot. This is how other ppl did.

victor_chan777 said:
Hi @4j17h, I was using xposed module to hide root notification, I uninstalled it before flashing this zip, I've tried flashing multiple times. It seems that it doesn't work. Is there any other way?
Click to expand...
Click to collapse
change recovery. use twrp ( blue) to flash.
r2x red recovery not working.

4j17h said:
There seems to be issues with the custom recovery, zip isn't getting installed. Only way to confirm that the zip is installed is to check /system/priv-app/SystemUI/ oat folder shouldn't be there.
Follow this, freshly boot into recovery then flash firmware, then install zip & flash magisk reboot. This is how other ppl did.
Click to expand...
Click to collapse
Hi, suggestion by @iki_sure works for me. Now no more xposed modules needed anymore. Thank you.

Flash without decryption?
Can we flash it by installing twrp recovery without decryption as data will be deleted while decrypting device

4j17h said:
Sorry, I didn't update the post. But yeah it should work for A21 too.
Click to expand...
Click to collapse
This is awesome work and I was looking for this for a long long time. I had an OTA to C.22 yesterday, are there any plans to make this fix available for C22 as well?
Thanks in advance!
EDIT: I went ahead and tried it, works like a charm!! And a big thanks to @iki_sure as I was trying R2X2 and after I switched to TWRP I was able to get this patch to work. Thanks a ton @4j17h

morfys said:
This is awesome work and I was looking for this for a long long time. I had an OTA to C.22 yesterday, are there any plans to make this fix available for C22 as well?
Thanks in advance!
EDIT: I went ahead and tried it, works like a charm!! And a big thanks to @iki_sure as I was trying R2X2 and after I switched to TWRP I was able to get this patch to work. Thanks a ton @4j17h
Click to expand...
Click to collapse
Which custom rom are you using in realme 2 pro, lite OS v2, or any other, cause i am on unrooted stock C22 update, was planning to move to custom rom, any advice would be appretiated.
Thanks in advance

It's not working on realme 2 pro with lite os v2.make another solution

TWRP fails to boot on Android 11, 'Error verifying the received boot.img: Invalid Parameter'

I successfully rooted the phone using Magisk, and looking at how to install LineageOS, I saw I needed TWRP first. I followed all the instructions, but when I use fastboot to boot twrp.img, I get the following error message, "Error verifying the received boot.img: Invalid Parameter". Searching for an answer, I saw there was an old issue with TWRP with the Pixel 3a XL and Android 10, but I found nothing more recent about Android 11.
I thought maybe I shouldn't have rooted the phone first, so I reflashed with the stock boot.img and tried TWRP again, but that doesn't solve it. Any idea how I can boot TWRP? Or is there a way to install LineageOS with TWRP? Thanks!
Build # RQ2A.2100505.002
TWRP image twrp-3.5.2_9-0-bonito.img

Twrp doesn't work currently for android 10+
You don't need it to install lineage, just flash the lineage recovery and follow the wiki install guide.
Install LineageOS on bonito | LineageOS Wiki
wiki.lineageos.org

If TWRP does not work on Android 10+ what are we doing about flashing custom roms? Booting the TWRP and then sideloading the ROM?
I need help. When I try to boot TWRP(assuming its possible) I get an error :invalid parameter, error verifying the boot image. I am on Android 11. Yes, Ive used the search function or else I would not have found this thread.
I do not want to flash lineage, but the instructions are vague in other ROM threads.

I just built a TWRP that works on Android 11. I wasn't sure how much interest there was in it, though, so I didn't bother posting it anywhere. I'll consider it once I clean up the source a bit.

Captain_Throwback said:
I just built a TWRP that works on Android 11. I wasn't sure how much interest there was in it, though, so I didn't bother posting it anywhere. I'll consider it once I clean up the source a bit.
Click to expand...
Click to collapse
Please post it! It would be greatly appreciated!

ncrawler said:
Please post it! It would be greatly appreciated!
Click to expand...
Click to collapse
I posted it on Telegram here: https://t.me/pixel3a/161825

Captain_Throwback said:
I posted it on Telegram here: https://t.me/pixel3a/161825
Click to expand...
Click to collapse
Thank You! I've been waiting for this!

I cant get your twrp and magisk to work together? I can only get one or the other working.

ncrawler said:
I cant get your twrp and magisk to work together? I can only get one or the other working.
Click to expand...
Click to collapse
Boot TWRP, copy image to device, use Install Image -> Install Recovery Ramdisk to install TWRP, then flash Magisk.apk.
I've done it a bunch of times and it works fine. Is that what you're doing?

Captain_Throwback said:
Boot TWRP, copy image to device, use Install Image -> Install Recovery Ramdisk to install TWRP, then flash Magisk.apk.
I've done it a bunch of times and it works fine. Is that what you're doing?
Click to expand...
Click to collapse
Done it about 10 times and never boots again

ncrawler said:
Done it about 10 times and never boots again
Click to expand...
Click to collapse
with or without lmza kernel

ncrawler said:
with or without lmza kernel
Click to expand...
Click to collapse
No idea what to tell you. It works for users in the TG group and it works for me. That's the exact process I'm using. You can alternatively try the Advanced -> Flash Current TWRP option and then flash Magisk and see what happens.

Thanks! I think I got it! Think I was using the wrong Magisk! I Guess I still have to use lmza kernel to pass integrity in magisk?

ncrawler said:
Thanks! I think I got it! Think I was using the wrong Magisk! I Guess I still have to use lmza kernel to pass integrity in magisk?
Click to expand...
Click to collapse
I have no idea about any specific kernel or integrity checks in Magisk. I only build TWRP.