I had been experiencing issues with memory and decided to factory reset.
I have rooted, as this may be a result of that.
I receive the error on the boot screen, "Secure booting Error! Cause: boot certification verify"
I have tried entering the hard reset menu via Power and Vol. - .
Any guidance would be appreciated.
vgking96 said:
I had been experiencing issues with memory and decided to factory reset.
I have rooted, as this may be a result of that.
I receive the error on the boot screen, "Secure booting Error! Cause: boot certification verify"
I have tried entering the hard reset menu via Power and Vol. - .
Any guidance would be appreciated.
Click to expand...
Click to collapse
I think it's because you rooted without unlocking the bootloader. It could be something else though. Anyway, Teenybin should fix everything right up. Head over to the Android Development forum and read up.
vgking96 said:
I had been experiencing issues with memory and decided to factory reset.
I have rooted, as this may be a result of that.
I receive the error on the boot screen, "Secure booting Error! Cause: boot certification verify"
I have tried entering the hard reset menu via Power and Vol. - .
Any guidance would be appreciated.
Click to expand...
Click to collapse
I was getting the "security error" on boot and this: pastebin[dot]com/Tnf1ssjB fixed it for me.
Teenybin would do it for you
Sent from my Optimus G using Xparent BlueTapatalk 2
Related
Hi
The RSD got error when trying to flash the stock 2.3.4 uk retail version.
When trying to boot with vol keys pressed it gave me following message:
Failed to boot 4
Starting Fastboot protocal support
the phone was not unlocked. I want to flash it because i rooted my phone and was messing with it system apps until contact kept force closing. tried factory reset but didnt solve the problem.
Could anyone help me please........
Many thanks
yuan_1202 said:
Hi
the phone was not unlocked. I want to flash it because i rooted my phone and was messing with it system apps until contact kept force closing. tried factory reset but didnt solve the problem.
Many thanks
Click to expand...
Click to collapse
How exactly did you do the factory reset? It would seem from your description that you are unable to boot your phone...
First off, MODS please let me know if this is the wrong section but as it was about rooting/unlocking the nexus 9 I figured this was the correct forum.
I went with chain fires unlocking method, after unlocking and rebooting i forgot to go back and set the device up and enable USB debugging priot to rooting. Now where my problem lies is since that mistake my device attempts to reboot but sticks at rebooting with the spinning red, green, blue, and yellow dot spinning in somewhat of a circle like its attempting to boot but it never goes anywhere. This appears to be a boot loop minus a restart in between time. anyone have an idea of how to start this and start from scratch? Any help will be much appreciated.
Did you try to factory reset? Boot into boot loader and factory reset
di11igaf said:
Did you try to factory reset? Boot into boot loader and factory reset
Click to expand...
Click to collapse
Yes, i was able to resolve it. I downloaded the nexus tool kit, relocked and loaded stock firmware back on it, this fixed the issue, then using the nexus tool kit reunlocked and rooted with no problem. unsure why it got stuck on the boot image but all is resolved now running fire and ice kernal with dirty unicorns ROM.
thanks for the suggestion though.
So my phone decided to do a hardware reset while I was at work and I'm now getting the Demigod Crash Handler screen after reboot.
I am stock rooted on 4.4.2 and did nothing unusual while on break before this happened.
The error was first "hardware reset." After booting into stock recovery and performing a regular reboot, the message is now "Apps Watchdog Bark."
I've looked all over for any ideas but there doesn't seem to be very much info.
Can anyone help?
gray1ify said:
So my phone decided to do a hardware reset while I was at work and I'm now getting the Demigod Crash Handler screen after reboot.
I am stock rooted on 4.4.2 and did nothing unusual while on break before this happened.
The error was first "hardware reset." After booting into stock recovery and performing a regular reboot, the message is now "Apps Watchdog Bark."
I've looked all over for any ideas but there doesn't seem to be very much info.
Can anyone help?
Click to expand...
Click to collapse
I think it's a kernel crash. Can you get into download mode so you can restore to stock? (Turn phone off, push and hold volume up while plugging USB cable into phone)
TOT Guide- http://forum.xda-developers.com/verizon-lg-g3/general/restore-verizon-to-stock-t2827878
Alright, so after having my Fire HD 6 rooted for a few months I started experiencing some random restart issues. I decided to reset to Factory Defaults as I believe that it doesn't touch root (Please verify that one.)
Whenever I clicked on Facotory Reset, however; it immediately restarted and DID NOT RESET.
Then I tried to boot into TWRP and just reflash 4.5.3 (Downgrade) but when I tried to boot into recovery nothing happened, it just booted as normal. Thinking that it was just an error on my part, liking the wrong buttons, etc, I tried running 'adb reboot recovery'
This yielded the same result, just a normal reboot.
I have since unrooted my Kindle to try to update to 5.0.1 (To downgrade again)
Upon trying to update, I restart with no change just like in Factory Reset.
This leaves me with no Root, and no Recovery.
Next I tried using Fastboot to reset it, which now leaves me in a reboot loop that's stuck on the "Fire" logo.
TL;DR:
I have no root, I cannot get into recovery, I cannot access bootloader since ADB doesn't have permission without me giving it (Again, bootloop)
Overall, I'm kind of screwed, any help appreciated.
KeybladePaladin said:
Alright, so after having my Fire HD 6 rooted for a few months I started experiencing some random restart issues. I decided to reset to Factory Defaults as I believe that it doesn't touch root (Please verify that one.)
Whenever I clicked on Facotory Reset, however; it immediately restarted and DID NOT RESET.
Then I tried to boot into TWRP and just reflash 4.5.3 (Downgrade) but when I tried to boot into recovery nothing happened, it just booted as normal. Thinking that it was just an error on my part, liking the wrong buttons, etc, I tried running 'adb reboot recovery'
This yielded the same result, just a normal reboot.
I have since unrooted my Kindle to try to update to 5.0.1 (To downgrade again)
Upon trying to update, I restart with no change just like in Factory Reset.
This leaves me with no Root, and no Recovery.
Next I tried using Fastboot to reset it, which now leaves me in a reboot loop that's stuck on the "Fire" logo.
TL;DR:
I have no root, I cannot get into recovery, I cannot access bootloader since ADB doesn't have permission without me giving it (Again, bootloop)
Overall, I'm kind of screwed, any help appreciated.
Click to expand...
Click to collapse
Please help.... I see you random viewer >.>
I think if someone had an answer they would have posted. Unfortunately, fastboot doesn't work on the 2014 HDs, and it sounds like that's what put you into the bootloop. At this point I think your only option is to contact Amazon for replacement if you're still under warranty.
DoLooper said:
I think if someone had an answer they would have posted. Unfortunately, fastboot doesn't work on the 2014 HDs, and it sounds like that's what put you into the bootloop. At this point I think your only option is to contact Amazon for replacement if you're still under warranty.
Click to expand...
Click to collapse
You're sure fastboot doesn't work? I believe I have used it prior to this with no issues. (By the way, warranty is out >.<)
KeybladePaladin said:
You're sure fastboot doesn't work? I believe I have used it prior to this with no issues. (By the way, warranty is out >.<)
Click to expand...
Click to collapse
Bootloader screen doesn't indicate fastboot mode. Getvar doesn't return anything. If flash commands worked, I'm sure someone would have reported it.
If you haven't tried all button combinations, you should. (You know, hold down power; try power and vol down; try all three.) Without recovery that's all I can suggest. Sorry this happened.
I got the same problem too.
I tried to root and install gapps follow this tutorial. Everything work perfectly.
One day, my Fire's battery was empty and it turned off. I charged it and when it started, it falt in bootloop. The screen show amazon about 8sec and reboot.
I booted into twrp and flashed only 2 files update-kindle-full_ariel-20.5.2.2_user_522053520 and supersu, try to make it work but it didn't
Now, when i hold power button , "Amazon" and then "Fire" appear and it stuck there.
I tried to get into recovery by power and volume+ but didn't work, the screen show "Amazon" and reboot and stuck on "Fire" again.
What should I do now?
Sorry about my English.
Hello XDA.
After whipping my Moto E out the other day, I noticed that turning it on results in it just... laying there and showing me the "WARNING - BOOTLOADER UNLOCKED" message.
Around 1 1/2 years ago, it just turned itself on after clicking the power button once. Now, not even Fastboot mode helps, as choosing any of the options listed there results in the warning mentioned above. For clarification, here is everything in short:
The phone does NOT turn on normally
Using any option in the Fastboot boot menu restarts the loop (i. e. instantly goes back to warning message)
NEITHER does Minimal ADB and Fastboot recognize the device, NOR does the phone recognize the connection to any PC (I've tried 4 different PCs)
Since Fastboot is unresponsive, suggestions to restore stock recovery are useless to me
Suggestions to perform a factory reset are also useless, since Fastboot is unresponsive.
So, am I right if I suppose that this is a hard brick? Or is this somehow salvageable? If so, please help me...
Thanks in advance!
DeBedenHasen said:
Hello XDA.
After whipping my Moto E out the other day, I noticed that turning it on results in it just... laying there and showing me the "WARNING - BOOTLOADER UNLOCKED" message.
Around 1 1/2 years ago, it just turned itself on after clicking the power button once. Now, not even Fastboot mode helps, as choosing any of the options listed there results in the warning mentioned above. For clarification, here is everything in short:
The phone does NOT turn on normally
Using any option in the Fastboot boot menu restarts the loop (i. e. instantly goes back to warning message)
NEITHER does Minimal ADB and Fastboot recognize the device, NOR does the phone recognize the connection to any PC (I've tried 4 different PCs)
Since Fastboot is unresponsive, suggestions to restore stock recovery are useless to me
Suggestions to perform a factory reset are also useless, since Fastboot is unresponsive.
So, am I right if I suppose that this is a hard brick? Or is this somehow salvageable? If so, please help me...
Thanks in advance!
Click to expand...
Click to collapse
If its stuck on boot, its definitely not hard brick.
What was the android version when you wiped data?
Was there any custom recovery you used to wipe data?
You possibly wiped /system too, wiping system can result in bootloop.
Daman5202 said:
If its stuck on boot, its definitely not hard brick.
Click to expand...
Click to collapse
That's a relief. Thanks.
What was the android version when you wiped data?
Click to expand...
Click to collapse
I'm not sure about it, but I think it was 4.x.
Was there any custom recovery you used to wipe data?
Click to expand...
Click to collapse
No, there wasn't.
You possibly wiped /system too, wiping system can result in bootloop.
Click to expand...
Click to collapse
Sorry, but that doesn't make sense. The phone's been rooted for almost 2 years now, and 1 year ago, it turned on perfectly fine.
But let's assume that actually happened somehow, how do I recover from this?