GSM Shop GSM Shop
GSM-Forum  

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 .

Go Back   GSM-Forum > Product Support Sections > Hard/Software Products (official support) > Pandora’s box


Reply
 
LinkBack Thread Tools Display Modes
Old 07-12-2022, 14:19   #1 (permalink)
No Life Poster
 
KrzychuG's Avatar
 
Join Date: Apr 2003
Location: Torun, Poland
Age: 40
Posts: 1,195
Member: 25996
Status: Offline
Thanks Meter: 253
Vivo V2109 - testpoint, fail [Solved]


Phone connected over testpoint is detected as bootrom, but Pandora has issues with EMI now.


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.
  Reply With Quote
Old 07-12-2022, 14:24   #2 (permalink)
Z3X
Product Supporter
 
Join Date: Feb 2008
Location: z3x
Posts: 15,938
Member: 706257
Status: Offline
Thanks Meter: 5,058
Hello. Provide screenshots please.
  Reply With Quote
Old 07-12-2022, 14:38   #3 (permalink)
No Life Poster
 
KrzychuG's Avatar
 
Join Date: Apr 2003
Location: Torun, Poland
Age: 40
Posts: 1,195
Member: 25996
Status: Offline
Thanks Meter: 253
See attachment, unless you need something specific screenshoted.
Attached Images
File Type: png Zrzut ekranu 2022-07-12 153645.png (118.2 KB, 133 views)
  Reply With Quote
Old 07-12-2022, 14:52   #4 (permalink)
Z3X
Product Supporter
 
Join Date: Feb 2008
Location: z3x
Posts: 15,938
Member: 706257
Status: Offline
Thanks Meter: 5,058
Whats phone condtition? Software cannot load emi from preloader.
  Reply With Quote
Old 07-12-2022, 15:05   #5 (permalink)
No Life Poster
 
KrzychuG's Avatar
 
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.
Attached Images
File Type: png Zrzut ekranu 2022-07-12 160301.png (114.8 KB, 76 views)
  Reply With Quote
Old 07-12-2022, 15:17   #6 (permalink)
Z3X
Product Supporter
 
Join Date: Feb 2008
Location: z3x
Posts: 15,938
Member: 706257
Status: Offline
Thanks Meter: 5,058
Last screenshot with original preloader and phone turning on?
  Reply With Quote
Old 07-12-2022, 15:22   #7 (permalink)
No Life Poster
 
KrzychuG's Avatar
 
Join Date: Apr 2003
Location: Torun, Poland
Age: 40
Posts: 1,195
Member: 25996
Status: Offline
Thanks Meter: 253
That's the picture in my previous post, yes.
  Reply With Quote
Old 07-15-2022, 11:26   #8 (permalink)
No Life Poster
 
KrzychuG's Avatar
 
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.
Attached Images
File Type: jpg v2109_v2110_tp.jpg (278.2 KB, 228 views)
  Reply With Quote
The Following 3 Users Say Thank You to KrzychuG For This Useful Post:
Show/Hide list of the thanked
Reply

Bookmarks


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


 



All times are GMT +1. The time now is 04:02.



Powered by Searchlight © 2024 Axivo Inc.
vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
- GSM Hosting Ltd. - 1999-2023 -
Page generated in 0.20661 seconds with 9 queries

SEO by vBSEO