Posts Tagged ‘Dev Team’
คราวนี้น่าจะออกมาพร้อมกับ firmware ใหม่คือ เวอร์ชั่น 4.0
หรือดูว่าไอโฟนตัวใหม่ออกมาเป็นยังไง ดูว่าช่องโหว่ทางด้าน hardware
เดิมยังสามารถนำมาใช้ได้อีกหรือไม่ ต้องคอยติดตามกัน ต่อไปนะครับ
ยังพบปัญหากับโครงสร้าง Cydia อยู่บ้าง และรอตัว iPad 3G มาทดสอบ และที่สำคัญกำลังมุ่งเน้นไปที่ตัว Hactivate ครับ ( กำลังหาวิธี Bypass จาก Dev-Team อยู่) ถ้าสมบูรณ์แล้วคงเป็นคืนนี้ หรือ พรุ่งนี้เช้าครับ
Rock Out without Lockout
This week Apple will be all over the news with their announcements at Wednesday’s “Let’s Rock” event. But with so many new owners of the iPhone 3GS, and with so many new owners of the iPhone 3G (perhaps sold to them buy these new 3GS owners)…now is a good time to send out this general advisory.
If you update to Apple’s new software using the normal iTunes process, you will lose your ultrasn0w unlock. In fact you may lose it permanently, because for most people the baseband firmware cannot be reverted to a previous version (unlike the main application CPU firmware).
But don’t worry…our PwnageTool program let’s you update your main firmware without touching your baseband firmware, so you can still have the best of both worlds. But you must be diligent about saying “no” to your iTunes request this week to update your firmware.
http://blog.iphone-dev.org/
The iPhone Dev-Team has confirmed that all its tools work well with Mac OS X Snow Leopard.
Snow Leopard, the OS released for Mac on Friday, poses no new wrinkles for the redsn0w jailbreak or ultrsn0w unlock.
You find a tutorial on how to jailbreak or unlock your iPhone (whichever it may be) using this guide.
iPhone 3.0.1 is here now to fix SMS vulnerability and you can still jailbreak it after update
Apple has issued a statement saying less than 24 hours after the demonstration of SMS vulnerability in the conference, they have issued the patch to fix it. You can now update the iPhone to 3.0.1 that fix the flaw in the iTunes now. It will break the current jailbreak, but you can re-jailbreak and software unlock it after the update.
iPhone Dev Team said users can still use redsn0w 0.8 to jailbreak. The trick is that when choosing the firmware, choose the old 3.0 one. (file that ends with _3.0_7A341_Restore.ipsw). They said redsn0w will only touch the part that is not related to 3.0.1 update. You may also install the ultrasn0w to software unlock also. You don’t have to wait for the updated jailbreak tools.
[via iPhone Dev Team]
What’s old is new again
Last night we released updated versions of our redsn0w jailbreak and ultrasn0w carrier unlock. These versions are now compatible with the iPhone 3GS running at 3.0. Welcome aboard, 3GS owners! (The tools of course remain compatible with all of the other platforms too.) Also last night, saurik released 3GS-compatible versions of MobileSubstrate and WinterBoard, components that enable many different add-ons and themes.
We realize we upset some folks (e.g. existing 3GS owners) with our earlier announcement that we wanted to hold onto the 3GS iBoot-family hole until 3.1 was out. Our aim there was to get as many people as possible onboard (within reason of course) before revealing the hole, since Apple will fix it immediately. But all of that became moot when the purplera1n release was made, since it uses the same hole.
For those of you who already own 3GS phones, the outlook is bright. As long as you have your personalized (signed) dfu/img3 files, you’ll always be able to jailbreak (even if you slip up and install stock Apple firmware in the future). For those of you without 3GS phones, it’s a race against the clock to use this particular hole. There’s nothing we can do about that, but we will always be looking for new holes.
ultrasn0w unlockers — You all must remain particularly vigilant against upgrading your basebands, since doing so will kill the unlock (for most phones, there’s no going backwards in baseband version). Apple has gotten very serious with the latest baseband — they’ve removed 180 (!) commands in an effort to cut down their exposure to holes. So please always stay away from stock Apple IPSWs and instead use our tools as we release them. These tools let you update your firmware without updating your baseband.
Those installing ultrasn0w will probably also need to do a single run of Settings->General->Reset->Reset Network Settings. We’re testing various fixes for that particular glitch.
Once again, thanks to @Oranav for finding the new injection vector that allowed us to transform yellowsn0w for baseband 02.28 into ultrasn0w for baseband 04.26, and for not revealing it to Apple before it could be used where it would be most effective — firmware 3.0.
redsn0w platforms — This is the first redsn0w release that also supports linux! It’s the newest version of the bunch, so any feedback would be appreciated. But right now, redsn0w should work on OS X, Windows, and linux.
How to get the goods:
- The redsn0w torrent seeds are all here. Any direct mirroring help would also be appreciated.
- The updates to ultrasn0w, MobileSubstrate, and WinterBoard are all handled directly through Cydia (after you’ve jailbroken!)
- The Cydia repo for ultrasn0w is http://repo666.ultrasn0w.com (that last o in ultrasn0w is the number 0!)
หลายท่านที่ใช้ Hacktivate iPhone คงจะมีปัญหาเรื่อง push notification ใช้งานไม่ได้
ตอนนี้ทาง Dev team ได้ปล่อย ตัว trial fix push ออกมาแก้ปัญหาเรื่องนี้แล้วนะครับ
How to
อันนี้เป็น step by step จาก Dev team
Push Solution Test Steps
————————
A. Get Legit Keychain Data:
*You Must Perform These Steps On A Properly Activated Device (iphone or ipod touch) with at least one working push app*
1.Unzip the downloaded zip file and copy the binary ‘nimble’ using SSH into /private/var/Keychains and set permission to 0755
2. Make sure the file “keychain-2.db” is in /private/var/Keychains and run nimble. You will see 4 files being created:
- youtube-cert.bin
- youtube-key.bin
- push-cert.bin
- push-key.bin
3. Copy these 4 files into the corresponding folder on your hactivated device.
B. Testing Push:
*You Must Perform These Steps On Your Hacktivated Device*
1.Unzip the downloaded zip file and copy the following files using SSH into /private/var/Keychains and set permission to 0755:
- inject
- nimble
2. Store in somewhere else the current “keychain-2.db” and run inject. A new keychain-2.db will be created
3. Uninstall the push app (i.e. beejive or similar) you intend to test on from your hacktivated device and reboot
4. Test youtube, reinstall the above push app and test.
ผมจะสรุปมาให้ง่ายๆดังนี้นะครับ
1.โหลดไฟล์นี้ก่อนครับ http://bit.ly/FxBtZ
2.โหลดไฟล์นี้ http://www.sendspace.com/file/e1kbmg
3.แตกไฟล์แรกที่โหลดมาจะได้ ไฟล์ inject และ nimble
4.นำไฟล์ที่แตกมาแล้วไปวางไว้ที่ /private/var/Keychains และ set 755
5.แตกไฟล์ที่2 จะได้ไฟล์ นามสกุล bin ทั้งสิ้น4 ไฟล์
6.นำไฟล์ bin ทั้งหมดไปวางไว้ที่ /private/var/Keychains
7.เปิด winscp แล้วเข้าไปที่/private/var/Keychains จากนั้นเปิด terminal command
8.ใช้คำสั่ง ./inject แล้วกด execute
9.ทำขั้นตอนทั้งหมดนี้เสร็จแล้วให้ uninstall push app ในเครื่องออก(ถ้าไม่เอาออกใช้ได้มั้ย อันนี้ผมยังไม่ได้ลองนะครับ) แล้ว reboot
10.เมื่อreboot เสร็จแล้วให้เข้าไป test youtube ว่าใช้ได้มั้ย แล้วลง push app อีกครั้ง แล้วลองใช้ได้เลยครับ
ตอนนี้ push ก็มาแล้วครับ
ฟ้องด้วยภาพ :spiteful:
ขอบคุณ Dev team ครับ
ขอบคุณพี่โดนัทด้วยครับสำหรับข้อมูลเพิ่มเติม
Thank Frezzer
Only so many ways to say it
You’ve seen us give this warning before, and there are only so many ways to say it or come up with a clever title 
But here it is: ultrasn0w users must stay away from any firmware updates past 3.0 (including today’s 3.1 beta) until we release the tools that let you update the firmware without updating the baseband. For most phones out there, baseband updates are irreversible and you’ll lose ultrasn0w.
The 3.0 jailbreak was one of those (rare) times where both the jailbreak and the unlock coincided (the only other time was 2.2). It’s important that people realize that *most* firmware releases aren’t like that, and you need to take steps (via the tools) to separate the firmware update from its included baseband update.
This warning does not apply to the iPhone 2G, which uses BootNeuter for the unlock, not ultrasn0w.
Spock said it best: “The needs of the many outweigh the needs of the few…”
Summary:
We can jailbreak the 3GS right now. But making our jailbreak public at this point in time would benefit relatively few people. It would in fact be detrimental to many more people than it would help. So we feel it’s best to keep our version of the jailbreak out of Apple’s sights for the time being.
Details:
If you already have a 3GS phone and have already done a full USB dump or captured your img3’s signed with your ECID, then you’re in great shape. You will always be able to jailbreak. But many people who plan on getting a 3GS do not yet have one. For instance, many people are waiting for their existing contracts to mature to the point where they get a price break on the 3GS. Many people are trying to sell their 3G before they can buy the 3GS. There are parts of the globe where you can’t even buy a 3GS yet! The reasons are varied, but they are many.
The nature of the 3GS hardware allows Apple to stop IPSWs from being usable unless you’ve already gotten the signed chunks they send to you based on your ECID (a unique chip ID). You cannot get these signed chunks without knowing your ECID, and you don’t know your ECID until you’ve bought your 3GS.
The jailbreak requires at least one signed iBoot-family img3 for your device. And that iBoot needs to have an exploitable bug. It’s an all-or-nothing deal…you either have your signed exploitable iBoot ready to use, for now and forever — always jailbreakable — or you have nothing.
Here’s the critical point, the reason why we’re delaying our version of the jailbreak: Once the jailbreak is out, Apple will fix the iBoot-family bug we use to accomplish it. They will simply stop signing the old iBoots and only sign the fixed ones. If you bought your phone after Apple has done this, there’s nothing you can do…the jailbreak isn’t going to work for you.
It is possible that Apple will find the bug we use without our handing it to them on a silver platter (via a public jailbreak). In that case, we will have delayed our jailbreak for “nothing”. But we’d rather be safe than sorry!
