Database Users

TWRP prevents Marshmallow?

I may be doing something stupid, but I've tried various options...
I had an original 5.1.1 build that I let OTA to 6.0. Everything was working fine. I wanted to root, so I installed TWRP... and then the machine wouldn't reboot; it stuck at the "powered by Android" screen and never went into the standard animation screens. I could reboot into TWRP recovery easily enough and using that I could see the filesystem data, but the OS wouldn't boot.
So I reflashed back to 5.1.1 (using http://www.andromods.com/download-files/xt1575-stock-firmware-moto-x-2015-pure-edition.html ), let that OTA to 6.0, installed TWRP... same result.
Third attempt; started at 5.1.1 then installed TWRP (which worked) and then did OTA to 6.0... but this went into a reboot loop.
(Of course during all this I've lost my configs, but I can rebuild that)
Has anyone been able to install TWRP onto an X-Pure 2015 that's running 6.0 ?

What TWRP version are you installing? Make sure it's 2.8.7.1 https://dl.twrp.me/clark/
Sent from my XT1575 using Tapatalk

Sorry, yes, I should have mentioned that; twrp-2.8.7.1-clark.img

Did you install TWRP as read only? I did this and now system recovery is overwriting TWRP and I have no idea how to get out of it.

I had the same problem a couple days ago and posted about it in the 'Android 6.0 Update rolling out! Pure Edition' thread:
"I keep running into a problem after doing the MM update when I flash TWRP (either 2.8.7.0 or 2.8.7.1) where it won't boot into system, just sits there where the animation part should start. Booted/rebooted fine a few times after finishing the MM update, even after flashing the unlocked bootloader logo fix, but as soon as I flash recovery it won't boot system. "
Tried it several times with both TWRP 2.8.7.0 and 2.8.7.1 with no success. Also tried sideloading the OTA per the manual steps in this thread but still couldn't boot to system. Only by already having TWRP installed on 5.1.1 am I able to flash a custom 6.0 ROM successfully. Haven't seen a really clear statement yet that someone has flashed TWRP on fully stock MM with no problem..

EVR_PR said:
Did you install TWRP as read only? I did this and now system recovery is overwriting TWRP and I have no idea how to get out of it.
Click to expand...
Click to collapse
First time I let /system be read-write and second time I let /system be RO. However this likely isn't related to recovery overwriting TWRP; it's documented that on first boot the OS may rewrite the recovery data meaning you'd need to install TWRP again.

Dahenjo said:
I had the same problem a couple days ago and posted about it in the 'Android 6.0 Update rolling out! Pure Edition' thread
...
Haven't seen a really clear statement yet that someone has flashed TWRP on fully stock MM with no problem..
Click to expand...
Click to collapse
Thanks; at least I know it's not me being stupid then (or if I am, then I'm not alone ).

sweh said:
First time I let /system be read-write and second time I let /system be RO. However this likely isn't related to recovery overwriting TWRP; it's documented that on first boot the OS may rewrite the recovery data meaning you'd need to install TWRP again.
Click to expand...
Click to collapse
I have flashed TWRP twice and even rebooted to recovery from recovery and system recovery still overwrites TWRP after booting to system.
Only way I can access TWRP is either flashing it or booting into from the fastboot folder using the fastboot boot command.
Doesn't matter what I do, the option for changing TWRP from read-write to read only doesn't show up anymore.

sweh said:
Thanks; at least I know it's not me being stupid then (or if I am, then I'm not alone ).
Click to expand...
Click to collapse
Well, at age 65 I do put my socks on backwards sometimes..... :silly:

Read on a fairly-detailed post that using adb to flash recovery and rebooting into it should actually work fine!
Could anyone confirm? Is it even possible?
P.S. I'm on XT1572 Indian stock 6.0, and very eager for twrp

I had the exact same problem. I used adb. Stuck on loading screen and then suddenly black. Not able to boot the phone. I'd like to make a nandroid and after that I'd like to use systemless root. If I'm correct, I'll still receive ota's while using systemless root.

Same for me. Returned to stock EU 5.1.1, got update, installed it. Later unlocked bootloader and installed latest TWRP. And now I am stuck on booting up image.
So stock Marshmallow cant be used with TWRP?

