Database Info

Having the oddest problems. Fear a brick.

I am on a Verizon Razr Maxx HD (xt926). This all started when I decided to cleanly flash the newest version of CM10.2. I had been running it before. I wanted to start from a blank slate, so I went into TWRP and did the format wipe. Installed the newest CM10.2 nightly and gapps. This went fine and I booted into the ROM and started recovering all of my stuff. I installed F-droid and AdAway, and rebooted for that. The phone never got past the Bootloader Unlocked warning screen. I turned it off and went into TWRP to try some things. I tried to fix permissions, but it failed, referencing something to do with fdroid. I wiped again and reinstalled CM, but I still couldn't get past the Bootloader Unlocked warning.
I booted into TWRP again and wiped what I could, and accidentally wiped my external SD, and I had no card readers lying around to get the ROM zips back onto it. I downloaded the Razr HD utility, used the batch file, and tried to flash the stock rom through fastboot, but it got stuck in some kind of loop and would not flash correctly. I then tried to do it manually, but got some sort of buffer error. I tried again, and it started ok but I never saw it actually finish flashing.
By this time I finagled the ROM zips onto the SD card and stopped the fastboot and booted into TWRP. I did another set of wipes, and rebooted into TWRP again. I flashed the CM and Gapps. The ROM booted fine from TWRP and I was able to start setting up my account again. I tried rebooting after the initial setup just to see if it was working correctly, and was met with the fastboot screen with fastboot reason: Flash failed. I rebooted into TWRP from there, and tried to boot normally, but it still brought me to the fastboot. I went to the boot menu and tried the normal boot selection, and now my phone is stuck on the Bootloader Warning screen and now it won't even turn off when I hold the power button.
I have no idea what is going on, or why I could get to the working ROM once but not again. Does anyone know anything that could help me?

Kopiok said:
I am on a Verizon Razr Maxx HD (xt926). This all started when I decided to cleanly flash the newest version of CM10.2. I had been running it before. I wanted to start from a blank slate, so I went into TWRP and did the format wipe. Installed the newest CM10.2 nightly and gapps. This went fine and I booted into the ROM and started recovering all of my stuff. I installed F-droid and AdAway, and rebooted for that. The phone never got past the Bootloader Unlocked warning screen. I turned it off and went into TWRP to try some things. I tried to fix permissions, but it failed, referencing something to do with fdroid. I wiped again and reinstalled CM, but I still couldn't get past the Bootloader Unlocked warning.
I booted into TWRP again and wiped what I could, and accidentally wiped my external SD, and I had no card readers lying around to get the ROM zips back onto it. I downloaded the Razr HD utility, used the batch file, and tried to flash the stock rom through fastboot, but it got stuck in some kind of loop and would not flash correctly. I then tried to do it manually, but got some sort of buffer error. I tried again, and it started ok but I never saw it actually finish flashing.
By this time I finagled the ROM zips onto the SD card and stopped the fastboot and booted into TWRP. I did another set of wipes, and rebooted into TWRP again. I flashed the CM and Gapps. The ROM booted fine from TWRP and I was able to start setting up my account again. I tried rebooting after the initial setup just to see if it was working correctly, and was met with the fastboot screen with fastboot reason: Flash failed. I rebooted into TWRP from there, and tried to boot normally, but it still brought me to the fastboot. I went to the boot menu and tried the normal boot selection, and now my phone is stuck on the Bootloader Warning screen and now it won't even turn off when I hold the power button.
I have no idea what is going on, or why I could get to the working ROM once but not again. Does anyone know anything that could help me?
Click to expand...
Click to collapse
Try the solution in the last few posts on this thread. http://forum.xda-developers.com/showthread.php?t=2465695

I hope you get more knowledgeable advice than mine but, were I in your situation, my primary goal would be to get back to STOCK. Forget CM and modding for now. Either through TWRP or through the recovery settings on the phone itself I'd get to where I could do a factory reset. If you're continuously able to boot into TWRP I don't see how your phone could be bricked. My experience is, if I can get a phone to do ANYTHING I've got a shot at figuring out how to get out of whatever mess I've created. I don't know if this could be a factor but I'd put in a different micro SD card too, in case there's something on the card you've got in there.

