Database Users

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?

[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

[SOLVED] Cascading failures leading to bootloop and softbrick

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

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

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

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

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

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

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

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

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

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

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

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

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

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