Hello, i have a nokia lumia 920 with 8.1, build 8.10.12393.890, and i can't seem to find anything to install more than the 2 xap limit provided by the developer unlock.The chinese jailbreak tool doesn't seem to be active anymore and doesn't do anything, (i really wanted at least to be able to install 10 xap's).Interop unlock doesn't work anymore (too late).And every other method requires an sd card, which lumia 920 doesn't have.Isn't there any way to root, vcreg, or remove that 2 xap limit?i also wouldn't install windows 10, as i don't wanna risk bricking my device.
Edit : Apparently, there is something called Wpinternal, wich unlocks the bootloader and grants root acces to the phone, the problem is now, it says there that i need a .ffu file that must match the rom image installed on my phone, i have an at&t cyan version, and i can't seem to find it anywhere, also says there's some risk of bricking, really intimidating stuff there :'(
Even later edit : So i tried to flash something to unlock the bootloader with wpinternal but used a wrong ffu file and messed everything up and bricked my phone, windows device recovery showed fatal error, and nokia recovery tool showed unhandled exception.
After realising that i may have messed up the phone forever and started crying a little, i reflashed an original image with wpinternal, and succesfully unlocked the bootloader and rooted the phone with mass storage and registry acces
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
Hi, I would like to see what the bootloader unlock does exactly do to the raw flash storage. Older phones can be fully unlocked that way, without official permission. Obviously, I need to read out the raw partitions before and after unlocking. The easiest way is to get root and backup from MIUI.
Does anybody know how to root the stock MIUI without unlocking the bootloader? Re-locking does not count.
Does a bootloader-locked, unrooted, stock MIUI let you downgrade? An older ROM might have security bugs that let you root it.
Known pieces of the puzzle, if going the root route:
* Earlier Xiaomi devices let you unlock the bootloader by writing to the devinfo partition. Both the Redmi Note 3 (kenzo) and Redmi Note 4 (mido) still have the bits set at 0x10 and 0x18 as described in the link. But Xiaomi changed things starting with the Redmi Note 5 (whyred) - it has a bit set at 0x90 in an otherwise conspiciously empty devinfo partition.
* The Sony Xperia XZ1 compact can be rooted without unlocking. For that phone, it's motived by DRM.
* How to take complete control of pre-2016 phones. Today, this can serve as a tutorial. Beyond my abilities.
The second way would be to read out (and write to) the phone in EDL mode, or memory debug mode, ...., before and after unlocking the bootloader. Known pieces of the puzzle:
* Zeroing out the abl_a and abl_b partitions might grant read/write access to the raw flash as a mass storage device. This is memory debug mode, similar to EDL. If it doesn't work, you will need EDL to recover because you zeroed out fastboot.
* A list of points of attack on EDL authentication. Once you can bypass EDL authentication, it lets you read and write to raw flash. However, a direct attack on EDL authentication is beyond my abilites.
* Enter EDL mode with test point method or by grounding one of the pins next to the SystemOnChip.
Does anybody know how to bypass EDL authentication?
Does anybody know how to enter memory debug mode without root?
The third way would be to decompile the bootloader chain and see how each piece checks bootloader lock status. However, this is the least useful and probably least fun method. Known pieces of the puzzle:
* Description of the Snapdragon 845 boot process (older but more complete overview)
* Unlock status is checked both by the primary bootloader and the Android bootloader. The primary bootloader lives somewhere in memory and will let you into EDL if the bootloader is unlocked and you rebooted with "fastboot oem edl" etc. The Android bootloader image is the abl.elf file in the official update downloads. It will let you flash (or honor "fastboot oem edl") if it is unlocked.
* Memory debug mode is accessed through the XBL bootloader, i.e. the xbl.img and xbl_config.img files in the official update downloads.
If you found this thread trying to unbrick your phone, you need to go here instead.
Hello sir,
I recently flashed a custom rom using twrp and successfully done, but then i thought to re-lock bootloader,
So, i did that using command
"fastboot flash oem lock"
and my device get bricked, it said the system has been destroyed
And screen get stuck in fastboot
I tried again flash twrp but nothing happened,
I also tried to flash by MiFlash tool but nothing happened,
Pls solve my problem
That's not a soft brick. That's a truly proper bricked device.
To relock a bootloader you must be 100% pure stock with no modifications whatsoever.
You can't relock a bootloader if you have a custom ROM installed.
The fact you locked the bootloader now opens up a lot of issues for you and the only way to recover is flashing in edl mode with a verified mi account.
In other words your going to have to look for someone with a verified account and give them remote access to your pc and probably have to pay them to get your device up and going again.
If you have a service centre near where you are you can try there but a person with a verified account is what you need.
Also you can't ask anyone here for it because paid services are against forum rules.
Always read up on stuff before attempting anything on your device.
Hello everyone, I've recently tried to root my Redmi Note 9 (merlinnfc) The OEM in Dev options is turned on, and the only problem is, there's no way to fix the " FAILED (remote: 'Token verification failed') " error message.
I have everything i need, there's the magisk zip on the phone, and i have the TWRP image for it.
The only this i need to do is unlock the boot loader.
Any ways to unlock it? PS: I've tried MiUnlock, my country's unssuported. (It dosen't work. No verification message, turns out my region isn't supported)
Best Regards - FriendlyChemist
Hint: Add "Redmi Note 9" to front of this tread's title thus owners of this device get addressed.