Problem with OPPO R5S TWRP install - Oppo R5

Hi People, I hope someone out there can help with the problem I have. I'm trying to install TWRP recovery and it results in all Twrp versions 2.xx, i get OPPO powered by Android screen then goes blank. All Versions 3.xx I get the aforementioned screen and it sticks on it. I'm using the unrooted stock version of project spectrum 1.1 atm. I did install the CM recovery when it was around a while back on the device but after bricking it I'm back on stock firmware now and want to use lineageos.
I have tried every method and every TWRP package via fastboot but with no luck, I have been successful before but not now. Thanks

Any luck with it. I'm also stuck with twrp-3.0.2-0-r5.img
davendiva said:
Hi People, I hope someone out there can help with the problem I have. I'm trying to install TWRP recovery and it results in all Twrp versions 2.xx, i get OPPO powered by Android screen then goes blank. All Versions 3.xx I get the aforementioned screen and it sticks on it. I'm using the unrooted stock version of project spectrum 1.1 atm. I did install the CM recovery when it was around a while back on the device but after bricking it I'm back on stock firmware now and want to use lineageos.
I have tried every method and every TWRP package via fastboot but with no luck, I have been successful before but not now. Thanks
Click to expand...
Click to collapse

davendiva said:
Hi People, I hope someone out there can help with the problem I have. I'm trying to install TWRP recovery and it results in all Twrp versions 2.xx, i get OPPO powered by Android screen then goes blank. All Versions 3.xx I get the aforementioned screen and it sticks on it. I'm using the unrooted stock version of project spectrum 1.1 atm. I did install the CM recovery when it was around a while back on the device but after bricking it I'm back on stock firmware now and want to use lineageos.
I have tried every method and every TWRP package via fastboot but with no luck, I have been successful before but not now. Thanks
Click to expand...
Click to collapse
Hi, i had the same problem but managed to fastboot this recovery successfully:
https://androidfilehost.com/?fid=1395089523397922634
Hope it works for you too.
Cheers!

Related

Issues reinstallling Custom Recovery

Hello everyone, long time lurker here. I have used xda over the course of many years with many different devices, and I am extremely grateful to all of you!
I recently cam across an issue. So with my OnePlus X I had unlocked it, rooted it, installed TWRP and a custom ROM (6.x.x). I had that setup for a while, it worked well, and I enjoyed it. I decided to try to update to a 7.x rom, but that is when I had issues. Trying to install the rom through twrp didn't work, and I couldn't revert back to the old rom either. I tried to use the master unbrick thread to set it back to stock, and it worked. The problem here is the stock rom is very broken, things like the OPX home launcher simply freeze and crash. Trying to usethe guide on the oneplus website to unlock it all again to reinstall TWRP doesn't work. I can unlock it, but installing recovery is where it screws up.
So it says it installs, but then when I try to reboot recovery it has a DTB: not found...manually rebooting to recovery leaves a black screen with the oneplus square logo.
Any ideas how to fix this? I am so lost, but I love this phone!
Fastboot flash old stock recovery from OOS2 wipe data and cache install 2.2.3 followed by 3.1.4 then make sure your flashing latest TWRP 3.0.3 from there site. Now should be able to flash Nougat.
Exodusche said:
Fastboot flash old stock recovery from OOS2 wipe data and cache install 2.2.3 followed by 3.1.4 then make sure your flashing latest TWRP 3.0.3 from there site. Now should be able to flash Nougat.
Click to expand...
Click to collapse
Good work sir! Mind you it probably be far easier for him to just
Code:
fastboot flash recovery 3.0.3.28w/e.img
fastboot boot recovery 3.0.3.28w/e.img
And then just plonk a nougat zip onto his device from the TWRP plugged into is computer?
Archtects said:
Good work sir! Mind you it probably be far easier for him to just
Code:
fastboot flash recovery 3.0.3.28w/e.img
fastboot boot recovery 3.0.3.28w/e.img
And then just plonk a nougat zip onto his device from the TWRP plugged into is computer?
Click to expand...
Click to collapse
No because he needs to upgrade the bootloader first to have a TWRP 3.0.3 that works OK.
Kéno40 said:
No because he needs to upgrade the bootloader first to have a TWRP 3.0.3 that works OK.
Click to expand...
Click to collapse
True true.

Can't keep TWRP

