Develop Bugs

Unable to mount partitions after flashing TWRP on Nexus 7 (2013, WiFi, flo)

I just bought this device a week and I haven't even rooted I wanted to install Cyanogenmode and follow through the instructions and flashed TWRP through fastboot commands from Windows7 using Minimal ADB and Fastboot [8-28-15].
I got the TWRP recovery but I am not sure what have I done wrong, when I am in the TWRP recovery, it does not show any partitions so I am unable to install any ROM on it.
I have also tried to use this thread: http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562 when I flash the given recovery from fastboot commands from this thread, the recovery get stuck with bootloop. So then I restored it back to the original TWRP 2.8.7.0.
So at this point now I can only access bootloader and the recovery which does not show partitions.
At this point Is it possible for me to go back to the stock ROM somehow? Please advice. Otherwise I might be able to return it because I have only bought it few days ago.
SOLVED: To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/androi...s/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/dev...o_20150630.img
This allowed TWRP to work.
Thanks to Batfink33 and lynnux

You can follow this guide to flash the newest factory image: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/. You should just download the latest factory image from: https://developers.google.com/android/nexus/images?hl=en the one in the guide is outdated.

Join the club, I did the same thing you did with the same results(even flashing the multirom twrp after flashing the regular one, and getting the recovery bootloop). I happened to find the same instructions theminikiller posted above after pulling my hair out trying to figure out what went wrong.
This post http://forum.xda-developers.com/showpost.php?p=62275723&postcount=558 explains what's going on. If you do the above and then flash the multirom twrp it should work fine, it did for me. I also reformatted system in adb after erasing everything, not sure if that was necessary or not.

lynnux said:
Join the club, I did the same thing you did with the same results(even flashing the multirom twrp after flashing the regular one, and getting the recovery bootloop). I happened to find the same instructions theminikiller posted above after pulling my hair out trying to figure out what went wrong.
This post http://forum.xda-developers.com/showpost.php?p=62275723&postcount=558 explains what's going on. If you do the above and then flash the multirom twrp it should work fine, it did for me. I also reformatted system in adb after erasing everything, not sure if that was necessary or not.
Click to expand...
Click to collapse
Did the multirom TWRP work for you? I get a bootloop in TWRP when I flash that multirom TWRP posted.

Batfink33 said:
Did the multirom TWRP work for you? I get a bootloop in TWRP when I flash that multirom TWRP posted.
Click to expand...
Click to collapse
It worked for me, but only after erasing everything via adb and reflashing all the stock images. I got the bootloop when I flashed the regular twrp first, then the multirom twrp. Also, I'm using the most recent multirom twrp from June (I believe).

lynnux said:
It worked for me, but only after erasing everything via adb and reflashing all the stock images. I got the bootloop when I flashed the regular twrp first, then the multirom twrp. Also, I'm using the most recent multirom twrp from June (I believe).
Click to expand...
Click to collapse
Yay, it works for me now. I had to install the stock ROM using adb then flash the multirom TWRP. Thanks!

Batfink33 said:
Yay, it works for me now. I had to install the stock ROM using adb then flash the multirom TWRP. Thanks!
Click to expand...
Click to collapse
Thanks for your replies here. Could you please give me the link to the multiroom Recovery that had worked for you? Also did you installed Cynageon mode after getting the mutliroom TWRP working? Please advice

a4abbas said:
Thanks for your replies here. Could you please give me the link to the multiroom Recovery that had worked for you? Also did you installed Cynageon mode after getting the mutliroom TWRP working? Please advice
Click to expand...
Click to collapse
To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/android/nexus/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/de...//multirom/flo/TWRP_multirom_flo_20150630.img
This allowed TWRP to work.

Batfink33 said:
To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/android/nexus/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/de...//multirom/flo/TWRP_multirom_flo_20150630.img
This allowed TWRP to work.
Click to expand...
Click to collapse
Is it required to enable Developer options at some point of flashing it successfully? I am in China and here the google is blocked i bought this tablet and I can not get through the first screen that ask me to connect the wifi (no option to skip it unless i connect to wifi) then after loading it gets error message that it is failed to connect to internet. So just understand that I can not goto the device options right now. So is it possible to flash cynagonmode rom without enabling developer option. Please advice

