Hi, this is my firs post, I hope to be posting in the right place.
I recently unlocked the bootloader and did the root, and everything worked perfectly, however, when I started the device, the message "Verity mode is set to disabled" appears, and although not influencing usability is very annoying.
Can someone give me a hint how to remove this message?
I already tried some of commands via fastboot like:
fastboot oem lock
fastboot enable dm verity
fastboot oem enable_dm_verity
Thank you all for your help
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Have the same problem is it possible to reactivate it?
same problem on moto X4! any news?
Im looking for some solution to this issue.
prognpunk said:
Im looking for some solution to this issue.
Click to expand...
Click to collapse
Have you tried:
https://forum.xda-developers.com/moto-z4/help/z4-boot-logo-animation-t4043957
kewlzter said:
Have you tried:
https://forum.xda-developers.com/moto-z4/help/z4-boot-logo-animation-t4043957
Click to expand...
Click to collapse
This will not work. The text is appearing on top of logo. If you change logo text will be appear on it too.
QkiZMR said:
This will not work. The text is appearing on top of logo. If you change logo text will be appear on it too.
Click to expand...
Click to collapse
Hmmm. I was talking about the last two replies.
The ones about boot signature. Maybe this tool and method could be adapted.
I read this thread that you mention but still text "Verity mode is set to disabled" will overlap bootpicture. Another thing is that MotoLogoEditor can edit only contents of logo partition and this "Verity..." text appears on bootpicture which is not in logo partition. Bootpicture is /system/media/bootanimation.zip. I think that there's no simple way to remove this text.
On my Moto G6 Plus the issue disappeared after flashing boot.img from Oreo, however, I cannot guarantee that it works on Moto Z3 Play.
daniel.smith said:
On my Moto G6 Plus the issue disappeared after flashing boot.img from Oreo, however, I cannot guarantee that it works on Moto Z3 Play.
Click to expand...
Click to collapse
You mentioned the wrong file. The right file is "bootloader.img" of oreo rom
Command: fastboot flash bootloader bootloader.img
Thank you. Work on my G6 Plus
jamesjunn said:
You mentioned the wrong file. The right file is "bootloader.img" of oreo rom
Command: fastboot flash bootloader bootloader.img
Thank you. Work on my G6 Plus
Click to expand...
Click to collapse
i have a Moto Z3 Play
i have flashed the "bootloader.img" file and it didn't remove de the message
i have flashed the "boot.img" file and it removed the message but i cannot boot anymore (i'm on lineageOS)
so i guess this trick only work with the official ROM
nononymous said:
i have a Moto Z3 Play
i have flashed the "bootloader.img" file and it didn't remove de the message
i have flashed the "boot.img" file and it removed the message but i cannot boot anymore (i'm on lineageOS)
so i guess this trick only work with the official ROM
Click to expand...
Click to collapse
You need to put the bootloader or boot file inside the rom folder, replace the previous files and flash the rom completely.
Related
So in preparation for the kitkat update, I did the following steps:
unrooted within superuser app
flash stock recovery
flash stock boot.img
flash stock system.img
Once I rebooted I downloaded the OTA and tried to install. Now, after that, I wasnt really sure what happened on the phone, as I passed the time by watching a youtube video on my computer. However, I looked back down, and it was inside the bootloader, giving a partition failure of some sort. And when I tried to flash anything, it gave a remote failure error. It won't boot into anything, and it says the device is locked. Can't do mfastboot oem get_unlock_data either, literally nothing but fastboot reboot works
do i have a $650 paper weight on my hands?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Fixed it! See the post at the very bottom of this page for the solution!
i would use RSD lite to get back to the latest 4.2.2
mj0528 said:
i would use RSD lite to get back to the latest 4.2.2
Click to expand...
Click to collapse
it won't boot at all
Well fastboot starts at least. If you try to reload stock firmware (4.2.2) using rsdlite(not fastboot from a command line) which error do you get?
Steve-x said:
Well fastboot starts at least. If you try to reload stock firmware (4.2.2) using rsdlite(not fastboot from a command line) which error do you get?
Click to expand...
Click to collapse
My device isn't showing up under rsdlite 6.1.4 at all
Sadly then I'm leaning towards it being a pretty looking brick. I've had many flash failures while experimenting with my XT1058s but I have never tried any custom recoveries so they were always recoverable with fastboot and rsdlite.
Hopefully someone else has some suggestions for you to try.
I flashed system.img, recovery.img, and boot.img from the original sbf file. not from the first OTA. and then the phone seems to have locked itself
alex94kumar said:
I flashed system.img, recovery.img, and boot.img from the original sbf file. not from the first OTA. and then the phone seems to have locked itself
Click to expand...
Click to collapse
Had you taken the first OTA already? If you had done that, you should have flashed these files from the new SBF file....
So, when you are in fastboot mode, your device is no longer getting recognized from fasboot command line? What does fastboot devices show?
tejaskary said:
Had you taken the first OTA already? If you had done that, you should have flashed these files from the new SBF file....
So, when you are in fastboot mode, your device is no longer getting recognized?
Click to expand...
Click to collapse
Ah. there's my problem. I flashed the files from the factory moto X.
And the device is recognized in fastboot, I can send it commands, it's just that none of them except fastboot reboot actually work
alex94kumar said:
Ah. there's my problem. I flashed the files from the factory moto X.
And the device is recognized in fastboot, I can send it commands, it's just that none of them except fastboot reboot actually work
Click to expand...
Click to collapse
Can you try these commands and see if anything changes?
fastboot oem fb_mode_clear
fastboot reboot-bootloader
After that can you try any of the fastboot flash commands using the new SBF file?
It worked!!! Oh my god thank you so much! You are a life saver!!
delete
alex94kumar said:
It worked!!! Oh my god thank you so much! You are a life saver!!
Click to expand...
Click to collapse
Glad it worked for you !! Enjoy with 4.4...
I have problem with it, it resets and shows android with red triagle on it.
i can't boot into flash mode but i can into fastboot.
Pease help me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
malivrag11 said:
I have problem with it, it resets and shows android with red triagle on it.
i can't boot into flash mode but i can into fastboot.
Pease help me
Click to expand...
Click to collapse
Looks like the CM recovery.. You have a chance of making CM work if you put whatever it is you are trying to flash into your internal storage and not to sdcard..
Please give some more info on what you are trying to do?
i flashed kenel and userdata trough fastboot but i cant flash system, now phone don't show this robot
but it resets again
now it shows battery when charging
malivrag11 said:
i flashed kenel and userdata trough fastboot but i cant flash system, now phone don't show this robot
but it resets again
now it shows battery when charging
Click to expand...
Click to collapse
ok.. What are you flashing through fastboot? And how come you cant flash the system image?
it says ''error: cannot load 'L:\firmwares\C5503_10.7.A.0.228_TR\system.img'''
malivrag11 said:
it says ''error: cannot load 'L:\firmwares\C5503_10.7.A.0.228_TR\system.img'''
Click to expand...
Click to collapse
Worth a try.. go here and download: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Install the adb/fastboot and put the system.img in the adb folder and try flashing through this tool rather than flashtool.. Good chance it will work..
i try with it before,it can't flash it. I run ''fastboot oem rebootRUU'' and wating, after i will try flash system again
now it says ''FAILED (remote: data too large)'' help me
malivrag11 said:
now it says ''FAILED (remote: data too large)'' help me
Click to expand...
Click to collapse
No brother.. in fastboot (not flashtool) use this command: fastboot flash system system.img
Press enter
and when it's done sending the system img, use this command: fastboot reboot
press enter
Your phone should now reboot..
Can you please tell me where you downloaded the ROM from bro? I'll have a look
i use fastboot this is what it said
UPDATE: my volume down button is broken, i flashed boot.img from cm12, go to recovery and install cm12
i have now problem with screen, there are moving horizontal lines, i read that is cm12 bug HELP MEE
malivrag11 said:
i have now problem with screen, there are moving horizontal lines, i read that is cm12 bug HELP MEE
Click to expand...
Click to collapse
so flash CM12.1, RR, Validus, Slim, a bunch of ports and RR/CM13 bro.. Stable as are most if not all the ROM's here in the ZR section..
no way all time same results
when it power on there all many horizontal lines on the screen, i tryed to flash bootloader but no succes
Ok, so got my brand new shiny Oneplus 3T yesterday after waiting aged for it to come in.
Using it for a bit, noticed an OTA update to nougat came out (about 900mb) which downloaded in the background.
Triggered the upgrade, now the phone won't boot. I'm also having trouble installing any recovery roms on to it, because I was never intending to root the phone in the first place, and as a result didn't unlock the bootloader using the phone interface when it was on.
So now, it appears I'm stuck! My phone won't accept any side-load roms, (fails), full roms don't read (cannot open file) and fastboot won't unlock the bootloader (Not allowed)
....um.. not having a clue what I'm doing here....help???
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
try going to stock oxygen recovery. wipe data and cache there. see if it boots.
try the unbricking thread too.
if all else fail, call OP customer service.
let us know what happens.
To fix it - see "[UNBRICK] Unbrick Tutorial For The OnePlus 3T!!!!!!!! by Harris K". You have to download his two files onto a laptop or desktop computer and install a qualcomm driver (one of the files). The qualcomm driver will open a serial port into the phone's chipset. The other file will download a stock system, recovery, and fastboot to your phone through the qualcomm serial port. Harris is a genius, buy him a beer. This will fix the following problems.
1) It sounds like the OTA patch screwed up your /system where it doesn't even try to boot. You can still boot into /recovery and /fastboot but just not into /system. Since the phone is still "locked" (flashing prohibited) you cannot flash anything to fix it.
2) dm-verity does not allow any changes to /system. dm-verity checks a hash of hashes of /system. If the hash check fails when you boot /system, dm-verity will "brick" your phone (by design) leaving you with a black screen.
The OTA updates the system and downloads a hash key corresponding to that version. After the OTA, everyone has to end up with exactly the same system in order to pass the dm-verity check.
When you enable flashing (called "unlocking the bootloader") dm-verity will wipe /data to prevent someone from flashing a non-stock recovery to access your data.
infamousvincci said:
try going to stock oxygen recovery. wipe data and cache there. see if it boots.
try the unbricking thread too.
if all else fail, call OP customer service.
let us know what happens.
Click to expand...
Click to collapse
Ok, so went to the unbricking thread. The tool worked! I'm back up and running
bunburyist said:
Ok, so went to the unbricking thread. The tool worked! I'm back up and running
Click to expand...
Click to collapse
I deserve a thank you button haha
Hi I bought a Z3 play yesterday and it was in "recovery mode", it has the Stock Rom but bootloader locked still. I try to download the Stock Rom again and flash it in fastboot but i get the first "fail" error by the bootloader locked.
Then I try to unlock the bootloader but it hasnt the "unlock OEM" activated and I cant access to the OS.
then i tried to use the RSAL but in 43% it shows me an error and aborts :/
And finally I tried to flash the stock firmware on RSD but it shows me the "the phone failed to switch to fastboot mode".
What Can I do? Im so blue about it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
betho1822 said:
Hi I bought a Z3 play yesterday and it was in "recovery mode", it has the Stock Rom but bootloader locked still. I try to download the Stock Rom again and flash it in fastboot but i get the first "fail" error by the bootloader locked.
Then I try to unlock the bootloader but it hasnt the "unlock OEM" activated and I cant access to the OS.
then i tried to use the RSAL but in 43% it shows me an error and aborts :/
And finally I tried to flash the stock firmware on RSD but it shows me the "the phone failed to switch to fastboot mode".
What Can I do? Im so blue about it
Click to expand...
Click to collapse
Have you tried LMSA (Lenovo Moto Smart Assistant)?
kewlzter said:
Have you tried LMSA (Lenovo Moto Smart Assistant)?
Click to expand...
Click to collapse
Yes, and fails at 46% all the time :/
betho1822 said:
Hi I bought a Z3 play yesterday and it was in "recovery mode", it has the Stock Rom but bootloader locked still. I try to download the Stock Rom again and flash it in fastboot but i get the first "fail" error by the bootloader locked.
Then I try to unlock the bootloader but it hasnt the "unlock OEM" activated and I cant access to the OS.
then i tried to use the RSAL but in 43% it shows me an error and aborts :/
And finally I tried to flash the stock firmware on RSD but it shows me the "the phone failed to switch to fastboot mode".
What Can I do? Im so blue about it
Click to expand...
Click to collapse
betho1822 said:
Yes, and fails at 46% all the time :/
Click to expand...
Click to collapse
You were able to solve it?
I'm having trouble very similar... LMSA stuck at 44% and RSD Lite "Get decompress file size Error" "Unzip fail"
[Help] Device bootloop and recovery wont flash or boot
I have installed LineageOS Beckham https://download.lineageos.org/beckham Besides some bugs like gps location and LTE on some providers, it was working great. Today device rebooted by itself and got stuck on bootloop... I tried: $ fastboot...
forum.xda-developers.com
First of all and most importantly, I want to say that this is not my work. This is a port of the work done by @abhinavgupta371 and @HELLBOY017 for the OP9RT. I merely made sure there weren't extra or missing files and edited the .bat and .sh files accordingly. I also edited the README.txt and that's exactly what you should do: READ IT BEFORE INSTALLING.
I pass this along so people can make their own Fastboot ROMs. @mauronofrio stopped making them quite a while ago and it's nice to have this tool again. It saves from having to unlock the BL again after a MSM flash. You have to edit the install.bat and install.sh as necessary for the partitions in your device's firmware and then edit the README.txt with your build's information.
WARNING: Most of this script runs in fastbootd. Ensure that your device can get into this mode BEFORE running it. You can do this by:
adb reboot fastboot or
fastboot reboot fastboot
If your device cannot enter fastbootd mode, DO NOT RUN THIS SCRIPT.
There wasn't a full A.14 build available for Global, so I had to make it with A.13. The EU and IN builds are A.14:
EU: https://androidfilehost.com/?fid=15664248565197183368
IN: https://androidfilehost.com/?fid=15664248565197183429
Global: https://androidfilehost.com/?fid=15664248565197183433
Would this be able to fix a soft brick? Or a bootloop?
Ph0nysk1nk said:
Would this be able to fix a soft brick? Or a bootloop?
Click to expand...
Click to collapse
get into bootloader and try it. what do you have to lose?
g96818 said:
get into bootloader and try it. what do you have to lose?
Click to expand...
Click to collapse
A lot actually, I'm not bricked. I just always like having a way to fix my phone when things go wrong lol.
Ph0nysk1nk said:
Would this be able to fix a soft brick? Or a bootloop?
Click to expand...
Click to collapse
While this shouldn't be the first thing you should use to fix a bootloop, it is a tool to fix both of those things.
thanks you
Sorry to wrong people.
Ayyyy! this is a good first step for the device modding ! Thanks!
+1 great to see this here!
Cheers
i can't flash with guide help me
Devar Bl3nd said:
i can't flash with guide help me
Click to expand...
Click to collapse
Extract all contents to same folder. Open command prompt in that directory. If you want phone/data wiped, run install.bat. If you want data preserved, run upgrade.bat.
```Failed to boot into userspace fastboot; one or more components might be unbootable.```
annnd im bricked
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Oh dang! What fastboot did you use.
latest from google official!
same issue on linux aswell
Fastboot roms by Mauronofrio are made to unbrick a soft bricked phone. But if is a bad bad brick it will not work.
MSM tool is the second to last action to restore a phone.
The last is OnePlus suport team.
I was under the impression we couldn't use the latest one from Google. Try Google searching fastboot enhance and see if that resolves it.
null0seven said:
Fastboot roms by Mauronofrio are made to unbrick a soft bricked phone. But if is a bad bad brick it will not work.
MSM tool is the second to last action to restore a phone.
The last is OnePlus suport team.
Click to expand...
Click to collapse
we dont have any for OP10P do we
Twiggy000b said:
I was under the impression we couldn't use the latest one from Google. Try Google searching fastboot enhance and see if that resolves it.
Click to expand...
Click to collapse
even when trying to enter fastbootd with this it still fails