|
Welcome to the GSM-Forum forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. Only registered members may post questions, contact other members or search our database of over 8 million posts. Registration is fast, simple and absolutely free so please - Click to REGISTER! If you have any problems with the registration process or your account login, please contact contact us . |
|
Register | FAQ | Donate | Forum Rules | Root any Device | ★iPhone Unlock★ | ★ Direct Codes ★ | Direct Unlock Source |
| LinkBack | Thread Tools | Display Modes |
07-12-2022, 14:19 | #1 (permalink) |
No Life Poster Join Date: Apr 2003 Location: Torun, Poland Age: 40
Posts: 1,195
Member: 25996 Status: Offline Thanks Meter: 253 | Vivo V2109 - testpoint, fail [Solved] Code: Selected model: Vivo V2111 (Y53s 4G) Operation: Read Flash Info Software version: 3.7 Host Power Off... OK Switch virtual port to NONE... OK Connect Type-C to HUB... OK Host Power On... OK Connect phone to BOX in BROM/PRELOADER Mode Wait for device connecting... OK Driver: [MediaTek Inc.,wdm_usb,MediaTek USB Port_V1632,usb2ser.sys,3.0.1504.0] Device found at COM89 [BROM] Open port... OK Send start cmd... OK Get HW code from device... 0707 Get HW & SW version from device... OK HW VER: CA00, SW VER: 0000, HW SUB CODE: 8A00 Detect chip [MT6768] Library Version [2] Select platform... OK Init BROM... OK Force Charge... OK Disable WatchDog Timer... OK Force switch to BROM... OK Switch virtual port to USB... OK Connect Type-C to BOX... OK Host Power On... OK Wait for device... OK Read usbhost speed... HIGH Read Device Descriptor... Get VID/PID...0E8D/0003 Send start cmd... OK Get HW code from device... 0707 Get HW & SW version from device... OK HW VER: CA00, SW VER: 0000, HW SUB CODE: 8A00 Detect chip [MT6768] Get sec config... OK [000000E5] Active sec flags: [SBC DAA] Advanced Bypass Security... OK Disconnect virtual port... OK Connect Type-C to HUB... OK Wait for device connecting... OK Driver: [MediaTek Inc.,wdm_usb,MediaTek USB Port_V1632,usb2ser.sys,3.0.1504.0] Device found at COM89 [BROM] Open port... OK Send start cmd... OK Get HW code from device... 0707 Get HW & SW version from device... OK HW VER: CA00, SW VER: 0000, HW SUB CODE: 8A00 Detect chip [MT6768] Library Version [2] Select platform... OK Init BROM... OK Force Charge... OK Disable WatchDog Timer... OK Reopen port for libver2... OK Get ME ID... OK ME_ID = 0x2CBF08D0, 0xE079EF9E, 0xE0EF25F1, 0x0C77D65D Get Chip ID... [MT6768] Get SOC ID... [4E3A1450EAA6E9F41169970C66CF50EF05E9B408A241EF66C016A876CAB62931] Get sec config... OK [000000E0] Load DownloadAgent... OK Search DA... OK [8] Send preloader... OK Start preloader... OK Check preloader answer... OK Send bootloader... OK Start bootloader... OK Wait for answer from bootloader... OK Send SYNC signal... OK Setup device enviroment... OK Setup device parametres... OK Receive DA SYNC signal... OK Set DA parametres... OK Get device connection agent... [BROM] Get device info... OK EMMC_ID: 0x1501005756364A4D42045C33DCC68893 Load EMI from phone... Skip (header is empty) Load EMI config from database [DB VER: 206 DB DATE: 05-25-2022] OK [1] Trying EMI [3438B588] Init EXT RAM... error(6) Firmware version: Code: Product Brand : vivo Product Device : 2109 Product Model : V2109 Product Name : 2109_EEA Patch Level : SP1A.210812.003 Display ID : SP1A.210812.003 release-keys Ver. CodeName : REL Ver. Release : 12 Sec. Patch : 2022-05-01 Build Time : 10.05.2022 Product Info : k69v1_64 Product Manfct : vivo Product Board : k69v1_64 Board Platform : mt6768 I tried proving a firmware file, with proper preloader but it doesn't change anything. |
07-12-2022, 15:05 | #5 (permalink) |
No Life Poster Join Date: Apr 2003 Location: Torun, Poland Age: 40
Posts: 1,195
Member: 25996 Status: Offline Thanks Meter: 253 | I wiped preloader partition so i won't have to use testpoint each time, but overall phone was working fine. Screenshot below is with preloader partition restored back, now it reads EMI from phone, but Pandora still fails to connect fully. |
07-15-2022, 11:26 | #8 (permalink) |
No Life Poster Join Date: Apr 2003 Location: Torun, Poland Age: 40
Posts: 1,195
Member: 25996 Status: Offline Thanks Meter: 253 | OK, so it was a hardware issue after all. One of the capacitors under the eMCP was slightly cracked, most likely during cutting EMI shield. It was causing a short, possibly interfering with RAM communication. After solving this, the phone can be read correct via bootrom mode using testpoint. |
The Following 3 Users Say Thank You to KrzychuG For This Useful Post: |
Bookmarks |
| |
|