Bootloader mode broken - Android Q&A, Help & Troubleshooting

This might be the first problem that everyone didn't encountered yet
So recently I unlocked my bootloader in order to flash custom ROM, but recently I reverted back to stock and decided to lock my bootloader in order to get OTA updates.after getting OTA updates I decided to unlock the bootloader again, when I was trying to boot to bootloader mode, it just shows the bootloader icon and boot back to system. I tried to use the in depth test app but it only shows me to request to exit deeptesting and the query status is not submitted.i tried to request to exit deeptesting but it only says no internet connection. I tried almost everything including flashing previous ROM, changing region, etc but none of it works
My device is Realms GT Master Edition (RMX3360) C.09In

Related

Is my bootloader unlocked? Rooting status: UNAVAILABLE in service menu

Unlocking bootloader wasn't allowed on my phone, but I decided to give it a try anyways. Flashtool reported that the unlocking process was finished, but the progress bar was stuck somewhere at the half-way point for 10 minutes or so. After this, rooting status in the service menu changed to Unavailable, and I can't tell whether my bootloader is unlocked or not, or somewhere in between.
I tried flashing a custom rom, it gets stuck indefinitely on the animated boot screen, but I don't get any errors, crashes, or warnings while installing the zip in TWRP.
I noticed that after the "unlocking" procedure, my phone takes significantly less time to boot and the interface seems to lag less.
So what is going on here? Have I really somehow unlocked my bootloader?
Try relock bootloader, and unlock bootloader again
I have the same issue
I want to unlock my bootloader and in status it says available no or when i tried to unlock it it says unavailable
Please help
Mine too.
I can only use my Sim slot 2 (slot 1 is not working)
I need help.
I tried installing the new marshmallows from Xperifirm but still not working.
Rooting status: UNAVAILABLE

Dead phone

Hello guys,
I'm not a noob when we speak about flashing ROMs and unlocking bootloaders. I've been doing that for some years. Yesterday I flashed the new stock ROM for LG G4 - v29a, android 7.0. Everything went fine. Later this day, I've seen a post claiming that it was possible to relock your bootloader with this specific ROM using the fastboot oem lock. And it worked indeed. The problem now is that when I turn on the phone the following message shows up on RED: "Your device is corrupt. It cannot be trusted and may not work properly".
So, here's the problem:
1 - Can't access recovery;
2- Can't access download mode;
3 - Can't boot normally;
4 - Can't re-unlock since (i guess) the IMEI is now 0;
5 - Can't flash stock ROM using LGUP;
6- Can't erase any partition via adb since the bootloader is now locked;
So, basically all my ways are locked. Any fix you know and want to share?