So I've unlocked my bootloader and have been trying to install TWRP and try various ROMS. I've only tried paranoid android and Lineage 14.1. Lineage 14.1 doesn't work with gapps, and paranoid doesn't work with blueooth. So I'm going to the stock UK rom.
What I'd like to do is go with the stock UK rom, but I want TWRP too so I can flash things (like a debloat script.) However, whenever I install the UK ROM, twrp stops working. If I re-flash TWRP, the the phone gets stuck in a boot loop.
RNZL3R said:
So I've unlocked my bootloader and have been trying to install TWRP and try various ROMS. I've only tried paranoid android and Lineage 14.1. Lineage 14.1 doesn't work with gapps, and paranoid doesn't work with blueooth. So I'm going to the stock UK rom.
What I'd like to do is go with the stock UK rom, but I want TWRP too so I can flash things (like a debloat script.) However, whenever I install the UK ROM, twrp stops working. If I re-flash TWRP, the the phone gets stuck in a boot loop.
Click to expand...
Click to collapse
are you using the minimal adb to flash the recovery not flashtools like the root thread says to coz if your using flashtool thats y ur in bootloop im on the uk customiseed and have no issues
buzzinkeegs said:
are you using the minimal adb to flash the recovery not flashtools like the root thread says to coz if your using flashtool thats y ur in bootloop im on the uk customiseed and have no issues
Click to expand...
Click to collapse
Which root thread are you referring to? I've seen quite a few and none of the ones I followed mentioned minimal adb. I'm using Flashtool on windows to flash the ROM and I'm using linux for fastboot, since it doesn't work on Windows for some reason and it's too much effort to troubleshoot when it works fine on Linux.
RNZL3R said:
Which root thread are you referring to? I've seen quite a few and none of the ones I followed mentioned minimal adb. I'm using Flashtool on windows to flash the ROM and I'm using linux for fastboot, since it doesn't work on Windows for some reason and it's too much effort to troubleshoot when it works fine on Linux.
Click to expand...
Click to collapse
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f5122-android-n-34-2-2-47-t3594502
that 1
RNZL3R said:
So I've unlocked my bootloader and have been trying to install TWRP and try various ROMS. I've only tried paranoid android and Lineage 14.1. Lineage 14.1 doesn't work with gapps, and paranoid doesn't work with blueooth. So I'm going to the stock UK rom.
What I'd like to do is go with the stock UK rom, but I want TWRP too so I can flash things (like a debloat script.) However, whenever I install the UK ROM, twrp stops working. If I re-flash TWRP, the the phone gets stuck in a boot loop.
Click to expand...
Click to collapse
While flashing the ROM through flashtool, deselect option FOTA-KERNEL, this will keep twrp as your recovery.
Also you can use X-GEN Rom which is based on latest stock rom to flash it from TWRP instead of flashtool
Should I flash TWRP now and then re-flash the UK ROM?
RNZL3R said:
So I've unlocked my bootloader and have been trying to install TWRP and try various ROMS. I've only tried paranoid android and Lineage 14.1. Lineage 14.1 doesn't work with gapps, and paranoid doesn't work with blueooth. So I'm going to the stock UK rom.
What I'd like to do is go with the stock UK rom, but I want TWRP too so I can flash things (like a debloat script.) However, whenever I install the UK ROM, twrp stops working. If I re-flash TWRP, the the phone gets stuck in a boot loop.
Click to expand...
Click to collapse
while flashing stockrom, uncheck FOTAKERNEL.sin in FLASHTOOL FIRMWARE SELECTION PANEL.
this way you can keep the twrp intact

TWRP or OS But Not Both

Hi, I'm hoping someone can offer some assistance. I have an Elephone P9000 (normal version NOT lite) that has official Android 7.0 and I want to install LineageOS 14.1.
As per the instructions I used SP Flash Tool to downgrade the phone to Android 6 (Elephone_P9000_20170112) which worked fine.
I then attempted to install TWRP 3.2.1.0 which also appeared to work ok as I could boot into TWRP recovery and all looked good. However when I tried booting the phone normally it stuck at the white boot logo and would not progress any further.
So I reloaded the Elephone_P9000_20170112 rom again with SP Flash Tool after which the phone would boot normally and then tried installing TWRP 3.0.2.8 as I'd seen threads saying that this version definitely worked with the P9000. However this produced the same result that I could boot into TWRP fine but it would get stuck at the boot logo if I tried booting the phone normally.
I have also tried re-installing the ROM but unticking the recovery option in SP Flash Tool hoping that this would leave the working TWRP intact but this didn't work either.
When I try to boot into recovery I get the little Android laying down with a red exclamation mark.
So I don't know where to go now. I can get EITHER Android to boot or TWRP to boot but not both.
Just in case it is relevant, I am using SP Flash Tool v5.1804_Win in Windows 7 32bit. I don't have any SIM's in the phone and no SD card inserted.
Can someone point me in the right direction please.
Thanks
Russell
Try flashing stock rom with 810 at the end then twrp 3.2.1 and then aokp it is better then lineage
aljoscha81 said:
Try flashing stock rom with 810 at the end then twrp 3.2.1 and then aokp it is better then lineage
Click to expand...
Click to collapse
Thanks very much, that worked fine and AOKP looks really good. When it said install the latest Android v6 it obviously means the previous latest not the current latest
Just in case anyone else is having the same trouble I was:
Using SP Flash Tool load the 20160810 ROM available here: https://forum.xda-developers.com/elephone-p9000/development/rom-elephone-p9000-20160810-t3445897
Then, also using SP Flash Tool, load TWRP v3.2.1 which is available from here: https://eu.dl.twrp.me/p9000/
Then you can use the TWRP recovery to load whichever ROM you like (LineageOS, AOKP etc, etc)
Once again, thanks very much for your help.
:good:

