Database Users

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!

can't upgrade

My dad gave me his Nexus 4 to look at the other day because his phone is running slow and using up power very quick . I saw it has been installed couple of suspicious apps like gaining root permission, mobile assistant etc, can't remember the names cause I did a factory reset immediately (already backup the data). Ok it should be clean but then I saw a update notification (it's still on 4.4.3) so go upgrade. The phone reboot into upgrading interface, but after a while it showed 'Error' with a dead robot. I can restart the phone and it's sill in 4.4.3 and ok to use but just can't upgrade. I am thinking those apps must have done something otherwise the phone should be good to upgrade after a factory reset. I am thinking some app may have started a upgrade but somehow never finished (not sure, just my feeling). BTW, my dad knows nothing regarding these apps, they were probably installed by my nephew when he was visiting my parents. Any idea?

If you've done a factory reset you might as well go one step further and unlock the bootloader and flash the 5.0.1 factory image and be done with it

EddyOS said:
If you've done a factory reset you might as well go one step further and unlock the bootloader and flash the 5.0.1 factory image and be done with it
Click to expand...
Click to collapse
I know I can go down that route (boot loader, root, customer image etc), but I am couple of years from doing that last time. So just want some really simple approach if possible. Something like boot into upgrade menu, then clear some cache etc or check some settings etc (I am just thinking based on my faint memory of previous experience). Of course if there is no such thing, then I will do as recommended. Thanks.
BTW, I did the factory reset from settings when the phone is operating not some recovery tool.

Flashing a factory image is the easiest thing to do...
1. Unlock the bootloader - http://forum.xda-developers.com/nexus-4/general/nexus-4-guide-unlock-bootloader-root-t2266654
2. Flash the factory image - Link: https://dl.google.com/dl/android/aosp/occam-lrx22c-factory-86c04af6.tgz Guide: http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
3. Reboot

EddyOS said:
Flashing a factory image is the easiest thing to do...
1. Unlock the bootloader - http://forum.xda-developers.com/nexus-4/general/nexus-4-guide-unlock-bootloader-root-t2266654
2. Flash the factory - Link: https://dl.google.com/dl/android/aosp/occam-lrx22c-factory-86c04af6.tgz Guide: http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
3. Reboot
Click to expand...
Click to collapse
I am having the same issue. Although I am running Android 5.0, still not able to upgrade for 5.0.1. A dead robot with Error! message......

gautam.is.sharma said:
I am having the same issue. Although I am running Android 5.0, still not able to upgrade for 5.0.1. A dead robot with Error! message......
Click to expand...
Click to collapse
Have you messed around the stock system (bootloader, root etc)? I am asking because I don't know what has been done to my Dad's phone and since you got the same problem.

EddyOS said:
Flashing a factory image is the easiest thing to do...
1. Unlock the bootloader - http://forum.xda-developers.com/nexus-4/general/nexus-4-guide-unlock-bootloader-root-t2266654
2. Flash the factory image - Link: https://dl.google.com/dl/android/aosp/occam-lrx22c-factory-86c04af6.tgz Guide: http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
3. Reboot
Click to expand...
Click to collapse
In the first step, in the Prerequisites -> 7. Fastboot binary (Put the file in <sdk_directory>/platform-tools)
The file appears to contain virus/trojan?

Probably a false positive but here's my files from my PC at work:
https://www.hightail.com/download/UlRUV0o4Q1BGR0VsYzhUQw
Trust me, they're not a virus

EddyOS said:
Probably a false positive but here's my files from my PC at work:
https://www.hightail.com/download/UlRUV0o4Q1BGR0VsYzhUQw
Trust me, they're not a virus
Click to expand...
Click to collapse
Thanks for that.

flashed new rom
Followed the link and finally flashed latest rom, fantastic! Thanks. I found the mskip’s toolkit alone is good enough for all the stuff (unlock bootloader, customer recovery, root, install and flash rom). It's much easier than I expected.

The reason I didn't link to toolkits is you're not learning anything by using them. If it goes went wrong, how would you have fixed it?
Better to learn it all now and then you have the knowledge

Soft brick bootloop help! I tried everything I could think of.

