Unconfigured Ad Widget

Collapse

Announcement

Collapse
No announcement yet.

HUAWEI RIO-L03 Factory Reset Protection Erase start gets error 398

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • HUAWEI RIO-L03 Factory Reset Protection Erase start gets error 398

    UNKNOWN ERROR (398)

    Factory reset protection Erase starts, and terminates with error 398

    First time I have used this, does anyone have an idea?

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

    DC - Unlocker 2 Client 1.00.1403

    Detecting phone :

    selection :
    manufacturer - Huawei phones
    model - Huawei phone in fastboot mode

    Found Phone : HUAWEI RIO-L03
    Model : Huawei phone in fastboot mode

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

    Factory reset protection Erase start

    unknown error (398)

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

  • #2
    Your phone asks to log in with google account when it boots up?
    >>Free Octohide VPN for Android, find it on Google Play Here<<

    Comment


    • #3
      Originally posted by Valdemaras View Post
      Your phone asks to log in with google account when it boots up?
      Should I delete the Google Account for the phone? Would that have an affect on the ability to
      unlock the phone? There is a Google account but it doesn't ask for it (since it is stored?) on boot.

      Thanks for the help.

      Comment


      • #4
        You see, whole purpose of frp erase is to remove google account sign in request from boot up screen. If you can do it manually from mobile settings then there is no point to do frp erase at all as it doesn;t do anything else.
        >>Free Octohide VPN for Android, find it on Google Play Here<<

        Comment


        • #5
          Originally posted by Valdemaras View Post
          You see, whole purpose of frp erase is to remove google account sign in request from boot up screen. If you can do it manually from mobile settings then there is no point to do frp erase at all as it doesn;t do anything else.
          I am just trying to Unlock the bootloader so I can root the device and install a CyanogenMod variant on the phone.
          How do I get on track to do that? Thanks for your help.

          Comment


          • #6
            We do not have bootloader unlock service, we can only read bootloader code from phone.

            How to read bootloader unlock code from working phone see here: https://www.dc-unlocker.com/how-to-r...er-unlock-code won’t work if device runs android 8 or later with latest security patch.
            Bootloader is unlocked from cmd/adb, can follow this guide: https://www.dc-unlocker.com/free-hua...nlock-tutorial
            >>Free Octohide VPN for Android, find it on Google Play Here<<

            Comment


            • #7
              THANKS ! I have a problem, but I was able to read the code.
              So then with fastboot, I have some inconsistent behaviors.

              C:\adb-toolkit\bin\files>fastboot devices
              3525d1b6 fastboot

              C:\adb-toolkit\bin\files>fastboot oem unlock 118369828279xxxx
              ...
              FAILED (status read failed (Too many links)) <---WHAT DOES THIS MEAN?
              finished. total time: 0.011s

              C:\adb-toolkit\bin\files>fastboot devices
              3525d1b6 fastboot

              C:\adb-toolkit\bin\files>fastboot oem unlock 118369828279xxxx
              ...
              FAILED (command write failed (Unknown error)) <----THEN GETTING THIS?
              finished. total time: 0.726s

              C:\adb-toolkit\bin\files>fastboot oem unlock 118369828279xxxx
              ...
              FAILED (command write failed (Unknown error)) <----TRY AGAIN, SAME FAIL
              finished. total time: 0.725s

              C:\adb-toolkit\bin\files>
              Maybe my problem is solved !
              I changed to a different USB cable, and repeated as below:


              C:\adb-toolkit\bin\files>fastboot devices
              3525d1b6 fastboot

              C:\adb-toolkit\bin\files>fastboot oem unlock 118369828279xxxx
              ...
              FAILED (remote: Already in UNLOCKED state)
              finished. total time: 0.011s

              C:\adb-toolkit\bin\files>

              SO LOOKS LIKE IT IS UNLOCKED !!
              THANKS FOR SO MUCH HELP !

              Comment

              Working...
              X