Related
Here's a recompiled version of the Browser that supports auto rotate.
Here's the download location for the Browser.apk:
http://www.koushikdutta.com/2008/12/auto-rotate-for-android-browser.html
Run the following from the command prompt to install the new Browser:
Installation Instructions:
adb remount
adb shell rm /system/app/Browser.odex
adb push Browser.apk /system/app/Browser.apk
Now start up the Browser.
You may not have a Browser.odex depending on your phone model.
The change, as I mentioned before, is really trivial. In the BrowserActivity.onCreate, I did the following:
// the next line is the original code
// setRequestedOrientation(mSettings.getOrientation());
// make it use the sensor for orientation instead.
setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_SENSOR);
To restore the original Browser, flash RC30 again.
Koush, thanks so much! I have been waiting for this!
i can't get it to install and now the browser don't work and i can't install the back up
I'm getting no space available when pushing the browser.apk
JF rc30 v1.2
kron2 said:
i can't get it to install and now the browser don't work and i can't install the back up
Click to expand...
Click to collapse
You can't get it to install? Could you be more specific?
saul972 said:
I'm getting no space available when pushing the browser.apk
JF rc30 v1.2
Click to expand...
Click to collapse
Your /system partition ran out of room. Is there something you can delete from there? I've seen this before as well on some of my company's phones; I usually end up deleting some ringtones or other junk files.
took a couple of tries but installed now...thanks!
fyi i rebooted phone to initially install the new Browser. I first got errors w/o rebooting so that may fix the problem
I had the same problems with the new browser crashing and then being told that the file couldnt be copied due to lack of space,
Easiest fix is to just reinstall rc30 or rc8 and install the patched browser again.
Worked fine after that
Koush said:
Your /system partition ran out of room. Is there something you can delete from there? I've seen this before as well on some of my company's phones; I usually end up deleting some ringtones or other junk files.
Click to expand...
Click to collapse
Not sure.
Here's the message
failed to copy 'Browser.apk' to 'system/app/Browser.apk' : no space left on device
SGTDavePwnage said:
I had the same problems with the new browser crashing and then being told that the file couldnt be copied due to lack of space,
Easiest fix is to just reinstall rc30 or rc8 and install the patched browser again.
Worked fine after that
Click to expand...
Click to collapse
Will I need to start the process again?
saul972 said:
Will I need to start the process again?
Click to expand...
Click to collapse
Its basically telling you that it cant copy the file because of lack of space withing the system partition.
As koush advises, if you know how to clear space that will fix the problem.
If you dont know how to remove things and are a bit unsure of what to do, reinstalling the modified rc30 / rc8 will reset the system partition back to its defaults.
Once your back and set to default you can try to install again if you want
I'm assuming this is for those who have root access only?
If so, it would be nice to state that when posting these mods.
Henchman said:
I'm assuming this is for those who have root access only?
If so, it would be nice to state that when posting these mods.
Click to expand...
Click to collapse
Yes this requires root access,
I can see what you are saying about perhaps specifying in the post when something requires root access, but when you look at the instructions in this case its quite obvious that this one does require root.
PS.... Cheers for the upload Koush
SGTDavePwnage said:
Yes this requires root access,
I can see what you are saying about perhaps specifying in the post when something requires root access, but when you look at the instructions in this case its quite obvious that this one does require root.
PS.... Cheers for the upload Koush
Click to expand...
Click to collapse
Obviouse to em...
But probably not to everyone.
And you know the old saying. When you Assume...
where do i put Browser.apk to install it on the sd card and if so how do i use adb to see it or do i push it from like c:\browser.apk \system\app\browser.apk
SGTDavePwnage said:
Its basically telling you that it cant copy the file because of lack of space withing the system partition.
As koush advises, if you know how to clear space that will fix the problem.
If you dont know how to remove things and are a bit unsure of what to do, reinstalling the modified rc30 / rc8 will reset the system partition back to its defaults.
Once your back and set to default you can try to install again if you want
Click to expand...
Click to collapse
Finally got it!!! Thanks for your help
kron2 said:
where do i put Browser.apk to install it on the sd card and if so how do i use adb to see it or do i push it from like c:\browser.apk \system\app\browser.apk
Click to expand...
Click to collapse
Place it in the tools folder of the SDK folder on your PC
thx joshoowa i installed it finally i did have it in the tool folder but would not install but after several tries it did i was starting to think i was installing it wrong
I've deleted most of my .ogg audio related tones in the /media/audio folder but i still get no space left. what else can i delete?
btw i'm using adb shell rm /xxx/xxx/xxx/xx.ogg to delete. is that right?
Hey Hey!!!...
Had to free up some room, but it works great..
Thanks..
I've been using Haykuro's G build because H has never worked for me. But now with the market problem I'm needing to switch to H because there are a lot of apps I want to download.
When I flash over to the H build and try to setup apps to sd, I always get stuck in a boot loop and I can't seem to figure out why that is. I thought maybe it was an app I had on my sdcard so I formatted both partitions and it still doesn't work.
If anyone can help it'd be greatly appreciated. =)
1st: you are trying the apps to sd H build right(not just the normal H version)?
2nd: what steps are you doing to try apps to sd and are any reporting errors?
3rd: are you trying to move the app cache also(/data/data)? If so that might be your problem.
It's the apps to sd version and I was just following the steps on the wiki pg.
http://android-dls.com/wiki/index.php?title=Haykuro_Apps_to_SD
And no I wasn't trying to move cache.
Hmm try going into the recovery terminal and do the following:
Code:
mount data
cd data
ls -l
look for the app directory listing and tell me what it says on that line(it'll probably carry over to the next line as well)
If the app directory doesn't exist well... then there's your problem.
app -> /system/sd/app
is that what you needed?
xocassidychick15ox said:
app -> /system/sd/app
is that what you needed?
Click to expand...
Click to collapse
Hmm ya, that looks correct. Was there anything else with that "->" next to it? If not, something is wrong with the sd card setup. Either /system/sd/app doesn't exist or the partitions aren't set up correctly. As a temporary fix(if there's nothing else with a '->') you can do this:
Code:
rm /data/app
mkdir/data/app
The only thing else that has '->' is:
app-private-> /system/sd/app-private
Hmm not looking good... try the code segment I put before, it should at least let you get into your phone. From there you can look into the /system/sd directory and make sure everything is correct.
EDIT: by not looking good I meant all that is correct which means it's something that'll be harder to fix.
When I try to enter the code it says:
rm /data/app
rm: cannot remove '/data/app' : No such file or directory
mkdir/data/app
sh: mkdir/data/app: not found
And when I look in /system/sd all it shows is lost+found
When I tried the code in ADB the first part went through but it still said
mkdir/data/app: not found
wfirst: there's a space between mkdir and /data/app.
also: you didn't restart the phone or anything since typing in the "mount data" bit have you? If so you need to type that again before doing that code segment.
EDIT: PM me your answers, I'll try to solve this through pm.
This has been solved. Reflashing the ROM fixed it.
The same thing happened to me. Went from 5.01G apps to SD, to 5.01Hr3 apps to SD. After setting up and changing the references to have apps point to the SD card (note that I already had apps on the SD card), all my apps appeared after rebooting. When I tried to reboot again, that's when I saw the endless HTC logo loop.
I reflashed the phone and it seemed to fix it. However, the phone later locked on me and I had to reboot by removing the battery. When the phone started again, I got the HTC logo loop.
I ended up going to Dude's G release instead. Hope someone figures this out.
As promised..
You need to obtain the new SPL and Radio first PRIOR to installing this ROM. Follow this post.
Installation:
1. Download http://www.droiddeveloper.com/hrbuilds/app_s.zip
2. extract "app_s" into your sdcard's ext2 partition.
3. Download http://www.droiddeveloper.com/hrbuilds/hero-signed.zip
4. Place on regular sd card.
5. Reboot into recovery, wipe and flash.
6. Enjoy.
Only thing that shouldn't work at the moment is bluetooth and some minor features.. besides that you have a fully functional hero rom.
enjoy guys..
Phuck the leakers, and there supporters.
EDIT: as far as the bluetooth problem goes, i haven't played with a fix just yet.. i've spent this free time since i've quit to catch up on homework guys.
this is not me coming back.... this is just to clear my conscience, and a big "Phuck YOU" to the leakers
EDIT2: it's using ext2 instead of ext3 because, again, i haven't worked on the rom since i've quit..
for those of you that don't know how to place app_s into sd card do this:
Code:
adb push app_s /system/sd/app_s
enjoy.
EDIT3: /system/app wouldn't fit.. and if i did /data/app_s like before, it wouldn't give you any space in /data this is why i did it this way.
and yes.. this has Rosie.
Enable Superuser.apk & Enhance ROSIE UI FOR HERO ROM
Bluetooth debuging on Hero
Clean up rosie!!
HTC Hero Speedup v2.0
HTC Hero Rosie UI toggle
How you put App_s into the ext2 partition
THE HERO HAS RISSEN! But really,thanks.
EDIT:how do I put the app_s onto a ext2 partion via windows? I lost my linux live cd.
wich one do we download 1 or 3 ?
and thanks alot haykuro much love dawg thanks again
I dont use Apps2SD so can i just add the app_s back to the data folder and resign?
F!! Why does it have to be on an ext2? I cant get the permissions yo ork on my sdcard! Is there a way to avoid this?
And ps. Good god thank you!
If you dont, then wait for someone else to say how. This isn't a tech. It's apps2sd method or none right now.
@justanothercrowd no, this requires apps2sd because its so large.
@ynghova187 and dutman yes
So how would I go about on doing step 3? Srry I just unrooted my phone because it was randomly shutting off, and now I see this, and I want to root. lol.
Darkrift said:
@justanothercrowd no, this requires apps2sd because its so large.
@ynghova187 and dutman yes
Click to expand...
Click to collapse
For someone whos never used apps2sd, is there a quick tutorial for this?
I've searched, but theres nothing that i found about putting a "app_s" folder onto the partition...
Sorry for the n00b question, im usually pretty good with this type of stuff, but i'm at a loss
Darkrift said:
@justanothercrowd no, this requires apps2sd because its so large.
Click to expand...
Click to collapse
Which method(s) should work? I've seen at least 5 so far, including an application or two.
will my apps2sd application automatically move this apps folder to partion2?
dutman said:
So how would I go about on doing step 3? Srry I just unrooted my phone because it was randomly shutting off, and now I see this, and I want to root. lol.
Click to expand...
Click to collapse
Step 3 is simply downloading a file. Is that really what you need help with?
if i dont have apps to sd what links can i download any help i never used apps to sd
This would be the perfect time for the few of us that still haven't been using apps2sd
nice that this has rosie.
Which tut would is the most widely used and most compatible method
startekee said:
How you put App_s into the ext2 partition
Click to expand...
Click to collapse
same question i am using windows... and i used paragon to partition my card before... but windows does not show ext2... is there a way around this??
ext2...
adb push app_s /system/sd
?
where do i put that into, im sorta new to this and i have the ion rom right now.. also do we need the special spl?
No, I need help with Step 2. Sorry that was a typo. And do you have an answer for me Mr. mikedmeyer?
281 said:
adb push app_s /system/sd
?
where do i put that into, im sorta new to this and i have the ion rom right now.. also do we need the special spl?
Click to expand...
Click to collapse
I can't help you with ADB, but if you are running a linux distribution, load GPartEd and you can format your card (if you havent already) and place it on the ext2 partition.
Introduction
If you are rooted and running a Hard SPL or a Stock SPL and really want to flash a ROM that claims to require Danger/Haykuro SPL, but you do not want to upgrade your SPL there are alternative ways to make these ROMs work on your phone without upgrading your SPL.
This is a very easy process, Ive done it with a few ROMs with no problems:
First off, keep in mind that on a Stock SPL
/system = about 67MB
Any ROM that has a system partition 67MB or Greater will require Danger/Haykuro SPL, UNLESS you can shrink that ROM's /system down below 67MB.
How do you do this, you ask?
------------------------------------------------------------------------------------------------------------------------------------------------------
Method #1 (Easy) -Move/Delete unneeded Apps, Sounds, Files
------------------------------------------------------------------------------------------------------------------------------------------------------
NOTE: This Method does NOT apply to HERO/SENSE ROMs, they are way too big! Check Method 2 if you want to fit ANY ROM on any SPL (Advanced)
Make sure you have 7-Zip! Dont have it? Google is your friend!
1) Read the first post and changelog of the ROM you wish to install on your phone. After youve made yourself familiar with what needs to be Wiped (ie: dalvik cache, ext, data) the Partition Layout the developer suggests (ie: FAT32/Ext3/Swap), then go ahead and download the ROM. Unzip it to a folder, name it something short. for example: C:\1\rom
now click on the system folder, scroll down and click on the media folder, and delete the audio folder. This will erase every sound effect and ringtone on your phone and usually will free up about 2MB in system.
To get your ringtones and sounds back download this (thanks Robot Teapot!) and unzip the folder to the root of your sdcard. (note: your ringtones might not show up the first time you boot the rom, in this case, reboot and theyll all be right there)
If removing your ringtones isnt enough to keep /system under 67MB then move on to step 2), if youre already below 67MB skip to step 3)
2) Return to the first post and changelog of the ROM you are trying to install. Look for apps the dev has added to the ROM that dont seem necessary for the ROM to function such as Twidroid.apk, Facebook.apk, NeroMedia.apk, WirelessTether.apk, WiredTether.apk, Maps.apk(takes up a lot of room, and sometimes outdated...just delete it and install the latest from the market!)etc.
You can use Android Barebones/Necessary Apps - CyanogenMod Wiki as a general guideline to determine which apps are essential to Android running properly and the functions of many system apps.
Delete those unnecessary apps or move them to your sdcard, and use ASTRO File Manager or a similar app to install them after you flash the ROM.
3) Okay, assume youve trimmed /system down below 67MB, good job! now you need to get those folders you extracted and the boot.img zipped up and signed. select the folders from the ROM you extracted and modified, the boot.img, right click, and select 7-Zip < Add to .zip
4) Download Stericson's Autosign place it in any directory and follow the instructions in the thread to sign your zip file.
5) Move the signed zip to your SD Card, making sure you have the proper partitions, wipe the necessary things, then flash your zip file and cross your fingers!
------------------------------------------------------------------------------------------------------------------------------------------------------
Method #2 (Advanced) -"Cache Hack"
------------------------------------------------------------------------------------------------------------------------------------------------------
NOTE: This Method will fit any ROM on any SPL but is more advanced than Method 1
lbcoder introduced the concept of moving files to the /cache partition of the phone and linking them back to /system or /data.
Firerat has come up with a way to make this concept work and explains the whole process in his thread and shows some examples of his method by providing some ports:
[HACK][ROM][BOOT.IMG][CACHE]-Stk SPL ROMs with Danger SPL size & extra 30mb! any SPL!
------------------------------------------------------------------------------------------------------------------------------------------------------
There you have it folks! Congrats if youve bypassed the Danger SPL requirements! Be sure to always keep a Nandroid/BART backup!!!!
Disclaimer: Not saying these methods will brick or damage your phone, but in the rare event this occurs I am NOT responsible for bricks or or any damages to your phone!
Autosign doesnt need to be in the SDK place, I had it in my music folder and it worked fine.I accidentally formatted my PC last night and dont have the SDK installed but autosign works for me so im happy.
Note to OP-You cant brick from flashing any 32B rom, you would only get a blank screen that stays..which some seem to call soft-brick, i call it nonsense though.
Thanks for this excellent tutorial
Ace42 said:
Autosign doesnt need to be in the SDK place, I had it in my music folder and it worked fine.I accidentally formatted my PC last night and dont have the SDK installed but autosign works for me so im happy.
Note to OP-You cant brick from flashing any 32B rom, you would only get a blank screen that stays..which some seem to call soft-brick, i call it nonsense though.
Click to expand...
Click to collapse
Really? I had no idea that the SDK wasnt required, ill remove that.
and yeah i know its usually a soft brick, if anything, and youre right its nonsense, and can be solved using a nandroid backup and wiping the proper things, but im playing it safe with that disclaimer just like the rom devs do lol
migalito said:
Thanks for this excellent tutorial
Click to expand...
Click to collapse
.
Youre welcome! I hope it works out for you!
Will this work with the Super D rom?
cg87 said:
Will this work with the Super D rom?
Click to expand...
Click to collapse
yes! I tried it on Super D!
speedysilwady said:
yes! I tried it on Super D!
Click to expand...
Click to collapse
Then I'm so confused. If it's possible, why does the rom still require the Danger SPL? Why didn't bbuchacher make it so it doesn't require the Danger SPL? Doesn't make any sense to me. Can someone please enlighten me?
cg87 said:
Then I'm so confused. If it's possible, why does the rom still require the Danger SPL? Why didn't bbuchacher make it so it doesn't require the Danger SPL? Doesn't make any sense to me. Can someone please enlighten me?
Click to expand...
Click to collapse
Well, to be honest, im not sure why, but im assuming some developers like to include features and apps that arent necessarily required for the rom to run properly but to make their rom more appealing to users, than other roms. keeping those apps in system prevents those apps from disappearing after you wipe your phone/ext. Plus devs always keep ringtones and sounds included in their roms for completeness's sake.
Now a Hero ROM on the other hand is loaded with system apps that cant be deleted and i dont think theyll ever fit on a Stock SPL, except maybe MicroHero, but im not sure.
But for whatever reason, a lot of regular ROMs are fat and bloated with apps and extras that dont necessarily have to be saved on the system partition,so the best thing to do is shrink those roms down till they fit, if you can't or dont want to upgrade your SPL.
How to make it work *WITHOUT TRIMMING*
Take a look at your update.zip archive.
Probably has 4 things in the root:
boot.img
system
META-INF
data
If system is greater than about 67MB (or lets say 60 just to be real safe...), then create ANOTHER directory and call it "cache".
Now MOVE /system/app into /cache/
You now have the space cleared up, but it still won't work.
So go into META-INF/com/google/android and edit the script "update-script".
just below the line where it says "format CACHE:", add these lines:
copy_dir PACKAGE:cache CACHE:
set_perm_recursive 0 0 0755 0644 CACHE:
symlink /cache/app SYSTEM:app
Wow, did we just move the extra crap into cache? Yep.
May require slight modification. Use your head.
Seems someone else is in the same boat as I am.
Can't update my radio, looks like some kind of hardware problem almost. Tried everything in any possible way.
So it looks like we're stuck with the standard or engineering SPL, which is fine but means there are some restrictions.
I'll try some of the tips you gave and flash something besides Cyanogenmod tonight.
lbcoder said:
Take a look at your update.zip archive.
Probably has 4 things in the root:
boot.img
system
META-INF
data
If system is greater than about 67MB (or lets say 60 just to be real safe...), then create ANOTHER directory and call it "cache".
Now MOVE /system/app into /cache/
You now have the space cleared up, but it still won't work.
So go into META-INF/com/google/android and edit the script "update-script".
just below the line where it says "format CACHE:", add these lines:
copy_dir PACKAGE:cache CACHE:
set_perm_recursive 0 0 0755 0644 CACHE:
symlink /cache/app SYSTEM:app
Wow, did we just move the extra crap into cache? Yep.
May require slight modification. Use your head.
Click to expand...
Click to collapse
I thought about that but I'm not 2 good @ programing unless its cars/video console. But doesn't the cache get used for something after the rom is up and running? Or is it only for ota updates?
If only for ota updates how come the danger spl doesn't give you 120mb or so since cache and system are 67mb each
That's a very good question. Just tried it and it seems to work, though. It's booting as we speak. All system/app files in the cache directory.
EDIT: Actually, all apps seem to force close on boot. So I'll just try it the regular way I guess.
try the Fix apk uid mismatches maybe idk ill try it in a lil bit
*update*
Got a boot loop on openeclair1.0.1 not sure why but dont got the time to fig. it out right now.
also why does a boot loop drain the crap out of your battery?
lbcoder said:
Take a look at your update.zip archive.
Probably has 4 things in the root:
boot.img
system
META-INF
data
If system is greater than about 67MB (or lets say 60 just to be real safe...), then create ANOTHER directory and call it "cache".
Now MOVE /system/app into /cache/
You now have the space cleared up, but it still won't work.
So go into META-INF/com/google/android and edit the script "update-script".
just below the line where it says "format CACHE:", add these lines:
copy_dir PACKAGE:cache CACHE:
set_perm_recursive 0 0 0755 0644 CACHE:
symlink /cache/app SYSTEM:app
Wow, did we just move the extra crap into cache? Yep.
May require slight modification. Use your head.
Click to expand...
Click to collapse
I remember you suggested this a while back when I asked about eclair roms on stock spl, I'm guessing if you use this method and wipe, you'll have to reflash the rom because those system apps are gone, correct?
yea anytime you wipe you would have to reflash the rom because a wipe deletes. data and cache folder
Dr-b said:
That's a very good question. Just tried it and it seems to work, though. It's booting as we speak. All system/app files in the cache directory.
EDIT: Actually, all apps seem to force close on boot. So I'll just try it the regular way I guess.
Click to expand...
Click to collapse
Might be a minor goofup on the permissions. Just verify the permissions and it will be fine.
What programming?
There is no programming involved in this.
Mainly cache is for OTA, but also some other crap related to the download manager.
As for the deathspl allocation, it puts *some* of the /cache into /system, *some* of the /cache into /data, and the balance of /cache remains in /cache.
xile6 said:
I thought about that but I'm not 2 good @ programing unless its cars/video console. But doesn't the cache get used for something after the rom is up and running? Or is it only for ota updates?
If only for ota updates how come the danger spl doesn't give you 120mb or so since cache and system are 67mb each
Click to expand...
Click to collapse
speedysilwady said:
I remember you suggested this a while back when I asked about eclair roms on stock spl, I'm guessing if you use this method and wipe, you'll have to reflash the rom because those system apps are gone, correct?
Click to expand...
Click to collapse
Why would you want to wipe it?
Note: you could just create an update.zip with an update-script that says ONLY "format DATA:" That would wipe the data withOUT wiping the /cache. Maybe name it "betterwipe.zip" and put it on your sdcard. Boot into recovery and apply "betterwipe.zip".
lbcoder said:
Why would you want to wipe it?
Note: you could just create an update.zip with an update-script that says ONLY "format DATA:" That would wipe the data withOUT wiping the /cache. Maybe name it "betterwipe.zip" and put it on your sdcard. Boot into recovery and apply "betterwipe.zip".
Click to expand...
Click to collapse
true, with fix permissions, and wipe dalvik, there really isnt much use in wiping data anymore, but would fix permissions still work if the apps are in cache? i know theyre syslinked, but im not sure how that works with the fix_permissions script. sorry if im asking dumb questions, im still learning.
Ill try your idea a really big rom and see if it works.
just wanted to confirm that all Hero ROMs seem to require Danger SPL, I see no way of shrinking system anywhere close to 67 or less.
But my method should still work on any eclair or donut rom. I still havent had a chance to try lbcoder's method though it should work. if people can get lbcoders method to work ill add it to the first post!
Tired of having to redownload and reinstall all of your apps when you reflash your phone? SaveMyApp can help.
This script will setup your phone so that after your flash to your favorite rom, all* of your apps will be install on the first boot. These apps will show up in the market too!
Also, the script will allow you to backup your /data/data folder to your sdcard and then restore it after your reflash. The /data/data is where Most of your user data is stored. This is not guaranteed to fully restore everything. This also does not backup your Google, Android, or Motorola settings; this is to improve compatibility with roms.
*The /preinstall folder is limited to 120MB, so if you have more then of apps this script will not fully work.
This should work with all phones, however it has only been tested on the Droid 2/X.
If you want to test this script on a different phone, let me know the /preinstall size and if it worked or not.
v0.1.4.2 - 11/17/2010
-Improved backup and restore of data
-Improved script usability
v0.1.4.1 - 11/17/2010
-Improve safety of removing /preinstall/app
v0.1.4 - 11/16/2010
-Added option to clear the /preinstall/app folder
-Added messages to support clear /preinstall/app
v0.1.3 - 11/12/2010
-Added backup of /data/data
-Added messages to support Data Backup
v0.1.2 - 11/11/2010
-Added Backup /data/app-private
-Show /data/app size, prompt user for continue
-Additional messages added to improve user experience
v0.1.1 - 11/10/2010
-First Release
-Backup and Restore /data/app
Installation:
WARNING: This steps must be completed as listed, failure to do so may result in unexpected errors which I am not responsible for.
1. Enable USB debugging and make sure Sdcard is mounted on phone
1. adb push apps.sh /data
2. adb shell
3. cd /data
4. chmod 775 apps.sh
5. ./apps.sh
a. Follow the onscreen directions
6. Reboot and proceed to wipe and reflash
7. On boot, wait between 5 and 10 minutes depending on how many apps you have before logging into your account. (30 apps takes about 4-5 minutes)
8. Login to your account
9. Droid 2/X Bootstrapper -> Bootstrap Recovery
10. Enable USB debugging and make sure Sdcard is mounted on phone
11. adb shell
12. tar -xzpf /sdcard/savemyapp/backup.tgz
FAQS:
Market isn't showing apps!
settings->applications->Manage Applications->All->Market->Force Stop, Clear data
Why is there a MACOSX file when I extract the archive?
Because I am lazy and I zipped it using Mac's built in archiver.
The script isn't working right away!
Redownload the newest script, just to make sure
Disclaimer:
You may repost this, but you must quote it as is.
I will only be responding to the threads I started on the Xda-Developers forums.
First!
I'm just holding a parking spot for this post!
What a great idea...thank you for developing this, im so tired of re downloading my apps back and setting everything up...done it about 10 times in the past month between sbfing and updating the fission rom several updates in a row so thank you...will most definitely be using this when I flash roms in the future. Thanks again
Sent from my DROID2 using XDA App
Excellent program! I'm having trouble getting it to work unfortunately. When apps.sh begins to copy files from /data/apps, I get errors saying "No space left on device" after every single file it tries to copy. This is of course not true since this D2 has over 6 gigs free on the system storage.
I am running this through the window's command prompt, but I don't see much in the code that won't run on windows aside from "du" which isn't even relevant unless my app + app-private folders combined size is over 120 MB (it's not).
I'm also running Epic 2.5 if that has anything to with this.
Any ideas? Am I just doing this terribly wrong?
Thanks!
tildaSparky said:
Excellent program! I'm having trouble getting it to work unfortunately. When apps.sh begins to copy files from /data/apps, I get an error saying "No space left on device." This is of course not true since this D2 has over 6 gigs free on the system storage.
I am running this through the window's command prompt, but I don't see much in the code aside from "du" which can't run with windows.
Any ideas? Am I just doing this terribly wrong?
Thanks!
Click to expand...
Click to collapse
If you read the first post it states the /preinstall folder can only hold only 120mb so it you have more than that to backup it won't fully work..I'm guessing that's were the apps are being saved...
Sent from my DROID2 using XDA App
turkeybuzzard said:
If you read the first post it states the /preinstall folder can only hold only 120mb so it you have more than that to backup it won't fully work..I'm guessing that's were the apps are being saved...
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Apps are normally saved in /data/app this script copies those apks to /preinstall so that after a wipe they will automatically be installed on the first boot. Yes /preinstall is limited to about 120MB.
tildaSparky said:
Excellent program! I'm having trouble getting it to work unfortunately. When apps.sh begins to copy files from /data/apps, I get an error saying "No space left on device." This is of course not true since this D2 has over 6 gigs free on the system storage.
I am running this through the window's command prompt, but I don't see much in the code aside from "du" which can't run with windows.
Any ideas? Am I just doing this terribly wrong?
Thanks!
Click to expand...
Click to collapse
Do you get the "No space left on device" message instantly or after some apks were copied to the /preinstall folder?
Here's what I get
Working…
cp: /preinstall/app/com.google.android.apps.maps-1.apk: No space left on device
cp: /preinstall/app/com.google.android.apps.translate-2.apk: No space left on device
cp: /preinstall/app/com.google.android.gm-1.apk: No space left on device
cp: /preinstall/app/com.google.zxing.client.android-2.apk: No space left on device
etc.
=(
tildaSparky said:
Here's what I get
Working…
cp: /preinstall/app/com.google.android.apps.maps-1.apk: No space left on device
cp: /preinstall/app/com.google.android.apps.translate-2.apk: No space left on device
cp: /preinstall/app/com.google.android.gm-1.apk: No space left on device
cp: /preinstall/app/com.google.zxing.client.android-2.apk: No space left on device
etc.
=(
Click to expand...
Click to collapse
How big is your /data/app folder?
OK! I sort of have it fixed. In that I'm not getting my original error.
What I did (which in retrospect was not such a hot idea) was delete the /preinstall/ folder and then created a new one with the subfolders /app/ and /md5/. The logic behind was that I saw the script had nothing in it to clean out the original preinstall folder, and I noticed that it had silly things like NFS in it. As I said, in retrospect I should have just deleted specific items from the folder, but that's what I get for acting without thinking too much.
How bad do you think it is that I remade the preinstall folder from scratch?
Now my preinstall folder is properly populated (I think). But the data won't back up for some reason. I think it might have something to do with the if statements being broken. I'm gonna go ahead and modify your script to bypass the if/else statements and see what happens.
SaveMyApp v0.1.2
By csscmaster3
Your app folder takes up
du: not found
If your app folder is more then 114MB I don't recommend continuing
do you want you to continue? (y/n)y
y
[[: not found
Working…
ignore No such file or directory error if you get it
tee: not found
SaveMyApp has completed your apps
Do you want to backup your data? (y/n)y
y
[[: not found
SaveMyApp has completed.
As an aside my app folder is 28 MB and my app-private folder has only the apkinstaller.
tildaSparky said:
OK! I sort of have it fixed. In that I'm not getting my original error.
What I did (which in retrospect was not such a hot idea) was delete the /preinstall/ folder and then created a new one with the subfolders /app/ and /md5/. The logic behind was that I saw the script had nothing in it to clean out the original preinstall folder, and I noticed that it had silly things like NFS in it. As I said, in retrospect I should have just deleted specific items from the folder, but that's what I get for acting without thinking too much.
How bad do you think it is that I remade the preinstall folder from scratch?
Now my preinstall folder is properly populated (I think). But the data won't back up for some reason. I think it might have something to do with the if statements being broken. I'm gonna go ahead and modify your script to bypass the if/else statements and see what happens.
SaveMyApp v0.1.2
By csscmaster3
Your app folder takes up
du: not found
If your app folder is more then 114MB I don't recommend continuing
do you want you to continue? (y/n)y
y
[[: not found
Working…
ignore No such file or directory error if you get it
tee: not found
SaveMyApp has completed your apps
Do you want to backup your data? (y/n)y
y
[[: not found
SaveMyApp has completed.
As an aside my app folder is 28 MB and my app-private folder has only the apkinstaller.
Click to expand...
Click to collapse
The NFS removal is a good call, I will append the script to check the /preinstall folder and prompt to remove the files there
The reason you are having trouble with this script looks it be like because you are not running it on the phone itself...meaning to say you are not running it via a terminal emulator on the phone nor are you running it via adb shell. The backup uses tar, which isn't on windows by default.
Actually I'm running everything through the adb shell. It's puzzling to me too. My terminal emulator for some reason doesn't have root access. At this point I think I'm just going to SBF anyway.
At any rate, I just decided to pull /data/data/ from my phone onto my HD and I will replace it after I reflash and install my programs, but before I log into my google account. Do you see any reason for this not to work?
tildaSparky said:
Actually I'm running everything through the adb shell. It's puzzling to me too. My terminal emulator for some reason doesn't have root access. At this point I think I'm just going to SBF anyway.
At any rate, I just decided to pull /data/data/ from my phone onto my HD and I will replace it after I reflash and install my programs, but before I log into my google account. Do you see any reason for this not to work?
Click to expand...
Click to collapse
Hmmm, you might have to check your superuser app to see if you accidently are denying su access. In adb shell do you have a $ or a #?
Backing up the /data/data folder to your HD then restoring might not work because I am not sure if it will retain the owner, permissions, etc.
I had a # in my shell. There was something slightly wonky about my root I think. At any rate my backup method didn't work so well (as you predicted) - it caused timeriffic to force close when I tried to load in my old settings via /data/data/.
I will try using this again once I've got my shiny new Fission 2.1 set up as I want.
Thanks for your attentiveness!
I'm guessing this script should be run AFTER all of the applications have been installed. Is this correct?
wsfanatic said:
I'm guessing this script should be run AFTER all of the applications have been installed. Is this correct?
Click to expand...
Click to collapse
That is correct
Sent from my DROID2 using XDA App
Ooooo this is getting popularrrr
Is this D2 specific, or would it work on any phone?
theimpaler747 said:
Is this D2 specific, or would it work on any phone?
Click to expand...
Click to collapse
It works with the D2 and should work with the DX, anything else is use at your own risk, if it does work let me know though
csscmaster3 said:
It works with the D2 and should work with the DX, anything else is use at your own risk, if it does work let me know though
Click to expand...
Click to collapse
Might risk it and try it on my hero Regardless, nice work
theimpaler747 said:
Might risk it and try it on my hero Regardless, nice work
Click to expand...
Click to collapse
The only problem I could forsee would be the /preinstall folder being different or something, if you do end up trying the script could you let me know the size of the /preinstall folder?