Develop Bugs

[SPRINT][CDMA][FROYO][GUIDE] Overcome/KhasMek 1.4ghz OC FAST (4.30.2011)

First off, this is not for the faint of heart. Backup your junk, don't flash modems or bootloaders if you don't what you're doing, in fact, don't flash anything, if you are not aware of what is what... Read this ENTIRE GUIDE FIRST, THEN DO IT... that way you have a clear understanding of what is suppose to be on your sd card, etc....
Second, none of this is my own work. I take no credit for the development of any of the following, this is more of a guide than
a rom on how to get a Sprint SPH-P100 working with a custom recovery, kernel and rom.
I should note, I have tmobile US, and my interest in this tablet is a secondary device, hence it being a sprint device. It is not meat to be a phone for me... I dont plan to make calls or text, only tether it to my phone, use GPS as well as the other functions. It is, essentially, a laptop replacement with extra goodies...
That being said, if you test this, it is at your own will and I will provide no further instructions on how to undo something you have done... this forum has a search feature, use it. Any contributions to developing it further and providing fixes for the problems listed below are welcomed.
Before I begin, big, BIG thanks to alterbridge for providing me with excellent tips.
Also to Khasmek for his kernel and everyone who helped in the production of heimdall.
Again I say, this guide is meant to give you overclocking features for your tablet. As-well-as the ability to reboot to a custom recovery from the gui (in this case cwm 3.0.0.0).
What works?
Wifi
Camera
Video Recorder
Gallery
all other apps
What does not work?
GPS
What may or may not work?
Calls
MMS
SMS
Voicemail
What's included:
Refer to:
http://forum.xda-developers.com/showthread.php?t=932082
I'm assuming here that you are rooted. If you are not, use superoneclick. Google it...
I'm assuming your are stock also, if you are not, I advise you to get that way using this: http://forum.xda-developers.com/showthread.php?p=9753941#post9753941
Please read it carefully as you can complete bork your tablet if you are not certain. Thanks to gordesky1 for the guide.
When/if you are back to stock you can begin this process. I insist that you do this, because it is the method I started from after flashing various roms/kernels etc...
Now preload your microSD card with the following (i'm assuming you have formatted and can load it with a pc-usb attachement)
[ROM] Overcome 1.6.3
Link: http://www.multiupload.com/8XVZ2JPE4V
Source: http://forum.xda-developers.com/showthread.php?t=932082
[Kernel] KhasMek Voodoo Plus v5
Link:http://gunsforgeeks.com/Tab/kernel/KhasMek.Voodoo.Plus.CDMA.Tab.v5.OC.zip
Source: http://forum.xda-developers.com/showthread.php?t=941781
You will also need a new vold.fstab file, a link is within the instructions.
Lets begin (flashed with Windows 7, sorry mac/linux users, you are on your own):
Step 1: Flash the VZW kernel, as it contains cwm custom recovery and allows you to flash kernels and roms.
Source: http://www.thegalaxytabforum.com/index.php?/topic/1775-clockworkmod-for-sprint-galaxy-tabs/
Download zImage file here: http://www.megaupload.com/?d=SV6IKL1D
Process: (thanks jkurl15)
"To get the zip file containing the zimage download it from here. http://www.megaupload.com/?d=SV6IKL1D
To flash the zimage you will need to use Heimdall which can be downloaded here. http://www.glassechi...ducts/heimdall/ <--------click on the binaries
link for 1.1.1
instruction are below.
Heimdall install instructions
1. Download Heimdall here http://www.glassechi...ducts/heimdall/
2. Download Microsoft Visual C++ 2010 Redistributable Package (x86) and install it. http://www.microsoft...&displaylang=en <------only if you are using Microsoft widows
2. Unzip Heimdall and you should have several files in the folder called Heimdall.exe, Heimdall-Frontend.exe, QtCore4.dll, QtGui4.dll, Readme.txt and drivers folder containing zadig.exe
3. Put you tab into Download mode(while the tab is OFF hold Volume Down + Power Button). Hook the tab up to you PC and Run Zadig.exe to install the
drivers.
4. From the menu chose Options -> List All Devices.
5. From the USB Device list chose "Samsung USB Composite DEvice".
6. Press "Install Driver", click "Yes" to the prompt and if you receive
a message about being unable to verify the publisher of the driver
click "Install this driver software anyway".
7. Done. This only needs to be done once.
ClockWorkMod Install Instructions
1. First root you tab (use one click root or z4root) then downloaded rom manager.
2. Unzip the flash_image_VZW_zimage.zip. It will have have two files flash_image and zimage. you only need to use the zimage file. Open Heimdall-Frontend.exe and browse to where you unzipped the zimage to and select it. Make sure the box infront of zimage is checked. Hit start and it should flash the zimage and reboot the tab. when it reboots it will get stuck at the samsung screen long hold the power button to shut it off. boot into recovery (cwm) power button plus volume up button it will start backing up to do the fs conversion but it will fail at /data and /cache. it will leave you in recovery.
3. While still in recovery select factory reset/data wipe when finished also do a cache wipe.
4. select reboot system, if you let it try to boot it will loop/hang on the SAMSUNG logo, this is not an issue just hold power key until it powers off.
5. while off hold volume up + power until you see the SAMSUNG logo then release both keys! NOTE: if step 4 does not fully power off and reboots just keep holding the power button until the screen blanks again then let go and quickly hold down only volume up + power until you see the SAMSUNG logo.
6. once it boots back into recovery (cwm) it will start the same backup/conversion process again, this time it will finish and leave you in recovery.
7. select reboot system and wait for it to load the tab back to froyo. (it will be back to factory defaults with the activation screen again)
8. Your tab will still be rooted so install terminal emulator and run "mount" to verify that your partitions are ext4.
9. Power off then boot back into recovery with volume up + power, it will boot back into recovery (cwm)
10. Do a backup and reboot your tab. " - zkurl
Step 2: Your screen should show you cwm 3.0.0.0 and be ready...
1) Wipe Data/Factory reset (for good measure)
2) Wipe Cache
3) Wipe Dalvick
Step 3:
Install the [Kernel]. It will flash and let you know when it is successful.
Step 4:
Install the [ROM]. It will flash and let you know when it is successful.
Step 5:
Install the [Kernel] AGAIN. (i know, it seems retarted, however I've had bootloops otherwise and it didn't matter if i didn't flash it before the rom or not, it would screw up) Anyways, it doesn't hurt.
Step 6:
Wipe again, just for good measure
Step 7:
Reboot device (first boot will take a few but doesn't hang at anything. Which means, if you see the samsung logo for longer than 60 seconds (actually takes right at 30 seconds)... you screwed up. The boot animation of the blue android with astro stars thingies going around it means you are on the path to booting)
Step 8:
The external and internal memory are jacked up. A fix has been provided and you will need to push it to your phone, and reboot.
Download vold.fstab here: http://www.multiupload.com/EKYF3CW39R (thanks to alterbridge)
bring up adb (if you dont know how, stop reading this, re-stock your phone and quit)
adb remount
adb push vold.fstab /system/etc
adb reboot
Your tab will reboot and when it comes back up, no more memory errors.
You've done it! You've flashed a oc'd kernel and a custom rom. From here, you can tinker with fixing the auto-rotate and gps and any other bugs you may encounter. I admit, i'm new to certain things, fixing it isn't my forte
I encourage you to post fixes/bugs here in the thread so that other sprint users can benefit from it all as there is a serious lack of development for them.
Future Updates: I'm assuming we can continue to flash whatever overcome updates come our way, we just have to then reflash the khasmek kernel and re-push the vold.fstab file. If we fix GPS, Screen orientation and it's through pushing means, that will have to continually be redone also. The alternative, someone cooks roms just for us... I myself could probably do it, however have never attempted to. If i get time, I will look into it, however, there are no promises...Maybe gingerbread/honeycomb variants will trickle out soon and we wont have to worry about it.
If you enjoy the rom/kernel, I encourage you to donate to the devs mentioned above, I myself will not require any donations, as this is merely a guide using other peoples materials. A big, big thanks again to the people who contributed to these roms, kernels and tools. Thank you!
Update 1: (4.30.2011 @ 6:49PM CST)
Fix for rotation using a method from the voodoo thread. Can either push it, or copy to usb with pc, then use root explorer or similar to move it into place (requires reboot)
"Try pushing the sensors.default.so file from bauxites thread. I have attached it.
unzip this and place it in /system/lib/hw (backup your old file just in case!)"
Update 2:
When you first boot, your keyboard is selected as "chinese". Simply change it to samsung or whatever else you may want to install...
Thanks to Bauxite!
File: http://forum.xda-developers.com/attachment.php?attachmentid=562977&d=1302188558
Source: http://forum.xda-developers.com/showthread.php?p=12722251&highlight=sensors.default.so#post12722251

Have you tried pushing the sensors.default.so from the v5 thread to /system/lib/hw
Thats what I just did to fix my sensors on the voodoo build
Sent from my SPH-P100 using XDA App

Obama's>god said:
Have you tried pushing the sensors.default.so from the v5 thread to /system/lib/hw
Thats what I just did to fix my sensors on the voodoo build
Sent from my SPH-P100 using XDA App
Click to expand...
Click to collapse
will give that a shot, thank you
Edit: that worked like a charm thank you so much, love XDA!

No problem its one of the last pages. Someone also posted a file gralloc.something.so dont use that. It gave me a weird boot crash where id get the 3 vibrates from a force close over and over again.
Sent from my SPH-P100 using XDA App

just curious, are you using this same setup as myself?
curious if sprint can still make/receive calls send/receive messages... etc...
if you're even utilizing those features... just wondering, thank you again

You mean stock sprint? On stock you can send or recieve messages but no calls
Sent from my SPH-P100 using XDA App

ah no, i meant sprint with the overcome rom and the voodoo kernel. I know there is a lot different so i'm sure it wont work, was just curious

From what I understand its only gsm that can do calling. It's either going to take aosp or some serious serious hacking to get calls on cdma. Im hoping for cyanogen, but I still cant get a stable version of that for my brother's samsung epic.
Sent from my SPH-P100 using XDA App

This worked like an absolute charm!

can anyone of you confirm if you
1. installed on Sprint Tablet
2. have the GPS working?
Thanks soo much!
BTW, great on the write up!

galexandr said:
can anyone of you confirm if you
1. installed on Sprint Tablet
2. have the GPS working?
Thanks soo much!
BTW, great on the write up!
Click to expand...
Click to collapse
1) Yes
2) No.