a4abbas said:
Is it required to enable Developer options at some point of flashing it successfully? I am in China and here the google is blocked i bought this tablet and I can not get through the first screen that ask me to connect the wifi (no option to skip it unless i connect to wifi) then after loading it gets error message that it is failed to connect to internet. So just understand that I can not goto the device options right now. So is it possible to flash cynagonmode rom without enabling developer option. Please advice
Click to expand...
Click to collapse
No, it's not required. Just turn off your device. Then to boot into the bootloader hold volume down + power button until it's done booting. From there you can follow other guides to unlock the bootloader and installing custom recovery and Rom's.

theminikiller said:
No, it's not required. Just turn off your device. Then to boot into the bootloader hold volume down + power button until it's done booting. From there you can follow other guides to unlock the bootloader and installing custom recovery and Rom's.
Click to expand...
Click to collapse
I have tried to do it. But the device is not being recognized with the ADB tools on my PC. Any ideas? Could it be because of the USB debugging option?

a4abbas said:
I have tried to do it. But the device is not being recognized with the ADB tools on my PC. Any ideas? Could it be because of the USB debugging option?
Click to expand...
Click to collapse
When you are in the bootloader it doesn't matter if you have USB debugging enabled or not. It could be a problem with your driver's.

theminikiller said:
When you are in the bootloader it doesn't matter if you have USB debugging enabled or not. It could be a problem with your driver's.
Click to expand...
Click to collapse
You must be right, it make sense.

Stuck at fastboot! (need help)!

Hi. Im stucked at fastboot... I have no OS and no TWRP.... on oneplus 2 it happen to me and I used a tool called FIRST AID, but for op3 it does not exist. I tried flash twrp by fastboot, it says success but when I boot to fastboot, I get a black screen.... Please help me

Im sorry to say this. But r.i.p oneplus 3
Sent from my ONEPLUS A3000 using XDA-Developers mobile app

please help me!

infamouzwt said:
Im sorry to say this. But r.i.p oneplus 3
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Click to expand...
Click to collapse
thats not true.....

Which TWRP are you flashing and what rom were you on before the speed bump

NZnewbie said:
Which TWRP are you flashing and what rom were you on before the speed bump
Click to expand...
Click to collapse
Hi. My rom before was freedom OS.... I tried twrp 3.0.2.0 and twrp 3.0.2.1 and stock recovery....

tuga49 said:
Hi. My rom before was freedom OS.... I tried twrp 3.0.2.0 and twrp 3.0.2.1 and stock recovery....
Click to expand...
Click to collapse
Try the modified 3.0.2-19 twrp. Search XDA for it. It's all over.

Don't panic, i had the same issue yesterday. but try to search for the 3.0.2.19 verison of TWRP and flash it with fastboot.

Flash His recovery From here Via CMD OR anytoolkit
Than Move a flashable 3.2.4 on Your Mobile Via Usb (Going Recoverymode first)
Than Install 3.2.4 reboot my be its work...

Nilshalok said:
Flash His recovery From here Via CMD OR anytoolkit
Than Move a flashable 3.2.4 on Your Mobile Via Usb (Going Recoverymode first)
Than Install 3.2.4 reboot my be its work...
Click to expand...
Click to collapse
hi. it says success flashed on cmd, but when I boot to recovery, it just show me a black screen!

abuddlah said:
Don't panic, i had the same issue yesterday. but try to search for the 3.0.2.19 verison of TWRP and flash it with fastboot.
Click to expand...
Click to collapse
Hi. I don't find any twrp with version 3.0.2.19... please help me.

Unbrick tool
Just look here it did help me in nearly the same situation:
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700

Hi! thank you all! I solved the problem flashing twrp with version 3.0.2.19! thank you all!

tuga49 said:
hi. it says success flashed on cmd, but when I boot to recovery, it just show me a black screen!
Click to expand...
Click to collapse
are you Trying 3.5.2???

