I found my answer. Can't see how to delete the post though.
Hi, my TF701T is rooted on 4.4.2. And, I do have encryption enabled. Somehow I messed up Google Play Services and seems I need to recover to stock and start over. I have been trying to follow some threads or videos such as; https://www.youtube.com/watch?v=HjK6TrO9Dlc. But, I still end up with the tablet essentially as it was. Do I need to use ADB to reformat the system partition or something before re-installing the stock ROM? What are the commands I need? TIA.
Related
Hello! This is my going to be my first post, so please bear with me.
I own a Samsung Galaxy S4 Active (SGH-I537) from AT&T. I've owned the device for about 6 months now and love it. Recently, I encountered a problem with connecting to GApps/Google services and adding a Google Account.
I rooted my S4 Active with this method from geohot I found here: http://forum.xda-developers.com/showthread.php?t=2347793
After tooling around with it for a day, I had trouble getting on the Play Store. My screen displayed "No Connection; Retry). After trying various solutions I removed my Google Account from the device.
When I couldn't log back in to my Google Account, I disabled 2-step verification and tried application-specific passwords. No avail.
I performed many factory reset, both from the Settings page and by a hard reset. I've wiped all the user data, so I have no apps or anything.
I keep getting this error message, see attachment below.
TD;LR #1 : I rooted my GS4a and I can't use my Google Account. Period.
My guess is that I need to restore the stock firmware onto my Galaxy S4 Active. I haven't been able to find a safe method of doing this yet. I think that this will "restore" my device as if I was doing this to an iOS device (I'm a convert from the Apple ecosystem )
Does anyone know how to flash the stock TouchWiz firmware onto the Galaxy S4 Active. I'm open to alternative solutions too, such as Cyanogenmod or stock Android 4.4.
TD;LR #2 : I need to flash stock firmware or something on my GS4a!
I appreciate all the help I can get. For now, I'm sitting with the Amazon Appstore and Google Chrome for Facebook, Gmail, Twitter, etc.
-Z3RODay
The method used for rooting shouldn't cause any problems with your phone since it only touches a couple files. I doubt that rooting your phone caused GApps to stop working, I'm guessing that either a root file got deleted or another app is incompatible and causing problems.
You're asking how to return your phone to stock and you're correct in that it will "restore" your device, but in doing so it will completely wipe your device and you will lose everything. It will essentially return your phone to the state of when you first pulled it out of the box. This question has been asked and answered a few times and you could probably find the answer by searching, but I'll post the answer here too. For the i537 below are the only known ways to get stock firmware back on your phone:
Devo7v said:
You can Odin back to a pre-release version and have a fully functioning phone, but you will no longer receive official OTA updates (read more about this option here), or
You can take it to the Samsung Experience Shop at your local Best Buy and have them restore your phone to official stock MF3 (read more about this option here).
Other than that I don't really know what else you can do.
Click to expand...
Click to collapse
Devo7v said:
The method used for rooting shouldn't cause any problems with your phone since it only touches a couple files. I doubt that rooting your phone caused GApps to stop working, I'm guessing that either a root file got deleted or another app is incompatible and causing problems.
You're asking how to return your phone to stock and you're correct in that it will "restore" your device, but in doing so it will completely wipe your device and you will lose everything. It will essentially return your phone to the state of when you first pulled it out of the box. This question has been asked and answered a few times and you could probably find the answer by searching, but I'll post the answer here too. For the i537 below are the only known ways to get stock firmware back on your phone:
Click to expand...
Click to collapse
Thank you so much! I'm going to take my phone to Best Buy tonight. I backed up everything on my SD card which is still intact (Thank God!).
Hi,
I am absolutely new to this, please redirect me or correct me where i am wrong.
I need to recover deleted photos and videos from the interal memory, I have installed "DiskDigger" to perform that task however my device is not "rooted".
I am anxious not to permenantly removed the data that i could possibly recover. (if at all possible)
I have seen a couple of threads on how to flash the phones, but nothing corresponding to my exact config. (Kitkat 4.4.4 build 14.4.A.0.157)
Could somebody indicate the process i should follow?
thanks
cabrolse said:
Hi,
I am absolutely new to this, please redirect me or correct me where i am wrong.
I need to recover deleted photos and videos from the interal memory, I have installed "DiskDigger" to perform that task however my device is not "rooted".
I am anxious not to permenantly removed the data that i could possibly recover. (if at all possible)
I have seen a couple of threads on how to flash the phones, but nothing corresponding to my exact config. (Kitkat 4.4.4 build 14.4.A.0.157)
Could somebody indicate the process i should follow?
thanks
Click to expand...
Click to collapse
Check this post for info on rooting your phone.
http://forum.xda-developers.com/xperia-z1/help/guide-downgrade-root-dualrecovery-c6916-t3062919
Use this site to get your specific firmware instead of Z1s c6916
http://storagecow.eu/index.php?dir=Xda%2FSony%2FXperia+Z1%2FC6903%2F
cabrolse said:
Hi,
I am absolutely new to this, please redirect me or correct me where i am wrong.
I need to recover deleted photos and videos from the interal memory, I have installed "DiskDigger" to perform that task however my device is not "rooted".
I am anxious not to permenantly removed the data that i could possibly recover. (if at all possible)
I have seen a couple of threads on how to flash the phones, but nothing corresponding to my exact config. (Kitkat 4.4.4 build 14.4.A.0.157)
Could somebody indicate the process i should follow?
thanks
Click to expand...
Click to collapse
I know this isn't exactly answering your question, but mine was on the same build and I searched high and low. The only methods I found for kitkat weren't working, but I believe they were for 4.4.2, not 4.4.4.
I ended up downgrading to Jellybean and rooting it that way. Sticking with Jellybean too, kitkat can kiss my rear, lol
SonyXperiaz1s said:
I know this isn't exactly answering your question, but mine was on the same build and I searched high and low. The only methods I found for kitkat weren't working, but I believe they were for 4.4.2, not 4.4.4.
I ended up downgrading to Jellybean and rooting it that way. Sticking with Jellybean too, kitkat can kiss my rear, lol
Click to expand...
Click to collapse
Thank you for the feedback.
Can you or somebody else confirm if by downgrading and rooted , will i still be able to recover deleted files within the DCIM folder ?
cabrolse said:
Thank you for the feedback.
Can you or somebody else confirm if by downgrading and rooted , will i still be able to recover deleted files within the DCIM folder ?
Click to expand...
Click to collapse
that depends completely on the folders location and software used to recover them. if on your external then should be good. if on internal then might get writen over during flashing process. remember that the information is not deleted...just marked with a deleted flag...meaning that the OS thinks its empty space and can use that space to write new information. it would be all luck sorry to say.
cabrolse said:
Hi,
I am absolutely new to this, please redirect me or correct me where i am wrong.
I need to recover deleted photos and videos from the interal memory, I have installed "DiskDigger" to perform that task however my device is not "rooted".
I am anxious not to permenantly removed the data that i could possibly recover. (if at all possible)
I have seen a couple of threads on how to flash the phones, but nothing corresponding to my exact config. (Kitkat 4.4.4 build 14.4.A.0.157)
Could somebody indicate the process i should follow?
thanks
Click to expand...
Click to collapse
Hi Bro,
Try this method which i used myself. this does not required any downgrade or re-flash or data loss. You just need .157 running already with your device.
I have a 1st gen motoX that I rooted ages ago with slapmymoto/pwnmymoto. It's stock, never messed with the bootloader. Never changed the ROM, it's running stock android 4.4.
Got a new job and requires encryption. If I try to encrypt it, will I break my phone? Alternatively, will it even work to encrypt it?
I've searched and see some details for other phones, but couldn't find this in my situation. If it's been asked/answered, my apologies.
Thanks so much for the help!:good:
You should be fine. It only really encrypts /data, anyway.
So, today I upgraded to 6.0 and had a hell of a time (took me 7 hours) and the problem was that when I installed su from twrp it'd soft brick my phone, anyway, that's not the problem, the problem is everything is saving to /storage/emulated and I can't access it without root. I noticed this when I was on OGInsta and I wanted to download a picture, it gave me an error code about how it couldn't find the directory, so I went to my file manager, everything was fine but I accidentally hit up instead of home and it brought me to an empty page. I started messing with the settings of my file manager assuming something went wrong with it, new version etc, and I found it had a root option. I clicked it and gave it root access and went back and I could see the files where I was previously. To make sure I tried to save something on kik, didn't work. I tried accessing my storage from the rar app and it wouldn't. I don't know what's going on or how it even got this way.
How did you install 6.0, what version of su did you install, and how did you fix the soft brick?
Sounds like you have very little idea what your doing and running a ton of random stuff. Probably best to do a system restore, take a step back learn what your doing and do it again properly... but if you can recount the steps you have done it may be fixable.
I like to think I have decent knowledge on what I am doing, I've been rooting phone's and made xposed apps (for myself) since kitkat. I've never had so much trouble with something. And to answer your questions, I figured using nexus root toolkit would he fine, as it always has worked before but I couldn't get it to root my phone. It would soft Brick it for an unknown reason, I left it on for about an hour at one point to make sure it was bootlooping. So then I used adb, flashed boot.img and then recovery. Went into recover and flashed SU 2.52 beta. (this is also how I solved the soft Brick the nexus toolkit was giving me)
scryan said:
How did you install 6.0, what version of su did you install, and how did you fix the soft brick?
Sounds like you have very little idea what your doing and running a ton of random stuff. Probably best to do a system restore, take a step back learn what your doing and do it again properly... but if you can recount the steps you have done it may be fixable.
Click to expand...
Click to collapse
Also, to clearly, I have 2 storage paths. One is "sdcard/" and the other is "storage/emulated/0" I'm not sure if the "storage" folder is new in 6.0, I know 4.+ and 5.+ used "sdcard/". Too see "storage/emulated/0" I need to grant root access to the file manager. And any app the does not have root, cannot access that directory.
YoureVexing said:
I like to think I have decent knowledge on what I am doing, I've been rooting phone's and made xposed apps (for myself) since kitkat. I've never had so much trouble with something. And to answer your questions, I figured using nexus root toolkit would he fine, as it always has worked before but I couldn't get it to root my phone. It would soft Brick it for an unknown reason, I left it on for about an hour at one point to make sure it was bootlooping. So then I used adb, flashed boot.img and then recovery. Went into recover and flashed SU 2.52 beta. (this is also how I solved the soft Brick the nexus toolkit was giving me)
Click to expand...
Click to collapse
you might have knowledge in making apps, but you are missing lots of knowledge when modding your phone. you are going to have to use an app like root explorer, and find where your storage was placed, then move it to the right location. or you can reflash the factory image. ive always just moved my storage back when its happened to me. anyways, flash the factory image the right way, not through a toolkit. then flash any custom kernel(if flashing marshmallow), and supersu.
YoureVexing said:
I like to think I have decent knowledge on what I am doing, I've been rooting phone's and made xposed apps (for myself) since kitkat.
Click to expand...
Click to collapse
Why are comments like this always made by people who take 7 hours to flash a factory image, and make statements like
YoureVexing said:
So then I used adb, flashed boot.img and then recovery.
Click to expand...
Click to collapse
ADB cannot flash factory images.
I didn't need your resume... Just answers to the questions I asked....
Do as simms said and flash factory image with fastboot to fix whatever you did, then a kernel and the lastest supersu.
The emulated storage folder has been there at least since kit kat. My S4 and Moto X, neither of which saw LP both had it.
scryan said:
Why are comments like this always made by people who take 7 hours to flash a factory image, and make statements like
ADB cannot flash factory images.
I didn't need your resume... Just answers to the questions I asked....
Do as simms said and flash factory image with fastboot to fix whatever you did, then a kernel and the lastest supersu.
The emulated storage folder has been there at least since kit kat. My S4 and Moto X, neither of which saw LP both had it.
Click to expand...
Click to collapse
It took me 7 hours because I could figure out what was wrong with it and why twrp kept soft bricking my device. And I'm not worried about emulated. I know that has been there. I'm saying there is 2 folders, /sdcard and /storage. Every app is trying to use the path "/storage/emulated/0/*insert app folder here" and it cannot do that without root. I'm confused as too why all the apps are trying to do that for a default location instead of /sdcard. I've already tried to reflash everything. I even looked up like 5 tutorials to make sure I was doing it right and I was.
Can't really help you with your current situation (other than to advise you to flash a factory image and start over), but if it confirms your sanity the exact same thing happened to me using the rootkit to root my Nexus 6. I should've known better than to use rootkit, but I'm not really used to fastboot having been on Samsung devices and using Odin for everything. I corrected it by flashing a factory image, flashing the modified boot image, flashing TWRP, and then SuperSU. But the whole process was quite a fiasco from what I'm used to and for what I expected from a Nexus phone.
YoureVexing said:
It took me 7 hours because I could figure out what was wrong with it and why twrp kept soft bricking my device. And I'm not worried about emulated. I know that has been there. I'm saying there is 2 folders, /sdcard and /storage. Every app is trying to use the path "/storage/emulated/0/*insert app folder here" and it cannot do that without root. I'm confused as too why all the apps are trying to do that for a default location instead of /sdcard. I've already tried to reflash everything. I even looked up like 5 tutorials to make sure I was doing it right and I was.
Click to expand...
Click to collapse
/sdcard is a simlink, its the same folder.
internetpilot said:
Can't really help you with your current situation (other than to advise you to flash a factory image and start over), but if it confirms your sanity the exact same thing happened to me using the rootkit to root my Nexus 6. I should've known better than to use rootkit, but I'm not really used to fastboot having been on Samsung devices and using Odin for everything. I corrected it by flashing a factory image, flashing the modified boot image, flashing TWRP, and then SuperSU. But the whole process was quite a fiasco from what I'm used to and for what I expected from a Nexus phone.
Click to expand...
Click to collapse
The rootkit wasn't working for me, it's been a charm for my nexus 5 and from 4.+ and nexus 6 on 5.+, on 6.0 it wasn't working so I tried to flash it on fastboot and I still got the same thing. I'll try it once more I suppose, thank you.
I am running CyanogenMod version 13.0-20160127-UNOFFICAL-ovation ( Marshmallow 6.01) on my Nook HD Plus. I am mostly pretty happy with it. I made a backup of it and tried a couple of other images on my device, all the while intending to go back to my original installation. When I got ready to go back to it, I wiped everything using TWRP Recovery ( on an external SD card) , because I didn't want any "leftover" stuff from the other images on the installation. I was under the impression that TWRP backed up the user data, photos etc. I found that was not the case. ( Not really a big problem at this time.) In order to prevent this from happening in the future, I attempted to use adb to my PC to back up my user data (media, etc). I could not get it to work.... tried with another HD Plus ( with Marshmallow flashed overtop Jelly Bean... it worked fine. The PC is not seeing the Nook ( the first one). I looked on the internet and discovered that adb had been left out of Marshmallow by Google. I found a zip by Osm0sis on XDA that was supposed to address this omission, but it did not correct the problem. Can anyone help me with this? Thanks.
Same Problem
I am having the same problem as fire1951. I am also running Android 6.0.1 and cannot communicate with my computer using adb. I had no problem with this on previous versions of android (Jellybean)..... same device -- same computer. Was this capability left out of 6.01? I get conflicting information on this forum and the internet in general. Surely there's a flashable zip or some method to get this function back. Has no one else experienced this problem and possibly found a fix? Please help if you know a way to correct this.
Juan1002, I found out how to enable and access adb on 6.0.1. Since no one else seems to have this problem, I will pm you the procedure.