Related
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.
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
Hi!
I just bought a Nexus 4 with broken touch screen which I replaced myself.
After I replaced it, I decided to start fresh and updated the device directly to stock 4.4 using fastboot commands and got stuck in bootloop (4 circles going on for hours).
Then I tried different factory images and managed to boot under official Android 4.2.2 and it worked flawlessly until I tried to update with 4.3 OTA (with radio .83)
I found out that downgrading radio from .83 to .48 (or .53) allows the device to boot under Android 4.3.
I'm now stuck at this stage because the same trick does not work after 4.4 OTA (from 4.3).
The issue seems to be acknowledged by Google but they don't seem to have an official software fix for it since they only go for a replacement.
I'm considering an RMA but since I replaced the screen myself, I'm facing the risk to be charged 200€ if my warranty gets void (if they really control the device as they say).
Anyone managed to fix this issue? It seems to be linked to the radio (can't go further than radio .48 / .53)?
Just found out that the jack/proximity/light sensor wasn't properly connected, probably after the screen replacement. It now boots under 4.4.2
Found people with the same issue on this thread : http://forum.xda-developers.com/showthread.php?t=2595283
Just ended up reading it but my researches did not drive there earlier.
To conclude, bootloop under 4.3 and 4.4 can be related to a faulty (or just disconnected) sensor.
neoantho said:
Just found out that the jack/proximity/light sensor wasn't properly connected, probably after the screen replacement. It now boots under 4.4.2
Found people with the same issue on this thread : http://forum.xda-developers.com/showthread.php?t=2595283
Just ended up reading it but my researches did not drive there earlier.
To conclude, bootloop under 4.3 and 4.4 can be related to a faulty (or just disconnected) sensor.
Click to expand...
Click to collapse
I confirm my nexus also bootloops on android version >= 4.3.0 due to faulty sensor.
Basis of conclusion:
My nexus 4 also started bootloop suddenly. I tried installing 4.4.2 and even 4.3 from factory images but everytime it stuck at boot animation. The only version currently working is 4.2. I always used a software called smart cover but it started mus-behaving. so i downloading phone tester and proximity sensor finder from play store, both the programs told me they were waiting for sensor/they did not get data from proximity and light sensor.
Question:
is there any way to update to 4.4.2 without being stuck at bootloop without replacing the sensor?
thanks in advance!
varun037 said:
I confirm my nexus also bootloops on android version >= 4.3.0 due to faulty sensor.
Basis of conclusion:
My nexus 4 also started bootloop suddenly. I tried installing 4.4.2 and even 4.3 from factory images but everytime it stuck at boot animation. The only version currently working is 4.2. I always used a software called smart cover but it started mus-behaving. so i downloading phone tester and proximity sensor finder from play store, both the programs told me they were waiting for sensor/they did not get data from proximity and light sensor.
Question:
is there any way to update to 4.4.2 without being stuck at bootloop without replacing the sensor?
thanks in advance!
Click to expand...
Click to collapse
Did you find a solution?
Not yet. I will definitely post if I am able to find one. Researching on the topic currently.
I've got the same problem with 4.3 bootloop. Could this be fixed with custom rom?
Try flashing 4.2.2 rom - custom or stock
I'm with 4.2.2... and that's not what I asked. I want 4.4.2. Is it possible to load custom kit kat with this kind of sensor problems?
Update:
I have been trying to update nexus. I tried to install radio version 98 and bootloader from 4.4.2 version to android 4.2.2 without updating system image. it works. so i think basically the issue is with the system image itself. looking for the patched system image now or a developer who can patch system image to ignore the faulty sensors.
varun037 said:
Update:
I have been trying to update nexus. I tried to install radio version 98 and bootloader from 4.4.2 version to android 4.2.2 without updating system image. it works. so i think basically the issue is with the system image itself. looking for the patched system image now or a developer who can patch system image to ignore the faulty sensors.
Click to expand...
Click to collapse
I'm on 4.3 and the sensors dont work ... the proximity, gyro... nothing works... any solution?
Hello friends, i have a similar problem.
I went to replace the glass and warmed him a lot and damaged the lcd. I bought a complete lcd with touch, but when installing it the cel came in infinite boot, Flashed the 4.2.2 and booted but sensor is working by testing q I did for an app, the problem is they do not find my network and baseband ta as unknown, been through the radio's 4.2.2 (the version I am now). the motherboard was not with the screen when I get heated to the glass, were in housing with the display flex earpiece with proximity sensor and flex usb that has the microphone and led, everything is normal, the LED only that does not work. One would like some light please. I thought about buying the flex usb to see if it resolves, but does not want to risk spending for nothing. Thank you very much!
Sorry for my english, I'm using google translator
Sorry to Disturb
Hello everyone I am very new to this area of computing (and this forum). However I have still ended up in the same hole as you guys are describing although it happened for a completely different reason. (BTW: I am rooted)
one day I tryed to play the android game NOVA 3 on my Nexus 7 on the highest graphical setting so I went and researched how to do this. I was pointed towards some kind of app called 'ChainFire 3D', Once I pressed the install button inside this app the Nexus 7 switched off and the next time I tried to turn it on I got the X logo of death (boot loop). I then tried to enter recovery and I got the annoying 'no command' error. I cant seem to remember how I rooted this thing but I do have access to the fastboot stuff ONLY (inside cmd).
if there is anyone who has any idea how to go about fixing such an issue without wiping everything on my nexus could they please get back to me ASAP.http://forum.xda-developers.com/images/smilies/fingers-crossed.gif
Gloftking said:
Hello everyone I am very new to this area of computing (and this forum). However I have still ended up in the same hole as you guys are describing although it happened for a completely different reason. (BTW: I am rooted)
one day I tryed to play the android game NOVA 3 on my Nexus 7 on the highest graphical setting so I went and researched how to do this. I was pointed towards some kind of app called 'ChainFire 3D', Once I pressed the install button inside this app the Nexus 7 switched off and the next time I tried to turn it on I got the X logo of death (boot loop). I then tried to enter recovery and I got the annoying 'no command' error. I cant seem to remember how I rooted this thing but I do have access to the fastboot stuff ONLY (inside cmd).
if there is anyone who has any idea how to go about fixing such an issue without wiping everything on my nexus could they please get back to me ASAP.http://forum.xda-developers.com/images/smilies/fingers-crossed.gif
Click to expand...
Click to collapse
You might be able to re install your android without clearing user data. Try to flash the device with Google provided factory images without the reset tag.
FEW
varun037 said:
You might be able to re install your android without clearing user data. Try to flash the device with Google provided factory images without the reset tag.
Click to expand...
Click to collapse
Thanks for the quick responce. Could you please describe in more detail what exactly you mean and how I would go about doing this because I only vagely know what you mean by flashing.http://forum.xda-developers.com/images/smilies/confused.gif
Gloftking said:
Thanks for the quick responce. Could you please describe in more detail what exactly you mean and how I would go about doing this because I only vagely know what you mean by flashing.http://forum.xda-developers.com/images/smilies/confused.gif
Click to expand...
Click to collapse
Follow this. It has the reset flag removed and will not wipe your data
http://forum.xda-developers.com/showthread.php?p=53176897
Sent from my Nexus 5 using XDA Free mobile app
Hi,
I am facing the same issue .. Nexus 4 is stuck at boot loader after screen replacement .. is there any solution that I can follow to resolve this .
Regards,
Ripu Daman
The same problem with me, i did replaced my phone screen. I didn't notice that could damaged the phone. :crying:
so, theres no way to solve ??
Only way is to downgrade the os version to 4.2.2 and stay there.
nexus 4 stuck at boot loop.
Hi guys i have the same problem as you are describing, o got a nexus 4 android 4.2.2 JQRW build I've flashed it from all different ways and i just got flash cm10.2 and carbon rom but only stuff jeallybean and as someone said here i used adb sideload to push the update 4.3 and got stuck at the boot but i flash the radio 84 to 48 and my phone boot Fine but i am stuck at jeallybean yet and i want chroma rom android 7
---------- Post added at 03:00 AM ---------- Previous post was at 02:56 AM ----------
Please we need a wise man to fix this problem. I am tired of flashing stock img and custom ron for nothing.
Hi people:
I bought a Xperia X Compact 2 weeks ago. It seems to be a "journalist and commercial" terminal, as it came with version 6.0.1 of Android and did not allow updates via OTA.
I've used FlashTool to put another version of Firmware, the 7.1.1, and everything looks perfect, until I'm going to make a photo.
In the screen is observed to make the photo and I see the "picture" to take, but the touch button of the screen is not working. From that moment, the mobile starts to spend a lot of battery and the photo is not done. If you force the camera to front, a photo comes out completely in green.
I've put ROM 6.0.1 (Journalist and Commercial) back in, but the camera no longer works.
I have not done root.
EDITED:
Sorry. I lost DRM and the problem solved when I install patched Kernel. Problem is solved and I have 7.1.1 "with" DRM.
Thank you for your help
I have the same problem now , anyone know how to repair it
I might be having exactly the same problem. How did you get (and install) the patched kernel?
Thanks.
hi everyone.
i am having this wierd issue for a month or so, when i try to update RR rom.
after i flash the rom, i get the screen attached. screen seems for like 2 seconds, and goes this half black / half blue screen. screen is still responsive, i can receive calls and if i double tap anywhere, screen locks. there is no problem with screen on twrp or anything ( because sometimes after flashing the rom i dont get this screen, so i don't do anything else, except use it normally.) but today it happened without a reason, the phone was in my pocket when i took it out and saw the screen in this state.
i always flash by following the steps given. i know it is not hardware related. where is the problem? what do i need to do?
p.s. : when charging, blue part goes yellow.
thank you all, waiting for a solution
rukenau said:
hi everyone.
i am having this wierd issue for a month or so, when i try to update RR rom.
after i flash the rom, i get the screen attached. screen seems for like 2 seconds, and goes this half black / half blue screen. screen is still responsive, i can receive calls and if i double tap anywhere, screen locks. there is no problem with screen on twrp or anything ( because sometimes after flashing the rom i dont get this screen, so i don't do anything else, except use it normally.) but today it happened without a reason, the phone was in my pocket when i took it out and saw the screen in this state.
i always flash by following the steps given. i know it is not hardware related. where is the problem? what do i need to do?
p.s. : when charging, blue part goes yellow.
thank you all, waiting for a solution
Click to expand...
Click to collapse
First go to recovery and check that display problem present or not if not then flash any other custom rom or reflash rr
if you are unable to go to recovery then flash stock rom via odin it will fix every software related issue
and if flashing stock rom doesn't work then it may be hardware issue
You confirmed the model # in download mode? Tried using different version of TWRP?
I am facing same problem recently, did you find any solution ?
still no solution. this problem is not hardware related since i can use it perfectly now. i tried to flash (via twrp) RR-N-v5.8.5 exactly as described in op. rom boots, i can see the home screen for a brief moment but screen goes immediately black and blue. i can receive calls, lock and wake screen, that's all. then i have to restore everything. i am currently on hexagon rom v2.5 and no issues but i like RR.
again, this problem is not hw related. i follow all the steps again and again checking everything..
any ideas?
blue screen
rukenau said:
still no solution. this problem is not hardware related since i can use it perfectly now. i tried to flash (via twrp) RR-N-v5.8.5 exactly as described in op. rom boots, i can see the home screen for a brief moment but screen goes immediately black and blue. i can receive calls, lock and wake screen, that's all. then i have to restore everything. i am currently on hexagon rom v2.5 and no issues but i like RR.
again, this problem is not hw related. i follow all the steps again and again checking everything..
any ideas?
Click to expand...
Click to collapse
make a clean install and try a different kernel than pre installed one
maniwaraich said:
make a clean install and try a different kernel than pre installed one
Click to expand...
Click to collapse
clean install worked for a day or so, until i turned off ambient dislpay and restart. then it went blue&black again.
i tried a few kernels, some bootloaders and modems (including nordic) but problem persists.
i will try to get a logcat :/
In case anyone has the same problem: reboot to safe mode, go to settings, flip cover and turn off S-View flip cover.
Same issue un lineage og 15.0 and 15.1 on samsung galaxy S 5 mini G800F someone find a solution?
pierpa2 said:
Same issue un lineage og 15.0 and 15.1 on samsung galaxy S 5 mini G800F someone find a solution?
Click to expand...
Click to collapse
Read thread .
Flash stock rom and test .
But this is the Note 3 forum not your phones forum .
JJEgan said:
Read thread .
Flash stock rom and test .
But this is the Note 3 forum not your phones forum .
Click to expand...
Click to collapse
lareay flashed lots of time differents ROM sorry for the wrong forum but i can't find a solution.
Stock rom with oreo does not exist.
Solved turning off smart cover