Screen orientation stuck.. Anyone else? - Droid Eris Q&A, Help & Troubleshooting

I did search before posting so please forgive me if I've overlooked anything...
So my screen keeps getting stuck sideways. I'll turn it sideways to type on the bigger keyboard, view a site, or view photos, and it will not turn back after. I can shake it like crazy and it sometimes goes back, but not always. It's also quite embarrassing to do this in public... So my solution for now is to go to the home screen, which usually sets it back upright. However this is also quite annoying to keep going back to the home screen.
This is actually my second Eris to do this. It first happened on the stock 1.5 firmware, so I returned the phone and it was replaced. I was told they have never seen this problem, but it happened again, after thirty days. I'm not sure I can return it as I declined insurance. I decided to try the 2.1 leak, and the problem is still there. Now I'm worried about taking it in because I have a leaked rom on it, and don't want to get in any trouble.
Oh, I also tried the G-Sensor calibration tool, but it seems to just switch which way my orientation is stuck. The phone is set to switch automatically when rotating, so that isn't the issue.
Has anyone else experienced this? Any ideas?

Did you try disabling and re-enabling the 'Automatic Screen Orientation' (or whatever it is...)?

I've tried that countless times. Doesn't do anything for me.. I called Verizon and their response was bring it in and they'll replace it. I'm still hesitant to try with a leaked rom though. I guess my only option is to wait for the official update at this point? Thanks for trying to help though.

you should still be covered under manufacturers warranty. EVEN IF THE PHONE GETS BRICKED YOU SHOULD STILL BE COVERED. you can try and do an update to the 2.1 official update and when u go to apply that follow the prompts. when it gets to where it starts installing, you will see what it says"
system - updating
at the bottom it will say "do not turn off phone" MAKE SURE YOU PAY ATTENTION TO THAT. and let it do the update. also when you reboot the phone after that, let it do a normal update BUT DO NOT PULL OUT AND PUT BACK IN THE SD CARD while it is rebooting. that could be bad as well and end up bricking the phone.

Thank you for the instructions. I'll be sure to try this when the official update arrives. Hopefully it doesn't take too much longer..
Edit: I decided to go ahead and take my phone to Verizon to see if I could get it replaced. The guy didn't say anything about 2.1 or didn't notice. They didn't have any in the store, so I'll have to wait 2 to 3 days, then send the old phone back with the package.

Screen orientation stuck ?
This happened to me after jail braking my Eris Driod. Was not sure how to fix it. But I stumbled on to a fix that worked for me. Here it is. In display options using the G-Sensor calibration. I always did this holding my Driod upright on a level surface. It worked just fine. Then I started having problems and no matter how many time I did the calibration – My screen still would get stuck. Then I tried doing the calibration with lying my Driod flat on a level surface and that did it. Not sure why but I really don’t care – it just works. Good luck !

Related

Suggestions before placing 8525 for sale

