Database Info

Did I hard brick?

Okay so I tried searching everywhere for a solution and I didn't find anything.
So this is what happened, I was on ICS leak 4.0.4 ICS.672.1.13.en.03 then I tried to Fxz to AT&T 2.3.5 InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID28 5.zip and it got stuck at 5/20 saying "Rebooting bootloader" the screen stayed black for a long time, so I clicked close and this is where all this happened. My phone doesn't turn on, not even Fastboot, when I plug it into the charger it doesn't do anything, but when I plug it into my laptop without battery the white led turns on but still it doesn't do anything, the laptop doesn't detect anything and when I press the buttons it doesn't react nor do anything. I don't know anymore what to do, I bought this overseas so I have no warranty and it's not an AT&T phone. If anyone went through this, I really don't know what to do.. I know it's not softbrick as I can see it. I'll be very thankful if there is a solution, but my hopes are really down..
I know I read all the guides, it said "Don't pull battery or unplug. So I didn't unplug or remove battery, I just clicked close. I really didn't know this could happend. Didn't see it in any thread or post that you can't Fxz from 4.0.4 to AT&T 2.3.5, I only followed the steps from this thread: http://forum.xda-developers.com/showthread.php?t=1779968
I don't want this to happen to anyone.

Wrong thread! sorry... check your PMs darkmixta!

I made the same mistake
darkmixta said:
Okay so I tried searching everywhere for a solution and I didn't find anything.
So this is what happened, I was on ICS leak 4.0.4 ICS.672.1.13.en.03 then I tried to Fxz to AT&T 2.3.5 InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID28 5.zip and it got stuck at 5/20 saying "Rebooting bootloader" the screen stayed black for a long time, so I clicked close and this is where all this happened. My phone doesn't turn on, not even Fastboot, when I plug it into the charger it doesn't do anything, but when I plug it into my laptop without battery the white led turns on but still it doesn't do anything, the laptop doesn't detect anything and when I press the buttons it doesn't react nor do anything. I don't know anymore what to do, I bought this overseas so I have no warranty and it's not an AT&T phone. If anyone went through this, I really don't know what to do.. I know it's not softbrick as I can see it. I'll be very thankful if there is a solution, but my hopes are really down..
I know I read all the guides, it said "Don't pull battery or unplug. So I didn't unplug or remove battery, I just clicked close. I really didn't know this could happend. Didn't see it in any thread or post that you can't Fxz from 4.0.4 to AT&T 2.3.5, I only followed the steps from this thread: http://forum.xda-developers.com/showthread.php?t=1779968
I don't want this to happen to anyone.
Click to expand...
Click to collapse
I made the same mistake, any way to repair my phone? Thanks a lot...

maqndon said:
I made the same mistake, any way to repair my phone? Thanks a lot...
Click to expand...
Click to collapse
THIS IS THE CORRECT WAY TO FXZ BACK FROM ICS:
http://forum.xda-developers.com/showthread.php?t=1805975
You are totally bricked, no way out, sorry, you need a new phone.

jimbridgman said:
THIS IS THE CORRECT WAY TO FXZ BACK FROM ICS:
http://forum.xda-developers.com/showthread.php?t=1805975
You are totally bricked, no way out, sorry, you need a new phone.
Click to expand...
Click to collapse
I was thinking about Motorola factory cable, if it would do something?
I read in some thread that it forces Motorola to go in fastboot mode http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
What's very interesting is that the phone definitely knows that it is not in the presence of mere mortals when you use a Factory Cable. The phone knows it is in the presence of Moto gods as it boot differently than normal. Some phones like the Motorola Napoleon actually come right out and say "Factory Cable Connected". Other phones will boot straight to the bootloader for flashing. The various Droids appear to boot normally until you notice that there is no USB connected indicator at the top (once the OS is up) and that the host computer doesn't register all the usual devices. Instead the host computer only registers the bare minimum interfaces needed for RadioComm, RSD Lite, etc. to be able to talk to the phone. This in and of itself simplifies things as you don't have to monkey with setting the phone to the right mode (e.g. "PC Mode") -- it is automatically in the right mode for flashing.
Another interesting thing that is allegedly possible with the Factory Cable is that with the battery removed, it is possible to access some diagnostic pads on the main board of the phone, that when shorted (before connecting the Factory Cable) will boot the phone in a special recovery mode to help recover bricked phones. I say "allegedly" because thus far we've not had much luck with this, and our information is that it may only apply to unsecured phones anyway -- not secured consumer phones. Running around shorting things randomly inside your phone is a very bad idea unless you are willing to risk the phone, your computer, or both -- but sometimes things must die in the name of science -- but again I digress.
Click to expand...
Click to collapse

