Database Develop

New Facebook App 1.1.2 on Cyan 4.2.8 Install error!

Getting
"Package file was not signed correctly"
Is this because i had a non market version of facebook installed before?

DownloaderZ said:
Getting
"Package file was not signed correctly"
Is this because i had a non market version of facebook installed before?
Click to expand...
Click to collapse
Yes. Uninstall and try again.

I am also getting an install error.
I have tried to uninstall the existing 1.1.1 version using the Expsetup but still won't install.
I'm thinking that clearing all associated data for facebook would help but don't know the directories etc that I would need to delete.
phil

That did it, thanks!
Chahk said:
Yes. Uninstall and try again.
Click to expand...
Click to collapse

Where to get Facebook 1.1.2?

I unistalled V1.1.1 but still cant install new version 1.1.2!!! went to aplication manager and found a file that says com.facebook.katana but doesnt let me do anything with it.
Any ideas?

If you're having problems uninstalling, that's because you used an update.zip and it is installed in the system/app folder. You have to use terminal or adb to mount the folder as rw to remove it.
My question, though, is it better than the one from droid? Cuz if not then I don't want to waste my time updating...

mrandroid said:
Where to get Facebook 1.1.2?
Click to expand...
Click to collapse
Android Market.

Anyone mind upping the APK? Removed all traces of FB from my phone and packages.xml and it still refuses to install.

Jonno12345 said:
Anyone mind upping the APK? Removed all traces of FB from my phone and packages.xml and it still refuses to install.
Click to expand...
Click to collapse
http://www.myhangoutonline.com/downloads/?did=15

Most importantly would be to ask how do you get your system back to normal so you can install updates later.
I know at one time I messed with my prop file to install the Nav at one time. I wonder if that could be a problem. I removed the Facebook app, but it told me it wasn't compatable so I wonder if it that prop file is affecting anything.

Put the original build.trout.prop file back in the /system folder. Deleted the old Sholes/droid version via the market and it installed without a hitch.
It doesn't seem to like a modified prop file.
To me personally it looks just like the droids version except the white bar at the top is fixed.
Heres the line you want to change back.
ro.build.fingerprint=tmobile/kila/dream/trout:1.6/DRC83/14721:user/ota-rel-keys,release-keys
or upload this buid.trout.prop file to your /system folder. Just drop the .txt from the end.
EDIT.
After fighting a bit with the prop file I ended up just reflashing the rom that I originally installed which over wrote the modded prop file. Now I'm back to the orginal file and then I used the APK provided here.
http://forum.xda-developers.com/showpost.php?p=5147596&postcount=16
After that I uninstalled it via the market and reinstalled it now I'm back to where I should be.
So you could use that stock prop file, but after 5 or so tries it was sorta mixed results.

Anyone got the apk? I tried the site posted above but nothing happened.

Beast84 said:
Anyone got the apk? I tried the site posted above but nothing happened.
Click to expand...
Click to collapse
I just went to the main site and clicked download, however it refuses to install on my G1 with no traces of facebook on it. So annoyed right now

i reinstalled Ver. 1.1.1 and unistalled aqain from aplication manager, went to the market and installed Ver 1.1.2 and works fine. really no diference besides the top blue bar is complete.

here you go. I pulled the 1.1.2 apk from my phone after installing

BSDADON said:
I just went to the main site and clicked download, however it refuses to install on my G1 with no traces of facebook on it. So annoyed right now
Click to expand...
Click to collapse
The website just hangs for me
nephron said:
here you go. I pulled the 1.1.2 apk from my phone after installing
Click to expand...
Click to collapse
Thanks for that. I shall try this now

mrandroid said:
http://www.myhangoutonline.com/downloads/?did=15
Click to expand...
Click to collapse
Greatly appreciated.. This will help out many.

what commands in terminal to mount the folder as rw to remove it?
i used a script to switch my build.trout, but i used the script to switch back to the old one and i can't get FB to install. i never did anything to mod these for the nav and FB a few weeks ago.
http://forum.xda-developers.com/showpost.php?p=5081309&postcount=7036
thanks in advance.
===================================================================
found a fix by just coping the new facebook to the system/app folder, duh. works fine =]

elingreen said:
found a fix by just coping the new facebook to the system/app folder, duh. works fine =]
Click to expand...
Click to collapse
Thanks for the tip...solved my problem...

