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 :/
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.
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.
Recieved my 6P on Tuesday, it updated to 6.0.1 and it's currently build number MMB29P but when I hit "System Update" it says it last checked 2 mins ago and my system is up to date but isn't the latest build MHC19I? Any idea what the issue is?
USFguy said:
Recieved my 6P on Tuesday, it updated to 6.0.1 and it's currently build number MMB29P but when I hit "System Update" it says it last checked 2 mins ago and my system is up to date but isn't the latest build MHC19I? Any idea what the issue is?
Click to expand...
Click to collapse
This seems to happen to done some people, no idea why though. You can update manually pretty easily, just flash the factory images for the latest build. I have instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
This seems to happen to done some people, no idea why though. You can update manually pretty easily, just flash the factory images for the latest build. I have instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thanks, I haven't used adb since 2014 with my HTC One X so I'm a little hesitant but seems easy enough.
Question if I manually update will that have any interference with future OTA's? As in would I have to manually flash from here on out?
USFguy said:
Question if I manually update will that have any interference with future OTA's? As in would I have to manually flash from here on out?
Click to expand...
Click to collapse
no, everything will just fine..
USFguy said:
Question if I manually update will that have any interference with future OTA's? As in would I have to manually flash from here on out?
Click to expand...
Click to collapse
Nope, it has no effect on future OTA's.
Heisenberg said:
Nope, it has no effect on future OTA's.
Click to expand...
Click to collapse
Just unlock bootloader and flash?
USFguy said:
Just unlock bootloader and flash?
Click to expand...
Click to collapse
Yeah that's it, unlock your bootloader and flash the factory images for MHC19I and you'll be up to date.
I have the same problem , i got the phone from bestbuy today it updated to MMB29P and thats it no more updates?
samomamo said:
I have the same problem , i got the phone from bestbuy today it updated to MMB29P and thats it no more updates?
Click to expand...
Click to collapse
Did you read the other posts in this thread?
Heisenberg said:
Did you read the other posts in this thread?
Click to expand...
Click to collapse
Yes i don't wanna unlock the bootloader. I know how to do it. But its suppose to update automatically.
samomamo said:
Yes i don't wanna unlock the bootloader. I know how to do it. But its suppose to update automatically.
Click to expand...
Click to collapse
I'd suggest unlocking the bootloader anyway. If an OTA fails on you you'll be soft bricked and there'll be absolutely nothing you can do about it with a locked bootloader, apart from sending it for repair. It's happened to a few people.
Heisenberg said:
I'd suggest unlocking the bootloader anyway. If an OTA fails on you you'll be soft bricked and there'll be absolutely nothing you can do about it with a locked bootloader, apart from sending it for repair. It's happened to a few people.
Click to expand...
Click to collapse
Thanks alot bro, im just lazy to set everything up again.
samomamo said:
Thanks alot bro, im just lazy to set everything up again.
Click to expand...
Click to collapse
It's worth it, I know I'd rather spend the time setting my phone up again than having to send the thing away because it got bricked.
I'm also stuck on January's patch so I wanted to know if I'll get February, then March or does the ota go straight to the latest security patch? If I decide to manually flash it, would I have to flash the February patch first or go straight to they latest one?
Sent from my Nexus 6P using Tapatalk
toddalvandi said:
I'm also stuck on January's patch so I wanted to know if I'll get February, then March or does the ota go straight to the latest security patch? If I decide to manually flash it, would I have to flash the February patch first or go straight to they latest one?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
If you decide to flash manually, you have two options.
1. Flash the factory images (via fastboot). With this option you can just download the factory images for the latest build and flash them, no need to go through each update to get there.
2. Flash the OTA zips (via stock recovery and adb sideload). This option means you need to flash the OTA zips in order. But since you're on the January build it would only be two zips: the MMP29P --> MMB29Q zip, then the MMB29Q -- > MHC19I zip.
Personally, I'd just flash the factory images with fastboot, it's easier. You do need an unlocked bootloader though, but in my opinion you should have an unlocked bootloader regardless.
Heisenberg said:
It's worth it, I know I'd rather spend the time setting my phone up again than having to send the thing away because it got bricked.
Click to expand...
Click to collapse
Thanks a lot u convinced me. I unlocked and for the hell of it flashed the Android N. Man is so fast , its like running 60fps, I thought its just gonna be little ui changes, but i was wrong. Its like lightning fast. Thanks
Ok it didnt last long. Back to M latest. The N was fast, but toooo many glitches.
Heisenberg said:
If you decide to flash manually, you have two options.
1. Flash the factory images (via fastboot). With this option you can just download the factory images for the latest build and flash them, no need to go through each update to get there.
2. Flash the OTA zips (via stock recovery and adb sideload). This option means you need to flash the OTA zips in order. But since you're on the January build it would only be two zips: the MMP29P --> MMB29Q zip, then the MMB29Q -- > MHC19I zip.
Personally, I'd just flash the factory images with fastboot, it's easier. You do need an unlocked bootloader though, but in my opinion you should have an unlocked bootloader regardless.
Click to expand...
Click to collapse
Just getting time to sit down and do this, I've gone and got all the SDK tools setup in the general thread you linked, and I know i have to unlock bootloader but for the factory image does it matter if I do post #10 or #11? With the phone being 4 days old would flashing without wiping be a big issue?
USFguy said:
Just getting time to sit down and do this, I've gone and got all the SDK tools setup in the general thread you linked, and I know i have to unlock bootloader but for the factory image does it matter if I do post #10 or #11? With the phone being 4 days old would flashing without wiping be a big issue?
Click to expand...
Click to collapse
You should have no issues flashing the images without wiping userdata.
Heisenberg said:
You should have no issues flashing the images without wiping userdata.
Click to expand...
Click to collapse
Ah, but I think I answered my own question, won't unlocking the bootloader wipe all data anyway?
After unlocking bootloader message is coming your device is corrupt and can't be checked for corruption but after some time I have reverted to stock and relocked OEM using Nexus Root toolkit but even then warning is coming any way to remove this..
Mohit M'S said:
After unlocking bootloader message is coming your device is corrupt and can't be checked for corruption but after some time I have reverted to stock and relocked OEM using Nexus Root toolkit but even then warning is coming any way to remove this..
Click to expand...
Click to collapse
It is highly unlikely that after relocking that message would come. Actually, that message could be ignored if your ROM boots fine.
What does the bootloader display about locked status?
DJBhardwaj said:
It is highly unlikely that after relocking that message would come. Actually, that message could be ignored if your ROM boots fine.
What does the bootloader display about locked status?
Click to expand...
Click to collapse
Your device is corrupt and can't be checked for corruption
Mohit M'S said:
Your device is corrupt and can't be checked for corruption
Click to expand...
Click to collapse
Not that. I meant in the bootloader mode itself. Does it display "Device is Locked" or "Device is Unlocked"?
DJBhardwaj said:
Not that. I meant in the bootloader mode itself. Does it display "Device is Locked" or "Device is Unlocked"?
Click to expand...
Click to collapse
Device is locked
Mohit M'S said:
Device is locked
Click to expand...
Click to collapse
Unlock it again. Go from scratch and flash the factory image using Heisenberg's guide in the General section. After flashing that, see if it solves the issue.
Using toolkits could be buggy at times. I am not against them, but it's good to flash manually, so that you can keep a track on things.
DJBhardwaj said:
Unlock it again. Go from scratch and flash the factory image using Heisenberg's guide in the General section. After flashing that, see if it solves the issue.
Using toolkits could be buggy at times. I am not against them, but it's good to flash manually, so that you can keep a track on things.
Click to expand...
Click to collapse
can I flash without unlocking bootloader because after unlocking bootloader there r some heat issues
Mohit M'S said:
can I flash without unlocking bootloader because after unlocking bootloader there r some heat issues
Click to expand...
Click to collapse
No you can't flash anything with a locked bootloader. Plus, it's entirely impossible for an unlocked bootloader to cause heat issues, that's either placebo or a coincidence (another cause).
PS. The title of this thread is useless, you should describe your issue in the title, not create text faces.
Heisenberg said:
No you can't flash anything with a locked bootloader. Plus, it's entirely impossible for an unlocked bootloader to cause heat issues, that's either placebo or a coincidence (another cause).
PS. The title of this thread is useless, you should describe your issue in the title, not create text faces.
Click to expand...
Click to collapse
OK OK but after unlocking it there is any way to relock it and remove this error message
Mohit M'S said:
OK OK but after unlocking it there is any way to relock it and remove this error message
Click to expand...
Click to collapse
Yes, of course. Infact that's the reason I asked you about the lock status on the first place. Stock ROM with locked bootloader shouldn't give this warning. It should make it go away.
That is why, I asked you to perform a flash manually. Please refer to Heisenberg's guide for the steps.
Here is the link: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Mohit M'S said:
OK OK but after unlocking it there is any way to relock it and remove this error message
Click to expand...
Click to collapse
Yes, after locking the bootloader the message should disappear. But, I'd strongly recommend leaving it unlocked and just dealing with the message. If an OTA ever fails or something else goes wrong you'll need fastboot to flash the factory images to recover your device, you'll be forced to unlock the bootloader, this will wipe the device and you'll lose all of your data because there'll be no way to back it up first.
DJBhardwaj said:
Not that. I meant in the bootloader mode itself. Does it display "Device is Locked" or "Device is Unlocked"?
Click to expand...
Click to collapse
Sorry message is Device can't be trusted or it may not work properly
Mohit M'S said:
Sorry message is Device can't be trusted or it may not work properly
Click to expand...
Click to collapse
Did you reflash manually?
DJBhardwaj said:
Did you reflash manually?
Click to expand...
Click to collapse
Nope gonna do this by today or tomorrow
Mohit M'S said:
Nope gonna do this by today or tomorrow
Click to expand...
Click to collapse
Sure and then let us know. And keep the bootloader unlocked, it will help you to deal with a few issues (if any), in the future, as already mentioned above by Heisenberg.
-_____- why do people still use toolkits? Try getting use to Adb; it would save you a lot of time dealing with errors.
Mohit M'S said:
Sorry message is Device can't be trusted or it may not work properly
Click to expand...
Click to collapse
There is only one way to get rid of the message, and you have already been told.
The solution is to relock your bootloader. Nothing else will fix it.
uicnren said:
There is only one way to get rid of the message, and you have already been told.
The solution is to relock your bootloader. Nothing else will fix it.
Click to expand...
Click to collapse
First when I unlocked it message is coming your device is corrupt and can't be checked for corruption but after relocking it message is coming device can't be trusted or may not work properly and it is happening it is not working properly no system update for me even Android one got update and all my friends got update who r using it..??
Ruined my phone
Mohit M'S said:
First when I unlocked it message is coming your device is corrupt and can't be checked for corruption but after relocking it message is coming device can't be trusted or may not work properly and it is happening it is not working properly no system update for me even Android one got update and all my friends got update who r using it..
Ruined my phone
Click to expand...
Click to collapse
It didnt ruin your phone.
Simply reflash the stock images and start over from scratch.
If you root or modify the phone in any way from stock, you will get those messages. They are simply that, messages. They do not affect your phone negatively. Other things you have done (like root, or installing apps from unknown sources) WILL affect the phone.
Flash stock images, relock bootloader and it will be brand new, like the day you got it.
If you dont wish to go back to stock, but want to flash OTA updates when they come out (and you are already rooted) look into using FlashFire.
uicnren said:
It didnt ruin your phone.
Simply reflash the stock images and start over from scratch.
If you root or modify the phone in any way from stock, you will get those messages. They are simply that, messages. They do not affect your phone negatively. Other things you have done (like root, or installing apps from unknown sources) WILL affect the phone.
Flash stock images, relock bootloader and it will be brand new, like the day you got it.
If you dont wish to go back to stock, but want to flash OTA updates when they come out (and you are already rooted) look into using FlashFire.
Click to expand...
Click to collapse
U didn't understand what I said I have already reverted my to stock ROM and relocked the bootloader but even then message is coming device can't be trusted or may not work properly and I'm not even getting any updates not even April update and all friends got this I'm currently pure stock
Problem are:-
Message is still there
Updates r not coming
Hey all, does anyone have a full OTA image of NPG47I?
My phone is bootlooping and the bootloader is locked and OEM unlock was not enabled so I can't flash a factory image. I tried to sideload OTAs but I can not install over newer build. Is the OTA out there anywhere? Is it possible for someone to upload it, or do I have to wait for google to upload it?
Thanks in advance
pakifood said:
Hey all, does anyone have a full OTA image of NPG47I?
My phone is bootlooping and the bootloader is locked and OEM unlock was not enabled so I can't flash a factory image. I tried to sideload OTAs but I can not install over newer build. Is the OTA out there anywhere? Is it possible for someone to upload it, or do I have to wait for google to upload it?
Thanks in advance
Click to expand...
Click to collapse
I'm in the same boat with you. I think we have to wait for google to release new build OTA.
NPG47i build date is March 8th, 2017
We need new OTA pass March 8th 2017
pakifood said:
Hey all, does anyone have a full OTA image of NPG47I? My phone is bootlooping and the bootloader is locked and OEM unlock was not enabled so I can't flash a factory image. I tried to sideload OTAs but I can not install over newer build. Is the OTA out there anywhere? Is it possible for someone to upload it, or do I have to wait for google to upload it?
Click to expand...
Click to collapse
510jungleboy said:
I'm in the same boat with you. I think we have to wait for google to release new build OTA. NPG47i build date is March 8th, 2017. We need new OTA pass March 8th 2017
Click to expand...
Click to collapse
Have you both tried doing a factory reset?
pakifood said:
Hey all, does anyone have a full OTA image of NPG47I?
My phone is bootlooping and the bootloader is locked and OEM unlock was not enabled so I can't flash a factory image. I tried to sideload OTAs but I can not install over newer build. Is the OTA out there anywhere? Is it possible for someone to upload it, or do I have to wait for google to upload it?
Thanks in advance
Click to expand...
Click to collapse
v12xke said:
Have you both tried doing a factory reset?
Click to expand...
Click to collapse
Yes I have. Numerous time.
v12xke said:
Have you both tried doing a factory reset?
Click to expand...
Click to collapse
Yes, cleared cache and factory reset. Still bootlooping. :/
With a locked bootloader I'm not aware of anything more that can be done at this point. It will be 3 weeks until the May security update... and the bad part is that the new OTA may not work either.
510jungleboy said:
I'm in the same boat with you. I think we have to wait for google to release new build OTA.
NPG47i build date is March 8th, 2017
We need new OTA pass March 8th 2017
Click to expand...
Click to collapse
Seems like OTA upload is not far away. Also seems like many others are facing bootloop issues on 7.1.2 beta 2. https://productforums.google.com/forum/#!topic/nexus/oty0zlqLN1E
pakifood said:
Hey all, does anyone have a full OTA image of NPG47I?
My phone is bootlooping and the bootloader is locked and OEM unlock was not enabled so I can't flash a factory image. I tried to sideload OTAs but I can not install over newer build. Is the OTA out there anywhere? Is it possible for someone to upload it, or do I have to wait for google to upload it?
Thanks in advance
Click to expand...
Click to collapse
Why don't you unlock your bootloader?
Wow it's here. Flashed and rebooted, still in bootloop. RIP. https://android.googleapis.com/pack.../381836b75c8f534c45c95b15912272b72200ca1f.zip there's the zip if you want, lmk if it works for you. Side note, any idea how much out of warranty RMA costs? I called them and they said they can't tell me the price until after it's repaired...
DEVILOPS 007 said:
Why don't you unlock your bootloader?
Click to expand...
Click to collapse
How can I do that? I tried in adb and it says permission denied. I never enabled bootloader unlock in developer settings.
pakifood said:
How can I do that? I tried in adb and it says permission denied. I never enabled bootloader unlock in developer settings.
Click to expand...
Click to collapse
Plug it into your computer and make sure the drivers are installed especially the adb bootloader interface. Then go to your adb and fastboot directory and put your phone in bootloader mode. Then type fastboot devices and your devices serial should show up and then type fastboot oem unlock. Are you using Windows or a Unix based OS like Linux or Mac?
DEVILOPS 007 said:
Plug it into your computer and make sure the drivers are installed especially the adb bootloader interface. Then go to your adb and fastboot directory and put your phone in bootloader mode. Then type fastboot devices and your devices serial should show up and then type fastboot oem unlock. Are you using Windows or a Unix based OS like Linux or Mac?
Click to expand...
Click to collapse
In his first post OP already stated he never enabled OEM unlock in dev settings so there is no way to unlock via ADB/fastboot.
---------- Post added at 05:38 PM ---------- Previous post was at 05:27 PM ----------
pakifood said:
Seems like OTA upload is not far away. Also seems like many others are facing bootloop issues on 7.1.2 beta 2. https://productforums.google.com/forum/#!topic/nexus/oty0zlqLN1E
Click to expand...
Click to collapse
The BLOD phenomenon is completely independent of Android build. It is a hardware defect, usually the motherboard (bad memory, cracked solder connections, etc.) In your case, the replacement part costs upwards of 60% of the original cost of the phone. Time to move on.
v12xke said:
In his first post OP already stated he never enabled OEM unlock in dev settings so there is no way to unlock via ADB/fastboot.
---------- Post added at 05:38 PM ---------- Previous post was at 05:27 PM ----------
The BLOD phenomenon is completely independent of Android build. It is a hardware defect, usually the motherboard (bad memory, cracked solder connections, etc.) In your case, the replacement part costs upwards of 60% of the original cost of the phone. Time to move on.
Click to expand...
Click to collapse
Wow. RIP nexus. Guy at Huawei support told me he had no idea how much it would cost but said "he would guess $60 but idk cause I'm not technical. I think they're just gonna redownload the software." Not tryna pay 300 dollars to get this fixed. Thanks.