Hi All,
Yesterday my LG Q Stylo plus was gone into black screen, and could not soft reset or hard reset. When I put it on charging, it vibrated again and again every few minutes, still with black screen. Then I opened the back cover, unplugged the battery to force it power off. Then I tried to factory reset it, but failed to start. Today I tried to flash it, but the PC could not detect the device even though I already downloaded LG driver. In this case, I can not flash it. And it showed on the screen said " FASTBOOT MODE.........". Please see attached picture. Anyone who know how to fix it please help me. Thanks a lot!
{
"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"
}
Can you get into recovery? If so, reset it in recovery or flash a new stock (or custom) rom onto it. In fastboot mode you may be able to directly boot into a custom recovery or flash a custom recovery if you need to.
I tried to flash a new stock rom on it. But PC could not detect the device, even though I already installed the driver. I tried to hold the power button with volume down key to reset it, it didn't work and the screen showed nothing but black. Only after the battery drained out, I plugged the charger on, the screen will be lit and showed the message like above picture showed. Is there any other way to let PC detect the device so that I can flash it?
If you're using Windows, maybe boot into a Linux Live USB (like linux mint for e.g.) and download adb and fastboot. Linux usually works all the time for me with fastboot, so try that and see if it can detect your phone. If detected you might have to run
Code:
fastboot oem unlock
which WILL erase your data, but you can't flash anything without doing so.
I just realized from the picture, msm8953 refers to the processor. Lock state is locked, does it mean the processor is locked? So it can't be soft reset or hard reset? How to unlock the processor? I remember the phone was running very very slow, then it went dead. Is it right that the processor was running on heat , so it was locked?
auroraguy123 said:
I just realized from the picture, msm8953 refers to the processor. Lock state is locked, does it mean the processor is locked? So it can't be soft reset or hard reset? How to unlock the processor? I remember the phone was running very very slow, then it went dead. Is it right that the processor was running on heat , so it was locked?
Click to expand...
Click to collapse
No. LOCK STATUS on Fastboot likely means the bootloader is locked to not allow custom images to be loaded. This is purely for security and can be unlocked by running the Fastboot oem unlock command I wrote about above. This wipes your data so that, no thief can steal your phone, unlock the bootloader, and browse your files with a custom recovery, as your data will be wiped. I'm not 100% sure but across the few phones in my life that use Fastboot, it has always meant the oem lock to prevent custom images for security reasons.
Any slowdowns occur either because battery saving scheme, full RAM, many processes running, malware, etc. Its not to do with Fastboot.
You should be able to see the device in Fastboot on Linux. Try and flash a custom recovery first, but it might not work because it's locked. In that case you'll need to unlock the Fastboot (which will erase your user data) and then flash a custom recovery, from which you can flash a new rom. Or flash stock recovery and load your official ROM zip if it's supported
Good luck, let us know if you have any issues.
as
quickishfm
said just connect your phone to computer and type
fastboot devices
if device is connected it will be shown on screen
after it just use command adb oem unlock
to unlock bootloader.
if you dont want to unlock bootloader then you will have to erase data partition by using command fastboot erase data
I downloaded adb and fastboot on Linux. But when I typed adb device, still can not see the device. What should I do?
You must type fastboot devices (or fastboot device, I can't remember ) when your screen is in that FASTBOOT MODE.
Once it's in there you just have to flash a custom recovery, or, unlock the bootloader first as we discussed before. This will wipe user data remember. After unlocking bootloader you can flash a custom recovery or stock recovery, and then a new ROM in recovery.
When the device is power off, after I plug it to pc usb, it will show charging sign on the screen and then go the fastboot mode as showed in the picture above. I checked the device manager it was connected as android bootlock inferface. But if I use adb device, there is no device is found.
Yes, you are right. I found the device. Then how to make a custom recovery if I don't want to lose the data?
auroraguy123 said:
Yes, you are right. I found the device. Then how to make a custom recovery if I don't want to lose the data?
Click to expand...
Click to collapse
There's no way to do that. It would not be secure if you could overwrite recovery if data is not deleted - then anyone could steal your phone, put a custom recovery and read data partition if not encrypted.
Maybe you can reflash a stock recovery zip (if you can find and if it let's you to flash) through fastboot, then go into recovery and sideload stock rom to your device. Most likely in this case the data will not be deleted.
Thanks. Why it showed unknowed command when I typed fastboot oem unlock?
Hmm, not sure, might have to look on Google. Does anything come up with
Code:
fastboot oem get_unlock_data
?
same when I typed fastboot oem get_unlock_data showed unknown command. Is there a way to let pc force the device to go to download moade because it stuck in the fastboot mode?
AFAIK the download mode is only a thing for Samsung, most other Android phones use fastboot as the download mode which flashes recovery etc.
Perhaps look online on ways to fix the unknown command issue... How did you install fastboot for the Linux?
Cn you run fastboot oem help, and fastboot --version please
Post the output here, thanks
I tried both on Linux and Windows, but the same result. I run fastboot devices, it showed my device. But when I run adb devices, it showed nothing. I run fastboot oem help, it showed the menu of the command. Please see the picture.
auroraguy123 said:
I tried both on Linux and Windows, but the same result. I run fastboot devices, it showed my device. But when I run adb devices, it showed nothing. I run fastboot oem help, it showed the menu of the command. Please see the picture.View attachment 5204225View attachment 5204225
Click to expand...
Click to collapse
That's useful, thanks. It seems the syntax has changed. Try
fastboot flashing unlock
to unlock the bootloader, and then you should be able to flash a custom recovery.
There's also update to directly flash an update.zip if you can find one, which might not need unlock boorloader. But this will likely have to be a stock update.zip signed by LG so no custom recovery or anything. I don't know if this will erase data.
I also run fastboot -w, it started wiping, but then failed as shown unknown command.
Related
I had a unfortunate incident where my waterproof jacket failed. My phone was inside the waterproof pocket and ended up being soaked.
The phone turned it self off and when I had turned it on the screen turned yellow.
Immediately pulled out the battery and let it sit in rice for 3 days.
Now when I turn it on it gets stuck at the google logo screen and never shuts off. I have to pull the batter to turn it off.
I can go into fastboot mode and my options are:
reboot bootloader
reboot
recovery
power off
If I choose recovery it simply goes back to the google logo again and sits.
Some additional info about the phone:
product name - hearing
hw versoin - rev 11
bootloader version - 19020xxka3
lock state - locked
I can access the unlock bootloader screen however it says if I unlock it it will erase all of my data which I do not want to do.
My main goal is recovering the data on the phone. I have a few files that I absolutely need to recover.
If my phone never works again, that is fine so long as I can access the data off of this phone.
Any help troubleshooting would be greatly appreciated.
sj_martin said:
I had a unfortunate incident where my waterproof jacket failed. My phone was inside the waterproof pocket and ended up being soaked.
The phone turned it self off and when I had turned it on the screen turned yellow.
Immediately pulled out the battery and let it sit in rice for 3 days.
Now when I turn it on it gets stuck at the google logo screen and never shuts off. I have to pull the batter to turn it off.
I can go into fastboot mode and my options are:
reboot bootloader
reboot
recovery
power off
If I choose recovery it simply goes back to the google logo again and sits.
Some additional info about the phone:
product name - hearing
hw versoin - rev 11
bootloader version - 19020xxka3
lock state - locked
I can access the unlock bootloader screen however it says if I unlock it it will erase all of my data which I do not want to do.
My main goal is recovering the data on the phone. I have a few files that I absolutely need to recover.
If my phone never works again, that is fine so long as I can access the data off of this phone.
Any help troubleshooting would be greatly appreciated.
Click to expand...
Click to collapse
HMMMMMMMMMMM. If you were rooted already I might have been able to sugest something more from here. Maybe someone else can elaborate based on my suggestion as far as how to get it done not
In fastboot: when you connect to the PC does it give you an option to connect USB Storage? Or, better: Go into recovery. Then, from there hit power and volume up at the same time. See what options are there. (I don't remember if there is one to mount US storage Try this before that and after your fully in recovery: connect and see if the usb storage will mount to your computer.
Wait, instead of erasing that: you said you couldn't get into recovery. But if you happen to: try that.
Otherwise first see if it mounts usb storage when in fastboot. I'm not sure if it would. I know if fastboot you can run fastboot program on your computer and pull the imgs if you needed system files and what not; but, you wouldn't be able to get them if you can't read the usb storage from your computer in the first place.
Edit again: Sorry, just tried mounting in fastboot. Doesn't work. Hmmmmmmm.
---------- Post added at 10:40 PM ---------- Previous post was at 10:27 PM ----------
BlackHawkA4 said:
HMMMMMMMMMMM. If you were rooted already I might have been able to sugest something more from here. Maybe someone else can elaborate based on my suggestion as far as how to get it done not
In fastboot: when you connect to the PC does it give you an option to connect USB Storage? Or, better: Go into recovery. Then, from there hit power and volume up at the same time. See what options are there. (I don't remember if there is one to mount US storage Try this before that and after your fully in recovery: connect and see if the usb storage will mount to your computer.
Wait, instead of erasing that: you said you couldn't get into recovery. But if you happen to: try that.
Otherwise first see if it mounts usb storage when in fastboot. I'm not sure if it would. I know if fastboot you can run fastboot program on your computer and pull the imgs if you needed system files and what not; but, you wouldn't be able to get them if you can't read the usb storage from your computer in the first place.
Edit again: Sorry, just tried mounting in fastboot. Doesn't work. Hmmmmmmm.
Click to expand...
Click to collapse
Ok, again. I don't know if this would work: I can't test this out. If anyone else knows or could confirm.
IF, you can use ADB while in fastboot (Anyone know if you can or can't? Never tried it; can't test it right now) check this post out about how to mount the storage using ADB: http://groups.google.com/group/android-developers/browse_thread/thread/485d7b04bc61d7be
I'm not sure if you can use ADB in fastboot though as you usually do it while the OS is on and debugging mode is enabled. Not sure how it would work from fastboot.
I feel like I have a chance at salvaging the data. Here are some additional notes after poking around a little bit.
This phone is completely stock, never unlocked, never rooted. Never even had a chance to turn on debugging mode before it was water logged.
With that said, here is what I have done and am able to do so far.
I've installed the Android SDK + ADB drivers. I am using both XP and Win 7 to test. I can see the phone in the device manager in windows and adb is working correctly in command prompt.
However when I do "adb devices" it does not show the phone as a device. I think it might be because it needs to be in debugging mode however I cannot turn on the phone to get to that stage.
With that said, it looks like once someone can help me get ADB to recognize my device there are commands where I can extract the data out of the phone via adb.
So, can anyone help troubleshoot getting windows to recognize my phone in command prompt? Again, I can see the phone in the device manager and have installed the correct drivers.
Thanks
sj_martin said:
I feel like I have a chance at salvaging the data. Here are some additional notes after poking around a little bit.
This phone is completely stock, never unlocked, never rooted. Never even had a chance to turn on debugging mode before it was water logged.
With that said, here is what I have done and am able to do so far.
I've installed the Android SDK + ADB drivers. I am using both XP and Win 7 to test. I can see the phone in the device manager in windows and adb is working correctly in command prompt.
However when I do "adb devices" it does not show the phone as a device. I think it might be because it needs to be in debugging mode however I cannot turn on the phone to get to that stage.
With that said, it looks like once someone can help me get ADB to recognize my device there are commands where I can extract the data out of the phone via adb.
So, can anyone help troubleshoot getting windows to recognize my phone in command prompt? Again, I can see the phone in the device manager and have installed the correct drivers.
Thanks
Click to expand...
Click to collapse
heres what you can do, unlock boot loader, install clockwork mod make a backup of the current rom installed, and try to work with that somehow heres the link for unlocking the bootloader and installing the recovery!
btw if you get clockwork installed you'll be able to access the sd card storage!
http://forum.xda-developers.com/showthread.php?t=895545
I'm not exactly sure that you can install a recovery without unlocking the bootloader but I'm sure one of the devs can use their tools to pull the /system & /data off of your device. if that's not what you need I'm pretty sure your sd card isn't wiped when you unlock the bootloader, I'm assuming only the phone is reset. Just read all the similar posts here about recovering data using recovery or ADB
anishs said:
heres what you can do, unlock boot loader, install clockwork mod make a backup of the current rom installed, and try to work with that somehow heres the link for unlocking the bootloader and installing the recovery!
btw if you get clockwork installed you'll be able to access the sd card storage!
http://forum.xda-developers.com/showthread.php?t=895545
I'm not exactly sure that you can install a recovery without unlocking the bootloader but I'm sure one of the devs can use their tools to pull the /system & /data off of your device. if that's not what you need I'm pretty sure your sd card isn't wiped when you unlock the bootloader, I'm assuming only the phone is reset. Just read all the similar posts here about recovering data using recovery or ADB
Click to expand...
Click to collapse
The issue here is that if I unlock the bootloader it will wipe EVERYTHING. There seems to be a way to side load clockwork via ADB if I could actually connect via ADB if I had debugging mode on which I cannot turn on.
Everything I read says unlocking bootloader will wipe all data. I haven't seen anything that states the data is maintained, have you?
Thanks.
download the SDK, or just the necessary files to use adb and fastboot.
then download a CWR recovery.img
the do a fastboot boot recovery CWR_filename.img. that will boot the CWR image without flashing it, from there you can try a backup. then mount the SD card from CWR, and then copy the backup to your pc.
if it won't backup your files, or won't mount your sd card partition, then most likely your data is corrupted.
sj_martin said:
The issue here is that if I unlock the bootloader it will wipe EVERYTHING. There seems to be a way to side load clockwork via ADB if I could actually connect via ADB if I had debugging mode on which I cannot turn on.
Everything I read says unlocking bootloader will wipe all data. I haven't seen anything that states the data is maintained, have you?
Thanks.
Click to expand...
Click to collapse
as i said just try to load the recovery following that guide, try it without unlocking the bootloader if it doesn't work you have to unlock the bootloader, and maybe your sd won't be wiped but you phone data will
Luxferro said:
download the SDK, or just the necessary files to use adb and fastboot.
then download a CWR recovery.img
the do a fastboot boot recovery CWR_filename.img. that will boot the CWR image without flashing it, from there you can try a backup. then mount the SD card from CWR, and then copy the backup to your pc.
if it won't backup your files, or won't mount your sd card partition, then most likely your data is corrupted.
Click to expand...
Click to collapse
I understand how to use cwr however i need to get that loaded onto the phone first, and for me to load it to the phone i need adb i need the computer to be able to recognize it first which it wont. it shows it in the device manger, and all the drivers are installed correctly however in command prompt when i type "adb devices" it does not list it.
Luxferro said:
download the SDK, or just the necessary files to use adb and fastboot.
then download a CWR recovery.img
the do a fastboot boot recovery CWR_filename.img. that will boot the CWR image without flashing it, from there you can try a backup. then mount the SD card from CWR, and then copy the backup to your pc.
if it won't backup your files, or won't mount your sd card partition, then most likely your data is corrupted.
Click to expand...
Click to collapse
When your phone is plugged into your PC and in fastboot mode, does the command
fastboot devices
show any results? If so, follow Luxferro's advice.
If you've got no warranty, you could take your phone apart to see the motherboard, and spray it with isopropyl alcohol which will properly dry it.
Sent from the future to put right what once went wrong.
For those telling him to try fastboot boot it doesn't work without an unlocked bootloader.
Sent from my Nexus S MV from the XDA Premium app.
If the bootloader is locked it might prevent u from flashing recovery (I dunno mine always been unlocked). But I'm not telling him to flash a new recovery. U can just boot a recovery without flashing it (again not sure if locked bootloader prevents this... but its not writing to the phone just booting a external recovery.img).
Fastboot boot recovery filename.img
Worth a try
Sent from my Nexus S using xda premium
my understanding is that i need the have the device visible in command prompt via adb to do any of this which is the issue i'm trying to solve. once i can get my computer to see the phone via adb i think i'm home free to extract all the data i need.
{
"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"
}
Also it looks like I have 2 threads in the same section now, it looks like mods moved my posts so sorry for double replying.
bedalus said:
When your phone is plugged into your PC and in fastboot mode, does the command
fastboot devices
show any results? If so, follow Luxferro's advice.
Click to expand...
Click to collapse
Yes, it sees it now. It looks like I kept trying "adb devices" as shown on the screen shot. So now when I do fastboot devices I see my device and try to boot clockwork 5.0.2.0 but run into a boot fail:
It says i need to unlock the bootloader which I cannot do if i want to preserve data =/
10 character delete
Ive seen some uncertainty here, so I'll offer my advice (the limited I feel qualified to give).
Unlocking the boot loader will erase everything. Considering your goal is data retrieval, I would definitely NOT ever do that.
Unfortunately, having a locked bootloader severely limits your options.
My opinion on the matter is your best bet is ADB, but if the data is not time sensitive, I would let this topic get a bit more exposure. (perhaps mirror post on some other forums like xda too)
Hopefully someone more knowledgeable can post and help you out.
sj_martin said:
Yes, it sees it now. It looks like I kept trying "adb devices" as shown on the screen shot. So now when I do fastboot devices I see my device and try to boot clockwork 5.0.2.0 but run into a boot fail:
It says i need to unlock the bootloader which I cannot do if i want to preserve data =/
Click to expand...
Click to collapse
I just tried cw 3.0.0.5 per this thread:
http://forum.xda-developers.com/showthread.php?t=931865
and still get the same failure stating i need to do fastboot oem unlock
Is your bootloader even unlocked?
mathkid95 said:
Is your bootloader even unlocked?
Click to expand...
Click to collapse
No it is not. That's the point of this thread. It was a completely stock phone trying to recover data.
There is a method to root + recovery with locked bootloaders
"WITHOUT oem unlock & wipe" http://forum.xda-developers.com/showthread.php?t=931865
The advantage here is that those who chose not to root when they first got the phone won't lose any app data or sdcard data like the methods that have you unlock the bootloader do. The disadvantage is your bootloader remains locked, which may prevent you flashing certain things in the future.
edit: see ravidavi's posts below; he's shown you can even flash custom roms that are clockwork compatible while having a locked bootloader with this method.
Click to expand...
Click to collapse
kenvan19 said:
For those telling him to try fastboot boot it doesn't work without an unlocked bootloader.
Sent from my Nexus S MV from the XDA Premium app.
Click to expand...
Click to collapse
Just want to restate this. If his bootloader is locked he is pretty much SOL. He needs data off if it but to get the data he has to wipe the phone.
To the poster above me, that method no linger works. You cannot root without unlocking the bootloader. You cannot flash or boot a custom recovery without unlocking the bootloader. The links in that thread are dead.
One more time just to be sure Ira clear: you CANNOT get into a custom recovery without unlocking the bootloader.
Sent from my Nexus S MV from the XDA Premium app.
I've been looking everywhere on how to get ADB to work without debugging on; however, the only shred of hope I saw was the ability to get into your stock recovery. I didn't read on as you said you can't so it wouldn't help you anyways.
BUT!, if somehow do get into it (Or want to try to get into it over and over again and hope it works) you might be able to use ADB there. Then, that link I posted in the beginning should work to mount the storage.
Edit: Just looking at the pictures and you said you don't see the device in ADB. Have you tried actually going into ADB Shell and seeing if it connects to the phone? Mine device didn't "Show" in the list when I was using ADB but it worked.
Okay, here's the deal... I have an OPO (not mine) that is completely stock running, I would presume 5.0.2. I'm not exactly sure which build. But I was told that she turned the phone off at night and charged it. Turned it on in the morning and it got stuck on the cyanogen logo. No boot loops, no getting past that. Just sitting there. The device is stock, bootloader locked, no root. I also highly doubt that ADB debugging was turned on while it was working...
I'm trying to wipe it bring it back to stock, but I'm not having any success. I've gone in to Cyanogen recovery and wipe/factory reset, wipe cache, wipe media. Reboot, still stuck. When I click apply update in recovery, it gives me a bunch of errors saying so and so directory isn't found. So that leaves to me to believe that something went bad.
I just tried to fastboot oem unlock, said it finished in a few seconds. Then I tried to fastboot the factory image files and after the first one (modem), it gave me an error saying the bootloader is locked.
I'm out of ideas and the unbrick a hard bricked OPO thread said it wouldn't work, so I haven't tried it. Any advice on where to look would be much appreciated.
Anybody?
{
"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"
}
I get this when I hit Apply Update and then use storage as option.
moobieboobie said:
Anybody?
I get this when I hit Apply Update and then use storage as option.
Click to expand...
Click to collapse
Flash The whole Rom with fastboot to fix The Problem ....make a backup of your internal sdcard....
jamal2367 said:
Flash The whole Rom with fastboot to fix The Problem ....make a backup of your internal sdcard....
Click to expand...
Click to collapse
That's the problem. I can't because the bootloader is locked. When I try to unlock it, it runs the command. Then when I try to fastboot flash, it tells me the bootloader is locked. I have my own OPO that I have unlocked and rooted, so knowing how to unlock isn't an issue either.
moobieboobie said:
That's the problem. I can't because the bootloader is locked. When I try to unlock it, it runs the command. Then when I try to fastboot flash, it tells me the bootloader is locked. I have my own OPO that I have unlocked and rooted, so knowing how to unlock isn't an issue either.
Click to expand...
Click to collapse
Run CMD as Admin ...have you install the right driver for your phone and install the ADB drivers correctly? ...
jamal2367 said:
Run CMD as Admin ...have you install the right driver for your phone and install the ADB drivers correctly? ...
Click to expand...
Click to collapse
Yes, all updated drivers. Drivers are not the issue since I can execute commands while in fastboot. The issue is not having an unlocked bootloader, so I can't flash anything and it won't unlock bootloader.
moobieboobie said:
Yes, all updated drivers. Drivers are not the issue since I can execute commands while in fastboot. The issue is not having an unlocked bootloader, so I can't flash anything and it won't unlock bootloader.
Click to expand...
Click to collapse
Ps did phone was encrypt?
geowolf1000 said:
Ps did phone was encrypt?
Click to expand...
Click to collapse
No, phone was not encrypted and ColorOS unbrick didn't work. It recognizes the phone, I hit start and it does it's thing. After first green bar, it boot loops instead of flashing all the files. Ran as admin and all the drivers are good.
moobieboobie said:
No, phone was not encrypted and ColorOS unbrick didn't work. It recognizes the phone, I hit start and it does it's thing. After first green bar, it boot loops instead of flashing all the files. Ran as admin and all the drivers are good.
Click to expand...
Click to collapse
hit install from recovery
Choose file to update
Search files
Do you see your partition?
System exist?
What system do you have color or cyanogen?
Data?
Sd?
geowolf1000 said:
hit install from recovery
Choose file to update
Search files
Do you see your partition?
System exist?
What system do you have color or cyanogen?
Data?
Sd?
Click to expand...
Click to collapse
See post above with picture. It was running stock Cyanogen OS 12, not modded or anything. When I hit Apply Update and Choose from internal storage, I get the error in above picture.
moobieboobie said:
See post above with picture. It was running stock Cyanogen OS 12, not modded or anything. When I hit Apply Update and Choose from internal storage, I get the error in above picture.
Click to expand...
Click to collapse
But you have adb
Sideload full rom included recovery
From adb
geowolf1000 said:
But you have adb
Sideload full rom included recovery
From adb
Click to expand...
Click to collapse
If by sideload, you mean copy the rom to device and then load..I can not access device storage. ADB sideload rom through command line gives me the same errors you see in the above picture.
moobieboobie said:
If by sideload, you mean copy the rom to device and then load..I can not access device storage. ADB sideload rom through command line gives me the same errors you see in the above picture.
Click to expand...
Click to collapse
F**ing recovery
With adb you can navigate to system and change built.prompt and enable debugg mode
All the other method i know need root so dd (replace)recovery from adb
geowolf1000 said:
F**ing recovery
With adb you can navigate to system and change built.prompt and enable debugg mode
All the other method i know need root so dd (replace)recovery from adb
Click to expand...
Click to collapse
Can you give instructions on how to? I'm not too familiar with adb, but can follow steps.
moobieboobie said:
Can you give instructions on how to? I'm not too familiar with adb, but can follow steps.
Click to expand...
Click to collapse
Even this suggest need root.
All need root.... To system...
moobieboobie said:
Can you give instructions on how to? I'm not too familiar with adb, but can follow steps.
Click to expand...
Click to collapse
Another trick for installation is
Code:
fastboot boot <path/name of the recovery twrp img>
It will boot your phone into recovery once from the recovery image
stored in your PC temporarily
then you can flash the zip either by sideload or
Check this
geowolf1000 said:
Another trick for installation is
Code:
fastboot boot <path/name of the recovery twrp img>
It will boot your phone into recovery once from the recovery image
stored in your PC temporarily
then you can flash the zip either by sideload or
Check this
Click to expand...
Click to collapse
cannot fastboot boot recovery, tells me bootloader is locked and fails. the link requires unlocking bootloader, which is not working for me.
moobieboobie said:
cannot fastboot boot recovery, tells me bootloader is locked and fails. the link requires unlocking bootloader, which is not working for me.
Click to expand...
Click to collapse
Haz a parametre here
There is a way to flash an unlocked bootloader if you can't fastboot oem unlock.
As you already tried the color.zip method you should already have most of the needed files.
Download the attachment and unzip it into color folder replacing the files emmc_appsboot.mbn and rawprogram0_64.xml (backup the originals first).
-power off the OPO
-hold VolUp and plug into PC
-on PC open device manager, OPO should be in QDloader 9008
-keep an eye on device manager and start msm8974downloadtool from color.zip
-when in device manager the QDloader 9008 disconnects press stop in msm8974downloadtool
-OPO should now be Qualcomm Diagnostics 9006 in device manager
-download MiFlash from here http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/ and set it up like on the pictures on that website
-click refresh. now it should show you OPO on the respective COM port. click flash
-when successfull finished unplug and press and hold power for 30 seconds
-now start into fastboot with power + VolUp and there is your unlocked bootloader
-now you can flash cos with fastboot
The rawprogram0_64xml is edited so that it only writes partition table and flashes sbl1, dbi, rpm, tz, recovery and emmc_appsboot.
This worked for me when i couldn't flash with msm8974downloadtool, it always flashed modem, started with flashing system and then began from the start again.
tropenfrucht said:
There is a way to flash an unlocked bootloader if you can't fastboot oem unlock.
As you already tried the color.zip method you should already have most of the needed files.
Download the attachment and unzip it into color folder replacing the files emmc_appsboot.mbn and rawprogram0_64.xml (backup the originals first).
-power off the OPO
-hold VolUp and plug into PC
-on PC open device manager, OPO should be in QDloader 9008
-keep an eye on device manager and start msm8974downloadtool from color.zip
-when in device manager the QDloader 9008 disconnects press stop in msm8974downloadtool
-OPO should now be Qualcomm Diagnostics 9006 in device manager
-download MiFlash from here http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/ and set it up like on the pictures on that website
-click refresh. now it should show you OPO on the respective COM port. click flash
-when successfull finished unplug and press and hold power for 30 seconds
-now start into fastboot with power + VolUp and there is your unlocked bootloader
-now you can flash cos with fastboot
The rawprogram0_64xml is edited so that it only writes partition table and flashes sbl1, dbi, rpm, tz, recovery and emmc_appsboot.
This worked for me when i couldn't flash with msm8974downloadtool, it always flashed modem, started with flashing system and then began from the start again.
Click to expand...
Click to collapse
gave it a shot a few minutes ago.. As soon as 9008 dc fom device manager, i hit stop. the phone turns off or reboots (the screen goes blank)... I hear the connection, but no 9006.
My phone (2nd nexus5, not my daily driver nexus) is stuck in a bootloop (stuck at the booting animation) after updating via the OTA updtes, never rooted or touched any setting in the dev options in the setting menu.
The phone stays like that for hours, doesn't even reboot on its own, just keeps playing the bootanimation for hours and hours until the battery dies.
I have access to the bootloader, and default(stock) recovery.
tried oem unlock, but it doesn't work, and shows no errors.
Tried hard reset from the stock recovery and got numerous E: Failed to mount ..... errors. (check attached photo)
All attempts to wipe or format anypart of the phone fail with the same error,
ADB side load of a custom recovery ( TWRP ) also failed with the same error.
Please help me out, data loss is not an issue as i had no imp data and used it mainly for calls and emails.
{
"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"
}
Try flashing twrp.
fastboot flash recovery (ur recovery name).img
Then unmount system from advance and flash a custom rom
pranavmali said:
Try flashing twrp.
fastboot flash recovery (ur recovery name).img
Then unmount system from advance and flash a custom rom
Click to expand...
Click to collapse
It shows an error
FAILED (remote: not supported in locked device)
Like I said, oem unlock doesn't work.
As soon as i give the oem unlock command, it will ask for conformation, after hitting yes,
it will even show LOCK STATE - unlocked.
But as soon as the phone reboots or re-enters bootloader, the phone is back to a locked bootloader.
On unlocking bootloader, flashing TWRP via fastboot, when i enter recovery mode, i am still taken back to the stock recovery.
Try Wug fresh's tool kit! To unlock bootloader
Does the give give an error message when issuing the fastboot oem unlock command?
pranavmali said:
Try Wug fresh's tool kit! To unlock bootloader
Click to expand...
Click to collapse
No effect, still stuck the same way.
below is the live log from the NRT toolkit
Live log initiated [2016-05-19]:
Analyzing factory image; please be patient...
Further extracting contents of factory image package for use in 'Force Flash Mode'...
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
04bfc514002e14ea fastboot
Connectivity Status: Fastboot Device Connected
+ Bootloader Status: Locked.
Checking ADB/FASTBOOT Connectivity
adb devices
03670030215d290e device
fastboot devices
04bfc514002e14ea fastboot
Connectivity Status: Fastboot Device Connected
+ Bootloader Status: Locked.
fastboot oem unlock
Rebooting your device...
and then suck at bootanimation loop
audit13 said:
Does the give give an error message when issuing the fastboot oem unlock command?
Click to expand...
Click to collapse
when i give the fast boot oem unlock command, it will get executed, my phone will ask for me to manually go to the yes key, hit power button to conform,
I am taken back to the bootloader screen, it shows lock state- unlocked
and the word "erasing..." flashes under it for less than 1 second and thats it...no other change what so ever, as soon as i reboot to bootloader or reboot the phone or do anything, the phone is back to the locked bootloader state.
The emmc is damaged or defective and can only be fixed with a motherboard replacement.
audit13 said:
The emmc is damaged or defective and can only be fixed with a motherboard replacement.
Click to expand...
Click to collapse
is there a sure-shot way of determining that my emmc is damaged ..?
the state that my phone is in now, it would make more sense to just buy a new device rather than replace the motherboard.
or
another option i can consider is the thread - http://forum.xda-developers.com/google-nexus-5/help/nexus-5-64gb-t3350533 for getting a new emmc and replacing, but before i take any actions i would like to know that there is no other option left.
Since you now appear to have nothing to lose, try installing the full N5 OTA image:
https://developers.google.com/android/nexus/ota#hammerhead-for-nexus-5-mobile
The instructions are on the page, or NRT has an OTA option (Advanced utilities/Sideload OTA update).
It may not work if your bootloader is genuinely locked or if the EMMC is really fried, but worst case you can't do any more damage, right?
Hi guys, I need a little help, what happens is that I went to the settings to unlock the bootloader and then proceeded to flash a rom, but after this I got the error "system has been destroyed" Does it mean that to fix it I need to wait for my bootloader to unlock? I forgot that I had to wait a week and I'm not sure what this is because of not waiting or another error, I would also like to know if after time I can fix it since using the MI unlock tool from xiaomi tells me that wait for the time and use the my flash tool to install the stock rom it drops the error "erase is not allowed in lock state"
(EDIT) finish the timer for the unlock bootloader, and after that i just flash a stock rom, thanks for everyone who support me
Re-flash Stock ROM
Tell the problem clearly what issues you are facing??
aaashzz said:
Tell the problem clearly what issues you are facing??
Click to expand...
Click to collapse
This is the problem, I wanted to go back to a previous version of MIUI, so I added my account to unlock the bootloader and immediately used the XiaomiToolV2 tool to flash this ROM, everything seemed to go well until the end of the device I started with the error "Systen has been destroyed "I read that flashing the stock ROM would solve it but when doing it in the MIflashtool tool it would give me the error" erase is not allowed in lock state "
{
"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"
}
Syxnetrax said:
This is the problem, I wanted to go back to a previous version of MIUI, so I added my account to unlock the bootloader and immediately used the XiaomiToolV2 tool to flash this ROM, everything seemed to go well until the end of the device I started with the error "Systen has been destroyed "I read that flashing the stock ROM would solve it but when doing it in the MIflashtool tool it would give me the error" erase is not allowed in lock state "
View attachment 5198249
Click to expand...
Click to collapse
Yes tha'ts right you can not flash rom with a locked boot loader. there is only way to recover your phone is via edl mode. Flashing the rom via edl mode requires an edl account. The edl account is not available for everyone it's only available for the developer's and services center's. So it's better you take your phone to a service center. Because this problem most probably can't solved by user because everyone May not have a edl account authorised by xiaomi. And the with miflash tool you cannot unlock your phone there is an entirely different tool for unlocking the bootloader "miunlock tool" they are entirely different tools the miflash is only for flash mi rom and for lock your phone. And the other side the miunlock tool is for unlocking the bootloader!
aaashzz said:
Yes tha'ts right you can not flash os with a locked boot loader. there is only way to recover your phone is via edl mode. Flashing the rom via edl mode requires an edl account. The edl account is not available for everyone it's only available for the developer's and services center's. So it's better you take your phone to a service center. Because this problem most probably can't solved by user because everyone May not have a edl account authorised by xiaomi.
Click to expand...
Click to collapse
But the unlocking has already started, even the xiaomi tool tells me that I have 41 hours left until it is unlocked, according to me after that I can repair it myself by flashing the ROM, or am I wrong?
Syxnetrax said:
But the unlocking has already started, even the xiaomi tool tells me that I have 41 hours left until it is unlocked, according to me after that I can repair it myself by flashing the ROM, or am I wrong?
Click to expand...
Click to collapse
Is the bootloader is unlocked, do you able boot the phone into fastboot mode?
aaashzz said:
Is the bootloader is unlocked, do you able boot the phone into fastboot mode?
Click to expand...
Click to collapse
i can access the fastboot, and the unlock will finish in the time mencioned
Syxnetrax said:
i can access the fastboot, and the unlock will finish in the time mencioned
Click to expand...
Click to collapse
To check whether Fastboot is really dealing with phone's bootloader, you run
Code:
fastboot devices
If you don't see fastboot in second line of command's output phone isn't booted into bootloader mode
To check whether phone's bootloader is unlocked, you run
Code:
fastboot getvar secure
If YES is returned then bootloader isn't unlocked.
jwoegerbauer said:
To check whether Fastboot is really dealing with phone's bootloader, you run
Code:
fastboot devices
If you don't see fastboot in second line of command's output phone isn't booted into bootloader mode
To check whether phone's bootloader is unlocked, you run
Code:
fastboot getvar secure
If YES is returned then bootloader isn't unlocked.
Click to expand...
Click to collapse
bootloader is working fine, i get a yes because i need to wait 40 hours more for the bootloader to unlock, my understanding is that after the time i can flash the stock rom, can anyone confirm?
Syxnetrax said:
bootloader is working fine, i get a yes because i need to wait 40 hours more for the bootloader to unlock, my understanding is that after the time i can flash the stock rom, can anyone confirm?
Click to expand...
Click to collapse
To flash a phone's Stock ROM it's not required that phone's bootloader is unlocked.
You flash phone's Stock ROM as shown next
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
flashing stock rom does not require bootloader to be unlocked.
just flash the rom using adb or fastboot
i will recommend using fastboot because it's reliable but some time it requires unlocked bootloader so just try fastboot after adb has failed.
jwoegerbauer said:
To flash a phone's Stock ROM it's not required that phone's bootloader is unlocked.
You flash phone's Stock ROM as shown next
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
Click to expand...
Click to collapse
adb reboot sideload starts a bootloop of the same screen "ths system has been destroyed"
bro, just go to recovery and type adb devices if any device is listed then give command adb sideload <drag file for its location> and press enter if it work tell me
Bhanu8082 said:
bro, just go to recovery and type adb devices if any device is listed then give command adb sideload <drag file for its location> and press enter if it work tell me
Click to expand...
Click to collapse
this happend, idk if im doing something wrong
Syxnetrax said:
View attachment 5198725
this happend, idk if im doing something wrong
Click to expand...
Click to collapse
Rename Stock ROM's .ZIP-fie to stock-rom.zip,, then it it should work
jwoegerbauer said:
Rename Stock ROM's .ZIP-fie to stock-rom.zip,, then it it should work
Click to expand...
Click to collapse
after this the same error repeats and start to bootloop with the system has been destroyed screen
bro problem might be your version of adb just use latest version or try version
Android Debug Bridge version 1.0.32
version 1.0.32 is reliable for me as it works
Syxnetrax said:
after this the same error repeats and start to bootloop with the system has been destroyed screen
Click to expand...
Click to collapse
Fix for "The system has been destroyed" Redmi note 8/8T
Fix for "The system has been destroyed" Redmi note 8/8T This will only work for unlocked bootloader...this guide will help you recover from the System has been destroyed when trying to install custom rom or recovery or maybe some other actions...
forum.xda-developers.com
Syxnetrax said:
But the unlocking has already started, even the xiaomi tool tells me that I have 41 hours left until it is unlocked, according to me after that I can repair it myself by flashing the ROM, or am I wrong?
Click to expand...
Click to collapse
Hey did you fixed the phone ??
so, i was trying to install twrp, but i made a stupid mistake, instead of fastboot flash recovery i did fastboot flash boot, now it tells me: "the current image(boot/recovery) have been destroyed", when i go into bootloader, and attack the cable (both before and after) restarts itself.
things I tried: flash the original boot (it gave "FAILED (Write to device failed (no link))", obviously before the bootloader happened) change usb cable, flash the stock rom (obviously before the bootloader happened)), redownload adb /fastboot drivers, phone drivers, and google drivers. this is all i remember trying to do, i'm desperate, could someone help me please?
update: now i can use bootloader
update: I fixed it, in case this situation happened to you, I solved it like this: I had a windows update, while it was doing it, I connected the phone to the pc, in the end it no longer rebooted by itself (the phone) , then do fastboot flash boot (original boot), if it doesn't work, reboot the bootloader , from the bootloader, if it doesn't work, do the same thing downloading the drivers again, then do fastboot flash boot (original boot.img), if you want to download costum recovery, do fastboot flash recovery (costum recovery.img). I fixed it like this, now I have a costum recovery, costum rom and root!
Hello friend, I have a question. I closed the bootloader and when I closed it, the recovery image was destroyed.
Now I can't enter my cell phone and it stays in an infinite boot
any solution with locked bootloader
Angel1104 said:
Hello friend, I have a question. I closed the bootloader and when I closed it, the recovery image was destroyed.
Now I can't enter my cell phone and it stays in an infinite boot
any solution with locked bootloader
Click to expand...
Click to collapse
try going into the bootloader and re-unlocking it
{
"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"
}
That happened to me when I wanted to block the boot, so I think the boot was blocked and only stayed in the realme recovery like the following photo
Angel1104 said:
View attachment 5798249That happened to me when I wanted to block the boot, so I think the boot was blocked and only stayed in the realme recovery like the following photo
Click to expand...
Click to collapse
I don't understand if the recovery works or not, it's a bootloop with locked bootloader and you can go into recovery or locked bootloader without accessing recovery? you are confusing me, however, if you have access to recovery download the stock rom from the recovery, if not, try to unlock the bootloader again by doing fastboot flashing unlock, then flash the stock recovery and then download the stock rom from the recovery
And how do you enter that mode without the application?
enter bootloader and do fastboot reboot recovery, in bootloader you can't perform flashing actions and many other things (bootloader locked) but some things, like reboot should work
in case you get the same error for the recovery you have to unlock the bootloader again
Can I send you a private message?
yes
Did you solve it? I'm facing the same issue.
Gamer_Mida said:
update: I fixed it, in case this situation happened to you, I solved it like this: I had a windows update, while it was doing it, I connected the phone to the pc, in the end it no longer rebooted by itself (the phone) , then do fastboot flash boot (original boot), if it doesn't work, reboot the bootloader , from the bootloader, if it doesn't work, do the same thing downloading the drivers again, then do fastboot flash boot (original boot.img), if you want to download costum recovery, do fastboot flash recovery (costum recovery.img). I fixed it like this, now I have a costum recovery, costum rom and root!
Click to expand...
Click to collapse
I am having trouble understanding what you did exactly. I am getting this same error with a Xiaomi Mi 8 Lite.
Edit: got it working by disconnecting all usb ports and trying another port.
Angel1104 said:
Hello friend, I have a question. I closed the bootloader and when I closed it, the recovery image was destroyed.
Now I can't enter my cell phone and it stays in an infinite boot
any solution with locked bootloader
Click to expand...
Click to collapse
same as me i dont know what to do