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

Recovery Screen Blank!

Hi,
I have a unlocked bootloader and a rooted phone(OnePlus3). I was clean flashing to a newer cm14 nightly on my oneplus 3 when I discovered a while later that my phone wouldn't boot into recovery mode. After flashing TWRP recovery, I booted onto my phone and selected recovery in the advanced reboot menu however it started to flash into fastboot whether i tried to fboot into recovery or into fastboot. So i, maybe mistakenly(i'm not sure), flashed stock recovery in command prompt and now there seems to be ,arginal improvement as I think a recovery mode may exist however the screen is blank so i have to power off by holding the button for a couple of seconds before anything appears on the screen and it does but only for fastboot and booting onto the system. Please help, I want to revert to Stock Oxygen OS with TWRP recovery but am unable to do do. I find it imperative for this to get resolved as my phone doesn't have gapps and doesn't offer much use beyond browsing. Any help would be massively appreciated.
Thanks!
P.S I apologise, in advance, if i have broken any forum rules; please tell me if I have so i will know not to do so again
P.P.S I may not understand some procedures or terms mentioned so please explain fully what to do as if I'm a complete noobie

I'm not quite understanding your situation. Can you get into fastboot or adb mode or no?
You can also skip right to http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700 and follow Method 2.
On a side note, what version of TWRP were you on? You need to be on the modified TWRP, not the official TWRP, for official 14.1 nightlies.

Hw4ng3r said:
I'm not quite understanding your situation. Can you get into fastboot or adb mode or no?
You can also skip right to http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700 and follow Method 2.
Click to expand...
Click to collapse
Yes i can get into fastboot mode on my phone but the problem present is recovery mode has a blank screen . And command prompt recognises my phone when I type fastboot devices.

Log_0 said:
Yes i can get into fastboot mode on my phone but the problem present is recovery mode has a blank screen . And command prompt recognises my phone when I type fastboot devices.
Click to expand...
Click to collapse
I'm guessing you're running official TWRP? Official 14.1 nightlies needs the modified TWRP http://forum.xda-developers.com/devdb/project/dl/?id=21065. If you have fastboot access, you should be able to flash this version.

Hw4ng3r said:
I'm guessing you're running official TWRP? Official 14.1 nightlies needs the modified TWRP http://forum.xda-developers.com/devdb/project/dl/?id=21065. If you have fastboot access, you should be able to flash this version.
Click to expand...
Click to collapse
By official TWRP, you mean? I don't understand that since i have no visible recovery. And thanks for the modified version... Never knew about that. Hopefully this works.
Thanks!

Log_0 said:
By official TWRP, you mean? I don't understand that since i have no visible recovery. And thanks for the modified version... Never knew about that. Hopefully this works.
Thanks!
Click to expand...
Click to collapse
Just the version that is "officially" released by TeamWin. I believe current official version is 3.0.2-1

Hw4ng3r said:
I'm guessing you're running official TWRP? Official 14.1 nightlies needs the modified TWRP http://forum.xda-developers.com/devdb/project/dl/?id=21065. If you have fastboot access, you should be able to flash this version.
Click to expand...
Click to collapse
Thanks so much! It worked!!!
Really, thank you:laugh::laugh:

Log_0 said:
Thanks so much! It worked!!!
Really, thank you:laugh::laugh:
Click to expand...
Click to collapse
Glad to hear!
Enjoy the phone!

Assistance regarding a possible bricked op3

Hi guys, I searched around the forum before posting this so I apologize but I recently installed a new rom and possibly a wrong kernel with it. Afterwards, if I try to turn it on, it just shows the logo and then turns right off. I can't even go into recovery since it does the same. The only thing I can do is boot it into fastboot but I'm not sure where to go from here. I tried using a guide with no success.
Any words of wisdom?

reflash your recovery via fastboot, then boot into recovery and do a clean install
fastboot flash [recovery].img

I tried reflashing recovery but all it does is show the old rom logo that was used and then shuts down.

Hi,
Read carefully and try this guide:
forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700

which rom did you flash? You need the correct twrp file for your bootloader.

That's the first place I tried. Anytime I hook-up my phone to the PC it shows up as OnePlus Android bootloader interface under Android phone and I can't seem to update the drivers..

