• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root For 2.2 Market issues, use this mod.

LiquidHonesty said:
Huh? You didn't have to be rooted to install the update....

Can't use root explorer because I'm not rooted :-(
Click to expand...

Sorry My understanding was you needed to be rooted. The directions i saw made sure you were first. I didn't realize it worked unrooted. Good to know though.
 
LexusBrian400 said:
I AM Beesley :) Check my signature on XDA.

Beesley is my IRC name.
Click to expand...

Dude, that is too funny! Competing with yourself! lol :D

LexusBrian400 is well-known to us old Eris guys who also occasionally peruse the XDA threads. He is a well-respected and sage member in both sites (and probably many more).

Thank you for the valuable information about the build.prop.
 
I just made the change with root explorer and it worked great. Get the new build prop on your sd card. Find it in root explorer and copy it. Go to system and then paste the new build prop (click r/w at the top first). It will ask you if you want to replace the current build prop. Replace it and reboot. I have full market now and it was super easy. DO NOT delete the current build prop just paste the the new one. Thanks for all who posted this.
 
elbacker said:
I just made the change with root explorer and it worked great. Get the new build prop on your sd card. Find it in root explorer and copy it. Go to system and then paste the new build prop (click r/w at the top first). It will ask you if you want to replace the current build prop. Replace it and reboot. I have full market now and it was super easy. DO NOT delete the current build prop just paste the the new one. Thanks for all who posted this.
Click to expand...

+1

Request for OP to include that when using root explorer, do not delete the original build.prop. Just paste the new one over it.

When I deleted the file before pasting the new one, I couldn't get past the M icon when booting. I had to flash SBF and then restart everything.
 
Wow, I'm getting a headache trying to figure all of this stuff out, but I'm doing a LOT of reading before trying any of this stuff. I am having the market issue where I can't see protected apps, so I'm thinking about doing the prop replacement to get the market back to normal.

However, I have several questions before starting this process. Before I ask, I'll state that I went from an unrooted phone to begin with. Then I rooted using Universalandroot. Then I moved my SU to the xbin before applying the 2.2 update. I have remained rooted and have 2.2 installed. Everything have pretty much been working great except for this market issue, so here are my questions:

1) If we do this mod, then we are identifying our phones as a Droid 2, right? Will this have any ramifications when updates are pushed to the Droid X or Droid 2? I mean, it won't accidentally push an update for the Droid 2 to our phones, will it? And what will happen when the official Droid X update is pushed OTA?

2) When the official Droid X OTA update is pushed out, can we then go back and edit the prop file again to properly identify the phone as a Droid X on Froyo? Or should we just leave it with this modified prop file?

3) So far, I have done everything on the phone itself since I am on a Mac. So to do this prop file replacement on the phone only, I have to download the prop file from my phone, open Root Explorer, turn R/W access on, and then overwrite the current prop file with the downloaded one?

4) I'm reading about doing the bootstrap backup but I really don't know what it does exactly or how to do it. But I'm thinking it would be a good idea to do it before modifying this prop file just in case something goes wrong. I'd really like to avoid having to do an sbf because that sounds even more difficult!

Thanks for any help in answering these questions!
 
Piiman said:
BTW Chrome to phone works great for stuff like this. I open this in web browser hit Chrome to phone button and bam! now it's on my phone and I can download it directly and not worry about transferring it later.

It's magic I tell magic! :D
Click to expand...

I tried this but it doesn't seem to download properly. I sent the forum thread link to my phone using Chrome to Phone. It opened the browser on my phone and then I clicked on the clean download link, but when the download starts, it just downloaded a prop.txt file instead of the actual file. Am I doing something wrong?
 
Travisimo said:
Wow, I'm getting a headache trying to figure all of this stuff out, but I'm doing a LOT of reading before trying any of this stuff. I am having the market issue where I can't see protected apps, so I'm thinking about doing the prop replacement to get the market back to normal.

However, I have several questions before starting this process. Before I ask, I'll state that I went from an unrooted phone to begin with. Then I rooted using Universalandroot. Then I moved my SU to the xbin before applying the 2.2 update. I have remained rooted and have 2.2 installed. Everything have pretty much been working great except for this market issue, so here are my questions:

1) If we do this mod, then we are identifying our phones as a Droid 2, right? Will this have any ramifications when updates are pushed to the Droid X or Droid 2? I mean, it won't accidentally push an update for the Droid 2 to our phones, will it? And what will happen when the official Droid X update is pushed OTA?

2) When the official Droid X OTA update is pushed out, can we then go back and edit the prop file again to properly identify the phone as a Droid X on Froyo? Or should we just leave it with this modified prop file?

3) So far, I have done everything on the phone itself since I am on a Mac. So to do this prop file replacement on the phone only, I have to download the prop file from my phone, open Root Explorer, turn R/W access on, and then overwrite the current prop file with the downloaded one?

4) I'm reading about doing the bootstrap backup but I really don't know what it does exactly or how to do it. But I'm thinking it would be a good idea to do it before modifying this prop file just in case something goes wrong. I'd really like to avoid having to do an sbf because that sounds even more difficult!

