I don't even know what I did, but my phone is basically useless now. I tried to install the PAC ROM over the summer but I got stuck ina boot loop and had to emergency reset flash back to what I thought was stock firmware using RSD Lite. I don't know if it was actually stock because when I booted up my phone, everything seemed to be in order; but then I found that the play store was not working. Whenever I opened the play store, I got the message "Unfortunately, Google Play Store has stopped." I tried a bunch of methods from here from people who had similar problems, but nothing worked so I decided it must have been the firmware that I used. So then I went and took a 4.04 firmware from the same place I got the first one and went to flash it. The flash on RSD Lite did not work. I tried a bunch of different firmwares and none of them seemed to work. And now, my phone has gotten even worse. Recently, I got a message saying that my storage space was getting low, when I could see in my settings app that it wasn't. And then, this morning, I got a message saying that storage space is too low, you will not be able to receive messages. Then about fifteen minutes later my wireless service dropped and I can't get any service now. I don't think that it is a carrier problem because I have been in the same place as I was yesterday and I was getting full 4G bars the whole time. Anybody know what I can do? I am unrooted an my bootloader is unlocked.
Have you tried Matt's utility? Option 1 I believe found here http://forum.xda-developers.com/showthread.php?t=2249773
Sent from my XT907 using xda app-developers app
indeed, mikes utility should get you back up and fully functional
Also, factory reset will help. Sounds like lots of stuff is messed up...
Sent from my XT907 using Tapatalk
Related
I'm having a problem with my Droid X using the 2.2 Froyo update. My phone was rooted using 2.1 when I updated to 2.2 and I started getting this problem. If my phone turns off then when it tries to turn back on it will get "stuck" at the Motorola logo screen. I say "stuck" because I discovered I can still use my phone, I can unlock it, open things, turn it off, it works except it only shows the boot up screen. I can get around this by leaving my battery out for several minutes, then it will boot up fine. I've already tried several things to fix my phone but nothing has worked. What I've tried so far:
Unrooting my phone
Rerooting my phone
flashing a "stock" 2.2 SBF
reset to factory defaults
I'm out of ideas except for trying to get my phone replaced by Verizon. So my question is what's left for me to try? Otherwise, will I be able to return my phone to verizon despite it being rooted at one point? Thanks in advance if anyone can help me out here.
EDIT: I noticed my phone didn't have this problem if my SD card was removed, so I tried reformatting it but that hasn't solved anything either...
Have you tried the 2.2.1 leak? This gives you a new kernel and bootloader.
Stoogie said:
I'm having a problem with my Droid X using the 2.2 Froyo update. My phone was rooted using 2.1 when I updated to 2.2 and I started getting this problem. If my phone turns off then when it tries to turn back on it will get "stuck" at the Motorola logo screen. I say "stuck" because I discovered I can still use my phone, I can unlock it, open things, turn it off, it works except it only shows the boot up screen. I can get around this by leaving my battery out for several minutes, then it will boot up fine. I've already tried several things to fix my phone but nothing has worked. What I've tried so far:
Unrooting my phone
Rerooting my phone
flashing a "stock" 2.2 SBF
reset to factory defaults
I'm out of ideas except for trying to get my phone replaced by Verizon. So my question is what's left for me to try? Otherwise, will I be able to return my phone to verizon despite it being rooted at one point? Thanks in advance if anyone can help me out here.
EDIT: I noticed my phone didn't have this problem if my SD card was removed, so I tried reformatting it but that hasn't solved anything either...
Click to expand...
Click to collapse
If the phone is not rooted when you take it into the Verizon store then you will be fine. I would ensure that any traces of root have been removed from the SD card (apps that require root, etc). As long as the phone is stock when they see it then it will be fine. I have had to do this several times with roms and root access.
Can't you just SBF it? I'm fairly new to the X but I've had to SBF rescue my D1 and D2 multiple times.
OOOPS didn't read the SBF part...
If it is still hosed after an SBF install I would guess that you have a hardware issue and need to replace the phone.
Stoogie said:
I'm having a problem with my Droid X using the 2.2 Froyo update. My phone was rooted using 2.1 when I updated to 2.2 and I started getting this problem. If my phone turns off then when it tries to turn back on it will get "stuck" at the Motorola logo screen. I say "stuck" because I discovered I can still use my phone, I can unlock it, open things, turn it off, it works except it only shows the boot up screen. I can get around this by leaving my battery out for several minutes, then it will boot up fine. I've already tried several things to fix my phone but nothing has worked. What I've tried so far:
Unrooting my phone
Rerooting my phone
flashing a "stock" 2.2 SBF
reset to factory defaults
I'm out of ideas except for trying to get my phone replaced by Verizon. So my question is what's left for me to try? Otherwise, will I be able to return my phone to verizon despite it being rooted at one point? Thanks in advance if anyone can help me out here.
EDIT: I noticed my phone didn't have this problem if my SD card was removed, so I tried reformatting it but that hasn't solved anything either...
Click to expand...
Click to collapse
It's a known issue with 2.3.15. gmanapps, the guy that created the hdmi app in the market said it was the video driver not loading up in time because of some code changes Motorola made; but supposedly it's fixed in 2.2.1. I suggest you don't upgrade to 2.2.1 until there is a full sbf.
I get stuck on the "M" logo 7 times out of 10 after every reboot; I just hold the power button down until the pop-up window comes up (of course I can't see it) and guess where the shutdown press is on the screen to power off the phone, and then power on again after a minute or two. This trick usually works.
Check it out here:
https://supportforums.motorola.com/message/256095#256095
Hello all,
I am usually a reader of this forum, first time post. I have done a search on this but I can't get it to install.
My current phone is running Froyo 2.2.1 system version 2.3.340. I have rooted it with the Z4mod root version 1.3.0.
Now, when I saw the update come down I uninstalled all my root applications and removed my root from my phone. It downloaded in no time flat. About 11 minutes yesterday morning at 9:49AM. (first attempt) And then I started the install and it shut down correctly and turned back on. When it turned back on it did what it was supposed to, had the unbox with android icon. The load bar gets to about 35% then the unbox changes to the triangle with the ! in the middle. Then it boots up Froyo and states the install failed. I attempted about 5 more times then said lets see what verizon says. This was probably the worst thing to do cause they did jack. The store I went to had 25 bricked droid X's yesterday. I was the only one to just have it fail and Froyo to work correctly. To quickly shorten this story they refused to assist in installing Gingerbread.
Any Ideas on getting it installed?
Try wiping data through stock recovery and if that doesn't work, you could try an SBF
Thank you for info. I ended up SBF'ing the phone. Says I need to re-activate the phone because there is a blue triangle next to the signal bars.
I know this is probably a repeated question but how do i re-activate the phone. Do I need to take it to Verizon?!
NVM, figured it out.
same thing happened to me. however i did not remove my z4root on froyo. install failed. did not try sbf, was hoping i wouldn't have to.
biggest reason ive found thus far amongst several different threads/ and friends with droids, root really didnt have much to do with it, as long as you were unrooted again the update went well, bloatware seemed to be the issue. myself i had uninstalled a lot of dumb memory eating stuff while i was on froyo such as the nfl and nfs games, blockbuster app so on, when i pulled the update originally it didnt detect that so it fubared me on getting the ota update. sbf the way to go, im so in love with my DX for being idiot proof atm i could dance lol
HI have search many post but feel like I am going round in circles.
I am just trying to get back to stock Froyo which the phone came with, it was bought new and unlocked from Ebay (e buyer I think).
Problem started when I noticed the phone kept freezing, pull batt, reboot, would freeze again within a few mins, guessed it must be a app playing up after an update or something.
So done a stock recovery but then it started with boot loops etc so tried wiping before and after, phone started but it would not start up wifi, done recovery again, got wifi working but then it would not open any browser. so after read lots of how to's I decided to use rsd lite and use 3.4.2 117 003 which was english retail but on loading i get checksum errors after group 33-34 and it fails.
I now only get the boot loader screen 9.10, code corrupt, batt ok, ok to program, how ever I try taking battery out putting back holding different buttons always this screen.
has this problem been solved? seen similar in other post but nothing saying it is solved
I just want back to stock and usable
Thanks in advance
Clayton
clay0001 said:
HI have search many post but feel like I am going round in circles.
I am just trying to get back to stock Froyo which the phone came with, it was bought new and unlocked from Ebay (e buyer I think).
Problem started when I noticed the phone kept freezing, pull batt, reboot, would freeze again within a few mins, guessed it must be a app playing up after an update or something.
So done a stock recovery but then it started with boot loops etc so tried wiping before and after, phone started but it would not start up wifi, done recovery again, got wifi working but then it would not open any browser. so after read lots of how to's I decided to use rsd lite and use 3.4.2 117 003 which was english retail but on loading i get checksum errors after group 33-34 and it fails.
I now only get the boot loader screen 9.10, code corrupt, batt ok, ok to program, how ever I try taking battery out putting back holding different buttons always this screen.
has this problem been solved? seen similar in other post but nothing saying it is solved
I just want back to stock and usable
Thanks in advance
Clayton
Click to expand...
Click to collapse
I don't think anything can be done except going to the service center.
clay0001 said:
HI have search many post but feel like I am going round in circles.
I am just trying to get back to stock Froyo which the phone came with, it was bought new and unlocked from Ebay (e buyer I think).
Problem started when I noticed the phone kept freezing, pull batt, reboot, would freeze again within a few mins, guessed it must be a app playing up after an update or something.
So done a stock recovery but then it started with boot loops etc so tried wiping before and after, phone started but it would not start up wifi, done recovery again, got wifi working but then it would not open any browser. so after read lots of how to's I decided to use rsd lite and use 3.4.2 117 003 which was english retail but on loading i get checksum errors after group 33-34 and it fails.
I now only get the boot loader screen 9.10, code corrupt, batt ok, ok to program, how ever I try taking battery out putting back holding different buttons always this screen.
has this problem been solved? seen similar in other post but nothing saying it is solved
I just want back to stock and usable
Thanks in advance
Clayton
Click to expand...
Click to collapse
Try dfp231 sbf. If still stuck then there is a hardware fault
Sent from my MB526 using Tapatalk 2
mb525
It has been a couple of weeks, I tried the file but it would still keep starting in BL9.10 have turned it on today to try again and it started….at press sitting there charging, connects to internet over wifi, frightened to turn off to out in sim and sd card in case it does not start again….
Will up date.
from the settings it is working on
firmware 2.2.2
kernel 2.6.32.9.ga28fcc4
bp flex usajrdnemarab1b8rtgb03a.or
built jorem_u3_3.4.2_177-3
only problem noticed is google maps force closing
thekguy said:
Try dfp231 sbf. If still stuck then there is a hardware fault
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
mb525
clay0001 said:
It has been a couple of weeks, I tried the file but it would still keep starting in BL9.10 have turned it on today to try again and it started….at press sitting there charging, connects to internet over wifi, frightened to turn off to out in sim and sd card in case it does not start again….
Will up date.
from the settings it is working on
firmware 2.2.2
kernel 2.6.32.9.ga28fcc4
bp flex usajrdnemarab1b8rtgb03a.or
built jorem_u3_3.4.2_177-3
only problem noticed is google maps force closing
Click to expand...
Click to collapse
It restarted, but did not save any blur or wifi settings, all set up again but now it force closes browser although it does connect and download gmail…phone works, sms works,
few more google processes force closing starting to worry
update
clay0001 said:
It restarted, but did not save any blur or wifi settings, all set up again but now it force closes browser although it does connect and download gmail…phone works, sms works,
few more google processes force closing starting to worry
Click to expand...
Click to collapse
still no browser, (application browser process com android.browser has stopped, please try again)
read about try to clear data by going into manage applications, I open the manage browser and it shows NO data for the app, does that mean it has not loaded correctly?
data does flow as I get gmail on both wifi and 3g
Force close after flashing only sbf? Try a system wipe, and ensure that your system partition has some free space
This looks like a eMMC problem, so if wiping doesn't work then it may not be fixable by software means
Sent from my MB526 using Tapatalk 2
please help cant get a new phon for another year and this one I almost want to throw in the garbage. Every couple of weeks i get the error saying cant establish a reliable connection for the google play store. Normally I can clear the cache and what not and clear the acount relog in and its fixed. This time nothing I could do that people suggested would help and the last option I had was to restore the phoone. So i restored the phone on the stock firmware for 4.2.2. Got the phone booted up and now my wifi is "turning on" and is stuck there. I've tried a few suggestions of reflashing stock firmware again, clearing ram, rooting the phone. and so far nothing. Please help im getting extremely frustrated and dont no what to do.
kasek55 said:
please help cant get a new phon for another year and this one I almost want to throw in the garbage. Every couple of weeks i get the error saying cant establish a reliable connection for the google play store. Normally I can clear the cache and what not and clear the acount relog in and its fixed. This time nothing I could do that people suggested would help and the last option I had was to restore the phoone. So i restored the phone on the stock firmware for 4.2.2. Got the phone booted up and now my wifi is "turning on" and is stuck there. I've tried a few suggestions of reflashing stock firmware again, clearing ram, rooting the phone. and so far nothing. Please help im getting extremely frustrated and dont no what to do.
Click to expand...
Click to collapse
aalso when i reboot it says SEandroid error for kernel... anyone no how to make that stock as well. and when i went to make a phone call i dial hit call and then screen flickers just goes black and no sound and nothing shows up only way to exit is restarting phone
If you have flashed the nb1 tar file and you still have problems I'm afraid it's a hardware problem.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If you have flashed the nb1 tar file and you still have problems I'm afraid it's a hardware problem.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
well none of those problems were there before i flashed stock firmware, which makes me wonder if its cuz im not on a stock kernel? Im not sure what you mean by nb1 file though
i flashed cyanogenmod and now its working fine
So I've been running the TEKHD 5.1 stuff for about a month now. I thought I had my model correct, it reads sm-n910t. Recently though I've had very wonky behavior. I frequently get system hanging when I turn the screen on and use apps. Yesterday, I pulled my phone from my pocket and it was at a screen similar to Odin download and was giving an error message that it couldn't read the system partition. After freaking the **** out for an hour, Odin flashing kept failing. I finally got it to take and then got installed again, booted up, and the freezing is still there, while searching through about phone, it reads sm-n910t3 so my question is, am I rocking the t3 or the t? Also could roms/kernels built for a different model give me those issues
Sent from my SM-N910T3 using Tapatalk
Install samsung phoneinfo app from playstore maybe it can help you?