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.
Related
So my FUZE was working fine since I bought it when it first came out. It was on Stock ROM, Radio, and SPL. I decided to flash the EnergyROM to try out the new Manilla. I installed the Hard-SPL, flashed the 1.12.25.19 radio, and then flashed EnergyROM 2.0 32209. First thing I noticed was that the DPAD was HORRIBLE.
It would not correctly sense what I am pressing! I press home, and some times it doesn't register anything, sometimes it thinks I pressed left. I try the back button but it thinks I pressed right. I have had this thing since it came out so I know how to use the DPAD now, but whatever happened has completely screwed it up! I thought it was the ROM so I went to the leaked AT&T Test ROM which is also VERY nice. But the problem is still there, the DPAD just does NOT work correctly.
Also, I was unable to send an SMS earlier until I soft reset the phone. That had never happened before either.
Since it is not the ROM, it is either the Radio or the SPL. What I don't understand is that many many people have installed both the same Radio and SPL without any problems. How can I fix my DPAD?
petard said:
So my FUZE was working fine since I bought it when it first came out. It was on Stock ROM, Radio, and SPL. I decided to flash the EnergyROM to try out the new Manilla. I installed the Hard-SPL, flashed the 1.12.25.19 radio, and then flashed EnergyROM 2.0 32209. First thing I noticed was that the DPAD was HORRIBLE.
It would not correctly sense what I am pressing! I press home, and some times it doesn't register anything, sometimes it thinks I pressed left. I try the back button but it thinks I pressed right. I have had this thing since it came out so I know how to use the DPAD now, but whatever happened has completely screwed it up! I thought it was the ROM so I went to the leaked AT&T Test ROM which is also VERY nice. But the problem is still there, the DPAD just does NOT work correctly.
Also, I was unable to send an SMS earlier until I soft reset the phone. That had never happened before either.
Since it is not the ROM, it is either the Radio or the SPL. What I don't understand is that many many people have installed both the same Radio and SPL without any problems. How can I fix my DPAD?
Click to expand...
Click to collapse
Did you try flashing back to the stock ROM? If that doesn't work, I wonder if flashing back to stock everything (ROM, radio, SPL) might kick out the bugs (?)
Did you hard reset after flashing? That might be your problem. And what programs/settings did you install? I would hard reset-don't run UC-then see if the dpad is working fine.
I had the problem without installing anything over the ROM itself. When you flash a ROM, it hard resets, so what does hard resetting again do? I spent like 2 hours getting it the way I like it so I don't want to hard reset again. I tried reflashing the radio but it still had the problem right afterwards, but now it seems to have stopped. This is very weired.
EDIT: It started doing it again but if I put the phone to sleep and bring it back, it normally fixes it. What an annoying problem. I am going to try to flash a different radio and see what happens. I just like this radio so much its GPS actually works decently.
petard said:
I had the problem without installing anything over the ROM itself. When you flash a ROM, it hard resets, so what does hard resetting again do? I spent like 2 hours getting it the way I like it so I don't want to hard reset again. I tried reflashing the radio but it still had the problem right afterwards, but now it seems to have stopped. This is very weired.
Click to expand...
Click to collapse
No, it doesn't do a full hard reset when you flash. A lot of crap is left over, and if you just start using the ROM, you get a bunch of random bugs, like, say your DPAD doesn't work. You're supposed to hard reset when the the phone asks you to align the screen. It's a must. Seriously, hard reset and start over and all of your problems will go away.
I reverted to my stock radio and the problem seems to have disappeared. I will try it out more tomorrow.
How is anything left over? It just seems so odd because I can't ever find anything from before when I flash a ROM.
It seems that I can still get fast GPS locks with this radio too, so I guess the A-GPS fix is all in the ROM.
petard said:
I reverted to my stock radio and the problem seems to have disappeared. I will try it out more tomorrow.
How is anything left over? It just seems so odd because I can't ever find anything from before when I flash a ROM.
It seems that I can still get fast GPS locks with this radio too, so I guess the A-GPS fix is all in the ROM.
Click to expand...
Click to collapse
I have no idea how anything is left over, it just is. Here's what mskip's thread says:
mskip said:
[FONT="]Flashing Via ActiveSync[/FONT]
[FONT="]1. Download your prefered Rom from the Raphael Rom Develpoment Page and unzip/unrar it to your computer.[/FONT]
[FONT="]2. REMOVE SIM and microSD CARDS!![/FONT]
[FONT="]3. Turn phone back on and wait until it syncs with your PC.[/FONT]
[FONT="]4. Run the Raphael_RUU.exe (or [/FONT][/SIZE]RaphaelWrapper.exe if thats included instead) [FONT="]from the Roms Folder.[/FONT]
[FONT="]5. Once phone finishes flashing and gets to the screen where it configures the stylus, HARD RESET[/FONT]
[FONT="](hold the VOLUME DOWN and ENTER (center) Buttons, press the RESET button with the stylus tip, then release the RESET button but continue to hold the VOLUME DOWN and ENTER buttons until the reset screen appears)[/FONT]
[FONT="]6. Follow onscreen instructions to set up your New Rom.[/FONT]
[FONT="]7. Once phone has gone through the customisation procedure then replace Sim and microSD Cards.[/FONT]
[FONT="]8. Turn phone back on and set up as required.[/FONT]
[FONT="]Flashing Via MicroSD Card[/FONT]
[FONT="]1. Make sure your microSD is Formatted to fat32 using a PC (you dont have to delete all files but it is safer if you do).[/FONT]
[FONT="]2. Download your prefered Rom from the Raphael Rom Develpoment Page and unzip/unrar it to your computer.[/FONT]
[FONT="]3. Goto the Roms Folder and rename the .nbh file to RAPHIMG.nbh[/FONT]
[FONT="]4. Copy the RAPHIMG.nbh file to the root of your microSD Card.[/FONT]
[FONT="]5. Plug the microSD Card into the phone.[/FONT]
[FONT="]6. Press and hold the volume down button, then press the reset button with the stylus. Release the volume down button when bootloader tricolour screen appears.[/FONT]
[FONT="]7. Follow the onscreen instructions to start flashing.[/FONT]
8. Once phone finishes flashing and says Update Complete, reset with the stylus
[FONT="]9. When it gets to the screen where it configures the stylus, HARD RESET[/FONT]
[FONT="](hold the VOLUME DOWN and ENTER (center) Buttons, press the RESET button with the stylus tip, then release the RESET button but continue to hold the VOLUME DOWN and ENTER buttons until the reset screen appears)[/FONT]
[FONT="]10. Follow onscreen instructions to set up your New Rom.[/FONT]
Click to expand...
Click to collapse
Here are flashing instructions from At0mAng:
Install Instructions
Read The Flashing Your First GSM ROM Guide
Make sure your battery is 50% charged or more
Power off & Remove SIM Card
Power back on and sync with PC
Flash ROM
Hard Reset where it ask you to align screen
Click to expand...
Click to collapse
They're not telling you to do the hard reset just for the heck of it; there's a very good reason for doing it. Not following the standard flashing instructions and then posting in the chef's thread that his ROM is buggy is just not cool.
It turned out to be the radio causing my problems not the ROM. I have never hard reset after flashing a ROM and never had a problem (and that time wasn't a problem because it was due to the radio ROM)
Not that I am asking for it, but unless there is actual proof that you need to hard reset, I don't think there is a point of doing it.
Ok the problem is back! So annoying. Does flashing the SPL hard reset the phone? I want to try going back to the stock SPL since that is the only thing it could still be, but I would rather not now if it hard resets.
Just get it over with and do a hard reset. Jeez, it's not that complicated.
roms and radios will not adjust the dpad i used the same rom u talk about and never had an issue
Hey petard, did you ever fix the issue with the D-pad ?
I have the exact same issue with my Fuze and can't figure it out.
It is a hardware issue. I had to replace it. My replacement worked fine until about 3 weeks ago where it just started to act up. I called for another replacement a couple days ago and should get it tuesday. They offered me a different phone (Epix or Incite) but I declined but told them to note it that I was offered a different phone.
In about 3 months (when my warranty ends) I will call for another replacement. If they have refurbed Touch Pro 2s by then I will ask for that, if not I will get another FUZE which will extend my warranty for 3 more months (you get 3 months or whatever was left of your original warranty, whichever is longer) and by that time they have to have refurbed Touch Pro 2s where I will then try to get one.
petard said:
It is a hardware issue. I had to replace it. My replacement worked fine until about 3 weeks ago ...
Click to expand...
Click to collapse
It figures, no easy fix. It's strange how it started to act up, mine crapped out right after a flash as well.
Good luck on aquiring the TP2 though.
I have a device that used to belong to a MSFT employee. At Microsoft you can just hand in your device and they will put a new ROM on it for you. So first thing I did when I got it is to HardSPL (OliNex 1.90) it and load up a new ROM (the one on it was a couple of builds back, and GPS didn't work etc.).
The strange thing is that ROMS seem to be 'loosing' files (as far as I can tell - apps won't open etc.) after a few days of otherwise great operation. If the device is rebooted, it's almost like a hard-reset; although the installation takes next to no time: and it gets stuck on the splash. Hard resetting the device makes it work for a few days more. The device didn't have these problems with the MSFT ROM (which I stupidly didn't backup).
I have tried a few ROMs and they all seem to have the problem:
MagicROM_23541_Sense25_Mar01
TAELROM_v4.23541_SENSE_2.5_28FEB10_LD
Timolol_5100207TH (awesome ROM)
So my current plan:
Flash stock ROM.
Flash stock SPL.
Flash stock ROM (hoping it will clear anything funny MSFT put on it).
Hard SPL.
Flash Timolol Stock-Like (seems to have the problems the soonest - 2 days max).
Does anyone have any other ideas?
Thanks guys.
I assume since you posted in the Touch Pro2/Tilt 2 section, that you own one of those devices. The roms you have mentioned below are (I believe) for a touch pro/fuze device. That could be your problem. Although, I would assume that you have one as I'm sure a rom for a different device would even flash to the device period. If you have the right rom/device combo and its a touch pro, then you should post in the thread for the roms. More details such as network and device will help the most.
Ah crap - the dangers of having too many tabs open. Can I move the thread myself?
moitoius said:
Ah crap - the dangers of having too many tabs open. Can I move the thread myself?
Click to expand...
Click to collapse
i moved it for you good luck at finding a solution
I don't think it's a hot idea to flash the stock spl. I'm not sure that it can be over-written with hard spl-you'll have to ask in the hard spl thread. If you do it, you might be stuck with the stock rom. Just try flashing the stock rom, then going to the custom one you want. That seems to work for a lot of people.
Farmer Ted said:
...Just try flashing the stock rom, then going to the custom one you want. That seems to work for a lot of people.
Click to expand...
Click to collapse
Thanks, that is significantly fewer steps . I will do that for now and report back in 2 or so days...
Small update - just flashed the latest stock Fuze ROM. Just before the customization app come up I saw that device.exe crashed... In any case, I will see what happens with the custom ROM.
You may need to reformat the memory of your phone. Having device.exe crash on a stock rom during bootup is kind of weird. I've never done it myself, but there are threads on it in the Leo forum. I wouldn't try the apps that they've put together, though. I guess you can search around for "Task 29" to find out how to do it properly.
Moved as not ROM Development.
@OP:
If the device was flashed on a regular basis, it's possible that the device flash memory is near end-of-life.
You could try running Raphael Diagnostics on it to see if that sorts it out.
HTH,
What is the lifespan (in terms of flashes) for a device like this?
Plus minus 2 days - it has been able to go as far as 5.
According to this post: http://forum.xda-developers.com/archive/index.php/t-514940.html
These are good options:
http://forum.xda-developers.com/showthread.php?t=435527
http://forum.xda-developers.com/showthread.php?t=491554
This one in particular: http://forum.xda-developers.com/showpost.php?p=3446141&postcount=16 (it applies to Rhodium, but people have had success with it).
Apparently Task 2a (equivalent of 29) is disabled on the OliNex 1.90 SPL - so I can't do a NAND format without reflashing the stock SPL (not that I would attempt that myself in any case ).
I'll run RaphaelDiagnostics and see if that comes up with anything.
Thanks for the help so far guys, I first want to see if the stock flash I did works (I smell a Wiki page).
I tried out the raphdiag-it's pretty cool. I've been having a few weird issues lately on my fuze. In particular, all of a sudden my boot-up time seems to have gotten slow (millisecond to idle thread went from 65-70 sec to 90-95 sec, and I hadn't messed with start up programs). Also, I have been having an issue with files on the main memory becoming corrupted, which has just been weird. Anyway, I ran an 'info 8' with mtty a few weeks ago, and it came up with 7 bad blocks, which seems normal. So, I ran raphdiag this morning, and ran the format nand routine. I was a little surprised, because after running it, I soft reset and the phone booted up normally like after a hard reset. I thought that it was going to wipe the entire rom memory clean, leaving only the radio, bootloader and splash screen. It didn't seem much different from a hard reset. The good news is that my startup is faster. With a setup I was using beforehand, the millisecond-to-idle-thread speed was 76 seconds, and after the format it was down to 71 seconds. However, I ran an 'info 8', and the memory analysis hadn't changed at all (same 7 bad blocks). I'm not sure if the formatting (task 29 or this) is supposed to clear that up, though.
I put both the raphdiag.nbh and a raphimg.nbh on the root of my normal 16 gb card. When you go into bootloader, it does a quick image update (takes about 2 seconds), then the screen tells you to push power for a rom update or push the action button to go into diagnostics. From there, you have maybe 4 or 5 choices. Scroll up and down with the up/down buttons, then push action. The first is a set of hardware tests, the second is something like 'run in/on', which appears to be a test scheduler. The 3d is the NAND format option, and I think the 4th and 5th options are 'calculate rom checksum' and then 'skuid', or something like that. To exit, I just soft reset, or used soft reset/vol down to go back to bootloader. After the format, I tried to flash (I think it called it re-flash), but it said there was no image present. You may need to do this on a clean card to get it to work (that is, format and then flash off the same card without swapping things out).
The diag tests are kind of cool. There's an auto mode that runs through all of them, but you have to do things to get it to work. The first is an LED test. The screen turns red, you stare at it for 5 min wondering what the hell is going on, then push the action button for the hell of it. Then the screen turns green. Push it a bunch more times, and it goes through shaded and checkered screens and whatnot, then it tells you it passed the test. There's a test for the slider, and you need to slide the keyboard in and out. The qwerty test was weird. It's configured for a touch pro (not a fuze), so I didn't know what the hell to do at first. The screen just says 'QWERTY_KBD_1', or something like that. I tried hitting the '1' button, and fn-1, and it did nothing. Then I just hit the top left button, and it said OK and prompted to hit 2. So, you just push all the keyboard buttons from left to right, top to bottom. There are also tests for the other hardware buttons, except for the 4 main buttons on the d-pad (home, back, send, end), which was kind of weird. If you think your power button or vol down button is effed, this tool will confirm/deny it for you.
Right, so the RaphDiag didn't brick your device. It's a bit risky - so I will first resort to less extreme measures - at least I know there is one success story.
I seriously wouldn't worry about it, but you may want to have a card reader available in case you need to remove raphdiag from you sd card to get a flash to work. It's possible that I didn't get the nand format to work properly, but I think I did it right, because the device definitely needed to cold boot. I was just surprised that there was still an OS there.
I'll take your word for it - BUT - in terms of gaining knowledge I am going to try the steps in the posts I found. If the NAND does need a format there is no doubt that I will land up doing it - but I will have first-hand experience.
This really needs a Wiki page once I am done; so I want to squeeze as much info out of the device as I can.
Can anyone else think of any gotcha's before I potentially brick it?
I ran the format a second time. It's really fast; it takes maybe 5 seconds. I haven't figure out how to exit from that part of the diag other than soft resetting, which leads to a cold boot. I'm surprised it's so fast. A hard reset takes about 30 seconds. I guess that it's working properly.
Farmer Ted said:
I ran the format a second time.
Click to expand...
Click to collapse
You are either very brave or very rich . Right, so here is hoping I have to go the final resort route - nothing yet though.
Hi All,
Disclaimer: I have scoured the internet and this forum looking for others who found solutions to my problem, and I've found several similar cases, but none quite like mine. I've done all I can think of short of sacrificing lambs on giant LG logos painted on the ground, so I'm resorting to posting. Forgive me if I missed something obvious - it's entirely possible since I'm still a newbie...
With that said, here's my issue:
I downloaded a CM7 nightly build and successfully flashed it on my p999 this morning using ROM manager. I went back to stock 2.2.2 afterward. Earlier this evening, I decided to flash CM7 again from the ClockWork recovery mode, but this time I didn't do a wipe (yes, I realize I'm a massive idiot). After rebooting, I got stuck in the standard boot loop with the cyan android alien doing its skateboard thing. I tried booting to recovery mode, but holding down power+down volume just brought up the android alien and the white box with a loading bar for a short time before rebooting. Standard suggestions involved (reasonably so) performing a hard reset. Though the phone won't boot straight into recovery mode, pressing the home button while the loading bar is visible brings up text suggesting the data, cache, etc of the phone are being formatted. After this process completes, I'm left at the system recovery utility with blue text and I can navigate the first menu, but the power button (nor any of the others for that matter) doesn't actually select any of the options. After removing the battery to reboot the phone, it still gets stuck in the boot loop and occasionally goes blank after failing to get to the launcher a few times.
I've also tried using the adb approach, but no device is detected on the linux machine despite being able to access some form of the bootloader.
Have I legitimately bricked my phone, or is there still something I haven't tried? Thanks a million for any help.
You didn't search very long did you? Go to the development section and find the thread on the one click nvflash tool, read the OP in that thread and you should be good to go.
G2X CM7
unusualparadigm said:
Disclaimer: I have scoured the internet and this forum looking for others who found solutions to my problem, and I've found several similar cases, but none quite like mine.
Click to expand...
Click to collapse
This forum is saturated with problems and cases exactly like yours, almost word for word.
G2X CM7
I found plenty involving a boot loop with CM7, but all of them were able to get to recovery mode just fine. Despite what you might think, I spent several hours trying to find something that worked. Thanks for the help. I'll see if nvflash helps.
They were able to get into recovery mode because they flashed it correctly using nvflash. Pardon my tone. I guess it sounds rude. Its been a long day and I'm tired. Anyway, nvflash recovery and you'll have no issues getting stuck like this.
G2X CM7
No problem. =) When trying to go the adb route, I saw the volume up+down trick to get the device to be detected, but it wasn't working on the linux or mac (lion - it's been having issues detects various external devices anyway) machines that I was using. After checking out the nvflash thread, it seems maybe a windows machine is necessary. Getting bootcamp going. Here's to hoping it'll work. Thanks a ton again for the suggestion - this is exactly what I was looking for (wanted a way to get CWM on the phone).
Make sure to check out this thread if you haven't already. Its a one click tool for nvflash.
http://forum.xda-developers.com/showthread.php?t=1056847
G2X CM7
Yay!
Thanks a ton! In retrospect, it seems my problem was right along the lines of multiple others', but I just didn't realize it since a few details on the specifics here and there seemed different. Sorry for wasting the board space, but thanks for your patience and help. I can't emphasize how much I appreciate it.
Hello,
I am posting in this forum for a few reasons.
First of all, I rooted my phone the day I bought it and took it home. I originally rooted it with a simple one-click method from a webpage I randomly found online.
Unfortunately, I do not remember the name of the hack, and I'm beginning to think that it has permanently affected the boot for my phone. After installing the hack, I found the CynoagenMod (or however it is spelled) custom ROM. I took some time into researching more about custom ROMs and installing with advanced settings, etc.
After I did my research, I found it best to flash with the new ROM and have had trouble with my boot since.
I did everything step by step from the website, and ran everything to the best of my abilities. The problem I am having now is that I can not access the HBoot menu.
In fact, every time I restart or shut off my phone, the screen goes black and will not respond to me holding down the recovery mode buttons. It stays pitch black and even battery resetting does nothing.
It will randomly turn on, vibrating for about a minute or two straight with the HTC splash screen, and then boot into my phone with the current ROM.
It seems strange that this is going on, and I have been searching all over the internet for weeks now trying to figure out what's wrong. I have reinstalled the stock RUU for my Inspire multiple times to no avail. It still sits at a black screen and will randomly boot into the splash whenever it deems to do so.
Is there anyone with any suggestions or advanced technical knowledge that could lead me to a solution? It is most unfortunate because I can't access for viewing s-on, s-off. I'm really debating whether to take the phone back to the rep and replace it. I'm just afraid they will discover the security off and tell me to suck a ****.
Thanks.
Run this nice little tool to factory reset, s-on your device
http://forum.xda-developers.com/showthread.php?t=1208507
Then reroot with the Hack Kit here. Read the "effen manual"
http://forum.xda-developers.com/showthread.php?t=952352
Thanks for the reply.
But here's my problem:
I can't access the HBoot menu in order to flash or install any type of file.
I've been using the terminal on my Mac to do most of my editing, and now I've ran in to a new problem: whenever I try to move files to my sd root, it says that the card is read only and therefore no files can be transferred to it.
I use the command ./adb push PD98IMG.zip /sdcard/
This is where I get the error.
Also, it takes my phone literally 5 or 6 minutes to boot into the splash screen after I use the command ./adb reboot bootloader/recovery (both of which I have tried).
I'm beginning to get quite frustrated, as I'm sure you can understand. I've also attempted to rewrite all of the necessary root programs onto the device in hope that the bootloader and recovery options will be accessible.
Do you have a solution for the write problem I am getting from my device?
Thanks.
Also, is there a way to go about doing this procedure straight from the Terminal since I can't run HBoot and recovery directly from my phone?
I have sucessfully restored s-on on my previous inspire so I can rma it for a signal issue I was having.
So I consider myself savy enough on this task. I rooted that inspire using a method available on here and not some random site. Doing that, u accept the possiblility that you may not get support on xda for using a root method that was not posted here. However, I do remember reading somewhere on here that certain inspires will go to a black screen at somewhere during the rooting process. My advice is to search the inspire threads for this topic, using keywords black screen, and see if this can provide a solution for you.
Sent from my HTC Inspire 4G using XDA App
Thanks soldier, but I've already searched through every black screen forum topic on this site for the inspire, all of which require reboot to HBoot, which I can not access from my phone without terminal access.
It seems like my phone is permanently soft bricked or something, or maybe the key commands don't do as they are supposed to. I can never get into the HBoot menu or recovery by holding down vol. - and the power button.
All it does is boots into the splash screen after about five minutes or son, and once the splash screen comes up, the phone vibrates for about 2 minutes straight.
During this time, my phone is not recognized by adp until after the phone stops vibrating.
I can't seem to find any forums ANYWHERE that propose a solution to this problem, let alone anyone that has the same issue as me.
Yeah that sux man. Well I would say, if you are within your warranty exchange, I would go that route first. Worst thing they can say is no. Although I still have yet to find a story about how someone was denied a warranty exchange for a phone that does not have physical damage. The next route is to suck it up and pay the deductible if you have insurance on it. (I always recommend insurance on any modern touchscreen smartphone) If that is not an option, then start saving up for a new phone, and lesson learned.
Ya, that seems like the only available option at the moment since my phone can't access HBoot even though I rewrote the root files to the device.
I just bought the phone this weekend, so I'm thinking of hard bricking the phone in case they decide to do an on-the-spot check. Hopefully they'll believe some bull**** story I can come up with and just give me a replacement.
Would any of you still recommend rooting again with a new phone? And what would be the best way to do so without the consequence of a soft or hard brick?
I'm just thinking of rooting and keeping the original stock OS on the device instead of running a custom ROM. That's what seems to have effed my phone.
All I really wanted to do was cut all the crappy useless programs and services out of the original Google Apps package with a fresh install to get the most out of my hardware.
FYI...if you haven't figured it by now, xda is the BEST site there is for android hacking/modding. This website IS the centralized location for all android developers/modders. Sure there are plenty of other android community sites out there, but this is the direct centralized source for all android hacking/modding.
My suggestion is to go ahead and root the next inspire you get using the hack kit in the development section. That is a long time proven and supported rooting method for the inspire. As far as roms go, from what you are saying, i would recommend you install a custom rom that is based on stock. (ex. Android Revolution) It was not the custom rom that effed up your phone, it was the questionable rooting method that did. Custom roms, by default, are superior to true stock roms, because they are modded, tweaked, and optimized far beyond the stock rom.
Awesome, I appreciate the information.
I'll keep that in mind. So which exact ROM would you suggest for my Inspire that's completely like Gingerbread?
I wasn't too fond of the CyanogenMod ROM because the GUI was a little sketchy. I like having a professional looking GUI, and I love the Gingerbread screens and menus.
Oh, one more thing. I had some success a little while ago getting into the HBoot menu from the terminal. Now I'm having a new issue:
I get into the menu at which the phone freezes and I can not use the arrow keys or power button to make a selection. Any tips?
I also believe that it is in fastboot, since it says fastboot at the top and has the Androids on the bottom skateboarding. Is this an issue? And am I screwed because I can't access the OS to turn the option off?
When you see the fastboot at the top of the screen and the androids skating at the bottom, that is perfectly normal. That is the pre screen before actually going into the bootloader. If your keys work, u press the volume down button to select which option you want, which will highlight in blue. The first option is the bootloader, so if you press the power button, it will load into the bootloader. The bootloader looks exactly the same as this screen, but with different options. This screen will show hboot at the top and have the options of fastboot, recovery, factory reset, simlock, and image crc. I have never heard of the keys not working at this point, so i couldn't help you there. Search around the forums if you haven't already.
If you want to compare this to something more familiar, think of these two screens as your motherboard bios to your PC. (What you see when your pc boots up, before it loads the OS, windows, mac, etc) On a pc, you can install any OS you want, like on the inspire, you can install any custom rom you want. But the motherboard bios is the highest level of permanent software that is directly written to the motherboard itself, like the bootloader/hboot is on the inspire. When rooting, you are essentially altering the motherboard bios on the inspire. When you install a custom rom, you are just installing an OS on the inspire.
There are plenty of custom ROMS that are based off of stock in the development section. I use and like Android Revolution. But when choosing custom roms, its always a matter of preference, and what works best for you.
digitalism said:
Thanks for the reply.
But here's my problem:
I can't access the HBoot menu in order to flash or install any type of file.
I've been using the terminal on my Mac to do most of my editing, and now I've ran in to a new problem: whenever I try to move files to my sd root, it says that the card is read only and therefore no files can be transferred to it.
I use the command ./adb push PD98IMG.zip /sdcard/
This is where I get the error.
Also, it takes my phone literally 5 or 6 minutes to boot into the splash screen after I use the command ./adb reboot bootloader/recovery (both of which I have tried).
I'm beginning to get quite frustrated, as I'm sure you can understand. I've also attempted to rewrite all of the necessary root programs onto the device in hope that the bootloader and recovery options will be accessible.
Do you have a solution for the write problem I am getting from my device?
Thanks.
Click to expand...
Click to collapse
It sounds like you may have the bad combination of a newer Inspire and the older ENG hboot. This is a problem dealt with commonly on the Aria/Inspire IRC channel. If you want to jump in, we can probably get you straightened out.
http://webchat.freenode.net/?channels=#liberatedAria
Awesome.
I am a little upset that I can't choose an action from the boot menu with the keys on the phone.
It also seems that the only way I can completely get into the boot menu is through the terminal after which I run ./fastboot-mac
After I put in this action, the menu will begin looking for the PD98IMG.zip file, and only goes on to say that there is no file, when there actually is one.
I just wish I could do all of this straight from the phone since I'm not well versed on terminal and commands for running programs to their full ability.
I wish I could figure out a way to the write permission on my sdcard so I could reinstall the .zip file for the bootloader to find.
digitalism said:
Awesome.
I am a little upset that I can't choose an action from the boot menu with the keys on the phone.
It also seems that the only way I can completely get into the boot menu is through the terminal after which I run ./fastboot-mac
After I put in this action, the menu will begin looking for the PD98IMG.zip file, and only goes on to say that there is no file, when there actually is one.
I just wish I could do all of this straight from the phone since I'm not well versed on terminal and commands for running programs to their full ability.
I wish I could figure out a way to the write permission on my sdcard so I could reinstall the .zip file for the bootloader to find.
Click to expand...
Click to collapse
You will not be able to use the volume rocker to select options if you have a PD98IMG.zip on your SD card.
Try booting into hboot with the SD card removed. That should let you move around the menu.
Sent from my Inspire 4G using the power of the dark side
Thanks for the heads up!
I can move the menus now.
Seems like all is going well now...
Just a matter of time.
digitalism said:
Thanks for the heads up!
I can move the menus now.
Seems like all is going well now...
Just a matter of time.
Click to expand...
Click to collapse
It's good to hear you're moving forward. Let us know how it comes out.
Sent from my Inspire 4G using the power of the dark side
Hi all
Today I was trying to get my nexus s onto the official ota ICS update by flashing it manually, following guides other people had had success with.
I was on the cm9 ics beta, so I had to flash the full rom of 2.3.6.
This worked completely, however I think the ota update file I downloaded was corrupted, as flashing didn't work, it said something about signature verification failed. So I redownloaded it, from the same link, and the new one was bigger. I tried that, and the same error. I tried wiping data/factory reset etc, and I accidentally started to flash a cm7 rom I had on my phone.
I stupidly did a battery pull as it started to flash (the back cover was off already), and now my touchscreen doesn't work. I was able to successfully flash other roms including the 2.3.6 I downloaded, and I couldn't do the first setup procedure (touch the android to begin). I tried cleaning the screen very carefully with 90% isopropyl alcohol, the same stuff I use to replace thermal paste on cpus.
It still doesn't work. I am hoping it is a software issue that can be fixed otherwise I have to return it.
Someone please help
I have used the search function and none of the solutions I found worked.
(UPDATE) I rebooted again, and when the phone booted into cm7, the "internet" icon(the globe picture) on the bottom left of the dock was in the "pressed" state(orange). It was like the phone thought I was holding my finger on it, which suggested a hardware issue. I cleaned it again and nothing changed. Then I held the phone in the landscape position. When the screen rotated, the button stayed pressed. So the phone doesn't think "this part of the screen is being pressed" it thinks "this internet icon" is being pressed. Rotating the phone again and again didn't change anything, the icon was still pressed in.
Defiantly a software issue. I would try to unroot and reroot. Then if it is still not working, try to format the SD card. You may want to considering buying a USB to micro USB adapter to help you, considering then u could plug in a mouse. I have one just in case I need it.
Thank me if any of this helped
Also try and keep this updated with new info. If I can't help, maybe someone else can.
Sent from my XT862 using XDA App
Thanks techno-update, I will try that. I haven't "unrooted" before, Is that just typing fastboot oem lock or whatever it is instead of fastboot oem unlock?
Also, I found a youtube video with the EXACT same problem.
v=zpfE15Xw_os&feature=related
Skip to 3:15, and you will see when he opens the power menu, the phone thinks he is pressing on one of the options, but he isn't.
I will let you know how unrooting and rerooting goes.
Thanks
(UPDATE)
I tried unrooting and then rooting again. It still does the same thing.
Even in cwr I can't use the capacitive buttons to navigate menus, does that rule out software problems? I am really hoping its just a software problem :/
I need my phone for an outing tonight (im in australia, its 5pm now) and I would appreciate it if some genius could solve this
I am usually the "go to fix it IT guy" in my area, but I can't figure this one out. I have tried formatting the phone, reflashing the mod etc.
Is there some more aggressive COMPLETE wipe or something that fully wipes the phone?
UPDATE 2
Guys please help,
I just flashed zulugen mod, as it has the trinity kernel, I don't know much about android os, but I hoped that that might replace the touchscreen driver or something. The rom flashed correctly, but touchscreen and the capacitive buttons still don't work. Please help
Guys, is there some sort of system partition where the touchscreen drivers are kept or something? And when I pulled the battery as it was flashing cm7, it corrupted these?
Is there some way to fix this?
bump
bump. I need help with this urgently. Is it possible the connections for the screen came loose inside? I would crack it open but don't have screwdrivers for the 3 smaller screws on the last layer of plastic before the pc board.