Can't get into TWRP BOOT?

Greetings:
I believe I'm having troubles getting into TWRP. I used to have MIUI 10.0.6 in an Unlocked and Rooted device with TWRP installed. Everytime I pressed VolUp+Power, I got into the TWRP. But, after MIUI 10.1.3 installed by itself, I can't get into TWRP and instead, get into MI-RECOVERY 3.0
Did the new update "roll backed" my TWRP recovery and instead installed the MI-RECOVERY 3.0? Do I have to install TWRP again? Help pls!
Seriously, MIUI is the biggest piece of **** ever...no wonder everyone suggest flashing a custom rom...
DarkDeux said:
Greetings:
I believe I'm having troubles getting into TWRP. I used to have MIUI 10.0.6 in an Unlocked and Rooted device with TWRP installed. Everytime I pressed VolUp+Power, I got into the TWRP. But, after MIUI 10.1.3 installed by itself, I can't get into TWRP and instead, get into MI-RECOVERY 3.0
Did the new update "roll backed" my TWRP recovery and instead installed the MI-RECOVERY 3.0? Do I have to install TWRP again? Help pls!
Seriously, MIUI is the biggest piece of **** ever...no wonder everyone suggest flashing a custom rom...
Click to expand...
Click to collapse
This is nothing new or exclusive to Mi. The original stock ROM will always replace the custom recovery. So you have to flash it again.
In future, after the update, don't boot into system. Boot into recovery and you should boot into TWRP. If not, flash TWRP again. Sometimes even that is not sufficient and you will have to flash Magisk also after flashing TWRP. And then boot into system.
tnsmani said:
This is nothing new or exclusive to Mi. The original stock ROM will always replace the custom recovery. So you have to flash it again.
In future, after the update, don't boot into system. Boot into recovery and you should boot into TWRP. If not, flash TWRP again. Sometimes even that is not sufficient and you will have to flash Magisk also after flashing TWRP. And then boot into system.
Click to expand...
Click to collapse
Thank you so much for the info! It's good to know that. Will have to flash it again.
Thank you once again.
DarkDeux said:
Thank you so much for the info! It's good to know that. Will have to flash it again.
Thank you once again.
Click to expand...
Click to collapse
If you want to thank someone, please use the thanks button below the post.
I have a Xiaomi mi5 and I have same problem...

TWRP 3.3.1 on BV9500 Plus

Hi,
Firstly, sorry for the lack of references in my post, as this is my first one, I'm not allowed to add URLs.
I recently purchased a Blackview BV9500 Plus and I have been trying to flash TWRP, I wanted to try different custom ROMs since the stock ROM for BV9500 PLus is apparently no longer updated (info comes from a Blackview forum).
The TWRP version that I'm trying to flash is 3.3.1 for BV9500 Plus (unofficial).
I have tried different ways, using fastboot flash recovery, using SPFlashTool and flash directly the recovery file, and it looks like the flashing succeeded but I have never been able to boot into TWRP. When I turn on the phone pression the Volume UP key, I see the Blackview logo (which sometimes appears color inverted black <-> white) and then nothing happens, it goes back to rebooting until I let go of the Volum UP key, then it starts normally. I even tried with a different TWRP version (3.2.3 for Android 9.0 Pie MT6771, unofficial) with same results ...
I unlocked the bootloader (ticked it in the phone settings) and did a fastboot flashing unlock, I tried rooted (with last version of Magisk with which I patched the boot.img and flashed), not rooted ... with no luck ... (I even lost my IMEI after a complete format with SPFlash along with the googlekey, fortunately I was able to reflash everything thanks to BV support :laugh::victory
Many thanks in advance for your help, I have been trying to figure this all out for a few days now ...
Best regards.

Categories

Resources