ll, I am still running 4.2.5 on rooted Magic. I tried upgrading a while back but found that I had to re-flash the Navigation piece i downloaded here. For some reason it is still failing to show up, even after clearing cache and rebooting.
Am I missing something. The instability of 4.2.5 is starting to get to me...
Thanks
re wipe and re flash.
oshizzle1991 said:
re wipe and re flash.
Click to expand...
Click to collapse
Im aware that I have to re-flash everytime I get a Cyano update, but are you telling me I have WIPE as well?? May not be worth the trouble....
Im getting this error and force close on one of my Heros when I try installing any of my apps on any of the 2.1 roms. Im coming from Fresh 1.1 and following the same procedure I used on my other Hero on which the market is fully functional. Ive wiped everything over and over and cleared data on anything that looked like it at to do with the market. I also tried fix apk mismatches from recovery. Short of RUU which Id like to avoid if at all possible Ive tried everything else I can think of. In searching I have come across this error code on other android phones, but nothing on the hero and nothing specific to trying to install apps. So has anyone else seen this? And would RUU do anything a full data wipe didnt already?
Reading instructions has its benefits grasshopper...
Download the latest recovery and throw it onto your SD Card, boot into the old version of recovery and flash the new recovery as a .zip update, reboot into recovery again and then wipe your phone again, then install android 2.1, don't reboot yet, make sure your rom either has it's own custom kernal or download one for 2.1 and flash it, open up adb and clear dalvik cache and boot cache, then reboot your phone and you should load without any problems.
Thanks. But I did that from the get go. Aside from flashing a kernal, but Im running Darchtrev2 on the fully functional Hero that I mentioned and thats got a custum kernal built into the rom. So thats what I started with on the second one using the exact same process without success. Does wiping from adb do more than wiping from recovery? Thats one other thing I didnt do after the initial install.... But do understand you correctly that you have seen this specific error before?
Just bumpin the tread in hopes of finding a solution. I dont even mind gettin flamed for asking a stupid question if I could get linked up with a fix! lol I see its getting views, just no ideas I guess... It sucks cuz everything else works fine except the market. I get the list of my downloads, when I tap on one to install I the download button instead of the install button, so Ill tap on it and I get get the progress bar saying its downloading. When it gets to 100% I get the error and force close... Anyone?
I would try wiping again then flashing fresh 1.1 see if that boots and everything works ok then I would redownload the recovery and flash that still running fresh then reboot make sure everyhting is cool, then redownload whatever 2.1 rom you want and wipe and flash.
doing this serves 2 purposes
1. make sure that somewhere along the line none of the files corupted
2. if you still have the same problem then it will let you know where the problem is coming from.
just process of elimination
if you still have problems after that then I would say RUU, yes it is different than just wiping from recovery as it restores a completely stock image and gets rid of everything else. all a data wipe really does is get rid of user data.
just my opinion.
honestley thinnking about it I RUU'd my phone just for giggles then I re-rooted and then flashed DCv1 right from stock and I found that a lot of the little bugs that people where seeing I wasnt so it may not be a bad idea to ruu anyways.
Thanks for the reply and for giving me something different to try. I hadnt thought about trying that. Frustration I guess! It makes sense though. Ill give it shot. Thanks!
Why not see why it fc'd?
Adb with logcat of ...vending....
Find the syntax here: http://developer.android.com/search.html
Just an idea. It may or maynot give you the insight to fix the cause ( like a parameter ...vending... is null fetching on ).
Yeah, Ive been thinking about RUU'n too just to see if making a fresh start would make any difference, but after all the time I spent getting the one Hero working like I want on 2.1 and the troubles Ive had with the second and what Ive read about people bricking trying to RUU or flash recovery Ive been kinda hesitant....
willy900wonka said:
Why not see why it fc'd?
Adb with logcat of ...vending....
Find the syntax here: http://developer.android.com/search.html
Just an idea. It may or maynot give you the insight to fix the cause ( like a parameter ...vending... is null fetching on ).
Click to expand...
Click to collapse
Thanks. I dont know that Im quite that knowledgable though. Im sure I could read a logcat... understanding what the hell I would be reading is something else again. Saving the url though in case I need to dig deeper. Thanks for the reply.
wtphoto said:
honestley thinnking about it I RUU'd my phone just for giggles then I re-rooted and then flashed DCv1 right from stock and I found that a lot of the little bugs that people where seeing I wasnt so it may not be a bad idea to ruu anyways.
Click to expand...
Click to collapse
Sometimes it's just fun to RUU and do everything again
Alright if you're still having problems then just follow these steps:
Boot into recovery and make a nandroid back up just in case something goes wrong.
Download the latest version of your current 2.1 rom and reflash it from Recovery.
Open up adb and mount the /data directory (adb shell, mount /data)
Enter the following two commands in adb: rm -r /data/boot-cache , rm -r /data/dalvik-cache
Go Back to ADB and type the following commands: cd /data/data/com.android.vending , rm -R cache
Fix UID Mismatches using the tool in Recovery and then reboot your phone
regaw_leinad said:
Sometimes it's just fun to RUU and do everything again
Click to expand...
Click to collapse
or NOT!
Thanks again for your help all. I ended up just RUU'in . I'm with fixxer... fun isn't how I'd describe it! Anyway, I got it all working just to find out its got the mms issue now... if its not one thing its another. Oh well, something for me to work on tomorrow! Thanks again for the replies and advice.
HERNANDEZ4LIFE said:
Thanks again for your help all. I ended up just RUU'in . I'm with fixxer... fun isn't how I'd describe it! Anyway, I got it all working just to find out its got the mms issue now... if its not one thing its another. Oh well, something for me to work on tomorrow! Thanks again for the replies and advice.
Click to expand...
Click to collapse
You should have updated to the latest ruu...
wcgbmd said:
You should have updated to the latest ruu...
Click to expand...
Click to collapse
The latest RUU? I used the 1.56..... I did get it working tho. Flashed the mms. fix zip. Just wasn't expecting to have to as I didn't with my other hero. Don't know what the difference is between the two devices. Both are google branded, but the second one fought me every step of the way.
HERNANDEZ4LIFE said:
Thanks again for your help all. I ended up just RUU'in . I'm with fixxer... fun isn't how I'd describe it! Anyway, I got it all working just to find out its got the mms issue now... if its not one thing its another. Oh well, something for me to work on tomorrow! Thanks again for the replies and advice.
Click to expand...
Click to collapse
First, sorry for the bump.
I just started getting this error and wanted to know if you figured out exactly what it was so I didn't have to go through that whole RUUing process. Thanks.
don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.
boredmug said:
don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.
Click to expand...
Click to collapse
You're the bomb. That worked like a charm.
boredmug said:
don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.
Click to expand...
Click to collapse
Cant believe nobody wrote this first
boredmug said:
don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.
Click to expand...
Click to collapse
I was having the same problem on DC a couple days ago and that fixed it for me. I was reading this thread wondering why no one had mentioned it yet.
I have a problem with all 2.2.1 ROMs.
I can't install any application, neither from market nor from my sd card.
In the market when I press OK (to accept permissions) nothing happens.
When I try to install from my sd my phone stucks at "installing" screen...
I tried factory reset, format cache, wip cache/dalvik cache, fix permissions...
None of them worked. I searched for solutions but the only thing I found was to clear cache...What can I do??
ps: In older miniCM builds I didn't have that problem...
and sorry for my English, I hope you understand...
EDIT* SOLVED..
I'm not sure because i'm not a developer, but don't you need to update your baseband when your switching to newer Android custom roms?
I've met the same problem the other day,it seems that it is my not wiping my phone before i switch to newer rom that causes it.Im not sure and im not a developer,too.
@deoxx
My baseband is always 015. I mean it doesn't change... Right now I'm using racht's cm7-54 and I don't have this kind of problem...
@Rrc111
Because I didn't understand exactly what you said, you mean that I don't have to wip cache or that I have to wip cache before install the new ROM??
anant123 said:
@deoxx
My baseband is always 015. I mean it doesn't change... Right now I'm using racht's cm7-54 and I don't have this kind of problem...
@Rrc111
Because I didn't understand exactly what you said, you mean that I don't have to wip cache or that I have to wip cache before install the new ROM??
Click to expand...
Click to collapse
after installing from xrecovery, do a factory reset before restarting the phone
treebill said:
after installing from xrecovery, do a factory reset before restarting the phone
Click to expand...
Click to collapse
I tried but it didn't help...
So today i S-OFF'ed with AlphaRevX. Got cwm recovery, rooted.
Then i tried to flash CM7 without wiping and/or factory reseting (damn now i think im dumb)
Ok cwm said its finished i rebooted and now its stuck and boot animation. What now?
Sorry im new to this
Just unplug battery, boot into hboot and wipe the data, then flash CM again.
Wipe data?
nejc121 said:
Wipe data?
Click to expand...
Click to collapse
oh noes i did this, anything wrong with that?! :O
Wipe data=necessary when installing a new rom.
yeaaah
Awww yeaaaah i now have cm7 thanks!
Oh and do you need GApps for apps like market?
Yes
/tenchars.
nejc121 said:
Yes
/tenchars.
Click to expand...
Click to collapse
So i flashed GApps and market didnt appear, do i need to log on to my google account.
try putting it on the home screen by long pressing-shortcut-applications.
It didn't appear right after I flashed it, so I added it that way.
nejc121 said:
try putting it on the home screen by long pressing-shortcut-applications.
It didn't appear right after I flashed it, so I added it that way.
Click to expand...
Click to collapse
still its not there. i think i need to log in my google account but i dont have connection now.
I got the logcat here: http://paste.ubuntu.com/6076817/
The device platform is APQ8064.
PLEASE HELP ME!
lackyking said:
I got the logcat here: http://paste.ubuntu.com/6076817/
The device platform is APQ8064.
PLEASE HELP ME!
Click to expand...
Click to collapse
grab the last good nightly and flash it. push it to your device via your recovery and adb sideload.
simms22 said:
grab the last good nightly and flash it. push it to your device via your recovery and adb sideload.
Click to expand...
Click to collapse
I tried, but also stopped on the first screen of manufacture logo.
lackyking said:
I tried, but also stopped on the first screen of manufacture logo.
Click to expand...
Click to collapse
well, you can always flash the factory img, if nothing else works. did you wipe data when flashing a known good nightly?
simms22 said:
well, you can always flash the factory img, if nothing else works. did you wipe data when flashing a known good nightly?
Click to expand...
Click to collapse
Yes, I can also flash the stock rom.
but I want to solve the problem for my built rom.
and I had wiped the data & cache.
lackyking said:
Yes, I can also flash the stock rom.
but I want to solve the problem for my built rom.
and I had wiped the data & cache.
Click to expand...
Click to collapse
youre not the only one that the latest cm code isnt booting up on.. http://forum.xda-developers.com/showthread.php?t=2435980