Database Users

Benefits of 2.3.32

What are they?

I second this.
Sent from my DROIDX using XDA App

Morkai Almandragon said:
What are they?
Click to expand...
Click to collapse
You can run Fission 2.3 without any real trouble with this, as opposed to some issues if you use it on 2.3.15
At least that's the reason I went to the leak .

SirBrass said:
You can run Fission 2.3 without any real trouble with this, as opposed to some issues if you use it on 2.3.15
At least that's the reason I went to the leak .
Click to expand...
Click to collapse
Same here.

Where cn i find 2.3 all i see is 2.2.2

catalystsupreme2 said:
Where cn i find 2.3 all i see is 2.2.2
Click to expand...
Click to collapse
If you donate to the Defuse Team, you will get a link to the Fission ROM Manager 1.1 apk. You can download the 2.3 update from there and flash it like you would 2.2.2. It gives you access to many early surprises from them and it supports a team that has brought us a lot.

I mean what fixes. To be honest I like blur if for no other reason than hands free voice dial over bt.

I haven't had a single Battery Info crash, where 2.2.15 would crash all the time.

Sunblood said:
I haven't had a single Battery Info crash, where 2.2.15 would crash all the time.
Click to expand...
Click to collapse
what about search lag? the voice search bug etc?

My phone no longer gets stuck at the M logo during boot up.

I wish there was some sort of performance comparison... Still deciding whether to bother updating right now or not.

just unbricked my droid x with the new sbf. unbricked the brick that im supposed to send back to verizon, but i wanted to test this sbf before i used it on my replacement. then im going to rebrick by using the 2.3.15 sbf and send it back to them.
2.3 seems the same but just a tad (and i emphasize tad) bit snappy-er. music player seems to look different. other than that, i just like to have the latest-and-greatest.
remember to pull the battery after you update when the droid x animation begins to boot loop. then hold the home button when booting up again, then data/factory reset from the recovery and select reboot system now.

GoldenCyn said:
just unbricked my droid x with the new sbf. unbricked the brick that im supposed to send back to verizon, but i wanted to test this sbf before i used it on my replacement. then im going to rebrick by using the 2.3.15 sbf and send it back to them.
2.3 seems the same but just a tad (and i emphasize tad) bit snappy-er. music player seems to look different. other than that, i just like to have the latest-and-greatest.
remember to pull the battery after you update when the droid x animation begins to boot loop. then hold the home button when booting up again, then data/factory reset from the recovery and select reboot system now.
Click to expand...
Click to collapse
You should do the wipe cache/wipe data BEFORE you reboot, after applying the 2.3.32 update zip.
Multiple people bricked by not following this step correctly, after they found that they couldn't get into their stock recovery mode anymore.

bladebarrier said:
You should do the wipe cache/wipe data BEFORE you reboot, after applying the 2.3.32 update zip.
Multiple people bricked by not following this step correctly, after they found that they couldn't get into their stock recovery mode anymore.
Click to expand...
Click to collapse
Isnt this what the the previous post said? Just making sure I understand correctly
Sent from my DROIDX using XDA App

amasse said:
I wish there was some sort of performance comparison... Still deciding whether to bother updating right now or not.
Click to expand...
Click to collapse
Yeah I'm wth you... I hear the new nexus s has gingerbread so its only a matter of time before there is a leak for it.
Sent from my DROIDX using XDA App

btucker2003 said:
Yeah I'm wth you... I hear the new nexus s has gingerbread so its only a matter of time before there is a leak for it.
Click to expand...
Click to collapse
Yes a matter of time ........ a LONG time

Rooting and debloating Froyo

So froyo is leaked and installed and all is fun (seems to run a bit slower than 2.1 to me, especially during start up) but I have the problem of A TON of bloatware.
Anybody played around yet? I've frozen a few of them but unsure of what all is good and bad.
How about root? The newest version Z4Root does not work, it stalls and you have to force close it.

got a link to the 2.2 download?

filesonic.com/file/1597204534/Blur_Version.2.159.17.MB508.ATT.en.US.zip
this is the beta version that was leaked out. Go thru all the steps to get the free download, the waiting and blah blah blah.

boazjuggalo said:
How about root? The newest version Z4Root does not work, it stalls and you have to force close it.
Click to expand...
Click to collapse
Have you by chance tried an older version?

