Related
Here is how you fix it.
Step 1. download OnePlus3t toolkit (note: don't attach the phone to PC yet)
step 2. reboot your phone into bootloader (if in twrp hit restart -> bootloader) if not in twrp try turning phone on and as you see the oem unlock screen hit volume up and down and choose fastboot (or bootloader)
step 3. open oneplus3t toolkit
step 4. choose option 8 (flash stock recovery)
step 5. hit enter and when it says waiting 4 devices attach your device to pc
step 6. let it finish
step 7. when recovery comes up, hold power button for 10 seconds or hit exit (if you can choose it) and reboot into system
step 8. if it keeps rebooting into a stock recovery and you cant decrypt... then when your phone first boots and goes into oem-unlock error hit volume up and click restart.
step 9. Reflash TWRP and SuperSU if needed
Step 10. Enjoy!
Did not work for me. Stock recovery, stock nougat, locked bootloader and I still have dm-verity error.
Skwerl23 said:
Here is how you fix it.
Step 1. download OnePlus3t toolkit (note: don't attach the phone to PC yet)
step 2. reboot your phone into bootloader (if in twrp hit restart -> bootloader) if not in twrp try turning phone on and as you see the oem unlock screen hit volume up and down and choose fastboot (or bootloader)
step 3. open oneplus3t toolkit
step 4. choose option 8 (flash stock recovery)
step 5. hit enter and when it says waiting 4 devices attach your device to pc
step 6. let it finish
step 7. when recovery comes up, hold power button for 10 seconds or hit exit (if you can choose it) and reboot into system
step 8. if it keeps rebooting into a stock recovery and you cant decrypt... then when your phone first boots and goes into oem-unlock error hit volume up and click restart.
step 9. enjoy!
Click to expand...
Click to collapse
Can TWRP be installed afterwards or will it come back when TWRP is installed?
Michalko5896 said:
Did not work for me. Stock recovery, stock nougat, locked bootloader and I still have dm-verity error.
Click to expand...
Click to collapse
Try flashing TWRP and back to stock recovery.
If all keeps happening you may need to follow the guide to unbrick the phone.
I'd personally keep flashing different things if data is important. Sorry to hear this happened. Sounds like dm-verity should never have been a thing. So frustrating. Please update us on what you find. You can always erase system and all then reflash image.
Skwerl23 said:
Try flashing TWRP and back to stock recovery.
If all keeps happening you may need to follow the guide to unbrick the phone.
I'd personally keep flashing different things if data is important. Sorry to hear this happened. Sounds like dm-verity should never have been a thing. So frustrating. Please update us on what you find. You can always erase system and all then reflash image.
Click to expand...
Click to collapse
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
I feel your frustration. There is this forum
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Michalko5896 said:
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
Click to expand...
Click to collapse
Go to TWRP>Wipe>Advanced Wipe>Select system>Repair or change file system>Change filesystem>EXT4>Flash your ROM
That fixed it for me
Michalko5896 said:
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
Click to expand...
Click to collapse
I used the hard brick fix to go back to 3.5.1? I let the system update to 3.5.4. Go into developer settings and check allow oem unlock. Went into bootloader and oem unlocked. It will erase everything. Downloaded and put the OTA patch(940gb~not full) and supersu 2.79 on the device somewhere and did a local update with the patch through stock recovery. Went into bootloader and flashed TWRP 3.0.2.0(not 3.0.3.0). Do not exit bootloader. In bootloader I fastboot BOOT the 3.0.2.0 TWRP(3.0.3.0 would not boot up and screwed the dm-verity). If it(3.0.2.0) doesn't want to boot then quickly hold the power button in and wait till it starts rebooting and go into recovery menu option). Swipe to allow modifications and flash the supersu 2.79 that was placed on the device somewhere. This worked for me and no dm-verity error with f2fs.
Long process but it worked.
does dm-verity error mean anything? I have it also currently but nougat seems to be running fine...
PaKii94 said:
does dm-verity error mean anything? I have it also currently but nougat seems to be running fine...
Click to expand...
Click to collapse
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
card13 said:
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
Click to expand...
Click to collapse
I see thanks. I guess it doesn't matter to me cause I haven't started using android Pay and since I'm rooted currently
What causes the dm-verity issue in the first place?
guys if my device is unlocked will i still get the ota updates?
how about root ? if my device rooted willi still get ota updates?
saberzaid said:
guys if my device is unlocked will i still get the ota updates?
how about root ? if my device rooted willi still get ota updates?
Click to expand...
Click to collapse
Yes to first. No to second, It will try but will fail.
Sent from my ONEPLUS A3000 using Tapatalk
Mine is unlocked and rooted. The update failed. Then it redownloaded the full 1.4gb. That's how I found the URL. Then it flashed fine but brought recovery to stock and wiped root. Had to use the toolkit to get TWRP and root back.
So yes, even rooted gets the update
noahvt said:
Go to TWRP>Wipe>Advanced Wipe>Select system>Repair or change file system>Change filesystem>EXT4>Flash your ROM
That fixed it for me
Click to expand...
Click to collapse
I did a system restore previously and it set system to ext4. Maybe that's why I didn't have issues.
This dm-verity issue could be showing the instability of f2fs. Hmmm
Hello, just reset original rom under 6.0.1 and the problems and then twrp then flash rom custom
jejemc said:
Hello, just reset original rom under 6.0.1 and the problems and then twrp then flash rom custom
Click to expand...
Click to collapse
Hi guy, I followed your instruction, however, it still has the problem.
When I use the stock recovery to flash the beta1 package, it could not be flashed in.
lanbingxuanyi said:
Hi guy, I followed your instruction, however, it still has the problem.
When I use the stock recovery to flash the beta1 package, it could not be flashed in.
Click to expand...
Click to collapse
Hello, I am going under the beta with the message in red dm-verity for the removed I returned under original rom then I handed twrp then rom custom
card13 said:
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
Click to expand...
Click to collapse
PaKii94 said:
I see thanks. I guess it doesn't matter to me cause I haven't started using android Pay and since I'm rooted currently
Click to expand...
Click to collapse
I'm running 7.0 stable, unlocked bootloader and dm-verity warning. Android Pay still functions with the workaround.
Since the May Security Update, there have been changes.
I won't get into that here, as there are already a number of threads where the new AVB process and what it means for updates and root is discussed at length on this forum.
For example - https://forum.xda-developers.com/an...-boot-images-android-verified-t3600606/page16
I'm just going to outline my process for installing the new security updates via full image (Not OTA) and then rooting the phone via TWRP.
A few things to bear in mind first.
You will need to have the following:
0. Know how to use ADB/Fastboot and have them installed. If not, you should please do some research first.
1. Full Image for Pixel (https://developers.google.com/android/ota)
2. TWRP boot image and zip files (https://dl.twrp.me/sailfish/)
3. Latest SuperSU by Chainfire (https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip)
4. VerifiedBootSigner by Chainfire (https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606)
Also...I don't make use of the vendor provided flashing scripts, I simply use the script commands and eliminate the '-w' flag manually.
*The SuperSu, TWRP and VerifiedBootSigner zips need to be saved to your phone*
From the bootloader ->
fastboot flash bootloader bootloader-sailfish-8996-012001-1704121145.img
fastboot reboot-bootloader
fastboot flash radio radio-sailfish-8996-012901-1702171013.img
fastboot reboot-bootloader
fastboot update image-sailfish-njh47b.zip
***The phone will automatically reboot at this phase and you will need to reboot back into the bootloader to continue either by manual means or by using "adb reboot-bootoader"
fastboot boot twrp-3.0.2-0-RC1-fastboot-sailfish.img
from TWRP (using files saved on phone) ->
TWRP install twrp-pixel-installer-sailfish-3.1.0-0RC2.zip
reboot TWRP
TWRP install SR3-SuperSU-v2.79-SR3-20170114223742.zip
TWRP install VerifiedBootSigner-v8.zip
reboot system
Edit - You should also update your SuperSU binary to 2.82 from within the app once you're booted into Android.
You're Done!
DISCLAIMER
I didn't create any of these files or take credit for them in anyway. This is simply an instructional that I hope will help many of you.
It requires some proficiency in using fastboot and TWRP.
If you don't know what you're doing and mess up your device, I take no responsibility for your actions or the results.
gonna give it a try, thanks dude.
The only issue is that after updating the system image the phone will auto reboots so you have no chance to input the fastboot command.
churchmice said:
The only issue is that after updating the system image the phone will auto reboots so you have no chance to input the fastboot command.
Click to expand...
Click to collapse
You're right.
I should update the instructions about that.
The reboot isn't really an issue, but it does add an additional step and some inconvenience.
churchmice said:
The only issue is that after updating the system image the phone will auto reboots so you have no chance to input the fastboot command.
Click to expand...
Click to collapse
phonepersonality said:
You're right.
I should update the instructions about that.
The reboot isn't really an issue, but it does add an additional step and some inconvenience.
Click to expand...
Click to collapse
fastboot has an option to skip reboot:
--skip-reboot
so the command would be something like: fastboot --skip-reboot update image-sailfish-njh47b.zip
Can't we just use ota? Like:
- sideload ota
- let reboot
- reboot bootloader
- boot twrp rc1
- flash twrp rc1
- flash bootloader signer
- reboot recovery
- flash root
- optional kernel
- flash bootloader signer
- reboot
I ask because I always did this and never got problems, so if anyone tried/wanna try just let me know
TENN3R said:
Can't we just use ota? Like:
- sideload ota
- let reboot
- reboot bootloader
- boot twrp rc1
- flash twrp rc1
- flash bootloader signer
- reboot recovery
- flash root
- optional kernel
- flash bootloader signer
- reboot
I ask because I always did this and never got problems, so if anyone tried/wanna try just let me know
Click to expand...
Click to collapse
If you'd like.
I don't like to use the OTA files, personally.
Will the OTA even work with root ? I thought OTA is like taking the update over the air and if the system files are altered it fails ? I recently re-flashed the stock image but I may try this next time. The Pixel has become more difficult to update and in the past when I have even tried to reflash the stock boot it starts wiping my phone.
mikeprius said:
Will the OTA even work with root ? I thought OTA is like taking the update over the air and if the system files are altered it fails ? I recently re-flashed the stock image but I may try this next time. The Pixel has become more difficult to update and in the past when I have even tried to reflash the stock boot it starts wiping my phone.
Click to expand...
Click to collapse
That is weird. Never had a problem with my phone being wiped except when flashing other than manually. I always flash mine one at a time, and never have a problem. I like to be in control but I am old lol! I've been wiped before.
Tulsadiver said:
That is weird. Never had a problem with my phone being wiped except when flashing other than manually. I always flash mine one at a time, and never have a problem. I like to be in control but I am old lol! I've been wiped before.
Click to expand...
Click to collapse
I did manual fastboot commands earlier, not the autoscript, automatically wiped my data.
---------- Post added at 05:43 PM ---------- Previous post was at 05:31 PM ----------
Not sure what happened. Just pretty much treated like a dirty flash and fastboot flash the image. It must have detected the prior and wiped it. Had the thing rooted which is the only thing I can think of, it was not untouched stock.
mikeprius said:
Will the OTA even work with root ? I thought OTA is like taking the update over the air and if the system files are altered it fails ? I recently re-flashed the stock image but I may try this next time. The Pixel has become more difficult to update and in the past when I have even tried to reflash the stock boot it starts wiping my phone.
Click to expand...
Click to collapse
You can update via ota, but you need to download the zip on your pc and sideload it in twrp. After booted up you can re-mod, keeping your data.
Have you deleted the "-w" near the fastboot command in the factory image "flash-all" file? This causes wipe, if you remove it'll skip wipe.
Did anyone else have to install the TWRP 3.1 zip via USB-OTG? After flashing the full factory image for June 2017, rebooting to system, rebooting to bootloader then running fastboot boot twrp3.0.2-RC1.img, I wasn't prompted to enter my password so my user data remained encrypted and I couldn't install the TWRP 3.1 zip from the internal SD card, had to load it on a usb dongle and mount USB-OTG storage.
TENN3R said:
You can update via ota, but you need to download the zip on your pc and sideload it in twrp. After booted up you can re-mod, keeping your data.
Have you deleted the "-w" near the fastboot command in the factory image "flash-all" file? This causes wipe, if you remove it'll skip wipe.
Click to expand...
Click to collapse
I've tried to take out the -w erase flag. I've also tried to reflash the stock boot in the past when reloading a new kernel. Not sure if it is triggering some kind of system default but it just auto wipes. It's not the end of the world, I have everything backed up, I just have to restore everything. Just have not had any luck
Guys I can confirm also sideload ota method works flawlessly, 7.1.2 june rooted
Does anyone know if once rooted and bootloader signed via this method Netflix becomes available again?
Coronado is dead said:
Does anyone know if once rooted and bootloader signed via this method Netflix becomes available again?
Click to expand...
Click to collapse
A phone setup according to this thread is not expected to pass the Safetynet check. I've been updating with SuperSU using FlashFire, and my phone just shows Netflix VR in the Play Store. The Magisk discussions are primarily the threads that have been active recently for having root and passing Safetynet.
Pixel discussion:
https://forum.xda-developers.com/pixel/how-to/magisk-pixel-t3573845
Pixel XL discussion:
https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
TENN3R said:
You can update via ota, but you need to download the zip on your pc and sideload it in twrp.
Click to expand...
Click to collapse
Could you please elaborate on how to sideload in TWRP? I used to use adb sideload, but maybe your method is easier.
My current steps are:
1) adb reboot recovery
2) adb sideload ota-update.zip
3 Reboot and check if everything is okay (root and TWRP are lost, data are not)
4) adb reboot bootloader
5) fastboot boot TWRP.img
6) Flash TWRP and SuperSU
7) Flash boot signer
8) Reboot
Flitskikker said:
Could you please elaborate on how to sideload in TWRP? I used to use adb sideload, but maybe your method is easier.
My current steps are:
1) adb reboot recovery
2) adb sideload ota-update.zip
3 Reboot and check if everything is okay (root and TWRP are lost, data are not)
4) adb reboot bootloader
5) fastboot boot TWRP.img
6) Flash TWRP and SuperSU
7) Flash boot signer
8) Reboot
Click to expand...
Click to collapse
I use the same method I don't think there are any others
TENN3R said:
I use the same method I don't think there are any others
Click to expand...
Click to collapse
Thanks for confirming.
Does this VerifiedBootSigner-v8.zip apply to the August security patch as well?
Hello everyone. I am trying to update to October 2017 OTA. Everytime it returns error "Installation problem".
Is this because my phone has a modified bootloader? Perhaps its because I have rooted it? How can I get OTA updates again?
I'm having the same issue. Thought it was because of root but I restored the stock boot.img and no longer rooted but still getting 'Installation Problem' whenever i try to update.
jhorner said:
I'm having the same issue. Thought it was because of root but I restored the stock boot.img and no longer rooted but still getting 'Installation Problem' whenever i try to update.
Click to expand...
Click to collapse
you should also lock the bootloader for ota to work, i dont have mi a1 yet, but on nexus 6 it worked that way
Note to self, re-locking the bootloader will brick your phone
jhorner said:
Note to self, re-locking the bootloader will brick your phone
Click to expand...
Click to collapse
Not on this device... Done many times
Need to be unrooted and stock recovery. Unlocked BL is fine. Switch partition and start device for ota. Then reroot
Chris_Cheekyz said:
Not on this device... Done many times
Click to expand...
Click to collapse
Hmm. I just did 'fastboot oem lock' and after rebooting it says 'The system has been destroyed'
jhorner said:
Hmm. I just did 'fastboot oem lock' and after rebooting it says 'The system has been destroyed'
Click to expand...
Click to collapse
If you are rooted, your phone won't work if you try to lock bootloader. Unroot first and try again
First install stock ROM via MiFlashTool and then update..
It'll definitely work!
matcho13579 said:
If you are rooted, your phone won't work if you try to lock bootloader. Unroot first and try again
Click to expand...
Click to collapse
Just for context, this was the process
1. Tried to update w/o any changes, it failed
2. Unrooted, confirmed w/ SuperSU and tried to update, it failed
3. Locked bootloader via 'fastboot oem lock' and when the device rebooted, it gave the 'system destroyed' message
jhorner said:
Note to self, re-locking the bootloader will brick your phone
Click to expand...
Click to collapse
relocking bootloader dons'nt brick my phone
i have done this using this cmd - fastboot oem lock
and its works perfact
but do this at your own risk
:good::good::good:
Most ota installations failed is because system partition has been compromised. Even if you just mount it rw. You'll need to reflash system img for both system_a and system_b partition.
Restore stock boot.img if your using root (I'm using magisk) install ota and reroot. For magisk, starting from 14.4,you can follow the ota instructions for magisk, basically mi a1 the same as the pixel but not as strict. Locking and unlocking bootloader will not brick or wipe data for mi a1.
jhorner said:
Just for context, this was the process
1. Tried to update w/o any changes, it failed
2. Unrooted, confirmed w/ SuperSU and tried to update, it failed
3. Locked bootloader via 'fastboot oem lock' and when the device rebooted, it gave the 'system destroyed' message
Click to expand...
Click to collapse
Damn.
I've tried to remove root. Removed SuperSu. Flashed stock bootloader - but update continues to fail.
I'll just wait for Oreo then do a full flash
Even i got the same error
What i did was,
Removed Magisk
Flashed latest rom by mi flash with save user data option
Then update ur device, it will work for sure!
Monthly security updates installation problem,how to fix that? Please throw some lights
GSAA RAIN said:
Monthly security updates installation problem,how to fix that? Please throw some lights
Click to expand...
Click to collapse
You should post some information on your phone. Is it stock/rooted? Did you unlock bootloader and install TWRP? What modifications have you done to the phone (if any?)
cheesekun27 said:
Damn.
I've tried to remove root. Removed SuperSu. Flashed stock bootloader - but update continues to fail.
I'll just wait for Oreo then do a full flash
Click to expand...
Click to collapse
You can use miflash and flash the full rom so you are back at stock, just make sure you select the option to save user data so it does not wipe your phone clean.
I have the same problem...what i did was unlocking the bootloader and tried to install themes via substratum and andromeda...but that didn't worked so i uninstalled both and relocked the bootloader. I didn't even rooted the phone but getting the same error. Is this because somehow partition was compromised and can someone please provide me a brief description of rooting this phone and usage of magisk?
Angelictears said:
Most ota installations failed is because system partition has been compromised. Even if you just mount it rw. You'll need to reflash system img for both system_a and system_b partition.
Restore stock boot.img if your using root (I'm using magisk) install ota and reroot. For magisk, starting from 14.4,you can follow the ota instructions for magisk, basically mi a1 the same as the pixel but not as strict. Locking and unlocking bootloader will not brick or wipe data for mi a1.
Click to expand...
Click to collapse
In short one needs to flash the stock rom using mi flash tool right?
---------- Post added at 06:43 AM ---------- Previous post was at 06:42 AM ----------
Angelictears said:
Most ota installations failed is because system partition has been compromised. Even if you just mount it rw. You'll need to reflash system img for both system_a and system_b partition.
Restore stock boot.img if your using root (I'm using magisk) install ota and reroot. For magisk, starting from 14.4,you can follow the ota instructions for magisk, basically mi a1 the same as the pixel but not as strict. Locking and unlocking bootloader will not brick or wipe data for mi a1.
Click to expand...
Click to collapse
thakurvishwendra said:
I have the same problem...what i did was unlocking the bootloader and tried to install themes via substratum and andromeda...but that didn't worked so i uninstalled both and relocked the bootloader. I didn't even rooted the phone but getting the same error. Is this because somehow partition was compromised and can someone please provide me a brief description of rooting this phone and usage of magisk?
Click to expand...
Click to collapse
Were you able to solve your problem?
Couldn't update Installation problem
Rohit Surya said:
Even i got the same error
What i did was,
Removed Magisk
Flashed latest rom by mi flash with save user data option
Then update ur device, it will work for sure!
Click to expand...
Click to collapse
I did thi but problem is still same installation problem
---------- Post added at 04:23 PM ---------- Previous post was at 04:20 PM ----------
goofball2k said:
You should post some information on your phone. Is it stock/rooted? Did you unlock bootloader and install TWRP? What modifications have you done to the phone (if any?)
Click to expand...
Click to collapse
Nothing yet I am facing the installation problem
Dear all,
first of all I would like to be sorry if I'm saying something worng. I'm not so expert about Android world.
I've got a OnePlus 6T that I've rooted with the help of a friend some months ago.
Not it's a lot that I keep see the notification abount the OS update and I keep skipping it but it's bothering me so... I searched for a guide and I found this (https://oneplus.gadgethacks.com/how...thout-losing-root-no-computer-needed-0192638/) (I hope I can post it also if it's from another website).
It seems so simple, I've downloaded the OTA update, the TWRP and the Magisk. My issue is that whene I reboot to the recovery I'm not booting into TWRP but I suppose into the OnePlus recovery instead.
I searched angain and found this other guide (https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953) that is more complete but I can't understand if it's the proper guide I need to follow to update my device keeping it rooted and most of all without loosing any data.
Thanks,
Riki
The first guide you linked to is wrong. Do not follow that. That is why you don't have TWRP anymore. The second guide you linked to on XDA is correct. Follow the TWRP guide. Once you have TWRP reinstalled.
You must download the zip from the second link you posted here at XDA.
Flash the Zip in TWRP. This flash the update to the opposite slot. It also wipes out TWRP and replaces it with the stock recovery.
Now you must reinstall TWRP. Flash the TWRP installer. This will flash TWRP to both slots.
Now reboot to recovery. This will reboot to the new slot where you update was just flashed.
This is when you install Magisk to the updated slot. You MUST do this.
Now reboot to system after you installed Magisk.
Now you have updated without losing any data.
The guide in the second link says to use the Magisk uninstaller. I've personally never done this. This is probably for people who use all sorts of weird add-ons and such. I don't know. Never uninstalled Magisk, never had a problem. That's all I can say. You can try it, or you can follow the official instructions.
OhioYJ said:
The first guide you linked to is wrong. Do not follow that. That is why you don't have TWRP anymore. The second guide you linked to on XDA is correct. Follow the TWRP guide. Once you have TWRP reinstalled.
You must download the zip from the second link you posted here at XDA.
Flash the Zip in TWRP. This flash the update to the opposite slot. It also wipes out TWRP and replaces it with the stock recovery.
Now you must reinstall TWRP. Flash the TWRP installer. This will flash TWRP to both slots.
Now reboot to recovery. This will reboot to the new slot where you update was just flashed.
This is when you install Magisk to the updated slot. You MUST do this.
Now reboot to system after you installed Magisk.
Now you have updated without losing any data.
The guide in the second link says to use the Magisk uninstaller. I've personally never done this. This is probably for people who use all sorts of weird add-ons and such. I don't know. Never uninstalled Magisk, never had a problem. That's all I can say. You can try it, or you can follow the official instructions.
Click to expand...
Click to collapse
Thanks OhioYJ,
so, before I can follow the TWRP guide, I must reinstall it. Could you please give me a link to a guide on how to do it?
Thanks again,
Riki
RikiBez said:
Thanks OhioYJ,
so, before I can follow the TWRP guide, I must reinstall it. Could you please give me a link to a guide on how to do it?
Click to expand...
Click to collapse
[Guide] OnePlus 6T [Fajita]: Unlock | Flash TWRP | Root | Nandroid & EFS Backup !!
Thanks to Funk Wizard again. Don't forget the section about backing up your modem, this is always important in case something really goes wrong. You'll probably never need it, but if you ever do you'll be really glad you have it.
OhioYJ said:
[Guide] OnePlus 6T [Fajita]: Unlock | Flash TWRP | Root | Nandroid & EFS Backup !!
Thanks to Funk Wizard again. Don't forget the section about backing up your modem, this is always important in case something really goes wrong. You'll probably never need it, but if you ever do you'll be really glad you have it.
Click to expand...
Click to collapse
I followed the guide but I get stucked into a loot without been able to boot into TWRP. I'm only able to enter the recovery mode and the fastboot mode but when I launch the command from Windows it finish with no error but the phone still stuck on the fastboot logo or the oneplus logo. After many tryes now I've got only this and also errors on PC:
Old_video_link_removed
EDIT: At the moment I'm not event able to enter the recovery mode, I keep restarting it and it will only boot to the fastmode.
RikiBez said:
I followed the guide but I get stucked into a loot without been able to boot into TWRP. I'm only able to enter the recovery mode and the fastboot mode but when I launch the command from Windows it finish with no error but the phone still stuck on the fastboot logo or the oneplus logo. After many tryes now I've got only this and also errors on PC:
https://youtu.be/7Re-p7Z1yhc
EDIT: At the moment I'm not event able to enter the recovery mode, I keep restarting it and it will only boot to the fastmode.
Click to expand...
Click to collapse
It's booting into recovery, but the OnePlus recovery. That is what the menu that is asking you to select a language is. When you enter the command fastboot boot trwp.img you don't get any sort of error? Or the phone doesn't respond?
OhioYJ said:
It's booting into recovery, but the OnePlus recovery. That is what the menu that is asking you to select a language is. When you enter the command fastboot boot trwp.img you don't get any sort of error? Or the phone doesn't respond?
Click to expand...
Click to collapse
At the beginning I had no error nor on PC not on phone. Now that I’m stuck into the fastboot I keep getting the error on windows that say he donno the fastboot command but the phone stand still.
RikiBez said:
At the beginning I had no error nor on PC not on phone. Now that I’m stuck into the fastboot I keep getting the error on windows that say he donno the fastboot command but the phone stand still.
Click to expand...
Click to collapse
Is fastboot installed? Are you typing the commands correctly?
Sent from my OnePlus 6T using XDA-Developers Legacy app
RikiBez said:
At the beginning I had no error nor on PC not on phone. Now that I’m stuck into the fastboot I keep getting the error on windows that say he donno the fastboot command but the phone stand still.
Click to expand...
Click to collapse
Sounds like you're not running the command from the folder where fastboot.exe is located.
Makes me wonder why you did it this way in the first place. And why people suggested it. Easiest way to install updates on a rooted 6T is to install the update through the normal updater without rebooting, going to Magisk Manager and selecting install to inactive slot and rebooting only after that. That's really all there is to it.
CazeW said:
Sounds like you're not running the command from the folder where fastboot.exe is located.
Makes me wonder why you did it this way in the first place. And why people suggested it. Easiest way to install updates on a rooted 6T is to install the update through the normal updater without rebooting, going to Magisk Manager and selecting install to inactive slot and rebooting only after that. That's really all there is to it.
Click to expand...
Click to collapse
If I want to clean flash my 9.0.13 rooted TWRP. What do I need to uninstall or wipe? Im on 9.0.13 currently
Sent from my OnePlus 6T using XDA-Developers Legacy app
i7vSa7vi7y said:
Is fastboot installed? Are you typing the commands correctly?
Sent from my OnePlus 6T using XDA-Developers Legacy app
Click to expand...
Click to collapse
Fastboot was working until I reinstalled adb and OnePlus drivers.
CazeW said:
Sounds like you're not running the command from the folder where fastboot.exe is located.
Makes me wonder why you did it this way in the first place. And why people suggested it. Easiest way to install updates on a rooted 6T is to install the update through the normal updater without rebooting, going to Magisk Manager and selecting install to inactive slot and rebooting only after that. That's really all there is to it.
Click to expand...
Click to collapse
I didn’t know any other way. That’s why I asked how to do it. Anyway I’m running the command from the right folder. Maybe something broke on my laptop.
Yesterday evening I tried from a new laptop windows 10, installed adb and OnePlus driver for the first time and I was able to run the commands without the error not finding the command but:
Fastboot boot twrp.image returned me an error
If I run fastboot flash boot twrp.image it does not give me error but the phone does not response. It only boot to the boot loader.
RikiBez said:
I didn’t know any other way. That’s why I asked how to do it. Anyway I’m running the command from the right folder. Maybe something broke on my laptop.
Yesterday evening I tried from a new laptop windows 10, installed adb and OnePlus driver for the first time and I was able to run the commands without the error not finding the command but:
Fastboot boot twrp.image returned me an error
If I run fastboot flash boot twrp.image it does not give me error but the phone does not response. It only boot to the boot loader.
Click to expand...
Click to collapse
Try uninstalling adb. Delete the whole folder and install it again. Try updating your netframework on your PC and the latest C++
Sent from my OnePlus 6T using XDA-Developers Legacy app
I'm creating a new tread about the issue and the state where I am because now I can't update or keep data, I just need to recover the phone to a normal state.
RikiBez said:
I'm creating a new tread about the issue and the state where I am because now I can't update or keep data, I just need to recover the phone to a normal state.
Click to expand...
Click to collapse
Use the msm tool for that
Sent from my OnePlus 6T using XDA-Developers Legacy app
Flashing the fastboot rom would probably have gotten you back in and maybe with your data in tact. Now fair warning I'm a Linux user anyways, but really fastboot and adb are so much easier in Linux. For people that have issues, it sometimes is easier just to make a bootable USB / CD of Linux Mint or Ubuntu and then from Synaptic or the Package manager install adb and fastboot. No drivers or anything else to install, everything will just work.
Last time I got stuck in fastboot I just used the fastboot ROM to get back to bootable.
OhioYJ said:
Flashing the fastboot rom would probably have gotten you back in and maybe with your data in tact. Now fair warning I'm a Linux user anyways, but really fastboot and adb are so much easier in Linux. For people that have issues, it sometimes is easier just to make a bootable USB / CD of Linux Mint or Ubuntu and then from Synaptic or the Package manager install adb and fastboot. No drivers or anything else to install, everything will just work.
Last time I got stuck in fastboot I just used the fastboot ROM to get back to bootable.
Click to expand...
Click to collapse
Those fastboot roms have sure saved me from raging before
I would also recommend using migrate, it's in the play store and it backs up all your data and then puts it in a flashable zip
i7vSa7vi7y said:
If I want to clean flash my 9.0.13 rooted TWRP. What do I need to uninstall or wipe? Im on 9.0.13 currently
Sent from my OnePlus 6T using XDA-Developers Legacy app
Click to expand...
Click to collapse
Do a factory reset from TWRP and flash the full ROM.
One best method...and the method that works 100% tested for upgrading a rooted OOS to new OOS version without any loss of data, without any issues.
I'll mention the guide that I have used to upgrade from 9.0.12 rooted to 9.0.13 rooted. Without any loss of data
Download latest OOS full ROM
Boot to TWRP
Flash OOS 9.0.13
Flash TWRP installer zip
Reboot system
Phone will boot.
Now go back to recovery mode
Flash Magisk if u want root again
Done
No confusion. No data loss. Not being stuck. Sweet and Simple.
sanjeev7 said:
One best method...and the method that works 100% tested for upgrading a rooted OOS to new OOS version without any loss of data, without any issues.
I'll mention the guide that I have used to upgrade from 9.0.12 rooted to 9.0.13 rooted. Without any loss of data
Download latest OOS full ROM
Boot to TWRP
Flash OOS 9.0.13
Flash TWRP installer zip
Reboot system
Phone will boot.
Now go back to recovery mode
Flash Magisk if u want root again
Done
No confusion. No data loss. Not being stuck. Sweet and Simple.
Click to expand...
Click to collapse
So I don't have to wipe my system data or anything. I heard some people had the problem of getting stuck or that there was a red warning screen that popped up when booting, and I'm not talking about the bootloader message. I'm currently on 9.0.11. Also should I download the latest version of TWRP or should I use the one I'm using currently. Don't wanna mess anything up. Another guide I read said I should flash the oos rom, then TWRP, than magisk
A few days ago I updated my phone via TWRP, the process taken always worked:
1. Install firmware
2. Install decrypt.zip
3. Install Magisk
But this time, it didn't. After rebooting the phone, forced encryption started and after it was done, I found out that Magisk wasn't installed, on top of that, TWRP was replaced with the original recovery. Is there any way to re-root the phone?
Note: I have updated the phone in this manner a few times and nothing like this ever happened also, I tried reinstalling TWRP via fastboot, sins the bootloader is already unlocked, but got write errors, because of the forced encryption more than likely.
Are you sure you used the correct decrypt zip file ?
Tianhe said:
Are you sure you used the correct decrypt zip file ?
Click to expand...
Click to collapse
Yep, have used it in the past so i am sure it was the correct one.
User483901 said:
Yep, have used it in the past so i am sure it was the correct one.
Click to expand...
Click to collapse
There are different decrypt zips for Oreo & Pie. Also, there may be variations for different firmwares within the same version itself. Same goes for TWRP.
Tianhe said:
There are different decrypt zips for Oreo & Pie. Also, there may be variations for different firmwares within the same version itself. Same goes for TWRP.
Click to expand...
Click to collapse
Oh, didn't know that. But regardless, what does it matter what was used, I mean TWRP is no longer on the device so talking about which decrypt was used doesn't matter cuz it can't be used until TWRP is reinstalled which i think is impossible, cuz of the forced encryption, unless you know of a way.
User483901 said:
Oh, didn't know that. But regardless, what does it matter what was used, I mean TWRP is no longer on the device so talking about which decrypt was used doesn't matter cuz it can't be used until TWRP is reinstalled which i think is impossible, cuz of the forced encryption, unless you know of a way.
Click to expand...
Click to collapse
Encryption doesnt affect TWRP, the only drawback is that you cannot mount internal storage. However, if the TWRP version supports FDE natively then even that is possible. So encrypted devices can have TWRP recovery, you just need unlocked BL etc.
XDA
How to flash TWRP recovery in max Pro M1 without PC please help
@secreattecheme said:
How to flash TWRP recovery in max Pro M1 without PC please help
Click to expand...
Click to collapse
Is your phone bootloader unlocked?
I have never heard someone losing twrp by updating firmware. Perhaps you might have updated the rom which contained the stock recovery and hence replaced twrp. You can flash twrp again using fastboot. Remember that in order to remove encryption (since your phone has already encrypted the data) you'll have to format data from twrp and you'll lose all your data, even internal storage and twrp backups.
About decrypt.zip, there is a sequence of flashing it. It didn't always work for me though.
farhanshaikh671 said:
I have never heard someone losing twrp by updating firmware. Perhaps you might have updated the rom which contained the stock recovery and hence replaced twrp. You can flash twrp again using fastboot. Remember that in order to remove encryption (since your phone has already encrypted the data) you'll have to format data from twrp and you'll lose all your data, even internal storage and twrp backups.
About decrypt.zip, there is a sequence of flashing it. It didn't always work for me though.
Click to expand...
Click to collapse
No, I updated it by going to the Asus website and downloading the firmware update, have done the same with the Pie update and the one before it, edited the image file, so it can be flashed using TWRP and then did the steps in the OP.
Also, as said before i can't flash TWRP sins i get write errors in fastboot.