Having a similar issue. I'm on 3.5.2 unlocked bootloader, no root, stock recovery. Everytime I try to flash TWRP, it appears to succeed, but will never boot to TWRP. Boots fastboot and OOS just fine, but no recovery available. I then tried to flash stock recovery, but same issue appears. I then was able to use skipsoft toolkit to get stock recovery, but only by relocking then unlocking the bootloader. Everytime I tried to simply flash a recovery it appears to succeed, but will not boot to recovery. So skipsoft was able to fix the no recovery problem, but I am still unable to flash TWRP

Mansquatch312 said:
Having a similar issue. I'm on 3.5.2 unlocked bootloader, no root, stock recovery. Everytime I try to flash TWRP, it appears to succeed, but will never boot to TWRP. Boots fastboot and OOS just fine, but no recovery available. I then tried to flash stock recovery, but same issue appears. I then was able to use skipsoft toolkit to get stock recovery, but only by relocking then unlocking the bootloader. Everytime I tried to simply flash a recovery it appears to succeed, but will not boot to recovery. So skipsoft was able to fix the no recovery problem, but I am still unable to flash TWRP
Click to expand...
Click to collapse
Here is the issue. 3.5.2 has a different firmware than previous OOS versions. You will need a specific 3.5.2 modified TWRP. The link is here:
http://forum.xda-developers.com/attachment.php?attachmentid=3875375&d=1473889816
You can see that this is discussed on the oneplus forums here: https://forums.oneplus.net/threads/...ity-update-with-working-twrp-recovery.465353/
I ran into this same problem myself, and realized that this was the issue. You should be very careful because it could cause you some grief. Whatever you do don't lock your bootloader if you end up with a nonfunctional and non functional recovery.

I have the same issue i can flash all the recovery images but non of them worked i tried 1000 different methods and nothing works.. Getting a bit desperate is someone please able to help me got my new phone already broke it kinda..

Saqrez said:
I have the same issue i can flash all the recovery images but non of them worked i tried 1000 different methods and nothing works.. Getting a bit desperate is someone please able to help me got my new phone already broke it kinda..
Click to expand...
Click to collapse
I suggest you to refer to the post of @gmarondel :
gmarondel said:
Just look here it did help me in nearly the same situation:
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Click to expand...
Click to collapse
Follow this guide and everything will be ok.

I know u fixed the problem but i think this is a general guide to fix your phone if you have this type of issue after flashing OOS 3.5.6 based roms!
i had the same issue yesterday with freedom os 1.7 (based on OOS 3.5.6) and OOS 3.5.6, here is how i fixed my phone:
- download http://forum.xda-developers.com/attachment.php?attachmentid=3875375&d=1473889816
-unzip it and put it on the desktop
-put your phone in fastboot (make sure you have unloked bootloader and installed all the drivers and adb on your pc)
-press shift and right mouse click on the desktop and hit open a new prompt window here
-write "fastboot boot twrp-3.0.2-19-oneplus3.img" and press enter, your phone should reboot in recovery (keep the prompt open)
-wipe dalvik/system/data/cache/internal storage go back and do format data
-reboot in bootloader(fastboot)
-write in the prompt "fastboot flash recovery twrp-3.0.2-19-oneplus3.img"
-unplug your phone and turn it off switching in fastboot with the volume buttons
-when it's powered off press power+volume down and chose recovery
-now you should boot and flash any rom in recovery (i suggest you to not try to flash any OOS 3.5.6 based roms)
i went back to OOS 3.2.6 but any other custom rom lshould be fine!

