Database Users

[Q] Where can I find correct system image for the I/O Tab 10.1?

I've been going through quite an ordeal with my Tab over the past few days.
It started with my Tab boot looping for no apparent reason, then I couldn't get fastboot to work, but now I solved my fastboot problems. I followed some instructions (here: http://forum.xda-developers.com/showpost.php?p=14600617&postcount=111) on how to use fastboot to get it working again, and i flashed that system image linked to in that post. And it worked, I had my Tab up and running again, but I noticed that my storage space total is now at 13GB; I remember it having 32GB total storage before this whole ordeal. I'm guessing I flashed the wrong system image to my device, so does anyone have the correct system image for the I/O Tab 10.1?
I tried this one: http://forum.xda-developers.com/showthread.php?t=1075993 and my device gets stuck in the boot screen (not even looping, it just stays on the "Samsung Galaxy Tab 10.1" screen)
Any help would really be appreciated.

use this to recover:
http://forum.xda-developers.com/showpost.php?p=14684694&postcount=77
read the whole thing (quoted and unquoted).
you can get images here:
http://droidbasement.com/galaxy/sys-backup/hc_31

if you have media (/data/media (internal sdcard)), back it up prior (you will lose it).

that droidbasement link returned a 404 not found error.

fixed.
refresh.

let me upload raw fastbootable images also, for the first part.
check back in one hr.

done uploading.

Ok, I've got it all sorted out. Thanks for the quick response, Pershoot.
Here's a breakdown of how I got it working again...
First, I installed PDAnet as a shortcut to get the fastboot drivers, as soon as I installed it, fastboot started working.
Then I downloaded the files linked here: http://forum.xda-developers.com/show...&postcount=111
Then I followed the first half of Pershoot's instructions (http://forum.xda-developers.com/showpost.php?p=14684694&postcount=77) using the files provided by novicejeep. I did all the fastboot stuff, booted into recovery, factory reset, reboot, but instead of getting a boot loop, my device booted up just fine. I had previously flashed these same files to get it working but those times my storage showed as 13GB for some reason, but now it's showing as 27GB. I'm guessing the factory reset corrected that issue (or maybe it was erasing before flashing each thing?).
The only downside now is that I'm back on 3.0.1, so what's the safest way to get up to 3.1 for a root user? I suppose I'll take my chances with System Update in the Settings.
Thanks Pershoot, novicejeep, kdietze3 and everyone else here on the forums

if you are on 3.0, then just use the restore method to 3.1.
you would have been on 3.1, if you would have used all 3.1 images, as outlined in my instructions from the sys-backup/hc_31 folder.

I ran system update and now I'm on 3.1 again
Even though I had fastboot working, I couldn't get ADB to work so I couldn't push the backup file to the device so I could restore it. Without that, I just kept bootlooping.
When I used the 3.0 files, I didn't even get that far in your instructions. At the part where you expect it to boot loop, it just booted up with no problems. Whereas when I flashed the hc31 files you posted, I bootlooped at that step.

dracoaffectus said:
I ran system update and now I'm on 3.1 again
Even though I had fastboot working, I couldn't get ADB to work so I couldn't push the backup file to the device so I could restore it. Without that, I just kept bootlooping.
When I used the 3.0 files, I didn't even get that far in your instructions. At the part where you expect it to boot loop, it just booted up with no problems. Whereas when I flashed the hc31 files you posted, I bootlooped at that step.
Click to expand...
Click to collapse
yea as outlined. then prceed on with the instructions, and when done, you will be sorted.

The new kernel did not like my tab. It crashed pretty hard when I plugged it in to charge. Now when I try to boot, it loops at the "glowing SAMSUNG" screen. I tried to restore with ODIN and it's still looping. Going to try this method.

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.

Bootloop with google screen and corruption screen after factory image flash

After flashing a rom my phone got hot, and I didn't want to run any more roms for awhile. So i decided it was time for a fresh install of factory image. I read the guide lines closely to fastbooting the latest factory image. Now im in a boot loop with the google unlock icon and the corruption screen . I tried going to stock recovery and factory wipe and still bootlooping. It's been doing this for awhile. Please help!

Did you verify the checksum of the image prior to executing the flash-all script?

