Develop Bugs

ZF2 bootloader stuck

Hi
I think I tried installing the dual twrp clockwork bootloader a long time ago and it never worked. I still have the standard bootloader but when I select recovery it just restarts to the normal boot option.
So basically its stuck, I can't use adb to put the latest factory rom on. I can use adb to reboot but once again I'm presented with the normal boot option. I can't do a factory restore either.
I'm looking for a way to force flash a fresh bootloader or repair somehow.

First you need unlocked bootloader for installing twrp.
And if you don't want unlock bootloader,you must install stock recovery

Leftrand said:
First you need unlocked bootloader for installing twrp.
And if you don't want unlock bootloader,you must install stock recovery
Click to expand...
Click to collapse
Is there a method to just flash the stock recovery?

rsgametech said:
Is there a method to just flash the stock recovery?
Click to expand...
Click to collapse
Download stock recovery img according your version HERE and flash with terminal emulator.

What are the commands I must use?

This worked like a charm
Rashr - Flash Tool worked like a charm, updated repo, pointed to the correct recovery.img and rebooted and working!
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools

After flashing TWRP, will not boot system

Good morning,
I'm sure it's something I'm missing. I had my tablet unlocked and running fine with TWRP. I went to Omni then to Preview 2. All was well.
Last night I decided to try SuperSU 2.72. I factory reset my Pixel C by installing the latest firmware. I then used fastboot to flash TWRP. It goes into TWRP fine but now it will not boot system any longer. It goes directly into TWRP when I have it boot system. Is this an encryption problem. I've tried both TWRP versions and same behavior.
Any idea what I'm doing wrong?
Thanks!

if you have 3.0.2 i think there was a problem with early build causing this. there was a link posted for the new one that supposedly fixed it. or just use the 3.0.0 build.

Mike02z said:
Good morning,
I'm sure it's something I'm missing. I had my tablet unlocked and running fine with TWRP. I went to Omni then to Preview 2. All was well.
Last night I decided to try SuperSU 2.72. I factory reset my Pixel C by installing the latest firmware. I then used fastboot to flash TWRP. It goes into TWRP fine but now it will not boot system any longer. It goes directly into TWRP when I have it boot system. Is this an encryption problem. I've tried both TWRP versions and same behavior.
Any idea what I'm doing wrong?
Thanks!
Click to expand...
Click to collapse
It seems some people have problems installing the NYCHitman1 TWRP version.
Most of them complaining because of boot problems.
To fix it:
Pls use xceed TWRP 3.0.0-0 version: http://forum.xda-developers.com/pix...official-twrp-2-8-7-0-pixel-c-dragon-t3288243
Or use my repacked TWRP 3.0.2-0 version : TWRP_dragon_3.0.2.0.img
Pls install TWRP via fastboot and boot directly into TWRP.
Install stock kernel (boot.img) via "fastboot" or use the TWRP flashable version from here: Update.ZIP_Nexus_Ryu_MXC89F-kernel_dragon.zip
Install SuperSU.zip 2.72 directly afterwards in TWRP - no reboot in between.
Download: http://forum.xda-developers.com/pixel-c/development/twrp-flashable-monthly-update-zip-pixel-t3375591
Good luck !

followmsi said:
It seems some people have problems installing the NYCHitman1 TWRP version.
Most of them complaining because of boot problems.
To fix it:
Pls use xceed TWRP 3.0.0-0 version: http://forum.xda-developers.com/pix...official-twrp-2-8-7-0-pixel-c-dragon-t3288243
Or use my repacked TWRP 3.0.2-0 version : TWRP_dragon_3.0.2.0.img
Pls install TWRP via fastboot and boot directly into TWRP.
Install stock kernel (boot.img) via "fastboot" or use the TWRP flashable version from here: Update.ZIP_Nexus_Ryu_MXC89F-kernel_dragon.zip
Install SuperSU.zip 2.72 directly afterwards in TWRP - no reboot in between.
Download: http://forum.xda-developers.com/pixel-c/development/twrp-flashable-monthly-update-zip-pixel-t3375591
Good luck !
Click to expand...
Click to collapse
Thanks guys! I did go back to 3.0.0-0 and it now boots into system. I'll also try your repackaged version of 3.0.2-0. I'm on my work PC but I don't see a link to your version. Is my work PC just hiding it or can I find it somewhere else? Thanks again!

