LeEco le pro 3 elite x722 (bootloader) Device critical unlocked: false - LeEco Le Pro3 Questions & Answers

After unlocking bootloader using twrp and flashing rom my phone is not turning on. I see just a Leeco logo or I can go to fastboot with adb. When I enter "fastboot oem device-info", I get:
(bootloader) Device product name: [le_zl0_whole_netcom]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
(bootloader) is_allow_unlock: 0
I got a hard brick? How to solve it?

It seems that you flashed the wrong firmware
You will need to unbrick the phone using the X722 Qfil

Related

OPT Fastboot OEM Device-Info

Hi guys,
I need you help : ) My OPT has a flickering display an I'd like to send it in. Therefore, I'd like to restore the factory default settings. Unfourtunatly, I don't know the default OEM Device-Infos. And how to change them.
I have just installed Oxygen OS 2.2.0: OnePlus2Oxygen_14_OTA_011_all_1512111634.zip from http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
And these are my Fastboot Device Infos:
C:\adb>fastboot oem device-info
(bootloader) Device tamper: true
(bootloader) Device unlocked: true
(bootloader) Device is_verified: false
(bootloader) Charger scree enable: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.073s]
Finished. Total time: 0.077s
Do you guys know, if I can hand my phone in with an unlocked bootloader or do I need to change these parameters? I would be very pleased for any advise. Thank you : )
frammies said:
Hi guys,
I need you help : ) My OPT has a flickering display an I'd like to send it in. Therefore, I'd like to restore the factory default settings. Unfourtunatly, I don't know the default OEM Device-Infos. And how to change them.
I have just installed Oxygen OS 2.2.0: OnePlus2Oxygen_14_OTA_011_all_1512111634.zip from http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
And these are my Fastboot Device Infos:
C:\adb>fastboot oem device-info
(bootloader) Device tamper: true
(bootloader) Device unlocked: true
(bootloader) Device is_verified: false
(bootloader) Charger scree enable: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.073s]
Finished. Total time: 0.077s
Do you guys know, if I can hand my phone in with an unlocked bootloader or do I need to change these parameters? I would be very pleased for any advise. Thank you : )
Click to expand...
Click to collapse
It's fine as it is - read this

Bootloader Mode - Connect USB Data Cable

I have my 6P connected via USB to my PC. I see the device in Device Manager as Android Bootloader Interface. I on the 6P, in bootloader mode, listed at the bottom is "Connect USB Data Cable". I know the USB cable works as I was able to boot into Android and see it as a drive on my PC.
Other items listed:
Product/Variant: ANGLER-VN2
Device is locked
Qfuse Status: ENABLED
Download Mode: Disabled
Should still be working. Try running fastboot getvar all, or just fastboot devices, on it and see if it works. I know mine always shows the "Connect USB Data Cable" text regardless.
eragon5779 said:
Should still be working. Try running fastboot getvar all, or just fastboot devices, on it and see if it works. I know mine always shows the "Connect USB Data Cable" text regardless.
Click to expand...
Click to collapse
fastboot devices:
84B5T15A29016374 fastboot
C:\WINDOWS\system32>fastboot getvar all
(bootloader) version:0.01
(bootloader) unlocked:no
(bootloader) hardware-revision:ANGLER-VN2
(bootloader) version-baseband:angler-03.84
(bootloader) version-bootloader:angler-03.75
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1d800000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x6400000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x66257ee00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc0000000
(bootloader) serialno:84B5T15A29016374
(bootloader) kernel:lk
(bootloader) product:angler
all:
finished. total time: 0.190s
I was able to unlock it this try.
C:\WINDOWS\system32>fastboot flashing unlock
...
(bootloader) Please select 'YES' on screen if you want to continue...
(bootloader) Unlocking bootloader...
(bootloader) Unlocked!
OKAY [ 11.930s]
finished. total time: 11.930s
C:\WINDOWS\system32>

Stuck with Fastboot, DFU and locked bootloader

