Database Info

[Q] Low Battry while Unbricking Corrupted Bootloader

Hi All,
My phone Got Stuck in Bootloop due to some unknown reason. While trying to fix I somehow bricked the bootloader too and later found this thread
[TOOL] Unbrick Corrupted Bootloader [http://forum.xda-developers.com/showthread.php?t=2623587 ].
I was able to "Blank-Flashing Bootloader" but now my phone battery is low.
when I turn on my phone it shows the following screen.
Please help / guide how to fix this. Thanks..
Mobile Screen Image .. might also help to guide me better, Thanks in advance
{
"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"
}

h e l p ....

speedytangent said:
Hi All,
My phone Got Stuck in Bootloop due to some unknown reason. While trying to fix I somehow bricked the bootloader too and later found this thread
[TOOL] Unbrick Corrupted Bootloader [http://forum.xda-developers.com/showthread.php?t=2623587 ].
I was able to "Blank-Flashing Bootloader" but now my phone battery is low.
when I turn on my phone it shows the following screen.
Please help / guide how to fix this. Thanks..
Mobile Screen Image .. might also help to guide me better, Thanks in advance
View attachment 2854323
Click to expand...
Click to collapse
The fastboot commands do not work when the battery is low. Is a security lock to avoid bricking your device while flashing. You did not specified if you tried charging your device. If the battery is low the best thing you can do is let it charge for a couple of hours and after that continue restoring the firmware.

alresave said:
The fastboot commands do not work when the battery is low. Is a security lock to avoid bricking your device while flashing. You did not specified if you tried charging your device. If the battery is low the best thing you can do is let it charge for a couple of hours and after that continue restoring the firmware.
Click to expand...
Click to collapse
I tried charging it with PC USB , as well as with Wall Charger.. let the phone pulgged on wall charger for about 6+ hours...
but still no charging.... :-/

So whats the way out now ? Can I open MOTO G to Charge its battery directly as we can do to Moto Droid Razr ?

I think I just hard bricked my Moto G

So the problem is that my Moto G won't turn on or enter in fastboot mode, I tried charging it up and holding the power button for 3 minutes but it doesn't works. The problem started when I flashed a stock rom so I could change my Moto G to the google edition, there was no problem, then I proceeded to update the firmware to 4.4.4, then I restarted my phone so the updates could be installed, when I checked back the screen was completely black, and it's been like this for more than 3 hours.
Another rare thing is that when I plug the phone on the computer, my computer recognizes the phone like it was on, but I can't access the media files.
I need some serious help right here, sorry for my english thought.

You have hardbricked your MotoG no solution for the moment, i am on your same situation....

I thought I hard-bricked my Moto G too by upgrading to GPe Lollipop through sideload, but I tried this (http://forum.xda-developers.com/mot...rick-hard-bricked-moto-g-2nd-gen-5-0-t2966010) and successfully booted into fastboot mode; and just now booted into GPe Lollipop with bootloader version 41.13 on the Boost variant (XT1031). The only bug I have is the usual screen-ripple, and it goes away after turning off the screen. (CDMA doesn't work, of course)

VitaTaf said:
I thought I hard-bricked my Moto G too by upgrading to GPe Lollipop through sideload, but I tried this (http://forum.xda-developers.com/mot...rick-hard-bricked-moto-g-2nd-gen-5-0-t2966010) and successfully booted into fastboot mode; and just now booted into GPe Lollipop with bootloader version 41.13 on the Boost variant (XT1031). The only bug I have is the usual screen-ripple, and it goes away after turning off the screen. (CDMA doesn't work, of course)
Click to expand...
Click to collapse
I've already tried with different softwares and I get the same result :/
{
"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"
}

When I had Samsung Galaxy Note 1, these devices reacted to certain system commands with permanent brick.
If you have tried all and the result is still VOID, then indeed the phone might have more value as spare parts - in ebay.

Help on sp flash tool error

Hello, my Android has been bricked and unable to power on. So I decided to flash stock rom via sp flash tool but it is not successful. I'm always getting errors which I don't know its meaning. Kindly help and provide solution to my problem. See attached Screenshot for error code. Thanks.
{
"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"
}

yusufroqib said:
Hello, my Android has been bricked and unable to power on.
Click to expand...
Click to collapse
There are 2 types of bricked phones - Soft and hard
1) Soft bricked: Your phone can be switched on, load recovery or get mesmerized by your bootloop
2) Hard Bricked: Just as the name states, you phone is a literally brick. You know your phone is hard bricked when it will not power on at all.
Since you are unable to power on your phone, I believe it might have been hard bricked. Hence, why your SP Flashtool is not working either

Tiqqy said:
There are 2 types of bricked phones - Soft and hard
1) Soft bricked: Your phone can be switched on, load recovery or get mesmerized by your bootloop
2) Hard Bricked: Just as the name states, you phone is a literally brick. You know your phone is hard bricked when it will not power on at all.
Since you are unable to power on your phone, I believe it might have been hard bricked. Hence, why your SP Flashtool is not working either
Click to expand...
Click to collapse
Do you have any possible solution to my problem?

