No command error after flashing TWRP and trying to boot into recovery - LG Stylo 2 Plus Questions & Answers

This particular model is a LGMS550. It is currently on stock firmware at Android 7.0, and it is just not making it's way to TWRP.
I've tried the method where you do the factory reset prompt that supposedly takes you to TWRP, however this only brought it to the screen that read "Erasing" and rebooted like normal.
I made extra sure the bootloader was unlocked.
Trying "fastboot boot (twrpfilename).img" only gave me "FAILED (remote: unknown command)" from the command prompt.
I tried 2 different versions of TWRP. The 64-bit version linked here, along with the official version (3.3.1 currently).
Using "adb reboot recovery" with USB debugging brings me to the "no command" screen that I've seen talked about all over the forums with no good answers. Even looked around on other forums to no avail.
Also tried the awful answer I read that just said "keep trying the factory reset method until it works". Did it 5 times to no success.
What a strangely common issue that has no solution. Does anybody have anything or am I SOL for no apparent reason?
EDIT: Got a quick, fast answer from the lovely person from this post.
No idea the circumstances of what caused this, but hope this will prevent some headaches for you all in the future. Also just to future-proof in case of the post being deleted or something:
1. Go back into fastboot (easy way is just to hold volume down while powering on with the USB plugged in)
2. Re-lock the bootloader with "fastboot oem lock" and unlock it again with "fastboot oem unlock".
3. Erase the recovery partition with "fastboot erase recovery" and then flash TWRP with "fastboot flash (file).img"
4. Reboot and do the hard reset method (reboot while holding power+volume down, let go and press back down instantly when the LG logo shows up, and factory reset by pressing Yes on the prompt twice)
5. Hopefully you're in TWRP by now.
No idea why this works, but it's the only thing that ended up working. Hope it works for you.

Related

Stuck on Bootloop & FirstAid kit won't help. Any Ideas? Please Help

Hello everyone!
Okay, so I'll try to keep it as short as possible but with the most information I can give ofc.
So here's what I did with my Oneplus 2:
- unlocked bootloader
- flashed custom recovery (twrp)
- flashed superSU.zip
- flashed xposed.zip
- used it for about half a year if not even longer
everything on Lollipop 5.1 stock rom so xposed would work.
Everything was fine but some day when I wanted to enter twrp recovery it didn't work. (I swear, this is the most illogical thing ever but I DID NOT CHANGE A THING!)
I tried to enter recovery via fastboot but that didn't work either.
So I reflashed latest TWRP recovery.img for OP2 via fastboot.
When I pressed power + vol. down to see if it'd work nothing happened.
When I tried to enter recovery when my system was booted via power button->restart->recovery my phone got stuck in a bootloop.
I had to go in fastboot mode to enter "fastboot continue" in order to get my phone booting normal again.
Then, one night when my phone was in my pocket it vibrated and got stuck in the bootloop again, even though it was booted into system and locked last time I used it (minutes before that).
I had no access to a computer at that moment so I had to wait for a few days.
Now when I boot my phone in fastboot mode and try to enter "fastboot continue" on my cmd nothing happens with my phone and cmd says "(command write failed (Unknown error))" even though "fastboot devices" shows that my device is connected properly.
I also tried:
- the FirstAidKit, copied the Win Files in my fastboot directory and started the firstaid.bat but it stops on "fastboot flash boot boot.img" (I waited for like two hours).
- a different USB port (USB 3 and USB 2)
I am kinda depending on my phone so yeah..
If someone knows how to fix this I would be very grateful.
Have a good day/night
SoulSnatcher
Do you have a backup??
If yes, download the latest official OS from Oneplus and the stock recovery. Flash the stock recovery. Try rebooting into stock recovery. If it succeeds, wipe everything and flash OS via adb sideload.
Honestly, I can't guess what went wrong with your device. Maybe it could've been some app which crashed the entire system.
AJay27 said:
Flash the stock recovery.
Click to expand...
Click to collapse
Same problem as with the FirstAidKit:
"fastboot devices" does display the device but "fastboot flash recovery recovery.img" doesn't do anything (I waited for 1h just to make sure).
I'll try this Mega Unbrick Guide for A Hard Bricked OnePlus 2 next, even though I can get into fastboot but since it doesn't do s**t I'll have to give it a try. I mean, what's the worst thing that could happen? That my phone gets bricked?!
Haha.... hmm.
I'll keep the person(s) updated who care to know what's happening.
Cheers
fml

