Good morning,
I don't know why but my current phone status is that doesn't boot anymore with Android installed on it. At the moment I've my phone unlocked, twrp 3.1.1 and a backup of last S.O.
I took (when unlocking) a complete full_dump.img as described in the thread UnlockBootloader correctly, with all other files also.
Now, I'm able to enter in TWRP, so I place these operatinos:
wipe all
restore backuped twrp zip
restart phone in normal booting
All operation seems to works fine but when I restart the phone it goes back in TWRP... no android boot window. I watched the content of phone and it seems no files where placed in system (it seems void).
What's the matter?
I'm able to go in fastboot mode also (download mode it working but my PC can't recognize the COM port at the moment)
Help me please, I'd like to restore the complete full_dump.img (and return with locked status var) with the command:
send_command \\.\COM19
dd if=/data/media/0/full_dump.img of=/dev/block/mmcblk0 bs=4096 count=1552384
Anyone help me please?
I tried many time to install a .ZIP custom image ROM, but it doesn't seem to boot with android because all times come back in TWRP.
Sounds like you wiped system, edited it, deleted something or it is corrupt.
Wipe everything excluding system ( don't check it off)
Go advanced > fix permissions
Install a ROM again
If that doesn't work. I suspect you have a file system anymore.
You will now have to go backwards, reinstall stock image using lg bridge if you didn't make a backup of stock with the file system
Romulus76 said:
Good morning,
I don't know why but my current phone status is that doesn't boot anymore with Android installed on it. At the moment I've my phone unlocked, twrp 3.1.1 and a backup of last S.O.
I took (when unlocking) a complete full_dump.img as described in the thread UnlockBootloader correctly, with all other files also.
Now, I'm able to enter in TWRP, so I place these operatinos:
wipe all
restore backuped twrp zip
restart phone in normal booting
All operation seems to works fine but when I restart the phone it goes back in TWRP... no android boot window. I watched the content of phone and it seems no files where placed in system (it seems void).
What's the matter?
I'm able to go in fastboot mode also (download mode it working but my PC can't recognize the COM port at the moment)
Help me please, I'd like to restore the complete full_dump.img (and return with locked status var) with the command:
send_command \.\COM19
dd if=/data/media/0/full_dump.img of=/dev/block/mmcblk0 bs=4096 count=1552384
Click to expand...
Click to collapse
You can use FWUL ( https://tinyurl.com/FWULatXDA ). Go into LG folder and double click on the lglaf auth icon.
Once you see the terminal window use your restore command:
dd if=/data/media/0/full_dump.img of=/dev/block/mmcblk0 bs=4096 count=1552384
Next time you should consider to use the DLM backup method ( https://tinyurl.com/dlbackup )
Regarding TWRP try the latest beta in the official TWRP thread.
Try to format system in the wipe menu then flash a custom ROM again. Pull the recovery log afterwards as described in the TWRP FAQ 4 A of the official TWRP thread.
.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
You can use FWUL ( https://tinyurl.com/FWULatXDA ). Go into LG folder and double click on the lglaf auth icon.
Once you see the terminal window use your restore command:
dd if=/data/media/0/full_dump.img of=/dev/block/mmcblk0 bs=4096 count=1552384
Next time you should consider to use the DLM backup method ( https://tinyurl.com/dlbackup )
Regarding TWRP try the latest beta in the official TWRP thread.
Try to format system in the wipe menu then flash a custom ROM again. Pull the recovery log afterwards as described in the TWRP FAQ 4 A of the official TWRP thread.
.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
I'd try this method first. Steadfaster is more credible and knows what he us talking about before you try my suggestion and wipe data as well.
His method is to restore the file system... And to make a backup of it in case it happens again
---------- Post added at 08:11 AM ---------- Previous post was at 08:06 AM ----------
BTW I'm using twrp 3.1.1 works fine but your phone might not like it
deltadiesel said:
Sounds like you wiped system, edited it, deleted something or it is corrupt.
Wipe everything excluding system ( don't check it off)
Go advanced > fix permissions
Install a ROM again
If that doesn't work. I suspect you have a file system anymore.
You will now have to go backwards, reinstall stock image using lg bridge if you didn't make a backup of stock with the file system
Click to expand...
Click to collapse
Yes, it sounds like something was corrupt in the file system or similar.
I tried to install a new custom ROM (as many other times in the past), wiping data - cache - system first but with no luck, it wont boot Android, and return always in TWRP.
Yesterday evening I tried also a full KDZ refurbish with LGUP since my phone can boot in download mode (and recognized from LGUP), but with no luck because after start the process the tool give me a message back (at 9% of operation):
"FAIL - Flash error code 0x2000"
Is there any method to repair corrupted file system or flash partition? TWRP o similar?
steadfasterX said:
Next time you should consider to use the DLM backup method ( https://tinyurl.com/dlbackup )
Regarding TWRP try the latest beta in the official TWRP thread.
Try to format system in the wipe menu then flash a custom ROM again. Pull the recovery log afterwards as described in the TWRP FAQ 4 A of the official TWRP thread.
Click to expand...
Click to collapse
Thanks,
but when I made the full_dump.img there wasn't this DLM method out yet (I made this on the 11/16/2015)
I'll try the new beta TWRP on the official thread late this evening, and I'll try to make a LOG...
Thread update: my phone doesn't go in recovery mode also, now only in DOWNLOAD MODE (volUP + USB cable) and it hangs on error 0x2000
I think I'll take the phone to the LG customer care, for motherboard change.
You are getting 0x2000 because you are trying to flash a KDZ with an older ARB version than what is currently on your phone. You need to flash newer firmware that has the same or greater ARB version than what is on your phone.
-- Brian
Romulus76 said:
Thread update: my phone doesn't go in recovery mode also, now only in DOWNLOAD MODE (volUP + USB cable) and it hangs on error 0x2000
I think I'll take the phone to the LG customer care, for motherboard change.
Click to expand...
Click to collapse
You are flashing the wrong file for your phone
Flash another one
After you success fully flash right file( try one that is biggest in size and most recent)
Flash TWRP (3.1.1 should be fine after)
MAKE A BACKUP OF EVERYTHING (data, system, firmware, etc - so you don't have to go through this again just in case)
Wipe ( don't wipe system - you can do a regular wipe without checking things off it doesn't select system)
Install custom ROM
Flash SuperSU to root again
https://forum.xda-developers.com/showthread.php?t=3660257
Post 71-75
Related
Even simpler root than Invisiblek's method for the older versions: If you have already tried that method and now have broken wireless, see Post #2.
Note: A more detailed and user-friendly version of these instructions can be found at: http://www.oppoforums.com/threads/n5206-international-root-instructions.24159
Download http://lum.uk/n3/files/recmodn3.img and http://lum.uk/n3/files/Root_ColorOS_by_tantrums_v2.zip
Copy the rooter onto your SD card.
Boot into fastboot by holding volume up while powering on the phone.
fastboot oem unlock
fastboot flash recovery recmodn3.img
fastboot boot recmodn3.img
Flash the root coloros zip file, reboot and you're rooted.
Note: This is a modified stock recovery that can flash OTAs as well as zips not signed by Oppo. If you prefer TWRP then that is available here: https://dl.twrp.me/n3/. Note that at the time of writing TWRP is unable to flash OTAs.
Thanks to [email protected] for the original root method, Arvin A. [email protected] for the fixing SuperSU to work on ColorOS, and [email protected] for providing the modified N3 recovery.
Restoring stock firmware
Download your chosen firmware and recovery from this thread
Copy the firmware to the root of the internal storage
Take a nandroid backup using TWRP
Reboot to bootloader from within TWRP
Code:
fastboot flash recovery recovery_N3.img
fastboot reboot
adb reboot recovery
Use the stock recovery to flash your chosen firmware
If you are downgrading then wipe data and cache (you did remember to take a nandroid, right?)
Reboot
You are now on stock fimware. Follow the rooting instructions in post #1, and if you wiped you may optionally restore only the data partition from your nandroid backup.
Will memory be erased?
Hi,
So i'm looking forward to root my beautiful Oppo N3.
On my last Phones memory (data and so on) was erased alongside with unlocking the phone.
Will it be the same on this phone so that I have to backup all my data?
Your data will not be erased when rooting or unlocking. Also your warranty will not be invalidated like it is with other manufacturers.
It is, however, always wise to take a backup before anything like this, just in case something does go wrong.
Hi,
I tried rooting my N3 now but i made a mistake by not executing the commands after falshing SuperSU.
That's why my phone is always booting into TWRP. There i tried executing your commands, but apparently the shell refuses to su by throwing exception: "command not found"
Going on with mount-command, it is also giving back an error: "can't find /system in /proc/mounts"
Hope sb could help me now...
EDIT: Solved by installing stock recovery, booting system, and the reflash twrp.
Lum_UK said:
Even simpler root than Invisiblek's method for the older versions: If you have already tried that method and now have broken wireless, see Post #2
Download http://teamw.in/project/twrp2/282 and http://download.chainfire.eu/supersu
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery openrecovery-twrp-2.8.4.0-n3.img
fastboot reboot
adb reboot recovery
Flash Super SU from within TWRP. Then boot the OS
adb shell
su
mount -o remount,rw /system
echo "/system/xbin/su --daemon &" >> /system/etc/init.qcom.post_boot.sh
Reboot and you're rooted.
By default ColorOS doesn't let apps auto-start themselves, so go into security centre and allow SuperSU to auto-start, otherwise you won't get prompts for root when other apps need it.
Thanks to invisiblek for the original root method and babelmonk for the fix. I have shamelessly copied these and adapted them for the new firmware.
Click to expand...
Click to collapse
Quoted from your post in oppo forum
Wait for the phone to boot:
adb reboot recovery
It should boot into TWRP recovery flash the SuperSU zip you downloaded but do not reboot as we need to fix a small bug in SuperSU due to Oppo not using the expected startup scripts.
adb shell
su
mount -o remount,rw /system
echo "/system/xbin/su --daemon &" >> /system/etc/init.qcom.post_boot.sh
Reboot and congratulations. You are now rooted.
Sorry , quite new in fastboot command so i apologize if I misunderstood you but I'm running on N5206_EX_23_150208 , which should i follow ? to boot up after flashing SuperSU or not to boot up ?
It doesn't matter which way around you do it, just that root won't work outside of ADB until it's done.
I assume that XDA folk are more familiar with ADB etc. than on the Oppo forums so the instructions skip over more detail here.
Updated the method to use fastboot boot instead of fastboot flash.
This should work around the issue with phones that can't flash twrp, and also leave the stock recovery in place which is more useful to have until we get some custom roms.
Lum_UK said:
Updated the method to use fastboot boot instead of fastboot flash.
This should work around the issue with phones that can't flash twrp, and also leave the stock recovery in place which is more useful to have until we get some custom roms.
Click to expand...
Click to collapse
I was using modified boot.img to get root and then edit init.qcom.post_boot.sh. Now my wi-fi is broken. Can I fix it without wiping? Maybe flash some other boot img?
Anilexis said:
I was using modified boot.img to get root and then edit init.qcom.post_boot.sh. Now my wi-fi is broken. Can I fix it without wiping? Maybe flash some other boot img?
Click to expand...
Click to collapse
Fixed it by flashing boot.img from 150208, root still there due to script edit.
Updated the OP to use the modified stock recovery (Wmjan's recovery for the N5207) as this will be friendlier to noobs and also make it easier to install OTAs.
Anyone know where to get the root coloros file? Link doesn't seem to work for me...
http://www.oppoforums.com/attachment..._v2-zip.31142/
cowabunga said:
Anyone know where to get the root coloros file? Link doesn't seem to work for me...
http://www.oppoforums.com/attachment..._v2-zip.31142/
Click to expand...
Click to collapse
Sorry for the delay in replying. I've re-hosted the file for you.
http://lum.uk/n3/files/Root_ColorOS_by_tantrums_v2.zip
You could also try this. It worked on my girlfriend's R5 running a similar version of ColorOS. Didn't need modified recovery or anything, install it, run, click the root button, and it'll reboot to recovery and root for you.
http://lum.uk/n3/files/ForceRoot.apk
can this root work with Chines n5207
Hello,
I'm from Malaysia,
I got problem with my N3 / N5206 after update the newest version of software...now it cannot detect any line signal and open a wifi...what the problem,can u help me...
I can't make the WiFi to work again. Installed all versions of firmware and no luck....
Update: I was using the wrong tool to flash the firmware.
Don't update the phone with Msm8974DownloadTool !!!!
You have to download and install QPST_2.7.460 and place the phone in download mode by pressing volume + and power button and then in QPST load the firmware N5206EX_11_A.11_150528_SVN6225 or Oppo_N3_N5206_EX_11_A.13_151230 or N5206EX_11_A.10_150519_SVN6196
After flashing the wifi is working but you gonna loose the NV ram backup for the IMEI numbers..
Then you have to open dealpad with *#801# and anable Full-port ON
In QFIL(QPST) click on Tools then click QCN Backup Restore
Choose the qcn file and press restore.
Everything will work again after reboot the phone...
Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
I have the same problem
Here the same but with CM14 after a wrong download & install now Recovery Loop
How to solve???
I had this problem too. Flash the Oxygen recovery OB7. It will update automatically and turn on. But be patient because it takes a lot.
sibmon said:
Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
Click to expand...
Click to collapse
The way I found works is to start from scratch and yes you will lose all data on the phone. Had to do this yesterday because I messed a few things up.
Make sure you have the modified recovery (1.28), Beta 9 Full (1.3GB), and SuperSU (SR5) if you want root, on your computer. And you will need your computer for these steps.
1. Boot to TWRP > Wipe > Format Data. There's a warning screen you just type yes and press enter. This should set your /data partition to F2FS; all other partitions will remain EXT4. (The TWRP MTP didn't pop up on me so then I had to reflash twrp from fastboot). If your PC see's your device after this step, skip to step 9, but my guess is, when you format data, the required files for MTP disappears with it.
2. Power off your device.
3. Put device into fastboot mode (start device by holding volume up + power)
4. Connect device to PC.
5. fastboot flash recovery modded_twrp.img
6. Disconnect device from computer and shut down phone.
7. Load recovery (start device by holding volume down + power)
8. Connect to PC
9. TWRP MTP should be working; transfer the recovery file, beta9, and super SU (if you want root) to your internal storage.
10. I usually disconnect my phone from my PC at this point.
11. Go to Install > sdcard > media folder (your files should be here).
12. Flash Beta 9 zip.
13. Reflash modded TWRP (click Install Image button and you should see your TWRP file).
14. Reboot to Recovery (I noticed that click on Reboot and Recovery freezes TWRP on me, so you can manually power down by holding power button down).
15. Swipe to accept modifications
16. If you don't need root, you're all done. The first boot takes like 5 min.
For some reason for root, it doesn't work if you try without freeing up some space in the system folder. What you can do is:
1. In TWRP > Mount > tick off System > head back out to main menu
18. Advanced > File Manager > > system folder > app folder > and delete some google apps (ie. calendar, gmail, chrome; should be enough; can be downloaded from play store later)
19. Flash SuperSU SR5.
20. Wipe Cache and Dalvik, reboot.
I've noticed that if you don't root, your device will be encrypted on first boot of beta 9 (which causes some issues in TWRP not being able to mount the /data partition and decryption passwords not working in TWRP.
Same problem here, **** broken OB9 update.
EDIT: For those with the same problem, download stock recovery from here, flash it using adb, boot into recovery (might say that installation of update failed, it did for me) and then reboot to system.
Now it booted successfully and says that I have Open Beta 9. TWRP and SuperSU installations worked just fine after that.
I used twrp-3.0.2-22 to reflash beta 9 all is well.
I have same problem with twrp-3.0.2-1.28. Just boot into bootloader and flash twrp-3.0.2-22.
Can I flash that twrp-3.0.2-22 after I'm already on beta 9?
Nevermind I saw that it encrypts on first boot. I'll just wait for root again until after the final comes out.
No need for clean installation like hw4ng3r said.
I'll copy my other post's edit here if someone needs it.
For those with the same problem, download stock recovery from here, flash it using adb, boot into recovery (might say that installation of update failed, it did for me) and then reboot to system.
Now it booted successfully and says that I have Open Beta 9. TWRP and SuperSU installations worked just fine after that.
Click to expand...
Click to collapse
Got 145849 AnTuTu result with OB9. Might be able to get a better result if I were to clean install, but I've just dirty flashed every update since 3.2.5.
karliyo said:
No need for clean installation like hw4ng3r said.
Click to expand...
Click to collapse
Very true.
I interpreted the OP's comment as:
1. Already on TWRP
2. Tried full wipe and install (all data lost anyways)
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
Tumpster said:
Can I flash that twrp-3.0.2-22 after I'm already on beta 9?
Nevermind I saw that it encrypts on first boot. I'll just wait for root again until after the final comes out.
Click to expand...
Click to collapse
I've read that .22 TWRP doesn't have decryption issues of the /data partition like .28 has, but don't take my word for it. And the encryption happened to me when I flashed Beta9 from TWRP .28 and rebooted system without flashing Super SU.
The decryption of the /data partition in TWRP seems to be an issue if the file system is F2FS on Beta 8 and Beta 9. I haven't had any issues with EXT4.
sibmon said:
Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
Click to expand...
Click to collapse
Download stock recovery from OnePlus site (on very bottom) ,flash it using fastboot and than sideload new beta 9
Tried to flash flash ob 10, but twrp said the zip was corrupted. I could not boot into the system anymore.
The problem is the system partition is ok ( verified from twrp file manager), but every time I choose reboot system, it will go back to twrp. I tried to re-flash ob 9, but twrp again reported another error. Log is attached. How should I solve the problem?
By the way, I wipe all data, including storage in twrp by mistake. Is there any way to recover the data? I am traveling now, just got several hundred pictures.:crying::crying: It seems to be impossible to do it on a computer in MTP mode, but I could not boot into the system neither.
Download the modded twrp from here and install it. Use it to flash community builds and all other roms from now on.
About the file recovering part, I wouldn't know.
You need to flash stock recovery, ADB sideload the official Open Beta, and boot into ROM.
By any chance, did you trigger an OTA update with TWRP installed?
zTweaked said:
Download the modded twrp from here and install it. Use it to flash community builds and all other roms from now on.
About the file recovering part, I wouldn't know.
Click to expand...
Click to collapse
I am always using the modified one. I am encountering a weird error.
The message is like
'E: unknown command [log]
........
script succeeded: result was [1.000000]'.
Update: flashing stock recovery seems to be effective ( of course, twrp does not exist anymore ).
SoybeanYoung said:
I am always using the modified one. I am encountering a weird error.
The message is like
'E: unknown command [log]
........
script succeeded: result was [1.000000]'.
Click to expand...
Click to collapse
Unknown command is a known and harmless issue on all 7.x.x roms. Just ignore it and go ahead.
And I think I saw 3.0.2-1 twrp version in your log.
---------- Post added at 09:20 AM ---------- Previous post was at 09:18 AM ----------
pmbabu said:
You need to flash stock recovery, ADB sideload the official Open Beta, and boot into ROM.
By any chance, did you trigger an OTA update with TWRP installed?
Click to expand...
Click to collapse
Open Beta builds can be flashed via modded twrp, no need to use stock recovery and adb sideloading. Plus even if he installed an OTA update, it won't get installed on twrp ~ and no harm will be done.
After you flash any rom, reflash recovery. Reboot to RECOVERY & then to system.
The red message it's on almoust every Nugat rom. And it's about some log .
zTweaked said:
Open Beta builds can be flashed via modded twrp, no need to use stock recovery and adb sideloading. Plus even if he installed an OTA update, it won't get installed on twrp ~ and no harm will be done.
Click to expand...
Click to collapse
He said he could only boot into twrp. That occurs (reboot to system will take it back to twrp over and over) only if someone tried an OTA update with twrp.
I don't think this is the case for you, but if you tried the other suggestions don't work try the below. I had a similar issue and found that my recovery partition was corrupted. However, an additional symptom I had was that my TWRP would hang completely when selecting reboot after any successful flash. I think modded TWRP does not like internal storage wipe from within TWRP (rather than through fastboot format userdata).
Boot to fastboot
Fastboot erase recovery
Fastboot flash recovery filename.img
Boot to recovery and flash your desired ROM+supersu which you can sideload via MTP (drag and drop from Windows) or adb push C:\SourceLocation\filename.zip /sdcard
I recommend ADB push over MTP.
Had the exact same problem as op, after some issues i was forced to use the unbrick method to get phone back as it wasn't even booting. Now im using beta 10 perfectly.
Did you manage to fix it? I have the same probem.
Hello,
I am having a problem where my phone is only, as far as I can tell, willing to boot into recovery. From the system, doing a normal reboot ends up in recovery, from powered off it goes into recovery, rebooting from recovery to system ends up back in the recovery, and the fastboot menu's "Continue" option goes reboots to recovery. The only way I can get into the system is to boot via fastboot -- i.e.,
Code:
fastboot boot boot.img
Where boot.img is the one packaged with the rom I am currently running.
This is not convenient because I need to connect it to a computer!
Is there some way to tell the bootloader to not boot recovery by default?
I have tried simply flashing the boot.img from above with:
Code:
fastboot flash boot boot.img
Which doesn't have any noticeable effect.
I suspect I broke something last night kicking around. I flashed the Open Beta 10 Modem & Firmware, then flashed the Open Beta 10 recovery, before changing my mind and installing TWRP 3-28 and Resurrection Remix v5.8. Somewhere in there, fastboot -w got run, but I don't think I did anything else potentially destructive.
Thanks for reading!
Hmm... Try install boot into recovery partition and recovery into boot? I know it's sound like a joke, but it will probably help you while u wait for a beter solution or just solution to repair that problem.
Anyway - maybe try flash old MM firmware?
A solution for me...
For anyone who rolls along and sees this in the future, my fix was:
0. Take a backup of sdcard AND data -- Step 2 will wipe data and sdcard without asking
1. Download the official recovery for the OnePlus 3
2. Use fastboot to boot (I didn't even have to flash) the official OnePlus 3 recovery AGAIN: WARNING: This step wipes all data without asking for confirmation!!!
I have now installed TWRP-3.0.4.0 and Resurrection Remix v5.8.1-20170202 and everything seems to be working just fine.
Thanks to @sylviohneto for finding this fix here: https://forum.xda-developers.com/oneplus-3/help/critical-bootloader-boot-recovery-fresh-t3530283
I had same problem so for that just take nandroid backup of data and while in turn copy it to pc and any other backup of data you need then format all the partions and reinstall rom and restore data... And if your lock screen have security then check Google you will have to delete a file called locscreen.db from file manager in twrp to access your phone
hi,
my oneplus 3 has been rote since i got it (i bought it on launch day) but since i updated it to the beta 19, my phone is no longer rooted : when i put the phone in fastboot it says that my bootloader it unlocked but all the apps who requier root are saying that the phne is not rooted and i cant get twrp to work. i tryied with the official app on my phone and with a program called "tool all in one" (https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3398993) and when i flash twrp from the program, i can boot into twrp but then i can't access my files and after i boot the phone, i can no longer boot to twrp
does anyone have a solution that doesn't involve me wiping the phone?
You loose root after updating. Try installing twrp again and then rooting it. Use the toolkit for oneplus 3. Simplifies the process
what do you mean by "then rooting it" ?
the program i use does the same thing as the toolkit and when i install twrp, as i said, it can boot on twrp one time and in twrp i can't access my files and after i boot the phone i can't get back to twrp ,i get the stock recovery
Unless your ROM has built-in root, after flashing TWRP, you have to flash SuperSU or Magisk to obtain root. Mere flashing of TWRP will not give you root.
I know but i can't get to the folder when the magisk file is : when in boot into twrp i cant see my files
Few details... it's quite difficult to help you.
What's the root method? Magisk, SuperSU or Kingroot? Which version?
Ps TWRP recovery is not depending by root, you just need to unlock bootloader (surely it's already unlocked) and flash the same recovery, from PC, via the command "fastboot flash recovery filename.img".
Now enter in TWRP:
1) Wipe /system and /cache;
2) Flash another time Open Beta 19;
3) Flash Magisk or SuperSU (be sure to have latest release);
4) Move TWRP img file from computer to device, then flash it another time (because firmware provides the OOS stock recovery);
5) Reboot and wait 5-10 minutes, because of cache rebuilding.
Tell me if you solve
I am using magisk
Yes my bootloader is unlocked
My problem is that when i flash twrp i cant access my files so i don't want to wipe system if i cant reflash something after
I think that I'll wait for the next update, maybe then it will work
But thank you for your help
Which version of TWRP do you have? Try eng.stk's latest version.
I tryied 3.1.1-2
The eng.stk is not available anymore
Your phone is encrypted, so you have to format data ( but your internal storage wiped by formating data, so back it up ,then only twrp read files in your storage)and flash custom kernel then boot restore backup .
how do you know that my phone is encrypted? i never encrypted it
i use titanium backup so i can't back my phone up until i get rot back
Whenever you flash stock ROM it encrypt if you boot into system directly . So twrp could not read internal storage. Whenever you flash stock ROM you must flash custom kernel or any other method to avoid encryption. This is happened to me and what I'd done is flash custom kernel before boot into rom
To save your data try this
https://forum.xda-developers.com/oneplus-3/how-to/unencrypt-oxygenos-loosing-data-t3412228
Who said that? Check this: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Edit: If you want to save items in internal storage, you can use ADB commands instead of TWRP. You can also simply copy and paste if your PC recognises the internal storage of your phone.
I succeeded but i had to clean everything and use the last backup i made a week ago
Thank you all for your help