[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.

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

Unroot?

Is it possible to unroot after using the 1 Click Root? I'm coming from a rooted Droid Eris and I remember the first few people who rooted their Erises had lots of problems and I just wanna make sure we can go back and re-root if a better root process comes along later on...

magicelf said:
Is it possible to unroot after using the 1 Click Root? I'm coming from a rooted Droid Eris and I remember the first few people who rooted their Erises had lots of problems and I just wanna make sure we can go back and re-root if a better root process comes along later on...
Click to expand...
Click to collapse
Yes, but you'd have to do it manually at this point.
You'd delete busybox and su, uninstall superuser.apk, and there may be a symlink you need to undo, but I think the latest one-click cleans that up. I'd have to go back and check.
And any bloat you froze needs to be unfrozen, or bloat removed needs to be restored.

Okay, first version of this tool, be kind and let me know if there are any problems with it.
Also: NO GUARANTEES. If it does something that breaks your phone, I am not liable. Use at your own risk. Etc., etc.
http://www.psouza4.com/Droid3/PetesMotorolaRootTools_v1.03.zip
UPDATE 9/1/2011: version 1.03

I'm trying the one touch unroot and keep getting an error about the /sdcard/d3unroot folder missing files.
I extracted all of the APKs from your link to my /sdcard/d3unroot directory, but for some reason one touch unroot will not work.
The root worked great

same error here...

Get that error as well

Same here.
Why does it even need that to un-root @ that point?

I'm getting the same error.

Is it really a one-click method?
I'm a dummy so I think I'm gonna wait for some clarity.
Thanks for doing this, man!

Fully re-written and should un-root and restore /system/app for both v5.5.959 and v5.6.890. Enjoy!
http://www.psouza4.com/Droid3/PetesMotorolaRootTools_v1.03.zip
This program is for Windows only and can:
root your device (most Motorola Gingerbread devices)
unroot your device
restore your /system/app, even if you deleted files
And a bit more, such as un-freezing apps if you un-root just like Titanium Backup can.

So how do I do this. Is it the same as the one click root meaning unzip the file and put my phone into charging mode and let it do its thing
Sent from my DROID3 using XDA App

spacecasespiff said:
So how do I do this. Is it the same as the one click root meaning unzip the file and put my phone into charging mode and let it do its thing
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Pretty much -- this is an all-in-one. It'll tell you where to download files and where to put them when you begin.

I guess I'm just retarded I can't get this to work. I give up. Looks like I'm gonna have to get VZ to mail me a new D3

Yonnor said:
I guess I'm just retarded I can't get this to work. I give up. Looks like I'm gonna have to get VZ to mail me a new D3
Click to expand...
Click to collapse
Why can't you? More than willing to help, but have to tell me what the problem is. And bear in mind that I put out a new version less than 2 hours ago that fixes a LOT (it's a full rewrite).

ok ive downloaded the file to my computer.

Keep getting the error for the Restore data not being in the right place. I've extracted the files to the right spot (I think)
is the restore folder supposed to be located in the Root Tools folder, and then all the apk's placed that Restore folder?

Yonnor said:
Keep getting the error for the Restore data not being in the right place. I've extracted the files to the right spot (I think)
is the restore folder supposed to be located in the Root Tools folder, and then all the apk's placed that Restore folder?
Click to expand...
Click to collapse
Basically, yes.
I'll use your desktop as an example, so if you have:
Desktop\New Folder\Pete's Motorola Root Tools.exe
Then you'll want to extract all the files for the /system/app fix to:
Desktop\New Folder\restore
So that you have:
Desktop\New Folder\restore\AccountAndSyncSettings.apk
Desktop\New Folder\restore\AccountAndSyncSettings.odex
Desktop\New Folder\restore\AdminFeedNotifier.apk
etc.
This assumes you are using my new version 1.03.

