Up to today, I still don't get why everyone is so enamored with Kies. It's a pretty crappy POS. If you really want to return to the stock JPE Gingerbread that is official for the Malaysian Samsung Galaxy Tabs, just go to samfirmware.com and grab the JPE edition. That's what I just did, easy as pie. All done in a matter of minutes - and having it stored in my folder as a backup, in case I ever need to send in for warranty is simple as pie too. All you have to do post Odin-flash is the *#272*IMEI number# routine to set it to XME and you're set.
Flashing firmware is not that tough. It's not easy too, especially if you're new to it. That's why you should read up and learn for yourself. Once you know the basics, you can do it with your eyes close. Just don't rush through the process, read up, do it step by step and learn what does what, each step of the way, and you'll learn in no time. That's why I'm darn
sien to help newbies that after first or second line of advice, still want to be spoon-fed.
I've seen idiots come with the mentality "I've been flashing ROMs for years on my Desire, yada yada yada..." and rush through the process and
fished-up their system big time, either because of arrogant assumptions and all that. Each manufacturer is different and their processes is different. Deal with it.
Dumbest move I've heard, installing the other POS, the ROM Manager app on the Galaxy Tab and swearing it'll work on the Tab.
---
To the poster who asked about the browser performance after reading about it in the reviews. Please note that almost all the reviews were based on the early firmware that the Galaxy Tab was released way back in August of last year, (whether it's the Asian JJ2 or the European JH3 versions) or gawd-forbid, the crippled American versions. Since then, there's been a slew of firm updates to the Tab, culminating in the latest Gingerbread-based JPE version. I would challenge anyone to say that the current browser on the latest Gingerbread-based firmwares is slow. It'll beat the pants of any of the competitors.
Which is why, sometimes I wonder if there a perceived bias to anything Samsung in the main-stream media. Sure, their update policies on their older-WinMobile units like the Omnias in the past may have contributed to it, but I've literally seen them turn over a new leaf with their Android phones (I'd even say, they're more pro-active in this area compared to the supposedly darling of the Android crowd, HTC - look how they'd literally had to backtrack with their tails tucked between their legs with the Desire/Gingerbread fiasco!) Samsung's on a much better roll!
Don't believe me? Just look at the list of firmware released for the European Region alone: 26 distinct firmwares since August 2010! 26 firmware updates in one year! And that's for Europe alone. 16 for the Asian version. For my HTC Hero? 3 in the entire life span of the phone's life span!
Sure, as a developer, some of the things Sammy does proprietorially do drive me nuts, as it makes my life quite difficult, but it's those a development choices that shouldn't affect most users.
---
@alshahmii and all.
First and foremost, and don't take this the wrong way, but please do not PM me directly about issues, as my mailbox is indeed heavily flooded, much so much that I rarely check them anymore. But you're in a sense quite lucky this very instance that I did, but I'll address this here for the benefit of others as well:
I am having a problem at the moment. Here's the scenario:
Went back home last nite. Played with my SGT til battery remaining 10% and was warned a couple of times. Plugged in for charging and still running coz was downloading the sd data for NOVA and let it be till this morning.
Turned it on and the battery was 100% charged. Noticed it was turned off. Tried turning on and it is stuck at loading (robot with a blue circle) until now. Tried turning it off and back on but still stuck at loading.
Using OC 1.6.4. So far no problems and this is the first time stuck.
Planning to move to Hermes or Jupiter later once this problem is solved. (recommendations?) Well, I'm not sure what's causing it to bootloop. Were you installing or doing anything else beside the Nova? It's rare for a stable firmware like the Froyo-based OC1.6.4 to just suddenly bootloop like that.
Without actually knowing the real reasons for the bootlop, I can't really diagnose. However, in cases like that, here's a few
possible solutions:
1) Get into the recovery and try doing a wipe of the cache and the dalvik cache, as well as a fix permissions routine. Usually this might help clear most issues. Do note that it'll take quite a while for it to boot right after this, especially if you got a lot of apps installed. Say around 5-15mins depending on apps installed.
2) If this fails, try to reflash the kernel. Repeat step 1 as well.
3) If that fails too, last recourse, try to find the 1.6.4 updater (not sure if the links are still alive, as we stopped supporting it a long time ago) and flash that. Repeat step 1 as well. This might clear out any gunk that my be jamming the system up.
However, if you're not inclined to try to salvage the data, then just restock according to the guide at teamovercome.net and just move on to Jupiter.
Cheers.
tpb
If these
Noted...sorry and thanks mate.
p/s : Did no. 3 to be safe and nothing to save.
Jul 6 2011, 09:53 AM
Quote
0.0391sec
0.46
7 queries
GZIP Disabled