yusufroqib said:
Do you have any possible solution to my problem?
Click to expand...
Click to collapse
Read the first post of a thread I will be attaching very carefully and hopefully everything will work out fine.
Thread: https://forum.xda-developers.com/cr...ndroid-one-hard-bricked-device-t3361988/page2
Let me know how it goes

[HELP] OP 7 Pro randomly bricked yesterday, trying to unbrick it but I have never touched any developer options

Hello everyone,
first of all I wish to apologize if I am not precise enough it is my first time on an android developers' forum.
Here's the situation:
My OP7 Pro (GM1910 model which is the chinese firmware, but I live in Europe so I think my seller flashed it himself prior to selling it) got bricked for no reason yesterday.
It pretty much froze while I was using (some pixels lines started going wild randomly cf. pic 1 the upper line
{
"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"
}
)
then got in a bootloop, until i got a black screen with "Qualcomm CrashDump Mode" (cf pic 2).
**Disclaimer: I never tried to root my phone nor Install custom ROMs, indeed both usb debogging, bootloader and OEM are locked.**
At this point I can only go through fastboot mode and recovery mode.
Here is what I tried to do, unsuccessfully:
My 1rst attempt to go on recovery mode and to wipe cache (did not work), then reset system settings (did not work), then erase everything (did not work too).
My 2nd attempt was to unbrick it via EDL Mode and using MSMtools for Android 10. I tried both EU and Global firmware and the download took approx. 200 sec, it did not work my phone still freezes while booting and goes into bootloop. I do think I was on Android 11, but I could not find a mirror to download Android 11 version of MSM.
My 3rd attempt was the Fastboot Method, using fastboot drivers but since both the bootloader and OEM are locked I get "FAILED (remote: 'Please enable OEM unlocking in developer options first')" in cmd.
At this point I am starting to be hopeless. Do you guys think my phone's hardware is just dead ? Do you have any ideas/solution for me?
Anyway, thank you for reading

it is late but... maybe you still own this phone. In that case you can try MSM tool. Try older stock ROMs and then try to upgrade them. Unfortunately you have on your own uncover upgrade route. Sure it is risky, bacause who knows what did previous owner with it, but it is your choice what to do about it.
Also read posts about going from chinese ofw to global/eu. If nothing intersting here, try oneplus community forum. Hope you figure out something very important and you get phone back alive.

Question [TB128FU] Xiaoxin Pad 2022 4/64 Flashing ROM went bad, fastbootloop and bricked.

Hello everyone,
I just bought a Lenovo TB128FU tablet which I thought flashing it would be easy. Turned out I managed to make it stucked in the fastboot and I have no idea which ROM should i use to bring it back to factory settings. I did try to use RSA and happened to be using a ROW type of ROM but it got stuck on logo bootloop and after several minutes it brings me back to fastboot (with the ROM from RSA, I could access the stock recovery). I tried aswell to flash it using the CN ROM I found across the internet but it bricked my device with no logo at all. I could still flash the ROM through EDL mode but I am not sure what to do to fix my ROM as I still wonder which correct ROM I should use.
P.S: I read some forums about unlocking the bootloader which requires the unlock ZUI thingy and my serial number is not detected there. Aswell as I searched for my tablet's model on the lenovo documentation. I assume this tablet to be Chinese ROM but the ROM I found "TB128FU_CN_OPEN_USER_Q00012.0_S_ZUI_13.5.365_ST_220526_qpst" doesn't seem to work (it bricked my device after flashing it through QFIL). Did I miss something or anybody could help me point out anything? I also notice that my serial number turned from its original to 0123456789ABDCEF. Please help me I am so frustrated with this problem.
{
"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"
}

Go to warranty, tell them ỵou don't know what happens

Hey! thank you for replying. Sadly i don't think that would be possible, I bought it in China but now I am back to my land

Try "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" after flash rom.
Get vbmeta from rom file

I had the same issue, so I tried flashing vbmeta.img.
It was stuck in a weird bootloop, but after holding the power button,
IT WORKED!!!
thanks for the fix, you're awesome
PS: never trust pre-unlocked tablets you bought on Aliexpress