Related
Hi,
So quick summary of what happened. I went to make coffee, came back to desk and my N6P has been stuck in boot loop.
It was running the latest Android 7.1.1 build (NPF26F)
I can access fastboot and recovery fine. However, I can't flash anything from fastboot as the device wasn't unlocked.
I tried wiping data / factory & cache from fastboot and recovery with no difference in result.
I also can't seem to sideload anything as all the OTA's from google come back with 'Can't install this package (%Date of build%) over newer build.
The latest OTA i can find is: 7.1.1 NMF26F (angler-ota-nmf26f-61b4a915.zip)
I also tried the official 7.0 NBD91K (angler-ota-nbd91k-32c2eac8.zip) with the same result.
Is there a different OTA I can use or can I force it to sideload an older version or any other suggestions?
I really don't want to have to deal with my telco. I'll be without a phone for weeks if I have to :'(
I have a phone with the same problem. Haven't gotten an answer yet. I am starting to wonder if it's an issue with the build.
bkgovols said:
I have a phone with the same problem. Haven't gotten an answer yet. I am starting to wonder if it's an issue with the build.
Click to expand...
Click to collapse
When you say haven't gotten an answer yet.... you posted it somewhere? I bet an easy fix for google would be to release a newer full OTA... but unless they respond in a day, i'll be returning phone...
gunigugu said:
Hi,
So quick summary of what happened. I went to make coffee, came back to desk and my N6P has been stuck in boot loop.
It was running the latest Android 7.1.1 build (NPF26F)
I can access fastboot and recovery fine. However, I can't flash anything from fastboot as the device wasn't unlocked.
I tried wiping data / factory & cache from fastboot and recovery with no difference in result.
I also can't seem to sideload anything as all the OTA's from google come back with 'Can't install this package (%Date of build%) over newer build.
The latest OTA i can find is: 7.1.1 NMF26F (angler-ota-nmf26f-61b4a915.zip)
I also tried the official 7.0 NBD91K (angler-ota-nbd91k-32c2eac8.zip) with the same result.
Is there a different OTA I can use or can I force it to sideload an older version or any other suggestions?
I really don't want to have to deal with my telco. I'll be without a phone for weeks if I have to :'(
Click to expand...
Click to collapse
You can unlock bootloader if you have fast boot. The computer needs to recognise your phone. Then just follow the steps in the beginner's guide.
tropical cactus said:
You can unlock bootloader if you have fast boot. The computer needs to recognise your phone. Then just follow the steps in the beginner's guide.
Click to expand...
Click to collapse
No, unfortunately, you can no longer unlock nexus devices from just the bootloader. You need access to Android OS.
gunigugu said:
No, unfortunately, you can no longer unlock nexus devices from just the bootloader. You need access to Android OS.
Click to expand...
Click to collapse
Install Android SDK or find adb mini bundle. Download latest factory images from Google's website. Run this command to sideload the factory image. You DON'T need unlocked bootloader for this command.
HTML:
adb sideload yourFactoryImagesFile
gunigugu said:
Hi,
...I can access fastboot and recovery fine. However, I can't flash anything from fastboot as the device wasn't unlocked....
Click to expand...
Click to collapse
You never went into Developer Options and toggled the "allow OEM Unlock"? If not, you will not be able to unlock bootloader via fastboot.
And are you positive you did a proper "factory reset" from recovery? From stock, this should get you out of a boot loop. The naming convention Google used for DP2/Public Release was screwed up and I've seen others reporting the inability to flash OTA's but the solution was to flash the full Google image. As someone else suggested, until a new OTA hits with a newer (higher) number, you may be out of luck. Maybe someone with more experience can help with perhaps altering the OTA signature?
fapste said:
Install Android SDK or find adb mini bundle. Download latest factory images from Google's website. Run this command to sideload the factory image. You DON'T need unlocked bootloader for this command.
HTML:
adb sideload yourFactoryImagesFile
Click to expand...
Click to collapse
Unfortunately as mentioned in original post 'I also can't seem to sideload anything as all the OTA's from google come back with 'Can't install this package (%Date of build%) over newer build'
v12xke said:
You never went into Developer Options and toggled the "allow OEM Unlock"? If not, you will not be able to unlock bootloader via fastboot.
And are you positive you did a proper "factory reset" from recovery? From stock, this should get you out of a boot loop. The naming convention Google used for DP2/Public Release was screwed up and I've seen others reporting the inability to flash OTA's but the solution was to flash the full Google image. As someone else suggested, until a new OTA hits with a newer (higher) number, you may be out of luck. Maybe someone with more experience can help with perhaps altering the OTA signature?
Click to expand...
Click to collapse
Yup never did it :'(
Didn't think I needed to unlock / root my devices anymore since I can get all the functionality out of stock android these days. Though now I feel like I'm being punished for not unlocking it :'(
I'm positive I did a factory reset from recovery. I do believe flashing a full google image would fix the issue, but im unable to from fastboot as device is locked and sideload images appear to be older :'(
Really sorry to hear this, and I know being without the phone even for a day or two is inconvenient at best. Could be critical for your work or school. Most every bootloop I have encountered, I've been able to fix by re-flashing the kernel. Either stock or custom... like EX Kernel. Have you ever played with WugFresh's NRT? You can temp flash TWRP and maybe temp flash or flash the kernel? This probably won't work with a locked bootloader If you could just start the OS, you could toggle the OEM unlock. At a minimum, TWRP will give you a file manager, MTP file transfer, wiping and other tools. If you have time, it may be worth a try. Other than that, successfully altering the signature of the OTA may work, but I've not seen any work on this, but have never had to look. I'd keep searching for ppl having the difficulty of going from DP2 to Public Release (older/newer) and see if there was another solution other than flashing the full image, which obviously you can't do right now. Good luck, and let us know if you make any progress.
Edit : Read here for possible help. This may work in conjunction with getting TWRP installed via NRT.
gunigugu said:
Unfortunately as mentioned in original post 'I also can't seem to sideload anything as all the OTA's from google come back with 'Can't install this package (%Date of build%) over newer build'
Click to expand...
Click to collapse
How can flashing the latest factory images released on 6 December can give this error? Make sure you download the 6 December factory images
fapste said:
How can flashing the latest factory images released on 6 December can give this error? Make sure you download the 6 December factory images
Click to expand...
Click to collapse
Many ppl have had problems sideloading the OTA coming from DP2 to Public Release NPF26F->>NMF26F and not just the 6P. Because the Public release numerically is "older" the OTA will not flash. When unlocked, the solution was to flash the full Google image, rather than the OTA. Why in their infinite wisdom Google did this I have no idea. Options are very slim when your bootloader is locked and you are stuck in a boot loop. OP cannot flash a full image when the NMF26F OTA is parsed as being "older".
fapste said:
How can flashing the latest factory images released on 6 December can give this error? Make sure you download the 6 December factory images
Click to expand...
Click to collapse
I believe it's because the latest OTA on https://developers.google.com/android/ota is 7.1.1 (NMF26F) and my phone is already running 7.1.1 build (NPF26F).
v12xke said:
Many ppl have had sideloading OTA coming from DP2 to Public Release NPF26F->>NMF26F and not just the 6P. Because the Public release numerically is "older" the OTA will not flash. When unlocked, the solution was to flash the full Google image, rather than the OTA. Why in their infinite wisdom Google did this I have no idea. Options are very slim when your bootloader is locked and you are stuck in a boot loop. OP cannot flash a full image when the NMF26F OTA is parsed as being "older".
Click to expand...
Click to collapse
This guy gets it!!! Yeah, I've unlocked a lot of my older devices and am comfortable with 'messing' my devices, but I didn't with the 6p as the stock experience is great now. But now I feel like I'm being punished because my device is dead with no recourse for action. Unless google release a newer full OTA.
If you haven't given up yet and gone back to the carrier with the phone, try the NRT toolkit to temp flash TWRP, and then FORMAT each partition, then try to reflash OTA with TWRP. Under "Advanced Utilities".
v12xke said:
If you haven't given up yet and gone back to the carrier with the phone, try the NRT toolkit to temp flash TWRP, and then FORMAT each partition, then try to reflash OTA with TWRP. Under "Advanced Utilities".
Click to expand...
Click to collapse
This will work on a locked device? I'll give it a crack and report back.
v12xke said:
If you haven't given up yet and gone back to the carrier with the phone, try the NRT toolkit to temp flash TWRP, and then FORMAT each partition, then try to reflash OTA with TWRP. Under "Advanced Utilities".
Click to expand...
Click to collapse
Yeah failed :'( (remote: unlock device to use this command)
[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexu...talls-t3518311
try this clean install should work i encountered a problem like this too
boxguy1 said:
[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexu...talls-t3518311
try this clean install should work i encountered a problem like this too
Click to expand...
Click to collapse
Firstly your link is broken: It's http://forum.xda-developers.com/nexus-6p/general/guide-fool-noob-proof-to-clean-installs-t3518311
Secondly as I've mentioned a few times including the OP. The device is locked. You need access to Android OS to unlock. It can not be done just from bootloader. So this does not work, but thanks for posting the suggestion anyway.
Deleted
---------- Post added at 05:53 AM ---------- Previous post was at 05:34 AM ----------
gunigugu said:
Firstly your link is broken: It's http://forum.xda-developers.com/nexus-6p/general/guide-fool-noob-proof-to-clean-installs-t3518311
Secondly as I've mentioned a few times including the OP. The device is locked. You need access to Android OS to unlock. It can not be done just from bootloader. So this does not work, but thanks for posting the suggestion anyway.
Click to expand...
Click to collapse
Sorry I thought it would have worked you should wait until the January security patch as all the other users said best of luck
In short, phone is stuck in a bootloop for no reason that I would know.
Out of warranty, so that option isn't available.
I really just need to get the bootloader unlocked, but I can't access the main screen.
I can access the recovery and bootloader, but when I tried doing an ota update through recovery, (even with NUF26K) it kept failing.
I need to be able to flash a full factory image, which is why I need the bootloader unlocked.
Thank you!
matistight said:
In short, phone is stuck in a bootloop for no reason that I would know.
Out of warranty, so that option isn't available.
I really just need to get the bootloader unlocked, but I can't access the main screen.
I can access the recovery and bootloader, but when I tried doing an ota update through recovery, (even with NUF26K) it kept failing.
I need to be able to flash a full factory image, which is why I need the bootloader unlocked.
Thank you!
Click to expand...
Click to collapse
Hi... Did the bootloop came from nowhere or what were you doing when it happened?
What error do you get when you sideload the ota?
Tried formatting cache or factory reset?
Edit: You can't downgrade with a locked bootloader.
matistight said:
I can access the recovery and bootloader, but when I tried doing an ota update through recovery, (even with NUF26K) it kept failing.
Click to expand...
Click to collapse
You will not be able to unlock the bootloader without booting the OS and entering Dev Options to allow "OEM Unlocking". Now that the 7.1.2 beta is out, that OTA is worth giving a shot. I'd certainly try the suggestions above if the beta OTA fails. If a factory reset does not work, you may be able to fastboot format userdata and cache and try the OTA route again.
v12xke said:
You will not be able to unlock the bootloader without booting the OS and entering Dev Options to allow "OEM Unlocking". Now that the 7.1.2 beta is out, that OTA is worth giving a shot. I'd certainly try the suggestions above if the beta OTA fails. If a factory reset does not work, you may be able to fastboot format userdata and cache and try the OTA route again.
Click to expand...
Click to collapse
Completely gave up on this, but I will give you the error when I get home, it was somewhat contradicting.
I have a Oneplus X I am using now, but the screen size is killing my hands! Atleast I am not out a phone
Maybe there is a way to erase/corrupt the system and bootloader and ota with a 6.0.x? I didnt really like android N
matistight said:
Completely gave up on this, but I will give you the error when I get home, it was somewhat contradicting.
I have a Oneplus X I am using now, but the screen size is killing my hands! Atleast I am not out a phone
Maybe there is a way to erase/corrupt the system and bootloader and ota with a 6.0.x? I didnt really like android N
Click to expand...
Click to collapse
If you erase or corrupt the bootloader then the phone is hard bricked (if it already isn't). I think you need an unlocked bootloader to do that anyways. Any flashing or erasing command in fastboot is going to need an unlocked bootloader. Even if you did somehow manage to delete the bootloader, without the phone being unlocked you can't flash a new one = hard brick.
If your phone is BL locked, you can't access Android, recovery doesn't help, you're mostly out of luck. Some people have said that using MSkips toolkit recovered their phones, but others had no such luck. There's a lot of people in the same boat as you. Others have tried calling Google about the issue despite their warranty status. Your phone is locked and a stock OTA took it out, from the sounds of it. Maybe they'll be willing to work with you. The worst they can do is say no, can't hurt to try. Good luck!
Why do you want to downgrade?
rchtk said:
Why do you want to downgrade?
Click to expand...
Click to collapse
Never really like 7.x and it has been the only OS that has bricked my phone without being rooted.
Unfortunately you can neither use an OTA to downgrade nor flash a factory image without BL unlocked.
And I'm not sure that would help either. Your device corrupted itself for a reason and that might be the flash failing (which the Nougat update exhibited, but Nougat isn't the root cause probably). You could rather wait for a higher OTA and hope.
Any recovery log to post?
How old is the phone? 1 year?
I have looked through the entire internet and i cant find one for that specific one, not an EU on atleast
(reteu.en.Eu retgb)
and i don't wanna screw up my phone.
thanks
XxperexX said:
I have looked through the entire internet and i cant find one for that specific one, not an EU on atleast
(reteu.en.Eu retgb)
and i don't wanna screw up my phone.
thanks
Click to expand...
Click to collapse
We don't have it for any variant... Don't know if we ever will, never been leaked and the sources for them are questionable if we will ever get any more factory images at all.
What is the problem?
acejavelin said:
We don't have it for any variant... Don't know if we ever will, never been leaked and the sources for them are questionable if we will ever get any more factory images at all.
What is the problem?
Click to expand...
Click to collapse
I need to restore to stock recovery and relock the bootloader, but i heard i cant do that if i use an image older than mine
XxperexX said:
I need to restore to stock recovery and relock the bootloader, but i heard i cant do that if i use an image older than mine
Click to expand...
Click to collapse
Why do you want relock BL? It can help with... nothing.
You can flash the newest version RetEu 6.0.1 with oem_lock commands.
I suggest rather:
Flash the first 6.0.1 reteu 24...58 without locking
If everything will be ok:
Flash the last 6.0.1 24...58-5 with locking BL.
After it you should get one or two OTAs.
Remember: bootloop with locked BL - only authorized service can help.
dzidexx said:
Why do you want relock BL? It can help with... nothing.
You can flash the newest version RetEu 6.0.1 with oem_lock commands.
I suggest rather:
Flash the first 6.0.1 reteu 24...58 without locking
If everything will be ok:
Flash the last 6.0.1 24...58-5 with locking BL.
After it you should get one or two OTAs.
Remember: bootloop with locked BL - only authorized service can help.
Click to expand...
Click to collapse
Oh, probably wont do that then.
Another question, can i download the android 7 ota uodate when i get it still? With an unlocked bootloader saying "Offical" and twrp?
So far ota update is only for 24...58-13.
With twrp you can't install any ota update.
Unlocked BL doesn't matter for OTAs.
dzidexx said:
So far ota update is only for 24...58-13.
With twrp you can't install any ota update.
Unlocked BL doesn't matter for OTAs.
Click to expand...
Click to collapse
Exactly, i need to get rid off twrp, but i can only do that if i flash a stock recovery, which i cant
It might be worth trying this older firmware whose name suggests that it is reteu for UK and FR, and seeing if newer OTAs show up:
https://firmware.center/firmware/Mo..._MPH24.49-18_cid7_subsidy-DEFAULT_CFC.xml.zip
More available here, but none of them seem like they're for UK phones:
https://firmware.center/firmware/Motorola/Moto X Style/Stock/XT1572/
If your bootloader is unlocked and you're trying to lock it, you could try flashing it while keeping the bootloader unlocked, and then flash it again as part of the flashboot oem lock begin -> flashboot oem lock process. (From what I've seen, the device is fine flashing older firmware with an unlocked bootloader, but not with a locked one.)
Has anybody with an unlocked bootloader completed the recent B353 system update? My M3 has downloaded the update (even though I have automatic updates turned off). It says it's going to do the update on the next reboot. I assume that the update will fail, because I have an unlocked bootloader. I would prefer to stop the update if possible.
Has anybody done this update manually? Did you run into any problems with getting root back after the update?
woody1 said:
Has anybody with an unlocked bootloader completed the recent B353 system update? My M3 has downloaded the update (even though I have automatic updates turned off). It says it's going to do the update on the next reboot. I assume that the update will fail, because I have an unlocked bootloader. I would prefer to stop the update if possible.
Has anybody done this update manually? Did you run into any problems with getting root back after the update?
Click to expand...
Click to collapse
My M3 is unlocked. The first attempt at the OTA update failed for reasons I don't know. But I initiated the download again and the second time it installed. I had to re-root afterward, but the update *did not* re-lock the bootloader, thankfully.
[Edit] My partition setup is probably different from yours. Recovery has the original Huawei recovery on it; I put TWRP onto recovery2. That's probably the only reason the OTA was able to perform the update.
CCarson said:
My M3 is unlocked. The first attempt at the OTA update failed for reasons I don't know. But I initiated the download again and the second time it installed. I had to re-root afterward, but the update *did not* re-lock the bootloader, thankfully.
[Edit] My partition setup is probably different from yours. Recovery has the original Huawei recovery on it; I put TWRP onto recovery2. That's probably the only reason the OTA was able to perform the update.
Click to expand...
Click to collapse
That's really good to know. I had the Hauwei recovery on recovery2 originally, but I think I forgot to put it there the last time I updated. That would be great if I didn't have to unlock the bootloader to do an upgrade!
woody1 said:
That's really good to know. I had the Hauwei recovery on recovery2 originally, but I think I forgot to put it there the last time I updated. That would be great if I didn't have to unlock the bootloader to do an upgrade!
Click to expand...
Click to collapse
Not sure, but I think the recovery and recovery2 recoveries are different. I think the Huawei recovery2 is an emergency restore utility, which I opted to overwrite with TWRP. (It's the one you can run using vol-up at the bootloader unlocked warning page.)
The normal Huawei recovery is the usual sort of vendor recovery that's booted into to do the auto-updates.
CCarson said:
Not sure, but I think the recovery and recovery2 recoveries are different. I think the Huawei recovery2 is an emergency restore utility, which I opted to overwrite with TWRP. (It's the one you can run using vol-up at the bootloader unlocked warning page.)
The normal Huawei recovery is the usual sort of vendor recovery that's booted into to do the auto-updates.
Click to expand...
Click to collapse
I think that's right. The 2nd recovery is called erecovery and it's not very useful. I think that's a good practice to put TWRP there.
I can't get the OTA update to work. That's probably because I have TWRP in the first recovery partition and the OTA is expecting to find the stock recovery there. When the OTA runs, it boots into TWRP and seems to install, but nothing happens. I wonder if there's a way I can put the stock recovery back into the first recovery partition and then run the OTA update?
Has anybody gotten this update through Firmware Finder? It doesn't show up for me.
I want to go back to stock, but how can i flash the latest stock rom?
i use the U version
Following this post, you will be able to go back to stock B32, not the latest B35, but almost.
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
Igorperrotta said:
I want to go back to stock, but how can i flash the latest stock rom?
i use the U version
Click to expand...
Click to collapse
llaalways said:
Following this post, you will be able to go back to stock B32, not the latest B35, but almost.
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
Click to expand...
Click to collapse
But the b35 is impossible to get back?
The edl method allow you to get back to B32 with everything from stock, such as gpt, recovery, modem, boot, system.
I have not tried to update from B32 to B35, but you may able to do it by OTA update.
There are other ways to flash it to B35, but you may need custom recovery such as twrp.
Igorperrotta said:
But the b35 is impossible to get back?
Click to expand...
Click to collapse
llaalways said:
The edl method allow you to get back to B32 with everything from stock, such as gpt, recovery, modem, boot, system.
I have not tried to update from B32 to B35, but you may able to do it by OTA update.
There are other ways to flash it to B35, but you may need custom recovery such as twrp.
Click to expand...
Click to collapse
Ota is dead, ZTE shutted It down
I used the twrp b35 but it doesn't have fastboot working, so I can't relock bootloader to sell the phone
I think it is OK to get back to B32 and relock the bootloader for selling the phone.
you do not really need B35.
Igorperrotta said:
Ota is dead, ZTE shutted It down
I used the twrp b35 but it doesn't have fastboot working, so I can't relock bootloader to sell the phone
Click to expand...
Click to collapse
llaalways said:
I think it is OK to get back to B32 and relock the bootloader for selling the phone.
you do not really need B35.
Click to expand...
Click to collapse
I wanted to get it to the lastest update because the guy I was selling it to had the phone and would know that I modded it
Lol. I spent all weekend trying to figure out how to get back to B35 locked. Decided that maybe I was happy with the unofficial Oreo builds after all.
Since there are no more otas, flashing stock and locking the bl is only hurting the new owner who will have to go through all that again if they want updates.
Pretty sure there is a modded b35 stack around here somewhere... maybe nFound's thread.
I bet the b32 stack also works just fine on b35 but no promises.
tried flash stock recovery from twrp. not yet found way to get fastboot back from twrp.
Wait, zte is back now, so ota maybe available soon.
espressoguy said:
Lol. I spent all weekend trying to figure out how to get back to B35 locked. Decided that maybe I was happy with the unofficial Oreo builds after all.
Click to expand...
Click to collapse
I did the same thing
llaalways said:
Wait, zte is back now, so ota maybe available soon.
Click to expand...
Click to collapse
Is it back???
https://community.zteusa.com is back. but no ota yet.
Igorperrotta said:
Is it back???
Click to expand...
Click to collapse
llaalways said:
Wait, zte is back now, so ota maybe available soon.
Click to expand...
Click to collapse
this should do the trick
getdroidtips.com/b35-zte-axon-7-december/
and since this is my first post, im unable to do the real hyperlink, so copy into browser and go
espressoguy said:
Lol. I spent all weekend trying to figure out how to get back to B35 locked. Decided that maybe I was happy with the unofficial Oreo builds after all.
Click to expand...
Click to collapse
Try using B03 from ztedevices.com it's for the G variation, but if you install B20 OR B35 afterwards you will get all your functions back, I was stuck with no phone functions with my U model on stock B01 ROM. Rather than use edl or tulip tool or Axon 7 toolkit just flash B03 in standard recovery mode then flash B20 both from SD Card, trust me it works for the U even though B03 is intended for the G, my U on the B01 ROM was identifing itself as a G and I had no phone functions at all, I used this method as I don't have access to a PC just Mac so I had to rely on SD Card updates to get it going, try this method. I had B35 when I bought it, I must admit it's a good build especially with the Hiys call blocker as a system app. Use SD Card upgrades and then you can sell it and upgrade to the Axon 10 pro