Vexo_ said:
I know u fixed the problem but i think this is a general guide to fix your phone if you have this type of issue after flashing OOS 3.5.6 based roms!
i had the same issue yesterday with freedom os 1.7 (based on OOS 3.5.6) and OOS 3.5.6, here is how i fixed my phone:
- download http://forum.xda-developers.com/attachment.php?attachmentid=3875375&d=1473889816
-unzip it and put it on the desktop
-put your phone in fastboot (make sure you have unloked bootloader and installed all the drivers and adb on your pc)
-press shift and right mouse click on the desktop and hit open a new prompt window here
-write "fastboot boot twrp-3.0.2-19-oneplus3.img" and press enter, your phone should reboot in recovery (keep the prompt open)
-wipe dalvik/system/data/cache/internal storage go back and do format data
-reboot in bootloader(fastboot)
-write in the prompt "fastboot flash recovery twrp-3.0.2-19-oneplus3.img"
-unplug your phone and turn it off switching in fastboot with the volume buttons
-when it's powered off press power+volume down and chose recovery
-now you should boot and flash any rom in recovery (i suggest you to not try to flash any OOS 3.5.6 based roms)
i went back to OOS 3.2.6 but any other custom rom lshould be fine!
Click to expand...
Click to collapse
I really appreciate your help but i think i fixed it. Today suddenly my phone went into recovery without doing anything except for 1000 methods. I am so happy that people like you are willing to help people.

Stuck rooting

Hi all, so I have Verizon's Pixel XL. I have unlocked it successfully and had rooted. I asked on the forums about upgrading the OTA update and was told it was fine. After doing so, I noticed my SuperSU was gone (although I might have lost it earlier and not noticed). So after trying to get it back and keeping getting stuck, I bit the bullet and ADB sideloaded the factory image from google (NDE63X) and got it able to boot up. Yay.
So then I ran the 'adb reboot bootloader' command, then verified my device was connected with 'fastboot devices' and finally I ran 'fastboot boot boot-to-root.img'. And here I am, stuck on the splash screen again.
So I looked around and saw some mentions of people that had used older versions of Chainfire's SuperSU. I tried the newer one (2.78 SR3) and the same thing happened. I do see that there is a SR5, but I also see Chainfire's comment "Do not use the SuperSU ZIP on work-in-progress TWRP releases for Pixel, it will not work - use the model specific links above instead.
I can get it to run just fine without using chainfire's supersu...but then I don't have the supersu app or any real gains from having rooted.
So, I feel like I must be doing something wrong. Any suggestions?

@smokeydriver,
You probably should update your Android SDK package. This problem can also be caused by an obsolete fastboot.

cam30era said:
@smokeydriver,
You probably should update your Android SDK package. This problem can also be caused by an obsolete fastboot.
Click to expand...
Click to collapse
I can give it a shot, but I only installed minimal adb yesterday on my new laptop. Thanks!

smokeydriver said:
I can give it a shot, but I only installed minimal adb yesterday on my new laptop. Thanks!
Click to expand...
Click to collapse
I understand. Here's the thing: I don't know if minimal has up to date ADB and fastboot for Android 7.1.1.

cam30era said:
I understand. Here's the thing: I don't know if minimal has up to date ADB and fastboot for Android 7.1.1.
Click to expand...
Click to collapse
The OTA update I took only got me to a new version of 7.1, not 7.1.1 (from NDE63P to NDE63X). It still shows an available update to 7.1.1 which I have *not* done.

Try using the Unified Toolkit. It saved me from having a bootloop disaster when I tried upgrading from 7.1.1 due to poor instruction availability around the web. It should fix whatever problem you are having, even if that means flashing the factory image first again.

Nitemare3219 said:
Try using the Unified Toolkit. It saved me from having a bootloop disaster when I tried upgrading from 7.1.1 due to poor instruction availability around the web. It should fix whatever problem you are having, even if that means flashing the factory image first again.
Click to expand...
Click to collapse
I've tried, but keep getting an error 21 code that it can't install...I tried this with SR5 and SR2.

How I Rooted
Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.
Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)
AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.
Flash TWRP, then SuperSU.
Reboot into OS, confirm root, give it 5 minutes.
Reboot back to Recovery and flash Kernel if desired.
Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb twrp.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.

FreeSoftwareServers said:
Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.
Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)
AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.
Flash TWRP, then SuperSU.
Reboot into OS, confirm root, give it 5 minutes.
Reboot back to Recovery and flash Kernel if desired.
Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb boot.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.
Click to expand...
Click to collapse
Ok, I must be doing something wrong on a very basic level. It gave me error 21 (signature verification error) when trying to use the unified android tookit to install 7.1. Anyways, I'll just move on and skip that step and see what happens.