Problems booting into recovery

Okay, to start with, I've read the other threads about this. I understand the process that *should* work:
1. Power off.
2. Then, press and hold both all Volume Down + Power buttons at the same time until the LG Logo is being displayed on your LG V20.
3. Now, release the keys and press the above combination again however, this time you should wait until recovery mode menu is displayed.
...and I've tried the version where you keep holding the Volume Down button the entire time.
So, yes, I've reached the white screen where it asks you if you want to do a factory reset. I've hit "Yes" to both questions. The problem is that it really does a factory reset then.
---
After unlocking the bootloader, I installed TWRP via fastboot:
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot reboot
...everything went fine.
But I can't get into recovery. And since I'm waiting to have TWRP working so that I can flash root, I can't boot into recovery via an app.
What did I do wrong?
EDIT:
Okay, it looks like TWRP isn't working properly. I tried "adb reboot recovery" and that got me to a dead Android icon and a "No command" message. I have no idea why TWRP isn't working.
Haphim said:
Okay, to start with, I've read the other threads about this. I understand the process that *should* work:
1. Power off.
2. Then, press and hold both all Volume Down + Power buttons at the same time until the LG Logo is being displayed on your LG V20.
3. Now, release the keys and press the above combination again however, this time you should wait until recovery mode menu is displayed.
...and I've tried the version where you keep holding the Volume Down button the entire time.
So, yes, I've reached the white screen where it asks you if you want to do a factory reset. I've hit "Yes" to both questions. The problem is that it really does a factory reset then.
---
After unlocking the bootloader, I installed TWRP via fastboot:
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot reboot
...everything went fine.
But I can't get into recovery. And since I'm waiting to have TWRP working so that I can flash root, I can't boot into recovery via an app.
What did I do wrong?
EDIT:
Okay, it looks like TWRP isn't working properly. I tried "adb reboot recovery" and that got me to a dead Android icon and a "No command" message. I have no idea why TWRP isn't working.
Click to expand...
Click to collapse
to confirm, have you verified you are using the correct TWRP version for your V20?
in this step "fastboot flash recovery twrp.img" is your twrp image that you saved, named twrp.img? If its not, that command won't work correctly.
usually after I flash recovery, when still in the recovery menu, i choose reboot recovery just to make sure it did stick. If it reboots back to itself, then try rebooting the device, and again confirm with manually entering recovery. Maybe overkill but it works for me LOL.
Good luck!
I am in need of big help! I made a critical error after days of trying to navigate the minefields of rooting my device. I have a LG V20 h910 and it is no one-click wonder root. It made me work for it and I finally got it. I loaded LineageOS 14.1 and all was good until the USB OTG cable from my PS4 controller did not register anymore. Damn, that was a let down, and probably led to my careless move of needing to downgrade my TWRP, saw the version I needed, forgot these are device specific, and now I'm stuck in a hard place.
Perhaps the fix is easy, but I have not found the answer after many, many searches...
I had TWRP 3.2.1-2 and needed to downgrade to 3.2.1-0 to try SuperRom (hoping it would have OTG ability). I hastily grabbed the first TWRP 3.2.1-0, threw it on the SD card, wiped everything except internal storage, and flashed the img, and did a reboot. Road block went up.
I tried getting back into recovery, did the PWR and DOWN pressing combo and got the Factory Reset screen, but after clicking "Yes" to both, instead of getting the TWRP screen, I got this error screen (attached).
I tried another idea - hooked it up USB to my PC and tried accessing it via adb/fastboot. I tried multiple drivers for my device, but no adb and no fastboot devices were ever found. The only thing that almost worked was booting phone into FASTBOOT mode by holding DOWN btn and plugging in a USB cable attached to PC. Once in FASTBOOT mode, My PC at least saw the ID for fastboot device. I tried to flash TWRP via fastboot, and it looked like it would happen, but in the end there was no phone screen response to my attempt, and the cmd window on my PC would get stuck and just hang.
Can someone please advise me on how I can fix this problem?

No system, no recovery, bootloader unlocked, FRP locked

