Question: Unlocking while firmware updates? - Xiaomi Poco X3 NFC Questions & Answers

when unlocking the bootloader and there is a waiting period of 1-2 weeks but in the meanwhile the phone wants to update it's firmware, what to do?
- is the unlock process interrupted when the phone updates itself to the next miui version?
- or is it actually necessary to update to the new version to successfully finish the unlocking process? (f.i. the "unlock" process started with the old miui version but ends with a new miui version)
the community blog is not clear about that, anyone got experience with that?
EDIT: nevermind, already done. for those who want to know nevertheless: don't update the firmware while on a waiting period to unlock, just stick to the version you started unlocking the phone, it works. though, it might work with updating too I've not tested it.

Related

Question regarding unlocking with the new firmware

I'm about to unlock and put Cleanrom on this bad boy. I haven't rooted my infinity yet and have just installed the latest firmware update. Has anyone had any issues with unlocking or rooting after they installed the latest firmware? I don't want to soft brick it and wait for a work around if possible. Thanks
spillner said:
I'm about to unlock and put Cleanrom on this bad boy. I haven't rooted my infinity yet and have just installed the latest firmware update. Has anyone had any issues with unlocking or rooting after they installed the latest firmware? I don't want to soft brick it and wait for a work around if possible. Thanks
Click to expand...
Click to collapse
First, you are not going to brick your device trying to unlock or root. It's pretty safe! Second, I heard a few reports that you are not able to unlock at this time due to some issue with Asus server, but you could try, not going to hurt, if it failed, keep trying until you get it.

Is it possible to sideload OTA and downgrade with a locked bootloader?

Title says it all. I have a 7.1.2 (beta) Pixel on VZW with a locked bootloader. I'd like to go back to 7.1.1 public static le release. I unenroll from the beta program and I haven't got an OTA to go back. It's been over 24hrs.
I know Google will eventually fix their OTA beta system, but in the meantime can't I do this manually?
I tried to side load the 7.1.1 OTA from Google via ADB and it gave me an error about being older than the version currently on the device. Is there a file I can modify in the OTA.zip to get around that or am I stuck as long as my bootloader is locked?
farfromovin said:
Title says it all. I have a 7.1.2 (beta) Pixel on VZW with a locked bootloader. I'd like to go back to 7.1.1 public static le release. I unenroll from the beta program and I haven't got an OTA to go back. It's been over 24hrs.
I know Google will eventually fix their OTA beta system, but in the meantime can't I do this manually?
I tried to side load the 7.1.1 OTA from Google via ADB and it gave me an error about being older than the version currently on the device. Is there a file I can modify in the OTA.zip to get around that or am I stuck as long as my bootloader is locked?
Click to expand...
Click to collapse
You're stuck for now. Don't modify anything that might brick the device since you can't recover with a locked bl. Just wait for the public release to be sent to the device. Why do you want to go back to 7.1.1?
bobby janow said:
You're stuck for now. Don't modify anything that might brick the device since you can't recover with a locked bl. Just wait for the public release to be sent to the device. Why do you want to go back to 7.1.1?
Click to expand...
Click to collapse
Ok thanks. I didn't notice anything new with 7.1.2 other than a couple little bugs. I had some graphical tearing on the status bar initially and then wifi advanced settings continuously crashes if you try to open it. Personally, I like 7.1.1 better than the first beta 7.1.2.
Since the update to 7.1.1 any possibility to downgrade is blocked. Verizon pushed the update to block any method that allows bootloader unlock. If you were locked and took the OTA you are permanently locked. Although anything is possible do not hold out for a new exploit to be found. I have never seen a new method found to unlock a device that has had the exploit patched.

[S8+] Purchased a stock AT&T S8+ in a lot. It has latest bootloader and bad IMEI....

