Database Users

[Q] Noob corporate email problem

Hello,
I have a Nexus 4 running Kitkat 4.4.2 and everything was good until a few days ago. I have a few accounts on the phone but the one I'm trying to fix is the corporate email - I had a stuck message (not in my Outlook inbox but in my phone inbox) and tried deleting & filing in a different folder but nothing worked. With iphones and newer Blackberry devices, you can simply remove the offending account and then add it again which usually fixes glitches like this. After removing the corporate email account from the accounts list and having it hang when trying to recreate it, I ended up doing some reading which led me to the Security section to remove the corporate email from there. Now I am able to create a corporate email account but my only options are POP or IMAP which won't work.
Any ideas...?
Peter

You probably deleted exchange services. Flash the system img file from the factory image in fastboot.
Sent from my Nexus 5

I am an Android beginner - will that wipe my N4 and does it involve rooting it?
jd1639 said:
You probably deleted exchange services. Flash the system img file from the factory image in fastboot.
Sent from my Nexus 5
Click to expand...
Click to collapse

PeterRooter said:
I am an Android beginner - will that wipe my N4 and does it involve rooting it?
Click to expand...
Click to collapse
It will not wipe your device or involve rooting, except if you haven't already unlocked the bootloader. That'll wipe your device.
Sent from my Nexus 5

PeterRooter said:
Hello,
I have a Nexus 4 running Kitkat 4.4.2 and everything was good until a few days ago. I have a few accounts on the phone but the one I'm trying to fix is the corporate email - I had a stuck message (not in my Outlook inbox but in my phone inbox) and tried deleting & filing in a different folder but nothing worked. With iphones and newer Blackberry devices, you can simply remove the offending account and then add it again which usually fixes glitches like this. After removing the corporate email account from the accounts list and having it hang when trying to recreate it, I ended up doing some reading which led me to the Security section to remove the corporate email from there. Now I am able to create a corporate email account but my only options are POP or IMAP which won't work.
Any ideas...?
Peter
Click to expand...
Click to collapse
Under add account in setting the options should look like this. (Pic attached)
{
"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"
}
Sent from my Nexus 4 using XDA Premium HD app

xxISYMFSxx said:
Under add account in setting the options should look like this. (Pic attached)
View attachment 2663599
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
I realize that, but it doesn't - the corporate selection isn't listed. Only POP and IMAP...

jd1639 said:
It will not wipe your device or involve rooting, except if you haven't already unlocked the bootloader. That'll wipe your device.
Sent from my Nexus 5
Click to expand...
Click to collapse
So to sum up - download fastboot, unlock bootloader and then load the system.img
I'll give it a shot this afternoon, thanks for your help.

Finally worked up the courage to try this today and ended up with a fresh phone (not what I wanted).
Here's what I did;
put phone in fastboot mode (by pressing vol up, vol down and power)
fastboot devices (to make sure it could see it)
fastboot oem unlock
fastboot flash system system.img (from Kitkat 4.4.2, same OS I was running before this crap started)
fastboot oem lock
fastboot reboot
Then I got to pick a language and start the setup, just like when it came out of the box (minus all my apps, data and pics)...

PeterRooter said:
Finally worked up the courage to try this today and ended up with a fresh phone (not what I wanted).
Here's what I did;
put phone in fastboot mode (by pressing vol up, vol down and power)
fastboot devices (to make sure it could see it)
fastboot oem unlock
fastboot flash system system.img (from Kitkat 4.4.2, same OS I was running before this crap started)
fastboot oem lock
fastboot reboot
Then I got to pick a language and start the setup, just like when it came out of the box (minus all my apps, data and pics)...
Click to expand...
Click to collapse
If you weren't unlocked before, unlocking is what wiped your device. Just flashing the system.img will not wipe the device
Sent from my Nexus 5

[Guide] Unlock the bootloader

Tested on PLK-L01 from Germany.
Download the following file:
http://rootjunkysdl.com/getdownload.php?file=Huawei%20P8%20Lite/Huawei%20Product%20ID%20Generator.exe
Insert you IMEI1 and choose "HUAWEI Y300-0000" as model.
Copy the product ID.
On the following picture it is in german, but on the page it is described in english which information you have to enter.
Enter the information on following page: http://emui.huawei.com/en/plugin.php?id=unlock&mod=detail
You have to login via Facebook to get the code and it only works with facebook.
Every Facebook account can unlock two devices every six months.
You will get the unlock code marked red.
{
"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"
}

