Initial install of the jailbreak code did not change this behaviour. This ping-response was useful for diagnostic purposes. The original behaviour of the iPad 1, if configured with static ip values, meant that if was on, and the wifi was enabled, it would respond to a "ping", even if the screen was "asleep". 1, running iOS 5.1.1, using Redsn0w, the initial install of the code that provides root access does not include standard inetutils. Maybe a security feature? If so, can I back out the network stuff, and just have ssh access, and have it not timeout? I want to to be "alive" all the time. I could, before I installed the networking utilities. If I set the iPad down, after a few minutes, I cannot ping it from any machine on my LAN. This is new behaviour, since the Cydia "inetutils" install. Really fine stuff, but I notice now that the iPad network access times out quickly. This makes an old tablet very, very useful. But there was no "ping" on the basic jailbreak version, so I installed "inetutils", which provides all the GNU inet stuff (ping, ftp, inetd, rlogin, telnet) and then found "arp iconfig netstat route traceroute" in Network Commands. Installed DOSbox (using b file), and it works fine. Installed OpenSSH, and I can use Putty on Windows or SSH on Linux to login to my iPad, and of course, pscp or scp to migrate files to/from using Windows or Linux. Any direct mirroring help would also be appreciated.I have done a jailbreak on old iPad 1, using redsn0w. But right now, redsn0w should work on OS X, Windows, and linux. 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. Once again, thanks to 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. We’re testing various fixes for that particular glitch. Those installing ultrasn0w will probably also need to do a single run of Settings->General->Reset->Reset Network Settings. These tools let you update your firmware without updating your baseband. So please always stay away from stock Apple IPSWs and instead use our tools as we release them. Apple has gotten very serious with the latest baseband - they’ve removed 180 (!) commands in an effort to cut down their exposure to 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). There’s nothing we can do about that, but we will always be looking for new holes. For those of you without 3GS phones, it’s a race against the clock to use this particular hole. 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). But all of that became moot when the purplera1n release was made, since it uses the same hole.įor those of you who already own 3GS phones, the outlook is bright. 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. existing 3GS owners) with our earlier announcement that we wanted to hold onto the 3GS iBoot-family hole until 3.1 was out. 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. These versions are now compatible with the iPhone 3GS running at 3.0. Last night we released updated versions of our redsn0w jailbreak and ultrasn0w carrier unlock.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |