hii guys i can't install twrp on my play.....whenever i enter the command i get the error
"error: cannot load twrp-lux-2.8.7.0"
also the windroid tool says twrp flashed successfully but when i reboot into recovery it boots into stock recovery with "no command" on display
any help appreciated
What are you typing when trying to flash?
fastboot flash recovery nameoffile.img
Not sure if you are having the same issue I did.
Are you flashing TWRP then using the reboot command to restart your phone immediately?
If so, try flashing TWRP again. Instead of rebooting, try to access the recovery menu right after flashing. This worked for me. The post I saw related to this mentioned the Moto was overwriting something when rebooting. I haven't had any issues since.
Related
So I rooted my Nexus Player running Marshmallow (6.0) using the instructions here:
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
My bootloader is unlocked, I flashed the boot.img from the first post in the above thread, (already flashed TWRP), then booted into recovery and flashed SuperSU 2.56 from the 2nd post. When I launch SuperSU it tells me that the SU binary needs to be updated, but it can't do it the "normal" way so I try to do it via the TWRP way, it says it's going to attempt to boot into recovery, but recovery never comes up, it looks like it's rebooting, and just hangs on a black screen. So I tried doing "adb reboot recovery" when SuperSU says it's going to try to reboot into recovery itself and do that before clicking ok, but I get the same results. If I go into recovery via the hardware button, no updating happens. It just loads recovery. If I load up the Nexus Player like normal boot, and connected to my PC do "adb reboot recovery" it loads the recovery fine without hanging on any black screen.
So I'm at a loss here on what to do. Any help is appreciated. Thanks!
I got cm 13 running on my d801 g2 the other day and I'm not a fan of it so I'm planning on flashing to cloudy g2 2.2 but now i am unable to boot into twrp. I enabled root, installed twrp and even enabled advanced reboot to boot directly into recovery but i keep getting secure booting error Cause: boot certification error which is what i was getting on stock android before getting cm13, i fixed the issue before with the kitkat auto rec app but I've read that auto rec can cause a hard brick if used in marshmallow. Trying to get into twrp through twrp, cm advanced reboot, hard key(power and vol down) recovery, flashify and adb reboot recovery command all cause the same error message. Any advice? I tried flashing twrp 3.0.0.4 and that put me into fastboot as does any other twrp version I've tried in flashify
lg g2 bricked
hevydevy said:
I got cm 13 running on my d801 g2 the other day and I'm not a fan of it so I'm planning on flashing to cloudy g2 2.2 but now i am unable to boot into twrp. I enabled root, installed twrp and even enabled advanced reboot to boot directly into recovery but i keep getting secure booting error Cause: boot certification error which is what i was getting on stock android before getting cm13, i fixed the issue before with the kitkat auto rec app but I've read that auto rec can cause a hard brick if used in marshmallow. Trying to get into twrp through twrp, cm advanced reboot, hard key(power and vol down) recovery, flashify and adb reboot recovery command all cause the same error message. Any advice? I tried flashing twrp 3.0.0.4 and that put me into fastboot as does any other twrp version I've tried in flashify
Click to expand...
Click to collapse
does ur phone goes in download mode?
kalpesh patil said:
does ur phone goes in download mode?
Click to expand...
Click to collapse
It will give me the download mode message then goes to a black screen. My computer brings up 15 disc partitions with only one partition containing data, one folder called image with files include adsp, cmnlib, mc_v2, modem, playread, wcnss and widevine they all have duplicates with different file types b00-b26 and mdt .
Hey everyone,
I decided to root my lg g6 and got a fickle. After unlocking the device and flashing TWRP I tried to boot into it (''adb reboot recovery'' command) and it deleted all data and then twrp shows on screen for a split second and almost instantly boots normally into android so I set it up while still being unable to access twrp and any of it's functions. Does anyone have any idea what could be the problem?
P.S. Of it helps: before that i had a problem that every time I tried to use the ''adb reboot recovery'' command the console said ''no devices/emulators found''. After a couple tries I wanted to check whether the phone was connected just to make sure (''adb devices'') and after that it worked and I ran into the problem above.
Thanks for all the answers
When you first unlock BL and flash recovery you have to manually enter recovery mode.
Hold power and vol down till it turns off. Hold same buttons again until you see lg logo. Release power and press and hold again.
Then ask you to wipe etc hit yes both times and it will boot to twrp.
I tried that but it still doesn't go into twrp. After confirming that wipe stuff it just boots into android (without wiping)
Ulrih said:
I tried that but it still doesn't go into twrp. After confirming that wipe stuff it just boots into android (without wiping)
Click to expand...
Click to collapse
You have to flash TWRP recovery and when it complete then use the button combo to boot into twrp, otherwise it will boot and restore the recovery.
flash twrp
button combo to twrp
done
Yes I've done that but the problem still exist.
btw thanks for the help
Maybe try fastboot flash recovery recovery.img
Try the all-in-one tool on this forum
By the way, I am running into the same issue.. I have a LG G6 US997,.. I have tried installing TWRP unofficial ones so many times and every time i manually try to access the recovery.. the phone simply wipes all my data to default
Hello,
I have the same problem. Did anyone figure out how to solve it? I'd highly appreciate any help.
If I try to boot into recovery, it asks me to factory reset, i hit yes twice and then the phone just goes on to boot normally. The data is not wiped but I can't get into TWRP.
If I enter "fastboot reboot recovery" after flashing TWRP it returns "fastboot: usage: unknown reboot target recovery"
i want to install pixel experience, i use twrp wipe data, system. Then i install the custom rom, and i suddenly install again the twrp and wrong clicked 'boot' and installed. After that, 'no command' occur when i boot into recovery mode. How can i fix it? I flash recovery through adb but also 'no command'... Pls help me:crying:
ArlenCheng said:
i want to install pixel experience, i use twrp wipe data, system. Then i install the custom rom, and i suddenly install again the twrp and wrong clicked 'boot' and installed. After that, 'no command' occur when i boot into recovery mode. How can i fix it? I flash recovery through adb but also 'no command'... Pls help me:crying:
Click to expand...
Click to collapse
You forgot to reboot recovery instead of the system after flashing TWRP so have lost TWRP. There is essentially no recovery on the phone now which is why you are getting that message. You need to boot TWRP using the fastboot image from fastmode mode and then reinstall TWRP again from there. Make sure to reboot to recovery after flashing. TWRP should stick after this.
Hi,
I have been using my P Smart (FIG-LX1) for a while with LineageOS 16 and decided to move on to Android 10. Installed LineageOS 17.1 (found it on this forum) and pph-Magisk 20.3 for root - it did work, but the system was unstable so i decided to try AOSP 10.0 instead. I entered TWRP, wiped cache,dalvik,system and data, flashed the ROM, gapps etc. It was advised to now flash stock recovery and use it to do a factory reset - and now i'm stuck here.
After flashing the recovery_ramdisk img the phone stopped being able to enter any recovery at all. The system itself does not boot (stuck on the "Your device has been unlocked (...) Your device is booting now..." screen forever), the recovery never appears (previously in the start screen with 'unlocked device' warning it used to suggest pressing volume UP to enter recovery, now it only shows "Your device is booting now"). As i can still access fastboot, I tried flashing TWRP again - the TWRP splash screen does appear, but the phone gets stuck on it. Also tried flashing another system's img - nothing changed.
Is there anything I can do or did i just brick it completely?
Thanks for help!
SOLVED:
Apparently running fastboot erase on system and userdata partitions made me able to boot into recovery/erecovery again. I do have another problem now, but it's not connected with this one so I will create another thread for that.
Could you try help me? I can't even get ADB to work anymore