Database Develop

Secure booting error [570]

Hello, I accepted the OTA lollipop update for LG L90 while being rooted and unlocked. Now my phone won't boot, it says secure boot error [570].
I tried to flash kdz but flash tool won't detect my phone. Please help!!!

Moto g 2014 xt1068 indian ver stuck in boot loop

Hello can any senior member plz help me out.
I have unlocked and rooted moto g2 2014 mobile it was working fine.
But I done a stupid thing by editing system file and overwriting it.
Then my phone stuck in boot loader
I can access recovery TWRP i tried to wipe Delvic and cache and factory resetting but it did'nt worked.
Therefore buy following the link i tried to flash with orginal frimware
www droidviewsmoto g 2014 to stock and lock the bootloader
it was not successful again it strucked in boot loop with Android dead symbol in recovery
------>> Then tried to install TWRP recovery it was successful, but unable to install super user.
There fore I tried to repeat the process buy using both sdk windows platfom tools and vfastboot
buy typing command in cmd as mfastboot.exe oem lock begin
and noticed error saying
hab check failed for boot
failed to verity hab image boot
failed to validate boot image
Plz sir can any one help me out plz

I did not face this exact error, but have faced error like image verification failed and my phone was bricked. Installing stock Lollipop didn't help. So I installed stock Kitkat via fastboot, and it worked, my phone booted successfully to Kitkat. Later I upgraded to Lollipop. Try this and let me know if it works.

Thanks for replying to my post
As it was a soft brick
I was searching so many links in xda
.... At last one link worked for me I got back my stock Lolly pop version back
XDA forums really helped me :good:

Only able to access fastboot, boot and recovery mode both fail.

Hello Guys,
Yesterday I tried to root my Moto 2g.
Unlocked it's bootloader,Installed Twrp and installed supersu. Also downloaded a custom mod(the most famous one I guess) and installed it,only to find out that the phone would no longer boot
but keep looping on the unlocked bootloader warning screen.While thinking that I had downloaded a non-compatible mod I Installed another one.After that,booting the phone would Instantly
take me to the recovery mode and keep looping the Teamwin logo.
I decided not to mess anymore with it and reinstall the stock firmware for moto 2g. After Installing it the Motorola logo comes up and then I am taken to the fastboot screen once again with the error saying:
"Fastboot reason,Fell through from boot recovery mode".Tried to flash CWM to see If I could get into recovery mode from there but I would get CWM logo loops exactly the same way they appeared with Teamwin logo.
Seems like phone is dead to me but still have a bit of hope,although the only place I can get is fastboot.
Edit:I tried to fastboot flash boot boot.img the stock image and I got and error saying that boot.img(10mb) exceeded the partition limit

shatterbb said:
Hello Guys,
Yesterday I tried to root my Moto 2g.
Unlocked it's bootloader,Installed Twrp and installed supersu. Also downloaded a custom mod(the most famous one I guess) and installed it,only to find out that the phone would no longer boot
but keep looping on the unlocked bootloader warning screen.While thinking that I had downloaded a non-compatible mod I Installed another one.After that,booting the phone would Instantly
take me to the recovery mode and keep looping the Teamwin logo.
I decided not to mess anymore with it and reinstall the stock firmware for moto 2g. After Installing it the Motorola logo comes up and then I am taken to the fastboot screen once again with the error saying:
"Fastboot reason,Fell through from boot recovery mode".Tried to flash CWM to see If I could get into recovery mode from there but I would get CWM logo loops exactly the same way they appeared with Teamwin logo.
Seems like phone is dead to me but still have a bit of hope,although the only place I can get is fastboot.
Edit:I tried to fastboot flash boot boot.img the stock image and I got and error saying that boot.img(10mb) exceeded the partition limit
Click to expand...
Click to collapse
try flashing the whole Stock Firmware
It might help,
U said u flashed a MOD over stock ROM?
If so, u should have boot first Just After unlocking the bootloader before Flashing any MODs

raj_45 said:
try flashing the whole Stock Firmware
It might help,
U said u flashed a MOD over stock ROM?
If so, u should have boot first Just After unlocking the bootloader before Flashing any MODs
Click to expand...
Click to collapse
I did boot after unlocking and normally flashed whole stock firmware.This morning I woke up and the error message in fastboot is 'boot up failed' for bot normal and recovery mode

