Database Users

Nexus 6P stuck on boot screen

Hi guys,
Right so I really need some help right now,
My nexus 6p is enrolled with the beta program but I am unsure which particular version of nougat it is on...
So I was sending a snapchat last night, and the phone randomly crashed and restarted. It then did it again when I attempted to do the same again. It kept on repeating do to this till the point where it wont boot anymore, it gets to the google logo and crashes or occasionally gets to the part of the boot with the shapes and crashes. So its stuck in some kind of bootloop?
So the phone is enrolled in the Beta, but I have not done anything else to it such as rooting etc.
This is a really stressful situation for me right now, my phone is essential for me right now, as a student from the UK studying abroad in Canada, I cant do any exchanges or afford to buy a new phone.
I was wondering if someone could help me fix this, I really dont know anything about Android when it comes to this kind of thing, and if possible I really don't want to void the warranty.
A guide on what to do would be really appreciated, keeping in mind Im not experienced in doing this kind of thing on androids.
Thanks,
Ben

Can you boot into the bootloader/fastboot mode?

benhawley2711 said:
Hi guys,
Right so I really need some help right now,
My nexus 6p is enrolled with the beta program but I am unsure which particular version of nougat it is on...
So I was sending a snapchat last night, and the phone randomly crashed and restarted. It then did it again when I attempted to do the same again. It kept on repeating do to this till the point where it wont boot anymore, it gets to the google logo and crashes or occasionally gets to the part of the boot with the shapes and crashes. So its stuck in some kind of bootloop?
So the phone is enrolled in the Beta, but I have not done anything else to it such as rooting etc.
This is a really stressful situation for me right now, my phone is essential for me right now, as a student from the UK studying abroad in Canada, I cant do any exchanges or afford to buy a new phone.
I was wondering if someone could help me fix this, I really dont know anything about Android when it comes to this kind of thing, and if possible I really don't want to void the warranty.
A guide on what to do would be really appreciated, keeping in mind Im not experienced in doing this kind of thing on androids.
Thanks,
Ben
Click to expand...
Click to collapse
i have the same issue, i have tried using toolkits and even using fastboot commands and the phone just keeps getting stuck on the google logo screen. at this point i think i might have to get a replacement. unless some can offer a solution

Same issue
I have exactly the same issue. I am on Angler 7.1.1 Beta/NPF10C. Since the OTA came out everything was fine, until yesterday while trying to send a picture on Hangouts the phone froze and rebooted, and rebooted and rebooted. The bootloader is locked and no USB debugging enabled. So far I tried:
- wipe data/factory reset through recovery - first try, the phone reset and let me set it up, but then froze after 5 minutes and kept rebooting; after that any factory reset just get's stuck at Google logo at boot
- tried to adb sideload rescue OTA - previous build NBD90X starts verification and fails at 50% with the error: can't flash older over newer (duh!); and the ota build npf10c can't be read. I tried on Mac and Windows. No matter what I do adb can't read zip file. Also tried updated sdk tools and everything, no luck.
Read on Google forums that there is a chance of hardware issue and the phone must be returned for exchange if still under warranty.
Update: I was able to sideload rescue OTA on Linux, but the phone is still in bootloop. Only showing Google logo and reboots. I'll wait till next DP2 comes out and I will try to sideload it and see if it fixes the issue.

redduc900 said:
Can you boot into the bootloader/fastboot mode?
Click to expand...
Click to collapse
Yes I can, any suggestions as to what I can do?(sorry im a noob, but the bootloader is the power button and volume down menus right? haha)
Is there any way I can get my data off the phone?

.
So I followed these instructions for the rescue OTA (I cant post the links because im new to the site)
You can find it by going to the google help forums
Well I Got to Step 9 and it didnt work and it says a warranty or repair is the only recourse.
Is there no other way of fixing this? As I said before, a warranty replacement is not possible for me as I'm in the wrong country

benhawley2711 said:
Yes I can, any suggestions as to what I can do?(sorry im a noob, but the bootloader is the power button and volume down menus right? haha)
Is there any way I can get my data off the phone?
Click to expand...
Click to collapse
I don't think there is a way, since the phone is encrypted, boot-loader locked and oem unlocking is disabled. I think that is the whole purpose of having device secured, so none can get files from your phone.
---------- Post added at 01:29 AM ---------- Previous post was at 01:26 AM ----------
benhawley2711 said:
So I followed these instructions for the rescue OTA (I cant post the links because im new to the site)
You can find it by going to the google help forums
Well I Got to Step 9 and it didnt work and it says a warranty or repair is the only recourse.
Is there no other way of fixing this? As I said before, a warranty replacement is not possible for me as I'm in the wrong country
Click to expand...
Click to collapse
Looks like your recovery is bad and that is when warranty suppose to be used. However, even if there is warranty, Huawei website states that they won't cover improper testing of the devices, which I think falls under beta testing category.

denys2000 said:
I don't think there is a way, since the phone is encrypted, boot-loader locked and oem unlocking is disabled. I think that is the whole purpose of having device secured, so none can get files from your phone.
---------- Post added at 01:29 AM ---------- Previous post was at 01:26 AM ----------
Looks like your recovery is bad and that is when warranty suppose to be used. However, even if there is warranty, Huawei website states that they won't cover improper testing of the devices, which I think falls under beta testing category.
Click to expand...
Click to collapse
At this point, I'm not too bothered about my data, because all my photos have backed up to google photos.
Should I just attempt a factory restore? I know someone above said their phone just froze after 5 mins, but I suppose I could try and unenroll from the beta in that time and hopefully take me back to a stable release without the bug.
- I'm not sure if that will work though :/

