Hi I tried to install few treble roms and every time I flash it it boots, but says "your device was corupted, contact your device manufacturer" or something like that and after that it says "system ui has stopped" this message can't go off.
Only rom that worked for me was android P pixelexperience. All other oreo-based roms does not work.
Any idea how to fix it? (fastboot -w does not work, it causes bootloop for me)
Related
Hi,
I have followed the official wiki to install Cyanogenmod 12.1 nightly builds (December 25, 2015 nightly build) on my xperia M. It all worked well for the first time.
But suddenly after using it for some days happily, when I rebooted the device, the moment the device boots up, all the apps start crashing, causing the device unusable. I tried to reboot but it's still there. So I tried to repeat the process to get rid of this and tried to flash the December 30, 2015 build but somehow it is not working.
When I sideload the update zip file, it starts and gets stuck at 47% for quite long time and then suddenly finishes with (Total xfer: 1.00x ). The instant it goes 100%, the android icon showing "update" process disappears and screen keeps blinking and stays dark but still "adb devices" shows my device connected but the device screen just keeps blinking and nothing shows. I tried "adb reboot" but it throws this error
"error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device."
the "kill-server" command fails as well and thus, the problem persists.
I also installed open gapps after installing CM12.1 on the very first time. But in all those re-flashes, I skipped flashing it altogether and wiping cache partition, media and data & factory reset, these apps (calendar, music and gmail etc) throw the error the devices boots up. I guess the device is not getting formatted properly and its not being flashed with just the newer image. It gets stuck at 47% for way too long (almost 20 mins or more), while if I remember correctly, it didn't do so on first flashing.
Since I can't use any app when the device is ON, I can't open settings to check anything. Please help me getting rid of this, so that I can enjoy using this awesome ROM.
Thanks in advance.
I succesfully rooted MM but I cannot get rid of the "Your device has failed verification and may not work propperly" warning screen when booting, is there a .img file I missed flashing?
Another reason not to install MM !
As it said in the rooting guide you used, it will do that. And just ignore. Its the price we pay to be early adopters.
When you modify some system files in stock MM like rooting or unlocking, that warning message will appear each time you boot your phone. It's normal, just ignore it
Its nothing to worry about, it's the new bootloader's security warning feature. didn't you vist http://g.co/abh its self explanatory if you changed the system software yourself, then you have nothing to worry about.
is there any way to remove this advertising ?
It seems this is the only message I found across google search for my device Asus Zoom ZX551ML.
Just installed a modified ROM and getting the same message.
Device verification failed on boot.. Everything is stable and working fine.
I'm sorry if the post is not in the right place.
I own a z2 force that turned itself off and the rear camera did not work.
Putting the "power low" message on the recovery screen, even when the full charge appeared, after a time off "power ok" was displayed.
One moment he did not call any more and I tried bootloader, but without being able to activate usb debugging (my fatal error!), Now the message "your device is corrupted. It can not be trusted and it does not boot" and I can not unlock bootloader nor flash a new rom to boot the device.
obs: camera and battery problems appeared after the upgrade via ota to 8.0 actions
Solved.
eriton carlos said:
I'm sorry if the post is not in the right place.
I own a z2 force that turned itself off and the rear camera did not work.
Putting the "power low" message on the recovery screen, even when the full charge appeared, after a time off "power ok" was displayed.
One moment he did not call any more and I tried bootloader, but without being able to activate usb debugging (my fatal error!), Now the message "your device is corrupted. It can not be trusted and it does not boot" and I can not unlock bootloader nor flash a new rom to boot the device.
obs: camera and battery problems appeared after the upgrade via ota to 8.0 actions
Click to expand...
Click to collapse
I was able to start the device after hours looking for a solution, now I'm flashing a new rom to try to fix the camera problem and automatic shutdown.
How do you solve it?
I usually buy second hand Motorola phones (also this ATT Z2F), but I've never met the problem on individual hardwares yet (like camera, fingerprint sensor). Almost errors can be solved via flashing a right firmware. I think you can now flash fw via Lenovo Moto Smart Assistant (LMSA). If you use flashall.bat method, just take a look at the xml file and compare it to the content of flashall.bat (two types can be opened by Notepad, Notepad++ is recommended). The xml one shows what will be flashed.
For example: in the xml one has oem.img_sparsechunk.0-1-2, but in flashall.bat only has: fastboot flash oem oem.img
If you continue, your phone won't boot.
You have to edit flashall.bat:
fastboot flash oem oem.im_sparsechunk.0
fastboot flash oem oem.im_sparsechunk.1
fastboot flash oem oem.im_sparsechunk.2
Save and continue your works.
The xml is the standard file for RSD Lite. But, RSD seems not to be supported on recent PC hardwares, so step-by-step fastboot or flashall.bat is recently used. Therefore, just take a look before flashsing (other preparations won't be mentioned here). You should flash the equal or higher version to your current fw version on your phone.
Hope this works for you all.
i'm facing same problem,
eriton carlos said:
I was able to start the device after hours looking for a solution, now I'm flashing a new rom to try to fix the camera problem and automatic shutdown.
Click to expand...
Click to collapse
how you get repaired your phone?
Hi i have bootloop problems on this device. When i do factory reset in recovery mode samsunf logo blinks as it wants to start system but it restarts. Then second time samsung logo doesnt even finish until i do factory reset then logo blinks again and restarts after some time.
The code is (reboot recovery cause is check_boot_mode recoverybootmodewithkey)
Block based ota
Ive tried to flash device multiple times with different stock roms with same results.
If i flash with oreo its the same error code but with addition when doing fastory reser something about some cache in first deletion and a number 0
In pie that code is not present which i assume that device is ment for pie. Both frp and oem are locked.
When i flash combination file its rpmb provisioned and rpmb fused 1. In z3x box there is no option to fix that. And that is strange because as i remember while i was doing repair on samsung s8 it was easy. Factory binary was there but not on this budget model which is strange. I even tried to force error so it triggers emergency recovery mode for smart switch but smart switch is just aweful. I dont even get recognition in that program. It shows as unsuppported model. I reinstalled drivers as well it just doesnt work. Now i would be glad and it would be awesome to get into fastboot mode just so i write down commands. Adb sideload doesnt have those options. Since i understood adb and fastboot for me its number one solution for everything. But how the hell am i supposed to get into fastboot on this model. Im pretty sure block based ota is sign that its blocked becuase of oem unlock aka locked bootloader. Its a friends phone and i tell people dont do stuff if you dot know ehat you are doing. But even locked bootloaders and frp locked are fixable. Especially with multiple brains on XDA and GSMforums.
Does anybody have any solutuon to this problem because this is some kind of new security method which was not present on like 2 years before.
P. S Is there any combination out there made out of Pie?
I fixed the issue. Front camera was defected. Some type of short circuit. Main camera auto focus mechanism also defected. It works allright as soon you detach all cameras. The only problem which i have with this device is that Samsung is using same concept as HTC. One camera defected all cameras not working. This is new from Samsung because in past when one camera brakes camera app still works. Autofocus mechanism can break with fall of the phone. Its not an software issue!!!
i have a similar problem do find solution?
I recently tried to install a custom ROM in my samsung j6+ but halfway through it my PC turned off.
Then the problem starts i decided to reboot my phone but it shows this error "No command" " #Reboot recovery cause is [[check_bootmode]RebootRecoveryWithKey]#
Block-based OTA
Supported API: 3
# MANUAL MODE v1.0.0#
E:Failed to mount / cache: Invalid argument
The error message keeps appearing for just a fraction of a second then disappear and appear again
I tried to go to recovery mode but no luck i cant get to it
I drained the battery to turn off the device then go download mode but after get to it, it also keep restarting
help me please. thank you
I have a Magisk Rooted, Samsung Galaxy Note 10+ (SM-N975F), stock ROM running Android 10.
When I am booted in Root mode I try to open a file in the "My Files" app and I keep getting the error "Android System keeps stopping" but when I try in un-Rooted mode it works perfectly fine.
Is there a way around this issue that does NOT involve me having to wipe all my data and files because I believe this has something to do with anti-root implementations or something of the sort since the files open fine when I boot un-Rooted but throw the error "Android System keeps stopping" when I boot with Root.
I can provide more device information if needed, I mostly understand what I am doing but I am by no means a "Rooting Pro", I would consider myself intermediate at best.
Thanks in advance for any help that can be given.