Nexus 6p stuck on Google logo - Nexus 6P Q&A, Help & Troubleshooting

I need your help, after upgrading to 7.1.1 the phone is dialed and restarted all the time in this way.
I would appreciate a solution, I leave an exact example of what happens to me.
OEM is not unlocked and debugging mode either because I can not start the phone
My problem is that it does not unlock OEM and I was not active debugging, the phone just let me enter Fastboot but at the time of choosing RECOVERY it restarts

emmafer44 said:
I need your help, after upgrading to 7.1.1 the phone is dialed and restarted all the time in this way.
I would appreciate a solution, I leave an exact example of what happens to me.
OEM is not unlocked and debugging mode either because I can not start the phone
Click to expand...
Click to collapse
Dude try Nexus toolkit my Wugfresh (NRT Toolkit) you have to boot to bootloader and use the application to clean install

I have this same problem. flashed MegaPixel6P, tried using the camera, and then my phone shut off and just keeps rebooting. i think /data and /system are corrupted. any attempt to nandroid backup or restore fails and causes TWRP to reboot.

Alot of users are facing this bootloop issue. So far no one has been able to figure out a pattern that will give us insight into what kind of devices might be affected by this issue. I have created this survey on GoogleForums so far there are very few responses. Please participate to help the community figure out the probable cause for this bootloop
https://docs.google.com/forms/d/1nGAVdnjbkOE1ohvZvqbntb_7afT4p2OzbFIJjJWiy9Q/edit?c=0&w=1
BTW what's your phone's manufacturing date? were you using Magisk or SuHide?

Dadud said:
I have this same problem. flashed MegaPixel6P, tried using the camera, and then my phone shut off and just keeps rebooting. i think /data and /system are corrupted. any attempt to nandroid backup or restore fails and causes TWRP to reboot.
Click to expand...
Click to collapse
If you can get to TWRP, you can just reflash via fastboot (or use NRT). You may be able to apply your TWRP backup afterwards if it is not corrupted.
As for OP, if the bootloader is locked, and "Allow OEM Unlock" is toggled off, your options are slim to none. If this setting was enabled before upgrading then it is still enabled. If it was not, you cannot unlock the bootloader.

v12xke said:
If you can get to TWRP, you can just reflash via fastboot (or use NRT). You may be able to apply your TWRP backup afterwards if it is not corrupted.
As for OP, if the bootloader is locked, and "Allow OEM Unlock" is toggled off, your options are slim to none. If this setting was enabled before upgrading then it is still enabled. If it was not, you cannot unlock the bootloader.
Click to expand...
Click to collapse
Ive tried literally every fix, its dead jim.

Dadud said:
Ive tried literally every fix, its dead jim.
Click to expand...
Click to collapse
Have you tried FORMATTING boot, system, data & vendor and then reflash? Format, not erase/wipe. Move your TWRP backup off to PC and try that. If you are rusty in ADB/Fastboot, then use NRT to do same in advanced tools. If you have a working recovery and your bootloader is unlocked, I would not give up yet. Good luck!

Dadud said:
I have this same problem. flashed MegaPixel6P, tried using the camera, and then my phone shut off and just keeps rebooting. i think /data and /system are corrupted. any attempt to nandroid backup or restore fails and causes TWRP to reboot.
Click to expand...
Click to collapse
Yeah your problem is a bit different that others and it's worth investigating.
To verify your complete emmc, you could try this command in twrp -> advanced settings -> terminal.
dd if=/dev/block/mmcblk0 of=/dev/null
Basically doing a read test by copying the complete mmc to the void. It should give you a status at the end that you can post here.
By the way, the recommended factory flashing is by using flash-all script that is inside the factory image itself. And you need the latests android SDK.

rchtk said:
Yeah your problem is a bit different that others and it's worth investigating.
To verify your complete emmc, you could try this command in twrp -> advanced settings -> terminal.
dd if=/dev/block/mmcblk0 of=/dev/null
Basically doing a read test by copying the complete mmc to the void. It should give you a status at the end that you can post here.
By the way, the recommended factory flashing is by using flash-all script that is inside the factory image itself. And you need the latests android SDK.
Click to expand...
Click to collapse
nope. i enter the command and it does nothing for about a minute before turning itself off
also, im not some complete n00b, so trust me when i say i've tried everything. any time i restore a backup, once it starts applying just /data or /system it'll shut off and bootloop without finishing.

Dadud said:
nope. i enter the command and it does nothing for about a minute before turning itself off
also, im not some complete n00b, so trust me when i say i've tried everything. any time i restore a backup, once it starts applying just /data or /system it'll shut off and bootloop without finishing.
Click to expand...
Click to collapse
You never know the level of the person you're talking about eh. Just tought you hadn't tried the dd.
So dd shutting down before completing wasn't expected but now if I read again your posts, you said doing a photo shuts down the phone and that's quite typical of power related problems. Sh*t.
Could be the battery not holding discharge. Can the device stay in twrp with screen off? Did you try to let it fully discharge and charge it with a slow charge?
There are a lot of information in /sys/ or dmesg but it won't solve your issue.
Still under warranty?

Dadud said:
nope. i enter the command and it does nothing for about a minute before turning itself off
also, im not some complete n00b, so trust me when i say i've tried everything. any time i restore a backup, once it starts applying just /data or /system it'll shut off and bootloop without finishing.
Click to expand...
Click to collapse
Forget restoring your backup for now. You're not a noob, so transfer your TWRP backup to PC, then FORMAT each partition first, including userdata and then reflash using a Google Imagehere. Ensure you are using the latest version of ADB/Fastboot. You didn't mention you have already attempted to Fastboot flash the NMF26F image. What was your result then? The reason I'm asking is that the Google script erases the partitions- does not format, but running the script will tell you which partition failed during writing.

