MIUI rom - Questions, Issues, Bugs, Problems, Complaints - Galaxy S I9000 General

Hi to all,
I created this thread here is for existing users, potential users, interested users and experienced users or any casual visitors who wants to know more about the rom. Well, SGS users will ask why create a thread just for this, when there is another one over at the development section. The answers are listed as follows:
To reduce the number of posts in the other thread (reduce spamming) thereby not bogging down the developers with issues that can be solved by the users. And they can spend their time to concentrate what they do best, which is improving the MIUI Rom.
To consolidate questions, problems, bug reports, comments in one place. As you can see from the other thread, many a times, some of the posts which benefits the users were consumed by newer posts. While there is a SEARCH function, I can understand it can sometimes be a challenging task just to sieve through the searched posts results. I know we can't eliminate users posting repeated issues, but at least this will attempt to reduce those posts.
To allow new xda members who are on MIUI but unable to post their ideas, comments, etc. This is also an important avenue to allow new xda members to have a voice. While they may be new, they might have tips, tricks and also can help to resolve issues. Issues brought up can be shared by everyone too.
To allow the developers concentrate on improving the MIUI rom. Who doesn't want a better MIUI? Of course the developers doors will always be open, and will help out whenever they can, but wouldn't it be better for us to let them concentrate on what they do best, and what we want best?
So, to make it successful, I need you guys to help one another out, like what I have seen over the other thread.
This thread belongs to all of you, and I am sure that there is active participations in here.
MIUI has a pretty long history. However, for our device, MIUI has just evolved. Likewise, the user base has just started to grow. There will be times when even the most experienced user or developer will get stumped too, and not able to come up with a solution to resolve. We can see from the other thread that there are diverse views regarding battery life, sdcard issue, etc etc. We will not know since the usage pattern of each individual is as good as your fingerprint. No one is alike. Therefore we seek your understanding that issues not solved immediately will be looked into seriously by the team. There will always be limitations for every rom, regardless what base they come from.
All we ask is whether this rom fits your usage or not. And the only way for you is to try it out. Feel it, experience it, and judge for yourself if this rom fits you, can you live with the shortcomings of the rom. If you decide that this rom doesn't fit your daily needs, you can just simply flash to another rom that fit your needs better. And you can at least tell yourself that I have tried but it is not suitable.
Is this thread some form of advertising? Well, again different interpretations for different people. We will not go into that as we believe the QUALITY OF THE ROM WILL SPEAK FOR ITSELF.
One thing that can be said though, credits goes to the cm7 team, the official MIUI developers too. And each day, we can see breakthroughs. I do foresee a bright future for this rom here.