matze19999 said:
which rom did you flash? You need the correct twrp file for your bootloader.
Click to expand...
Click to collapse
I used the Freedom Rom 2.0

Arken2121 said:
I used the Freedom Rom 2.0
Click to expand...
Click to collapse
you need this twrp file:
https://forum.xda-developers.com/devdb/project/dl/?id=21835

matze19999 said:
you need this twrp file:
https://forum.xda-developers.com/devdb/project/dl/?id=21835
Click to expand...
Click to collapse
Thank you so much, I guess I installed the wrong TWRP and I can FINALLY get into recovery. Thank you so much.

TWRP 3.2.3-1 for Pixel 2 XL

Note: Do not use if you have multiple users (including a guest user)
Lots more information here: https://plus.google.com/u/1/+DeesTroy/posts/i33ygUi7tiu
I strongly recommend that kernel developers start building the touch drivers into the kernel instead of depending on modules to ensure a fully functional TWRP since recovery is now part of the boot partition.
Be careful about what you install on your device as far as kernels and ROMs go. I think there is a high potential for losing the ability to decrypt because of the OS and patch level tags that are included in the boot image and the anti-rollback features that Google has implemented.
MTP does not work in TWRP on the Pixel 2 and will not work until we have time to update the TWRP MTP implementation. You may still use adb to push and pull files.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, you will need to reflash root.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set
Pixel 2:
https://twrp.me/google/googlepixel2.html
https://dl.twrp.me/walleye/
Pixel 2 XL:
https://twrp.me/google/googlepixel2xl.html
https://dl.twrp.me/taimen/

Reserved!

Awesome to see the progress here, thank you for working on it and dealing with all the impatient requests. Will definitely be keeping an eye on this thread ?

Hurray for progress!

fastboot boot /path/to/twrp.img reboots into TWRP, but it never goes past the teamwin splash screen. I am able to reboot the phone normally after that, so no biggie.
I don't have time now to mess with figuring out how to get you logs, but I'll do that later this evening. Just wanted to give you a quick "what happened when I tried it."
And THANK YOU for working on this for us so quickly!
Edit: The logs are posted here:
https://forum.xda-developers.com/pixel-2-xl/development/twrp-alpha-pixel-2-xl-t3698148/post74363478

This makes me smile. Thanks Troy and TeamWin!

Thanks Dees_Troy and Team for getting this started!

Things are looking up, thanks guys!

Awesome to see action with this phone! Thanks!!

You da man

sharkie405 said:
fastboot boot /path/to/twrp.img reboots into TWRP, but it never goes past the teamwin splash screen. I am able to reboot the phone normally after that, so no biggie.
I don't have time now to mess with figuring out how to get you logs, but I'll do that later this evening. Just wanted to give you a quick "what happened when I tried it."
And THANK YOU for working on this for us so quickly!
Click to expand...
Click to collapse
Here are those logs.

Nice! Great to see the progress

Thanks for the progress guys. Has anyone tried flashing root from TWRP yet? I wonder if this process would work, if we used this modded TWRP... https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-systemlessly-root-pixel-xl-t3660324

sharkie405 said:
Here are those logs.
Click to expand...
Click to collapse
Did you try unlocking critical?

cwalker0906 said:
Did you try unlocking critical?
Click to expand...
Click to collapse
Yes, I've already unlocked critical.
Sent from my Pixel 2 XL using XDA Labs

Great to see...this is the start!

I unlocked the bootloader without critical and was able to bootloader into twrp. No just figuring out a way to get root.

bggold said:
I unlocked the bootloader without critical and was able to bootloader into twrp. No just figuring out a way to get root.
Click to expand...
Click to collapse
From here we should be able to push ADB shell comands to edit build.prop right?

I just fastboot booted your .img. All functioning as expected except for the issues that you indicated.
Rebooted back to system without any issues.
Thank You Great Job!

chazall1 said:
I just fastboot booted your .img. All functioning as expected except for the issues that you indicated.
Rebooted back to system without any issues.
Thank You Great Job!
Click to expand...
Click to collapse
Have you unlocked critical?
Sent from my Pixel 2 XL using XDA Labs