Related
hello all
i just upgraded to the Tmobile GS2 from my trusty old Nexus One. I must say I do miss my good ol' nexus but i am truly falling in love with the beast that is the GS2!
anyways, after having the device for you know, 10 hours, I decided it was time to root it. The root went smoothly, CWM, Titanium, and SU are all working properly.
However, I have tried to flash several kernels but I am not able to overclock using any overclocking app, and in ABOUT PHONE it says im just on kernel 2.6.35.11. Making me think that the kernel flash did not happen , although it did say that it was completed successfully each time. I have noticed bits and pieces of other people having a similar issue, although I havent found a fix.
Does anyone know why my GS2 wont take to the kernel I am flashing over it?
That's weird have you flashed bullet or synergy kernels cause they have boot animation, and so you will no 4Shore if it stuck. Also in about phone you will see the bullet or synergy.
Sent from my SGH-T989 using Tapatalk
bbobarino said:
That's weird have you flashed bullet or synergy kernels cause they have boot animation, and so you will no 4Shore if it stuck. Also in about phone you will see the bullet or synergy.
Click to expand...
Click to collapse
ah yes thank you for reminding me I forgot to mention this.
YES I DO GET THE BOOT ANIMATIONS. But nothing in ABOUT PHONE and SetCPU or any other similar app cant change the Governor or Max/Min settings.....Im super confused
Can you post a link to the kernel you're trying to install? Only certain ones are compatible with the Stock image you're running.
Are you wiping cache/dalvik? If yes, when?
tweak. said:
Can you post a link to the kernel you're trying to install? Only certain ones are compatible with the Stock image you're running.
Are you wiping cache/dalvik? If yes, when?
Click to expand...
Click to collapse
I have tried to install (http://forum.xda-developers.com/showthread.php?t=1348007) BULLET versions 2.9b and 2.7b! I have also tried the newest Synergy (http://forum.xda-developers.com/showthread.php?t=1333128) kernel.
I have been wiping cache from CWM after flashing kernel. The only way I know to wipe dalvik is from flashing via rom manager, but I dont like doing that so much. Should I be? Thank you for your help already, I will do whatever you tell me to lol
I should also note that I am not looking to run a custom ROM, at least not at this time. I have my stuff already set up very nicely and would like to keep everything as is (no wipe) , just get that kernel working....
This time, try going to "Advanced" while in CWM; then 'Wipe Dalvik Cache', you might get an ext-sd card error, but your dalvik will still wipe; and then try flashing the kernel.
If that fails, goto "Mounts and Storage" and wipe your cache partition, then dalvik, THEN try flashing.
Get back to us! Always nandroid backup before this procedure as well.
A lot of the custom roms here (with the exception of juggernaut) show a static name for the kernel, regardless of which one you have installed. Juggernaut is the only one that will show the true kernel version. You may very well have installed the new kernel, and just can't tell because the name doesn't show up in about phone.
tweak. said:
This time, try going to "Advanced" while in CWM; then 'Wipe Dalvik Cache', you might get an ext-sd card error, but your dalvik will still wipe; and then try flashing the kernel.
If that fails, goto "Mounts and Storage" and wipe your cache partition, then dalvik, THEN try flashing.
Get back to us! Always nandroid backup before this procedure as well.
Click to expand...
Click to collapse
Thank you! Your first method appears to have worked for me. I can now OC. Related question, what are the details on the new smartassv2 governor and lagfree governor. How do you all find that they compare to the interactive governor, which I am used to using on my N1.
During the time of me writing this response, my phone restarted itself automatically, something that has been happening with the my S2 regardless of which kernel (even stock), do you all experience this aswell? is there a fix?
to mstrk242: thank you for this note, I did not realize.
I am fairly new to Android, but am comfortable with command line operation on other Unix systems, etc. I read every thread I can find on this, but did not find my problem described exactly (there are some similar problems), so here it is:
My phone is a GSM Galaxy Nexus, about a month old. I rooted and unlocked it right away using post 1 from this guide: [VZW/SPRINT/GSM][Guide] Ultimate Galaxy Nexus Guide (Unlock/Root/Flash Roms/FAQ) - thanks Jubakuba!
I did NOT use any of the toolkits or automated methods.
A couple of days ago, I decided to try loading another ROM. I read through post 2 of the above guide. I followed the instructions in that thread and flashed a Trinity ROM. The flash seemed to go fine, and completed normally, but when I rebooted the phone, it was stuck in the Google Lock screen bootloop. I was able to restore a nandroid to get it back to where it was before, and the phone operates normally, no resets, reboots, nada. I inquired in Jubakubas thread as well as in the Trinity ROM thread in the developers section, and got some suggestions, which I tried. None of them worked. I also tried flashing a few other ROMS, a CM9 ROM and the RASCREAM ROM, and they all do the same thing. I have tried flashing these without wiping data or cache or dalvik cache, wiping some of them and wiping all of them, and the results are always the same - boot loop, which I can restore using CWM recovery and my nandroid.
One of the posters in the developers forum suggested taking the phone back to unrooted stock condition, so I did that, using this thread: [HOW-TO] [GSM & CDMA] Convert to latest yakju/takju/mysid build / Return to stock - another excellent guide, which worked exactly as described.
After that, my phone was back to as new, and I had to go through the whole start-up and restore applications, etc. I made a new nandroid so that recovery would be relatively painless, etc. Not too tough. I then Rooted the phone (it was always unlocked) and tried flashing a ROM again, with exactly the same results. Again, I was able to restore my nandroid and get back to operational.
I guess my question at this point is what on earth could be causing this? Some of the threads on boot loops where peoples phones start to boot loop spontaneously suggest a hardware problem, but the fact that I have NEVER had a boot loop in a month of use while running 4.0.4 stock rooted and unlocked seems to point more toward software as the cause. I will say one thing - I am learning how to use CWM and the bootloader commands! But, I would really like to be able to use some custom ROMS, not that there is anything really wrong with stock - this is a great phone. But, please HELP!
Reflash bootloader and radio through fastboot and please describe exactly (!) how you are going about flashing a custom Rom after
Sent from my Galaxy Nexus using Tapatalk 2
d0msen said:
Reflash bootloader and radio through fastboot and please describe exactly (!) how you are going about flashing a custom Rom after
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Okay, I booted into fastboot mode, then flashed the bootloader (bootloader-maguro-primela03.img) and radio (radio-maguro-i9250xxla02.img). I rebooted the bootloader, then went into recovery mode. From recovery mode, I selected "Install zip from sd card", "Choose zip from sd card", then selected the zip file in the /Download folder "TNP1536-384-Alpha86b-4.7-lto.zip". It went through its' install and said "System successfully corrupted" at the end and "Install from sdcard complete." I went back to reboot system rom and rebooted. Now, it is not looping anymore, but just sitting at the Google lock screen for about 2 minutes now. I will wait a few more minutes to see if it boots the rest of the way or starts looping, etc.
Okay, it has been 5-6 minutes with no additional changes, so I am pulling the battery. Powering it on now results in the same boot loop as before, so I will need to boot into bootloader mode and restore my nandroid.
are you wiping data when you flash the rom?
if not, you need to do that first inside of cwm
I would let it sit longer before pulling the battery
Sent from my Galaxy Nexus using xda premium
Anytime you flash a different ROM, you need to wipe - not optional. If you don't, you will have problems.
CYoung234 said:
"System successfully corrupted"
Click to expand...
Click to collapse
The
BOOM!
System successfully corrupted
Please freak out now
is a joke. By your account the kernel flashed successfully. Try flashing another kernel, perhaps not an Alpha version, although I've run that particular Alpha successfully. Do you have an app that sets kernel settings on boot by chance?
Hmmm thats a Kernel i think try another kernel.. Franco is a option ... maybe ur phone can't handle the undervolt of Trinity? I don't know worth a try download franco and post ur results here
Good luck
Is the Rom in the nandroid you're always restoring to something else than 4.0.3 or. 4 based? That would cause trinity to boot loop as it doesn't work on anything lower.
Aside try wiping everything (factory reset + format system under mounts and storage), then flashing something that is considered fairly stable like an aokp milestone build and see if you can boot it without flashing any custom kernel before. Report back
Sent from my Galaxy Nexus using Tapatalk 2
d0msen said:
Is the Rom in the nandroid you're always restoring to something else than 4.0.3 or. 4 based? That would cause trinity to boot loop as it doesn't work on anything lower.
Aside try wiping everything (factory reset + format system under mounts and storage), then flashing something that is considered fairly stable like an aokp milestone build and see if you can boot it without flashing any custom kernel before. Report back
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
The nandroid I am restoring to is stock 4.0.4. I will wipe everything, then try flashing a known stable aokp build, then report back.
efrant said:
Anytime you flash a different ROM, you need to wipe - not optional. If you don't, you will have problems.
Click to expand...
Click to collapse
I have tried this both ways. Wiping prior to flashing does not seem to be as universally accepted as you indicate. For example, in the Trinity ROM dev forum, a number of the more senior posters have the opinion that you should never wipe prior to flashing, that is is an un-necessary step. I do not personally know one way or the other, so I will make sure I wipe prior to flashing from now on.
CYoung234 said:
I have tried this both ways. Wiping prior to flashing does not seem to be as universally accepted as you indicate. For example, in the Trinity ROM dev forum, a number of the more senior posters have the opinion that you should never wipe prior to flashing, that is is an un-necessary step. I do not personally know one way or the other, so I will make sure I wipe prior to flashing from now on.
Click to expand...
Click to collapse
Perhaps they meant if flashing an update of the same ROM (?), just guessing. Even then it can be a good idea sometimes; new Android version (i.e. 4.0.3 > 4.0.4), significant framework changes, etc... but I err on the "safe" side.
Updating to the next nightly of CM9 I wipe absolutely nothing.
CYoung234 said:
I have tried this both ways. Wiping prior to flashing does not seem to be as universally accepted as you indicate. For example, in the Trinity ROM dev forum, a number of the more senior posters have the opinion that you should never wipe prior to flashing, that is is an un-necessary step. I do not personally know one way or the other, so I will make sure I wipe prior to flashing from now on.
Click to expand...
Click to collapse
What Trinity ROM? Unless I'm mistaken, there is no such thing as a Trinity ROM. Trinity kernel, yes, but ROM, no.
Sent from my Galaxy Nexus using Tapatalk 2
CMNein said:
Perhaps they meant if flashing an update of the same ROM (?), just guessing. Even then it can be a good idea sometimes; new Android version (i.e. 4.0.3 > 4.0.4), significant framework changes, etc... but I err on the "safe" side.
Updating to the next nightly of CM9 I wipe absolutely nothing.
Click to expand...
Click to collapse
Yes, pretty much this. If you are updating CM9 to the next build, no need to wipe. If you are going from CM9 to AOKP, then you need to wipe.
Updating: no need to wipe.
New ROM: wipe.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
What Trinity ROM? Unless I'm mistaken, there is no such thing as a Trinity ROM. Trinity kernel, yes, but ROM, no.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Just had a thought. Trinity is the unofficial support thread for Rascream (by Rascarlo), and Morfic did make a build of Rascream with the Linaro 4.7 tool chain.
OP, which Galaxy Nexus do you have?
efrant said:
What Trinity ROM? Unless I'm mistaken, there is no such thing as a Trinity ROM. Trinity kernel, yes, but ROM, no.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
You are correct, it is a kernel, not a ROM. I have tried 3 different Trinity kernels and one Franco kernel, all with the same results. The specific kernel I flashed for post #3 was TNP-1536-384-ALPHA86b-4.7-LTO.zip. The other two I tried were both stable releases. Morfic asked me to try the alpha kernel.
CMNein said:
Just had a thought. Trinity is the unofficial support thread for Rascream (by Rascarlo), and Morfic did make a build of Rascream with the Linaro 4.7 tool chain.
OP, which Galaxy Nexus do you have?
Click to expand...
Click to collapse
Google Galaxy Nexus i9250.
CYoung234 said:
Google Galaxy Nexus i9250.
Click to expand...
Click to collapse
Okay, was asking in the event that you were also flashing Rascream, or Morfic's build of it.
Re: wiping, since we now know that we're just talking kernel here, wiping dalvik + wiping cache is indeed approaching useless, so they weren't leading you astray. I can't think of what would be causing you to boot loop however.
d0msen said:
Is the Rom in the nandroid you're always restoring to something else than 4.0.3 or. 4 based? That would cause trinity to boot loop as it doesn't work on anything lower.
Aside try wiping everything (factory reset + format system under mounts and storage), then flashing something that is considered fairly stable like an aokp milestone build and see if you can boot it without flashing any custom kernel before. Report back
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
SUCCESS! I followed your advice (mostly - I did not factory reset + format system) and d/led AOKP Milestone 5 + GAPPS, flashed bootloader and radio from the bootloader, wiped data / reset, wiped dalvik cache, and booted into recovery and installed both zip files. It booted fine, and I am grabbing my apps and configuring now. I will let you know how it performs and use it for a few days. I will likely head in the Rascream / Trinity direction after using this one for a bit. But thank you to all who have posted.
CYoung234 said:
SUCCESS! I followed your advice (mostly - I did not factory reset + format system) and d/led AOKP Milestone 5 + GAPPS, flashed bootloader and radio from the bootloader, wiped data / reset, wiped dalvik cache, and booted into recovery and installed both zip files. It booted fine, and I am grabbing my apps and configuring now. I will let you know how it performs and use it for a few days. I will likely head in the Rascream / Trinity direction after using this one for a bit. But thank you to all who have posted.
Click to expand...
Click to collapse
This got me thinking: is trinity even compatible with a stock ROM (regardless of it being 4.0.4)? Maybe that is why you were having issues.
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
I am having a weird problem flashing 3rd party kernels.
Whenever I do, my phone will continue to restart until I restore a backup.
Let me give you guys some background:
I turned my initial att galaxy s3 in due to hardware problems.
I learned how to root, install custom recovery, and flash on that phone.
Naturally, when I get my replacement phone, I do the same thing, root, recovery, flash ROMs.
But when I go to flash a third part kernel (BMS, ktoonsez, underware, etc), the phone boots then loops.
I have tried this on aosp ROMs, with 3.0 and 3.4 Linux version kernels (paired appropriately). I have not tried this on TW ROMs. I always wipe cache/dalvik cache prior to flashing kernel, then wipe both caches and fix permissions immediately after flashing.
Does anybody have any idea what's going on?
Any advice?
Sent from my SGH-I747 using xda app-developers app
If you are running an AOSP-based ROM and are only flashing aosp kernels, I don't know why this is not working. What ROM/version are you on? You only need to wipe cache and dalvik when flashing a kernel
I am currently using deviant xone. I've tried flashing the 3.4 versions of both the ktoonsez and BMS kernels.
I tried those kernels with tasks650s ROM, bajee's rootbox ROM, and the official paranoid android. I paid attention to match up the 3.0 ROMs with the 3.0 kernels, and then same with the 3.4 kernel versions.
Its pretty strange. I had no problems whatsoever doing this on previous phone I had; and they're supposed to be identical.
Sent from my SGH-I747 using xda app-developers app
My phone locks up almost daily and I have to remove the battery and then put it back in to get it going again.
This cant be normal...
I have TeamWin loaded onto it and have installed LiquidSmooth using this. I wiped the Cache, Dalvik, System at least three times before installing LiquidSmooth. I have tried installing it a few times with the same result.
Still, the phone locks up and it generally locks up while I am on a call. It generally doesnt lock up while using an app or browsing.
I am getting kind of sick and tired of removing the back cover and pulling the battery daily....
Any thoughts ?? Help !
INFO:
Phone: Samsung Galaxy S3, AT&T, SGH -I747
Android version 4.2.2
LiquidSmooth: liquid_d2att-userdebug 4.2.2 JDQ39 eng.liquid.20130403.222500 test-keys
LiquidSmooth Version Liquid - JB-v2.1-OFFICIAL
Kernel version: [email protected] #167
(I did try installing AOKP as well, and that gives me an error installing, so I couldnt even get that going - maybe these problems are related??)
Shane24 said:
My phone locks up almost daily and I have to remove the battery and then put it back in to get it going again.
This cant be normal...
I have TeamWin loaded onto it and have installed LiquidSmooth using this. I wiped the Cache, Dalvik, System at least three times before installing LiquidSmooth. I have tried installing it a few times with the same result.
Still, the phone locks up and it generally locks up while I am on a call. It generally doesnt lock up while using an app or browsing.
I am getting kind of sick and tired of removing the back cover and pulling the battery daily....
Any thoughts ?? Help !
INFO:
Phone: Samsung Galaxy S3, AT&T, SGH -I747
Android version 4.2.2
LiquidSmooth: liquid_d2att-userdebug 4.2.2 JDQ39 eng.liquid.20130403.222500 test-keys
LiquidSmooth Version Liquid - JB-v2.1-OFFICIAL
Kernel version: [email protected] #167
(I did try installing AOKP as well, and that gives me an error installing, so I couldnt even get that going - maybe these problems are related??)
Click to expand...
Click to collapse
Hey man,
My suggestion is to use Odin to flash the stock image back to stock and see if the problem persists. If it does, I'd take it back to at&t for a new phone (if you've had it less than a year or you have some sort of insurance plan.)
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
---------- Post added at 02:23 AM ---------- Previous post was at 02:18 AM ----------
If flashing back to stock fixes it, its user error. Make sure you're up to date on everything, I.e boot loader, recovery, everything. If that does nothing for you maybe try flashing the new version of CWM and see if it'll flash right that way.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Is it just me or is your lean kernel like years old? Isn't the newest version 7.2?
Same with your rom.. 2.9 is out?
Sent from my SGH-I747 using xda premium
Yes, the kernel could be old. I have never updated it... I hate to admit, but I have no idea what the kernel does actually or how to flash a new one.
I have installed the ROM, but not the kernel obviously....
Any info on what a kernel does? Can I flash it easily with TeamWin ?
I can definitely upgrade the ROM to the latest version of liquidSmooth
Shane24 said:
Yes, the kernel could be old. I have never updated it... I hate to admit, but I have no idea what the kernel does actually or how to flash a new one.
I have installed the ROM, but not the kernel obviously....
Any info on what a kernel does? Can I flash it easily with TeamWin ?
I can definitely upgrade the ROM to the latest version of liquidSmooth
Click to expand...
Click to collapse
Hey man,
If you're going to be flashing custom ROMs you should probably learn what a kernel is. Use the search feature or simply use google. In fact, the xda TV channel just put out a video on kernels this week on YouTube.
Anyways, as I said previously, make sure EVERYTHING is up to date. Including the ROM version. Dont worry about flashing kernels until you have a solid understanding of what they are. I'm almost positive that you are just flashing out of order. Just start from scratch, make sure EVERYTHING is up to date. Good luck.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
yup, I got up to speed on kernels. (Thanks for the suggestions as I didnt know about Kernels, but now I do...)
So, the plan is to
- wipe: dalvic, cache, etc... (3X)
- install the Bionic Sheep 4.2.2 Kernel
- install ROM (I'll try Hyperdrive and DeadlyVenom and LiquidSmooth again)
- install Google Apps...
I have TeamWin installed obviously.
Hopefully this will get my phone back on track...
Shane24 said:
yup, I got up to speed on kernels. (Thanks for the suggestions as I didnt know about Kernels, but now I do...)
So, the plan is to
- wipe: dalvic, cache, etc... (3X)
- install the Bionic Sheep 4.2.2 Kernel
- install ROM (I'll try Hyperdrive and DeadlyVenom and LiquidSmooth again)
- install Google Apps...
I have TeamWin installed obviously.
Hopefully this will get my phone back on track...
Click to expand...
Click to collapse
Hyperdrive and Deadly venom are touchwiz ROMs, u can't flash bionic sheep with them!!! And u don't need to flash gapps with tw ROMs either!!
Also, u need to flash a kernel after u flash the ROM, otherwise it will be overwritten by the stock kernel for whatever particular ROM u are flashing. I would suggest sticking with the stock kernel for a bit and see how it runs!
Shane24 said:
yup, I got up to speed on kernels. (Thanks for the suggestions as I didnt know about Kernels, but now I do...)
So, the plan is to
- wipe: dalvic, cache, etc... (3X)
- install the Bionic Sheep 4.2.2 Kernel
- install ROM (I'll try Hyperdrive and DeadlyVenom and LiquidSmooth again)
- install Google Apps...
I have TeamWin installed obviously.
Hopefully this will get my phone back on track...
Click to expand...
Click to collapse
What the guy above me said about TW roms is correct. Flashing the wrong kernel is not a good idea. Here's what I do on every flash
- wipe system, data, caches, etc.
- flash rom( and gapps if necessary)
- boot up rom and let it settle for 5 min, then boot back into recovery
-flash correct kernel for the rom's version(check kernel number in about device and custom kernels op), then wipe both caches and fix permissions.
-reboot and enjoy:laugh:
DMF1977 said:
Hyperdrive and Deadly venom are touchwiz ROMs, u can't flash bionic sheep with them!!! And u don't need to flash gapps with tw ROMs either!!
Also, u need to flash a kernel after u flash the ROM, otherwise it will be overwritten by the stock kernel for whatever particular ROM u are flashing. I would suggest sticking with the stock kernel for a bit and see how it runs!
Click to expand...
Click to collapse
Which Kernel would I need to use then for Touchwiz ROM's ???
And which kernel for LiquidSmooth and AOKP ??
Shane24 said:
Which Kernel would I need to use then for Touchwiz ROM's ???
And which kernel for LiquidSmooth and AOKP ??
Click to expand...
Click to collapse
Like I said, I would suggest sticking with the packaged kernel that comes with whatever ROM that you are going to flash, run it for a few days, after that if u still feel the need for something more, go with a custom kernel! Ktoonsez makes an excellent kernel, one for tw, and one for aosp, u just have to pick the right one according to which ROM you're running!! Good luck...
DMF1977 said:
Like I said, I would suggest sticking with the packaged kernel that comes with whatever ROM that you are going to flash, run it for a few days, after that if u still feel the need for something more, go with a custom kernel! Ktoonsez makes an excellent kernel, one for tw, and one for aosp, u just have to pick the right one according to which ROM you're running!! Good luck...
Click to expand...
Click to collapse
I did try flashing AOKP with TouchWiz, and it gives me an error that it cant flash.
Is the kernel that Ktoonsez all part of the ROM and just one file ?
Ultimately, I would like to flash AOKP, but my Galaxy S3 wont allow it...
Shane24 said:
I did try flashing AOKP with TouchWiz, and it gives me an error that it cant flash.
Is the kernel that Ktoonsez all part of the ROM and just one file ?
Ultimately, I would like to flash AOKP, but my Galaxy S3 wont allow it...
Click to expand...
Click to collapse
What?
What DMF1977 was saying is just flash the ROM you desire to have on your device and just run the kernel that comes with the ROM. After running the ROM you chose for awhile, if you feel the need to flash a new kernel then and only then flash the correct version of Ktoonsez kernel. And its not surprising that if you tried to flash anything AOKP related with TW you got an error.
Just flash an AOKP ROM and Dont worry about flashing an additional kernel.
Goodluck
Sent from my SAMSUNG-SGH-I747 using xda app-developers app