Hi,
I have following problem, phone is D405N:
If I boot into fastboot and try to flash some file - TWRP recovery for example I always get following error:
c:\adb>fastboot flash recovery L90.img
target reported max download size of 536870912 bytes
sending 'recovery' (13818 KB)...
OKAY [ 0.546s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.546s
Any idea where is a problem and how to fix this it? Using latest adb and drivers also.
same here
Did you tried with driver from @LaDY Vengeance post?
http://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825
neverdies said:
Did you tried with driver from @LaDY Vengeance post?
http://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825
Click to expand...
Click to collapse
I tried those drivers, and I have no luck. I have the same problem, except that I can't use any command, they all return FAILED (remote: unknown command)
I'm stuck in fastboot, and with this issue I can't flash the backup img's to restore it.
SOMEONE PLS HELP
jmang98 said:
I tried those drivers, and I have no luck. I have the same problem, except that I can't use any command, they all return FAILED (remote: unknown command)
I'm stuck in fastboot, and with this issue I can't flash the backup img's to restore it.
SOMEONE PLS HELP
Click to expand...
Click to collapse
what steps have you done so far?
ie: unlock/root/flash recovery?
itsJohnuno said:
what steps have you done so far?
ie: unlock/root/flash recovery?
Click to expand...
Click to collapse
Same problem....
Did anyone who was having this problem end up finding a fix?
This is a problem I have too, need a fix.
Still need a solution. Is this due to lollipop? Cuz back then I was able to unlock the bootloader. LG L90 D415
BlaMa said:
Hi,
I have following problem, phone is D405N:
If I boot into fastboot and try to flash some file - TWRP recovery for example I always get following error:
c:\adb>fastboot flash recovery L90.img
target reported max download size of 536870912 bytes
sending 'recovery' (13818 KB)...
OKAY [ 0.546s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.546s
Any idea where is a problem and how to fix this it? Using latest adb and drivers also.
Click to expand...
Click to collapse
D405_v20a_patched_aboot??
http://forum.xda-developers.com/lg-l90/development/recovery-twrp2-7-1-0lgl90w7xxshoxx-t2826150
EDIT:
Did you flash D405_v20a_patched_aboot if not, you need to flash D405_v20a_patched_aboot
i also have same poblem d415
me too...same problem D415 tmobile version
Does anyone with this problem have an lg d-415 and android with root? Because I think these commands in a terminal emulator or in an adb shell will fix fastboot:
Code:
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
Or if that doesn't work try this >> https://forum.xda-developers.com/lg...ick-hard-bricked-l90-variants-t3173429/page24
I think this problem is caused by people not unlocking the bootloader.
Same error on LG D415
BlaMa said:
Hi,
I have following problem, phone is D405N:
If I boot into fastboot and try to flash some file - TWRP recovery for example I always get following error:
c:\adb>fastboot flash recovery L90.img
target reported max download size of 536870912 bytes
sending 'recovery' (13818 KB)...
OKAY [ 0.546s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.546s
Any idea where is a problem and how to fix this it? Using latest adb and drivers also.
Click to expand...
Click to collapse
PLEASE HELP. I'm getting the same error on my LG D415. They said on the other thread that this variant comes with the bootloader already unlocked but whenever i try to enter a command (e.g fastboot flash laf laf.img) or pretty much every command I enter (except fastboot getvar all and fastboot devices), I get the same message FAILED (remote: unknown command). My android is now stuck on the T-mobile logo whenever I try to power it up and I can't flash because download mode has been replaced with fastboot.
aixhinnn said:
PLEASE HELP. I'm getting the same error on my LG D415. They said on the other thread that this variant comes with the bootloader already unlocked but whenever i try to enter a command (e.g fastboot flash laf laf.img) or pretty much every command I enter (except fastboot getvar all and fastboot devices), I get the same message FAILED (remote: unknown command). My android is now stuck on the T-mobile logo whenever I try to power it up and I can't flash because download mode has been replaced with fastboot.
Click to expand...
Click to collapse
How did you enable fastboot, what commands did you run?
0000.0000.00 said:
How did you enable fastboot, what commands did you run?
Click to expand...
Click to collapse
i followed this guide
https://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-t-mobile-l90-t2836457
but once I was already in fastboot no other commands work.
aixhinnn said:
i followed this guide
https://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-t-mobile-l90-t2836457
but once I was already in fastboot no other commands work.
Click to expand...
Click to collapse
Did you try volume down+ power to factory reset and see if that fixes it?
im having this problem too, but on an lg v10 tmobile
17mm said:
im having this problem too, but on an lg v10 tmobile
Click to expand...
Click to collapse
This problem is strange and I'm not sure if it has a solution.
0000.0000.00 said:
This problem is strange and I'm not sure if it has a solution.
Click to expand...
Click to collapse
what i did was get lg bridge and mobile support, let if flash the most current update then used this method to root on the latest 30c update https://forum.xda-developers.com/tm...901-nougat-t3773942/post76711778#post76711778
twrp flashed fine, magisk installed flawlessly, now rooted on latest official update with all kinds of goodies to play with :good:
oh and with magisk you pass safetynet aswell so all good.
Related
Hello all!
So recently I was playing around with my G4, and decided to see if i could boot into fastboot mode. Turned out I could: theandroidsoul.com/lg-g3-fastboot-mode-61660/, but it would remove download mode in the process. It was totally useless. I couldn't run any commands and so I decided to put download mode back. I rebooted my phone, a notification caught my eye, and I completely forgot to put it back.
Fast forward a couple days, and my phone starts to run at 2 miles per hour. So, I factory reset, losing root and recovery in the process. That still didn't fix it, and now the camera, all speakers, and microphone don't work. Now, I can't replace download mode without root, so I cant run the LG Flash Tool. I'm starting to lose my mind over this. Please help!
Can your phone boot to android at all? if yes, then this might help put TWRP back on the phone WITHOUT ROOT. http://forum.xda-developers.com/tmobile-g4/development/tool-one-click-twrp-root-t3172936 thank micromod for making it possible.
MrSteelX said:
Can your phone boot to android at all? if yes, then this might help put TWRP back on the phone WITHOUT ROOT. http://forum.xda-developers.com/tmobile-g4/development/tool-one-click-twrp-root-t3172936 thank micromod for making it possible.
Click to expand...
Click to collapse
I can, but that unfortunately requires download mode, which I removed(oops).
jlynch630 said:
I can, but that unfortunately requires download mode, which I removed(oops).
Click to expand...
Click to collapse
Factory reset should have kept twrp recovery on the phone. With phone off, hold vol down and power together, when you see lg logo just release power button the hold it down again stioll holding vol down. say yes to the next 2 screens and it should boot into recovery.
MrSteelX said:
Factory reset should have kept twrp recovery on the phone. With phone off, hold vol down and power together, when you see lg logo just release power button the hold it down again stioll holding vol down. say yes to the next 2 screens and it should boot into recovery.
Click to expand...
Click to collapse
Hmm... I must have done something then, because it isn't there anymore. It just boots to the android logo and resets my phone.
jlynch630 said:
Hmm... I must have done something then, because it isn't there anymore. It just boots to the android logo and resets my phone.
Click to expand...
Click to collapse
Your only hope is to get fastboot to work then or lg service center
MrSteelX said:
Your only hope is to get fastboot to work then or lg service center
Click to expand...
Click to collapse
Heres what fastboot says:
Code:
[COLOR="Red"]FASTBOOT MODE[/COLOR]
PRODUCT NAME - msm9992_p1_tmo_us
VARIANT - msm9992_p1_tmo_us Toshiba 32GB
HW VERSION - rev-10
BOOTLOADER VERSION - N/A
BASEBAND VERSION - N/A
CARRIER INFO - N/A
SERIAL NUMBER - LGH811********
SIGNING - Production
SECURE_BOOT - disabled
LOCK_STATE - locked
[1280]
[1280] Fastboot mode started
[2780]
I think the lockstate may be why it doesn't work. Any clues to disable it?
jlynch630 said:
Heres what fastboot says:
Code:
[COLOR="Red"]FASTBOOT MODE[/COLOR]
PRODUCT NAME - msm9992_p1_tmo_us
VARIANT - msm9992_p1_tmo_us Toshiba 32GB
HW VERSION - rev-10
BOOTLOADER VERSION - N/A
BASEBAND VERSION - N/A
CARRIER INFO - N/A
SERIAL NUMBER - LGH811********
SIGNING - Production
SECURE_BOOT - disabled
LOCK_STATE - locked
[1280]
[1280] Fastboot mode started
[2780]
I think the lockstate may be why it doesn't work. Any clues to disable it?
Click to expand...
Click to collapse
Have twrp on internal storage then run
fastboot flash recovery twrp.img pray it flashes twrp and go from there.
MrSteelX said:
Have twrp on internal storage then run
fastboot flash recovery twrp.img pray it flashes twrp and go from there.
Click to expand...
Click to collapse
Ohh!! So close! It finishes writing, but then says : Failed(remote: Unknown Command)
jlynch630 said:
Ohh!! So close! It finishes writing, but then says : Failed(remote: Unknown Command)
Click to expand...
Click to collapse
in android, do u have the oem lock checked
also make sure that twrp is named twrp.img
MrSteelX said:
in android, do u have the oem lock checked
also make sure that twrp is named twrp.img
Click to expand...
Click to collapse
I didn't, but I enabled it and tried again, and it still didn't work.
try updating adb from the latest SDK. Also check to make sure your twrp download in not corrupted. then try again.
MrSteelX said:
try updating adb from the latest SDK. Also check to make sure your twrp download in not corrupted. then try again.
Click to expand...
Click to collapse
Updated adb(& fastboot) to no avail
Code:
C:\Users\21JohnL\adb>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.016s
C:\Users\21JohnL\adb>fastboot flash recovery twrp-2.8.7.0-h811.img
target reported max download size of 536870912 bytes
sending 'recovery' (32968 KB)...
OKAY [ 0.719s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.750s
jlynch630 said:
Updated adb(& fastboot) to no avail
Code:
C:\Users\21JohnL\adb>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.016s
C:\Users\21JohnL\adb>fastboot flash recovery twrp-2.8.7.0-h811.img
target reported max download size of 536870912 bytes
sending 'recovery' (32968 KB)...
OKAY [ 0.719s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.750s
Click to expand...
Click to collapse
Did you make a backup of laf?
Yes, why?
EDIT: Haha! Factory reset got me again! I'll make a comment on that page and see if someone has a copy stored
EDIT 2: I found one for the G3, will that work?
jlynch630 said:
Yes, why?
EDIT: Haha! Factory reset got me again! I'll make a comment on that page and see if someone has a copy stored
EDIT 2: I found one for the G3, will that work?
Click to expand...
Click to collapse
https://www.mediafire.com/?4a8bivbgk4s1d7q this is laf from 10n. flash this in fastboot should put download mode back for you.
MrSteelX said:
https://www.mediafire.com/?4a8bivbgk4s1d7q this is laf from 10n. flash this in fastboot should put download mode back for you.
Click to expand...
Click to collapse
Which partition?
Edit:
Still get error
Code:
C:\Users\21JohnL\Downloads>fastboot flash laf "laf (1).img"
target reported max download size of 536870912 bytes
sending 'laf' (36864 KB)...
OKAY [ 0.821s]
writing 'laf'...
FAILED (remote: unknown command)
finished. total time: 0.844s
jlynch630 said:
Which partition?
Click to expand...
Click to collapse
I am not sure at this time. Still goggling the problem.
edit 1.fastboot flash laf laf.img try this.
edit 2. fastboot erase laf.img
fastboot flash laf laf.img
---------- Post added at 08:37 PM ---------- Previous post was at 08:25 PM ----------
jlynch630 said:
Which partition?
Edit:
Still get error
Code:
C:\Users\21JohnL\Downloads>fastboot flash laf "laf (1).img"
target reported max download size of 536870912 bytes
sending 'laf' (36864 KB)...
OKAY [ 0.821s]
writing 'laf'...
FAILED (remote: unknown command)
finished. total time: 0.844s
Click to expand...
Click to collapse
fastboot erase laf.img
fastboot flash laf laf.img
try that.
MrSteelX said:
I am not sure at this time. Still goggling the problem.
edit 1.fastboot flash laf laf.img try this.
edit 2. fastboot erase laf.img
fastboot flash laf laf.img
---------- Post added at 08:37 PM ---------- Previous post was at 08:25 PM ----------
fastboot erase laf.img
fastboot flash laf laf.img
try that.
Click to expand...
Click to collapse
Both return:
Code:
FAILED: (remote:unknown command)
I think something is blocking fastboot commands from running
jlynch630 said:
Both return:
Code:
FAILED: (remote:unknown command)
I think something is blocking fastboot commands from running
Click to expand...
Click to collapse
At this time, I am unable to help you out. You should get into contact with Jcase or Autoprime. They know a lot more about this and may be able to help fix this laf.
fastboot erase laf
When I try:
fastboot boot recovery.img
I only get this and it wont boot into the Cyanogen Recovery :/
downloading 'boot.img'...
OKAY [ 0.217s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.221s
Any idea what I can do?
Check to see what Fire OS version you have. If it is 5.11 then booting a custom recovery will not work til a new custom boot.img can be created for it.
tuckerwagner said:
When I try:
fastboot boot recovery.img
I only get this and it wont boot into the Cyanogen Recovery :/
downloading 'boot.img'...
OKAY [ 0.217s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.221s
Any idea what I can do?
Click to expand...
Click to collapse
As far as I know you can only do temporary recovery boots (either twerp or Cyanogen) using a PC to push the recovery image and then boot it.
Code:
adb reboot bootloader
fastboot TWRP_Fire_2.8.7.0.img
Is what works for me.
same problem. Any way to downgrade?
skola28 said:
same problem. Any way to downgrade?
Click to expand...
Click to collapse
Same here... Bought two, got one to work and I think my girlfriend let the other update and now I am getting the "FAILED (remote: unknown command)" on the other.....
Ugh, time to look at Amazon's return policy?
skola28 said:
same problem. Any way to downgrade?
Click to expand...
Click to collapse
If on 5.1.1, at this time,
cannot root
cannot boot custom recovery
cannot downgrade
once a the update.zip is captured, maybe a new twrp can be built
RW2112 said:
Check to see what Fire OS version you have. If it is 5.11 then booting a custom recovery will not work til a new custom boot.img can be created for it.
Click to expand...
Click to collapse
Turns out it is 5.1.1. I guess I will wait for a new boot.IMG unless there is a way to downgrade. Thanks for your help!
I've got a moto x '14 verizon XT1096. Tried to use fastboot to load twrp to eventually get to install Cm13. However, it threw this message:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (0 KB)...
OKAY [ 0.006s]
writing 'recovery'...
(bootloader) Invalid boot image
FAILED (remote failure)
finished. total time: 0.024s
Dumbass me thought it would be a good idea to unplug the device and simply try again. Well, what a bad decision. The phone now flashes the "no command" robot on it's back. yes, flashes. i can get back to fastboot, but after this i'm not sure what to do.
Thanks in advance. I'm fairly new at this, be easy on me.
Try this. This is my mini guide I wrote in another thread.
Well, at first I tried to flash twrp through fastboot but the original recovery override the twrp recovery.
So, what I did, instead of flashing, I just temporary booted into twrp.
adb reboot bootloader
fastboot boot twrp.img (and not fastboot flash recovery twrp.img)
Then phone booted into twrp, I flash supersu 2.46.
Then I easily downloaded twrp manager from google play and installed twrp recovery to my xt1096.
Have fun
Use this https://twrp.me/devices/motorolamotox2014.html
Click to expand...
Click to collapse
Hi all,
I have an incorrect firmware installed for my P10 and lots of things are not working (oreo 8.0). I want to re-flash or rollback to other firmwares but problem is I can't get into TWRP anymore. flashing it doesn't work and although I see in fastboot Phone Unlocked and FRP unlock i have the idea it has to do with the OEM unlock not working properly. It's also not available in the developer options. What;s exactly the link to huawei's page where you can request your phone unlock ID ?
Thanks
Whats not working ?
What is it saying when flashing something through fastboot ?
virusdunil said:
Whats not working ?
What is it saying when flashing something through fastboot ?
Click to expand...
Click to collapse
When I go into the bootloader and want to flash TWRP I get following message:
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (16494 KB)...
OKAY [ 0.552s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.566s
What is the ADB command youre using ?
virusdunil said:
What is the ADB command youre using ?
Click to expand...
Click to collapse
fastboot flash recovery_ramdisk twrporeo.img
and my twrp oreo name is twrporeo.img
Thats why its not working...
TRY....... fastboot flash ramdisk twrporeo.img
virusdunil said:
Thats why its not working...
TRY....... fastboot flash ramdisk twrporeo.img
Click to expand...
Click to collapse
Same problem...:
C:\Android>fastboot flash ramdisk twrporeo.img
target reported max download size of 471859200 bytes
sending 'ramdisk' (16494 KB)...
OKAY [ 0.532s]
writing 'ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.546s
i did a mistake...its really recovery_ramdisk
Look Here...
TWRP
virusdunil said:
i did a mistake...its really recovery_ramdisk
Look Here...
TWRP
Click to expand...
Click to collapse
I already tried that but no success. Did a factory reset and now the bootloader is locked again. How can I unlock the bootloader again?
Thanks
1-is your phone working now ?
for bootloader unlock,do what you did first time... fastboot oem unlock yourcode123
how did you get the last update ?....firmware finder ?
virusdunil said:
1-is your phone working now ?
for bootloader unlock,do what you did first time... fastboot oem unlock yourcode123
how did you get the last update ?....firmware finder ?
Click to expand...
Click to collapse
First of all, I've tried to update from Nougat to Orea via Blackballs method in this thread https://forum.xda-developers.com/p10-plus/development/oreo-update-thread-l29c432-t3729907 with the firmware mentioned there
What is not working:
I've managed to do the first part (oreo install), but:
- SImcard has 'No service
- Can't flash TWRP
- Bootloader / phone locked in Fastboot
- I can't remember how I unlocked the P10 last year (I have a P10 L09-VTR, rebranded to L29-VTR and now 'working' on a VKY P10 plus rom)
How to unlock the OEM when I could not activate the developer options, because the device does not turn on?
It is not possible to flash a ROM because it says: flashing_locked
In short, the device only goes to Fastboot.
------------------
I manage to do the following. I did a temporary boot via Fastboot.
fastboot boot "Original ROM file or Boot.img Patched with Root"
More information I have I will be putting it here.
An application to use adb and fastboot without a computer.
Bugjaeger or Bugjaeger Premium
ps: requires otg support on the device you are going to control.
I'm out of results at the moment, I couldn't recover my Moto G7 Plus.
I've already lost almost 100% of the hopes that I can manage.
I think I will have to send it to a Motorola Official Technician or buy another device, as it is not worth me to have it fixed. because the stores are far from my city.
I was able to start the device, but I still can't activate oem unlock.
it is already a progress.
I used a modified boot.img and started the device using:
fastboot boot boot.img
the problem I have to use this command to turn on the device without...
if i get more news i will talk here.
Anrito Kun said:
if i get more news i will talk here.
Click to expand...
Click to collapse
Did you manage to solve it, or did you have any progress?
Could you send the boot.img file you used?
wfsmnt said:
Did you manage to solve it, or did you have any progress?
Could you send the boot.img file you used?
Click to expand...
Click to collapse
------------------
I don't know how to send files here.
I have no new results, but I will try to send the boot.img that could connect the device.
wfsmnt said:
Did you manage to solve it, or did you have any progress?
Could you send the boot.img file you used?
Click to expand...
Click to collapse
Boot.img: https://mirrorbits.lineageos.org/recovery/lake/20201222/lineage-17.1-20201222-recovery-lake.img
I haven't been able to do anything new yet.
I think that only specialist technicians will know how to fix the device.
Anrito Kun said:
Boot.img: https://mirrorbits.lineageos.org/recovery/lake/20201222/lineage-17.1-20201222-recovery-lake.img
Click to expand...
Click to collapse
------------------
After downloading use the command: fastboot boot file.img
This managed to start the device, but I couldn't get into Recovery ... At least I couldn't.
Does anyone know how to patch a boot.img file? most have to sign almost the same kernel signature.
Anrito Kun said:
Does anyone know how to patch a boot.img file? most have to sign almost the same kernel signature.
Click to expand...
Click to collapse
------------------
I think it may be possible to join TWRP with the system's Boot.img. As if it were a magched patched, only instead of magisk it is TWRP.
delete
delete
poog said:
Thanks for replying to my post. I tried your patched boot.img but when I try to flash it I get " (bootloader) fllash permission denied "
renamed it to boot.img and then....tried 2 things that fail
C:\adb>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.501s]
booting...
(bootloader) Failed to load/authenticate boot image: Not Found
FAILED (remote failure)
finished. total time: 0.510s
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (21845 KB)...
OKAY [ 0.465s]
writing 'boot'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.479s
Click to expand...
Click to collapse
------------------
You're using the Moto G7 plus, right?
the command has to be this to use the file:
fastboot boot "file name".img
poog said:
I can boot to fastboot, but I cannot flash anything. I cannot get a proper return with "fastboot devices"
I cannot get RSD LITE to recognize my device. (win 10). I have read to try win7
Device Manager (windows 10) can only show the device as "Motorola ADB Device". I have not figured out how to force it to show as Qualcom ..............if that will make a difference or not. qualcom drivers are installed.
Before I messed it up I was able to load the device as a qualcom device on the right port and blankflashed after I hardbricked with nothing on screen.
Ability to boot to fastboot but not flash anything seems it is effectively dead for now.
Click to expand...
Click to collapse
------------------
There is no point in trying Flash on the device when the device is Flashing Locked.
My phone is in the same situation after I tried to re-lock the bootloader. Please do follow up on your progress.
hey I have the same problem have you found a solution?
Unfortunately, no.