Hi guys, thanks for the forum and i hope to become a part of it. I've been under so much stress since yesterday, my galaxy s3 (on EE in the UK) for the first time decided it's data was corrupted yesterday after my battery died, never done this or anything like it before, and it wouldn't let me access the phone itself unless the data was reset.
I had a lot of very precious pictures in my gallery from the weekend, which unfortunately chose not to backup to google+ for the last few days, even though it always has up until recently. All night/day i've been trying to figure out and get software to recover these photos, which i think is possible as i did it a long time ago on a blackberry, but not android yet. I'm just hoping it can be done so the photos aren't forever lost, the other stuff gone doesn't bother me so much.
The guide i'm following (here: http://forum.xda-developers.com/gal...de-internal-memory-data-recovery-yes-t1994705) says it needs to be rooted first, and i can't even get past step 1. I've only ever rooted my old galaxy S1 (which worked back then) but i can't seem to get the S3 to do it. And now my phone also believes there's no sim card in and i get no signal now.
this is the guide i followed: http://www.ibtimes.com/how-root-sam...-jelly-bean-official-firmware-tutorial-975812
though i think i need a newer PDA file to flash my i9305 with. I'm on the EE network running 4.3 jelly. It installed Super SU but root checker says it still isn't rooted.
So have i messed this up? And is there any hope for me getting these pictures back?
Thanks in advance for any help, it's much appreciated.
if you are running on 4.3 then you are not following the right guide to root...
use THIS ONE instead... if it fails to root use the workaround part, i used it and worked....used the workaround to install custom recovery and then flashed chainfire zip from his website and updated SU and worked.
are you still able to boot the phone?
Thanks for the response, tried that guide and still getting no signal on my phone (no mobile connection at all, sim card isn't recognised as being there) and i don't think it's rooted right. Still saying SuperSU has stopped working when i try to open it.
I put the Root_SuperSU.1.02-Busybox.1.21.0.zip on the internal SD and tried that too.
Which is the chainfire zip you're talking about, could you possibly link it? I don't really get what you mean by custom recovery, do you mean it's the same as flashing the Busybox thing from recovery mode?
And yeah it still boots up normally...
use that tutorial to install a custom recovery...then install this SuperSU - http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip?retrieve_file=1 - flash it in custom recovery....after that update app with playstore and should work.
but i suggest you get it to a specialized shop to get your photos back...
I wasn't going to root my phone but this "its on" app is killing half my battery now, so I guess its time. Can someone point in in the right direction for a tutorial that can root after the 4.4.4 update? also, does anyone know if there's a way to root without erasing the phone? I don't want to reinstall everything, I really just want to get rid of the its on app. Its unbelievable that sprint hasn't fixed this in over a month.
The method to root is the same as it is with previous Android versions on this device. Unlocking your bootloader factory resets the device, but you can connect your phone to your PC and backup whatever you need to beforehand. HTC backup also works great for backing up apps, ringtones, etc. I've used it in the past and it works quite well. As far as the ItsOn garbage, you'll need to flash a ROM that removes it from the device, as it's not simply an app that you can delete.
I have an ATT S5 (SM-G900A), completely stock, unrooted, updated to the latest 5.0 OTA update. My requirements for my phone are that it be able to pass Airwatch checks and that it be able to be encrypted (Personal device used at work). Some background first:
Last time I tried to play around with rooting, other mods, and whatnot was on my ATT S3 (I think I747?) and I discovered that an unspecified combination of rooting, installing a custom loader (CWM in my case) and installing a custom mod (Cyanogenmod at the time) made my phone unable to encrypt. At the time I was not required to use Airwatch, but encryption was required for my phone to connect to work, so I gave up on the whole lot.
I have now discovered that ATT, in their infinite wisdom, has replaced the S Voice drive mode with their own "ATT Drive Mode", and it's been verified they went so far as to remove the related APKs from the phone entirely. For those unaware, S Voice Drive mode is an feature of S Voice that (when turned on) reads out all callers and text messages, and then verbally prompts you for actions; reply, answer, ignore, etc. It allows fully hands free functionality. ATT Drive Mode, on the other hand, automatically kicks in whenever speeds of 20 MPH are detected (even if you're a passenger), rejects all calls and texts excluding a user-defined 5 person list, and essentially makes your phone useless anytime you're in a car. The goal is to "reduce texting and distracted driving", but as I'm on-call as part of my job and need to at least be aware of texts that come in within 10 minutes of receipt, it actually makes my drive much more dangerous. ATT Drive mode is a good idea for teens, perhaps, but i'm not a teen.
This brings me to my question: What are my options?
--Does rooting break my ability to encrypt? I know airwatch will flag, but I'm thinking there's a possibility of being able to root, put a custom loader on my phone, and then restore stock with that custom loader, whereupon I can try to install the drive mode APK...which leads me to my next question:
--Does having a custom loader (like safestrap or CWM or whatever is in use nowadays) break my ability to encrypt?
--Does anyone know of a way to install the S Voice drive mode in the G900A? I tried searching, but the only references involved being rooted, or ended with something vague like "download a stock rom and find the apk using root explorer" as the solution (which is vague to me because I don't know which stock rom to use, what apk to look for, and last time I used root explorer on my s3, it needed root...)
Honestly, the ideal solution would be something like the stock rom from the international version that would run on my ATT version...but I don't know if such a thing exists or is possible. I don't mind Samsung's cruft, but I do dislike ATT's lobotomizing of my phone to push their own little product that treats me like a kid. I know that I am less safe as a driver without the S Voice drive mode than I was with it.
I take it I have no options? And that no one knows how rooting affects encryption?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
sheaiden said:
I take it I have no options? And that no one knows how rooting affects encryption?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
I will make it easy for you. Since you took the 5.0 OTA update rooting is not possible anymore. Also there is no way to downgrade to KitKat which was rootable. Sorry. Not much you can do until someone finds a way to root 5.0. If you find the S Voice Drive app, you can side load it and see if it works.
Waiting4MyAndroid said:
I will make it easy for you. Since you took the 5.0 OTA update rooting is not possible anymore. Also there is no way to downgrade to KitKat which was rootable. Sorry. Not much you can do until someone finds a way to root 5.0. If you find the S Voice Drive app, you can side load it and see if it works.
Click to expand...
Click to collapse
Actually, while I greatly appreciate the fact that you took the time to reply (seriously! at least you took the time!), this is neither easy nor related to the questions I asked. If you look at my post, I'm not asking "how can I root", I'm asking three rather different questions:
--Does rooting break my ability to encrypt? I know airwatch will flag, but I'm thinking there's a possibility of being able to root, put a custom loader on my phone, and then restore stock with that custom loader, whereupon I can try to install the drive mode APK...which leads me to my next question:
--Does having a custom loader (like safestrap or CWM or whatever is in use nowadays) break my ability to encrypt?
--Does anyone know of a way to install the S Voice drive mode in the G900A? I tried searching, but the only references involved being rooted, or ended with something vague like "download a stock rom and find the apk using root explorer" as the solution (which is vague to me because I don't know which stock rom to use, what apk to look for, and last time I used root explorer on my s3, it needed root...)
In fact, I am unable to remain rooted (Airwatch; it's part of the post title), and the whole point and thrust of my question lies in the fact that I am looking to find out what affects encryption and what options I have as far as getting S Voice Drive mode on my phone while staying Airwatch compliant (not rooted). In addition, "if you can find the s voice drive app" is part of the problem too, as evidenced by the third question I asked above; I don't know where to find said app.
Does anyone know anything regarding what I was actually asking?
Everything that you want to do requires ROOT! Safstrap needs root, CWM will brick you phone since the bootloader is locked. Again, there is no way as of now to root the S5 with 5.0 att OTA.
Here is the link to download the GS4 S Voice app. You can try and side load it,
https://www.dropbox.com/s/oe7i2g81iuhjv38/S-Voice_Android_phone_J.apk?dl=0
Waiting4MyAndroid said:
Everything that you want to do requires ROOT! Safstrap needs root, CWM will brick you phone since the bootloader is locked. Again, there is no way as of now to root the S5 with 5.0 att OTA.
Here is the link to download the GS4 S Voice app. You can try and side load it,
Click to expand...
Click to collapse
Awesome, I'll start with that sideloading, and test it out. Thanks! As far as the rest, I suppose that does clarify some things (that I admittedly already knew), so I do appreciate it, but it still does leave the answers to the other questions. I can infer, of course, that the answer to whether having a custom bootloader on the Galaxy S5 breaks encryption will be dependent on whether root breaks the encryption, since as you pointed out custom bootloaders need root to install, but the fantasy I entertained for a little while was rooting when there's a method (hope springs eternal, so I'm hoping it will eventually be possible), installing a custom bootloader so I can do things like backups and sideload, getting the proper apk's installed for the drive app, and then unrooting it so I can connect it via airwatch to my work's network. Perhaps I should have marked this as a solidly theoretical question, since as you said, there currently exists no root. I just want to know, with the unique way that Samsung implemented Knox and the encryption on the S5, what will break encryption and what won't?
Of course, there is a side question brought up by all this...how possible is it to load another firmware on my phone? as in, use Odin to put the tmobile image on my phone. That is likely a bad example, since I'm fairly certain there are actual hardware differences between the ATT and the tmobile models, but the concept still stands. At what level are the hardware configurations different between phone companies?
sheaiden said:
Awesome, I'll start with that sideloading, and test it out. Thanks! As far as the rest, I suppose that does clarify some things (that I admittedly already knew), so I do appreciate it, but it still does leave the answers to the other questions. I can infer, of course, that the answer to whether having a custom bootloader on the Galaxy S5 breaks encryption will be dependent on whether root breaks the encryption, since as you pointed out custom bootloaders need root to install, but the fantasy I entertained for a little while was rooting when there's a method (hope springs eternal, so I'm hoping it will eventually be possible), installing a custom bootloader so I can do things like backups and sideload, getting the proper apk's installed for the drive app, and then unrooting it so I can connect it via airwatch to my work's network. Perhaps I should have marked this as a solidly theoretical question, since as you said, there currently exists no root. I just want to know, with the unique way that Samsung implemented Knox and the encryption on the S5, what will break encryption and what won't?
Of course, there is a side question brought up by all this...how possible is it to load another firmware on my phone? as in, use Odin to put the tmobile image on my phone. That is likely a bad example, since I'm fairly certain there are actual hardware differences between the ATT and the tmobile models, but the concept still stands. At what level are the hardware configurations different between phone companies?
Click to expand...
Click to collapse
You will not be able to change your bootloader period... At this point the locked bootloader is unbreakable. That leads to your next question about tmobile and that's a no as well due to the locked down bootloader.
Even with root you won't be able to do anything you've suggested due to the locked bootloader.
OPOfreak said:
You will not be able to change your bootloader period... At this point the locked bootloader is unbreakable. That leads to your next question about tmobile and that's a no as well due to the locked down bootloader.
Even with root you won't be able to do anything you've suggested due to the locked bootloader.
Click to expand...
Click to collapse
Interesting. I had been under the impression that I had seen people referring to installing clockworkmod or some similar thing on an S5, but I think I may be getting caught up in terminology; those are recoveries, aren't they? not bootloaders? Or perhaps people were posting about the other S5s with unlocked bootloaders. 15 different versions of S5, and I get stuck with the most apple-like of all the carriers....(in the sense of "you take what we give you and don't play with it!")
So, assuming I don't manage to get it installed via the link Waiting4MyAndroid was kind enough to post, I think that rules out anything other than the method of:
--wait for a root method to be established for the new OTA
--root, install the drive apk
--unroot, so I can encrypt and pass airwatch
Does anyone know if the old method of rooting broke encryption? and whether encryption was able to be performed after unrooting again?
Edit: Attempted to Sideload. Sadly, it is telling me "App not installed" (other sideloads do work; it's not the unknown sources setting). I'm thinking either the apk is marked for s4, and it's not compatible, or it's trying to overwrite files from the established svoice system, and that's not allowed. I suppose if someone has the drive apks from a tmobile S5 image or some such thing (same model, different carrier), then I could try again, but unfortunately this apk doesn't work. Thanks for the attempt, Waiting4MyAndroid!
First Root Ive ever done.
I have a few questions.
I'm done rooting my phone with cwm, and root-stock, I'm confused what to exactly do next,
I am using Titanium backup, and I've frozen several apps including the ones that were running w/o my say so, I haven't removed anything as of yet, but I feel as if I'm still missing a few steps somewhere, and that's why I haven't moved forward as of yet.
I wondering is there anything else I need to before removing the bloatware?
Is there a program available to debug, partition, or make adjustments to it while connected to a computer?
+
Is there a way to see what is sending loads of data out, I am using avast to block most of the apps from using my network data, exception of the ones I use on a regular basis.
+
And what settings should everything be on, in the *#197328640# menu, I may have buggered a few things up in it. *a few days prior to root.
Any and all help will be great, thank you
*I used the info from this site, found a few broken kinks, searched some more, and found the files for the root.
I mistakenly did a factory reset and I need to recover files. My device is not rooted and cannot be rooted (G925VVRU2OAF1), and the recovery tools I've come across while searching the forums require root to work fully. This also renders DiskDigger and Undelete useless to me. Is there ANY WAY possible for me to recover my files? Or I'm done for without root?
Hi
Here is your post(I mistakenly did a factory reset and I need to recover files. My device is not rooted and cannot be rooted (G925VVRU2OAF1), and the recovery tools I've come across while searching the forums require root to work fully. This also renders DiskDigger and Undelete useless to me. Is there ANY WAY possible for me to recover my files? Or I'm done for without root? )
and answer is given below
Many reasons may cause the data loss, such as, mistakenly tapping the “Delete” button when you are exploring the new features of S6.Thats why you should avoid the deleted button. The available backups is far enough to avoid data loss. To get back you can follow this link and i hope you will get your answer(http://www.jihosoft.com/android-recovery/galaxy-s6-data-recovery.html )
I feel like im in the twilight zone and there's all these body snatchers trying to make me pay 50 dollars to recover a ten minute video.
I'm in the same boat as OP. Was in Maintenance Mode and forgot that menu is select and not power. Also on OF1.
I've tried more things than I can count. My solutions thus far has been to just wait until somebody discovers a root method. Preferably something to bypass the locked bootloader altogether but...meh.
In the meantime, my S6 gathers dust as I don't want to chance overwriting anything.
Try some recovery professional app.
My wife's phone is in the similar boat.
Word from the wise- 1) turn OFF the "factory reset after 15 failed screen unlock attempts" security feature, or 2) NEVER let a young relative handle your phone when it's been locked.
My wife had already maxed out her backup storage, so there's a couple months worth of pics that are in danger of being forever lost if she dares use the memory.
And it's been updated to 6.0.1, so root options seem to be nil at this time. So frustrating.