Related
This guide is for the proper preparation of your nexus 6 for resale or warranty return.
There have been many instances of people buying or selling their Nexus 6 and not following the correct procedure which leads to the new owner needing the previous owner's Google account password to set up and use the device. I am creating a separate thread for this information due to the fact that it needs to be more visible.
Credit for the following guide goes to @PatimusXPrime
How to properly prepare your Nexus 6 running Android 5.1 to sell:
1. Flash Stock ROM and reboot.
2. Set up your phone and add your Google account(s).
3. Remove any screen protection such as: pins, swipe patterns, facelock, ect.
4. Verify that your Google account(s) have synced to Google servers then remove them from the device.
5. Factory Reset your phone. You should do this via the settings menu.
6. I would even go so far to say -- reboot the phone and begin setup. Once you log into your WiFi, verify that the request for previous Google account message does NOT appear.
7. Once the new user is able to setup the phone and enter their own Google credentials, you are free to reset your Google password with no worry. You can likely reset this sooner if you have removed the account prior to the factory reset.
If you do not remove your Google account prior to Factory Resetting:
The next person to use the phone (setup the device) will require your Google account credentials in order to get past the setup phase.
Caution: If you reset your Google Account password before using it to get past the setup phase, the new user will have to wait 72 hours before the phone can be able to move past the setup phase.
References:
http://www.greenbot.com/article/2904...ndroid-51.html
https://support.google.com/nexus/answer/6172890?hl=en
http://forum.xda-developers.com/show...01&postcount=4
http://www.androidpolice.com/2015/03...w-do-i-use-it/
Also, thanks @cam30era @02840 @efrant for collaboration and advice.
Original thread here:
http://forum.xda-developers.com/nexus-6/help/5-1-sign-loop-email-verification-sent-t3057436
Additional relevant threads:
http://forum.xda-developers.com/nexus-6/help/purchased-nexus-6-locked-t3104430
http://forum.xda-developers.com/nexus-6/help/set-problem-t3102979
http://forum.xda-developers.com/nexus-6/help/please-help-bought-locked-nexus-6-t3071521
http://forum.xda-developers.com/nexus-6/help/encrypted-sold-ebay-t3100335
http://forum.xda-developers.com/nexus-6/help/n6-factory-reset-protection-password-t3098013
The above XDA links are just a few I've found in the first 6 pages of the Q&A forum but there are many more. What people need to realize is that significant changes have come about with lollipop and things aren't done the way they used to be done.
Advice for buyers:
If possible, contact the seller ahead of time and make sure they have removed their Google account prior to factory resetting.
Factory images:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Re-locking your bootloader on 5.1 and up:
http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
needed thread :good::good::good:
I just flash the factory image. Done.
Evolution_Freak said:
Reserved.
Click to expand...
Click to collapse
Amazing, and sorely needed thread.
Congrats!
Sent from my Nexus 6 using Tapatalk
wolfen69 said:
I just flash the factory image. Done.
Click to expand...
Click to collapse
The problem is more related to those that are not taking that step. I.E. their device is stock, so they factory reset and ship. Without removing the Google account first, the factory reset won't clear your account password from the device.
However, if you look at the second link in the relevant threads, you'll see an XDA user who says they flashed factory and reset and sold. The buyer was still unable to access the device due to it asking for previous users password during activation.
Evolution_Freak said:
. . . an XDA user who says they flashed factory and reset and sold. The buyer was still unable to access the device due to it asking for previous users password during activation.
Click to expand...
Click to collapse
Everybody who wants to buy a used phone, must think 4x.
A. How about warranty?
B. How about security?
C. Try before buy !
D. Wait a day before pay!
fastboot oem unlock the thing before shipping it, and the buyer will have free access to the device without all the problems.
This should be stickied.
orangechoochoo said:
This should be stickied.
Click to expand...
Click to collapse
It is listed in the sticky roll up thread.
Evolution_Freak said:
It is listed in the sticky roll up thread.
Click to expand...
Click to collapse
To get around the security features of your google account on android 5.1 would I be able to just flash the factory image of something earlier 5.0.1? Wouldn't this eliminate the issue of the google password then the buyer could just set the device up. Does this only apply to flashing back to android 5.1 and up?
flyinj54 said:
To get around the security features of your google account on android 5.1 would I be able to just flash the factory image of something earlier 5.0.1? Wouldn't this eliminate the issue of the google password then the buyer could just set the device up. Does this only apply to flashing back to android 5.1 and up?
Click to expand...
Click to collapse
The security features only apply in 5.1, but why go through all that trouble when you just have to remove your Google account then factory reset?
Yes you can revert but don't revert your bootloader or you'll end up bricked.
wolfen69 said:
I just flash the factory image. Done.
Click to expand...
Click to collapse
yea I don't get why you would go through some lengthy and unnecessary steps for no reason when you just flash the stock image from the provide which is publicly available and be done with it. or even just put on a custom rom for the sake of its usually just better for people.
---------- Post added at 04:54 AM ---------- Previous post was at 04:51 AM ----------
Evolution_Freak said:
The problem is more related to those that are not taking that step. I.E. their device is stock, so they factory reset and ship. Without removing the Google account first, the factory reset won't clear your account password from the device.
However, if you look at the second link in the relevant threads, you'll see an XDA user who says they flashed factory and reset and sold. The buyer was still unable to access the device due to it asking for previous users password during activation.
Click to expand...
Click to collapse
then that specific user used an improper image/recovery tool/process.
twrp allows for the device to be wiped and deletes partitions for you when restoring an old image file of which every single user should have when they just get the phone. custom roms even have options to full wipe these days.
there is literally no reason to do the above steps in this thread unless your too lazy to find your stock image file and flash wipe/flash that.
None of it makes any sense what so ever as devices change hands and the results from a fresh install are identical to purging the account unless the data is stored in a new partition that is not handled by twrp etc...
I could see the issue persisting if the user dirty flashed the image file and did a factory reset thinking that would be just as good.
Solace50 said:
yea I don't get why you would go through some lengthy and unnecessary steps for no reason when you just flash the stock image from the provide which is publicly available and be done with it. or even just put on a custom rom for the sake of its usually just better for people.
---------- Post added at 04:54 AM ---------- Previous post was at 04:51 AM ----------
then that specific user used an improper image/recovery tool.
twrp allows for the device to be wiped and deletes partitions for you when restoring an old image file of which every single user should have when they just get the phone. custom roms even have options to full wipe these days.
there is literally no reason to do the above steps in this thread unless your too lazy to find your stock image file and flash wipe/flash that.
Click to expand...
Click to collapse
Lengthy process? Removal of your Google account takes all of 5 seconds. Then a factory reset. Not everybody roots or unlocks, so not everybody knows about flashing factory images. The fact is, this is a real issue affecting real people. Otherwise this wouldn't be in the sticky roll up.
Evolution_Freak said:
. . . The fact is, this is a real issue affecting real people. Otherwise this wouldn't be in the sticky roll up.
Click to expand...
Click to collapse
That's why this thread is also useful for everyone who wants to buy a used phone.
@Solace50,
The Nexus 6, with 5.1 is different from every other device that you (or I) have ever owned, from a security standpoint. Google made significant changes that were intended to render the device unusable if it was ever stolen. And this is new with 5.1.
The bottom line is that it's not "business as usual" when it comes to selling your used Nexus 6, if:
1) It 100% stock, including stock recovery, and
2) You had enabled the security settings.
Even if you wipe and flash a factory image, if you don't follow the recommendations of @Evolution_Freak, then the new owner won't be able to log in to the device.
nm - figured it out.
Great information. It's going to come in handy some day.
wolfen69 said:
I just flash the factory image. Done.
Click to expand...
Click to collapse
If the previous owner didn't have "OEM unlock" and/or USB debugging, how would you be able to flash the phone, though? You can't get past the initial setup to get into settings.
FoneWatcher said:
If the previous owner didn't have "OEM unlock" and/or USB debugging, how would you be able to flash the phone, though? You can't get past the initial setup to get into settings.
Click to expand...
Click to collapse
If the bootloader is locked, and you cannot boot into Android (in order to get into the settings to enable OEM unlock), then you are out of luck. Nothing you can do besides send the phone in for repair.
Hey all! My Nexus 6P that has been on N Preview since day 2 is now stuck in a boot loop. It will usually just display the Google logo and then reboot. Sometimes it will get to the very beginning of the Android boot animation, but rarely.
Unfortunately, I didn't even know about the OEM Unucking setting until I've been trying to get my phone to boot again. I've tried using clearing cache, factory restore, adb sideload, and the flashing instructions Google provides. I've also tried using SkipSoft Android ToolKit with no avail as well. At this point I don't care if I end up with Marshmallow or back on N. I just want my phone working again xP
Does anyone have any ideas on how to restore my phone back to a working state? Thanks!
It also might be good to mention is I'm not all that well versed in a lot of the android development tools. I'm not afraid to get my hands dirty though.
UPDATE (Thanks @NeoAcheron)
While this didn't work for me, this seems to work for some.
NeoAcheron shared the OTA update Google sends out to go from N to Marshmallow. YMMV, so best of luck to you!
If anyone has any other idea's to try, I'd be eternally grateful!
And remember kids, always enable OEM Unlocking like good boys and girls. (Settings -> Developer Options -> OEM Unlocking)
JPT62089 said:
Hey all! My Nexus 6P that has been on N Preview since day 2 is now stuck in a boot loop. It will usually just display the Google logo and then reboot. Sometimes it will get to the very beginning of the Android boot animation, but rarely.
Unfortunately, I didn't even know about the OEM Unucking setting until I've been trying to get my phone to boot again. I've tried using clearing cache, factory restore, adb sideload, and the flashing instructions Google provides. I've also tried using SkipSoft Android ToolKit with no avail as well. At this point I don't care if I end up with Marshmallow or back on N. I just want my phone working again xP
Does anyone have any ideas on how to restore my phone back to a working state? Thanks!
It also might be good to mention is I'm not all that well versed in a lot of the android development tools. I'm not afraid to get my hands dirty though.
Click to expand...
Click to collapse
If you can use fastboot fastboot system that should work out wipe userdata
jaythenut said:
If you can use fastboot fastboot system that should work out wipe userdata
Click to expand...
Click to collapse
Unfortunately, that didn't seem to work
Code:
> fastboot format userdata
Creating filesystem with parameters:
Size: 58688266240
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14328190
Block groups: 438
Reserved block group size: 1024
Created filesystem with 11/3588096 inodes and 271280/14328190 blocks
target reported max download size of 494927872 bytes
erasing 'userdata'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.013s
From the bootloader page on the phone...
Code:
Console: NULL
Battery OK
Device is LOCKED
Qfuse Status: ENABLED
Off-mode-charge: ENABLED
Download Mode: DISABLED.
Also worth a note...
Code:
> fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.005s
format from stock recovery ?
@JPT62089 You are not alone. My Nexus 6P is experiencing the same problem now. Signed up for the Dev Preview, phone behaved strangely today, reboot the device as per usual, and now its stuck on the boot screen...
I have tried applying the preview OTA update, and the Factory firmware reset, with the same results as you.
This is awesome considering I didn't unlock the bootloader, because I would have thought installing stock firmware would be possible.
This sucks... Lets hope Google releases a fix soon.
---------- Post added at 03:02 PM ---------- Previous post was at 03:01 PM ----------
csjneek said:
format from stock recovery ?
Click to expand...
Click to collapse
Unfortunately telling the device to reset to factory doesn't help either. Seems like the latest update broke the OS completely.
Wooohooo! Glad I'm not the only one It's unfortunate to have such a major issue as Preview 3 has been extremely stable for me up until yesterday...
NeoAcheron said:
@JPT62089 You are not alone. My Nexus 6P is experiencing the same problem now. Signed up for the Dev Preview, phone behaved strangely today, reboot the device as per usual, and now its stuck on the boot screen...
I have tried applying the preview OTA update, and the Factory firmware reset, with the same results as you.
This is awesome considering I didn't unlock the bootloader, because I would have thought installing stock firmware would be possible.
This sucks... Lets hope Google releases a fix soon.
---------- Post added at 03:02 PM ---------- Previous post was at 03:01 PM ----------
Unfortunately telling the device to reset to factory doesn't help either. Seems like the latest update broke the OS completely.
Click to expand...
Click to collapse
JPT62089 said:
Wooohooo! Glad I'm not the only one It's unfortunate to have such a major issue as Preview 3 has been extremely stable for me up until yesterday...
Click to expand...
Click to collapse
The Developer Preview was never meant to be signed up by any average user without prior knowledge on Android Development. If you sign up for the beta program, then it's always imperative that you have the bootloader previously unlocked, in case this exact situation happen. Did you actually think that you can just sign up for the Beta program and hope that it will not cause any problems?
ttminh1997 said:
The Developer Preview was never meant to be signed up by any average user without prior knowledge on Android Development. If you sign up for the beta program, then it's always imperative that you have the bootloader previously unlocked, in case this exact situation happen. Did you actually think that you can just sign up for the Beta program and hope that it will not cause any problems?
Click to expand...
Click to collapse
I am a software technical lead, knowing full well what the implications might be of running beta software on any piece of computing equipment. However, not at any point when I signed up was there a statement that I need to unlock the bootloader. Booloader unlocking in my mind (and on previous devices, like the HTC One) was only required when you wanted to deviate from the Stock firmware on the device. This is stock firmware, from Google.
I'm generally quite excited to test new things and I report my findings often with details about my experience and how the software behaved upto that point. But this has left a bad experience and I am not participating in the program anymore due to this.
Coming back now to say "oh you shoulda known" is not constructive. I am interested in a solution, because Google pretty much bricked my device without me touching it. The update (and the beta version since the announcement) applied seamlessly, and was working fine until I rebooted the device today.
---------- Post added at 04:18 PM ---------- Previous post was at 04:09 PM ----------
Found this: https://www.reddit.com/r/Nexus6P/comments/4jzp1o/soft_bricked_nexus_6p_with_locked_bootloader_need/
Might be possible to reproduce the special ZIP file to create a "special" downgrade OTA zip file to unbrick it, just to unlock the bootloader (at the very least).
I will have to look into it later, as I am still at work, and need to tend to some other tasks before getting back to this.
Will keep everyone updated...
NeoAcheron said:
I am a software technical lead, knowing full well what the implications might be of running beta software on any piece of computing equipment. However, not at any point when I signed up was there a statement that I need to unlock the bootloader. Booloader unlocking in my mind (and on previous devices, like the HTC One) was only required when you wanted to deviate from the Stock firmware on the device. This is stock firmware, from Google.
I'm generally quite excited to test new things and I report my findings often with details about my experience and how the software behaved upto that point. But this has left a bad experience and I am not participating in the program anymore due to this.
Coming back now to say "oh you shoulda known" is not constructive. I am interested in a solution, because Google pretty much bricked my device without me touching it. The update (and the beta version since the announcement) applied seamlessly, and was working fine until I rebooted the device today.
Click to expand...
Click to collapse
Bootloader unlocks are extremely important if you want to do any system-level mods (rooting, flashing custom recoveries, rom). Not only does it allow you to deviate from stock firmwares, like you said, but it also opens a gateway in which you can just flash a factory image and resolve any potential problems that may arise from otherwise stock Android or any custom roms you have. And stock firmwares, whether from Google, Samsung or even Apple, don't always mean good, or even stable. They may be stable 99% of the time, but eventually bugs and glitches are bound to happen; that's why they are continually updated, and that's why the 2011 Samsung ICS brick fiasco happened.
I did not mean to insult you or anything in the reply. That being said, yes, you really should have known before venturing into flashing firmwares without unlocking the bootloader and creating a backup first. As for solution, have you recently installed any apps that may not be compatible with N? Can you boot into safemode and disable some apps? If you can actually go into safemode, check allow oem unlock, unlock the bootloader and reflash factory image.
ttminh1997 said:
Bootloader unlocks are extremely important if you want to do any system-level mods (rooting, flashing custom recoveries, rom). Not only does it allow you to deviate from stock firmwares, like you said, but it also opens a gateway in which you can just flash a factory image and resolve any potential problems that may arise from otherwise stock Android or any custom roms you have. And stock firmwares, whether from Google, Samsung or even Apple, don't always mean good, or even stable. They may be stable 99% of the time, but eventually bugs and glitches are bound to happen; that's why they are continually updated, and that's why the 2011 Samsung ICS brick fiasco happened.
I did not mean to insult you or anything in the reply. That being said, yes, you really should have known before venturing into flashing firmwares without unlocking the bootloader and creating a backup first. As for solution, have you recently installed any apps that may not be compatible with N? Can you boot into safemode and disable some apps? If you can actually go into safemode, check allow oem unlock, unlock the bootloader and reflash factory image.
Click to expand...
Click to collapse
No offence taken, but I will make sure to unlock the device once I get it back up. Unfortunately the device doesn't boot at all, I cannot get it into safemode either (using the volume keys during boot).
What I do have though is the thread that is mentioned in the reddit post, I will need to check if this works before unleashing it here...
Will update when any developments made.
---------- Post added at 05:08 PM ---------- Previous post was at 04:46 PM ----------
HEY HEY! It worked!
So you need to get this file: https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
NeoAcheron said:
No offence taken, but I will make sure to unlock the device once I get it back up. Unfortunately the device doesn't boot at all, I cannot get it into safemode either (using the volume keys during boot).
What I do have though is the thread that is mentioned in the reddit post, I will need to check if this works before unleashing it here...
Will update when any developments made.
---------- Post added at 05:08 PM ---------- Previous post was at 04:46 PM ----------
HEY HEY! It worked!
So you need to get this file: https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
Click to expand...
Click to collapse
Glad you could make your phone work again. Make sure that you unlock your bootloader before unlocking or testing any new roms.
NeoAcheron said:
No offence taken, but I will make sure to unlock the device once I get it back up. Unfortunately the device doesn't boot at all, I cannot get it into safemode either (using the volume keys during boot).
What I do have though is the thread that is mentioned in the reddit post, I will need to check if this works before unleashing it here...
Will update when any developments made.
---------- Post added at 05:08 PM ---------- Previous post was at 04:46 PM ----------
HEY HEY! It worked!
So you need to get this file: https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
Click to expand...
Click to collapse
Did you just flash every .img file? There does not appear to be any other way.
NeoAcheron said:
HEY HEY! It worked!
So you need to get this file: https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
Click to expand...
Click to collapse
Thanks for posting this NeoAcheron, I sideloaded this yesterday and was actually able to perform an adb sideload this time (found a handy tip... Once the phone is waiting for adb commands, unplug and plug it back into the computer as it may not already see it)
It didn't seem to immediately help, unfortunately. I let it bootloop for a while before giving up and then tried again last night. I had left it on my desk bootlooping for a while and then all of a sudden it was booted and waiting for me to set it up. I quickly did so and immediate went to settings to enable the OEM Flashing setting and just as I did so it went to the red warning screen and then proceeded to bootloop again... I tried to run fastboot flashing unlock again in hopes that my changing the setting took before it bootlooped, but still got the FAILED message. I've since tried every which way of factory resetting, sideloading again, leaving it for hours in bootloop, and still nothing
Anyone have any more ideas?
Maybe a dumb question...but
ttminh1997 said:
Glad you could make your phone work again. Make sure that you unlock your bootloader before unlocking or testing any new roms.
Click to expand...
Click to collapse
Deleted
---------- Post added at 10:19 PM ---------- Previous post was at 09:59 PM ----------
So you need to get this file: https://android.googleapis.com/packa...cd4f52b800.zip
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
Can I flash this ( https://android.googleapis.com/packa...cd4f52b800.zip) in TWRP ? I am running N5...I wanted to go back to Marshmallow to be able to flash some roms.
Thanks
NeoAcheron said:
No offence taken, but I will make sure to unlock the device once I get it back up. Unfortunately the device doesn't boot at all, I cannot get it into safemode either (using the volume keys during boot).
What I do have though is the thread that is mentioned in the reddit post, I will need to check if this works before unleashing it here...
Will update when any developments made.
---------- Post added at 05:08 PM ---------- Previous post was at 04:46 PM ----------
HEY HEY! It worked!
So you need to get this file:
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
Click to expand...
Click to collapse
Hey NeoAcheron. I'm having a similar issue. After years of flashing custom ROMs, I joined the Beta programme so I could do things 'properly' on my Nexus 6P. Been working fine for a fortnight, until today when it randomly froze, crashed, and is now stuck in a bootloop on the 'Google' screen. I can get into the bootloader menu, but every option I select takes me back to the 'Google' bootloop screen. I can't even get my PC to recognise it as a device so I can't sideload a workaround.
Any ideas, or is it basically useless? Google have offered me a replacement phone, but I'd like to try and rescue this one first
Thanks in advance
kristianj79 said:
Hey NeoAcheron. I'm having a similar issue. After years of flashing custom ROMs, I joined the Beta programme so I could do things 'properly' on my Nexus 6P. Been working fine for a fortnight, until today when it randomly froze, crashed, and is now stuck in a bootloop on the 'Google' screen. I can get into the bootloader menu, but every option I select takes me back to the 'Google' bootloop screen. I can't even get my PC to recognise it as a device so I can't sideload a workaround.
Any ideas, or is it basically useless? Google have offered me a replacement phone, but I'd like to try and rescue this one first
Thanks in advance
Click to expand...
Click to collapse
The first thing you could try wiping cache from the stock recovery, and see if it works. Do you have any data on the device that you desperately wanna save, and can't loose?
DJBhardwaj said:
The first thing you could try wiping cache from the stock recovery, and see if it works. Do you have any data on the device that you desperately wanna save, and can't loose?
Click to expand...
Click to collapse
Thanks DJBhardwaj - I'm all backed up. I just wanted to see if I could fix it myself because I'd rather not be without a decent phone for a week. I'm no expert and I usually need my hand holding, but I've managed to get out of a few scrapes in the past with custom ROMs and bootloops!
My issue is that I can't even access stock recovery. I can get into the fastboot menu using the hardware keys but selecting any ption from there throws the device into a bootloop again. I also can't get my PC to see the device and wrestle beck control using adb commands, so I'm a bit stuck :/
kristianj79 said:
Thanks DJBhardwaj - I'm all backed up. I just wanted to see if I could fix it myself because I'd rather not be without a decent phone for a week. I'm no expert and I usually need my hand holding, but I've managed to get out of a few scrapes in the past with custom ROMs and bootloops!
My issue is that I can't even access stock recovery. I can get into the fastboot menu using the hardware keys but selecting any ption from there throws the device into a bootloop again. I also can't get my PC to see the device and wrestle beck control using adb commands, so I'm a bit stuck :/
Click to expand...
Click to collapse
Have you tried on any other Windows or Mac PC? If you can get it to detect, then the problem would be pretty easily solved. To confirm if your device is being recognized, type in the following command in CMD/Terminal:
Code:
fastboot devices
My daughter managed to change the pattern on her phone while on vacation and she can't remember what the new one is. I have gotten into the boot menu in attempts to completely reset the phone, however, there is no option for factory reset. Can somebody please tell me how to wipe this phone so she can use it again.
I'm just gonna ask for someone who knows better. I guess you'd be better off leaving the bootloader locked so you can have the warranty, so would it be possible to flash TWRP through fastboot, then delete lockscreen database stuff with it, then flash stock recovery? All without unlocking the phone?
Also could you tell us the model? Is it an A2017G, A2017, or A2017U?
If the phone hasn't got fastboot, you would have to use MiFlash to flash A2017*_FASTBOOT_UNLOCK_EDL then get TWRP and delete the files.
---------- Post added at 10:56 PM ---------- Previous post was at 10:49 PM ----------
Also, if you do that process you could avoid resetting the phone. I'm just not sure if you can change system stuff without unlocking the bootloader. so until someone with actual knowledge shows up I'd advise you to hold on tight.
MasterDDF said:
My daughter managed to change the pattern on her phone while on vacation and she can't remember what the new one is. I have gotten into the boot menu in attempts to completely reset the phone, however, there is no option for factory reset. Can somebody please tell me how to wipe this phone so she can use it again.
Click to expand...
Click to collapse
unlock the bootloader.
Jusz go into recovery mode, shutdown the phone wait for 5 seconds than push the volume up and Power button at the same time and wait till. you are in recovery mode, than you can factory reset the phone
https://youtu.be/Rw5TMxyAGMc
nuridurdu27 said:
Jusz go into recovery mode, shutdown the phone wait for 5 seconds than push the volume up and Power button at the same time and wait till. you are in recovery mode, than you can
Click to expand...
Click to collapse
If only it was that simple. That was the first thing I did after 30 failed attempts for her figuring out her pattern. However there isn't am option to reset to factory. I've never seen a phone not have the option before
Choose an username... said:
I'm just gonna ask for someone who knows better. I guess you'd be better off leaving the bootloader locked so you can have the warranty, so would it be possible to flash TWRP through fastboot, then delete lockscreen database stuff with it, then flash stock recovery? All without unlocking the phone?
Also could you tell us the model? Is it an A2017G, A2017, or A2017U?
If the phone hasn't got fastboot, you would have to use MiFlash to flash A2017*_FASTBOOT_UNLOCK_EDL then get TWRP and delete the files.
---------- Post added at 10:56 PM ---------- Previous post was at 10:49 PM ----------
Also, if you do that process you could avoid resetting the phone. I'm just not sure if you can change system stuff without unlocking the bootloader. so until someone with actual knowledge shows up I'd advise you to hold on tight.
Click to expand...
Click to collapse
Slightly embarrassing realizing I even had the model of phone wrong. Not listening to my wife anymore. It is an axon 7 mini. Model B2017G. If there is a moderator that would like to relocate the post that would be fine
lafester said:
unlock the bootloader.
Click to expand...
Click to collapse
Is there a walkthrough on unlocking the bootloader? I haven't messed with getting that done before.
MasterDDF said:
Model B2017G.
Click to expand...
Click to collapse
Oops... Sorry man, but there's no proven way(or probably just no way) of doing this kind of stuff on the Axon 7 mini. For some reason there are zero developers for that phone
The only other thing I can think of is to put a bunch of random patterns, then wait, then do that again until the phone decides to leave you put her Google account and password. I hope that works...
Or one other thing, but I'm almost sure this won't work: if the phone has Nougat, which I doubt, you can look over at zte support if there's a Marshmallow system zip. Download it and extract the zip that's inside the zip, then throw it inside an SD card, put it in the phone, then go to the recovery and select to flash update, select it. It should wipe everything to oblivion.
---------- Post added at 01:42 AM ---------- Previous post was at 01:28 AM ----------
MasterDDF said:
Is there a walkthrough on unlocking the bootloader? I haven't messed with getting that done before.
Click to expand...
Click to collapse
Wait - even better, there seems to be a factory reset option. Look at this:
https://forum.xda-developers.com/axon-7-mini/help/b2017g-forgot-password-factory-data-t3596774
Choose an username... said:
[/COLOR]
Wait - even better, there seems to be a factory reset option. Look at this:
https://forum.xda-developers.com/axon-7-mini/help/b2017g-forgot-password-factory-data-t3596774
Click to expand...
Click to collapse
Was worth a shot. But I don't even get a robot. Any other device I've owned I get the robot laying on the ground.
MasterDDF said:
Was worth a shot. But I don't even get a robot. Any other device I've owned I get the robot laying on the ground.
Click to expand...
Click to collapse
I don't know. If that phone hasn't got a recovery then ZTE is weirder than I thought. Try power + volume up or power + volume down, it has to do something...
Hello, MasterDDF. I'm afraid that the last maintenance update removed the factory reset option from the Android Recovery Menu, however, we've confirmed that an update will be released soon for the Axon 7 Mini device. Since you are unable to unlock the device, we're happy to repair or replace the device utilizing your warranty. If you'd like additional information or, have any questions or concerns, please feel free to contact our Support team at 1-800-617-5065 or, via our social media on Facebook ZTEUSA, and Twitter ZTE_USA.
ZTEUSA Support
Hey friends,
As I already informed you in the "geekbuying firmware" thread, I have ordered a Nubia Z17S with "gobal rom". See here where I got it from: https://nl.aliexpress.com/store/pro...hone/708786_32837057331.html?isOrigTitle=true. I have 2 subjects to discuss with you. One is FOR you, one is where I need help .
GLOBAL ROM UPLOAD:
I got the phone in, just a few days ago. But it appears it really HAS a stock global ROM with full Google Play support, everything works! It is the EN_COMMON v1.02 ROM.
If you like, I can make a backup from this ROM and upload it for you guys, in order to see if you can cook a compatible Z17 ROM from it?
The only question: How do I do this, WITHOUT rooting my phone, if you have a tutorial for me, I will try for you.
Mobile Iron not installing:
Why I ordered a Z17S with the global ROM, is that I am NOT allowed to root my phone. Why: I need to have Mobile Iron installed, a secure enterprise cloud service, used for my work email. See here: https://play.google.com/store/apps/details?id=com.mobileiron&hl=en. Normally on my other phones (for instance the Z9 mini) it was no problem to install this app, as long I had an official rom on it. It was always on a Android 5 ROM. However, now, the APP is not installing and gives me the following error: "Your work has set up a work profile. If you like to use [email protected], use the version with badge that has been installed on your device". The problem is however, that my company does NOT have installed ANYTHING yet on my phone. Searching around on the internet shows that also Samsung users with Android 7 have this issue, as there is a secure folder installed that is not allowed by Mobile Iron, see here: https://forums.androidcentral.com/a...galaxy-note-7-unable-install-mobile-work.html. So, my question here is the following: Does the official Nubia ROM have something like a "secure folder" option, or anything like that? And if so, how can I uninstall that? I tried to look around myself, but no luck.
In summary: if you could help me with the Mobile Iron installation, I will help you with the Z17S ROM (and even if you cannot help me with the Mobile Iron installation ).
flash twrp,
make a backup
flash official recovery.
Sorry but for twrp I need to unlock the bootloader, which I can't do.
Can you make the backup using the stock recovery? It would be great to get the ROM. I found this on an official Nubia forum: http://bbs.nubia.cn/thread-1079140-1-1.html But haven't tried yet.
Troxelke said:
Sorry but for twrp I need to unlock the bootloader, which I can't do.
Click to expand...
Click to collapse
Finally I was managed to get it working. Now my phone is rooted with just two or three steps. Really easy to do .
1. In your phone, Open settings, about phone, tap many times on a build number to access the developer mode and enable USB debugging, enable also OEM unlock!
2. Download this file: https://1drv.ms/u/s!Aibwba12yUANjd4Ss0xEQErPtMrfTw
2. Unzip the folder somewhere to your disk
3. Run recovery.bat
4. Close the opened website and in the opened command line, press 1 and enter to install drivers
5. Press 2 and enter to install TWRP, after the installation is finished, the phone remains in a fastboot mode but you will see press any key to continue in the command line (don't press anything on the computer!) you have to press volume down on your phone to choose reboot to recovery mode and confirm it by pressing the power button
6. Voila, you are in a TWRP. In TWRP first of all, if you have a set pattern or a code, type in the code or a pattern, select language and confirm by pressing the blue enter button. You can also choose your language (for me English). Swipe to allow modifications.
7. Navigate to advanced, tools and root device, swipe to confirm
8. Wipe cache/dalvik and reboot to system.
9. Download root checker and check if you are rooted.
10. If you want to boot to the recovery again, I think this is a temporary TWRP installation. If I tried to boot to TWRP again, I just got into the original recovery. BUT the root still remains! And if you want to unroot the device, you just tap to unroot device in TWRP.
11. If you want to get into TWRP, again repeat steps 3 and 5 - Just open the recovery.bat and hit 2 to install TWRP, then get into it and make a backup.
MOREOVER, I was able to make the backup! So if you could make the backup (I skipped the data part because I think it is not so important since there should be just some apps data and other things not the system files), but please make a backup of your rom and upload it somewhere. Please give it a try
Thanks in advance
Thanks, but as I mentioned, I cannot unlock, root or reflash the device, sorry!
unlock bootloader,
flash twrp,
make a backup
flash official recovery if you want
lock bootloader if you want.
you are still not rooted so your iron will go on working. any many no zero operation done to ROM - system so you are still unrooted.
Troxelke said:
Thanks, but as I mentioned, I cannot unlock, root or reflash the device, sorry!
Click to expand...
Click to collapse
Once again, did you try my method?
I also couldn't unlock, root or anything else. But with this manual, you can do that. And then you can unroot your device easily if needed.
---------- Post added at 06:02 PM ---------- Previous post was at 05:56 PM ----------
BTW. Guys, is there anyone who could make his backup even with the Chinese rom in TWRP?
I accidentally formated data and now the phone cannot boot again, the only thing I can do is get to the TWRP but I cannot do anything else. Please someone, make your backup and post it somewhere to download.
Thank you very much.
vasington1993 said:
Once again, did you try my method?
I also couldn't unlock, root or anything else. But with this manual, you can do that. And then you can unroot your device easily if needed.
---------- Post added at 06:02 PM ---------- Previous post was at 05:56 PM ----------
BTW. Guys, is there anyone who could make his backup even with the Chinese rom in TWRP?
I accidentally formated data and now the phone cannot boot again, the only thing I can do is get to the TWRP but I cannot do anything else. Please someone, make your backup and post it somewhere to download.
Thank you very much.
Click to expand...
Click to collapse
Sorry but you don't get me I am afraid ... I mean I am not going to risk my 600 euro phone to root unlock and reset, as the Z17s has no solid twrp and I do not have a international ROM to fall back at the moment. If something goes wrong, which is very likely (see your own situation at the moment), I will be stuck for weeks or longer, and having the risk to never be able to install Mobile Iron anymore.
So to be clear, I will be more than happy to make a backup of my system, but if this involves rooting, unlocking or reset, I cannot help you. Sorry!
My situation was totally different. It was just my fault that I did a full reset with all the data erased but I am back alive. Just flashed the old recovery and stock rom. So a quick and simple solution. Hopefully there will be someone who is not so afraid.
The method I posted is 100% safe. I have tested it and worked like a charm. I was managed to install Google Play and other services so I am happy now. Do not need the geekbuying rom. Because there are no updates which I would miss.
Anyway, thanks.
Install TWRP
Troxelke said:
Sorry but for twrp I need to unlock the bootloader, which I can't do.
Click to expand...
Click to collapse
I can help you.
install TWRP
Sorry but you don't read carefully.
https://yadi.sk/d/xpugXV7r3QTDEV
Double post
sokomind said:
https://yadi.sk/d/xpugXV7r3QTDEV
Click to expand...
Click to collapse
Great, thanks! Where did you get it from?
I just find this : http://www.nubia.com/th/support.php?a=phone&pid=65
Thanks! Nice to see it is downloading from this site:
http://rom.download.nubia.com/Europe&Asia/Z17S/
Too bad this "root folder" for the Z17S is forbidden. But nice to see the folder is named "europe & asia".
Hoz.be said:
I just find this : http://www.nubia.com/th/support.php?a=phone&pid=65
Click to expand...
Click to collapse
On the previous link i have a ROM available for download see on the following picture :
http://hpics.li/3e45823
The name is NX595J_Z69_EN_VNG0N_V105
"EN" mean english? Can i install this ROM on my Z17 ?
Thanks !
Hoz.be said:
On the previous link i have a ROM available for download see on the following picture :
http://hpics.li/3e45823
The name is NX595J_Z69_EN_VNG0N_V105
"EN" mean english? Can i install this ROM on my Z17 ?
Thanks !
Click to expand...
Click to collapse
most probably, you can't
Please allow a couple of stupid questions:
-Is this ROM you linked ( NX595J_Z69_EN_VNG0N_V105.zip ) compatible with both the models? (6/64 GB and 8/128 GB?)
-Is OTA update possible once they're installed?
-Are they already equipped with google services and stuff?
Thanks to whom might answer
I recently bought a used oneplus 5 and i was told/asured it was factory reset and all. Now i'm trying to set it up but im required to enter the gmail account data from the former user, which, of course, i dont have and probably won't get because i mean who's gonna give a stranger his gmail password even if one can change it immediately.
Question is: Is there a way to bypass it (i factory resetted it another 2 times and erased all system settings and all already) and actually use my account for it or is it unusable until i get the account data of the seller
The bootloader is still locked and i factory resetted it myself 2 times.
Apotrox said:
I recently bought a used oneplus 5 and i was told/asured it was factory reset and all. Now i'm trying to set it up but im required to enter the gmail account data from the former user, which, of course, i dont have and probably won't get because i mean who's gonna give a stranger his gmail password even if one can change it immediately.
Question is: Is there a way to bypass it (i factory resetted it another 2 times and erased all system settings and all already) and actually use my account for it or is it unusable until i get the account data of the seller
Click to expand...
Click to collapse
Enter into fastboot mode by pressing volume up + power button together when the device is powered off. Connect your pc to your phone and do fastboot format userdata. For more information you can contact @MrWilsonxD he is an expert for this.
sleepwalking0593 said:
Enter into fastboot mode by pressing volume up + power button together when the device is powered off. Connect your pc to your phone and do fastboot format userdata. For more information you can contact @MrWilsonxD he is an expert for this.
Click to expand...
Click to collapse
Aye did this and it failed (Flashing is not allowed in Lock State). So i guess it's because the bootloader is still locked which i can't do since i can't access the settings to enable it (which i have to if i carry out the steps of a basic tutorial). Can i access the settings somehow without finishing the inital setup? Maybe in addition to being able to unlock the bootloader i can also remove the restriction of the old user account?
Apotrox said:
Aye did this and it failed (Flashing is not allowed in Lock State). So i guess it's because the bootloader is still locked which i can't do since i can't access the settings to enable it (which i have to if i carry out the steps of a basic tutorial). Can i access the settings somehow without finishing the inital setup? Maybe in addition to being able to unlock the bootloader i can also remove the restriction of the old user account?
Click to expand...
Click to collapse
Okay do this now. Wipe system, data, cache, dlavik, vendor. Then go in format and type yes. Flash oos. Reboot to recovery. Flash magisk. Flash no verity. Boot into os. See if it solve your issue.
Next method. Delete these 3 colour files in twrp. Look at photo attached.
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
Refer to this thread.
Hope it solves your issue. Goodluck. Happy Friday. Don't forget to leave thanks if I helped.
Me sleep now goodnight. See you tomorrow. I would try to do my best to help you and solve your issue
sleepwalking0593 said:
Okay do this now. Wipe system, data, cache, dlavik, vendor. Then go in format and type yes. Flash oos. Reboot to recovery. Flash magisk. Flash no verity. Boot into os. See if it solve your issue.
Next method. Delete these 3 colour files in twrp. Look at photo attached.
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
Refer to this thread.
Hope it solves your issue. Goodluck. Happy Friday. Don't forget to leave thanks if I helped.
Me sleep now goodnight. See you tomorrow. I would try to do my best to help you and solve your issue
Click to expand...
Click to collapse
The op has a device with a locked bootloader.
So he cannot have twrp, flash magisk every other things that you suggested...
BTW: if you're sleeping you can grab a BBS idle dump file for sure, you know what I mean
---------- Post added at 09:43 PM ---------- Previous post was at 09:30 PM ----------
Apotrox said:
I recently bought a used oneplus 5 and i was told/asured it was factory reset and all. Now i'm trying to set it up but im required to enter the gmail account data from the former user, which, of course, i dont have and probably won't get because i mean who's gonna give a stranger his gmail password even if one can change it immediately.
Question is: Is there a way to bypass it (i factory resetted it another 2 times and erased all system settings and all already) and actually use my account for it or is it unusable until i get the account data of the seller
The bootloader is still locked and i factory resetted it myself 2 times.
Click to expand...
Click to collapse
If the device has nougat, you can try to type *#812# within the emergency calling screen to get access to the home screen and can factory reset your device.
Otherwise you can try to write the partitions from scratch with the unbrick tool which should also work https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
strongst said:
The op has a device with a locked bootloader.
So he cannot have twrp, flash magisk every other things that you suggested...
BTW: if you're sleeping you can grab a BBS idle dump file for sure, you know what I mean
---------- Post added at 09:43 PM ---------- Previous post was at 09:30 PM ----------
If the device has nougat, you can try to type *#812# within the emergency calling screen to get access to the home screen and can factory reset your device.
Otherwise you can try to write the partitions from scratch with the unbrick tool which should also work https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
Click to expand...
Click to collapse
But you didn't read my last message i moved to oos now. You don't understand that many people face this issue. Even lightning kernel developer whose kernel was used by Sian in his earlier ROM also had that issue. People don't report on XDA because of things i can't type because i will get warning from mods. Everyone has shifted to telegram and those chats are not moderated and things that happen aren't good. If you are on telegram you will know. Okay i guess i will have to become like others and don't post my own question. Just will reply to others. I will post dump file when i flash ROM again and also developer doesn't support it. + Logs won't show anything. If it was possible atleast a kernel developer would have sent to others. + It's definitely not because of me. Because i didn't install anything apart from magisk, no verity zip, fk kernel app, bbs when i did my last testing. Sorry to bother you.
sleepwalking0593 said:
But you didn't read my last message i moved to oos now. You don't understand that many people face this issue. Even lightning kernel developer whose kernel was used by Sian in his earlier ROM also had that issue. People don't report on XDA because of things i can't type because i will get warning from mods. Everyone has shifted to telegram and those chats are not moderated and things that happen aren't good. If you are on telegram you will know. Okay i guess i will have to become like others and don't post my own question. Just will reply to others. I will post dump file when i flash ROM again and also developer doesn't support it. + Logs won't show anything. If it was possible atleast a kernel developer would have sent to others. + It's definitely not because of me. Because i didn't install anything apart from magisk, no verity zip, fk kernel app, bbs when i did my last testing. Sorry to bother you.
Click to expand...
Click to collapse
Again: The op of this thread thread as the factory reset protection issue on stock rom with locked bootloader.
You cannot suggest him to boot to twrp or format several partitions, that's simply not possible!
strongst said:
Again: The op of this thread thread as the factory reset protection issue on stock rom with locked bootloader.
You cannot suggest him to boot to twrp or format several partitions, that's simply not possible!
Click to expand...
Click to collapse
I'm sorry, i got messed up with another thread i guess. Okay i will think of another solution now.
---------- Post added at 07:23 AM ---------- Previous post was at 07:20 AM ----------
Apotrox said:
I recently bought a used oneplus 5 and i was told/asured it was factory reset and all. Now i'm trying to set it up but im required to enter the gmail account data from the former user, which, of course, i dont have and probably won't get because i mean who's gonna give a stranger his gmail password even if one can change it immediately.
Question is: Is there a way to bypass it (i factory resetted it another 2 times and erased all system settings and all already) and actually use my account for it or is it unusable until i get the account data of the seller
The bootloader is still locked and i factory resetted it myself 2 times.
Click to expand...
Click to collapse
If you click on i forgot my email id. Than you get an option to enter your phone number. Will that work for you.
If you click on i forgot my email id. Than you get an option to enter your phone number. Will that work for you.
Click to expand...
Click to collapse
Nope i don't have the phone number used with the google account (apparently the seller used another number than the one he has on ebay). I messaged him but haven't gotten an answer yet.
Apotrox said:
Nope i don't have the phone number used with the google account (apparently the seller used another number than the one he has on ebay). I messaged him but haven't gotten an answer yet.
Click to expand...
Click to collapse
Have you tried my suggestions?
strongst said:
Have you tried my suggestions?
Click to expand...
Click to collapse
I'm at it, the *#812# didn't work so i'll have to try the unbrick tool method which takes some time to download the files. I'll keep you updated
strongst said:
Have you tried my suggestions?
Click to expand...
Click to collapse
Alright i skipped the thing with the drivers because it showed up correctly and used the msm download tool for OOS 9.0.4.
And it did work!! Thank you so much!