Database Users

[Q] Stuck in Colored Circles screen

I've already searched the forums and found no thread with the solution to my problem. People have had a very similar issue, but not exactly mine, so prior solutions I've found seem to not solve it:
I have a Nexus 7 (2012 WiFi).
It is rooted, clockwork mod.
I have a mac (that seems to not want to detect my Nexus 7 anymore).
I got the update for KitKat, like an idiot, I jumped at it, let it update overnight, and now I'm stuck in the 4 circles loading screen. Since I have CWM, I'm stuck in the CWM recovery mode when I try to do a factory reset. The factory reset does nothing, I was hoping to get back into the stock recovery mode, but have no idea how to get there (nor do I think it's possible).
Keep in mind, I'm semi-tech savvy, but when it comes to "flashing blah blah" I have no idea what the hell anyone is talking about if it's not broken down step by step in layman's terms. If you say, "open the terminal, and type exactly this", then I'm golden, but otherwise, I'm just googling tab after tab to figure out what it means.
As stated above, my mac does not want to even acknowledge the existence of my tablet either with ADK or Android File Transfer. Is there maybe a way I can put a zip on an sd and somehow use an SD reader to mini-usb adapter to sideload a fix? Anyone have any other ideas of how I can fix this issue? I'm not enjoying my Nexus 7 as a paper weight.
Thanks.

Phillustrate said:
I've already searched the forums and found no thread with the solution to my problem. People have had a very similar issue, but not exactly mine, so prior solutions I've found seem to not solve it:
I have a Nexus 7 (2012 WiFi).
It is rooted, clockwork mod.
I have a mac (that seems to not want to detect my Nexus 7 anymore).
I got the update for KitKat, like an idiot, I jumped at it, let it update overnight, and now I'm stuck in the 4 circles loading screen. Since I have CWM, I'm stuck in the CWM recovery mode when I try to do a factory reset. The factory reset does nothing, I was hoping to get back into the stock recovery mode, but have no idea how to get there (nor do I think it's possible).
Keep in mind, I'm semi-tech savvy, but when it comes to "flashing blah blah" I have no idea what the hell anyone is talking about if it's not broken down step by step in layman's terms. If you say, "open the terminal, and type exactly this", then I'm golden, but otherwise, I'm just googling tab after tab to figure out what it means.
As stated above, my mac does not want to even acknowledge the existence of my tablet either with ADK or Android File Transfer. Is there maybe a way I can put a zip on an sd and somehow use an SD reader to mini-usb adapter to sideload a fix? Anyone have any other ideas of how I can fix this issue? I'm not enjoying my Nexus 7 as a paper weight.
Thanks.
Click to expand...
Click to collapse
If your recovery is broken you need to boot into the Bootloader (Hold power until you see the Google logo, then press Vol down.) and then use fastboot to flash a good image from there. You can then do a factory reset etc. You could also do a factory reset from fastboot directly, but you'll want to fix your broken recovery at some point.
Or.. Possibly the better method, since your device is in an unknown state.
https://developers.google.com/android/nexus/images
Get the image FOR YOUR EXACT DEVICE. Don't get the LTE version for the WIFI, etc. Then just run the batch file. It will reset everything (including the internal SD card) and reflash the stock OS. This will leave your bootloader unlocked, with a stock ROM, kernel, recovery. You can flash the custom recovery and supersu.zip if you wish to re-root it.

khaytsus said:
If your recovery is broken you need to boot into the Bootloader (Hold power until you see the Google logo, then press Vol down.) and then use fastboot to flash a good image from there. You can then do a factory reset etc. You could also do a factory reset from fastboot directly, but you'll want to fix your broken recovery at some point.
Or.. Possibly the better method, since your device is in an unknown state.
Get the image FOR YOUR EXACT DEVICE. Don't get the LTE version for the WIFI, etc. Then just run the batch file. It will reset everything (including the internal SD card) and reflash the stock OS. This will leave your bootloader unlocked, with a stock ROM, kernel, recovery. You can flash the custom recovery and supersu.zip if you wish to re-root it.
Click to expand...
Click to collapse
Thank you so much for the response. I apologize for my ignorance: My secondary issue is that my computer does not even recognize when I plug in my Nexus 7. It did previously before my tinkering with it, and before the KitKat update, but now it's like I'm plugging in a brick. I did get to the point of downloading the proper factory image, but it does me no good since I can't load it on there. I don't know how to flash the drive when my computer can't even load anything on to it.
Is it possible to load it through a micro-usb to SD reader adapter? I'm thinking I can load the factory image on to the SD card, and then "sideload" the factory image from there.

To add information so I maybe can get help:
I think the reason my mac doesn't detect it is because I can't get the device into MTP mode so that my mac will see it as a storage device.
I would have to be able to get into the Android OS settings to actually be able to change this setting. I can get into bootload mode, and cwm recovery, but nothing else. I just need some way to get this factory image file onto the Nexus 7, but can't figure out how since this connection does nothing.

Fastboot and recovery do not require any settings configured in the OS. They are independent of the OS. You need to update your sdk on your Mac for the device to be seen in terminal
Sent from my Nexus 5

Pirateghost said:
Fastboot and recovery do not require any settings configured in the OS. They are independent of the OS. You need to update your sdk on your Mac for the device to be seen in terminal
Sent from my Nexus 5
Click to expand...
Click to collapse
It is up to date. It is not recognized either in sdk, android file transfer, or just in finder as a device at all.

You should never see it in a file browser of any sort while in recovery or fastboot mode. Use adb in recovery and fastboot commands in fastboot
Sent from my Nexus 5

I fixed it and recovered it back to 4.2.2, but I will take it!!! NOW I'm going to update to KitKat.
Unfortunately, I can't post links right now since I'm such a new member, but to anyone that has this same issue, I used this guide to get me through it:
Google "nexus 7 factory image restore" written by 2DefMouse. You should find it there.
Also, there's a youtube video counterpart, Google/Youtube this: "How to return to Stock / Updating with Factory Images / Unbrick your Nexus 7"
I'm sure this is fairly common and usual, but for some reason I couldn't figure it out, but to any morons like me, I recommend the guides I followed.
As a tip, for mac, when you type terminal commands, always put the ./ before every "fastboot"... so "./fastboot"
Also, in the guide, it says to type "./fastboot-mac"... I left out the "-mac".
Thanks everyone.

Softbricked during unlock

I went to unlock my Shield TV Pro model using fastboot, and after I hit OK on the OEM unlock screen it rebooted as per usual. Now my issue is its been sitting here 'erasing data' for hours and I can't boot back into the bootloader using any of the methods on Nvidias site. Does anyone know how to get back into the bootloader or into fastboot mode? If I unplug it the console will show the splash screen then continue with its endless erasing data screen. I factory reset it anyway before unlocking to help shorten the time because then there's virtually no data on it. Normally I would use a hardware override via the buttons like on a phone but the methods Nvidia has don't work so its been a fun day.
Edit: I managed to boot into the bootloader, however even after using the fastboot format userdata and cache commands (both were successful) it's still not going past the 'erasing data' android. I also can't flash any images because it results in an error.

It's supposed to take a long time (hours). Just let it do it's thing.

Luxferro said:
It's supposed to take a long time (hours). Just let it do it's thing.
Click to expand...
Click to collapse
Well it's been 12 hours now so I'm going to try and see if there's another way to fix this

Pilz said:
Well it's been 12 hours now so I'm going to try and see if there's another way to fix this
Click to expand...
Click to collapse
Yeah, you're right. 12 hours is way too long... something is definitely wrong. Per Nvidia's factory image page:
NOTE: On the SHIELD Android TV Pro 500GB edition, two steps of the flash process may take a very long time. The first time you apply a custom OS image, you must execute fastboot oem unlock which securely erases the user data partition and can take up to two hours. Additional, each time the user data partition is flashed with fastboot flash userdata userdata.img it must be erased which can take up to an hour.
Click to expand...
Click to collapse

Luxferro said:
Yeah, you're right. 12 hours is way too long... something is definitely wrong. Per Nvidia's factory image page:
NOTE: On the SHIELD Android TV Pro 500GB edition, two steps of the flash process may take a very long time. The first time you apply a custom OS image, you must execute fastboot oem unlock which securely erases the user data partition and can take up to two hours. Additional, each time the user data partition is flashed with fastboot flash userdata userdata.img it must be erased which can take up to an hour.
Click to expand...
Click to collapse
Yeah I read something similar in their website. I'm still messing with it trying to get it to boot fully now. I wish the Android TV's had a better method to flash things and boot into the BL like phones do. My Nexus Player is still alive and well running M so that's good.

Update:
I managed to get it to boot after messing with it for another few hours so St least it somewhat works now.

Just need someone to confirm that I'm SCREWED

I cannot get my phone to accept ADB commands while in the Bootloader. The phone has been doing some strange stuff so I decided to start from scratch and reinstall everything. I tried to use the "Restore to Stock Tool" but once it reboots to the bootloader, I get "device not found" until it gets to the erase commands, phone restarts and is wiped but still on the 6.0 update. I tried "adb devices" and the device shows up but if I try "adb reboot bootloader" it reboots to the bootloader but "adb devices" doesn't see the device anymore. The only thing I can think that could cause this is a corrupt bootloader but how can you correct the problem if you can't flash anything? If someone can suggest anything I can try, I would appreciate it.

6.0 is the current update...
Flash twrp then try flashing a custom ROM. Honestly it sounds like you might be doing something wrong, or maybe a bad USB cable? Keep trying I don't think you're screwed

Steeleio said:
I cannot get my phone to accept ADB commands while in the Bootloader. The phone has been doing some strange stuff so I decided to start from scratch and reinstall everything. I tried to use the "Restore to Stock Tool" but once it reboots to the bootloader, I get "device not found" until it gets to the erase commands, phone restarts and is wiped but still on the 6.0 update. I tried "adb devices" and the device shows up but if I try "adb reboot bootloader" it reboots to the bootloader but "adb devices" doesn't see the device anymore. The only thing I can think that could cause this is a corrupt bootloader but how can you correct the problem if you can't flash anything? If someone can suggest anything I can try, I would appreciate it.
Click to expand...
Click to collapse
Do you still have an custom recovery installed? TWRP?

Steeleio said:
I cannot get my phone to accept ADB commands while in the Bootloader. The phone has been doing some strange stuff so I decided to start from scratch and reinstall everything. I tried to use the "Restore to Stock Tool" but once it reboots to the bootloader, I get "device not found" until it gets to the erase commands, phone restarts and is wiped but still on the 6.0 update. I tried "adb devices" and the device shows up but if I try "adb reboot bootloader" it reboots to the bootloader but "adb devices" doesn't see the device anymore. The only thing I can think that could cause this is a corrupt bootloader but how can you correct the problem if you can't flash anything? If someone can suggest anything I can try, I would appreciate it.
Click to expand...
Click to collapse
Frankly, I would be surprised if your "SCREWED"... it sounds more like your misinformed.
ADB will NEVER work in the bootloader, it isn't intended to, that is what fastboot is for. ADB stands for Android Debugging Bridge because it is the computer's "bridge" to Android, you can think of it as the connection to the operating system, meaning the phone must be booted and running Android for it to work or there is nothing to "bridge" to.
Fastboot is a more limited tool designed to talk to the bootloader and get the phone so that operating system can boot or it can be returned to it's factory state, fastboot cannot talk or "bridge" to Android. They are different and unique tools with different purposes that are used at different times.
This is another case of why one-click or scripting tools are not recommended... even if they work 90% of the time or more, there is still failure due to automation.
I would suggest grabbing the full factory firmware package and install it MANUALLY with the fastboot commands and you will likely be fine. Remember to give it time on the first boot, it can be 20 minutes or more before things look like they are progressing initially.

acejavelin said:
Frankly, I would be surprised if your "SCREWED"... it sounds more like your misinformed.
ADB will NEVER work in the bootloader, it isn't intended to, that is what fastboot is for. ADB stands for Android Debugging Bridge because it is the computer's "bridge" to Android, you can think of it as the connection to the operating system, meaning the phone must be booted and running Android for it to work or there is nothing to "bridge" to.
Fastboot is a more limited tool designed to talk to the bootloader and get the phone so that operating system can boot or it can be returned to it's factory state, fastboot cannot talk or "bridge" to Android. They are different and unique tools with different purposes that are used at different times.
This is another case of why one-click or scripting tools are not recommended... even if they work 90% of the time or more, there is still failure due to automation.
I would suggest grabbing the full factory firmware package and install it MANUALLY with the fastboot commands and you will likely be fine. Remember to give it time on the first boot, it can be 20 minutes or more before things look like they are progressing initially.
Click to expand...
Click to collapse
So I got the computer to recognize the phone. I reset everything back to stock 5.1.1. Once I had it reset, the Bluetooth would not turn on (which was one of my original problems). So I took all the OTAs to get back to 6.0. For some reason when It got to about the 3rd update, it wouldn't complete. It failed but didn't specify a reason. I tried this 2 times without any luck. I left it at the update it was on and used it for a day. The Bluetooth still would not turn on and I was experiencing random data drops which required a reboot. I finally gave up because I was so frustrated. I figured something must be going wrong some hardware inside the phone.

Steeleio said:
So I got the computer to recognize the phone. I reset everything back to stock 5.1.1. Once I had it reset, the Bluetooth would not turn on (which was one of my original problems). So I took all the OTAs to get back to 6.0. For some reason when It got to about the 3rd update, it wouldn't complete. It failed but didn't specify a reason. I tried this 2 times without any luck. I left it at the update it was on and used it for a day. The Bluetooth still would not turn on and I was experiencing random data drops which required a reboot. I finally gave up because I was so frustrated. I figured something must be going wrong some hardware inside the phone.
Click to expand...
Click to collapse
Style or Pure? And why flash 5.1.1 when 6.0 images are available? http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Also, I see many guides don't show flashing the Bluetooth firmware for some reason, so depending on the guide you used might be wrong, always look at the XML file in the image.
fastboot flash bluetooth BTFM.bin
Sent from my XT1575 using Tapatalk

acejavelin said:
Style or Pure? And why flash 5.1.1 when 6.0 images are available? http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Also, I see many guides don't show flashing the Bluetooth firmware for some reason, so depending on the guide you used might be wrong, always look at the XML file in the image.
fastboot flash bluetooth BTFM.bin
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Pure. I figured if I start all the way over from the beginning it would work out. Like I said, even one of the OTA's failed. I tried flashing the BTFM.bin file but that didn't work either. I will try some other stuff when I get off work today.

So I tried starting from scratch again. I get a "validation failed" when I try to flash the gpt.bin file. Everything else worked. Bluetooth and data are working now. Could I have a corrupt partition that is causing the validation to fail? Does anyone know the partition sizes for the Pure?

Steeleio said:
So I tried starting from scratch again. I get a "validation failed" when I try to flash the gpt.bin file. Everything else worked. Bluetooth and data are working now. Could I have a corrupt partition that is causing the validation to fail? Does anyone know the partition sizes for the Pure?
Click to expand...
Click to collapse
No, in fact it is quite common to get that message with the partition information... Ignore it, if everything else went fine and you having no more problems, your good to go.

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?

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