Debugging and getting the system up and running.
My rig and a friend's running headless and mining away!
Saturday, February 15, 2014
Doge Mining: to the moon!
Obligatory components-in-boxes pic:
Debugging and getting the system up and running.
My rig and a friend's running headless and mining away!
Debugging and getting the system up and running.
My rig and a friend's running headless and mining away!
A Bitcoin Miner's Journel
Everybody has a bitcoin story, here is mine (wall of text warning):
Early August in 2011, I started seeing the occasional Reddit post about some new currency called Bitcoin. I did my homework and once I started to process how it worked I was immediately in love with the idea that my computer could help create a currency by crunching some algorithm via the GPU. I've contributed to the distributed programs Folding@Home and SETI since High School, but this one would actually make me money! I spec'd out a decent mining rig for around $1000 using other people's hardware as a baseline to hit my goal of 1500 Mhash/s. I let the rig sit in my cart for a week and finally decided against it. Posts kept appearing claiming I missed Bitcoins big boom and mining was no longer economically feasible. Bitcoin was almost a dollar or something ridiculous and the difficulty factor was rising quickly.
The idea was still interesting and fun so I decided to throw together a mining rig with some parts that I already had. I mined from August until January 2012 and made about .6 BTC. During this span BTC doubled from $1 to $2. That would be great for an investor but, for a miner, $1.20 in BTC was hardly worth the 6 months in electricity I was using. I considered the experiment a complete and powered down the miner.
Through the year Bitcoin continued to slowly climb in value. I continually spec'd out new systems but never had the spare cash to actually buy one. It broke $10 around November 2012, which was a big deal. The idea that a digital cryptocurrency with no tangible value and no governments backing it could be worth $10 each was mind blowing. That was enough for me to fire up the mining rig again and see what the current yield was. I didn't stop with the one rig this time though. On and off, every computer in my possession was mining when it was not in use. When the month was over I tallied up the total and discovered I mined .4 BTC. Even with the rise in BTC value, it still was not economical to mine with my current hardware. I shut everything off once that .4 BTC was added to my .6 BTC. Having 1 Bitcoin in my wallet was enough to give me closure on this whole ridiculous thing. Or so I thought.
Bitcoin started exploding in early 2013. By March it was obvious it could actually hit $100 per BTC. I could not handle sitting idle any more! I did not have much but I was able to budget $100 for some new hardware. I snagged a deal for two Radeon HD 6750s for $100 and put them to work immediately. The payout was awesome, at first. I was making about .05 BTC a day! After about a week, .05 BTC every other day. Then once every three days. As the value went absolutely crazy, more and more miners were joining. This causes the difficulty to rise. And it did not take long for my cheap cards to become as obsolete as my original miner. And then the final blow, the ASIC Block Erupter, an FPGA programmed to mine Bitcoins. These were so efficient that one of them could mine as well at both of my cards at a fraction of the Watts. All GPU miners were now becoming obsolete. I shut down the miner July 2013 once I was down to mining .005 BTC a day. To celebrate the end, I ordered Dominos Pizza using Bitcoin which ended up costing me .4 BTC.
My total earnings during this experience was around 2.2 BTC but the fun had and knowledge gained was priceless. I also learned to trust my instincts more. If it weren't for being otherwise dissuaded, I would have built that rig in 2011. Almost everybody who knew about Bitcoin in the beginning has a story about how they were so close to being millionaires. Some were much closer to others and some were actually millionaires that lost their fortunes in different ways. I was somewhere in the middle, I did not come out of it badly but there will always be some regret.
Early August in 2011, I started seeing the occasional Reddit post about some new currency called Bitcoin. I did my homework and once I started to process how it worked I was immediately in love with the idea that my computer could help create a currency by crunching some algorithm via the GPU. I've contributed to the distributed programs Folding@Home and SETI since High School, but this one would actually make me money! I spec'd out a decent mining rig for around $1000 using other people's hardware as a baseline to hit my goal of 1500 Mhash/s. I let the rig sit in my cart for a week and finally decided against it. Posts kept appearing claiming I missed Bitcoins big boom and mining was no longer economically feasible. Bitcoin was almost a dollar or something ridiculous and the difficulty factor was rising quickly.
The idea was still interesting and fun so I decided to throw together a mining rig with some parts that I already had. I mined from August until January 2012 and made about .6 BTC. During this span BTC doubled from $1 to $2. That would be great for an investor but, for a miner, $1.20 in BTC was hardly worth the 6 months in electricity I was using. I considered the experiment a complete and powered down the miner.
Through the year Bitcoin continued to slowly climb in value. I continually spec'd out new systems but never had the spare cash to actually buy one. It broke $10 around November 2012, which was a big deal. The idea that a digital cryptocurrency with no tangible value and no governments backing it could be worth $10 each was mind blowing. That was enough for me to fire up the mining rig again and see what the current yield was. I didn't stop with the one rig this time though. On and off, every computer in my possession was mining when it was not in use. When the month was over I tallied up the total and discovered I mined .4 BTC. Even with the rise in BTC value, it still was not economical to mine with my current hardware. I shut everything off once that .4 BTC was added to my .6 BTC. Having 1 Bitcoin in my wallet was enough to give me closure on this whole ridiculous thing. Or so I thought.
Bitcoin started exploding in early 2013. By March it was obvious it could actually hit $100 per BTC. I could not handle sitting idle any more! I did not have much but I was able to budget $100 for some new hardware. I snagged a deal for two Radeon HD 6750s for $100 and put them to work immediately. The payout was awesome, at first. I was making about .05 BTC a day! After about a week, .05 BTC every other day. Then once every three days. As the value went absolutely crazy, more and more miners were joining. This causes the difficulty to rise. And it did not take long for my cheap cards to become as obsolete as my original miner. And then the final blow, the ASIC Block Erupter, an FPGA programmed to mine Bitcoins. These were so efficient that one of them could mine as well at both of my cards at a fraction of the Watts. All GPU miners were now becoming obsolete. I shut down the miner July 2013 once I was down to mining .005 BTC a day. To celebrate the end, I ordered Dominos Pizza using Bitcoin which ended up costing me .4 BTC.
My total earnings during this experience was around 2.2 BTC but the fun had and knowledge gained was priceless. I also learned to trust my instincts more. If it weren't for being otherwise dissuaded, I would have built that rig in 2011. Almost everybody who knew about Bitcoin in the beginning has a story about how they were so close to being millionaires. Some were much closer to others and some were actually millionaires that lost their fortunes in different ways. I was somewhere in the middle, I did not come out of it badly but there will always be some regret.
Tuesday, February 4, 2014
RTL SDR: Running gqrx on OSX
This post is long overdue. Mid-2012, some ubernerds were poking around some cheap Realtek RTL2832U based USB TV tuners and discovered they could use GNU Radio to receive and demodulate a much wider frequency range than the device was designed for. I saw a Reddit post referencing the breakthrough and got really excited over the idea of a Software Defined Radio for the average dude. I subscribed to the new subreddit, /r/RTLSDR, and ordered an ezcap DVB-TFM DAB on DealExtreme.
I received the ezcap and, like many before me, had no clue where to start. I grabbed a Raspberry Pi and installed GNU Radio since I knew that was Step 1. Then I started compiling other people's projects with mixed results. All I wanted (to start) was an easy to use GUI with a few demodulation options and maybe a waterfall. Through searching I found gqrx. This software meets everything I wanted and more. The RPi is not exactly known for being a workhorse; and demodulating a FM signal and showing the waterfall for a 1MHz bandwidth brought it to its knees. If only something existed for OSX, an easy solution to implement on my MacBook. If only...
it does! A hero named Elias Oenal went into an older version of gqrx and ported it to OSX. It doesn't get any easier than this. Download gqrx_8.dmg, install it, plug in the ezcap, enjoy!
Bonus pic: talking to myself.
gqrx on crunchbang on a M6400 receiving an AM signal being broadcast from the Arduino
I received the ezcap and, like many before me, had no clue where to start. I grabbed a Raspberry Pi and installed GNU Radio since I knew that was Step 1. Then I started compiling other people's projects with mixed results. All I wanted (to start) was an easy to use GUI with a few demodulation options and maybe a waterfall. Through searching I found gqrx. This software meets everything I wanted and more. The RPi is not exactly known for being a workhorse; and demodulating a FM signal and showing the waterfall for a 1MHz bandwidth brought it to its knees. If only something existed for OSX, an easy solution to implement on my MacBook. If only...
it does! A hero named Elias Oenal went into an older version of gqrx and ported it to OSX. It doesn't get any easier than this. Download gqrx_8.dmg, install it, plug in the ezcap, enjoy!
Bonus pic: talking to myself.
gqrx on crunchbang on a M6400 receiving an AM signal being broadcast from the Arduino
Friday, January 31, 2014
Christmas Lights 2013
After a year hiatus I finally finished the redesigned light controllers and put on a Christmas light show! Video first. Here is the new song for this year.
Vixen played the show automatically on the half hour. Much better than manually triggering it in the cold! I also added an FM transmitter to allow the audience to enjoy the show from their warm horseless carriages. Also, a bit more neighborly than gigantic speakers blasting TSO all hours of the night.
As I discussed in my 2011 review, the hundreds of extension cords had to go. My best solution was to use the software approach of object orientation to break up the large relay boards into smaller, manageable modules. I knew I wanted 5-6 relays per box, so CAT5 worked perfectly to carry the Arduino signals to the relay boards. Working with my buddy, Josh Arndt, we came up with a plan and he designed some extremely professional relay boards. It simply took two years for me to get the boards made and tested.
But first! I had to put the Arduino in something to protect it. Since I was using CAT5, I figured one of the broken Linksys routers lying around would do nicely. It's not super pretty but it holds the Arduino and the RJ-45 rail.
Now time to focus on the relay boards. The boards were soldered and tested.
I harvested most of the parts from the original light controller.
I used our CNC machine to mill out the junction boxes and face plates.
Test fitting the 6-gang wall cover.
Time for assembly!
The whole set, collect them all!
Finally, time to set up the show! You can see the extension cords are not gone but this is much, MUCH cleaner than 2011.
The show went extremely well! The entire thing was fully automated and broadcast on 91.1FM. It almost looked professional. (Minus me never putting up a sign to specify the frequency, DOH!)
Here is the entire ~15 minute show.
What are the plans for next year? Well, now that the base 5 boxes (30 channels) are built, all I have to do is add as many boxes as I need to expand the show. When/if I max out my Arduino, Vixen even supports adding multiple Arduinos as COM port controllers. I may even make one of the boxes solid state relays for 6 dimming channels with PWM. So stay tuned for many more updates and changes as this crazy experiment continues to evolve!
I leave you with a couple aerial shots taken with the quad. Yes, it was the X1; the big quad is still in pieces. (Coming soon: my loving wife got me a Y-6 for Christmas! w00tw00tw00t)
CREDITS
Ashley - Motivation and wire debuncher
Evie - Motivation and wire buncher
Josh - Relay board design and part time genius
Peter - Uber debugger and master of solder
Mat - Electron tamer lvl 1
Tyler - Light man (no fear of heights)
Shawn - Audio expert
John - Common sense consultant
This isn't a one-man show. You don't get far trying to do things alone. It pays to have awesome friends willing to share your passions and interests. Thanks everybody!
Vixen played the show automatically on the half hour. Much better than manually triggering it in the cold! I also added an FM transmitter to allow the audience to enjoy the show from their warm horseless carriages. Also, a bit more neighborly than gigantic speakers blasting TSO all hours of the night.
As I discussed in my 2011 review, the hundreds of extension cords had to go. My best solution was to use the software approach of object orientation to break up the large relay boards into smaller, manageable modules. I knew I wanted 5-6 relays per box, so CAT5 worked perfectly to carry the Arduino signals to the relay boards. Working with my buddy, Josh Arndt, we came up with a plan and he designed some extremely professional relay boards. It simply took two years for me to get the boards made and tested.
But first! I had to put the Arduino in something to protect it. Since I was using CAT5, I figured one of the broken Linksys routers lying around would do nicely. It's not super pretty but it holds the Arduino and the RJ-45 rail.
Now time to focus on the relay boards. The boards were soldered and tested.
I harvested most of the parts from the original light controller.
I used our CNC machine to mill out the junction boxes and face plates.
Test fitting the 6-gang wall cover.
Time for assembly!
The whole set, collect them all!
Finally, time to set up the show! You can see the extension cords are not gone but this is much, MUCH cleaner than 2011.
The show went extremely well! The entire thing was fully automated and broadcast on 91.1FM. It almost looked professional. (Minus me never putting up a sign to specify the frequency, DOH!)
Here is the entire ~15 minute show.
What are the plans for next year? Well, now that the base 5 boxes (30 channels) are built, all I have to do is add as many boxes as I need to expand the show. When/if I max out my Arduino, Vixen even supports adding multiple Arduinos as COM port controllers. I may even make one of the boxes solid state relays for 6 dimming channels with PWM. So stay tuned for many more updates and changes as this crazy experiment continues to evolve!
I leave you with a couple aerial shots taken with the quad. Yes, it was the X1; the big quad is still in pieces. (Coming soon: my loving wife got me a Y-6 for Christmas! w00tw00tw00t)
CREDITS
Ashley - Motivation and wire debuncher
Evie - Motivation and wire buncher
Josh - Relay board design and part time genius
Peter - Uber debugger and master of solder
Mat - Electron tamer lvl 1
Tyler - Light man (no fear of heights)
Shawn - Audio expert
John - Common sense consultant
This isn't a one-man show. You don't get far trying to do things alone. It pays to have awesome friends willing to share your passions and interests. Thanks everybody!
Friday, November 1, 2013
Ardupilot FPV Quadcopter
If you read my previous post on my FPV Syma X1, you'd probably guess it was only the beginning. You would be right.
I started building a quad on a Hobbyking SK450 around Christmas last year. Initially I wanted to make a simple, cheap quad to learn to fly on. I built it with all HK parts with motors being the exception. I've learned through others that cheap, wobbly motors cause most issues with these quads. So I sprung for some CarbonBird motors from MultiwiiCopter. I slowly built it over six months or so and used a cheapo HK KKBoard clone as the flight controller.
After some software tweaking she finally flew. It was not the easiest thing to fly as almost all of my experience came from fixed wing. It made me reluctant to fly it, especially since this is my most expensive RC model. Around this time I found the Syma X1 which was the perfect trainer for me to learn on and the big quad got put on the shelf.
Between my X1 practice sessions I started helping a friend work on his Ardupilot controlled Bixler. After the maiden I knew what I wanted to do with my quad.
I decided to go with the HK Ardupilot 2.5 clone since I knew anything on a quad is not long for this world. I added a HK UBLOX GPS, HK telemetry module, HK video transmitter downlink, and eBay 808 v2 720p camera. All powered up with the video transmitter on board.
The command and control Mission Planner software with all systems running. (No GPS link since I was indoors.)
I wish I could have caught the maiden of this beauty but the microSD card ejected itself mid-flight and was never seen again. It seems MissionPlanner defaulted the flight speed to 100mph. So that first flight was kind of... intense.
The second flight went well, I hover-held over my parent's house. Got some decent shots of the Patuxent River on a gloomy, overcast day.
We had a freak warm day on Halloween this year. Knowing this would probably be the last nice day before winter, I decided to give waypoint navigation another try. I tweaked some settings and went to Saint Mary's College of Maryland (SMCM) since it's the largest publicly available field I know of. The quad flew beautifully! It navigated waypoints smoothly and held point even with the light gusts of wind. The video is worth a watch.
If you watched the video, you're probably wondering what happening. I was wondering the same thing as I numbly gathered pieces not even expecting the camera to still be filming. The last frame is my surprised face that the camera was working (its case was split apart) and then excitement that maybe the cause of the crash could be revealed.
After some "video analysis" (frame-by-frame in VLC) I found some really spectacular stills. Especially in those moments of flashes on impact. But first, I present a UFO right at the beginning of the tumble. I have no idea what it is. All wiring was accounted for and attached, so that isn't it. Maybe a bug?
Next we see what caused the unfortunate accident.
Yup, that's one of the four very important propellers branching off to try flight on its own. I assume the cause was the prop adapter loosened itself during the jerky corrections when fighting the wind 50 meters up. The trailing edge of the prop had a chip out of it. Only the leading edge should chip if it was spinning in its rightful place. The prop likely got nicked by another prop before fluttering away.
With that closure I can begin my grieving. I got some nice orbits before it hit, so that helps a little. Also, the destruction is interesting to watch. Keep in mind this is frame-by-frame at 30fps. This happened really, really quickly.
You can see the moment of impact and first bounce. The camera takes a slightly jigglyer image than usual and you can see it abandoning ship in the next image. Now for my favorite part, the quad takes a selfie!
And that was the end of the quad. A majestic flight turned horrific with a single $2 part failing. Today, the quad spends most its time in a pile on my desk.
But I will not forget the experiences it gave me in its short life. Let us remember the quad as it was, in its prime. Taking beautiful photos at a perspective I would otherwise never have seen.
Godspeed quad, may your parts be salvageable for my next build (with redundant motors).
In memory of Quadcopter v1.0 2013-2013
I started building a quad on a Hobbyking SK450 around Christmas last year. Initially I wanted to make a simple, cheap quad to learn to fly on. I built it with all HK parts with motors being the exception. I've learned through others that cheap, wobbly motors cause most issues with these quads. So I sprung for some CarbonBird motors from MultiwiiCopter. I slowly built it over six months or so and used a cheapo HK KKBoard clone as the flight controller.
After some software tweaking she finally flew. It was not the easiest thing to fly as almost all of my experience came from fixed wing. It made me reluctant to fly it, especially since this is my most expensive RC model. Around this time I found the Syma X1 which was the perfect trainer for me to learn on and the big quad got put on the shelf.
Between my X1 practice sessions I started helping a friend work on his Ardupilot controlled Bixler. After the maiden I knew what I wanted to do with my quad.
I decided to go with the HK Ardupilot 2.5 clone since I knew anything on a quad is not long for this world. I added a HK UBLOX GPS, HK telemetry module, HK video transmitter downlink, and eBay 808 v2 720p camera. All powered up with the video transmitter on board.
The command and control Mission Planner software with all systems running. (No GPS link since I was indoors.)
I wish I could have caught the maiden of this beauty but the microSD card ejected itself mid-flight and was never seen again. It seems MissionPlanner defaulted the flight speed to 100mph. So that first flight was kind of... intense.
The second flight went well, I hover-held over my parent's house. Got some decent shots of the Patuxent River on a gloomy, overcast day.
We had a freak warm day on Halloween this year. Knowing this would probably be the last nice day before winter, I decided to give waypoint navigation another try. I tweaked some settings and went to Saint Mary's College of Maryland (SMCM) since it's the largest publicly available field I know of. The quad flew beautifully! It navigated waypoints smoothly and held point even with the light gusts of wind. The video is worth a watch.
If you watched the video, you're probably wondering what happening. I was wondering the same thing as I numbly gathered pieces not even expecting the camera to still be filming. The last frame is my surprised face that the camera was working (its case was split apart) and then excitement that maybe the cause of the crash could be revealed.
After some "video analysis" (frame-by-frame in VLC) I found some really spectacular stills. Especially in those moments of flashes on impact. But first, I present a UFO right at the beginning of the tumble. I have no idea what it is. All wiring was accounted for and attached, so that isn't it. Maybe a bug?
Next we see what caused the unfortunate accident.
Yup, that's one of the four very important propellers branching off to try flight on its own. I assume the cause was the prop adapter loosened itself during the jerky corrections when fighting the wind 50 meters up. The trailing edge of the prop had a chip out of it. Only the leading edge should chip if it was spinning in its rightful place. The prop likely got nicked by another prop before fluttering away.
With that closure I can begin my grieving. I got some nice orbits before it hit, so that helps a little. Also, the destruction is interesting to watch. Keep in mind this is frame-by-frame at 30fps. This happened really, really quickly.
You can see the moment of impact and first bounce. The camera takes a slightly jigglyer image than usual and you can see it abandoning ship in the next image. Now for my favorite part, the quad takes a selfie!
And that was the end of the quad. A majestic flight turned horrific with a single $2 part failing. Today, the quad spends most its time in a pile on my desk.
But I will not forget the experiences it gave me in its short life. Let us remember the quad as it was, in its prime. Taking beautiful photos at a perspective I would otherwise never have seen.
Godspeed quad, may your parts be salvageable for my next build (with redundant motors).
In memory of Quadcopter v1.0 2013-2013
Wednesday, June 12, 2013
Syma X1 with FPV Camera
So while in Huntsville I came across a Syma X1 in a GigaParts store and had to impulse buy it. It didn't take long for my colleague and I to attach a HobbyKing 720p camera to the top of it.
The maiden flight...
Plus I got to test the durability of the camera and the quad...
I love this thing.
The maiden flight...
Plus I got to test the durability of the camera and the quad...
I love this thing.
Tuesday, January 29, 2013
Spoof your iPhone firmware iOS 4.2.6 as iOS 4.3
I am sure I can't be the only one. I currently have an iPhone 4 (Verizon) updated to the last iOS4 version that is jailbreakable, 4.2.6. I really like this iOS version and my iPhone 4. I thought I was set for years. I could stand up against the onslaught of tempting technology. Then Apple got tricky.
Before iOS 5, CDMA and GSM iPhones were on different firmwares for the slightly different phones. Towards the end of iOS 4, GSM got 4.3 and CDMA got 4.2.10. Greenpois0n didn't bother releasing a jailbreak for the last firmware since iOS 5 was on the horizon and deserved their full attention. The result: any iPhone owner who did not want iOS 5 (for many reasons) and wanted to stay jailbroken had to stay with the earlier iOS 4.2. This was fine with me. Until I started seeing apps on Apple's App Store requiring 4.3 or above.
At face value, this seems straight forward. iOS 4.3 must include some newer libraries required for these newer apps. Not quite. The only main addition in 4.3 was a patch for the 4.2 jailbreak exploit. This was the checkmate to jailbreakers. Either update and lose your jailbreak, keep your jailbreak and be prohibited from using newer apps, or suck it up and continue the cycle with iOS 5. Until now.
As it turns out, the reported iOS firmware is actually set in a plist file. Once you modify the file, you can spoof the version as 4.3. Your jailbreak will stick around and you can download and use all apps requiring iOS 4.3!
A quick note:
There are reports that some have yielded their iPhone unbootable by misnaming or screwing up the plist file. As always, back your phone up and make absolutely sure everything is correct before rebooting. You can always do a restore. I have done this many times using the method below on my CDMA Verizon iPhone. TLDR: I'm not responsible if you have to do a restore.
STEP 1
First, make sure you are running the latest RC6 greenpois0n jailbreak. There are many fixes included in RC6 that you definitely want. Especially if you use emulators. You might be rolling back to 4.2 from another firmware. I won't get into that here since there are guides everywhere out there. Just follow a tutorial until you have a working, jailbroken, iOS 4.2.
STEP 2
Install iFile from Cydia
STEP 3
Navigate to /System/Library/CoreServices in iFile
STEP 4
Make a copy of SystemVersion.plist (call it SystemVersion.plist.old)
STEP 5
Open the original SystemVersion.plist in "Text Viewer"
STEP 6
Change the version id string to 8F190 (mine was 8E200)
Change the version number string to 4.3 (mine was 4.2.6)
STEP 7
Double check to make sure your SystemVersion.plist is set correctly
STEP 8
Reboot! (Don't mind the crazy screens you get during reboot)
And you're done! Feel free to enjoy the App Store once again. If you ever need to rollback, such as re-jailbreaking, change SystemVersion.plist to something else and remove the .old from the original.
Before iOS 5, CDMA and GSM iPhones were on different firmwares for the slightly different phones. Towards the end of iOS 4, GSM got 4.3 and CDMA got 4.2.10. Greenpois0n didn't bother releasing a jailbreak for the last firmware since iOS 5 was on the horizon and deserved their full attention. The result: any iPhone owner who did not want iOS 5 (for many reasons) and wanted to stay jailbroken had to stay with the earlier iOS 4.2. This was fine with me. Until I started seeing apps on Apple's App Store requiring 4.3 or above.
At face value, this seems straight forward. iOS 4.3 must include some newer libraries required for these newer apps. Not quite. The only main addition in 4.3 was a patch for the 4.2 jailbreak exploit. This was the checkmate to jailbreakers. Either update and lose your jailbreak, keep your jailbreak and be prohibited from using newer apps, or suck it up and continue the cycle with iOS 5. Until now.
As it turns out, the reported iOS firmware is actually set in a plist file. Once you modify the file, you can spoof the version as 4.3. Your jailbreak will stick around and you can download and use all apps requiring iOS 4.3!
A quick note:
There are reports that some have yielded their iPhone unbootable by misnaming or screwing up the plist file. As always, back your phone up and make absolutely sure everything is correct before rebooting. You can always do a restore. I have done this many times using the method below on my CDMA Verizon iPhone. TLDR: I'm not responsible if you have to do a restore.
STEP 1
First, make sure you are running the latest RC6 greenpois0n jailbreak. There are many fixes included in RC6 that you definitely want. Especially if you use emulators. You might be rolling back to 4.2 from another firmware. I won't get into that here since there are guides everywhere out there. Just follow a tutorial until you have a working, jailbroken, iOS 4.2.
STEP 2
Install iFile from Cydia
STEP 3
Navigate to /System/Library/CoreServices in iFile
STEP 4
Make a copy of SystemVersion.plist (call it SystemVersion.plist.old)
STEP 5
Open the original SystemVersion.plist in "Text Viewer"
STEP 6
Change the version id string to 8F190 (mine was 8E200)
Change the version number string to 4.3 (mine was 4.2.6)
STEP 7
Double check to make sure your SystemVersion.plist is set correctly
STEP 8
Reboot! (Don't mind the crazy screens you get during reboot)
And you're done! Feel free to enjoy the App Store once again. If you ever need to rollback, such as re-jailbreaking, change SystemVersion.plist to something else and remove the .old from the original.
Subscribe to:
Posts (Atom)