Thanks for any help in answering these questions!
Click to expand...

Yes get bootstrap recovery make sure it is version 1.0.0.3, open it press bootstrap recovery, get rom manger from the market, open it, press flash clockwork at the top, then go down to backup and backup your current set-up.

Then you can do everything through root explorer make sure to overwrite the build.prop not delete and replace.

And the next update is gingerbread:D so... but everyone will have to cross that bridge when it comes

Anyways you are going to be flashing custom ROMs soon so you will get a new build.prop all the time:p, this is just temporary
 
Travisimo said:
Wow, I'm getting a headache trying to figure all of this stuff out, but I'm doing a LOT of reading before trying any of this stuff. I am having the market issue where I can't see protected apps, so I'm thinking about doing the prop replacement to get the market back to normal.

However, I have several questions before starting this process. Before I ask, I'll state that I went from an unrooted phone to begin with. Then I rooted using Universalandroot. Then I moved my SU to the xbin before applying the 2.2 update. I have remained rooted and have 2.2 installed. Everything have pretty much been working great except for this market issue, so here are my questions:

1) If we do this mod, then we are identifying our phones as a Droid 2, right? Will this have any ramifications when updates are pushed to the Droid X or Droid 2? I mean, it won't accidentally push an update for the Droid 2 to our phones, will it? And what will happen when the official Droid X update is pushed OTA?

2) When the official Droid X OTA update is pushed out, can we then go back and edit the prop file again to properly identify the phone as a Droid X on Froyo? Or should we just leave it with this modified prop file?

3) So far, I have done everything on the phone itself since I am on a Mac. So to do this prop file replacement on the phone only, I have to download the prop file from my phone, open Root Explorer, turn R/W access on, and then overwrite the current prop file with the downloaded one?

4) I'm reading about doing the bootstrap backup but I really don't know what it does exactly or how to do it. But I'm thinking it would be a good idea to do it before modifying this prop file just in case something goes wrong. I'd really like to avoid having to do an sbf because that sounds even more difficult!

Thanks for any help in answering these questions!
Click to expand...

Bootstrap is easy. Get it from the market (2 bucks). Install it, open it, click bootstrap recovery button---wait---success---now click the reboot recovery button. It will boot you into recovery mode where you can backup your current state. once it i done backing up in reboot recovery, just hit reboot and you have yourself a backed up 2.2

I want to do an SBF just to do it. Get some practice, but I don't wanna do it just to do it at the same time, heh.
 
droider13 said:
Yes get bootstrap recovery make sure it is version 1.0.0.3, open it press bootstrap recovery, get rom manger from the market, open it, press flash clockwork at the top, then go down to backup and backup your current set-up.

Then you can do everything through root explorer make sure to overwrite the build.prop not delete and replace.

And the next update is gingerbread:D so... but everyone will have to cross that bridge when it comes

Anyways you are going to be flashing custom ROMs soon so you will get a new build.prop all the time:p, this is just temporary
Click to expand...

Okay, I downloaded Bootstrap Recovery and clicked on the first option. It said "success" a second later. Now you and bosox2k1 said two different things for the next step. You said to get rom manager and bosox2k1 said to just click on the second option in Bootstrap and create the backup after rebooting. I'm not sure what to do next. I have no interest at this point in custom roms when they come out... I just want to back everything up before I do this prop file replacement.

So I'm not sure if I need Rom Manger or not?
 
Travisimo said:
Okay, I downloaded Bootstrap Recovery and clicked on the first option. It said "success" a second later. Now you and bosox2k1 said two different things for the next step. You said to get rom manager and bosox2k1 said to just click on the second option in Bootstrap and create the backup after rebooting. I'm not sure what to do next. I have no interest at this point in custom roms when they come out... I just want to back everything up before I do this prop file replacement.

So I'm not sure if I need Rom Manger or not?
Click to expand...

It's essentially the same thing. If you do it through ROM manager, it will reboot your phone and bring to you recovery and do everything on its own.

My way, you do it yourself. Go into recovery reboot, click on backup/restore--choose backup, sit back and watch and then hit reboot when it is completed.
 
Candroid said:
Thanks Man, What I did the correct the video was just change my settings to 780 x 480. and play back is just fine. just my 2. I am happy with it. I'd rather have insane quadrant and linpack scores and a phone that responds on demand!!! ;)
Click to expand...

I'm curious, where did you change your settings at? Please share :)

Edit: nevermind, found them. Kinda sucks that you cant record in HD with that mod just for a higher quadrant score and no real time performance increase. The reason qaudrant is scoring so high is because it is skipping the H.264 encoding all together. Its a fake score. Just an FYI
 
I keep getting permission denied...I've done the OP version and this version as well:

"adb shell"
"su"
"mount -o remount,rw -t yaffs2 /dev/mtd/mtdblock4 /system"
"exit"
"exit"
"adb push build.prop /system/build.prop"

 
draconius said:
I keep getting permission denied...I've done the OP version and this version as well:

