Upgraded to 4.5.91 via moto-fastboot .img flashes and market has not worked since. Not sure if its the back-up restore i did or what. 1st it just wouldn't downloaded period, then i installed the new version of market and now it gives me an error at least. Thinks there is insufficient space when there is tons of it.
Since a few threads about it, none with a solution. Tried clearing data, restarting, mounting/unmounting, nothing worked.
edit:
I also unlocked with pudding today. RSDlite took a while to go to 100% while rebooting the phone, then said to boot it manually even the the phone was on. Phone itself seems fine but RSD did not say "finished". Maybe thats what caused it?
demens13 said:
Upgraded to 4.5.91 via moto-fastboot .img flashes and market has not worked since. Not sure if its the back-up restore i did or what. 1st it just wouldn't downloaded period, then i installed the new version of market and now it gives me an error at least. Thinks there is insufficient space when there is tons of it.
Since a few threads about it, none with a solution. Tried clearing data, restarting, mounting/unmounting, nothing worked.
edit:
I also unlocked with pudding today. RSDlite took a while to go to 100% while rebooting the phone, then said to boot it manually even the the phone was on. Phone itself seems fine but RSD did not say "finished". Maybe thats what caused it?
Click to expand...
Click to collapse
I had to do a factory reset on mine, and then it worked.
Gr8Danes said:
I had to do a factory reset on mine, and then it worked.
Click to expand...
Click to collapse
I seem to have fixed it with Uninstalling all the apps i restored with TitaniumBackup and then clearing the Cache from recovery. I'm guessing the 2nd step is the one the fixed it.
had same issue with market not working/downloading/installing any apps from google market. Tried to Factory Reset, but that was oddly stuck and not working (could POUND the "reset"-button but nothing was executed. Did flashing to 4.5.91 via moto-fastboot .img flash-files AGAIN. now its working *odd-headscratch*
@
clearing the cache in the recovery worked for me
Related
I used the 1 click toot method and thought I may return my fascinate. I decided against it and tried to root again with no luck. The root always has a bunch of FC's and eventually gets stuck. The generic ringer also starts with no way to stop it. Only a battery pull will restart the phone afterward. I have also already really installed the Samsung drivers for the phone. Anybody have any thoughts?
Did you go back to stock via odin...if not do so...and push root manually...instead of an app.
I did through Odin. Tried to push root manually last night. The phone froze right after the push and never recovered. Had to battery pull. I had all of the files pushed and got to the chmod and wait stage when it froze.
Hmm, maybe re push to stock in odin...make sure you are doing the correct files...though it sounds like you did...a second time around sometimes seems to hit the spot...droid used to give me the same issues with sbf.
Do a factory data reset after you redo the odin recovery. Make sure you are using the verizon file when pushing each flash and doing it in the proper order. Then manually root, dont use one click or an app.
Also remember to push the files one at a time and let the phone restart between each one booting back into download mode.
Sent from my SCH-I500 using XDA App
I've been working all weekend so I havent had too much time to deal with it. I wiped data and cache in the recovery menu initially and then the phone wouldn't allow me to sign back into my Google account. It kept telling me that I didn't have a data connection on 3g OR wifi. I finally did a factory reset through the privacy menu (not in recovery) and all seems to finally be working and completely stock. Now off to root and flash voodoo...
hey i had the same problem i made a post on how to fix it though.. go to the 0.00 internal storage issue mine was doing what u said plus more but i fixed it just follow the steps i set
http://forum.xda-developers.com/showthread.php?t=804457
Got it. Just for the record: Rooted, Flashed all three files with Odin to get "back to stock". Re-OTA'd. Somehow Busybox and Su were still there so I manually removed. Then changed my mind about returning the phone and attempted to root again with no luck. Re-flashed through Odin ok, then attempted root but errors prevented finish. Cleared data and wiped cache through recovery. Then my google account wouldn't resync b/c of network connection error, even though I had a working data connection the entire time. Tried booting into recovery and clear and wipe data again. No luck. Finally decided to use factory data reset from within settings. Now all clear, rooted again, re-synced my google account and all good. You guys rock. Thanks for the help.
My x2 doesnt seem to wont to update to gingerbread i tried to install the pre rooted gingerbread from p3 yesterday to no avail ..i tried wiping data and cache after several failed installs coming rooted 2.2 i decided to try the locked down offical update from vzw. The update always fails to install after it reboots and goes into the recovery. Upon rebooting and goin back to the homescreen the installation still fails. Any suggestions . i even tried unrooting and removing apps that required super user access and still no luck.
You need to SBF your phone back to complete stock in order to install either update. There can't be any removed system apps, or modified system files.
uhh186 said:
You need to SBF your phone back to complete stock in order to install either update. There can't be any removed system apps, or modified system files.
Click to expand...
Click to collapse
yeah do that also you understand that both versions Are exactly THE SAME XDDDDD, The only difference is the rooted one has a patch
gcforreal said:
My x2 doesnt seem to wont to update to gingerbread i tried to install the pre rooted gingerbread from p3 yesterday to no avail ..i tried wiping data and cache after several failed installs coming rooted 2.2 i decided to try the locked down offical update from vzw. The update always fails to install after it reboots and goes into the recovery. Upon rebooting and goin back to the homescreen the installation still fails. Any suggestions . i even tried unrooting and removing apps that required super user access and still no luck.
Click to expand...
Click to collapse
You are not the only one. I did a pre-emptive total defrost and factory reset before downloading the update, so everything should have been stock. The update starts to install, makes it about a fourth of the way through, then the phone reboots and tells me the update failed. After spending an hour with Verizon's tech support I finally convinced them to replace the phone, hopefully with one that already has the update installed..
God, I'm starting to hate smartphones. My old Moto KRZR never gave me this kind of trouble ... I'm seriously thinking of going back to it.
Ok, Just so I have this right. I have to reset the phone to factory settings, then update to GB. A simple unroot will not do the trick. (I tried this and the update failed)
I factory reset my wife's DX before updating to GB and had no issues.
Also as of this post it appears there is no way to root GB 2.3.3 correct?
depco164 said:
Ok, Just so I have this right. I have to reset the phone to factory settings, then update to GB. A simple unroot will not do the trick. (I tried this and the update failed)
I factory reset my wife's DX before updating to GB and had no issues.
Also as of this post it appears there is no way to root GB 2.3.3 correct?
Click to expand...
Click to collapse
Nope. Needs to be prerooted because the exploit used by gingerbreak is fixed in the update.
Go to my thread here, it explains how to install the update.
Here's what I did:
From a rooted 2.2.2 - unrooted using gingerbreak, then followed the spf tutorial.
Now back to stock with all my apps, ran the update. Installed fine.
SBF
Just do the SBF procedure listed on several threads and it will work fine. Something that has been done to your phone isn't playing nice with either update. There is virtually no difference between the updates other than the patch for root. I format and factory reset, then sbf and then wipe/data in recovery every time before I flash new roms or updates, just to eliminate any crap that might cause problems. Helps to narrow down what I need and don't need. If I forget to re-install it, I probably don't need it anyways. Good Luck. After root try the eclipse rom it pretty basic mostly just a debloat.
so you can not yet root when you do the GB update......
So I know there are few threads out there already on this topic, and i read through them, and I think my situation is a little different. I fully Factory reset my phone. I am on .173 right now, but when I go to apply the update, it downloads, reboots, installs about 25%ish, then the icon turns to the droid+exclamation inside a triangle, it reboots to home screen, and a message pops up that the install failed. I have the DRUtility 1.51. I've tried running the update with and without ROOT enabled. I've lost track of what RECOVERY mod im using/running and not sure how to find out what it is, but I think that is what is preventing the update from completeing. I've had Bootstrap installed at some point but that should be gone now since i did a factory reset. I also had clockwork mod installed at some point too. But I assume that is gone now as well due to the factory reset.
Any help would be greatly appreciated!
EDIT: Also my android version shows 2.3.6
Factory resets just clear the data on your phone. You will need to fastboot.
[TSON] said:
Factory resets just clear the data on your phone. You will need to fastboot.
Click to expand...
Click to collapse
sorry for being noob, but how do i do that and what is it? or can you point me to a thread that clarifies that?
EDIT: I found a youtube link detailing a fastboot method complete with RSD Lite 5.6.4 link and FastBoot file links. However, in the video it shows that it restores the phone to android version 2.3.5. This seems to be outdated. Will it still work for my purposes?
My issue is now resolved.
Used Droid RAZR Utility 1.51
Booted into AP Fastboot mode and used the utility to revert to .173
booted phone ran the update without issue.
Thank you mattlgroff for a great Utility.
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Thanks for the reply!
I didn't check the MD5 last night but I did just now and it matches.
I did a cache wipe the first time but not a system wipe. Then I started getting more desperate and tried reinstalling w/ system wipes and factory resets, but it didn't change anything.
No, I didn't change the ROM. Doing the Bootloader unlock exploit was about the absolute maximum of my technical abilities! The only thing I know I did wrong was that I didn't downgrade to the old boot version the first time (mainly because the wifi thing sounded inconsequential and I didn't want to learn the procedure if I didn't have to).
Anyway, I just tried Ultimate KangBang and it seems to work--no error messages so far. I don't know what I did wrong, but hopefully this keeps working!
IceDragon59 said:
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
Click to expand...
Click to collapse
andybones said:
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Click to expand...
Click to collapse
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
franklin411 said:
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
Click to expand...
Click to collapse
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
in the future it is always good practice to backup(nandroid) your current ROM. I have been burned too many times, always do a nandroid before you do anything in recovery.
your photos are normally saved to the SD, flashing ROMs or wiping the system will not delete them
andybones said:
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
Click to expand...
Click to collapse
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
franklin411 said:
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
Click to expand...
Click to collapse
na the name has nothing to do with it. it can be named whatever.
im guessing the wipe worked.
franklin411 said:
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Click to expand...
Click to collapse
weird, i was having the same problem with the same processes stopped working. i wiped cache dalvik and system but not factory reset. once i factory reset, it worked fine. i figured a system wipe would have been enough....
Ok, I have 2 Rezounds. Rooted mine, went s-off and loaded Liquidsmooth and Gaaps. Everything works fine after 1 week.
Went and did second phone (wife's) and everything seemed to go well, but I had 1 thing occur in this phone that did not happen in my phone. When in HBoot, it would constantly update and then force a restart. I couldn't get into Recovery, and my phone would not be recognized as an ADB device. Googled around and think it was something related to the PH98IMG file, so I deleted that off of my SD Card and bingo it worked.
So I flashed AICP KitKat and its Gaaps. I thought all was well until my wife tried to call someone and the screen blacked out (call was being made) and then the camera launched. We could not unfreeze the screen, even holding Pwr button - had to pull the battery.
I assumed it was the ROM, so I loaded CarbonROM - same thing.
I reset to factory, wiped everything and retried, same thing.
I restored my factory backup latest OTA (ICS), and it worked fine. I reinstalled my Amon recovery file. Rest phone again, and reloaded. Same problem - my phone screen locks up on outgoing calls.
Help..........
One thing, I assume you can flash the ROM and Gaaps back to back with no reboot. I did this, but also wiped all data and reinstalled them separately with a reboot between. Same results.
one additional item
Not sure why, but no matter how I reset or wipe, my contacts always reload. I am not selecting Google backup when going through setup screen. I have reset and wiped all cache, dalvik cache, and all other.
briggss3 said:
Not sure why, but no matter how I reset or wipe, my contacts always reload. I am not selecting Google backup when going through setup screen. I have reset and wiped all cache, dalvik cache, and all other.
Click to expand...
Click to collapse
Google will always restore your contacts, even if you uncheck the backup/restore options, they are part of your Google account.
As far as your other issues, it kind of sounds like a proximity sensor issue, try installing https://play.google.com/store/apps/details?id=com.incredicontrol.ProxSensorCalibrator&hl=en and see if you can calibrate it... although this doesn't explain the camera issue, it does explain why the screen goes blank during a call and will not come back on.
I wonder also if my HBoot was corrupted. I don't know why, but when I booted into Bootloader, it would go through the motions of updating and then prompting me to restart (no other option). I read that this was because my Bootloader was finding a PH98IMG file on the SD card - is this an update exe? So I deleted it and Bootloader worked.
Also, both phones hung up (dots) on Rumrunner "Pouring 2" phase, and I had to break the connection during this step. Rebooting showed s-off, but I reran the exe file and it went through and completed "successfully."
Is there any need to update my recovery file, currently Amon RA which i did from Scotty's Newbie Guides? I downloaded 7.2.2.2 TWRP and tried to flash it in recovery, but it says fail. I can not find instructions on doing this for newbies - only the one that references s-on users, but it just glosses over.
I'll do the Play store download and see if that works.
Thanks for your help. I am totally a novice, although I have learned alot after going through this. I read alot on the Android Forums and XDA before I post.
AmonRa could be your whole problem actually... Get TWRP 2.7.1.1 and either flash it via Fastboot, use the PH98IMG way, or try Flashify as a last resort.
The chances that your Hboot is corrupted is slim, but you can download the firmware zip from 4.5.605.14 and reflash with no issues, it will not change S-Off or unlock state.
Updated TWRP and tried the resound calibrator, still same bad result. Phone will work on the OTA recovery file (ICS), but will not work on any kitkat ROM installs. When making calls, I can not power off or anything, total loss of phone while call is active (unless I pull battery). Once call is hung up, then I get control back of the screen.
I can't seem to find anything, should I go s-on then relock and unlock it again maybe? If you think that's a good idea worth trying, let me know and I'll search for instructions on how to do that.
More I think about it, its proximity sensor issues. I replaced the glass just before rooting. I downloaded the calibration app, but can't find instructions. I will play around with that a bit and see what happens. I'll post back if I can't get that to work, I may have replaced the adhesive too close to (or touching) the sensor in the ear piece.
briggss3 said:
More I think about it, its proximity sensor issues. I replaced the glass just before rooting. I downloaded the calibration app, but can't find instructions. I will play around with that a bit and see what happens. I'll post back if I can't get that to work, I may have replaced the adhesive too close to (or touching) the sensor in the ear piece.
Click to expand...
Click to collapse
You can find more info here: http://forum.xda-developers.com/showthread.php?t=1904974