State of Development on R800x (ROM and Kernel List)

Because what the world needs now is another R800x related thread.

I'm going to try to document all of the kernels and ROMs posted currently about the forum and exactly what they will or will not do when used in their current state on the R800x. This thread will be for developers to help figure out issues related to the CDMA differences and for end users trying to figure out what works or doesn't.

Please post your experiences with testing different builds and kernels. Also, if applicable, post any software that you were able to remove with root and if you ran into any complications because of the removal.

Note that this can also serve as a directory for GSM users as well. Just disregard the comments and do diligent research.

If you are not using a custom kernel (and you're probably not at this point because of how poorly they are responding) then you will need to run this command to make your system read/writable so that you can remove apps:

If you have not already done so, download Omnius! Backup your TA file. This can save a lot of headaches in the long run for everyone!


Root

Basic Root Steps
Link: R800x Root
Status: Steps to follow if you have an unlocked bootloader....

zergRush Root Method
Link: [HOW-TO] Root R800x/i v2.3.3+ (zergRush Method)
Status: Instructions for rooting without a unlocked bootloader. Works on stock 2.3.3.

Bin4ry's Original Root
Link: [How-to] Root your Play
Status: No. Bin4ry's file contains the entire system for the GSM plays. This is an original rooted generic system build. Do not flash this.


Kernels

DooMLoRD's CDMA Kernel
Link: [KERNEL][PLAY][CDMA] DooMKernel [Rel:v01][Dt:30/Nov][FW:3.0.1.A.0.145]
Status: Currently in very active development, check the thread for most recent updates and information about whether this will work for you. Probably most recommended for stock ROM.

Blagus' SEtweak Kernel
Link: [Kernel] SEtweak - insecure ADB, ext4, NTFS, overclock, USB OTG - updated 24th July
Status: Boots stock ROM. Unusably slow. Root shell in adb.

DooMLoRD's GSM Kernel
Link: [KERNEL][PLAY][GSM] DooMKernel [Rel:v08][Dt:17/Nov][FW:4.0.2.A.0.42]
Status: Newest Doom revision will boot stock 2.3.3 system without wifi or camera. Version 3 of the kernel will allow you to use both of these items. Will also boot other systems with same results.

FreeXperia's (jerpelea) Kernel
Link: [DEVELOPMENT] - CM7.1.0 - FXP041 RELEASED - FreeXperia Project
Status: It works like it should for the most part. Regressions in and out on camera, but overall stable. Used for CM7 only.


Roms

Stock ROM
Link: Check stock section below for downloads
Status: Boots and roots with everything available to use as it should be. See kernel info above for finer points to it. Stock ROM is easily rootable.

FreeXperia's CyanogenMod 7.2.0 CDMA
Link: {GSM/CDMA}[DEVELOPMENT] - CM7.2.0 - FXP049 RELEASED - FreeXperia Project
Status: Newest builds work almost 100%. If you are having camera issues, check out this post and apply the linked update.zip. You should have a working system with everything except MMS. And even the MMS is hit or miss. So give it a try.

ZeroROM
Link: [ROM] zerorom v0.4 (GSM/CDMA, CWM Install)
Status: Boots great using Doom's kernel, however, system is based on 4.0 series generic GSM roms and the radio doesnt function yet. Work in progress.

UK ROM For R800x
Link: [CDMA][ROM] R800x with UK firmware

Status: Work in progress but good reports about it running great. Check out thread for most current information and build data.

FrAsErTaG's FTS
Link: [SYSTEM] FTS v05 ONLINE [FINAL] DooMLoRD Kernel Compatible
Status: Seems there is lots of success with new patches and some minor tweaks starting about there in the thread. Well suited for using as a daily driver at this point with the tweaks. Easiest method is just flashing the awesome nandroid backup zero_1_2 made.


Requests

Kernels for 2.3.3


Back to Stock

Stock Kernel 2.3.2
Link: Attatched to this post
Status: Its the stock kernel. So of course it works just fine. Flash the same as you would any kernel: fastboot flash boot kernel.sin

Stock System 2.3.2
Link: Multiupload
Status: Should work just fine. This is just the .sin. Use this command: fastboot flash system system.sin

Stock System 2.3.3
Link: DropBox
Status: Untested system img. Use this command: fastboot flash system system.img

Stock Kernel+System TFT 2.3.2
Link: Multiupload
Status: Should contain a tft file with the kernel and system. From what I understand this is not the complete restore?

Full system FTF 2.3.2
Link: Multiupload
Status: Full system restore tft. This should bring you back to 100% stock (minus the bootloader being returned to locked)

Full system FTF 2.3.3
Link: Multiupload
Status: Full system restore tft. This should bring you back to 100% stock (minus the bootloader being returned to locked)

All Original System APKs
Link: Multiupload

MD5 Values for Stock Items
This isn't an optional check. The following values must match up or you need to download the file again.


Potentially Safe to Remove Applications

Users have personally removed and verified the following apps. Removing all of these will take every Verizon application out of your menu. And all of the games. Except for Crash. Because, honestly, who doesn't want to keep Crash.

I remove all of these apps completely (cause I live on the edge like that and I dont mind flashing a system file) but you are also free to simply rename the package and put .old on the end of it or something similar. The point will be served to get them out of your menu, but it, of course, wont clear up any of the precious little space we have. It saddens me to have to say this but I think its wise to remind everyone: you are not required to remove all these applications. If you don't know what you are deleting, don't. If you still manage to screw this up, the apps are all linked in the stock section above.

1. /system/app/starbattalion.apk
2. /system/app/Asphalt.apk
3. /system/app/madden.apk
4. /system/app/Sims.apk
5. /system/app/tetris.apk
6. /system/app/com.skype.android.verizon.apk
7. /system/app/com.fusionone.android.sync.sonyericssonr800xbaclient.apk
8. /system/app/com.vzw.vvm.androidclient.apk
9. /system/app/com.amazon.kindle.apk
10. /system/app/com.vznavigator.r800x.apk
11. /system/app/com.gravitymobile.vzwinstaller.apk
12. /system/app/com.gravitymobile.app.hornbill.apk
13. /system/app/Launcher2.apk
14. /system/app/Camera.apk
15. /system/app/com.vzw.hss.myverizon.apk ##This one has to be done last. If your phone is running, prepare for it to hate you. Reboot after its gone and you should be alright.

There is a more comprehensive guide here but together by sonicfreak360. Check it out.

Tips or Tricks

Question: Cant boot or pass the Sony Ericsson logo? Can you still get into fastboot (power off and plug in USB with search button held)?
Status: Check out the post made by gwaine later on in the thread

I seem to now be unable to install anything from the market at all. It doesn't go past the "Starting download..." step. my logcat is filled (literally hundreds a minute) of this error: Waiting for service drm.drmManager... I'm betting its related. But I dont know if its due to the kernels or due to the DRM partition getting erased at bootloader unlock time. This poor device has gone through every kernel and rom available in the last two hours. Such a hoss, she is.

Ash, just flashed the "stock" kernel you have on your thead. Where did that come from? And did it come with root?

I just tried pretty much every combination of kernel and rom. I just flashed back that kernel I just mentioned in my edit (the stock one you posted) and then wiped in CWM and recovered my original backup and now its clean. Market downloads are working. And that error is gone out of the logcat.... it must be something thats different about the CDMA builds.

But did that kernel file you post have root pre built into it? Because I appear to still be rooted...

ashergray said:

Nope it was a stock kernel.sin I pulled from blob file. The thing is, you keep root after kernel flash. Nifty huh?

Click to expand...

Click to collapse

Yeah it sure is. The backup I restored was made right after I flashed the first thing, which was Doom's kernel. Looks like that kernel actually copies the su and superuser programs into the system as opposed to running them from the kernel persistently (like CWM or busybox or the other neat tricks he had up his sleeve with that kernel because apparently none of them are still on my phone, just su and superuser). So basically I'm back to where i would have likely ended up just doing these steps:

1. Unlock Bootloader
2. Flash system zip file from Bin4ry for root

But I have compiled a kick ass list so far of my journeys. Cant wait till the CM nightlies start dropping. Bet there will be a good chance that they run fine right out the gate.

Also note that the freexperia kernel for cyanogen was the only custom kernel that didnt have the "slow" feeling on the stock rom, and the stock rom was the only rom that had the slow problem at all it seemed because frasers worked fine with all of them, i just had the issue with the market, but again thats probably due to the kernels.

Also, in regards to the roms feeling slow, we talked earlier about it maybe being a clock issue. But it doesnt seem like it is. I've never seen response times this bad. I also cat checked all the proc info for the cpu and could see that at its low end it wouldnt have been dropping below 200mhz. although slow i would have at least been able to load the launcher, which is something that I am yet to get on these at all. top isnt being very responsive so its hard to see whats going on there and the only output i was seeing from logcat was the stupid DRM error i was having. phew.....

time for bed.

I do have one, just not with me at the moment. I have it on a windows computer at work ready to go. Had it around since the time I tried to flash the GSM TA to my first play. Three plays later...

Awesome work and progress tonight. All downhill from here.

crono141 said:

The stock kernel attached is a .sim file. Are these flashed in the same way as a boot.img file?

Code:

fastboot flash boot kernel.sim

Click to expand...

Click to collapse

Yes sir, but it's ".sin", not ".sim." Just didnt want you tearing your hair out over that

Also, I am yet to have any success with just a straight fastboot command like that. I always put in the USB identifier, so it would look more like this:


Probably doesn't matter if you can get it to go the other way though, it should be the same thing and its probably related to the way my hardware is setup.

axiom, i dont know if anyone has tried that one yet but jellofreak tried the full system image from Bin4ry's post which did a similar thing. it flashed the entire r800i build on his r800x without issue. he says there are a few bugs here and there but over all usable.