shatterbb said:
I did boot after unlocking and normally flashed whole stock firmware.This morning I woke up and the error message in fastboot is 'boot up failed' for bot normal and recovery mode
Click to expand...
Click to collapse
is this your problem

raj_45 said:
is this your problem
Click to expand...
Click to collapse
Ok let me explain the situation better.Last night I used a stock firmware I found and flashed it.When I tried to boot I would see motorola logo once
fore boot mode,Then it would go to recovery so I would see it for a second time and then I would see teamwin logo looping so the phone was not
able to get into recovery mode but only into bootloader.
After That I flashed CWM and the same thing would happen with CWM logo looping now in recovery mode.
Today I woke up and flashed CWM again,and for some reason I could get into CWM and use it normally
So what I did is Installed Supersu and a mod for my xt1068 and tried to boot but phone stuck in the same endless loop again and I also cant get
into CWM again as its logo keeps flashing instead of taking me into the menu.
I believe there is an error with my data folder or partition or w/e.
Most of all I want to be able to get into CWM again

shatterbb said:
Ok let me explain the situation better.Last night I used a stock firmware I found and flashed it.When I tried to boot I would see motorola logo once
fore boot mode,Then it would go to recovery so I would see it for a second time and then I would see teamwin logo looping so the phone was not
able to get into recovery mode but only into boot loader.
After That I flashed CWM and the same thing would happen with CWM logo looping now in recovery mode.
Today I woke up and flashed CWM again,and for some reason I could get into CWM and use it normally
So what I did is Installed Supersu and a mod for my xt1068 and tried to boot but phone stuck in the same endless loop again and I also cant get
into CWM again as its logo keeps flashing instead of taking me into the menu.
I believe there is an error with my data folder or partition or w/e.
Most of all I want to be able to get into CWM again
Click to expand...
Click to collapse
So u are not able to get into Recovery
And u can get to Fast boot Mode?
If yes Flash TWRP latest(3..1.0-0)
Boot into TWRP
Reset or Install any Custom ROM like LiniageOS or AOSP
I think it's the problem with SuperSU?
Which MOD did u install?

raj_45 said:
So u are not able to get into Recovery
And u can get to Fast boot Mode?
If yes Flash TWRP latest(3..1.0-0)
Boot into TWRP
Reset or Install any Custom ROM like LiniageOS or AOSP
I think it's the problem with SuperSU?
Which MOD did u install?
Click to expand...
Click to collapse
Thanks for the replies,I managed to solve the problem and install Cyanogenmod.I guess everything came up to this:
After the first time I installed twrp I decided to wipe my data folder but somehow it was deleted and the partition became raw type which caused
all the bootlooping problems.
Using CWM I was able to get into recovery mode and then I chose to format my data folder and sd card(as ext4 I guess) and the data folder was
recreated.
After that I normally flashed Cyanogenmod and device booted just fine

Forced recovery stuck at 5%

Hey all. I was trying to rollback my P9 to a stock ROM, but it failed and now I am stuck with a bricked P9 (bootloop).
My phone is a European P9 (EVA-L09C432). I have an unlocked bootloader.
- Huawei eRecovery and HiSuite restore does not work.
- I've tried forcing the update using the SRK Tool brick utility, but receive the message "FAILED (remote: sparse flash write failure)" when it's strats writing 'system'.
- My TWRP backup does not work, I had a 7GB backup that installs fine, but the phone is still stuck in a bootloop.
- I can flash EVA-L09C432B378 ROM using the SRK brick utility fine, but the phone is still stuck in a bootloop.
- After I have installed B378 and try to force flash B136 using the dload method, it either gets stuck on the "going into restore mode" or it goes to the "installing package" screen, where it is stuck at 5% until it reboots.
Any suggestions?

try one more time install rollback package by download mode

I've tried. Several times, all day :crying: My process:
Write TWRP from fastboot so I can boot into TWRP and transer UPDATE.app to the dload folder
Reboot into fastboot
Write stock recovery image from fastboot
Boot into recovery mode
Get stuck at 5% on the "Installing update" screen.
I've tried the UPDATE.app or firmware B136 (stock), and UPDATE.app for B378 (Nougat)
Both get stuck at 5%.
I'm stuck at the bootloop