After some problems (corrupted data partition and sticking in bootloop after reboot) on LineageOS 14.1 and PA 7.2.2, I decided to reflash the EMUI. That didn't work and through a series of my mistakes I have no recovery, no system and can't flash anything.
Fastboot gives me the "remote: command not allowed" error whatever I try to do except for "fastboot reboot" and "fastboot oem get-bootinfo" (which says the bootloader is unlocked). The fastboot screen says : Phone Unlocked, FRP Lock.
I can connect to adb after a few minutes of waiting at the "Your device is booting now..." screen that also shows 3 options. But I have nothing in /system/, which means /system/bin/sh doesn't exist so I can't get a shell into the phone. "adb ls" does work, though (don't know how).
I've also tried to push at least a shell into /system/ with "adb push", but it says that the partition is mounted read-only. Is there a way to mount it read-write without using "adb shell"?
Is my phone recoverable or is it bricked beyond repair? Any suggestions on how to repair it without changing the motherboard?
Thanks in advance!
CanIHelp said:
After some problems (corrupted data partition and sticking in bootloop after reboot) on LineageOS 14.1 and PA 7.2.2, I decided to reflash the EMUI. That didn't work and through a series of my mistakes I have no recovery, no system and can't flash anything.
Fastboot gives me the "remote: command not allowed" error whatever I try to do except for "fastboot reboot" and "fastboot oem get-bootinfo" (which says the bootloader is unlocked). The fastboot screen says : Phone Unlocked, FRP Lock.
I can connect to adb after a few minutes of waiting at the "Your device is booting now..." screen that also shows 3 options. But I have nothing in /system/, which means /system/bin/sh doesn't exist so I can't get a shell into the phone. "adb ls" does work, though (don't know how).
I've also tried to push at least a shell into /system/ with "adb push", but it says that the partition is mounted read-only. Is there a way to mount it read-write without using "adb shell"?
Is my phone recoverable or is it bricked beyond repair? Any suggestions on how to repair it without changing the motherboard?
Thanks in advance!
Click to expand...
Click to collapse
https://forum.xda-developers.com/huawei-p9lite/how-to/unified-help-thread-huawei-p9-lite-t3649152
Post 5. Unbricking EMUI 5. Don't take for granted it will work, but considering FRP is locked, this is the only way not needing a unlocked bootloader.
Doesn't work. It's still stuck at the "Your device is booting now..." under the vmall link screen.
Isn't the 3-button method counting on the original recovery being in the recovery partition?
I only have the second recovery working (that eRecovery which only lets you "download and install the latest recovery and system"...and doesn't do anything).
Is there a way to override the frp lock? I saw a couple of tools online claiming to do that, but none worked. I haven't tried DC-Unlocker. If I'm gonna pay for it, might as well go to a service
Dload method uses the secondary recovery, It should be there if you press all three buttons.
From what i have heard, DC-Unlocker works.
Plug your phone on computer.
You see yellow advice? Appears automatically.
Juste after this advice, tip "fastboot reboot bootloader".
After, unlock your bootloader again "fastboot oem unlock YOUR_OEM_CODE"
Ok now shutdown and hold buttons for boot to TWRP recovery, if not appears, flash it on "fastboot flash recovery recovery.img"
Warning command not allowed on fastboot is 90% time du at bootloader unlocked (even if he says it's good)
dariomrk said:
Dload method uses the secondary recovery, It should be there if you press all three buttons.
From what i have heard, DC-Unlocker works.
Click to expand...
Click to collapse
It did boot in the secondary recovery (had to hold onto the 3 button for 3-4 minutes continuously). But it said that "Software install failed/ Incompatibility with current version. Please download the correct update package."
I'm now trying the B160 image in that thread. Wish me luck!
EDIT: It worked. The B160 image flashed using the three button method. I'm now at the setup screen. And the keyboard is there. (Also had the problem where I'd only have the voice input keyboard)
Thank you very much!
CanIHelp said:
It did boot in the secondary recovery (had to hold onto the 3 button for 3-4 minutes continuously). But it said that "Software install failed/ Incompatibility with current version. Please download the correct update package."
I'm now trying the B160 image in that thread. Wish me luck!
EDIT: It worked. The B160 image flashed using the three button method. I'm now at the setup screen. And the keyboard is there. (Also had the problem where I'd only have the voice input keyboard)
Thank you very much!
Click to expand...
Click to collapse
No problem mate, nice to hear you did it without problems.

[HELP] Bootloader relocked, won't unlock, boots directly to fastboot

Help, I'm in a real state. I was happy on US997 Fulmics, with root, etc, but decided to try Stock Oreo. I upgraded, didn't like the substratum issues, and restored my Nandroid backup. As others discovered, this means the fingerprint doesn't work. I googled, and saw "just factory reset", so I went into my settings and selected "Factory Reset". This took me to TWRP, because of course, but then when I rebooted system, it took me back to TWRP. After some hours of trying to fix this by flashing various ROMs, I came across the advice to try this command in TWRP Terminal:
dd if=/dev/zero of=/dev/block/platform/624000.ufshc/by-name/misc
dd if=/dev/zero of=/dev/block/platform/624000.ufshc/by-name/fota
Click to expand...
Click to collapse
(except I had to add "/soc" after /platform)
Now my bootloader is locked, and its bootloop directly to Fastboot, and type in "fastboot flash unlock unlock.bin" but it returns "FAILED (remote: oem unlock is not allowed)". I can get into Download mode, and I've tried loading two stock Nougat KDZ files, and it still just brings me to Fastboot, right around 80% in the upload process. I can hold volume and get to the recovery prompt, choose erase, I see a brief window of "Erasing" and then its back to Fastboot.
Please, any help is super appreciated!
I'm back trying to fix this after very little sleep, and am at least trying to ask the right questions.
Are there other Fastboot commands I could be using?
Could I have wiped the boot partition, and that's why it goes to Fastboot when it starts?
Is there a way to restore the boot partition using LGUP?
Are there other ways to unlock the bootloader now?
I see in red letters "Please check "Enable OEM unlock in Developer options" in Fastboot, but I can't get into Android to do that, is there anyway to do enable that from within Fastboot or Download?
Is there a KDZ I could flash that has it enabled?
I'm so upset about breaking this through my own idiocy, and really don't want to have to purchase a new phone right now, so I'm definitely willing to throw a few bucks to anyone who knows a sequence of steps to get me working again!
You need to put it in qc9008 mode and do with jtag box
If u can boot into fastboot mode then all hope is not lost. Try using the official LG bridge app for pc, idk if itll work with an unlocked bootloader device but its worth a try, in the app under the update phone tab there is an option "update error recovery" just connect your phone in fastboot mode, select that option, and follow the app instructions. It should atleast take u back to stock. where u can probably start fresh.

Semi-bricked??

Weird: I was just using it normally, it switched off and now it stays stuck on the Google logo; when entering recovery mode, I get TWRP"s splash screen and it stays there, so I cannot even recover.
Suggestions please??
Note 1: I'm pretty bad with this kind of stuff, need step-by-step instructions.
Note 2: rom is AOSP 7.1.2 but I guess is irrelevant, as even TWRP does not load.
Thanks in advance!!
Can you fastboot boot the TWRP recovery?
Hmmm dont know exactly what that means sorry; I mean I havent tried connecting it to the laptop and using thr ADB toolkit, but I can reset via Power+VolDown to the bootloader menu (? the android layind down and giving the option to StartSystem/ SwitchOff/ Restart/ RecoveryMode), and choosing RecoveyMode it tries to launch TWRP (it even shows the logo) but stays there on the splashscreen, doesn't quite manage to give me the TWRP menus
Someone?
AndDiSa said:
Can you fastboot boot the TWRP recovery?
Click to expand...
Click to collapse
let's see... I set in recovery mode, connect to the PC (does not recognise it), and with "fastboot boot twrp.img" it just sends/writes the file, the tab shows the Google logo with open lock, and then tries to launch Twrp, but as before, it just get stuck in the splashscreen "TeamWin Recovery Project 3.3.1.0" , so just the same.
Command "fastboot flash boot twrp.img" the same
Command "fastboot flash recovery twrp.img" the same
Command "adb devices" returns the list empty
Command "adb reboot recovery" returns "error: no devices / emulators found"
Command "fastboot oem unlock" returns "(bootloader) bootloader is already unlocked"
I tried running a tool called FirstAid (https://forum.xda-developers.com/devdb/project/dl/?id=16684) but does nothing for me
I'm lost, please help
Video and photos of the issue (device, not adb)
video: https://photos.app.goo.gl/GrFrmQhbyQeHVFZN7
Well, looking at your video it seems that there is no bootable ROM installed and also the recovery (for what ever reason) has some issues to start.
The fact, that you are able to boot into bootloader shows that at least it's not completely bricked ... but there's still the chance that the flash memory has some issues.
I would connect the device via usb with a PC and try to do a
fastboot boot <twrp-3.3.1-grouper.img>
to whether in that case the recovery is booting.
If this is successful, the next step would be re-flashing the recovery into the recovery partition and booing into recovery mode from the bootloader.
If this is successful, too, wiping and flashing a new ROM would be the last step.

Categories

Resources