Database Develop

Stuck at TWRP after OTA

Hi Guys,
I'm stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off, but wil still boot in TWRP
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditionally'
- Another zip flashes, but gets stuck at the end, no reboot option (or was I to hasty? )
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
Not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please

sndr1384 said:
Hi Guys,
I'm stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off, but wil still boot in TWRP
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditionally'
- Another zip flashes, but gets stuck at the end, no reboot option (or was I to hasty? )
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
Not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
Click to expand...
Click to collapse
downloading the ota wont cause this. Did u try doing the update after it downloaded?
---------- Post added at 02:27 AM ---------- Previous post was at 02:24 AM ----------
sndr1384 said:
Hi Guys,
I'm stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off, but wil still boot in TWRP
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditionally'
- Another zip flashes, but gets stuck at the end, no reboot option (or was I to hasty? )
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
Not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
Click to expand...
Click to collapse
Make sure u are one 3.0.4-1 twrp.
https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391
go to the second post on this thread and download full zip of 4.0.3 and the use mtp while in twrp and proceed to follow the steps on how to install a rom.
do a factory reset
transfer file to phone and install.

the_rooter said:
downloading the ota wont cause this. Did u try doing the update after it downloaded?
---------- Post added at 02:27 AM ---------- Previous post was at 02:24 AM ----------
Make sure u are one 3.0.4-1 twrp.
https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391
go to the second post on this thread and download full zip of 4.0.3 and the use mtp while in twrp and proceed to follow the steps on how to install a rom.
do a factory reset
transfer file to phone and install.
Click to expand...
Click to collapse
OK Thanks, That seemed to be it,
Back on 4.0.3 now, but with stock recovery so no root acces..
Now i should read the fist post to get root acces again?
Once again, thanks for the quick response, most of the times i'm just to afraid to go out and flashing right and left

sndr1384 said:
OK Thanks, That seemed to be it,
Back on 4.0.3 now, but with stock recovery so no root acces..
Now i should read the fist post to get root acces again?
Once again, thanks for the quick response, most of the times i'm just to afraid to go out and flashing right and left
Click to expand...
Click to collapse
use the toolkit to flash TWRP and Super SU

TimFlex said:
just reflash super Su through TWRP
Click to expand...
Click to collapse
I've lost TWRP and its has stock recovery again.
Guess I have to install it again?

sndr1384 said:
I've lost TWRP and its has stock recovery again.
Guess I have to install it again?
Click to expand...
Click to collapse
Sorry I miss read your post...
Just use the toolkit to flash twrp and SU.

sndr1384 said:
OK Thanks, That seemed to be it,
Back on 4.0.3 now, but with stock recovery so no root acces..
Now i should read the fist post to get root acces again?
Once again, thanks for the quick response, most of the times i'm just to afraid to go out and flashing right and left
Click to expand...
Click to collapse
use the toolkit as a last resort. use adb and flash via fastboot twrp 3.0.4-1

Flash Failed trying to Install Recovery

Hi guys, is the first time i try to install another room on my Xperia Z, i followed step by step all the requeriments
-I unlocked the bootloader
-I rooted my phone
-Install Recovery. I downloaded the TWRP App on Play Store. I select my device (Xperia Z) and i choose the last file to flash (twrp-3.0.2.0-yuga.img). I press "Flash To Recovery" and it says Flash Failed, so i can turn on my phone on the Recovery Mode..
There's another way to install the recovery? I'm a little bit worried because i heard about "Bricked Phone" and i don't wanna do something that could bring me to that.
PD: After i unlock the bootloader and root the phone, i downloader the TWRP App, and i think this could be important. The first time i open this App i have the Option to "Backup Existing Recovery". And i never installed a Recovery and in addition, when i unlocked the bootloader, all the information was deleted (yes i knew this) but TWRP gave me the option to backup and existing recovery.
Maybe if now i reset all data to zero and install again TWRP app could work?
PD2: First time i did it i don't read if the Recovery was installed. I was following instructions and tryied to reboot to enter recovery (turn off button + volume down) but it didn't work. So i once again did the same process and it said Flash Failed. Seems maybe i already have the recovery installed but for some reason i can enter

