yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] overground:
Well that's nifty. So basically, I

bart.sh -n -s LittleDumfuqBeta1

, and then later add an EXT to it by

bart.sh -e -s LittleDumfuqBeta1

and the nandroid will be fine. Nice. As far as all my delete option requests....you say it's not possible??? Not the words I wanted to hear from my future kid's namesake!:( It was just an idea to clear some space for those who may need it.

Example: You are storing a complete backup, and whoops...out of space. You have one or two old backups which you want to keep the nandroid, however the EXT is stale, and will never be used again. Then you could just

bart.sh -e -d OldLittleDumfuq

to make some room?? Now I think a restore of "OldLittleDumfuq" will then fail without the -n switch, but then again, if you only stored using -n now, a restore will fail without the switch. Am I making any sense?

As far as my other idea of deleting certain .img's from a nandroid, that's just another one of my stupid ideas. Unnecessary and probably dangerous. Sorry. :eek:
[G1 Android Development] dumfuq:
Well that part is trivial and can be easily added. As long as you are deleting entire ext partititon or entire nandroid partition. As to deleting parts of the nandroid: it is be possible, the script would just have delete the relative line in the md5 file corresponding to the image being deleted so there isn't a mismatch error on restore. Deleting specific parts of the ext partition is also possible but more of a pain since everything is stored in one archive. Pretty much the archive would have to be opened, edited, and resaved.
[G1 Android Development] dumfuq:
Well, so much for not adding anymore features.

Just posted a new version which allows the user to delete nandroid backup or ext-backup separately. Also added more output for verbose mode.

examples:

delete just the ext-backup of myrom

sh /system/sd/bart.sh -e -d myrom

delete just the nandroid backup of myrom

sh /system/sd/bart.sh -n -d myrom
[G1 Android Development] dumfuq:
non-interactive mode

Since it seems like a lot of people are using this on magics as well, I added a non-interactive mode. If given the '--noninteractive' flag, it will automatically name the rom 'defaultrom' and not prompt for any verification before storing/restoring/deleting. You can still name the rom if you want (and have a keyboard) but it is no longer necessary.

to store complete backup named 'defaultrom' with no user input

sh /system/sd/bart.sh --noninteractive -s

to restore complete backup named 'defaultrom' with no user input

sh /system/sd/bart.sh --noninteractive -r

to delete 'defaultrom' with no user input

sh /system/sd/bart.sh --noninteractive -d

**************************************************

note that '--noninteractive' should be the FIRST argument

**************************************************

all other flags still apply so...

to restore 'myrom' with no input prompts

sh /system/sd/bart.sh --noninteractive -r myrom

I realize this does you no good right now because currently it is only in Amon_Ra's recovery via adb but at least now it is possible to add it to an actual recovery menu.
[G1 Android Development] overground:
You rock!! I guess I'm done *****ing about features. :D I'm trying to get a grasp on the noninteractive thing. Really doesn't make a difference to me, as I have a G1. Someone really needs to implement BART with it's options into a menu driven recovery for Magic and lazy Dream users alike. I feel a little saddened by this closure, but really happy about the powerful tool devsk initiated and dumfuq carried much further than what was required. End result: perfection delivered. Thanks to both!
[G1 Android Development] psjames:
shift: can't shift that many

I have been trying sh /system/sd/bart.sh -s and I get the following message:

shift: can't shift that many

I am running this from adb shell
[G1 Android Development] overground:
It has to be run in recovery.

1. Place bart.sh in /system/sd

2. adb shell chmod 755 /system/sd/bart.sh <may not be necessary, but won't hurt>

3. adb shell reboot recovery

4. adb shell

5. mount /system/sd

6. sh /system/sd/bart.sh -s <romname>
[G1 Android Development] dumfuq:
per request:

here is an option to backup/restore app_s, dalvik-cache and nandroid only

backup:

sh /system/sd/bart.sh -a -s romname

restore (deletes only app_s & dalvik-cache before extracting tar file):

sh /system/sd/bart.sh -a -r romname
[G1 Android Development] schtuka:
I have attempted to use this promising yet unachievable program. I have installed and backed up ROM/ext3 in full as instructed, but I can't perform restore. I see bart folder created with back up. I changed upgraded adk to 1.5 and still same story. By searching this thread I understand that I can wipe my ext4 and the script is not getting affected. Every time I flash new ROM the bart.sh is missing from system/sd. Obviously I am doing something wrong, but I can't find a solution. In recovery I get a message that "cannot open the bart.sh file" Any suggestions?
[G1 Android Development] dumfuq:
First off make sure you mounteds system/sd

2nd, if you wiped your ext then the script is no longer there, put it back.

But if your using amon ra's recovery, you can skip both of these and just leave off the sh and path from the invocation

bart -r

Because it is included in ra's recovery there is no need to mount or explicitly declare path.
[G1 Android Development] dumfuq:
Double post
[G1 Android Development] schtuka:
Thanks man for replay. I have been reading both bart and switchrom threads seems like for few days straight. I thought that script changes after back up procedure is done and you can't just put it back after flashing another ROM. I've kept one in sd card just in case. I will try it tomorrow.
[G1 Android Development] overground:
Can I get an explanation and usage example for this cutting edge option, please? Do I need quotes?

such as:

sh /system/sd/bart.sh "Double post" -d -u -m -f -u -q knockeduphooker9.1.1Full10-26-09

Is this right?
[G1 Android Development] dumfuq:
That is correct. Or you cold use the escape sequence instead of quotes.

sh /system/sd/bart.sh Double\ post -d -u -m -f -u -q knockeduphooker9.1.1Full10-26-09
[G1 Android Development] overground:
You never cease to amaze me with you superior knowledge and intellect, El Guapo. Going to try this now, but I have to first enable Madafatch on the Foursquare Mode in biatchloader in order to compile my kernel sanders. Thanks!! Yeah, really...that's about it. :p

EDIT:Yep...it's in my sig. BWAHAHAHAHAHAHAHA!!!
[G1 Android Development] schtuka:
Yes!

It fi8nally worked, bart -r that is. The sh /system/sd/bart.sh -r didn't work at all. I knew I wasn't total idiot.

Thanks Dumfaq. Much obliged.
[G1 Android Development] Joe333x:
I just want to thank devsk and dumfuq, i used this today to go from aosp to cyan and then back again with out a single force close on an app. Thanks for you hard work guys :-)
[G1 Android Development] BrooklynAvi:
Battery check in nandroid script

