Related
I'm currently stuck at the s5 active logo screen and then it boots into recovery. I've tried flashing the full odin.rar (yes I extracted it) and it fails everytime. I get the message "Sw REV CHeck Fail: [aboot]Fused 2> Binary 1. I've already tried wiping the data from the recovery menu. Nothing is working.
We need more info. What were you attempting to do and from what ROM. Are you sure you are using the proper ROM 900 or 870?
I was attempting to downgrade back to stock from 5.0 and hit the stock kernel instead of the firmware accidently when in odin. And yes I am absolutely sure i'm using the 870 rom.
Edit: What if I use a stock img and a PIT file for the phone? OR is it because I need a 5.0 lollipop firmware to flash through odin?
Edit number 2: okay I'm stupid, im on G870AUCU2BOF3. I'm going to have to reflash the of3 zip aren't I?
Okay so I found the OF3 cfg on another thread and was able to load it and flash it and get my phone working! Now, the next question is can I root in my situation or downgrade or am I just stuck?
Edit: Going to wait for a possible root! Mod can close this thread.
if you loaded the 2400258.cfg you probably loaded the OF3 bootloader as well and now you can't go back. No root at this time and it doesn't look good for the future.
Cloudsdabomb said:
Okay so I found the OF3 cfg on another thread and was able to load it and flash it and get my phone working! Now, the next question is can I root in my situation or downgrade or am I just stuck?
Edit: Going to wait for a possible root! Mod can close this thread.
Click to expand...
Click to collapse
At command prompt type without the qoutes.
"getprop ro.bootloader"
Then paste output.
Sent from my SAMSUNG-SM-G870A using Tapatalk
If you took the of3 ota or are otherwise on the of3 bootloader your stuck there....no downgrade or root as of this time.
Me too
I am in a similar situation. Saturday I was on a rooted 4.4.2, flashed a stock unrooted 4.4.2 with Odin (G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5), let AT&T update me to 4.4.4, installed the old kernel with Odin (G870A_NE4_Stock_Kernel.tar.md5), rooted with towelroot, installed the new kernel with Odin (G870A_OA1_Stock_Kernel.tar.md5), updated to 5.0 with Odin and it retained root. However, certain things such as XPosed didn't work and I really really hated the white notification drawer so I just want to go back. I tried flashing the stock 4.4.2 in Odin again and it said success. It restarts and seems to be working but gets stuck on the AT&T logo. Now if I restart it always sticks on the AT&T logo even when I flash again. I don't know what else to try. A different file? Is there a way to go back to KitKat?
Update: I got into recovery mode (I kept trying vol up, vol down, power but it's actually vol up, home, power). I wiped the cache and did a data reset and restarted the phone. It worked! I'm excited to have a black notification screen again
pgross41 said:
I am in a similar situation. Saturday I was on a rooted 4.4.2, flashed a stock unrooted 4.4.2 with Odin (G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5), let AT&T update me to 4.4.4, installed the old kernel with Odin (G870A_NE4_Stock_Kernel.tar.md5), rooted with towelroot, installed the new kernel with Odin (G870A_OA1_Stock_Kernel.tar.md5), updated to 5.0 with Odin and it retained root. However, certain things such as XPosed didn't work and I really really hated the white notification drawer so I just want to go back. I tried flashing the stock 4.4.2 in Odin again and it said success. It restarts and seems to be working but gets stuck on the AT&T logo. Now if I restart it always sticks on the AT&T logo even when I flash again. I don't know what else to try. A different file? Is there a way to go back to KitKat?
Update: I got into recovery mode (I kept trying vol up, vol down, power but it's actually vol up, home, power). I wiped the cache and did a data reset and restarted the phone. It worked! I'm excited to have a black notification screen again
Click to expand...
Click to collapse
How long did you have to wait for your phone to boot all the way up from the ATT logo? Mine is doing exactly the same thing and I've flashed all kinds of kernels via odin and heimdall with no affect. None of the various fixes I've found have helped, including trying to re-apply the OTA file (system just won't do it). All I wanted was to unroot. Awesome.
The first boot can take a while but if it lasts more than 10 minutes it's probably not going to happen. I've gotten it stuck there twice since my last post and I'm always able to salvage it by going into recovery mode (vol up, home, power while powered off). Wipe the cache and data reset and it should be a fresh start like out of the box new.
Hm. So the only real two options are take it in to AT&T and hope they have the full stock G870AUCU2BOF3 image to flash over (since Samsung locked down their bootloader so hard, so downgrading is impossible :good: ) or hope they release G870AUCU2BOF3 on SamMobile/Kies/Smart Switch. This is like the new hard brick... potentially it's salvageable but the company (I'm guessing AT&T here since this is an AT&T exclusive phone) is just screwing us. Guess I'll try the walk of shame to AT&T. Or maybe putting in a claim like that one person did, get a whole new phone because of a mysterious cut on the rear panel seal...
Alright, took it in to AT&T and sure enough they had the full 5.0 image available so after signing a no-return data waiver (didn't even confirm my AT&T account or ask for any ID) the tech took my phone in the back and flashed it back to stock. First boot still showed the "custom" with unlocked padlock on the boot screen but after I rebooted it, I guess it updated the bootloader because it was back to normal.
No more root and he confirmed there's no way to go back to 4.4 once you go up to 5.0, so if you want root, I'd suggest staying away from 5.0. At least now I can use my phone again. Just thought I'd post this up in case anyone wasn't sure if AT&T would actually be able to reflash stock 5.0 and at the very least get your phone working again... enough to put on ebay and get a Moto or some other brand that doesn't lock down the bootloader so hard.
Edit: note the first boot will take a few minutes but I knew it worked when there was a quick vibe and the notification light went from pulsing blue to off. Maybe 4-5 minutes.
retro486 said:
Alright, took it in to AT&T and sure enough they had the full 5.0 image available so after signing a no-return data waiver (didn't even confirm my AT&T account or ask for any ID) the tech took my phone in the back and flashed it back to stock. First boot still showed the "custom" with unlocked padlock on the boot screen but after I rebooted it, I guess it updated the bootloader because it was back to normal.
No more root and he confirmed there's no way to go back to 4.4 once you go up to 5.0, so if you want root, I'd suggest staying away from 5.0. At least now I can use my phone again. Just thought I'd post this up in case anyone wasn't sure if AT&T would actually be able to reflash stock 5.0 and at the very least get your phone working again... enough to put on ebay and get a Moto or some other brand that doesn't lock down the bootloader so hard.
Edit: note the first boot will take a few minutes but I knew it worked when there was a quick vibe and the notification light went from pulsing blue to off. Maybe 4-5 minutes.
Click to expand...
Click to collapse
It's not Samsung that locks down the bootloader, it's AT&T. the T-Mobile Version doesn't have a locked bootloader and is easily rooted . Just have to SIM unlock it and you can use T-Mobile phone on AT&T network.
Delete
Hey guys!
So I really wanted to try out Xposed and get some modules working on my phone. So I unlocked the bootloader by following the directions from Motorola. I then used the moto x 2014 multitool to install twrp recovery and to root (#2 and #7).
I then installed the Xposed apk and flashed the zip file. All Seemed well until I started getting massive amounts of lag if my phone was on for more than 2 minutes. I thought it might be Xposed so I uninstalled it (and the 2 modules that I had installed -- youtube ad blocker and xmultiwindow). That didn't fix it though. So then I thought it might be supersu, so I updated that. That didn't work either.
So then I went back to the multitool and I chose #5... and now it won't boot. It shows the "warning bootloader unlocked" screen and then shows the motorola boot screen for 20 seconds, then shuts off. I also can't boot into fastboot by pressing down the power and volume down buttons.
Any help would be super appreciated!! I'm really not experienced with this stuff but, I had a nexus s with cyanogenmod on it which I loved and then I rooted my note 4 but that's it...
Thank you!!!
EDIT: I can get into fastboot mode, so far I just tried to select 'factory' and it went through the same "bootloader unlocked" then motorola boot for 20 seconds before shutting off...
Maybe try getting to fastboot, selecting recovery, and then wiping cache and dalvik
dictionary said:
Maybe try getting to fastboot, selecting recovery, and then wiping cache and dalvik
Click to expand...
Click to collapse
Ok I actually just got into fastboot and did a factory reset. It put me back on 4.4.4 so I'm updating to 5.1 right now.
What is the proper method to installing Xposed on this phone? I'd really like the multiwindow and adblock modules... but the intense lag that would freeze my phone after 2 minutes was just too much.
HinaPanda said:
Ok I actually just got into fastboot and did a factory reset. It put me back on 4.4.4 so I'm updating to 5.1 right now.
What is the proper method to installing Xposed on this phone? I'd really like the multiwindow and adblock modules... but the intense lag that would freeze my phone after 2 minutes was just too much.
Click to expand...
Click to collapse
For that I don't have an answer. I don't really have a need for Xposed much anymore, so I haven't been following. Sorry
HinaPanda said:
Ok I actually just got into fastboot and did a factory reset. It put me back on 4.4.4 so I'm updating to 5.1 right now.
What is the proper method to installing Xposed on this phone? I'd really like the multiwindow and adblock modules... but the intense lag that would freeze my phone after 2 minutes was just too much.
Click to expand...
Click to collapse
If you're on 5.1:
First, go here http://forum.xda-developers.com/showthread.php?t=3034811
You will need to download the XposedInstaller_3.0_alpha4.apk and the Xposed-v74-sdk22-arm.zip. It wouldn't hurt to go ahead and download the xposed-uninstaller-20150831-arm.zip either, in case you have problems.
Now you need TWRP. Flash it using fastboot by typing fastboot flash recovery (name of recovery image file.img) from a terminal. Or download TWRP Manager from the Play Store and flash it from there.
Finally, flash the Xposed-v74-sdk22-arm.zip in TWRP. Reboot and install the XposedInstaller_3.0_alpha4.apk.
If you already have root, install TWRP from the Play Store. Otherwise, install it by using fastboot.
dictionary said:
For that I don't have an answer. I don't really have a need for Xposed much anymore, so I haven't been following. Sorry
Click to expand...
Click to collapse
Care to share why?
Phoenix232 said:
If you already have root, install TWRP from the Play Store. Otherwise, install it by using fastboot.
Care to share why?
Click to expand...
Click to collapse
I'd used it a lot when I had my htc m7 with sense, and lg g3 with stock. All I used it for were really mods to make it more AOSP like. There were some features that I miss, like FakeWifi, and App Settings, to name two, but overall with AOSP ROMs out, I haven't had as much desire.
Ok... so the update bricked the phone even more I didn't see the threads that said to not do the OTA update from 4.4.4.
I connect it to the computer and see the qhsusb_bulk. I installed the drivers and now I see the qualcomm 9008. I tried using a couple of blankflash files to fix it, but none of them work. Even ones that say they're for the moto x 2014. Is there anything I can do? I can't get it into fastboot mode... I was able to but then I don't know what happened and now I can't.
Can I send it into motorola for a warranty repair? I have a pure edition and I live in the US. I don't know if unlocking the bootloader and rooting will cause motorola to not repair it.
HinaPanda said:
I can't get it into fastboot mode... I was able to but then I don't know what happened and now I can't.
Click to expand...
Click to collapse
Sometimes when your phone is messed up, it can take quite a while for the bootloader to start. If the phone is off, hold down the volume down/power button combo for a long time, like 20-30 seconds before releasing them. Then wait several seconds for the bootloader screen to appear, be patient. If the phone starts to boot, hold the vol down/power combo until the phone shuts off, continue holding for 15-30 seconds and then release, again wait a long time for the bootloader screen to appear. I don't have anything else for you but know that many times I've caused myself grief by not being patient getting into the bootloader/fastboot mode when a problem has arisen!
mikeoswego said:
Sometimes when your phone is messed up, it can take quite a while for the bootloader to start. If the phone is off, hold down the volume down/power button combo for a long time, like 20-30 seconds before releasing them. Then wait several seconds for the bootloader screen to appear, be patient. If the phone starts to boot, hold the vol down/power combo until the phone shuts off, continue holding for 15-30 seconds and then release, again wait a long time for the bootloader screen to appear. I don't have anything else for you but know that many times I've caused myself grief by not being patient getting into the bootloader/fastboot mode when a problem has arisen!
Click to expand...
Click to collapse
Thank you! But I actually did try holding down the power button alone and also the power + vol down for like 2 minutes or 30 seconds, etc. The 2 minutes worked the first time, but now it won't It just blinks a green light. Does that mean it's out of battery? I left it plugged into a wall charger overnight though.. how can I tell it's charging?
It sounds like you have a hard brick. Only way to fix it is to send it to a repair center.
Sent from my XT1095 using Tapatalk
Yeah.. I just called motorola and the rep said they had to check on the unlocked bootloader voiding warranty thing. I told him that because I have the pure edition phone, it shouldn't void the warranty. Plus, it's bricked because of the OTA update from 4.4.4, which I believe is motorola's fault.
Does anyone have any link to a motorola statement saying that unlocking the bootloader on the pure edition does not void warranty? The rep said they'd call me back tomorrow. I tried searching on the 'netz but didn't find much.
Pure edition = developer edition, right?
HinaPanda said:
Yeah.. I just called motorola and the rep said they had to check on the unlocked bootloader voiding warranty thing. I told him that because I have the pure edition phone, it shouldn't void the warranty. Plus, it's bricked because of the OTA update from 4.4.4, which I believe is motorola's fault.
Does anyone have any link to a motorola statement saying that unlocking the bootloader on the pure edition does not void warranty? The rep said they'd call me back tomorrow. I tried searching on the 'netz but didn't find much.
Pure edition = developer edition, right?
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x-2014/general/unlocking-bootloader-moto-x-pure-t3004779
Looks like information is all over the place. Bummer. Hope it works out for you, especially since it was an ota. They could be cheats and try to say it failed due to the unlocked bootloader, and if you'd had root, but that would be a lie. If this rep denies you, just call back and speak to someone else.
Good evening and sorry if post a thread of which I see two similar oness
However, I could not find a solution in the other ones and have questions which go a little further and really hit my privacy.
I have two XZ3 and both could go into recovery node when I bought them and after a while could not.
I used the reset to factory seting fo wiping cache etc. quite regularly as I had/have reasons to belive that I was/am spied on.
Sice the recovery mode possibility is gone I feel totally unsafe with both phones.
I tried all possibilities I can find of this website or any other in internet, and all were without success.
As described by others, after pushing the power button, there is no led light and it boots suoer-quicklyto the blue stripe view in which we wait till the boot is complete.
Till two days ago I thought ok, the phone just needs a flash, wipe everything away once and all would be resolved.
Well, two days ago I flashed my phone the first time from lollipop to kitkat, which worked without problems and then rooted it with gifroot and then put back lollipop.
Everything ran smoothly and after the whole process I had a rooted lollipop version with a working recovery. I tried the apps which confirm if the root works abd everything was great.
Tthe morning after, however the recovery possibility was gone. The phone was still rooted for everything, but for recvery mode.
I tried several apps, which I gave superuser access with SuperSu, but even from the apps the boot goes always just the NORMAL way without recovery.
To give it another try today I flashed that xz3 again, then rooted it with Kingo root, which in Kitkat firmware worked lalso super easy, the checked with other apps whihchconfirmed that the root works, but still no recovery possibility, no matter with which app..
I really need a specialist who can explain that to me, as I am going mad to think that someone else has total control over my phones.
How realistic is that some spyware does not allow the recovery as of course it knows that it would be eliminated then.
Please give me your thuoghts or knowledge. Everything helps. And if you know a method with which I can be sure that nothing is keft on the phone, I would appreciate.
Thanks and Regards
iFran72 said:
Good evening and sorry if post a thread of which I see two similar oness
However, I could not find a solution in the other ones and have questions which go a little further and really hit my privacy.
I have two XZ3 and both could go into recovery node when I bought them and after a while could not.
I used the reset to factory seting fo wiping cache etc. quite regularly as I had/have reasons to belive that I was/am spied on.
Sice the recovery mode possibility is gone I feel totally unsafe with both phones.
I tried all possibilities I can find of this website or any other in internet, and all were without success.
As described by others, after pushing the power button, there is no led light and it boots suoer-quicklyto the blue stripe view in which we wait till the boot is complete.
Till two days ago I thought ok, the phone just needs a flash, wipe everything away once and all would be resolved.
Well, two days ago I flashed my phone the first time from lollipop to kitkat, which worked without problems and then rooted it with gifroot and then put back lollipop.
Everything ran smoothly and after the whole process I had a rooted lollipop version with a working recovery. I tried the apps which confirm if the root works abd everything was great.
Tthe morning after, however the recovery possibility was gone. The phone was still rooted for everything, but for recvery mode.
I tried several apps, which I gave superuser access with SuperSu, but even from the apps the boot goes always just the NORMAL way without recovery.
To give it another try today I flashed that xz3 again, then rooted it with Kingo root, which in Kitkat firmware worked lalso super easy, the checked with other apps whihchconfirmed that the root works, but still no recovery possibility, no matter with which app..
I really need a specialist who can explain that to me, as I am going mad to think that someone else has total control over my phones.
How realistic is that some spyware does not allow the recovery as of course it knows that it would be eliminated then.
Please give me your thuoghts or knowledge. Everything helps. And if you know a method with which I can be sure that nothing is keft on the phone, I would appreciate.
Thanks and Regards
Click to expand...
Click to collapse
Spyware cannot affect Recovery unless it is granted root permissions and is embedded on system.
Also do not use KingoRoot, a thread in the SG note 3 forums reported Spyware installed after using it, source. For now steer clear of that application until all claims have been proven false
At any rate, ( assuming you have Unlocked Bootloader ) just flash another kernel with recovery, do a full wipe including formating the system partition and restore your system via flashing a rom
9
Revontheus said:
Spyware cannot affect Recovery unless it is granted root permissions and is embedded on system.
Also do not use KingoRoot, a thread in the SG note 3 forums reported Spyware installed after using it, source. For now steer clear of that application until all claims have been proven false
At any rate, ( assuming you have Unlocked Bootloader ) just flash another kernel with recovery, do a full wipe including formating the system partition and restore your system via flashing a rom
Click to expand...
Click to collapse
i got that problem i cant hard reset my phone i forgott my posswords and the key combo dosent work and i have never rooted before, can you give me a step by step for dummie (me)
petterssonjohan said:
9
i got that problem i cant hard reset my phone i forgott my posswords and the key combo dosent work and i have never rooted before, can you give me a step by step for dummie (me)
Click to expand...
Click to collapse
If you can enter flash mode, flash the latest firmware and software for your device using flash tool.
What is flash mode? I can get the phone in a mode where the indicator lamp turns blue is it that?
get Flashtool @ https://xperiafirmware.com/flashtool/
it includes Xperiafirm so you can download a stock ROM for your device and build an .ftf file
when you have the ftf file, drag it into the main Flashtool window
follow prompts
I am coming with hat in hand fully expecting to find out that there is no solution and I am out the $$$ it will cost me to replace. After having this device for close to 2 years, I decided I would root it. I have 5 other devices currently that are rooted and numerous others that I have rooted over the years (including Samsung). Admittedly, I dislike Odin and a lot of other things about rooting Samsung devices. That is part of the reason this was the only device that I ever kept unrooted for more than a month or two. I installed twrp_3.1.0-1_sm-t713_14417n with Odin with no issues. I had SuperSU 2.82 in internal. When I got into TWRP to install it, I saw nothing but directories in internal and it became clear to me that it was encrypted. Attempts to mount, wipe and even reset data all ended up with me booting back to TWRP. I'm sure frustration set in the more things I tried, but now I can't even shut the device down from TWRP or by long pressing power and volume down. Even that just goes back to TWRP. Obviously, I can't get into download mode or system. I just get the recovery booting set warranty bit: recovery message when it starts back up to TWRP. Can't say I have ever seen a device that can't even be forced to shut down, LOL. Thanks in advance if anyone can help.
*I've made some progress. I managed to back door my way into download mode by installing the boot.img from the external SD card. That didn't fix anything, but after that I was able to hold down power down and volume and spam the home button until I got to the download screen. I was able to get back into Odin, but the full firmware file I tried to install errored out at the end with a rev check fail. Hopefully, it was because it thought it was downgrading, so I am downloading the newest file now. The samsung-firware.org D/L is brutally slow. Has a few more hours to go, and I am not positive if it will work yet. Cross your fingers, and throw out any ideas if you have them.
Well, it's alive. Everything is back to normal (except needing to reinstall). Time to root now, LOL!
OK, tried again and ended up restoring the full image again (minus D/L time at least). I am ready to scrap root on this device. I have tried to do everything in the [TWRP 3.1.0-1][ROOT] Galaxy Tab S2(2016) - SM-T713/SM-T719/SM-T813/SM-T819 - 1/4/17 thread. https://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627 I would have tried installing no verify, but no matter what I do not see the SU and no verify files on the tablet either after format data without reboot or after rebooting into TWRP. After the format, it shows that data is mounted. Looking at the pictures in the thread, I think maybe it needs the work done on the external SD but the instructions say nothing about that. Time to sleep on it, and maybe someone smarter than me can think of what I might be missing and maybe better step by step instructions are available. At least it is up and running, KNOX trips be damned. I'll post to the TWRP/ROOT thread. BTW, the OS version I am running is XAR-T713XXU2BRB2_T713XAR2BRB2-20180206.
Well, thanks to some middle of the night assistance from ashyx and about 3 hours sleep in the past 48 hours, I am not only restored and working but now rooted with TWRP 3.1.0-1 and Magisk 17.1! Time for a nap.
sliding_billy said:
Well, thanks to some middle of the night assistance from ashyx and about 3 hours sleep in the past 48 hours, I am not only restored and working but now rooted with TWRP 3.1.0-1 and Magisk 17.1! Time for a nap.
Click to expand...
Click to collapse
I am thinking about rooting my T713. Are there better instructions? What did you have to do differently?
I'd like to get it a go, but the instructions aren't as good as for the many devices I've rooted in the past.
Thanks!
Cheers,
Rich
Sent from my SM-T810 using Tapatalk
rholm said:
I am thinking about rooting my T713. Are there better instructions? What did you have to do differently?
I'd like to get it a go, but the instructions aren't as good as for the many devices I've rooted in the past.
Thanks!
Cheers,
Rich
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
The instructions in the TWRP thread are OK, but they could be a little clearer in some places. Take a look at the interaction between ashyx and I towards the end of the TWRP thread.
https://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627
welp. A month back I pulled my phone from my pocket and it was stuck on the boot screen.
I can only guess it came on in my pocket and triggered the update I was going to deal with that coming Monday.
And I guess the update had failed.
I had no time to deal with it till now. I side loaded the latest OTA update, and it's changed nothing.
Is there anything else I can try to either get it to boot or get access to the storage to recover data from it?
OhYou_ said:
welp. A month back I pulled my phone from my pocket and it was stuck on the boot screen.
I can only guess it came on in my pocket and triggered the update I was going to deal with that coming Monday.
And I guess the update had failed. I had no time to deal with it till now. I side loaded the latest OTA update, and it's changed nothing.
Is there anything else I can try to either get it to boot or get access to the storage to recover data from it?
Click to expand...
Click to collapse
If your bootloader is locked there is nothing else you can really do. Flashing the full image would likely bring it right back with your data intact. If BL locked, the only options you have are in the stock recovery. You can side load OTA's via recovery using adb, but it is restricted to that. If you didn't have usb debugging already enabled you can't use push/pull or use any other commands, and your data is encrypted. There is only a very slim chance doing a FDR from recovery would get you back into System. Very slim. Hopefully you purchased through the Google Store, otherwise your only recourse is to go back to the store/carrier where you bought it.
v12xke said:
If your bootloader is locked there is nothing else you can really do. Flashing the full image would likely bring it right back with your data intact. If BL locked, the only options you have are in the stock recovery. You can side load OTA's via recovery using adb, but it is restricted to that. If you didn't have usb debugging already enabled you can't use push/pull or use any other commands, and your data is encrypted. There is only a very slim chance doing a FDR from recovery would get you back into System. Very slim. Hopefully you purchased through the Google Store, otherwise your only recourse is to go back to the store/carrier where you bought it.
Click to expand...
Click to collapse
Yes it's locked. I did not much to the phone because it is a company phone. It was purchased through Verizon.
I'm pretty confident that a factory reset will fix it, from my research on it, but I'm going to keep holding off and try the next OTA update before giving up.
It's just unfortunate because as it does have a great camera, I used it a lot for taking pictures when I didn't have a dslr on hand. So a few trips worth of pictures are on it and I only pulled a few off.
I usually backup all that before updating, but didnt get a chance to because it decided to just do it in my pocket.