after instant ubl i got notice dm-verity corruption, and i fastboot flash vbmeta still not working. any1 can help?
kaye48 said:
after instant ubl i got notice dm-verity corruption, and i fastboot flash vbmeta still not working. any1 can help?
Click to expand...
Click to collapse
Any news on this?
I also have it, have to press a button in order for it to boot, each time.
Did you try fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img when flashing vbmeta.img?
What fixed it for me was using the vbmeta file that is provided in this recovery, and apply the command.
Trying the fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img command with the original vbmeta, extracted from my ROM somehow did not do the trick.
That's strange! In the future I'd try re-downloading and extracting the image and trying again; I've found that this fixes strange bugs surprisingly often
dm-verity corrupted fix after unlocking bootloader:
Plug your phone in fastboot mode to PC and open command prompt in platform tools.
Type:
fastboot oem cdms
inrope said:
dm-verity corrupted fix after unlocking bootloader:
Plug your phone in fastboot mode to PC and open command prompt in platform tools.
Type:
fastboot oem cdms
Click to expand...
Click to collapse
Worked for me, thanks!
inrope said:
dm-verity corrupted fix after unlocking bootloader:
Plug your phone in fastboot mode to PC and open command prompt in platform tools.
Type:
fastboot oem cdms
Click to expand...
Click to collapse
Worked for my Xiaomi Redmi 10A. Thank you.
inrope said:
dm-verity corrupted fix after unlocking bootloader:
Plug your phone in fastboot mode to PC and open command prompt in platform tools.
Type:
fastboot oem cdms
Click to expand...
Click to collapse
Bro Thank you VERY VERY Much it Fixed because i unlock bootloader and i got the error dm verity even install img and fastboot oem cdms worked! | and becuase 168 hours i can't wait i install different exe file now it fixed! thank you | i make this account right now
to thanks | im from philippines
Hi i have an redmi note 11s it was showing dm-verity corruption earlier and then now it just wont boot at all not even to fastboot or recovery.. anyways i still can save this phone? its only 1 year and 1 month old...
How is that? Can anyone show me a tutorial please? My mom's xioami is showing this error and I don't know how to fix It, I have only found YT videos in Idian but nome of It worked.
inrope said:
dm-verity corrupted fix after unlocking bootloader:
Plug your phone in fastboot mode to PC and open command prompt in platform tools.
Type:
fastboot oem cdms
Click to expand...
Click to collapse
Could you show me how you did It step by step please? I would really appreciate it
malex174 said:
Worked for me, thanks!
Click to expand...
Click to collapse
JJLechadores said:
Bro Thank you VERY VERY Much it Fixed because i unlock bootloader and i got the error dm verity even install img and fastboot oem cdms worked! | and becuase 168 hours i can't wait i install different exe file now it fixed! thank you | i make this account right now
to thanks | im from philippines
Click to expand...
Click to collapse
Hi, I'm also from the philippines. can you help me? I'm having the same issue
For anyone facing this issue on Realme devices, or any other devices, here's how you can solve it without resetting or wiping out your data:
Steps:
Turn off your phone.
Press the volume down + power button.
Release both buttons once the Realme logo appears.
Select the recovery mode option.
Choose your preferred language.
Select the reboot option.
By following these steps, you should be able to resolve the issue without losing any of your data.
Related
My moto z before using RSD lite flash NPL 25.86-30, then OTA updated to NPL25.86-30.3. It seems that bootloarder is also updated. now I want to re-use RSD lite to flash NPL25.86-30. But RSD has shown an error in flashing GPT.bin, show "FAIL"
Who can help me?:crying:
You can't go back, if the Bootloader got updated.
jump the step of flashing gpt by editing the xml file(delete the line)
Now my device have a very strange question, if I use the battery mod, is unable to shutdown, automatically enter the bootloarder. Do not use the module can shutdown, but the connection charger will automatically enter the bootloarder,can not be charged in the shutdown state.
Sorry,my english is bad.
rakee said:
Now my device have a very strange question, if I use the battery mod, is unable to shutdown, automatically enter the bootloarder. Do not use the module can shutdown, but the connection charger will automatically enter the bootloarder,can not be charged in the shutdown state.
Sorry,my english is bad.
Click to expand...
Click to collapse
start fastboot in the cmd and start the following command
fastboot oem fb_mode_clear
this should solve your bootlader at reboot issue...
treibstoff said:
start fastboot in the cmd and start the following command
fastboot oem fb_mode_clear
this should solve your bootlader at reboot issue...
Click to expand...
Click to collapse
Its work for me,thanks man!:highfive::highfive:
treibstoff said:
start fastboot in the cmd and start the following command
fastboot oem fb_mode_clear
this should solve your bootlader at reboot issue...
Click to expand...
Click to collapse
After the last OTA (july) update has failed, I got an issue very similar, but in my case, everytime I restart or turn off the device, it gets to twrp recovery and I need do restart it on fastboot mode then choose START on side menu to get boot properly. Can you help?
Hello everyone !
I updated my tablet to android 9, during the update an error occured and now my tablet can't boot (it's stuck on LENOVO screen forever).
My tablet is Lenovo TB-X605F.
I tried:
- Wipe/data (recovery mode)
- Wipe/cache (recovery mode)
- Fastboot (my bootloader is locked so I can do nothing)
Note: I don't have TWRP or custom recovery, I have the default one .
I don't know what can i do please help me !
XX_MRBEAN_XX said:
Hello everyone !
I updated my tablet to android 9, during the update an error occured and now my tablet can't boot (it's stuck on LENOVO screen forever).
My tablet is Lenovo TB-X605F.
I tried:
- Wipe/data (recovery mode)
- Wipe/cache (recovery mode)
- Fastboot (my bootloader is locked so I can do nothing mSpy reviews)
Note: I don't have TWRP or custom recovery, I have the default one .
I don't know what can i do please help me !
Click to expand...
Click to collapse
I am sorry to say that but I guess nothing could be done to fix your tablet. I would be happy to proven wrong and see some solutions in this thread.
@XX_MRBEAN_XX
The mostly overlooked command
Code:
adb sideload <ROM / MOD>
may help: Get device's Stock ROM and flash it this way.
jwoegerbauer said:
@XX_MRBEAN_XX
The mostly overlooked command
Code:
adb sideload <ROM / MOD>
may help: Get device's Stock ROM and flash it this way.
Click to expand...
Click to collapse
Windows detect my tablet only when It's in fastboot. I don't know why
When I do recovery --> apply update from adb it's say "E: failed to open driver control: Permission denied"
And in my pc, ADB don't recognize my tablet (only fastboot recognize)
Btw, i downloaded my stock tablet rom
XX_MRBEAN_XX said:
Windows detect my tablet only when It's in fastboot. I don't know why
When I do recovery --> apply update from adb it's say "E: failed to open driver control: Permission denied"
And in my pc, ADB don't recognize my tablet (only fastboot recognize)
Btw, i downloaded my stock tablet rom
Click to expand...
Click to collapse
1. Looks to me that the ADB-driver you use isn't suitable: Download and install the correct driver for your Lenovo. tab:
https://devsjournal.com/download-lenovo-usb-drivers-adb.html
2. Wondering why then you didn't flash this Stock ROM by means of Fastboot ?
Code:
fastboot devices
fastboot erase boot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot flashall <STOCK-ROM-IMG>
fastboot reboot
jwoegerbauer said:
1. Looks to me that the ADB-driver you use isn't suitable: Download and install the correct driver for your Lenovo. tab:
2. Wondering why then you didn't flash this Stock ROM by means of Fastboot ?
Code:
fastboot devices
fastboot erase boot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot flashall <STOCK-ROM-IMG>
fastboot reboot
Click to expand...
Click to collapse
Well, i think i am ****ed because when i do these fastboot command, it's saying "FAILED (remote: 'device is locked. Cannot erase.')
And adb still don't recognize my system.
Thank you for your help
XX_MRBEAN_XX said:
Well, i think i am ****ed because when i do these fastboot command, it's saying "FAILED (remote: 'device is locked. Cannot erase.')
Click to expand...
Click to collapse
Oh man
become familiar with Fastboot-driver and its subcommands available!!!
Anyway, unlock tab's boot-loader by means of Fastboot before you carry out the commands previously shown
Code:
fastboot devices
fastboot OEM unlock
FYI: I no longer participate with this thread.
jwoegerbauer said:
Oh man
become familiar with Fastboot-driver and its subcommands available!!!
Anyway, unlock tab's boot-loader by means of Fastboot before you carry out the commands previously shown
Code:
fastboot devices
fastboot OEM unlock
FYI: I no longer participate with this thread.
Click to expand...
Click to collapse
I tried fastboot oem unlock
It's say "unknow commands"
Anyway thank you for your help !
I think we can't do something for this tablet.
Thank you very much
XX_MRBEAN_XX said:
Hello everyone !
I updated my tablet to android 9, during the update an error occured and now my tablet can't boot (it's stuck on LENOVO screen forever).
My tablet is Lenovo TB-X605F.
I tried:
- Wipe/data (recovery mode)
- Wipe/cache (recovery mode)
- Fastboot (my bootloader is locked so I can do nothing)
Note: I don't have TWRP or custom recovery, I have the default one .
I don't know what can i do please help me !
Click to expand...
Click to collapse
To rescue a bricked Lenovo device, download their LMSA tool to a Windows PC. Use the Rescue option.
Have a look on the TWRP thread for the unlock commands. They will only work if you had already enabled Developer Options and OEM unlocking before the device bricked.
Yahoo Mike said:
To rescue a bricked Lenovo device, download their LMSA tool to a Windows PC. Use the Rescue option.
Have a look on the TWRP thread for the unlock commands. They will only work if you had already enabled Developer Options and OEM unlocking before the device bricked.
Click to expand...
Click to collapse
Holy crap. My hero! Can I buy you a beer dude?
Hello guys. My brother's Huawei p20 Lite is stuck in a bootloop. I'm unable to access the recovery and Erecovery (tried 10 times but it just won't work.) The only thing that works is Fastboot mode and it shows this error. Can't use Hisuite because apparently this phone isn't supported to be recovered using that program. How can I fix this phone? Is it permanently bricked?
Advanced07 said:
Hello guys. My brother's Huawei p20 Lite is stuck in a bootloop. I'm unable to access the recovery and Erecovery (tried 10 times but it just won't work.) The only thing that works is Fastboot mode and it shows this error. Can't use Hisuite because apparently this phone isn't supported to be recovered using that program. How can I fix this phone? Is it permanently bricked?
Click to expand...
Click to collapse
Hello, try this way out...
1. install on your PC "Minimal ADB and fastboot" tool, in fastboot mode run command
fastboot erase userdata
and try restart the device.
Or,
2. download and use a Service ROM with an sd/card or an USB-OTG flashdrive in dload mode. Download correct Service ROM from androidhost.ru website, unpack .zip archive , find dload file in "Software" folder, and simply transfer it to the SD card, without unpacking it! (instruction can be found in ReleaseDoc folder).
Turn off your phone and flash FW using three button combo .
The first step is to determine which variant of your device you are on.
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
(The bracketed (Cxxx) is your device’s regional variant.
This number is very important in determining the correct firmware to download!).
Service ROM can be found here:
https://androidhost.ru/search.html . Type Ane- or Anne- .
For example, for build number ANE-LX1 9.1.0.278 C432) :
https://androidhost.ru/Xar
Maybe it will help you...
-Alf- said:
Hello, try this way out...
1. install on your PC "Minimal ADB and fastboot" tool, in fastboot mode run command
fastboot erase userdata
and try restart the device.
Or,
2. download and use a Service ROM with an sd/card or an USB-OTG flashdrive in dload mode. Download correct Service ROM from androidhost.ru website, unpack .zip archive , find dload file in "Software" folder, and simply transfer it to the SD card, without unpacking it! (instruction can be found in ReleaseDoc folder).
Turn off your phone and flash FW using three button combo .
The first step is to determine which variant of your device you are on.
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
(The bracketed (Cxxx) is your device’s regional variant.
This number is very important in determining the correct firmware to download!).
Service ROM can be found here:
https://androidhost.ru/search.html . Type Ane- or Anne- .
For example, for build number ANE-LX1 9.1.0.278 C432) :
https://androidhost.ru/Xar
Maybe it will help you...
Click to expand...
Click to collapse
Thanks I'm gonna give these a try and I will let you know how it goes
-Alf- said:
Hello, try this way out...
1. install on your PC "Minimal ADB and fastboot" tool, in fastboot mode run command
fastboot erase userdata
and try restart the device.
Or,
2. download and use a Service ROM with an sd/card or an USB-OTG flashdrive in dload mode. Download correct Service ROM from androidhost.ru website, unpack .zip archive , find dload file in "Software" folder, and simply transfer it to the SD card, without unpacking it! (instruction can be found in ReleaseDoc folder).
Turn off your phone and flash FW using three button combo .
The first step is to determine which variant of your device you are on.
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
(The bracketed (Cxxx) is your device’s regional variant.
This number is very important in determining the correct firmware to download!).
Service ROM can be found here:
https://androidhost.ru/search.html . Type Ane- or Anne- .
For example, for build number ANE-LX1 9.1.0.278 C432) :
https://androidhost.ru/Xar
Maybe it will help you...
Click to expand...
Click to collapse
Tried all the ADB commands and they all failed, gonna try to use the SD card method.
-Alf- said:
Hello, try this way out...
1. install on your PC "Minimal ADB and fastboot" tool, in fastboot mode run command
fastboot erase userdata
and try restart the device.
Or,
2. download and use a Service ROM with an sd/card or an USB-OTG flashdrive in dload mode. Download correct Service ROM from androidhost.ru website, unpack .zip archive , find dload file in "Software" folder, and simply transfer it to the SD card, without unpacking it! (instruction can be found in ReleaseDoc folder).
Turn off your phone and flash FW using three button combo .
The first step is to determine which variant of your device you are on.
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
(The bracketed (Cxxx) is your device’s regional variant.
This number is very important in determining the correct firmware to download!).
Service ROM can be found here:
https://androidhost.ru/search.html . Type Ane- or Anne- .
For example, for build number ANE-LX1 9.1.0.278 C432) :
https://androidhost.ru/Xar
Maybe it will help you...
Click to expand...
Click to collapse
Device won't enter dload mode either. I hold the 3 buttons but it just bootloops.
Sorry, I'm out of ideas (with the locked bootloader).
-Alf- said:
Sorry, I'm out of ideas (with the locked bootloader).
Click to expand...
Click to collapse
I'm as well, the only thing that might work is removing and placing the battery ribbon cable again but I don't have the glue to close the case. Should I still try it?
Advanced07 said:
but I don't have the glue to close the case. Should I still try it?
Click to expand...
Click to collapse
You should try it, why not.
IMO it might be the HW problem , dead memory or damaged motherboard, (fastboot commands are not working).
-Alf- said:
You should try it, why not.
IMO it might be the HW problem , dead memory or damaged motherboard, (fastboot commands are not working).
Click to expand...
Click to collapse
The fastboot commands are working but it says I don't have permission to do it or something along those lines it refuses to execute it
Advanced07 said:
Hello guys. My brother's Huawei p20 Lite is stuck in a bootloop. I'm unable to access the recovery and Erecovery (tried 10 times but it just won't work.) The only thing that works is Fastboot mode and it shows this error. Can't use Hisuite because apparently this phone isn't supported to be recovered using that program. How can I fix this phone? Is it permanently bricked?
Click to expand...
Click to collapse
Same phone and same thing happened to me. What's different is that twrp recovery works.
It all started when I unlocked the bootloader with PotatoNV. I unlocked it with the fastboot oem unlock MYUNLOCKCODE command.
Then i flashed twrp: fastboot flash recovery_ramdisk d:\twrp.img
Then whatever happened, I started seeing the error "AP_S_ABNORMAL 64" in fastboot mode, but running commands was fine.
I deleted everything by entering the codes below with fastboot mode.
fastboot erase system -w
fastboot erase userdata
Then I reinstalled twrp recovery by entering the codes below and flashed a custom rom.
fastboot flash recovery_ramdisk d:\twrp.img
fastboot flash system d:\MyCustomRom.img
Suddenly what do I see.
When I rebooted with the fastboot reboot command, twrp was constantly opening. The system would not boot at all. I was desperately doing everything I could think of. Only one thing worked. I opened emui e-recovery by pressing the volume up, volume down and power keys at the same time. It was failing there and there was only one option; I clicked restart. The system booted this time, not twrp, and after a long wait, the main installation screen came.
biorap said:
I opened emui e-recovery by pressing the volume up, volume down and power keys at the same time. It was failing there
Click to expand...
Click to collapse
it is not e-recovery, this buttons combination triggers the installation of FW by the dload method.
biorap said:
fastboot erase system -w
fastboot erase userdata
Click to expand...
Click to collapse
Use stock Recovery - Wipe cache partition & Factory reset
biorap said:
flashed a custom rom
Click to expand...
Click to collapse
How to install Treble GSI ROMs on Kirin-devices:
https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/post-84305543
-Alf- said:
it is not e-recovery, this buttons combination triggers the installation of FW by the dload method.
Use stock Recovery - Wipe cache partition & Factory reset
How to install Treble GSI ROMs on Kirin-devices:
https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/post-84305543
Click to expand...
Click to collapse
Thank you for your clarify.
Is it possible to use stock recovery when i flash a custom rom via fastboot mode? I mean; do i have to use twrp when i wanna flash a custom rom? Is it possible to use custom rom with stock recovery?
biorap said:
Thank you for your clarify.
Is it possible to use stock recovery when i flash a custom rom via fastboot mode? I mean; do i have to use twrp when i wanna flash a custom rom? Is it possible to use custom rom with stock recovery?
Click to expand...
Click to collapse
Have you read?
https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/post-84305543
Hi guys I am having an interested issue,
I want to install custom rom in my phone
I have downloaded in depth test and applied for un depth test
my mobile do connect to computer when it prompt to select mod I do select file transfer and my mobile do connect to laptop
and it shows in "adb devices" but when it goes into bootloader mod my mobile gets disconnected I have done everything I could
I have install every possible driver i got from articles but non worked is it the issue with my windows 10 ? or driver issue I have spent my whole night on this but couldn't find the way
fastboot devices
0purple said:
fastboot devices
Click to expand...
Click to collapse
what does it mean ?
when i connect my phone it prompt me with this and usb debugging is on
i tried adb devices but it didn't showed anything but when i chose transfer file it do connect to the laptop and shows in adb devices
najam489 said:
what does it mean ?
Click to expand...
Click to collapse
Try it once you are in fastboot
wow its showing
najam489 said:
wow its showing
Click to expand...
Click to collapse
0purple said:
Try it once you are in fastboot
Click to expand...
Click to collapse
i have another problem now my device is showing with fastboot devices but my devices status is locked when i tried this command "fastboot flash recovery recovery.img" it didnt work i am follwing this article https://www.guidetoroot.com/root-realme-3-pro/
thank you for your help my bootloader wasn't unlock it is now thanks a lot
It appears your device's bootloader is locked. Try:
fastboot oem unlock
fastboot flashing unlock
If that doesn't help, search for a guide on how to unlock bootloader for your specific brand.
It also looks like don't really know what you are doing. Make sure you are following trusted guide. If no, I'll be happy to help.
0purple said:
It appears your device's bootloader is locked. Try:
fastboot oem unlock
fastboot flashing unlock
If that doesn't help, search for a guide on how to unlock bootloader for your specific brand.
It also looks like don't really know what you are doing. Make sure you are following trusted guide. If no, I'll be happy to help.
Click to expand...
Click to collapse
well i did installed custom roms few time but i dont know much, i did unlock bootloader now the problem is i do install custom recovery twrp and it do installed and rom manager shows that custom recovery is installed but pressing volume down + power button just shows fastboot logo and it restart my phone, and with command "
adb reboot bootloader" i am able to boot into fastboot mood and when i go to recovery from their it open stock recovery instead of twrp
Stolen from my guide:
7. Go into fastboot mode
8. fastboot flash recovery recovery.img
9. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
10. fastboot reboot recovery
12. Sometimes recovery doesn't want to stick as a permanent one. To test it, hold the power button and select "Reboot to recovery". If you reboot to TWRP, you can move on, but if you reboot to stock one, flash recovery using fastboot again and from recovery flash recovery again (sounds crazy, right?). I won't give you instructions on this, research it yourself. Make sure guide you will find is for your device and your recovery.
HI to all
I got my phone back from service, latest version installed (DN2103_11_A.14 EU).
I will flash TWRP and root, so do I need A.14 vbmeta or can I just use vbmeta from same post I will download TWRP?
If I need A.14 vbmeta, does anyone have it?
Thanks
There is no difference, the same one can be used for all versions.
you can use the vbmeta from TWRP Thread.
Zombnombs said:
There is no difference, the same one can be used for all versions.
Click to expand...
Click to collapse
HI and thank you.
HofaTheRipper said:
you can use the vbmeta from TWRP Thread.
Click to expand...
Click to collapse
HI and thank you.
How do you enter fastboot mode? There is no option from power button, and when I use adb reboot bootloader, I go to a black screen with font size 1 that says we are in fastboot mode, and this is for developers only, press power up + power to exit.
In recovery there is no "Advanced" option to reboot to fastboot.
krugm0f0 said:
I use adb reboot bootloader, I go to a black screen with font size 1 that says we are in fastboot mode, and this is for developers only, press power up + power to exit
Click to expand...
Click to collapse
That's exactly what fastboot mode is. Your phone is in fastboot mode. Use your poershell terminal on the pc to start sending fastboot commands. Eg "fastboot devices" to test the connection.
If you phone is not responding to fastboot commands, try adding "./" to the start of every fastboot command instead, eg "./fastboot devices"
Zombnombs said:
That's exactly what fastboot mode is. Your phone is in fastboot mode. Use your poershell terminal on the pc to start sending fastboot commands. Eg "fastboot devices" to test the connection.
If you phone is not responding to fastboot commands, try adding "./" to the start of every fastboot command instead, eg "./fastboot devices"
Click to expand...
Click to collapse
It's just that it looks nothing like the fastboot mode on my OP2, OPX, OP5T or OP Nord 5G. And it's not recognized by fastboot devices, and does not accept any commands. <waiting for device>
krugm0f0 said:
It's just that it looks nothing like the fastboot mode on my OP2, OPX, OP5T or OP Nord 5G. And it's not recognized by fastboot devices, and does not accept any commands. <waiting for device>
Click to expand...
Click to collapse
Seems like you just don't have the right drivers installed. Sure it looks different but that doesn't mean it has to work differently.
Windows can get the drivers automatically for you, connect in fastboot mode, then check for updates in windows, then they should either get installed or show up in optional updates as Mediatek ADB something.