Motorola XT1644 No Service - Moto G4 Plus Questions & Answers

i got 3 phones with the same problem. phone is brand new never used... BUT one this written on top is MOTOROLA CONFIDENTIAL PROPERTY: NOT FOR SALE... so i wonder is this possible to get signal on this device?
i flashed with XT1644_ATHENE_RETUS_MPJ24.139-48_cid50_subsidy-DEFAULT_regulatory-XT1644_CFC.xml but problem is the same... when search for network it shows "error while searching network".
here is fastboot info
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B0.0E(*)
(bootloader) product: Athene_16MP
(bootloader) board: Athene_16MP
(bootloader) secure: no
(bootloader) hwrev: P1A
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB TOSHIBA 032G32 RV=08 PV=00 FV=0000000000000003
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: NADI110010
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 7C0B3E0000000000000000000000
(bootloader) securestate: engineering
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 3541150xxxxxxxx
(bootloader) meid:
(bootloader) date: 12-24-2015
(bootloader) sku: XTBLAH
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jul 29 4:38:35 UTC 1971"
(bootloader) ro.build.fingerprint[0]: motorola/athene/athene:6.0.1/MPJ24
(bootloader) ro.build.fingerprint[1]: .139-48/48:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.31.48.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.3-02720-8976.0
(bootloader) version-baseband: M8952_70009.08.03.45R DFLT_FSG
(bootloader) kernel.version[0]: Linux version 3.10.84-g06a4fb5 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld35) (gcc version 4.9.x-google 20
(bootloader) kernel.version[2]: 140827 (prerelease) (GCC) ) #1 SMP PREEM
(bootloader) kernel.version[3]: PT Sun Jun 5 11:16:49 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VB0.0E-0-g83950b7
(bootloader) rpm.git: git=1dc910e
(bootloader) tz.git: git=9fa1804
(bootloader) hyp.git: git=9fa1804
(bootloader) keymaster.git: git=9fa1804
(bootloader) cmnlib.git: git=9fa1804
(bootloader) aboot.git: git=MBM-NG-VB0.0E-0-g4986429
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.129s

nomi_42us said:
i got 3 phones with the same problem. phone is brand new never used... BUT one this written on top is MOTOROLA CONFIDENTIAL PROPERTY: NOT FOR SALE... so i wonder is this possible to get signal on this device?
i flashed with XT1644_ATHENE_RETUS_MPJ24.139-48_cid50_subsidy-DEFAULT_regulatory-XT1644_CFC.xml but problem is the same... when search for network it shows "error while searching network".
Click to expand...
Click to collapse
Try different SIM card

HueyT said:
Try different SIM card
Click to expand...
Click to collapse
Already did but same problem

nomi_42us said:
Already did but same problem
Click to expand...
Click to collapse
Try to cut a piece of 3"X5" index card to same size as sim card and put it under sim as you're inserting into slot. Maybe this will improve contact to phone? Otherwise, I have no clue if you still have this problem after reflashing N stock rom using FASTBOOT.

HueyT said:
Try to cut a piece of 3"X5" index card to same size as sim card and put it under sim as you're inserting into slot. Maybe this will improve contact to phone? Otherwise, I have no clue if you still have this problem after reflashing N stock rom using FASTBOOT.
Click to expand...
Click to collapse
there is no sim tray/slot in this model. sim is directly inserted in phone... anyone else have any clue?

nomi_42us said:
there is no sim tray/slot in this model. sim is directly inserted in phone... anyone else have any clue?
Click to expand...
Click to collapse
How are you inserting your SIM card into your device?
Hmm, that device does not look healthy regardless:
1) If this was a genuine engineering sample, then it may have certain functions disabled depending on what stage of development it came from. The IMEI may also not be registered. Alternatively, it might have been misflashed before you got it.
2)CID of 0xDEAD and a baseband of DFLT_FSG suggest a bad flash too. I don't know if flashing a correct HW partition to the device would allow it to recognise the SIM (or at least assign the correct radio settings).
3)Attempting to flash further on engineering state devices might cause boot looping as pointed out by acejavelin https://forums.lenovo.com/t5/MOTORO...g-and-Unlocked-bootloader-status/td-p/3420219
I'd suggest, if you can, to return the phone and get a refund, this device might be more trouble than it's worth.

there is inside info from phone. and i do repair phones and customer gave me even dead warranty so i can do all tries without worry, so if there is any possible solution i am willing to try...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

nomi_42us said:
there is inside info from phone. and i do repair phones and customer gave me even dead warranty so i can do all tries without worry, so if there is any possible solution i am willing to try...
Click to expand...
Click to collapse
Stick an active SIM card from your cell provider in SIM1 slot. The far left is MicroSD. The middle one is SIM1. The far right is SIM2.

HueyT said:
Stick an active SIM card from your cell provider in SIM1 slot. The far left is MicroSD. The middle one is SIM1. The far right is SIM2.
Click to expand...
Click to collapse
already tried that one also as per my knowledge network is locked because of test unit. i want to gain access by any way. because radio is always off. want to know is it possible to turn it on?

nomi_42us said:
already tried that one also as per my knowledge network is locked because of test unit. i want to gain access by any way. because radio is always off. want to know is it possible to turn it on?
Click to expand...
Click to collapse
Try the Secret menu in phone dialer to enable radio :
*#*#4636#*#*
then chose "enable radio" mode or change to "USA band" on upper right corner of menu.

