Database Develop

[TIP] Running Dwang on Stock SPL? - If you have a problem loading themes...

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?

Help to remove disastrous apk - please android Wizards

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

[FIX] For 2.2 Market issues, use this mod - *Updated* with Stock Build.prop

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.

[Q] Remove Superuser Permission Icon

I used universal androot to root my phone and I want to unroot it. I can't get rid of the superuser permission icon with the skull and crossbones. How can I get rid of that to return my phone back to normal?

The only way I was able to do this was to flash the old ERE27 passimg then the FRF91 Rom. Yes this wipes everything and takes your phone back to stock.
Not sure if anyone else was able to remove the SU icon and app without a full reflash back to the old version.

There has to be an easier way than that.

Get root explorer and go to system/app/superuser delete that is the easiest way
Sent from my Nexus One using XDA App

Is root explorer in the market? Priced in ₤.? I have android mate. Can I do it with that? Or another free app? I couldn't find a delete option in android mate.

rm is the delete command in linux. /system/app is the directory. Just use terminal and delete the apk. Don't forget to mount the /system/ dir as rw. Google should help you with that.

evilkorn said:
rm is the delete command in linux. /system/app is the directory. Just use terminal and delete the apk. Don't forget to mount the /system/ dir as rw. Google should help you with that.
Click to expand...
Click to collapse
That's pretty much Greek to me. Are there some instructions to do that somewhere? I just want to put my phone back to normal.

http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=remove+system+applications+android

I think you can delete pretty much anything using titanium backup while rooted. Then, unroot and become a slave to your device.

NO ONE KNOWS HOW TO REMOVE THIS DAMN ICON? I can't delete it using Titanium Backup or Android Mate

tardman91 said:
NO ONE KNOWS HOW TO REMOVE THIS DAMN ICON? I can't delete it using Titanium Backup or Android Mate
Click to expand...
Click to collapse
Not anyone that's been in this thread...LoL!

tardman91 said:
NO ONE KNOWS HOW TO REMOVE THIS DAMN ICON? I can't delete it using Titanium Backup or Android Mate
Click to expand...
Click to collapse
Do you still have root?
Actually why would you want to unroot?

Tardman
I promise you I went through this all. SU is not an "app" and cannot be removed like any app can. It becomes part of the ROM. As far as I could tell. It wont even go away if you re-flash the stock ROM.
The only way I got rid if it was through installing the passimg from boot so the whole system wiped. Then flashed froyo clean.
Everything else, including all mentioned here, did not work.
And it only takes about 10 minutes to get through the process.
Sent from my Nexus One using Tapatalk

I unrooted. If I just leave it there it doesn't affect anything, right?
I tried to reflash froyo clean, but I kept getting some kind of errors (see my Restore Nexus One for Dummies thread). Oh well.
I want to unroot so that I get all of my over the air updates without any hassles. I thought about jumping ship to the new Cyanogen Mod now that it's a stable release, but I just don't feel comfortable enough messing with the phone like that just yet. Although tonight I did get adb and fastboot working, so I'm making progress. Maybe one day...

tardman91 said:
... I thought about jumping ship to the new Cyanogen Mod now that it's a stable release, but I just don't feel comfortable enough messing with the phone like that just yet. Although tonight I did get adb and fastboot working, so I'm making progress. Maybe one day...
Click to expand...
Click to collapse
All it takes is patience.
I was once where you are. Afraid of messing up my expensive phone.
I followed enough threads. Read enough wikis. Kept up with the Android™ blogs, and now?! I'm pretty good at this stuff.
Good enough that I rooted, and flashed a new ROM on a friends EVO today.
Although I DID BRICK IT for a while, I was confidant that I would find the solution on these forums.
Chance are it's happened to MANY MORE PEOPLE, aside from you and I.
No need to start a new thread. It's been asked before.
SEARCH, and YE SHALL FIND!

I used universal androot to root my phone an i selected unroot just to see if it actually unroots ur phone an when it said my phone wasnt rooted anymore i noticed that superuser was gone. So unrooting deleted superuser for me

chris6278 said:
I used universal androot to root my phone an i selected unroot just to see if it actually unroots ur phone an when it said my phone wasnt rooted anymore i noticed that superuser was gone. So unrooting deleted superuser for me
Click to expand...
Click to collapse
The problem with that is, Universal Androot no longer works after the FRG22D update. I forgot to unroot before updating and now universal androot can't unroot nor can I remove the superuser.apk since I'm no longer rooted...even though androot says I am and can't unroot. I guess universal androot is dead because I've been watching for an update and there has been no activity for 2+ months. I only used androot to enable the wireless tether option.

SuperOneClick...
Sent from my Nexus One using XDA App