Just an update. So, I got it to go back to fastboot this morning and I tried using the Razr Utility to flash back stock and stock recovery, but I got a "Failed" line with the reason "Remote Failure". Not sure what that's about. When it reset it got back to the Cyanogenmod boot graphic, but it never started. I left it there for a good 12 minutes.
Right now it's sitting in TWRP. I'm going to let it charge to 100% (it was a little less when I tried all of this) and attempt it again at 100% battery. Thanks for the help so far!

So, I tried using the Razr Utility to flash the system, kernel, radio and for system it was unsuccessful (something about too many threads or strings, something to that effect), but the rest said OK. Now my phone doesn't seem to turn on. My computer still makes the device plugged in sound when it's plugged/unplugged, but I cannot get the screen to show anything or seem to turn on the phone.
Is this it? Is it... bricked!? ;-;
Edit: I ordered the Factory Adapter as a last resort sort of thing. This is lame.
Edit Edit: I've seen the boot logo since my last edit! But... it's not coming back and I still can't even bring up the bootloader. I don't know why it will sometimes turn on or sometimes not. In any case, I'm now hopeful that not ALL is lost.

Bottom line, the adapter will allow you to fix your phone and flash the stock FXZ in RSD Lite or fastboot and get back to a clean slate and start over.
That's why we went to the trouble of making them!

cellzealot said:
Bottom line, the adapter will allow you to fix your phone and flash the stock FXZ in RSD Lite or fastboot and get back to a clean slate and start over.
That's why we went to the trouble of making them!
Click to expand...
Click to collapse
That's the plan! One odd thing happening now... My phone's screen isn't showing anything, so I assumed it was off. I left it unplugged and went to see a movie..... and the phone is still warm. This leads me to believe the phone is still drawing power, for some reason... God this is weird. I'll wait for the adapter and try again. Thanks for the help!

cellzealot said:
Bottom line, the adapter will allow you to fix your phone and flash the stock FXZ in RSD Lite or fastboot and get back to a clean slate and start over.
That's why we went to the trouble of making them!
Click to expand...
Click to collapse
according to the packaging on mine from tbh a chinaman made it, just sayin

Yes, we designed them and contracted through our US supplier who produced all of our cables who, in turn, had them produced in China according to our specifications. There is no longer any injection molded plastic production done in the US that can work at this small scale for affordable rates.
Sorry...that's the way the world works these days.

cellzealot said:
Yes, we designed them and contracted through our US supplier who produced all of our cables who, in turn, had them produced in China according to our specifications. There is no longer any injection molded plastic production done in the US that can work at this small scale for affordable rates.
Sorry...that's the way the world works these days.
Click to expand...
Click to collapse
thanks for making it either way, better to have and not need.
havent had to use it so far

bweN diorD said:
thanks for making it either way, better to have and not need.
havent had to use it so far
Click to expand...
Click to collapse
You're welcome! They are definitely the best $10 investment you can make in any Motorola phone.
Next time you want to invest many thousands of dollars of your own money in a wild, hairbrained scheme to help a bunch of anonymous people on the internet fix their phones that they recently finished destroying themselves, let us know...we have just the plan!

cellzealot said:
You're welcome! They are definitely the best $10 investment you can make in any Motorola phone.
Next time you want to invest many thousands of dollars of your own money in a wild, hairbrained scheme to help a bunch of anonymous people on the internet fix their phones that they recently finished destroying themselves, let us know...we have just the plan!
Click to expand...
Click to collapse
how many thousands, and whats the plan?

I got the Factory Adapter and used RSD Lite to flash stock. And it works! Yay! It's starting up reliably and everything.
Except... it won't start up without the cable attached, and the battery icon has a big question mark on it. It also won't connect to the cell network (but does connect to WiFi). What do I do now?
Edit: So I noticed that while the battery status said "Unknown", it did go from 2% to 3% charge level when I plugged it in normally for a little. My plan at the moment is to try leaving it plugged in for a while and then try taking the OTA update to see if that fixes everything. Good plan?
Edit Edit: Never mind! I just had to let it charge for a bit. It seems to be back in working order, now! Thank you so much for all the help everyone!

That is exactly what is supposed to happen. Congrats on fixing your phone!
The factory cable/adapter does not charge the device but powers it directly, allowing it to boot no matter what state the battery is in or even without a battery at all.
You cannot charge in bootloader, which is why the cable/adapter is so valuable. Once the device can boot/charge normally then you are all set.

