EskeRahn

@Whitey, having it disassembled, can you see if there are any circuitry between the plug and the cable? (this is interesting to know for the DIY suggestions over here) (I think I better move these comments to a battery thread, as it really in no way is a sailfish specific thing) done... (This thread is split out from here)

I think you are on the right path, and will need to go through EDL-mode. If the phone were turned off, the battery of a phone usually last for at the least a year if fully charged, without depleting it self. But if it was in a state where it turned it self off, and then was left for months, it might well be problematic. I do not know if there are any tricks to charge the battery in that state without opening the phone and charging the battery directly, by a circuitry bypassing the charging-logic (do not give the battery 5V directly). Many phones by default comes with a silly mode

Thanks, I corrected the link.

Did I in any way say that people should not do what you suggested? I even did follow one of your links for a recipe and fetched the source, There are zero control that any code and link in the text on github are related, so yeah I see that as random links, obvious less random that what a google search can throw at you, but still unsafe. That Is why I needed to compile any source, that as open source is much less likely to be dirty than linked binaries..

Would be great if we could thus rule out or confirm, if it is the location or the specimen that is the culprit.

I do not know if a similar thing exists publicly available in the US, But here in Denmark there is a public site "mastedatabasen.dk" where one can zoom in and see quite a bit of info on each cell-tower location. ADD: https://www.cellmapper.net/ give some information along the highways , and several roads. That might help.

You are aware that the links you posted were for the source, right?. And yes I did not read all the blah blah so I did not look for links for the binaries, And anyway I never install binaries from random links, so would not have used them had I found them..

yes...

Except having to install something else that can execute .go instead of .py ...... 🤣

Yeah, but we do NOT know if there are any circuitry between the cable and the battery cells. We would need some close ups, or even disassembled batteries... But sure we could be lucky that there are only connecting wires between the plug and the cells.

OK, I tried TLDR: Waste of time, AICP-S is BROKEN for Pro1!!! I gave AICP a final chance by infesting a windows-pc with Phewton (it was already infested with GIT) and extracted the boot.img from the zip. Following this guide https://wiki.lineageos.org/extracting_blobs_from_zips#extracting-proprietary-blobs-from-payload-based-otas (adjusted as needed...) Infested a PC with Python, https://www.python.org/ Downloads Download for Windows, Python 3.11.2 Found pip.exe and installed packages needed C:\Users\Administrator\AppData\Local\Programs\Python\Python311\Scripts

The campaign was opened in October (My contribution is From October 27) And I bet that a large portion came within a few days (to benefit from the early offers), so depending on when in November you joined, 1528 do not have to be a high number. (And not all numbers are equal to a perk for a phone. Spare parts, and failed or cancelled orders 'burns' a number - on previous campaign I have had problems with IGG accepting the payment, and that is not uncommon that an order fails this way, and we have to try again)

Though we still know too little on the cause, we should not rule out the possibility that there COULD be some hardware issue that does not affect ALL Pro1X. I mean that it is totally feasible that some batches are better/worse than the rest. That would explain why some have problems and others not. though it is obviously not the only possible explanation, until we have a situation with a spot where one Pro1X consistently fails and another is working flawless (or at the least much better), with the same sim/provider.

Remember that he wrote that it can be accessed from a computer, so a good guess is that no 'vital' parts are damaged, though the display (or cables for it) is. But obviously no guarantee, that no other parts have suffered.

same via adb.

Well if you fiddle extracting the boot image from the newest S image, as e.g. claude0001 suggests, I guess it is likely that it will work with that as boot-loader.

....In the second repair video here they take out the battery, at about 3min in, but it is hard to get any details from the images.

As we have seen there is 'something' on the battery/end of the cable, I have no idea what that circuitry actually is, but it means the lithium calls are not just directly connected to the board, so what ever it is have to be mimic by a DIY solution we can glimpse it at the FCC image also

Though certainly an interesting idea., I guess one reason could be pure cash-flow, as they have troubles in even scraping in the money to send the devices already produced. And at best a single trip could collect data, so repeated trips would be needed to test any firmware fix they may come up with.

@Casey as we are speculating in modifying alternatives. would the one for the Pro1X physically fit the slot? If so that might be a better start than the other suggested, or what do you say?

Note that FxTec told that the batteries are not interchangeable between the two models.... (Do not know the reason)

Just to be sure, Is it Pro1 or Pro1X? If a Pro1, you could try to attach an external display through an usb-hdmi adapter. It duplicates what is on the display, so you will be able to know if touch, front camera, proximity sensor etc etc works. IF it works, it is likely that a fairly simple replacement of the display will do the trick. You can get displays from e.g. AliExpress just search for "Elephone U pro". You do NOT want to buy it with a frame, it will just be a waste (as it is different)

The big question is if we can just move over the electronics part and the ribbon cable from an old one, even if it fits inside??? I guess we should be pretty sure that a new is of same physical composition and has at the least the same capacity as the original, so the electronics will not try to overcharge it - dependent on how dumb/clever the small circuitry between the cells and the phone is.... Anyone knows anything on this? Maybe from FxTec? @Casey can you help with some info here?

I see it just fine,

"20230322" A lot of changes in their change-log, so optimistically tried again ..... Same as usual. So got a crazy idea. What would happen if I flashed the same image to BOTH slot A and B, wiped the user-data, and booted?? After the usual 8 x 30s boot-loop, it continues to boot another eight time, and ends back at the at the boot-loader. So what I has seen as wrong package content really most likely was the backup image!! I was never able to actually boot the image after the change they made after a few S-upgrades! So most likely I really need to extract the boot-image f