Bootloop after replacing framework-res.apk - Galaxy Tab General

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.

Related

[Q] Froyo Update - playlogo

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.

gingerbread root question... help appreciated

So I got gingerbread, updated from rubix 2.01. Question is would z4root would to root it. Or do I absolutely have to sbf to 2.2 and get rooted gingerbread file? Thanks
the rageagainstthecage exploit doesn't work on 2.3 (z4root) so right now you will have to sbf and flash the prerooted one.
tried running sbf app and it didnt like me.. clicked start nothing happened... had all drivers as well.. i dont know
Droid2kev said:
tried running sbf app and it didnt like me.. clicked start nothing happened... had all drivers as well.. i dont know
Click to expand...
Click to collapse
the gb file is flashable through clcokwork recovery
Sent from my DROID2 using XDA App
And you don't have to wipe. It's signed as an update so all your apps and settings will be the same.
Sent from my DROID2 using XDA App
so i can grab the sbf and stick it through recovery as if i would with any other file update and put it on root of the sd card?
Droid2kev said:
so i can grab the sbf and stick it through recovery as if i would with any other file update and put it on root of the sd card?
Click to expand...
Click to collapse
Yes. What they did was they took the .sbf file, and converted it into an update.zip format so we can flash it in recovery.
So just get the file in sbf format and stick it on sd card and go from there correct... thanks
Is Clockwork ROM Manager the same as Recovery? I looked in the Market, but it only brings up Clockwork ROM Manager in the search.
I would install ROM Manager on my phone, put the update.zip file in the root directory of the SD card and then run it with ROM Manager?
silverfang77 said:
Is Clockwork ROM Manager the same as Recovery? I looked in the Market, but it only brings up Clockwork ROM Manager in the search.
I would install ROM Manager on my phone, put the update.zip file in the root directory of the SD card and then run it with ROM Manager?
Click to expand...
Click to collapse
Yes clockworkmod is the same as the custom recovery. You need to get Droid 2 bootrstrap recovery app from the market. The droid 2 bootloader is locked, preventing us from completely flashing a custom recovery. the bootstrapper is the only way to get to clockwork.
hey OR, i got the bootstrap recovery unfortunately its not working. i got the correct one for the droid 2 but it keeps saying error running exec(). command and it list a lot of other writing as well. i also tried rom manager to reboot into recovery with the result of it saying error while trying to run privileged command.. what shall i do
Droid2kev said:
hey OR, i got the bootstrap recovery unfortunately its not working. i got the correct one for the droid 2 but it keeps saying error running exec(). command and it list a lot of other writing as well. i also tried rom manager to reboot into recovery with the result of it saying error while trying to run privileged command.. what shall i do
Click to expand...
Click to collapse
Uninstall bootstrap and reinstall, be sure to give it su permission.
how do i assign it superuser again?
Is your phone rooted?
no i cant root it, cause it has the 2.3 leaked update on it... i put super user on it and it wont give me access to bootstrap until i install an update it said it put on my sd card but i cant reboot into recovery to even alow the superuser update... frustrating
Download SuperOneClick to computer, link to phone with USB debug on, click "root".
Voila!
Edit: Flash back to Froyo, root with SuperOneClick, bootstrap clockwork recovery, then install .zip file with rooted Gingerbread.
hey man i cannot ind a link to it, u got one? and it will work on 2.3 droid 2? thanks
figured it out

[GUIDE] Enabling old-school CRT off animation in Gingerbread