redduc900 said:
Did you verify the checksum of the image prior to executing the flash-all script?
Click to expand...
Click to collapse
I don't use flash all script. I flashed each img individually like it's posted in the guide

redduc900 said:
Did you verify the checksum of the image prior to executing the flash-all script?
Click to expand...
Click to collapse
Yes the checksum was verified

XMayhem2099 said:
After flashing a rom my phone got hot, and I didn't want to run any more roms for awhile. So i decided it was time for a fresh install of factory image. I read the guide lines closely to fastbooting the latest factory image. Now im in a boot loop with the google unlock icon and the corruption screen . I tried going to stock recovery and factory wipe and still bootlooping. It's been doing this for awhile. Please help!
Click to expand...
Click to collapse
Don't panic yet. Try formatting both userdata and cache and then flash all the image files again. Any errors?

v12xke said:
Don't panic yet. Try formatting both userdata and cache and then flash all the image files again. Any errors?
Click to expand...
Click to collapse
Did both still the same bootloop

XMayhem2099 said:
Did both still the same bootloop
Click to expand...
Click to collapse
1. Ok, so format, not erase. Exactly which img files did you flash... and you did not get any errors back from fastboot, meaning it always finished cleanly? Have you tried using the flashall.bat?
2. Do you have any saved backups to restore (even of the old custom rom).
3. May sound funny, but have you tried NRT? Wug has a flash to stock/unroot routine with the option for a bootlooping case. It will also allow you to "point" it to the Google image you are using, but you may try allowing NRT to re-download and hash check it again just in case.
You should be able to recover from this. Don't try lock/unlock the bootloader. Leave it unlocked.

v12xke said:
1. Ok, so format, not erase. Exactly which img files did you flash... and you did not get any errors back from fastboot, meaning it always finished cleanly? Have you tried using the flashall.bat?
2. Do you have any saved backups to restore (even of the old custom rom).
3. May sound funny, but have you tried NRT? Wug has a flash to stock/unroot routine with the option for a bootlooping case. It will also allow you to "point" it to the Google image you are using, but you may try allowing NRT to re-download and hash check it again just in case.
You should be able to recover from this. Don't try lock/unlock the bootloader. Leave it unlocked.
Click to expand...
Click to collapse
Absolutely no errors from fastboot which is weird. I'll try the fashall.bat . Nope no custom backups, i tried nexus toolkit and the hashcheck matched still in bootloop. I haven't messed with the bootloader it's always been unlocked

XMayhem2099 said:
Absolutely no errors from fastboot which is weird. I'll try the fashall.bat . Nope no custom backups, i tried nexus toolkit and the hashcheck matched still in bootloop. I haven't messed with the bootloader it's always been unlocked
Click to expand...
Click to collapse
Gotcha. Which partitions did you flash, and in what order? If you look at the flashall.bat in a text editor, there is a check/requirement for a certain bootloader version level to for system (at least, and maybe more) ....anyway when manually flashing, bootloader.img should be the first, and then fastboot reboot into that bootloader before proceeding with all the other partitions. Look for any errors during the flashall batch run.
Edit: You may also want to re-run NRT, confirming the "soft brick mode" is ticked, and check the log window for ANYTHING out of the ordinary. Could also try NRT to revert back to 7.0 release.

v12xke said:
Gotcha. Which partitions did you flash, and in what order? If you look at the flashall.bat in a text editor, there is a check/requirement for a certain bootloader version level to for system (at least, and maybe more) ....anyway when manually flashing, bootloader.img should be the first, and then fastboot reboot into that bootloader before proceeding with all the other partitions. Look for any errors during the flashall batch run.
Edit: You may also want to re-run NRT, confirming the "soft brick mode" is ticked, and check the log window for ANYTHING out of the ordinary. Could also try NRT to revert back to 7.0 release.
Click to expand...
Click to collapse
I did the flash all command it ran successfully. Looks like im still getting a bootloop. I'll let it sit for an hour or so. If it doesn't run ill flash an older factory image. Thanks for the help, Ill let you know what happens.

Mine started doing the same thing last night, so far nothing I have tried has worked. Wireless provider is no help maybe Huawei will replace.

I'm active in a couple threads myself over this exact scenario. What the hell is going on with these phones?
Sent from my Nexus 6 using XDA-Developers mobile app

