Hey community,
I have been running Poco F1 with twrp and PixelExperience for the last 2 years. Considering the past record of the OS and my experience with the OS, I decided recently to upgrade to the newer PE12 for Poco F1 (maintained by Lakshay Garg). It went smooth initially and after the last OTA update, the phone started behaving weirdly.
Long story short,
This morning the phone went into an automatic restart and is now stuck in a boot loop. It boots and reaches the "G" logo and reboots. However, the weird part is,
Code:
fastboot flash
and
Code:
fastboot boot
are not available, throwing errors. The device is visible in
Code:
adb devices
and
Code:
fastboot devices
. This problem occurs when the phone is not plugged in. Once plugged in, the phone runs fine and everything just works. TWRP is not accessible, as if it is not there anymore and the only recovery that I can reach is the pixel recovery which has no option to flash any custom recovery (newbie, so not sure if something like this should exists or not).
I've tried various threads here and wasn't able to find any solution. Let me know what commands/outputs you guys might need from the device to help me in this.
Thanks in advance. Hope this gets fixed soon.
tysonX5653 said:
Hey community,
I have been running Poco F1 with twrp and PixelExperience for the last 2 years. Considering the past record of the OS and my experience with the OS, I decided recently to upgrade to the newer PE12 for Poco F1 (maintained by Lakshay Garg). It went smooth initially and after the last OTA update, the phone started behaving weirdly.
Long story short,
This morning the phone went into an automatic restart and is now stuck in a boot loop. It boots and reaches the "G" logo and reboots. However, the weird part is,
Code:
fastboot flash
and
Code:
fastboot boot
are not available, throwing errors. The device is visible in
Code:
adb devices
and
Code:
fastboot devices
. This problem occurs when the phone is not plugged in. Once plugged in, the phone runs fine and everything just works. TWRP is not accessible, as if it is not there anymore and the only recovery that I can reach is the pixel recovery which has no option to flash any custom recovery (newbie, so not sure if something like this should exists or not).
I've tried various threads here and wasn't able to find any solution. Let me know what commands/outputs you guys might need from the device to help me in this.
Thanks in advance. Hope this gets fixed soon.
Click to expand...
Click to collapse
Seems to be a battery problem. How old is it? You may need to replace it.
However make sure you followed the clean install method before you come on a conclusion. Also try to not use any Magisk modules.
Best Clean Install method:
Backup all your data. All your data into Internal Storage will be lost during this process.
Download latest Official TWRP Recovery, Pixel Experience build.
Create one Folder and move all the files you downloaded there.
Reboot to Fastboot Mode
Connect your device to PC and Boot into to TWRP via ADB or Minimal ADB and Fastboot:
Code:
fastboot boot <recovery_filename>.img
Example:
Code:
fastboot boot C:\Users\Retrial\Desktop\twrp-3.6.1_9-0-beryllium.img
Select Wipe > Advanced Wipe -> Select Dalvik / ART Cache, System, Data, Internal Storage, Vendor, Cache and then Swipe to Wipe.
Go back and select Wipe > Format Data > type yes
While you are in TWRP, transfer the Folder with the files you downloaded above.
Flash Pixel Experience ROM.
Flashing the ROM will replace TWRP with PE Recovery so OTA updates can be installed without problems since TWRP currently doesn't support decryption on A12 encypted ROMs - If you need in future to change ROM just fastboot boot to twrp via adb and flash img of twrp to recovery partition.
Done! Reboot to system.
Thanks, turns out that it was a battery problem after all. After battery replacement everything is working just fine. I also installed Awaken OS as Pixel Experience was removing the TWRP recovery each time I flashed it. Now as for my fastboot, initially it was not working; it was showing this error whenever I tried to flash TWRP recovery or any stock recovery:
Sending 'boot.img' (38640 KB) FAILED (Write to device failed (Cannot send after transport endpoint shutdown)) fastboot: error: Command failed
After this, the fastboot mode was diconnected and my phone was showing this Error:
Press any Key to Shut Down
It was resolved by running this bat file (as admin) :
https://bit.ly/31T2LcB
After running this file, there was no error and I was able to flash the twrp Recovery smoothly. So thanks for all the help really appreciate it.
tysonX5653 said:
Thanks, turns out that it was a battery problem after all. After battery replacement everything is working just fine. I also installed Awaken OS as Pixel Experience was removing the TWRP recovery each time I flashed it. Now as for my fastboot, initially it was not working; it was showing this error whenever I tried to flash TWRP recovery or any stock recovery:
Sending 'boot.img' (38640 KB) FAILED (Write to device failed (Cannot send after transport endpoint shutdown)) fastboot: error: Command failed
After this, the fastboot mode was diconnected and my phone was showing this Error:
Press any Key to Shut Down
It was resolved by running this bat file (as admin) :
https://bit.ly/31T2LcB
After running this file, there was no error and I was able to flash the twrp Recovery smoothly. So thanks for all the help really appreciate it.
Click to expand...
Click to collapse
Did you face the problem again?
I am using PE11 since last 2 years but suddenly i started facing the same problem. When plugged in, works fine. When I unplug it, works until screen is on and when I use power button to lock or unlock, phone goes into bootloop. I opend it in twrp where it can work as long as battery lasts, that's why I am not sure if it's a battery problem or something else
Related
Hello, XDA-Members,
long story short, I tried to flash CM-13 on my Honor 5X(KIW-L21 B340). Well, that didn't work and the phone always booted into TWRP. So I flashed FlymeOS because I couldn't flash the stock rom anymore(No matter why.).
It worked perfectly, and I were able to use my phone. After restarting my phone it booted back into TWRP, tried to wipe and all that stuff and even re-flashed Flyme OS, but still booted into TWRP. I was so UPSET that I deciced to flash the original RECOVERY.img for my Honor 5X. Well and from there I made it worse.
Windows and Linux don't recognize my phone. Windows just shows an empty E:\ drive. Reinstalled Google USB drivers, reinstalled driver etc. Didn't work. Now, when I start my phone it boots into the honor 5x recovery. I got these options available:
- Reboot system now
- Wipe data/factory reset
- Wipe cache partition
So, well. I can't install a rom anymore. As well when trying to connect my phone to ADB it won't work either. ADB doesn't recognize my phone. I made a big bull****, tbh. Installed HI-Care as well, but it doesn't get recognized either. I can also boot into Huawei eRecovery, connect to my wifi because it says it can download the stock rom. Guess what, it always said failed so I'm not able to do this either.
I'm really stuck. Anybody got an idea? Thanks in advance!
dunios said:
Hello, XDA-Members,
long story short, I tried to flash CM-13 on my Honor 5X(KIW-L21 B340). Well, that didn't work and the phone always booted into TWRP. So I flashed FlymeOS because I couldn't flash the stock rom anymore(No matter why.).
It worked perfectly, and I were able to use my phone. After restarting my phone it booted back into TWRP, tried to wipe and all that stuff and even re-flashed Flyme OS, but still booted into TWRP. I was so UPSET that I deciced to flash the original RECOVERY.img for my Honor 5X. Well and from there I made it worse.
Windows and Linux don't recognize my phone. Windows just shows an empty E:\ drive. Reinstalled Google USB drivers, reinstalled driver etc. Didn't work. Now, when I start my phone it boots into the honor 5x recovery. I got these options available:
- Reboot system now
- Wipe data/factory reset
- Wipe cache partition
So, well. I can't install a rom anymore. As well when trying to connect my phone to ADB it won't work either. ADB doesn't recognize my phone. I made a big bull****, tbh. Installed HI-Care as well, but it doesn't get recognized either. I can also boot into Huawei eRecovery, connect to my wifi because it says it can download the stock rom. Guess what, it always said failed so I'm not able to do this either.
I'm really stuck. Anybody got an idea? Thanks in advance!
Click to expand...
Click to collapse
Shut down the phone
plug the phone into your windows PC
hold volume down + power to enter the bootloader
from windows open the command prompt - type fastboot devices hit enter (your phone serial number will display)
type fastboot flash recovery TWRP.img (be sure to use this TWRP and it's named TWRP.img and in the same folder as fastboot)
after the file is flashed successfully hold power + volume up + volume down
after 5 seconds let go of power and continue to hold the volume buttons until TWRP boots
From TWRP you can now copy the CM13.zip and Gapps.zip to your phone and wipe/factory reset - then install them one by one
be sure their are no errors .. if you see errors choose reboot recovery and try the flash again until it succeeds.
first boot of cm13 will take some time, be patient
Thanks,
I recovered my phone. Awesome!
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
DOWNLOAD
TWRP 3.2.3.0
Flashing Instructions
Make sure you have fastboot drivers installed and your bootloader is unlocked
Download the file
In fastboot open the directory of downloaded file and type
fastboot flash recovery recovery.img, after that type
fastboot oem reboot-recovery, You'll have a black screen on your display wait for 5-10s you'll be greeted with TWRP screen if you still didn't get the screen then press power button 2-3 times
BUGS
Data decryption ( For this you need to select Wipe -> format data (You'll lose all your data in this process) )
No Battery% ( I purposefully disabled it as the battery% always stays at 50% so I'll find the battery% path and fix this in the next build)
Flash force encrypt disabler in recovery to fix magisk module installation and other data partition related issues.
Source Code: TWRP source, Device Tree and Kernel Source
Tried to install recovery twrp v 3.3.0 and 3.2.3, stuck in bootloop flashing recovery is successful but while rebooting its continues in loop after showing lenovo sign (Orange Mode), started due to reboot problem, oem unlock was successful as well, please help
pankajyadav_18 said:
Tried to install recovery twrp v 3.3.0 and 3.2.3, stuck in bootloop flashing recovery is successful but while rebooting its continues in loop after showing lenovo sign (Orange Mode), started due to reboot problem, oem unlock was successful as well, please help
Click to expand...
Click to collapse
By reboot problem if you mean, the phone getting restarted randomly in loop then the only way to fix it is to go to the service center.
Please help, I've been trying to do this for a while now. Excuse me if i'm being dumb, I am new to the rooting scene.
So long ago, a few weeks after buying my phone, I tried to root it. Idk if the info in this paragraph is important, but somehow the wifi stopped working in the magisk boot.img and even the stock boot.img and whatever I tried it would not work and after lots of time I was able to get a custom ROM working on it and wifi worked and I got android 10. Win win! And i later updated it without issue too.
The problems start when i found out there was another update to my ROM (Pixel Experience) and for some reason updating it in the android update menu doesn't work, it downloads fine but won't install. So I go to do it in my recovery of choice (OrangeFox, I tried TWRP during this and couldn't get it to work) and it won't boot. I must have flashed it and reflashed it different ways like 50 times and asked a friend how to do it and I could not get it to boot to an OS, I even tried another ROM and a fastboot only ROM. At this point I give up, leave the phone for like 10 days. I was missing my phone a lot so I decided to give it another go yesterday. Now when I try to flash OrangeFox (I have to run fastboot commands like setting the active slot and erasing boot partition) all the fastboot commands that used to work now give me some sort of error! It's usually something like:
Code:
Erasing 'boot' FAILED (remote: 'unknown command')
fastboot: error: Command failed
And also the device randomly goes on and off and I know for sure this USB port works but the phone sometimes appears in fastboot devices and sometimes it just goes away for no reason. I'm using Linux if it matters.
Sorry if I'm doing something dumb again or didn't give some info
There are a number of generic installation guides for custom roms eg https://www.xda-developers.com/how-to-install-custom-rom-android/
However this one is specifically for the LG G6 and tested using the US997 model. It worked for me, but I welcome comments on how to improve it.
Create a folder on the PC for all the downloads and files
Download phone driver from LG website
https://www.lg.com/us/support/help-library/lg-mobile-drivers-and-software-CT10000027-20150179827560
Download ADB/Fastboot https://developer.android.com/studio/releases/platform-tools (You need to unzip once downloaded)
(I had an error "adb server version (31) doesn't match this client (41) killing". I searched my PC and found an older version which I had used for another phone and deleted the folders and reinstalled from the download)
Ensure the phone is backing up. (Google backup is working, you have all your photos music etc downloaded) the next steps will wipe the phone
Remove the PIN/Password/Fingerprints from the phone so it will boot without any security.
Unlock the bootloader
https://developer.lge.com/resource/mobile/RetrieveBootloader.dev
The phone will then reboot and do a complete wipe so you need to wait a while for Android to setup.
Telegraph has the latest news on LG G6 ROMs and Recovery. From here I got the links for SHRP recovery which seems more up to date for LG G6 than TWRP. (https://web.telegram.org/#/[email protected])
https://sourceforge.net/projects/pa-g6/files/Releases/SHRP/20.07.2020/US997/
I named the downloaded file "recovery" (You need the .img file not the ZIP)
There are lots of active ROMS for LG G6 I have Lineage installed on another phone which works really well, but Havoc seems the most popular on the G6.
Download the ROM and Gapps https://opengapps.org/ (I used Nano, remember G6 is 64bit)
You will also need to update the bootloader. This was the latest I found for the US997
https://androidfilehost.com/?fid=1899786940962575226
(I missed the bootloader the first time and Gapps will not flash, I was helped by the LG G6 community on Telegram https://web.telegram.org/#/[email protected])
Now you have downloaded all you need
Then connect the phone to the PC and ensured you have ADB debug on in developer options and boot the phone into fastboot
On the PC open a command prompt in the folder you have all the files:
adb reboot bootloader
To load the recovery to the phone :
Fastboot flash recovery recovery.img
YOU MUST NOW BOOT DIRECTLY TO RECOVERY. Do not reboot to Android as this will automatically reset recovery to the stock version.
Unplug the USB cable and reboot to recovery (hold volume down + power button).. continue holding until phone reboots...
As soon as you see the LG logo on the screen.. let go of the power button then quickly press it again (never letting go of volume down).
Keep holding until you see the Factory Reset screen. Click thru the factory reset screens using the volume buttons to move up/down and power button to select. Choose "Yes" twice (saying you want to reset the phone it should boot into your new recovery. Despite what the screen says it won't actually factory reset/wipe your data... as long as you've installed a custom recovery and have not booted into Android since then.
Most likely you will be asked the password to decrypt the data folder. I tried my phone PIN and other default passwords suggested on the internet. I eventually found that this is a known issue and you need for cancel out of this screen and go and "FORMAT DATA"
Reboot directly to recovery (select reboot recovery in Skyhawk), this time you should not be asked for the decryption password.
I recommend you backup your current setup before making changes. If you hit issues you can use the recovery to restore. My SD card slot is broken (Poor LG design) so I plugged a USB thumb drive into the USB C slot and did a full backup. (No data since I just formatted it).
Wipe the partitions before you flash
Full wipe ("The only option you ever need")
Select Advanced and wipe system partition.
FLASH (You need to put the ZIP files either on the USB drive as I did, or copy to your SD card, or you can use ADB sideloader from the PC to push the files to the phone). The USB drive seems the easiest since you can plug it into your PC to load the files then plug it into the phone to read them.
Flash in the following order
Bootloader
ROM
Gapps
After Installing wipe cache and Davik
Reboot
It will do lots of processing while setting up. Ensure it stays cool (remove case and leave it plugged in with the screen off)
Donate to the developer of your new ROM at the end when it works.
I have been running my LG G6 on Android 10 for a few weeks and thought I would share my observations, I am using Havoc 3.7 installed with Skyhawk, I did not root the phone.
Likes : Very smooth experience, phone feel like it is running much faster. Very stable, I had one surprise reboot in the time I have used it. No issues (so far) with installing or using any apps including banking. Much lower use of storage, I have 6GB free.
Same : Battery life is about the same as before.
Gaps : Cannot encrypt, VOLTE doesn't work (which may become a big issue for T-Mobile and AT&T soon), when being used the phone gets much warmer than it did before and the wifi setting randomly turns off.
Next Steps: I am going to try Lineage which has released some fixes for the WIFI issue and report back.
I'm trying to follow the instructions as per this guide for the tmo version of G6 (H87220g) and I'm running into a roadblock on the recovery flash:
[[email protected] tmp]$ mkdir skyhawk
[[email protected] tmp]$ cd skyhawk && 7z x ../SHRP_v2.3.2_us997-233920072020.zip
[[email protected] skyhawk]$ fastboot flash recovery recovery.img
Sending 'recovery' (36936 KB) OKAY [ 1.252s]
Writing 'recovery' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
I downloaded the Skyhawk zip from the PA download link, unzipped it and used the recovery.img file found inside the zip as part of the fastboot command. Is this incorrect ?
Yes, you need the recovery.img file to flash via fastboot. Have you successfully unlocked the boot loader? You cannot replace recovery without unlocking.
You also need to ensure you have the appropriate files for your phone I have a US997 but as you have H872 you would need skyhawk for the H872 in the notes above you are still using US997.
bootloader is unlocked as per:
https://forum.xda-developers.com/tmobile-g6/how-to/unlock-bootloader-tmo-t3578099
fastboot flash is failing and I'm not the only one it seems like based on comments here and reddit...
I gonna try out @runningnak3d guide and see if that works...
This guide is for the US997. The H872 has a much more complicated process to install recovery : https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518
Hi, I have a semibrick on my X3 Superzoom (Global), and I can't seem to restore the original firmware. When it was working properly, I think the phone was updated to the latest version available in Europe (RMX2081EU_11.A.50), hence Realme UI 1.0.
I do not remember very well what I did, it's been a few weeks since my "screw up", I must have flashed an untrusted firmware, the thing is that when rebooting the screen looks black and goes into a continuous bootloop, but allows to enter fastboot mode with power + Vol down (I know because I can launch fastboot commands). Curiously, when it goes into bootloop you don't see the Realme logo, I discovered that the logo is there but with the screen illumination at minimum, and you can only glimpse a little if you put it under a lamp. Very strange.
Since it can go into fastboot mode I have tried flashing several firmwares for my phone, RMX2086 and none of them repair brik. I have tried always by command line because with MsmDownloadTool I don't have login access and with Realme Flash Tool always shows error "cannot find central directory", I have tried also with QFil and I can't get it to stay stable on the port.
I flash with command line with "fastboot flash" all .img files of super, recovery, boot, boot, dtbo, vbmeta (in that order) but it does nothing. Furthermore, I have tried with several ofp files like for example the following file from realmefirmware.com, which seems to be the last released full version of Realme UI 2.0 (I have tried also with Realme UI 1.0 versions):
RMX2086GDPR_11_C.11_2022011318270168.zip (I decrypt the ofp file inside to extract the .img files.).
Interestingly, I can flash TWRP Recovery (it works, and you see the screen with normal TWRP recovery) and from the recovery I can flash a Custom Recovery like PixelPlusUI. The phone boots (no logo visible) in CustomROM normally, but after a while of use the screen turns off but working ROM.
What should I do? Although I have some flashing experience, I'm pretty much stuck. Can anyone give me any suggestions?
Sorry with making it so long, but I wanted to explain this as best as possible so it is well understood.
When you already upgrades to Android 11, you can not flash custom rom, otherwise it bricks, because all the custom roms required android 10 ROM system, you may downgrade using flash tool (I tried but failed to flash any stock rom using any tool, only able to flash using fastboot commands)
bernarbernuli said:
Hi, I have a semibrick on my X3 Superzoom (Global), and I can't seem to restore the original firmware. When it was working properly, I think the phone was updated to the latest version available in Europe (RMX2081EU_11.A.50), hence Realme UI 1.0.
I do not remember very well what I did, it's been a few weeks since my "screw up", I must have flashed an untrusted firmware, the thing is that when rebooting the screen looks black and goes into a continuous bootloop, but allows to enter fastboot mode with power + Vol down (I know because I can launch fastboot commands). Curiously, when it goes into bootloop you don't see the Realme logo, I discovered that the logo is there but with the screen illumination at minimum, and you can only glimpse a little if you put it under a lamp. Very strange.
Since it can go into fastboot mode I have tried flashing several firmwares for my phone, RMX2086 and none of them repair brik. I have tried always by command line because with MsmDownloadTool I don't have login access and with Realme Flash Tool always shows error "cannot find central directory", I have tried also with QFil and I can't get it to stay stable on the port.
I flash with command line with "fastboot flash" all .img files of super, recovery, boot, boot, dtbo, vbmeta (in that order) but it does nothing. Furthermore, I have tried with several ofp files like for example the following file from realmefirmware.com, which seems to be the last released full version of Realme UI 2.0 (I have tried also with Realme UI 1.0 versions):
RMX2086GDPR_11_C.11_2022011318270168.zip (I decrypt the ofp file inside to extract the .img files.).
Interestingly, I can flash TWRP Recovery (it works, and you see the screen with normal TWRP recovery) and from the recovery I can flash a Custom Recovery like PixelPlusUI. The phone boots (no logo visible) in CustomROM normally, but after a while of use the screen turns off but working ROM.
What should I do? Although I have some flashing experience, I'm pretty much stuck. Can anyone give me any suggestions?
Sorry with making it so long, but I wanted to explain this as best as possible so it is well understood.
Click to expand...
Click to collapse
Have you found solution? I have exactly the same problem!
maskalicz said:
Have you found solution? I have exactly the same problem!
Click to expand...
Click to collapse
It's been over a year since it happened, I didn't find a solution on my own, and since it was still under warranty, I sent it to the official technical service and a couple of weeks later I received it back with the firmware working.