Did you tried also to flash something? (Root or xposed)

Piemo said:
Did you tried also to flash something? (Root or xposed)
Click to expand...
Click to collapse
Not until now, but if you have something reliable to flash for rooting I will try it.
There was the guide for rooting the Honor 7, but I don't know if it is only for the chinese version?

Aurevo said:
Not until now, but if you have something reliable to flash for rooting I will try it.
There was the guide for rooting the Honor 7, but I don't know if it is only for the chinese version?
Click to expand...
Click to collapse
Actually I've seen only that one, dunno if it would work. I'm like that my order is "waiting for stock" so other can try for me. XD

Worked for me
Piemo said:
Did you tried also to flash something? (Root or xposed)
Click to expand...
Click to collapse
This method worked for me, so thanks to OP.
As fastboot oem get-bootinfo shows the Bootloader as unlocked.
I flashed a Chinese TWRP from the guide I found elsewhere here. It definitely boots into TWRP and everything works inside TWRP, albeit in Chinese.
Unfortunately, I'm now in a TWRP bootloop and can't get out of it.
I don't have a stock ROM/recovery to re-flash, so I'm hosed until one appears online.
Model PLK-L01

philipcraig said:
This method worked for me, so thanks to OP.
As fastboot oem get-bootinfo shows the Bootloader as unlocked.
I flashed a Chinese TWRP from the guide I found elsewhere here. It definitely boots into TWRP and everything works inside TWRP, albeit in Chinese.
Unfortunately, I'm now in a TWRP bootloop and can't get out of it.
I don't have a stock ROM/recovery to re-flash, so I'm hosed until one appears online.
Model PLK-L01
Click to expand...
Click to collapse
Try the tutorial on gizdev!

haasgo said:
Try the tutorial on gizdev!
Click to expand...
Click to collapse
Is it useful to try it without an recovery image available? Some other user tried it and is in a bootloop now without the possibility to recover.

I also slashed beta-supersu, using the Chinese twrp. I didn't reboot in between flashing twrp and supersu. Maybe I should have.

Thanks!
Works perfect for me

What to do with the unlock code? I mean where to enter it?

Using your tip, I made this http://androidmtk.com/unlock-bootloader-of-huawei-honor-7

rahul964 said:
Using your tip, I made this http://androidxda.com/unlock-bootloader-of-huawei-honor-7
Click to expand...
Click to collapse
I get stuck on the step 10: after I fill everything out, it says "Sorry, you must use a phone account to submit this application."

I had this too. I needed to log in at the first step with a Facebook account. Basically Huawei want a record of who they've given codes to.

philipcraig said:
I had this too. I needed to log in at the first step with a Facebook account. Basically Huawei want a record of who they've given codes to.
Click to expand...
Click to collapse
Yes, it worked.
Did you figure out how to get out of the bootloop? Did you successfully root it?

pappapishu said:
Yes, it worked.
Did you figure out how to get out of the bootloop? Did you successfully root it?
Click to expand...
Click to collapse
Yes, and yes.

philipcraig said:
Yes, and yes.
Click to expand...
Click to collapse
Okay, but the "bootloop part" is necessary, isn't? Did you fix it thanks to duky_duke's post?
http://forum.xda-developers.com/showpost.php?p=62737969&postcount=17

pappapishu said:
Okay, but the "bootloop part" is necessary, isn't? Did you fix it thanks to duky_duke's post?
http://forum.xda-developers.com/showpost.php?p=62737969&postcount=17
Click to expand...
Click to collapse
Yes. Though mine seemed even more complex. I couldn't boot into the bootloader that way.
What I found is that via some combination of volume/power keys and having power plugged in or not, I finally:
* did a boot into safe-mode
* discovered I was rooted
* used to to install ROM manager
* rebooted, out of safe mode
* ran ROM manager
* rebooted to bootloader
And then did what dukey said.

strange i have tried to log using facebook button but it keeps sending me the '"Sorry, you must use a phone account to submit this application."'
any ideas?

