[Q] Pulled /data/data from phone, how to reverse? - HTC EVO 3D

ok so i was trying to remove an app that was stuck in a FC loop through adb.
in trying to remove the app, it would not let me remove the directory for it under /data/data. so i tried to adb pull and accidentally typed adb pull /data/data <app name> (with a space lol) so now i have that folder on my computer containing all contents of /data/data.
How do i push it all back? adb push <folder name> would simply put the folder there, but everything would remain in it i assume. really dont want to have to push each one individually as i only have 1 hand available atm due to surgery lol.

And I thought driving and texting was bad! You can play with your phone while performing surgery? Now that's talent.
Wish I could help u but I don't know about pushing it back. I'll bump the thread though. g/l

Put a star at the end
Adb push /data/data/*
If that fails wipe data and restore data only in recovery.

wikdNoob said:
And I thought driving and texting was bad! You can play with your phone while performing surgery? Now that's talent.
Wish I could help u but I don't know about pushing it back. I'll bump the thread though. g/l
Click to expand...
Click to collapse
lol I had surgery on my left hand
il Duce said:
Put a star at the end
Adb push /data/data/*
If that fails wipe data and restore data only in recovery.
Click to expand...
Click to collapse
Thanks, ill give that a try
Sent from my PG86100 using Tapatalk 2

il Duce said:
Put a star at the end
Adb push /data/data/*
If that fails wipe data and restore data only in recovery.
Click to expand...
Click to collapse
What's the star for? Curious I am.
#Root-Hack_Mod*Always\

I think the asterisk means the whole directory.
It was bugging me so I looked it up, this is for dos but it might mean the same.
[ * ] (Asterisk) (ASS-ter-isk) (Erroneously referred to as "Star".) DOS uses this as a wild card to represent one or more characters. So "*.txt" would mean all files with an extension of "txt". "READ-ME.*" means all `Read-Me' files with any extension. They typically would be "READ-ME.txt" or "READ-ME.doc".
"A*.txt" means all files with an extension of "txt" that begin with the letter `A'. Some versions of DOS allow an Asterisk at the start, as well: "*-ME.doc" means all files with an extension of "doc" that have "-ME" at the end of the file name.
Some DOS versions use this sign coupled with a percent sign (%*) to represent all parameters on the command line in a batch file.
Another example: DEL A:*.BAK
will delete all files that have the extension .BAK in the current directory of Drive A. The asterisk (*) is a wildcard symbol that means "any string of characters."

wikdNoob said:
I think the asterisk means the whole directory.
It was bugging me so I looked it up, this is for dos but it might mean the same.
[ * ] (Asterisk) (ASS-ter-isk) (Erroneously referred to as "Star".) DOS uses this as a wild card to represent one or more characters. So "*.txt" would mean all files with an extension of "txt". "READ-ME.*" means all `Read-Me' files with any extension. They typically would be "READ-ME.txt" or "READ-ME.doc".
"A*.txt" means all files with an extension of "txt" that begin with the letter `A'. Some versions of DOS allow an Asterisk at the start, as well: "*-ME.doc" means all files with an extension of "doc" that have "-ME" at the end of the file name.
Some DOS versions use this sign coupled with a percent sign (%*) to represent all parameters on the command line in a batch file.
Another example: DEL A:*.BAK
will delete all files that have the extension .BAK in the current directory of Drive A. The asterisk (*) is a wildcard symbol that means "any string of characters."
Click to expand...
Click to collapse
Cudos mate. Thanks
#Root-Hack_Mod*Always\

JWhip804 said:
ok so i was trying to remove an app that was stuck in a FC loop through adb.
in trying to remove the app, it would not let me remove the directory for it under /data/data. so i tried to adb pull and accidentally typed adb pull /data/data <app name> (with a space lol) so now i have that folder on my computer containing all contents of /data/data.
How do i push it all back? adb push <folder name> would simply put the folder there, but everything would remain in it i assume. really dont want to have to push each one individually as i only have 1 hand available atm due to surgery lol.
Click to expand...
Click to collapse
adb pull doesnt erase from phone, it just copy and pastes to computer.
if you want to delete said app from phone you would need to type
adb shell
rm data/data/{choosen app}
exit
adb reboot

steal25 said:
adb pull doesnt erase from phone, it just copy and pastes to computer.
if you want to delete said app from phone you would need to type
adb shell
rm data/data/{choosen app}
exit
adb reboot
Click to expand...
Click to collapse
That was my assumption but when I tried to cd to /data/data, the directory no longer existed.
Sent from my PG86100 using Tapatalk 2

JWhip804 said:
That was my assumption but when I tried to cd to /data/data, the directory no longer existed.
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
Is it possible to cd to this directory??? I thought it would be the adb shell LS command.

Related

[Q] Please help me... (problems with md5sum mismatch)

Hello,
I am having a major problem... earlier today i made a backup of my ics'd out v8 rom in order to try the new CM7 Kang. I got the kang running but needed to install gapps. For some reason rom manager was not letting me install it from there because it wasn't an updated version of rom manager and i couldn't get an updated version. So i figured I would go back to my ics'd rom, download gapps on the sdcard, and then go back to cm7 to install... NOPE.
Every time I try to restore my backup I get md5 mismatch error. I went through a bunch of different threads for different phones and tried all the adb stuff it said and nothing worked. For some reason when I ran the command (given here http://forum.xda-developers.com/showthread.php?t=714114) "cd /sdcard..." the pound # changed to a > and everything I typed would just be repeated back at me. The phone never even asked for superuser permission. I am pretty sure that I have the adb stuff right since when I type in "adb devices" in command I see the device, but I just have no clue how to fix this. Maybe the instructions given on this page only applies to that particular phone?
I would really like to be able to recover this backup and if anyone has instructions on how to fix this error on this phone it would be very much appreciated.
Thanks!
ADB was working if you got a # prompt
Custom kernels are almost all "insecure" kernels - ADB sessions automatically have root permissions.
This was the case for you - a # prompt means you have root privileges.
A $ prompt means you don't
A > prompt means that something you typed on the previous line made the shell decide you wanted to type more before executing the command. Control-C will break out of this. So if you got a > prompt after the "cd /sdcard/clockworkmod/backup/blahblah" command - you mistyped something on that line. Possibly you put a ; in there by accident, or you have opening quotes without closing quotes
There is a comment later in that thread "the folder name for your backup couldn't have spaces in it" - Weird characters in the directory name would be a possible cause of your cd command failing.
CWM should never have created a folder name that behaves like this, unless you did a nandroid backup using ROM Manager. If you did - another reason NOT to use ROM Manager.
Did you change the file name of the backup? make sure there is no spaces in file name. hope this help.
I would just download gapps to computer then move the file to phone. Then reboot into cwm and flash galls.
Sent from my SAMSUNG-SGH-I777 using XDA App
Artimus009 said:
I would just download gapps to computer then move the file to phone. Then reboot into cwm and flash galls.
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Code:
adb push
is your friend - great way to put a file on the phone when it's in recovery
Entropy512 said:
ADB was working if you got a # prompt
Custom kernels are almost all "insecure" kernels - ADB sessions automatically have root permissions.
This was the case for you - a # prompt means you have root privileges.
A $ prompt means you don't
A > prompt means that something you typed on the previous line made the shell decide you wanted to type more before executing the command. Control-C will break out of this. So if you got a > prompt after the "cd /sdcard/clockworkmod/backup/blahblah" command - you mistyped something on that line. Possibly you put a ; in there by accident, or you have opening quotes without closing quotes
There is a comment later in that thread "the folder name for your backup couldn't have spaces in it" - Weird characters in the directory name would be a possible cause of your cd command failing.
CWM should never have created a folder name that behaves like this, unless you did a nandroid backup using ROM Manager. If you did - another reason NOT to use ROM Manager.
Click to expand...
Click to collapse
Thanks for the reply! Yeah that would make sense but I copied the file path directly from windows explorer and I checked for spaces too... Yeah I only do backups straight from CWM.
getbuzzin said:
Did you change the file name of the backup? make sure there is no spaces in file name. hope this help.
Click to expand...
Click to collapse
I did change the name from the original name, I added like "ics'doutv8siyah2.6.1blahblahblah" to the beginning so that I could distinguish which backup was which. Could this make a difference? I mean I have done this before without issue.
Shadow12347 said:
Thanks for the reply! Yeah that would make sense but I copied the file path directly from windows explorer and I checked for spaces too... Yeah I only do backups straight from CWM.
I did change the name from the original name, I added like "ics'doutv8siyah2.6.1blahblahblah" to the beginning so that I could distinguish which backup was which. Could this make a difference?
Click to expand...
Click to collapse
Change it back and see if it works
Only letters, numbers and periods. the ' is probably to blame.
Sent from my SAMSUNG-SGH-I777
Well I deleted the beginning and it looked like it was going to work because it was checking md5 sums for a while and then it said md5 mismatch. But it wasn't instant like the other times.
I think I read on one of the pages that you could take the nandroid.md5 from another backup and replace it with the one in the nonworking backup, is this true and would it work?
Ok nevermind, I forgot to do the ADB thing again xD it worked... THANK YOU SO MUCH!
karth500 said:
Only letters, numbers and periods. the ' is probably to blame.
Sent from my SAMSUNG-SGH-I777
Click to expand...
Click to collapse
Most likely.
I usually rename my backups manually to something like romname_date in ADB
e.g.
villainrom_1224
I NEVER put spaces or other characters in the rom name
Right now I think I have:
modstock_1128
villainrom_1224
uckk6_1224
one other ROM...
Ok guys I'm sorry, it happened again... except this time I think it may be a problem with ADB. When I am in adb shell, it shows up as "~ #" instead of just "#", however, typing "su" changed it to just "#". However, in both instances ("~ #" and "#") it gets an error:
~ # cd /sdcard/clockworkmod/backup/2012-01-22.18.04.05
cd /sdcard/clockworkmod/backup/2012-01-22.18.04.05
/sbin/sh: cd: can't cd to /sdcard/clockworkmod/backup/2012-01-22.18.04.05
and
# cd /sdcard/clockworkmod/backup/2012-01-22.18.04.05
cd /sdcard/clockworkmod/backup/2012-01-22.18.04.05
cd: can't cd to /sdcard/clockworkmod/backup/2012-01-22.18.04.05
This is the original name, there are no spaces, I checked the driver for the phone, etc.
Anyone got any ideas?
Oops double post -_-
Try tab-completion (type part of a directory name and hit tab - sometimes it works and sometimes it doesn't, usually should work when ADBing into CWM), and use "cd" and "ls" to navigate through directories instead of just pasting the whole path.
ls = same thing as dir in DOS
Alright so I did that and found out the sdcard isn't mounting...
C:\android-sdk-windows\platform-tools>adb shell
~ # su
su
# ls
ls
acct fota.rc recovery.rc
app-cache init res
cache init.goldfish.rc sbin
config init.rc sdcard
customkernel init.smdkc210.rc sys
d init.smdkv310.rc system
data init_kernel_only.rc tmp
dbdata lib ueventd.rc
default.prop lpm.rc ueventd.smdkc210.rc
dev misc ueventd.smdkv310.rc
efs mnt vendor
etc proc
# cd /mnt
cd /mnt
# ls
ls
asec obb sdcard secure usb
# cd /sdcard
cd /sdcard
# ls
ls
#
I also went into root explorer and it said "SD card is not currently mounted"
...uhhh I feel like a noob to ask this but, how do you mount it? xD
The thing is, though, that it dismounts when I plug it into the computer to transfer files/adb, but it is mounted afterwards...

[Q] Is there an easier way to move files?

Currently, if I want to add a new custom wallpaper. I make it on my PC using GIMP, save it, plug in my reZound, switch to disk drive, copy the file to my sd card, unplug my reZound, go to ES File explorer, navigate to ex_sd, copy the file, navigate to /system/customize/resources, paste the file, go to home, change wallpaper. Now, I can do all that faster than I can type out the steps, but is there someway to move the file straight from my PC to the /system/customize/resources folder?
Thanks
pmterp said:
Currently, if I want to add a new custom wallpaper. I make it on my PC using GIMP, save it, plug in my reZound, switch to disk drive, copy the file to my sd card, unplug my reZound, go to ES File explorer, navigate to ex_sd, copy the file, navigate to /system/customize/resources, paste the file, go to home, change wallpaper. Now, I can do all that faster than I can type out the steps, but is there someway to move the file straight from my PC to the /system/customize/resources folder?
Thanks
Click to expand...
Click to collapse
Just put them on your sd card in a folder called /media/images/ and you can apply them with the gallery
NilsP said:
Just put them on your sd card in a folder called /media/images/ and you can apply them with the gallery
Click to expand...
Click to collapse
Or I think he can push with adb. I don't know the exact commands so if anyone can help with the commands...
Sent from my ADR6425LVW using Tapatalk
xxxxxx.png is the name of the image:
adb push xxxxxx.png /system/customize/resource
NilsP said:
xxxxxx.png is the name of the image:
adb push xxxxxx.png /system/customize/resource
Click to expand...
Click to collapse
Probably need to adb remount first. Here's my suggestion, make a batch file/script something like this:
echo off
adb wait-for-device
adb remount
adb push somdirectory/newwallpaper.png /system/customize/resource/
MrSmith317 said:
echo off
adb wait-for-device
adb remount
adb push somdirectory/newwallpaper.png /system/customize/resource/
Click to expand...
Click to collapse
That works great. Thanks everyone. Now, what about the reverse? Is there a way to get the files (default wallpapers, apks, etc.) pushed to my computer? I tried running the same script and reversing the file and destination but that did not work.
Edit: Never mind, found it. adb pull
I haven't used adb commands since I was rooting my eris, thanks guys.

Edited build.prop; phone now hangs during boot

Well I've had my first issue with my shiny new handset! I rooted it this afternoon and decided to modify the build.prop to change the dalvik heap size as recommended by various people. However on rebooting, the phone's now hanging on the splash screen.
I can get into download and recovery ok - any ideas on how to fix this? Is build.prop editable in either of these modes?
If you have adb, boot in to CWM, adb pull /system/build.prop
Edit the file, please note that if you're on windows, DO NOT USE WORD or anything similar, it'll mess up your line endings (Newline Format), I suspect this is what happened in the first place.
In any case, if you need to edit the file in plain notepad, download "ToFroDos" and run todos on the file before editing,
then edit, then run fromdos on the file, then adb push it back on to the device.
Note on Re-uploading: you may need to execute adb remount rw in order to upload the file.
In any case, short form:
1. Boot to recovery
2. adb pull /system/build.prop
3. Edit locally (Making sure to keep the proper newline format (\n))
3.5 adb remount rw
4. adb push ./build.prop /system/build.prop
As said extract the original one from the rom and push it manually via adb push command
Sent from my GT-I9300 using Tapatalk 2
Oddly enough I used the build.prop editor app from the Play store. Seems that the issue was that it didn't put an 'm' at the end of the line specifying the size - so it read as '128'. Anyway, I've done what you suggested, and it worked - excellent stuff, thanks!
Next time, just use Jota Text Editor on your phone
I have use it many times to edit my build.prop file and never have issue
I tried adb pull /system/build.prop, but the build.prop file doesn't appear anywhere on my PC, so I can't edit it. My device appears in adb devices, and the command line responds with "718 KB/s (2943 bytes in 0.004s)" when I enter "adb pull /system/build.prop", but I can't find it
guitarplayer365 said:
I tried adb pull /system/build.prop, but the build.prop file doesn't appear anywhere on my PC, so I can't edit it. My device appears in adb devices, and the command line responds with "718 KB/s (2943 bytes in 0.004s)" when I enter "adb pull /system/build.prop", but I can't find it
Click to expand...
Click to collapse
Make sure you're not in a readonly directory on the host,
a default cmd in windows will start in the dir of %ComSpec% (Usually C:\windows\system32).
Abd will try to put files wherever you're located in you filesystem, unless you tell it otherwise. (adb pull {source} [destination])
Sent from my GT-I9300 using XDA
T0yK4T said:
If you have adb, boot in to CWM, adb pull /system/build.prop
Edit the file, please note that if you're on windows, DO NOT USE WORD or anything similar, it'll mess up your line endings (Newline Format), I suspect this is what happened in the first place.
In any case, if you need to edit the file in plain notepad, download "ToFroDos" and run todos on the file before editing,
then edit, then run fromdos on the file, then adb push it back on to the device.
Note on Re-uploading: you may need to execute adb remount rw in order to upload the file.
In any case, short form:
1. Boot to recovery
2. adb pull /system/build.prop
3. Edit locally (Making sure to keep the proper newline format (\n))
3.5 adb remount rw
4. adb push ./build.prop /system/build.prop
Click to expand...
Click to collapse
How do I do ADB pull/push if I can only get to the stock recovery screen? (The one with Mr. Android on his back with the ! above him)
BTW, I'm on a Note 3
Check the permissions!!!!!
The build.prop file should have 644 permissions.
Check if it fits, else change them using adb.
See other thread
http://forum.xda-developers.com/showthread.php?t=1927198

[Q] Remove annoying CDROM mounts?

I tried to search but didn't see anything here. I remember having this issue on another phone but forgot how to fix (not an issue with my Nexus or S3). So anyone figured out how to stop the annoying images from mounting everytime I plug in USB?
I believe you need to remove the CD.iso file.
Once I get my DNA I'll make a bloat free ROM with that and vol wake fixed.
Sent from my ADR6425LVW using xda app-developers app
they are in the \etc folder labled cdrom.iso and PCTool.iso
crackeyes said:
they are in the \etc folder labled cdrom.iso and PCTool.iso
Click to expand...
Click to collapse
Yup, delete those and no more annoying pop-ups.
Sorry to hijack a topic, but I didn't want to create another forum for the same question.
But, how can this be made possible? Do we have to wait for S-Off? (Still kind of new to this whole thing)
I have tried deleting the .ISO files through Root Explorer, no avail.
I tried to use Rexdog's De-Bloating Mod modified slightly to indicate a deletion of the two .ISO files. (I left everything the same except for the "/META-INF/com/google/android/updater-script" File.)
I modified that single file to say this,
Code:
ui_print("Removing Bloatware");
run_program("/sbin/mount", "/dev/block/mmcblk0p32", "/etc");
package_extract_dir("etc", "/etc");
show_progress(1, 15);
delete("/etc/CDROM.ISO", "/etc/PCTOOL.ISO");
ui_print("Unmounting Filesystems . . .");
unmount("/etc");
ui_print("Finished");
I was going off on a whim by editing the single file and hoping that it would work, but it doesn't appear to have worked. Is there something I was missing, or something else?
BigRed35m said:
Sorry to hijack a topic, but I didn't want to create another forum for the same question.
But, how can this be made possible? Do we have to wait for S-Off? (Still kind of new to this whole thing)
I have tried deleting the .ISO files through Root Explorer, no avail.
I tried to use Rexdog's De-Bloating Mod modified slightly to indicate a deletion of the two .ISO files. (I left everything the same except for the "/META-INF/com/google/android/updater-script" File.)
I modified that single file to say this,
Code:
ui_print("Removing Bloatware");
run_program("/sbin/mount", "/dev/block/mmcblk0p32", "/etc");
package_extract_dir("etc", "/etc");
show_progress(1, 15);
delete("/etc/CDROM.ISO", "/etc/PCTOOL.ISO");
ui_print("Unmounting Filesystems . . .");
unmount("/etc");
ui_print("Finished");
I was going off on a whim by editing the single file and hoping that it would work, but it doesn't appear to have worked. Is there something I was missing, or something else?
Click to expand...
Click to collapse
try to make the .iso in lowercase. That is the way it showed up on mine,
BigRed35m said:
I have tried deleting the .ISO files through Root Explorer, no avail.
Click to expand...
Click to collapse
I just deleted those 2 files through root explorer, and plugged in usb to pc. no more pop-ups.
jasonpascoe said:
I just deleted those 2 files through root explorer, and plugged in usb to pc. no more pop-ups.
Click to expand...
Click to collapse
That's only going to work until you reboot. /system is write protected. You have to go onto recovery mount /sys as writeable and use adb to delete the 2 files.
str8upx said:
That's only going to work until you reboot. /system is write protected. You have to go onto recovery mount /sys as writeable and use adb to delete the 2 files.
Click to expand...
Click to collapse
You are indeed knowledgable. You don't happen to know a place where i can fnd instruction on how to do that, would you? (for a noob?)
BigRed35m said:
You are indeed knowledgable. You don't happen to know a place where i can fnd instruction on how to do that, would you? (for a noob?)
Click to expand...
Click to collapse
Make sure you install the htc drivers (htc sync is not required) which is the first option when you plug in your phone to the pc.
Assuming you have usb debugging enabled and downloaded the android sdk http://developer.android.com/sdk/index.html#win-bundle and extracted the zip.
Navigate to the platform-tools folder inside /adt-bundle-windows-x86_64/sdk/platform-tools/
In an empty space inside that folder hold down shift and right click, then select open command window here.
Now in the command window type:
adb devices (your devices serial # should be displayed)
adb reboot recovery
On the phone select: mounts and storage, then: mount /system
Now in the command window type each of the following:
adb pull /system/etc/CDROM.ISO
adb pull /system/etc/PCTOOL.ISO
adb remount
adb shell
rm /system/etc/CDROM.ISO
rm /system/etc/PCTOOL.ISO
exit
adb reboot
You have now made copies of both of these files on to your pc and removed them from your phone.
To restore these files open a command window and mount /sys in recovery as shown above then:
adb push CDROM.ISO /system/etc
adb push PCTOOL.ISO /system/etc

[GUIDE] Get 48 GB Free promotional Dropbox space

I saw a post in this thread about getting the promotional space on AT&T S4 without flashing TMobile roms. I gave it a try, and it worked just fine. So I thought of sharing the files with you. I pulled them out of a deodexed TMobile rom.
Download the attached file. You need to push Dropbox.apk and DropboxOOBE.apk into system/app and fix permission. Then you need to push com.dropboxpartner into system/framework and again fix permission.
Then, you need to modify the build.prop using a root explorer. Find the following lines and modify them as follow:
ro.product.model=SGH-M919
ro.product.name=jfltetmo
ro.product.device=jfltetmo
Reboot your device, open the Dropbox app, and log in with your existing account, or create a new account. You will receive an email, and after fulfilling 5 of the 7 tasks, you will receive the 48 GB promotional space. After fulfilling the tasks, you can restore your build.prop to its original state.
Attached Files:
http://d-h.st/fZJ
smnfriend said:
I saw a post in this thread about getting the promotional space on AT&T S4 without flashing TMobile roms. I gave it a try, and it worked just fine. So I thought of sharing the files with you. I pulled them out of a deodexed TMobile rom.
Download the attached file. You need to push Dropbox.apk and DropboxOOBE.apk into system/app and fix permission. Then you need to push com.dropboxpartner into system/framework and again fix permission.
Then, you need to modify the build.prop using a root explorer. Find the following lines and modify them as follow:
ro.product.model=SGH-M919
ro.product.name=jfltetmo
ro.product.device=jfltetmo
Reboot your device, open the Dropbox app, and log in with your existing account, or create a new account. You will receive an email, and after fulfilling 5 of the 7 tasks, you will receive the 48 GB promotional space. After fulfilling the tasks, you can restore your build.prop to its original state.
Attached Files:
http://d-h.st/fZJ
Click to expand...
Click to collapse
Worked great for me, thanks! I already had 12GB and had completed the 5 Getting Started steps long ago. When I signed into the DropBox app and got it setup, I suddenly had 60GB for 24months and an email from DropBox.
Here's the instructions I followed:
Cleared cache of, cleared data of, and uninstalled the DropBox app I already had.
Reminder: backup your build.prop
I ended up using this build.prop Editor. When you open it, use the menu key to make a backup before touching anything. Then scroll through and make the changes prescribed in the OP.
Downloaded the file attached in OP.
Extracted files using my computer to my internal sdcard. Possible to do this with apps on your phone (various file explorers or unzip programs), but I found it easier to just do it over USB/MTP.
Fired up ADB Shell - could also use a terminal emulator from the device, but do not use the "stop" command below if you are using an emulator on the device.
Performed the following commands (after running "adb shell" from a command line on the computer):
Code:
$ su
# mount -o rw,remount /system
# stop
# cp /sdcard/Dropbox.apk /system/app
# cp /sdcard/DropboxOOBE.apk /system/app
# cp /sdcard/com.dropboxpartner.jar /system/framework
# reboot recovery
Device rebooted into TWRP, where I used the Advanced menu to Fix Permissions.
Rebooted back into the System like normal.
Opened the DropBox app and signed in. Setup the camera sync again of course (awesome feature).
Checked my mail - Woot.
Used the build.prop editor to restore my build.prop
Closed the build.prop editor and re-opened. For some reason after restoring the backup, the restored changes were not reflected until I restarted the editor. Whatever, but it worked.
Worked for me:thumbup: Thanks! Now what to do after the two year promo period ends...
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
I'm already up to 50GB on doing something like this before. I'm not sure if it'll work again but I'll give it a whirl sometime today. Will report back if I find myself up to 98GB.
Perfectly working.
Followed general instructions (used FX root explorer instead of Android Terminal for dropping apks in designated locations) and this worked just fine without a hitch. I appreciate the straightforward and simple instructions.
All I did was flash Wicked (T-Mobile ROM) then KTOONSEZ touchjizz kernel. After getting my free dropbox space, I flashed back.
Sent from my SGH-I337 using xda premium
lol same here with GOLD3N3Y3 rom; any non-ATT rom works if you DL and activate it. i have my own server so im letting everyone in my family use it for our stuff.
Slade8525 said:
lol same here with GOLD3N3Y3 rom; any non-ATT rom works if you DL and activate it. i have my own server so im letting everyone in my family use it for our stuff.
Click to expand...
Click to collapse
i can confirm that this works on vzw.
Thanks, worked great on my VZW S4.
Aou said:
Worked great for me, thanks! I already had 12GB and had completed the 5 Getting Started steps long ago. When I signed into the DropBox app and got it setup, I suddenly had 60GB for 24months and an email from DropBox.
Here's the instructions I followed:
Cleared cache of, cleared data of, and uninstalled the DropBox app I already had.
Reminder: backup your build.prop
I ended up using this build.prop Editor. When you open it, use the menu key to make a backup before touching anything. Then scroll through and make the changes prescribed in the OP.
Downloaded the file attached in OP.
Extracted files using my computer to my internal sdcard. Possible to do this with apps on your phone (various file explorers or unzip programs), but I found it easier to just do it over USB/MTP.
Fired up ADB Shell - could also use a terminal emulator from the device...
Performed the following commands:
Code:
$ su
# mount -o rw,remount /system
# stop
# cp /sdcard/Dropbox.apk /system/app
# cp /sdcard/DropboxOOBE.apk /system/app
# cp /sdcard/com.dropboxpartner.jar /system/framework
# reboot recovery
Device rebooted into TWRP, where I used the Advanced menu to Fix Permissions.
Rebooted back into the System like normal.
Opened the DropBox app and signed in. Setup the camera sync again of course (awesome feature).
Checked my mail - Woot.
Used the build.prop editor to restore my build.prop
Closed the build.prop editor and re-opened. For some reason after restoring the backup, the restored changes were not reflected until I restarted the editor. Whatever, but it worked.
Click to expand...
Click to collapse
Using terminal emulator, after using #stop, device screen goes black... what do I do, just wait?
Cinosinu said:
Using terminal emulator, after using #stop, device screen goes black... what do I do, just wait?
Click to expand...
Click to collapse
You need to do it from your computer terminal/shell using adb shell command through the USB, not using a terminal emulator on the device. Stop does exactly what it says, it stops the device from running I think , or maybe just pauses.
You should be able to copy the files without stop though, it's probably riskier, and then you need to use reboot. You just need to copy the files into the right locations and then fix the permissions.
Cinosinu said:
Using terminal emulator, after using #stop, device screen goes black... what do I do, just wait?
Click to expand...
Click to collapse
These are linux commands. Stop, stops your device, and you cannot use it unless you reboot it. You can punch in the commands through your computer (this way, you need to install android sdk. Then, open the installed folder, and go to sdk\platform-tools. Here, you should hold shift, right click and select "open command window here", and punch the commands). Also, you can simply use a root explorer, and manually move the files to their folders and fix permissions
Just pull the battery and reboot. It happened to me also.
Sent from my SGH-M919 using xda premium
smnfriend said:
Also, you can simply use a root explorer, and manually move the files to their folders and fix permissions
Click to expand...
Click to collapse
What does this mean? I have ES fie explorer, trying to move the files I get a rewrite error. Do i need to fix the permissions first? What is the adb command?
thanks
I got it!!! :victory:
Why didn't someone tell me you must use the command 'ADB Shell' to start?
I'm no expert with ADB obviously. Knew it was something trivial. Hope someone else finds my comment helpful. :highfive:
Thank you OP and all! XDA rocks!
Thanks for pointing these things out. Yes, "stop" should only be used if doing this from an ADB shell. I've updated my instructions a tad bit to reflect this.
How can i do this for multiple accounts? I logged out and in and no luck.
Sent from my SGH-M919 using xda premium
kalparker said:
How can i do this for multiple accounts? I logged out and in and no luck.
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
did you do a factory reset, re-install of your ROM, then the steps again? that may help by giving you a different device ID (you may have had this warning before in TiBU), which i'm guessing DB is looking for to limit 1 upgrade per device ID.
-rf
xrabbitfootx said:
did you do a factory reset, re-install of your ROM, then the steps again? that may help by giving you a different device ID (you may have had this warning before in TiBU), which i'm guessing DB is looking for to limit 1 upgrade per device ID.
-rf
Click to expand...
Click to collapse
That might work. In TiBu, I have the option to create a new, random device ID - might be a Pro feature only. Check your menu key, and near the bottom you can Manager your Device ID...
I would advise a nandroid backup first - this may screw up some of your other accounts, including Google. I've personally never tried it, but I would imagine it could cause some amount of chaos.
thanks!

Categories

Resources