I currently am using my V10 on at&t.
When I first got the phone I did the temporary unlock so I could use the phone out of the box until I was eligible for a "Permanent Unlock".
I used the permanent unlock and it was successful.
After the allotted time for the temporary unlock ran out, T-Mobile locked my phone again rendering it unusable as far as calls/texts.
I saved a backup with TWRP and wiped it and It worked again.
The problem is when I restore my backup it is still locked.
Any help is appreciated! Restarting from scratch on this phone would be a huge pain.
Since you already did the permanent unlock, your IMEI is whitelisted in T-Mobile's database.
Clear data for the Device Unlock app, run it, and do Permanent Unlock. It will unlock the phone again.
You might need to have a T-Mobile SIM card in the phone when you do it.
siraltus said:
Since you already did the permanent unlock, your IMEI is whitelisted in T-Mobile's database.
Clear data for the Device Unlock app, run it, and do Permanent Unlock. It will unlock the phone again.
You might need to have a T-Mobile SIM card in the phone when you do it.
Click to expand...
Click to collapse
Thank you for the reply! I also forgot to mention that I am running this debloated rom:
http://forum.xda-developers.com/tmo...-lg-v10-h901-10c-debranded-debloated-t3277305
The T-Mobile unlock application is on the rom but does not function properly. I assume this is because most of the services that are used by the app are disabled in the rom.
Is there any place I could download the T-Mobile services or maybe even just reinstall the device unlock application.
Once again thank you for the reply!
johnfroedge said:
Thank you for the reply! I also forgot to mention that I am running this debloated rom:
http://forum.xda-developers.com/tmo...-lg-v10-h901-10c-debranded-debloated-t3277305
The T-Mobile unlock application is on the rom but does not function properly. I assume this is because most of the services that are used by the app are disabled in the rom.
Is there any place I could download the T-Mobile services or maybe even just reinstall the device unlock application.
Once again thank you for the reply!
Click to expand...
Click to collapse
Yes, you're running my ROM. Did you read the first post in the ROM thread?
I clearly wrote there that the Device Unlock app does not work on my ROM (and is not even included in it).
You must flash back to full stock and unlock there, then flash my ROM again.
siraltus said:
Yes, you're running my ROM. Did you read the first post in the ROM thread?
I clearly wrote there that the Device Unlock app does not work on my ROM (and is not even included in it).
You must flash back to full stock and unlock there, then flash my ROM again.
Click to expand...
Click to collapse
Sorry for not noticing ha:laugh:. Great job by the way!
I will give it a go. Is there any way I can restore the majority of what I have on my phone(apps/settings) without the phone relocking.
I assume that no matter what, if I restore the phone with the backup I made it will be locked again.
In T-mobile's database this phone is unlocked.
johnfroedge said:
Sorry for not noticing ha:laugh:. Great job by the way!
I will give it a go. Is there any way I can restore the majority of what I have on my phone(apps/settings) without the phone relocking.
I assume that no matter what, if I restore the phone with the backup I made it will be locked again.
In T-mobile's database this phone is unlocked.
Click to expand...
Click to collapse
SIM lock status is not stored in the Android OS. It's stored in the baseband processor, which is a separate chip with its own proprietary OS that Android can talk to in a very limited and specific way via the RIL (Radio Interface Layer).
The SIM lock status is NOT stored in your TWRP backup. You can backup and restore at will.
Once the phone is permanently SIM-unlocked, it should stay that way forever, unless the permanent unlock did not stick. After you do a permanent unlock in the Device Unlock app, you must reboot the phone and wait for the toast notification saying "device is permanently unlocked." If it worked, the Device Unlock app will disappear from your app drawer (it disables itself). If you still see it, the unlock did not stick and you have to open the app and do it again.
siraltus said:
SIM lock status is not stored in the Android OS. It's stored in the baseband processor, which is a separate chip with its own proprietary OS that Android can talk to in a very limited and specific way via the RIL (Radio Interface Layer).
The SIM lock status is NOT stored in your TWRP backup. You can backup and restore at will.
Once the phone is permanently SIM-unlocked, it should stay that way forever, unless the permanent unlock did not stick. After you do a permanent unlock in the Device Unlock app, you must reboot the phone and wait for the toast notification saying "device is permanently unlocked." If it worked, the Device Unlock app will disappear from your app drawer (it disables itself). If you still see it, the unlock did not stick and you have to open the app and do it again.
Click to expand...
Click to collapse
Any suggestions for when I recieve a message like this? I assume it is not a problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
johnfroedge said:
Any suggestions for when I recieve a message like this? I assume it is not a problem.
View attachment 3631869
Click to expand...
Click to collapse
Yes, that means the app failed to unlock the phone because it's already permanently unlocked. There's nothing for you to do there.
siraltus said:
Yes, that means the app failed to unlock the phone because it's already permanently unlocked. There's nothing for you to do there.
Click to expand...
Click to collapse
Thanks! I got it working again!
need help
johnfroedge said:
Thanks! I got it working again!
Click to expand...
Click to collapse
Pls what did you do to get it to work again? My galaxy core prime is network dead and I get the same unlock failed unlock approved crap.
Unlock t-mobile LG v10
Did anyone figure out how to get this unlocked? I am in the same situation and would love to collaborate with anyone on getting this unlocked.
In a similar situation with a LG K20 Plus unlocked third party. Restored a TWRP backup of Lineage OS 14.1 from stock OS. All was well I thought and then i noticed i lost UNLOCK + 1) IMEI 2) BASEBAND 3) SERIAL NUMBER. I restored IMEI, BASEBAND and working on SERIAL. Cannot get the Unlock back. Flashed back to stock to repair all and got all done but UNLOCK. Doesn't make sense.. I have tried a number of things but no success. I since flashed back to LineageOS thinking i might get the UNLOCK back but all i get now is a code input prompt like you get on LineageOS and most importantly code based unlock phones.. ATT,SPRINT,CRICKET etc. I got the same thing on Stock as well.. odd eh? Anyone have some suggestions?
Will post some screenshots soon.
Figured it out.. Flashed back to stock but a build newer than what i flashed before. Then I simply used the built in MetroPCS unlock app and it worked. lol... Flashed my custom stuff back and nothing lost at all. Got serial # back as well.
Related
What it says in the title. I got the phone from a guy, who I assume got it from aliexpress (because it had gifts with it) or imported some other way. The phone came in fully packed up, in all kinds of stickers and protective thingies and in it's box, with all the equipment packaged. Even has the protective thing (can't remember the eng word) over the screen still, so I'm pretty sure the phone is new and not used.
Anyway, if I'm not wrong the bootloader shows its already unlocked. Now my first goal is to root it, and I saw a lot of guides, and decided to follow these here but theres separate guides for officially unlocked and unofficially. My phone came like this so I don't know which is it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So questions:
1. How can I know whether its officially unlocked or unofficially?
2. Did I decide to follow the right guide or is there better ones?
3. My MTP and other drivers isn't working. I have Windows 7 Ultimate. EDIT: After installing a bunch of drivers I found, including the Mi PC Suite, universal adb drivers, and what not, MTP appears to be working, I can access the phone just fine and theres no exclamation mark over it like in "Devices and Printers". But I have some exclamation marks in device manager, as seen on screenshot. I'm not sure if "Unknown Device" is related. It could have been there before the phone, but ADB is new.
4. Are these exclamation marks an issue for following the guides to root and flash? The fastboot commands from screenshots work fine.
Phone Info:
- Android Version 5.1.1
- MIUI Version MIUI Global 7.3 | Stable
Sorry for the long post.
ChrisBunny said:
What it says in the title. I got the phone from a guy, who I assume got it from aliexpress (because it had gifts with it) or imported some other way. The phone came in fully packed up, in all kinds of stickers and protective thingies and in it's box, with all the equipment packaged. Even has the protective thing (can't remember the eng word) over the screen still, so I'm pretty sure the phone is new and not used.
Anyway, if I'm not wrong the bootloader shows its already unlocked. Now my first goal is to root it, and I saw a lot of guides, and decided to follow these here but theres separate guides for officially unlocked and unofficially. My phone came like this so I don't know which is it.
So questions:
1. How can I know whether its officially unlocked or unofficially?
2. Did I decide to follow the right guide or is there better ones?
3. My MTP and other drivers isn't working. I have Windows 7 Ultimate. EDIT: After installing a bunch of drivers I found, including the PCSuite, universal adb drivers, and what not, MTP appears to be working, I can access the phone just fine and theres no exclamation mark over it like in "Devices and Printers". But I have some exclamation marks in device manager, as seen on screenshot. I'm not sure if "Unknown Device" is related. It could have been there before the phone, but ADB is new.
4. Are these exclamation marks an issue for following the guides to root and flash? The fastboot commands from screenshots work fine.
Phone Info:
- Android Version 5.1.1
- MIUI Version MIUI Global 7.3 | Stable
Sorry for the long post.
Click to expand...
Click to collapse
1. If you buy it new the boot loader should be LOCKED , according to your screenshot it has been unlocked either by the seller or who knows but it's unlocked.
2. that guide is for installing twrp (custom recovery) not unlocking- but yeah to root you need to install twrp then supersu
https://download.chainfire.eu/969/SuperSU/
3. to get the correct drivers install MI PC Suite it has mostly everything you need for this device.
4. you shouldn't have any exclamation marks, try installing Mi Pc Suite.
otyg said:
1. If you buy it new the boot loader should be LOCKED , according to your screenshot it has been unlocked either by the seller or who knows but it's unlocked.
2. that guide is for installing twrp (custom recovery) not unlocking- but yeah to root you need to install twrp then supersu
https://download.chainfire.eu/969/SuperSU/
3. to get the correct drivers install MI PC Suite it has mostly everything you need for this device.
4. you shouldn't have any exclamation marks, try installing Mi Pc Suite.
Click to expand...
Click to collapse
1. Yes but the problem is I don't know whether its officially unlocked or unofficially unlocked, and its important because the guides for rooting and flashing twrp are different. That's what I'd like to know, but don't know how.
2. Yep. Like I said I'd like to root it, and later probably flash a CM rom, but I need TWRP first.
3. Already installed Mi PC Suite (forgot to write "Mi" in the Mi PC Suite, I'll correct that), and its working. Kind of. I can't make a backup, and sometimes it tells me theres an update when I plug the phone in (I'm reluctant to update atm), but when I press the "Update" it says the firmware is up to date. The rest of the functions seem to be working, like screencast or viewing the storage.
4. The exclamation mark is related to ADB, I don't know if Mi PC Suite should be installing that too, but anyway its there.
@ChrisBunny
There is no way to tell what method was used to unlock your phone. More than likely it is unofficial.
Your getting exclamation marks because some drivers haven't been installed properly, you may have to uninstall and reinstall to get the right versions installed.
What is the reported MIUI version in settings about phone? If your not getting something with four numbers (X.X.X.X). You could possibly have a vendor rom. Which may have spyware etc and you won't get updates.
corkiejp said:
@ChrisBunny
There is no way to tell what method was used to unlock your phone. More than likely it is unofficial.
Your getting exclamation marks because some drivers haven't been installed properly, you may have to uninstall and reinstall to get the right versions installed.
What is the reported MIUI version in settings about phone? If your not getting something with four numbers (X.X.X.X). You could possibly have a vendor rom. Which may have spyware etc and you won't get updates.
Click to expand...
Click to collapse
I'm assuming its unofficial too. If its from aliexpress I doubt they wait for official unlock for each phone they ship.
Also it came with Google Apps and MIUI apps. Didn't see chinese kanji on any apps or menu.
The MIUI version is "MIUI Global 7.3 | Stable" and under it says "7.3.6.0.0(LHOCNDD)".
Most aliexpress redmi note 3 pro pages say something like "we will open the original box to check the phone and install Multi-language ROM and Google play store,If you have special requests about the original box,please leave us a message" and also "And Many Multi-language ROM not support OTA Update" whatever OTA Update is. Over-the-air I assume. Which means the built in "Update" app shouldn't work. Which is fine, my old phone LG Optimus L7 II Prime didn't support OTA either. I didn't tap it yet in case it started updating right away, and I don't want to change anything without first backing up the entire rom, just in case, but don't know how to do that yet.
ChrisBunny said:
The MIUI version is "MIUI Global 7.3 | Stable" and under it says "7.3.6.0.0(LHOCNDD)".
Click to expand...
Click to collapse
That is definitely a Vendor Rom.
https://www.reddit.com/r/Xiaomi/wiki/roms/unofficial
Sort out your drivers first.
Then flash an official global developer rom, which might re-lock your bootloader and then unlock officially.
https://www.reddit.com/r/Xiaomi/wiki/roms/flashofficial
I assume you don't have the mediatek version of RN3?.
corkiejp said:
That is definitely a Vendor Rom.
https://www.reddit.com/r/Xiaomi/wiki/roms/unofficial
Sort out your drivers first.
Then flash an official global developer rom, which might re-lock your bootloader and then unlock officially.
https://www.reddit.com/r/Xiaomi/wiki/roms/flashofficial
I assume you don't have the mediatek version of RN3?.
Click to expand...
Click to collapse
"also adware and bloatware, which are annoying and slow the phone down. This ROM is also buggy and unoptimised, so some things might not work (e.g. battery showing negative percentage or the rear LED not working at all), you might encounter issues and inconsistencies (e.g. freezing, lagging)" funny I'm not experiencing any of that. No bloatware except a couple Mi stuff and usual system apps you'd find on the phone like Calendar and explorer and what not. The only new thing I didn't see on other phones is "Security" app. It appears to be a very clean vendor rom then. Its super fast and smooth I'm impressed.
Yes the phone is Pro version, with Snapdragon. Are the pictures I posted not visible?
If its already unlocked unofficially, should I be relocking it and then applying for an unlock? Isn't it simpler to just follow the unofficial guide for flashing?
ChrisBunny said:
Yes the phone is Pro version, with Snapdragon. Are the pictures I posted not visible?
If its already unlocked unofficially, should I be relocking it and then applying for an unlock? Isn't it simpler to just follow the unofficial guide for flashing?
Click to expand...
Click to collapse
I didn't notice the third image posted.
DO NOT lock it while on a vendor rom.
Is it up to yourself, if you want it unlocked officially or not. You just need to be careful when flashing.
I still get rid of the vendor rom. If you want future updates and to avoid unknown/unseen future bugs.
corkiejp said:
I didn't notice the third image posted.
DO NOT lock it while on a vendor rom.
Is it up to yourself, if you want it unlocked officially or not. You just need to be careful when flashing.
I still get rid of the vendor rom. If you want future updates and to avoid unknown/unseen future bugs.
Click to expand...
Click to collapse
Yeah but is there any disadvantages to having an unofficial unlock over official? If not then I guess I'll just be careful following the unofficial guide for flashing. If there is disadvantages then I'll apply for official unlock and just wait.
I do want to get rid of this rom at some point and try CM if theres a fully functional one, but for now I'd just like TWRP and root on it.
ChrisBunny said:
Yeah but is there any disadvantages to having an unofficial unlock over official? If not then I guess I'll just be careful following the unofficial guide for flashing. If there is disadvantages then I'll apply for official unlock and just wait.
I do want to get rid of this rom at some point and try CM if theres a fully functional one, but for now I'd just like TWRP and root on it.
Click to expand...
Click to collapse
With unofficial unlock you have to be very precautious while flashing MIUI based rom else hard brick later is not the case for official unlock
My Kenzo is just about 4-5 months old. I am fed up with MIUI, hence want to install Lineage OS
Now I previously owned a Moto E (XT1022) before, and tinkering it was damn easy (cough Xiaomi!). :cyclops:
I know that working with an unlocked bootloader is better in such cases, and so I had applied for permissions, and was granted the same after 2 days.
But trying to unlock via the Unlock Tool, I found that it got stuck at 50%. (Googled a lot, still not being able to unlock :crying
What am I missing?
It's showing this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
P.S. All drivers are perfectly installed. Please do not suggest me the unofficial method, or installing TWRP without unlocking BL.
Are you sure you're using the same Mi account on the phone and the one you have logged in in the Mi Unlock Tool?
I came from Zenfone 2 and the processes was kinda different from where I came from but I was able to get past that bootloader unlocking process easily. I was on China Stable ROM, if it helps.
krazy23 said:
Are you sure you're using the same Mi account on the phone and the one you have logged in in the Mi Unlock Tool?
I came from Zenfone 2 and the processes was kinda different from where I came from but I was able to get past that bootloader unlocking process easily. I was on China Stable ROM, if it helps.
Click to expand...
Click to collapse
Yes, absolutely.... I am on the same account
You'll be able to unlock bootloader only on MIUI beta ROM. Learned it a hard time. Flash latest beta ROM via EDL and try to unlock on the next day.
BlueJeans said:
You'll be able to unlock bootloader only on MIUI beta ROM. Learned it a hard time. Flash latest beta ROM via EDL and try to unlock on the next day.
Click to expand...
Click to collapse
Is it so?
That means all my data will be wiped!
Rohitagni said:
Is it so?
That means all my data will be wiped!
Click to expand...
Click to collapse
Yes. Take a backup of all your data (internal storage) and then flash global beta.
I have struggled with this situation for almost 2 months and then I learned that it is the only way.
BlueJeans said:
Yes. Take a backup of all your data (internal storage) and then flash global beta.
I have struggled with this situation for almost 2 months and then I learned that it is the only way.
Click to expand...
Click to collapse
Thanks for the update, I am downloading the latest Dev ROM now.
BlueJeans said:
Yes. Take a backup of all your data (internal storage) and then flash global beta.
I have struggled with this situation for almost 2 months and then I learned that it is the only way.
Click to expand...
Click to collapse
Ok now I have the DEV rom, and it sucks like HELL, basic things like the vibration on fingerprint doesn't even work.... I need to get it up and running on Lineage as early as possible.
Are you sure that we can try that "UNLOCKING" on the next day? Or will it take more?
Rohitagni said:
Ok now I have the DEV rom, and it sucks like HELL, basic things like the vibration on fingerprint doesn't even work.... I need to get it up and running on Lineage as early as possible.
Are you sure that we can try that "UNLOCKING" on the next day? Or will it take more?
Click to expand...
Click to collapse
It takes at least a day. My friend tried on the same day he installed beta ROM but still got the same error. He enabled find device and went to i.mi.com just to double check that everything goes smoothly. Then he tried to unlock the next day and it worked.
BlueJeans said:
It takes at least a day. My friend tried on the same day he installed beta ROM but still got the same error. He enabled find device and went to i.mi.com just to double check that everything goes smoothly. Then he tried to unlock the next day and it worked.
Click to expand...
Click to collapse
ok... i'll try after a day or two
I applied for the permission and got it on the same day. Tried for a week but got the same error on Unlock tool. Run out of patience, I unlocked the bootloader unofficially and installed Unofficial RR 5.7.3 (latest available RR at that time) which locked my Bootloader again.
After booting successfully, I rebooted into Fastboot and tried to unlock with Official Unlock tool and damn.! it unlocked at that very instant. I remember I tried that very same day on MIUI but it failed.
So speaking of my experience, as long as you have applied for permission and got the same, you can unlock unofficially. You'll be able to unlock officially later with any ROM. Moreover having a locked bootloader is not much of an issue once you have a custom recovery installed.
The availability of so many ROMs for Kenzo is simply too tempting to wait I guess.
Try after fifteen days, it will surely get unlocked.. I also faced the same problem! The problem is that they upload the servers late! Also check whether mi. Find device is on or no! Trust me, patience is the only key other than the unofficial process!
Rohitagni said:
My Kenzo is just about 4-5 months old. I am fed up with MIUI, hence want to install Lineage OS
Now I previously owned a Moto E (XT1022) before, and tinkering it was damn easy (cough Xiaomi!). :cyclops:
I know that working with an unlocked bootloader is better in such cases, and so I had applied for permissions, and was granted the same after 2 days.
But trying to unlock via the Unlock Tool, I found that it got stuck at 50%. (Googled a lot, still not being able to unlock :crying
What am I missing?
It's showing this:
P.S. All drivers are perfectly installed. Please do not suggest me the unofficial method, or installing TWRP without unlocking BL.
Click to expand...
Click to collapse
BlueJeans said:
You'll be able to unlock bootloader only on MIUI beta ROM. Learned it a hard time. Flash latest beta ROM via EDL and try to unlock on the next day.
Click to expand...
Click to collapse
Rohitagni said:
ok... i'll try after a day or two
Click to expand...
Click to collapse
Don't worry you will be able to unlock your device in a couple of days.
I unlocked mine on latest MIUI 8.1.4.0 mm global stable ROM
I got permission in 2 days and was unable to unlock this is what I learnt:
Go to mi cloud and check the device ID yours and find is location.
Upload something in mi cloud and view it there.
After that wait for 4 to 6 days and your will be easily be able to unlock it bootloader.
Hope it helps.
Hello All,
I saw in this thread, that someone was able to re-lock an unlocked bootloader on an S9+. I think the S9 and S9+ are basically the same, right?
https://forum.xda-developers.com/gal...oader-t3870600
I purchased a pre-owned S9 from an eBay seller with the intent of rooting it. After unlocking the bootloader and working through the process of rooting in detail, I learned that the US (Qualcomm) version of the S9 cannot be rooted. Therefore, I decided to send the phone back and buy a OnePlus 6T.
I factory reset the Galaxy, but I forgot about the unlocked bootloader. After I returned the phone, the seller pointed out that the bootloader was unlocked, (actually, what he said, was that there was now a "custom bootloader" on the phone) .
Here's what the seller said:
The phone came back with the custom boot loader on at startup and then when rebooted it is saying that you let your account still on the phone. Please we need this removed from the phone as this is now locked to your account. It cannot be resold or used until your account is removed.
Pics from the seller:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The seller has returned half of my payment of $300. I'd like to get him to send me the phone, so I can re-lock the bootloader and get the rest of my money back. Is this possible?
Thank you in advance, for any guidance you might be able to provide.
NBUK
NoBodyUKnow said:
Hello All,
I saw in this thread, that someone was able to re-lock an unlocked bootloader on an S9+. I think the S9 and S9+ are basically the same, right?
https://forum.xda-developers.com/gal...oader-t3870600
I purchased a pre-owned S9 from an eBay seller with the intent of rooting it. After unlocking the bootloader and working through the process of rooting in detail, I learned that the US (Qualcomm) version of the S9 cannot be rooted. Therefore, I decided to send the phone back and buy a OnePlus 6T.
I factory reset the Galaxy, but I forgot about the unlocked bootloader. After I returned the phone, the seller pointed out that the bootloader was unlocked, (actually, what he said, was that there was now a "custom bootloader" on the phone) .
Here's what the seller said:
The phone came back with the custom boot loader on at startup and then when rebooted it is saying that you let your account still on the phone. Please we need this removed from the phone as this is now locked to your account. It cannot be resold or used until your account is removed.
Pics from the seller:
The seller has returned half of my payment of $300. I'd like to get him to send me the phone, so I can re-lock the bootloader and get the rest of my money back. Is this possible?
Thank you in advance, for any guidance you might be able to provide.
NBUK
Click to expand...
Click to collapse
If its a US model it can be rooted and the bootloader cannot be unlocked so your good
all you need to do is put in your google account and factory reset withing setting while in the device not recovery
there is no custom bootloader for the US models they CANNOT be unlocked or modded in any way so he is full of crap
The custom bootloader you both see Is in fact the stock android recovery that is installed on almost every android phone
Need some clarification, please
TheMadScientist said:
If its a US model it can be rooted and the bootloader cannot be unlocked so your good
Click to expand...
Click to collapse
Thanks, but I am pretty sure I unlocked the bootloader, using fastboot/ADB. Otherwise, the device would not boot to recovery as in the picture. Isn't that correct?
all you need to do is put in your google account and factory reset withing setting while in the device not recovery[/QUOTE said:
I did a factory reset from recovery mode, as seen on the picture. I thought that would totally reset the device to stock . I'm wondering why the Google account was still there.
there is no custom bootloader for the US models they CANNOT be unlocked or modded in any way so he is full of crap[/QUOTE said:
Thanks what I thought. I did unlock the bootloader though, or I would not be able to get to it. Is that correct?
The custom bootloader you both see Is in fact the stock android recovery that is installed on almost every android phone[/QUOTE said:
Thanks what I thought.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
NoBodyUKnow said:
Thanks, but I am pretty sure I unlocked the bootloader, using fastboot/ADB. Otherwise, the device would not boot to recovery as in the picture. Isn't that correct?
I did a factory reset from recovery mode, as seen on the picture. I thought that would totally reset the device to stock . I'm wondering why the Google account was still there.
Thanks what I thought. I did unlock the bootloader though, or I would not be able to get to it. Is that correct?
Thanks what I thought.
Click to expand...
Click to collapse
You have to purchase something thats called and engineering certificate. For nearly 300 dollars to unlock the bootloader. Again that is Android's factory recovery. Not modified. So like I said as long as you reboot and enter your Gmail. The reset from within Android settings that is a proper factory reset
it is not possible to unlock the bootloader on this phone. you did not unlock the bootloader, you simply used adb to reboot the phone into recovery. that is something you can do with any android device
dmtec said:
it is not possible to unlock the bootloader on this phone. you did not unlock the bootloader, you simply used adb to reboot the phone into recovery. that is something you can do with any android device
Click to expand...
Click to collapse
Thank you for your response!
Here is the last message I sent the seller, based on the input I've received here:
I believe the phone can be returned to original state by actuating the "factory reset" found under Settings > System > Advanced > Reset Options > Erase All Data (Factory Reset). If that cannot be done, then let's discuss other options
Is the above an accurate statement?
The seller's reply, to the above:
The reset is producing the same issue. We are not sure about what happened, but whatever bootloader you used, caused the phone to think it has an account on it and now it will not get past that point. We are going have to mail you this device if we cannot figure out a way to get rid of this issue. Please understand, we cannot even get to the home screen. The phone will not go through setup. It is saying "An unauthorized reset was detected, please provide the last account that was on this device"
Oy...
Update: I called the seller and provided my Gmail credentials, so the phone could be reset, which it was. All good now. Naturally, I changed passwords immediately after.
Thanks for the input. Much Love! <3
NoBodyUKnow said:
Update: I called the seller and provided my Gmail credentials, so the phone could be reset, which it was. All good now. Naturally, I changed passwords immediately after.
Thanks for the input. Much Love! <3
Click to expand...
Click to collapse
Awesome Im glad to see it worked out for ya as long as they give the rest of your refund
TheMadScientist said:
Awesome Im glad to see it worked out for ya as long as they give the rest of your refund
Click to expand...
Click to collapse
I guess we will see. Thanks for your help!
Moto G Power 2021
XT2117
borneo
Firmware
Rescue and Smart Assistant (LMSA)
https://mirrors.lolinet.com/firmware/moto/borneo/official/
https://t.me/s/MotoUpdatesTracker
[Index] Motorola Stock Firmware
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Moto G Play
XT2093
Moto G Stylus
XT2115
I have the moto g power borneo, just got it yesterday. the option for "enable oem unlocking" is greyed out. I did a full factory reset, and still grey. It's not tied to any carrier, and I've already connected to the internet via wifi. the phone is network unlocked. Would I be able to flash the stock rom via LMSA, and that might get it to work?
edit: just to clarify. yes, the bootloader is locked.
gutter_chris said:
I have the moto g power borneo, just got it yesterday. the option for "enable oem unlocking" is greyed out. I did a full factory reset, and still grey. It's not tied to any carrier, and I've already connected to the internet via wifi. the phone is network unlocked. Would I be able to flash the stock rom via LMSA, and that might get it to work?
edit: just to clarify. yes, the bootloader is locked.
Click to expand...
Click to collapse
Sometimes there's a time delay for the allow oem unlocking, it may take a few days, be sure to connect to wifi or lte after factory reset.
You certainly can try LMSA, but reflashing the firmware is unlikely to speed up the process.
sd_shadow said:
Sometimes there's a time delay for the allow oem unlocking, it may take a few days.
Click to expand...
Click to collapse
Yeah, I had read that somewhere yesterday. Thanks for confirming that. I will wait patiently first.
If anyone has suggestions on how to flash the cricket firmware to a boost mobile device let me know. I'm open to try anything on this $90 device.
TheTrueJayTwenty said:
If anyone has suggestions on how to flash the cricket firmware to a boost mobile device let me know. I'm open to try anything on this $90 device.
Click to expand...
Click to collapse
You may only need the radio flash
Flashing the Radio Firmware
https://mirrors.lolinet.com/firmware/moto/borneo/official/Cricket/
I would try to unlock the bootloader first, but just flashing the radio firmware is pretty safe.
sd_shadow said:
You may only need the radio flash
Flashing the Radio Firmware
https://mirrors.lolinet.com/firmware/moto/borneo/official/Cricket/
I would try to unlock the bootloader first, but just flashing the radio firmware is pretty safe.
Click to expand...
Click to collapse
Unfortunately OEM unlock is grayed out, but I was able to get an unlock key from Motorola. I've been trying to figure out a way to flash the cricket firmware because I don't think OEM unlock is grayed out.
TheTrueJayTwenty said:
Unfortunately OEM unlock is grayed out, but I was able to get an unlock key from Motorola. I've been trying to figure out a way to flash the cricket firmware because I don't think OEM unlock is grayed out.
Click to expand...
Click to collapse
Flashing a different software channel with a locked bootloader, will not end well.
Better off trying a factor reset, and connect to wifi or lte.
There can be a timed delay of a few days, on the allow OEM unlock
sd_shadow said:
Flashing a different software channel with a locked bootloader, will not end well.
Better off trying a factor reset, and connect to wifi or lte.
There can be a timed delay of a few days, on the allow OEM unlock
Click to expand...
Click to collapse
I have it on Wi-Fi right now, hopefully its just delayed. I only got this device to use on Wi-Fi, but if I don't keep airplane mode on Boost mobile locks the Wi-Fi unless you activate service with them. Very strange way to do business if you ask me.
TheTrueJayTwenty said:
I only got this device to use on Wi-Fi, but if I don't keep airplane mode on Boost mobile locks the Wi-Fi unless you activate service with them.
Click to expand...
Click to collapse
I have the same issue. Anyone know of a way to disable this? I've tried to remove anything associated with carrier and boost from the device (borneo) through adb. Some I was able to disable but most failed as non-disable. I got this device for my 5 yr old to mess around on, but the TOS popup is intrusive and she has repeatedly accidentally pressed the accept button which locks out wifi. Would rooting and flashing a new rom even resolve the TOS requests from boost. Forgive my ignorance as I haven't messed with root or custom roms since my lg g3. Any help is greatly appreciated.
MuffinGod said:
I have the same issue. Anyone know of a way to disable this? I've tried to remove anything associated with carrier and boost from the device (borneo) through adb. Some I was able to disable but most failed as non-disable. I got this device for my 5 yr old to mess around on, but the TOS popup is intrusive and she has repeatedly accidentally pressed the accept button which locks out wifi. Would rooting and flashing a new rom even resolve the TOS requests from boost. Forgive my ignorance as I haven't messed with root or custom roms since my lg g3. Any help is greatly appreciated.
Click to expand...
Click to collapse
So I may have figured it out, I did a factory reset, on setup I declined everything. I removed everything I could via adb that had anything to do with sprint, boost, and carrier. I then went into the apps list on the device clicked show system apps, went through the apps I couldn't disable under advanced I denied the app permission to modify system settings. As for the TOS the keeps popping up you can try turning on airplane mode you can still use Wi-Fi, I've had hit or miss luck with this one. But Wi-Fi is still working as of now... Hopefully someone can get the bootloader unlocked on the boost model.
I think we're in the same boat. I have airplane mode on with wifi but it doesn't seem to stop the popup. I did get the bootloader unlocked with a code from Motorola, but I'm unsure what step I should take next. Root the device and blast everything I don't think I'll need off of it. Or install a stock moto rom?
MuffinGod said:
I think we're in the same boat. I have airplane mode on with wifi but it doesn't seem to stop the popup. I did get the bootloader unlocked with a code from Motorola, but I'm unsure what step I should take next. Root the device and blast everything I don't think I'll need off of it. Or install a stock moto rom?
Click to expand...
Click to collapse
Do you have the boost version? My oem unlock is still grayed out so my bootloader code us useless, but yeah I would root, and remove carrier device manager.
TheTrueJayTwenty said:
Do you have the boost version? My oem unlock is still grayed out so my bootloader code us useless, but yeah I would root, and remove carrier device manager.
Click to expand...
Click to collapse
Yeah boost varient. Mine was grayed out for a couple of days and then it wasn't.
If I understand correctly I download the firmware from lolinet. Patch it with magisk and then flash in fastboot, reboot, done. Has anyone made a detailed post on this process? I really prefer to understand each step as I do it.
MuffinGod said:
If I understand correctly I download the firmware from lolinet. Patch it with magisk and then flash in fastboot, reboot, done. Has anyone made a detailed post on this process? I really prefer to understand each step as I do it.
Click to expand...
Click to collapse
I have a general moto root thread.
Pretty much all the same as long as ramdisk is in the boot.img
Spoiler: Like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just make sure the firmware matches what is installed (device, channel, software version)
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
sd_shadow said:
I have a general moto root thread.
Pretty much all the same as long as ramdisk is in the boot.img
Spoiler: Like this
Just make sure the firmware matches what is installed (device, channel, software version)
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Click to expand...
Click to collapse
sd_shadow said:
I have a general moto root thread.
Pretty much all the same as long as ramdisk is in the boot.img
Spoiler: Like this
Just make sure the firmware matches what is installed (device, channel, software version)
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Click to expand...
Click to collapse
Great guide. Thank you
sd_shadow said:
I have a general moto root thread.
Pretty much all the same as long as ramdisk is in the boot.img
Spoiler: Like this
Just make sure the firmware matches what is installed (device, channel, software version)
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Click to expand...
Click to collapse
sd_shadow said:
I have a general moto root thread.
Pretty much all the same as long as ramdisk is in the boot.img
Spoiler: Like this
Just make sure the firmware matches what is installed (device, channel, software version)
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Click to expand...
Click to collapse
Great guide. Thank you
Hmm... I followed steps correctly (I think) flashed img and rebooted. Downloaded root checker and confirmed had root. I downloaded a system app Uninstaller, granted root permissions and tried to uninstall carrier device manager. The app requested a reboot. Reboot completed anf now I don't have root access and the carrier app is still installed. Any ideas what I did wrong?
Re-flashed and have root again. Trying to delete system apps through root explorer results in a failure. Is there a system write protection on this phone I need to disable?
Is it safe to try:
adb shell reboot disemmcwp
i got pixel 6 and I've been planning to sell it, i tried to lock the bootloader but the commend didn't work i don't know why. After that i was trying to re flash the stock ROM via fastboot mode but for some reason flashing process aborted at particular point and phone wasn't booting, kept in bootloop .. google logo then restart and it went on.
after that i made a mistake which was i attempted to re lock the bootloader while phone was in bootloop and the process completed successfully.
now I'm not able to flash anything via fastboot as bootloader is locked and it's cannot get unloaded ..
is there anything i could do to reflash the stock image in this state? phone now doesn't boot .. only google logo the it restarts it self
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
abdulmajed1 said:
i got pixel 6 and I've been planning to sell it, i tried to lock the bootloader but the commend didn't work i don't know why. After that i was trying to re flash the stock ROM via fastboot mode but for some reason flashing process aborted at particular point and phone wasn't booting, kept in bootloop .. google logo then restart and it went on.
after that i made a mistake which was i attempted to re lock the bootloader while phone was in bootloop and the process completed successfully.
now I'm not able to flash anything via fastboot as bootloader is locked and it's cannot get unloaded ..
is there anything i could do to reflash the stock image in this state? phone now doesn't boot .. only google logo the it restarts it self
Click to expand...
Click to collapse
Try sideloading the OTA. Also, if you still have OEM unlocking enabled in Developer Options you can try using Android Flash Tool.
Lughnasadh said:
Try sideloading the OTA. Also, if you still have OEM unlocking enabled in Developer Options you can try using Android Flash Device not boot
Click to expand...
Click to collapse
Lughnasadh said:
Try sideloading the OTA. Also, if you still have OEM unlocking enabled in Developer Options you can try using Android Flash Tool.
Click to expand...
Click to collapse
Android Flash Tool can't be used on a locked bootloader. That being said, it's the best way to return the phone to stock state.
Sideloading the OTA is the only possibility of restoring the device in this situation. I don't think the Pixel Repair Tool works with the Pixel 6 yet.
Try booting to recovery mode and perform a factory reset.
Lastly...A "bricked" device is completely unresponsive. If the device boots, the screen works, and can be forced into bootloader/fastboot/recovery, it's not bricked.
V0latyle said:
Android Flash Tool can't be used on a locked bootloader. That being said, it's the best way to return the phone to stock state.
Sideloading the OTA is the only possibility of restoring the device in this situation. I don't think the Pixel Repair Tool works with the Pixel 6 yet.
Try booting to recovery mode and perform a factory reset.
Lastly...A "bricked" device is completely unresponsive. If the device boots, the screen works, and can be forced into bootloader/fastboot/recovery, it's not bricked.
Click to expand...
Click to collapse
All you need is OEM Unlocking enabled to use Android Flash Tool. You don't actually have to have your bootloader unlocked. The Flash Tool will do it for you.
Lughnasadh said:
All you need is OEM Unlocking enabled to use Android Flash Tool. You don't actually have to have your bootloader unlocked. The Flash Tool will do it for you.
Click to expand...
Click to collapse
No kidding? I wasn't aware of that!
Doesn't help in this situation, sadly.
V0latyle said:
Android Flash Tool can't be used on a locked bootloader. That being said, it's the best way to return the phone to stock state.
Sideloading the OTA is the only possibility of restoring the device in this situation. I don't think the Pixel Repair Tool works with the Pixel 6 yet.
Try booting to recovery mode and perform a factory reset.
Lastly...A "bricked" device is completely unresponsive. If the device boots, the screen works, and can be forced into bootloader/fastboot/recovery, it's not bricked.
Click to expand...
Click to collapse
I've tried sideloading the latests ota file but then the process got aborted.
it showed: failed to verify whole file signature.
I've tried both latest stable ota " Androd 12 " and beta as well
Lughnasadh said:
All you need is OEM Unlocking enabled to use Android Flash Tool. You don't actually have to have your bootloader unlocked. The Flash Tool will do it for you.
Click to expand...
Click to collapse
I'm not able to reach oem unlocking option since it cannot boot
abdulmajed1 said:
I'm not able to reach oem unlocking option since it cannot boot
Click to expand...
Click to collapse
Sideload the OTA. Make sure your Platform Tools are up-to-date. Make sure you are sideloading the OTA and not the factory image and it's the correct OTA for your device. Try different cables and ports. Re-download in case your original download got corrupted.
Lughnasadh said:
Sideload the OTA. Make sure your Platform Tools are up-to-date. Make sure you are sideloading the OTA and not the factory image and it's the correct OTA for your device. Try different cables and ports. Re-download in case your original download got corrupted.
Click to expand...
Click to collapse
already tried sideloading different ota versions, different ports and cables as well. There's no point
Have you tried the Android Flash Tool?
I don't know if it would work since I believe locking the bootloader also disables OEM Unlocking, but it's worth a try.
hello guys
I fixed the pixel
ٖ:
The problem was mostly from the laptop
I used an Bugjaeger Mobile ADB - USB OTG app and install beta update from adb update recovery
thanks