Related
I'm in a bit of a panic and think I need help.
I bought the HTC Hero from Bestbuy roughly Nov. 2009. And like everyone else love it, but was frustrated with all the bugs and slowness, lag ext. Reading and waiting for 2.1, getting impatient weekly...blah blah blah....but horrified to try to root the phone, because im not the techiest guy in the world, so when I saw that there was a 2.1 leak that I could just click from my computer, I did it like an impatient child.
RUU_Hero_C_Sprint_2206511_signed_test.exe
and have had a major problem ever since. The phone will shut off if its not plugged in. I have to constantly turn it back on and wait for it to reboot.
So I followed "How-To repair your bootloader after using the 2.1 RUU" to the T! With no error messages and got it back to "stock" which still looked like 2.1 to me. I formated the SD card from the phone, did a full wipe in that black/green boot page and flashed Beezy's "option 4",
I believe I did a nanbackup right before the "option 4". But I don't think it matters, since the phone was shutting down before that anyway.
So that's where I am. If I'm messing around with the phone (on a call, web, playing with apps) it will stay on, but as soon as I set it down and the screen goes to sleep, thats it, when I pick it up and hit the menu or power button, it reboots (white screen, HTC logo). Am I F'ed? I do have insurance through sprint, but believe that is void now, since I stated messing around with it.
I swapped Batteries with my wife's phone and it still happend, so it's not a bad battery.
I'm sorry if I posted in the wrong forum. I did a search for "constant rebooting" and couldn't find anything similar to my problem.
Thanks in advance.
If all you see is the white htc screen you probably aren't actually rebooting just rosie is restarting. Probably because the ruu doesn't work too well on its own. I suggest you just take the plunge and root, wipe, and flash fresh 2.0d or damage 2.07.2 ( your choice really, both are excellent roms)
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
Well, first off it doesn't sound like you are rebooting, it sounds like sense might just be restarting.
Also, don't panic. Whatever you have done is fixable
surely someone who is not posting from their phone will be along to help soon, if not I'll be back home and on my pc in a few hours
Just to confirm
Can you go into settings > about phone > software information (1.5 maybe slightly different I can't remember any more) and tell us what Firmware version says? this way we can make sure that you are running the appropriate version to RUU back to 1.5 and reroot.
I am not sure exactly what is still on your phone.
Also have you ever flashed a radio update from flipz?
I agree, that it isn't rebooting, but its the sense crashing and restarting. I would also agree, that your best option would be to root.
Honestly, the guides are laid out as plain as they could be. It isn't that difficult, you just have to check and re-check typed commands, if done manually.
I think you will be pleasantly surprised and find it simpler than you think.
However, ALWAYS make sure to do to the following:
1. nandroid before you do anything.
2. NEVER EVER NEVER EVER touch anything that doesn't say CDMA HERO. (gsm hero radio flashes can literally fry your nice phone into a nice paperweight)
3. Don't be afraid to ask questions here. I'm pretty new to this, but there are a lot of cool helpful people.
4. nandroid again. (copy nandroids to your PC/Mac and keep a whole library of them.) I even have some extra google space that I've been uploading them to incase I'm not at my computer and I need one...lol)
5. Don't get too sucked into it.
Thank you guys for responding, as I was worried I would get flamed for being an idiot for doing what I did.
"I suggest you just take the plunge and root, wipe, and flash fresh 2.0d or damage 2.07.2 ( your choice really, both are excellent roms) "
Isn't "How-To repair your bootloader after using the 2.1 RUU" basically rooting the phone? Because after I follow those instructions, I get the the recovery menu. I just haven't tried Damage roms yes.
Also, "Well, first off it doesn't sound like you are rebooting, it sounds like sense might just be restarting."
Looks like a full boot...
HTC Logo white screen, green text
HTC Quietly Brilliant
Sparkly Sprint thing
HTC Quietly Brilliant
Lock Screen
Loading apps
I should mention that I have been testing things like, Turning off "Screen Timeout" completely, 10 mins, 1 min, 30 seconds...ext. And it still shuts down after a few minutes when the screen is off......HOWEVER, it is random as far as how long it has been sitting.....Sometimes the screen will be black for a minute and when I hit the menu or power it will reboot....sometimes it will sit for 10 mins and will turn on.....very random, but it WILL reboot eventually.
Thanks again, guys
Chaid said:
Looks like a full boot...
HTC Logo white screen, green text
HTC Quietly Brilliant
Sparkly Sprint thing
HTC Quietly Brilliant
Lock Screen
Loading apps
Click to expand...
Click to collapse
Do you see the first black HTC screen? I know I've done the HTC quietly brilliant screen, but then it goes right to lock screen and loading apps.
I still don't think it is a full reboot, but I'm not THAT up to speed with most of this stuff.
Also, RUU'ing back to stock, then rooting and installing a 2.1 rom by Damagless or Flips should be your best bet.
RUUing back to stock has some problems in and of itself, but it should go ok.
Chaid said:
Looks like a full boot...
HTC Logo white screen, green text
HTC Quietly Brilliant
Sparkly Sprint thing
HTC Quietly Brilliant
Lock Screen
Loading apps
Click to expand...
Click to collapse
Weird...
Regardless, this is fixable.
As Kcarpenter asked, post your system info if you can get to it.
What is your:
Firmware
Baseband
Kernel
Build
Software Number
PRI
PRL
Firmware: 2.1 -update1
Baseband: 2.42.00.03.10
Kernel: 2.6.29-d30020a8
[email protected] #1
Build: 2.20.651.1 CL157175 test-keys
Software Number: 2.20.651.1
PRI: 2.10_003
PRL: 60664
Chaid said:
Looks like a full boot...
HTC Logo white screen, green text
HTC Quietly Brilliant
Sparkly Sprint thing
HTC Quietly Brilliant
Lock Screen
Loading apps
Thanks again, guys
Click to expand...
Click to collapse
Sounds like you are using a 2.1 rom not the stock 1.5
I would try using this guide http://forum.xda-developers.com/showthread.php?t=608434 to correct your issues it will take you back to stock 1.56.651.2 that come with the phone
Oh and if you get any errors this will help too http://forum.xda-developers.com/showthread.php?t=654119
Guys, since he used the 2.1 RUU, isn't he only able to use the 2.1 RUU now? Not the 1.5?
I too am experiencing this.
Factory reset my phone and then flashed from 1.6 to 2.1. I have tried two different 2.1 roms (the sprint leak one and Freshrom) and both of them are causing spontaneous reboots of my phone. I never experienced reboots when on 1.6.
Software information:
2.1 fresh
baseband 1.04.01.09.21
Kernel is 2.6.29-d30020a8
build is fresh rom 2.0d
Software number is 2.20.651.1
PRI is flipz_01
PRL is 60660
any suggestions from anyone?
mrinehart93 said:
Guys, since he used the 2.1 RUU, isn't he only able to use the 2.1 RUU now? Not the 1.5?
Click to expand...
Click to collapse
I believe you are correct, although I have yet to use any RUU
OP, you really should just root the thing flash a rom and succumb to the new obsession you don't even know you have yet
Personally, I'm a fan of RegawMODv2.1, it's lean and stable.
I think that even though you have run 2.1 RUU we can take you back to a bone stock 2.1
When I get home tonight I will try to link to all of the appropriate guides to get you there.
Once we have you back at a stock 1.5 I think we can all say "ROOT IT!" but I would feel more comfortable knowing that you came from the begining in the right order of things.
And get you on a solid stable Rom. I have recently started having issues with my damage rom and all of the aps2sd stuff that has been going on. Not sure what I am going to move to next. But that's besides the point, and none of it is Damageless's fault.
Ok, Kcarpenter, I'll be waiting LOL. I have been f'ing with this thing for a few days now, reading different forums and searching and searching. I finally broke down and posted here, because I'm at a loss. So I REALLY appreciate you guys taking the time to help me. Plugging the phone into my work truck laptop and running to the house to plug it in is wearing me down...
You just need to get over the fear of f*ing up your phone and root it. I'm not sure where the treads are on everything you need, but it's pretty straight forward.
If you had rooted while still running 1.5 you probably would not be in this mess. And Flipz has Fresh Kitchen which makes it even easier to Root and put a recovery console on.
"If you had rooted while still running 1.5 you probably would not be in this mess." You are absolutely correct, &RoidRage. I got excited when I saw the word "Official" 2.1, and jumped the gun.
Chaid said:
"If you had rooted while still running 1.5 you probably would not be in this mess." You are absolutely correct, &RoidRage. I got excited when I saw the word "Official" 2.1, and jumped the gun.
Click to expand...
Click to collapse
That probably created lots of people to get excited.. Anyway, here is what I got
Okay first I looked here
http://forum.xda-developers.com/showthread.php?t=661057&page=6
Which directed me to
http://forum.xda-developers.com/showthread.php?p=6013606#post6013606<--------This is the one you really want.
If you get it to work then you can flash a custom rom. But make sure you download it and put it on the sdcard before doing anything else.
I know it says it is for the 110 error, but people have used it to get back to 1.5 from 2.1
Thanks, man. I'll give it a shot......I have nothing to loose at this point, so I'm over my fear of F'ing up the phone.
I would read everything first, I didn't have the time look it all over.
Editamn predictive text said wetting instead of everything.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
Rooted my Hero and it doesn't matter which custom Rom I've tried(Fresh, Damage, others) my phone will shut off most of the time it goes into sleep. I don't know its off until I go to wake it up by hitting the end button. When I restore back to the stock Rom(still rooted) it works fine. I do a wipe and a Dalvick wipe prior to flashing. I'd like to get this figured out so I can use one of the nice Roms. Thanks.
If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD
patkin said:
Rooted my Hero and it doesn't matter which custom Rom I've tried(Fresh, Damage, others) my phone will shut off most of the time it goes into sleep. I don't know its off until I go to wake it up by hitting the end button. When I restore back to the stock Rom(still rooted) it works fine. I do a wipe and a Dalvick wipe prior to flashing. I'd like to get this figured out so I can use one of the nice Roms. Thanks.
Click to expand...
Click to collapse
WOW! You are the first person that has had the same problem I have...I was never able to resolve the issue. I used that bastard 2.1 test leak.......read my posts and what I went through.
http://forum.xda-developers.com/showthread.php?p=6268366#post6268366
My phone works fine now with gumbo 1.5, but I cant use any 2.1 roms or the problem comes back......
kyouko said:
If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD
Click to expand...
Click to collapse
I am not positive what A2SD is. I have a new 8MB SD card that came today. If I pop that in what will happen. Should it be partitioned? Thanks.
Chaid said:
WOW! You are the first person that has had the same problem I have...I was never able to resolve the issue. I used that bastard 2.1 test leak.......read my posts and what I went through.
http://forum.xda-developers.com/showthread.php?p=6268366#post6268366
My phone works fine now with gumbo 1.5, but I cant use any 2.1 roms or the problem comes back......
Click to expand...
Click to collapse
Thank God I thought I was the only one. I searched but didn't see your thread. Weird problem.
Same problem here too since the new leaked 2.1 test ruu from damaged. The only 2.1 Rom that works for my needs without rebooting every 3rd or 4th time I wake it using the end call/power button is Damagedtrev 2.01, the updated 2.05 Rom in his thread just makes my phone reboot as described above. I don't have a link to his thread, but it would be interesting to see if it worked on your phone too. Other's have claimed a battery shorting might be causing this issue, but I'm not buying that. I've looked at /proc/lastkmsg for clues, but nothing obvious there. I hope the official Sprint update doesn't have this bug or sprint will be giving me a new phone. /end rant
I can't seem to find Damagedtrev 2.01
So I can't test it.
Here's the link to the thread.
I cannot post links, because of some restrictions,but here is the last part of the url.
forum.xda-developers.com/showthread.php?t=653622
here's the link for the full rom
Oops cannot post link to rom on 4shared, look in the bottom of the first post in the thread for a link to the full rom of DamagedTrev_v201
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.
Ok, downloading......stay tuned.
I really hope this 2.1 ROM works.....I'm kinda sick of 1.5.
Edit:
P.S. I'm reading that there is a battery issue....do you have that?
kyouko said:
If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD
Click to expand...
Click to collapse
Hey good news. I put the new SD card in after backing up the other one, partitioned it and copied the files and folders back on then flashed ALOYSIUS and so far so good. I have woken it up about 10 times in a row. Looking good.
I had tried that perticular Rom before with no success.
Interesting.....I'm using the 2 gig sd card that came with the phone....I wonder if that is my problem?
Well it started again. This was right after setting my Gmail and POP3 mail accounts. It shut off on the first sleep after this. Hmmmmm.
I'm re-flashing now and not setting up the mail accounts. Will report back later.
Waldo447
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.
Well, my friend. You were correct! full rom of DamagedTrev_v201 works on our phones for some strange reason. And updating his ROM caused the re-booting to start again. So whatever was changed from 2.0.1 to 2.0.5 is causing our particular problem. I'm not a dev by any means and don't know much about his stuff, but this is encouraging. Perhaps someone can figure out what it is?
I did notice that ALL the other 2.1 ROM's I have used that cause my phone to re-boot from sleep mode, is that when I hit the menu or power button to turn it on, the lights turn on, then reboot phone. With DamagedTrev_v201 that doesn't happen. The screen just pops up to unlock it.....don't know if that helps, it's just something I noticed.
Heres to crossing our fingers that someone can fix this!
P.S. I wiped and went back to Gumbo 1.5c as that 2.1 ROM was way to slow for me and I couldn't get bluetooth to work and audio would cut in and out.
reboot
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation
kwajr said:
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation
Click to expand...
Click to collapse
It's a full reboot. The phone actually turns off when it goes into sleep. You don't know it's off until you hit the button to wake it up and the phone boots up.
Now for the good news. After re-flashing and not setting up the email accounts it was still shutting downconfused so I started looking elsewhere so I opened up what I thought was a likely culprit in Autokiller and none of the presets where selected so I picked Moderate and haven't had a shutdown since which has been over an hour. Fingers are crossed. I'll report back later.
That's it I've wasted way too much time on this. Phone works great on the stock ROM. They must have planted some devious anti-flash widget in this phone. I'll leave it rooted for now.
patkin, dude, I felt the same...I gave up on 2.1.
download, wipe then flash Gumbo-1.5c-BARE-signed.zip after it reboots, download and flash Gumbo-Sense-signed.zip.
You flash Gumbo-Sense-signed.zip over the Gumbo-1.5. No need to wipe or anything, it just adds to the ROM. Fast as hell and works PERFECT.
http://www.4shared.com/file/217809392/5fcf1f5d/Gumbo-15c-BARE-signed.html
http://www.4shared.com/file/217811195/3afb5fcf/Gumbo-Sense-signed.html
Give it a shot....I think you will like it......let me know =)
Gumbo thred so you can read up if you like. http://forum.xda-developers.com/showthread.php?t=630221
Chaid said:
Waldo447
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.
Well, my friend. You were correct! full rom of DamagedTrev_v201 works on our phones for some strange reason. And updating his ROM caused the re-booting to start again. So whatever was changed from 2.0.1 to 2.0.5 is causing our particular problem. I'm not a dev by any means and don't know much about his stuff, but this is encouraging. Perhaps someone can figure out what it is?
I did notice that ALL the other 2.1 ROM's I have used that cause my phone to re-boot from sleep mode, is that when I hit the menu or power button to turn it on, the lights turn on, then reboot phone. With DamagedTrev_v201 that doesn't happen. The screen just pops up to unlock it.....don't know if that helps, it's just something I noticed.
Heres to crossing our fingers that someone can fix this!
P.S. I wiped and went back to Gumbo 1.5c as that 2.1 ROM was way to slow for me and I couldn't get bluetooth to work and audio would cut in and out.
Click to expand...
Click to collapse
Glad to see your rebooting issue was fixed with this rom even though you went back to gumbo 1.5. In my mind, this just confirms that it is not a battery issue. I never use bluetooth and have never experienced any audio loss with this rom, but apparently even people on the same hardware and firmware versions have different problems.
kwajr said:
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation
Click to expand...
Click to collapse
Full Reboot here too.
patkin said:
That's it I've wasted way too much time on this. Phone works great on the stock ROM. They must have planted some devious anti-flash widget in this phone. I'll leave it rooted for now.
Click to expand...
Click to collapse
Yeah, got my phone beginning of march 2010 and I also think there is something in the 2.1 test ruu or hardware that is keeping the phone from functioning properly with an altered 2.1 rom.
Just wanted to let people know what happened to resolve this. I went back to 1.5 then when 2.1 official came out last week I said what the heck if I can't enjoy a rooted custom 2.1 I'll try the official and guess what. Same problem as the other 2.1's.........phone shuts off randomly! Except this time they are replacing it with a new phone. Yeaaah! I'm probably going Evo now though since I found out I can get a new phone. Anyone need a new Hero?
I'm having the same problem.. One question. Does DarchDroid automatically move dalvik-cache to the sd
First let me say thank you to everyone who makes this place such an awesome resource. I'm sure I'm not the only lurker who feels a ton of gratitude and appreciation for all the time and effort shared here!
Because of that gratitude I just wanted to register and post this in the hope that it'd help someone else in the same position.
I was hesitant to root my vibrant because I'm really not in a position to replace it if I managed to destroy it in the process, but finally 2 days ago I gave in and did the one click root plus clockwork recovery process so that I could use barnacle wifi tether. Of course 2 days later this official over the air update gets pushed through, immediately filling me with dread.
I assumed it was froyo finally but did some reading first, mostly here; and while it was not the much anticipated 2.2 it still sounded like something I'd want to have. Plus there seems to be no simple way to get rid of the update nag in the notification bar unless you update.
So I went ahead and risked it. And I'm happy to say that despite a horrifyingly long pause at the galaxy s screen, the update went thru perfectly using just the official push delivery method, not Odin or anything but the stock delivery method.
Now I have media hub, the gps fix, my signal bars seem to finally be working right and maybe I'm fantasizing but the whole phone feels faster; and I didn't even lose root.
Anyway, I hope this helps someone who like me only rooted and clockworked for wifi tether.
I wasn't so luckly. I undid my lag fix and un rooted and still soft bricked mine and had to use odin to get it back
how long
HumanTarget said:
First let me say thank you to everyone who makes this place such an awesome resource. I'm sure I'm not the only lurker who feels a ton of gratitude and appreciation for all the time and effort shared here!
Because of that gratitude I just wanted to register and post this in the hope that it'd help someone else in the same position.
I was hesitant to root my vibrant because I'm really not in a position to replace it if I managed to destroy it in the process, but finally 2 days ago I gave in and did the one click root plus clockwork recovery process so that I could use barnacle wifi tether. Of course 2 days later this official over the air update gets pushed through, immediately filling me with dread.
I assumed it was froyo finally but did some reading first, mostly here; and while it was not the much anticipated 2.2 it still sounded like something I'd want to have. Plus there seems to be no simple way to get rid of the update nag in the notification bar unless you update.
So I went ahead and risked it. And I'm happy to say that despite a horrifyingly long pause at the galaxy s screen, the update went thru perfectly using just the official push delivery method, not Odin or anything but the stock delivery method.
Now I have media hub, the gps fix, my signal bars seem to finally be working right and maybe I'm fantasizing but the whole phone feels faster; and I didn't even lose root.
Anyway, I hope this helps someone who like me only rooted and clockworked for wifi tether.
Click to expand...
Click to collapse
thats great to hear since I'm rooted and i just installed ROM Manager/Clockwork in order to make a nandroid backup. Now Im wondering whether i should wait for the OTA to hit my phone or if I should use Kies Mini to do it manually over USB. In either case, could you please answer one question...how long did it stay at the galaxy s screen?
Becuase some people are saying it stayed on it for an hour and assuming they're soft bricked but if it really takes 1 hour and 2 minutes than that extra bit of patience is needed...
jblade1000 said:
thats great to hear since I'm rooted and i just installed ROM Manager/Clockwork in order to make a nandroid backup. Now Im wondering whether i should wait for the OTA to hit my phone or if I should use Kies Mini to do it manually over USB. In either case, could you please answer one question...how long did it stay at the galaxy s screen?
Becuase some people are saying it stayed on it for an hour and assuming they're soft bricked but if it really takes 1 hour and 2 minutes than that extra bit of patience is needed...
Click to expand...
Click to collapse
took about 3-6 minutes for me.
I got very worried... but was patient.
Stock ROM
Rooted
All bloatware removed.
wasted mine with no lag fix rooted on stock kernel, stock build..had to odin back and update via odin...****ty
well damn, im kinda at a loss then about whether to go through with this. I want the update but I dont have the time to be messing with flashing and odin right now...
Weirdddddddd
I to bricked my phone with the ota. I was rooted, stock rom, lagfix with clockwork. I undid the lagfix but still bricked. My boy's running the same without clockwork (never had time to put it on). Unrooted, delaged and removed the update.zip that was on the phone from root and cleared the cache. Ota worked without a problem. Some believe it is the result of an update.zip left on the sd which causes the problem.
Hey everyone, I woke up this morning to find a surprise! My Atrix screen was unresponsive. It took me a couple reboots to figure out that the top part of the screen doesn't respond to touch. Worse yet, none of the capacitive buttons work. So if I get into an app, most of the time, there's no real way for me to get out of it, thus requiring a reboot and more careful selections.
The weird part is, it happened within a span of about 2 hours. I woke up around 5:30AM, checked some emails and texts, and woke back up around 7AM with a buggy screen. It did drop from about 18 inches off the couch last night. But everything was in working order...
Right now I'm in the process of backing up my text messages, because I might have to use a set of them to prove my case in court.
What's the first steps to try to get it back working? Or do you think its a hardware problem(maybe a cable loose)? As far as returning it under warranty goes, I'm rooted and unlocked on Kenn's GB ROM, so that's a no-go.
bigb252 said:
Hey everyone, I woke up this morning to find a surprise! My Atrix screen was unresponsive. It took me a couple reboots to figure out that the top part of the screen doesn't respond to touch. Worse yet, none of the capacitive buttons work. So if I get into an app, most of the time, there's no real way for me to get out of it, thus requiring a reboot and more careful selections.
The weird part is, it happened within a span of about 2 hours. I woke up around 5:30AM, checked some emails and texts, and woke back up around 7AM with a buggy screen. It did drop from about 18 inches off the couch last night. But everything was in working order...
Right now I'm in the process of backing up my text messages, because I might have to use a set of them to prove my case in court.
What's the first steps to try to get it back working? Or do you think its a hardware problem(maybe a cable loose)? As far as returning it under warranty goes, I'm rooted and unlocked on Kenn's GB ROM, so that's a no-go.
Click to expand...
Click to collapse
you are unlocked/rooted/custom rom = no warranty
anyways backup and maybe reflash the rom and see how that goes.
Hopefully you don't need to replace the digitizer... But if you do, there are lots of videos and it's reported to be one of the easier phones to do. Keep that in your back pocket as an alternative to a lengthy and costly court fight over a phone with no warranty!
Sent
Thanks guys, I already knew the risks associated with rooting and unlocking. I used an app called SMS Backup+ that allowed me to backup all my sms/mms and it also linked and sent copies to my Gmail.
I'll go ahead and try a reflash
*EDIT*
Did a quick wipe of the phone, and during setup, everything was OK! When blur came back, it was back to the same thing.
Bump...
Still lost
I would suggest backup all you apps and do a complete wipe of data. I had a similar problem when I first installed Alien. This fixed the issue.
bigb252 said:
Thanks guys, I already knew the risks associated with rooting and unlocking. I used an app called SMS Backup+ that allowed me to backup all my sms/mms and it also linked and sent copies to my Gmail.
I'll go ahead and try a reflash
*EDIT*
Did a quick wipe of the phone, and during setup, everything was OK! When blur came back, it was back to the same thing.
Click to expand...
Click to collapse
I would do a wipe and reinstall. You could also fix your permissions through rom manager or cwm.
Sent from my MB860 using XDA Premium App
I had a simillar problem: WIPE through CWM solved this problem
hi, guys i had the same problem... I remember getting it shortly after updating it to the leak version of gingerbread. Since then I have flash Alien built #3 but the problem remains...
I'm currently doing a Nandroid backup of my phone so i could try flashing to cherrypie hopefully this will solve my problem cuz I'm seriously feed up with it...
do you guy's think this will help? if so any suggestions before i flash? thanks in advance...
I had this problem brand new out of the box. I just took it to the store and they gave me a new one. One other thing i noticed was the FP sensor/button was almost like loose and i had to push it in real far for it to work. Maybe its a stuck FP button...
Sent from my MB860 using XDA App
im having the same issue, i cant make the buttons work, i have wiped everything in CWM, and using fastboot also and nothing, also tried flashing different roms but the problem persists, if anyone know how to solve will be great
thanks
I think you have one file corrupted... I'll try to remember which
Sent from my MB860 using XDA App
I think it may be touchpad.cfg. try Googling that and see if you can find a clue.
Sent from my MB860 using XDA App
Try here: http://www.kandroid.org/online-pdk/guide/keymaps_keyboard_input.html#androidKeymapKeyLayoutMapTitle
Sent from my MB860 using XDA App
thnaks for the answear, i flashed the 10 point multitouch patch to see if solved the problem but it didnt, yesterday i reproduced the error but idk how to solve ir, im gonna make a thread to show what i did
i'm running on a darkside prefinal rom for about a month.
suddenly the soft stopped responding(don't work at all), and the screen sometimes think i'm touching it when the phone lays on the table far from me.
i think i should mention that before the darkside i had a gingerbread at&t stock rom and after that a cm7 nightly rom.
i read on the internet and even in this forum that i need to run a pds fix.
i tried that it fixed the phone for about day or two and then everything went wrong again.
i returned to the store where i bought the phone. they burned me a at&t original stock rom. that fixed the problem for two hours at most.
i wanted to know if someone knows how to fix it or did anyone encounter this problem.
thanks
Nir