04 February, 2013

Rooting GT-I9103 on ICS Android 4.0.4

English: Android Market on Samsung Galaxy S.
English: Android Market on Samsung Galaxy S. (Photo credit: Wikipedia)
04-Feb-2013

Sometime back in December 2012, after my Samsung Galaxy R phone lapsed on its 1-year warranty, my phone just hanged. If I recall correctly, my 3-year old girl was playing with it, and when I found it, it was already off – kids usually drain out the battery – so I didn’t think that there was a problem at all.

When I tried to turn it on, to check if the battery is dead, it turned on, but it stayed at the Samsung logo – it was stuck there, even after waiting for a considerable amount of time (5 minutes, I would say, is already a long time if we are talking of a normal phone, whatever brand that may be). I did what would be normally done: took out the battery, waited a couple of seconds (although recommended is 15 seconds), then put it back in and pressed the power button on, and voila! Still the same: stuck at the logo.

By then I knew that something else happened. Something has gone wrong.

“That was a rooted phone,” I thought to myself... now what?

I tried to go back to rooting the phone and searching for the same kernel that I used before, which are still in my laptop, did it many times, not once, but many times, and every time, it is a failure.

I then went to search in the web for possible solutions, or at the least, a newer version of the kernel, each time typing the phone model GT-I9103 as the selective search string.

I found several, tried again, failed, tried again, failed... many times... until one came out nice and completed the whole process of installing a kernel.

When the phone was finally working (again), I checked everything, still intact, but I noticed that something else is different – and that was when I found out that the kernel that revived my phone was ICS, Android 4.0. The original OS was Gingerbread, Android 2.3. I said, “What a jump!”

I was almost very happy, except that when I checked through my phone, I found that the root privilege was gone! “Should be easy,” I said, so I went right away to rooting my “upgraded” device. Easier said than done, and no matter what I did, I can’t root my upgraded phone. And after trying out so many times, I gave up. I settled with having just “an upgraded, albeit un-rooted,” phone.

Of course, a lot of those apps that I installed before which required root access don’t work anymore, so while the phone was working, it was not as before, it was not as when I had it rooted, and I have the complete control over it. Blast it!

With unsettled mind over my un-rooted phone, I have inside of me a resolve to look out for other means, other ways, other newer releases, someday, somehow, something that will give me back root access to my phone.

Yesterday, that day came!

In my random search, I chanced upon a page that tells about installing CWMR version xxx.xxx, followed by many other articles. I checked on that one, looked through the procedure, and I found that it is very identical to what I have been referencing before, but just that the version of code it is using is newer (supposedly newer). Basically, I found page for the exact search string I used: “root GT-I9103 ICS”.

Having found that, there is also the article on installing CWMR on GT-I9103.

These 2 I tried, and at first shot, I hit the mark. I rooted the phone running on Ice Cream Sandwich OS. But wait, there is more.

My initial version of ICS is 4.0.2. When I was done with the rooting, and also installing the new version of CMWR, I found that the ICS version is 4.0.4. Wow!

What more could I ask for? After rooting my Galaxy R phone, I also got an upgraded version of ICS.

I’m back!

And here are the pages that I referenced in my latest rooting adventure:
How To Root Galaxy R I9103 on Android 4.0.4 ICS
How To Install CWM Recovery v6.0.1.5 Touch on I9103 Galaxy R

As for this page, beware, not that it doesn’t work, but it is not in English! Bummer! Good thing I backed up my phone and it was a very simple recovery method of restoring the phone.
How To Install Android 4.1.2 Jelly Bean on I9103 Galaxy R

Till then!
Enhanced by Zemanta

I rooted my GT-P3100 – EASILY!

English: samsung-galaxy-tab
English: samsung-galaxy-tab (Photo credit: Wikipedia)
04-Feb-2013

A week ago, I went to the telecom service provider that services one of my mobile phones (I don’t use more than one; this line is used by one of my daughters). Since it is already one year, I am now eligible for a re-contract, which, primarily, is geared towards having a new phone, while all other things remain the same.

