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) > DC Unlocker

Reply
 
LinkBack Thread Tools Display Modes
Old 05-04-2021, 05:18   #1 (permalink)
Freak Poster
 
Join Date: Dec 2006
Posts: 449
Member: 407630
Status: Offline
Thanks Meter: 29
NOVA 3e cannot be repaired


After replaceing an emmc chip,I want to repair as an empty board,I get this error logs:
2021-05-04 12:13:09.576 Repairing start
Repair as empty board
New MEID : A00000987E710F
New IMEI 1 : 867903030085952
New IMEI 2 : 867903030095969
New Bluetooth MAC : 32:14:01:E0:BA:45
New WiFi MAC : 34:14:01C:B2:07
New SN : RCDSAQQ0976VF3S2
New PCB SN : FD321A1221S3EWWQ
New Vendor : all
New Country : cn
New Model : ANE-AL00
2021-05-04 12:13:09.631 Read from server...
2021-05-04 12:13:09.957 Read from server success!
2021-05-04 12:13:13.525 Read from server...
2021-05-04 12:13:20.314 Read from server success!
2021-05-04 12:13:20.322 Writing SN...
2021-05-04 12:13:20.364 Write SN success!
2021-05-04 12:13:20.382 Writing TMMI...
2021-05-04 12:13:20.409 Write TMMI success!
2021-05-04 12:13:20.417 Writing FACINFO...
2021-05-04 12:13:20.459 Write FACINFO success!
2021-05-04 12:13:20.467 Writing RPMBKEY...
2021-05-04 12:13:20.612 Write RPMBKEY fail! AT command error
2021-05-04 12:13:20.619 Writing FINGERKEY...
2021-05-04 12:13:20.634 Write FINGERKEY success!
2021-05-04 12:13:20.947 Writing HUK...
2021-05-04 12:13:22.239 Write HUK success!
2021-05-04 12:13:22.247 Writing public keys...
2021-05-04 12:13:23.588 Write public keys fail!
2021-05-04 12:13:23.608 ERROR!
AT command error

Memo log saved to F:\BaiduNetdisk\HCU_378\Logs\20210504_121323_HCU_R epairCdma_83V1O8843218805.txt
  Reply With Quote
Old 05-04-2021, 16:08   #2 (permalink)
Product Supporter
 
Join Date: Sep 2013
Posts: 4,354
Member: 2023196
Status: Offline
Thanks Meter: 1,703
Please, provide info or add screenshot of device detection that you get before doing repairs.
  Reply With Quote
Old 05-05-2021, 04:52   #3 (permalink)
Freak Poster
 
Join Date: Dec 2006
Posts: 449
Member: 407630
Status: Offline
Thanks Meter: 29
Here is my screenshot:
Attached Images
File Type: png Image 3.png (48.4 KB, 12 views)
  Reply With Quote
Old 05-05-2021, 16:07   #4 (permalink)
Product Supporter
 
Join Date: Sep 2013
Posts: 4,354
Member: 2023196
Status: Offline
Thanks Meter: 1,703
Where is detection of device before repair, which I've asked in previous post?
  Reply With Quote
Old 05-06-2021, 02:37   #5 (permalink)
Freak Poster
 
Join Date: Dec 2006
Posts: 449
Member: 407630
Status: Offline
Thanks Meter: 29
Sorry,here is my screenshot of device detection:
Attached Images
File Type: png Image 1.png (178.1 KB, 9 views)
File Type: png Image 2.png (86.3 KB, 8 views)
  Reply With Quote
Old 05-06-2021, 15:57   #6 (permalink)
Product Supporter
 
Join Date: Sep 2013
Posts: 4,354
Member: 2023196
Status: Offline
Thanks Meter: 1,703
Please do this:
1. Restart HCU software.
2. Login with your account on software.
3. Right click on memo area make sure "enable debug logging" has a check mark.
4. Detect your device. Try to repair it, repair only model/country/vendor this time, after error do rest of the steps
5. Right click on memo area and save "debug log file".
6. Send that file to me, please.
  Reply With Quote
Old 05-07-2021, 06:08   #7 (permalink)
Freak Poster
 
