Develop Bugs

Cannot enter recovery mode! Please help!

Hey all. I'm thinking I may have bricked my mother's Zenfone So I was trying to help her out by installing a custom rom on the phone as she complained about the bloatware that comes with the phone slowing things down. I couldn't get the bootloader unlocked (tried every procedure under the sun), so I tried entering recovery mode and flashing the boot.img and droidboot.img directly (saw a thread where someone did this, then tried unlocking and it worked).
The phone boots into up fine but now everytime I try entering recovery mode, I get the dreaded USB logo screen. It remains there for about a minute, reboots and comes back again. Does that about 3-4 times before turning off. Is there a way to just completely get the phone back to 100% factory settings? I'd rather just starting over from there. The problem I'm having is pretty much exactly the same as what the person in the video below is experiencing....

Can you get to bootloader mode?
Sent from my ASUS_Z00AD using Tapatalk

jimchee said:
Can you get to bootloader mode?
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Sorry for the late reply. If u mean Fastboot mode, where I can see the Product name, Booloader version, etc, then no. That's where I see the USB icon.

You've screwed it up, there might be a way if you can flash a RAW image of the rom on there but you'd need to look around as I can't remember the thread name, something about recover hard brick (which is what you have)...

ultramag69 said:
You've screwed it up, there might be a way if you can flash a RAW image of the rom on there but you'd need to look around as I can't remember the thread name, something about recover hard brick (which is what you have)...
Click to expand...
Click to collapse
Hmmm. Well I came across this thread...
http://forum.xda-developers.com/zenfone2/general/unbricking-research-unbricking-method-t3162848
They seem to have procedures to help with my issue. But I came across another problem. Hopefully someone there could help with it. I post here if I succeed.

hi, I removed os from my Asus and now it is not entering fast boot mode any one can kindly help me pls.

Bootloop, soft brick?

I don't know why, but for some reason my nexus 5x is stuck in a bootloop. I was rooted running 6.0.1 (MTC19T) when it shutoff and was not trying to update to N as others were.
I can access the bootloader, but not recovery (just reboots). I have flashed other stock 6.01 OTA's which hasn't changed anything. Flashing TWRP again does nothing. Was trying to follow THIS thread, but PC does not recognize phone in download mode. Also, the phone will only stay download mode for about 15 seconds before rebooting. Any advice?
LGH970 32GB
Bootloader: BHZ10m
Baseband: M8994F-2.6.32.1.13
Secure boot: enabled
Device state: unlocked

shadows006 said:
I don't know why, but for some reason my nexus 5x is stuck in a bootloop. I was rooted running 6.0.1 (MTC19T) when it shutoff and was not trying to update to N as others were.
I can access the bootloader, but not recovery (just reboots). I have flashed other stock 6.01 OTA's which hasn't changed anything. Flashing TWRP again does nothing. Was trying to follow THIS thread, but PC does not recognize phone in download mode. Also, the phone will only stay download mode for about 15 seconds before rebooting. Any advice?
LGH970 32GB
Bootloader: BHZ10m
Baseband: M8994F-2.6.32.1.13
Secure boot: enabled
Device state: unlocked
Click to expand...
Click to collapse
Well If u can access bootloader you can flash any firmware using fastboot commands.

Totally weird, but my 5x just did the same thing. I opened the Yahoo Sports app, and it froze. An attempted reboot, and it's now stuck in a boot loop. If I try to enter recovery, it reboots. Unfortunately, my desktop is at work, so I can't troubleshoot right now.
I'm starting to wonder if I'll be reading several of these posts today. Hmmm...

enzo_cz said:
Well If u can access bootloader you can flash any firmware using fastboot commands.
Click to expand...
Click to collapse
Yes, but I've tried flashing multiple different stock images from the google repository by unzipping them and flashing the components to no avail. Is there another way to flash it? Should I be flashing something else?

UPDATE: tried everything. Getting a replacement from google. Only a month or two from the year warranty. Week without a phone. Thanks Obama...

shadows006 said:
UPDATE: tried everything. Getting a replacement from google. Only a month or two from the year warranty. Week without a phone. Thanks Obama...
Click to expand...
Click to collapse
That is exactly the route I took with customer service this afternoon.