Backstory I'm running PureNexus rom with Experimental kernel. Yesterday out of nowhere the phone started bootlooping, usually this is fine and i'll just restart the phone. Well after trying this the bootloop stayed for 15mins. I cleared cache and dalvik and still the same results. I ended up trying to restore a previous nandroid and nothing changed. Frustrated I backuped my titanium backups to my PC and cleared everything, factory reset and data format from twrp. I tried flashing the PureNexus rom clean and still bootloops. It just hangs on the white Google screen with the black background.
I'm following Heisenberg's tutorial (section 10) and after using fastboot and following the directions, i'm getting stuck on flashing the system. I'll get, "load_file: could not allocate 2014388768 bytes
error: cannot load 'C:\angler\images\system.img'
I read restarting the computer might help and i tried that and nothing has changed. It seems this is not rom related, since I downloaded a couple different ones and pushed it to my phone/flashed and it still bootloops. Any suggestions or help? Thanks!

Subiegsr said:
Backstory I'm running PureNexus rom with Experimental kernel. Yesterday out of nowhere the phone started bootlooping, usually this is fine and i'll just restart the phone. Well after trying this the bootloop stayed for 15mins. I cleared cache and dalvik and still the same results. I ended up trying to restore a previous nandroid and nothing changed. Frustrated I backuped my titanium backups to my PC and cleared everything, factory reset and data format from twrp. I tried flashing the PureNexus rom clean and still bootloops. It just hangs on the white Google screen with the black background.
I'm following Heisenberg's tutorial (section 10) and after using fastboot and following the directions, i'm getting stuck on flashing the system. I'll get, "load_file: could not allocate 2014388768 bytes
error: cannot load 'C:\angler\images\system.img'
I read restarting the computer might help and i tried that and nothing has changed. It seems this is not rom related, since I downloaded a couple different ones and pushed it to my phone/flashed and it still bootloops. Any suggestions or help? Thanks!
Click to expand...
Click to collapse
Just download NexusRoot Toolkit to flash back to stock or boot into recovery TWRP and flash PN rom again. It should work fine after that.

luckyfate said:
Just download NexusRoot Toolkit to flash back to stock or boot into recovery TWRP and flash PN rom again. It should work fine after that.
Click to expand...
Click to collapse
Just updated the SDK tool and it actually did let me install the system.img file now after it allocated some. But phone still boot looped.
Downloading the NexusRoot Toolkit now! Thank you for the suggestion, I'll update with the results.

So I installed the toolkit and did the flash stock + Unroot and checked soft-bricket/bootloop and phone is still bootlooping 30 mins later. It's doing the same bootloop as before. Just the black and white Google logo and then the orange pause boot screen. Although, as I type this the Google is not just there and it doesn't flash back to the orange screen..
Not sure if this helps but the live log said:
"Nexus Root Toolkit v2.1.6
Masterlists:
- LatestToolkitFiles.ini 3124
- AndroidDeviceListFull.ini 3124
- AndroidDeviceListFlash.ini 3124
ANGLER-ANGLER: Android 6.0.0 - Any Build
Live log initiated [2016-07-31]:
Further extracting contents of factory image package for use in 'Force Flash Mode'...
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
5VT7N15A25003518 fastboot
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
fastboot getvar product
product: angler
finished. total time: 0.012s
Launching flashstock.bat"

Subiegsr said:
So I installed the toolkit and did the flash stock + Unroot and checked soft-bricket/bootloop and phone is still bootlooping 30 mins later. It's doing the same bootloop as before. Just the black and white Google logo and then the orange pause boot screen. Although, as I type this the Google is not just there and it doesn't flash back to the orange screen..
Not sure if this helps but the live log said:
"Nexus Root Toolkit v2.1.6
Masterlists:
- LatestToolkitFiles.ini 3124
- AndroidDeviceListFull.ini 3124
- AndroidDeviceListFlash.ini 3124
ANGLER-ANGLER: Android 6.0.0 - Any Build
Live log initiated [2016-07-31]:
Further extracting contents of factory image package for use in 'Force Flash Mode'...
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
5VT7N15A25003518 fastboot
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
fastboot getvar product
product: angler
finished. total time: 0.012s
Launching flashstock.bat"
Click to expand...
Click to collapse
Have you tried just downloading the nexus6p IMG and using the flash-all command? I've always been able to recover that way. It restores everything to stock and wipes everything. If it still doesn't work then I would assume a hardware issue. Unless your PC drivers are messing with the process. Some USB hardware can have issues.

