I've usually managed to solve all my problems with searching around, but I seem to have hit a roadblock this time. I'll try to describe the problem as crisp as i can.
What is the state:
On turning on the phone, the phone gets stuck with this error message:
Failed to boot 1
PwrReason: PWR_KEY_PRESS
Starting Fastboot Protocol Support
If I push the volume down and try to start, it's stuck with this message:
Failed to boot 1
Entering NvFlash Recovery Mode
How I reached this state:
It happened immediately after I installed this app from the play store:
NavFree (World)
On starting the map, it asked my for the country to download, followng the selection of which it downloaded a ~128MB download. At the end of the download, the phone went blank. Nothing worked, so I had to do a hard reboot. After the reboot, I am in said state.
What I have tried:
I have the following sbfs:
1ff-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-att-us-gas_na_olpsgbattspe_p011.sbf
1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf
att-2.3.4_pudding_preroot
I first tried flashing with the 2.3.4 stock, and later with others. RSD finishes btu says fail.
No sd card, no sim card. I am not a noob, but not very much better either.
Versions:
Driver: 5.4.0
RSDLite: 5.6
Any help is appreciated.
Edit:
I realize that I am able to put the phone into fastboot mode by holding the vol + key when powering on. So i download and tried some commands.
The devices command comes back with a serial number result.
But the following commands:
moto-fastboot erase boot
moto-fastboot erase system
error out, both on the phone and in the pc as follows:
PC: erasing 'boot'... FAILED (remote: (00180001))
PH: Failed to process command erase:boot error (0x180001)
Wow.. No replies in 24 hours?
Is my post even in the correct section - mods, please help move to right place.
Related
My almost two-year-old Hero froze this morning, so I had to take out the battery, but after this I've been unable to boot, it's stuck on the HeRO screen. I can't start recovery either, the only thing working is hboot / fastboot. Erasing user data using fastboot doesn't do anything.
Also, plugging the phone into charger doesn't signalize charging – the LED doesn't light up, and the PC doesn't recognize the phone either. Only fastboot does connect the phone to the PC, but adb doesn't work and all attempts to flash a new recovery or do anything else via fastboot end with "FAILED (remote: not allowed)":
Code:
c:\adb>fastboot devices
HT97JL903267 fastboot
c:\adb>fastboot boot recovery-RA-hero-v1.7.0.1.img
downloading 'boot.img'... FAILED (remote: not allow)
c:\adb>fastboot flash boot recovery-RA-hero-v1.7.0.1.img
sending 'boot' (3972 KB)... FAILED (remote: not allow)
I tried installing the official RUU updates (2.73.405.66, 2.73.405.5 and 1.76.405.1 too) but none of them could connect to the phone, Error [170]: USB Connection error.
I was using Elelinux-Hero-2.1-update1-Reloaded with radio 63.18.55.06SU_6.35.17.03 and recovery was Amon RA 1.6.2 I guess.
The phone did a similar thing 3 weeks ago but I was able to boot into recovery and erase data and cache and it worked fine afterwards. Now only fastboot is accessible.
Is there anything else I can do at this point or is the phone dead for good?
Disregard my previous post.
I left the phone booting for 30 minutes, the battery got uncomfortably hot, but the phone booted up eventually. Then I managed to install the official RUU from here.
It didn't solve anything though – it still takes around 20 minutes to boot, the touch screen doesn't work and I get an "android.process.acore" error all the time – but since the phone seems untouched (thanks to the RUU install) I can lodge a claim and get a replacement phone hopefully.
You could try putting HEROIMG.NBH on the sdcard and booting into hboot. If you go into fastboot and press vol-down it quickly scans for files on the SD, of which heroimg is one, and if it finds them, installs them.
Can't really help more than that. My phone did that last year, took it to the shop and ended up getting a new motherboard, cause the ROM chip was knackered.
One thing I would recommend though when you get it fixed is to flash an engineering bootloader, do if it breaks again you've got none of this "remote not allow" rubbish.
Of all the times to say disregard my last post.........
Sorry about that, thanks a lot though!
I suppose some hardware is broken in my Hero as well, I will take it back to the shop tomorrow.
Thanks again!
Hi,
I get the below message whenever I reboot. It started when I tried to flash an ICS update from GB.
I have treied the solutions mentioned in the other threads on XDA but whenever I reboot I just get the error below. I cannot go into AP Fastboot message as when I select it from the menu I once again get the message below.
I dowloaded the ICS update from the Settings About Phone Update menu and it starts to install then tries to reboot to complete the installation but of course gets stuck at the first step with the below message.
I tried downloading the radio empty_radio.img file from this solution thread http://forum.xda-developers.com/showthread.php?t=1634223 and flash it using RSD lite 5.7 but when I try to select the file it is not listed as a suitable file type.
I seem to have run out of options. Please will somebody help. I am ready to punch the wall!
Thanks
Fergy
Here's the message (I have googled solutions for this but found none that mention the QA.6C but not the QA.74 as below):
The Device Error LOCKED. Status Code: 0 "
"Fastoboot AP mode (S) (Flash Failure)
QA.74
To return to normal mode - first press power key to power down
Device to LOCKED. Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable "
You haven't specified which carrier you are using. Try going to sbf.droid-developers.com and locating the ICS build version for your carrier. Download it, then extract the dukes, and point rsdlite to the xml file.
Make sure your battery doesn't go under 50% since you can't fastboot if that's the case.
Good luck
Sent from my XT894 running ICS
I am with Telstra in Australia. I bought the phone in HK.
I cannot seem to flash anything. Flash always fails.
What are dukes? I don't really understand your instructions as I am old
Thanks for answering. I really need to fix this.
hello,
part 1
I will start by that the LG G3 I got from a neighbor and she did not exactly know what her boys do to the device :angel:
I do not know if the device was in debugging mode and ROOT so I will describe the current situation:
1 If you turn on the device is stuck the logo of LG
2 he can get into a normal recovery, but after I perform Clear / Reset is back to being stuck in the logo.
3- When I try to enter download mode he entered to fastboot mode Started and wait for fastboot Processsing command.
4- My computer installed SRKtool_2.1 droidth and SRKtool_1.0.5_droidth, as well as SDK is updated.
5- I tried to make various adjustments through SRKtool and via fastboot command, the file (*.bin\*.img) send to the device from the PC but faild to write them, and I get messages:
sending laf "okay"
writing laf "failed (remote: flash write failure)
all file have the same masssage.
I try to perform repair to:
A- fastboot mode Started
B- recovery mode
from srktools and I got the same write fail massage !
He's trying to re-write the BIN files taking off from the original rom,
again he can transfer files but does not actually write the on the device,
then the device restarts and then he stuck the logo of TWRP, the expense of battery re-enters the regular recovery mode.
part 2 Updated!
From time to time the device did not enter the FASTBOOT MODE and gets to the firmware update, I install a new ROM, but !!!
the operating system install LGE Android MTP Device driver,
when I flash the rom he stack on 3% and the hardware driver turn to yellow with code 10 (device not work properly).
does LGE Android MTP Device have to be install to do the FLASH ???
the MPT can be damage and that cause the problem ?
the same problem on 2 different PC & OS (xp/7/10) with different drivers for MPT,
after you restart the mobile it returns to FASTBOOT MODE
Today I tried to root my Maxx2 with kingroot (Version 6.0 Verizon) and it shutdown and went to the bootloader menu? (srry im fairly new) anyways it says at the top Start up Failed: your device didnt start up successfully Use the Software repair assistant
connect your device to your computer to get SRA, but when i do nothing pops up! i cant boot up the phone or anything, heres the text i get when i try to boot up my phone: AP Fastboot flash mode (secure) hab check failed, failed th verify hab image boot, failed to validate boot image, ERROR: Failed to pass validation, backup to fastboot, Fastboot Reason: Fall-through from normal bootmode.
Thank you
the device was left unused for the last six months but when i tried to turn it on yesterday it turned on with an error message and the asus logo. The error message was error: invalid boot image. I downloaded the latest ROM version from asus offiicial site and tried to flash it through sd card and recovery mode but unfortunately it got stuck on 23% and eventually failed. Next time i tried to flash the room again but this tim it came with another error which is E: Can't mount/cache/recovery/last_log(invalid argument). What i did next is... i tried to flash it using adb sideload but then the error keeps on coming. When i tried the fastboot mode there was another error which is error: oem unlocking is not possible (i tried to unlock the oem because without that flashing is not possible from fastboot). The thing you should note is that :
1. debugger mode is not on
2. OEM lock is not on
3. I cant boot past the bootloop/error message which means i cant set usb debugging or oem unlock on
4. i have tried every other procdure from wipe cache/format data etc. what have i missed?
help me out.... its my crush's mobile phone.. hope you understand how much important is it to repair the device.:crying:
here are some pics please help me out
ibb(.)co/cohV5z
ibb(.)co/kyb1Ce
ibb(.)co/gGJEXe
ibb(.)co/eLnV5z
ibb(.)co/k8wOQz
remove the ( ) from (.) to go to the link of the images
Hi,
I got Z010D stuck on Invalid Boot Image ..
when i try Vol UP+Power = It gives CSC mode.
Vol Down+Power = Invalid Boot image ..
I am unable to go to recovery mode..
Any suggestions ...