Huawei Customer Service!!
Had the exact same problem creep up on me this past weekend. I ended up calling Huawei and they are doing a free warranty repair on my phone even though I'm almost two months out of warranty.

Make sure you are on SDK 25, I had the problem synonymous. I have been hunted at Huawei and only when I had already given it I realized that I was not on SDK 25 and I know of some others that was the reason with most.
Whether it was the reason with me, I know tomorrow, the device is back and can be picked up,

Tylog said:
Make sure you are on SDK 25...
Click to expand...
Click to collapse
Yes, the latest ADB / Fastboot is required. The rest of the SDK is not mandatory. You can get a minimalist ADB-Fastboot-Driver install from an XDA dev here.
Also, TWRP updated for Angler recently here. This update solved a persistent backup problem I had with the previous v3.0.2-2

bought it second hand, and the previous owner bought it at launch, so im just a month or so out of warranty. im trying to get the original receipt to attempt to RMA it. Huawei's IMEI lookup says its under warranty till april 4th next year.

Tylog said:
Make sure you are on SDK 25, I had the problem synonymous. I have been hunted at Huawei and only when I had already given it I realized that I was not on SDK 25 and I know of some others that was the reason with most.
Whether it was the reason with me, I know tomorrow, the device is back and can be picked up,
Click to expand...
Click to collapse
Was your phone stuck in Bootloop of death as well? How did you fix it? What do think causes this issue and how can it be avoided?

Related

PwnMyMoto Infinite Reboot Loop

