Database Users

Tips and tricks when Odin and Kies dont work

Ok, I want to leave a message on here for future noobs like me with a Galaxy S
i9000 but it might work for others too.
My issue when flashing custom roms is that I have not been able to access my galaxy from my computer via usb since literally day 1 (when it did work once).
I spent a week trying to connect to Kies on multiple computers (vista and Windows 7). Tried via Android SDK, even tried hiemdall. I almost tried in ubuntu also but I never did get that working as I really don't know linux well enough. I've now given up...
So then I saw that you can do flashing all on the phone with the clockwork mod. With clockwork, my first rom flashed, well, like clockwork! But then I had some issues with lag and hang ups and reception and I decided to switch to another rom (seearms jl2 based rom - good stuff so far).
However this rom install went sideways... It said that it had installed ok but on reboot it stalled on the Galaxy I9000 screen and froze. Luckily I could still use the 3 button recovery to boot to clockworks but the hitch was that I HAD NO OTHER ROM to flash back to.
I had done a backup through clockworks but when I tried to restore it said the systems.img file was missing so it skipped it and the end result was the same freeze.
Normally everone says to reflash at this point with odin but that was not an option for me. So this is where I got lucky. The SeeARMs rom included Steam recovery module (though I thought it was the stock 3 button recovery menu for a while - I was panicking a little). I highly recommend seeing if you can get steam because it allows access to the External SD card for flashing which can be a lifesaver. Ahh, finally I could get the old rom on that, reflash it and go one with my life. My theory being that at least the issues would be aligned with the this rom and it worked.
So the lessons I learned:
1) Always have your new rom and your old rom on the interanal SD card in case of issues.
2) check your nandroid backup - even try testing it? - they don't always work perfectly with every device.
3)I highly recommend finding out if Steam or similar will work if you cannot access the USB connection and load things on when things go wrong.
Some tips I saw that also worked for me
1) flash a new kernel before you flash a new whole rom.
2) if things go sideways, try redownloading or retransferring the file to make sure there were no errors.
I did both and then reflashed (with my old rom Voodoo Doctor, SeeArms Rom and Darky's 8.1 rom on the card just to have options) and all was good!
PS: the steam recovery knocked off the first letter of the file when executing for some reason so I had to make 2 copy's of each rom I wanted access to ie Darkysrom.zip and arkysrom.zip just look for that error when you are doing this.

Good post - hopefully it'll help someone out who's stuck.

Hopefully
I'd like to stick some of that in on the thread for your rom but I need put another 7 half relevent messages out there before I am worthy... I understand the rule but I'd rather only post where it is meaningful...
GF

MIUI rom - Questions, Issues, Bugs, Problems, Complaints

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.

VZW update fix

if your have issues with the update not finishing 100% this will work
http://www.4shared.com/file/3skyGV3V/Verizon-GTab-Stock.html
download the zip using heimdall flash like normal
factoryfs-factoryfs.rfs
zimage-zimage
param.lfs-param.lfs
cache-cache.rfs
recovery-zimage
ignore the rest of the files
then before first boot wipe data and cache reboot
manually use update.zip or just let it download itself
install update and your done
you can verify by going to "about device" build number will be SCH-I800.EC02
use superoneclick for root z4mod not working keep getting f/c's
it seems like anybody who used z4mod to root or flashed recovery "back to stock" is having problems a 100% fix is just download the files from my post and flash like normal then use superoneclick for root
***for it to work you must download the recovery files from my post***
the files in my post are created using a temp. root so the files are a pure clone of unrooted rom 100% stock that is why you have to use superoneclick to root I tried everything and have done this to 6 tabs with no errors
EC02 stock ota update.zip download
http://www.4shared.com/file/qIHEta11/update.html

Thanks, I noticed you posted this on the other thread too. I have never used Heimdall so I was REALLY trying to avoid this but I guess I will have to take the plunge and figure it out.......

this works
I have tried every which way and this way has worked every time for me

Finally worked
works 100% just followed the steps and no problems finally updated!!!!!

It works, 100% Thank you so much for this

This does work, 100%, but please note that it DOES NOT WIPE THE DEVICE. It will boot up with all your stuff. This is not neccessarily practical, but it will probably be fine. If you have any root dependent mods, such as set cpu or lcd density, they wont work and it may operate funny/slow until you reroot and set them back up.

stock restore files download
http://dl.dropbox.com/u/21215221/Verizon-GTab-Stock.zip
or
http://www.4shared.com/file/3skyGV3V/Verizon-GTab-Stock.html
Download Mode (Volume down and power)
Download Heimdall from Here:
http://www.glassechidna.com.au/products/heimdall/
Also just below version 1.1.0 is Microsoft C++ This also needs installed on your machine because it has .dll files Heimdall uses.
Launch download mode on your tab that is already connected to your PC.
unzip heimdall and go into the drivers folder where you will see zadig.exe. Run this.
At the top you see options. Click "list all devices"
Then in the dropdown select Android USB composite device or might say it other ways
Click start and let heimdall download the drivers. Once its finished, close zadig and launch heimdall front end leaving Tab plugged in and in download mode
Unzip the stock files.
the zImage goes in both the Kernel AND Recovery slot.
The factoryfs.rfs goes in Factoryfs
The Param.lfs goes in Param.lfs make sure you use param.ifs not param.rfs
and the cache.rfs goes in the cache slot.
ignore the rest of the files in the zip and just use these
After you have the files in place click start to flash. ALWAYS make sure your battery is sufficiently charged or you will have MAJOR problems.
After this runs you will more then likely have to Power down, wait a few seconds and hold power and up volume to boot into recovery. (NOTE, do not hold power too long, just long enough to turn it on, then continue holding up volume till you see recovery. WIPE DATA AND CACHE. Tab should boot.
then let update download install it and you can use superoneclick if you want root back

This worked!
Thank you lexriley! That seemed to work. I forgot to wipe data/cache before i applied the update.zip, it still worked anyway. I should probably have wiped the data/cache.
Thank you !!!!!! Great Work!

Thanks so much. I rooted using Z4 and the update failed. I used your instructions and got up and running again! You saved my Tab!

I'm happy its working for everyone like it worked for me

100% fully working!!!!!!!
thank you lexriley your guide is easy to follow and do your the man!!!!!!

This should be a sticky!!!!
Sent from my ADR6300 using Tapatalk

Anyway to turn off the nagging update notification?. I have my tab where I want it, while your walk through is detailed and obviously a good solution, seems like an awful alot of time just for a minimal upgrade in software?.

oldmacnut said:
Anyway to turn off the nagging update notification?. I have my tab where I want it, while your walk through is detailed and obviously a good solution, seems like an awful alot of time just for a minimal upgrade in software?.
Click to expand...
Click to collapse
Well let me tell you what I have noitced with the upgrade
1) Stock browser speed is faster, but I dont use the stock so that wasnt much help
2)There is now a item in the top of settings for you to activate your device through verizon (like you would using *228 or whatever it is from your phone)
3)The wifi searching thing. I often forget to turn wifi off so when I drive it drains battery searching, the drain is significantly less now.
4) BLUETOOTH HID SUPPORT! Sorry for the caps but I have been wanting this one for quite some time now. First thing I did was try my MX5500 at home and it paired up and worked perfectly.
5)Hyperlinks in emails issue. Constantly many hyperlinks were cut off and I wasnt able to click them, this has now been resolved.
If none of these things are appealing to you then by all means you have no need to upgrade. But I found that most of this was a welcomed change. The tab seems faster, but I believe that is just due to the fact that I do not have LCD density changing the density, which I find slows down many things on the tab.

