i am wondering why my app market is not working and how i would fix that. It keeps saying "the requested app cannot be found". Yet when i search i find them as soon as i click them i get that error. I am running the latest kingxrom. On his thread it says to use this script but were do put this script i tried entering it in the terminal but it just forceclosed and then i tried the console and after the reboot i got just a blackscreen so i had to reflash so im wondering were im suppose to put this script or what another way to fix my market thanks.
# mount -o rw /dev/block/mmcblk0p2 /system/sd
(enter)
# rm -rf /system/sd/*
(enter)
# rm -rf /system/data/*
(enter)
# reboot recovery
I myself also have been experiencing this issue, really annoying and don't know whats the cause.
ya i have flashed a couple other roms and im getting the same problem when i had mlign rom i didnt have this problem so i think im going to flash back to the mlign and see if it works. I searched google for 3 days and didnt come up with anything that worked man im so stumped on this problem.
I am also getting the errors. I have tried other ROMs and still get the errors.
mpfuzz2 said:
I am also getting the errors. I have tried other ROMs and still get the errors.
Click to expand...
Click to collapse
seriously dang that sucks man now i know im screwed i dont know what to do i guess im going to have to buy a new phone because i lost all my apps to plus my navi that i need lol
if anyone finds a fix please let me know
still no fix
i been having the same problem also... with mlign... tried two different hero roms and the same thing happened, put cm 4.2.2 on it an now it works... so seems to me that google has somehow blocked 1.5 versions of the market??? only thing i can think of... im gonna try a couple other different hero roms and maybe trying cm 4.0.4 and see if it still works...
crackahunky said:
i been having the same problem also... with mlign... tried two different hero roms and the same thing happened, put cm 4.2.2 on it an now it works... so seems to me that google has somehow blocked 1.5 versions of the market??? only thing i can think of... im gonna try a couple other different hero roms and maybe trying cm 4.0.4 and see if it still works...
Click to expand...
Click to collapse
ok well i have tried kings new rom sense v1.3 and the market still doesnt work so i guess ill be trying cm's 4.2.2 by the way is that rom faster then the hero's i find the hero's to be pretty dang fast
I switched to CM 4.1.11.1 and the is market working. It is the 1.6 version of course. Don't know what the 1.5 version market's issue is, and I really like the Hero ROM's.
mpfuzz2 said:
I switched to CM 4.1.11.1 and the is market working. It is the 1.6 version of course. Don't know what the 1.5 version market's issue is, and I really like the Hero ROM's.
Click to expand...
Click to collapse
ya me to man i like the hero roms a lot but i need the market so guess ill be trying out the cm rom now is it faster then hero
why arent you guys flashing 4.2.1 - it is Very fast and better than the other CMs in my opinion.
i might just try that one
Strange, but I decided to try and go back to Hero ROM again and it works fine (the market). Like nothing ever happened.
associated with login
I had this problem. I tried several different roms, completely wiped everything, reformatted sd... I even wiped and went back to stock Donut. It didn't work, until I created a new Google account. Now it works fine on any rom. I wonder if google has put a limit on how many times you can log in to the market, to stop sharing of paid apps.
carnegie0107 said:
I had this problem. I tried several different roms, completely wiped everything, reformatted sd... I even wiped and went back to stock Donut. It didn't work, until I created a new Google account. Now it works fine on any rom. I wonder if google has put a limit on how many times you can log in to the market, to stop sharing of paid apps.
Click to expand...
Click to collapse
I'm pretty sure that google did not do anything like that. Something got borked for all of you guys. While I have not flashed any Hero roms in a long long time, I do know that you need to really clean out your phone before you even attempt to put Hero on it. That includes
Wipe
Wipe again
Drop to terminal and rm -r
system/sd/app
system/sd/app-private
system/sd/dalvik-cache
data/app
data/app-private
data/dalvik-cache
data/data (I think)
run e2fsk on your system/sd
wipe again
And only then you should install Hero rom following all recommendations from the creator of the rom.
Also, I wouldn't wipe right after installing a rom: sometimes devs sneak a thing or two into /data which you could delete if you wipe.
Good luck.
borodin1 said:
I'm pretty sure that google did not do anything like that. Something got borked for all of you guys. While I have not flashed any Hero roms in a long long time, I do know that you need to really clean out your phone before you even attempt to put Hero on it. That includes.....
...Good luck.
Click to expand...
Click to collapse
Yes, I definitely completely cleaned out my phone. I completely wiped EVERYTHING, everything in data, in cache, in system... I even completely formatted my sd back to fat32, then reformatted again with ext4 and swap partitions. Then I wiped again, twice, then flashed cyan's stable. I also did the same thing (minus the total reformat of sd, just a simple delete of data) with a couple other ROMs, including kingklick. Market still didn't work. I did one wipe, flashed kingklick's latest sapphire sense port, and logged in with a NEW google account, and it worked perfectly. I'm going to try wiping and logging in with my old account, to see if it gives me the same error.
edit: Confirmed. Wiped, flashed, logged in with old account --> Market broken. Wiped again, flashed again, logged in with new account again --> Market works. I'm trying to contact Google to see what can be done.
borodin1 said:
I'm pretty sure that google did not do anything like that. Something got borked for all of you guys. While I have not flashed any Hero roms in a long long time, I do know that you need to really clean out your phone before you even attempt to put Hero on it. That includes
Wipe
Wipe again
Drop to terminal and rm -r
system/sd/app
system/sd/app-private
system/sd/dalvik-cache
data/app
data/app-private
data/dalvik-cache
data/data (I think)
run e2fsk on your system/sd
wipe again
And only then you should install Hero rom following all recommendations from the creator of the rom.
Also, I wouldn't wipe right after installing a rom: sometimes devs sneak a thing or two into /data which you could delete if you wipe.
Good luck.
Click to expand...
Click to collapse
i tried this over and over and over again and nothing im gonna try creating a new google account and see if that works
I ended up wiping, repartitioning my sdcard card and wiping and reinstalling my ROM and it all works (I did backup ONLY using backup for root users.) and it all works fine for me know, going on 1 1/2 days. I use the same google account.
i had apps backed up on my sd card but if repartioning the sd card worked for you then i might to do that dont want to make a new google account lol.
ok so pretty much nothing worked for me besides changing my gmail account anyway i can change my gmail account sign in back to my old one without reflashing
Related
I was bothered by the fact that Google Talk didn't show some of the messages I received. Johan de Koning submitted a patch that wasn't accepted by Google but works well. I applied this patch for personal use, but I thought that you might be interested as well.
Also, I had a look at the IM application and I modified it to allow login instead of having the "phone number cannot be read from your SIM" error. This might or might not work. It works for me, but users in the US have reported that it still fails.
UPDATE 16th Jun 2010:
Added version 1.1.2 from Cliq.
UPDATE 3rd Feb 2010:
New eclair version for IM.apk, completely untested. Might or might not work.
Patched ImProvider is no longer useful for Android versions >= 2.
Also, I removed the cupcake IM.apk because I just noticed it is broken and won't work. No-one should be still running a rooted cupcake anyway.
Notes
This is for donut. I tested it on cm 4.2.2 and 4.3.2.1, but it should work with any donut rom. As far as I know, it doesn't use sms at all. It still needs the tmo plugins to login, but no sms are sent. Other than that, it does exactly the same as when you login on wifi.
Installation
Some of these steps will fail depending on the rom (the dalvik-cache and odex part). These errors can be safely ignored.
First reboot into recovery, then, on your computer :
Code:
adb shell
mount /system
mount /sdcard
cp /system/app/IM.apk /sdcard/IM.apk
cp /system/app/ImProvider.apk /sdcard/ImProvider.apk
exit
adb push ImProvider.zip /system/app/ImProvider.apk
adb push IM.zip /system/app/IM.apk
adb shell
mount /system/sd
rm /system/sd/dalvik-cache/*
rm /system/app/ImProvider.odex
rm /system/app/IM.odex
umount /system/sd
umount /system
umount /sdcard
reboot
Of course, I'm not responsible if anything breaks.
More information about the sources is available in this post.
which roms are these for? cupcake? donut? hero? haha. i pushed them to my hero rom and they do not show up in my app tray or in applicantion manager.
Tested them on cm 4.2.2 and it works. Does this use ip traffic or sms?
ok cool, probably for donut. i tried on Hero cupcake and it fails, just keep getting ForceCloses. owell, i dont use it anyways but just thought it be fun =)
Bavilo said:
Tested them on cm 4.2.2 and it works. Does this use ip traffic or sms?
Click to expand...
Click to collapse
You can try removing TmoImPlugin.apk and see if it still works.
edit:
I asked him in another thread earlier and this is his response
Zappletoo said:
Data only hopefully.. I've not been charged for any sms so far.
Click to expand...
Click to collapse
I'm going to push it into Cyan's build and remove TmoImPlugin.apk and see if it still works.
Well, it doesn't work without tmoimplugin, and with that, I know it uses sms.
Sorry for the lack of details.. I updated the first post to make it clearer. It doesn't send sms afaik, becaus my plan doesn't have unlimited sms and I wasn't charged for any sms since I patched the IM app.
Also, this is for donut only, because the IM subsystem changed a bit since cupcake.
can you somehow modify im.apk so that it would stay in memory?
seems to work fine *tries out this im comparison to ebuddy, seems much faster ^^*
not sure if it uses sms, but dont think so.. ah well got unlimited anyway ^^
Do you have the source patches for these?
I'd like to have more feedback.. Does it work properly for everyone ? Any bugs or FC ?
cyanogen said:
Do you have the source patches for these?
Click to expand...
Click to collapse
The patch from ImProvider is here : http://code.google.com/p/cyanogenmod/issues/detail?id=597
but I couldn't recompile it from source without breaking everything.. I had to patch the apk directly. Maybe you'll do better.
The patch for the IM application is attached, the edited file is in packages/apps/IM/src/com/android/im/service
DOHCtor said:
can you somehow modify im.apk so that it would stay in memory?
Click to expand...
Click to collapse
I don't know how to do that, sorry. But it seems the app already stays in memory for a while. Are you sure it doesn't stay already, if it's not killed by an application manager ?
Sorry if I'm being a noob, but how exactly does one install this? I did
adb push /path/IM.apk /system/app
adb push /path/ImProvider.apk /system/app
and rebooted, and I still get SIM card cannot be read errors. I feel like I'm probably missing a step like installing.
enderx1 said:
Sorry if I'm being a noob, but how exactly does one install this? I did
adb push /path/IM.apk /system/app
adb push /path/ImProvider.apk /system/app
and rebooted, and I still get SIM card cannot be read errors. I feel like I'm probably missing a step like installing.
Click to expand...
Click to collapse
Yea, same here. I guess it doesn't work for users in the States. However, it does work on wifi but once I turn off wifi, it disconnects.
Try installing it from recovery if you didn't, and clear dalvik cache (rm /system/sd/dalvik-cache/* on cm with apps2sd, not sure about others).
i'm tryin using it on CM ROM 4.0.4 but when i try push it, i can't use the IM, is there anyone already can used that IM in CM ROM 4.0.4 ?? thanks before
I hate when my messages are loosed, and run loose around the intarwebs.
Additionally, I don't like to be LOSING messages. =9
Thanks! Works perfect on enomther 2.1.1
kamikaze2311 said:
i'm tryin using it on CM ROM 4.0.4 but when i try push it, i can't use the IM, is there anyone already can used that IM in CM ROM 4.0.4 ?? thanks before
Click to expand...
Click to collapse
It doesn't work on cupcake, donut only (cm >= 4.2).
danguyf said:
I hate when my messages are loosed, and run loose around the intarwebs.
Additionally, I don't like to be LOSING messages. =9
Click to expand...
Click to collapse
You can never have enough o's.
Did anyone else lose use of the market doing this?
ZeroGDarius said:
Did anyone else lose use of the market doing this?
Click to expand...
Click to collapse
Are you sure this is related ? I don't really see how the IM application could affect the market..
If you are running Dwang on a Stock SPL and you are having problems installing a theme, I have some suggestions and ideas, some of these are very basic and common but ill repeat them anyway because youd be surprised at how many people dont follow these:
1) Make sure the theme you are using is compatible with the right version of Dwang that you are using. (keep in mind that v1.13-1.17.1 themes are interchangeable among those versions. ex: you can use a 1.13 theme on 1.17.1)
2) Make sure to ALWAYS have a Nandroid/BART backup, in case anything goes wrong.
3) Make sure youre using an EXT 3 file system.
4) Do NOT wipe BEFORE or AFTER flashing a theme. If you are using one theme and wish to switch to another theme, simply flash your base ROM over the old theme, then flash the new one.
5) Always have your apps backed up if you dont want to go looking for them again. I suggest ASTRO File Manager which can be downloaded from the Market for free.
Q. STUCK AT THE G1 SCREEN?
A. This happens sometimes if the theme is a little too large and you have Stock SPL....but what if you really want the theme and are afraid to upgrade your SPL because youre afraid of bricking your phone, or because youre one of the few people like me who are unable to upgrade to the latest radio? Theres a solution for that, I cant promise itll work for every single theme, but Ive tested it with Darkstar and DBeCe's black theme which gave me problems before I tried this method. I believe it will work for most themes on Dwang.
The solution is simple, try to free up space in your SYSTEM partition by moving your ringtones, sound effects, alarms, etc to your sdcard. This will free up around 2.66mb in the system partition. You can do this using Terminal Emulator.
type in
$su
mount -o remount,rw /system/dev/mtdblock3 /system
cp -r /system/media/audio /sdcard/
rm -R /system/media/audio
and you should see your audio folder in the root of your sdcard. You can add ringtones and sounds there too if you like, but the point is, now your SYSTEM has a little more space.
Restart your phone and boot into recovery and try to flash the theme again, and it should work now.
Q....OKAY SO I GOT PAST THE G1 SCREEN AND IT SHOWS THE ANDROID SPLASH SCREEN BUT AFTER A WHILE I GET A BLACK SCREEN!!!
A. If this happens to you, then you must format your EXT 3 partition. I suggest using the latest Amon_RA Recovery (v1.5.2 at the time of this post, MAKE SURE YOU DOWNLOAD THE CORRECT RECOVERY FOR YOUR PHONE).
If youre still having problems, i suggest wiping everything including the phone, dalvik cache, battery and rotate settings (i like to wipe everything 3 times, but thats just me), reinstall dwang, login at the beginning, wait for the sync, and make sure to open up market and agree to the terms otherwise you might have problems with the market when you install a theme, (also keep in mind when u flash the rom again, you have to move the ringtones back to the sdcard again using the method i mentioned above), after you have done all that, reboot into recovery, flash the theme again, and it should be okay.
I hope Ive helped. Im still new to the scene but Ive found that this works for me and I just wanted to share, and I hope I helped and that your themes are working now.
If you have any suggestions or feedback, please feel free to share.
Thank You!
well done on a detailed and excellent advice. Keep it up
Great tutorial. I have the HardSPL and I am getting the same symtoms. All the themes that I have tried get to the theme splash and then stop. The longest I have allowed one to run is an hour. Do you think that space is still the issue? I am going to try these steps as they cannot hurt, but I thought that I was good with the HardSPL.
s2welee said:
Great tutorial. I have the HardSPL and I am getting the same symtoms. All the themes that I have tried get to the theme splash and then stop. The longest I have allowed one to run is an hour. Do you think that space is still the issue? I am going to try these steps as they cannot hurt, but I thought that I was good with the HardSPL.
Click to expand...
Click to collapse
the hard spl has the same partition spacing as the stock spl, it is the 1.33.2005 spl that provides more space to system.
tryed it..
Tried this method and only got darkstar to work for a min then force close when I tried to login to my google account and wouldn't stop force closing....U got any other methods that might work.
tom_me said:
Tried this method and only got darkstar to work for a min then force close when I tried to login to my google account and wouldn't stop force closing....U got any other methods that might work.
Click to expand...
Click to collapse
Thanks everybody, if you have any other suggestions, ill add them to the first post.
darkstar 0.6.7 is kinda complicated... you said google login so im guessing you wiped before u flashed? normally you shouldnt do that but for this theme i had to, ill explainin the next paragraph, but first of all, did you try to skip the initial sign in and then try to login by clicking on gmail or checking sync settings? i had a similar problem with another theme, and thats how i solved it. let me know if that works.
this is why darkstar 0.6.7 is a little different and more challenging to install compared to most themes (at least for me):
darkstar 0.6.5 flashed fine with me, when i had dwang 1.15 but when i upgraded dwang 1.17.1 and used darkstar 0.6.7, it gave me a little trouble and i had to get a little creative in order to install it properly because for some reason the market app was pushed to ext and it was no longer available after i wiped the ext before, and i kept getting a black screen if i didnt wipe the ext system. so what i did was wipe everything flash the stock rom, backup the market app using astro file manager (some reccomend backup for root users, i havent tried it yet), flashed the theme got a black screen, wiped the ext3, then i reflashed the theme again and i got it working but i was missing market, and i couldnt download astro without market.....unless i went to google using the browser and i looked up astro 2.2.3 apk and i downloaded the app directly to my phone, and restored market. however the market will start force closing even after you run fix_permissions so i went against the rule of wiping after a flash, and i decided to wipe the phone....lo and behold its been running flawlessly ever since, but it took a lot of work, idk why it gave me such a hard time this time, but i managed to get it working. try the first method first and let me know how that goes.
david1171 said:
the hard spl has the same partition spacing as the stock spl, it is the 1.33.2005 spl that provides more space to system.
Click to expand...
Click to collapse
Thanks, that clears up some confusion.
got it
Ok the first time I did it I had to wipe cuz it would never get pass the G1 screen and it worked for a min. Now I tried wiping everything and repartition my sd and restored backup and then I flash theme again and reboot. I finally get pass g1 screen then stuck on android screen. I took out the battery reboot and flash theme again reboot, same thing happen then took batt out powered on regularly did it four times and it finally worked.....
tom_me said:
Ok the first time I did it I had to wipe cuz it would never get pass the G1 screen and it worked for a min. Now I tried wiping everything and repartition my sd and restored backup and then I flash theme again and reboot. I finally get pass g1 screen then stuck on android screen. I took out the battery reboot and flash theme again reboot, same thing happen then took batt out powered on regularly did it four times and it finally worked.....
Click to expand...
Click to collapse
im glad u finally got it working. idk why that specific theme was so difficult to install. the g1 screen was still stuck even after you moved the ringtones to sd?
speedysilwady said:
im glad u finally got it working. idk why that specific theme was so difficult to install. the g1 screen was still stuck even after you moved the ringtones to sd?
Click to expand...
Click to collapse
Yea moved ringtones to sd... and still got stuck......but I think u just need to run the rom for a bit before flashing a theme. But yea it looks great.... and thanks for the help.
Tom
there are a few things that could be removed from the /system partition of dwang's rom.
rm /system/app/GenieWidget.apk
rm /system/app/Maps.apk (since the updates are installed on the /data partition)
rm /system/app/BugReport.apk (its not in cyan's roms anymore)
cp /system/app/Mail.apk /data/app/
rm /system/app/Mail.apk
(cyan did it in his latest release)
(maybe? haven't tested this one)
rm /system/app/LatinImeTutorial.apk
There are probably some more "useless" .apk's that could be removed.
david1171 said:
there are a few things that could be removed from the /system partition of dwang's rom.
rm /system/app/GenieWidget.apk
rm /system/app/Maps.apk (since the updates are installed on the /data partition)
rm /system/app/BugReport.apk (its not in cyan's roms anymore)
cp /system/app/Mail.apk /data/app/
rm /system/app/Mail.apk
(cyan did it in his latest release)
(maybe? haven't tested this one)
rm /system/app/LatinImeTutorial.apk
There are probably some more "useless" .apk's that could be removed.
Click to expand...
Click to collapse
thank you so much for confirming my suspicions. i knew there was more useless stuff in the apps folder but i wasnt sure how to test it all. ill try this method out later tonight and try to flash a large theme and see what happens, ill add this info to the first post tonight!
sorry im late guys ive been pretty busy. i stumbled upon this page on cyanogenmods wiki
http://wiki.cyanogenmod.com/index.php/Barebones
it shows which files can be deleted safely out of /system and /dev. im gonna try removing a lot of those apks from my dwang rom and i wanna find a huge theme to flash thats supposed to be used only with danger spl, anyone have any suggestions? i think this might work. btw does anyone know if its possible to make a script to make removing multiple apks easier?
I REALLY need some assistance, think I screwed my phone, really want to avoid a hard wipe.
I installed Lockbot the other day, has some issues with dual lock layers (i.e. the lockbot app wasn't disabling my HTC lock so I had two unlocks.). emailed dev and he sent me a beta version to hopefully correct issue. I only received an apk file from him.
FYI I am on fresh 1.1, rooted.
I used the kitchen to puch this file: "LockBotPro_1.10.0_beta.apk" to /system/app.
The install went successfully, but later after a reboot I face a HUGE issue. The lockbot app is hanging upon reboot and will not unlock. At first I thought i would still be okay, I had ATK and Advanced Task manager both running at start up, so I can enter both of them through my notification drop down menu. I used both to kill the task-to no avail it is still locked. I tried to use advanced task manager to uninstall lockbot - to no avail, it cannot be removed.
Then I tried to pull back the file through kitchen, to no avail.
I don't know what to do. I cannot get my phone to unlock and i cannot pull the file off through adb or kitchen. DOES ANYONE HAVE ANY IDEA ON HOW TO FIX THIS??????
I would suggest pulling the battery and rebooting into recovery then use adb to cd to system/app and use rm to remove the apk that way and then boot the phone
wtphoto said:
I would suggest pulling the battery and rebooting into recovery then use adb to cd to system/app and use rm to remove the apk that way and then boot the phone
Click to expand...
Click to collapse
I have tried to pull the file in both adb and in kitchen. Would it have installed as something other than the name I pushed it under?
Even if the phone is hard locking (kind of rare of android. even in all the stupid f'd up things I've done I've only hard locked my phone to the point that I couldn't even get in to adb once or twice) then the file system is still completely accessible while it's booting up. You can use the "pull any file" from the kitchen and check off that you want it to delete it after it's done. Just get it all queued up in the kitchen and then power on your phone. Once it gets passed the HTC logo wait a few seconds and then run the pull file from the kitchen. Should work just fine for you.
The alternative (if you are comfortable with adb) would be to boot your phone in to recovery (can also be done through the kitchen, even when it's in the middle of booting) and then type the following from a command prompt:
adb shell mount /system
adb shell rm /system/app/your-application.apk
FYI for future reference you should push these types of applications to /data/app. Your hard locks could either be caused by the fact that the beta just broke things, or it could be that you have a copy of it in both /data/app and in /system/app.
the problem is that you dont want to just pull the file all that does is create a copy of the file where ever you pull it to you need to use the rm cmd to actually remove the file and have you tried to do this from the recovery menu before the phone boots? I mean I am by no means an expert but commonsence says that if you do it in the recovery menu that it would be gone when the phone actually boots and the problem would be gone.
edit: sweet im not a complete noob anymore I was right about removing from the recovery. flipz explained it better though.
thanks flipz, I'm going to try this. I will try via adb first, then via kitchen. Last time kitchen gave me a message to "post" but I didn't figure I would catch you online. Hope you're still around in 15-20. thanks for the how-to!
TF1984 said:
thanks flipz, I'm going to try this. I will try via adb first, then via kitchen. Last time kitchen gave me a message to "post" but I didn't figure I would catch you online. Hope you're still around in 15-20. thanks for the how-to!
Click to expand...
Click to collapse
I'll be here.
hmmm. I think I've really screwed something up.
I opened CMD, ran adb, here's where I am and what I have (fyi I get the same thing no matter in Recovery, boot or after normal start up)... and I use apps2sd
C:\android-sdk-windows\tools>adb shell mount /system
mount: cannot read /etc/fstab: No such file or directory
If I use Kitchen to pull file: It says "Files Deleted".
Now on my Hero, after fresh reboot...
Well maybe it's okay. But now many of my apps are giving FC error. AHH Crap!!!
That app is demonic... LockBot, I'm gonna get my moula back!
TF1984 said:
hmmm. I think I've really screwed something up.
I opened CMD, ran adb, here's where I am and what I have (fyi I get the same thing no matter in Recovery, boot or after normal start up)... and I use apps2sd
C:\android-sdk-windows\tools>adb shell mount /system
mount: cannot read /etc/fstab: No such file or directory
If I use Kitchen to pull file: It says "Files Deleted".
Now on my Hero, after fresh reboot...
Well maybe it's okay. But now many of my apps are giving FC error. AHH Crap!!!
That app is demonic... LockBot, I'm gonna get my moula back!
Click to expand...
Click to collapse
You have a nandroid backup... don't you? Actually what you can try doing is flashing fresh right on top of itself. You won't lose any settings and it will overwrite everything in /system/app.
I haven't made a recent Nandroid backup.
All of my third party apps are giving FC upon trying to execute any action within them. I think I might just reinstall each. I think something happened with my sdcard through this process trying to get rid of lockbot. Not sure.
If I flash fresh it wouldn't remove any data right, will anything change? I think I remember last time I flashed it I even retained my scenes and all, but I have a bad memory. I guess I'll give it a go.
TF1984 said:
I haven't made a recent Nandroid backup.
All of my third party apps are giving FC upon trying to execute any action within them. I think I might just reinstall each. I think something happened with my sdcard through this process trying to get rid of lockbot. Not sure.
If I flash fresh it wouldn't remove any data right, will anything change? I think I remember last time I flashed it I even retained my scenes and all, but I have a bad memory. I guess I'll give it a go.
Click to expand...
Click to collapse
Yea so in general when it comes to the phone /system should remain untouched and /data is where all saved settings and market apps go. Obviously we change that by rooting the phone and creating custom roms. But that concept still applies when flashing a rom. It will only wipe /system and not /data (unless the rom dev does something wrong heh).
Flipz I swear one day I am going to make a sizeable donation to you. If I can only find some extra money.
I think you have helped in every issue I have had after rooting, there haven't been many but you are always helpful when I run into trouble.
Well I flashed 1.1 again, but it didn't help to fix the FC on every app.
Guess I will just remove and install each one by one. This will make for a good time to review each app and decide which I should part with for non-use.
Thanks again, my lock issue is resolved!
Maybe I'll try the lockbot again but install to app/data as you suggested in earlier posting.
TF1984 said:
Well I flashed 1.1 again, but it didn't help to fix the FC on every app.
Guess I will just remove and install each one by one. This will make for a good time to review each app and decide which I should part with for non-use.
Thanks again, my lock issue is resolved!
Maybe I'll try the lockbot again but install to app/data as you suggested in earlier posting.
Click to expand...
Click to collapse
Might be worth it for you to try clearing your dalvik-cache to see if it fixes your FC's. If that doesn't work then my guess is you are using apps2sd and the symlink got broken somewhere along the way.
And no problem.
Yes I am using apps2sd. I tried the davlik clear cache in kitchen earlier today in attempt to fix the lockbot (I don't know, figured maybe it would work since i have no idea what that does to begin with).
Question, I did pull my sd card out earlier while the phone was off. Then booted and it only went into a boot loop, is that likely to have caused the FCs?
Does that mean that I cannot ever remove the sd card at all or will always cause this problem...cause that would friggin suck a big one!
flipzmode said:
Yea so in general when it comes to the phone /system should remain untouched and /data is where all saved settings and market apps go. Obviously we change that by rooting the phone and creating custom roms. But that concept still applies when flashing a rom. It will only wipe /system and not /data (unless the rom dev does something wrong heh).
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=4942088&postcount=2 -- post #2 from the fresh rom thread from back in november.
The reason I don't like it is because it puts your phone at a huge risk of having problems once anything goes wrong. If you install a program that causes issues, a nandroid backup will not resolve the issue because the application is installed on your SD card not your phone. If your phone starts going crazy as reported here and here, then even just a restore possibly won't fix it. You might need to go as far as to wipe your SD card too. If you are lucky enough to have a restore fix your problems you will still need to reinstall every app, even if you didn't wipe your card. And on top of that when you try to reinstall any app it will think it's still installed, even though you restored your phone. But when you click "uninstall" it will just freeze half the time because there's nothing on the phone for it to actually install. I have also read many threads that say if you happen to boot the phone up without the SD card in then it will screw everything up.
Click to expand...
Click to collapse
yikes.
I guess it is a gamble, do I want the space provided while keeping apps on my card (I do have A LOT of apps) or do I go the safe route?
Hmmm. thanks again. Quick question, earlier you said I needed to install that apk in data/app, not system/app. I pushed it back via kitchen to data/app and it isn't showing up anywhere. Was there an additional step I am not aware of?
TF1984 said:
yikes.
I guess it is a gamble, do I want the space provided while keeping apps on my card (I do have A LOT of apps) or do I go the safe route?
Hmmm. thanks again. Quick question, earlier you said I needed to install that apk in data/app, not system/app. I pushed it back via kitchen to data/app and it isn't showing up anywhere. Was there an additional step I am not aware of?
Click to expand...
Click to collapse
Make sure you aren't forgetting the leading slash. /data/app not data/app. But no, nothing special. That should work. Although if using apps2sd you might want to push to /data/sd/app. It should work regardless because a2sd sets up a symlink but if your stuff is messed up then it might not be working right.
TF1984 said:
hmmm. I think I've really screwed something up.
I opened CMD, ran adb, here's where I am and what I have (fyi I get the same thing no matter in Recovery, boot or after normal start up)... and I use apps2sd
C:\android-sdk-windows\tools>adb shell mount /system
mount: cannot read /etc/fstab: No such file or directory
If I use Kitchen to pull file: It says "Files Deleted".
Now on my Hero, after fresh reboot...
Well maybe it's okay. But now many of my apps are giving FC error. AHH Crap!!!
That app is demonic... LockBot, I'm gonna get my moula back!
Click to expand...
Click to collapse
Type this command in to mount:
mount -o rw -t yaffs2 /dev/block/mtdblock3 /system
That will mount the /system volume and put it in read-write mode.
Once you are finished deleting the file, type:
umount /system
Then reboot the phone.
Edit: If you want to mount the /data volume, type: mount -o rw -t yaffs2 /dev/block/mtdblock5 /data
I've installed maps from both the market, and the thread in XDA dev, but although the app says it's 3.4.0, I'm not able to multitouch.
I'm on CM 4.2.14.1 with the 10meg hack.
Also, the main application I use (GeoBeagle) is now crashing with the new map. I'm wondering what I can do to make sure I've got everything installed correctly, or how to revert back to a previous version where I can at least still go geocaching.
You can either rm by going into the Terminal emulator and typing this in:
Code:
$ su
# mount -o rw,remount /dev/block/mtdblock3 /system
# cd /system/app
# rm Maps.apk
# mount -o r,remount /dev/block/mtdblock3 /system
This will remove the modified version.
afterwards go into the Market and download the newest un modified maps application.
thanks, yeah, i did that... however, when I go to market, it says that Google Maps is "installed" even though the options for "open" and "uninstall" are greyed out.
I am indeed in a pickle.
pilkro said:
thanks, yeah, i did that... however, when I go to market, it says that Google Maps is "installed" even though the options for "open" and "uninstall" are greyed out.
I am indeed in a pickle.
Click to expand...
Click to collapse
Try rebooting.
if you can download the maps from the market then hoorah
if not:
Then try to flash the modded maps back in.
if it still doesnt work after you flash it and try it again, go on the market and you should be able to download the original maps 3.4.0.
otherwise the last resort would be to wipe and re flash the rom.
sorry if this causes any inconveniences.
Yeah, I did get the 3.4.0 from Market working again, but it still does NOT perform multitouch. Is this only available in the moded version on G1?
*edit* I did get multitouch working by installing the update from market first, and then adding the modded version afterwards. Geobeagle is still crashing, however.
pilkro said:
Yeah, I did get the 3.4.0 from Market working again, but it still does NOT perform multitouch. Is this only available in the moded version on G1?
*edit* I did get multitouch working by installing the update from market first, and then adding the modded version afterwards. Geobeagle is still crashing, however.
Click to expand...
Click to collapse
Happy to hear it.
and yeah ive been seeing some posts where people have been saying that somethings have been crashing.
but it should work out fine. and maybe the dev of this app will make a modded ver that wont crash GeoBeagle
Lucky you, how about me?
pilkro said:
Yeah, I did get the 3.4.0 from Market working again, but it still does NOT perform multitouch. Is this only available in the moded version on G1?
*edit* I did get multitouch working by installing the update from market first, and then adding the modded version afterwards. Geobeagle is still crashing, however.
Click to expand...
Click to collapse
I ahve the same setup and got the same result. Which map version did you flash? What method did you use?
MLonon said:
I ahve the same setup and got the same result. Which map version did you flash? What method did you use?
Click to expand...
Click to collapse
I used option 2 from here: http://forum.xda-developers.com/showthread.php?t=627582
Okay, so now I'm wondering if i've destroyed whatever file lets applications access the maps program, because none of the geocaching apps work when I try to show the map. I had done some wildcard deletions in my desperation in trying to fix the maps.
Can anyone point me towards what I can do to fix that? As in what files might need replacing? I've already re-flashed CM 4.2.12.1, but that didn't repair any associations afaict.
pilkro said:
I used option 2 from here: http://forum.xda-developers.com/showthread.php?t=627582
Okay, so now I'm wondering if i've destroyed whatever file lets applications access the maps program, because none of the geocaching apps work when I try to show the map. I had done some wildcard deletions in my desperation in trying to fix the maps.
Can anyone point me towards what I can do to fix that? As in what files might need replacing? I've already re-flashed CM 4.2.12.1, but that didn't repair any associations afaict.
Click to expand...
Click to collapse
Depends on what you deleted.
2 Options.
1.Find out exactly what you deleted and maybe we will be able to help you out.
2.Full Wipe and Re-Flash
These are the only options I see at least.
Hey all,
I've been an xda stalker for a while and have been using all sorts of roms for a while now, but now I am in need of my own question.
For a while now, my mother's G1 has been acting up, whether it be her own fault or a bug. But this one has me confused. Over the past three roms i flashed (dwang, cm, superd) this same problem is always around. Everytime I touch browser, dolphin, etc the page begins loading and then i see the home screen.
Everything else works as it should, which confuses me. Everytime I flash a rom, i wipe, wipe ext, repair ext, wipe, flash.
I'd be happy to post a logcat if someone would be so kind as to inform me how to dump to a txt file.
Hopefully this is something extremely easy so I can get her off my back hah
erkmasterflex said:
Hopefully this is something extremely easy so I can get her off my back hah
Click to expand...
Click to collapse
sure its easy, if its your mom's phone, dont have a unsupported non-factory rom on it... the REAL awnser is: wipe EVERYTHING, even your ext partition, and reinstall base, then CM... I'm guessing its something you mucked up by going between builds without wiping, or not fixing permissions between builds, or some app on your ext didnt play nicely.
*oh yeah, wrong section, read stickys, or DIAF, your choice*
jmhalder said:
sure its easy, if its your mom's phone, dont have a unsupported non-factory rom on it... the REAL awnser is: wipe EVERYTHING, even your ext partition, and reinstall base, then CM...
Click to expand...
Click to collapse
Nah I think he should install the RC29...just kiddin you should use Super-D or Enom's official. I kinda assumed this thread was about some kind of fix for browser problems.
Ace42 said:
Nah I think he should install the RC29...
Click to expand...
Click to collapse
well, the RC29 might actually force a wipe... and would update itself and have OTA keys... honestly probably not a bad way to go... Super-D is good, but honestly dont notice a huge difference between that and CM.
it was even not working when i reverted to complete stock. could this be a problem with the phone itself? Maybe revert to stock again and take it in to t-mo?
There should not be any problem with leftovers from previous roms, since i completely wipe data and ext as i mentioned in my first post.
Moderators, please move this to correct section. this seemed like the correct section since this seems to be more involved in the development side of things. Definately not Accessories but more involved than Q&A. Thank you
Phone ><---USB--->< PC/Laptop/Mac
adb logcat
watch text fly up screen ... make browser crash
quick !!!!! take a picture of that text.............
if you don't have a usb cable handy, a PC or the time to figure out how to get adb installed
go to terminal emulator on phone, and type
logcat|tee /sdcard/logcat.txt
( get the pipe "|" with alt then s )
make browser crash
go back to terminal press ball then C
Edit : the ball can be a bit of a pain, when in term do menu --> preferences --> control key , and set to which key you prefer, I like left alt as ctrl[\i]
now have a look at the logcat.txt file, it
less /sdcard/logcat.txt
you could just do logcat > /sdcard/logcat.txt
but it doesn't look as geeky
NB use >> instead of > to append > will make new file >> will add to file
to append to file with tee use tee -a file.txt[\i]
and yeah, wrong section
thank you very much for your assistance and the little linux command briefing ha
i decided to try every sort of wipe, repair, etc and do it multiple times. probably didn't do anythin, but worth a shot ha.
Ended up working! I removed the ext and swap partitions, wiped anything i could multiple times, flashed super d, didn't work, wiped a bunch, flashed htc recovery image, then cyan, and presto. For whatever reason it finally worked.
Shoulda done the logcat and posted it so y'all could see whatever was going on and hopefully help someone out later. but all is resolved for now.
If there is a next time, I will post in Q&A. I want to thank everyone for their input and wish all a good night.
-Eric
Moved as not Android Development.