This is a "best practices" question regarding ways to flash a new kernel whereby there are safe ways, and then there are convenient ways. Best case scenario is that the convenient way is also the safest way, which is the genesis of this thread; I'd like some feedback regarding flashing kernels, especially when we suspect that there may be a bad kernel on our phone, and we need to flash a new one, without the use of a computer.
For the past 6 months, I've used CWM to flash kernels, typically running the Kernel Cleaning Script from Jivy, however, I've recently read here that it isn't necessary, that instead we can just flash the new kernel, without a dalvic or cache wipe, and reboot.
Today, I installed Mobile Odin on my i777 (running ShoStock2-ICS) and installed a kernel with no problem (though it takes mobile odin a few minutes to find the zImage).
So the question for the community is whether or not mobile odin is the "safest" approach to kernel flashing, AND, what procedure one should use to flash a new kernel when they suspect that the kernel they're running is corrupt.
Thanks in advance, and I apologize if this has been covered to death elsewhere. In my opinion, this isn't covered enough for us noobs.
Here's a reference article on flashing kernels (albeit specifically for the stated ROM), wherein the author (bajee11) detests Odin, and adds his personal wipe methodology:
http://forum.xda-developers.com/showpost.php?p=25102880&postcount=1
I wouldn't use the kernel cleaner, it is the only time I have ever had problems.
Galaxy_Cat said:
This is a "best practices" question regarding ways to flash a new kernel whereby there are safe ways, and then there are convenient ways. Best case scenario is that the convenient way is also the safest way, which is the genesis of this thread; I'd like some feedback regarding flashing kernels, especially when we suspect that there may be a bad kernel on our phone, and we need to flash a new one, without the use of a computer.
Click to expand...
Click to collapse
I'm pretty sure Mirriam and Webster rolled over in their graves.
Sent from my SGH-I777 using XDA
How did you get CwM in first place (so that you could flash kernel)?
There are multiple ways, 3 at least but I believe flashing kernel via Mobile Odin is the safest way and it should be a practical way to do so.
votinh said:
How did you get CwM in first place (so that you could flash kernel)?
There are multiple ways, 3 at least but I believe flashing kernel via Mobile Odin is the safest way and it should be a practical way to do so.
Click to expand...
Click to collapse
Why do you believe it is he safest?
Sent from my SGH-I777 using XDA
It's the most user-friendly. It's so freaking easy. And it doesn't trip the flash counter. That's why I think Mobile Odin is the safest.
What are the other ways of getting a custom kernel flashed from stock? Desktop Odin/Heimdall (which trips the counter), anything else?
EDIT: I thought you were asking specifically for flashing your *first* custom kernel. For all other custom kernels after the first one, CWM is definitely easy, since it's the same procedure as flashing new ROMs, mods, etc. Using the kernel cleaning script just wipes cache and Dalvik for you so you don't have to click a couple more times in CWM to do it yourself; you probably don't have to do it when updating to the latest version of the same kernel by the same dev, but it's always a good idea if switching between different kernels and it's just a good practice in general because it ensures you won't have problems whenever you change something.
karate104 said:
It's the most user-friendly. It's so freaking easy. And it doesn't trip the flash counter. That's why I think Mobile Odin is the safest.
What are the other ways of getting a custom kernel flashed from stock? Desktop Odin/Heimdall (which trips the counter), anything else?
EDIT: I thought you were asking specifically for flashing your *first* custom kernel. For all other custom kernels after the first one, CWM is definitely easy, since it's the same procedure as flashing new ROMs, mods, etc. Using the kernel cleaning script just wipes cache and Dalvik for you so you don't have to click a couple more times in CWM to do it yourself; you probably don't have to do it when updating to the latest version of the same kernel by the same dev, but it's always a good idea if switching between different kernels and it's just a good practice in general because it ensures you won't have problems whenever you change something.
Click to expand...
Click to collapse
thank you for the input! I see that Siyah kernel will always say to wipe dalvic and cache, but others do not (like Entropy's, i think, don't quote me). The fact that Jivy made a kernel cleaner in the first place led me to believe it was absolutely necessary, but the more I read in forums, the rule is something like, only when you experience problems.
But that's what I wanted to start this thread for, maybe even here about some horror stories, lessons learned the hard way.
I'm using mobile odin for a while, and it doesn't even have the option to wipe (as far as I can tell..., maybe wrong on that). I like that mobile odin only deals with the zimage itself, no other stuff.
Lekerstein said:
I'm pretty sure Mirriam and Webster rolled over in their graves.
Sent from my SGH-I777 using XDA
Click to expand...
Click to collapse
well, you are mr. clever, so, I'll take your word for it.
switch to Q and A forum?
I realized too late, that I posted this in the wrong forum (it started off a reflection, and ended up more of a question seeking answers...)
If the moderator would like to move it, then please do, and thank you in advance.
Galaxy_Cat said:
thank you for the input! I see that Siyah kernel will always say to wipe dalvic and cache, but others do not (like Entropy's, i think, don't quote me). The fact that Jivy made a kernel cleaner in the first place led me to believe it was absolutely necessary, but the more I read in forums, the rule is something like, only when you experience problems.
But that's what I wanted to start this thread for, maybe even here about some horror stories, lessons learned the hard way.
I'm using mobile odin for a while, and it doesn't even have the option to wipe (as far as I can tell..., maybe wrong on that). I like that mobile odin only deals with the zimage itself, no other stuff.
Click to expand...
Click to collapse
It's been a while, so my recall might be a little fuzzy on this; I think Jivy originally put together the kernel cleaner when we were basically running 2 options for kernels - Entropy's DD and Siyah. I think the original motivation for it was that at some point (and maybe still) Siyah kernel included some init.d scripts for performance, where as Entropy developed his kernel, intentionally, with nothing in init.d. So at the time, if one were to flash from Siyah to Entropy without using a kernel cleaner, those init.d scripts from Siyah would still remain and potentially cause problems with Entropy's kernel. IIRC there was no need for the kernel cleaner when going from Entropy to Siyah.
I am not familiar enough with the inner workings of this stuff to look at it on my own and determine what code is doing what, so at this point, I don't know if the kernel cleaner is still necessary. I don't know if the kernel cleaner "just" wipes cache and dalvik, or if that is an additional feature that Jivy baked in to facilitate flashing for those using the cleaner. I'm inclined to believe that it does "something" else besides wipe dalvik and cache. Perhaps just wipes init.d? I'd imagine that formatting /data and /system prior to a new ROM flash would do the same thing as I would think init.d resides on one of those partitions - but I don't know that for a fact, so someone correct me if I'm wrong here...
Not sure if that helps you at all, but I think that's where this all came from...
Easiest and best are often times polar opposites from one another. The Kernel cleaning script is used, as said above to clear dalvik and cache and some stuff in init.d, with more new Kernels coming to the i777 variant and many of those become more exotic (think NEAK), learning the good practice of using the script, is just that, good practice.
With the exception of flashing the first rooted Kernel, I advocate using CWM to flash any subsequent Kernels. This is the preferred method IMO, as it transcends phones/ROMS/Manufacturer etc. For example I came from Motorola/HTC to Samsung, but as I was already very comfortable with CWM and root in general, I have not had to 're-learn' everything. The same goes with this phone. Learn how to use CWM and when you move onto your next platform, that knowledge goes with you.
That's at least my $.02
I've noticed that most of the kernels leave files on the system partition that aren't used by you anymore, after you delete that kernel.
Flashing kernels in CWR is fine..... I still use Jivys script it takes 2 seconds.... What's it going to hurt? Siyah does leave behind all kind of ****..... I don't use his kernels at all so it don't matter to me but the guys who do run them may want to clean them out. Wiping before flashing has always proved to be a smoother transition between roms and kernels... I would not start making it a practice to not go the next step. This is bad noob banter that's going to get a guy to make a new thread about his glitchy kernel issues.
killing is my business, And business is good.
Lekerstein said:
I'm pretty sure Mirriam and Webster rolled over in their graves.
Sent from my SGH-I777 using XDA
Click to expand...
Click to collapse
Especially when they saw how you spelled Merriam.
xhepera said:
Especially when they saw how you spelled Merriam.
Click to expand...
Click to collapse
Touché...
Sent from my SGH-I777 using XDA
xhepera said:
Especially when they saw how you spelled Merriam.
Click to expand...
Click to collapse
I seriously laughed when I saw that. You just made my day!
So, update is, I'm off the mobile odin bandwagon... Seems like it may have been a poor choice when flashing kernels; it doesn't allow for wiping dalvic and cache, which when coming from Siyah's kernel, is a problem.
Further more, flashing in a unique way won't prevent the catastrophe that happened several weeks ago with the siyah/ att leak fiasco.
good bye mobile odin, hello cwm recovery for all my kernel flashing needs!
Which isn't to say there won't be a special need for flashing a kernel that way in the future, I just haven't seen it yet; good tool to have just in case.
I use the kernel cleaning script with every rom I flash. I wipe /system /data and /cache as well. I have only had one bad flash. I've been using custom roms for 10 months. Wiping fully takes literally like 30 seconds. And prevents any possible problemz. Just do it.
Sent from my SGH-I777 using Tapatalk 2
Be sure to post any flashing problems you have here
For those who hit upon this thread looking for a little insight and help, please post your problem, and let's see what we can do to walk you through it, in the very least, point you towards the proper reference material on xda so you can help yourself, and learn about your phone, and software.
Here's a link to a flashing how-to (by creepyncrawly), that may help shed some light on things in the meantime.
http://forum.xda-developers.com/showthread.php?t=1311081
and here's a link to a beginner's guide from the i9100 forums:
http://forum.xda-developers.com/showthread.php?t=1592104
Galaxy_Cat said:
So, update is, I'm off the mobile odin bandwagon... Seems like it may have been a poor choice when flashing kernels; it doesn't allow for wiping dalvic and cache, which when coming from Siyah's kernel, is a problem.
Click to expand...
Click to collapse
Mobile Odin may not be the best way to switch from one custom kernel to another, but it is certainly the best way to install a CWM kernel once root is initially achieved.
Related
hi i have litening 6.1 installed on my SGS2 but as litepro (litening's maker) has technically retired i am thinking of moving to CyanogenMod7, is there an easy way to do this, as i am totally new to all this.
thanks for looking in.
rab1es
Yes, follow the installation guide that the ROM developer took the time to write for installing his/her ROM.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
After a little practice flashing new roms is like changing your t-shirt. I've found the instructions to be quite similar with most roms. Just double-check for specific variations and use paid backup tools. 15 mins to get completely up and running with a new rom if you're optimized.
Flash this kernel with ODin: http://forum.xda-developers.com/showthread.php?t=1118693
Then install it with CWM. Flash it twice or it won't work,.
sorry for putting it in the wrong section (newbie)
ive downloaded CWM from the market but will have to do some reading as its all foreign to me, is flashing a kernal just like flashing a rom using odin, only point it to the kernal?
rab1es said:
sorry for putting it in the wrong section (newbie)
ive downloaded CWM from the market but will have to do some reading as its all foreign to me, is flashing a kernal just like flashing a rom using odin, only point it to the kernal?
Click to expand...
Click to collapse
You put it in PDA (it must be a .tar file, so don't extract it. If it is a zip file on't flash it through ODIN)
DO NOT check repartition.
After flashing the kernal I gave you, you will have a CWM version that is compatible with CM7 but you wil need root for this.
rab1es said:
sorry for putting it in the wrong section (newbie)
ive downloaded CWM from the market but will have to do some reading as its all foreign to me, is flashing a kernal just like flashing a rom using odin, only point it to the kernal?
Click to expand...
Click to collapse
You don't need ODIN to flash subsequent kernels unless specified by their author/developer. The ones I've flashed have necessitated a cache wipe & a davlik cache wipe followed by an installation from the sd card & reboot. Done.
EDIT: don't listen to me if your question is specifically about kernels for use with CM7 because I haven't flashed that ROM but inevitably will end up there.
Don't let the jargon and nomenclature dampen your spirits. After my first flash things started to click. It seems like instructions for flashing roms and kernels are usually tailored for real power users who have quite a decent grasp of all the terminology and concept. I'm sure part of that is just the sheer frequency of these geniuses doing write-ups (that and the fact that many of them use English as a second language). But after actually using CWM and some of the tools referenced in these forums things just start to click.
I'm a pure noob myself but will be happy to lend any assistance where I can. After all I'll need much of the same courtesy.
anonomike, like you said because its all new to me its very daunting, especially when i read stories of people getting their phone stuck on a certain screen and bricking it. (ive read this is almost impossible) i will have a go at it later today, so everybody stay where you are (just in case )
Is it possible to Hellraise the SGSII (I'm assuming it is an i9100) Oxygen 2.3.2 ROM for our devices? I'm still unsure about all the compatibility issues, but I wanted to ask those who may know before doing something unbelievably dumb.
Well you should be able to use any i9100 rom as long as it can be flashed through CWM, and doesn't need ODIN to install it, i'm not familiar with Oxygen ROM though.
Only thing to be worried about is if the rom has bootloaders included. If it does, stay away.
Other than that, run a backup in cwm before you flash so if it does go bad, you have an easy recovery.
Sent from my páhhōniē
Yeah, I checked for the dreaded Sbl.bin and other assorted bootloaders. Just finished my backup, gonna give it a whirl.
Well, it appears as if I have answered that question, and the answer is "No." The installation keeps aborting, no matter what version I try.
You aren't attempting to install through ROM Manager are you? If so you need to boot into recovery yourself, full wipe, then install. I can't see many other reasons why the install would abort- If that is not the case i'm of no help lol.
No, I booted into recovery, did the various wipes, then tried to install the zip. I tried v2.3 and 2.3.2, with no luck. I'm guessing AdamG put some sort of verification script in to keep dumbass noobs like me from making big mistakes.
Thanks for the update
Sent from my páhhōniē
Oxygen is AOSP-derived, so you'd need to use the CM7 boot.img instead of a Samsung-derived kernel.
If Oxygen enforces device-checking via asserts, you may need to Hellraise an I9100 ROM first. (Although I'm going to be changing this behavior in Hellraiser soon to report the device as a 777.)
Ah, good to know. Well, no harm was done to any phones, so I will consider myself lucky and move on.
Sent from my SAMSUNG-SGH-I777 using xda premium
i wanted to ask if i extract a rom can i use it threw odin to flash a rom
or does anyone have a list of odin flashable roms send it to me please
It would not be easy for someone who doesnt really know what they are doing to convert a flashable .zip into a pit/tar...
Well which type of rom are you looking for specifically? And why flashable through Odin?
Sent from my SGH-T959 (Samsung Vibrant)
Simply stock jvt 2.3.5 can you do it?
Sent from my GT-I9000 using XDA App
Sorry, but I wouldn't know how to go by doing it either. However, you may be able to get the developer to do it... Still I must ask, why through Odin?
Sent from my SGH-T959 (Samsung Vibrant)
Cus my phones dumb it always bootloops everytime I try to flash I do everything they say
Sent from my GT-I9000 using XDA App
whitehawx has a 2.2 odin flashable deodexed kb5 rom I use it as a stepping stone, not sure what your looking for, check dev. sec it wont loop, hawk writes good script
Why not?
I actually came to the Q&A section with a question along these same lines...is there a reason, other than developer preference, for NOT creating more ODIN flashable ROMs? I don't screw up flashing through recovery like the OP but I can say that I have never had to deal with one-off bugs, leftovers from previous ROMs that didn't get wiped (I'm lately a subscriber to the 'wipe three times' even after the paper is clean method), or ROM "settling," etc. I have a little more confidence in the process, I'm seldom so in need of a ROM flash that I am not near a computer...anyway, enough about me.
I am willing, if any developers want to take the time to teach me what is required to accomplish it, to start a project to convert as many of the flashable .zip ROMs as possible into tar files that can be flashed via ODIN.
There. Volunteered meself.
bord1er said:
i wanted to ask if i extract a rom can i use it threw odin to flash a rom
or does anyone have a list of odin flashable roms send it to me please
Click to expand...
Click to collapse
Good luck my friend tried doing this once and ended up bricking his device.
I warned him that it was for experienced people but he didn't listen to me haha
probably the definition of a newb
It's atually pretty easy to do if someone wants to take the time.
Here's the way to do it.
http://forum.xda-developers.com/showthread.php?t=960946&highlight=create+Odin+tar
Once I have my phone configured the way I like it I usually make one as a backup.
edit: the listed partition are for Samsung based roms not CM7or Miui.
heysoos said:
I actually came to the Q&A section with a question along these same lines...is there a reason, other than developer preference, for NOT creating more ODIN flashable ROMs? I don't screw up flashing through recovery like the OP but I can say that I have never had to deal with one-off bugs, leftovers from previous ROMs that didn't get wiped (I'm lately a subscriber to the 'wipe three times' even after the paper is clean method), or ROM "settling," etc. I have a little more confidence in the process, I'm seldom so in need of a ROM flash that I am not near a computer...anyway, enough about me.
I am willing, if any developers want to take the time to teach me what is required to accomplish it, to start a project to convert as many of the flashable .zip ROMs as possible into tar files that can be flashed via ODIN.
There. Volunteered meself.
Click to expand...
Click to collapse
I usually wipe 2 or 3 times as well.. just because I do it at work. I'm an electronics tech, and anytime we clear flash chips we do it 3 times to make sure the old stuff is gone. Stuff does stay in there!! Not sure if it applies to the chips in our devices, but it doesn't hurt to make sure you are clean.. that way you know you won't get skidmarks.
I also wish there were more odin roms.. I guess it is just too much extra trouble when these roms get updated so often.
Hey all,
I just received my i777 and I'm impressed. Coming from a sgs4g seems like a huge improvement, though the devices look physically the same LOL (with the i777 being a bit on the larger side).
Anyways, I've been flashing roms for about a year now with my sgs4g. The forums for the sgs4g had very detailed instructions when flashing, instructions like, what to do if coming from stock, but on this forum ppl just assume you have CWM installed.
What I want is a safe way to upgrade to, let's say, phone bricker. I've noticed that all roms are installed through CWM, and all OP say is "make sure CWM is installed", but there's no mention whatsoever on how to install CWM on this phone.
Maybe i'm complicating things a little bit. On my previous phone, Rom Manager downloaded from market was a NO NO because it'd brick it. So we had to flash a modded CWM via odin made specifically for our phones. Maybe for this phone installing rom manager is all that is needed? yes? OK, found the FAQ. no ROM manager.
Also, somehow this phone came rooted... I bought it new from a store but the unlocked version since I live outside USA.
So, if I'm not mistaken, I should just install rom manager, select my phone from the list, flash CWM recovery and flash away roms on the dev section. Am I correct? I don't want to brick my phone
I would not use Rom manger it's proven to be more of a headache for this device. Look on the dev section there are a couple of packages that you can use to get cwm. If your already rooted you could simply flash a custom kernel like entropys daily driver which already has cwm included in kernel.
Again, if your rooted, easiest way could be to simply use mobile Odin to flash custom kernel(I'm assuming your running gingerbread).
I bought the full version of mobile ODIN. makes life a little simpler when flashing, in my opinion. It's worth the few bucks.
eep2378 said:
I would not use Rom manger it's proven to be more of a headache for this device. Look on the dev section there are a couple of packages that you can use to get cwm. If your already rooted you could simply flash a custom kernel like entropys daily driver which already has cwm included in kernel.
Again, if your rooted, easiest way could be to simply use mobile Odin to flash custom kernel(I'm assuming your running gingerbread).
Click to expand...
Click to collapse
Running GB, yes. It's (i think) completely stock: GB KJ4.
I've checked and I have standard recovery, so I'm looking for the best and safest way to get cmw.
Mobile odin looks like a good option, but would I need the full paid version?
mikeflash said:
Running GB, yes. It's (i think) completely stock: GB KJ4.
I've checked and I have standard recovery, so I'm looking for the best and safest way to get cmw.
Mobile odin looks like a good option, but would I need the full paid version?
Click to expand...
Click to collapse
You don't need pro version, lite version will do just fine. Are you sure you're rooted? You have superuser app? Whether you're rooted or not look here(if you are rooted look at #3 : http://forum.xda-developers.com/showthread.php?t=1311081
Check out this thread, was my experience and I'm running PhoneBricker just fine!
However, backup your apps before flashing and factory reset, wipe cache and dalvik after (possibly before as well) and you should be fine! Will root then you can flash away.
Clay
Sent from my SGH-I777 using XDA
One other point for you. Your phone was flashed, in most probability by the folks who sold it to you, with a leaked version of Gingerbread, UCKJ4. As a result, your flash count is probably at 1, and the secondary bootloader was probably replaced with one that disables the ability to clear the flash counter with a usb jig. If this matters to you, you can test first with a jig to see if it will reset, and if not, you can flash the original UCKH7 secondary bootloader to fix it. Needed files can be found in the Download Repository.
Oh, and my guide explains how to flash a modified kernel containing ClockworkMod Recovery if you need it.
Well, I flashed my phone last night. Used mobile odin for flashing a kernel (siyah) to get CWM, then flashed phone bricker via CWM like I used to do on my old phone. Everything went smooth.
Though I'm not fond on this "4.0.3", it's just a launcher that looks like ICS but I don't want to believe it's a true ICS ROM, because it feels weird, I certainly prefer stock GB (or a custom GB rom) instead of some heavily modded rom with ICS theme.
creepyncrawly said:
One other point for you. Your phone was flashed, in most probability by the folks who sold it to you, with a leaked version of Gingerbread, UCKJ4. As a result, your flash count is probably at 1, and the secondary bootloader was probably replaced with one that disables the ability to clear the flash counter with a usb jig. If this matters to you, you can test first with a jig to see if it will reset, and if not, you can flash the original UCKH7 secondary bootloader to fix it. Needed files can be found in the Download Repository.
Oh, and my guide explains how to flash a modified kernel containing ClockworkMod Recovery if you need it.
Click to expand...
Click to collapse
There're several new terms I need to learn about this phone that weren't used on sgs4g. Such as DPI (i.e lowering it, what for? isn't that a step back?) and flash counter.
I suppose flash count is just a counter for how many times you have flashed the phone with custom Roms, so that warranty people can check if a returned phone was damaged due to bad flash, or something like that. Am I correct?
If that's the case, then I'm not too worried about flash count because I live outside US, and my AT&T phone wouldn't get warranty over here, but I'll definitely look into that, to check where my counter is at and to check if resetting it back to 0 is still possible.
I'll be checking up on the links you provided.
Thanks a lot.
mikeflash said:
Though I'm not fond on this "4.0.3", it's just a launcher that looks like ICS but I don't want to believe it's a true ICS ROM, because it feels weird, I certainly prefer stock GB (or a custom GB rom) instead of some heavily modded rom with ICS theme.
Click to expand...
Click to collapse
It is a true ICS rom. Samsung didn't do a lot of cosmetic changes when they moved the S2 to ICS though...most changes are under the hood.
If you want something that looks and feels more like true ICS, you should consider trying either CM9 or AOKP. They are both based on Google's source code, nothing Touchwiz about them.
Or if you'd rather stick with what you have, you can always try different launchers. I'm running ICS, but I use Go Launcher and it runs beautifully.
mikeflash said:
There're several new terms I need to learn about this phone that weren't used on sgs4g. Such as DPI (i.e lowering it, what for? isn't that a step back?) and flash counter.
I suppose flash count is just a counter for how many times you have flashed the phone with custom Roms, so that warranty people can check if a returned phone was damaged due to bad flash, or something like that. Am I correct?
Click to expand...
Click to collapse
That is mostly correct. You're right about the purpose of the flash counter, but it actually counts how many times you flash kernels, not roms. And even then, it only increments if you flash a kernel via Odin in download mode. Flashing a kernel in Mobile Odin or CWM doesn't touch the counter.
Incrementing the flash counter also places that possibly annoying yellow triangle on bootup on your phone. Since you're on ICS, you can just use triangle away app from play store (free version is on here somewhere) to get rid of it, though I'm not sure if that'll fix the whole secondary bootloaders thing (probably not). I think it'd be worth it to fix that just so you don't run into anymore problems later if you decide to change something, especially since after the fixes you can just nandroid back to your current setup, but it's not essential and completely up to you.
Sent from my Samsung SGH-I777 using XDA
I'm confused why this thread was started. There ARE detailed instructions in the stickies and by using Google search along with the words XDA after the search u would easily find any and all information needed. Why do we need a thread dedicated to helping one person read stickies which already have this information.
Sent from my SGH-I777 using Tapatalk 2
Phalanx, did you not read the Title?
It says be nice!
crawls back into hole
Sent from my SGH-I777 using XDA
Phalanx7621 said:
I'm confused why this thread was started. There ARE detailed instructions in the stickies and by using Google search along with the words XDA after the search u would easily find any and all information needed. Why do we need a thread dedicated to helping one person read stickies which already have this information.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Thank you friend.
To sum up for OP
1. Strongly suggest NOT to use ROM Manager on any custom ROMs unless you are surely running CyanogenMod ROM.
2. Check the "About phone" to see if it is true ICS or ICS-theme GB.
Hi,
I rooted my GSII, using step 2c from the guide found here: http://forum.xda-developers.com/showthread.php?t=1311081 with the UCKK6 Stock + Root package found here: http://forum.xda-developers.com/showthread.php?t=1286432
Afterwards, I used CWM to flash PhoneBricker v2.7 (http://forum.xda-developers.com/showthread.php?t=1560759). After only a few minutes of use, my phone began locking up and rebooting randomly. It didn't matter what I was doing at the time. After reading through some threads, I tried wiping cache, factory reset, and flashing only the ROM again, to no avail. I also noticed the phone would get pretty hot when it would lock up.
I thought the ROM was the issue, so I flashed Mystic's Glory ROM (v.4.9.2beta) after wiping cache, factory reset. Same behavior.
I've resorted to restoring the first nandroid backup I did, which is just stock + root.
Would anyone have any suggestions? Thank you.
I'm not sure i have a suggestion, but i do have a couple of questions, maybe these will at least rule out some obvious possibilities:
- first, the obvious. This is probably not the issue in your case, but since this happens so often i figured I'd ask: we often see people here who have a different SGS2 variant than the I-777 the ROMs on this forum are for. Which variant of the SGS2 do you have? To use the ROMs here it should be I-777, which is AT&T's version of the SGS2, but NOT the skyrocket. If you have a skyrocket or a non-AT&T version, you need to get the ROMs from the appropriate forums.
-Since the FCs are happening with different ROMs, maybe the problem is being caused by an app or app restore method. Do the problems start before you even restore or install your apps, or after? If you are restoring apps with Titanium Backup, make sure you don't restore any system apps, only user apps. Restoring system apps with TiBu is known to cause problems, specially if you restore system apps that you backed up from a different base
Edit: still in the spirit of ruling out the obvious, when you wipe cache before installing the ROM, i assume you are ALSO wiping the dalvik cache?
wgoldfarb said:
I'm not sure i have a suggestion, but i do have a couple of questions, maybe these will at least rule out some obvious possibilities:
- first, the obvious. This is probably not the issue in your case, but since this happens so often i figured I'd ask: we often see people here who have a different SGS2 variant than the I-777 the ROMs on this forum are for. Which variant of the SGS2 do you have? To use the ROMs here it should be I-777, which is AT&T's version of the SGS2, but NOT the skyrocket. If you have a skyrocket or a non-AT&T version, you need to get the ROMs from the appropriate forums.
-Since the FCs are happening with different ROMs, maybe the problem is being caused by an app or app restore method. Do the problems start before you even restore or install your apps, or after? If you are restoring apps with Titanium Backup, make sure you don't restore any system apps, only user apps. Restoring system apps with TiBu is known to cause problems, specially if you restore system apps that you backed up from a different base
Edit: still in the spirit of ruling out the obvious, when you wipe cache before installing the ROM, i assume you are ALSO wiping the dalvik cache?
Click to expand...
Click to collapse
wgoldfarb,
I do, in fact, have the I777 variant.
Can you please tell me what you mean by FCs?
The random lockups/reboots began even before I started installing other apps. I do not have Titanium Backup. I installed the apps from the Play store.
Yes, I made sure to do a factory reset, wipe cache, and wipe dalvik cache.
Could it be an issue with the way the ROM is handling CPU usage? Perhaps there is a preset that is on by default that may be causing lockups.
I'm also wondering rooting using the UCKK6 package was the correct way, as opposed to rooting back to the UCKH7.
I appreciate your help.
What kernel are you running? That sounds like the issue to me
jthatch12 said:
What kernel are you running? That sounds like the issue to me
Click to expand...
Click to collapse
jthatch,
When I rooted, it remained as stock kernel (2.6.35.7).
When I flashed PhoneBricker and Mystic's Glory, I stayed with the kernels that were supplied by the ROM zip package.
wwjd3 said:
jthatch,
When I rooted, it remained as stock kernel (2.6.35.7).
When I flashed PhoneBricker and Mystic's Glory, I stayed with the kernels that were supplied by the ROM zip package.
Click to expand...
Click to collapse
You can't flash a "rom zip package" from the stock kernel with 3e recovery. You need to install a custom kernel with ClockworkMod Recovery first before you install a "rom zip package". So what you are saying is not making sense.
I really don't think it would make any difference whether you used the UCKK6 plus root or the UCKH7 plus root.
Whenever you change base, it is necessary to perform a wipe data/factory reset, and also recommended to wipe cache and to wipe dalvik cache. These should be performed from within Recovery. The wipe data/factory reset should not be performed from the phone settings.
If you flash a new firmware after doing the proper wipes in recovery before flashing, then the new firmware should run without problems, unless the download was bad, causing a bad flash. You should also check the md5 sum of the downloaded file to verify a good download before you flash it.
creepyncrawly said:
You can't flash a "rom zip package" from the stock kernel with 3e recovery. You need to install a custom kernel with ClockworkMod Recovery first before you install a "rom zip package". So what you are saying is not making sense.
I really don't think it would make any difference whether you used the UCKK6 plus root or the UCKH7 plus root.
Whenever you change base, it is necessary to perform a wipe data/factory reset, and also recommended to wipe cache and to wipe dalvik cache. These should be performed from within Recovery. The wipe data/factory reset should not be performed from the phone settings.
If you flash a new firmware after doing the proper wipes in recovery before flashing, then the new firmware should run without problems, unless the download was bad, causing a bad flash. You should also check the md5 sum of the downloaded file to verify a good download before you flash it.
Click to expand...
Click to collapse
I'm sorry. I failed to mention that after rooting, I used MobileOdin to flash a custom kernel (Siyah 2.6) with CWM (step 3a in the first link I provided). From there, before flashing PhoneBricker, I did a factory reset, cache wipe, dalvik cache wipe, all from within CWM. I did NOT perform factory reset from phone settings.
I have not performed a md5 sum check. I guess that would be the next step.
Wwjd3
You are now getting help from extremely knowledgeable people, so i wont even try to add any suggestions...you are in excellent hands
I only wanted to answer your question about "FCs". By FCs I meant forced closes...it's when an app has a problem or stops responding and you get a message saying the app had a problem and had to close. When you said your phone locks up i assumed you meant you were experiencing forced closes.
wgoldfarb said:
Wwjd3
You are now getting help from extremely knowledgeable people, so i wont even try to add any suggestions...you are in excellent hands
I only wanted to answer your question about "FCs". By FCs I meant forced closes...it's when an app has a problem or stops responding and you get a message saying the app had a problem and had to close. When you said your phone locks up i assumed you meant you were experiencing forced closes.
Click to expand...
Click to collapse
Ah, I understand. What I meant by lockup is that the system freezes. The capacitive buttons no longer respond. Neither do the volume/power buttons. The screen simply freezes, and I have to force a restart by holding down the power button for a number of seconds. I hope that makes sense.
Wow. Well, I hate to say it, but...lol I would go back to stock 2.3.4 with Odin, wipe everything, and try again. I mean that answer sucks. But it may help rule out some things and give u an idea if its hardware or software related. U could also try different kernels and using the kernel cleaning script, just Google it with xda in the search and it'll come up.
Sent from my SGH-I777 using Tapatalk 2
Phalanx7621 said:
Wow. Well, I hate to say it, but...lol I would go back to stock 2.3.4 with Odin, wipe everything, and try again. I mean that answer sucks. But it may help rule out some things and give u an idea if its hardware or software related. U could also try different kernels and using the kernel cleaning script, just Google it with xda in the search and it'll come up.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Phalanx7621,
heh. That's what I'm thinking of doing. Can someone clarify, though: according to the forum stickies, when flashing a custom kernel with CWM after rooting, there are only two available, correct? Daily Driver and Siyah.
Secondly, can you briefly describe what the kernel cleaning script accomplishes. I've seen the term in some posts, but didn't think it was relevant. Thank you.
wwjd3 said:
Phalanx7621,
heh. That's what I'm thinking of doing. Can someone clarify, though: according to the forum stickies, when flashing a custom kernel with CWM after rooting, there are only two available, correct? Daily Driver and Siyah.
Secondly, can you briefly describe what the kernel cleaning script accomplishes. I've seen the term in some posts, but didn't think it was relevant. Thank you.
Click to expand...
Click to collapse
1. Short answer - yes. Long answer - no (I remember a few other options floating around). For all intents and purposes, just pick one of those; either will accomplish what you need.
2. From what I remember about looking at the script, it wipes dalvik cache and deletes the contents of /etc/int.d (to prevent incompatible scripts across kernels - not exactly relevant since you're doing clean installs). No rom should have kernel specific scripts anyway. I think it wipes some system caches or something also.
Simba501 said:
not exactly relevant since you're doing clean installs). No rom should have kernel specific scripts anyway. I think it wipes some system caches or something also.
Click to expand...
Click to collapse
If I read correctly, Phalanx was offering up a secondary option to try out before taking the complete stock route which would make it relevant. However, if he does the return to stock... Then you're right, not gonna do much for him. (though it wouldn't hurt)
Clay
Team Pirate
Sent from my PINK SGH-I777
You've described following the correct procedure for rooting and flashing a custom firmware. I don't see anything in that procedure that could cause firmware problems, except perhaps corrupt downloads. But the odds are against getting two corrupd downloads in a row.
If it were my phone, I would probably flash back to stock, and run it a few days to see if it runs correctly, to rule out hardware problems. If there is developing hardware issues, bad memory perhaps, then it should be evident even on straight stock.
The next thing is to just start from scratch, and do everything over again. When I flashed SHOstock2 1.4.1 over 1.3.2 (change of base) I did everything right, but I got apps freezing and other problems, so much that the phone was unusable. I went back to 1.3.2 for a week, then flashed 1.4.2 successfully. So the answer could be just a bad flash even though you can't put your finger on the exact reason.
creepyncrawly said:
You've described following the correct procedure for rooting and flashing a custom firmware. I don't see anything in that procedure that could cause firmware problems, except perhaps corrupt downloads. But the odds are against getting two corrupd downloads in a row.
If it were my phone, I would probably flash back to stock, and run it a few days to see if it runs correctly, to rule out hardware problems. If there is developing hardware issues, bad memory perhaps, then it should be evident even on straight stock.
The next thing is to just start from scratch, and do everything over again. When I flashed SHOstock2 1.4.1 over 1.3.2 (change of base) I did everything right, but I got apps freezing and other problems, so much that the phone was unusable. I went back to 1.3.2 for a week, then flashed 1.4.2 successfully. So the answer could be just a bad flash even though you can't put your finger on the exact reason.
Click to expand...
Click to collapse
I just used your guide to return back to stock UCKH7. I am attempting to root again, this time using DooMLoRD's Easy Rooting Toolkit. Not having any luck with that one (complaining about "cannot stat files"). I'm looking through the I777 forums but there is no chatter about this issue. There is for other phones, however. And the search continues. Thanks for your help!
wwjd3 said:
I just used your guide to return back to stock UCKH7. I am attempting to root again, this time using DooMLoRD's Easy Rooting Toolkit. Not having any luck with that one (complaining about "cannot stat files"). I'm looking through the I777 forums but there is no chatter about this issue. There is for other phones, however. And the search continues. Thanks for your help!
Click to expand...
Click to collapse
How did you root your phone b4? which method?
Use that.
votinh said:
How did you root your phone b4? which method?
Use that.
Click to expand...
Click to collapse
I used method 2c, Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package with Modem using Odin3 One-Click Downloader previously. I was thinking of using a different method, since I ran into problems using Entropy512's method. Try something different.
-------------------------------------------------
EDIT:
I'm sorry, I was wrong. Since I had UCKK6 build previously I used Odin to flash the Kernel + cache + rooted UCKK6 system package found here: http://forum.xda-developers.com/showthread.php?t=1286432
So, using method 2c would, in fact, be a different method altogether. I'm beginning to think that initially rooting using Odin+UCKK6 package is what got me into trouble in the first place.
wwjd3 said:
I'm beginning to think that initially rooting using Odin+UCKK6 package is what got me into trouble in the first place.
Click to expand...
Click to collapse
It's as good a theory as any other... I guess.