isn't srk tool only for MM?
maybe try extract recovery , boot and system partition from b378 and flash by fastboot , next start flash rollback package by download mode

I noticed when I tried to restore my backup using TWRP it failed at "vendor" (Failed to wipe vendor). I receive this issue at vendor and product.
I tried using fastboot to flash vendor and product manually, I receive these error messages:
"failed: remote command not allowed"
The phone won't allow me to write vendor and product.img... but my bootloader was unlocked?
Is it possible I could have relocked my bootloader? How am I supposed to get the bootloader code for my P9 again :/ It's nearly impossible.

I managed to use the recovery dload method to install a beta version of B378 (build number NRD90M test-keys). Will now try to use the recovery method to roll back to B136 and update back to B378 again.

Highfall said:
I managed to use the recovery dload method to install a beta version of B378 (build number NRD90M test-keys). Will now try to use the recovery method to roll back to B136 and update back to B378 again.
Click to expand...
Click to collapse
I'm having similar issues. Have you solved your problem? What have you tried so far?

Same problem here! Did you resolve?
Thanks you.

Try unplug charger or usb cable then do it

WTF, that ist the solution to the whole damn problem! Just unplugging the damn usb cable and it installs the update just fine. ive spend 2 whole days on this, almost giving it up beacuse everytime it got stuck at 5% and then this...
seriously thank you!

JimmyEatFood said:
Try unplug charger or usb cable then do it
Click to expand...
Click to collapse
thx i managed to boot my device, but i relocked bootloader and factory reset doesnt work correctly it deleted 3rd party apps and leaved few system apps and blotware. what should i do.
and really thanks, you saved me.

Removing cabled worked for me also

Flashing TWRP

I'm trying to flash TWRP on the phone.
I unlocked OEM bootloader and enabled USB debugging.
I also waited for the 7 days to be able to flash.
When I try to flash TWRP I get an error: "error validating footer (6)". It was going into a download mode loop so I reinstalled stock rom which is now running again.
Does anyone have advise on the error that I'm getting?

lintwurm said:
I'm trying to flash TWRP on the phone.
I unlocked OEM bootloader and enabled USB debugging.
I also waited for the 7 days to be able to flash.
When I try to flash TWRP I get an error: "error validating footer (6)". It was going into a download mode loop so I reinstalled stock rom which is now running again.
Does anyone have advise on the error that I'm getting?
Click to expand...
Click to collapse
Have you disabled auto reboot in odin? Always do that when flashing twrp.
Also do you have other twrp version to flash?
Also try redownloading twrp as your twro moght be corrupted.

LR7875 said:
Have you disabled auto reboot in odin? Always do that when flashing twrp.
Also do you have other twrp version to flash?
Also try redownloading twrp as your twro moght be corrupted.
Click to expand...
Click to collapse
Thank you so much for your reply! I did redownload TWRP and the same error occurred.
I tried with auto reboot disabled but get an error message: "Error validating footer (6)
CUSTOM RECOVERY
VBMETA " and then some numbers...
Thanks again!

I tried again with auto reboot disabled.
I then restarted the phone by pressing vol down+power.
As soon as the screen went black I then held vol up+power and got the error:
"Error validating footer (6)
CUSTOM RECOVERY
VBMETA " and then some numbers...
Maybe I'll try with an older version of TWRP...

Try this.
[GUIDE] Flash TWRP 3.4.0.0 and Root Android 10 ( Fix vbmeta error )
Disclaimer I'm not responsible if something went wrong on your phone(Usually nothing goes wrong). You are doing this on your own responsibility. Installing TWRP and Rooting may void warranty. The bootloader must be unlocked, if not watch this...
forum.xda-developers.com

LR7875 said:
Try this.
[GUIDE] Flash TWRP 3.4.0.0 and Root Android 10 ( Fix vbmeta error )
Disclaimer I'm not responsible if something went wrong on your phone(Usually nothing goes wrong). You are doing this on your own responsibility. Installing TWRP and Rooting may void warranty. The bootloader must be unlocked, if not watch this...
forum.xda-developers.com
Click to expand...
Click to collapse
I will try that later tonight thanks!