Database Develop

Camera and camcorder force close after upgrading to Cyanogen 4.2.12.2

Just today I upgraded to the latest Cyanogen release (4.2.12.2) on my G1 from pre-4.1.99, and any time I attempt to open either the Camera or Camcorder, it Force Closes, and returns me to the home screen.
I've tried cleaing the cache/data for both the Camera and Camcorder, but that didn't appear to fix the issue. I've also run the fix_permissions command as well, which didn't help either.
Any ideas on what might help fix this problem?

run fix_permissions from console... and post in correct section next time

I apologize for having posted this in the wrong section - where does it belong?
Also, I stated in my OP that I ran the fix_permissions command; from the console was implied.

In the 4.2.12.2 thread.

Thread Moved to Q&A.

I just tried two things: first just wiping and flashing the Cyan Rom again, and that didn't fix it.
Then, I wiped, installed the 1.6 base rom, and then Cyan Rom on top of that, and I still get Force Closes for both the camera and camcorder.
So, I'm still stuck. Any more ideas?

Do you have any apps that use camera (Google Goggles, Barcode Scanner, etc)? You may have to wipe data from those as well.
Also, do you have apps2sd? If so, wiping is not as effective as it is without it. If you do apps2sd then you need to run this from terminal
Code:
su
rm -r system/sd/dalvik-cache/*
reboot
Good luck.

borodin1 said:
Do you have any apps that use camera (Google Goggles, Barcode Scanner, etc)? You may have to wipe data from those as well.
Also, do you have apps2sd? If so, wiping is not as effective as it is without it. If you do apps2sd then you need to run this from terminal
Code:
su
rm -r system/sd/dalvik-cache/*
reboot
Good luck.
Click to expand...
Click to collapse
I tried running these commands in the Terminal Emulator, and after the reboot, I still get FCs when trying to open the Camcorder and Camera.
I collected the log, and have attached what I believe to be the relevant portion of it to this message.
Any more ideas?

same here!!!
I am having the exact same issue as you show in the log file
have had some success in reflashing base rom but it only works for a day or so (or hours in some cases)
believe it to be an issue with the drivers but something is killing the camera every time
have removed all apps and reflashed but now it just keeps fc
if any of the devs working on camera issues could have a look please help
cheers
j.

Same thing here.

Same problem here, sucks.

Same HEre 2 =[

Androiid=D said:
Same HEre 2 =[
Click to expand...
Click to collapse
same here, and I tried:
going back to 4.2.8 (where camera last worked for me, before going straight to 4.2.13),
I tried wiping,
I tried removing and and re-making the ext3 partition
I tried reflashing the radio (2.22.19.26I from http://code.google.com/p/sapphire-port-dream/)
My camera is still dead (force closes)

If you have the same issue (camera force closing, flashing older OS not fixing the issue), PLEASE go to Cyanogenmod project Google Code website and click the star next to "Vote for this issue and get email change notifications" on the bottom of the page. You have to be signed into your Google account.
Voting for this issue will raise it's priority (crucial, as it seems to affect a small number of units so far, but it's a show stopper).
Cyanogenmod project Google Code website:
http://code.google.com/p/cyanogenmod/issues/detail?id=1037
Thanks!
Blaz

Much respect for Cyanogen and all he does for further the HTC Dream: G1 community.
However, if you are having so many issues maybe its time to change to
another Rom altogether. Just my 2 cents..

legend221 said:
Much respect for Cyanogen and all he does for further the HTC Dream: G1 community.
However, if you are having so many issues maybe its time to change to
another Rom altogether. Just my 2 cents..
Click to expand...
Click to collapse
Ummm, I've only one issue: camera not working. Thanks for the pennies tho

blazzr said:
Ummm, I've only one issue: camera not working. Thanks for the pennies tho
Click to expand...
Click to collapse
Here's a few more pennies my good man, if the camera is a deal breaker then consider my above comment and change Rom.
Your choice, that's why this community should never go away.
Freedom to customize as you see necessary and fit is the ultimate reward.

legend221 said:
Here's a few more pennies my good man, if the camera is a deal breaker then consider my above comment and change Rom.
Your choice, that's why this community should never go away.
Freedom to customize as you see necessary and fit is the ultimate reward.
Click to expand...
Click to collapse
have tried other roms but i still get the force close so not really a cyan problem methinks

cqms13 said:
have tried other roms but i still get the force close so not really a cyan problem methinks
Click to expand...
Click to collapse
I too a while back had problems installing roms and constantly seeing FCs on my phone. .
The way I fixed that problem was using a bigger/better/faster microSD card I already had.
( @Cqms: I see you already have a newer microSD however, perhaps formatting it after backing up your contents first suits you and then copying everything back once finished. Finally wipe completely/flash Rom and you're set).
Formatted it fat32, since I copied my data on the pc first I copied what I had to the new one.
And finally installed what in my opinion to be one of the best Roms (see my signature) through the wipe/flash procedure and have been extremely happy since.

Camera is back (sort of!!)
Ok as suggested by Legend in above post - wiped formatted etc and flashed super D ROM
Camera comes back but has some kinda solarisation effect which I cant seem to get rid off.
Added to this is my contacts and dialer keep fC ing on me so this ROM is a non runner for me even with a semi working camera
getting closer to the fix though
maybe ima try reflashing cyanogens latest again and see if i can sort the weird effect on the camera
heres hoping
j.

[Q] nexus one cyan mod problem - big one for me

hey guys, new to rooting my device. always been heavy into customization and seen alot of work on here for cyanogen mod. so - went ahead and did the one click root. worked fine, checked with superuser permissions, and rom manager. downloaded cm 6.0.0 stable. "flashed" that rom onto my device, and it asked me to reboot to take effect. so hit reboot. and it is now stuck on the startup boot logo for cm6 with the blue android with the circle around the edge (im sure you all know what im on about) having a look about cant seem to see anybody else with this problem.
heres hoping somebody will help me out, hopefully make me look like a prat and tell me its something really simple and easy to do. beacuse im not liking my phone right now at all :/

Boot into recovery, wipe the device, then reflash the rom.

okay, after having a play i've got it to boot into cm6.0.0 with google addon, however it now says there is no internet connection. anybody?

wiggey1337 said:
hey guys, new to rooting my device. always been heavy into customization and seen alot of work on here for cyanogen mod. so - went ahead and did the one click root. worked fine, checked with superuser permissions, and rom manager. downloaded cm 6.0.0 stable. "flashed" that rom onto my device, and it asked me to reboot to take effect. so hit reboot. and it is now stuck on the startup boot logo for cm6 with the blue android with the circle around the edge (im sure you all know what im on about) having a look about cant seem to see anybody else with this problem.
heres hoping somebody will help me out, hopefully make me look like a prat and tell me its something really simple and easy to do. beacuse im not liking my phone right now at all :/
Click to expand...
Click to collapse
Stick to stock rom, CM6 kills your battery within a day, half a day if you are a heavy user. I am a lot into customization too but after moving to cm6 I moved back to stock within a week. I think your phone is hinting to you not to install cm6

i didnt know cm6 did that to be fair brother. however, that doesnt solve my problem at the moment. if i find i cant live with it, then ill reset back to stock or a different rom, but at the moment my main priority is to get access to my internet again for the time being whilst i look into different roms

Mine did the same thing. I just waited and within 5 to 10 minutes my phone started and I was able to use it.
Sent from my Nexus One using XDA App

wiggey1337 said:
okay, after having a play i've got it to boot into cm6.0.0 with google addon, however it now says there is no internet connection. anybody?
Click to expand...
Click to collapse
Have you inserted the appropriate APN settings? Are you talkin about 3G or WIFI?

Enter/select the correct APNs for your carrier.

ROM Manager does not Work

ROM Manager just does not work.
................... So mad anybody buys this program it installs Clockwork Boot Partition but IT DOES NOT ALLOW TO UNINSTALL !!!! This is like a virus.
To make matter worse the program just does not work.
Download any RON from ROM Manager it boots to Clockwork Recovery "the virus" and just sits the with the clockwork Android/exclamation.
Clockwork does not answer emails.
Their Forum is full of people that like me are kind of nobbish and very mad that you can not restore the normal android partition.
Two questions anybody have any clue why the program does not work for me?
Failing that how to uninstall revert back to normal Nexus One configuration?
I seen somewhere where somebody says you download a file.
Run some commands from somewhere??? not sure where. I think if you find the the Android ADK you can connect you Nexus One to a computer, turn on some sort of terminal emulator "how?", type these commands from a promote in this emulator. THEY SAY THIS IS EASY ???
You know I live in Toronto I would pay somebody to revert my N1 to stock and not go through the hassle.
All this rooting stuff maybe nice, Titanium Back up, Shoot me, "Cool ROMs which I can not install with ROM Manager" but the education curve is not worth it in my book.

Did you click "flash clockwork recovery" at the top of the program?

pwig said:
Did you click "flash clockwork recovery" at the top of the program?
Click to expand...
Click to collapse
I did but it still does not work. Oh well tried to load CyanogenMod 6.0.0 said there was an error in recovery and it did not work.

pwig said:
Did you click "flash clockwork recovery" at the top of the program?
Click to expand...
Click to collapse
I did but it still does not work. Oh well tried to load CyanogenMod 6.0.0 said there was an error in recovery and it did not work got the exclamation android again

Did you flash anything? Or just root and install Rom Manager?

Here are the steps......
Made sure I was rooted, ran a few apps that require root permissions.
Ran ROM Manager,
Flashed the latest Clockmod Recovery
Select Download ROM
Selected CyanogenMod 6.0.0 "I know it work well at least they say so here"
First time select backup current ROM, I did not go for a wipe, selected Google Apps addon.
Watched and it seemed to back up,
Rebooted but.... everything looked the same.
About phone, looked at Andriod Version 2.2 Baseband , kernal Build FRF91
see CyanogenMod nowhere.
Sucker for punishment opened ROM Manager and it asked me if I wanted to report an error "cancel" tried to install CyanogenMod again, it went staright to Andriod Guy/Exclaimation, hit up volume/power, rebooted.
Now whenever I try again I get Andriod guy/exclamation.
I think if I hit "fix permisions in ROM Manager", Flashed CLockwork recovery again .... I can go back to the first step above.

Have you downloaded a rom off of xda and attempted to flash it through recovery?

You can download ROMs from ROM Manager.
I downloaded them from ROM Manager.

Is Rom manager listed under the allowed list under the superuser apps? And it doesn't seem like clockwork is properly loaded on the system, otherwise you would not see the android/with exclamation mark when you boot into recovery. You would see that the latest clockwork recovery is listed twice on the top of the phone. If you have both lines there, that means you have the latest recovery. If you are still having problems with the latest clockwork recovery to install, have you tried the earlier versions to see if they properly install on the phone?
From my experiences, you need to indeed wipe and install gapps to properly install any rom. Then use titanium backup to restore your apps and settings. Looks like you are already backed up/nandroid before doing so.

Wipe first. My fault I didnt see that you ddint wipe

v0kal said:
Wipe first. My fault I didnt see that you ddint wipe
Click to expand...
Click to collapse
I know most people say when you download ROMs you need to wipe.
I know with Android this should not be a big deal, enter your Google info, the market downloads everything you paid for and then set up exchange mail again but it does take me a few hours to go through the steps and I been lazy.
Try a wipe......

No one said rooting would be easy lol. Customizing one's possesion, let it be a car to a phone is no real small feat. Like anything, you can go into detail as much as you want or not depending on why type of Rom you choose and like. For CM6, that ROM is excellent for customizing pretty much everything on your phone, but it does take some time to get it to your liking.
If you like a "kitchen sink" ROM, have you looked at eVilD's Sense ROMs? Well thats if you like the Sense UI's really, which I do not mind, but everything is thrown in there lol. BUT CM6 is a great launching pad for a novice, like I still am.

I've had no problems with Rom Manager. which clockwork did you install? the beta or stable one? Cause i know when i was doing mine it asked me.
I did the following steps
1. Root
2. Installed Rom Manager and backed up
3. Downloaded Rom of my choice
4. Full wipe and installed rom (via rom manager)

The OP just didn't root, of course.
If the education curve isn't worth it - just uninstall the application. Because you didn't install anything besides the application - because you have no root privileges - because you didn't root. And since you state that you don't want to learn - then why did you start messing with it in the first place?
The only thing that I don't like about ROM Manager is that it creates a lot of people like the OP - starting to mess with something without any wish for understanding, how it works, screwing things up (or not), and start complaining. You did what you did, you didn't bother learning, so why exactly are you complaining?!

Well I will ignore Jack_r1 who is a troll.
"All boards have them ..... sigh"
For the people that were much more friendly and helpful,
Ok next time I try it I will do a full wipe.

Full wipe won't help you. Installing a root-only program without rooting the phone and expecting it to work wouldn't care if you wipe or not.
Guess you really have no clue...
Read my signature.
Calling me a troll won't help you either, and won't make you less infant. Especially for anyone who did bother reading my sig and my posts.

Jack_R1 said:
Full wipe won't help you. Installing a root-only program without rooting the phone and expecting it to work wouldn't care if you wipe or not.
Guess you really have no clue...
Read my signature.
Calling me a troll won't help you either, and won't make you less infant. Especially for anyone who did bother reading my sig and my posts.
Click to expand...
Click to collapse
I thought OP said he has root.
To OP: Open the app drawer, do you have the superuser app?

Mokurex said:
I thought OP said he has root.
To OP: Open the app drawer, do you have the superuser app?
Click to expand...
Click to collapse
I didn't bother reading his next post, where he said he had root. My mistake.
I believe he had the recovery installed initially (otherwise he wouldn't see it backing up), but the first reboot to stock ROM removed it. After that, he wasn't able to do anything, being booted to stock Android recovery. And came here to complain. I guess a difference between running a program and rebooting from different partition aren't common sense to understand? Should be a prerequisite list before rooting.
The correct way would be, of course, to reflash the recovery through ROM manager again, but for people who don't understand the concept of dual-booting and think they run an application - that's not obvious (and it's one of the reasons I think ROM Manager is bad, and manual installation is good). And the better way would be to read the guides and flash the recovery manually. And while going any of those ways, whining on internet boards instead of asking questions would be the most unwelcome way.

I use ROM Manager because I'm a lazy bastard and it has worked flawlessly for me. I have literally flashed over 50 ROMs (mostly CM nightlies) and it has yet to fail me.
But people that have no clue what they're doing shouldn't be using a program like this and I'm pretty sure it comes with a disclaimer of sorts? Although I've barely flashed anything manually I did read up on the processes before going the custom ROMs route, it just seemed obvious.

Me too - lazy bastard, that is...
However, there was an issue with one of the ROM Manager updates a while back, where backups wouldn't restore. That's when a bit of manual knowledge came in handy...
Sent from my Nexus One using XDA App

After booting aospCMod 2.3.2

So for the past two days I've been trying to flash the new AOSP Gingerbread ROM, but although I follow everything straight from the wiki it always seems to get stuck on the HTC screen after the last reboot. Help me please!
EDIT: So I somehow got the rom to boot last night using RA recovery but after loading up a notice says Setup Wizard not being able to respond...etc, etc. Also after booting my home, call, and search buttons don't work at all. not even for other roms. PLEASE HELP!
020211 So after following instructions from this post: http://forum.xda-developers.com/showpost.php?p=11078749&postcount=4860 i was finally able to boot CM7 fully and without problems. If you're having problems with booting aosp's gingerbread rom just use this guy's instructions (at the bottom) and you should be good to go.

Make sure u install manually through clockworkmod mod first format boot system data and cache then install the rom let it boot then reboot and install gapps without wiping and reboot then you should be good I'm using the normal clockworkmod 2.5.2 and it works great
Sent from my HTC Hero CDMA using XDA App

okay thanks! ill try that and get back to you.
so no luck at booting. i'm still stuck at the HTC Boot screen.

i tried also and still no luck .. i hate this

to anybody having problems flashing GB, try these steps EXACTLY:
1) use clockwork 2.5.0.1 and follow the wipe/format process in the wiki
2) flash the rom then gapps
3) FLASH A CAPPED 691 KERNEL
This seems to be a continued issue, and I think it is because some phones can't handle high clock speeds like 768. The recovery currently posted by aosp (cwm 3.0.0.5) is overclocked and therefore will not boot, same with the kernel in the rom. Report back here if it works, I have already updated the wiki to advise people of this. Good Luck.

So i tried it again with the capped kernel and it still didn't work. also tried it without firerat's MOD but still a no go.

I'm upgrading aosp 2.3.2 rom from nightly build #188. Before flashing aosp rom plesae try to wipe everything like data, dalvik-cache, battery and rotate status. BTW, I'm using RA-Recovery not ClockworkMod.

i installed it after the standard wipes and thats it and its working just fine at 768 on my hero200. didnt have any issues and im loving the rom, but i am having one issue. this link is to my issue in q and a. if you can help feel free to hop on my thread and reply. other than that, i juast wanted to say this rom is great!

sai5o4 said:
So i tried it again with the capped kernel and it still didn't work. also tried it without firerat's MOD but still a no go.
Click to expand...
Click to collapse
Did you also flash a capped recovery?
sent from my hero, which no longer sucks ass

il Duce said:
Did you also flash a capped recovery?
sent from my hero, which no longer sucks ass
Click to expand...
Click to collapse
I agree with that. He should try a recovery that's not overclocked.
Root-Hack-Mod-Always™

Yeah I'm using clockwork 2.5.0.1.

sai5o4 said:
Yeah I'm using clockwork 2.5.0.1.
Click to expand...
Click to collapse
Well, I hate to say it but you must be missing a step somewhere. FYI in the OP for gingerbread the cwm3.0.0.5 is now capped at 691, so try that one again. Wipe both wipe options, go to mounts and format boot,system,data,cache, then gn into advanced wipe dalvik twice. Flash the rom,gapps,deca #43 capped 691 kernel, reboot. The first boot should take a while so be patient. Report back here if you can't get it, and I would recommend going into the live help room (aospbot IRC) which in the OP for GB. Good luck.

So still no luck. But I'm determined to somehow fix this no matter how many times I try!
Sent from my HERO200 using XDA App

sai5o4 said:
So still no luck. But I'm determined to somehow fix this no matter how many times I try!
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I think you should back up your sd card and then format it in your pc. Then start all over. From the recovery on down. Skip any mods till you get booted up. Like keyboards and boot screens etc. And try the capped cwm recovery. Hope it helps good luck
Something.About.Me.You.Dont
Like.Its.Cool.I.Understand.AWAH

Still no luck on booting aospCMod. Like they say no two heroes are the same. But that doesn't mean I'm still not going to try again and again and again (xinfinity).

got it to boot but...
so i somehow got it to boot using ra-recovery but right as i loads it says the setup wizard has unexpetedly stopped processing. any help?

sai5o4 said:
020211 So after following instructions from this post: http://forum.xda-developers.com/showpost.php?p=11078749&postcount=4860 i was finally able to boot CM7 fully and without problems. If you're having problems with booting aosp's gingerbread rom just use this guy's instructions (at the bottom) and you should be good to go.
Click to expand...
Click to collapse
Glad I could help man! Glad to see you got it worked out!

There's a readme in the Aosp 2.3.2 OP. It's right under the files, labeled README. I think it would help if anyone having trouble actually reads through this. skipping steps causes problems.
also, Factory reset skips over the /system partition. I recommend wiping /system partition if you're coming from another rom, or if you are decided to start fresh. You have to go into the partitions menu to actually format the /system partition.

mtran2988 said:
You have to go into the partitions menu to actually format the /system partition.
Click to expand...
Click to collapse
This is true if you use CWM (which I do not ) but if you fastboot wipe all the partitions you will have no issues w/ RA as the OP discovered once he used the instructions that I posted.

touble with vvm
uh not quite sure if this is rite place to post this but looked better than the rest, so i got the rom running fine and it is wonderful improvement to my what use to be my wifes stock hero. Only problem is with the visual voice mail, i copied it from the stock hero before flashing, than after flashing copied it back, it works in the sense that i can see the voicemail in the app and even the voicemail to text works, but 2 things are wrong, 1 is i cant clear voicemail notification in the status bar without rebooting phone, and now she gets a text from a 9069 that tells her phone has recieved a voicemail, found a work around for the second one i blocked the number using blacklist so the text dont come thru nomore, but how i can i fix the fact that the only way to clear the voicemail notification is to reboot the phone? Any help, comments or suggestions would be greatly appreciated. Or is there somewhere i can dl the latest sprint vvm app?? or are they device specific. Thank you in advance for any help

Android Market Unstable?

Hello all,
After flashing CyanogenMod the other day, I decided I didn't like it too much. ( Mind you, I just use my phone for basic phone stuff, so please don't flame me for it. xD ) So I used a nandroid to go back to my original (rooted) stuff.
However, in doing this, it seems that it messed up my Market app somehow.
Whenever I try to search, open, or do anything involving the Market App, it'll say: Attention. A network error has occurred. Retry, or cancel and return to the previous screen.
It's been like this for a while now. I can use internet, voice-to-text, and anything else that requires data ( not even WiFi works with Market ), but not Market.
What can I do to fix this?

Full wipe. Fresh install of rom+gapps.
Yea its Me Again With The
Modified Hero

@laie - he said he nanded back to rooted stock
@OP - try the nand restore again? Otherwise you could try adb shell fix_permissions?

laie1472 said:
Full wipe. Fresh install of rom+gapps.
Yea its Me Again With The
Modified Hero
Click to expand...
Click to collapse
Tried factory reset, that didn't work, I'll try that option last >.<
il Duce said:
@laie - he said he nanded back to rooted stock
@OP - try the nand restore again? Otherwise you could try adb shell fix_permissions?
Click to expand...
Click to collapse
It tells me that "fix_permissions: not found"
Edit: I've got it fixing now, will edit with update.
Edit(2): It didn't help, sadly.

I don't even remember, but does rooted stock 1.5 allow you to install non-market apps? If so, go find a market 2.3.6 apk on xda or google. Delete the one you have, boot into recovery wipe cache and then reboot, install the app - see if that'll work.

Nope, that didn't work sadly... Ironically, my Market worked perfectly without the updates installed. Is it possible just to block all updates for the Market apk?

this might work for you. a friend was having similar problem. this is what i did (note, i really really think that it was pure coincidence but...) go to SETTINGS -> APPLICATIONS -> MANAGE APPS. locate Market, if Force Stop is not greyed out. then click it, then click Clear Data.
like i said, his was having the same problem, i really think that it may have been a coincidence, but maybe not.

Vvh said:
Nope, that didn't work sadly... Ironically, my Market worked perfectly without the updates installed. Is it possible just to block all updates for the Market apk?
Click to expand...
Click to collapse
Yes, you need to delete the system app "marketupdater.apk". Also, if you go into settings/manage apps/all/market - can you click the button "uninstall updates"? If not, do you know what market version you had that worked? If so try to find and install that one using the same steps as I mentioned before. If that doesn't work, I'm at a loss.
Also what ngholson just posted is a good idea along with clear cache from the same menu.
I hope you get it figured out, good luck.

il Duce said:
@laie - he said he nanded back to rooted stock
@OP - try the nand restore again? Otherwise you could try adb shell fix_permissions?
Click to expand...
Click to collapse
Yea and??? He can still start fresh. He posted he did a nand back to his rooted stuff. Which means he can srart fresh. As in wipe data,cache dev-cache and sd-ext. Boot up and then reboot back into recovery reflash gapps. Boot up. Load tb go into settings, manage apps locate market force stop and clear data. Open tb up locate market updater apk. Uninstall. Reboot should be good.
Yea its Me Again With The
Modified Hero

ngholson said:
this might work for you. a friend was having similar problem. this is what i did (note, i really really think that it was pure coincidence but...) go to SETTINGS -> APPLICATIONS -> MANAGE APPS. locate Market, if Force Stop is not greyed out. then click it, then click Clear Data.
like i said, his was having the same problem, i really think that it may have been a coincidence, but maybe not.
Click to expand...
Click to collapse
Must have been, I tried it with no luck, but I'm glad it worked for your friend.
il Duce said:
Yes, you need to delete the system app "marketupdater.apk". Also, if you go into settings/manage apps/all/market - can you click the button "uninstall updates"? If not, do you know what market version you had that worked? If so try to find and install that one using the same steps as I mentioned before. If that doesn't work, I'm at a loss.
Also what ngholson just posted is a good idea along with clear cache from the same menu.
I hope you get it figured out, good luck.
Click to expand...
Click to collapse
The problem version is 2002306, oddly enough, I've overheard some other people having problems with it as well at a place a friend works. Maybe it's a stock hero thing. I'll revert to an older version, maybe one day this will clear itself out.
Thank you everyone for participating in helping me. At least it was a good effort.

laie1472 said:
Yea and??? He can still start fresh. He posted he did a nand back to his rooted stuff. Which means he can srart fresh. As in wipe data,cache dev-cache and sd-ext. Boot up and then reboot back into recovery reflash gapps. Boot up. Load tb go into settings, manage apps locate market force stop and clear data. Open tb up locate market updater apk. Uninstall. Reboot should be good.
Yea its Me Again With The
Modified Hero
Click to expand...
Click to collapse
Laie I was just telling you, don't get all frisky. If you read the OP again, you'll see he WANTS to be on stock 1.5. I couldn't tell you why lol. Maybe you forgot (it's been forever) but stock and sense based ROMs already contain gapps. You only flash those on AOSP based ROMs, so he can't reflash gapps. If he wiped and then nand restored it would've restored /system which is where the market would live in a stock ROM. His issue was likely a market auto-update which did not agree with old ass donut stock. Who knows. I wasn't bashing you, and I'm not now, calm down. Hopefully this info helps you help someone later. Peace.
OP- I have ONE MORE idea. Go grab a themed market zip from xda member "pendo" - he has green, blue, and red. They should flash from recovery. Delete your current market app FIRST, and clear cache and dalvik cache in recovery, flash and reboot. Good luck.
EDIT: 2 ideas I guess, copy the nand backup to your computer, find the "marketupdater.apk" in /system/app and delete it out of the nand. Copy that new nand to the same place as the current one you have and try to wipe all then restore that newish one.... I actally have NO idea if you can alter a nand or the system.img it contains, but it may be worth a shot. You could also just give up, and get gingerbread, because it's AWESOME.

il Duce said:
...You could also just give up, and get gingerbread, because it's AWESOME.
Click to expand...
Click to collapse
LOL agreed.
@OP - You could also try one of the *ahm* market replacements. like *ahm* applanet or something (not sure how 'legal' they are but...)
also, i know someone mentioned it before but did you ever get your permissions fixed? if not try that too, you can do it from ROM Manager.

ngholson said:
LOL agreed.
@OP - You could also try one of the *ahm* market replacements. like *ahm* applanet or something (not sure how 'legal' they are but...)
also, i know someone mentioned it before but did you ever get your permissions fixed? if not try that too, you can do it from ROM Manager.
Click to expand...
Click to collapse
or amazon app store.

il Duce said:
Laie I was just telling you, don't get all frisky. If you read the OP again, you'll see he WANTS to be on stock 1.5. I couldn't tell you why lol. Maybe you forgot (it's been forever) but stock and sense based ROMs already contain gapps. You only flash those on AOSP based ROMs, so he can't reflash gapps. If he wiped and then nand restored it would've restored /system which is where the market would live in a stock ROM. His issue was likely a market auto-update which did not agree with old ass donut stock. Who knows. I wasn't bashing you, and I'm not now, calm down. Hopefully this info helps you help someone later. Peace.
OP- I have ONE MORE idea. Go grab a themed market zip from xda member "pendo" - he has green, blue, and red. They should flash from recovery. Delete your current market app FIRST, and clear cache and dalvik cache in recovery, flash and reboot. Good luck.
EDIT: 2 ideas I guess, copy the nand backup to your computer, find the "marketupdater.apk" in /system/app and delete it out of the nand. Copy that new nand to the same place as the current one you have and try to wipe all then restore that newish one.... I actally have NO idea if you can alter a nand or the system.img it contains, but it may be worth a shot. You could also just give up, and get gingerbread, because it's AWESOME.
Click to expand...
Click to collapse
Duce were in the op does he say he's looking to get back to 1.5??? Humm think you might be reading to much " lol " eyes playing tricks on you??? He said he restored his rooted stuff. Not restored 1.5. And nope I remember 1.5 and I'm aware of the gapps only flash with aosp. I posted my comment because he didn't say 1.5 so I took a guess as he was not on 1.5 because he didn't mention it. So mabey this will help you help someone in the future slow it down when ya read. Because you know what happens when you assume. "" Read slow "" duce read slow lol
Yea its me again. With the
Modified Hero

Hm, well your right. Hey op, stock sucks. Get gingerbread.
sent from a series of tubes.

il Duce said:
Hm, well your right. Hey op, stock sucks. Get gingerbread.
sent from a series of tubes.
Click to expand...
Click to collapse
Super agree. Ditch stock. Who doesn't like cookies???
Yea its me again. With the
Modified Hero

@il Duce
Pendo's themed market wouldn't flash, sadly. And it's a shame too, because they look really great.
@ngholson
I looked into that, but it's permissions are a bit much.
@laie1472
I'm really sorry, you're right, I forgot to mention what I'm using.
It's:
Firmware: 2.1-update1
Build: 2.27.651.5
Again, I'm sorry for not mentioning that.
I redid everything on it, the only thing I haven't touched is the radio file.
When I tried CyanogenMod 6 at the start of this thread, it had me flash 2.42.01.04.27. Could that be the problem?
And I'm terribly sorry for the delay in replying. Other issues are stealing my time.

Ok let's start from scratch. What rom,recovery, kernel & mods are you using?? Also whats your prl, and are you s-off???
Yea its me again. With the
Modified Hero

Firmware: 2.1-update
Baseband: 2.42.01.04.27
Kernel: 2.6.29-bc0d2cff [email protected] #1
Build: 2.27.651.5 CL 169236 release-keys
Software: 2.27.651.5
Browser: Webkit 3.1
Pri: 2.62_003
PRL: 60677
ROM: Stock (and rooted) 2.1 Eclair.
Recovery: RA-heroc-v1.6.2
Mods:
Android Bios Boot animation
LauncherPro
That's about it. I think it's all worked flawlessly until the radio, but I'm not sure. If I'm missing any info, please let me know.

maybe consider starting completely over. download a new rom, i recommend aospcmod. download the latest version of gapps at the same time. if you don't already have it install ROMManager from errr. damnit your market doesn't work... hopefully you already have it. Open rom manager and install a custom recovery (i recommend clockworkmod) once that is done copy both the new rom and gapps zips to your sdcard, reboot to recovery (either manually or using rommanager) wipe everything. then select 'choose zip from sdcard' (or similar, can't remember exact verbiage) and install your ROM, then before you let it reboot, then use the same option and install gapps as well, then reboot. follow setup and it should work fine.