Hi guys,
So this is how my OEM Unlocking option looks like right now. It's greyed out, which I think is normal, since the bootloader is unlocked, indeed. BUT the toggle is set to OFF. Which is not good. It should be ON.
{
"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"
}
This is from another phone.
Funny enough, with PE 13 for example, that option is ON. But I wouldn't try locking the bootloader on that.
So...why is my option turned OFF? What makes it look like that? How can I turn it back ON?
@Raghu varma any idea on this?
arsradu said:
Hi guys,
So this is how my OEM Unlocking option looks like right now. It's greyed out, which I think is normal, since the bootloader is unlocked, indeed. BUT the toggle is set to OFF. Which is not good. It should be ON.
View attachment 5733465
This is from another phone.
View attachment 5733467
Funny enough, with PE 13 for example, that option is ON. But I wouldn't try locking the bootloader on that.
So...why is my option turned OFF? What makes it look like that? How can I turn it back ON?
@Raghu varma any idea on this?
Click to expand...
Click to collapse
Doesn't really hamper anything. Just have fun with gimmics towards bootloader status. Ultimately the real status about bootloader lock or unlock can be checked from fastboot command "fastboot getvar all"
Once your bootloader is unlocked, then don't bother about all these. Ultimately the bootloader status from custom roms settings are just dummy
Raghu varma said:
Doesn't really hamper anything. Just have fun with gimmics towards bootloader status. Ultimately the real status about bootloader lock or unlock can be checked from fastboot command "fastboot getvar all"
Once your bootloader is unlocked, then don't bother about all these. Ultimately the bootloader status from custom roms settings are just dummy
Click to expand...
Click to collapse
I see... Ok, but if I want to go back to stock ROM and lock the bootloader (because contactless payments don't work anymore with bootloader unlocked), what would be the best way to do so?
Cause I tried flashing back stock (with LMSA), and...the ON/OFF toggle is set to OFF (so bootloader is not unlockable anymore).
Which means that, if I try to lock the bootloader now, and something goes wrong, I won't be able to fix it. Cause the option is OFF (so fastboot will complain about that when you try to flash anything), and...if you can't boot (like in the case of "no valid operating system could be found" error, that seems to be plaguing some of the Motorola devices)...well, you've got yourself a brick. And I don't want that.
So...if you were to go back to stock and lock the bootloader back, what would be the recommended procedure?
By the way, this is my getvar output (removed serials and IMEI and all that, since they're not important).
Code:
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader[0]: MBM-3.0-hanoip_retail-182ec3123a1-22
(bootloader) version-bootloader[1]: 0830
(bootloader) product: hanoip
(bootloader) board: hanoip
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EUAPEM
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB SKhynix H9HQ15AECMBDAR FV=A002 WB=0
(bootloader) ram: 6GB SKHYNIX LP4x DIE=16Gb M5-M8=06 06 00 11
(bootloader) cpu: SM7150 1.0
(bootloader) serialno: [removed]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 21006A06
(bootloader) token: inactive
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: [removed]
(bootloader) imei2: [removed]
(bootloader) meid:
(bootloader) date: 09-20-2021
(bootloader) sku: XT2135-2
(bootloader) carrier_sku: XT2135-2
(bootloader) battid: SB18D01687
(bootloader) battery-voltage: 4299
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: reteu
(bootloader) ro.build.fingerprint[0]: motorola/hanoip_retailenq/hanoip:1
(bootloader) ro.build.fingerprint[1]: 2/S2RIS32.32-20-7-4/41d937-0279a:u
(bootloader) ro.build.fingerprint[2]: ser/release-keys
(bootloader) ro.build.version.qcom[0]: LA.UM.9.1.r1-11500.02-SMxxx0.QSSI
(bootloader) ro.build.version.qcom[1]: 12.0
(bootloader) version-baseband[0]: M7150_25.333.01.82R HANOIP_EUAPEMDSDS_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 4.14.190-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 Tue A
(bootloader) kernel.version[4]: ug 30 06:55:43 CDT 2022
(bootloader) git:xbl: MBM-3.0-hanoip_retail-a4efaacd8-220830
(bootloader) git:xbl_config: MBM-3.0-hanoip_retail-a4efaacd8-220830
(bootloader) git:aop: MBM-3.0-hanoip_retail-2af95bb-220830
(bootloader) git:tz: MBM-3.0-hanoip_retail-845be54dd-220830
(bootloader) git:hyp: MBM-3.0-hanoip_retail-845be54dd-220830
(bootloader) git:devcfg: MBM-3.0-hanoip_retail-845be54dd-220830
(bootloader) git:cmnlib: MBM-3.0-hanoip_retail-845be54dd-220830
(bootloader) git:keymaster: MBM-3.0-hanoip_retail-49ec050-220830
(bootloader) git:storsec: MBM-3.0-hanoip_retail-845be54dd-220830
(bootloader) git:prov: MBM-3.0-hanoip_retail-845be54dd-220830
(bootloader) git:abl: MBM-3.0-hanoip_retail-182ec3123a1-220830
(bootloader) git:qupfw: MBM-3.0-hanoip_retail-fb017b4-220830
(bootloader) git:uefisecapp: MBM-3.0-hanoip_retail-845be54dd-220830
(bootloader) frp-state: protected (77)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(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
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D03127
(bootloader) primary-display: tm_ili7807s_fhd_vid
(bootloader) secondary-display:
(bootloader) fdr-allowed: yes
all: listed above
Finished. Total time: 0.049s
Does anything from that strike you as potentially not ok...? Or something from this output that could explain why that option is OFF?
Ok, so looks like you CAN lock the bootloader, even if that option is greyed out and turned OFF.
Tested it earlier, it worked fine.
The only thing I did (aside from flashing the ROM with LMSA), was that, before I booted the ROM after locking the bootloader, I booted into Recovery and did a Factory Reset. Then I booted the OS.
So, steps to follow for anyone wanting to attempt this:
restore the ROM with LMSA
make sure it boots!
reboot into bootloader
lock the bootloader with command "fastboot oem lock"
without rebooting, go into Recovery
do a Wipe Data/Factory Reset
select Reboot System (from Recovery)
Now everything is back to stock, the option is now active (not greyed out anymore) and the switch is in its default position (turned OFF).
I have moto g40 fusion 6gb/128gb and am currently am on android 12 and want to downgrade to android 11. I have unlocked the bootloader and it's saying the same that 'bootloader is already unlocked' and the option is grayed out. What is the correct procedure?
Also when you unlock bootloader and flash stock rom does the bootloader get automatically locked or you have to seperately lock it?
Thanks in advance.
Ishaan123 said:
I have moto g40 fusion 6gb/128gb and am currently am on android 12 and want to downgrade to android 11. I have unlocked the bootloader and it's saying the same that 'bootloader is already unlocked' and the option is grayed out. What is the correct procedure?
Also when you unlock bootloader and flash stock rom does the bootloader get automatically locked or you have to seperately lock it?
Thanks in advance.
Click to expand...
Click to collapse
Hello,
The recommended (also easier) procedure would be using the LMSA software, in Rescue mode to reflash your stock ROM.
Personally, I also did a factory reset from Recovery immediately after that, just to make sure the recovery is indeed the stock Recovery, and not TWRP or PE or other ROM's. Theoretically, if you're using LMSA, there shouldn't be any "dirt" left. But...I chose to do that, too. Personal choice. It's not mandatory.
However, make sure you can boot the device BEFORE you attempt to lock back the bootloader.
Command for locking the bootloader is:
fastboot oem lock (phone should be in fastboot mode for that, obviously)
As for your second question, yes, locking the bootloader is a separate step.
arsradu said:
Hello,
The recommended (also easier) procedure would be using the LMSA software, in Rescue mode to reflash your stock ROM.
Personally, I also did a factory reset from Recovery immediately after that, just to make sure the recovery is indeed the stock Recovery, and not TWRP or PE or other ROM's. Theoretically, if you're using LMSA, there shouldn't be any "dirt" left. But...I chose to do that, too. Personal choice. It's not mandatory.
However, make sure you can boot the device BEFORE you attempt to lock back the bootloader.
Command for locking the bootloader is:
fastboot oem lock (phone should be in fastboot mode for that, obviously)
As for your second question, yes, locking the bootloader is a separate step.
Click to expand...
Click to collapse
Thanks buddy for these answers on these bootloader lock steps and for others here about the Moto G60... So are the steps, risks, security about bootloader lock still the same? I'm going to block the bootloader again and I wanted to know if following your steps will still work or if there's anything new.
Thanks again!
Ewer_B said:
Thanks buddy for these answers on these bootloader lock steps and for others here about the Moto G60... So are the steps, risks, security about bootloader lock still the same? I'm going to block the bootloader again and I wanted to know if following your steps will still work or if there's anything new.
Thanks again!
Click to expand...
Click to collapse
Yes, everything's the same.
arsradu said:
Yes, everything's the same.
Click to expand...
Click to collapse
Thanks for the answer. I forgot to ask earlier, but can you do the process of unlocking and locking the bootloader multiple times? Or is there a limit or could there be a problem?
Ewer_B said:
Thanks for the answer. I forgot to ask earlier, but can you do the process of unlocking and locking the bootloader multiple times? Or is there a limit or could there be a problem?
Click to expand...
Click to collapse
I don't think there is a limit. And yes, I already did it multple times. No problem, as long as you're careful what you're doing, especially when locking the bootloader.
arsradu said:
I don't think there is a limit. And yes, I already did it multple times. No problem, as long as you're careful what you're doing, especially when locking the bootloader.
Click to expand...
Click to collapse
thank you very much friend for the answer!
Related
Hi all,
Sorry if this thread is in the wrong area.
I have in my possession a Nexus 5X which is stuck in a boot loop. I don't think it's a case of the power button being held down because the phone behaves differently depending on whether I hold the power button down or not.
I can boot into bootloader/fastboot mode which is locked. I have the standard options to Start/Restart bootloader/Recovery mode/Power off. If I try to get into recovery mode from here, the phone enters "download mode" for a short amount of time. After that, the bootloop begins again and I can only get the phone back to bootloader at best.
If I try to use the comment fastboot oem unlock I will get the message (remote: oem unlock is not allowed). I believe this is because don't have USB debugging/developer options enabled. I can't turn the phone on to enable this.
I have tried using Nexus Root Toolkit to unlock the bootloader (using the Flash Stock + Unroot and Soft-Bricked/Bootloop option) and everything seems to run fine until it restarts the phone. This triggers the boot loop again and the Nexus Root Toolkit hangs "waiting for phone..." after previously having been able to detect it.
I've tried using WinDroid Toolkit v3.1 also to unlock the bootloader without success.
Quite simply, is it possible to unlock the bootloader while the phone is in this state? I know this is a common problem with these phones but I'm not convinced this can't be fixed at home yet!
Thanks in advance for any help.
Some extra info:
fastboot getvar all
(bootloader) product: bullhead
(bootloader) off-mode-charge: 1
(bootloader) max-download-size: 0x20000000
(bootloader) battery-soc-ok: yes
(bootloader) battery-voltage: 4017mV
(bootloader) version-hardware: rev_1.0
(bootloader) version-baseband: M8994F-2.6.36.2.20
(bootloader) version-bootloader: BHZ11h
(bootloader) variant: bullhead LGH791 32GB
(bootloader) serialno: (hide)
(bootloader) kernel: lk
(bootloader) secure-boot: yes
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:bootloader: 0xa80000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:boot: 0x2000000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:recovery: 0x2000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0xc0000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x65a3fb800
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x6000000
(bootloader) partition-type:vendor: ext4
(bootloader) partition-size:vendor: 0xf800000
(bootloader) unlocked: no
Seems u are having problems with bootloader, have u tried flash stock bootloader image via fastboot and then proceed with OEM unlock?
imor said:
Seems u are having problems with bootloader, have u tried flash stock bootloader image via fastboot and then proceed with OEM unlock?
Click to expand...
Click to collapse
No, I haven't tried that. I'll give it a go later. Assumed I couldn't flash anything with a locked bootloader.
Cannot lock my bootloader, progress is stopped by "still need signed oem/system.img"
I want to lock my bootloader, I don't want to lose my Software status: Official flag in fastboot mode
when I run fastboot getvar all this appears( IMEI and SN changed for privacy reasons)
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.23
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG RE1BMB RV=08 PV=07 FV=000000000000000D
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8937
(bootloader) serialno: (changed for privacy)
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 3415337500000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: (changed for privacy)
(bootloader) meid:
(bootloader) date: 03-08-2017
(bootloader) sku: XT1676
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 3 3:14:55 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:7.0/NPPS25.
(bootloader) ro.build.fingerprint[1]: 137-72-4/4:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.246.4.cedric.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8937_11.16.02.51R CEDRIC_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g517c70f-0010
(bootloader) kernel.version[1]: 6-g2ab6438 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Fri Aug
(bootloader) kernel.version[3]: 4 04:33:06 CDT 2017
(bootloader) sbl1.git: git=MBM-NG-VB8.23-0-g2cafa24
(bootloader) rpm.git: git=3f612e6-dirty
(bootloader) tz.git: git=MBM-NG-VB8.21-0-g6c4172f-dirty
(bootloader) devcfg.git: git=MBM-NG-VB8.21-0-g6c4172f-dirty
(bootloader) keymaster.git: git=MBM-NG-VB8.21-0-g6c4172f-dirty
(bootloader) cmnlib.git: git=MBM-NG-VB8.21-0-g6c4172f-dirty
(bootloader) cmnlib64.git: git=MBM-NG-VB8.21-0-g6c4172f-dirty
(bootloader) prov.git: git=MBM-NG-VB8.09-0-g1a41aff
(bootloader) aboot.git: git=MBM-NG-VB8.23-0-g8fcce1f
(bootloader) qe: qe 0/1
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: reteu
all: listed above
and when I run
Code:
fastboot oem lock
I get
Code:
(bootloader) Still require signed system.img and/or oem.img
OKAY [ 0.014s]
finished. total time: 0.016s
Have you done
fastboot oem lock begin
flash stock firmware - all of it using fastboot commands
fastboot oem lock
You can't just do fastboot oem lock without doing the previous commands
Why do you want to lock the bootloader? There's no benefit unless you are selling the phone
Except that if I'm using stock with no root whatsoever, it's not worth having a message shaming you for unlocking your bootloader every time you boot or reboot
Also, I had issues beforehand doing the method you suggested, so that is why I'm not bothering with it
ap4ss3rby said:
Except that if I'm using stock with no root whatsoever, it's not worth having a message shaming you for unlocking your bootloader every time you boot or reboot
Also, I had issues beforehand doing the method you suggested, so that is why I'm not bothering with it
Click to expand...
Click to collapse
You can get rid of that message easily
Flash this in twrp recovery
https://drive.google.com/file/d/0B4BcNVrbrBOzZko3VjhmRWtrVms/view
TheFixItMan said:
You can get rid of that message easily
Flash this in twrp recovery
https://drive.google.com/file/d/0B4BcNVrbrBOzZko3VjhmRWtrVms/view
Click to expand...
Click to collapse
Not what I intend, also NO TWRP (Software Status: official in fastboot)
ap4ss3rby said:
Not what I intend, also NO TWRP (Software Status: official in fastboot)
Click to expand...
Click to collapse
My software status is official & I have twrp
Just flash twrp
Flash the zip file given to remove unlocked bootloader warning
Flash stock recovery if you don't want twrp
TheFixItMan said:
My software status is official & I have twrp
Just flash twrp
Flash the zip file given to remove unlocked bootloader warning
Flash stock recovery if you don't want twrp
Click to expand...
Click to collapse
Oh, will download, or just extract logo.bin from the zip, and flash it using fastboot commands
ap4ss3rby said:
Oh, will download, or just extract logo.bin from the zip, and flash it using fastboot commands
Click to expand...
Click to collapse
yes you can do that
TheFixItMan said:
yes you can do that
Click to expand...
Click to collapse
Thanks, flashed your logo.bin via fastboot and bootloader warning was gone. Though it reads "bad key" displayed on top of the stock Motorola logo.
A way to get rid of that too to have clean stock look?
No_Signal said:
Thanks, flashed your logo.bin via fastboot and bootloader warning was gone. Though it reads "bad key" displayed on top of the stock Motorola logo.
A way to get rid of that too to have clean stock look?
Click to expand...
Click to collapse
See
https://forum.xda-developers.com/g5/themes/motorola-boot-logo-n-removed-t3663735/post74065607
Please browse the Moto G5 threads - much quicker looking yourself & you can see what else is available
TheFixItMan said:
See
https://forum.xda-developers.com/g5/themes/motorola-boot-logo-n-removed-t3663735/post74065607
Please browse the Moto G5 threads - much quicker looking yourself & you can see what else is available
Click to expand...
Click to collapse
Those threads are known to me as those came up after after I did a look up myself.
No_Signal said:
A way to get rid of that too to have clean stock look?
Click to expand...
Click to collapse
That's why I explicit asked for "clean stock look", no fancy boot logo but original one without the "bad key" showing up.
"bad key" showing up ain't a problem of the boot graphics afaik. I didn't got it fixed myself though correct firmware/cedric image was flashed.
My phone does not enter in recovery mode nor can I restore it from the factory, since it does not enter into recovery mode it only stays in fastboot, the last commands that it used were: adb kill-server and then fastboot -w, that's when the problem started, any solution? Thank you.
:good:
omnismart said:
:good:
Click to expand...
Click to collapse
does not enter into recovery mode, when I select recovery, it returns to fasboot mode
luiguy said:
does not enter into recovery mode, when I select recovery, it returns to fasboot mode
Click to expand...
Click to collapse
can you flash any recovery image and see if it enters the recovery after that?
It's possible that the is no recovery image in the recovery partition to boot hence it is taking back to the bootloader.
Sent from my [device_name] using XDA-Developers Legacy app
shibaa987 said:
can you flash any recovery image and see if it enters the recovery after that?
It's possible that the is no recovery image in the recovery partition to boot hence it is taking back to the bootloader.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
can be done by having the boot loader blocked?
luiguy said:
can be done by having the boot loader blocked?
Click to expand...
Click to collapse
you mean to say that you have a locked bootloader?
Sent from my [device_name] using XDA-Developers Legacy app
shibaa987 said:
you mean to say that you have a locked bootloader?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
that's right, and I'm in the stock ROM, the bootloader has never been unlocked
You keep posting the same question all over the place, but you're not helping anyone to help you. I've asked a couple times to see your flashfile, but it has never been posted. Maybe there is something wrong with it. We really need to try and flash the bootloader, that will tell us what we're up against. If you can flash the bootloader, then you can flash back to stock and get out of this mess, but if you get a permission denied and you're using an official signed, then that's another problem.
You said you've tried, but no you haven't. You've tried to use your flashfile and nothing happened, hence the reason I keep asking to see it. Your main goal right now, and I've said this before, is to determine whether you can flash or not. A locked bootloader will only accept official signed firmware from the same carrier with the same revision or higher. So pretty please, don't post the same question anymore but do post your flashfile so we can see if there is anything wrong with it. Better yet, if anyone has a working flashfile for the lastest -05 variant please post it so we can rule it out. In the meantime run this command in fastboot and post the output, but be sure that you don't post your imei info. Not trying to be a ****, but posting the same question all over the forum does nothing to help and will get you banned.
Code:
fastboot getvar all
Post the output of this command minus your imei info.
Code:
fastboot getvar all
Post the output of this command minus your imei info.[/QUOTE]
all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-b48569f-170628
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: no
(bootloader) hwrev: PVT
(bootloader) radio: ROW
(bootloader) storage-type: UFS
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: NGRL470061
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 86027E05
(bootloader) securestate: engineering
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 05-29-2017
(bootloader) sku: XT1789-05
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4172
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_amx/nash:7.1.1/NPX26
(bootloader) ro.build.fingerprint[1]: .122-49/53:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.26.11.53.nash_amx.am
(bootloader) ro.build.version.full[1]: x.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.7.r1-09300-8x98.0
(bootloader) version-baseband: M8998_24.71.01.87R NRS
(bootloader) kernel.version[0]: Linux version 4.4.21-perf-gb6ca254 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 2015012
(bootloader) kernel.version[2]: 3 (prerelease) (GCC) ) #1 SMP PREEMPT We
(bootloader) kernel.version[3]: d Jun 28 08:50:20 CDT 2017
(bootloader) abl.git: MBM-3.0-nash_retail-b48569f-170628
(bootloader) xbl.git: MBM-3.0-nash_retail-dea2712-170628
(bootloader) pmic.git: MBM-3.0-nash_retail-dea2712-170628
(bootloader) rpm.git: MBM-3.0-nash_retail-d3e45a4-170628
(bootloader) tz.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) hyp.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) devcfg.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) cmnlib.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) cmnlib64.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) keymaster.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) storsec.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) prov.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: openmx
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(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: 7.146s
41rw4lk said:
You keep posting the same question all over the place, but you're not helping anyone to help you. I've asked a couple times to see your flashfile, but it has never been posted. Maybe there is something wrong with it. We really need to try and flash the bootloader, that will tell us what we're up against. If you can flash the bootloader, then you can flash back to stock and get out of this mess, but if you get a permission denied and you're using an official signed, then that's another problem.
You said you've tried, but no you haven't. You've tried to use your flashfile and nothing happened, hence the reason I keep asking to see it. Your main goal right now, and I've said this before, is to determine whether you can flash or not. A locked bootloader will only accept official signed firmware from the same carrier with the same revision or higher. So pretty please, don't post the same question anymore but do post your flashfile so we can see if there is anything wrong with it. Better yet, if anyone has a working flashfile for the lastest -05 variant please post it so we can rule it out. In the meantime run this command in fastboot and post the output, but be sure that you don't post your imei info. Not trying to be a ****, but posting the same question all over the forum does nothing to help and will get you banned.
Code:
fastboot getvar all
Post the output of this command minus your imei info.
Click to expand...
Click to collapse
there are the data that you asked me
What were you trying to do when all your trouble initially began? I see that you still have nougat on that slot and the bootloader secure state is engineering, that's not right. Can you still boot into your system? If so make sure adb is enabled. I assume oem unlock is greyed out and unavailable right? What firmware have you tried to flash? Also, if you're able to boot into your system you should disable fingerprint/lockscreen security until you have everything resolved.
41rw4lk said:
What were you trying to do when all your trouble initially began? I see that you still have nougat on that slot and the bootloader secure state is engineering, that's not right. Can you still boot into your system? If so make sure adb is enabled. I assume oem unlock is greyed out and unavailable right? What firmware have you tried to flash? Also, if you're able to boot into your system you should disable fingerprint/lockscreen security until you have everything resolved.
Click to expand...
Click to collapse
I just tried to update it to Android 8, if I can enter the system and I have USB debugging enabled, EOM is in gray, the ROM I wanted to install was: https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/ . Android 8
luiguy said:
I just tried to update it to Android 8, if I can enter the system and I have USB debugging enabled, EOM is in gray, the ROM I wanted to install was: https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/ . Android 8
Click to expand...
Click to collapse
In fastboot mode switch slots and run the getvar command again. Post the results and see if the other slot boots. If not switch back. You're currently on _a
Code:
fastboot devices
fastboot --set-active=b
fastboot getvar all
fasboot reboot
Post the results of the getvar command. If the phone boots to system on slot _b check out your settings, see if oem unlock is available and make sure adb debugging is on. If it doesn't boot, it should automatically fall back to slot _a but if it doesn't just run the commands above again only set active to a. You don't need to run the getvar command again once you're back to _a. *Note when you run the getvar command the 'current-slot' entry tells you what slot you're on.
41rw4lk said:
In fastboot mode switch slots and run the getvar command again. Post the results and see if the other slot boots. If not switch back. You're currently on _a
Code:
fastboot devices
fastboot --set-active=b
fastboot getvar all
fasboot reboot
Post the results of the getvar command. If the phone boots to system on slot _b check out your settings, see if oem unlock is available and make sure adb debugging is on. If it doesn't boot, it should automatically fall back to slot _a but if it doesn't just run the commands above again only set active to a. You don't need to run the getvar command again once you're back to _a. *Note when you run the getvar command the 'current-slot' entry tells you what slot you're on.
Click to expand...
Click to collapse
C:\Users\luiguymm\Desktop\adb - fastboot MOTO Z2 PLAY Z2 FORCE>fastboot --set-
active = b
fastboot: unrecognised option `--set-active'
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-b48569f-17062
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: no
(bootloader) hwrev: PVT
(bootloader) radio: ROW
(bootloader) storage-type: UFS
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: NGRL470061
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 86027E05
(bootloader) securestate: engineering
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 05-29-2017
(bootloader) sku: XT1789-05
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4301
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_amx/nash:7.1.1
(bootloader) ro.build.fingerprint[1]: .122-49/53:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.26.11.53.nash_
(bootloader) ro.build.version.full[1]: x.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.7.r1-09300-8x98.0
(bootloader) version-baseband: M8998_24.71.01.87R NRS
(bootloader) kernel.version[0]: Linux version 4.4.21-perf-gb6ca254
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 2
(bootloader) kernel.version[2]: 3 (prerelease) (GCC) ) #1 SMP PREE
(bootloader) kernel.version[3]: d Jun 28 08:50:20 CDT 2017
(bootloader) abl.git: MBM-3.0-nash_retail-b48569f-170628
(bootloader) xbl.git: MBM-3.0-nash_retail-dea2712-170628
(bootloader) pmic.git: MBM-3.0-nash_retail-dea2712-170628
(bootloader) rpm.git: MBM-3.0-nash_retail-d3e45a4-170628
(bootloader) tz.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) hyp.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) devcfg.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) cmnlib.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) cmnlib64.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) keymaster.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) storsec.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) prov.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: openmx
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(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: 7.193s
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(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: 7.193s
You're still on slot a, you need to be on slot b
After you run the command set-active, reboot the bootloader then do a getvar. Also, see if it will boot.
Code:
fastboot --set-active=b
fastboot reboot bootloader
fastboot getvar all
fastboot reboot
41rw4lk said:
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(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: 7.193s
You're still on slot a, you need to be on slot b
After you run the command set-active, reboot the bootloader then do a getvar. Also, see if it will boot.
Code:
fastboot --set-active=b
fastboot reboot bootloader
fastboot getvar all
fastboot reboot
Click to expand...
Click to collapse
C:\Users\luiguymm\Desktop\adb - fastboot MOTO Z2 PLAY Z2 FORCE>fastboot --set-
active = b
fastboot: unrecognised option `--set-active'
luiguy said:
C:\Users\luiguymm\Desktop\adb - fastboot MOTO Z2 PLAY Z2 FORCE>fastboot --set-
active = b
fastboot: unrecognised option `--set-active'
Click to expand...
Click to collapse
Either your fastboot file is out of date, or that engineering state is limiting your accessibility. Close any command prompt windows. Download this utilities zip, it has known good adb and fastboot files in it. Extract it to a folder somewhere, open the folder, hold shift and right click a blank area inside the folder, then choose open a command window here. Verify that your device is connected in fastboot 'fastboot devices', then try setting the active slot again and proceed from there.
*Note - Make sure you're using a 2.0 usb port off the motherboard, not a hub from the front of the pc and such. Most people don't have problems with this, but it has caused problems for some. Not all usb ports are so universal, ports on the mobo tend to have more consistent power supply and transfer rates; less interference as well.
41rw4lk said:
Either your fastboot file is out of date, or that engineering state is limiting your accessibility. Close any command prompt windows. Download this utilities zip, it has known good adb and fastboot files in it. Extract it to a folder somewhere, open the folder, hold shift and right click a blank area inside the folder, then choose open a command window here. Verify that your device is connected in fastboot 'fastboot devices', then try setting the active slot again and proceed from there.
*Note - Make sure you're using a 2.0 usb port off the motherboard, not a hub from the front of the pc and such. Most people don't have problems with this, but it has caused problems for some. Not all usb ports are so universal, ports on the mobo tend to have more consistent power supply and transfer rates; less interference as well.
Click to expand...
Click to collapse
C:\Users\luiguymm\Downloads\FlashAllUtils>fastboot devices
NGRL470061 fastboot
C:\Users\luiguymm\Downloads\FlashAllUtils>fastboot --set-active = b
(bootloader) slot-suffi: not found
(bootloader) current-slots: not found
fastboot: usage: unknown command =
C:\Users\luiguymm\Downloads\FlashAllUtils>
luiguy said:
C:\Users\luiguymm\Downloads\FlashAllUtils>fastboot devices
NGRL470061 fastboot
C:\Users\luiguymm\Downloads\FlashAllUtils>fastboot --set-active = b
(bootloader) slot-suffi: not found
(bootloader) current-slots: not found
fastboot: usage: unknown command =
C:\Users\luiguymm\Downloads\FlashAllUtils>
Click to expand...
Click to collapse
It has to be your phone that limiting your commands. I ran the same commands right out of the utilities zip and had no troubles. I think since you can't really do anything else, and you can't flash back to stock normally you might need to blank flash to get the gist of things back in order. First though, I would open your flashall file and paste the lines one by one in the command prompt and see if you could manually flash your phone. As it stands now, whenever you try to run the .bat file it just does nothing. Skip the fb_mode set and the getvar and start with the actual flashing. It will either flash or you'll get a permission denied most likely.
If you can't manually flash the oreo firmware, then you'll most likely need to blank flash. Several people have had their phone go wonky after trying to upgrade from nougat. So much for seamless updates.
luiguy said:
C:\Users\luiguymm\Downloads\FlashAllUtils>fastboot devices
NGRL470061 fastboot
C:\Users\luiguymm\Downloads\FlashAllUtils>fastboot --set-active = b
(bootloader) slot-suffi: not found
(bootloader) current-slots: not found
fastboot: usage: unknown command =
C:\Users\luiguymm\Downloads\FlashAllUtils>
Click to expand...
Click to collapse
Just noticed, you're entering the command wrong. The only space in this command is between the 't' and the '-' fastboot --set-active=b
You need to check out the _b slot, see what is on it and whether it will boot or not. If it does boot, check the settings and take note of everything. If it doesn't boot then we'll go from there. Just copy the fastboot command as I typed it.
Help me find compatible firmware to flash on fastboot my Moto G5 EU version 2/16GB
I try flash random clean stock 8.1 fw. But i have errorcant start system or enter recovery.
I cant start phone
Info from my phone is
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SKHYNIX HAG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: XXXX
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 625716AC00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: XXXXXX
(bootloader) meid:
(bootloader) date: 06-13-2017
(bootloader) sku: XT1676
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 0: 0:40 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPPS2
(bootloader) ro.build.fingerprint[1]: 8.85-13-6/04442:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.7.cedric.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband[0]: M8937_22.29.02.69.01R CEDRIC_EMEADSDS_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g6fc7aba (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Thu Feb 7 01:47:04 CST
(bootloader) kernel.version[3]: 2019
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=4942431
(bootloader) devcfg.git: git=4942431
(bootloader) keymaster.git: git=4942431
(bootloader) cmnlib.git: git=4942431
(bootloader) cmnlib64.git: git=4942431
(bootloader) prov.git: git=4942431
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: reteu
(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
finished. total time: 0.702s
C:\Program Files\Minimal ADB and Fastboot>
Any help will be apperciate. I really need this phone back to work. I want only flash clean stock 8.1.0 rom.
When i buyed this phone. But now i have semi brick.
Anyone here can help me?
Problem solved. I found newest 8.1.0 stock rom. I flashed and phone back to life.
Last problem what i have is i cant unlock bootloader.
Morricorne said:
Problem solved. I found newest 8.1.0 stock rom. I flashed and phone back to life.
Last problem what i have is i cant unlock bootloader.
Click to expand...
Click to collapse
Follow the process for unlocking on
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Make sure usb debugging and oem unlock (if available) is enabled
Make sure the unlock string is correct and you have removed all spaces so its on one long single line as per instructions
TheFixItMan said:
Follow the process for unlocking on
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Make sure usb debugging and oem unlock (if available) is enabled
Make sure the unlock string is correct and you have removed all spaces so its on one long single line as per instructions
Click to expand...
Click to collapse
This device is supported. But i have message This device isnt allowed to unlock bootloader. On Motorola site.
I follow every step on This guide
Still the same.
XT1676 EU 2/16 GB version here.
Stock Android 8.1.0 OPP28.85-19-4-2
This suck, cause i want try 64 os but os on This device. But cant
Morricorne said:
This device is supported. But i have message This device isnt allowed to unlock bootloader. On Motorola site.
I follow every step on This guide
Still the same.
XT1676 EU 2/16 GB version here.
Stock Android 8.1.0 OPP28.85-19-4-2
This suck, cause i want try 64 os but os on This device. But cant
Click to expand...
Click to collapse
Either the device is an amazon device or locked to a carrier which doesn't allow bootloader unlocking until the device is carrier unlocked (officially) or it has been previously unlocked in which case you would need to know the unlock code to unlock it again
If it has been registered before with Motorola you need to sign in using that email or try and unlink that address from the device (motorola device id option under settings)
https://imgur.com/cDPKjin
https://imgur.com/hblRtIU
Still no luck
TheFixItMan said:
Either the device is an amazon device or locked to a carrier which doesn't allow bootloader unlocking until the device is carrier unlocked (officially) or it has been previously unlocked in which case you would need to know the unlock code to unlock it again
If it has been registered before with Motorola you need to sign in using that email or try and unlink that address from the device (motorola device id option under settings)
Click to expand...
Click to collapse
I Just give up for good. I try many times, and cant unlock bootloader. I spend almost 5 hour today to figure out how ressurect this phone from dead. Its working and Its enough. Adreno 505/506 is to weak to emulate Dolphin And Citra emulator.
Time to buy something with new snapdragon cpu.
I buyed this moto from second hand for 10 euro today. Little cracked screen. But works. Its enough for me. Anyway thanks for all help i really apperciate it.
Morricorne said:
I Just give up for good. I try many times, and cant unlock bootloader. I spend almost 5 hour today to figure out how ressurect this phone from dead. Its working and Its enough. Adreno 505/506 is to weak to emulate Dolphin And Citra emulator.
Time to buy something with new snapdragon cpu.
I buyed this moto from second hand for 10 euro today. Little cracked screen. But works. Its enough for me. Anyway thanks for all help i really apperciate it.
Click to expand...
Click to collapse
Can you copy and paste the bootloader output of fastboot oem get_unlock_data (unedited) and I'll try and unlock it - I can't be bothered to manually type it in
If it gives the same for me then it can't be unlocked
Last question about bootloader and this device.
Root is needed to unlock bootloader on moto G5?
Maybe this is a problem. I dont have root access.
Morricorne said:
Last question about bootloader and this device.
Root is needed to unlock bootloader on moto G5?
Maybe this is a problem. I dont have root access.
Click to expand...
Click to collapse
You need to have an unlocked bootloader
Flash twrp
Flash magisk in twrp
I unlocked bootloader, flash twrp 64 bit. I now check lineageos 17 64 bit.
But battery life suck.
Time to find Best 64 bit rom.
Anyway thanks for help
Hello Guys,
I have Moto G60. I have unlocked boot loader and downgrade with Stock Android 11 and Locked boot loader again.
After flashing locked, when I started my phone, it shows me error "No Valid Operating System could be Found. The device will not boot."
I have tried Lenovo RSA tool to rescue my phone but it gets failed, same in RSD Lite.
Now, I am trying to unlock boot loader again using ADB tools and it gives me error that "Check 'OEM unlocking' in Android Settings > Developer"
Can anyone help me?
Thanks in advance.
Milan
milan.vyas7 said:
Hello Guys,
I have Moto G60. I have unlocked boot loader and downgrade with Stock Android 11 and Locked boot loader again.
After flashing locked, when I started my phone, it shows me error "No Valid Operating System could be Found. The device will not boot."
I have tried Lenovo RSA tool to rescue my phone but it gets failed, same in RSD Lite.
Now, I am trying to unlock boot loader again using ADB tools and it gives me error that "Check 'OEM unlocking' in Android Settings > Developer"
Can anyone help me?
Thanks in advance.
Milan
Click to expand...
Click to collapse
Did you boot the phone to make sure everything's ok before locking the bootloader?
I see a lot of people with this issue. Locking the bootloader should be the absolute last step you do. After you make sure everything works fine.
The problem is you don't have USB debugging on anymore, so no adb. Bootloader is locked, and you've got no access to the OS, so you can't either enable or disable OEM unlocking.
I'll look around to see if there's any way to fix this at home. But I'm afraid the only way might be to bring the phone to a repair center.
arsradu said:
Did you boot the phone to make sure everything's ok before locking the bootloader?
I see a lot of people with this issue. Locking the bootloader should be the absolute last step you do. After you make sure everything works fine.
The problem is you don't have USB debugging on anymore, so no adb. Bootloader is locked, and you've got no access to the OS, so you can't either enable or disable OEM unlocking.
I'll look around to see if there's any way to fix this at home. But I'm afraid the only way might be to bring the phone to a repair center.
Click to expand...
Click to collapse
Yes, when I have unlocked bootloader and downgrade from Android 12 to Android 11 and every thing was working perfectly.
To, install banking apps on my mobile, I thought it will be good to relock the bootloader.
Once I locked the bootloader and reboot my phone, I get this error.
I have also bring my phone to mobile shops to get it repaired but no luck.
milan.vyas7 said:
Yes, when I have unlocked bootloader and downgrade from Android 12 to Android 11 and every thing was working perfectly.
To, install banking apps on my mobile, I thought it will be good to relock the bootloader.
Once I locked the bootloader and reboot my phone, I get this error.
I have also bring my phone to mobile shops to get it repaired but no luck.
Click to expand...
Click to collapse
For banking apps to work, you only need the device to be non-rooted. Bootloader status doesn't matter, for as far as I know. But I guess it depends on the app.
Anyway, I'm guessing OEM unlocking was not checked before you locked the bootloader, right? Otherwise it shouldn't have complained about it when you tried to unlock again.
Weird thing. I don't know where you got the bootloader unlocking procedure, but on the official Motorola site that I used to unlock the bootloader, it said to use:
fastboot oem unlock [UNLOCK_CODE]
But Google's documentation mentioned something about newer devices using "fastboot flashing" command. Kinda confusing...
They're probably the same. But I never used this command. Also, when you try to unlock using "fastboot flashing" don't you also need to provide the unlock code...?
I don't know man... I don't know what to say. I was thinking of going back to stock Android 12 just to test this theory, but now I'm not so sure. )
I have unlocked and locked bootloader before, on other Motorola phones. Successfully of course. ) So...I'm not sure why so many people keep getting into this issue.
By the way, what is the exact error you get with RSA when trying to restore your device? That should have worked...even with a locked bootloader. After all, it asumes the bootloader is locked. Can you boot into fastboot mode? Is the device recognised in fastboot mode?
I remember I had a failure with RSA one time, but just restarting the process made it go away, and flashing finished successfully.
Anyway, to check fastboot status, while in fastboot mode, do the following command:
fastboot devices
It should display your device underneath. After that, you can go restore your device with RSA.
arsradu said:
For banking apps to work, you only need the device to be non-rooted. Bootloader status doesn't matter, for as far as I know. But I guess it depends on the app.
Anyway, I'm guessing OEM unlocking was not checked before you locked the bootloader, right? Otherwise it shouldn't have complained about it when you tried to unlock again.
Weird thing. I don't know where you got the bootloader unlocking procedure, but on the official Motorola site that I used to unlock the bootloader, it said to use:
fastboot oem unlock [UNLOCK_CODE]
But Google's documentation mentioned something about newer devices using "fastboot flashing" command. Kinda confusing...
They're probably the same. But I never used this command. Also, when you try to unlock using "fastboot flashing" don't you also need to provide the unlock code...?
I don't know man... I don't know what to say. I was thinking of going back to stock Android 12 just to test this theory, but now I'm not so sure. )
I have unlocked and locked bootloader before, on other Motorola phones. Successfully of course. ) So...I'm not sure why so many people keep getting into this issue.
By the way, what is the exact error you get with RSA when trying to restore your device? That should have worked...even with a locked bootloader. After all, it asumes the bootloader is locked. Can you boot into fastboot mode? Is the device recognised in fastboot mode?
I remember I had a failure with RSA one time, but just restarting the process made it go away, and flashing finished successfully.
Anyway, to check fastboot status, while in fastboot mode, do the following command:
fastboot devices
It should display your device underneath. After that, you can go restore your device with RSA.
Click to expand...
Click to collapse
Hi,
Please find attached screenshot of error in RSA.
In fastboot mode its showing me device while running command: "fastboot devices"
Yeah, looks like there are a lot of Motorola users with this exact issue.
So, the problem here is that, when you flash the ROM with bootloader unlocked, OEM Unlocking is in the Off position, and greyed out. Showing "bootloader is already unlocked". So you can't change that.
Then you try to relock the bootloader, data gets erased, and you can't boot. No idea why it's showing "no valid operating system could be found". That's the first problem.
Also, when you try to unlock again, it complains about the OEM Unlocking switch not being ON, which...well, you couldn't turn on to begin with, cause it was inactive/greyed out, saying bootloader is already unlocked (which it was).
What's interesting is that, according to Google, that option should be persistent to factory resets. I guess it's persistent to user triggered factory resets, but not when bootloader is being locked and triggers the erase userdata on its own. Which I guess makes sense. But with the OS not booting, that option being likely unchecked...it's becoming a huge pain in the butt.
Some people said to wait 7 days and then try to reflash using RSA.
In the meantime, I've found an awesome guide here.
And some technical details from google here.
Also this about boot flow.
I've reverted to stock Android 12 myself, for the time being. But I did not lock the bootloader. For multiple reasons. This being only one of them. And I'm not planning to, until I find out more about this issue.
I'll let you know if I find anything more.
Update:
Ok, so apparently the switch being in the off position doesn't really have any effect on the software functionality after relocking the bootloader. You CAN relock the bootloader, even with the switch greyed out and in the OFF position. It should be ok, as long as you don't try to lock the bootloader on a custom ROM.
So, my advice would be using LMSA to flash the stock ROM, make sure it boots, lock the bootloader, and without rebooting the system, go into recovery and do a wipe data/factory reset. Then reboot to system.
It worked fine for me. Already did this operation twice. All good. Just make sure everything is clean (LMSA should take care of this).
You can boot into bootloader, right?
If so, can you try these commands?
fastboot getvar current-slot
Should return something like this:
current-slot: a
or
current-slot: b
If it says current-slot: a, try to switch to b slot with this command:
fastboot --set-active=b
If your current slot is b, try to change it to slot a with the following command:
fastboot --set-active=a
Then try to reboot.
If you're on Windows, do NOT use Minimal ADB and fastboot. Use this instead: https://developer.android.com/studio/releases/platform-tools
Let me know if you still encounter that issue.
Also, another question: did you flash a custom recovery? Cause you might have needed to flash back stock recovery (boot.img) before locking the bootloader.
What happened here I think is that you locked the bootloader. But slot a and slot b might have different recoveries.
For testing, I reverted to stock Android 11 on my Moto One Action. And I've noticed, on slot b, I had Pixel Experience recovery. So I flashed stock first.
Then booted from slot a, and the OEM Unlocking switch was still greyed out but on the ON position (bootloader allowed to be unlocked). Still with the same message "bootloader is already unlocked", but switch set to ON. Which is a big difference.
Then I locked the bootloader. And with fingers crossed, successfully booted into the OS.
And when I booted back, OEM Unlocking was no longer inactive. And it can be set to ON or OFF, just like in the beginning.
So, I think the goal here would be to get that switch greyed out and in the ON position. I think that's a good sign.
After that, locking the bootloader should work just fine.
In your case, I think it's trying to boot from an inactive slot. Or one that doesn't have an operating system linked to it. The error you get seems accurate for this case (no valid operating system found). So of course it cannot boot. So we just need to figure out why there's no valid operating system found.
But I'm waiting for more info, before reaching a conclusion. Anyway, I've learned a lot about these things in the past couple of days.
Also, another thing I've learned is that you can't have Google Pay (now called Wallet) and Tap to Pay working on stock ROM if your bootloader is unlocked. It's not gonna pass the CTS match test. So...in order to get that, either you're on a custom ROM, obviously with bootloader unlocked, or on a stock ROM, rooted, with Magisk and certain tricks to make it work. Which..,since you're on stock ROM, I'm guessing you don't want root. So...yeah.
Also, please, run this command from Fastboot mode:
Code:
fastboot getvar all
and post the output here.
You can remove IMEIs and other personal data. We don't need those.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-hanoip_retail-aea4f158e7-210611
(bootloader) product: hanoip
(bootloader) board: hanoip
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EUAPEM
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB SAMSUNG KM2V8001CM-B707 FV=1500 WB=0
(bootloader) ram: 6GB SAMSUNG LP4x DIE=16Gb M5-M8=01 07 01 12
(bootloader) cpu: SM7150 1.0
(bootloader) serialno: ZY22F4X32L
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 290C2617
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805306368
(bootloader) reason: Volume down key pressed
(bootloader) imei: 3
(bootloader) imei2: 3
(bootloader) meid:
(bootloader) date: 01-18-2022
(bootloader) sku: XT2135-2
(bootloader) carrier_sku: XT2135-2
(bootloader) battid: SB18D01687
(bootloader) battery-voltage: 4316
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: reteu
(bootloader) ro.build.fingerprint[0]: motorola/hanoip_retailenq/hanoip:1
(bootloader) ro.build.fingerprint[1]: 1/RRIS31.Q1-42-51-12-4/24f96:user/
(bootloader) ro.build.fingerprint[2]: release-keys
(bootloader) ro.build.version.qcom: LA.UM.9.1.r1-07700-SMxxx0.0
(bootloader) version-baseband[0]: M7150_09.297.01.75.01R HANOIP_EUAPEMDS
(bootloader) version-baseband[1]: DS_CUST
(bootloader) kernel.version[0]: Linux version 4.14.190-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 Mon M
(bootloader) kernel.version[4]: ay 2 07:50:18 CDT 2022
(bootloader) git:xbl: MBM-3.0-hanoip_retail-e90680732-210611
(bootloader) git:xbl_config: MBM-3.0-hanoip_retail-e90680732-210611
(bootloader) git:aop: MBM-3.0-hanoip_retail-4bfd5e5-210611
(bootloader) git:tz: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) git:hyp: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) git:devcfg: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) git:cmnlib: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) git:keymaster: MBM-3.0-hanoip_retail-bf902af-210611
(bootloader) git:storsec: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) gitrov: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) git:abl: MBM-3.0-hanoip_retail-aea4f158e7-210611
(bootloader) git:qupfw: MBM-3.0-hanoip_retail-6ac31cc-210611
(bootloader) git:uefisecapp: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) frp-state: protected (77)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(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: 7
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D03127
(bootloader) primary-display: tm_ili7807s_fhd_vid
(bootloader) secondary-display:
all: listed above
finished. total time: 0.178s
milan.vyas7 said:
Hello Guys,
I have Moto G60. I have unlocked boot loader and downgrade with Stock Android 11 and Locked boot loader again.
After flashing locked, when I started my phone, it shows me error "No Valid Operating System could be Found. The device will not boot."
I have tried Lenovo RSA tool to rescue my phone but it gets failed, same in RSD Lite.
Now, I am trying to unlock boot loader again using ADB tools and it gives me error that "Check 'OEM unlocking' in Android Settings > Developer"
Can anyone help me?
Thanks in advance.
Milan
Click to expand...
Click to collapse
Good morning, dear friend, I also had the same error and I regret to inform you that there is no resolution without using certain equipment at the moment, the only possible way to solve this problem at the moment would be through a JTAG BOX type MEDUSA PRO 2 or OCTOPLUS, I'll explain why, recently with the update to android 12, a security patch also came with it, with the same problem, it turns out that the boot structures that are with android 11, are not compatible with the 12 and it ends up that you can't go back, this error seems intentional, the only way to be solving it even because the bootloader is blocked would be you using a box to rewrite the system in the device's UFS memories directly through the JTAG which is the direct connection from the box with the motherboard of the device, another solution would be to send it to motorola itself, which according to them it is necessary to change the entire motherboard of the device and the concert costs around 181.71 Dollar, if you are lucky and find a technician in your city who operates with jtag, the concert costs around 40 Dollars, I'm Brazilian so for me, the plate replacement came with a budget of R$ 920.00 and the concert for JTAG R$ 200.00
A hug in advance and if you need to just call.
arsradu said:
Also, please, run this command from Fastboot mode:
Code:
fastboot getvar all
and post the output here.
You can remove IMEIs and other personal data. We don't need those.
Click to expand...
Click to collapse
Hello Arsradu,
I have gone through steps which you given me to run on platform tools and output is as below.
C:\platform-tools_r33.0.3-windows\platform-tools>fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.004s
C:\platform-tools_r33.0.3-windows\platform-tools>fastboot --set-active=b
Setting current slot to 'b' FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools_r33.0.3-windows\platform-tools>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-hanoip_retail-aea4f158e7-210611
(bootloader) product: hanoip
(bootloader) board: hanoip
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EUAPEM
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB MICRON MT128GASAO4U21 FV=0106 WB=0
(bootloader) ram: 6GB MICRON LP4 DIE=24Gb M5-M8=FF 05 00 14
(bootloader) cpu: SM7150 1.0
(bootloader) serialno: ********
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: E7F4957D
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) reason: Volume down key pressed
(bootloader) imei: ************
(bootloader) imei2: *******
(bootloader) meid:
(bootloader) date: 04-15-2021
(bootloader) sku: XT2135-2
(bootloader) carrier_sku: XT2135-2
(bootloader) battid: SB18C87844
(bootloader) battery-voltage: 3947
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retin
(bootloader) ro.build.fingerprint[0]: motorola/hanoip_retailnq/hanoip:11
(bootloader) ro.build.fingerprint[1]: /RRI31.Q1-42-42-3/149b5:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) ro.build.version.qcom: LA.UM.9.1.r1-07700-SMxxx0.0
(bootloader) version-baseband[0]: M7150_09.297.01.60R HANOIP_EUAPEMDSDS_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 4.14.190-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 J
(bootloader) kernel.version[4]: un 11 07:59:53 CDT 2021
(bootloader) git:xbl: MBM-3.0-hanoip_retail-e90680732-210611
(bootloader) git:xbl_config: MBM-3.0-hanoip_retail-e90680732-210611
(bootloader) git:aop: MBM-3.0-hanoip_retail-4bfd5e5-210611
(bootloader) git:tz: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) git:hyp: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) git:devcfg: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) git:cmnlib: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) git:keymaster: MBM-3.0-hanoip_retail-bf902af-210611
(bootloader) git:storsec: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) gitrov: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) git:abl: MBM-3.0-hanoip_retail-aea4f158e7-210611
(bootloader) git:qupfw: MBM-3.0-hanoip_retail-6ac31cc-210611
(bootloader) git:uefisecapp: MBM-3.0-hanoip_retail-994049848-210611
(bootloader) frp-state: no protection (0)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D03162
(bootloader) primary-display: tm_ili7807s_fhd_vid
(bootloader) secondary-display:
all: listed above
Finished. Total time: 0.269s
Hmm...according to this, you should be able to boot. Do you still see the same error? Can you boot into recovery and do a factory reset?
arsradu said:
Hmm...according to this, you should be able to boot. Do you still see the same error? Can you boot into recovery and do a factory reset?
Click to expand...
Click to collapse
When I boot into recovery mode, I got same error "No valid OS found. The device will not boot."
milan.vyas7 said:
When I boot into recovery mode, I got same error "No valid OS found. The device will not boot."
Click to expand...
Click to collapse
Hmmm that's interesting... You should have been able to boot into recovery from bootloader... Just use the arrow keys until you see recovery mode, then Power key to select. But if that doesn't work...then I don't know.
Can you boot a custom recovery and try the same thing?
To boot into twrp (without flashing it), you can do the following command:
fastboot boot /path-to-your-twrp.img
You can download it from here.
arsradu said:
Hmmm that's interesting... You should have been able to boot into recovery from bootloader... Just use the arrow keys until you see recovery mode, then Power key to select. But if that doesn't work...then I don't know.
Can you boot a custom recovery and try the same thing?
To boot into twrp (without flashing it), you can do the following command:
fastboot boot /path-to-your-twrp.img
You can download it from here.
Click to expand...
Click to collapse
Here is the output.
C:\platform-tools_r33.0.3-windows\platform-tools>fastboot boot twrp-3.6.2_12.1-0-hanoip-20220808-0701.img
Sending 'boot.img' (36600 KB) OKAY [ 0.792s]
Booting (bootloader) Fastboot boot command is not available in locked device
FAILED (remote: '')
fastboot: error: Command failed
Oh maaan... This sucks. Then I don't know...
arsradu said:
Oh maaan... Isso é uma merda. Então não sei...
Click to expand...
Click to collapse
Até agora não há como resolver esse problema sem usar jtag
Yeah, I'm not sure you can fix it without using the JTAG...
By the way, which Android version did you install before reaching this state?
arsradu said:
Yeah, I'm not sure you can fix it without using the JTAG...
By the way, which Android version did you install before reaching this state?
Click to expand...
Click to collapse
In this case he was on android 12 and tried to downgrade to 11, but in doing so he also blocked the bootloader and in that the system no longer allows to rewrite the rom