Happened to me when. I was in school with my pixel 7 rooted, it started spamming me with android update notifications till I decided to power the whole phone off with force (vol down + pwr) then when it booted back up it was bootlooping so when I got home I decided to flash stock firmware and it hard bricked itself
Haven't worked much with motorola phones but seeing this is a Qualcomm chip phone, the flashing lights mean that its in EDL mode. You could probably confirm it in Device manager under "Ports". You might be able to rescue the phone if you find a firmware you can flash in EDL mode, you will need a tool like QFIL (Qualcomm Flash Image Loader)
Yeah NAND integrity has failed. Like as he said, the phone was working perfectly when he placed It in the drawer and 2 weeks later, Startup Failure, also its been 1 year now, he just threw the phone away probably, also even if he saved it the screen turned White meaning the screen also burned out in its last seconds of life. This phone may have suffered either an electrical Failure or the components used to make It where super low quality.
In oneplus 6 phones, it shows like qualcomm dump crash and a bunch of verbose. My friend had that issue and reballing the nand fixed the issue. Somehow i also have the same phone 😂😂
I had an old Moto G that also died suddenly and it was because of the eMMC reaching the end of its life. The bootloader screen was pretty much like this one and nothing could be flashed successfully, no matter how much I tried. The only difference was that *sometimes* it would boot randomly and work shortly, but then it would crash and return to the bootloader.
I actually had the same problem too that I was still learning about phones and etc; if I remember, my phone would out of nowhere just start blinking with the little dot and I would never know that it's fully bricked up to now. I never had a cable or anything to fix it, so I was kinda screwed and got a new phone (RIP saved money (no I'm not in the US))
Whoa holy crap I had a Moto G die the same way! I was in a bit of a bind because I tried to buy a flagship phone afterwards, but my bank needed to confirm my identity...but I couldn't confirm it with a text or call because my phone was dead lol.
It has gone in edl mode but blinks because it doesnt show the display like it shows in oneplus 6 phones as "qualcomm crash dump". My friend had that issue and reballing fixed it
I think the reason why the phone won't boot anymore is because when you pressed the power button, it applies pressure and then the screen breaks because it was mostly destroyed. My main phone is dumb and likes to brick itself unless I take out and place back in the battery and turn it on without the casing when I drop it, so maybe try replacing the screen or taking out the battery and placing it back in. edit: Guys leave this 1 year old comment aloneee
It may sound dumb but try to leave the phone plugged in for some time. From a quick google search it is rare but that can fix it and maybe give you a second chance to flash it again. Just so you know to get the best results use the OEM cable and always use the back USB ports not the ones on the front. From my understanding, if nothing works, the motherboard is done for. You can try researching whether the phone has an emergency flash more (some phone like OnePlus phones have) and try to revive it again but the data was gone from the start as the phone itself was corrupted. R.I.P stopwatch
@@JigaTech its either fully bricked or u just need to replace the display, it might sound weird but its quite easy to replace a display. if you're not confident, just watch a video from hugh jefferys or something.
@@JigaTechyes I have the same phone and it can be fixed. When I plugged in the charger it will be blinking because of a component (idk what that is) is shorted out. I just hold down power and vol up but somehow it worked. It happened because I was using a 3rd party charger 😂
apparently phones can build up static electricity which prevents them from working at all, if this is the case then take out the battery and press the power button and hold it for at least 10 seconds, this will get rid of the residual electricity, then put the battery back on and try booting it up.
Guys EDL (Emergency Download Mode) will not work, the NAND integrity has failed. He said in the video that it still worked when he put it in a drawer and 2 weeks later. It bricked itself. Either the phone was made with very bad quality components or it suffered an electrical failure. Also even if he saved it he could not use it, the screen turned white meaning it burned itself in the last seconds of its lifetime. A year has passed and threw away the device probably.
The phone is bulletproof. I have that phone and idk how many times i have dropped it, it still functions. He definately had no storage on his emmc which ofc bricked his phone
if this phone literally just died randomly, i think it might be a broken flash chip and there is literally no way to rescue it also that flashing light is probably EDL (emergency download) mode, as that failed fastboot flash probably completely screwed up all partitions on the phone
It looks like it's in some sort of DFU Mode I usually get out of these clunky modes by holding power and volume up while plugged in, power and volume down while plugged in, power and volume up and volume down while plugged in, power and volume up while unplugged, power and volume down while unplugged, power and volume up and volume down while unplugged (all of these methods have to have the buttons being held for at least 1 minute/(or until something happens) it's what I have to do when I brick old phones and if that does nothing it's completely dead and belongs in the bin or sits on a shelf gathering dust as a useless novelty or whatever or in a box to dig up 6 months later and try again but somehow make it worse (I have about 50 phones dumb phones smart phones and brick phones)
go to a professional chip reballer and get the NAND chip removed, solder it onto a USB drive's NAND flash location and plug it in, u will get access to all ur data
Phone is not dead. During fastboot flash the whole system was formatted. Use MTK Preloader mode to flash system, there are literally tons of info out there. As far as I know, you must remove the battery, hold the power button and connect the phone to PC for the phone to enter Preloader Download mode, from where you can use any MTK flash software compatible with it to load the firmware. The phone should automatically power off after a few seconds it enters Preloader mode if not software triggers flash mode.
Qcom port like com 5 or smth idk. I had the same phone (moto g6) and it still works but the battery is flat and i also once bricked it and reflashed using qcom
I suspected this phone is powered by MTK. In case it is a Qualcomm, it should be detected as QHSUSB_DLOAD in Device Manager with appropriate Qualcomm USB drivers.
Try these steps and see if it will work. Please do these steps while your phone is connected to the original Motorola charger that came with the phone, plugged directly to a wall outlet. 1. Please press and hold the VOL DOWN key. 2. While still holding the VOL DOWN key, press and hold the POWER key. 3. Hold both keys down for over 120 seconds. This is more than 2 minutes and will seem like a long time, it will help to time this to ensure you hold the keys long enough. 4. After holding the keys down for more than two minutes, release them. 5. The Flash Boot screen will display, and the Normal Reboot option will be highlighted. 6. Press the VOL UP key and the device will start a normal reboot. If after step number 4, the flash boot screen does not come up, service/repair/replacement is your next step.
@@ArthurReming will not work as the phone's bootloader is failed. You have to unlock the bootloader somehow and get into edl mode. The software is encrypted hence you cannot access bootloader. Also the oem was locked so you have to completely flash the device.
Yep this happened to me with one of my Samsung phones flashed stock rom and failed and got stuck and my old Samsung phone never turned on again. Sad. And the same thing happened with my Sony phone too 😒
yep my s7 edge was working nicely and i was just using the phone normally but then the screen turned off and the phone completely restarted and stuck on the galaxy s7 edge i rebooted it but still stuck so then i entered to download mode but there is nothing you can do in it everysingle odin versions was just keep stucking on initializing... after 15 minutes of that then it said set pit file and then failed about creating re partitions failed so i really think the Nand is just gone also in heimdall frontend it also says failed to send data odin so cant even send a command that really sucks! im going to replace the motherboard there is no other way@@buzdi_dop
The flashing light unfortunately remembers me of my old phone that I had that I tried to update because it kept asking (it was a motorola too i think) with that colored circle and it would just shut down after a little while and started blinking or something and then while me having no idea of what it meant, I pretty much believed it was screwed. I had no cable or anything or a computer, so it pretty much just died to me because I had no tools, it kinda died and I left it and bought another phone which I was needing anyway cuz the other one was old anyway. Basically, in your case possibly, you are stuck, on the long way to say it, Qualcomm Emergency Download Mode or EDL for short, it's possible that Android is stuck on a boot loop, probably. Maybe things like maybe system or boot are corrupted, but since it's actually connecting to a recovery app, POSSIBLY it might be soft bricked but flashing just doesn't work because some hardware died? If you can connect it to ADB or something IT MIGHT BE SOFT BRICKED and you could give it to a professional to fix possibly! In android's developer site they have download links to adb and/or fastboot that can help you flash manually, but as I have never used fastboot or adb, pretty much it would be better to check on the internet on how to use. Would be good off trying if you have a cable to put your android device in a pc and if you don't want to waste money on getting another phone. Though I only wrote this for your (and everyone reading's) knowledge and I would rather going with the money wasting way.
Don't know if this will work for this particular phone but try googleing EDL mode or Download mode for your device , u can flash anything from that point on
Your phone is in fastboot mode, so it is supposed to allow you to re-flash firmware So also in EDL too. You should've get MSM tool too But as far as i know, because i focus on MediaTek than Snapdragon much
Bro i have this phone and im commenting through this. That blinking flash means something bad with the board. I had the exact same problem i remember. One youtube comment told to go in bootloader mode and it saved my device. I think your lcd broke during this process. Somehow it is still running without any problem. Really spooky 💀💀
Ok: Random Theory. can you take the phone apart and get the storage out of the phone and somehow hook it up to the computer because the hard drive might actually be ok… Idk if that will work
well its too complex to do that i think and i seriously dont think thats worth it anymore because its already reset and you would need to solder the Nand chip to a usb flash disk
phone is encrypted as the bootloader is locked. You have to use some special applications to get that thing unlocked and working. you can write the data manually but again, the phone data cannot be written as the partition is encrypted
there's a chance the eMMC chip just died, because the same exact thing happened on a nokia lumia 630 that i bought for 2 euros. Also i'm pretty sure that that phone has aome kid of mass storage mode / meta mode / Qualcomm emergency reflash that could in theory makeit work again. What model is it btw?
I know Amazon Fire Tablets have an option to format SD Cards as an expansion of the system itself (can't be used on any other devices). Could that by why your card wouldn't read?
This is nothing. Mi note phones after a failed emmc or bootloader missing will show a linux penguin. I have flashed a bunch of roms and you dont want to see the penguin
looks like some hardware issue, perhaps strobe dead light is a code for defective chip? I mean since the screen is cracked, idk how much physical injury it suffered
retry or give it to a repair shop Ok I'm back now, that blue or white LED it means it has notifications and it's turned on but no sound and the display is just dead
Maybe the recovery partition could be corrupted or the phone itself would have tried to want to brick itself but mostly if I know that flashing light means in the fastboot mode but without any restrictions it is EDL mode or maybe it a soft bricked itself or because you have applied too much pressure on the power button the screen may have just wanted to break are there is some problem with the USB cable audio computer that's why it didn't get fixed you could try replacing the screen and try or go to the Motorola rescue team and then mostly if nothing works then you have to ask Google and recover it by yourself
Probably the nand of the phone was failing thus erroring out when the software tried to flash it because of bad sectors i aint a expert but that happened to my old phone and it was dead
Use a REAL flashing tool. Not that Motorola crap. Flash tools are made for specific CPUs, choose carefully : MTK : use SP flash tool SM (QCOM) : use QFIL SPD : use ResearchDownload
I had a "W200" OverheatingTek phone from my childhood which had a PS1 emulator and shit, and when I tried to make something useful out of it apps started deleting themselves then it bootlooped, then I reflashed it same story, and then it just stopped showing anything (LED only) and the MTK flash tool said that the firmware is made for "NAND" mempry but the phone has "NONE" memory. Fucking "NONE". eMMC is fucked. I also had a friend come in with a Nokia 5, story is just like yours. Bricked itself, tried to fix, and only then the screen cracked and it went into the blinking LED of death.
Im a year later but i have the same problem with my phone. Same brand and model. I tried the same steps as you the only difference is my phone hasn't completely bricked yet. Every time I try to put the phone in a different mode it takes me back to the bootlog screen. Also the rescue thing didn't work for me. It kept saying flash failed. Any tips? From anyone?
Use edl mode as a last resort. I didnt had to face this with my moto g6. In fact in commenting via the same phone. Get a usb cable which can do data, put it in edl mode and download the software manually. Pretty sure there is going to be a video about it.
Maybe check the emmc once. It may happen if the emmc health goes bad and the device can't start as the emmc cant be recognised. If the EDL trick doesnt work then just toss the phone out. There is no need to get data by desoldering the emmc and extracting data out of it
The flashboot may fail if your data cable is dogshit. Maybe there is a process running in your pc which is terminating adb?? Try using another os?? Maybe check the phone's sub board if it takes a constant charge?? Bunch of possibilities for a failed flashboot. I think his process failed because the usb cable he was using disconnected midsession and ruined the partition
I think this might work Try installing a fresh copy of antroyd on it Or I know you don’t have a backup but if you back up another phone and then put that back up on the bricked phone that might just work
Its never easy to see something become more dead when you try to help it. We've all been there
Happened to me when i tried to install lineage os on my s9 plus
I has the OEM unlocking thing on but the bootloader is locked
Happened to me when I tried to fix my laptop by opening it up.
But at least you tried
@@MainAccReborned how tf are USB drivers going to fix a laptop that doesn't even take charge after this lol
Happened to me when. I was in school with my pixel 7 rooted, it started spamming me with android update notifications till I decided to power the whole phone off with force (vol down + pwr) then when it booted back up it was bootlooping so when I got home I decided to flash stock firmware and it hard bricked itself
It’s in EDL (emergency download) mode. It’s like fast boot but without the restrictions. You can try to reflash it again.
It's in EDL mode. The flashing white light is EDL mode. EDL mode is basically fastboot WITHOUT any restrictions.
yeah that thing happened to me once ahah
in my phone i just have to flash the preloader (firmware) in brom mode (mediatek)
Can you install Windows Phone when its in this mode?
@@MicrosoftXbox360-jw6oo ye
and how do i get into it (dont ask why)
Haven't worked much with motorola phones but seeing this is a Qualcomm chip phone, the flashing lights mean that its in EDL mode. You could probably confirm it in Device manager under "Ports".
You might be able to rescue the phone if you find a firmware you can flash in EDL mode, you will need a tool like QFIL (Qualcomm Flash Image Loader)
Nope, nand chip is fucked
Yeah NAND integrity has failed. Like as he said, the phone was working perfectly when he placed It in the drawer and 2 weeks later, Startup Failure, also its been 1 year now, he just threw the phone away probably, also even if he saved it the screen turned White meaning the screen also burned out in its last seconds of life. This phone may have suffered either an electrical Failure or the components used to make It where super low quality.
In oneplus 6 phones, it shows like qualcomm dump crash and a bunch of verbose. My friend had that issue and reballing the nand fixed the issue. Somehow i also have the same phone 😂😂
@furhad You are right, attempting write stuff in the already Broken NAND may have also corrupted the processor firmware making this happen.
I had an old Moto G that also died suddenly and it was because of the eMMC reaching the end of its life. The bootloader screen was pretty much like this one and nothing could be flashed successfully, no matter how much I tried. The only difference was that *sometimes* it would boot randomly and work shortly, but then it would crash and return to the bootloader.
I actually had the same problem too that I was still learning about phones and etc; if I remember, my phone would out of nowhere just start blinking with the little dot and I would never know that it's fully bricked up to now. I never had a cable or anything to fix it, so I was kinda screwed and got a new phone (RIP saved money (no I'm not in the US))
Whoa holy crap I had a Moto G die the same way! I was in a bit of a bind because I tried to buy a flagship phone afterwards, but my bank needed to confirm my identity...but I couldn't confirm it with a text or call because my phone was dead lol.
The reflash bricked it. a unfinished reflash can fully brick a device, because the EMMC storage chip is now limbo dead
One thing I've learned from rooting and custom ROMs is you never want to exit the bootloader if it fails while flashing.
It has gone in edl mode but blinks because it doesnt show the display like it shows in oneplus 6 phones as "qualcomm crash dump". My friend had that issue and reballing fixed it
3:18 memories... damn the flashback
I think the reason why the phone won't boot anymore is because when you pressed the power button, it applies pressure and then the screen breaks because it was mostly destroyed. My main phone is dumb and likes to brick itself unless I take out and place back in the battery and turn it on without the casing when I drop it, so maybe try replacing the screen or taking out the battery and placing it back in.
edit: Guys leave this 1 year old comment aloneee
I had a Motorola phone before and it bricked itself after being dropped then LCD damaged and being left for a while btw.
@@scrappy_BIRDthere could be corrupted partitions or something due to the failed recovery thingy in the video
@@Tairex777 Probably not.
@@TacoDoesShit I meant more "the recovery thingy could have actually corrupted it" but if that's what you meant ok
@@Tairex777the fact that it failed likely made it worse
4:40 reminds me of the chromebook shutdown screen
Yep, can relate because I used a Chromebook before.
Yea
Well actually, it shines white on a Chromebook, not blue
Instead faster though
It reminds me of mine, before I threw a dice at him with all my force for no reason.
Lol. I also have a stopwatch that have been running for the past three years
the rescue couldn't go to 69%
hello ci
Like count: 31 in turkey
It refused to be funny
It's "bricked" though...
I wonder if the timer is what made the EMMC brick itself
No.
Health of the emmc was degreading ofc it would die then. He probably had no storage left or did a bunch of reading and writing on the device
The moot g6 is old all nand flash will sie no matter how nicely you care for it@Unknown-64209
@@Unknown-64209 yeah, the timer.
It may sound dumb but try to leave the phone plugged in for some time. From a quick google search it is rare but that can fix it and maybe give you a second chance to flash it again.
Just so you know to get the best results use the OEM cable and always use the back USB ports not the ones on the front. From my understanding, if nothing works, the motherboard is done for. You can try researching whether the phone has an emergency flash more (some phone like OnePlus phones have) and try to revive it again but the data was gone from the start as the phone itself was corrupted.
R.I.P stopwatch
I left it plugged in for 45 minutes, nothing
@@JigaTech its either fully bricked or u just need to replace the display, it might sound weird but its quite easy to replace a display. if you're not confident, just watch a video from hugh jefferys or something.
@@JigaTechyes I have the same phone and it can be fixed. When I plugged in the charger it will be blinking because of a component (idk what that is) is shorted out. I just hold down power and vol up but somehow it worked. It happened because I was using a 3rd party charger 😂
basically what I was saying but in more detail lol
apparently phones can build up static electricity which prevents them from working at all, if this is the case then take out the battery and press the power button and hold it for at least 10 seconds, this will get rid of the residual electricity, then put the battery back on and try booting it up.
the LCD Could be interfering with the process, I had an iPhone 5 claim it was Bricked but replacing the screen and front camera revived it
Guys EDL (Emergency Download Mode) will not work, the NAND integrity has failed. He said in the video that it still worked when he put it in a drawer and 2 weeks later. It bricked itself. Either the phone was made with very bad quality components or it suffered an electrical failure. Also even if he saved it he could not use it, the screen turned white meaning it burned itself in the last seconds of its lifetime. A year has passed and threw away the device probably.
The phone is bulletproof. I have that phone and idk how many times i have dropped it, it still functions. He definately had no storage on his emmc which ofc bricked his phone
Now the battery is flat and dies when plugged out the charger 😂
if this phone literally just died randomly, i think it might be a broken flash chip and there is literally no way to rescue it
also that flashing light is probably EDL (emergency download) mode, as that failed fastboot flash probably completely screwed up all partitions on the phone
I have the same phone and i had my bootloader unlocked. I once bricked the phone but using qcom and flashing the stock image, it was fine
1:22 truly a talking tom moment
where talking tom
take it to a local repair shop so they can fix the screen and make the phone usable again
It looks like it's in some sort of DFU Mode I usually get out of these clunky modes by holding power and volume up while plugged in, power and volume down while plugged in, power and volume up and volume down while plugged in, power and volume up while unplugged, power and volume down while unplugged, power and volume up and volume down while unplugged (all of these methods have to have the buttons being held for at least 1 minute/(or until something happens) it's what I have to do when I brick old phones and if that does nothing it's completely dead and belongs in the bin or sits on a shelf gathering dust as a useless novelty or whatever or in a box to dig up 6 months later and try again but somehow make it worse (I have about 50 phones dumb phones smart phones and brick phones)
go to a professional chip reballer and get the NAND chip removed, solder it onto a USB drive's NAND flash location and plug it in, u will get access to all ur data
he formatted it
rip stopwatch
@@Enter_D1sc bruh ik but when i wrote that comment i must have been half asleep 😂
Repairing price 🙁
@@furry541 oof! i wouldn't pay 2k to get that fixed
@@Jimiscool88 exactly
0:23 thats exactly what my A10E looks like right now
The 3ds eshop sound effect gave me the nistolgic effect
"a stopwatch of 20000 hours" ☠️
1:16 bro empty ur drives
Ikr his ssd will also die soon lol
That moto surely died bcuz it had no storage
randomly found this in my recommended. made me interested in this and made me sub
the phone, just fried itself
Phone is not dead. During fastboot flash the whole system was formatted. Use MTK Preloader mode to flash system, there are literally tons of info out there. As far as I know, you must remove the battery, hold the power button and connect the phone to PC for the phone to enter Preloader Download mode, from where you can use any MTK flash software compatible with it to load the firmware. The phone should automatically power off after a few seconds it enters Preloader mode if not software triggers flash mode.
It is not in brom mode it is in qcom mode. Just seeing in device manager, it will show all the ports.
Qcom port like com 5 or smth idk. I had the same phone (moto g6) and it still works but the battery is flat and i also once bricked it and reflashed using qcom
I suspected this phone is powered by MTK. In case it is a Qualcomm, it should be detected as QHSUSB_DLOAD in Device Manager with appropriate Qualcomm USB drivers.
Try these steps and see if it will work. Please do these steps while your phone is connected to the original Motorola charger that came with the phone, plugged directly to a wall outlet.
1. Please press and hold the VOL DOWN key.
2. While still holding the VOL DOWN key, press and hold the POWER key.
3. Hold both keys down for over 120 seconds. This is more than 2 minutes and will seem like a long time, it will help to time this to ensure you hold the keys long enough.
4. After holding the keys down for more than two minutes, release them.
5. The Flash Boot screen will display, and the Normal Reboot option will be highlighted.
6. Press the VOL UP key and the device will start a normal reboot.
If after step number 4, the flash boot screen does not come up, service/repair/replacement is your next step.
@@rockpie.iso.tar.bz2 to be honest I just copied and pasted it
@@ArthurReming will not work as the phone's bootloader is failed. You have to unlock the bootloader somehow and get into edl mode. The software is encrypted hence you cannot access bootloader. Also the oem was locked so you have to completely flash the device.
Gg for the stopwatch :(
I almost cried at the end
probably the bios corrupted and that restart made it hard bricked.
The phone seems to be in EDL mode, so there's a chance that it could be fixed
@@AngelCastillo029 how did you find this practically dead comment
@@thisisbup by checking the comments section obviously
@@AngelCastillo029 nand chip is probably cooked
@@hatsumi_rou_ yeah probably
Yep this happened to me with one of my Samsung phones flashed stock rom and failed and got stuck and my old Samsung phone never turned on again. Sad.
And the same thing happened with my Sony phone too 😒
Broken nand, after flashing it gets even more broken
yep my s7 edge was working nicely and i was just using the phone normally but then the screen turned off and the phone completely restarted and stuck on the galaxy s7 edge i rebooted it but still stuck so then i entered to download mode but there is nothing you can do in it everysingle odin versions was just keep stucking on initializing... after 15 minutes of that then it said set pit file and then failed about creating re partitions failed so i really think the Nand is just gone also in heimdall frontend it also says failed to send data odin so cant even send a command that really sucks! im going to replace the motherboard there is no other way@@buzdi_dop
The phone was in EDL mode btw. You have to use Qcom flash tool to reciver from it(considering the emmc on the phone is not cooked)
Emmc is surely cooked. My phone also was once bricked while flashing custom rom, only blinking. I saw qcom port and i reflashed and it still works
4:58 it is in qcom as he plugged the device in, it made the hardware insert sound.
@@Unknown-64209 yes correct
we are waiting for another video on this. its in EDL mode
Because nand health is done for. See "qualcomm crash dump mode" on oneplus devices and basically it is the same thing for oneplus devices too
The flashing light unfortunately remembers me of my old phone that I had that I tried to update because it kept asking (it was a motorola too i think) with that colored circle and it would just shut down after a little while and started blinking or something and then while me having no idea of what it meant, I pretty much believed it was screwed. I had no cable or anything or a computer, so it pretty much just died to me because I had no tools, it kinda died and I left it and bought another phone which I was needing anyway cuz the other one was old anyway. Basically, in your case possibly, you are stuck, on the long way to say it, Qualcomm Emergency Download Mode or EDL for short, it's possible that Android is stuck on a boot loop, probably. Maybe things like maybe system or boot are corrupted, but since it's actually connecting to a recovery app, POSSIBLY it might be soft bricked but flashing just doesn't work because some hardware died? If you can connect it to ADB or something IT MIGHT BE SOFT BRICKED and you could give it to a professional to fix possibly! In android's developer site they have download links to adb and/or fastboot that can help you flash manually, but as I have never used fastboot or adb, pretty much it would be better to check on the internet on how to use. Would be good off trying if you have a cable to put your android device in a pc and if you don't want to waste money on getting another phone. Though I only wrote this for your (and everyone reading's) knowledge and I would rather going with the money wasting way.
Phone: I am bricked
Jiga: *tries to rescue the phone*
Phone: I am dead *flashes white light*
😂😂🤣🤣
That is the Sign Of Life indicator, you just have to try flash again.
there could be a way to enter some sort of META mode to flash the phone even without the bootloader working properly
it was in EDL which is does what you said
RIP insane stopwatch
Moral of the story: never set up a 20,000 hour timer
I done it-
My old Samsung phone was running stopwatch till 2016 and now i cant find the phone
Don't know if this will work for this particular phone but try googleing EDL mode or Download mode for your device , u can flash anything from that point on
Bring it to a expert technician they will fix it chances are low but if they do they will charge alot of money and it consume a lo of time too
My dumbass really thought it was “BRICKED”
bro 2 years of stopwatch
Your phone is in fastboot mode, so it is supposed to allow you to re-flash firmware
So also in EDL too. You should've get MSM tool too
But as far as i know, because i focus on MediaTek than Snapdragon much
Bro i have this phone and im commenting through this. That blinking flash means something bad with the board. I had the exact same problem i remember. One youtube comment told to go in bootloader mode and it saved my device. I think your lcd broke during this process. Somehow it is still running without any problem. Really spooky 💀💀
First replace the LCD screen, then you have to put it into recovery mode. Then flash it
Emmc is cooked
I have a stopwatch on my phone too, that has been going on for 3 thousand hours
Ok: Random Theory. can you take the phone apart and get the storage out of the phone and somehow hook it up to the computer because the hard drive might actually be ok… Idk if that will work
well its too complex to do that i think and i seriously dont think thats worth it anymore because its already reset and you would need to solder the Nand chip to a usb flash disk
phone is encrypted as the bootloader is locked. You have to use some special applications to get that thing unlocked and working. you can write the data manually but again, the phone data cannot be written as the partition is encrypted
Can we fix it?
No, Its fucked
its bricked up
oh cool! my tablet also hit 20,000 hours just recently about 3-5 days ago!
Sorry For Your Loss.
thank you so much for helping me! I was searching everywhere! This helped me so much.
Bricked is wild
U can recover swapping the nand or motherboard from a donor board
"The phones droid soul ascends" 4:40
さようならモトローラ、閉じ込められて安らかに眠ってください 💀👍🏻
there's a chance the eMMC chip just died, because the same exact thing happened on a nokia lumia 630 that i bought for 2 euros. Also i'm pretty sure that that phone has aome kid of mass storage mode / meta mode / Qualcomm emergency reflash that could in theory makeit work again. What model is it btw?
I have the same phone. Moto g⁶
i have lumia 640 lte but it wasnt bricked it was frp locked and was hard to remove lock
I wonder if the phone has been exposed to water, or has been dropped.
I dropped the phone like 2 days after I got it and that's how it cracked, no water damage from what I can remember tho
@@JigaTech I think it just self-destructived 😂. That last screen it showed, really seemed like water damage...
Well I mean, it only happened after the flash failed, I think it straight up corrupted the firmware
@@UltimateSayori yes the bootloader was probably erased but flash tool couldn't flash the new one so there is no bootloader now
@@JigaTech u dropped it 2 days after you got it? Be more careful with Technology man....
"He's dead jim."
what model is the phone?
Moto G5 Plus
@@prapakornlakornpol7221you can try to rescue it with Fastboot
@@prapakornlakornpol7221it's a g6
moto g6
It’s Easier Just If If Its In EDL Mode Just Wait Till The battery Is 0% And Charge It And It’s Out Of EDL Mode
I know Amazon Fire Tablets have an option to format SD Cards as an expansion of the system itself (can't be used on any other devices). Could that by why your card wouldn't read?
Wow well I didn’t know phones can get bricked, lol.
This is nothing. Mi note phones after a failed emmc or bootloader missing will show a linux penguin. I have flashed a bunch of roms and you dont want to see the penguin
looks like some hardware issue, perhaps strobe dead light is a code for defective chip?
I mean since the screen is cracked, idk how much physical injury it suffered
retry or give it to a repair shop
Ok I'm back now, that blue or white LED it means it has notifications and it's turned on but no sound and the display is just dead
Bruh you making the phone more dead 💀that not seems a perfect tool
Maybe the recovery partition could be corrupted or the phone itself would have tried to want to brick itself but mostly if I know that flashing light means in the fastboot mode but without any restrictions it is EDL mode or maybe it a soft bricked itself or because you have applied too much pressure on the power button the screen may have just wanted to break are there is some problem with the USB cable audio computer that's why it didn't get fixed you could try replacing the screen and try or go to the Motorola rescue team and then mostly if nothing works then you have to ask Google and recover it by yourself
I had a stopwatch on my chromebook going for 1 year but I reset my chromebook so I lost it =(
Stop this obsession with the number 69
it´s an hardware failure, probably the nand or ram.
How have you managed to break or brick this software so much?
I DONT KNOW
@@JigaTechIt's so bricked
Probably the nand of the phone was failing thus erroring out when the software tried to flash it because of bad sectors i aint a expert but that happened to my old phone and it was dead
Maybe u could give it to that one phone fixer
The phone won’t boot because if you update or restore and it fail it fully bricks if it’s already broken
IT IS IN EDL MODE ITS BASICALLY FASTBOOT AND NO RESTRICTIONS
3:45 bro forgor💀
fun fact: they bricked my lenovo amd laptop cause of using linux
This video is how I found him…
It Happen To Me 1 Time And Waited Till It Was 0% Of Battery And Charge The Battery
Bro went kamikaze mode 💀
Use a REAL flashing tool. Not that Motorola crap. Flash tools are made for specific CPUs, choose carefully :
MTK : use SP flash tool
SM (QCOM) : use QFIL
SPD : use ResearchDownload
I had a "W200" OverheatingTek phone from my childhood which had a PS1 emulator and shit, and when I tried to make something useful out of it apps started deleting themselves then it bootlooped, then I reflashed it same story, and then it just stopped showing anything (LED only) and the MTK flash tool said that the firmware is made for "NAND" mempry but the phone has "NONE" memory. Fucking "NONE". eMMC is fucked.
I also had a friend come in with a Nokia 5, story is just like yours. Bricked itself, tried to fix, and only then the screen cracked and it went into the blinking LED of death.
5:21 Linux 🐧 Movement
Im a year later but i have the same problem with my phone. Same brand and model. I tried the same steps as you the only difference is my phone hasn't completely bricked yet. Every time I try to put the phone in a different mode it takes me back to the bootlog screen. Also the rescue thing didn't work for me. It kept saying flash failed. Any tips? From anyone?
Use edl mode as a last resort. I didnt had to face this with my moto g6. In fact in commenting via the same phone. Get a usb cable which can do data, put it in edl mode and download the software manually. Pretty sure there is going to be a video about it.
Maybe check the emmc once. It may happen if the emmc health goes bad and the device can't start as the emmc cant be recognised.
If the EDL trick doesnt work then just toss the phone out. There is no need to get data by desoldering the emmc and extracting data out of it
The flashboot may fail if your data cable is dogshit. Maybe there is a process running in your pc which is terminating adb?? Try using another os??
Maybe check the phone's sub board if it takes a constant charge??
Bunch of possibilities for a failed flashboot. I think his process failed because the usb cable he was using disconnected midsession and ruined the partition
Rip phone.
Ur phone is EDL enabled EDL stands for Emergency Download Mode
Bad eemc flash or nand flash.
oh yea I have 2 of those. good phone.
I think this might work
Try installing a fresh copy of antroyd on it
Or I know you don’t have a backup but if you back up another phone and then put that back up on the bricked phone that might just work
I bricked my old phone 5 times while changing the android version and i just fixed with the Odin app.
RIP phone :(
i think the emmc is dead mate
nope its not you can recover it
bri'ish mafe
@@LazyPerson18 :facepalm:
@@windowsquest Probably not. With a quick look at the phone you can tell that some of it is physically damaged. EMMC is probably damaged also.
Model?
Moto G6
I thing that you can rescue it by switching IMEI and motherboard or just try to boot of an SD card
I think its Nand issue. not the software
My stopwatch is in: 2011:33:59
I have moto g6 and my time is 7010 hrs
you phone needs a need hard drive
Phones dont take hard drives
r.i.p ur old phone
i've had that bricking 2 times and lost my data but now it working
From what I know, the blinking light means the battery is dead AF, maybe the port is dead.
happens in moto phones. it can also indicate a serious system problem/hardware problem