LG refurb updated the ROM to 20x, and (supposedly) replaced MB & RF.
Now I can't get into bootloader, with either ADB or power/vol down combo. Bootloops instead and takes 15 mins to become a working phone again.
I've factory reset 2x today.
Perhaps factory reset and don't restore from Google?
Perhaps 20x is corrupt?
I have no idea what to do next other than deal with the apparent idiots at LG Texas. This is the 2nd "refurb" in a month and 3rd since I've had the G4.
HTC M7 is saving my sanity as backup.
finally got out of bootloop. OEM unlock was the issue in Developer options.
But now having problem getting it to boot into twrp.
fastboot flash recovery twrp.img - went ok, as per past experience.
but - fastboot boot twrp.img - is a no go.
I get this back - cannot load 'twrp.img': No such file or directory.
Can't power down with power button held for 10secs.
Only fastboot reboot works.
What happens if you try to boot into recovery with the key combo (power and vol down until lg logo appears, then release power briefly whilst still holding vol down and then press power again whilst still holding vol down - should bring you to "factory reset page" but once factory reset is confirmed should go to TWRP)
nope, goes to factory reset. tried that twice.
Ok so even after you have flashed twrp, when you enter that factory reset page and click yes twice, it actually factory resets it (that screen is there for everyone but it normally goes to twrp afterwards). Did you boot into your phones OS inbetween flashing twrp and booting to it? LG software replaces twrp with stock recovery if you don't patch the os.
The way to permanently install twrp is:
1) reboot to bootloader and perform "fastboot flash recovery twrp.img"
2) fastboot reboot
3) AS SOON AS IT REBOOTS (<-- that is important) - use key combo and click yes twice - do NOT let it boot back into the main android system inbetween, or you will need to start again
k, I'll give that a go tonite after work. Don't recall the issue with the earlier OS, 20v (before "refurb"), but I'll do oit.
What model of phone is it?
In terms of flashing twrp, that has always been the process (I have a G4 on v20g firmware and it took me a while to work out why twrp kept being wiped)
it's a G40 w/20x. Never had this issue before 20x.
still actually having an issue on reboot. Takes about 7 mins now as it optimizes 1 unknown app.
used this method from fastboot:
fastboot boot twrp.img and pointed (d&d) to twrp on my drive.
then installed twrp from memory as described on twrp page/Fastboot Installation Method.
Ding Ding Ding!
thanks.
Related
So I already had a rooted (and I'm pretty sure unlocked bootlader) version of the stock Asus and wanted to put CM13 nightly on there. Everything was going smooth until I got to the stage where I have to load into TWRP and I got the error screen with the little dead alien and the red symbol.
Now I can't enter normal boot, but entering recovery mode seems to work. I tried the option to side load a package from ADB on that screen but nothing worked (.zip files extracted, but I got an error on the phone).
As you can tell, I'm really new to this so any help would be greatly appreciated. I tried looking around, but it seems the more common issue is people not being able to enter recovery mode or something similar.
Thanks
Looks like your doing it wrong. Being rooted does not necessarily mean that your bootloader is unlocked.
By the looks of it your in recovery mode with the dead robot with the "error" message. That is normal. To reboot back into system you either have to press (I don't remember) power button and volume up or down button. Then you should see some options with reboot to system. Or if that does not work you can hold the power button till it turns off.
Then you get back into Android, download the official bootloader unlock tool from ASUS and install it on your device. NOTE: If you updated to MM then this will not work and this will void your warranty.
Run the tool and press unlock and it should reboot into fastboot where it should begin the unlocking process. I believe it should automatically reboot and you should see that the Asus logo is now black instead of white. If not, repeat the process.
You can now proceed to flash twrp recovery. Boot into fastboot/bootloader mode either with "adb reboot bootloader" or hold a specific set of buttons while off to go directly into fastboot.
On the computer, connect your device and type in "fastboot flash recovery (path to twrp IMG without brackets)"
When done you should be able to reboot into twrp recovery where you can flash the cm13 zip.
Hope this helped.
Hello there,
we have here a Swift that is stuck on a starting screen since an attempt to downgrade from Cyanogenos 13.1 to Cyanogenmod 12.1. Bootloader ist unlocked and to my knowledge only the recovery was flashed via fastboot.
As soon as the USB cable is connected, the screen goes on with "Wileyfox(with logo) powered by android" and remains there.
Luckily fastboot works, but I can't get into recovery. Neither by selecting "reboot into recovery" from fastboot nor by "Vol-" + "Power".
I tried to reflash Cyanogenos 13 via fastboot as it was suggested in several threads (i.e. unzip and flash the different files step by step). Fastboot always stated success, but no luck... Still the same starting screen.
I even tried flashing TWRP recovery, no change either.
Is there something else I can try?
Thank you all
SOLVED: I was persistent: one other threads regarding a lenovo phone suggested to hold down Power and VolDn continuously for several minutes. After about a minute or so and multiple (min. 15x) power off/ons to the "powered by android" screen, I finally got into TWRP! After a format /data I was able to flash the desired CM.
I hope this helps others with similar problems
Erdbeerfrosch said:
Hello there,
we have here a Swift that is stuck on a starting screen since an attempt to downgrade from Cyanogenos 13.1 to Cyanogenmod 12.1. Bootloader ist unlocked and to my knowledge only the recovery was flashed via fastboot.
As soon as the USB cable is connected, the screen goes on with "Wileyfox(with logo) powered by android" and remains there.
Luckily fastboot works, but I can't get into recovery. Neither by selecting "reboot into recovery" from fastboot nor by "Vol-" + "Power".
I tried to reflash Cyanogenos 13 via fastboot as it was suggested in several threads (i.e. unzip and flash the different files step by step). Fastboot always stated success, but no luck... Still the same starting screen.
I even tried flashing TWRP recovery, no change either.
Is there something else I can try?
Thank you all
SOLVED: I was persistent: one other threads regarding a lenovo phone suggested to hold down Power and VolDn continuously for several minutes. After about a minute or so and multiple (min. 15x) power off/ons to the "powered by android" screen, I finally got into TWRP! After a format /data I was able to flash the desired CM.
I hope this helps others with similar problems
Click to expand...
Click to collapse
I've got the same problem. How id you solve yours?
I did hold the VolumeDown+Power buttons for 5 minutes and I did not get into recovery at all (this was with latest TWRP version 3.1.1-0)
Then I thought it could be the TWRP version, and I tried 3.0.3-0 and finally 3.0.0-0.
After flashing 3.0.0-0 I typed "fastboot reboot" and immediately after pressed VolumeDown+Power on the phone and ... finally was in recovery mode, where I could install microG's lineageos version.
cweiske said:
I did hold the VolumeDown+Power buttons for 5 minutes and I did not get into recovery at all (this was with latest TWRP version 3.1.1-0)
Then I thought it could be the TWRP version, and I tried 3.0.3-0 and finally 3.0.0-0.
After flashing 3.0.0-0 I typed "fastboot reboot" and immediately after pressed VolumeDown+Power on the phone and ... finally was in recovery mode, where I could install microG's lineageos version.
Click to expand...
Click to collapse
hi could you post exactly what you did line by line inc code plz i have twrp 3 img just need to get it over i must be typing something wrong.
thanks
im having a problem, my phone wont go out of fast boot mode, tried everything
Any suggestions??
Here is the correct fix, at least it worked for me,
https://forum.xda-developers.com/showpost.php?p=66158015
Hello,
Yesterday, doing noting special, I took my phone from my pocket and saw it was stucked on "fastboot".
Ok, no problem, I made a hard reset (power button 20s-30s): it reboots and immediately the screen fastboot appears.
I tried a fastboot reboot from my PC: idem: it reboots and immediately shows "Fastboot".
I tried vol UP + power button: a menu shows me just 2 options: wipe cache or reboot. I tried wipe cache: nothing better. I reboot in fastboot mode. It's weird because I had TWRP menu before (I rooted it a few months ago).
In summary, I cannot leave from the Fastboot screen. Whatever I do, I always come back to "fastboot" menu.
Could you help me please?
You can try to flash your device with the latest fastboot ROM witch can be found there
Flash MIUI fastboot ROM using MiFlash software..
Note : Do not relock bootloader for safer side
isterios said:
Hello,
Yesterday, doing noting special, I took my phone from my pocket and saw it was stucked on "fastboot".
Ok, no problem, I made a hard reset (power button 20s-30s): it reboots and immediately the screen fastboot appears.
I tried a fastboot reboot from my PC: idem: it reboots and immediately shows "Fastboot".
I tried vol UP + power button: a menu shows me just 2 options: wipe cache or reboot. I tried wipe cache: nothing better. I reboot in fastboot mode. It's weird because I had TWRP menu before (I rooted it a few months ago).
In summary, I cannot leave from the Fastboot screen. Whatever I do, I always come back to "fastboot" menu.
Could you help me please?
Click to expand...
Click to collapse
I had a similar problem like that and I thought all was hopeless and then I tried the simplest thing. Fastboot boot recovery instead of trying to flash it and then I flash the recovery through recovery to make sure everything was okay but it happened when using Orange ? recovery. I have not used it since. I hope this helps.
I bought a Pixel XL yesterday from the local marketplace. It was being sold for cheap and mentioned that after an update the device doesn't start. I bought it for experimentation. When I brought it home it was completely discharged so I hooked it up to a wall charger and tried to turn it on. It turned on but was stuck in bootloop. I left it on charge for about 12 hours or so. After that I picked it up and saw that it was still in bootloop but now it was giving the "no command" screen as opposed to the Google splash screen that it was showing up in the morning. I pressed some buttons and went into recovery. I was completely unfamiliar with the issue at this point. I downloaded the official firmware matching the firmware version with the one being displayed at the top of the recovery screen. I put the phone into the "adb sideload" mode and started the sideload. After it completed the device booted up. I was really happy that I fixed the issue so easily.
However, I immediately got the prompt to update to Android 10 so without doing anything with the phone, I started the update process. I left it to update and after a few minutes I noticed the device was again stuck in the bootloop with the google splash screen. At this point, no matter what I tried, I could not boot into recovery mode but could easily boot into bootloader. After that I did the following things:
-> Tried installing the factory firmware from fastboot using the flash_all.bat file. It failed with an error saying could not update partitions table or something like that
-> I tried to boot into recovery using twrp recovery img but that failed as well, kept getting the Google splash screen
-> I flashed the boot.img from the factory firmware zip (that matched my firmware version) to both the partitions a and b using this command: fastboot flash boot_a path/to/file and fastboot flash boot_ab path/to/file. It did the flashing alright but the device just won't boot into recovery.
-> In short, I exhausted all the options but could not boot into recovery. When powered on with volume up button pressed, the device stayed on a black screen and when I let go the volume up button, the device would start bootlooping again
I hooked up the device to the charger and slept. When I woke up, the device was again stuck in bootloop. I went into bootloader and selected the option to power off. Since the device was on charge it showed the charging battery symbol and automatically landed onto the no command screen. I went into the recovery from there and again sideloaded the factory firmware hoping that the device will boot once done but upon restart it again got stuck into bootloop. I again exhausted all my options but could not get the device boot into the OS. I was however able to boot into twrp recovery and tried to do a complete wipe there but it gave error while wiping the dalvik cache and stopped there without completing the wipe. I pushed the twrp recovery.zip through adb into the device and tried installing, it got stuck while installation was in progress and started rebooting again. I could not get into the recovery again after that point onward. I flashed the factory boot.img to slots a and b but still couldn't get into it.
Now I have hooked up the device to the charger again and left it there. I am hoping after going through the bootloop for another 3 or 4 hours, it will boot into recovery once again. I will provide my results on this.
At this point, does anybody want to share their thoughts on this and suggest something that I should try? One option that I can think off is to disconnect the battery and reconnect it. It may break the loop but I don't want to disassemble the device at this point as I may break something and then won't be able to play with this anymore.
Hello guys,
I have a Ginko device. It started to act weird, as if the volume down button was held down at all times. I took it to some shop and they told me it's most likely software and not hardware, and to try and flash a new ROM.
Now, I believe he was talking out of his ass. Rebooting the phone automatically puts it into fastboot because of the volume- button being broken. If it was a software issue this would not happen, I believe.
Whatever, I decided to try and flash a ROM just because maybe if I have root I will be able to block that button from working somehow.
The issue is, I can't boot into TWRP.
I unlocked the phone through Xiaomi and downloaded TWRP for Ginko. I did the `fastboot flash recovery twrp.img` thing and it works fine, but after that the command to reboot it to recovery `fastboot boot twrp.img` does not work. The fastboot image goes black for .1s then it shows the fastboot image again. Nothing happens. If I run the command again it takes a few seconds shoing "booting..." then the phone reboots to SYSTEM and an error shows on the CMD saying "FAILED (status read failed (Too many links))".
The only way I've found to boot to recovery is by using `adb reboot recovery` but that needs me to boot into system, which means TWRP is erased and the default recovery comes up.
If I reboot the phone the only way to go into system is by holding volume+, as it seems to counter the broken volume- button... But that means I can't boot to recovery, no matter how many times I try.
So I have no idea what to do.
AckmanDESU said:
Hello guys,
I have a Ginko device. It started to act weird, as if the volume down button was held down at all times. I took it to some shop and they told me it's most likely software and not hardware, and to try and flash a new ROM.
Now, I believe he was talking out of his ass. Rebooting the phone automatically puts it into fastboot because of the volume- button being broken. If it was a software issue this would not happen, I believe.
Whatever, I decided to try and flash a ROM just because maybe if I have root I will be able to block that button from working somehow.
The issue is, I can't boot into TWRP.
I unlocked the phone through Xiaomi and downloaded TWRP for Ginko. I did the `fastboot flash recovery twrp.img` thing and it works fine, but after that the command to reboot it to recovery `fastboot boot twrp.img` does not work. The fastboot image goes black for .1s then it shows the fastboot image again. Nothing happens. If I run the command again it takes a few seconds shoing "booting..." then the phone reboots to SYSTEM and an error shows on the CMD saying "FAILED (status read failed (Too many links))".
The only way I've found to boot to recovery is by using `adb reboot recovery` but that needs me to boot into system, which means TWRP is erased and the default recovery comes up.
If I reboot the phone the only way to go into system is by holding volume+, as it seems to counter the broken volume- button... But that means I can't boot to recovery, no matter how many times I try.
So I have no idea what to do.
Click to expand...
Click to collapse
Did you also try to flash recovery as you did before but right after that booting directly into recovery using hw buttons (vol- and pwr button till boot splash appears) from fastboot?
AckmanDESU said:
The only way I've found to boot to recovery is by using `adb reboot recovery` but that needs me to boot into system, which means TWRP is erased and the default recovery comes up.
Click to expand...
Click to collapse
to prevent twrp to be erased flash vbmeta (attached) using :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
i suggest you use OrangeFox and enable "aggresive stock recovery deactivation" in settings
This is a hardware problem and it's better to replace it
you can disable that button (while on Android) using xposed edge by setting "none" to click and long clic (need root + lsposed or edxposed)