lexriley said:
I'm happy its working for everyone like it worked for me
Click to expand...
Click to collapse
At first it didn't work for me. I got "failed to access device. Error: -12". But that was my fault. I had forgotten to load the zagdig drivers for Heimdall. So I did that following the instructions in this thread and tried again. First try, I simply got a "fail", second try worked like a charm. When finished the Tab rebooted on its own.
As soon as it rebooted, I got the message that an update was waiting to be installed (EC02). Since I had already wiped the cashe (twice) on earlier attempts, I just went ahead and let the update install. Worked like a charm and now I've got EC02 update.
As a help to other noobs, I will add this.... The reason the update would not install in the first place is that I had deleted the VZW Vcast bloatware. Lexriley's fix here reinstalled all that VZW junk, which is what ultimately solved the problem. LESSON LEARNED: If you want future updates NEVER delete pre-installed apps. Either rename them and back them up to the SD, or better yet, "freeze" them with Titanium Backup.
Now to begin the task of re-rooting, installing ADW, and putting my Tab back into shape the way I had it.
BIG THANKS goes out to lexriley!! (And by all means, make this thread a sticky.)
Robin

Excellent work! This worked perfectly.

Got it, installed the newest Keis for drivers.

i hate to be that guy but is it possible to get odin files too? i can never get heimdall to work but odin works just fine