Mine is @ LG as I haven't bought from Google... Let's see...

talkEDtv said:
That is exactly the route I took with customer service this afternoon.
Click to expand...
Click to collapse
Same here, when I went back from 7 to 6.0.1 bootloop. I unfortunately did not get to try the TOT file method as I had already RMA it out and just this morning caught this.
Out of all the Android devices it amazes my how easily this device bricked. I had numerous HTC devices and despite being carrier locked and using a java card to unlock the bootloader i never once had this issue with with any of them, they are very forgiving and will be seriously considering the 2016 HTC nexus as this one is only 4 months old. Im nowhere near n noob to rooting and flashing but disappointed how unforgiving the device is. Granted there are some things I really like about it, but bricked in 4 months is a bad sign of quality IMO.

Nexus are impossible to brick, unless you flash stock factory image...

I have had this same problem.
http://forum.xda-developers.com/nexus-5x/help/5x-bootloops-recovery-t3391459
Eventually after disassembly, I called Google Play and LG, to have it replaced.
I also had a cracked camera glass and screen, got a new Nexus 5x , and havent been charged since it seems the phone was due for failure no matter what.
The problem SEEMS to be the button or signal of of the power button always being pressed. When it's off it will even turn on by itself, and maybe if your lucky itll stay on for a while.
Call in, request RMA
---------- Post added at 04:20 PM ---------- Previous post was at 04:19 PM ----------
gpvecchi said:
Nexus are impossible to brick, unless you flash stock factory image...
Click to expand...
Click to collapse
This is not true, unless in context TO BRICK, as they seem to be BRICKING themselves sometimes. Hardware defects exist in all electronics, even the good ol'nexus

My pixel randomly bricked itself and I'm stuck

Hello.
Yesterday my pixel xl (non-carrier-locked model) suddenly rebooted and got into a bootloop. It never gets past the white google loading screen.
It's fully stock, running the latest Pie + update. Bootloader is locked and the allow oem unlock in developer mode is also disabled.
I though I could just get into bootloader and swap the active partition using fastboot --set-active=(a or b) whichever works. But I soon realized that this is not allowed when the bootloader is locked. I can't unlock the bootloader using fastboot flashing unlock because oem unlocking is disabled in the developer settings. I can't obviosly get to the developer options without getting my phone to boot.
As an alternative I thought I could simply factory reset / erase user data from the recovery. However, when I try to get into android recovery from the bootloader, the phone reboots!
Things at the moment are looking grave. I don't have much data to lose on the device. What are my options given this predicament?
Thanks.

blueren said:
Hello.
Yesterday my pixel xl (non-carrier-locked model) suddenly rebooted and got into a bootloop. It never gets past the white google loading screen.
It's fully stock, running the latest Pie + update. Bootloader is locked and the allow oem unlock in developer mode is also disabled.
I though I could just get into bootloader and swap the active partition using fastboot --set-active=(a or b) whichever works. But I soon realized that this is not allowed when the bootloader is locked. I can't unlock the bootloader using fastboot flashing unlock because oem unlocking is disabled in the developer settings. I can't obviosly get to the developer options without getting my phone to boot.
As an alternative I thought I could simply factory reset / erase user data from the recovery. However, when I try to get into android recovery from the bootloader, the phone reboots!
Things at the moment are looking grave. I don't have much data to lose on the device. What are my options given this predicament?
Thanks.
Click to expand...
Click to collapse
Have you tried rebooting with Volume down+ power held in? Or has the battery died? Also what exactly were you doing when this happened?

same issue happeend now to me. any updates?

hey whats weird... ive got the same issue, December security patch stock pie....
---------- Post added at 05:01 AM ---------- Previous post was at 05:01 AM ----------
ive tried other stock pie, stock oreo, custom kernels, I cant even boot into twrp... anything I try to boot up it just bootloops.

