Related
My Friend has an Unlocked XT1022... Now suddenly something happened and when I try to boot My device it boots into TWRP (always) and TWRP loading screen keeps flashing for every 2 seconds... I am able to fastboot and I also tried to flash TWRP in fastboot mode again but still it is the same... HELP ME PLEASE :crying: :crying: :crying:
bharathulaganathan said:
My Friend has an Unlocked XT1022... Now suddenly something happened and when I try to boot My device it boots into TWRP (always) and TWRP loading screen keeps flashing for every 2 seconds... I am able to fastboot and I also tried to flash TWRP in fastboot mode again but still it is the same... HELP ME PLEASE :crying: :crying: :crying:
Click to expand...
Click to collapse
Try flashing stock firmware including the recovery via fastboot.
Sent from my landline
moto e stuck in TWPR loop please help
update2 of today.
There is a small white button in the centre of the bottom of the TWRP screen, and when I press it, i get this gobbledygoook
E:storage partition ' /data/media/0/TWRP/BACKUPS/Z/X1B224KGZ' not found
Updating partition details. . .
Full SELinux support is present.
Processing AOSP recovery commands. .
.
installing zip file '/cache/Blur_Version.21.12.40.condor_retgb.rgtgb.en.gb.zip'
. . .
checking for MD5file. .
Skipping MD5 check: no MD5f file found.
Package expects build fingerprint of motorola/condor_umts:4.4.4/KXC21.5.40/46.user/release^keys.or.motorola/condor_retgb/condor_umts:5.1/LPC23.13.34.8/9:user/release.keys;this device has motorola/slim_condor/condor:4.4.2/KVT49L/eng.cybojenix.20140518.094536:eng/test^keys.
E:Error executing updater binary in zip '/cache/Blur_Version.21.12.40.condor_retgb.retgb.en.GB.zip'
done processing script file.
Click to expand...
Click to collapse
I dunno what that is, but I want to use my android phone and cannot access it.
Is my phone bricked?
I am not tech savvy but I rooted it successfully, following instructions, and today, the problem started when I downloaded android 5.0 on a phone that has been rooted.
Could anyone help me access my phone again, but in terminology that I understand?, that would be very helpful thank you.
bharathulaganathan said:
My Friend has an Unlocked XT1022... Now suddenly something happened and when I try to boot My device it boots into TWRP (always) and TWRP loading screen keeps flashing for every 2 seconds... I am able to fastboot and I also tried to flash TWRP in fastboot mode again but still it is the same... HELP ME PLEASE :crying: :crying: :crying:
Click to expand...
Click to collapse
flash other recovery try official one
Hello Guyz I Have J7Max And i Need A devloper For root recovery and Roms I AmReady to be a Tester
Try this out please:
TWRP 3.1.1-1 J7 max sm-g615f:
https://www.androidfilehost.com/?fid=673368273298981161
.
Is this recovery working ?
Rumorbox33 said:
Is this recovery working ?
Click to expand...
Click to collapse
Who knows, did you see anybody bother to reply?
ashyx said:
Try this out please:
TWRP 3.1.1-1 J7 max sm-g615f:
https://www.androidfilehost.com/?fid=673368273298981161
.
Click to expand...
Click to collapse
yes bro it is working
pardhav said:
yes bro it is working
Click to expand...
Click to collapse
Wow, 970 downloads and you are the ONLY one decent enough to reply!
Can you post the recovery log, so I can check it over.
Thanks for replying!
ashyx said:
Wow, 970 downloads and you are the ONLY one decent enough to reply!
Can you post the recovery log, so I can check it over.
Thanks for replying!
Click to expand...
Click to collapse
i did'nt try it on my own on of fellow members in the telegram grp stated it was working so i said it was working today i tested it on my own but i could boot into twrp odin says pass! status also custom but cannot boot into twrp the recovery logs which u asked ,i dont know the way how to get those from stock recovery ! tell me how to get those logs i would surely post them!
pardhav said:
i did'nt try it on my own on of fellow members in the telegram grp stated it was working so i said it was working today i tested it on my own but i could boot into twrp odin says pass! status also custom but cannot boot into twrp the recovery logs which u asked ,i dont know the way how to get those from stock recovery ! tell me how to get those logs i would surely post them!
Click to expand...
Click to collapse
What happens when you attempt to boot to twrp. Give details please.
ashyx said:
What happens when you attempt to boot to twrp. Give details please.
Click to expand...
Click to collapse
No command screen appears after sometime it boots into stock recovery
---------- Post added at 02:50 AM ---------- Previous post was at 02:31 AM ----------
pardhav said:
No command screen appears after sometime it boots into stock recovery
---------- Post added at 02:50 AM ---------- Previous post was at 02:31 AM ----------
Click to expand...
Click to collapse
You're booting to stock recovery.
You MUST disable auto reboot in Odin.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery
ashyx said:
You're booting to stock recovery.
You MUST disable auto reboot in Odin.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery
Click to expand...
Click to collapse
yeah bro got it !
booted into twrp successfully
initially /data is not mounted i need format my data to mount /data
the main one it gets stuck in bootloop tried flashing 3 tyms result gets stuck in bootloop
logs attached
pardhav said:
yeah bro got it !
booted into twrp successfully
initially /data is not mounted i need format my data to mount /data
the main one it gets stuck in bootloop tried flashing 3 tyms result gets stuck in bootloop
logs attached
Click to expand...
Click to collapse
Recovery log looks fine. When and how does it get stuck in a boot loop, can you explain in more detail?
ashyx said:
Recovery log looks fine. When and how does it get stuck in a boot loop, can you explain in more detail?
Click to expand...
Click to collapse
after exiting from the download mode
entering into twrp recovery (manually)
rebooting my device through twrp recovery
that"s it my device gets stuck in bootloop
pardhav said:
after exiting from the download mode
entering into twrp recovery (manually)
rebooting my device through twrp recovery
that"s it my device gets stuck in bootloop
Click to expand...
Click to collapse
Do you mean a recovery loop or boot loop and is this after installing supersu?
ashyx said:
Do you mean a recovery loop or boot loop and is this after installing supersu?
Click to expand...
Click to collapse
No bro it's a boot loop
I haven't flashed anything
Just booted into recovery then reboot - > system
Doing this gave bootloop
Then I tried flashing magisk and reboot it worked fine
pardhav said:
No bro it's a boot loop
I haven't flashed anything
Just booted into recovery then reboot - > system
Doing this gave bootloop
Then I tried flashing magisk and reboot it worked fine
Click to expand...
Click to collapse
Something isn't making sense here, this doesn't seem a twrp problem if you're saying installing Magisk solves the problem?
[/COLOR]
ashyx said:
Something isn't making sense here, this doesn't seem a twrp problem if you're saying installing Magisk solves the problem?
Click to expand...
Click to collapse
Yeah without flashing anything and rebooting gets me into bootloop
Flashing magisk worked perfectly
As u said after flashing boot into twrp I booted into twrp and reboot into system but my gets stuck in boot loop
So I tried formating data and reboot same result
Then I flashed magisk and then rebooted
It worked perfectly nd I'm using it without any problems
pardhav said:
[/COLOR]
Yeah without flashing anything and rebooting gets me into bootloop
Flashing magisk worked perfectly
As u said after flashing boot into twrp I booted into twrp and reboot into system but my gets stuck in boot loop
So I tried formating data and reboot same result
Then I flashed magisk and then rebooted
It worked perfectly nd I'm using it without any problems
Click to expand...
Click to collapse
Oddly it seems the bootloop is caused by the patch twrp does to prevent it being replaced by stock recovery and is possibly causing dmverity to kick in.
Magisk disables dmverity as does supersu and my boot patch for encryption.
ashyx said:
Oddly it seems the bootloop is caused by the patch twrp does to prevent it being replaced by stock recovery and is possibly causing dmverity to kick in.
Magisk disables dmverity as does supersu and my boot patch for encryption.
Click to expand...
Click to collapse
Yeah probably it would be the reason
---------- Post added at 04:12 AM ---------- Previous post was at 04:07 AM ----------
pardhav said:
Yeah probably it would be the reason
Click to expand...
Click to collapse
Bro why don't create a thread for your work
Because many people are facing the same issue I have faced
pardhav said:
Bro why don't create a thread for your work
Because many people are facing the same issue I have faced
Click to expand...
Click to collapse
Because nobody actually confirmed it working.
im on havoc os with sesh gaming kernel. while i never encountered any reboot before then this morning when i woke up my poco just keep rebooting. i can go into recovery but only for 3-5 second it reboot again, same thing happened in fastboot mode. help please.
Edit: problem solved after I go to repair shop. There's water inside my poco, after the repair all working fine. I don't even know how this happen maybe due to rain.
Try Flashing stock rom using miflash. It will only need a second to detect in fastboot mode And it will start the process. Hopefully it won't reboot during the process and if it does then the device may get bricked.
tejjoshii said:
Try Flashing stock rom using miflash. It will only need a second to detect in fastboot mode And it will start the process. Hopefully it won't reboot during the process and if it does then the device may get bricked.
Click to expand...
Click to collapse
yeah i do think that too but the reboot stopped me from doing it. i might go for it if it was the last option. thanks for your reply.
force it to twrp! or fastboot
power+volumUP or Power+vol DOWN and flash vendor/crdroid/ dont flash same kernel/ and reboot!
YasuHamed said:
force it to twrp! or fastboot
power+volumUP or Power+vol DOWN and flash vendor/crdroid/ dont flash same kernel/ and reboot!
Click to expand...
Click to collapse
Even if I forced my poco into twrp or fastboot it still reboot. But problem solved now. Thanks.
Irwan Fauzi said:
Even if I forced my poco into twrp or fastboot it still reboot. But problem solved now. Thanks.
Click to expand...
Click to collapse
please do share for knowledge base how and what exactly you did.
YasuHamed said:
please do share for knowledge base how and what exactly you did.
Click to expand...
Click to collapse
The problem is hardware not software. Like I said I don't know how my poco got water inside.
Hello !!! The phone is Realme XT bootloop and does not go into fastboot (((How can I restore the phone to work?thanks !!!
Aleksandr1980 said:
Hello !!! The phone is Realme XT bootloop and does not go into fastboot (((How can I restore the phone to work?thanks !!!
Click to expand...
Click to collapse
What've you done exactly?
amodeos said:
What've you done exactly?
Click to expand...
Click to collapse
Installed TWRP and flashed the stock firmware RMX1921EX_11_OTA_0130_all_FjPhN3YP2XVI.ozip
Aleksandr1980 said:
Hello !!! The phone is Realme XT bootloop and does not go into fastboot (((How can I restore the phone to work?thanks !!!
Click to expand...
Click to collapse
try this out might help
https://www.youtube.com/watch?v=yjtSteuPkI4
[
I can not go into recovery, a constant cyclic reboot
Aleksandr1980 said:
[
I can not go into recovery, a constant cyclic reboot
Click to expand...
Click to collapse
You have flashed , stock ROM that means on first boot twrp will be replaced by stock recovery unless you flashed VB meta zip to retain twrp.
You are from which region ? Coz realme released same phone in diff part of world with different internal partitions. If you flash wrong region ro m even though for same phone , it can break your phone. Check if you can go to service center.
anand28 said:
You have flashed , stock ROM that means on first boot twrp will be replaced by stock recovery unless you flashed VB meta zip to retain twrp.
You are from which region ? Coz realme released same phone in diff part of world with different internal partitions. If you flash wrong region ro m even though for same phone , it can break your phone. Check if you can go to service center.
Click to expand...
Click to collapse
Phone region Realme XT, if you flash firmware from Realme EUEX, then it will completely block, as I understand it, when flashing a different drain, the system board goes into defense and besides replacing it there is no way to restore the phone?
Aleksandr1980 said:
[
I can not go into recovery, a constant cyclic reboot
Click to expand...
Click to collapse
Try this, hold volume +, volume - and power button for about 13 Seconds. Hope this will you..
While holding all three buttons, the phone cyclically tries to enter fastboot.
Aleksandr1980 said:
While holding all three buttons, the phone cyclically tries to enter fastboot.
Click to expand...
Click to collapse
If that not helped you, I guess maybe u should go to service center
Aleksandr1980 said:
While holding all three buttons, the phone cyclically tries to enter fastboot.
Click to expand...
Click to collapse
@Aleksandr1980
do you have an XT??? what firmware was installd????? RMX1921EX_11_A.05?
and have you find a way to update the phone??
Shortys1988 said:
@Aleksandr1980
do you have an XT??? what firmware was installd????? RMX1921EX_11_A.05?
and have you find a way to update the phone??
Click to expand...
Click to collapse
We are at A15. Not sure how are still in A05
We updated through ota.
---------- Post added at 02:07 PM ---------- Previous post was at 02:04 PM ----------
If you are able to go in A05 ..then download A15 and store in your phone and use any file manager to install
When you have euex Then a05 is your Firmware, a15 will Not work
Gesendet von meinem RMX1921 mit Tapatalk
Thankyou, I had installed Android 10 pixel experience rom and eneded up in a boot loop. Now solved. Thanks
how did you resolve ? can you tell me please. i have the same problem
Realme XT in bootloop and only fastboot page is working.. i tried to flash twrp recovery, vb meta..all successfully completed on pc but recovery page not showing and when clicking on recovery it is going on bootloop..only fastboot page is working...please help me!!!
Aleksandr1980 said:
Installed TWRP and flashed the stock firmware RMX1921EX_11_OTA_0130_all_FjPhN3YP2XVI.ozip
Click to expand...
Click to collapse
Flash official stock rom fix your problem
Hi! I was on the February update and was trying to update to the March update using the factory images.
While updating I was faced with sparse file too big or invalid error. Then my device was stuck at bootloader. After that, I proceeded to stupidly change my active partition from b to a. Now my device won't boot at all. Is there any way I can recover from this? Or is there a chance at all?
Xeust said:
Hi! I was on the February update and was trying to update to the March update using the factory images.
While updating I was faced with sparse file too big or invalid error. Then my device was stuck at bootloader. After that, I proceeded to stupidly change my active partition from b to a. Now my device won't boot at all. Is there any way I can recover from this? Or is there a chance at all?
Click to expand...
Click to collapse
Boot to fastboot mode and install TWRP or any custom recovery on both slots.
Now reboot to recovery and change the active partition.
Xeust said:
Hi! I was on the February update and was trying to update to the March update using the factory images.
While updating I was faced with sparse file too big or invalid error. Then my device was stuck at bootloader. After that, I proceeded to stupidly change my active partition from b to a. Now my device won't boot at all. Is there any way I can recover from this? Or is there a chance at all?
Click to expand...
Click to collapse
What happens when you turn your device on? Are you able to boot to bootloader? Does the screen turn on at all?
If the file size was wrong, you were probably using the wrong file...although there's been issues with the latest Platform Tools, and bad USB cables can cause problems too.
TheMystic said:
Boot to fastboot mode and install TWRP or any custom recovery on both slots.
Now reboot to recovery and change the active partition.
Click to expand...
Click to collapse
TWRP isn't really relevant to A/B devices unless installing a custom ROM. If he's able to get into bootloader, TWRP isn't going to be any more help than reflashing the factory image.
V0latyle said:
TWRP isn't really relevant to A/B devices unless installing a custom ROM. If he's able to get into bootloader, TWRP isn't going to be any more help than reflashing the factory image.
Click to expand...
Click to collapse
In case of a bootloop, one can boot into recovery if it is installed on both slots. And from there the active partition can be changed, and this is possible only using custom recovery.
This is my understanding. I could be wrong because it's been a while since I got away from all these stuff, which are also becoming increasingly complex for no proportionate returns.
TheMystic said:
In case of a bootloop, one can boot into recovery if it is installed on both slots. And from there the active partition can be changed, and this is possible only using custom recovery.
This is my understanding. I could be wrong because it's been a while since I got away from all these stuff, which are also becoming increasingly complex for no proportionate returns.
Click to expand...
Click to collapse
The problem is, the recovery kernel is packaged into the boot image alongside ramdisk and the system kernel. Most A/B devices like Pixels do not have a recovery partition. TWRP does not support the compression that's used for the stock recovery as packaged, and if you flash the TWRP image to /boot, it overwrites everything else - meaning that your system will only boot to TWRP, because that's the only thing in /boot.
You could potentially live boot TWRP since this doesn't flash the boot partition, but again this is generally unnecessary and won't be of much help when you can simply reflash the original boot image
V0latyle said:
The problem is, the recovery kernel is packaged into the boot image alongside ramdisk and the system kernel. Most A/B devices like Pixels do not have a recovery partition. TWRP does not support the compression that's used for the stock recovery as packaged, and if you flash the TWRP image to /boot, it overwrites everything else - meaning that your system will only boot to TWRP, because that's the only thing in /boot.
Click to expand...
Click to collapse
Are all these done to enhance security or discourage custom mods? Or both?
For a short time when I had rooted my OnePlus 8T, I would flash TWRP on the inactive slot. That's because Oxygen OS would replace any custom recovery with its own recovery during boot, so this allowed me to boot into the inactive slot (which now has TWRP) and then run commands from there, so I don't have to use a PC each time.
TheMystic said:
Are all these done to enhance security or discourage custom mods? Or both?
Click to expand...
Click to collapse
Neither. It's just compression to reduce the amount of space the recovery kernel takes up in the boot image. If TWRP supported this compression we could potentially replace the stock recovery with TWRP. But, there isn't really much need to do this; most custom ROMs for the Pixel series just flash everything via web ADB.
TheMystic said:
For a short time when I had rooted my OnePlus 8T, I would flash TWRP on the inactive slot. That's because Oxygen OS would replace any custom recovery with its own recovery during boot, so this allowed me to boot into the inactive slot (which now has TWRP) and then run commands from there, so I don't have to use a PC each time.
Click to expand...
Click to collapse
That's not the case here. The boot slot cannot be changed without booting into TWRP. You could potentially install TWRP to boot_b, then set slot B as active; upon the next boot, the device will load TWRP. You could then do whatever you need to in TWRP, then set slot A as active, but you'd have no way of getting back to TWRP.
Xeust said:
Hi! I was on the February update and was trying to update to the March update using the factory images.
While updating I was faced with sparse file too big or invalid error. Then my device was stuck at bootloader. After that, I proceeded to stupidly change my active partition from b to a. Now my device won't boot at all. Is there any way I can recover from this? Or is there a chance at all?
Click to expand...
Click to collapse
The likely reason this occurred is because you used Platform Tools 34+. These 34 versions can't boot into fastbootd. For now you should be using Platform Tools 33.0.3.
You can't just switch slots and boot up the slot you switched to. You can only boot into the slot where the last firmware was flashed to. Therefore, when you changed your slot from b to a, you would have to flash the firmware onto slot a before it would boot into that slot.
If you can still get into the bootloader/fastboot mode, try flashing the factory image or using Android Flash Tool.
Lughnasadh said:
The likely reason this occurred is because you used Platform Tools 34+. These 34 versions can't boot into fastbootd. For now you should be using Platform Tools 33.0.3.
You can't just switch slots and boot up the slot you switched to. You can only boot into the slot where the last firmware was flashed to. Therefore, when you changed your slot from b to a, you would have to flash the firmware onto slot a before it would boot into that slot.
If you can still get into the bootloader/fastboot mode, try flashing the factory image or using Android Flash Tool.
Click to expand...
Click to collapse
For now its not booting at all. My pc can still detect it for a moment while I'm holding the power button but its not booting into bootloader so I can't do anything at the moment afaik.
V0latyle said:
What happens when you turn your device on? Are you able to boot to bootloader? Does the screen turn on at all?
Click to expand...
Click to collapse
Nope. Nothing and as I mentioned above, my pc only detects it while I hold the power button. Aside from that, its only a black screen.
Is there any way to flash the firmware or change the partition through other means that does not require bootloader/fastboot?
Xeust said:
For now its not booting at all. My pc can still detect it for a moment while I'm holding the power button but its not booting into bootloader so I can't do anything at the moment afaik.
Nope. Nothing and as I mentioned above, my pc only detects it while I hold the power button. Aside from that its only a black screen.
Click to expand...
Click to collapse
Ah. It sounds like the bootloader can't start, so the device is probably in QUSB mode. Unfortunately your only recourse is to have it repaired, as the files and tools you'd need to fix this are not publicly available. While it's possible to find the software (QPST/QFIL) you won't be able to find the necessary binary images to reflash your device.
Xeust said:
For now its not booting at all. My pc can still detect it for a moment while I'm holding the power button but its not booting into bootloader so I can't do anything at the moment afaik.
Nope. Nothing and as I mentioned above, my pc only detects it while I hold the power button. Aside from that its only a black screen.
Click to expand...
Click to collapse
There have been several people who have ended up like you after using Platform Tools 34+. None have been able to recover that I know of. The issue is known to Google (they are working on a fix). Can you confirm you were indeed using Platform Tools 34.0.0 or 34.0.1?
Lughnasadh said:
There have been several people who have ended up like you after using Platform Tools 34+. None have been able to recover that I know of. The issue is known to Google (they are working on a fix). Can you confirm you were indeed using Platform Tools 34.0.0 or 34.0.1?
Click to expand...
Click to collapse
Yes it was the 34.0.1
V0latyle said:
Ah. It sounds like the bootloader can't start, so the device is probably in QUSB mode. Unfortunately your only recourse is to have it repaired, as the files and tools you'd need to fix this are not publicly available. While it's possible to find the software (QPST/QFIL) you won't be able to find the necessary binary images to reflash your device.
Click to expand...
Click to collapse
If there's nothing I can do on my own, is it still possible to get it repaired? Or my only option is to send it back to google?
Xeust said:
Yes it was the 34.0.1
If there's nothing I can do on my own, is it still possible to get it repaired? Or my only option is to send it back to google?
Click to expand...
Click to collapse
If you're still under warranty, try to get repair that way. Warranty or no warranty, Google will probably refer you to a repair center like uBreakiFix.
V0latyle said:
If you're still under warranty, try to get repair that way. Warranty or no warranty, Google will probably refer you to a repair center like uBreakiFix.
Click to expand...
Click to collapse
Unfortunately not under warranty anymore. And its hard to reach google. or ubreakifix from my country :/
Thank you everyone. I conclude that my chances are pretty slim so I guess I'll consider getting a new phone.
Xeust said:
Unfortunately not under warranty anymore. And its hard to reach google. or ubreakifix from my country :/
Thank you everyone. I conclude that my chances are pretty slim so I guess I'll consider getting a new phone.
Click to expand...
Click to collapse
If you do end up contacting Google, you can refer them to this issue. Frankly it's there fault. They know their current Platform Tools are borked and yet still leave them up on the site for people to download and use.
Anyway, I wish you luck.
For those of you having the Platform Tools 34+ bug, as I did because I'm old and stupid at times, you may want to go thank this guy since using the 33.0.3 version of the PLatform Tools
did the trick for me.
V0latyle said:
Neither. It's just compression to reduce the amount of space the recovery kernel takes up in the boot image. If TWRP supported this compression we could potentially replace the stock recovery with TWRP. But, there isn't really much need to do this; most custom ROMs for the Pixel series just flash everything via web ADB.
That's not the case here. The boot slot cannot be changed without booting into TWRP. You could potentially install TWRP to boot_b, then set slot B as active; upon the next boot, the device will load TWRP. You could then do whatever you need to in TWRP, then set slot A as active, but you'd have no way of getting back to TWRP.
Click to expand...
Click to collapse
Wait, hold up. TWRP? On the Pixel 6? That exists?
(edit: nevermind, think I misread)
Deleted, since it's not for here.
Jaitsu said:
Wait, hold up. TWRP? On the Pixel 6? That exists?
(edit: nevermind, think I misread)
Click to expand...
Click to collapse
That What I want to know!