First post, hope I'm not noobing it up right away but I think I should post this here. Also, I did search with as many keywords as I could with no results pertaining to my issue.
The problems started when i rooted my recently updated fascinate (2.2 ED01). I followed the instructions on the android central site using ODIN. Everything went fine until I realized I could not get some of my apps to restore via TB. They kept failing. So i restarted the phone. All my customized screens settings, phone settings, and many of my apps were then gone. So did the root process over again, same results. So I said screw it and wiped it back to stock, rooted, then loaded it back up. Went fine for a few days until my PC would not react when I plugged in my phone. Drivers were fine, port was fine so I thought, ill restart the phone. BAD IDEA. It reverted back again.
I assume I missed a step in cleaning up after the root that is causing the phone to jump backwards after each reset.
Any Ideas?
Thanks
hugges said:
First post, hope I'm not noobing it up right away but I think I should post this here. Also, I did search with as many keywords as I could with no results pertaining to my issue.
The problems started when i rooted my recently updated fascinate (2.2 ED01). I followed the instructions on the android central site using ODIN. Everything went fine until I realized I could not get some of my apps to restore via TB. They kept failing. So i restarted the phone. All my customized screens settings, phone settings, and many of my apps were then gone. So did the root process over again, same results. So I said screw it and wiped it back to stock, rooted, then loaded it back up. Went fine for a few days until my PC would not react when I plugged in my phone. Drivers were fine, port was fine so I thought, ill restart the phone. BAD IDEA. It reverted back again.
I assume I missed a step in cleaning up after the root that is causing the phone to jump backwards after each reset.
Any Ideas?
Thanks
Click to expand...
Click to collapse
I'm betting you have zero internal memory if you look. Search on here for how to fix that and you'll be good.
Sent from my SCH-I500 using XDA App
I checked into 0 internal problem, sounds like what my problem was.
In the mean time a buddy of mine here at work put the community ROM on my phone and that seemed to get it out of the wipe loop.
Thanks for the help.
Ok, so my phone is stuck trying to install the damn OTA update even though I rejected it. It apparently self downloaded a few days later. I'm running an XDABolt ROM, can't remember which, but it's basically stock Sense just debloated. When I power the phone on, it boots up, but then power cycles a few seconds later and tries to install the update. It freezes a few seconds into the cycle. Is there anything I can do besides wiping the phone? And will wiping it even work? I neglected to do a backup in the last few weeks, and I'd rather not lose any of my changes since my last backup.
Thanks for any help.
Nevermind, I bit the bullet and just factory reset, seems to be OK now.
Thanks anyways.
I just got a CDMA Droid Razr Maxx 2 weeks ago. On day 1 I rooted and installed Safestrap 1.09 and Eclipse 1.73 (I think?). Been running that rom every day and loving it.
Well, last night my friend decided he wanted to play with my phone for a little bit and see if he wanted to upgrade to that (he's on a D1). I thought I'd switch out of Safeboot mode and back to stock because he does everything stock. No rooting, hell, no other launchers for him even. I did that and he played around with it and gave it back like 10 minutes later.
I went to toggle safemode back on and it said it failed because it couldn't copy the data back. Weird. Well, I tried a few more times, I tried selective restore of backups, etc. Booted back into stock and uninstalled and reinstalled SafeStrap. Nothing worked.
So I went home and RSD'd back to .748 using this file. It installed fine. Booted back into Safestrap, enabled safemode, worked fine. Installed Eclipse. After about 30-45 minutes of the boot animation, it finally loaded. No signal. Whatsoever.
So, a quick Google search told me that it was because I was using a version of Eclipse not compatible with my current radios. Back to stock. Checked for OTA update, there's one available. It downloads, approximately 151mb. Attempt to install: Failed.
I've tried the OTA about 4 times before downloading this file to attempt the OTA manually. But Safestrap won't install zips from the SD card except when Safeboot is enabled.
What should my next step be? Where do I go from here? I'm so frustrated, I can't even think straight.
tldr: Had Safestrap+Eclipse rom running fine, turned of safeboot and couldn't turn it back on. Fastbooted back to .748, reinstalled Eclipse, no service. Can't do OTA to 12.173
PyRo_DuDe said:
I just got a CDMA Droid Razr Maxx 2 weeks ago. On day 1 I rooted and installed Safestrap 1.09 and Eclipse 1.73 (I think?). Been running that rom every day and loving it.
Well, last night my friend decided he wanted to play with my phone for a little bit and see if he wanted to upgrade to that (he's on a D1). I thought I'd switch out of Safeboot mode and back to stock because he does everything stock. No rooting, hell, no other launchers for him even. I did that and he played around with it and gave it back like 10 minutes later.
I went to toggle safemode back on and it said it failed because it couldn't copy the data back. Weird. Well, I tried a few more times, I tried selective restore of backups, etc. Booted back into stock and uninstalled and reinstalled SafeStrap. Nothing worked.
So I went home and RSD'd back to .748 using this file. It installed fine. Booted back into Safestrap, enabled safemode, worked fine. Installed Eclipse. After about 30-45 minutes of the boot animation, it finally loaded. No signal. Whatsoever.
So, a quick Google search told me that it was because I was using a version of Eclipse not compatible with my current radios. Back to stock. Checked for OTA update, there's one available. It downloads, approximately 151mb. Attempt to install: Failed.
I've tried the OTA about 4 times before downloading this file to attempt the OTA manually. But Safestrap won't install zips from the SD card except when Safeboot is enabled.
What should my next step be? Where do I go from here? I'm so frustrated, I can't even think straight.
tldr: Had Safestrap+Eclipse rom running fine, turned of safeboot and couldn't turn it back on. Fastbooted back to .748, reinstalled Eclipse, no service. Can't do OTA to 12.173
Click to expand...
Click to collapse
Did you uninstall safestrap before you rsd'd?
Sent from my DROID RAZR using xda premium
Install .173 (next-to-latest OTA) with RSD. DroidRzr has a howto with file images.
Eclipse, last I used it, was built around .173 (not .181, the latest). I'd use that.
Check the available space for SafeStrap to store its backups. Your pal may have run you out of room.
Golden Rule: never let anyone touch your phone. If they touch your phone without permission, break all of their fingers.
The phone was working great, other than the noise cancelling mic cancelling out my voice, but I thought since the update was available, I might as well do it. Once I got on ICS I was having quite a few issues: overall slower, delay in the screen turning on, hotter battery, longer time to charge, wallpaper would flash on before the HTC screen when booting up, there were more just can't remember right now.
I hear about the Global update and think it may fix some of the problems I was having, but they got worse. Now I still have everything I did before (except maybe the hot battery) Also have 3 new issues now: the screen doesn't come back on when I take it away from my ear during a call, browser goes white when going to a new page and I have to reload the page, can't post on any forums in the browser.
Here's the process I went through getting the Global (copied from another forum that I was updating as I was going)
I downloaded it from android police, got to step 6 of the directions, looked away from the phone to see what step 7 was. The phone vibrated and is now on the screen with the green down arrow and 2 in a circle around it. Says "Updating Software from Verizon Wireless" with a green progress bar. Hope I did it right.
That went through rebooted to HBOOT, pressed vol. up twice. It checked everything. Rebooted. Pressed. Vol. up to install. Upadated everything. Pressed power to reboot.
Took a little while on the white HTC screen, now says "Andoid is upgrading..." "Optimizing application [some number] of 77." I think I did it right.
Just checked and everything is right. Woo-Hoo! Not that I'll ever use global, I was hoping it may have fixed some of the bugs I was having, but no
Also of note, I didn't pull the battery. My case is hard to get off, so I just turned off fast boot and that worked.
Click to expand...
Click to collapse
What do I do at this point? My phone is getting less usable by the day as I keep noticing all these bugs.
Wipe your phone clean and use the RUU that android police posted today to install the latest patched OTA clean. That's what I'd try anyway.
I'll try that in the morning, thanks. Hopefully all goes smoothly. Still learning how to do things (afraid of rooting, but that's another thread)
VooDooCC said:
I'll try that in the morning, thanks. Hopefully all goes smoothly. Still learning how to do things (afraid of rooting, but that's another thread)
Click to expand...
Click to collapse
There are plenty of knowledgeable members here to walk you through it if you just shoot someone a pm. It's all very simple.
As for your problem, try the ruu hopefully that works I'm not sure about the mic canceling out your voice that might be a hardware problem let's hope not
Sent from my ADR6425LVW using xda app-developers app
Stupid person time (I don't believe there are stupid questions)
By "wipe phone clean" then flash the RUU. I get the flashing part, but what do you mean by wipe clean. Is there another step in there or does it automatically happen when flashing? I've only been in recovery once, so I didn't really study the options. On my D2, there was a wipe option.
VooDooCC said:
Stupid person time (I don't believe there are stupid questions)
By "wipe phone clean" then flash the RUU. I get the flashing part, but what do you mean by wipe clean. Is there another step in there or does it automatically happen when flashing? I've only been in recovery once, so I didn't really study the options. On my D2, there was a wipe option.
Click to expand...
Click to collapse
The RUU should wipe it but you can go into recovery and wipe /data and /system to remove the current rom.
Making sure I got all this right, but won't be trying until tomorrow afternoon. Only at 40% charge and going out of town in the morning and need the phone.
1. Rename the Android Police download to PH98IMG.zip and copy to sd card (don't have to extract anything out like I did on the .1)
2. Boot into recovery (vol. down and power)
3. Let it start flashing (If it starts automatically, how do I get to the wipe /data and /cache options?) I know it should be wiped auto. but I want to do it myself to make sure.
4. Pray to Andy that there's no bugs this time.
You need to boot into bootloader, not recovery, that will happen when you do the battery pull then start it volume down + power. I'm pretty sure the RUU will wipe everything so you should be good.
Problem with newest ICS
The new ICS has a problem with the browser. Links are squirrelly when touched; sometimes
no reaction, sometimes checks every box on the page. Just does not feel right when moving
around on web pages.
Seems ok to me, I'd recommend Chrome over stock unless you need Flash support anyway.
Sorry, I got the terms confused on the terms. I knew it was vol. down and power though
I finally got around to flashing the RUU, all is well so far, will report back if anything changes.
I'm s-off but my bootloader is unlocked. Do I need to relock the bootloader before flashing the RUU.
Sent from my ADR6425LVW using xda app-developers app
There is a tradition on rezounds to always install an RUU two times in a row, then let it boot up normally before installing custom things like hboots, recoveries, or ROMs.
I used to read posts of people saying that it must be done twice to assure everything gets installed right, and to avoid problems.
So, I recommend doing the ruu twice in a row, especially if your phone was not stock beforehand.
Howard
p.s. my favorite browser is opera mobile.
If s-off and unlocked, there is no need to relock to install an RUU.
Turns out I got a little too anxious. I thought stuff was working, but that was just because I was thankful that I installed the RUU right, still new to this. Still having all the same problems though
When you say install twice in a row, should I just try installing it once again tomorrow or twice since I downloaded an app or two?
Also, you say twice, then boot up normally, when I installed this it just booted up after the install was finished. Is there a way to install it again before it boots for the first time?
method
Make sure the Android Police 3.14.605.12 renamed PH98IMG.zip on your sdCard.
Boot up with Volume down, Power to get into hboot. It will ask your permission with a
Volume up and then run the update. I think they mean after 1st boot, answer English,
and get out of setup with No and default until steady. Do a factory reset in Settings,
Storage and boot up again. Then shut her off again and restart as previously to run that
PH98IMG.zip again.
After the next boot up, insert actual information like Google etc. to start Google Play
and fetch your favorite apps. Then you're running 100% stock.
noticed the same thing with in calls. Pull the phone away from your ear and the screen should come back on, but it seems delayed. I usually have to tap the power button twice to get the screen back on.
Running simplistic 3.0 which is based on the newest leak, after flashing the leak.
FWIW I have the issue with the screen not coming back on after pulling the phone away form your ear as well, however I'm on the ICS OTA, not the global.
I never had the problem on the ICS OTA, but I also only had that for a couple of days before getting the global (.1) from Android Police.
In the process of doing the second flash. As per michaels instructions.
I went to Verizon yesterday and tried seeing about exchanging the phone, since it's having all these problems, and was told no. That it's so common and pretty much every phone has the same things, so it's considered to be working and I just have to wait on a patch. He then told me that if I wanted I could void my warranty and s-off it to go back to GB. I found that kind of odd. Then he tried pushing the Razr on me, I said no I like HTC so then he told me that the Droid 4's are having the same problems too.