My first post This worked for me after hours of research
Hey I'm new here and wow this forum has ton of information. Thanks all for sharing!
Hope this help!
But for this specific problem (superuser permission icon) won't delete. After hours of looking and trying multiple solutions, only one worked. The other ones deleted it, but as soon as I reformat my phone it would come back. Got this from another forum (travisFC thx!!) and it WORKS!!
I used Z4root (off the market) to re-root, fantastic app!!
1. Re-root your phone (yes make sure your phone is "jailbroke" again) and download an app in the market called Terminal Emulator (its free)
2. Now type the following in the terminal emulator app. One line at a time and pressing enter after each line
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
rm Superuser.apk
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
3. Sync phone with google (in the settings). (Not sure what the hell this meant, but sent an email to myself, don't think you need this step.)
4. Reboot phone
5. App should now be gone, but you will probably see the NEW superuser icon (widget)
6. Reapply unrooted OS (Z4root select unroot) and wipe device .
7. Should be unrooted and the app will be gone..you can check your root status by using the Terminal Emulator app and typing "su" it should say permission denied.
FYI - I'm on Rogers Captivate.
Hope this helps...what a headache.

get rid of superuser icon
Want to rid yourself of the superuser icon and be able to take your phone back to provider without worry? Here's how and it's less steps than Thumpers way (no disrespect intended).
1. I'm assuming you have unrooted your phone and just have the annoying su icon.
2. Download z4root from market. root your phone with it. Use the "temporary root" bar.
3. Once rooted go in and out of a few apps, then go back to z4oot and press it. It will ask for superuser permission and say yes.
4. Z4root will open and then tap on the "unroot" bar and that's it. It removes everything including superuser icon.
Enjoy.
By the way I have Galaxy S Vibrant i9000M with 2.1 eclair.

Want to try to avoid 1.3.0 OTA? Modify build prop?

Hey everyone, I'll up front say I'm more a user than a tweaker, so right now my NC (and my wifes) work awesome. I am currently on CM7, but my wife and many folks need to use the stock ROM and until a clean way to update with autonoot and such comes out, hopefully this is useful.
Clockwork Mod won't install an OTA, but I have a feeling that it'll still download it and try to install it, and I'm afraid it will try to install it over and over as long as the file is there. So moving to CWM to avoid the OTA is out.
Renaming otacerts doesn't work, lots of accounts of that.
But in my experience, OTAs always compare the build prop to see if they need to OTA, so what I'm going to do to my NC and my wifes NC is modify the build prop to the new settings and see if that avoids the OTA.
BTW, I know Nookie Froyo, CM7 etc won't OTA, etc, so now that's out of the way....
Due to multiple reports that using Root Explorer has somehow screwed up the system requiring users to manually re-copy their old build.prop back, I suggest you DO NOT use Root Explorer to do this.
First thing is look in /media for the uploader, in case it's already downloaded. Delete it if it's there! If you're paranoid, check when you're done with the following too, just in case it snuck in while you were editing
Get the new build.prop from here:
If you're still on Eclair: http://dl.dropbox.com/u/334233/build.prop-1.3.0-eclair
If you're on Froyo: http://dl.dropbox.com/u/334233/build.prop-1.3.0-froyo
Remount the system r/w
Code:
adb shell
su
busybox mount -o remount,rw /dev/block/mmcblk0p5 /system
Push the new build.prop to your system
Code:
adb push build.prop-1.3.0-[COLOR="Red"]YOURBUILD[/COLOR] /system/build.prop
Note you need to replace YOURBUILD with the appropriate build, Froyo or Eclair, or whatever you named the build.prop..
Now your NC should have thew new build.prop, so now reboot. When you reboot, you should get a pop-up message with a green N saying you've updated to 1.3, but you should not see any update progress dialogs or any indication there was an actual update. Hopefully this makes it not try to OTA to 1.3.0! Please report back! It worked for 1.0.1 with the 1.1.0, as well as the 1.2.0 update out there, and it should work for 1.3.0.

Below is for old 1.2.0 information, don't use this unless you're sure you need to!
Get the new build.prop from here: http://dl.dropbox.com/u/334233/build.prop-1.2.0
Remount the system r/w
Code:
adb shell
su
busybox mount -o remount,rw /dev/block/mmcblk0p5 /system
Push the new build.prop to your system
Code:
adb push build.prop-1.2.0 /system/build.prop

Once I get a little feedback on this, I'm going to move it to the NookDevs wiki, just don't want to put nonsense there if that's what it is I've done this to both my NC and my wifes, no problem so far, and hopefully it avoids the OTA.

done - we'll see what happens next ....

newbie
Hello
I am a newbie at all of this and used the autonooter with 1.01. That's about as deep as i planned going with the nook, enough to read, play some games and surf the web. So my question is for someone like me that really may not have the skill as most of you, what would be the easiest way to prevent an ota update that will unroot my nook? Thanks for any advise

JF-WS6 said:
Hello
I am a newbie at all of this and used the autonooter with 1.01. That's about as deep as i planned going with the nook, enough to read, play some games and surf the web. So my question is for someone like me that really may not have the skill as most of you, what would be the easiest way to prevent an ota update that will unroot my nook? Thanks for any advise
Click to expand...
Click to collapse
I'll keep revising the instructions in the first post, but that's so far the only theory that hasn't failed yet... So get adb to work and follow the instructions. You can do it over Wifi, so even if USB isn't working out for you due to your OS, the Wifi ADB widget on the Market will work.
How to use ADB itself, you can google.. It's fairly straightforward. Basically you'll just need to adb connect ip : port once you know it, the Wifi ADB widget tells you when it sets up.

FYI, I just did all of this from Root Explorer on the device. I snagged yer file from your dl.dropbox link, copy it over via root explorer, and set the rights. When I restarted, the little green n told me I had recently updated.
Maybe we can bypass optional future updates by changing our version to something really high like 1.99?

Yes I know I never say anything on here but will now. I have used something like this on before I I do think this will work just fine as the Nook already things it's updated so when it checks it's going to see that it is already updated.
Now as to what BN will do in a week or so who knows. We just need some more support for roms and so on for the nook and we will be good to go.

ClockworkMod has no bearing on the OTA; it's not the recovery that attempts to download and install OTAs.

Used your download link to install it. Says I updated to 1.1.0. Thanks

danguyf said:
ClockworkMod has no bearing on the OTA; it's not the recovery that attempts to download and install OTAs.
Click to expand...
Click to collapse
Um, yeah... Let me explain further I guess?
B&N Components decide it needs an update, downloads it
B&N components see the update is downloaded, sets up the OTA update, reboots
Clockwork Recovery does NOT update
System boots
Repeat step 2 - 5 forever?
That's what I meant by "Clockwork won't install an OTA" and such.

MattJ951 said:
Used your download link to install it. Says I updated to 1.1.0. Thanks
Click to expand...
Click to collapse
Check your software version? Pretty sure it wouldn't show any updates, mine nor my wifes did. I think you probably already got the OTA.

khaytsus said:
Check your software version? Pretty sure it wouldn't show any updates, mine nor my wifes did. I think you probably already got the OTA.
Click to expand...
Click to collapse
Copied the new build and rebooted. I received a upgrade notice in the notification bar that said I upgraded to 1.1. I checked the new software version for the nook and it also says 1.1. I know I have not gotten anything ota because I have watched all afternoon. Thanks for this. Only time will tell when the real update hits my nook.

bdcrim said:
Copied the new build and rebooted. I received a upgrade notice in the notification bar that said I upgraded to 1.1. I checked the new software version for the nook and it also says 1.1. I know I have not gotten anything ota because I have watched all afternoon. Thanks for this. Only time will tell when the real update hits my nook.
Click to expand...
Click to collapse
Yes, mine too! interesting! Maybe it fooled it, it just didn't expect it to do that

khaytsus said:
Yes, mine too! interesting! Maybe it fooled it, it just didn't expect it to do that
Click to expand...
Click to collapse
Thanks again.

khaytsus said:
Yes, mine too! interesting! Maybe it fooled it, it just didn't expect it to do that
Click to expand...
Click to collapse
I just checked the about settings and it also says 1.1.0 . If im on 1.1.0 I don't really mind since my device is still rooted and works identically to how it did a day ago. I'm guessing it pulls the about settings pulls the data from the build.prop every reboot

Maybe in the doctored file we should update the build to something like 1.1.5 so we have something in "device info" that says the device is build 1.1.5 instead of 1.1.0 which would denote the OTA... that way, if somehow the OTA does install it will change to 1.1.0 and we'll have evidence in the setting menu (unfortunately, of failure of the method).

skaman77 said:
Maybe in the doctored file we should update the build to something like 1.1.5 so we have something in "device info" that says the device is build 1.1.5 instead of 1.1.0 which would denote the OTA... that way, if somehow the OTA does install it will change to 1.1.0 and we'll have evidence in the setting menu (unfortunately, of failure of the method).
Click to expand...
Click to collapse
Good thought. Do you want to flip a coin or draw straws?

As soon as I saw the thread about the 1.1.0 update today, I turned my WiFi off. There was no zip file in my /media folder or on root when I made the changes to the build.prop file. When I rebooted, I received a notice in the bar that my Nook Color software had been updated. WiFi is still off, but I am going to turn it back on and see what happens.

i also updated file lines thru root explorer and gave me massage that i had been updated. crossing fingers