Related
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.
Greetings everyone!
Few weeks ago, I gave my device to a friend of mine to manually update it. Something went wrong so he decided not to go any further. Yday i tried to "Factory reset", after reset some error pop'd in the left upper corner of the phone.It says:
[LGE_SECURITY] ERROR: boot image signature
Critical failure: Unable to start kernel.
Unrecoverable bootloader error (0x00000002).
Anyone had any similiar or even the same problem as i am facing right now? Thanks in advance.
best regards, Milan
Guy didn't know what he was doing apparently. Your handset is still locked and he apparently tried installing a 3rd party ROM, lemme guess, you wanted a newer version of Android than 4.1., which is a reasonable enough thing. Problem is that out of the box you can't do that because it only boots images signed by LG and they abandoned development after releasing 4.1 and a couple of minor point releases. You aren't totally screwed but if you were having somebody else do it for you, you might need to get some help. You can find the details elsewhere here, or more likely point a more skilled friend at it, but here it is in a nutshell.
You need to get LG's official updating software (from the LG website) and you need to fiddle with it a bit until you get it to do a rescue because it expects to have already paired up with the phone while it was still working. If you already had it installed, great because it will make it easier. Anyway, you will probably have to manually pick your model and input the IMEI since it won't already know those things and it will go out and fetch the most recent image. You will push VOL Down and insert the USB cable from a powered down state, it will then do the rest. Good chance you will even retain your data unless that 'factory reset' you mention actually succeeded.
Of course that will only get you back to stock 4.1. Read around for the official way and several un-official ways to unlock your boot loader. Once that is done you can install a better recovery and then a newer version of Android. But the first step is to restore the stock software since you have to have a running phone to be able to unlock it.
And no, nobody has ever been able to explain WHY they lock them, but every single manufacturer seems determined to do it, chipmakers put a lot of work and ad copy into how extensive and unbreakable the locks on their newest chip is, etc. And then they either bow to customer demand and add an unlock feature or we here at xda do it for them... as a courtesy of course. Truly we do live in the asylum. Wonko the Sane was onto something.
Hi - apologies first of all if this is covered elsewhere in the forums.
I purchased a brand new Nexus 6 directly from Motorola this week as they had slashed the price down to just £309 for the 64gb. It arrived Monday. I turned it on, signed into my network etc. it starting updating apps. Then it said that Android 5.1.1. was available so I downloaded it and proceeded to install. About halfway through the installation it crashed. My phone is now stuck on continually booting up and saying 'optimising xxx apps'. After a bit of research, I found that this was a common problem as 5.1.1. was trying to update and some apps were incompatible. So I read many forums and booted into Recovery mode, wiped the cache, wiped data and did a factory reset, but it still won't work.
I called Motorola who told me that they have had many of their Nexus 6s do this and all they could do was to refund me the phone as they now are out of stock.
Further research led me to read about 'flashing' the phone so I downloaded Wugfresh but I cannot get into the phone to enable me to debug. After many hours today I have come to the conclusion that I am never going to be able to use my new phone which I am gutted about.
My question is, is there anyway to flash the phone without enabling debugging because I cannot get into the main menu because all if does is just keep optimizing apps?
Many thanks for reading and any assistance would be greatly appreciated.
bacon_roll said:
Hi - apologies first of all if this is covered elsewhere in the forums.
I purchased a brand new Nexus 6 directly from Motorola this week as they had slashed the price down to just £309 for the 64gb. It arrived Monday. I turned it on, signed into my network etc. it starting updating apps. Then it said that Android 5.1.1. was available so I downloaded it and proceeded to install. About halfway through the installation it crashed. My phone is now stuck on continually booting up and saying 'optimising xxx apps'. After a bit of research, I found that this was a common problem as 5.1.1. was trying to update and some apps were incompatible. So I read many forums and booted into Recovery mode, wiped the cache, wiped data and did a factory reset, but it still won't work.
I called Motorola who told me that they have had many of their Nexus 6s do this and all they could do was to refund me the phone as they now are out of stock.
Further research led me to read about 'flashing' the phone so I downloaded Wugfresh but I cannot get into the phone to enable me to debug. After many hours today I have come to the conclusion that I am never going to be able to use my new phone which I am gutted about.
My question is, is there anyway to flash the phone without enabling debugging because I cannot get into the main menu because all if does is just keep optimizing apps?
Many thanks for reading and any assistance would be greatly appreciated.
Click to expand...
Click to collapse
You could try and flash a flash a factory image via fastboot...
draa2711 said:
You could try and flash a flash a factory image via fastboot...
Click to expand...
Click to collapse
No, he can't try, he has his bootloader locked.
OP, this thread is a classic case of why the first thing anyone should do with this device, even if not planning to root or otherwise modify it, is to enable developer options in settings and enable both USB Debugging and OEM Unlocking. Without both enabled there's no way to resolve your problem, and unfortunately you'll need to contact Motorola and arrange a return, since they are out of stock.
Once you get your money back, look on Swappa for a used device. You may be able to get a device that way at a lower price than what Motorola offers.
Strephon Alkhalikoi said:
OP, this thread is a classic case of why the first thing anyone should do with this device, even if not planning to root or otherwise modify it, is to enable developer options in settings and enable both USB Debugging and OEM Unlocking. Without both enabled there's no way to resolve your problem, and unfortunately you'll need to contact Motorola and arrange a return, since they are out of stock.
Once you get your money back, look on Swappa for a used device. You may be able to get a device that way at a lower price than what Motorola offers.
Click to expand...
Click to collapse
Thanks for your advice, but I had no idea, probably like so many others who aren't as clued up on Android that USB Debugging even existed. I just bought a phone that I wanted that now is no good to me having never been able to use it because of a bug in 5.1.1. I am returning to Motorola for refund.
Without wanting to raise false hopes, there is a thread in this forum where the OP says he recovered his device even though the bootloader was locked (he was certain of it, he said...), other people replying that this was impossible, and yet they eventually seemed to accept that it might be. My bootloader has been unlocked since day one, and I don't remember if there was an "Allow OEM unlock" option in Settings - the same thread had discussion about Marshmallow not having it. I suppose this N6 is still on Lollipop, so maybe a red herring...
I'll see if I can find the thread for reference, but in the meantime does anyone recognise the thread I mean?
bacon_roll, since I'm vegetarian I shouldn't be helping you but have you tried Wugfresh's option of "Phone is bricked/bootlooping"? I think all it does is to reboot the device into bootloader anyway, but I think this might be worth a go if you haven't already tried it. You did mention that you've booted into recovery, but you don't mention bootloader mode.
draa2711 said:
You could try and flash a flash a factory image via fastboot...
Click to expand...
Click to collapse
Thanks. As per my post, I can't because the phone is locked.
dahawthorne said:
My bootloader has been unlocked since day one, and I don't remember if there was an "Allow OEM unlock" option in Settings - the same thread had discussion about Marshmallow not having it. I suppose this N6 is still on Lollipop, so maybe a red herring...
Click to expand...
Click to collapse
You could check in the About Phone menu to see what version you're on.
Both Android 5.x and Android 6.x have an OEM Unlocking toggle in Development Options. I know because I followed my own advice given above in my previous post in order to flash the latest Android 6.0.1 ROM to the device, and then checked Developer Options afterward.
dahawthorne said:
Without wanting to raise false hopes, there is a thread in this forum where the OP says he recovered his device even though the bootloader was locked (he was certain of it, he said...), other people replying that this was impossible, and yet they eventually seemed to accept that it might be. My bootloader has been unlocked since day one, and I don't remember if there was an "Allow OEM unlock" option in Settings - the same thread had discussion about Marshmallow not having it. I suppose this N6 is still on Lollipop, so maybe a red herring...
I'll see if I can find the thread for reference, but in the meantime does anyone recognise the thread I mean?
bacon_roll, since I'm vegetarian I shouldn't be helping you but have you tried Wugfresh's option of "Phone is bricked/bootlooping"? I think all it does is to reboot the device into bootloader anyway, but I think this might be worth a go if you haven't already tried it. You did mention that you've booted into recovery, but you don't mention bootloader mode.
Click to expand...
Click to collapse
Hi - please get my hopes up, I really want to keep this phone if I can
Without sounding like a complete nerd, what is the difference between recovery and bootloader mode?
When I scroll through the options with both arrows pressed and power button, I have START, RESTART BOOTLOADER, RECOVERY MODE, POWER OFF, FACTORY, BARCODES, BP TOOLS, QCOM & BOOTLOADER LOGS
I have done factory wipe/cache/restart bootloader etc.
How do I boot into bootloader mode please.
Thank you.
Overly simplistic reply here, but it should be enough to answer the question.
The bootloader prepares the system for booting. Once it's done its work it hands off control of the system to Android's kernel. Recovery is a mini operating system used to initiate low level functions such as wiping the on-board storage. The screen you describe I believe is the bootloader interface, hence why you have a "Restart Bootloader" option instead of "Start Bootloader".
You can probably save some serious money by returning and buying off swappa really. I just broke my N6 and couldn't find one in stock but, used swappa to find one around $260 that was only used for 2 weeks.
If you already have Wugfresh's Nexus Root Toolkit installed, use the "Install & test drivers" button to make sure that you have all your drivers installed properly. If all is ok, although I know this won't be popular advice, then start with the "My device is soft-bricked", then try the "Unlock" button and then "Flash stock" button. If the phone is already a paperweight then I don't believe it can possibly do any more harm, and you might even hit it lucky...
If none of this works, grab Motorola's refund offer with both hands...
Strephon Alkhalikoi said:
Overly simplistic reply here, but it should be enough to answer the question.
The bootloader prepares the system for booting. Once it's done its work it hands off control of the system to Android's kernel. Recovery is a mini operating system used to initiate low level functions such as wiping the on-board storage. The screen you describe I believe is the bootloader interface, hence why you have a "Restart Bootloader" option instead of "Start Bootloader".
Click to expand...
Click to collapse
Ok thank you.
I downloaded and installed Wugfresh, followed all the instructions. It won't work once it goes to flash because it can't see my phone connected. My PC recognises it as Nexus 6 but on the 'bootloader' screen at the bottom, it says Connect USB Data Cable, even though the phone says Battery OK (Charging). I tried to install latest USB drivers but apparently the latest are installed.
I am giving up now as I don't believe I can try anything else. Just strange that Wugfresh won't see the phone, yet my PC does.
Thanks.
Oh well...
You did try the Wugfresh "Test drivers"? It has a really helpful walkthrough on deleting and installing drivers. I'd give it a go before you give up.
dahawthorne said:
Oh well...
You did try the Wugfresh "Test drivers"? It has a really helpful walkthrough on deleting and installing drivers. I'd give it a go before you give up.
Click to expand...
Click to collapse
Ok I don't often use this phrase because I think it's very over rated but O M G - IT WORKED!!
I followed the driver guide in Wugfresh as you suggested, downloaded the CORRECT drivers, flashed it, unlocked bootloader, enabled usb debugging (just in case ) and then restored it then finally relocked the bootloader. It worked flawlessly and after setting up it is now 6.0.1 with the 1 Jan 2016 security patch applied - OTA.
I can't think you enough for your suggestion and advice, I really appreciate it and glad that I persevered with it.
Have a great weekend.
Thanks.
Bacon_Roll (vegetarian version)
That is absolutely fantastic news. I'm almost as pleased as you are. Remote assistance across the ether - you can't beat it with a big stick...
But as your attorney I advise you to go back into bootloader, check the connection (fastboot devices) and unlock again (fastboot oem unlock). This will wipe your device, but I reckon in the last 25 minutes you won't have been able to install much.
There are so many threads on this forum where people have been told "You're stuffed" because they have a problem and have a locked bootloader. Just this afternoon in another thread I read, literally in capital letters "DON'T RELOCK YOUR BOOTLOADER" for this very reason - without it you don't have recourse to the recovery tools you may one day need.
(P.S. Another person whose thread I followed also managed to get a result with NRT after all else had failed. I suggested to him that he might like to thank the developer, Doug Cohen/Wugfresh, more tangibly by donating a few dollars, which you can do through Paypal on his website. After all, he just saved your £300 phone... ).
@dahawthorne: I'll have to look into Wugfresh's utility. Not that I need it for anything, but it would be good to have in the unlikely event something goes wrong over here. Meanwhile, bacon_roll should take your advice to heart, because it will save him a lot of trouble in the future.
dahawthorne said:
That is absolutely fantastic news. I'm almost as pleased as you are. Remote assistance across the ether - you can't beat it with a big stick...
But as your attorney I advise you to go back into bootloader, check the connection (fastboot devices) and unlock again (fastboot oem unlock). This will wipe your device, but I reckon in the last 25 minutes you won't have been able to install much.
There are so many threads on this forum where people have been told "You're stuffed" because they have a problem and have a locked bootloader. Just this afternoon in another thread I read, literally in capital letters "DON'T RELOCK YOUR BOOTLOADER" for this very reason - without it you don't have recourse to the recovery tools you may one day need.
(P.S. Another person whose thread I followed also managed to get a result with NRT after all else had failed. I suggested to him that he might like to thank the developer, Doug Cohen/Wugfresh, more tangibly by donating a few dollars, which you can do through Paypal on his website. After all, he just saved your £300 phone... ).
Click to expand...
Click to collapse
Understood! I will take your advice on both counts but I was going to donate anyway as it really is a fantastic tool.
Thanks again
Strephon Alkhalikoi said:
@dahawthorne: I'll have to look into Wugfresh's utility. Not that I need it for anything, but it would be good to have in the unlikely event something goes wrong over here. Meanwhile, bacon_roll should take your advice to heart, because it will save him a lot of trouble in the future.
Click to expand...
Click to collapse
Thanks for your help over the thread Strephon - much appreciated.
Strephon Alkhalikoi said:
@dahawthorne: I'll have to look into Wugfresh's utility. Not that I need it for anything, but it would be good to have in the unlikely event something goes wrong over here. Meanwhile, bacon_roll should take your advice to heart, because it will save him a lot of trouble in the future.
Click to expand...
Click to collapse
FFS, it's not a magic wand, people! It can't do anything that fastboot and adb can't. Don't start a religion here instead teaching people to do stuff with their phones, Christ!
Some people were lucky enogh that their phones came with 5.0, and some early 5.0s didn't check yet for the Enable OEM Unlocking switch. You could have typed fastboot OEM unlock and achieved the same.
So I bought this phone from eBay, like many before it. But this time it came with a twist: when I booted the phone, initial setup ran and all wend fine until I got to the register Google account screen.
There, the phone says: "This phone was reset. To continue, sign in with a Google Account that was previously synced on this device".
No matter what account I use, I always get a Toast message saying "Unable to sign in to device due to a unknown error. Please try another account or try to sign in again after 24 hours.".
I'm guessing this is some kind of theft protection where entering a previously synced account "proves" that you're the legit owner. The authorised service here told me that I need some kind of proof that I'm the legit owner and surely enough the eBay seller has issued no invoice containing the phone's IMEI (or any similar document).
Anyway, here I am with this gorgeous phone on my hands which is little more than a brick due to this.
Is there any way I could get it to work again? Returning it will just generate more costs for me and I'd like to avoid that.
I've seen guides on youtube where they managed to bypass this security measure, but both methods I've seen failed for me. I guess the version running on my phone is just too recent and plugged all the holes.
Do I have any way of downgrading the software at least? Note that this is a fully locked phone and I can't even start TWRP from fastboot.
Anything else?
Edit: Now that I'm re-reading this post, it occurred to me that there's very little chance that this phone wouldn't be a stolen one. Had it not been, the seller would easily issue me an invoice.
Leaving this post only because my searching hasn't turned up anything on XDA. Probably also reporting the guy on eBay.
velis74 said:
So I bought this phone from eBay, like many before it. But this time it came with a twist: when I booted the phone, initial setup ran and all wend fine until I got to the register Google account screen.
There, the phone says: "This phone was reset. To continue, sign in with a Google Account that was previously synced on this device".
No matter what account I use, I always get a Toast message saying "Unable to sign in to device due to a unknown error. Please try another account or try to sign in again after 24 hours.".
I'm guessing this is some kind of theft protection where entering a previously synced account "proves" that you're the legit owner. The authorised service here told me that I need some kind of proof that I'm the legit owner and surely enough the eBay seller has issued no invoice containing the phone's IMEI (or any similar document).
Anyway, here I am with this gorgeous phone on my hands which is little more than a brick due to this.
Is there any way I could get it to work again? Returning it will just generate more costs for me and I'd like to avoid that.
I've seen guides on youtube where they managed to bypass this security measure, but both methods I've seen failed for me. I guess the version running on my phone is just too recent and plugged all the holes.
Do I have any way of downgrading the software at least? Note that this is a fully locked phone and I can't even start TWRP from fastboot.
Anything else?
Edit: Now that I'm re-reading this post, it occurred to me that there's very little chance that this phone wouldn't be a stolen one. Had it not been, the seller would easily issue me an invoice.
Leaving this post only because my searching hasn't turned up anything on XDA. Probably also reporting the guy on eBay.
Click to expand...
Click to collapse
From the Settings / About, what is exact (full) build name/number?
Generally, if you are on Nougat then IMO, rolling back to MM should completely reset your phone.
You cannot flash TWRP without unlocking Bootloader. But that will not help much for resetting Google protection.
Btw, enable Developer's menu, does it allow you to unlock FRP/OEM Unlocking - in that case you will be able to reset all from EMUI recovery.
zgfg said:
From the Settings / About, what is exact (full) build name/number?
Generally, if you are on Nougat then IMO, rolling back to MM should completely reset your phone.
You cannot flash TWRP without unlocking Bootloader. But that will not help much for resetting Google protection.
Btw, enable Developer's menu, does it allow you to unlock FRP/OEM Unlocking - in that case you will be able to reset all from EMUI recovery.
Click to expand...
Click to collapse
He can't get passed the setup screen
Twisted Prime said:
He can't get passed the setup screen
Click to expand...
Click to collapse
- Boot to Recovery (switch off, press and keep pressing Vol+ and Pow). Does it boot to stock Recovery and does it allow there to Factory reset (it should but if FRP was unlocked)
- Boot to Fastboot (switch off, connect by USB to PC, press Vol- and Pow), do you see Phone (Bootloader) and FRP locked or unlocked?
zgfg said:
- Boot to Recovery (switch off, press and keep pressing Vol+ and Pow). Does it boot to stock Recovery and does it allow there to Factory reset (it should but if FRP was unlocked)
- Boot to Fastboot (switch off, connect by USB to PC, press Vol- and Pow), do you see Phone (Bootloader) and FRP locked or unlocked?
Click to expand...
Click to collapse
It is stock recovery. I don't recall the option for factory reset. In fact there's no options at all, save for reboots.
Fastboot says everything is locked as it should be.
Don't know how to downgrade to MM.
velis74 said:
It is stock recovery. I don't recall the option for factory reset. In fact there's no options at all, save for reboots.
Fastboot says everything is locked as it should be.
Don't know how to downgrade to MM.
Click to expand...
Click to collapse
Rollback instructions are here
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
But not sure would it allow you to setup.
That is Factory Reset Protection (FRP/OEM Unlocking) - if it was unlocked you would be allowed to reset from recovery.
You can ask seller - maybe he can login to his Google account and remotely remove Google account from the sold phone.
Or you can try DC Unlocker, not sure would it work
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Well, DC unlocker ultimately worked, but not before buying a wrong package, having to ask tech support, etc, etc. Not to mention the guy really has no patience for people who don't have his level of understanding of the subject. Why does he do it then if he hates the whole thing so much?
velis74 said:
Well, DC unlocker ultimately worked, but not before buying a wrong package, having to ask tech support, etc, etc. Not to mention the guy really has no patience for people who don't have his level of understanding of the subject. Why does he do it then if he hates the whole thing so much?
Click to expand...
Click to collapse
So did you use DC Unlocker to unlock Bootloader or DC Phoenix to reinstall the phone?
zgfg said:
So did you use DC Unlocker to unlock Bootloader or DC Phoenix to reinstall the phone?
Click to expand...
Click to collapse
DC unlocker. I wanted minimal impact on the OS as the phone is for my daughter and she doesn't do custom ROMs et al
velis74 said:
DC unlocker. I wanted minimal impact on the OS as the phone is for my daughter and she doesn't do custom ROMs et al
Click to expand...
Click to collapse
Sorry for bothering but I'm interested now - when Bootloader was unlocked (and FRP too), were you just able to pass setup or you needed to do Factory reset from Recovery or how did you get the stock ROM working for you
Final resolution: the seller sent me an invoice. I guess that means that the phone wasn't stolen after all since they can only expect that this will be entered into Huawei databases.
zgfg said:
Sorry for bothering but I'm interested now - when Bootloader was unlocked (and FRP too), were you just able to pass setup or you needed to do Factory reset from Recovery or how did you get the stock ROM working for you
Click to expand...
Click to collapse
The procedure was thus:
1. unlocker unlocked the FRP
2. phone rebooted into a factory reset (low level) mode - it specifically said "low level"
3. phone booted into normal Android where the FRP protection was no longer active. On screen where it previously demanded a previous Google account it now only demanded A (any) Google account as I'm used to from all the other phones I ever bought.
Sorry old post
!!! This is a HIGH RISK method of performing any form of modification, if you are on a T-Mobile ne2217 !!!
There are unidentified files that your device might have conflict with, and cause a bootloop!
Proceed at your own risk! You have been warned!
OK, first lemme explain. The NE2217 (10 pro) itself does not have any special restrictions on it, unlike the CPH 2419 (10T) which is an exclusive T-Mobile variant. My guide on region swapping the CPH2419 (10T, link below) is still valid for the NE2217 (US- NA) . But there are conditions required or you will enter an infinite bootloop which becomes un-recoverable, without an edl flash. I do not have the specifics as to exactly which partitions cause this, but basically the bottom line is, IF YOU HAVE NOT UNLOCKED YOUR BOOTLOADER, EVEN IF YOU ARE SIM UNLOCKED, do not attempt to region swap.
There are a couple of partitions that are specially locked, that ONLY become write capable using the fastboot command, "Unlock Critical". Without a Bootloader unlock, the Oxygen Updater/Local Update programs, CANNOT make the needed changes to the Kernel, as well as these other important partitions, which have instructions that implicitly block changing to other regions. I cannot confirm if this exists in other countries with carrier locks, but i do know for a fact that T-Mobile has this enforced on all of the 10 Pro (ne2217) purchased through them.
As mentioned in previous threads that ive replied in, I suspected that the apps Oxygen Updater and Local Update, do not have the permissions capable to make direct changes to the boot.img, or recovery.img directly, primarily because those partitons cannot be altered while the system is currently running. These images can only be altered through Fastboot, or EDL thus the need for an MSM Tool if you cannot unlock your bootloader via conventional methods. So what happens is upon "Pre-boot" those special instructions i spoke of, take authority and put the carrier specific files, into an untouchable state that are locked behind the USERDATA partition, so these applications just copy the updated files to the inactive partition and performs the changes during the next boot, and even a hard wipe factory reset does not have the authority to erase the carrier instructions. The only way they are removed is by Unlocking your Bootloader! When you do that, the Qualcomm Processor has an embedded command, which is required to ERASE the entire Userdata partition, to protect the encrypted files protected by the bootloader lock! You can read about that by googling "Qualcomm Bootloader Unlocking".
Hope that makes sense to the majority of you. So again, the ONLY requirement for you to be able to go from 'ne2217', to any other fw is YOUR BOOTLOADER MUST BE UNLOCKED!
Failure to follow that one requirement will indeed force your device into an unusable, infinite bootloop, which can be resolved only by an EDL flash, which as of right now we do not have the tools that can perform this on CONSUMER level. You will have to RMA, your device, or go thru third party channels, which in itself is very risky, and puts you at risk of viruses/malware/wormholes/zombie-apocalypse because you must give someone full access to your computer remotely, and pray that the person only does what you requested. (NOT IDEAL).
Now if you're on a T-Mobile locked device, you are NOT hopeless... as I am on a T-Mobile locked device, and i am now bootloader unlocked as well! These two conditions are independent of each other, but trust me when i tell you that YOU DO NOT WANT TO GO THRU WHAT I HAVE EXPERIENCED, IN ORDER TO REACH THIS GOAL!
In so I will not publicly disclose how i was able to enter the real Fastboot Mode, so that i could pull the unlock code needed to request the unlock token from T-mobile.
(If you are so inclined to do this that you are willing to forgo ALL precautions and risk the possibility of bricking your device, or you have already landed yourself in an unrecoverable bootloop state, and are willing to try ANYTHING, you can join Bootloopers Anonymous, by clickiing it, and drop a message. This is a brand new telegram channel, and i will try to watch it for your requests. And again i strongly advise that you DO NOT embark on MY adventure, but if Unlocked Bootloader by Any Means Necessary is your ultimate goal, and nothing less is acceptable, i will try to help you achieve it... *** YOUR DEVICE WILL ENTER A COMPLETELY UNUSABLE STATE FOR A MINIMUM OF 7 DAYS!! *** but bear in mind that EVEN IF you have to use my method, you will be still subject to the 7-day waiting period outlined by OnePlus company policy. No one can overcome that, as the unlock token comes thru a separate division of Oppo/Oneplus that only generates the token through an automated request which is pushed after the expiration of 7 full days (1-week) has passed. YOU HAVE BEEN WARNED!)
The 10-Pro doesn't require the "In-Depth Testing" app to get your BL unlocked. That said, it also does not mean that OPPO has not designed one for this device because indeed they have. That application is individually encoded with device specifications so that only devices and regions EXPRESSLY AUTHORIZED by Oppo, can submit a request to unlock. DO NOT TRY sideloading any "In Depth Testing" apk floating around on the internet, as these can be altered to contain malware or worse, and then if your device becomes corrupted by it, Oppo can deny you an RMA on your device, thus charging you for the repair as there are warnings that you must acknowledge to even run the app, and attempting to circumvent the safeguards that this app already has in place is considered a violation of ToS.
If OPPO adds your device/region to the list of allowed devices, you will be able to download this application through OFFICIAL channels, and it will be made known to the public.
Once you are completely knowledgeable that your BL has indeed been fully unlocked, you can proceed to follow the instructions in the link to my guide below. The guide is for the CPH2419 (10T), but the instructions are completely compatible with the 10 Pro entire series, assuming your BL is unlocked. On the 10T this is not a requirement, and i honestly do not understand why this enforcement was put into our 10 Pro model, released almost a year earlier. Probably just an oversight by T-Mobile which might be corrected in future builds.
How to use Oxygen Updater + Local Update apks to switch regions.
EDIT: Local Update downgrade it currently installing
No Go, The update installed and downgraded but it just loads to the welcome screen and crashes and boot loops
supercobaltss said:
EDIT: Local Update downgrade it currently installing
No Go, The update installed and downgraded but it just loads to the welcome screen and crashes and boot loops
Click to expand...
Click to collapse
again, what most ppl are failing to do is follow my guide exactly as i defined. The VERY 1st thing you MUST DO... prior to unlocking the Bootloader... Prior to even downloading ANY rollback packages is, you MUST go and Download ANY of the Android 13 beta updates that are available in Oxygen updater. Turn on advanced mode, and select the whichever model you prefer... Its actually best to choose the region you plan on swapping to, for easier transition with the rollback package. IMHO i would always pick the EU model whenever attempting this, simply because that one usually has more bands available. But the main idea behind this is to make the phone, first BREAK the connection it has with T-Mobile's custom kernel, and modem... which is done just by upgrading to an Android 13 beta, as T-Mobile does not EVER release any beta builds, so by doing an actual OS upgrade, your phone must load the OS kernel, and several other partitions/files which i am sure that T-Mobile has branded in the 2217. Upgrading to a newer OS will without a doubt overwrite the carrier locked files, because the Upgrade comes from a higher authority in the chain of trust. Until TMO releases an update, then this is a requirement so that the rollback package of that region can safely downgrade the files, in their correct partitions. If you download a beta 13 thru oxygen updater, you can local update flash it, without problem. I did it myself to several demo devices at Tmobile stores here in Texas to test the technique, after i bricked mine by using a rollback package first!
Remember the 2217 is a T-Mobile EXCLUSIVE! No other carrier may sell this same model... but ALL of the internals are the exact same, and as im sure we are all well aware of, T-Mobile doesnt have the fastest adaptations when it comes to OS updates.
But there are several key identifiers which point to a custom made BL, Kernel, and Modem: 1. The build for all T-Mobile versions is on a revision that no other model has released... This alone could cause BL because if you flash a build that is older than the one you have currently, several files have anti-downgrade measures built into them. This is why we need the signed rollback packages to downgrade. But even if OPPO signed a rollback, unless they released one with T-Mobiles file specs, then anything you flash can create a conflict with an existing file... BL! But i know of about 13 ppl who have attempted my method, plus i just did another one myself last night for someone who contacted me and offered to compensate me royally if i would meet them since we were local logistically. 2. AFAIK, when installing a different rom to a device, you cannot downgrade the modem version. I know this is apparent with Samsung... as if you try to flash a rom with a lower modem version, it usually bricks, and you have to use odin to flash the newer modem back, in order to boot. Again this is taken care of by installing the NEWEST beta for Android 13, unless you had my situation which is, my phone CAME WITH updated security, and build already installed for October 2022. I havent heard of anyone who has said they even have the option to update theirs past August. So new purchases have to be careful. T-mobile sold mine with a blocked Fastboot, that doesnt respond to the button combo. Which clearly identifies they modified the recovery partition. 3. E-fuses have become a staple in Android devices for the past 5+ years.
Sure we have not heard of anything being in the T-mobile fw... but also who here can say that they have a FULL BUILD of the Tmo fw to examine? No one.... there is a generic 2217 build floating around that claims to be official, yet it is the ONLY build that does not have an OTA formatted file structure. All the 10 Pro OTA have been in payload.bin format, yet this happens to come only as a decrypted OFP, or a compressed OFP. *** OPPO is not directly supporting the 10 Pro 2217 or 10 T 2419 ! As these are proprietary T-Mobile builds. This is why you cannot find either of those models fw in the Oppo repository. So if OPPO doesnt release builds for TMO, then how exactly did an "Official 'OFP' for 2217" get released? *** OFP is an Official OPPO format for all the OPPO model phones. 10 Pro is still branded Oneplus, thus just about any OFP file you find in the wild, is almost 100% guaranteed NOT to be an official released build for our phones. Every package for this and the 10T that they have OFFICIALLY released, has been in Payload.bin format, because they havent released any full images yet! So in theory, who's to say that TMO didnt place an efuse into their specific model? Its only code, and if set, then it could have been burned during the initial release, or a later update, like AMAZON did with updates to the Firestick/FireTV devices, which would ONLY allow newer updates to certain files in THEIR build. That would totally explain a bootloop, because the rollback packages all push you back to 11_A.013 .... that build is from Feb-March 2022. Rolling back would almost guarantee that some files are overwritten with older components, which would cause a brick by e-fuse standards. We had to be lucky enough to catch it early in the FIrestick forum, to stop ppl from installing the update. Everyone who did, had their ability to unlock/load custom fw to their devices blocked, and there is still today no way to circumvent it. Sure new methods to mod became available, but only minimal changes, cuz the e-fuse blocked downgrading to exploitable builds. Since TMO has gone this far to stop us from modifying this phone, you can bet solidly on the fact that they have several safeguards in place to protect their investment.
Now im not trying to discourage anyone or discredit anything anyone has said or experienced regarding this phone, but look at the NUMEROUS unanswered replies to handfuls of problems that only happen to 1 or 2 ppl... they all have the same final result, but its astounding how many different scenarios ppl have found, that no one else has experienced, yet it leads to another bricked device. If this problem was rampant among a significant number of users, and it was triggered by the exact same scenario, then TMO would have to address it with an update... But all we know for sure is that there is some file(s) that is not compatible with any other model except the 2217. Til we have an EXACT culprit identified, all we can do is speculate, which is why I am going to re-label this as HIGH RISK in the OP. It has about a 40-50% chance of causing a bootloop, and about a 10% chance to leave your device unresponsive! There have been several released guides for other devices that have close to the same success rate / risk factor. All i can do is share what I have done, and what i know from personal exp.
Im sorry if anyone lands themselves on the wrong side of that equation, but it is a risk that only you can decide if its worth taking. For me, that answer is and always will be YES because i will not own a device that i do not OWN! For others this may be a touch more out of their league, and if thats true they should steer clear, until I or another user can get hold of an official TMO OTA, to examine the diff files in each.
****** Now all of that being said.... if ANYONE wishes to contribute to finding a solution to this dumpster fire, I am not asking for donations.... What i am asking, is for SOMEONE who might have a T-Mobile 10Pro on the release build, or any build PRIOR to 11_A.13 and is looking to help, we NEED an exact copy of an OTA update that might be sitting in your notifications. All updates download to the /sdcard/ partition of your phone in a folder that is accessible without root permissions. If you accept the download for the update, and DONT begin the install immediately, you can locate and pull that OTA to your computer, then delete the file from your phone, and it will cancel the update on reboot. No loss to you, but EXTREMELY HELPFUL to us, because we will have something from TMO to work with, which may give us a clue as to what we need to remove from the updater script ! *******
and FYI the signatures used to sign some of the OTA we already have, are already deciphered and as such can be used to create new signatures after making some changes to the respective regions package. But to make having these be of any value, we need to know what to take out or change in the manifest, that will prevent alterations of the files causing bootloops. If anyone can help with an upload of a TMO-OTA please share publicly or dm myself or one of the other devs who have expressed interest in this issue.
Thanks
I can probably pull the update from my wifes phone. She never updates anything. I did get my 10 pro to boot to android 13 but everything just says its disabled. This is only the 3rd phone ive done this with so ill warranty another one if i have to lol.
supercobaltss said:
EDIT: Local Update downgrade it currently installing
No Go, The update installed and downgraded but it just loads to the welcome screen and crashes and boot loops
Click to expand...
Click to collapse
Yup, this happened to me as well. Setup wizard crashes before I even get very far in it, and I've wiped multiple times trying to complete it somehow.
GuyInDogSuit said:
Yup, this happened to me as well. Setup wizard crashes before I even get very far in it, and I've wiped multiple times trying to complete it somehow.
Click to expand...
Click to collapse
Ive tried to convert multiple different ways. Upgrading to 13 basically screws you with the disabled apps BS, Downgrading just crashes the device. Either way its broken. I've went through 3 devices now messing around.
So I guess it's time to replace it, then? Crap.
GuyInDogSuit said:
So I guess it's time to replace it, then? Crap.
Click to expand...
Click to collapse
Start a RMA on OnePlus website, don't go through T-Mobile. They will have you send in phone and then either reflash your phone and send it back or just send you a new phone which is what they did when I had to do it. All that bs about voiding warranty when unlocking bootloader is just that, bs. They fix or replace without any issues but you have to go through OnePlus.
FML.
I've gotten it working for the most part, but what's most concerning is that there's no IMEI. And it doesn't charge or even acknowledge the cable. Fantastic.
jeffsga88 said:
Start a RMA on OnePlus website, don't go through T-Mobile. They will have you send in phone and then either reflash your phone and send it back or just send you a new phone which is what they did when I had to do it. All that bs about voiding warranty when unlocking bootloader is just that, bs. They fix or replace without any issues but you have to go through OnePlus.
Click to expand...
Click to collapse
I can't even request an RMA as I don't have an IMEI to provide. It's blank in the phone. I think I'm screwed. Or try T-Mobile. Dunno. This sucks.
GuyInDogSuit said:
I can't even request an RMA as I don't have an IMEI to provide. It's blank in the phone. I think I'm screwed. Or try T-Mobile. Dunno. This sucks.
Click to expand...
Click to collapse
The T-Mobile version has your IMEI sketched into the back cover of your phone. You should be able to use that.
jeffsga88 said:
The T-Mobile version has your IMEI sketched into the back cover of your phone. You should be able to use that.
Click to expand...
Click to collapse
Oh. Uh.... completely forgotten about that.
I just updated to Android 13 on the TMO NE2217, device not unlocked, still financed. And now have the option to unlock the BL.
beatbreakee said:
All updates download to the /sdcard/ partition of your phone in a folder that is accessible without root permissions. If you accept the download for the update, and DONT begin the install immediately, you can locate and pull that OTA to your computer, then delete the file from your phone, and it will cancel the update on reboot.
Click to expand...
Click to collapse
Is this still useful, with the NE2217_11_C.26 update? And either way, how can I delete it? I couldn't find anything big in /sdcard. Thanks!
deleted
psm321 said:
Is this still useful, with the NE2217_11_C.26 update? And either way, how can I delete it? I couldn't find anything big in /sdcard. Thanks!
Click to expand...
Click to collapse
^
^
^
^
^
THIS Please my phone ignored my saying no and next reboot the damn thing will go off on me ... so frustrating that even when you set the darn thing to OFF on auto update and such it STILL does this BS...
Damn TMobile and their special lock junk UGH ...
anyway ... please can one direct with a screen shot and file manager they used to find this file so I can delete the thing? ... I have tried to find it and struck out ... but having got the notification today and the Oxygen app is showing 'REBOOT' instead of 'resume' when I ignored the update previously has me thinking if I reboot I will see android 13 pop up and in this case means I will lose my whoop as something with it breaks pairing my wearable ... whoop has offered no timetable for a fix