Hi,
I recently have fallen victim to this reboot loop issue and yes it is my own fault - all I wanted was to be able to get control of my permissions and installed Pwnmymoto - What I read later on a different thread was that the OTA update would brick my phone.
Now, I could careless since I can get a new phone.
I just have one simple question - Is there anyway to connect to my phone and extract all the data out via adb or any other manner since I know my encryption password?
Here is the breakdown to make things simple.
1. OTA updated keeps phone in infinite reboot loop.
2. Phone is encrypted.
3. I want to be able to retrive my data and just do not know how to connect to my phone because it is encrypted.
I truly would appreciate any help regarding this matter!!
Sincerely,
Tony
minitele said:
Hi,
I recently have fallen victim to this reboot loop issue and yes it is my own fault - all I wanted was to be able to get control of my permissions and installed Pwnmymoto - What I read later on a different thread was that the OTA update would brick my phone.
Now, I could careless since I can get a new phone.
I just have one simple question - Is there anyway to connect to my phone and extract all the data out via adb or any other manner since I know my encryption password?
Here is the breakdown to make things simple.
1. OTA updated keeps phone in infinite reboot loop.
2. Phone is encrypted.
3. I want to be able to retrive my data and just do not know how to connect to my phone because it is encrypted.
I truly would appreciate any help regarding this matter!!
Sincerely,
Tony
Click to expand...
Click to collapse
this has been answered in more than one thread,
You don't have a valid recovery on your phone, you need to fastboot flash --> system, boot, recovery. This will get you out of the bootloop and let your phone update normally.
jimmydafish said:
this has been answered in more than one thread,
You don't have a valid recovery on your phone, you need to fastboot flash --> system, boot, recovery. This will get you out of the bootloop and let your phone update normally.
Click to expand...
Click to collapse
Thanks for the reply man. I will be honest, I did try to search within the forums and there were so many articles I literally was slightly overwhelmed.
Would you be able to point to a specific thread which would provide some steps, I am sure I can follow it. I am a little gunshy since I ended up bricking my phone when I updated. I performed the root process no problem and was happy I could still actually do this stuff. I just dont want to make things worse than they already are.
Thanks again!
minitele said:
Thanks for the reply man. I will be honest, I did try to search within the forums and there were so many articles I literally was slightly overwhelmed.
Would you be able to point to a specific thread which would provide some steps, I am sure I can follow it. I am a little gunshy since I ended up bricking my phone when I updated. I performed the root process no problem and was happy I could still actually do this stuff. I just dont want to make things worse than they already are.
Thanks again!
Click to expand...
Click to collapse
you should join the G+ community for much better and more pointed help. The forums get cluttered.
1) download correct 4.2.2 (57-1) FXZ file
2) extract boot, system, recovery from the file
3) fastboot flash each of the partitions to your phone
(fastboot flash boot boot.img)
(fastboot flash recovery recovery.img)
(fastboot flash system system.img)
Doing this will put your phone in a state where it is ready to update.
minitele said:
Hi,
I recently have fallen victim to this reboot loop issue and yes it is my own fault - all I wanted was to be able to get control of my permissions and installed Pwnmymoto - What I read later on a different thread was that the OTA update would brick my phone.
Now, I could careless since I can get a new phone.
I just have one simple question - Is there anyway to connect to my phone and extract all the data out via adb or any other manner since I know my encryption password?
Here is the breakdown to make things simple.
1. OTA updated keeps phone in infinite reboot loop.
2. Phone is encrypted.
3. I want to be able to retrive my data and just do not know how to connect to my phone because it is encrypted.
I truly would appreciate any help regarding this matter!!
Sincerely,
Tony
Click to expand...
Click to collapse
what the above poster said is all accurate. but you can get your phone out of the bootloop by connecting it to fastboot mode and running fastboot erase cache. after you do that the phone will boot normally. Then you can take whatever data you want off it. then do what the above poster said to take the ota.
What happened was the ota downloaded to the phone and is forcing it to try and update the phone every time it boots. You need to erase that download which is located in /cache and then it wont force reboot thhe phone. this has also been answered many places. basically every thread titled brick or bootloop or whatever.
jayboyyyy said:
what the above poster said is all accurate. but you can get your phone out of the bootloop by connecting it to fastboot mode and running fastboot erase cache. after you do that the phone will boot normally. Then you can take whatever data you want off it. then do what the above poster said to take the ota.
What happened was the ota downloaded to the phone and is forcing it to try and update the phone every time it boots. You need to erase that download which is located in /cache and then it wont force reboot thhe phone. this has also been answered many places. basically every thread titled brick or bootloop or whatever.
Click to expand...
Click to collapse
erasing cache will cause the following to happen,
You reboot your device, it downloads the update, you bootloop again, you wipe cache, your reboot your device, you download the update, your bootloop again.
@jayboyyyy why not just have him fix the problem that is causing the update and then he will update correctly to KitKat, isn't that the best possible outcome?
jimmydafish said:
erasing cache will cause the following to happen,
You reboot your device, it downloads the update, you bootloop again, you wipe cache, your reboot your device, you download the update, your bootloop again.
@jayboyyyy why not just have him fix the problem that is causing the update and then he will update correctly to KitKat, isn't that the best possible outcome?
Click to expand...
Click to collapse
well for starters, it seems he is trying to go from original stock FW to 4.2.2 (he said he is using pwnmymoto so he isn't on 4.2.2 yet).
He also said he wants to keep root so he isn't trying to take 4.4 because he won't have root on that FW.
While flashing that stuff will fix his problem and allow him to take the ota, I always like to make backups of everything before doing that. he won't be able to make a tibu backup of his current set-up by doing what you said because it will remove root once he flashes that stuff. So when he then gets root on 4.2.2 he will not have a back up to work with. (I believe you were thinking he was trying to take 4.4, which he may be, but i didn't read it that way).
If he is trying to take 4.4 he should know that he won't have root and he might never have root on 4.4. So if it is essential to him, he should only be taking the 4.2.2 update.
And once he erases cache. he can freeze otas from popping up on his phone. Also, he won't keep getting stuck in a BL because it prompts you and asks if you want to download the latest ota. it doesn't auto download it, so if he doesn't click yes then it won't download or cause a Bbootloop.
Finally, if he doesn't want to try and root with rockmymoto to save time, he can just install pwnmymoto without running it, then take the ota, then it will automatically root the phone for him. This is why i said what i did.
jayboyyyy said:
well for starters, it seems he is trying to go from original stock FW to 4.2.2 (he said he is using pwnmymoto so he isn't on 4.2.2 yet).
He also said he wants to keep root so he isn't trying to take 4.4 because he won't have root on that FW.
While flashing that stuff will fix his problem and allow him to take the ota, I always like to make backups of everything before doing that. he won't be able to make a tibu backup of his current set-up by doing what you said because it will remove root once he flashes that stuff. So when he then gets root on 4.2.2 he will not have a back up to work with. (I believe you were thinking he was trying to take 4.4, which he may be, but i didn't read it that way).
If he is trying to take 4.4 he should know that he won't have root and he might never have root on 4.4. So if it is essential to him, he should only be taking the 4.2.2 update.
And once he erases cache. he can freeze otas from popping up on his phone. Also, he won't keep getting stuck in a BL because it prompts you and asks if you want to download the latest ota. it doesn't auto download it, so if he doesn't click yes then it won't download or cause a Bbootloop.
Finally, if he doesn't want to try and root with rockmymoto to save time, he can just install pwnmymoto without running it, then take the ota, then it will automatically root the phone for him. This is why i said what i did.
Click to expand...
Click to collapse
Guys, Thank you for your input, it is really appreciated. ( I am glad the forums are still alive and just as helpful as when they started! )
I see that I may not have been as clear as I could have and for that I apologize.
My only goal at this time is to recover my data, since I have activated my old phone ( couldnt wait since it happened on sunday and this is my only phone).
Would the flashboot erase cache method fulfill my only goal which is to recover the data?
If so, are there any different steps that need to be taken to accomplish this?
Thank you again both for your input. If only the world would be discussing two SOLUTIONS to any problem, or worked as this thread , man would it be a much better place!!
minitele said:
Guys, Thank you for your input, it is really appreciated. ( I am glad the forums are still alive and just as helpful as when they started! )
I see that I may not have been as clear as I could have and for that I apologize.
My only goal at this time is to recover my data, since I have activated my old phone ( couldnt wait since it happened on sunday and this is my only phone).
Would the flashboot erase cache method fulfill my only goal which is to recover the data?
If so, are there any different steps that need to be taken to accomplish this?
Thank you again both for your input. If only the world would be discussing two SOLUTIONS to any problem, or worked as this thread , man would it be a much better place!!
Click to expand...
Click to collapse
if you know how to use fastboot then no other steps are necessary. If you had root explorer on your phone, then you could just go to the cache directory and erase it before the phone bootloops again. most people have like 30 to 40 secs before it loops. Just another option. But all you need to do is remove the file from cache.
jayboyyyy said:
if you know how to use fastboot then no other steps are necessary. If you had root explorer on your phone, then you could just go to the cache directory and erase it before the phone bootloops again. most people have like 30 to 40 secs before it loops. Just another option. But all you need to do is remove the file from cache.
Click to expand...
Click to collapse
Just a quick question - Will it matter if my device is encrypted? I only ask because it seems most tutorials never cover encrypted phones.
At least the 10 or so I have read, even youtube videos .
Thanks!
minitele said:
Just a quick question - Will it matter if my device is encrypted? I only ask because it seems most tutorials never cover encrypted phones.
At least the 10 or so I have read, even youtube videos .
Thanks!
Click to expand...
Click to collapse
doubt it matters. I think encryption just encrypts user data and other stuff, not all of the phones files. but i could be wrong. I jsut think thats probably the case. i think encryption can cause problems when people are trying to write to certain directories that might be encrypted. I don't think you should run into an issue with the cache though. Not like it wills crew anything up trying.
jayboyyyy said:
doubt it matters. I think encryption just encrypts user data and other stuff, not all of the phones files. but i could be wrong. I jsut think thats probably the case. i think encryption can cause problems when people are trying to write to certain directories that might be encrypted. I don't think you should run into an issue with the cache though. Not like it wills crew anything up trying.
Click to expand...
Click to collapse
Cool, I have taken a look at a youtube video regarding fastboot.
I will give it a shot and report, thanks again!
minitele said:
Cool, I have taken a look at a youtube video regarding fastboot.
I will give it a shot and report, thanks again!
Click to expand...
Click to collapse
My Moto X is encrypted and can confirm that it will be fine after you fastboot flash boot, system, recovery. My phone was doing something similar when I tried to install OTA without returning the recovery partition to stock. One thing that I learned was that if you are trying to run fastboot command from an Ubuntu machine make sure you run it via sudo, otherwise your regular user will most likely not have permission and the fastboot command will fail.
tracyde said:
My Moto X is encrypted and can confirm that it will be fine after you fastboot flash boot, system, recovery. My phone was doing something similar when I tried to install OTA without returning the recovery partition to stock. One thing that I learned was that if you are trying to run fastboot command from an Ubuntu machine make sure you run it via sudo, otherwise your regular user will most likely not have permission and the fastboot command will fail.
Click to expand...
Click to collapse
To all,
The forums and people in our arena never fail, fastboot erase cache worked perfect. I have recovered all my data and now I will definitely continue to performing a full recovery with stock image.
Thank you again all for all of your help, I am glad to see at least this corner in the internet still is alive and kicking!

Bootloop with google screen and corruption screen after factory image flash

After flashing a rom my phone got hot, and I didn't want to run any more roms for awhile. So i decided it was time for a fresh install of factory image. I read the guide lines closely to fastbooting the latest factory image. Now im in a boot loop with the google unlock icon and the corruption screen . I tried going to stock recovery and factory wipe and still bootlooping. It's been doing this for awhile. Please help!
Did you verify the checksum of the image prior to executing the flash-all script?
redduc900 said:
Did you verify the checksum of the image prior to executing the flash-all script?
Click to expand...
Click to collapse
I don't use flash all script. I flashed each img individually like it's posted in the guide
redduc900 said:
Did you verify the checksum of the image prior to executing the flash-all script?
Click to expand...
Click to collapse
Yes the checksum was verified
XMayhem2099 said:
After flashing a rom my phone got hot, and I didn't want to run any more roms for awhile. So i decided it was time for a fresh install of factory image. I read the guide lines closely to fastbooting the latest factory image. Now im in a boot loop with the google unlock icon and the corruption screen . I tried going to stock recovery and factory wipe and still bootlooping. It's been doing this for awhile. Please help!
Click to expand...
Click to collapse
Don't panic yet. Try formatting both userdata and cache and then flash all the image files again. Any errors?
v12xke said:
Don't panic yet. Try formatting both userdata and cache and then flash all the image files again. Any errors?
Click to expand...
Click to collapse
Did both still the same bootloop
XMayhem2099 said:
Did both still the same bootloop
Click to expand...
Click to collapse
1. Ok, so format, not erase. Exactly which img files did you flash... and you did not get any errors back from fastboot, meaning it always finished cleanly? Have you tried using the flashall.bat?
2. Do you have any saved backups to restore (even of the old custom rom).
3. May sound funny, but have you tried NRT? Wug has a flash to stock/unroot routine with the option for a bootlooping case. It will also allow you to "point" it to the Google image you are using, but you may try allowing NRT to re-download and hash check it again just in case.
You should be able to recover from this. Don't try lock/unlock the bootloader. Leave it unlocked.
v12xke said:
1. Ok, so format, not erase. Exactly which img files did you flash... and you did not get any errors back from fastboot, meaning it always finished cleanly? Have you tried using the flashall.bat?
2. Do you have any saved backups to restore (even of the old custom rom).
3. May sound funny, but have you tried NRT? Wug has a flash to stock/unroot routine with the option for a bootlooping case. It will also allow you to "point" it to the Google image you are using, but you may try allowing NRT to re-download and hash check it again just in case.
You should be able to recover from this. Don't try lock/unlock the bootloader. Leave it unlocked.
Click to expand...
Click to collapse
Absolutely no errors from fastboot which is weird. I'll try the fashall.bat . Nope no custom backups, i tried nexus toolkit and the hashcheck matched still in bootloop. I haven't messed with the bootloader it's always been unlocked
XMayhem2099 said:
Absolutely no errors from fastboot which is weird. I'll try the fashall.bat . Nope no custom backups, i tried nexus toolkit and the hashcheck matched still in bootloop. I haven't messed with the bootloader it's always been unlocked
Click to expand...
Click to collapse
Gotcha. Which partitions did you flash, and in what order? If you look at the flashall.bat in a text editor, there is a check/requirement for a certain bootloader version level to for system (at least, and maybe more) ....anyway when manually flashing, bootloader.img should be the first, and then fastboot reboot into that bootloader before proceeding with all the other partitions. Look for any errors during the flashall batch run.
Edit: You may also want to re-run NRT, confirming the "soft brick mode" is ticked, and check the log window for ANYTHING out of the ordinary. Could also try NRT to revert back to 7.0 release.
v12xke said:
Gotcha. Which partitions did you flash, and in what order? If you look at the flashall.bat in a text editor, there is a check/requirement for a certain bootloader version level to for system (at least, and maybe more) ....anyway when manually flashing, bootloader.img should be the first, and then fastboot reboot into that bootloader before proceeding with all the other partitions. Look for any errors during the flashall batch run.
Edit: You may also want to re-run NRT, confirming the "soft brick mode" is ticked, and check the log window for ANYTHING out of the ordinary. Could also try NRT to revert back to 7.0 release.
Click to expand...
Click to collapse
I did the flash all command it ran successfully. Looks like im still getting a bootloop. I'll let it sit for an hour or so. If it doesn't run ill flash an older factory image. Thanks for the help, Ill let you know what happens.
Mine started doing the same thing last night, so far nothing I have tried has worked. Wireless provider is no help maybe Huawei will replace.
I'm active in a couple threads myself over this exact scenario. What the hell is going on with these phones?
Sent from my Nexus 6 using XDA-Developers mobile app
CyberpodS2 said:
I'm active in a couple threads myself over this exact scenario. What the hell is going on with these phones?
Click to expand...
Click to collapse
Huawei seems to have done a crappy job manufacturing them. Mine bootloops every time I update to a new ROM build, every time I switch ROMs and every time I try to restore a backup. Thankfully I've been able to get out of it every time so far but I've owned a lot of phones and none went into bootloops as often as the 6P. I've resigned myself to the fact that this phone is a time bomb and that it likely won't have a very long life. Would never buy another phone made by Huawei.
Problem google and hawuei (hardware) RMA
People facing bootloop of death.
1. How long have you been using your phone?
2. What's your EMMC and RAM name in bootloader?
3. What's your manufacturing date in bootloader?
4. Do you play games on your phone?
5. Does your phone get hot often?
fapste said:
People facing bootloop of death.
1. How long have you been using your phone?
2. What's your EMMC and RAM name in bootloader?
3. What's your manufacturing date in bootloader?
4. Do you play games on your phone?
5. Does your phone get hot often?
Click to expand...
Click to collapse
1. In general or when it happened? Averaged 4 hours SOT in 14-16 hours total.
2. 128 Toshiba
3. 3-29-2016
4. No
5. No
Same issue on a buddies 6p.. Fastboot commands go through the script with no errors but no results.. Still stuck in this bootloop. Has to be hardware causing this bootloop.
I'm having the same issue
Sent the device to Huawei and they say they'll repair it but I'm not sure if that's possible
My question is when they replace them, is the defect still waiting to pop up again??
Sent from my Nexus 6 using XDA-Developers Legacy app
Bought 2nd hand phone, managed to coax original sales receipt from Google store out of seller. Sent it in for an RMA and they swapped out my motherboard. Was also out of warranty by 2 months