Mike02z said:
Thanks guys! I did go back to 3.0.0-0 and it now boots into system. I'll also try your repackaged version of 3.0.2-0. I'm on my work PC but I don't see a link to your version. Is my work PC just hiding it or can I find it somewhere else? Thanks again!
Click to expand...
Click to collapse
Here is the direct link for TWRP_dragon_3.0.2.0.img:
https://onedrive.live.com/?authkey=...&id=479EB75F5DD9DA59!131&cid=479EB75F5DD9DA59
Here is the complete folder: (TWRP flashable stock kernel)
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Cheers

Well in case of "recovery bootloop" start your device in bootloader mode and type "fastboot reboot" in command shell. That works mostly. No need to flash another recovery.

redukt said:
Well in case of "recovery bootloop" start your device in bootloader mode and type "fastboot reboot" in command shell. That works mostly. No need to flash another recovery.
Click to expand...
Click to collapse
And connect everytime with PC to do a manual reboot via fastboot .. seems a little bit too much for a simple reboot. At least for me
A proper TWRP with proper vboot will boot always correctly, like the one from xceed.
Did you ever had to do a manual reboot on his version ?
Should be fixed at the root cause .. Hope you agree ?
Cheers

I think there´s a little missunderstanding
The fastboot command helps you to get out of "recovery bootloop". After this you can reboot your device how offen you want without issues.
And yes with all existing TWRP versions I had some reboot hickups and have solved it with the fastboot method...

redukt said:
I think there´s a little missunderstanding
The fastboot command helps you to get out of "recovery bootloop". After this you can reboot your device how offen you want without issues.
And yes with all existing TWRP versions I had some reboot hickups and have solved it with the fastboot method...
Click to expand...
Click to collapse
Interesting .. I did not have any reboot issues with xceed TWRP versions .. I had to use the fix fastboot option once, but this is another topic.
But thanks for your information ...

followmsi said:
It seems some people have problems installing the NYCHitman1 TWRP version.
Most of them complaining because of boot problems.
To fix it:
Pls use xceed TWRP 3.0.0-0 version: http://forum.xda-developers.com/pix...official-twrp-2-8-7-0-pixel-c-dragon-t3288243
Or use my repacked TWRP 3.0.2-0 version : TWRP_dragon_3.0.2.0.img
Pls install TWRP via fastboot and boot directly into TWRP.
Install stock kernel (boot.img) via "fastboot" or use the TWRP flashable version from here: Update.ZIP_Nexus_Ryu_MXC89F-kernel_dragon.zip
Install SuperSU.zip 2.72 directly afterwards in TWRP - no reboot in between.
Download: http://forum.xda-developers.com/pixel-c/development/twrp-flashable-monthly-update-zip-pixel-t3375591
Good luck !
Click to expand...
Click to collapse
Hi.. after installing TWRP my phone nokia 3 TA-1020 I only booted to system once, when I restarted it later it does not boot the system but boots to TWRP. what can I do so that it will be rebooting to system instead of TWRP your help will be highly appreciated, thanks in advance.

Annan Denis said:
Hi.. after installing TWRP my phone nokia 3 TA-1020 I only booted to system once, when I restarted it later it does not boot the system but boots to TWRP. what can I do so that it will be rebooting to system instead of TWRP your help will be highly appreciated, thanks in advance.
Click to expand...
Click to collapse
Wrong device thread .. anyway just restore "stock" ROM/recovery to make it working again.
Good luck !

I can't reflash stock recovery

Hi, yestarday I flashed CM 14 with TWRP to try it, and today I have tried to return to stock rom & recovery but I can't do it. At the beginning I have tried to flash stock recovery that I have downloaded from op.net with fastboot and I couldn't do it and after I have tried to do the same process but this time flash it with TWRP and also this time I couldn't able to fix it. In fine I have installed the stock ROM via TWRP and I managed to install it but now the problem is that I still can not install the stock recovery and accordingly I can't install op3 update.
An another problem is that I have tried to re-lock OEM from fastboot and when I try to turn on the phone, is asks me a pin to enable it and I don't know that pin because I haven't set no one

