Unconfigured Ad Widget

Collapse

Announcement

Collapse
No announcement yet.

HCU: 'Phone secure identify fail' on Mediapad M1 S8-301U (velcom)

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    HCU: 'Phone secure identify fail' on Mediapad M1 S8-301U (velcom)

    I was trying to do a carrier unlock using the HCU client software without a dongle and it wouldn't work. HCU was somewhat successful at detecting the phone and reading the essential info, but DC-unlocker itself wouldn't even detect the phone. It seems that my phone should not be supported, however here it is listed as unlockable in the supported models page. I was foolish enough to lose the log, but it was very uneventful anyway. The message was something like 'Phone secure identify fail: unknown response' just after a successful 'read phone secure info' operation. The USB communication captured with Wireshark is attached to this message ( I probably got banned for doing this, as the program now refuses to connect to the server because it has detected some apparently suspicious processes. But this was sort of a last measure.). The phone doesn't want to reveal its oeminfo, as far as I can tell from this dump. If any of the devs are interested in the technicalities of this issue, I would be happy to provide TeamViewer access to the machine.
    Is it feasible at all to unlock this phone, or returning it to the seller would be a safer bet?
    USB dump: HUAWEI_S8-301U_HCU_Fail_USBdump_fed0r.zip
    Last edited by fed0r; 2016-05-07, 06:15 PM.
    Tags: None
  • #2
    Please write your username.

    Comment

    • #3
      My username is fed0r. I've purchased dc-unlocker credits through uo5oq.com service, so I don't even know the email.

      Comment

      • #4
        Originally posted by fed0r View Post
        My username is fed0r. I've purchased dc-unlocker credits through uo5oq.com service, so I don't even know the email.
        Please do this:
        1. Restart DC-Unlocker software.
        2. Go to Server tab, press check login.
        3. Try to Detect your device, if not possible do rest of the steps
        4. After that, go to Options tab.
        5. Click "Save log".
        6. Send that file to me, please.
        >>Free Octohide VPN for Android, find it on Google Play Here<<

        Comment

        • #5
          DC-unlocker just hangs up on detecting the phone (waited for it for >10 min) regardless of settings used. Mind you, I've got HiSuite installed and phone put into maintenance mode.
          HCU's autodetect doesn't work correctly either, it fails to detect the CPU type and the COM port. Sometimes it fails to detect anything, other times it wrongly shows that I have a Qualcomm device at COM4 (DBAdapter Reserved Interface), whereas I have a HiSilicon and the only port that gives a meaningful response is COM5 (Android Adapter Modem). COM6 (Android adapter PCUI) does not work due to a write error:
          Code:
          2016-05-10 17:12:07.348  Debug Log Enabled!
2016-05-10 17:12:07.364 Start read phone info!
2016-05-10 17:12:07.364 Open COM port COM6 (Android Adapter PCUI (COM6))...
2016-05-10 17:12:07.707 ERROR!

Write to port error!
          Setting the connection parameters manually yields the following output:
          Code:
          5/10/2016 4:56:35 PM
HCU Client   v1.0.0.0013

Before detection connect cable to usb and enable Manufacture mode !

Qualcomm and HiSilicon: *#*#2846579#*#*
MTK: *#*#14789632#*#*
Windows: ##2846579#

ProjectMenu
1.Background setting
2.USB ports setting
Select Manufacture mode

Before detection connect cable to usb and enable Manufacture mode !

*#*#2846579#*#*
ProjectMenu
1.Background setting
2.USB ports setting
Select Manufacture mode

Select Android Adapter PCUI COM port

2016.05.10 16:56:53.243 Checking account fed0r...
2016-05-10 16:56:53.258 Connecting to server...
2016-05-10 16:56:56.067 Connected!

Account: fed0r
Check success!

Credits left: 3
Valid till 6/5/2016

2016-05-10 16:56:56.839  Debug Log Enabled!

2016.05.10 16:56:59.647 Checking account fed0r...
2016-05-10 16:56:59.647 Connecting to server...
2016-05-10 16:57:02.368 Connected!