Robin M said:
As a help to other noobs, I will add this.... The reason the update would not install in the first place is that I had deleted the VZW Vcast bloatware. Lexriley's fix here reinstalled all that VZW junk, which is what ultimately solved the problem. LESSON LEARNED: If you want future updates NEVER delete pre-installed apps. Either rename them and back them up to the SD, or better yet, "freeze" them with Titanium Backup.
Click to expand...
Click to collapse
So if I just restore the vcast stuff then I should be able to update without doing all the recovery stuff? I just renamed them all with a .bak at the end instead of deleting just incase I needed them again so I still have them all.
Edit: apparently yes, removed the .bak I added to the files names, un-rooted, clicked update and it worked fine

shiltz said:
Edit: apparently yes, removed the .bak I added to the files names, un-rooted, clicked update and it worked fine
Click to expand...
Click to collapse
You're welcome. ...Isn't it great when you answer your own questions? I find myself doing that more frequently now, as I learn more about Android and my Tab - mostly from this forum.
PS... Now that you've successfully updated, take a look at the recovery.log file in your /cashe/log folder. I was amazed at the number and the variety of files this upgrade patched.

[Guide][CDMA R800x] FXP CM7 to CM9 upgrade. (As of FXP 125)

Hi everybody! I'm Dr...
Nah nm. Anyways well the past 2 days I have been working on switching from FXP CM7 to CM9. Needless to say, the process was abit confusing and did run across some snags along the way. So now that I figured it out with some help. I am returning the favor to the community and putting up this guide. (Also this guide is for users who already have an unlocked bootloader and so. So if you are a new R800x user who JUST unlocked their bootloader using testpoint or so, you too can use this guide)
Keep in mind this guide is based on the changes and tweaks from FXP 125!
So for those who are using a R800x CDMA Xperia play, this is for you.
-= The Prep =-
1: You will need the Flashtool to flash the latest ftf from Verizon. agraceful was nice enough to put it on his cloud storage here. http://www.mediafire.com/?yas7dola6dgd8 (You may wanna disable your AV for this as Kaspersky for me, didnt like the file since it uses exploits to do the stuff to your phone) if the cloud storage is down, this is the thread for the flashtool. http://forum.xda-developers.com/showthread.php?t=1351299
2: The latest Verizon ftf file here. http://forum.xda-developers.com/showthread.php?t=1696233
3: The latest FXP CM9 (remember its zeusc that you are downloading for!) AND the gapps for ICS! (Very important you use the right gapps here), http://forum.xda-developers.com/showthread.php?t=1447542
*OPTIONAL* 4: Mjolnir Kernel (boot.img) - http://forum.xda-developers.com/showthread.php?t=1708459 (Rename that img file to boot.img) (This is a diff kernel which may have some different features and abilities compared to fxp 125, so take a look and choose, atm it has zRam support (compcache) )
*OPTIONAL* 5: Cdma Carrier Name Fix - https://dl.dropbox.com/u/21955004/Carrier Fix.zip (This can either let you use a custom carrier name or least fix it from saying T-Cdma 64)
6: Of course, fastboot, drivers, and drivers for the flashtool which come with flashtool for flash drivers. (Not covered in this guide, cause if you already have CM7 on CDMA.. I am assuming you already have an unlocked bootloader, drivers etc already installed)
Now once you have everything. Time to do some EXTRA note prep work:
1: Make note of your MDN/MSID numbers. (The phone number and 2nd set of number incase you need to manually program your phone if OTA programming doesnt work)
2: Titanium Backup of your apps/data
3: Put the CM9 zip, cdma mega fix, and gapps ics into the memory card root folder. You will need this here to flash in a bit.
4: Kiss your phone bye bye and tell it you love it and that it will be back online soon if you dont mess it up!
Now you are ready to get started!
-= The Upgrade Install Process! =-
1: Turn your phone off, hold the back button and plug in the usb, You should be in the flash mode. Load up flashtool. (Your PC will install the drivers now if it needs to or the flashtool will error and tell you where the drivers are located to install and run its exe file to install)
2: With drivers ready, phone ready, you can drag the verizon ftf file to the main screen of flashtool. It should start up, give you some notes, tell you what you need to do if needed and just start flashing. Wait till its done fully, then you can close out of it, reboot your phone, if it boots up to Verizon screen setup, you have done the job correctly! Grats!
3: Unplug USB, Turn off phone, hold the search button, then plug in the usb again. You will see a blue light on the power button to tell you that you are fastboot mode.
4: Make sure the boot.img (Either the boot.img from FXP 125 zip file or the downloaded one) is in the same folder as your fastboot command! From cmd prompt, be in the directory of your fastboot and type fastboot -i 0xfce flash boot boot.img this should be a quick process and will put the new kernel you need with its cwm recovery built in needed for CM9. After thats done, type fastboot -i 0xfce reboot
5: During the reboot phase, LOOK at the power button. The MOMENT you see it light up "blue" hold the back button. This will load you into CWM where you can get started!
6: Now you SHOULD have your files on your SD card ready to be flashed! If you dont and you forgot. Just go to "mount" and mount the usb storage and then put your files on the sd card. (Silly person forgetting! Remember, its the cm9 zip, cdma fix, and the gapps ics)
7: Now flash the fxp 125 cm9 zip. Will take a min or 2. Once that is done. Do the 4x wipe. Wipe/Factory reset, Wipe Cache, Then goto Advanced, Wipe Devlik, Wipe Battery Stats.
8: Now flash gapps ics
9: (Optional) Flash the Cdma Carrier name fix.
10: Reboot into your phone.
If you see the cool transwarp sliders style android logo. Go WOOT!
-= The Inital Setup =-
Now that you are staring at the new android setup wizard here are my "personal" tips
1: From the setup wizard. I just did the basic, and SKIPPED the sign in part. Get your wifi running once inside if you want. Then load up "Play Market" and sign into google from there.
Why did I do this? Well.. I did it the other way 1st time signed in during the setup process.. and well.. I left the option "Restore phone from google" enabled.. yea.. not smart, next I know its installing EVERY app I had from Google. (Which I guess it was basing it on the google history or using my G1s installed stuff to restore from) By doing it the way above, it doesnt try to start restoring everything. Which is good.
2: Now to program your phone number and so again. Now I did this using pageplus, which is still verizon. For me, the OTA to get my number back in was *228 send. Wait wait wait, and it should program and be done with. Alt numbers are *22890 and *22891 which some update the roaming towers or just an alt form of OTA. Now if none of that works, then do the manual programming.
3: In the market, get titanium backup (and your pro key) and install.
4: The rest you should be able to do yourself as far as restoring goes using titanium backup.
Congrats you are now running ICS CM9 FXP!
Hope this guide helps people who maybe confused and would like a lil thread with something to look over to help them get it going. =)