Hi,
I got stuck when posting my numbers with the following answer:
We regret to say that the information you are searching is not found. Pleae mail to [email protected], We'll respond to you as soon as possible, thanks.
Click to expand...
Click to collapse
Has anybody else got stuck here or knows how to get around it?
I have not received an answer to the mail I sent them yesterday - I hope somebody replies at all
lippl

The .exe linked in the first post is not required to determine the product ID. It can be determined using universal code *#*#1357946#*#* (which returns an 8-digit code as expected)
Further, the .exe linked in the first post does not get a clean bill of health at VirusTotal - nothing definitive but not clean. Anyone planning to use it to generate an unlock code should use reasonable caution, sandbox the application or (better) run it on a disposable VM.

FIXING "Couldn't verify device" stuck at 50%

{
"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"
}
If you got result above when official unlocking your phone, here is my solution for this.
No MiFlashTool needed. I'm not sure 32-bit Windows works, but it should, tested on Windows 10 64-bit with 10 years old hardware
This only fix: Couldn't verify device "Current account is different from the account info on the device"
YOUR DEVICE WILL BE WIPED, BACKUP EVERYTHING
First: (what you need)
- You have to login account that have permission to unlock.
- Enable find device, lock, etc... (everything that help security)
- Reliable, stable Wi-Fi connection.
- Xiaomi Driver (I recommended install Mi PC Suite), plug your phone with Mi PC Suite running, if it recognize your phone, you are good to go.
Next step:
- Download latest DEVELOPER ROM on MIUI homepage. I use GLOBAL DEV but CHINESE DEV should work too.
- Copy it to INTERNAL STORAGE put it in downloaded_rom folder (create it if it not there) (DON'T USE EXTERNAL STORAGE, your phone will reboot like nothing happened)
- Use Updater app and browse to DEV ROM file.
- Updater app will ask you to confirm that everything will be wipe and you should probably backup everything.
- Updating will take about 10-20 minutes.
Another next step:
- You will be asked to enter password for the account that you logged in before update, enter and wait till everything is okay.
- Login to Google Play isn't necessary.
- Reboot to Fastboot screen (Volume Down + Power or "adb reboot fastboot" if you have adb on your PC)
- Run official unlock tool, login with the account on your phone.
- Plug your phone (which is in Fastboot mode right now).
- Click unlock and your phone will be unlocked in 15 seconds.
- Your phone will reboot and enjoy unlocked bootloader.
Last but not least: Checking your phone unlocked or not. (you will need adb and fastboot for this)
- Boot to Fastboot (manually or command: "adb reboot fastboot")
- Use command: fastboot oem device-info
- If "Device unlocked: true" that means your phone is unlocked.
P/s: Sorry for my broken English

when i choose the developer rom it shows "could not verify package" !!

this is not a fix
The problem lies with Mi Servers
If there's a mismatch of your details on your local device and server, you will get unable to verify error
No matter which rom you try, u going to get the same error
BTW i unlocked on global stable, i had the same issue for like 15days and finally contacted one MIUI device team member he refreshed my details in the server and boom, my device got unlocked

T/[email protected]$ said:
when i choose the developer rom it shows "could not verify package" !!
Click to expand...
Click to collapse
Check archive file with WinRAR or 7z, it may corrupted.
Harish_Kumar said:
this is not a fix
The problem lies with Mi Servers
If there's a mismatch of your details on your local device and server, you will get unable to verify error
No matter which rom you try, u going to get the same error
BTW i unlocked on global stable, i had the same issue for like 15days and finally contacted one MIUI device team member he refreshed my details in the server and boom, my device got unlocked
Click to expand...
Click to collapse
If it's lies from Mi servers, then I know what is happening.
My method would help when it contact to Mi server and tell it: "This account logged in to this device, update it to your database". Basically, it "Find device" function will talk to Mi servers to update.
Yeah, any method that make Mi server update will help.

Archmage1809 said:
Check archive file with WinRAR or 7z, it may corrupted.
If it's lies from Mi servers, then I know what is happening.
My method would help when it contact to Mi server and tell it: "This account logged in to this device, update it to your database". Basically, it "Find device" function will talk to Mi servers to update.
Yeah, any method that make Mi server update will help.
Click to expand...
Click to collapse
I have tried that find device stuff, it didnt work
The method is to go to i.mi.com
Login to your account
and enable your mobile number by clicking find device
It didnt work, then i have to contact that guy

Harish_Kumar said:
I have tried that find device stuff, it didnt work
The method is to go to i.mi.com
Login to your account
and enable your mobile number by clicking find device
It didnt work, then i have to contact that guy
Click to expand...
Click to collapse
Well, I have been trying the same thing and basically what he says is true. I tried on all types of roms, until I flashed the latest China Dev (gflobal would prolly work too) rom and tried it again and it worked instantly. So, I dunno what it is, but going to China Dev rom and then trying it fixed it for me instantly.

Harish_Kumar said:
I have tried that find device stuff, it didnt work
The method is to go to i.mi.com
Login to your account
and enable your mobile number by clicking find device
It didnt work, then i have to contact that guy
Click to expand...
Click to collapse
My issue is when I request for unlocking they send me a SMS with different Mi Account ID which does not match with my device Mi Account ID write down several mails but problem persists every time the same.
can you plz let me know to whom to contact regarding the issue.
Thanks in advance
Triggered from my Nexus 10

Harish_Kumar said:
this is not a fix
The problem lies with Mi Servers
If there's a mismatch of your details on your local device and server, you will get unable to verify error
No matter which rom you try, u going to get the same error
BTW i unlocked on global stable, i had the same issue for like 15days and finally contacted one MIUI device team member he refreshed my details in the server and boom, my device got unlocked
Click to expand...
Click to collapse
To whom you contacted, can you give me his details and how can I contact, because I have done all those things mentioned here and there none helps.
Thankyou in advance

All guides and solutions on mi forums and elsewhere are useless. Nothing works.

Seems @Harish_Kumar did not want to disclose anything.
Triggered from rn3

This does not works tried it my self.
Sent from my Nexus 6P using Tapatalk

amitroutray said:
Seems @Harish_Kumar did not want to disclose anything.
Triggered from rn3
Click to expand...
Click to collapse
Sorry, i have been busy these days
I was trying to find that one specific thread on MIUI forum where i contacted that MIUI device team member (his name is naseer - not exactly sure) and i was asked my MI account ID , OS version, device info and he got it fixed within 48 hours
http://en.miui.com/forum-64-1.html
One of the threads in the above link, this happened like around May last week so its been quite few days couldnt exactly find that thread

@Harish_Kumar can you tell me what was your user ID on that forum??
Triggered from rn3

today morning i unlocked my rn3 .. moved to global stable 7.5.3 to global dev rom 6.8.11 via updater and tried to unlock... and boom its unlock in 1st attempt...(sorry for my bad english)

hadiyalkishan said:
today morning i unlocked my rn3 .. moved to global stable 7.5.3 to global dev rom 6.8.11 via updater and tried to unlock... and boom its unlock in 1st attempt...(sorry for my bad english)
Click to expand...
Click to collapse
When did you get the SMS? I received my confirmation SMS before 5 days or so.

MakDroid said:
When did you get the SMS? I received my confirmation SMS before 5 days or so.
Click to expand...
Click to collapse
before 8 days.

Harish_Kumar said:
this is not a fix
The problem lies with Mi Servers
If there's a mismatch of your details on your local device and server, you will get unable to verify error
No matter which rom you try, u going to get the same error
BTW i unlocked on global stable, i had the same issue for like 15days and finally contacted one MIUI device team member he refreshed my details in the server and boom, my device got unlocked
Click to expand...
Click to collapse
which member you contacted
---------- Post added at 11:54 PM ---------- Previous post was at 11:53 PM ----------
hadiyalkishan said:
today morning i unlocked my rn3 .. moved to global stable 7.5.3 to global dev rom 6.8.11 via updater and tried to unlock... and boom its unlock in 1st attempt...(sorry for my bad english)
Click to expand...
Click to collapse
how you go to dev 6.8.11 via updater? i cant see and miui8 rom in updater

ilvmyname said:
To whom you contacted, can you give me his details and how can I contact, because I have done all those things mentioned here and there none helps.
Thankyou in advance
Click to expand...
Click to collapse
amitroutray said:
Seems @Harish_Kumar did not want to disclose anything.
Triggered from rn3
Click to expand...
Click to collapse
I mailed on "[email protected]" regarding the issue with screenshot and MiUnlockTool log. Let's see what happnes. :fingers-crossed::fingers-crossed:
Hopefully it will get fixed asap
Also you can leave comment in this Mi forum thread for the same --> http://en.miui.com/thread-202290-1-1.html

bravonova said:
I mailed on "[email protected]" regarding the issue with screenshot and MiUnlockTool log. Let's see what happnes. :fingers-crossed::fingers-crossed:
Hopefully it will get fixed asap
Also you can leave comment in this Mi forum thread for the same --> http://en.miui.com/thread-202290-1-1.html
Click to expand...
Click to collapse
Mate just apply for a new unlock with a different email ID. and unlock using that. it will work.
all the best.

Having similar issue ...nothing works...

Stuck in Google FRP (Nougat)

Followed these instructions to unlock the bootloader and flash the latest DU to my wife's XT1575: https://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808
DU was buggy so I decided to flash stock nougat using these instructions (left bootloader unlocked): https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
Everything seemed to go fine until we attempted to sign into her existing account and got this error: Unable to sign in to device due to an unknown error. Please try another account or try to sign in again after 24 hours.
Had no idea what that was about, so I Googled it and found out about Factory Reset Protection (FRP). I didn't find much information and the only advice I found was to wait at least 24 hours before trying again. Turned off the phone and waited a full 26 hours before turning it on again--attempted to sign in again and still getting the same error.
Any advice for what to do next?

This was the first link that popped up. Just asking, have you tried this?

antariksh said:
This was the first link that popped up. Just asking, have you tried this?
Click to expand...
Click to collapse
Thanks for the reply. I hadn't tried that yet, but I just did and it didn't seem to work. Everything happened exactly the same even after "removing" the device as per the instructions.
Screenshot from Google account: https://image.ibb.co/dbnjz6/screenshot.jpg

thejukes said:
Thanks for the reply. I hadn't tried that yet, but I just did and it didn't seem to work. Everything happened exactly the same even after "removing" the device as per the instructions.
Screenshot from Google account: https://image.ibb.co/dbnjz6/screenshot.jpg
Click to expand...
Click to collapse
Are you seeing 'Access Removed' in Google Settings?
{
"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"
}
Have you tried logging in any other GMail accounts?

antariksh said:
Are you seeing 'Access Removed' in Google Settings?[/IMG]
Click to expand...
Click to collapse
No. I saw the big red "REMOVE" button, clicked it, and got the confirmation just like the article said, but as you can see from my screenshot, it does not say "Access Removed." next to the device. There is also no more "REMOVE" button. But the interface seems slightly different from the time that article was written so perhaps that's why.
antariksh said:
Have you tried logging in any other GMail accounts?
Click to expand...
Click to collapse
Yes, tried but it won't allow it. It says that a factory reset was done on it and that I need to log in from the account that was on it. But, when I try doing that, of course I get the same error as before: Unable to sign in to device due to an unknown error. Please try another account or try to sign in again after 24 hours.

thejukes said:
No. I saw the big red "REMOVE" button, clicked it, and got the confirmation just like the article said, but as you can see from my screenshot, it does not say "Access Removed." next to the device. There is also no more "REMOVE" button. But the interface seems slightly different from the time that article was written so perhaps that's why.
Yes, tried but it won't allow it. It says that a factory reset was done on it and that I need to log in from the account that was on it. But, when I try doing that, of course I get the same error as before: Unable to sign in to device due to an unknown error. Please try another account or try to sign in again after 24 hours.
Click to expand...
Click to collapse
Not sure what causing it, but try Factory resetting the current Stock ROM or try any other custom ROM with Nano GApps.
P.S: If you currently are on Stock Nougat then flash any Custom ROM based on stock nougat.

I thought FRP didn't work with an unlocked bootloader?

antariksh said:
Not sure what causing it, but try Factory resetting the current Stock ROM or try any other custom ROM with Nano GApps.
P.S: If you currently are on Stock Nougat then flash any Custom ROM based on stock nougat.
Click to expand...
Click to collapse
The phone originally had Marshmallow. The issue with custom ROMs is reliability. Even with DU, which is known for being one of the more stable ROMs, there were a lot of glitches. For example, sometimes the camera app would open, sometimes it wouldn't, which isn't good when you've got a toddler and want to capture moments.
Maybe I'm misinterpreting what you're saying... Are you suggesting that maybe I can somehow circumvent FRP by going from a custom ROM and back to a stock ROM?

Try commenting out this line in build.prop with a # tag
Code:
ro.frp.pst=/dev/block/platform/soc.0/f9824900.sdhci/by-name/frp

antariksh said:
Try commenting out this line in build.prop with a # tag
Code:
ro.frp.pst=/dev/block/platform/soc.0/f9824900.sdhci/by-name/frp
Click to expand...
Click to collapse
Thanks. Unfortunately, I don't know how to do this. I did some Googling and found instructions that won't work for me since I can't get into the phone. Also, looking at the firmware files, I don't see any the files in question.
I called Google and they blamed Motorola and patched me through to their support line. Motorola had no clue what to do. They blamed the legally required "kill switch" but said that it should let me in if I know the right account and password, which I do, but it still doesn't work.

[SOLVED] Redmi A1 (Ice) - Unlock bootloader: Error 0x1002

Hello,
I have recently acquired an Xiaomi Mi A1 device to try LineageOS.
I follow the steps of the official installation guide here: https://wiki.lineageos.org/devices/tissot/install
I'm facing problems to unlock the bootloader. Despite many tries, the command "fastboot oem unlock" return the following error code "0x1002"
ADB version: 1.0.41
fastboot version: 33.0.3-8952118
USB debugging: ON
OEM unlock: ON
I have access to the fastboot mode, the device is listed with adb command "fastboot devices" and an entry appears on Windows Device Manager.
{
"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"
}
Here is the command result:
I have tried to factory reset the phone but the problem still occurs.
Also Mi Unlock tool seems not be usable because Mi Account APK (com.xiaomi.account) is not installed on the phone.
Yoru2647 seems facing the same issue: https://forum.xda-developers.com/t/urgent-help-xiaomi-mi-a1-unlock-bootloader.4295115/post-87995167
Did i miss something? Any ideas about this 0x1002 error code?
Thanks for your advices.

Eren'X said:
Hello,
I have recently acquired an Xiaomi Mi A1 device to try LineageOS.
I follow the steps of the official installation guide here: https://wiki.lineageos.org/devices/tissot/install
Thanks for your advices.
Click to expand...
Click to collapse
You must have a Xiaomi account with the associated phone,
If you don't have an account, create one and use the official Xiaomi tool to unlock the bootloader.
Unlocking bootloader:
https://new.c.mi.com/global/post/101245
https://en.miui.com/unlock/index.html

Thank you for the answer.
I tried that but I'm unable to finish it, the problem is that I cannot bind the Xiaomi account on the phone.
I'm stuck in this step:
The phone was delivered with Android 12 (Go edition) without MIUI's layer. The build number indicate: 12 V13.0.8.0SGMEUXM
That means i have not "Mi Unlock status" on developer options or "Mi Account" on phone settings.
Is it possible to install additional components for bind Mi account on the phone? or any workaround to bypass it?
I desperately tried to install Xiaomi Account APK manually with adb: https://www.apkmirror.com/apk/xiaomi-inc/mi-account/mi-account-r-22-12-26-01-release/
But it failed with the error : "Reconcile failed: Package com.xiaomi.account requires unavailable shared library security-device-credential-sdk.jar; failing!]"
Is it possible to put one of the official MIUI ROM on phone even with a locked bootloader? (like these ones: https://xiaomifirmwareupdater.com/miui/tissot/)

Eren'X said:
Thank you for the answer.
I tried that but I'm unable to finish it, the problem is that I cannot bind the Xiaomi account on the phone.
I'm stuck in this step:
The phone was delivered with Android 12 (Go edition) without MIUI's layer. The build number indicate: 12 V13.0.8.0SGMEUXM
That means i have not "Mi Unlock status" on developer options or "Mi Account" on phone settings.
Is it possible to install additional components for bind Mi account on the phone? or any workaround to bypass it?
I desperately tried to install Xiaomi Account APK manually with adb: https://www.apkmirror.com/apk/xiaomi-inc/mi-account/mi-account-r-22-12-26-01-release/
But it failed with the error : "Reconcile failed: Package com.xiaomi.account requires unavailable shared library security-device-credential-sdk.jar; failing!]"
Is it possible to put one of the official MIUI ROM on phone even with a locked bootloader? (like these ones: https://xiaomifirmwareupdater.com/miui/tissot/)
Click to expand...
Click to collapse
check your model version: My phone/features/version
Example:
220733SG, 220733SH, 220733SI, 220733SL,MDG2, MDI2

Hi,
My model version is: 220733SG

Eren'X said:
Hi,
My model version is: 220733SG
Click to expand...
Click to collapse
Code name ACE not TISSOT.
And the phone is up to date
https://xiaomifirmwareupdater.com/archive/miui/ice/.
If you really want to unlock the bootloader.
Try: download Platform tools and run CMD/Power shell from platform tools folder.
CMD fastboot oem unlock
Power shell ./fastboot oem unlock

NOSS8 said:
Code name ACE not TISSOT.
Click to expand...
Click to collapse
Good catch, I should have paid more attention to this point.
I did not find any LineageOS ROM for it. I assume it is not supported on my phone for now.
However, i tried "fastboot oem unlock" command on both command promp and powershell with and without admin rights.
The result is the same: FAILED (remote: 'Unlock failed - Err:0x1002)
In the next days, i will continue to try few others things like changing USB cable, USB port, computer, ...
The problem also may be linked to FRP mode? i will check that too.
I will share the solution if i success.
Thanks

Eren'X said:
Good catch, I should have paid more attention to this point.
I did not find any LineageOS ROM for it. I assume it is not supported on my phone for now.
However, i tried "fastboot oem unlock" command on both command promp and powershell with and without admin rights.
The result is the same: FAILED (remote: 'Unlock failed - Err:0x1002)
In the next days, i will continue to try few others things like changing USB cable, USB port, computer, ...
The problem also may be linked to FRP mode? i will check that too.
I will share the solution if i success.
Thanks
Click to expand...
Click to collapse
Have you enabled usb debugging?
And why would you want to unlock the bootloader?
may be try https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3695256/

Eren'X said:
Hello,
I have recently acquired an Xiaomi Mi A1 device to try LineageOS.
I follow the steps of the official installation guide here: https://wiki.lineageos.org/devices/tissot/install
I'm facing problems to unlock the bootloader. Despite many tries, the command "fastboot oem unlock" return the following error code "0x1002"
ADB version: 1.0.41
fastboot version: 33.0.3-8952118
USB debugging: ON
OEM unlock: ON
I have access to the fastboot mode, the device is listed with adb command "fastboot devices" and an entry appears on Windows Device Manager.
View attachment 5821853
Click to expand...
Click to collapse
Your device has to be listed like Android Bootloader Interface, this image is referential, taken from the net.
Eren'X said:
Thank you for the answer.
I tried that but I'm unable to finish it, the problem is that I cannot bind the Xiaomi account on the phone.
I'm stuck in this step:
View attachment 5822313
The phone was delivered with Android 12 (Go edition) without MIUI's layer. The build number indicate: 12 V13.0.8.0SGMEUXM
That means i have not "Mi Unlock status" on developer options or "Mi Account" on phone settings.
Click to expand...
Click to collapse
Your device is not Xiaomi Mi A1 (Tissot) but Redmi A1 (Ice), they're very different devices, even one came with Snapdragon when yours come with MediaTek.
Pay attention specially if you think to root it or install some custom ROM on it.
It runs Android One, not Android Go (Edition).
Eren'X said:
Is it possible to install additional components for bind Mi account on the phone? or any workaround to bypass it?
I desperately tried to install Xiaomi Account APK manually with adb: https://www.apkmirror.com/apk/xiaomi-inc/mi-account/mi-account-r-22-12-26-01-release/
But it failed with the error : "Reconcile failed: Package com.xiaomi.account requires unavailable shared library security-device-credential-sdk.jar; failing!]"
Click to expand...
Click to collapse
In Xiaomi devices running Android One, you don't need (nor can't) to bind an account, and the Xiaomi Unlock tool is useless for.
Unlocking bootloader is done through command fastboot oem unlock
Eren'X said:
The problem also may be linked to FRP mode? i will check that too.
Click to expand...
Click to collapse
FRP has nothing to do with.

Eren'X said:
Good catch, I should have paid more attention to this point.
I did not find any LineageOS ROM for it. I assume it is not supported on my phone for now.
However, i tried "fastboot oem unlock" command on both command promp and powershell with and without admin rights.
The result is the same: FAILED (remote: 'Unlock failed - Err:0x1002)
In the next days, i will continue to try few others things like changing USB cable, USB port, computer, ...
The problem also may be linked to FRP mode? i will check that too.
I will share the solution if i success.
Thanks
Click to expand...
Click to collapse
Facing the same issue, FAILED (remote: 'Unlock failed - Err:0x1002) when trying "fastboot oem unlock". I have tried Please share if you find solution thanks

If all the mentioned were met, and the error persists, then try opening the CMD as admin.

NOSS8 said:
Code name ACE not TISSOT.
Click to expand...
Click to collapse
SubwayChamp said:
Your device is not Xiaomi Mi A1 (Tissot) but Redmi A1 (Ice), they're very different devices, even one came with Snapdragon when yours come with MediaTek.
Click to expand...
Click to collapse
Helpful answers.
Finally, i did it.
This article give the soluce: https://www.droidwin.com/unlock-bootloader-on-mediatek-devices-using-mtkclient
"However, there are a few MediaTek devices that don’t accept any of these Fastboot Commands. if your device also falls in this domain, then this guide shall help you out. In this tutorial, we will show you the detailed steps to unlock the bootloader on your MediaTek device using MTKClient."
I followed it step by step and it works!
SubwayChamp said:
Pay attention specially if you think to root it or install some custom ROM on it.
Click to expand...
Click to collapse
Yep, I haven't found a lot of custom ROM who support (ice) codename.
Any better place here to post about "Redmi A1/POCO C50/A1+ (ice)"?
I don't seem to be the only one to make this confusion.

Eren'X said:
Helpful answers.
Finally, i did it.
View attachment 5828629
This article give the soluce: https://www.droidwin.com/unlock-bootloader-on-mediatek-devices-using-mtkclient
"However, there are a few MediaTek devices that don’t accept any of these Fastboot Commands. if your device also falls in this domain, then this guide shall help you out. In this tutorial, we will show you the detailed steps to unlock the bootloader on your MediaTek device using MTKClient."
I followed it step by step and it works!
Yep, I haven't found a lot of custom ROM who support (ice) codename.
Any better place here to post about "Redmi A1/POCO C50/A1+ (ice)"?
I don't seem to be the only one to make this confusion.
Click to expand...
Click to collapse
Well, not, unfortunately, it seems that your device is not popular at all among developers. As a "deposit" of custom ROMs, you should try AFH, SourceForge, PlingOS, apart than from Twitter.
Depending on how many similar are the two linked devices, then you should search for something for them.

The device is young, it's been released in September 2022. I don't expect to find a custom ROM before long time.
The generic system images may be a good alternative in this case, like this one: https://forum.xda-developers.com/t/gsi-13-lineageos-20-light.4509315/
It's not my daily phone, i get it specifically to experiment. I would be careful, but for 80$ it's not a big loss if i brick it.
I will try it when i have more free time.
Thanks for helping

Eren'X said:
The device is young, it's been released in September 2022. I don't expect to find a custom ROM before long time.
The generic system images may be a good alternative in this case, like this one: https://forum.xda-developers.com/t/gsi-13-lineageos-20-light.4509315/
It's not my daily phone, i get it specifically to experiment. I would be careful, but for 80$ it's not a big loss if i brick it.
I will try it when i have more free time.
Thanks for helping
Click to expand...
Click to collapse
Yes, it's not much time since was released, the normal waiting time could be at least 6 months.
Yes, GSIs, are a good alternative.
Don't forget to back up all the partitions available, less userdata, that occupy a really huge size (about 100 GB of storage), and super partition (don't care about). And a last advice, never user format all feature through SPFT, otherwise you'll erase NVRAM partition, fingerprint, LTE signal, IMEI and more.