Related
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.
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
Hi guys.
I rooted my Tattoo, and installed ROM Manager, clicked on first option "Flash latest recovery", and when it finished it showed message "Succesfully flashed". When i rebooted to recovery it just showed yellow ! and picture of phone.
Please help I need CWM to install CM 7 because I am going on a trip.
Note: I have stock rom flashed using RUU, before that I had CM 7.
Sent from my HTC Tattoo using XDA App
PavleSRB said:
Hi guys.
I rooted my Tattoo, and installed ROM Manager, clicked on first option "Flash latest recovery", and when it finished it showed message "Succesfully flashed". When i rebooted to recovery it just showed yellow ! and picture of phone.
Please help I need CWM to install CM 7 because I am going on a trip.
Note: I have stock rom flashed using RUU, before that I had CM 7.
Sent from my HTC Tattoo using XDA App
Click to expand...
Click to collapse
You could either use automated tool from the following thread
[1 Click Root and/or Recovery]Root and ClockWorkMod 5.0.2.0 [UPDATED 02/10/11]
or look at following post for doing it manually
http://forum.xda-developers.com/showpost.php?p=9192029&postcount=21
please check existing threads before posting
I can't access my computer right now, but I rooted Tattoo with Universal Androroot, and still can't flash CWM.
Note: I used Universal Androroot while ago and I did managed to flash CWM.
Sent from my HTC Tattoo using XDA App
1. Format SDCard 2. Place the ROM in the root 3. PowerOff 4. Press HOME + EndCall Button 5. ClockWorkMod Recovery Page Will Appear. 6. Wipe n Clear...Flash
Sent from my HTC Tattoo using xda premium
Can't install ClockwordMod man. Stock recovery appears instead.
Sent from my HTC Tattoo using XDA App
PavleSRB said:
I can't access my computer right now, but I rooted Tattoo with Universal Androroot, and still can't flash CWM.
Click to expand...
Click to collapse
As you are rooted, you could flash recovery using terminal on the phone.
install terminal and Superuser from market
download CWM recovery 3.0.2 from Kalims' thread and place it in root of your sdcard
download flash_image to root of your sdcard
enter following commands in terminal
Code:
su
cp /sdcard/flash_image /data/local/flash_image
cd /data/local
chmod 04755 flash_image
./flash_image recovery /sdcard/recovery_3.2.0.1.img
Thans. I will try it. Is it posibble to install newer version of CWM via terminal?
Sent from my HTC Tattoo using XDA App
I can't download flash_image, says nothinhg was found.
Sent from my HTC Tattoo using XDA App
Try this
Do u have Universal Androot still installed on ur phone? If its there, then re-root with it and launch ROM Manager immediately after that. Flash recovery TWICE. The new CWM has problems flashing in 1st go.
And secondly, if u are on stock ROM, before updating recovery, always re-root with Androot. Because after every reboot, the tattoo_hack.ko module gets unloaded from the memory if you used Universal Androot on stock ROM.
Things to know while rooting stock ROM:
1. HTC Tattoo is HTC's first NAND locked device preventing users to write to system and recovery under normal conditions.
2. This NAND lock can be defeated by inserting tattoo_hack.ko module. This module was created on taking the help of info from a leaked QualComm datasheet.
3. The module needs to be inserted prior to writing to system or flashing recovery.
4. The manual rooting method and Maveric/NTenisOT 1-click method flashes a custom boot.img after rooting so that the NAND remains unlocked everytime the device is used. On the other hand, Universal Androot unlocks the NAND temporarily while rooting and unrooting. If Androot is used, the device gets permanently rooted, but the NAND locks itself after a reboot, until Androot is used again or tattoo_hack is inserted.
5. Custom 1.6, 2.1, 2.2 roms have tattoo_hack added to their modules list to keep NAND unlocked while device is running. On 2.3, however, the unlock code is compiled into the kernel, so the module is not needed.
6. We deal with this module because no one has developed S-OFF for the Tattoo.
7. Most users forget about this module once their Tattoo is rooted. New users oversee this module and run into problems. The CyanogenMod wiki is misleading in 'How to root Tattoo' because of this.
Finally, please sticky this info if possible because I tell this to everyone who has rooting problems.
Thanks. I did everething just like you sad, but no luck.
Sent from my HTC Tattoo using XDA App
download attached flash_image.zip and remove ".zip" extension.
and try as mentioned in my previous of my post.
And remember what sunitknandi mentioned about re-rooting with androot after a reboot.
PavleSRB said:
Thanks. I did everething just like you sad, but no luck.
Sent from my HTC Tattoo using XDA App
Click to expand...
Click to collapse
Go to universal androot. Hit root again. Let it complete.
Then use Root Explorer and mount /system as rw. Or u ca also use Terminal Emulator. Just type these.
su
mount -o remount rw /system
Close terminal.
Go to ROM Manager. Tap Flash ClockWorkMod recovery. First it will take time. Let it successfully flash. Tap again. Let it flash. Tap again. Let it flash.
I am telling you to tap this many times. Because CWM 5.0.2.0 doesnt flash easily. I got so many failed flashes even on CM7. It only gets flashed after a couple of time.
Otherwise, hit menu button on ROM Manager, slect settings and check mark 'Erase recovery before flashing'. Go back and flash recovery twice.
Finally reboot manually. No need to use ROMManager's reboot option. I read that it works rather badly on Android 1.x. Boot with HOME+POWER.
Lemme know.
Btw, the safest method to flash recovery is NTenis's tool. Used it many times without problems because it flashes the boot to disable the write-protection.
sunitknandi said:
Go to universal androot. Hit root again. Let it complete.
Then use Root Explorer and mount /system as rw. Or u ca also use Terminal Emulator. Just type these.
su
mount -o remount rw /system
Close terminal.
Go to ROM Manager. Tap Flash ClockWorkMod recovery. First it will take time. Let it successfully flash. Tap again. Let it flash. Tap again. Let it flash.
I am telling you to tap this many times. Because CWM 5.0.2.0 doesnt flash easily. I got so many failed flashes even on CM7. It only gets flashed after a couple of time.
Otherwise, hit menu button on ROM Manager, slect settings and check mark 'Erase recovery before flashing'. Go back and flash recovery twice.
Finally reboot manually. No need to use ROMManager's reboot option. I read that it works rather badly on Android 1.x. Boot with HOME+POWER.
Lemme know.
Btw, the safest method to flash recovery is NTenis's tool. Used it many times without problems because it flashes the boot to disable the write-protection.
Click to expand...
Click to collapse
Thank you so so much. I rooted using Androot, then typed commands for Terminal and finally flashed CWM from ROM Manager five or six times. Then I used Home + End call buttons and CWM was there.
BTW, thanks to rallepag, too.
Sent from my HTC Tattoo using XDA App
Good so u did it. If u feel like thanking me, would u do me a favor?
Just copy my posts about the tattoo-hack and how to fixed your problem in a thread and share with others. It will come of great help.
I will try to do that via XDA app, because my monitor is currently broken.
Sent from my HTC click using XDA App
sunitknandi said:
Go to universal androot. Hit root again. Let it complete.
Then use Root Explorer and mount /system as rw. Or u ca also use Terminal Emulator. Just type these.
su
mount -o remount rw /system
Close terminal.
Go to ROM Manager. Tap Flash ClockWorkMod recovery. First it will take time. Let it successfully flash. Tap again. Let it flash. Tap again. Let it flash.
I am telling you to tap this many times. Because CWM 5.0.2.0 doesnt flash easily. I got so many failed flashes even on CM7. It only gets flashed after a couple of time
Click to expand...
Click to collapse
Thanks for this. This has been driving me mad the past week or so!
ClockWorkMod 5.0.2.0 Seems to need 5 installs to work properly (and you granting access in the 3rd or 4th install). After that you can use the install from sd card option in rommanager!
WWWeed said:
Thanks for this. This has been driving me mad the past week or so!
ClockWorkMod 5.0.2.0 Seems to need 5 installs to work properly (and you granting access in the 3rd or 4th install). After that you can use the install from sd card option in rommanager!
Click to expand...
Click to collapse
Happy to help!
Eh hehe, its the saying in vodafone's ad.
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.
Get full root without get any bootloop, restart problem while mounting system..
actually i m not a owner of the scripts/apps used in this procedure, i m just sharing here..
all credits goes to original developer of towel root and reboot mount fix...
REQUIRED FILES:
Towel Root.apk
RemountReboot Fix by Abrar9322
STEPS:
First you need adb in pc..if you dont have or dont know what it is please install from here http://forum.xda-developers.com/showthread.php?t=2588979
Install towel root and execute it, then reboot.
Install latest SuperSU from playstore
Open supersu and click yes to install binary
Now Install latest busybox from playstore
Now open busybox and follow below according to ur device
For devices[C1904,C1905,C2004,C2005,C2104,C2105],install busybox in system/xbin[default]
For other devices,install busybox in sytem/bin[change it in busybox while installing busybox]
Copy remountrebootfix.zip anywhere on your computer and extract it.
Open the extracted folder and run install.bat
select option 1( SuperSu ) then press enter.
It asks you to connect your device.
Now Connect your mobile with usb debugging enabled...[Note: if you don't know how to enable usb debugging, click below to show the content]
go to settings > about phone > press on the build number 7 times until it says 'you are now a developer'
Go to settings>developer options>USB debugging.
Grant Root permission when prompt in your phone.
Follow on screen instruction.
Device will reboot, then enjoy full root with locked bootloader...!!!!
SPL Thanks to @geohot, @Snoop05, @mbc07 , @Abrar9322, @ananthtcr....
and if i didnt give credit to anyone..please pm or post here...i will add
or if this is already posted...or if i violated any rule of xda...moderators please remove this thread..
Reboot problem? what is that?can you explain more to me? i also root using towelroot but when i'm restarting my phone, it keep rebooting.. its the problem from towelroot?
BlueSky_Vincent said:
Reboot problem? what is that?can you explain more to me? i also root using towelroot but when i'm restarting my phone, it keep rebooting.. its the problem from towelroot?
Click to expand...
Click to collapse
r u used folder mount or gl2sd or link2sd??
if no, then try... you will get bootloop or restart problem...
actually reboot problem happens when we mount system partion...
so to fix this issue, we should apply reboot fix given by our xda developers....
ananthtcr said:
r u used folder mount or gl2sd or link2sd??
if no, then try... you will get bootloop or restart problem...
actually reboot problem happens when we mount system partion...
so to fix this issue, we should apply reboot fix given by our xda developers....
Click to expand...
Click to collapse
I have link2sd but im not sure whether i mount system or not. When im trying to restart the phone, it keep rebooting. Im flashing a ftf and after that, my phone cant boot up without connecting to the power source. Im already sent to service center but the say that is not battery problem. Can you help me?
Su Binary not installed , and cant install it !
SuperSu ..
I can’t get root on Acro S JB :/ , why ?