Greetings all. I was under the impression that one could download the latest OTA's from the images page from Google and sideload them so the phone wouldn't wipe itself in the process.
My version number is still at the April security patch but I downloaded the May patch MTC19T, followed the instructions on the google page but for some reason it didn't sideload. In fact after I issued the command to sideload it said it was loading it but the came back with a "no device connected." No I know it WAS connected because I ran the "adb devices" before I issued the load command and it did indeed return my device serial #.
Any help or ideas? I'm using terminal on mac and I've never had problems before. I used my mac and terminal to return the device to factory original after running Pure Nexus for months (because of work stuff) so I know it works. I'm bootloader locked (is that the problem?) and factory stock image, stock recovery...just the way the IT department likes it
Vref said:
Greetings all. I was under the impression that one could download the latest OTA's from the images page from Google and sideload them so the phone wouldn't wipe itself in the process.
My version number is still at the April security patch but I downloaded the May patch MTC19T, followed the instructions on the google page but for some reason it didn't sideload. In fact after I issued the command to sideload it said it was loading it but the came back with a "no device connected." No I know it WAS connected because I ran the "adb devices" before I issued the load command and it did indeed return my device serial #.
Any help or ideas? I'm using terminal on mac and I've never had problems before. I used my mac and terminal to return the device to factory original after running Pure Nexus for months (because of work stuff) so I know it works. I'm bootloader locked (is that the problem?) and factory stock image, stock recovery...just the way the IT department likes it
Click to expand...
Click to collapse
Have you tried switching ports?
Bootloader locked will cause a problem..
You need to be unlocked to issue the fastboot commands
I had the same issue with the no device found after issuing the ./adb sideload "ota.zip" command.. I simply unplugged the cable from the machine and plugged it back in, and the system found the device and pushed the .zip. However, I've also noticed that after pushing the update (done this three times now) it still boots up showing the April 2nd patch update instead of the May patch.
edit: Forgot to note that I'm also using a Mac, no root, stock, etc, etc...
DJBhardwaj said:
Have you tried switching ports?
Click to expand...
Click to collapse
Nope...didn't think that would be an issue but I can always try.
brichardson1991 said:
Bootloader locked will cause a problem..
You need to be unlocked to issue the fastboot commands
Click to expand...
Click to collapse
Is there no other way to load the OTA? When I hit "Check for updates" it always comes back with "system up to date."
I can see the device with ./adb devices, but there's no way to sideload while locked bootloader?
mgrass said:
I had the same issue with the no device found after issuing the ./adb sideload "ota.zip" command.. I simply unplugged the cable from the machine and plugged it back in, and the system found the device and pushed the .zip. However, I've also noticed that after pushing the update (done this three times now) it still boots up showing the April 2nd patch update instead of the May patch.
edit: Forgot to note that I'm also using a Mac, no root, stock, etc, etc...
Click to expand...
Click to collapse
Sounds like with locked bootloader we may be stuck with the April update. I just don't understand why when I force it to look for the update it says there isn't one when there clearly is one...its on Googles own site
brichardson1991 said:
Bootloader locked will cause a problem..
You need to be unlocked to issue the fastboot commands
Click to expand...
Click to collapse
You're talking about flashing the factory images with fastboot, he's talking about sideloading the full OTA.
Vref said:
Nope...didn't think that would be an issue but I can always try.
Is there no other way to load the OTA? When I hit "Check for updates" it always comes back with "system up to date."
I can see the device with ./adb devices, but there's no way to sideload while locked bootloader?
Sounds like with locked bootloader we may be stuck with the April update. I just don't understand why when I force it to look for the update it says there isn't one when there clearly is one...its on Googles own site
Click to expand...
Click to collapse
Your bootloader status is irrelevant. I'm not sure why it isn't working for you but it definitely isn't because of your bootloader.
Heisenberg said:
Your bootloader status is irrelevant. I'm not sure why it isn't working for you but it definitely isn't because of your bootloader.
Click to expand...
Click to collapse
Roger that. Thanks Heisenberg... I'll give it another go tonight.
Vref said:
Roger that. Thanks Heisenberg... I'll give it another go tonight.
Click to expand...
Click to collapse
Can we get a confirmation that you are using the proper file? Mind posting the zip name?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Can we get a confirmation that you are using the proper file? Mind posting the zip name?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
LOL...what, no faith in my reading skills? :laugh::laugh:
It was the correct file. Just tried it again and initially got the same result, adb devices returns the phone serial# but commands won't sideload. Swapped ports three times (on a macbook with only two USB ports ) and it finally updated. Checked build# afterwards and I'm now on 19T. Thanks guys(gals? who knows, its the internet)!
Vref said:
LOL...what, no faith in my reading skills? :laugh::laugh:
It was the correct file. Just tried it again and initially got the same result, adb devices returns the phone serial# but commands won't sideload. Swapped ports three times (on a macbook with only two USB ports ) and it finally updated. Checked build# afterwards and I'm now on 19T. Thanks guys(gals? who knows, its the internet)!
Click to expand...
Click to collapse
How in the world did it finally work? Lol well as long as things are running fine, that's great! I use a mac as well so I was hoping it wasn't anything specific to Apple causing trouble.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
How in the world did it finally work? Lol well as long as things are running fine, that's great! I use a mac as well so I was hoping it wasn't anything specific to Apple causing trouble.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Dunno how or why it finally took but this isn't the first time I've had to switch from port to port (like a drunken sailor) to get it to see the phone but I've always attributed that to Android File Transfer being a little b!tch. I can tell you when I restored from Pure Nexus and relocked the bootloader two weeks ago it worked 4.0....not a clue as to why it got all fussy today.
Vref said:
Nope...didn't think that would be an issue but I can always try.
Is there no other way to load the OTA? When I hit "Check for updates" it always comes back with "system up to date."
I can see the device with ./adb devices, but there's no way to sideload while locked bootloader?
Sounds like with locked bootloader we may be stuck with the April update. I just don't understand why when I force it to look for the update it says there isn't one when there clearly is one...its on Googles own site
Click to expand...
Click to collapse
my friends nexus 6 was showing the same problem "system upto date" even though it had april patch. i tried updating all his google apps via playstore. after updating all his google apps i tried "Check for updates" and voilà it was working, it downloaded the 60mb may update.
billamin said:
my friends nexus 6 was showing the same problem "system upto date" even though it had april patch. i tried updating all his google apps via playstore. after updating all his google apps i tried "Check for updates" and voilà it was working, it downloaded the 60mb may update.
Click to expand...
Click to collapse
Cool. Glad you got it working.
Related
Hi there,
I sideloaded the OTA (downloaded from google) and installed it using the adb method for my 2013 32GB wifi edition.
The OTA installed fine and the device booted up without issue. However, on the lockscreen no input was registered on the touchscreen.
I double-checked the md5 of the file and that I had downloaded the wifi version. I tried a full wipe, still no touchscreen.
I then went and downloaded the factory image for 4.4 from google and installed that.
Again, this installed perfectly but the touchscreen still does not work.
The device was working perfectly prior to flashing so I'm mystified.
Any suggestions before I RMA this device??
Cheers,
Euan.
sstmax said:
Hi there,
I sideloaded the OTA (downloaded from google) and installed it using the adb method for my 2013 32GB wifi edition.
The OTA installed fine and the device booted up without issue. However, on the lockscreen no input was registered on the touchscreen.
I double-checked the md5 of the file and that I had downloaded the wifi version. I tried a full wipe, still no touchscreen.
I then went and downloaded the factory image for 4.4 from google and installed that.
Again, this installed perfectly but the touchscreen still does not work.
The device was working perfectly prior to flashing so I'm mystified.
Any suggestions before I RMA this device??
Cheers,
Euan.
Click to expand...
Click to collapse
I'm not being funny but why are so many people impatient to get the update ? it's going to be here in a few days so if you don't know the proper steps to flash a correct working update then don't attempt it in the first place.
You'll be lucky if they RMA it once they see it's been flashed.
Ady1976 said:
you don't know the proper steps to flash a correct working update then don't attempt it in the first place.
Click to expand...
Click to collapse
... except I followed the proper steps....
Well, I reflashed 4.3 from the factory image and the touchscreen works again!
Something is odd with the OTA and the Factory image for 4.4 when installed on my device.
Any constructive thoughts are much appreciated in case this helps others.
Ady1976 said:
I'm not being funny but why are so many people impatient to get the update ? it's going to be here in a few days so if you don't know the proper steps to flash a correct working update then don't attempt it in the first place.
You'll be lucky if they RMA it once they see it's been flashed.
Click to expand...
Click to collapse
Updating via a sideloaded OTA is done while the bootloader is locked, using the same file that would eventually be pushed out. I find it hard to see how this means he would be lucky to get an RMA?
sstmax - strange the 4.3 works. The sideloaded OTA worked fine for me.
sstmax said:
... except I followed the proper steps....
Well, I reflashed 4.3 from the factory image and the touchscreen works again!
Something is odd with the OTA and the Factory image for 4.4 when installed on my device.
Any constructive thoughts are much appreciated in case this helps others.
Click to expand...
Click to collapse
I was going to attempt it myself until all the guides I found on here didn't make any sense or didn't apply to my setup ie renaming folder names from the android SDK which didn't even exist in the SDK I downloaded which was pointed out in 1 of the guides so I figured something could get messed up and I'm glad I haven't bothered.
My theory is google have not pushed it yet because there is still issues on some devices as you have just found out.At the end of the day they don't wan't a mass recall just because of a software update.
I would just leave 4.3 if that's working for you now until they officially push it.
---------- Post added at 11:58 PM ---------- Previous post was at 11:54 PM ----------
indigolemon said:
Updating via a sideloaded OTA is done while the bootloader is locked, using the same file that would eventually be pushed out. I find it hard to see how this means he would be lucky to get an RMA?
sstmax - strange the 4.3 works. The sideloaded OTA worked fine for me.
Click to expand...
Click to collapse
As for sideloading I wasn't aware that could be done with the bootloader still locked ?
Either way the "So Called" OTA is on google's dev page so as far as I'm concerned it's for developers to test and is not official as such.
Ady1976 said:
As for sideloading I wasn't aware that could be done with the bootloader still locked ?
Either way the "So Called" OTA is on google's dev page so as far as I'm concerned it's for developers to test and is not official as such.
Click to expand...
Click to collapse
Yep, done via the built in recovery using ADB, and I think you're confusing the OTA with the Factory Images. Either way, as long as you have adb and fastboot in your path it's normally a very painless process.
There is nothing wrong with sideloading as it verifies the system MD5 before flashing. It wouldn't ruin or impede chances of receiving an RMA over anyone who received the update via OTA.
Sent from my Nexus 7 using XDA Premium 4 mobile app
indigolemon said:
Yep, done via the built in recovery using ADB, and I think you're confusing the OTA with the Factory Images. Either way, as long as you have adb and fastboot in your path it's normally a very painless process.
Click to expand...
Click to collapse
I tried it with a locked bootloader and I couldn't get into the recovery menu to initiate an adb sideload. Unlocking the bootloader resolved this issue.
Regards,
Dave
Sent from my SM-N9005 using Tapatalk
Well, I reset the device with the 4.3 factory image and all was fine. The OTA for 4.4 came in last night and the issue returned - no input registered on the touchscreen!
Looks like I'll have to RMA after all. Annoying as the hardware works fine on 4.3.
Sent from my Nexus 5 using xda app-developers app
sstmax said:
Well, I reset the device with the 4.3 factory image and all was fine. The OTA for 4.4 came in last night and the issue returned - no input registered on the touchscreen!
Looks like I'll have to RMA after all. Annoying as the hardware works fine on 4.3.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
You might want to try this thread:
http://forum.xda-developers.com/showthread.php?t=2428133
Given your sypmtoms, there's a reasonable chance it can allow your 4.4 to work with your touchscreen.
Been toying with some development which has led to a few factory restarts... On the latest, Kingroot won't root
positivehxcgo said:
Been toying with some development which has led to a few factory restarts... On the latest, Kingroot won't root
Click to expand...
Click to collapse
just try kingroot 4.1 (New Version)
has worked for me
LG Noah
Hi I've tried both Kingroot 4.0 and 4.1 but still having no luck rooting. Do they work with fire OS 4.5.4?
jon_lad said:
Hi I've tried both Kingroot 4.0 and 4.1 but still having no luck rooting. Do they work with fire OS 4.5.4?
Click to expand...
Click to collapse
There is no official download for 4.5.4 yet, did you get it OTA ? If so, it's a big warning for everybody out there to disable the OTA updates!!!
Most likely Amazon fixed the Kingroot exploit, so I'd be actually surprised if 4.5.4 is rootable via the same approach as before.
Fellas, cherish the root that you got, and don't even think about updating !!!
Is there any way to downgrade to 4.5.3 without going through Amazon?
what is the command line to disable auto update ?
and does it auto update ?
alucard_xs said:
what is the command line to disable auto update ?
and does it auto update ?
Click to expand...
Click to collapse
Code:
pm block com.amazon.otaverifier
You can also use my tool in OG dev to do it also.
jmz said:
Code:
pm block com.amazon.otaverifier
You can also use my tool in OG dev to do it also.
Click to expand...
Click to collapse
Thanks so just adb to my device and this command line is enough ?
alucard_xs said:
Thanks so just adb to my device and this command line is enough ?
Click to expand...
Click to collapse
yes. I dunno if it gets reset on boot or not. I think it does.
My tool also does
Code:
mv /system/priv-app/DeviceSoftwareOTA.apk /system/priv-app/DeviceSoftwareOTA.apk.bak
Yeah it was an OTA update. Literally just as is was getting my laptop out to block them
otaverifier stays blocked with boot
jmz said:
yes. I dunno if it gets reset on boot or not. I think it does.
Click to expand...
Click to collapse
Hi--Haven't been able to use your tool yet, but with the adb shell command you showed, otaverifier stays blocked through reboots. (Used Debloater by GatesJunior to confirm)
.
DoLooper said:
Hi--Haven't been able to use your tool yet, but with the adb shell command you showed, otaverifier stays blocked through reboots. (Used Debloater by GatesJunior to confirm)
.
Click to expand...
Click to collapse
Ok. I wasn't sure.
what is the exact command line ? wihing adb
"pm block com.amazon.otaverifier" is not ok for me, it tells me it's not a program in adb,
do I have to write adb in front of pm ?
alucard_xs said:
what is the exact command line ? wihing adb
"pm block com.amazon.otaverifier" is not ok for me, it tells me it's not a program in adb,
do I have to write adb in front of pm ?
Click to expand...
Click to collapse
Code:
adb shell pm block com.amazon.otaverifier
Same thing happened to me today. A few days ago I put my kindle back to factory settings, turned it on today to start playing around with it, only to find it had started to update. Tried various ways to stop this from happening, but none succeeded and sadly my kindle has now updated itself which is so annoying.
Anyway, I presume there no way to roll it back, and I think I may just sell mine, even though its probably worth nothing now it cant be rooted
CrazyRach said:
Same thing happened to me today. A few days ago I put my kindle back to factory settings, turned it on today to start playing around with it, only to find it had started to update. Tried various ways to stop this from happening, but none succeeded and sadly my kindle has now updated itself which is so annoying.
Anyway, I presume there no way to roll it back, and I think I may just sell mine, even though its probably worth nothing now it cant be rooted
Click to expand...
Click to collapse
had this happen to one of my hd6's a few days ago because i forgot to block ota updates after rooting.
i was able to get downgraded back to 4.5.3 by amazon support, then i blocked ota updates, and contacted support again to have them move my device back to the normal ota update pool to keep the ability to update in the future if another root method appears that works against newer updates/kernels so then ota can be re-enabled at that point in time
jon_lad said:
Hi I've tried both Kingroot 4.0 and 4.1 but still having no luck rooting. Do they work with fire OS 4.5.4?
Click to expand...
Click to collapse
blackwat3r said:
had this happen to one of my hd6's a few days ago because i forgot to block ota updates after rooting.
i was able to get downgraded back to 4.5.3 by amazon support, then i blocked ota updates, and contacted support again to have them move my device back to the normal ota update pool to keep the ability to update in the future if another root method appears that works against newer updates/kernels so then ota can be re-enabled at that point in time
Click to expand...
Click to collapse
Wow, lucky you !!! Remember that you can always update manually, so the whole OTA pool is kind of useless.
But I wonder if there is a way to intercept Amazon's downgrade to one's Fire, and use it to downgrade other devices. There must be a moment when that downgrade bin sitting nicely in /cache, waiting to be copied ...
Perhaps, after a downgrade, you can try to recover the downgrade bin file from the system?
bibikalka said:
Wow, lucky you !!! Remember that you can always update manually, so the whole OTA pool is kind of useless.
But I wonder if there is a way to intercept Amazon's downgrade to one's Fire, and use it to downgrade other devices. There must be a moment when that downgrade bin sitting nicely in /cache, waiting to be copied ...
Perhaps, after a downgrade, you can try to recover the downgrade bin file from the system?
Click to expand...
Click to collapse
i actually had my device proxied via burpsuite while contacting support and them conducting the rollback but wasnt able to capture anything
one interesting thing i noticed while having the hd6 proxied is that the silk browser constantly tries to phone home to internal.amazon.com
blackwat3r said:
had this happen to one of my hd6's a few days ago because i forgot to block ota updates after rooting.
i was able to get downgraded back to 4.5.3 by amazon support, then i blocked ota updates, and contacted support again to have them move my device back to the normal ota update pool to keep the ability to update in the future if another root method appears that works against newer updates/kernels so then ota can be re-enabled at that point in time
Click to expand...
Click to collapse
What exactly do you say to customer support in order for them to roll your firmware back. I do find it very annoying there you can't opt out of ota. I mean even Apple give you the option.
CrazyRach said:
What exactly do you say to customer support in order for them to roll your firmware back. I do find it very annoying there you can't opt out of ota. I mean even Apple give you the option.
Click to expand...
Click to collapse
apologies for the delayed response,
ive been dealing with a serious injury over the past few days.
i just went and told them that after updating to 4.5.4 i was having issues with the screen flickering and glitching, and system lags that persisted across factory resets.
if i have the time to try later im gonna see if i can get them to roll back one of my other devices while monitoring my entire network this time vs just proxying the device via burpsuite like i did before, then perhaps this may shed some light on the rollback/upgrade process
When I got my phone last month, I unlocked the bootloader and installed TWRP. I just got the march OTA and it will not update. It just boots into TWRP and doesnt update. How do I update to the newest patch?
UntamedTyrant said:
When I got my phone last month, I unlocked the bootloader and installed TWRP. I just got the march OTA and it will not update. It just boots into TWRP and doesnt update. How do I update to the newest patch?
Click to expand...
Click to collapse
I'd assume that you have to manually flash it with the zip. I'm not sure how it is with a 6p, but with my Oneplus devices that's how it worked.
UntamedTyrant said:
When I got my phone last month, I unlocked the bootloader and installed TWRP. I just got the march OTA and it will not update. It just boots into TWRP and doesnt update. How do I update to the newest patch?
Click to expand...
Click to collapse
You can't flash an OTA with TWRP, and you can't take an OTA if you have root/modifications. If you've never rooted or modified in any way you should be able to just flash the stock recovery back and then initiate the OTA process. If you do have root you need to flash the factory images to update. See my guide for details:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Sr Vincenzo said:
I'd assume that you have to manually flash it with the zip. I'm not sure how it is with a 6p, but with my Oneplus devices that's how it worked.
Click to expand...
Click to collapse
This is why it's best to stick to giving advice for devices that you own and are familiar with.
Heisenberg said:
This is why it's best to stick to giving advice for devices that you own and are familiar with.
Click to expand...
Click to collapse
I understand that. However it was just an assumption, i never said it would actually work. I'm still trying to learn this device myself as it is my first and only Nexus.
Sr Vincenzo said:
I understand that. However it was just an assumption, i never said it would actually work. I'm still trying to learn this device myself as it is my first and only Nexus.
Click to expand...
Click to collapse
Ok, but you need to realise that people could still try whatever you're assuming and posting here. If what you're posting is incorrect, it could cause major problems for them. What I'm saying is this: do your learning for this device first, and then advise people one you know the information you're giving is solid.
Heisenberg said:
Ok, but you need to realise that people could still try whatever you're assuming and posting here. If what you're posting is incorrect, it could cause major problems for them. What I'm saying is this: do your learning for this device first, and then advise people one you know the information you're giving is solid.
Click to expand...
Click to collapse
Alright man...
Some people should never unlock their bootloader or root their phone.
UntamedTyrant said:
When I got my phone last month, I unlocked the bootloader and installed TWRP. I just got the march OTA and it will not update. It just boots into TWRP and doesnt update. How do I update to the newest patch?
Click to expand...
Click to collapse
I used Heisenberg's method yesterday and it worked well. If you copy the commands into notepad, edit them so the file paths and build numbers are correct you can just copy/paste into the command prompt. All settings will be saved with the exception of a couple of widgets I had to redo.
I will say with the latest update the device seems faster so I feel like it is worth it.
I applied the wrong ota file by mistake and now the phone is stuck in bootloop.
phone is unlocked and "fastboot flashing unlock" won't work as unlocking was disabled in developer options.
Factory reset didn't work. Further, getting the Google's device corrupted message during the bootloop.
Any solutions?
sumit29 said:
I applied the wrong ota file by mistake and now the phone is stuck in bootloop.
phone is unlocked and "fastboot flashing unlock" won't work as unlocking was disabled in developer options.
Factory reset didn't work. Further, getting the Google's device corrupted message during the bootloop.
Any solutions?
Click to expand...
Click to collapse
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Heisenberg said:
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Click to expand...
Click to collapse
Is it possible to downgrade to an older OTA? I received DP3, got a bootloop. Tried sideloading, wiping, nothing solved.
I´m trying to sideload DP2 but it gives me this error:
Cant install this package over newer build
E: error in /sideload/package.zip (Status 7)
gasparzim said:
Is it possible to downgrade to an older OTA? I received DP3, got a bootloop. Tried sideloading, wiping, nothing solved.
I´m trying to sideload DP2 but it gives me this error:
Cant install this package over newer build
E: error in /sideload/package.zip (Status 7)
Click to expand...
Click to collapse
No, as per the instructions in my guide you can only install a newer build. I wasn't aware that full OTA zips were even available for the Developer Previews.
Heisenberg said:
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Click to expand...
Click to collapse
Have already tried doing this...this also gets interrupted mid-way, with the command terminal showing - "connection reset by peer". these are the same OTA files available on the google developers website.
and for some reason, it worked this time around!!!
Heisenberg said:
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Click to expand...
Click to collapse
hey can you help me please? i was on marshamllow and yesterday when the android n beta came i installed it through ota update. after it installed and started booting up for the first time it does not boot up. the android boot animation keeps on going for hours. i tried wiping cache and doing factory reset to but its still the same. i cant flash stock image since i didnt enable oem unlocking.
Ame123 said:
hey can you help me please? i was on marshamllow and yesterday when the android n beta came i installed it through ota update. after it installed and started booting up for the first time it does not boot up. the android boot animation keeps on going for hours. i tried wiping cache and doing factory reset to but its still the same. i cant flash stock image since i didnt enable oem unlocking.
Click to expand...
Click to collapse
Same problem have you been able to sort it out yet?
Ame123 said:
hey can you help me please? i was on marshamllow and yesterday when the android n beta came i installed it through ota update. after it installed and started booting up for the first time it does not boot up. the android boot animation keeps on going for hours. i tried wiping cache and doing factory reset to but its still the same. i cant flash stock image since i didnt enable oem unlocking.
Click to expand...
Click to collapse
AlfexOmega said:
Same problem have you been able to sort it out yet?
Click to expand...
Click to collapse
I don't know what you can do, sorry. I'm not sure why you wouldn't just unlock your bootloader and leave it unlocked, that alone would mean you could fix this issue in a matter of minutes. I know me saying this is of no use to you right now, but hopefully it'll impress on you (and anyone reading) the importance of having a fail-safe when things go sideways like this.
Heisenberg said:
I don't know what you can do, sorry. I'm not sure why you wouldn't just unlock your bootloader and leave it unlocked, that alone would mean you could fix this issue in a matter of minutes. I know me saying this is of no use to you right now, but hopefully it'll impress on you (and anyone reading) the importance of having a fail-safe when things go sideways like this.
Click to expand...
Click to collapse
i did not think that the update will break the device and since i didnt wish to unlock the bootloader as all my data could have gone. do you know where i can report to google so that they an fix this issue in next ota update?
---------- Post added at 02:50 PM ---------- Previous post was at 02:50 PM ----------
AlfexOmega said:
Same problem have you been able to sort it out yet?
Click to expand...
Click to collapse
no.:crying::crying:
Ame123 said:
i did not think that the update will break the device and since i didnt wish to unlock the bootloader as all my data could have gone. do you know where i can report to google so that they an fix this issue in next ota update?
---------- Post added at 02:50 PM ---------- Previous post was at 02:50 PM ----------
no.:crying::crying:
Click to expand...
Click to collapse
An update failing is the single most likely cause of a problem like this. The issue here isn't with the update itself, otherwise pretty much every other user taking the update would be experiencing the same thing. There could be any number of reasons for this update going badly for you.
If you had researched you would have known that you need to unlock the bootloader when you first get the device, before you commit too much data to it. Either that or just back up your personal data, unlock the bootloader and then copy your data back. Surely even that is a better option that being stuck in a situation like this where you essentially have a brick.
All you can do now is contact Google support, explain what has happened, and ship it off to them to have it fixed. You shouldn't have to pay if it genuinely wasn't your fault. And remember to unlock your bootloader when you get it back.
Heisenberg said:
An update failing is the single most likely cause of a problem like this. The issue here isn't with the update itself, otherwise pretty much every other user taking the update would be experiencing the same thing. There could be any number of reasons for this update going badly for you.
If you had researched you would have known that you need to unlock the bootloader when you first get the device, before you commit too much data to it. Either that or just back up your personal data, unlock the bootloader and then copy your data back. Surely even that is a better option that being stuck in a situation like this where you essentially have a brick.
All you can do now is contact Google support, explain what has happened, and ship it off to them to have it fixed. You shouldn't have to pay if it genuinely wasn't your fault. And remember to unlock your bootloader when you get it back.
Click to expand...
Click to collapse
the place where i stay does not have any support so that i can ship to them. i bought the device from uk but now i stay in UAE. I dont know what to do now:crying::crying: . Also there are many such cases on xda having the same issue.
Ame123 said:
i did not think that the update will break the device and since i didnt wish to unlock the bootloader as all my data could have gone. do you know where i can report to google so that they an fix this issue in next ota update?
---------- Post added at 02:50 PM ---------- Previous post was at 02:50 PM ----------
no.:crying::crying:
Click to expand...
Click to collapse
Mine is also still messed up I'm calling the store where I bought it to see if they can do anything highly doubt they will though
Ame123 said:
the place where i stay does not have any support so that i can ship to them. i bought the device from uk but now i stay in UAE. I dont know what to do now:crying::crying: . Also there are many such cases on xda having the same issue.
Click to expand...
Click to collapse
Oh, that is not a good situation at all. You might need to find a good repairer in your area and pay for them to fix it for you.
Heisenberg said:
Oh, that is not a good situation at all. You might need to find a good repairer in your area and pay for them to fix it for you.
Click to expand...
Click to collapse
I've heard that it's basically unrepairable.. As there is literally no way to flash android again without an unlocked bootloader and with OEM unlocking disabled
AlfexOmega said:
I've heard that it's basically unrepairable.. As there is literally no way to flash android again without an unlocked bootloader and with OEM unlocking disabled
Click to expand...
Click to collapse
An accredited repair centre should have access to software tools that can do it.
AlfexOmega said:
I've heard that it's basically unrepairable.. As there is literally no way to flash android again without an unlocked bootloader and with OEM unlocking disabled
Click to expand...
Click to collapse
ADB Sideload the developer 3 preview 3 like the other user successfully did.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
ADB Sideload the developer 3 preview 3 like the other user successfully did.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
did not understood what you said. can you explain a little bit more?
Heisenberg said:
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Click to expand...
Click to collapse
Ame123 said:
did not understood what you said. can you explain a little bit more?
Click to expand...
Click to collapse
Sure, see the above post.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Sure, see the above post.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I've tried sideloading multiple times and they succeeded however my phone is still not booting :/
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.