Related
hey boys
so I finally gave it and did the whole adb rooting thing... lots of command lines and so on but finally it works so I got rid of Universal Androot..
so now my problem is still there though...
I run the update.zip and I get this:
assert failed: apply_patch_check(“system/app/GenieWidget.apk”,”(insert tons of digits here″,”(insert tons of digits here)″)
“E: Error /sdcard/update.zip
(Status 7)
Installation aborted.”
Anybody got a solution?
My phone and its changes:
Stock Nexus One 2.2
Rooted word-per-word via http://forum.xda-developers.com/showthread.php?t=736271
Uninstalled Amazon MP3 and "News & Weather" (genie widget?)
I figure maybe reinstalling News & Weather would fix it ... but Titanium backup does not recover it even if I did back it up first... (useless??)
I downloaded the APK and instaled it, but still the same thing.
What else what else...
thanks
I'm only posting this here because I, too, have an error and am in no way trying to thread-jack. I got the 2.2.1 OTA the other day and went ahead to update. Unfortunately, I use AndRoot also and when I got halfway through the OTA, I got an error during installation. I pulled the battery, rebooted, and I was still 2.2 rooted. I unrooted with AndRoot and now seemingly have no way of acquiring the update OTA. Any advice, OP?
OTA seems absolutely random to me ... so I would download the update (found in this very forum) and rename it to update.zip and put it in the root of your sd card and run the update as prescribed on many sites...
as for my problem... damnit damnit damnit is all I can say. I know 2.2.1 is generally useless, but I want to be sure I can install Gingerbread when it comes out!!
damn so I tried 2 different versions of GenieWidget installations (it's news and weather)
seems I get the same error everytime.
I know the "simplest" thing is to run a full reinstall of my phone (recover console?) but I don't want to redo all my apps/settings... can't there be a way to recover 1 or 2 components only? in this case, amazon mp3 and geniewidget, just so that the 2.2.1 update works...?
I had the same issue with com.amazon.mp3.apk not being found (I remember deleting it as soon as I got root)... well I had to put it back under /system/app/ (meaning you can't do it via the market - only manually)
Note: the exact version that was shipped with froyo has to be installed. You can check that you have the right apk by computing its sha1 sum (that's the second "insert tons of digits here" MitchRapp refers to)
*UPDATE*
oh snap.
my friend has the same nexus one as me ... so I copied his GenieWidget.apk and .odex into my /system/app and so far so good... i got another error (com.amazon.mp3) so I'm going to copy that too
update to follow...
hey it worked!
after a (seemingly) endless "X" animation bootup... 2.2.1 is there.
now I lost the root access I just made with adb shell something something.... that's normal I guess, so I'll redo it
Uh oh, I removed amazon mp3 too...;(
toss the .apk back in /system/app and reboot and update... it worked!
now for re-rooting... that wont work damnit.
I'm doing the rageagainstthecage thing word-for-word and the thing is, when I try
./busybox cp busybox etc...
it says file already exists
and the chmod commands only give me a "read-only" error
cuz I already rooted earlier using the .freenexus style .......
what can I do for this?
Anyone happen to have the2.2 Amazon apk and willing to share?
Sent from my Nexus One using XDA App
I do, what's your email
anyone know how to re-root 2.2.1 using the rageagainstthecage without it telling me everytime that busybox file exists and is in read-only... i followed the steps to the letter...
bennettm89 said:
Anyone happen to have the2.2 Amazon apk and willing to share?
Click to expand...
Click to collapse
Sure.
sha1sum is c3b285c13db4b7f8fcfb72372d77b388157bf6cd
MitchRapp said:
I do, what's your email
anyone know how to re-root 2.2.1 using the rageagainstthecage without it telling me everytime that busybox file exists and is in read-only... i followed the steps to the letter...
Click to expand...
Click to collapse
I used superboot (1.1-FRF91-nexusone-superboot) - worked like a charm.
I had an issue with settings.apk , had used universal androot and metamorph to make changes to the battery meter.
After getting the ota , the installation was aborted due to changes in settings.apk . i downgraded to android 2.1 erd79 ( had the passimg.zip file from few months ago).
Once downgraded never got OTA for further updates ( eg ere27 , frf91 etc).
had to manually update to frg83.
Jony, Thank you.
OP, thank you anyway, I got it from Jony. Now to find the update.zip...
God bless it. Went to go install from SD, I don't have twitter. I hate twitter. Anyone have it...
MitchRapp said:
anyone know how to re-root 2.2.1 using the rageagainstthecage without it telling me everytime that busybox file exists and is in read-only... i followed the steps to the letter...
Click to expand...
Click to collapse
The rageagainstthecage step-by-step is missing a couple steps that will cause it to give the errors you're seeing. I ran into this and posted the solution, with follow-up and confirmation by others, later in the thread. Check out
http://forum.xda-developers.com/showthread.php?t=792016
In a nutshell, the /system partition needs to be mounted for both read and write in order to set permissions on the Superuser.apk and su files. Also, if you already were rooted and have Superuser.apk, su, and busybox installed, you don't have to copy them back to the phone--you can just set the permissions on the existing files.
Ohhhh jony! Can you post the twitter APK pl0x
bennettm89 said:
Now to find the update.zip...
Click to expand...
Click to collapse
There it is: http :// android.clients.google.com/packages/passion/signed-passion-FRG83-from-FRF91.c8847c98.zip
bennettm89 said:
Ohhhh jony! Can you post the twitter APK pl0x
Click to expand...
Click to collapse
Hre you go - sha1sum is 2acade940a14e65abcb93ff7fc68b0a95b733113
jony22 said:
There it is: http :// android.clients.google.com/packages/passion/signed-passion-FRG83-from-FRF91.c8847c98.zip
Hre you go - sha1sum is 2acade940a14e65abcb93ff7fc68b0a95b733113
Click to expand...
Click to collapse
Thanks buddy, I appreciate it.
I'm not really happy with the update. Lost root ( I knew I would ) but the most upsetting thing is that I removed my work email from my phone. I had to update security settings to authorize the remote administration of my device through my exchange server at our HQ which is not happening. I know it doesn't have to be done but I was getting increasingly angry just looking at it in the notification bar 24/7.
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
Firstly,pls notice this script is only for the phone which have got root.
Before below steps,pls make sure your usb mode is not as mass storage.you need choose none or first item when you plug your usb cable in.
Thx for all the XDA guys hard work and especially DG ,Shawnbuck,Fenny and anyone else that contribute a lot for XDA and us.
2011/7/4 Update for restoring script of stock Webtopmod 4.1.83
2011/5/4 updating:
Adding the restore script for restoring to stock version of V4.1.57 webtop files in order to update to 4.1.83.
After succeed updating and got root access,you can run webtopmod V8 again to get the webtop cracked.
pls notice in order to backup the stock webtop version ,you need answer "N" when prompt "Have your cracked ago with old mod files?" for your first run script after updating.
Then your stock webtop file will be backed up in /sdcard/webtopmodbackup(thx for terrypchan's uploading files)
Background:
I found some guys complained lose webtop mod after root for 4.1.57(now 4.1.83).
Actually, what we need is just to replace some files that we use for stock version.
But the original script will not work for 4.1.57.
In order to make some new guys crack webtopmod easily , i update the script to make it useful again.
I also add Chinese font support on webtop.Now you can visit Chinese webside at webtop.The Chinese will displayed correctly.(If some errors happend regarding font fix,it doesn't matter of your crack.Maybe it's because your system is English version)
I don't need your bears for it.Just press "thank" butten or leave a feedback,which is enough for me.
V8 will be stable version for you and could not be updated so far.
Steps:
1. download the file
2. extract and press install.bat as usual
3. run script in rooted Atrix before you do any action regarding deodex or theme changing
3. look at the screen and answer the question accordingly(If it's your first time to run the script in this system version---noticed i mean version not the phone,you need put "N" when prompting "Have your cracked ago with old mod files?" to backup your stock files
4. after reboot,you webtop back again.
[option]5. If you want to deodex or any theme changing,then do it.
[option]6. Run the script V8 again after you do deodex or theme changing,this time you don't need input "N" when prompting "Have your cracked ago with old mod files?"
Remark:
1. webtopmodbackup.zip is the script that return webtopmod files to stock 4.1.26 version for updating to 4.1.57
2. restorewebtopmodv4.157 is the script that return webtopmod files to stock 4.1.57 version for updating to 4.1.83
3.webtopmod1.1updatedV8 can be run under any rooted Atrix to active the webtop mod
4. You'd better to run V8 to get webtop before you do deodex or any theme modification like gingleblue which will replace your webtop files with deodex and V8 cannot backup your stock files automatically
Version Introduction:
1.V8 (instead of V7)is fixed for Bell version.--updated on 4/18--I missed one sentence in scripts of V7.Thanks for Becart's correction.All the users(at&t and bell version) can use this version for webtopmod
1.V6 is compatible with the updated 4.1.57 mod files done by Fenny.You can updated from your old mod files or use it to crack your webtopmod directly.
Updated History below:
4/23 Now adding script of going back stock mod files(4.1.26.Pls notice it's different from 4.1.57 files and cannot use for updating to 1.8.3).Any one can download WebtopModBackup.zip and run uninstall.bat to make the files go back to stock version.You need notice i didn't test it but you can try and if any error,let me know.
(Update V8):
Fix script for Bell version.Thanks Becart's correction.
(Update V6):
Now reinclude the Fenny's file and update a little script.It works with Fenny's updated 4.1.57 Mod files now.Thx for his job and updated.You can find details throughthis link .
(Update V5):
Sorry .Made a mistake,i didn't notice Fenny's file format,it cannot be used for this script directly.V5 went off line. Sorry for the inconvinience.You can find V6 above.It should be workable.
V5 Version is compatible with the updated 4.1.57 mod files done by Fenny. Thx for Fenny's quick updated for 4.1.57 mod files.
Thx for Fenny's mod files again.
Then follow above steps to update.
Pls notice you need answer if you have crack the mod files ago in order to keep you stock files in SDCARD otherwise it will be overwritten when you run the V5 script.
(Update V4):
Now it can be used for any version of atrix including Bell.
(Update V3):
Donot need input command by manually any more.But you need keep phone screen on and allow SU when the script run.
(update V2) :
Filename of webtopmod.sh changed from WebtopMod.sh to webtopmod.sh since many person ignor the capitalization.
pls notice the last command need use filename exact same as webtopmod.sh now.all the letter is lowercase
Backup:
You can find the link for root:
http://forum.xda-developers.com/showthread.php?t=1013931
The 3 crack files are from Fenny's thread. you can find it through below link.
http://forum.xda-developers.com/showthread.php?t=980193
This is great. As Soon as I am able to try it I will.
thank you for this update
Do you need to root your Atrix before doing or is this just like the no root needed version from that pther fourm?
Sent From My Motorola Atrix
Boarder24 said:
Do you need to root your Atrix before doing or is this just like the no root needed version from that pther fourm?
Sent From My Motorola Atrix
Click to expand...
Click to collapse
The big red text in the OP says you need root.
Ronaldo_9 said:
thank you for this update
Click to expand...
Click to collapse
Hey Ronaldo, did you try it?
I just updated and rooted. Will try once I get home...
thanks for this!
tried it dont work it say WebtopMod.sh not found... maybe cause i have windows 7
Is this the new webtop.apk modded from 1.57 or the original from 1.26?
I ask because this file was updated as part of the ota update and has some performance improvements over the original.
Sent from my MB860 using XDA App
It can't find the sh file.. even tho its in the extracted folder along with everything else? What do I do?
macperson123 said:
It can't find the sh file.. even tho its in the extracted folder along with everything else? What do I do?
Click to expand...
Click to collapse
Im in the same situation here
Sent from my MB860 using XDA App
Ugh wtf. Now it can't even find the adb... I'm pissed.
macperson123 said:
It can't find the sh file.. even tho its in the extracted folder along with everything else? What do I do?
Click to expand...
Click to collapse
pls notice the filename need be exact same as WebtopMod.sh.cannot use webtopmod.sh or anything else.
You can download my updated file and now you can use webtopmod.sh as filename.
Pls try again.any problem,pls let me know
macperson123 said:
Ugh wtf. Now it can't even find the adb... I'm pissed.
Click to expand...
Click to collapse
try to killed adb through taskmanager of windows firstly
yokozuna82 said:
Im in the same situation here
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
need use WebtopMod.sh as filename.don't try webtopmod.sh or anything else.
You can download my updated file and now you can use webtopmod.sh as filename
rjohnstone said:
Is this the new webtop.apk modded from 1.57 or the original from 1.26?
I ask because this file was updated as part of the ota update and has some performance improvements over the original.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
use the old file.the OTA doesn't show any clue about webtop.apk updated.
update some script.
1.could help out about the adb missing...if you meet this issue,you could force close adb.exe through task manager of windows.
2.change webtopmod.sh filename from WebtopMod.sh to webtopmod.sh. Now you can ignor the capslock letter
sorry still not working i even put it in the C: with run as administrator
Ran the script last night and tested it. Works great.
Thanks!
yokozuna82 said:
sorry still not working i even put it in the C: with run as administrator
Click to expand...
Click to collapse
can you print screen of your input and output?
It seems at least one guy has finished..and also i test it in my computer again..
update to V3.
Whoever has not been succeed by old version,you can try this one.
The original Android 2.3 update for the Captivate came with a new email client. Or updated version anyway. This client blows any other one I've seen out of the water. Does anyone know where I can get the apk for that? I am running Serendipity 7. I downloaded the package with the Samsung email but its the version that was prior to the 2.3 upgrade. I have been looking all over for this.
Why not just use K-9?
Sent from my SAMSUNG-SGH-I897 using Tapatalk
The one that came with the Captivate update is 10 times better than K9. I briefly looked at K9 and didn't really like it.
extract .apk from any stock KK4 .zip CWM ROM - Nostalgia 2.2, Fasty, Saurom, Apex - it's under /system/app stored as Email.apk
Thanks, I think I have the correct files. I tried to install the .apk, but it failed. I am assuming that it needs to be deodexed. I am very new at this, but I found a program called xUltimate that is supposed to do this for me. I am going to give it a try.
Did you just try to install it regularly? Cause that won't work, you need a root file explorer, a terminal emulater, or adb and put our on /system/app then reboot.
Yes, I tried to just install it regularly first. I noticed that there was an .apk file and an .odex file, so I figured it needed to be deodexed. I took a look at that xUltimate software, but it wasn't as self-explanatory as I had hoped. Maybe someone can provide some decent instructions on how I can install it.
I've looked and I couldn't find a direct solution, so I'm going to give birth to this thread.
Problem: I want (and have problems downloading) the OTA Ice Cream Sandwich update on my rooted Verizon Motorola Droid 4
I rooted my phone awhile back. Just today I received a message that the system update was available.
-I am able to download the update.
-I am able to begin installing the update.
-During the installation process, the yellow progress indication bar fills about 1/8 of the way, then I get the ! warning sign above the little android figure.
Here's what I've done so far to try and correct this problem:
-Restarted my phone
-Restarted my computer
-Downloaded and installed the latest Motorola drivers from the official Motorola website.
-I attempted* to un-root my phone using the Droid 4 Utility 0.4.
--I should note that in the log, there was a like that read:
rm failed for /data/app/com.noshufou.android.su-1.apk, No such file or directory
Click to expand...
Click to collapse
-Restarted my phone again
-Tried installing the update with still no luck
*It appears that all the Droid 4 Utility did was remove Superuser, though I could be wrong. However, if this is the case, I still have a rooted device.
Once again, I'd prefer to have the OTA update, and not a leaked/rooted version of ICS. There's a possibility I didn't unroot my phone all the way. Am I doing this right?
Thanks in advance for the help.
ICS hasn't been officially released for the D4 yet.
This morning when I woke up I received an "Update available" notification. I am able to download an update for my phone. After downloading the update, I receive another notification:
"Install update
Update (6.13.219.en.US) has been downloaded and is ready to install.
Installation will take up to 10 minutes. Upon completion the phone will power off than back on.."
So it absolutely did not occur to you that this is the "219" update which can be found in this (General) section as well as in the Android development section .
Please do take a look in the topics mentioning "update" or "219". You will find topics for rooted and stock phones regarding the 219 update and how to proceed.
Die Bruine said:
So it absolutely did not occur to you that this is the "219" update which can be found in this (General) section as well as in the Android development section .
Please do take a look in the topics mentioning "update" or "219". You will find topics for rooted and stock phones regarding the 219 update and how to proceed.
Click to expand...
Click to collapse
Thanks for your help. I'm slightly inexperienced. I was so excited when I saw the system update that I suspected it to be ICS. Albeit, my hunt continues.
it failed because u altered system files of some kind... its happening to me too. i downloaded the stock system app zip from here in hopes to replace the system apk's so the update will go through but i dont know how to replace the system files... is it as simple as copy and paste, do u have to copy it to the sd card then use a file explorer to copy and overwrite over the files? i dont want to mess something up
I did modify the build file in root/system in order to install a certain APP from the Google Play Store, but I made sure I went and reversed all of the changes I made. Could you please post where you got this file from?
http://forum.xda-developers.com/showthread.php?t=1608866&page=3
Stensin said:
I did modify the build file in root/system in order to install a certain APP from the Google Play Store, but I made sure I went and reversed all of the changes I made. Could you please post where you got this file from?
Click to expand...
Click to collapse
The original post has also been updated with a link to the original files, as well as more complete instructions.
http://forum.xda-developers.com/showthread.php?t=1608866
omniuni said:
The original post has also been updated with a link to the original files, as well as more complete instructions.
http://forum.xda-developers.com/showthread.php?t=1608866
Click to expand...
Click to collapse
but how do u copy those files from NOTE 2? i downloaded the file, extracted the files but i cant copy them to the system folder
copy them to your phone via usb, make sure you are rooted, and CAREFULLY COPY them using a root explorer. You can get a good one from AntTek for free on the Play Store.
I tried that.. copied the files to the sd card. I can see them when i browse the sd card via the computer but when i unplug the cord they arent there anymore. Would replacing the stock boot animation via rom manager have anything to do with the fail?
Sent from my DROID4 using XDA
remember that the "sd card" the computer sees is the phone's internal storage. your actual sd card, as the computer sees it, is referred to by the phone as "sd-ext" or "external sd card" usually.
I did the samething, I changed two files and got help from this forum to get the originals. I use es file explorer in root and copied the files to where they need to be. I checked the permissions and rebulit the checksum for each file. After that I used voodoo to save my root. I rebooted instal from sdcard and it worked. hope this helps.
well it wasnt an app that i deleted.. i was reading somewhere about the build.prop file being messed up from using rom manager so i downloaded a new copy and pasted it over the old one and the update went through! thanks everyone!
Montecarlo97z said:
well it wasnt an app that i deleted.. i was reading somewhere about the build.prop file being messed up from using rom manager so i downloaded a new copy and pasted it over the old one and the update went through! thanks everyone!
Click to expand...
Click to collapse
I tried doing this, but it didn't work. Could you post the build.prop file that you used?
EDIT:
I was copying my build.prop file incorrectly. More details here.