galexandr said:
Thanks soo much!
BTW, great on the write up!
Click to expand...
Click to collapse
You are very welcome

My Wifi all of a sudden quit working. I turn the Tab on, press the wifi toggle in the notification bar, and then it says "Error" and turns off.

That's interesting. This and Force Closes is why I ended up wanting Overcome over the KhasMek rom....
However, My sprint tab has not encountered this as an error, and I've flashed other modems and everything...
You might try and "fix permissions" from the recovery ... otherwise reflash again just for s's and g's.... I myself haven't seen this as a problem and have used it this way well over a week.

mr2324jgf said:
That's interesting. This and Force Closes is why I ended up wanting Overcome over the KhasMek rom....
However, My sprint tab has not encountered this as an error, and I've flashed other modems and everything...
You might try and "fix permissions" from the recovery ... otherwise reflash again just for s's and g's.... I myself haven't seen this as a problem and have used it this way well over a week.
Click to expand...
Click to collapse
I wiped data from CWM 3.0 and wifi started working again. I wonder what the issue was.
I'm also curious - would this technique work for the GSM CM7 port? Or is CM7 too far away from stock?

I've tried flashing cm7 a few ways and am always unable to get it to work. I'm assuming it's because I need the pit file with it which in heimdall requires the bootloaders also. I haven't messed with oldin or heimdall command prompt...
Last night I attempted again to flash the voodoo kernel over top of the clockwork mod with the stock rom... I then used titanium to clean some junk up, so i'm basically back to stock sprint with a custom OC kernel... it's pretty nice. I'm still not satisifed fully because I know there has to be other options.

