I've got a problem with my XDA Mini S. It's been sitting in a box in my shed for about a year, before I got it out yesterday to have a play around with it, and possibly try some software I found on it.
I put my sim card in, plugged it in to charge, and turned it on. It worked absolutely fine.
I haven't done anything with it yet, but I've turned it on now, and the colours are messed up on the screen. For example there is a red hue over the today screen, and on certain screens (like in bootloader mode) the colours appear to be inverted (I will post pictures later if needed).
I've tried reformatting the device, but this has not fixed the problem. I thought I would try reflashing the rom on it. I used to have the original o2 rom on my old laptop, but lost that when I had to reload windows.
I downloaded the original rom from here, along with the Rom Update Utility, and attempted to reflash it. It gets as far as 'verifying the information on your PDA phone', then crashes with the error: Rom update utility MFC application has stopped working.
I'm running windows vista on my laptop, and read that the RUU won't work until the drivers are updated. Following the instructions on mrvanx.org, I have downloaded the driver for vista and installed it, but i'm still getting the problem when I try and reflash the device.
I've also tried running the RUU in compatibility mode for XP as it worked fine on my old laptop which was running xp, but it still crashes, every time.
I'm beginning to wonder if reflashing it will even work though, since the colours are messed up in bootloader mode as well, which leads me to think it may be a hardware problem.
I know next to nothing about repairing these though, and probably wouldn't bother if it's a hardware problem, but until I can reflash the firmware, I won't know whether this is a case.
I'll get the photo's of what the screen is like uploaded to my server later on, and post the links here, so you can see what the problem is.
Show photos and specific error when reflashing arrangement.
sorry my english
photo's are in this thread: http://forum.xda-developers.com/showthread.php?t=384800
The original thread double posted for some reason.
Related
I've an XDA/Wallaby here (PW10A1) that I've tried upgrading it to various newer versions of Windows Mobile Edition. None of them seem to work however - the XDA always gets as far as the splash screen (the screen on which the ROM versions are printed) and then freezes. I've left it like that for days to see if anything further happens and it doesn't. Only restoring the original image from an SD card fixes the device.
Has anyone else come across this? Am I missing some crucial part of the upgrade process? Or is my XDA just fubarred?
my reply would work for you too
http://forum.xda-developers.com/viewtopic.php?t=23882
It doesn't really - I haven't had any problems getting the ROM up there, it's getting the XDA to boot afterwards that's the problem!
I've just tried applying this upgrade and the same thing happens. But this time I've noticed that the O2 graphic on the splash screen is slightly corrupted. Does this help at all?
I have the phone for almost an year without having any problems at all.
Approximately 1 month ago i installed a theme (from this forum) and it worked perfectly untill i decided to change it with another one (also taken from the this forum).After the restart the main screen froze and the touch flo was not active.I could only scroll the menu and acces it.
Also, i could't change the wallpaper.
After this, i tried a hard reset and apparently everything came back to normal EXCEPT: the internet connection didn't work at all no matter the settings i've made and from time to time a "dont send" error popped up. The error was : AudioManager_eng.exe.
After this, i updated my rom (from the htc official website) and had another hard reset and still NOTHING.
In fact i noticed other errors as well.When i tried to acces the mussic tab - audioManager_eng.exe error appeared, when i open wm another wm error appeared.
PS: i also had the storage card formated hopping to solve the audiomanager_eng.exe error (no result)
What should i do now? I feel like i tried everything ...
PS2: i am sorry for the possible mistakes
english is not my mother tongue. Also please try explainig a sollution in simple terms so i can understand step by step what i am supposed to do
thanks
please help....
Have you tried a hard reset to restore everything to default? Or removing theme which started all problems? When you flashed a new rom you may have added more problems, especially if you didn't follow this guide. Depending on what rom you flashed your SPL may not match causing incompatibilities. Does the screen look distorted when you start/boot up phone? Does this discolourization go away when you press power on/off? If so you have a mismatching SPL. Read and follow the dummies guide to see if this fixes some of your issues.
I didnt flash the rom.I had an upgrade .This one: http://www.htc.com/europe/SupportDownload.aspx?p_id=179&cat=2&dl_id=533
And YES, i also had not one hard reset but 4 or so.Can that harm the phone?
Hey all, been poking around the forums and trying out various WM and Android ROMS and they all seem to work beautifully, kudos to the devs.
I seem to be running into a bit of a problem though.
My phone is an MP6900 (Vogue 100) from Bell. And while the roms work great, the second my phone goes into standby mode (when not attached to my comp) the phone resets.
I have tried four different roms, two android and two WM and the problem persists.
Also hard resets, battery removal etc etc to no avail.
I also tried to roll back the radio as that got updated when I went to my stock rom previously.
And to boot I can't seem to flash back to the stock ROM anymore, while I was able to even just yesterday. I get Error 262, for whatever reason.
I was wondering if anyone else has run into this issue and could point me in the right direction.
And I did a search on the forum (pre-registration) but couldn't find anything, sorry if this has been brought up before.
Again, great work on all of the ROMs! I had no idea phones had come this far. (Sad to say but true lol)
JustinHTC said:
Hey all, been poking around the forums and trying out various WM and Android ROMS and they all seem to work beautifully, kudos to the devs.
I seem to be running into a bit of a problem though.
My phone is an MP6900 (Vogue 100) from Bell. And while the roms work great, the second my phone goes into standby mode (when not attached to my comp) the phone resets.
I have tried four different roms, two android and two WM and the problem persists.
Also hard resets, battery removal etc etc to no avail.
I also tried to roll back the radio as that got updated when I went to my stock rom previously.
And to boot I can't seem to flash back to the stock ROM anymore, while I was able to even just yesterday. I get Error 262, for whatever reason.
I was wondering if anyone else has run into this issue and could point me in the right direction.
And I did a search on the forum (pre-registration) but couldn't find anything, sorry if this has been brought up before.
Again, great work on all of the ROMs! I had no idea phones had come this far. (Sad to say but true lol)
Click to expand...
Click to collapse
Sounds like a dying battery to me.
It worked fine in the original Windows though so that's why I am a bit baffled.
what happens if you put your device in bootloader and try to flash to stock? Error 262 is a connection error. basically happens whenever some event interrupts the flashing process (a dead battery will cause this). If you haven't yet, try to flash to stock via the method in this post (bootloader and then flash)
Tried that, didn't work. Just gets to 31% and pops 262 no matter how I try to do it.
The odd thing is though that I can flash any other ROM just fine.
Would reformatting the SD card work?
Figured it out. I used the 0.41 ROM to unlock the phone which was causing the issues. I reflashed with the 2.3.1 and everything works fine.
JustinHTC said:
Figured it out. I used the 0.41 ROM to unlock the phone which was causing the issues. I reflashed with the 2.3.1 and everything works fine.
Click to expand...
Click to collapse
0.41 was reportedly having tons of issues, you should have started from there
Glad you got it working.
During an update, (PASSIMG.zip) in hboot I selected yes (to install) then about a second later, my screen
turned black and now, the only thing I can do is to boot in the installed stock rom (FRG33).
My english is not perfect, i'm sorry for that.
1. I Removed my battery after a while. (about 10 minutes)
2. Inserted the battery back in his place
3. Power down + vol down and I'm stock, I can navigate in
the menu but I can't see anything...
Anyone know how I can get my screen back ? OLED vs SLCD ?
Note: I can boot in my rom, the rom is unrooted, my phone is unlocked.
(And yes, I tried to flash recovery and another rom without success. And I can't
find a way to flash hboot again (bad signature)
I'm using the last version of hboot and radio.
If anyone have an idea of how I can fix this, this will be really appreciated.
Thanks.
I'm starting to think than my /dev/mtd/mtd0 is screwed up.
Anyone know where I can get/or generate a image of a normal mtd0 ?
At the moment I'm running debian sid dand SuperOneClick seem to freeze
after trying to chmod rageagainstthecage or psneu..
Note: Yes my screen work when the boot is completed. (but not in hboot/recovery)
bad spl ?
fblodroid
Ok, sorry for the noise, I was able to perform an update via 766a101ae02c.signed-passion-ota-60505.766a101a.zip (renamed to update.zip) and I powered off my phone.
Removed the battery to be sure there is no power at all.
and using some screenshot found on the web.
I was able to perform the update (blindly, this word exist ?) and the phone rebooted
and asked me if I want to update again (google update) I selected yes, the phone rebooted
and, VOILA, I can see again the crappy X logo with an open lock at the bottom.
Thanks again (ok for nothing, but if than can help some people...)
Yes, shame on my english again.
fblodroid
My guess is that you have an SLCD Nexus One, and the passimg installed the .33 HBOOT which doesn't work for them.
I had the same problem when flashing the MIUI-AU rom, screen went black,removed battery and replaced but the phone was dead,I was already thinking which phone to buy then when I connected the N1 to my laptop miraculously the X logo appeared and the rom launched ok
At the moment my phone is working again but I'm still having a camera issue.
About a 1 1/2 month ago I experienced this problem, no flash, no camera, just
a black screen when I try to run anything than use the camera.
Then a day, I was walking on the street and I checked to see if the flashlight was
working and obscured magic occured, the flash was working again but not the camera,
I wiped my phone again, repartitionned my SD card and installed a new rom and the
camera was back to normal.
Now, about a month later, (the problem started yesterday) i'm having the same issue.
I'm persuaded than this problem is related to a firmware problem, something related to
my /dev/mtd/mtd0 (hboot, perpaps ?) I don't know exactly where the camera firmware
is writed in the phone memory (nand)
I wiped and flashed again and again a lot of rom last night and today and the problem
still exist.
No camera/flash at all.
I'm thinking about returning the phone for warranty issue but like I said before, the
phone is unlocked... perpaps I will try to black the screen again and send the phone for
warranty... this way they cannot see (without fastboot) if the phone is locked or not.
If anyone have an idea of what I can do... a rom to recommend ?
Today I tryed to revert hboot without success...
EDIT: At the moment I'm running a rooted rom based on FRG83G.
fblodroid...
Related to my camera/flash problem:
Hum, I think I found the problem, this is hardware related, something seem to be
badly connected in the phone, I tryed too apply some force on the right border of the
phone with the flashlight ON (I previously looked on the web to see where the "contacts/plugs"
are located on the pcb (teardown pictures) and after applying some pressure, the light came ON
and now I can open and stop the "flashlight" mode.
teardown on the way ? I'm thinking about it... but i'll try to flash another rom again to see
if my camera is back.. (like in the past)
EDIT: No camera for the moment and the flashlight app light on the LED only if I select
the option "High Brightnes", ON/OFF are working with this option selected.
fblodroid
FIXED
After a complete teardown of my phone, and a lots of cigarettes..
I found two cables not correctly connected to her pin.
I made a picture, hum, an ugly picture of which cables.
http://img121.imageshack.us/i/icedqlubgg4zzbv2huge.jpg/ (in the red circles, the two pink dots)
And yep, now my camera/flash are working perfectly.
NOTE: the phone is not easily to dismantle, this is at your risk and peril. (time: about ~25 min)
Thanks again and please, ignore my english. I'm thinking about starting a thread
related to this problem. Should I ?
fblodroid
Hi, I have a HTC Desire GSM PVT4 (HTC__203), with the exact same issue as what is described in the original post. When I boot in hboot or recovery the screen is completely black. When I boot in the normal rom the screen works fine. I reflashed a number of RUU's successfully, but the problem remains.
The misc partition is not part of the RUU images, and I did re-flash the misc partition in an attempt to downgrade. Any idea where I can get an image for the misc partition for my device, or where I can generate one?
Thanks,
Hans
fblodroid said:
After a complete teardown of my phone, and a lots of cigarettes..
I found two cables not correctly connected to her pin.
I made a picture, hum, an ugly picture of which cables.
/link/
And yep, now my camera/flash are working perfectly.
NOTE: the phone is not easily to dismantle, this is at your risk and peril. (time: about ~25 min)
Thanks again and please, ignore my english. I'm thinking about starting a thread
related to this problem. Should I ?
fblodroid
Click to expand...
Click to collapse
Hey. I have the same issue you had with the camera, black screen and forced to close when running it. My flashlight works perfectly thoug.
I tried wiping and reflashing diferent ROMs, stock and Cyanogen with no luck. I also followed your lead and disassembled the phone to check all the connectors but the problem persists.
Any idea for me to try? Thanks for your posts anyway.
soylapinta said:
Hey. I have the same issue you had with the camera, black screen and forced to close when running it. My flashlight works perfectly thoug.
I tried wiping and reflashing diferent ROMs, stock and Cyanogen with no luck. I also followed your lead and disassembled the phone to check all the connectors but the problem persists.
Any idea for me to try? Thanks for your posts anyway.
Click to expand...
Click to collapse
Did you managed to fix it ? Be sure to check all the plugs, at best unplug everythings
and disassemble the phone entirely.
Mine is still working perfectly after two years.
fb
Yesterday I needed to take a picture and used my Galaxy S. for it. After that I connected my phone to my laptop USB port and got an unknown device error. Assuming it was a driver problem I re-installed them keeping the same error.
I also got telephony problems before, after some minutes calling the other side couldn't hear me anymore and I needed to put the call on wait and back to continue the call.
Both problems together made me decide to update my Darky 10.1 Extreme edition to the latest 10.2 Extreme edition. I took my sd card out and copied the darky 10.2 zip to it using my laptop. Put it back in and used Astro filemanager to copy it to the internal sd. Because I can't use the usb port this was the only way.
Rebooted to recovery and flashed 10.2. After reboot the screen stayed at the boot screen with green Darky text for half an hour without doing anything. No vibrate or anything. I did read some info about 10.2 before i downloaded it but missed the lagfix point. Tried to get into recovery and luckily that worked. Turned on the lagfix, did hear the computer voice 2 or 3 times and last time it said lagfix was enabled. Rebooted to recovery again, checked lagfix was on, also for next boot, and flashed 10.2 again. Same problem, hangs at bootscreen.
Turned lagfix off again and flashed the old 10.1 again. Same problem again, this time only bootscreen with white SG text and both button lights on. Nothing for the rest. Flashed back, after lagfix enabled, to 10.2 again without luck. Again bootscreen only.
Someone knows how to fix this? Because of the usb problem I can't use Odin. I did read somewhere now there might be a cable problem or a dirty usb connector on the phone. Checked the connector visually and can't see any dirt, I also keep it closed when not using it.It does load the battery also when connected to my laptop. At least it did when I first got the unknown device error.
1) USB Error
I am not sure you have Only installed the USB driver alone or Kies it self. Anyway, try this http://support.microsoft.com/kb/315265. Scandisk with delete currupted file on your disk drive and replace with default window file. You can reinstall your driver/Kies on your laptop after scandisk complete.
2) First, you must come from JVP or JVQ base rom. JVO and older rom have older bootloader. What you need to do is to flash JVP or JVQ stock rom with bootloader into your phone. Then, flash over Darky 10.2 over the phone. Take note that Darky still have many problem and it is not that stable yet. I've run it over a week and decided to dump it. The rom is too big at 215MB where else others rom only 195MB. The startup is too slow, take 5-10min after reboot the phone. The initial start up takes nearly 15min after flash.
from.insider said:
2) First, you must come from JVP or JVQ base rom. JVO and older rom have older bootloader. What you need to do is to flash JVP or JVQ stock rom with bootloader into your phone. Then, flash over Darky 10.2 over the phone. Take note that Darky still have many problem and it is not that stable yet. I've run it over a week and decided to dump it. The rom is too big at 215MB where else others rom only 195MB. The startup is too slow, take 5-10min after reboot the phone. The initial start up takes nearly 15min after flash.
Click to expand...
Click to collapse
If your boot takes so long, you doing something wrong
First boot, yes... it takes some time. But then, the animation isn't finished yet and I'm already good to go (after media bla bla bla)
@OoZic
For darkys rom... i had the same problem.
First flash Ficetos resurection 10.2, then make shure lagfix is ON (full lagfix - check in voodoo control app) and then flash 10.2 extreme edition
For details go to
http://www.darkyrom.com/community/index.php?threads/v10-2-final-what-are-you-waiting-for.4253/
I had the problem too
Thank you for your reply from.insider
Problem is the phone can only do bootscreen and recovery. The device isn't recognized in any way. Tried it on 2 computers (laptop/PC) with different multiboots (Win7 X64 and Vista X86 on both). Maybe that is because the OS isn't loaded and can't go to MTP?
Is there a way to copy something from external SD to internal SD within recovery menu? Because that way I can copy a JVP or JVQ image to internal. Now there are only the 10.1 and 10.2 zips from Darky.
FSCK didn't find any problems btw.
Thanks again.
Problem solved, my Galaxy is unbricked and working again. Very happy now
Can't post a link because of low post count but the answer is on post-87372 on Darky.com.
The USB problem also went away, but after using Titanium to put my backup back the problem was here again. something in my settings or a service is screwing something up with the mtp I think. Used Android Booster to kill some things and it works again. As soon as I know what exactly is screwing up my mtp I will let you all know.
OoZic said:
Problem solved, my Galaxyd and working again. Very happy now
Can't post a link because of low post count but the answer is on post-87372 on Darky.com.
The USB problem also went away, but after using Titanium to put my backup back the problem was here again. something in my settings or a service is screwing something up with the mtp I think. Used Android Booster to kill some things and it works again. As soon as I know what exactly is screwing up my mtp I will let you all know.
Click to expand...
Click to collapse
Can you copy and paste the the answer and post it here man, i cant find the post your talking about and my phone has the exact same problem.