i noticed the droid x2 only supports two touch points is it possible to enable more like some devices seem to be able to?
That would be really nice! Would make emulators a lot more playable.
Took down this information because it was causing some people to lose touch response. Until we figure out why that is, I'm leaving it off.
navenedrob said:
You can fix this yourself, it is really easy... actually I'm already doing this in some Atrix ports that I am working on, because while looking through portable ROM's I found a mod to enable more multitouch points! You can do it right on your phone, with something like Root Explorer that has a built-in text editor and can remount your /system read-write. If you can't mount within your app just do mount -o remount,rw /dev/block/mmcblk0p12 /system in terminal emulator or adb.
The files you need to modify are:
/system/etc/touchpad/21/touchpad.cfg
and
/system/etc/touchpad/22/touchpad.cfg
Open both of those up and modify this line NUMTOUCH=2 to NUMTOUCH=10. That should get 4 for sure, and 5 points I think.
Also, you might try adding:
ro.product.max_num_touch=5
to your build.prop, in addition, just in case.
Click to expand...
Click to collapse
Could you add all of these brilliant things to the roms?
Watch out, just tried these edits & had restore system from my nandroid cuz I lost all touch response.
Sent from my DROID X2 using xda premium
garywojdan81 said:
Watch out, just tried these edits & had restore system from my nandroid cuz I lost all touch response.
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Worked fine for me.
Sent from my DROID X2 using xda premium
Wow this is exactly like the ATRIX. Im sure if you dig up the flushable zip and with very little modification, if any, you could use that
Sent from my DROID X2 using xda premium
I modified the .cfg files, but still only have two inputs. I didn't add the line to the build.prop, but I will tomorrow (after making a nandroid, just in case) and see if that works. I did notice that, in addition to the normal .cfg files, there's now .cfg.bak files in the folders as well. Is that just a result of me editing the others?
doesnt seem to work for me,I edited the touchpad files first and restarted and I lost a touch point, so it only recognized one point, then I tried adding in the build prop edit,just not sure where to put it exactly, so I just added it in near the top where the ro.products are
Sent from my DROID X2
After restarting this morning, I've lost all touch points. Any way to fix this without nandroiding?
stick1300 said:
After restarting this morning, I've lost all touch points. Any way to fix this without nandroiding?
Click to expand...
Click to collapse
I don't think so, but if you do an advanced restore you can just load the system partition backup w/o affecting your total setup. When I did it last night it just put me back to square one before I debloated, but apps & data were undisturbed.
Sent from my DROID X2 using xda premium
stick1300 said:
After restarting this morning, I've lost all touch points. Any way to fix this without nandroiding?
Click to expand...
Click to collapse
This is really weird, I'm running the exact same mod without an issue. Not sure what is going on.
Same Here When Editing Both Cfg And Build.Prop Lost All Touchscreen Response.
You should be able to fix it with the adb if you have USB Debugging enabled, though very carefully.
I just changed the touchpad values, and didn't do anything to the build.prop and I'm fine.
Sent from my DROID X2 using xda premium
mistawolfe said:
I just changed the touchpad values, and didn't do anything to the build.prop and I'm fine.
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
That's what I did and didn't have any problems until I rebooted...
stick1300 said:
That's what I did and didn't have any problems until I rebooted...
Click to expand...
Click to collapse
The reboot is what did it to me.
Sent from my DROID X2 using xda premium
I did the mod.
I only have a single touch point, so I'll be undoing it.
you'd have to look into the touch controller we have in our phones, if they're all the same. They may not support more than 2 inputs.
Example: on the Droid Incredible which i had, there were 2 different controllers used, one supported up to 10, the other only 2.
Is there any progress on this? It would be great to have a solid way to increase the number of touch points.
Related
Has anyone tried this on the X2?
Sent from my DROID X2 using xda premium
Why would we, ours works fine
Sent from my DROID X2 using XDA App
EvilTim said:
Why would we, ours works fine
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
Actually it doesn't. We kinda have to work around a few of the flaws that our recovery has to get it to work "properly." If we ever got CWR, we'd have a bit easier time flashing ROMs. Plus, it's built a lot better, and is more stable.
I have it. However, If the phone is powered down, when I plug it in it boots into recovery. Turn off the phone while plugged in, and it reboots into recovery. Other than that little irritation, it works great.
"You have it' is that system recovery? On a X2? The std one?
Or do you mean the Bionic version?
dragonzkiller said:
Actually it doesn't. We kinda have to work around a few of the flaws that our recovery has to get it to work "properly." If we ever got CWR, we'd have a bit easier time flashing ROMs. Plus, it's built a lot better, and is more stable.
Click to expand...
Click to collapse
Maybe as you are a dev you know things I don't, but to say an official version is more stable when it doesn't exist is a stretch. The only drawback is having to plug it in. I've never had any issues flashing anything so from a USER standpoint it is fine. Your post also fails to address the original post which should probably just be answered with a 'dont use cwm unless it is the one for your phone.'
Sent from my DROID X2 using XDA App
Scur827 said:
I have it. However, If the phone is powered down, when I plug it in it boots into recovery. Turn off the phone while plugged in, and it reboots into recovery. Other than that little irritation, it works great.
Click to expand...
Click to collapse
Open system recovery in app drawer and put it back in charge mode
Sent from my DROID X2 using XDA App
EvilTim said:
Open system recovery in app drawer and put it back in charge mode
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
Just be careful not to do anything that might cause bootloop cause u wont be able to get into cwm by power off and plug in to restore a nandroid
EvilTim said:
Maybe as you are a dev you know things I don't, but to say an official version is more stable when it doesn't exist is a stretch. The only drawback is having to plug it in. I've never had any issues flashing anything so from a USER standpoint it is fine. Your post also fails to address the original post which should probably just be answered with a 'dont use cwm unless it is the one for your phone.'
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
I said IF we get one. From a dev standpoint, it's a little difficult to work with. We can't use all the update script commands we want, for example. Also, ADB is broke from the recovery side, so if we did want to do something manually before/after flashing, we can't.
Sent from my DROID X2 using XDA App
The current recovery for X2 is flawed. If I want to install a new ROM and a wipe is required, once that wipe is complete entering CWM is NOT an option. The recovery apk must be reinstalled to enter CWM. This is a problem if the ROM doesn't properly install, leaving the user high and dry. Only option is to enter stock recovery which is limited.
See instructions further down in thread...
Here is a new one...
http://db.tt/ulgkIjvg
the file is in the Bin folder I believe... but I suggest you don't do it!! I think it hard bricks your phone. I THINK!!!!!! otherwise, I'm sure naven and dragonz woulda changed it in their bootups.
Peperm1nt said:
the file is in the Bin folder I believe... but I suggest you don't do it!! I think it hard bricks your phone. I THINK!!!!!! otherwise, I'm sure naven and dragonz woulda changed it in their bootups.
Click to expand...
Click to collapse
Ya thats what i was thinking...i looked in the bin folder, nothing but i figured if nothing was out there and i looked really hard, then don't mess with it...lol
Changing the splash screen is definitely possible. It doesn't hard brick your phone, and I changed it many times on my tbolt. It just isn't in the same spot on the dx2 it seems.
Sent from my DROID X2 using Tapatalk
I have done this quite a few times and it's not that hard, nor will it brick your phone. If you mess up the worse that will happen is that you'll have a black screen instead of the actual logo. These steps are exactly like the ATRIX and can be found here: http://forum.xda-developers.com/showthread.php?t=1187337
dragonzkiller said:
I have done this quite a few times and it's not that hard, nor will it brick your phone. If you mess up the worse that will happen is that you'll have a black screen instead of the actual logo. These steps are exactly like the ATRIX and can be found here: http://forum.xda-developers.com/showthread.php?t=1187337
Click to expand...
Click to collapse
Ya i was reading that...but does it work on X2? Has anyone tried it?
mattfox27 said:
Ya i was reading that...but does it work on X2? Has anyone tried it?
Click to expand...
Click to collapse
Why don't you do it yourself? Worst case you get a black screen and have to fix it. Just make a backup.
Sent from my DROID X2 using Tapatalk
ilovesoad said:
Why don't you do it yourself? Worst case you get a black screen and have to fix it. Just make a backup.
Sent from my DROID X2 using Tapatalk
Click to expand...
Click to collapse
I have found very little info about the subject i looked a lot so i figure there might simple way to change it without it being a BFD i was just seeing if threre was an easy way to do like just replace a picture so im just waiting to see if anyone has done it or has an more info about before i dive in...that's all
Boot animation in the market
dual core snap dragon beast
homephysician said:
Boot animation in the market
dual core snap dragon beast
Click to expand...
Click to collapse
Ya bootanimations ae no problem, im talking about the screen before the boot animation.
mattfox27 said:
Ya bootanimations ae no problem, im talking about the screen before the boot animation.
Click to expand...
Click to collapse
Ok mine blows past the red dot pretty quick so doesn't really bother me. But I am sure there is a way around it. Good luck with it. If you do find way around it, please post it. Hp
dual core snap dragon beast
I'm pretty sure we need s-off to change the M screen
Sent from my DROID X2 using Tapatalk
colonel187 said:
I'm pretty sure we need s-off to change the M screen
Sent from my DROID X2 using Tapatalk
Click to expand...
Click to collapse
Motorola phones don't have s on and off
Sent from my DROID X2 using XDA App
Guys please read my post. I have done this on the X2 and can confirm that it works.
Sent from my DROID X2 using XDA App
dragonzkiller said:
Guys please read my post. I have done this on the X2 and can confirm that it works.
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
So the atrix method works on X2, have you done it recently?
Hey it worked...right on but one thing was it says to delete the last two bits in file but when i do that it throws the size off instead of being 1036820 it becomes 1036818 so i left the two bits in and it stayed at the proper size, fastboot flashed and it worked. Whats the deal with deleting the last two bits?
So it worked great thanks dragonzkiller, im going to attach the file i made in-case anyone wants to change it using the directions from the link below.
The attached image is just to show you what it looks like you need the bin file to flash it which is located in logo.zip below, also i found the fastboot method provided in directions was super easy and worked no problem where the CWR zip method did not work i think because the zip template they give you is corrupt or something it acts weird if you try to edit or unzip it. Just use fastboot method super easy.
http://forum.xda-developers.com/showthread.php?t=1187337
EvilTim said:
Motorola phones don't have s on and off
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
Dang. I just got took to school. I did not know that.
Sent from my DROID X2 using Tapatalk
mattfox27 said:
So it worked great thanks dragonzkiller, im going to attach the file i made in-case anyone wants to change it using the directions from the link below.
The attached image is just to show you what it looks like you need the bin file to flash it which is located in logo.zip below, also i found the fastboot method provided in directions was super easy and worked no problem where the CWR zip method did not work i think because the zip template they give you is corrupt or something it acts weird if you try to edit or unzip it. Just use fastboot method super easy.
http://forum.xda-developers.com/show....php?t=1187337
Click to expand...
Click to collapse
Page not found. I just tried doing this in another thread, wouldn't find files thru CMD. Anywho I'll try again later, after I make a custom one.
Elite49 said:
Page not found. I just tried doing this in another thread, wouldn't find files thru CMD. Anywho I'll try again later, after I make a custom one.
Click to expand...
Click to collapse
I fixed the link...you have to download the fastboot.zip from link and unzip it like in c:/fastboot then go to command prompt go to that directoy and run the commands. You also have to copy the logo.bin into the fastboot directory.
In the link posted over at the atrix page there are a bunch of other ones people made that you can download and install.
Its easy to make your own you just have to use a hex editor to tweak the finished image which seems very scary at first but its really easy you just have to be very carefull.
I use Hxd Hex Editor... http://mh-nexus.de/en/hxd/
I will also say that in the directions it says once your done editing hex the size will be 1036820 bits it says to remove 2 bits from end of image but when i did that the size changed to 1036818 bits, 2 bits lower then what it says so i did not remove the last 2 like it says and it came to the correct size of 1036820 bits so im just saying it says to take delete 70 bits from beginning then 2 from end and i did not remove the 2 from the end because it threw off the size, do whatever you want but that's what i did if it helps.
I've always appreciated having the option of rebooting into recovery on the "phone options" when powering off. Typically if I have already used the dx2 bootstrap into recovery previously I can just power down when im plugged in and ill reboot into cwm...and my old dx and other phones I've seen have it typically. Pretty sure its doable.
So if anyones up for adding it to your list of things to do id be extatic.
Thx in advance.
Sent from my DROID X2 using XDA App
We don't have an official bsr. In order for the reboot recovery to work, i think the script calls for Koush's signature, or something like that, and our recovery doesn't have the proper sig. Not only is it a hacked up recovery, it's an ancient one. I don't see recovery ever being added, unfortunately.
Oh, btw, wrong forum.
Sent from my DROID X2 using xda premium
Xodus is correct.
We were all excited for a while when koush got an x2 bout a month or two ago thinking we would finally get a "real" x2 recovery option. Its a little frustrating to see almost EVERY moto phone except for us have that option. And the only "real"x2 difference between our phone and others is our tegra2. I can't see that being the reason we can't get this option. It Has GOT to be doable if someone would just put the work/time into creating it.
Well, don't they have one for the Xoom? We need to see if we can port some of the Xoom hacks. The only difference REALLY are honeycomb and the screen size(right?).
AtLemacks said:
Well, don't they have one for the Xoom? We need to see if we can port some of the Xoom hacks. The only difference REALLY are honeycomb and the screen size(right?).
Click to expand...
Click to collapse
XOOM is unlocked and the x2 is locked
Liberated X2
Sandso9 said:
XOOM is unlocked and the x2 is locked
Liberated X2
Click to expand...
Click to collapse
For inquiring minds they're don't know, an unlocked bl allows you to flash cwm to become THE recovery; no bsr or hacked jobs needed.
Sent from my DROID X2 using xda premium
Cuz XOOM SHIPS with unlocked bootloader of.course
This is what the x2 needs desperately if we ever want to see some.permanent fixes for.performance issues we have had.
I swear someone needs to unlock this caged beast. @Motorola I'm looking at you. STOP LETTING VZW BULLY YOU INTO PERMANENT LOCKED BOOTLOADERS. THEY ARE BREAKING THE LAW!! AT LEAST LEAK US SOME.OPTIONS OR.PUT A METHOD OUT THERE FOR US TO USE...doesn't even need to be official on their website....just send it to a newb in the x2 forum and let em spread the news lol....AAAAGGGHHHH
.
/end rant sorry
Ya well even though we aren't unlocked...it would seem that some sort of autorun sequence for the two commands in the dx2 bootstrap could be programmed to run one after the other in the background at the push of a button on that menu. But it couldn't really be that simple -_-
Sent from my DROID X2 using XDA App
xerotix said:
Ya well even though we aren't unlocked...it would seem that some sort of autorun sequence for the two commands in the dx2 bootstrap could be programmed to run one after the other in the background at the push of a button on that menu. But it couldn't really be that simple -_-
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
If only I wasn't such a noob I would try to make that happen
hopefully someone will figure out what needs to happen for us to even feel like we are "officially "I supported
xerotix said:
Ya well even though we aren't unlocked...it would seem that some sort of autorun sequence for the two commands in the dx2 bootstrap could be programmed to run one after the other in the background at the push of a button on that menu. But it couldn't really be that simple -_-
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
Logic seems airtight. I mean, if you can push the button in System Recovery and it'll boot to charge mode or recovery mode then why can't the same commands used to perform that action be used as a reboot recovery option. I'm no dev. I would imagine if it was that easy, it would've been done by now.
"Reboot widget" from the market is a good alternative for now....
Sent from my DROID X2 using XDA App
X0dus said:
Logic seems airtight. I mean, if you can push the button in System Recovery and it'll boot to charge mode or recovery mode then why can't the same commands used to perform that action be used as a reboot recovery option. I'm no dev. I would imagine if it was that easy, it would've been done by now.
Click to expand...
Click to collapse
Seems to me the charge mode is the weakest link in the chain. The normal boot sequence is dependent on encryption and system checks, the battery animation doesn't require so much security. It would make sense to me, after reading the cvpcs blog about 2nd init, they could use 2nd init to hijack normal boot, but that sounds like a total pain in the ass.
Sent from my DROID X2 using XDA App
ya XOdus...with nitro and masta being basically the only two devs for the dx2 I figured I'd just throw this out there and hopefully someone reads it. If i were savoy with making roms I'd be all over it, but hopefully just my train of thought may help someone with their endeavors in making their rom worth while. Nitro put our bootstrapper in his "eclipse parts" so I would imagine he might be interested in advancing farther.
We have it on the bionic. We're locked plus have to use a bootstrap. Ask around in that forum....
It's on Th3ory's ROM.
Sent from my DROID BIONIC using xda premium
xerotix said:
ya XOdus...with nitro and masta being basically the only two devs for the dx2 I figured I'd just throw this out there and hopefully someone reads it. If i were savoy with making roms I'd be all over it, but hopefully just my train of thought may help someone with their endeavors in making their rom worth while. Nitro put our bootstrapper in his "eclipse parts" so I would imagine he might be interested in advancing farther.
Click to expand...
Click to collapse
Not true kejar is also working on the x2 he's just busy cause he has the x, d2, x2, d3, and bionic to deal with. We should see liberty 3 by mid week or at the end of the week
Liberated X2
Sandso9 said:
Not true kejar is also working on the x2 he's just busy cause he has the x, d2, x2, d3, and bionic to deal with. We should see liberty 3 by mid week or at the end of the week
Liberated X2
Click to expand...
Click to collapse
Let's hope!
Sent from my DROID X2 using xda premium
X0dus said:
Oh, btw, wrong forum.
Click to expand...
Click to collapse
Please report threads/posts that are in the wrong section. Thanks.
arrrghhh said:
Please report threads/posts that are in the wrong section. Thanks.
Click to expand...
Click to collapse
That should be a feature added to the app. Kept forgetting whenever i was using the Web based.
Sent from my DROID X2 using xda premium
X0dus said:
That should be a feature added to the app. Kept forgetting whenever i was using the Web based.
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
I only used the xda app after my laptop broke, but even now with it working I still use my phone haha
Would be cool to get the option to reboot to recovery in the power menu.
Sent from my DROID X2 using XDA App
I can do it but you still have to be plugged into the wall. I found it kind of pointless since you need the app to toggle it back to charge mode if needed.
Sent from my DROID BIONIC using xda premium
Hi guys, just wondering if anyone can help me with my dx2. The 'home' button is now my 'back' button and vice versa with the 'back' button. Im currently on eclipse 1.3 but have had this issue prior to eclipse. I've sbf'd twice(I think) but didn't change anything. Im kinda getting used to it now but was just gonna see if anyone have any trouble shooting ideas they can share. Thanks in advance
Merv
Sent from my DROID X2 using Tapatalk
I read a while back someone else had the same issue. I don't believe he ever got a answer on a fix.
Thanks for the reply.
Sent from my DROID X2 using Tapatalk
I really don't think it's a ROM issue. I think it's a hardware issue. These ROMs in no way edit or modify any of the button's actions.
No I totally agree I don't think its a (custom) ROM issue at all I hope it didn't sound like that, if it does I don't mind editing my original post. Please let me know. I just wanted to see if anyone else experienced this issue and have ideas to help resolve it
Sent from my DROID X2 using Tapatalk
wnrdx2 said:
No I totally agree I don't think its a (custom) ROM issue at all I hope it didn't sound like that, if it does I don't mind editing my original post. Please let me know. I just wanted to see if anyone else experienced this issue and have ideas to help resolve it
Click to expand...
Click to collapse
If it is a hardware issue, I don't think there will be a way for you specifically to resolve it. It'll have to be replaced/fixed by Motorola/Verizon.
Gotcha. Thanks anyways
Sent from my DROID X2 using Tapatalk
actually the fix is super easy,just use a file explorer,I use root explorer and go into /system/usr/keylayout/tegra-kbc.kl open it with text editor and just switch the two numbers next to home and back,super easy fix
Sent from my DROID X2
Oh wow ok I will give that a try and report back tomorrow. Thank you so much
Sent from my DROID X2 using Tapatalk
I think I should note that if that fix works, the hardware problem will still actually exist and this will only mask it.
Kurihonoo thank you thank you thank you(!) for the suggestion it helped and fixed my issue, Donlad do you mind elaborating on why you think its just a temporary fix?
Sent from my DROID X2 using Tapatalk
wnrdx2 said:
Kurihonoo thank you thank you thank you(!) for the suggestion it helped and fixed my issue, Donlad do you mind elaborating on why you think its just a temporary fix?
Sent from my DROID X2 using Tapatalk
Click to expand...
Click to collapse
It may be a permanent fix, but it is technically just masking things *IF* it is a hardware issue.
Example: your phone's physical keys *MAY* be switched around on the main board of the phone, and the fix just switched the keys back around.
What I'm saying is that there shouldn't have needed to be a fix in the first place *IF* it was a hardware issue and somehow that file didn't get changed before.
Donlad thank you for elaborating on that, I understand your point. I've had this issue for a good couple of weeks and just now addressed it. Im hoping that I can remember what I was doing prior to having this issue so that I can actually pinpoint the reason this happened in the first place. Right now off the top of my head I can't remember. It may have been an app that I installed(?) And that's a big MAYBE. Anyway thanks for your help. I'll do my best to address issues I need help with sooner next time so that I wont have a hard time remembering changes I've done with my phone.
On a different note I'd like to say kudos and big ups to all the devs working hard and supporting the DROID X2. Please let me know if there's anything I can do to help
Sent from my DROID X2 using Tapatalk
You're welcome
It happened to me after sbfing, I installed eclipse 1.3 and my phone refused to start up so I had to use the 2.3.4 sbf and after using it my keys were switched. after trying many things ,my fix seemed to be the only solution
Sent from my DROID X2
Well thank you so much for your suggestion. You're a lifesaver!
Sent from my DROID X2 using XDA App
KurioHonoo said:
It happened to me after sbfing, I installed eclipse 1.3 and my phone refused to start up so I had to use the 2.3.4 sbf and after using it my keys were switched. after trying many things ,my fix seemed to be the only solution
Sent from my DROID X2
Click to expand...
Click to collapse
I had the same issue while sbf'ing. It is definitely a hardware issue with no fix. I think believe it happened during multiple boot loops before I got into the stock android recovery and wiped everything. Would be nice if you could confirm this but its not a big deal.
Download root explorer or rom toolbox and go into your system/usr/keylayout folder. Edit any files with keys 102 and 158. For instance on normal working phones 158 would b home and 102 would be back or vice versa... I dont remember the exact order. Because your phone is messed up you have to switch the settings so that 102 would be home and 158 now means back or, again, vice versa. Also remember to set "WAKE_DROPPED" for whatever you set the back button to and "WAKE" for the home button.
You should do this with all the files that contain those 2 button numbers so check all the files in that folder. If my memory serves me correct it requires editing of all except the first 2 files. Remember to save them first and they should be in working order after reboot until the next time you wipe your phone, install a new rom or sbf. If you do, you have to edit them again.
KurioHonoo said:
actually the fix is super easy,just use a file explorer,I use root explorer and go into /system/usr/keylayout/tegra-kbc.kl open it with text editor and just switch the two numbers next to home and back,super easy fix
Sent from my DROID X2
Click to expand...
Click to collapse
I just hijacked my (SEARCH) function for the (CAMERA) shutter using your tip. Thanks.
skwoodwiva said:
I just hijacked my (SEARCH) function for the (CAMERA) shutter using your tip. Thanks.
Click to expand...
Click to collapse
I'd totally do that if I ever used my camera
Sent from my DROID X2
skwoodwiva said:
I just hijacked my (SEARCH) function for the (CAMERA) shutter using your tip.
Click to expand...
Click to collapse
How'd you do that???
Sent from my DROID X2 using XDA App
I am not responsible for the things you do to your phone.
I no longer have this phone. With that being said, I will still keep these links up. If for some reason they don't work, I WILL NOT be updating them. If you need them or wish to redistribute them, go for it and grab them while they are still here.
It was a nice phone while it lasted, but after 6 replacements I moved on to something better.
This DOES NOT unlock your bootloader, but will update to 2.3.5 on the already unlocked phones. Sorry to the folks that are locked with the 2.3.5 update. Hopefully something soon happens for you.
This is stock 2.3.5 WITH the updated kernel. Updated baseband as well, in a separate .zip of course.
Download link- http://http://dl.dropbox.com/u/1407...UN_USC_19.0-19-release-keys-signed-USC-US.zip
MD5- f63b20e76ff03107475f5ba033e00084
De-odexed
Download link- http://dl.dropbox.com/u/14078277/electrify_2.3.5_deodexed-zipaligned.zip
MD5- f1f6cbdd1340ed2e96b6848ef710a87a
Here is the updated radio. Electrify only!
This will update your radio from n_01.10.00s.xj to n_01.11.00s.xj
Flash in CWM
Please don't be a dumbass and flash on the Photon.
Download link- http://dl.dropbox.com/u/14078277/electrify_2.3.5_bp.img.zip
MD5- 669f600effecc7e2acfac82e068eabe9
Known issues-
MMS on Sprint- Use GoSMS with Sprint MMS settings
Wifi-Fixed!
You could use my modified install-recovery.sh it enables init.d on stock roms. Btw great job
yepitsme19 said:
I am not responsible for the things you do to your phone.
This DOES NOT unlock your bootloader, but will update to 2.3.5 on the already unlocked phones. Sorry to the folks that are locked with the 2.3.5 update. Hopefully something soon happens for you.
Thanks to samcripp here at XDA and his Fruit Cake Maker, I have a CWM flashable .zip for you. This is stock 2.3.5 WITH the updated kernel. I still haven't figured out how to update the baseband though
Download link-http://www.multiupload.com/QXI98X7NNX
MD5- 420fbfb46bf4547d23dcd9ae29171afa
Flashing this will revert your recovery to the stock recovery BUT will keep you unlocked
Re-install your custom recovery according to this guide-http://www.teamuscellular.com/Forum/viewtopic.php?f=105&t=1221
Also, I have noticed that after every boot it re-installs the stock recovery. To fix this, use a root file explorer(I use Root Explorer) and go into /system/etc and delete the file "install-recovery.sh"
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Gonna see if it works on the photon......if so maybe a new base joker?
Sent from my MB855 using xda premium
Everything except mms works fresh flash.....even 1080p video. The mms should be easily fixable.
If your real picky the us cellular on the notification and such but thats easily fixeable as well.
Needs to be deodexed
Programming menu is #073887* then hit dial enter msl
Sent from my GT-P7510 using xda premium
Is this safe to flash on a photon?
ChadH42 said:
Is this safe to flash on a photon?
Click to expand...
Click to collapse
I believe that is what cryptix is getting at... But don't take my word for it as I don't have a Photon.
Sent from my Motorola Electrify using XDA App
It s full working on my PHOTON 4G.
Great working! Fastest stock, GSM is working!
but PC see photon as electrify mb853
yepitsme19 said:
Also, I have noticed that after every boot it re-installs the stock recovery. To fix this, use a root file explorer(I use Root Explorer) and go into /system/etc and delete the file "install-recovery.sh"
Click to expand...
Click to collapse
I have been using this since you posted it on TUSCC forums and I prefer it over my fudged method, However I have not had this issue with it at all..
My Recovery stays the same after I have re-flashed it, after flashing this ROM.. Weird..
Yeah you could change the topic to electrify/photon.
Sent from my Motorola Electrify using xda premium
Cythrawl said:
I have been using this since you posted it on TUSCC forums and I prefer it over my fudged method, However I have not had this issue with it at all..
My Recovery stays the same after I have re-flashed it, after flashing this ROM.. Weird..
Click to expand...
Click to collapse
Hmm...Idk then. It always seems to replace for me lol.
criptix said:
Yeah you could change the topic to electrify/photon
Click to expand...
Click to collapse
So everything on the Photon works except for MMS?
Yup still running now no problems.
Sent from my Motorola Electrify using xda premium
criptix said:
Yup still running now no problems.
Sent from my Motorola Electrify using xda premium
Click to expand...
Click to collapse
Maybe it's just APN settings for the MMS?
Sent from my Motorola Electrify using XDA App
Yeah i havent messed with it yet to see plus some apps are showing device incompatible which is a few changes as well
Sent from my Motorola Electrify using xda premium
Does this fix the screen becoming unresponsive after touching a specific area for more than 30 seconds?
Sent from my Photon 4G using Tapatalk
Dsparil said:
Does this fix the screen becoming unresponsive after touching a specific area for more than 30 seconds?
Sent from my Photon 4G using Tapatalk
Click to expand...
Click to collapse
No clue. I haven't had any problems with it but I'm on an Electrify not a Photon. Flash and find out
Dsparil said:
Does this fix the screen becoming unresponsive after touching a specific area for more than 30 seconds?
Sent from my Photon 4G using Tapatalk
Click to expand...
Click to collapse
Thats actually a feature more or less so if water gets on the screen it doesnt bug out, can be annoying on games tho
Sent from my Motorola Electrify using xda premium
criptix said:
Thats actually a feature more or less so if water gets on the screen it doesnt bug out, can be annoying on games tho
Sent from my Motorola Electrify using xda premium
Click to expand...
Click to collapse
I'm not saying this to troll, but this is a deal breaker for me, and I never thought for a minute that Sprint's only Tegra powered phone would be crippled over a trivial limitation.
Here is to hopes for motorola to make this feature optional in a future update.
Sent from my Photon 4G using Tapatalk
Our screen is way too sensitive without that feature. I disabled it once. That was a dark day
Dsparil said:
I'm not saying this to troll, but this is a deal breaker for me, and I never thought for a minute that Sprint's only Tegra powered phone would be crippled over a trivial limitation.
Here is to hopes for motorola to make this feature optional in a future update.
Sent from my Photon 4G using Tapatalk
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
jokersax11 said:
Our screen is way too sensitive without that feature. I disabled it once. That was a dark day
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
I think if motorola would make it optional as well as add at least more than 2 points of multitouch this would help gaming. There are several games that can use more than 2 touch points.
Joker, with it disabled is there no way to adjust it?
Probably, but youre screen has to be perfectly clean all the time.
scoobdude said:
I think if motorola would make it optional as well as add at least more than 2 points of multitouch this would help gaming. There are several games that can use more than 2 touch points.
Joker, with it disabled is there no way to adjust it?
Click to expand...
Click to collapse
Sent from my MB855 using XDA App