Factory Cable
I made this cable yesterday and nothing... when i connect the phone into PC the white light turn on for less than a second then turn off. The PC don't recognize the phone in Linux neither Windows.
I believe that i made the cable right but i'm not a 100% sure.

white led is also an indication battery out of power. Do try connecting wall charger for a while and see if that brings up the power.

The bootloader is what controls the phone at this level. If the bootloader is corrupted the phone is hard bricked and the only way to fix it would be to jtag flash a working bootloader.

jboxer said:
The bootloader is what controls the phone at this level. If the bootloader is corrupted the phone is hard bricked and the only way to fix it would be to jtag flash a working bootloader.
Click to expand...
Click to collapse
But how is the bootloader corrupted if it was stuck at rebooting bootloader? Motorola got a very strange flashing thing...

darkmixta said:
But how is the bootloader corrupted if it was stuck at rebooting bootloader? Motorola got a very strange flashing thing...
Click to expand...
Click to collapse
Your bootloader is not corrupted, you hard bricked because you tried to flash a bootloader that is a lower version. There is code in the BL to not allow that, that is one of a few things that will actually brick this phone.

jimbridgman said:
Your bootloader is not corrupted, you hard bricked because you tried to flash a bootloader that is a lower version. There is code in the BL to not allow that, that is one of a few things that will actually brick this phone.
Click to expand...
Click to collapse
If the phone still has the new bootloader and it is not corrupted then why are these phones hard bricked? The Android boot sequence starts with the bootloader when the power key is pressed. During the bootloader process it initilaizes the hardware using init.rc and init.<machine_name>.rc and then it looks for keys being pressed to run fastboot, recovery, etc and in the absence of that will attempt to boot up the Android system. So did RSD wipe the kernel and then when it got stuck on the flashing the downgraded bootloader (many phones don't allow this) was the kernel not reflashed yet? Or is there no init.rc and init.<machine_name>.rc for the bootloader to initiize the hardware? If the phone still has a valid bootloader, kernel and init files it should boot so that fastboot can be run. What got wiped that is preventing the phone from booting? When hard bricked phones are resurrected with a jtag flash often it is just a valid bootloader or bootloader and kernel that are flashed that allow the phone to be booted into fastboot or recovery so a valid rom can be flashed.The bootloader is also what handles charging the phone when you charge a phone that has been turned off, so if a valid bootloader and kernel are present when you plug in the charger you should see the charging sequence. Just curious what got so messed up that the bootloader is not even booting to a point where fastboot can be run and the phone doesn't respond to a charger.

jboxer said:
If the phone still has the new bootloader and it is not corrupted then why are these phones hard bricked? The Android boot sequence starts with the bootloader when the power key is pressed. During the bootloader process it initilaizes the hardware using init.rc and init.<machine_name>.rc and then it looks for keys being pressed to run fastboot, recovery, etc and in the absence of that will attempt to boot up the Android system. So did RSD wipe the kernel and then when it got stuck on the flashing the downgraded bootloader (many phones don't allow this) was the kernel not reflashed yet? Or is there no init.rc and init.<machine_name>.rc for the bootloader to initiize the hardware? If the phone still has a valid bootloader, kernel and init files it should boot so that fastboot can be run. What got wiped that is preventing the phone from booting? When hard bricked phones are resurrected with a jtag flash often it is just a valid bootloader or bootloader and kernel that are flashed that allow the phone to be booted into fastboot or recovery so a valid rom can be flashed.The bootloader is also what handles charging the phone when you charge a phone that has been turned off, so if a valid bootloader and kernel are present when you plug in the charger you should see the charging sequence. Just curious what got so messed up that the bootloader is not even booting to a point where fastboot can be run and the phone doesn't respond to a charger.
Click to expand...
Click to collapse
This is similar to what has been done here with our phone:
http://www.xda-developers.com/android/motorola-at-it-again-locks-down-atrix-4g-even-more/
It is just like the atrix 4G situation.
What Moto has done with the A0.72 bootloader is that it will not allow you to flash back to the A0.65 bootloader once the A0.72 has been flashed to the device. What it does is blows one of the 3 efuses that allows the phone to boot to the mbmloader (moto's bootloader loader).
That is why we now have a modified fxz that will flash all of the fxz minus the bootloder. So you will be on GB, but still have the latest BL A0.72.
Moto has 3 layers of the bootloader itself and all 3 are signed with the same root CA, the very last one is the one that actually loads the kernel, and the issue with these bricks is that the 2nd layer of the bootloader mbmloader that is what these people that have bricked after flashing, was the mbmloader that allowed you to "load"/flash the mbm.bin for A0.65 and that tripped the efuse that turns the 1st layer BL off, so no charging either.
Moto seems to have gotten real nasty to to us Devs as of late, and why most of us in here are saying this will be our last MOTO phone.
P.S. so far even JTAG has not been ale to resurrect some of these bricks. I was at an AT&T repair facility the other day (yes I have full access to the back area) and we played with one of the reported ICS leak bricked phones and it would not even see that the phone was connected to the JTAG box. There was another phone that was also a "hard brick" that was not from the same leak that was a GB phone and it connected right up to the JTAG box without issue.

jimbridgman said:
This is similar to what has been done here with our phone:
http://www.xda-developers.com/android/motorola-at-it-again-locks-down-atrix-4g-even-more/
It is just like the atrix 4G situation.
What Moto has done with the A0.72 bootloader is that it will not allow you to flash back to the A0.65 bootloader once the A0.72 has been flashed to the device. What it does is blows one of the 3 efuses that allows the phone to boot to the mbmloader (moto's bootloader loader).
That is why we now have a modified fxz that will flash all of the fxz minus the bootloder. So you will be on GB, but still have the latest BL A0.72.
Moto has 3 layers of the bootloader itself and all 3 are signed with the same root CA, the very last one is the one that actually loads the kernel, and the issue with these bricks is that the 2nd layer of the bootloader mbmloader that was these people that have bricked with was the mbmloader that allowed you to "load"/flash the mbm.bin for A0.65 and that tripped the efuse that turns the 1st layer BL off, so no charging either.
Moto seems to have gotten real nasty to to us Devs as of late, and why most of us in here are saying this will be our last MOTO phone.
P.S. so far even JTAG has not been ale to resurrect some of these bricks. I was at an AT&T repair facility the other day (yes I have full access to the back area) and we played with one of the reported ICS leak bricked phones and it would not even see that the phone was connected to the JTAG box. There was another phone that was also a "hard brick" that was not from the same leak that was a GB phone and it connected right up to the JTAG box without issue.
Click to expand...
Click to collapse
That's definitely a strange situation. Jtag talks directly to the cpu and the nand flash so no matter how hard the phone is bricked it should be able to be accessed via jtag. I guess the moto efuses are operating at a very low level? Kind of crappy to put that in there that renders a device unusable. People are going to run out of phones to buy. On the LG-P999 forum many people swore off LG due to lack of updates and not being able to get hardware drivers from LG or Nvidia. At least with the Nvidia chip the P999 is virtually unbrickable as recovery and bootloader can be flashed at a very low level using Nvidia tools (bootloader is not even run to flash at this level). Phones that get the most updates are Nexus branded phones but I personally will never buy a Samsung device again. They have bad hardware code in their EMMC chips and there is a rash of Nexus S devices bricking themselves during an OTA flash or factory reset when the EMMC is issued an erase command. The bad code corrupts the EMMC during the erase and renders the device bricked beyond any repair. It only happens sometimes and when it does Samsung cannot even flash them again. So I guess that just leaves HTC. Now that Google owns Motorola future Moto models may become Nexus devices. I personally prefer Moto phones but I have not hard bricked mine yet. Since I bought it second hand and am in Thailand I have been very cautious and have done very little modding to it and decided to wait (thankfully) for the official OTA release. I almost flashed the leak and glad I waited. Thanks for the explanation as to why they are perma-bricked.

This is exactly happened to my phone.
I was up on the first ICS leak, rooted and everything working great! I tried installer a font and it rebooted as normal but then stalled at the "Rethink Possible" screen. After pulling the battery and starting all over, I attempted to start the ICS process again, starting with going back to 2.3.5 (Yes, this is where I went wrong!)
The darn thing is literally a brick right now.
I wish I would have left it alone....

MACKSnare519 said:
This is exactly happened to my phone.
I was up on the first ICS leak, rooted and everything working great! I tried installer a font and it rebooted as normal but then stalled at the "Rethink Possible" screen. After pulling the battery and starting all over, I attempted to start the ICS process again, starting with going back to 2.3.5 (Yes, this is where I went wrong!)
The darn thing is literally a brick right now.
I wish I would have left it alone....
Click to expand...
Click to collapse
Yes, you hard bricked it and there is nothing you can do to fix it. There were many warning about this posted with the leak and in other threads. Sorry to hear that you killed your phone. :crying:

Technically, if you were on the FIRST leak, you should be able to fxz back.
Sent from my SAMSUNG-SGH-I727 using xda premium

Fall of Enosis said:
Technically, if you were on the FIRST leak, you should be able to fxz back.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Yea, but he would have had to read the forums and fxz back using the custom script to prevent downgrading the baseband and bricking.

[Q] Hard Bricked LG G3.

The issue with my phone.
I can't get into Download mode, computer won't pick it up and non of the buttons work. So I can't just flash a new rom.
It happened when I was trying to install This(I was being stupid and didn't look at the device.) So is there a way to fix it?
Things I tried and have
I have tried ADB, and fast boot they all get stuck waiting for the device (on every port).
I have the laf file. BUT here is the main issue my computer won't pick it up rendering the laf file useless.
I have looked on the forums and all methods purposed. Were for 32 bit computers or didn't work.
Signs of Life (Update One)
It just showed signs of life. It was dead so I charged it and the LED was flashing red and it charged now it is back to black screen and now sign of life though. I tried ADB on my tablet (didn't work) so I know the ADB issue might be my computer. That is good news because it means there is a chance of fixing it.
I am going to try to use ADB on my other computer to see if that works. If it does then there may be a chance of fixing it.

voxoph said:
The issue with my phone.
I can't get into Download mode, computer won't pick it up and non of the buttons work. So I can't just flash a new rom.
It happened when I was trying to install This(I was being stupid and didn't look at the device.) So is there a way to fix it?
Things I tried and have
I have tried ADB, and fast boot they all get stuck waiting for the device (on every port).
I have the laf file. BUT here is the main issue my computer won't pick it up rendering the laf file useless.
I have looked on the forums and all methods purposed. Were for 32 bit computers or didn't work.
Signs of Life (Update One)
It just showed signs of life. It was dead so I charged it and the LED was flashing red and it charged now it is back to black screen and now sign of life though. I tried ADB on my tablet (didn't work) so I know the ADB issue might be my computer. That is good news because it means there is a chance of fixing it.
I am going to try to use ADB on my other computer to see if that works. If it does then there may be a chance of fixing it.
Click to expand...
Click to collapse
I looked into the zip that you tried to flash, and it looks like it flashed the mmcblk0p5 partition, which on the G3 is aboot (and I believe is why even download mode is broken). You can get a clean aboot.img from the thread here (http://forum.xda-developers.com/att-lg-g3/development/rom-lg-d850-20f-lollipop-5-0-1-extras-t3052041) , but you will have to have some way to flash it. Are you able to get into anything at all on the phone itself, recovery even?
@southern87 : maybe you can provide some insight. I remember in the Lounge a while back you had a broken aboot. Where you ever able to get back to download mode or some other way to repair aboot?

cmulk said:
I looked into the zip that you tried to flash, and it looks like it flashed the mmcblk0p5 partition, which on the G3 is aboot (and I believe is why even download mode is broken). You can get a clean aboot.img from the thread here (http://forum.xda-developers.com/att-lg-g3/development/rom-lg-d850-20f-lollipop-5-0-1-extras-t3052041) , but you will have to have some way to flash it. Are you able to get into anything at all on the phone itself, recovery even?
@southern87 : maybe you can provide some insight. I remember in the Lounge a while back you had a broken aboot. Where you ever able to get back to download mode or some other way to repair aboot?
Click to expand...
Click to collapse
Thanks for responding. I am going to try ADB again but I can't get into recovery mode at the time being.

A similar thing just happened to me, except I got right out of it. Device was completely unresponsive, no download mode, adb nothing, indicative of a hard brick. Scared the **** out of me as I've had it less than 6 hours... Started holding buttons, and it came to life after ~1 minute of power button + volume down. Related? Well maybe not, thought I'd post it here. (TWRP 2.8.5 + Rooted CM12)

True Hard Brick, No OS!
Well I really did it this time. F*cked up big time. Wiped everything on phone, all I have is TWRP which is useless. Nothing. No bootloader, no sideloader, NO files! Guess I'll try to get into download mode.
Anyone have any ideas? Would be greatfull for any help.

TSF14 said:
Well I really did it this time. F*cked up big time. Wiped everything on phone, all I have is TWRP which is useless. Nothing. No bootloader, no sideloader, NO files! Guess I'll try to get into download mode.
Anyone have any ideas? Would be greatfull for any help.
Click to expand...
Click to collapse
Follow the TOT method.
http://forum.xda-developers.com/showthread.php?t=2785089

hyelton said:
Follow the TOT method.
http://forum.xda-developers.com/showthread.php?t=2785089
Click to expand...
Click to collapse
Thanks hyelton, I don't even have download mode. Nothing, zero, (no).zip, zilch, nada. Guess I'll run it up to the AT&T Corporate store & see how much $s they'll charge to put it back to stock.

TSF14 said:
Thanks hyelton, I don't even have download mode. Nothing, zero, (no).zip, zilch, nada. Guess I'll run it up to the AT&T Corporate store & see how much $s they'll charge to put it back to stock.
Click to expand...
Click to collapse
They don't put it bAck to stock.. They either will tell you no as you voided warranty or it will be sent off for warranty. They don't flash in store.
You have to have download mode to flash.
So your plugging your phone inTo a non USB 3.0 plug using the OEM LG cable while holding volup and then plugging in the USB cable?

hyelton said:
They don't put it bAck to stock.. They either will tell you no as you voided warranty or it will be sent off for warranty. They don't flash in store.
You have to have download mode to flash.
So your plugging your phone inTo a non USB 3.0 CCCC?
Click to expand...
Click to collapse
Yes, AT&T said they would replace it for $199.00. Screw that. they gave me the phone # for LG, I will call them & see how much they charge to reinstall the OS. Yes, plugging into 2.0 usb while holding vol up with phone off. No sign of life.

TSF14 said:
Yes, AT&T said they would replace it for $199.00. Screw that. they gave me the phone # for LG, I will call them & see how much they charge to reinstall the OS. Yes, plugging into 2.0 usb while holding vol up with phone off. No sign of life.
Click to expand...
Click to collapse
Are you sure your battery is not dead??

hyelton said:
Are you sure your battery is not dead??
Click to expand...
Click to collapse
Yes, if only it was that easy.

There are a few things you can try :
1.) Press the Powerbutton for a longer time
If you have a responce like the LG Logo or something like that, you might want to try and plug it to the computer and use the managing software
with which you can emergency reinstall the firmware.
2.) Press Power + Volume Down
If it restarts into the recovery menu, try to find a way to load a flashable stock rom of your handy onto the memory of your phone in order to "reflash" it.
(I don't know how you can do that )
3.) Go to the shop where you bought it and explain your problem, since rooting a LG device is not really easy to detect the chances that your warranty will cover for it are pretty high.
Sent from my LG-D955 using XDA Free mobile app

http://forum.xda-developers.com/spr...y-download-t3053985/post60106965#post60106965

Read this.
http://forum.xda-developers.com/att-lg-g3/help/bricked-d850-help-t3064874

[Help] Super Hard Brick - Stuck in EDL and no button response at all + SHA256 fail

Hi everyone,
I'm having an issue with my 7 pro (1911). This is my 1st Oneplus as I used a Mi 5 before, the flash procedure was much easier without this A/B mess.
So I somehow messed up a new install of pixel experience with blu_spark kernel and twrp and found myself with the qualcomm crash error. Trying to get back into fastboot with the button combination (was able to save it once in it) the phone restarts and got stuck in edl mode. I noticed it's recognized as 9008 in the PC so I said okey this is nothing I'll just use the MSMTool to get it back on again.
Went through the xda Mega thead procedure, had no problem getting the phone to connect to the tool, however, first unexpected thing I encounter is the fact it stops with a SHA256 doesn't match error, and fails to send op2.img. I verified the ops file to make sure it has no errors and it was good. I then checked "disable sha256" box and it goes normally with the flash this time. Except in the end instead of restarting into the system it restarts into edl mode again and if the cable is still attached starts flashing again. This loop keeps going on forever.
I checked everywhere the only other thing I found that hints at a possible solution was doing an SMT download (based on this thread from OP6). Having an EFS backup already in one of my TWRP backups I went ahead with the procedure. Everything goes normally with the sha256 box disabled. it takes longer than upgrade mode (it flashes also to b slot), it finishes fine till the end. I disconnect the phone to boot it but it's still stuck in EDL mode!!! pressing any combination of button only keeps restarting the phone in EDL; when connected to the pc you see it going off then on in device manager.
The only idea I have left is waiting for battery to die, which could take forever and I have no idea if that'll work
Things I tried/used :
Qualcomm drivers are the latest from microsoft server v2.1.2.2. Tried some other ones but no change.
Pressing any combination of buttons (up + down + power, up + power, down + power) for multiple minutes doesn't change anything (it only hurts your fingers lol)
Before the issue the phone was at around 40%, I don't think the problem was battery charge, but I still tried connecting to official charger for some time but no boot.
I tried using multiple cables, ports (usb 3 and 2 from front of pc), tried on a laptop with both usb 2 and 3, all give me the same results, sha256 fails, without the check it flashes but no boot or response.
I redownloaded the MSMTool multiple times from both the Mega thread and newer one with oos 10 images, even the chinese image, all of them give the exact same issue. The only one that didn't work was the TMobile image, saying it's the wrong image (tried it just to be sure my phone wasn't originally a TMO converted, as it's 2nd hand).
Tried starting a normal flash in MSMTool and leaving it on that loop (flash, finish, restart again in EDL, flash...) all night but still found it flashing in the morning, never booted to system.
I found some people in the forums having the same symptomes (but quite rare compared to others), only 2 said they found a solution:
OP7P (this guy fixed the issue by charging his phone) https://forum.xda-developers.com/showpost.php?p=80329855&postcount=83
OP6T (this guy discharged his phone completely then connected it and it booted) https://forum.xda-developers.com/showpost.php?p=79079192&postcount=5
OP7 https://forum.xda-developers.com/showpost.php?p=81183765&postcount=41
OP7 https://forum.xda-developers.com/showpost.php?p=81185793&postcount=43
OP6 https://forum.xda-developers.com/showpost.php?p=81308571&postcount=88
OP6 https://forum.xda-developers.com/showpost.php?p=79445923&postcount=203
I'm making this thread maybe someone who had the same issue can show me how he solved it, or if not and my last resort works (complete battery discharge) hopefully stays as a helpful history to someone else.
Thanks.

Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.

Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
EDIT: Sorry for the accidental double post

Charnet3D said:
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
EDIT: Sorry for the accidental double post
Click to expand...
Click to collapse
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.

ANY NEWS>?
i also have an OP6T
used MsmDownloadTool V4.0_factory_mcl_op1_patched
with
rev_OverSeas_181226_1920_release_disable_OTA-BLOCK_Signed_fp1812260627_cve2018-12-01_ufs_9.0.11
and
fajita_41_O.18_181226.ops
phone was stock.
Proceeded to flash custom rom etc.
Now since then i decided i wanted stock again to try new custom rom etc. and,
i booted twrp and just wiped everything like a mad man.
i have had this happen before.
Currently, it will and can boot into any mode such as fastboot recovery(TWRP) edl and device state/secureboot are both unlocked/enabled
TRY TO LET IT DIE AND PUT RUBBERBANDS OLONG THE PHONE SO THE VOLUME AND POWER BUTTONS ARE HELD DOWN GOOD AND LET IT SIT FOR A DAY TO DIE.
After you do that let it sit for a bit and its dead. take off the bands and let it sit for another half a day and redo the bands to make sure its been reset and is indeed complete dead. repeat, whatever.
when its surely dead and been reset, THE ONLY thing you can try is
plug it in and almost at the same time (not simultaneously, but sequentially)
YOU NEED TO HOLD VOLUME UP+DOWN at the same time RIGHT AFTER YOU PLUG IT IN LITTERALLY. And, it should display the 1plus logo briefly and boot into fastboot mode.(i had to do this after wiping rom etc via twrp an became stuck in edl mode)
from there i booted twrp
(was my reccovery still)
mind that i wiped everything like a mad man and i lost my ADB AND FASTBOOT AND AS WELL AS MY EDL MODE PRIVILEGES(2 PCs, a couple cables tried and the phone is still not being recognized in any of the mentioned modes ), and after doing what i mention if you can get into fastboot mode you may be in luck, however if you can get back into any other mode.(Or fastboot flash a stock rom, adb sideload etc)
im still here waiting my usb otg type c because the usb wont recognize with the adapter to micro usb. Now ive never had a usb otg type c adapter before, but i know i could never get the micro usb (universal) to adapt my otg with a, "type C" type adapter and see the storage device(usb) being recognized by android. So i will reply when it arrives and i can attempt to flash stock again via otg twrp with oos zip. (THIS HAS TO BE AN A10 ISSUE WITH TWRP BEING FAIRLY RECENT IN RELEASES AND CAUSING IT TO NOT BE RECOGNIZED AFTER PERFORMING A, "FULL WIPE")
hopefully the otg for usb c is going to be recognized by twrp still.
if all else fails and your still under contract warranty, just light the **** on fire and run it over and pay the $40 deductable and take it as a $40 lesson and have them send you a new one(or upgrade depending on eligibility etc.)
---------- Post added at 10:06 PM ---------- Previous post was at 10:00 PM ----------
billyt1 said:
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.
Click to expand...
Click to collapse
agree
im using a tmoblie variant with msm from above
---------- Post added at 10:27 PM ---------- Previous post was at 10:06 PM ----------
https://twitter.com/NTAuthority/status/1115496145051164672

billyt1 said:
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.
Click to expand...
Click to collapse
No still stuck in EDL mode.
Johndoesmoked said:
TRY TO LET IT DIE AND PUT RUBBERBANDS OLONG THE PHONE SO THE VOLUME AND POWER BUTTONS ARE HELD DOWN GOOD AND LET IT SIT FOR A DAY TO DIE.
After you do that let it sit for a bit and its dead. take off the bands and let it sit for another half a day and redo the bands to make sure its been reset and is indeed complete dead. repeat, whatever.
when its surely dead and been reset, THE ONLY thing you can try is
plug it in and almost at the same time (not simultaneously, but sequentially)
YOU NEED TO HOLD VOLUME UP+DOWN at the same time RIGHT AFTER YOU PLUG IT IN LITTERALLY. And, it should display the 1plus logo briefly and boot into fastboot mode.(i had to do this after wiping rom etc via twrp an became stuck in edl mode)
Click to expand...
Click to collapse
I don't know if you saw my last comment but I had even opened the phone up to disconnect the battery ribbon, hoping that would get it out of EDL but it didn't. However I didn't do the trick with the buttons when connecting it, I'll try this after disconnecting the battery. Also if that didn't work I'll leave it on rubber bands like you said, nothing to lose anyway. Thanks for the tips. I'll let you know what's up.
How did you know when the phone was dead while on rubber bands, do you verify if it still gets detected on the PC ?

Yeah i had did the rubberbands for a lil more than couple days and like i said i let it sit for about a day without the bands on after i had a good 20+ hours with em on then reapplied bands for about 20 hours.my phone was completely discharged during that process( OP6T).
Upon doing this i lost access to my recovery img.
Phone only boots fastboot (even if i choose recovery, it was previously working)
So now i still cant recognize in fastboot or edl.
GOT my OTG type c and put oos on usb, but as i said now my twrp isnt booting, so i shouldnt have depleted the battery as now i have no possible recovery access modes . Aside from that, im trying to figure out more info on the device and will reply in a day with what i may come to find out.
My phone did get detected because it started up as soon as i plugged into pc.
battery seems un-accessible but may have to take this apart.
I am figuring this out and i will get back to you. I need more tech assistance from a friend in the repair industry to disassemble without destroying it tomorrow or sometime friday.
This is going to have to be some sort of an intricate process to diagnose this supposed "HARD BRICK"
:Have to correct myself
talked to my brody at tmobile to see wassup with the warrenty etc.
basically its not covered under warrenty when you mess with software, blah blah i figured anyway, and he basically advises (OR more so "i didnt tell you anything like that!"- laughing) to literally run it over with your car or just smash the screen, and file the claim without issue...
BUT THE ISSUE IS ITS GONN COST YOU $99 to get a new OP6T via Assurant
your device might be the same, or even more costly,
i would prefer to avoid all costs, spending more money, not trying to..

Charnet3D said:
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
Click to expand...
Click to collapse
I wonder if you've managed to solve your problem. I have the same error SHA256 on Oneplus 7 Pro

Lefren said:
I wonder if you've managed to solve your problem. I have the same error SHA256 on Oneplus 7 Pro
Click to expand...
Click to collapse
facing same issue with oneplus 7 pro 1910, tf is wrong with this cursed series lol

thedeadfish59 said:
facing same issue with oneplus 7 pro 1910, tf is wrong with this cursed series lol
Click to expand...
Click to collapse
Yeah so sad, probably the internal memory has a slight % chance it gets corrupted or something...
Since my story in the OP I bought a used 1913 that's a bit cheaper coz of external scratches and took its motherboard for my cleaner original phone. It's been working like a charm since.

hi everyone last night i plug my phone for charging after a while i came back and see crash dump mode i switch off the and try to unbrick via msm tool 1st attempt everything fine auto reboot after progress complete it stuck in oneplus logo after that i tried to redo all thing now i faced this error on MSM TOOL PLEASE HELP ME I CHANGED THE CABLE USB PORTS DRIVER REINSTALL BUT STUCK AT THIS POINT. when i uncheck sha256 downloading start but it does not stop again and phone did not auto reboot help please

Question Recover after bad flash?

I was attempting to downgrade my moto g stylus 2021 from android 11 to 10. Something when wrong during my flash attempt and now I am stuck with a rapid bootloop where a motorolo logo will briefly flash on the screen and then go to back.
I can't seem to get back to fastboot although if I hold the down volume and power button the logo stops flashing and I just get a black screen.
Is there any possible path out of this I can try or did I hard brick my phone?

im having same thing downgrade issue i plug cord in just blink light no fastboot or recovery either.
So if you find a way let me know and ill do the same.

travy said:
im having same thing downgrade issue i plug cord in just blink light no fastboot or recovery either.
So if you find a way let me know and ill do the same.
Click to expand...
Click to collapse
Same boat as you two. Used "fastboot set_active b" after flashing stock firmware and ignored the bootloader warning. Now im stuck hardbricked with no success blankflashing. Including info for EDL Mode and log from one of my blankflash attempts as well as the correct firehose programmer for this device.

ezril said:
I was attempting to downgrade my moto g stylus 2021 from android 11 to 10. Something when wrong during my flash attempt and now I am stuck with a rapid bootloop where a motorolo logo will briefly flash on the screen and then go to back.
I can't seem to get back to fastboot although if I hold the down volume and power button the logo stops flashing and I just get a black screen.
Is there any possible path out of this I can try or did I hard brick my phone?
Click to expand...
Click to collapse
Seems to be a few of us in the same situation. I downloaded Motorola's program for, supposedly, diagnosing and fixing their phones. I'm hesitant to use it because the only place I have Windows is a VM and I've found that the connection between the phone and the computer can get a little sketchy on reboots because the USB forwarding.

Linux_SF said:
Seems to be a few of us in the same situation. I downloaded Motorola's program for, supposedly, diagnosing and fixing their phones. I'm hesitant to use it because the only place I have Windows is a VM and I've found that the connection between the phone and the computer can get a little sketchy on reboots because the USB forwarding.
Click to expand...
Click to collapse
I have had no luck whatsoever. Originally I thought I was successful using a blankflash although it was not. I've pretty much given up on that device for now although if you have anything that may help, I have no problem being the guinea pig, lol.
Keith

Question Please help me I brick my Phone!!

Hello everyone
Please help me
I have a Moto g Sylus 5g
I was following this tutorial https://www.getdroidtips.com/lineage-os-19-moto-g-stylus-5g/
to download a custom room for my Motorola device and then after I finished the installation of the room when I was on TWRP screen I've pressed recovery and then my phone went black screen nothing works..
But it didn't work. Now my phone is bricked. It's powered off and I can't turn it on again
It doesn't respond to anything
Pressing Powerbutton - Nothing
Pressing Power + Volume Up/Down - Nothing
Hold Volume down and connect to PC - Nothing
Connect to the Adapter for charging - only showing the Led light
ADB doesn't recognize the phone
Flashtool responds "Device disconnected"
So I can't flash back stock ROM
Please help me out. What went wrong? How can I fix it? Is it repairable or is my phone hard bricked?
Thank you for your answers

Hello friend, honestly I am new to this. In fact I'm looking for how to unlock my moto g stylus 5g xt2131-1 from metropcs to use it with a mobile operator in Colombia. But given your problem, and everything I've researched recently, I would say you could check this video:
in which revive a moto g8+, although it is a different version, it should work if you do the steps as indicated.

Join Electimons telegram https://t.me/electimonrel someone might be able to help.
Don't follow random guides and guides for other phones.

Yep my phone did the same thing. There is some glitch with TWRP for this phone that hard bricks the device. There are several posts here with the same issue. I tried what this video suggestion with every combination of contacts on the board. I bought an EDL cable as well and nothing would bring it back to life. I cannot recommend TWRP for this phone at this time.

duffman452001 said:
Yep my phone did the same thing. There is some glitch with TWRP for this phone that hard bricks the device. There are several posts here with the same issue. I tried what this video suggestion with every combination of contacts on the board. I bought an EDL cable as well and nothing would bring it back to life. I cannot recommend TWRP for this phone at this time.
Click to expand...
Click to collapse
Yes, Same. Nothing worked with it. I bought a new phone. I hope we find something in the future to fix it.