Gizmoe said:
Have you tried just downloading the nexus6p IMG and using the flash-all command? I've always been able to recover that way. It restores everything to stock and wipes everything. If it still doesn't work then I would assume a hardware issue. Unless your PC drivers are messing with the process. Some USB hardware can have issues.
Click to expand...
Click to collapse
Could you tell me where I could find the nexus6p img file at and how to flash all command? Seems like most are files I come across are zip files.
*edit: I downloaded the latest version from https://developers.google.com/android/nexus/images did the flash all command and it still hangs on the white Google screen. Although, it did say it couldn't flash boot.sig, recovery.sig, vendor.sig, and etc.. but still completed the flash? I did have all the files unzipped in the same folder of the platform-tools. I just held shift + right clicked the folder and opened the run command window. Am I missing something?

duplicate*

Subiegsr said:
Could you tell me where I could find the nexus6p img file at and how to flash all command? Seems like most are files I come across are zip files.
Click to expand...
Click to collapse
You should try to flash by choosing different stock rom N
Except any stock rom. I will try to flash any android N stock rom by checking Device is normal or no soft brick. If phone boots up fine, u can flash back any to different stock rom like 19X....

luckyfate said:
You should try to flash by choosing different stock rom N
Except any stock rom. I will try to flash any android N stock rom by checking Device is normal or no soft brick. If phone boots up fine, u can flash back any to different stock rom like 19X....
Click to expand...
Click to collapse
doesn't seem any rom is working when booting clean from twrp.

Subiegsr said:
Could you tell me where I could find the nexus6p img file at and how to flash all command? Seems like most are files I come across are zip files.
*edit: I downloaded the latest version from https://developers.google.com/android/nexus/images did the flash all command and it still hangs on the white Google screen. Although, it did say it couldn't flash boot.sig, recovery.sig, vendor.sig, and etc.. but still completed the flash? I did have all the files unzipped in the same folder of the platform-tools. I just held shift + right clicked the folder and opened the run command window. Am I missing something?
Click to expand...
Click to collapse
Usually you would want to run it from an elevated command prompt and navigate to folder and just type flash-all.bat, as long as adb tools are in environment variables it will work. But if it made it all the way to flashing vendor, wiping data and then rebooting it should have worked. This seems like the symptoms of a bad chip. Bad luck I'm guessing. You could try another PC just to be sure but I would trade it in if it was me.

Gizmoe said:
Usually you would want to run it from an elevated command prompt and navigate to folder and just type flash-all.bat, as long as adb tools are in environment variables it will work. But if it made it all the way to flashing vendor, wiping data and then rebooting it should have worked. This seems like the symptoms of a bad chip. Bad luck I'm guessing. I would try another PC just to be sure but I would trade it in if it was me.
Click to expand...
Click to collapse
Yeah, the command prompt installed everything successfully. The only other computer I have is a MacPro that I could try to use, but honestly I spent 7 hours today trying to fix the phone and 4 last night.. i think my eyes are done lol. Good call on the bad chip, probably was too hot over the weekend for it. I did talk to Google and they're sending me a replacement. Sucks though, I took care of my battery life crazy to preserve the life, hopefully the refurb one is just as good. Thanks for the help anyways. :good:

Subiegsr said:
Yeah, the command prompt installed everything successfully. The only other computer I have is a MacPro that I could try to use, but honestly I spent 7 hours today trying to fix the phone and 4 last night.. i think my eyes are done lol. Good call on the bad chip, probably was too hot over the weekend for it. I did talk to Google and they're sending me a replacement. Sucks though, I took care of my battery life crazy to preserve the life, hopefully the refurb one is just as good. Thanks for the help anyways. :good:
Click to expand...
Click to collapse
The exact same thing happened to me over the weekend, and I've tried all the steps you did. I'm now at the same conclusion of hardware failure, so will be calling google today for an RMA.

zamula said:
The exact same thing happened to me over the weekend, and I've tried all the steps you did. I'm now at the same conclusion of hardware failure, so will be calling google today for an RMA.
Click to expand...
Click to collapse
That's crazy it happened to you too. Good luck with the replacement. I hope the replacement doesn't have scratches/scuffs. Mine is seriously immaculate.

Nexus 6p stuck on Google logo

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?

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