There is a small issue with the battery check in the nandroid script. I don't know if/how it can be fixed from bart.sh but the issue is as follows.

The script checks to see if there is enough battery to perform the backup/restore (forgot when it checks) but it assumes the stock battery. I think it won't run if it's below 25% but I could be wrong. Either way, since I have an extended battery, so 25% of mine is essentially 50% of the stock battery. So if I am at 25% it fails to do the backup/restore even though I still have plenty of battery left. I wonder if there is a way to prompt the user for what type of battery they have and then adjust the check accordingly.

This would probably not be doable since the check is in the nandroid script itself and it would require an edit to that script. It would also have to know what battery levels mean what for each battery. For example, 25% of a 2300 battery is enough but not for the stock battery. I figured I throw it out there as food for thought even though it doesn't seem like it's possible without editing the nandroid script.
[G1 Android Development] schtuka:
it actually worked for me in same situation with tar empty.
[G1 Android Development] dumfuq:
new version is up which doesn't try to mount /system/sd when nandroid-only option is given. This should help for people without appstosd. Granted you still cannot use it from /sdcard because nandroid will fail if /sdcard is mounted.
[G1 Android Development] bkmo:
So where does it store the nandroid if there is no /system/sd and /sdcard is not mounted?
[G1 Android Development] dumfuq:
It still works the same, it just doesn't try to mount /system/sd if '-n' option is set. It shouldn't matter to the average user but keeps it from failing I the user doesn't have a ext partition. Of course without an ext partition the user has to figure out where to put the script in the first place. It could be pushed (every time) to /sbin or whatnot or it could be packed into a recovery image for more permanent use.
[G1 Android Development] PlatinumMOTO:
can someone tell me how to install this because every time I reinstall it it says not found.

I've done it in recovery and while the phone is running and for example I just flashed the new lockscreen and made a backup didn't wipe or anything and then went back to recovery to restore my rom and it says bart not found. I just used it a second ago. and I pushed it back after I flashed the lockscreen.

yet it's still not found.
[G1 Android Development] dumfuq:
Install info is in first post.
[G1 Android Development] PlatinumMOTO:
ok well let me tell you what I've tried I've done it in terminal and recovery.