Join Date: Dec 2006
Posts: 449
Member: 407630
Status: Offline
Thanks Meter: 29
here is debug log file,after repairing only mode/****ry/vendor phone always restart.
Attached Files
File Type: zip 20210507_121904_DebugLog.zip (45.8 KB, 4 views)
  Reply With Quote
Old 05-07-2021, 13:43   #8 (permalink)
Product Supporter
 
Join Date: Sep 2013
Posts: 4,354
Member: 2023196
Status: Offline
Thanks Meter: 1,703
Quote:
Originally Posted by xiakaijun View Post
here is debug log file,after repairing only mode/****ry/vendor phone always restart.
But did it give any errors during repair or just phone in bootloop afterwards? From what it looks now your board software either not fully flashed or phone is damaged and not ready to be repaired as empty board.

Last edited by Namelocked; 05-07-2021 at 14:03.
  Reply With Quote
Old 05-08-2021, 02:38   #9 (permalink)
Freak Poster
 
Join Date: Dec 2006
Posts: 449
Member: 407630
Status: Offline
Thanks Meter: 29
DC Phoenix 0.0.0.153
user:01325041

Looking for a device in testpoint mode
Device detected:
COM17: HUAWEI USB COM 1.0 (COM17)

Standard update
Not Reboot NOT checkked
Update Verlist to server on file load NOT checked
Enable testpoint NOT checked
Disable testpoint NOT checked
Try Rescue Recovery NOT checked
Bypass version check NOT checked
Old slow algo NOT checked

2021/5/8 9:21:51 Starting to write device in FASTBOOT mode...
File to update: F:\华为刷机资料\Kirin659\NOVA 3E ANE-AL00\ANE-Full-Repair-NV-included-Board-A039-8.0.0.dgtks
Device detected:
COM17: HUAWEI USB COM 1.0 (COM17)

Process identifier:31325364


Writing bootloader...
Step 1...
Step 2...

Waiting for device REMOVAL/INSERTION...
REMOVAL/INSERTION wait result: iUsbProc.DisConnect:True; iUsbProc.Connect:False; Elapsed time:60319; Waitfor:60000

Waiting for fastboot device...
Device found: OM6B0D4582533956


Looking for a device in fastboot mode
Device found: OM6B0D4582533956


Getting IMEI...
Getting build number...
Getting model ...
Getting battery state...
Getting backdoor info...
Getting lock state info...
Getting lock boot info...

Build number: :System-FAC 8.0.1.044(00BV)
Model: ANE-AL00
Vendor/Country: all/cn
Battery state: 4237mv
OEM lock state info:
FB LockState: UNLOCKED
USER LockState: LOCKED
OEM get bootinfo:
unlocked



Waiting for OEM erase_storage_all command ...OK

Waiting for device REMOVAL/INSERTION...

USB Device REMOVAL
Type: @oem20.inf,%hwfastboot%;Android Sooner Single ADB Interface
VidPid: VID_18D1&PID_D00D
Instance id: OM6B0D4582533956
REMOVAL/INSERTION wait result: iUsbProc.DisConnect:True; iUsbProc.Connect:False; Elapsed time:60099; Waitfor:60000

Device detected:
COM17: HUAWEI USB COM 1.0 (COM17)

Writing bootloader...
Step 1...
Step 2...

Waiting for device REMOVAL/INSERTION...
REMOVAL/INSERTION wait result: iUsbProc.DisConnect:True; iUsbProc.Connect:False; Elapsed time:60191; Waitfor:60000

Waiting for fastboot device...
Device found: 0123456789ABCDEF


Looking for a device in fastboot mode
Device found: 0123456789ABCDEF


Getting IMEI...
Getting build number...
Getting model ...
Getting model by product ...
Getting model by roduct ...
Getting battery state...
Getting backdoor info...
Getting lock state info...
Getting lock boot info...

Model: hi6250
Battery state: 0
OEM lock state info:
FB LockState: UNLOCKED
USER LockState: LOCKED
OEM get bootinfo:
unlocked


Writing xloader partition
XLOADER partition update ...OK

Writing ptable partition
PTABLE partition update ...OK

Writing fastboot partition
FASTBOOT partition update ...OK

Writing dts partition
DTS partition update ...OK

Writing fw_lpm3 partition
FW_LPM3 partition update ...OK

Writing sensorhub partition
SENSORHUB partition update ...OK

Writing fw_hifi partition
FW_HIFI partition update ...OK

Writing teeos partition
TEEOS partition update ...OK

Writing recovery_vbmeta partition
RECOVERY_VBMETA partition update ...OK

Erasing cache partition
Partition cache erased
Writing cache partition
CACHE partition update ...OK

Writing nvme partition
NVME partition update ...OK

Writing trustfirmware partition
TRUSTFIRMWARE partition update ...OK

Writing modem_fw partition
MODEM_FW partition update ...OK

Writing modemnvm_update partition
MODEMNVM_UPDATE partition update ...OK

Writing modem_om partition
MODEM_OM partition update ...OK

Writing modemnvm_img partition
MODEMNVM_IMG partition update ...OK

Writing modemnvm_backup partition
MODEMNVM_BACKUP partition update ...OK

Writing modemnvm_factory partition
MODEMNVM_FACTORY partition update ...OK

Writing modemnvm_system partition
MODEMNVM_SYSTEM partition update ...OK

Erasing userdata partition
Partition userdata erased
Writing userdata partition
USERDATA partition update ...OK

Writing system partition
sending sparse file 413714128 bytes
Waiting for answer...
send sparse file OK
sending sparse file 471379936 bytes
Waiting for answer...
send sparse file OK
sending sparse file 463200008 bytes
Waiting for answer...
send sparse file OK
sending sparse file 77705316 bytes
Waiting for answer...
send sparse file OK
SYSTEM partition update ...OK

Writing vendor partition
sending sparse file 459899448 bytes
Waiting for answer...
send sparse file OK
sending sparse file 146912472 bytes
Waiting for answer...
send sparse file OK
VENDOR partition update ...OK

Writing product partition
PRODUCT partition update ...OK

Writing version partition
VERSION partition update ...OK

Writing splash2 partition
SPLASH2 partition update ...OK

Writing frp partition
FRP partition update ...OK

Writing oeminfo partition
OEMINFO partition update ...OK

Writing secure_storage partition
SECURE_STORAGE partition update ...OK

Writing modem_secure partition
MODEM_SECURE partition update ...OK

Writing kernel partition
KERNEL partition update ...OK

Writing ramdisk partition
RAMDISK partition update ...OK

Writing recovery_ramdisk partition
RECOVERY_RAMDISK partition update ...OK

Writing recovery_vendor partition
RECOVERY_VENDOR partition update ...OK

Writing vbmeta partition
VBMETA partition update ...OK

Writing odm partition
ODM partition update ...OK
Software written
2021/5/8 9:36:44 Writing device finished OK
  Reply With Quote
Old Today, 15:13   #10 (permalink)
Product Supporter
 
Join Date: Sep 2013
Posts: 4,354
Member: 2023196
Status: Offline
Thanks Meter: 1,703
This leads only to assumption that part of phone's board is damaged since model/country/vendor repair worked without errors as visible from the logs.
  Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

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 23:18.



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

SEO by vBSEO