Related
I recently purchased a R800 from someone on Craigslist. The phone is already rooted, permanantly I think since it is rooted after doing a factory restore. It is not sim locked, I believe its factory unlocked.
I tried to do the OTA update, which downloads, but fails to install. It appears to get about 3/4 of the way done, reboots and gives me an "update failed" message.
I wanted to unlock the boot loader, I got the unlock key from SE. I must of tried 10 times to get the phone to boot into fastboot mode, it NEVER does it. It simply boots up normally. I even got an app that makes it easy to reboot into restore or fastboot modes (just click an option and it reboots), however just like before the phone simply reboots normally. I even did a factory restore prior to trying the update... no go.
Should I try to remove the root access? Is this what is giving me all the problems. I was able to successfully install root explorer and titanium backup and both of those programs worked fine.
R800i, Android 2.3.3, Kernel 2.6.32.9-perf [email protected] #1, Build number 3.0.1.A.0.145
Edit: Title should be "Can not OTA or enter fastboot mode, root problems?"
Is your phone sim locked? Sim locked phones need to be unlocked before able to unlock bootloader or fast load. After you unlock bootloader make sure you never ota update.
Sent from my XPlay using XDA App.
Your phone has a locked bootloader and a factory lockout on fastboot.
Best advice to you is flash the r800a world generic 2.3.2 root it with gingerbreak then ota update. Use a program called wontanserver as its super easy.
Dont get anyone to remove your factory locks on fastboot until you read tons of threads on these fourms from the last couple months.
Ok, lets see....
Deoxlar said:
"Is your phone sim locked? Sim locked phones need to be unlocked before able to unlock bootloader or fast load. After you unlock bootloader make sure you never ota update."
Click to expand...
Click to collapse
My phone is the R800a. It was my understanding that this phone was never locked (factory unlocked). It came in an official Sony Ericsson box and has no carrier branding on it what-so-ever. It was not purchased through a carrier. It does have a weird stock data APN called "Telekila"?!?!?
sdlaurin said:
"Your phone has a locked bootloader and a factory lockout on fastboot.
Best advice to you is flash the r800a world generic 2.3.2 root it with gingerbreak then ota update. Use a program called wontanserver as its super easy.
Dont get anyone to remove your factory locks on fastboot until you read tons of threads on these fourms from the last couple months."
Click to expand...
Click to collapse
Doesn't wontonserver require credits to run? How expensive does this get?
I didn't know the phone could have a factory lock on the bootloader. I did go to the SE website where you get the unlock key and it was successful in giving me a key... Well I shouldn't exactly say "successful", it did give me a key code to use if and when I can unlock the bootloader, weather or not that code is actually legit remains to be seen. I'm a bit skeptical now since you said the phone is bootloader locked from the factory. I though SE was allowing their phones to be unlocked. I recently unlocked my Motorola Atrix and was expecting to do the same with this phone.
Thank you guys for the advice. I love this phone so far but I can't wait to get a custom rom on it
It uses credits but they are free.
There are currently 2 gentlemen on these forums that can remove your fastboot locks and unlock your bootloader.
Have a look for thier threads on this matter
I would like to have this done now, so gentlemen, whomever is able to do this please message me and we can work something out. Im dieing to get a new rom on this awesome phone/game console.
Sent from my R800i using xda premium
If you need help with unlocking your phone contact Alejandrissimo he does Unlocks
I flashed the r800a world generic 2.3.2 rooted it with gingerbreak then ota updated.I get the same thing as DMpire , reboots and gives me an "update failed" message.
Is this because I removed some of the stock apps that came on the phone after it was rooted? Anyone know about this?
Does it matter if the SD card is mounted or not?
Removing stock apps then trying to ota isnt going to happen. Reflash, root, ota, then remove your stock apps
Is there any easy way to do this? can I reflash it as it has a locked bootloader, or do I have to get the bootloader unlocked?
JDMpire said:
I would like to have this done now, so gentlemen, whomever is able to do this please message me and we can work something out. Im dieing to get a new rom on this awesome phone/game console.
Sent from my R800i using xda premium
Click to expand...
Click to collapse
Christian6809 said:
Is there any easy way to do this? can I reflash it as it has a locked bootloader, or do I have to get the bootloader unlocked?
Click to expand...
Click to collapse
Add me to gtalk pals: alejandrissimo[at]gmail.com
Google wontanserver its free
Hello, I purchased a Pixel 3 XL off craigslist and it is working fine, but the bootloader is unlocked therefore I am receiving a warning when restarting the phone and Google Pay does not work. How can I re-lock the bootloader? Do I need to flash the latest standard google image? The build number is: "crosshatch-userdebug 9 PQ1A.181105.013 5027108 dev-keys". When in bootloader the bootloader version is: b1c1-0.1-5004167. Obviously a n00b here, please be gentle. Thank you for any help.
Do you have a computer? If so what OS do you use?
Sent from my Pixel 3 XL using Tapatalk
superchilpil said:
Do you have a computer? If so what OS do you use?
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
I do have a computer, a Windows 10 Pro
Are you planning on rooting? If so, you can use Magisk Hide (after using Magisk to root of course) to get Google Pay to work. I would be hesitant to re-lock the BL unless you are certain that it is completely stock otherwise. Re-locking a modified phone can brick the device. Better to just learn how to root, etc and keep it unlocked. You have come to the right place to learn.
sliding_billy said:
Are you planning on rooting? If so, you can use Magisk Hide (after using Magisk to root of course) to get Google Pay to work. I would be hesitant to re-lock the BL unless you are certain that it is completely stock otherwise. Re-locking a modified phone can brick the device. Better to just learn how to root, etc and keep it unlocked. You have come to the right place to learn.
Click to expand...
Click to collapse
No, I don't plan on rooting. But I am afraid of bricking the phone since I don't know what has been done to it. Is there a way to determine what was done to unlock the bootloader? Otherwise I will follow your recommendation of using Magisk Hide. I would prefer to keep the phone stock. Thanks.
eec007 said:
No, I don't plan on rooting. But I am afraid of bricking the phone since I don't know what has been done to it. Is there a way to determine what was done to unlock the bootloader? Otherwise I will follow your recommendation of using Magisk Hide. I would prefer to keep the phone stock. Thanks.
Click to expand...
Click to collapse
If you live in Denver I'll trade you my Verizon one for yours. It has a locked bootloader.
eec007 said:
No, I don't plan on rooting. But I am afraid of bricking the phone since I don't know what has been done to it. Is there a way to determine what was done to unlock the bootloader? Otherwise I will follow your recommendation of using Magisk Hide. I would prefer to keep the phone stock. Thanks.
Click to expand...
Click to collapse
The two obvious things you can check are that you have stock recovery and that the phone is not rooted. Manually power on to bootloader (hold volume down and press power then use the volume keys to select recovery and press power. you should get a no command android screen if in stock recovery. assuming you don't have a Magisk icon, you are probably not rooted but you can confirm by installing and running a root app like root checker. likely, the previous owner did nothing but unlock the BL given how recently it came out, but if someone where really creative they could have done work in the other partition. there are no exploites, so doing it normally (running fastboot flashing unlock from a prompt) is pretty much all that would have been done other than enabling developer options and OEM unlocking in settings.
Personally, I think you have a good chance to learn your device, root (you need to be rooted for Magisk hide) and keep the bootloader unlocked. Besides rooting, being able to install a full factory image instead of an OTA is so much better in my opinion. The amount of work it would take to be 100% confident that the only thing done was the BL unlock would take as much work as at least getting a working knowledge of rooting and reinstalling the OS.
P.S. Keeping a phone "stock and rooted" has advantages. That is how I run my 3 XL and how I ran my OG XL. No custom OS. Not even a kernel.
coolhandz said:
If you live in Denver I'll trade you my Verizon one for yours. It has a locked bootloader.
Click to expand...
Click to collapse
lol, what I don't get is that I thought the google edition could have the bootloader unlocked in the developer options. So why go to this hassle of unlocking the bootloader from fastboot? FYI, in the Developer options the OEM unlocking is greyed out and says "Bootloader is already unlocked".
sliding_billy said:
The two obvious things you can check are that you have stock recovery and that the phone is not rooted. Manually power on to bootloader (hold volume down and press power then use the volume keys to select recovery and press power. you should get a no command android screen if in stock recovery. assuming you don't have a Magisk icon, you are probably not rooted but you can confirm by installing and running a root app like root checker. likely, the previous owner did nothing but unlock the BL given how recently it came out, but if someone where really creative they could have done work in the other partition. there are no exploites, so doing it normally (running fastboot flashing unlock from a prompt) is pretty much all that would have been done other than enabling developer options and OEM unlocking in settings.
Personally, I think you have a good chance to learn your device, root (you need to be rooted for Magisk hide) and keep the bootloader unlocked. Besides rooting, being able to install a full factory image instead of an OTA is so much better in my opinion. The amount of work it would take to be 100% confident that the only thing done was the BL unlock would take as much work as at least getting a working knowledge of rooting and reinstalling the OS.
P.S. Keeping a phone "stock and rooted" has advantages. That is how I run my 3 XL and how I ran my OG XL. No custom OS. Not even a kernel.
Click to expand...
Click to collapse
Thank you! Root Checker says that "root access is not properly installed on this device". The recovery mode screen just has a warning about the bootloader is unlocked and a link to a google help page. I figure that I can always unlock the bootloader again if I need to later, but for now I just want everything to work (bank and pay app) and not worry about updating anything myself. I think I may try fastboot to lock the bootloader for now. Thanks for all the help.
Hope it all works out for you. I assume you did a factory reset on the device since you got it used. Re-locking will do another factory reset.
sliding_billy said:
Hope it all works out for you. I assume you did a factory reset on the device since you got it used. Re-locking will do another factory reset.
Click to expand...
Click to collapse
Yeah, so I locked using "fastboot flashing lock" but then it doesn't start, saying that there is no operating system or something like that. I freaked out and was able to unlock again using "fastboot flashing unlock". Now all is wiped. I guess I need to flash the oem rom first, then lock. I'll have to do this all later tonight. Just glad that I didn't brick it yet.
eec007 said:
Thank you! Root Checker says that "root access is not properly installed on this device". The recovery mode screen just has a warning about the bootloader is unlocked and a link to a google help page. I figure that I can always unlock the bootloader again if I need to later, but for now I just want everything to work (bank and pay app) and not worry about updating anything myself. I think I may try fastboot to lock the bootloader for now. Thanks for all the help.
Click to expand...
Click to collapse
I haven't rooted or bl unlocked in some time now so if I make a mistake someone please correct me. After buying it from a 3rd party I'd wipe the device entirely. Download the correct image and install the latest platform tools for Windows (here) https://developer.android.com/studio/releases/platform-tools and make sure you can connect with adb devices and fastboot devices commands. Then extract the latest full image from here https://developers.google.com/android/images to your platform-tools directory and run the flashall.bat command if you wish to wipe the entire device and get rid of anything the previous owner might have "inadvertently" installed. (this is what I would do but not necessarily what you should do if you want to keep the current apps and system intact) This will reset your device and then you can lock the bootloader with no worry and you'll have a stock system.
I agree that since you can unlock it at any time and you don't need it now then relock it. But there are those here that disagree with me and fight with Magisk and OTAs constantly. But they are not noobs and know what they're doing. If you want to learn there is a wealth of information here so it's your call. Just my 2 cents. But please check my steps before you do anything that might cause issues.
edit: darn, sorry I just saw above that you already tried to lock it. I hope what I said to do will get you out of the predicament.
bobby janow said:
I haven't rooted or bl unlocked in some time now so if I make a mistake someone please correct me. After buying it from a 3rd party I'd wipe the device entirely. Download the correct image and install the latest platform tools for Windows (here) https://developer.android.com/studio/releases/platform-tools and make sure you can connect with adb devices and fastboot devices commands. Then extract the latest full image from here https://developers.google.com/android/images to your platform-tools directory and run the flashall.bat command if you wish to wipe the entire device and get rid of anything the previous owner might have "inadvertently" installed. (this is what I would do but not necessarily what you should do if you want to keep the current apps and system intact) This will reset your device and then you can lock the bootloader with no worry and you'll have a stock system.
I agree that since you can unlock it at any time and you don't need it now then relock it. But there are those here that disagree with me and fight with Magisk and OTAs constantly. But they are not noobs and know what they're doing. If you want to learn there is a wealth of information here so it's your call. Just my 2 cents. But please check my steps before you do anything that might cause issues.
edit: darn, sorry I just saw above that you already tried to lock it. I hope what I said to do will get you out of the predicament.
Click to expand...
Click to collapse
Your steps are basically what I will try tonight. Currently the phone is working again, so there was no harm done yet (just the restore of all apps and such). But I'm going to flash the oem image tonight and start all over again.
eec007 said:
Your steps are basically what I will try tonight. Currently the phone is working again, so there was no harm done yet (just the restore of all apps and such). But I'm going to flash the oem image tonight and start all over again.
Click to expand...
Click to collapse
One thing I would do before I relocked the bl would be to do the full login procedure, email everything other than apps. Then make sure you're on the Nov update in about phone, I'm sure you will be, and then fastboot relock the bl with the proper command. It will wipe the device again but it's a small price to pay for about 10 minutes of work. Then once it reboots and there is no more error message you'll be fully stock. Enable dev options again and make sure the oem switch is active allowing bl unlock. Then you're done. I've gotten to the point on my 5X where I even flip the oem switch so it can't be bl unlocked until I go in and flip it back. Dangerous if you're flashing stuff but not so much if you're just taking OTAs. That's of course your call entirely. Good luck.
eec007 said:
lol, what I don't get is that I thought the google edition could have the bootloader unlocked in the developer options. So why go to this hassle of unlocking the bootloader from fastboot? FYI, in the Developer options the OEM unlocking is greyed out and says "Bootloader is already unlocked".
Click to expand...
Click to collapse
That will stay grayed out until you relock the bootloader. That slider "allows" unlocking. Then you boot into fastboot and unlock it.
So you would reverse the process, hit fastboot and relock the bootloader. Then you can toggle the slider back to not allow unlocking.
Relocking the bootloader will wipe your phone.
You should not do this until you first flash the full factory image to make sure the phone is 100 percent stock. And if it were my phone I would wait for the next OTA update after flashing it back to stock to make sure it goes ok. Then lock it.
And then I would wait awhile before hitting the slider.
You are playing with fire here, if you mess it up and lock it and hit the slider you will not be able to fix it. And no offense, but since you have not done this all before on this phone chances are good you will mess it up.
So, flash to stock and leave it unlocked.
Then wait for the next OTA.
Then lock it.
Then wait a bit more before you hit the slider.
And remember, since you are not the original buyer you will not be able to warranty it.
eec007 said:
Hello, I purchased a Pixel 3 XL off craigslist and it is working fine, but the bootloader is unlocked therefore I am receiving a warning when restarting the phone and Google Pay does not work. How can I re-lock the bootloader? Do I need to flash the latest standard google image? The build number is: "crosshatch-userdebug 9 PQ1A.181105.013 5027108 dev-keys". When in bootloader the bootloader version is: b1c1-0.1-5004167. Obviously a n00b here, please be gentle. Thank you for any help.
Click to expand...
Click to collapse
They're right to mention that relocking a modified device can result in a brick.
Your best bet is to go to https://developers.google.com/android/images#taimen
Follow the directions to the "T", then relock it if you are really really sure that the unlock screen bothers you.
Would suggest to do this anyway, no matter future unlock status.
TonikJDK said:
That will stay grayed out until you relock the bootloader. That slider "allows" unlocking. Then you boot into fastboot and unlock it.
So you would reverse the process, hit fastboot and relock the bootloader. Then you can toggle the slider back to not allow unlocking.
Relocking the bootloader will wipe your phone.
You should not do this until you first flash the full factory image to make sure the phone is 100 percent stock. And if it were my phone I would wait for the next OTA update after flashing it back to stock to make sure it goes ok. Then lock it.
And then I would wait awhile before hitting the slider.
You are playing with fire here, if you mess it up and lock it and hit the slider you will not be able to fix it. And no offense, but since you have not done this all before on this phone chances are good you will mess it up.
So, flash to stock and leave it unlocked.
Then wait for the next OTA.
Then lock it.
Then wait a bit more before you hit the slider.
And remember, since you are not the original buyer you will not be able to warranty it.
Click to expand...
Click to collapse
I agree with most of your post other than waiting for the next OTA before you lock the bootloader. Why would he need to do that? If he's stock, and he'll see that immediately, then relock it. He doesn't want root or Magisk but only wants banking and Pay. With the slider allowing bl unlock he's in no danger whatsoever. Lock and relock whenever he wants. OTA will not disallow the slider once it's set.
TonikJDK said:
That will stay grayed out until you relock the bootloader. That slider "allows" unlocking. Then you boot into fastboot and unlock it.
So you would reverse the process, hit fastboot and relock the bootloader. Then you can toggle the slider back to not allow unlocking.
Relocking the bootloader will wipe your phone.
You should not do this until you first flash the full factory image to make sure the phone is 100 percent stock. And if it were my phone I would wait for the next OTA update after flashing it back to stock to make sure it goes ok. Then lock it.
And then I would wait awhile before hitting the slider.
You are playing with fire here, if you mess it up and lock it and hit the slider you will not be able to fix it. And no offense, but since you have not done this all before on this phone chances are good you will mess it up.
So, flash to stock and leave it unlocked.
Then wait for the next OTA.
Then lock it.
Then wait a bit more before you hit the slider.
And remember, since you are not the original buyer you will not be able to warranty it.
Click to expand...
Click to collapse
Thank you for explaining this. I had thought that the Developer Option slider was to unlock the bootloader, but your explanation clarifies it, the slider is to allow the bootloader to be unlocked...
Ok, so I tried to flash the factory image using adb flash-all and it keeps getting the error:
Sending sparse 'vendor_a' 2/2 (193888 KB) FAILED (Error reading sparse file)
Now the phone is not working at all and says that "device is corrupt" and will not boot past the white google screen. I can try again using adb, but it is the same error each time. I tried to download the image again and same sparse error. I can also fastboot in TWRP, but not sure what to do in there. What am I doing wrong? I guess I should've rooted and used Magisk like others have said.
turns out changing to a different cable resolved my sparse error and I was then successfully able to apply the factory image and lock the device. Thanks everyone for the help.
I am on the official Android 10 firmware and would like to downgrade back to Pie. Is this possible without unlocking the bootloader? The T-Mobile unlock app apparently don't work on 10 yet so I need to get back to Pie to unlock then I can go back to 10.
Yes, I think you can. You can sideload an OTA image without unlocking the bootloader. Even though it says OTA, it is a full factory image. The files and directions are both available at that link. If possible, I would certainly do a full factory reset of your phone as soon as it booted however. You never want to back into an older version of Android without doing a full factory reset.
sic0048 said:
Yes, I think you can. You can sideload an OTA image without unlocking the bootloader. Even though it says OTA, it is a full factory image. The files and directions are both available at that link. If possible, I would certainly do a full factory reset of your phone as soon as it booted however. You never want to back into an older version of Android without doing a full factory reset.
Click to expand...
Click to collapse
Ok, I just tried that and part way through installation it aborted. "E:Failed to verify package compatibility" along with some other errors...
To revert to pie you have to use the full image and the platform tools available over at Goog but for this you need to unlock the bootloader. If you want to stay on a locked bootloader you then lock it after you're up on stock pie again. Keep in mind you'll want to do the works before you move any data back to the phone and that unlocking the bootloader will wipe the phone so you'll need to back up everything before you unlock.There are specific instructions for all of that and the images and tools at https://developers.google.com/android/images
Don't be afraid of unlocking the bootloader, it can be unlocked and locked again at your whim over and over. Doesn't hurt anything other than you get a wipe in the process.
krabman said:
To revert to pie you have to use the full image and the platform tools available over at Goog but for this you need to unlock the bootloader. If you want to stay on a locked bootloader you then lock it after you're up on stock pie again. Keep in mind you'll want to do the works before you move any data back to the phone and that unlocking the bootloader will wipe the phone so you'll need to back up everything before you unlock.There are specific instructions for all of that and the images and tools at https://developers.google.com/android/images
Don't be afraid of unlocking the bootloader, it can be unlocked and locked again at your whim over and over. Doesn't hurt anything other than you get a wipe in the process.
Click to expand...
Click to collapse
I cant unlock the boot loader because the phone is SIM locked to T-Mobile. This is the whole reason I want to go back to Pie so the unlock app will work. This sucks
You can get it sim unlocked by phone if you meet their unlock requirements, or at least you used to be able to do so, I did it that way there myself a few years ago. If that's not the case anymore then... yeah, you're in a pretty sucky spot.
krabman said:
You can get it sim unlocked by phone if you meet their unlock requirements, or at least you used to be able to do so, I did it that way there myself a few years ago. If that's not the case anymore then... yeah, you're in a pretty sucky spot.
Click to expand...
Click to collapse
I do meet their unlock requirements..They have a ticket open with engineering for over a week but I’ve found out from other means that the unlock app isn’t compatible with Android 10.
Do you mean there’s another way to SIM unlock then the app? If so please enlighten me.
"You can get it sim unlocked by phone..." You call them on the good old fashioned telephone and tell them you want to remove the sim lock. Customer service can do it without the app, to my knowledge this was possible as recently as the 6T; Tmo guys were calling up and getting it done in essentially the same scenario you're in.
So Moto One Action keeps on surprising every now and then. The latest addition to it is the System Integrity is Compromised message. This is how I end up doing so:
https://photos.app.goo.gl/8Q5xZXTzGWGVMZX48
Unlocked the device's bootloader.
Rooted the device successfully using Magisk patched boot image and Moto One Vision's vbmeta file.
Then I had to unroot my device (for some reason), so flashed the stock firmware using Moto Smart Assistant Tool. But kept the device's bootloader in an unlocked state.
Now I have a stock ROM on my device, unrooted without any modification to the /system partition. The only modification is the unlocked bootloader.
Then I went to System > Advanced > System Updates and then got greeted with the message that I am no longer eligible for software updates. Although not an issue as I could still flash the stock firmware by one way or the other, I am just curious to know whether it is indeed a result of an unlocked bootloader or not. All the users who have unlocked their bootloader kindly let me know in the comments whether they have the same message or not. Thanks in advance
binary**# said:
So Moto One Action keeps on surprising every now and then. The latest addition to it is the System Integrity is Compromised message. This is how I end up doing so:
https://photos.app.goo.gl/8Q5xZXTzGWGVMZX48
Unlocked the device's bootloader.
Rooted the device successfully using Magisk patched boot image and Moto One Vision's vbmeta file.
Then I had to unroot my device (for some reason), so flashed the stock firmware using Moto Smart Assistant Tool. But kept the device's bootloader in an unlocked state.
Now I have a stock ROM on my device, unrooted without any modification to the /system partition. The only modification is the unlocked bootloader.
Then I went to System > Advanced > System Updates and then got greeted with the message that I am no longer eligible for software updates. Although not an issue as I could still flash the stock firmware by one way or the other, I am just curious to know whether it is indeed a result of an unlocked bootloader or not. All the users who have unlocked their bootloader kindly let me know in the comments whether they have the same message or not. Thanks in advance
Click to expand...
Click to collapse
Yeah you need locked bootloader for OTA. Same on One Vision.
Magisk will hide the unlocked status while you're rooted so that you can check for OTA, but I believe it will fail to install during update. Never tyried but that's how it is on Motorola One and One Power.
fastboot flash if you're unlocked and want to update.
Hey, sorry if I am wrong but I highly doubt this claim of yours: "you need a locked bootloader for OTA". True to my knowledge, I don't think any OEM really blocks OTA on an unlocked bootloader device. Until we modify system files, we are safe to get OTA updates. That's what I always knew and every time it stood correct. Isn't it?
binary**# said:
Hey, sorry if I am wrong but I highly doubt this claim of yours: "you need a locked bootloader for OTA". True to my knowledge, I don't think any OEM really blocks OTA on an unlocked bootloader device. Until we modify system files, we are safe to get OTA updates. That's what I always knew and every time it stood correct. Isn't it?
Click to expand...
Click to collapse
I don't know about all oem's but I believe samsung blocks ota if bootloader is unlocked.
I read somewhere in G7 forum that Moto support had told that OTA is disabled on that device if you're on unlocked bootloader, so I guess Moto changed their policy about that too.
tys0n said:
Yeah you need locked bootloader for OTA. Same on One Vision.
Magisk will hide the unlocked status while you're rooted so that you can check for OTA, but I believe it will fail to install during update. Never tyried but that's how it is on Motorola One and One Power.
fastboot flash if you're unlocked and want to update.
Click to expand...
Click to collapse
tys0n said:
I don't know about all oem's but I believe samsung blocks ota if bootloader is unlocked.
I read somewhere in G7 forum that Moto support had told that OTA is disabled on that device if you're on unlocked bootloader, so I guess Moto changed their policy about that too.
Click to expand...
Click to collapse
Not sure about Samsung, but was going through Motorola's official blog, and this is what they have to say:
"Unlocking your bootloader does not affect your eligibility to receive over-the-air (OTA) upgrades from Motorola."
Anyways, thanks for your inputs.....
binary**# said:
Not sure about Samsung, but was going through Motorola's official blog, and this is what they have to say:
"Unlocking your bootloader does not affect your eligibility to receive over-the-air (OTA) upgrades from Motorola."
Anyways, thanks for your inputs.....
Click to expand...
Click to collapse
Oh I see. I don't know then.
You could ask here:
https://forums.lenovo.com/t5/motorola-one-action/bd-p/motorola_one_action_en
They should be able to give a proper answer.
I got a XT2013-4 US - Unlocked boot loader, but the root method doesn't work for the US Firmware (Hear the EU Firmware works for someone in Canada) but I am unable to check for updates being fully stock, unrooted, and only an unlocked bootloader so yes if the OS can read that the bootloader is unlocked then it won't let you check for updates (At least on the US Firmware) but then we aren't Android One though on the XT2013-4
If you are on Stock Firmware, unrooted but your Bootloader is Unlocked, you'll not get any OTA despite the Motorola Support page you've posted (It might be old information, just look the phone they used on the top).
Is it possible to relock it?
ReConfirmed: Official OTA Updates is possible after Unlocked Bootloader.
Just to reiterate the facts (in response to #2 and #8), I guess my assumption was well and truly correct. This is because I did end up receiving an OFFICIAL OTA update from Motorola, a few days back. And at this point, my BOOTLOADER IS STILL UNLOCKED! The first image attached below shows the OTA update notification as well as the proof that my Bootloader is unlocked. The second one provides details about that OTA.
binary**# said:
Just to reiterate the facts (in response to #2 and #8), I guess my assumption was well and truly correct. This is because I did end up receiving an OFFICIAL OTA update from Motorola, a few days back. And at this point, my BOOTLOADER IS STILL UNLOCKED! The first image attached below shows the OTA update notification as well as the proof that my Bootloader is unlocked. The second one provides details about that OTA.
Click to expand...
Click to collapse
Rooted with Magisk? That would explain why OTA would work. It tries to hide the unlock/root status.
tys0n said:
Rooted with Magisk? That would explain why OTA would work. It tries to hide the unlock/root status.
Click to expand...
Click to collapse
No, my device isn't rooted. The only modification is the unlocked bootloader. I did this when I saw enrolled users getting beta Android 10 updates for Moto One Power. Since One Action has released almost a year after Power, I thought the soak test would just be around the corner for our device as well. But here we are with One Power receiving Stable Android 10 update, and there is no news of the same for our device. I have got myself enrolled in the MFN and just keeping my fingers crossed.
binary**# said:
No, my device isn't rooted. The only modification is the unlocked bootloader.
Click to expand...
Click to collapse
Ok, thanks. That's intresting.
tys0n said:
Rooted with Magisk? That would explain why OTA would work. It tries to hide the unlock/root status.
Click to expand...
Click to collapse
One more doubt. I tried the root hide via Magisk for some apps like Google Pay or Pokemon Go and it worked pretty well. But could it trick OEMs as well into thinking the device is unrooted, so that the device may receive OTA updates? I guess probably not, but need some more weight on this opinion.
It's possible to relock the bootloader and get ota functionality back.. just use 'fastboot oem lock' command and then reflash the original firmware..
aditya7286 said:
It's possible to relock the bootloader and get ota functionality back.. just use 'fastboot oem lock' command and then reflash the original firmware..
Click to expand...
Click to collapse
Bootloader Locking/Unlocking has nothing to do while receiving OTAs. As I have mentioned in my other post, I have already received Android 10 OTA on an unlocked bootloader. And as far as the response to my own question goes, it was regarding whether one could hide root from the system as we do for Google Pay and get OTAs. The answer is nopes. I tried hiding root from all the necessary files related to Motorola's system OTA via Magisk but didn't get the update. As soon as I unrooted, BOOM the Android 10 update was right there!
Anyways thanks for your response
Unlocking bootloader on its own does not lead to that message. So I'm guessing it's probably something specific to that ROM, or....something else entirely.
arsradu said:
Unlocking bootloader on its own does not lead to that message. So I'm guessing it's probably something specific to that ROM, or....something else entirely.
Click to expand...
Click to collapse
binary**# said:
Bootloader Locking/Unlocking has nothing to do while receiving OTAs. As I have mentioned in my other post, I have already received Android 10 OTA on an unlocked bootloader. And as far as the response to my own question goes, it was regarding whether one could hide root from the system as we do for Google Pay and get OTAs. The answer is nopes. I tried hiding root from all the necessary files related to Motorola's system OTA via Magisk but didn't get the update. As soon as I unrooted, BOOM the Android 10 update was right there!
Anyways thanks for your response
Click to expand...
Click to collapse
I am getting same thing on my moto g8 plus. just flashed omni and now when i returned the device shows this message.
methuselah said:
I am getting same thing on my moto g8 plus. just flashed omni and now when i returned the device shows this message.
Click to expand...
Click to collapse
You mean "System Integrity Compromised" or something else?
Omni, if we're talking about OmniROM, is a custom, pre-rooted ROM, right? So...maybe that's why.
Interesting though that people with stock ROM, who only unlocked the bootloader (no root) are getting the same message.
Personally, I never rooted this phone and I'm not planning to. Also never seen that message on my phone. However, it was bootloader unlocked and now it's back to locked again.
So... For custom ROMs I can understand why it would show you this. For stock ROM with no root, that doesn't make much sense to me. But maybe I'm missing something.
Sent from my motorola one action using Tapatalk
arsradu said:
You mean "System Integrity Compromised" or something else?
Omni, if we're talking about OmniROM, is a custom, pre-rooted ROM, right? So...maybe that's why.
Interesting though that people with stock ROM, who only unlocked the bootloader (no root) are getting the same message.
Personally, I never rooted this phone and I'm not planning to. Also never seen that message on my phone. However, it was bootloader unlocked and now it's back to locked again.
So... For custom ROMs I can understand why it would show you this. For stock ROM with no root, that doesn't make much sense to me. But maybe I'm missing something.
Sent from my motorola one action using Tapatalk
Click to expand...
Click to collapse
The issue in brief.
Well the thing is i have again flashed back stock that with blankflash file. Before april update i had locked bootloader. But now nothing is happening. As soon as i flash stock ROM(clean stock) and relock the bootloader, the phone just says it is corrupted. But at the same time when i unlock the boot loader it boots.
Hello everyone. I installed the developer preview for Android R and i'm over it. I wanna go back to stock and I tried sideloading the OTA image and I get this message
update package is older than the current build. Downgrade not allowed.
My bootloader is locked so I can't flash the image through fastboot. I need help.
May update released might want to try that one.
hedgehogmd said:
May update released might want to try that one.
Click to expand...
Click to collapse
I tried but it didn't work.
I was on the phone with t-mobile to see if they could unlock my phone but we're having issues with the unlock app.
I miss the days of typing in a code and getting your phone unlocked.
As you have just learned, the developer previews are not the same as beta releases. With the beta releases, you can "quit" the beta program and have the old OS version reinstalled via an OTA update The preview releases have no such OTA reset ability. Therefore, you should not participate in the preview releases unless your phone is unlocked.
If the May release doesn't let you revert back, then I think the only option you will have is to wait until the beta is released. Join the beta and have it installed on your phone and then quit the beat and hope that the OTA update takes you back to stock Android 10. In theory I think it will.
you should use the flashall.bat script if you're installing the factory image. Though this will earase data. Just make sure you have USB debugging on
EDIT: I think you should still be able to unlock your bootloader
EDIT2: After reading a bit more I see that on carrier specific devices, OEM unlocking is greyed out until the phone is sim unlocked. But after you get the app working everything should work fine. Did you use another sim thats not from T Mobile?
RicardoSal24 said:
you should use the flashall.bat script if you're installing the factory image. Though this will earase data. Just make sure you have USB debugging on
EDIT: I think you should still be able to unlock your bootloader
EDIT2: After reading a bit more I see that on carrier specific devices, OEM unlocking is greyed out until the phone is sim unlocked. But after you get the app working everything should work fine. Did you use another sim thats not from T Mobile?
Click to expand...
Click to collapse
I put a different sim on the phone and it worked but it's b/c I did the temporary unlock. After 30 days the phone will be locked again. The phone won't let me unlock the bootloader unless it's a permanent unlock. The problem is I'll have to wait 30 days for the phone to re-lock. I wish t-mobile could just give me a code...
Lucky for me this phone isn't my daily driver but I wanted to revert to stock android b/c I got an invite to test out the Ratio launcher by Blloc. It's incompatible with Android R.
chivamex10 said:
I put a different sim on the phone and it worked but it's b/c I did the temporary unlock. After 30 days the phone will be locked again. The phone won't let me unlock the bootloader unless it's a permanent unlock. The problem is I'll have to wait 30 days for the phone to re-lock. I wish t-mobile could just give me a code...
Lucky for me this phone isn't my daily driver but I wanted to revert to stock android b/c I got an invite to test out the Ratio launcher by Blloc. It's incompatible with Android R.
Click to expand...
Click to collapse
Your best bet would be to just wait until you can permanently unlock it. I got mine from best buy and only recently did I bother with flashing roms on it.
I have a TMO device and had a temp unlock, and obviously it doesn't allow oem unlocking to be enabled. I DM'd TMOhelp on twitter and was able to get a permanent unlock there. They told me that I'd have to wait for my temp unlock to expire before I could perm unlock, but I didn't. If you have trouble with the app, just clear the storage and cache data for it. Once it is actually perm unlocked you'll immediately get a notification and be prompted to restart the phone. After that you should see oem unlocking enabled in dev options and be able to hit bootloader and unlock it.