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.
Related
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.
Hello,
Back in August of 2015 I bought a FreedomPop Samsung Galaxy S4 which I used with FreedomPop up until just recently when I signed up with RingPlus, ported my old FreedomPop number to my R+ account and then deactivated my FreedomPop account. OK, so.. my problem is is that now I can't use R+ because it requires me to update my PRL, but I can't. I get this error: "The PRL update could not be completed. Please try again later. If the problem persists, you may need to contact Customer Service. Error: Connection Error (6)"
Now, in the past when I was trying to root my phone I really screwed things up and ended up having to install new Firmware. You can find more information about that here: http://forum.xda-developers.com/galaxy-s4-sprint/help/caught-boot-loop-rooting-t3304144
Any help would be greatly appreciated, especially since my phone is practically useless at the moment.
-Chuck
Try dialing ###72786#
{
"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"
}
bilgerryan said:
Try dialing ###72786#
Click to expand...
Click to collapse
When I tried that, the number disappeared when I added the last #. And it still won't let me update the PRL.
I think I know why that didn't work. I'm suppose to dial ##72786#, not ###72786#. I'm assuming you meant for me to reprovision my phone?
Anyway, I did that and seemed to be working fine, but then when I tried to update the PRL it, took me to hands free activation. Same when I tried to update my profile as well. How do I go about avoiding this?
I could really use some help here please.
Chuck38 said:
I could really use some help here please.
Click to expand...
Click to collapse
With what? If it updated profile and PRL them you are done. You only have to do this about once a month, not every day.
Alright. I should probably contact Ringplus directly about my other problem here.
Sorry for bothering you and thanks for the help.
Chuck38 said:
Alright. I should probably contact Ringplus directly about my other problem here.
Sorry for bothering you and thanks for the help.
Click to expand...
Click to collapse
Sorry, I missed that. I recommend Odining TWRP and then flashing the SuperSU zip in recovery for rooting.
bilgerryan said:
Sorry, I missed that. I recommend Odining TWRP and then flashing the SuperSU zip in recovery for rooting.
Click to expand...
Click to collapse
How would I go about Odining TWRP?
I've only used Odin to re-install my Firmware.
Chuck38 said:
How would I go about Odining TWRP?
I've only used Odin to re-install my Firmware.
Click to expand...
Click to collapse
Download TWRP and run it in the PDA slot.. Make sure to uncheck Auto Reboot.
bilgerryan said:
Download TWRP and run it in the PDA slot.. Make sure to uncheck Auto Reboot.
Click to expand...
Click to collapse
Alright. TWRP has been installed, as well as SuperUS. Just checked with Root Checker and my phone has been properly rooted.
However.. the problem still persists. I still am unable to get RingPlus to work with my phone. Perhaps because I can't update the PRL, it keeps taking me to hands free activation, or perhaps there's something else going on. I will see if I can contact RingPlus and see if they know what's wrong.
Thank-you for your assistance, I will report back if I get this figured out.
Welp, I'm pretty sure I messed this up. Found a YouTube video (not even sure which one at this point, sorry) that was recently uploaded detailing how to root a Galaxy S7 Edge. Downloaded the firmware, opened up Odin, put it into Download mode, selected the Qualcomm firmware version for the AP field, and click start. It flashed correctly (according to Odin) and the phone began restarting and didn't stop. Just show's the "Galaxy S7 Edge" screen, goes black, and starts over.
I tried downloading the stock firmware for Sprint, load the appropriate files into Odin, and click start, I then get this output:
{
"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"
}
And on the phone, I see:
My build number is NRD90M.G935PVPS5BRA1, kernel version 3.18.31-12623509
I'm fairly certain this is entirely something that could have been avoided had I read more guides or instructions. Unfortunately, here I am! I really appreciate any help anyone can give me. I've been Googling and reading all morning, and I'm sure the answer is there, but I'll be damned if I can see it.
While I don't think there's much important info here, I figure it's at least showing some more in terms of version and name:
Your binary boot is v5. It won't work and you can't downgrade at the moment. What are you trying to do with root? There are many non root alternatives. To fix your bootloops, odin the stock firmware again.
Make sure you have the special version of odin too.
Also, download the stock firmware again. Try updato.com or plug the firmware version into android file host
lvpre said:
plug the firmware version into android file host
Click to expand...
Click to collapse
I don't know why I did not put together the relevance of firmware and the build number, but that was the issue all along it seems! After a dozen different cables, ports, and firmware versions I finally realized I needed to plug in the whole build number to find the firmware for that build specifically. Once flashed, the phone rebooted, asked to restore the backup based on the Google account, and it can text and make calls! Thank you so much for the help, I really appreciate it. I'll be sure to read and research a lot more before the next attempt to root a phone.
reddeth said:
I don't know why I did not put together the relevance of firmware and the build number, but that was the issue all along it seems! After a dozen different cables, ports, and firmware versions I finally realized I needed to plug in the whole build number to find the firmware for that build specifically. Once flashed, the phone rebooted, asked to restore the backup based on the Google account, and it can text and make calls! Thank you so much for the help, I really appreciate it. I'll be sure to read and research a lot more before the next attempt to root a phone.
Click to expand...
Click to collapse
Glad it worked out...we all have been there at some point. Any reason you wanted to root? There may be some non-root alternatives available.
lvpre said:
Glad it worked out...we all have been there at some point. Any reason you wanted to root? There may be some non-root alternatives available.
Click to expand...
Click to collapse
Mainly I was just wanting to get rid of the stock Sprint bloatware that you can't uninstall by default. If you've got any other suggestions for it, they're very much appreciated!
I'm on latest Oxygen OS 10.5.6 IN11AA my device is IN2025 and the fingerprint doesn't work. I tried everything even factory reset. I can't get the first fingerprint step, it shows this message when i click next to go scan my finger.
{
"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"
}
"enrollment was not completed | Fingerprint registration error, please try again" I tried without screen protector and it still didn't work. Any help would be appreciated.
There is an in depth thread about this already, literally above this one in the same section.. Please check that thread for answers
dladz said:
There is an in depth thread about this already, literally above this one in the same section.. Please check that thread for answers
Click to expand...
Click to collapse
my bad, sorry i saw the thread but i though it was about something else so i never checked it out
username2077 said:
my bad, sorry i saw the thread but i though it was about something else so i never checked it out
Click to expand...
Click to collapse
No worries.
They're looking at the persist partition, not sure if it's correct but they're looking into it , I think a solution may be close
Anytime since this fingerprint issue? I'm updated to .58 but still no fix...?
bigjailerman said:
Anytime since this fingerprint issue? I'm updated to .58 but still no fix...?
Click to expand...
Click to collapse
have you tried to remove any magisk module reboot uninstall magisk reboot?
I had the exact same issue. On global
I downgraded magisk from canary to stable and fixed the fingerprint issue.
mlkemac said:
I had the exact same issue. On global
I downgraded magisk from canary to stable and fixed the fingerprint issue.
Click to expand...
Click to collapse
Had you restored your persist partition prior to doing this?
From what I've been reading the cause is one of a few things
Using Canary is top of the list of potential causes.
Also I would recommend banking up you're personal persist partition and only using Magisk 20.4 for the time being as this has proved to fix it for some..
Up til this point the only definite is that we should all back up our own persist partitions prior to making changes like root ROMs / mods.
Can't be sure but I think each person's persist has something unique per device. So another person's persist part won't fix someone else's as it doesn't identify.
Least this is what I've gathered anyway.
This will be ironed out but if it's not happening with stock devices then I can't see OnePlus going out of their way to fix it.
So it's on us as a community to pull together, if you have any definitive input for this and a replicable fix then post it in the other threads too, this really needs to be common knowledge or it'll be the one thing that plagues this device.
I've held off rooting and unlocking due to this issue, all sensor info is kept in the persist part, but only your persist can fix your fp reader.
I'm having the same issue. Already factory reset a couple of times. Downgraded to 10.5.4 and 10.5.5 still nothing
I started the replacement RMA process last night. Hopefully this new loaner phone program I get something decent to use till I get my replacement.
polo2883 said:
I'm having the same issue. Already factory reset a couple of times. Downgraded to 10.5.4 and 10.5.5 still nothing
I started the replacement RMA process last night. Hopefully this new loaner phone program I get something decent to use till I get my replacement.
Click to expand...
Click to collapse
are you sure you were not running Magisk Canary?
Nekromantik said:
are you sure you were not running Magisk Canary?
Click to expand...
Click to collapse
I have reset to factory, and also tried the unbrick tool to downgrade the OS to 10.5.4. Nothing Magisk related is currently installed.
I have stable magisk 20.4 and today I found out the fingerprint scanner many times has delay, especially when screen is off ( ambient display).
I recently found at the dumps a box of t350's 6/18 didnt like combination flashing the mdm away/new firmware install. 3 failed the same way while putting on newest firmware with odin now they say mdm mode in odin again and i have no debug access. 1 black screens in bootloader and when booting no debug access mdm mode in odin again. BUT ! I have 1 with debug access and see it in ADB BUT it fails to install due to signature verifcation of the ROM's I've tried. I think the later is savable EZ just need a a little help getting TWRP onto it I guess and I'm good. I'll worry about the others later but any ideas ? my brain hurts from trying cables/roms/adb versions lol
Maybe the rom is incorrect have you checked the region and model number etc?
Kenora_I said:
Maybe the rom is incorrect have you checked the region and model number etc?
Click to expand...
Click to collapse
the issue is the MDM mode seems like, it fails to write. only time i every got them to flash was after the combination flash the download menu popped up very slow after it was working hard to explain..... i have 7.1.1 on all the working one's which seem finebut i ****ed up i shouldve TWRP them first, one of them i successfully did get twrp on and lineage after the fact and i tried again with now another boot looping tablet SMH. idk what i did to do it the first time
TDIfrogman said:
the issue is the MDM mode seems like, it fails to write. only time i every got them to flash was after the combination flash the download menu popped up very slow after it was working hard to explain..... i have 7.1.1 on all the working one's which seem finebut i ****ed up i shouldve TWRP them first, one of them i successfully did get twrp on and lineage after the fact and i tried again with now another boot looping tablet SMH. idk what i did to do it the first time
Click to expand...
Click to collapse
no matter what i write to it twrp any firmware just fails like it did when it was mdm locked
Could you provide ODIN logs?
{
"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"
}
it shows mdm locked and the odin log reflects that BUT they where unlocked at some point im, afraid to try and flash the other and they'll end up like this one
TDIfrogman said:
View attachment 5364601
Click to expand...
Click to collapse
They might have NAND flash erros because they arent able to write to it.
Kenora_I said:
They might have NAND flash erros because they arent able to write to it.
Click to expand...
Click to collapse
hmmmm how can i fix it ?
It could be hardware issue, I'm not sure how to fix hardware issues. Thats probably the reason they were all together in a box.
no they where in a box because they came from a school and they didn't take knox off, there was 1000+ of them I just grabbed a tray full they have these crazy polycarbonate cases on them too with security screws. they all worked until i flashed knox away with varying results 12/18 working fine 18 worked prior but in knox
Oh that info is noted.
May I help you later. Its pretty late and I have to get off.
Ill help in the mornin