Moto Z bricked OEM Locked

Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
I'm with same problem here!
Suckmymfdick17 said:
Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
Click to expand...
Click to collapse
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
knjigo said:
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
Click to expand...
Click to collapse
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Suckmymfdick17 said:
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Click to expand...
Click to collapse
What do you mean with "I blocked my bootloader"?
Twrp is easy to flash. Root is integrated in ressurection remix rom. And this rom is great. Just try to flash twrp in Fastboot and than ressurection remix with twrp.
Can you boot in Fastboot?
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
tjgibri said:
I'm with same problem here!
Click to expand...
Click to collapse
I solved it, I finally flashed the stock rom to my phone and it works.
Apparently my pc was not flashing the stock rom in adb, and the phone turned off when loading the software. I did it 3 times until I load correctly and start well.
if you have the same problem apparently then OEM Blocking is not responsible. You have to flash the most current rom or the one that you had by default when the brick happened to you, you flash it in a normal way with commands of adb and ready, I would have to come back to life.
download from firmware center MotoZ Griffin the most current rom stock at 7.1.1
echo92 said:
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
Click to expand...
Click to collapse
Thanks for your help friend, I finally flashed it with a recent android 7.1.1 update. Apparently the OEM lockout was not the culprit, but it was an interrupted flash of android 7.1.1 at some point when loading the software to the phone, it would shut down on its own and not complete the installation, which showed me the mentioned message. I didn't realize that and thought it was the OEM blockade.
I finally did it on another pc and it worked. the phone came back to life.
I have one Moto Z2 Force (XT1789-05), bought from coolicool.com, I didn't know device came Unlocked Bootloader, Device rom had problem with many apps, I googled and found one topic in XDA developer to Install Stock Rom, I downloaded and Installed India Rom, it's worked somehow fine, but still had problem, I downloaded Verizon Rom, Android 8, after Installed Android 8 Verizon Rom, Locked device bootloader immediately, now device stuck at Welcome Wizard in Android 8, after select language I got this message: (Please wait, this may take a few minutes) this is proof video (http://ahmn.co/Upload/IMG_0161.MOV), after this issue, device already locked, I can't unlock, because need to go to the Developer Option in Setting, I stucked in Welcome Wizard, there isn't any bypass, So, I start to search in Google, XDA-Forum, Android Central and more, I created many threads, many requests, no one can't help me, I tried to reach google developer support to the tell to me how can I bypass Android 8 Welcome Wizard, there is must be a way, but I can't find it, now I can access to Android Recovery and Bootloader
1. if you help me to FORCE UNLOCK device without need Developer Option in setting my problem will solve
2. If you help me to Bypass Android Welcome Wizard, access setting and enable OEM Unlock
3. If you help me to update the device from Android 8 to Android 9 Verizon ROM via ADB Sideload or Update from SD card in Recovery mode
4. If you have any idea to how can I fix it
Extra Information: I bought Belkin and Uni USB-C to Ethernet Adaptor to help me bypass Android 8 Welcome Wizard, I bought WSKY WIFI Adaptor because device Wifi can't find any network (I found QR setup by tap several times in Language Selection), after this section need to download google device policy apk, my device can't find any Wifi Network and my Ethernet Adaptor can't help me either, So, I just remained with my phone, and I can't do anything,
Please, someone, help me
My Device SKU: XT1789-05

P10 Lite Bootloader locked/unlocked at the same time? OEM Unlocking greyed out?

Hi all,
I have a P10 Lite that is running Nougat, EMUI 5.1. The phone displays the very ominous 'This phone has been unlocked and is therefore not secure' message at every boot. I would like to get rid of this message as we are putting it back on sale within the store and do not want to scare customers with this warning. I have the bootloader lock/unlock code but whether it is locked/unlocked, the message still appears AND OEM unlocking is greyed out in developer settings. Additionally after 'locking' it in fastboot, when put back into fastboot mode it still displayed as 'Phone Unlocked'. I have tried updating it through SD card but that did nothing. Is it basically stuck in this state now?
Just flash official firmware to replace bootloader.
Skyhuppa said:
Just flash official firmware to replace bootloader.
Click to expand...
Click to collapse
How can I flash if OEM unlocking is greyed out?
pandatechrma said:
How can I flash if OEM unlocking is greyed out?
Click to expand...
Click to collapse
I think flashing it original full firmware will work for you, whether OEM unlocking at settings has greyed or disappear. Ones the device drivers can be recognize by computer at this stage it should support full flash. That is why is always advisable to keep device full backup before tempering with it. Download the device original firmware online, use it supported flash tool and flash through computer.
Since you are also on sale point or shop, you can take same phone from shop if available, backup then restore the files to the OEM greyed phone.
But before performing full flash make sure you keep backup of exiting firmware, so that you can restore back when new firmware does not support your device.
I think flashing it original full firmware will work for you, whether OEM unlocking at settings has greyed or disappear. Ones the device drivers can be recognize by computer.
Check this link but follow all instructions and comments
https://forum-xda--developers-com.c...pilation-firmware-flasheables-huawei-t3736754

S9+ G965 flashing issues

I've recently (successfully?) bootloader unlocked my S9+ snapdragon and am trying to flash twrp in order to flash lineage. I waited a week for the oem unlock option, which I used sucessfully, and I used the crom service app to unlock my bootloader. Neither have given me any issues, and when I boot normally and open the crom app, it tells me that my bootloader is already unlocked. Unfortunately, when I run odin, it successfully sees my device and is able to push the twrp .img.tar file through the AP option. It fails to flash however, and the phone gives a "only official released binaries are allowed" message. The frp lock and oem lock fields say off in the download mode screen, but the rmm state is prenormal again. I've heard that you can flash some rmm state bypass zip if if resets after you unlock your phone, but I'm not sure which one would work with my device, or if I need to wait another week. Thanks in advance to anyone who can provide information on what I should do.

Categories

Resources