adb push bart.sh /system/sd/bart.sh - successful but when I restart the phone it's gone.

cp /sdcard/bart.sh /system/sd/bart.sh - not successful.

I flash a lot of ROMS but as soon as I do I put bart in /system/sd/ in recovery and it says successful then when I reboot back into recovery it's not there.

any advice, am I not using the proper commands?
[G1 Android Development] dumfuq:
a) do you have an ext partition?

b) did you remember to mount it before putting script there?
[G1 Android Development] PlatinumMOTO:
Yes I have an ext partition it's ext3 as of now but gonna convert it to ext4 if it makes a difference.

Yes I've mounted mount /system/ is how I did it I read you don't need to type mount /system/sd but the second time I've done it I mounted /system/sd/.

I'll post screenshots so you can advise.
[G1 Android Development] dumfuq:
ext3 vs ext4 shouldn't matter, it's user preference.

there is no need(that I know of) to ever mount /system

mount /system/sd is mandatory for using this script (every time, unless option 2 is chosen)

by default recovery images do not mount /system/sd. Since this is where you placed the script, it needs to be mounted in order to read the file.

you have two options on installing.

option 1) manual installation

while phone is on, make sure /system/sd/bart.sh exists.

reboot to recovery

mount the ext partition

execute script via sh

in terminal

ls /system/sd/bart*
reboot recovery

in recovery

mount /system/sd
sh /system/sd/bart.sh -s myrom #or whatever options you want

Option 2)

The other option is to install Amon_Ra's 1.2.3 recovery image which has bart in /sbin.

If using Amon_Ra's recovery

bart -s myrom

note that when using the version built in to the recovery image there is not a file extension, you don't have to mount the partition, invoke with sh, or use the entire path.
[G1 Android Development] josedecuba:
please help

:confused::confused:well I already have different backup so far but I have another question ..for restoring those backup I need do wipe ....or bart (util) do it alone .please help with this
[G1 Android Development] dumfuq:
Depending on the options, bart will delete what you want from ext partition before restoring a backup.

If you use default options

bart -r myrom

then it will delete everything on /system/sd before restoring the backup
[G1 Android Development] josedecuba:
thank

thank for the answer

but if I did the complete backup bart -s for example from hero rom , I want to come back from cyan rom just need bart -r

sorry for the noob question
[G1 Android Development] dumfuq:
you are correct
[G1 Android Development] BrooklynAvi:
Reboot/Shutdown Option

Can a reboot and shutdown option be added as a switch? The reason I ask is that it takes me 30 minutes to create a full compressed backup of my ext and nandroid and I'd like to be able to do it before I go to sleep.

Here's the scenario. I just started the half hour process but I'd like to head off to bed in 15 minutes but am now forced to wait until the backup completes. I'd love to be able to plug in my phone, start the backup process and have it automatically reboot so my phone's backed up and ready to go when I wake up.

I'm requesting the shutdown option as well in case one wishes to shutdown the phone instead of rebooting. I'll gladly take the reboot only. I would use this feature every single night if you added it.
[G1 Android Development] dumfuq:
Here you go. New version uploaded that includes reboot and shutdown options. These only options only work with store and restore.
[G1 Android Development] BrooklynAvi:
You..Are..The...Man!

Now it just needs to be added to recovery for the myTouch since there's no console.
[G1 Android Development] overground:
All depends on what switches you use. If just you use:

bart -s <romname>

You will backup nandroid and complete ext partition, including any userinit scripts or anything else on ext. Same goes for restore:

bart -r <romname>

You can throw switches in there (see bart -h or OP) for nandroid only backup/restore, ext only backup/restore, and lots more advanced options.
[G1 Android Development] aryndar:
ok I have read all 12 pages and I am just not understanding..., maybe due to lack of sleep trying to save my sdcard from crapping out..

made bart & nandroid backup via Amon_Ra recovery:

sdcard/bart/defaultrom​

sdcard/nandroid/HT845GZ12130/CBDMRS12-20091112-0417​

I realize that my answer is probable posted on page 1, but... argh.. brain not working..

On a new 8GB sdcard, made a 32 mb swap, 512 ext4 and the rest open for files... slick AMon-RA... so slick...

so, what are my steps get my new card up and running...

I need the commands from the recovery console, as, when my sdcard 'hiccups', I am able to boot into recovery, but not the phone (unable to access terminal)

