Blog

  • Redsn0w 0.9.13dev2 Released To Jailbreak iOS 6 Beta 2 And Fix SSH Issue

    Redsn0w 0.9.13dev2 Released To Jailbreak iOS 6 Beta 2 And Fix SSH Issue

    Today Apple pushed out iOS 6 Beta 2 to developers for the application development and other improvements for their applications. The iPhone Dev-Team tackling Apple also released there upgraded version of Redsn0w 0.9.13dev2 to jailbreak iOS 6 Beta 2 and also solve the ex-SSH issue.

    There update notes

    Update #1 – June 15: The “dev2” version should fix the various SSH problems and crashes with apps that some have been seeing.

    This version of developers redsn0w jailbreaks the A4 devices and below, not the A5 and A5X devices. It’s a tethered jailbreak for everyone, as there is no untehtered jailbreak for beta’s in any situation. The users who intend and hope to have Cydia after the jailbreak may stay away because the iOS 6 beta’s after simply jailbreaking son’t get Cydia. The iOS 6 Beta 2 expires on the upcoming 31st July 2012.

    Download the redsn0w o.9.13dev2 for

  • iOS 6 Beta 3 Coming 10 July, iOS Beta 2 Expires 31st July 2012

    iOS 6 Beta 3 Coming 10 July, iOS Beta 2 Expires 31st July 2012

    Like we predicted in past that the iOS 6 beta 2 will debut after two weeks of the first iOS 6 Beta 1 launch. The same thing happened. The second Beta of iOS 6 debuted today for Developers only. All the developers would be digging in the iOS 6 Beta to see for something new and on the same time we will be telling you about the expiry date of the second beta found by, @ih8sn0w, the developer behind the most famous Jailbreaking Tool called Sn0wbreeze. Whenever there is a release of any iOS Beta, he is the first one to tell about the expiry date of that beta.

    According to him, this second iOS 6 Beta 2 will expire 31st July 2012 at 8pm (EST). This news was given by ih8snow on his official Twitter account stating:

    This iOS 6 Beta 2 will be expiring on July the 31st, so we can expect the next iOS 6 beta 3 somewhere from next to next week.  The date we have assumed is 10th of July or 11th of July. The next iOS 6 Beta 3 will be coming somewhere within these dates. So mark up your calendar for the iOS 6 Beta 3 release and set up a reminder for your self to check back for iOS 6 Beta 3.

    To save your time, you can download the iOS 6 Beta 2 from here or if you got your UDID registered, you can do OTA Update.

  • iOS 6 Beta 2 (10A5338d) Is Here, Get It (Direct Links)

    iOS 6 Beta 2 (10A5338d) Is Here, Get It (Direct Links)

     Apple has just released iOS 6 Beta 2 build 10A5338d at the weekend to the developers. The iOS 6 Beta 1 released on 11th of June at the WWDC 2012. The iOS 6 features above 200 features, including the all new 3D-maps, deep Facebook integration, Passbook which slightly keeps all the record of the cards which you have and are in use, Siri completely refined with all new app integration for opening apps and other related tasks with many new languages added.

    Below are the links for the users/developers who hold  a developer account at Apple, the direct links will go live in hours.

     

    Check out the new animation while updating via OTA

     

  • Apple Approves Activator After Display Recorder and Cydia in iTunes

    Apple Approves Activator After Display Recorder and Cydia in iTunes

    Since the iOS 6 beta 1 debuted for Developers after WWDC 12, Apple is challenging the Jailbreaking Community openly. They have started to Approve some well known and most used Cydia Tweaks in their iTunes Store. This is something really strange. The Application approval team at Apple crossed their limit and approved Cydia App in the App Store that is the Copyright name by @Saurik. The same Cydia for which we wait for ages to come to our iDevice is now publicly available with the same name at the App Store with the same image of it. Though the function of that Cydia is not to Jailbreak your iDevice or allows you to have Tweaks after installing that App.

    The Cydia App simply copies the name of the most famous .DEB file from the Jailbreaking community and what it allows is a Snake Game. Can you imagine? The same Snake Game that we used to or we play on our Phone’s. The description of the game used to state that the game character consists of a Caterpillar named Cydia. The job was to collect the Apples with that caterpillar character. The amazing thing about that Cydia App was that it was available at the cost of 0.99$ in the iTunes store.

    Now lets talk about the second Tweak that debuted in the App Store. The name of the Tweak converted into App is called Display Recorder. This is the Tweak that was released in Cydia by Ryan Petrick the Cydia App Developer.

    This was another App that copied the same idea of the Cydia Tweak and the BUGUN Software Co. made an App out of it performing the same functions that the Cydia Tweak does. The App was approved in the App Store recently. The App is now available for sale at 1.99$.

    The best thing is that the release of these two Apps over the App Store wasn’t enough. Few days back another Cydia tweak rolled into the App Store with the same name and fake functions called Activator. This Cydia Tweak is free under the repo of BigBoss, where as the same name App costs 0.99$ in the App Store with fake description. The description of the App vows to deliver the same function as of the Cydia Tweak, though it is only a wallpaper maker.

    cydia-display-recorder-activator

    (image Courtesy)

    This is really epic. The Developers are stealing the name of Cydia Tweaks to make the Apps and increase their sale and they are failing to deliver the same quality functions that the original Cydia Tweak is offering. The best thing is that Apple is approving these fake Apps in the App Store easily. Apple has already started to copy Cydia Tweaks into their iOS versions and now they want to do a battle with the Cydia Tweak developers. It is still unclear that what is Apple up to. Why they are approving already released Cydia Tweaks in the face of Apps in their App Store.

    There is a great saying by some one,

    “If you cannot beat them, so join them.”

    I would like to dedicate this Quote to Apple.

  • Redsn0w 0.9.14b2 to Fix iPad Baseband Downgrade Issues on iPhone 3GS

    Redsn0w 0.9.14b2 to Fix iPad Baseband Downgrade Issues on iPhone 3GS

    Few days back we reported about the iPad Baseband 6.15.00 Downgrade for the iPhone 3GS and iPhone 3G users. After hearing the news of the iPad Baseband downgrade, many of the users owning an iPhone 3GS and iPhone 3G opted to downgrade the iPad Baseband to the old Baseband version of 5.13.02 to get officially unlocked by Ultrasn0w. When they were on the iPad Baseband, Ultrasn0w also unlocked them officially, but they were unable to use GPS on their iPhone 3GS and 3G. So, after the baseband downgrade, they were allowed to use the GPS on their iPhone 3GS and iPhone 3G without any hustle.

    Many of the users owning an iPhone 3GS tried to downgrade the iPad Baseband and they were unable to downgrade it back to the old one. Even they tried every single trouble-shooting step. Still they couldn’t downgrade it back. Few people started to think that their iPhone might have some issue due to which they cannot downgrade it.

    ipad-baseband-dwongrade

    Luckily, @MuscleNerd today regarding this iPad Baseband Downgrade found the problem that was causing this issue. The issue persists in few iPhone 3GS’s that uses a different NOR CHIP due to which the iPad Baseband Downgrade is interrupted.

     There’s a subset of 3GS iPhones that won’t take the downgrade.  We now understand why (they use a slightly different NOR chip), and should be receiving a loaner of such a phone on Thursday the 28th.  After we have one in hand we’ll tweak the redsn0w payload to handle that variation too!

    The good news is that they got the fix for this issue and they are waiting for the iPhone 3GS from a loaner that would be arriving this Thursday the 28th. After they have got that iPhone 3GS, they would be fixing this issue in Redsn0w and after doing a test on that iPhone 3GS, they will release a new version of Redsn0w with that fix. We expect the new version of Redsn0w to be called Redsn0w 0.9.14b2.

    Till then the issue is resolved, if you have an iPhone 3GS or iPhone 3G and want to downgrade the iPad Baseband 6.15.00, you can follow our complete guide for the Downgrade. Incase you face any issue, then wait for this new version Redsn0w coming this Thursday.

    UpdateX1:

    The time we talked about has passed away and still no update to the Redsn0w for the iPad Baseband Downgrade issue because @MuscleNerd haven’t received the iPhone 3GS yet. He is still waiting for the iPhone 3GS to arrive in his hands, so he can proceed on with the downgrade issue.

    Thanks to Val Ernouf for posting in the comments about this latest update. Here is the latest Tweet of @MuscleNerd on the iPad Baseband.

     

    According to the latest Tweet of @MuscleNerd, the status of the deliver is 6/24. This means that the delivery was made on 24 June 2012 and still he doesn’t have the iPhone 3GS in his hand. If the delivery of the iPhone 3GS takes long, @MuscleNerd will be going with the backup plan and most likely, he will release the new version of Redsn0w without testing it or will release the new version to specific testers. After testing, he will make the public release.

    UpdateX2:

    The latest updates are that @MuscleNerd got the iPhone 3GS from the loaner today and he will be doing some extreme testing for few days regarding the iPad Baseband Downgrade.

    Now the iPad Baseband Downgrade for people who couldn’t make it is on its way in few days. At first, it was expected that the new version of Redsn0w would be landing last week on Thursday and it was delayed due to the late arrival of the iPhone 3GS. It was also expected that @MuscleNerd would be going with the backup plan. However, the wait was fair enough.

    Now he finally got the iPhone 3GS, so we can expect the release within few days.

    Thanks to Val Ernouf for the heads up.

  • Samsung Galaxy SIII Catches Fire in the Bottom Bursting Charging Port

    Samsung Galaxy SIII Catches Fire in the Bottom Bursting Charging Port

    A really shameful act copied by Samsung Galaxy SIII from Apple’s iPhone. The Samsung Galaxy SIII, Flagship of Samsung today caught fire at the bottom burning the charging port of the handset. The Samsung Galaxy SIII was released about a month a go and this incident happened after a month. This is something that needs to taken seriously. In past we have heard a lot about Apple Devices that they got burnt/exploded due some circumstances like over charging or the iPhone/iPod went hot and exploded. This Samsung Galaxy SIII is only a month old and it got exploded without any reason makes no sense.

    The Samsung Galaxy SIII didn’t exploded in the showcase or some niche place. It exploded on at the moment when this unlucky user dillo2k10 of a niche form was driving with his Samsung Galaxy SIII; on his way he sawed a white flame coming out of his Phone. He pulled over to see the status of that White Flame from his Phone, what he found was the Phone’s bottom got burned melting the plastic body with damaging a part inside of his car.

     Hi, 

    So I driving along today with my Galaxy S3 in my car mount when suddenly a white flame, sparks and a bang came out of the phone. 

    I pulled in to look at my phone, the phone burned from the inside out. Burned through the plastic and melted my case to my phone. The phone kept working but without any signal.

     

    Then he went to the carrier/shop from where he purchased the Samsung Galaxy SIII to replace it for him under warranty or so. The concerning company simply denied him from claiming the Handset under warranty because they have to send that phone for checking and no phone was giving him as a replacement.

    I brought it to the carphone warehouse and they told me that they couldnt replace it for me that they had to send it off to be checked out first. No even replacement phone, left with nothing. 

    The phone was destroyed and it slightly burned a piece of plastic on the inside of my car.

    Below are the images of the Samsung Galaxy SIII in Flames:

    samsung-s-3-fire

     

    samsung-s-3-hspfa

    samsung-s-3-exploded

    The good news is that the person got neglected by the company from which he purchased the phone was later on contacted by Samsung Officials on this issue. The official Samsung Blog states:

    There have been recent online posts displaying pictures of a Samsung GALAXY SIII that appears to have heat-related damage at the bottom of the device. Samsung is aware of this issue and will begin investigating as soon as we receive the specific product in question.

     

    Once the investigation is complete, we will be able to provide further details on the situation. We are committed to providing our customers with the safest products possible and are looking at this seriously.

    Now Samsung has taken the issue into consideration instantly, we expect that the market value of the Samsung Galaxy SIII might decrease due to this incident only if the matter is taking seriously by people. Still it is not clear that how can a Phone catch fire so easily, the Phone that launched a month a go. This is something strange. This issue raises many questions in a customer’s mind before they go to buy the flag ship of Samsung.

    What we expect is that the person might have putted his phone on the Dashboard of his car where the sunrays would be coming directly through the cars front screen making the phone go heat up and explode.

    Anyways the person got the replacement from Samsung for his Samsung Galaxy SIII with few free gifts, still don’t forget that the Samsung Galaxy SIII was designed for humans and inspired by nature. We hope that you got our point.

    Update X 1:

    Kindly see the update from here. The issue has been resolved and the problem was not with Samsung Galaxy S III.