Account: fed0r
Check success!

Credits left: 3
Valid till 6/5/2016

2016-05-10 16:57:03.045  Debug Log Enabled!
2016-05-10 16:57:03.076 Start read phone info!
2016-05-10 16:57:03.092 Open COM port COM5 (Android Adapter Modem)...
2016-05-10 16:57:03.217 Read phone basic info...
2016-05-10 16:57:05.064 Read phone secure info...
2016-05-10 16:57:10.714 Read phone info done!

IMEI: ################ <Correct IMEI>
IMEISV: 00
Firmware ver.: (unknow)
SN: ################ <Some serial number>
Custom SN: ############## <Another serial>
WiFi MAC: ##:##:##:##:##:## <Correct MAC>
BlueTooth MAC:  ##:##:##:##:##:## <Correct MAC>
FASTBOOT:S8-30XlV100R001C001B010SP33_FASTBOOT
BOOT:(unknow)
RECOVERY:(unknow)
SYSTEM:(unknow)
MAINVER:(unknow)
APTIME:Thu Jul 24 19:17:49 CST 2014
RAM: 1G
eMMC: 8G

IMEI 1 Sim Lock status:
NET: locked, unlock retry counts: 10
NETSUB: unlocked
SP: unlocked
Fastboot LockStatus: locked

<SIM unlock started>

2016-05-10 16:57:27.711 Open COM port COM5 (Android Adapter Modem)...
2016-05-10 16:57:27.852 Connecting to server...
2016-05-10 16:57:30.492 Connected!
2016-05-10 16:57:30.492 Read from server...
2016-05-10 16:57:31.008 Read from server success!
2016-05-10 16:57:31.023 Unlocking start
2016-05-10 16:57:31.023 Read phone secure info...
2016-05-10 16:57:37.632 Read phone secure info success!
2016-05-10 16:57:37.632 Read phone basic info...
2016-05-10 16:57:41.492 Read phone basic info success!
2016-05-10 16:57:41.492 Phone secure identify start
2016-05-10 16:57:43.148 Phone secure identify fail!
unknown responce!
2016-05-10 16:57:43.164 ERROR!
unknown responce!

Saving debug log to file...
          That scenario is virtually the same as in the Wireshark dump mentioned in the first post.
          I'm attaching the HCU debug logs to this message, it seems that they are encrypted and a layperson couldn't extract the serials easily (not that I would care even if they can).
          fed0r_Huawei_s8301u_HCU_autodetect_fail.zip
          fed0r_Huawei_s8301u_HCU_manual_unlock_fail.zip
          Last edited by fed0r; 2016-05-10, 02:29 PM. Reason: added files

          Comment

          • #6
            Some magic has happened and DC-unlocker didn't hang up this time. Here is the log file:
            Code:
            Check account status

User         : fed0r
Credits left : 3

Activated features:

Software debugger

2016.05.10 17:40:02.663 Logging enabled !

===================================================================

===================================================================

DC - Unlocker 2 Client 1.00.1290

Detecting phone :

selection :
manufacturer - Huawei phones
model - Auto detect (recommended)

Found Applications port COM6
Found Diagnostics port COM4

Phone not found !

===================================================================
            fed0r_Huawei_s8301u_DCUnlocker_notdetect_fail.zip
            Attached Files

            Comment

            • #7
              Detect your device on HCU module http://hcu-client.com/ since dc-unlocker is not compatible with s8.
              >>Free Octohide VPN for Android, find it on Google Play Here<<

              Comment

              • #8
                I've just tried HCU module 1.0.0.0035 and this gives the exact same result as with the older version (0013). Please see my previous post for the log files.

                Comment

                • #9
                  Then no way to unlock it.
                  >>Free Octohide VPN for Android, find it on Google Play Here<<

                  Comment

                  • #10
                    Thank you for looking into the issue. Now that it is clear that the phone model is not supported, would you mind removing it from the list to avoid further confusion of HCU users?

                    Comment

                    Previous template Next
                    Working...
                    X

                    We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.

                    By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.

                    I Agree