Reserved..For..Stuff..

-=Tweaks=-
V6 Supercharger - http://forum.xda-developers.com/showthread.php?t=991276 (This is being used to help increase performance of CM9 on our xperia as well as some games that started sluggishing up after the change to ICS)
Volume+ - https://play.google.com/store/apps/details?id=com.TEST.android.lvh&hl=en Well worth the money.. otherwise my emulators sounded too quiet lol. Not to mention Youtube. Now at work, I use Speaker setting 8.

Hey,
You can make the update, as of FXP125 you don't need a separate kernel to get CWM. It's baked in again. Volume keys get you into it.

Mogul345 said:
Hey,
You can make the update, as of FXP125 you don't need a separate kernel to get CWM. It's baked in again. Volume keys get you into it.
Click to expand...
Click to collapse
Done. I left it optional for now. =) Also the only thing I need to confirm on is if we need that cdma mega fix file still... I forgot my XP at home.. (Go figure) so I wont be able to test the update out till tm. Heh.

Mysticales said:
Done. I left it optional for now. =) Also the only thing I need to confirm on is if we need that cdma mega fix file still... I forgot my XP at home.. (Go figure) so I wont be able to test the update out till tm. Heh.
Click to expand...
Click to collapse
I did not have to flash the megafix. All I did was the following (w/ FXP125):
1)Use flashtool to flash new baseband from 2.3.4 FTF (when selecting what to flash, I excluded everything but baseband).
2)Use fastboot to flash the FXP125 kernel.
3)Booted into CWM, wiped data/cache/dalvik cache/battery stats, then flashed FXP125 and the 4/29 Gapps.
Only thing I think needs flashed is the carrier name fix. My phone says T-CDMA 64 again.