Apologies for such a long delay in my response.
Phalanx7621 said:
Have you tried rebooting with Volume down+ power held in? Or has the battery died? Also what exactly were you doing when this happened?
Click to expand...
Click to collapse
ferydaboss said:
same issue happeend now to me. any updates?
Click to expand...
Click to collapse
godkingofcanada said:
hey whats weird... ive got the same issue, December security patch stock pie....
---------- Post added at 05:01 AM ---------- Previous post was at 05:01 AM ----------
ive tried other stock pie, stock oreo, custom kernels, I cant even boot into twrp... anything I try to boot up it just bootloops.
Click to expand...
Click to collapse
The only thing that loads up fine is the bootloader menu via vol down + power. I can't even get into the recovery from there. When I do, the phone simply reboots and continues it's bootloop.
I've already tried reflashing the latest stock rom on both the slots. Still no juice. The same thing happens. Powers on, I see the white google logo screen with the small unlocked icon to the bottom. Then reboots into the same screen forever. I thought doing a clean flash would most certainly fix this issue. But seems like I was wrong.

Looks like hardware (eMMC, main board) fail, not soft brick...

Hi there,
Did anyone tried to heat their phone a bit with a hair dryer or something to see if the phone boot? Could be another bootloop fiasco similar to LG crap and Nexus 6P chip solder getting loose?!
People got their Nexus 6P temporary booting heating the device...
If nothing else works, you guyz could try it? ?
Good luck...

I gave up. I opened the phone and looted it for parts.

Question Hard Bricked Pixel 6 Pro Android 13

Hello! I think I've bricked my Pixel 6 Pro using Android 13, I rooted with Magisk successfuly but when I flashed kirisakura kernel using EXKM and rebooted it gave me a bootloop, after bootloop tried flashing patched boot.img from factory in Pixel Flasher but didn't work, also tried using adb and nothing. I think I have flashed the wrong file or something after kirisakura because it would show on Pixel Flasher with a ? at the beginning of the ADB connected devices.
It only would boot to Google logo and then restart, did it a few times but then the screen became black and unresponisive, I've tried vol down power and vol down power and vol down only and vol up power any combination for more than 30 seconds and nothing works, doesn't show on adb devices or wants to boot into any mode.
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Sad thing, my Pixel arrived yesterday and I hard bricked it in the same day.
willing to pay anyone here if someone helps me to boot my pixel again.
Thanks in advance.

PunkOz said:
Hello! I think I've bricked my Pixel 6 Pro using Android 13, I rooted with Magisk successfuly but when I flashed kirisakura kernel using EXKM and rebooted it gave me a bootloop, after bootloop tried flashing patched boot.img from factory in Pixel Flasher but didn't work, also tried using adb and nothing. I think I have flashed the wrong file or something after kirisakura because it would show on Pixel Flasher with a ? at the beginning of the ADB connected devices.
It only would boot to Google logo and then restart, did it a few times but then the screen became black and unresponisive, I've tried vol down power and vol down power and vol down only and vol up power any combination for more than 30 seconds and nothing works, doesn't show on adb devices or wants to boot into any mode.
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Thanks in advance.
Click to expand...
Click to collapse
Reflash the entire android 13 image

DespairFactor said:
Reflash the entire android 13 image
Click to expand...
Click to collapse
How if it doesn't boot into fastboot or anything, PC won't recognize anything since my Pixel's screen is completely black, won't do a single thing, just a sandwich glass, won't even show if it's charging, nothing.

Read this thread if you haven't...

blackhawk said:
Read this thread if you haven't...
Click to expand...
Click to collapse
Everything downloaded to my PC belongs to Android 13, factory image, kernel, everything, didn't rollback, I was in a bootloop where my device went into fastboot mode everytime but then it went to google logo and stopped working at all. Nothing shows on my screen, I've read somewhere on reddit that a guy had the same problem and had to return his device.

PunkOz said:
Everything downloaded to my PC belongs to Android 13, factory image, kernel, everything, didn't rollback, I was in a bootloop where my device went into fastboot mode everytime but then it went to google logo and stopped working at all. Nothing shows on my screen, I've read somewhere on reddit that a guy had the same problem and had to return his device.
Click to expand...
Click to collapse
Yeah I've been watching this out of curiosity as I run Samsung's on 9 and 10. That thread has a lot of good information and links. Someone there may be able to help.
I thought 13 be fubar, it hasn't disappointed