[S8+] Purchased a stock AT&T S8+ in a lot. It has latest bootloader and bad IMEI....
First off, I'm an engineering scientist with years of development experience developing both hardware and software for all sorts of phones and companies. So I feel I'm pretty familiar with Android and every conceivable (and off-the-wall) way to get this phone unlocked, rooted, and/or just flat out usable. And I have failed which is why I am finally giving this to the multiverse in hopes there is someone with some solution I have yet to attempt.
I have been searching and trying every possible option for a week and counting. I'm also aware of how close to impossible it is to work with locked Snapdragon CPUs. But not entirely impossible. There has to be a way of reviving this phone!
So I recently purchased a lot full of untested and "for parts" electronics. In there was an AT&T S8+ with a cracked screen. It was also stuck in a boot loop, so I can safely hazard a guess that someone tried to update the ROM, bricked it, and didn't realize they could reflash stock firmware and fix it. Well, upon further examination, I discovered they had attempted flashing a V7 bootloader. Yes, version 7. So that basically robbed me of any options I may have had, as well as all the bugs I could have used to root the device. All I could do was install Pie with a V7 bootloader. Voila! The phone boots up. But it gets better....
Now that the phone was working, I did some examining, one part of which was the IMEI as I wanted to unlock it if possible. I check the IMEI, and it is frakking blacklisted! So that blew ever being able to use this phone on a network. I even sat on hold for 46 minutes to speak with someone at AT&T to see if they could remove it off the blacklist. They promptly said "sure!", then transferred me to someone else to fix it and the guy said "no".. So it's stuck locked to AT&T, which sucks because I checked with several other networks who all said the phone could be used on their networks. But that's not an option if it is carrier locked and impossible to unlock. :silly:
Furthermore, OEM Unlock is 110% unavailable, and no bugs work or exist to force it to appear on Android 9 Pie like you can with 8 Oreo and 7 Nougat; and I tried for days. So the bootloader is permanently locked. If it wasn't, I could root the phone, fix the IMEI, unlock it, and get the phone functional again. Alas, I cannot, at least any time soon, if ever.
I've tried every possible thing out there to root this, unlock the bootloader, and/or try to roll back Pie to Oreo, Nougat, or some stock ROM with bugs that are still active. At the very least just to change the IMEI and get the phone working again. But there is no version of Oreo/Nougat that can be installed with a V7 bootloader.
Also, there is absolutely no Engineering Mode (NOT Developer Mode) available under this stock Android 9 Pie, either by code or by app/settings. Does anybody know of an exact Android 9 Pie stock ROM with an accessible no-root Engineering Mode?
And I've tried every way out there to force OEM Unlock to appear, but the bugs that work in Oreo and Nougat have all been patched and none of them work on Android 9 Pie. So I'm stuck with this ROM and bootloader
So I'm here today with these issues in hopes someone may have solutions for:
A way to force OEM Unlock to appear under Android 9 Pie (as no Oreo/Nougat hacks work under Pie)
A way to bypass KG state under stock Android 9 Pie (as no Oreo/Nougat hacks work under Pie)
A way to install Android 8 Oreo or Android 7 Nougat with a V7 bootloader
A stock ROM with Engineering Mode available
A way to change the IMEI without root
A way to modify the V7 stock ROM so it installs a Nougat/Oreo ROM instead of Pie
Another option to keep this phone from just being a fancy, pretty paperweight
Any solution we or I may discover, I will clean it up and make a guide to help others with these same issues as there is not much info yet V7 on bootloaders. So this is a group activity that could help many, many people; help me help us all!
Thank you all in advance for anything you can offer to help!
-DL
EDIT 1: I forgot to mention that the KG State is stuck on "Checking...." so I couldn't get "OEM Unlock" even by waiting
I used this video to figure out how to get the OEM Unlock option.
(input this after youtube url) watch?v=zhNhyT4F3e8&t=133s
Hopefully this helps.
domiluci said:
First off, I'm an engineering scientist with years of development experience developing both hardware and software for all sorts of phones and companies. So I feel I'm pretty familiar with Android and every conceivable (and off-the-wall) way to get this phone unlocked, rooted, and/or just flat out usable. And I have failed which is why I am finally giving this to the multiverse in hopes there is someone with some solution I have yet to attempt.
I have been searching and trying every possible option for a week and counting. I'm also aware of how close to impossible it is to work with locked Snapdragon CPUs. But not entirely impossible. There has to be a way of reviving this phone!
So I recently purchased a lot full of untested and "for parts" electronics. In there was an AT&T S8+ with a cracked screen. It was also stuck in a boot loop, so I can safely hazard a guess that someone tried to update the ROM, bricked it, and didn't realize they could reflash stock firmware and fix it. Well, upon further examination, I discovered they had attempted flashing a V7 bootloader. Yes, version 7. So that basically robbed me of any options I may have had, as well as all the bugs I could have used to root the device. All I could do was install Pie with a V7 bootloader. Voila! The phone boots up. But it gets better....
Now that the phone was working, I did some examining, one part of which was the IMEI as I wanted to unlock it if possible. I check the IMEI, and it is frakking blacklisted! So that blew ever being able to use this phone on a network. I even sat on hold for 46 minutes to speak with someone at AT&T to see if they could remove it off the blacklist. They promptly said "sure!", then transferred me to someone else to fix it and the guy said "no".. So it's stuck locked to AT&T, which sucks because I checked with several other networks who all said the phone could be used on their networks. But that's not an option if it is carrier locked and impossible to unlock. :silly:
Furthermore, OEM Unlock is 110% unavailable, and no bugs work or exist to force it to appear on Android 9 Pie like you can with 8 Oreo and 7 Nougat; and I tried for days. So the bootloader is permanently locked. If it wasn't, I could root the phone, fix the IMEI, unlock it, and get the phone functional again. Alas, I cannot, at least any time soon, if ever.
I've tried every possible thing out there to root this, unlock the bootloader, and/or try to roll back Pie to Oreo, Nougat, or some stock ROM with bugs that are still active. At the very least just to change the IMEI and get the phone working again. But there is no version of Oreo/Nougat that can be installed with a V7 bootloader.
Also, there is absolutely no Engineering Mode (NOT Developer Mode) available under this stock Android 9 Pie, either by code or by app/settings. Does anybody know of an exact Android 9 Pie stock ROM with an accessible no-root Engineering Mode?
And I've tried every way out there to force OEM Unlock to appear, but the bugs that work in Oreo and Nougat have all been patched and none of them work on Android 9 Pie. So I'm stuck with this ROM and bootloader
So I'm here today with these issues in hopes someone may have solutions for:
A way to force OEM Unlock to appear under Android 9 Pie (as no Oreo/Nougat hacks work under Pie)
A way to bypass KG state under stock Android 9 Pie (as no Oreo/Nougat hacks work under Pie)
A way to install Android 8 Oreo or Android 7 Nougat with a V7 bootloader
A stock ROM with Engineering Mode available
A way to change the IMEI without root
A way to modify the V7 stock ROM so it installs a Nougat/Oreo ROM instead of Pie
Another option to keep this phone from just being a fancy, pretty paperweight
Any solution we or I may discover, I will clean it up and make a guide to help others with these same issues as there is not much info yet V7 on bootloaders. So this is a group activity that could help many, many people; help me help us all!
Thank you all in advance for anything you can offer to help!
-DL
EDIT 1: I forgot to mention that the KG State is stuck on "Checking...." so I couldn't get "OEM Unlock" even by waiting
Click to expand...
Click to collapse
There is no OEM unlock on us snap dragon devices. Locked boot loader. Closest you will get is the combination firmware. But the OEM unlock in that does not work trust me on this. The imei is cert coded to the hardware. And can't be discussed on xda how to change. It's possible. But not by just anyone. The combination files are nougat. But their not going to help you out in this situation

