Help needed
My device is on EDL mode ( showing on device manager as Qualcomm HS-USB QDLoader 9008).
I tried every single blankfash file from lolinet and my device not booted.
Mine is the brazillian version (XT2083-1_GUAMP_RETBR).
Someone have the correct file for Blankflashing my device or other solution for my problem?
Thanks in advance.
Hello friend, I created a Blankflash based on the latest version of android 11 (RPX31.Q2-58-17-7), it worked for me, if you want to try it do it at your own risk, I am not responsible for any possible problems let it happen.
RMS100 said:
Hello friend, I created a Blankflash based on the latest version of android 11 (RPX31.Q2-58-17-7), it worked for me, if you want to try it do it at your own risk, I am not responsible for any possible problems let it happen.
Click to expand...
Click to collapse
Worked fine for me, thank you.
my phone also returned to image, what did you do after that?
vtrxz said:
my phone also returned to image, what did you do after that?
Click to expand...
Click to collapse
You can use this tool from motorola to flash the latest Stock Rom on your device: https://www.motorola.com/us/rescue-and-smart-assistant/p
Thank you very much, my phone is working again thanks to you
RMS100 said:
Olá amigo, criei um Blankflash baseado na última versão do android 11 (RPX31.Q2-58-17-7), funcionou para mim, se você quiser experimentar faça por sua conta e risco, não me responsabilizo por quaisquer problemas possíveis deixe acontecer.
Click to expand...
Click to collapse
God bless you my friend, save me a lot!!!
Hello, I had the same problem and managed to get out of EDL mode, but when trying to install the stock rom via fastboot, an error occurred and, in the failed attempt to solve it, I ended up blocking the bootloader. Now I have my device bricked and the bootloader is locked.
I've already used Rescue and Smart Assistant and it can't finish the process. I can't flash any roms through adb either. It really is a misfortune.
Below is the information about my device:
C:\Users\whoami\Desktop\platform-tools>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-guamp_retail-252ee94a78-220503
(bootloader) product: guamp
(bootloader) board: guamp
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DP6DAB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5-M8=01 07 01 12
(bootloader) cpu: SM_KAMORTA_H 1.0
(bootloader) serialno: 0073117509
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: B74625DD
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 804464640
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: 352234676210270
(bootloader) imei2: 352234676210288
(bootloader) meid:
(bootloader) date: 04-30-2021
(bootloader) sku: XT2083-1
(bootloader) carrier_sku: XT2083-1
(bootloader) battid: SB18C45530
(bootloader) battery-voltage: 3904
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retbr
(bootloader) ro.build.fingerprint[0]: motorola/guamp_retail/guamp:11/RPX
(bootloader) ro.build.fingerprint[1]: 31.Q2-58-17-7/c9ebb:user/release-k
(bootloader) ro.build.fingerprint[2]: eys
(bootloader) ro.build.version.qcom: LA.UM.9.15.r1-02200-KAMORTA.0
(bootloader) version-baseband: HA10_32.40.02.106R DFLT_FSG
(bootloader) kernel.version[0]: Linux version 4.19.157-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Fri A
(bootloader) kernel.version[4]: pr 29 11:24:11 CDT 2022
(bootloader) git:xbl: MBM-3.0-guamp_retail-0ed29cb2f-220503
(bootloader) git:xbl_config: MBM-3.0-guamp_retail-0ed29cb2f-220503
(bootloader) git:abl: MBM-3.0-guamp_retail-252ee94a78-220503
(bootloader) git:rpm: MBM-3.0-guamp_retail-834e250d-220503
(bootloader) git:tz: MBM-3.0-guamp_retail-2c435ecc4-220503
(bootloader) git:hyp: MBM-3.0-guamp_retail-2c435ecc4-220503
(bootloader) git:devcfg: MBM-3.0-guamp_retail-2c435ecc4-220503
(bootloader) git:keymaster: MBM-3.0-guamp_retail-4b088521-220503
(bootloader) git:storsec: MBM-3.0-guamp_retail-4b088521-220503
(bootloader) git:uefisecapp: MBM-3.0-guamp_retail-4b088521-220503
(bootloader) gitrov: MBM-3.0-guamp_retail-2c435ecc4-220503
(bootloader) git:qupfw: MBM-3.0-guamp_retail-2c412ce-220503
(bootloader) frp-state: protected (77)
(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: 4
(bootloader) slot-retry-count:_b: 7
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D19213
(bootloader) primary-display: hlt_ili9882h_video_display
(bootloader) secondary-display:
all: listed above
Finished. Total time: 0.125s
friend, I have the same problem, the motorola updated and the version of the blankflash that I need is the version RPXS31.Q2-58-17-7-2 I looked in several places on the internet and it really doesn't have it. help!
L1p3Droid_BR said:
friend, I have the same problem, the motorola updated and the version of the blankflash that I need is the version RPXS31.Q2-58-17-7-2 I looked in several places on the internet and it really doesn't have it. help!
Click to expand...
Click to collapse
Did you try the blankflash that was made available here? maybe it still works as the latest Motorola update was just a security patch.
RMS100 said:
Did you try the blankflash that was made available here? maybe it still works as the latest Motorola update was just a security patch.
Click to expand...
Click to collapse
yes, I tried but without success.
RMS100 said:
Did you try the blankflash that was made available here? maybe it still works as the latest Motorola update was just a security patch.
Click to expand...
Click to collapse
follows the photo, but it does not restart to fastboot. it is version xt2083-3 retbr
{
"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"
}
L1p3Droid_BR said:
follows the photo, but it does not restart to fastboot. it is version xt2083-3 retb
Click to expand...
Click to collapse
L1p3Droid_BR said:
follows the photo, but it does not restart to fastboot. it is version xt2083-3 retbrView attachment 5701121
Click to expand...
Click to collapse
Ok, try this, download LSMA from motorola and try to run the fastboot commands with the device connected to the PC with the program already open. if the device is recognized, download the stock and install using the program.
RMS100 said:
Ok, try this, download LSMA from motorola and try to run the fastboot commands with the device connected to the PC with the program already open. if the device is recognized, download the stock and install using the program.
Click to expand...
Click to collapse
the device does not turn on. even the cmd command saying that it was completed for fastboot, but it is false, it does not show any signal, it just exits edl mode only and unresponsive and does not recognize on the computer even with drivers and platform tools configured on the computer. It's a brick, it only enters edl at the moment, I believe only with the blankflash of the current version.
RMS100 said:
Ok, try this, download LSMA from motorola and try to run the fastboot commands with the device connected to the PC with the program already open. if the device is recognized, download the stock and install using the program.
Click to expand...
Click to collapse
Worse than I've done it using LMSA, I left it in the background and it's still not recognized.
L1p3Droid_BR said:
Worse than I've done it using LMSA, I left it in the background and it's still not recognized.
Click to expand...
Click to collapse
Hello friend, I didn't find a specific firmware for your model (XT2083-3), apparently the only difference between this model and the XT2083-1 is the NFC, so I made this blankflash based on the latest firmware of the model XT2083-1. If you want to try, do it at your own risk, I am not responsible for any problems.
RMS100 said:
Hello friend, I didn't find a specific firmware for your model (XT2083-3), apparently the only difference between this model and the XT2083-1 is the NFC, so I made this blankflash based on the latest firmware of the model XT2083-1. If you want to try, do it at your own risk, I am not responsible for any problems.
Click to expand...
Click to collapse
I tried, I didn't succeed. I tried, without success. this phone's software is hosted on lolinet. can you flash this software? Follow the link https://mirrors.lolinet.com/firmware/motorola/guamp/official/RETBR/
L1p3Droid_BR said:
Eu tentei, não tive sucesso. Eu tentei, sem sucesso. o software deste telefone está hospedado no lolinet. você pode mostrar este software? Siga o link https://mirrors.lolinet.com/firmware/motorola/guamp/official/RETBR/
Click to expand...
Click to collapse
Hi, I used exactly the firmware available on lolinet, I think unfortunately I can't do anything else for you.
RMS100 said:
Hi, I used exactly the firmware available on lolinet, I think unfortunately I can't do anything else for you.
Click to expand...
Click to collapse
Thank you for making yourself available to help. It went into Hard brick after deleting the vendor by passing a gsi. At least the blankflash created can help another forum member.
hello someones knows where are the edl points in moto g9 play? i putted in contacts a lot of places and i cant know the place
Related
After hardbrick, only blinking led, and devices in old Qualcomm HS-USB QDLoader 9008 mode,succesfully back to fastboot and recovery, with blankflash.
xt1805 eu
now i'm try to flash stock, but still with error: (downgrading, preflash validation, no gpt.bin flash, no bl flash, erorr on flash oem partition and chunk0)
(bootloader) version-bootloader: moto-msm8953-C0.C5
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 10C7D55D00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:7.1.1
(bootloader) ro.build.fingerprint[1]: /NPSS26.116-26-11/12:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.26.286.12.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8953_24.34.07.35R SANDERS_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-gce86ddc-0013
(bootloader) kernel.version[1]: 4-g3301624 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9 20150123 (prerelease) (GCC) ) #
(bootloader) kernel.version[3]: 1 SMP PREEMPT Thu Mar 1 15:12:52 CST 201
(bootloader) kernel.version[4]: 8
(bootloader) sbl1.git: git=MBM-NG-VC0.C5-0-g98be833
(bootloader) rpm.git: git=MBM-NG-VC0.C5-0-g5578f74
(bootloader) tz.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) devcfg.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) keymaster.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) cmnlib.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) cmnlib64.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) prov.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) aboot.git: git=MBM-NG-VC0.C5-0-g99aa1c1
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
any suggestion plz ?
Moto G5S plus
I think parttion table go corrupted, with downgrade-upgrade, after custom mod, any way to correct parttion table ?? gpt.bin flash give me error
bro how you recover hard brick ? share blankflash.please
How u unbrick? Please share blank flash
noio said:
After hardbrick, only blinking led, and devices in old Qualcomm HS-USB QDLoader 9008 mode,succesfully back to fastboot and recovery, with blankflash.
xt1805 eu
now i'm try to flash stock, but still with error: (downgrading, preflash validation, no gpt.bin flash, no bl flash, erorr on flash oem partition and chunk0)
(bootloader) version-bootloader: moto-msm8953-C0.C5
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 10C7D55D00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:7.1.1
(bootloader) ro.build.fingerprint[1]: /NPSS26.116-26-11/12:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.26.286.12.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8953_24.34.07.35R SANDERS_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-gce86ddc-0013
(bootloader) kernel.version[1]: 4-g3301624 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9 20150123 (prerelease) (GCC) ) #
(bootloader) kernel.version[3]: 1 SMP PREEMPT Thu Mar 1 15:12:52 CST 201
(bootloader) kernel.version[4]: 8
(bootloader) sbl1.git: git=MBM-NG-VC0.C5-0-g98be833
(bootloader) rpm.git: git=MBM-NG-VC0.C5-0-g5578f74
(bootloader) tz.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) devcfg.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) keymaster.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) cmnlib.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) cmnlib64.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) prov.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) aboot.git: git=MBM-NG-VC0.C5-0-g99aa1c1
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
any suggestion plz ?
Click to expand...
Click to collapse
How u unbrick? Please share blank flash
Blankflash attached
madeaboutu said:
How u unbrick? Please share blank flash
Click to expand...
Click to collapse
blankflash attached
moto g5s plus
if succesful reboot, i have procedure to stock oreo via twrp
noio said:
if succesful reboot, i have procedure to stock oreo via twrp
Click to expand...
Click to collapse
Thanks,shall share you [email protected]
noio said:
After hardbrick, only blinking led, and devices in old Qualcomm HS-USB QDLoader 9008 mode,succesfully back to fastboot and recovery, with blankflash.
xt1805 eu
now i'm try to flash stock, but still with error: (downgrading, preflash validation, no gpt.bin flash, no bl flash, erorr on flash oem partition and chunk0)
(bootloader) version-bootloader: moto-msm8953-C0.C5
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 10C7D55D00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:7.1.1
(bootloader) ro.build.fingerprint[1]: /NPSS26.116-26-11/12:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.26.286.12.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8953_24.34.07.35R SANDERS_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-gce86ddc-0013
(bootloader) kernel.version[1]: 4-g3301624 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9 20150123 (prerelease) (GCC) ) #
(bootloader) kernel.version[3]: 1 SMP PREEMPT Thu Mar 1 15:12:52 CST 201
(bootloader) kernel.version[4]: 8
(bootloader) sbl1.git: git=MBM-NG-VC0.C5-0-g98be833
(bootloader) rpm.git: git=MBM-NG-VC0.C5-0-g5578f74
(bootloader) tz.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) devcfg.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) keymaster.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) cmnlib.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) cmnlib64.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) prov.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) aboot.git: git=MBM-NG-VC0.C5-0-g99aa1c1
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
any suggestion plz ?
Click to expand...
Click to collapse
bro try to flash stock oreo 8.1 latest , bucz your are flashing 7.1.1 may be it is giving you error
re-brick ....
After blankflash, no way of flash system and oem, restoring oreo backup via twrp ok, phone boot, but no imei on oreo, because have restore twrp backup (with "getvar imei" i see correct imei), but no way of flashing system and oem via fastboot or adb, frustrated !!!!!! i have restored a loader.img from extsdcard, but are wrong, people that send me right blankflash, send me wrong image loader, now i'm rebricked with only fastboot of wrong loader(bl) restored ..... In return, i think, i've succesfoul downgraded bl, baseband and othr stuff ..... now i'm on bricked Hybrid Moto .....
madeaboutu said:
Thanks,shall share you [email protected]
Click to expand...
Click to collapse
Didnt got success with this:crying:
madeaboutu said:
Didnt got success with this:crying:
Click to expand...
Click to collapse
any solution to the error?
i hope it works
madeaboutu said:
Didnt got success with this:crying:
Click to expand...
Click to collapse
Hi, boot the twrp image and go to wipe and erase all, try until it works and then install the stock android oreo using the adb, if you got an error try again because there is a corruption of the security patches. The IMEI works after the upgrade the security patches, they are many. I have a similar trouble with my moto g5s plus. Good luck
Thank you so much awesome my congratulations God bless you
Muito obrigado sensacional meus parabéns que Deus abençoe vocês
Hey there, I have two questions.
First, is it ok for a blankflash file to be less than 2Mb in size? I saw someone claiming he managed to reverse engineer xt1806 blankflash but claimed it to be too big for him to upload.
Also, does anyone know if the xt1805 blankflash would work for a xt1806 or am I gonna mess it up further than I did? I am unable to find xt1806 blankflash.
It's been like year and a half with a hard bricked xt1806 and I am so upset about being unable to bring it back. I went to my old phone but it's not usable anymore and I'm not situation to buy a new one. Argentina sucks
Thanks in advance to any kind of reply
noio said:
blankflash attached
Click to expand...
Click to collapse
You saved my day. Thank you so much :good:
Ooops. Looks like my phone is XT1804 and this has lead me into a different situation now.
Update: Managed to hard brick my phone again by intentionally flashing the wrong bootloader which is apparently the only one that got accepted. All other legit versions gave errors. Now preparing a 32GB SD card with mmcblk0. Will try to boot with that and flash the stock ROM. Shall update if I get through. Fingers crossed.
applechap said:
You saved my day. Thank you so much :good:
Ooops. Looks like my phone is XT1804 and this has lead me into a different situation now.
Update: Managed to hard brick my phone again by intentionally flashing the wrong bootloader which is apparently the only one that got accepted. All other legit versions gave errors. Now preparing a 32GB SD card with mmcblk0. Will try to boot with that and flash the stock ROM. Shall update if I get through. Fingers crossed.
Click to expand...
Click to collapse
Hey, so you tried 1805's on a 1804 and it didn't work? I'm about to try it on a 1806, they are supposed to have the same processor so I don't get why it wouldn't work
Sagazdelrey said:
Hey, so you tried 1805's on a 1804 and it didn't work? I'm about to try it on a 1806, they are supposed to have the same processor so I don't get why it wouldn't work
Click to expand...
Click to collapse
Its because 1805 boot loader is customized for Verizion USA. Sure enough it kicked the phone out of the hard brick. But I couldn't install anything after that due to the mismatch. Looks like the only way out is to open the phone and program the chip. Too much for a spare phone for me. So its a paper weight as of now.
Today I was trying to install the original stock ROM on my Moto G5s plus ....When I used the last command fastboot reboot my mobile didn't started again....What to do now please help me I am not able to start my device again in fastboot mode or recovery mode... infact it is not turning on....even when kept on charging.....please help me out and mention steps as in order what to do.....please
Help
my phone is hard bricked Moto G5s Plus given bankflash is not working can u please help me ?
email [email protected]
Moto g5s easy hard bricked solutions on this video
Moto g5s easy solution youtube my youtube channel please search P2bro techno
Good Afternoon community, I have a small question about my Moto Z3 Play beckham Brazilian model XT 1929-5. but checking bootloader and settings found that it is showing the incorrect SKU with the number TX1601, if I am not mistaken this number and the Moto G4 plus, there is a way to repair this, and the phone works perfectly running Android 9 Whoever can help will be grateful.
l.rochas said:
Good Afternoon community, I have a small question about my Moto Z3 Play beckham Brazilian model XT 1929-5. but checking bootloader and settings found that it is showing the incorrect SKU with the number TX1601, if I am not mistaken this number and the Moto G4 plus, there is a way to repair this, and the phone works perfectly running Android 9 Whoever can help will be grateful.
Click to expand...
Click to collapse
Do you use Magisk, root or any other kind of "device spoofing"???
Nothing, bootloader locked factory. When I checked the incorrect SKU, the bootloader was the first thing I checked and to my surprise it was blocked.
Can you take a picture of the bootloader screen, usually there's information about the SKU in there...
---------- Post added at 02:33 PM ---------- Previous post was at 02:23 PM ----------
Also, try flashing this ROM, it already contains the May 1st patches:
https://forum.xda-developers.com/showpost.php?p=79122632&postcount=45
you can get more informations on how to flash here:
https://forum.xda-developers.com/z3-play/how-to/firmware-oficial-9-0-0-pie-instalacion-t3911995
Thanks for replying, as requested I will have a photo of the bootloader screen in this mode the sku is incorrect, and also the function barcodes in this, the sku is correct.
Another photo I took was from rsd lite shows an error of (the phone could not switch to fastboot mode) so I can just update the phone in Minimal ADB and Fastboot.
I'm sticking down the getvar all I did on adb walks fastboot
C:\Minimal ADB and Fastboot>mfastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-beckham_retail-8ca64c4-190327
(bootloader) product: beckham
(bootloader) board: beckham
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: BRAZIL
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: 0049643811
(bootloader) cid: 0x0000
(bootloader) channelid: 0x1b
(bootloader) uid: A93A2333
(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: I hid
(bootloader) meid:
(bootloader) date: 03-16-2019
(bootloader) sku: XT1601
(bootloader) carrier_sku: XT1929-5
(bootloader) battid: SB18C20117
(bootloader) battery-voltage: 4202
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/beckham/beckham:9/PPWS29.
(bootloader) ro.build.fingerprint[1]: 131-27-1-2/7699:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.201.3.beckham.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05500-sdm660.0
(bootloader) version-baseband: M636_25.43.01.89R BECKHAM_BRAZILDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gcc5f412 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Wed Mar 27 12:33:10 CDT 2019
(bootloader) git:abl: MBM-3.0-beckham_retail-8ca64c4-190327
(bootloader) git:xbl: MBM-3.0-beckham_retail-d286d94-190327
(bootloader) git:rpm: MBM-3.0-beckham_retail-4696e9e-190327
(bootloader) git:tz: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:hyp: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:devcfg: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:cmnlib: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:cmnlib64: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:keymaster: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:storsec: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retla
(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.159s
l.rochas said:
Good Afternoon community, I have a small question about my Moto Z3 Play beckham Brazilian model XT 1929-5. but checking bootloader and settings found that it is showing the incorrect SKU with the number TX1601, if I am not mistaken this number and the Moto G4 plus, there is a way to repair this, and the phone works perfectly running Android 9 Whoever can help will be grateful.
Click to expand...
Click to collapse
Me pasa lo mismo solo que estoy con Android 8.1 Parche de seguridad 1 de Setiembre de 2018 Compilacion OPWS28.70-31-2
Alguna solucion para poder actualizar?
l.rochas said:
Thanks for replying, as requested I will have a photo of the bootloader screen in this mode the sku is incorrect, and also the function barcodes in this, the sku is correct.
Another photo I took was from rsd lite shows an error of (the phone could not switch to fastboot mode) so I can just update the phone in Minimal ADB and Fastboot.
I'm sticking down the getvar all I did on adb walks fastboot
Click to expand...
Click to collapse
Did you tried to flash the ROMs i've posted here???
tb110188 said:
Did you tried to flash the ROMs i've posted here???
Click to expand...
Click to collapse
yes, I updated the rom as you mentioned it, and after restart it shows update of May 2019, but continues with the incorrect sku.
yes, the same as you posted with the May 2019 update.
Did you manage to solve the problem?
My XT1802 MOTO G5S Plus went on updating, directly from Google, and bricked. Now it shows this string when I use getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.12(*)
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(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: MSM8953
(bootloader) serialno: 9d2d9af7
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: B09C22F200000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 534773760
(bootloader) reason: Last time flashing failed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC2.12-0-g07ff23c
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Click to expand...
Click to collapse
I don't know what else to do. Tried at least 10 different firmwares, but nothing comes out of it. Every single one of them was rejected due to invalid image or something like that, and I can't unlock the bootloader (oem) because the phone bricked with it locked.
How to proceed?
PLease give more details and current status, are you able to boot to recovery or bootloader. You may need a blankflash file fore your model.
If anyone has a blankflash file for XT1802 I would appreciate a lot!!!
pradeeppk said:
PLease give more details and current status, are you able to boot to recovery or bootloader. You may need a blankflash file fore your model.
Click to expand...
Click to collapse
It turns on but goes to a recovery mode which I can't do anything.
I can only view the status on pic 1 and view bootloader log on pic 2, anything else seems not to be working properly.
Is there a blank flash available for the XT1802 model?
{
"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"
}
bump, seriously i need help
Kudsey said:
It turns on but goes to a recovery mode which I can't do anything.
I can only view the status on pic 1 and view bootloader log on pic 2, anything else seems not to be working properly.
Is there a blank flash available for the XT1802 model?
Click to expand...
Click to collapse
You need to flash the device using fastboot and the error you are getting is due to firmware is not singed by Motorola , so you need singed image firmware, you can have one from here
https://mirrors.lolinet.com/firmware/moto/sanders/official/
Then just flash the rom and the device will boot up.
riyan65 said:
You need to flash the device using fastboot and the error you are getting is due to firmware is not singed by Motorola , so you need singed image firmware, you can have one from here
https://mirrors.lolinet.com/firmware/moto/sanders/official/
Then just flash the rom and the device will boot up.
Click to expand...
Click to collapse
I've sent it to service and they said it would require a board replacement, which is set up for tomorrow. Would this solution solve the IMEI issue as well? If so then I'll go there with my laptop today and try to flash with these files.
Kudsey said:
I've sent it to service and they said it would require a board replacement, which is set up for tomorrow. Would this solution solve the IMEI issue as well? If so then I'll go there with my laptop today and try to flash with these files.
Click to expand...
Click to collapse
It will solve IMEI problem too, if you flash Oreo firmware.
riyan65 said:
It will solve IMEI problem too, if you flash Oreo firmware.
Click to expand...
Click to collapse
Tried several of these roms in the link you posted. None of the worked, the phone keeps rejecting them, even though I certified myself of downloading the most recent ones. Any tips?
Kudsey said:
Tried several of these roms in the link you posted. None of the worked, the phone keeps rejecting them, even though I certified myself of downloading the most recent ones. Any tips?
Click to expand...
Click to collapse
When you try to flash bootloader, what failure does it give security downgrade or verification failed??? And did you unlock the bootloader before and bricked once.
Does anyone have mmcblk0.img for moto G5s plus (XT18xx) , My phone just blinks LED , is not detected by pc
Hi Everyone have a stock rom of moto x4 whit this version of bootloader?
Code:
BL: MBM-3.0-payton_retail-0e6e7ce-181231
I download all retail stock roms on lolinet, around 80gb of stock roms for x4 and all have other BL versions...
The PPWS29.69-26-4 have this MBM Version: MBM-3.0-payton_retail-6b0c3d7-181231
But 6b0c3d7 i need whit 0e6e7ce because all the sotck roms say (Bootloader) Permison denied
My x4 dont have system to boot and have bootloader locked, only can flash the stock rom whit same bootloader version
llue45 said:
Hi Everyone have a stock rom of moto x4 whit this version of bootloader?
Code:
BL: MBM-3.0-payton_retail-0e6e7ce-181231
I download all retail stock roms on lolinet, around 80gb of stock roms for x4 and all have other BL versions...
The PPWS29.69-26-4 have this MBM Version: MBM-3.0-payton_retail-6b0c3d7-181231
But 6b0c3d7 i need whit 0e6e7ce because all the sotck roms say (Bootloader) Permison denied
My x4 dont have system to boot and have bootloader locked, only can flash the stock rom whit same bootloader version
Click to expand...
Click to collapse
I will jump in here briefly. You may be getting the bootloader error because your phone has a 9 bootloader and you are trying to flash it with an 8 or 7 bootloader. I am assuming your phone was Amazon, yes?
In lolinet moto/payton/official/AMZ I see:
file "XT1900-1_PAYTON_AMZ_9.0_PPW29.69-26_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2019-01-16 13:03 2263643 KB"
Have you tried that?
If not Amazon, do not try that but reply back.
KrisM22 said:
I will jump in here briefly. You may be getting the bootloader error because your phone has a 9 bootloader and you are trying to flash it with an 8 or 7 bootloader. I am assuming your phone was Amazon, yes?
In lolinet moto/payton/official/AMZ I see:
file "XT1900-1_PAYTON_AMZ_9.0_PPW29.69-26_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2019-01-16 13:03 2263643 KB"
Have you tried that?
If not Amazon, do not try that but reply back.
Click to expand...
Click to collapse
i have the PPW29.69-26 retail, the bootloader is the same between retail and amz version and i try with that, the result is the same (Bootloader) Permison denied...
Code:
BUILD REQUEST INFO:
SW Version: payton-user 9 PPW29.69-26 7a8e1 release-keysM660_7042.27.01.89R
MBM Version: MBM-3.0-payton_retail-6b0c3d7-181117
Modem Version: M660_7042.27.01.89R
FSG Version: FSG-660-01.95
Build Fingerprint: motorola/payton/payton:9/PPW29.69-26/7a8e1:user/release-keys
CQATest App Version: 6.0.4
My moto x4 isnt amz is openmx...My getvar is
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-0e6e7ce-181231
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: LATAM
(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: ZY224QT2VT
(bootloader) cid: 0x0032
(bootloader) channelid: 0x29
(bootloader) uid: AB7DEE02
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: 356486081004948
(bootloader) meid:
(bootloader) date: 01-11-2018
(bootloader) sku: XT1900-4
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 3846
(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]: -26-4/a2a2:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.211.11.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: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g6448940 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Mon Dec 31 10:17:24 CST 2018
(bootloader) git:abl: MBM-3.0-payton_retail-0e6e7ce-181231
(bootloader) git:xbl: MBM-3.0-payton_retail-6b0c3d7-181231
(bootloader) git:pmic: MBM-3.0-payton_retail-6b0c3d7-181231
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-181231
(bootloader) git:tz: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) git:hyp: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) git:devcfg: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) git:cmnlib: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) git:keymaster: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) git:prov: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) git:storsec: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: openmx
(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: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 5.939s
Okay. 1900-4
unlocked at motorola
flashed lineage 16
erased system
locked the phone but without a system???????? how?
and when you try to unlock the phone again as you did first, what happens?
You got the 2 sets of code above by doing what? booting to bootloader, connecting to PC and issuing what commands?
Could you give me a picture of your bootloader screen. Thanks.
I notice looking at lineage 16 in X4 ROMs, that though it is based on pie (9), the OP on that thread says it is based on Oreo 8.1
Assuming that is correct, you couldn't have a Pie bootloader, but an Oreo bootloader (?) But your getvar says 29.69 which is Pie.
(confused!) but let me have pic of your bootloader screen please.
EDIT: You said"...all ok...but i erase all the system and by mistake i reunlock the bootloader but whitout system...
I cant start sistem because not exist! I cant reflash because bootloader is lock..."
When you issued that "lock" what ROM were you trying to flash? what ROM was present in that flash? Did that flash change the bootloader?
KrisM22 said:
Okay. 1900-4
unlocked at motorola
flashed lineage 16
erased system
locked the phone but without a system???????? how?
and when you try to unlock the phone again as you did first, what happens?
You got the 2 sets of code above by doing what? booting to bootloader, connecting to PC and issuing what commands?
Could you give me a picture of your bootloader screen. Thanks.
I notice looking at lineage 16 in X4 ROMs, that though it is based on pie (9), the OP on that thread says it is based on Oreo 8.1
Assuming that is correct, you couldn't have a Pie bootloader, but an Oreo bootloader (?) But your getvar says 29.69 which is Pie.
(confused!) but let me have pic of your bootloader screen please.
EDIT: You said"...all ok...but i erase all the system and by mistake i reunlock the bootloader but whitout system...
I cant start sistem because not exist! I cant reflash because bootloader is lock..."
When you issued that "lock" what ROM were you trying to flash? what ROM was present in that flash? Did that flash change the bootloader?
Click to expand...
Click to collapse
Hi bro, sorry, i have a time without internet access...
1.-
Code:
locked the phone but without a system???????? how?
First i erase the partitions in twrp because i want a clean instalation, after this i unlock the bootloader runing the wrong code "fastboot lock oem", for that reason i have bootloader locked and not android system...
2.-
Code:
and when you try to unlock the phone again as you did first, what happens?
it say "enable OEM unlocking on Android"
I need enter to android and in developer options active oem unlock...But i dont have android system...
3.-
Could you give me a picture of your bootloader screen. Thanks.
Click to expand...
Click to collapse
{
"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"
}
4.-
Code:
When you issued that "lock" what ROM were you trying to flash? what ROM was present in that flash? Did that flash change the bootloader?
I lock the bootloader before try to flash, before to erase the system i have lineage OS 16
llue45 said:
Hi bro, sorry, i have a time without internet access...
...snip...
4.-
Code:
When you issued that "lock" what ROM were you trying to flash? what ROM was present in that flash? Did that flash change the bootloader?
I lock the bootloader before try to flash, before to erase the system i have lineage OS 16
Click to expand...
Click to collapse
Thanks. Sorry if repeat, but I am confused.
You "locked the bootloader", or, it WAS locked since you never unlocked it. Or did you at one point have it unlocked?
How did you manage to lock it???
Thanks.
KrisM22 said:
Thanks. Sorry if repeat, but I am confused.
You "locked the bootloader", or, it WAS locked since you never unlocked it. Or did you at one point have it unlocked?
How did you manage to lock it???
Thanks.
Click to expand...
Click to collapse
I locked the bootloader after unlock...
I do this...
1.-Unlock Bootloader
2.-Flash TWRP
3.-FLASH LINEAGE OS 16
4.-ERASE SYSTEM FORMATING PARTITIONS
5.-LOCK BOOTLOADER WITH COMAND "fastboot oem lock"
6.-Im stupid guy ... i know
In just five hours i destroy my new moto x4
llue45 said:
...snip...
Click to expand...
Click to collapse
llue45 said:
I locked the bootloader after unlock...
I do this...
1.-Unlock Bootloader
2.-Flash TWRP
3.-FLASH LINEAGE OS 16
4.-ERASE SYSTEM FORMATING PARTITIONS
5.-LOCK BOOTLOADER WITH COMAND "fastboot oem lock"
6.-Im stupid guy ... i know
In just five hours i destroy my new moto x4
Click to expand...
Click to collapse
I was afraid of that. I have no idea. If sd_shadow's thoughts don't help, I guess send it back to Moto to be factory reset. Sorry.
Been seeing too many folks waylaid by lineage; and re-locking bootloader.
:crying:
KrisM22 said:
I was afraid of that. I have no idea. If sd_shadow's thoughts don't help, I guess send it back to Moto to be factory reset. Sorry.
Been seeing too many folks waylaid by lineage; and re-locking bootloader.
:crying:
Click to expand...
Click to collapse
Thanks for all your support bro You are an excellent person
The real problem is folks, who should know better, posting bat files with that lock command, and noobs coming along and using them.
---------- Post added at 05:30 PM ---------- Previous post was at 05:14 PM ----------
llue45 said:
Thanks for all your support bro You are an excellent person
Click to expand...
Click to collapse
You're welcome - wish I could have helped.
hello when this happens you need to look for the rom with the VPN activated, because it is not the same in your country. If the BL is not the same, the rom does not pass.
EN-US:
In short I can't flash on any official device rom, and the bootloader is unlocked, which I actually need to enable and the OEM at the developer's option.
But I can't turn on the device because the phone says it has a different operating system, and goes back to fastboot. (I can't go to any other screen besides fastboot)
Can anyone help me with this?
ps: I'm using the translator because I don't speak English.
PT-BR:
Resumidamente eu não consigo da flash em nenhuma rom oficial do dispositivo, e o bootloader esta desbloqueado, o que na verdade preciso habilitar e o OEM na opção do desenvolvedor.
Mais não consigo ligar o aparelho pois o celular diz está com um sistema operacional diferente, e volta para o fastboot. (Não consigo ir para nenhuma outra tela fora o fastboot)
Alguém pode me ajudar com isso?
ps: Eu tou usando o Tradutor pois não falo inglês.
PU Kirito LP said:
EN-US:
In short I can't flash on any official device rom, and the bootloader is unlocked, which I actually need to enable and the OEM at the developer's option.
But I can't turn on the device because the phone says it has a different operating system, and goes back to fastboot. (I can't go to any other screen besides fastboot)
Can anyone help me with this?
ps: I'm using the translator because I don't speak English.
PT-BR:
Resumidamente eu não consigo da flash em nenhuma rom oficial do dispositivo, e o bootloader esta desbloqueado, o que na verdade preciso habilitar e o OEM na opção do desenvolvedor.
Mais não consigo ligar o aparelho pois o celular diz está com um sistema operacional diferente, e volta para o fastboot. (Não consigo ir para nenhuma outra tela fora o fastboot)
Alguém pode me ajudar com isso?
ps: Eu tou usando o Tradutor pois não falo inglês.
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
fastboot getvar all
sd_shadow said:
What does getvar all say?
Code:
fastboot getvar all
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
------------------
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9-191220
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5=FF M6=04 M7=10 M8=10
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: 0055749849
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 0F2A4B3E
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355577096137011
(bootloader) meid:
(bootloader) date: 04-05-2019
(bootloader) sku: XT1965-2
(bootloader) carrier_sku: XT1965-2
(bootloader) battid: SB18C44559
(bootloader) battery-voltage: 4320
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/lake_n/lake_n:9/PPW29.98-
(bootloader) ro.build.fingerprint[1]: 28/b7d2f:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.31.31.lake.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05200-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g73ca513-0001
(bootloader) kernel.version[1]: 1-g007505b ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9.x 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Tue Dec 11 09:54:13 CST
(bootloader) kernel.version[4]: 2018
(bootloader) git:abl: MBM-3.0-lake_retail-38523c9-191220
(bootloader) git:xbl: MBM-3.0-lake_retail-923e768-191220
(bootloader) gitmic: MBM-3.0-lake_retail-923e768-191220
(bootloader) git:rpm: MBM-3.0-lake_retail-50d7845-dirty-191220
(bootloader) git:tz: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:hyp: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:devcfg: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:cmnlib: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:cmnlib64: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:keymaster: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) gitrov: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:storsec: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retbr
(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.312s
PU Kirito LP said:
What does getvar all say?
------------------
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9-191220
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5=FF M6=04 M7=10 M8=10
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: 0055749849
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 0F2A4B3E
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355577096137011
(bootloader) meid:
(bootloader) date: 04-05-2019
(bootloader) sku: XT1965-2
(bootloader) carrier_sku: XT1965-2
(bootloader) battid: SB18C44559
(bootloader) battery-voltage: 4320
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/lake_n/lake_n:9/PPW29.98-
(bootloader) ro.build.fingerprint[1]: 28/b7d2f:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.31.31.lake.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05200-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g73ca513-0001
(bootloader) kernel.version[1]: 1-g007505b ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9.x 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Tue Dec 11 09:54:13 CST
(bootloader) kernel.version[4]: 2018
(bootloader) git:abl: MBM-3.0-lake_retail-38523c9-191220
(bootloader) git:xbl: MBM-3.0-lake_retail-923e768-191220
(bootloader) gitmic: MBM-3.0-lake_retail-923e768-191220
(bootloader) git:rpm: MBM-3.0-lake_retail-50d7845-dirty-191220
(bootloader) git:tz: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:hyp: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:devcfg: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:cmnlib: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:cmnlib64: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:keymaster: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) gitrov: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:storsec: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retbr
(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.312s
Click to expand...
Click to collapse
Says bootloader is locked.
Code:
securestate: flashing_locked
And baseband is missing
Code:
version-baseband: <not found>
Try using the unlock code again.
Sent from my ocean using XDA Labs
---------- Post added at 08:08 PM ---------- Previous post was at 08:04 PM ----------
If that doesn't work see
https://forum.xda-developers.com/showpost.php?p=81614501&postcount=9
Sent from my ocean using XDA Labs
sd_shadow said:
Says bootloader is locked.
Code:
securestate: flashing_locked
And baseband is missing
Code:
version-baseband: <not found>
Try using the unlock code again.
Sent from my ocean using XDA Labs
---------- Post added at 08:08 PM ---------- Previous post was at 08:04 PM ----------
If that doesn't work see
https://forum.xda-developers.com/showpost.php?p=81614501&postcount=9
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
------------------
check 'allow oem unlock' in android settings developer (bootloader) options.
is sending I enable, plus the internet does not pay for lack of the modem.
even if i use bluetooth to use internet, or use the pc to send internet to the cell phone i can't enable the OEM in the developer's option.
PU Kirito LP said:
Says bootloader is locked.
And baseband is missing
------------------
check 'allow oem unlock' in android settings developer (bootloader) options.
is sending I enable, plus the internet does not pay for lack of the modem.
even if i use bluetooth to use internet, or use the pc to send internet to the cell phone i can't enable the OEM in the developer's option.
Click to expand...
Click to collapse
Did you lock the bootloader or did it seem to lock it's self?
Sent from my ocean using XDA Labs
sd_shadow said:
Did you lock the bootloader or did it seem to lock it's self?
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
-----------------
in this case I formatted the cell phone and the oem option was disabled. and now I can’t flash the roms anymore.
PU Kirito LP said:
-----------------
in this case I formatted the cell phone and the oem option was disabled. and now I can’t flash the roms anymore.
Click to expand...
Click to collapse
I think the only fix is boot into edl mode
Code:
fastboot oem blankflash
Then flash a blankflash
Sent from my ocean using XDA Labs
sd_shadow said:
I think the only fix is boot into edl mode
Code:
fastboot oem blankflash
Then flash a blankflash
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
------------------
But how do I do this? boot into edl mode
I never hear about that command just do I apply?
Code:
fastboot oem blankflash
PU Kirito LP said:
But how do I do this? boot into edl mode
I never hear about that command just do I apply?
Click to expand...
Click to collapse
See my blankflash post in
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my ocean using XDA Labs
sd_shadow said:
See my blankflash post in
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
------------------
I will try to run tests later.
sd_shadow said:
See my blankflash post in
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
------------------
None of the things on that page worked. I'm still in the same problem.
PU Kirito LP said:
------------------
None of the things on that page worked. I'm still in the same problem.
Click to expand...
Click to collapse
What things?
Sent from my ocean using XDA Labs
sd_shadow said:
See my blankflash post in
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
------------------
I tried everything that was here on this link but I was not successful.
I'm trying to activate the 'Unlock OEM from the developer option' by ADB Shell, since the wi-fi and the operator chip won't catch on.
But I haven't had much success yet, I just found some commands to enter developer mode via adb shell. But I found nothing on how to activate the Unlock OEM via ADB Shell.
PU Kirito LP said:
------------------
I tried everything that was here on this link but I was not successful.
I'm trying to activate the 'Unlock OEM from the developer option' by ADB Shell, since the wi-fi and the operator chip won't catch on.
But I haven't had much success yet, I just found some commands to enter developer mode via adb shell. But I found nothing on how to activate the Unlock OEM via ADB Shell.
Click to expand...
Click to collapse
Fastboot oem blankflash failed?
Sent from my ocean using XDA Labs
sd_shadow said:
Fastboot oem blankflash failed?
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
------------------
Yes, it failed.
PU Kirito LP said:
------------------
Yes, it failed.
Click to expand...
Click to collapse
Dod you try to boot twrp?
Sent from my ocean using XDA Labs
sd_shadow said:
Dod you try to boot twrp?
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
------------------
I can go to Recovery mode, but I can't send TWRP to my cell phone.
i have been in exactly the same problem since last year,
Eu to com o mesmo problema desde o ano passado, e até hoje nao achei uma solução pro Flashing_locked
Coxinha2139 said:
i have been in exactly the same problem since last year,
Eu to com o mesmo problema desde o ano passado, e até hoje nao achei uma solução pro Flashing_locked
Click to expand...
Click to collapse
[PT-BR]
Estou com o mesmo problema, levei na assistência e foi diagnosticado com problema na memoria eMMC
[EN-US]
I have the same problem. Sent to technical assistance, and I was told that it is a hardware problem on eMMC memory.
{
"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"
}