mr2324jgf said:
I've tried flashing cm7 a few ways and am always unable to get it to work. I'm assuming it's because I need the pit file with it which in heimdall requires the bootloaders also. I haven't messed with oldin or heimdall command prompt...
Last night I attempted again to flash the voodoo kernel over top of the clockwork mod with the stock rom... I then used titanium to clean some junk up, so i'm basically back to stock sprint with a custom OC kernel... it's pretty nice. I'm still not satisifed fully because I know there has to be other options.
Click to expand...
Click to collapse
Just curious, why did you revert back to stock from this rom?
Sent from my SPH-P100 using XDA App

followed the guide and still stuck at the samsung screen after flashing kernel, rom kernel.

This is going to sound like critisism but I mean it as an honest sincere question. Why would anyone want to follow this guide if it breaks GPS? It's already possible to get the OC with Kazmek or Bauxite's kernels on the stock firmware with EXT4, and GPS also works fine with that other AOSP build, so what's the point of this?

cmoreno911 said:
Just curious, why did you revert back to stock from this rom?
Sent from my SPH-P100 using XDA App
Click to expand...
Click to collapse
I've since returned to overcome, I really wouldn't mind having my gps back... but i'm testing different options on it. It's fun to tinker with it, whatever the case, lol
idumych said:
This is going to sound like critisism but I mean it as an honest sincere question. Why would anyone want to follow this guide if it breaks GPS? It's already possible to get the OC with Kazmek or Bauxite's kernels on the stock firmware with EXT4, and GPS also works fine with that other AOSP build, so what's the point of this?
Click to expand...
Click to collapse
the stock firmware has bloatware for any given carrier. the overcome rom is stripped of some of the nonesense without having to go into titanium and delete crap trial and error...
also, in the overcome rom, i can boot into recovery, reboot etc from the power button, whereas with the stock rom i can only power off....
not to mention, i dont have sprint and the sprint branding bothers me... custom boot etc makes me feel like i'm in control of my tablet.
the other benefit of myself and others doing this, is to try and FIX the gps, thus making this the best CDMA/Sprint option for the tablet.
etc etc etc....
thanks.

Gingerbread on Droid Pro with Unlocked Froyo Radio