Help for my SM-P900

Hi everyone,
I'm hoping that someone can help me out with my device. I have a rooted sm-p900 that was working fine until a month ago when I tried to flash [ROM][7.1.x|SM-P900| Unofficial LineageOS 14.1 (v1awifi). I was busy multi-tasking and made the stupid mistake of flashing the rom before updating the BL. Since trying to do so, I have not been able to get past the first screen that says "Samsung sm-p900" . After the logo disappears, my screen remains lit but is just black.I could not restore my backup after either.
Where I am now:
- I can still access and use T.W.R.P. (latest 3.1.1) (If TWRP is left alone for too long, the device will reset to the same black screen and hang forever. If flashing a rom is taking long, the device will restart mid-flash as well.)
- I can still access download mode and use odin as well.
- I have since flashed the appropriate BL but that has not changed anything.
-I have tried clean flashing a magnitude of different roms and still come across the same problem.
I honestly have no idea how I can fix the device and have tried everything I know how. I would love to get it back as soon as possible. Any help is greatly appreciated, so thank you in advance!

jp2572 said:
Hi everyone,
I'm hoping that someone can help me out with my device. I have a rooted sm-p900 that was working fine until a month ago when I tried to flash [ROM][7.1.x|SM-P900| Unofficial LineageOS 14.1 (v1awifi). I was busy multi-tasking and made the stupid mistake of flashing the rom before updating the BL. Since trying to do so, I have not been able to get past the first screen that says "Samsung sm-p900" . After the logo disappears, my screen remains lit but is just black.I could not restore my backup after either.
Where I am now:
- I can still access and use T.W.R.P. (latest 3.1.1) (If TWRP is left alone for too long, the device will reset to the same black screen and hang forever. If flashing a rom is taking long, the device will restart mid-flash as well.)
- I can still access download mode and use odin as well.
- I have since flashed the appropriate BL but that has not changed anything.
-I have tried clean flashing a magnitude of different roms and still come across the same problem.
I honestly have no idea how I can fix the device and have tried everything I know how. I would love to get it back as soon as possible. Any help is greatly appreciated, so thank you in advance!
Click to expand...
Click to collapse
Have you tried taking it completely back to stock via Samsung Kies on your PC?
Sorry I don't have complete details, but it goes something like this (and if you search this site or Google, you'll find a good write-up on how to do a complete recovery using Kies):
1. If you can, make a backup using TWRP - if not, you are going to lose everything because of the next steps
2. Download and install the Kies software from the Samsung site and install it on your PC (I grabbed both versions, can install both on the same PC at the same time)
Make sure that it installs the Samsung USB driver
3. Connect to the tablet using the OEM cable - if you get a reaction from Kies, great
4. Somewhere in the Kies menu, you can tell it to do a complete recovery, including bootloader- if I remember correctly, you'll need your serial number (Sorry, been 18 months since I did just about the same thing and was able to recover it from my FUBAR, and I no longer run Windows so I can't step thru it)
It will go through downloading and flashing your tablet back to the state it was when you pulled it out of the box.
If you get to that point, you will have to go the whole route (including loading TWRP) to get it back to Lineage. It took me about two weeks to get it back to the way I had it before I was flashing and reading a book and talking to my wife all at the same time and didn't pay attention to what I touched on screen.
I apologize for the rambling and not having definitive statements, but I'm drugged up and been awake for the last 36 hours, and at my age that isn't a good combination.

Thank you so much for your help! I couldn't end up using that method because kies would not recognize my device for anything. It did get me inspired to try fixing it again however and it worked!
If anyone ever encounters the same or a similar problem, I just tried re-rooting it using odin and cf's autoroot file. It allowed me to be able to install roms again.
rhricik447 said:
Have you tried taking it completely back to stock via Samsung Kies on your PC?
Sorry I don't have complete details, but it goes something like this (and if you search this site or Google, you'll find a good write-up on how to do a complete recovery using Kies):
1. If you can, make a backup using TWRP - if not, you are going to lose everything because of the next steps
2. Download and install the Kies software from the Samsung site and install it on your PC (I grabbed both versions, can install both on the same PC at the same time)
Make sure that it installs the Samsung USB driver
3. Connect to the tablet using the OEM cable - if you get a reaction from Kies, great
4. Somewhere in the Kies menu, you can tell it to do a complete recovery, including bootloader- if I remember correctly, you'll need your serial number (Sorry, been 18 months since I did just about the same thing and was able to recover it from my FUBAR, and I no longer run Windows so I can't step thru it)
It will go through downloading and flashing your tablet back to the state it was when you pulled it out of the box.
If you get to that point, you will have to go the whole route (including loading TWRP) to get it back to Lineage. It took me about two weeks to get it back to the way I had it before I was flashing and reading a book and talking to my wife all at the same time and didn't pay attention to what I touched on screen.
I apologize for the rambling and not having definitive statements, but I'm drugged up and been awake for the last 36 hours, and at my age that isn't a good combination.
Click to expand...
Click to collapse