I know you said you tried all combinations of buttons, but when pressing power+volume down, have you tried "fastboot devices" in terminal to see if the device ID shows?
If you can get into fastboot even with no display, you should be able to reflash the factory images.
Edit:
Also, if you're going to try flash custom kernels and want an easy app to use, I'd recommend installing Kernel Flasher as it'll backup all of the modified images and allows you to check the partitions.

lottarake said:
I know you said you tried all combinations of buttons, but when pressing power+volume down, have you tried "fastboot devices" in terminal to see if the device ID shows?
If you can get into fastboot even with no display, you should be able to reflash the factory images.
Click to expand...
Click to collapse
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices

@PunkOz can you describe exactly how you updated? Did you attempt to flash the custom kernel immediately after the update, or did you let Android 13 boot normally on the stock kernel?

PunkOz said:
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
Click to expand...
Click to collapse
ADB and fastboot display different device IDs. You'll want fastboot vs adb when in fastboot mode.
If you can't get it to display and want to get a new pixel, hopefully you're within the return window and can exchange it easily.
Edit:
Reread your OP and the reason you bootlooped from what I gather is that you manually flashed the stock boot.img and kernels now modify more than just the boot.img, so you're in conflict with dtbo, vendor_boot, and vendor_dlkm images. When returning to stock with a custom kernel, you'll need to be sure reflash all of these from the factory zip.

PunkOz said:
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
Click to expand...
Click to collapse
it seems like you may have booted a kernel that didn't work, failed boot a few times and threw you onto the A12 bootloader. Would need to verify how you installed android 13

Following....
I have the same problem...blackscreen. All I did was use the command " fastboot flash boot patched_magisk.img”.

Easy solution: using chrome on your pc or mac go to pixel factory firmware and find the the newest update. Plug in your phone and click "flash", select your device, wipe everything and flash all partitions.

rajchelu said:
Following....
I have the same problem...blackscreen. All I did was use the command " fastboot flash boot patched_magisk.img”.
Click to expand...
Click to collapse
If you manage to fix it, I recommend booting the magisk image, instead of flashing it with the 'fastboot boot /patched_boot.img' command
Then direct install in magisk app
If it fails when booting the image, device will just reboot into normal mode.

PunkOz said:
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Sad thing, my Pixel arrived yesterday and I hard bricked it in the same day.
willing to pay anyone here if someone helps me to boot my pixel again.
Click to expand...
Click to collapse
The good news is that your phone is still under warranty!
The bad news is that you now have to USE the warranty.
A13 includes anti-rollback code for the bootloader. Unfortunately, the anti-rollback code BRICKS the device instead of putting you into a recoverable state.
The sequence that killed you is this; you installed A13 and the updated bootloader to one slot, but not the other. You successfully booted A13 at least one time, which advanced the anti-rollback version. You then installed a kernel/boot that was incompatible with A13, which failed to boot a few times, causing it to switch to the other slot (with the old bootloader). Because it tried to run the old bootloader with the updated anti-rollback version, it immediately went into BRICK mode.

DespairFactor said:
it seems like you may have booted a kernel that didn't work, failed boot a few times and threw you onto the A12 bootloader. Would need to verify how you installed android 13
Click to expand...
Click to collapse
I think that's what happened, I installed Android 13 via OTA, had to apply for beta in order to receive the update faster because it wasn't available in my country yet.
Than installed patched boot - magisk - custom kernel via EXKM app and then bootloop and then flashed a few times boot stock and patched and nothing worked. @V0latyle
96carboard said:
The good news is that your phone is still under warranty!
The bad news is that you now have to USE the warranty.
A13 includes anti-rollback code for the bootloader. Unfortunately, the anti-rollback code BRICKS the device instead of putting you into a recoverable state.
The sequence that killed you is this; you installed A13 and the updated bootloader to one slot, but not the other. You successfully booted A13 at least one time, which advanced the anti-rollback version. You then installed a kernel/boot that was incompatible with A13, which failed to boot a few times, causing it to switch to the other slot (with the old bootloader). Because it tried to run the old bootloader with the updated anti-rollback version, it immediately went into BRICK mode.
Click to expand...
Click to collapse
Yeah, I haven't been around XDA community as much as before, it was 100% my fault, didn't read that much before starting to flash custom kernel and boot. Didn't know there were 2 slots. My phone is 100% dead now, I bought it through amazon from a third party store, do you think I voided my warranty? Screen won't turn on at all with any combination of keys (Pwr+Vol) and won't even display when it's charging, completely bricked