So, as people know, the newest builds of CM7 or CM9 by JackpotClavin require it to be placed on top of a fully updated Gingerbread Droid Pro. However, those of us with a US Band unlocked radio can't do that without losing our unlocked radio since there is no unlocker for the gingerbread radio. Based on what Axl did for the Droid 2 Global, I've created a gingerbread kernel based on the Droid Pro to allow us to install gingerbread roms while maintaining our unlocked radios. I've also created a clockworkmod backup that can be used as is, or as a base for installing another gingerbread rom such as CM7. Thanks to JohnS and dettofatto, the kernels and clockworkmod backups were updated to 4.7.3. Below are the Resources and the Process.
Resources:
1) RDS Lite (http://forum.xda-developers.com/showpost.php?p=19390783&postcount=1)
2) SBF 2.26 (http://db.tt/5gKwCQwF)
3) TBH Radio Unlocker (http://goo.gl/6NuuG - http://www.mediafire.com/?9pfbk846tjb5a36)
4) Root (http://www.psouza4.com/Droid3/)
5) Droid 2 bootstrap (http://www.mediafire.com/?g8l7vy0futbc4g5)
6) Kernel (US http://www.mediafire.com/?swv4bl7wa47mpxg or EU http://www.mediafire.com/?w6963rmkvdqmro1)
7) ClockworkMod Backup (Verizon US http://www.mediafire.com/?yhr4b768qbnyote or European http://www.mediafire.com/?wn3pyy5fw3i1nr2)
8) Optional Roms - CM7 for Droid Pro (http://goo.gl/M6e4s) or Apex for Droid Pro (http://goo.gl/sTwSp)
Process:
1) Boot to Recovery & Wipe Data (R+M+Power)
2) Boot to Bootloader (Up+Down+Power) & SBF to 2.26 (Using RSD Lite & SBF file) - Usually I have to copy SBF File to root of Hard Drive & name it 2026.sbf or it may fail (ymmv)
3) Skip Activation (http://goo.gl/n2Zhw)
4) Settings->Applications, Set Unknown Sources and USB Debugging (in development)
5) Root
6) Install Bootstrap apk, open, press 'bootstrap recover'. then 'reboot recovery' to boot to recovery mode.
7) While in recovery mode, and without rebooting at all:
...a) Wipe Data
...b) Install Radio Unlock
...c) Install Kernel
...d) Restore Clockworkmod backup (you should have extracted the clockworkmod zip so the folder is located on your sdcard at [ie clockworkmod\backup\...] folder (with the system.img and other images under that folder))
8) Optional - Install cm7, apex or other rom you download
9) Reboot
Notes:
1) You can build your own Clockworkmod recovery file by following the JackpotClavin link below and then just backing up your build. It won't have signal while you're doing it (because of the locked radio), but after you restore it later using the above steps, it'll be fine.
2) Your SIM needs to be unlocked from verizon (i used sim-unlock.net) to work.
3) Info on an Argentinian 2.3.6 rom here
Credits:
JackpotClavin - CM7 for Droid Pro (http://goo.gl/M6e4s)
Axl - Created the Droid2 Kernel which allowed me to use the same method for the Droid Pro (http://goo.gl/ErLAR)
dettofatto - Clockworkmod backup and kernel for European 4.7.3
JohnS - Clockworkmod backup and kernel for Verizon US 4.7.3
Good Luck!

hey im from argentina, here we have Motorola Pro which is the same as droid pro but it doesnt use cdma, it uses gsm and hsdpa. Can i install this on my phone or will it turn to a nice brick?
now i have ANDROID 2.2.2 and it says that the phone is the xt610 same as the droid pro.
thanks
edit: i just followed your source (jackpotcalvin) and it says it should work with gsm but there are still issues

bveditz, thanks for your work.
i have a droid pro (unlocked, verizon branded).
right now i'm using android v2.2 because the TBH radio hack only works with this version. i didn't dare doing any updates because of that. lol. i have one questions.
my phone is already sim unlocked.
so with this new CM7 build, can i just flash and use it without doing the TBH radio hack all over again?

chagla said:
bveditz, thanks for your work.
i have a droid pro (unlocked, verizon branded).
right now i'm using android v2.2 because the TBH radio hack only works with this version. i didn't dare doing any updates because of that. lol. i have one questions.
my phone is already sim unlocked.
so with this new CM7 build, can i just flash and use it without doing the TBH radio hack all over again?
Click to expand...
Click to collapse
Yes, you don't need to unlock the radio, you can start from step 5 (or 6 if its already rooted) and just skip the part about running the radio unlock. Running the radio unlock again doesn't hurt anything either.
Just a word of note, I don't know how the froyo build is by default (i didn't use it), but the current CM7 build still has the issue with switching between mobile data and wifi data, and mobile data can also cut out at times. All that info is in the CM7 discussion, but it's worth noting that the Droid Pro CM7 Build isn't a final build and might not function with the same stability as the Froyo build did. This has nothing to do with this process, it's just the current state of the CM7 rom at the moment. Flashing APEX might produce better results with the radio, but you lose features of CM7, although it has a number of its own features.

installed it. i just started with step 7C. so far so good.
radio is working. sim is still unlocked.
so far i've found one thing, maybe i didn't see the setting yet. the keyboard back lights aren't working?

chagla said:
installed it. i just started with step 7C. so far so good.
radio is working. sim is still unlocked.
so far i've found one thing, maybe i didn't see the setting yet. the keyboard back lights aren't working?
Click to expand...
Click to collapse
No, with that issue and the wifi/radio issues (loosing connection and not being able to switch between the two) , I switched over to the APEX ROM, it's more stable. You don't get the features of CM7, but it has less bugs. Might want to try that. You don't need to do anything different, just put the apex file on your SD, reboot to clockwork mod and wipe data and reflash.

is it possible to use this in some way to have band unlock and normal ginerbread without cm7

Yes. You need to basically upgrade Gingerbread to the full release, root it and do a nandroid backup. Then, you follow the steps in the first post but instead of restoring the nandroid backup of CM7, you install the nandroid backup of regular gingerbread that you made yourself.

bveditz, thanks, that is along the lines of what i was thinking might work after reading the directions... Im already running tbh rooted gingerbread... Do i need to sbf and upgrade to a clean gingerbread, or can i nandroid backup what i already have and then retain all my settings and apps so i dont have to start over. Has anyone noticed any disadvantage to useing the older radio besides the obvious advantage of being able to use the band unlock?

Excellent tutorial!!
EXCELLENT TUTORIAL GUYS. Also, you should make sure to mention after installing bootstrap, press 'bootstrap recover'. then 'reboot recovery' option. I did that, installed the kernal and restored backup fine.
Only issue so far was a -20% battery decrease randomly. I had 100% with a brand new battery fully charged for the first time and when I finished installing cm7 I was already on 80%, then dropped to 70% on a reboot or two, its weird. Anyone else had this happen? I heard the apex 2.0 rom did it to someone else as well on another forum
Also, do you guys know how to get back the blur social network apps such as friendfeed, or whichever app it was that adds your friends social network updates to their contact numbers on your contacts? Most people don't like it, but I think its a pretty awesome built in feature

jxs714 said:
EXCELLENT TUTORIAL GUYS. Also, you should make sure to mention after installing bootstrap, press 'bootstrap recover'. then 'reboot recovery' option. I did that, installed the kernal and restored backup fine.
Only issue so far was a -20% battery decrease randomly. I had 100% with a brand new battery fully charged for the first time and when I finished installing cm7 I was already on 80%, then dropped to 70% on a reboot or two, its weird. Anyone else had this happen? I heard the apex 2.0 rom did it to someone else as well on another forum
Also, do you guys know how to get back the blur social network apps such as friendfeed, or whichever app it was that adds your friends social network updates to their contact numbers on your contacts? Most people don't like it, but I think its a pretty awesome built in feature
Click to expand...
Click to collapse
Thanks, made the note to the tutorial. I haven't noticed the issue with the battery, but I do know that this is one of those roms that seems to jump in increments of 10 for the battery which is kinda weird. That said, i only used it about a week on CM7 before switching over to the Apex rom (and haven't noticed that issue on the apex rom).
Don't know about blur, I didn't use the original OS at all. That said, you can do what the guy above did and wipe the phone, upgrade all the way to gingerbread, do a nandroid backup then follow the original instructions but use that backup to restore to, which should have the full motoblur functionality. Thats just a guess though, haven't tried it myself.

------------------

