Legitunlocks.com
Martview RB-02

xiaomi Redmi Note 8(ginkgo) Dead after isp pinout please help me

B

bambinogsm

Active Member
May 26, 2020
15
0
egypt
my phone proplem is hang on logo
after flashing now only 9008 com port and phone is dead

Connection status: XHCI:HUB3:USB 2.00 High-Speed
Interface: UFI High-Speed
Serial number: 0011-8839-****
Boot version: 1.04, FW version: 1.13 (Aug 19 2019 23:46:09)
Insertion test... Done
Init bus...
VCC: 3.3 V, VCCQ: 1.8 V
Bus: 1 bit (SDR 4MHz)
Access mode: sector mode
Power supply: dual-voltage (1.70-1.95V, 2.7-3.6V)
Card/BGA: BGA (Discrete embedded) - High density MMC
Manufacturer ID: 0x13 (Micron)
Product name: S0J9K8 (0x53304a394b38), rev: 0x10, serial number: 0x134B62AA
Manufacturing date: Sep 2019
CID: 13014E53 304A394B 3810134B 62AA968E
CSD: D05F0132 8F5913FF FFFFFFEF 964000A8
EXT_CSD revision: 1.8 (MMC v5.1)
Partition info:
Boot1: 4096 KiB
Boot2: 4096 KiB
RPMB: 16384 KiB
User area: 58.24 GiB(62,537,072,640 bytes)
Cache size: 2 MiB
Hardware reset function: 1
Partition configuration: 0x38
No boot acknowledge is sent (default)
User area is enabled for boot
Partitioning support: 0x07
Device support partitioning feature
Device can have enhanced technological features
Device partitioning possible
Boot configuration protection: 0x00
Boot bus conditions: 0x00
Boot area write protection: 0x00
Power-on write protection: possible
Permanent write protection: possible
Lock status: not locked

ANDROID System Info:
platform: trinket, cpu abi: arm64-v8a
manufacturer: Xiaomi
board: ginkgo, name: ginkgo
brand: xiaomi, model: Redmi Note 8
build model list: Redmi Note 8
build id: PKQ1.190616.001, version: 9 Pie (PKQ1.190616.001)
build description: ginkgo-user 9 PKQ1.190616.001 V11.0.8.0.PCOMIXM release-keys

Internal storage: 48.95 GiB
crypto state: unencrypted


eMMC 5.x HEALTH report:
Device lifetime: Normal
Estimation of the device lifetime (SLC): 0% - 10% device life time used
Estimation of the device lifetime (MLC): 0% - 10% device life time used
 
K

kadarabu915

Active Member
Dec 31, 2019
29
5
bambinogsm said:
my phone proplem is hang on logo
after flashing now only 9008 com port and phone is dead

Connection status: XHCI:HUB3:USB 2.00 High-Speed
Interface: UFI High-Speed
Serial number: 0011-8839-****
Boot version: 1.04, FW version: 1.13 (Aug 19 2019 23:46:09)
Insertion test... Done
Init bus...
VCC: 3.3 V, VCCQ: 1.8 V
Bus: 1 bit (SDR 4MHz)
Access mode: sector mode
Power supply: dual-voltage (1.70-1.95V, 2.7-3.6V)
Card/BGA: BGA (Discrete embedded) - High density MMC
Manufacturer ID: 0x13 (Micron)
Product name: S0J9K8 (0x53304a394b38), rev: 0x10, serial number: 0x134B62AA
Manufacturing date: Sep 2019
CID: 13014E53 304A394B 3810134B 62AA968E
CSD: D05F0132 8F5913FF FFFFFFEF 964000A8
EXT_CSD revision: 1.8 (MMC v5.1)
Partition info:
Boot1: 4096 KiB
Boot2: 4096 KiB
RPMB: 16384 KiB
User area: 58.24 GiB(62,537,072,640 bytes)
Cache size: 2 MiB
Hardware reset function: 1
Partition configuration: 0x38
No boot acknowledge is sent (default)
User area is enabled for boot
Partitioning support: 0x07
Device support partitioning feature
Device can have enhanced technological features
Device partitioning possible
Boot configuration protection: 0x00
Boot bus conditions: 0x00
Boot area write protection: 0x00
Power-on write protection: possible
Permanent write protection: possible
Lock status: not locked

ANDROID System Info:
platform: trinket, cpu abi: arm64-v8a
manufacturer: Xiaomi
board: ginkgo, name: ginkgo
brand: xiaomi, model: Redmi Note 8
build model list: Redmi Note 8
build id: PKQ1.190616.001, version: 9 Pie (PKQ1.190616.001)
build description: ginkgo-user 9 PKQ1.190616.001 V11.0.8.0.PCOMIXM release-keys

Internal storage: 48.95 GiB
crypto state: unencrypted


