I did run lf t5 p1detect to make sure I was in the right spot as shown in my screenshot. I was pressing rather hard once again so I was able to get a good read.
That would be helpful, but I do have to be somewhere very soon, expecting a call for me to leave soon. Would it be okay to set up a time possibly tomorrow?
some 1-1 might be good, i’m super squeezed for time except for this thursday i could do, im GMT.
the annoying thing about this is, any number of things could have happened during the initial bad write trailed by further damage with some of the debugging done.
I have a feeling this is recoverable but it might take a good bit of messing around. if you happen to be in the uk it genuinely might be easier for you to come to me/vis versa
edittoadd: cut off your hand, mail it to me in an icebox, i’ll fix your chip and mail it back with some sewing thread and you can stick 'er back on.
I wish I could stop by, but I’m on the total other side of the earth in Seattle. I don’t mind doing more troubleshooting with really anything as I’m learning every step of the way. I don’t think I’m busy Thursday, except for work from 7am - 3pm PST (2pm - 10pm GMT), so please let me know what a good time would be!
@amal
I do apologize to ping you once more, but since this situation seems to be getting nowhere, do you think this would apply for the warranty? What would you recommend to do next moving forward?
Also, if it is under warranty for a replacement, seeing that the NExT2 recently was released, would I be able to pay the difference and get that instead?