Related
Was wondering which recovery everyone likes and why. Been using Ra since my G1 and I love it. (searched around for one of these and didnt see it. Mods delete if there was already one of these polls)
Amon all the way
Sent from my EVO using the Earths core to power my death ray
So...since this brought up...I see that some ROMs don't work with some recoveries? Is that correct? I swear it seems some ROMs only work with clockwork...but then I read all over that clockwork is buggy...or doesn't seem to work for everyone...or something.
I was thinking Amon Ra was the way to go.
I'll follow the answers to this one as well.
sablesurfer said:
So...since this brought up...I see that some ROMs don't work with some recoveries? Is that correct? I swear it seems some ROMs only work with clockwork...but then I read all over that clockwork is buggy...or doesn't seem to work for everyone...or something.
I was thinking Amon Ra was the way to go.
I'll follow the answers to this one as well.
Click to expand...
Click to collapse
Thats true. As far as I know, there have been issues with Clockwork not wiping correctly(I know someone like that)and causing bootloops after flashing. I dont know of any roms that dont work with Ra, but I believe Rom Manager will only work with Clockwork.
Clockwork since it is compatible with ROM Manager.
Clockwork since it has a back option in the menus. It's also updated frequently.
I've been running clock on the evo. I tried putting amon in but I guess I'm too stupid cause when I tried following the directions, I borked the phone good and it took me awhile to get everything back into working order. I could flash it now with rom manager but I'm kinda afraid after the last fiasco.
Sent from my PC36100 using XDA App
I've found that using both have worked for me the best. If I'm running Fresh Rom I will use Amon Ra's but I'll use clockwork for cm6. Its so easy to jump back and forth between recoveries using rom manager its never really an issue. Either way both developers are awesome and their recoveries both have good things to offer
anyway to switch back to Amon? not feelin the Clockwork im too use to it...
seriousblack25 said:
anyway to switch back to Amon? not feelin the Clockwork im too use to it...
Click to expand...
Click to collapse
Use ROM Manager to "flash alternate recovery."
another poll
dglowe343 said:
Was wondering which recovery everyone likes and why.
Click to expand...
Click to collapse
i was wondering the same thing exactly!! So a few days ago i asked the question on the Cyanogen forums... I got a lot of good responses and summarized the comments on the first post... check it out here: http://forum.cyanogenmod.com/topic/2562-best-recovery-for-evo-to-use-with-cm6/
I haven't had one single problem with clockwork recovery.
I like the recovery originally included with toastcfl's root found here. it's very similar to Armon's (don't know if things have to be signed or not), but you use the power button to go back instead of the double-press volume (which I find annoying to do).
I just don't like clockwork as much as the other two, that's just the way it is.
Using Amon Ra because I think it's the only recovery fully compatible with DamageControl.
Not sure of the actual "differences" between it and Clockwork - can anyone clarify?
oblivion0 said:
Using Amon Ra because I think it's the only recovery fully compatible with DamageControl.
Not sure of the actual "differences" between it and Clockwork - can anyone clarify?
Click to expand...
Click to collapse
I'm using clockwork with Damage Control I've had zero problems so far.
I hate Amon recovery... always have to move my ROM downloads to the root of the SD card... forget it 90% of the time and have to reboot to fix it... and that doesn't work so well if I borked my ROM.
I use Clockwork and have zero issues unless I'm trying to autoflash theme updates and such so I have to do those manually. Otherwise no complaints. And no signing issues with Clockwork either.
Amon_RA's recovery FTW!
Well, since rooting 24 hours ago, I've been using Clockwork via recovery boot (not through ROM Manager) and it's worked flawlessly so far. Backed up my rooted stock setup, flashed Fresh, DC, CM6, and then back to Fresh, wiped between every flash, and I've had no problems. Even flashed some Fresh Tweaks in the recovery boot. I actually flashed Amon Ra to see how I liked it . . . and I didn't. Mostly just navigating was a pain with the volume up+down thing, everything else seems like a wash. My only question is whether the Dalvik cache is really being wiped by Clockwork, since it takes half a second to complete when I select the option. I'm going to test it in a few minutes here.
Going to give Baked Snack a run for a while, we'll see how that holds up.
I have wondered that for awhile, silver. It may sound stupid but at least a confirmation in the log messages below would be nice.
Sent from my PC36100 using XDA App
herbthehammer said:
I have wondered that for awhile, silver. It may sound stupid but at least a confirmation in the log messages below would be nice.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Okay, I decided to test. Fired up ADB and booted into recovery from Android. Mounted /data and looked inside /data/dalvik-cache. There was a long list of .dex files. Then I unmounted /data and used the Clockwork menu to wipe the Dalvik-cache (this option is located under the "advanced" menu, NOT just the "wipe cache" option). Re-mounted /data and looked inside . . . and the dalvik-cache directory was gone. It took *slightly* longer than normal when I actually hit the button to wipe it (more like .7 seconds instead of .5), but it does appear that my Clockwork v2.5.0.1 is wiping dalvik just fine. And, of course, when I rebooted back into Android (rooted .6 stock at the moment) it took a long time to boot at the 4G screen, as the cache was being rebuilt. Once I was back in, I checked the /data directory again and dalvik-cache was back and full of .dex files again.
So there. No more speculating, just science.
And if you're ever worried about it, you can just use ADB to wipe the dalvik-cache yourself:
Code:
adb shell
mount /data
rm -rf /data/dalvik-cache/*
Then you can use the Clockwork menu to wipe everything else and flash your ROM. These three commands actually just delete everything inside the dalvik-cache directory, whereas Clockwork appears to remove the directory entirely. Doesn't really matter either way, the system will replace the directory if it gets deleted.
Mmm . . . terminal code.
ok so i messed up my fascinate, im smart enough to use odin to restore, however its still fu*ked.
i am unable to set ANYTHING, ringtones, notifications, wallpapers. Cant download anything from the market. unable to get root access (used super one click) process shows complete (have su icon but it force closes when i open it, root explorer doesnt work) im totally lost at the moment! ive checked A LOT of forums and nothing is working. i have cwr and am able to load custom roms(dont know how its working..) Im unable to get to stock recovery to stock wipe. PLEASE SOMEONE HELP i know this can be fixed somehow.
now in the RIGHT area
fuzz1 said:
ok so i messed up my fascinate, im smart enough to use odin to restore, however its still fu*ked.
i am unable to set ANYTHING, ringtones, notifications, wallpapers. Cant download anything from the market. unable to get root access (used super one click) process shows complete (have su icon but it force closes when i open it, root explorer doesnt work) im totally lost at the moment! ive checked A LOT of forums and nothing is working. i have cwr and am able to load custom roms(dont know how its working..) Im unable to get to stock recovery to stock wipe. PLEASE SOMEONE HELP i know this can be fixed somehow.
Click to expand...
Click to collapse
If you want help, you might want to post in the right forum first.
Did you have voodoo and the permanent cwr mod?
Moved to general. You were right the first time. Questions like this are not development, and belong in the general section.
Please don't make 2 threads either, as you posted it in the right place in the first instance.
Wipe data and cache in stock recovery from stock recovery would be a good start.
Sent from my SCH-I500 using XDA App
Floormatt said:
Did you have voodoo and the permanent cwr mod?
Click to expand...
Click to collapse
i had installed voodoo, and tried to install diff kernal over it(seeing thats what messed things up) followed steps to remove voodoo and yes permanent cmr
ksizzle9 said:
Wipe data and cache in stock recovery from stock recovery would be a good start.
unable to get to stock recovery, tried booting w vol up+power, vol dwn+power, vol up+dwn+power, cmr reboot into recovery, noting works
Click to expand...
Click to collapse
In the permanent cwr thread you should find the file to flash to get stock recovery back.once that is done try the stock wipe. If that doesn't fix then go to the sticky for removing voodoo in the dev sub-forum
This post is only for discussing all issues regarding the use of the Bonsai roms. We can talk here about any version from 1.0.0 to x.x.x
Due to some political issues please do not post any links to the Bonsai website! This thread is just for us users and don't expect the developers of Bonsai to ever visit here.
One last thing >
nor
Yes this try to keep this thread open.
Sent From My Evo Killer!
So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Sent from my SPH-D700 using XDA App
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Were you using CWM 3.0.0.6 or 3.0.0.5 ?
Sent from my SPH-D700 using Tapatalk
Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?
abrcrmdl23 said:
So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Click to expand...
Click to collapse
I can't remember what stepping is on the kernel as we have been beta testing 4.0.1 and have been mainly dealing with a new setCPU governor called interactive. Were also still working on the other governor called smartass as well. I think that the stepping goes directly from 400 to 800, but we are always looking to go faster and with better battery life. I'll bug Randy and Mammon about it.
The sound will be Voodoo version 7, but I don't think the Voodoo color fix is going to make it into 4.0.1. Sorry, but we can't do everything...at least not all at the same time.
forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Did I see a similar post on the Bonsai website earlier today? I just want to verify that you were using CWM 3.0.0.6 as anything else will cause problems like that. Also when you get to these kinds of problems you should attempt a second flash of Bonsai before going to the trouble of a ODIN job. A second flash seems to fix a whole variety of odd kind of problems.
As you can imagine with all the beta testing I do I'm always finding ways to corrupt my phone. Some days I have managed to bork it 3-5 times.
I decided to test out today a 4.0.1 install directly from DI18 > CWM 3.0.0.6 > Bonsai 4.0.1 full rom. It went great with no problems at all and running just fine, so far
I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0
bluetooth
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?
forcelite said:
Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?
Click to expand...
Click to collapse
Do not use Rom Manager to be installing the beta CWM files. The correct way is with one of the 1 step CWM tools in the development forum. 3.0.2.4 is half-finished and is very difficult even to navigate through the various menu's. I know this because I tried out that CWM version for some grins one day. It will majorly screw your Epic if your not extremely careful. When DI18 was prevalent Rom Manager worked great to root your phone. When we started the move into the Froyo roms Rom Manager quit working and that is why the 1 click then became more prevalent.
Just follow the directions posted all over the place and Bonsai will install just fine and you will be a happy camper.
I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Thx All,
Force
forcelite said:
I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0
Click to expand...
Click to collapse
The linked one is the correct one for Bonsai version 4.x.x.
olddocwhite said:
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?
Click to expand...
Click to collapse
Some people do and some don't I do know that Randy has instituted quite a few bluetooth linux upgrades into 4.0.1 rom. Some people are able to clear the data, but the problem usually reappears. Mattalica76 has the link to a more permanent fix to this problem, give him a PM.
Duplicate... Sorry
forcelite said:
I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Click to expand...
Click to collapse
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.
Actually it didnt boot this time either, it installed the firs ttime fine, then kept booting after samsung in a loop,
So I went into CW3 and tried to flash bonsai 4.0.01 again and it gave me this error. It is long, however I shortened it, I have the whole error photo copied)
Finding package
Opening package
Install update
Assert failed getprop (“ro.product.device)”)
Sph-700
E:error in /SDcard/bonsai……….
(status 7)
Installation aborted
Top Nurse said:
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.
Click to expand...
Click to collapse
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
CWM3 will convert your filesystem to ext4 the first time you boot into it. It won't touch the sdcard so that won't be converted. After CWM is finished with the conversion, do not reboot the phone, you will then flash Bonsai.
forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
After flashing the boot script of cwm 3.0.0.6 you then have to power off. Then hold down the camera button, vol down, and power keys at the same time and the EXT4 script will automatically start to format your system. Please keep in mind that it is not formatting the SD card, but only the read only memory of the phone.
After you finished a few beers it will be done and will drop you back to cwm. Do not reboot, but flash bonsai. After bonsai is finished then reboot.
Sent from Bonsai 7.0.3
Hey guys my MyTouch 4g froze while updating flash lastnight
I was runnung the stock deodexd bloatware removed updated rom that is in
the dev section (Icannot remember who it belongs to)
I rebooted the phone and it frove on the splash screen
I rebooted into the bootloader
It wont let me do a factory wipe, and 4ext touch will not finish
installing any of the 4 backups I have on the sd card
I was finally able to flash CWM Recovery 2.5.0.7 but cannot get anywhere
To top it off my phone will not connect to my computer so I can
use adb. All I can do is place files on the sd card and try to push them from recovery
When I boot into recovery I get the following error
booting into safemode...
please format all partitions
after 7 minutes it says
E:Cant open /cashe/recovery/log
E:Cant open /cashe/recovery/log
E:Cant open /cashe/recovery/last_log
E:Cant open /cashe/recovery/last_log
cannot mount system, sdext, sd card, or MISC
can't mount /dev/block/mmcblk0 or mmcblk0p1
Would someone mind helping me out. I also tried to flash the
PD15IMG.IMG...nothing.I dont know if the partitions are jacked or what
S-OFF
HBOOT-0.85.2007
emmc-samsung 2151mb
rooted
Hi,
I guess in your frustrated mood, like many before you, you also need a dedicated, special confirmation that you're not an exception to the rule, and just reading "if this and that - your phone is screwed" doesn't work for you. So I'll honor your feelings by writing it 10000th time again.
Look at Glacier Wiki, section "Troubleshooting". Or at the topmost sticky in General section. Or in Q&A. Or search for any part of the error message you're getting. You'll receive the same reply:
If you flash PD15IMG and it either doesn't complete or shows you Fail-PU on one of the partitions - YOUR PHONE IS DEAD, AND THERE IS NO WAY BACK.
Have you tried wiping dalvik and cache and rebooting recovery? Make sure you unmount cache also. My phone did this before too, and that's what I did to fix.
Sent from my HTC Glacier using xda premium
did you even read before posting?
if you did, you would've found this...
http://forum.xda-developers.com/showthread.php?t=1394238
saranhai said:
did you even read before posting?
if you did, you would've found this...
http://forum.xda-developers.com/showthread.php?t=1394238
Click to expand...
Click to collapse
Yes, yes I did along with a lot of other posts re the same topic.
BTW your link for the PD15IMG.zip is dead due to our wonderful government
and must I refer you to your post about you being mean to others ;p j/k
If I could get my phone to connect to my computer I could use adb no problem. But something with the driver is stopping it from connecting.
Ok thanks to PCLiteratesJax I was able to dl a good PD15IMG.zip. Phone is now stock and running good
I've finally lost patience with my TF101 boot looping and being flat when I come to use it. Asus clearly aren't in a rush to fix it, and I can't find an alternative tablet that I'm happy to replace it with right now, so I've decided to give guevor's version a go.
The problem being that I've read a load of threads on rooting a TF, but still haven't come to a conclusion on which method actually works for a WW one on 9.2.1.17, if there even is one!
So any chance some one could help me out and point me in the right direction? Thanks
Use Vipermod to root. Search the forum for link.
Thanks, I'll take a look.
Just wanna check my list with you experienced guys before getting stuck in, mostly because it's been a while since I did anything like this and I can't find a thorough guide for the whole process.
1. Root with vipermod.
2. Install ROM manager from the market and use to flash CWM recovery.
3. Boot into CWM recovery and make backup.
4. Copy kernel .zip file to storage of the TF.
5. Boot into CWM recovery and select install .zip option.
6. Enjoy new kernel and hope for no more bootloop/flat battery scenarios making me angry?
Correct, except you shouldn't use apps like Rom Manager to do things that you can easily do yourself. Don't blindly flash whatever Rom Manager tells you to because sometimes it will screw up your tablet. Haven't you read all these threads about people having problems because of ROM manager?
Just use the recovery installer apk by Gnufabio. It will flash a slightly outdated CWM but it works without problems and you can update it yourself by downloading and flashing a newer CWM posted on this forum.
I can confirm viper for root, and gnufabio recovery installer.apk. I just went through the process last night. If you do not use gnufabio you will spend hours trying to get cwm on your device, and failing.(2 hours of dead androids in recovery) wish i had seen gnufabio sooner.
Edit: also theres a remixed viper out there supposed to be a 1 click root
http://forum.xda-developers.com/showthread.php?t=1534475 is the link
Also i suggest the touch cwm from
http://forum.xda-developers.com/showthread.php?t=1213723
It works very well and all touch so no need to press physical buttons.
Thanks for the input guys, it's very much appreciated.
I haven't seen the threads on problems with ROM manager. I've just been searching for specific terms and TBH I find this forum generally difficult to find up to date information. It's very time consuming searching and reading lots of nothing posts. The TF info threads have a lot of links to outdated guides (or ones that lack detail as they assume you know everything already ) and a lot of the shortened terminology that's used is confusing unless you visit here. I've read as much as I can, but I wanted to be sure I had the right information before trying out something that could render my tablet useless.
Typical, fallen at the first hurdle!
"hold volume down and power for 3 seconds, let go of power only, then press volume up when prompted on screen" just results in a screen with an Android with a red triangle on his chest. More extensive searching needed I suppose.
lol nope this is my problem i told you about in earlier post
get the recoveryinstall.apk by gnufabio install it on your tf and run it. it installs a working cwm then you can do the touch cwm,kernel rom etc after that
gnufabio installer link
http://forum.xda-developers.com/showthread.php?t=1346180
Oops, yeah sorry that passed me by some how! Busy day.
Thanks again!!
no problem bro thats what we are here for to help you catch those moments when your about to bash your head against the wall and say "oh hey didnt you see this..." and make you slap your forehead instead.
Finally got around to doing this. All OK so far, got it rooted and touch CWM installed but I'm a bit unsure about what caches and stuff I should wipe. Do I need to do both wipe data/factory reset AND/OR wipe cache partition in the touch CWM recovery before flashing the new kernel?
wolvers69 said:
Finally got around to doing this. All OK so far, got it rooted and touch CWM installed but I'm a bit unsure about what caches and stuff I should wipe. Do I need to do both wipe data/factory reset AND/OR wipe cache partition in the touch CWM recovery before flashing the new kernel?
Click to expand...
Click to collapse
I ALWAYS do a full wipe, dalvik cache the lot when flashing a different ROM, if you're just flashing a new kernel no need for wipe data just dalvik cache
Thanks for the reply. I found some posts last night where peeps were not wiping anything so I just flashed the 16b test kernel. Seems to be all OK so far.
I have the same issue...no recovery. Ive downloaded the gnufabio recovery file from the link, however i was expecting an .apk file that could be installed from the tablet OS desktop maybe usinf File Mgr. What the link downloads is a .zip w/ some folders and asstd files. Everyone is referring to it as an apk...Im confused.
fwbflash said:
I have the same issue...no recovery. Ive downloaded the gnufabio recovery file from the link, however i was expecting an .apk file that could be installed from the tablet OS desktop maybe usinf File Mgr. What the link downloads is a .zip w/ some folders and asstd files. Everyone is referring to it as an apk...Im confused.
Click to expand...
Click to collapse
It should be an apk. Did you use the link in his thread?
I have links to the apk in post 218 also including a modified version that will flash Team Rouge recovery.
http://forum.xda-developers.com/showpost.php?p=22359727&postcount=218
Thank you very much for those links...yes, those were apks. I have been looking for those links for sometime.
flashed the RecoveryInstaller.apk, giving me a recovery system to work from, now Im restored, rooted, ROMd and OC'd...thanks for the links!!
Since rooting mine, flashing the 16b kernel and OCing to 1600mhz it's been completely stable and fast. I just hope that continues!
Thanks everyone for your kindly assistance.