Its easy too fix if you are in Pk,
karachi.
nomi_42us said:
there is inside info from phone. and i do repair phones and customer gave me even dead warranty so i can do all tries without worry, so if there is any possible solution i am willing to try...
Click to expand...
Click to collapse

Salik Iqbal said:
Its easy too fix if you are in Pk,
karachi.
Click to expand...
Click to collapse
i am not in karachi but if you give me working solution i can pay you for that

nomi_42us said:
i am not in karachi but if you give me working solution i can pay you for that
Click to expand...
Click to collapse
check your imei, it could be zero (0).
if it is, you need to change your modem to dsds.
read this guide its for z play, but you can apply it to g4 plus also
https://forum.xda-developers.com/moto-z-play/how-to/guide-to-enable-dualsim-singlesim-t3570601

Related

Fastboot oem commands

Some of these commands can and will brick your phone.
Maybe this will be usefull.
fastboot oem
(bootloader) command list
(bootloader) dmesg
(bootloader) last_dmesg
(bootloader) clearaspflag
(bootloader) refurbish
(bootloader) get_identifier_token
(bootloader) checkKeycardID
(bootloader) get_tamper_flag
(bootloader) checkSbl1
(bootloader) checkHWSecurity
(bootloader) enter
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) erase_phone_storage
(bootloader) erase_nfc_record
(bootloader) gotohboot
(bootloader) resetgift
(bootloader) ats
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloader) readmeid
(bootloader) readpid
(bootloader) writepid
(bootloader) readcid
(bootloader) writecid
(bootloader) readimei
(bootloader) writeimei
(bootloader) readsecureflag
(bootloader) writesecureflag
(bootloader) ddr2gbh
(bootloader) ramdump2gbh
(bootloader) ddr2gstatus
(bootloader) get_temp
(bootloader) writemeid
(bootloader) lock
(bootloader) readusername
(bootloader) writeusername
(bootloader) resethtcdebugflag
(bootloader) load_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) load_modem_emmc
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
i dont understand how do you use it?
fasboot oem readcid?
hamdir said:
i dont understand how do you use it?
fasboot oem readcid?
Click to expand...
Click to collapse
Yes, in fastboot usb you have to type:
Code:
fastboot oem readcid
and you can see your cid.
You can use
Code:
fastboot getvar cid
too
what's refurbish for?
fastboot oem get_identifier_token...
shiningarmor said:
what's refurbish for?
Click to expand...
Click to collapse
I'm curious too. Refurbish sounds exciting. Someone should try it!
Sent from my HTC One
I will try ...
ECEXCURSION said:
I'm curious too. Refurbish sounds exciting. Someone should try it!
Sent from my HTC One
Click to expand...
Click to collapse
wouterx said:
I will try ...
Click to expand...
Click to collapse
[email protected]*******:~$ fastboot oem refurbish
< waiting for device >
...
(bootloader) Start Verify: 3
(bootloader) Start Verify: 3
(bootloader) Boot/Recovery signature checking...
(bootloader) TZ_HTC_SVC_HASH ret = 0
(bootloader) setup_tag addr=0x80600100 cmdline add=0x00347020
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:skuid 0x34C0C
(bootloader) TAG:hero panel = 0x940069
(bootloader) TAG:engineerid = 0x0
(bootloader) TAG: PS ID = 0x0
(bootloader) TAG: Gyro ID = 0x2
(bootloader) Device CID is not super CID
(bootloader) CID is HTC__E11
(bootloader) setting->cid::HTC__E11
(bootloader) serial number: FA354W903578
(bootloader) commandline from head: console=ttyHSL0,115200,n8 androidboot
(bootloader) .hardware=m7 user_debug=31
(bootloader) command line length =866
(bootloader) active commandline: poweron_status=1 reset_status=0 board_m7
(bootloader) _ul.disable_uart3=0 diag.enabled=0 board_m7_ul.debug_uart=0
(bootloader) userdata_sel=0 androidboot.emmc=true androidboot.pagesize=20
(bootloader) 48 skuid=0 ddt=20 ats=0 dap=6 androidboot.lb=1 uif=O000 td.
(bootloader) sf=1 td.td=1 td.ofs=328 td.prd=1 td.dly=0 td.tmo=300 hlog.of
(bootloader) s=628 un.ofs=694 imc_online_log=0 androidboot.efuse_info=2N
(bootloader) SL androidboot.baseband=4A.14.3250.13 androidboot.cid=HTC__E
(bootloader) 11 androidboot.devicerev=3 androidboot.batt_poweron=good_bat
(bootloader) tery androidboot.car
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=local
(bootloader) aARM_Partion[5].name=cache
(bootloader) aARM_Partion[6].name=userdata
(bootloader) aARM_Partion[7].name=devlog
(bootloader) aARM_Partion[8].name=pdata
(bootloader) aARM_Partion[9].name=extra
(bootloader) aARM_Partion[A].name=radio
(bootloader) aARM_Partion.name=adsp
(bootloader) aARM_Partion[C].name=dsps
(bootloader) aARM_Partion[D].name=radio_config
(bootloader) aARM_Partion[E].name=modem_st1
(bootloader) aARM_Partion[F].name=modem_st2
(bootloader) aARM_Partion[10].name=cdma_record
(bootloader) aARM_Partion[11].name=reserve_1
(bootloader) aARM_Partion[12].name=reserve_2
(bootloader) aARM_Partion[13].name=reserve_3
(bootloader) aARM_Partion[14].name=reserve
(bootloader) partition number=21
(bootloader) Valid partition num=21
(bootloader) setting_get_bootmode() = 3
(bootloader) smem 8CF04000 (phy 8CF04000): TZ_HTC_SVC_UPDATE_SMEM ret = 0
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) Start Verify: 3
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) TZ_HTC_SVC_DISABLE ret = 205643776 (0xC41E000)
(bootloader) [PARTITION_ERR] partition_write_prot_emmc: Cannot find end p
(bootloader) artition [modem]
(bootloader) msm_mpu_emmc_protect: set write protection fail (from reserv
(bootloader) e_2 to modem)
(bootloader) Start Verify: 3
(bootloader) [RUMBA_S] firmware version: 3-45-43-33-0-0-0-0
(bootloader) [RUMBA_S] ondevice version: 3-45-43-33-4-28-A3-0
(bootloader) [RUMBA_S] firmware version already up-to-date
(bootloader) pm8921_vreg_disable function, vreg_id = 7
(bootloader) pm8921_vreg_disable function, vreg_id = 37
(bootloader) pm8921_vreg_disable function, vreg_id = 34
(bootloader) pm8921_vreg_disable function, vreg_id = 8
(bootloader) jump_to_kernel: machine_id(4308), tags_addr(0x80600100), ker
(bootloader) nel_addr(0x80608000)
(bootloader) -------------------hboot boot time:46925 msec
FAILED (status read failed (No such device))
finished. total time: 8.247s
In the end its boots in ClockworkMod Recovery....
bump! as we have s off for all!!!
Hey guys.
So, I'll be direct. None command worked on my RAZR D3.
Maybe fast boot have a limitation or some kind like that.
Did you see something like this?
Please, if you did, "quote me"hehe
Adriano-A3 said:
Hey guys.
So, I'll be direct. None command worked on my RAZR D3.
Maybe fast boot have a limitation or some kind like that.
Did you see something like this?
Please, if you did, "quote me"hehe
Click to expand...
Click to collapse
I think different hboots have different commands available, so between devices its likely that they will be different also.
Lol that's a very bad idea to post all those commands
If you dont know what it does.....don't use it!
Sent from my HTC One using xda app-developers app
zaphodbeeb said:
I think different hboots have different commands available, so between devices its likely that they will be different also.
Click to expand...
Click to collapse
Most of these commands are HTC-specific. They ain't gonna work on other phones.
Every phone has it's own set of "fastboot oem" commands, only the "fastboot" commands are universal.
Apart from that, Motorola phones don't use HBOOT(HTC BOOT). AFAIK they use a customized ABOOT.
Adriano-A3 said:
Hey guys.
So, I'll be direct. None command worked on my RAZR D3.
Please, if you did, "quote me"hehe
Click to expand...
Click to collapse
You should try on your Nokia 3310!
These commands are OEM-specific, i.e. not common for Android project.
need help
please "fastboot oem writeimei" gives command error please what can i do...
Sammie5 said:
please "fastboot oem writeimei" gives command error please what can i do...
Click to expand...
Click to collapse
you can't change the IMEI using this command and changing the IMEI number might be illegal in your country.
alray said:
you can't change the IMEI using this command and changing the IMEI number might be illegal in your country.
Click to expand...
Click to collapse
its not illegal here because i need to change it to connect to internet for some service providers
and please what is the command
Sammie5 said:
its not illegal here because i need to change it to connect to internet for some service providers
and please what is the command
Click to expand...
Click to collapse
There is no command to change the imei number and if you need to change your imei it means your phone is declared lost or stolen/linked to unpaid bills.
alray said:
There is no command to change the imei number and if you need to change your imei it means your phone is declared lost or stolen/linked to unpaid bills.
Click to expand...
Click to collapse
so it cant be changed?
Sammie5 said:
so it cant be changed?
Click to expand...
Click to collapse
short answer, no
sorry