As I found out, the plan had a change, some that used to be free are now chargeable, some limits reduced, etc., etc. Anyway, bottom line is, we got a new phone. And it was a Samsung Tab 2 7.0, paying just a minimum sum, since my plan is a bare essential one, not having data at all. Just the basic set: phone line, talk time, SMS. No internet.

With everybody in the house having a mobile phone, except the 3-year old, our youngest thought to herself, and declared, that the new phone is hers. Who would argue with that?

The phone was broken in, and it was used, charged, installed with apps, recharged, played with, until I can’t hold on any longer, then on Saturday, I stole it away from my daughter while she was busy watching TV, and she didn’t notice that the Tab was gone, and that she had something else to busy herself with.

I took the Tab in the room, and went to search for rooting procedures. Found one that is for beginners, and I said, “What the heck. I ain’t a beginner!” and looked for something more complicated. I did find out, and when I checked through, it was way too complicated, so I went back to the beginner’s method.

I followed the procedure, downloaded the files, and without batting an eyelash, went straight away to rooting the device. I used Odin before, and I used Odin now. I am not new to the procedure, so I did as I can remember, and i believe I did everything correctly, but it hanged!

Before I started with the rooting procedure, I plugged in Tab in, and it was recognized by my personal laptop. However, when I disconnected my Tab, and put it to download mode, plugged it back in, Odin, or rather my laptop, don’t see it anymore. I almost panicked!

At this point, I did about 2-3x cycle of unplugging and plugging back, but still my laptop couldn’t see the Tab. So no choice, I needed to open it so I can take out the battery and hopefully, start all over again.

Problem!

The Tab isn’t easy to open up. The back cover is quite seamlessly attached to the body, without any nick or opening that is designed for taking out the cover. So I searched the web, then I found one on YouTube, and it was easy, so easy. But when I tried it myself, I had to give up – it isn’t easy after all.

A Chinese would say “Luckily,” but I ain’t Chinese, but I’ll say it anyway, “Luckily...” my work laptop was at home, and it will always be home when I am home, for such is the purpose if being issued a laptop, to be able to support even at home, even from home. I would recall that the other phones were rooted using the work laptop, while some others were rooted using the home laptop.

I took the cables and plugged it in my work laptop, with Odin already open and waiting. Boom! It was recognized ASAP. So I just searched for the same rooting procedure, downloaded the files, and went right to root my Tab 2 phone, a Samsung GT-P3100 unit.

How do I describe what happened next? It was a breeze! And with the initial problem that I went through, it seems that the quick rooting of the Tab was unbelievable, so much so that I can’t believe it at first. I had to install all those apps that is applicable only to rooted devices, and without a single complaint from the apps, my doubt was gradually replaced by a confirmation – the Tab 2 phone has been rooted!

Below is the link on the Rooting Procedure for Beginners, well, there will be times that it pays to go down low, again. Like this time.

Root Galaxy Tab 2 7.0

Till then!
Enhanced by Zemanta

01 February, 2013

Azure hijacked my VS2010 Publish Web dialog window

Image representing Microsoft Azure as depicted...
Image via CrunchBase
01-Feb-2013

Around Wednesday of last week, I got to check on what could be new to me on the Web Development arena. I mean, I haven’t been keeping up lately with the latest releases, and so what could have been out in the world for some time, maybe a year or so already, will be new to me, since these would be my first time to encounter them.

I am reading on one book, Beginning ASP.NET 4.5 in C# and VB, and I saw that one thing I have been seeing, but keep on ignoring, is Azure – and it was mentioned in that book.

It took my curiosity by the hand, and I just found myself installing here and there.

That’s when my problem started... VS2010 Publish Web calls Azure dialog...

I was just happy finishing all of my installation, and since these are add-ons, or plug-ins, I couldn’t immediately “see” the effect of what I have just done.

When I went back to my codes using VS2010, opened up one web application, made some minor changes, and tried to publish it, lo and behold! The Publish Web Dialog Window is now an Azure dialog box, telling me to publish on Azure, and as I found out, the only way to make a publication is either by logging in with an existing account, or by creating a new one. What?!

I got these installed, by the way: Visual Studio 2010 Ultimate, used for some time already, Microsoft Visual Studio Express 2012 for Windows Desktop, recent but not so recent, and Microsoft Visual Studio Express 2012 for Web.