BooBzi said:
Same for me. Returned to stock EU 5.1.1, got update, installed it. Later unlocked bootloader and installed latest TWRP. And now I am stuck on booting up image.
So stock Marshmallow cant be used with TWRP?
Click to expand...
Click to collapse
That seems to be the case since I have yet to hear of anyone freshly setting up TWRP for clark/MXPE on purely stock MM without it failing to boot to system afterwards. If you already have TWRP on 5.1.1 you can install a custom MM ROM and then TWRP works normally (ie boots to system), but so far that's the only way I'm aware of to get it functional on MM.
I see you started another thread on this, which may help it get noticed, but maybe also post in the TWRP thread. I posted there on this issue over a week ago but have had zero response from OP, but if others keep doing so maybe that will help.
IMVHO, TWRP for MXPE isn't being supported well - this problem, the version being incorrect for several weeks causing confusion w/dozens of unnecessary posts (this alone could likely be fixed in 2 minutes), as well as the 'SD as internal storage' issue(s) which may be more involved but are still the type of thing those maintaining it are supposed to address. Even some acknowledgement that the issues are recognized and being worked on would be nice, but thus far not even that.

Dahenjo said:
That seems to be the case since I have yet to hear of anyone freshly setting up TWRP for clark/MXPE on purely stock MM without it failing to boot to system afterwards. If you already have TWRP on 5.1.1 you can install a custom MM ROM and then TWRP works normally (ie boots to system), but so far that's the only way I'm aware of to get it functional on MM.
I see you started another thread on this, which may help it get noticed, but maybe also post in the TWRP thread. I posted there on this issue over a week ago but have had zero response from OP, but if others keep doing so maybe that will help.
IMVHO, TWRP for MXPE isn't being supported well - this problem, the version being incorrect for several weeks causing confusion w/dozens of unnecessary posts (this alone could likely be fixed in 2 minutes), as well as the 'SD as internal storage' issue(s) which may be more involved but are still the type of thing those maintaining it are supposed to address. Even some acknowledgement that the issues are recognized and being worked on would be nice, but thus far not even that.
Click to expand...
Click to collapse
Thanks for reply, I did listen to you and post on TWRP thread.

Dahenjo said:
That seems to be the case since I have yet to hear of anyone freshly setting up TWRP for clark/MXPE on purely stock MM without it failing to boot to system afterwards. If you already have TWRP on 5.1.1 you can install a custom MM ROM and then TWRP works normally (ie boots to system), but so far that's the only way I'm aware of to get it functional on MM.
I see you started another thread on this, which may help it get noticed, but maybe also post in the TWRP thread. I posted there on this issue over a week ago but have had zero response from OP, but if others keep doing so maybe that will help.
IMVHO, TWRP for MXPE isn't being supported well - this problem, the version being incorrect for several weeks causing confusion w/dozens of unnecessary posts (this alone could likely be fixed in 2 minutes), as well as the 'SD as internal storage' issue(s) which may be more involved but are still the type of thing those maintaining it are supposed to address. Even some acknowledgement that the issues are recognized and being worked on would be nice, but thus far not even that.
Click to expand...
Click to collapse
I was on pure stock mm and sideloaded twrp without any issues. I use the twrp app (requires root) to reboot into recovery without any problems.

ccic2491 said:
I was on pure stock mm and sideloaded twrp without any issues. I use the twrp app (requires root) to reboot into recovery without any problems.
Click to expand...
Click to collapse
Hello, is it possible to get step by step tutorial?
Later will try on Style with stock MM.
Thanks!

ccic2491 said:
I was on pure stock mm and sideloaded twrp without any issues. I use the twrp app (requires root) to reboot into recovery without any problems.
Click to expand...
Click to collapse
Did you not use the Fastboot Install Method on the TWRP site? We are unable to reboot back into system after using this on stock MM, which always worked fine on stock LP. If you used a different method that worked could you please share what that was?

I am using twrp 2.8.7.1 on my Moto X Style XT1572 Asia retail without any trouble for past two weeks.
I normally flashed it using the fastboot and never ran into trouble.

gulshanstrider said:
I am using twrp 2.8.7.1 on my Moto X Style XT1572 Asia retail without any trouble for past two weeks.
I normally flashed it using the fastboot and never ran into trouble.
Click to expand...
Click to collapse
Just to confirm - when you flashed TWRP you were completely stock after installing the 6.0 OTA (not still on 5.1.1 before taking the OTA), correct?

