Related
Hi all,
I installed the SuperHero V3 Mas in my G2 (magic 32b) and it run so good and faster than all of others roms that I have tried. The problem that is the wifi cant turn on (it's normal this rom is made for G1).
Someone can help me to solve this problem and make this rom able to all G2 users.
The trick is to get and push the working wlan.ko (I think its in the sperhero 3 thread already) now why don't you tell me the trick you did to make this the fastest so I can try it
try pulling the wlan.ko file from a magic rom and pushing it through adb to /system/lib/modules, and im guessing its the fastest because he might have the magic that has the 288mb ram instead of 192, so virtually identical to the hero.
thank you for your response, I will try this right now
Thas is not work
failed to copy 'wlan.ko' to '/system/lib/modules/wlan.ko': Read-only file system
I tried to change file access using chmod and I go this message:
failed to copy 'wlan.ko' to '/system/lib/modules/wlan.ko': Read-only file system
please help
Ps: adbd is already running as root
co2gaz said:
Thas is not work
failed to copy 'wlan.ko' to '/system/lib/modules/wlan.ko': Read-only file system
I tried to change file access using chmod and I go this message:
failed to copy 'wlan.ko' to '/system/lib/modules/wlan.ko': Read-only file system
please help
Ps: adbd is already running as root
Click to expand...
Click to collapse
Try "adb remount" to mount /system as writeable.
Thank you for this information.
I tried it. the copy work OK, but the wifi problem steel here
I should have been more clear because pulling the file from any Rom isn't how you go about it. It has to match the kernel you are on and often even be further modified to the build. I think I heard either the wlan from superhero2 or the one from an earlier jachero worked. I just forget what one. Give me some time ill upload it. I had fixed and re-released this build.
Edit: Wlan.ko attatched. Belongs in system/lib/modiules
I thank you so math for your help,
I putted the file in my phone and i restart it, but wifi steel not work
Hi, I tried with JCAHero and it's same, very great rom, run so good on my magic G2, but the wifi not work
co2gaz said:
I thank you so math for your help,
I putted the file in my phone and i restart it, but wifi steel not work
Click to expand...
Click to collapse
Use the one I posted in this thread. I edited the post above ya. It should work then.
Thank you, I putted the new wlan.ko on my phone. now it seems better but it not work, now when I want to start wifi it show wifi is turning on during 4 or 5 sec, after that it show unable to start wifi.
if it was some link to explain how I can modify wlan.ko, maybe I can do some things (I'm java developer and I think it's native kernel file)
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
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?
For those of you having trouble seeing protected apps, I modified our fingerprint in the build.prop. What this does is spoofs the market into thinking its seeing a Droid 2 (with Froyo) It worked for me, let me know if it does for you.
1. Put build.prop into your AndroidSDK\TOOLS folder
2. Connect via USB.
3. CD (Navigate) in CMD to your tools folder
Mount your /system (adb remount) works for me
Copy and paste this
4. adb remount
5. adb push build.prop /system/build.prop
6. adb reboot
To test if you need this before you push the build.prop fix, search the market for Us Bank. If only 2 or 3 show up, you are not getting the full market. After this fix, you should see 10 items listed when you search for Us Bank.
Hope this helps.
2.2 Market Fix Build.Prop -- WITH STAGEFRIGHT=TRUE
This can also be done via Root Explorer.
Edit: Here is a "clean" build.prop for those of you who do not want the stagefright fix (which breaks video playback) Sorry, I was not aware it did that. Thank you.
Non Stagefright Build.prop -- WITH STAGEFRIGHT=FALSE
For everyone flipping out about Birdmans tweet and you want the stock build.prop, here ya go
Stock Build.prop -- WITH NOTHING! STOCK!
You only need the stock one if you ever plan on doing a factory reset. But, you also cant do a factory reset if you have removed or renamed apps so I feel that should be mentioned. If you've done any modding and you are planning on upgrading, your best bet is to always use the SBF anyway. I dont think birdman realizes the panic he sets in with one little tweet. Factory resets suck anyway. But then again... "you decide..."
Thanks to Jcase for giving me the original idea way back when. I just basically applied his Eris Market Fix to work with our phones.
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Found a fix
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Zaphod-Beeblebrox said:
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Click to expand...
Click to collapse
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
elkniwcire said:
i must say i take no responsibility if this causes problems but this worked for me. Do a search in the market for "eris market fix." it was designed for the eris but works just fine on my droid x. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but i assume most everyone on froyo already is rooted.
Click to expand...
Click to collapse
yes this worked for me aswell thank you
Yes this method definitely works. I have market working now and can search for protected apps etc.
elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
he was just explaining where the idea comes from i think... You'd have to be crazy to use the eris market fix app on a droidx, just simply edit the build.prop fingerprint line.
I just used the root explorer meathod and now it wont boot.
I downloaded the file.
renamed my build.prob to build.prob/bak
placed the new build.prob in the system folder
rebooted and now after the M screen it just goes to a black screen with the backlight lit. Wont boot up. Im learning adb so this may be a noob question but can I access adb if the phone wont boot all the way up. That way I could change the build.prob back
Edit Delete Post: Im just retarted haha .prop not .prob :/
Could you plz give us some details on doing this with root explorer. Thanks
Prolly simple but I did try moving current build file then renaming and pasting yours without success doing us bank search. Also rebooted cleared cache and market history prior to search. Appreciate any help with doing this via root explorer.
LexusBrian400 said:
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
Click to expand...
Click to collapse
LexusBrian400 said:
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
Click to expand...
Click to collapse
I took a brief look at each file and I really don't understand how I got into trouble. As I said, I had not yet started doing any mods, just trying to install a few apps.
While I'm no computer or phone neophyte, I don't profess to be up to speed on Android yet. I do typically read through instructions pretty well, and search out multiple sources/explanations so I have a better 'understanding' of what I'm doing, rather than just "parrotting" the steps.
Having said that, I would like to know the difference between using 'adb remount' and the instructions I used in my first post. Is that just the difference in doing this via a shell command and not? ie, they perform the same action, just from a different starting point?
As for the Eris file, I did download that and all seems to be OK right now.
Sorry ahead of time for a possibly stupid question but I just wanted to be sure. Do you have to be rooted to do this fix?
Yes, it requires an edit to a file that you can only be edited when rooted
elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
This works for me...thanks!
OP has been updated with original build.prop
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
will2live said:
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
Click to expand...
Click to collapse
Just use the non-stagefright one.
Just like the post says, stagefright breaks HD video playback for SOME people. However some people dont care and just want higher quadrant scores, so they use the stagefright=true build.prop
Use the =false version for better stability.
Thanks for the reply.