Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - woodfix

Pages: [1] 2
Hello, I'm new to developing for jailbroken devices.

Can I use XCode 4.3.2 (or thereabouts) to develop for Whited00r?

Also would like to know the same about developing for jailbroken 4.2.1 devices.

Links welcome.

I hope this is the correct topic for this. I am planning a move to whited00r on my 3G because performance is important to me.

But Whited00r will be a drop in security I think because it is 3.1.3. This is tradeoff and I understand but I have questions.

Does Whited00r have any additional security enhancements or control over iOS 3.1.3?

Do all 3.1.3 exploits also work on Whited00r? Are all known exploits browser based?

Great project. Thank you.

Tried the guide recommended by Bomslang for 4.2.1. I used only Daemon Tool and SBSettings, did not reinstall the phone at all. After couple of days running and few reboots everything is faster. Still not as fast as I'd like in some areas but a big improvement. The guide recommends some Springtomize settings. It is a paid app, so I skipped that for now since I am working still towards Whited00r.

Whited00r Development - Archive / Re: RealBackup
« on: May 16, 2012, 12:09:58 PM »
So, my backup finally completed. Yay!

But there is a problem - RealBackup requires an enhancement/bugfix relating to 'Camera Roll'. Here's why:

When you are shooting photos with iPhone, the photos are put in a folder called DCIM/100APPLE. Until...

You reach 999 photos - the next 999 photos are placed in a new directory DCIM/101APPLE (etc).

RealBackup does not capture from DCIM/101APPLE. (Note: The BTH and THM files for /101APPLE are in the archive correctly).

I'll tar those files in DCIM/101APPLE manually, and untar them on the destination :  ).

That should work right?

Logs attached.

Whited00r Development - Archive / Re: RealBackup
« on: May 15, 2012, 11:37:38 PM »
So I freed a bit of RAM using Sinful's Daemon Tool. Then rebooted and began again with realbackup.

I'm about 15 hours in, DCIM.tar size 395MB. Freeing some ram did not make a huge difference unfortunately.

PS gives the command line as "/usr/bin/tar -prf /private/var/mobile/Backup/may14b2/DCIM.tar IMG_0739.JPG" (of about 1200)

Each file is added to the archive individually, and then another file is added, and so on.

I wonder if this process would be much faster if the approach was tar of the directory instead? :-\

Closer to when the process started ([email protected]) tar time for each file was 11 seconds realtime (reading under 2 seconds CPU time).

The current tar time for each jpg is approx 3 minutes 20 seconds realtime. (reading 23 seconds CPU time) - and getting longer all the time.

As you can see, this will take a really long time to complete.

Whited00r Development - Archive / Re: RealBackup
« on: May 15, 2012, 09:11:12 AM »
I still have the terminal history. Definitely deleted the specified file.

My-iPhone:/User/Library/Preferences root# rm com.realblack7.realbackup.plist

No change after a normal restart. I reinstalled RB.

Looking at top during operation. Each JPEG is currently taking 5.50 seconds of CPU time to go into the archive. In realtime that's about 40 seconds. My guess is this increases as the archive grows in size. It is currently 128MB. When it was at 67MB it was under 2 seconds CPU time and 11 seconds realtime.

I think I'm going to try running my own tar and integrate that with the RB archive package. Or something like that. Any suggestions appreciated..

Whited00r Development - Archive / Re: RealBackup
« on: May 15, 2012, 06:34:43 AM »
I deleted the file and hard reset afterwards. Now I have a new problem - realbackup does not start. I am returned instantly to the home screen.

Reinstall RB?

Whited00r Development - Archive / Re: RealBackup
« on: May 15, 2012, 03:54:11 AM »
Another interesting thing - after exiting RealBackup DCIM.tar is still growing. I don't have multitasking enabled. Is this a bug or expected behavior?

Whited00r Development - Archive / Re: RealBackup
« on: May 15, 2012, 02:00:20 AM »
Every time I start the phone - realbackup asks me if I want to start the backup?

Is there a way to turn off this option?
Also, how does it do this?