Seems i already have installed the Recovery with the TWRP Official App. The problem is that the first time i installed i didn't read the message that said if it was all ok or no. Seems was all Ok. But when i tried to enter into the Recovery Mode i coudn't (Turn On + Volumen Down Button). So again i installed the Recovery but this time it said "Flash Failed"
If i install XZDualrecovery assuming for a moment that i have already installed a recovery, could be any problem?

I m also facing problem in flashing from twrp.
Each time I m unble to flash.
As msg is showing flash failed.

@ MrDubsstep @Yuvraj aryan
hi,
both of you, did you already unlock the bootloader and after that root the phone?
TWRP app from playstore need root permission to be able install the recovery..

Thanks I will unlock boot loader and then try to flash custom recovery.

Yuvraj aryan said:
Thanks I will unlock boot loader and then try to flash custom recovery.
Click to expand...
Click to collapse
dummytest97 said:
@ MrDubsstep @Yuvraj aryan
hi,
both of you, did you already unlock the bootloader and after that root the phone?
TWRP app from playstore need root permission to be able install the recovery..
Click to expand...
Click to collapse
Yes i did it but my problem is already fixed.
First i unlocked the bootloader, then i rooted with Kingroot app. I installed TWRP Official App but this didn't work for me. So i installed the XZDualrecovery. After that i tried to install the ROM but again failed with another error. So after i installed the XZDualrecovery i installed TWRP 3.1.0 and then the ROM, and is done.
You can see the Chippa post, people helped me there

MrDubsstep said:
Yes i did it but my problem is already fixed.
First i unlocked the bootloader, then i rooted with Kingroot app. I installed TWRP Official App but this didn't work for me. So i installed the XZDualrecovery. After that i tried to install the ROM but again failed with another error. So after i installed the XZDualrecovery i installed TWRP 3.1.0 and then the ROM, and is done.
You can see the Chippa post, people helped me there
Click to expand...
Click to collapse
Congratz for you,,now you can use custom rom...
but not like me..still having trouble with custom rom...always stuck at logo animation..i just can use stock rom for now..
my xperia z bootloader already unlocked..i have been trying your method too ,,install dualrecovery and the TWRP 3.1.0 and then the custom rom but still stuck at logo animation...i dont know where i miss..T_T
---------- Post added at 11:10 AM ---------- Previous post was at 10:26 AM ----------
@MrDubsstep
hi,
may i ask,how long you must wait for the custom rom to boot for the 1st time?
and did you flash the gapps too after flash custom rom?

dummytest97 said:
Congratz for you,,now you can use custom rom...
but not like me..still having trouble with custom rom...always stuck at logo animation..i just can use stock rom for now..
my xperia z bootloader already unlocked..i have been trying your method too ,,install dualrecovery and the TWRP 3.1.0 and then the custom rom but still stuck at logo animation...i dont know where i miss..T_T
---------- Post added at 11:10 AM ---------- Previous post was at 10:26 AM ----------
@MrDubsstep
hi,
may i ask,how long you must wait for the custom rom to boot for the 1st time?
and did you flash the gapps too after flash custom rom?
Click to expand...
Click to collapse
I'm gonna explain you all the method for you to know and if somebody has any problem.
First of all, if you did something and was wrong, go to flash your phone here: https://developer.sonymobile.com/open-devices/flash-tool/use-the-flash-tool-for-xperia-devices/. This restart your phone, quit root and recovery.
1- Unlock your phone here: https://developer.sonymobile.com/unlockbootloader/
2- Download and install Kingroot App, root and then download Check root App if all is okay.
3- Download the XZDualrecovery here: http://nut.xperia-files.com/path/XZ...g21jd24hub9so04tqn9vc50&randomizer=_oupgp8psh and follow the instructions here: https://www.youtube.com/watch?v=NteAd_MzsPI
4- Once recovery is installed, reboot, enter the recovery and Press Wipe and select Data, Cache and Dalvik Cache. Maybe system but i don't know.
5-Install the ROM and without reboot install the Gapps. First time maybe it could 10-15 minutes or less to restart with the new ROM, just wait.
Hope it worked for you!