failed to unlock bootloader moto x play 6 (with fastboot)

Hi everybody,
I have a moto x play updated to 6.0 official that i am trying to unlock to root but so far failed.
I have installed ALL drivers then uninstalled then reinstalled more than five times but still failed to get unlock string.
The device is seen in adb/fastboot and the bootloader logs on the device show the commands i am sending but it still says failed try again.
I have followed all advice given on the other posts but same message, so i typed in the getvar all cmd hopeing it could help someone find a solution thanks in advance.
C:\Users\Sandwiches>fastboot devices
ZY22247TWN fastboot
C:\Users\Sandwiches>fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.281s
C:\Users\Sandwiches>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8939-80.EC
(bootloader) product: lux
(bootloader) board: lux
(bootloader) secure: yes
(bootloader) hwrev: 0x82C0
(bootloader) radio: 0x4
(bootloader) emmc: 16GB Toshiba REV=07 PRV=00 TYPE=57
(bootloader) ram: 2048MB Samsung S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8939
(bootloader) serialno: ZY22247TWN
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 54FE1D0400000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 268435456
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 358967060920707
(bootloader) meid:
(bootloader) date: 08-14-2015
(bootloader) sku: XT1562
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Feb 22 16:31:24 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/lux_reteu/lux:6.0/MPD24.6
(bootloader) ro.build.fingerprint[1]: 5-18.1/1:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.14.1.lux_reteu.re
(bootloader) ro.build.version.full[1]: teu.en.EU
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LA.BR.1.1.3_RB1.
(bootloader) ro.build.version.qcom[1]: 05.01.00.032.015
(bootloader) version-baseband: M8936_2020628.40.03.21.50R LUX_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.10.49-g6dd1a6d (hudsoncm
(bootloader) kernel.version[1]: @ilclbld73) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Thu Dec 3 16:18:03 CST 2015
(bootloader) sbl1.git: git=MBM-NG-V80.EC-0-g7abea31
(bootloader) rpm.git: git=MBM-NG-V80.EC-0-g932f716
(bootloader) tz.git: git=MBM-NG-V80.EC-0-ga1c5ae6
(bootloader) hyp.git: git=MBM-NG-V80.EC-0-ga1c5ae6
(bootloader) aboot.git: git=MBM-NG-V80.EC-0-gcfa8344
(bootloader) partition-type:modem: raw
(bootloader) partition-type:sbl1: raw
(bootloader) partition-typeDR: raw
(bootloader) partition-type:aboot: raw
(bootloader) partition-type:rpm: raw
(bootloader) partition-type:tz: raw
(bootloader) partition-type:hyp: raw
(bootloader) partition-type:utags: raw
(bootloader) partition-type:misc: raw
(bootloader) partition-typeadA: raw
(bootloader) partition-type:abootBackup: raw
(bootloader) partition-type:rpmBackup: raw
(bootloader) partition-type:tzBackup: raw
(bootloader) partition-type:hypBackup: raw
(bootloader) partition-type:utagsBackup: raw
(bootloader) partition-type:logs: raw
(bootloader) partition-type:frp: raw
(bootloader) partition-typeadB: raw
(bootloader) partition-type:modemst1: raw
(bootloader) partition-type:modemst2: raw
(bootloader) partition-type:hob: raw
(bootloader) partition-type:dhob: raw
(bootloader) partition-type:fsg: raw
(bootloader) partition-type:fsc: raw
(bootloader) partition-type:cid: raw
(bootloader) partition-type:metadata: raw
(bootloader) partition-type:logo: raw
(bootloader) partition-type:clogo: raw
(bootloader) partition-typeersist: raw
(bootloader) partition-type:kpan: raw
(bootloader) partition-type:boot: raw
(bootloader) partition-type:recovery: raw
(bootloader) partition-type:ssd: raw
(bootloader) partition-typeadC: raw
(bootloader) partition-type:sp: raw
(bootloader) partition-type:keystore: raw
(bootloader) partition-type:customize: raw
(bootloader) partition-typeem: raw
(bootloader) partition-type:carrier: ext4
(bootloader) partition-type:cache: raw
(bootloader) partition-type:system: raw
(bootloader) partition-type:userdata: raw
(bootloader) partition-size:modem: 0x00000000027e0000
(bootloader) partition-size:sbl1: 0x0000000000080000
(bootloader) partition-sizeDR: 0x0000000000020000
(bootloader) partition-size:aboot: 0x0000000000113000
(bootloader) partition-size:rpm: 0x000000000003e800
(bootloader) partition-size:tz: 0x000000000008c000
(bootloader) partition-size:hyp: 0x0000000000020000
(bootloader) partition-size:utags: 0x0000000000080000
(bootloader) partition-size:misc: 0x0000000000080000
(bootloader) partition-sizeadA: 0x000000000036f000
(bootloader) partition-size:abootBackup: 0x0000000000113000
(bootloader) partition-size:rpmBackup: 0x000000000003e800
(bootloader) partition-size:tzBackup: 0x000000000008c000
(bootloader) partition-size:hypBackup: 0x0000000000020000
(bootloader) partition-size:utagsBackup: 0x0000000000080000
(bootloader) partition-size:logs: 0x0000000000200000
(bootloader) partition-size:frp: 0x0000000000080000
(bootloader) partition-sizeadB: 0x000000000022f000
(bootloader) partition-size:modemst1: 0x0000000000180000
(bootloader) partition-size:modemst2: 0x0000000000180000
(bootloader) partition-size:hob: 0x000000000007a000
(bootloader) partition-size:dhob: 0x0000000000008000
(bootloader) partition-size:fsg: 0x0000000000180000
(bootloader) partition-size:fsc: 0x0000000000000400
(bootloader) partition-size:cid: 0x0000000000020000
(bootloader) partition-size:metadata: 0x0000000000080000
(bootloader) partition-size:logo: 0x0000000000600000
(bootloader) partition-size:clogo: 0x0000000000600000
(bootloader) partition-sizeersist: 0x0000000000800000
(bootloader) partition-size:kpan: 0x0000000000800000
(bootloader) partition-size:boot: 0x0000000002000000
(bootloader) partition-size:recovery: 0x0000000001ffc000
(bootloader) partition-size:ssd: 0x0000000000002000
(bootloader) partition-sizeadC: 0x000000000061e000
(bootloader) partition-size:sp: 0x0000000000800000
(bootloader) partition-size:keystore: 0x0000000000800000
(bootloader) partition-size:customize: 0x0000000002000000
(bootloader) partition-sizeem: 0x0000000001000000
(bootloader) partition-size:carrier: 0x0000000001000000
(bootloader) partition-size:cache: 0x0000000030000000
(bootloader) partition-size:system: 0x00000000aa000000
(bootloader) partition-size:userdata: 0x00000002c03e0000
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.452s
Make sure that OEM Unlocking is enabled in Developer Options. I had the same problem when I did mine.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Moto X Play
I used this tool "WinDroid" to unlock the bootloader. Its fully automated and very easy to use.
You can unlock your bootloader only with a few mouse clicks. Very handy tool :good:
http://forum.xda-developers.com/showthread.php?t=2499926
moto
brian10161 said:
Make sure that OEM Unlocking is enabled in Developer Options. I had the same problem when I did mine.
Sent from my Moto X Play
Click to expand...
Click to collapse
They are all enabled.
Developer Options are enabled
Usb debug enabled
oem unlocking enabled
Thats what i can't understand.
Sickaxis79 said:
I used this tool "WinDroid" to unlock the bootloader. Its fully automated and very easy to use.
You can unlock your bootloader only with a few mouse clicks. Very handy tool :good:
http://forum.xda-developers.com/showthread.php?t=2499926
Click to expand...
Click to collapse
i have tried the tool suggested gives me an error contact xda devs message.
That is very weird. Just wondering, can you try using mfasboot instead of fastboot? It's the Motorola branded version of the software. Maybe it will help?
Sent from my Moto X Play
brian10161 said:
That is very weird. Just wondering, can you try using mfasboot instead of fastboot? It's the Motorola branded version of the software. Maybe it will help?
Sent from my Moto X Play
Click to expand...
Click to collapse
Same message
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.268s
I did have it sent for repair a couple of weeks ago because i forget my gmail account details, do you think that has somethink to do with it.
I do not think it will help but maybe worth a try to just factory reset it and see if has an effect.
That might be your best net, you will be erased anyway when you unlock so nothing to lose attempting it.
Sent from my XT1563 using Tapatalk
No luck, i will try a full windows reinstall tomorrow maybe that will help if not i am stuck with a unrooted phone :crying:
I don't think reinstalling Windows will be necessary. I have a feeling something has changed as far as Moto goes. Does your phone have any subsidy on it? Was it purchased out right? Maybe a network unlock is needed? What carrier, if it applies, was it purchased through?
Sent from my Moto G 2014 using Tapatalk
brian10161 said:
I don't think reinstalling Windows will be necessary. I have a feeling something has changed as far as Moto goes. Does your phone have any subsidy on it? Was it purchased out right? Maybe a network unlock is needed? What carrier, if it applies, was it purchased through?
Sent from my Moto G 2014 using Tapatalk
Click to expand...
Click to collapse
What do you mean by subsidy?.
It was purchased on ebay a couple of days before official launch day. It was unlocked out of the box to any carrier and i haven't had a sim in it at all as i have another phone for that.
Oh okay. A subsidy, in what I'm referring to, is when a phone is purchased with a contract or a tab and has a debt owed against the phone.
Just was curious. But if the phone was purchased before launch I'm wondering if maybe it has a special board with older software in it that won't allow a bootloader unlock.
Very strange, I have never seen anything like it.
Sent from my Moto X Play
No subsidy no contacts.
I brought it off the top of my head between 3-7 days before launch day.
I won't know about old software stuff i'm a novice at the stuff its my second phone in 11 years! and both i've had in the last year so i'm new to this stuff.
brian10161 said:
Oh okay. A subsidy, in what I'm referring to, is when a phone is purchased with a contract or a tab and has a debt owed against the phone.
Just was curious. But if the phone was purchased before launch I'm wondering if maybe it has a special board with older software in it that won't allow a bootloader unlock.
Very strange, I have never seen anything like it.
Sent from my Moto X Play
Click to expand...
Click to collapse
A part from unique id strings and region code from this guys getvar all info it looks the same as mine. But i did notice his bootloader date is older (bootloader) date: 08-05-2015 vs mine (bootloader) date: 08-14-2015 if that counts at all, like i said i am new to this.
http://forum.xda-developers.com/mot...nlock-data-t3225594/post63320372#post63320372
Try this fastboot and unlock bootloader
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
if nothing works ask the service center guys to unlock it.
Have you also installed the Motorola device drivers?
drmuruga said:
Try this fastboot and unlock bootloader
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Click to expand...
Click to collapse
Thats what i am using when receiving the failed message and its been tried as admin and without still the same.
Sickaxis79 said:
Have you also installed the Motorola device drivers?
Click to expand...
Click to collapse
I have installed and reinstalled the moto device manager/drivers and the ADB Installer v1.4.3 exactly as instructed + i have used fastboot, mfastboot and tried out the windroid toolkit.
I have usb debug, oem unlocking and dev options enabled.
hello everybody said:
I have installed and reinstalled the moto device manager/drivers and the ADB Installer v1.4.3 exactly as instructed + i have used fastboot, mfastboot and tried out the windroid toolkit.
I have usb debug, oem unlocking and dev options enabled.
Click to expand...
Click to collapse
Maybe you could try using another pc from someone else and see if it works. Its a very strange situation.

