Hey, I really didn't want to have to start a new thread but unfortunately as i have not posted before i could not post on the development thread for this ROM.
Basically I managed to successfully install SGBS 2.8.2, or i though i had. It boots fine but when it gets loading sense it gets stuck at the sense loading box, I am not entirely sure what may be causing this problem but i thought it may have something to do with me using a class 2 micro SD card.
Being that I am relatively new to the whole ROM and flashing scene i am not exactly sure on how to effectively troubleshoot the problem without posting on here.
I hope someone can help me and thanks in advance to anyone that is able to.
Thanks , Luke.
Sorry to re-post, I just realised that I missed some information that may be important, firstly I am using the stock Hboot version of SGBS, so I am not sure if perhaps that could be causing an issue as I am unsure as to how different boot tables would affect the loading speeds, if the would at all.
Also I have been experiencing problems with the flashlight on my phone, it began when I was using the flashlight apk and it randomly started becoming out of sync with the level of brightness that I selected within the app so I uninstalled it, now the flashlight LED randomly turns itself on for no reason, I did some research and I thought it could have been an issue with the proximity sensor but after downloading an app that reads the values for the sensor I discovered it wasn't.
I really am clueless as to what to do in an attempt to fix any of these problems but it certainly is becoming really annoying.
Thanks, Luke.
Flash a ruu and see if your problems are still present
Sent from my HTC Desire using XDA App
Yeah, I have thought of attempting to flash a RUU to fix my flashlight problems however I still cant figure out how to fix SGBS hanging at the loading box for sense. It's weird because I can still receive calls and use the notification bar and quick settings but sense just doesn't seem to load :/
Right well I just flashed the official HTC 2.3.3 RUU and it has not fixed any problems, ,my flashlight still randomly turns itself on and off. Although for some reason flashing the RUU did not s-on my device which it has done every time I have flashed my RUU.
Sounds like a hardware problem if the ruin has not fixed it
Sent from my HTC Desire using xda premium
Yeah, it has turned out to be a hardware fault so I contacted virgin and they sent out a new phone the next day. So all of those problems are fixed.
However I am still not entirely sure as to how to get SGBS working properly, the installation instructions for it are pretty vague so if anyone could give me some more detailed instructions for this ROM it would be greatly appreciated.
Related
Hi all,
I have been using LeeDrOiD on my phone for a while and really like it. I tried to upgrade to LeeDrOiD HD V3.3.3 GB-Port-R5 A2SD and despite everyone else seeming to sing its praises - I cannot get the thing to be stable. Everything seems to run fine until I make or receive a call. Sometimes I can make or receive a call fine and other times as soon as I get a call the thing crashes.
I say it crashes as the phone becomes totally unresponsive. If the screen was on it freezes with the current image or if the screen was off it freezes blank. None of the hardware buttons respond and the only way out seems to be to remove the battery and restart. The phone seems to still be alive somewhere below as if I am connected via bluetooth in my car, sometimes the call can carry on unhindered.
I seem to have narrowed it down to something between the radio and the LeeDrOiD ROM. Depending on the radio that use I get different frequencies of crash but I have not yet found a radio that in combination with this ROM that is stable.
It doesn't seem to be a hardware based fault as I can run other ROMs perfectly fine without crashes. I have no idea how to trouble shoot this further.
Does anyone have any ideas how to get further with this?
Thanks in advance.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
I guess no-one else has experience this problem. It was worth a try at least.
You just waited one day. Just chill a little.
TouchPaled from Oxygen with Transparent XDA App
I had the same problem. What radio and ril are you using? Might be worth flashing the latest ones you can. Wiping cache and dalvik.
The latest ril I flashed was for gingerbread and ended with HM. If that doesn't work try the latest kernel from snq- in the development sub-forum
Sent from my Leedroid HD Port powered Desire using Tapatalk
So far I have tried it with :-
LeeDrOiD_Radio_32.56.00.32U_5.17.05.08.zip
bravo_radio_5.17.05.23.zip
LeeDrOiD_Radio_32.54.00.32U_5.14.05.17.zip
a few others before I started to take note
Each time I tested it was with a full wipe and clean install. So far none have been stable. Any specific recommendations to try?
Hello,
I have an HTC Desire HD running Android 2.3.3. The device isn't rooted and I've never rooted it before.
I've checked on this site, and I've scoured Google all day but I haven't managed to find anything that matches my problem specifically, as explained below.
In the last couple of days I have been having a bizarre problem where after several minutes of normal use the phone becomes completely unresponsive or very laggy (to the point where it is unusable). This occurs whether I am using apps or simply looking at the home-screen.
The only thing that's responsive is the screen lock button, this works as normal. However when I then try to unlock the screen, the phone is still unresponsive and I'm unable to unlock it.
The only fix I've found (if you can call it a fix) is to leave the phone alone for a several minutes. If I do this I can once again unlock the screen as normal and continue using the phone, however after a few minutes of use it locks up again! This has been happening since last night now and I've found no way to break this cycle.
I did a hard reset to see if this solved the problem but it had no effect. The phone will boot as normal, and after a few minutes of normal use it will become unresponsive again.
I've also booted my phone without the SD card in just in case anything on this was causing the problem, still no improvement.
Has anyone else experienced a similar issue who could provide some insight as to what might be causing this issue? Any help you can provide would be greatly appreciated.
At first I thought this might have been a software issue, but as it persisted after the reset I'm beginning to think this might not be the case.
Thanks,
KaRsKiN
The problem is coming from the magnetometer. I have the same issue, please check this thread: http://forum.xda-developers.com/showthread.php?t=1394264
The only workaround I found is to disable screen rotation and do a couple of restarts (not switch off). Of course, no compass in the end, but at least I can use the phone.
KaRsKiN said:
Hello,
I have an HTC Desire HD running Android 2.3.3. The device isn't rooted and I've never rooted it before.
I've checked on this site, and I've scoured Google all day but I haven't managed to find anything that matches my problem specifically, as explained below.
In the last couple of days I have been having a bizarre problem where after several minutes of normal use the phone becomes completely unresponsive or very laggy (to the point where it is unusable). This occurs whether I am using apps or simply looking at the home-screen.
The only thing that's responsive is the screen lock button, this works as normal. However when I then try to unlock the screen, the phone is still unresponsive and I'm unable to unlock it.
The only fix I've found (if you can call it a fix) is to leave the phone alone for a several minutes. If I do this I can once again unlock the screen as normal and continue using the phone, however after a few minutes of use it locks up again! This has been happening since last night now and I've found no way to break this cycle.
I did a hard reset to see if this solved the problem but it had no effect. The phone will boot as normal, and after a few minutes of normal use it will become unresponsive again.
I've also booted my phone without the SD card in just in case anything on this was causing the problem, still no improvement.
Has anyone else experienced a similar issue who could provide some insight as to what might be causing this issue? Any help you can provide would be greatly appreciated.
At first I thought this might have been a software issue, but as it persisted after the reset I'm beginning to think this might not be the case.
Thanks,
KaRsKiN
Click to expand...
Click to collapse
It is possible that your battery could be failing. See if att has one they will let you exchange.
If its not the battery then it could be a hardware issue. Just send it in for warranty if that is the case. You should still be covered as the phone is not yet a year old.
Sent from my Inspire 4G using xda premium
Gizmoe said:
It is possible that your battery could be failing. See if att has one they will let you exchange.
Click to expand...
Click to collapse
How should this be connected to the battery...?
Anyway, I think that it is a software issue rather than a hardware one. Maybe something is running in the background, using 100% of the cpu. You could try CPUNotify for realtime cpu monitoring.
If that doesn't work, you should try the magnetometer way. Maybe it's a new issue. Never heard about it though
I do what i want, because I can.
Flussen said:
How should this be connected to the battery...?
Anyway, I think that it is a software issue rather than a hardware one. Maybe something is running in the background, using 100% of the cpu. You could try CPUNotify for realtime cpu monitoring.
If that doesn't work, you should try the magnetometer way. Maybe it's a new issue. Never heard about it though
I do what i want, because I can.
Click to expand...
Click to collapse
I'm not going to explain in detail about the relationship of voltages and CPU usage. The battery being bad can and has caused these exact issues. Just like if a power supply is failing it can cause a blue screen in windows. In android the phone rebooting itself or freezing is the equivalent to a blue screen. Since they have never rooted and are on a stock rom there is nothing except a hardware problem that would cause this. If the battery is not the culprit then one of the many components in the phone can cause freezes and reboots if it is failing. Android os does not allow a single task to take over the CPU. This is not a windows os. So like I said, just use your warranty and get it fixed. Stock phones should not be presenting this behavior, you would have to root it to cause these kind of problems.
Sent from my Inspire 4G using xda premium
Gizmoe said:
I'm not going to explain in detail about the relationship of voltages and CPU usage. The battery being bad can and has caused these exact issues. Just like if a power supply is failing it can cause a blue screen in windows. In android the phone rebooting itself or freezing is the equivalent to a blue screen. Since they have never rooted and are on a stock rom there is nothing except a hardware problem that would cause this. If the battery is not the culprit then one of the many components in the phone can cause freezes and reboots if it is failing. Android os does not allow a single task to take over the CPU. This is not a windows os. So like I said, just use your warranty and get it fixed. Stock phones should not be presenting this behavior, you would have to root it to cause these kind of problems.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Thanks for your help! My dad has the same device as me so I'll try swapping out the battery to see if this solves the problem. If not I'll try calling HTC to arrange a repair.
Any news? Was it the battery issue?
I recently installed the new RunnyRom 6.0 ROM, so it is my current ROM. With the previous version, at random intervals, my phone would either freeze after doing some simple task such as turning on the mobile network or just at random. At other times, the phone would not respond after the screen goes blank.
I am at my wits end and might end up throwing my phone at a wall. I've tried increasing the minimum CPU speed to no avail and other remedies from googling.
Must I buy a new phone? (my warranty is up btw, so I can't send it away back to HTC or the store I bought it from)
Before you say you are at your wits end, have you even tried flashing an entirely different rom to see if the issue presents itself again?
via xda app
Or a faster sd-card !
do you have ext on your sdcard and some kind of app2ext script?
Something like this?
It's a combination of sd card, sd-ext scripts running on it and bad reception. For me, the only ROM that doesn't have this problem is RSK v6.
stankyou said:
Before you say you are at your wits end, have you even tried flashing an entirely different rom to see if the issue presents itself again?
via xda app
Click to expand...
Click to collapse
I have, that's the reason I went from CM7 to Oxygen and back to Sense.
MarcelHofs said:
Or a faster sd-card !
Click to expand...
Click to collapse
I think this could be the problem, but I'll need to buy another card today to see. As for some reason my current card keeps getting errors when I connect it to my pc.
.tnm said:
do you have ext on your sdcard and some kind of app2ext script?
Click to expand...
Click to collapse
I believe RunnyRom v6 has that.
Ronok said:
Something like this?
It's a combination of sd card, sd-ext scripts running on it and bad reception. For me, the only ROM that doesn't have this problem is RSK v6.
Click to expand...
Click to collapse
I will try to switch back to CM7/Oxygen and see if the problems persist with the same frequency.
Go back to CM7 than Oxygen to test. Oxygen uses a script if an ext partition is detected. You wanna try and see if your phone will work well without any ext partition and CM7 doesn't support it out of the box.
Or if you can't help not having ext partition because of your apps, how about you format your sd card, repartition and start fresh.
via xda app
So as I did a full wipe and reinstalled CM7, lo and behold, the phone freezes on me in the 4ext recovery screen. Wiped again and tried to reinstall RunnyRom, same thing.
Seems like hardware issue if you get freezes even on recovery. You can flash a stock rom as a last verification but since you don't have warranty you might as well consider it as a reason to get a new phone.
There's the HTC One series or if you can still wait a bit longer, Galaxy S III is about to make a debut this May.
stankyou said:
Seems like hardware issue if you get freezes even on recovery. You can flash a stock rom as a last verification but since you don't have warranty you might as well consider it as a reason to get a new phone.
There's the HTC One series or if you can still wait a bit longer, Galaxy S III is about to make a debut this May.
Click to expand...
Click to collapse
I think I will need to settle for something a bit cheaper.
However, I have noticed that if my mobile network is on, most times it will freeze my phone if I use any app that uses internet such as Whatsapp, facebook or Google+. Not sure if that might be relevant. (I am on a CM7 ROM and it still freezes so it is most definitely a hardware problem I would agree with).
I had a similar problem with my HTC Desire. I was on the road a lot and noticed that when I came near certain areas, my phone froze. I think it was because of a bad radio or something like this.
Does it happen when you are in airplane mode?
I flashed the new CM9 and the problem stopped.
Alternatively, it didn't happen with the sandvold-ICS.
Have you tried flashing with a new SD-Card?
ravach0l said:
I had a similar problem with my HTC Desire. I was on the road a lot and noticed that when I came near certain areas, my phone froze. I think it was because of a bad radio or something like this.
Does it happen when you are in airplane mode?
I flashed the new CM9 and the problem stopped.
Alternatively, it didn't happen with the sandvold-ICS.
Have you tried flashing with a new SD-Card?
Click to expand...
Click to collapse
Never tried it with airplane mode on. There's less freezing with MildWild 4.4 but occasionally it will freeze.
I had this issue once with ics and drewis kernel, on tiamat no problems at all
From using Mildwild 4.4 I've realized that when my phone rings, the ringtone will not play and if I answer it as soon as the call ends the screen will not wake up. If I ignore the call and open any application, the phone will freeze. In both cases I will need to remove the battery.
Sometime fixing permissions from recovery sorts out freezing issues
Sent from my HTC Desire using xda premium
jmcclue said:
Sometime fixing permissions from recovery sorts out freezing issues
Sent from my HTC Desire using xda premium
Click to expand...
Click to collapse
Tried that too. No major change.
same exact problem, i'm running runnymede AIO, phone freezes often, especially when i'm at home where signal is not good.
i've got the feeling is mainly related to whatsapp, but it's just a feeling.
phone usually freezes when i wake it up from standby, the lockscreen ring does not respond.
it never freezes when in airplane mode.
i think i'll try a different phone part, then a different rom, it's a pity since this one performs really well for my needs.
sorry for my english, if i fix this i'll post here, cheers.
jeremypps said:
same exact problem, i'm running runnymede AIO, phone freezes often, especially when i'm at home where signal is not good.
i've got the feeling is mainly related to whatsapp, but it's just a feeling.
phone usually freezes when i wake it up from standby, the lockscreen ring does not respond.
it never freezes when in airplane mode.
i think i'll try a different phone part, then a different rom, it's a pity since this one performs really well for my needs.
sorry for my english, if i fix this i'll post here, cheers.
Click to expand...
Click to collapse
I think my problem was mainly the sd card as it deleted all of my photos and then randomly stopped reading in my phone.
I switched sd cards and ROMs and so far no freezes.
NovaStark said:
I think my problem was mainly the sd card as it deleted all of my photos and then randomly stopped reading in my phone.
I switched sd cards and ROMs and so far no freezes.
Click to expand...
Click to collapse
well, might be, but i'd find strange, mine is a brand new samsung class 6.
but i'll give it a try when i can.
Hi everyone,
I need help to sort out an issue about my front facing camera.
My phone is stock WWE version, I took the first OTA (1.54.401.5 I believe), then unlocked bootloader, rooted and installed ARHD 6.0.
Everything was working fine, then I flashed version 7.0 few days ago (without upgrading firware, as I'm one of the poor "Whelp" guys with firewater, so I couldn't get s-off) and now my front camera won't work. When I try to select it, camera application force closes and I'm back to homescreen. If I try to setup face unlock, I get a message saying sth like "Can't connect to front camera".
I've tried other ROMs like InsertCoin, same issue. Only way I could get it back to work again for a while was flashing Maximus HD.
I have NO IDEA what is going wrong here.
I doubt it is a hardware issue as everything has been working flawlessly for some weeks. So my question is, could it be a problem of ROM/firware version compatibility? Can keeping an "old" firmware cause this kind of issues?
Thanks a lot for your help!
right now, installing OTA (after going back to stock rom & recovery), hope things will get fixed...
I might be f***d for S-off since 1.54.xxx.10 patches the firewater exploit, but anyway...
I had similar issue after 2 months...my ffc 'disappeared' when I used a system info app to check hardware etc. and also noticed the duo effects stopped working...swiping to ffc in camera app didn't do anything either...weird...took to Sprint store and they verified and I had new phone sent in as replacement.
Sent from my 831C using XDA Free mobile app
Thanks for your feedback...
afterfirmware update, same issue, on ARHD and even on Stock ROM 1.54.xxx.10. Started to think itwas a hardware issue, thinking of sending the phone in HTC warranty (although I unlocked the bootloader) then I tried to flash maximus HD 4.0 again and WOOSH, issue gone!! FFC works as it should again. STRANGE as hell.
If anyone has a clue on how to solve this...
I have the same problem, I flashed the MaximusHD and doesn't work:crying:
Hello,
What version of Maximus HD did you flash?
I used version 4.0.
Well, what is strange is that after a while I switched to ARHD 8.0, then 8.1. All went well until last weekend, boom, issue is here again.
I'm thinking of a few things :
- software issue cause by God knows what.
probably not as I have had the issue with many ROMS, whatever version I'm using when it pops up.
Might be other apps but issue remains with clean install...
- Other hardware issue not related to phone (SD card...)
probabbly not as I tried to remove SD card, restart phone, same issue.
- hardware issue with the FFC, coming and going. In that case, not much to do apart from trying to get an exchange model.
maybe...
You could S-OFF using Sunshine and then reflash everything from the beginning and see what happens. Also means you'll get the right firmware on your phone as well
Hi EddyOs, and thanks.
Yes, did S-Off when sunshine was released. I used it to install HK audio mod on ARHD 8.1
Issue only came back recently, and hasn't gone since...
I'm completely lost here. Can a hardware issue be temporary, go, and come back? Seems strange to me.
nuts77 said:
Hi EddyOs, and thanks.
Yes, did S-Off when sunshine was released. I used it to install HK audio mod on ARHD 8.1
Issue only came back recently, and hasn't gone since...
I'm completely lost here. Can a hardware issue be temporary, go, and come back? Seems strange to me.
Click to expand...
Click to collapse
Well hit it with a hammer, if it still doesn't do anything then perhaps it wasn't hardware but software. :silly:
Seriously though, Yes hardware issues can "come and go" intermittently. I see that crap all the time at work.
Could try and completely start from scratch again and see if it helps like Eddy suggested, if it's a hardware problem then naturally it'll have to be sent back but luckly you have S-OFF so you can return to stock fully. Unlucky for you however, if the device gets exchanged then it means you'll have to fork out another $25 for S-OFF as it's a 1 phone only license
after five days, issue is gone. Now everything seems to work normally.
No hit, no drop, no shock whatsoever.
Now just waiting for the issue to come back...
I am also facing same issue..some1 Help,.
hello friends.. recently selfie option in camera is missing in my htc m8 phone.
Even i downloaded Selfie application from google play, But Front camera is not working..
Some one help us please..
IF any 1 got the solution, please post it here
Isn't there a HTC diagnostics code that you can use to test all features...that might help to see if hardware in fact has failed...that's basically what HTC would do if you were to call them...forgot the key combo off hand
Sent from my HTC One_M8 using XDA Free mobile app
Mafiakillers said:
hello friends.. recently selfie option in camera is missing in my htc m8 phone.
Even i downloaded Selfie application from google play, But Front camera is not working..
Some one help us please..
IF any 1 got the solution, please post it here
Click to expand...
Click to collapse
From the dialer dial *#*#3424#*#*
hit accept and test your camera
Hello everyone,
Before people start asking me to search the forums, I have searched for months about this issue and I'm hoping that we'll finally get a proper answer from some kind devs who are willing to take time to really debug and trace this issue.
I got a Nexus 7 2013 a looong time ago, used it on pure stock, locked boot loader, no root, no recovery, nothing. All the way until KitKat and the issue was never resolved. Can't remember when it started but the rotation gets stuck just randomly throughout use and doesn't work anymore, sensors show no data as others have reported, etc. Reboot and voila it works again. Rinse and repeat.
So I tried unlocking and flashing CM11 M7 at last. Same thing.
The thing that drives me up the wall is how little attention the issue is being given. Google barely acknowledges it, and not a single hint in the XDA forums of where the issue originates. Kernel, ROM? It's obviously most likely fixable via software if a simple reboot can fix it... We just need someone to start debugging.
I'd appreciate it if anyone who has the same issue or info about it post it below
Thanks
Sent from my Nexus 4 using Tapatalk
abubakr125 said:
Hello everyone,
Before people start asking me to search the forums, I have searched for months about this issue and I'm hoping that we'll finally get a proper answer from some kind devs who are willing to take time to really debug and trace this issue.
I got a Nexus 7 2013 a looong time ago, used it on pure stock, locked boot loader, no root, no recovery, nothing. All the way until KitKat and the issue was never resolved. Can't remember when it started but the rotation gets stuck just randomly throughout use and doesn't work anymore, sensors show no data as others have reported, etc. Reboot and voila it works again. Rinse and repeat.
So I tried unlocking and flashing CM11 M7 at last. Same thing.
The thing that drives me up the wall is how little attention the issue is being given. Google barely acknowledges it, and not a single hint in the XDA forums of where the issue originates. Kernel, ROM? It's obviously most likely fixable via software if a simple reboot can fix it... We just need someone to start debugging.
I'd appreciate it if anyone who has the same issue or info about it post it below
Thanks
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
No ideas other than to suggest that you do an RMA with ASUS. I just looked and I pre-ordered mine through Best Buy and it shipped July 26 of last year so you might still have time left on the one year warranty.
Hey, I hope this topic is still alive. Mine has exactly same issue as yours. It all started after I re- clean flashed Mahdi ROM (I messed up some stuff so I had to do it). Ive tried clean flash again, but it doesn't work. I've also tried different settings and apps but nothing helped. The only thing I found working is turning on lockscreen blur. For some reason, it makes the rotation work for a bit longer.