Hi all, got my MyTouch 4G a couple weeks ago and immediately started researching how to root it and install a non-Sense ROM. Finally got up the nerve a few days ago. This is my first post, so I can't post links. I followed the "TMobile myTouch 4G: Full Update Guide" on the CyanogenMod Wiki.
To be clear, I did the following:
- permroot via "gfree -f"
- Flash ClockworkMod Recovery (3.0.0.5)
- Flash CM7 Nightly build 34 + gapps via Recovery
After doing so and using it for a bit, I noticed that the "back" or "<--" button on the front wasn't responding to button presses at times. Sometimes it would be fine, then sometimes it would take a "long press" on the button to get it to work, then finally it would stop working altogether, only to randomly start working again later.
I thought maybe this was a problem with the nightly build, so last night I wiped all data and flashed CM7 build 38. It only got worse after that. Now, the back button NEVER works, and the MENU button is now acting buggy in the same exact way the back button was before. I also noticed the "Genius" button doesn't work either, but I don't know if it was working in build 34 because I don't use it.
I tried booting into recovery and cleaning caches/wipe and reset/clean davlik/etc and nothing worked.
I went into the "Key Test" and got NO RESPONSE when pressing the menu, back or genius buttons All the other buttons on the phone still work as expected. It's amazing how many apps depend on a functional back button. I am stuck in configuration menus in a couple of apps because I can't back out of it!
So to the point... what are my options? How can I get these buttons back?
Thanks in advance.
texastoast said:
Hi all, got my MyTouch 4G a couple weeks ago and immediately started researching how to root it and install a non-Sense ROM. Finally got up the nerve a few days ago. This is my first post, so I can't post links. I followed the "TMobile myTouch 4G: Full Update Guide" on the CyanogenMod Wiki.
To be clear, I did the following:
- permroot via "gfree -f"
- Flash ClockworkMod Recovery (3.0.0.5)
- Flash CM7 Nightly build 34 + gapps via Recovery
After doing so and using it for a bit, I noticed that the "back" or "<--" button on the front wasn't responding to button presses at times. Sometimes it would be fine, then sometimes it would take a "long press" on the button to get it to work, then finally it would stop working altogether, only to randomly start working again later.
I thought maybe this was a problem with the nightly build, so last night I wiped all data and flashed CM7 build 38. It only got worse after that. Now, the back button NEVER works, and the MENU button is now acting buggy in the same exact way the back button was before. I also noticed the "Genius" button doesn't work either, but I don't know if it was working in build 34 because I don't use it.
I tried booting into recovery and cleaning caches/wipe and reset/clean davlik/etc and nothing worked.
I went into the "Key Test" and got NO RESPONSE when pressing the menu, back or genius buttons All the other buttons on the phone still work as expected. It's amazing how many apps depend on a functional back button. I am stuck in configuration menus in a couple of apps because I can't back out of it!
So to the point... what are my options? How can I get these buttons back?
Thanks in advance.
Click to expand...
Click to collapse
Have you tried a different keyboard?
To be clear, I'm talking about the PHYSICAL buttons on the front of the phone.
Well, with no other ideas, I reflashed the stock mt4g ROM, unrooted and took it back to TMo. They swapped me out with a new one (good ffc, good screen).
Unfortunately, this new one is resistant to rooting. Using the same CyanogenMod Wiki article referenced above, "rage" seems to work (I get the # in terminal), but "gfree -f" gives an input error when trying to do the part7 backup and "sync" gives an I/O error and freezes the device. The part7 backup files created on the SD card are all zero bytes (plural because I've tried multiple times).
I found other posts about the input error and I/O error for other devices, but no resolution.
I also tried visionary, but it didn't work. I temprooted and again it seemed to work (# in terminal). When I tried to permroot it said it needed to be temprooted in order to work, implying that it was not, in fact, temp rooted. One time, after doing a factory reset and immediately loading visionary, it seemed to actually work. I was able to temproot and proceed to the permroot which also seemed to succeed, but then the phone rebooted and the result was no root ($ in terminal).
Any ideas? Links to more recent permroot instructions? Anything?
Simply because I don't like leaving open-ended threads, I thought I'd wrap this one up. I ended up returning the second MT4G to TMo and getting a third one shipped. For some reason they sent 2. First thing I did was try rooting both. 1 rooted, the other one did not. OK, so I checked the FFC's, both slightly off-center, but flat against the glass. Checked the screens, and the rooted one had panel_type 2 and black was obviously blacker at an angle than the other one, so it looks like I got a winner. Successfully flashed CM7 and everything still works.
On the G2, HTC updated something (radio I think) to patch the exploit used by gfree. If they're doing that now for the Glacier as well, then it may still be possible to use gfree if you downgrade using a pre-update firmware image from the forums. But, since it seems you have one that you're satisfied with, maybe there's no sense in bothering with it. (Then again, since you have a spare to play with, you might decide to have some fun and try it.)
Actually, I don't have a spare. I sent both unrootable phones back. Last thing I need is to be charged for that second phone they accidentally sent.
I don't know what the problem actually was, but I can see from these boards that I'm not the only one. It fails at the part where it's trying to set the eMMC r/w and it can't do the part7.* backup.
There's a good chance gFree may have been failing on the second phone because your phone was connected to your computer via USB. It's normally not that big of a deal, but MT4Gs are set to automount the sd card upon connection. Gfree freaks out about this and fails.
Glad you got everything figured out, even if it took you 4 phones.
Well, I have a HipStreet Nova HS-7DTB1-4GB Chinese Tablet with Android v2.2 Froyo.
I don't know much about froyo but i think mine has stock rom with little modifications.
I am not getting any touch response from the phone. I faced this problem one before when i deleted the ILITEK Touch Utility (manages touch screen functions on my tablet) after rooting the phone, but physical buttons were working so i tried some combination of keys when powering on the tablet and one them worked and it said something like recovering your phone and it flashed back the original firmware back, so i think it has some kind of recovery mod.
But this time i was trying to manually update the ILITEK Touch Utility and the touch became immediately Irresponsive. now i cannot remember that combination of keys i used last time, i think i have tried all combinations but now it doesn't flash back the firmware, please help if you can.
The Tablet has A Power Button, Auto-Screen-Rotation Lock, Home Button, Menu Button, Volume Up and Down Buttons and A Back Button!
I am still new to android and don't know much about Android, So bear me if i look stupid to you
Hey guys,
I have a really strange display issue with my Galaxy R.
I'm on CM10.1 nightly and already tried different nightlies with factory reset and wipe data/cache.
If the phone is not used for a while (sometimes even after 30 minutes), meaning it is on and screen is off, the display won't turn on anymore.
So I press the power button and the capacitive buttons light up, but the screen stays completely black.
Today I noticed that I can even use the touch screen and I could hear all sounds, I even managed to open the dialer and start typing blindly and it would make the dial sounds.
But whatever I try, the screen won't turn on.
Also, it seems when I'm connected to a charger and/or connected to wifi, this problem doesn't seem to occur.
Then I have no choice but to remove the battery, but then often I can't even start the phone.
Sometimes it takes some minutes, sometimes a really long time until I can start it again.
Usually the battery isn't drained, this only happened once.
This occurs after I dropped the phone twice, so it might be related to that.
(Though before I've also dropped it and this never happened.)
Any ideas?
flash stock ics and see if problem persists.
once i flashed a custom rom and faced this issue, reverted to stock and now my device is running with zero issues.
Nikhil said:
flash stock ics and see if problem persists.
once i flashed a custom rom and faced this issue, reverted to stock and now my device is running with zero issues.
Click to expand...
Click to collapse
I tried to find the stock rom online, but all links seem to be down.
Do you know where I can get it?
wasabah said:
I tried to find the stock rom online, but all links seem to be down.
Do you know where I can get it?
Click to expand...
Click to collapse
You need to register and then download from here.
Thanks for that, I installed newest stock rom.
Could boot fine, set up the phone, put it to the side.
One hour later I checked it - same problem again.
Capacitive buttons flaring up, screen not.
Thanks for that, I installed newest stock rom.
Could boot fine, set up the phone, put it to the side.
One hour later I checked it - same problem again.
Capacitive buttons flaring up, screen not.
Then you should visit SSC. They can only repair your device.
Hi everybody! Hope someone can help me with this little problem.
A month ago I had a problem with the vibration on my One S, the engine was broken, so my uncle decided to change it by himself (the phone was bought via aliexpress). Then, there was a problem with the screen and he also changed it. At that moment the phone had CyanogenMod 11 installed.
The problem is that after reparing it, and when I change to a sense based rom, the optical keys for home, back and multitask aren't working, whereas those keys do work when I'm on TWRP or in CM 11.
Does anybody knows what may happen?
Hello, everyone.
I tried to install AOSiP 9.0 pie official on my Huawei GR5(I even check 256sum, and make sure nobody touched the original ROM), everything works fine, and i like that os, the only thing is bothering me is the home screen at bottom, there is a Google sign "which can drag up) taking some space, i can not get ride of that. It is not a big problem. I still can use it, i like that simple and customed interface.
Then there is a problem on my phone yesterday, I accidently pressed "power key" several time, then my phone had no response, like brick. I only can see there is light on my charging display light. The full screen is black whatever i do. When i got home, i use ADB command to wake phone up again.
Then i flashed back LineageOS 17.1 again.
What happened to my phone? did anyone have this problem before?