I came from cm13 and i suddenly think of returning back to stock lollipop. After a few days, I realize cm13 is a lot better. I downgraded back to kitkat and unlocked the bootloader the way I did before. Before, it was successful. But now, when I flash TWRP and reboot to recovery using flashify, it shows security boot error. I upgraded to stock lollipop and tried it unlocking bootloader there. I flashed TWRP but when I entered TWRP, I cannot reboot back to system. I cannot get out of recovery!! Pleasee help... I want to get cm13 back
ShadowBlade_20 said:
I came from cm13 and i suddenly think of returning back to stock lollipop. After a few days, I realize cm13 is a lot better. I downgraded back to kitkat and unlocked the bootloader the way I did before. Before, it was successful. But now, when I flash TWRP and reboot to recovery using flashify, it shows security boot error. I upgraded to stock lollipop and tried it unlocking bootloader there. I flashed TWRP but when I entered TWRP, I cannot reboot back to system. I cannot get out of recovery!! Pleasee help... I want to get cm13 back
Click to expand...
Click to collapse
you should write this in other section but i want to help you.
maybe try to flash stock kdz again if you still can then check if bootloader method you use is correct but if was not you will brick your phone.
Related
I came from cm13 and i suddenly think of returning back to stock lollipop. After a few days, I realize cm13 is a lot better. I downgraded back to kitkat and unlocked the bootloader the way I did before. Before, it was successful. But now, when I flash TWRP and reboot to recovery using flashify, it shows security boot error. I upgraded to stock lollipop and tried it unlocking bootloader there. I flashed TWRP but when I entered TWRP, I cannot reboot back to system. I cannot get out of recovery!! Pleasee help... I want to get cm13 back
ShadowBlade_20 said:
I came from cm13 and i suddenly think of returning back to stock lollipop. After a few days, I realize cm13 is a lot better. I downgraded back to kitkat and unlocked the bootloader the way I did before. Before, it was successful. But now, when I flash TWRP and reboot to recovery using flashify, it shows security boot error. I upgraded to stock lollipop and tried it unlocking bootloader there. I flashed TWRP but when I entered TWRP, I cannot reboot back to system. I cannot get out of recovery!! Pleasee help... I want to get cm13 back
Click to expand...
Click to collapse
actually i gave a answer for you http://forum.xda-developers.com/showpost.php?p=64674426&postcount=2
u even can flash kdz ? if yes, try it and check if your bootloader unclocking method, file, is correct.
You could brick your phone.
I have a Z5C(E5803) that was originally able to unlock the bootloader and let me flash ROMs, specifically the Cyanogen ROM that CTXz has been working on. I ran out of power and got stuck in some kind of nasty bootloop yesterday that prompted me to re-flash boot.img and TWRP.
After I did these things I left it charging for a few hours and it was able to boot into TWRP where I then restored it to a backup of the basic Xperia pre-loaded ROM.
This all worked fine, thought I could boot into TWRP and just flash the Cyanogen zip again. I can get into TWRP just fine but I attempt to flash Cyanogen I get an "ERROR 7"
I have since done several wipes, gotten into the bootloader settings by entering that code in the dialer and have seen that bootloader unlock = no. I distinctly remember bootloder unlocking being allowed the first time I installed CM on my device, what could have caused this?
I was able to use it with fastboot anyway and install CM13 again, maybe this was a bug?
When I tried using oem unlock command with fastboot it said my device was already rooted even though I had just restored from a backup, and then I just proceeded normally from there.
use CM13 official Recovery to FLASH CM13.
also i don't think so twrp3.0.2 is out there for z5c. are you using any other variants Twrp? (YUGA ? )
hello,
my current situation: i am on oos 2.2.3, not rooted, twrp 3.0.1-0 running.
i want to install a 3.x.x oos, version, i wanted to install 3.1.2 first, cause oneplus site i can install that directly form 2.2.3 (no such info on 3.1.3 and 3.1.4)
when i try to install with twrp, it says "this package is for "Oneplus" devices, this is a "ONE"
i think i am using the wrong twrp version. tried to install the newest (3.0.3-0), but this one doenst work, can not boot into it.
please help
Best is to fastboot flash old OOS 2 recovery
Then, with it, flash the 2.2.3. Reboot. then Flash 3.1.4. with the recovery
First you need to flash official oxygen os recovery for android 5.1 lollipop https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img Now you will be able to boot the phone. Now download and copy oxygen os 3.1.4 to internal memory http://downloads.oneplus.net/devices/oneplus-x/ Reboot into recovery and flash the rom.
Aftrr successful flash of oos3 boot into fastboot and flash latest twrp from twrp website.. This time it should work.
thanks, it work with the costum recovery.
on 3.1.4 i installed a slightly older twrp form sparkfire (3.0.2 i think), rooting and installing xposed worked fine though.
is it important to have the latest twrp?
and another question. at some point in my hours long struggel with updating my opx i softbricked it. i guess my bootloader was locked and i tried to install another recovery. i expected it to be still unlocked from my first rooting months ago. when does the bootloader lock?
dooglrig said:
thanks, it work with the costum recovery.
on 3.1.4 i installed a slightly older twrp form sparkfire (3.0.2 i think), rooting and installing xposed worked fine though.
is it important to have the latest twrp?
and another question. at some point in my hours long struggel with updating my opx i softbricked it. i guess my bootloader was locked and i tried to install another recovery. i expected it to be still unlocked from my first rooting months ago. when does the bootloader lock?
Click to expand...
Click to collapse
It is always recommended to use latest (bugs free)
You can use this one https://dl.twrp.me/onyx/twrp-3.0.3-0-onyx.img latest as of now. And no u didn't brick ur phone. U flashed a new twrp for old bootloader version. Thts y u got stuck with oneplus logo. Its all oneplus things. Its always preferred to use stock recovery for updating bootloader which is safe. Check your bootloader state by giving this cmds "fastboot oem device-info"
cva_kabil said:
It is always recommended to use latest (bugs free)
You can use this one https://dl.twrp.me/onyx/twrp-3.0.3-0-onyx.img latest as of now. And no u didn't brick ur phone. U flashed a new twrp for old bootloader version. Thts y u got stuck with oneplus logo. Its all oneplus things. Its always preferred to use stock recovery for updating bootloader which is safe. Check your bootloader state by giving this cmds "fastboot oem device-info"
Click to expand...
Click to collapse
Hmm isnt that for new BL as well ?
NielDK said:
Hmm isnt that for new BL as well ?
Click to expand...
Click to collapse
Yes it is. OP said that he's on OOS 3.1.3, so already on the new BL.
I really don't know what is left to do, I always end up with a bootloop and have to repair my phone with flashtool. I have tried flashing twrp by adb/fastboot, temporarily booting to twrp, flashing different twrp files after repair.... I always get boot loop. Help please :/
Once I had my phone rooted by oneclickroot support, then I started to get play store crashed constantly. Once I booted to recovery and when try to reboot, got a bootloop. I tried to flash a new rom, so found a stock rom for Z5C and flashed it by twrp. But after a reboot I lost the twrp recovery this time. Then I tried to flash the recovery myself using abd, following the basics; fastboot flash boot boot.img/recovery recovery.img But I again stuck into a bootloop. Repaired again... I thought flashing a custom recovery breaks the phone, so I decided to just boot the recovery and install supersu. but again a bootloop in the end.
Is your bootloader already unlocked?
Gewiz said:
Is your bootloader already unlocked?
Click to expand...
Click to collapse
yes sir, already.
flash complete stock, no modifications.
confirm if it loads to usermode
NeoBeum said:
flash complete stock, no modifications.
confirm if it loads to usermode
Click to expand...
Click to collapse
I have flashed the lastest stock ftf by flashtool, that is what I do after everytime I brick it while trying to obtain root. And if you mean switching to another user, yes it does.
that's good. it means hardware is fine.
it's your root method.
try this
https://forum.xda-developers.com/showthread.php?t=3609358
Hi peeps
New Pocophone owner here. I got my bootloader unlocked earlier today and now trying to flash the official TWRP 3.3.0.0 recovery from twrp.me, simply following the fastboot instructions on the device guide.
However every time I reboot the device, the recovery always reverts to the stock MIUI recovery?
What am I doing wrong here?
I just got the phone and have upgraded it to MIUI 10.3.6 as well. I am wanting to flash pixel experience onto it.
Do following, instead of flashing your recovery.
Use this method boot and flash Magisk. Reboot back to your system and install Flashify and install your choosen Recovery with it
jonske said:
Hi peeps
New Pocophone owner here. I got my bootloader unlocked earlier today and now trying to flash the official TWRP 3.3.0.0 recovery from twrp.me, simply following the fastboot instructions on the device guide.
However every time I reboot the device, the recovery always reverts to the stock MIUI recovery?
What am I doing wrong here?
I just got the phone and have upgraded it to MIUI 10.3.6 as well. I am wanting to flash pixel experience onto it.
Click to expand...
Click to collapse
in stock rom you need to flash magisk right after flashing twrp else it will get replaced by stock
jonske said:
Hi peeps
New Pocophone owner here. I got my bootloader unlocked earlier today and now trying to flash the official TWRP 3.3.0.0 recovery from twrp.me, simply following the fastboot instructions on the device guide.
However every time I reboot the device, the recovery always reverts to the stock MIUI recovery?
What am I doing wrong here?
I just got the phone and have upgraded it to MIUI 10.3.6 as well. I am wanting to flash pixel experience onto it.
Click to expand...
Click to collapse
What the post above says is correct. However, if you don't want Magisk, after flashing TWRP, reboot into recovery and then into system. You may retain TWRP. However, this doesn't work for everyone.
Hi all, I fixed the issue by completely wiping my phone via TWRP and clean flashing pixel experience ROM. After rebooting on pixel rom TWRP persists.
It appears that MIUI rom has something that keeps reverting it to stock MI-recovery.
If you are on MIUI and flashing TWRP, once the recovery is up for the first time, you need to head on to reboot>recovery again in order to overwrite MIUI stock recovery. So the whole process would be like this;
i) Fastboot flash recovery twrp.img (or whatever the name of the image)
ii) Fastboot boot recovery
iii) Once TWRP is up, Swipe to allow modification and then go to Reboot>Recovery and reboot into TWRP once more. That's it! You have just overwritten the stock recovery and are now on TWRP!! Now you can reboot to system and TWRP will remain on your device. There's no need to flash Magisk etc if you want just TWRP and nothing else.
Rowdyy Ronnie said:
If you are on MIUI and flashing TWRP, once the recovery is up for the first time, you need to head on to reboot>recovery again in order to overwrite MIUI stock recovery. So the whole process would be like this;
i) Fastboot flash recovery twrp.img (or whatever the name of the image)
ii) Fastboot boot recovery
iii) Once TWRP is up, Swipe to allow modification and then go to Reboot>Recovery and reboot into TWRP again. That's it! You have just overwritten the stock recovery and are now on TWRP!! There's no need to flash Magisk etc if you just want TWRP and nothing else.
Click to expand...
Click to collapse
I did those exact steps and it didn't work. It ALWAYS kept getting overwritten.
jonske said:
I did those exact steps and it didn't work. It ALWAYS kept getting overwritten.
Click to expand...
Click to collapse
Did you follow step 3? You can't boot into system right after twrp is up for the first time. You need to reboot into twrp twice before you boot into system. This is what I do whenever I flash twrp and it never failed me yet.
Rowdyy Ronnie said:
Did you follow step 3? You can't boot into system right after twrp is up for the first time. You need to reboot into twrp twice before you boot into system. This is what I do whenever I flash twrp and it never failed me yet.
Click to expand...
Click to collapse
Yes, I even flashed the recovery image from within TWRP and rebooted to recovery again. Still didn't work.
Note this was on the new 10.3.6 stable MIUI release that got rolled out recently. Not sure if it has new detection or anything that rolls it back.
Anyway I have resolved my issue now all is good.
jonske said:
Yes, I even flashed the recovery image from within TWRP and rebooted to recovery again. Still didn't work.
Note this was on the new 10.3.6 stable MIUI release that got rolled out recently. Not sure if it has new detection or anything that rolls it back.
Anyway I have resolved my issue now all is good.
Click to expand...
Click to collapse
How did you fix it?