Whited00r Development - Archive / Re: RealBackup
« on: May 15, 2012, 01:52:19 AM »
Unfortunately it's only added 8MB to DCIM.tar in the last hour, so it looks like it is grinding to a halt.

I'm thinking i might need to do something to increase the RAM available and try again.

Whited00r Development - Archive / Re: RealBackup
« on: May 14, 2012, 10:37:22 PM »
Thanks for that. I'll compare the db structure of each file from 4 to 3 before I run the restore. I might also restrict the restore to - sms history, contacts and perhaps photos.

If I need to modify a database file before the restore - can I just manually update and replace that file in the realbackup archive? Will the restore process be happy to go ahead after an update to the archive?

Meanwhile, still doing the backup, my DCIM.tar has reached 475MB after 19.5 hours. Hopefully that completes before I desperately need to use the device lol.  :)

Hey, thanks for your opinion on that. I'm struggling a bit to get my data from my 4.2.1 to Whited00r (3.1.3), and your method is a good alternative if I get some UI speed back.

The other big concern I have about Whited00r (3.1.3) is the security aspect. Not so much from the Whited00r build itself but just the implications of running 3.1.3 in today's world.

On the app compatibility aspect, there is a post in the thread you linked to which tells how to spoof the version number so apps will run:

If there are no serious API differences in the app that should work. No doubt there are many caveats to be aware of, but useful. Many developers don't try earlier versions for compatibility so they just set the version to 4 or 5 because that is what they are developing on. Many of these apps will run on 3 just fine.

Even when Redd00r arrives we will have the same problem with apps for the next version. It is a good project to figure this out. If there is a team looking at the problem I'd like to keep in touch with that.

Whited00r Development - Archive / Re: RealBackup
« on: May 14, 2012, 08:58:18 AM »
and you are going from 4.2.1 to 3.1.3 right?

Yes, that is correct. I'm planning to take my data off 4.2.1 iOS, put Whited00r on the same phone, and then restore the data to Whited00r 3.1.3 on the same phone.

from 3.1.3 it is possible to just restore and everythings fine. i did not try the other way around

Are you saying the path of backup on 4.2.1 (iOS) and then a restore to 3.1.3 (Whited00r) is not tested and therefore it might not work?

Sorry for the question, I just need to make sure I understand what I'm in for here. ;D

Whited00r Development - Archive / Re: RealBackup
« on: May 14, 2012, 06:27:09 AM »
well. photos are uncompressed. as you see it is saved as dcim.tar not dcim.tar.gz

Thanks for pointing that out. I'm new to 'nix. It just surprised me that it took so long for a .tar wrap.

Any way of speeding up or optimizing that process? At present it is looking like (guestimate) six hours or so, which just seems a bit excessive.

so you just backed up personal data and recordings.

Yes, that's correct. I'd like to get the photos if possible as well, but I'm not sure I can leave the phone on the desk for the required amount of time.

Would it be simple for me to perform the entire process (or maybe just the photos) manually with scp directory copies - or does Realbackup do a lot of db attach/detach type stuff to make it all work?


Whited00r Development - Archive / Re: RealBackup
« on: May 14, 2012, 05:22:39 AM »
I tried with Camera Roll preference 'Off'. The backup completes quickly and exits to main screen. There is no completion notification message. After that my location contains:

-rw-r--r-- 1 root mobile 299K May 14 14:56 Recordings.tar.gz
-rw-r--r-- 1 root mobile 634K May 14 14:56 personaldata.tar.gz

Is that a successful backup?

I also tried again with Camera Roll 'On'. I'm monitoring the creation of DCIM.tar (with SSH). Creation is very slow. I have just under 700MB of photos - after 3 hours DCIM.tar has reached only 192MB.

I'd like to suggest a new version using zero compression for the photos and any archive which will contain them. Wrap only. There is little to be gained by compressing JPG's. :)

I've attached the logs. There is very little in them. Do they overwrite each run? Hopefully they are no longer needed if the mysteries are mostly solved.

Pages: [1] 2