Hello, I am totally lost... I've been trying to solve this problem but no luck... I relocked my bootloader. Since that day, I can only access : fastboot.
It seems I can flash recovery with fastboot, but the phone never boots into recovery (stuck on ZTE logo B2017G ).
I've tried to put my device in EDL mode with DeepFlash cable but without success.
###########
fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.017s
##############
any one can help me plz.
anyone can help
t.zennad said:
anyone can help
Click to expand...
Click to collapse
I'm also in the same condition...
fastboot not accessible...
Help!!!
Axon 7 mini 7.1.1 build B2017gV1.2.0B14
Still waiting too.
Get a stock recovery (not TWRP), flash it with fasboot flash recovery recovery.img
I think tdm has a thread with all stock images, flash the one for your country
https://forum.xda-developers.com/axon-7-mini/development/firmware-stock-firmware-t3696538
If this doesn't work, maybe the verity check fails, making the device unable to boot, then go ahead and flash system and boot via fastboot.
fastboot flash system system.img
fastboot flash boot boot.img
Good luck
just a hailmairy here but...
"(bootloader) Charger screen enabled: 'false'"
in Advanced Settings ->Developer Options->Stay Awake (while charging) [ ]
should possible be switched on as it does mentions that charging screen set to off?
Probably would only sort one item though but you never know and if it does your one more step forward.
sonnettie
HEEEEELP! From Liquid tried to flash Lineage16.....flashed bootloader...I'm stuck on fastboot. The down volume key is broken. Only up volume works but not in fastboot. Tried to adb/flash a sock recovery....only can reboot in fastboot dialogue. Any solution? Thank you.
Hello
any one can help please, i am still in same problem
fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3447000
(bootloader) variant:TULIP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x12c00000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5ebb79e00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x100000000
(bootloader) serialno:bc13c89a
(bootloader) kernel:lk
(bootloader) product:TULIP
all:
finished. total time: 0.022s
------
fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.007s
-------
I relocked my bootloader. Since that day, I can only access : fastboot.
It seems I can flash recovery with fastboot, but the phone never boots into recovery (loop on ZTE logo B2017G ).
I've tried to put my device in EDL mode with DeepFlash cable but without success.
Thanks
I tried to unlock my b2017g with fastboot commands but not luck, i tried use Hydra too... i hope will find a solution soon :/
Hi Everybody, I think I have a similar issue. After many years with regular stock system I decided to change to a custom ROM, hoping I can use my phone with my native language, which was not in the stock rom.
But now I stucked in the fastboot, and I can not get out of it. I can access my phone via fastboot, I have already flashed the TWRP, but the phone can not boot into the recovery and the system. How can I fix this? Please help me, I like this phone, I would like to get it back to life.
I bricked my Axon mini n2015 by flashing No verity boot.img and a custom recovery. Now phone is stuck in fastboot mode. Help guys, what do i do?
Looks like no solution

[HELP] Unlocking the booloader of Amazon Echo Show 2nd Gen

