Related
well im attempting to port a rom from the cdma hero to the verizon droid eris and i have evrything working great except the softkeys right below the screen and ive tried switching out some of the .so files and i still cant seem to get them to work... the haptic feedback works like they should be working but the os dosent respond to the action... any ideas?
Sent from my Eris using the XDA mobile application powered by Tapatalk
kaiya215 said:
well im attempting to port a rom from the cdma hero to the verizon droid eris and i have evrything working great except the softkeys right below the screen and ive tried switching out some of the .so files and i still cant seem to get them to work... the haptic feedback works like they should be working but the os dosent respond to the action... any ideas?
Sent from my Eris using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
Kaiya, I would recommend you ask in the Droid Eris development forum, as you will get more exposure for your issue there... I am sure others have seen this problem. Sorry, just noticed this post only now.
Then this thread will be moved there. Thanks dsixda.
goto the irc and ask the devs. thats the only way to get a quick response
Ok, i'm not a noob but i'm not the best at this stuff either. i have searched for the past 3 days. Got my DX2 the other day coming from a droid incredible. Day one of the incredible i had it rooted, then had it S-off not far after.
Day one with the dx, havent done much research. Get the phone, check for system updates, it says it has an update for 2.3.3. O yay, i don't have to wait to get gb on here. woohoo. DL it while at work since i shouldn't be playing on the phone anyway.
Get home. go online to try see what i have to do to get root so i can get some screen shots going and just all around get it back to the feel of having control of my phone. see a few ways of root, all of them saying to sbf back to 2.2. Well damn, wish i hadnt updated. Ok, lets try this sbf thing.
IDK why, but it won't let me sbf. Ive tried. Several times. No dice, always says failed.
Lets keep looking. O yay, a one click method for the ota GB?!?! woohoo!! i try it....try it several times. try it more times.....WTMFHELL!!???!!!?? i got nothing. i don't know why it wont let me root it...but it wont. if anyone has any advice, any tips...anything at all, i'm all ears. i've tried sbf, i've tried the adb commands but for some reason it won't let me use adb, says java isn't in the path, cant fix it. tried one click, different variations of one click. i got nothing
build number 4.5.1a-dtn-117-15
if anyone can help me i would greatly GREATLY APPRECIATE IT
sorry for the long wind
thanks for your time
-Typhoone
There is a one click root that i just used on a freinds phone and it worked great and you don't have to do any of that sbf'ing or anything...
http://rootzwiki.com/showthread.php?t=3714&p=75934
http://rootzwiki.com/showthread.php?t=3714&p=75934&viewfull=1#post75934
not fast enough
Thats the thing, I've done that one. 2 versions of it. Said I should have root. No dice. Checked through connect bot just to see. still have the $ instead of the #. No busy box, no nothing.
Sent from my DROID X2 using xda premium
is ther an app called superuser in your app drawer with a kinda droid pirate icon?
Did you install moto drivers? Maybe its an adb problem...adb can be tricky what os are you using on computer?
Check this out...
http://forum.xda-developers.com/showthread.php?t=502010
I have it. Got excited. Tried to use drocap and it actually asked for su permissions. Gave it, won't take pic. Opened titanium backup, no root rights.
Sent from my DROID X2 using xda premium
Windows 7
Sent from my DROID X2 using xda premium
go to market and download app called busybox installer, it will give you options to what version of busybox you want...select 1.18.2 and try to install.
Won't open. Can't run, may be because it doesn't have root rights
Sent from my DROID X2 using xda premium
Sent from my DROID X2 using xda premium
Maybe try to sbf to froyo 2.2 and then install P3's Rooted GB update, have you tried that?
it won't let me sbf, keep getting a failure every time i've tried.
does it try to sbf then fail? Does the phone show up in RSD?
Try a different sbf file maybe the one you have is corrupt.
WWW.k33pw1shen.WordPress.com I have all the files over there
Dx2RGB.E
The only reason I referred you there is someone commented on my page that they had tried a couple different things and mine was the only one that worked
Dx2RGB.E
tried it using a different sbf file and a different usb port on my comp and its in the process of makine me feel like it just may work.
just rebooted and
bootlooped. lol
recovery
full wipe
2.2
thanks for your help, greatly appreciated.
-ty
Glad we could help
Dx2RGB.E
i know i'm late, but are you sure you were on charging mode, i know its a bit out there but that could effect.... ALOT
Side note, none of the screen cap apps on the market work on the x2. I believe it's a tegra 2 issue.
Someone wrote an app called "Screen Grabber" for the Atrix that works perfectly on the x2.
http://forum.xda-developers.com/showthread.php?t=1009451
Sent from my DROID X2 using XDA App
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'm not sure if its cause iv'e flashed so many ROMS but my keyboard isn't as responsive as it used to be, i can rarely hit the P key anymore it always will click the O button. Also when it write "hahahahahaha" the A key stops working and only H's will come up like this "Hahahahhhahahhh" something like that. Can anyone help me fix this? Or suggest what I should do?
So i'm guessing i might be the only one? or no one else knows what to say?
Never heard of this. Do you run superwipe after wiping and b4 flashing rom?
Sent from my ADR6400L using XDA
What's superwipe?
Superwipe is a program that you flash, it does a very good wipe of everything, after you have aleady wiped everything. Ive been using one since the dinc days, never had an issue.
Sent from my ADR6400L using XDA
Could you give me a download link for it? i might as well start using it now haha.
No I've had this happen as well. It happens with A, S, D, J, K, and L for me. As if it's just those two little strips.
It's only happened recently too though, and has happened even if I use different roms and wipe fully. I might try that Superwipe deal though, I'm hesitant to give up my T-Bolt as I've heard it's the only phone with simultaneous voice/data and 4G.
That would be a hardware problem( i had the same thing).... put ur phone to stock and call vzw.... they will send u out a new one as long as its under warranty
Sent from my DROID BIONIC using xda premium
keyboard
thunderbolt33 said:
I'm not sure if its cause iv'e flashed so many ROMS but my keyboard isn't as responsive as it used to be, i can rarely hit the P key anymore it always will click the O button. Also when it write "hahahahahaha" the A key stops working and only H's will come up like this "Hahahahhhahahhh" something like that. Can anyone help me fix this? Or suggest what I should do?
Click to expand...
Click to collapse
have you tried swiftkeyX. if you have the same problem when using a different keyboard, probly a hardware problem. call verizon
FrostyOrDie said:
have you tried swiftkeyX. if you have the same problem when using a different keyboard, probly a hardware problem. call verizon
Click to expand...
Click to collapse
Just started having the same problem last night except I always use swiftkeyX and verified the issue using the stock keyboard. Replacement phone will be here by Wed.
I have really messed up. I cannot get into my phone at all. button reset starts after being plugged in for a few minutes then green light comes on when plugged in followed by, "Failed to Boot 1". Motorola of course shows but phone goes no further. We have tried everything we can think of including, all Verizon sbf's & intelos sbf's. Not sure what to do. My phone is a Motorola Droid X2 MB867.
e.penrose1 said:
I have really messed up. I cannot get into my phone at all. button reset starts after being plugged in for a few minutes then green light comes on when plugged in followed by, "Failed to Boot 1". Motorola of course shows but phone goes no further. We have tried everything we can think of including, all Verizon sbf's & intelos sbf's. Not sure what to do. My phone is a Motorola Droid X2 MB867.
Click to expand...
Click to collapse
Reinstall ddrivers, use latest rsd lite or sbf flash, reflash with Verizon android 2.3.4. Failed to boot 1 is a bootloader failure if I remember right. Keep trying till it boots.
Sent from my Nexus 7 using XDA Premium HD app
Question
Lrs121 said:
Reinstall ddrivers, use latest rsd lite or sbf flash, reflash with Verizon android 2.3.4. Failed to boot 1 is a bootloader failure if I remember right. Keep trying till it boots.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I think I may be missing something; if I cannot get the phone to come on at all except for a couple of minutes when it states Failed to Boot 1, then how do I go about proceeding?
Beth
e.penrose1 said:
I think I may be missing something; if I cannot get the phone to come on at all except for a couple of minutes when it states Failed to Boot 1, then how do I go about proceeding?
Beth
Click to expand...
Click to collapse
make sure its completely off then start the phone holding up on the volume rocker. that should bring it into rsd mode. if it wont stay on that usually means the battery is low and it needs to be charged before flashing. however it will not charge the battery in the state its in now.
Added Note....
e.penrose1 said:
I think I may be missing something; if I cannot get the phone to come on at all except for a couple of minutes when it states Failed to Boot 1, then how do I go about proceeding?
Beth
Click to expand...
Click to collapse
I really appreciate everything you are doing to help me. I do have one more detail to add. I have been running eclipse with only one problem, the data never worked. My wifi worked fine but never any data. Any ideas would be wonderful.
Thank you Again,
Beth
Got Battery (x3) Same Story
Lrs121 said:
make sure its completely off then start the phone holding up on the volume rocker. that should bring it into rsd mode. if it wont stay on that usually means the battery is low and it needs to be charged before flashing. however it will not charge the battery in the state its in now.
Click to expand...
Click to collapse
Well, one exception, I am no longer getting "Battery to Low to Flash"....
I have RSD Lite, Daytona & nTelos SBF via your files (Thank you). Help Please
E
e.penrose1 said:
Well, one exception, I am no longer getting "Battery to Low to Flash"....
I have RSD Lite, Daytona & nTelos SBF via your files (Thank you). Help Please
E
Click to expand...
Click to collapse
If I had known you had the milestone x2 I would never have recommend red lite. It erases your carrier files which removes your ability to have a 3g data connection the only way to fix it is to go to your carrier and have them rewrite their files to it. However you need a fully functional stock ROM for that to work. Check out this thread I has everything you need to know about messing with the mx2 http://forum.xda-developers.com/showthread.php?t=2101633
Sent from my SCH-I535 using xda premium
Tried & Tested
Lrs121 said:
If I had known you had the milestone x2 I would never have recommend red lite. It erases your carrier files which removes your ability to have a 3g data connection the only way to fix it is to go to your carrier and have them rewrite their files to it. However you need a fully functional stock ROM for that to work. Check out this thread I has everything you need to know about messing with the mx2 http://forum.xda-developers.com/showthread.php?t=2101633
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I thank you but, I have been looking at that thread and to say the least my brain is fried. Should anyone want to trade a working touchscreen android for Verizon for an experiment I am game lol. Being without a phone is almost calming and peaceful but, NOT.
E.
e.penrose1 said:
I thank you but, I have been looking at that thread and to say the least my brain is fried. Should anyone want to trade a working touchscreen android for Verizon for an experiment I am game lol. Being without a phone is almost calming and peaceful but, NOT.
E.
Click to expand...
Click to collapse
He did a lot of experiments I was more referring to the start of the thread which explains how to root, flash and also restore to stock
Sent from my SCH-I535 using xda premium
I have tried them all with no result thank you though.
E
e.penrose1 said:
I have tried them all with no result thank you though.
E
Click to expand...
Click to collapse
Then I'd have to say its time to talk to the carrier
Sent from my SCH-I535 using xda premium
Success!!!!
Lrs121 said:
If I had known you had the milestone x2 I would never have recommend red lite. It erases your carrier files which removes your ability to have a 3g data connection the only way to fix it is to go to your carrier and have them rewrite their files to it. However you need a fully functional stock ROM for that to work. Check out this thread I has everything you need to know about messing with the mx2 http://forum.xda-developers.com/showthread.php?t=2101633
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Got it although I am not sure how, a combination of RSD Lite, Experia Flasher, Easy SBF among others.
E.
e.penrose1 said:
Got it although I am not sure how, a combination of RSD Lite, Experia Flasher, Easy SBF among others.
E.
Click to expand...
Click to collapse
What ever works for you
Sent from my SCH-I535 using xda premium