[Motorola Photon 4G] thundercles:
****!!!!! Testers only******!!!!!

-Disclaimer-

This is an untested build, my phone is very very bricked (again) and might need to be exchanged again (still in the 30 days). I usaully flash anything to my phone to ensure it boots before putting out for testing, but I can't right now. Also testing is now available to the public, but beware, only put this on a phone with intent for testing, I don't even know if this will boot, but pm/e-mail me if it doesn't and I'll put together a different image.

I take no responsibility if this ****s up your phone, it's not an sbf so I don't think you can **** yours up any more then I have mine ;) Don't see any reason why it shouldn't work though.

-/Disclaimer-

*Also, I could really use help packing up images, at least two thirds to three fourths of my time is just doing tedious packing and unpacking of images and associated files, most of the rest of the time is spent involving doing the initial testing, which is why I'm no longer doing that either, maybe 5-10% of the time has been spent actually doing anything new or productive, so one person who could help put together the actual images would be appreciated. packing/unpacking sbfs and checking/modifying the META-INF before zipping up a rom, and reading/editing .img files (cpio,yaffs2 blah blah) if most of that makes sense to you and you want to help cause you have spare time over the next week or two and all that, get ahold of me, I'll get you up to speed on any of that stuff you don't know enough about, there just isn't enough time in a day for one person to handle all that and all the system/kernel building too.

E-mail address is my name here @gmail.com (nobots/nospam) I think my facebook and instant messanger accounts are in my profile, those are faster ways to get ahold of me then PMs.

special thanks to: Dsimms for the box, and shabbypenguin for idling on IRC all the time.

----begin transmission-----

Uploading Rom image to google docs, please test ASAP:

test notes:

This is a full system compile from KDDI source code after I patched the motorola source so it would compile. This only included open source items and code directly derived from the google vanilla source code 2.3.4_r1 so I unpacked the system.img from the oldest sbf I could find on the internet, hopefully it is old enough that these builds are still compatible with the supplemental software.

This is a zip file with meta installer so install through custom recovery, will wipe and replace /system

Don't forget to wipe cache.

Report back what the results of this are, you can play around with various kernels and see what does or doesn't work. If it wont boot, let me know right away so I can put something else togther, if it boots, this is the baseline I'm working from.

If it boots and doesn't view domestic GSM networks, let me know because I had to leave .odex files from the original build in that I wanted to remove, but I applied my changes before deodexing, so I don't know whether it will load the odex or the apk versions. It is probably using the odex versions or the baseband is too new if it wont see GSM networks.

The best way to test this is to flash back to a 154 baseband sbf image in rsd mode. I'm not certain if this will work on the updated basebands, if anyone can flash back to the 154 baseband or still has a photon on that baseband please let me know cause you're tests will be priority.

ty seth "tcles"

https://docs.google.com/open?id=0BwH9o3eKmuZsN2NmZDg1OWQtYzg5Ni00ZDA1LWIyNjUtMzU0Nzg4MjE2MjBj

will put out an accompanying boot.img and/or zImage, for now I don't see why any kernel compilation that includes the tegra source from Motorola's open source release wont work, I'm fairly certain the lock is located within the system apps/framework but the kernel still needs to have the correct drivers which the tegra source tree on that release has. The baseband may or may not be an issue, the last baseband that has ever been on a carrier unlocked phone to my knowledge is the one that comes with the 154- prefixed releases. KDDI hasn't released any firmware since then, so I don't know whether or not they began customizing the basebands to support sprints desire to carrier lock these phones or not after that. I might try contacting sprint directly for answers regarding the baseband if needed, I paid full price for my phone so under normal circumstances they wouldn't have any reason to not give me an unlock code if that were an option with this phone*.

*which it isn't, putting in a non-sprint simcard doesn't lock the phone, it simply can't see other networks. This is why I could make the claim that it has been carrier unlocked since the AT&T sim card the tester used was able to enter E911 mode which typically can't even be done, I don't know what they did to other kernel releases to block the sim card outright, but a custom compiled kernel should allow E911 access like mine did, E911 would likely bypass any blocks in the software because there are federal mandates around phones' ability to make emergency calls.

-----------end transmission-----------

good luck, I'll make changes and updates as fast as I can and as fast as I get feedback, so if you are giving feedback check back often.