benhawley2711 said:
At this point, I'm not too bothered about my data, because all my photos have backed up to google photos.
Should I just attempt a factory restore? I know someone above said their phone just froze after 5 mins, but I suppose I could try and unenroll from the beta in that time and hopefully take me back to a stable release without the bug.
- I'm not sure if that will work though :/
Click to expand...
Click to collapse
If you have no worries about losing data then you should try a factory reset, after all it might help. IMO you should definitely unenroll from beta at this point.

denys2000 said:
If you have no worries about losing data then you should try a factory reset, after all it might help. IMO you should definitely unenroll from beta at this point.
Click to expand...
Click to collapse
Yeah, so it wont let me go into recovery mode just bootloops, safe to say its pretty f***ed.
Suppose trying to claim warranty is all I can do, but can't do that for two months.
At this point, I'm gonna have to admit defeat and buy a new phone until I can claim the warranty back in the UK when I return.

benhawley2711 said:
Yeah, so it wont let me go into recovery mode just bootloops, safe to say its pretty f***ed.
Suppose trying to claim warranty is all I can do, but can't do that for two months.
At this point, I'm gonna have to admit defeat and buy a new phone until I can claim the warranty back in the UK when I return.
Click to expand...
Click to collapse
Good luck with the warranty. Unfortunately, mine has ended and I am currently using my girlfriend's old iphone 5s with a tiny tiny tiny screen

I used adb and sidecar and all the stuff mentioned by others. it says 100% and i rebooted my device and still google logo occuring and its not fixed. Any other option that i can try now?