pre4speed said:
filesonic.com/file/1597204534/Blur_Version.2.159.17.MB508.ATT.en.US.zip
this is the beta version that was leaked out. Go thru all the steps to get the free download, the waiting and blah blah blah.
Click to expand...
Click to collapse
They have released the non-beta on the motorola site. the only issue is. that it won't install on a rooted phone so you have to undo your root first

thebluetoothkid said:
got a link to the 2.2 download?
Click to expand...
Click to collapse
Hi!
Well, I made some post with the info that good people make available and that I collect to try to make it easy,in this link:
http://forum.xda-developers.com/showthread.php?t=1211799
I already made the update since 2 days ago and very happy, in my case I found very usefull that at leats by now some usefull 2.2 tricks are very welcome like move some apps to sdcard and few other, but as new detail in my case the 2.2 update is detecting one of my 2 batteries as non original moto, and refuse to charge it, but in 2.1 it works perfect and could be charged...
So, for me is stable and hope that could be better the final release (if it may really happen, since Moto put down the page about the release.... :-/ so could be lucky that at least we have this beta, for possible future roms)
Best regards!

Froyo runs faster and it has a great file explorer built in. The only thing that sucks is that there is even more bloatware from AT&T
I have the phone unlocked and in Canada so my unlock stayed and unknown sources is still available after the upgrade
hope there are some edits soon they get rid of all the bloatware, there are legitimately 12 bloatware apps from AT&T on the phone now.
The interface is a little bit sleeker and the boot up of the phone is now silent, which i love since the old boot up was a bit to loud.

xaser, your guide is what I followed to do mine and I really apprecite your time to put it up. Worked great.
Somebody said the full update is up on moto, anybody got a link? I couldn't find anything.
No I have not tried an older version.
Anybody had any luck with a root on the beta? Or the full version either one?
Are we sure this "beta" isn't the full version? The Android Version in About Phone just says 2.2.2 instead of 2.2.2b like i'd expect with a beta.

boazjuggalo said:
xaser, your guide is what I followed to do mine and I really apprecite your time to put it up. Worked great.
Somebody said the full update is up on moto, anybody got a link? I couldn't find anything.
No I have not tried an older version.
Anybody had any luck with a root on the beta? Or the full version either one?
Are we sure this "beta" isn't the full version? The Android Version in About Phone just says 2.2.2 instead of 2.2.2b like i'd expect with a beta.
Click to expand...
Click to collapse
Here is the official upgrade
https://motorola-global-portal.custhelp.com/app/utils/guided_assistant/g_id/1004

thebluetoothkid said:
Here is the official upgrade
https://motorola-global-portal.custhelp.com/app/utils/guided_assistant/g_id/1004
Click to expand...
Click to collapse
Hm, won't show an update for me running 2.2 beta... guess i'm goign to have to flash back to 2.1

boazjuggalo said:
Hm, won't show an update for me running 2.2 beta... guess i'm goign to have to flash back to 2.1
Click to expand...
Click to collapse
Could you tell me how to flash back to 2.1?
Thanks

sharethl said:
Could you tell me how to flash back to 2.1?
Thanks
Click to expand...
Click to collapse
Use caution... I flashed back to 2.1 once by simply following the guide in the development forum again. But tried to do it again this morning and my phone bricked. So I had 50% success which is too little for me to suggest it.

boazjuggalo said:
Use caution... I flashed back to 2.1 once by simply following the guide in the development forum again. But tried to do it again this morning and my phone bricked. So I had 50% success which is too little for me to suggest it.
Click to expand...
Click to collapse
I see, Thanks for your advise.
Why Motorola make the phone so un-opensource!!!

I know the only issue I had with reverting my Flipside was the RSD software, 4.9 wouldn't detect my phone but 4.5 worked perfectly fine
It's been a day so far and froyo is working perfect on mine

thebluetoothkid said:
I know the only issue I had with reverting my Flipside was the RSD software, 4.9 wouldn't detect my phone but 4.5 worked perfectly fine
It's been a day so far and froyo is working perfect on mine
Click to expand...
Click to collapse
So have you tried to reflash? and as for rooting, have you been able to do so?

