Related
Sure the phone has a big screen. Yes it's easier to see things than my Wifes Dinc. No I dont think it is worth it, lets review.
All these issues/problems? happen rooted or not, or rooted without removing Bloat.
Rooted with Following Bloatware removed,
Blockbuster
City ID
Amazon
Youtube
3G hotspot
NFS
Issues........
Keyboard puts period in instead of space when typing, especially when typing fast. Had all features turned off like spell check, etc. Got so bad it would put a period in when I hit the H key or something, and I had to type real slow. Then there would be a delay in typing. I would start typing away and there would be no animation or...typing in the text box, then it would seem like the phone woke up and all of a sudden an entire sentence shows up.
Screen would not recognize touch. Could not unlock phone, could not scroll, if my finger got close to the screen it would select something and open it, but not scroll. Even though I was not touching screen. At times No response. Cleaned screen, cleaned hands. Tried clean hands, dirty hands, sweaty , etc. all same results.
Extreme slow response time. I would unlock phone, select app drawer, it would take 20 seconds before the app drawer would open, or if an app would open, or if the cursor would let me start typing, I had gone through 2 days of dealing with that BS.
Speaker. Oh this one is good...
So one day I notice the phone vibrates, yet no audio. So I check the volume, yup its up, check settings, ok all good. So I decide to play a song, its playing but just next to nothing for volume. I fiddle a bit and said Eff it, I reboot the phone. Audio is back to normal. Seems every 2 days or so I need to reboot the phone so I can hear any audio from speaker.
Random Lock ups.....
BT drops and then phone shows speakerphone button highlighted and BT button highlighted yet no audio from phone call from either BT or Speakerphone.
Unrooted bone stock with only a few apps on phone,
Same **** mentioned above.
Im tired of this. Can someone tell me what I need to do to have a stable Dx?.
Currently the phone is not rooted, and I am still experiencing issues.
I have documented these issues with the Big V as they happen, but have not done anything but order one for my wife gee looking forward to that mess, she loves to load up the apps.......
Try wiping your cache partition from recovery mode. If that doesn't work you can use the now available sbf to get your X back to factory. Now leave the bloatware alone and root again.
I agree with TF. try wiping the phone (I would suggest complete flash if possible) and see if same stuff happens.
I think you may have a bad phone. If the software reset doesn't fix it, See if VZW will exchange it. I've not had any of the problems you describe. And the fact that you are having screen/touch issues, and there was a small batch of phones with screen problems, tells me you may be one of the "lucky:
Don't have much to say, i've only had one reboot and that was bc of rogue app and i had on complete freeze but my battery was less than 10% while actually on this forum, other than that it has been smooth as butter for the most part. I came from the DInc and wouldn't switch back for anything
sent from Shawn Micheals...The heartbreak Kid
I forogt to mention I did unroot, then wipe, then left it stock, still have same issues.
oldmacnut said:
I forogt to mention I did unroot, then wipe, then left it stock, still have same issues.
Click to expand...
Click to collapse
Unfortunately, wiping (factory Reset) doesn't completely restore all of the files. As evidenced by other threads where people changed/removed some APK's and were left in a boot loop when they did a reset.
I'm still leaning towards you having a bad piece of hardware, but it would be better to rule out the software environment first. Thus, it may be worth learning how to flash the new SBF file. That should truly put your phone back in 'out of the box' condition.
To get outta the box you need to use the .sbf file then factory reset. Just using the.sbf leaves all apps and data. Have done .sbf from linux and windows with no problems.remember to *228 option 1 after to reactivate. Would give this a try then bring in for warranty if it doesn't solve it
Sent from my DROIDX using XDA App
you def have a bad phone...exchange it.
I've never had any of these problems, except for the ****ty speaker.
There is as 17+ page thread on Motos forum about the rebooting issue. I just jumped ship from Verizon and went with Sprint.
I could of handled the phone issues and waited for the 2.2 update, however working for Verizon I was in awe of the ****ty service by one particular Verizon store. On a Evo now with 2.2
Yes my phone is a beast. Much more so than the evo. I owned the DInc so yes i know EXACTLY how the evo runs. I definitely think there was an initial bad batch that went out, just like every other phone, evo and dinc, and iphone, and all the galaxy phones that went out. Im in love with this phone
sent from Shawn Micheals...The heartbreak Kid
mine works fine
Mine runs like a champ, get yours exchanged before the 30 days runs out. Simple and easy fix.
Mine is rock solid... works great... this should be a comfort to you... since all you have to do is exchange it for another one.. then you should be good!
Loving mine, glad I waited several weeks to jump on it, after the screen issues, speaker issues, I ended up getting a flawless device, speaker isnt like my tp2, but I havent missed any calls or had any issues hearing it like many others. After being burned time after time, think im gonna wait on pulling the trigger on every phone I get from now on!
this phone is definitely a beast, love it, coming from a Dinc, i have to say the X blows it out the water...
you may have a bad phone...
did u experience the issues you listed prior to rooting? if no, then theres your answer and follow the advice listed earlier about flashing the phone back
You're not by chance running a task killer set to kill everything are you?
Let me preface by saying I'm not a newb, just a newb to the Galaxy S line.
I've rooted other Samsung android phones, no problem.
The day after buying my Epic, I tried to root to use wifi tether and remove bloatware. Not interested in modding right now, as well.... this thing is blazing fast as is. Only complaint so far is of course battery life.
So, following this thread, It bricked my phone.
It successfully rooted, and I even had ADB access to SU, and my android terminal program could get SU.
I then restarted the phone after the "one click" root, and it hangs after the splash screen.
I could still get to the Recovery that was flashed, and tried a wipe of all data/cache etc. No go. The bottom 4 lights stay on, as well as the red LED. Nothing happens. I couldn't get ADB to connect. I never even had the chance to do a Nand backup. The FIRST reboot after booting, "bricked" it. The sprint 4G logo came on, then the Galaxy S splash screen, then hangs.
Took it back to BestBuy (purchased the black tie warranty as well) and the first question he asked is "Did you try and root it." I've bought 3 phones from this guy, and a crap ton of accessories for friends and family, so I was honest and said yeah, I tried. He said no worries, and gave me a new one, but I wasn't the only one to bring in a bricked phone like mine after trying to root.
SO what gives?
After purchasing the phone, there was 2 system updates. The first one downloaded and installed, and about an hour or two after that another one. Is this a patch?
The z4 root option from the market still works (the temporary option, not permanent) and with temp root I can still get WiFi tether to work, so it's not that big of a deal.
However I'm noticing some quirky things that I think a custom ROM may fix.
One: the GPS will randomly activate with no active programs on, not get a fix because I'm inside, and DRAIN the battery. I went from 80% to 17% in about an hour.
Two: The battery percentage/capacity/stats seem to be VERY unstable. I've had the phone at 60%, rebooted, then it shows like 15%. Reboot again and its back up to 50%. Very odd.
Other than that, MY GOD THIS PHONE REALLY IS EPIC. I mean, un freakin' believable. Everything I've EVER wanted from a phone.
http://forum.xda-developers.com/showthread.php?t=771590
Well you didn't actually brick it if the sprint and galaxy s things came on. Could've used odin to reset it to factory.
poor_red_neck said:
Let me preface by saying I'm not a newb, just a newb to the Galaxy S line.
I've rooted other Samsung android phones, no problem.
The day after buying my Epic, I tried to root to use wifi tether and remove bloatware. Not interested in modding right now, as well.... this thing is blazing fast as is. Only complaint so far is of course battery life.
So, following this thread, It bricked my phone.
It successfully rooted, and I even had ADB access to SU, and my android terminal program could get SU.
I then restarted the phone after the "one click" root, and it hangs after the splash screen.
I could still get to the Recovery that was flashed, and tried a wipe of all data/cache etc. No go. The bottom 4 lights stay on, as well as the red LED. Nothing happens. I couldn't get ADB to connect. I never even had the chance to do a Nand backup. The FIRST reboot after booting, "bricked" it. The sprint 4G logo came on, then the Galaxy S splash screen, then hangs.
Took it back to BestBuy (purchased the black tie warranty as well) and the first question he asked is "Did you try and root it." I've bought 3 phones from this guy, and a crap ton of accessories for friends and family, so I was honest and said yeah, I tried. He said no worries, and gave me a new one, but I wasn't the only one to bring in a bricked phone like mine after trying to root.
SO what gives?
After purchasing the phone, there was 2 system updates. The first one downloaded and installed, and about an hour or two after that another one. Is this a patch?
The z4 root option from the market still works (the temporary option, not permanent) and with temp root I can still get WiFi tether to work, so it's not that big of a deal.
However I'm noticing some quirky things that I think a custom ROM may fix.
One: the GPS will randomly activate with no active programs on, not get a fix because I'm inside, and DRAIN the battery. I went from 80% to 17% in about an hour.
Two: The battery percentage/capacity/stats seem to be VERY unstable. I've had the phone at 60%, rebooted, then it shows like 15%. Reboot again and its back up to 50%. Very odd.
Other than that, MY GOD THIS PHONE REALLY IS EPIC. I mean, un freakin' believable. Everything I've EVER wanted from a phone.
Click to expand...
Click to collapse
black screen of death. reflash stock .tar with odin. happened less than an hour after i bought mine.
LucJoe said:
http://forum.xda-developers.com/showthread.php?t=771590
Click to expand...
Click to collapse
Wow, that was helpful. Thanks.
If the vbulleting search feature didn't blow donkey balls so hard, then maybe I could find an answer. Instead all I find are generic results that happen to have the word root or brick in them, none of which applied to my scenario.
If this belongs in General, then my apologies. In the hero forum we didn't discuss rooting, or ROMs in General section. It was all in Development.
So should I just try again, or is there something I'm doing wrong? I mean how hard is it to screw up a one click root???
I'd actually be more comfortable doing it through ADB...
Try again. Make sure you use a good usb cable and you connect through the back of your computer. Restart phone and computer to be safe.
If you "brick" it again just use Odin to flash the stock tar.. you were never truly bricked!
poor_red_neck said:
Let me preface by saying I'm not a newb, just a newb to the Galaxy S line.
I've rooted other Samsung android phones, no problem.
The day after buying my Epic, I tried to root to use wifi tether and remove bloatware. Not interested in modding right now, as well.... this thing is blazing fast as is. Only complaint so far is of course battery life.
So, following this thread, It bricked my phone.
It successfully rooted, and I even had ADB access to SU, and my android terminal program could get SU.
I then restarted the phone after the "one click" root, and it hangs after the splash screen.
I could still get to the Recovery that was flashed, and tried a wipe of all data/cache etc. No go. The bottom 4 lights stay on, as well as the red LED. Nothing happens. I couldn't get ADB to connect. I never even had the chance to do a Nand backup. The FIRST reboot after booting, "bricked" it. The sprint 4G logo came on, then the Galaxy S splash screen, then hangs.
Took it back to BestBuy (purchased the black tie warranty as well) and the first question he asked is "Did you try and root it." I've bought 3 phones from this guy, and a crap ton of accessories for friends and family, so I was honest and said yeah, I tried. He said no worries, and gave me a new one, but I wasn't the only one to bring in a bricked phone like mine after trying to root.
SO what gives?
After purchasing the phone, there was 2 system updates. The first one downloaded and installed, and about an hour or two after that another one. Is this a patch?
The z4 root option from the market still works (the temporary option, not permanent) and with temp root I can still get WiFi tether to work, so it's not that big of a deal.
However I'm noticing some quirky things that I think a custom ROM may fix.
One: the GPS will randomly activate with no active programs on, not get a fix because I'm inside, and DRAIN the battery. I went from 80% to 17% in about an hour.
Two: The battery percentage/capacity/stats seem to be VERY unstable. I've had the phone at 60%, rebooted, then it shows like 15%. Reboot again and its back up to 50%. Very odd.
Other than that, MY GOD THIS PHONE REALLY IS EPIC. I mean, un freakin' believable. Everything I've EVER wanted from a phone.
Click to expand...
Click to collapse
Lol. Agree. I screamed and yelled at htc ppcs cuz they lack 3d gpu power.and cripple features on their hsndsets. Now im a samsung costumer for life. Even faster than iphone 4. Love it!
Sent from my SPH-D700 using Tapatalk
Try the drockstar all in one root v2.01, worked like a charm for me rerooting the other day. Had some issues with the one click the first time awhile ago.
You didn't really brick your phone. Hold 1 when you power up to enter download mode. Make sure you firewall and antivirus are disabled, odin wouldn't work with my Norton AV. Then you can always flash the stock D18 through Odin.
You should root asap. Like they said you can allways flash to stock if something happens instead of returning the phone. I remember I used to use my phone all day connected to a power supply. Now I don't have to do it with the syndicate rom and my phone is even faster.
Sent from my SPH-D700 using XDA App
You didnt brick your phone. I have had that screen hang for 6-7 minutes many of times after rooting or flashing. Because that is when your kernel and files get rebuilt at that splash screen so it is really slow and feels like forever but it will boot. If not battery pull and try to boot again or use odin.
poor_red_neck said:
Let me preface by saying I'm not a newb, just a newb to the Galaxy S line.
I've rooted other Samsung android phones, no problem.
The day after buying my Epic, I tried to root to use wifi tether and remove bloatware. Not interested in modding right now, as well.... this thing is blazing fast as is. Only complaint so far is of course battery life.
So, following this thread, It bricked my phone.
It successfully rooted, and I even had ADB access to SU, and my android terminal program could get SU.
I then restarted the phone after the "one click" root, and it hangs after the splash screen.
I could still get to the Recovery that was flashed, and tried a wipe of all data/cache etc. No go. The bottom 4 lights stay on, as well as the red LED. Nothing happens. I couldn't get ADB to connect. I never even had the chance to do a Nand backup. The FIRST reboot after booting, "bricked" it. The sprint 4G logo came on, then the Galaxy S splash screen, then hangs.
Took it back to BestBuy (purchased the black tie warranty as well) and the first question he asked is "Did you try and root it." I've bought 3 phones from this guy, and a crap ton of accessories for friends and family, so I was honest and said yeah, I tried. He said no worries, and gave me a new one, but I wasn't the only one to bring in a bricked phone like mine after trying to root.
SO what gives?
After purchasing the phone, there was 2 system updates. The first one downloaded and installed, and about an hour or two after that another one. Is this a patch?
The z4 root option from the market still works (the temporary option, not permanent) and with temp root I can still get WiFi tether to work, so it's not that big of a deal.
However I'm noticing some quirky things that I think a custom ROM may fix.
One: the GPS will randomly activate with no active programs on, not get a fix because I'm inside, and DRAIN the battery. I went from 80% to 17% in about an hour.
Two: The battery percentage/capacity/stats seem to be VERY unstable. I've had the phone at 60%, rebooted, then it shows like 15%. Reboot again and its back up to 50%. Very odd.
Other than that, MY GOD THIS PHONE REALLY IS EPIC. I mean, un freakin' believable. Everything I've EVER wanted from a phone.
Click to expand...
Click to collapse
Well 1st things 1st. Your phone WAS NOT BRICKED!!! All you had to do was use Odin to flash your phone back to stock! If you would have done your homework, you woulda known that! But you didnt! Cuz your too freakin LAZY to READ!!!! A EPIC CONNOT BE BRICKED UNLESS YOUR A IDIOT!!!!
@OP
Hey man, did you try this procedure?
http://forum.xda-developers.com/showthread.php?t=773032&highlight=revert+stock
Good luck and don't give up on it!
It is fully possible to Brick an Epic... a fair amount of idiocy is involved though.
Epic Experience 1.2.0.9/Phoenix 1.49s/Elegant Steel .21
Damn, I always rush into these topics thinking someone bricked their phone, but turns out most of the time it's just someone else misusing that word
sniperkill said:
Well 1st things 1st. Your phone WAS NOT BRICKED!!! All you had to do was use Odin to flash your phone back to stock! If you would have done your homework, you woulda known that! But you didnt! Cuz your too freakin LAZY to READ!!!! A EPIC CONNOT BE BRICKED UNLESS YOUR A IDIOT!!!!
Click to expand...
Click to collapse
Should I release the angry grand wizard kkk silverback gorilla on him? Lol.
Sent from my SPH-D700 using Tapatalk
If I use the current version of VISIONary (r14) and ONLY temp-root my MT4G, will ANY residual effects be left once I reboot?
I remember when using VISIONary on my MT3G, it seemed to cause permanent changes even though I only used "temp" root.. eventually my phone seemed to have conflicts with apps and it never really "unrooted"
It's my understanding that VISIONary should be completely safe as it does not write to the system partition..?
Please move this to q&a......
From my don't talk about changelog CM7 Glacier
Anyone?? Need some advice here.
$pitacular1 said:
Anyone?? Need some advice here.
Click to expand...
Click to collapse
VISIONary.apk was designed to only be used on the HTC Vision and the HTC Glacier.
Nandroot was designed to be use on the HTC Magic and HTC Dream. and later came the desktop client SuperOneClick.
If i didn't know any better the reason your Magic went FUBAR is because you used the wrong method and installed something that didn't belong.
But to answer your question my wife's phone is temp rooted with VISIONary.apk and she has had zero usability problems after a reboot.
neidlinger said:
VISIONary.apk was designed to only be used on the HTC Vision and the HTC Glacier.
Nandroot was designed to be use on the HTC Magic and HTC Dream. and later came the desktop client SuperOneClick.
If i didn't know any better the reason your Magic went FUBAR is because you used the wrong method and installed something that didn't belong.
But to answer your question my wife's phone is temp rooted with VISIONary.apk and she has had zero usability problems after a reboot.
Click to expand...
Click to collapse
In the modaco forum I read earlier today that someone was having constant reboots from using VISIONary for temp root.
You said your wife's phone "had zero usability problems after a reboot". What about after temp-rooting, but before rebooting? Any issues there?
$pitacular1 said:
In the modaco forum I read earlier today that someone was having constant reboots from using VISIONary for temp root.
You said your wife's phone "had zero usability problems after a reboot". What about after temp-rooting, but before rebooting? Any issues there?
Click to expand...
Click to collapse
Nope she uses it all day everyday.
Thank you, much appreciated.
Temp-Root here I come!
Btw, is she using the latest version (r14) ?
Noticed no problems
I've seen no problems after a reboot with Visionary r14. On another point, I had it originally set to automatically temproot after every reboot, but once I discovered that the programs that Titanium Pro freezes stay frozen after a reboot even if you're not temprooted, I no longer temproot. Have to use it, though, if I want to add/subtract frozen programs.
ecdy said:
I've seen no problems after a reboot with Visionary r14. On another point, I had it originally set to automatically temproot after every reboot, but once I discovered that the programs that Titanium Pro freezes stay frozen after a reboot even if you're not temprooted, I no longer temproot. Have to use it, though, if I want to add/subtract frozen programs.
Click to expand...
Click to collapse
I wonder if that's normal. It was residual root-like effects like that I was wondering about.
neidlinger said:
VISIONary.apk was designed to only be used on the HTC Vision and the HTC Glacier.
Nandroot was designed to be use on the HTC Magic and HTC Dream. and later came the desktop client SuperOneClick.
If i didn't know any better the reason your Magic went FUBAR is because you used the wrong method and installed something that didn't belong.
But to answer your question my wife's phone is temp rooted with VISIONary.apk and she has had zero usability problems after a reboot.
Click to expand...
Click to collapse
On another note, I had previously experimented on my MT3G with Universal Androot which worked perfectly.. it was only later after the 2.2 update that I needed a root alternative as they had patched the exploits Universal Androot used to get root.. VISIONary was a perfect solution. The only problem is it resulted a permanent "partial" root instead of a temporary root or a full perm root. It was still an excellent tool to use for the job though.. nothing went "FUBAR" lol I was still able to SAPPIMG and then manually update to the official Froyo.
I was just curious if I was going to get the same perm root issue with the MT4G, as I have not yet familiarized myself with the process of restoring the 4G to stock although I am aware of PD15IMG.. just haven't read through the specifics. I swear I'm not a total noob I promise.. I've written tutorials on root for the MT3G
Ok, so last night I used VISIONary for temp root only..
Immediately after temp rooting, my phone started acting weird.. syncing extra long, everything was slow (even after the syncing).. it just seemed to be severly affecting the performance of my device.
I don't know if perhaps I have an active app it was having issues working with or what, all I know is without temp root my phone flies 24-7.
Once I rebooted, everything went back to normal. Don't think I'll be using VISIONary anymore
$pitacular1 said:
Ok, so last night I used VISIONary for temp root only..
Immediately after temp rooting, my phone started acting weird.. syncing extra long, everything was slow (even after the syncing).. it just seemed to be severly affecting the performance of my device.
I don't know if perhaps I have an active app it was having issues working with or what, all I know is without temp root my phone flies 24-7.
Once I rebooted, everything went back to normal. Don't think I'll be using VISIONary anymore
Click to expand...
Click to collapse
i guess you are one in a million who have experienced problems with VISIONary.apk.
I guess if you are that bent on rooting you can do it the old fashioned way.
neidlinger said:
i guess you are one in a million who have experienced problems with VISIONary.apk.
I guess if you are that bent on rooting you can do it the old fashioned way.
Click to expand...
Click to collapse
Well last night when I first tried it, I had not enabled USB debugging..
So this morning, I tried it again, but made sure it was enabled the FIRST time lol..
and it's working flawlessly. I guess my initial idiocy caused something.. but it's fine now!
$pitacular1 said:
Well last night when I first tried it, I had not enabled USB debugging..
So this morning, I tried it again, but made sure it was enabled the FIRST time lol..
and it's working flawlessly. I guess my initial idiocy caused something.. but it's fine now!
Click to expand...
Click to collapse
That's cool. Glad to hear it is working.
Looking for some advice/help. I got my wife the Evo Shift a couple of weeks ago. Her phone has not been rooted and other than a few added apps the phone is completely stock. The phone reboots on her 4 and 5 times a day. She does not have any kind of task killer installed so that's not it. She plays Angry Birds a lot and uses Pandora quite a bit. I have also installed Sound Manager for her. Other than that I can't think of anything that would be helpful for trouble shooting. I have searched here and through Google and have not seen any info of others having this problem. I am not sure if I should root the thing or return it to best buy. I have the Evo and previously the Hero and am no stranger to rooting or custom ROMs. Just really did not see the need to root it since my wife has no idea about any of that. Any help or advice will be appreciated.
Thanks.
root and install nfinitefx's or mik's rom; you'll have less trouble than if it was stock.
danaff37 said:
root and install nfinitefx's or mik's rom; you'll have less trouble than if it was stock.
Click to expand...
Click to collapse
That's what I was thinking. I am a little worried its a hardware problem though. I guess I could always flash back to stock and return it if that doesn't fix it.
hell return it ya got nothing to lose but a headache
Did you try a factory reset?
Sent from my PG06100 using XDA App
JKILO said:
Did you try a factory reset?
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Not yet. I did get some more info from my wife though. It only happens when she is at work. And she says she get some sort of "radio error". I'm starting to think it might have something to do with the building she is in. She had my hero for a couple months before I got her the shift and had no problems. It had CM 6.1 running though.
hauntedchild said:
Not yet. I did get some more info from my wife though. It only happens when she is at work. And she says she get some sort of "radio error". I'm starting to think it might have something to do with the building she is in. She had my hero for a couple months before I got her the shift and had no problems. It had CM 6.1 running though.
Click to expand...
Click to collapse
im running mine stock and rooted and dont have any problems with reboots. sounds like a app is probably screwing something up
i had a similar problem with one of the streaming media apps i used to use a month or so ago i cant remember the name but for some reason if i lost signal it would crash the phone and need to be rebooted
i took it off and installed tuneinradio and it worked better anyways
My shift was rebooting itself 3 to 4 times a day, I just rooted it and it seemed to stop rebooting itself for a day. Now its starting to reboot itself again, but not as often.
I am almost convinced its a hardware problem. Sounds too rare to be anything else. Maybe bad memory or something.
Sent from my PC36100 using Tapatalk
I had a freezing issue with my phone which people suggested possible due to pandora and bluetooth. Perhaps you have the same issue?
Anyway, try to find "bluetooth for automotive" settings for pandora and turn it off.
I wouldn't recommend rooting your phone if you think its broken. You might just end up breaking it further and render your warranty void.
If you can't fix it, get sprint to replace it.
i dont need a signature
This may be resolved by now, but I got my shift previously used. When I first activated it, I was getting some radio errors and I could not make calls or send sms messages, but the email worked fine. I contacted Sprint customer service via chat from the website and they did something from their end to fix it. I had to turn off my phone and she said now wait till I tell you to turn it back on. I waited 5 minutes and when I turned it back on, everything was fine. So I would take it in or contact Sprint and see what they say. As for not sure if you wanna root it for her, I would definitely recommened it, she doesn't have to take advantage of all the advanced tweak that some use but it will just make the phone a lot smoother and easier to use. IMHO.
Sent from my PG06100 using XDA App
Michael61182 said:
This may be resolved by now, but I got my shift previously used. When I first activated it, I was getting some radio errors and I could not make calls or send sms messages, but the email worked fine. I contacted Sprint customer service via chat from the website and they did something from their end to fix it. I had to turn off my phone and she said now wait till I tell you to turn it back on. I waited 5 minutes and when I turned it back on, everything was fine. So I would take it in or contact Sprint and see what they say. As for not sure if you wanna root it for her, I would definitely recommened it, she doesn't have to take advantage of all the advanced tweak that some use but it will just make the phone a lot smoother and easier to use. IMHO.
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Thanks for the input. I think I'm going to go ahead and root it. After keeping an eye on the situation its seems its only happening when she is at work. I can't imagine it will fix it but I think its worth a shot.
I think I fixed mine. I tried to use navigation and it kept force closing, that was strange because I've used it before with no problems. I googled around and found some info that if you had another text to speak engine in your phone then uninstalled it without setting it back to pico as default it would cause nav to FC, which is what I had done. So I set it back and checked "Always use my settings" in the Voice section of settings, nav started working and the reboot issue went away for the past 7 days.
I don't really know crap about phones and most tech stuff for that matter (heck 99% of what is said in these forums goes over my head) but I think why this fixed it is either nav or some app was trying to use pico or something and when it couldn't the phone would get an error and reboot itself. I may be wrong (probably am) but maybe she deleted something or changed a setting some app needs and that is causing her problem. Hope this helps in someway or at least gives you another direction to start checking.
Here's how I bricked my phone, for the ones who're interested:
I think it's a pretty funny story, so keep reading if you're searching for some entertaining story.
So I Bought a flipout because I wanted a small phone. I was pretty satisfied by the phone and it's performance, althought it's kinda an effeminate phone. Anyways, before I knew it (When I booted up the phone for the first time) I was disgusted by Orange's laggy intro: it was supposed to be an explosion followed by an implosion which created the Orange logo (sort of XBOX style). The reality was less: a very laggy 2 or 3 fps intro. Bravo Orange if you were actually aiming for this rate.
When I boot up the phone it shows the menu just like any other phone, but it came with another disgusting fact: MotoBlur. Lag, lag and lag. There it was, in all it's glory:
- It's laggy (not as much as Orange's intro...)
- Uses default services (calendar, gallery) with some unfinished 3D features (that caused needless lag)
- "Happenings" which connects your twitter, facebook and other things.
Although I have to say, I did like the lil tab that shows above and tells you on which screen you were. It looks kinda like the following (excuse me my drawing skills):
.: : . |^| . : :.
resp. -3 -2 -1 0 +1 +2 +3
Anyways, I had to get rid of this "MotoBlur" and the first thing I had to do was to root my device. I remember the days with the G1 which were a hassle to just root your phone, so I was hesitating if I really wanted to go through all this again...
But after a lil search, I found that nowadays we have superoneclick, androot, z4root, etc... etc... So I tried one of these "new" apk's which gave me a small error, so then I tried z4root which was quite easy, fast and simple. I was in. Things were going my way, hell, I even found a brand-new-looking 4GB microSD on my work. Just out of nowhere there it was, very small, laying down on the ground waiting for me to get picked up.
What goes up, must go down...
So there I was with my first steps trying to remove MotoBlur, and although I knew there were tut's about how to remove Orange and Blur, I just couldnt wait. I made backups of my system apk's with Titanium which was quite easy, and it was that precise moment when I was like "GET!", i'm sick of this MotoBlur, let's remove these "things". They are right in front of me, just get rid of them... And while continuously hitting the "remove" button I was daydreaming of a simple usefull handy phone. Bam, bam, bam, I deleted one app after the other, even Google Talk didn't had a chance. Everything was going smooth, bye Blur.Calendar.apk, bye odex, bye Blur.gallery.apk, bye Blur.happenings.apk,... ... ... about 20 apk's later, I was quite satisfied.
But you know how it goes when you just delete stuff without greater knowledge. You BRICK your phone. But people, this was just the start. I had some force close after this one man operation, but my phone was smoother. I have to admit, things were comming unexpected. First I couldnt find my gallery (removed). Then I found out I couldnt download anymore from the Android Market because I deleted Blur.calendar.apk which is connected with Calendar.apk which syncs my G-Mail account which is needed before you can download anything from the Market. Hah! Owned.
Backups.
So there I was having these problems, but the phone still works great. I have to admit I silently thought: luckely I made a backup, and was kinda proud I wasn't one of those noobs who just goes forward without a save game, right? Right? Guys...? Anyone...? . ... ...Wrong! The reality was I couldn't even "restore" with Titanium. The backups weren't real backups, but just data-backups which were stored on my sdcard in .tar format. Aaarrgh!
No problem, no problem. There has to be a way to fix this, someone did this stupidity before me. Obviously. Ofcourse. No?
When I was searching about why I couldn't fix my Titanium backups, someone answered to someone else that's because he couldn't sideload the apps. He needs to root his phone in a way so sideloading is enabled. Great! Sideloading it will be then.
Sideloading is def a great way to install .apk's without the market, because I tried a factory reset (hoping that would solve everything) and I couldn't download anymore from the market. I had to sideload ASTRO which was successful with the right ADB drivers - even though I didn't knew what ADB meant I did register on MotoDev's website (so I can download the little bastard).
Easy peasy. Now I'm back on track with ASTRO and an easy install of Flan Gallery (fixed camera) replaced my gallery. We're off to set!
Despite this minor victory I was aware I'm still not were I wanted to be. Factory reset doesn't get me were I want to be and I'm still having issues. But no problem no problem. This time I'll turn my questions to the community, not google. That's eventually why there is a community? That's why we are open source? Yes. Score. Win.
So maybe some knowledgeable people will reply because they can help the ones who are trying to learn. I think I'll start with how to fix the calendar-issue and then I'll try to make a ROM-backup, so I can install a new ROM or whatever. That's probably a better idea then before. Cool, I even got a quick reply by someone who told me to go to this-and-this site, which is better for noobs. Allrighty then...
Trying my own way.
Since things weren't going were I wanted to, I thought now it's time to give it a real last try by searching about this mystery "ADB" and eventually to push some apps into system/app/ so I could fix all this misery. I found what I was searching for, however the tut about how to push apps sounded like someone was holding a gun against the writer's head. It really sounded like he wrote it against his will.
Desperate attempts.
I started today (15 april) around 5pm local time with this whole pushing-thing because I thought I had the knowledge that I needed and even surprised myself by actually successfuly pushing some apk's using a quick and nice XDA how-to, but then things went from worse to worser. I pushed Blur.calendar.apk, Blur.service.apk, Blur.email.apk, Blur, Blur, Blur... Ironically thát what I wanted to remove at the start came voluntary back in my system/app/ of my phone.
That's quite funny especially when I rebooted my phone and I kept getting force close com.motorola.blur.service.main and I couldn't get around this except by using voice-commands (double tap home button). "Find ASTRO" I said. Finding ASTRO... Opening ASTRO... Ingenious! It was quite amazing that this feature actually works without any bugs or misunderstandings. So I started root manager, rebooted the system with r/w settings so I can try a final attempt by trying to remove blur-service.apk from the system/app/ which actually didn't had any impact. Nothing really happened.
The end.
And there I was having these problems, and the phone doesn't work. A friend of me adviced me on Steam-chat to hard-reset the phone. I could care less, but we had a little discussion about what has more effect hard-reset or factory-reset? Btw... Holding down the power button and the camera button...?! The phone doesn't even has a camera button! Hilarious.
I eventually did the hard-reset with another tut and now the phone is... ehm... kinda... pretty... bricked. It just boots up and then gives 1 continously looping force close of the blur service (which I allready had), and another force close when I finish setting up the blur account wizard. At the end of the wizard it just force close and shows the wizard again,... and again... and again...
Mathematical summon:
+1 noob
+1 bricked phone
- $$$
- (a lot of) time
+ frustrations/stress
+1 story
Equals a possitive outcome?
i've not rooted my Flipout as it seems there's not much you can do with a rooted one anyway
but I've done bad flashes before...many times
and i've always been able to rescue those phones by flashing the original rom. just wondering if this might be an option for you..
See if you can flash that device using RSDLite, I can see some tuts in this board that features this, likely that debranding guide. Hold up+power when it's off and boot into flash mode, not camera+power
A brick = a dead phone, no boot, no flicker, nothing. If it acts like a brick it's a brick, otherwise it's just a messed up phone. I'm sure you'll be able to recover yours...
Sent from my HTC HD2 using XDA Premium App
Moto phone + rsdlite + flipout sbf= fixed phone. Just find those two things and you can restore your phone back to fresh out of the box state again. Promise.
Sent from my SGH-I897 using Tapatalk
Yeap i just did it first try hold "up" button on the keyboard + power for 4 sec then plug usb. in flex options i checked everything and it all went god then