I am very sure that having installed the Express 2012 IDEs did not give me the problem, but I doubted that suddenly.

Troubleshooting

First thing I checked is my list of installed programs, and as I expected, and was happy enough to confirm my initial guess, is that “some” Azure programs kicked in, by design, since Azure is supposed to, I believe, be taking over some of Visual Studio’s dialog boxes and windows (Now is that right? Is my understanding right? Am I making any sense at all?) So what I did first is to uninstall these Azure programs, as selected by date of installation. I thought I was done, and things will be back to normal.
It didn’t – I still see the Azure dialog window when doing a Publish Web in VS2010.

Along with the bunch of Azure products installed in the past few days were some updates to VS2010, and even Windows itself. So I carefully checked on the list, and selected those that I think were add-ons, and uninstalled them as well.

Nope, that didn’t help; still got the problem when doing a Web Publish act.

As I needed to apply the changes I made, I have to make a choice by making a “synchronize” move, copying the modified code to the other PCs I use, and doing a web publish on these production machines. Thankfully, the change done was okay, and no untoward side effect was observed or reported.

Back to my problem: I thought that if I would uninstall VS2010, and do a reinstall, maybe that would do the trick. So that is what I did. Went through the time-consuming process of uninstalling Visual Studio 2010 Ultimate, and hey, it was fast, cause only 2 items were uninstalled. Maybe nothing was left after the previous uninstallation... think so?

I restarted my machine, and went right away to reinstalling the Visual Studio 2010 suite. When it was done, I clicked on the shortcut, applied the license key, and then called up the web application. I went straight to publishing the web – and lo and behold! I would like to pull out all my hairs!

Nah, I still have the problem!

I couldn’t believe that a week has come and gone, and I was trying to solve one small problem, but I couldn’t fix it. I was thinking, I was making this troubleshooting skill of mine an asset in my job applications, but here I am, doing one simple problem, and I’m going nowhere, getting nothing done. Just running around in circles, to say the least.

Then yesterday, out of desperation, I wondered whether taking out all of the Visual Studio programs would somehow be the solution to my problem.

Well, that wondering led to doing, and since I have to go home for some urgent errand (my 2nd daughter had a high fever while in school, so I had to leave work at noon and filed that as an urgent leave of absence), I brought along my laptop, and around past 3pm, when we got home, I opened my laptop to execute the complete uninstallation of *Visual Studio*.

That took some time, especially that I had to attend to some other things here and there, and we had to eat dinner, and I have to look after the youngest while my wife looked  after our sick child – time flew so swiftly and it was night all of a sudden without my knowing it... I should say, without my noticing it...

That was last night. And while I was uninstalling the Visual Studio suites from my laptop, I have another desktop PC back in the office that I am working on, and since the desktop PC is an older model, making it the slower unit, and a fresh install at that, I said, why not I make this somehow the control unit, and find out, to confirm, that it is the Azure products, and not the Visual Studio Express 2012 products, that gave me the problem? Anyway, it would be the same steps that I will take:

Install Visual Studio 2010
Install Visual Studio Express 2012 for Windows Desktop
Install Visual Studio Express 2012 for Web

The VS2010 should come first, followed by either the Web or Windows Desktop version.

So I worked on the 2 machines simultaneously, the desktop PC back in the office I’m doing remotely, while the laptop is with me at home.

True enough, installing Visual Studio 2010 first and foremost gave me back the original Publish Web dialog window. True for both desktop and laptop PCs.

I then installed Visual Studio Express 2012 for Windows Desktop. When it was done, I opened up VS2010, called up the web application, invoked Publish Web command, and I got the same dialog window.

Confirmed, it is not the VS Express 2012 for Windows Desktop that caused the problem.

As a last step, I proceeded to install Visual Studio Express 2012 for Web, and when it was done, I opened up VS2010, called up the web application, invoked Publish Web command, and I still got the same, original, unaltered, Publish Web Dialog Window – 2 weeks ago was “hijacked” by Azure.

I’m back in business!

And with that, I end my recollection of my past 2 weeks’ adventure in software development.

Till then!

Enhanced by Zemanta