Okay, I'll explain what I've done from getting the phone, up until now.
When I first got my N6P, I've managed to add my card (unsupported) into Pay with no problems. I was able to make NFC payments and whatnot.
Flash forward to the November security patch. I couldn't wait for the OTA, so I unlocked the bootloader, installed TWRP and did a full wipe, flashed the image (with userdata wipe), and booted into the system (bootloader still unlocked). I was still able to add my unsupported card and use it to make payments with no problems with an unlocked bootloader.
Yesterday, I decided to flash a custom ROM (install TWRP, full wipe, the whole deal). After a while, I decided to revert back to full stock. Went to TWRP, full wipe, then went and flashed the image via ADB commands. When I went to add my card again, it gave me a "Request Failed. Please verify your card information and try again."
Here's what I've done to attempt to fix it:
1. Went to payments.google.com, removed the card from there, re-add it from there, then add it on Pay. Nothing
2. Flashed the image again, then locked the bootloader. Nothing
3. Tried three other cards (unsupported). Nothing
I'm guessing that there are three possibilities:
1. Problem on Google's end
2. Custom ROM might've tripped something (qFuse hasn't been tripped)
3. I can't grandfather my cards onto Pay any more.
Any solutions or explanations would be greatly appreciated
Android Pay does not work with root or with custom roms even if it is not rooted for security reasons.
unixasaurusrex said:
Android Pay does not work with root or with custom roms even if it is not rooted for security reasons.
Click to expand...
Click to collapse
I know, but I went back to stock via factory image straight from Google.
ak47nerd said:
I know, but I went back to stock via factory image straight from Google.
Click to expand...
Click to collapse
Have you checked that SE Linux is enforcing?
unixasaurusrex said:
Have you checked that SE Linux is enforcing?
Click to expand...
Click to collapse
Well, I did a full wipe on TWRP, then installed the factory image again. I went to add my card, and now it isn't supported any more.
I'm guessing that I can't grandfather my old cards again.
ak47nerd said:
I know, but I went back to stock via factory image straight from Google.
Click to expand...
Click to collapse
ak47nerd said:
Well, I did a full wipe on TWRP, then installed the factory image again. I went to add my card, and now it isn't supported any more.
I'm guessing that I can't grandfather my old cards again.
Click to expand...
Click to collapse
That's odd I have added my card many times. Make sure SE is enforcing, other than that I don't know what to tell you im out of knowledge on this. Sorry.
Related
Just got the notice. Updating now!
About damn time.
Sent from my XT1058 using XDA Free mobile app
Yep, bought mine outright through Fido, updated tonight.
I'm using it on Bell, nice to see you can finally get rid of your carrier label in the status bar.
Yay, now do I unroot and try the OTA or do I wait for the full image.
ChrisAG said:
Yep, bought mine outright through Fido, updated tonight.
I'm using it on Bell, nice to see you can finally get rid of your carrier label in the status bar.
Click to expand...
Click to collapse
You can? How? I didn't save the link to the release notes, and can't find them now.
thedosbox said:
You can? How? I didn't save the link to the release notes, and can't find them now.
Click to expand...
Click to collapse
Removing provider name from the Status bar:
Settings > Wireless & Networks > More > Mobile Networks > Show Mobile Network (check on or off)
I completely forgot about the carrier being removed. Really cool.
Sent from my XT1058 using XDA Free mobile app
Install went fine, I unrooted, upgraded and then rooted again with no problem. The show carrier on/off is a great upgrade, I don't have to mess with modifying APK's anymore.
The new dialer will take some time to get used to.
Steve-x said:
Install went fine, I unrooted, upgraded and then rooted again with no problem. The show carrier on/off is a great upgrade, I don't have to mess with modifying APK's anymore.
The new dialer will take some time to get used to.
Click to expand...
Click to collapse
Ugh... I have TWRP on mine. Can I just unroot, or I need to remove TWRP? (read: flash stock 4.4.2...)
OK. Ended up flashing the whole damn phone again.
So which root method works for us, Rogers users?
R3dbeaver said:
OK. Ended up flashing the whole damn phone again.
So which root method works for us, Rogers users?
Click to expand...
Click to collapse
I removed root using the option in Super SU and then flashed the system.img and recovery.img from 4.4.2 in fastboot.(probably didn't need to do anything with Super SU because I reflashed system.img)
I then let the phone update. When it was done I went back into fastboot and flashed TWRP to recovery, went into recovery and let it begin the root process. From there boot up and update Super SU and finish rooting.
Overall a pretty painless way to go from 4.4.2 to 4.4.4 without losing any data or settings. All of this assumes you have an unlocked bootloader of course.
Steve-x said:
I removed root using the option in Super SU and then flashed the system.img and recovery.img from 4.4.2 in fastboot.(probably didn't need to do anything with Super SU because I reflashed system.img)
I then let the phone update. When it was done I went back into fastboot and flashed TWRP to recovery, went into recovery and let it begin the root process. From there boot up and update Super SU and finish rooting.
Overall a pretty painless way to go from 4.4.2 to 4.4.4 without losing any data or settings. All of this assumes you have an unlocked bootloader of course.
Click to expand...
Click to collapse
Ah you used TWRP's.
OK cool. Will give it a shot. Will try. I'm assuming I need SuperSU and BusyBox installed beforehand? Remember, I'm starting clean here.
R3dbeaver said:
Ah you used TWRP's.
OK cool. Will give it a shot. Will try. I'm assuming I need SuperSU and BusyBox installed beforehand? Remember, I'm starting clean here.
Click to expand...
Click to collapse
If your bootloader is unlocked then it is very simple. Just go to fastboot and flash the TWRP recovery, once flashed you can access it from fastboot. TWRP will load, then you can just select to restart the phone from it and it will ask if you want to root the phone, swipe to confirm and it will do it and restart the phone for you. Once the phone is booted you will need to finish the process - it should prompt you to update SuperSU, I selected the play store option, it downloaded and installed and was done. From there do yourself a favor and install AdAway
waiting for the firmware image..... anybody knows where to get it?
It has been posted to one of the various sites. I grabbed it the other night but couldn't tell you which site it was from as I am at work right now. Enough searching should find it.
Steve-x said:
It has been posted to one of the various sites. I grabbed it the other night but couldn't tell you which site it was from as I am at work right now. Enough searching should find it.
Click to expand...
Click to collapse
Would you please send the download link when you are convinient? I searched and find this http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=25, but looks something wrong with the system.img.
Steve-x said:
I removed root using the option in Super SU and then flashed the system.img and recovery.img from 4.4.2 in fastboot.(probably didn't need to do anything with Super SU because I reflashed system.img)
I then let the phone update. When it was done I went back into fastboot and flashed TWRP to recovery, went into recovery and let it begin the root process. From there boot up and update Super SU and finish rooting.
Overall a pretty painless way to go from 4.4.2 to 4.4.4 without losing any data or settings. All of this assumes you have an unlocked bootloader of course.
Click to expand...
Click to collapse
Thanks, works a charm, went from rooted 4.4.2 to 4.4.4.
PS- I grew up in Langley.
I don't know if it's dumb luck or not, but I didn't even unroot and was able to accept OTA to 4.4.4.
This is what I did to prepare the phone:
- Uninstall Xposed Framework from within the Xposed installer itself. Left the installer app in place.
- Changed recovery from TWRP back to factory.
- Enabled all apps previously disabled.
At this point my phone was still rooted. I accepted the OTA and everything worked fine.
Afterwards, I re-installed Xposed from the installer app, and re-disabled the apps I don't use. But left the factory recovery in place since I don't have a need to go into TWRP for now.
Everything is working fine.
No Rogers Update?
I just picked up a Moto X (Brand New) It came with 4.2.2 Im with Rogers, It is a Rogers phone , its been 2 hours now still no software update notification. When I try to check manually in about phone, system update. Keeps telling me my device is up to date??
Any one experienced this before? Or am I being to impatient
Now, a dummy question: what is Rogers?
Rogers is the Canadian phone company that's selling the original Moto X
Thought I was good at this. Never mind.
So I have managed to brick my device after 6 hours of having it.
Managed to unlock the BL, install TWRP, but the OS has gone, and I have no way of getting the thing mounted to copy over a ROM or anything.
What's the best way for me to sort this out ?
I'm thinking I could buy an SD card, copy a ROM to it, then flash it via TWRP.
Is this the only option ?
Help
grifforama said:
Thought I was good at this. Never mind.
So I have managed to brick my device after 6 hours of having it.
Managed to unlock the BL, install TWRP, but the OS has gone, and I have no way of getting the thing mounted to copy over a ROM or anything.
What's the best way for me to sort this out ?
I'm thinking I could buy an SD card, copy a ROM to it, then flash it via TWRP.
Is this the only option ?
Help
Click to expand...
Click to collapse
If you can get to the bootloader then just use the restore to stock tool from shawn5162. Should work fine as long as you have successfully unlocked the bootloader. Here is the link http://forum.xda-developers.com/moto-x-style/development/windows-tool-moto-x-style-pure-edition-t3199905
Should be clear that this will put your device to LP 5.1.1 without root or TWRP. Then just do the OTA MM update and re-root and flash TWRP. You can follow this guide I created if you like.
http://forum.xda-developers.com/moto-x-style/help/updating-to-mm-lp-moto-x-pure-t3270473
robn30 said:
If you can get to the bootloader then just use the restore to stock tool from shawn5162. Should work fine as long as you have successfully unlocked the bootloader. Here is the link http://forum.xda-developers.com/moto-x-style/development/windows-tool-moto-x-style-pure-edition-t3199905
Should be clear that this will put your device to LP 5.1.1 without root or TWRP. Then just do the OTA MM update and re-root and flash TWRP. You can follow this guide I created if you like.
http://forum.xda-developers.com/moto-x-style/help/updating-to-mm-lp-moto-x-pure-t3270473
Click to expand...
Click to collapse
Thanks for this, and I now have a booting , but wifi is not working ? I cannot connect to any wifi at all ? And when I try to turn wifi on, it turns itself off immediately ?
grifforama said:
Thanks for this, and I now have a booting , but wifi is not working ? I cannot connect to any wifi at all ? And when I try to turn wifi on, it turns itself off immediately ?
Click to expand...
Click to collapse
You have to flash correct modem to your device. Check that thread for more info.
kadopt said:
You have to flash correct modem to your device. Check that thread for more info.
Click to expand...
Click to collapse
I have never had such issues when setting up a phone before. Now I have this message
"there's a problem signing in to your google account on this device
Please sign in from a browser on your computer or tablet first, then try signing in again on this device"
Needless to say, I've done this numerous times, and I still cannot sign in on the phone.
Ugh.
grifforama said:
I have never had such issues when setting up a phone before. Now I have this message
"there's a problem signing in to your google account on this device
Please sign in from a browser on your computer or tablet first, then try signing in again on this device"
Needless to say, I've done this numerous times, and I still cannot sign in on the phone.
Ugh.
Click to expand...
Click to collapse
Ouch...Thats a security feature on MM... Only way ive found to avoid it is to restore a backup and before you wipe/flash your next ROM either disable the lockscreen(i.e. unsecured lockscreen), re-enable OEM unlocking, or factory reset your device from it from your running phone(not in TWRP) through settings->Backup and reset...that removes your google account from your phone so once you reset it you can set your phone up with your google account
pizzlewizzle said:
Ouch...Thats a security feature on MM... Only way ive found to avoid it is to restore a backup and before you wipe/flash your next ROM either disable the lockscreen(i.e. unsecured lockscreen), re-enable OEM unlocking, or factory reset your device from it from your running phone(not in TWRP) through settings->Backup and reset...that removes your google account from your phone so once you reset it you can set your phone up with your google account
Click to expand...
Click to collapse
Think I'm screwed. No backup. No ability to log into the OS to reset from within. Just keeps looping on the input screen.
I think I read somewhere that if you wait 72 hours it fixes itself. We'll see.
Joyful start to the year
grifforama said:
Think I'm screwed. No backup. No ability to log into the OS to reset from within. Just keeps looping on the input screen.
I think I read somewhere that if you wait 72 hours it fixes itself. We'll see.
Joyful start to the year
Click to expand...
Click to collapse
Why not use the restore to stock tool then before taking the update just make sure your phone has no security on it or the OEM unnlocked turned on...
pizzlewizzle said:
Why not use the restore to stock tool then before taking the update just make sure your phone has no security on it or the OEM unnlocked turned on...
Click to expand...
Click to collapse
That's what I've tried. I used the return to stock tool, and when it asks for my google email address and password, that's what it won't go past. that's exactly where I'm at right now. Stuck at the verification screen.
Is this an xt1575? If so, try my TWRP stock backup?
gokart2 said:
Is this an xt1575? If so, try my TWRP stock backup?
Click to expand...
Click to collapse
Can you give me me a link ?
grifforama said:
That's what I've tried. I used the return to stock tool, and when it asks for my google email address and password, that's what it won't go past. that's exactly where I'm at right now. Stuck at the verification screen.
Click to expand...
Click to collapse
hmmm thats weird... the new security feature wasn't implemented until MM... The restore to stock should take you to 5.1.1. not sure what else to try. Hopefully you can get in after the wait...next time you get your phone running make a backup to save a headache down the road
edit: you couldnt use the restore to stock then before it loads flash a 5.1 ROM?
gokart2 said:
Is this an xt1575? If so, try my TWRP stock backup?
Click to expand...
Click to collapse
Do you have a link ?
I keep trying and trying. I just keep getting sent back to a screen saying "This device was reset. To continue, sign in with a Google account that was previously synced on this device"
infuriating
http://www.androidpolice.com/2015/03/12/guide-what-is-android-5-1s-antitheft-device-protection-feature-and-how-do-i-use-it/
OK looks like this is a "feature" I guess. I'm stuck for 72 hours
grifforama said:
Can you give me me a link ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Its the stock TWRP backup from either 5.1.1 or 6.0....whichever you are currently supposed to be on.
wait, if this is a new phone and you had added your google account before "bricking," why cant you just sign in using that google account. My understanding is that the lockout is to prevent a NEW google account that was not associated with your phone from being used to set it up
pizzlewizzle said:
Ouch...Thats a security feature on MM... Only way ive found to avoid it is to restore a backup and before you wipe/flash your next ROM either disable the lockscreen(i.e. unsecured lockscreen), re-enable OEM unlocking, or factory reset your device from it from your running phone(not in TWRP) through settings->Backup and reset...that removes your google account from your phone so once you reset it you can set your phone up with your google account
Click to expand...
Click to collapse
That error means you don't have a 72 hour lock yet. Go to https://accounts.google.com/b/0/displayunlockcaptcha on your computer. Login, hit the accept button, then try logging in your phone. Your phone is not locked out, just to to the website. If you changed your password, though, then you shot yourself in the foot with the Google protection.
I'll make this as short and quick as I can. I had unlocked my bootloader, rooted my device and flashed a custom ROM(PureNexus) and TWRP. I had made a full nandroid backup and all was good.
Then the Android N Developer preview came along and I just HAD TO get it. So I used a tutorial on YouTube to ease the process and it went downhill from there. I used my fastboot folder and a command prompt to run the version of the file that wouldn't wipe my data.
When the device rebooted I noticed that none of my third party (downloaded) apps were working. I was upset and decided to just go back and restore my backup. That's when I noticed that I had no custom recovery anymore. I reinstalled TWRP, but when it loaded it told me my internal storage was encrypted. I tried the method of getting rid of all lock screen security and fingerprints but to no success. I also noticed that every time I reboot TWRP never seems to stick, I have to reinstall it through the fastboot folder and a command prompt every single time. I just wnna be able to get back to where i was and use my backup.
I'm lost on the situation, any suggestions guys? Any help is much appreciated
Big-K said:
I'll make this as short and quick as I can. I had unlocked my bootloader, rooted my device and flashed a custom ROM(PureNexus) and TWRP. I had made a full nandroid backup and all was good.
Then the Android N Developer preview came along and I just HAD TO get it. So I used a tutorial on YouTube to ease the process and it went downhill from there. I used my fastboot folder and a command prompt to run the version of the file that wouldn't wipe my data.
When the device rebooted I noticed that none of my third party (downloaded) apps were working. I was upset and decided to just go back and restore my backup. That's when I noticed that I had no custom recovery anymore. I reinstalled TWRP, but when it loaded it told me my internal storage was encrypted. I tried the method of getting rid of all lock screen security and fingerprints but to no success. I also noticed that every time I reboot TWRP never seems to stick, I have to reinstall it through the fastboot folder and a command prompt every single time. I just wnna be able to get back to where i was and use my backup.
I'm lost on the situation, any suggestions guys? Any help is much appreciated
Click to expand...
Click to collapse
Flash the MHC19I factory images to get back to a stock configuration, then start fresh; flash TWRP again (the latest) and then flash whatever ROM you want to use.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Thank you for the reply and info. I actually just got an RMA request approved because my Nexus also had some hardware issues. So my question now is, will my phone being rooted, with an unlocked bootloader, and in this condition have its warranty voided? Or am I good to exchange it just the way it is?
Big-K said:
Thank you for the reply and info. I actually just got an RMA request approved because my Nexus also had some hardware issues. So my question now is, will my phone being rooted, with an unlocked bootloader, and in this condition have its warranty voided? Or am I good to exchange it just the way it is?
Click to expand...
Click to collapse
The warranty isn't voided by unlocking or rooting, but you should return it to a stock configuration before sending it back anyway. Check out section 10 of my guide.
Heisenberg said:
The warranty isn't voided by unlocking or rooting, but you should return it to a stock configuration before sending it back anyway. Check out section 10 of my guide.
Click to expand...
Click to collapse
Thanks for all your help!
Big-K said:
Thanks for all your help!
Click to expand...
Click to collapse
No problems.
Lets see if it comes faster to our Device then Marshmellow...after Google released it to the Manufactures.
And it comes as it seems just to three Devices. (A9,M9, HTC 10)
I just got a OTA message to move from 3.39.531.7 to 3.39.531.12 I'm with T-MO and have it rooted with Teamwin recovery 2.8.7.1_CPTB-B1 on 6.0 Marshmallow
I just wish I knew how to do the upgrade all I do is go round and round, when I tell it to update it boots into the TRWP mentioned above and I have no idea what to do next.
guess I will wait until the smart people figure it out
rtoledo2002 said:
I just got a OTA message to move from 3.39.531.7 to 3.39.531.12 I'm with T-MO and have it rooted with Teamwin recovery 2.8.7.1_CPTB-B1 on 6.0 Marshmallow
I just wish I knew how to do the upgrade all I do is go round and round, when I tell it to update it boots into the TRWP mentioned above and I have no idea what to do next.
guess I will wait until the smart people figure it out
Click to expand...
Click to collapse
You can't install OTAs with a custom recovery. You'll need to flash the stock recovery first and try again.
Got that system security OTA notification as well today. I'm using the stock ROM with root (SuperSU flashed via TWRP). Can I stay rooted to apply the OTA with the stock recovery or do I have to flash the RUU first?
Solved:
Make a backup with Titanium or however you like. Save all your data from internal SD. Afterwards apply latest RUU.exe from HTC (depending on your carrier). If you wanna reroot, I would suggest SuperSU 2.65, because newer versions end up in bootloops.
Don't expect Nougat this year...
It's the August security update
Sent from my HTC One M9 using Tapatalk
hope this year released
matmaneyre said:
You can't install OTAs with a custom recovery. You'll need to flash the stock recovery first and try again.
Click to expand...
Click to collapse
Do you have 3.39.531.12 stock recovery??
missicolin said:
Do you have 3.39.531.12 stock recovery??
Click to expand...
Click to collapse
If you are flashing from 3.39.531.7 to .12 then you need the stock recovery from 3.39.531.7 to be installed.
If you've already flashed a custom recovery like TWRP, then just pull down the RUU from HTC's Web site. Be warned, however, that it will wipe the phone back to factory-fresh, so back up all your files/data/photos/music etc. and remove the SD card just to be safe.
RUU 531.12 T-Mobile
And to answer your specific question, I don't have the stock recovery for 531.12, but I presume that I will later today after I RUU my own device. I don't know how to archive the stock recovery but I plan to flash over it immediately with TWRP.
Amishrabbit said:
If you are flashing from 3.39.531.7 to .12 then you need the stock recovery from 3.39.531.7 to be installed.
If you've already flashed a custom recovery like TWRP, then just pull down the RUU from HTC's Web site. Be warned, however, that it will wipe the phone back to factory-fresh, so back up all your files/data/photos/music etc. and remove the SD card just to be safe.
RUU 531.12 T-Mobile
And to answer your specific question, I don't have the stock recovery for 531.12, but I presume that I will later today after I RUU my own device. I don't know how to archive the stock recovery but I plan to flash over it immediately with TWRP.
Click to expand...
Click to collapse
Is it okay if i flash the RUU with unlocked bootloader or do i need to relock it?
any news on Android N at least not official
drakeNas said:
Is it okay if i flash the RUU with unlocked bootloader or do i need to relock it?
Click to expand...
Click to collapse
you should
" fastboot oem lock "
to relock your bootloader - remeber - to save alll yor apps / settings (via TitaniumBackup for exaple) before
(re) unlocking bootlader will wipe all data
...
rtoledo2002 said:
I just got a OTA message to move from 3.39.531.7 to 3.39.531.12 I'm with T-MO and have it rooted with Teamwin recovery 2.8.7.1_CPTB-B1 on 6.0 Marshmallow
I just wish I knew how to do the upgrade all I do is go round and round, when I tell it to update it boots into the TRWP mentioned above and I have no idea what to do next.
guess I will wait until the smart people figure it out
Click to expand...
Click to collapse
I just got a OTA message and doing the upgrade to 3.39.531.21 will let you all know how it goes.
since I had TWRP installed , I had to download the RUU from HTC to do the first update to .12 , it went well 2 weeks ago when I first posted here, except it wiped out TWRP. then 3 days ago my phone started complaining , when ever I tried to change permissions on apps , with a message telling me to turn off draw over on the apps, all the searches on google, sent me to people telling me it was Twighlight causing the problem , EXCEPT I don't have that app installed, then it said something about turning off sidekeyborad? I never found it, I hard reset the phone, and as usual it ruined some of my contacts ?? I always loose 5 people I call all the time.
will post in here what new bugs crop up with this PART 2 upgrade of 7.0 nougat 63 things updating now
adios :cyclops:
rtoledo2002 said:
I just got a OTA message and doing the upgrade to 3.39.531.21 will let you all know how it goes.
since I had TWRP installed , I had to download the RUU from HTC to do the first update to .12 , it went well 2 weeks ago when I first posted here, except it wiped out TWRP. then 3 days ago my phone started complaining , when ever I tried to change permissions on apps , with a message telling me to turn off draw over on the apps, all the searches on google, sent me to people telling me it was Twighlight causing the problem , EXCEPT I don't have that app installed, then it said something about turning off sidekeyborad? I never found it, I hard reset the phone, and as usual it ruined some of my contacts ?? I always loose 5 people I call all the time.
will post in here what new bugs crop up with this PART 2 upgrade of 7.0 nougat 63 things updating now
adios :cyclops:
Click to expand...
Click to collapse
here is a screen shot
rtoledo2002 said:
then 3 days ago my phone started complaining , when ever I tried to change permissions on apps , with a message telling me to turn off draw over on the apps, all the searches on google, sent me to people telling me it was Twighlight causing the problem , EXCEPT I don't have that app installed, then it said something about turning off sidekeyborad? I never found it, I hard reset the phone, and as usual it ruined some of my contacts ??
Click to expand...
Click to collapse
That's not a bug but a security feature introduced by google. It's meant to prevent malicious apps from making you accept things/permissions you don't want (keyword: tapjacking). Go to settings > app > open the three dot menu > configure apps > draw over other apps. There you can revoke that permission from any suspicious app.
There is an article about tapjacking on the xda portal if anyone wants more information. It's called "How tapjacking made a return with android marshmallow - and nobody noticed". Btw, the article explains why the security feature isn't perfect, too. (Using xda labs at the moment I can't add a direct link to the article. However google should be able to find it.)
I just hope for the classic Non-GP Sense UI. The one with the Grid View Recent Apps.
HTC One M9 is the last chance for the full Sense experience on Nougat, because is the last Non-GP HTC that is being updated.
Rollout started
rhisendark said:
any news on Android N at least not official
Click to expand...
Click to collapse
Read that Rollout started in America for Brand free devices
HTC root mobiles cannot install OTA, RUU are only way when rooted
drakeNas said:
Is it okay if i flash the RUU with unlocked bootloader or do i need to relock it?
Click to expand...
Click to collapse
Yeah you only need to flasb the RUU it would solve your problem
Hello everybody!
I guess there are hundreds of threads out there about this topic, however, I could not find a clear answer to my question.
One week ago my Nexus 6p decided to go into a bootloop... I got a refurbished replacement by google because I am still in warranty.
However, I did not do a backup for a loooooong time (one year :/ ) and my photos are on the bootlooping phone.
Some of them are very dear to me.
No, I did not use google photos for backup, as I don't like google having rights to use my photos.
So, my phone is bootlooping. No, the bootloader is not unlocked. I am not sure if USB debugging is enabled or not.
If I go into fastboot i can identify my phone via terminal (fastboot devices).
If I go into recovery and enter adb devices nothing showes up. However, if i go into sideload via adb i can find my phone (adb devices), but not pull any data (adb pull does not work).
My question: Is there any possibility to get my pictures off that phone? If yes, what can I do.
If not, then thats it.
I am looking forward to some good advice! I hope someone might be able to help me
Thank you all!
@mori88 If you have already tried sideloading a full OTA in recovery mode, then you are done. Sideloading via ADB in recovery works because it is a different mode.
v12xke said:
@mori88 If you have already tried sideloading a full OTA in recovery mode, then you are done. Sideloading via ADB in recovery works because it is a different mode.
Click to expand...
Click to collapse
Well, I did not try to sideload a full OTA yet. I was not sure if it would delete all my data on the phone. But I am not sure it would let me access my data either...?
mori88 said:
Well, I did not try to sideload a full OTA yet. I was not sure if it would delete all my data on the phone. But I am not sure it would let me access my data either...?
Click to expand...
Click to collapse
OTA will not delete your data and is your last chance that I am aware of. The OTA needs to be newer than your current build. If it completes successfully you may be able to boot the phone... but you may not. You are just eliminating a software issue as being at fault (rather than the more likely hardware defect). If after flashing the OTA the OS won't load then "that's it".
v12xke said:
OTA will not delete your data and is your last chance that I am aware of. The OTA needs to be newer than your current build. If it completes successfully you may be able to boot the phone... but you may not. You are just eliminating a software issue as being at fault (rather than the more likely hardware defect). If after flashing the OTA the OS won't load then "that's it".
Click to expand...
Click to collapse
Well... nothing newer than Android O out there yet, so I guess I'm not lucky... :/
mori88 said:
Well... nothing newer than Android O out there yet, so I guess I'm not lucky... :/
Click to expand...
Click to collapse
Oh, so you are on OPR6.170623.019 ? It was the second September image that came out a week ago right after OPR6.170623.017 which was late. Usually there is only one image per month, but this month there were two because of the Android Pay issue. Go get the full OTA and sideload it from stock Recovery.