[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

KKPGAME said:
I used adb and sidecar and all the stuff mentioned by others. it says 100% and i rebooted my device and still google logo occuring and its not fixed. Any other option that i can try now?
Click to expand...
Click to collapse
use these commands in bootloader.
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384

Nexus 6P BOOTLOOP after using Facebook

1 hour ago, I was checking Facebook, and a moment later, my phone started to restart... After a few moments, I realized that my phone was in bootloop. I tried booting into recovery, but It started a bootloop again. Flashed TWRP, nothing happens, still bootloop. Flashed vendor, system, boot, cache, recovery, radio, bootloader from lastest factory image. I have very important data on my phone, so the last thing I want to do is to do a factory reset. But I still hope that I can somehow get the userdata partition from bootloader or somehow make it boot. Can you help me? The only thing I can open right now is bootloader.

I'm having an exactly the same problem with you.
The only difference is that I didn't use Facebook.
I dared to lose my every data so I formatted userdata partition of my phone and flashed stock image, but it didn't fix mine.
I failed at figuring out the solution yet, but there's still one hope.
When I contacted with huawei, they said there's an upcoming update, and it will fix bricked phones.
I don't know if it will work, but considering you had your bootloader unlocked and can access it, and you have some important datas that you don't wanna lose, I recommend you keep your phone until the update gets released, then manually flash it without wiping your user data.
Given our phone's symptom is exactly the same and you tried similar methods I've tried, this is the best way I think you can try.
Good luck. You're in the same boat with me.

frostydawn said:
I'm having an exactly the same problem with you.
The only difference is that I didn't use Facebook.
I dared to lose my every data so I formatted every partition of my phone and flashed stock image, but it didn't fix mine.
I failed at figuring out the solution yet, but there's still one hope.
When I contacted with huawei, they said there's an upcoming update, and it will fix bricked phones.
I don't know if it will work, but considering you had your bootloader unlocked and can access it, and you have some important datas that you don't wanna lose, I recommend you keep your phone until the update gets released, then manually flash it without wiping your user data.
Given our phone's symptom is exactly the same and you tried similar methods I've tried, this is the best way I think you can try.
Good luck. You're in the same boat with me.
Click to expand...
Click to collapse
Yes, but we can wait for this update for months.. Also, when you flash a factory image, you lose you data (correct me if I'm wrong). So, it doesn't matter to me, if I try to format user data, or wait for the update. Hm...

fftorettol said:
Yes, but we can wait for this update for months.. Also, when you flash a factory image, you lose you data (correct me if I'm wrong). So, it doesn't matter to me, if I try to format user data, or wait for the update. Hm...
Click to expand...
Click to collapse
Well, android 7.1.2 beta for nexus 5x, pixel, or etc was released a few days ago, and for nexus 6p, it'll be released soon.
This is just my imagination, but maybe they're taking some times fixing boot loop so the release for 6p is getting late.
Also, you can flash factory images without user data lose by manually flashing it using fastboot commands.
The released image will contain some .img files, then you can extract it and then only flash required files without formatting userdata partition.
Don't use flash-all.bat, and use fastboot commands to selectively install image files except for userdata.

frostydawn said:
Well, android 7.1.2 beta for nexus 5x, pixel, or etc has been released a few days ago, and for nexus 6p, it'll be released soon.
This is just my imagination, but maybe they're taking some times fixing boot loop so the release for 6p is getting late.
Also, you can flash factory images without user data lose by manually flashing it using fastboot commands.
The released image will contain some .img files, then you can extract it and then only flash required files without formatting userdata partition.
Don't use flash-all.bat, and use fastboot commands to selectively install image files except for userdata.
Click to expand...
Click to collapse
Right! I've just got an idea to try older factory image versions for Nexus 6P... Mabye I get it working . I will let you now

I'm on the same boat as both of you guys. I tried installing TWRP but it continues to bootloop.
I have some important data I didn't get a chance to backup. and would not want to send it back/factory reformat.
Here's my thread:
https://forum.xda-developers.com/nexus-6p/help/nexus-6p-bootloop-to-recover-files-t3551455
Please keep us updated.

stillwind said:
I'm on the same boat as both of you guys. I tried installing TWRP but it continues to bootloop.
I have some important data I didn't get a chance to backup. and would not want to send it back/factory reformat.
Here's my thread:
https://forum.xda-developers.com/nexus-6p/help/nexus-6p-bootloop-to-recover-files-t3551455
Please keep us updated.
Click to expand...
Click to collapse
frostydawn said:
Well, android 7.1.2 beta for nexus 5x, pixel, or etc was released a few days ago, and for nexus 6p, it'll be released soon.
This is just my imagination, but maybe they're taking some times fixing boot loop so the release for 6p is getting late.
Also, you can flash factory images without user data lose by manually flashing it using fastboot commands.
The released image will contain some .img files, then you can extract it and then only flash required files without formatting userdata partition.
Don't use flash-all.bat, and use fastboot commands to selectively install image files except for userdata.
Click to expand...
Click to collapse
Guys, did you manage to fix it? I was doing some research, talking to some persons, and they said that it is probably a hardware problem. So, I went to the nearest Huawai servis, and they told me, that if the problem is really on hardware, it will cost me around 340€ (363 dollars) to replace motherboard... I can't afford that much... Its is almost a price of a new phone. I hope you came up with some better solutions.

fftorettol said:
Guys, did you manage to fix it? I was doing some research, talking to some persons, and they said that it is probably a hardware problem. So, I went to the nearest Huawai servis, and they told me, that if the problem is really on hardware, it will cost me around 340€ (363 dollars) to replace motherboard... I can't afford that much... Its is almost a price of a new phone. I hope you came up with some better solutions.
Click to expand...
Click to collapse
For now, I failed.
New 7.1.1 minor build update didn't fix my phone.
And google said they can't assure there will be update that will fix my phone.
I'm waiting for 7.1.2 beta, and if that doesn't work, well.. I don't know.
Maybe I should await 7.1.2 official, or.. just give up everything.
My hope is getting faded, and yeah.. for now, I can do nothing but wait for update.
Actually, I don't think those updates will work.
I'm just giving it a last chance, since repair service at here also costs about 350$, and if I fail, I should keep using Nexus 5.
Ah... It didn't took 2 weeks for my phone to be bricked after I bought this phone.
I really want to get this phone back, but the hope is too faint.

frostydawn said:
For now, I failed.
New 7.1.1 minor build update didn't fix my phone.
And google said they can't assure there will be update that will fix my phone.
I'm waiting for 7.1.2 beta, and if that doesn't work, well.. I don't know.
Maybe I should await 7.1.2 official, or.. just give up everything.
My hope is getting faded, and yeah.. for now, I can do nothing but wait for update.
Actually, I don't think those updates will work.
I'm just giving it a last chance, since repair service at here also costs about 350$, and if I fail, I should keep using Nexus 5.
Ah... It didn't took 2 weeks after I bought this phone.
I really want to get this phone back, but the hope is too faint.
Click to expand...
Click to collapse
Exactly... I was thinking... What if we lock the bootloader and send the phone to repair service with warranty papers... Do you think that can actually work out? Can they see that the phone was rooted, if we lock the bootloader with ADB Shell?

fftorettol said:
Exactly... I was thinking... What if we lock the bootloader and send the phone to repair service with warranty papers... Do you think that can actually work out? Can they see that the phone was rooted, if we lock the bootloader with ADB Shell?
Click to expand...
Click to collapse
I live in South Korea and in my country, they provide repair by post service for devices in the warranty period.
For me, my warranty is expired, so I had to bring it to the service center myself.
I've locked the bootloader and brought it the center.
They didn't check if it was ever unlocked or rooted.
The engineer only tried rebooting my phone several times, and said he should replace the motherboard. And they said they couldn't fix it for free because the warranty is expired.
I don't know how Huawei in your country will handle it, but I think if you flash the stock image and lock your phone, maybe they won't see that was ever rooted.
But I also don't know if they will provide free repair.

No luck on my end. I tried everything... I've been flashing and repairing problems like these since the nexus one but I'm totally stumped. Lucky/Unlucky for me I've only had the device for 3 months so I have an RMA ready since it is under warranty.
Most importantly tho is that I want to recover the files on the device which will not happen if I take it to the repair center as they reflash all the devices before proceeding to fix it.
I tried getting TWRP but the device reboots back into the boot as soon as I select recovery.
Also tried flashing everything but user data using flashboot and the nexus 6 .img files but still in the same situation.
I just wished they would've at least added a microsd option so I could at least have some of my files back...
I don't think I will ever get a phone without microsd option again or root and unlock bootloader on every device I get. This was the first phone I decided not to mess around with since everyone kept telling me to enjoy the stock experience....
Worse experience to date with android.

Well I gave up trying to fix it by software, and found another solution.
My warranty is expired, so it wasn't cost-efficient to bring my phone to official service center.
Now I bought a display-broken phone at about 60 dollars.
Gonna bring it to an engineer and replace my phone's motherboard with its intact one.

frostydawn said:
Now I bought a display-broken phone at about 60 dollars.
Click to expand...
Click to collapse
That's a great price. Is it the H1512 (International) and where did you purchase? Haenguneul bileoyo.

v12xke said:
That's a great price. Is it the H1512 (International) and where did you purchase? Haenguneul bileoyo.
Click to expand...
Click to collapse
It seems like you're Korean like me.
I bought it from Naver Cafe Google Reference Nexus Forum's market.
And yeah. It's H1512.

No, i'm not Korean but I spent a couple of years working in Okpo and Ulsan on several projects. There is a guy from KL in another thread looking for an H1512 motherboard. I'll pass your info on to him. Thanks.

v12xke said:
No, i'm not Korean but I spent a couple of years working in Okpo and Ulsan on several projects. There is a guy from KL in another thread looking for an H1512 motherboard. I'll pass your info on to him. Thanks.
Click to expand...
Click to collapse
Well, then tell him this too.
Naver Cafe 'Joonggonara'
This is one of the largest market for used stuffs.

frostydawn said:
Well, then tell him this too.
Naver Cafe 'Joonggonara'
This is one of the largest market for used stuffs.
Click to expand...
Click to collapse
Link Product

VN_Optimus said:
Link Product
Click to expand...
Click to collapse
It was a one-off purchase of a broken phone on a Korean market equivalent of Craigslist. You'll have to dig around and find one locally... and be lucky, too.

I just had reboots today for the first lasting about 20 minutes. I was able to get into Recovery and clear the cache and then shut down the phone. Upon restart it looped a few times and then fully booted (thankfully). I have placed the latest firmware in the phone in the hope that if this happens again I can flash the firmware and access the phone.
I hope this helps a bit.
I am rooted and running N2G47H.
Doc

DocEsq said:
I just had reboots today for the first lasting about 20 minutes. I was able to get into Recovery and clear the cache and then shut down the phone. Upon restart it looped a few times and then fully booted (thankfully). I have placed the latest firmware in the phone in the hope that if this happens again I can flash the firmware and access the phone.
I hope this helps a bit.
I am rooted and running N2G47H.
Doc
Click to expand...
Click to collapse
Hopefully it will but realistically this could be the beginning of the end for your phone given the 6P history with the boot loop of death. Presumably your phone is out of warranty?

Unusable A2017G

So i have this A2017G owned by a cousin of mine. He had never tempered with anything except updating OTAs from the settings app. Meaning Stock everything and BL locked. Now, all of a sudden his device lags a lot (after the N-B06 update). When booting the device the boot animation lags like crazy. And it almost never gets past the boot animation (always restarts at Axon 7). The times it does reach past the boot screen, the device hangs after a minute or so and restarts.
Things that i have tried:
# Factory resetting through stock recovery.
# Downloading update.zips from ZTE and trying SD Card update trough stock recovery. Which always fails saying Signature verification failed.
# Booted to factory test mode and tried adb devices on cmd. Nothing comes up as there is no new device on the device manager. Also no sound.
# Booted to EDL mode and flashed N-B06 from this post: https://forum.xda-developers.com/axon-7/how-to/guide-ztea2017v2-0-0b08-t3658636
Nothing helped. Same old lags. And of course, the device is unusable.
What to do? Suggestions?

nsabir said:
So i have this A2017G owned by a cousin of mine. He had never tempered with anything except updating OTAs from the settings app. Meaning Stock everything and BL locked. Now, all of a sudden his device lags a lot (after the N-B06 update). When booting the device the boot animation lags like crazy. And it almost never gets past the boot animation (always restarts at Axon 7). The times it does reach past the boot screen, the device hangs after a minute or so and restarts.
Things that i have tried:
# Factory resetting through stock recovery.
# Downloading update.zips from ZTE and trying SD Card update trough stock recovery. Which always fails saying Signature verification failed.
# Booted to factory test mode and tried adb devices on cmd. Nothing comes up as there is no new device on the device manager. Also no sound.
# Booted to EDL mode and flashed N-B06 from this post: https://forum.xda-developers.com/axon-7/how-to/guide-ztea2017v2-0-0b08-t3658636
Nothing helped. Same old lags. And of course, the device is unusable.
What to do? Suggestions?
Click to expand...
Click to collapse
Get a new phone. Unfortunately I think it's some hardware that is broken. But in case it's not try to flash b05 instead?

I don't see anything else you could do since adb doesn't seems to work. I'd just RMA it with the warranty still being in effect. And if it was purchased trough amazon you'll probably just get a new one ! (that's what happened to me last time).

nsabir said:
So i have this A2017G owned by a cousin of mine. He had never tempered with anything except updating OTAs from the settings app. Meaning Stock everything and BL locked. Now, all of a sudden his device lags a lot (after the N-B06 update). When booting the device the boot animation lags like crazy. And it almost never gets past the boot animation (always restarts at Axon 7). The times it does reach past the boot screen, the device hangs after a minute or so and restarts.
Things that i have tried:
# Factory resetting through stock recovery.
# Downloading update.zips from ZTE and trying SD Card update trough stock recovery. Which always fails saying Signature verification failed.
# Booted to factory test mode and tried adb devices on cmd. Nothing comes up as there is no new device on the device manager. Also no sound.
# Booted to EDL mode and flashed N-B06 from this post: https://forum.xda-developers.com/axon-7/how-to/guide-ztea2017v2-0-0b08-t3658636
Nothing helped. Same old lags. And of course, the device is unusable.
What to do? Suggestions?
Click to expand...
Click to collapse
Did you try downgrading through EDL? I'll post the link to MM B10 for you to install through EDL, see if that helps. I seriously doubt that it's a hardware issue since it would not even boot if that was the case (take the Nexus 6P and 5X as an example: big cores busted and the phones wouldn't get past the boot logo).
Don't unlock the bootloader if you can't fix it, it'd make matters worse if LOS-based ROMs didn't work.
Edit: Here are a couple of links for B10 from 4pda. should be the same file:
https://drive.google.com/file/d/0Bynn_Z9_tfeOZWZmN1o2U09pWVU/view
https://mega.nz/#!ZhwR1BAD!PuIWa5Vivk3DxZ1Dgk-wAoITxiKmBiR-j1U8wZZidTw

Choose an username... said:
Did you try downgrading through EDL? I'll post the link to MM B10 for you to install through EDL, see if that helps. I seriously doubt that it's a hardware issue since it would not even boot if that was the case (take the Nexus 6P and 5X as an example: big cores busted and the phones wouldn't get past the boot logo).
Don't unlock the bootloader if you can't fix it, it'd make matters worse if LOS-based ROMs didn't work.
Edit: Here are a couple of links for B10 from 4pda. should be the same file:
https://drive.google.com/file/d/0Bynn_Z9_tfeOZWZmN1o2U09pWVU/view
https://mega.nz/#!ZhwR1BAD!PuIWa5Vivk3DxZ1Dgk-wAoITxiKmBiR-j1U8wZZidTw
Click to expand...
Click to collapse
I have tried this EDL package as well. Most of the time it says can not found programmer file. Only once it said can not find hello packet, reset status. That also ended up in error.
The N-B06 EDL package flashes fine. But the problem still persists.
I have also tried replacing N-B06 recovery.img with TWRP recovery.img and flashed it. But that just bricks the recovery.
Currently the 2 EDL packages i know are these two. N-B06 and MM-B10 for the G. The N one works fine while the MM one doesn't. Do u have any other EDL packages?
I too think it's a software problem since he has never dropped the phone and only used it for 2 months.

nsabir said:
I have tried this EDL package as well. Most of the time it says can not found programmer file. Only once it said can not find hello packet, reset status. That also ended up in error.
The N-B06 EDL package flashes fine. But the problem still persists.
I have also tried replacing N-B06 recovery.img with TWRP recovery.img and flashed it. But that just bricks the recovery.
Currently the 2 EDL packages i know are these two. N-B06 and MM-B10 for the G. The N one works fine while the MM one doesn't. Do u have any other EDL packages?
I too think it's a software problem since he has never dropped the phone and only used it for 2 months.
Click to expand...
Click to collapse
I think something is wrong with the hardware. I had a similar problem as u with my last phone a honor 8, it frozed up and it was nothing I couldnt do other than go back to the store with it. I got a new one.

nsabir said:
I have tried this EDL package as well. Most of the time it says can not found programmer file. Only once it said can not find hello packet, reset status. That also ended up in error.
The N-B06 EDL package flashes fine. But the problem still persists.
I have also tried replacing N-B06 recovery.img with TWRP recovery.img and flashed it. But that just bricks the recovery.
Currently the 2 EDL packages i know are these two. N-B06 and MM-B10 for the G. The N one works fine while the MM one doesn't. Do u have any other EDL packages?
I too think it's a software problem since he has never dropped the phone and only used it for 2 months.
Click to expand...
Click to collapse
I got that package from 4pda. if you go to the 4th category brick repair manual, then enter the link that says "Qualcomm drivers and MiFlash" it will redirect you to 4pda. no need to translate: just open the spoilers (I think it's the 2nd) and you'll find all of the images. You obviously have to use the A2017G ones. there's B10, i think B11, B05, B06 and maybe another N package too
The thing is that it'd be best if you could downgrade to Marshmallow, as that would probably do some other stuff that N packages don't do.

Do you have an external SD card plugged in? Try to use without external sd, i already had lags because of a defective sd card (that couldnt be rescued nor reformatted )

Perru said:
Do you have an external SD card plugged in? Try to use without external sd, i already had lags because of a defective sd card (that couldnt be rescued nor reformatted )
Click to expand...
Click to collapse
I was gonna suggest that, but a read-only SD card wouldn't provoke that. I had one that got read-only after using it as swap for a long time, and you would only notice in twrp (booted in ~2 minutes). If he was able to try to install a system update through the recovery, he was able to write to the SD card --> it's not dead

Perru said:
Do you have an external SD card plugged in? Try to use without external sd, i already had lags because of a defective sd card (that couldnt be rescued nor reformatted )
Click to expand...
Click to collapse
It lags the same. Regardless a sd card is inserted or not.

Choose an username... said:
I got that package from 4pda. if you go to the 4th category brick repair manual, then enter the link that says "Qualcomm drivers and MiFlash" it will redirect you to 4pda. no need to translate: just open the spoilers (I think it's the 2nd) and you'll find all of the images. You obviously have to use the A2017G ones. there's B10, i think B11, B05, B06 and maybe another N package too
The thing is that it'd be best if you could downgrade to Marshmallow, as that would probably do some other stuff that N packages don't do.
Click to expand...
Click to collapse
Thank you for mentioning there is EDL packages in 4pda. I just tried the packages that are available for the G variant on 4pda. But the problem still persists.
I was thinking that too. Trying to downgrade through EDL. But so far i've found only one MM so far, B10. But that ends up in error during flashing process.
Is there any way to install TWRP through EDL without unlocking bootloader? Also, is there any way to unlock BL without adb? If i could at least unlock the BL, i could flash twrp through EDL. There are EDL packages available for flashing TWRP.
Thanks.

nsabir said:
Thank you for mentioning there is EDL packages in 4pda. I just tried the packages that are available for the G variant on 4pda. But the problem still persists.
I was thinking that too. Trying to downgrade through EDL. But so far i've found only one MM so far, B10. But that ends up in error during flashing process.
Is there any way to install TWRP through EDL without unlocking bootloader? Also, is there any way to unlock BL without adb? If i could at least unlock the BL, i could flash twrp through EDL. There are EDL packages available for flashing TWRP.
Thanks.
Click to expand...
Click to collapse
Why don't u just go back to the store with it and get a new one? Its clearly something that can't be fixed by yourself unfortunately.

jw1985 said:
Why don't u just go back to the store with it and get a new one? Its clearly something that can't be fixed by yourself unfortunately.
Click to expand...
Click to collapse
Not all that clear, but yeah the last thing I'd do is unlock the bootloader.

Choose an username... said:
Not all that clear, but yeah the last thing I'd do is unlock the bootloader.
Click to expand...
Click to collapse
Mabey but I think as in my case that something has happened with the hardware. I think it is a hardware's fault that has come up to the surface when he updated the phone like it did 2 me. But hey, it's just my theory.

jw1985 said:
Why don't u just go back to the store with it and get a new one? Its clearly something that can't be fixed by yourself unfortunately.
Click to expand...
Click to collapse
Choose an username... said:
Not all that clear, but yeah the last thing I'd do is unlock the bootloader.
Click to expand...
Click to collapse
jw1985 said:
Mabey but I think as in my case that something has happened with the hardware. I think it is a hardware's fault that has come up to the surface when he updated the phone like it did 2 me. But hey, it's just my theory.
Click to expand...
Click to collapse
The problem is axon 7 is not available in our country. If he has to rma it then he has to send it to a relative in Sweden. Then the relative can do that for him. That's why he asked me to do what i can to revive the phone. RMA is the last resort for him.
Now, i guess i will give up and tell him i did everything i could.
Anyways, thank you all for helping.

[SOLVED] Cascading failures leading to bootloop and softbrick

Hello all. I am about done with this phone. Let me give you a quick timeline.
I had a bootloader error, so I flashed the NPN25.137-35 images to get it working
I used it for about 1 week, installing all of the OTA security updates
One morning, my phone had restarted (I know because "You must enter your pattern after a restart")
Over the course of this day, google apps starting force closing and opening some of them would soft reboot the phone.
The next day, random apps were doing it too
Finally, after one crash, the OS never came back up, it was bootlooping
Upon a hard restart, the phone only boots into bootloader.
This is where I am now. I have downloaded NPN...35-5, NPNS...93-10, and NPNS...92.14. Unfortunately, trying to flash any of these give me a "prevaildation failed security update downgrade" error on every partition I try to flash. The phone just bootloops when I try to restart it.
Things I have tried:
Using fastboot to manually install one of the 3 packages mentioned above.
Using a toolkit to automate the install of the 3 packages.
Using Motorola Device Manager (Never got it to launch)
Flashing the blankflash bin (No usable image file found)
Android OEM unlock setting was not set before this crash, so I cannot unlock the bootloader.
Praying to various deities.
Unzipping the packages, editing the *info.txt file into androidinfo.txt and rezipping to use as an update package (Invalid info.txt error)
I have no idea what to do next. I find it frustrating that Motorola doesn't differentiate between 32GB, 64GB, Amazon ads, no amazon ads, US, EU, or indian variant in it's model numbers! Everything is just "XT1687" and none of the update files are named with words, so knowing what the hell I'm flashing is impossible.
So, frustrations aside, does anyone have any suggestions as to how I can get this phone working again. On a side note, the only thing that I can think of that would cause such a cascading failure from Stock OS is RAM or Storage corruption / failing. Any thoughts on that as well?
=~=~=~=~= SOLUTION FOUND =~=~=~=~=
This may not be a good solution for anyone else that has this issue, but recently Oreo came out and the OTA update was captured. I was able to flash the new OTA because it had a higher security level and at least got the phone bootable.

Do you know what software channel you were on? E.g. retus, retla, etc? If your phone was completely up to date with the OTA, then you can't use a firmware version of less than 92-14 or 93-14. Whether or not you use 92 or 93 depends on the channel.
Locked bootloader limits other possibilities unfortunately.

Retus. I can't guarantee it, but that looks familiar to me, like I had seen it somewhere in the "about phone" section. Is there a released Stock image that has the current security patch? I can't find it on XDA and I'm not trusting androidfixfiles.info or a link in a youtube video.

93-14 hasn't been leaked yet. So you'll be stuck for now.

Kilo__ said:
I have no idea what to do next. I find it frustrating that Motorola doesn't differentiate between 32GB, 64GB, Amazon ads, no amazon ads, US, EU, or indian variant in it's model numbers! Everything is just "XT1687" and none of the update files are named with words, so knowing what the hell I'm flashing is impossible.
So, frustrations aside, does anyone have any suggestions as to how I can get this phone working again. On a side note, the only thing that I can think of that would cause such a cascading failure from Stock OS is RAM or Storage corruption / failing. Any thoughts on that as well?
Click to expand...
Click to collapse
As a last resort you might try booting TWRP in fastboot mode, download and flash the TWRP flashable version of NPNS25.137-93-14. and see if that gets you back to a working phone. Just a suggestion. I don't know if it will boot when the bootloader is locked but it is worth a try.

pastorbob62 said:
As a last resort you might try booting TWRP in fastboot mode, download and flash the TWRP flashable version of NPNS25.137-93-14. and see if that gets you back to a working phone. Just a suggestion. I don't know if it will boot when the bootloader is locked but it is worth a try.
Click to expand...
Click to collapse
The phone was completely stock. It has the stock recovery and bootloader.

Kilo__ said:
The phone was completely stock. It has the stock recovery and bootloader.
Click to expand...
Click to collapse
I get that. What I am suggesting is not installing TWRP, but booting it from fastboot, if it is even possible. Given your results trying to flash a ROM I would say not. But what do you have to lose by trying?

pastorbob62 said:
I get that. What I am suggesting is not installing TWRP, but booting it from fastboot, if it is even possible. Given your results trying to flash a ROM I would say not. But what do you have to lose by trying?
Click to expand...
Click to collapse
I've tried that with a locked bootloader myself, it doesn't allow a non-signed image to boot. OP should give it a go as a 'hail Mary' attempt, but I wouldn't be holding my breath.

I've never heard of a phone that was fully stock with no mods or flashing ever done on it getting a bootloader error. The only bootloader error I am aware of is when the bootloader and ROM build are mismatched which doesn't happen unless the phone is being manually flashed. Was the phone on a custom ROM and you tried to return to full stock? Did you purchase the phone used?
If no to both exactly what did you see when you got the bootloader error? What was the message and what was the phone doing?
People who are on full stock with a locked bootloader don't usually flash system images so your story is a little hard for me to understand unless there is more to it. Normally a factory reset would be the logical solution when your phone is acting odd--flashing a system image seems pretty extreme and it sounds like flashing the wrong system image might be the cause of your current problems.

jhs39 said:
I've never heard of a phone that was fully stock with no mods or flashing ever done on it getting a bootloader error. The only bootloader error I am aware of is when the bootloader and ROM build are mismatched which doesn't happen unless the phone is being manually flashed. Was the phone on a custom ROM and you tried to return to full stock? Did you purchase the phone used?
If no to both exactly what did you see when you got the bootloader error? What was the message and what was the phone doing?
People who are on full stock with a locked bootloader don't usually flash system images so your story is a little hard for me to understand unless there is more to it. Normally a factory reset would be the logical solution when your phone is acting odd--flashing a system image seems pretty extreme and it sounds like flashing the wrong system image might be the cause of your current problems.
Click to expand...
Click to collapse
I agree. :good:

While my phone was wholly stock, I am not new to phone rooting or custom ROMS. I bought the phone from someone who was trying to unlock it. They screwed something up and couldn't get the phone to boot. I bought it, flashed the NPN25.137-35 image after reading plenty of XDA posts about it. This one was the Retus / North America stock image. Flashed using the suggested guidelines that are along the lines of "fb_oem_mode ... flash oem oem.bin ... flash partition sparsechunk1.img" (Something like that). That got it running and once booted, it had many OTAs update in quick succession. After about a week the phone started having trouble. Google apps would crash frequently, then non-google apps started crashing and restarting my phone. After one said restart, the phone would only bootloop. I tried rebooting into recovery to do a factory reset and got the bootloader instead. I can go take a look at the bootloader and see if it says it's secure / oem or what

Kilo__ said:
While my phone was wholly stock, I am not new to phone rooting or custom ROMS. I bought the phone from someone who was trying to unlock it. They screwed something up and couldn't get the phone to boot. I bought it, flashed the NPN25.137-35 image after reading plenty of XDA posts about it. This one was the Retus / North America stock image. Flashed using the suggested guidelines that are along the lines of "fb_oem_mode ... flash oem oem.bin ... flash partition sparsechunk1.img" (Something like that). That got it running and once booted, it had many OTAs update in quick succession. After about a week the phone started having trouble. Google apps would crash frequently, then non-google apps started crashing and restarting my phone. After one said restart, the phone would only bootloop. I tried rebooting into recovery to do a factory reset and got the bootloader instead. I can go take a look at the bootloader and see if it says it's secure / oem or what
Click to expand...
Click to collapse
Try flashing just the stock recovery, as it sounds like that is corrupt. Ideally you'd want to get a recovery that was the same build as you were on after all the OTAs had installed. At least you'd hope that that would give you the factory reset option.
If that doesn't work, there's fastboot commands to erase user data, cache, which would be pretty much what a factory reset would do. Hope you had your data backed up.

Oreo OTA came out recently. Someone grabbed the update file and uploaded it. I was able to flash it and get the phone to boot. The verdict is still out on if it'll be stable.

Your device is corrupted. It can't be trusted and ...

After rooting and decrypting OP6T complains during boot about a corrupted device that may wont work properly....
This is not a problem: If the power key is pressed as indicated by the error message the device boots properly.
But that is exactly the problem!!!
If not pressed then nothing happpens!
Thats mean that it wont boot for example after a reboot...
Tried to clean install latest rom at both slots -via fastboot, via twrp, via system update-, tried factory reset, tried re-encrypt, even locking the bootloader again...
Does anybody have any idea about how to fix it???

azzinder said:
After rooting and decrypting OP6T complains during boot about a corrupted device that may wont work properly....
This is not a problem: If the power key is pressed as indicated by the error message the device boots properly.
But that is exactly the problem!!!
If not pressed then nothing happpens!
Thats mean that it wont boot for example after a reboot...
Tried to clean install latest rom at both slots -via fastboot, via twrp, via system update-, tried factory reset, tried re-encrypt, even locking the bootloader again...
Does anybody have any idea about how to fix it???
Click to expand...
Click to collapse
I remember seeing this long time ago.
You can take a look at this, maybe it will apply to you as well
https://forum.xda-developers.com/oneplus-6/how-to/pie-how-to-fix-device-corrupt-boot-t3841724

azzinder said:
After rooting and decrypting OP6T complains during boot about a corrupted device that may wont work properly....
This is not a problem: If the power key is pressed as indicated by the error message the device boots properly.
But that is exactly the problem!!!
If not pressed then nothing happpens!
Thats mean that it wont boot for example after a reboot...
Tried to clean install latest rom at both slots -via fastboot, via twrp, via system update-, tried factory reset, tried re-encrypt, even locking the bootloader again...
Does anybody have any idea about how to fix it???
Click to expand...
Click to collapse
You're not waiting long enough.
And by the way it tells you to press the power button to PAUSE booting.
It's only a few second wait (possibly one second longer than the default unlocked message on other devices). I just timed it. It's 8 seconds. A regular device will display that message for 3-4 seconds.
It just means that your bootloader is unlocked.
Sent from my ONEPLUS A6013 using Tapatalk

genbu said:
I remember seeing this long time ago.
You can take a look at this, maybe it will apply to you as well
https://forum.xda-developers.com/oneplus-6/how-to/pie-how-to-fix-device-corrupt-boot-t3841724
Click to expand...
Click to collapse
Had this issue on my op6. This solution fixed it for me. not sure if we have this tool for the 6t yet. If the message is orange then it's the unlocked bootloader message. If it's in red it's the corrupt message and you gotta hit the power button twice to boot.

The message i get is in RED color. Not in ORANGE.
And yes if you press twice the power button it boots normally.
My question is about how to get rid of this!!!
If for some reason the device is gonna reboot -like in Settings-> Utilities-> Scheduled power on/off- it wont boot until I get action...

Fear!!!
genbu said:
I remember seeing this long time ago.
You can take a look at this, maybe it will apply to you as well
https://forum.xda-developers.com/oneplus-6/how-to/pie-how-to-fix-device-corrupt-boot-t3841724
Click to expand...
Click to collapse
I am thinking to try this solution but i am scared...
This tool is gonna try to install Oxygen os Oreo for the OP6 as far as I understand.
But the OP6T never had this.
I wonder that maybe it wont boot after process and if it boots gonna refuse to upgrade to Oxygen OS Pie for OP6T
:confused
***Just found the OP6T version here***
As soon as i find a pc with Windows installed i'll try it!!!

I have the same issue and have a remote session booked with OP support today.
Hopefully I will be able to grab a copy of MSMTool for the 6T and share it.

azzinder said:
I am thinking to try this solution but i am scared...
This tool is gonna try to install Oxygen os Oreo for the OP6 as far as I understand.
But the OP6T never had this.
I wonder that maybe it wont boot after process and if it boots gonna refuse to upgrade to Oxygen OS Pie for OP6T
:confused
***Just found the OP6T version here***
As soon as i find a pc with Windows installed i'll try it!!!
Click to expand...
Click to collapse
And password

iaTa said:
I have the same issue and have a remote session booked with OP support today.
Hopefully I will be able to grab a copy of MSMTool for the 6T and share it.
Click to expand...
Click to collapse
Waiting patiently for news...

azzinder said:
Waiting patiently for news...
Click to expand...
Click to collapse
Rescheduled to tomorrow

https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
Done

Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter

This works! It is a lot easier than the MSM download tool solution. However, I wonder if it just mutes the notification, or solves the problem indeed?
I flashed a TWRP backup afterwards and that did not go well. I wonder if that could be caused bij the corrupt problem?
[email protected] said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse

[email protected] said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse
Doesnt working for me. after reboot also i can see same error. however i can boot after twice pressing on power. i do not want to use Msm tool as it will format data. seems no other way as of now

[email protected] said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse
Hey that's amazing! I think this has finally solved this for me on my OnePlus 6. I was perfectly content to just put up with that warning forever, but this seems to have cured it ... And simple too! Thanks ?

[email protected] said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse
Thanks, this worked.

That is only for hide your message. But device is still corrupted. You have to relock your bootloader for that problem.

vikram.mohal said:
That is only for hide your message. But device is still corrupted. You have to relock your bootloader for that problem.
Click to expand...
Click to collapse
i had this happen when i went to update to 9.0.13. ended up backing up to usb otg, reflashing the full update via msm tool, and having to unlock bl again, reflash twrp again, installing magisk again, etc. then, and only then was my device no longer corrupt. i tried many things prior to that, but this was my only fix long term.
ive heard its die to A/B having different security patches, but reflashing both A/B with stock full 9.0.13 did not stop the issue. only msm tool reflashing to 9.0.12 did. and i then did the same on my second partition for good measure.
as far as trying to run decrypted, unless im remembering wrong, unlike the op6, the op6t will not abide that without the corrupted message unless i missed progress. id love that personally, but last i had read here it made op6t unstable. which sucks bonkey dalls.

vikram.mohal said:
That is only for hide your message. But device is still corrupted. You have to relock your bootloader for that problem.
Click to expand...
Click to collapse
No the device is not corrupted. Unlocked bootloader warning vs the device is corrupt are 2 different things. My bootloader ia unlocked since the day 1 and never had the corrupt warning until I flashed OOS 9.0.5. The step above resolved the device is corrupt issue.
---------- Post added at 07:26 AM ---------- Previous post was at 07:22 AM ----------
kitcostantino said:
i had this happen when i went to update to 9.0.13. ended up backing up to usb otg, reflashing the full update via msm tool, and having to unlock bl again, reflash twrp again, installing magisk again, etc. then, and only then was my device no longer corrupt. i tried many things prior to that, but this was my only fix long term.
ive heard its die to A/B having different security patches, but reflashing both A/B with stock full 9.0.13 did not stop the issue. only msm tool reflashing to 9.0.12 did. and i then did the same on my second partition for good measure.
as far as trying to run decrypted, unless im remembering wrong, unlike the op6, the op6t will not abide that without the corrupted message unless i missed progress. id love that personally, but last i had read here it made op6t unstable. which sucks bonkey dalls.
Click to expand...
Click to collapse
Yeah I agree its something to do with the slot A and B. I was running the phone with unlocked bootloader since day 1 and had flashed multiple twrp updates, kernels etc and never had the issue. It's when i recently flashed OOS 9.0.5 and then twrp on it is when this started.
Not sure about OP6T but on my OP6 the terminal commands helped.

[email protected] said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse
This worked on my 6T ! Thanks !