Sorry if this has already been posted.
My phone is rooted on stock rom.
It started freezing up and wouldnt send text messages. GO sms locked me out. I had to take the battery out and restart several times. Now i cant connect to any wifi. In wifi settings it just says error. Any ideas what could be wrong?
your best bet is probably to flash back to stock OS...i dunno if there is a one click for inspire
or you could flash a rom :]...this was probably a weird glitch that would go away with a simple full flash
Why not start with doing a factory reset?
Sent from my Desire HD using XDA Premium App
I think he already did that, but if that doesn't work, try restoring your entire phone to stock...idk if there is a one click Odin for inspire like there is for Galaxy S models
Thats what I was thinking about doing. Will try that this weekend when I have time. Thanks!
henry.menzies said:
Thats what I was thinking about doing. Will try that this weekend when I have time. Thanks!
Click to expand...
Click to collapse
There's a guide stickied to this section that believe has the link to the RUU, which is what you might try, though I think going the RUU route will unroot you.
Inspired Ace 1.0.1¦ XDA Premium
Full wipe reflash should do it.
Sent from my HTC Desire HD using XDA App
yep I would try wipe data/factory reset, wipe cache, wipe delvik cache and a clean install of the rom
Flashed CoreDroid didnt fix the problem
would flashing a new radio fix the problem?
Did you have any luck with this? Im having the same issue and debating whether or not I should flash back to stock to see if this resolves the issue. I have flashed countless ROMs since root with no luck.
My phone is doing the same thing. Not sure when it started doing it since I don't use wifi often. I wanted to check for updates and the HTC one requires WIFI be on, thats how I found out.
My phone is completely stock, with only Apps installed. Factory reset made it say something about connecting for 10 seconds or so before saying error, and now once again it just says error every time i try to enable it.
Related
Okay so.. I have an answer to my problem.. this is a problem that i had encountered many times in forums while i was looking for my answer.. big thanks to diablo2224 for his help and a thanks goes out to Cranvis for actually replying at all..
Okay so the home button wasn't working at all and it would flash and basically do zero (im sure this fix would help any buttons if this was the case). In the end i didnt have much to lose the home button not working was giving me the 'sheets' so i just tried to flash most things for wifi xoom as i was hoping it would crack a difference but it didnt... i ended up seeing a post from stachre for an update and in it was there he had pointed to stock motorola files.. i grabbed these and preformed all wipes (user data, cache, delvik - i doubt it would do much but i did it anyway).. using fastboot i then flashed the boot.img, the system.img, the userdata.img and finally the recovery.img (can always flash over the CWM anway so not a big deal) and booted it back up... suprise suprise the home button was perfectly functional again (every other update/flash of software would seeming 'update' and not actually flash to that portion of the device thereby leaving my problem and the stock images must have actually hit these sectors) i know my answer is long but just trying to be helpful to anyone else with this type of problem (stock Xoom WiFi MZ604 HWI69 images from Motorola)
as a side note : this was followed by flashing the CWM again and booting into CWM and flashing the 2.1 hammer and then wiping user data and booting into the freshly updated rom stoked!
okay it seems the home button is not working at present. i have wiped all data and cache and dalvik cache a thousand times and tried reflashing, etc still to no avail. does anyone have any more ideas? its painful to push the back button a million times to get anywhere lol
joshndroid said:
okay it seems the home button is not working at present. i have wiped all data and cache and dalvik cache a thousand times and tried reflashing, etc still to no avail. does anyone have any more ideas? its painful to push the back button a million times to get anywhere lol
Click to expand...
Click to collapse
ok, so a few questions.
I am guessing it is rooted so my questions are:
What ROM are you using?
Have you tried other ROMs?
Have you been experiencing this problem since you installed the rom?
have you downloaded anything (APP, Live Wall Paper, a random APK File) before this happened?
Are you using a screen protector on the Xoom?
~If yes to the last question, is there any air bubbles or dirt in that area of the button?
~If no to last question, are you aware of any dirt or scratches in that area?
Have you tried the Home tab in Landscape as well as Portrait mode?
Have you just recently updated to a OTA that was pushed out by either Motorola/Verizon/etc?
There could be many possible reasons as to why this is happening... and I would like to help you (and who ever posts afterwords) to fix this situation. I or someone else on this board will respond as soon as possible to your problem and I hope this post helps to solve the problem
Cranvis said:
ok, so a few questions.
I am guessing it is rooted so my questions are:
What ROM are you using?
Have you tried other ROMs?
Have you been experiencing this problem since you installed the rom?
have you downloaded anything (APP, Live Wall Paper, a random APK File) before this happened?
Are you using a screen protector on the Xoom?
~If yes to the last question, is there any air bubbles or dirt in that area of the button?
~If no to last question, are you aware of any dirt or scratches in that area?
Have you tried the Home tab in Landscape as well as Portrait mode?
Have you just recently updated to a OTA that was pushed out by either Motorola/Verizon/etc?
There could be many possible reasons as to why this is happening... and I would like to help you (and who ever posts afterwords) to fix this situation. I or someone else on this board will respond as soon as possible to your problem and I hope this post helps to solve the problem
Click to expand...
Click to collapse
Okay mate ill answer each question firstly i was on the manta ray with update rom.. Everything was fine i was able to use it perfect as normal no updated apks no new apks.. I was fine i cam home from work seen the update so downloaded check the md5 and did all wipes as instructed in the tiamat 2.1 rom.. I had previously installed the kernal for that the day prior and was running great.. I tried reinstalling the previous rom again after a few reflashes of the 2.1 hammer and wiped that see if the button would come back to no avail..
I have a screen protector but it is fine i was using it for days prior wirh not 1 hiccup so that is definately elimated.. No pushed updates.. I went through all otas already before i flashed the manta ray stuff and as i said that was fine all the other buttond beside it work like tje back menu and switcher just the home does nothing
Cheers
Josh
Sent from my HTC Sensation Z710e using XDA Premium App
joshndroid said:
Okay mate ill answer each question firstly i was on the manta ray with update rom.. Everything was fine i was able to use it perfect as normal no updated apks no new apks.. I was fine i cam home from work seen the update so downloaded check the md5 and did all wipes as instructed in the tiamat 2.1 rom.. I had previously installed the kernal for that the day prior and was running great.. I tried reinstalling the previous rom again after a few reflashes of the 2.1 hammer and wiped that see if the button would come back to no avail..
I have a screen protector but it is fine i was using it for days prior wirh not 1 hiccup so that is definately elimated.. No pushed updates.. I went through all otas already before i flashed the manta ray stuff and as i said that was fine all the other buttond beside it work like tje back menu and switcher just the home does nothing
Cheers
Josh
Sent from my HTC Sensation Z710e using XDA Premium App
Click to expand...
Click to collapse
Thank you for the speedy reply to my questions. And I am sorry to say, this is one that is over my head. I would suggest that you go to Tiamat's (Or current ROM's) maker and inquire for their help. I am new to some of this but I thought I should at least ask you the basics and make sure on everything. (Woo A+ Tech Training haha!) But unfortunately, I cannot help you with this problem because I do not know what could be doing this other then maybe a line of code didn't get placed into memory when the device was flashed, or maybe there is a small error in the code itself and only certain devices have this problem (different model number = slightly different change to the chip-sets and code of the device.) There are many things that could be the trouble, and like i said, unfortunately, they are out of my understanding of the device.
I do hope that you are able to get an answer soon to your question and I hope it is a simple answer.
Sorry I could not help any more but I hope others can!
Good Luck
joshndroid said:
okay it seems the home button is not working at present. i have wiped all data and cache and dalvik cache a thousand times and tried reflashing, etc still to no avail. does anyone have any more ideas? its painful to push the back button a million times to get anywhere lol
Click to expand...
Click to collapse
I reported this issue once before when I was using Xoom Zone a month or so ago. I hadn't wiped data, and it was like the home button was there just to look pretty. You could click it, it would highlight, but it was broken. If anything, I can be of service as I have had this issue once before.
I will need more info though. Do you restore data and try to hit the home button, or do you try the home button after a fresh data wipe without restoring data? It's hard for me to explain what I want you to explain, but...
diablo2224 said:
I reported this issue once before when I was using Xoom Zone a month or so ago. I hadn't wiped data, and it was like the home button was there just to look pretty. You could click it, it would highlight, but it was broken. If anything, I can be of service as I have had this issue once before.
I will need more info though. Do you restore data and try to hit the home button, or do you try the home button after a fresh data wipe without restoring data? It's hard for me to explain what I want you to explain, but...
Click to expand...
Click to collapse
A fresh data wipe mate exactly as the hammer rom thread instructed to do. No restore of data as i wanted to start fresh as i find less problems arise when u try to recover too much data and as the thread specifically called for a wipe i was more than obliging lol
Sent from my HTC Sensation Z710e using XDA Premium App
joshndroid said:
A fresh data wipe mate exactly as the hammer rom thread instructed to do. No restore of data as i wanted to start fresh as i find less problems arise when u try to recover too much data and as the thread specifically called for a wipe i was more than obliging lol
Sent from my HTC Sensation Z710e using XDA Premium App
Click to expand...
Click to collapse
I see. I've never heard of this version of the problem. My problem occurred when updating from the 3.1 Rom to the 3.2 Rom. I only had this problem because I didn't wipe data the first time because after it booted up I thought all was well... until I discovered the home button was broken... lol.
Anyways, even I'm at a loss here for how we can solve your problem. A simple data wipe resolved mine in a heartbeat... but it seems your problem is still persistent even after a clean data wipe install... interesting... can't say that I've ever seen a problem stay in the memory even after a complete data wipe...
The only thing I can suggest is to maybe drop back to a stock Rom, maybe 3.1, then installing Tiamat from that fresh stock Rom with another clean data wipe before and after. That's all I can think of since after a data wipe it's still there. Good luck!
I dropped back to manta still with the issue.. Would a nandroid recovery possibly help fix as it takes precedence over an update cuz thwn someone maybe be able to help
Sent from my HTC Sensation Z710e using XDA Premium App
joshndroid said:
I dropped back to manta still with the issue.. Would a nandroid recovery possibly help fix as it takes precedence over an update cuz thwn someone maybe be able to help
Sent from my HTC Sensation Z710e using XDA Premium App
Click to expand...
Click to collapse
That might help. I can help as much as I can, but...
Try to go full stock first before anything. Do not use Tiamat for right now. Install a completely stock, but rooted 3.1 Rom is what I suggest for you to do so that you can see if it's still giving you troubles on a stock Rom.
I tried that from the other thread and gained a bootloop.. Maybe stock 3.1 recovery and not just an update more to the point where would i find such? I only used otas as i was just speeding process to get to 3.2 to start flashing customs
Sent from my HTC Sensation Z710e using XDA Premium App
joshndroid said:
I tried that from the other thread and gained a bootloop.. Maybe stock 3.1 recovery and not just an update more to the point where would i find such? I only used otas as i was just speeding process to get to 3.2 to start flashing customs
Sent from my HTC Sensation Z710e using XDA Premium App
Click to expand...
Click to collapse
I dunno man, I'm usually one who has great helpful answers, but... uh, this one stumps me. Like I said, I've never seen a problem that still persisted after a data wipe. It's almost as if it is much deeper than a data wipe, but more like something has locked itself into your Xoom's memory and won't leave without forcing it out manually... something must be messing with your system files or something like that. Possibly something left over from the OTA updates of some sort maybe. Very strange...
I would pass this by Team Tiamat. Sorry I can't help this time. Good luck!
I need a nandroid i think from someone
Sent from my HTC Sensation Z710e using XDA Premium App
joshndroid said:
I need a nandroid i think from someone
Sent from my HTC Sensation Z710e using XDA Premium App
Click to expand...
Click to collapse
So you want someone to have a completely data wiped nandroid backup of the latest Tiamat Rom so that you can use that? That should work, especially if the backup has everything working perfectly. By having the ability to use nandroid backups you have nothing to lose since it can be restored very easily.
im not picky i would like a nandroid of any rom really mate... as long as the home button was working... so basically from a wifi US xoom (if compatibility was an issue) and the rest was okay yeh that would be great... i dont know anyone else with one here in AUS so someone here would have to help me out
p.s i have already tried the one from the dev thread of the stock 3.2 but that is bogus and doesnt really work for anyone and it didnt for me
joshndroid said:
im not picky i would like a nandroid of any rom really mate... as long as the home button was working... so basically from a wifi US xoom (if compatibility was an issue) and the rest was okay yeh that would be great... i dont know anyone else with one here in AUS so someone here would have to help me out
p.s i have already tried the one from the dev thread of the stock 3.2 but that is bogus and doesnt really work for anyone and it didnt for me
Click to expand...
Click to collapse
I have a 3G Xoom, but I can make a data wiped clean nandroid backup for the latest Tiamat Rom, which I am running since Tiamat supports 3G and Wifi models alike. I can do that after work tomorrow if you would like me to...
Or you could find someone who has the Wifi model and do that.
diablo2224 said:
I have a 3G Xoom, but I can make a data wiped clean nandroid backup for the latest Tiamat Rom, which I am running since Tiamat supports 3G and Wifi models alike. I can do that after work tomorrow if you would like me to...
Or you could find someone who has the Wifi model and do that.
Click to expand...
Click to collapse
thanks for ya help... i solved my problem and edited my first post
joshndroid said:
thanks for ya help... i solved my problem and edited my first post
Click to expand...
Click to collapse
Cool! I knew it was something with the system files. Case closed.
In the ARHD forum a while back someone advocated the strategy of never wiping data when switching between ROMs. He said he had never wiped data, and if he ever ran into problems with an app on a new ROM he just manually cleared that app's data and everything was fine.
He boasted essentially never having to reconfigure anything on his phone, and that he has successfully retained every app, setting, and text message that he's always had every time he has flashed a new ROM.
Is it possible that this is true?
I doubt it,
I didn't wipe once and ran into so much errors that I ended up re flashing whole rom..
Honestly it doesn't take much more then 30-35 min to setup a new rom specially if you buy the titanium backup app they even have a free version of it which also works great.
Sent From My Sexy Sensation Running Aokp.
well on the ARHD thread it says a wipe is optional when coming from previous versions, but personally i've only flashed it once so i can't say something about it.. however, when i do upgrade from rom's i have just flashed over it (if im switching to different rom i do a wipe) and haven't had problems, unless it says a wipe is recommended when upgrading then i just do a full wipe, and then restore the data from previous backups within 4EXT, this restores all my apps and settings i had previously.. its worked for me so far
I had once do that because i forgot to wipe the data. I forgot the rom's name but i experienced no error then i switched to Smartdroid rom
Sent from my HTC Sensation XE using xda premium
Like i said before.
You do wipe your ass when you are done taking a dump dont you?
Its possible. But dont complain about having crap in your underware
Btw. Use search. (Not attacking.you)
http://forum.xda-developers.com/showthread.php?p=23405654
Ive seen multiple threads about this
typed on a sensation cracked screen
stroobach said:
Like i said before.
You do wipe your ass when you are done taking a dump dont you?
Its possible. But dont complain about having crap in your underware
Btw. Use search. (Not attacking.you)
http://forum.xda-developers.com/showthread.php?p=23405654
Ive seen multiple threads about this
typed on a sensation cracked screen
Click to expand...
Click to collapse
LOL
Sent From My Sexy Sensation Running Aokp.
Love that analogy! But yes, wiping is very important!
Sent from my HTC Sensation 4G using xda premium
think id be ok to flash a completely new rom without wiping if my plan is to reflash again after a wipe?
cresch07 said:
think id be ok to flash a completely new rom without wiping if my plan is to reflash again after a wipe?
Click to expand...
Click to collapse
Yeah but what's the point, there are many apps out there that can back up your data to restore afterwards.
I almost lost my phone!
I flashed a custom rom in my htc.... it was a total loss.. i don't know what happened..but as soon as i locked it....it never came back.... proximity sensor flashed red light all the time.....finally, had to open the back cover to make it work and boot into recovery....
I'm currently on ViperS 1.2.1, Ive had this issue for couple of Sense 4 roms already. Sometimes when a call comes, I dragged the accept button to the ring (or pull up the ring), it stops at the screen which have 2 rectangle buttons at the bottom (the screen which an incoming call shows when youre using your phone). After awhile the call will be missed. Anyone experiencing the same issue? It only happens sometimes though and I've been scolded by parents for missing their calls
Hi there, I use viper also. I don't have this issue. What I suggest is doing a new fresh download of viper and a fresh installation. Meaning wipe cash wipe dalvik, wipe data factory reset, then install the new fresh download and see if that solved the issue.I'm hoping it will because not everyone experiences this and perhaps a fresh download will help. You can also post this on viper development site where everyone is using the same Rom and see if others are also experiencing this. In the mean time try what I suggested and make sure you do your backup. Backup applications too for easier retrieval . I hope this helps, I think it might because like I said its not a issue all viper users have. Best of luck and I do hope this works. Remember use a new download incase the old download got compromised somehow causing this issue. Best wishes.
Sent from my HTC Sensation 4G using xda premium
realsis said:
Hi there, I use viper also. I don't have this issue. What I suggest is doing a new fresh download of viper and a fresh installation. Meaning wipe cash wipe dalvik, wipe data factory reset, then install the new fresh download and see if that solved the issue.I'm hoping it will because not everyone experiences this and perhaps a fresh download will help. You can also post this on viper development site where everyone is using the same Rom and see if others are also experiencing this. In the mean time try what I suggested and make sure you do your backup. Backup applications too for easier retrieval . I hope this helps, I think it might because like I said its not a issue all viper users have. Best of luck and I do hope this works. Remember use a new download incase the old download got compromised somehow causing this issue. Best wishes.
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
i always do a super wipe everytime i flash a rom. strange though.
Yes but download could have been compromised somehow, it's worth a try
Sent from my HTC Sensation 4G using xda premium
well its hard to reproduce the problem , I'll pm you the video when I get the chance to film and get the problem again :good:. Thanks for the response!
Ok, I flashed something that wasn't for my sgs2 skyrocket and when I did it nothing happened, then when I rebooted it it seemed ok untill it kept freezing, no sound even on full val. I cant call because I cant here the other person and that it freezes on every app I open it takes like 2mins to open or a force close comes up. Well I have flashed back to stock using odin but still the same problem. I dont know what to do? Any thoughts about fixing this?
Sent from my samsung galaxy s2 skyrocket i727.
If you have flashed back to stock, and are still having the same issues it sounds like there may be a hardware problem. Did you do a full clean flash back to stock? (system wipe, clear the dalvik)
Sent from my SAMSUNG-SGH-I727 using xda premium
Why would you flash something not for the Skyrocket?
Wipe the phone completely, as in all data, the system, caches, and repeat that wipe three times in recovery, then power down. Go into download mode and restore to GB stock (yes, all the way back), then use Kies to do the ICS update and stay stock for a few days to make sure everything works after that.
If it's still not working after that, your hardware is jacked. Restore the thing back to GB, pull the cord out during the ICS update on Kies and finish the job. Hope you're still in warranty; if not, I hear you can get a used Captivate for $60 or so while you learn not to flash stuff for the wrong phone.
in stock recovery wipe caches and do a reset, if still a no go, install cwm, wipe caches and reset x3, reflash stock firmware with odin again, perform a reset, if still a no go then hw malfunction
Well someone's lazy...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
No I just flashed it back. But ima try that right now. Hope it this will work.
CaLLm3LAzY- said:
No I just flashed it back. But ima try that right now. Hope it this will work.
Click to expand...
Click to collapse
You just flashed it back? You're not making any sense. Post a link to the ROM you flashed or we can't help you.
I flashed the stock rom.
Okay so I am running CM10 stable on i9023. Its been fine for like a month I think with just a couple of reboots. But today I have been getting reboot whenever I turn on bluetooth. Its a very ugly situation where upon boot the phone reboots again as soon as trying to turn on bluetooth. I then clear dalvik cache and cache to make it work again. However it seems like I really am stuck now it just wont boot anymore.
I have tried clearing cache again but it still wants to turn on bluetooth and reboots. Even took out the battery for several minutes but to no avail.
My titanium backup is a bit old so please what should I do here that doesnt require data reset?
Does nandroid backup also restore those apps which were moved to SD card?? Would it even solve the situation here?
Thanks.
Okay I finally got it running again but what do I do about the bluetooth problem now? I am scared even touching bluetooth now but I really need it from time to time. :S
So everything was fine for a few hours then I decided to do a normal reboot and bam I get the bootloop again. Something has seriously got messed up I guess.
Please anyone what would you suggest me?
Do a factory reset from recovery. If that still fails, flash the factory images and see if everything works.
Sent from my Nexus S 4G using xda app-developers app
rasengan82 said:
Do a factory reset from recovery. If that still fails, flash the factory images and see if everything works.
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
Yes that's what I have decided to do.
Sent from my Nexus S using xda app-developers app
Did factory reset and everything is working fine so far including bluetooth. I just wish it doesnt happen again or I'll be really put off by CM.
Gambler_3 said:
Did factory reset and everything is working fine so far including bluetooth. I just wish it doesnt happen again or I'll be really put off by CM.
Click to expand...
Click to collapse
Had you installed something just before the problem started? I'm also on CM10 and make extensive use of bluetooth, so you just scared me
Gambler_3 said:
Did factory reset and everything is working fine so far including bluetooth. I just wish it doesnt happen again or I'll be really put off by CM.
Click to expand...
Click to collapse
How can you blame CM for that? Or any rom for that matters?
You had multiple reboots, the early ones which might have be caused by something unrelated to the rom, and the later ones something was probably corrupted. If data was being written when it rebooted on you, it's no wonder you'll have problems...
fgumo said:
Had you installed something just before the problem started? I'm also on CM10 and make extensive use of bluetooth, so you just scared me
Click to expand...
Click to collapse
Well my bluetooth is now working fine after a factory reset.
Infact yes I did install/uninstall this app a few days ago but I suppose I cant be sure about blaming it for it.
http://forum.xda-developers.com/showthread.php?t=1987032
polobunny said:
How can you blame CM for that? Or any rom for that matters?
You had multiple reboots, the early ones which might have be caused by something unrelated to the rom, and the later ones something was probably corrupted. If data was being written when it rebooted on you, it's no wonder you'll have problems...
Click to expand...
Click to collapse
It wasnt the first time CM rebooted on me, stock rom on the other hand was very stable.
And then this whole mess happens.
only had some bugs with newer nightlies.
reflashing the rom w/o factory reset did the job