Flashing SuperSU SR5 works just fine with TWRP RC1. All you have to do is delete the file you're told to before flashing.
Dees_Troy said:
How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.
Click to expand...
Click to collapse

FreeSoftwareServers said:
Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.
Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)
AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.
Flash TWRP, then SuperSU.
Reboot into OS, confirm root, give it 5 minutes.
Reboot back to Recovery and flash Kernel if desired.
Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb twrp.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.
Click to expand...
Click to collapse
I transferred those 2 files to my download folder on my phone, ran the twrp.img script, and then when I go in...the file names are not normal. Everything is random letters and numbers. Again, I feel like I'm making some stupid basic mistake that I don't understand (and I've rooted plenty of phones).

spotmark said:
Flashing SuperSU SR5 works just fine with TWRP RC1. All you have to do is delete the file you're told to before flashing.
Click to expand...
Click to collapse
So I go in TWRP to advanced, file manager, and I don't see the names of those files. Are they buried in a folder?

smokeydriver said:
So I go in TWRP to advanced, file manager, and I don't see the names of those files. Are they buried in a folder?
Click to expand...
Click to collapse
You have TWRP RC1 installed?

spotmark said:
You have TWRP RC1 installed?
Click to expand...
Click to collapse
Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.

smokeydriver said:
Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.
Click to expand...
Click to collapse
Ah, I see. I misunderstood. I thought you were just under the impression that you couldn't flash SU with RC1. My apologies.

Ok, so can someone tell me why I am getting stuck with 1 thing. I go to my stock recovery and into ADB sideload. When I tell it the file, it keeps failing to verify whole-file signature. What is wrong with this one step?
Or alternatively...when I'm in TWRP Alpha 2- why are all the files within the sdcard random letters and numbers?

smokeydriver said:
Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.
Click to expand...
Click to collapse
Twrp is not decrypting you're data. Try rebooting twrp from fastboot a second time.

toknitup420 said:
Twrp is not decrypting you're data. Try rebooting twrp from fastboot a second time.
Click to expand...
Click to collapse
Son-of-a B#[email protected]#$. It asks me to 'decrypt data' by entering a password. I had hit cancel. What's the password??

smokeydriver said:
Son-of-a B#[email protected]#$. It asks me to 'decrypt data' by entering a password. I had hit cancel. What's the password??
Click to expand...
Click to collapse
Never mind...it's my 4 digit password that's used when my finger unlock doesn't work. Ugh- I knew it was something simple and dumb I was doing!

smokeydriver said:
Ok, so can someone tell me why I am getting stuck with 1 thing. I go to my stock recovery and into ADB sideload. When I tell it the file, it keeps failing to verify whole-file signature. What is wrong with this one step?
Or alternatively...when I'm in TWRP Alpha 2- why are all the files within the sdcard random letters and numbers?
Click to expand...
Click to collapse
Can I ask you how you fixed this? I'm having the same issue and this post popped up on Google.

TWRP stuck on splash screen for a miute then reboots back to the TWRP splash screen

No matter how many resets I just can't boot into my recovery or the OS. If I try to reboot the system all that happens is the TWRP splash screen pops up, hangs there for a while, reboots to the splash screen again and repeats. Is this a brick? The most I can do is get into fastboot mode. Please, any advice would be very much appreciated. I feel like a total dipstick. The ROM I'm on is Resurrection Remix official N and the TWRP version is 3.1.1-0. This combo was never an issue before.

showofdeth said:
No matter how many resets I just can't boot into my recovery or the OS. If I try to reboot the system all that happens is the TWRP splash screen pops up, hangs there for a while, reboots to the splash screen again and repeats. Is this a brick? The most I can do is get into fastboot mode. Please, any advice would be very much appreciated. I feel like a total dipstick. The ROM I'm on is Resurrection Remix official N and the TWRP version is 3.1.1-0. This combo was never an issue before.
Click to expand...
Click to collapse
Use the unbrick guide method 2. Make sure you follow ALL steps otherwise it will not work..
Feel free to ask any questions!

First, go in FastBoot mode & reflash recovery from PC.

null0seven said:
First, go in FastBoot mode & reflash recovery from PC.
Click to expand...
Click to collapse
Tried that using different TWRP versions but it didn't work. My issue still persisted.

Puddi_Puddin said:
Use the unbrick guide method 2. Make sure you follow ALL steps otherwise it will not work..
Feel free to ask any questions!
Click to expand...
Click to collapse
Thanks but that that seemed a bit daunting so after MUCH searching I found a thread with a very simple fix. In fastboot type the command "fastboot format cache" and "fastboot format user data". I lost all my stuff but I'm up and running again.
However, I have a new issue. "system" is taking up 29gb of space. What's that about?

showofdeth said:
Thanks but that that seemed a bit daunting so after MUCH searching I found a thread with a very simple fix. In fastboot type the command "fastboot format cache" and "fastboot format user data". I lost all my data but I'm up and running again.
However, I have a new issue. "system" is taking up 29gb of space. What's that about?
Click to expand...
Click to collapse
Try the latest OOS 4.2.5.. It had some fixes

Puddi_Puddin said:
Try the latest OOS 4.2.5.. It had some fixes
Click to expand...
Click to collapse
I like OOS and all but I like the customisation of RR more. Cheers though.

You did even better. Now you have a Clean phone, because you wipe it all.
It's from your rom. I'm on Oos 4.1.5. Look at mine.

null0seven said:
You did even better. Now you have a Clean phone, because you wipe it all.
It's from your rom. I'm on Oos 4.1.5. Look at mine.
Click to expand...
Click to collapse
Can you install oos through TWRP? Maybe as recommended it may fix my storage issue.

How else ?
Never did Fastboot sideload.
I instal any rom ONLY in TWRP.

showofdeth said:
No matter how many resets I just can't boot into my recovery or the OS. If I try to reboot the system all that happens is the TWRP splash screen pops up, hangs there for a while, reboots to the splash screen again and repeats. Is this a brick? The most I can do is get into fastboot mode. Please, any advice would be very much appreciated. I feel like a total dipstick. The ROM I'm on is Resurrection Remix official N and the TWRP version is 3.1.1-0. This combo was never an issue before.
Click to expand...
Click to collapse
showofdeth said:
Tried that using different TWRP versions but it didn't work. My issue still persisted.
Click to expand...
Click to collapse
At this point I'm sure it's a firmware related issue.
Download and install latest one here: https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
Stable or Open Beta, doesn't matter.
Then... what TWRP have you tried? For custom roms is highly recommended the blu_spark variant.
Because the stock TWRP is good only for OOS-based firmware, with other configurations it may not boot up at all.
showofdeth said:
Thanks but that that seemed a bit daunting so after MUCH searching I found a thread with a very simple fix. In fastboot type the command "fastboot format cache" and "fastboot format user data". I lost all my stuff but I'm up and running again.
However, I have a new issue. "system" is taking up 29gb of space. What's that about?
Click to expand...
Click to collapse
What have you done? ?
Two theories:
1) You've done encryption via custom rom.
2) After formatting /data via fastboot commands, you've not installed and booted up once latest OOS rom.
Until doing that, device will read 25 GB of free space, both in recovery and system.
I don't know the reason of that trouble.
So you have to:
1) Install latest OOS firmware (via TWRP / adb sideload);
2) Bootup once the system: be sure to choose a pattern required at bootup, for the rest skip wizard as fast as possible;
3) Install latest TWRP blu_spark via fastboot command;
4) From recovery, wipe everything and flash Resurrection Remix.
Tell me if you solve ?

