The other day my WiFi Xoom stopped getting past the "Motorola Dual Core" screen.
I have removed the SD card.
Android recovery mode gives me the error android with the "!"
It does this plugged in or on battery.
Not rooted.
What else should I try?
neoka said:
The other day my WiFi Xoom stopped getting past the "Motorola Dual Core" screen.
I have removed the SD card.
Android recovery mode gives me the error android with the "!"
It does this plugged in or on battery.
Not rooted.
What else should I try?
Click to expand...
Click to collapse
What were you trying to do before this hapened? Need more info to be able to help.
24348542 26
DavilaDarkness said:
What were you trying to do before this hapened? Need more info to be able to help.
Click to expand...
Click to collapse
Hadn't really done anything. Just normal use. No out of the ordinary installs. Turned it off. Next day I tried turning it on and it won't boot.
Did you ever resolve this ?? I was give one to repair for a child and it too is stuck on the red boot screen. The good thing is the person who sold it to them was a hacker and put TWRP on it of all things. I was floored when I tried to enter recovery and found teamwin.
but the problem is its still stuck on the boot screen, i did flash it 3-4 times with M604 M602 flashes and some other customs but nothing works, it completes flashing and wiping caches but always goes back to stuck on boot screen..
perhaps I have to unclock the bootloader or something for the flash to be succesfull ?
Just wanted to say I fixed it with these commands and firmware if anyone is interested. I tried everything else including flashing with twrp and wiping all caches and it didn't work, getting the stock firmware and doing it like this worked to clear boot screen endless stuck
download fastboot and adb and xoom drivers 6.4 (about 5mb) and the appropriate stock firmware. for me it was ZM604
at the command type
adb reboot bootloader
you may need to unplug and replug cable after it goes in fastboot mode.
fastboot devices
.. should return something "02a439cj0skjdke fastboot" to proceed.
fastboot oem unlock
.. look at your tablet and follow the instructions, for me it was down twice and up once to accept unlock conditions, then it reboots
on reboot press vol down 2 seconds after you see moto logo, it will enter fastboot
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot erase userdata
fastboot reboot
no need to relock after, you will see android logo and first boot pop up after 2-3 mins
Hello a year ago I updated my phone however when it was done i was greeted to the normal boot until it said droid then it stayed at the image for a while and never started. I got to AP fastboot and it said"AP Fastboot Flash Mode (s) 10.9B(*) (sha-61146a2, 2014-05-02 03:15:48) eMMC Info: Size 16GB Device is LOCKED. Static Code: 0 Battery ~~~ Connect USB Data Cable Fastboot Reason: Flash Failure" and addition to bad luck i didnt drivers installed till yesterday and my computer still does not know what it is. Can somebody help me?
P.S My phone is not rooted.
Hi everyone I first want to sincerely thank everyone that will answer to try to help me solve these problems with my nexus.
So the other day my nexus suddenly decided to stop being awesome and it started to be a pain in the ass instead.
When I turn it on it just keeps loading the booting animation of android 6 marshmallowand it never turn on. I identified this problem as a "bootloop" and i tried solving it anyway but it's being really hard and i'm almost getting no results.
I first tried with going into recovery mode. from the fastboot the recovery mode won't start, pops out a died android with a red triangle on it. Pressing volume up and power from that screen got me to another menu. I tried wiping the cache and wipe all the datas/ factory resets but no results. the crappy marshmallow animation goes on till forever.
On the screen that follow the dead android appears the error: E: failed to mount /cache (Invalid argument).
After that i tried with the famous sdk tools.
I am able to unlock the bootloader with the command [fastboot oem unlock]. however after unlocking it, if I turn the phone off and on again it auto lock itself.
i tried to flash a recovery image with the command [fastboot flash recovery recovery.img] but it won't flash. I unlock the device first, and then i try to flash the images. it says ok after the sending but on the writing says FAILED <remote: flash write failure>
same things happen flashing anything else (android factory images etc.)
I can't use adb, i d need to put the usb debugging mode from the developer options but since I coulnd't turn it on I don't know how to turn this option on.
So i discovered existed a "download mode"
Apparently for the nexus5 you have to push volume up and then connect it to the usb to enter in it. I tried many times and it just don't go to download mode (is this the correct procedure??)
I installed the last google divers, no results.
I really don't know what to do, do you guys have any ideas about how to save it?
phone details:
hammerhead d821(E) 32GB
hw version- rev 11
bootloader version: hhz12k
Cheers
Mattia
I think your emmc chip has gone bad and that is why you are getting locked bootloader everytime you reboot the phone as it is not able to hold any memory.
I suggest RMA if its in warranty
tiapnn said:
Hi everyone I first want to sincerely thank everyone that will answer to try to help me solve these problems with my nexus.
So the other day my nexus suddenly decided to stop being awesome and it started to be a pain in the ass instead.
When I turn it on it just keeps loading the booting animation of android 6 marshmallowand it never turn on. I identified this problem as a "bootloop" and i tried solving it anyway but it's being really hard and i'm almost getting no results.
I first tried with going into recovery mode. from the fastboot the recovery mode won't start, pops out a died android with a red triangle on it. Pressing volume up and power from that screen got me to another menu. I tried wiping the cache and wipe all the datas/ factory resets but no results. the crappy marshmallow animation goes on till forever.
On the screen that follow the dead android appears the error: E: failed to mount /cache (Invalid argument).
After that i tried with the famous sdk tools.
I am able to unlock the bootloader with the command [fastboot oem unlock]. however after unlocking it, if I turn the phone off and on again it auto lock itself.
i tried to flash a recovery image with the command [fastboot flash recovery recovery.img] but it won't flash. I unlock the device first, and then i try to flash the images. it says ok after the sending but on the writing says FAILED
same things happen flashing anything else (android factory images etc.)
I can't use adb, i d need to put the usb debugging mode from the developer options but since I coulnd't turn it on I don't know how to turn this option on.
So i discovered existed a "download mode"
Apparently for the nexus5 you have to push volume up and then connect it to the usb to enter in it. I tried many times and it just don't go to download mode (is this the correct procedure??)
I installed the last google divers, no results.
I really don't know what to do, do you guys have any ideas about how to save it?
phone details:
hammerhead d821(E) 32GB
hw version- rev 11
bootloader version: hhz12k
Cheers
Mattia
Click to expand...
Click to collapse
OK so ur ennc chip is NOT dead, that little Android with the triangle is stock recovery, which u can do nothing with, ur going to need a PC, preferably running ubuntu or some other form of Linux with adb and fastboot installed, i cam help with that too if u need it, once u get that settled what u need to do is this, download TWRP for ur hammerhead and rename it recovery.img, place it in a folder u have access to. Open a terminal and connect ur nexus to the pc with USB cable, and boot into bootloader. Then type this into the terminal:
cd (folder with recovery.img in it)
fastboot reboot bootloader (this should boot u back into bootloader if ur device is connected right)
fastboot flash recovery recovery.img
fastboot reboot recovery
This will boot u to TWRP in which u can perform a factory reset, if this doesn't work and ur still in a bootloop, download ur fav rom and gaps and flash it, this will take care of everything
And there is no download mode on the nexus that would be bootloader mode, so let me get this right, what system are u on, and did u try manually formatting with ADB? What happens when u do, I would force format cache, system, boot, and userdata and then flash recovery, that might work
Sent from my Nexus 6 using Tapatalk
Hello,
following problem:
Mate 9 (MHA-L29C432). Had an update on Android 8 (Oreo) made. It was perfect too. But when I did not manage to install Magisk, I did a backup of Flashfire via TWRP version B194 (Boot, Recovery, System).
Flashfire, by that I mean the program for backup and restore.
Now the phone starts in Fastboot mode, but looks different:
ERROR fashion
Attention!
Please update system again
Error!
Func NO: 15 (bl31 image)
Error NO: 1 (security verify failed!)
I can not turn off the phone !!! It always starts again, with the above screen.
It is also not possible to boot into recovery or eRecovery.
And with the above message, my PC recognizes no more device. So Fastboot still download mode is not possible.
What can I do? Can it be because of the partions, because Android 7 and 8 have other partion names?
Sorry u must write in english here!
Du musst in English schreiben hier!
My German is not very good, so you'll have to translate this if you need to.
You should still be able to boot to fastboot mode.
However, that error seems to refer to /system partition, and it has triggered AVB or verity.
I would try flashing stock system.img using fastboot, download your Oreo firmware from http://pro-teammt.ru/firmware-database/ and extract update.app, then extract system partition from it using Huawei Update Extractor. Alternatively, if Huawei Update Extractor gives you errors like it did to me, use this: https://github.com/marcominetti/split_updata.pl (you need perl for this, I use Strawberry).
When you have system extracted, flash it in fastboot using fastboot flash system system.img.
Do the same with KERNEL, extract and flash to fastboot flash kernel KERNEL.IMG
(BOOT is now split into RAMDISK and KERNEL)
(And flash recovery_ramdisk, recovery_kernel, erecovery_ramdisk, erecovery_kernel too.)
And you're not actually starting in fastboot mode, it's error mode.
You have to plug in usb and reboot and hold volume down to get to fastboot.
Thanks for the answers.
The problem is, no matter what I do, the Hamdy does not start in Fastboot. It always comes error mode. I can not turn off the phone, so far, it always showed the error mode and always starts again by itself. But now, I think, the battery is running low.
laptop45307 said:
Thanks for the answers.
The problem is, no matter what I do, the Hamdy does not start in Fastboot. It always comes error mode. I can not turn off the phone, so far, it always showed the error mode and always starts again by itself. But now, I think, the battery is running low.
Click to expand...
Click to collapse
Try plugging USB in, hold volume down and power down for a while. A while can be a minute or 2. I don't remember how long I had to hold it when I got ERROR MODE.
Alternatively you could maybe let it run out of battery, hold down volume down and plug in USB. It should get you to fastboot as soon as it starts.
Does it display different errors when you try to boot recovery/eRecovery? It should say Func error: recovery or eRecovery. If it doesn't, just keep pressing power until it does reboot and be ready with volume buttons.
Hello, battery is empty. As soon as I press the volume button and connect USB, the error mode appears. If I keep it pressed, the device restarts again and again after a few seconds. Again and again with the error mode.
laptop45307 said:
Hello, battery is empty. As soon as I press the volume button and connect USB, the error mode appears. If I keep it pressed, the device restarts again and again after a few seconds. Again and again with the error mode.
Click to expand...
Click to collapse
Have you figured it out or still looking for solution. Because I'm now in the same situation. Just error no is 14.
Ditto here , two error numbers 11 and 2. 11 is recovery and 2 is load failed!
laptop45307 said:
Hello, battery is empty. As soon as I press the volume button and connect USB, the error mode appears. If I keep it pressed, the device restarts again and again after a few seconds. Again and again with the error mode.
Click to expand...
Click to collapse
any progress?
---------- Post added at 07:38 PM ---------- Previous post was at 07:34 PM ----------
sgtduckyboy said:
Ditto here , two error numbers 11 and 2. 11 is recovery and 2 is load failed!
Click to expand...
Click to collapse
fixed?
yes, forgot to update. when my battery died down, i put it on a charger as it got up a few percent , I then held the volume down and power buttons,, booted right up to erecovery! downloaded nougat, installed and it immediately gave me the Oreo update, so i took it, been running great for a week or more now!
Sorry for gravedigging, but I am having the same problem. I followed ante0´s directions but i cant flash system cause the command is not allowed (FRP Lock). Any chance to get it running again?
laptop45307 said:
Hello, battery is empty. As soon as I press the volume button and connect USB, the error mode appears. If I keep it pressed, the device restarts again and again after a few seconds. Again and again with the error mode.
Click to expand...
Click to collapse
Hi, I was having the same problem. Mate 8 EMUI 8.
After looking everywhere and trying all the options available, I wasnt able to resolve.
Finally, I tried FunkyHuawei and got my system back through eRecovery.
Gave them the readings like version no. , build no...etc through fastboot. The required info is on their site. They then reverted with a link of the firmware which I flashed through their FuHunbrick tool. It force updates the entire full last version.
After flashing and booting, the system didnt boot but was able to go to eRecovery and restored my previous version.
If you or anyone else stuck at this error, they can try at their own risk as they dont guarantee anything.
Edit: you should and will be able to boot into fastboot once the battery is totally down and phone shuts off completely. Just press volume down button and insert usb. Try again and again if it doesnt work first time.
Thanks.
I tried to flash stock kdz with LG Flash Tool 2 days ago and process was stopped in the middle of flashing so I had to exit program and to pull my battery off. And then when I tried to turn phone on again it wouldn't boot but it showed only something about fastboot and when I'm trying to flash something with it I get unknown error.
This is what it says on screen:
fastboot int()
loading keystore failed status 5
Usb init ept @ 0x....
udc_start()
--reset---
--portchange---
fastboot: processing commands
Phone wasn't rooted and bootloader was locked, I can't access download mode anymore, neither anything else cause no matter what combination of keys I use it only boot into this.
So what are my options for this?