I was successfully able to install TWRP and LineageOS on my OnePlus3T. However, due to the bugs in LineageOS, I downloaded the latest (non-Beta) OxygenOS from the OnePlus website and flashed that back onto my phone. I didn't realize that this would remove TWRP and give me an error screen about dm-verity error (in red) during the boot process. I have tried many things to get rid of the dm-verity error and to put TWRP back on the device so that I can eventually move back to a custom ROM. However, I am unable to get rid of the dm-verity error and everytime I try to install TWRP, it gets stuck on the TWRP splash screen. Then, I have to hold down the power button to power off, power back on, re-encounter the red dm-verity error and I am back into OxygenOS.
How can I get rid of the dm-verity error and get TWRP back on my phone?
Try sideloading any OOS version 4.0.2 or below, then use the following commands in fastboot:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
This will reset dm-verity, remember to root or flash the no-verity zip after flashing TWRP or it will trip dm-verity again.
This will not work in OOS 4.0.3 or the latest open beta as OP has patched out those commands.
Anova's Origin said:
Try sideloading any OOS version 4.0.2 or below, then use the following commands in fastboot:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
This will reset dm-verity, remember to root or flash the no-verity zip after flashing TWRP or it will trip dm-verity again.
This will not work in OOS 4.0.3 or the latest open beta as OP has patched out those commands.
Click to expand...
Click to collapse
I can do that. However the latest version of the fastboot command does not allow for fastboot oem disable_dm_verity (assuming that this command runs from the PC and is executed against the phone via USB). For example, in command prompt, if I type fastboot help, there are no options for oem disable or oem enable.
oem disable_dm_verity doesn't show up in my fastboot prompt either when I enter "fastboot", but it was able to lock and unlock dm-verity when I used it a few weeks ago. I'm not entirely sure what version of fastboot I have, though are you sure the command was removed and not just hidden?
Anova's Origin said:
oem disable_dm_verity doesn't show up in my fastboot prompt either when I enter "fastboot", but it was able to lock and unlock dm-verity when I used it a few weeks ago. I'm not entirely sure what version of fastboot I have, though are you sure the command was removed and not just hidden?
Click to expand...
Click to collapse
I used it earlier today and it said that it is an unknown command. However, I attempted it against OOS 4.0.3. I don't think this should matter.
You could try using older versions of minimal adb and fastboot:
https://forum.xda-developers.com/showthread.php?t=2317790
Thanks. I will try an older version this evening and let's see what happens. I should be able to get OOS 4.03 correct? Is there a reason you are recommending OOS 4.02 and lower?
Oneplus patched out the fastboot oem lock/unlock commands in the OOS 4.0.3 update. The phone will refuse the commands outright, technically it was a vulnerability. I suspect that the reason your fastboot was unable to run the command was because the phone's firmware didn't recognize it, not because the commands were removed from fastboot.
Those commands will only work on OOS with firmwares from 4.0.2 or below.
You could flash only the 4.0.2 firmware without replacing the entire 4.0.3 ROM by using this guide, though I'm not sure if you can do it without TWRP.
After resetting dm-verity on an older version, you can dirty flash OOS 4.0.3 (or just the firmware if you followed the guide).
weaponG said:
IHowever, everytime I try to install TWRP, it gets stuck on the TWRP splash screen. Then, I have to hold down the power button to power off, power back on, re-encounter the red dm-verity error and I am back into OxygenOS.
How can I get rid of the dm-verity error and get TWRP back on my phone?
Click to expand...
Click to collapse
TWRP Is already flashed on your phone
You just have to wait a while as oxygen os uses f2fs system and it takes time to boot into twrp
For the dm verity error you can follow the guide which is mentioned above
But as the error does not affect any functionality of Rom it should not be bothered with
Thank you all for your help. I did wait out the TWRP splash screen for about 20 minutes and it didn't seem to make any difference. The resolution was to download and install OOS 4.02 via adb sideload and then perform the following commands: fastboot oem disable_dm_verity, fastboot oem enable_dm_verity. The sideload of OOS 4.02, itself, did remove the dm-verity error. However, I wanted to be sure and performed the fastboot oem commands. (As speculated earlier in this post, fastboot oem enable_dm_verity and fastboot oem disable_dm_verity are known and working commands against OOS 4.02, but NOT against OOS 4.03.) I was then able to install TWRP and am now running a version of CM which has been modded by Sultan. This is a very stable ROM and is exactly what I was looking for. The issues which I had with LineageOS do not occur in Sultan's ROM.
Related
This only works coming from KNX01R!
Edit, Camazza has found you can flash the stock 5.0.1 bootloader and sideload the update. See here http://forum.xda-developers.com/g-watch-r/development/manual-ota-update-root-t2969845
Download the update here http://android.clients.google.com/p....signed-lenok-LWX48P-from-KNX01R.149e0c34.zip
1. Root using tonu42's method here http://forum.xda-developers.com/g-watch-r/development/root-root-twrp-r-t2960511
2. After verifying you have root re install the stock recovery for 4.4w.2 from intersectRaven here http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964 (same command used during rooting).
3. Boot in the system and upload the update
adb push 149e0c34d0ab10d3e356d6301915dcc04552d9db.signed-lenok-LWX48P-from-KNX01R.149e0c34.zip /sdcard/update.zip
4. adb shell
5. cp /sdcard/update.zip /cache/update.zip
6. echo 'boot-recovery ' > /cache/recovery/command
7. echo '--update_package=/cache/update.zip' >> /cache/recovery/command
8. reboot recovery
9. Update installs
Thanks to tonu42 for root and intersectRaven for the stock boot.
Use at your own risk.
Does it remain rooted after the update ?
Would applying the update return the watch to stock? Including upgrading the bootloader and such?
I'm interested in manually updating, but I'd want the watch to be completely stock afterwards.
The bootloader and recovery are updated to stock, but, the device has still been oem unlocked so a fastboot oem lock command will need to be issued. This does remove the lock icon and the watch shows as locked, but, I don't know if lg can tell that is has been unlocked at one time. Root is lost after the update and will need to be reapplied.
nxt said:
Would applying the update return the watch to stock? Including upgrading the bootloader and such?
I'm interested in manually updating, but I'd want the watch to be completely stock afterwards.
Click to expand...
Click to collapse
superdave said:
The bootloader and recovery are updated to stock, but, the device has still been oem unlocked so a fastboot oem lock command will need to be issued. This does remove the lock icon and the watch shows as locked, but, I don't know if lg can tell that is has been unlocked at one time. Root is lost after the update and will need to be reapplied.
Click to expand...
Click to collapse
Yup, I knew that part so didn't ask. But I finally got it working (had issues flashing recovery, had to switch usb ports).
All is good now, thanks!
EDIT: Looks like SuperSU is still installed though (won't run)
Everything else seems stock, I even did oem lock/unlock a few times, recovery is stock
Between step 4 and 5 you need to type su
You'll lose root and I am working on a fix.
Sent from my A0001 using XDA Free mobile app
Why all this manipulations? Why not use ADB Sideload?
superdave said:
The bootloader and recovery are updated to stock, but, the device has still been oem unlocked so a fastboot oem lock command will need to be issued. This does remove the lock icon and the watch shows as locked, but, I don't know if lg can tell that is has been unlocked at one time. Root is lost after the update and will need to be reapplied.
Click to expand...
Click to collapse
I don't think LG cares as long as the lock icon is gone. I've already screwed up and sent them a G2 that was on older radios with TWRP installed, and they sent it back factory flashed to the latest firmware (ZVA at the time).
AntonChernov said:
Why all this manipulations? Why not use ADB Sideload?
Click to expand...
Click to collapse
I'd like to know as well, which method is better/safer, this or ADB sideload?
Adb does not work in Stock recovery that is why twrp is needed, . I am having the same issue with supersu crashing once booted. I have not had a chance to look at it yet. If you shell in and su before the phone boots su works fine though.
Actually there's a faster and safer way that does not involve rooting.
1) Unlock Bootloader
2) Flash 5.0.1 Stock Recovery
3) Enter recovery and sideload update (it works in the new recovery)
4) Profit
Nice, good catch. I'll add that to the first post.
Camazza said:
Actually there's a faster and safer way that does not involve rooting.
1) Unlock Bootloader
2) Flash 5.0.1 Stock Recovery
3) Enter recovery and sideload update (it works in the new recovery)
4) Profit
Click to expand...
Click to collapse
superdave said:
Nice, good catch. I'll add that to the first post.
Click to expand...
Click to collapse
I did the same as following and it's work for me:
recoveryll.bin => 5.0.1 Recovery http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964
1. adb reboot bootloader
2. fastboot oem unlock
3. fastboot boot recoveryll.bin
4. Select adb sideload then
adb sideload 149e0c34d0ab10d3e356d6301915dcc04552d9db.signed-lenok-LWX48P-from-KNX01R.149e0c34.zip
5. Done
6. Reboot to fastboot
7. fastbook oem lock
5.0.1 Recovery work with adb
kanzone said:
I did the same as following and it's work for me:
recoveryll.bin => 5.0.1 Recovery http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964
1. adb reboot bootloader
2. fastboot oem unlock
3. fastboot boot recoveryll.bin
4. Select adb sideload then
adb sideload 149e0c34d0ab10d3e356d6301915dcc04552d9db.signed-lenok-LWX48P-from-KNX01R.149e0c34.zip
5. Done
6. Reboot to fastboot
7. fastbook oem lock
5.0.1 Recovery work with adb
Click to expand...
Click to collapse
hey I am trying the same method:
ok, so I unlocked the bootloader, flashed the 5.0.1 recovery, then booted to recovery, selected the adb sideload (the watch now says "Now send the package you want to apply to the device with "adb sideload <filename>"..."
however, in CMD, adb devices is not returning anything. there is no 'new devices connected' sound in windows when removing/replacing the watch from the cradle.
can someone please tell me what am I doing wrong?
b0gd4n said:
hey I am trying the same method:
ok, so I unlocked the bootloader, flashed the 5.0.1 recovery, then booted to recovery, selected the adb sideload (the watch now says "Now send the package you want to apply to the device with "adb sideload <filename>"..."
however, in CMD, adb devices is not returning anything. there is no 'new devices connected' sound in windows when removing/replacing the watch from the cradle.
can someone please tell me what am I doing wrong?
Click to expand...
Click to collapse
adb version
make sure the adb version is > 1.0.32
kanzone said:
adb version
make sure the adb version is > 1.0.32
Click to expand...
Click to collapse
hey, nevermind, I did fastboot flash recovery, not adb boot recovery. I just did that, and I am now uploading the zip....exiting!
thanks!
So wait, the command to flash recovery is what exactly? I've seen 3 different commands on this very page. Also, we do it from the bootloader screen, right?
i am unlocked and rooted with twrp and everytime I try and fastboot the boot img. it says "remote image is not a boot image?
what the hell am i doing wrong?
I have also tried to fastboot a new recovery and I get the same thing?
Are you trying to restore the stock recovery? If so, you fastboot flash recovery recovery.img on the stock image.
cottageboy said:
i am unlocked and rooted with twrp and everytime I try and fastboot the boot img. it says "remote image is not a boot image?
what the hell am i doing wrong?
I have also tried to fastboot a new recovery and I get the same thing?
Click to expand...
Click to collapse
hi,
when I am trying to flash the recovery I get this error:
fastboot flash rcovery recoveryll.img
target reported max download size of 268435456 bytes
sending 'rcovery' (6634 KB)...
OKAY [ 0.312s]
writing 'rcovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.403s
adb version
Android Debug Bridge version 1.0.32
any idea?
do I need to flash the new boot.img before?
Hi - I was having big problems with a custom ROM, so I decided to try loading OOS 4.0.2.
I got the Oxygen O/S loaded, TWRP is installed, and SuperSU is installed and working.
However, I am now seeing a non-enforcing dm-verity error during bootup, where I never saw that before. One "Unsecure" amber warning during boot is too much, and now an additional dm-verity red warning is TWO much!
Is there an easy way to get rid of the dm-verity error?
Use these commands with fastboot:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
You'll need the andriod SDK from them to work
Evolution101 said:
Use these commands with fastboot:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
You'll need the andriod SDK from them to work
Click to expand...
Click to collapse
Thanks! That did the trick!
Hi
Have anyone faced this before? yesterday i updated the viper4android from magisk and when reboot i got stucked on bootloader warning, android wont boot. After few reboots and turn the phone off, it still the same. So i imagined doing a full wipe and clean install everything will make the device usable, BUT... it persist and now my device is somehow tethered. I cannot boot to android without fastboot commands or otherside i wil get stucked forever on bootload warning, some things i tried is flash magisk from 16.4 to 16.7, clean install rom, install only rom and gapps only, not flashing any external kernel.
crazy uh? now everytime i reboot or turn off the phone, i have to use fastboot to get into android, not aways I will have computer nearby to send:
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
fastboot reboot
I can get to twrp recovery and fastboot, maybe there is a fastboot commands to "untether" my phone?
Model: xt1802
Current flashed rom: xtended x9
Current kernel: arsenic r4 (early mount)
I dirty flashed a new version of xiaomi.eu stable build, and it caused TWRP to uninstall itself.
Whenever I hold power on and volume up it just goes to fastboot.
Now I tried reinstalling TWRP like I've done many times before, but it keeps throwing an error. The error I get is when trying to boot without flashing the img. When I do this, I get the error:
Code:
fastboot boot TWRP.img"
downloading 'boot.img'...
OKAY [ 1.609s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.675s
Anyone gotten any ideas on what could be going on here? I'm scared to try anything as my phone currently works, but I need TWRP back to update my phone to a different versions and to install the clock mod again.
Thanks!
Got it to load once, but now back to square one. Throwing same error.
Now when running the command fastboot reboot recovery it's saying
Code:
fastboot: usage: unknown reboot target recovery
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.
Try on a computer with a USB 2.0 port, or a different usb cable, had the same issue once
Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.
I have the same error. How can I fix this pls?
MrkoZino said:
I have the same error. How can I fix this pls?
Click to expand...
Click to collapse
Flash the latest official rom then start all over again. Follow the post above you about miflash.
Hello, I've had the same problem, then flashed latest dev rom via MiFlash and it booted, but now after I flash any custom ROM in TWRP i have this issue again and need to reflash chinese ROM. How can I flash any custom rom?
i'm stuck in the same issue. stuck in fastboot and it would not load recovery. any fix?
Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
greendra8 said:
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.
Click to expand...
Click to collapse
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?
DJPlaya said:
Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?
Click to expand...
Click to collapse
long time ago now. but i remember at one point having to flash the stock firmware using the mi unlock tool. i also remember trying every single version of twrp and rom until one finally worked. sorry i can't help much but i believe that's how i eventually fixed it.
hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp
Marihot said:
hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp
Click to expand...
Click to collapse
Where do you get these .img files?
iconoclasthero said:
Where do you get these .img files?
Click to expand...
Click to collapse
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder
Marihot said:
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder
Click to expand...
Click to collapse
Please tell the details for this method
greendra8 said:
Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.
Click to expand...
Click to collapse
BROOOOOOOOOO HAHAHAHAHAHA I LITERALLY JUST READ YOUR COMMENT AND 10 SECONDS LATER I FLASH THE ROM WITH "CLEAN ALL AND LOCK" Im a f-king dumb bro
Marihot said:
你好，我也经历过同样的事情。
这个方法帮助我摆脱它。
尝试使用 adb 从要在 hh 中安装的 rom 中重新刷新一些文件映像。
将下面的文件从 rom 映像复制到 adb 文件夹
1.system.img（adb >> fastboot flash system system.img中的命令）
2. boot.img（adb 中的命令，如#1，更改 img 文件的名称）直到 #6
3. 供应商.img
4.dtbo.img
5. 自定义.img
6. 杂项.img
7. 现在用adb刷twrp/recovery.img（选择twrp与你要安装的rom兼容）
8. adb 的“fastboot boot recovery.img”
9. twrp刷入rom
Click to expand...
Click to collapse
Thank you, brother
try fastboot set_active a
or fastboot set_active b
Hoping I could get some help for this old phone. I've spent over 5 hours trying to get twrp installed and having no success in what should be one of the quickest steps in the whole rooting/flashing game. Reaching out for help before I lose my mind...
I've tried 2 different builds of oreo and 2 different builds of pie (all stock) and for each build I flashed different twrp versions from this link https://androidfilehost.com/?w=files&flid=232371. I even tried the android 9/10 versions on the android 8 builds. No errors in fastboot. If I try using power plus either of the volume keys it just boots right to android. If I try using the fastboot command (fastboot boot recovery.img) it freezes at the Sony logo. Doesn't seem to be an issue with twrp because I couldn't find a single mention of anyone else having this issue in any of the threads I've read while trying to troubleshoot. Any suggestions?
Is your bootloader locked?
betacrypt said:
Is your bootloader locked?
Click to expand...
Click to collapse
Oh, right, I should have mentioned that it's definitely unlocked. I checked in the service menu and I get the warning at startup.
Hmm what android version are you running currently, latest stock pie? It's possible your recovery partition is corrupt somehow.
Open up a terminal for fastboot and try running:
fastboot format recovery
or
fastboot erase recovery
then
fastboot flash recovery twrp-3.3.1-0-lilac-pie-5.img
I used twrp-3.3.1-0-lilac-pie-5.img on my device so I can confirm that one is definitely working.
betacrypt said:
Hmm what android version are you running currently, latest stock pie? It's possible your recovery partition is corrupt somehow.
Open up a terminal for fastboot and try running:
fastboot format recovery
or
fastboot erase recovery
then
fastboot flash recovery twrp-3.3.1-0-lilac-pie-5.img
I used twrp-3.3.1-0-lilac-pie-5.img on my device so I can confirm that one is definitely working.
Click to expand...
Click to collapse
So I managed to get this working. I tried the fastboot erase command but still had no success. Googled "fastboot erase twrp" or something like that and found a thread discussing how twrp was suspected of corrupting someone's data partition and running a "fastboot erase userdata" command to reformat the partition. I didn't think this would help my situation but figured I had nothing to lose at this point. Ran the "erase userdata" command, set up the phone again, but had no success at first.
I re-ran the "erase recovery" command and had no success with twrp 3.3.1. Then I tried 3.2.1 and initially had no success with hardware buttons or the "boot recovery" command. What I did this final time though, which I don't think I did on my previous attempts, was that instead of going back immediately and trying to re-flash twrp after the frozen sony screen, I gave up this time. BUT....I also said "f* it...let me try booting into recovery with the hardware buttons one last time." Lo and behold, I finally got into twrp!
I don't know if running the "erase recovery" command is what was needed, or it was just some quirky glitch where I needed the phone to freeze. Nevertheless, many thanks for responding and prompting me to make the last few attempts. Flashed magisk with no issue afterwards.