Hello,
I want to know if someone can help me unlocking the bootloader of this device for installing custom rom/apps
It has an Intel Cherry Trail Processor
I can boot to fastboot using the Vol- and Power together and tried the following commands
fastboot oem unlock - returns OKAY but doesn't unlock the bootloader
Code:
fastboot oem lock
- returns that the device is already in the required state
Code:
fastboot flash twrp.img
- returns that it cannot be possible since the device is locked
Code:
fastboot boot twrp.img
- goes to the amazon logo and then right to fastboot again
Code:
fastboot getvar all
(bootloader) serialno: ------------------------ [hidden for purposes]
(bootloader) board: Intel Corp. Cherry Trail CR 0
(bootloader) device-state: locked
(bootloader) boot-state: GREEN
(bootloader) firmware: Intel Corporation CH2T.BSHP.X64.0005.R09.18091217
(bootloader) product-name: CHERRYVIEW D1 PLATFORM
(bootloader) secureboot: yes
(bootloader) off-mode-charge: 1
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) partition-type:vendor: ext4
(bootloader) partition-size:vendor: 0x0000000016C00000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x00000000FA800000
(bootloader) partition-type:data: ext4
(bootloader) partition-size:data: 0x00000000FA800000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x000000008CC00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x0000000020000000
(bootloader) partition-type:factory: none
(bootloader) partition-size:factory: 0x0000000002000000
(bootloader) partition-type:recovery: none
(bootloader) partition-size:recovery: 0x0000000002000000
(bootloader) partition-type:boot: none
(bootloader) partition-size:boot: 0x0000000002000000
(bootloader) partition-type:metadata: none
(bootloader) partition-size:metadata: 0x0000000001000000
(bootloader) partition-type:config: ext4
(bootloader) partition-size:config: 0x0000000000800000
(bootloader) partition-type:misc: none
(bootloader) partition-size:misc: 0x0000000000100000
(bootloader) partition-type:persistent: ext4
(bootloader) partition-size:persistent: 0x0000000000100000
(bootloader) partition-type:bootloader2: none
(bootloader) partition-size:bootloader2: 0x0000000004000000
(bootloader) partition-type:bootloader: vfat
(bootloader) partition-size:bootloader: 0x0000000004000000
(bootloader) max-download-size: 0x0000000010000000
(bootloader) battery-voltage:
(bootloader) version-bootloader: kernelflinger-02.19
(bootloader) device-type: PROD
(bootloader) product: bishop
all:
Finished. Total time: 1.098s
I can also boot into DNX FASTBOOT MODE using all 3 buttons, but I can't do anything in that mode, but the device is recognized using fastboot devices
Does anyone know how to use dnx fastboot mode? Or what is it?
Thank you
Wrong command
Hey! You should be using fastboot OEM unlock, not fastboot OEM lock. Also the unit doesn't have a way to enable adb from what I can tell.
Note: I have NO experience hacking amazon echo
Could you use the same method we use to hack the fire HD8 or HD10 with the brick.sh, then flash the bootrom, then enter a hacked fastboot? From what it looks like, recovery mode on the show looks like the same one used on the HD10.
Echo Show need to unlock
Hello
I tried with the following commands.
I tried with "fastboot oem unlock", but command is not working.
I want to unlock my amazon echo show devices. Or is there any way to open echo show without login with amazon account.
Please help me to solve the issue.
arcanandrei said:
Hello,
I want to know if someone can help me unlocking the bootloader of this device for installing custom rom/apps
It has an Intel Cherry Trail Processor
I can boot to fastboot using the Vol- and Power together and tried the following commands
fastboot oem unlock - returns OKAY but doesn't unlock the bootloader
Code:
fastboot oem lock
- returns that the device is already in the required state
Code:
fastboot flash twrp.img
- returns that it cannot be possible since the device is locked
Code:
fastboot boot twrp.img
- goes to the amazon logo and then right to fastboot again
Code:
fastboot getvar all
(bootloader) serialno: ------------------------ [hidden for purposes]
(bootloader) board: Intel Corp. Cherry Trail CR 0
(bootloader) device-state: locked
(bootloader) boot-state: GREEN
(bootloader) firmware: Intel Corporation CH2T.BSHP.X64.0005.R09.18091217
(bootloader) product-name: CHERRYVIEW D1 PLATFORM
(bootloader) secureboot: yes
(bootloader) off-mode-charge: 1
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) partition-type:vendor: ext4
(bootloader) partition-size:vendor: 0x0000000016C00000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x00000000FA800000
(bootloader) partition-type:data: ext4
(bootloader) partition-size:data: 0x00000000FA800000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x000000008CC00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x0000000020000000
(bootloader) partition-type:factory: none
(bootloader) partition-size:factory: 0x0000000002000000
(bootloader) partition-type:recovery: none
(bootloader) partition-size:recovery: 0x0000000002000000
(bootloader) partition-type:boot: none
(bootloader) partition-size:boot: 0x0000000002000000
(bootloader) partition-type:metadata: none
(bootloader) partition-size:metadata: 0x0000000001000000
(bootloader) partition-type:config: ext4
(bootloader) partition-size:config: 0x0000000000800000
(bootloader) partition-type:misc: none
(bootloader) partition-size:misc: 0x0000000000100000
(bootloader) partition-type:persistent: ext4
(bootloader) partition-size:persistent: 0x0000000000100000
(bootloader) partition-type:bootloader2: none
(bootloader) partition-size:bootloader2: 0x0000000004000000
(bootloader) partition-type:bootloader: vfat
(bootloader) partition-size:bootloader: 0x0000000004000000
(bootloader) max-download-size: 0x0000000010000000
(bootloader) battery-voltage:
(bootloader) version-bootloader: kernelflinger-02.19
(bootloader) device-type: PROD
(bootloader) product: bishop
all:
Finished. Total time: 1.098s
I can also boot into DNX FASTBOOT MODE using all 3 buttons, but I can't do anything in that mode, but the device is recognized using fastboot devices
Does anyone know how to use dnx fastboot mode? Or what is it?
Thank you
Click to expand...
Click to collapse
All Amazon echo show devices required unlock code which is generated from the serial number to unlock the devices.
Unfortunately this unlock code can be only retrieved inside amazon corp network through their internal tool for developing purpose.
Hello! I bought a second hand show 5 and the former owner has the account locked out. I can not do anything. When I go into configuration it tells me that it does not recognize the account in amazon.
I have thought that if I can change the serial number of the device, I could finish the configuration correctly.
Code:
fastboot getvar all
(bootloader) antirback_tee_version: 0x0103
(bootloader) antirback_lk_version: 0x0001
(bootloader) antirback_pl_version: 0x0001
(bootloader) rpmb_state: 1
(bootloader) lk_build_desc: cd178e6-20190703_190118
(bootloader) pl_build_desc: d14f08f-20190512_232119
(bootloader) secure: yes
(bootloader) prod: 1
(bootloader) otu_code: +QdtQ0mzlUklt9mtCmRNAYIKNnfW6akA
(bootloader) unlock_status: false
(bootloader) unlock_code: 0x???????????????????? [hidden for purposes]
(bootloader) serialno: ???????????????? [hidden for purposes]
(bootloader) max-download-size: 0x6d00000
(bootloader) off-mode-charge: 1
(bootloader) warranty: no
(bootloader) kernel: lk
(bootloader) product: CHECKERS
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 0.018s
I have tried this:
Code:
sudo fastboot oem unlock 0xMy_onlock_code
FAILED (remote: 'the command you input is restricted on locked hw')
fastboot: error: Command failed
I cannot access adb.
Any ideas to root or start adb from fastboot?
Any ideas to unlink the old user's account?
I already did a factory reset. Sorry for my english.
Hello , have any sucess?
halfblood* said:
Hello , have any sucess?
Click to expand...
Click to collapse
I got the bootloader unlock code just now using power and both volume buttons to boot fstboot then plugged my phone into micro USB on back running bugajager app
I have had some success using Bugjaeger on my android phone while attached to a couple of uncooperative devices, namely my Tesla style head unit, as well a "Class VR" headset I picked up on eBay . The headset was locked down fairly well, but it was no match for Bugjaeger. I ended up able to load my own launcher, and now it acts like any other rooted android. There may be other tools that can help, I am just sharing my experience with one app. Hope this helps. R*
memorixo said:
Hello! I bought a second hand show 5 and the former owner has the account locked out. I can not do anything. When I go into configuration it tells me that it does not recognize the account in amazon.
I have thought that if I can change the serial number of the device, I could finish the configuration correctly.
Code:
fastboot getvar all
(bootloader) antirback_tee_version: 0x0103
(bootloader) antirback_lk_version: 0x0001
(bootloader) antirback_pl_version: 0x0001
(bootloader) rpmb_state: 1
(bootloader) lk_build_desc: cd178e6-20190703_190118
(bootloader) pl_build_desc: d14f08f-20190512_232119
(bootloader) secure: yes
(bootloader) prod: 1
(bootloader) otu_code: +QdtQ0mzlUklt9mtCmRNAYIKNnfW6akA
(bootloader) unlock_status: false
(bootloader) unlock_code: 0x???????????????????? [hidden for purposes]
(bootloader) serialno: ???????????????? [hidden for purposes]
(bootloader) max-download-size: 0x6d00000
(bootloader) off-mode-charge: 1
(bootloader) warranty: no
(bootloader) kernel: lk
(bootloader) product: CHECKERS
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 0.018s
I have tried this:
Code:
sudo fastboot oem unlock 0xMy_onlock_code
FAILED (remote: 'the command you input is restricted on locked hw')
fastboot: error: Command failed
I cannot access adb.
Any ideas to root or start adb from fastboot?
Any ideas to unlink the old user's account?
I already did a factory reset. Sorry for my english.
Click to expand...
Click to collapse
Hi! Have you managed to do anything with it? I have a locked echo show 8, which I'm trying hard on finding a way to unlock it... Would very much appreciate any help on this matter, thanks!