psouza4 said:
Basically, yes.
I'll use your desktop as an example, so if you have:
Desktop\New Folder\Pete's Motorola Root Tools.exe
Then you'll want to extract all the files for the /system/app fix to:
Desktop\New Folder\restore
So that you have:
Desktop\New Folder\restore\AccountAndSyncSettings.apk
Desktop\New Folder\restore\AccountAndSyncSettings.odex
Desktop\New Folder\restore\AdminFeedNotifier.apk
etc.
This assumes you are using my new version 1.03.
Click to expand...
Click to collapse
Ok thank you, I'll give this a shot again.
EDIT: I have it set up as:
Desktop/PetesMotorolaRootTools_v1.03/restore/(all the apk's)
And I'm still getting the:
ERROR: /restore/ backup doesn't exist or is incomplete! etc etc

ok i just unrooted and all is good now im rooting agian. so thank you for this on click unroot meathod. its good to know that if i want to unroot i can. You should put this on every forum that you can. I will aslo tell people about it. You did a good thing for the people on this one. I think a lot of new people will whant to root now that they have a way to undo it.

Lol well like 8th try and I got it to work. Sorry for pestering you so much.

OTA Update Issue

My Droid 3 is rooted and I received the OTA notification. It downloads fine, reboots the phone, and begins to update. About 1/3 the way to update, the Android turns into an Exclamation point and reboots. Once back to home screen I get an Update Failed error.
Here is what I did so far:
-Defrosted all apps then rebooted
-Restored all system apps with Pete's One Click Root
-Pulled Battery for 5 min
-Factory Reset Phone
After each of these steps I tried to install the update and same thing. Will not get past 1/3. Any suggestions?

u need to rsd the swu.zip in order to get the update

OK, where can I get the swu.zip?

lacesout said:
OK, where can I get the swu.zip?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1255198
here u will find it along with rsdlite n adb fastboot. (make sure U read all that b4 U do it)

mrcastillo said:
http://forum.xda-developers.com/showthread.php?t=1255198
here u will find it along with rsdlite n adb fastboot. (make sure U read all that b4 U do it)
Click to expand...
Click to collapse
Thank you, this work!

lacesout said:
My Droid 3 is rooted and I received the OTA notification. It downloads fine, reboots the phone, and begins to update. About 1/3 the way to update, the Android turns into an Exclamation point and reboots. Once back to home screen I get an Update Failed error.
Here is what I did so far:
-Defrosted all apps then rebooted
-Restored all system apps with Pete's One Click Root
-Pulled Battery for 5 min
-Factory Reset Phone
After each of these steps I tried to install the update and same thing. Will not get past 1/3. Any suggestions?
Click to expand...
Click to collapse
lacesout, had the same experience. Used one-click method to root, then used psouza4's bloat script to remove, then restore apps when the update became available. These were my only mods. Went to /system/app and all app's are back with the proper apk extension. Update downloads fine, then hangs at 1/4 to 1/3 of install. Anyone else with similar experience or thoughts as to what's hanging the OTA install?

If you used the script to re-bloat the system, use root explorer and double check all the ".bak"s were removed. I don't remember which one, but I remember there was a file or two the script skipped over.
Also, if you did a nandroid before debloating, you can restore it, then go get the update. (The second option is what worked for me).
Sent from my DROID3 using XDA App

nu2droid said:
If you used the script to re-bloat the system, use root explorer and double check all the ".bak"s were removed. I don't remember which one, but I remember there was a file or two the script skipped over.
Also, if you did a nandroid before debloating, you can restore it, then go get the update. (The second option is what worked for me).
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Thanks for the reply and the tip on root explorer, it's an elegant tool, more intuitive to use than the freeware apps.
All the file extensions in /system/app are either .apk or .odex with the exception of Fota.apk.bak, and Fota.odex.bak. As the first time I heard of nandroid was your post, I unfortunately didn't use it, so I don't know if these were the extensions before I used psouza's bloat removal script. Fota was not on the list of scripts to remove/rename in his original post.
As Fota is the "firmware over the air" app, it is suspicious that it's the only one with a .bak ext. I am using root explorer to rename both, removing the .bak, and then will attempt another update.
Success! "Your phone has been upgraded to 5.6.890.en US version". Have lost root, at least for the moment. Will deal with that tomorrow. Last thing to do before going to bed is find the "Thanks" button. Thanks for setting me on the right path. P.

Unable to root after OTA to .890
One click root not longer works. After clicking "run_to_root_your_droid3.sh" on PC (Ubuntu 10.04) I get no prompts on screen, but phone does reboot twice. No su privileges after boot. Busybox is installed in /system/xbin and there is nothing I can do about it as I can't mount r/w. Using Root Explorer and Script Manager as tools.
I realize I'm going to have to increase my learning curve here. Would appreciate any links to relative threads on this topic, or suggestions on what to try next (I have searched, but need some direction).