Try updating the bootloader again using odin
When this has happend factory reset
Flash the rom, addonsu and gapps in the same TWRP session
The rom should work then, I've been happily using it for about 6months now

[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

A8 SM-A530F TWRP Install Failure

[SOLVED, ANSWER BELOW]
Hi
Yesterday I tried to install TWRP Custom Recovery on my phone. I have done it before succesfully on different models.
The installation went smoothly, and I managed to boot into TWRP quickly. However the touch screen went all funky. Every little button I had to press was a difficult process, and I could barely swipe the unlock mechanism. Using the keyboard to type 'yes' for certain functions was impossible. I tried everything from aluminium foil to special gloves..
I looked up methods how to fix this and this site came up multiple times. Some solutions offered however were too complicated for me to use, because I have no knowledge on the core electronics of my device.
I decided to just leave it at this and turn off my phone. I tried going to the menu to power my phone off, however it decided pressing a lot of buttons was a better idea. I have no idea what buttons were pressed during that moment of craziness, and now I can only get my phone into the download mode. If I try to acces TWRP, it boots up to the first screen, then immediately turns off, and does it again. I can shut that process off, by pressing the power button + volume down, and then using volume up+down+power button to go into download mode.
I have the version of Odin that matches my android 9.0 Pie version, not the latest, as the latest version of Odin did not even install TWRP the first time I tried this, but the matching yet older version did.
I tried reinstalling TWRP. No luck.
I tried flashing stock firmware. I get a Complete(write) Operation failure.
I have up-to-date USB drivers
I tried Samsung Smart Switch but it does not recognize my device. I tried reinstalling my USB drivers to no avail. I used different USB ports, and a different USB cable.
I have tried to look up any and everything that may relate to this issue but I have not succeeded in finding anything that fixes my issue.
When I started the process, OEM unlock and USB Debugging was turned on. It may or may not have turned off in that crazy moment, I can't tell
All of my data is backed up or not valuable to me. A factory reset, or wipe, or whatever, is something I'm okay with. I just want my phone back.
Thank you for your help
Greetings, Jaxus
[SOLUTION]:
I decided to go ahead and use the latest Odin anyway. It worked. My touchscreen issue has been fixed, and I can go back to rooting as I expected I should be able to. I apologize if I broke any social convention in my post.

SM-A530W
I just recently ran into same'ish TWRP issues and locked up totally upon a reboot with a SM-A530W. Here's why,apparently. https://forum.xda-developers.com/galaxy-a8-2018/samsung-galaxy-a8-2018-guides-news--discussion/guide-root-install-twrp-samsung-january-t3760975 I got the "Only official released binaries are allowed to be flashed" message. Most certainly worth a read. Wow, 7 full days (168h) going unmolested, who would of guessed such.

Does Rooting work for Android 9?

I don't know what to do!!!
uwannabananababy said:
I just recently ran into same'ish TWRP issues and locked up totally upon a reboot with a SM-A530W. Here's why,apparently. https://forum.xda-developers.com/galaxy-a8-2018/samsung-galaxy-a8-2018-guides-news--discussion/guide-root-install-twrp-samsung-january-t3760975 I got the "Only official released binaries are allowed to be flashed" message. Most certainly worth a read. Wow, 7 full days (168h) going unmolested, who would of guessed such.
Click to expand...
Click to collapse
I have the same phone and I've got a similar problem I've used every odor known to man the newest one to the oldest one I can no longer load TWRP I can't root it I can't do anything please tell me what I can do thank you in advance

Did I just destroy my phone ? Japanese Pixel 4a can't boot after first reboot under LineageOS

Hi all,
I recently imported a used Japanese Pixel 4a (I wanted the jp-exclusive "Barely Blue" model), and immediately upon receiving it, installed LineageOS 19 on it.
The phone originally came in with some form of android 12 (I didn't check that very precisely unfortunately, could have been 12.0 and not 12.1)
Installing LineageOS went mostly fine, the phone managed to boot and I was able to use it for a few hours ... then wifi and mobile data stopped working. I thought rebooting would fix that, so I tried rebooting, but the phone never rebooted completely.
I've tried a lot of things to get it back to a working state :
Flash LineageOS again
Flash Google's Factory Image for the last 12.1
both via the online tool AND the flash-all.sh script
both on slot A and B
also tried the very old 10.0.0 JP-carrier-specific image
with a different USB cable
on a different USB2 port on my computer
on a USB3 port on my computer
Flash Google's Full OTA Image for the last 12.1
by using fastboot to boot into lineageos's recovery image
At one point in my attempts at making it work it even displayed the "Your device is corrupt" error message (it's now gone btw).
My phone is now in a state where I can reach fastboot, but everytime I try booting up any ROM (Google or LineageOS), it shows the boot animation for something like 2 seconds then shuts down.
Any help you guys could provide would be awesome

Stepland said:
Hi all,
I recently imported a used Japanese Pixel 4a (I wanted the jp-exclusive "Barely Blue" model), and immediately upon receiving it, installed LineageOS 19 on it.
The phone originally came in with some form of android 12 (I didn't check that very precisely unfortunately, could have been 12.0 and not 12.1)
Installing LineageOS went mostly fine, the phone managed to boot and I was able to use it for a few hours ... then wifi and mobile data stopped working. I thought rebooting would fix that, so I tried rebooting, but the phone never rebooted completely.
I've tried a lot of things to get it back to a working state :
Flash LineageOS again
Flash Google's Factory Image for the last 12.1
both via the online tool AND the flash-all.sh script
both on slot A and B
also tried the very old 10.0.0 JP-carrier-specific image
with a different USB cable
on a different USB2 port on my computer
on a USB3 port on my computer
Flash Google's Full OTA Image for the last 12.1
by using fastboot to boot into lineageos's recovery image
At one point in my attempts at making it work it even displayed the "Your device is corrupt" error message (it's now gone btw).
My phone is now in a state where I can reach fastboot, but everytime I try booting up any ROM (Google or LineageOS), it shows the boot animation for something like 2 seconds then shuts down.
Any help you guys could provide would be awesome
Click to expand...
Click to collapse
Could you walk us through the steps you took to initially flash LOS?
Also, have you tried flashing versions other than 12.1 of Google's factory images?
Can you boot into recovery? Did you root LOS?
How did you import the device? Are you sure it was a trusty site/seller? Could they have tinkered something with the device to not make it work?

Could you walk us through the steps you took to initially flash LOS?
Click to expand...
Click to collapse
The very first time I flashed LineageOS I just followed these "official" installation instructions from the LineageOS website. The only mistakes I remember making were :
I forgot to really check that the phone actually was on the latest stock 12.1, the phone may have been on 12.0 or an older 12.1 prior to flashing LOS
I forgot to reboot between flashing LineageOS and GApps (MindTheGapps in my case), noticed my mistake, rebooted then flashed GApps again
After I saw things weren't working, I double checked the version numbers and the sha256 hashes of everything I had downloaded and they were all correct
Also, have you tried flashing versions other than 12.1 of Google's factory images?
Click to expand...
Click to collapse
Yes,
I tried flashing factory images of
10.0.0 (Android 10) QD4A.200805.001 (6583866) (JP carriers and Verizon)
12.1.0 (SP2A.220405.003, Apr 2022)
12.1.0 (SP2A.220505.002, May 2022)
12.1.0 (SQ3A.220605.009.A1, Jun 2022)
12.1.0 (SQ3A.220705.003.A1, Jul 2022)
13.0.0 (TP1A.220624.014, Aug 2022)
Can you boot into recovery?
Click to expand...
Click to collapse
Yes
Did you root LOS?
Click to expand...
Click to collapse
No
How did you import the device? Are you sure it was a trusty site/seller? Could they have tinkered something with the device to not make it work?
Click to expand...
Click to collapse
By asking a person who's used to proxying things, this phone was from a listing on rakuten, it came from this seller. Since it came in with stock 12 (or 12.1, don't remember), I think it's unlikely they tinkered with it

Stepland said:
I forgot to really check that the phone actually was on the latest stock 12.1, the phone may have been on 12.0 or an older 12.1 prior to flashing LOS
I forgot to reboot between flashing LineageOS and GApps (MindTheGapps in my case), noticed my mistake, rebooted then flashed GApps again
Click to expand...
Click to collapse
These likely have nothing to do with the issue you're facing.
Since you're able to boot into recovery, would you be open to try to flash literally any custom ROM (with the provided custom recovery), and see if that works?
You can flash whatever you like, since you said you wanted to go for LOS, I'd recommend you flash PixelExperience, since it's the closest to that (I think). You can download the regular or the plus edition, doesn't really matter. Make sure you not only download the build (flashable zip), but also the recovery image.
I assume you're familiar with the process of flashing custom ROMs. Should you be unfamiliar, I followed this guide when I first flashed a custom ROM on my 4a.
(If you don't feel like watching a video made for newbies, here are some notes I took a while back, just so I can know I never skip a step):
Spoiler: Flashing steps
adb reboot bootloader
fastboot devices
fastboot flash --slot all boot <img_name>.img (i think this can be skipped?)
use power buttons to enter recovery mode
apply update
apply update over adb
adb sideload <zip_name>.zip
*/ if you don't want to root, you can skip everything below /*
reboot recovery (to change to active slot so that magisk flash goes to correct slot)
apply update over adb
adb sideload <magisk_name>.zip

Oh my GOD thank you SO much I'm finally getting somewhere !
I tried flashing PixelExperience, both recovery and the ROM itself, the flashing part went well.
Then I rebooted and the following things happened in order :
static google screen
phone reboots (before the animated G even appeared)
PixelExperience screen that warns "your data may be corrupt you may need to perform a factory reset"
I chose the factory reset / wipe data option
phone reboots
boot animation that lasts WAY longer than in any of my previous attempts, goes as far as 3/4 of the progress bar
phone reboots before reaching the welcome screen
PHONE SUCCESFULLY REACHES THE SETUP/WELCOME SCREEN ON THE NEXT BOOT
phone seems to freeze for a moment
"Bluetooth keeps stopping" message pops up
phone reboots + reaches welcome screen a few times
phone reboots, reaches welcome screen, then plays the "charging" chime (didn't hear it before even though it was plugged in the whole time)
It has now been a solid 10 minutes and my phone is showing the welcome screen and hasn't crashed !?!
What should I do to troubleshoot what caused the crashes ?
Thank you SOOOOOO much for your help so far !

Stepland said:
PixelExperience screen that warns "your data may be corrupt you may need to perform a factory reset"
I chose the factory reset / wipe data option
Click to expand...
Click to collapse
Ah, yeah, my mistake. You are supposed to perform a factory reset whenever you flash a different ROM. Step can only be skipped when performing a dirty flash.
Stepland said:
It has now been a solid 10 minutes and my phone is showing the welcome screen and hasn't crashed !?!
Click to expand...
Click to collapse
What do you mean by "showing the welcome screen"? Can you use your device? Can you log in to your Google account and set it up? If we don't take Bluetooth crashing into account, would you be able to use your device regularly?
Stepland said:
"Bluetooth keeps stopping" message pops up
Click to expand...
Click to collapse
Stepland said:
[...]the phone managed to boot and I was able to use it for a few hours ... then wifi and mobile data stopped working.
Click to expand...
Click to collapse
See, these malfunctions you get regardless of the OS makes me think somebody tinkered with your phone/gave you a faulty unit to begin with.
You could try to flash any / of / these kernels to see if they stop the "bluetooth crashed" notification. If you do flash a new kernel, I'd suggest you do another factory reset after the kernel has been flashed (and before you boot your device up). Just to make sure nothing stays in cache and no configurations remain that could cause this error again.
If that doesn't help, for starters, I would suggest you flash radio.img provided by Google on this site. Make sure you download the one corresponding to your build number (which you can find out by going to Settings -> About phone -> Build number (it will be at the very bottom of the page)).
You can flash this downloaded radio.img using "fastboot flash radio radio.img"
If that doesn't help either, I would try to use the Android Flash Tool. I assume the PixelExperience you downloaded is A12.1, so I would choose the latest 12.1 version in the Flash Tool. Be sure you have the "Wipe Device" and "Force Flash all Partitions" boxes ticked!!

Lada333 said:
What do you mean by "showing the welcome screen"?
Click to expand...
Click to collapse
It reached the setup assistant you are presented with the first time you power on a phone, without crashing
Lada333 said:
Can you use your device? Can you log in to your Google account and set it up? If we don't take Bluetooth crashing into account, would you be able to use your device regularly?
Click to expand...
Click to collapse
Unfortunately no :
Wi-Fi doesn't work
I can access the Wi-Fi menu in the settings, I can "turn it on" but it never finds any network. My other phone is doing just fine on my home wi-fi so it's not just that there's no network reachable​
my SIM card is not recognized
Not much to say, I placed it in and the phone says it has no SIM card inserted, even after I reboot​
it takes many attempts to successfully boot the phone
Last reboot took 8 tries​
Surprisingly, Bluetooth seems to be working just fine ? I was able to connect to a bluetooth speaker and play some sounds
Lada333 said:
You could try to flash any / of / these kernels to see if they stop the "bluetooth crashed" notification. If you do flash a new kernel, I'd suggest you do another factory reset after the kernel has been flashed (and before you boot your device up). Just to make sure nothing stays in cache and no configurations remain that could cause this error again.
Click to expand...
Click to collapse
Tried blu_spark, exact same problems :
Takes many attempts before a "successful" boot
Wi-Fi broken
Can't detect my SIM card
Lada333 said:
If that doesn't help, for starters, I would suggest you flash radio.img provided by Google on this site. Make sure you download the one corresponding to your build number (which you can find out by going to Settings -> About phone -> Build number (it will be at the very bottom of the page)).
You can flash this downloaded radio.img using "fastboot flash radio radio.img"
Click to expand...
Click to collapse
That worked almost perfectly !
fastboot was refusing to flash radio when the phone was on fastbootd, regular fastboot worked just fine, I also flashed with --slot all because ... why not ?
After that the phone booted just fine on the FIRST TRY ! Wifi and mobile data both work !
Unfortunately it's still a bit unstable, after the first boot the phone shut down after about 10 minutes (while I was playing back a youtube video, if that's of any importance ?). It rebooted just fine without crashing even once, and it's now been running for half an hour without a problem.
If that doesn't help either, I would try to use the Android Flash Tool. I assume the PixelExperience you downloaded is A12.1, so I would choose the latest 12.1 version in the Flash Tool. Be sure you have the "Wipe Device" and "Force Flash all Partitions" boxes ticked!!
Click to expand...
Click to collapse
Well actually it was 13, so I tried flashing 13. it all went fine ! The phone rebooted fine on the first try, wifi and mobile data both work ... I'm speechless, I don't even understand what I did that made it work ... but it works !
I'll try using the phone for a few days and report back any problems if I don't forget about it.
Thank you so much for your help ! I owe you big time

Well uh, the joy was short-lived. The phone lasted a couple hours before shuting down and going back into a short series of failed boot attemps, but now every failed boot attempt gets noticeably "further" in the boot animation than they did at the time of my initial post.
The phone managed to boot yet again, wifi + data + bluetooth still work.
Keeping an eye on it for now

Stepland said:
Well uh, the joy was short-lived. The phone lasted a couple hours before shuting down and going back into a short series of failed boot attemps, but now every failed boot attempt gets noticeably "further" in the boot animation than they did at the time of my initial post.
The phone managed to boot yet again, wifi + data + bluetooth still work.
Keeping an eye on it for now
Click to expand...
Click to collapse
I honestly don't have any experience with custom ROMs on Pixels, but if you want to return to bone stock, you can use the Android Flash Tool. Since you've been using custom firmware, make sure you check the Force flash all partitions option.
Otherwise, you can refer to my guide to flash the factory firmware and root using Magisk.

Yup, that's what I did to get it to its current state.
The phone is still unstable, it rebooted itself twice just this morning.
If this is a hardware issue, how do I diagnose it ?

Stepland said:
Yup, that's what I did to get it to its current state.
The phone is still unstable, it rebooted itself twice just this morning.
If this is a hardware issue, how do I diagnose it ?
Click to expand...
Click to collapse
If you tried a stock rom, a custom ROM , with all the same results it's probably a hardware issue, have you noticed excessive heat coming from the phone? You could always trade it in for a 6a and get 300.00 credit as long as the screens good and it turns on.

hammered58 said:
have you noticed excessive heat coming from the phone?
Click to expand...
Click to collapse
Yes in fact I have ?! How did you guess that, that's weirdly specific ?
It was heating up a bit, at least enough to be noticeable and to feel abnormal but not uncomfortable. I can't remember if it got warm while it was doing its updates or before. I would have guessed it was just working pretty hard if it had been happening during some updates. Weirdly enough now that it's doing nothing it's not warm anymore
hammered58 said:
You could always trade it in for a 6a and get 300.00 credit as long as the screens good and it turns on.
Click to expand...
Click to collapse
Hmm, that's good to know. I think I'll pass tho, I chose the 4a specifically because it's small and lightweight while not being a completely out-dated phone, the 6a would take me back to more or less the same size and weight as my current phone (xiaomi vince) which I find too big and heavy. Oh the things I'd do for a flagship phone that's like, actually small

Stepland said:
Well uh, the joy was short-lived. The phone lasted a couple hours before shuting down and going back into a short series of failed boot attemps, but now every failed boot attempt gets noticeably "further" in the boot animation than they did at the time of my initial post.
The phone managed to boot yet again, wifi + data + bluetooth still work.
Keeping an eye on it for now
Click to expand...
Click to collapse
As the others have pointed out as well, it is likely a hardware malfunction. Your radio partition (?) was likely corrupt, so we got rid of that, but if random reboots still happen PLUS your device overheats, it's 99% not a software issue.
Not sure about the RMA process, since you imported the device from overseas. Try contacting your POS?

Stepland said:
Yes in fact I have ?! How did you guess that, that's weirdly specific ?
It was heating up a bit, at least enough to be noticeable and to feel abnormal but not uncomfortable. I can't remember if it got warm while it was doing its updates or before. I would have guessed it was just working pretty hard if it had been happening during some updates. Weirdly enough now that it's doing nothing it's not warm anymore
Hmm, that's good to know. I think I'll pass tho, I chose the 4a specifically because it's small and lightweight while not being a completely out-dated phone, the 6a would take me back to more or less the same size and weight as my current phone (xiaomi vince) which I find too big and heavy. Oh the things I'd do for a flagship phone that's like, actually small
Click to expand...
Click to collapse
Your right though,, it's the size and weight of the 4a that brought me here in the first place so I can see your point in not switching, good luck!!

You seem really ticked off, I'm sorry if my answer came out as snarky or something ? that really wasn't the intent
Nevermind, completely misread your answer, non-native english speaker moment

Hm, just when I was about to post that the phone seemed to be working fine because it hadn't rebooted for 30+hours ... it just rebooted again.
And yeah it also got warm again while I was installing some apps ... so uh ... no luck

Stepland said:
And yeah it also got warm again while I was installing some apps
Click to expand...
Click to collapse
That's not necessarily an issue. Installing apps uses the CPU, which, in term, generates heat.
What we and hammerhead meant by 'the phone heating up' is it randomly becoming inexplicably hot.
Like for example when it's just sitting on your desk, not doing anything. No notifications popping up constantly, no music/video playback, nothing. Just when it's supposed to be in deep sleep.
This app is rather outdated and you need to type in 3 adb commands for the advanced stats to show up, but it still works perfectly for finding out if any apps are draining the battery in the background and to see if you have any wakelocks.
You could give it a shot, install it, enable in settings -> general "App Usage," "Device Usage Access" and "Record History," and wait a few days, see if you have any apps misbehaving.
Again, I'm still leaning toward it being a hardware issue, but hey, worth a try.

I give up, it just has to be a hardware defect.
Since with stock 13 it looked like the phone was almost stable (it would only reboot every 10 hours or so) I tried using it for a day, unfortunately it quickly went back to the exact same state it was in when I created this thread : the phone won't boot, it crashes two seconds into the boot animation.
Still, massive thanks to everyone who helped me through this !
I ordered a replacement.
If anyone wants the broken one my DMs are open