MrDubsstep said:
I'm gonna explain you all the method for you to know and if somebody has any problem.
First of all, if you did something and was wrong, go to flash your phone here: https://developer.sonymobile.com/open-devices/flash-tool/use-the-flash-tool-for-xperia-devices/. This restart your phone, quit root and recovery.
1- Unlock your phone here: https://developer.sonymobile.com/unlockbootloader/
2- Download and install Kingroot App, root and then download Check root App if all is okay.
3- Download the XZDualrecovery here: http://nut.xperia-files.com/path/XZ...g21jd24hub9so04tqn9vc50&randomizer=_oupgp8psh and follow the instructions here: https://www.youtube.com/watch?v=NteAd_MzsPI
4- Once recovery is installed, reboot, enter the recovery and Press Wipe and select Data, Cache and Dalvik Cache. Maybe system but i don't know.
5-Install the ROM and without reboot install the Gapps. First time maybe it could 10-15 minutes or less to restart with the new ROM, just wait.
Hope it worked for you!
Click to expand...
Click to collapse
my xperia z already unlocked...so i just go straight flash using flashtool from sony link or i need to relock the bootloader 1st?
or the flashtool from sony will relock the bootloader too when flash?
---------- Post added 18-06-2017 at 12:04 AM ---------- Previous post was 17-06-2017 at 11:38 PM ----------
1 more question,
when you install the the xz dual recovery what stock rom you use? kitkat or lollipop 5.1.1?
and when you install TWRP 3.1.0 it ask to flash at boot or fota kernel,which one you choose?

dummytest97 said:
when you install the the xz dual recovery what stock rom you use? kitkat or lollipop 5.1.1?
and when you install TWRP 3.1.0 it ask to flash at boot or fota kernel,which one you choose?
Click to expand...
Click to collapse
Dual recovery will work in both Stock KitKat and Stock Lollipop rom.
The very first install should be from KitKat ofcourse, because in KitKat
its the most easy to root, and root is require for install dual recovery.
The recovery must be installed in fota partition if you read instructions
on twrp homepage.
Its hard to try help people when they partly ignore
and do their own experiments ..

franticfreddy said:
Dual recovery will work in both Stock KitKat and Stock Lollipop rom.
The very first install should be from KitKat ofcourse, because in KitKat
its the most easy to root, and root is require for install dual recovery.
The recovery must be installed in fota partition if you read instructions
on twrp homepage.
Its hard to try help people when they partly ignore
and do their own experiments ..
Click to expand...
Click to collapse
Nice point you have there..:victory:at least I will not doing wrong step again..thank you @franticfreddy

dummytest97 said:
my xperia z already unlocked...so i just go straight flash using flashtool from sony link or i need to relock the bootloader 1st?
or the flashtool from sony will relock the bootloader too when flash?
---------- Post added 18-06-2017 at 12:04 AM ---------- Previous post was 17-06-2017 at 11:38 PM ----------
1 more question,
when you install the the xz dual recovery what stock rom you use? kitkat or lollipop 5.1.1?
and when you install TWRP 3.1.0 it ask to flash at boot or fota kernel,which one you choose?
Click to expand...
Click to collapse
No, no matter if you flash or not, if you unlock the bootloader is gonna be unlocked even if you flash. If you did something and was wrong, in my opinion you should flash and start again.
And the rom i used was lollipop 5.1.1. I didn't see what you say about kernel or boot, maybe i did it wrong but i'm good now with the ROM.
I forgot to mention that after installing dualrecovery you install TWRP 3.1 but i see you know it

Stuck in Fastboot Mode / TWRP without OS

Hello people,
I have an OnePlus 3T, which does not start the OS. I can open Fastboot Mode or TWRP. I do not even know which OS is installed (I think stock rom, but do not know). When I boot into Fastboot, I get the dm-verity notification "Phone is unlocked and cannot be trusted". When I boot into system, it stops at the black "Powered by android" Screen (very first screen).
When I connect my phone to the PC and open the internal storage, it shows only the "TWRP" folder.
So what Information do I have so far (with my amateur knowledge):
adb shell getprop ...
ro.build.version.release: 6.0.1
ro.build.version.sdk: 23
ro.build.display.id: omni_oneplus3-eng 6.0.1 MOB31K eng.jc.20170208.012427 test-keys
ro.modversion: OmniROM-6.0.1-20170208-oneplus3-HOMEMADE
ro.twrp.version: 3.0.4-1
When I start the bootloader:
Product_Name - msm8996
Variant - MTP UFS
Bootloader Version -
Baseband Version -
Serial Number - *****
Secure Boot - enabled
Device State - unlocked
I tried to reflash the original recovery => device did not start in recovery anymore => reflashed twrp
I tried to flash the stock ROM => did not work (with this Error 7)
So my first question: Which OS do I have? Really Marshmallow 6.0.1?
Second: Do you need more infos?
Third and most important: How to repair this mess?
What do I want: A stable, rooted ROM. It can be the stock ROM, but also a custom, I do not care right now.
I read that this unlocked-notification appears because I have the wrong kernel? Is that true? Which one do I need?
Thank you very much for your help.

