Related
I just rooted a new captivate (about 2 wks old) using one-click root method. All seemed to go smoothly & SU permission is installed. I still can't sideload (sirius/xm app) or uninstall any at&t apps. I downloaded androidmate, astro & even bought Root Explorer......NO LUCK!!! THE PHONE IS THE SAME, I can't install or uninstall anything. I would just like to install sirius/xm app. Are the new phones patched against rooting? any help is appreciated, thanks!
ice10 said:
I just rooted a new captivate (about 2 wks old) using one-click root method. All seemed to go smoothly & SU permission is installed. I still can't sideload (sirius/xm app) or uninstall any at&t apps. I downloaded androidmate, astro & even bought Root Explorer......NO LUCK!!! THE PHONE IS THE SAME, I can't install or uninstall anything. I would just like to install sirius/xm app. Are the new phones patched against rooting? any help is appreciated, thanks!
Click to expand...
Click to collapse
need to enable sideloading first
rsx19 said:
need to enable sideloading first
Click to expand...
Click to collapse
thanks for the quick response. how is that done? I rooted the phone because 'sideload wonder machine' wouldn't work. I kept getting this error - 'loader.bat' is not recognized as an internal or external command, operable program or batch file.
is there something I'm missing. I've viewed dozens of vid tutorials & forum entries., they all said the same thing - 'use swm or root your phone and boom - start downloading apps' Obviously something is being left out. I don't know what steps I'm missing.
In the dev section, somewhere in the first couple of pages there should be a thread titled something like how to enable side loading. In the gen section stickies there is a wiki that had it too.
From a phone on an app
here's where i'm at so far:
1.tried sideload wonder machine, which failed. I kept getting this error:
'loader.bat' is not recognized as an internal or external command, operable program or batch file. this led me to step 2
2. used galaxy 'one-click root' to successfully root the phone, & i now have superuser permission accessible. still can't sideload apps, leading to step 3.
3. tried sideloading using andriod browser, which also doesn't work. i keep getting this error:
unable to find a version of the runtime to run this application. (running on winxp 32)
it seems as though my only other option is the adb method using command prompt, but i've avoided this method; i'm new to android and don't want to risk bricking my phone just yet.
is there any other 'simple' way to sideload on a rooted phone?????? i only want to install a few apps.
any help is appreciated, thanks!!!
What I did was go on youtube and watched a tutorial on how to enable third party apps, then searched another video for removing ATT bloatware. This helped me greatly as my captivate was my first android device. Now I have set up all kinds of cool stuff like wireless tethering and the lagfix. youtube really helps because you can watch them do it as you do it!
ice10 said:
it seems as though my only other option is the adb method using command prompt, but i've avoided this method; i'm new to android and don't want to risk bricking my phone just yet.
Click to expand...
Click to collapse
adb is the only method I've ever used ... never had a problem and find it hard to believe that sideloading a known app would ever brick the phone by doing it this way.
laxwillsch said:
What I did was go on youtube and watched a tutorial on how to enable third party apps, then searched another video for removing ATT bloatware. This helped me greatly as my captivate was my first android device. Now I have set up all kinds of cool stuff like wireless tethering and the lagfix. youtube really helps because you can watch them do it as you do it!
Click to expand...
Click to collapse
startngate said:
adb is the only method I've ever used ... never had a problem and find it hard to believe that sideloading a known app would ever brick the phone by doing it this way.
Click to expand...
Click to collapse
thanks for the replies. i just meant i didn't want to mess up the commands & brick the phone. the directions for 'set third party app to 1' etc, seemed confusing for a noob.
laxwillsch - thanks for the info. i went back to youtube & realized i misunderstood the directions. i just had to drop the apk files into tools folder in the sdk and install from there. thanks for all your help guys
um...anyone know how to undo all this if i get rid of this phone? lol
My Droid 3 is rooted and I received the OTA notification. It downloads fine, reboots the phone, and begins to update. About 1/3 the way to update, the Android turns into an Exclamation point and reboots. Once back to home screen I get an Update Failed error.
Here is what I did so far:
-Defrosted all apps then rebooted
-Restored all system apps with Pete's One Click Root
-Pulled Battery for 5 min
-Factory Reset Phone
After each of these steps I tried to install the update and same thing. Will not get past 1/3. Any suggestions?
u need to rsd the swu.zip in order to get the update
OK, where can I get the swu.zip?
lacesout said:
OK, where can I get the swu.zip?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1255198
here u will find it along with rsdlite n adb fastboot. (make sure U read all that b4 U do it)
mrcastillo said:
http://forum.xda-developers.com/showthread.php?t=1255198
here u will find it along with rsdlite n adb fastboot. (make sure U read all that b4 U do it)
Click to expand...
Click to collapse
Thank you, this work!
lacesout said:
My Droid 3 is rooted and I received the OTA notification. It downloads fine, reboots the phone, and begins to update. About 1/3 the way to update, the Android turns into an Exclamation point and reboots. Once back to home screen I get an Update Failed error.
Here is what I did so far:
-Defrosted all apps then rebooted
-Restored all system apps with Pete's One Click Root
-Pulled Battery for 5 min
-Factory Reset Phone
After each of these steps I tried to install the update and same thing. Will not get past 1/3. Any suggestions?
Click to expand...
Click to collapse
lacesout, had the same experience. Used one-click method to root, then used psouza4's bloat script to remove, then restore apps when the update became available. These were my only mods. Went to /system/app and all app's are back with the proper apk extension. Update downloads fine, then hangs at 1/4 to 1/3 of install. Anyone else with similar experience or thoughts as to what's hanging the OTA install?
If you used the script to re-bloat the system, use root explorer and double check all the ".bak"s were removed. I don't remember which one, but I remember there was a file or two the script skipped over.
Also, if you did a nandroid before debloating, you can restore it, then go get the update. (The second option is what worked for me).
Sent from my DROID3 using XDA App
nu2droid said:
If you used the script to re-bloat the system, use root explorer and double check all the ".bak"s were removed. I don't remember which one, but I remember there was a file or two the script skipped over.
Also, if you did a nandroid before debloating, you can restore it, then go get the update. (The second option is what worked for me).
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Thanks for the reply and the tip on root explorer, it's an elegant tool, more intuitive to use than the freeware apps.
All the file extensions in /system/app are either .apk or .odex with the exception of Fota.apk.bak, and Fota.odex.bak. As the first time I heard of nandroid was your post, I unfortunately didn't use it, so I don't know if these were the extensions before I used psouza's bloat removal script. Fota was not on the list of scripts to remove/rename in his original post.
As Fota is the "firmware over the air" app, it is suspicious that it's the only one with a .bak ext. I am using root explorer to rename both, removing the .bak, and then will attempt another update.
Success! "Your phone has been upgraded to 5.6.890.en US version". Have lost root, at least for the moment. Will deal with that tomorrow. Last thing to do before going to bed is find the "Thanks" button. Thanks for setting me on the right path. P.
Unable to root after OTA to .890
One click root not longer works. After clicking "run_to_root_your_droid3.sh" on PC (Ubuntu 10.04) I get no prompts on screen, but phone does reboot twice. No su privileges after boot. Busybox is installed in /system/xbin and there is nothing I can do about it as I can't mount r/w. Using Root Explorer and Script Manager as tools.
I realize I'm going to have to increase my learning curve here. Would appreciate any links to relative threads on this topic, or suggestions on what to try next (I have searched, but need some direction).
ok, i have a problem with the g sensor on the samsung captive. now, i've thoroughly searched online and on these forums for a fix, and i've found a few fixes. unfortunately, none of them worked.
before i get into that, here's my phone info:
SAMSUNG-SGH-I897
firmware 2.2
kernal 2.6.32.9
build Cognition 4.3
comp os win7 64bit (if it matters)
now, here is the first fix ive found:
http://androidforums.com/captivate-support-troubleshooting/162768-lost-auto-rotation.html
response #12
ive tried that using terminal emulator, but i get an error saying ADB not found. i downloaded the Android SDK with ADB, navigated to it using the command prompt and typed adb shell as instructed only to get an error saying device not found.
now, i completely abandoned that fix (since i felt i was doing something wrong and going nowhere) and found this one:
http://forum.xda-developers.com/showthread.php?t=712439&page=3
this one had better results, but up until sensorcalibutil_yamaha. like some users on that forum, my result was:
fgets: Unknown error: 0
msmachdep_SaveGsOffset failed
calibration utilities failed
so, after following that forum, i found the solution, which was to delete ms3c_yamaha.cfg from /data/system and rerun. i navigated to that folder on my computer, and nothing. there was no system folder in the data folder. i allowed hidden folders to be visible and still nothing. i downloaded a root explorer app, searched for ms3c_yamaha.cfg and nothing popped up. i couldnt even find the folder it was telling me to look in. and this is where i am stuck.
i cant find ms3c_yamaha.cfg, nor the folder to look into, and i dont know what else to do...
perhaps i'm using the wrong root explorer, or perhaps that folder isnt even on the ROM i used. completely flashing the ROM would be my last resort, since i'm not too savvy on stuff like that, and it took forever for me to figure out how to even put Cog4.3 on my phone, so hopefully someone out there has some info.
thanks for your time
edit:
problem solved!
when i woke up this morning, on my way to work i started thinking about my problem, basically, why couldnt i find the system folder. i searched again in the market for a root explorer and found one that specifically stated "even allows access to the elusive system data folders". i bought the app right away, and immediately i was given access and found ms3c_yamaha.cfg and proceeded with the second solution. after running the calibration, it gave me an odd result, which made my screen rotate when held vertically. i reran the test, and ran the system calibrate (the 3 circles with the blue ball) and all was set. phone works perfectly now.
thanks for anyone who read this, and who was taking the time to find a solution
Hello.
Can you tell me what application explorer you are using?
I got the same problem as yours.
Please reply to my email: [email protected].
Thanks a lot.
Hi All,
Since I am getting nowhere and no replies for my questions, I am going to rephrase them differently here so hopefully someone can jump in and give me a helping hand... (and please forgive if I seem to bombard the forums with questions).
My Note 3 SM-N900A, build KOT49H.N900AUCUCNC2, running 4.4.2. It is having issues with permissions that effectively block the phone from seeing any SD Card, USB, and internal memory space. It won't access any remote resources like internet or Google Play...either
Issues arose after I changed platform.xml. I since then unrooted the phone and uninstalled SuperSU. I can see that these 3 changes were reckless on my part, that I just put the phone into a very bad state that made it very very difficult to recover. I am still banging my head for the blunders but obviously that didn't help fix the phone. :crying:
I would like to know if there is a way to gain access to the phone's system area again to fix the permission issues. Can I use ADB Shell along with USB debugging? If yes, what are the commands I need? Can I somehow send towelroot and SuperSU to the phone via Odin and execute them? The reason I ask this is that I have no way to access any storage area on the phone, and there is no way to go online to download apps. Or can I put the phone into service mode by typing in the *# numbers on the keypad and hopefully fix it there?
Thank you
At this point I'm not even sure if adb would be able to access your memory card to push TowelRoot to it. You might be best off restoring using the stock Odin files, lick your wounds, start over and chalk it up as a learning experience.
http://forum.xda-developers.com/showthread.php?t=2703006
Sent from my AT&T Galaxy Note 3 using Tapatalk®
OK, Something Positive
andygev35 said:
At this point I'm not even sure if adb would be able to access your memory card to push TowelRoot to it. You might be best off restoring using the stock Odin files, lick your wounds, start over and chalk it up as a learning experience.
http://forum.xda-developers.com/showthread.php?t=2703006
Sent from my AT&T Galaxy Note 3 using Tapatalk®
Click to expand...
Click to collapse
Ah, thanks for replying. I was really worrying about that too.
However, I just installed ADT on my PC and connected to the phone via USB debugging. Using the adb shell ls command, I could see the entire directory structure. I was able to get to the system folder too.
I pulled the platform.xml back and attached to this message. Could you or someone please take a look and let me know if anything is wrong in the file? I made very small changes and reverted them. So it should be same as original, but I am not so sure. Also do you know if the encoding of the file is wrong so that Android couldn't read it?
At this point, it appears all is NOT lost. I just need some of your experts to guide me thru the commands needed to regain the access to my SD card or storage from the phone.
Now, let me bring in another point: Prior to having all this snafu, I granted ES File Explorer root access so that I could overwrite the platform.xml file. I don't know if doing that messed up the system. If it did, what would be the most straight forward way, simplest way to try to get back to normal? Provided now adb seems to be able to access the files and directory.
I know I could try install towelroot again, but would like to see if I can bring the system back to normal operation first.
Thanks
I may be wrong, but adb being able to see and pull system files is one thing. To get adb to actually modify system files, you'd need to be able to give adb root access. You may however be able to download the TowelRoot apk to your computer, put it in the same directory as adb, then in the command prompt type "adb push towelroot.apk /data/app/" (without quotes). Reboot and see if TowelRoot installed.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
vbcomer said:
Ah, thanks for replying. I was really worrying about that too.
However, I just installed ADT on my PC and connected to the phone via USB debugging. Using the adb shell ls command, I could see the entire directory structure. I was able to get to the system folder too.
I pulled the platform.xml back and attached to this message. Could you or someone please take a look and let me know if anything is wrong in the file? I made very small changes and reverted them. So it should be same as original, but I am not so sure. Also do you know if the encoding of the file is wrong so that Android couldn't read it?
At this point, it appears all is NOT lost. I just need some of your experts to guide me thru the commands needed to regain the access to my SD card or storage from the phone.
Now, let me bring in another point: Prior to having all this snafu, I granted ES File Explorer root access so that I could overwrite the platform.xml file. I don't know if doing that messed up the system. If it did, what would be the most straight forward way, simplest way to try to get back to normal? Provided now adb seems to be able to access the files and directory.
I know I could try install towelroot again, but would like to see if I can bring the system back to normal operation first.
Thanks
Click to expand...
Click to collapse
Here's the original stock platform.xml if it helps you.
andygev35 said:
I may be wrong, but adb being able to see and pull system files is one thing. To get adb to actually modify system files, you'd need to be able to give adb root access. You may however be able to download the TowelRoot apk to your computer, put it in the same directory as adb, then in the command prompt type "adb push towelroot.apk /data/app/" (without quotes). Reboot and see if TowelRoot installed.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
Click to expand...
Click to collapse
Edit: instead of using adb push, use "adb install towelroot.apk" (if that's the actual package name). Go through the rooting process, download the ES File Explorer apk to your computer install it using adb. Hopefully if all that works, you'll be able to check and fix any permissions that got messed up with your platform.xml. It should be rw-r-r.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
A Step Forward
andygev35 said:
I may be wrong, but adb being able to see and pull system files is one thing. To get adb to actually modify system files, you'd need to be able to give adb root access. You may however be able to download the TowelRoot apk to your computer, put it in the same directory as adb, then in the command prompt type "adb push towelroot.apk /data/app/" (without quotes). Reboot and see if TowelRoot installed.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
Click to expand...
Click to collapse
OK. You are right. adb doesn't have write access yet.
I tried this and got success:
C:\AndroidDev\sdk\platform-tools>adb install tr.apk
1767 KB/s (113099 bytes in 0.062s)
pkg: /data/local/tmp/tr.apk
Success
What should I do next? Does it mean the tr.apk has been installed?
Thanks
Update: I saw the Towelroot app in the App Drawer, but after clicking on it and choosing "make it ralr", I got message "Unfortunately, towelroot has stopped."
vbcomer said:
OK. You are right. adb doesn't have write access yet.
I tried this and got success:
C:\AndroidDev\sdk\platform-tools>adb install tr.apk
1767 KB/s (113099 bytes in 0.062s)
pkg: /data/local/tmp/tr.apk
Success
What should I do next? Does it mean the tr.apk has been installed?
Thanks
Click to expand...
Click to collapse
Sounds as though towelroot is now installed. Go to your app drawer and run it.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
andygev35 said:
Sounds as though towelroot is now installed. Go to your app drawer and run it.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
Click to expand...
Click to collapse
Yeah, it is installed in the App drawer, but running it gave me error "Unfortunately, towelroot has stopped.".
I went ahead and install both ES File Explorer and SuperUser packages. From ES FE, I could look at the /system/ect/permissions/platform.xml and could see that it had a different date, its date is older, 3/15/2014. I think it came with the N900AUCUCNC2 that I flashed with Odin yesterday.
So, it appears the permission come from a different place or source, I would like to know where Android actually sees the permissions. You know, how did it think that it needed to lock down read/write access to storage areas while the /system folder has been replaced.
Thanks
vbcomer said:
Yeah, it is installed in the App drawer, but running it gave me error "Unfortunately, towelroot has stopped.".
I went ahead and install both ES File Explorer and SuperUser packages. From ES FE, I could look at the /system/ect/permissions/platform.xml and could see that it had a different date, its date is older, 3/15/2014. I think it came with the N900AUCUCNC2 that I flashed with Odin yesterday.
So, it appears the permission come from a different place or source, I would like to know where Android actually sees the permissions. You know, how did it think that it needed to lock down read/write access to storage areas while the /system folder has been replaced.
Thanks
Click to expand...
Click to collapse
I'm at the limit of my experience here... Did you do the all in one restore or the 4 file restore?
Sent from my AT&T Galaxy Note 3 using Tapatalk®
andygev35 said:
I'm at the limit of my experience here... Did you do the all in one restore or the 4 file restore?
Sent from my AT&T Galaxy Note 3 using Tapatalk®
Click to expand...
Click to collapse
Thanks for hanging in and helping, you don't know how much I appreciate your time!
I did the all in one first. That didn't help. Then I did it again with the re-partition with PIT file. But that didn't help either. I didn't try the 4 files individually for fear of losing data.
vbcomer said:
Thanks for hanging in and helping, you don't know how much I appreciate your time!
I did the all in one first. That didn't help. Then I did it again with the re-partition with PIT file. But that didn't help either. I didn't try the 4 files individually for fear of losing data.
Click to expand...
Click to collapse
I think you've just about done everything you can do without a complete Odin reinstall and reformat. If adb pull is working for you I suggest pulling the folders you want to save and doing the complete 4 file install with the PIT file as well.
Someone more experienced than I may be able to get you back up without losing your but tbh with the amount of troubleshooting you've done already I think a full Odin reinstall is your best option and will prevent any issues that could stem from this further down the line.
The only thing I can think of with towelroot is that it needs internet access to run were you connected to wifi when you ran it? It's probably not that simple but figured it couldn't hurt to try!
brisinger08 said:
I think you've just about done everything you can do without a complete Odin reinstall and reformat. If adb pull is working for you I suggest pulling the folders you want to save and doing the complete 4 file install with the PIT file as well.
Someone more experienced than I may be able to get you back up without losing your but tbh with the amount of troubleshooting you've done already I think a full Odin reinstall is your best option and will prevent any issues that could stem from this further down the line.
The only thing I can think of with towelroot is that it needs internet access to run were you connected to wifi when you ran it? It's probably not that simple but figured it couldn't hurt to try!
Click to expand...
Click to collapse
Hi there,
Thanks for replying. I am kind of afraid I will have to go down that route, but at the same time trying not to if I could.
One of the other reasons I didn't try the 4 files was because I thought the all-in-one, as its name suggested, would be equivalent to those 4 files.
Is there a way to pull the SMS, MMS, call logs from the phone via adb? Do you know where those records are kept?
Thanks
vbcomer said:
Hi there,
Thanks for replying. I am kind of afraid I will have to go down that route, but at the same time trying not to if I could.
One of the other reasons I didn't try the 4 files was because I thought the all-in-one, as its name suggested, would be equivalent to those 4 files.
Is there a way to pull the SMS, MMS, call logs from the phone via adb? Do you know where those records are kept?
Thanks
Click to expand...
Click to collapse
The all-in-one file is the same as the 4 files, the only difference is installing it doesn't wipe the internal storage.
Have you tried running adb backup? That would be a heck of a lot easier than pulling a bunch of folders...if that doesn't work the databases are in /data/data
Calls: /data/data/com.android.providers.contacts
SMS and MMS: data/data/com.android.providers.telephony
Is there is any shell command to long tap
Hello!
So I have become a crazy cat collector with Nougat. But I recently switched roms so I dont have my beautiful cats anymore. :crying: What files can I copy from my old rom to get them back into my new one?
I found this article:
https://www.reddit.com/r/Android/comments/4tualq/what_i_know_about_cats_the_android_nougat_easter/
It didn't specifically say that cats can be restored but i tried copying the xml file from directory below. But it was a no-go
/root/data/data/com.android.egg/shared_prefs/mprefs.xml
Is there anyway I can be reunited with my cats. Please let me know.
God Bless
-The Cat Lady
You could try backing up the android easter egg app in tibu and restoring data when you flash the rom. I haven't tried it, so if you feel like taking a risk go for it.
CollinsB said:
Hello!
So I have become a crazy cat collector with Nougat. But I recently switched roms so I dont have my beautiful cats anymore. :crying: What files can I copy from my old rom to get them back into my new one?
I found this article:
https://www.reddit.com/r/Android/comments/4tualq/what_i_know_about_cats_the_android_nougat_easter/
It didn't specifically say that cats can be restored but i tried copying the xml file from directory below. But it was a no-go
/root/data/data/com.android.egg/shared_prefs/mprefs.xml
Is there anyway I can be reunited with my cats. Please let me know.
God Bless
-The Cat Lady
Click to expand...
Click to collapse
This might work but it also might crash your phone. Proceed at your own risk.
I was wondering if you ever figured out a way. I'm using a Nexus 5X so it's only a matter of time before the bootloops plague my device. Was hoping to back them up before then.
EDIT:
Would using ADB work?
Code:
adb backup -f "C:\CatsBackup20161229.ab" -apk com.android.egg
EDIT 2:
I was so close. Thanks to this Reddit post, I have used the following in a Windows Batch File to backup my Cats with a timestamp. Hope this helps any Googlers.
Code:
adb root
adb backup -f C:\CatsBackup_%date:~-4,4%%date:~-10,2%%date:~-7,2%.ab com.android.egg -system
What I'd done was long press the cat when one came up then just shared it to my Drive folder. I've also found duplicates will most likely come up (number of the cat) but the cat will be different color.
I've personally flashed numerous different nougat ROMs and different versions (7.0, 7.1, 7.1.1) in no particular order, and the Easter egg cat collection got backed up and restored on each and every ROM I've tried and used.
The way I go about this is, before I decide to switch ROMs or update using clean flash, I use titanium backup to backup the Easter egg app. Once I clean install an update or a different nougat ROM, I first unlock the nougat Easter egg in settings (tap the Android version a bunch and long press on the N animation to find the cat icon). Then head over to quick toggles, hit edit, find the cat toggle and add it to a desired slot. Finally, in titanium backup, find the Easter egg app, hit restore. It will ask what to restore, make sure you select "data only," do NOT restore "app + data," this may or may not cause system UI issues.
Requirements: Nougat ROM of your choice (any version) and root access.
This method works for restoring chrome tabs and possibly a few other system apps' data. Restoring system app(s) + data, however, will usually break things, so make sure to only restore the respective system apps' data only.
okay so i got the easteregg.ab file to back up onto my local disk, but i cannot get my phone to restore the .ab file through ADB.
ADB will say that i must unlock my device and allow the restore to complete however the phone is completely unresponsive to the request to restore, it as if nothing is happening.
what am i missing here :
adb backup -f easteregg.ab com.android.egg -system
(that puts an easteregg.ab file into c\users\xxxx)
then : adb restore c\users\xxxx
(adb then tells me "Now unlock your device and confirm the restore operation)
.....but nothing has happened and it asks for nothing on my phone and the cats are not loaded =(
Permissions. Were they set on the file when you restored it?
Strephon Alkhalikoi said:
Permissions. Were they set on the file when you restored it?
Click to expand...
Click to collapse
im not sure if i know which permissions your refering too, but the easteregg.ab file permissions are currently set to allow full control for the System, Administrator and the User.
How do i ensure the permissions are correct ?>
The permissions were likely completely stripped from the file when it was sent via ADB. You'll need to root and do one of the following.
*Use a terminal app to set permissions.
*Use a file manager with root access, navigate to the file's location, and set permissions manually.
The correct permissions are likely rw-r--r--, which uses the number 644.
Strephon Alkhalikoi said:
The permissions were likely completely stripped from the file when it was sent via ADB. You'll need to root and do one of the following.
*Use a terminal app to set permissions.
*Use a file manager with root access, navigate to the file's location, and set permissions manually.
The correct permissions are likely rw-r--r--, which uses the number 644.
Click to expand...
Click to collapse
My s7 edge is not rooted.
Is there anyway to restore the easteregg kitties with out root ? i thought that was possible.
Did you downgrade from a Nexus 6 to a S7? Sorry to hear that if true, because the S7 has a locked bootloader. The file likely never transferred to where you wanted it to go, as the locked bootloader would prevent that. Thus you need to unlock the bootloader to even transfer the file. ADB may have commands to set file permissions, but my recollection on that is hazy. It would also be irrelevant if the bootloader cannot be unlocked.
Strephon Alkhalikoi said:
Did you downgrade from a Nexus 6 to a S7? Sorry to hear that if true, because the S7 has a locked bootloader. The file likely never transferred to where you wanted it to go, as the locked bootloader would prevent that. Thus you need to unlock the bootloader to even transfer the file. ADB may have commands to set file permissions, but my recollection on that is hazy. It would also be irrelevant if the bootloader cannot be unlocked.
Click to expand...
Click to collapse
oh wow! i pulled up this thread last night and didn't even realize i was on the nexus 6 groups forums haha, boooooo on me =(
no i didnt down grade lol, i never had the nexus, i am just a s7 edge owner who doesn't want to loose their kitties in a phone swap =(
and yeah i had some real difficulties getting the .ab file to even save to my computer after messing around with a bunch of variations on commands through adb.
now im getting depressed again
..hey i REALLY appreciate all this help btw =\
Sorry to hear that. But unfortunately, unless you can unlock the bootloader, you're not going to be able to use ADB to transfer the file back. With a locked bootloader you can pull files, but not push them.
I shoulda realized that cause im not new to the rooting process at all and i hate having a phone with a locked bootloader but i really do like the s7 edge, it grew on me,....... alas my kittens will have to wait till the bootloader becomes available.....
Check the S7 Edge forums. I'm sure they have something that may help.