Simone98RC said:
At this point I'm sure it's a firmware related issue.
Download and install latest one here: https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
Stable or Open Beta, doesn't matter.
Then... what TWRP have you tried? For custom roms is highly recommended the blu_spark variant.
Because the stock TWRP is good only for OOS-based firmware, with other configurations it may not boot up at all.
What have you done?
Two theories:
1) You've done encryption via custom rom.
2) After formatting /data via fastboot commands, you've not installed and booted up once latest OOS rom.
Until doing that, device will read 25 GB of free space, both in recovery and system.
I don't know the reason of that trouble.
So you have to:
1) Install latest OOS firmware (via TWRP / adb sideload);
2) Bootup once the system: be sure to choose a pattern required at bootup, for the rest skip wizard as fast as possible;
3) Install latest TWRP blu_spark via fastboot command;
4) From recovery, wipe everything and flash Resurrection Remix.
Tell me if you solve
Click to expand...
Click to collapse
I've fixed everything. Flashed a OOS based ROM then did a factory wipe in TWRP and then installed a new RR ROM. Panic over. Sorted.

TWRP won't stick, tried everything

Hi, since this morning I'm trying to install TWRP as a recovery, only everytime I reboot while holding the right buttons, it loops, and if I'm not holding, it will just boot normally, I tried several versions of the TWRP, and followed every guide, with no results, even flashing vbmeta.img before flashing twrp.img
Is it my phone ? Has anyone have this problem before? Should I stop trying?
Thank you.

