I have been looking around for about an hour or two trying to find a solid tutorial on how to install a custom recovery to install new Roms. I flashed my phone onto Virgin Mobile on FH13. It seems to me that there is more than meets the eye to installing a recovery on this phone. I really don't want to mess anything up at all. Could anyone guide me the right way as to how I can get CWM on my phone? I appreciate any help you can give me. Thanks!
Recovery is packed into the kernel on this phone. Flash a kernel tar through ODIN if you want, it will trigger the yellow triangle though. If your already rooted you could use Mobile ODIN. If you already have some form of custom recovery and are just trying to switch up you can flash the kernel zip in recovery.
rwilco has pretty much every kernel for every purpose but since your on stock you will either want a repacked stock or custom tw kernel - http://rwilco12.androidfilehost.com/?dir=Kernels/Recovery Kernels/ICS
If your unfamiliar then keep asking questions. Our phone has a bug in its eMMC firmware triggered during format operations on the stock kernel as of Android 4.0. The specifics are detailed but all you really need to know is grab a kernel with a safe recovery, or even going as far as AGAT's custom kernel which has more work around in place to prevent a factory reset or rom install from turning your phone into a super brick.
RainMotorsports said:
Recovery is packed into the kernel on this phone. Flash a kernel tar through ODIN if you want, it will trigger the yellow triangle though. If your already rooted you could use Mobile ODIN. If you already have some form of custom recovery and are just trying to switch up you can flash the kernel zip in recovery.
rwilco has pretty much every kernel for every purpose but since your on stock you will either want a repacked stock or custom tw kernel - http://rwilco12.androidfilehost.com/?dir=Kernels/Recovery Kernels/ICS
If your unfamiliar then keep asking questions. Our phone has a bug in its eMMC firmware triggered during format operations on the stock kernel as of Android 4.0. The specifics are detailed but all you really need to know is grab a kernel with a safe recovery, or even going as far as AGAT's custom kernel which has more work around in place to prevent a factory reset or rom install from turning your phone into a super brick.
Click to expand...
Click to collapse
Also new to the e4gt, im currently rooted on fh13.
say i want to flash paranoidandroid, which kernel (which includes recovery?) would you recommend?
also this is either flashed from odin (pc) or can be done through mobile odin?
then once kernel is flashed, i can then reboot into recovery, wipe and flash rom/gapps?
sorry for all the questions, just want to make sure!
bongzilla said:
Also new to the e4gt, im currently rooted on fh13.
say i want to flash paranoidandroid, which kernel (which includes recovery?) would you recommend?
also this is either flashed from odin (pc) or can be done through mobile odin?
then once kernel is flashed, i can then reboot into recovery, wipe and flash rom/gapps?
sorry for all the questions, just want to make sure!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1953783
RainMotorsports said:
Recovery is packed into the kernel on this phone. Flash a kernel tar through ODIN if you want, it will trigger the yellow triangle though. If your already rooted you could use Mobile ODIN. If you already have some form of custom recovery and are just trying to switch up you can flash the kernel zip in recovery.
rwilco has pretty much every kernel for every purpose but since your on stock you will either want a repacked stock or custom tw kernel - http://rwilco12.androidfilehost.com/?dir=Kernels/Recovery Kernels/ICS
If your unfamiliar then keep asking questions. Our phone has a bug in its eMMC firmware triggered during format operations on the stock kernel as of Android 4.0. The specifics are detailed but all you really need to know is grab a kernel with a safe recovery, or even going as far as AGAT's custom kernel which has more work around in place to prevent a factory reset or rom install from turning your phone into a super brick.
Click to expand...
Click to collapse
My phone already has root. Everything else is stock. 4.0.4, build FH13, with no custom recoveries.
I don't understand what you mean in your second paragraph with "repacked stock" or "custom tw kernel".
I am completely lost as to where I should be going. My plan is to install this rom: http://goo.im/devs/Shabbypenguin/E4GT-Nightlies
How would I go around to getting this on my phone?
Also, what about this rom: http://forum.xda-developers.com/showthread.php?t=1810315
I am not sure which rom runs the fastest and most efficient. There are so many kernels for so many things, I have absolutely no idea which kernel to flash and how to flash it.
EDIT: So I have done some more reading up and I THINK I can starting to understand some of it. I assume the steps are to:
1. Install Mobile Odin Lite on my phone.
2. Flash the EL26 kernel on Odin Lite. Link to kernel: http://forum.xda-developers.com/showthread.php?t=1662295 (first kernel on the page)
3. This part I am kinda lost. Not sure if that kernel installed a new recovery or not. I assume I just reboot and go into recovery.
4. Nandroid a backup of my ICS stock that is on now? Can I even go back to this stock backup after putting on a new Rom? Which kernel would I need to install backup of stock?
5. Wipe data, dalvic, and install new Rom using instruction it came with. My problem is I want to run this Rom: http://goo.im/devs/Shabbypenguin/E4GT-Nightlies and it has no instructions. I assume you just wipe data and dalvic?
6. flash Rom, then flash Gapp? It doesn't have a link for any of the Gapps, so either I have to find a link to download Gapp or that rom already comes with it? Not sure.
7. Reboot into new Rom? Not sure if I missed a step or not.
Another question I have is with the kernels. Can I just leave it on the EL26 kernel for daily use of the phone? Say I want to install maybe cm10 next, do I just keep it on EL26?
Sorry for the spam of questions. I like to be 100% certain.
Best bet if your trying to install CM9 is to go to the EL26 CWM kernel as all of the AOSP rom instructions dictate. Using the EL26 kernel means your phone will only boot to Download and Recovery as it will only boot gingerbread roms.
Download the nightly you want to the device and then flash the EL26 CWM kernel in Mobile ODIN. After its all over with you might need to battery pull if you messed up booting into recovery and then boot into recovery (power + vol up). Install the rom. Install gapps. Wipe cache/dalvik but as I will recommend below you should just backup everything and a full wipe.
You can nandroid if you want but it will be making a copy of the ICS rom you have with the EL26 kernel on it so it is literally a restore to the point your starting from not where you were just before that. Its still a good idea if your afraid of losing things. I would use Super Backup from the market to backup your Contacts, Call Logs and MMS. Wipe cache and dalvik and all that. But realisticly you should backup your apps and data if you have Titanium Backup and start fresh just factory reset after your on CM9. Restore your apps with data (no system data) after that. A clean install will present the least of issues, even the Samsung updates from one rom to another are not without issues.
You can not boot anything but gingerbread with EL26 and once you install a rom you will be on the kernel with that rom. So you will have a Linux 3 android kernel with cwm 6 if you go with a CM9 nightly. From there you can flash the next nightly or the next beta etc. Older stuff will not flash from your new setup as AOSP roms have switched to a new device name in the build.prop.
As far as gapps here it is - http://goo.im/gapps/gapps-ics-20120429-signed.zip and don't forget to put this on the device ahead of time or you will have to mount usb and transfer using the pc in recovery.
RainMotorsports said:
Best bet if your trying to install CM9 is to go to the EL26 CWM kernel as all of the AOSP rom instructions dictate. Using the EL26 kernel means your phone will only boot to Download and Recovery as it will only boot gingerbread roms.
Download the nightly you want to the device and then flash the EL26 CWM kernel in Mobile ODIN. After its all over with you might need to battery pull if you messed up booting into recovery and then boot into recovery (power + vol up). Install the rom. Install gapps. Wipe cache/dalvik but as I will recommend below you should just backup everything and a full wipe.
You can nandroid if you want but it will be making a copy of the ICS rom you have with the EL26 kernel on it so it is literally a restore to the point your starting from not where you were just before that. Its still a good idea if your afraid of losing things. I would use Super Backup from the market to backup your Contacts, Call Logs and MMS. Wipe cache and dalvik and all that. But realisticly you should backup your apps and data if you have Titanium Backup and start fresh just factory reset after your on CM9. Restore your apps with data (no system data) after that. A clean install will present the least of issues, even the Samsung updates from one rom to another are not without issues.
You can not boot anything but gingerbread with EL26 and once you install a rom you will be on the kernel with that rom. So you will have a Linux 3 android kernel with cwm 6 if you go with a CM9 nightly. From there you can flash the next nightly or the next beta etc. Older stuff will not flash from your new setup as AOSP roms have switched to a new device name in the build.prop.
As far as gapps here it is - http://goo.im/gapps/gapps-ics-20120429-signed.zip and don't forget to put this on the device ahead of time or you will have to mount usb and transfer using the pc in recovery.
Click to expand...
Click to collapse
Ah, I read it twice and now it makes more sense. I have a pretty good idea of what to do now.
Put rom and gapp on phone, install EL26, backup, full wipe, flash rom and gapp, rom will install new kernel for me, then just reboot.
Last question, I just want to make sure. What exactly is a full wipe on this phone. I have done plenty of full wipes on the evo 4g. I am just asking because I hear some people have problems when they do a full wipe.
I really appreciate your help. Thank you!
Sorry if I jumbled everything together in my post by the I was running out the door. But this Hurricanne has stopped that and I regret not taking my time.
Well what I mean is a factory reset which formats /Cache and /Data. When you install the rom its going to format /System prior to writing the new firmware/rom. /Data has all your user apps, their data and your information etc. This does not wipe the Internal SD or the External SD though at times a line saying it was does come up in CWM.
Just don't do a Factory reset on the stock kernel you are on now, its fine on EL26 its fine on the kernels that come with the CM9 nightlies. Super Backup apparently does app's now too. I have never used it since I have Titanium Backup Pro but figured its also worth mentioning.
A note on turning back. As I said before if you flash the EL26 CWM kernel you wont be able to boot the ICS rom installed on the phone. At that point to go back instead of forward you can flash the FH13 kernel in desktop ODIN or the zip in CWM and you will have the FH13 kernel instead of EL26 and be back where you were. But once you flash the EL26 CWM kernel your goal at that point is flashing your rom of choice in CWM and not things like booting the phone.
You should be "okay" coming from a dirty install just wiping cache. But you may never know if a problem your having is the rom or some left over data unless you go clean and factory reset. Its a choice and its also a choice you can make later as you can always reset later. I would back up anything important first before doing any of this. Not so much a worry about bricking, as just about any normal situation will be recoverable, but more so to the point of if you have to wipe the phone and start from scratch.
RainMotorsports said:
Sorry if I jumbled everything together in my post by the I was running out the door. But this Hurricanne has stopped that and I regret not taking my time.
Well what I mean is a factory reset which formats /Cache and /Data. When you install the rom its going to format /System prior to writing the new firmware/rom. /Data has all your user apps, their data and your information etc. This does not wipe the Internal SD or the External SD though at times a line saying it was does come up in CWM.
Just don't do a Factory reset on the stock kernel you are on now, its fine on EL26 its fine on the kernels that come with the CM9 nightlies. Super Backup apparently does app's now too. I have never used it since I have Titanium Backup Pro but figured its also worth mentioning.
A note on turning back. As I said before if you flash the EL26 CWM kernel you wont be able to boot the ICS rom installed on the phone. At that point to go back instead of forward you can flash the FH13 kernel in desktop ODIN or the zip in CWM and you will have the FH13 kernel instead of EL26 and be back where you were. But once you flash the EL26 CWM kernel your goal at that point is flashing your rom of choice in CWM and not things like booting the phone.
You should be "okay" coming from a dirty install just wiping cache. But you may never know if a problem your having is the rom or some left over data unless you go clean and factory reset. Its a choice and its also a choice you can make later as you can always reset later. I would back up anything important first before doing any of this. Not so much a worry about bricking, as just about any normal situation will be recoverable, but more so to the point of if you have to wipe the phone and start from scratch.
Click to expand...
Click to collapse
That clarified a lot, thanks.
So I did it all. I did a factory reset from the new kernel. did dalvic also. I installed the new rom and gapp. Problem is that once I reboot, it shows the Galaxy SII screen, then goes into a black screen. I can't turn it back on again, so I remove the battery and it can restart. Does the same thing though. I followed your instruction and http://e4gtcm.blogspot.com/p/cm9-install-guide.html
What did I do wrong? I am worried I messed up my phone completely.
EDIT: So I went back into recovery and it was now a new version of CWM. I did everything over again; factory reset, cache, dalvic, and it is doing the same thing. Boots up "Galaxy SII" screen, then a black screen. It seems to still be on in the black screen seeing that it doesn't "turn" on again. I can hold if for 15 second or so for it to reset and does the same thing. Why is there a black screen?
Sorry for not checking back. Your probably freaking right now lol but relax your at a good point everything is fine.
Either a bad download or the nightly you went with happens to be a baddy. I am still on 10/20 I was gonna flash 10/28 today but the weather is screwing with me. goo.im seems pretty slow today.
Download another, battery pull and hold vol up + power until it hits recovery then go into mounts and mount usb storage hook a usb cable to the pc and copy over another build. I would say try 10/20 just because it works pretty good but that won't stop another bad download in which case you have to try try again.
Worst case from here we can just odin you back to stock rooted FH13 or your choice of other. Your phone is fine from what you have told me so far. I can upload one of the builds I have if you think ti would help any.
RainMotorsports said:
Sorry for not checking back. Your probably freaking right now lol but relax your at a good point everything is fine.
Either a bad download or the nightly you went with happens to be a baddy. I am still on 10/20 I was gonna flash 10/28 today but the weather is screwing with me.
Download another, battery pull and hold vol up + power until it hits recovery then go into mounts and mount usb storage hook a usb cable to the pc and copy over another build. I would say try 10/20 just because it works pretty good but that won't stop another bad download in which case you have to try try again.
Worst case from here we can just odin you back to stock rooted FH13 or your choice of other. Your phone is fine from what you have told me so far.
Click to expand...
Click to collapse
Phew! I was pretty positive that I could still get back to something working, just my paranoid self was getting tense. I got 10/28. I guess I will do 10/20. Do you know what the other updates have? I would hate to install something that isn't working its most efficient.
Again, thank you so much. You were of great help! Good luck with the weather issue. Hope you're safe!
I stopped following chris's experimentals so i am not sure what the most recent focuses have been. The Nightlies have whatever code was commited. They are built automatically and can range from very stable to not booting at all. I dont have any of the links on me but someone can get it to you. Reading commits is not exactly 100% user friendly especially if your not a developer. But they often have clues. I would follow the CM9 Beta thread and the CM9 User Support Threads - http://forum.xda-developers.com/showthread.php?t=1874374 and http://forum.xda-developers.com/showthread.php?t=1720771
I used to DL nightlies from work over 3g or 4g all the time and would get a bad dl and end up in situations where even my experienced self felt like I couldn't fix it till I got home and always got the phone running within an hour without the assistance of a near by pc.
I am uploading 10/20 to my server just in case its in Chicago so if your away from the weather it should be unaffected for the most part. Glad its not in NY anymore.
EDIT - http://android.rainmotorsports.net/10-20-CM9-d710-KANG.zip the md5 hash as I have it is 66246125ACDBEF2EBF2144E0CBFEBB7B and it matches the md5 listed on goo.im
RainMotorsports said:
I stopped following chris's experimentals so i am not sure what the most recent focuses have been. The Nightlies have whatever code was commited. They are built automatically and can range from very stable to not booting at all. I dont have any of the links on me but someone can get it to you. Reading commits is not exactly 100% user friendly especially if your not a developer. But they often have clues. I would follow the CM9 Beta thread and the CM9 User Support Threads - http://forum.xda-developers.com/showthread.php?t=1874374 and http://forum.xda-developers.com/showthread.php?t=1720771
I used to DL nightlies from work over 3g or 4g all the time and would get a bad dl and end up in situations where even my experienced self felt like I couldn't fix it till I got home and always got the phone running within an hour without the assistance of a near by pc.
I am uploading 10/20 to my server just in case its in Chicago so if your away from the weather it should be unaffected for the most part. Glad its not in NY anymore.
EDIT - http://android.rainmotorsports.net/10-20-CM9-d710-KANG.zip the md5 hash as I have it is 66246125ACDBEF2EBF2144E0CBFEBB7B and it matches the md5 listed on goo.im
Click to expand...
Click to collapse
I just got it downloaded. It is now up and running perfectly. I appreciate all your help man, thanks a bunch. I live in Washington state. So the weather wont affect me.
Good evening all. I hope this is the right forum to post my question about recovery for my e4g touch. I recently rooted my phone and my phone is currently on the fi27 build. Is there a recovery i can put on there now to go ahead and start flashing ruins, or will i have to wait for qbkng77 to post his video on you tube on putting cwm recovery on fi27 rooted e4g touch? Thanks in advance for the help!
Sent from my SPH-D710 using xda app-developers app
n1stunna84 said:
Good evening all. I hope this is the right forum to post my question about recovery for my e4g touch. I recently rooted my phone and my phone is currently on the fi27 build. Is there a recovery i can put on there now to go ahead and start flashing ruins, or will i have to wait for qbkng77 to post his video on you tube on putting cwm recovery on fi27 rooted e4g touch? Thanks in advance for the help!
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I assume you do the same thing as I did. Get the EL26 kernel and flash it with Mobile Odin. I would wait on someone else to confirm that though.
Another really quick question. I want to overclock my phone. I tried using setcpu and the overclocker it came with. It only goes to a max of 1200 but I know it can go higher. I am guessing I need another kernel. What kernel can I use?
joshlete said:
Another really quick question. I want to overclock my phone. I tried using setcpu and the overclocker it came with. It only goes to a max of 1200 but I know it can go higher. I am guessing I need another kernel. What kernel can I use?
Click to expand...
Click to collapse
You either need a kernel with built in over clock support(you'd see the CPU slider go up to 1400-1600 automatically if it was). Or a kernel that supports over locking in tegrak, which you "load over clock module" with in tegrak.
Both Kuban kernel and some of Agats kernels have built in support, mine you need to use tegrak as I have not added built in yet
You can get them all in rwilco's (awesome) kernel repository stickied in development
Sent from my SPH-D710 using xda premium
Related
So I'm getting tired of waiting for Sprint to roll out the damn ICS OTA...and even when they do, the Touchwiz leaks I've seen don't look terribly interesting. So I'm considering going to CM9 Alpha 2, having already experienced it on my HP Touchpad and loved it.
My original thought process was: backup all apps and settings, use QBking's guide to install CWM, do an additional nandroid backup and move that onto my PC, and install CM9 A2.
My problem is that I'm currently on completely stock Gingerbread EL29. No root. So I can't use Titanium Backup in case I have to go back to GB. I guess theoretically then I could go: Stock -> Stock Root -> Titanium Backup -> CM9A2...but I'm aware that you install CWM as part of the CM9 installation, so trying to shove TB into the mix might be redundant.
My questions are the following:
1. Is a nandroid backup sufficient for this kind of move, or should I be looking to fit Titanium into the mix as well? My understanding is that Titanium would be more or less required to actually get those apps to cross the GB-ICS threshold, short of downloading them all again. But it seems like more work.
2. QBking has videos on how to go from stock GB to CM9A2. But what do I do if I want to go back to EL29 GB, on the offchance I decide to go for Sprint's OTA?
3. Assuming I do go back, can the nandroid backup I made before installing CM9 be used to restore my stock GB settings (after I reinstall the EL29 kernel), or will that brick my phone?
Thanks in advance.
Aganar said:
So I'm getting tired of waiting for Sprint to roll out the damn ICS OTA...and even when they do, the Touchwiz leaks I've seen don't look terribly interesting. So I'm considering going to CM9 Alpha 2, having already experienced it on my HP Touchpad and loved it.
My original thought process was: backup all apps and settings, use QBking's guide to install CWM, do an additional nandroid backup and move that onto my PC, and install CM9 A2.
My problem is that I'm currently on completely stock Gingerbread EL29. No root. So I can't use Titanium Backup in case I have to go back to GB. I guess theoretically then I could go: Stock -> Stock Root -> Titanium Backup -> CM9A2...but I'm aware that you install CWM as part of the CM9 installation, so trying to shove TB into the mix might be redundant.
My questions are the following:
1. Is a nandroid backup sufficient for this kind of move, or should I be looking to fit Titanium into the mix as well? My understanding is that Titanium would be more or less required to actually get those apps to cross the GB-ICS threshold, short of downloading them all again. But it seems like more work.
2. QBking has videos on how to go from stock GB to CM9A2. But what do I do if I want to go back to EL29 GB, on the offchance I decide to go for Sprint's OTA?
3. Assuming I do go back, can the nandroid backup I made before installing CM9 be used to restore my stock GB settings (after I reinstall the EL29 kernel), or will that brick my phone?
Thanks in advance.
Click to expand...
Click to collapse
Hello! Welcome to the AOSP club.
1. Restoring data is usually a no-no for these ROMs because they might cause force closes and slow downs etc. Ultimately, your mileage will vary, but I wouldn't try because
AOSP roms automatically install all the apps you have installed from the market! It's an awesome feature. If some apps aren't automatically installed, then you can find them in data/app or system/app of your nandroid and push it through root explorer or manually install them
2. I would head over the dev section and look for sfhub's oneclick el 29 root. Whenever I want to flash an ICS rom and I'm on ICS, I first use sfhub's oneclick to go back to stock rooted gingerbread, then I go about and install stock el26 cwm and flash etc etc. I don't know if stock root can accept OTA, but I'm sure you'll find a way to back to stock stock in that thread, or in the sticky of dev section that says Auto Root package.
3. It will brick your phone. As a general rule of thumb, don't do anything in the recoveries provided by ICS Roms, as over the past month the E4GT community have seen a high rise in bricks due to them. It will hopefully be resolved once samsung released ICS Source for epic 4g touch, and we can get a real kernel to mess with.
Good luck and have fun! Remember, once you go AOSP, you can never go back.
Why cm9 rather than a leaked version of ics? Im not trying to be an ass or concince you otherwise just curious. From my viewpoint the leaks are stable and some are in odin so its baaically a 1 click install after rooted? Everything about an alpha version makes me nervous and cm9 doesnt seem ready to me so i wonder if im missing something.
Sent from my SPH-D710 using Tapatalk
cm9
someguyatx said:
Why cm9 rather than a leaked version of ics? Im not trying to be an ass or concince you otherwise just curious. From my viewpoint the leaks are stable and some are in odin so its baaically a 1 click install after rooted? Everything about an alpha version makes me nervous and cm9 doesnt seem ready to me so i wonder if im missing something.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
u must not have used a2 because there is less wrong with it than any tw leak there has been ....
just because its a alpha doesnt mean anything its a daily for alot of people almost everything works ....even stuff you will never get on tw like naitive tether and blue tooth controllers like ps3 wii etc
Well I went ahead and did it. No issues to report just yet.
A few post-CM9 install questions though:
1. How do I set speed dials on my phone contacts? I've been searching around and can't quite find it.
2. After ODIN'ing the phone but before installing CM9, I was able to boot to CWM recovery by turning the phone off then holding vol-up + power. But now when I do that it boots into Android recovery. How do I boot to CWM recovery again?
Aganar said:
2. After ODIN'ing the phone but before installing CM9, I was able to boot to CWM recovery by turning the phone off then holding vol-up + power. But now when I do that it boots into Android recovery. How do I boot to CWM recovery again?
Click to expand...
Click to collapse
This is my first Samsung. I have been on HTC until now. I have been wondering the same thing about recovery. I also tried to reinstall CWM from the included Rom Manager it just freezes. Also, I had a problem this morning where I had to use ODIN to put CWM back on and I wiped cache and dalvik and then it would no longer boot. I tried to restore my back up and the same thing. Just froze at boot screen. I had to start over. Luckily I had a pretty current Titanium backup to quickly put my programs back on it.
So, I have the same question as you about CWM and also wiping cache/delvik and restoring the backup.
caseyatbt said:
This is my first Samsung. I have been on HTC until now. I have been wondering the same thing about recovery. I also tried to reinstall CWM from the included Rom Manager it just freezes. Also, I had a problem this morning where I had to use ODIN to put CWM back on and I wiped cache and dalvik and then it would no longer boot. I tried to restore my back up and the same thing. Just froze at boot screen. I had to start over. Luckily I had a pretty current Titanium backup to quickly put my programs back on it.
So, I have the same question as you about CWM and also wiping cache/delvik and restoring the backup.
Click to expand...
Click to collapse
Never touch rom manager for this phone as of now it is not compatible and could brick you. To answer both of your questions about recovery, I do not recommend flashing a different kernel with CM9 the dev did this for your own safety to prevent bricks, and they're really is no need for it on CM9 until you need to update it. Play safe and save your phone, try to save time and you'll brick it
O...k...
That poses problems for my next question. Namely, my signal seems to have taken a nose-dive since installing ICS. I don't know if the signal has actually degraded, since I'm no longer on a Touchwiz-based ROM, or if it only seems like it's degraded, because perhaps the ICS signal detector is more accurate than the GB one and my signal indicator was incorrect before. But I just had a few calls earlier today and there was more static than I'm used to.
So, how do I go about getting another PRL? The workaround I saw for that involved "flashing" a version of the stock kernel onto the SD card long enough to get another one. But if I can't get into CWM...
Can any one answer why I can't restore a CWM backup or even reboot after performing cache or dalvik wipe? I really like this phone, but it sure seems like rooting/recovery/roms work the same as it did on my HTC phone.
Aganar said:
So, how do I go about getting another PRL? The workaround I saw for that involved "flashing" a version of the stock kernel onto the SD card long enough to get another one. But if I can't get into CWM...
Click to expand...
Click to collapse
caseyatbt said:
Can any one answer why I can't restore a CWM backup or even reboot after performing cache or dalvik wipe? I really like this phone, but it sure seems like rooting/recovery/roms work the same as it did on my HTC phone.
Click to expand...
Click to collapse
Here's a link to an FC22 CWM Recovery. ODIN this guy into your phone - http://forum.xda-developers.com/showthread.php?t=1563547&highlight=fc22
@Aganar - The way I've been getting the whole PRL / Profile thing is ---- Get all setup in CM9 the way you like it, fast backup everything via your preferred user land method (titanium, smsbackup, call log backup, etc). Roll back to a Stock GB ROM (calkulin EL29). Update PRL / Profile. Immediately upgrade to ICS but dont wipe the cache. Restore apps & logs from backups. Havent had a single issue...
takes about 10 min round trip.
I guess my concern is, if the flash from GB to ICS is what caused the signal degradation in the first place, why would flashing back to GB in order to update the PRL have any benefit, if I have to flash back to ICS again?
You won't lose the PRL update after you reflash.
---------- Post added at 08:35 PM ---------- Previous post was at 08:35 PM ----------
CyberMacGyver said:
Here's a link to an FC22 CWM Recovery. ODIN this guy into your phone - http://forum.xda-developers.com/showthread.php?t=1563547&highlight=fc22
Click to expand...
Click to collapse
Are you sure? There are all sorts of warnings about that recovery and ICS.
I just upgraded my E4GT Sprint from GB to ICS using the oneclick installer. I am trying to install the CODENAME rom from CWM but havng issues getting CWM installed. I used the the E4GT auto but FE16 isnt listed so i tried FE15 but it wont load into CWM. So i tried this link "http://forum.xda-developers.com/showthread.php?t=1390393" and flashed from ODIN and it goes into CWM but before it boots it says my phone is a gt-i9100 and has a ! on the bottom. It appears to boot though so i booted back into CWM and tried to flash the ZIP for CODENAME and the gapps file and it jsut gets stuck at the boot screen with the transformer logo. I cant get into CWM after that point and have to ODIN back to ICS. I am on ICS now and its working fine. Does anyone have any instructions on getting CWM installed and the codename rom from a fresh odin ICS install?
mazdaspeed6 said:
I just upgraded my E4GT Sprint from GB to ICS using the oneclick installer. I am trying to install the CODENAME rom from CWM but havng issues getting CWM installed. I used the the E4GT auto but FE16 isnt listed so i tried FE15 but it wont load into CWM. So i tried this link "http://forum.xda-developers.com/showthread.php?t=1390393" and flashed from ODIN and it goes into CWM but before it boots it says my phone is a gt-i9100 and has a ! on the bottom. It appears to boot though so i booted back into CWM and tried to flash the ZIP for CODENAME and the gapps file and it jsut gets stuck at the boot screen with the transformer logo. I cant get into CWM after that point and have to ODIN back to ICS. I am on ICS now and its working fine. Does anyone have any instructions on getting CWM installed and the codename rom from a fresh odin ICS install?
Click to expand...
Click to collapse
You really should read more before hopping around like that without checking. Real risk for a brick here.
-Flash EL26 stock CWM kernel via the PDA option in ODIN/Mobile ODIN
-When phone begins reboot, Hold Power + Volume up until boots into recovery.
-Wipe data/factory, cache and dalvik cache
-Flash ROM
-Flash Gapps
-Reboot
Those are the instructions right from the developer's thread. This is an AOSP rom and it sounds like you're trying to install TW kernels.
http://forum.xda-developers.com/showthread.php?t=1662295
This is the kernel repository. It links to each kernel where you can read further and find out if they are safe for flashing things.
Seems like you've done a bunch of stuff. But you really should do a whole bunch of reading first or you will brick your phone.
My suggestion would be to use sfhub's one-click http://forum.xda-developers.com/showthread.php?t=1705730 to get to a fully stock rooted device. Then use his autoroot package http://forum.xda-developers.com/showthread.php?t=1342728 to add CWM (the lates in the package is FF11+CWM Agat I believe) then you can add Agat's latest kernel with CWM http://forum.xda-developers.com/showthread.php?t=1721065
But I would be very careful when flashing ANY ROM; use the developers prefered method. Some recommend using EL26 CWM. Some a different recovery or procedure. Be especially careful with CM9 and AOKP builds to follow the directions there.
Good luck
So while i was waiting for a response i just went back to the stock GB using the one click install. I then used the autoroot package to install CWM and then restored my nandroid backup before i made in the very beginning. So my phone is back to a perfect state with GB and CWM installed. Can i just flash the ROM from CWM as is then? For some reason i thought it had to be "converted" to ICS and thats what started this whole mess. Things have changed since my old Evo
I just noticed that im running EL29 not 26...does that matter? When i try to flash that CMW EL26 stock root is when it gave me that gt-i9100 on boot and the ! at the bottom. Using the autoroot and choosing the EL29 Rogue is the only way i got it installed.
mazdaspeed6 said:
So while i was waiting for a response i just went back to the stock GB using the one click install. I then used the autoroot package to install CWM and then restored my nandroid backup before i made in the very beginning. So my phone is back to a perfect state with GB and CWM installed. Can i just flash the ROM from CWM as is then? For some reason i thought it had to be "converted" to ICS and thats what started this whole mess. Things have changed since my old Evo
I just noticed that im running EL29 not 26...does that matter? When i try to flash that CMW EL26 stock root is when it gave me that gt-i9100 on boot and the ! at the bottom. Using the autoroot and choosing the EL29 Rogue is the only way i got it installed.
Click to expand...
Click to collapse
My friend some good suggestions above your post. Give yourself a day or two and do some reading prior to flashing. This way you may not end up at Sprint making up stories about why your phone wont boot up.
Let me just echo what everybody else has said, you're gotta read more. A lot more! If you're one goal is to get CNA in your phone I would recommend reading all of the very first post on that thread. They give step by step instructions.
If you need CWM there are several options to get it on your phone. Both sfhub and I have put together several one-click and automated options to get it on your phone.
One thing that hasn't been suggested yet but I would strongly encourage you to do is to read the "How Not To Brick Your E4GT" thread. It's sticked in the General section.
Good luck!
Two more things.
1) If you're going to ask for help give it a few minutes before trying something new. It takes people a minute to reply. Sometimes waiting that extra minute or two is all you need to be saved from bricking.
2) Don't be afraid to hit your thanks button for everyone who has offered advice already. I got them once for you but it might not hurt to do it again.
Back around may i flashed my gf's gs2 to ics akop and it was an ordeal with odin and recovery and whatnot. At the time my friend had one too and helped walk me through it, but hes moved onto the gs3. Im used to htcs where i just need to flash a recovery and rom and im good to go, and i see some talk of safe recovery so it looks like things have gotten better. Shes having all kinds of problems with this akop build and id like to get her on something new, hopefully something cm10 based, but have no idea what all that entails. It looks like her kernel is fe07, if someone could let me know what i need to do to get her on a better rom id greatly appreciate it
Us in mobile Odin or desktop Odin to flash a kernel. I would highly recommend el26+cwm5 its a kernel with recovery built in because that's how our phone does the recovery. After you have el26 kernel installed it won't boot. Its OK. This just means you have an ics rom trying to use a gb kernel. Just push and hold both the power button and volume up until you get in recovery. This is the safest kernel to flash from. Then once in recovery go ahead and flash your cm10.
Things you will need.
1. el26kernel with cwm5.
2. Rom you want to flash.
3. Either mobile Odin by chain fire or desktop Odin with drivers already installed.
4. Calkulins format all.zip is highly recommended to use so you don't have traces of hour last rom messing things up.
sent from my BAD A$$ Epic touch
Thanks for the detail. So with having a gb kernel whats going to allow it to boot once i install cm10? Once cm is installed, do i have to go through that whole process again to flash another rom if i want?
kellybrf said:
Thanks for the detail. So with having a gb kernel whats going to allow it to boot once i install cm10? Once cm is installed, do i have to go through that whole process again to flash another rom if i want?
Click to expand...
Click to collapse
Cm10 should have a safe recovery, but you can if you want to be doubly sure. When you install cm it will have the jb kernel with it so all you have to do is rom gapps and boot. Highly recommend mobile Odin for going to el26 recovery because it makes it soo much faster and easier.
When you flash a rom from that el26 kernel, it will be overwritten. The kernel is packed into the rom. So by flashing cm10 you will now have a new kernel.
sent from my BAD A$$ Epic touch
Ok, so I've been flashing Roms since I first had the G1 but my step sons Galaxy S II is giving me fits as of late.
I've been working on it for over 2 days now and can not figure the problem even after reading through all the how to's and individual rom threads. I initialy rooted his phone back in April/May and had a early ICS phandroid rom on it. However I wanted to move him to JB. I've done the customary wipe data/cache but no matter what JB rom I flash it goes into what I believe is a bootloop. I've read several places it been said to let sit after flashing for 10 minutes so I let sit for 20 and it was still on boot (but no obvious point where you can tell it's looping).
When I went to restore his backup that would no longer boot at all, just a blank screen. So long story short I restored everything to stock then updated to ICS through keis. and tried the process again thinking it might need updated firmware/radio. Same thing happened and I had to restore stock and update through keis again. I am now at a complete loss as I update my phone (One S) and wifes (GSIII) atleast once a week on nightlies.
The one thing that I thought was odd is both on the original 2.3.6 and now 4.0.4 when I go into settings at search for update i get a message saying "no firmware". Not sure if that means anything but it didn't sound right to me.
Any help or suggestions would be overwhelmingly appreciated.
You will get different methods on here but for starters what recovery are you running. Thats problem 1 I guarantee for your bootloop. I use TWRP 2.3 which can be found by downloading goo.im and flashing it from the menu screen. You can also go to the forum here in development for the zip file.
When using TWRP or any touch recovery do not use the wipe scripts. Lets start there.... Since the method to flashing is basically the same all over its just the wiping procedure with the wrong recovery can be tricky
I'm using CWM 6.0.3 I believe he's at school so I don't have the phone to know the exact CWM version. It's also not the touch version. How should I go about wiping data/cache for his phone then? I've never used TWRP but going to assume if you've used one recovery it's pretty similar or self explanatory.
jhenson496 said:
I'm using CWM 6.0.3 I believe he's at school so I don't have the phone to know the exact CWM version. It's also not the touch version. How should I go about wiping data/cache for his phone then? I've never used TWRP but going to assume if you've used one recovery it's pretty similar or self explanatory.
Click to expand...
Click to collapse
I personally prefer that recovery and I'm running a cm 10 on my phone with no issues at never had anything. Yes it's rather simple to put on an even if you want to try the CWM touch recovery by all means go ahead
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Ok, I'll give TWRP a try when he gets home. I guess my next question would be is there a different way of wiping then with other phones?
Do I need the recovery to be touch (never heard of a recovery needing touch version)
Anything different then wiping dalvik, cashe and data? Also I've look around and do not see an actual JB radio. So I'm assuming the ULVH1 radio would work for ICS & JB.
I appreciate your help with this btw.
jhenson496 said:
Ok, I'll give TWRP a try when he gets home. I guess my next question would be is there a different way of wiping then with other phones?
Do I need the recovery to be touch (never heard of a recovery needing touch version)
Anything different then wiping dalvik, cashe and data? Also I've look around and do not see an actual JB radio. So I'm assuming the ULVH1 radio would work for ICS & JB.
I appreciate your help with this btw.
Click to expand...
Click to collapse
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
Click to expand...
Click to collapse
There is a lil something from the TWRP thread about the new recovery... basically its built off a JB which improves the features being used like wipes, fix permissions, backups etc. Its not that its solely touch but it was the direction most if not all recoveries have gone to basically preserve that power button and vol keys of our phones. It kinda makes sense...
So with updated technology just came a better way to use a recovery and since the SGII originally had wiping issues TWRP on this phone is made solely for this phone which cut out alot of issues. Now if you prefer a non touch may I suggest 5.0.2.7 w/darkside cache wipes and you would be ok as well. Honestly though I dont think anyone would be upset with TWRP its quite nice
TWRP Link - http://forum.xda-developers.com/showthread.php?t=1768742
Darkside Wipes - http://forum.xda-developers.com/showthread.php?t=1477955 (Only use with CWM 5.0.2.7)
CWM Touch(Latest) - http://forum.xda-developers.com/showthread.php?t=1844637
I would switch to Clockwork Recovery 5.0.2.7 which you can find in ROMmanager app. Thus, you can use TDJ's Darkside super wipe and cache wipe scripts which install very clean.
Finding his scripts might be a bit of a challenge but they are out there. I have them but not sure how i can get them to you... my dropbox isnt working.
if you do find those scripts, then the flash is simple...
reboot into recovery
Flash TDJ's Darkside SUPERWIPE
Flash your ROM or Gapps depending on what that OP says goes first
Flash Darkside CACHE wipe
Reboot, let is settle 10 mins reboot
That works with 5.0.2.7 where you have to mash the side buttons.. Ive installed a few JB and ICS roms this way, worked well for me.
Hit thanks if i helped
abesgs2 said:
I would switch to Clockwork Recovery 5.0.2.7 which you can find in ROMmanager app. Thus, you can use TDJ's Darkside super wipe and cache wipe scripts which install very clean.
Finding his scripts might be a bit of a challenge but they are out there. I have them but not sure how i can get them to you... my dropbox isnt working.
if you do find those scripts, then the flash is simple...
reboot into recovery
Flash TDJ's Darkside SUPERWIPE
Flash your ROM or Gapps depending on what that OP says goes first
Flash Darkside CACHE wipe
Reboot, let is settle 10 mins reboot
That works with 5.0.2.7 where you have to mash the side buttons.. Ive installed a few JB and ICS roms this way, worked well for me.
Hit thanks if i helped
Click to expand...
Click to collapse
My friend I linked the zips in the post right above yours
playya said:
CHANGELOG for 2.3.0.0:
There is a lil something from the TWRP thread about the new recovery... basically its built off a JB which improves the features being used like wipes, fix permissions, backups etc. Its not that its solely touch but it was the direction most if not all recoveries have gone to basically preserve that power button and vol keys of our phones. It kinda makes sense...
So with updated technology just came a better way to use a recovery and since the SGII originally had wiping issues TWRP on this phone is made solely for this phone which cut out alot of issues. Now if you prefer a non touch may I suggest 5.0.2.7 w/darkside cache wipes and you would be ok as well. Honestly though I dont think anyone would be upset with TWRP its quite nice
TWRP Link - http://forum.xda-developers.com/showthread.php?t=1768742
Darkside Wipes - http://forum.xda-developers.com/showthread.php?t=1477955 (Only use with CWM 5.0.2.7)
CWM Touch(Latest) - http://forum.xda-developers.com/showthread.php?t=1844637
Click to expand...
Click to collapse
Just saw that last part by Playa, sorry didnt mean to kang you haha... but hes got it down ^^^
So, I have flashed CWM Recovery and CWM Touch Recovery onto my Epic 4G Touch. Rom Manager says both are installed. However, when I boot into recovery, I get the stock recovery. I've searched and searched and all I have found are people who aren't pushing the right buttons and others with junk answers that are no help at all, like instructions on how to flash the recovery.
Even if I reflash using Rom Manager or any other recovery installer, it boots to the stock recovery. It's as if any changes to the file system are being completely ignored.
The weird thing is, if I flash StockCWM-EL26 or rogue_ET-recovery-1.2.2-FB27-rc0 using Odin/Mobile Odin and get to whichever one I flashed once, then either the phone won't boot at all or subsequent reboots result in the stock recovery once again.
To reiterate, I have *no* problem booting the phone and I have *no* problem getting to recovery... it's the wrong recovery, but still.
Oh, and I'm using HyDrA ROM.
Wrong forum. Report your post & ask mods to move your thread here.
MistahBungle said:
Wrong forum. Report your post & ask mods to move your thread here.
Click to expand...
Click to collapse
That forum is for the Epic 4G. My phone is not the Epic 4G, it is the Epic 4G Touch.
Try here then (doesn't belong here regardless).
WARNING do not use rom manager. Use odin or mobile odin. You have a high risk of bricking using rom manager. Take a look at some how-to's in this section.
sent from MY BAD A$$ ET4G
patrao_n said:
WARNING do not use rom manager. Use odin or mobile odin. You have a high risk of bricking using rom manager. Take a look at some how-to's in this section.
sent from MY BAD A$$ ET4G
Click to expand...
Click to collapse
^^^^^ this been there done that
patrao_n said:
WARNING do not use rom manager. Use odin or mobile odin. You have a high risk of bricking using rom manager. Take a look at some how-to's in this section.
sent from MY BAD A$$ ET4G
Click to expand...
Click to collapse
As I said, it either works once and never again or never at all no matter what I use to flash it.
Venum's Hydra rom? Wow, talk about a flash back..
Anyway, have you tried the el26 kernel one click?
No, but I don't imagine it would be any different than the Odin flash.
At any rate, I have an addendum. Flashing Rogue 1.2.2, the one that works - I can't get 1.5.0 to work at all (no boot, no recovery, only download mode), doesn't magically disappear, but it doesn't mount my external SD card and I can't open System Settings/Storage - I just can't win.
Would you mind listing the steps of flashing and items being flashed?
Only reason a custom won't stick is that you're flashing something behind it. In my mind at least..
First Time
<Download Mode>
Flash EL26 CWM Recovery - Phone no longer boots to OS. Can only get to CWM Recovery or Download Mode.
<Recovery Mode>
Wipe.
Flash HyDrA twice as per instructions.
Flash GApps.
Flash Multi-DPI Play Market while I'm at it.
Reboot.
Setup ROM.
Attempt to get to Recovery - got stock recovery.
Decided to try again without wiping. Same results.
Decided to try something:
<Download Mode>
Flash EL26 CWM Recovery - Phone no longer boots to OS. Can only get to CWM Recovery or Download Mode.
<Recovery Mode>
Made a NAND backup of /system and /data.
Flash HyDrA twice as per instructions.
Flash CWM Touch Recovery - Recovery takes effect immediately.
Restore the NAND backups.
Reboot.
Attempt to get to Recovery - got stock recovery.
Another thing:
<Download Mode>
Flash Rogue recovery.
Reboot.
Attempt to get to Recovery - got Rogue recovery - So far so good.
Flash CWM Touch Recovery - Recovery takes effect immediately.
Reboot.
Attempt to get to Recovery - got Rogue recovery - Interesting, but I can only access the external SD card from Recovery.
Flashed back to EL26.
Reinstalled HyDrA.
Restored the NAND backups.
(The Touch Recovery version is 5.8.1.5).
ROM Manager
Attempt to flash either CWM Recovery or CWM Touch Recovery.
Reboot.
Attempt to get to Recovery - got stock recovery.
Here is a list of my apps if you want that, too.
https://www.dropbox.com/s/k67l6mb294ruyug/apps-list.txt
I'm hesitant on trying anything else because it's a pain to restore it if I can't boot to the OS.
Just went back to Venums thread.
:edit: Briefly reading the thread, you'll need to have and AOSP kernel to run the Rom, so no, EL26 will not work.
:2d edit: This is out of the second post in that thread. - *If you are restoring a nandroid that you backed up via the above process, you will need to wipe cache and dalvik, then flash an AOSP ICS kernel or the ROM wont boot because it is backed up with the EL26 kernel. Then reboot.
Hydra comes with FD26 kernel. As per the OP.
I don't know, and haven't tested, if Hydra will run with EL26 cwm. But you need to add that to the last step.
But that's why you're going back to stock. It's part of the package.
Please, please, please; STOP using Rom Manager to flash a recovery.
I see a AOSP/TWRP repack by Times Infinity in the Kernel Repo that you could try, But I have not read the Hydra thread to see if Venum had tested this prior to discontinuing support.
egingell said:
No, but I don't imagine it would be any different than the Odin flash.
At any rate, I have an addendum. Flashing Rogue 1.2.2, the one that works - I can't get 1.5.0 to work at all (no boot, no recovery, only download mode), doesn't magically disappear, but it doesn't mount my external SD card and I can't open System Settings/Storage - I just can't win.
Click to expand...
Click to collapse
The easiest thing to do is find the EL29 auto boot recovery... goes straight into recovery after you flash it thru Odin.. check RWilco's repository
bilgerryan said:
The easiest thing to do is find the EL29 auto boot recovery... goes straight into recovery after you flash it thru Odin.. check RWilco's repository
Click to expand...
Click to collapse
From what I'm gathering from his OP, he wants to have a custom after flashing Hydra.. Gonna have to be an AOSP repack to run with a custom. I didn't really gather that until he listed the flashing steps he's doing.
MoHoGalore said:
I see a AOSP/TWRP repack by Times Infinity in the Kernel Repo that you could try, But I have not read the Hydra thread to see if Venum had tested this prior to discontinuing support.
Click to expand...
Click to collapse
I downloaded one, I haven't tried it.
I take it back, I did try it, but it wouldn't install. FF18 Rev2, for the record.
MoHoGalore said:
bilgerryan said:
The easiest thing to do is find the EL29 auto boot recovery... goes straight into recovery after you flash it thru Odin.. check RWilco's repository
Click to expand...
Click to collapse
From what I'm gathering from his OP, he wants to have a custom after flashing Hydra.. Gonna have to be an AOSP repack to run with a custom. I didn't really gather that until he listed the flashing steps he's doing.
Click to expand...
Click to collapse
Right. And I would have no problem just reflashing EL26 /w CWM if it would actually boot into the OS.
egingell said:
I downloaded one, I haven't tried it.
Right. And I would have no problem just reflashing EL26 /w CWM if it would actually boot into the OS.
Click to expand...
Click to collapse
Yeah, anything that's not an AOSP kernel/recovery isn't gonna work. So, if Time's aosp repack doesn't work, you'll have to run the included kernel.
MoHoGalore said:
Yeah, anything that's not an AOSP kernel/recovery isn't gonna work. So, if Time's aosp repack doesn't work, you'll have to run the included kernel.
Click to expand...
Click to collapse
Odin wouldn't install it, if that makes a difference. It's not that the install failed and I had to start over, again.
Well, since my touch isn't my daily use phone at the moment, I'll test that setup tonight.
I decided to try the One-Click of the FF18 v2 kernel and it flashed successfully.
However, as with Rogue, I only have no external SD card and no access to Settings/Storage. TWRP is pretty, but if I can't use my SD card, I'd rather use the stock kernel.
egingell said:
I decided to try the One-Click of the FF18 v2 kernel and it flashed successfully.
However, as with Rogue, I only have no external SD card and no access to Settings/Storage. TWRP is pretty, but if I can't use my SD card, I'd rather use the stock kernel.
Click to expand...
Click to collapse
My apologies on not getting back with you on this last night.
But the SD issue is also seen on the repacks with JB. Depending on when and how FF18 v2 was built (without source at the time?) could be similar to the issues with current repacks.
I'd have to refer those issues/questions to Agat or Garwynn..