I'm unable to unlock my qualified for unlocking Moto g4 plus

Hey, I am not able to unlock the bootloader of the Moto g4 plus. The cid is 0x0000. I am on stock nougat 7.0 with the April 2018 security patch. If I need to send more info, feel free to ask.
rick kode said:
Hey, I am not able to unlock the bootloader of the Moto g4 plus. The cid is 0x0000. I am on stock nougat 7.0 with the April 2018 security patch. If I need to send more info, feel free to ask.
Click to expand...
Click to collapse
Did you followed this guide https://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584 ?
strongst said:
Did you followed this guide https://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584 ?
Click to expand...
Click to collapse
Yes I have followed that guide, I have tried it multiple times
rick kode said:
Yes I have followed that guide, I have tried it multiple times
Click to expand...
Click to collapse
Where in the process is your unlocking attempt failing? Is it getting the unlock code from your device or requesting the code from Motorola?
Can we see your getvar info?
1) reboot your device to the bootloader. Connect your device to your computer via USB.
2) open an ADB terminal. In the ADB terminal, type 'fastboot getvar all' without the quotes. Press enter. You should get a list of variables about your device.
3) please post or upload the details here, you may wish to omit your IMEI.
echo92 said:
Where in the process is your unlocking attempt failing? Is it getting the unlock code from your device or requesting the code from Motorola?
Can we see your getvar info?
1) reboot your device to the bootloader. Connect your device to your computer via USB.
2) open an ADB terminal. In the ADB terminal, type 'fastboot getvar all' without the quotes. Press enter. You should get a list of variables about your device.
3) please post or upload the details here, you may wish to omit your IMEI.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.07
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: ZY2239XJQJ
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 1A8BC10000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: (i deleted this)
(bootloader) meid:
(bootloader) date: 06-13-2016
(bootloader) sku: XT1642
(bootloader) battid: SNN5966A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Mar 1 0: 9:19 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: S25.93-14-18/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.236.3.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband[0]: M8952_70030.25.03.62.02R ATHENE_EMEA_D
(bootloader) version-baseband[1]: SDS_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-ge03508d-00131-g44
(bootloader) kernel.version[1]: 2576f ([email protected]) (gcc version
(bootloader) kernel.version[2]: 4.8 (GCC) ) #1 SMP PREEMPT Wed Mar 28 06
(bootloader) kernel.version[3]: :58:16 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VB1.07-0-g57d1343
(bootloader) rpm.git: git=MBM-NG-VB1.06-0-ga970ead
(bootloader) tz.git: git=69dd24b-dirty
(bootloader) hyp.git: git=69dd24b-dirty
(bootloader) keymaster.git: git=69dd24b-dirty
(bootloader) cmnlib.git: git=69dd24b-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.07-0-gf9b89ba
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (210)
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.085s
C:\Users\RickK\Downloads\mfastboot-v2\mfastboot-v2>mfastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
OKAY [ 0.105s]
finished. total time: 0.107s
and this is the result from trying to get the code
rick kode said:
C:\Users\RickK\Downloads\mfastboot-v2\mfastboot-v2>mfastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
OKAY [ 0.105s]
finished. total time: 0.107s
and this is the result from trying to get the code
Click to expand...
Click to collapse
Hmm, thanks for that - looks like there's an issue with your device - looking at the getvar info, there's no carrier listed ((bootloader) ro.carrier: unknown ). What software channel is listed on your device under Settings>About Phone?
You may wish to submit the unlock data information and getvar info (including IMEI) to the official Motorola forums: https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/Bootloader-Unlock-Problems/td-p/3222809 Please follow the instructions on that thread, and provide all the information they request. Hopefully they can generate an unlock code for you, but please bear in mind they request at least 2 business days once the request is forwarded.
My software channel is reteu, it can Be true that I don't have a carrier, I bought this device stand alone and later put the Sim in. I will see what they can do at the official forums
rick kode said:
My software channel is reteu, it can Be true that I don't have a carrier, I bought this device stand alone and later put the Sim in. I will see what they can do at the official forums
Click to expand...
Click to collapse
In that case, that entry in the getvar info should show up as reteu, regardless of if you bought the device standalone. For example, my device was bought direct from Motorola, no phone carrier involved and it reports retgb as the carrier.
Code:
(bootloader) current-time: "Tue Jun 16 22:51:38 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: S25.93-14-18/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.236.3.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband[0]: M8952_70030.25.03.62.02R ATHENE_EMEA_D
(bootloader) version-baseband[1]: SDS_CUST
<snip>
(bootloader) frp-state: protected (77)
[B](bootloader) ro.carrier: retgb[/B]
I'd consult the Motorola forum thread on the issue, they may be able to generate a code for you or ask you to submit your device for service.
Okay, thanks for the help! I'll check the forum!