Could you re-up just the Kernel file? I've followed your instructions to the T and every time it seems that I have a problem at that step.
I've gotten to Flashing the Kernel VIA CWM, and when I try to restore the backup of CM7 via \clockworkmod\restore\ folder - it will say MD5 mismatch.
Also, if I skip the restore portion of CM7 and just try to reboot the phone after flashing the Kernel, I will be stuck at the red M.
I've tried rebooting the phone right after applying the band unlock (all after SBF + Wipe data), and the phone will boot up just fine if I skip flashing the Kernel (again I leave it in zip form and install it via CWM).
I’ve already unlock my SIM via code provided by VZW (I am a VZW customer in good standing)
While stuck at the red M, I’ve done a battery pull and tried to enter Recovery mode by pressing M+R+Power, and the recovery screen that is booted up doesn’t look like it’s compatible with the phone. I can almost describe it as a bunch of white horizontal lines of what the menu should be, and all the menus and the green android are skewed diagonally to the right/and also looks like it’s double or triple vision.
I know a very similar process works for the D2G, because I have successfully performed and tested it on the D2G on one of my other lines.
Any help is greatly appreciated. I can stick with Froyo, but I’d like to have GB.

Try redownloading the CM7 backup, it might be a corrupted download. If that doesn't work, try the APEX file. But, yes, you cannot reboot without restoring a gingerbread backup or you'll have to start over again (there's ways to get back to the cwm but i'm not sure how, I did it accidently a few times).

Thanks I am a complete noob
So it turns out the problem is when I unzipped the Backup that it created sub folders "\nandroid\restore\xxxx\xxx\backup\restore\"
Just to save everyone headaches, make sure the when you unzip the file into your backup folder that the name of the next folder down is the series of numbers that represent the name & number i.e.
Should NOT be
\clockworkmod\backup\clockworkmod\clockworkmod\backup\2011-11-27.09.52.03\
but instead SHOULD BE
\clockworkmod\backup\2011-11-27.09.52.03\
My 7zip by default created all those sub directories, which caused the CWM restore not to find the back up files.
On another note, I am having issues with GSM Wifi and 3G.
With a fresh flash & WiFI on - if I connect WIFI first I cannot later add the APN and access Cellular Data
Inversely, If I add the APN first (again after a fresh SBF flash, kernel update, and Backup restore), and connect to cellular data, none of the WIFI connects I make can access WIFI Data
I am going to try WIFI fixer in one of the older threads to see if this resolves the problem.

DROID PRO
Please upload the file in other downloads bc megaupload is temp down

agni said:
Please upload the file in other downloads bc megaupload is temp down
Click to expand...
Click to collapse
If you're talking about the two multiupload files I put up, use one of the other links below megaupload. I just tried the bottom one (wupload) and it worked. If you're talking about RSD Lite and SBF files, I'll see if I can find another link to them, but you can easily find them by searching the forums or google.
**Edit** Edited first post with non-megaupload links.

jraskal said:
On another note, I am having issues with GSM Wifi and 3G.
With a fresh flash & WiFI on - if I connect WIFI first I cannot later add the APN and access Cellular Data
Inversely, If I add the APN first (again after a fresh SBF flash, kernel update, and Backup restore), and connect to cellular data, none of the WIFI connects I make can access WIFI Data
I am going to try WIFI fixer in one of the older threads to see if this resolves the problem.
Click to expand...
Click to collapse
Let me know how that worked out. I stopped using CM7 and switched to Apex because of the Wifi/Cellular switching issues of the november cm7 rom.

bveditz said:
Let me know how that worked out. I stopped using CM7 and switched to Apex because of the Wifi/Cellular switching issues of the november cm7 rom.
Click to expand...
Click to collapse
Can you provide a link to the Apex rom you're using?

aaevann said:
Can you provide a link to the Apex rom you're using?
Click to expand...
Click to collapse
Theres an apex thread on xda that links to the rom http://forum.xda-developers.com/showthread.php?t=1292506

[Q] Custom Kernel Problems, HELP!

OK, here it goes.
I have a R800x CDMA Verizon Xperia Play
I had bootloader unlocked successfully by alejandrissimo.
I am rooted.
Today I decided to try the MIUI rom for CDMA.
It required custom kernel, and recommended Kieren's darkforest kernel.
I installed that kernel via fastboot with no problems.
Upon turning on phone, i get a page that says Sony, then I get ANDROID page.
Then it just stays on ANDROID. I can tell that it is not frozen because I can see the waving lines going across.
SO, I decided to just go back to stock kernel then try again.
BUT, I cannot get into fastboot!!
I hold search while connecting usb, and the led blinks blue once, then continues with boot.
I am at a loss.
I Can get into CWM.
Please Help!
Edit: I just noticed that after holding search then plugging in USB, the light blinks blue once. Then about 25 seconds later, the light turns solid blue for about 3 seconds. Then just to orange for charging. During this time, I can not get fastboot to recognize device, nor does my computer recognize any devices.

OK, first - don't panic! I had some issues myself with this, but it's easy to resolve.
First - if you want to return to stock, the easiest thing to do is to download flashtool from this link:http://androxyde.github.com/Flashtool/
And the FTF of the stock ROM from here: http://www.mediafire.com/?u70ci3bdzak3u9e
Follow the directions on the Flashtool website for how to flash back to stock. This will make your phone just like it came out of the box. It does not touch the SDCard.
Second - Make sure the kernel you flash in fastboot is the one intended for the ROM you want to install. Also make sure you copy the zip file of the rom you want to install onto your sdcard. Then enter into CWM and do the following:
- clear data
- clear cache
- clear Dalvik cache (under the advanced menu)
- clear Battery Stats (same menu as above)
Then use the menu "install zip from sd card" (or whatever it says ) find the zip file you copied onto you card and load it. Reboot when finished and you should be good to go. Please be aware some ROMS take a long time to boot up the first time around.
Good luck.

