After flashing vendor and havos os rom on Realme 5 RMX1911 i didn't wipe/format my data as recommended.So my phone I’m unable to goto fastboot,recovery or anything my device is only turning on for 20 seconds to display “The current image(boot/recovery) have been destroyed and can not boot.” How to fix it? Well somehow this screen flashing stops when i connect my phone to laptop and hold my volume keys and power key for a couples of seconds,and it shuts down.But laptop plays a device connection chime sound after it.
NOTE: "I'm unable to go to fastboot or recovery and i've now locked my bootloader" I was able to flash recovery.img but unable to boot into recovery.But now i'm stuck at destroyed image screen loop.
Also i've ran some commands from https://android.tutorials.how/fastboot-commands/
NOTE: "I'm unable to go to fastboot or recovery and i've now locked my bootloader"
AmmarMujahid69 said:
After flashing vendor and havos os rom on Realme 5 RMX1911 i didn't wipe/format my data as recommended.So my phone I’m unable to goto fastboot,recovery or anything my device is only turning on for 20 seconds to display “The current image(boot/recovery) have been destroyed and can not boot.” How to fix it? Well somehow this screen flashing stops when i connect my phone to laptop and hold my volume keys and power key for a couples of seconds,and it shuts down.But laptop plays a device connection chime sound after it.
NOTE: "I'm unable to go to fastboot or recovery and i've now locked my bootloader" I was able to flash recovery.img but unable to boot into recovery.But now i'm stuck at destroyed image screen loop.
Also i've ran some commands from https://android.tutorials.how/fastboot-commands/
NOTE: "I'm unable to go to fastboot or recovery and i've now locked my bootloader"
Click to expand...
Click to collapse
any update? did you find a way?
Related
The other day my WiFi Xoom stopped getting past the "Motorola Dual Core" screen.
I have removed the SD card.
Android recovery mode gives me the error android with the "!"
It does this plugged in or on battery.
Not rooted.
What else should I try?
neoka said:
The other day my WiFi Xoom stopped getting past the "Motorola Dual Core" screen.
I have removed the SD card.
Android recovery mode gives me the error android with the "!"
It does this plugged in or on battery.
Not rooted.
What else should I try?
Click to expand...
Click to collapse
What were you trying to do before this hapened? Need more info to be able to help.
24348542 26
DavilaDarkness said:
What were you trying to do before this hapened? Need more info to be able to help.
Click to expand...
Click to collapse
Hadn't really done anything. Just normal use. No out of the ordinary installs. Turned it off. Next day I tried turning it on and it won't boot.
Did you ever resolve this ?? I was give one to repair for a child and it too is stuck on the red boot screen. The good thing is the person who sold it to them was a hacker and put TWRP on it of all things. I was floored when I tried to enter recovery and found teamwin.
but the problem is its still stuck on the boot screen, i did flash it 3-4 times with M604 M602 flashes and some other customs but nothing works, it completes flashing and wiping caches but always goes back to stuck on boot screen..
perhaps I have to unclock the bootloader or something for the flash to be succesfull ?
Just wanted to say I fixed it with these commands and firmware if anyone is interested. I tried everything else including flashing with twrp and wiping all caches and it didn't work, getting the stock firmware and doing it like this worked to clear boot screen endless stuck
download fastboot and adb and xoom drivers 6.4 (about 5mb) and the appropriate stock firmware. for me it was ZM604
at the command type
adb reboot bootloader
you may need to unplug and replug cable after it goes in fastboot mode.
fastboot devices
.. should return something "02a439cj0skjdke fastboot" to proceed.
fastboot oem unlock
.. look at your tablet and follow the instructions, for me it was down twice and up once to accept unlock conditions, then it reboots
on reboot press vol down 2 seconds after you see moto logo, it will enter fastboot
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot erase userdata
fastboot reboot
no need to relock after, you will see android logo and first boot pop up after 2-3 mins
Hi I have the following problem: after I flash Cannibal open touch recovery I could not flash any .zip file so I decided that I go back to CWM touch so I restarted my phone. Phone booted into fastboot mode with the following message no boot or recovery IMG so I decided to flash recovery with fastboot. I opened the folder with fastboot command flash_recovery connect the phone to usb but the command line always showed waiting for device. I unplugged the phone and tried to press the volume keys but nothing happened as if it freezes. I pulled the battery and try it again but no response. I cant connect phone to odin because it has broken power button and after I insert the battery it always turn on itself. Please advise me what to do thank you.
Seems your drivers have gone corrupt. Try a different system and use Nexus Root Toolkit.
I tried this option but without success. Phone does not respond to anything. No volume up or volume down. It´s just stucked on bootloader.
This link says that if you get <waiting for device> , then fastboot is not configured properly. Check out the link over here.
You may also try this command "fastboot boot recovery-clockwork-6.0.4.3-crespo.img" to boot into recovery without installing it.
no hope
The reason you cannot navigate in fastboot/bootloader is that your powerswitch is probably stuck in the "on position"...does your device immediately power on when battery is inserted?
The way i solved this a few months ago was to completly remove my powerswitch from the board power my device on..use quickboot to enter fastboot menu and input commands...
Also completely removing your power button makes powering on your nexus alot more complicated.
what i did was go to download mode (holding vol+ and -) and pluging phone in..this takes you to download mode
then you need to get a copy of a boatloader file to flash via odin which will reset your phone and power it on...pm me if interested i can provide you with files necessary
Hi There!
I'm exeriencing a wierd problem:
On my rooted Doogee S60, i was able to enter the built in recovery mode (and from there the fastboot mode) with Vol+ and Power.
Since i've installed a twrp recovery.img, pressing Vol+ and Power will launch the TWRP UI (wich i cant use, because my touchscreen is disabled).
Normal boot won't work eighter - i flashed a corrupted system.img file as it looks like (ooops). There is also the message at the Boot Screen saying:
"Orange State - Your device has been unlocked and can't be trusted. Your device will boot in 5 seconds"
... although these 5 seconds won't countdown and the device won't boot.
If i enter the TWRP, i can still access the ADB mode. So i can sideload stuff on the device, even the sd card is shown on pc. But the command
adb reboot fastloader
will reboot the phone, but not load the fastloader/fastboot - as it stucks at boot screen (orange state).
Any other ideas to access fastboot, due to flash the recovery.img again with the original to fix?
... or simple question: did i brick it?
thx in advance
Command
Code:
adb reboot fastloader
doesn't exist.
Look inside here:
How to Reboot Android Device into Fastboot or Recovery Mode via ADB « My Digital Life
If you’re using Android phones, tablets or devices, which is proliferating across all markets, prices and channels nowadays, then you may want to familiar yourself with fastboot or recovery mode, which is useful when you need to troubleshoot your beloved phone from the like of Samsung, HTC...
www.mydigitallife.net
introjoe said:
Hi There!
I'm exeriencing a wierd problem:
On my rooted Doogee S60, i was able to enter the built in recovery mode (and from there the fastboot mode) with Vol+ and Power.
Since i've installed a twrp recovery.img, pressing Vol+ and Power will launch the TWRP UI (wich i cant use, because my touchscreen is disabled).
Normal boot won't work eighter - i flashed a corrupted system.img file as it looks like (ooops). There is also the message at the Boot Screen saying:
"Orange State - Your device has been unlocked and can't be trusted. Your device will boot in 5 seconds"
... although these 5 seconds won't countdown and the device won't boot.
If i enter the TWRP, i can still access the ADB mode. So i can sideload stuff on the device, even the sd card is shown on pc. But the command
adb reboot fastloader
will reboot the phone, but not load the fastloader/fastboot - as it stucks at boot screen (orange state).
Any other ideas to access fastboot, due to flash the recovery.img again with the original to fix?
... or simple question: did i brick it?
thx in advance
Click to expand...
Click to collapse
Hi introjoe,
Are you doing? i have the doogee s60 but i just cant root it :'( can you tell me please how did you do it, or the files you use for it? i allready tried but, when i reset and enter fastboot mode, my pc simply dont recognize it.
I want to upgrade the android system to 9 or 10, thats why im doing all o this.
Thanks in advance.
@doryan666
i wasnt able to root the device in the end unfortunately.
i tried using an unofficial twrp, but i was stuck at the main boot screen
i t seems to need some bootloader-activation-code to enter the bootloader to install a new os.
the command line would look like
adb reboot bootloader "CODE"
the activation code has not been released yet by doogee ... and most probably never will be.
sorry to say but i dont think android upgrad will be possible with this device
After I tried to reflash the boot through the fastboot utility, my phone began to vibrate wildly without stopping, lasts for about 10-15 seconds, then stops for a couple of seconds and starts vibrating again, attempts to hold down the shutdown keys, volume up and down keys did not help: (
I assumed that you need to reflash the bootloader board, maybe I'm wrong (I don't understand this).
Are there any solutions to this problem without resorting to flashing the phone board itself?
As far as I remember, the command was like this:
fastboot flash boot twrp.img
or
fastboot flash boot recovery twrp.img
(*) [(twrp.img) The firmware image worked, I played around with the command and added the word boot, and then pressed enter into the console, everything broke]
Phone model: Xiaomi Redmi 6 (was unlocked by fastboot)
Hi guys,
I'm facing the following issue:
I took my pixel 4a, unlocked the bootloader, later worked on the boot.img to with magisk to root the device... prepared the modified img file and launched the command fastboot and it went successfully. Later sent the fastboot reboot comand, and the device booted up, it is stuck with the google logo and from there, trying to get back into fastboot mode but whenever I do the procedure (presso volume down + power up) , I first get a screen telling that the device is corrupted and it might be not safe... later starting to bootup but straight away stuck at google logo ... the device is not seen from adb commands or fastboot commands... how can i recover the device according to you guys ?
thanks,
giuseppe
letsrock666 said:
Hi guys,
I'm facing the following issue:
I took my pixel 4a, unlocked the bootloader, later worked on the boot.img to with magisk to root the device... prepared the modified img file and launched the command fastboot and it went successfully. Later sent the fastboot reboot comand, and the device booted up, it is stuck with the google logo and from there, trying to get back into fastboot mode but whenever I do the procedure (presso volume down + power up) , I first get a screen telling that the device is corrupted and it might be not safe... later starting to bootup but straight away stuck at google logo ... the device is not seen from adb commands or fastboot commands... how can i recover the device according to you guys ?
thanks,
giuseppe
Click to expand...
Click to collapse
If you are getting the unlocked bootloader message of "being corrupted", that is normal. You'll see it every time you reboot now that your bootloader is unlocked. Sounds like you are having trouble getting back into fastboot. I find it easier if I unhook my phone from the pc while holding the power and volume down (not up) buttons. You should be able to fastboot flash your stock boot.img to get your phone back. Make sure you have the correct boot.img for your firmware.