Ok thanks. Yea, according to lightningdude the only things in the cdma mega fix was just the gamepad fix (dont know what that is yet) and the cdma carrier name. Gonna try to see about those. While its minor, still good info to have.
Also its being said that we should use V6 Supercharger on the CM9 to improve some games again for XP users.

Ok thanks to lightningdude, I put the cdma carrier name fix in the guide. =)

Mysticales said:
Ok thanks. Yea, according to lightningdude the only things in the cdma mega fix was just the gamepad fix (dont know what that is yet) and the cdma carrier name. Gonna try to see about those. While its minor, still good info to have.
Click to expand...
Click to collapse
Ahh OK. That gamepad fix is the patch to the .idc file changing the button map so circle isn't back in some games.
Sounds like the megafix is just all the preferred patches that were applied to paxChristos' CDMA builds.

Yea, just made life easier. Also I excluded the gamepad fix as thats a personal pref.. cause BUTTON_B vs BACK_ALT mapping can break some apps which devs code for one or the other. Normally everyone is using BACK_ALT. Then emulators which can remap it all anyways works fine with it.
Edit: Ok just updated to 125 myself without the CDMA carrier name thing. My Pageplus comes up as Verizon Wireless, so not sure if the patch was needed, but still its in guide as optional, case you want a custom name or you do get that t-cdma 64 issue.

Mogul345 said:
Hey,
You can make the update, as of FXP125 you don't need a separate kernel to get CWM. It's baked in again. Volume keys get you into it.
Click to expand...
Click to collapse
are you saying that steps 3-5 of the install process is not required since its baked in? Sorry, just getting into the more advanced rooting/customization with the r800x. I'm going to unlock the bootloader (put this off for way to long but with the latest "No ICS from Sony/Verizon" i'm just going to move ahead with my own upgrades, then ftf the verizon 2.3.4, and then hopefully be getting ICS.

