Hi, i'm confused, i flashed my xperia x10i with x10_2.3.3_stock-with-xrecovery-v3.ftf, when i boot up,i get the custom logo as seen on youtube. When i dial the code in to get the system settings menu up, there is no sign of bootloader info,according to SE web site if this is'nt present then it can't be unlocked. Also, i can still use TrackID.
So, am i locked or unlocked ? ......Anyone ?......Please.
Problem solved,thanx to this post
http://forum.xda-developers.com/showthread.php?t=1636686
my phone had the small r,so that meant the bootloader was unlocked,
Thanx Guys
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
Hey folks,
I've tried my best so far, but I am stuck.
I wanted to change the ROM on my wife's Redmi 3 pro. It was running on a rather old RR version and I wanted to go back to MIUI to have a better camera.
After an unsuccesful attempt to flash this, I was stuck in a bootloop.
This - in general - was no problem: I've decieded to flash an official firmware via MiFlash, but this apparently didn't work as well.
So, now MiFlash has locked the phone again but not properly installed anything.
I can access Fastboot and the pre-installed recovery, but nothing more.
The unlock tool tells me that I can't unlock it because it is apparentyl not bound to my MI account (and I have no clue with which account I've unlocked it the last time).
Desperately appreciation any kind of help!
Thanks in advance.
UPDATE: I was apparently not patient enough. After quite a while it finally booted. Now I can access the system again, but still can't unlock the phone.
UPDATE 2: I also found out with which account I've unlocked it and thus everything worked after all. Now sporting Lineage 14 with camera mod.
Please, feel free to explain how can it finally booted. Your experience might be help somebody sometime.
?
Hello all,
my Pad 4 does not want to start anymore. It comes the Mi logo for a minute then restarts. I have not done anything. It is stock and closed bootloader.
Is there anything I can do here besides a hard reset? I have already tried this via the Mi-Recovery 3.0 without success.
Edit:
Flashing is not allowed in lock state?
I have now tried MiFlash. With the version V10.3.2.0.ODJCNXM. Does this only work with open bootloader?I thought the original I can flash?
stereo007 said:
Flashing is not allowed in lock state?
Click to expand...
Click to collapse
Hi. Never encountered this error, possibly because I unlock the bootloader of all my devices ASAP.
Yet, I always assumed official tools to be exempt from such restrictions -- how else would one solve a catastrophic device failure?
Well, looks like this isn't the case and your only remaining option is to seek help with Mi Customer Service (if available).
Should the device be sold on European markets (which it isn't...) this alone would be reason for a complaint...
hello .... I have a sister redmi note 4 who has a bootloop ... on the screen with the MI logo it keeps restarting .... it goes to fastboot but not to recovery ... the bootloader is locked and I still can't unlock it because what I looked so unlocked in the system by logging into my MI account ... but I can't get to the system ... I tried my flash but it says that it did something for 4 seconds and nothing still the same .... I tried to put it into download mode - by connecting contacts on the board and miflash download ROM to the phone but bootloop still continues
do you have any ideas?
the phone was so stupid that it kept restarting but always after several restarts it started but now even after two days of restart it didn't start ...
thanks sorry for my english
I had a stroke reading this.
Unlocked bootloader is the basic requirement of flashing. If you don't have it, then sorry you're out of options.
Your only option is to flash stock ROM through test-point method. DO IT ON YOUR OWN RISK.
You can find Xiaomi stock ROMs of your device here (MTK) or here (MIDO).
Of course you can always just send your device to a repair center and change it there.
Goodluck.
test point method is lint two pins od board and run mobile to download mode? I try it ... flashing was succesfull but mobile ist still bootloop
johnyfly1 said:
test point method is lint two pins od board and run mobile to download mode? I try it ... flashing was succesfull but mobile ist still bootloop
Click to expand...
Click to collapse
You need to flash stock ROM not any other ROM.
As in the same ROM you had before any issue. Because your bootloader is locked it will refuse to run any boot image that isn't registered in it.
If you have a backup maybe you can flash it through download mode.
I try ROMs from your link and not working...always bootloop I try a lot of ROMs - global, china, stable, weekly and not working....flash is succesfull around 190seconds.... but still bootloop
johnyfly1 said:
I try ROMs from your link and not working...always bootloop I try a lot of ROMs - global, china, stable, weekly and not working....flash is succesfull around 190seconds.... but still bootloop
Click to expand...
Click to collapse
Do you know what ROM you had before the issue started?
I dont know is sister phone... but she have original stock rom... i think global because phone was buy on slovakia
johnyfly1 said:
I dont know is sister phone... but she have original stock rom... i think global because phone was buy on slovakia
Click to expand...
Click to collapse
I Can't help you there mate.
Maybe there is a way to get system info from bricked phone. Maybe through a hex editor or something. That way you know exact version of the ROM you had.
So instead of that maybe you can unlock your bootloader, just request from Xiaomi unlock code with your XIaomi account and unlock it. It usually takes 30-60 days for the request to go through.
Where I find old way to unlock bootloader? because in new unlocker I unlock phone butt I must log in to my account in system... thanks
johnyfly1 said:
Where I find old way to unlock bootloader? because in new unlocker I unlock phone butt I must log in to my account in system... thanks
Click to expand...
Click to collapse
There is no other way to unlock bootloader. Unless you know a guy, know what I'm sayin?