For this you need to be running the ROOTED Gingerbread leak on a Droid X.
IF YOU HAVE MADE MODIFICATIONS TO YOUR FRAMEWORK-RES.APK, DO NOT USE THIS FILE. You'll have to make your own.
All thanks go to the guys in this thread for directions. This is just the finished framework-res.apk
Flashable zip:
johnclevenger said:
I posted this in the other thread as well. I created a zip that you can flash from clockwork.
1. download to somewhere on sdcard
2. boot into clockwork
3. make a backup
4. install zip from sdcard, etc.
5. reboot
http://www.multiupload.com/FD85GYCAJM
Click to expand...
Click to collapse
Manual Instructions
Download: http://www.megaupload.com/?d=4TTAF6OM
Rename to framework-res.apk
Connect your phone via adb and run these commands
Code:
adb remount
adb push framework-res.apk /data/local/tmp/framework-res.apk
adb shell
su
stop
rm /system/framework/framework-res.apk
cp /data/local/tmp/framework-res.apk /system/framework/
rm /data/local/tmp/framework-res.apk
reboot
Your phone should reboot and be good to go.
Verified working on a rooted Droid X 2.3
Definitely going to try this!
Worked perfect on my Dx! Damn is that sexy!!! Thanks man! Did u happen to deodex the system yet?
This is that awesome animation when you turn it off???
Sent from my DROIDX using Tapatalk
Yes this is the awesome animation.
Beamed from my MB810
I posted this in the other thread as well. I created a zip that you can flash from clockwork.
1. download to somewhere on sdcard
2. boot into clockwork
3. make a backup
4. install zip from sdcard, etc.
5. reboot
http://www.multiupload.com/FD85GYCAJM
I can confirm the zip worked great. Thanks a lot.
Beamed from my MB810
johnclevenger said:
I posted this in the other thread as well. I created a zip that you can flash from clockwork.
1. download to somewhere on sdcard
2. boot into clockwork
3. make a backup
4. install zip from sdcard, etc.
5. reboot
http://www.multiupload.com/FD85GYCAJM
Click to expand...
Click to collapse
Looks awesome. Thanks for making it into a zip. I'm so excited to show it off. Haha.
Well, that sufficiently screwed my phone up... SBF it is.
EsotericPunk said:
Well, that sufficiently screwed my phone up... SBF it is.
Click to expand...
Click to collapse
Worked for me
Beamed from my Gingerbreaded DroidXtreme
Anyone have any idea why my Clockwork Bootstrap is not working?
I'm on the leaked rooted GB, trying to bootstrap recovery to install CRT animation.
I know my root works because I've used root explorer just fine.
I load up Koush's Bootstrap Recovery, Bootstrap, get the Success message (first time I ran it I approved Superuser permissions), I then Reboot Recovery.
Upon reboot, I get the red Motorola logo followed by nothing but a blank screen. It requires a battery pull at this point, upon which it then just boots normal afterward.
I've rinsed and repeated several times and I've uninstalled and reinstalled Koush's Bootstrap as well....same issue.
gc14 said:
Anyone have any idea why my Clockwork Bootstrap is not working?
I'm on the leaked rooted GB, trying to bootstrap recovery to install CRT animation.
I know my root works because I've used root explorer just fine.
I load up Koush's Bootstrap Recovery, Bootstrap, get the Success message (first time I ran it I approved Superuser permissions), I then Reboot Recovery.
Upon reboot, I get the red Motorola logo followed by nothing but a blank screen. It requires a battery pull at this point, upon which it then just boots normal afterward.
I've rinsed and repeated several times and I've uninstalled and reinstalled Koush's Bootstrap as well....same issue.
Click to expand...
Click to collapse
I believe you have to use the droid 2 bootstrap to be able to get into recovery
Sent from my DROIDX using XDA App
Ahh...so I have to purchase the Droid 2 Bootstrap now too...
Yup would have to use D2 bootstrap, its too bad that since already had dx bootstrap purchased .
Why doesnt the dx bootstrap work ?
gc14 said:
Ahh...so I have to purchase the Droid 2 Bootstrap now too...
Click to expand...
Click to collapse
You can get it for free from the Gingerbread prerelease thread on My Droid World
Sent from my DROIDX using XDA App
Free? Is this sanctioned by Koush, or did someone just illegally post a pirated apk up without the author's permission? I'm all about free stuff, but I'm not looking to rip anyone off.
Sent from my DROIDX using XDA App
Koush gave away both apks free on his website, but the links are broken now.
hanone said:
I believe you have to use the droid 2 bootstrap to be able to get into recovery
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
same thing happened to me and tried using d2 boot strap
and still didn't work it took the file but it still has the same on off
ant ideas?
I don't know...mine worked just fine after I installed D2 bootstrap.
You need to use the Droid 2 bootstrap.
Sent from my DROIDX using Tapatalk

2.3.4 Update resets CW back to stock recovery

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

CWM not sticking on 9020a after official 4.0.4

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.

Categories

Resources