i recently purchased a refurbished Indian G5 Plus. I followed the unlocking tutorial and it seemed like the bootloader was unlocked properly. I do get a warning saying the device is unlocked when trying to boot up, but it also says "ID : bad key" which was a little unsettling. I tried flashing twrp.img using fastboot and that too seemed to work (th eprocess completed saying "Okay"). However, when I try to go to recovery from the fastboot screen, I end up in a screen saying no command and pressing vol up+ pwr takes me to what I assume is the stock recovery. What should I do to be able to flash twrp?
Solved it myself. I had to flash the recovery again and boot directly into it. Booting into system first is what caused the problem.
SD008 said:
Solved it myself. I had to flash the recovery again and boot directly into it. Booting into system first is what caused the problem.
Click to expand...
Click to collapse
How do you solve it. I can't flash twrp recovery on my moto g5 plus. It says FAILED (data transfer failure (Unknown error)) every time I flash twrp recvery. I have tried different version of twrp. And my device says bad key when it boots up. Please give me a detail solution
Related
Hi,
Currently on 2.22.40.54 firmware, and successfully rooted it, but with a wrong root method. Therefore I lost camera access. Followed this guide , and flashed the 2.22.40.30 fastboot / recovery (which was successful), but the firmware flash didnt proceed, (had to restart), which resulted in not able to access fastboot / recovery. Tried flashing a new recovery tru xFSTK, but encountered the driver error and the ASUS Flash Tool gives me "serial number not found" error... I usually get the USB logo on start up, but sometimes I get a normal boot (which is nice).
Now, what is the best way to recover my recovery / fastboot? I'm willing to try everything except bringing it to a Service Center.
turn off devices and then pres power buton and vol. up y will see asus logo then pres only vol. up .. if it will works please write there
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"
"your device software cannot be checked for corruption" after installing twrp, help!!
Hello, as title says, following oem unlock procedure, i flashed twrp using fasboot however i could never boot it and now when i try to go to fastboot mode and/or reboot, i see this message "your device software cannot be checked for corruption[...] please lock bootloader"!! Dunno what to do? Please help!
Easy: do absolutely nothing, this is intended behaviour. Unlocking the bootloader leads to the displaying of this message on boot up. Just LG's way of saying continue at your own risk.
Ok so they're even more annoying than samsung..! Anyway, my problem is : how do i enter TWRP..? I flashed again, successfully.. Then i dunno how to enter it!
"The stock recovery appears but you have to select the factory reset option and it will boot into TWRP" i read this. Well it's wrong. Doing so just launch the factory reset!
This video https://www.youtube.com/watch?v=MR4DTgTxhGI shows phone reboots to TWRP after entering "fastboot reboot" (once recovery was flash) : here it just reboots normally!
"Finally Type “fastboot boot TWRP-Recovery-filename.img” to boot your LG G6 into TWRP Recovery" well i thought about that and tried it :
D:\Android\ADB&Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.901s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.925s
I'm very disapointed so far, i expected the G6 to be easier to handle the S7 but it's a pain even before i start using it.. Hell!!
It seems to me that you didn't boot into twrp immediately after flashing it via fastboot. Afaik it's important that you don't boot into OS after flashing, otherwise twrp will be overwritten with stock recovery. I had the same problem when I did the procedure.
The only way I got it to work was booting into twrp via button combo immediately after flash (you know - keep pushing power and vol- until Lg G6 logo appears, release only power and immediately push it again, keep 'em pushed until factory reset, confirm twice and it should boot into twrp). Once you've booted into twrp directly after flashing, it should stick.
grushnickij said:
It seems to me that you didn't boot into twrp immediately after flashing it via fastboot. Afaik it's important that you don't boot into OS after flashing, otherwise twrp will be overwritten with stock recovery. I had the same problem when I did the procedure.
The only way I got it to work was booting into twrp via button combo immediately after flash (you know - keep pushing power and vol- until Lg G6 logo appears, release only power and immediately push it again, keep 'em pushed until factory reset, confirm twice and it should boot into twrp). Once you've booted into twrp directly after flashing, it should stick.
Click to expand...
Click to collapse
After doing this, for TWRP to stick, you have to flash a custom rom, or delete the system/bin/install-recovery.sh to prevent stock recovery overtwrite
Hello everybody !
My A2017G displays the unlocked bootloader warning message, and then says that "Your device is corrupt [...] will poweroff in 30 seconds".
When the second message is displayed, if:
I hold power button, LOS15.1 starts properly and work well.
I hold power button + volume up, Recovery TWRP Nfound is launched.
So my question is: Is it the normal way to start the phone? Or something wrong during flash ?
What I have done:
I tried to flash my A2017G from LOS14.1 to LOS15.1, with some difficulties
I booted in (functional) TWRP, flash zip file of Oreo modem and universal bootloader, success
Always in TWRP, I flash TWRP NFound image. Try to reboot in the new recovery ... Problem occurs
Finally I found a way to go into recovery mode (read above) and format data, system ... and flash LOS15.1
I have access to fastboot, recovery and EDL mode.
TTR6214 said:
Hello everybody !
My A2017G displays the unlocked bootloader warning message, and then says that "Your device is corrupt [...] will poweroff in 30 seconds".
When the second message is displayed, if:
I hold power button, LOS15.1 starts properly and work well.
I hold power button + volume up, Recovery TWRP Nfound is launched.
So my question is: Is it the normal way to start the phone? Or something wrong during flash ?
What I have done:
I tried to flash my A2017G from LOS14.1 to LOS15.1, with some difficulties
I booted in (functional) TWRP, flash zip file of Oreo modem and universal bootloader, success
Always in TWRP, I flash TWRP NFound image. Try to reboot in the new recovery ... Problem occurs
Finally I found a way to go into recovery mode (read above) and format data, system ... and flash LOS15.1
I have access to fastboot, recovery and EDL mode.
Click to expand...
Click to collapse
this is normal due unlocked bootloader and custom bootstack.
Its mentioned everywhere....
Predatorhaze said:
this is normal due unlocked bootloader and custom bootstack.
Its mentioned everywhere....
Click to expand...
Click to collapse
I already know about warning message due to unlocked bootloader. After 5 seconds phone boots normally.
But in my case, after the warning, phone doesn't boot and displays "Your device is corrupted ..."
I can boot only if I press power button during the second warning.
If I try
Code:
fastboot boot recovery.img
, phone will never boot into recovery.
TTR6214 said:
I already know about warning message due to unlocked bootloader. After 5 seconds phone boots normally.
But in my case, after the warning, phone doesn't boot and displays "Your device is corrupted ..."
I can boot only if I press power button during the second warning.
If I try , phone will never boot into recovery.
Click to expand...
Click to collapse
Also the second screen is normal,its because modified bootstack.Just press power button and your good to go.Modified b20 splash bootstack does not have this
Predatorhaze said:
Also the second screen is normal,its because modified bootstack.Just press power button and your good to go.Modified b20 splash bootstack does not have this
Click to expand...
Click to collapse
Ok thanks for your answer and explanation
Hello
Long story short, i digged out my axon 7 to use it with some music apps.
I wanted to return the phone to stock firmware, it had unlocked bootloader and running a custom nougat rom (AEX i think).
I followed this thread: https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413 and flashed full EDL package.
Now when i try to turn on the phone, or enter recovery i see the boot logo and quick flash of the commandpromt with a broken droid and the phone turn off again.
I can still enter EDL mode and flash the phone.
Any ideas how i get it up and ruunning gain ? preferably on stock firmware
Thanks
Drunkenmazter said:
Hello
Long story short, i digged out my axon 7 to use it with some music apps.
I wanted to return the phone to stock firmware, it had unlocked bootloader and running a custom nougat rom (AEX i think).
I followed this thread: https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413 and flashed full EDL package.
Now when i try to turn on the phone, or enter recovery i see the boot logo and quick flash of the commandpromt with a broken droid and the phone turn off again.
I can still enter EDL mode and flash the phone.
Any ideas how i get it up and ruunning gain ? preferably on stock firmware
Thanks
Click to expand...
Click to collapse
Use one of the less archaic methods:
Download "EDL Tool" from the ROMs, kernels, development section, along with an EDL package that goes with your phone model. Put your phone in EDL and just flash it with that tool. after that, if it still doesn't boot you have to format data, because you might have conflicting data. If you can't do it from EDL Tool (i think you can, don't remember) just enter the recovery with Vol+ and Power and make a factory reset
My story is very similar and now i'm stuck in EDL mode. I was able to flash stock Oreo B02 EDL package successfully and boot into OS. But after i was trying to unlock bootloader and reboot to recovery, ZTE logo appears for a second or two and then following error message starts looping:
(broken droid logo)
No command
Supported API: 3
E:failed to mount /cache: Invalid argument
E:Can't mount /cache/recovery/last_locale
EDL mode works but if i flash EDL package or boot/recovery again nothing changes, i still get the same error. Can't boot to OS any more and recovery does not work - screen just stays black.
So what are my options now to get it to work again?
From some other threads, I believe you could try to EDL flash Nougat instead of Oreo, it would work better.
https://forum.xda-developers.com/axon-7/help/help-edl-factory-restore-stuck-device-t4031619
I did that already but no luck, i still end up with the same error.
Is there some way to reformat or clean up internal storage completely in EDL mode? It seems that some garbage left behind by trying to unlock bootloader is surviving even EDL ROM flash and breaking OS boot.
xperiaatic said:
I did that already but no luck, i still end up with the same error.
Is there some way to reformat or clean up internal storage completely in EDL mode? It seems that some garbage left behind by trying to unlock bootloader is surviving even EDL ROM flash and breaking OS boot.
Click to expand...
Click to collapse
According to other threads, the problem could be due to "sparse" structure while flashing.
I suggest the following:
- Use Axon 7 EDL toolkit to flash latest official TWRP recovery (for Oreo a specific TWRP would be requied).
- Inside TWRP then wipe data/factory reset and at the utmost Format data. Then retry to boot.
- If not OK, reflash with EDL full ROM and try again.
Already done that for several times with O ja N EDL rom's but no luck. Can't get to recovery nor make system to boot.
Did you successful unlocked bootloader?
If not, I would recommended Axon 7 EDL Tool by djkuz, flashing nougat edl package and unlock it through the options.
Can you get into stock recovery after flashing EDL package? It supposed to have a format option for userdata and cache.
Did you try to get into fastboot mode? Power + Vol up buttons if i'm not wrong.
If so, you could try to format these partitions.
fastboot erase /cache
fastboot erase /data
I have experienced the same problem but I have resolved flashing, with Xiaomi MiFlash (sometimes I use this program because occasionally flashing EDL packages with AxonEDLTool, it gives me problems like this) this package Axon7_RR-O_B32-B10_TREBLE-Ready_Oki20180803_FULL_EDL.
With this EDL, if the flash is successful, you will find NFound recovery 3.2.1-7 installed with which you can make a complete wipe and / or format them with the file system you prefer.
Afterwards, using MiFlash or EDLTool at your discretion, you can flash the EDL of the original system if you prefer.
I'm not an expert but this has solved my problem.
To unlock the bootloader, if the unlocking with EDLTool does not go well (it happened to me just yesterday while I was installing a Rom on another Axon 7), you can use Axon7ToolKit 1.2.1, it always worked well for me.
I hope it can help :fingers-crossed:.
xperiaatic said:
My story is very similar and now i'm stuck in EDL mode. I was able to flash stock Oreo B02 EDL package successfully and boot into OS. But after i was trying to unlock bootloader and reboot to recovery, ZTE logo appears for a second or two and then following error message starts looping:
(broken droid logo)
No command
Supported API: 3
E:failed to mount /cache: Invalid argument
E:Can't mount /cache/recovery/last_locale
EDL mode works but if i flash EDL package or boot/recovery again nothing changes, i still get the same error. Can't boot to OS any more and recovery does not work - screen just stays black.
So what are my options now to get it to work again?
Click to expand...
Click to collapse
Hi, just want to let here my solution for the same problem, it may help others.
I tried to flash A2017G_B10_NOUGAT_FULL_EDL and A2017G_B02_OREO_FULL_EDL but always getting the Can't mount /cache/recovery/last_locale error, phone completely bricked.
So I flashed A2017_B13_FULL_EDL_UNBRICK_DFU using MiFlash through EDL, you can find this here: https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898 (if your EDL mode works fine there is no need to disassemble the phone as shown in that tutorial)
Now the phone is completely working, recovery and system, but everything in chinese.
Then I flashed A2017G_B02_OREO_FULL_EDL using MiFlash through EDL, and now everything is working and in english
Thanks a lot for the tip! A2017_B13_FULL_EDL_UNBRICK_DFU did the trick and unbrick the phone.
What i did:
1. used MiFlash to flash A2017_B13_FULL_EDL_UNBRICK_DFU
2. after that A2017G_B03_OREO_FULL_EDL
3. reboot to recovery and performed factory reset
First time I did not perform the factory reset and got stuck on the boot picture without the reset function (power button did not work). Drained the battery and performed factory reset and got the phone working again.
update:
Phone is not stable on B03, some apps crashing from time to time for no apparent reason and also soft reboots happening randomly.
Now I got stuck on the Axon boot screen again after rebooting the phone manually and waiting for the battery to drain ...
i did not install or perform any custom action to the system, just regular use and apps, but it is still acting up badly.
I was planning to use this phone as a secondary handset because it is actually a very nice piece of hardware but now i am starting to have second thoughts about that.