Is it really impossible to restore and rewrite an imei 0 code? No solution for xt1562

Hi,
I'm stumped
I had a fully functional Moto x phone, but unfortunately I decided to change the firmware and do a clean installation by deleting everything (I could just install twrp and do a complete wipe, but I thought about it too late) so I sent the ****ing command "fastboot erase all" thinking that it would have deleted everything except the protected partitions (like efs, persist etc ..) where there were important files ..
With the result that I lost my code imei and now there is no possibility to use the network with the sim, everything works perfectly except the mobile network!
How to solve? Is it possible that at the end of 2018 there is not yet a practical and fast solution?
I still have my code imei on the box, and if I run the command
Code:
fastboot getvar imei
is displayed correctly.
I looked around, here on the forum and it happened to many who could not easily solve the problem ..
I tried to solve it in different ways but I could not solve it
I have installed different versions of android 7.1. retasia, one or dual sim, custom rom as lineage os and aosp etc..
I also downgraded to MM 6.0 bloated rom via twrp (with fastboot there is a risk of brick) but nothing of good happened and the imei code remains 0..
I tried to install the modules xposed and rewrite the code with the app 'Device id imei changer' with no result .. the phones with soc qualcomm snapdragon unlike those mediatek are much more protected and it is difficult to succeed ..
One of the last things I'm trying is to use a program to rewrite the imei for soc snapdragon called "write dual imei" as in tihis video: https://www.youtube.com/watch?v=4P12MvP-p1o
or to use qpst with RF NV Item Manager, but I could not put the phone in diagnostic mode with these commands:
Code:
adb shell
on
setprop sys.usb.config diag, adb
I can not get the phone in diag mode with 'Qualcomm hs-usb android' and without this I can not try to rewrite the imei with the above programs ..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
how it should be:
I have seen that there are solutions like 'sigmakey' but I do not think it costs very little and I do not know if it's convenient ..
What do you advise me to do?
if I run the command
Code:
fastboot getvar all
i get this !
Code:
PS C:\Users\Gab\Desktop\Unità USB\adb-fastboot-tool-2016> fastboot devices
ZY2232F5L9 fastboot
PS C:\Users\Gab\Desktop\Unità USB\adb-fastboot-tool-2016> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8939-80.F3
(bootloader) product: lux
(bootloader) board: lux
(bootloader) secure: yes
(bootloader) hwrev: 0x82C0
(bootloader) radio: 0x4
(bootloader) emmc: 16GB Toshiba REV=07 PRV=00 TYPE=57
(bootloader) ram: 2048MB Samsung S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8939
(bootloader) serialno: ZY2232F5L9
(bootloader) cid: 0x0007
(bootloader) channelid: 0x40
(bootloader) uid: 2EAA680400000000000000000000
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 268435456
(bootloader) reason: Reboot mode set to fastboot
[COLOR="Red"](bootloader) imei: 35896706623****[/COLOR]
(bootloader) meid:
(bootloader) date: 12-17-2015
(bootloader) sku: XT1562
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Oct 22 15:43:28 UTC 2018"
(bootloader) ro.build.fingerprint[0]: motorola/lux_reteu/lux:7.1.1/NPD26
(bootloader) ro.build.fingerprint[1]: .48-24-1/1:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.26.31.1.lux_reteu.re
(bootloader) ro.build.version.full[1]: teu.en.EU
(bootloader) ro.build.version.qcom: LA.BR.1.2.9-01810-8x16.0
(bootloader) version-baseband: M8936_20250112.18.05.38y LUX_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.10.49-gd043ad1-00008-gbc
(bootloader) kernel.version[1]: f239c ([email protected]) (gcc version
(bootloader) kernel.version[2]: 4.8 (GCC) ) #1 SMP PREEMPT Mon Sep 11 02
(bootloader) kernel.version[3]: :03:43 CDT 2017
(bootloader) sbl1.git: git=MBM-NG-V80.F3-0-gd925c02
(bootloader) rpm.git: git=MBM-NG-V80.F3-0-g932f716
(bootloader) tz.git: git=MBM-NG-V80.F3-0-gcf5b5ba
(bootloader) hyp.git: git=MBM-NG-V80.F3-0-gcf5b5ba
(bootloader) aboot.git: git=MBM-NG-V80.F3-0-g8dc6510
(bootloader) partition-type:modem: raw
(bootloader) partition-type:sbl1: raw
(bootloader) partition-type:DDR: raw
(bootloader) partition-type:aboot: raw
(bootloader) partition-type:rpm: raw
(bootloader) partition-type:tz: raw
(bootloader) partition-type:hyp: raw
(bootloader) partition-type:utags: raw
(bootloader) partition-type:misc: raw
(bootloader) partition-type:padA: raw
(bootloader) partition-type:abootBackup: raw
(bootloader) partition-type:rpmBackup: raw
(bootloader) partition-type:tzBackup: raw
(bootloader) partition-type:hypBackup: raw
(bootloader) partition-type:utagsBackup: raw
(bootloader) partition-type:logs: raw
(bootloader) partition-type:frp: raw
(bootloader) partition-type:padB: raw
(bootloader) partition-type:modemst1: raw
(bootloader) partition-type:modemst2: raw
(bootloader) partition-type:hob: raw
(bootloader) partition-type:dhob: raw
(bootloader) partition-type:fsg: raw
(bootloader) partition-type:fsc: raw
(bootloader) partition-type:cid: raw
(bootloader) partition-type:metadata: raw
(bootloader) partition-type:logo: raw
(bootloader) partition-type:clogo: raw
(bootloader) partition-type:persist: raw
(bootloader) partition-type:kpan: raw
(bootloader) partition-type:boot: raw
(bootloader) partition-type:recovery: raw
(bootloader) partition-type:ssd: raw
(bootloader) partition-type:padC: raw
(bootloader) partition-type:sp: raw
(bootloader) partition-type:keystore: raw
(bootloader) partition-type:customize: raw
(bootloader) partition-type:oem: raw
(bootloader) partition-type:carrier: ext4
(bootloader) partition-type:cache: raw
(bootloader) partition-type:system: raw
(bootloader) partition-type:userdata: raw
(bootloader) partition-size:modem: 0x00000000027e0000
(bootloader) partition-size:sbl1: 0x0000000000080000
(bootloader) partition-size:DDR: 0x0000000000020000
(bootloader) partition-size:aboot: 0x0000000000113000
(bootloader) partition-size:rpm: 0x000000000003e800
(bootloader) partition-size:tz: 0x000000000008c000
(bootloader) partition-size:hyp: 0x0000000000020000
(bootloader) partition-size:utags: 0x0000000000080000
(bootloader) partition-size:misc: 0x0000000000080000
(bootloader) partition-size:padA: 0x000000000036f000
(bootloader) partition-size:abootBackup: 0x0000000000113000
(bootloader) partition-size:rpmBackup: 0x000000000003e800
(bootloader) partition-size:tzBackup: 0x000000000008c000
(bootloader) partition-size:hypBackup: 0x0000000000020000
(bootloader) partition-size:utagsBackup: 0x0000000000080000
(bootloader) partition-size:logs: 0x0000000000200000
(bootloader) partition-size:frp: 0x0000000000080000
(bootloader) partition-size:padB: 0x000000000022f000
(bootloader) partition-size:modemst1: 0x0000000000180000
(bootloader) partition-size:modemst2: 0x0000000000180000
(bootloader) partition-size:hob: 0x000000000007a000
(bootloader) partition-size:dhob: 0x0000000000008000
(bootloader) partition-size:fsg: 0x0000000000180000
(bootloader) partition-size:fsc: 0x0000000000000400
(bootloader) partition-size:cid: 0x0000000000020000
(bootloader) partition-size:metadata: 0x0000000000080000
(bootloader) partition-size:logo: 0x0000000000600000
(bootloader) partition-size:clogo: 0x0000000000600000
(bootloader) partition-size:persist: 0x0000000000800000
(bootloader) partition-size:kpan: 0x0000000000800000
(bootloader) partition-size:boot: 0x0000000002000000
(bootloader) partition-size:recovery: 0x0000000001ffc000
(bootloader) partition-size:ssd: 0x0000000000002000
(bootloader) partition-size:padC: 0x000000000061e000
(bootloader) partition-size:sp: 0x0000000000800000
(bootloader) partition-size:keystore: 0x0000000000800000
(bootloader) partition-size:customize: 0x0000000002000000
(bootloader) partition-size:oem: 0x0000000001000000
(bootloader) partition-size:carrier: 0x0000000001000000
(bootloader) partition-size:cache: 0x0000000030000000
(bootloader) partition-size:system: 0x00000000aa000000
(bootloader) partition-size:userdata: 0x00000002c03e0000
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.366s
PS C:\Users\Gab\Desktop\Unità USB\adb-fastboot-tool-2016
Any help ???