so, so so, sorry for asking something answered so many times, but, I am just not seeing the steps...

thanks for your patience and assistance
[G1 Android Development] aryndar:
Update: 11.18.2009

Found an answer without having to use Bart..

Untar the archive of your ext partition, and drag and drop to new ext partition. You can do a chmod here, but it is not needed due to fix_permissions. Drag and drop everything you want on the FAT32 (now or later, it does not matter). Put the card in the G1, and boot to recovery, drop to the console, run fix_permissions, reboot, and you should be set (Cyanogen has made this too easy).
[G1 Android Development] dumfuq:
user config file

Well I got sick of adding –verbose –reboot and such everytime I used bart, so I made a version which sources a user config file that can be edited to someones needs. The config file needs to be /system/sd/bart.config.

So If for example you have a /system/sd/bart.config that contains:

verbose=1
reboot=1

sh /system/sd/bart -r myrom

would be equivalent to

sh system/sd/bart –verbose –reboot -r myrom

As with bart in general, use with caution.

An example config file is on the first post as well.
[G1 Android Development] dumfuq:
1.1.1

Putting the new one into the recovery image I am using, I noticed the shbang was wrong. So now there is one with proper shbang. User no longer has to invoke with "sh" if permissions are set right. duh.
[G1 Android Development] Zei:
Ok, ive been using amon_ra's recovery for a few weeks now and never touched the BART.

From what im reading, Nand +ext seems to do the same function as the BART. Plz correct me if im wrong on this cause im a little confused on the issue
[G1 Android Development] saleum:
One of the best tools !

I'm using it without the least problem since I discover it. Just great and sure and simple.

A big THANKS for your help. !!
[G1 Android Development] androidmonkey:
I am trying to mount my SD card via console in recovery, I get

mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: Invalid argument

Any ideas whats wrong?
[G1 Android Development] darkfluid:
Can I use this with a perfect SPL, or do I need to get an engineer SPL on my mt3g in order to use fastboot?
[G1 Android Development] tsheeley:
I'm trying to make a backup of Firerats cache-hacked CE (link in my sig)... but I've been getting the empty tar error - which makes sense since Firerats A2SD patch skips the ext partition if you have a Magic phone.

So, that being said, which option do I need to use in order to do a complete backup?
[G1 Android Development] dumfuq:
I'm not really sure, I haven't used that rom. If you used the nandroid only option it would skip the ext like you want, but I don't believe it will back up your cache at all in its current state. In the op of the rom you mentioned it kinda implied that might cause an issue. I am pretty sure nandroid itself has the ability to back up the cache partition itself but I'm not positive and don't know the flags. Anyhow I will look into it when I get a chance.
[G1 Android Development] tsheeley:
Awesome! Thanks!

For giggles, I tried copying the txt file for the current version to the ext partition (as suggested a few posts ago for someone else) - it seemed to work... it didn't throw any errors at me at least. I haven't had the guts yet to wipe and try to restore it tho. Ha! I might give it a try this weekend. If it works, I'll just write up a small batch file to copy a dummy file over and then do the backup and reboot.

Also, can I push 1.1.1 to my current AR recovery? His is a tad behind, I don't think it includes the reboot/shutdown options. What ADB commands would I have to use?
[G1 Android Development] dumfuq:
1.2.0

new version which adds the ability to backup/restore cache partition.

This does not completely backup the cache, it creates a tar/tar.gz file that omits lost+found and recovery folders.

to backup entire rom and cache

bart --cache -s romname

to restore entire rom and cache

bart --cache -r romname
[G1 Android Development] dumfuq:
you can push it to the recovery but it will be gone on reboot. you have to pack a new recovery to get it to stay.

here is a recovery-RA-dream-v1.6.2-blue.img with bart-1.2.0 in it.

If you want to learn to repack your own recovery images read this

http://xdaforums.com/showthread.php?t=443994

when it comes to the mkbootimg command just leave off the "--cmdline 'no_console_suspend=1 console=null" option or the command line won't work in your new recovery.
[G1 Android Development] tsheeley:
Awesome! I can't wait to try this out - most likely sometime in the next day or so.

So the parts that aren't backed up aren't needed in order to get it to boot?
[G1 Android Development] tsheeley:
Again... so very awesome!

