Related
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
I feel like if we put together a thread, we can share our progress and knowledge on unlocking the Fire HD bootloader which will allow us to root and install custom roms. I want to just put out into the open that I am a noob to Android so I may not make sense sometimes.
I am going to post all the information about the bootloader in this thread, so that people who do not have an HD device can still debug and poke around a little. It is going to start off small, but if people are willing to contribute their knowledge we will add it to the thread!
$ fastboot getvar all
Code:
(bootloader) unlock_status: false
(bootloader) unlock_version: 1
(bootloader) unlock_code: 0x4ad481f13eb0c4d7
(bootloader) prod: 1
(bootloader) serialno: G090G80953540BQG
(bootloader) partition-offset:userdata: 5ec80000
(bootloader) partition-size:userdata: 173f7be00
(bootloader) partition-type:userdata: unknown
(bootloader) partition-offset:cache: 4f280000
(bootloader) partition-size:cache: fa00000
(bootloader) partition-type:cache: unknown
(bootloader) partition-offset:system: 4280000
(bootloader) partition-size:system: 4b000000
(bootloader) partition-type:system: unknown
(bootloader) partition-offset:persisbackup: 3280000
(bootloader) partition-size:persisbackup: 1000000
(bootloader) partition-type:persisbackup: unknown
(bootloader) partition-offset:MISC: 3200000
(bootloader) partition-size:MISC: 80000
(bootloader) partition-type:MISC: unknown
(bootloader) partition-offset:DKB: 3100000
(bootloader) partition-size:DKB: 100000
(bootloader) partition-type:DKB: unknown
(bootloader) partition-offset:KB: 3000000
(bootloader) partition-size:KB: 100000
(bootloader) partition-type:KB: unknown
(bootloader) partition-offset:recovery: 2800000
(bootloader) partition-size:recovery: 800000
(bootloader) partition-type:recovery: unknown
(bootloader) partition-offset:boot: 2000000
(bootloader) partition-size:boot: 800000
(bootloader) partition-type:boot: unknown
(bootloader) partition-offset:UBOOT: 1f00000
(bootloader) partition-size:UBOOT: 100000
(bootloader) partition-type:UBOOT: unknown
(bootloader) partition-offset:TEE2: 1a00000
(bootloader) partition-size:TEE2: 500000
(bootloader) partition-type:TEE2: unknown
(bootloader) partition-offset:TEE1: 1500000
(bootloader) partition-size:TEE1: 500000
(bootloader) partition-type:TEE1: unknown
(bootloader) partition-offset:PMT: 1100000
(bootloader) partition-size:PMT: 400000
(bootloader) partition-type:PMT: unknown
(bootloader) partition-offset:PRO_INFO: 1008000
(bootloader) partition-size:PRO_INFO: 20000
(bootloader) partition-type:PRO_INFO: unknown
(bootloader) max-download-size: 52429824
(bootloader) kernel: lk
(bootloader) product: THEBES
(bootloader) version: 0.5
(bootloader) unlocked: not unlocked
(bootloader) production: Unknown
all: Done!!
finished. total time: 0.022s
nyln said:
I feel like if we put together a thread, we can share our progress and knowledge on unlocking the Fire HD bootloader which will allow us to root and install custom roms. I want to just put out into the open that I am a noob to Android so I may not make sense sometimes.
I am going to post all the information about the bootloader in this thread, so that people who do not have an HD device can still debug and poke around a little. It is going to start off small, but if people are willing to contribute their knowledge we will add it to the thread!
$ fastboot getvar all
Code:
(bootloader) unlock_status: false
(bootloader) unlock_version: 1
(bootloader) unlock_code: 0x4ad481f13eb0c4d7
(bootloader) prod: 1
(bootloader) serialno: G090G80953540BQG
(bootloader) partition-offset:userdata: 5ec80000
(bootloader) partition-size:userdata: 173f7be00
(bootloader) partition-type:userdata: unknown
(bootloader) partition-offset:cache: 4f280000
(bootloader) partition-size:cache: fa00000
(bootloader) partition-type:cache: unknown
(bootloader) partition-offset:system: 4280000
(bootloader) partition-size:system: 4b000000
(bootloader) partition-type:system: unknown
(bootloader) partition-offset:persisbackup: 3280000
(bootloader) partition-size:persisbackup: 1000000
(bootloader) partition-type:persisbackup: unknown
(bootloader) partition-offset:MISC: 3200000
(bootloader) partition-size:MISC: 80000
(bootloader) partition-type:MISC: unknown
(bootloader) partition-offset:DKB: 3100000
(bootloader) partition-size:DKB: 100000
(bootloader) partition-type:DKB: unknown
(bootloader) partition-offset:KB: 3000000
(bootloader) partition-size:KB: 100000
(bootloader) partition-type:KB: unknown
(bootloader) partition-offset:recovery: 2800000
(bootloader) partition-size:recovery: 800000
(bootloader) partition-type:recovery: unknown
(bootloader) partition-offset:boot: 2000000
(bootloader) partition-size:boot: 800000
(bootloader) partition-type:boot: unknown
(bootloader) partition-offset:UBOOT: 1f00000
(bootloader) partition-size:UBOOT: 100000
(bootloader) partition-type:UBOOT: unknown
(bootloader) partition-offset:TEE2: 1a00000
(bootloader) partition-size:TEE2: 500000
(bootloader) partition-type:TEE2: unknown
(bootloader) partition-offset:TEE1: 1500000
(bootloader) partition-size:TEE1: 500000
(bootloader) partition-type:TEE1: unknown
(bootloader) partition-offset:PMT: 1100000
(bootloader) partition-size:PMT: 400000
(bootloader) partition-type:PMT: unknown
(bootloader) partition-offset:PRO_INFO: 1008000
(bootloader) partition-size:PRO_INFO: 20000
(bootloader) partition-type:PRO_INFO: unknown
(bootloader) max-download-size: 52429824
(bootloader) kernel: lk
(bootloader) product: THEBES
(bootloader) version: 0.5
(bootloader) unlocked: not unlocked
(bootloader) production: Unknown
all: Done!!
finished. total time: 0.022s
Click to expand...
Click to collapse
i wish i had a second one lying around so that i could help out on these initial stages. as it stands, we need a better bootloader. as we get closer to the goal, i'll feel more comfortable using my mom's HD 10.
Having toyed around with fastboot, it seems to me that the blank fastboot screen is less of an issue and more of an added security measure. I think the focus should be on the current capabilities of the bootloader via fastboot, but I'm usually just a novice, instead of focusing on that it's a blank screen. Such as, if you run 2015 7" root scripts on the HD 8/10 it refuses with errors, not lack of device communication. I'd dive in deeper but this is a Christmas gift that I'm using daily around the living room.
I know I'm somewhat stating the obvious but I've read a lot of misleading post regarding a "proper fastboot". I'm thinking this is just an evolved bootloader instead.
madsc13n41s4 said:
Having toyed around with fastboot, it seems to me that the blank fastboot screen is less of an issue and more of an added security measure. I think the focus should be on the current capabilities of the bootloader via fastboot, but I'm usually just a novice, instead of focusing on that it's a blank screen. Such as, if you run 2015 7" root scripts on the HD 8/10 it refuses with errors, not lack of device communication. I'd dive in deeper but this is a Christmas gift that I'm using daily around the living room.
I know I'm somewhat stating the obvious but I've read a lot of misleading post regarding a "proper fastboot". I'm thinking this is just an evolved bootloader instead.
Click to expand...
Click to collapse
I would be happy to setup my device remotely if anyone wants to tinker with the fastboot console.
Is anyone interested in giving me commands to run on my device?
I would start by taking a look at the rootjunkie 5th gen supertool for the 2015 7". Its probably the closest compatible effort, fastboot commands are in the .bat files. You look like you know a thing or two about scripts.
madsc13n41s4 said:
I would start by taking a look at the rootjunkie 5th gen supertool for the 2015 7". Its probably the closest compatible effort, fastboot commands are in the .bat files. You look like you know a thing or two about scripts.
Click to expand...
Click to collapse
I have already tried this, there is a different fastboot screen, and the bootloader unlock command does not function on HD models.
Send me commands to try if you want me too.
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!
Hi Guys,
I´m stuck with a tricky problem, may someone can help/has an idea how to fix that.
My Moto X4 has no unlock data, I was also in contact with the lenovo support.
The reply of the lenovo support was:
"Sorry for the late reply. The team I endorsed this with told me that the phone cannot be unlocked. We don't know the reason for sure, but it's possible that unlock data block has gone missing, is corrupt, or has not been programmed into the device."
last option(may)
"You can try checking in the service center and reflash the phone, but I can't guarantee anything. Thanks."
Phone data:
fastboot oem get_unlock_data
(bootloader) Failed to get unlock data.
OKAY [ 0.007s]
Finished. Total time: 0.007s
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-8510c11-190829
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: EMEA
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DD68MB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 3GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: (removed by me)
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 0E0D69C6
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: (removed by me)
(bootloader) meid:
(bootloader) date: 09-25-2017
(bootloader) sku: XT1900-7
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4140
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPWS29.69
(bootloader) ro.build.fingerprint[1]: -37-5/63ca8:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.381.29.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: M660_7045.36.01.100R PAYTON_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g3ff98f3 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Thu Aug 29 11:07:24 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-8510c11-190829
(bootloader) git:xbl: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) gitmic: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190829
(bootloader) git:tz: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:hyp: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:devcfg: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:keymaster: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) gitrov: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:storsec: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
Finished. Total time: 0.040s
So I tried first the recovery with the lenovo software (rescue_and_smart_assistant_v5.6.0.15),
fixed nothing.
So google gave me no hint how to "crack" the bootloader... does someone know how I could unlock the bootloader anyway,
I don´t care if i may break the phone, if it´s stuck in Android 9 it´s useless. I already upgraded to Moto Edge (G100).
Just want to use it as fallback phone.
Bests Marc
spacewan said:
Hi Guys,
I´m stuck with a tricky problem, may someone can help/has an idea how to fix that.
My Moto X4 has no unlock data, I was also in contact with the lenovo support.
The reply of the lenovo support was:
"Sorry for the late reply. The team I endorsed this with told me that the phone cannot be unlocked. We don't know the reason for sure, but it's possible that unlock data block has gone missing, is corrupt, or has not been programmed into the device."
last option(may)
"You can try checking in the service center and reflash the phone, but I can't guarantee anything. Thanks."
Phone data:
fastboot oem get_unlock_data
(bootloader) Failed to get unlock data.
OKAY [ 0.007s]
Finished. Total time: 0.007s
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-8510c11-190829
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: EMEA
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DD68MB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 3GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: (removed by me)
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 0E0D69C6
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: (removed by me)
(bootloader) meid:
(bootloader) date: 09-25-2017
(bootloader) sku: XT1900-7
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4140
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPWS29.69
(bootloader) ro.build.fingerprint[1]: -37-5/63ca8:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.381.29.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: M660_7045.36.01.100R PAYTON_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g3ff98f3 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Thu Aug 29 11:07:24 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-8510c11-190829
(bootloader) git:xbl: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) gitmic: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190829
(bootloader) git:tz: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:hyp: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:devcfg: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:keymaster: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) gitrov: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:storsec: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
Finished. Total time: 0.040s
So I tried first the recovery with the lenovo software (rescue_and_smart_assistant_v5.6.0.15),
fixed nothing.
So google gave me no hint how to "crack" the bootloader... does someone know how I could unlock the bootloader anyway,
I don´t care if i may break the phone, if it´s stuck in Android 9 it´s useless. I already upgraded to Moto Edge (G100).
Just want to use it as fallback phone.
Bests Marc
Click to expand...
Click to collapse
You have an X4 so next time you should post in the X4 forum
https://forum.xda-developers.com/c/moto-x4.6912/
Well, looking at the getvar all it's not good.
XT1900-7 could be DTPL(TMO), Playpl, or RetEU
Cid 0x0000 cannot be unlocked
Code:
(bootloader) cid: 0x0000
You might be able to flash the stock firmware.
Looks like it's on the latest version
PPWS29.69-37-5
If you know which Carrier/software channel it was on download the firmware from
https://mirrors.lolinet.com/firmware/moto/payton/official/
If you have an old Windows 7 or XP machine use RSD Lite, that is your best option, it doesn't work on Windows 9/10.
If that's not an option use fastboot.exe or mfastboot
and flash this from Firmware
Code:
fastboot flash partition gpt.bin
If it's the firmware and it flashes successfully, Getvar all should have more info
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
sd_shadow said:
You have an X4 so next time you should post in the X4 forum
https://forum.xda-developers.com/c/moto-x4.6912/
Click to expand...
Click to collapse
I´m sorry, haven´ t seen it... @Admin... could you may move it?
sd_shadow said:
Well, looking at the getvar all it's not good.
XT1900-7 could be DTPL(TMO), Playpl, or RetEU
Click to expand...
Click to collapse
I´m almost sure that it´s the RetEU one
sd_shadow said:
Cid 0x0000 cannot be unlocked
Code:
(bootloader) cid: 0x0000
You might be able to flash the stock firmware.
Looks like it's on the latest version
PPWS29.69-37-5
If you know which Carrier/software channel it was on download the firmware from
https://mirrors.lolinet.com/firmware/moto/payton/official/
Click to expand...
Click to collapse
Thanks for this link I´ll gonna check. I´m using Vodafone, but the Phone is not branded.
sd_shadow said:
If you have an old Windows 7 or XP machine use RSD Lite, that is your best option, it doesn't work on Windows 9/10.
Click to expand...
Click to collapse
No I only have Win 10, but only for "emergency", I´m using generally a linux desktop,
so I gonna try it with fastboot of the adb-tools
sd_shadow said:
If that's not an option use fastboot.exe or mfastboot
and flash this from Firmware
Code:
fastboot flash partition gpt.bin
If it's the firmware and it flashes successfully, Getvar all should have more info
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Click to expand...
Click to collapse
I´ll try that during the next days, let´s see what happens, thanks so far.
Bests Marc
HI Shadow,
made it (used XT1900-7_PAYTON_RETEU_DS_9.0_PPWS29.69-37-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC)
, this was the output:
[email protected]:/home/moto-x4# fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
Sending 'partition' (37 KB)...
OKAY [ 0.001s]
Writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.112s]
Finished. Total time: 0.114s
[email protected]:/home/moto-x4# fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-8510c11-190829
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: EMEA
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DD68MB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 3GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: (removed by me)
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 0E0D69C6
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: (removed by me)
(bootloader) meid:
(bootloader) date: 09-25-2017
(bootloader) sku: XT1900-7
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4264
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPWS29.69
(bootloader) ro.build.fingerprint[1]: -37-5/63ca8:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.381.29.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: M660_7045.36.01.100R PAYTON_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g3ff98f3 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Thu Aug 29 11:07:24 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-8510c11-190829
(bootloader) git:xbl: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) gitmic: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190829
(bootloader) git:tz: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:hyp: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:devcfg: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:keymaster: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) gitrov: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:storsec: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.048s
I see as quick view that the slot switched from b to a, may have have to specify the slot during the falsh as well?
Bests Marc
I was impatient, so I flashed everything, now the phone is (as may expected) stuck in a bootloop.
output is:
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-8510c11-190829
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: EMEA
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DD68MB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 3GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: (removed by me)
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 0E0D69C6
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: (removed by me)
(bootloader) meid:
(bootloader) date: 09-25-2017
(bootloader) sku: XT1900-7
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4246
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPWS29.69
(bootloader) ro.build.fingerprint[1]: -37-5/63ca8:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.381.29.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: M660_7045.36.01.100R PAYTON_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g3ff98f3 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Thu Aug 29 11:07:24 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-8510c11-190829
(bootloader) git:xbl: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) gitmic: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190829
(bootloader) git:tz: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:hyp: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:devcfg: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:keymaster: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) gitrov: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:storsec: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.041s
I´m wondering why fastboot set_active a/b is not working, get the message FAILED (remote failure).
Bests Marc
Ok, got it running again with recovering about the original LMSA Software.
Now it says:
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-8510c11-190829
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: EMEA
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DD68MB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 3GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: (removed by me)
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 0E0D69C6
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: (removed by me)
(bootloader) meid:
(bootloader) date: 09-25-2017
(bootloader) sku: XT1900-7
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4275
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPWS29.69
(bootloader) ro.build.fingerprint[1]: -37-5/63ca8:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.381.29.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: M660_7045.36.01.100R PAYTON_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g3ff98f3 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Thu Aug 29 11:07:24 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-8510c11-190829
(bootloader) git:xbl: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) gitmic: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190829
(bootloader) git:tz: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:hyp: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:devcfg: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:keymaster: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) gitrov: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:storsec: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: unknown
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.048s
Again from the beginning...how to kill/crack this damn locked bootloader without oem_unlock_data...
I want to get a custom rom on it.
Bests Marc
I have system bin files,but It can't go in recovery mode,so I don't know how to flash the bin file.
fastboot getvar all
(bootloader) serialno: G090G8*
(bootloader) partition-offset:userdata: eaa80000
(bootloader) partition-size:userdata: e7dfbe00
(bootloader) partition-type:userdata: unknown
(bootloader) partition-offset:MDUMP: a6a80000
(bootloader) partition-size:MDUMP: 44000000
(bootloader) partition-type:MDUMP: unknown
(bootloader) partition-offset:dfs: 86a80000
(bootloader) partition-size:dfs: 20000000
(bootloader) partition-type:dfs: unknown
(bootloader) partition-offset:dkernel: 86280000
(bootloader) partition-size:dkernel: 800000
(bootloader) partition-type:dkernel: unknown
(bootloader) partition-offset:cache: 4f280000
(bootloader) partition-size:cache: 37000000
(bootloader) partition-type:cache: unknown
(bootloader) partition-offset:system: 4280000
(bootloader) partition-size:system: 4b000000
(bootloader) partition-type:system: unknown
(bootloader) partition-offsetersisbackup: 3280000
(bootloader) partition-sizeersisbackup: 1000000
(bootloader) partition-typeersisbackup: unknown
(bootloader) partition-offset:MISC: 3200000
(bootloader) partition-size:MISC: 80000
(bootloader) partition-type:MISC: unknown
(bootloader) partition-offsetKB: 3100000
(bootloader) partition-sizeKB: 100000
(bootloader) partition-typeKB: unknown
(bootloader) partition-offset:KB: 3000000
(bootloader) partition-size:KB: 100000
(bootloader) partition-type:KB: unknown
(bootloader) partition-offset:recovery: 2800000
(bootloader) partition-size:recovery: 800000
(bootloader) partition-type:recovery: unknown
(bootloader) partition-offset:boot: 2000000
(bootloader) partition-size:boot: 800000
(bootloader) partition-type:boot: unknown
(bootloader) partition-offset:UBOOT: 1f00000
(bootloader) partition-size:UBOOT: 100000
(bootloader) partition-type:UBOOT: unknown
(bootloader) partition-offset:TEE2: 1a00000
(bootloader) partition-size:TEE2: 500000
(bootloader) partition-type:TEE2: unknown
(bootloader) partition-offset:TEE1: 1500000
(bootloader) partition-size:TEE1: 500000
(bootloader) partition-type:TEE1: unknown
(bootloader) partition-offsetMT: 1100000
(bootloader) partition-sizeMT: 400000
(bootloader) partition-typeMT: unknown
(bootloader) partition-offsetRO_INFO: 1008000
(bootloader) partition-sizeRO_INFO: 20000
(bootloader) partition-typeRO_INFO: unknown
(bootloader) max-download-size: 52429824
(bootloader) kernel: lk
(bootloader) product: THEBES
(bootloader) version: 0.5
(bootloader) production: Unknown
andrew99168 said:
I have system bin files,but It can't go in recovery mode,so I don't know how to flash the bin file.
fastboot getvar all
(bootloader) serialno: G090G8*
(bootloader) partition-offset:userdata: eaa80000
(bootloader) partition-size:userdata: e7dfbe00
(bootloader) partition-type:userdata: unknown
(bootloader) partition-offset:MDUMP: a6a80000
(bootloader) partition-size:MDUMP: 44000000
(bootloader) partition-type:MDUMP: unknown
(bootloader) partition-offset:dfs: 86a80000
(bootloader) partition-size:dfs: 20000000
(bootloader) partition-type:dfs: unknown
(bootloader) partition-offset:dkernel: 86280000
(bootloader) partition-size:dkernel: 800000
(bootloader) partition-type:dkernel: unknown
(bootloader) partition-offset:cache: 4f280000
(bootloader) partition-size:cache: 37000000
(bootloader) partition-type:cache: unknown
(bootloader) partition-offset:system: 4280000
(bootloader) partition-size:system: 4b000000
(bootloader) partition-type:system: unknown
(bootloader) partition-offsetersisbackup: 3280000
(bootloader) partition-sizeersisbackup: 1000000
(bootloader) partition-typeersisbackup: unknown
(bootloader) partition-offset:MISC: 3200000
(bootloader) partition-size:MISC: 80000
(bootloader) partition-type:MISC: unknown
(bootloader) partition-offsetKB: 3100000
(bootloader) partition-sizeKB: 100000
(bootloader) partition-typeKB: unknown
(bootloader) partition-offset:KB: 3000000
(bootloader) partition-size:KB: 100000
(bootloader) partition-type:KB: unknown
(bootloader) partition-offset:recovery: 2800000
(bootloader) partition-size:recovery: 800000
(bootloader) partition-type:recovery: unknown
(bootloader) partition-offset:boot: 2000000
(bootloader) partition-size:boot: 800000
(bootloader) partition-type:boot: unknown
(bootloader) partition-offset:UBOOT: 1f00000
(bootloader) partition-size:UBOOT: 100000
(bootloader) partition-type:UBOOT: unknown
(bootloader) partition-offset:TEE2: 1a00000
(bootloader) partition-size:TEE2: 500000
(bootloader) partition-type:TEE2: unknown
(bootloader) partition-offset:TEE1: 1500000
(bootloader) partition-size:TEE1: 500000
(bootloader) partition-type:TEE1: unknown
(bootloader) partition-offsetMT: 1100000
(bootloader) partition-sizeMT: 400000
(bootloader) partition-typeMT: unknown
(bootloader) partition-offsetRO_INFO: 1008000
(bootloader) partition-sizeRO_INFO: 20000
(bootloader) partition-typeRO_INFO: unknown
(bootloader) max-download-size: 52429824
(bootloader) kernel: lk
(bootloader) product: THEBES
(bootloader) version: 0.5
(bootloader) production: Unknown
Click to expand...
Click to collapse
By the way, The Comand that "ADB Devices" is empty, just use fastboot command. it can go in fastboot mode by touch the power button and vol+ button. it normally stop in normal boot mode by power on.
You don't. You can't flash stuff thru fastboot.
Rortiz2 said:
You don't. You can't flash stuff thru fastboot.
Click to expand...
Click to collapse
so, what can I do?
andrew99168 said:
so, what can I do?
Click to expand...
Click to collapse
Trash the device.