So I was trying to change the fonts on my Epic by using these instructions
1. Install SuperUser
2.Install TypeFresh from market and grant super user permission.
3.Install AndExplorer from market(Type Fresh needs this for browsing files)
4.Before proceeding further Back up existing fonts using Type Fresh and Save the files in /sdcrd/fonts.
5.Add your desired .ttf file to /sdcard/fonts and apply using Type Fresh
Reboot the phone and you are done with changing the font
I did everything in the order of those instructions but noticed that when my phone rebooted, it got stuck.
I know I have ClockworkMod and ROM Manager installed but when I try to go to recovery mode by pressing the volume down key + camera key + power, it boots to stock recovery (blue font)
I have a backup that i made through ROM Manager, but was wondering if there was a way to restore the backup ROM even though my epic is stuck on the samsung boot screen. I'm more hoping that I didn't brick my phone...
Try redoing the oneclick for cwm. If u still can't boot into cwm, then I would odin back to stock. There is an awesome how to in the development section.
Sent from my Epic 4G
NOTE
This is took from untermensch's thread in the Vibrant forum so I take no credit for this (http://forum.xda-developers.com/showthread.php?t=833423)
I have noticed some of you are having issues after installing a new kernel or rom, when you boot into recovery you now have 3e, which does not allow unsigned zips to be flashed. With this version of 3e it has no-verification check, now allowing you to flash whatever you want.
This zip has
1) 3e recovery modified to disable signature checking
2) disables the forced wipe after installing any update.
Instructions
1)Download and extract the file below
2)Use a terminal emulator or ADB shell and type.. (or you can use Root Explorer or SGSTools to mount system RW)
Code:
mount -o rw,remount /dev/block/stl9 /system
3)Use a file manager like Root Explorer and copy the recovery file to /system/bin and replace the one there
4)Now, reboot and you should have a modded 3e recovery with no signature verification
You can either leave the modded 3e recovery or you can now flash CWM via Rom Manager
**Just like anything else, I am not responsible if this bricks your phone, this is fairly simple, follow the guide...Do at your own risk**
Old news, we have CWM now in pretty much everything.
Also you cannot just replace the recovery file... you have to replace the images in sbin or in the zImage its self, otherwise you get errors and cannot do anything.
designgears said:
Old news, we have CWM now in pretty much everything.
Also you cannot just replace the recovery file... you have to replace the images in sbin or in the zImage its self, otherwise you get errors and cannot do anything.
Click to expand...
Click to collapse
I done the exact method above and works fine for me...
Place extracted recovery file in /system/bin/ , reboot and flash cwm via rom manager, works perfectly fine...the reason I posted was, if you read Hardcores thread, and seen this in other threads, that after flashing his kernel, when they goto recovery they now have 3e (depending on which method when entering recovery)..alot of people have done it the way I posted with no issues...im not trying to argue with you, you by far know more then me, just posting what worked for me and some others
sounds like a good idea for the people that updated to Rogers froyo that has the 3e recovery. You could just flash a new kernel, but this is definately a good alternative.
Thanks
Sent from my SGH-I897 using XDA App
If you look at Darkyy's rom he has a script that does this.
Thanks, this works flawlessly on a Rogers Froyo Stock. Now I have CWM working and good to go. The only thing left would be to apply some kind of lagfix.
Tested and works with Rogers 2.2 Rom. Thanks
skorchir said:
Tested and works with Rogers 2.2 Rom. Thanks
Click to expand...
Click to collapse
I also have.
Thanks
Works great on Rogers 2.2. Thanks
I tested it on Galaxy S i9000m bell and it work A+
i do not have to flash cf-boot to make unsigned zip to be installed
thanks a lot for your hard work.
only thing is botton function become different then original 3e
but its working A+
I'm a little confused on how the Recovery works..... I have a I897 that I flashed Cognition 2.3b8 to with ROM Manager/CWM and when I chose "reboot into recovery" from ROM Manager from inside Cognition, it worked fine after reloading packages once. A few days ago, I flashed Perception 10.1 with the firebird kernel. After noticing the battery didn't last as long as it used to with Cognition, I did some research and found the SpeedMod kernel K12L. Before I flashed it, I did a backup from ROM Manager which rebooted into CWM with no problems and did the backup with no problem. I have since flashed K12M and K12N. Now I thought I would give Cog 3.0 a shot and wanted to back up my current config with Perception 10.1/SpeedMod K12N. From ROM Manager, I chose to backup, named my backup and the phone rebooted into 3e Recovery and gave the errors you listed above but I don't understand why? Is it because of the I9000 kernel which doesn't make sense since Firebird is a I9000 kernel. Was it from flashing SpeedMod? Also noticed, that only the volume up/down buttons worked, not the power button which is also the select key. Only way out was to 3 button reboot (or pull the battery) which rebooted into CWM and then initiated the ROM Manager backup.
Any ideas why? Also, if I was to ODIN flash JH6 back to the phone, would that restore the Stock 2e Recovery? Sorry for the long post, but I'm still trying to learn this stuff and think you guys are awesome. The captivate would be a crappy phone if it wasn't for you all.
I guess if I had read your second post a little closer I would have seen that flashing SpeedMod causes it. I used your fix in the OP and when I tell it to "Reboot into Recovery" from ROM Manager, it boots into what I assume is 3e (Goes by real quick) and shows something about MOVI and verification and then boots into CWM Recovery v2.5.1.2. If I 3 button boot into recovery, it boots into CWM v2.5.1.0 SpeedMod ULFK. Seems to work now but I'm still confused. Thanks again.
Using sgstools to change mount RW completes its task fine. When I try to copy the new file to /system/bin it does not allow it. The permissions do not change. I tried terminal emulator it doesnt work either. The files stay -r only. I have tried so many times to delete/rename/ or copy over. I just gave up. My system is 2.2 and rooted before you ask.
davidis57 said:
Using sgstools to change mount RW completes its task fine. When I try to copy the new file to /system/bin it does not allow it. The permissions do not change. I tried terminal emulator it doesnt work either. The files stay -r only. I have tried so many times to delete/rename/ or copy over. I just gave up. My system is 2.2 and rooted before you ask.
Click to expand...
Click to collapse
Use a terminal emulator or adb shell and type...
Code:
chmod 777 /system/bin/recovery
That should give r/w permission to the file, ...i just tested to verify it and it worked for me. also if you have Root Explorer you can just long press the file and select Permissions and check all the boxes.
Exact the same thing is happening to me! Beforehand I had flashed CF Root to get Superuser also at the same time when rooting. I Still can boot into recovery with 3BR and come into the speedmod ULFK settings. Speedmod introduces 3e and you need signed packages. You must have 2e for this I assume!? Can anyone tell me what goes wrong?
Im using the Speedmod kernel and it always pissed me off that everytime I wanted to flash somethng via CWM that I had to pull the battery and restart my phone for it to finish because of the 3e 'no signed packages'
I did the steps in the OP and I noticed that I didnt even have a recovery file in system/bin but I put it in there anyway. I rebooted and flashed a different modem just to check and sure enough, it worked. Now I dont have to worry about pulling my battery and having to reboot my phone everytime I want to flash something.
Thanks for this!
Well the file is moved now. I get reinstall packages in recovery and thats all does. I installed rom manager and have cwm on my sdcard. The phone does not go into cwm recovery. It doesnot give me options to apply install.zip. I have dxjpa and z4root running. This modded recovery does not work. Any ideas?
davidis57 said:
Well the file is moved now. I get reinstall packages in recovery and thats all does. I installed rom manager and have cwm on my sdcard. The phone does not go into cwm recovery. It doesnot give me options to apply install.zip. I have dxjpa and z4root running. This modded recovery does not work. Any ideas?
Click to expand...
Click to collapse
Once you install cwm and reboot back into 3e, select reinstall packages, it will install cwm and then load into it , if it doesn't then the file didn't copy over, make sure it replaces it ok, I've used this quite a few times and it works everytime, and everyone that has posted has not had an issue, so it does work
Sent from my SGH-I897 using XDA App
It did copy over in fact i deleted the old one and put the new one in its place. It never installs anything and seems to error but its so fast i cant read it.
Sent from my GT-I9000 using XDA App
davidis57 said:
It did copy over in fact i deleted the old one and put the new one in its place. It never installs anything and seems to error but its so fast i cant read it.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Try starting over, delete the recovery file and also delete the update.zip on the root of the sdcard, then copy the modded recovery over to /system/bin/ , then open rom manager and install cwm again, something could have happened with the update.zip, cause if you are able to get into 3e and select reinstall packages and it actually starts but errors out with the update.zip, then something could possibly be wrong with the update.zip .. it might restart after you select reinstall packages, but it should then load in to cwm, if it doesnt and boots back into android, then go into rom manager and select restart recovery and see if that works
I just loaded SyndicateROM and wanted to flash the stock Sprint boot animation back onto my phone, so I found this thread here:
http://forum.xda-developers.com/showthread.php?t=951184
And tried using the attached file ("epic_stock_boot.zip") and flashing it in CWM, and it successfully removed the ACS boot animation, but it then boots immediately to the phone without displaying the bootanimation or the sound. I am curious as to if I am doing anything wrong. Do I need to mount /system in CWM before flashing? Is there an alternative to do this other than flashing the .zip file, for example, can I adb push/Root Explorer push the .qmg files to a certain folder in /system? Any help is greatly appreciated, thanks.
-BP
Hello, I tring to get root on my Nexus 7.
I install the clockwork recovery and then install the JB-SuperSU, but every time I reboot, I lose the recovery.
How could I keep the recovery?
Thanks and best regards.
Which version of CWM are you using? I believe 6.0.1.0 comes with a script that tweaks certain files to make it easier to get back in to recovery. It should prompt you the first time you select "reboot system now".
Also, are you trying to get into recovery from the boot screen (i.e. power + volume buttons) or through an app's rebooter? I've never had luck doing it the first way, but getting in through the reboot function on Titanium Backup or ROM Toolbox should work.
Sent from my DROID BIONIC using xda app-developers app
Can you boot into stock N7 recovery?
If so, find a superuser.zip (or something similar to this name) compatible with the N7, then put into the root of the N7, Install zip from SD. <------------------------- YOU DO THIS AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR ANY DAMAGE.
Have you unlocked your boot loader?
Thanks,
I am using recovery-clockwork-6.0.1.0-grouper.img, I think that it is a problem of Hosts Editor app. It says that I have no read/write permission.
I access from "adb shell" and I can execute "su" command. How can I check if I have full root access on the device?
Thanks and best regards.
Is anyone else having loads of problems with clockwork mod and rom manager since updating to 4.2.1
For me RM doesnt do anything and I CWM keeps will not re-flash a backup unless its 4.2.1. Even though I copy n past to new directory where CWM keeps backups but will not reflash them. Also everytime after I use CWM it seems to delete itself and i have to reflash via the command line. Help welcome. Thx in advance....
Update: Not sure if its RM or CWM. Have just worked out CWM is deleting itself everytime after use. IT doesnt leave any other option once you try to re-boot device from CWM....
veroby said:
Is anyone else having loads of problems with clockwork mod and rom manager since updating to 4.2.1
For me RM doesnt do anything and I CWM keeps will not re-flash a backup unless its 4.2.1. Even though I copy n past to new directory where CWM keeps backups but will not reflash them. Also everytime after I use CWM it seems to delete itself and i have to reflash via the command line. Help welcome. Thx in advance....
Update: Not sure if its RM or CWM. Have just worked out CWM is deleting itself everytime after use. IT doesnt leave any other option once you try to re-boot device from CWM....
Click to expand...
Click to collapse
There's a file in /system that you should either rename or delete called: recovery-from-boot.p
That reloads the stock Android recovery at each reboot. Then once you have renamed/deleted it, reflash CWM Recovery again from the command line and it should stick now.
You're using the latest CWM Recovery correct? I don't use RM or CWMR at all (TWRP), so I may not be able to totally help out.
RMarkwald said:
There's a file in /system that you should either rename or delete called: recovery-from-boot.p
That reloads the stock Android recovery at each reboot. Then once you have renamed/deleted it, reflash CWM Recovery again from the command line and it should stick now.
You're using the latest CWM Recovery correct? I don't use RM or CWMR at all (TWRP), so I may not be able to totally help out.
Click to expand...
Click to collapse
Hey thx - I have always used them and found them to be easy tools in the past. Dont really want to change to TWRP but it seems all recommendations are leaning towards and its the way to go with 4.2.1. Thx again... I have to ask why that file exist in the first place. Just to catch donkeys like me out.....Also if you know and are still around. Is there a way to restore old backups from 4.1.1
veroby said:
Hey thx - I have always used them and found them to be easy tools in the past. Dont really want to change to TWRP but it seems all recommendations are leaning towards and its the way to go with 4.2.1. Thx again... I have to ask why that file exist in the first place. Just to catch donkeys like me out.....Also if you know and are still around. Is there a way to restore old backups from 4.1.1
Click to expand...
Click to collapse
I've had no issues flashing 4.1.1/4.1.2 ROMs to 4.2.1 and vice versa...but again I'm using TWRP Recovery.
The file is in the stock images from Google, and it's there to reload stock Android recovery at boot...other than that I'm not sure of the exact reasoning.
I know that Android 4.2 has multi-user support, and that has been the cause for many issues with 4.2 in general due to it creating a folder /sdcard/0...so flashing multiple 4.2 ROMs without the latest CWM Recovery version 6.0.1.9 would cause another folder created there at /sdcard/0/0...and so on. If you created another user, they would have their own folder at /sdcard/1...and so on.
I would make sure that you have the latest CWM Recovery flashed to your device, then put your backup in the correct folder. From what I remember when using RM and CWM, there's the folder for your backup and then one level up from that there's the blobs folder, you'll need BOTH of those in order to restore things, as the blobs folder is the backup.