I used Epic All in One Root and Recovery v2.04 a while back to root my Epic. Uninstalled a few of the apps. Got the froyo push today but it wouldn't take, figure it had to do with removing apps and rooting. I recovered the apps and removed root. Downloaded the update.zip and booted into recovery mode to install. I'm now getting an assertion error because the install cannot find /system/bin/playlogo
I've read some threads and noticed some of the root procedures created a playlogo-orig. I don't have that file. I do have playlogos1 though, though I'm guessing that isn't the same file?
Sort of stuck on what to do next. Can't seem to locate a playlogo to download to sdcard. Any help would be appreciated.
deflin39 said:
I used Epic All in One Root and Recovery v2.04 a while back to root my Epic. Uninstalled a few of the apps. Got the froyo push today but it wouldn't take, figure it had to do with removing apps and rooting. I recovered the apps and removed root. Downloaded the update.zip and booted into recovery mode to install. I'm now getting an assertion error because the install cannot find /system/bin/playlogo
I've read some threads and noticed some of the root procedures created a playlogo-orig. I don't have that file. I do have playlogos1 though, though I'm guessing that isn't the same file?
Sort of stuck on what to do next. Can't seem to locate a playlogo to download to sdcard. Any help would be appreciated.
Click to expand...
Click to collapse
Just use Odin to flash back to stock
Sent from my SPH-D700 using XDA Premium App
deflin39 said:
I used Epic All in One Root and Recovery v2.04 a while back to root my Epic. Uninstalled a few of the apps. Got the froyo push today but it wouldn't take, figure it had to do with removing apps and rooting. I recovered the apps and removed root. Downloaded the update.zip and booted into recovery mode to install. I'm now getting an assertion error because the install cannot find /system/bin/playlogo
I've read some threads and noticed some of the root procedures created a playlogo-orig. I don't have that file. I do have playlogos1 though, though I'm guessing that isn't the same file?
Sort of stuck on what to do next. Can't seem to locate a playlogo to download to sdcard. Any help would be appreciated.
Click to expand...
Click to collapse
You are correct playlogos1 is not the same file as playlogo.The one click root should backup playlogo since it still gets run by the script that replaces playlogo it just runs playlogo-orig from the script that is named playlogo that one click installs.
Thanks for the info. I'll give Odin a shot.
Related
I've replaced the file using root explorer. rebooted the now having bootloop.
tried the adb push method posted by bullyfrog but still can make it to work. issit because i have oclf installed and ext2 tools?
im not really good at this, i've got 2 tabs. the previous one did fine with the battery mod, but not my 2nd tab.
i cant update my firmware with oclf installed issit?
Do adb reboot recovery. Then reflash any kernal you have on your sd card.
slideworks said:
I've replaced the file using root explorer. rebooted the now having bootloop.
tried the adb push method posted by bullyfrog but still can make it to work. issit because i have oclf installed and ext2 tools?
im not really good at this, i've got 2 tabs. the previous one did fine with the battery mod, but not my 2nd tab.
i cant update my firmware with oclf installed issit?
Click to expand...
Click to collapse
Just a word of advice: always push framework-res.apk using adb in recovery. My OG Droid would always bootloop if i replaced it using root explorer.
I have a Nexus S(I9023) and used the full Rom to update from 2.3.3 KB3 GRI54 to the 2.3.4 KD1 GRJ22 version, except I can't get my clockworkmod recovery to stick, I unlocked the bootloader and flashed the recovery with clockworkmod 3.0.2.5, and installed the superuser file, except each time I boot into the OS, and then boot back into recovery, the clockworkmod is gone, and I'm stuck with the stock recovery again.
What I did was the following procedure:
Odin flashed back to stock 2.3.3 - KB3 - GRI54
installed the full update 2.3.4 with the recovery
unlocked bootloader
flashed clockworkmod recovery 3.0.2.5
installed superuser
reboot
checked if superuser app was installed successfully - yes
reboot to recovery
And to my surprise the clockworkmod recovery was gone, and I was stuck with the stock recovery again.......
How do you make the CW stick and not have it reverted to the stock recovery?
There is a script that resets it. Been like that for a while. Look in the root threads on how to make it permanent
Sent from my Nexus S
Matridom said:
There is a script that resets it. Been like that for a while. Look in the root threads on how to make it permanent
Sent from my Nexus S
Click to expand...
Click to collapse
Tried looking in the Root threads, but can't find the solution, the funny thing is that I never had this before, only started after updating to 2.3.4.
There's a file in the system's /etc folder named install-recovery.sh. You need Root Explorer to rename it in order to prevent further installs. Mount the "etc" directory as writable using Root Explorer and rename the file (to for example: install-revocery.sh.old).
This will prevent the stock recovery from being installed in the future...
pullermann said:
There's a file in the system's /etc folder named install-recovery.sh. You need Root Explorer to rename it in order to prevent further installs. Mount the "etc" directory as writable using Root Explorer and rename the file (to for example: install-revocery.sh.old).
This will prevent the stock recovery from being installed in the future...
Click to expand...
Click to collapse
Yep. Also if you use this method you will still have to flash CWM one more time after you do what this poster says (the script runs when the phone boots) .
Sent from my Nexus S using XDA App
I had same problem..it worked for me..now should I back up that Tom so I don't gotta do it again??
Sent from my Nexus S using XDA App
pullermann said:
There's a file in the system's /etc folder named install-recovery.sh. You need Root Explorer to rename it in order to prevent further installs. Mount the "etc" directory as writable using Root Explorer and rename the file (to for example: install-revocery.sh.old).
This will prevent the stock recovery from being installed in the future...
Click to expand...
Click to collapse
Thanks for the solution, I did what you described, and things are working now
You just saved me a lot of frustration........
RISHI-O said:
Thanks for the solution, I did what you described, and things are working now
You just saved me a lot of frustration........
Click to expand...
Click to collapse
Guides for rooting had the solution for this problem.Dont frustrate just search )
Sent from my Desire HD using Tapatalk
Okay I verified that if you have s-off you will be able to get root back on your phone if you run the RUU.
As expected the RUU did unroot my phone but it didn't touch s-off. So I downloaded CWM 3.0.0.8 from dougpiston.com and changed it to PB31IMG.zip (this has to be a flashable zip file to work) and it loaded from hboot no problem. I then downloaded the latest superuser app using ROM Manager, version 2.3.6.3 efgh, older versions will not work, and just flashed it through recovery. Superuser does not need to be renamed update.zip you can just leave the name as is and select let me choose zip from sdcard and it installs just fine.
Took a while for me to get superuser running again as I had an older version and I could only find the newest version in ROM Manager.
****YOU MUST HAVE S-OFF FOR THIS TO WORK*********************
kzoodroid said:
Okay I verified that if you have s-off you will be able to get root back on your phone if you run the RUU.
As expected the RUU did unroot my phone but it didn't touch s-off. So I downloaded CWM 3.0.0.8 from dougpiston.com and changed it to PB31IMG.zip (this has to be a flashable zip file to work) and it loaded from hboot no problem. I then downloaded the latest superuser app using ROM Manager, version 2.3.6.3 efgh, older versions will not work, and just flashed it through recovery. Superuser does not need to be renamed update.zip you can just leave the name as is and select let me choose zip from sdcard and it installs just fine.
Took a while for me to get superuser running again as I had an older version and I could only find the newest version in ROM Manager.
****YOU MUST HAVE S-OFF FOR THIS TO WORK*********************
Click to expand...
Click to collapse
I can't seem to find a link to to superuser inside ROM Manager. Can you tell me where to locate it?
thanks,
John
under download rom > extras
kzoodroid said:
under download rom > extras
Click to expand...
Click to collapse
You can also get it from here
Thanks to you both. I didn't even click on the Download ROM because it's premium and I'm still getting my feet wet with the whole root thing. I'm off to try the GB RUU w/radio and then re-root.
What if you have s-on?
You can only re-root if you have s-off. S-on blocks you from replacing the stock recovery with a custom recovery and blocks the installation of superuser into the system folder.
Eventually the Unrevoked team will come up with a new way to root phones but this most likely won't happen till the OTA actually starts to drop and people report how they lost root. And then who knows how long it will take them to do it. Could be a few days to a few months.
kzoodroid said:
You can only re-root if you have s-off. S-on blocks you from replacing the stock recovery with a custom recovery and blocks the installation of superuser into the system folder.
Eventually the Unrevoked team will come up with a new way to root phones but this most likely won't happen till the OTA actually starts to drop and people report how they lost root. And then who knows how long it will take them to do it. Could be a few days to a few months.
Click to expand...
Click to collapse
Jeez, can't believe I screwed myself like that. I'm a regular root/flasher, and no idea how to get my fix now..
deadsoulboy said:
Jeez, can't believe I screwed myself like that. I'm a regular root/flasher, and no idea how to get my fix now..
Click to expand...
Click to collapse
I ran the RUU with all expectations of not being able to re-root my phone just so I could test if the OTA would change the security settings on my phone. I also still wasn't sure if I could even get root back if it was still s-off so I was willing to experiment with knowing full well what could happen. From past experience with the Eris and losing root for about 3 months you have to flash these leaks with all expectations that it will break your phone and not sweat it too much if it does as eventually someone will find a fix.
kzoodroid said:
I ran the RUU with all expectations of not being able to re-root my phone just so I could test if the OTA would change the security settings on my phone. I also still wasn't sure if I could even get root back if it was still s-off so I was willing to experiment with knowing full well what could happen. From past experience with the Eris and losing root for about 3 months you have to flash these leaks with all expectations that it will break your phone and not sweat it too much if it does as eventually someone will find a fix.
Click to expand...
Click to collapse
You're absolutely right. I have no doubt in my mind someone will come up with a way to root 2.3 on the INC
Alright, I've got s-off, downloaded the superuser 2.3.6.3 efgh app from the ROM manager butttt... now what? I've tried to boot into recovery but I just get an icon of a phone with an exclamation mark inside of a triangle, which I'm assuming isn't good.
Flash clockworkmod recovery first, then the superuser zip.
I tried that but it gives me an error saying: "An error occurred while attempting to run privileged commands!".
If you flashed the GB RUU and lost root and/or s-off.
Someone correct me please if I'm wrong but couldn't you download the froyo RUU and load it then root and s-off?
Sent from my ADR6300 using XDA App
How are you trying to flash it? I'd recommend getting the 3.0.0.7 (AMOLED) or 3.0.0.8 (SLCD) recovery from www.dougpiston.com. Flash in hboot. Or is that how you're doing it?
deadsoulboy said:
You're absolutely right. I have no doubt in my mind someone will come up with a way to root 2.3 on the INC
Click to expand...
Click to collapse
The Eris had a manual method (race method) for rooting the phone but I could never find one posted for the Inc. It involved having the phone connected to a pc with adb running and then taking out the sdcard and rebooting, at a certain point of the boot process you counted to 4 and then pushed the sdcard back in. If you did it correctly adb was able to connect to the phone and you could slip a custom recovery and su in. It was rather complicated and only a handful of people ever did it correctly myself included and it was eventually replaced by a one-click method. The one-click method still pretty much does the same thing you just don't have to manually remove the sdcard or have the phone connected to a pc. In some ways the Eris has a lot more support from its community than the Inc does probably because it was Verizons first android phone.
k_nivesout said:
How are you trying to flash it? I'd recommend getting the 3.0.0.7 (AMOLED) or 3.0.0.8 (SLCD) recovery from www.dougpiston.com. Flash in hboot. Or is that how you're doing it?
Click to expand...
Click to collapse
I second this it has to be a flashable version (contains android-info text file + the recovery image) to work. I used the 3.0.0.8 file from doug pistons website which is already to go just needs to be renamed PB31IMG.zip and make sure it isn't being named PB31IMG.zip.zip as file extensions can be hidden especially if you are renaming it on a pc. I downloaded it directly to my phone and renamed it there so the extension wasn't hidden.
swskeptic said:
Alright, I've got s-off, downloaded the superuser 2.3.6.3 efgh app from the ROM manager butttt... now what? I've tried to boot into recovery but I just get an icon of a phone with an exclamation mark inside of a triangle, which I'm assuming isn't good.
Click to expand...
Click to collapse
I beleive that is becasue you stil have the stock recovery? Did you flash the clockwork recovery from dougpiston.com?
I flashed the clockwork mod recovery 3.0.0.7 from dougpiston via hboot.
I tried several different ways to boot into recovery to flash the superuser app but it isn't working. When I try to do it from the clockword mod app it says the same error: "An error occurred while attempting to run privileged commands!".
I tried to manually download the superuser .zip and boot into recovery from the hboot menu, but it still gave me that same phone icon with the exclamation mark and triangle and then nothing.
swskeptic said:
I flashed the clockwork mod recovery 3.0.0.7 from dougpiston via hboot.
I tried several different ways to boot into recovery to flash the superuser app but it isn't working. When I try to do it from the clockword mod app it says the same error: "An error occurred while attempting to run privileged commands!".
I tried to manually download the superuser .zip and boot into recovery from the hboot menu, but it still gave me that same phone icon with the exclamation mark and triangle and then nothing.
Click to expand...
Click to collapse
First thing are you getting into recovery from the hboot menu? And you can't get into recovery from ROM Manager because you need superuser installed to do it that way. It still sounds to me like you don't have ClockworkMod Recovery installed. Maybe only version 3.0.0.8 works I'm not sure but that version is for both amoled and SLCD screens. So either try reflashing your copy of 3.0.0.7 or try flashing 3.0.0.8. I do think I had to flash the recovery a couple times to get it to stick.
I can flash it, it works as it should until I reboot the phone. Once I reboot, the stock recovery comes back. Ive seen threads about deleting a couple files, but not sure if I should be doing that. any ideas on what I may be doing wrong?
blackhemi4x4 said:
I can flash it, it works as it should until I reboot the phone. Once I reboot, the stock recovery comes back. Ive seen threads about deleting a couple files, but not sure if I should be doing that. any ideas on what I may be doing wrong?
Click to expand...
Click to collapse
Stock restores the install-recovery.sh file in /system/etc. This prevents recover mods from "sticking." After you root, load up your favorite root file explorer and delete/rename that file in /system/etc/ . Then, reflash recovery and you're golden.
belyle said:
Stock restores the install-recovery.sh file in /system/etc. This prevents recover mods from "sticking." After you root, load up your favorite root file explorer and delete/rename that file in /system/etc/ . Then, reflash recovery and you're golden.
Click to expand...
Click to collapse
Thanks
Just tried that, but my root explorer is not allowing write access.
Flashed superuser again, same thing....
I starting from scratch again, 4.0.4 is getting installed as I type.
Ill try rooting again and getting my root explorer to delete that file and try again
for some reason my cwm recovery is sticking and its causing my play store to stay on 3.4.7
Any ideas on why the recovery is sticking I didn't even touch the install-recovery.sh
Infact all I did was get the stock image from google flash that
then flash cwm to gain root and install superuser
after that my stock recovery just won't come back, any ideas?
Flash the newest version of su.zip
albundy2010 said:
Flash the newest version of su.zip
Click to expand...
Click to collapse
I got the latest version 3.0.7 it still won't work, I've tried so many different methods including manually flashing the stock recovery but that doesn't help with updating the play store either
---------- Post added at 04:36 PM ---------- Previous post was at 04:35 PM ----------
blackhemi4x4 said:
Thanks
Just tried that, but my root explorer is not allowing write access.
Flashed superuser again, same thing....
I starting from scratch again, 4.0.4 is getting installed as I type.
Ill try rooting again and getting my root explorer to delete that file and try again
Click to expand...
Click to collapse
to allow write access you just have to press "remount as R/W" in Root Explorer
There are different versions of 3.0.7. You should have efghi version.
Also as the other poster said you have to use root explorer the correct way if you're not doing so.
Thanks, its the little things that get me. I had the wrong 3.0.7. Got the efghi and all problems solved. time for a nandroid and mod this thing.
Is there a working circle bat mod for stock 404
Same issue
I had the same issue when I upgraded to 4.0.4.
I used the ADB shell to remount \system as R/W and was then able to rename my install-recovery.sh. After that I installed CWM and it sticks properly.
just download ROM manager from the market and install the newest CWM from the manager, it will stick. That's how I got it to stick
PhoenixIce22 said:
I had the same issue when I upgraded to 4.0.4.
I used the ADB shell to remount \system as R/W and was then able to rename my install-recovery.sh. After that I installed CWM and it sticks properly.
Click to expand...
Click to collapse
I had the same issue, rename the install-recovery.sh and manage to get CWM to stick.
Here's a fix recovery.zip just flash in cwm and it will stick.http://db.tt/B1vOd9K4 I didn't make it, just sharing it.
I've been spending a few hours trying to fix this - when upgrading from 4.1.1 to 4.1.2 either OTA or via sideloading through ADB I get an error saying "assert(apply_patch_check("/system/app/PlusOne.apk" has failed and I am unable to complete upgrade.
I tried downloading 4 different plusone.apk's and none have rectified this problem. I also tried removing the check for plusone.apk from the updater script and re-zipping the files to no avail.
Can anyone help? Either with a correct PlusOne.apk I can put in system/app or by explaining what I can do to update without resettingback to factory first?
I am on 4.1.1, JRO03D. I converted PlusOne into a user app after I got the nexus using TB and have since converted it back to a system app and placed various PlusOne.apk's in the system/app folder.
I APPRECIATE ANY HELP!!!
zdeno888 said:
I've been spending a few hours trying to fix this - when upgrading from 4.1.1 to 4.1.2 either OTA or via sideloading through ADB I get an error saying "assert(apply_patch_check("/system/app/PlusOne.apk" has failed and I am unable to complete upgrade.
I tried downloading 4 different plusone.apk's and none have rectified this problem. I also tried removing the check for plusone.apk from the updater script and re-zipping the files to no avail.
Can anyone help? Either with a correct PlusOne.apk I can put in system/app or by explaining what I can do to update without resettingback to factory first?
I am on 4.1.1, JRO03D. I converted PlusOne into a user app after I got the nexus using TB and have since converted it back to a system app and placed various PlusOne.apk's in the system/app folder.
I APPRECIATE ANY HELP!!!
Click to expand...
Click to collapse
not sure if I will be a big help, but try to download the 4.1.2 OTA upgrade, and put in N7, then hoping you have CWM if not, just install Clockwork recovery if you have not done so, then boot in clockwork recovery, once you are clockwork recovery, make sure "signature check" is disabled, and install from zip option, point where you put 4.1.2 OTA upgrade file, and then reboot.
I am thinking that error you get most likely signature check since you converted to user app and then converted back to system app.
If you have removed any system apps the upgrade will fail.
Download this and flash from custom recovery
http://androidforums.com/nexus-7-all-things-root/630284-4-1-2-update-rooted-users.html
Rootbrain
I am trying to do it through CWM now... if I try the second option, downloading and flashing from the file will I lose all my data and apps, correct? I am trying to avoid having to restore everything.
Thank you both for your help!
jazzespresso said:
not sure if I will be a big help, but try to download the 4.1.2 OTA upgrade, and put in N7, then hoping you have CWM if not, just install Clockwork recovery if you have not done so, then boot in clockwork recovery, once you are clockwork recovery, make sure "signature check" is disabled, and install from zip option, point where you put 4.1.2 OTA upgrade file, and then reboot.
I am thinking that error you get most likely signature check since you converted to user app and then converted back to system app.
Click to expand...
Click to collapse
Just tried this with signature verification disabled and still get the error about "assert failed: apply_patch_check yada yada yada PlusOne.apk"
If you replaced the .apk, did you try removing (after backing up) the .odex?
fozzie said:
If you replaced the .apk, did you try removing (after backing up) the .odex?
Click to expand...
Click to collapse
I am not sure where that .odex lives. I did a search in system and its sub directories and didn't find one for google +.
rootbrain said:
If you have removed any system apps the upgrade will fail.
Download this and flash from custom recovery
URL ABOVE
Rootbrain
Click to expand...
Click to collapse
This worked!!! I downloaded the version with the code removed to check files that had been failing me on google +. Thank you very much!
I had the same issue and just like zdeno888 got it solved by the right package... on the url above INSIDE one of the messages there's a modified version without verification scripting.
THIS IS NOT THE VERSION POSTED ON THE FIRST POST!
i am running stock but rooted and unlocked. when i did the unlock or root it installed a basic version on cwm, i think a custom one someone had created for the nexus 7.
i cannot get this sorted. first i managed to get the ota by clearing the google framework data a few times until it offered but it the failed to install saying something about 'failed to verify whole-file signature'
due to this i downloaded the zip i found on, i think, androidpolice and booted to recovery. that failure said something like 'assert failed:apply-patch-check gmail.apk'
i then found on this thread -
rootbrain said:
If you have removed any system apps the upgrade will fail.
Download this and flash from custom recovery
http://androidforums.com/nexus-7-all-things-root/630284-4-1-2-update-rooted-users.html
Rootbrain
Click to expand...
Click to collapse
but this also came back with a failure, i think it was the gmail one mentioned above.
marc.knuckle said:
i am running stock but rooted and unlocked. when i did the unlock or root it installed a basic version on cwm, i think a custom one someone had created for the nexus 7.
i cannot get this sorted. first i managed to get the ota by clearing the google framework data a few times until it offered but it the failed to install saying something about 'failed to verify whole-file signature'
due to this i downloaded the zip i found on, i think, androidpolice and booted to recovery. that failure said something like 'assert failed:apply-patch-check gmail.apk'
i then found on this thread -
but this also came back with a failure, i think it was the gmail one mentioned above.
Click to expand...
Click to collapse
The OP from that thread took down the link, the only one in his post is now the same zip you already had.
This is the file with checks disabled.
https://www.dropbox.com/s/isqpvb0w26kqjdx/4.1.2edited.zip
Use with caution tho, only flash this is stock rom and kernel.
great, that sorted it so thanks very much.
i presume you have done the update, apart from the rotation are you finding much difference?
Little to none
Most changes in this one were under the hood, as they say.