Software fail after replacing screen *2
So i have a google pixel fold.
I was changing the sim out and poked the tool into the hole... the sim holder came off the board and right into the screen and broke the outer screen literally the day after warrantee ran out lol
inner screen did work but it went into a boot loop.
Bought a replacement screen and accidentally tore the ribbon connecting the cable from the pull in port. so i have a useless "spare screen with town off cable end" if that can be used /repaired in anyway let me know the right terms to google! ANYWAYS...
I bought a second screen fitted it and put the wrong screw in the wrong hole which went through to the fold screen and damaged it but it still works. can load recovery etc on it. boot to recovery rescue or fastboot modes.
see the google logo etc. outer screen doesn't work or appear to do anything.
I assumed rightly or wrongly that once i replaced the screen it would load up again and it was the hardware damage to the screen that had cause the software boot loop.
I tried a factory reset from recovery mode. No change.
I then sideloaded a full OTA file from googles website. Nothing... now it reaches the "google logo"
i found the phone using ./adb devices in powershell.
i sideloaded the felix files from googles website (COULDNT load downgraded files but the latest file (details below) sideloaded fine.
i used the online tool from google but it then suggested to flash back to factory but as i cant toggle fastboot etc it just gives me "preparation instructions" to unlock fastboot which i cant perform as it doesnt load.... maybe im on the wrong screen or soemthing to utilise this tool but i thought being in "rescue mode" would be all i needed if its locked... do i need to be on a different mode like fastboot or recovery or is the flash option just out the window because its not been unlocked when the phone worked?
the phone is locked to flashing "fastboot mode etc" otherwise id have flashed it back to factory.
Phone is not locked to O2 but it is locked to flashing. i can see this when i go into recovery it shows the word locked next to it.
OTA files match the phones requirements 16/BP4A.251205.006/14401865... they verify fine... supported api: 3
FINDING UPDATE PACKAGE:
VERIFIYING UPDATE PACKAGE UPDATE GOES 0-100%
VERIFIICATION TOOK 171.1S
INSTALLING UPDATE STEP 1/2 STEP 2/2 THEN REBOOT SYSTEM
INSTALL FROM ADB WITH STATUS: 0
bootloader version felix-16.4-14097579
doesnt load im confused now.
Any idea what im doing wrong? the best fault finding technique or how to recover to factory without the option of unlocking. i dont know enough to know the difference between loading a factory file and loading a complete OTA in terms of sideloading.
ive read theres a difference in cache partitions etc with googles... which gives me hope that the factory and gettingitbackness might be on the otherside of this partition we dont touch and its perhaps repairable but i dont know how...
i can take screen back off. is there a way to test the screen when not on the phone etc (i dont think there will be anything wrong with it but incase it was damaged in transit etc. I see nothing visually wrong with it...
can i just boot the phone with one screen working if i take the outer screen off?
have i soft bricked my phone?
Next step is to send to google " inner and outer screen and a software reset" is £405 quid
happy to do everything i have all-over again in an order or start a fresh to give better information or results .
if i can get it to work even just on the inner screen ill do that until i can afford a new one or to send it to an expert.
좋은 질문입니까?