Posts Tagged ‘technology’
The WordPress.com stats helper monkeys prepared a 2012 annual report for this blog.
Here’s an excerpt:
600 people reached the top of Mt. Everest in 2012. This blog got about 3,800 views in 2012. If every person who reached the top of Mt. Everest viewed this blog, it would have taken 6 years to get that many views.
Watch your ICS build step by step till you get it on your Orange Boston, Gsmart G1305, XT502, Apanda A60, Vibo A688, Excalibur, A1, A88, Z71, Blaze, Journey, F911, Spice Mi300
There is more to everything… and when the more stops, it is then that we look for alternatives.
I come back to write about a new link that I found, like the rest of us who own any of the device mentioned here (Orange Boston, Gsmart G1305, XT502, Apanda A60, Vibo A688, Excalibur, A1, A88, Z71, Blaze, Journey, F911, Spice Mi300), eagerly wait to see ICS on it. Most of the time we do lose hope to see ICS on our device ever and that is what I did… it never occured to me that ICS will not run on my device but then I am not good enough to build one for myself…
I just kept an eye open out there (especially CyanogenMod) to see if I can just pull something out… meanwhile I tried few other ROMs out there too… some try to bring Xperia and some goes to MIUI experience on it, some say ICS look and feel…. sorry to say, nothing did work for me, I was never satisfied with any of those.
If one does not lose hope then there is never a defeat… and here we are, an ICS in the making… fixing bit by bit… just to meet users like us. I got this and thought it is a valuable resource to those who come to my page for help… below is the link for you to track what you will be getting for your device…
Do comment with feedback, any ROM you tried and any issues you face… communities are meant to share and have fun
ClockworkMod Recovery 5.X.X.X for Orange Boston, Gsmart G1305, XT502, Apanda A60, Vibo A688, Excalibur, A1, A88, Z71, Blaze, Journey, F911
Hi There… Hope you guys are doing great 🙂
I believe now that CyanogenMod is not active on new builds for our devices you must have started surfing out the net for custom roms that offers you new features or look and feel … I myself doing the same 😉
I came across this ROM OptimusXperia which said it ported from the XperiaArc and has TimeScape so thought I should try it out [though i moved back to my CM7 just in few minutes as the ROM was not anything that surprised me]…
What I write today is not on the custom ROM out there but the Recovery image that we are using, if you are active on the internet for Custom ROM you must have seen that now most of those demand latest recovery image and that for other devices is v5 and higher… if we go to Rom Manager and check for latest recovery image it still list v2.5 and thus limits us from trying new things…
I spent say a week trying to figure out how I can move to v5 recovery and did some failed attempts too :). Finally I made it and as obvious my success goes to this blog for more users to try themselves… this method works for all devices for their respective recoveries, be careful to choose compatible one…
Let me start with a warning… recovery is a very important part of customization… if this corrupts your device there is very weak chances that you will have your handset back… I say weak not impossible 🙂
Ok so for now to get the recovery as obvious you should have your handset rooted and Super User available… hope by now every android user has rooted their devices… if not … you are missing the fun 🙂
This is quite an easy process…
1. Copy the Recovery image to your SD card root folder… [root folder means write on the SD card not in any folder you created]… image can be found here http://www.mediafire.com/?qj763f940glkw4p
2. Rename the recovery image if not already named as recovery.img… [it is already named recovery.img, this is when you are trying any other recovery image with other name… and yes you can rename it before moving to SD… also the naming is just to simplify our next steps, you can use it as it is]
3. I am not sure if this is needed, if you fail to apply the image, enable the USB Debugging under development settings… this is optional, it works without enabling too
4. Launch the Terminal application… normally this comes with every rooted rom and is also available in market… this is kind of command prompt for Linux systems
5. Now under the Terminal which will be on $ prompt… write “su” without the quotes and hit enter on the keys…
6. It will launch the Super User to grant admin permissions to the Terminal… make sure your Super User is not protected by some app locker application… you should see the super user popping up and prompting you to click Allow or Deny… say allow
7. Now the Terminal is running as an admin… this means it can do a pretty good damage to your device if you try to upset it 🙂
8. Now type the command as it is flash_image recovery /sdcard/recovery.img , make sure the spaces are as same here… and hit Enter again
9. You will see the terminal reading the memory segments it is over-writing and once it finishes it will be at the $ or # prompt again
10. Exit from the Terminal and reboot your device to Recovery…
Done… now you see the recovery reads the version as 5.X.X.X…
Be careful of what you do here… and the responsibility lies all with you… 🙂