OK, so I decided to try the modified build.prop (as described on modaco) on my 2.1 O2 Streak (build 8105). It's rooted and engineering mode is activated.
Downloaded from the link, removed the html bits (checked against the standard build.prop for where it should start and finish), saved as build.prop
copied it to sd card then used root explorer to copy and paste it into the system folder, after choosing "mount R/W". chose "replace existing file" when asked.
restarted and it hangs at the "Dell" boot screen. Fires up, shows Dell logo, goes blank and then shows the logo again kinda permanently
Sooo I'm guessing i've done something wrong with the build.prop? Can anyone put me right with what it SHOULD be (the modified version that speeds things up etc) or what I should have done differently?
Can't do anything now til I get home (I KNOW I KNOW trying it at work was a bit daft, but I have my backup Sony X1 in the car so it's not a total disaster! )
I've also got the pdf of "things you need to know about the streak". Armed with this and the correct build.prop will I be able to fix it or do i need to do a recovery with an update.pkg?
thanks in advance for any help!!
get the proper build.prop
there shouldn't be a need to clear off html stuff unless its been grabbed wrong.
get your original build.prop (or another one) such as http://android.modaco.com/index.php?act=attach&type=post&id=62881 which is the original 8105
connect adb
Code:
adb push build.prop /sdcard/build.prop
adb shell
su
mount -o remount,rw /etc
cp /sdcard/build.prop /etc/
mount -o remount,ro /etc
exit
adb reboot
tbh you don't need the entire build.prop from steve, just change
debug.sf.hw=1
and the dalvik cache to 64m
using root explorer (there's a built in text editor)
thanks for that - much appreciated!
i don't think the PC suite has been recognising the streak since the 2.1 update. will adb work ok with it, assuming i've done all the other bits (downloading drivers etc)
fortunately i did back up my original build.prop (renamed copy_build.prop) to the sd card so I can recover that through a card reader at home...
gotcha re: the mods using root explorer. Will try that once i've recovered it (assuming i can of course!!)
thank you again for the assistance!
woohoo!
recovered (reinstall tho, but it's kept my contacts?!).
build.prop modified using root explorer's text editor. not sure if it's any different yet as i fell asleep before I could test it
thanks for the tips, fards!
Update: Ahh yes it DOES improve it! Videos are much smoother (ie if a shot "pans" it now does it smoothly and not with jerking like it was doing. Wasn't BAD before but is definitely improved). Seems a bit snappier too. I'm probably hoping for too much now but does it help psx4droid at all?
kept the dalvik cache set to 40mb. no issues yet.
triondave said:
snip..
recovered (reinstall tho, but it's kept my contacts?!).
Click to expand...
Click to collapse
yep because if you were singed into google it syncs contacts to google and retrieves them when you log back in
Ahh that makes sense - thanks!
btw lovin it after the mod. videos really are fantastic now. no major increase in psx4droid but i presume that's using 3d rather than 2D? and it really needs updating to utilise the graphics hardware, from what i've read..
Related
Im looking to take a go at some theme making / startup shows. Ive done some looking but I can't find a definitive guide on pulling the framework-res.apk. I have found some how-too on modifying the files contained inside but most assume you already have a pretty solid understanding of abd. Mine is basic so if someone was willing to right out the abd commands for pulling it, backing it up (im guessing just a right click and copy), and then putting the original / modified (if different) back in, it would be much appreciated.
Not much in the line of themes for the Streak so far, so although it take me a while, im willing to do some work.
Any help is appreciated.
Ok I have been looking around and since no one has provided any info/insight ill post what ive found here and perhaps "someone" could be kind enough to just verify.
Pulling "framework-res.apk":
adb pull /system/framework/framework-res.apk
Pushing "framework-res.apk":
adb shell remount rw
adb push framework-res.apk /system/framework/
I also found this code for remount (not sure which is more appropriate?):
adb shell mount -o rw /dev/block/mtdblock1 /system
Also has anyone tried using this:
http://forum.xda-developers.com/showthread.php?t=737526
i was looking to change the bootscreen and in the process i found 'rootexplorer' together with z4root working great. you can copy the files to sdcard (i use usb, but bluetooth or wifi works also) and from there to the system dir.
dell splash logo
you have themed the dell splash logo @ power on? Sweet! can you tell us where it is located?
maybe a short vid to see it in action.
Yes I cant wait do debrand my streak,
chrisrotolo said:
you have themed the dell splash logo @ power on? Sweet! can you tell us where it is located?
maybe a short vid to see it in action.
Yes I cant wait do debrand my streak,
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=859009
please dont hijack the poor man's thread lol
Ha, ha @da_jojo. I suppose that should be happy that sooomeone posted any reply in this thread. Im going to have a look at the boot animation you posted as that was something else id like to try tackling in the future as well. Although I have to admit I was a little bummed that no one could confirm my questions. Just keeping trying on my own I guess.
Sent from my Dell Streak using XDA App
brunswick000 said:
Ha, ha @da_jojo. I suppose that should be happy that sooomeone posted any reply in this thread. Im going to have a look at the boot animation you posted as that was something else id like to try tackling in the future as well. Although I have to admit I was a little bummed that no one could confirm my questions. Just keeping trying on my own I guess.
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
yeah same here.. information sharing is limited to helpdeskfunctionality nowadays lol
the method i used works great and doesnt require a pc to use. the adb commands should be fine i guess.remount the dir should do. im not to sure about the block remount. you can remount system in adb with :
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock6 /system
after some fiddling i found out that bootanimations installer for droid x works good.
You don't neccessarily need a knowledge of ADB to theme. You could just open up Steve's ROM, edit what you want and sign it again (each .zip inside the update.zip must be signed also).
Then you just flash it through recovery.
Meltus said:
You don't neccessarily need a knowledge of ADB to theme. You could just open up Steve's ROM, edit what you want and sign it again (each .zip inside the update.zip must be signed also).
Then you just flash it through recovery.
Click to expand...
Click to collapse
yu, but i think its more handy to just copy the file over with rootexplorer, for testing. the end-product can then be implented in the update if required , the way you describe it.
Ok sounds good. Ill give it a try tomorrow if I have some down time at work. Cant wait to get to work on something for this beast.
Hello all.
Well, here is my problem. I was searching for some theme to change the "colors" of the menu of my device. SInce i couldn't find one, i just started to read a lot, and try to do it myself.
Well, I followed the instructions... and finally got my framework-res. The only problem was that the size of the file was lower thatn the original one. Anyway, I just went to root explorer, took my new framework-res.apk and replaced it on framework folder in internal storage.
The problem is that now my device won't start, I mean... it's stuck on the samsung logo, doing the animation over and over and over. Well I tried to get to the original framework-res, but I don't know how since I cannot replace things because I can't use a file explorer.
I searched some themes on the forum, thinking that maybe the framework-res would be replaced for the new one, and then it would work. Well it doesnt.
I have kph rom, and tried with "Dark simplify theme" and "circle battery kph" couse it's supposed to be stock theme with the circle battery...
Now, I dont know what to do, I dont know how to make an update.zip myself (I tried searching and learning but i just don understand).
I think i would reflash my system but, My internal partition was transformed to ext4 with cf-root, and I read a lot that If i want to flash any other rom, I have to change it to rfs first, but i can't do it couse i can't get to the ext4manager application.
So any ideas? please?
Thanks in advance.
ps: okay, i was a little desesperated when I wrote this (i still am). I searched for some with ext4 compatiblity. I have just tried gingerReal now. It's working. I'm gonna change the internal storage to rfs again, and flash kph.
Bootloop is really common here
you don;t need to reflash, if you have working framework-res.apk you just need to raplace it..
copy framework-res.apk to your sdcard
connect your phone to computer when in recovery
mount system partition using CWM
then using adb follow this command
adb shell
su
cd /sdcard
cp framework-res.apk /system/framework/
reboot
done
also if you reflash your ace using odin to stock one, ext4 partition automatically reverted to rfs
seilent said:
Bootloop is really common here
you don;t need to reflash, if you have working framework-res.apk you just need to raplace it..
copy framework-res.apk to your sdcard
connect your phone to computer when in recovery
mount system partition using CWM
then using adb follow this command
adb shell
su
cd /sdcard
cp framework-res.apk /system/framework/
reboot
done
also if you reflash your ace using odin to stock one, ext4 partition automatically reverted to rfs
Click to expand...
Click to collapse
Hi thanks for the answer. About the adb, that is supossed to be used in a pc, right? (sorry I never used it, i have just used terminal emulator in the device itself). I mean, I enter cmd, write adb shell and i'm in? (i have already installed sdk and all the neccesary things)
About the ext4 to rfs, well thanks! nice to know that ahaha . I have already flashed kph again, so it's all working now. But the next time, I'll do what you say. I guess I already know about adb shell, but I dont know how to use it (i get easily confuse when it comes to apply commands). Well, that's what I love of all of this. You screw things up, you get really nervous, but then you know you can solve it and it is the best ahaha.
Thank you!.
I have an AT&T Atrix 4G with system version 4.5.91 and android version 2.3.4. I am a Noob to the Android platform and researched this extensively on the web but I am still unsure about how to or if I need to Deodex my phone. I have rooted the phone using Petes Motorola Root Tools v1.05 (worked awesome) and downloaded several recommended apps for rooted phones. I want to use the modification to unlock the Webtop using the HDMI cable without the dock (http://forum.xda-developers.com/showthread.php?t=980193). All web sites say the phone needs to be deodexed before performing this modification. Is my phone already deodexed? Do I need to deodex my Atrix? Is there an auto-deodexer program that will work for this phone? How do I back everything up before deodexing my phone (I use Titanium Backup app)? Any help would be greatly appreciated and sorry for being a Noob! I LOVE this Phone!!!! Might even have to get rid of the ole lady so I can spend more time with my Atrix 4G!!! LOL
http://forum.xda-developers.com/showthread.php?t=1162764&highlight=how+to+deodex
Atrix4guser said:
I have an AT&T Atrix 4G with system version 4.5.91 and android version 2.3.4. I am a Noob to the Android platform and researched this extensively on the web but I am still unsure about how to or if I need to Deodex my phone. I have rooted the phone using Petes Motorola Root Tools v1.05 (worked awesome) and downloaded several recommended apps for rooted phones. I want to use the modification to unlock the Webtop using the HDMI cable without the dock (http://forum.xda-developers.com/showthread.php?t=980193). All web sites say the phone needs to be deodexed before performing this modification. Is my phone already deodexed? Do I need to deodex my Atrix? Is there an auto-deodexer program that will work for this phone? How do I back everything up before deodexing my phone (I use Titanium Backup app)? Any help would be greatly appreciated and sorry for being a Noob! I LOVE this Phone!!!! Might even have to get rid of the ole lady so I can spend more time with my Atrix 4G!!! LOL
Click to expand...
Click to collapse
Thank you for your post. I have read this topic (http://forum.xda-developers.com/show...=how+to+deodex) and because I am such a super noob with Android here is where I get confused:
I am assuming that when I first run xUltimate v2.2 my USB connenction should be set to none????? I do have USB Debugging and Unknown Sources enabled.
1. Unzip xUltimate v2.2, and launch "Main.exe"
2. If everything goes well xUlt should recognize the phone and make a connection. You now should see a list of options.
3. Run option 1. After option 1 is done, run option 2.
4. Now these well take a while. Run option 3.
5. IMPORTANT: After you have run option 3, you MUST navigate to the xUltimate folder and find "origi_frame" folder, and delete "guava.odex". It's a bad file, and interferes with deodexing process.
6. Now run option 4, and wait.
7. Exit xUltimate, and put the phone in USB mass storage.
8. Go back into the xUltimate folder and copy "done_frame", and "done_app", and move them to the root of the sdcard.
How do I access the root of sdcard and have the ability to copy them?
9. Put the phone in PC mode
I have never seen an option for PC Mode in my USB connection. Does this get installed in the previous steps or do I enable this in settings somewhere?
10. Open a command prompt, and do the following:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
Hi.
First, a disclaimer... I will not be responsible for you messing this up and bricking your device. I am only outlining a guide which I figured out and used to get my TP setup the way I wanted. DO NOT come to me for support, as I am not a dev and really have no time to save anyone from their doom...
I used RootExplorer (Paid App -
https://market.android.com/details?...sImNvbS5zcGVlZHNvZnR3YXJlLnJvb3RleHBsb3JlciJd) to do the steps outlined below. You may use any file manager of your choice, granted that it gives you root access with read/write access to /boot folder. Please make sure you backup anything you plan on changing by making copies and moving them to a safe location... Don't way I did not warn you... ^_^
With that said... I hope this helps some one... ^_^
I have just figured this thing out and soon after noticed that there is a thread with a video showing the methods to remove the extra UImage from the moboot boot menu.
The video shown here http://forum.xda-developers.com/showthread.php?t=1511050 is a great way to remove the redundant UImages from the list except I figured out a easier method and also a way to choose the default OS (WebOS or CM or CN) to load when TP boots, which the video does not get into.
Once I updated to the latest CM9 V2, I rebooted and my TP wanted to boot into the Bricked_Kernel which I did not want. I would, in this case as many of you, scroll (within 3 seconds) to the right entry to boot or else, I would be needing to reboot again.
So here is what I did.
Boot into your Rom (CM9 in my case)
Install RootExplorer from the market.
Launch RootExplorer. You will be asked to grant SU. Press Yes.
Navigate into /boot folder.
Click on the Mount R/W. This will change to Mount R/O. Now you have read and write (important) access to the contents of this folder.
Find the entry UImage.Bricked_Kernel (It might be UImage.ClassicNerd or something else).
Long press the UImage you want to delete (or modify).
Delete (rename, if you want to keep it for some reason) the UImage of the old kernel
Click on the Mount R/O to set the folder for read only access before you exit.
Now when you reboot, you will notice that the MoBoot menu is missing the entry for the extra kernel that was there before. The problem now is that the default boot selection has been set to WebOS. This is because the device is looking for the missing default entry in the boot menu. So it's just going to the top of the list. If this is what you want, you can stop here but if this is not the OS you want to load by default, follow the next few steps.
Launch RootExplorer
Navigate into /boot
Click on the Mount R/W to set write access.
Find the entry moboot.default
Long press moboot.default and choose Open in Test Editor.
The entry in this text file will show the OS that MoBoot will choose to load by default. Mine had an entry "Bricked_Kernel"
Delete the entry in this file and retype the OS of your choice. Mine was "CyanogenMod" (without the "").
Exit. You will be told that RootExplorer made a moboot.default.bak was created for safety. If you are using other file explorers you might not get the automatic backup. So please make a back up of this file before you change the entry.
Click Mount R/O to set the permissions to read only before exiting.
Reboot.
Now you will see that the MoBoot has the right OS as the default OS.
For those of you that desire to make the WebOS as the default OS you can type WebOS in the moboot.default. Well, good luck.
PLEASE DO NOT CHANGE FILES IN THE /BOOT IF YOU ARE NOT SURE WHAT YOU ARE DOING!!! Only follow this guide if you are comfortable doing so!!!
Good stuff, man.
The major difference between my tutorial and yours is that Root Explorer is a paid app, whereas my tutorial uses ES File Explorer which is free.
If you have Root Explorer though, this is definitely easier.
Choosing Default OS
Or plug in the device to computer and type:
adb shell [enter]
mount -o remount,rw /boot [enter]
ls | grep uImage [enter]
sample output:
Code:
uImage-2.6.35-palm-tenderloin
uImage.ClockworkMod
uImage.CyanogenMod
uImage.moboot
uImage.webOS
echo "CyanogenMod" > /boot/moboot.default [enter]
exit [enter]
done
nomadman said:
Choosing Default OS
Or plug in the device to computer and type:
adb shell [enter]
mount -o remount,rw /boot [enter]
ls | grep uImage [enter]
sample output:
Code:
uImage-2.6.35-palm-tenderloin
uImage.ClockworkMod
uImage.CyanogenMod
uImage.moboot
uImage.webOS
echo "CyanogenMod" > /boot/moboot.default [enter]
exit [enter]
done
Click to expand...
Click to collapse
The thing is... even though I am not a total noob when it comes to using ADB commands, it's usually not the most convenient to have to deal with connecting TP to a PC, putting it in USB mode, Command Prompt, etc... a lot of steps... What I described can be done within the TP... which was my case...
cvcduty said:
The thing is... even though I am not a total noob when it comes to using ADB commands, it's usually not the most convenient to have to deal with connecting TP to a PC, putting it in USB mode, Command Prompt, etc... a lot of steps... What I described can be done within the TP... which was my case...
Click to expand...
Click to collapse
well there's more than one way to skin a robot. i personally think it's even easier running the commands in android terminal than plugging into a pc.
what if i dont have the moboot default file?
phonetec said:
what if i dont have the moboot default file?
Click to expand...
Click to collapse
Ok... can you describe your situation with bit more detail?
Are you running CM9? Or any other ICS or GB custom rom?
How did you install your android rom?
I am not aware (since I am not a dev and no where near an expert on the matter) a way to install Android other than the CM7 or CM9 method using MoBoot to push the files to TP...
So if you can outline some details of your situation, I hope someone can shed some light for you...
im running cm9 alpha 2, installed using cwm, after using acmeinstall of cm7, it defaults to webOS when i boot up and I hate it
phonetec said:
im running cm9 alpha 2, installed using cwm, after using acmeinstall of cm7, it defaults to webOS when i boot up and I hate it
Click to expand...
Click to collapse
So if you don't have Moboot in your system anymore, I think you can push it to the TP via cminstall and get the OS chooser back.
How do you get into CWM? Do you see any UImage.Clockworkmod, UImage.Cyanogemod, etc? Are you missing moboot.default? I wonder if you can just create the moboot.default file with the CyanogeMod as it's content and see if MoBoot will read the file...
cvcduty said:
So if you don't have Moboot in your system anymore, I think you can push it to the TP via cminstall and get the OS chooser back.
How do you get into CWM? Do you see any UImage.Clockworkmod, UImage.Cyanogemod, etc? Are you missing moboot.default? I wonder if you can just create the moboot.default file with the CyanogeMod as it's content and see if MoBoot will read the file...
Click to expand...
Click to collapse
i still have moboot injstalled, but when I go in /boot I dont have a file called moboot.default
phonetec said:
i still have moboot injstalled, but when I go in /boot I dont have a file called moboot.default
Click to expand...
Click to collapse
I think if moboot is still installed, it's probably looking for the moboot.default file but since in your case, it's missing, it's booting what ever is on the top of the list of the UImages. I think you can simply create a text file and name it moboot.default in the /boot directory. As the content of the text file put CyanogenMod. Change the permissions of this file once it's placed in the /boot directory to rw_r__r__ (same as other files in the folder). Change the folder to R/O and reboot... I think it will work.
Worst case I guess you will have to push moboot via pc again...
Good luck...
yeah...that did not work....oh well, I have to send it to HP for repair anyway so i'm not going to worry too much about it
phonetec said:
yeah...that did not work....oh well, I have to send it to HP for repair anyway so i'm not going to worry too much about it
Click to expand...
Click to collapse
wait... you said you used the cm7 acmeinstaller? You shouldn't be using that if you installed cm9.
Sent from my HP Touchpad with CM9!
itsDefying said:
wait... you said you used the cm7 acmeinstaller? You shouldn't be using that if you installed cm9.
Sent from my HP Touchpad with CM9!
Click to expand...
Click to collapse
Good catch. I missed that one. He should have used the new moboot. If he used CM7 acmeinstaller he probably meant he also used the old moboot also.
Why not just edit the boot via CyBoot? Just about to try it myself.....
http://www.webosnation.com/cyboot
Well, it works after a fashion. Boot into WebOS, open up PreWare, install CyBoot. Launch it, and change the default boot to Android. Reboot, and the correct CyanogenMod entry is selected by default, but it doesn't autoboot - waits for you to hit the home key. Still, better than scrabbling for the volume key and a relatively quick way to (semi) fix the issue if you don't have RootExplorer.
dirtyfrog said:
Why not just edit the boot via CyBoot? Just about to try it myself.....
http://www.webosnation.com/cyboot
Well, it works after a fashion. Boot into WebOS, open up PreWare, install CyBoot. Launch it, and change the default boot to Android. Reboot, and the correct CyanogenMod entry is selected by default, but it doesn't autoboot - waits for you to hit the home key. Still, better than scrabbling for the volume key and a relatively quick way to (semi) fix the issue if you don't have RootExplorer.
Click to expand...
Click to collapse
Very good point. As some one said, there is more then one way to skin a cat.
I found that if you use terminal emulator and entering the following is the easiest way to set the default.
su
cd /boot
mount -o rw,remount /boot
echo CyanogenMod > moboot.default
Follow this entry exactly with the spaces them reboot, it will set your default to CyanogenMod. If you want to use another default just replace CyanogenMod with whatever you are using.
This is fast and easy.
Thank me if this helps.
travisross69 said:
I found that if you use terminal emulator and entering the following is the easiest way to set the default.
su
cd /boot
mount -o rw,remount /boot
echo CyanogenMod > moboot.default
Follow this entry exactly with the spaces them reboot, it will set your default to CyanogenMod. If you want to use another default just replace CyanogenMod with whatever you are using.
This is fast and easy.
Thank me if this helps.
Click to expand...
Click to collapse
That's perfect! The point is for people to able to fix this easily on the fly. So if you don't have access to Rootexplorer, this method can be used to change the default OS the TP would load at reboot. Thanks.
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!