netizenmt said:
OK, first - don't panic! I had some issues myself with this, but it's easy to resolve.
First - if you want to return to stock, the easiest thing to do is to download flashtool from this link:http://androxyde.github.com/Flashtool/
And the FTF of the stock ROM from here: http://www.mediafire.com/?u70ci3bdzak3u9e
Follow the directions on the Flashtool website for how to flash back to stock. This will make your phone just like it came out of the box. It does not touch the SDCard.
Second - Make sure the kernel you flash in fastboot is the one intended for the ROM you want to install. Also make sure you copy the zip file of the rom you want to install onto your sdcard. Then enter into CWM and do the following:
- clear data
- clear cache
- clear Dalvik cache (under the advanced menu)
- clear Battery Stats (same menu as above)
Then use the menu "install zip from sd card" (or whatever it says ) find the zip file you copied onto you card and load it. Reboot when finished and you should be good to go. Please be aware some ROMS take a long time to boot up the first time around.
Good luck.
Click to expand...
Click to collapse
ok, small problem with that.
when I click to install flashtool, it tells me that it is not available for my region (Central USA).
I do have a nandroid and titanium backups made just before flashing.

Use this link - I forgot about their link blocking us. But use that site for instructions.
http://www.mediafire.com/?t2pxz1j7snieeos
Having just unlocked my bootloader this weekend as well, I don't know what to tell you there. But since you can get into CWM, reverting to stock is a good way to go. Then try flashing the firmware, etc again.

still stuck
netizenmt said:
Use this link - I forgot about their link blocking us. But use that site for instructions.
http://www.mediafire.com/?t2pxz1j7snieeos
Having just unlocked my bootloader this weekend as well, I don't know what to tell you there. But since you can get into CWM, reverting to stock is a good way to go. Then try flashing the firmware, etc again.
Click to expand...
Click to collapse
OK, thanks for your help, but I am still stuck.
I can not get the device to be recognized.
So, now I need an alternate method.
I will attach the kernel that I flashed, maybe I could flash a ROM that could be compatible.
I tried to flash MIUI v4 from near the end of the MIUI port for CDMA thread (pg 9, I think) , which paxchristos and a few others reported working fine for the R800x
I flashed the kernel that was listed to use in the same post.
But, when I tried to flash the ROM, CWM told me that it was not compatible with my device. It checked the ro.build.fingerprint and determined that it was not compatible.
Maybe another rom would work, and then I would be able to work on it from there

zeeky120 said:
OK, thanks for your help, but I am still stuck.
I can not get the device to be recognized.
So, now I need an alternate method.
I will attach the kernel that I flashed, maybe I could flash a ROM that could be compatible.
I tried to flash MIUI v4 from near the end of the MIUI port for CDMA thread (pg 9, I think) , which paxchristos and a few others reported working fine for the R800x
I flashed the kernel that was listed to use in the same post.
But, when I tried to flash the ROM, CWM told me that it was not compatible with my device. It checked the ro.build.fingerprint and determined that it was not compatible.
Maybe another rom would work, and then I would be able to work on it from there
Click to expand...
Click to collapse
Yeah, that seems to be the wrong boot.img. It should be called boot-v2.img.
EDIT: WOW - I just reread your post after posting mine and realized I pointed you to the same spot!
Try this ROM which is a version of CM9 that Chevyowner got working for our R800x. I know it works because I'm using it. http://www.mediafire.com/?1xnh54i6lvnnh73

It is the same one, i just renamed it because i thought kernels had to be boot.img to flash correctly. I will try that rom when i get home.
Sent from my T100 using XDA