pre4speed said:
So have you tried to reflash? and as for rooting, have you been able to do so?
Click to expand...
Click to collapse
I didn't need to reflash, I used RSD to downgrade. Since I had my phone rooted. then I just ran the official upgrade and it's been running like butter for me, real smooth.
I've searched all over for info on rooting froyo on the Flipside and it looks like it's going to take awhile because they locked the phone down tight and the few guys that have rooted the phone have started experiencing problems with the phone because of the root.

FYI:
SUPERONECLICK TO THE RESCUE!!!!!!!!!
Sent from my MB508 using Tapatalk

rignfool said:
FYI:
SUPERONECLICK TO THE RESCUE!!!!!!!!!
Sent from my MB508 using Tapatalk
Click to expand...
Click to collapse
SUPERONECLICK can root froyo, I just tried, and working.

sharethl said:
SUPERONECLICK can root froyo, I just tried, and working.
Click to expand...
Click to collapse
Which version of soc did you use? I have had problems rooting with it ever since I updated to the most current version, but I dont remember which version I used that worked fine. I ended up sideloading z4root to gain root, but from what im seeing, that wont work. thanks! Im almost ready to upgrade.

pre4speed said:
Which version of soc did you use?
Click to expand...
Click to collapse
I just successfully used the latest version, 2.1.1

Milestone X - C-Spire: Custom ROMS? Droid X Bootstrapper Working

Anyone with luck flashing a Milestone X w/ a custom ROM?
Running Rooted 2.3.5 w/bloatware removed (but backed up) along w/ DROID X Bootstrapper.
Have made my first full system backup using this tool.
If complete ROMS could not be used, what components would I need to modify, replace, ... exchange to get it to work on C-Spire (say, Verizon).
I've heard that there are some ROMS that don't mess with the baseband and other communications settings, files, frequencies, protocol, etc... What are these type called if they exist? Where can I find them? Are these a safer alternative to full ROMS?
Will DX Bootstrapper get the job done? Reports ClockworkMod REcovery v2.5.0.6.

I would recommend staying off custom roms for the Milestone X until a working sbf for us makes an appearance. Myself and ngholson both had issues where we got stuck in a bootloop and the sbf just output more errors until a replacement device was needed.

