Hi, I just got an Z2 D6503 and after using it a few days I've noticed some random reboots. First time I've suspected the modifications that I did to it : root, recovery, xposed and went for a clean ftf flash. The phone still reboots...
I have no warranty and no desire to take it to a Sony service as it will take too long for nothing.
Therefore I'm writing here maybe there is a solution to my problem. Maybe this is a known issue with the Z2?
Let me know if you have any suggestions
Hmm, my dad had such a thing with his note 2, but in this case it was hardware problem.
Other than that, I've noticed that if minimum cpu frequency is set to high value it will also cause a reboot.
But since you're stock, then there shouldn't be any software issues and it might be hardware fault.
Sent from Xperia Z2
Luckily not from an iPhone = Yesterdays technology at tomorrows prices
@asilviug
I've had random reboot problems with several custom roms, never figured out the cause. I've been using Rajeev's pure x V11 for a few months with xposed and layers and never got a single reboot on that rom, maybe try this one.
Worst case scenario flash a stock .ftf with flashtool and don't root / mod anything.
If you have random reboots in stock rom it can be an hardware problem like @mr.loverlover suggested.
ptmaniac said:
@asilviug
I've had random reboot problems with several custom roms, never figured out the cause. I've been using Rajeev's pure x V11 for a few months with xposed and layers and never got a single reboot on that rom, maybe try this one.
Worst case scenario flash a stock .ftf with flashtool and don't root / mod anything.
If you have random reboots in stock rom it can be an hardware problem like @mr.loverlover suggested.
Click to expand...
Click to collapse
Thanks for the suggestion but I don't want to switch from stock to a different rom. I tried a repair with pc companion and so far no restarts (24h).
Related
My phone started rebooting several times. At first I thought it was the custom ROM, but it started happening in ALL roms I tested, specially when I try to test GPS: it just NEVER works. And that also happended with completely different basebands (Tested .49, .52, .54 and .58), 2.1, 2.2 and 2.3 ROMs.
My last attempt was to a clean Froyo FreeX10 beta install. Bb .54, Full wipe, etc etc.. For a few hours everything was normal but when I tried GPS (Google app) it restarted and ended up in a boot loop. Removed battery but it continues into loop.
Should I flash SE original ROM again (using SEUS?) to see if works? I'm out of ideas right now, please help!
Arrrgh! It's even worst than I thought. I tried flash Generic version 2.1update1 build 2.1.A.0.435 and the random reboots persists.
Also I noticed some weird things using Wifi, downloads on Marked just doesn't start, get paused like forever... HELP!!!!
I suppose force a repair with seus.and if that doesn't fix it then it might be some hardware issue :/
Sent from my Delorean using a flux capacitor!
Thanks. I even formatted my SD Card but still with problems, I'm thinking about buy a bigger/faster one and maybe another battery, but if it's the phone itself the problem then I'm in trouble.
PS: I tried SEUS but no go :S
sounds like the same problem i and other users have faced, tell me when the phone reboots take the battery out and give the phone a smell, does it smell like burning? mobo has gone
I say remove the GPS app using adb. Then flash a new ROM from scratch. Then install another GPS app.
lolman2810 said:
sounds like the same problem i and other users have faced, tell me when the phone reboots take the battery out and give the phone a smell, does it smell like burning? mobo has gone
Click to expand...
Click to collapse
Ouuuuch! It does! I thought it was the battery dying but in this case should I flash back to stock and use my warranty?
kozxmartt said:
I say remove the GPS app using adb. Then flash a new ROM from scratch. Then install another GPS app.
Click to expand...
Click to collapse
Thanks, didn't even know it was possible, will give it a try but now I think its the mobo
what is moboo?
mobo = mother board
Just FYI, my phone is on technical assistance right now and they informed it will take long because many X10 are having the same issue, it will probably be escalated to SE and I will probably receive a new one
Now let's wait, will report back later.
I've had the EVO3D since launch, and recently, it has been randomly rebooting at least once a day. It seems like it's getting worse and worse, as about a month or two ago (when I first got root) it was maybe 2-3 times a week. For the first month I had the phone before root (or even temp root), I only remember two specific occasions when it boot-looped until I had to do a battery pull. So i guess you can say it happened 2 times a month back from June-July.
I really love this phone but this is just getting ridiculous. I don't know what to do from here since I didn't buy the warranty. Any suggestions? I am using SupraRom (the latest AOSP version) and TWRP (1.2 or 1.3 (?))
As I typed this up, I tryed to reboot into recovery to see what version I have and it locked up again (black screen with lights on the buttons).
tannerw_2010 said:
I've had the EVO3D since launch, and recently, it has been randomly rebooting at least once a day. It seems like it's getting worse and worse, as about a month or two ago (when I first got root) it was maybe 2-3 times a week. For the first month I had the phone before root (or even temp root), I only remember two specific occasions when it boot-looped until I had to do a battery pull. So i guess you can say it happened 2 times a month back from June-July.
I really love this phone but this is just getting ridiculous. I don't know what to do from here since I didn't buy the warranty. Any suggestions? I am using SupraRom (the latest AOSP version) and TWRP (1.2 or 1.3 (?))
As I typed this up, I tryed to reboot into recovery to see what version I have and it locked up again (black screen with lights on the buttons).
Click to expand...
Click to collapse
I used to get it too. It stopped after I flashed (from hboot) the new radio, pri, and rpm, then updated ROM base to sense w/2.3.4 base. Try that, and of course, full wipe, sometimes random reboots is from dirty flashing oh yeah, and try making sure your VM heap is 42m or less in the /system/build.prop
tannerw_2010 said:
I've had the EVO3D since launch, and recently, it has been randomly rebooting at least once a day. It seems like it's getting worse and worse, as about a month or two ago (when I first got root) it was maybe 2-3 times a week. For the first month I had the phone before root (or even temp root), I only remember two specific occasions when it boot-looped until I had to do a battery pull. So i guess you can say it happened 2 times a month back from June-July.
I really love this phone but this is just getting ridiculous. I don't know what to do from here since I didn't buy the warranty. Any suggestions? I am using SupraRom (the latest AOSP version) and TWRP (1.2 or 1.3 (?))
As I typed this up, I tryed to reboot into recovery to see what version I have and it locked up again (black screen with lights on the buttons).
Click to expand...
Click to collapse
il Duce said:
I used to get it too. It stopped after I flashed (from hboot) the new radio, pri, and rpm, then updated ROM base to sense w/2.3.4 base. Try that, and of course, full wipe, sometimes random reboots is from dirty flashing
Click to expand...
Click to collapse
If the above steps don't work to clear the issue, I would suggest loading the latest stock system and kernel. If you still have random reboots on the latest stock system and kernel, it definitely sounds like it could be a possible hardware issue triggering a kernel panic causing the device to reboot.
This level of troubleshooting, determining what is causing the kernel panic and rebooting the device is beyond and most users and goes a bit deeper. Generally, on a fully stock system, this would indicate a serious programming error which should affect many users, or some type of hardware flaw in the specific device.
Random reboots are hard to prove. The best route would be to take the device back to where you purchased and/or Sprint and see if they are able to help you.
Hopefully the steps quoted above by updating the firmware and software to the most recent versions resolve the issue as it could have been a programming bug on HTC/Sprint's part.
Hope the extra information and details help!
here is the reboot fix
http://forum.xda-developers.com/showthread.php?t=1253126&page=2
download it and rename it to PG86IMG and goto bootloader problem solved
---------- Post added at 02:58 AM ---------- Previous post was at 02:07 AM ----------
follow the above link, then follow the link in the post. i would recommend installing the eniter zip package m the one that says nohboot, it has everything in it including the rpm update.
I've had 3 3D's, each running the same software at the time, only one ever did this. I personally think the freezing and reboots are more hardware related than not.
hi, my samsung galaxy s2 started making problems, if i reboot, most of the times I get a black screen which, curiosly, if I press the menu and back buttons, they light up! still, I have to reboot it several times (removing the battery does not help) untill i get a "successful" boot. I'm rooted and I am using omega v13 AOKP, based on JB 4.2.2 but this problem started some time ago, when i was using Omega v24 based on 4.1.2.
My phone is in warranty, but I woud like first to determin if it is a software or hardware thing, because if it is a hardware problem, I have to figure out a way or restoring to stock without leaving traces, so I can use it...
any ideas what the problem might be? the kernels on both versions I used were different, so it has to be something different...
thanks
Clean install of stock first. Test for a few days. Problems persist, then you send it in for warranty service. If the problems go away, then it's obviously something on the firmware you were using side. Try different custom roms/kernels in that case & see if you can reproduce the problem. If you can't reproduce it with other custom firmware, then it's an Omega problem - talk to the dev.
thanks
MistahBungle said:
Clean install of stock first. Test for a few days. Problems persist, then you send it in for warranty service. If the problems go away, then it's obviously something on the firmware you were using side. Try different custom roms/kernels in that case & see if you can reproduce the problem. If you can't reproduce it with other custom firmware, then it's an Omega problem - talk to the dev.
Click to expand...
Click to collapse
thanks, that is was i was thinking, although i hate to waste such an amount of time.. anyway, thanks for the advice, I'll guess I'll have to do it.
Hello XDA! I have been a keen follower of this forum for long, but this is my first post, 'cause well... this is the first time I pretty stuck at something.
I have a Xperia Mini Pro (SK17i) and I have been using it for quite a while, around 2 years I presume. I have rooted and unlocked the bootloader by the end of the first year, and have been trying out several custom roms, until stopping at CM10.1 of LegacyXperia. (the amazing creation of Mike for our 2011-line of devices!) However, as of a month back, my touchscreen kinda broke - it wouldn't respond along with the capacitive buttons. I tried the methods mentioned in the general section, but no avail - it simply wouldn't work at all. There's a thin small strip that appears around the screen during pulling out the hardware keyboard, and I guess that somewhat suggests that the touchscreen is invalid by hardware means.
However, that's merely a background to the problem I'm facing. Recently, after the launch of CM11, I thought of giving it a swing, seeing how I have been an avid-fan of the pure look of CM. I tried flashing the kernel using flashtool and start the phone, but the only thing that takes place is just a vibration and a black screen. The screen remains black for like ever, until I pull out the battery. I tried flashing the kernel thrice, and the same problem persisted all through. I reverted back to the stock ICS then and it worked like a charm, and the same goes for FXP CM10 and the last CM10.1 I used... there's no problem whatsoever, save for the broken touchscreen.
Any suggestion one might give about my problem? Thanks a ton for reading out everything!
psychoticdemon said:
Hello XDA! I have been a keen follower of this forum for long, but this is my first post, 'cause well... this is the first time I pretty stuck at something.
I have a Xperia Mini Pro (SK17i) and I have been using it for quite a while, around 2 years I presume. I have rooted and unlocked the bootloader by the end of the first year, and have been trying out several custom roms, until stopping at CM10.1 of LegacyXperia. (the amazing creation of Mike for our 2011-line of devices!) However, as of a month back, my touchscreen kinda broke - it wouldn't respond along with the capacitive buttons. I tried the methods mentioned in the general section, but no avail - it simply wouldn't work at all. There's a thin small strip that appears around the screen during pulling out the hardware keyboard, and I guess that somewhat suggests that the touchscreen is invalid by hardware means.
However, that's merely a background to the problem I'm facing. Recently, after the launch of CM11, I thought of giving it a swing, seeing how I have been an avid-fan of the pure look of CM. I tried flashing the kernel using flashtool and start the phone, but the only thing that takes place is just a vibration and a black screen. The screen remains black for like ever, until I pull out the battery. I tried flashing the kernel thrice, and the same problem persisted all through. I reverted back to the stock ICS then and it worked like a charm, and the same goes for FXP CM10 and the last CM10.1 I used... there's no problem whatsoever, save for the broken touchscreen.
Any suggestion one might give about my problem? Thanks a ton for reading out everything!
Click to expand...
Click to collapse
The kernel is incompatible with your phone.
Care to explain a little more? I have flashed the kernel provided within the rom zip itself (as suggested time and time again), and I have double checked its for the correct device - i.e. mango.
psychoticdemon said:
Care to explain a little more? I have flashed the kernel provided within the rom zip itself (as suggested time and time again), and I have double checked its for the correct device - i.e. mango.
Click to expand...
Click to collapse
kernel is for mango??unofficial port right...can you provide the rom link once.....??
http://forum.xda-developers.com/showthread.php?t=2545367
This is the one - LegacyXperia CM11 by mikeioannina.
psychoticdemon said:
http://forum.xda-developers.com/showthread.php?t=2545367
This is the one - LegacyXperia CM11 by mikeioannina.
Click to expand...
Click to collapse
yeah i though so...was going through the post...did you try this..
1.1 (optional): If the device is not booting, reboot to bootloader again and run:
fastboot erase system
fastboot erase userdata
As the rom requires a new partition table and maybe system and userdata is conflicting...
Dark Wraith said:
yeah i though so...was going through the post...did you try this..
1.1 (optional): If the device is not booting, reboot to bootloader again and run:
fastboot erase system
fastboot erase userdata
As the rom requires a new partition table and maybe system and userdata is conflicting...
Click to expand...
Click to collapse
Thanks a lot for pointing it out, mate! Usually the roms I tried didn't require such a thing, but this might be it. I'll provide feedback if the steps works.
I tried the steps advised, but the problem seems to still persist to some extent. The capacitive lights are lit and the screen is lit as well (as could be understood from the viewing angles - it's brighter and powered up). Nothing seems to appear on the screen though - no boot logo or anything - and trying to enter recovery fails as well (through power + vol up shortcut). I have tried it twice already, kept the phone switched on for five minutes or so, but no avail. I had to pull battery out every time to shut down the device. Anyone have any other advice?
psychoticdemon said:
I tried the steps advised, but the problem seems to still persist to some extent. The capacitive lights are lit and the screen is lit as well (as could be understood from the viewing angles - it's brighter and powered up). Nothing seems to appear on the screen though - no boot logo or anything - and trying to enter recovery fails as well (through power + vol up shortcut). I have tried it twice already, kept the phone switched on for five minutes or so, but no avail. I had to pull battery out every time to shut down the device. Anyone have any other advice?
Click to expand...
Click to collapse
try this.....Have the stock ICS 4.1.B.0.587 full ftf flashed (doesn't matter if you have flashed it in the past or if you flash it before installing cm11.0, it will work both ways)
then see if device powers up...
once it does...go for the next steps........
Dark Wraith said:
try this.....Have the stock ICS 4.1.B.0.587 full ftf flashed (doesn't matter if you have flashed it in the past or if you flash it before installing cm11.0, it will work both ways)
then see if device powers up...
once it does...go for the next steps........
Click to expand...
Click to collapse
Thanks for the quick response, but I tried that too. Unfortunately, the problem still seems to persist.
psychoticdemon said:
Thanks for the quick response, but I tried that too. Unfortunately, the problem still seems to persist.
Click to expand...
Click to collapse
I wonder if its a hardware related issue...you said in your op that there is some problem with your screen and capacitive buttons...Got any friend with sk17i???? I had one before it was stolen......Every other rom apart from CM11 is working right..Is there any other Kitkat based ROM for sk17i..if its there you may try that out and see if you have the same problem...otherwise..wait for a kitkat based rom to come up and try before flashing this...Try one more time from scratch...flash stock ICS 4.1.B.0.587 full ftf..reboot....once its working...fastboot flash boot.img...then better to fastboot erase system and fastboot erase userdata and then before it boots enter recovery and wipe data cache everything...flash update.zip..wipe cache,data,dalvik cache again...and boot..if it doesnt boot up then there is no option but to wait..
Dark Wraith said:
I wonder if its a hardware related issue...you said in your op that there is some problem with your screen and capacitive buttons...Got any friend with sk17i???? I had one before it was stolen......Every other rom apart from CM11 is working right..Is there any other Kitkat based ROM for sk17i..if its there you may try that out and see if you have the same problem...otherwise..wait for a kitkat based rom to come up and try before flashing this...Try one more time from scratch...flash stock ICS 4.1.B.0.587 full ftf..reboot....once its working...fastboot flash boot.img...then better to fastboot erase system and fastboot erase userdata and then before it boots enter recovery and wipe data cache everything...flash update.zip..wipe cache,data,dalvik cache again...and boot..if it doesnt boot up then there is no option but to wait..
Click to expand...
Click to collapse
Exactly. That's the whole reason why I posed this thread - to know if it was a hardware related problem right off the bat, or there was really something that I was doing wrong. I'll rather leave this one open to see if anyone have any other opinion about the matter. I really want to see what Kitkat looks like seeing how it's not available for my current device. (Micromax A210)
Also, about trying out other 4.4 roms... I guess I can try that route. But seeing how this problem is induced by the kernel itself and every other rom out there is mainly based off the LX 3.4 kernel, I doubt if that will work. I'll try the option anyway and see if it works.
psychoticdemon said:
Exactly. That's the whole reason why I posed this thread - to know if it was a hardware related problem right off the bat, or there was really something that I was doing wrong. I'll rather leave this one open to see if anyone have any other opinion about the matter. I really want to see what Kitkat looks like seeing how it's not available for my current device. (Micromax A210)
Also, about trying out other 4.4 roms... I guess I can try that route. But seeing how this problem is induced by the kernel itself and every other rom out there is mainly based off the LX 3.4 kernel, I doubt if that will work. I'll try the option anyway and see if it works.
Click to expand...
Click to collapse
Yeah.....waiting for other roms wont work.....cz they are all based on 3.4.x kernel.......Umm can you check your baseband after flashing full ftf...baseband should be : 8x55A-AAABQOAZM-203028G-77..every other rom based on 3.4.x kernel works right???...btw if you want to see how it looks just download a kitkat launcher from playstore....
Yes, the baseband is .77 after flashing the ICS 4.1.0.B.587. I used 3.4.x kernel with CM10.1, but never really tried CM10.2 to that extent. Maybe I'll try downloading that and see if it works... or even the EOL CM10.1.
And sure, the launcher would give in the feel, but I want the full experience possible really.
I flashed Iced Bean 4.0 on my xperia sk17i and i think my touch screen died because of it, That rom has aroma installer and there was no my device on that list so i chose xperia pro. Installation was successful but touch screen didnt work. I reverted to stock using flashtools and it still doesnt work. Is there any way to fix this problem? i really need to try something so pleas suggest.
Just to be clear i'm not blaming on anybody, it is total my fault. I'm fully aware of risk installing custom roms so pleas help in any way you can
Thanks in advance
Have you tried to flashing a new kernel which was made for the phone? As far as I know drivers areusually stored within it in Linux / Unix systems so it might apply here for the touch screen as well.
i tried using command fastboot flash boot boot.img and generally did not work. I have unlocked bootloader. I had hard time finding guide to do that for my phone. I did revert to stock using flashtools and ftf file.
When you say fastboot didn't work, do you mean it could not connect to the phone? Where you in fastboot mode when you tried it?
I recently put the 4.4.4 AOPK rom (Link) on my phone and had trouble getting into fastboot to flash the required kernel, I think I solved that by using the flashtool.
If flashing the stock kernel doesn't fix the issue, perhaps using a custom one, which works with ICS, will help?
You can find some here: http://forum.xda-developers.com/showpost.php?p=47407355&postcount=3
-edit-
does this thread help you? [TUT] Fix broken touchscreen problem of xperia mini pro (SK17i,SK17a)
Fastboot worked fine, but any custom kernel after successful flashing didn’t work. I have installed managed to install xperialegacy cm11 it has custom kernel and it didnt fix touch screen. I will try the link you posted. On the side note i bought another sk17 today, yes i love this phone LOL xD
Yess, million times thank you . I made it using this tutorial
here is what you have to do for fix your Bricked touchscreen.
What you need for that is any custom rom with an aroma installer.
1. Flash suitable firmware with Flashtool ( i flashed .587 Because i used Zellycream rom V4 )
2. Then Install any ics Kernel that you like (I installed messa hybrid kernel v4.3 )
3: Then install Any rom that has Aroma installer in it and does support your device, via Cwm recovery (I installed Zellycream V4)
3. While installing the rom choose ST17i in Aroma instead of SK17i
4. Reboot after installation is completed.
5. Wait until phone is On homescree.Nopw touchscreen should work but h/w keyboard not
5. Reboot again into CWM install "keymap_for_pro_XXXX.zip
Link here For Keymap Mini pro
6. Reboot phone again.. Now keyboard and touchscreen should be working. Also options for h/w keyboard should appear now.
Good luck,
It did worked for me hopefully its also going to work for you.
Notice : At first your Touch might not responce how it was before, but give it a time it will work fine after some hours or day or it might never work like before.Mine touch screen worked normally after 8 hours of installing the rom with this method.
Click to expand...
Click to collapse
Now i have questions. Can for some reason touchscreen die again? and also which rom do you recommend for good battery and camera? i like stock but i find it tedious to root and remove all the unwanted apps only to free up a couple of MB and potential screw something
Update: I see that i need to flash a zip which fixes tochscreen. when installing new rom. Is this hardware or software problem?
It would surprise me if the screen died again from the same issue, as the harmful code should have been overwritten by the fix.
I am not a developer though, just a normal user with some basic linux knowledge.
I'd suggest trying out Real ICS. I think I ran it before I got my new phone (I just recently started using the Mini Pro again) and can't remember having any complaints back then.
Other than that you could just go through the rom list. There are some which claim to be focusing on performance, I haven't tried them myself though.
I currently use AOKP kitkat (with some modifications, see this post) but I cannot yet if I'll stick with it. Maybe gonna try out this one http://forum.xda-developers.com/showthread.php?t=2277199 next.
I think im going to stick to the stock for the now. Camera is the best there
I tried swapping motherboard from working sk17i to mine. MB is on stock 2.3 and bt is locked. To my surprises it did not work. Phone boot fine but touch screen does not work. I though this is a software problem, but i guess touch screen device has some controllers or something that were affected too.
Bucov said:
I tried swapping motherboard from working sk17i to mine. MB is on stock 2.3 and bt is locked. To my surprises it did not work. Phone boot fine but touch screen does not work. I though this is a software problem, but i guess touch screen device has some controllers or something that were affected too.
Click to expand...
Click to collapse
I'm confused. Didn't you solve the issue already?
If the damage is permanent, then maybe the touchscreen got damaged by using the wrong rom?
If you really want to have two working phones, you could get a replacent display from ebay. They start at around 30€ these days.