[HELP][BRICK] ZE552KL Z012DC doesn't boot to system

Hello guys,
I need help. Definitely
My phone stopped booting into system after some service.
First a little brief:
Phone never showed any problems before.
LCD+Touch were replaced.
Phone stopped booting into system.
Stills boots/ works perfectly in fastboot, recovery and userdebug.
Tried:
factory reset
unlocking and relocking bootloader
flashing several factory and stock RAWs
stock recovery and TWRP
stock raw alone
update stock system from stock raw
twrp + stock rom + magisk
twrp + lineageos + magisk
several guides on this forum
Nothing works. Problem remains the same, doesn’t matter the alternative I try.
Now the whole story:
I’ve had this phone for a while. Always did the OTA updates. Never had problems… at all.
Some days ago, I dropped it and was finally able to break the screen. The lcd became black in some spots and had different brightness in others. Touch kind of worked, kind of got crazy after some seconds (and I had to turn the screen off and on again).
I’ve got some experience in repairing electronics and phones. So, I watched/read a dozen guides about this particular service, bought an original LCD+Touch kit, and replaced myself.
No apparent problems with that. The process is quite simple and straight forward. (I knew what I was doing. But if you tell me something might be wrong with that, I will look into it. I will take any help. Just tell me what to do.)
And so it begins.
I set my phone up again - without gluing anything, as it was the first test – and turn it on. It seems to boot normally… boot logo shows normally… boot animation seems to take longer than usual… the screen suddenly goes black.
I open the whole thing again, check every connector, everything is ok.
I try to turn it on again, now the phone turns off after just one or two seconds of boot animation.
I did then a factory reset, problem persisted just the same.
I thought to myself: “ok, then. System must be somehow corrupted.”
I updated the system to the lasted version in ASUS website trough adb sideload. Problem persisted.
“ok, maybe I must clear the system partition then… let’s go a little further”.
I read some guides, and proceeded to unlock the bootloader (flash factory raw, fastboot commands, flash oreo raw), flash TWRP and LineageOS.
When I turn it on again, a bit of hope. Boot animation takes, again, a long time. An “encrypting device” screen comes up and I believe it’s finally over. But no. The phone goes off after about 10 seconds of supposed encrypting and, when I turn it on again, same as before… two seconds of boot animation and then darkness.
After that I Just went deeper into the habbit hole.
Tried several brick fixes in sent by the XDA community.
Tried flashing RAWs using Asus Flash Tool (v1.0.0.86 (20201124)) and flashall_AFT.cmd (that comes inside de RAWs.
Tried all combination and orders I could imagine of the following RAWs:
CSC_ZE552KL_13.1301.1603.53_WW_Lock_20171128
CSC_ZE552KL_13_13_1_36_M2_6_7_P7_userdebug
WW_ZE552KL_13.20.10.137_M3.10.35_Phone-user.raw
WW_ZE552KL_14.2020.1703.28_M3.10.47.3_Phone-user.raw
WW_ZE552KL_15.0410.1712.31_M3.10.47.16_Phone-user.raw
WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw
It doesn’t matter. Whenever I flash a RAW, the phone goes to this encrypting process and then goes black. From there on, I can flash anything through adb sideload, fastboot or twrp…. It shows the boot logo, (possibly shows the dm-verity screen, depending on the set up), and goes off after about 2 seconds of boot animation.
Tested everything I could with TWRP: LCD, Touch, mounting partitions and storage seem to be working fine.
Tested everything I could with the factory RAW userdebug (using command fastboot oem enable-userdebug boots a very simple system (there’s an image below)): Again, LCD and touch work fine. Also, hard keys, wifi, Bluetooth, calling, messaging, 4G and both speakers are working.
And there we get to present time. I just don’t know what else I can do.
My next steps would be going into QFIL flashing. That would actually be new to me. But since I can use all these functions properly, it doesn’t seem to me that that’s the way to go.
Please help. I will take anything. Tell what I may have passed by. Send me the guides you think may help me, even if I’ve already tried.
I can give you any information you guys believe is pertinent.
I will start leaving here some info I think may help:
ZE552KL Z012DC ASUS_Z012DC Brazilian model BRAZIL
4GB RAM. 64GB storage.
Code:
C:\Users\Vanisi\Desktop\ZE552KL>fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4236000
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:O-CS4 - 4 - user
(bootloader) display-panel:
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) max-download-size: 0x1fe00000
(bootloader) partition-type:asdf:ext4
(bootloader) partition-size:asdf: 0x4000000
(bootloader) partition-type:APD:ext4
(bootloader) partition-size:APD: 0xd000000
(bootloader) partition-type:ADF:ext4
(bootloader) partition-size:ADF: 0x2000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x8000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xd683f7000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xf0000000
(bootloader) cpuid:046
(bootloader) project:ZE552KL
(bootloader) serialno:H2AZB601E85****
(bootloader) kernel:lk
(bootloader) product:MSM8953
all:
Finished. Total time: 0.281s
C:\Users\Vanisi\Desktop\ZE552KL>fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
(bootloader) Device is_authorized: false
(bootloader) ssn_num: H2AZB601E85****
(bootloader) isn_num: MB352KL0AB****
(bootloader) check_fused: 0
(bootloader) Device resize: false
(bootloader) BOOT_COUNT : 175
(bootloader) SB=Y
(bootloader) Re-partition: false
(bootloader) Device had been rooted: >>> YES <<< (Warranty void)
(bootloader) Device has copy fsg to fsgCA: false
(bootloader) Device last copy fsg status: fail
(bootloader) verity_mode: 1
(bootloader) is_ffu: false
(bootloader) verity_counter: 0
(bootloader) total verity_counter: 0
OKAY [ 0.203s]
Finished. Total time: 0.203s
C:\Users\Vanisi\Desktop\ZE552KL>fastboot oem system-info
(bootloader) board_info: msm8953
(bootloader) mem_info: 4GB
(bootloader) mmc_info:
(bootloader) product_name: ASUS_Z012D
(bootloader) product_locale: en-US
(bootloader) product_carrier: US-ASUS_Z012D-WW_Phone
(bootloader) csc_build_version: WW_ZE552KL-13.20.10.152-20161222
(bootloader) bt_mac: 2C4D5****B18
(bootloader) wifi_mac: 2C4D5****E38
(bootloader) imei: 35905207393****
(bootloader) imei2: 35905207393****
(bootloader) ssn: H2AZB601E85****
(bootloader) isn: MB352KL0A****
(bootloader) color: 1B
(bootloader) country: BR
(bootloader) customer: CKD
(bootloader) revenuecountry: BR
OKAY [ 0.188s]
Finished. Total time: 0.188s
(the **** don't actually come up... it's just to hide the information I believe may be sensitive)
Help. Please

Categories

Resources