An Improbable Journey
A few weeks back I received an invite from Maaz for a winter expedition to climb Makra Peak. We had planned similar expeditions before, only to have them canceled at the last minute for one reason or another. So, despite already having an extremely busy schedule, I accepted the invite with a thought that it likely wasn’t going to happen anyway.
As the date of departure grew closer, I started to suspect that this time, it might be for real. It was mostly gladdening since the proverbial call of the mountains had turned into a deafening roar after being away from them for over half a year. However, some panic also set in as I lacked the right gear for a winter climb. Physically, I hadn’t prepared at all and was lacking in stamina and endurance. Both are prerequisites for carrying up essentials; camera gear, food, clothing and one’s own body weight; through ice and snow. Tempted to back out, when the day arrived, I decided to wing it and see how far I can push myself.
Makra Peak at Dusk
The night we were to leave, Islamabad was being sealed off in preparation for the March 23 Pakistan Day parade. I was to join the team at the bus terminal at 3am and go onwards from there. My father was to drop me there and although we left home well in time, soon we were stuck in the middle of hundreds of trucks that were denied entry into the capital. It took some coordination with the traffic police and the truck drivers to get out of there and we made it just in time.
The Trek to Paye
The bus ride to Abbottabad allowed much needed nap time. Then we took a shuttle van to Mansehra and from there, a mini-van to Kiwai where Maaz’s local friends were ready with a jeep and awaiting our arrival. These amazing people drove us up to the hill resort of Shogran, did most of the heavy lifting and most importantly, led the way through the snow. Walking through even a light layer of untouched snow is exhausting work. These people carved a path through snow that was at least a few meters deep and allowed the rest of the team to follow without extra effort.
Shogran is a hill-top village 2,362 meters (7,749 feet) above sea level. From there, a few kilometers of slight incline takes one to Siri lake (2,590m/8,500ft) and then a steep ascent leads to Paye lake and meadows (2,895m,9,500ft). Makra Peak rises above the surroundings, standing at 4,000 metres (13,123 feet) above sea level. At this time of the year, everything above Shogran freezes over. Lakes and streams disappear under layers of ice and snow. Plants and rocks get completely buried and only the tallest trees manage to stand out.
Our plan was to reach Paye on the first day, spend the night there and attempt Makra Peak the next day. The first day’s plan was already quite ambitious. Another team had arrived in Shogran before us and aimed to reach Siri by nightfall. However, realizing how treacherous the snow was, they conveniently stayed put and allowed us to go ahead first.
We were into deep snow soon after leaving Shogran. Although the path through the forest isn’t very steep here, it was still exhausting work. We reached Siri at about two o’clock in the afternoon. Quite a feat, given the experience and stamina level of some of the team members. For Saad, it was the first time climbing a mountain, let alone a snow-clad one. The steep trek to Paye lasted over three hours and took every ounce of our remaining strength, but we made it before sundown.
Crossing Siri on the way to Payee
Most people picture Paye as rolling green meadows. Our efforts were rewarded with a stunningly beautiful frozen landscape. Even the wooden huts we were to stay in had almost completely disappeared under the ice. This was soon remedied by digging through the ice and creating a channel to the wooden door.
Once inside, we lit a fire in an attempt to warm up and dry our completely soaked boots and clothing. It didn’t help much, but the fire was a good psychological boost. The pink glow of the setting sun over the surrounding landscape was worth capturing, but at this point, not even the lure of amazing photos could move us and we set about preparing for the cold night ahead. Sleep came almost instantly.
The fire must have died out sometime before midnight or someone may have put it out earlier. The sheer cold woke me in the middle of the night and I must have spent hours trying to stay warm in my light sleeping bag. Though quite tempted, I simply didn’t have the energy to get up, get out and shoot the amazing sky above.
Finally, I realized that at least a few others were also suffering the same discomfort and that it was almost dawn. Hasan and I plucked up the courage to go out and managed to take a few good photos. By this time, the Milky Way was barely visible due to the rising sun’s glow, but the rest of the landscape was worth the effort. The snow had also frozen solid, allowing an excellent grip on the surface.
Push to Makra Peak
It was time to prepare for the final climb. Here, I made two critical mistakes. Firstly, I missed out on breakfast while I was out with my camera. Secondly, I decided not to carry extra water. Six of us set out while the other three decided to stay behind at the camp.
We had two paths to reach the top of the peak. One was a direct ascent over the foothills, which meant climbing up and down three hills before the final ascent. The other was a shorter, but more treacherous path through the adjacent valley. We chose the latter.
Maaz, Babar, Shams and Arif on the way to the top
Hassan had trouble getting a foothold on the hard ice and had to turn back before we entered the valley. Maaz, Shams, Babar, Arif and I went ahead, traversing the steep wall of the valley. Although the valley didn’t look very deep, a small slip here would have been fatal. The rocks and trees below would have dealt a severe blow to anyone tumbling down. The rising sun was now causing the ice to melt and made the move more exhausting.
We reached a point where an overhanging rock made it dangerous to continue or climb above it. It was time to climb down the steep slope. The others did this facing outwards, though I found it easier to face the ice and climb down as if it was a ladder. It worked pretty well.
Halfway down, the valley wall was free from trees or rocks and we decided to slide the rest of the way. This brought us to the valley floor which was mostly still in the shadows and frozen. After a short break, we continued onwards and could see Makra Peak ahead of us.
The solid ground made it easier to walk over it and the frozen channel was an amazing sight. However, by this time, I was suffering from severe dehydration. Realizing that nobody had brought water and there was only a single bottle of orange flavored drink for the whole group, I made a hasty decision. I decided to head back to camp and return with my invaluable water pouch. It would not only resuscitate me, but also act as a backup for the rest.
Despite my insistence to go alone, the rest of the team asked Arif to accompany me. The move back was gradual, but both of us made it without much trouble. We also met one of the guides from the other team here. His team had chosen the longer route over the hills, but he separated from them to try out our path instead. Smart choice.
Valley path to Makra Peak
There was little liquid water back at the camp, but I ate a few dates, put a few gulps of what water was available in the pouch and headed out. In the back of my mind, I knew I had missed the opportunity and the resulting emotions blurred my thought a little. However, Arif and Hassaan advised me to rethink things. In all my travels, I have rarely backed away from a challenge, pushing myself to the limits. When I have had to stop, it is usually due to time constraints. This time, I gave in and let cooler heads prevail. The next few hours were spent chatting with the team and following the barely visible dots moving up the mountain.
As mentioned earlier, all that the team had for sustenance was a bottle of orange drink, plus a few dates. At one point, even these became too cumbersome for them to carry and they left these behind for the return journey, along with other equipment. Unfortunately for them, the other team thought it was a gift for them and helped themselves to it.
The team reached the summit at about noon and were back to the camp by 3:30pm. Must have set a record for doing this in such a short time and at this time of the year.
We all had hot soup, some instant food and a hot cup of coffee. The rest of the day was spent relaxing (as well as answering the vital call of nature) until the warm sun disappeared behind the mountains and the cold winds took over. I stayed out shooting, until the pink afterglow of sunset disappeared from the landscape.
We had a few boiled potatoes for dinner and once the rest had hit the bed, Hassan and I went out to capture a few Milky Way shots. The stars were even more impressive than the last time I was here. However, due to the biting cold and threat of predators, we couldn’t spend a lot of time here. Back in the hut, everyone had fallen asleep. Although I wore extra clothes this time, the cold was worse and we endured another sleepless night.
We broke camp early the next morning and after a few group shots, headed back down. The steep slopes that were a challenge on the way up were instruments of fun on the way down. We had no trouble sliding down these in a fraction of the time it took to climb them.
Team Makra Peak, 2015 Winter Expedition
The pace slowed a little by the time we reached the forest, but our feet had grown accustomed to the snow and ice. So much so that we managed to keep pace with the locals and reached Shogran in a mere two and a half hours of leaving Paye.
After a meal and more group photos, we bid farewell to Arif, Shoaib and Shams. Babar drove us back down to Kiwai and we took another mini-van to Mansehra.
Babar, Shams, Arif and Shoaib, the local porters from Kiwai
A tragic event near Balakot marred our feelings of joy and euphoria. A vehicle had slid off the road and fallen straight down into the River Kunhar. A number of rescue vehicles had arrived, but with such a sheer drop, there wasn’t any chance of survivors. Standing right at the edge, we couldn’t even see it. We probably will never know the fate of those that fell.
Upon reaching Mansehra, we discovered that the buses would not be running for several hours. Instead, we took a local van to Rawalpindi. I reached home by dusk while the others headed back to Lahore.
And so ended an epic adventure, the first successful climb of Makra Peak this season. It left us more confident, refreshed and better prepared for the next challenge.
The Lal Suhanra National Park is located near the city of Bahawalpur and offers a chance to see some amazing wildlife, up close. The park is home to a pair of Indian rhinoceros (greater one-horned rhinoceros) that were given by Nepal in 1983. The couple has yet to produce an offspring.
The Indian rhinoceros differs in many ways from other major rhino species, such as the Black rhino or the more common White rhino. For one, while most other species are two-horned, it has a single horn. Also, its skin folds down into an armor-like cover with distinct bumps across the legs and shoulders.
Seeing the rhino up close was quite an experience. Its characteristic horn, ears and thick hide made me think of a triceratops and what it must have looked like all those millions of years ago.
The Indian rhino is a vulnerable species. Once spread across south asia, it is now found in small pockets and in captivity. We have already lost the West African Black Rhino which was declared extinct in 2011. I hope conservation efforts pay off and we manage to preserve remaining species such as this.
Last weekend we had planned to camp at the hilltop lake and meadow known as Paye (the second and more impressive part of the Siri Paaye area). Located in the Kaghan Valley, Siri Pae lies above the hilltop resort of Shogran and under the shadow of Makra Peak (about 3,600 meters/12,000 feet above sea level).
Shot at 16mm, 30 seconds, f/3.5, ISO 3200
My biggest motivation for this trip was being able to shoot the Milky Way which isn’t normally possible from urban areas. Here are some things I did to get my shots:
One of the main requirements for Milky Way photography is being far away from artificial lighting of any kind. City lights, as well as light from small towns and villages, cause all but the brightest stars to be invisible, both to the naked eye, as well as to the camera sensor. Air pollution also reduces visibility so being up on a mountain, in the middle of nowhere, is almost a must. This is the reason observatories are built in such places.
Weather reports had said there would be clear skies. However, I had neglected to check where the moon would be. Though not a full moon, it was enough to ruin my plans. Moonlight is good for general night photography, but makes milky way photography almost impossible due to it “drowning out” the light from other heavenly bodies. Luckily, I had installed the Solar and Moon Calculator Android app some time back and it told me the exact time the moon would eventually set (somewhere past midnight).
After trying out a few moonlit shots once the sun had set, I took a nap and woke up again around 2am. It was pretty cold at this altitude, my friends were all asleep and there were strange howling sounds coming up from the valley next to our tents, but the view really was impressive, even to the naked eye. I had never seen the Milky Way this clear before. The campfire had gone out, but I was glad it did. Else, any stray light from it could have ruined my shots. In some cases, the reflected campfire light off of trees and other structures could add an interesting effect, but I didn’t want to risk it here.
Shot at 17mm, 30 seconds, f/2.8, ISO 800
It really was good timing since within a couple of hours, a light cloud cover started to roll in and blot out the milky way. The clouds also dashed my chances of getting some long exposure, star trail photos.
So I got my gear ready, dialed in the basic settings that I had memorized and took a shot. Amazingly, they came up really good on the first try. There are some basic rules to follow when shooting the Milky Way. The most important one is to use the 600/focal length, or 500/focal length, rule to prevent stars turning into trails or ovals (I shot at 16mm, so 500/16 allowed me about 30 seconds of exposure). If you have good equipment, you can also try 450/focal length to get even better results.
A limited exposure time also means that you’ll need to have a wide aperture and shoot at a high ISO to get a good exposure. This is where my investment in the Canon EF 16-35mm f/2.8 II USM lens and the Canon EOS 5D Mark III paid off. The 16-35mm is just 1mm wider than the much cheaper 17-40mm and they are both excellent lenses. However, the f/2.8 aperture really came in handy as opposed to the 17-40mm’s f/4. And the 5D Mark III’s ultra low noise at high ISOs made it perfect for the job.
Unless you have a lens with an aspherical element (like the 16-35mm) you may experience coma or comatic aberration in the stars. That’s another thing to consider when selecting a lens for this.
Off course, a tripod is a must since you’re shooting with several seconds of exposure. I have a cheap ball head tripod from some Asian company that can’t really replace a branded one such as Manfrotto, Gitzo or Benro. However, it is really stable and surprisingly light. Weight is important since as in my case, you may have to drag it up a few thousand feet along with the rest of your gear.
Other things I did included stabilizing the tripod by attaching some weight to the hook at the end, using a remote release (intervalometer) and covering up the eyepiece with the provided rubber. This last step ensures that no stray light from your torch entering the viewfinder ruins the shot.
Shot at 16mm, 30 seconds, f/2.8, ISO 800
I took several shots, some at f/2.8, others stopped down to f/3.5 just to see the difference, though there wasn’t much in the final shots and I suggest just shooting at f/2.8 (or whatever maximum you can achieve). I also had Long Exposure Noise Reduction (LENR) turned on to reduce noise buildup.
I keep the white balance set to “Cloudy” for most shots, though star light is usually around the same temperature as the sun so it was later changed to “Sunny”. A custom white balance can be a pain (especially for Canon users), though if your camera supports shooting in RAW format, the white balance and other parameters can be fine-tuned later on.
First of all, auto focus is pretty much useless here. Unless you and your camera can find a really bright star or another high contrast object that is visible in the tiny viewfinder, the camera will keep trying to auto focus without success. So manual focus is a must here.
Ever since I discovered live view focusing, my shots have been a lot better focused and sharper. For astrophotography however, it may be too dark to see much on the screen. You can either focus using the focus scale set to around “infinity” or try to locate a bright star on the LCD, zoom in and turn the focus ring until you get a clear, sharp dot.
Failing that, the only option left is the tedious trial and error method. That is, take a shot, slightly change focus, take another shot and compare it to the last one. Repeat until you have sharp exposure.
Though it couldn’t be used for focusing, the viewfinder was very useful for composing the shot. So best thing to do would be to use live view to focus and then look through the eyepiece to compose and frame the shot.
Shooting the Milky Way alone doesn’t seem very exciting. Adding an object in the foreground gives it some depth and perspective. This is why I included a silhouette of a tree in most shots. Light painting the foreground objects is also a nice way to bring out the shots. Unfortunately, I only had a small LED flashlight which wasn’t very powerful and gave a much whiter effect, compared to the Milky Way’s warmer tone.
I’m not much for very fancy post-production or “Photoshopping”. However, you will need to adjust the white balance, exposure and contrast a little to bring out the details. You may also need to use a noise reduction software/plugin, depending on how good your camera handles high ISO noise.
I can’t wait to get another shot at this and try to improve on what I achieved from this trip. There isn’t much I would change, but I would be better prepared for any light painting. Maybe with a more powerful flash lights with varying degrees of temperature. Would also light to get some good star trail pics. Till next time.
Canon EF 16-35mm f/2.8L II USM
If I was asked to pick my favorite type of photography, or range of focal lengths to be precise, I would have to go for the ultra-wide end. The sense of grandeur and surrealism that an ultra-wide lens captures, just isn’t possible at higher focal lengths. Whether it’s mountains, grand buildings or confined spaces, an ultra-wide really delivers.
For my previous camera, the Canon EOS 500D (Rebel T1i), the decision was quite simple. After much reading and contemplation, I found the Tokina 11-16mm f2.8 to be the most suitable for my needs. The narrow focal range and fixed maximum aperture of f/2.8 mean it is equal to a high quality prime. If you can find one, that is.
Since it wasn’t available here in Islamabad and at the time, I had no way of getting it from elsewhere, I settled for the equally great Canon EF-S 10-22mm USM. The only disadvantage was the smaller, f/3.5-4.5 variable aperture. The optics are great and I loved it. One of my favorite shots from this lens is the Salt Stalagmite one.
After moving to full frame, things got more complicated. The EF-S 10-22mm isn’t compatible with non-APS-C sensors and there isn’t one, really inexpensive or really great option. Some friends and online guides suggested I hack it into a 16-20mm, full-frame compatible lens.
Canon EF-S 10-22mm f/3.5-4.5 USM
The hack involves cutting/filing down the EF-S mount into an EF one and forcibly restricting the lens’s focal range so the end closer to the sensor doesn’t hit the SLR’s mirror. However, I didn’t want to risk damaging such an amazing and under-appreciated piece of glass (nor my even dearer camera) so it is still intact, and still up for sale.
It took a couple weeks of searching and reading to settle on the Canon EF 15mm f/2.8 Fisheye. Yes, it’s a fisheye lens, but firstly, it is a very sharp, prime lens. Secondly, the fisheye effect can be removed through photo editors to create a still sharp, super-ultra-wide, 12mm rectilinear image.
Unfortunately, most shops list this as a discontinued lens and a new piece is notoriously difficult to find. It definitely wasn’t available anywhere in Pakistan and I ended up asking a friend to get a used one on his way back from the States. The order was placed, but a well-timed snowstorm delayed the delivery and it got left behind. Even sent via courier, it couldn’t have made it into my hands in time for my upcoming Uzbekistan trip.
Canon EF 15mm f/2.8 Fisheye
I had anticipated such a delay and even before I got the bad news, I had started looking for an alternative. The Canon EF 17-40mm f/4L is a great lens for landscapes and it’s priced very nicely, but the f/4 part bothered me a bit. Although larger/fast apertures aren’t usually required for ultrawide shots, I’m the type of person who’d curse myself whenever I did need it.
Tokina 11-16mm f/2.8
Best option optically was the manual focus, all-metal Zeiss 15mm f/2.8 ZE. It’s a prime (I love primes), it’s fast, has very low distortion and is really durable. However, at around $3,000, it’s reserved for those with very deep pockets and is probably impossible to find in Pakistan.
I also considered the Canon EF 14mm f/2.8L II USM, but the reviews weren’t very impressive. At least not impressive enough to justify the price tag. In the end, I went ahead and ordered Canon’s top of the line UW zoom (and also the goto lens for photo journalists). The Canon EF 16-35mm f/2.8L II USM.
At first glance, it looked a little… well, little. It’s lighter and smaller than the 24-105mm I have been using with the 5D Mark III. However, both the zoom and focus rings are a pleasure to use. Really easy and smooth to turn and unlike the 24-105mm’s sudden jump from 24mm to 35mm, the zoom range is nicely divided.
I have yet to use it for the intended purpose of travel shots and some astrophotography, but over the weekend, I did cover a protest with it. And it wasn’t long before I realized the advantage of having a f/2.8 aperture. The large aperture makes capturing important moments a breeze, even in low light and without bumping up the ISO. It also brightens up the viewfinder for composing those low-light shots.
It’s easily my favorite lens at the moment and I don’t have any complaints about it. One speed bump you may run into is the 82mm filter size. Filters that large are not easily available and are significantly costlier than smaller sizes when you do find them.
So far, I have not found any 82mm UV filter in the Islamabad shops. Such a filter is a must to complete the weather seal of the lens (oh yes, this lens is weather sealed). However, I did manage to get a B+W Variable ND (neutral density) filter. It seems large and I expected quite a lot of vignetting in shots taken at 16mm, but there just wasn’t any. It should come in pretty handy for shots requiring very long exposures.
Well, enough with the long rant. Hoping to post some interesting pics from this lens soon. Stay tuned.
Life has been filled with so many things that I just haven’t had the time to blog here.
Haven’t had time to do a lot of photography either, but there are a number of pics I want to post here. Will do it soon hopefully.
Besides that, have moved to a nice office in Islamabad, created a super-fast, optimized WordPress setup and hoping to find some good people to work with soon.
Oh, and going to be traveling to at least one beautiful place this summer. Should capture some awesome photos.
Till next time.
Swype doesn’t quite work with Gingerbread (Android 2.3.2) on Galaxy S GT-I9000 due to a small, silly bug. If you attempt to select Swype as the input method, it gives the following error:
The Swype package you installed is configured for another device and will operate with limited functionality. Please contact Swype about this issue.
After much searching, I finally found a fix by Rawat, available here. In the device’s build.prop file, you’ll need to change this line:
to this line:
Here’s how to do this:
- rooted device (I used the fix given here)
- adb (can be installed from here)
- USB cable
These are the steps I followed to make it work (it’s simpler than it looks):
- Connect the device to your system via USB. Make sure USB debugging is on
- Copy /system/build.prop to your local system (I copied it in /tmp, using adb):
adb pull /system/build.prop /tmp/
- Open the file in a good text editor (use one that doesn’t mess up the newlines, like vim). Search for
ro.product.board=GT-I9000 and replace it with
- Copy build.prop to sdcard:
adb push /tmp/rom/build.prop /sdcard/
- Now you need to be able to write to the /system partition. Using adb shell, type su. At the # prompt, type:
mount -o remount,rw /dev/block/stl9 /system
- If there weren’t any errors, copy the updated build.prop file to /system:
dd if=/sdcard/build.prop of=/system/build.prop
- Reboot device:
That should keep you Swyping until they issue an official fix. Hopefully, it is already fixed in Android 2.3.3.
My Samsung Galaxy S is doing relatively well. I’ve found some amazing apps for it and it is both productive and fun, though it is probably in for another update. Like I said, I wasn’t planning on doing anything funky with it at first, but Sohaib convinced me to work on it to get the most out of it.
The first thing I was advised to do was to update the phone to a newer version of Google’s Android mobile operating system. Sounded simple enough, but as I later discovered, it was a little confusing and tricky. Especially since I wasn’t using a Windows system to do this. It can be a pain, even on a MacOS laptop/PC.
There is a chance that you might end up bricking your shiny new phone so just to give you an idea of what you might be getting into, read this forum thread first. The worst case scenario is where your phone fails to even turn on. Even in that case, there is a way to reset it using a custom connector which you can purchase or make yourself.
You should also familiarize yourself with the XDA Developers forum. It has lots of useful information on everything Android.
With that out of the way, here are the details of what I did and how you can flash your Galaxy S:
(Note: These methods were tested and worked on Ubuntu Maverick 10.10 and Ubuntu Lucid 10.04. They may differ slightly for other Linux systems)
1. Get the Android SDK Platform Tools
There is a chance you might not need this package, but most probably, you do. Even if you don’t, the tools within are very useful to have around.
Download the SDK from here. The Linux package contains a folder by the name of android-sdk-linux_x86. Go into this folder and run the SDK Manager, like this:
Now from the “Available Packages” menu, install the Android Platform Tools. This contains adb, a small utility you can use to control a number of low-level functions on your Android phone.
If the above step works ok, you should have adb installed in the platform-tools folder under android-sdk-linux_x86. Add it to your path to avoid having to re-type the full path every time.
2. Get Heimdall
Heimdall is an awesome piece of open source software that allows you to flash ROMs or firmware onto your Galaxy S smart phone. Some say it’s a lot better than Samsung’s own software or the one most Windows users use, Odin. Get Heimdall here:
I’d suggest getting both the graphical tool, as well as the command line (if you’re comfortable with it). I got the latest version (1.1.1, at the time of this writing).
3. Get Download Mode working
I must have spent hours trying to figure out why I couldn’t get my phone to go into Download Mode, a state where the phone isn’t running anything else and is ready to accept updates.
You normally do this by holding down the Volume Down, Home and Power buttons. Flashing your device without this is a little risky, but no matter what I tried, it didn’t work. Seemed that my phone wasn’t configured for the 3-button Download Mode and I had to install a fix to get it to work.
More details can be found here, but I got it to work like this:
Download RAZ_P-SBL_SGS.tar and run this:
tar xf RAZ_P-SBL_SGS.tar
(this will extract the files boot.bin and Sbl.bin to the current directory)
Use adb to reboot the phone into download mode:
./platform-tools/adb reboot download
You should see the phone reboot and the appearance of the distinct “android at work” logo, like the one in the above photo.
Now, you can use Heimdall to update the boot loaders:
heimdall flash --primary-boot boot.bin --secondary-boot Sbl.bin
This should take a couple seconds, but once done, you’ll be able to go into Download Mode using the 3-buttons (Vol Down + Home + Power).
4. Decide on the version and type of Android ROM
Once that step is complete, you can move onto flashing the ROM/firmware of your choice. It seems that there are various types of ROMs availabe. Leaked ROMs, official ROMs, custom ROMs etc.
If you’re like me, you can go with an official or Stock ROM. This XDA thread has a whole list of stock firmwares for the i9000.
However, you may want to look around and pick a custom ROM that suits you. There are ROMs which are greatly trimmed down to the essentials so you get a bare-bones phone on top of which you can install what you like. Or you can get a feature-rich one. Here is a site with a good collection of custom firmwares.
5. Prepare the necessary files
In any case, pick one and download it. These are often packaged as self-extracting Windows executables. I thought this may be a hurdle on Linux, but running the exe file with wine extracted the files just fine.
I got the I9000XWJS7.exe file (Android version 2.3.2, codename Gingerbread) and simply running
wine I9000XWJS7.exe extracted it into it’s own folder. Inside, there were these three files:
These are standard tar files and you can extract them using the tar command:
for a in CSC_XEE_JS1.tar.md5 PDA_JS7.tar.md5 PHONE_JPY.tar.md5;do tar xf $a;done
Search and download the appropriate .pit file for your phone. I needed the 512 version which can be downloaded here.
Now you should have the following files (depending on the ROM you downloaded):
6. Start the flash
--repartition flag will destroy any data you might have on your phone. Save it to your PC or to your SD card if it is worth saving, or run this command without the “–repartition” and “–pit ….” flags.
heimdall flash --repartition --pit s1_odin_20100512.pit --factoryfs factoryfs.rfs --cache cache.rfs --dbdata dbdata.rfs --param param.lfs --kernel zImage --modem modem.bin
Once this command completes, the phone should automatically boot into the new system. That should be all and you should have an updated mobile. I updated my phone from Android 2.1 to Android 2.3.2 and it felt more colorful, a little faster and even the battery life had improved.
I am however having some issues with the phone. It sometimes shuts down or reboots after a long call and running a few different apps together also causes it to hang, slow down or power off. There is an Android 2.3.3 update available which will probably help with these, but I’ll save that for some other day.
I have often argued that the root cause of the problems we are facing in Pakistan is the lack of education. Without proper education, we are unable to elect competent leaders or make any rational decisions as a nation. If almost half of our population is unable to read and write a single word, extremism easily flourishes and there is no way we can have a stable and performing economy.
This already desperate situation was dealt another blow this week after the government announced its plans to dissolve the HEC or Higher Education Commission. This federal body was one of the best performing organizations in the country (until its funding was drastically slashed) and oversaw some of Pakistan’s universities rise to worldwide prominence.
It’s hard to imagine what logical reasoning could have driven our glorious leaders to take such a catastrophic step. It makes no sense to hand over such a critical role to the corrupt and incompetent provinces. On this issue, I’d have to agree with the conspiracy theorists and also add a few theories of my own.
The HEC takes a strong stand against fake degrees and has had an exceptionally clean record. Once disbanded, our dirty politicians, many of whom hold fake degrees, would be completely free to run amock. Most likely, this was the main motivation behind the move.
It could also be a conspiracy to ensure that our future will remain in the hands of the corrupt few while most of our populations remains illiterate and powerless. How medieval is that?
Here is a message from Dr. Atta-ur-Rahman, one of the most respected men in the country and the man who can be credited with jump-starting the IT and Telecom sector in Pakistan. He had been heading the HEC during its best performing years.
A demonstration in protest of the dissolution of HEC is being held tomorrow (Tuesday, April 5th). You can join in through the Facebook event Defending HEC.
I’m writing this from my new Samsung Galaxy S, my first ever Android phone. I was considering buying the Tab instead, but lots of bad reviews put me off it (size is not much of an issue, especially if you use it with a Bluetooth device).
It took a lot of sweat and tears, but I now have it pretty much the way I want it. Wasn’t planning on getting into the nitty gritty this time, but ended up hacking it to pieces.
More on the surgery i did later.
I’ve been a big supporter of Linux for a while, but now that I’m getting more involved with photography, it’s starting to become a hindrance. No doubt there are countess tools available to get the best out of any photos, but the learning curve for most is pretty steep and they usually don’t compare well to their Windows counterparts.
Though GIMP takes care of most of my needs, it can be time-consuming and lacks built-in support for such essential things as RAW images and HDR. For the former, I use the dcraw plugin which does the job, but isn’t very powerful.
There are numerous resources for HDR on Linux, but I’m mostly quite disappointed. My favorite is Enfuse which doesn’t produce the greatest of results, but can be installed via Ubuntu’s repository and is really easy to use with the default settings.
Another great tool that I’m using quite often now is jpegoptim which helps optimize the size of any JPEG images I publish to the web to about 30% of the originals (with some compromise in quality, off course) and can be used for batch processing.
So now I want to take things to the next level (build a proper gallery, shoot and publish more photos, etc.) and it seems like the right time to switch to something more appropriate. Waiting for my new Mac. Let’s hope I get it soon.
My Betterphoto profile has a few pics. So does Flickr, though am building a portfolio that I’ll post soon.