I Got a new XT1926-7 EVERT from Amazon today.
Did OTA to PPWS29.116-11-13 (Nov.1, 2019 update) , everything stock, no warnings, Google Pay worked fine.
Then unlocked BL and then > Settings > System Update > see "System integrity is compromised..... no longer eligible for software updates"
Then I have re-locked BL with 'fastboot oem lock'.
Still, Settings > System Update > see "System integrity is compromised.....no longer eligible for software updates"
Google Pay is not working
On reboot, warning message: "Your device has loaded a different OS".
BTW, On BL screen, "flashing_locked"
in Developer options, OEM unlocking is set to left (locked)
I have a second identical phone which I flashed to stock EVERT_RETAIL_9.0_PPWS29.116-11-11 and re-locked BL, same result.
So, it looks like there is no way to return to clean stock after BL has been unlocked.
Once you have unlocked the BL you won't get back to the "locked" state, only to "relocked". To solve your problem regarding the updates you have to install Magisk.
WoKoschekk said:
Once you have unlocked the BL you won't get back to the "locked" state, only to "relocked". .
Click to expand...
Click to collapse
and the "relocked" state appears to be not eligible for future OTA updates
You can receive OTA updates in any case, but your FW must be complete stock to install it. It doesn't matter if your BL is unlocked or not.
The info under settings > System updates does not have any effect on it.
Hey there,
I wanna bring up this topic. I used a moto g6 plus for about a half year now with just bootloader unlocked and magisk rooted.
When there was an update I got it installed via Download on Lolinet and flash command no erase found here on xda.
So now I wanna resell the phone again. Of course I will tell the potential buyers about the unlocked bootloader but I wanted to bring it to stock and OTA able again.
So I thougt reflashing the stock downloaded from lolitnet and relocking the bootloader would do the job. Well no.
If the Reteu Version (which is my phone) from Lolinet is not 100% stock, where can I find something to flash on it for doing the job and letting disappear the "Your device has loaded a different OS" prompt?
Thank you out there.
Dennis
Hobbygamer27 said:
Hey there,
I wanna bring up this topic. I used a moto g6 plus for about a half year now with just bootloader unlocked and magisk rooted.
When there was an update I got it installed via Download on Lolinet and flash command no erase found here on xda.
So now I wanna resell the phone again. Of course I will tell the potential buyers about the unlocked bootloader but I wanted to bring it to stock and OTA able again.
So I thougt reflashing the stock downloaded from lolitnet and relocking the bootloader would do the job. Well no.
If the Reteu Version (which is my phone) from Lolinet is not 100% stock, where can I find something to flash on it for doing the job and letting disappear the "Your device has loaded a different OS" prompt?
Thank you out there.
Dennis
Click to expand...
Click to collapse
Lenovo Smart Assistant.
Peace.
Related
Hi all! I tried to flash 5.1 retus on a 5.0.2 retla variant (as the tutorial said it would work on all variants, and both are for XT1527) without unlocking the bootloader.
Sadly it won't boot (boots directly to bootloader) and can't go back to stock.
It says: 'version downgraded for boot' 'failed to validate boot image'
This is a problem because everything I find about it says that I should either unlock the bootloader or find a newer retla ROM to flash over. Sad part is that this version is not coming any soon.
I tried to unlock bootloader afterwards but since I've never checked the option inside Dev Options this is like a no-go.
Any ideas?
I was wondering if the S6 on Vodafone in the UK came with a locked bootloader, and if so how difficult was it to unlock? I have an S7 Edge on pre-order, and presume that would come locked too if the S6 did. I can't live without root. Cheers.
No one has an S6 Edge on Vodafone?
Beefheart said:
I was wondering if the S6 on Vodafone in the UK came with a locked bootloader, and if so how difficult was it to unlock? I have an S7 Edge on pre-order, and presume that would come locked too if the S6 did. I can't live without root. Cheers.
Click to expand...
Click to collapse
Seems so, as I have had the same problem by installing MM 6.0.1 firmware with the UK csc code VOD (appearing as BTU on phone). The bootloader wouldn't let me flash TWRP through ODIN (sorry, could flash, but not boot into TWRP, stuck on bootloader).
So i took the provided MM 6.0.1. bootloader from Carotix CarHDRom, flashed it together with at the same place provided TWRP for
MM (the old 2.8.7.0/2.8.7.1 or even new TWRP 3.0 provided on the homepage of TWRP.me , won't work on MM) throught ODIN.
Within TWRP flashed hybridmax's S5E-AELKernel_MM...kernel 1.5 and superSU beta 2.67 (previosly stored/copied to the mobile device) and rebooted - rooted and all working fine.
Take a look at : http://forum.xda-developers.com/galaxy-s6-edge/development/rom-carhdrom-1-t3111519
coco722 said:
Seems so, as I have had the same problem by installing MM 6.0.1 firmware with the UK csc code VOD (appearing as BTU on phone). The bootloader wouldn't let me flash TWRP through ODIN (sorry, could flash, but not boot into TWRP, stuck on bootloader).
So i took the provided MM 6.0.1. bootloader from Carotix CarHDRom, flashed it together with at the same place provided TWRP for
MM (the old 2.8.7.0/2.8.7.1 or even new TWRP 3.0 provided on the homepage of TWRP.me , won't work on MM) throught ODIN.
Within TWRP flashed hybridmax's S5E-AELKernel_MM...kernel 1.5 and superSU beta 2.67 (previosly stored/copied to the mobile device) and rebooted - rooted and all working fine.
Take a look at : http://forum.xda-developers.com/galaxy-s6-edge/development/rom-carhdrom-1-t3111519
Click to expand...
Click to collapse
Did you have the OEM Unlock toggle in dev options?
Beefheart said:
Did you have the OEM Unlock toggle in dev options?
Click to expand...
Click to collapse
Do not know if or not.
Just flashed first the original VOD 6.0.1 fw and then tried to have a working TWRP recovery, but could't boot into TWRP recover, the original bootloader did not let me... this for, bootloader and twrp from carotix (and eventually his provided kernel and/or rom) , and everything goes fine.
coco722 said:
Do not know if or not.
Just flashed first the original VOD 6.0.1 fw and then tried to have a working TWRP recovery, but could't boot into TWRP recover, the original bootloader did not let me... this for, bootloader and twrp from carotix (and eventually his provided kernel and/or rom) , and everything goes fine.
Click to expand...
Click to collapse
My understanding of a locked bootloader is that you can't flash anything that isn't official, including a replacement bootloader, which you indicate you did successfully. Otherwise Verizon Samsung customers would simply flash a new bootloader over their locked one. Ever TWRP wouldn't have flashed, it would have kicked out an error in Odin as you made the attempt because the bootloader wouldn't have allowed it. It sounds like your attempt at flashing it finished successfully, but just wouldn't boot into it. I'm wondering if this was caused by something other than the bootloader being locked.
Beefheart said:
My understanding of a locked bootloader is that you can't flash anything that isn't official, including a replacement bootloader, which you indicate you did successfully. Otherwise Verizon Samsung customers would simply flash a new bootloader over their locked one. Ever TWRP wouldn't have flashed, it would have kicked out an error in Odin as you made the attempt because the bootloader wouldn't have allowed it. It sounds like your attempt at flashing it finished successfully, but just wouldn't boot into it. I'm wondering if this was caused by something other than the bootloader being locked.
Click to expand...
Click to collapse
All possible. However, sometimes we'll just have to give it a try, by using the information and software available. I do have to mention, that my mobile is/was provider-free (not locked to a specific provider). But even a locked mobile can be handeld to get
in free and unlocked. In such case, this should be done first and after that the upgrade to rooted MM and ROM, etc.
No worries, cheers for the reply. I'll wait until I receive it then simply return it and cancel the contract if it's locked.
Hi, i had the same problem. I flashed TWRP, but i could not boot to TWRP. I found that I also have locked bootloader. No OEM Unlock toggle in dev options.
Login on this site
https://findmymobile.samsung.com/login.do
and try Disable Reactivation lock if you can.
vrzy007 said:
Hi, i had the same problem. I flashed TWRP, but i could not boot to TWRP. I found that I also have locked bootloader. No OEM Unlock toggle in dev options.
Login on this site
https://findmymobile.samsung.com/login.do
and try Disable Reactivation lock if you can.
Click to expand...
Click to collapse
I've not received my phone yet, but this doesn't look good. Were you able to disable the reactivation lock on your S6? Or, alternatively, like coco722, were you able to simply overwrite the bootloader? I'm not concerned with Knox or Vodafone's warranty, as long as I'm able to overcome the locked bootloader and root.
Software up to date issue
HI all, just got this M8 and it is an ATT Version. but I believe it is unlocked because I am using it with cricket.
When trying to update Android Tells me software is up to date ?
Android version 5.0.2
HTC Sense Version 6.0
Software Number 4.28.502.1
HTC SDK API Level
I am pretty sure that ATT has updated to Marshmallow by now / So why can't I update? I am on wifi and 4G/LTE Could it be because I am using a Cricket Sim Card in the Phone ?
I have downloaded the RUU for Marshmallow software version 6.20.502.5. Should I continue with the Manual update ?
I believe this phone was originally purchased from ATT on May of 2016 if it makes any difference , figured I post it. since it could be a newer version of HTC M8.
Also is there a way to back up my current stock rom, without Rooting phone ? Thanks for all your help.
As I cannot root my phone, because when I go into developer option and search for S-off That option is not there and I can't Continue.
My responses below in red font:
ELEVO said:
HI all, just got this M8 and it is an ATT Version. but I believe it is unlocked because I am using it with cricket.
When trying to update Android Tells me software is up to date ?
I am pretty sure that ATT has updated to Marshmallow by now / So why can't I update? I am on wifi and 4G/LTE Could it be because I am using a Cricket Sim Card in the Phone ?
That is correct, the AT&t version (and most US versions) can only OTA update if connected to the proper branded carrier (AT&T in this case). Therefore, the RUU is your best option to update.
I have downloaded the RUU for Marshmallow software version 6.20.502.5. Should I continue with the Manual update ?
You can. But you need to flash the 6.20.502.5 firmware first, before you can flash the RUU. See instructions to flash the firmware here: https://forum.xda-developers.com/showpost.php?p=67123738&postcount=7
Then run the RUU. Keep in mind, that RUU will wipe the phone. So backup your data to an off-phone location (cloud, computer, etc.) before RUU.
Also is there a way to back up my current stock rom, without Rooting phone ? The current Lollipop ROM? No, there will be no way to revert to LP by official means, once you RUU to Marshmallow. I doubt you will find the need or desire to "downgrade" to obsolete LP version. If for some reason you did want to, there are options, but would require unlocking the bootloader (to install custom recovery and flash a Lollipop ROM), or s-off (which would allow you to "downgrade" by RUU - which is not allowed with s-on).
As I cannot root my phone, because when I go into developer option and search for S-off That option is not there and I can't Continue.
You are misunderstanding a couple things:
1) s-off is not a setting in Developer Options. s-off can only be obtained with sunshine app ($25)
2) You don't need s-off to root this device. Simply unlock the bootloader, install TWRP, and flash SuperSU to root
Click to expand...
Click to collapse
Detailed
redpoint73 said:
My responses below in red font:
Click to expand...
Click to collapse
Thanks for the detailed reply, really helpful and greatly appreciated :good:
Two more Questions, Can I upgrade to an official DEV Edition RUU on this ATT Device? or would I have to use a Custom Dev ROM ? as I am trying to Tether with my phone, just like my official Developer HTC M8 I purchased in 2014 , Seems AT&T phone wont allow me to Tether ?
Also once I flash firmware and upgrade to official RUU will need to Unlock and Root Loader? Will doing upgrading to official Marshmallow Relock bootloader and Un Root Phone ? Back to Stock ? Thanks again, I will be attempting this pretty soon. Thanks again
For the Record, I have made a back up of my Lollipop via TWRK. I also backed it up using Titanium back up, just in case.
Again, my responses in red font:
ELEVO said:
Thanks for the detailed reply, really helpful and greatly appreciated :good:
You're welcome. Always happy to help!
Two more Questions, Can I upgrade to an official DEV Edition RUU on this ATT Device?
You can't flash the Dev Edition RUU with s-on. Even though the versions are very similar (same model ID - MID) the two versions have different carrier ID (CID). Wrong carrier ID will make the Dev Ed RUU fail, by definition. And the only way to change CID is with s-off. Further, its not really necessary to flash the Dev Ed RUU (and not worth spending money of s-off) to accomplish what you want (see more below)
or would I have to use a Custom Dev ROM ? as I am trying to Tether with my phone, just like my official Developer HTC M8 I purchased in 2014 , Seems AT&T phone wont allow me to Tether ?
Its correct that the AT&T stock ROM disables tethering. Flashing most custom ROMs (or the Dev Ed ROM) will enable tethering - as well as remove annoying AT&T branding and bloat apps. Flashing the Dev Ed RUU is not necessary to accomplish this.
Also once I flash firmware and upgrade to official RUU will need to Unlock and Root Loader? Will doing upgrading to official Marshmallow Relock bootloader and Un Root Phone ? Back to Stock ? Thanks again, I will be attempting this pretty soon. Thanks again
You need to relock the bootloader in order to flash firmware and RUU (command: fastboot oem lock). Once the RUU is complete, the phone will be on a fully stock "factory" image. So you will be unrooted. You will also be back to stock recovery (no longer have TWRP installed). From there, what you want to do:
1) Unlock the bootloader again. Either use the same unlock bin code you used to unlock BL before. Or get a new code from HTCDev.com
2) Flash TWRP back to the phone with fastboot. TWRP 3.0.2 is recommended for compatibility with MM firmware.
3) Flash the desired custom ROM. The custom ROM will be rooted (if you flash the Dev Ed ROM, you can select root in the AROMA installer).
For the Record, I have made a back up of my Lollipop via TWRK. I also backed it up using Titanium back up, just in case.
Always good to make backups. Although be aware, that RUU will wipe the phone, including internal storage. So if you picked internal storage as your backup location, you'll want to move/copy to another location (removable SD is okay, otherwise to computer or cloud).
Also note that restoring app data (as well as call logs, SMS) using Titanium, after RUU or ROM flash should be okay. But don't restore any system data, as this can cause problems.
Click to expand...
Click to collapse
redpoint73 said:
Again, my responses in red font:
Click to expand...
Click to collapse
Ok i came back to this old post. I forgot all about it, it really is helping me alot.
My questioin is after i Relock the bootloader can i do a factory wipe? will this remove everything from my phone and bring it back to stock?
I relocked my phone, but all my apps and contacts are their.
Bricked ?
ELEVO said:
Ok i came back to this old post. I forgot all about it, it really is helping me alot.
My questioin is after i Relock the bootloader can i do a factory wipe? will this remove everything from my phone and bring it back to stock?
I relocked my phone, but all my apps and contacts are their.
Click to expand...
Click to collapse
I think i may have bricked my phone? I went and installed an RUU firmware file for Marshmallow as most instruct to do via Fastboot. All went well, installation completed and i was able to send command to phone to reboot. when it tried to reboot. white screen with HTC Comes on and then goes almost black with a very light dark grey background.
Phone would not reboot into anything but dark screen. even when i restarted it with power button. the only thing that worked for me, was Holding Down Power/Volume and quickly hit the volume down button before device would vibrate to reboot, that took me into recovery. Below is what i see in Recovery.
Phone now has new software
***RELOCKED***
m8_UL_CA PVT SHIP S-ON
HBOOT-3.1.0.0000
RADIO-4.0 [email protected]
OpenDSP-V56.2.2-00593-M8974_FO.0126
0S-6.20.502.5
eMMC-boot 2048MB
APR 14 2016,19:39:46.0
HBOOT
<Vol UP> to previous item
<Vol Down> to next item
<Power> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
I was able to run and "IMAGE CRC" via boot loader. it gave me alot of numbers after calculating. not sure if that is a good sign ?
Things I've tried in Recovery.
1. Recovery goes back to black screen.
2. SHOW BARCODE Works- 3 bar codes showed up.
3. Fastboot works. but when i try command "adb devices" it says list of devices attached. but nothing shows up
4. Tried to do a factory reset and tries to do it, then a black phone pops up on screen with green arrow sgoing in circles for like 10 seconds. then reboots to dark screen.
Please Help :crying: Thanks
Can anyone help me with this? I bought the phone with me on vacation and now using an HTC Developer Edition that the button down doesn't work and Volume down button us sunk in But at least i have my phone with all my contacts and apps , For now ?
I would like to know if i can unbrick my other HTC . Thanks.
Late in responding, as I was on work travel myself, and not on XDA for over a week.
ELEVO said:
I think i may have bricked my phone?
Click to expand...
Click to collapse
It's basically impossible for you to do anything with an s-on M8 that will actually brick it. That is the good thing about s-on.
ELEVO said:
I went and installed an RUU firmware file for Marshmallow as most instruct to do via Fastboot. All went well, installation completed and i was able to send command to phone to reboot. when it tried to reboot. white screen with HTC Comes on and then goes almost black with a very light dark grey background.
Click to expand...
Click to collapse
I think you only flashed the firmware.zip and not the RUU. Based on the condition here, and your other thread you created here: https://forum.xda-developers.com/htc-one-m8/help/htc-one-e-m8-fastboot-issues-t3757628
I clearly described above to flash the firmware.zip then the RUU. They are 2 completely different things. Firmware is about 80 MB and only contains hboot, radio, and a few other things. RUU is a full image that is 1.5 GB.
No boot after flashing signed firmware is normal, as it expects the RUU to be run afterwards.
ELEVO said:
Fastboot works. but when i try command "adb devices" it says list of devices attached. but nothing shows up
Click to expand...
Click to collapse
adb doesn't work in fastboot mode. Only fastboot commands will work in fastboot mode. You can only use adb when booted to OS (not an option for you, obviously) or alternately in custom recovery TWRP. So what you describe (adb not working) is normal and expected.
However, fastboot is enough to get the phone working from the described condition.
I've done a good bit of scouring here but cannot seem to get a definitive reason or fix to my current issue.
Here's the order of events:
Bought a new N200 unlocked version.
Unlocked bootloader - no issues.
Put TWRP on it - still a WIP so the issues with it were expected. It's minimal and is not fully working. I was aware of this and succeeded at this step as well.
Put Magisk on it. Once again, minimal issues.
Decided to return to stock because it's difficult to update the device.
Removed root. Complete uninstall of magisk.
Used payload dumper to extract the factory boot image. Used the same method to reinstall this to the device.
Booted back to stock recovery. Completely wiped device keeping system intact. Then booted up.
Booted back to fastboot to relock bootloader. ERROR - DEVICE CORRUPT.
Hardware booted back to fastboot and unlocked bootloader. Device works.
New partial update rolls out. Cannot update.
So here's the issue. I cannot relock the bootloader or the device will read as corrupt and not boot up. I also cannot update the device because it states the device is either "busy" or has an "installation problem". I also cannot sideload from recovery because it states the device is unauthorized (weird since the bootloader is still unlocked) and sideload doesn't really seem to work via fastboot either.
Any tips or help that can get me completely back to stock on this unlocked variant would be greatly appreciated.
You'll have to just redo everything msm your device back to factory. Then update to the partial patch. Afterwards you can do the root process.
Winnower Amber said:
You'll have to just redo everything msm your device back to factory. Then update to the partial patch. Afterwards you can do the root process.
Click to expand...
Click to collapse
The problem lies in the MSM part of your reply Winnower. I have the unlocked variant. The tool for that is not available. Not yet, anyways. But I am hopeful I will be getting my hands on that today for the community.
You could use Android studio to piggy back on the update file.
When you relock the bootloader, you have to have correct vbmetas. (Verified boot metadata). When you unlocked, OnePlus automatically disabled them. They may have been cleared (This is the usual way to disable verified boot, by blanking the hashes from the vbmetas.) or they may just not match the current version installed.
You restored to the "full" OTA version from the website, but if you previously took a "patch" OTA update over the network, your existing vbmetas would not match the full OTA version.
Also, keep in mind there are two slots to deal with. The sideload update mechanism checks both copies for modification, and you probably only reverted one.
I've read comments by others that relocking the bootloader is not a requirement for the sideloader to update, but reverting the software is.
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 recovery​3) "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.