CyberpodS2 said:
I'm active in a couple threads myself over this exact scenario. What the hell is going on with these phones?
Click to expand...
Click to collapse
Huawei seems to have done a crappy job manufacturing them. Mine bootloops every time I update to a new ROM build, every time I switch ROMs and every time I try to restore a backup. Thankfully I've been able to get out of it every time so far but I've owned a lot of phones and none went into bootloops as often as the 6P. I've resigned myself to the fact that this phone is a time bomb and that it likely won't have a very long life. Would never buy another phone made by Huawei.

Problem google and hawuei (hardware) RMA

People facing bootloop of death.
1. How long have you been using your phone?
2. What's your EMMC and RAM name in bootloader?
3. What's your manufacturing date in bootloader?
4. Do you play games on your phone?
5. Does your phone get hot often?

fapste said:
People facing bootloop of death.
1. How long have you been using your phone?
2. What's your EMMC and RAM name in bootloader?
3. What's your manufacturing date in bootloader?
4. Do you play games on your phone?
5. Does your phone get hot often?
Click to expand...
Click to collapse
1. In general or when it happened? Averaged 4 hours SOT in 14-16 hours total.
2. 128 Toshiba
3. 3-29-2016
4. No
5. No

Same issue on a buddies 6p.. Fastboot commands go through the script with no errors but no results.. Still stuck in this bootloop. Has to be hardware causing this bootloop.

I'm having the same issue
Sent the device to Huawei and they say they'll repair it but I'm not sure if that's possible

My question is when they replace them, is the defect still waiting to pop up again??
Sent from my Nexus 6 using XDA-Developers Legacy app

Bought 2nd hand phone, managed to coax original sales receipt from Google store out of seller. Sent it in for an RMA and they swapped out my motherboard. Was also out of warranty by 2 months

[Q] Warranty Repair/Replacememt Questions

My Nexus 6P is suferring from bootloop issues. I've tried to repair it using every method available but after doing some research online it seems to be a known hardware issue.
I bough my phone on BestBuy and have proof of purchase and everything. I already checked on the Huawei Warranty Query site and my device seems to be under warranty until june 2017.
I have some questions. First, nothing on that site points me to a phone or address about where to start the process. Do any of you who have gone trough this process can be kind to point me in the right direction about where to start.
Second, whats the policy regarding boot unlocking, root, etc etc.
I purchase my Nexus 6P 32GB(H1511 ) outrigh unlocked.
Thank you for any of your help.

Lare2 said:
My Nexus 6P is suferring from bootloop issues. I've tried to repair it using every method available but after doing some research online it seems to be a known hardware issue.
I bough my phone on BestBuy and have proof of purchase and everything. I already checked on the Huawei Warranty Query site and my device seems to be under warranty until june 2017.
I have some questions. First, nothing on that site points me to a phone or address about where to start the process. Do any of you who have gone trough this process can be kind to point me in the right direction about where to start.
Second, whats the policy regarding boot unlocking, root, etc etc.
I purchase my Nexus 6P 32GB(H1511 ) outrigh unlocked.
Thank you for any of your help.
Click to expand...
Click to collapse
Call the hotline support phone number at the bottom of the page you bookmarked. If your phone has boot loop of death Huawei likely can't tell what you did in terms of rooting. If the phone still works well enough that you can flash the full factory image then you should. My understanding is that unlocking the bootloader doesn't void the warranty on Nexus devices.
---------- Post added at 07:00 PM ---------- Previous post was at 06:58 PM ----------
Depending on where you are located Huawei might point you to a local service center rather than have you mail in the device. Huawei contracts with some phone repair chains.

The phone was working OK until suddenly it froze on me. I had to force a reboot and from then on it wasn't able to pass further that the Google logo before restarting again.
I can still get it to enter TWRP and can flash everything but as soon as I try to reatart it, the same happens, it just gets to the Google logo and restarts itself in a boot loop.

Lare2 said:
The phone was working OK until suddenly it froze on me. I had to force a reboot and from then on it wasn't able to pass further that the Google logo before restarting again.
I can still get it to enter TWRP and can flash everything but as soon as I try to reatart it, the same happens, it just gets to the Google logo and restarts itself in a boot loop.
Click to expand...
Click to collapse
Did you try flashing the full factory image with fastboot?