blkwhk said:
are you saying that steps 3-5 of the install process is not required since its baked in? Sorry, just getting into the more advanced rooting/customization with the r800x. I'm going to unlock the bootloader (put this off for way to long but with the latest "No ICS from Sony/Verizon" i'm just going to move ahead with my own upgrades, then ftf the verizon 2.3.4, and then hopefully be getting ICS.
Click to expand...
Click to collapse
Looks like the original instructions have been updated. You should follow the instructions as directed in the OP. Steps 3-5 currently are where you flash the boot.img (kernel) you wish to use. It's either FXP's (which would be extracted from the ROM .zip), or Moljnir's or the other one listed. All three have working Clockworkmod recoveries now. At the time these instructions were originally written the recovery in FXP's kernel was busted, the next FXP build fixed it, and that's when I wrote the post you're referring to.

[ROM][OFFICIAL] P7300XXLQ6 (OpenAustria) cwm+odin (2012-12-16)

Hello guys,
so I've seen others do this before, and I thought, I should be able to do that too I'm a computer geek by training, but never got very deep in Linux/Android hacking.
Anyways, I made a CWM-flashable zip out of the Odin package for the latest ICS for P7300. (PDA: P7300XXLQ6; CSC: P7300OXALQ6; "OpenAustria")
Odin package: (source sammobile)
info: http://www.sammobile.com/firmware/?page=8&view=8417
download: P7300XXLQ6_P7300OXALQ6_ATO.zip (from hotfile)
I initially flashed the Odin package on my tab, and kept all my userdata, user apps, and even my homescreens. But I came from official, odin-flashed P7310UELPB ICS for USA released 3 months ago (yes, that's wifi-only, but runs fine on P7300); so that may have an influence.
If you are concerned about the integrity of your device, I do recommend you install the Odin package, as it is straight from Samsung, so you can be assured not to suffer from the error injected by anyone else (not that I made any errors, mind you :angel: ).
CWM-flashable package: (by direct conversion from the Odin package - no modification, not rooted, nothing added/removed/altered)
downloads:
- ROM: P7300XXLQ6-ROM.fred-v01.zip (for links, see post #3)
- MODEM: P7300XXLQ6-Modem.zip https://www.sugarsync.com/pf/D6778724_7163149_619563
md5:
e16200b688b8f4e602448f76e78a7d27 P7300XXLQ6-ROM.fred-v01.zip
48f9d2b048c2416d84ecdfcea904a434 P7300XXLQ6-Modem.zip
How to install
- if coming from stock ICS or HC, I suspect only wipe /cache is needed. From any other ROM (like CM or AOSP) I suspect you need a /data wipe (warning: deletes all your application data; but not your /sdcard)
- flash from any CWM recovery (I tested only 5.1.2.6). Turn OFF signature validation, as these zips are not signed. It took about 3-5 minutes on my tab
- (ps: the updater-script was borrowed from a recent kallt_kaffe ROM, so it's pretty bog-standard Just added a few outputs to show progress)
Other info
- the Odin package also includes a newer bootloader. I don't know if it's essential to have that newer bootloader, but I can add it later.
- It may not be necessary to flash the MODEM, but I would recommend keeping the MODEM+ROM combination.
Optional additions & tweaks
- any root package should work. (Update: I recommend either v3.1.3 or 3.2 from the original developer of Superuser: http://androidsu.com/superuser/ )
- if you have rooting problems, first uninstall other root packages, including superuser/superSU updates from Market. There is an "unroot" procedure in the sticky on General forum.
- you can get voice-call mod by flashing these 2 from cwm
* P7300XXLQ6_ENABLE_VOICE_CALL.zip from suwandiapr - http://forum.xda-developers.com/showpost.php?p=35264752&postcount=36
* the I9103 modem - http://forum.xda-developers.com/attachment.php?attachmentid=1309125&d=1347032493
- if you hate the boot sound, remove/rename the /system/etc/PowerOn.ogg
- fix for system freezes: see FAQ link under "reading"
- fix for wifi: see tracid's thread linked under "reading"
- OCUV kernel: see AAccount's thread for A1 kernel (careful, some versions work only on stock, others work only on cm10/aosp versions. Use e.g. the well-tested 1.7.3; or the much less tested 1.8.3c. Read carefully his posts and know that custom kernel involves experimentation, trial&error and potential instability)
- attached to this post is a flashable zip to easily return to stock XXLQ6 kernel (or you could flash the who ROM again, if you want)
Interesting reading
A MUST: my FAQ regarding ICS issues (especially if you are first time upgrading from HoneyComb to ICS)
http://forum.xda-developers.com/showthread.php?t=1895496
tracid's thread - he had the first "stock" ICS for P7300 2 months ago (it required a heroic effort to pull the update from an OTA package, that was available on Samsung servers, but not being pushed out by Samsung). As such, his thread (and esp the first post) has lots of useful info for Stock ICS on P7300, gathered over last 2 months.
http://forum.xda-developers.com/showthread.php?p=31720406
Credits
for inspiration, for sharing, for a couple lines in the updater-scripts, for being great devs, or great modders, or for letting me think I can do this...
kallt_kaffe
tracid
suwandiapr
safariking
and others who posted info that I used to make this
Returning a favor?
PS: I use SugarSync cloud storage for sharing this file - and will keep it there as long as I can. Help me keep the file alive by creating your own SugarSync account with THIS link (we both get 500mb extra - but only if you install the app on computer or smart device): https://www.sugarsync.com/referral?rf=cw2yimm8cchga. I also spend 10 hours of my life making this conversion, most of it in the middle of the night, so that must count for something, right
Alternatively, hit thanks - it gives a warm feeling too

reserved by OP
screenshot attached, unfortunately xda resized it to 640x400
Update 2012-12-25:
I received twice the question "what is the difference between this and tracid's rom". (e.g. here
Both are stock ROMs from Samsung with no modifications. (tracid added root, busybox; but this can be easily added yourself on this ROM as well)...
tracid's ROM = ZSLP7, regional variation: Taiwan. Obtained by *manually* applying an OTA file found on sammobile, to the P7300ZSKK2 honeycomb ROM. Samsung never officially pushed out the ZSLP7 as far as we know; so it may have been an internal test build.
here = XXLQ6, regional variation: Austria; An official and distributed build, as far as we know.
Samsung is not releasing changelogs, so the actual differences are hard to find, other than the fact that different regions (have slightly different set of added application (e.g. kobo, Polaris, ...). XXLQ6 came with swype keyboard. Not sure if ZSLP7 came with that.
Most importantly, XXLQ6 has a more recent build date, and seems to be officially distributed, so one can *assume* it has more fixes.

initial hosting on sugarsync broken: files blocked because of a "Fair Usage" violation. Probably it broke the "10GB per day max download on Free accounts" limit that I was not aware about
For a limited time, you can get the files from my Adrive (no download limit, but only 10 concurrent downloads possible - links expire after 14 days) / links valid 2012-12-22 until 2013-01-05
ROM: http://www.adrive.com/public/BAMDga/P7300XXLQ6-Modem.zip
MODEM: http://www.adrive.com/public/srnfuF/P7300XXLQ6-ROM.fred-v01.zip (830 downloads until 2012-12-22)
User x24 has a mirror up -> see his post on page 3: http://forum.xda-developers.com/showpost.php?p=36135549&postcount=25
here are md5's in case anyone wants to mirror/verify.
48f9d2b048c2416d84ecdfcea904a434 P7300XXLQ6-Modem.zip
e16200b688b8f4e602448f76e78a7d27 P7300XXLQ6-ROM.fred-v01.zip
cheers, Fred.
PS: referral signup for dropbox - should you feel interested to give yourself and me an extra 500mb on dropbox: http://db.tt/g26Egj0

Thank You a lot for the upload because today is the second day that I try to download the Odin Package of this P7300XXLQ6 Rom... But without success... This Hotfile link is "out of ordrer" since 2 days...
Your "NON Odin package" is only around 400Mo and the Odin package is around 600Mo... Is it normal?

about smaller size... The odin package is poorly compressed. Also, it contains some 100mb stuff that does not get installed, at least not on my tab (these are mostly demo apk in a hidden.img - I can make them available, but as I said, they were not even installed on my tab)

Ok! Thanks! :good:

installed in on my P7300 tab just now and it's running okay. I did not do any factory reset. Just wipe cache, as stated in OP, coming from stock honeycomb. Um. But I always run into "Android is updgrading, optimising application 1/1" every reboot. is that normal?
UPDATE:
Upon installing the kk_root_ics.zip, tab won't respond after some seconds. I reflashed the rom and it responded fine again.

Optimizing apps is the message when creating the dalvik-cache for a deodexed APK. It should happen after initial install, and then again if you add apps through recovery or so. E.g. I got it (once only) after flashing root package, as this added superuser.apk.

Other than the ROM itself, what else have you flashed (the more exact, the better to diagnose)

Even if I didn't install from CWM, it always show the optimising app 1/1. I'll further check since I'm always trying to root my tab to no avail.
I tried flashing different ROOT.ZIP, including the link on OP, on CWM, and it ALWAYS hangs after some seconds after apps has been loaded. Opening an app right after boot will also end up the tab not responding.
I only flashed ROM+MODEM then reboot. Everything runs well. but whenever I flash a flashable cwm file to root the tab, that's when I experience the hang.
Update:
Tried to odin CF-Root, but failed. Got stuck on "Leave CS" thrice~ and stuck on 1/8 progress bar so I flashed the rom again.
Update 2:
I uninstalled SuperSU and Superuser from tab. I then flashed Stock Recovery (from here) via Odin. Flashed kk_root_ics.zip and booted okay. I found Superuser installed. But when I try to update binary, it says failed. I downloaded superSU, and it also failed to install the binaries.

haramizuki said:
Even if I didn't install from CWM, it always show the optimising app 1/1.
....
I tried flashing different ROOT.ZIP, including the link on OP, on CWM, and it ALWAYS hangs after some seconds after apps has been loaded. Opening an app right after boot will also end up the tab not responding.
Click to expand...
Click to collapse
See my FAQ. There's a bug in many stock Samsung ics, that mean that any application FC, leads to full OS hang. I made a fix for that....
As for the optimizing 1/1 on boot: might be a corrupted apk file on your data partition.

Full wipe/factory reset fixed it. I actually didn't have any backup because I accidentally hit the full wipe forgetting that it will wipe internal files as well. I installed rom via Odin since it's the only way coming from a full wipe. :thumbup:
Btw, Which do you prefer: Supersu or superuser?
sent from S2 running latest pa+dori ,unless stated otherwise ^^

Superuser serves me fine. I never tried superSu

not bad. So far 600 ROM downloads on the Adrive link
If you installed this successfully, let others know!

Will this work on the 7310, or will it freak out because there's no phone?
Sent from my GT-P7310 using xda app-developers app

upconvert said:
Will this work on the 7310, or will it freak out because there's no phone?
Click to expand...
Click to collapse
Until somebody tries, we don't know
However, why would you want to. There are recent enough ICS packages (e.g. on sammobile)
In theory, I somewhat expect it might work, and if it doesn't, should be easy to overwrite with p7310 ROM.
No promises, no warranty !
Sent from my HTC Desire using xda app-developers app

Was this the one you had suggested to me over on the a1 kernel thread?
Sent from my GT-P7310 using xda app-developers app

Sorry about that. Thought you had a p7300. The discussion on a1 v1.8.3 not working on stock, was with a mixed audience.

fred_be9300 said:
Sorry about that. Thought you had a p7300. The discussion on a1 v1.8.3 not working on stock, was with a mixed audience.
Click to expand...
Click to collapse
No prob, I just wanted to make sure I wasn't missing something. I really want a rom with working face unlock, so I think my only options right now are stock or the mostly stock discovery.
Sent from my LG-VM670 using xda app-developers app

If you are coming from cm10, do you need to flash modem.zip also? Also what version of cwm to use? Thanks
Sent from my GT-P7300 using xda premium