zeeky120 said:
It is the same one, i just renamed it because i thought kernels had to be boot.img to flash correctly. I will try that rom when i get home.
Sent from my T100 using XDA
Click to expand...
Click to collapse
just an fyi, you can name kernels whatever you feel like (I'm not sure about spaces, I use linux, so I never have spaces in names anyways )
Sent from my R800x using Tapatalk

Flashing now
OK, I just downloaded and flashed the ROM about 3 minutes ago.
I cleared everything just like you told me to.
It installed with no errors.
You may be right about long boot times for first boot, otherwise I have a really bad kernel.
It has just sat on Sony screen for the past 10 minutes.
It hasn't even went on to the android page that I got before.
Hoping that it will Work.
Assuming that it doesn't, what would be my best next move?
Can I flash a kernel (Such as doom_lord's CDMA Kernel) via clockwork?
I think I saw a video about it for the Samsung fascinate, however I seem to recall something about needing an s2 file or something??
I will update as soon as I get something. (hopefully good news)
Update: It has been about 20 minutes now and still on Sony screen.
Now it has been 30, im starting to get worried. Should I plug in? Should I just let it be? Should I let it die? Should I battery pull?
Major Edit: I got impatient and just battery pulled. I then tried to get into CWM, but failed. THen I got a bright Idea, why not try fastboot with the new rom. IT WORKED. I WILL NOW TRY TO FLASH A NEW KERNEL AND SEE IF THAT HELPS.

it should not take 30 minutes to boot, only thing i can think of right now is to redownload kernel (boot-v2.img) and reflash that.

chevyowner said:
it should not take 30 minutes to boot, only thing i can think of right now is to redownload kernel (boot-v2.img) and reflash that.
Click to expand...
Click to collapse
is this your kernel, or someone else's? If it's yours/you have a working copy, could you post an md5 so the op can double check it?
Sent from my R800x using Tapatalk

nope not my kernel, and i doubt i have an original working copy as i added 2 lines so i could mount my sdext partition.

Finally!
OK, I am now back up and running.
I went through every kernel and rom for CDMA play, and got nowhere.
I ended up getting Doom's kernel to run. It worked, and booted to android... Then stayed at android.
Then I decided to flash my nandroid i made, and am now working on stock rom W/ DoomKernel.
The ROM seems to be lagging a lot.
Since everything is *working* now, what kernel/ROM combo can anyone verify working for the Play R800x CDMA.
I would really like CM9 or ICS based roms.
Thanks for your help getting me out of this mess!!
EDIT: Nothing seems to be working!! My touchscreen seems to be non responsive, no phyiscal keys except for the power key seem to be working with my original ROM now!!! Maybe somebody could attach a copy of the stock kernel for my device, so that I could start from scratch.

If you're using keiran (darkforest) cm9 kernel the md5sum for it should be: 74a5be2bf95322b8c45780d9daeda4fa
Sent from my R800x using Tapatalk

zeeky120 said:
Nothing seems to be working!! My touchscreen seems to be non responsive, no phyiscal keys except for the power key seem to be working with my original ROM now!!! Maybe somebody could attach a copy of the stock kernel for my device, so that I could start from scratch.
Click to expand...
Click to collapse
This site has some of the stock FTFs, just extract the kernel.sin from the R800x one http://www.xperiagamer.com/Stock-Roms/233-se-stock-firmware-for-root.html

kernel.sin: http://www.mediafire.com/?e29j13d9wpgdvoj
md5sum: 45116201967408d70895ef63c500ed1e

@zeeky120 - I'm sorry you're having so many problems. For me when everything seemed hosed, I started over by using Flashtool and flashing the ftf file I gave you links for. Then once it came back up as stock, I started again from scratch. Depending on what your goals are, you need to flash the proper kernel for that. Then get into CWM. Clear DATA, CACHE, DALVIK CACHE before you do anything else. Then load via zip file the rom you want to install, making sure it matches the kernel you loaded. And, whether necessary or not, I always wipe the big 3 again, just in case. (Call me paranoid, but it helps! )

Ok now up and running on stock everything working great just like out of box. The only thing I have done so far is to root. I want to do it right this time. I would like to flash cm9 based miui for r 800x. Could anyone provide detailed step by step instructions and links for download. Thanks in advance.
Sent from my R800x using xda premium

Closing Notes
This thread has reached its end, because my problem has been fully solved. Advice to future users, always clear the big three, and when in doubt: use flashtool to reboot the ftf. Right now I am up and running on CM9 (use the link in Chevy's signature to download. I can verify that it works great on CDMA. (faster download speeds than stock!!!) Thanks for everyone for all of their help, and I hope to be contributing to development in the near future.

[Q] Flashed update, now I have a blank screen

Hey all -
I have a T-Mobile Galaxy SIII with TWRP, AOKP JB Milestone 5 and GooManager. I got a pop-up for AOKP JB Milestone 6 this morning, so I downloaded it and added that file, Lean Kernel 2.9 and gapps (latest that could be downloaded) to the flash list. I set my Dalvik cache to clear before flashing anything, then rebooted the phone to flash everything. Immediately after the flash, the phone seemed to reboot, but with a blank screen. After a while, the capacitive buttons on the front started working and when I plugged the phone into my computer the file transfer program popped up.
However ... at no point can I ever get anything to display on the screen. I've tried rebooting into recovery (volume up, home button, power button) and nothing. I don't really care about the data on my phone, I have proper backups of everything. But what I can't seem to do is get it to a point where I can recover it. What are my options here if rebooting into recovery doesn't work?
Thanks!

As an addendum, the phone is clearly booted into the OS. I have a blinking notification LED that indicates a new e-mail, and calls placed to the phone cause it to ring. I just can't see .... anything on it.

I was able to get into TWRP, somehow. I took out my T-Mobile SIM card and had it plugged into USB. I held down the recovery combo and then it booted up into recovery. It also displayed the Galaxy SIII white splash screen for the first time since the bad flash. What the hell.

chuffykow said:
I was able to get into TWRP, somehow. I took out my T-Mobile SIM card and had it plugged into USB. I held down the recovery combo and then it booted up into recovery. It also displayed the Galaxy SIII white splash screen for the first time since the bad flash. What the hell.
Click to expand...
Click to collapse
so was you able to use your phone again i say go back to a nandroid you have or flash a rom that you know works good on your phone without that white screen and trouble shoot from there that it very strange indeed if you get success with the other just try posting in the ROM thread that you flashed you could possibly get more help where it happened :good:

I went back to AOKP Milestone 5 after doing a full wipe. I saw a number of graphics changes in the Milestone 6 code review, so it's possible that had something to do with it. In any case, I'm no longer panicing

Does mr6 use the 3.4 kernel? If yes, then you were using the wrong version of leankernel.

Ya its all kernel related and user error.

Aerowinder said:
Does mr6 use the 3.4 kernel? If yes, then you were using the wrong version of leankernel.
Click to expand...
Click to collapse
mt3g said:
Ya its all kernel related and user error.
Click to expand...
Click to collapse
I assumed it was user error. I just wanted to lay out the steps I took, so I could get some help on a recovery path. I thought that a JB based ROM would work with any kernel that supports JB. Looks like I was wrong.

chuffykow said:
I assumed it was user error. I just wanted to lay out the steps I took, so I could get some help on a recovery path. I thought that a JB based ROM would work with any kernel that supports JB. Looks like I was wrong.
Click to expand...
Click to collapse
Nope, JB can be AOSP, TouchWiz, 4.1, 4.2, 4.2.2, 3.0 kernel, 3.4 kernel. Just need to read and make sure you know what you're doing before just doing it. That's why I frown at people being lazy (not just you) and not reading the forums and such, and just using apps to update and flash.

mt3g said:
Nope, JB can be AOSP, TouchWiz, 4.1, 4.2, 4.2.2, 3.0 kernel, 3.4 kernel. Just need to read and make sure you know what you're doing before just doing it. That's why I frown at people being lazy (not just you) and not reading the forums and such, and just using apps to update and flash.
Click to expand...
Click to collapse
Thank's for the condescension, I appreciate being called lazy. I might not have an encyclopedic knowledge of Everything Android, but between the knowledge I do have and the details I read on the AOKP release page, I saw nothing that indicated I _couldn't_ run LeanKernel, especially when it was only a point release on the same ROM I was previously using.

I had a look at the changelog that's available on their page. It's pretty lame. http://gerrit.sudoservers.com/#/q/status:merged,n,z that one will probably have the kernel info. A good rule of thumb is when you flash a new rom, wait until the kernel is up to date (release date). For instance, don't flash a 3/01 kernel on a 4/24 rom - wait for kernel update.
I don't recommend flashing anything with the 3.4 kernel right now. Even if you manage to pull off stability, it's still laggy and eating about 3x the battery it should. This goes for the custom kernels, too. I'll put up with stability issues, but can't deal with bad battery. Already bad enough as it is. Need my phone during the day and not near a charger.

chuffykow said:
Thank's for the condescension, I appreciate being called lazy. I might not have an encyclopedic knowledge of Everything Android, but between the knowledge I do have and the details I read on the AOKP release page, I saw nothing that indicated I _couldn't_ run LeanKernel, especially when it was only a point release on the same ROM I was previously using.
Click to expand...
Click to collapse
calm down lol, you could have read up any of the kernel threads that there are some compatible issues with kernels and roms right now.

Aerowinder said:
I had a look at the changelog that's available on their page. It's pretty lame. http://gerrit.sudoservers.com/#/q/status:merged,n,z that one will probably have the kernel info. A good rule of thumb is when you flash a new rom, wait until the kernel is up to date (release date). For instance, don't flash a 3/01 kernel on a 4/24 rom - wait for kernel update.
I don't recommend flashing anything with the 3.4 kernel right now. Even if you manage to pull off stability, it's still laggy and eating about 3x the battery it should. This goes for the custom kernels, too. I'll put up with stability issues, but can't deal with bad battery. Already bad enough as it is. Need my phone during the day and not near a charger.
Click to expand...
Click to collapse
Thanks for the tip! I appreciate it.

Blue screen after kernel flash

What's up everyone? I am having a strange problem when trying to flash just about any kernel on my N7. While I'm not a developer or anything, I'm not new to flashing ROMs or Kernels by far. In fact, my love affair with smartphones began when I got an HTC Apache with Windows Mobile 5. Anyway, every time I try to flash a kernel, it will show successful, and then the phone will boot into a fuzzy/pixelated light blue screen. Eventually, this screen will go away and my device will be pretty much locked up. All the images will have turned blue and orange, and the only way for me to get back into recovery will be to hold volume down + power, until the phone shuts off. The only kernel I have had any success with is Glitch, and I have even had this happen with it a couple times.
I always make sure to read through the instructions, and have done lots of searching here, and via Google. After I flash a rom, I will make sure the N7 boots up, and works properly, then reboot into recovery, do a full wipe, and flash the zip from TWRP. My most recent attempt was with Buttered AOKP w/Aroma installer. It walks you through the steps in a manner that should make this easy for anyone. It give you the option to wipe cache and kernel, which I always do, but no go. The only way I can get Glitch to run on it, is to complete the whole process twice.
Sorry if the answer is right under my nose, but I couldn't take it anymore and had to ask. I've never once bricked a device, nor have I had issues flashing kernels on any device before. Somebody please restore my sanity!!! I didn't have much to begin with.

yamus08 said:
What's up everyone? I am having a strange problem when trying to flash just about any kernel on my N7. While I'm not a developer or anything, I'm not new to flashing ROMs or Kernels by far. In fact, my love affair with smartphones began when I got an HTC Apache with Windows Mobile 5. Anyway, every time I try to flash a kernel, it will show successful, and then the phone will boot into a fuzzy/pixelated light blue screen. Eventually, this screen will go away and my device will be pretty much locked up. All the images will have turned blue and orange, and the only way for me to get back into recovery will be to hold volume down + power, until the phone shuts off. The only kernel I have had any success with is Glitch, and I have even had this happen with it a couple times.
I always make sure to read through the instructions, and have done lots of searching here, and via Google. After I flash a rom, I will make sure the N7 boots up, and works properly, then reboot into recovery, do a full wipe, and flash the zip from TWRP. My most recent attempt was with Buttered AOKP w/Aroma installer. It walks you through the steps in a manner that should make this easy for anyone. It give you the option to wipe cache and kernel, which I always do, but no go. The only way I can get Glitch to run on it, is to complete the whole process twice.
Sorry if the answer is right under my nose, but I couldn't take it anymore and had to ask. I've never once bricked a device, nor have I had issues flashing kernels on any device before. Somebody please restore my sanity!!! I didn't have much to begin with.
Click to expand...
Click to collapse
Flashing a CAF kernel on an aosp Rom or a aosp kernel on a CAF Rom. What Rom are you on? (cynanogen based roms are CAF)
Sent from my Nexus 7 using Tapatalk 4

xfrancis14 said:
Flashing a CAF kernel on an aosp Rom or a aosp kernel on a CAF Rom. What Rom are you on? (cynanogen based roms are CAF)
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Currently on: [ROM] Buttered Flo AOKP 4.3.1 [+Aroma] [2013-10-12]
It has all the kernels built into the aroma installer, so I would assume they are all compatible. Some more than others.
I got 3.4.1 Glitch-Flo to run on it, but had to return phone to stock, and flash twice, to get it to work. The aroma installer also has the option to use Faux Kernel in one of three flavors. I tried the "Ultra CCCCCCOMBO" first, and then the "Enhanced Stock", but no go.
When I go to the thread for both kernels, it says they are CAF kernels, but it's kind of strange they they would be included as an option in the rom. I have tried a few other roms, with various kernels too, and not had any luck. I want to get a log to post, but I'm not sure if I will be able to pull it via ADB, when the device is pretty much unresponsive.
Thanks for your response, and let me know if what you think about the CAF kernels being inlcuded with the AOKP rom.
Thanks,
Yam

Sooooo..... Isn't aokp based of the cm kernel? If that's the case, any of the kernels I am trying should work. I would post this in the ROM thread, but its happened with just about every ROM kernel combination in have tried. What's the dealio

Any update on this? I am having the exact same problem with my Nexus 4 running ProBAM 2.0 ROM. I have tried flashing every kernel and every version possible and it either freezes before boot (Google logo) or I get the blue screen... help anyone? I really want to flash a kernel with FauxSound, that's really all I want. Thanks so much!