ICosmin said:
Hi, yestarday I flashed CM 14 with TWRP to try it, and today I have tried to return to stock rom & recovery but I can't do it. At the beginning I have tried to flash stock recovery that I have downloaded from op.net with fastboot and I couldn't do it and after I have tried to do the same process but this time flash it with TWRP and also this time I couldn't able to fix it. In fine I have installed the stock ROM via TWRP and I managed to install it but now the problem is that I still can not install the stock recovery and accordingly I can't install op3 update.
An another problem is that I have tried to re-lock OEM from fastboot and when I try to turn on the phone, is asks me a pin to enable it and I don't know that pin because I haven't set no one
Click to expand...
Click to collapse
Need to download custom twrp http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Then use flashify to flash recovery

cbendixe84 said:
Need to download custom twrp http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Then use flashify to flash recovery
Click to expand...
Click to collapse
i have already flashed twrp 3.0.2.2 but now I would flash stock recovery but when I try to install it and turn into it op3 show me only op logo and after a few seconds the screen become black.

your phone is bricked I'm assuming. there is a thread for that. that should work for you!

sahed01 said:
your phone is bricked I'm assuming. there is a thread for that. that should work for you!
Click to expand...
Click to collapse
No it isn't. Because I managed to put stock ROM into it via adb with push command and after I have installed it from twrp that works. My only problem is that i can't flash stock recovery.

i have the same issue. Tried many times but i'm getting a black screen after one plus logo for both stck recovery and unmodified twrp. only moidified twrp is working. please let me know if u find a way to resolve this.
thanks in advance

varmasagiraju said:
i have the same issue. Tried many times but i'm getting a black screen after one plus logo for both stck recovery and unmodified twrp. only moidified twrp is working. please let me know if u find a way to resolve this.
thanks in advance
Click to expand...
Click to collapse
I downloaded the stock rom and inside it(stock rom.zip) i put the stock recovery after I reflashed the stock rom via adb from twrp and in fine I locked bootloader.

ICosmin said:
I downloaded the stock rom and inside it(stock rom.zip) i put the stock recovery after I reflashed the stock rom via adb from twrp and in fine I locked bootloader.
Click to expand...
Click to collapse
you can reboot in to stock recovery without any issues?? I think I should give it a try. And you are saying the bootloader is locked again ?

varmasagiraju said:
you can reboot in to stock recovery without any issues?? I think I should give it a try. And you are saying the bootloader is locked again ?
Click to expand...
Click to collapse
Yes, I manage to reboot into stock recovery and i relocked bootloader(you needn't relock bootloader if you do not want)

ICosmin said:
Yes, I manage to reboot into stock recovery and i relocked bootloader(you needn't relock bootloader if you do not want)
Click to expand...
Click to collapse
Great. Can I place the file in beta8 rom .zip file and flash it using adb ??

If this procedure doesn't you can download an older version of oxygen os and update it via ota. At the first attempt when you will try it will give you an error and at the second attempt It will download all the ROM again and it will reflash by itself

varmasagiraju said:
Great. Can I place the file in beta8 rom .zip file and flash it using adb ??
Click to expand...
Click to collapse
I suggest you to try at the beginning with the beta 7 because if that procedure not work for you, you can't downgrade to beta 7.

ICosmin said:
I suggest you to try at the beginning with the beta 7 because if that procedure not work for you, you can't downgrade to beta 7.
Click to expand...
Click to collapse
Thank you.
Will let you know if it worked.

I had that problem.
Solution as follows, worked everytime for me: (I have not tried this method with the newest beta 8)
1. Flash OOS 3.2.6 firmware in twrp.
2. Reboot to fastboot and flash official oxygen os recovery downloaded from the OnePlus website. (This is still the old version for some reason, thus why it won't work)
3. Side load community build with oxygen os recovery, this will flash the new firmware back and update the recovery to be community build compatible.
4. Before rebooting erase everything (factory restore)
5. Reboot to OOS, finish setting up.
6. Turn on advance reboot in developer settings.
7. Reboot to recovery via the reboot menu. First time boot into the recovery may take sometime, but it has always worked for me.
8. After everything looks good, go ahead and OEM lock in fastboot, recovery should work as usual this time and format your phone

OP did you find a solution to this?? Im on the same boat as you

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.

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.