Hello,
As the title says I'm stuck in fastboot mode none of the options (Start, Restart bootloader, Recovery mode, Rescue mode) work.
I get error on the following:
NOS production: error!
Device state: error!
Enter reason: boot failure
The device has been sent to Google service center, and was denied warranty because of a small dent in top right corner.
They did not repair the device either and just sent it back to me.
The device is not listed when running adb devices, but is when running fastboot devices.
I'm trying to flash stock image files downloaded from google, but the problem here is that whatever I try to do I get "error getting device locked state -1".
And what I can find on the internet you need to enable OEM unlock and USB debugging.
Since I can't get the phone to boot that's impossible.
Is there anyway to unlock the device just by using fastboot?
Or is this phone just a very expensive paper weight?
Thank you for any help regarding this.
Have you tried flash.android.com? It might work if it finds fastboot.
superior888 said:
Have you tried flash.android.com? It might work if it finds fastboot.
Click to expand...
Click to collapse
Thank you for the tip, tried but same problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Update picture of the dent.
Just so you all know that the dent is not critical.
Red arrow put there by google service center.
What did you do beforehand that would not allow it to boot now? Anything in particular? Did it boot when you got the phone back?
Silly question maybe, but have you tried to hold the power button down until it boots?
A couple things you might try in fastboot (I take no responsibility given I have no idea how you got into the state you are in and this will erase your data):
fastboot -w
Then see if you can boot
fastboot reboot or power button
or
fastboot format userdata
Then see if you can boot
fastboot reboot or power button
However, I fear you may get the same "device is locked" error when trying this.
Another Option:
Leave in fastboot mode with phone unplugged until battery dies
Let phone sit for a while after battery dies
Hold down power button and plug into charger
Hopefully it boots
Also, have you tried to see if it boots in Safe Mode?
Lughnasadh said:
What did you do beforehand that would not allow it to boot now? Anything in particular? Did it boot when you got the phone back?
Silly question maybe, but have you tried to hold the power button down until it boots?
A couple things you might try in fastboot (I take no responsibility given I have no idea how you got into the state you are in and this will erase your data):
fastboot -w
Then see if you can boot
fastboot reboot or power button
or
fastboot format userdata
Then see if you can boot
fastboot reboot or power button
However, I fear you may get the same "device is locked" error when trying this.
Another Option:
Leave in fastboot mode with phone unplugged until battery dies
Let phone sit for a while after battery dies
Hold down power button and plug into charger
Hopefully it boots
Also, have you tried to see if it boots in Safe Mode?
Click to expand...
Click to collapse
"What did you do beforehand that would not allow it to boot now? Anything in particular? Did it boot when you got the phone back?"
Answer: I was watching TikToks and noticed that the phone got hotter than usual. So I closed the app and locked the phone. When I was trying to unlock the phone it didn't recognize my fingerprint. And said my PIN code was wrong, so I rebooted the phone and then I was stuck in fastboot mode.
"Silly question maybe, but have you tried to hold the power button down until it boots?"
Answer: Yep, didn't work.
"fastboot -w
Then see if you can boot
fastboot reboot or power button"
Answer: Don't work fastboot -w just gives the device locked state -1 error. Fastboot reboot and power button restarts phone back to fastboot mode.
"fastboot format userdata
Then see if you can boot
fastboot reboot or power button"
Answer: Fastboot format userdata gives the following error:
fastboot: error: Formatting is not supported for file system with type 'raw'
"Leave in fastboot mode with phone unplugged until battery dies
Let phone sit for a while after battery dies
Hold down power button and plug into charger
Hopefully it boots"
Answer: Boots right back up into fastboot mode.
"Also, have you tried to see if it boots in Safe Mode?"
Answer: Back into fastboot mode.
Thank you for all your help.
I guess
'fastboot format cache' and
'fastboot reboot recovery' doesnt work?
superior888 said:
I guess
'fastboot format cache' and
'fastboot reboot recovery' doesnt work?
Click to expand...
Click to collapse
fastboot format cache give the following error:
FAILED (remote: 'variable (partition-type:cache) not found')
fastboot reboot recovery reboots phone to fastboot mode.
Thank you.
lang0liers said:
"fastboot format userdata
Then see if you can boot
fastboot reboot or power button"
Answer: Fastboot format userdata gives the following error:
fastboot: error: Formatting is not supported for file system with type 'raw'
Click to expand...
Click to collapse
I'm afraid I have bad news for you. There is no software fix for your issue as this is a hardware problem. The flash storage has failed and the clue is in the output of the fastboot command above. A file type of "raw" means there is no master boot record or equivalent in the flash storage. All your attempts at fixing via software fail because a side effect of the flash storage failure is to place the storage into a pemanent read-only state.
In simpler language the phone is a brick with no possibility of recovery short of cracking open the phone and trying to replace the flash storage.
That sucks. I'm a little bit concerned google didn't repair it due to it had been dropped? That shouln't really **** up the phone this much.
It didn't. Google used it however as a reason to void the warranty.
lang0liers said:
"What did you do beforehand that would not allow it to boot now? Anything in particular? Did it boot when you got the phone back?"
Answer: I was watching TikToks and noticed that the phone got hotter than usual. So I closed the app and locked the phone. When I was trying to unlock the phone it didn't recognize my fingerprint. And said my PIN code was wrong, so I rebooted the phone and then I was stuck in fastboot mode.
"Silly question maybe, but have you tried to hold the power button down until it boots?"
Answer: Yep, didn't work.
"fastboot -w
Then see if you can boot
fastboot reboot or power button"
Answer: Don't work fastboot -w just gives the device locked state -1 error. Fastboot reboot and power button restarts phone back to fastboot mode.
"fastboot format userdata
Then see if you can boot
fastboot reboot or power button"
Answer: Fastboot format userdata gives the following error:
fastboot: error: Formatting is not supported for file system with type 'raw'
"Leave in fastboot mode with phone unplugged until battery dies
Let phone sit for a while after battery dies
Hold down power button and plug into charger
Hopefully it boots"
Answer: Boots right back up into fastboot mode.
"Also, have you tried to see if it boots in Safe Mode?"
Answer: Back into fastboot mode.
Thank you for all your help.
Click to expand...
Click to collapse
Not looking good, as others have said. Only other thing I can think of is:
fastboot format:ext4 system
or
fastboot erase system
fastboot format:ext4 system
Not hopeful though...
Thank you all for your help.
I tried once more sending the product under warranty, but since the Pixel phone is not sold in my country and the company I bought it from didn't want to send it one more time to Google I disassembled the phone.
Before that I tried once more to empty the battery and the following commands:
fastboot format:ext4 system
fastboot erase system
fastboot format:ext4 system
But the I just got back that it couldn't find the partition named "system".
Also tried
fastboot format boot
fastboot format userdata
And got back:
fastboot: error: Formatting is not supported for file system with type 'raw'
So I opened the phone and if you look at the attached picture I believe that's where the heat came from.
So if anyone has a spare mother board for a Pixel 6, I'm intrested
lang0liers said:
Thank you all for your help.
I tried once more sending the product under warranty, but since the Pixel phone is not sold in my country and the company I bought it from didn't want to send it one more time to Google I disassembled the phone.
Before that I tried once more to empty the battery and the following commands:
fastboot format:ext4 system
fastboot erase system
fastboot format:ext4 system
But the I just got back that it couldn't find the partition named "system".
Also tried
fastboot format boot
fastboot format userdata
And got back:
fastboot: error: Formatting is not supported for file system with type 'raw'
So I opened the phone and if you look at the attached picture I believe that's where the heat came from.
So if anyone has a spare mother board for a Pixel 6, I'm intrested
View attachment 5531673
Click to expand...
Click to collapse
Oof, that's fried
How can google even deny warranty for that?
superior888 said:
How can google even deny warranty for that?
Click to expand...
Click to collapse
The warranty only covers manufacturer defects. The damage could have been a result of dropping the unit, which isn't covered by warranty. Not to mention the OP's country is not one where the unit is sold, so he has no warranty regardless.
Strephon Alkhalikoi said:
The warranty only covers manufacturer defects. The damage could have been a result of dropping the unit, which isn't covered by warranty. Not to mention the OP's country is not one where the unit is sold, so he has no warranty regardless.
Click to expand...
Click to collapse
Well, the warranty is valid in the whole EU, so if you live in a another country you just need to send it to the country where you bought the phone from.
jnsson said:
Well, the warranty is valid in the whole EU, so if you live in a another country you just need to send it to the country where you bought the phone from.
Click to expand...
Click to collapse
Apparently this is how the OP sought warranty service the first time. Google denied his warranty.
Sorry to read through this thread as my Pixel 6 Pro is exhibiting the same symptoms, after being in my car, in the shade, for 4 hours. Exact same fastboot screen, exact same response to all the helpful suggestions.
How widespread is this problem? I'm gun-shy to get another Pixel 6 Pro after this
finnd1 said:
Sorry to read through this thread as my Pixel 6 Pro is exhibiting the same symptoms, after being in my car, in the shade, for 4 hours. Exact same fastboot screen, exact same response to all the helpful suggestions.
How widespread is this problem? I'm gun-shy to get another Pixel 6 Pro after this
Click to expand...
Click to collapse
Seems to not be an isolated incident as I've had this happen last week with the exact same symptoms about the pin and fingerprint sketchy... Only that I simply turned it off to put a screen protector on it.
Luckily I'm still in warranty but the fact that op opened theirs up and clearly identified a cooked chip is a bit worrying for 'replacements' they send out.
Related
So I have a Telus version of the HTC One X+ 64GB. I have been pretty familiar with flashing roms on samsungs. Wasn't the case so much with the HTC. So I decided to unlock boot loader, root, and flash a custom recovery. Decided to flash this rom from this thread. http://forum.xda-developers.com/showthread.php?t=2219520 not understanding how the boot.img works well guess what I didn't flash that. Now I'm stuck on the Panandriod 3+ boot logo. The phone from my understanding don't seem to wanna charge. Just gets a slow blinking red notification light. When I was able to get into recovery when the battery had charge I was unable to get the ad card to mount so I could add the boot.img to the phone to get fast boot to flash it. I have all the drivers installed on the PC but unsure if maybe the reason that recovery is unable to mount is because of HTC Sync is installed on the PC as well?
The whole reason for trying to flash a rom on this HTC is because I have the HTC One Developer Edition on the way and I wanted to learn as much about flashing HTC as I could so I wouldn't mess up and brick my HTC One when it came. Nowwwww I'm not so confident.
Two days research I have a little more knowledge but still unable to find a good thread or resource to fix this problem. I was able to get some charge thru to the phone when I selected recovery and it went to a black screen with the notification light pulsing red. It seems like its not fully bricked. I tried to use Cmd in windows to try and communicate and see if he phone would respond to the fast boot commands but to no lunch Cmd cannot find the phone. Do anyone know where I could start? Is there a tool kit that can send me back to stock? It was running 4.1.1 any help in the right direction would be great. Thank you guys.
You HAVE to flash the boot.img! Flash it in fastboot
fastboot flash boot boot.img
Without the new boot.img (which is the kernel) your Rom will not run.
Download the pizza boot.img
sixcarnage said:
You HAVE to flash the boot.img! Flash it in fastboot
fastboot flash boot boot.img
Without the new boot.img (which is the kernel) your Rom will not run.
Download the pizza boot.img
Click to expand...
Click to collapse
Hey thanks for replying
I downloaded the pizza boot.img but the issue I'm facing is charging it seems either very very slow on black screen or maybe it's not charging? But main issue is that PC cannot find the One X+ I will try this command but where do I place the pizza boot.img on windows?
The only thing is getting me is I'm getting the sound from windows when you connect a device when I plug the phone in USB but the cmd so far that I have tried even the All in one toolkit don't seem to see that the phone is connect USB in fast boot or boot loader mode. Think this is due to not enough charge? Plus should I just leave it in custom recovery to charge which is a black screen due to it says not enough charge to flash to charge my device?
sixcarnage said:
You HAVE to flash the boot.img! Flash it in fastboot
fastboot flash boot boot.img
fastboot erase cache
Without the new boot.img (which is the kernel) your Rom will not run.
Download the pizza boot.img
Click to expand...
Click to collapse
Corrected.
Gene1985 said:
Two days research I have a little more knowledge but still unable to find a good thread or resource to fix this problem.
Click to expand...
Click to collapse
I can hardly believe you didn't find anything that help you with this issue on this forum.
First is your SDK/ADB tool install on your computer?
It's not that complicated to flash the boot.img. Take the pizza boot.img and put it in your platform-folder of your SDk tool. Reboot your phone by holding Volume down and pressing Power button. In bootloader plug in your USB cable and at the prompt confirm that your computer is seen by typing this >fastboot devices if you have your serial confirmation then simply proceed with this at the prompt>fastboot flash boot insert_pizza_name_boot.img (enter) again at the prompt>fastboot erase cache (enter) the for rebooting >fastboot reboot (enter)
If you need more infos, you have everything required in my signature to help you.
Do you have the latest TWRP
Lucky Thirteen said:
Corrected.
I can hardly believe you didn't find anything that help you with this issue on this forum.
First is your SDK/ADB tool install on your computer?
It's not that complicated to flash the boot.img. Take the pizza boot.img and put it in your platform-folder of your SDk tool. Reboot your phone by holding Volume down and pressing Power button. In bootloader plug in your USB cable and at the prompt confirm that your computer is seen by typing this >fastboot devices if you have your serial confirmation then simply proceed with this at the prompt>fastboot flash boot insert_pizza_name_boot.img (enter) again at the prompt>fastboot erase cache (enter) the for rebooting >fastboot reboot (enter)
If you need more infos, you have everything required in my signature to help you.
Click to expand...
Click to collapse
Thanks Lucky, I noticed tonight I went thru everything in issues and I noticed that I didn't correctly have SDK set up right on my windows. Hopefully that this is the issue and that when I set it up right that I can fix this problem. This has been far different then Samsung to fix hahaha thanks again and kinda my bad for posting the question. But hopefully that works.
sixcarnage said:
Do you have the latest TWRP
Click to expand...
Click to collapse
No I don't have TWRP I have the recover that came in the noob tool kit. The none touch screen one lol. But I understand a fair bit on what I should have done. I'm gonna try and follow luckies link for the SDK set up and see if I can send the zip file to the phone then flash it in recovery. Just I hope the thing can charge. I had it on the charger for 4 hours today and it still said that there was not enough charge to flash I tried charging it in the boot loop and in recovery.
So I guess the issue is worse. The phone won't charge at all the red notification light blinks red but it don't seem to be charging at all I have looked for fixes and it says flash latest compatible recovery but it won't even discover the phone connected to windows with proper HTC drivers installed
Is your phone capable of booting in bootloader mode?
Lucky Thirteen said:
Is your phone capable of booting in bootloader mode?
Click to expand...
Click to collapse
Yea I am able Lucky. But what I tried today was to get RUU to recognize the phone to do that but no go. So tomorrow I'm gonna do a fresh reinstall on a new laptop of windows and install drivers again and all that. But as for boot loader mode it boots. I click recovery and I get a black screen. I can fast boot USB but I'm not quite sure about USB debugging is still turned on. If it where I'm sure I wouldn't have an issue with the PC not seeing the phone connected.
OK try this in bootloader mode with the USB plug
fasboot devices
Do you have a confirmation serial number?
Will do Lucky. Thanks for your time and patience. I will try this over the night. I really like to try and get this fixed and to understand how the htc works with installing roms and tweaks. I really don't wanna mess up my Develeper Edition of the HTC One that's on the way.
If you have your serial confirmation.
Download this recovery HERE
Move this file in your platform-tools folder
Press and hold the Shift key and right click on a empty space of that folder and select Open Command Window Here
In the command window with your phone in FASTBOOT USB mode
Type>fastboot flash recovery TWRP2500.img
(Success)
Type again>fastboot erase cache
(Success)
Unplug your USB cable
Hit one time Power
Select Recovery (Volume down)
Hit Power to Reboot in Recovery
Phone should charge in recovery even if the red light doesn't lit.
Just tried this on my phone with less than 10% and it worked flawlessly, after ~10 minutes my phone was at 13%+
Otherwise you will have to create a batch file and run it while your phone is in FASTBOOT USB mode :
Code:
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
That should allow your phone to charge to the minimal required to flash or to re-unlock your bootloader.
Lucky Thirteen said:
If you have your serial confirmation.
Download this recovery HERE
Move this file in your platform-tools folder
Press and hold the Shift key and right click on a empty space of that folder and select Open Command Window Here
In the command window with your phone in FASTBOOT USB mode
Type>fastboot flash recovery TWRP2500.img
(Success)
Type again>fastboot erase cache
(Success)
Unplug your USB cable
Hit one time Power
Select Recovery (Volume down)
Hit Power to Reboot in Recovery
Phone should charge in recovery even if the red light doesn't lit.
Just tried this on my phone with less than 10% and it worked flawlessly, after ~10 minutes my phone was at 13%+
Otherwise you will have to create a batch file and run it while your phone is in FASTBOOT USB mode :
Code:
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
That should allow your phone to charge to the minimal required to flash or to re-unlock your bootloader.
Click to expand...
Click to collapse
Thanks Lucky. I will try this first thing in the A.M I hope that works.
Lucky Thirteen said:
If you have your serial confirmation.
Download this recovery HERE
Move this file in your platform-tools folder
Press and hold the Shift key and right click on a empty space of that folder and select Open Command Window Here
In the command window with your phone in FASTBOOT USB mode
Type>fastboot flash recovery TWRP2500.img
(Success)
Type again>fastboot erase cache
(Success)
Unplug your USB cable
Hit one time Power
Select Recovery (Volume down)
Hit Power to Reboot in Recovery
Phone should charge in recovery even if the red light doesn't lit.
Just tried this on my phone with less than 10% and it worked flawlessly, after ~10 minutes my phone was at 13%+
Otherwise you will have to create a batch file and run it while your phone is in FASTBOOT USB mode :
Code:
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
That should allow your phone to charge to the minimal required to flash or to re-unlock your bootloader.
Click to expand...
Click to collapse
worked like a charm Lucky. thanks i followed all the steps now im up and running. thanks again.
Great! This is a good news!
Please take the time to edit your OP and change your title to this : [SOLVED] BAD FLASH!!!! NOOB. Possible Brick HELP THANK YOU.
Happy flashing now!
C:\Android\sdk\platform-tools>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (31748 KB)...
OKAY [ 1.053s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 1.076s
C:\Android\sdk\platform-tools>fastboot flashing unlock ...
(bootloader) Device already : unlocked!
OKAY [ 0.012s]
finished. total time: 0.013s
I have both oem unlock and usb debugging checked on the developer options plus i was able to unlock the devices oem through fastboot. I opened the command prompt in androids/sdk/platform tools but nothing happens just repeats recovery failed. What am I doing wrong? (My goal is to download twrp onto my lg V10)
I am having the same problem and it's driving me nuts. Any solution yet?
Which device are you on? lg has locked the fastboot commands. Until we have root you can't flash recovery. That's if installed the official ota marshmallow(6.0.1) from your carrier you lose root and you CANNOT downgrade doing so will BRICK!! your device because there is no (5.1) lollipop kdz for our device . So therefore we are stuck until the developers find a way to root it. So Be patient...
Sent from my LG-H901 using XDA-Developers mobile app
DAMN sent my v10 to lg for repair and got it back with official 6.0 on it. i'm getting the same remote unknown command error when using fastboot. Hopefully a fix soon!
I'm on the official 6.0 - not 6.0.1 referenced above. Any chance I can root? Screenshot shows my software info
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LG-H901 using XDA Free mobile app
Same here. Any Solution? Also i read we can get FM Radio in h901. Is that possible? Please let me know. Thanks
Hi,
-Atlas__ said:
I have both oem unlock and usb debugging checked on the developer options plus i was able to unlock the devices oem through fastboot. I opened the command prompt in androids/sdk/platform tools but nothing happens just repeats recovery failed. What am I doing wrong? (My goal is to download twrp onto my lg V10)
Click to expand...
Click to collapse
disabling the "OEM unlock" option will probably solve your problem. It is only needed to unlock the bootloader and can be disabled afterwards. This did the trick for me.
you need to unlock the bootloader
this is what i did to get past it on my brand new tmobile v10 (H901)
if not in the bootloader pass the command
Code:
adb reboot bootloader
now pass
Code:
fastboot oem unlock
now continue to install twrp
you may need to use [/code]fastboot boot {path to image}[/code]
then transfer the twrp img to the phone via mtp (use mounts >enable mtp to do the transfer) disable mtp when done
and then install it again inside twrp using the install image option, just make sure you install it to recovery and NOT BOOT as that is a 1 way trip to brick ville
Has there been any development on this issue? I just picked up a refurb H901 with MM on it, and I get the same error.
I was able to unlock the bootloader, but I can't boot to the TWRP image (fastboot boot twrp.img), nor can I flash the recovery img to recovery from the stock (unlocked) bootloader (fastboot flash recovery twrp.img).
Thanks! I'm on H90120j
Seconded, I have bootloader unlock but get the same error message when flashing TWRP. Going to try Hünstetten suggestion.
No luck after disabling OEM Unlock and retrying, still get the failed message.
Alright guys i figured it out. Use the command "fastboot boot [recoveryfilename.img]"
then once in twrp, flash twrp again and flash super user. Thats how i solved my problem. Also make sure that the recovery files is in your internal storage as well as the adb file on your computer
remember to open the command prompt from inside the adb folder
plz sand pix on instal recovery,myh901 not instal recovery
krixxux said:
Alright guys i figured it out. Use the command "fastboot boot [recoveryfilename.img]"
then once in twrp, flash twrp again and flash super user. Thats how i solved my problem. Also make sure that the recovery files is in your internal storage as well as the adb file on your computer
remember to open the command prompt from inside the adb folder
Click to expand...
Click to collapse
I am also getting Failure with both boatloader commands. Is there an update to this fix, or additional info? Thank you.
dogfyter said:
I am also getting Failure with both boatloader commands. Is there an update to this fix, or additional info? Thank you.
Click to expand...
Click to collapse
install "Minimal ADB and Fastboot" - search here on the V10 forum or google, and then in V10 section here you find the TWRP for V10, download the zip and extract the img to Minimal ADB and Fastboot main folder.
Then you open Minimal ADB and with USB debbuging on and the phone connected type:
adb reboot bootloader
- hit enter
- wait till the phone ask your permission from adb, for this keep the screen on and check the box in that window, then it will enter bootloader
- when in bootloader type in Minimal ADB:
fastboot flash recovery twrp-3.0.2.0-0-h960a.img
- and you done (note the twrp-3.0.2.0-0-h960a.img is the file of my TWRP img and yours can be different but i assume you download it from V10 section here so it will be the same after extracting it.)
- to enter TWRP just take the battery out after done all commands and put back in, keep your finger in volume down and power at same time, when LG logo appears release and put the finger back in power button.
- then a window will show up to restore defaults - ignore this saying yes to both, use volume rocker and power to confirm twice asked.
and thats it... if you want help see this:
https://forum.xda-developers.com/lg-v10/development/recovery-twrp-v3-0-2-0-unofficial-t3387783
I appreciate the effort. After the "adb reboot bootloader" command I get the "error: no devices/emulators found" response.
Keep in my my phone does reboot after typing the "fastboot reboot" command. I also have usb debugging acknowledged in the MM OS whenever I plug the usb in.
So I proceeded to the next step "fastboot flash recovery twrp... img" anyway and I get the same "Failed... " msg.
I think my V10 days will be short lived.
dogfyter said:
I appreciate the effort. After the "adb reboot bootloader" command I get the "error: no devices/emulators found" response.
Keep in my my phone does reboot after typing the "fastboot reboot" command. I also have usb debugging acknowledged in the MM OS whenever I plug the usb in.
So I proceeded to the next step "fastboot flash recovery twrp... img" anyway and I get the same "Failed... " msg.
I think my V10 days will be short lived.
Click to expand...
Click to collapse
try: fastboot reboot-bootloader
with " - " between reboot and bootloader.
OR
with your phone powered off put the finger on volume down and then connect usb and they will be in fastboot mode, before that try the command above mentioned.
sun_is_shinning said:
try: fastboot reboot-bootloader
with " - " between reboot and bootloader.
OR
with your phone powered off put the finger on volume down and then connect usb and they will be in fastboot mode, before that try the command above mentioned.
Click to expand...
Click to collapse
Thanks again, Sun. I tried both and ways and got the same failure results. My amateur opinion is that when I installed LG Bridge on my PC (looking for drivers) it updated a tamper proof boot loader on my phone. But, who knows. Have a great day.
dogfyter said:
Thanks again, Sun. I tried both and ways and got the same failure results. My amateur opinion is that when I installed LG Bridge on my PC (looking for drivers) it updated a tamper proof boot loader on my phone. But, who knows. Have a great day.
Click to expand...
Click to collapse
i never read something like that about "tamper proof bootloader", you did some update in LG bridge?
- are u sure you have bootloader unlocked?! this is strange...i never saw something like your problem.
sun_is_shinning said:
i never read something like that about "tamper proof bootloader", you did some update in LG bridge?
- are u sure you have bootloader unlocked?! this is strange...i never saw something like your problem.
Click to expand...
Click to collapse
I just verified the bootloader is unlocked. Since I unlocked it the next boatloader menu only provides the two options for how to exit bootloader. There are no menu options for "quick guidance" (ie, flash, erase, or reboot).
All attempts end with "FAILED (remote: unknown command)".
I do not know what that means so, I can only guess. Thanks again tho.
late response
sun_is_shinning said:
i never read something like that about "tamper proof bootloader", you did some update in LG bridge?
- are u sure you have bootloader unlocked?! this is strange...i never saw something like your problem.
Click to expand...
Click to collapse
I figured out it had nothing to do with lg bridge. I was having driver issues with windows 8.1. So after trying to follow another to install android sdk I had issues with that not installing properly. The thread suggested re-configuring files I could not even find/did not install. So I just gave up and got a different phone. Thanks again for trying.
I ported TWRP using Android kitchen to flash to my device (Coolpad 801es) since there isn't an official version. For some reason, I can't seem to get fastboot to play nice with my phone (see my earlier post) so I used flashify. On reboot i'm stuck in a bootloop. I did have the foresight to back up my stock recovery with flashify and transfer it to my PC first, in case something went wrong. Now, I can't boot into recovery at all and ADB isn't working since the phone isn't being recognized by my PC when I plug it in. I just want to flash the stock recovery back and fix this. I can get into fastboot, and the PC does recognize the phone in fastboot, but when I try any commands it just hangs at waiting for device. I've googled but every solution i've seen for fixing a bootloop tells you to boot into recovery to do so.
Can someone please help me out?
UPDATE:
Upon further research, I discovered the reason fastboot commands weren't working is because my phone apparently isn't whitelisted in the fastboot exe. However, if I type Fastboot followed by -i 0x1ebf the commands seem to work. Using this method, fastboot devices lists my phone and fastboot reboot reboots the phone.
I think i'm on the right track, but when I try "Fastboot -i 0x1ebf flash recovery (path to recovery.img)" the terminal shows "sending 'recovery' (10240kb)..." and nothing else. No progress indicator, and i've waited 10 minutes for it to complete which should be more than enough time to flash a 10 meg file, but there's no change it just sits there. Like I said, I think i'm on the right track but I could REALLY use some help. I can't be the first person on here with this problem. Can someone, anyone, PLEASE help me.
So, more Googling would indicate that either i'm not using the correct USB port, or that my bootloader is locked. I have tried all the USB ports on my PC (front and back) as well as two different cables, no joy. As far as the bootloader being locked, the phone is rooted which I thought meant that the bootloader is unlocked as that is part of the rooting process. I try "Fastboot oem unlock" to check but I just get "failed remote no such command unlock" and there is no OEM option under developer options on this phone. I'm trying to piece this together but I could really use some help.
Hello, i got this p20 lite 2018 from a friend, basically he told me that the phone was performing a software update during the night while it was charging, but then in the morning he found the device in a bootloop.
All i can do with it is get into fastboot, Recovery mode and download mode do not work (it just keeps bootlooping).
Sadly hisuite does not the recognize the phone, it pops up when i plug it in and that's, it just keeps saying that it doesn't recognize any phone. Also adb doesn't work(i already installed the drivers) and when i try to send fastboot commands i keep getting some kind of error.
Currently my main concern is data recovery, but if it's not possible to recover the data is it possible to at least save this brick?
Fastboot screen:
https://imgur.com/a/s8FBkDn
p.s. now it shows AP_S_ABNORMAL 64 but on other occasions it shows COLDBOOT 16 or AP_S_COOLDBOOT 0
SignoreTNT said:
data recovery
Click to expand...
Click to collapse
Hello,
just to be sure - have you tried boot into eRecovery? (connect the phone to PC or charger, then press and hold Power and Vol. Up for 10 sec).
There's an option on EMUI 9.1 - Emergency backup. It can backup your data to the external SD card.
SignoreTNT said:
save this brick
Click to expand...
Click to collapse
With the locked bootloader/FRP lock you have only a few options. First of all, you need access to Recovery (service firmware & dload mode) or eRecovery ("Download latest version and recovery") .
-Alf- said:
Hello,
just to be sure - have you tried boot into eRecovery? (connect the phone to PC or charger, then press and hold Power and Vol. Up for 10 sec).
There's an option on EMUI 9.1 - Emergency backup. It can backup your data to the external SD card.
With the locked bootloader/FRP lock you have only a few options. First of all, you need access to Recovery (service firmware & dload mode) or eRecovery ("Download latest version and recovery") .
Click to expand...
Click to collapse
Sadly nothing works except fastboot, i also tried eRecovery like 5 times but it just keeps bootlooping.
I tried again to execute some fastboot commands but i always get:
FAILED (remote: 'command not allowed')
Fastboot: error:Command failed
Edit: i forgot to say that i have the google account credentials and the phone password, i hope that might help with frp.
SignoreTNT said:
I tried again to execute some fastboot commands but i always get:
FAILED (remote: 'command not allowed')
Fastboot: error:Command failed
Click to expand...
Click to collapse
With locked FRP and bootloader only information commands work, e.g. fastboot oem get-build-number, fastboot getvar vendorcountry etc.
Drain the battery completely, IMO last chance...
-Alf- said:
With locked FRP only information commands work, e.g. fastboot oem get-build-number, fastboot getvar vendorcountry etc.
Drain the battery completely, IMO last chance...
Click to expand...
Click to collapse
Disconneting the battery might help? im not afraid to open up the phone at this point...
SignoreTNT said:
Disconneting the battery might help?
Click to expand...
Click to collapse
Yes.
-Alf- said:
With locked FRP and bootloader only information commands work, e.g. fastboot oem get-build-number, fastboot getvar vendorcountry etc.
Drain the battery completely, IMO last chance...
Click to expand...
Click to collapse
I drained the battery completely but as soon as it gets enough charge it tries to boot and it keeps getting stuck.
Also sometimes i get a weird green background with a blue square and a red square for a split second.
SignoreTNT said:
Also sometimes i get a weird green background with a blue
Click to expand...
Click to collapse
Something like this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Recovery software, at home, on the unit costs $19 (via DC-Phoenix), but if the problem is hardware, (dead memory, damaged motherboard), it won't help you.
-Alf- said:
Something like this?
View attachment 5213075
Recovery software, at home, on the unit costs $19 (via DC-Phoenix), but if the problem is hardware, (dead memory, damaged motherboard), it won't help you.
Click to expand...
Click to collapse
Yep exactly like that screen.
Btw i guess that it is a software problem because it happened during a software update.
-Alf- said:
Something like this?
View attachment 5213075
Recovery software, at home, on the unit costs $19 (via DC-Phoenix), but if the problem is hardware, (dead memory, damaged motherboard), it won't help you.
Click to expand...
Click to collapse
Can i recover data with DC-Phoenix?
SignoreTNT said:
Can i recover data with DC-Phoenix?
Click to expand...
Click to collapse
Google search - 3 minutes
-Alf- said:
Google search - 3 minutes
Click to expand...
Click to collapse
Hey I am in the same situation but I have bootloader unlocked can you help me?
A little update (finally). i managed to unlock the bootloader so now i *should* be able to load a custom recovery or the stock firmware, if everything works ill make a little guide.
Now i need to flash the new firmware with fastboot but i really have no idea on how to do so, i have already downloaded the stock firmware that i need to load and i opened the update.app with huawei update extractor 0.9.9.5,but now i don't really know what to do (and i don't want to worsen the situation lol).
Can someone help me? any help would be appreciated <3
SignoreTNT said:
A little update (finally). i managed to unlock the bootloader so now i *should* be able to load a custom recovery or the stock firmware, if everything works ill make a little guide.
Now i need to flash the new firmware with fastboot but i really have no idea on how to do so, i have already downloaded the stock firmware that i need to load and i opened the update.app with huawei update extractor 0.9.9.5,but now i don't really know what to do (and i don't want to worsen the situation lol).
Can someone help me? any help would be appreciated <3
Click to expand...
Click to collapse
1. In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results pls.
2. check if your device has been detected and recognized by your computer, type
fastboot devices
If you get a response with your Serial number, it means that your device is properly connected
3.
SignoreTNT said:
i have already downloaded the stock firmware
Click to expand...
Click to collapse
Which firmware?
-Alf- said:
1. In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results pls.
2. check if your device has been detected and recognized by your computer, type
fastboot devices
If you get a response with your Serial number, it means that your device is properly connected
3.
Which firmware?
Click to expand...
Click to collapse
oem get-build-number
ANE-LX1 9.1.0.372(C432E7R1P7)
oem get-product-model
ANE-LX1
getvar vendorcountry
hw/eu
oem oeminforead-CUSTOM_VERSION
ANE-LX1-CUST 9.1.0.7(C432)
oem oeminforead-SYSTEM_VERSION
ANE-LX1 9.1.0.132(C432E5R1P7)
The firmware that i downloaded is C432E7R1P7T8
SignoreTNT said:
The firmware that i downloaded is C432E7R1P7T8
Click to expand...
Click to collapse
Just to be sure - 9.1.0.370(C432E7R1P7T8) downloaded from androidhost.ru?
And what about command "fastboot devices"? It's okay?
I would suggest the following:
- there is a dload folder in stock firmware, copy it (without unpacking it!) to the SD card
Now try to install stock Recovery , download link
- in fastboot mode run
fastboot flash recovery_ramdisk RECOVERY_RAMDISK-9.1.img
- fastboot reboot
- turn off the phone, then press and hold Power+Vol Up+ Vol Down ('three buttons combo') and try to install Service ROM (aka stock firmware) . Disconnect the phone from the PC before starting the process!
-Alf- said:
Just to be sure - 9.1.0.370(C432E7R1P7T8) downloaded from androidhost.ru?
And what about command "fastboot devices"? It's okay?
I would suggest the following:
- there is a dload folder in stock firmware, copy it (without unpacking it!) to the SD card
Now try to install stock Recovery , download link
- in fastboot mode run
fastboot flash recovery_ramdisk RECOVERY_RAMDISK-9.1.img
- fastboot reboot
- turn off the phone, then press and hold Power+Vol Up+ Vol Down ('three buttons combo') and try to install Service ROM (aka stock firmware) . Disconnect the phone from the PC before starting the process!
Click to expand...
Click to collapse
yea, downloaded it from androidhost.ru, fastboot devices is ok. now ill try to flash the recovery
-Alf- said:
Just to be sure - 9.1.0.370(C432E7R1P7T8) downloaded from androidhost.ru?
And what about command "fastboot devices"? It's okay?
I would suggest the following:
- there is a dload folder in stock firmware, copy it (without unpacking it!) to the SD card
Now try to install stock Recovery , download link
- in fastboot mode run
fastboot flash recovery_ramdisk RECOVERY_RAMDISK-9.1.img
- fastboot reboot
- turn off the phone, then press and hold Power+Vol Up+ Vol Down ('three buttons combo') and try to install Service ROM (aka stock firmware) . Disconnect the phone from the PC before starting the process!
Click to expand...
Click to collapse
C:\Users\Davide\Desktop>fastboot flash recovery_ramdisk RECOVERY_RAMDISK-9.1.img
Sending 'recovery_ramdisk' (32768 KB) OKAY [ 1.209s]
Writing 'recovery_ramdisk' OKAY [ 0.162s]
Finished. Total time: 1.405s
C:\Users\Davide\Desktop>fastboot reboot
Rebooting OKAY [ 11.589s]
Finished. Total time: 11.592s
I still cannot boot into Recovery, if i press that ccombination it goes into the huawei logo screen and then it reboots (and keeps bootlooping)
SignoreTNT said:
C:\Users\Davide\Desktop>fastboot flash recovery_ramdisk RECOVERY_RAMDISK-9.1.img
Sending 'recovery_ramdisk' (32768 KB) OKAY [ 1.209s]
Writing 'recovery_ramdisk' OKAY [ 0.162s]
Finished. Total time: 1.405s
C:\Users\Davide\Desktop>fastboot reboot
Rebooting OKAY [ 11.589s]
Finished. Total time: 11.592s
I still cannot boot into Recovery, if i press that ccombination it goes into the huawei logo screen and then it reboots (and keeps bootlooping)
Click to expand...
Click to collapse
Maybe your emmc memory is dead...
Try command
fastboot erase userdata
then try enter Recovery.
If you want, extract from stock ROM :
CUST, KERNEL, SYSTEM, RECOVERY_RAMDIS , USERDATA.
Flash partitions using commands
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash cust CUST.img
etc.
Note: USERDATA.img can be found in _ANE-L21_hw_eu (second folder in dload).
-Alf- said:
Maybe your emmc memory is dead...
Try command
fastboot erase userdata
then try enter Recovery.
If you want, extract from stock ROM :
CUST, KERNEL, SYSTEM, RECOVERY_RAMDIS , USERDATA.
Flash partitions using commands
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash cust CUST.img
etc.
Note: USERDATA.img can be found in _ANE-L21_hw_eu (second folder in dload).
Click to expand...
Click to collapse
uhh, it's been erasing userdata for the past 20 mins at this point, should i disconnect the phone and try again?
Edit:
Erasing 'userdata' FAILED (remote: 'failed to erase partition')
fastboot: error: Command failed
ill try again
I have a Moto G Play 2021 (XT2093-4) (another one), that I made a mistake to relock the bootloader after I had it unlocked. I don't have access to the OS on the phone anymore. Previously I had the treble floss installed on it. I don't have TWRP installed. The only thing I have access to is fastboot. I realise I might have completely bricked this phone but I thought I ask here to see if there is any way to unlock the OEM again just using the fastboot.
the fastboot screen on the phone has a menu option to go into recovery mode. stock recovery might be able to restore your phone to working condition.
volume-down + power buttons > fastboot mode > volume button to 'recovery' option > power button to execute. if your recovery screen is broken with the 'no command' message, hold down the power button and quickly press and release the volume-up button. that should get you to the working recovery screen where you can try to factory reset your phone.
strumcat said:
the fastboot screen on the phone has a menu option to go into recovery mode. stock recovery might be able to restore your phone to working condition.
volume-down + power buttons > fastboot mode > volume button to 'recovery' option > power button to execute. if your recovery screen is broken with the 'no command' message, hold down the power button and quickly press and release the volume-up button. that should get you to the working recovery screen where you can try to factory reset your phone.
Click to expand...
Click to collapse
Thanks, but I think my phone is completely messed up now. If you can believe it, I can't even get to recovery mode. I can get to fastboot and then find the recovery mode and click to go to it but then it just starts the fastboot again. I'm basically stuck in fastboot forever. It's just weird cause there's nothing wrong with the hardware. Thanks again.
if you have nothing working on your phone but fastboot mode, that might still be enough to rescue your phone. boot it to the fastboot screen, connect it to a pc that has the fastboot program installed, open a terminal window on the pc wherever fastboot is, and type 'fastboot devices'. if your phone answers with its serial number, you'rr probably able to flash a whole stock rom to it piece by piece. get a stock rom from somewhere like lenovo, using their lmsa program, or just download the right one from lolinet or somewhere. unzip it. then, for instance, to flash the boot.img to your phone you would type 'fastboot flash boot boot.img'. that would replace your possibly broken boot partition with a known good one. then 'fastboot reboot' to see if that helped. there are tutorials on the net for flashing the rest of the rom. be sure to read one, because all of the flash commands aren't that straightforward.
strumcat said:
if you have nothing working on your phone but fastboot mode, that might still be enough to rescue your phone. boot it to the fastboot screen, connect it to a pc that has the fastboot program installed, open a terminal window on the pc wherever fastboot is, and type 'fastboot devices'. if your phone answers with its serial number, you'rr probably able to flash a whole stock rom to it piece by piece. get a stock rom from somewhere like lenovo, using their lmsa program, or just download the right one from lolinet or somewhere. unzip it. then, for instance, to flash the boot.img to your phone you would type 'fastboot flash boot boot.img'. that would replace your possibly broken boot partition with a known good one. then 'fastboot reboot' to see if that helped. there are tutorials on the net for flashing the rest of the rom. be sure to read one, because all of the flash commands aren't that straightforward.
Click to expand...
Click to collapse
Sorry for the really late reply. I tried what you said, but it fails right at the (fastboot flash partition gpt.bin) command and the output I get is:
Sending 'partition' (37 KB) OKAY [ 0.002s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) flash permission denied
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
It keeps saying flash permission denied. I have another exact same phone with an unlocked bootloader and I did the same on that one and I was able to flash a stock ROM to it. I've tried every RETCA and RETUS on this site: https://mirrors.lolinet.com/firmware/motorola/guamna/official/ but it fails with the same error. I'm going to try all the rest later but it's a lot to download for now.
Thanks again for the help!