Relocking the bootloader after vendor build change

So, I have the MIUI 12 EEA on a Mi 10 Lite, and it's not the stock ROM but the Vodafone build (QJIEUVF).
As there's the new Android 11 update coming, I'd like to have that and not wait for Vodafone to release its build, as that's notoriously slow.
I tried the official Updater app, to install the XM build, but it says the network carrier is different. Seems like the only way is to unlock the bootloader. However, it seems that means losing Netflix and Google Pay support?
Now, can I unlock the bootloader, flash the QJIEUXM with XiaoMiToolV2, and then relock the bootloader with Clean and Lock? Would that lead to a softbrick? Any other downside to doing that, such as losing OTA updates?
I tried to find info, but it's really hard to find any reliable information anywhere
Hi, I am on the same situation as you, did you successfully relocked your phone?

Weird t-mobile OTA / factory reset issue

Hello just a few minutes ago I manually searched for updates from the system setting (have auto update off) and realized I had an update so I took it. I've taken updates OTA before with no issues however this time it basically completely factory data reset my phone and also what's more bizarre is it removed my bootloader unlock that I had gotten way back when the phone was first released. I have never installed custom firmware or even rooted the device but I did get my bootloader unlocked using a paid service that I found about here. I have a snapdragon model note 20 ultra 5g. I am so confused why this time around the OTA affected these things. I have included a screenshot of the OTA I took. Can anyone tell me what happened to my bootloader unlock I've had for like 6 months ?
Do you have a U or a UI device? If so I think Samsung changed the bootloader from version 1 to version 2 and that might be why you lost it. Checkout the last 2 pages of this thread here where you might be able to get more clarification.
Whenever you lock or unlock your bootloader, you device will factory reset.
When you took the update, it updated the bootloader to version 2.
Since your unlock was not an official one, it relocked your bootloader in the process.
This is what caused the wipe.
Yup. You're not supposed to take ota updates with unofficial unlocked bootloader.
Not even sim unlock.
coilbio said:
Yup. You're not supposed to take ota updates with unofficial unlocked bootloader.
Not even sim unlock.
Click to expand...
Click to collapse
Is there such a thing as an official bootloader unlock?
shpotik said:
Is there such a thing as an official bootloader unlock?
Click to expand...
Click to collapse
Nope. Not for US versions.
Why did you unlock the bootloader if you haven't ever rooted or flashed custom?
*Detection* said:
Why did you unlock the bootloader if you haven't ever rooted or flashed custom?
Click to expand...
Click to collapse
It sounded like a good idea at the time.

Categories

Resources