HELP!! my Asus Max Pro M1 bootloop & orange fox recovery got stuck too - Android Q&A, Help & Troubleshooting

so just like the title say, i can't enter android and my orange fox recovery got stuck at orange fox starting screen, i can go to fastboot but i didn't manage to enable usb debugger because my system got stuck just after i flash it, so adb didn't recognize my device.
is there a way to fix my phone or is it impossible to fix it?
is there a way to enable usb debugging in this state?

What happened, did you get any solution on this? same happened to my device and it's still in bootloop

Related

Help - Bootlooped

I have been looking at hundreds of forums to find no true solution to my problem.
I installed a custom boot and now my phone is stuck boot looping. There are actually some solutions to my problem but, this is what I have.
Usb debugging is disabled
Cannot axcess device through ADB
I do have axcess to fastboot
When trying to flash, get error phone returned fail
Cannot axcess recovery menu
Device not detected by odin
Is there a way to fix any of these so I can get rid of bootanimation.zip and fix my issue?
Please help!

Phone stuck in boot loop - Need to turn on USB debugging

I am currently in a situation where USB debugging was not enabled, CROM service status is set to "Locked". This is causing an issue on my International Galaxy S6 Edge (g9250) -- It is stuck in a boot loop and the android OS that was previously installed was wiped on accident through the stock android recovery mode.
I am unable to flash TWRP recovery to the phone, I am unable to use Odin to flash a stock ROM image to the phone, or perform any data transfer between my Windows machine to the phone. Smart Switch also does not work. Also Now I am sure this is because I never enabled developer mode and turned on USB debugging, and also because this CROM service is set to lock. When I attempt to sideload using ADB I get error:closed. When using the Skipsoft Unified Android Toolkit any task performed stops at: "Waiting for USB debugging".
Is there any solution for this? I've looked all over the internet and haven't been able to solve my issue -- I'm stuck at a perpetual boot loop because there is no Android OS on the device's partition, and also am unable to flash the stock ROM using ODIN or sideload using ADB.
Is there is a way to turn on USB debugging when stuck in a bootloop? Or a way to disable CROM service on the phone to be able to flash or transfer files?
As of right now the device is completely useless and I have been researching for the past 5 days
Any help is very appreciated, please let know if there is more information needed.
Hi there. I am presently stuck in the exactly same situation. Can you please tell me what you did after that. thanks

HardBricked Tablet NOT recognice pc after installing TWRP

Hey guys! The last day I wast trying to Install a custom recovery (twrp) to my Tablet Polaroid pmid7102dc, and I didn't found the TWRP for my model so I downloaded twrp-3.2.1-0-twrp.img. I used the adb program to Install it and after that, I triyed to reboot my Tablet I only got the surprise that my tablet was HardBricked. It stays in the POLAROID screen with a message "orange State Your devices has been unlocked and can't be trusted. Your device will boot in 5 seconds" after that the tablet reboot but didn't enter. Actaully I can not enter to the recovery mode and my pc will not recognice it when I connect it.
What can I do?
Help :c

Question Stuck in dm-verity curruption screen

Hi all,
my wifes phone was stuck in a bootloop at the MIUI logo (phone is full stock original, no changes at all).
All options with the buttons (rebbot,safe mode, wipe all data) did no work. Battery drain also not.
I tried to reboot via "Minimal ADB an Fastboot" and since then I get the message -> dm-verity curruption on the POCO Screen. If I press POWER within 5s, the message disappears and phone is stuck on the POCO screen forever, not even booting to the MIUI logo anymore.
I tried to flash the exact same version of the recovery ROM that is on the phone via MIFlashPro -> did not change anything.
Is there a solution to flash the original firmware to the phone? Like a "full reset"? I am able to enter the red FastBoot logo with the buttons.
Thanks for every help
Is the bootloader unlocked?
aricooperdavis said:
Is the bootloader unlocked?
Click to expand...
Click to collapse
They said “no changes at all”. Nobody unlocks bootloader for sh-ts and giggles.
rosicky88 said:
Hi all,
my wifes phone was stuck in a bootloop at the MIUI logo (phone is full stock original, no changes at all).
All options with the buttons (rebbot,safe mode, wipe all data) did no work. Battery drain also not.
I tried to reboot via "Minimal ADB an Fastboot" and since then I get the message -> dm-verity curruption on the POCO Screen. If I press POWER within 5s, the message disappears and phone is stuck on the POCO screen forever, not even booting to the MIUI logo anymore.
I tried to flash the exact same version of the recovery ROM that is on the phone via MIFlashPro -> did not change anything.
Is there a solution to flash the original firmware to the phone? Like a "full reset"? I am able to enter the red FastBoot logo with the buttons.
Thanks for every help
Click to expand...
Click to collapse
is usb debuging enabled?
Arealhooman said:
is usb debuging enabled?
Click to expand...
Click to collapse
They said “no changes at all”. Nobody enables usb debugging for sh-ts and giggles.
aricooperdavis said:
They said “no changes at all”. Nobody enables usb debugging for sh-ts and giggles.
Click to expand...
Click to collapse
Yes they do. I enable it as soon as I get any device. Multiple years before I rooted. Why wouldn’t I .
They're trying to flash stuff, so asking if the bootloader is unlocked is a reasonable question. But to answer your question, most users don't enable USB debugging. MIUI warns users that it's a bad idea, which is enough to put many people off, and this is sensible if you don't need to use it as it's a security risk (see this paper for some clear examples).
Fix for dm-verity error on Xiaomi devices · Issue #261 · bkerler/mtkclient
Hi, I've managed to fix the dm-verity error on the Redmi Note 10 Pro 5G/Poco X3 GT by simply rebooting into the bootloader and running fastboot oem cdms. After running this my device remains unlock...
github.com

Realme 8 5g

I have an issue with this phone
Let me explain
First i unlock bootloader and all that stuff
Root the phone installed a custom rom
Suddenly I notice the Wi-fi was not workin and I installed an actualization, the phone runs out of battery
Now when I try to turn on the phone it says that the image had been destroyed and cannot boot
I cant go in to fastboot mode or recovery mode
My pc does not recognize the device
What can I do?
Take it to authorized service center and let them try to fix it.

Categories

Resources