Use ADB Sideload to Sideload a ROM onto the phone since you have TWRP working. It's not a huge problem, and it's easily solvable.
*OR* you can use the Unbrick tool to solve your problem.

thes3usa said:
Use ADB Sideload to Sideload a ROM onto the phone since you have TWRP working. It's not a huge problem, and it's easily solvable.
*OR* you can use the Unbrick tool to solve your problem.
Click to expand...
Click to collapse
Thank you for your reply.
Okay so it is not important which system I run right now? And what about this kernel thing?
I can just flash it with sideload (e.g. https://forum.xda-developers.com/on...pment/rom-kernel-resurrectionremix-n-t3524715) and finished? Rooted and particularly working?
Sorry for the questions but I am a little nervous

elchico92 said:
Thank you for your reply.
Okay so it is not important which system I run right now? And what about this kernel thing?
I can just flash it with sideload (e.g. https://forum.xda-developers.com/on...pment/rom-kernel-resurrectionremix-n-t3524715) and finished? Rooted and particularly working?
Sorry for the questions but I am a little nervous
Click to expand...
Click to collapse
You may want to Sideload the latest Firmware too, Open Beta 21 that is. And then Sideload a Nougat ROM. Don't sideload any GAPPs.

thes3usa said:
You may want to Sideload the latest Firmware too, Open Beta 21 that is. And then Sideload a Nougat ROM. Don't sideload any GAPPs.
Click to expand...
Click to collapse
So first this one (downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_21/), then this (androidfilehost.com/?w=files&flid=131965 - latest)?
Thanks again!
PS: Sorry I cannot post links yet.

elchico92 said:
So first this one (downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_21/), then this (androidfilehost.com/?w=files&flid=131965 - latest)?
Thanks again!
PS: Sorry I cannot post links yet.
Click to expand...
Click to collapse
Nope, that's the complete stock Zip. Unless you want to install OOS, that's not the one to Sideload.
Download the FW only from here: https://forum.xda-developers.com/oneplus-3t/how-to/firmware-beta-10-t3631166
And then Sideload it, reboot back to recovery, and then Sideload the ROM.

elchico92 said:
When I connect my phone to the PC and open the internal storage, it shows only the "TWRP" folder.
Click to expand...
Click to collapse
What is in the TWRP folder, anything? The TWRP folder would normally only be created, if a backup was created. You can possibly just boot TWRP, select the RESTORE option, select the backup from the TWRP folder, and get the phone up and running again.
Another possibility, if you aren't that up on adb commands (sideload, etc.), since you can access the internal storage, just download a ROM or fill stock ROM zip onto your PC, then just drag/copy to internal storage. Then boot TWRP, select INSTALL, pick the file, and flash it.
What is the background of the device, how do you not know the OS version? Did you receive it this way, or fixing it for a friend or something?
---------- Post added at 09:19 AM ---------- Previous post was at 09:12 AM ----------
elchico92 said:
When I boot into Fastboot, I get the dm-verity notification "Phone is unlocked and cannot be trusted".
I read that this unlocked-notification appears because I have the wrong kernel? Is that true? Which one do I need?
Click to expand...
Click to collapse
That isn't the dm-verity notification. The dm-verity notification screen is similar, but says "dm-verity is not started in enforcing mode".
What you described is the bootloader unlocked warning screen. The bootloader unlocked warning screen is expected and normal (in fact, unavoidable) if the bootloader is unlocked. And unlocked bootloader is required for TWRP, flashing custom ROMs, etc.
dm-verity warning screen is in fact normal, as well, if you have TWRP installed. That one can be disabled by a couple different methods. But it's only purpose is to notify a "average" user that the system has been modified. For XDA users that are intentionally modifying their phones (TWRP, root, etc.) the warning is pretty meaningless. Under certain conditions, dm-verity will prevent the phone from booting. But TWRP and root in themselves, will normally not do that.
Neither warning means you have the wrong kernel, necessarily. And unless you (or someone else) tried to flash a kernel, there really isn't any reason to believe that.
---------- Post added at 09:29 AM ---------- Previous post was at 09:19 AM ----------
elchico92 said:
I tried to reflash the original recovery => device did not start in recovery anymore => reflashed twrp
Click to expand...
Click to collapse
Flashing stock recovery will (by definition) replace TWRP with stock recovery. You probably have recovery, just the stock one (not TWRP) which is fairly useless in your case (can't flash custom ROMs, root, etc.).
elchico92 said:
I tried to flash the stock ROM => did not work (with this Error 7)
Click to expand...
Click to collapse
Can't really troubleshoot this, unless you tell us what file exactly (file name) and where you got it from. "Stock ROM" is far too vague, and can literally mean a dozen or more different things.
Also, what version TWRP?
Using a TWRP version which does not support Oreo is one reason for Error 7. Or you may have tried a file intended for the 3, not the 3T. So these details need to be provided, before we can figure out what went wrong.
elchico92 said:
What do I want: A stable, rooted ROM. It can be the stock ROM, but also a custom, I do not care right now.
Click to expand...
Click to collapse
You kind of need to decide which of those you want. Otherwise, there are just too many options for us to give.
Yet another option (in addition to those given) would be to flash the full stock OOS zip from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Then before rebooting, flash Magisk to root, and you should be all set. The full zip will put you on a fully stock baseline (including firmware). Which, if you aren't sure if you want stock, beta or custom ROM, is not a bad place to be; you can see what the "stock" condition is, before messing with things like custom ROMs. But again, it's totally subjective and a matter of personal preference, and you really do need to decide for yourself what is best for you (as an individual) at this time.

thes3usa said:
You may want to Sideload the latest Firmware too, Open Beta 21 that is. And then Sideload a Nougat ROM. Don't sideload any GAPPs.
Click to expand...
Click to collapse
Why not just sideload stock ROM which includes the firmware? Make life easier

przemcio510 said:
Why not just sideload stock ROM which includes the firmware? Make life easier
Click to expand...
Click to collapse
Yeah, that is a good option, among many. As I mentioned, there are just too many options since the original poster hasn't even decided stock or custom ROM.

przemcio510 said:
Why not just sideload stock ROM which includes the firmware? Make life easier
Click to expand...
Click to collapse
Since OP hasn't mentioned whether he wants to use a stock or custom ROM. So I gave him the link for the latest FW, in case he wants to use a recently updated custom ROM without needing to download the whole Stock zip.

Done!
Thanks a lot. The phone is working again.
I have flashed with adb sideload the firmware and the ResurrectionRemix-Rom (Nougat) and then via TWRP the gapps.
So I hope, everthing will be fine now.
answers:
- TWRP-folder: yeah I created one because I thought, maybe to restore will fix anything
- I tried to flash with TWRP a ROM, but it says "Error 7", which means: wrong ROM => but I am sure, it was the right one
- background: it was the phone of a friend of mine => he never heard anything about ROMs etc
The thread can be closed.

elchico92 said:
- I tried to flash with TWRP a ROM, but it says "Error 7", which means: wrong ROM => but I am sure, it was the right one
Click to expand...
Click to collapse
I already offered to troubleshoot this error for your, but you never supplied the requested info. Don't assume it is the "right one" next time, but rather, give exact file names, version numbers, and let us verify. Mistakes happen, and it always is good to have another set of eyes look at the specifics.
---------- Post added at 09:58 AM ---------- Previous post was at 09:56 AM ----------
elchico92 said:
The thread can be closed.
Click to expand...
Click to collapse
Threads on xda don't get closed, just because you solved your current issue. Others may have a similar problem, and may want to ask questions, etc.

I'm stuck in Fastboot Mode & TWRP without OS
I everyone,
Like the title say I'm totally stuck, I don't know what to do ....
I've got a OnePlus 3T few years ago, and the first thing i did at the installation was to encrypt the phone with an option of oxygen OS, and after that i unlock the oem and add root access.
But when oneplus release a major update, there was issues with phone encrypted and unlock, for that I never could make an update of the OS, so I did try to install the lastest lineage os recently, and add an "error 7".
After reading a lot of stuff and try a lot of manupilations, i'm now totally stuck with only access to the fastboot, twrp, and the recovery of oneplus.
If someone here could help me, you will be very gratefull because i can't afford to buy a new phone for the moment... thank's

slykereven said:
I everyone,
Like the title say I'm totally stuck, I don't know what to do ....
I've got a OnePlus 3T few years ago, and the first thing i did at the installation was to encrypt the phone with an option of oxygen OS, and after that i unlock the oem and add root access.
But when oneplus release a major update, there was issues with phone encrypted and unlock, for that I never could make an update of the OS, so I did try to install the lastest lineage os recently, and add an "error 7".
After reading a lot of stuff and try a lot of manupilations, i'm now totally stuck with only access to the fastboot, twrp, and the recovery of oneplus.
If someone here could help me, you will be very gratefull because i can't afford to buy a new phone for the moment... thank's
Click to expand...
Click to collapse
This should get you back to OOS:
In TWRP:
1. Do a factory reset
2. Flash OOS 9.0.6 full rom
3. Flash this modified firmware (to avoid the issue 9.0.6 with encrypted+unlocked) https://github.com/nvertigo/firmwar...3t/oxygenos-9.0.6-bl-km-5.0.8-firmware-3T.zip (see https://forum.xda-developers.com/on...5-0-8-firmware-barrier-t3941164/post79758055)
4. Reboot
This should leave you with a clean install of OOS 9.0.6 and an encrypted phone with the stock recovery (TWRP gets replaced when you boot stock OOS).
From that point you can do what you want.
Sent from my OnePlus 3T using XDA Labs

Resolved
OK, that's a little crazy but it's working, i've got a one plus 3T A3003, but i had to install Stable9.0.3+Firmware+Modem_OnePlus3.zip and not the one for the 3T ..... then install the last lineage os 17, and everything seems to work for now !!!
---------- Post added at 09:13 AM ---------- Previous post was at 09:09 AM ----------
BillGoss said:
This should get you back to OOS:
In TWRP:
1. Do a factory reset
2. Flash OOS 9.0.6 full rom
3. Flash this modified firmware (to avoid the issue 9.0.6 with encrypted+unlocked) https://github.com/nvertigo/firmwar...3t/oxygenos-9.0.6-bl-km-5.0.8-firmware-3T.zip (see https://forum.xda-developers.com/on...5-0-8-firmware-barrier-t3941164/post79758055)
4. Reboot
This should leave you with a clean install of OOS 9.0.6 and an encrypted phone with the stock recovery (TWRP gets replaced when you boot stock OOS).
From that point you can do what you want.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Hi, thank's for your help, i didn't see your answer before and i have resolved the issue with other method

October update is out - QP1A.190711.148

October 2019 Release | Q 10 - Q Release 2 - QP1A.190711.148 | Open Market
https://www.essential.com/developer/current-builds

chanh2018 said:
October 2019 Release | Q 10 - Q Release 2 - QP1A.190711.148 | Open Market
https://www.essential.com/developer/current-builds
Click to expand...
Click to collapse
Won't root for me.

you mean magisk not working with this build?

mcdull said:
you mean magisk not working with this build?
Click to expand...
Click to collapse
No, it's not working for ME.
Sent from my PH-1 using XDA Labs

avd said:
Won't root for me.
Click to expand...
Click to collapse
Were you able to root the previous 10 build? I have the 148 rooted with Magisk canary, same as the previous two builds (just root, no TWRP). Not sure if it makes a difference, but I don't do OTA updates. I always download and flash the OTA image in adb sideload, then flash the patched boot.img in fastboot.

kt-Froggy said:
Were you able to root the previous 10 build? I have the 148 rooted with Magisk canary, same as the previous two builds (just root, no TWRP). Not sure if it makes a difference, but I don't do OTA updates. I always download and flash the OTA image in adb sideload, then flash the patched boot.img in fastboot.
Click to expand...
Click to collapse
oh cool, so flashing boot images work with the latest canary of MM?! will do that then this evening as well :fingers-crossed:

JimmyCash030 said:
oh cool, so flashing boot images work with the latest canary of MM?! will do that then this evening as well :fingers-crossed:
Click to expand...
Click to collapse
Yes, it does work for me. I've always been doing updates like this, on 9 and 10. Download both OTA and the full image, extract boot.img from the full image, patch it with Magisk, then sideload OTA image in adb, reboot, and finally fastboot flash the patched boot.img. Never had a problem. The only thing is that you have to use Magisk canary build with 10; stable or beta doesn't work.

kt-Froggy said:
Yes, it does work for me. I've always been doing updates like this, on 9 and 10. Download both OTA and the full image, extract boot.img from the full image, patch it with Magisk, then sideload OTA image in adb, reboot, and finally fastboot flash the patched boot.img. Never had a problem. The only thing is that you have to use Magisk canary build with 10; stable or beta doesn't work.
Click to expand...
Click to collapse
yeah worked for me as well with the latest canary MM !!

Magisk 19.4 works just fine on latest 148 build if need be I can upload magisk rooted boot. Img

https://www.androidfilehost.com/?fid=1899786940962605417
MD5:49484e6733bba257051eef831eb25689
This is for QP1A.19711.148
Magisk-Patched-Boot.img

allenjthomsen said:
https://www.androidfilehost.com/?fid=1899786940962605417
MD5:49484e6733bba257051eef831eb25689
This is for QP1A.19711.148
Magisk-Patched-Boot.img
Click to expand...
Click to collapse
getting back to the topic at hand, I flashed this, then TWRP on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now I got to plug this in and swap slots to reinstall TWRP.
Is possible that magisk and twrp are back to not playing nice to each other again?
(I'll test this out if I get a chance to swap slots)
---------- Post added at 11:11 AM ---------- Previous post was at 10:49 AM ----------
avd said:
getting back to the topic at hand, i flashed this, then twrp on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now i got to plug this in and swap slots to reinstall twrp.
Is possible that magisk and twrp are back to not playing nice to each other again?
(i'll test this out if i get a chance to swap slots)
Click to expand...
Click to collapse
now i'm just sitting here looking at the boot animation. Will let it go a little further to see if it starts.

Honestly i couldnt tell you i only rooted havent used twrp much yet because of the lack of android 10 custom roms havent seen a need to use it as of yet.
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
And any further information on this would be great.

allenjthomsen said:
Honestly i couldnt tell you i only rooted havent used twrp much yet because of the lack of android 10 custom roms havent seen a need to use it as of yet.
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
And any further information on this would be great.
Click to expand...
Click to collapse
pretty much everything for this phone resides in t.me/ESSENTIALPH1DEV

avd said:
getting back to the topic at hand, I flashed this, then TWRP on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now I got to plug this in and swap slots to reinstall TWRP.
Is possible that magisk and twrp are back to not playing nice to each other again?
(I'll test this out if I get a chance to swap slots)
---------- Post added at 11:11 AM ---------- Previous post was at 10:49 AM ----------
now i'm just sitting here looking at the boot animation. Will let it go a little further to see if it starts.
Click to expand...
Click to collapse
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again

rignfool said:
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again
Click to expand...
Click to collapse
Flashing the patched image provided just sits there looking at the boot animation.
I'll play with it tonight.
It's a Sprint phone. Could that be the issue?
Sent from my PH-1 using XDA Labs

I flashed September build like this no problem however when I try and adb the October build I cannot get into recovery, when trying it just boots back into system however I can get into fastboot, any ideas?

I'm no expert but did this ans it worked:
1. In TWRP recovery (created nandroid and wiped cache)
2. Flashed full update zip from official download link, then TWRP, then wipe cache
3. Reboot system and let it settle
4. Reboot into TRWP and flashed Canary Channel zip file
5. Wipe cache
6. Reboot system
Hope this helps.

jionny said:
I flashed September build like this no problem however when I try and adb the October build I cannot get into recovery, when trying it just boots back into system however I can get into fastboot, any ideas?
Click to expand...
Click to collapse
Try using the fastboot image (not the OTA the image one) from the essential site.
Download it, remove the "fastboot or something wipe userdata maybe?" line from the flashall.bat script (or from flashall.sh if you're on Mac/Linux)
Then run the flashall.bat or flashall.sh script (again .bat for Win, .sh for the rest)
Should get you working again, albeit without root & twrp
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
rignfool said:
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again
Click to expand...
Click to collapse
? I always have trouble remembering, not anymore it seems

gavinfernandes2012 said:
Try using the fastboot image (not the OTA the image one) from the essential site.
Download it, remove the "fastboot or something wipe userdata maybe?" line from the flashall.bat script (or from flashall.sh if you're on Mac/Linux)
Then run the flashall.bat or flashall.sh script (again .bat for Win, .sh for the rest)
Should get you working again, albeit without root & twrp
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
I always have trouble remembering, not anymore it seems
Click to expand...
Click to collapse
Are you able to give more precise instructions on fastboot instructions?

jionny said:
Are you able to give more precise instructions on fastboot instructions?
Click to expand...
Click to collapse
Nevermind, got the instructions from essentials site. flashed via fastboot which erased everything had to do a complete setup again

Bootloop after "Factory Reset" from TWRP

I tried to perform a factory reset from TWRP cause it wouldn't let me from Configuration>Reset and Restore (or something like that), and after a reboot system didn't launch, it said something about an encryption problem, so I decided to restore a system backup I did and now my phone is stuck in bootloop. Someone can point me in the right direction? Thanks in advance.

Yzakz said:
I tried to perform a factory reset from TWRP cause it wouldn't let me from Configuration>Reset and Restore (or something like that), and after a reboot system didn't launch, it said something about an encryption problem, so I decided to restore a system backup I did and now my phone is stuck in bootloop. Someone can point me in the right direction? Thanks in advance.
Click to expand...
Click to collapse
We're you on stock Orero, Pie? Or one of the custom Pie, Q ROMs?

Ainz_Ooal_Gown said:
We're you on stock Orero, Pie? Or one of the custom Pie, Q ROMs?
Click to expand...
Click to collapse
Stock Pie

Yzakz said:
Stock Pie
Click to expand...
Click to collapse
Yeah TWRP and Stock are at odds with each other.... You must fallow the guide to make TWRP and Stock compatible with each other when restoring.... alternatively you can try to flash one of the custom ROMs and see if it boots.
---------- Post added at 11:55 PM ---------- Previous post was at 11:51 PM ----------
This guide specifically https://forum.xda-developers.com/lg-v40/how-to/guide-twrp-data-access-stock-t3970149

Ainz_Ooal_Gown said:
Yeah TWRP and Stock are at odds with each other.... You must fallow the guide to make TWRP and Stock compatible with each other when restoring.... alternatively you can try to flash one of the custom ROMs and see if it boots.
---------- Post added at 11:55 PM ---------- Previous post was at 11:51 PM ----------
This guide specifically https://forum.xda-developers.com/lg-v40/how-to/guide-twrp-data-access-stock-t3970149
Click to expand...
Click to collapse
I tried with LineageOS but no luck. In fact, I tried to install LineageOS before I had this problem and even when TWRP said "Success", the phone booted into stock pie rom

Yzakz said:
I tried with LineageOS but no luck. In fact, I tried to install LineageOS before I had this problem and even when TWRP said "Success", the phone booted into stock pie rom
Click to expand...
Click to collapse
Did you switch slots?

Ainz_Ooal_Gown said:
Did you switch slots?
Click to expand...
Click to collapse
When? When installing LineageOS? To be honest right now I don't remember exactly what I did, but I'm 100% that I followed the write-up in the TWRP thread step by step.

Which slot should I select to install a custom rom?

Yzakz said:
Which slot should I select to install a custom rom?
Click to expand...
Click to collapse
When you install a ROM made for the V40 if your on Slot A when you boot into TWRP then the ROM installs in Slot B and if on B the it installs into A. But gapps and other flashable zips install into the current booted slot.
So flashing steps would be
1. Boot TWRP
2. Check which slot your on in the reboot menu
3. Flash ROM
4. Flash the TWRP recovery IMG. To ram disk
5. Go to reboot menu and select opposite Slot
6. Select reboot recovery and swipe to reboot
7.flash anything else gapps etc.
8. Reboot into your new working ROM.

Ainz_Ooal_Gown said:
When you install a ROM made for the V40 if your on Slot A when you boot into TWRP then the ROM installs in Slot B and if on B the it installs into A. But gapps and other flashable zips install into the current booted slot.
So flashing steps would be
1. Boot TWRP
2. Check which slot your on in the reboot menu
3. Flash ROM
4. Flash the TWRP recovery IMG. To ram disk
5. Go to reboot menu and select opposite Slot
6. Select reboot recovery and swipe to reboot
7.flash anything else gapps etc.
8. Reboot into your new working ROM.
Click to expand...
Click to collapse
I thought I did that, but when I rebooted the phone it booted to the stock Android rom

Yzakz said:
I thought I did that, but when I rebooted the phone it booted to the stock Android rom
Click to expand...
Click to collapse
My guess is you didn't select reboot recovery and instead hit reboot system...