FAQ Section​
[Written by Galnet, g00ndu and me]
Before asking for help, please read through post 1 to post 4. Most of the issues have been addressed in this 4 posts. By doing so, you are helping to keep this thread clean.
1. APP RELATED:​
1.1 Apps crashing all the time!
Simply enter recovery mode and do a Format on Data, System, Cache
1.2.1 Apps restored from backup not working
I would always flash from clean and redownload all your apps from market. I know you can backup and restore, but to me this causes alot of issues which people bring up all the time. If you want a clean install and avoid any issues in the long run, then 15 - 20 minutes of redownloading isn't as bad as hours of issues!
Also, if you want to try to restores apps using Titanium Backup, restore "APP ONLY," restoring data causes problems.
1.2.2 3rd party apps force closing
Turn off compatibility mode. Settings > Programs Tab > Manage Applications > All Tab > Select app > Turn off OR IF IT STILL FORCE CLOSES Settings > Programs Tab > Manage Applications > All Tab *again* > Select app > Clear Data > Uninstall and then reinstall using Market.
1.3 Apps not installing
Clear market cache and try again.
1.4 Can't See Paid Apps in Market
Download SGS-Tools and select Market Fix and apply then reboot.
1.5 Downloading from Market Not working
Goto Downloads Press Menu Key and switch Settings to WiFi or Mobile network.
1.6 Searching not working
Simply enter search advanced settings and turn off searching within SMS (Mentioned on Original Post)
2. HARDWARE RELATED:​
2.1 SD-CARD Not working or other issues with Camera or Sensors
When flashing if you don't see the Cyanogen Logo after the Samsung one when turning the phone on to enter recovery (After flashing cm7-galaxys-initial-kernel.tar) , then STOP flashing process as you have done something wrong or are trying to install coming from a JVK rom. Downgrade to Froyo or if need be JM1 and start the process over.
Also, camera is not working properly (known bug) – poor saturation and multiple lines running through image.
2.2 External SD card not detected
If your external sd card is not detected even when the kernel had corrected the issue, you most likely has the 2.3.3 bootloaders. You may flash the bootloader (definitely not recommended) or you can restart using EZBase rom or follow galnet's guide in his site.
2.3 Auto rotation/accelerometer not working
If your auto rotation/acceleromter is not working (despite having it enabled in Settings > Common Tab > Display Settings > Auto-rotate screen) then hard reboot (completely switch off device, wait 10+ seconds, and then switch device back on)
2.4 High Battery Drain
Known CM7 bug that is not fixed yet.
2.5 Battery only reports ~96% on full charge
This is a function implemented on ALL 2.2.1+ ROMS (including MIUI, which is based off CM7 2.3.3) so that the battery of the devices do not overcharge. Samsung ROMS falsely report 100% charge, but in actual fact, it also charges to ~96% and that if you watch closely, after a few minutes, the battery will rapidly drop back down to ~96% and stablise.
http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
2.5 Battery has stopped charging
Battery is known to stop charging when it gets too hot. This is to protect the battery and phone from exploding.
2.6 Phone turns on when I insert charger
This is a known bug (or function LOLS) which is present in the Nexus S ROMS and because the SGS MIUI ROM is a derived from the MIUI Nexus S ROM, SGS will also have this bug/function.
3. ETC:​
3.1 Where do I start?
Have a look at Galnet's MIUI Guide and note that you can start from ANY Froyo ROM (Stock and Custom) as long as your device has a Froyo Bootloader.
3.2 Flashing from JVK to MIUI
You must first downgrade the firmware to Froyo (which MUST include a Froyo Bootloader - check in zip via WinRar for boot.bin and sbl.bin) It has been found that the Gingerbread bootloader has caused major problems. It is recommended that you downgrade to Eclair JM1 then upgrade to JS5 (files are avaliable on Galnet's Website) and then follow Galnet's MIUI guide to flash MIUI.
Note that flashing/using any Gingerbread modems such as JVK will not cause problems, it is only the Gingerbread bootloader that is causing problems.
3.3 IMEI SCREWED!
Flash back to JS5 or another Official Rom and it will be restored!
3.4 FLASH AT OWN RISK
If you don't have a clue what you are doing or ODIN is a strange word, then please go over to Galnet's MIUI guide and read it before flashing, make sure you understand the risks and note that the developers are not always available to answer your questions instantly!
3.5 Applying a downloaded theme:
Move theme file anywhere onto your phone's memory (should have a .mtz file extension) > Open Theme Manager > Press on Capacitive Menu Button > Import Theme > Locate and Select the theme you added onto your phone's memory
Alternatively, you can directly move the theme (.mtz) file to sdcard/MIUI/theme/
3.6 (SOME) Themes not changing lockscreen
Check that the theme supports MIUI Gingerbread 1.4.8, older MIUI FROYO themes will not work.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
COPY AND PASTE:
(Insert FAQ here)
In the future, please refer to the MIUI FAQ Section[/URL ] before posting.

TIPS AND TRICKS
1. Download seems to get stuck forever. Download only works with wifi.
To fix, open up the Download App, click menu, select toggle 3g /wif. This normally will work. If it doesn't work, try for 2 or 3 times. Remember to cancel the download from the app. If it still doesn't work, reboot and try again. The best fix will be to boot into recovery, and do a wipe / factory reset and reboot. Before downloading, go to the download app to activate the 3g / wifi toggle.
2. Speaker phone is too loud (Thanks to Ekin)
Goto DSPManager > Phone Speaker > Enable equalizer
Then drag all the zeros on the graph down to about -3.0 but keep them all roughly the same. This will lower the volume on the loudspeaker for everything, fixing your problem. When you want to watch a movie and want to make it louder, go back here and just swipe it to disable. So its only one swipe to get it on/off. In order to keep the settings, you need to hit the Back button for it to register correctly.
Raising it/enabling bass boost seems to kill the quality a little bit, so I recommend not to do those.
I have a Nokia headset that I use, and its a little quite so I do the same trick (except I raise the "headset" equalizer) and this nifty trick is basically the same as the voodoo sound hack which takes proper use of the high-quality sound card inside the Hummingbird.
3. Choppy / Laggy graphics and interface (Thanks to whitesox311)
In the settings under battery options....it has " power saving mode" on automatically....if you disable this it gets rid of all the issues. Also, if you leave "Hi-res graphics" turned off in the launcher settings it vastly improves smoothness.
4a. How to get Swype to work (Thanks to Prototype159)
Download the swype installer.
Follow the directions all the way til the end.
Hit the finish button. Reboot.
If it didn't work, clear data and uninstall swype and the swype installer. Try again.
If you change the kernel, you will have to redo it again.
4b. How to get Swype to work (Thanks to agha123)
Follow the instructions to the tee on this web page ,
http://www.androidpeek.com/2010/12/get-swype-keyboard-working-on-miui-rom/
5. Screenshot (Thanks to hacksome)
Pressing Menu + Volume DOWN -->> Screenshot!

reserved
Sent from my GT-I9000

Hmm...good timing. I have some questions on my own.
I have been reading the installation procedures for a while. This particular line intrigues me
6: Pull out the USB cable and start (in download mode) with 3-button-combo in recovery mode (waiting until samsung logo appears)
How do I start recovery mode within download mode? I don't want to take any risks but wish to understand fully on what I will be doing before I commit.
Another question: Assuming that later I decided MIUI is too buggy, is there a backtrack procedure? Usually I will just reflash with ODIN to a stock rom(eg: JPY) to rid of all the lagfixes etc then to maybe Doc's rom for example.
Since this is a ASOP sort of ROM in GB. how do I go about it?
Noob questions I know but I rather be noob now then to beg for help around later

i dont have the maps application in my rom. After installation i dont see any maps app.

mystifiyer said:
Hmm...good timing. I have some questions on my own.
I have been reading the installation procedures for a while. This particular line intrigues me
6: Pull out the USB cable and start (in download mode) with 3-button-combo in recovery mode (waiting until samsung logo appears)
How do I start recovery mode within download mode? I don't want to take any risks but wish to understand fully on what I will be doing before I commit.
Another question: Assuming that later I decided MIUI is too buggy, is there a backtrack procedure? Usually I will just reflash with ODIN to a stock rom(eg: JPY) to rid of all the lagfixes etc then to maybe Doc's rom for example.
Since this is a ASOP sort of ROM in GB. how do I go about it?
Noob questions I know but I rather be noob now then to beg for help around later
Click to expand...
Click to collapse
It means exactly that. In download mode hold the 3 buttons (vol up, power & home) and release all keys when the Samsung logo appears. After about 5 seconds you will see recovery mode.
You can easily backtrack. In Odin use a fw that has all three files and tick repartition. I use jpu.
Sent from my GT-I9000 using XDA App

sxi200 said:
It means exactly that. In download mode hold the 3 buttons (vol up, power & home) and release all keys when the Samsung logo appears. After about 5 seconds you will see recovery mode.
You can easily backtrack. In Odin use a fw that has all three files and tick repartition. I use jpu.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
@mystifyer,
this is the same answer i will give. it is correct.
thanks sxi200.
Sent from my GT-I9000

vivekrk44 said:
i dont have the maps application in my rom. After installation i dont see any maps app.
Click to expand...
Click to collapse
maps can be downloaded from market.
Sent from my GT-I9000

This is new! I didn't know we can do that!
Shall give it a try this Friday Thanks for the explanation
Another question:
I understand also that ASOP roms don't have the very good codec support. Fair enough. Some threads I seen has mentioned of Moboplayer. I gave it a try. Works well enough in hardware acceleration mode but software decoding mode looks really slow.
Now my question is: Does software decoding mode works better in ASOP roms than say a generic lagfixed rom?

vivekrk44 said:
i dont have the maps application in my rom. After installation i dont see any maps app.
Click to expand...
Click to collapse
Download from Market.

mystifiyer said:
This is new! I didn't know we can do that!
Shall give it a try this Friday Thanks for the explanation
Another question:
I understand also that ASOP roms don't have the very good codec support. Fair enough. Some threads I seen has mentioned of Moboplayer. I gave it a try. Works well enough in hardware acceleration mode but software decoding mode looks really slow.
Now my question is: Does software decoding mode works better in ASOP roms than say a generic lagfixed rom?
Click to expand...
Click to collapse
wow, this one i dont really know. i am not sure if there were bemchmarks being made on that or not.
not a good comparison, but still say this. i ran quadrant for this two roms, and the framerate for samsung is better in 3D, and not much different on 2D.
dont forget samsung did not release the sourcecode, and cyanogenmod do it from scratch. but nevertheless it is still good in aosp.
Sent from my GT-I9000

Prasad007 said:
Download from Market.
Click to expand...
Click to collapse
tks buddy, glad you are here too.
Sent from my GT-I9000

g00ndu said:
tks buddy, glad you are here too.
Sent from my GT-I9000
Click to expand...
Click to collapse
Likewise.

No problem. I will know it after I try this Friday. I can share it then, provided nothing goes wrong.
Quite a fair bit of adventurous users tend to dive in straight without checking the cons of a ASOP rom, only to regret and then flash back. I don't really want to fall in this category.
Multimedia is big for me as I watch alot of animes. This codec problem might give me abit of a headache with the software decoding and probably missing code support.
I think I asked enough. Shall camp here and explore other users' problems.
Thanks for the feedback. Appreciate it.

Did the galnet's instructions and the result is the same. so tired by the way

dr.bahaeddin said:
Did the galnet's instructions and the result is the same. so tired by the way
Click to expand...
Click to collapse
I've PM'ed you, I advise you do a 3 file install of JP2 via ODIN to make sure all your files on the phone aren't corrupted.
Once you have got Froyo installed then please get back to us. (Boot into Froyo and make sure it's all working correctly)

galnet said:
I've PM'ed you, I advise you do a 3 file install of JP2 via ODIN to make sure all your files on the phone aren't corrupted.
Once you have got Froyo installed then please get back to us. (Boot into Froyo and make sure it's all working correctly)
Click to expand...
Click to collapse
got your message man downloading right now. maybe my internal sd makes files corrupted?

dr.bahaeddin said:
got your message man downloading right now. maybe my internal sd makes files corrupted?
Click to expand...
Click to collapse
Pass mate, but if you have a felling this could be the case then format the internal sd, after installing Froyo and then copy the required MIUI files back across to your internal sd and then try to proceed in flashing MIUI again.

galnet said:
Pass mate, but if you have a felling this could be the case then format the internal sd, after installing Froyo and then copy the required MIUI files back across to your internal sd and then try to proceed in flashing MIUI again.
Click to expand...
Click to collapse
ok now i'm on JP2 everything works fine.

Related

My test results for several DK17 ROMs

I am posting this message in the developer section because I thought the developers of the various ROMs might want to know of problems that at least one user is experiencing.
The problems I have noticed include the loss of ADB access to the phone, Market freezing and doing reboots during updates and installs, and apps installed via Zips not showing in Market Downloads for updates.
It appears that the problem with the Market freezing during updates may have been caused by me doing multiple zips when in clockwork, for these tests I only did one zip each time and that corrected the problem.
I was experiencing a problem where ODIN would not recognize the phone after the DK17 ROM was loaded but I suspect that was due to going from one DK17 ROM to another because the process I followed below ODIN saw the phone each time.
The ADB not working and the zip apps not showing persist. My test plan and results for multiple ROMs are below...
My process...
- Use 3 finger salute to enter Clockwork Recovery
- Wipe 3 times
- Install from zip to [ACS] SyndicateROM 1.0.2 (Shuriken)
This ROM works well for me and does not experience any of the problems I have been having with DK15
- Reboot system and confirm proper operation
- Able to use ADB
- WiFi, 3G, and 4G working
- All Apps installed via Zip detected by Market
- Update of App (Using Google Maps) not hanging system
- Power down system
- Reboot phone into Download Mode
- Confirm Odin3 v1.61 sees the phone
- Remove battery for cold restart
- Use 3 finger salute to enter Clockwork Recovery
- Wipe 3 times
- Install from zip to desired ROM
- Reboot System
- Test ADB
- Test 4G
- Sign into Google
- Test Update of App (Google Search & Maps)
- Power down system
- Use 3 finger salute to enter Clockwork Recovery
- Install Zip of preferred apps
- Reboot System
- Check Market for Apps
- Attempt Update again
- Retest ADB
- Connect WiFi
- Test Wireless ADB
- Reboot phone into Download Mode
- Confirm Odin3 v1.61 sees the phone
- Rinse & Repeat for next ROM
The results:
[Stock Flash][Odin]Dk17 Extended 11/27/2010
-------------------------------------------------
Filename: DK17-Extended.rar
Note: Installed via ODIN and not using Clockwork
ADB - Device not found
4G - Worked (Fell asleep during download - Continued after waking back up)
Market Update - Installs worked with no problems
Zipped Apps - Not listed in market
Market Update x2 - Worked
ADB x2 - Device not found
WiFi - Worked
adbWireless - Worked
ODIN - Detected (Retest?)
[ACS] Froyo Build DK17 - Deodexed/Zipaligned/Rooted - No FC - 11/23
-------------------------------------------------
Filename: acs-dk17-signed.zip
ADB - Device not found
4G - Worked
Market Update - Worked
Zipped Apps - Not showing
Market Update x2 - Worked
ADB x2 - Device not found
WiFi - Worked
adbWireless - Worked
ODIN - Detected
Froyo Beta V1.0.2 Devsforandroid
-------------------------------------------------
Filename: Mammon_Froyo_Beta_V1.0.2.zip
ADB - Works!
4G - Works
Market Update - Worked
Zipped Apps - Did not show
Market Update x2 - Worked
ADB x2 - Worked
WiFi - Workd
adbWireless - Worked
ODIN - Detected
Froyo Beta V1.0.3 - Devsforandroid 11-27-2010
-------------------------------------------------
Filename: Mammon_Froyo_Beta_V1.0.3.zip
ADB - Device not found
4G - Works (but sleeps easy)
Market Update - Worked
Zipped Apps - Not shown in market
Market Update 2 - Worked
ADB x2 - No
WiFi - Started Freezing - Restart Cycle
adbWireless - Unable to test
ODIN - Worked
Quantum Rom v1.4 DK17
-------------------------------------------------
Filename: QuantumRomv1.4_signed.zip
ADB - Device not found
4G - Worked
Market Update - Worked
Zipped Apps - Not detected
Market Update 2 - Worked
ADB x2 - Device not found
WiFi - Worked
adbWireless - Worked
ODIN - Worked
Quantum Rom v1.5 DK17 [WarpSpeed Edition] [Updated 11/27]
-------------------------------------------------
Filename: QuantumRomv1.5.zip
ADB - Device not detected
4G - Worked
Market Update - Worked
Zipped Apps - Not listed in market
Market Update 2 - Worked
ADB x2 - Device not detected
WiFi - Worked
adbWireless - Worked
ODIN - Worked
VIPERrom [IMPact] (DK17 Kernel) 2.2
-------------------------------------------------
Filename: VIPERrom [IMPact] DK17 2.2.zip
ADB - Device not detected
4G - Worked
Market Update - Worked
Zipped Apps - Not listed in market
Market Update 2 - Worked
ADB x2 - Device not detected
WiFi - Worked
adbWireless - Worked
ODIN - Worked
This is extremely helpful.
I've experienced the Sleep issue mentioned with the two ROMs mentioned above as well the ziped apps update issue.
Thanks for putting the time in to compile this
PokrTom said:
[Stock Flash][Odin]Dk17 Extended 11/27/2010
-------------------------------------------------
Filename: DK17-Extended.rar
Note: Installed via ODIN and not using Clockwork
ADB - Device not found
4G - Worked (Fell asleep during download - Continued after waking back up)
Market Update - Installs worked with no problems
Zipped Apps - Not listed in market
Market Update x2 - Worked
ADB x2 - Device not found
WiFi - Worked
adbWireless - Worked
ODIN - Detected (Retest?)
Click to expand...
Click to collapse
Well first thing wrong is that this isn't a rom by normal standards, its an Odin flash sort like the official Releases and what you get on your phone natively.
Secondarly it's also using the same "rom" flashable as the ACS dk17 that k0nane made. Second thing wrong is there is no way to install this via clockwork.
Therefore it's not a rom, it's a stock as sprint wouldnt have given it to you more or less and shouldn't be treated as a rom but as a recovery point.
Nothing overtly special has been done with this Flash or with the ACS k0nane flashable. so therefore there is nothing to fix.
Figured i'd make this point as everyone seems to see something new on the forums and go ooo new wrong works great except....
Perhaps understanding what they are would be a touch more helpful than a biased self comparision, seeing as how i could do the exact same test and get different results because my phones is different(ie it doesnt suffer the gps bug a fair amount do)
but it is what it is....
Take it with a grain of salt and understand that your mileage may very.
PS: the market not seeing apps is a simple fixable thing that's searchable in the forum, while it can be corrected quite easily, it's not a flaw that it's missing, these are BETA not for public distro leaks.
art3mis-nyc said:
but it is what it is....
Take it with a grain of salt and understand that your mileage may very.
PS: the market not seeing apps is a simple fixable thing that's searchable in the forum, while it can be corrected quite easily, it's not a flaw that it's missing, these are BETA not for public distro leaks.
Click to expand...
Click to collapse
This.
And keep in mind that stock builds don't turn USB Debugging on by default.
Tabulating the results would get you an A+; it's kind of hard to make any sense of it right now.
...but I also strongly agree that all of this is very circumstantial. The mere fact that some people have _____ working and others do not means that whatever results you get will not always be repeatable.
Yeah... Why would you list adb device not found when you forgot to turn on usb debugging? lmao.
art3mis-nyc said:
Well first thing wrong is that this isn't a rom by normal standards, its an Odin flash sort like the official Releases and what you get on your phone natively.
Click to expand...
Click to collapse
I understood this. I included it in my testing in part, as a baseline, and also because if I had not, then if someone had been interested in the results they may have asked how it behaved for me.
Forgive me for being a Noob and providing the information I did. I thought that this was a development forum, where developer might be interested in what results some people were getting. It appears that if you are not part of the developing community then input providing results is not wanted. I will just keep my mouth shut and enjoy the fruits of their labor.
On that point, to all the developers out there who have put forth the great effort they have, I give my thanks.
PokrTom said:
I understood this. I included it in my testing in part, as a baseline, and also because if I had not, then if someone had been interested in the results they may have asked how it behaved for me.
Forgive me for being a Noob and providing the information I did. I thought that this was a development forum, where developer might be interested in what results some people were getting. It appears that if you are not part of the developing community then input providing results is not wanted. I will just keep my mouth shut and enjoy the fruits of their labor.
On that point, to all the developers out there who have put forth the great effort they have, I give my thanks.
Click to expand...
Click to collapse
It is not that "We developers are better than you." It is the fact that the tests you performed were not done properly.
For one; For adb to work, USB Debugging must be turned on. (And no it is not on in every ROM by default)
What the hell are zipped apps?
PokrTom said:
I am posting this message in the developer section because I thought the developers of the various ROMs might want to know of problems that at least one user is experiencing.
The problems I have noticed include the loss of ADB access to the phone, Market freezing and doing reboots during updates and installs, and apps installed via Zips not showing in Market Downloads for updates.
It appears that the problem with the Market freezing during updates may have been caused by me doing multiple zips when in clockwork, for these tests I only did one zip each time and that corrected the problem.
I was experiencing a problem where ODIN would not recognize the phone after the DK17 ROM was loaded but I suspect that was due to going from one DK17 ROM to another because the process I followed below ODIN saw the phone each time.
The ADB not working and the zip apps not showing persist. My test plan and results for multiple ROMs are below...
My process...
- Use 3 finger salute to enter Clockwork Recovery
- Wipe 3 times
- Install from zip to [ACS] SyndicateROM 1.0.2 (Shuriken)
This ROM works well for me and does not experience any of the problems I have been having with DK15
- Reboot system and confirm proper operation
- Able to use ADB
- WiFi, 3G, and 4G working
- All Apps installed via Zip detected by Market
- Update of App (Using Google Maps) not hanging system
- Power down system
- Reboot phone into Download Mode
- Confirm Odin3 v1.61 sees the phone
- Remove battery for cold restart
- Use 3 finger salute to enter Clockwork Recovery
- Wipe 3 times
- Install from zip to desired ROM
- Reboot System
- Test ADB
- Test 4G
- Sign into Google
- Test Update of App (Google Search & Maps)
- Power down system
- Use 3 finger salute to enter Clockwork Recovery
- Install Zip of preferred apps
- Reboot System
- Check Market for Apps
- Attempt Update again
- Retest ADB
- Connect WiFi
- Test Wireless ADB
- Reboot phone into Download Mode
- Confirm Odin3 v1.61 sees the phone
- Rinse & Repeat for next ROM
The results:
[Stock Flash][Odin]Dk17 Extended 11/27/2010
-------------------------------------------------
Filename: DK17-Extended.rar
Note: Installed via ODIN and not using Clockwork
ADB - Device not found
4G - Worked (Fell asleep during download - Continued after waking back up)
Market Update - Installs worked with no problems
Zipped Apps - Not listed in market
Market Update x2 - Worked
ADB x2 - Device not found
WiFi - Worked
adbWireless - Worked
ODIN - Detected (Retest?)
[ACS] Froyo Build DK17 - Deodexed/Zipaligned/Rooted - No FC - 11/23
-------------------------------------------------
Filename: acs-dk17-signed.zip
ADB - Device not found
4G - Worked
Market Update - Worked
Zipped Apps - Not showing
Market Update x2 - Worked
ADB x2 - Device not found
WiFi - Worked
adbWireless - Worked
ODIN - Detected
Froyo Beta V1.0.2 Devsforandroid
-------------------------------------------------
Filename: Mammon_Froyo_Beta_V1.0.2.zip
ADB - Works!
4G - Works
Market Update - Worked
Zipped Apps - Did not show
Market Update x2 - Worked
ADB x2 - Worked
WiFi - Workd
adbWireless - Worked
ODIN - Detected
Froyo Beta V1.0.3 - Devsforandroid 11-27-2010
-------------------------------------------------
Filename: Mammon_Froyo_Beta_V1.0.3.zip
ADB - Device not found
4G - Works (but sleeps easy)
Market Update - Worked
Zipped Apps - Not shown in market
Market Update 2 - Worked
ADB x2 - No
WiFi - Started Freezing - Restart Cycle
adbWireless - Unable to test
ODIN - Worked
Quantum Rom v1.4 DK17
-------------------------------------------------
Filename: QuantumRomv1.4_signed.zip
ADB - Device not found
4G - Worked
Market Update - Worked
Zipped Apps - Not detected
Market Update 2 - Worked
ADB x2 - Device not found
WiFi - Worked
adbWireless - Worked
ODIN - Worked
Quantum Rom v1.5 DK17 [WarpSpeed Edition] [Updated 11/27]
-------------------------------------------------
Filename: QuantumRomv1.5.zip
ADB - Device not detected
4G - Worked
Market Update - Worked
Zipped Apps - Not listed in market
Market Update 2 - Worked
ADB x2 - Device not detected
WiFi - Worked
adbWireless - Worked
ODIN - Worked
VIPERrom [IMPact] (DK17 Kernel) 2.2
-------------------------------------------------
Filename: VIPERrom [IMPact] DK17 2.2.zip
ADB - Device not detected
4G - Worked
Market Update - Worked
Zipped Apps - Not listed in market
Market Update 2 - Worked
ADB x2 - Device not detected
WiFi - Worked
adbWireless - Worked
ODIN - Worked
Click to expand...
Click to collapse
Your kidding right? Well for starters, if you want a Froyo build/ROM to work right, first thing you gotta do is flash DI18 FULL ROM using Odin, then re-install clockworkmod, then flash (if your goin to a DK17 ROM ) the DK17 modem, and pit. Then you boot into cwm and wipe/factory reset 3 times, then wipe cache 3 times, then factory reset once more, then wipe Dalvik, then flash DK17 ROM, let phone boot all the way until your media scanner stopes (usually about a minute or two ). Then power back off, then boot back into clockworkmod, and wipe data 3 times, then wipe cache 3 times, then wipe data once more, but this time, dont wipe Dalvik. Then re-flash DK17 ROM and let it boot all the way. And ONLY then, will you have a fully working phone with DK17. If your not wiping cache before every MOD you install, you got problems. If you restore data after install of DK17 ROM, you will prolly get problems.
Im not saying that this will GUARENTEE that you will not have any problems, but I am saying that THIS method has treated me WELL over the past year or so. If you are doing ANYTHING differently, then how do I, or any of the DEV's here, take what your saying, to be fact, meaning that their ROM's are defective? Or somethings wrong with their ROM??? Im not saying your lying, all im saying is perhaps you did/doing something wrong.... you can chew on that a while, lol..
Dameon87 said:
For one; For adb to work, USB Debugging must be turned on. (And no it is not on in every ROM by default)
Click to expand...
Click to collapse
We learn something new everyday. This was something I did not know/realize. My guess is that up until now the ROMs I had downloaded had USB Debugging on my default and so I had not connected those dots.
I had posted earlier that ADB had not been working for me with the DK17 ROMs and no one had responded that I needed to check if USB Debugging was turned on.
I now know that and will act accordingly.
Dameon87 said:
What the hell are zipped apps?
Click to expand...
Click to collapse
I placed a number of apps that I prefer to use into a Zip file, similar to the ROM files being provided, but only apps. Signed the zip, and then used clockwork to install those apps, saving me the time of downloading and installing all of them.
art3mis-nyc said:
Well first thing wrong is that this isn't a rom by normal standards, its an Odin flash sort like the official Releases and what you get on your phone natively.
Secondarly it's also using the same "rom" flashable as the ACS dk17 that k0nane made. Second thing wrong is there is no way to install this via clockwork.
Therefore it's not a rom, it's a stock as sprint wouldnt have given it to you more or less and shouldn't be treated as a rom but as a recovery point.
Nothing overtly special has been done with this Flash or with the ACS k0nane flashable. so therefore there is nothing to fix.
Figured i'd make this point as everyone seems to see something new on the forums and go ooo new wrong works great except....
Perhaps understanding what they are would be a touch more helpful than a biased self comparision, seeing as how i could do the exact same test and get different results because my phones is different(ie it doesnt suffer the gps bug a fair amount do)
but it is what it is....
Take it with a grain of salt and understand that your mileage may very.
PS: the market not seeing apps is a simple fixable thing that's searchable in the forum, while it can be corrected quite easily, it's not a flaw that it's missing, these are BETA not for public distro leaks.
Click to expand...
Click to collapse
True that!!!
PokrTom said:
We learn something new everyday. This was something I did not know/realize. My guess is that up until now the ROMs I had downloaded had USB Debugging on my default and so I had not connected those dots.
I had posted earlier that ADB had not been working for me with the DK17 ROMs and no one had responded that I needed to check if USB Debugging was turned on.
I now know that and will act accordingly.
I placed a number of apps that I prefer to use into a Zip file, similar to the ROM files being provided, but only apps. Signed the zip, and then used clockwork to install those apps, saving me the time of downloading and installing all of them.
Click to expand...
Click to collapse
If those aren't working; then you likely didn't make the zip properly. You have to have an update-script add the files either to /data/app or system/app respectively.
They also have to be in a proper format: example:
./
./META-INF
./META-INF/folders under it
./system
./system/app
./data
./data/app
And of course a properly made update-script (Copying the files to the proper directories.)
sniperkill said:
Your kidding right? Well for starters, if you want a Froyo build/ROM to work right, first thing you gotta do is flash DI18 FULL ROM using Odin, then re-install clockworkmod, then flash (if your goin to a DK17 ROM ) the DK17 modem, and pit. Then you boot into cwm and wipe/factory reset 3 times, then wipe cache 3 times, then factory reset once more, then wipe Dalvik, then flash DK17 ROM, let phone boot all the way until your media scanner stopes (usually about a minute or two ). Then power back off, then boot back into clockworkmod, and wipe data 3 times, then wipe cache 3 times, then wipe data once more, but this time, dont wipe Dalvik. Then re-flash DK17 ROM and let it boot all the way. And ONLY then, will you have a fully working phone with DK17. If your not wiping cache before every MOD you install, you got problems. If you restore data after install of DK17 ROM, you will prolly get problems.
Click to expand...
Click to collapse
Live and learn. I did post the process that I used, which did not involve all of the steps you listed above. I will follw what you recommend in the future.
sniperkill said:
Im not saying that this will GUARENTEE that you will not have any problems, but I am saying that THIS method has treated me WELL over the past year or so. If you are doing ANYTHING differently, then how do I, or any of the DEV's here, take what your saying, to be fact, meaning that their ROM's are defective? Or somethings wrong with their ROM??? Im not saying your lying, all im saying is perhaps you did/doing something wrong.... you can chew on that a while, lol..
Click to expand...
Click to collapse
Understood, which was why I listed the process I followed, that way some of what I did was there and may have shown where I may have made a mistake. Which has been pointed out to me earlier regarding turning on USB debugging. I do not expect any developer to take what I post to be a statement that their ROM is broken. I never said that anyones ROM was broken, I started the post saying that I thought the developers might want to know what one user was experiencing. I know that it could be something I did.
Dameon87 said:
If those aren't working; then you likely didn't make the zip properly. You have to have an update-script add the files either to /data/app or system/app respectively.
Click to expand...
Click to collapse
I am using an update-script and the applications themselves are being installed and are working, they just don't show up in the market as installed. Something that there must be a fix for since sniperkill referenced searching the forums for the fix, so I will do that and will hopefully find it.
PokrTom said:
Live and learn. I did post the process that I used, which did not involve all of the steps you listed above. I will follw what you recommend in the future.
Understood, which was why I listed the process I followed, that way some of what I did was there and may have shown where I may have made a mistake. Which has been pointed out to me earlier regarding turning on USB debugging. I do not expect any developer to take what I post to be a statement that their ROM is broken. I never said that anyones ROM was broken, I started the post saying that I thought the developers might want to know what one user was experiencing. I know that it could be something I did.
I am using an update-script and the applications themselves are being installed and are working, they just don't show up in the market as installed. Something that there must be a fix for since sniperkill referenced searching the forums for the fix, so I will do that and will hopefully find it.
Click to expand...
Click to collapse
Oh. That is because when installed from the market, the market sets information in the database that says it is installed. This likely will not be fixable by using a zip to flash a bunch of apps. I believe what sniper was referring to was market apps now showing up because of the fingerprint in the build.prop.
Dameon87 said:
Oh. That is because when installed from the market, the market sets information in the database that says it is installed. This likely will not be fixable by using a zip to flash a bunch of apps.
Click to expand...
Click to collapse
I looked for the apps installed via the ZIP because when I did the same think using the Syndicate ROM on 2.1 all of the apps installed via the zip file did show up in the market, so I had been looking for the same thing.
It was worth a try, I have 4 Android phones in the household (My Epic & 3 Heroes) and so I was looking for any way to make reinstalling apps easier.
Thanks to all who answered questions or pointed out where I made mistakes.
k0nane said:
This.
And keep in mind that stock builds don't turn USB Debugging on by default.
Click to expand...
Click to collapse
I'm runing the ACS buildand USB debugging is definitely not on by default. After I enabled it ADB works fine.
Good stuff though! Thanks for the useful info!
Sent from my SPH-D700 using Tapatalk
it will be in next build
pokrtom, thanks for the informative post its always good to see people giving feedback that isnt "zomg dis is teh suxz you broke wifis!!!" 950 times over.
This is the first time Ive seen someone else notice the 4g sleeping issue. I thought I was imagining it.
Any clues on what could cause it?
sniperkill said:
Your kidding right? Well for starters, if you want a Froyo build/ROM to work right, first thing you gotta do is flash DI18 FULL ROM using Odin, then re-install clockworkmod, then flash (if your goin to a DK17 ROM ) the DK17 modem, and pit.
Click to expand...
Click to collapse
If you're going to try and bash someone atleast do it right. If you're going to be flashing the dk17 modem then why the hell would you flash the di18 first? All the dk17 modem does is overwrite... so ummm nothing stays behind which means.. un-needed step. Anyways..
Why don't you people stop being assholes. He's merely trying to help out the community with his testing efforts.. yea maybe he did a few things wrong but he's new.. we all were in the same boat.
Give the new people a chance; the ones who arnt meant to be fall through the cracks.. whilst the others stand by and prosper..
agreed. although i might also say that going from rom to rom, i have noticed that i have needed to uninstall the epic drivers and reinstall them to get them to notice my phone. this is on my win7 bootcamp on my mac.
that being said, you might also do a little bit of searching and throw some other general errors in the mix, that way we can be sure and document what is a "rom" bug or a "froyo" bug. that way some of the developers will ease off your back a little bit.
for example, i havent been using sniperkills 30 step "getcha rom runnin right" method, just a simple 3f salute, wipex3, install zip, restore apps from mybackup pro (still have never gotten titanium backup working correctly on my epic) and voila call it quits. but i have noticed a constant keyboard wake every 5-10 seconds with the keyboard slid out. this is on every rom ive tried so im thinking its a froyo problem and less of a specific problem.
just saying, lets make this a project and not a "dear developer. your rom blows. love the community."

[Telus T959D Fascinate][VIDEO]step by step instructions to use custom roms

[TELUS FASCINATE USERS] Hello XDA and community. I've compiled a complete walkthrough to install either i9000 or vibrant custom roms onto a telus T959D fascinate. Follow these instructions to have relatively the same STABLE setup im using at the moment
I AM NOT ACCOUNTABLE IF U BRICK YOUR PHONE!!! PLEASE FOLLOW CAREFULLY!! I MADE SURE I MENTIONED EVERY SINGLE BIT OF INFORMATION SO YOU COULD FOLLOW ALONG, NOT THINK YOU KNOW WHAT YOUR DOING THEN TRY WITHOUT FOLLOWING THE INSTRUCTIONS LIKE MY DAD PUTTING TOGETHER A COMPUTER DESK!!! THIS IS A EXPENSIVE PIECE OF HARDWARE SO FOLLOW MY EXACT STEPS!!!!!
The only 2 known issues ive had personally were
-no home button just 2 back buttons for the time being
-phone model specific apps for the T959D wont download from the market because you will be using a i9000 kernel to mimic the i9000 system
THE ONLY REQUIREMENTS ARE TO MAKE SURE YOUR BATTERY IS FULLY CHARGED AND YOU HAVE DOWNLOADED AND INSTALLED THE SAMSUNG USB DRIVERS
http://www.samsung.com/ca/consumer/...TLS/index.idx?pagetype=prd_detail&tab=support
I've Added a video of my current setup.. i was going to do a video showcasing the installation but i really dont want to redownload all my apps. far too time consuming.
STEP ONE - Download and reflash froyo 2.2 1st thing were gonna do is reflash stock 2.2. i know most of u r already on stock 2.2 but a fellow tester by the name of roccos_van said he was having market issues. So i wanna be 100% careful. So lets flash to stock. TO start, download the omega 2.2 leak here: http://www.megaupload.com/?d=C3DQ1LZF
the leak comes with odin and all files needed to flash back to 2.2 stock. Once the download is complete, unzip the file to somewhere your familiar with ie. desktop or my documents. The files name will b T959TJL3. inside this file, youll find odin and 3 files. Right click odin and click start as administrator. Odin has a fairly simple setup. the thing u wanna do in odin is place the files from the
T959TJL3 folder into the proper catagories. Heres a screenshot of what it should look like when its properly setup
once your odin looks EXACTLY THE SAME, its time to put your phone into download mode.
Turn off your phone and wait for it too completely power down. once its completely off, pull your battery. SGS phones come with a hidden mode called download mode which is what the phone goes into when you recieve a OTA update. to manually put your phone into download mode, follow these instructions
MAKE SURE YOU USE THE SAMSUNG CABLE THAT CAME WITH YOUR PHONE!!
make sure u have your samsung usb cable plugged into the pc but not into the phone (not yet at least) and make sure u remove your battery.
step 1. hold down the volume down button and continue holding
step 2. whille still holding down the volume down button, plug your phone into the usb cable
step 3. while still holding down the volume down button, pop your battery in.
Your phone should show this screen
Now if u look at odin you will have a yellow stripe on the top left area as seen in this picture
Now your ready to flash to stock 2.2. In odin, click start. It will then begin flashing the stock firmware into the phone.
It will look something like this
After afew minutes, it will reset your phone and odin will look like this but will say reset instead of pass
let your phone sit for while untill odin looks like this
once it says pass, your officially back to stock 2.2. CONGRATZ!!! step1 complete!
Now onto the i9000 kernel
STEP 2 - DOWNLOAD AND INSTALL CUSTOM VOODOO i9000 KERNEL
1st off, download the custom kernel here
http://rapidshare.com/#!download|30...stable-5.0.1-Froyo-GT-I9000-odin-pda.tar|6461
This kernel has clockwork recovery enabled which allows you to flash new roms, make backups, etc.
once the file is done downloading, reopen odin and place the file in to PDA section and do nothing else!!
Put your phone back into download mode following the steps above until your ready to flash. Once your ready to go, click start. It will only take like 10 seconds this time around since your only flashing a kernel.
When your phone resets, it will say 959d then quickly change to i9000 and then it will begin to talk to you! lmao. dont fret, its supposed todo this. its installing the voodoo lagfix in your phone. this will take approx 5-10 minutes. once your phone is up and running, let it sit for about 5 minutes so it can finish installing the lagfix. Once your phone is up and running again, power it down. Wait for it to be completely off, then we are going to get into recovery mode.
To get into recovery mode, hold down both volume buttons and hold power. Continue holding these 3 buttons until your phone loads the i9000 bootscreen for the 2nd time then release.
You should b in a screen resembling this but yours will be red
To navigate recovery, you must use the volume buttons for up and down and power for enter.
From the main menu, go down to lagfix and click enter.
in this menu, u can enable or diasble the voodoo lagfix. Since we want to flash a new rom, WE MUST TURN OFF VOODOO!!!
YOU MUST ALWAYS TURN OFF VOODOO BEFORE FLASHING ANYTHING OR YOU CAN POTENTIALLY BRICK YOUR PHONE!!!
once youve clicked disable lagfix, disable system lagfix and disable debug lagfix, go back to the main menu then click reboot.Againm, it will take like 5-10 minutes to completely disable the lagfix. Once its completely done disabling the lagfix, your phone will load. You wont have signal to telus quite yet, but we will get to that. From this point, u can choose what u want to do.
U have 3 options
1. Install a vibrant rom
2. Install a i9000 rom or
3. Flash The telus modem and stay stock
But since this is a tutorial on how to get a custom rom up and running, ill choose a rom. On to step 3!
STEP 3 - CHOOSING AND FLASHING A CUSTOM ROM
If u want my opinion, if u choose vibrant rom, choose Nero v5
Nero v.5: http://www.teamwhiskey.com/DownVibrant.html
If u choose a i9000 rom, id say darkys v8.1.
Darkys v8.1: http://www.multiupload.com/SHPR3TXLYB
Either choice you make, download the file to a familiar place on your computer.
On your phone, goto Settings > Applications > Development and turn on USB debugging.
Once the download is complete, connect your phone to your computer. Once your phones signals it knows its connected to the computer, pull down your notification bar and click USB CONNECTED. This will open up the Mass storage. Then click enable usb storage.
Now your computer and phone are able to communicate and share files. click my computer then you should see your phone named removable storage. Open the device. Now you want to drag and drop the custom rom zip into the root of your internal storage. once its finished copying the zip, click close usb storage on your phone then unplug it once it says its ok. Now you have the custom rom on your phone but its not installed quite yet.
IF U CHOSE NERO v.5: NERO HAS A VIBRANT KERNEL PREINSTALLED WHICH WILL NOT ALLOW A TELUS FASCINATE TO CHARGE! IT WILL BOOTLOOP UNTIL U UNPLUG YOUR CHARGER. WE WILL B OVERWRITING THE VIBRANT KERNEL WITH A I9000 KERNEL FURTHER INTO THE TUTORIAL SO DONT START THINKING NEGATIVE! IT IS A SIDEAFFECT OF PORTING A VIBRANT KERNEL. ONCE WE HAVE THE ROM WORKING, WE WILL BE RE-ADDING ANOTHER I9000 CUSTOM KERNEL TO FIX THIS ISSUE. SO JUST CONTINUE WITH THE INSTALLATION
IF U CHOOSE DARKYS: NO ISSUES HERE BECAUSE IT IS A I9000 KERNEL. BUT I PERFER THE LOOK OF NERO V5 SO THE ADDED BULLS**T TO GET IT WORKING PROPERLY IS DEFINATELY WORTH IT!!
To install the custom rom you chose, follow these instructions:
1. Turn off phone and wait till its completely shutdown
2. Use the above mentioned 3 button combo to get into recovery
3. Once in recovery, click wipe data/factory reset. once it finshes, click wipe cache partition. Once it finishes, goto advanced then wipe dalvik cache.
4. After youve wiped everything, go back to the main menu and click install zip from SDcard. Then click choose zip. u should see your nero 5 - voodoo file. click it. it will ask if your sure. click yes. your rom will then proceed to install. you will see some wierd stuff but it will load perfectly. once its done, click reboot.
Because both Roms come with Voodoo enabled, you will have to sit and wait while voodoo reenables itself. once your rom is up and running, you probably still dont have a signal from telus and depending on which type of rom u chose, u may not be able to charge your battery. This is exactly y i said make sure your battery was fully charged. Im quite sure both of these roms come with enter recovery mode by holding your power button and it will say recovery. click that.
Once in recovery, your going to want to disable the lagfix, system lagfix and debuglagfix. Once youve disabled all of them, reboot. Again, it will take like 5 minutes to disable the lagfix. Once its done, shut down your phone entirely.
Now that the rom is installed, Step 3 is complete! Congratz! We are almost done!!
STEP 4 - OVERCLOCKED KERNEL & TELUS MODEM
The final steps to have your phone up and running is to flash a new advanced voodoo kernel that is overclocked and allows undervolting for better battery life (as well as fixes the charging bootloop issue on a vibrant rom) and reflashing the telus modem file so you can get signal again.
Click the following link and download this file:
voodoo.advanced.v666.2-20110111-21.53.tar
http://kernel.1ug.org/
Once the download is complete, reopen odin and place the voodoo.advanced.v666.2-20110111-21.53.tar in the pda file and thats it!!
get your phone into download mode and click start in odin. This will flash the stable kernel to your phone and allow you to overclock and undervolt. If u chose Nero v.5, plug your phone in for a charge, it deserves it Finally to get your telus signal back up and running.
Shut down your phone completely. Open odin (for the final time :0). You remember the T959TJL3 folder we used to first restore to stock froyo 2.2 in step 1 (also the folder odin is in)? Well what we want to do is take the file with the word "phone" in it and place it in the phone section and thats it thats all!! Get your phone back into download mode and click start in odin. this shouldnt take very long as your just exchaging the nero modem for the telus.
Once the flash is complete, BAAAMMMMMM BABYYYY!!!! custom roms!!!!! WITH WORKING DATA!!! ON A TELUS FASCINATE!!!
Now that your successfully running a custom rom, i suggest going back into recovery and re-enabling lagfix, system lagfix and debug lagfix then rebooting. After the reboot, i suggest re-opening recovery then going to backup and restore then clicking backup. This will create a system image of your freshly loaded rom so if u have issues down the line, u can easily restore back to your freshly loaded rom problem free. I THINK THIS IS DEFINATELTY A NECCESITY!!! BETTER SAFE THEN SORRY!!! IF NOT YOULL HAVE TO START FROM STOCK 2.2 ALL OVER AGAIN!!!
(OPTIONAL): HOW TO OVERCLOCK AND UNDERVOLT
Overclocking your phone is super easy considering once youve added the advanced voodoo kernel its automatically overclocked but you cant control it. I suggest going onto the market and purchasing SETCPU. Its pritty cheap, comes with a widget, and allows you to choose the max cpu speed (overclocked its 1.28ghz) and the minimum. I only overclock when im playing psx4droid v1.7 (final fantasy 9 runs mint) but usually keep my cpu set at 600mhz max 200mhz min while im doing my day to day to preserve battery life but also keep the speed.
SETCPU HAS ISSUES ON GALAXY S PHONES WITH THE SET TO BOOT OPTION AND SAVING PROFILES. DO NOT USE SET TO BOOT OR PROFILES!!! JUST CHANGE THE CPU SPEED MANUALLY WHEN YOU WANT TO CHANGE IT OR YOU COULD SERIOUSLY MESSUP YOUR PHONE
Undervolting is pritty easy also. just go checkout Xan`s app: voltage control v.3.
Heres a link to his thread and the the download link for the apk is at the bottom of his post:
http://forum.xda-developers.com/showthread.php?t=829731
Either download this file directly to your phone or download it to your computer then use usb storage to drag and drop the apk into the root of your internal sdcard. Close your usb storage and unplug phone. Open your custom roms file manager and find the apk. Click it. Use program installer to install it.
Once its installed open the app. Superuser will ask you if its allowed to allow voltage control to work. Click yes. You will then see a list of voltages etc.
1st thing you should do is change your scheduler to noop. Its the best scheduler in the app and easiest on your phone.
I`m going to paste stable undervolting values you should copy into your voltage control.
1280 = -25
1200 = -25
1120 = -25
1000 = -50
900 = -50
800 = -50
600 = -50
400 = -75
200 = -75
100 = -75
These settings have worked perfectly for me although you could try different settings. Once youve added the above values into voltage control, click the menu button and click apply now. then click menu again then apply now again (i heard it takes 2 times to actually go through). The values i put there are safe so if you followed those, open menu and click apply to boot, then menu then apply to boot. Your phone is now undervolted.
I just spent roughly 9 hours creating this post so if it has helped you in anyway possible, plz click thank you. I'd like to thank supercurio for creating voodoo, omega1 for creating my interest in custom roms with faded froyo, and roccos_van for testing what everyone else was afraid to test. Id also like to thank everyone reading this post. Plz click the thank you button
The market issue is fixed, it had nothing to do with your instructions, I have a bad imei and simply had to force stop a few market related apps, clear data and cache then reboot.
You should also update your post as user supercurio released a custom t959d kernel today with clockwork and voodoo.
Now we can flash roms for i9000 or t959 with no issues.
just my luck. spend 9 hours posting then supercurio posts a kernel.. lmao. o well. if your looking for a overclocked undervolted phone, follow this post
roccos_van said:
The market issue is fixed, it had nothing to do with your instructions, I have a bad imei and simply had to force stop a few market related apps, clear data and cache then reboot.
You should also update your post as user supercurio released a custom t959d kernel today with clockwork and voodoo.
Now we can flash roms for i9000 or t959 with no issues.
Click to expand...
Click to collapse
ill b updating my post to include instructions on flashing stock 2morop morning when i got some free time
EDIT: so i think my battery is finally syncedup properly. i have no task killers with the above setup. Charged my phone yesterday at 1pm. Its now 7:30am the next day and i have 51 percent left
You did a good job with the post.
I think when you add the supercurio modded stock kernel it will be fairly complete.
roccos_van said:
You did a good job with the post.
I think when you add the supercurio modded stock kernel it will be faily complete.
Click to expand...
Click to collapse
i was just in the shower with my phone playing music on the counter and it stopped playing. i jumpedout to see wtf was going on. the lockscreen just magically appeared saying sim card removed reboot phone. seems to be working now but fuk it. thats too messed up 4 me. imma re edit this thread to include the telus voodoo stock so no1 gets the same issues im hjaving. overclock undervolt or not, i hate glitches.
Im thinking ill return to stock and start from scratch. Should i make a video showing complete installation? i think so
LINKSLOVESANDROID said:
i was just in the shower with my phone playing music on the counter and it stopped playing. i jumpedout to see wtf was going on. the lockscreen just magically appeared saying sim card removed reboot phone. seems to be working now but fuk it. thats too messed up 4 me. imma re edit this thread to include the telus voodoo stock so no1 gets the same issues im hjaving. overclock undervolt or not, i hate glitches.
Im thinking ill return to stock and start from scratch. Should i make a video showing complete installation? i think so
Click to expand...
Click to collapse
Try the stock voodoo kernel first...i don't know if you should disable lag fix first but I would just in case.
roccos_van said:
The market issue is fixed, it had nothing to do with your instructions, I have a bad imei and simply had to force stop a few market related apps, clear data and cache then reboot.
You should also update your post as user supercurio released a custom t959d kernel today with clockwork and voodoo.
Now we can flash roms for i9000 or t959 with no issues.
Click to expand...
Click to collapse
Thanks for the tip, my market stopped working today, cleared data and cache, rebooted and now I'm back in action!
well headsup telus users. i flashed axura on my fascinate and it completely bricked my phone. wont turn on. no recovery no download mode. i tihnk im screwed
LINKSLOVESANDROID said:
well headsup telus users. i flashed axura on my fascinate and it completely bricked my phone. wont turn on. no recovery no download mode. i tihnk im screwed
Click to expand...
Click to collapse
Oh man...that sucks...did you disable voodoo before flashing? You have a one year warranty take it back.
LINKSLOVESANDROID said:
i was just in the shower with my phone playing music on the counter and it stopped playing. i jumpedout to see wtf was going on. the lockscreen just magically appeared saying sim card removed reboot phone. seems to be working now but fuk it. thats too messed up 4 me. imma re edit this thread to include the telus voodoo stock so no1 gets the same issues im hjaving. overclock undervolt or not, i hate glitches.
Im thinking ill return to stock and start from scratch. Should i make a video showing complete installation? i think so
Click to expand...
Click to collapse
roccos_van said:
Oh man...that sucks...did you disable voodoo before flashing? You have a one year warranty take it back.
Click to expand...
Click to collapse
i did disable voodoo. dunno y it bricked. i went to the future shop i got it from, lied and said i flashed official froyo from kies and it wouldnt start afterward. They checked my account. turns out i was 3 days late on my replacement policy fee so i have 2 wait 3 business days with a paper weight phone until it goes through b4 they can replace it for me. but on the brightside, my buddy who works the cell area said when i get my replacement, if the same thing happens he has to give me the telus phone of my choice. SOO. if the htc desire hd does come to telus, i can purposely brick my phone, say froyo did it, and get the desire hd for free. although i dont know much about htc, ive heard they r the best android brand around. u got any info on htc at all rocco? all i know is sense looks sexier then any rom ive seen thus far including every differenty model rom ive seen on youtube. imma post a new thread warning t959d users to beware on flashing roms until there propp[erly ported to our phone. cause as u can see in the above post, i know what i was doing. wasnt like i just fukedup and forgot something. i had nero v5 running with the supercurio stock voodoo kernel last night but it felt like it was hiccuping after i enabled the lagfix so i decided to go back to stock and try other roms. from what i heard, axura is the best of the best for vibrant roms. so i flashed to stock with odin. added the new kerne; thru odin, let the lagfix install, rebooted into recovery, disabled the lagifx, system lagfix and debug. rebooted. let the lagfix uninstall. copied the zip to my interna; sdcard, rebooted into recovery, wipe data, cache and dalvik then chose the zip. it installed properly. i clicked reboot phone then it turned off. and that was that. question is is there anyway to use slp to open your phone and try and reset it or is it bricked and am i without a phohe till next wednesday?
LINKSLOVESANDROID said:
i did disable voodoo. dunno y it bricked. i went to the future shop i got it from, lied and said i flashed official froyo from kies and it wouldnt start afterward. They checked my account. turns out i was 3 days late on my replacement policy fee so i have 2 wait 3 business days with a paper weight phone until it goes through b4 they can replace it for me. but on the brightside, my buddy who works the cell area said when i get my replacement, if the same thing happens he has to give me the telus phone of my choice. SOO. if the htc desire hd does come to telus, i can purposely brick my phone, say froyo did it, and get the desire hd for free. although i dont know much about htc, ive heard they r the best android brand around. u got any info on htc at all rocco? all i know is sense looks sexier then any rom ive seen thus far including every differenty model rom ive seen on youtube. imma post a new thread warning t959d users to beware on flashing roms until there propp[erly ported to our phone. cause as u can see in the above post, i know what i was doing. wasnt like i just fukedup and forgot something. i had nero v5 running with the supercurio stock voodoo kernel last night but it felt like it was hiccuping after i enabled the lagfix so i decided to go back to stock and try other roms. from what i heard, axura is the best of the best for vibrant roms. so i flashed to stock with odin. added the new kerne; thru odin, let the lagfix install, rebooted into recovery, disabled the lagifx, system lagfix and debug. rebooted. let the lagfix uninstall. copied the zip to my interna; sdcard, rebooted into recovery, wipe data, cache and dalvik then chose the zip. it installed properly. i clicked reboot phone then it turned off. and that was that. question is is there anyway to use slp to open your phone and try and reset it or is it bricked and am i without a phohe till next wednesday?
Click to expand...
Click to collapse
The only thing I can say is keep trying to get it into download mode? I had an HTC desire, I just sold it on ebay, and have the cash waiting for the Desire HD...so yeah, the HTC stuff is real nice. It's being released at TELUS on feb 10, for $499.
LINKSLOVESANDROID said:
i did disable voodoo. dunno y it bricked. i went to the future shop i got it from, lied and said i flashed official froyo from kies and it wouldnt start afterward. They checked my account. turns out i was 3 days late on my replacement policy fee so i have 2 wait 3 business days with a paper weight phone until it goes through b4 they can replace it for me. but on the brightside, my buddy who works the cell area said when i get my replacement, if the same thing happens he has to give me the telus phone of my choice. SOO. if the htc desire hd does come to telus, i can purposely brick my phone, say froyo did it, and get the desire hd for free. although i dont know much about htc, ive heard they r the best android brand around. u got any info on htc at all rocco? all i know is sense looks sexier then any rom ive seen thus far including every differenty model rom ive seen on youtube. imma post a new thread warning t959d users to beware on flashing roms until there propp[erly ported to our phone. cause as u can see in the above post, i know what i was doing. wasnt like i just fukedup and forgot something. i had nero v5 running with the supercurio stock voodoo kernel last night but it felt like it was hiccuping after i enabled the lagfix so i decided to go back to stock and try other roms. from what i heard, axura is the best of the best for vibrant roms. so i flashed to stock with odin. added the new kerne; thru odin, let the lagfix install, rebooted into recovery, disabled the lagifx, system lagfix and debug. rebooted. let the lagfix uninstall. copied the zip to my interna; sdcard, rebooted into recovery, wipe data, cache and dalvik then chose the zip. it installed properly. i clicked reboot phone then it turned off. and that was that. question is is there anyway to use slp to open your phone and try and reset it or is it bricked and am i without a phohe till next wednesday?
Click to expand...
Click to collapse
Best way I've found to avoid this is to unzip the ROM and take a look at the update script to see exactly what it's flashing. Some custom ROMs flash more then just the kernel and modem and modify things like the boot.bin, which is almost sure to brick your phone if it's not compatible.
To all Telus Fascinate T959D users, I have posted a complete guide to installing custom Vibrant ROM's.
The guide shows you how to install any ROM for the T-Mobile Vibrant (I prefer Team Whiskey's Nero 5), then flash a custom Telus Fascinate kernel with Voodoo and CWR built-in, and then finally flashing the stock Telus Fascinate JL3 modem.
This will leave you with a 100% functioning (yes, flawless) custom ROM on your Fascinate.
The reason I posted the guide, despite this one already existing, is that it doesn't require you to sacrifice certain functionality. The guide I have posted is only for flashing Vibrant ROMs, and uses supercurio's newly released T959D Stock+Voodoo kernel that is built on the Telus one, so everything works.
Themes
So I just followed samperlmutar's guide and installed the nero v5 rom. My question is now I'm having problems applying themes for Nero v5. I followed instructions to the T on the theme pages in the Vibrant section but it says it is not compatible. Anyone know if Vibrant Nero v5 themes will work on a Telus Fascinate?
This is a very informative post - thank you.
im very new to this my phone will not turn on completely i can get into download mode still but phone isnt functioning. I'm just trying to install 2.2 OS on it. Is anyone online that can help
crap
I have an issue. Everything was going great Step 1 complete. Step 2 the download was deleted from rapidshare. so I googled and downloaded the file from dl.project-voodoo.org
It failed. now the phone boots but only to a screen with a phone icon and a computer icon with a warning icon. so it wont boot, it wont connect to the pc and wont hard reset.
Any suggestions? Thanks.
Rick
still failing
merganser said:
I have an issue. Everything was going great Step 1 complete. Step 2 the download was deleted from rapidshare. so I googled and downloaded the file from dl.project-voodoo.org
It failed. now the phone boots but only to a screen with a phone icon and a computer icon with a warning icon. so it wont boot, it wont connect to the pc and wont hard reset.
Any suggestions? Thanks.
Rick
Click to expand...
Click to collapse
k well I got it back in download mode and odin 3 recognizes it but step 2 is still failing. any chance I can get that step 2 download?
Yeah it's pretty annoying how every guide I've tried to go through so far has broken links.

[Q] about to reset my phone

been having some problems with my phone lately and just wondered if anyone else has encountered these. first off it seems to stop playing any media files whatsoever. i have a bunch of music on it and the player just cycles through and says its not supported. youtube always brings up the error message that the video can not be played. i turn the phone off and on and it works after that but around 24 hours later i'm back to the same thing. also tried using kies to download the 2.2 update but that sucks and doesn't work. would like to root but have no idea where to begin and am afraid i'll screw the phone up. does anyone have an explanation as to what my problem can be and the best way to get 2.2 on this phone?
1st things 1st, Go to the noob guide by S15274N in the Gen section. It has all the info you need. Read it..........
Here is basically what you will do:
Make sure you have the Samsung USB drivers loaded on your computer (found in the noob guide)
Download superonclick to Root the phone (on to the computer)
On the phone download rom manager (from the apps store)
Follow the directions from superoneclick (look at unlockcr.com good how to video)
After you root the phone then decide what to load as far as a custom ROM. I would Try the Trigger or Axura, they both very stable Download on to the computer
Then hook up the phone on to the computer Make sure you connect the usb
(the pulldown at the top) make usb debugging is clicked.
Load the rom on to the Internal sd card and then go to the Rom manager and click reboot into into recovery.. install it wait 15 mins to install and you are good to go
READ the NOOB guide it is complete this is just an outline.
good luck
well i'll give it a read and see if i have enough balls to do it. thanks
ndavis_28 said:
been having some problems with my phone lately and just wondered if anyone else has encountered these. first off it seems to stop playing any media files whatsoever. i have a bunch of music on it and the player just cycles through and says its not supported. youtube always brings up the error message that the video can not be played. i turn the phone off and on and it works after that but around 24 hours later i'm back to the same thing. also tried using kies to download the 2.2 update but that sucks and doesn't work. would like to root but have no idea where to begin and am afraid i'll screw the phone up. does anyone have an explanation as to what my problem can be and the best way to get 2.2 on this phone?
Click to expand...
Click to collapse
I'm having these same exact problams and it is very frustrating. Also the video recorder will stop working I found.
So you are using 2.1? I've gone up to 2.2 using kies. I can't remember when I went to 2.2, but my guess is this has been happening since then.
In the past week I've been on the phone way too long with Tmobile support. They say that they have never heard of this (apparently I'm not the only one though) and had me try a master reset. That didn't work and the only solution seems to be to reboot the phone. Am I the only one who thinks having to reboot within 24 hours is ridiculous?
So now that they have sent me 3 phones, they directed me to Samsung which wanted to try the same Master Reset. I know that will only temporarily fix the problem so the next step is to send the phone in. How is that suppose to work? Have no phone for a week.
I guess I could ask Tmobile to do it for me and give me a loaner, but I think it is time to go with a custom ROM.
So is anyone else having the problems we are having? We can't be the only two. Is the stock 2.2 just bad and I will be better served with a custom ROM?
I was hoping to avoid this, but the phone is pretty much crap to me now anyway, so I guess what can I lose?
pmiller said:
So is anyone else having the problems we are having? We can't be the only two. Is the stock 2.2 just bad and I will be better served with a custom ROM?
I was hoping to avoid this, but the phone is pretty much crap to me now anyway, so I guess what can I lose?
Click to expand...
Click to collapse
IMO stock from samsung have never been very impressive especially when compared to all the custom roms out here. The simplest roms to flash will be the kb1 based roms such as Trigger, Axura or Bionix (in no particular order).
Your phone will feel completely different and you will likely gain a new found appreciation for it, so go flash a custom rom
shreddintyres said:
IMO stock from samsung have never been very impressive especially when compared to all the custom roms out here. The simplest roms to flash will be the kb1 based roms such as Trigger, Axura or Bionix (in no particular order).
Your phone will feel completely different and you will likely gain a new found appreciation for it, so go flash a custom rom
Click to expand...
Click to collapse
Thanks for the advice. After reading through the steps and getting lost at only the 2nd step of rooting, I think I'll just stick to stock and deal with the problems.
Not ideal, but I'm just not in the mood to put that much into a phone anymore. Maybe I'm just lazy, but I'd like to have a program that will do all the steps of getting a new ROM on my device. I feel overwhelmed by having to maintain a ROM.
Its not as hard as you think. Just use superoneclick to get root access, download rom manager , download the rom you want on your sd then reboot into recovery from root manager and chose your rom from the sd.
Sent from my Bi-Winning powered SGH-T959 using XDA App
pmiller said:
Thanks for the advice. After reading through the steps and getting lost at only the 2nd step of rooting, I think I'll just stick to stock and deal with the problems.
Not ideal, but I'm just not in the mood to put that much into a phone anymore. Maybe I'm just lazy, but I'd like to have a program that will do all the steps of getting a new ROM on my device. I feel overwhelmed by having to maintain a ROM.
Click to expand...
Click to collapse
Give this a look
http://forum.xda-developers.com/showthread.php?t=954509

Still on 2.1. Source says 2.3 is available for Galaxy S

I haven't been around for a while and could not quickly get up to date despite going through thread after thread here. I would appreciate some advice and clarification.
First, you guys are saying that GB won't be available for Vibrant, but this article clearly states that it is already available:
“update news! the android 2.3 gingerbread update for the samsung galaxy S vibrant is good to go. connect to samsung kies to hook it up.”
Could you please clarify? The problem is that I downloaded Keys 2.0, but my phone, which is 2.1 and rooted (nothing else done, no roms, etc), is not being recognized. Keys says that my phone isn't supported.
Could you guys please clarify what is really going on in terms of 2.3? Also, how can I get the update? Assuming that the article is false, many here say that 2.3 roms are battery hogs and it looks like I would have to update to 2.2 and then root it. If so, I'd appreciate a link to a pure 2.2 to be installed via Odin. Reading all these threads doesn't convince me that getting a rom, a modem, or a kernel really does that much to improve our phones.
Thanks!
Thats for the Bell/ Virgin Mobile Vibrant theres a difference ya know...
I thought that the phone is the same so it wouldn't matter or perhaps the devs could use it to create a better ROM. If not, I guess the situation is even worse because Samsung actually released the update for Vibrant but T-mobile is refusing to allow users to have it! Clusterf*ck. Steve Jobs was right about android when he talked about market fractionization last year. Oh well.
Ok, well given the bad news, I would appreciate some help from those of you who have flashed your phones to hell and back. I know there are different ROMs etc with different features. I don't use my phone heavily. Actually, the main feature I care about is 1.Good GPS and 2.Good battery life. I go on long cycling trips and my phone is the only thing I use to track my stats (sometimes five hours or longer).
Based on this info, could you guys tell me if upgrading to Android 2.2 be good enough or do any of the ROMs, kernels, and modems provide a clear advantage over stock 2.2? If so, could you recommend a few? Right now my phone is in a very bad shape - the GPS is often dying in mountains and the battery doesn't last much. At this point I have to upgrade just to clean up my phone, especially since it's not clear if/when 2.3 will be released. I am hoping that at least 2.2 should be very stable by now.
only thing in common is the name and the fact that they are both Galaxy S series phones, the canadian bell Vibrant is different hardware then our Vibrant.
I'd say go with something stable such as Bionix 1.3.1 or Trigger 3.2. If you wanna go with 2.2.1 go with a Darky ROM's port or Bi- Winning 3. All good ROMS I'd recommended. Regardless that's what I prefer pperhaps just play around with all types of ROM's you may like something else its not for me to decide.
Sent from my SGH-T959 using XDA App
i would suggest cm7 if u like gb its almost fully functitioning except gps is weak
Would you guys say that you have seen significant performance improvements (~30% or more) of ROMs over rooted stock 2.2? If so, have you also seen significant improvements by adding a kernel and/or a modem?
I know that it's not supposed to be too hard to flash and find out for myself, but I have never flashed anything and evaluating all the different combos can be quiet time consuming. Given that I work and study so much I barely have enough time to date, I was hoping that I could get some succinct advice that will cut my Android pains in half. I have read the thread about different modems and know that something like KB5 is a pretty good modem (still have no idea what it is or where do you get it and how you flash it); however, that thread missed one key comparison - the actual performance and battery improvement of a given modem (and even a kernel) over stock 2.2/2.3 or even over a ROM like Bionix. I'd appreciate any info/links regarding this.
Thanks.
Stop writing walls of text for no reason ... kernel will make your phone faster, particularly if you enable voodoo lagfix (helluvah lot faster >30% over stock)... modem will not make it faster but may make your data connection faster and battery last longer as well as morr signal ... look for the modem page for dl link....
Now go flash a rom!! All the roms here are amazing and huge improvements over stock, as are the kernels. Suggestions??? Print out all the names, put em on notecards and throw a dart... flash whatever you hit.
Sent from a cell tower to the XDA server to you.
Bell vibrant is completely different from ours ... the 2.3 for them is no help to us.. lol were not lying to you
Sent from a cell tower to the XDA server to you.
None of the Gingerbread roms are anywhere near where some of the Froyo roms are.
Team Whiskey Bionix 1.3.1 is the best I've used. NextGen V2 isnt' bad either. I just tried Simply Honey 5 RC1 and CM7 nightly #84. Out of the 4 roms I just listed, I flashed back to Bionix 1.3.1. It has the best speed and is the most stable I've ever used.
If you don't have the time to read about flashing your phone, I would suggest you either not do it or pay someone to do it for you. Set aside 2-3 hours if you want it done properly otherwise say goodbye to your phone.
I am in SoCal too and wouldn't mind paying someone to do it for me. The problem is then a whole other set of headaches: how do you trust someone to get hold of your private info? What about doing a good job? Arranging a pickup/dropoff, etc, etc. Also have no idea how much people charge for this service. Expensive enough and it might just be worth it to get a new phone, especially after I sell the Vibrant. Maybe that's what many of us need to do.
Im sure you can find someone nearby thatll do it as a favor and let you watch... problem solved
Sent from a cell tower to the XDA server to you.
I would never pay anyone to flash anything for me. Its a simple process.
To figure out what ROM's go good with what Modem I would go to this thread http://forum.xda-developers.com/showthread.php?t=959088 and a good kernel would be Bali or SuperDragonModz both great.
Excelsius said:
I am in SoCal too and wouldn't mind paying someone to do it for me. The problem is then a whole other set of headaches: how do you trust someone to get hold of your private info? What about doing a good job? Arranging a pickup/dropoff, etc, etc. Also have no idea how much people charge for this service. Expensive enough and it might just be worth it to get a new phone, especially after I sell the Vibrant. Maybe that's what many of us need to do.
Click to expand...
Click to collapse
I recommend listening to some of the other folks in the thread and flash bionix 1.3.1. The stock kernel is fine, as is the modem it ships with. Battery life will be as good as just about anything else.
If you really want to flash a custom kernel, go with Bali 1.8.8. Battery life will be similar, but that kernel has some additional features like voodoo sound, which uses the audio hardware more effectively. If that doesn't seem like something you care about I wouldn't worry about it.
The only catch is that you will need to flash bionix through CWM recovery, there are no prepackaged odin files that I am aware of. There are numerous threads to help you getting CWM installed, just check out the stickies.
Don't pay anyone, if your still not comfortable flashing anything, but you still really want to, PM me and I'll help you through it.
Thank you so much for the more precise advice. That's exactly what I needed. It's not that I want to upgrade, but rather that I have to because my phone has become unstable. It freezes almost every time I open Voice or Maps, among other problems.
So I will get the Bionix 1.3.1 and worry about Bali 1.8.8 at a later time. I came across this guide: http://forum.xda-developers.com/showthread.php?t=925400
Is it the guide for CWM? My phone is rooted (ODIN) and has paid version of Root Explorer and BusyBox. I was wondering if I still have to install SuperOneClick or if my root is fine already.
By the way, I'd appreciate a link to some guides that you guys have used to install your Bionix. I read this: http://forum.xda-developers.com/showthread.php?t=732458, but the CWM and Rom Manager points are moot. Like I don't know if installing Rom Manager already includes CWM with it. Here are the steps:
Installation instructions:
1.Download ROM Manager from the Market.
2.Flash Recovery.
3.Choose Vibrant as your phone.
4.Accept the Superuser prompt.
5.On the very FIRST boot of Clockwork, you may need to manually select "reinstall packages" if Clockwork does not start. You should only ever have to do this once. It will be automatic from then on.
6.Watch the backup go!
If this is it, then I'll just do it (after I do a nandroid backup, which will hopefully backup all my paid applications).
I'm in SoCal, running Cyanogen7 nightly 81. (Android 2.3)
I am running Bali, and did both the hardware GPS fix, and the software GPS fix using the terminal scripting.
I get around 10-12 locks, accuracy tends to be in the 12-14 foot range, so the GPS works flawlessly.
I've been a lurker on these forums for a LONG time now, but decided to register and post to kinda give back. In this case, to someone looking to fix up their Vibrant.
If you're interested, PM me. I work for Microsoft, and you're welcome to stop by and I'll show you everything I've done. (Yes, I have an Android phone, and a WP7 phone, both of which I love) If you like what you see, (You will) I'll set your phone up as my way of kinda returning all of the favors other users on this site have done for me, even though they didn't know it.
Excelsius said:
Thank you so much for the more precise advice. That's exactly what I needed. It's not that I want to upgrade, but rather that I have to because my phone has become unstable. It freezes almost every time I open Voice or Maps, among other problems.
So I will get the Bionix 1.3.1 and worry about Bali 1.8.8 at a later time. I came across this guide: http://forum.xda-developers.com/showthread.php?t=925400
Is it the guide for CWM? My phone is rooted (ODIN) and has paid version of Root Explorer and BusyBox. I was wondering if I still have to install SuperOneClick or if my root is fine already.
By the way, I'd appreciate a link to some guides that you guys have used to install your Bionix. I read this: http://forum.xda-developers.com/showthread.php?t=732458, but the CWM and Rom Manager points are moot. Like I don't know if installing Rom Manager already includes CWM with it. Here are the steps:
Installation instructions:
1.Download ROM Manager from the Market.
2.Flash Recovery.
3.Choose Vibrant as your phone.
4.Accept the Superuser prompt.
5.On the very FIRST boot of Clockwork, you may need to manually select "reinstall packages" if Clockwork does not start. You should only ever have to do this once. It will be automatic from then on.
6.Watch the backup go!
If this is it, then I'll just do it (after I do a nandroid backup, which will hopefully backup all my paid applications).
Click to expand...
Click to collapse
If you already have ROM manager, and have "Flashed Recovery" then you have Clockwork Mod. At this point, should be able follow the Bionix instructions after the CWM point.
Nandroid backs up EVERYTHING, including the Android OS version you are running. If you want to back up just your apps, use Titanium Backup, the premium version lets you do a "One touch" batch restore of all user apps. One thing to remember about Titanium: do NOT back up system data. Easiest rule of thumb for it, "Menu--> Batch--> backup all user apps" then let it do it's thing. flash your ROM, then go into Titanium (Almost positive the free version is part of Bionix) "Menu--> Batch--> Restore missing apps with data" If you have the premium version, you can restore them all with no further input, if you have the free version, you will have to accept and install each app as you go, but they all come back with your saved data.
If you are going to do a FULL wipe (Format storage so the phone is empty) first connect to USB Storage, and move your "Titanium Backup" folder from the root of your internal SD card to your PC. Then, before you run titanium for the first time after wiping, reverse the process. Apps are back.
Excelsius said:
Thank you so much for the more precise advice. That's exactly what I needed. It's not that I want to upgrade, but rather that I have to because my phone has become unstable. It freezes almost every time I open Voice or Maps, among other problems.
So I will get the Bionix 1.3.1 and worry about Bali 1.8.8 at a later time. I came across this guide: http://forum.xda-developers.com/showthread.php?t=925400
Is it the guide for CWM? My phone is rooted (ODIN) and has paid version of Root Explorer and BusyBox. I was wondering if I still have to install SuperOneClick or if my root is fine already.
By the way, I'd appreciate a link to some guides that you guys have used to install your Bionix. I read this: http://forum.xda-developers.com/showthread.php?t=732458, but the CWM and Rom Manager points are moot. Like I don't know if installing Rom Manager already includes CWM with it. Here are the steps:
Installation instructions:
1.Download ROM Manager from the Market.
2.Flash Recovery.
3.Choose Vibrant as your phone.
4.Accept the Superuser prompt.
5.On the very FIRST boot of Clockwork, you may need to manually select "reinstall packages" if Clockwork does not start. You should only ever have to do this once. It will be automatic from then on.
6.Watch the backup go!
If this is it, then I'll just do it (after I do a nandroid backup, which will hopefully backup all my paid applications).
Click to expand...
Click to collapse
The steps you listed are correct. You also of course need to have downloaded the bionix 1.3.1 zip file and placed it somewhere on your SD card (I make a ROMS folder on mine). As the instructions noted, you'll have to do reinstall packages twice (ie you do it once and the phone reboots into recovery and it looks like nothing happened, you do it again and go immediately to CWR recovery where you can select "install ROM from SD" or similar). From this point on you won't have to worry about CWR recovery, it will always be there. As StarGazer mentioned, when you flash this it will wipe your phones settings and all the apps (but not the SD card). There are a variety of backup apps that can help restore them, but I usually don't mind starting fresh once in a while, especially if your contacts are stored on Google.
Finally, once the bionix finishes flashing and the phone reboots for the first time, expect to hear a voice start talking to you about backing up partitions, estimated times, etc. This is the "voodoo lagfix" being applied, which is converting internal phone partitions from the Samsung RFS to ext4, which noticeably reduces lag on the phone when opening apps and so forth. Good luck
Thank you for your help, everyone. I was able to dedicate a few hours and just take care of it since it didn't feel right to waste someone else's time. Please note that I haven't PMed anyone and if there are readers here who are technologically challenged, perhaps they can take my place and get help from some of the generous people who offered help here.
I currently have Bionix 1.3.1, Bali 1.8.8, and KB5.
To give back to the community, I wanted to post benchmarks. I have some amazing results:
Android 2.1 (everything stock, rooted) - Quadrant benchmark 852 (average of 2 tests)
Bionix 1.3.1 (with stock kernel) - 1504 (average of 3 tests). That's a 43% improvement! Now this is likely due to Android 2.2 rather than Bionix. It's definitely worth going from 2.1 to 2.2.
Bionix 1.3.1 + Bali 1.8.8 (after adding the kernel) - 1852 (average of 3 tests). That's 19% more than stock 2.2 and 54% more than 2.1! This isn't 30%+ improvement that some people here think kernels provide, but ~20% is still not bad, considering that battery life is also very important.
Now as far as the KB5 modem goes, I saw no improvements using GPS Test and Speed Test. My GPS is still at about 50ft accuracy and internet speed is 6000x2300kbps. The real test will come during my 60 mile ride on Saturday.
Right now I am only hoping that the battery will last at least as long or more than on 2.1, despite the kernel.
Question: before flashing with Bionix I had applied the software GPS fix to my phone a year ago. Do I have to do it again or does Bionix already include the software tweak?
Once again, thanks everyone.
P.S: My clock on the phone is off by two minutes from the atomic clock. I noticed that the "Autoupdate" of date and time message doesn't appear when I start the phone. Is there a time syncing issue with Bionix?

[GUIDE] Flashing ROMs to the Vivo Air

Alright, so following some prodding, searching, and questioning, I flashed MIUI V6 to my BLU Vivo Air alongside TWRP.
I will update this post with a detailed, step-by-step guide including my own personal mirrors for your convenience and those of you without 4PDA accounts, which is the Russian equivalent of XDA.
Upon booting, I noticed apps force closing without being launched. Namely Hangouts and Newsstand. I'm sure reinstalling them will resolve the issue rather quickly.
Stay tuned for updates.
Update 1:
TWRP had difficulty mounting data and cache for me, and was unable to format them. This led to applications force closing, window mishaps, and accounts glitching out. I just flashed Carliv recovery, and flashed MIUI with it. Flashing gapps at the moment, and will update you on my progress.
Update 2:
Currently attempting to format data (success), cache (success), and dalvik (success).
Update 3:
Rebooting into MIUI V6, checking if I've entered a bootloop.
5 seconds - Boot animation reached, "MIUI Pro."
165 seconds - Still booting.
180 seconds - Setup screen reached, MIUI V6 flashed successfully.
Update 4:
Google apps flashed successfully, no redraws or force closes this time. Had an issue with the keyboard not registering as being selected, Google voice typing appeared as the default. Pull down notification shader and "choose input method" to select MIUI Smart Keyboard. Signed into Google successfully. Will run preliminary tests on video playback, camera, and multitasking.
Guide:
If you mess up your phone, it is on you, and I am not to be held liable for your actions. This is your responsibility. A lack of planning on your part does not constitute an emergency on mine. With that out of the way, if you encounter troubles, I am more than happy to help you.
Step 1:
Root your phone using one of the links provided. Click HERE for method 1, or HERE for method 2. I personally used method 1 because it was the first I saw. They both get the job done.
Step 2:
Install THIS application (Settings -> Security -> Unknown Sources), and install a recovery. I installed Carliv recovery, and had no problems with it. You can also install TWRP, however, it had issues mounting data and cache. This left it unable to factory reset when I flashed MIUI, which subsequently led to problems. I do not recommend flashing TWRP - You have been warned. Carliv recovery says it can't "mount" cache, although when formatting it does so without a problem. I believe Carliv is supposed to be touch-based, although the touches weren't responding for me. The controls are as follows: Volume +/- for navigating, Power for selecting, and the Back key for, you guessed it, going back.
Step 3:
Install MIUI V6, located HERE, and then install Google Apps, located HERE. After installing, factory reset the device from recovery and reboot into the system. I posted my timestamps at the top of the post, so you can get an idea of how long your flash/boot process should take.
Step 4:
Basic setup. Be ready to fix your keyboard if you had the same issue I did, which isn't even necessarily a problem. Choose WLAN network and sign into your accounts, then you're good to go.
To root the ROM, I recommend finding "iRoot" for your computer. Then boot to recovery and install the SuperSU zip, as it's better than the root app which comes with the iRoot method.
Enjoy your ROM, and be sure to thank our Ruski comrades over at 4PDA!
Special thanks to @DvDwx. (research), @itsJohnuno (answers), and @Milly7 (testing).
All download links are being hosted by me, and I recommend creating mirrors of your own as safety precautions in the event that the files are removed or become unavailable.
Have a phenomenal day or night, possibly even both. If you have any questions, I'll do my best to answer them.
Nice Guide ;D
DvDwx. said:
Nice Guide ;D
Click to expand...
Click to collapse
Push that Guide to Android Development thread, that is a ROM ;D
We need talk with our Forum Administrator to Manage some Topics and Fuse KAZAM Tornado 348 with BLU Vivo Air menu... and try explain to this administrator about the re-branding process to he can add the other phones like AllView, Fly and Gionee to this Phone Menu Threads topics ;D
:highfive:
DvDwx. said:
Push that Guide to Android Development thread, that is a ROM ;D
We need talk with our Forum Administrator to Manage some Topics and Fuse KAZAM Tornado 348 with BLU Vivo Air menu... and try explain to this administrator about the re-branding process to he can add the other phones like AllView, Fly and Gionee to this Phone Menu Threads topics ;D
:highfive:
Click to expand...
Click to collapse
I didn't create the resources in the ROM, I just made a guide to flashing ROMs using a specific ROM as an example. I would feel bad posting it in the developer section because I don't wish to be given credit for the ROM. I didn't make it.
Ilxaot said:
I didn't create the resources in the ROM, I just made a guide to flashing ROMs using a specific ROM as an example. I would feel bad posting it in the developer section because I don't wish to be given credit for the ROM. I didn't make it.
Click to expand...
Click to collapse
i understand that ;D
on my WonderMedia WM8880 Tablet project i share the projects from other developers... but i asked they to have permission to share that, and leave on post the credits with their names... maybe if you talk with developer on 4PDA for permission to do it or ask him if it is possible he share he ROM Project here is will be perfect... anyway Good Guide to Flash this ROM :highfive:
Could you please describe how to flash the carliv recovery. I downloaded the app in step 2 but I can't even seem to install the twrp recovery because phone reboots into stock recovery and I don't even see an option for the carliv one.
dimasp6 said:
Could you please describe how to flash the carliv recovery. I downloaded the app in step 2 but I can't even seem to install the twrp recovery because phone reboots into stock recovery and I don't even see an option for the carliv one.
Click to expand...
Click to collapse
You need have root to do this... And sometimes the root dont work correctly and dont stay giving the rights to aplicantion can work...
DvDwx. said:
You need have root to do this... And sometimes the root dont work correctly and dont stay giving the rights to aplicantion can work...
Click to expand...
Click to collapse
I do have root with Kingroot. So I just need to keep trying until it successfully flashes?
Edit: The app mlp RIO recovery installer constantly freezes on me not allowing me to flash any of the recoveries.
dimasp6 said:
I do have root with Kingroot. So I just need to keep trying until it successfully flashes?
Edit: The app mlp RIO recovery installer constantly freezes on me not allowing me to flash any of the recoveries.
Click to expand...
Click to collapse
You can also try iRoot. Install SuperSU and try using it as the root granter for the recoveries.
Does the magnetometer (compass) work for you guys on the miui rom? It doesn't work for me.
ron580 said:
Does the magnetometer (compass) work for you guys on the miui rom? It doesn't work for me.
Click to expand...
Click to collapse
The app itself hadn't worked for me, I tried it earlier. Have you tested another app? It may be the stock app. I haven't messed with it much, not a huge navigator myself. [emoji14]
Ilxaot said:
The app itself hadn't worked for me, I tried it earlier. Have you tested another app? It may be the stock app. I haven't messed with it much, not a huge navigator myself. [emoji14]
Click to expand...
Click to collapse
The senor doesn't work at all using this rom & google maps wont work properly without it. Also the time on the lock screen and the home screen show different times about an hour apart Other than that everything else works fine.
ron580 said:
The senor doesn't work at all using this rom & google maps wont work properly without it. Also the time on the lock screen and the home screen show different times about an hour apart Other than that everything else works fine.
Click to expand...
Click to collapse
Yeah. I've also noticed that downloading updates is botched, because it downloads an update for a different phone model. If you try to install it the installation will fail, but it won't hurt your phone.
All in all it's a pretty solid ROM for me.
Ilxaot said:
Yeah. I've also noticed that downloading updates is botched, because it downloads an update for a different phone model. If you try to install it the installation will fail, but it won't hurt your phone.
All in all it's a pretty solid ROM for me.
Click to expand...
Click to collapse
Yes its a great rom maybe we can ask the developer if he can fix the issues for us on 4pda. I would do it but i couldn't register on 4pda i kept on receiving an error.
request
Ilxaot said:
All in all it's a pretty solid ROM for me.
Click to expand...
Click to collapse
Known bugs? any screenshot running this ROM please? I'd like to see some, I'm not updated on what's going on with MIUI and btw, great work! thanks in advance!
JesusEMC said:
Known bugs? any screenshot running this ROM please? I'd like to see some, I'm not updated on what's going on with MIUI and btw, great work! thanks in advance!
Click to expand...
Click to collapse
I'll post some tomorrow. Re-read the past 5-6 posts and you'll see the bugs. I think you'll like it. MIUI is certainly different (settings default apps) and such, but it's a formidable ROM and performs relatively well.
ron580 said:
Yes its a great rom maybe we can ask the developer if he can fix the issues for us on 4pda. I would do it but i couldn't register on 4pda i kept on receiving an error.
Click to expand...
Click to collapse
on Captcha you need count the numbers and ignore the russian Letters Like for exemple -> ##22###16## -> 22+16= 38
to can finish the registration... and no, you don't need use VPN or Proxy to create the account :highfive:
ron580 said:
Yes its a great rom maybe we can ask the developer if he can fix the issues for us on 4pda. I would do it but i couldn't register on 4pda i kept on receiving an error.
Click to expand...
Click to collapse
I'm sure he knows about it...and the guy is activity working on the ROM...except the latest update seems to just boot loop from what I've read, rather just wait and see.
itsJohnuno said:
I'm sure he knows about it...and the guy is activity working on the ROM...except the latest update seems to just boot loop from what I've read, rather just wait and see.
Click to expand...
Click to collapse
Our Buddy @SSJGohon found the kernel source code and already shared on some topic(i Already re-shared that on Cyanogen Mod to Mediatek SoC's Development thread... but anyone there say nothing about it... and already shared on 4PDA to maybe the MiUi developer can Bring something to All...). i already downloaded and already start my research about what can be maked with that and for sure have a possibility to we have a custom Kernel and maybe Custom ROM like PURE AOSP, AOSPA... but Cyanogen Mod is more difficult because we don't have a updated Repo Source from MediaTek to work like Driver Blobs to GPU, Bluetooth, Wifi Drivers... etc
My real problem is i don't have all skills to make a custom kernel to Mediatek SoC because a lot of things change from Qualcomm to Mediatek.. but if anyone here want to try development that just search the topics with @SSJGohon comments replays :highfive:
Ilxaot said:
I'll post some tomorrow. Re-read the past 5-6 posts and you'll see the bugs. I think you'll like it. MIUI is certainly different (settings default apps) and such, but it's a formidable ROM and performs relatively well.
Click to expand...
Click to collapse
I've already installed the ROM, it runs smoothly! You were right, I really like it! I had an issue trying to format /data, it took like 15 minutes, and did a hard reset (pressed power button for a few seconds) and tried to format again and it worked. Im a little bit worry cause I've had 2 radom reboots so far.. Any idea of what has happened to me?

Categories

Resources