The nexus one failed to unlock, and locked me out permanently. I used ADB shell to defeat it. Now although my phone is no longer locked. when I check my security setting. Every thing on it is still hightlighted as if it has a set pattern. Is there a way to reset it? I'm afraid to use the change pattern setting, since I don't remember the pattern anymore. Please Help. Thanks.
Try backing everything up and resetting all your settings. May I ask what adb shell command you used for this?
EDIT: If it was a pattern lock why didn't you just use your google account to reset it? This completely disables it.
I used this. The reason I didn't use google account reset is because of the bug that invalid all attempt to reset using google account.
How do I reset my setting?
> ./adb shell
# sqlite3 data/data/com.android.providers.settings/databases/settings.db
sqlite> update system set value=0 where name='lock_pattern_autolock';
sqlite> update system set value=0 where name='lockscreen.lockedoutpermanently';
sqlite> .exit
# exit
is there an update to this by chance? Note you CANNOT use your google login credentials to reset a lock pattern - the bug still exists.
I was able to get out of the lock screen via mobile defense but I want to go back in and get rid of it completely and reset it - any idea how?
thx
bpm2000 said:
is there an update to this by chance? Note you CANNOT use your google login credentials to reset a lock pattern - the bug still exists.
I was able to get out of the lock screen via mobile defense but I want to go back in and get rid of it completely and reset it - any idea how?
thx
Click to expand...
Click to collapse
That 5 tries bug is no longer there. I successfully unlocked the phone with my credentials a few weeks ago.
Its definitely still there - like I said I had this problem today and it wouldn't accept my credentials.
[email protected]
user
neither work.
also, "null" does not work.
ROM in sig.
thx
You're rooted, right?
I'm sorry if this is a stupid question... but can't you shut the phone off, boot into recovery, wipe, then flash the ROM again?
bpm2000 said:
Its definitely still there - like I said I had this problem today and it wouldn't accept my credentials.
[email protected]
user
neither work.
also, "null" does not work.
ROM in sig.
thx
Click to expand...
Click to collapse
Whoa, whoa, whoa. Don't be so quick to say that the "bug" is "definitely still there."
I literally just locked myself out, used my gmail username and password, and it had me immediately draw a new pattern. So there's no such bug on my device..
the bug was on 2.1 and fixed with 2.2.
Ryjabo said:
You're rooted, right?
I'm sorry if this is a stupid question... but can't you shut the phone off, boot into recovery, wipe, then flash the ROM again?
Click to expand...
Click to collapse
I could definitely do that - I just wanted to preserve all my stuff without having to wipe.
Whoa, whoa, whoa. Don't be so quick to say that the "bug" is "definitely still there."
I literally just locked myself out, used my gmail username and password, and it had me immediately draw a new pattern. So there's no such bug on my device..
Click to expand...
Click to collapse
That is great stuff - now did you list your ROM? I'm still on 2.1 like I said, and I *just* had this problem a day or two ago, so for some of us, the problem still exists. I didn't say anywhere it exists on 2.2 or that it exists for everyone now did I? Reading comprehension, its good stuff .
A quick look on the google bug reports would also note that this bug still exists for a great many number of users.
The bug was fixed in 2.2, and the assumption is that you should already be running 2.2 by now, since it has a ton of advantages and not one disadvantage over 2.1. Nobody's going to bother fixing the bug for the old version of OS, slowly being phased out.
Man when did xda get so uppity?
I am not going to run 2.2 yet - CM isn't out yet other than RC and I do not run stock. There are plenty of people who do this. If you're not one of them, don't worry about it and leave the question alone. If you are, and you figured out how to bypass, then please let us know. There are plenty of reasons to be running 2.1 CM/custom ROM over 2.2 stock.
Jack I hope you're on the latest Droid btw, I mean with your line of thinking you should have it right? Why are you in the N1 forum?
bpm2000 said:
Man when did xda get so uppity?
I am not going to run 2.2 yet - CM isn't out yet other than RC and I do not run stock. There are plenty of people who do this. If you're not one of them, don't worry about it and leave the question alone. If you are, and you figured out how to bypass, then please let us know. There are plenty of reasons to be running 2.1 CM/custom ROM over 2.2 stock.
Jack I hope you're on the latest Droid btw, I mean with your line of thinking you should have it right? Why are you in the N1 forum?
Click to expand...
Click to collapse
Whose being uppity? The bug is part of 2.1, the bug was fixed and implemented in 2.2.
Bug prevents you from unlocking phone, the solution is factory reset, or update to 2.2.
So....
Wow.
Lets state it one more time so people get it - bug is still present on 2.1 and fixed on 2.2
Google Account locked
wormbaby11 said:
I used this. The reason I didn't use google account reset is because of the bug that invalid all attempt to reset using google account.
How do I reset my setting?
> ./adb shell
# sqlite3 data/data/com.android.providers.settings/databases/settings.db
sqlite> update system set value=0 where name='lock_pattern_autolock';
sqlite> update system set value=0 where name='lockscreen.lockedoutpermanently';
sqlite> .exit
# exit
Click to expand...
Click to collapse
when i use this command >adb -d shell but it has message "device not found" . i set up the phone driver already. pls help me!!!
bpm2000 said:
Wow.
Lets state it one more time so people get it - bug is still present on 2.1 and fixed on 2.2
Click to expand...
Click to collapse
To be honest I wouldn’t even assume that it was definitely fixed in 2.2. It was inconsistent on 2.1. I actually pointed it out on the general board when I first got my Nexus One (not long after it was released) and I got the “uppity brigade” replying and telling me I was wrong and there was no bug because they couldn’t reproduce it.
Out of interest - has anyone got proof it was fixed in 2.2? Aside from the fact it doesn’t happen on your specific phone (which you know… congrats, but anecdotal evidence is useless). I assume its in a android changelog or similar?
bpm2000 – wish I had an answer but I ended up wiping my phone in the end. Didn’t even know about the ADB method back then. Sorry can’t be of more help. Its an incredibly annoying bug and one that was known about and should have been fixed long before the Nexus and 2.1 came out.
That is frustrating to hear BDH, I tried the adb stuff when it happened looking through the google support boards but I always got stuck on the:
sqlite>
portion and it would never register the commands for some reason. I was lucky that I had set up remote lock/unlock with mobile defense or else I would have had to wipe as well.
Thanks for the relevant reply.
sokhoeut said:
when i use this command >adb -d shell but it has message "device not found" . i set up the phone driver already. pls help me!!!
Click to expand...
Click to collapse
Did you try mounting first?
Related
hi I hope this is the right place for this but I updated my rom to congnitions 2.2 froyo beta 5.5 and now I cant log into my storm 8 accounts it keep telling me that my user id and password are incorrect. I emailed storm 8 and they told me they are aware of the problem and are working on it. I tried that a week ago but they have not given me a response or an answer. So i thought maybe someone here would know more info or even better know how to fix it. I'm soooooo addicted to imobsters I think i need to go to rehab. lol thanks to anyone with any info.
smoeki said:
hi I hope this is the right place for this but I updated my rom to congnitions 2.2 froyo beta 5.5 and now I cant log into my storm 8 accounts it keep telling me that my user id and password are incorrect. I emailed storm 8 and they told me they are aware of the problem and are working on it. I tried that a week ago but they have not given me a response or an answer. So i thought maybe someone here would know more info or even better know how to fix it. I'm soooooo addicted to imobsters I think i need to go to rehab. lol thanks to anyone with any info.
Click to expand...
Click to collapse
I think it has to do with the device ID of the Froyo ROM...Whoever flashes it ends up with the same device ID...DG said there is nothing he can do about it till the Final version is released from Samsung...
I have been working with the higherup techs over there and the issue will not be fixed until the official froyo is released, mainly becasue the issue is not with Storm8 but with our phones. The leaked version of froyo and all of the roms since have the same device ID (which is why your username and passwords do not work); this usually happens with custom roms.
Since Storm8's apps use your device ID to log in and since we all have the same ID, it basically crashes. So unles you flash back to JH7 and somehow extravt your deice ID and import it to Froyo, we are stuck until the official update.
However I am working on doing just that, if it works, I'll post how.
[edit]
Ok I found the solution and it works (same time the other guy in the cog thread did). You have to change you device ID.
WARNING!!! I do not know what other isues this may cause like with market or other apps; so try this at your own risk. If a Dev with more experence with this sees an issue, please post and I'll take this info down. Doing the following requires that your phone is rooted and you have SQlite3 installed.
Go back to JH7 as the device id works there (verify by loading one of the storm 8 apps)
You have to go back to get the correct DeviceID
install this app from Market: http://bubiloop.com/android-tools-device-id
Use DeviceID to get your correct device id, this is the one that works
Reinstall or restore back to froyo
Install DeviceID on Froyo and verify that your ID is now different/wrong
Backup your /dbdata/databases /com.android.providers.settings /settings.db file
Now to change your device id you need to type the following in either adb or connectbot
(note when using SQLite, enter “.help” for instructions and SQL statements always end with a “;”)
su
cd /dbdata/databases/com.android.providers.settings
sqlite3 settings.db
sqlite> insert into secure (’name’, ‘value’ ) values (’android_id’,'what-ever-your-device-id-was-before’);
sqlite> .exit
Reboot
You can verify it changed by running DeviceID again, or just firing up one of the games.
Hi
my device_id from 2.1 and 2.2 are the same Oo
but i cannot log into my storm8 account.
whats wrong?
only the android_id changed. can i insert the id from 2.1 ?
Stooorm said:
Hi
my device_id from 2.1 and 2.2 are the same Oo
but i cannot log into my storm8 account.
whats wrong?
only the android_id changed. can i insert the id from 2.1 ?
Click to expand...
Click to collapse
It is not Device_ID that is the issue, it is Android_ID. Download Android ID Changer from market andf just change some of the numbers and letters (only use a-f). Or flash back to a 2.1 rom, use Android ID Changer from market to backup your correct ID and then go back and restore it.
Your ID should contain both numbers and letters android ID changer is what I use.
Sent from my SAMSUNG-SGH-I897 using XDA App
Mechpilot said:
Your ID should contain both numbers and letters android ID changer is what I use.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
it worked.. thanks im a very happy dude now ;o)
Since android id changer is kinda the topic or is being talked about, will android id changer let me have different storm8 accts on my phone?
Right now i have the app but havnt tryed that yet would be really cool if i could.
I have the app on my kindle fire running cm7 rom.
God Bless
I was searching for a way to debrand my AT&T Samsung Focus S to receive the latest update and was at first surprised to find out that none of the registry editors work and secondly, that I could not find a simple way how to unbrand it.
So here is a simple way for anybody who was looking for the same thing.
Please note that this will unlock and debrand your phone (and I’ve also thrown in the 3G toggle tweak) but after you update to 7.10.8107.79 through Zune, you will no longer be able to use the ProvXML method of deploying registry settings (that we are using here).
All credit goes to Deathbyvegemite who told me what to do and Jaxbot and his WindowBreak Project which helped me figure out how to do it. This is really just a simple modification of his work, so I have to thank him and all the other people that have worked on this.
Okay, so to do this, please follow these steps:
1) Open your mobile browser and go to: http://www.kremese.sk/debrand_focus_s.zip
2) The file will be opened. Follow the instructions and tap on “debrandfocuss.xml”
3) Press Start
4) Navigate to Phone
5) Dial ##634#
6) Type *#9908#
7) Select DebrandFocusS
8) Press Save and Reboot
After that, connect to Zune and you will receive the 8107 update.
Thanks for the hack! I'm completing the Zune update to 8107 now, it should be complete in another minute or so.
I have some wifi issues with the Focus S -- as well as several other people I know and I'm hoping that even though this update does not say it fixes the wifi connection issue, I'm crossing my fingers that it does.
Thank you again, I always love having the latest OS version installed.
-John
jfreiman said:
Thanks for the hack! I'm completing the Zune update to 8107 now, it should be complete in another minute or so.
I have some wifi issues with the Focus S -- as well as several other people I know and I'm hoping that even though this update does not say it fixes the wifi connection issue, I'm crossing my fingers that it does.
Thank you again, I always love having the latest OS version installed.
-John
Click to expand...
Click to collapse
Well, it's been a couple hours since I completed the upgrade to 8107 and I just had the phone reboot during a phone call.
Thanks for the update, but I'll go back to my backup and wait patiently for the official update. Not that this one isn't official, but there maybe special tweaks that need to be done for the Focus S/i937 or AT&T.
-John
To be honest, I don't think it's related to the update, but I can of course understand that you want to be safe.
Doesn't seem to work for me. Not seeing any updates.
onesikpuppy said:
Doesn't seem to work for me. Not seeing any updates.
Click to expand...
Click to collapse
Do you have an unlocked device? If you have a registry editor you can check under this path:
HKEY_LOCAL_MACHINE\System\Platform\DeviceTargetingInfo\MobileOperator
The string value should be "000-88". If it still says "ATT-US" then please try again and follow the instructions precisely.
Yes, unlocked. Do you know of a registry editor that works on Focus S?
onesikpuppy said:
Yes, unlocked. Do you know of a registry editor that works on Focus S?
Click to expand...
Click to collapse
There are a couple that work, but currently only in read-only mode.
This one is the most user friendly I think:
EDIT: Argh, can't post outside links. Please google "Registry Editor for Windows Phone 7 Beta Testing".
Got the registry editor working. It still says ATT. I've gone through the process 5 times now. Each time it tells me "debrandfocussProvisioning succeeded" but after the reboot it's back to ATT-US.
but does this just give the OS update? Does this also give you the firmware update?
is the focus s out there for anyone else but ATT?
Not sure about the firmware update, but my firmware version after the update is: 2103.11.10.1.
onesikpuppy said:
Got the registry editor working. It still says ATT. I've gone through the process 5 times now. Each time it tells me "debrandfocussProvisioning succeeded" but after the reboot it's back to ATT-US.
Click to expand...
Click to collapse
Can you please check which version of the Diagnosis tool you have?
ver.0923
Thanks
Well, that's the same as mine. Are you sure you are not on 8107 already?
One thing you can try is to pull out your sim card and see if it works then.
I'll try pulling the sim
Sent from my SGH-i937 using XDA Windows Phone 7 App
Sim pull didn't help
Sent using xda premium
I have the samme issue that onesikpuppy with the same parameters in his attached thumbnails.
I bought a demo phone, can anyone help me get it out of the mode it's in?
works wonderfully. thanks to op
whats the diffrent betwween this unlock to the windows break unlock?
can i use registry editor to edit some enteries?
thank you
I recently purchased a nexus 6 off ebay, likely a mistake, and now that I try to run the setup i can't because i'm not the original account on the phone. Is there anything I can do to get past this step, remove the old user account and add myself to the phone? I know the security measure was put in for a reason, but it definitely makes it hard when someone like me gets the phone and is now stuck with a good looking paperweight. I have tried contacting the seller and getting them to provide me with their info for the purposes of setting it up but they are reluctant to offer that up. Unsurprisingly.
Any help would be appreciated.
Thank you,
Fk
fkoulbot said:
I recently purchased a nexus 6 off ebay, likely a mistake, and now that I try to run the setup i can't because i'm not the original account on the phone. Is there anything I can do to get past this step, remove the old user account and add myself to the phone? I know the security measure was put in for a reason, but it definitely makes it hard when someone like me gets the phone and is now stuck with a good looking paperweight. I have tried contacting the seller and getting them to provide me with their info for the purposes of setting it up but they are reluctant to offer that up. Unsurprisingly.
Any help would be appreciated.
Thank you,
Fk
Click to expand...
Click to collapse
I'm sorry but the only way is with that password. This is fault of the seller, they did a factory reset without removing their Google account. If the seller won't help you, contact eBay resolution center.
@fkoulbot,
Unfortunately, plenty of threads here with the same situation.
What @Evolution_Freak said, or open a PayPal claim. Device "Significantly Not As Described". You'll get your money back.
Or, just post it back to him at his expense, and get him to do it properly.
"Hi,
I understand that you feel uncomfortable giving me your Google password. Since the phone is unusable without it, I will have to consider opening a paypal dispute.
To avoid this however, if you offered to cover the cost of 2 way postage of the device (+insurance), I could send the device to you to log into and remove your account properly before resetting and returning to me."
fkoulbot said:
I recently purchased a nexus 6 off ebay, likely a mistake, and now that I try to run the setup i can't because i'm not the original account on the phone. Is there anything I can do to get past this step, remove the old user account and add myself to the phone? I know the security measure was put in for a reason, but it definitely makes it hard when someone like me gets the phone and is now stuck with a good looking paperweight. I have tried contacting the seller and getting them to provide me with their info for the purposes of setting it up but they are reluctant to offer that up. Unsurprisingly.
Any help would be appreciated.
Thank you,
Fk
Click to expand...
Click to collapse
Hey, buddy. I had the same thing happen to me on Swappa. Fortunately the guy was willing to give me his password... BUT in the 2 hours it took him to respond to my dilemma, I had already found a way around it. (Take note that my bootloader was already unlocked when I received the device.) Here's what I did.....
I tried flashing a couple different ROMs to no avail.
Then I realized it was because I was flashing 5.1 ROMs.
So, I found a 5.0.1 ROM that doesn't have the reactivation built in, flashed it, got it set up, then flashed a new 5.1 ROM. It worked for me but YMMV. I do believe having an unlocked bootloader in the first place helped. Hope that helps.
hyst3rical said:
Hey, buddy. I had the same thing happen to me on Swappa. Fortunately the guy was willing to give me his password... BUT in the 2 hours it took him to respond to my dilemma, I had already found a way around it. (Take note that my bootloader was already unlocked when I received the device.) Here's what I did.....
I tried flashing a couple different ROMs to no avail.
Then I realized it was because I was flashing 5.1 ROMs.
So, I found a 5.0.1 ROM that doesn't have the reactivation built in, flashed it, got it set up, then flashed a new 5.1 ROM. It worked for me but YMMV. I do believe having an unlocked bootloader in the first place helped. Hope that helps.
Click to expand...
Click to collapse
Thanks so much for that info. I had actually received and tried that but because it wasn't unlocked i was stuck. I did get the login info but now worried that they somehow have access to the phone. I noticed the label of a "group" of apps on my home screen was randomly changed. I did DL an antivirus app and it found something but I'm still worried about the security of the phone. Do you happen to have any suggestion on the best thing i can do to absolutely clear any of the old account information etc?
fkoulbot said:
Thanks so much for that info. I had actually received and tried that but because it wasn't unlocked i was stuck. I did get the login info but now worried that they somehow have access to the phone. I noticed the label of a "group" of apps on my home screen was randomly changed. I did DL an antivirus app and it found something but I'm still worried about the security of the phone. Do you happen to have any suggestion on the best thing i can do to absolutely clear any of the old account information etc?
Click to expand...
Click to collapse
First thing I would do is go into Settings -> Accounts and remove the Google account that it was originally linked on. Then add your own. Do a factory reset, and you should be fine. If you want to go the extra mile, set up the reactivation lock under your account. I do believe that should clear any permissions he may still have as they would be linked to his Google account.
fkoulbot said:
Thanks so much for that info. I had actually received and tried that but because it wasn't unlocked i was stuck. I did get the login info but now worried that they somehow have access to the phone. I noticed the label of a "group" of apps on my home screen was randomly changed. I did DL an antivirus app and it found something but I'm still worried about the security of the phone. Do you happen to have any suggestion on the best thing i can do to absolutely clear any of the old account information etc?
Click to expand...
Click to collapse
Boot to bootloader.
Fastboot format userdata
(Note that this will wipe everything, including contents of SDcard.
I would lock then unlock bootloader which would wipe the phone and then go to google and download latest builds and flash the phone to factory stock. Boot in, if there isn't anything funky, then I would made a backup of the stock and flash custom ROMs from that point. I like to check first if it works bone stock wiped before tinkering. That way if anything is still wrong with it I know who's at fault.
farangutan said:
I would lock then unlock bootloader which would wipe the phone and then go to google and download latest builds and flash the phone to factory stock. Boot in, if there isn't anything funky, then I would made a backup of the stock and flash custom ROMs from that point. I like to check first if it works bone stock wiped before tinkering. That way if anything is still wrong with it I know who's at fault.
Click to expand...
Click to collapse
Why would you lock the bootloader? If you want everything wiped do > fastboot format userdata
cam30era said:
Why would you lock the bootloader? If you want everything wiped do > fastboot format userdata
Click to expand...
Click to collapse
Well, more likely if it's locked I would just unlock, but yes the act of flashing it to factory images will wipe in one go. Relocking and unlocking is redundant.
Guys does anyone confirm that is any way you can remove the Google Account Lock on Nexus 6 that the previous seller didn't remove the Goggle Account?
Thanks in advance!
Im having the same dang issue!! Hopefully I can get it flashed since sell won't give me password.
I have recently purchased a used Nexus 6 and I have just noticed that my phone may be compromised. It took a while to set up the phone as i wasn't getting the original account info to complete the setup, but now that I have run the setup, and set up a 'group' on the home screen that I labelled 'Entertainment' which holds a couple games. I see now, that the label has been changed to 'D's Sacs Was DQ'. Why would this happen and or what can be done to secure my phone? Please help!
Thank you
FK
fkoulbot said:
I have recently purchased a used Nexus 6 and I have just noticed that my phone may be compromised. It took a while to set up the phone as i wasn't getting the original account info to complete the setup, but now that I have run the setup, and set up a 'group' on the home screen that I labelled 'Entertainment' which holds a couple games. I see now, that the label has been changed to 'D's Sacs Was DQ'. Why would this happen and or what can be done to secure my phone? Please help!
Thank you
FK
Click to expand...
Click to collapse
LMAO! Really?! Did you factory wipe it? Is it stock or boot loader unlocked? Is it rooted?
fkoulbot said:
I have recently purchased a used Nexus 6 and I have just noticed that my phone may be compromised. It took a while to set up the phone as i wasn't getting the original account info to complete the setup, but now that I have run the setup, and set up a 'group' on the home screen that I labelled 'Entertainment' which holds a couple games. I see now, that the label has been changed to 'D's Sacs Was DQ'. Why would this happen and or what can be done to secure my phone? Please help!
Thank you
FK
Click to expand...
Click to collapse
Flash userdata.img and erase and flash cache.img in fastboot (if you have a unlocked bootloader) and after that data factory reset in recovery and reboot. That all you can you do.
Flashing it to ensure it was wiped of anything on it prior to use, since it was used, should have been the first thing done to it (ensuring ti wasn't locked to an account or you would have issues afterwards).
gee2012 said:
Flash userdata.img and erase and flash cache.img in fastboot (if you have a unlocked bootloader) and after that data factory reset in recovery and reboot. That all you can you do.
Click to expand...
Click to collapse
How do i know if I have an unlocked bootloader? I'm worried if i do a factory reset I'd be locked out if their account is still considered the original.
fkoulbot said:
How do i know if I have an unlocked bootloader? I'm worried if i do a factory reset I'd be locked out if their account is still considered the original.
Click to expand...
Click to collapse
To get in booltoader/fastboot mode:
1. with adb, type in cmd: adb reboot bootloader
2. Manualy: power down the phone and press both volume up and down + power.
RW-1 said:
Flashing it to ensure it was wiped of anything on it prior to use, since it was used, should have been the first thing done to it (ensuring ti wasn't locked to an account or you would have issues afterwards).
Click to expand...
Click to collapse
That was an issue when I began. I needed their account info to log in during setup but then was able to add my info.
fkoulbot said:
That was an issue when I began. I needed their account info to log in during setup but then was able to add my info.
Click to expand...
Click to collapse
Try logging in and boot the phone with the original account, delete the account and then perform a data factory reset in recovery. Then boot up with your account and that should do it usualy.
fkoulbot said:
How do i know if I have an unlocked bootloader? I'm worried if i do a factory reset I'd be locked out if their account is still considered the original.
Click to expand...
Click to collapse
Or even easier... do you see a little icon of an unlocked lock at the bottom of the screen when you boot your phone?
Or, something much less nefarious...
I would think that it could be possible you may have placed the phone in a pocket with the home screen showing (or some similar action) and the folder got renamed with random presses that also triggered random words through autocomplete. Been there, done that.
It was me.. I hacked you.. But once I was in, I couldn't think of anything to do, so I renamed a folder. Was gonna key log your bank details but this was way better
I hack phones and change events in the calendar app. Because I like confusion and making people late.
Whenever I setup Android for the first time, or setup again after resetting my phone, I'm always faced with the same problem. I'm unable to manually perform a backup to Google Drive. The normally blue "Back up now" button is grayed out, and in place of the date and time of the last backup is a message saying, "Waiting to back up..." This message never goes away, even after waiting for days, and a backup never takes place.
I tried every solution I found in my Google searches, but nothing worked except the solution I'm sharing, and it requires ADB (Android Debug Bridge).
How to setup and use ADB (Android Debug Bridge)
Once you have an ADB connection to your phone, enter the following commands exactly as displayed:
Code:
[SIZE="4"]adb -d shell
bmgr enabled
bmgr list transports
bmgr backupnow --all[/SIZE]
This should trigger your first Google Drive backup which you should allow to complete. Once the backup completes, reboot your phone, and return to the Backup screen. The "Back up now" button should now be blue and enabled, allowing you to manually backup to Google Drive at will. Additionally, Android's automatic daily backups should now work normally as well.
I removed my screen lock and I could back up already.
gtasaryder said:
I removed my screen lock and I could back up already.
Click to expand...
Click to collapse
Hi Gtasaryder. Yes, I tried this hack too and it worked, but it cannot be a permanent solution because it sacrifices one form of security for another, and this is not viable. Imagine having to leave you phone unlocked just so you can backup. It is like having to open your doors if you want to close your windows to keep thieves out. It's not a practical solution.
thanks for sharing, the only solution keeps working for me!!
andypongom said:
thanks for sharing, the only solution keeps working for me!!
Click to expand...
Click to collapse
You're welcome, Andy. I'm glad I could help.
Thank you!!!!
nemiroN said:
Thank you!!!!
Click to expand...
Click to collapse
Hi nemiroN. You're welcome. I'm glad it worked for you.
i have the same problem on the xiaomi redmi note 9, will they solve it?
Worked for my Xiaomi Poco x3 nfc. Thank you so much!
gtasaryder said:
I removed my screen lock and I could back up already.
Click to expand...
Click to collapse
Same, and I'm able to Google Backup now... when I turn screen locks back on though won't future Backups be restricted?
This is a Xiaomi bug, surely?