"adb shell"
"su"
"mount -o remount,rw -t yaffs2 /dev/mtd/mtdblock4 /system"
"exit"
"exit"
"adb push build.prop /system/build.prop"

Click to expand...

I don't know, does it matter that you hit "se" initially? Or was that corrected once you input the correct "su"?


EDIT- No that doesn't matter, I don't know what the issue is. Wish I did!
 
draconius said:
I keep getting permission denied...I've done the OP version and this version as well:

"adb shell"
"su"
"mount -o remount,rw -t yaffs2 /dev/mtd/mtdblock4 /system"
"exit"
"exit"
"adb push build.prop /system/build.prop"

Click to expand...

ummm.... you dont exit first. do it this way :)


"adb shell"
"su"
"mount -o remount,rw -t yaffs2 /dev/mtd/mtdblock4 /system"
"adb push build.prop /system/build.prop"
"exit"
"exit"

and if that doesnt work... dont do it in the shell


adb remount
adb push build.prop /system/build.prop
exit
exit
 
LexusBrian400 said:
ummm.... you dont exit first. do it this way :)


"adb shell"
"su"
"mount -o remount,rw -t yaffs2 /dev/mtd/mtdblock4 /system"
"adb push build.prop /system/build.prop"
"exit"
"exit"

and if that doesnt work... dont do it in the shell


adb remount
adb push build.prop /system/build.prop
exit
exit
Click to expand...
I'll try doing it before the exit...if not I'll do the remount, push, exit.
 
LexusBrian400 said:
ummm.... you dont exit first. do it this way :)


"adb shell"
"su"
"mount -o remount,rw -t yaffs2 /dev/mtd/mtdblock4 /system"
"adb push build.prop /system/build.prop"
"exit"
"exit"

and if that doesnt work... dont do it in the shell


adb remount
adb push build.prop /system/build.prop
exit
exit
Click to expand...

No go on either... :(
See the screen cap for errors:


Why wouldn't I have permission to do any of these?!?!?

I'm in PC Mode
 
bosox2k1 said:
It's essentially the same thing. If you do it through ROM manager, it will reboot your phone and bring to you recovery and do everything on its own.

My way, you do it yourself. Go into recovery reboot, click on backup/restore--choose backup, sit back and watch and then hit reboot when it is completed.
Click to expand...

Thanks again! I skipped the rom manager and did it as you described. So this means that if something goes wrong on my droid x, I can always recover to the state I was in when I did the backup?

I was also able to replace the build.prop file (carefully) and the market seems to be showing protected files again! Woot!

As I asked earlier, will this affect PTA updates? I mean, I know we'll probably be skipping them for now anyway since we are rooted and already have froyo. But when ota updates ARE sent out, will the droid 2 ones be sent to us since we are identifying our phones as droid 2 devices? Or does this only apply to how the market sees our phone?
 
Thanks again! I skipped the rom manager and did it as you described. So this means that if something goes wrong on my droid x, I can always recover to the state I was in when I did the backup?
Click to expand...

No problem! Supposedly if something goes bad when you are on 2.2, you can go into Koush's recovery and restore a backup. I have yet to try it, but I assume it works---or I hope it works.

For instance, it would not work if you SBF'd to 2.1, pulled battery and somehow got into Koush's recovery screen and asked to restore then. I was told if you try to restore a backup that has a different kernel than what you are running---it'll brick your phone.

So TLDR: Yes restoring a 2.2 backup should work if you are in 2.2 currently.
 
bosox2k1 said:
No problem! Supposedly if something goes bad when you are on 2.2, you can go into Koush's recovery and restore a backup. I have yet to try it, but I assume it works---or I hope it works.

For instance, it would not work if you SBF'd to 2.1, pulled battery and somehow got into Koush's recovery screen and asked to restore then. I was told if you try to restore a backup that has a different kernel than what you are running---it'll brick your phone.

So TLDR: Yes restoring a 2.2 backup should work if you are in 2.2 currently.
Click to expand...

Yeah, looks like at least a couple of people are having trouble restoring from a Nandroid backup (Blur username and password error), though it sounds like they are trying to go back to 2.1.

http://androidforums.com/all-things-root-droid-x/154544-blur-service.html

My main goal is to only go forward! Unless I am forced to, I really don't want to have to reinstall everything or redo all of my customizations.

In fact, unless there is a significant difference between the leaked 2.2 update and the official one, I'm quite content. The only two issues I seem to have had are the market problem (no protected apps) and the Force Close when clicking on the battery icon under Battery Manager (which seems to come and go for whatever reason).

Now then, once the official version is out and it gets rooted, how difficult will it be for those of us who have installed the leaked version? Will we be able to do something similar by going into Bootstrap recovery and installing another update.zip? I realize this might not happen right away after the official update comes out.
 
easiest way

with computer

adb push build.prop /sdcard
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtd/mtdblock4 /system
mv /sdcard/build.prop /system

or terminal emulator

put build.prop on sdcard
open terminal
su
mount -o remount,rw -t yaffs2 /dev/mtd/mtdblock4 /system
mv /sdcard/build.prop /system
 
You must log in or register to reply here.
Back
Top Bottom