Hi,
Today I installed an update for my Moto G4, and the phone crashed while it was installing. Now I'm stuck at the bootloader with the error,
"Start Up Failed:
Your device didn't start up successfully. Use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the Software Repair Assisstant."
and the log underneath states,
"Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Boot up failed"
I have tried recovery mode and factory mode, to no avail. I also tried to flash the rom of the XT1625 that is on Motorola's website, but it ends up failing validation. Is there anything I can do, or do I now have a shiny new brick?
Can you remember what update your device was installing before it failed?
If you're running a retail (non-Amazon branded) XT1625, have a look at flashing this NPJ25.93-14.5 firmware (June 2017 security patch): https://androidfilehost.com/?fid=673368273298984458 or NPJ25.93-14.7 (Sept 2017 security patch) firmware: https://androidfilehost.com/?fid=817906626617945295
Related
Hello. I have a XOLO Play Tegra Note 7.
A couple of days back I, in an attempt to flash a ROM that I downloaded from the NVIDIA website, I accidentally flashed a boot file from a CyanogenMod image that I downloaded for another purpose. Now, I'm neither able to flash the correct boot image (it is not recognised by adb) nor apply update through bootloader recovery (it says E:footer is wrong, E:signature verification failed). All that's happening is that its bootlooping.
Hi,
I have problems to get root access on my LG G2 (D802). I have a refurbished Vodafone device, which runs with the Lollipop version (5.0.2). The phone boots into the OS and works fine (as you can say with 5.0.2), but I want switch to CM13.
Unfortunately I can't access the download mode: I got the "Boot certification verify" error, which results in a DemiGod Crash Handler. I know, I should flash the phone with a stock version. But: I can't downgrade this phone - I tried every LG flash tool version.
Either the LGMobile Tool Suite says I already have the latest Firmware (trying to install a older version -.-), the process just stops because the phone is missing a functional download mode or the whole process just stops at 4% within the "S/W Upgrade is in process"-task and ends with a error message ("Upgrade stopped due to an error").
When doing the command "adb reboot recovery", the phone restarts. Sadly I only see the droid laying with an exclamation mark. I once accomplished (still don't knowing how) to get the options and I tried to install the kk_root.zip with the command "adb sideload", but there is another issue/error message: "E:failed to verify whole-file signature / E:signature verifcation failed"
Is there any other way to get around this mess and to install CM13?
Thanks in advance,
dash
Hello!
Everytime that I try to update my system to NPN25.137-35 from NPN25.137-33 I get an error while it updates. Then, when it is rebooted it gets stucked in the "Your device has failed verification and may not work properly" screen which I have to reinstall the stock firmware to get it working again. My question is, can I install the NPN25.137-35 directly from my computer via ADB and fastboot? Or I must update it normally in order to change the system?
Thanks.
U can direct install from Ur PC...
Sent from my Moto G (5) Plus using Tapatalk
Backstory:
Received the message "Custom binary blocked by FRP lock" when restarting my phone. I had a custom ROM installed so this was probably why, but I had flashed no-verity-opt-encrypt previously so I don't know why I randomly got this message.
Tried to flash the latest Android 8.0.0 stock firmware from sammobile, successfully flashed through Odin but when the phone boots it keeps looping into recovery, followed by "No command".
When I try to access the recovery settings by pressing power+up it comes with:
fail to open recovery_cause(No such file or directory)#
Reboot Recovery Cause is [UNKNOWN]# No Support SINGLE-SKU
Along with a bunch of lines saying failed to mount /system and dm-verity failed.
I've tried flashing many different stock ROMs but only the factory binary combination ROM is able to boot up. Therefore, I cannot turn off FRP lock. I am struggling to find out why, even though Odin successfully flashed the whole stock BL, AP, CP and CSC, the recovery cannot be opened.
Any ideas would be greatly appreciated.
Edit: Managed to fix it through a YouTube video by Mr.Lee
Try downgrading to nougat or marshmallow. That should remove FRP.
Sent from my SM-G935FD using Tapatalk
I've tried but I cannot find any marshmallow/nougat version which does not result in a SW REV CHECK FAIL error, my kernel only accepts Oreo or higher it seems.
Hello everyone!
Today i tried to install twrp on my s10+ SM-G765F/DS to install android 12 lineage os.
I placed TWRP at AP and VBmeta at CS.
VBmeta was stuck at the installing phase, for a very long time too.
I decided to quit Odin and unplug the phone.
Error showed up : An error uas occured while updating the device software. Use the emergency revovery function in the Smart Switch PC software.
Using smart switch pc : device dosent show up
FRP Bypass : into download mode, tried flashing original firmware, back to download mode, tried flashing twrp, didn't work, with vbmeta and without.
top left said:
ODIN MODE (AVB FAIL)
recovery: Error validating footer. (0)
recovery: Error verifying vbmeta image : invalid vbmeta footer (6)
CUSTOM RECOVERY
VBMETA G975FXXSBFUE6, 40448985R
Please help me, i dont know what this means and whether my phone can be saved.
I have found a fix.. to everyone who is facing this problem, here is what you need to do.
1.get frija ( you will need visual c++ 2010 and 2008.)
2. obtain your model number and your csc ( found if you search up your carrier in sammobile along with your phones model number product code in my case, i got it under starhub in Singapore therefore, STH)
3. key in the details into frija
4. download the firmware from frija.
5. frija will give you a rar with your firmware, unpack that.
6. match the BL, AP, CS and CSC with the firmware and start.
The process will take a while as its a big file but your phone will be saved!
precautionary measures if you were to attempt again
1. keep the firmware files
2. use a good version of Odin, my error happened because my version of odin didnt work.
3. do a lot of research
For me with my S10+ G975F, this saved me:
An error has occured while updating the device software.
Hello everyone! Today i tried to install twrp on my s10+ SM-G765F/DS to install android 12 lineage os. I placed TWRP at AP and VBmeta at CS. VBmeta was stuck at the installing phase, for a very long time too. I decided to quit Odin and unplug...
forum.xda-developers.com