unable to unlock bootloader

Dear Members,
I request you to please help me unlocking the bootloader of my phone.
When checked for eligiblity, the website shows that my device is not eligible for unlocking the bootloader,
below is the unlock data string and the getvar all details. My device runs on oreo 8.1.
Please help me.
3A45110517225963#
5A593232333853435754004D6F746F2047200000#
400346C746060C4A50361A1621BB90BCF1437429#
BDC19700000000000000000000000000
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.09
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8952
(bootloader) serialno: ZY2238SCWT
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: BDC1970000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 354115071229536
(bootloader) meid:
(bootloader) date: 05-05-2016
(bootloader) sku: XT1643
(bootloader) battid: SNN5966A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Feb 22 19:16: 7 UTC 2021"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:8.1.0/O
(bootloader) ro.build.fingerprint[1]: PJ28.111-22/532da:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) ro.build.version.full[0]: Blur_Version.28.11.26.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.7-04410-8976.0
(bootloader) version-baseband[0]: M8952_70030.25.03.77R ATHENE_INDIA_DSD
(bootloader) version-baseband[1]: S_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-g4bcbf43 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld68) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Tue Jan 29 12:12:11 CST 2019
(bootloader) sbl1.git: git=MBM-NG-VB1.09-0-g6e71967
(bootloader) rpm.git: git=MBM-NG-VB1.06-0-ga970ead
(bootloader) tz.git: git=9af563b-dirty
(bootloader) hyp.git: git=9af563b-dirty
(bootloader) keymaster.git: git=9af563b-dirty
(bootloader) cmnlib.git: git=9af563b-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.09-0-g9a76df4
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retin
remove spaces in your string code, so that it is a single line.
try this again:
3A45110517225963#5A593232333853435754004D6F746F2047200000#400346C746060C4A50361A1621BB90BCF1437429#BDC19700000000000000000000000000
zitronenmelissa said:
remove spaces in your string code, so that it is a single line.
try this again:
3A45110517225963#5A593232333853435754004D6F746F2047200000#400346C746060C4A50361A1621BB90BCF1437429#BDC19700000000000000000000000000
Click to expand...
Click to collapse
That was indeed a great help. I am running out of words to thank you. It worked!!!! Now i am gonna enjoy custom roms............

Categories

Resources