And for everyone saying Fastboot bricked their phone after flashing a fw directly ... You are PARTIALLY right... What actually happened is that EACH region's fw, has a specific manifest file (looks like "10001011" which cues which partiioning scheme to use for flashing. Using the 2213 .... 2211.... 2215 FULL Fw package has literally no bearing on what is going to be installed on your phone.... Other than Cosmetic, as in when you go to About Phone, your model and build details will all reflect whatever you think you flashed... But then taking the phone into DIag Mode, and reading the EFS partition with the ACTUAL fw information that is installed on your phone, will have at least 4 (all ive located so far) different files hidden in plain sight, but odd locations like 8 blank folders that only have another blank folder in them.... 8 levels deep, then 1 single TXT file that has NOTHING in it but your FACTORY BUILD DATA from when it was programmed at factory.... then a few details later, the EXACT Region, Model, Imei, and ESN that your phone is supposed to be running.... and flags that clearly state "FALSE" on every fw related line where it shows that the phone checks whether or not you have permission to do any modifications or replace those files. THAT IS YOUR BRICK!.... It shows permission to change ALL of these files, as FALSE.... so your phone is set to do all actions quietly... so when these files FAIL to get changed by the FW you just flashed... it is an instant device conflict the moment you press power.... Cuz you have mismatched Region specific code and files missing.
abl
cpucp
dtbo
engineering_cdt
modem
my_engineering
my_manifest
my_region
odm
recovery
vbmeta
xbl
xbl_ramdump
I might have missed 1 or 2, but it EXPLICITLY states <Permission_Granted>False<....
next to all of these files in a config file that is hidden in at least 4 different places in the EFS. It would be a NIGHTMARE chasing down the instruction that assigns the location of those conf files, so that you could either delete the entire instruction, or what i did... which was to use Android AGAINST ITSELF....
When i realized they could hide these conf files ANYWHERE and then drop instructions in any part of the Initrc, secure trust zone, bootloader, recovery ... ANYWHERE... then write one instruction somewhere that tells the phone to verif the hash of those files before proceeding..... i knew that was a losing strategy! I found copies of that SAME files content, WORD FOR WORD, in random "db folder" but were named without an extension at all.... same 1st name, but no extension.... adding txt did not let me open them either, except to a bunch of glyphs that looked like hundreds of characters stacked over each other, Like if you wrote a word, then used a darker pen and wrote something else.... then again... and again... and again.... but using some windows apps i was able to find what program was needed to read that file, and when i installed it, and renamed the extension to whatever it sad to, then the file opened and looked EXACTLY like the plain text ones i found in other places.
Wanna know the WEIRDEST PART??? ALL OF THESE FILES... EVERY ONE already has FULL RWX permissions granted to the folder and the files themselves!.... why go to ALL THIS CRAZY , with hiding... renaming....forcing special tools.... and duplicating, if you are just gonna make the files RWX by default to ANYONE? Im sorry but i think Oneplus/Oppo called every place they have an office/development facility, and broke the whole Oxy 12 into like 20 different sections, then gave each office 1 section and said "Complete your section... dont worry about building the OS.... just make sure your part works in an emulator.... then once complete send your completed data to the main office. They will BANDAID all the sections together, so that there is not 1 single center who knows WTH is really going on with this fw... then theres no leaks.... security breaches... nothing will matter because itll look so retarded that EVERY developer or highly technical user, will take one look and give up when they see then level of disorganization, and abnormal data structures we "Frankenstein'd" together to break their creative thought process!" --- OPPO CEO
tl'dr - device will still respond to ISP Pinout/Touch Point connection, WITHOUT the battery connected. You can proceed to have someone remote flash you
once jumpered and connected. Use windows and keep "Device Manager"
open. You will be able to watch and know when EDL becomes ready, and if the jumper becomes disconnected. Total flash time is about 7 minutes!
hope that shed a little more light on whats happening!
cheers
abl
cpucp
dtbo
engineering_cdt
modem
my_engineering
my_manifest
my_region
odm
recovery
vbmeta
xbl
xbl_ramdump
I might have missed 1 or 2, but it EXPLICITLY states <Permission_Granted>False<....
next to all of these files in a config file that is hidden in at least 4 different places in the EFS. It would be a NIGHTMARE chasing down the instruction that assigns the location of those conf files, so that you could either delete the entire instruction, or what i did... which was to use Android AGAINST ITSELF....
When i realized they could hide these conf files ANYWHERE and then drop instructions in any part of the Initrc, secure trust zone, bootloader, recovery ... ANYWHERE... then write one instruction somewhere that tells the phone to verif the hash of those files before proceeding..... i knew that was a losing strategy! I found copies of that SAME files content, WORD FOR WORD, in random "db folder" but were named without an extension at all.... same 1st name, but no extension.... adding txt did not let me open them either, except to a bunch of glyphs that looked like hundreds of characters stacked over each other, Like if you wrote a word, then used a darker pen and wrote something else.... then again... and again... and again.... but using some windows apps i was able to find what program was needed to read that file, and when i installed it, and renamed the extension to whatever it sad to, then the file opened and looked EXACTLY like the plain text ones i found in other places.
Wanna know the WEIRDEST PART??? ALL OF THESE FILES... EVERY ONE already has FULL RWX permissions granted to the folder and the files themselves!.... why go to ALL THIS CRAZY , with hiding... renaming....forcing special tools.... and duplicating, if you are just gonna make the files RWX by default to ANYONE? Im sorry but i think Oneplus/Oppo called every place they have an office/development facility, and broke the whole Oxy 12 into like 20 different sections, then gave each office 1 section and said "Complete your section... dont worry about building the OS.... just make sure your part works in an emulator.... then once complete send your completed data to the main office. They will BANDAID all the sections together, so that there is not 1 single center who knows WTH is really going on with this fw... then theres no leaks.... security breaches... nothing will matter because itll look so retarded that EVERY developer or highly technical user, will take one look and give up when they see then level of disorganization, and abnormal data structures we "Frankenstein'd" together to break their creative thought process!" --- OPPO CEO
tl'dr - device will still respond to ISP Pinout/Touch Point connection, WITHOUT the battery connected. You can proceed to have someone remote flash you
once jumpered and connected. Use windows and keep "Device Manager"
open. You will be able to watch and know when EDL becomes ready, and if the jumper becomes disconnected. Total flash time is about 7 minutes!
hope that shed a little more light on whats happening!
cheers