Dahenjo said:
Just to confirm - when you flashed TWRP you were completely stock after installing the 6.0 OTA (not still on 5.1.1 before taking the OTA), correct?
Click to expand...
Click to collapse
Here is what I did:-
1) I was in Stock 5.1.1 (had unlocked bootloader)
2) I took the OTA.
3) Flashed the twrp 2.8.7.1 using fastboot
So yes I was completely stock 6.0 when I flashed the TWRP for MM

Anyone who installed TWRP and rooted on Marshmallow able to update to Nougat?

If so, how? Thanks!

magicmanfk said:
If so, how? Thanks!
Click to expand...
Click to collapse
This was totally bugging me too but after a whole day of trying I've finally managed it.
1) Go to this thread here
2) Boot into fastboot and flash the boot.img and system.img as suggested in the thread
3) Also flash the original recovery using "fastboot flash recovery recovery.img"
4) Go to the official asus support site here and download the update files you need, the last two
5) Download Version V11.41.87.2 and place the file in the internal storage of your sd card, once you pull the cable out your phone the phone should detect a update file and ask if you want to install it. Click OK.
6) The phone will unpack the update and reboot and install it
7) Delete this update file and then add the latest Nougat update file (Version V20.31.49.2)
8) Do the same again and install it and there you have it... the key is that you have to install each incremental update rather than go straight to the latest.
Oh and I don't know if it makes any difference, but I decided to turn off adb debugging once I'd flashed the various boot, system and recovery images before I started to update using the Asus method.
Also I have successfully re-flashed TWRP through fastboot on Nougat.
Hope this helps.

worked for me perfectly

pjcarrmole said:
This was totally bugging me too but after a whole day of trying I've finally managed it.
1) Go to this thread here
2) Boot into fastboot and flash the boot.img and system.img as suggested in the thread
3) Also flash the original recovery using "fastboot flash recovery recovery.img"
4) Go to the official asus support site here and download the update files you need, the last two
5) Download Version V11.41.87.2 and place the file in the internal storage of your sd card, once you pull the cable out your phone the phone should detect a update file and ask if you want to install it. Click OK.
6) The phone will unpack the update and reboot and install it
7) Delete this update file and then add the latest Nougat update file (Version V20.31.49.2)
8) Do the same again and install it and there you have it... the key is that you have to install each incremental update rather than go straight to the latest.
Oh and I don't know if it makes any difference, but I decided to turn off adb debugging once I'd flashed the various boot, system and recovery images before I started to update using the Asus method.
Also I have successfully re-flashed TWRP through fastboot on Nougat.
Hope this helps.
Click to expand...
Click to collapse
Thanks for the instructions; worked for me. Were you able to re-root? I tried to by following this guide: https://www.reddit.com/r/zenfone/comments/6gqha5/zenfone_3_ze553kl_z01hd_root/
But on step 8 of the supersu website, my phone gets stuck on "starting adb sideload feature." I had already tried installing supersu via twrp, but still no root.

Devalorize said:
Thanks for the instructions; worked for me. Were you able to re-root? I tried to by following this guide: https://www.reddit.com/r/zenfone/comments/6gqha5/zenfone_3_ze553kl_z01hd_root/
But on step 8 of the supersu website, my phone gets stuck on "starting adb sideload feature." I had already tried installing supersu via twrp, but still no root.
Click to expand...
Click to collapse
I flashed TWRP from one of the other threads on here filename twrp-3.1.0-0-Z01H-20170408.img to be precise.
I then flashed the latest version of magisk the zip found here
Then selecting core files only and magisk hide options I have root that passes the latest safetynet checks. No problem.

pjcarrmole said:
I flashed TWRP from one of the other threads on here filename twrp-3.1.0-0-Z01H-20170408.img to be precise.
I then flashed the latest version of magisk the zip found here
Then selecting core files only and magisk hide options I have root that passes the latest safetynet checks. No problem.
Click to expand...
Click to collapse
This worked for me, thanks. It's too bad Xposed doesn't support Nougat yet. Missing my Xposed modules.