Would I have to setup some sort of Linux environment on my computer to repack my own recovery? Up until getting my MT3G I have zero experience with it.
[G1 Android Development] tsheeley:
Before I go flashing this thing and blowing up my toy... this is the proper recovery for Google branded MT3G phones, right?
[G1 Android Development] dumfuq:
No. I didn't notice your sig. Its the dream one. Not around my box now either.
[G1 Android Development] tsheeley:
No rush. Seriously. I'm just thankful that it was able to be done at all.
[G1 Android Development] dumfuq:
alright...this should be the one. Good luck.

recovery-RA-sapphire-v1.6.2G-bart-1.2.0.img
[G1 Android Development] tsheeley:
Re: [UTIL] BART-1.2.0 Backup and Restore Tool

I'll try it out first thing in the morning.
[G1 Android Development] tsheeley:
It was perfect!

Full backup w/cache + full wipe + full restore w/cache = same swanky phone = priceless.

Once my wedding is done in a few months I think I owe a bunch of beers to folks. :D
[G1 Android Development] dumfuq:
bart-1.3.0

New version which now backs up cache partition by default unless --nocache option is given.

Now works in recoverys that mount ext at /sd-ext or /system/sd

So for full nandroid+ext+cache backup it would be

bart --verbose -s romname

obviously --verbose is optional
[G1 Android Development] juangil:
thanks a lot, we really need this for new big sense rom
[G1 Android Development] tsheeley:
Oohh... so does this now mean that we can drop the new version to /system/sd without it going 'poof' when we reboot?
[G1 Android Development] Boomgawd:
Rogers EBi1 (32A) Dream (3.xx radio)

Hey everyone, can someone please post the 1.6.2R with bart-1.2.0 in it?

thanks alot!
[G1 Android Development] dumfuq:
heres the 1.6.2 for dream and sapphireG

recoveries
[G1 Android Development] Boomgawd:
not sure I follow

B not R? are you sure, I have the rogers dream with ebi1 radio (3.x.x)..

I currently have the 1.6.2R installed.

Please confirm.
[G1 Android Development] dumfuq:
not itts not for rogers, I thought you were talking about the stupid carebear color.

Well I threw one in there for Rogers but I have no way of knowing whether it works.
[G1 Android Development] Boomgawd:
Ok so I tried the 1.6.2R-bart1.3.1 and it just freezes at the rogers screen... reflashed the old 1.6.2R...

Not sure whats missing!

Wanna try again?
[G1 Android Development] dumfuq:
Not sure what to say...I just unpacked, added script, repacked. Maybe someone with a rogers can do it. Don't really know what to try.
[Touch HD Themes and Apps] soom:
Hello. I am using the recent WM6.5 roms with manila 2.5.

I would like someone to tell me if there are somewhere here the icons that are used.

These icons:.

I have been searching thread under

xda-developers > Blackstone > Themes, Applications and Software

but with no results. I asked in the rom's thread and still no answer. Even a pm to the creator had no response. So i am asking here. If someone could tell me... I would like to use them in some other roms using older TF3D, that have not these nice icons!:o:o:o:o:o:o
[Touch HD Themes and Apps] antoniomistretta:
Try these!;)

http://rapidshare.com/files/282419569/Icone_Manila_2.5_Touch2_like.rar
[Touch HD Themes and Apps] soom:
Thanks a lot man! I will use them as soon as i flash a rom without these icons! :D

Thanks again! :D:D:D
[Touch Pro CDMA] ApplesNoranges:
Hey whats up fellow TP users. I got a quick question.

I have an Sprint TP, that i flashed to use with MetroPCS. I want to sell it, and i have a buyer, who has Sprint. My question is, To get it back to sprints service, all i have to do is install a sprint stock Rom correct? and that will do the job? or are there other steps and things i need to do. I just need to get the phone working back with sprint again.

Thanks for your time.

Also on a side note, i was thinking of getting a Palm pre, i heard you can flash those to MetroPCS, but i didnt see it anywhere on here, and even on PalmPre forums, i didnt see a step by step or any tutorials.

Any help would be aprreciated. I am selling this in the next 30-40 mins, so please, don't bash. I need quick answers.

Once again thanks.
[Touch Pro CDMA] ApplesNoranges:
No one can help me? 11 views, and not a single comment? I just need help understanding this all. Damn its like that.
[Touch Pro CDMA] ApplesNoranges:
really? No one wants or can help me? I find that hard to believe with this many talented people on this forum. Thanks for nothing.