Related
Hi everybody.
I have, installed on my Htc touch cruise, the Kostas wm6.5 Rom.
Everything seems to work wonderful, but I have a problem.
Sometimes wm6.5 blocks everything and I have to make a soft reset.
After that, wm6.5 doesn't restart for a few seconds.
Subsequently my Polaris makes a Hard Reset by itself, without any kind of request or intervention.
Someone can help me?
Thank you very much!!
its a bug in some of the builds. please talk about this in your ROM thread
This is what happend to me! exactly with this kernel and after some time I even couldn't turn on this device, it'was like a dead no screen. After 5h without battery it again started but after that again freeze, so now I installed original http://www.htc.com/www/SupportDownload.aspx?p_id=59&cat=2&dl_id=113
But it restart themself during loading, so now I am solving what to do probably I will try install ROM from SD card. But this is 2 issue, I don't know if there is som corelation between them, but first is that phone seems like that and need rest for start, now it I am nearly sure that it's HW problem and 2nd is bad OS.
But anyway I am trying to ask if you have similar experience, because my case start exactly same as yours, but now ends in real hell
EDIT: I definitelly had Kostas too, but I think that WM6.1
EDIT2: Can you send your S/N number, it's weird beacause friend which sold me this phone told me that phone was working 1y absolutelly OK and now around same date as you happend something similar, that's weird, or you have new phone?
Thanks anyway!
I flashed the original ROM and than Kostas' ROM. Now everything is ok!
I'm sorry I can't help you.
Bye
what you mean under original? I am pretty confused from so many versions now, can you give me link?
Have you used the correct radio?
I've installed an Italian Rom wm6.5 and I've had to install Radio 1.59 before install the ROM, then it's better to install an original ROM like this:
RUU_Polaris_HKCSL_WWE_3.19.831.3_radio_sign_25.85. 30.07_1.59.42.15_Ship
Daniele
From Kostas Rom Page:
Radio not included.You must use any 1.59.xx.xx version.(1.59.46.12 is the latest and recomended.)
general guidelines;
certain application is not working (particularly camera) -> change your radio
system unstable, random freezes -> hard reset
hard reset cannot solve the problem -> flash stock rom, then reflash custom rom, then hard reset.
my GF has a SGS I9000...i updated her via Kies to the latest firmware because it was performing like crap. The update fixed that but every now and again it stops responding and the screen goes black...lights are still working on the buttons.
You can't power it off with the power button and the only way to fix it is to remove the battery. I've just updated her the the latest ROM from XDA for the SGS from http://forum.xda-developers.com/showthread.php?t=1102881 XWJVZ/XXJVT/OXXJV9/Sbl (MultiCSC) but it still does it...any ideas??
I've seen a few posts but no fixes..any ideas...HW vs. SW..was fine before the updates.
tia
First thing to do is isolate the problem as a hardware or software one. Simple task: flash stock, and see if it happens. If it does, you know it's hardware.
If it isn't, ask the developer (if it's a custom rom), or post under the appropriate phone of the forum. Chances are, if it is software, someone else with the same device has had it before.
NType3 said:
First thing to do is isolate the problem as a hardware or software one. Simple task: flash stock, and see if it happens. If it does, you know it's hardware.
If it isn't, ask the developer (if it's a custom rom), or post under the appropriate phone of the forum. Chances are, if it is software, someone else with the same device has had it before.
Click to expand...
Click to collapse
Tried a stock ROM straight from the Telco, now flashed to a stock ROM from XDA. Happening on 2 phones, both SG2 i9000. Both have different ROMS from different Telco's both were fine before the latest ROM updates.
One appears better with the latest official stock ROM from XDA but just monitoring it at the moment...just wanted to know if it was a know issue before spending too much time on it
ta
To start of, I have been into rooting, installing custom ROMs and everything regarding it for quite a while but never ran into a problem like this. After Love posted his MIUI V5 I downloaded it and installed it. When it booted up I couldn`t unlock my SIM card due to a resolution error, you can`t see the "OK" nor "0" button. Then I switched to the Paranoid Android ROM ported and it booted up successfully. I went into options and changed settings regarding interface from "Phone mode" to "Phablet mode" as much as I remember it was the only thing I have done... Then when I had to reboot the phone, when it booted up, I inserted my PIN, but it showed something like "SIM card not inserted" and there was a popup which allowed me to reboot the phone. Now I can`t do anything about the problem. Tried switching back to the stock firmware and there I can unlock the SIM card without the "Reboot" prompt but still have no 3G access nor access to my contacts. I am asking you if you know anything about such a problem and if you have a fix for it. I also tried inserting a SIM from another phone, same problem- its not my SIM that is causing the problem. I think that it could do something with the radio, perhaps a component got corrupted somehow. Would really appreciate your help!
i also have the same problem on tipo caused from touchwiz rom, i am afraid only sony center are fixing this problem
I have spoken with my bro that has a Sony Erricsson Xperia X8 about the problem. He had the exactly same problem and he tried the same things as I did, but managed to fix the problem by relocking the bootloader and again unlocking it for further ROM installing. I will try and keep you updated.
Still nothing, nothing seems to help. Not even relocking the bootloader. Come on devs, can anyone at least try to assist us here? There seems to be something wrong with updating to another ROM. I would really appreciate some help here!
well yes i have also tried that locking and unlocking the BL, not just once about 10 times but still nothing, i tried almost everything and still have no clue,how to fix this
There is a fault in the ROMs, whichever caused this problem. I also saw the same thing happened to a Xperia J user with the MIUI v4.
Came across this today, I think some bring to light the issue:
http://forum.xda-developers.com/showthread.php?p=39845122
Nice find mate. So basically we need the stock radio files that we can flash in order for the SIM card to work again? Correct me if I am mistaken, in case I am not, can any of the devs look into it to try providing us with the radio file? I am not really keen in waiting a month until the phone gets repaired... Anyone?
I think that i have the same problem with my Xperia TIPO. After unlocking the bootloader and try some ROMs i found that i can´t do any calls.
I have try with a stock rom and another rom, but it doesn´t work. And the problem is not the sim card...
I am going to try relocking the bootloader, but it looks that the problem is going to stand there.
P.S: Sorry about my English
Well, it certainly seems you have the same problem. I would like to point out at this problem as it seems that everyone will have this problem when flashing a couple of ROMs...
Here is a topic regarding the same problem but with the exception that it is a problem the guy has on an Xperia S instead of Miro. It seems that the MIUI v4 3.1.11 ROM fixed the problem for another user(reply number 3 or 4 in the link). One of the repliers copy-pasted a probable fix but the download link for the provided radio modules are down. I sent a PM to Love if he can get his MIUI V4 3.1.11 download link back online. Will post for further updates!
Any luck with this? I have the same problem on my Tipo, and have had it for a while now. I outlined my problem here. I have had contact with devitrified, who has the same problem, and he has some more details here.
In any case, it is heartening to know there's more people with this problem.
i believe there are many people with this problem... i didnt figured out fix almost 2 months
STEELBAS said:
Any luck with this? I have the same problem on my Tipo, and have had it for a while now. I outlined my problem here. I have had contact with devitrified, who has the same problem, and he has some more details here.
In any case, it is heartening to know there's more people with this problem.
Click to expand...
Click to collapse
First of all thanks for posting something so everyone get to know that this problem exists, it seems like devs don`t really care or aren`t doing much to fix it. I hope that by time a lot of people will get this problem and that it will be fixed soon.
Is there any fix for this already?
It's really weird that no one said anything about this yet, since it's a problem that's being more and more widespread.
I have got a confirmation from the above poster that the problem stated in this topic started after flashing the Paranoid Android ROM for Sony Xperia Miro device. Can anyone else confirm the same thing?
WhiteHawkgrr said:
I have got a confirmation from the above poster that the problem stated in this topic started after flashing the Paranoid Android ROM for Sony Xperia Miro device. Can anyone else confirm the same thing?
Click to expand...
Click to collapse
mine problem became after installing touchwiz rom for tipo
This happened to me on Tipo (ST21i). I Flashed paranoid android fine, could a make call. Went looking around the settings and saw the page of DOOM, as i'm calling it, and there was no box checked, so I hit Phone mode and it asked whether it should reboot. I said yes, and then it broke. I thought it was the kernel so flashed pure CM10 kernel, which is what this port of P.A. was based on, and that didn't work, so I flashed MIUI port, but didn't do the kernel flashing, so it was on the CM10 Kernel. That didn't work and I couldn't enter my sim pin to try anyway, So I've flashed it again after flashing the kernel properly. Still didn't work. My grandad & mum are gonna be so angry. and it looks like I can't revert to stock, and Without stock it will cost a fortune to send it to sony. :crying::crying::crying::crying::crying: :crying::crying::crying::crying::crying::crying::crying: :crying: . Keep me posted if you find a download for the modules.
WhiteHawkgrr said:
I have got a confirmation from the above poster that the problem stated in this topic started after flashing the Paranoid Android ROM for Sony Xperia Miro device. Can anyone else confirm the same thing?
Click to expand...
Click to collapse
My problems came after flashing xperia z fire 5 ROM on xperia jlo.
I think my phone has water damage and thus not able to get warranty
Verstuurd vanaf mijn GT-P7510 met Tapatalk 4
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Try flashing a stock UCMC1 ROM and doing a factory reset after your flash finished successfully and Odin rebooted your phone.
3 things you need:
1- skyrocket windows drivers from Samsung website
2-Odin
3-stock ucmc1 tar ball.
Refer to this page:
http://forum.xda-developers.com/showthread.php?t=2228247
Good luck.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
sjbonner said:
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Click to expand...
Click to collapse
You don't need to install a custom rom. Try updating to official jellybean with kies, if that doesn't work then try C64's advice above with either UCMC1 or UXUMA7 (uxuma7 is less bloated).
The issue you're having is odd and I haven't encountered it before..
lingowistico said:
You don't need to install a custom rom. Try updating to official jellybean with kies, if that doesn't work then try C64's advice above with either UCMC1 or UXUMA7 (uxuma7 is less bloated).
The issue you're having is odd and I haven't encountered it before..
Click to expand...
Click to collapse
Thanks for the suggestions, C64 and lingowistico. Upgrading to JB was going to be my next move, but I wanted to know if anybody had seen this behavior first. I don't want to mess with the phone too much in case the seller will take it back (I may be on a loser there). I'll try the official upgrade and let you know.
Custom ROM not necessary -- true, but I've been running CM on my bravo for a couple of years and can't go back to a stock ROM. I'll try the de-bloated version of the official JB release, but I'd like something I can have more control over.
Cheers...
sjbonner said:
Thanks for the suggestions, C64 and lingowistico. Upgrading to JB was going to be my next move, but I wanted to know if anybody had seen this behavior first. I don't want to mess with the phone too much in case the seller will take it back (I may be on a loser there). I'll try the official upgrade and let you know.
Custom ROM not necessary -- true, but I've been running CM on my bravo for a couple of years and can't go back to a stock ROM. I'll try the de-bloated version of the official JB release, but I'd like something I can have more control over.
Cheers...
Click to expand...
Click to collapse
when phone is doing odd things the best way to ts is a complete wipe, formatting/removing sdcards then returning to stock w/odin, but you could try the debloated rom 1st just to test it out, if its resolved then its prob not hw related, just make a backup of ur current rom if planning on returning it but since you install an official stock it should also be returnable
vincom said:
when phone is doing odd things the best way to ts is a complete wipe, formatting/removing sdcards then returning to stock w/odin, but you could try the debloated rom 1st just to test it out, if its resolved then its prob not hw related, just make a backup of ur current rom if planning on returning it but since you install an official stock it should also be returnable
Click to expand...
Click to collapse
Thanks Vincom. I don't have access to a Windows machine at the moment so haven't been able to try the upgrade.
One question -- how is it possible to make a backup of the current ROM without first rooting and installing a custom recovery? I suppose that I could install the custom ROM and create a nandroid backup. Then if I needed to restore I could restore the nandroid and reinstall the stock recovery. Is there an easier way?
Apologies, I just saw that you have information on reinstalling the stock recovery on your Newb Guide.
BTW, I want to say thanks for your work on the Newb Guide. One of the things that sold me on this phone was the support that it has here. Amazing to have all of the information on installing the custom recovery, rooting, etc. all in one place.
sjbonner said:
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Click to expand...
Click to collapse
I believe I had this kinda issue once before, it was when I flashed CM10 or something. No incoming sound, sound did not work whatsoever, but installed a different kernel solved the issue, or flashing a new different rom.
econan1214 said:
I believe I had this kinda issue once before, it was when I flashed CM10 or something. No incoming sound, sound did not work whatsoever, but installed a different kernel solved the issue, or flashing a new different rom.
Click to expand...
Click to collapse
UPDATE:
So, I managed to upgrade to the official JB 4.1.2 this evening. Had to do it twice.
First time the boot got stuck at the AT&T logo and PC wouldn't detect the device. I followed the directions in another post http://forum.xda-developers.com/showpost.php?p=34682377&postcount=9 to repeat the upgrade and the same thing happened.
On a whim I decided to try rebooting a few times to see what would happen -- and it worked! Sort of...
I'm repeatedly rebooting the phone and sometimes it will start without problem. However, most of the time it gets stuck when the AT&T logo appears exactly where it should play the start up sound, except it freezes and the sound never plays.
I'm guessing that wiping the data before had nothing to do with fixing the problem and I was simply getting lucky on reboot.
I realize that this is a hard question without having the phone in hand -- but does this sound like a hardware issue?
Thanks again to everyone for their help.
Boot into recovery and factory reset from there. That should clear up the boot loop issue.
theesotericone said:
Boot into recovery and factory reset from there. That should clear up the boot loop issue.
Click to expand...
Click to collapse
Just a quick note to let you know how this was resolved. I returned the phone to the seller who provided a full refund.
Thanks again to those who respondend.:highfive:
Hello.
My problem is that sometimes, when I receive a notification, ambient display turns screen on to show it (as it should do normally), but then, when it is supposed to turn screen off again, it only goes black, but the backlight is still on. It's hard to notice, but I don't want the backlight on, using battery, when I think it's off.
The only way to turn it off is by activating ambient display again (moving the phone, waving in front of proximity sensor, pressing power button), and then it would show my normal lock screen and then turn off, until "something" makes it leave the backlight on again.
Anyone have/had/knows this issue? I've used Mokee ROM, now I'm on RR and it happened on both, I don't remember if it happened in CM. Could it be something app related?
Thanks.
Yeah same happened with cm 12.1 latest nightly too.....just checked it now...
The Answer
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
That's strange! I guess it may be something like the drivers you said, because just one user said that have the same problem, but I'll have to wait until I have some free time to flash stock and root and flash CM and restore all apps and that again... I hate that part of installing another ROM.
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Secuential said:
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Click to expand...
Click to collapse
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
therealduff1 said:
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
Click to expand...
Click to collapse
Thanks!
1)I can't tell if it occurs on stock, because on stock I use moto display (which doesn't have this issue).
2) I'm almost sure, because I've used 2 ROMs and both do the same. Maybe I'll have to try with CM nightlies?
3)I followed the guide in "general" section to flash stock using fastboot and android sdk. After that, I booted on stock, then rebooted to bootloader, flashed TWRP, entered to recovery, wiped data and then flashed RR ROM with it's gapps and then flashed moto camera and gallery. After that, wipe dalvik and cache and rebooted to system.
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
therealduff1 said:
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
Click to expand...
Click to collapse
Well, the other user that commented on this post was also using latest CM nightly, so I'm not very positive about it, but I may try it when I have time.
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
therealduff1 said:
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
Click to expand...
Click to collapse
Thanks! I have a lot of work right now, so I can't work with this now, but I'll email you when I have more free time!