I have this same problem..... I Don't know how to fix it... But, yeah.

Hmm, closing avb via flashing vbmeta should do the trick.
Try:
1. Flash vbmeta with following arguments:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
2. Flash your favourite flavor of recovery
3. Hold volume up while you execute reboot command
4. See if it load to recovery. If it load to recovery, try to reboot to recovery. Your recovery should stick. Flash recovery inside recovery if you unsure.
Or (although I haven't tested it on begonia, I've ran this on whyred)
1. Boot to recovery by executing
Code:
fastboot boot recoveryimage.img
2. Flash your recovery inside the booted recovery.
3. See if your recovery have sticked by rebooting to recovery.
Hope that helps.

Gave up on TWRP. OrangeFox worked for me: https://forum.xda-developers.com/t/...ngefox-recovery-project-r11-0-stable.4004127/

The TWRP mentioned in the PE install docs is working for me:
https://wiki.pixelexperience.org/devices/begonia/install/
https://sourceforge.net/projects/be...twrp-3.5.0_10-UNIFIED_UNOFFICIAL.img/download
This video might help:

hanzn said:
The TWRP mentioned in the PE install docs is working for me:
https://wiki.pixelexperience.org/devices/begonia/install/
https://sourceforge.net/projects/be...twrp-3.5.0_10-UNIFIED_UNOFFICIAL.img/download
This video might help:
Click to expand...
Click to collapse
https://sourceforge.net/projects/be...3.5.1_10-begonia_UNOFFICIAL_1604.img/download
This latest version fixes encryption.
Compass.

Compass Linux said:
https://sourceforge.net/projects/be...3.5.1_10-begonia_UNOFFICIAL_1604.img/download
This latest version fixes encryption.
Compass.
Click to expand...
Click to collapse
Thanks for the info!
I had troubles last time I tried the official TWRP one. The PE-UNIFIED one was working without any issues.
Di you know what the UNIFIED means in this case?

hanzn said:
Thanks for the info!
I had troubles last time I tried the official TWRP one. The PE-UNIFIED one was working without any issues.
Di you know what the UNIFIED means in this case?
Click to expand...
Click to collapse
I previously thought that encryption meant system too, which doesn't seem to be the case. The encryption problem is with TWRP, so if you have to flash files located in internal storage and it's encrypted, you won't be able to access them with recovery. Once booted into system things are normal.
You can workaround encryption easily though. Either use a SDCARD or a USB drive (OTG). Best of all, use the latest TWRP.
If I'm not mistaken "UNIFIED" means compatibility with both non-CFW ROMS and MIUI official ROM.
It's good practice to check before each PE+ 11 update if there is a TWRP update too.
Compass.

Thanks for pointing out to UNIFIED one.
In my case both OFFICIAL and UNOFFICIAL didn't work.
Only UNIFIED UNOFFICIAL works.
https://sourceforge.net/projects/begonia-oss/