Database Info

Moto G XT1033 Soft Bricked, Cannot Boot To TWRP or CWM

no custom recovery loading
I am currently using moto G first generation xt1033 indian dual sim version.
I have soft bricked my phone.
WHAT I HAVE: I have access to fastboot
My bootloader is unlocked
Access to stock recovery
PROBLEM: I have tried to flash twrp , cwm and philz recovery but every time i boot into recovery mode stock recovery loads.
I cannot access USB Debugging mode since the phone is soft bricked.
I have also tried to flash stock firmware no change seen.
I would be glad if you all can help me.
@ravibhat i have read your thread and my starting problem was same as yours @lost101 please help me as well.Thank You

Ok.Post pics,videos so that we know it's the same problem.
Go to a service centre when you can and share what they've told.

did u use these steps ?
fastboot erase recovery
fastboot flash recovery ur_recover_zip_name.zip
try different versions of recovery, i suggest u use CWM V6.0.4.7
If that works, use the adb sideload feature to flash the ROM

thank you for the reply
@ankur.walia
i tried the erase recovery command this was the output
{
"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 when i tried to lock bootloader this was the ouput

mrawal031 said:
@ankur.walia
i did not try the erase recovery command but i tried to flash it directly.
ill try this and revert i hope it wouldn't pose a problem if i directly flash the .img file
Click to expand...
Click to collapse
yes, and try the version i mentioned because i was also facing the problem like u and only this specific versions worked for me

still no change
@ankur.walia @ravibhat
i tried the command you told me to. There is no change im unable to boot in flash recovery also now xD.
i also went to the service centre they said there is nothing they can do for this phone as the only thing they know is to flash the stock firmware.

mrawal031 said:
@ankur.walia @ravibhat
i tried the command you told me to. There is no change im unable to boot in flash recovery also now xD.
i also went to the service centre they said there is nothing they can do for this phone as the only thing they know is to flash the stock firmware.
Click to expand...
Click to collapse
are u not able to go in fastboot mode now?
if u are, then ls try different versions of the recoveries...
and yes...what actually is happening? are u able to see the boot logo? its stuck in bootlogo screen?..or is it struck in recovery's logo screen?
are it is not even booting itself?

ankur.walia said:
are u not able to go in fastboot mode now?
if u are, then ls try different versions of the recoveries...
and yes...what actually is happening? are u able to see the boot logo? its stuck in bootlogo screen?..or is it struck in recovery's logo screen?
are it is not even booting itself?
Click to expand...
Click to collapse
I can go to the bootloader after entering stock recovery no combination of keys can display the option.
my phone starts normally shows logo and all booting animation but after that it gets stuck on a blank screen showing nothing and no touch response. I have tried aprox 4-5 variants of custom recoveries but i can flash none of them even after trying your command and getting success written on screen.

mrawal031 said:
I can go to the bootloader after entering stock recovery no combination of keys can display the option.
my phone starts normally shows logo and all booting animation but after that it gets stuck on a blank screen showing nothing and no touch response. I have tried aprox 4-5 variants of custom recoveries but i can flash none of them even after trying your command and getting success written on screen.
Click to expand...
Click to collapse
well if u got the successful execution of recovery flashing then it should go to recovery mode, try holding powe and volume down together for quite some time (5-6 seconds by the clock) and then release it

ankur.walia said:
well if u got the successful execution of recovery flashing then it should go to recovery mode, try holding powe and volume down together for quite some time (5-6 seconds by the clock) and then release it
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B6y6POATHFhrLVhpUThNVUc1VXc/view?usp=sharing
you can see the condition even after flashing the custom recovery i get booted into stock recovery

OnePlus 7 Pro 5G [UK Model] Bricked Please Help!

I was attempting to root my OnePlus 7 so that I could increase the volume limits (I'm hearing impaired) via TWRP and then eventually Magisk, however it seems many things went wrong along the way. I managed to get TWRP working on my phone but then it wasn't finding any of my stored memory and therefore the TWRP Zip file I needed to finally root the phone. In my efforts to correct that I have bricked my phone (not sure if it's hard bricked or soft bricked) but currently it will only boot into the fastboot menu and selecting any option brings me right back to the fastboot menu again.
I tried getting back to the TWRP but no luck when I try to boot it I get the error message FAILED (remote: Failed to load/authenticate boot image: Load 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"
}
After reading online for a bit of help I thought it might be hard bricked so I tried to use the MSM tool but again I had no luck due to Param Preload - Device not match image
I have attached screenshots for both issues, I've also tried guides for soft bricked OP7P and despite showing as successful they reboot right back into the fastboot menu as if nothing has happened.
Please I'd really appreciate some help I've been trying for days to fix this mess!

Darhk Citadel said:
I was attempting to root my OnePlus 7 so that I could increase the volume limits (I'm hearing impaired) via TWRP and then eventually Magisk, however it seems many things went wrong along the way. I managed to get TWRP working on my phone but then it wasn't finding any of my stored memory and therefore the TWRP Zip file I needed to finally root the phone. In my efforts to correct that I have bricked my phone (not sure if it's hard bricked or soft bricked) but currently it will only boot into the fastboot menu and selecting any option brings me right back to the fastboot menu again.
I tried getting back to the TWRP but no luck when I try to boot it I get the error message FAILED (remote: Failed to load/authenticate boot image: Load Error)
After reading online for a bit of help I thought it might be hard bricked so I tried to use the MSM tool but again I had no luck due to Param Preload - Device not match image
I have attached screenshots for both issues, I've also tried guides for soft bricked OP7P and despite showing as successful they reboot right back into the fastboot menu as if nothing has happened.
Please I'd really appreciate some help I've been trying for days to fix this mess!
Click to expand...
Click to collapse
How did you unlock the boot loader?

tech_head said:
How did you unlock the boot loader?
Click to expand...
Click to collapse
I enabled USB Debugging on my phone and then used "Shift + Right Click" from within the folder with twrp file and used the command "fastboot oem unlock"

Was in this situation. If you have an unlocked bootloader, try to search for the fastboot ROMs on xda. Not sure if there is a 5g version though. With a try. Best of luck.

Darhk Citadel said:
I enabled USB Debugging on my phone and then used "Shift + Right Click" from within the folder with twrp file and used the command "fastboot oem unlock"
Click to expand...
Click to collapse
Look here https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424

toonstra said:
Look here https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Click to expand...
Click to collapse
Thanks, I tried that this morning perhaps I did it wrong, but when I used the same cmd window as I did to "unlock" the bootloader nothing happened. It went through the process and finally finished with no errors and said "press any key to exit" -But as for my phone it did not reboot in fact there was no change at all, it remained on the bootloader screen as normal. When I tried to reboot for a normal load it looped back to the bootloader, when I tried to reboot to recovery it booted back to recovery. It was as if the fastboot ROM was completely ineffective.

Darhk Citadel said:
Thanks, I tried that this morning perhaps I did it wrong, but when I used the same cmd window as I did to "unlock" the bootloader nothing happened. It went through the process and finally finished with no errors and said "press any key to exit" -But as for my phone it did not reboot in fact there was no change at all, it remained on the bootloader screen as normal. When I tried to reboot for a normal load it looped back to the bootloader, when I tried to reboot to recovery it booted back to recovery. It was as if the fastboot ROM was completely ineffective.
Click to expand...
Click to collapse
So I just tried to flash a recovery.img and I got this error "failed (remote (recovery_a) no such partition)" which leads me to believe that my phone is a lot worse than I originally thought...
Any help would be greatly appreciated I fully accept that I messed this up BIG TIME!

Darhk Citadel said:
So I just tried to flash a recovery.img and I got this error "failed (remote (recovery_a) no such partition)" which leads me to believe that my phone is a lot worse than I originally thought...
Any help would be greatly appreciated I fully accept that I messed this up BIG TIME!
Click to expand...
Click to collapse
Ok so I finally managed to get to the root of the problem and my phone is now back up and running without any issues, I completely missed the correct MSM too package that I needed for my phone and region as I have a UK OnePlus Pro 7 5G I needed to use this specific package to reset my phone back to stock: [OP7PRO 5G EU][OOS 9.5.11 GM27BA]
Appreciate all the help everyone hopefully someone else can use this to avoid making the same mistake I did!

My LG Q Stylo plus bricked, Please help save

Hi All,
Yesterday my LG Q Stylo plus was gone into black screen, and could not soft reset or hard reset. When I put it on charging, it vibrated again and again every few minutes, still with black screen. Then I opened the back cover, unplugged the battery to force it power off. Then I tried to factory reset it, but failed to start. Today I tried to flash it, but the PC could not detect the device even though I already downloaded LG driver. In this case, I can not flash it. And it showed on the screen said " FASTBOOT MODE.........". Please see attached picture. Anyone who know how to fix it please help me. Thanks a lot!
{
"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"
}

Can you get into recovery? If so, reset it in recovery or flash a new stock (or custom) rom onto it. In fastboot mode you may be able to directly boot into a custom recovery or flash a custom recovery if you need to.

I tried to flash a new stock rom on it. But PC could not detect the device, even though I already installed the driver. I tried to hold the power button with volume down key to reset it, it didn't work and the screen showed nothing but black. Only after the battery drained out, I plugged the charger on, the screen will be lit and showed the message like above picture showed. Is there any other way to let PC detect the device so that I can flash it?

If you're using Windows, maybe boot into a Linux Live USB (like linux mint for e.g.) and download adb and fastboot. Linux usually works all the time for me with fastboot, so try that and see if it can detect your phone. If detected you might have to run
Code:
fastboot oem unlock
which WILL erase your data, but you can't flash anything without doing so.

I just realized from the picture, msm8953 refers to the processor. Lock state is locked, does it mean the processor is locked? So it can't be soft reset or hard reset? How to unlock the processor? I remember the phone was running very very slow, then it went dead. Is it right that the processor was running on heat , so it was locked?

auroraguy123 said:
I just realized from the picture, msm8953 refers to the processor. Lock state is locked, does it mean the processor is locked? So it can't be soft reset or hard reset? How to unlock the processor? I remember the phone was running very very slow, then it went dead. Is it right that the processor was running on heat , so it was locked?
Click to expand...
Click to collapse
No. LOCK STATUS on Fastboot likely means the bootloader is locked to not allow custom images to be loaded. This is purely for security and can be unlocked by running the Fastboot oem unlock command I wrote about above. This wipes your data so that, no thief can steal your phone, unlock the bootloader, and browse your files with a custom recovery, as your data will be wiped. I'm not 100% sure but across the few phones in my life that use Fastboot, it has always meant the oem lock to prevent custom images for security reasons.
Any slowdowns occur either because battery saving scheme, full RAM, many processes running, malware, etc. Its not to do with Fastboot.
You should be able to see the device in Fastboot on Linux. Try and flash a custom recovery first, but it might not work because it's locked. In that case you'll need to unlock the Fastboot (which will erase your user data) and then flash a custom recovery, from which you can flash a new rom. Or flash stock recovery and load your official ROM zip if it's supported
Good luck, let us know if you have any issues.

as
quickishfm
said just connect your phone to computer and type
fastboot devices
if device is connected it will be shown on screen
after it just use command adb oem unlock
to unlock bootloader.
if you dont want to unlock bootloader then you will have to erase data partition by using command fastboot erase data

I downloaded adb and fastboot on Linux. But when I typed adb device, still can not see the device. What should I do?

You must type fastboot devices (or fastboot device, I can't remember ) when your screen is in that FASTBOOT MODE.
Once it's in there you just have to flash a custom recovery, or, unlock the bootloader first as we discussed before. This will wipe user data remember. After unlocking bootloader you can flash a custom recovery or stock recovery, and then a new ROM in recovery.

When the device is power off, after I plug it to pc usb, it will show charging sign on the screen and then go the fastboot mode as showed in the picture above. I checked the device manager it was connected as android bootlock inferface. But if I use adb device, there is no device is found.

Yes, you are right. I found the device. Then how to make a custom recovery if I don't want to lose the data?

auroraguy123 said:
Yes, you are right. I found the device. Then how to make a custom recovery if I don't want to lose the data?
Click to expand...
Click to collapse
There's no way to do that. It would not be secure if you could overwrite recovery if data is not deleted - then anyone could steal your phone, put a custom recovery and read data partition if not encrypted.
Maybe you can reflash a stock recovery zip (if you can find and if it let's you to flash) through fastboot, then go into recovery and sideload stock rom to your device. Most likely in this case the data will not be deleted.

Thanks. Why it showed unknowed command when I typed fastboot oem unlock?

Hmm, not sure, might have to look on Google. Does anything come up with
Code:
fastboot oem get_unlock_data
?

same when I typed fastboot oem get_unlock_data showed unknown command. Is there a way to let pc force the device to go to download moade because it stuck in the fastboot mode?

AFAIK the download mode is only a thing for Samsung, most other Android phones use fastboot as the download mode which flashes recovery etc.
Perhaps look online on ways to fix the unknown command issue... How did you install fastboot for the Linux?

Cn you run fastboot oem help, and fastboot --version please
Post the output here, thanks

I tried both on Linux and Windows, but the same result. I run fastboot devices, it showed my device. But when I run adb devices, it showed nothing. I run fastboot oem help, it showed the menu of the command. Please see the picture.

auroraguy123 said:
I tried both on Linux and Windows, but the same result. I run fastboot devices, it showed my device. But when I run adb devices, it showed nothing. I run fastboot oem help, it showed the menu of the command. Please see the picture.View attachment 5204225View attachment 5204225
Click to expand...
Click to collapse
That's useful, thanks. It seems the syntax has changed. Try
fastboot flashing unlock
to unlock the bootloader, and then you should be able to flash a custom recovery.
There's also update to directly flash an update.zip if you can find one, which might not need unlock boorloader. But this will likely have to be a stock update.zip signed by LG so no custom recovery or anything. I don't know if this will erase data.

I also run fastboot -w, it started wiping, but then failed as shown unknown command.

AVB VERIFY FAIL Rog Phone 2

hi guys i am looking for a on my rog phone 2 with AVB VERIFY FAIL after 5-6times stuck on logo,
It happen when my phone get battery drain and die, then i recharge it to 90% and tried to power on it stuck on the logo then suddenly AVB VERIFY FAIL show
{
"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"
}

In my case, even if I connect Rog Phone 2 via USB, it does not detect it, and even if I press START or Recovery mode on the boot loader, it enters the boot loader, so I can not even recover it on my computer
If press START several times, will get "AVB VERIFY FAIL!!"
What I did was downgrade with the official downgrade file and then update from settings to A10 and I got bootloader loop.
someone help plz.

Reflash phone's Stock ROM.

jwoegerbauer said:
Reflash phone's Stock ROM.
Click to expand...
Click to collapse
Okay.
I try it

jwoegerbauer said:
Reflash phone's Stock ROM.
Click to expand...
Click to collapse
I tried using the attached file but doesn't change.
Still don't detect.

A phone's Stock ROM typically gets flashed via ADB Sideload method and NOT via Fastboot.
Example:
Code:
adb devices
adb reboot sideload
adb sideload <PATH-TO-STOCK-ROM-ZIP-FILE-HERE>
adb reboot

jwoegerbauer said:
A phone's Stock ROM typically gets flashed via ADB Sideload method and NOT via Fastboot.
Example:
Code:
adb devices
adb reboot sideload
adb sideload <PATH-TO-STOCK-ROM-ZIP-FILE-HERE>
adb reboot
Click to expand...
Click to collapse
impossible

Have you ever successfully enabled "USB Debug" option on phone ( what is required you can access phone via ADB) ?

jwoegerbauer said:
Have you ever successfully enabled "USB Debug" option on phone ( what is required you can access phone via ADB) ?
Click to expand...
Click to collapse
I'm not sure if USB debugging was turned on, but I think it was ON.

I decided send ASUS Service Center

jhie1989 said:
hi guys i am looking for a on my rog phone 2 with AVB VERIFY FAIL after 5-6times stuck on logo,
It happen when my phone get battery drain and die, then i recharge it to 90% and tried to power on it stuck on the logo then suddenly AVB VERIFY FAIL showView attachment 5385729
Click to expand...
Click to collapse
Same

AVB VERIFY FAIL is shown when Stock Android OS got tampered by whatsoever method.

jwoegerbauer said:
AVB VERIFY FAIL is shown when Stock Android OS get tampered by what method whatsoever
Click to expand...
Click to collapse
A10→A9 official downgrade and upgrade to A10 by FOTA.
This is what I did.

Dungle unlock said:
A10→A9 official downgrade and upgrade to A10 by FOTA.
This is what I did
Click to expand...
Click to collapse
did your device get a fix

jhie1989 said:
did your device get a fix
Click to expand...
Click to collapse
nope

jhie1989 said:
hi guys i am looking for a on my rog phone 2 with AVB VERIFY FAIL after 5-6times stuck on logo,
It happen when my phone get battery drain and die, then i recharge it to 90% and tried to power on it stuck on the logo then suddenly AVB VERIFY FAIL showView attachment 5385729
Click to expand...
Click to collapse
Open platform tool type cmd
ADB devices
Reboot to bootloader
Fastboot devices
Fastboot boot twrp.img
Enter and u will get phone back

[solved + how i solved it] the current image(boot/recovery) have been destroyed

so, i was trying to install twrp, but i made a stupid mistake, instead of fastboot flash recovery i did fastboot flash boot, now it tells me: "the current image(boot/recovery) have been destroyed", when i go into bootloader, and attack the cable (both before and after) restarts itself.
things I tried: flash the original boot (it gave "FAILED (Write to device failed (no link))", obviously before the bootloader happened) change usb cable, flash the stock rom (obviously before the bootloader happened)), redownload adb /fastboot drivers, phone drivers, and google drivers. this is all i remember trying to do, i'm desperate, could someone help me please?

update: now i can use bootloader

update: I fixed it, in case this situation happened to you, I solved it like this: I had a windows update, while it was doing it, I connected the phone to the pc, in the end it no longer rebooted by itself (the phone) , then do fastboot flash boot (original boot), if it doesn't work, reboot the bootloader , from the bootloader, if it doesn't work, do the same thing downloading the drivers again, then do fastboot flash boot (original boot.img), if you want to download costum recovery, do fastboot flash recovery (costum recovery.img). I fixed it like this, now I have a costum recovery, costum rom and root!

Hello friend, I have a question. I closed the bootloader and when I closed it, the recovery image was destroyed.
Now I can't enter my cell phone and it stays in an infinite boot
any solution with locked bootloader

Angel1104 said:
Hello friend, I have a question. I closed the bootloader and when I closed it, the recovery image was destroyed.
Now I can't enter my cell phone and it stays in an infinite boot
any solution with locked bootloader
Click to expand...
Click to collapse
try going into the bootloader and re-unlocking it

{
"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"
}
That happened to me when I wanted to block the boot, so I think the boot was blocked and only stayed in the realme recovery like the following photo

Angel1104 said:
View attachment 5798249That happened to me when I wanted to block the boot, so I think the boot was blocked and only stayed in the realme recovery like the following photo
Click to expand...
Click to collapse
I don't understand if the recovery works or not, it's a bootloop with locked bootloader and you can go into recovery or locked bootloader without accessing recovery? you are confusing me, however, if you have access to recovery download the stock rom from the recovery, if not, try to unlock the bootloader again by doing fastboot flashing unlock, then flash the stock recovery and then download the stock rom from the recovery

And how do you enter that mode without the application?

enter bootloader and do fastboot reboot recovery, in bootloader you can't perform flashing actions and many other things (bootloader locked) but some things, like reboot should work

in case you get the same error for the recovery you have to unlock the bootloader again

Can I send you a private message?

yes

Did you solve it? I'm facing the same issue.

Gamer_Mida said:
update: I fixed it, in case this situation happened to you, I solved it like this: I had a windows update, while it was doing it, I connected the phone to the pc, in the end it no longer rebooted by itself (the phone) , then do fastboot flash boot (original boot), if it doesn't work, reboot the bootloader , from the bootloader, if it doesn't work, do the same thing downloading the drivers again, then do fastboot flash boot (original boot.img), if you want to download costum recovery, do fastboot flash recovery (costum recovery.img). I fixed it like this, now I have a costum recovery, costum rom and root!
Click to expand...
Click to collapse
I am having trouble understanding what you did exactly. I am getting this same error with a Xiaomi Mi 8 Lite.
Edit: got it working by disconnecting all usb ports and trying another port.

Angel1104 said:
Hello friend, I have a question. I closed the bootloader and when I closed it, the recovery image was destroyed.
Now I can't enter my cell phone and it stays in an infinite boot
any solution with locked bootloader
Click to expand...
Click to collapse
same as me i dont know what to do