Related
Please, i relock my bootloader, i had unlocked it but i decided to lock it again.
How can I test, how to know if everything is ok? If I did right?
In line Xperia ARC when unlock the bootloader, the Track ID stopped working, when the relock bootloader again, he returned to work.
Xperia in S there is the same way to verify this? Or have some other way to make sure everything is ok with the bootloader? Because I want to receive updates from ICS by PCC or OTA.
Thanks for attention.
Just check it in the service menu.
joaonds said:
Please, i relock my bootloader, i had unlocked it but i decided to lock it again.
How can I test, how to know if everything is ok? If I did right?
In line Xperia ARC when unlock the bootloader, the Track ID stopped working, when the relock bootloader again, he returned to work.
Xperia in S there is the same way to verify this? Or have some other way to make sure everything is ok with the bootloader? Because I want to receive updates from ICS by PCC or OTA.
Thanks for attention.
Click to expand...
Click to collapse
Connect your phone to pc and open PCC, then click on update phone, it'll take few moments and should say no update available or your phone has updated software or something like that...!!! If it says, you are running modified software or something like that then its not locked...!!! Try relocking...!!!
adiktz said:
Connect your phone to pc and open PCC, then click on update phone, it'll take few moments and should say no update available or your phone has updated software or something like that...!!! If it says, you are running modified software or something like that then its not locked...!!! Try relocking...!!!
Click to expand...
Click to collapse
Thanks, PCC say: you have already the last firmware...
So everything is ok here.
Very Thanks !
mine says that even with the bootloader unlocked. try the service menu to find out for sure
Hello everyone.
I had posted this in the Z forum, not realizing there was a Z Ultra forum. So I will just quote my previous post and add some info at the end:
Hello guys. New guy here with an Xperia Z Ultra phone.
I'm trying to load the Paranoid Android custom ROM.
Had a couple of questions:
1. I went thru Sony's instructions to unlock the bootloader. When I ran the fastboot -i 0x0fce oem unlock (e-mail code), the first error message I got was "FAILED - Remote - Command did not succeed". So I tried the exact command again, and then I got "FAILED - Remote: The device is already rooted".
I have searched high and low, and cannot seem to find any way to verify that the bootloader is now in fact unlocked.
2. Reading the instruction on how to install CWM/TWRP recovery menus, Every single list of instructions includes the following "This tutorial is only for Sony Xperia Z Ultra with 510 and 493 LTE firmware. Do not use it for any other carriers or variants"
Again, I have searched high and low to find a way to confirm what firmware version I have. All I know is I have the C6806 model, with the build number: 14.2.A.0.290
So can someone please help out a very confused guy here? I don't want to brick my phone by accident
So far it's still working ok
Click to expand...
Click to collapse
So far, after doing some major searching, I seem to have found that I currently have "290" Firmware, and that this Firmware is currently NOT able to be rooted. Is this correct?
Also, I still have not found a way to verify wether the boot loader actually did unlock or not. From what I have been able to read, it seems that if a proper boot loader was in fact, unlocked, it would have wiped all the data on my phone along with the SD card data.
So far, it seems everything on my phone is intact. So does this mean the boot loader unlock command failed for me? If so, why did I get the reply "this device is already rooted?"
I can't believe how difficult it is to root a damn Android phone! Jailbreaking an Apple device is 10 times easier!
First of all, it's usually pretty easy to root Android devices. In most cases it's only a simple click, but sony has done a good(?) job at fixing exploits, so it does it much harder for us.
Second, you can check if your bootloader is locked or unlocked by opening the dialer and insert *#*#7378423#*#*, go to "Service Info" and then "Configuration". If your bootloader is unlocked, it should say "Rooting status: Bootloader unlocked: Yes". It's easier to use Flashtool to unlock the bootloader if you're having issues using a terminal.
You'll find the rest here (including bootloader unlocking). If you need some help, ask in that thread.
If you aren't boot loader unlocked then "BACKUP TA PARTITION" from My Lord's guide @LordManhattan
Just incase you need to re-lock it for service
LordManhattan said:
First of all, it's usually pretty easy to root Android devices. In most cases it's only a simple click, but sony has done a good(?) job at fixing exploits, so it does it much harder for us.
Second, you can check if your bootloader is locked or unlocked by opening the dialer and insert *#*#7378423#*#*, go to "Service Info" and then "Configuration". If your bootloader is unlocked, it should say "Rooting status: Bootloader unlocked: Yes". It's easier to use Flashtool to unlock the bootloader if you're having issues using a terminal.
You'll find the rest here (including bootloader unlocking). If you need some help, ask in that thread.
Click to expand...
Click to collapse
First of all it' pretty damn complicated and unrewarding to root a Sony device. Not all android but Sony definately. We checked, bootloader is unlockable. We unlocked and relocked bootloader prevoiusly because there is no robust, easy-to-install ROM for ZU. But time to time we try to root it.
Now, the question is the same: what should we do to re-unlock the bootloader if anything is OK, but flashtool says "Command did not succeed" for the first time and "Device is already rooted" for subsequent times at unlocking?
Please write some advice about the question, not about TA backup and your success. Thx!
Champdor said:
First of all it' pretty damn complicated and unrewarding to root a Sony device. Not all android but Sony definately. We checked, bootloader is unlockable. We unlocked and relocked bootloader prevoiusly because there is no robust, easy-to-install ROM for ZU. But time to time we try to root it.
Now, the question is the same: what should we do to re-unlock the bootloader if anything is OK, but flashtool says "Command did not succeed" for the first time and "Device is already rooted" for subsequent times at unlocking?
Please write some advice about the question, not about TA backup and your success. Thx!
Click to expand...
Click to collapse
Oh, are we demanding help now?
Bootloader unlocking is a straight forward process. I've had a couple of strange errors in Flashtool while trying to unlock the bootloader, but just close Flashtool and try again. Also be sure to be on the latest version of Flashtool.
LordManhattan said:
Oh, are we demanding help now?
Bootloader unlocking is a straight forward process. I've had a couple of strange errors in Flashtool while trying to unlock the bootloader, but just close Flashtool and try again. Also be sure to be on the latest version of Flashtool.
Click to expand...
Click to collapse
No sir, not at all. I wrote please, no demanding. Well yes, I'm a bit picky because there were no answer and I usually find some on XDA. Besides I used custom roms on Samsung devices for years (SGS2, SGN, SGN2) and I was disapponted when I bought my XZU that there are very few roms and I couldn't use them (I managed with very hard work to go back to stock in 9 hours after unsuccesful flashing).
So there is some basic problem every time. Like trying to root but cannot re-unlock because of some mysterious errors with no solutions.
Enough of my problems, your answer is much appreciated, will try to re-unlock some time. Thx!
Champdor
Champdor said:
No sir, not at all. I wrote please, no demanding. Well yes, I'm a bit picky because there were no answer and I usually find some on XDA. Besides I used custom roms on Samsung devices for years (SGS2, SGN, SGN2) and I was disapponted when I bought my XZU that there are very few roms and I couldn't use them (I managed with very hard work to go back to stock in 9 hours after unsuccesful flashing).
So there is some basic problem every time. Like trying to root but cannot re-unlock because of some mysterious errors with no solutions.
Enough of my problems, your answer is much appreciated, will try to re-unlock some time. Thx!
Champdor
Click to expand...
Click to collapse
Oh, i get that. I came from Samsung myself, and this is my first Sony device ever, so I've had some issues myself. I've gotten the same error message(s) as you before, and i think i restarted Flashtool and rebooted my Ultra and it was back to normal again - i think, but it "fixed itself" after trying a couple of times, so don't give up. It's also important to always be on the latest version of Flashtool.
It would also help us if you could tell us what you're trying to achieve, so you don't end up spending 9 hours on something that takes 5 minutes
@Champdor
From what I can make out you have never managed root your phone or back up the TA. If the latter is true then there is very little point in relocking the bootloader.
Yes the process is a little harder than Samsung, but the last device I rooted was a ZTE, and that was even harder to root and flash from what I can remember (yes this is my first Sony device as well, and I will buy another...)
Take you time and read the stickies that we have written and all should go well. Don't be afraid to ask (intelligent) questions if you get stuck, and read some more
HELP!
i am in same situation as OP
in past, i unlocked the bootloader then i relocked.
now I like to re-unlock. but I get same errors (i.e. 'command did not suceed' or 'device is already rooted')
i check service menu and it says 'bootloader unlock allowed: yes' meaning its not unlocked yet.
i use latest flashtool and try to unlock but i get error
can any expert help!?
thanks for your help
corrado85 said:
HELP!
i am in same situation as OP
in past, i unlocked the bootloader then i relocked.
now I like to re-unlock. but I get same errors (i.e. 'command did not suceed' or 'device is already rooted')
i check service menu and it says 'bootloader unlock allowed: yes' meaning its not unlocked yet.
i use latest flashtool and try to unlock but i get error
can any expert help!?
thanks for your help
Click to expand...
Click to collapse
I have not had this error so have not tested this, but what happens if you flash a full FTF and wipe everything then try to unlock the BL?
And remember that you can take a backup of the unlocked BL (re member to name it as such) and just flash that to unlock again. Doing it this way you don't get the format that happens when using the unlock code.
I followed this post to downgrade, root, i use Backup TA v9.10 to backup DRM Keys, use Flashtool 0.9.14.0 to unlock Bootloader, then to flash other Rom's (stock and customs), came back to Stock Rom .681, relock the Bootloader with Flastool 0.9.15.0 flashed the last .757 and unlock the Bootloader again with no kind of problems using Flashtool 0.9.15.0....
blueether said:
I have not had this error so have not tested this, but what happens if you flash a full FTF and wipe everything then try to unlock the BL?
And remember that you can take a backup of the unlocked BL (re member to name it as such) and just flash that to unlock again. Doing it this way you don't get the format that happens when using the unlock code.
Click to expand...
Click to collapse
I just flashed C6802 .757 FW using flashtool, and i get same issue
is there a tutorial about backup of the unlocked BL? assuming you meant I have to have own device backup..
this is so confusing at the end :crying:
corrado85 said:
I just flashed C6802 .757 FW using flashtool, and i get same issue
Click to expand...
Click to collapse
I dont know what else to suggest other than rebooting every thing and reinstalling all the drivers
is there a tutorial about backup of the unlocked BL? assuming you meant I have to have own device backup..
this is so confusing at the end :crying:
Click to expand...
Click to collapse
You just back it up as you would for a locked BL. Just remember to make sure you name them well so you know which is the locked one and the unlocked one.
NEVER use a TA backup from another phone, you WILL HARD BRICK IT
Lc1975 said:
I followed this post to downgrade, root, i use Backup TA v9.10 to backup DRM Keys, use Flashtool 0.9.14.0 to unlock Bootloader, then to flash other Rom's (stock and customs), came back to Stock Rom .681, relock the Bootloader with Flastool 0.9.15.0 flashed the last .757 and unlock the Bootloader again with no kind of problems using Flashtool 0.9.15.0....
Click to expand...
Click to collapse
problem is i get message 'device already rooted' when i enter my bootloader key using flashtool as well
---------- Post added at 03:42 PM ---------- Previous post was at 03:40 PM ----------
blueether said:
I dont know what else to suggest other than rebooting every thing and reinstalling all the drivers
You just back it up as you would for a locked BL. Just remember to make sure you name them well so you know which is the locked one and the unlocked one.
NEVER use a TA backup from another phone, you WILL HARD BRICK IT
Click to expand...
Click to collapse
ahh ok, in that case, i do not have a backed up unlocked bootloader rom
corrado85 said:
problem is i get message 'device already rooted' when i enter my bootloader key using flashtool as well
---------- Post added at 03:42 PM ---------- Previous post was at 03:40 PM ----------
ahh ok, in that case, i do not have a backed up unlocked bootloader rom
Click to expand...
Click to collapse
Did you tried:
*#*#SERVICE#*#*
and confirm that the Bootloader is unlock?
Lc1975 said:
Did you tried:
*#*#SERVICE#*#*
and confirm that the Bootloader is unlock?
Click to expand...
Click to collapse
It states
Rooting status
Bootloader unlocked allowed:Yes
corrado85 said:
It states
Rooting status
Bootloader unlocked allowed:Yes
Click to expand...
Click to collapse
When you try to unlock the Bootloader.. What button or icon do you click?
The one who has the padlock or BLU?
Lc1975 said:
When you try to unlock the Bootloader.. What button or icon do you click?
The one who has the padlock or BLU?
Click to expand...
Click to collapse
I choose which states 'BLU'
actually I do get the option to click on padlock but i dont know what to do there
corrado85 said:
I choose which states 'BLU'
actually I do get the option to click on padlock but i dont know what to do there
Click to expand...
Click to collapse
The padlock is to root the device..
Sorry but i can't help you much more then this... I don't have much knowledge to go foward...
Try to start from scratch..
Downgrade...
Root...
Try to unlock the Bootloader
And update to the latest...
root didnt work
Hello , i want to root my phone z ultra 6833 .757 i watch this video youtube . com/watch?v=uFSeSe8gQOY
i unlock bootloader after this install 757.img by flashtool so i can open recovery but after this i didnt find the same file he run i try run supersu.zip but the phone havent rooted plz what the problem
Huami started to lock the bootloader of the Amazfit watch in their official release 1.2.13 and 1.3.2b onwards.
If you want to keep the possibilty to flash custom software on your watch, DO NOT UPGRADE TO THESE VERSIONS. You will not be able to flash any other firmware afterwards.
PACEfied firmware is safe, and does NOT lock your bootloader.
UPDATE 14.07.17:
We have heard several times now via inofficial sources that Huami is working on an official bootloader unlocking service. So far, we, however, have no official information here.
On the other hand, Olivier (french developer on xda) has spent a significant amount of time to understand the unlocking process and we have succeeded to successfully unlock two watches. We are currently in the process of setting up a (free) unlocking web service, allowing individual xda users to unlock their watches for private usage (and accepting loss of warranty from Huami).
In case, Huami may ever come out with their service, we will stop our service, as we do not want to compete with Huami here, just filling the gap if Huami doesn't move forward with their unlocking service.
Please give us some time (we expect 2-3 weeks) to setup the unlock service.
UPDATE 7.08.17:
The unlock service is live now. Head over to https://forum.xda-developers.com/smartwatch/amazfit/tutorial-unlock-bootloader-warning-void-t3654011, if you want your bootloader unlocked!
Fastboot oem unlock
And the command to unlock the bootloader does not work?*
Code:
Fastboot oem unlock
scrubber said:
And the command to unlock the bootloader does not work?*
Code:
Fastboot oem unlock
Click to expand...
Click to collapse
No, neither does
Code:
fastboot flashing unlock
I wouldn't expect Huami to put efforts into locking the bootloader and at the same time making it that easy to unlock it again. This is no coincidence. They saw our work and reacted. That's what happened. Very sad
Neuer_User said:
No, neither does
Code:
fastboot flashing unlock
I wouldn't expect Huami to put efforts into locking the bootloader and at the same time making it that easy to unlock it again. This is no coincidence. They saw our work and reacted. That's what happened. Very sad
Click to expand...
Click to collapse
Perhaps we need to find the Fastboot oem command, they can be different for different devices
https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/
scrubber said:
Perhaps we need to find the Fastboot oem command, they can be different for different devices
https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/
Click to expand...
Click to collapse
Well, the strings dump shows that the "oem unlock" command seems to exist, but it indicates that an unlock code is necessary, probably based on the serial number of the watch:
strings dump extract:
Code:
oem:
unlock
serial no length is null
magic_serialno:%s
, len:%d
%02x
uncrypted_str_serialno:%s
Unlocked code sucess
Unlocked code is error
Unsupport oem cmd
FAILED: The command is not recongized
So, we have three possibilities:
We find the method on how the code is calculated based on the serial of the watch
We find the location, where u-boot stores the variable, if the device is locked or not (EDIT: I would expect that in the Misc partition.)
We just reflash the old bootloader (easiest, but only temporary until next OTA update)
Neuer_User said:
So, we have three possibilities:
We find the location, where u-boot stores the variable, if the device is locked or not (EDIT: I would expect that in the Misc partition.)
Click to expand...
Click to collapse
Drop me stock ota 1.2.11c and 1.2.13
scrubber said:
Drop me stock ota 1.2.11c and 1.2.13
Click to expand...
Click to collapse
You will only need the bootloaders (rest of the OTA is just modified apks). I will send them both (old and new one) to you via PM. It would be necessary to disassemble and understand the new bootloader (the old one does not have any OEM commands and also did not read the serial no at all, instead displayed always a dummy serial).
The serial is stored on the misc partition, so the bootloader now needs to read this partition. That's why I believe they probably stored the lock/unlock flag also there. We just need to know which byte.
Of course, if there were someone with a functioning unlock code, he could dump his misc partition before and after unlocking. That would make it pretty clear
so I now have no way to flash a stable version starting from 1.2.13?
It's safe to update 1.3.2b ? English version
zbuh said:
It's safe to update 1.3.2b ? English version
Click to expand...
Click to collapse
No, also locks bootloader. But there is a good chance that we can unlock or reflash the bootloader, if someone wants to switch firmware later.
I also have this problem. I accidentally updated my Amazfit to the latest version official rom. Now I wanted to upgrade to PACEfied, but the bootloader is locked.
Do you have any ideas how to unlock it?
Hi neur_user will I be losing the interval timer and countdown timer app that I installed in pace 1.3.1m rom if update it to 1.3.2b since you said it is bootloader locked? And can you still install developers app in 1.3.2b?
powerforward said:
Hi neur_user will I be losing the interval timer and countdown timer app that I installed in pace 1.3.1m rom if update it to 1.3.2b since you said it is bootloader locked? And can you still install developers app in 1.3.2b?
Click to expand...
Click to collapse
Instalation of additional apps like those timer apps should still work.
barciol said:
I also have this problem. I accidentally updated my Amazfit to the latest version official rom. Now I wanted to upgrade to PACEfied, but the bootloader is locked.
Do you have any ideas how to unlock it?
Click to expand...
Click to collapse
I have an idea how we can unlock the bootloader. In the weekend I will see if I can post a tutorial.
Well, I don't know what I could gain by flashing PACEified FW on my watch... all I've really been looking for is working notifications from my phone to the watch. I'm coming from wearing a Samsung Gear Live that's now worn-out, and it integrated into my life by bringing notifications to my wrist. The Amazfit was perfect for fitness, runtime, and notifications -- but notifications have never worked despite all my hacking and flashing (originally came with Chinese ROM). My saga so far is detailed here: https://www.reddit.com/r/amazfit/comments/61w4ga/most_notifications_not_coming_through_facebook
I flashed the English ROM to it tonight, and proceeded to OTA it (because newer is better, right?). The update failed as I still had the Chinese recovery on it. When it failed, I decided to try intercepting the update bundle before it rebooted. I succeeded, by kicking it into Fastboot mode using the power-button trick, then I pulled the 1.3.2b update.zip file through the "mod recovery". That file is here: https://mega.nz/#!nIBDhLrR!7nQlWsn-TF4bsMNBSaTOfimY-vo-Z2R3dSavrDp1wsA
I fixed my recovery with help of another thread, and OTA'd again to success - the darn thing took a good solid 10 minutes to run the ~33MB update! The progress bar hung the longest (~2 mins each) near the "w", "c", and at the end of "watch" in the message about not powering off the watch. Rather surprising, and wasn't sure if it hung due to my mods or what it was doing...
Hopefully this helps someone interested in looking into how the bootloader gets locked (IDK if Amazfit expected someone to intercept this, being as it's near impossible to intercept except with a MitM on WiFi), perhaps in exchange for some help with these notifications?
Neuer_User said:
I have an idea how we can unlock the bootloader. In the weekend I will see if I can post a tutorial.
Click to expand...
Click to collapse
I'm stuck in 1.2.13 dev, if u want i can test the unlock
Cracklydisc said:
I'm stuck in 1.2.13 dev, if u want i can test the unlock
Click to expand...
Click to collapse
OK, will prepare it today and send it to you.
Neuer_User said:
OK, will prepare it today and send it to you.
Click to expand...
Click to collapse
I also want test the unlock. Please contact with me
barciol said:
I also want test the unlock. Please contact with me
Click to expand...
Click to collapse
Just to clarify: Technically, it is not "unlocking" the bootloader. It just reflashes the old one (which did not have the locking function). That implies that the "unlocked" bootloader will only stay "unlocked" until you install the next official OTA update (which again flashes the locked bootloader). If you move to PACEfied, then that is ok, as PACEfied certainly does not lock your bootloader.
Hi, I was going to unlock my phone using the Xiaomi Unlock tool, but in the attention section, it says that fingerprint recognition won't be available anymore. Is it true, and if it ever happens, how can I reverse that? how can I re-lock my device? I want to unlock my device to maybe put an AOSP Rom when one comes out or MIUI 10 a little early, but if I lose those features I'll stick with the built-in updater!
Don't worry it just means that it can be bypassed on an unlocked device as it is insecure.
It wil not stop fingerprint/face unlock. Go Ahead.
PocoSteve said:
Hi, I was going to unlock my phone using the Xiaomi Unlock tool, but in the attention section, it says that fingerprint recognition won't be available anymore. Is it true, and if it ever happens, how can I reverse that? how can I re-lock my device? I want to unlock my device to maybe put an AOSP Rom when one comes out or MIUI 10 a little early, but if I lose those features I'll stick with the built-in updater!
Click to expand...
Click to collapse
I've just asked pretty much this same question in another thread (though I was more concerned about the property face unlock). I gather from reading around that the miunlock tool allows you to relock the bootloader.
My follow up question is, if you do this, relock your bootloader, are access to autoupdates and face unlock (if lost) reinstated?
Sorry for (kinda) cross-posting
narora9999 said:
Don't worry it just means that it can be bypassed on an unlocked device as it is insecure.
It wil not stop fingerprint/face unlock. Go Ahead.
Click to expand...
Click to collapse
Are you sure ? because the software literally says
"Fingerprint recognition, Find device, and other security features will no longer be available"
PocoSteve said:
Are you sure ? because the software literally says
"Fingerprint recognition, Find device, and other security features will no longer be available"
Click to expand...
Click to collapse
my phone is unlocked and everything works like normal
bluedragon02 said:
my phone is unlocked and everything works like normal
Click to expand...
Click to collapse
Ok, thanks! Also, when it says "will remove all data" does this mean a factory reset? Is the phone "as new" next time you boot it up?
PocoSteve said:
Ok, thanks! Also, when it says "will remove all data" does this mean a factory reset? Is the phone "as new" next time you boot it up?
Click to expand...
Click to collapse
Yeah i think its like new but now i dont remeber
It will do a factory reset and also wipe internal storage.
Just to confirm what everyone's saying, I just unlocked my bootloader. It did a factory reset, then allowed me to set up face and fingerprint unlock, opt into (or out of) updates and mi services, all as it did at first boot.
Obviously, I don't yet know if it will actually get OTA updates, but time will tell (unless I root in the meantime). Also I forgot to check if mitool allows easy BL relocking and I've turned the pc off now, but everyone says it does
Hello,
After receiving my new Motorola x40 I realized that I wasn't able to use my GooglePay nor did it have other language support. So I decided to unlock my x40 bootloader via https://en-us.support.motorola.com/app/standalone/bootloader/unlock-your- device-a
It all worked. I managed to install a global rom with all the google apps and extra language support.
However, Global rom didn't allow my GooglePlay to use my cards or backup via googleOne since the flashing was unlocked. So I went to fastboot to " fastboot flashing lock". After which my cards were able to work.
After few days of using global rom I decided to go back to chinese one since I found it a bit easier to navigate.
So when I decided to go back to my old chinese rom, in "Developer Options" OEM unlocking says "Connect to the internet or contact your operator" and it is greyed out.
I tried using " fastboot flashing/oem unlock" in fastboot however it tells me that i need to unlock it in " developer options " first.
My phone has already been connected to wifi for around 90 hours on a Global rom And around a week before I transitioned from Chinese room over to global rom.
How long do I need to be connected to the internet or what operator do I need to contact to unlock my OEM again? Or maybe there is another way to unlock OEM without waiting?
Things I tried and failed:
1) Factory reset
2) Wipe/Cache reset via recovery3) "fastboot flashing/oem unlock" via bootloader
Global rom used: https://mirrors.lolinet.com/firmware/motorola/rtwo/official/RETGB/
Have same problem.
cryptm said:
Have same problem.
Click to expand...
Click to collapse
How many days are you in this state? maybe you are closer to 7 days than I am
The toggle to unlock the bootloader is now enabled for me after 8 days. I have the Edge 40 Pro.
mine too, didn't look before, i own mine since 14 april
Ok so the theory is that once you get a global rom and "fastboot oem lock", it will act like new phone and will only unlock after 7-8 days. Guess will have to wait to test this theory out.
zeakey said:
Ok so the theory is that once you get a global rom and "fastboot oem lock", it will act like new phone and will only unlock after 7-8 days. Guess will have to wait to test this theory out.
Click to expand...
Click to collapse
Any update whether you can toggle OEM Unlocking?
Also, as someone who have been using Moto phones from China for years, CN ROM is way way way better the Global ROM when it comes to features and software updates. One useful feature is the built in Motorola Wallet app where I can use my phone as keycard and transpo card.
ijuanp03 said:
Any update whether you can toggle OEM Unlocking?
Also, as someone who have been using Moto phones from China for years, CN ROM is way way way better the Global ROM when it comes to features and software updates. One useful feature is the built in Motorola Wallet app where I can use my phone as keycard and transpo card.
Click to expand...
Click to collapse
Nope. Still not unlocked. Waiting for new firmware updates. So far EU region didn't get any.
zeakey said:
Nope. Still not unlocked. Waiting for new firmware updates. So far EU region didn't get any.
Click to expand...
Click to collapse
Supposedly OTA updates are being released, some can update successfully, others can't. Keep us updated if you're able to successfully update.
JustHereForNow said:
Supposedly OTA updates are being released, some can update successfully, others can't. Keep us updated if you're able to successfully update.
Click to expand...
Click to collapse
I did update from from 20-15 to 20-28 version. OEM still didn't get unlocked
zeakey said:
I did update from from 20-15 to 20-28 version. OEM still didn't get unlocked
Click to expand...
Click to collapse
I'm assuming it's a Motorola issue. I'm assuming maybe even real Edge 40 Pro devices can't unlock yet? Honestly if OTA works and so do all features (banking, 5g, etc) then I have no problem doing the conversion.
zeakey said:
I did update from from 20-15 to 20-28 version. OEM still didn't get unlocked
Click to expand...
Click to collapse
Does this mean you were able to update to 20-28 even with the locked bootloader (and locked OEM)?
Zechosenjuan said:
Does this mean you were able to update to 20-28 even with the locked bootloader (and locked OEM)?
Click to expand...
Click to collapse
I also updated without problem with bootloader closed and oem blocked and everything fine in the same way I solved the vpn and everything at 100 on the computer
ziggmax said:
I also updated without problem with bootloader closed and oem blocked and everything fine in the same way I solved the vpn and everything at 100 on the computer
Click to expand...
Click to collapse
What tools\steps did you take to update while bootloader and OEM are locked?
Zechosenjuan said:
What tools\steps did you take to update while bootloader and OEM are locked?
Click to expand...
Click to collapse
Using TinyFastbootScript flashing the reteu rom But when I installed it I blocked the bootloader thinking that it could be opened again to my surprise I could no longer activate the box so I have to wait and see if with any update I can go back To activate that option To activate that option
ziggmax said:
Using TinyFastbootScript flashing the reteu rom But when I installed it I blocked the bootloader thinking that it could be opened again to my surprise I could no longer activate the box so I have to wait and see if with any update I can go back To activate that option To activate that option
Click to expand...
Click to collapse
You won't be able to unlock the bootloader twice, impossible it's done by design by motorola.
You can only unlock your bootloader once
jody2k said:
You won't be able to unlock the bootloader twice, impossible it's done by design by motorola.
You can only unlock your bootloader once
Click to expand...
Click to collapse
does this mean the phone that went through unlock\lock of the BL will never get a firmware update (whether OTA or manual)?
Zechosenjuan said:
does this mean the phone that went through unlock\lock of the BL will never get a firmware update (whether OTA or manual)?
Click to expand...
Click to collapse
It's possible that we won't get OTA, only will know for sure in the future, i'm in the same situation.
But you can always manually update your firmware with rescue tool or through ADB as long it's the official firmware. You don't need a unlocked bootloader for that
jody2k said:
It's possible that we won't get OTA, only will know for sure in the future, i'm in the same situation.
But you can always manually update your firmware with rescue tool or through ADB as long it's the official firmware. You don't need a unlocked bootloader for that
Click to expand...
Click to collapse
This gives hope. Can you link me to flashing through adb? So far have only seen fastboot and magisk.
Zechosenjuan said:
This gives hope. Can you link me to flashing through adb? So far have only seen fastboot and magisk.
Click to expand...
Click to collapse
I think this method would work:
I screwed up...moto X40 bricked / Any EDL mode available?
Hi guys sadly I completely softbricked my motorola X40 phone i'm a idiot. I flashed to a wrong firmware file (edge 30 pro) and re-locked bootloader then found it phone doesn't properly boot anymore. I can boot it in fastboot mode but flashing in...
forum.xda-developers.com
But I think this will erase all your data so it's not a real "upgrade firmware" method
I also found out there is an "software update" in the lenovo rescue tool
Maybe it's worth the shot to try this out too, but for me it's says I have the latest firmware already (which is correct) so I can't test it out right now.