Hello, about a month ago my phone randomly shut off (full battery) and when I tried to turn it back on I was in a bootloop. I was able to boot into recovery mode (TWRP) and it said I had no OS installed so I installed the rom (viper) again. Tried to boot and was still in a bootloop, went back into twrp and noticed it said I had -1 mb of storage available. I needed a phone ASAP so I went out and got a new one but I miss my HTC so I figured I would try and get it back on its feet.
This is were I am lost. Whenever I turn it on it bootloops still. I can access Bootloader mode but when I try and access download mode it says "Failed to boot to download mode." and whenever I try to access recovery it just puts me into a bootloop. I am S - ON bootloader is unlocked. Whenever I try to use RUU it just says my battery is below 30%
Whenever I use fastboot getvar I get :
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT565SV00478
Any help would be appreciated!
i was just about to request on the same topic, i've just come across an m9 with what sounds like the same issue, and id really love to restore it back into working condition, fastboot doesnt give me any info or able to send any commands but i have access to a xtc2clip so i was able to read some info on its current state
Sending getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT54GYJ03824
Sending oem readsecureflag
... (bootloader) read secure flag: 3
Click to expand...
Click to collapse
Kiwasad said:
Hello, about a month ago my phone randomly shut off (full battery) and when I tried to turn it back on I was in a bootloop. I was able to boot into recovery mode (TWRP) and it said I had no OS installed so I installed the rom (viper) again. Tried to boot and was still in a bootloop, went back into twrp and noticed it said I had -1 mb of storage available. I needed a phone ASAP so I went out and got a new one but I miss my HTC so I figured I would try and get it back on its feet.
This is were I am lost. Whenever I turn it on it bootloops still. I can access Bootloader mode but when I try and access download mode it says "Failed to boot to download mode." and whenever I try to access recovery it just puts me into a bootloop. I am S - ON bootloader is unlocked. Whenever I try to use RUU it just says my battery is below 30%
Whenever I use fastboot getvar I get :
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT565SV00478
Any help would be appreciated!
Click to expand...
Click to collapse
If u get in TWRP, format your partitions in TWRP before installing a new ROM from your SD.
If not, take it in service.
I cant access TWRP. I'm avoiding sending it in for service since I have a phone to use now and just want to try myself to get this one running. I tried to flash a hosd.img to get download mode back but I get :
target reported max download size of 536870912 bytes
sending 'hosd' (22228 KB)...
OKAY [ 0.688s]
writing 'hosd'...
FAILED (remote: image verify failed. cannot flash this partition)
finished. total time: 0.917
for some odd reason I've turned on the phone today to find out i can now access download mode, but its going to be a fun filled day trying to find the correct ruu as im not able to request cid
sorry edit that, it allowed me to access the recovery today when it wouldn't yesterday. still no joy messing around with it today. the recovery wouldn't let me mount the sdcard to install an update and it wouldn't let me sideload a zip file via adb sideload. would anyone know what update i should use to sideload ??
Still having this problem, any help is appreciated
yeah same, after coming across two m9's with this issue and still no further with my research. but i wont give up and ill report back if i find anything.
Kiwasad said:
Still having this problem, any help is appreciated
Click to expand...
Click to collapse
did you ever find a resolution?
I'm stuck as well
getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT59MSV01213
https://forum.xda-developers.com/sp...print-htc-one-m9-1-32-651-17-t3073355/page106
I have the exact same problem..... plus my laptop updated to Windows 10 so now when I try to install the RUU it just tells me to make sure my USB cable is connect... i have tried every driver.
I seriously need help and instructions on what to do!!
Today my phone turn off suddently and no turned on until i press the power button for 10/20 seconds. Now i got a bootloop phone within GOOGLE LOGO and BLACK SCREEN.
I can enter to BOOTLOADER and i can use FASTBOOT without a problem but the phone is OEM LOCKED and FLASHING LOCKED
Recovery takes me to the bootloop again so after reading and reading i got no answers to my most expensive brick i ever purchased...
There is no way to boot the phone to ENABLE the DEVELOPER OPTIONS.
Google replaces my phone but i will not be in the US for the next 6 months...
This is my ALL VARS i get from the fastboot:
HTML:
(bootloader) version:0.5
(bootloader) hw-revision:PVT
(bootloader) mid:G-2PW2100
(bootloader) version-main:0.12.999.1
(bootloader) imei:[REMOVED]
(bootloader) ramdump-mode:false
(bootloader) boot-mode:FASTBOOT
(bootloader) has-slot:radio:yes
(bootloader) has-slot:bootloader:yes
(bootloader) has-slot:reserve5:no
(bootloader) has-slot:devinfo:no
(bootloader) has-slot:fsg:no
(bootloader) has-slot:mfg:no
(bootloader) has-slot:board_info:no
(bootloader) has-slot:reserve4:no
(bootloader) has-slot:metadata:no
(bootloader) has-slot:pg2fs:no
(bootloader) has-slot:pg1fs:no
(bootloader) has-slot:ramdump:no
(bootloader) has-slot:frp:no
(bootloader) has-slot:reserve3:no
(bootloader) has-slot:cdt:no
(bootloader) has-slot:ddr:no
(bootloader) has-slot:modemst2:no
(bootloader) has-slot:modemst1:no
(bootloader) has-slot:fsc:no
(bootloader) has-slot:dip:no
(bootloader) has-slot:dpo:no
(bootloader) has-slot:devinfobak:no
(bootloader) has-slot:sec:no
(bootloader) has-slot:persist:no
(bootloader) has-slot:ssd:no
(bootloader) has-slot:misc:no
(bootloader) has-slot:xbl:yes
(bootloader) has-slot:reserve0:no
(bootloader) has-slot:userdata:no
(bootloader) has-slot:system:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:apdp:yes
(bootloader) has-slot:msadp:yes
(bootloader) has-slot:modem:yes
(bootloader) has-slot:devcfg:yes
(bootloader) has-slot:hosd:yes
(bootloader) has-slot:boot:yes
(bootloader) has-slot:aboot:yes
(bootloader) has-slot:cmnlib64:yes
(bootloader) has-slot:cmnlib32:yes
(bootloader) has-slot:hyp:yes
(bootloader) has-slot:pmic:yes
(bootloader) has-slot:rpm:yes
(bootloader) has-slot:tz:yes
(bootloader) has-slot:keymaster:yes
(bootloader) has-slot:bootlocker:yes
(bootloader) slot-count:2
(bootloader) current-slot:a
(bootloader) slot-retry-count:b:2
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:2
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3724000
(bootloader) variant:US
(bootloader) secure:yes
(bootloader) unlocked:no
(bootloader) version-baseband:8996-012511-1611190200
(bootloader) version-bootloader:8996-012001-1611091517
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x635400000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0x80000000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0x80000000
(bootloader) partition-type:vendor_b:ext4
(bootloader) partition-size:vendor_b: 0x12c00000
(bootloader) partition-type:vendor_a:ext4
(bootloader) partition-size:vendor_a: 0x12c00000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0x2000000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0x2000000
(bootloader) serialno:HT6C90201174
(bootloader) kernel:lk
(bootloader) product:marlin
Anyone can save me with this problem?
Try skipsofts toolkit might be worth a shot
Heres the thread.
https://forum.xda-developers.com/pixel-xl/development/tool-skipsoft-android-toolkit-google-t3482767
joeyac02 said:
Try skipsofts toolkit might be worth a shot
Heres the thread.
https://forum.xda-developers.com/pixel-xl/development/tool-skipsoft-android-toolkit-google-t3482767
Click to expand...
Click to collapse
Thanks but it doesn't work...it requires "ENABLE/ALLOW OEM UNLOCKING" but i can't boot into android...:crying:
lupus2k said:
Thanks but it doesn't work...it requires "ENABLE/ALLOW OEM UNLOCKING" but i can't boot into android...:crying:
Click to expand...
Click to collapse
Try this command > fastboot continue
cam30era said:
Try this command > fastboot continue
Click to expand...
Click to collapse
Nothing...keeps bootlooping...
First off I am really sorry to hear about your issue. It sounds similar to one I had, however my bootloaded was unlocked so I was able to install a full factory image and be up and running.
Question: Are you saying your bootloader WAS unlocked and now it is not since the shutdown occurred?
ssb13 said:
First off I am really sorry to hear about your issue. It sounds similar to one I had, however my bootloaded was unlocked so I was able to install a full factory image and be up and running.
Question: Are you saying your bootloader WAS unlocked and now it is not since the shutdown occurred?
Click to expand...
Click to collapse
Nonono, i enabled do the ADB DEBUGGING in the phone (is the first phone i not do this).
The bootloader was never unlocked...
Can you get in Stock recovery via bootloader
If yes and you see the lying android hold power and press vol+
You can try a factory reset there.
If this is not helping
You can try sideload ota image from there
Just follow Google instructions here
https://developers.google.com/android/ota
mikaole said:
Can you get in Stock recovery via bootloader
If yes and you see the lying android hold power and press vol+
You can try a factory reset there.
If this is not helping
You can try sideload ota image from there
Just follow Google instructions here
https://developers.google.com/android/ota
Click to expand...
Click to collapse
It doesn't work...i can't enter to recovery :crying:
So if you choose recovery in when you are in bootloader it just bootloops again?
mikaole said:
So if you choose recovery in when you are in bootloader it just bootloops again?
Click to expand...
Click to collapse
Yes...bootloops when:
- Normal power on
- Fastboot + command "fastboot continue"
- Fastboot + press Start
- Fastboot + press Recovery
Any chance you can boot to TWRP?
sliding_billy said:
Any chance you can boot to TWRP?
Click to expand...
Click to collapse
No...cant install any recovery because of OEM LOCKED
lupus2k said:
No...cant install any recovery because of OEM LOCKED
Click to expand...
Click to collapse
I wasn't looking to install the recovery but instead to tmp boot to TWRP and work from there (including sideload). I wasn't sure if that needed OEM unlocked.
lupus2k said:
Yes...bootloops when:
- Normal power on
- Fastboot + command "fastboot continue"
- Fastboot + press Start
- Fastboot + press Recovery
Click to expand...
Click to collapse
Fastboot has nothing to do with bootloader. When you are in bootloader on your phone you can choose with vol+ and vol- between several commands.
Start
Restart bootloader
Recovery Mode
Barcodes
Power off
Choose recovery mode
mikaole said:
Fastboot has nothing to do with bootloader. When you are in bootloader on your phone you can choose with vol+ and vol- between several commands.
Start
Restart bootloader
Recovery Mode
Barcodes
Power off
Choose recovery mode
Click to expand...
Click to collapse
Yes i will do this and goes to bootloop again....bootloops everywhere!
lupus2k said:
Yes i will do this and goes to bootloop again....bootloops everywhere!
Click to expand...
Click to collapse
Wait so you can get into bootloader mode? What is the issue then? Can't you just flash the factory image?
aholeinthewor1d said:
Wait so you can get into bootloader mode? What is the issue then? Can't you just flash the factory image?
Click to expand...
Click to collapse
No, i never enabled the USB DEBUGGING in Developer Options when the phone works so i can't execute the "fastboot oem unlock" to enable Flash in fastboot
Curiously, I've just run into the same issue. I found that unplugging the device from any usb cable, then choosing the "power off" option would sort of reset the bootloop and bring the whole system down. Once I did that I could boot into the bootloader menu with Power + Vol down, then choose recovery, and it would (usually) boot successfully to the "no command" screen in the recovery system. I was able to flash the OTA file via adb once I got it to that point, but unfortunately even after flashing OTA and then doing the factory reset process I still can not get it to fully boot up . It sounds like I'm a little bit further along in troubleshooting than OP at the moment, but I don't have good news to share...
superhyper said:
Curiously, I've just run into the same issue. I found that unplugging the device from any usb cable, then choosing the "power off" option would sort of reset the bootloop and bring the whole system down. Once I did that I could boot into the bootloader menu with Power + Vol down, then choose recovery, and it would (usually) boot successfully to the "no command" screen in the recovery system. I was able to flash the OTA file via adb once I got it to that point, but unfortunately even after flashing OTA and then doing the factory reset process I still can not get it to fully boot up . It sounds like I'm a little bit further along in troubleshooting than OP at the moment, but I don't have good news to share...
Click to expand...
Click to collapse
Sorry to hear about that....
I try this and mine don't even enter to recovery...
Hi,
I have read a lot of Threads and still nothing.
Device: HTC ONE m9
S-on, Official, Locked
When i try get into Recovery Mode (Silver Logo HTC and restart restart and restart)
When i try get into Download Mode result is same.
I cant flash anything because fu***g s-on blocks everything.
I tried by RUU.exe and it always gives me error that battery havent 30% but i recharged battery and it shows me 100% on lcd.
command fastboot getvar all shows this:
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT61KYJ00849
no bootloader version?
Is it possible to fix this htc or i have to change motherboard?
Give me any advices, please
BTW, sorry for my bad English and thanks for reply!
maslo77 said:
Hi,
I have read a lot of Threads and still nothing.
Device: HTC ONE m9
S-on, Official, Locked
When i try get into Recovery Mode (Silver Logo HTC and restart restart and restart)
When i try get into Download Mode result is same.
I cant flash anything because fu***g s-on blocks everything.
I tried by RUU.exe and it always gives me error that battery havent 30% but i recharged battery and it shows me 100% on lcd.
command fastboot getvar all shows this:
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT61KYJ00849
no bootloader version?
Is it possible to fix this htc or i have to change motherboard?
Give me any advices, please
BTW, sorry for my bad English and thanks for reply!
Click to expand...
Click to collapse
Have you tried flashing one the the RUU zips in fastboot mode?
Download RUU from https://forum.xda-developers.com/showpost.php?p=65358513&postcount=4.
Boot to bootloader and issue "fastboot oem rebootRUU"
Once the device reboots, you see the HTC logo, and your computer recognizes the device, go ahead and issue "fastboot flash zip 0PJAIMG....zip" and wait.
In my experiences, you don't have to run the flash command twice, it does it for you with the M9. Just see if it says flush again and if it doesn't do it for you, issue the "fastboot flash zip 0PJAIMG...zip" again.
Once it completes and you are back at a command prompt, issue "fastboot reboot-bootloader"
See if the version matches. Finally issue "fastboot reboot" and see if it boots up to Android!
Report back... good luck.
If I helped, click Thanks
Edit:
If you are planning on rooting or S-Offing, you may want to use the 3.37.605.7 firmware since that is last firmware Sunshine can temproot. Of course you already have to be on the 3.37.605.x firmware because you can't downgrade firmware versions with S-On. If you can get to bootloader, you see which version you are on
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