[Q] Warranty Repair/Replacememt Questions

My Nexus 6P is suferring from bootloop issues. I've tried to repair it using every method available but after doing some research online it seems to be a known hardware issue.
I bough my phone on BestBuy and have proof of purchase and everything. I already checked on the Huawei Warranty Query site and my device seems to be under warranty until june 2017.
I have some questions. First, nothing on that site points me to a phone or address about where to start the process. Do any of you who have gone trough this process can be kind to point me in the right direction about where to start.
Second, whats the policy regarding boot unlocking, root, etc etc.
I purchase my Nexus 6P 32GB(H1511 ) outrigh unlocked.
Thank you for any of your help.
Lare2 said:
My Nexus 6P is suferring from bootloop issues. I've tried to repair it using every method available but after doing some research online it seems to be a known hardware issue.
I bough my phone on BestBuy and have proof of purchase and everything. I already checked on the Huawei Warranty Query site and my device seems to be under warranty until june 2017.
I have some questions. First, nothing on that site points me to a phone or address about where to start the process. Do any of you who have gone trough this process can be kind to point me in the right direction about where to start.
Second, whats the policy regarding boot unlocking, root, etc etc.
I purchase my Nexus 6P 32GB(H1511 ) outrigh unlocked.
Thank you for any of your help.
Click to expand...
Click to collapse
Call the hotline support phone number at the bottom of the page you bookmarked. If your phone has boot loop of death Huawei likely can't tell what you did in terms of rooting. If the phone still works well enough that you can flash the full factory image then you should. My understanding is that unlocking the bootloader doesn't void the warranty on Nexus devices.
---------- Post added at 07:00 PM ---------- Previous post was at 06:58 PM ----------
Depending on where you are located Huawei might point you to a local service center rather than have you mail in the device. Huawei contracts with some phone repair chains.
The phone was working OK until suddenly it froze on me. I had to force a reboot and from then on it wasn't able to pass further that the Google logo before restarting again.
I can still get it to enter TWRP and can flash everything but as soon as I try to reatart it, the same happens, it just gets to the Google logo and restarts itself in a boot loop.
Lare2 said:
The phone was working OK until suddenly it froze on me. I had to force a reboot and from then on it wasn't able to pass further that the Google logo before restarting again.
I can still get it to enter TWRP and can flash everything but as soon as I try to reatart it, the same happens, it just gets to the Google logo and restarts itself in a boot loop.
Click to expand...
Click to collapse
Did you try flashing the full factory image with fastboot?
jhs39 said:
Did you try flashing the full factory image with fastboot?
Click to expand...
Click to collapse
Yes I did, using the flash-all.bat as per instructions and it succeeds without issues. But as soon as you restart the device and gets to the Google logo, it restarts again and again and again up to the Google logo and never past from there
I had this very same issue, I ended up using a toolkit and that did away my problems.
SkipSoft toolkit did the job, it's pretty straight forward. You can try pulling your data off the phone through twrp.
Then follow the toolkit to flash stock completely - I would recommend first without wiping userdata, if that doesn't work then with userdata.
For some reason the toolkit worked, and not me manually flashing the images in the correct order and a complete wipe.
Goodluck
TnT_ said:
I had this very same issue, I ended up using a toolkit and that did away my problems.
SkipSoft toolkit did the job, it's pretty straight forward. You can try pulling your data off the phone through twrp.
Then follow the toolkit to flash stock completely - I would recommend first without wiping userdata, if that doesn't work then with userdata.
For some reason the toolkit worked, and not me manually flashing the images in the correct order and a complete wipe.
Goodluck
Click to expand...
Click to collapse
I downloaded the Unified Android Toolkit.
I tried following this instructions
FLASH A STOCK IMAGE BACK TO YOUR DEVICE [FIXES NEARLY ALL PROBLEMS]:
1. Unplug the usb cable
2. Reboot manually to Fastboot Mode [see above for button combination]
3. Plug the usb cable back in
4. From the Toolkit Main Menu select option 9,1 to download/flash a stock firmware
image back to your device. Choose to format userdata and is should fix everything.
Mentioned on this Url
But I can't see and option for 9. When I initially open it it asks me to select the device and then asks me to choose the Android version to go but never see that option 9 mentioned above.
Can you guide me to the steps you followed to fix yours
TnT_ said:
I had this very same issue, I ended up using a toolkit and that did away my problems.
SkipSoft toolkit did the job, it's pretty straight forward. You can try pulling your data off the phone through twrp.
Then follow the toolkit to flash stock completely - I would recommend first without wiping userdata, if that doesn't work then with userdata.
For some reason the toolkit worked, and not me manually flashing the images in the correct order and a complete wipe.
Goodluck
Click to expand...
Click to collapse
The difference I see between the flash-all.bat and using the toolkit is formatting partitions instead of erasing them (including userdata and cache). I realize you are out of the woods now, but others experiencing the bootlooping should try manually fastboot formatting userdata and cache first. @Lare2
v12xke said:
The difference I see between the flash-all.bat and using the toolkit is formatting partitions instead of erasing them (including userdata and cache). I realize you are out of the woods now, but others experiencing the bootlooping should try manually fastboot formatting userdata and cache first. @Lare2
Click to expand...
Click to collapse
Well, for anyone scrolling through here. This is how my device semi-hard bricked (after not booting)
I was flashing PureNexus (I've been using it since I got my 6P in April, it was a standard update to me). I was going from November build to January build, and I thought nothing of it. Next thing I know my phone isn't booting, so I try flashing again. I realize I'm stuck so I backup all the stuff that isn't already backed up, and I wipe everything. Flash stock from my computer. Welp looks like that didn't work. So I go through and format everything before trying again, still. No luck. Vendor refused to flash at that point, so vendor had gotten corrupted in the process ( I kept on getting invalid directory for /vendor - weird right?). Or a string of complex errors in fastboot. I saw something earlier while I was helping someone, about the took. I usually like doing things myself, but I used it as a last resort. I flashed back to stock and everything worked. Then I flashed PureNexus again, and had to do the toolkit all over again. Because my phone absolutely refused to boot on December PureNexus for the angler.
TL;DR : I would not recommend flashing the December update of PureNexus at ALL
I have been trying to get it to work with all the suggestions mentioned here sin my last post. No luck at all. I'm in the process to call the warranty support number and will se how it goes.
Even though I have been unable to get it working this has been an amazing learning experience. I got to try several solutions that made me gain more knowledge that I know will be useful in the future.
I'll report back to see how it went with the warranty guys.
Thank you all

Moto E4 sperry XT1766 not booting up after a restore via TWRP

Long story short, my phone only displays the n/a screen and won't boot up.
I got the phone from Sprint, and it is the Qualcomm version. (The box says that anyway.) I wanted to root the device, so I unlocked the bootloader and attempted to flash SuperSU. This didn't work, as the app didn't show after the flash. I then tried to use Magisk, but I received Error 1 (boot image patched by other programs). To fix this issue, I downloaded a similar stock ROM and tried to install that. I ended up just wiping all the data on the phone, including the OS. Luckily I did make a nandroid backup.
The phone currently has no OS, due to me wiping all my data on it. I made a backup of when it did work (said earlier), with all partitions excluding Data. I have restored it, but it doesn't boot up. TWRP says nothing about there being no OS on the phone. I can't find a stock ROM of this particular phone, but there are some close ones. (sperry XT1768 I believe.) If anyone could help me restore my phone or possibly provide me the stock ROM I would be beyond grateful. I would also be also be okay with posting any logs or things you need.
Thanks much!
Go here:
https://firmware.center/firmware/Motorola/Moto E4/Stock/
This is the Boost XT1766 firmware :
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I did a dumb and was rewarded
So, I ended up flashing the sperry XT1768 ROM that I had downloaded. Keep in mind I already lacked an OS, so I had nothing to lose.
PLEASE NEVER FLASH A ROM THAT DOESN'T BELONG TO YOUR DEVICE. THIS COULD CAUSE YOUR PHONE TO BE BRICKED.
Against the above statement, I literally had nothing to lose. I got my phone to boot up, and it has all of its functionality. Thank you for posting the correct software amarc78, I'll have to flash the correct ROM at a later time.
Moral of the story, please know what you are doing before you do something dumb. Use proper forums (such as the one you are on...) to do such tasks as rooting your phone.
Zachery Calahan said:
So, I ended up flashing the sperry XT1768 ROM that I had downloaded. Keep in mind I already lacked an OS, so I had nothing to lose.
PLEASE NEVER FLASH A ROM THAT DOESN'T BELONG TO YOUR DEVICE. THIS COULD CAUSE YOUR PHONE TO BE BRICKED.
Against the above statement, I literally had nothing to lose. I got my phone to boot up, and it has all of its functionality. Thank you for posting the correct software amarc78, I'll have to flash the correct ROM at a later time.
Moral of the story, please know what you are doing before you do something dumb. Use proper forums (such as the one you are on...) to do such tasks as rooting your phone.
Click to expand...
Click to collapse
Hmmmm, sounds intriguing. I soft bricked my xt1766 a few days ago and have found multiple fixes, but nothing that sticks. That above firmware? Took me two days to realize I needed RSD Lite to flash it. What was that RSD Lite? You play funny with Windows 10, no worries, I'll create my own batch file to manually flash this firmware.........WHAT!!!!!!! Why is there a multi colored ring saying "erasing" at the bottom and rebooting every 30 seconds?????? So after further research and "multiple error 7s" as well as "cant mount cache/data" errors, I came to another fix, lo and behold, im in a TWRP bootloop. Long story short, FML!!!!! Im glad you found a fix. Happy flashing.
TeamAndro08 said:
Hmmmm, sounds intriguing. I soft bricked my xt1766 a few days ago and have found multiple fixes, but nothing that sticks. That above firmware? Took me two days to realize I needed RSD Lite to flash it. What was that RSD Lite? You play funny with Windows 10, no worries, I'll create my own batch file to manually flash this firmware.........WHAT!!!!!!! Why is there a multi colored ring saying "erasing" at the bottom and rebooting every 30 seconds?????? So after further research and "multiple error 7s" as well as "cant mount cache/data" errors, I came to another fix, lo and behold, im in a TWRP bootloop. Long story short, FML!!!!! Im glad you found a fix. Happy flashing.
Click to expand...
Click to collapse
I used this rsdlite, and it works on my PC with Windows 10. Just make sure you have Motorola drivers installed.
madbat99 said:
I used this rsdlite, and it works on my PC with Windows 10. Just make sure you have Motorola drivers installed.
Click to expand...
Click to collapse
Im at work now, but when I get home, I'll definitely give that pony a whirl! Thanks man.
TeamAndro08 said:
Im at work now, but when I get home, I'll definitely give that pony a whirl! Thanks man.
Click to expand...
Click to collapse
For the Twrp loop, try selecting reboot bootloader, then in bootloader, select start. That should get you into system.
There is a fix for that, I'll find the link. Some twrp build aren't wiping something properly and causes a recovery loop after formatting data.
madbat99 said:
For the Twrp loop, try selecting reboot bootloader, then in bootloader, select start. That should get you into system.
There is a fix for that, I'll find the link. Some twrp build aren't wiping something properly and causes a recovery loop after formatting data.
Click to expand...
Click to collapse
Definitely appreciate the info brother, I havent been able to get to it cuz of work. But tonight, I will try all things youve mentioned.
TeamAndro08 said:
Hmmmm, sounds intriguing. I soft bricked my xt1766 a few days ago and have found multiple fixes, but nothing that sticks. That above firmware? Took me two days to realize I needed RSD Lite to flash it. What was that RSD Lite? You play funny with Windows 10, no worries, I'll create my own batch file to manually flash this firmware.........WHAT!!!!!!! Why is there a multi colored ring saying "erasing" at the bottom and rebooting every 30 seconds?????? So after further research and "multiple error 7s" as well as "cant mount cache/data" errors, I came to another fix, lo and behold, im in a TWRP bootloop. Long story short, FML!!!!! Im glad you found a fix. Happy flashing.
Click to expand...
Click to collapse
THIS! Have you ever found a solution? I have the EXACT SAME PROBLEM
steevo398 said:
THIS! Have you ever found a solution? I have the EXACT SAME PROBLEM
Click to expand...
Click to collapse
So you're in a TWRP loop now?
madbat99 said:
So you're in a TWRP loop now?
Click to expand...
Click to collapse
You're just all over the place, kudos to your dedication.
Basically in trying to fix the bad key/erasing boot loop I flashed twrp and tried to format data/unencrpyt which in turn throws errors which require manually reformatting /data until errors are gone and then formatting/unencrypting again which upon rebooting turns into twrp loop. Then tried to flash no-verity, the twrp loop persists.
steevo398 said:
You're just all over the place, kudos to your dedication.
Basically in trying to fix the bad key/erasing boot loop I flashed twrp and tried to format data/unencrpyt which in turn throws errors which require manually reformatting /data until errors are gone and then formatting/unencrypting again which upon rebooting turns into twrp loop. Then tried to flash no-verity, the twrp loop persists.
Click to expand...
Click to collapse
Used to have a couple of these phones .
If you're stuck in a TWRP loop
The quick workaround is to reboot to bootloader, then proceed from there to Start. However, you'll need to do this *every* time until the BCB is cleared.
To clear the BCB manually, issue this command in TWRP terminal:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1M
have you tried formatting data, then flashing.magisk?

Messed up my phone's boot loader image, is retrieving at least my photos possible?

Hi all, I really messed up my 6T today, after messing with the new update and root, I ran the flash_all.bat file (from https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516) to restore images but didn't realize it would clear all my data, I stopped the process after it ran for a few seconds in a panic but now my phone only has the fastboot screen and fastboot.exe from my cmd shell is unable to do anything (just errors out for most commands), is there a way for me to at least retrieve my photos from my phone? I've tried 3rd party software and they all require usb debugging which I can't activate due to my phone not having a boot image. Any help would be a miracle, thanks.
I would try fastbooting a TWRP image. From there you may get access to your internal storage. You can then copy it off to a PC. I say may because you could encounter encryption issues when trying to first boot into TWRP.
If you do hit encryption issues, you could modify the "flash all" batch file to remove the -w command so it doesnt format. However, I thought that it gave you an option to wipe or not?
If it did wipe first, your a gonner my friend. You are too late.
Hope this gives you some insight on where to go from here.
Thanks, that's what some others have been telling me, I have tried to fastboot flash a few versions of TWRP and blu spark (I had the latest android version I believe, so even tried the Q version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482), but none of them are working, I get a failed to load/authenticate error when doing fastboot flash <img name> and fastboot flash boot <img> doesn't error out but I still can't get past the fastboot menu.
I see the flash_all script has the -w in it, but yeah it never prompted me about wiping all data. I managed to kill the process a few seconds in, so even if it was deleting, large files like my photos and videos should still be existent on the drive somewhere, right? Unless the -w command does a really fast purge of the files?
christmasdesparation said:
Thanks, that's what some others have been telling me, I have tried to fastboot flash a few versions of TWRP and blu spark (I had the latest android version I believe, so even tried the Q version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482), but none of them are working, I get a failed to load/authenticate error when doing fastboot flash <img name> and fastboot flash boot <img> doesn't error out but I still can't get past the fastboot menu.
I see the flash_all script has the -w in it, but yeah it never prompted me about wiping all data. I managed to kill the process a few seconds in, so even if it was deleting, large files like my photos and videos should still be existent on the drive somewhere, right? Unless the -w command does a really fast purge of the files?
Click to expand...
Click to collapse
THe -w command does a very fast wipe. So if it was at the beginning of the scrip that more than likely like your files are gone.
Run the script again, this time delete the -w command. This will be your best chance of finding any data.
I see, if the wipe has already happened, are there more low-level ways to retrieve the data? Since it couldn't have purged from the disk all 20 gigs of photos in such a short time span. Though I'm guessing even if there are fragments left like that they're most likely corrupted and unusable?
Anyway, I took it to a shop today since I couldn't do much else my self, we'll see what happens. Lesson learned to always back up before messing with the boot.
Thanks
christmasdesparation said:
Lesson learned to always back up before messing with the boot.
Click to expand...
Click to collapse
And to properly read and understand what it is you're attempting to do.
sssarg said:
And to properly read and understand what it is you're attempting to do.
Click to expand...
Click to collapse
lol yes but in my defense I was already kind of freaking out since the fastboot wasn't working like it did previous times and messed up my normal boot
christmasdesparation said:
I see, if the wipe has already happened, are there more low-level ways to retrieve the data? Since it couldn't have purged from the disk all 20 gigs of photos in such a short time span. Though I'm guessing even if there are fragments left like that they're most likely corrupted and unusable?
Click to expand...
Click to collapse
Probably not possible as user data are stored in a virtual filesystem, mounted over an encrypted partition.
That's the reason why police forces regularly ask phone makers to put a backdoor, it's very hard even for a high tech forensic specialist to find data on a phone
So I actually re-ran the flash_all.bat script without the -w flag and I was able to fast boot flash into twrp (twrp-3.3.1-30-fajita-Q-mauronofrio to be specific). I can see what i believe are my files in the internal storage, but encrypted, however twrp never prompted me for a password, also going to the twrp terminal and entering twrp decrypt <passcode> did not work. Anybody know how to get twrp to decrypt? For some reason flash_all.bat did not restore my original boot or anything so I am only able to boot into recovery mode or twrp from the fastboot on my PC. doing fastboot getvar all shows that my slot-unbootable:a is "yes" if anyone knows how to make sense of this, it would be appreciated, even if I just need to copy my phones internal storage on to my computer and run 3rd party software to decrypt it that is fine
Thank you
Final update: fixed my device completely, turns out I was using the flash all for update 41, all I had to do was use the same script for the 42 update without the -w flag and now my phone is back to normal, everything is where it originally was
christmasdesparation said:
Final update: fixed my device completely, turns out I was using the flash all for update 41, all I had to do was use the same script for the 42 update without the -w flag and now my phone is back to normal, everything is where it originally was
Click to expand...
Click to collapse
Could have used msm tool. You would have lost everything but at least phone would have worked
jamescable said:
Could have used msm tool. You would have lost everything but at least phone would have worked
Click to expand...
Click to collapse
Yeah, he was trying hard to avoid that.
christmasdesparation said:
Final update: fixed my device completely, turns out I was using the flash all for update 41, all I had to do was use the same script for the 42 update without the -w flag and now my phone is back to normal, everything is where it originally was
Click to expand...
Click to collapse
Im glad it did not wipe the phone the like I feared it may have. Glad you got it going.
Scott said:
Im glad it did not wipe the phone the like I feared it may have. Glad you got it going.
Click to expand...
Click to collapse
Thanks, I owe it to you, your original advice was spot on and all I failed to do was check the version number
jamescable said:
Could have used msm tool. You would have lost everything but at least phone would have worked
Click to expand...
Click to collapse
Well to me "everything" on my phone was worth more to me than the phone itself

Categories

Resources