Realme 5 showing big battery with cross sign - Realme 5 Questions & Answers

So, first my Realme 5 goes to bootloop and fastboot mode was not opening and it was showing the following error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I took it to Realme care and they returned the phone saying its fastboot is not opening. Now the phone is showing the following. What to do?
Please help

charge your phone
boot to fastboot mode then apply boot destroyed fix
Fix Boot Destroyed Error
📌 Why this error?-> You might encounter this error when you try to reboot to system after flashing a Rom (RUI/OSS vendor based rom more importantly) but you didn't flash vbmeta disabler or vbmeta image. 📌 How to fix this error?-> There are three possible ways:1. Go to fastboot mode and try to...
telegra.ph

you don't need to repair it from realme center
it's just kernel or vbmeta partition broken

CjConvento said:
you don't need to repair it from realme center
it's just kernel or vbmeta partition broken
Click to expand...
Click to collapse
Can I recover my data from phone? Also fastboot is not opening. I thing fastboot is also crashed. What should i do?

Related

Pixel 2 Stuck On Bootloader, Can't Boot/Recovery [ERROR: Slot Unbootable: Load Error]

Hey guys! I have a Pixel 2 that basically bricked this morning. When booting only the bootloader comes up. The device can't boot into the OS or even the recovery.
Now I understand the Pixel 2's are dual partition and my "Boot-slot" is "b" not "a". I don't remember changing it though, that is if the factory default is "a". I'm not sure if everything is on "a" and that's why this is happening but I can't switch the boot slot over to "a" through fastboot as "slot change is not allowed in lock state". I did not enable USB Debugging so I can't change Lock State, or at least not that I know of.
Does anyone know how to get this phone back up and running?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Re flash factory image.
You don't need usb debugging for fastboot, only ADB. Unlock your bootloader using fb, then reflash the factory image, as enzyne said. Yeah, when you unlock, you're going to lose everything, as it completely wipes your device, but at least you'll have your phone back.

oneplus 7 stuck in fastboot (Fixed)

guys please help me, my oneplus 7 non pro stucked in fastboot. i tried boot to recovery but its still boot to fastboot mode. my phone is unlocked and already flashed recovery. please help me thanks
Edited: fixed guys, I've tried any method and the works one was flash rom with fastboot. I conclude that Iam not supposed to wipe vendor... Thanks for all of your, hope this will help anyone else
Try wiping the cache from recovery and see if it boots. Since you didn't say what you did right before this happened people won't be able to help you.
That's right. You should explain what you did before stuck at Bootloader.
arkanaulia said:
guys please help me, my oneplus 7 non pro stucked in fastboot. i tried boot to recovery but its still boot to fastboot ode. my phone is unlocked and already flashed recovery. please help me thanks
Click to expand...
Click to collapse
Check this out, this will fix it:
https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3930862
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

No Play-Protect Certification despite complete OOS reinstall

So I wasnt able to use GPay anymore when I rooted my device a month or two ago. Understandable.
To fix that, I've tried unrooting: didnt work. Now I reinstalled OOS entirely, wiped the whole device first, and it still doesnt work.
Do I need to lock the bootloader again or what are the criteria to get the certification?
Here some screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wipe all is different with erase all, if you really want to wipe all use toolallinone firmware recovery flash and select wipe all and reboot options. Gpay probly sees the root files or magisk manager somewhere still
I don't really think that that was the case. I wiped everything in TWRP and then formatted the data as well.
In case someone else is facing this problem, this is what I did:
Boot into fastboot and re-lock the bootloader.
Code:
fastboot oem lock
I was then only able to boot into fastboot, and since the bootloader is locked, you can't boot into TWRP etc.
You then turn off the device and use MSM Tool to re-install OOS.

8T booting in fastmode and can't find the boot & recovery image

Hello,
I tried to install ColorOS 12 for the 8T yesterday. Installation worked fine but had alot of bugs with the OS and I wanted to get back to OxygenOS 11...
But after trying to install OxygenOS11 I got an error while installing and the phone just showed this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And now my phone boots into fastboot mode. I can't access the recovery mode.
I also can't boot it into EDL mode or using MSM tool. The MSM tool is empty and I can't see my device there.
I tried to install the qualcomm driver but nothing helps. My phone instantly starts booting into the fastboot menue when I plug in the usb cable
Picture from google:
My device state is unlocked btw.
I dunno what to do now
Would be thankful when I got some tips here
Use MSM to revert to stock firmware.
If you have chinese KB2000 variant revert to HOS, then local upgrade to OOS, if you want.
If you have EU model, you can use OOS MSM straight.

Energizer HARDCASE H550S firmware

Hello,
I bought this phone and didnt notice that it has only Android 7. Exists some custom firmware with higher Android for install on it?
Apparently not.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thing is that this is a nearly 4 year old device from a brand that doesn't have much of a name in the smartphone industry and virtually no community. As far as I can see there isn't even a way to unlock the bootloader of this device. Couldn't even find a way for their newer (2020) U710S so I'm afraid it's a dead end.
I did oem unlock with fastboot.
Also I tried boot original recovery.img by command
Code:
fastboot boot recovery.img
just for test, but it won't work, it displays "No command" on screen and broken android logo. It has MT6750 processor, I found some TWRP recovery images for same chip, but I do not want flash it with fastboot flash recovery twrp.img, becouse im scaried about bricking it. It's safe to flash recovery.img with this TWRP image? It's possible to get back stock recovery.img, if it won't work?
I tried it and it was not able to work, so i did original flash. And really, stok recovery gave me the same error, "no command", also new phones, when someone tries boot to recovery from bootloader menu gave same error, so its manufacturer problem

Categories

Resources