okay so after trying some other options i was able to solve this problem, here is the how to in case this has happened to anyone else. my original post is below the how to.
1.flash the sbf that returns your defy to stock eclair using a different T-Mobile sim, after it is done flashing you will seem to still have the problem, except it will say no sim emergency calls only.
2.power off the device and install your original sim from T-mobile.
3.reboot the device and you will not be prompted to setup motoblur, because you device is in soft brick limbo still, but you will have laggy touch responses, be patient with your device as you navigate to settings>privacy>factory reset and confirm. ( this process will take much longer than usual and the progress bar will not show any progress but it will shutdown and reboot as it normally would with a factory reset)
4. you will now be prompted to setup your motoblur account ( if you are not restart the steps until this happens, if it does not happen your device did not actually do a factory reset you will need to try again until it does ask you to setup blur, this is your sign from the moto gods that your device is no longer in softbrick limbo)
5. setup your blur account ( you will still have no recovery menu at this time so don't try and check or you will have to start back over at step one)
6. now navigate to settings>about phone> check for updates
7.download and install the update to froyo ( durring downloading you phone may shut off several times, however if you reboot it will automatically pick up the update where it left off as if your device never powered off to begin with)
8. once you have installed the update you device will be back to froyo stock and your recovery partition will no longer be bricked
9. enjoy your defy once again, and be more careful with your device in future ROOT mods and tweaks, cheers!
10. If this helped you recover your device please thank me for this solution.
okay so i am new to posting on XDA and i will try to organize my problem as best as possible, but i may need much guidance on if i am posting in the proper forum.
here are my details of my device and the problems i am facing with my device currently.
Motorola Defy
MB525
T-mobile US
stock Froyo rom 2.2.1 ROOTED overclocked with milestone overclock to 1224 mhz @ 85% voltage /V6 SUPERCHARGER SCRIPTS. MODDED BUILD.PROP TO REFLECT THE MAX HSUPA CATEGORY 34/MAX HSDPA CATEGORY 36/ GPRS CLASS 10/ HSXPA=2/RO.RIL.VIDEO_MODES=TRUE EVERYTHING ELSE IN BUILD.PROP WAS STOCK EXCEPT WHAT THE V6 SUPERCHARGER SCRIPTS CHANGES. I was running a custom bootscreen that i placed in the location of the old one using ES file explorer with root browsing rights, i had defy Recovery installed but only used it basically as a system restore app ( context of previous statement is relating to system restore if you were talking about a windows machine) used Avast anti virus as root installation w/antitheft installed used system tuner to manage startups down to core services or other services i did want to run at boot i.e. stuff like facebook and weather channel.
DEVICE WAS ALSO SUBSIDY UNLOCKED
SBF started with and reflashed to try to correct problems was JORDN_U3_6.36.0_SIGNED_USAJRDNTMOB1B4B5DE1028.OR_JORDANTMO_PO22_HWp3_SERVICE1FF.sbf
****NOW TO THE PROBLEMS****
I was starting to think that maybe the v6 supercharger scripts were not really doing anything performance wise for me as it would disable my overclock settings at boot and i would have to manually invoke them after everything had requested its SU rights at boot. so i decided to get rid of the v6 supercharger scripts and all other softwares pertaining to managing and running the scripts, I decided the best way to do this was to do as i had always done in the past when wanting to re-tweak my phone and use the stock recovery to start fresh with 0 tweaks and only apply the ones i wanted after restoring to stock, when i used the stock recovery this time it didn't work, i booted the phone back up after wiping data/ factory data reset and to my surprise the recovery did nothing but delete the SU.apk the custom boot was still in tact, everything else listed above still in tact except for the phone was obviously throwing errors left and right because there was no SU for apps to request permissions from, so i reinstalled the SU.apk just to make sure i didn't have to deal with the device being slow while restarting the process of doing a full wipe. this time i used the DefySDrecovery.apk i mentioned above to do the same steps and while adding wiping the dalvik cache after wiping data and before invoking the recovery, it then gave me the same error i have always gotten when wiping the cache which is
e:\ cant mount cache partition
e:\ cant find /recovery/caller
e:\ cant find/recovery/cache
(this has never caused problems with the device once recovery was finished)
this time however I was only able to boot(loop) to the moto logo
so i reflashed The above mentioned SBF and the device booted normally i went through the entire setup like it was a new device with blur and google and it finished. when I got to the home screen it was frozen and would not respond to touch it also showed to have no cellular signal, i turned it of and back on and it made me go through blur and gmail setup again, went to home screen same thing frozen with no signal.
i reflashed the SBF again thinking maybe something went wrong as they do sometimes with RSD yet still finished and passed on everything
the above description repeated except for this time it responded to touch for the first few seconds before it froze completely ( oops! sorry one detail to add when i say it froze i mean froze like would respond to nothing, touch, hardware buttons, nothing) i had to pull the battery in both instances to try and start over, after many attempts of getting in the phone and trying to turn on usb debugging before it froze i finally was able to complete the finger olympics and get usb debugging turned on, i was able to root it using superoneclick so that i could have a look at the logcat in ADB. now in my experiences with ADB normally when you run a logcat command it will print to the screen for about two to three hundred lines and then slow down and only print one to six lines at a time as the server is calling actions when i ran a logcat on this device it runs two to three hundred lines slows down and then runs lines until you close the ADB window i let it run a logcat overnight and it was still running lines the next morning with no sign of stopping where you could freeze the window and read over all the crap it was calling to action, looking at the device durring this process i saw force close windows a few times saying the com.android.process has stopped but the home screen never crashed and the phone didn't do a random reboot. so to sum it all up ( so sorry for the lengthy explaination but i wanted you to have the whole problem fully explained in hopes you wouldn't have to ask for more detail)
it freezes and has no service with my T-mobile sim in it ( if i put my at&t sim in it has service but still freezes)
flashing a new SBF doesn't fix the problem as it should
and there is no way to enter the Recovery Menu now its gone, non existant, cant find it, cant fix it, i'm F***** right now Please help if you know how, and if i totally screwed the phone i'm cool with you saying so but it can still be in a respectful way i already feel like an idiot for not being able to correct this with all the knowledge i have of this phone, a negative attitude insinuated is not going to help me in either direction, thanks in advance for any help you may be able to provide.
Well this is my 1st post so first of all hey everyone
I just spent a week in Amsterdam and my phone restarted twice, different times different days and I dont remember what I was doing with it back then.
But as I landed back home I put the phone back from "Airplane Mode" and went on to toggle "Cellular Data" on.
The second I pressed the cellular data shortcut on my the phone restarted itself but this time whenever it would finish the screen would be on but fully black and sometimes it'll show battery precentage at the top but then will restart again in an infinite loop.
Sometimes it'll pop up the "Optimizing Apps" window and will go through all 24, upon finishing it will restart once more and do the same.
I tried using the bootloader and it worked (the bootloader that is) but the phone would do the same thing even after Rebooting from there or shutting down from there and then turning back on.
I contacted tech support on chat but they couldnt help past telling me to go to bootloader and reboot, said I should factory wipe when it failed.
Also tried wiping cache but to no avail.
I have no backup of my phone (wanted to do one before the flight but got lazy and I suck for not doing one sooner) since probably October and google doesnt backup my contacts properly for some unknown reason.
I already downloaded Android Studio with everything included for me to try using adb to sideload stock without wiping but its my first time and I couldnt get it to do anything at all...
I already got the official stock .gz file from the motorola website.
Anyway here are the specs to my phone:
XT1575
Everything is stock. didn't root or change recovery once in my life.
Was fully updated and had plenty of drive space (I have almost 128GB with the 64GB version + 64GB SD)
I'm really lost here so help will be very appreciated.
Thanks in advance,
-Noam
Start with a full wipe and if that doesn't work flash the stock image. Not sure what your question is though as you never really say. Once fixed I would unlock and make a backup so you don't have to deal with this again.
lafester said:
Start with a full wipe and if that doesn't work flash the stock image. Not sure what your question is though as you never really say. Once fixed I would unlock and make a backup so you don't have to deal with this again.
Click to expand...
Click to collapse
The thing I pretty much want to know is if theres a way to either backup the phone now with it connected to the computer while in bootloader or recovery. or a way to flash the stock rom without wiping which I read someone did with his tablet. I cant post source normally because I'm a new user so here it is but change spaces to dots: schnouki net/posts/2014/08/13/flashing-a-stock-android-image-without-wiping-user-data/
Also while in recovery I noticed 2 options under wipe: 1. userdata only. 2. userdata+(insert something I dont remember here) and I was wondering what gets deleted in both? if I delete only userdata what data will remain? something helpful?
Sure you can try flashing without wiping data but being locked I personally wouldn't risk it. No idea about backing up in your state... somewhere I remember a thread on backing up without root try searching in q&a.
lafester said:
Sure you can try flashing without wiping data but being locked I personally wouldn't risk it. No idea about backing up in your state... somewhere I remember a thread on backing up without root try searching in q&a.
Click to expand...
Click to collapse
Out of curiosity why shouldnt I try flashing with no wipe if ill lose the data anyway? worst case wont I just have to wipe after it fails and flash again?
And I will try thank you
Do you have any knowledge about the 2 wipe options?
Thanks in advance
Well I tried turning the phone on and it took a couple of minutes before loading to a fresh start. It apparently wiped itself on its own. Managed to restore almost everything.
Anyhow the phone takes too long to boot now. Was even stuck at boot and I had to restart it.
Anyway to fix my software? Or at least check for corruption?
Sent from my XT1575 using XDA-Developers mobile app
Hello all,
I have a Nexus 6P, stock, rooted, with Xposed installed. The phone is completely functional for the better part of its life time since I bought it at release -probably first or second batch- (except for random reboots once daily on average, deemed by my investigation and exhausting all options to be a hardware issue or Xposed related).
Today, out of nowhere, the phone randomly rebooted itself and surprisingly it launched the "Android is starting..." dialogue which, if I'm not mistaken, optimize apps for ART. The battery was at 19% before it randomly rebooted, so when it started that optimize apps it went down to 0 (I assume) and it turned off. The charger wasn't connected correctly so that happened. Now the phone keeps restarting itself up to before it gives me the boot up decryption phase of the Data partition and reboots again. I assumed it can't decrypt Data for some reason, so I launched TWRP recovery to try and decrypt data and take a backup copy of my Titanium Backup folder on storage... Unfortunately, TWRP reports "failed to decrypt data" even though I'm 100% positive that the pattern is correct because I'm literally inputting it almost 10-20 times a day for the past two years...
Note: there seems to be a red blinking LED in the top left corner of the the phone. I never even knew this existed.
WHAT I WILL DO
I'll reflash everything system-wise.. I'm ok with that. I'll reflash the factory images, root it, install Xposed, no problem.
WHAT I NEED HELP WITH
I need to extract some folders from my phone storage, namely the Titanium Backup folder. I know the pattern protection of the encryption.
How do I go about doing this?
UPDATE:
Help is urgently needed now indeed: The phone doesn't even turn on to bootloader mode anymore now. It was able to, just half an hour ago. Now all I see it the red blinking LED.
UPDATE2: https://support.google.com/nexus/troubleshooter/3337561?hl=en-GB#ts=3337942
I'll try in 30 minutes.
Meanwhile, please help me with my original problem; extracting data.
I was thinking, if I boot into bootloader mode, can I use adb to pull any folder? If so, will that work in my case with decryption fails or Data partition doesn't seem to mount correctly?
Relevent:
Reviewing some other threads:
TWRP: 3.0.2-2
Bootloader: UNLOCKED
I did NOT upgrade to Android 7.0 nor was I planning to, until Xposed is available.
I did NOT flash anything **new** recently. However, Installed an Xposed module yesterday which caused a bootloop. I rebooted into TWRP, uninstalled Xposed, rebooted into system (which looped once, out of the ordinary) and I uninstalled that module, back to TWRP installed Xposed, and rebooted back into system. It worked for 12 hours and then what I wrote this post for happened as stated above.
UPDATE3:
15 minutes into charging... NOT EVEN A RED BLINKING LED ANYMORE.
Last? UPDATE:
Almost 1 and a half hour into charging and there is no longer ANYTHING. Is it hard-bricked now?
How the **** is this possible? I'm very much capable of solving any sof-brick but not a hard-brick...
Thats a really crappy scenario. Im a little busy right now (not that I can get you out of this regardless) but I sort of skimmed through your post. Are you able to connect adb? If so you might be able to use "adb pull" to get that data.
On my 6p TB is located at:
/storage/emulated/0/TitaniumBackup/
Itll probably be the same location on your phone. Good Luck
KLit75 said:
Thats a really crappy scenario. Im a little busy right now (not that I can get you out of this regardless) but I sort of skimmed through your post. Are you able to connect adb? If so you might be able to use "adb pull" to get that data.
On my 6p TB is located at:
/storage/emulated/0/TitaniumBackup/
Itll probably be the same location on your phone. Good Luck
Click to expand...
Click to collapse
I was indeed able to connect to a PC after I saw the problem (the bootloop essentially)... But I didn't at the time as I didn't have a plan of action as to how to get my data, so I turned it off. After sometime, I couldn't do anything with the phone... Not able to boot into bootloader, not recovery, the phone is essentially not turning on to anything, not even the splash screen; like a hard-brick. I'm not sure if this indeed is a hard brick as I've never seen any.. and don't currently know what to try next.
Is the LED still showing? if so, do the bootloader boot combo, and see if fastboot devices gets a response in a command prompt - or terminal if you're a linux guy.
if so, you can boot to twrp, decrypt data - try default_password -, and browse the phone's files from your computer's file browser, the phone will show up as Nexus 6P. That's my suggestion, wish you luck.
TnT_ said:
Is the LED still showing? if so, do the bootloader boot combo, and see if fastboot devices gets a response in a command prompt - or terminal if you're a linux guy.
if so, you can boot to twrp, decrypt data - try default_password -, and browse the phone's files from your computer's file browser, the phone will show up as Nexus 6P. That's my suggestion, wish you luck.
Click to expand...
Click to collapse
I honestly declared it hard-bricked.
Will Fastboot show any devices if the phone didn't show bootloader screen?
I'll try again today.
Update:
Didn't work.
check out my post
[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexus-6p/general/guide-fool-noob-proof-to-clean-installs-t3518311
This dreadful error: "Verification Failed, Unable to restart your device. The Integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data."
And a "Reset" button.
Nothing seems to have caused this. One minute phone was sitting on my desk happily, the next it rebooted itself (I assume) and this error appeared. Given that I'm not interested in losing my data I haven't pressed the factory reset button... because that's just silly.
- Phone is S5 Neo (W version). Rooted (CF-autoroot) with TWRP installed. Has been this way for months.
- Software updates are turned off
- ADB is disabled but I can access terminal using TWRP.
- Data partition is encrypted
What I've done so far:
- Backed up my Data partition using DD; but as it's encrypted I can't access the data
- Attempted terminal "twrp decrypt mypassword" using the password I used to unlock encryption at boot (result: "Failed to decrypt data")
What do I do now? Is there any way to decrypt this partition on my PC (I have linux and windows available to me) to at least rescue my data?
Thanks in advance...
I just had the same thing happen to me with the exact same model with the exact same settings as well today about a couple hours ago EXCEPT I never rooted the phone like yourself. So it isn't developer mode or anything like that. That can be ruled out. It's such f**king BS!
I heard rumors about nonsense like this years ago and the only way to supposedly fix the problem is to send the phone into samsung where they fiddle with the phone, never fix it, keep it (for whatever reason ??), and send a new phone back out IF we fall into warranty.
With all the corruption in the world and the shady happenings with government and businesses, why in the hell would any logical person send their phone back in to an OEM after it's been used? I'm a good person and come from a good family and all that, but ever since I had my information stolen from me a little over 5 years ago I really don't want to send my phone in and have my life in shambles again. No damn chance!
I'm thinking about calling in but I want all my info! I have important work related documents on here!
Only thing I am going to ask you is what software did you use to back it up (DD?)
Do these exact steps, Do not miss.
1. Reboot to recovery.
2. Do a data wipe (WIPE>FORMAT DATA) And Say "Yes"
3.Go to Reboot and Reboot back to recovery.
4.Download DM Verify Disabler https://build.nethunter.com/android-tools/no-verity-opt-encrypt/, Get the latest.
5.Copy in to the phone and flash it.
6.Go to Reboot and Reboot back to recovery.
7.Now Flash any rom as you wish.
8.Make Sure to Wipe Dalvik, Cache after.
Enjoy!!
Shameera_N said:
Do these exact steps, Do not miss.
1. Reboot to recovery.
2. Do a data wipe (WIPE>FORMAT DATA) And Say "Yes"
3.Go to Reboot and Reboot back to recovery.
4.Download DM Verify Disabler, Get the latest.
5.Copy in to the phone and flash it.
6.Go to Reboot and Reboot back to recovery.
7.Now Flash any rom as you wish.
8.Make Sure to Wipe Dalvik, Cache after.
Enjoy!!
Click to expand...
Click to collapse
Shameera_N you sound pretty smart....but why didn't you read the comments we posted and actually try and answer what we asked? WE DO NOT WANT TO WIPE OUR DATA and there is no way that wiping is part of the solution.
For this do we need a rooted phone?
This happened to me on a completely stock SM-G903F with data encryption enabled. So it has nothing to do with custom recoveries or root. It seems that the encryption method is flawed.
I don't think there is a way to get out of this one, so I wiped it. I don't have all that much stuff on the internal SD of my phone except for apps and messages. Your SD card won't get formatted, so if you save your photos there, they should be safe.
It's a pain, but this means you can't really safely use data encryption unless you regularly take backups (and even then, factory resetting a phone is no fun), even if errors like this only happen once in a blue moon.
This happend to me on my SM-G920P. I just odin flashed stock rom and back to new no data wipe or loss.
Same problem with a samsung galaxy s5 neo. Envrypted partition, Stock firmware, no root and updated.
At least i understood what caused it. I was listening to a youtube video. While the video was playing, i pressed the power button and switched off. When i switched on, i could not start android anymore
Shameera_N said:
Do these exact steps, Do not miss.
1. Reboot to recovery.
2. Do a data wipe (WIPE>FORMAT DATA) And Say "Yes"
3.Go to Reboot and Reboot back to recovery.
4.Download DM Verify Disabler https://build.nethunter.com/android-tools/no-verity-opt-encrypt/, Get the latest.
5.Copy in to the phone and flash it.
6.Go to Reboot and Reboot back to recovery.
7.Now Flash any rom as you wish.
8.Make Sure to Wipe Dalvik, Cache after.
Enjoy!!
Click to expand...
Click to collapse
Thanks for the link, do you know who built this? Need update for 7.0...
githyanki said:
Thanks for the link, do you know who built this? Need update for 7.0...
Click to expand...
Click to collapse
You can use same for 7.x.x Use latest version from the link
I know this isn't exactly related to the issue in this thread, but I'm not having much luck elsewhere.
My completely stock J3 (2017 model, J327A) was hit with verification failed. From what I've seen, I can fix my issue merely by flashing the original OS back into my phone. I have the files and programs I need to do this.
But I can't get the phone into download mode. I can boot it up to the warning screen. It tells me to press VolUp to enter download mode, or VolDn to cancel and restart the phone. However, neither pressing nor holding either of them does anything. I know they aren't broken, as I can boot into recovery mode as well, which requires VolUp. The buttons just don't respond when I'm at the warning screen. Is this something I can work around, or something I have to be patient with, or something I can't fix?
(Data partition is encrypted, though. Not sure if that will affect this.)
Simply long press the Shut Down Button !!!!!!!!
I simply pressed the shut down button and restarted my phone and it worked !!!!!
A light at the end of the factory reset error tunnel!
Well I had an encounter with that dreaded 'factory reset losing all data' message and I'm telling you I was furious! Anyways, after a few seconds of gasping and wondering how the heck am I gonna retrieve all of my data and stuff, the thought came to me to try some 'old school tactics' which involved removing the battery and pressing the power button to drain any residual power remaining on the phone's circuit board and then try powering up after reinserting the battery. Low and behold, the phone booted up with no issues at all. I was able to log in and access my phone as if nothing happened. It's funny how that one message can just change your whole outlook on things. I just hope that folks out there will try this and perhaps it will work for them instead of losing all their data and jumping through all sorts of hoops. Most importantly, BACK THAT THING UP!! You never know what next will come out of the woods at any given time!
Resolved error without loss of data
Hi,
I came across this problem today as soon as I woke up today, but was able to solve it.
I have a Samsung J5 prime phone and did the following steps:
Why this occurs?
The system thinks you wish to root your phone.
How to solve this?
1) when you have the verification failed screen, press "power" button + "Home" button + "Volume Down" button.
you'll be presented with a new screen which gives you 2 options-first, installing a custom OS and second, canceling it.
NOTE: I did not want to root my phone.
2) Hence, I chose the 2nd option and after that, my phone restarted with no loss of data.
Hope this helps!
if u can boot into recovery, go ahead and wipe cache/dalvik cache and reboot
this worked for me without any loss (i used twrp recovery to wipe and my device is SM_C900F /INS variant)
zay2046 said:
This happend to me on my SM-G920P. I just odin flashed stock rom and back to new no data wipe or loss.
Click to expand...
Click to collapse
Sir, can you guide me a bit further ? it just happened with my J7 prime and i don't want to loose data.
Same Problemo
I Jst Had The Same Issue, Bit I Fixed It Straight Away, Jst By Restarting It, Hold Both "Up & Down Volume", "Power Button" and "Home Button", And It Restarted & Worked
This works!
This worked with my daughters J7. THANK YOU!
udit_e said:
Hi,
I came across this problem today as soon as I woke up today, but was able to solve it.
I have a Samsung J5 prime phone and did the following steps:
Why this occurs?
The system thinks you wish to root your phone.
How to solve this?
1) when you have the verification failed screen, press "power" button + "Home" button + "Volume Down" button.
you'll be presented with a new screen which gives you 2 options-first, installing a custom OS and second, canceling it.
NOTE: I did not want to root my phone.
2) Hence, I chose the 2nd option and after that, my phone restarted with no loss of data.
Hope this helps!
Click to expand...
Click to collapse
Shameera_N said:
Do these exact steps, Do not miss.
1. Reboot to recovery.
2. Do a data wipe (WIPE>FORMAT DATA) And Say "Yes"
3.Go to Reboot and Reboot back to recovery.
4.Download DM Verify Disabler https://build.nethunter.com/android-tools/no-verity-opt-encrypt/, Get the latest.
5.Copy in to the phone and flash it.
6.Go to Reboot and Reboot back to recovery.
7.Now Flash any rom as you wish.
8.Make Sure to Wipe Dalvik, Cache after.
Enjoy!!
Click to expand...
Click to collapse
Came here to thank you with all my heart, this worked. I've been using TWRP for years on several phones, and I never knew that Wipe > Format Data did something different than Wipe > Advenced Wipe > Selecting Data > Swiping. I thought it served the same purpose. I don't know if the script did anything, though (because I used it before, but without formating data, and it didn't help at all).
Anyway, thank you so much!
how to remove Verification Failed or root in the TWRP file manager without losing data
Yes this post is correctly dated. I've had this device a LOOOONNNGGG time.
The device has been rooted since shortly after I bought it new years ago. I've had very few problems since... which is why it's never been replaced.
I believe I have the stock ROM, sorry it's been a while.
When I start the device it gets stuck at the splash screen with the sprint logo.
I can get the device to "download mode" but I don't know what to do once there and I'm not sure I can do anything from here.
I can get the device to "android system recovery."
I know I installed TWRP when I rooted and installed the rooted ROM but when I boot to recovery it doesn't go there.
I've wiped the "cache partition" but the problem remained. I'm not sure what else to do from here and still be able to salvage data.
I'm trying to salvage the data on the internal storage. I'm pretty sure I could successfully "wipe data/ factory reset" and get it to "function" again but that's not the priority. I'm going to replace it regardless of success or failure. Data recovery is the priority here. (pictures and videos of my young children as well as less important stuff like contacts.)
I have an old laptop with an old version of ubuntu I can use or a newer one with windows 7 to work with. I mention this in case it makes this easier to help?
Thank you very much if you try to take a stab at this or refer someone that might!
Update:
So I managed to install TWRP via Odin.
I booted to this recovery and my data partition appears to be empty?
When I try to back up I get the error message "unable to mount '/data'"
I tried doing a wipe, not one of the fancy extra options ones just the regular wipe and it failed.
Any guidance will be extremely appreciated.
Edit:
So I've come to the conclusion that the data isn't accessible because of encryption and my pass code. Is there any way to enter it via recovery and access this info?
Is anybody out there?
Edit 2:
I hope this helps someone someday. I haven't solved the problem but I think I'm making progress.
First I had an old version of TWRP. I installed the latest for my device and tried backing up again. I'm not sure but I think it's working. TWRP dosen't seem to need my password for the backup. I imagine I'll just need it to access the data later.
Edit 3:
No sooner did I save the last edit and my backup failed.
Process ended with error : 255