When using Fastboot oem unlock to flash the kitkat image, I got this message:
C:\Users\riel>fastboot oem unlock
...
FAILED (status read failed (Unknown error))
finished. total time: 122.501s
Now, I cannot see to get the phone on. When I plug the phone in the PC, I hear the usb connection sound but unknown device. It did boot once after this error, and got me into a fresh 4.3. Then, after turning it off to charge, it is not turning on again.
I saw the red light very shortly, and now it is doing nothing when I press power button or power / vol down.
Any next steps? I only see 'red light fix' but maybe something went wrong with fastboot?
not to get down on you or anything, but fastboot oem unlock does not flash anything. it only unlocks your bootloader. and fastboot oem lock locks it back up. if you are trying to flash the factory image, its also done via fastboot and the bootloader, but there are other commands for it. theres a how to flash the factory image thread in general, you should check it out.
simms22 said:
not to get down on you or anything, but fastboot oem unlock does not flash anything. it only unlocks your bootloader. and fastboot oem lock locks it back up. if you are trying to flash the factory image, its also done via fastboot and the bootloader, but there are other commands for it. theres a how to flash the factory image thread in general, you should check it out.
Click to expand...
Click to collapse
I only did fastboot oem unlock for now, and rebooted.
My battery is very dead maybe? It's not turning on anymore, no lights, nothing.
Riel said:
I only did fastboot oem unlock for now, and rebooted.
My battery is very dead maybe? It's not turning on anymore, no lights, nothing.
Click to expand...
Click to collapse
It has nothing to do with fastboot. Search for Nexus 4 red light fix on this forum or google. Or let your battery charge for a while.
Riel said:
I only did fastboot oem unlock for now, and rebooted.
My battery is very dead maybe? It's not turning on anymore, no lights, nothing.
Click to expand...
Click to collapse
its possible. if you turn off the device, and plug it in, it charges?
have you flashed a custom recovery yet? try charging it a little, the go into your stock recovery(if you didnt flash a custom recovery) and factory reset/wipe data. see if you will boot then.
simms22 said:
its possible. if you turn off the device, and plug it in, it charges?
have you flashed a custom recovery yet? try charging it a little, the go into your stock recovery(if you didnt flash a custom recovery) and factory reset/wipe data. see if you will boot then.
Click to expand...
Click to collapse
it failed when he done oem unlock, so he is everything stock.
Now to fix - for me looks like eMMC fail to me,if red light fix dont work, see if u can get your phone to recognize as QHSU_DLOAD so u can use QPST to recover it.
Related
Hi, I think this should go into Dev section, but i dont have enough Posts yet... This forum is my last hope. I already did Custom Recovery, Root and Custom Rom on a different phone, but I think this time ive briked my Phone
I rooted my brandnew Play yesterday and landed in a bootloop today, i think i had a wifi Problem, however, I then tried out FrAsErTaG's FTS Customrom and everything worked fine. Afterwards I wanted to flash the DooMLoRD Kernel. Now I cant access my phone anymore... Cant get into Bootloader mode nor into flashmode or anything, the led on the Powerbutton stays black. But when i press the Powerbutton, the phone vibrates for a second and a blue or green light flashes for a millisec. When i do the same while connected via usb, the phone does nothing, and the phone isnt recognized by the pc. any Help PLEASE??? Phone was brandnew
Somehow i can access Fastboot mode now, but though i flashed another rom, the phone wont bootup.. no animation, nothing, just the vibration for a sec again.
arihellmichimich said:
Somehow i can access Fastboot mode now, but though i flashed another rom, the phone wont bootup.. no animation, nothing, just the vibration for a sec again.
Click to expand...
Click to collapse
You need to flash a new kernel/boot.img by the looks of it, maybe try flashing the stock kernel as you know it works, if boot partition is corrupt or badly flashed, flashing a rom wont solve the problem
Sent from my R800i using Tapatalk
I think i now realize what i ve done... While using fastboot, i renamed the img files by numbers - also the ClockWorkMod Recovery from this Post http://forum.xda-developers.com/showthread.php?t=1130639 where it is clearly stated that i should not flash it. I think I mixed up the numbers and flashed it and thats why i cant boot anymore... Stupid me!!! Any Idea??? I could kick my own butt right now!!! By the way, i can access CWM now via Fastboot, but booting up normaly still doesnt work of course...
arihellmichimich said:
I think i now realize what i ve done... While using fastboot, i renamed the img files by numbers - also the ClockWorkMod Recovery from this Post http://forum.xda-developers.com/showthread.php?t=1130639 where it is clearly stated that i should not flash it. I think I mixed up the numbers and flashed it and thats why i cant boot anymore... Stupid me!!! Any Idea??? I could kick my own butt right now!!! By the way, i can access CWM now via Fastboot, but booting up normaly still doesnt work of course...
Click to expand...
Click to collapse
Just flash doomlords kernel from fastboot, that has CWM embedded into the kernel, so you get to keep your recovery and get to boot your phone
just to be safe, use the command "fastboot erase boot" before you flash a kernel, this will format the boot partition so you can make a clean install
doomlord thread:
http://forum.xda-developers.com/showthread.php?t=1176502
Thanks a lot! Right now, when i connect it to the Powercable, the red led flashes every few seconds. I will try as soon, as my battery is charged again..
... I have a really bad feeling again. After the red led stopped blinking, i connected via Fastboot (blue light), erased the Boot partition and flashed DoomLords Boot Image. Sais 1 bad block encountered! (it told me already, that i had 10 bad sectors when i flashed the rom before but i didnt think this was the problem, because it bootet up at that time).
For now, i cant even get into this fastboot mode, only red light blinking.
Any other ideas please???
arihellmichimich said:
... For now, i cant even get into this fastboot mode, only red light blinking.
Any other ideas please???
Click to expand...
Click to collapse
Good luck with this. I basically did the same thing on Sunday. I gave up trying to fix late Sunday night, but when I tried again yesterday evening I'm only getting the blinking orange light. I did leave the device on charge last night, but the light didn't come on to say it was charging. How do you know your battery is charged?
I'll take AH's advice and if I ever manage to get the blue light back I'll erase boot, installed DoomLords custom kernel and then hope recovery can fix the rest.
I'll post back here if I make any progress before you (and please let us know how, if you manage to fix it in the mean time).
Daeron.
I've spent the last couple of days searching the forum, search google, search the forum some more and I've made a bit of progress.
After finding similar threads in the X10 forum I believe the flashing red light is related to the battery. Also my inability to get a fastboot blue light was caused by uninstalling SE Companion while trying to use other drivers for a Flashtool stock image flash (I didn't get that to work either). I have reinstalled SE Companion and can now connect to my PC in fastboot mode (with the blue light).
This is where my progress ends. I have tried using using this and the commandline outputs this
Code:
F:\Xperia Play\Boot Unlock\fastboot>fastboot boot recoveryPLAY.img
downloading 'boot.img'...
(bootloader) USB download speed was 41547kB/s
OKAY [ 0.549s]
booting...
(bootloader) Download buffer format: boot IMG
OKAY [ 0.003s]
finished. total time: 0.552s
but the phone does nothing except the blue light goes out. Which leads me back to the battery.
After trying to fastboot the recovery image the only thing I can do is disconnect, take out the battery, put battery back and plug into mains charger. The red light starts flashing again for a short while then I can try again with fastboot.
Next step is to leave it on charge for a few hours (only did 30mins last time) and try again. I think the reason the recovery didn't work is the battery won't hold enough charge to boot on its own, so I need a new battery
The only other thing I haven't tried is to erase partitions before booting recovery. I'll give that a go before booting recovery image in a few hours.
D.
When i boot into CWM from the boot image via fastboot. It will shut off the phone. Just unplug the device, wait a sec, and try to enter fastboot again. Usually it hangs and then goes to CWM. And when you flash a new rom, You need to factory reset in CWM clearing data and cache or else it will bootloop. Thats just basic Android rommage right thurrrr. Mine was stuck, and i just flashed the stock system.sin and kernel.sin and erase the /data and /cache with Clockwork.
fastboot flash system system.sin
fastboot flash boot kernel.sin
Sooo sorry, i didnt post before, but i moved out of my flat and had a lot of other stuff to do last week...
In the End this helped for me.
1. FULLY CHARGE YOUR PHONE!!! I was told to remove battery for 30minutes, then put it back in but without sim card and withough SD Card. Then plug the charger back and charge for at least 5-10 hours!!!
2. Connect your Phone in Fastboot mode (blue light) by pressing the searchbutton before connecting.
3. Do the steps of relocking your play through Fastboot
4. Try SE Update again with the official Sony Software, it said software could be updated :-D
So in the end, the blinking red light was just a battery problem, i couldnt imagine it was such a big deal, because i always charged for at least an hour and i thought the usb port of my netbook was at least strong enough to provide power during the flashing progress BUT IT WAS NOT!!!
Thank you soo much for the help!!!
Everything worked out fine that way.
Okay, so there is no screen protector or anything. Not rooted or unlocked or tampered in any way. I've had the phone for 26 hours and then the following happened:
EDIT: YouTube video added https://youtu.be/yAVmTz7MQbQ
I pulled the phone out of my pocket to unlock it. I see the lock screen and put in my pin (yes, I see the actual screen and stuff on it. Let me make that clear.) after I enter my pin successfully the screen locks itself. I contacted Google support and they said to factory reset it. I did the full factory data reset in the recovery mode (again, the screen works. I can see everything to do a FDR and I can see the boot animation) and it starts to boot up. Once I see the "welcome" screen it instantly locks itself. I can hear the audible "latch" locking sound that it makes when you press the power button. I know the buttons are not malfunctioning because they work perfectly fine in bootloader / recovery mode to scroll up and down and select things. I've tried multiple things but nothing seems to work. The problem here is that I want to try and do a factory image but my computer will NOT recognize my Nexus 6P when in recovery mode / bootloader mode. I have all the drivers installed but since I can't access the OS and enable OEM UNLOCKING there is no way to factory flash a factory image is there? Can someone maybe help point me in the right direction? Again, I can NOT access the OS at all whatsoever.
You just need the bootloader unlocked to flash a factory image, you can't enable that from settings o.0 so I guess your down to RMA now.
The command is now "fastboot flashing unlock"
Hey downloading a tool kit from this devices tools sections. Install the latest adb / fastboot binarys and try again
Good luck !
hutzdani said:
You just need the bootloader unlocked to flash a factory image, you can't enable that from settings o.0 so I guess your down to RMA now.
The command is now "fastboot flashing unlock"
Hey downloading a tool kit from this devices tools sections. Install the latest adb / fastboot binarys and try again
Good luck !
Click to expand...
Click to collapse
Hi Hutzdani, when I try to run the command it says "remote: oem unlock is not allowed". I have the RMA in progress but 3-5 days with no phone is going to become grueling unfortunately and I want to try everything I can. :S
xandr00 said:
Hi Hutzdani, when I try to run the command it says "remote: oem unlock is not allowed". I have the RMA in progress but 3-5 days with no phone is going to become grueling unfortunately and I want to try everything I can. :S
Click to expand...
Click to collapse
Can you run fastboot format cache and format user data? Then will anything happen ?
Sounds like you need to edit the partition that holds the data change for allow OEM unlock - there's a few threads about this on XDA for the N9 and N6 as far as I can remember.
It would seem the ability to flash a fresh system.img would solve this
last night i got the notification to say that i was able to update to 7.0 and i was so excited that i kinda forgot about xposed and stuff and now
the phone is completely useless it wont turn on it just does nothing, when its charging the white light flashes but still nothing Please help
Can you connect your phone to a computer and see if adb/fastboot still senses your device, or whether your device still shows up (or reports as a Qualcomm HS-USB)?
echo92 said:
Can you connect your phone to a computer and see if adb/fastboot still senses your device, or whether your device still shows up (or reports as a Qualcomm HS-USB)?
Click to expand...
Click to collapse
nope not seeing it
Hmm, so you're not getting anything showing up in Device Manager (like in this thread https://forum.xda-developers.com/moto-g4-plus/help/help-xt1642-hard-bricked-help-t3498943 )?
I am not familiar with the procedure of how to unbrick a device like this, vache has uploaded a blank flash file (https://forum.xda-developers.com/showpost.php?p=70701015&postcount=1975), I hope someone else can guide you on the procedure to unbrick your phone if you need such a file.
Sounds crazy, but push the power button for 2-3 minutes.... Dont know why, but worked for me in the past.
bullfinch110 said:
Sounds crazy, but push the power button for 2-3 minutes.... Dont know why, but worked for me in the past.
Click to expand...
Click to collapse
thankyou it worked perfectly
The same here after update!
I have a Moto G4 Plus, Product: athene_16mp XT1644 64GB P2A
Since last update (Nouga) my phone doesn't pass the bootloader screen. Connected to my PC, only fastboot commands works as adb don't see it. The recovery mode is dead, every time I try to enter it says:
Failed to validate recovery image. Error: Failed to pass validation, backup to fastboot. Boot up failed.
I searched the forum to find the original rom image but as I didn't Check 'Allow OEM Unlock' in Android Settings > Developer, I can't install any image from there.
Any help?
alemangioni said:
I have a Moto G4 Plus, Product: athene_16mp XT1644 64GB P2A
Since last update (Nouga) my phone doesn't pass the bootloader screen. Connected to my PC, only fastboot commands works as adb don't see it. The recovery mode is dead, every time I try to enter it says:
Failed to validate recovery image. Error: Failed to pass validation, backup to fastboot. Boot up failed.
I searched the forum to find the original rom image but as I didn't Check 'Allow OEM Unlock' in Android Settings > Developer, I can't install any image from there.
Any help?
Click to expand...
Click to collapse
If fastboot still works, perhaps try this fastboot Nougat image, see if that'll flash? https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
It requires you booting into bootloader (so power down your device, wait 5 seconds then hold the volume down and power button, should then boot into bootloader), so it might flash a working recovery and system onto your device.
bullfinch110 said:
Sounds crazy, but push the power button for 2-3 minutes.... Dont know why, but worked for me in the past.
Click to expand...
Click to collapse
I believe there are two possible reasons...
Either 2-3 minutes forces a fully hard reset.
Or
If you have a really really flat battery sometimes as it charges and then boots up it gets stuck in repeated reboot since effort to boot drains more than it can charge in that time, so holding power button holds boot sequence long enough for battery to gain enough charge to allow boot to work..
Both are just my opinions so might be completely wrong
I think it's Option no1, because in my case the battery was nearly full charged.
Nevertheless... One guy happy to have helped, the other guy happy to have reanimated his phone:laugh:
Hello everyone!
First of all - this is my first post here, so if I'm doing something wrong, please, correct me.
Three days ago i dropped my ALE-L21 into water closet (don't ask). I dismantled it and put into rice for 2 days. Today I decided to check if phone will start normally, but there is a following problem:
The phone is stuck into bootloop - after turning it on I see only the brand logo and after every 1 minute it vibrates for a while, the screen goes black and the brand logo appears once again. I tried to get it into recovery mode, but nothing happens. (none of button combination: holding power, power+volup or power+volup+voldown works. The phone always try to reboot)
I plugged it to PC and the only thing I can do is to get into fastboot (bootloader unlocked, phone rooted, but USB debugging is off, so adb doesn't see the device).
Any ideas of how can I fix that? Maybe just volume button is broken? Should I try to clean volume&power flex? Maybe there is an alternative solution to turn usb debugging mode on? Then I could try to recover it manually, with adb.
Flash the correct firmware in fastboot.
Szabi01 said:
Flash the correct firmware in fastboot.
Click to expand...
Click to collapse
How can I do that?
I can run fastboot by power+vol_down, but probably USB-debugging is turned OFF. ADB doesn't see any devices plugged in.
turbotramp said:
How can I do that?
I can run fastboot by power+vol_down, but probably USB-debugging is turned OFF. ADB doesn't see any devices plugged in.
Click to expand...
Click to collapse
If you pc doesn't recognize phone with adb or fastboot commands in fastboot you propably have some broken hardware.
But you can try this stuff if it recognize something.
Go to fastboot and flash TWRP with "fastboot flash recovery (recovery_filename_here).img" then try power + vol up, if it doesn't work you can try to extract UPDATE.APP app and flash system.img, boot.img, cust.img in fastboot. If TWRP works use this to re-install stock firmware https://forum.xda-developers.com/honor-4x/how-to/install-emui-4-1-4x-4c-g-play-g-play-t3515702.
Ok. Fastboot recognized my device, so I installed everything what you mentioned. Everything went 'OKAY', as it printed in cmd, but still there is no change. Whatever I am doing it freezes at brand logo and after some time reboots.
But I used branded ROM, which I downloaded from huawei website - it is the only one that not gives me "balong" error.
Any ideas before I give back my Huawei to the official service? Maybe there is some way to diagnose volume_up button?
Wife's phone got stuck in a bootloop last night, just stayed on the moto logo. Tried wiping cache and then data from recovery. phone now boots to moto then a black screen. I can see the device in fastboot, but not in recovery. I want to unlock the phone so that I can reflash the OS either from a custom recovery or from fastboot, but since I cant fully boot, I cant get to the developer options. This phone has never been unlocked/rooted or anything.
Is there a way to unlock the bootloader without going into the developer options and enabling it?
rokenford said:
Wife's phone got stuck in a bootloop last night, just stayed on the moto logo. Tried wiping cache and then data from recovery. phone now boots to moto then a black screen. I can see the device in fastboot, but not in recovery. I want to unlock the phone so that I can reflash the OS either from a custom recovery or from fastboot, but since I cant fully boot, I cant get to the developer options. This phone has never been unlocked/rooted or anything.
Is there a way to unlock the bootloader without going into the developer options and enabling it?
Click to expand...
Click to collapse
No there is no way to unlock bootloader without allowing OEM unlock, you're gonna wanna flash the latest version of stock available for your phone. Unfortunately I'm not very familiar with the commands so maybe another user can chime in here!
rokenford said:
Is there a way to unlock the bootloader without going into the developer options and enabling it?
Click to expand...
Click to collapse
You cannot unlock BL without "allow oem unlock" enabled.
Usb debugging you can't enable with fastboot.
You can try to erase with commands:
fastboot erase userdata
fastboot erase cache
fastboot erase customize
fastboot reboot
Give it some time.
How long are you waiting for it to boot after a factory reset? This can take 30 minutes... sometimes more.
acejavelin said:
How long are you waiting for it to boot after a factory reset? This can take 30 minutes... sometimes more.
Click to expand...
Click to collapse
I've waited at least 20 mins (not really timing it.) but with the black screen (screen on, not displaying anything) after the boot screen, how can I be sure its actually doing anything?
Honestly... Locked and stock there isn't much you can do. If we had the latest firmware image, maybe, but we are a release behind with no way knowing when, or if, we will ever get the current one.
There are two likely cases here for the cause of this problem... Actually, the cause is corruption of data on the internal emmc chip, the reason behind that corruption is the issue. It is either a faulty emmc chip or a fluke from cosmic radiation, static electricity, or who knows what. Either way, there since a factory reset isn't fixing it and we don't have a current firmware image your only option is send it in to Moto or replace it.