Hello:
I have searched to forums, but did not find a thread that addressed my specific problem. I'm hoping that someone here might be able to help...
I have a Fuze running the EnergyRom August 1st build. I have not had any problems to date except for the occasional lag and the battery drain. I've never had to reset or anything.
Last night the phone was working fine, I set the alarm, plugged it in and went to sleep. At 2:30 this morning I woke up to my voicemail message on the phone. The phone had somehow called my voicemail. I hit the end key - no problem - but after that my touch screen would not function.
At first I thought the screen was broken somehow. (There are no cracks or spots; it hadn't been dropped. I did not get the "broken screen" or any black/white "noise" that others referred to in their posts.)
I did a soft reset, no result.
Hard reset, no result.
Then I realized that the screen actually works, but so slowly that it is almost imperceptable.
Right now I am on the align screen part of the boot-up. It is taking approximately 8-10 minutes for the phone to register each touch of the target and move to the next.
I assume that eventually it will boot, but my questions are:
Where do I go from there?
Should I just reflash?
What the heck happened???
Any and all advice would be appreciated. Thank you!
Flash back to stock ROM, then reflash a custom one.
Your issue will be resolved
Hi, Bruce. Thanks for responding.
I tried what you suggested, but still no luck. I flashed back to the HTC OEM ROM, then to EnergyROM 'Genesis' (SYS 23016). Now I am stuck on the "tap the screen to set up your Windows phone" screen.
No response at all when I tap the screen.
Any thoughts?
There's an empty text file you can put on your sd card that will let you skip alignment, but I don't remember what you need to name it. Try searching for skip alignment in this forum. Also, there's another recent thread in this forum where 3-4 other posters had sudden screen problems with that rom or one in the series. They may have had black screens. The phones still worked, like with MyMobiler, but the phones were messed up. Search for that thread to see if there's any help. This may be return time, I'm afraid.
When you flashed back to stock, did you see the same issues or only on Energy ROM?
I would say try another ROM.
As Ted said, many users had issues like this on his ROMs.
I looked it up, and the file you need is called "welcome.not" (no quotes). Just rename a blank text file that and put it on the root of your storage card.
Here's another thread on screen issues with that rom.
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.
People, I've tried a bunch of assemblies and options for your phone after the display is changed to the Chinese and found that only 3 boot penguin display and inscriptions at boot true test, with those two idit load equally, and one with the other inscriptions but also hangs. These feeders: 1) polaimg-panel3-240x320-2.6.32-froyo-06-09-10_22 2) polaimg-panel3-240x320-2.6.32-froyo-09-09-10_21 3) polaimg-panel3- 240x320-2.6.32-froyo-27-08-10_23.
All three normally pick up the screen but the writing bug usb_vsync.
Founded on the Internet has the very first assembly androyda, who works in the demo rezhime.Reshil try to install it and wonder, android has started without any problems.
Here is a link to the installation package that will install this demo on your phone: hxtps://rapidshare.com/#!download|304l34|123389441|RUU_Polaris_Android_DEMO_v1_0.exe|72394|R~EC5F7C5EBDDD628BF8BFF91F71607033|0|0
Those who say they say android does not support Chinese screens, just a lie or do not know. At this assembly it is clear that androyd runs perfectly, and on the phones with a Chinese screen.
Most likely, DZO, or what the other developer of the kernel is not corrected. Suggest to write a petition to save money and to develop a normal boot. Let's say it can do the same DZO or what the other developer. I do not think it would be very difficult and time consuming. Who can help me in this, please come forward!
But there's more, I decided to try to run through the HARET andriod 1.5 on the same firmware WM and you think, android has started well!!
At the moment, try to build a working version of Ecler, I do not know whether I can or not but the fact that at least 1.5 works already happy!
That it happened. All the same I managed to run Android on my devayse 2.1-2.2. Of course there are problemma, and a large - is not responsible for nozhatie touch screen, but the fact that he obsalyutno normally displays everything on the screen is great plshyusom and proves once again that all the matter in the loader, which local craftsmen or they can not fix! !
Below we will explain how to start. If you do not get something right the first time, try again, I got yed)
1) Download the assembly android_by_polyrhythmic-beta3.zip (Look on the internet, I think problemma not be found)
2) Download the assembly polymod.rar.
3) Unpack android_by_polyrhythmic-beta3.zip and copy the folder on the SD android.
In the folder are 2 files android default and default-s, files and zImage-15-12-09 and zImage3. The file default by one run android in Haret changing the panel on 1,2,3. Each time you start when you have to wait for the LED zamegaet either blue, green or yellow, and goes off the screen. This would mean that the android booted and shut off the screen. After clicking on a retreat or off you will see a white screen.
After running all three panels so turn off your phone zaydmite to stick and move to folder android Fail of the default-polaris zborki polymod and change it to default. Replace the old Fail them, and then rename the zImage-15-12-09 in just a zImage. Now run the android. Wait until you have a light starts blinking LED goes off and the screen. As it happens, click on the rebound a few times. You will see a line of code and then the welcome screen android. Since the touch screen is not working I could not go further, but pressing the buttons can be issued to the soglashatsya message.
Here vprintsype all.
Try it. The point I was told, then I welcome your ideas and results!
A few years back I purchased a Flytouch II / Superpad. Installed several custom roms and had no issues. It sat in my parts box for a while and I figured I drag it out and see what I could use it for.
Initially it booted fine (running Tim6...I think) once it was up and running it started lagging and would not respond (Screen got too hot and it stopped seeing my touches)
One of the icons on the screen was a shutdown script pre-loaded. Apparently it had pressed this, the script popped up and I tried to hit close before it shutdown, The script closed and after a little more playing I shut it off by holding the power button down, then sliding the power off slider that came up.
The next day I went to power it up and it just freezes on the android logo screen. No bootanimation, nothing.
Since I'm not shy about taking stuff apart it carefully took it apart and removed the internal sd card (4gb) and made a backup of it using dd. I then loaded an sdcard v4 image I found online, it still just hangs at the green android screen.
Also tried several "brick fixes" here on xda.
If I boot it without an sdcard it says "No Card in Machine!!!" so I think the systems is ok hardware wise.
Any ideas of other steps to take?
Got it figured out. Feel kind of silly.
Just needed to format both cards to fat32 and add the two files from tim6a back to the external card. It booted, reflashed and away it went.
Phew, thought I was going to have to rig up a touchscreen for my computer
Hello All,
This is my first post on this forum. I am not a technology idiot, but as far as Android goes "under the hood" I'm a relative neophyte.
I purchased an LG Optimus V not long after they were introduced. The device was never used for mobile phone service as I already had a phone and was replacing a Palm Zire as Palm OS was reaching its end of life. It came with Froyo on it and after I had it for about a year I rooted the device.
It has since been replaced and had been being used as an MP3 player (but it was handy to be able to take a quick peek at e-mail, etc.) and hummed along for several years doing that. Then one day, when I went to turn it on, it would not boot up. When the device is off and plugged in to the charger, the battery charging state (battery with flashing bars showing how charged until at 100%, then they stay solid) behaves as it always has. When I try to boot up, I get the LG icon splash screen followed by the "big" Virgin Mobile splash screen with music, followed by the black screen with the small Virgin Mobile icon in the center and there it sits. It will stay on this screen until the battery runs out or you pop it out.
Since then I have tried getting into recovery using the hold HOME plus Volume Down plus Power Button technique and I can get in to the stock recovery. I have tried wiping the cache partition (which shows it worked) and a wipe data/factory reset (which claims it worked) but when I try to reboot I get precisely the same behavior as described in the last paragraph.
So, I thought I might try loading a custom ROM, but any attempt to do that fails saying that there is no such file or directory but also adds that signature verification failed and installation is aborted.
I gather I need to load a custom recovery first, but have no idea how to do that with the phone in its current state. I can still bring up the stock recovery mode, though.
This is really a "can I do this" sort of project rather than driven by any real need. If anyone has any suggestions as to how to proceed, or knows that proceeding is actually not possible, I'd appreciate the input.
Thanks,
Brian
Just one additional data point. I've now got Android Studio and adb on my machine and have installed the drivers for the LG Optimus V.
When I run "adb devices" it comes back with the correct MEID for the OV and reports that it's offline.
After a great deal more time and effort I finally unbricked this device using the step-by-step instructions, including an RAR file that contains all the needed items, on androidforums.com in a thread entitled, [GUIDE] Unbrick/Upgrade Optimus V [EASY] [KDZ]. I would have posted the link, but apparently my post count is not yet high enough to allow that.