Hi everyone,
I have an SGS 9000 with stock 2.1 + Voodoo lagfix on it.
When I bought it, the browser would detect and use Flash because it would use Flash Lite. I have since done a factory reset several times, and noticed that neither browser (Google's stock browser and Opera) can use Flash sites any more. I tried to remedy this problem by installing the Flash 10.1 apk onto the SGS but predictably this did not work.
Does any one know how to get Flash Lite to work with either the stock browser or Opera on 2.1?
Regards.
Please note: I shall not upgrade to Android 2.2 until the Voodoo lag fix is available. Then I shall. Discussions about Android 2.2 should be considered out of scope.
I have a GT-I9000M (Bell) SGS and I was wondering what mods, kernels, etc are compatible with it?
Most mods or custom ROMs are based on JPU or JPY and the only JL2 custom ROM is seeARMS version.
I tried to update to JS3 a couple of times but it only rebooted at the Samsung splash screen. How do I know what is compatible with the I9000M and what is not? Why is a ROM from Europe not compatible with my phone? Is it location set into the firmware?
I do not know what the differences between the stock ROM and the custom ROMs are, but some custom ROMs do work.
I have a funny feeling the bricks a lot of people are getting are due to incompatible mods and their firmware.
I would gather there is some info about this somewhere on the forums, but I was not able to find anything useful.
Thanks,
Ian
w98seeng said:
I have a GT-I9000M (Bell) SGS and I was wondering what mods, kernels, etc are compatible with it?
Most mods or custom ROMs are based on JPU or JPY and the only JL2 custom ROM is seeARMS version.
I tried to update to JS3 a couple of times but it only rebooted at the Samsung splash screen. How do I know what is compatible with the I9000M and what is not? Why is a ROM from Europe not compatible with my phone? Is it location set into the firmware?
I do not know what the differences between the stock ROM and the custom ROMs are, but some custom ROMs do work.
I have a funny feeling the bricks a lot of people are getting are due to incompatible mods and their firmware.
I would gather there is some info about this somewhere on the forums, but I was not able to find anything useful.
Thanks,
Ian
Click to expand...
Click to collapse
Hey,
I have a gt i9000m and have been flashing lots of custom roms. I have flashed Darky's rom, Doc's rom (jpy and js3) and used Hardcore's kernel and Supercurio's kernel. I have had no problems whatsoever with any of them. I would stay away from any lagfixes if i were you, just to be safe. Watch out because some versions of voodoo kernel (supercurio) have the lagfixes enabled by defaut on first boot. So if you hear a weird voice coming from your phone, do not turn it off. It may take up to 20 minutes to complete the process where you will stay on the first boot screen where it says GT i9000m / i9000. Lagfixes are not bad, just they can be a pain and imo do not show any real performance boost.
Basically your i9000m can handle anything that is for i9000 ...
I always flash custom rom's with CWM (which is included with cutom kernels). When i received my replacement i9000m,
1) i first flashed stock jl2 for the sbl.bin (fixes corruption issues)
2) flashed hardcore's kernel via odin.
3) let it boot to see that everything works.
3) download a doc's custom rom. preferably with hardcore's kernel.
4) put it on your internal SD card
5) Shut down phone, enter recovery
6) You should see a green menu if you installed the kernel correctly.
7) Choose Install zip from SD card.
8) Choose zip from sd card
9) navigate to and select doc's .zip you put on your sd card.
10) let it install and then boot. It can take a while (10 minutes) for first boot
Have fun
OH and the latest doc's rom have the APN set to inet.bell.ca, which is supposed to be tethering data. So go change that to pda.bell.ca in apn settings .... just as a precaution. I can't say if it actually incurs more charges because i have the 6gb tethering plan from bell
Hope this helps a bit, sorry for my bad english, im from Quebec
Hi! I'm experiencing some problem with my froyo upgrade... I'm from Quebec too. Can you help me?
my 9000m stop at S logo...
Can you give me the link where you download the files? I think my problem came from bad version for my Bell I9000M.
Lightarrow said:
sorry for my bad english, im from Quebec
Click to expand...
Click to collapse
Votre anglais est parfait. Plus bon que mon francais.
Thanks for the info. I really want info on flashing stock ROMs and kernels. I like the stock stuff. It seems as fast as cooked ROMs without the incompatibility I seem to have on some apps/widgets.
I heard 2.2.1 is a better performer with better GPS than 2.2 so I thought I would try it in stock form first.
Thanks,
Ian
thenamelessthing said:
Hi! I'm experiencing some problem with my froyo upgrade... I'm from Quebec too. Can you help me?
my 9000m stop at S logo...
Can you give me the link where you download the files? I think my problem came from bad version for my Bell I9000M.
Click to expand...
Click to collapse
Need more information before i can help you. What rom were you on ? JH2 ? were you updating with kies to JL2 ? with odin ?
You can download i9000 stock roms here : http://www.samfirmware.com/android.htm
You will need to register to download files. Get the JL2 stock rom and a copy of Odin to flash. Make sure to read guides on how to flash using odin on this forum like this one :
http://forum.xda-developers.com/showthread.php?p=7152078#post7152078
1.Flash Firmware and kernels using Odin.
Note: This will in (almost) all cases erase all your data and applications (includind root!). It will NOT touch the internal or external SD card.
Requirements:
-Odin3 version 1.7 (Note: Odin should be on the system partition (the partition where windows is installed) to avoid possible issues)
-".PIT" file for the Samsung Galaxy S (See FAQ#B9 or the source of the FW for the version to use! Not needed for kernel flashes)
-USB cable
-Desired firmware package or desired kernel package
Procedure:
1.Open ODIN. (And close Kies, if you have it open. It is important to have ODIN open BEFORE connection the phone via USB!)
2.Select the PDA/Modem/CSC/.PIT files in Odin. (For kernel flashes, only PDA is required. For FW flashes, .PIT and at least a PDA is required. Some PDAs have Modem and CSC integrated. Make sure you have the correct .PIT file. Usually 512.pit)
3.Check the "Re-Partition" checkbox.
4.Turn the phone into the download mode by pressing and holding VolumeDown+Home+Power.
5.Connect your phone with your computer and wait until the drivers are installed.
6.When the drivers are installed, click Start.
7.The phone will be flashed and once it’s finished, it will boot up. (Do NOT disconnect the usb-cable, remove the battery or otherwise interrupt this process!)
8.You have successfully flashed your phone.
Click to expand...
Click to collapse
w98seeng said:
Votre anglais est parfait. Plus bon que mon francais.
Thanks for the info. I really want info on flashing stock ROMs and kernels. I like the stock stuff. It seems as fast as cooked ROMs without the incompatibility I seem to have on some apps/widgets.
I heard 2.2.1 is a better performer with better GPS than 2.2 so I thought I would try it in stock form first.
Thanks,
Ian
Click to expand...
Click to collapse
Merci, je me doute toujours
i am currently on latest doc's rom from the kitchen and i have to say GPS is really spot on , I am using JL2 modem with hardcore's k12Q-t5 kernel + doc's base 9.1.3. the rest of the phone is just butter smooth without any lagfixes and tweaks. I find that the stock one is a little laggy but again, i have lots of apps and data
If you haven't tried yet, you should definately check out SuperCurio's sound fixes, they are amazing !! the SGS sounds soooo much better with them.
all you need is hardcore's (k12Q-t5) or supercurio's (5.2) kernel and the Voodoo Control App from the market. It really changes the output of the galaxy and makes it able to compte againts much higher-end audio devices
Have a good one
Thanks Lightarrow, I have tried so many of the custom ROMs but I was never really happy with them, so I always went back to stock.
I think I will try hardcore's k12Q-t5 kernel and SuperCurio's sound fixes asnd see how the phone is.
You're right, there is a slight (Very) lag with the stock JL2, but I never minded it.
Salut,
Ian
I think it's better to start a new topic for my problem. It's a long story....;-/
http://forum.xda-developers.com/showthread.php?p=10845624#post10845624
http://www.androidcentral.com/can-my-device-use-flash
The Samsung Galaxy S is not listed on this list.
I have Froyo installed and the Flash 10.1 player installed - I can't access Flash - why not ?
i9000m (2.2)
Funkadelick said:
http://www.androidcentral.com/can-my-device-use-flash
The Samsung Galaxy S is not listed on this list.
I have Froyo installed and the Flash 10.1 player installed - I can't access Flash - why not ?
i9000m (2.2)
Click to expand...
Click to collapse
I have flash and it works great. Im not sure whay you cant seem to access it. Make sure you have "plugins" enabled in your browser settings and then give it a go. You should have it no problem.
Also... You dont have to install the flash player from the market... When you upgrade to 2.2 it is automatically there. Perhaps you messed something up by installing the market version???
yiannisthegreek said:
I have flash and it works great. Im not sure whay you cant seem to access it. Make sure you have "plugins" enabled in your browser settings and then give it a go. You should have it no problem.
Also... You dont have to install the flash player from the market... When you upgrade to 2.2 it is automatically there. Perhaps you messed something up by installing the market version???
Click to expand...
Click to collapse
I am on 2.2 not 2.2.1
I have plugins enabled (does flash only work with stock internet browser???) I use opera
I have installed the 10.1 app
nothing .
whats a good flash site to check ?
i want to restock my tab to froyo from gingerbread ..as i am not happy with the performance of the gallery and some other apps ..
i am in india.. so can u please provide me stock froyo rom ..and i need help in reverting back ..
thanks in advance
First make a backup of your currently working firmware using ROM manager by CwM and copy all the files to your PC.
Then you need to know what is the model number of your Galaxy Tab. P1000 or other?
Start the phone application on somebody's Tab who has exactly the same Tab what you have and runs on Froyo. Then enter *#1234#. It will give you some data like:
PDA: P1000.....
PHONE: P1000.....
CSC : P1000.....
write it down. I have to mention that the code only returns data if it has the original stock on it and not a custom firmware.
What makes difficult that for Froyo and Gingerbread there are many country and mobile vendor specific versions and you have to find the correct version. Search the net for the correct version. You should find a file for example: P1000XXXXX_P1000XXXXX_P1000XXXXX_HOME.tar (XXXXXX = PDA, PHONE and CSC)
Extract this tar file to a directory on your PC.
Your Tab accepts only those specific files without problem. No other. Put your Galaxy Tab into download mode and install Heimdall driver.
Then start Heimdall Frontend to flash back the files. Load first the PIT file included in the package. Then make sure you put the correct files to the correct places.
http://vincent.bernat.im/en/blog/2011-android-samsung-galaxy-s.html
This site explains the structure.
inder6644 said:
.. i am not happy with the performance of the gallery and some other apps ..
Click to expand...
Click to collapse
An app called QuickPic is a nice alternative to Gallery, which I found is typically very slow & laggy on my devices. QuickPic is pretty snappy although there is a very slight delay in sharpening the pic when you advance to the next photo.
Are you still using a stock kernel? I wonder if you might get better performance using a compatible kernel that has Voodoo lagfix (ie. EXT4 conversion)?
Greetings from a droid noob,
I have been trying to update my Galaxy Tab GT-P1000M using KIES, but KIES keeps telling me that I cannot update using KIES. I am very frustrated by this. It might be because the Tab I have used to be a display model used in stores. There is a continual demo screensaver that I can't disable either. It might be that there is something custom about it from Samsung/Bell for this functionality. I have never rooted the tab.
I then downloaded P1000MUGKF6_P1000MBMCKF6_BMC.ZIP from Bell to try to update to Gingerbread using Odin. This is where I get confused.
I have made many searches and there appear to be just a many versions of Odin as there are guides for the various phones out there. The instructions do not seem to follow the same pattern. Some say uncheck partition, some say leave it checked. Some use a PIT file, some don't. I really don't want to brick it.
I would really appreciate any help I can get on this. Step by step instructions would be especially helpful.
Model number: GT-P1000M
Firmware version: 2.2
Baseband version: P1000MUGJJ6
Kernel Version: 2.6.32.9 [email protected] #3
Build number: FROYO.UGJJ6
Go to overcome site
Http://www.teamovercome.net
Read the guide,
Missing pictures can be seen here.
http://forum.xda-developers.com/showthread.php?p=20974872
Follow the picture step by step.
Basically to restock:
Download GB-stock-safe-v5.zip, unzip it and and flash with ODIN according to the guide.
Stop there and you will have Gingerbread JQ1
You can continue with the rest, and you will get Overcome 4.1 and you won't regret.
From there you can then try AOKP or CM9, all requires you to have Overcome Kernel with its CWM recovery to flash.
Thanks, priyana. I have actually seen that guide before. However, I am not trying to root. I am just trying to either go back to the "stock" FROYO and get rid of the KIES trouble or update to Gingerbread using ODIN.
"Stop there and you will have Gingerbread JQ1"
Not trying to root.
Read the guide images, it is exactly doing what you want. : flashing GB using ODIN.
BTW, no harm using the guide to apply your version of fimmware too.
Just use it as a guide for ODIN, what to put in what fields, what to tick, etc..
Also, it is good to hop on to GB stock safe first because that will get rid of bad bootloader, since some Froyo has locked bootloader.
Here is a step directly from the Guide section titled Preppin’ The System…
[REQUIRED FOR FROYO-BASED TABS ONLY:] Your Tab must be rooted.
Or am I understanding something wrong in those steps
Followed the pictures but I think I now have a brick.
My tab did not reboot itself as in the instructions. Instead it stayed in download mode. I rebooted manually...got the new start up sound and then got to the Samsung screen. It has been stuck on that for 10 minutes now.
Not sure if this is a good thing but I just saw the Samsung logo flicker.
Hmm.. did you get all steps passed in ODIN?
No harm redoing it again, but make sure you follow every steps (i.e. parts that let it reboot itself, etc)
Edit: I missed that bit that you said it did not boot itself.
I think it is essential, could it be that you didn't wait long enough?
The good thing is I think you can reach download mode, meaning you have not screwed up the bootloader, likely the bootloader were flashed correctly.
Power down the tab, and re-enter download mode and re-flash but make sure it completes itself.
Here, a very easy to follow going back to Gingerbread stock, follow carefully:
You can download any official firmware at http://fus.nanzen.se/
1a. Download Fus Check Downloader 2.1 from the above site. Using the Fus Check downloader, download a Firmware for your region. It will automatically decode the .enc2 file to.zip file
(For your case choose GT-P1000M)
1b. Download Odin3-v1.85
2. Extract the .zip file generated from decoding file to a folder and you will get
tar.md 5 file.
3. Start Odin - put the .md5 to PDA
3a. If your last firmware was gingerbread, leave everything else as is (No .pit file, leave repartition unchecked).
3b. If your last firmware was NOT gingerbread (get pitfile, and check the repartition) Note -- open up the.md5 package to check if there is a pitfile included,
as well as dbdata included. If they are included, you don't need to find pit file again, you can use it for your flash.
4. Go to download mode on the G-tab, connect it to your computer,
and click start on Odin. It takes about 6 to 7 minutes to do the flashing.
Good to know this! thanks.
I guess @ThiesWindu can try this way too, provided ODIN can see the tab.
Thanks, yappoe.
I am on step 3b. There was a tar file but no MD5. The tar file included a pit file but no dbdata.
I am going to try this. Fingers crossed.
Looks like I need that dbdata file as there was an error to that effect on the tab. However I did get further than last time. The tab is still stuck at the Samsung screen.
Where can I find that dbdata file?
Thanks
The issue was the dbdata.rfs file missing.
I found it here under misc notes.
http://forum.xda-developers.com/showpost.php?p=9305891&postcount=1
It finally rebooted but what I got was the following message:
Sorry!
The application com.sec.android.app.samsungapps.una (process com.sec.android.app.samsungapps.una) has stopped unexpectedly. Please try again.
Is this something major or is it normal?
Thanks for the help so far.
that is why I recommend Overcome GB Stock safe in the first place.
Too many people asking where is dbdata.rfs, factoryfs.rfs, pit files etc when using other method.
Could your problem stem from using dbdata.rfs from different ROM?
priyana said:
that is why I recommend Overcome GB Stock safe in the first place.
Too many people asking where is dbdata.rfs, factoryfs.rfs, pit files etc when using other method.
Could your problem stem from using dbdata.rfs from different ROM?
Click to expand...
Click to collapse
Yes, of course, but he specifically wanted a non-rooted stock, and most likely from his region (and probably is ready to sell the tab for the newer tablet )
@ThiesWindu: one more step, and you should be done! (Hopefully -- Unless Priyana's fear is true... then the dbdata might not be for your Tab
go to Recovery Mode, and do a Factory Wipe and a Data Cache wipe.
The tab is working. The dbdata file seems to have done the trick. The tab works fine just takes longer to boot than before. Had to re-install a ton of apps though. I guess there are different versions for the different droid versions.
Is the slow down on boot up of concern? This is the first time I have done this.
Why would the stock not include it?
First boot after flash always takes longer time. What happen is android is installing and configuring your device for the first time.
Dbdata, pit and bootloader are not always included in a packaged stock because some Releases are meant for 'upgrade'. Since these files rarely changed from version to version, it wouldn't be included.
That is also why Priyana directed you to Team Overcome's GB-Stock-safe, because they include everything in the package. But because they have complete package, sometimes it's overwhelming for some people to follow the instruction.
Perhaps now that you completed flashing your g-tab, if you go back to team overcome website, you will have less difficulties following their instruction.
It seems to take longer all the time. Once booted it seems smoother and faster than before.
I have a 2nd Galaxy Tab that I can compare the times to and then report back when I get home tonight.
Thanks again
Compared it to the other tab and the boot time actually improved a little. Guess nothing to worry about then.
Thanks for the help guys.
updating your Canadian P1000M tab to android 4.4.4. or whatever other ROM you wish
I didn't want android 5 or up but the most stable Custom rom on my tab which only had the 2.3.3 update on it.
The problem with all the custom ROMs was they wouldn't work on the P1000M sim card model as only made for a P1000 .
There were a few threads about converting my current model to a P1000 but somewhat confusing about exactly what to do and where to get the downloads needed .After two days of playing around I found the guide and links in this thread as the most helpful they worked :http://forum.xda-developers.com/showthread.php?t=1881981
Once you install the GB Stock safe 5 tar file as per PDF instructions(which you need to read a few times ) use the JPZ Modem folder as per instructions on PDF –this is an Italian modem bin file but it will convert the P1000M to a P1000 which then allows you to complete the rest of the installs with the overcome wipe files and at the end of all the installs ,put your chosen recovery rom on tablet internal memory and flash using whatever custom Rom for a P1000 you wish (as there isn’t any links or availability for a P1000M except for gingerbread).Its a long process to get to using the custom rom but it works and seems to be the only way to go. I used omni nightly4.4.4 plus the gapps files and and updated SU zipfile.
Unfortunately once the omni ROMwas installed I kept getting the android process media has stopped message constantly so used the following to fix that issue :
Go to your app settings page (Settings > Applications > Manage Applications) and open Media Storage. Hit clear data.
If you have a custom recovery installed (most custom ROMs and kernels do have it), boot into it and fix permissions. In Clockworkmod Recovery, you can find it under “Advanced”. TWRP recover also has a similar option. Being a Linux-based OS, permissions are of paramount importance to smooth functioning of Android components.
In Manage Applications, open Google Services Framework. Clear data.
Open Google Play Store. Hit clear data. Note that this will clear all play store data, including your Google sign in. You will have to login with your Google / GMail account again the next time you open Play Store.
Open Download Manager, and clear its data too.
Backup your data and format SD card. Make sure to backup all data on your SD card, including media, apps and other files, before formatting it. Use FAT32 formatting, which is preferred for Android. This is because android.process.media is related to camera, gallery and other multimedia components, and SD card errors may cause this force close error.
Try a different SD card. Many SD cards, particularly those of class 6, 8 and 10, have been reported to not work reliably with Android devices. Class 4 seems to be the safest option .
Now running 4.4.4 on my tab P1000. thank goodness.