After I gave warranty on my Realme Q because of the error "The current image (boot / recovery) has been destroyed and can not boot". My phone has rebooted but when I checked it did not enter fastboot mode (when I pressed the power button + volume down, the fastboot logo kept showing up and then off continuously, when I released my hand the device started automatically. Please tell me what the error is & how to fix it
Khan Tran said:
After I gave warranty on my Realme Q because of the error "The current image (boot / recovery) has been destroyed and can not boot". My phone has rebooted but when I checked it did not enter fastboot mode (when I pressed the power button + volume down, the fastboot logo kept showing up and then off continuously, when I released my hand the device started automatically. Please tell me what the error is & how to fix it
Click to expand...
Click to collapse
I don't have a phone, so I can't be more helpful than that, but I can suggest one thing:
Try to find online the stock rom of your phone and then to flash it.
Related
Hi,
I own galaxy s3 i9000, currently on custom rom. My phone automatically rebooted and got stuck on bootloop. If I am able to enter in recovery mode, i can wipe cache(which may can help to get out of bootloop). But the problem is I am unable to enter into recovery mode because phone's volume up button is not working and my phone auto reboots every time after power off or reinserting battery. Is there any other way to clear cache or enter into recovery mode?
I dont want to flash my stock rom via odin (because i didnt backup my some important apps and msgs), this will be my last option.
sorry for my bad english
The normal way I get my phone into recovery mode from the PC is using ADB and the command: "adb reboot recovery". However, I bet this won't work in your case for one of several possible reasons: depending on when the bootloop occurs in the boot process, the phone may never reach a point where ADB is able to see your phone in the first place; if this is happening after a flashing a new custom ROM, then also it's unlikely that USB debugging is turned and the PC is not yet authorized to connect with it over ADB.
Another thought, could your power button be stuck down? I had a GS3 SCH-I535 several years ago and the power switch went bad on it, it would keep rebooting, shutting down randomly, or I'd be unable to turn on the screen. I had a switch replaced and it was fine after that. I don't think it's normal for the phone to automatically boot up when you reinsert the battery, that's why I bring that up. Maybe you can wiggle the power button a bit and try to unstick it if that's the case.
I tried to remove and stick back the power button again, but still it didnt worked. By the way fixing power button will not help me to get into recovery mode as my phone's volume up button is also not working, and recently I found out that I cant enter into download mode too because when I press respective buttons (volume down + home + power) for download mode, it gives warning msg to click 'volume up' buttton to enter into download mode or 'volume down' to reboot. Therefore again volume up button is required to enter into download mode too. So the only option remained for me is to visit service center and fix the volume up button.
Hello, all.
I have a tricky problem here.
Let me tell the background of the problem first.
Basically, I flashed cf-autoroot using odin on my phone and it restarted all perfectly, then I restarted it to download mode using pc command "adb reboot download" since trying from my phone always gets stucked on download mode warning screen, PRESSING VOL UP DOES NOTHING.... When I reached download mode, I FLASHED TWRP V2.8.0 using ODIN, it went directly to home screen not recovery, then I powered it down and restarted it to recovery mode and since then its stuck on Samsung boot logo with 'recovery not seandroid enforcing screen' . I tried to boot into download mode using VOL DOWN + POWER KEY since my HOME BUTTON IS FAULTY AND DOESNT WORK. So, I get to the download mode warning screen, BUT pressing volume up OR volume down does nothing and I have to keep POWER + VOL DOWN pressed for about 10 seconds again to come to download mode warning screen. How can I go to download mode when I cant access the TWRP recovery and also have A NON-WORKING home button .
URGENT HELP NEEDED, PLEASE.
Good day everyone. Recently my Mate SE (BND-L34) was left to charge overnight and wouldn't boot up the next day, it's just stuck on the start up screen. Unfortunately, developer options weren't on so no usb debugging although I can only access fastboot when I hold power + vol down. However, when I hold vol + up, nothing happens so I can't access any recovery menu. The phone is completely stock so no root, no custom recovery or firmware, locked bootloader, etc. I did try both methods mentioned here for locked bootloader: "https://forum.xda-developers.com/mate-20-x/how-to/fw-emui-9-1-0-123-evr-al00-t3935995"
Neither of them worked. With HStool, the program (HStool) closes itself after HiSuite has decompressed the download and is about to start installing recovery. The other method mentioned, when "installing recovery" part of the process starts, the phone exits fastboot and goes to the boot screen... both methods actually end in the same result with HiSuite giving me the error message "Recovery Failed" and the phone being on at the boot screen (exiting fastboot before the procedure has finished).
In case it's of any relevance the current firmware on the phone is BND-L34 8.0.0.362. Any suggestions would be greatly appreciated, thanks.
After flashing stock rom for realme Q, my device has an error "The current image (boot / recovery) has been destroyed and can not boot" . I tried to do everything to get into fastboot mode but it didn't work ( Press Power+ Volume Down, Power+Volume Down+Volume Up+Plug in the usb cable). Now my phone can't reboot, can't enter fastboot mode and recovery mode. Please tell me how to fix it
MOD ACTION:
Thread closed as duplicate of https://forum.xda-developers.com/android/help/current-image-boot-recovery-detroyed-t4105425
Hello! i don't know how but my rooted Mi A3 last night decided on its own to update to Android 10. So i woke up with all of mine Magisk magic all gone. I tried to root again but my phone is stuck on the 'Mi' boot screen.
So here's the situation:
if i press volume up + power button, instead of entering recovery mode the "no Command" screen shows up;
if i try to fastboot, my pc doesn't recognize anymore my device;
There is any another way to enter recovery mode? Can i flash a boot image on a sd card? Do i have to throw away my beloved xiaomi?
You have most probably incompatible Magisk module which prevents phone from booting Android 10. Flash stock boot image to get phone working (fastboot should work, double check your drivers etc.).
Or perform factory reset from stock recovery:
"If presented with an image of a broken Android with "No Command" shown on the screen, do the following:
- Press and hold the Power button.
- While holding the Power button press the Volume Up button then release the Volume Up button then the Power button."