I bought the phone thinking i could fix it... i have tried all the suggestions on resolving white screen... i have attempted to load Schap's cooked rom 4.22 and not luck... the phone powers on, syncs up i can access the files thru windows explorer... it charges... but still just shows the white screen...
Now after multiple attempts at loading the rom, i was able to get the today screen up once, but then it went away...
I have the phone, battery, charger, usb cable and software cd....
Since i can access the files thru explorer... is there anything i can do that way to see if i can get this phone working? maybe some files i can delete or replace...
I have tried the hard reset and soft resets adn nothing helps..
when i try to load the TNT rom when it gets to the part that its going to begin loading, it kills the activesync and then complains that its not connected or has been disconnected...
Anything else i can try?
Read this page, maybe you'll find the necessary help.
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick
cubangt said:
I bought the phone thinking i could fix it... i have tried all the suggestions on resolving white screen... i have attempted to load Schap's cooked rom 4.22 and not luck... the phone powers on, syncs up i can access the files thru windows explorer... it charges... but still just shows the white screen...
Now after multiple attempts at loading the rom, i was able to get the today screen up once, but then it went away...
I have the phone, battery, charger, usb cable and software cd....
Since i can access the files thru explorer... is there anything i can do that way to see if i can get this phone working? maybe some files i can delete or replace...
I have tried the hard reset and soft resets adn nothing helps..
when i try to load the TNT rom when it gets to the part that its going to begin loading, it kills the activesync and then complains that its not connected or has been disconnected...
Anything else i can try?
Click to expand...
Click to collapse
Two things to try if you've not...
1) Open it up (it's quite rugged!) and check the screen connector is plugged in OK. A lot of white screens are simply loose cables apparently. There is a thread discussing this here. Also Mikechannon is your hardware guru and his website has some excellent information about disassembly/reassembly that should help you out.
2) Try using the application "mymobiler" (freeware) - which allows you to see your hermes screen on your desktop PC when connected over activesync. I've put a mirror of the setup file here until 23/01 as the www.mtux.com site was timing out occasionally while I was looking this up for you (might be my end tho!)
Finally - I don't recommend attempting to flash any more ROMs until the screen issue is updated as you can't see whats going on and there is a risk you could end up with a weirdo hybrid-type brick
Good luck - Hope you get it working and if all else fails (I know you don't want to hear this) but I'm sure some of us here would be interested in slipping you a few quid for spares if the worst came to the worst...
I had almost given up on the phone once i was offered money for it.. i originally took it apart and only checked the connections on the main motherboard.. and that didnt work.. after reading the HTC tech manual and noticing that the LCD also had a cable that connected to a slot and not physically part of the screen i decided to open the LCD casing also.. and sure enough it was the LCD screen cable.. unless you really paid attention you would have never notice.. but i could see a slight angle on the cable connection, it was barely lose on one corner.. i re-seated the connection closed it up and less than 5 minutes the phone was working...
THANK YOU!!!!
I was able to fix a phone i bought for $75 and loaded TNT rom on it lastnight.. and have been customizing it the rest of the night and today...
Funny part is the guy who sold it to me, said it only need to have the ROM reloaded on it..
THANKS again for the suggestions and links... i have saved and booked marked everything..
I guess i spoke to soon... after posting that i was on my way with a nicely used $75 phone. The screen started to fade white....
Using My Mobiler i can see my desktop of the phone.. i can access and do everything... but the screen is white.. and it still functions as far as touch screen, so if guess at where things are i can tap on them and the phone reacts...
So now im back to square 1 with the phone, but atleast this time i know that it is functional software wise just cant see anything..
I opened it up 2 times since it went out and re-verified all connections.. everything has been reseated.. still no improvement.. if im lucky, it will come up to display but once i start tapping around on the screen it will slowly fade out to white...
I have noticed that alot of people have mentioned that after getting the white screen they load another rom on the phone and works for a while then starts to act up again.. can someone tell me how they are loading a rom on a phone with a white screen?
I mean i know the phone works besides the display since i have My Mobiler i can see and do anything i want on the phone.. but thats only good with a active connection thru activesync...
I dont want to try and reload a rom on the phone and mess it up more than it already is..
The screen will display for a few seconds sometimes.. and then fade out to white..

Help, I have a weird phone!

My phone is doing something really strange. It's a little hard to explain, but I'll try:
When I touch the screen to i.e. open an app, the phone "touches" somewhere else on the screen (mostly to the left of where I'm touching, I think) and opens something else. It also keeps doing stuff by itself, so if I am trying to type an "a" in a text message, it will write 7-8 other letters, followed by 5 spaces or something. Once in a while I am able to hit whatever button I am aiming for.
This makes my phone impossible to use.
Some background:
I've had the phone for a little over a month.
I rooted it less than two weeks ago with the exploid method described in this forum. I installed titanium backup and used it to erase the pre-installed game demos. Didn't touch anything else.
I tried to change some wifi settings after rooting, but unplugged usb cable at the wrong time, so my phone died. After one hour of charging it booted again and seemed fine.
I updated it last week and lost root. Other than that, the phone seemed fine.
Today it started behaving as described above. I have not made any changes to it recently. It started doing this when I took it out of my pocket to answer a call. I tried SEUS repair. It didn't fix it...
So. What should I do now?
That sounds as if the screen's registering multiple touches (you get that sort of behaviour if you're accidentally touching the edge of the screen when you use it) - have you tried thoroughly cleaning the screen, in case dirt is upsetting it.
Otherwise, I'd do a SEUS repair back to factory default, and take it back to the shop you bought it from, asking for a replacement
benjymous said:
That sounds as if the screen's registering multiple touches (you get that sort of behaviour if you're accidentally touching the edge of the screen when you use it) - have you tried thoroughly cleaning the screen, in case dirt is upsetting it.
Otherwise, I'd do a SEUS repair back to factory default, and take it back to the shop you bought it from, asking for a replacement
Click to expand...
Click to collapse
I did a SEUS repair earlier today. Is it impossible to tell that the phone has been rooted after you do a repair?
Also, yes, I have tried cleaning the screen, lol
I'm sending it tomorrow. Can anyone answer this:
Do I have to do anything to hide the rooting of the phone? I have done the repair process with SEUS. Is it possible to see that the phone has been tinkered with?
Regards,
don`t worry .....after repair is not possible identify if phone was root or not ....
Ok. Thank you!

[Q] Banging my head on my desk over moral dilemma

I just can't freaking stand it.
Starting about three weeks ago I have been having major problems with my Streak doing spontaneous restarts. I tried everything. Nothing worked.
I went as far as to use the Wiki instructions to install a version one generation old on the phone so that it would do an over the air update to the current release, which it did. Didn't help. Whenever I used the phone for a long call or to play a game or use navigation, anything that kept it actually doing something for several minutes, it would start rebooting. Sometimes it would freeze to where I had to pull the battery. I even bought a disposable phone while on vacation so I could have something I could count on.
So last week I called Dell support and described what is going on. When the tech heard the symptoms and that I had already done a factory reset and fresh loads and more factory resets, he quickly decided to replace the phone.
I have had the phone since April 2011 and in May I dropped it in my living room. It has worked perfectly but does have a crack in the glass that is purely cosmetic and is not why I tried to get it replaced. The phone has worked perfectly until recently.
I'm banging my head on the desk because, wouldn't you know it, the phone has been working perfectly since I called in. We didn't do anything, just talked about the phone, and it has had one restart in the last week. As a test, I used the Navigator for the 30 mile commute home from work. My wife called me, the phone answered, worked flawlessly on speaker, and when she hung up the Navigator came right back up as smooth as you could ask for. The one game I play right now (Grave Defense) has worked flawlessly except for one restart in the middle of a game. I couldn't ask for the phone to be better.
So what do I do when the replacement arrives? I'm not sure if I trust the phone not to start screwing up again, but I'm going to be sending back a phone that is apparently working fine but has a cracked glass. We all know the entirely reasonable conclusion they will come to.
So what should I do?
Maybe you should call Dell and tell them that the screen is cracked. Find out if they will even take it back. They may not, and wind up charging you for the new one. I've not heard of them doing this, mind you, but it sounds possible.
They may just tell you to send in the old one anyway, but you may as well let them know that the screen is cracked, since they are going to find out when they get it. Hopefully since you already have a return authorization, it wont matter...
Has anyone noticed it seems to be easier to get a replacement since they EOL'd the Streak?
Sent from my Dell Streak using Tapatalk
Maybe they're trying to clear out stock?
I had no problem sending it back with the cracked glass as long as the problem had nothing to do with the glass. Now the damned thing is working, so I have an issue with it.
I really don't understand this phone. I didn't change anything and it is like a different phone.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Oh, I thought the screen cracked after you called them.
Nevermind. As long as you disclosed the cracked screen, don't hesitate to send it back. If it was bad once, no reason to think it wont be again.
There are definitely some flaky ones.
From some posts I've read, it does seem as though they are being unusually friendly about returns lately. Prolly just my imagination...
Sent from my Dell Streak using Tapatalk
slaydog said:
As long as you disclosed the cracked screen, don't hesitate to send it back.
Click to expand...
Click to collapse
Oh, I never said I did that. I don't want people to think they are knowingly taking back units with cracked screens. The tech didn't ask if it had ever been dropped and I didn't see the point in volunteering the information as it had nothing to do with the problem I was having. I know that is not exactly taking the high road, but as I said, the screen isn't why I'm exchanging it. I considered swapping my cracked screen and the unbroken one from the replacement and sending my flaky phone back with the good screen, but they would probably notice that the phone had been dismantled and assume that is the source of the problem. I'm between a rock and a hard place here, but it's my own fault. I'm probably going to end up with a bill for the replacement phone, but I'll cross that bridge when I come to it.
I'm mostly just astonished at how freaking strange the behavior of this phone is. It was working fine then lost its mind for about three weeks and then decided that it was going to start working the way it is supposed to again with no interference from me. It was flaky in the morning, I did nothing to it, and that afternoon it started behaving itself.
Well, it froze up good yesterday. Tried everything short of swinging a dead cat over my head in a cemetary at midnight and got it working again, just in time to retire it.
When I got home the replacement was waiting for me. Smooth as silk. I played the hell out of my new favorite time sucking game last night (Stupid Zombies) and not a single hiccup. I'd love to lose some of the extra apps, but I think I am going to leave well enough alone this time. Now I need to find out how much Dell is going to bill me for returning a unit with a cracked screen, but I'll worry about that when it happens.

Blue Screen of Death,, not really dead..

Not sure if any of you have seen this,, but every now and again when I unlock my screen the screen flickers blue to a magnified/garbled screen. If I lock out the screen and unlock it, it goes away. Anyone else get this?
Never seen that before. Maybe you should try a hard reset
Sent from my HTC Rezound
Never seen it. Device hot at all? Are you rooted/debloated or anything?
Phone is still stock with a few apps disabled (amazon, blockbuster) but I noticed it even before disabling. No heat from what I can tell, is there an app I should load to monitor? I may go to Verizon tomorrow and see if they'll replace it.
I have seen this and more. Now and then when I hit power to turn my Rez on I get 2 screen images, one on top of the other, both flickering and jumping around. The phone will do nothing during this "episode", but if I hit power off and then back on it's fine. If I could only get it to do it while at the Verizon store! I tried to take a screen shot last time and all I got was a normal screen. I'll take a pic with my camera if I get the chance. I'm sure that my Rez will need to be replaced, but after all the time to set it up like I like it, I"m not in a hurry to swap. I came from having 3 Tbolts and am tired of changing phones. I will say otherwise, I love this phone!!
my friends rezound has this problem. she was too lazy to return it iwthin the 2 weeks to swap it out, so now she's stuck with it..shes an idiot lol but she hasn't complained to me since about it..so either it doesn't do it as much, or she's used to it. i told her to try a factory reset, she hasn't yet. have you?
I got my Rez because I called Verizon so many times complaining about my Tbolt, (after I had 3 Bolts). The last time I called I said I just wanted out of the phone. The nice Verizon lady asked what I wanted and I said a Rezound. It was just a swap, I had to buy a battery and I didn't get the beats headphones. She also didn't change my contract, so I still get my upgrade at the end of this year. I will do a hard reset if this persists.

[Q] Need MAJOR HELP **A PHONE FROM HELL.*

Hi guys! I'm new around here, I've been lurking the forums for the past year or 2.
I originally had a i9000. Had it rooted, flashed & running 4.2.2 Hellybean, it was a dream, easiest android phone i've ever dealt with.
Today, I bring you a device that is so mind boggling and mysterious, it's ridiculous. Before you ask, yes I've searched and searched countless hours on end & sleepless nights. Trying to work out how to PERMANENTLY fix this device.
Straight up, I'm going to tell you what I've done, what I've tried, where the phone came from, model of the phone & all the useless stuff.
OKAY. Go.
I got the Samsung Galaxy S2 (i9100T) off a friend recently, about a month or two back. He didn't have a back cover for it, and the camera was all smashed up (back camera). It was running on 4.1.2 Vodaphone Stock DVLSH. It had a few issues when the phone got to me.
I wasn't sure if the phones battery was depleted, but I had to muck around with the phone for a couple of hours just to get the damned thing to turn on.
When I had got the phone to turn on, I kept getting "Warning! Battery Disconnected!" messages, this was frustrating. I eventually let the phone fully charged before I mucked around with it and ignored the warning.
When it was fully charged, I went straight to rooting it. I first rooted it by flashing CF-Root and then flashed a custom rom. (Xylon AOKP. 4.2.2)
From here on, the phone started to randomly restart, drop signal, lose battery after random restarts, get semi boot loops.
So I flashed a different stock (XWPL8) and got rid of the Samsung Galaxy SII i9100T boot logo and it was changed to Samsung Galaxy SII i9100.
After this, I then again rooted the phone but this time a different method and used Siyah kernel and flashed Carbon rom 4.2.2.
I still encountered the same problem as Xylon 4.2.2.
So I kept reverting back to stock, re-rooting & trying again.
I've tried countless methods.
POSSIBLE HARDBRICK RECOVERY DON'T TAKE MY WORD THOUGH: I've even managed to HardBrick the device (yes I mean hardbrick, i didn't even JTAG to bring it back... I flashed Dorimax Kernel at some point and it hardbricked it to all ****.) I spent a few days trying to unbrick it when finally I just plugged it into the charged and forced it to internally turn on (i believe) and let the battery deplete (the phone was hot even when i unplugged it. So I let the battery drain.) Yes I even battery pulled and tried to reboot it to see if I could boot recovery or download or the rom even before I tried any of this! (absolutely nothing.)
I took out my SIM card after a full day of letting it drain (just to be sure) plugged it in, took out the battery while the charger was plugged in, put the battery back in, unplugged the charger while holding power, and plugged it back in and I got the charging logo booted into download mode after 80% charge and flashed stock again.
Now the problem(s) with the phone:
SEMI-BOOTLOOPS: Every time i've rooted the phone and even flashed different roms just to make sure, it does a "semi boot-loop" I've searched everywhere for people with the same problem but found nothing on it.
What it does, is it turns on (boots the samsung logo.) turns off, turns back on, turns off, turns back on etc and then after about 2-8 times of doing is usually it boots to the ROM and the phone works for awhile.
RANDOM REBOOTS: I don't get these much anymore since I found a solution where someone had just folded up a receipt and pushed the battery up against the prongs because it had about .5mm movement off the prongs. This fixed most of the random reboots and don't see many anymore.
SLEEP OF DEATH!?!?!? OR JUST A BLACK SCREEN THAT DOESN'T TURN BACK ON!?: This one I'm not 100% sure what it is, I read it's the S.O.D (Sleep of Death). Which is common on 4.0.4 and was apparently fixed in later Android versions. But sometimes, when I lock my phone, or my phone goes to sleep, the screen stays black even after I press the home button or the power button, at first I thought just restart it by battery pull or holding down power like everyone says, yeah it works, my phone boots up and does a semi-bootloop and goes back on eventually, but one day I left it on in the mysterious S.O.D. and waited 5-10 mins pressed the power button and it unlocked... This one really has me baffled and it does it a LOT.
REALLY BRIGHT SCREEN AFTER REBOOT SOMETIMES!: Okay, so sometimes when the phone finally turns on, the screen is really bright, like the brightness is still on half, but it's a lot more noticeable on how much brighter it is, it's nearly like a white.
It's really really BRIGHT. Phone shouldn't be able to look/get that bright. After a reboot though it goes away and goes back to normal but this leads me to believe something to do with the battery just a hunch.
RANDOM FREEZES!??!?: Sometimes the phone will just randomly freeze, I can be doing something and it'll just freeze, it won't turn off, I still get picture on the screen but it's frozen and I can't do anything until I either battery pull or reboot it by holding down the power button.
Before anyone asks, yes, I Factory Reset from recovery, Wipe Cache & Dalvik Cache before, I flash a new rom etc.
- My GApps matches with my Android versions each time.
- The ROMs I have flashed are compatible with my phone.
- And I've made sure everything I have done is completely compatible with my phone and android version.
What I think!:
SEMI BOOT-LOOPS:
This one, I don't think much of, it's got me baffled. It could be something to do with the Boot-Loader, could be something to do with a bad flash (but I've even tried double flashing a single rom.)
the eMMC could be damaged in a certain way that it causes these self proclaimed "semi boot-loops"
RANDOM REBOOTS:
This one, I've pretty much fixed with the help of lurking the internet over and over for hours, so this indicates a battery problem, will be replacing it this week. (Yes I'm aware that this battery problem could be causing everything else to play up and that it could all be due to the battery but can we leave the battery out of this just for now so I have more options on how to fix it.)
SLEEP OF DEATH!?!?!? OR JUST A BLACK SCREEN THAT DOESN'T TURN BACK ON!?:
I believe that this could be due to either a high load on the CPU (maybe not so much high but a really low load that it goes into a state of nothing for awhile.) It drops into a mode where it's turned off (something bigger than deep-idle.)
REALLY BRIGHT SCREEN AFTER REBOOT SOMETIMES!:
I haven't changed voltages or messed with any voltages on my phone, but I believe that it does indeed have something to do with the CPU & GPU voltages or even the BATTERY Voltages either undervolting or being to high.
RANDOM FREEZES!??!?:
I think this one is something to do with my phone not liking the voltages stock set to it.
I read that somewhere Freezing the System Alarm Clock can fix the random reboots, so I've done that and also pushed the battery up with a bit of receipt so it touches the prongs completely.
Anyway, right now, the phone is on Stock Kernel with CWM Recovery6, with PacMan's 4.3.1 Nightly release on XWLP8 Baseband and it still does this all.
I know i'm asking for a lot of help and I'm probably going to get yelled at by Devs or forum mods or some body because I've done something wrong.
But if it doesn't belong here, move it please.
IT TRULY IS A PHONE FROM HELL.
-Thanks, Just another man who wants to fix silly problems for fun.
Youve said "dont mention get a new battery".What if that is the problem.
Maybe the phone has water damage, or it needs that hawkerpaulls scripts run.
Youve just got to try free stuff, then maybe splash a bit of cash I.e battery.
Nothing software/firmware-side is fixing this. Phone has major hardware issues going on. I wouldn't bother beyond trying the 'free stuff' TheUnderling mentioned.
erm - I'm agreeing with you on this 'phone from hell!' also agree with @theunderling and @MistahBungle - it doesn't sound like its worth fixing if the free stuff doesn't work - sounds like it would probably be cheaper to buy a second hand s2! Don't think dori kernel had anything to do with your 'hard brick' - I've been running dori for some time including the experimental builds, dori tests everything himself as do his team of testers - the 'd team' and I have never known him to release anything that even soft bricks let alone hard bricks.
Good luck :cyclops:
Hey guys thanks for the speedy replies! I love waking up to instant replies!
theunderling said:
Youve said "dont mention get a new battery".What if that is the problem.
Maybe the phone has water damage, or it needs that hawkerpaulls scripts run.
Youve just got to try free stuff, then maybe splash a bit of cash I.e battery.
Click to expand...
Click to collapse
Sorry, I was half asleep when writing all this! I am getting a new battery this week! But I wanted to have a go at trouble shooting it but crossing out the battery from the list of problems seeing as it's being replaced this week @theunderling
MistahBungle said:
Nothing software/firmware-side is fixing this. Phone has major hardware issues going on. I wouldn't bother beyond trying the 'free stuff' TheUnderling mentioned.
Click to expand...
Click to collapse
It may sound like it @MistahBungle but I have faith and I come down to being very patient with technology even when I do reach ticking time bomb mode. I believe I can fix it if I just get the right help !
If the new battery doesn't do anything, It might be the logic board and i'll just go buy a new one.
Jimsilver73 said:
erm - I'm agreeing with you on this 'phone from hell!' also agree with @theunderling and @MistahBungle - it doesn't sound like its worth fixing if the free stuff doesn't work - sounds like it would probably be cheaper to buy a second hand s2! Don't think dori kernel had anything to do with your 'hard brick' - I've been running dori for some time including the experimental builds, dori tests everything himself as do his team of testers - the 'd team' and I have never known him to release anything that even soft bricks let alone hard bricks.
Good luck :cyclops:
Click to expand...
Click to collapse
@Jimsilver73 It really is!
I'm not the most wealthy person or have money to just throw at things like new phones etc etc. I'd love to see what I can do on my side and try and trouble shoot every problem for even the simpilest of DIY Solutions. I get a kick out of mucking with phones and computers.
Your probably right, but I was thinking that does Dori kernel keep stock voltages or does it change the voltages at all? Because it just managed to Hardbrick its self a few hours after flashing it which was odd, which led me to suspect that my phone didn't like the Dori Kernel & Carbon Rom Combination!
@theunderling I will try that Hawkers script by the way!
Is this the one? http://forum.xda-developers.com/showthread.php?t=2100558
Phone having no back cover and camera smashed suggests that there is a physical damage to the phone, i wouldn't even try battery to this one, it may just kill the new battery if there is some kind of water damage, tho you seem like having fun trying to repair it Yes, that's hawkers script, use it and couple of ROMs, (ICS,GB etc) to see if there is a software problem. If you can dissamble it, you can check if there are some contact problems between pieces.
Hi @Dakura thanks for the reply!
The camera isn't smashed completely, but at fist I thought that the camera would be screwing up the phone in someway.
I know for sure as well that there is no water damage, and the phone was just sitting around he lost the back cover randomly after he had bought an iPhone 4S.
I can disassemble it, I just need to find my little screw driver I use for stand-off changing on PC cases.
I read somewhere that the proximity sensor has a bit to do with things, so seeing as the back cover isn't on, that maybe dust got into it while it was in his draw and that's the reason for screen-offs? because the phone is still responsive. I can receive calls & text messages just the screen is black and doesn't come back on.
The warning in 4.0.4 "Warning! Battery Disconnected!" leads me to think that in versions above 4.0.4 (4.1.2 for example) don't have warnings and the phone just turns off.
**major update**
@Dakura @theunderling @Jimsilver73 @MistahBungle
Hey guys, so I've just taken the back CASING not the cover. Off the phone.
I've been looking for breaks in solder points on the Logic Board and around it.
- The Camera ISN'T smashed it was the lens on the case..
- Looks a tad dusty.
- Semi Boot-Loops have disappeared! booted the phone with the case off and the semi boot loops are gone tried booting multiple times each time with success!
- No breaks on the logic board from what I can see as far!
- For some reason the Camera app would not connect to the Camera. "Can't connect to Camera!" maybe the camera flex cable isn't in properly.
- First boot with case off, battery gave false reading of -1021032418914 (something along those lines). That's usually caused by a lose battery correct me if I'm wrong?
- Everything seemed a lot more responsive and working.
Hmmm.
So removing the screws and taking the back casing off made the Semi Boot-Loops go away.
Maybe a part of the back casing was pushing on the Logic board and shorting it out?
Maybe the screws torque where messing with it (e.g. on a HDD with computers the simpliest change in toque on the screws in the HDD can screw the HDD.)
But the torque of the screws where very loose.
Any ideas are much appreciated!!
Yep, probably a short-circuit or dust problem or displacement somewhere around there. What you said proves that somehow the phone was physically damaged. You may need to actually disassemble all the pieces, inspect them and put them all back together, and it still may not work, for now, try cleaning the dust and tighten the screws, fasten the board.
@Dakura thanks for the help today Dakura!
Finally got around to putting everything back together after an evaluation, made the flex-cables all snug and tightened up the screws a lot!
The phone appears to be working now.
at 100% it even vibrates now when i tap things it never used to.
I couldn't quite locate the problem, but I have a feeling that one of the flex cables could have come loose but only just enough to generate fluctuation of power between full and under to keep the phone on.
Hopefully the phone stays stable!
@theunderling thanks for recommending me HawkerPauls Nuke script, I'll be using that every time I re-rom my phone from now on!
Will update the thread on a possible fix for anyone else with this problem.
It's always good to run through every possibility and solution to fix problems before going out and blowing money.

Categories

Resources