If anyone out there has an answer to fixing this problem. Please let us know! I'm also on the same boat. Didn't flash to both slots so now I have a paperweight. Really don't wanna spend money on a new phone so I'll try to be patient and hope someone can be my saviour

So does anyone have an update about this problem? I'v eread somewhere that it could be in EDL mode when the screen doesn't turn on. Could that be the case and could we do something with that?

Markelijk said:
So does anyone have an update about this problem? I'v eread somewhere that it could be in EDL mode when the screen doesn't turn on. Could that be the case and could we do something with that?
Click to expand...
Click to collapse
We don't have tools to deal with this processor's EDL mode, so unfortunately it's likely the only fix is to reach out to Google to have it repaired under warranty.

Shot in the dark here...but this reminds me of people only flashing to one slot and the phone rebooting into the other "okd OS" slot and the phone bricking. So this is a little different...the phone MIGHT be on, just on a big black screen that just shows nothing. So yes it IS "bricked".
But UNPLUG the phone, give it about 10 seconds, then press and hold power, volume up and volume down, preferably OUT of the case, and just hold it for like a minute. After thirty seconds or so it might forcefully reboot, if it does, then we need to get into fastboot and reflash A13, but then ALSO flash it to the other slit. This is why it is SO IMPORTANT to flash BOTH SLOTS.
I had THIS problem on my Oneplus 6T, yes...a different phone...but it my phone was DEAD for a week before I discovered that I could force boot it.
But if you have the phone connected to the pc, the bootloader or whatever is trying to talk will not allow the phone to do anything.
Also, plug the phone into the charger. If it is in a hard soft brick and the phone DIES it can be a NIGHTMARE to get it back to life, usually involving you JUMPING the battery manually....like I said. A shot in the dark. But worth a shot.

Xiaomi Stuck in MI logo data backup needed

Hi all;
I writing to ask if I can get support from you in order to recover data from my phone. This is the situation I have a Xiaomi 10T 5G device that 4 days ago suddenly reboot and get stuck on MI logo screen. I have try entering in Recovery mode and test Reboot, Safe Mode and Repair Mode with no luck. I have try also to connect it to MIPC suit but the phone get not detected, only if I put it in fastboot mode I got a message from PC suite telling that I should change to Normal mode and reconnect.
I have installed ADB drivers and my usb drivers of my device.
The issue and before sending it back for reparation I want to backup the photos, all the other data is not relevant. The phone is with the fabric ROM. Is there any way that I can recover the data??
Thanks in advance for your support.

locked bootloader? unlocked?

GizmoTheGreen said:
locked bootloader? unlocked?
Click to expand...
Click to collapse
I assume is blocked as nothing g has been done to it since the purchase.

That happened to me twice. I was pushing it to recovery, fastboot, safemode for over and hour untill it turned on. It was after update last spring. Never happened again. I cant remember what happened (i know i realized it than, but i was on a business trip and pissed, just remember that prior to that it was a problem with unlocking it/power button/sensor, maybe not the same thing as you have, since it was looping),i think it was some bug

Hi thanks for the reply but I assume is not the same case as I have try to fastboot, safe mode and repair mode a lot of times and nothing happened.
Hope to find a way to get the data from the device.

zepo88 said:
Hi thanks for the reply but I assume is not the same case as I have try to fastboot, safe mode and repair mode a lot of times and nothing happened.
Hope to find a way to get the data from the device.
Click to expand...
Click to collapse
it may be stuck in some kind of recovery loop because it crashed and think it couldn't boot. like windows does.
try turn it completely off then start it.
I'm sorry if you did not unlock before hand, there is nothing you can do.
flashing rom requires unlocked bootloader. running TWRP requires unlocked bootloader.
flashing stock rom/ recovery rom from SD will I think wipe your data
unlock bootloader will wipe your data.
if you can't get it to boot you are SoL for the data friend :/

Thanks Sir. Seen that there is no option I have wipe all the data and the phone has come back again to normal operation. Now I will try to root to use some data recovery tool to see what I can get. Any recomendations??