eMMC 5.x HEALTH report:
Device lifetime: Normal
Estimation of the device lifetime (SLC): 0% - 10% device life time used
Estimation of the device lifetime (MLC): 0% - 10% device life time used
Click to expand...
Hi Bro check clk, cmd and dato lines
 
K

kadarabu915

Active Member
Dec 31, 2019
29
5
I don't have any redmi note 8 mobile and dump file.so iam verify with some members after post it

Sent From vivo 1818 Using Martview Forum App
 
K

kosovo37

Active Member
Feb 20, 2020
29
2
I have dumped all partitions from a Ginkgo global 11.0.6.0 rom after dumping and writing mi account remove files phone becomes dead, but I used Medusa Pro, after writing backup back phone booted in bootlop, writen mi account files again and phone didn't boot any more, I have tried to update miui rom via isp with no sucess.
 
  • Like
Reactions: olawale2017
O

olawale2017

Member
Oct 11, 2017
9
1
lagos
kosovo37 said:
I have dumped all partitions from a Ginkgo global 11.0.6.0 rom after dumping and writing mi account remove files phone becomes dead, but I used Medusa Pro, after writing backup back phone booted in bootlop, writen mi account files again and phone didn't boot any more, I have tried to update miui rom via isp with no sucess.
Click to expand...
I have same problem how can i fix this please. I was told short clk . is it to connect both end of the clk resistor together?. Thanks group.
 
K

kosovo37

Active Member
Feb 20, 2020
29
2
olawale2017 said:
I have same problem how can i fix this please. I was told short clk . is it to connect both end of the clk resistor together?. Thanks group.
Click to expand...
The problem is not related with hardware, the problem is that MI account remove files for some reason changed boot config in the ext_csd data, check your first log when the phone was alive, and compare it with the data you are reading from the phone now its dead, and you will see that it changed, set the config as it was before and then full flash and phone will boot again.

That's what I did with mine and I solved the problem.
The only thing I haven't solve yet it's I haven't recovered both imeis and I have a full dump.
 
O

olawale2017

Member
Oct 11, 2017
9
1
lagos
kosovo37 said:
The problem is not related with hardware, the problem is that MI account remove files for some reason changed boot config in the ext_csd data, check your first log when the phone was alive, and compare it with the data you are reading from the phone now its dead, and you will see that it changed, set the config as it was before and then full flash and phone will boot again.

That's what I did with mine and I solved the problem.
The only thing I haven't solve yet it's I haven't recovered both imeis and I have a full dump.
Click to expand...
That process when it flash completely, and yet device in download mode 9008.
 
manowar khan111

manowar khan111

Junior Member
Feb 26, 2021
1
0
dhubri assam
Interface: UFI High-Speed
Serial number: 0011-8843-1247
Boot version: 1.05, FW version: 1.13 (Aug 19 2019 23:46:09)
Insertion test... Done
Init bus...
VCC: 3.3 V, VCCQ: 1.8 V
Bus: 1 bit (SDR 4MHz)
Access mode: sector mode
Power supply: dual-voltage (1.70-1.95V, 2.7-3.6V)
Card/BGA: BGA (Discrete embedded) - High density MMC
Manufacturer ID: 0x90 (SK Hynix)
Product name: hC8aP (0x68433861503e), rev: 0x03, serial number: 0xA14B2EF4
Manufacturing date: Aug 2019
CID: 90014A68 43386150 3E03A14B 2EF48622
CSD: D0270032 8F5903FF FFFFFFEF 8E400042
EXT_CSD revision: 1.8 (MMC v5.1)
Partition info:
Boot1: 4096 KiB
Boot2: 4096 KiB
RPMB: 16384 KiB
User area: 58.24 GiB(62,537,072,640 bytes)
Cache size: 2 MiB
Hardware reset function: 1
Partition configuration: 0x38
No boot acknowledge is sent (default)
User area is enabled for boot
Partitioning support: 0x07
Device support partitioning feature
Device can have enhanced technological features
Device partitioning possible
Boot configuration protection: 0x00
Boot bus conditions: 0x00
Boot area write protection: 0x00
Power-on write protection: possible
Permanent write protection: possible
Lock status: not locked

ANDROID System Info:
platform: trinket, cpu abi: arm64-v8a
manufacturer: Xiaomi
board: ginkgo, name: ginkgo
brand: xiaomi, model: Redmi Note 8
build model list: Redmi Note 8
build id: PKQ1.190616.001, version: 9 Pie (PKQ1.190616.001)
build description: ginkgo-user 9 PKQ1.190616.001 V10.3.3.0.PCOINXM release-keys

Internal storage: 48.95 GiB
crypto state: unencrypte only qualcom port
 
You must log in or register to reply here.
Top