Rocheforte said:
I would recommend staying off custom roms for the Milestone X until a working sbf for us makes an appearance. Myself and ngholson both had issues where we got stuck in a bootloop and the sbf just output more errors until a replacement device was needed.
Click to expand...
Click to collapse
agreed. [10chars...............

another thing to consider, since we cannot sbf at this time, is that the bootstrapper will break your ability to install any future ota updates. it modifies the logwrapper and makes a copy called logwrapper.bin, however, uninstalling the bootstrapper and restoring the logwrapper file does not correct the problem. best i can tell the only answer that i can find when this happens is to sbf back to stock... well you see where this is going.... currently we cannot do this, so unless you never want the ota upgrades i do not recommend installing the bootstrapper on cspire's milestone x.
oh well nevermind went back and re-read your post, you already have the bootstrapper installed. (at least you did it after ota)

here is a link to the post that has the sbf that is reported to work with cell south (cspire) http://forum.xda-developers.com/showthread.php?t=1117885
maybe someone else can try it again and report back.
daywalker04 said:
SBF flash for MB809 - Milestone X Generic North America
SHADO_X6_3.1.39_SHADOW_BP_C_02.06.00R_AP_BP_Flex_1E_signed_secure_dist_1ff_P3_USERBLD.sbf.gz
http://www.filesonic.com/file/11766...x_1E_signed_secure_dist_1ff_P3_USERBLD.sbf.gz
Compression MD5 - BF942D55992C774446F24B56116649A1
SBF MD5 - 2EAEBD1540D563114523BEB09539A8AF
Click to expand...
Click to collapse
abcleanonme said:
Well I can confirm it works on Cellular South.
Sent from my MilestoneX using XDA Premium App
Click to expand...
Click to collapse

I can confirm that the old sbf it does not work after ota update. I had to get a new phone. I have rooted, but I am not installing a bootstrapper until a working sbf is available. Hopefully that will happen soon.

I am on C spire out of Byram, MS and can in fact confirm that "Droid X Bootstrapper" from the market indeed works like a charm on the Milestone X with stock versions 2.2.2 and 2.3.5.
I use "Super One Click" to root, then the same prog to "Allow non market apps" then buy "Droid X Bootstrapper" from market, run it. Reboot while holding camera button and power button,,,,voila
Confirmed roms that I have and currently run or ran: CM 7 nightlies, Liberty 1.5, and Fission 2.5.7 DroidX
---------- Post added at 07:12 AM ---------- Previous post was at 06:57 AM ----------
A little trick I figured out to sbf back to stock,,,,download the latest ota from Cspire "Blur_Version.3.2.6.MB809.ACG-CellSouth.en.US" blah blah,,,,,rename it to "update.zip",,,,not "update.zip.zip"put it on the root of your sd card and boot into stock recovery or clockwork mod and run update.......BLAM! Simple as that...

Brickster said:
A little trick I figured out to sbf back to stock,,,,download the latest ota from Cspire "Blur_Version.3.2.6.MB809.ACG-CellSouth.en.US" blah blah,,,,,rename it to "update.zip",,,,not "update.zip.zip"put it on the root of your sd card and boot into stock recovery or clockwork mod and run update.......BLAM! Simple as that...
Click to expand...
Click to collapse
i tried that too it didn't work for me.

I dunno,,,, it worked for me twice. I tried to update cwm from the app using the flash for droid x and it messed up my recovery. So i updated to the latest ota from Cspire via the stock android recovery by naming the ota file to update.zip and running it like that.
I'm running CM7 nightlies for the droid x on the Milestone x....you might have to remove the line of code in the update file that asked for Kernel assert,,,,I can't remember, but seems like it kept giving me an error that says, "assert failed: run_program("/tmp/check_kernel") but after that all was fine.
Sent from my Milestone X using XDA App

Brickster said:
I dunno,,,, it worked for me twice. I tried to update cwm from the app using the flash for droid x and it messed up my recovery. So i updated to the latest ota from Cspire via the stock android recovery by naming the ota file to update.zip and running it like that.
I'm running CM7 nightlies for the droid x on the Milestone x....you might have to remove the line of code in the update file that asked for Kernel assert,,,,I can't remember, but seems like it kept giving me an error that says, "assert failed: run_program("/tmp/check_kernel") but after that all was fine.
Sent from my Milestone X using XDA App
Click to expand...
Click to collapse
is there a reason that your not using the new liberty rom and used 1.5?

tylorjefcoat said:
is there a reason that your not using the new liberty rom and used 1.5?
Click to expand...
Click to collapse
Nah, it's a cool rom .....I'm just a flash whore. I like cm7 nightlies the best though.

Brickster said:
Nah, it's a cool rom .....I'm just a flash whore. I like cm7 nightlies the best though.
Click to expand...
Click to collapse
what has been the best in your opinion? i just upgraded from the hero and was running aosp and loved it.
i actually like some of the blur apps, hard to believe that i like a custom ui on android lol.
i have been reading on the droid x vs milestone x and i am weary of flashing update that also includes the radio/baseband.
what version of cm7 nightfiles are you on? any complaints?

Brickster said:
I dunno,,,, it worked for me twice. I tried to update cwm from the app using the flash for droid x and it messed up my recovery. So i updated to the latest ota from Cspire via the stock android recovery by naming the ota file to update.zip and running it like that.
I'm running CM7 nightlies for the droid x on the Milestone x....you might have to remove the line of code in the update file that asked for Kernel assert,,,,I can't remember, but seems like it kept giving me an error that says, "assert failed: run_program("/tmp/check_kernel") but after that all was fine.
Sent from my Milestone X using XDA App
Click to expand...
Click to collapse
I am getting the exact same error. Where do I need to go to eliminate this line of code. I have setup everything else up until this point and it works perfectly with recovery and everything. A bit of help please.

thenig said:
I am getting the exact same error. Where do I need to go to eliminate this line of code. I have setup everything else up until this point and it works perfectly with recovery and everything. A bit of help please.
Click to expand...
Click to collapse
Open the ROM zip and go: META-INF/com/google/android/ and in the updater-script, remove the code that asked for Kernel assert.

tylorjefcoat said:
what has been the best in your opinion? i just upgraded from the hero and was running aosp and loved it.
i actually like some of the blur apps, hard to believe that i like a custom ui on android lol.
i have been reading on the droid x vs milestone x and i am weary of flashing update that also includes the radio/baseband.
what version of cm7 nightfiles are you on? any complaints?
Click to expand...
Click to collapse
I too just upgraded from the Hero....and I still love that phone! My hero has had every rom known on it,,,and some that weren't even made for it....It's unbrickable! LOL
Yea, the Milestone is a little more finicky than the Hero, and with Motorola's locked bootloaders, one could get in a fix..
I've ran the past 3 nightlies and currently on cm_shadow_full-154.zip.
I tell ya, they all have some kind of bug somewhere. It all depends on what you want to put up with. Me, personally, I like the stock ota 2.3.5 from Cspire. It works. Plain and simple. Now, I would like some of the CM7 options and spare parts.

Brickster said:
Open the ROM zip and go: META-INF/com/google/android/ and in the updater-script, remove the code that asked for Kernel assert.
Click to expand...
Click to collapse
Open the updater-script with notepad (new to this) and found no mention of kernel assert. Almost there...a bit more help would get me in.

It should be the top 3 lines, if I remember correctly.... I checked it out on my phone to make sure but,,,, duh, I already removed it (face palm).
It's in there somewhere.
Run install again and right down all the errors... Then try to find them in the script file.
I'm new to this also (as far as motorola stuff) too. And I take risks that most people wouldn't..... Hell, if I mess something up bad enough , just sbf back.
I'll try to help you more when I get off work... Maybe send you my roms that have already been fixed.
Make sure to turn off script and signature asserts off in cwm... Sometimes that helps.
Sent from my Milestone X using XDA App

Brickster said:
It should be the top 3 lines, if I remember correctly.... I checked it out on my phone to make sure but,,,, duh, I already removed it (face palm).
It's in there somewhere.
Run install again and right down all the errors... Then try to find them in the script file.
I'm new to this also (as far as motorola stuff) too. And I take risks that most people wouldn't..... Hell, if I mess something up bad enough , just sbf back.
I'll try to help you more when I get off work... Maybe send you my roms that have already been fixed.
Make sure to turn off script and signature asserts off in cwm... Sometimes that helps.
Sent from my Milestone X using XDA App
Click to expand...
Click to collapse
Thank you sir! I'm gonna try that.

Brickster said:
I too just upgraded from the Hero....and I still love that phone! My hero has had every rom known on it,,,and some that weren't even made for it....It's unbrickable! LOL
Yea, the Milestone is a little more finicky than the Hero, and with Motorola's locked bootloaders, one could get in a fix..
I've ran the past 3 nightlies and currently on cm_shadow_full-154.zip.
I tell ya, they all have some kind of bug somewhere. It all depends on what you want to put up with. Me, personally, I like the stock ota 2.3.5 from Cspire. It works. Plain and simple. Now, I would like some of the CM7 options and spare parts.
Click to expand...
Click to collapse
I despised that phone lol, wait i take that back, i guess i had "phone" envy lol Mine was a rom whore as well, it was rooted almost immediately after i got it with the ole gold card method.
the ota 2.3.5 is actually a good CLEAN rom, i do like the fact that it is so clean, just need a few tweaks as you said from the cm7 build, status bar tweaks ect..
may build up one.
built a rom for a tablet we are selling here, BIG learning curve but the locked boot-loader throws a real curve ball
now, have you gotten it to overclock?

Brickster said:
. Hell, if I mess something up bad enough , just sbf back.
Click to expand...
Click to collapse
that still amazes me. i haven't tried it on 2.3.5, but when i did it from stock 2.2.2 it was a no go.... maybe it will only work if you are already on 2.3? hell i dunno... motorola has me chasing my tail.... like everyone else, i came from the hero too, that was one awesome little phone. i read somewhere that the motorola bootloader had been cracked by someone on here but..... not sure what ever happened there.....

Droid Pro Stuck On Bootloader

My Driod Pro is stuck in bootloader. It was not rooted. It was completely stock for that past 1.5 years. I had it in my pocket and went to use it and it was on the bootloader screen. I took it to Verizon and they couldn't do anything so ended up upgrading to iPhone 4S but I still want to get my Droid Pro working again...
Any thoughts? I saw other models with the bootloader issue but am not sure if those solutions would work for the Droid Pro.
(hopefully I won't lose all my stuff on the Droid Pro)
Thanks in advance!

Can you post or type what the bootloader screen says?
P.S. why did you go with the iphone over another Android

Bootloader
03.0A
Code Corrupt
Battery OK
OK to Program
Connect USB
Data Cable
That's what they screen says.
Went with an iPhone to just consolidate and family and friends have iPhones.

If it was a Samsung you'd use Odin and flash a new rom on...
any moto experts care to give us a clue what should be used for this situation?

I was able to revive the phone!
Used RSD Lite and SBF files. Ran it. Restarted phone by pulling battery. Got the green Androind icon with yeallow exclamation so did a full factory wipe and the phone started up perfectly.
Took a few more hours of research and finding the SBF files but it worked.
Thanks.

Which .sdf did you use? Because recovery-clockwork-2.5.0.1-sholes.sbf
from
http://wiki.cyanogenmod.com/wiki/Motorola_Droid:_Full_Update_Guide
isn't working for me
("phone is not compatible with multi-interface superfile")

jago25_98 said:
Which .sdf did you use? Because recovery-clockwork-2.5.0.1-sholes.sbf
from
http://wiki.cyanogenmod.com/wiki/Motorola_Droid:_Full_Update_Guide
isn't working for me
("phone is not compatible with multi-interface superfile")
Click to expand...
Click to collapse
you must install droid 2 bootstrapper from market....
open the app click on bootstrap recovery, then reboot recovery...
You must have your phone rooted...

I was going to say your best bet would be to sbf it back to verizon default following my instructions here but ignoring the root part. Iphone? Really??
http://forum.xda-developers.com/showthread.php?t=1590489

jago25_98 said:
Which .sdf did you use? Because recovery-clockwork-2.5.0.1-sholes.sbf
from
http://wiki.cyanogenmod.com/wiki/Motorola_Droid:_Full_Update_Guide
isn't working for me
("phone is not compatible with multi-interface superfile")
Click to expand...
Click to collapse
I used DroidPro_2.26.20_FULL.sbf.zip from MyDroidWorld.

retrobot said:
Iphone? Really??
Click to expand...
Click to collapse
Returned the iPhone and back on DroidPro!

dubLeE said:
I used DroidPro_2.26.20_FULL.sbf.zip from MyDroidWorld.
Click to expand...
Click to collapse
Thanks bud! There's thankfully a few mirrors out there for it post megaupload now.
I managed to get CyanogenMod9 on it but that was by rooting and then doing the .zip over the top.
But this wouldn't be as thourgher as using a .sbf would it? I mean, the kernel is still old right?
It seems to be running quite well but one problem. When trying to use the keyboard the screen goes blank... how's that image for that kind of thing you reckon?
For anyone else reading this, CM9 ICS seems to work ok apart from that keyboard problem, but I'm running an older kernel.
Can I achieve the same usability as a i9000 on Ice Cream Sandwich...?

[Q] Screen not recognizing touch

I've been looking around and found nothing about this... So, a little back story...
Yesterday I updated to CM9, and it all was good. Trying to tune it, I elevated the number of touchscreen points (dont remember well the name of that option) to 4... but then I was like "why I need that much? Let's reduce to default" and screen no longer recognices touch keypress, not even the softkeys are working... Thought it was a CM9 bug and restored to original stock rom and bug still present...
Anybody has faced this? USB Debugging is disabled, so no way to extract a logcat (sorry for that)...

dbarrera said:
I've been looking around and found nothing about this... So, a little back story...
Yesterday I updated to CM9, and it all was good. Trying to tune it, I elevated the number of touchscreen points (dont remember well the name of that option) to 4... but then I was like "why I need that much? Let's reduce to default" and screen no longer recognices touch keypress... Thought it was a CM9 bug and restored to original stock rom and bug still present...
Anybody has faced this? USB Debugging is disabled, so no way to extract a logcat (sorry for that)...
Click to expand...
Click to collapse
Did You wipe data too apart from cache and dalvik while reverting ?

AnkurBedi said:
Did You wipe data too apart from cache and dalvik while reverting ?
Click to expand...
Click to collapse
I tried that, performed a Factory Reset with CM9 and no go. Restored back to Froyo and screen still doesn't respond.

dbarrera said:
I tried that, performed a Factory Reset with CM9 and no go. Restored back to Froyo and screen still doesn't respond.
Click to expand...
Click to collapse
Try flashing the kernel again and then the ROM zip .

AnkurBedi said:
Try flashing the kernel again and then the ROM zip .
Click to expand...
Click to collapse
Full wipe > Kernel > CM9 > Cache/Dalvik wipe > boot
Nothing

dbarrera said:
Full wipe > Kernel > CM9 > Cache/Dalvik wipe > boot
Nothing
Click to expand...
Click to collapse
The new Boot menu is touch enabled . Does the touch get recognized there ?
i am using CM 10 .
PS : From advanced try fix permissions too . I am at a loss to other solutions , apart from flashing fixed sbfs

Nope, yesterday (while working) a blue dot appeared where I touched in the recovery screen. Now, not even that... =(

I've been searching all around and found out I'm not the only one with this problem... Some have solved it by removing the sd card, I tried that solution and no luck... Guess I'll be flashing a sbf and pray for some warranty luck...

dbarrera said:
I've been searching all around and found out I'm not the only one with this problem... Some have solved it by removing the sd card, I tried that solution and no luck... Guess I'll be flashing a sbf and pray for some warranty luck...
Click to expand...
Click to collapse
Flashing a stock sbf would work, it worked atleast for me when i too did the same a month ago. Best of luck
Sent from my alienware lappy

vedang81 said:
Flashing a stock sbf would work, it worked atleast for me when i too did the same a month ago. Best of luck
Sent from my alienware lappy
Click to expand...
Click to collapse
Really? Which SBF version you flashed?

dbarrera said:
Really? Which SBF version you flashed?
Click to expand...
Click to collapse
I dnt remember properly just google stock sbfs for defy plus... flash it through rsd. It should work for u. And forst of all it doesn't matter vich one u flash coz u just want to ur phone to start up.. so u decide.. later u got options
Sent from my alienware lappy

vedang81 said:
I dnt remember properly just google stock sbfs for defy plus... flash it through rsd. It should work for u. And forst of all it doesn't matter vich one u flash coz u just want to ur phone to start up.. so u decide.. later u got options
Sent from my alienware lappy
Click to expand...
Click to collapse
True... Oh well... When I get home I'll get into it...

dbarrera said:
True... Oh well... When I get home I'll get into it...
Click to expand...
Click to collapse
I read ur thread abt what next... is it so that u don't know baseband num or kernel or whatever it is? The only option is flash all
Although here's the link to all sbfs for defy and defy plus http://forum.xda-developers.com/showthread.php?t=966537
Enjoy
Sent from my alienware lappy

Flash all, One must work... right? Yeah... I think I'll get into it... In my signature is the original version that came loaded, if it helps in any way...
I read that thread and it points to other threads where I have to fish the DL links... ATM, I'm downloading a CEE (wth does CEE means?) version... Office internet connection sucks, so for the other SBFs I'll download when I get home...

dbarrera said:
Flash all, One must work... right? Yeah... I think I'll get into it... In my signature is the original version that came loaded, if it helps in any way...
I read that thread and it points to other threads where I have to fish the DL links... ATM, I'm downloading a CEE (wth does CEE means?) version... Office internet connection sucks, so for the other SBFs I'll download when I get home...
Click to expand...
Click to collapse
As per i remember i flashed 2 or 3 for my Defy... if its wrong it wnt boot... aftr 2-3 attempts i succeeded. No idea abt that CEE. But thats the option coz i dnt think warranty would help here though worth a try.
Sent from my alienware lappy

Please ask all questions in the Q&A section. Thread moved there.

TeeJay3800 said:
Please ask all questions in the Q&A section. Thread moved there.
Click to expand...
Click to collapse
Sorry and thanks for the heads up...

Tried Latin America (Retail, Claro), British (Retail)' and no luck so far.. Iusacell Mexico, Claro Latin America previous version, T-Mobile US are in line downloading... Just wondering, couldn't it be the digitizer that is malfunctioning? I have a 2-year warranty still (bought at Best Buy)...

So, I went through Hell and back... Flashed Retail and Carrier SBFs and no luck..Which makes me think that problem is officially hardware... I'll flash an english SBF so I can send it back for warranty.. Fingers crossed... Thanks for your help anyway...

dbarrera said:
So, I went through Hell and back... Flashed Retail and Carrier SBFs and no luck..Which makes me think that problem is officially hardware... I'll flash an english SBF so I can send it back for warranty.. Fingers crossed... Thanks for your help anyway...
Click to expand...
Click to collapse
Sent from my HTC Wildfire S A510e using xda premium