jhs39 said:
Did you try flashing the full factory image with fastboot?
Click to expand...
Click to collapse
Yes I did, using the flash-all.bat as per instructions and it succeeds without issues. But as soon as you restart the device and gets to the Google logo, it restarts again and again and again up to the Google logo and never past from there

I had this very same issue, I ended up using a toolkit and that did away my problems.
SkipSoft toolkit did the job, it's pretty straight forward. You can try pulling your data off the phone through twrp.
Then follow the toolkit to flash stock completely - I would recommend first without wiping userdata, if that doesn't work then with userdata.
For some reason the toolkit worked, and not me manually flashing the images in the correct order and a complete wipe.
Goodluck

TnT_ said:
I had this very same issue, I ended up using a toolkit and that did away my problems.
SkipSoft toolkit did the job, it's pretty straight forward. You can try pulling your data off the phone through twrp.
Then follow the toolkit to flash stock completely - I would recommend first without wiping userdata, if that doesn't work then with userdata.
For some reason the toolkit worked, and not me manually flashing the images in the correct order and a complete wipe.
Goodluck
Click to expand...
Click to collapse
I downloaded the Unified Android Toolkit.
I tried following this instructions
FLASH A STOCK IMAGE BACK TO YOUR DEVICE [FIXES NEARLY ALL PROBLEMS]:
1. Unplug the usb cable
2. Reboot manually to Fastboot Mode [see above for button combination]
3. Plug the usb cable back in
4. From the Toolkit Main Menu select option 9,1 to download/flash a stock firmware
image back to your device. Choose to format userdata and is should fix everything.
Mentioned on this Url
But I can't see and option for 9. When I initially open it it asks me to select the device and then asks me to choose the Android version to go but never see that option 9 mentioned above.
Can you guide me to the steps you followed to fix yours

TnT_ said:
I had this very same issue, I ended up using a toolkit and that did away my problems.
SkipSoft toolkit did the job, it's pretty straight forward. You can try pulling your data off the phone through twrp.
Then follow the toolkit to flash stock completely - I would recommend first without wiping userdata, if that doesn't work then with userdata.
For some reason the toolkit worked, and not me manually flashing the images in the correct order and a complete wipe.
Goodluck
Click to expand...
Click to collapse
The difference I see between the flash-all.bat and using the toolkit is formatting partitions instead of erasing them (including userdata and cache). I realize you are out of the woods now, but others experiencing the bootlooping should try manually fastboot formatting userdata and cache first. @Lare2

v12xke said:
The difference I see between the flash-all.bat and using the toolkit is formatting partitions instead of erasing them (including userdata and cache). I realize you are out of the woods now, but others experiencing the bootlooping should try manually fastboot formatting userdata and cache first. @Lare2
Click to expand...
Click to collapse
Well, for anyone scrolling through here. This is how my device semi-hard bricked (after not booting)
I was flashing PureNexus (I've been using it since I got my 6P in April, it was a standard update to me). I was going from November build to January build, and I thought nothing of it. Next thing I know my phone isn't booting, so I try flashing again. I realize I'm stuck so I backup all the stuff that isn't already backed up, and I wipe everything. Flash stock from my computer. Welp looks like that didn't work. So I go through and format everything before trying again, still. No luck. Vendor refused to flash at that point, so vendor had gotten corrupted in the process ( I kept on getting invalid directory for /vendor - weird right?). Or a string of complex errors in fastboot. I saw something earlier while I was helping someone, about the took. I usually like doing things myself, but I used it as a last resort. I flashed back to stock and everything worked. Then I flashed PureNexus again, and had to do the toolkit all over again. Because my phone absolutely refused to boot on December PureNexus for the angler.
TL;DR : I would not recommend flashing the December update of PureNexus at ALL

I have been trying to get it to work with all the suggestions mentioned here sin my last post. No luck at all. I'm in the process to call the warranty support number and will se how it goes.
Even though I have been unable to get it working this has been an amazing learning experience. I got to try several solutions that made me gain more knowledge that I know will be useful in the future.
I'll report back to see how it went with the warranty guys.
Thank you all

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