ok thew00 you got you wanted you too chronic...
i quit...have fun. im handing the team over to spitfirehaz. he will be in charge i quit goodbye
.....
Edit: I never did that irc conversation on dhowwets bullshit site! I didn't say any of that I may not have total proof but I believe thew00 did that.... Funny...not Really fuck you all!
Monday, May 11, 2009
Sunday, May 10, 2009
one step forward...
As you can see we have made slight progress by changing the bootpath to the device but applying anything to the device's ramdisk will be hard including virtual nor,virtual kernel etc...
we are using an iPod touch 1G. as we have said earlier THIS IS NOT DGD!!!!... it is a potential way to achieve it but in any case its not DGD...
we now are coding a patch to apply these componants to the ramdisk
also we have a way to up the size of the ramdisk as to fit the whole OS
Saturday, May 9, 2009
iGavotte FAQ
Q: isnt iGavotte impossible?
A: No iGavotte is not. iGavotte is NOT dgd. its just a bootable ramdisk
Q:how will it work?
A:iGavotte Ramdisk will be a change in the bootpath and will have A virtual NOR written to it. as well as a virtual kernel and kernel parameters.
Q: why is this so importanat?
A: think about this. since iGavotte can run on a clean unjailbroken device, and you make the ramdisk bootable. you may only need to modify the ramdisk and you might have another Exploit for a jailbreak. this may come in handy for the 3rd generation iPhone.
A: No iGavotte is not. iGavotte is NOT dgd. its just a bootable ramdisk
Q:how will it work?
A:iGavotte Ramdisk will be a change in the bootpath and will have A virtual NOR written to it. as well as a virtual kernel and kernel parameters.
Q: why is this so importanat?
A: think about this. since iGavotte can run on a clean unjailbroken device, and you make the ramdisk bootable. you may only need to modify the ramdisk and you might have another Exploit for a jailbreak. this may come in handy for the 3rd generation iPhone.
Thursday, May 7, 2009
my unofficial irc channel(hint hint its not on the list at ALL!)
if you want to chat with abyssalcmd go to iphun.osx86.hu then room is #abyssalcmd
-enjoy
(ill be on every once in a while.)
-enjoy
(ill be on every once in a while.)
this has nothing to do with iphone tech but it has to do with network hacking.
basically theres xat chat room that uses an irc server in gui its the freewebs one i have taken the liberty of disableing it (for like 20 mins too! lol) i took out the room via clone flood! my reason... because the mods are pissy lil (in a polite manner) hoes
Sunday, April 12, 2009
Blast From the Past!
thanks to SpitFirehaz were are now activally making the iGavotte Ramdisk to boot the ipt1g fs on the ipt2g. and so ill activally update and post a download link
new feed 1)
techinical difficulty's... ok so were having a hard time transferring the .DMG file from pc to mac.
edit: Fixed!
new feed 1)
techinical difficulty's... ok so were having a hard time transferring the .DMG file from pc to mac.
edit: Fixed!
Tuesday, April 7, 2009
Announcing the D.G.D. Project
DGD or "DEVICE-GENERATION-DOWNGRADE" is now a long term project for Stand-alone-dev. Basically All devices have a nice code segment declairing them as 2nd gen 1st gen etc...
this differntiation code is inactive while in recovery/dfu modes. so say we write a patch that allows the two device paths to co-exist. by either splitting partition or parralel device trees we could do this. problem is is that if you do a new partition you have to delete the code segment permanantly. so say we put the device in recovery mode apply the patch then copy the 1st gen's generation verification code and write it parralel to the 2nd gen devices generation verification code.then after this we write the device tree on top of the verifyer. then using "args" commands boot between the generations like we do partitions. to do this we need these things:
-(x)iPod Touch 2G (jailbroken)
-patch to tell code sign to more or less "leave it alone its 'signed'.
-(x)devcert. (and an apple dev account and self code signer)
-extracted file system componants from ipod touch 1G (jailbroken or not jailbroken It doesnt really matter.)
-(x) a command line
check back every once in a while to see some exciting results
- stand alone dev team
UPDATE!: iPt1G filesystem extracted.
and now were going to make a gavotte ramdisk per say. in other words instead of writting to the Nor or another partition were going to write the filesystem to the Ramdisk
because:
1) on a jailbroken device the ramdisk isn't sig checked.
2)bootup will be faster
3) because its much easier!.
so when we do this a new boot path must be set then comes the hard part...
because all boot paths are sig checked were gonna need a new exploit or an adapted one
this differntiation code is inactive while in recovery/dfu modes. so say we write a patch that allows the two device paths to co-exist. by either splitting partition or parralel device trees we could do this. problem is is that if you do a new partition you have to delete the code segment permanantly. so say we put the device in recovery mode apply the patch then copy the 1st gen's generation verification code and write it parralel to the 2nd gen devices generation verification code.then after this we write the device tree on top of the verifyer. then using "args" commands boot between the generations like we do partitions. to do this we need these things:
-(x)iPod Touch 2G (jailbroken)
-patch to tell code sign to more or less "leave it alone its 'signed'.
-(x)devcert. (and an apple dev account and self code signer)
-extracted file system componants from ipod touch 1G (jailbroken or not jailbroken It doesnt really matter.)
-(x) a command line
check back every once in a while to see some exciting results
- stand alone dev team
UPDATE!: iPt1G filesystem extracted.
and now were going to make a gavotte ramdisk per say. in other words instead of writting to the Nor or another partition were going to write the filesystem to the Ramdisk
because:
1) on a jailbroken device the ramdisk isn't sig checked.
2)bootup will be faster
3) because its much easier!.
so when we do this a new boot path must be set then comes the hard part...
because all boot paths are sig checked were gonna need a new exploit or an adapted one
Subscribe to:
Posts (Atom)