Related
Okay so I downloaded the ota and install it. When the phone boots back up it just says update failed. I am rooted, but that is it. Any suggestions? I tried twice.
Sent from my DROIDX using XDA App
gobbles23 said:
Okay so I downloaded the ota and install it. When the phone boots back up it just says update failed. I am rooted, but that is it. Any suggestions? I tried twice.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I got that message too, now Im stuck in the M logo.
My phone booted up, but once bored it gabe me the error. Perhaps when I tried to unroot I messed something up. I deleted some of the sd card files associated with the root
Sent from my DROIDX using XDA App
I'm in the same boat.
I used one-click to unroot and it said it was successful but Titanium Backup was still able to get root rights. Not sure what to do here.
When ever in doubt, SBF - Back to stock 2.1
WARNING: ONCE YOU APPLY OFFICIAL FROYO 2.2 YOU CAN'T USE THIS METHOD ANYMORE
Thanks for the reply dr. I rooted but stuck with 2.1. Would that method do anything for me?
Using Bootstrap? If so, delete /system/bin/logwrapper then rename logwrapper.bin to logwrapper. I did this and it worked.
I was not using Bootstrap.
Currently attempting to fix this by reinstalling all of the bloatware that I uninstalled (per this: droidxforums.com/forum/froyo-2-2-news-rumors-wishes/7471-froyo-2-2-ota-install-issues.html).
I thought I had backed up the apps before uninstalling them with Titanium Backup but I was unable to restore them and it seems that it only backed up the application data and not the applications themselves before uninstalling. Funsies. That was an unroot, re-root, unroot, re-root carousel that I never want to go on again.
So... I went here (chadhaney.com/droidXDefault/516/) and downloaded all of the apps that I uninstalled, put them onto my SD card and then used Root Explorer to paste them into the system\app folder because I'm not so good with the command prompt stuff that you all use (if you do use this method, make sure to click "Mount R/W" at the top to get into read/write mode otherwise you can't paste into the system folder... took me way too long to figure out).
I've manually installed all of the apps while the OTA downloads (for some reason no 3G at the office) and will report back once it's finished and I have either Froyo, another failed attempt or a bricked phone. Exciting, no?
More fail. Will update with any useful information.
Yea i can't install it either
Sent from my DROIDX using XDA App
zehkaiser said:
Using Bootstrap? If so, delete /system/bin/logwrapper then rename logwrapper.bin to logwrapper. I did this and it worked.
Click to expand...
Click to collapse
I just wanted to say that this worked perfectly for me. Thank you so much.
Looks like I installed the wrong versions of the stock apks (516) and using the right version (604) did the trick.
GL to anyone still having troubles.
Pressing the Search key while it's unpackaging, I get this error:
assert failed: apply_patch_check("/system/framework/framework-res.apk", "4c785f91df976d18a3d032adae8dce5c8b2fa43" , "7a7d51db30170e92a8f84ae49cd73d9ae48b48dd")
E:Error in /cache/Blur_Version.1.13.604.MB810.Verizon.en.US.zip
(Status 7)
Installation aborted
Can someone link me to the stock framework-res.apk ?
SkyHawkEcks said:
Pressing the Search key while it's unpackaging, I get this error:
assert failed: apply_patch_check("/system/framework/framework-res.apk", "4c785f91df976d18a3d032adae8dce5c8b2fa43" , "7a7d51db30170e92a8f84ae49cd73d9ae48b48dd")
E:Error in /cache/Blur_Version.1.13.604.MB810.Verizon.en.US.zip
(Status 7)
Installation aborted
Can someone link me to the stock framework-res.apk ?
Click to expand...
Click to collapse
Same here. any help?
thanks
The OTA beta version was posted on XDA earlier today and removed by XDA. I am sure there are legal reasons they can't host a thread with a link to the files.
Plenty of us still have the file and may share info about it. The OTA patches exploits to root methods currently known. Join the irc and help us crack the root. Id be happy to share any file i have for you to use.
Chat with us
Thanks!
10char
hopefully this won't get pulled down too
MOD EDIT: Pulled down.
You might as well take it down. It's against forum rules i believe.
Sent from my MB860 using XDA App
Is this file tied to an IMEI? Or is the update file for any phone?
unfortunate
We don't know yet if its IMEI or sig checking I think I read that it is running checks against sigs. Also I think they only used imei to push the OTA to the phones not to lock that particular update to that particular phone
Sent from my MB860 using XDA Premium App
Sorry for the newbie question, but how do I use this update?
rename the zip to update.zip and put it in the root directory of your sd card, then boot into recovery and load it. If it fails the check you may need to reflash the original sbf first.
what do you mean rename the zip? are you referring to the file name or are you referring to a specific file? and also do we need to extract the file?
In the accompanying message it said something along the lines of 'who can use this uppate/ any atrix.'
Sent from my MB860 using XDA App
need help. did alll the steps corectly, then it says finding update package, opening update package, verifying update package, failed to read footer from /sdcard/update.zip (is a directory) signature verification failed, installation aborted. am i doing something wrong?
Has anyone tried putting the update file into their cache along with the ctc or cbc (don't remember what the file ext is) and tried hitting the update button in the phone to see if it recgonizes the update as though it actually came OTA?
Sent from my MB860 using XDA Premium App
Any known new bugs as of this update?
I am referring to the .zip file of the update that is available in the 3rd post.
PAulyhoffman said:
hopefully this won't get pulled down too
Click to expand...
Click to collapse
As far as copying to the cache goes, I did not try that but renaming to update.zip and updating through recovery worked fine after I re-flashed to the stock sbf. It took a little bit longer to go through the initial boot process after the update than it did flashing an sbf file, but seems to be smoother overall so far, I only have about an hour on it though.
diedemus said:
I am referring to the .zip file of the update that is available in the 3rd post.
As far as copying to the cache goes, I did not try that but renaming to update.zip and updating through recovery worked fine after I re-flashed to the stock sbf. It took a little bit longer to go through the initial boot process after the update than it did flashing an sbf file, but seems to be smoother overall so far, I only have about an hour on it though.
Click to expand...
Click to collapse
I've renamed the file to update.zip and have put it into the sdcard directory and then rebooted but have not noticed anything updating. I've also tried sdcard-ext directory. Can you explain a little as how you got this file to work? I am not rooted, and have not done any mods so I am on the original sbf.
Thanks for your help.
James62370 said:
I've renamed the file to update.zip and have put it into the sdcard directory and then rebooted but have not noticed anything updating. I've also tried sdcard-ext directory. Can you explain a little as how you got this file to work? I am not rooted, and have not done any mods so I am on the original sbf.
Thanks for your help.
Click to expand...
Click to collapse
Place the file in the root of your sdcard ext them reboot in recovery mode and I believe it will either update or prompt for if you want to run update.zip from sdcard
Sent from my MB860 using XDA Premium App
James62370 said:
I've renamed the file to update.zip and have put it into the sdcard directory and then rebooted but have not noticed anything updating. I've also tried sdcard-ext directory. Can you explain a little as how you got this file to work? I am not rooted, and have not done any mods so I am on the original sbf.
Thanks for your help.
Click to expand...
Click to collapse
When you reboot your phone hold the volume down button until you see the Fastboot text at the top of the phone, then hit the volume down button until you see it say Android Recovery, hit the volume up key to load into recovery, once you see the android guy and the triangle tap the lower right portion of the screen, from there you will have the recovery menu, at this point you can use volume up/down to select and then tap the ok at the bottom left
drock212 said:
Place the file in the root of your sdcard ext them reboot in recovery mode and I believe it will either update or prompt for if you want to run update.zip from sdcard
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
How do you reboot into recovery mode?
I'm thinking Moto is watching this forum very carefully to gauge the success of their root access lock-down efforts (I know I would). The only counter an open forum like this has is to delay posting of any new root access methods until after Moto's offical release of the ATRIX Update software. Time is on our side, not Moto's - their release process is long and expensive with little return in $$$. I know that devs are just starting to look at this, and a new root method is wishful thinking at this point, but just had to throw in my 2 cents.
If I do the Verizon update will it "unroot" my Tab? Will it screw anything up?
Thanks.
I'm not sure, I'm rooted and when I clicked to install the update, my tab did nothing. I know that doesn't help.
Same thing happened to me, there is another thread about this and there is a post of the update file, I ran that and it worked
robinsmy1 said:
Same thing happened to me, there is another thread about this and there is a post of the update file, I ran that and it worked
Click to expand...
Click to collapse
Do you have a link to that thread?
-- thanks, mike
Here is the dropbox link from the thread
http://dl.dropbox.com/u/11358417/fcaaa4b8ca18.htm
this is the thread
http://forum.xda-developers.com/showpost.php?p=12727936&postcount=7
robinsmy1 said:
Here is the dropbox link from the thread
http://dl.dropbox.com/u/11358417/fcaaa4b8ca18.htm
this is the thread
http://forum.xda-developers.com/showpost.php?p=12727936&postcount=7
Click to expand...
Click to collapse
Hmmm. When I click those links I get a bunch gobblygoop on my screen.
EDIT: Just read it needs to be opened in IE. Weird.
Yeah, I found it weird too.
I never tried from the Tab though, might work from there I guess
Update:tried from tab with Dolphin....same result as Chrome
Ok, so now it's on the Tab. How do I make the update do it's thing?
name it update.zip....put it in root of SD, reboot to recovery and choose install update.zip
At least that is what I did and it worked perfectly......do it at your own risk though.
robinsmy1 said:
name it update.zip....put it in root of SD, reboot to recovery and choose install update.zip
At least that is what I did and it worked perfectly......do it at your own risk though.
Click to expand...
Click to collapse
Dumb question: How do I boot to recovery?
Turn off....hold volume up while powering on
Volume down to install update.zip and press home. (after menu comes up)
Make sure you have decently full battery or on AC
Worked! Thanks!
Still can't copy/paste from the mail program.
Update
I zipped the file so it should be easier to dl. Try this link. If you are going to rename it unzip it first, then rename. It was originally a htm file in my cache folder but as above some have had success renaming and flashing it. I have not tried yet myself yet as I'd like to here from people who have root and bootstrapped ext filesystem. If you do let us all know your results. Cheers.
https://dl-web.dropbox.com/get/Public/fcaaa4b8ca18.htm.zip?w=64e40992
I put the update.zip on rapidshare for anyone who wants it
http://rapidshare.com/files/456489639/update.zip
So has anyone successfully updated that was rooted and running ext4?
Will it affect kernels or root access? If this gets rid of my of my kernel and won't allow to reflash ill be pissed! So if anyone has installed this please let me know. And if it's for the worst. Tell me how to get rid of the damn update icon!
Sent from my SCH-I800 using XDA App
coheirnt said:
Will it affect kernels or root access? If this gets rid of my of my kernel and won't allow to reflash ill be pissed! So if anyone has installed this please let me know. And if it's for the worst. Tell me how to get rid of the damn update icon!
Sent from my SCH-I800 using XDA App
Click to expand...
Click to collapse
Root was still there, and kernel build number did not change. the [email protected] did change.
I cannot guarantee that it will not affect kernel, but it did number change the build number so it suggests it did not
Hear me out here. I WAS running Franco kernel but went back to stock and also deleted the modified file that he posted that had to be deleted. I rebooted my phone and flashed the stock kernel that is floating around here on the forums. I went to settings to see what kernel I was running and was no longer on Franco. I click to download the OTA and it say that it is verified and downloaded. Click the install and reboot button and a count down starts to happen from 10 till it shows rebooting....and it stays three. I left it there for about 5 mins with nothing happening.
I download the OTA .zip file that's on the forums and try to install it with twrp and get the error 7.
Anyone have any ideas as to what I can do for this?
StyleUkno said:
Hear me out here. I WAS running Franco kernel but went back to stock and also deleted the modified file that he posted that had to be deleted. I rebooted my phone and flashed the stock kernel that is floating around here on the forums. I went to settings to see what kernel I was running and was no longer on Franco. I click to download the OTA and it say that it is verified and downloaded. Click the install and reboot button and a count down starts to happen from 10 till it shows rebooting....and it stays three. I left it there for about 5 mins with nothing happening.
I download the OTA .zip file that's on the forums and try to install it with twrp and get the error 7.
Anyone have any ideas as to what I can do for this?
Click to expand...
Click to collapse
You deleted the modified file but did you rename the backup of that file?
harpo1 said:
You deleted the modified file but did you rename the backup of that file?
Click to expand...
Click to collapse
I'm on the same boat as the OP, but I'm on complete stock, never rooted or unlocked the bootloader. I go to system updates and check for updates, but nothing comes up
Kid Poker said:
I'm on the same boat as the OP, but I'm on complete stock, never rooted or unlocked the bootloader. I go to system updates and check for updates, but nothing comes up
Click to expand...
Click to collapse
Go to settings/Apps and scroll over to the all tab then scroll down to Google Services Framework and select it. Then clear data and Force stop. Now go back and check for system update again. You may have to do this a few times but it will work eventually.
harpo1 said:
Go to settings/Apps and scroll over to the all tab then scroll down to Google Services Framework and select it. Then clear data and Force stop. Now go back and check for system update again. You may have to do this a few times but it will work eventually.
Click to expand...
Click to collapse
Worked for me. Thanks for the info :good:
harpo1 said:
You deleted the modified file but did you rename the backup of that file?
Click to expand...
Click to collapse
Yea I deleted the .Bak part of the file, it was actually fkbak or something like that, I made it so that it looked the same as the other modified one that I deleted
Sent from my Nexus 4 using xda premium
I really don't understand this phone. I've been on a quest of 2 weeks to be rooted and on official status, finally i gave up everything because i was not able to have both. Finally i flashed factory rom through odin, formated a couple of time the phone, and i got back official status. I much rather gave up a few rooting benefits then OTAs, at least until they fix the phone's problems.
Well, this morning, i wake up, and that DAMN custom status is back....WHY????????? I'm not rooted, i'm 100% stock, i checked with rootchecker and my phone doesnt have root....then why does that damn status keep coming back??? There is obviously something else that triggers it......man i'm so deperate! Please help!
polish_pat said:
I really don't understand this phone. I've been on a quest of 2 weeks to be rooted and on official status, finally i gave up everything because i was not able to have both. Finally i flashed factory rom through odin, formated a couple of time the phone, and i got back official status. I much rather gave up a few rooting benefits then OTAs, at least until they fix the phone's problems.
Well, this morning, i wake up, and that DAMN custom status is back....WHY????????? I'm not rooted, i'm 100% stock, i checked with rootchecker and my phone doesnt have root....then why does that damn status keep coming back??? There is obviously something else that triggers it......man i'm so deperate! Please help!
Click to expand...
Click to collapse
It's really not as big of a deal as you are making it. The way I see it you have 2 choices.
1. Exchange the phone for another (that might do the same thing)
2. Ignore it.
Just like every other Galaxy phone out there (you remember the skyrockets, right?) not all of them react the same way. Some get custom, some do not. Others switch back and forth.
I've noticed you have made many posts about this same thing. If someone hasn't provided a concrete answer that has worked for you by now it just doesn't exist yet. No matter how frustrated you are over it, making new posts about it are not going to change anything.
Its up to you if you keep wanting to post about it (I'm not complaining about it), I just don't think it's going to get you any more information at this point than what already has been said. Maybe I am wrong and someone will tell you exactly what to do to make it "official", but I haven't seen anything yet.
Good luck and try not to let it get to you so much.
euhhh no, they are not about the same thing, one was about retaining officiel while rooted, and now that i've given up on that, i still have a custom status, the reson why i dont report there is becuase poeple have seen the thread and will not go back, so in order to attract new poster i create a new thread. And no, i dont want to ignore anything because i want OTAs. If you have a problem with that, dont answer
You need to re-root (motochopper method) and then using a file browser such as "root explorer" go to:
/System/Xbin
Once you have navigated to the above path, delete these two files:
"su" and " busybox"
Once you've deleted the two files, uninstall SuperSU and reboot your phone twice.
You'll notice that after the second reboot the "custom" will revert back to "official"
Sent from my SGH-I337M using Tapatalk 2
peoples_flip said:
You need to re-root (motochopper method) and then using a file browser such as "root explorer" go to:
/System/Xbin
Once you have navigated to the above path, delete these two files:
"su" and " busybox"
Once you've deleted the two files, uninstall SuperSU and reboot your phone twice.
You'll notice that after the second reboot the "custom" will revert back to "official"
Sent from my SGH-I337M using Tapatalk 2
Click to expand...
Click to collapse
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
I went through what you have, I completed a full stock restore via Odin and these two files I mentioned were still there. Use a file explorer and go to the path I suggested and you'll see them there
Sent from my SGH-I337M using Tapatalk 2
polish_pat said:
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
Click to expand...
Click to collapse
I don't believe the current Odin contains a pit...or whatever it is that formats the phone...
So all Odin is going to do is reinstall everything...so replace missing or corrupted files - it will not delete your new files
Formating from the phone itself won't delete everything...its just going to delete your apps, app data, and cache
Therefore doing multiple factory resets and odins likely will not remove all traces of root...someone correct me if I'm wrong but that's what I believe is the case...
Sent from my HTC PH39100 using Tapatalk 2
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
XGhozt said:
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
AT&T software update push or download will not work for your phone if it is showing custom. People like to be getting these stock updates as soon as they are published by the provider, not when some good heart packages a new ROM using them.
polish_pat said:
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
Click to expand...
Click to collapse
Good info here, I did this procedure as you described, and yes, official is showing, but you can NOT delete su, it will unroot. I just renamed the 2 files, and root was gone. renamed su back, re-installed su superuser, and reboot, root is back with official status.
Thanks.
TheAxman said:
Good info here, I did this procedure as you described, and yes, official is showing, but you can NOT delete su, it will unroot. I just renamed the 2 files, and root was gone. renamed su back, re-installed su superuser, and reboot, root is back with official status.
Click to expand...
Click to collapse
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
CAG-man said:
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
Click to expand...
Click to collapse
Same here
CAG-man said:
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
Click to expand...
Click to collapse
Correct. the one from the playstore updates the binaries. then uninstall.
---------- Post added at 07:11 PM ---------- Previous post was at 07:10 PM ----------
XGhozt said:
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Good answer, why does it matter if it says custom? whats the big deal here. If you are wanting the update, why not just wait until a dev does what they need to do to it, and flash it later. I updated 1 time in a year on my GS3, and never did it again. When a new rom is developed, it usually is a base from the update...so....
Had a posting. Could not delete
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Did some digging in the forums and I am rooted with OFFICIAL.
This is how to do it. Taken from this thread.
http://forum.xda-developers.com/showthread.php?t=2252248&page=42
Mr. Q said:
Well, you do not have to install the ZIP, but instead, do the following:
- Install SuperSU from the market
- Grant SuperSU root access
- When asked to update su-binary, please do
- Remove SuperUser from your device
- Reboot (I read two reboots are needed to make the icon disappear again.)
Click to expand...
Click to collapse
My process completely.
Remove Busybox from system/xbin (or your busybox backup)
Install SuperSU by Chainfire from playstore.
Open SuperSU and Grant SU root
Update the binary
Say yes to try to remove other root apps. This will remove superuser.
reboot
reboot
On second reboot you will notice the Galaxy S4 logo returns and Official Status has returned.
If it has not returned then some other issue is causing the custom status.
CAG-man said:
Did some digging in the forums and I am rooted with OFFICIAL.
This is how to do it. Taken from this thread.
http://forum.xda-developers.com/showthread.php?t=2252248&page=42
My process completely.
Remove Busybox from system/xbin (or your busybox backup)
Install SuperSU by Chainfire from playstore.
Open SuperSU and Grant SU root
Update the binary
Say yes to try to remove other root apps. This will remove superuser.
reboot
reboot
On second reboot you will notice the Galaxy S4 logo returns and Official Status has returned.
If it has not returned then some other issue is causing the custom status.
Click to expand...
Click to collapse
I was able to get official and root, the problem is it comes back after 2-3 days, please report back on sturday and tell me if its still official, also this logo you are talking about, i never see it because im in canada and my bootloader is unlocked already
EDIT: Ok, so once i was rooted and installed SuperSU and got superuser out, i deleted busybox, i then rebooted ONCE and got official just like that. I also took out SD card because i know this screwed me up last time. I'm happy because i'm rooted and official, but i'm not convinced this will last very long because it has never lasted more than 2 days. I will report back in a few days. Thanks Cagman, you've been very helpful and what you told me to do did the best results for me, i just hope they last
so far so good!!!:fingers-crossed:
polish_pat said:
so far so good!!!:fingers-crossed:
Click to expand...
Click to collapse
Try rebooting a few more times.
For about a week i was getting the custom status every 2nd or 3rd reboot, and then eventually it just went away...
joeybear23 said:
Try rebooting a few more times.
For about a week i was getting the custom status every 2nd or 3rd reboot, and then eventually it just went away...
Click to expand...
Click to collapse
Hahaha, i did it!! earlier this afternoon i sort of challenged my phone by rebooting it constantly, ive rebboted probbaly 20-30 times and its still official, i guess deleting busybox sealed the deal!!
Polish_pat I am glad I was able to help. You are welcome. Congratulations.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app