I am in need of some assistance. Been trying to update to a new version of Android. However i keep receiving failed to update messages. So i figured i would wipe the phone clean. I went to recovery (PhilZ Touch 6) and took the option to wipe everyhting (Clean to install a New ROM). However i am encountering some problems. The phone is now stuck at "Warning bootloader unlocked". So i cant really 'access' my phone. I tried sideloading a .zip firmware via PhilZ mod, but the problem is that my device does not show up as connected.
What can i do?`I've killed the adb server and restarted it several times, restarted phone and computer several times, without any luck. Whenever i go in to fastboot mode and insert the USB cable, it still says "Connect USB data cable".
Help would be very much appreciated .
Hi
Well if you're trying to update from a stock firmware or a rom based on stock it will always show an error because you modified a system file, in this case you changed your recovery, so it wont let you update.
The phone is stuck because you erased the OS so now you have to flash again the stock firmware via fastboot or flash twrp recovery and then copy a rom from your PC to the phone.
Try to flash your stock back using Odin.
And this time use proper methods to root, flast ROMs and kernels and unlocking the boot loader.
The problems generally arise when you ignore the procedure.
Soory for the bad language. Hope it has helped you
The problem is though i cannot get the computer/phone to recognize that the other one exists. No matter what I do it says Connect USB data cable, even though its connected. Which means i cannot get the device to show up in the CMD menu.
If you boot into a Linux Live CD (for example, Ubuntu) fastboot / adb will work - provided the problem is not your cable.
Whenever i'm in the bootloader menu, when i look at my device manager on the PC, it says Fastboot Falcon S "the drivers for this device are not installed". but i'm unable to install them because windows cant find them.
Also, no problem with the cable since it works for other phones and devices.
Another problem i have noticed is that i cannot turn the phone off. It just restarts sitting at the "Warning bootloader unlocked screen".
samuelcr93 said:
Hi
Well if you're trying to update from a stock firmware or a rom based on stock it will always show an error because you modified a system file, in this case you changed your recovery, so it wont let you update.
The phone is stuck because you erased the OS so now you have to flash again the stock firmware via fastboot or flash twrp recovery and then copy a rom from your PC to the phone.
Click to expand...
Click to collapse
I cannot copy anything to the phone, because it does not show up on my computer.
When i have the phone connected via the USB cable and running PhilZ Touch 6, my device manager shows XT1032 and a yellow exclamation mark on it. When i go to properties, it says "drivers for this device are not installed".
I had the same issue with philz but using twrp the mtp mode works fine
How can i install twrp instead?
Download the twrp. Img file and flash it using fastboot
The thing is though, how do i flash ANYTHING, when i cannot even get my device and computer to recognize eachother? the adb devices command returns nothing, just blank space under "List of devices attached". Since there is no OS i cannot enable USB-debugging. So i'm kind of stuck in a catch 22 it seems.
are you using motorola fastboot to flash? or just adb .exe?
Ive tried using regular fastboot and mfastboot nothing works
Can you post a screenshot of the phone in fastboot mode and fasboot console?
---------- Post added at 06:01 PM ---------- Previous post was at 05:52 PM ----------
Have you tried reinstalling the Motorola drivers?
Yes i've already tried reinstalling the motorola device drivers.
Here is a screenshot of the fastboot mode
{
"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"
}
This is how it looks with USB cable plugged in
http://postimg.org/image/nng2g7io7/
http://postimg.org/image/lvrdeh4bd/
If you type "fastboot devices" instead of adb does it shows the same?
If your usb cable is working fine then maybe you could try using another PC
This is what happens when i use the fastboot command
http://postimg.org/image/dv2x28r9v/
cr00mz said:
This is what happens when i use the fastboot command
Click to expand...
Click to collapse
The common solutions are:
(i) Try a different usb cable
(ii) Reinstall Motorola Drivers
(iii) Load a linux live CD on PC / Laptop - Drivers are not required then
(iv) Try another PC / Laptop
(v) Install a newer version of Windows​
I) Tried several USB cables
II)Tried reinstalling the motorola drivers
III)This i dont know how to do, is there a link with perhaps a tutorial or a guide?
IV)If all else fails i guess i'll have to try this, just a bit difficult to get access to another computer
V)already have windows 10
Related
Hello,
I was attempting to clean out (format) everything on my phone and start over with a fresh ROM, and it looks like I went a bit overboard. Now I'm stuck at the bootloader, but it appears to be frozen. When it loads, I get:
Code:
FASTBOOT MODE - NO BOOT OR RECOVERY IMG
PRODUCT NAME - HERRING
HW VERSION - REV 11
BOOTLOADER VERSION - 19020XXLC2
BASEBAND VERSION - 19020XXKI1
CARRIER INFO - TMB
SERIAL NUMBER - (REDACTED)
LOCK STATE - UNLOCKED
The menu appears as well, but I am unable to change the current selection, or perform a selection. (My power button stopped functioning a couple months ago).
Occasionally when I unplug the usb cable I'll see a quick message "USB Control Init USB Control Init End" and it restarts the bootloader. FASTBOOT MODE then just appears empty, and I still cannot access the menu items.
ADB was working before, but now 2 separate computers cannot detect it using "adb devices". I hadn't tried 'fastboot devices' beforehand, but it doesn't detect the phone now.
I tried installing a couple different drivers (Google's, PDANet), and using Wugfresh NRT, but could never connect.
So how's it look, doc? Will it live? Or should I bury it?
Thanks!
Lanik42 said:
So how's it look, doc? Will it live? Or should I bury it?
Click to expand...
Click to collapse
As long as the bootloader isn't deleted there's a good chance.
I think you have deleted the OS and the recovery :silly:
When you are in the bootloader, only fastboot commands work.
Type "fastboot devices" to check the connection
Or "fastboot help"
https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
I had to force the "Google Nexus BootLoader Interface" driver onto the system (win 8.1)
I know it says Acer, but it is my Nexus S
{
"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"
}
When fastboot.exe can see your device you can flash a recovery image.
"fastboot flash recovery recovery.img"
"fastboot boot recovery.img"
You should now be able to start the recovery and use the adb commands.
Hope some of this can help
Thanks for the response! I wasn't sure if I would even get a reply, as the board appears to be rather quiet.
Lar5 said:
As long as the bootloader isn't deleted there's a good chance.
I think you have deleted the OS and the recovery :silly:
Click to expand...
Click to collapse
Yeah, I'm afraid I did. I got a little overly aggressive in my data purge
Lar5 said:
When you are in the bootloader, only fastboot commands work.
Type "fastboot devices" to check the connection
Or "fastboot help"
Click to expand...
Click to collapse
Sadly, therein lies my problem. I haven't been able to get fastboot to recognize my device, at all
Lar5 said:
I had to force the "Google Nexus BootLoader Interface" driver onto the system (win 8.1)
I know it says Acer, but it is my Nexus S
View attachment 2936108
When fastboot.exe can see your device you can flash a recovery image.
"fastboot flash recovery recovery.img"
"fastboot boot recovery.img"
You should now be able to start the recovery and use the adb commands.
Hope some of this can help
Click to expand...
Click to collapse
I tried the driver install listed, and I assume it successfuly installed, though I'm not sure how I'd check. but I'm still having the same problem. neither fastboot nor adb recognize the device (though as you said, adb wouldn't at this stage either way).
It doesn't appear that it's even showing up in the device manager (using Windows 7 x64). No search for drivers, no unrecognized device, nothing
I'm afraid it means that my phone is actually freezing during the bootloader loading, since the computer does not appear to recognize it and I can't navigate its menu.
Is there anything I'm forgetting? I may try booting into a Linux live image, to see if windows is just ignoring due to some driver issue. Will follow up with those results.
Thanks again!
I suggest removing all drivers. Each and every trace of it to be removed. Then install the Google USB drivers.
You can also get drivers from Windows Update...
Bootloop
Hi there, i was on cm7, than i found this rom "Desire XS version 1.1" and I decided to install it, after aroma installation, I rebooted it and now i'm in bootloop and i can't access to hboot, what should I do?
Hi, I assume you are s-on with unlock bootloader? If yes, then enter fastboot(if my memory serves me right, hold vol down and power on). The instructions can be found here. I assume u have already wipe/format and flash the rom, so the next thing to do is flash the boot.img in fastboot, found in the link, step 4.
Thank you for your reply, but i think that i can't access to fastboot
evilken9555 said:
Thank you for your reply, but i think that i can't access to fastboot
Click to expand...
Click to collapse
pull the battery out for a min then put back in, u should be able to boot into bootloader then select fastboot in the menu
Got an update :
Both of the suggestions didn't work, so i've tried to connect my phone to a PC and tried to use adb to access into fastboot mode, once I've got into fastboot I've tried to install the stock firmware through ruu, but I get an error : USB error
{
"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"
}
#Fear said:
Hi, I assume you are s-on with unlock bootloader? If yes, then enter fastboot(if my memory serves me right, hold vol down and power on). The instructions can be found here. I assume u have already wipe/format and flash the rom, so the next thing to do is flash the boot.img in fastboot, found in the link, step 4.
Click to expand...
Click to collapse
i can't find boot.img :|
edit: i've found the boot.img, now the problem is that when i connect my phone to the pc when it is in fastboot mode, after a bit a notification with a yellow exclamation mark appears and says "Usb device not recognized", i have windows 8.1, could it be the problem?
evilken9555 said:
i can't find boot.img :|
edit: i've found the boot.img, now the problem is that when i connect my phone to the pc when it is in fastboot mode, after a bit a notification with a yellow exclamation mark appears and says "Usb device not recognized", i have windows 8.1, could it be the problem?
Click to expand...
Click to collapse
the ruu wont work coz ur bootloader is "unlocked". u need to relock it then run the ruu. and yes windows 8 is a problem with fastboot, theres a few guides here on xda how to use fastboot with windows 8. so either find a way to get fastboot working then flash custom rom in recovery then flash the boot.img via fastboot or relock the bootloader (ul need fastboot commands working for that too) and then run ur ruu. either way, get fastboot working first.
jmcclue said:
the ruu wont work coz ur bootloader is "unlocked". u need to relock it then run the ruu. and yes windows 8 is a problem with fastboot, theres a few guides here on xda how to use fastboot with windows 8. so either find a way to get fastboot working then flash custom rom in recovery then flash the boot.img via fastboot or relock the bootloader (ul need fastboot commands working for that too) and then run ur ruu. either way, get fastboot working first.
Click to expand...
Click to collapse
thank you for your support guys, i'll try this in the afternoon =).
I wanted to thank you so much guys, thank you for your help and kindess, i've finally installed the original sense rom =).
Have a good day!
I have bricked M2 D2303. I don't know how it was bricked for the first time(it's not mine), but yesterday I temporarily resurected it by flashtool. It booted and worked few minutes on any system(i dont remember what it was) After trying to put customrecovery it started to bootloop.
Now Flashtool doesn't see this device anymore, but fastboot is stil alive. I flashed CM12.1 boot.img - it showed sony logo, android logo and then bootanimation(blue waves). After few more tries of flashing different images it doesn't start to boot, screen remains black. I searched for boot, system and userdata IMG packets, but I've found only this one: http://forum.xda-developers.com/xperia-m2/general/aosp-5-0-2-d2303-progress-t3073842
After flashing nothing happens. Fastboot still works, but flashtool doesn't.
I don't have any idea how to resurect it now...
I've never had any sony android device... My only ones were nexuses and Oneplus One.
Try repairing using Sony PC Companion...This may solve your problem
Than you. I tried to follow this instruction: http://talk.sonymobile.com/t5/Xperi...uctions-using-Pc-Companion-Win-or/td-p/249946
But in my version of app isn't any "repair phone/tablet" button
{
"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"
}
Download the TWRP recovery and OmniROM or any other flashable ROM.
Flash the recovery through fastboot.
Reboot into the recovery, allow /system modification and install the ROM; reboot to system.
Then re-flash stock if needed.
Maybe stupid question. I've already tried to unbrick via recovery yesterday, but I can't boot it. I flashed TWRP by "fastboot flash recovery twrp.img" but i wasn't able to boot. ADB works only on android and there is no fastboot command to boot recovery. I tried some hotkeys like volume up/down, both, but they do nothing.
fastboot boot twrp.img also returns an error.
wefhy said:
Maybe stupid question. I've already tried to unbrick via recovery yesterday, but I can't boot it. I flashed TWRP by "fastboot flash recovery twrp.img" but i wasn't able to boot. ADB works only on android and there is no fastboot command to boot recovery. I tried some hotkeys like volume up/down, both, but they do nothing.
fastboot boot twrp.img also returns an error.
Click to expand...
Click to collapse
If the bootloader is locked you shouldn't be able to flash any .img file. It it isn't unlocked in order to flash a recovery the phone must have a kernel (Sony made them for KK) that supports the recovery in a separate partition. Stock Xperia phones don't. Flashing any random .img file I won't be surprise if the phone gets bricked, it isn't like in many other phones.
Anyway, to fix it you must be able to flash via flash mode. Flashtool when connecting a phone reports in the log which mode is enabled (if the phone gets recognized at all). So you can use it to see if anything is alive. If the flash mode is dead for any reason but fastboot still works you must a kernel for Xperia M2 flashable via fastboot, if any is available. That may reopen the flash mode and from there do a phone repair from PC Companion.
Oh, and as usual if you are in Windows be sure all USB drivers are correctly installed..
wefhy said:
Than you. I tried to follow this instruction: http://talk.sonymobile.com/t5/Xperi...uctions-using-Pc-Companion-Win-or/td-p/249946
But in my version of app isn't any "repair phone/tablet" button
Click to expand...
Click to collapse
To repair your phone by using PC Companion you have to go to Support Zone: 1
Then follow the steps (sorry for the language i can't change it) : 2
3
I hope it will help you
Hope your Xperia will fixed bro,
Keep your spirit
@Miche1asso
Fastboot mode works, I'm able to flash any boot image.
Windows drivers are installed correctly because flashtool repaired this phone few days ago.
Wchich kernel to flash? Recovey-friendly one? It's for 4.4.4, but last installed system was lollipop. I am able to flash system via recovery on bricked sony device? On my Oneplus One it's impossible.
Or rather any original kernel to revive flashtool?
Unfortunately most of download links are dead :/
@tromine It would be better if my PC companion worked the same... Support zone shows nothing.
Edit: I flashed this kernel: http://www.android.gs/install-cwm-recovery-on-sony-xperia-m2-lte/ It's a progress - its shows sony logo again I tried few times to boot into recovery bu every time it stucked on sony logo. I pressed power off button (next to sim/sd) and left it for few minutes on c harger and... It booted into recovery (without any volume hotkey)
It looks like stock recovery on my oneplus or zenfone:
I am able to flash system using it? Only stock one or any?
O rather i should flash any other recovery?
Push zip file via ADB or any other way to tho this?
Or one question for everything: What's the fastest way to flash CM12.1 from there?
Edit: Nearer than farther Now I have CWM v6 on it But it still can't flash any system image
It says installation aborted; error in storage(...).zip; can't partition non mmbcblk device: /devices/msm_sdcc.2/mmc_host
Edit3: I tried 4 roms(stock rooted, CM12, CM11 and one more) and the same error. I have no idea what to do next... cant partition... maybe flashing userdata? It was flashed recently... Anyone knows what can i do?
sorry for doubleposting, i can't delete it.
wefhy said:
Edit3: I tried 4 roms(stock rooted, CM12, CM11 and one more) and the same error. I have no idea what to do next... cant partition... maybe flashing userdata? It was flashed recently... Anyone knows what can i do?
sorry for doubleposting, i can't delete it.
Click to expand...
Click to collapse
Wich flashtool do you use?
wefhy said:
Edit3: I tried 4 roms(stock rooted, CM12, CM11 and one more) and the same error. I have no idea what to do next... cant partition... maybe flashing userdata? It was flashed recently... Anyone knows what can i do?
sorry for doubleposting, i can't delete it.
Click to expand...
Click to collapse
A couple of things: Did you update PC Companion to the last release? It must have the option to repair the phone somewhere. I can't help much on that because I use the OS X version, but the option is there on one of the top menu.
Anyway, since you managed to flash a working kernel (with CWM) the phone isn't bricked. From there (the CWM) I would flash a full custom ROM which includes a kernel with CWM, obviously wiping everything (cache and data). The kernel must belong to the ROM to avoid further troubles. At that point hopefully the flash mode is restored. But even if it isn't from there with the last PC Companion repair the phone.
PS: I realize I messed up a bit writing in English in my previous post. But it seems you've got what I meant anyway.
I use the newest flashtool and PC companion downloaded from sony page. I updated them.
I searched few times, but my pc companioj just hadn't got repair option.
CWM wasn't able to flash anything(alwatys the same error)
Anyway... I installed flashtool on Linux Mint. It detected device immediately. As linux version is hardly outdated, it couldn't flash anything on this device(device list stopped on Xperia T/S - no M/M2) but somehow it unlocked my xperia.
When I next time tried to use flashtool on windows it just detected it and flashed stock.
Now I'm on 5.1.1 and everything works fine Thanks!
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.
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