Devalorize said:
This worked for me, thanks. It's too bad Xposed doesn't support Nougat yet. Missing my Xposed modules.
Click to expand...
Click to collapse
Magisk has a few modules for it but nothing like Xposed.
I'm going to do a full back up and then see how well ZenUI plays with Substratum as most of the ZenUI Themes are pretty poor and I want an all black theme. I'll let people know how it goes if anyone is interested in using substratum.
---------- Post added at 10:28 AM ---------- Previous post was at 09:32 AM ----------
pjcarrmole said:
I flashed TWRP from one of the other threads on here filename twrp-3.1.0-0-Z01H-20170408.img to be precise.
I then flashed the latest version of magisk the zip found here
Then selecting core files only and magisk hide options I have root that passes the latest safetynet checks. No problem.
Click to expand...
Click to collapse
Oh, if you're having trouble getting TWRP to stick don't reboot the system but reboot back into Recovery, by holding the Vol - & Power together and using the Volume buttons to select Recovery.
After this you can then reboot normally.

[marmite] Official Wileyfox Swift 2+ Updates (also for root) - Repository

Hi!
As Wileyfox issued another OTA today and the last time I had a hard time to find the proper information, I thought I'd start a thread that contains the update information and links for ALL OTAs in one place right at the start.
But first of all: This would not be possible without linuxct and mdosch who delivered this information in a combined effort. I added only a few things, like the new updates and put everything in one place.
1. The official update links from Wileyfox (partially from here, here and myself):
TOS118C (Recovery Image)
TOS163B (Recovery Image) Deleted by Wileyfox
TOS208G (Recovery Image) Deleted by Wileyfox
TOS249H (Recovery Image)
TOS319I (Recovery Image) Deleted by Wileyfox
TOS373J missing
UOS224B missing
UOS273C (Recovery Image)
TOS118C (Fastboot Image) Deleted by Wileyfox
TOS163B (Fastboot Image) Deleted by Wileyfox
TOS208G (Fastboot Image) Deleted by Wileyfox
TOS249H (Fastboot Image)
TOS319I (Fastboot Image)
TOS373J (Fastboot Image)
UOS224B missing
UOS273C missing
TOS089A to TOS118C (OTA Update)
TOS118C to TOS163B (OTA Update)
TOS163B to TOS208G (OTA Update)
TOS208G to TOS249H (OTA Update)
TOS249H to TOS319I (OTA Update)
TOS319I to TOS373J (OTA Update)
TOS373J to UOS224B (OTA Update to OREO 1)
UOS224B to UOS273C (OTA Update)
TOS373J to UOS273C (OTA Update to OREO 2)
2. The instructions how to make the OTA links work (taken from here):
If you directly click it, it will return an Error 404, but that is not true since the file actually exists... But requires a special HTTP header to be visible. Since I wanted to grab the OTA link now that, for once, I finally got an OTA in this phone after always upgrading through fastboot images, I used wireshark to determine the server where it fetches it and the full file route. It turns out the header sends a special UA string as you can see in the picture attached: rsotaua 1.0, which is, most probably, a randomly generated string. Now here's the thing: if you want to switch the UA you'll need an extension to do so. linuxct has used this one and on Firefox I used this one. As soon as it's installed, go to the Options of the extension and add it like here:
Code:
WILEYFOX rsotaua 1.0 Chrome Replace WF
Once the string is inserted, switch to it and hit the URL. The OTA should be downloadable now.
As I just found out: The "User Agent Switcher" for Chrome works just as fine.
3. The instructions how to update a rooted phone (taken from here):
I'll write down what I did to get it finally work, but be aware you might brick your phone. I did this with Windows 7 and 10 successfully with fastboot and adb installed.
3.1. Download and unzip the fastboot image from point 1. Then switch to fastboot mode and flash boot, recovery and system.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
3.2. Boot to stock recovery and choose "apply update from adb". Then sideload the update.
Code:
adb sideload wf-marmite-aa4d5d86bc-to-8eec3af77b-signed.zip
This is, of course, an EXAMPLE! You have to put in the name of the actual update you want to do.
3.3. After successful install wipe cache and dalvik/arts cache and reboot to system. If you have issues with "dm verity" do it with the following command (I myself didn't need to do it):
Code:
adb reboot "dm-verity enforcing"
3.4. When the update is configured let the phone switched on for a while (I don't know why, but mdosch ended in a bootloop and had to start again when he instantly rebooted, I myself didn't need to wait). Here you can already put the SuperUser ZIP-file onto your phone via USB (or do it later via sideload).
3.5. Then boot to bootloader and BOOT (not flash) TWRP
Code:
fastboot boot twrp-3.1.1-0-marmite.img
3.6. If you have the SuperUser ZIP-file already on the phone flash it, otherwise go to "ADB -> Sideload" and install there
Code:
adb sideload superuser.zip
3.7. Wipe cache and dalvik/arts cache and finally reboot. Again, if you have issues with "dm verity" do it with the following command (I myself didn't need to do it)::
Code:
adb reboot "dm-verity enforcing"
This is how it worked for me in Windows 7 and 10 on my Wileyfox Swift 2 Plus. Neither did I brick my phone, nor did I loose ANY(!) data, neither from storage nor from any app. But as I don't know what you did with yours I won't issue any warranties here...
BTW: If you ever wondered, when you do the OTA the phone saves the zip here: data/data/com.android.providers.downloads/cache
So, linuxct and mdosch thank you very much again and I hope you don't mind about what I did with your input. :fingers-crossed:
And also thanks to image45 and DIMICH666 for getting hold of some more of the image links.

Thanks, wish I had found this 2 hours earlier! I had been downloading the OTA update but it was failing to install. Spent ages searching my phone for the location of the download without success. Eventually connected my phone to my laptop and did 'adb logcat' - found the URL of the OTA File download "http:\/\/ota-files.wf.bsp.ninja\/marmite\/wf-marmite-8eec3af77b-to-0fcf4099d0-signed.zip". Changed 'User Agent' as described, put the URL in the address bar and hit enter and hey presto! Good to have a repository to refer to.

Hi
I'm already on TOS163B. Can I just sideload the TOS208G OTA zip? Without reflashing the boot, recovery and system images from TOS163B?
The images from TOS208G are not available.?

Thanks for this.
I managed to grab the TOD208G OTA. Flashing the zip in TWRP did not work though. I got an unexpected fingerprint error (6.0.1 instead of 7.1.2). I flashed the last available debloater on TOS163B (which worked fine), but that probably has got me in trouble now. Is there any way to fix this easily, without having to root and remove all the debloat stuff manually?
(... I dream about Lineage 14.1)

H2Oxide said:
Thanks for this.
(... I dream about Lineage 14.1)
Click to expand...
Click to collapse
We all do, I tried an unofficial build however no WiFi yet :crying:
Even with an official build we would still have the unlocked bootloader warning screen and the dm-verity screen that threatens to switch your phone off in 30 seconds if power not pressed. I am sure it only gave you 5 seconds then just continue to boot when running on the Cyanogen ROMs
I am sure there is some ADB the resolve this for the oneplusone phones.
After initial boot the ROM got stuck on the white splash screen. After I installed Magisk via TWRP flashable zip it worked so must need dm-verity switch off.

I never updated back at the end of 2016 because I was unsure if it was a good idea but now I've become annoyed by it constantly asking me to (OTA UK). Should I update to cm-marmite 460.6 MB like it's asking me to? And then I suppose it will pick up and ask me to install the updates since? Thanks.

quixoticduck said:
Should I update to cm-marmite 460.6 MB like it's asking me to? And then I suppose it will pick up and ask me to install the updates since? Thanks.
Click to expand...
Click to collapse
It needs to be what you want, I flashed the cm-13.1.4-ZNH2KAS5RM-marmite-signed-5175bd793a.zip then removed the cm updater to stop it prompting me to move to the next update as it would eventually have you on current build if you accept all the updates.
I flashed cm-13.1.4 as I found it the most stable Cyanogen Marshmallow 6.0.1 ROM and I wanted xposed framework.
However like I said at start of post what do you need from your phone/ android version?

image45 said:
It needs to be what you want, I flashed the cm-13.1.4-ZNH2KAS5RM-marmite-signed-5175bd793a.zip then removed the cm updater to stop it prompting me to move to the next update as it would eventually have you on current build if you accept all the updates.
I flashed cm-13.1.4 as I found it the most stable Cyanogen Marshmallow 6.0.1 ROM and I wanted xposed framework.
Click to expand...
Click to collapse
Thanks, I see what you mean, about it being personal preference. The last couple years I've stepped away from rooting and flashing roms, so right now I suppose all I really want is a stable safe version. Back in 2016 I remember people being worried about the OTA update released right after Cyanogenmod's end, with people thinking the new update might be suspicious (why I never updated, and then stopped following things). So if it turned out that the OTA update was fine then I suppose the easiest and safest way to stop it bugging me about the update might just be to update xD as long as there's no risks (besides the basic risk that any update could bring). Probably makes it easier for any further updates too if any appear.
I hadn't heard of the xposed framework, sounds interesting, I'll look into that just in case I want to use it.

quixoticduck said:
I hadn't heard of the xposed framework, sounds interesting, I'll look into that just in case I want to use it.
Click to expand...
Click to collapse
You need an unlocked bootloader and custom recovery to install xposed framework. However I can jump between any of the Swift 2 ROMs when ever I wish of course.

Currently on the update right before that one, with TWRP and Magisk installed. I found the zip as instructed. Has anybody had success with Flashfire for a small OTA update like this or do you absolutely have to use adb sideload?

Don't know whether I can post links to other sites but there are instruction on how to update to 7.1.2 using the OTA file for both rooted and non-rooted devices at
http://www.stechguide.com/install-android-7-1-2-nougat-on-wileyfox-swift-2/

H2Oxide said:
Thanks for this.
I managed to grab the TOD208G OTA. Flashing the zip in TWRP did not work though. I got an unexpected fingerprint error (6.0.1 instead of 7.1.2). I flashed the last available debloater on TOS163B (which worked fine), but that probably has got me in trouble now. Is there any way to fix this easily, without having to root and remove all the debloat stuff manually?
Click to expand...
Click to collapse
Any thoughts on this? Can I force a sideload or would that be unwise...

der_dkw said:
So, linuxct and mdosch thank you very much again and I hope you don't mind about what I did with your input. :fingers-crossed:
Click to expand...
Click to collapse
Sure that's fine.
I really appreciate you collected all the information and created this overview.

Well I finally managed to try the adb sideload and this is what I got.
What's wrong here?
I'm using TOS163B (7.1.2) so I don't know why it says I have 6.0.1 test keys. I'm trying to sideload TOS208G
Any help is much appreciated

Jack3volution said:
What's wrong here?
Click to expand...
Click to collapse
You are using TWRP not stock recovery.
The OTA zips check your device for not being altered (like rooting or using custom recovery) this is why you have to go to a plain stock rom while flashing boot, recovery and system from the fastboot image (not the complete image as it will erase your data as well I assume).
After you have done this boot to stock recovery and adb sideload the first OTA zip then reboot and so on until you are on the latest.
Then you can boot twrp (I recommend booting instead of flashing as for me it complained about my device being altered when I flashed twrp) and root again (as root was lost during this update process).

Thanks! my mistake. Yeah I still have stock recovery
Cheers

mdosch said:
Then you can boot twrp (I recommend booting instead of flashing as for me it complained about my device being altered when I flashed twrp) and root again (as root was lost during this update process).
Click to expand...
Click to collapse
What's the actual different between booting TWRP and flashing please?

image45 said:
What's the actual different between booting TWRP and flashing please?
Click to expand...
Click to collapse
Booting means you boot TWRP temporarily without replacing your stock recovery. Flashing means you replace the stock recovery with TWRP.

mdosch said:
You are using TWRP not stock recovery.
Click to expand...
Click to collapse
Hmm it didn't work in stock recovery either

Jack3volution said:
Hmm it didn't work in stock recovery either
Click to expand...
Click to collapse
Did you apply the OTA zips in the correct order?
Did you alter your devices in any way like rooting or installing magisk?
You are on TOS163B you said. Did you start your device before booting to recovery? For me after sideloading the TOS163B, sideloading of TOS208G failed when I tried to install it instantly so I cleared the cache/dalvik cache booted to Android, then rebooted to (stock) recovery again and successfully sideloaded TOS208G.

Accidentally flashed boot to TWRP

Good evening!
Well, my problem is, that trying to install TWRP as recovery (which I did). After doing it, I used the following command -stupidly because I wasn't thinking- thinking it was another thing:
flashboot flash boot twrp.img
Now, everytime I try to boot my OP5, it loads the TWRP.
Now, what can I do? I have the full 4.5.12 OTA that I downloaded from a post in the original OP5 forum, but the one I have installed in my phone is the 4.5.10 or 4.5.11 (I'm not sure now, the last one available before the .12).
Thank you very much!

enlapse said:
Good evening!
Well, my problem is, that trying to install TWRP as recovery (which I did). After doing it, I used the following command -stupidly because I wasn't thinking- thinking it was another thing:
flashboot flash boot twrp.img
Now, everytime I try to boot my OP5, it loads the TWRP.
Now, what can I do? I have the full 4.5.12 OTA that I downloaded from a post in the original OP5 forum, but the one I have installed in my phone is the 4.5.10 or 4.5.11 (I'm not sure now, the last one available before the .12).
Thank you very much!
Click to expand...
Click to collapse
1.Unzip the full OTA file
2. Take boot.img from OTA file
3. Execute following command:
flashboot flash boot boot.img

Thank you very much!
But what if my version is not the same as the OTA I have? Will that affect? Because my version is for sure lower than what I have.

enlapse said:
Thank you very much!
But what if my version is not the same as the OTA I have? Will that affect? Because my version is for sure lower than what I have.
Click to expand...
Click to collapse
You can flash the OTA (if it's over 1GB) in TWRP too.
That will simply update your software to the latest version and will hopefully also bring your phone to a working state.

In other words, what you did was flash TWRP to the boot partition instead of the normal recovery partition. Simply reflash the boot.img to the boot partition and you should be good to go. The boot.img is mostly the kernel and doesn't usually change much from OTA to OTA so you should be fine.

Help Plz...Stock recovery missing and unable to install any recovery !

Thanks in advance......i'm so frustrated feel ripping my **** off.. being struggling with this for 3 days...
I was on official stock 7.0 nougat (generic russian), genesis kernel drmfix & Twrp for about a year with no issue. In fact that's my 1st and only attempt in flashing this phone. Decided to upgrade to 8.0. Big mistake!?!
Used Emma flash to flash the latest stock 8.0 release for my region, Asia. It booted up fine, all was well. I read that flashing stock will simply remove root and twrp. But i realized stock recovery was missing as well. And i can't restore any kind of recovery no matter what i tried. Suggestions please !
When i tried to enter recovery, the phone simply vibrated twice, and then 3 times quickly. If i continue holding the buttons, it goes into a loop of black screen and boot screen.
Tried flashing twrp via adb/fastboot. It appeared successful . No error messages. File size and time taken was also reported. But no recovery upon rebooting.
Fastboot flash recovery twrp.img
I can only flash roms using Emma, Flashtool ftf always fail with a 'no loader' found message.
Tried re-flashing mm, nougat and oreo via Emma. Phone runs well for all but again no stock recovery.
Don't know what else to do or what the problem is......
If i reflash to stock rom and relock boot loader without any recovery, it that dangerous?

Baron Zemo said:
Thanks in advance......i'm so frustrated feel ripping my **** off.. being struggling with this for 3 days...
I was on official stock 7.0 nougat (generic russian), genesis kernel drmfix & Twrp for about a year with no issue. In fact that's my 1st and only attempt in flashing this phone. Decided to upgrade to 8.0. Big mistake!?!
Used Emma flash to flash the latest stock 8.0 release for my region, Asia. It booted up fine, all was well. I read that flashing stock will simply remove root and twrp. But i realized stock recovery was missing as well. And i can't restore any kind of recovery no matter what i tried. Suggestions please !
When i tried to enter recovery, the phone simply vibrated twice, and then 3 times quickly. If i continue holding the buttons, it goes into a loop of black screen and boot screen.
Tried flashing twrp via adb/fastboot. It appeared successful . No error messages. File size and time taken was also reported. But no recovery upon rebooting.
Fastboot flash recovery twrp.img
I can only flash roms using Emma, Flashtool ftf always fail with a 'no loader' found message.
Tried re-flashing mm, nougat and oreo via Emma. Phone runs well for all but again no stock recovery.
Don't know what else to do or what the problem is......
If i reflash to stock rom and relock boot loader without any recovery, it that dangerous?
Click to expand...
Click to collapse
https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479
1. Download 'Modded boot img for 34.4.A.2.118' from that thread
2. Flash stock with Emma
3. Don't turn on the phone, go to fastboot and flash the boot img and TWRP img

levone1 said:
https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479
1. Download 'Modded boot img for 34.4.A.2.118' from that thread
2. Flash stock with Emma
3. Don't turn on the phone, go to fastboot and flash the boot img and TWRP img
Click to expand...
Click to collapse
Hi, Thanks for the reply
1. Done
2. Which do i choose in Emma? Software update content (erases user content) or Firmware update versions.
Also must i choose the stock rom which must tally with boot img 34.4.A.2.118? ie. the rom version which ends with .118?
3. Fingers crossed.

Baron Zemo said:
Hi, Thanks for the reply
1. Done
2. Which do i choose in Emma? Software update content (erases user content) or Firmware update versions.
Also must i choose the stock rom which must tally with boot img 34.4.A.2.118? ie. the rom version which ends with .118?
3. Fingers crossed.
Click to expand...
Click to collapse
Yes, flash 118 fw. If you want to save data, back it up first.

levone1 said:
Yes, flash 118 fw. If you want to save data, back it up first.
Click to expand...
Click to collapse
I have given up I followed the instructions explicitly.
Tried flashing latest stock from different regions via Emma, Flashtool/xperifirm and ftfs from online depositories. Then flashed with the corresponding downloaded boot.img, then TWRP without any rebooting inbetween. Even created patched boot.img from extracted .elf files to try. There was no error messages or anything.
Recovery runs fine. But starting normally it either boot loops are stuck at Sony logo.
Is there any other way to get the drm restored? Can i root it via common methods and work my way from there?

Baron Zemo said:
I have given up I followed the instructions explicitly.
Tried flashing latest stock from different regions via Emma, Flashtool/xperifirm and ftfs from online depositories. Then flashed with the corresponding downloaded boot.img, then TWRP without any rebooting inbetween. Even created patched boot.img from extracted .elf files to try. There was no error messages or anything.
Recovery runs fine. But starting normally it either boot loops are stuck at Sony logo.
Is there any other way to get the drm restored? Can i root it via common methods and work my way from there?
Click to expand...
Click to collapse
Did you full wipe before flashing, or when flashing, (check boxes in 'wipe' section)?

levone1 said:
Did you full wipe before flashing, or when flashing, (check boxes in 'wipe' section)?
Click to expand...
Click to collapse
If i use flash tool, i ticked all boxes under Wipe sin during stock rom flashing. All the rest (exclude sin & misc TAs) are unchecked. No other wiping during the process.
If i use Emma, there's no chance to wipe anything, it's auto flash stock rom, then flash boot.img, then flash Twrp, then reboot to a boot loop.
btw, i've tried latest twrp 3.2.3 and 3.2.1
Also, when i flash stock, is stock recovery supposed to return? Twrp just gets removed, and i don't have any recovery at all.
Am i cursed?

Baron Zemo said:
If i use flash tool, i ticked all boxes under Wipe sin during stock rom flashing. All the rest (exclude sin & misc TAs) are unchecked. No other wiping during the process.
If i use Emma, there's no chance to wipe anything, it's auto flash stock rom, then flash boot.img, then flash Twrp, then reboot to a boot loop.
btw, i've tried latest twrp 3.2.3 and 3.2.1
Also, when i flash stock, is stock recovery supposed to return? Twrp just gets removed, and i don't have any recovery at all.
Am i cursed?
Click to expand...
Click to collapse
I don't think you can boot to Sony stock recovery. If you flash stock 118, then flash modded boot img and TWRP, and reboot, I don't know why it wouldn't work. Many have done it. Just to be sure -
1. To enter recovery, you power off, then press power and volume down together, until vibration.
2. First boot takes a while. Wait a good 10 minutes to be sure.

levone1 said:
I don't think you can boot to Sony stock recovery. If you flash stock 118, then flash modded boot img and TWRP, and reboot, I don't know why it wouldn't work. Many have done it. Just to be sure -
1. To enter recovery, you power off, then press power and volume down together, until vibration.
2. First boot takes a while. Wait a good 10 minutes to be sure.
Click to expand...
Click to collapse
There's why it's so odd to me. Not the 1st time i'm doing this too. I would have waited even longer if it was stuck, but it was looping continuously back to the start.
I suspect could simply be a hardware fault developed. Anyway, i've given up. Probably best excuse to get a new phone
Many thanks for trying to help :good:

I haven't been able to get mine to reboot to recovery either, so i just boot recovery.img from fastboot anytime I want to mod. Kinda annoying but I haven't figured a way around it.