Guys, I installed the ROM Pixel Experience. This one:
https://forum.xda-developers.com/mi-pad-4/development/rom-pixelexperience-t3878616
I am having a huge issue with this rom. I installed it and it works fine, however, since it doesn't support USB, I decided to install the MIUI stock rom back. Well, in order to do that, you have to have the device in FASTBOOT mode.
When I go to the prompt and type fastboot devices, I get a result, showing that my computer can detect the device.
However, every time I am in FASTBOOT mode, after 30 seconds (exactly!) it reboots. So, I am afraid to start flashing it and then the device reboots and my installation gets corrupted.
Any ideas on how to solve this? I just need the FASTBOOT mode to last as long as necessary for me to install the older room back.
Can you explain what you mean by "Doesnt support USB"?
And the fastboot issue is definitely weird. That should not be happening. Does this happen when the device is plugged in only? What happens if the device is not plugged to the computer?
Related
This is my very first time trying to flash a phone.
So far I have:
installed ADB on PC
unlocked the bootloader
downloaded a 1.17GB rom so that I could extract the 5mb boot.img
patched the boot.img using magisk
run "fastboot flash boot magisk_patched.img"
fastboot reboot
The phone never came-up after the reboot. Nothing on screen at all but because it was still connected to the PC I can hear beeping sounds through the PC every so often, like it does when you connect or disconnect a phone.
It seems like it is continually rebooting. I suspect it will continue to do that if I unplug it, until the battery dies.
I have no way to stop it and the hardware buttons in any combination don't seem to do anything. The battery is non-removable.
I'd really, really appreciate some patient assistance here please guys!
Re-flash phone's Stock ROM
Device is not detected by ADB. Is there another way?
Don't know of any.
Maybe u flashed x930.
i managed to delete twrp and when i did then it shows that the system has been destroyed and after restart it is stuck on
fastboot windows. i tried to connect it with my pc so i could install flash rom but it doesnt show up on pc after connecting to usb.
i dont understand what to do next... helppppppppppppppppppppppppp
I have been in this situation before but I'm not sure how exactly i got into it but I was also doing something to do with twrp. Anyway, whenever you encounter such a problem you need to provide as much information as you possibly can to help us help you. This way people are able to narrow down to what causes a particular problem. One question I have is how did you "delete" twrp?
Now for how I got out of that "system has been destroyed" problem. First off, I had already successfully unlocked my bootloader (don't know if you had). Also, the adb drivers were properly installed on my pc. What I did (at the "system has been destroyed" screen) was to let it sit there while connected to the charger for what seemed to be around 10 minutes and kept doing what I was doing and out of the corner of my eye I saw it rebooting and unexpectedly it went into fastboot. I connected it to my pc and it showed up in device manager and "fastboot devices" command detected it. I proceeded to successfully flash recovery with fastboot and then used "fastboot boot recovery.img (or whatever you have renamed your recovery to)" command. It went into recovery mode after which I copied rom via mtp and flashed it and it agreed to boot into system after the flashing was successful.
These may not be the exact steps I took but as close to them as I can recall (because I was bewildered at the thought that my phone was dead). I think the key turning point was to let it sit at the "system has been destroyed" screen for a while.
twistyplain said:
I have been in this situation before but I'm not sure how exactly i got into it but I was also doing something to do with twrp. Anyway, whenever you encounter such a problem you need to provide as much information as you possibly can to help us help you. This way people are able to narrow down to what causes a particular problem. One question I have is how did you "delete" twrp?
Now for how I got out of that "system has been destroyed" problem. First off, I had already successfully unlocked my bootloader (don't know if you had). Also, the adb drivers were properly installed on my pc. What I did (at the "system has been destroyed" screen) was to let it sit there while connected to the charger for what seemed to be around 10 minutes and kept doing what I was doing and out of the corner of my eye I saw it rebooting and unexpectedly it went into fastboot. I connected it to my pc and it showed up in device manager and "fastboot devices" command detected it. I proceeded to successfully flash recovery with fastboot and then used "fastboot boot recovery.img (or whatever you have renamed your recovery to)" command. It went into recovery mode after which I copied rom via mtp and flashed it and it agreed to boot into system after the flashing was successful.
These may not be the exact steps I took but as close to them as I can recall (because I was bewildered at the thought that my phone was dead). I think the key turning point was to let it sit at the "system has been destroyed" screen for a while.
Click to expand...
Click to collapse
Hey thanks for replying to be honest ..i thought people will help but seems like nobody cares here..
The thing is i dont remember actually exact process but i somehow managed to delete the twrp ..
the main problem is you said after ur phone got onto fastboot you connected it to ur pc and flashed official rom but in my case in the device manger or anywhere ... when my phone is in fastboot mode and i connect it to my pc it doesnt show up as connected not in device manager or any other place...this is the main problem....if only my device shows up connected i wouldve flashed rom way before anything...its been 1 week since my phone died ...i need help...i tried everything from youtube ...seems it doesnt work for me
AjTheKiller1 said:
Hey thanks for replying to be honest ..i thought people will help but seems like nobody cares here..
The thing is i dont remember actually exact process but i somehow managed to delete the twrp ..
the main problem is you said after ur phone got onto fastboot you connected it to ur pc and flashed official rom but in my case in the device manger or anywhere ... when my phone is in fastboot mode and i connect it to my pc it doesnt show up as connected not in device manager or any other place...this is the main problem....if only my device shows up connected i wouldve flashed rom way before anything...its been 1 week since my phone died ...i need help...i tried everything from youtube ...seems it doesnt work for me
Click to expand...
Click to collapse
Have you ever had your phone detected by your pc in fastboot mode? And if you connect it to the pc, does the computer play the hardware detected sound?
You need to rule out a driver issue. I'm not the only other person to get the "system has been destroyed" message and people usually get out of it. I don't know why yours is so problematic.
Had you successfully unlocked bootloader?
The Good old "System has been destroyed" Message. Well, This is terrible This should not happen in the first place. I assume it happened Because you wiped data and then deleted twrp. But If you want help you have to specify how exactly did you " Delete TWRP" What steps did you follow to Delete it. None the less the best bet on getting your device back would be to go to the nearest service center. Pretend you did nothing and maybe they will say you got a bad update.
Still very new to the community, so please bear with me if I miss something or make any mistakes.
Trying to flash havocOS
I flashed an unofficial version of twrp (for X657, made sure to disable verity on both vbmeta and vbmeta_system), then attempted to boot into twrp, with no luck (it just ended up booting into fastboot for some reason).
I then tried to boot into fastbootd, completely forgetting i had twrp still installed, to flash havoc from there (this is where i think i messed up, i remember reading somewhere that twrp prevents this)
Now my phone is stuck looping on the infinix logo
Tried the SP Flash Tool, but kept getting this error. Which I'm guessing is because the phone keeps restarting (mainly because "Disconnected!" shows up in the console between two instances of the same error).
Any advice?
UnequalB said:
Still very new to the community, so please bear with me if I miss something or make any mistakes.
Trying to flash havocOS
I flashed an unofficial version of twrp (for X657, made sure to disable verity on both vbmeta and vbmeta_system), then attempted to boot into twrp, with no luck (it just ended up booting into fastboot for some reason).
Click to expand...
Click to collapse
Probably you haven´t to flash vbmeta to boot to TWRP but just when you are ready to boot to system.
UnequalB said:
I then tried to boot into fastbootd, completely forgetting i had twrp still installed, to flash havoc from there (this is where i think i messed up, i remember reading somewhere that twrp prevents this)
Click to expand...
Click to collapse
You can flash the TWRP image through fastboot and then boot to it through commands.
UnequalB said:
Now my phone is stuck looping on the infinix logo
Tried the SP Flash Tool, but kept getting this error. Which I'm guessing is because the phone keeps restarting (mainly because "Disconnected!" shows up in the console between two instances of the same error).
Any advice?
Click to expand...
Click to collapse
This is the list of errors from SP Flash tool https://forum.hovatek.com/thread-439.html
Anyway, you have a tool specific for your device https://forum.hovatek.com/thread-9224.html
I guess this thread must be moved to Android General Questions.
SubwayChamp said:
Probably you haven´t to flash vbmeta to boot to TWRP but just when you are ready to boot to system.
You can flash the TWRP image through fastboot and then boot to it through commands.
Click to expand...
Click to collapse
I meant twrp prevents booting to fastbootd, it was after trying to boot into fastbootd using "fastboot reboot fastboot" that the bootloop started, right now I can't seem to get past the boot logo.
SubwayChamp said:
This is the list of errors from SP Flash tool https://forum.hovatek.com/thread-439.html
Click to expand...
Click to collapse
Weirdly enough the error i got was not listed here..
SubwayChamp said:
Anyway, you have a tool specific for your device https://forum.hovatek.com/thread-9224.html
I guess this thread must be moved to Android General Questions.
Click to expand...
Click to collapse
This method doesn't work either since the phone won't stay off for more than 7 seconds.
I'm not stuck in a bootloop as in the phone powers on, then gets stuck, or powers off again
The phone continuously powers on and off and nothing I do (apart from disconnecting the battery) stops it, even then, once the battery is back in it begins looping again...
UnequalB said:
I meant twrp prevents booting to fastbootd, it was after trying to boot into fastbootd using "fastboot reboot fastboot" that the bootloop started, right now I can't seem to get past the boot logo.
Click to expand...
Click to collapse
You don't need to reboot to fastbootd, and you can't apply ADB commands either, because your device doesn't allow it due to random reboots and due to USB debugging is disabled right now.
UnequalB said:
Weirdly enough the error i got was not listed here..
This method doesn't work either since the phone won't stay off for more than 7 seconds.
Click to expand...
Click to collapse
Not true, this is the whole idea of this kind of tools either through SP Flash tool or Infinix tool you just have to GET device can be detected, this tiny portion of time will be enough for the tools can start its job, once the tool started the device get attached without a way to get out of it. To achieve this, prepare ALL that you need for tool to work even press flash/download, connect device with PC and apply the right combination key,
Prepare device manager on Windows and check which status of connection it is passing through to better understand which mode is lacking of.
UnequalB said:
I'm not stuck in a bootloop as in the phone powers on, then gets stuck, or powers off again
The phone continuously powers on and off and nothing I do (apart from disconnecting the battery) stops it, even then, once the battery is back in it begins looping again...
Click to expand...
Click to collapse
You are not saying till now which model your device is, assuming that the bootloader is unlocked.
SubwayChamp said:
You don't need to reboot to fastbootd, and you can't apply ADB commands either, because your device doesn't allow it due to random reboots and due to USB debugging is disabled right now.
Not true, this is the whole idea of this kind of tools either through SP Flash tool or Infinix tool you just have to GET device can be detected, this tiny portion of time will be enough for the tools can start its job, once the tool started the device get attached without a way to get out of it. To achieve this, prepare ALL that you need for tool to work even press flash/download, connect device with PC and apply the right combination key,
Prepare device manager on Windows and check which status of connection it is passing through to better understand which mode is lacking of.
You are not saying till now which model your device is, assuming that the bootloader is unlocked.
Click to expand...
Click to collapse
I tried again and that error seems to just be an issue with the linux version, it detected the phone fine and started writing to "super" on windows, but my laptop died, and now the phone isn't showing up on SP Flash, neither would it turn on at all.. but the charging indicator light comes on when I plug it in.
UnequalB said:
I tried again and that error seems to just be an issue with the linux version, it detected the phone fine and started writing to "super" on windows, but my laptop died, and now the phone isn't showing up on SP Flash, neither would it turn on at all.. but the charging indicator light comes on when I plug it in.
Click to expand...
Click to collapse
Well, if you interrupted the process, that's not good at all. The only you can do is keeping trying it, if your motherboard was not damaged.
hi guys i am DELTIERO from the Philippines did you allready solve the problem?
If not yet done message me on my facebook page https://www.facebook.com/del.villalobos.1/
and i will help you im here veltech san carlos negross occidental phil
Help please! I flashed a gapps zip file using flashify on my infinix smart 5 x657 (Running on lineageos gsi android 12) then the phone just went off. and it not turning on. but it shows the charging indicator light when i connect it to power.
I've tried disconnecting the battery still nothing
what possible solution is there for this?
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
Hello, i want to share my experience because it may me useful for others. I have also a question for you at the end of the story.
I rooted my MI A3 with magisk but without twrp back in 2019 following the guide posted on this forum. The phone had android 9 and I never did software updates. Once in a while a messagge appeared on the screen saying that my software was obsolete and that I needed to update but I always managed to dodge it.
Some days ago my phone started behaving strangly (eg: I turned the volume down to zero but it turned up by itself) so I decided to reboot it. Something went wrong and the phone rebooted in fastboot mode. I tried many things but the phone was only able to boot in fastboot mode.
I thought that maybe the problem was related to the software update that sometimes was popping on the screen. So, i connected the phone to my pc and executed some fastboot commands:
fastboot getvar current-slot (to know which partition was in use. It was B)
fastboot set_active A (to switch to the other partition)
fastboot reboot
The phone rebooted correctly but it was on android 10 (before the problem it was on android 9) and without root. Everything seemed working fine and all the data was safe (only one thing changed, the boot process require much more time now). So, I realized that the phone applied the system update by itself (without my consent).
Now my question. The phone works well for the moment but how can i check the status of the partition B? I suspect that it may be damaged.
Furthermore I would like to flash the stock firmware, clear all the data and unroot the phone. Can I proceed? Should I flash both partitions?
Thanks
Any suggestions?