Okay so I checked it out and it looks easy to root this phone but I want to put clockworkmod on the phone so that I can make custom backups. I am a little confused it looks like this phone has a download mode where I can do my flashing without CWM is that correct? If I understand right I have to download or flash a custom kernel with temp root permissions in order to install CWM, then from there I can use superoneclick to root permanantly. So then do I go back to the original kernel or a custom one if I like? Do I need CWM to install custom ROMS or can I just use this download mode? I am sorry for all the questions this is only my second samart phone actually third but I dont really count the Blackberry curve 2g. I never rooted my g2x till after it got its gingerbread update so I never used superoneclick I just had to use nvflash to install CWM then flash a custom ROM so this is a little different to me. I see there is alot of dev stuff for this phone and I cant wait to get started but I want to make sure I do it right. I saw a few other methods for root but since I want cwm anyway I figure just use superoneclick. Also if I hold vol down+home+power then my phone will do a factory reset right? unless I install CWM then it will boot into cwm right? Sorry to ask all these questions I just need alittle bit more info before I start I am very nosy and I like to understand fully what I am doing and how it works. so anyone with any helpful advice on this phone please chime in I would like to know all the tips tricks and shorcuts that this phone has. Thanks in advance and again it is nice to join a new fourm.
Charlie
Tl;dr; there's a Q&A thread with your answers.
Have a look for cf-root, its got everything you need and easy to follow instructions
Sent from my GT-I9100 using XDA App
As per seanicca above, you need CF root which is both rooting and CWM in one flash (using Odin).
Look at the xda bookmarks in my sig for a link and just read the instructions in the thread. It's a couple of minutes and it's done.
So what is this flash counter I keep reading about? Samsung actually put a counter in the phone to see how much flashing goes on? I still cant belive this phone has its own flash mode basically. I dont know that much about phones maybe that is a normal feature but I dont think so.
mojorisin7178 said:
So what is this flash counter I keep reading about? Samsung actually put a counter in the phone to see how much flashing goes on? I still cant belive this phone has its own flash mode basically. I dont know that much about phones maybe that is a normal feature but I dont think so.
Click to expand...
Click to collapse
You're right - it's not a normal feature. I've never had it on a phone before the S2, but I'm sure it must have been around before. I've heard of some suppliers refusing to repair or replace phones that have a flash count on them, but I've also heard of an equal amount that don't care and ignore or don't know about it.
As you'll see all over the place on this forum there's 2 ways to get rid of it. 1 reflash a stock kernel, or 2 use a usb jig. I've gone down the 2nd route as it was only a few quid and is just quick and easy.
I understand that this may have been asked, and I've been looking at similar threads, but I'm having a hard time finding a direct answer, so I apologize.
I have some experience rooting with an Atrix, but I just got this phone two days ago, this morning I used the 1-click method from rootwhiz to install the ICS leak. No problems having it run at all. I need to know, directly, did this install change my bootloader and change the binary count? I can't remember if I saw anytime of yellow triangle as people talk about. If it changed the bootloader what is there a safe method to return to the older bootloaders, and or do I even need to do so to root and install other roms?
I know that the Atrix had some problems in terms of returning to prior versions of things, and in my research I haven't found a direct answer to this question too.
Basically, did my bootloader change? Can I root using the heimdall method I keep seeing about safely? What would be the best way to root and install custom roms, neglecting the binary counter if I can get a jig or something?
Forgive me again for asking, I just need to have better answers before I try anything.
Are you asking for info for your Atrix or SGS2 device?
Sorry, I am asking about the SGS2.
ds1904.ds said:
I understand that this may have been asked, and I've been looking at similar threads, but I'm having a hard time finding a direct answer, so I apologize.
I have some experience rooting with an Atrix, but I just got this phone two days ago, this morning I used the 1-click method from rootwhiz to install the ICS leak. No problems having it run at all. I need to know, directly, did this install change my bootloader and change the binary count? I can't remember if I saw anytime of yellow triangle as people talk about. If it changed the bootloader what is there a safe method to return to the older bootloaders, and or do I even need to do so to root and install other roms?
I know that the Atrix had some problems in terms of returning to prior versions of things, and in my research I haven't found a direct answer to this question too.
Basically, did my bootloader change? Can I root using the heimdall method I keep seeing about safely? What would be the best way to root and install custom roms, neglecting the binary counter if I can get a jig or something?
Forgive me again for asking, I just need to have better answers before I try anything.
Click to expand...
Click to collapse
If you used the 1-Click method, yes. Your bootloaders are changed. Wouldve been much better to use the Heimdall method or just root your phone then flash the Leak ROM that task650 and Fenny made. As far as reverting bootloaders to stock, thats out of my range of knowledge. Im sure there is a way to do it though.
EDIT: For rooting, best way is to be on stock 2.3.4 and use the Zergrush exploit.
I've seen you're using the past tense a lot, I thought you already DID.
Anyway, for rooting and installing custom ROM, follow this thread:
http://forum.xda-developers.com/showthread.php?t=1311081
I can't pinpoint exactly what to do since having no info.
Thanks for the answers so far, now that I know my bootloaders have been changed I need to figure out how to either change back / and how to safely root. I may just have to wait it out I think though, no problem with that really, working just fine now. And never use the alarm
For clarification, my rooting experience is limited to the Atrix, the SGS2 is new as of Monday, and I am having trouble sifting through information. What I've learned so far is that maybe it was a little hasty to install the ICS leak the way I did. Prior to the ICS leak there was nothing changed on the phone.
You're going to have to get some experience with ODIN. Here is the bootloader you'll want to flash back to, however, then you'll probably need to flash a kernel with CWM (clock work mod) and then boot into cwm to flash a rom such as Tasks stock ICS leak. http://forum.xda-developers.com/showthread.php?t=1316726
So if I follow correctly the ICS leak I installed added newer bootloaders that prevent jigging in the future if it was needed. My two options are apparently to use the method that bypasses the counter, which was posted, or to use ODIN and flash the older bootloader, but this can be dangerous if done incorrectly.
The danger of bricking scares me a little, but I successfully used RSD Lite to unlock the bootloader on my Atrix, don't know if it's similar. Perhaps I should take the Atrix and attempt to install an older bootloader on it to get a feel for things? I figure that it wouldn't make much of a difference however...
I figured out that even though I have a newer bootloader now I still have a 0 for the binary counter, as the leak is considered a samsung official release, of course I don't know how that would effect any given warranty.
So, I still feel that these following questions are unanswered, I apologize if I am not understanding correctly:
1. Is it safe for me to root with the heimdall method even with the newer bootloaders
2. Is it safe for me to install custom roms without reverting the bootloader, as long as I am using the bypass method to prevent my counter from changing?
3. What is the exact risk to flashing the older bootloader, and what precautions should I take before doing so? If I flash the older bootloader without reverting to stock firmware will that cause a brick? Or is the risk just associated with fudging up the process of the flash itself, and hoping that the connection doesn't get cut (on that note, the phone, usb cord, and computer I'm using are all less than 4 months old, so that risk doesn't concern me a whole lote).
Sorry if these are stupid questions, I hope I am asking good enough questions to help others out in the future
After some more reading, here's another question as well:
Does the SGS2 technically have an unlocked bootloader already? It just counts how many times you install non samsung firmware?
Also just so I know that I'm not wrong, are Kernal, Firmware, and "Roms" all the same thing? How can you tell if a "package" or "rom" comes with bootloaders, as this is something I apparently am supposed to avoid.
ds1904.ds said:
1. Is it safe for me to root with the heimdall method even with the newer bootloaders
Click to expand...
Click to collapse
Dont believe you can root since you already flashed it with ODIN 1-Click
ds1904.ds said:
2. Is it safe for me to install custom roms without reverting the bootloader, as long as I am using the bypass method to prevent my counter from changing?
Click to expand...
Click to collapse
You cannot install custom ROM's because you dont have CWM.
ds1904.ds said:
3. What is the exact risk to flashing the older bootloader, and what precautions should I take before doing so? If I flash the older bootloader without reverting to stock firmware will that cause a brick? Or is the risk just associated with fudging up the process of the flash itself, and hoping that the connection doesn't get cut (on that note, the phone, usb cord, and computer I'm using are all less than 4 months old, so that risk doesn't concern me a whole lot).
Click to expand...
Click to collapse
Really not sure on these questions. Any takers?
ds1904.ds said:
After some more reading, here's another question as well:
Does the SGS2 technically have an unlocked bootloader already? It just counts how many times you install non samsung firmware?
Click to expand...
Click to collapse
No; Only download mode (Odin/Heimdall) flashes trigger changes to the warning screen.
ds1904.ds said:
Also just so I know that I'm not wrong, are Kernal, Firmware, and "Roms" all the same thing? How can you tell if a "package" or "rom" comes with bootloaders, as this is something I apparently am supposed to avoid.
Click to expand...
Click to collapse
Kernel is a set of drivers that tells the hardware what to do. Firmware is like a new base. (XXLPQ, DXLP7 etc.) A ROM is the whole package.
Please if I missed anything or am incorrect about some/all of this, somebody correct me.
Okay I think I'm starting to figure this out. I downgraded to 2.3.4 using an unroot/stock method I found, using odin and it worked. It would not accept the OTA update however, but I believe this is due to the ULCL2 baseband? Someone correct me if I am wrong.
Now I am going to use method 2c found here:
http://forum.xda-developers.com/showthread.php?t=1311081
to root and restore to the other baseband, which also happens to be the one that's best for my area I believe. From there, I can install CWM using one of the 31-c methods, and use CWM to install custom roms as long as they don't have bootloaders, correct? Or does it not matter if the packages have bootloaders.
Someone correct me if I am wrong, I don't want to ruin anything here. I think it's safe to install the files that come from the 2c method but wont be doing anything else until I know it's safe.
ds1904.ds said:
Okay I think I'm starting to figure this out. I downgraded to 2.3.4 using an unroot/stock method I found, using odin and it worked. It would not accept the OTA update however, but I believe this is due to the ULCL2 baseband? Someone correct me if I am wrong.
Now I am going to use method 2c found here:
http://forum.xda-developers.com/showthread.php?t=1311081
to root and restore to the other baseband, which also happens to be the one that's best for my area I believe. From there, I can install CWM using one of the 31-c methods, and use CWM to install custom roms as long as they don't have bootloaders, correct? Or does it not matter if the packages have bootloaders.
Someone correct me if I am wrong, I don't want to ruin anything here. I think it's safe to install the files that come from the 2c method but wont be doing anything else until I know it's safe.
Click to expand...
Click to collapse
Should be fine. NONE of the ROMs you find on the I777 boards in Ported or Original will have bootloaders so no worries. And yes after root use Mobile ODIN to install a zImage which will give you CWM. Highly recommend Siyah 2.6.14. Please stick to just trying some GB ROM's and get the hang of making nandroids etc before moving on the ICS ROM's.
D3M3NT3D_L0RD said:
Should be fine. NONE of the ROMs you find on the I777 boards in Ported or Original will have bootloaders so no worries. And yes after root use Mobile ODIN to install a zImage which will give you CWM. Highly recommend Siyah 2.6.14. Please stick to just trying some GB ROM's and get the hang of making nandroids etc before moving on the ICS ROM's.
Click to expand...
Click to collapse
All I get is an apk file, I've been searching all night for a zimage... The file says i777 flashkernal, and it's just an .apk. Mobile Odin can't see it unless I name it zimage with no file extension. I tried that and it seemed like it was soft-bricked so I used odin on the PC to reflash the stock root think mentioned in the thread.
I was thinking of CM7 if it will work flashing as a zip from CWM, if I can get CWM on there that is.
ds1904.ds said:
All I get is an apk file, I've been searching all night for a zimage... The file says i777 flashkernal, and it's just an .apk. Mobile Odin can't see it unless I name it zimage with no file extension. I tried that and it seemed like it was soft-bricked so I used odin on the PC to reflash the stock root think mentioned in the thread.
I was thinking of CM7 if it will work flashing as a zip from CWM, if I can get CWM on there that is.
Click to expand...
Click to collapse
Where in the hell are you getting an apk from? If you dl Siyah or Entropy kernel, the zImage is in the zip. Pull that and put it on your SD card
I am interested because I was in your position. Did the ICS leak 1 day too early and lost root. So what method did you use to go back to GB? Did you have to flash a new bootloader or was that all done in one package? Was it Entropy's "return" method?
I was seeing if I can keep the ICS leak and root. A dev here advised that all I need to do is re-flash the zip filed ICS leak. However since I have no root, I can't CWM recovery...I don't know another method to flash the rooted ICS leak.
So I'm thinking I have to wait for an exploit, or flash back to an old GB, root, ensure I have CWM, nandroid (I nandroided my rooted GB before upgrading to ICS leak), then flash the zip ICS leak.
Does anyone else have alternatives?
ds1904.ds said:
Okay I think I'm starting to figure this out. I downgraded to 2.3.4 using an unroot/stock method I found, using odin and it worked. It would not accept the OTA update however, but I believe this is due to the ULCL2 baseband? Someone correct me if I am wrong.
Now I am going to use method 2c found here:
http://forum.xda-developers.com/showthread.php?t=1311081
to root and restore to the other baseband, which also happens to be the one that's best for my area I believe. From there, I can install CWM using one of the 31-c methods, and use CWM to install custom roms as long as they don't have bootloaders, correct? Or does it not matter if the packages have bootloaders.
Someone correct me if I am wrong, I don't want to ruin anything here. I think it's safe to install the files that come from the 2c method but wont be doing anything else until I know it's safe.
Click to expand...
Click to collapse
SMH...root is not needed for CWM... a custom kernel is
Pirateghost said:
SMH...root is not needed for CWM... a custom kernel is
Click to expand...
Click to collapse
True but to do it with Mobile ODIN you need root
ds1904.ds said:
After some more reading, here's another question as well:
Does the SGS2 technically have an unlocked bootloader already? It just counts how many times you install non samsung firmware?
Also just so I know that I'm not wrong, are Kernal, Firmware, and "Roms" all the same thing? How can you tell if a "package" or "rom" comes with bootloaders, as this is something I apparently am supposed to avoid.
Click to expand...
Click to collapse
"ROM" is an improper name for the firmware flashed to a phone. (the memory in question isn't read-only by any means. In Windows Mobile devices, you had to flash the firmware image all in one go - but on Android, /system contents can be modified on the fly as they're a normal file system.) garyd9 started a little crusade against the term ROM and I try to continue it (but I slip up sometimes).
Kernel contains the most basic low-level hardware drivers for a device. It's a small portion of the firmware for a phone. The remaining portion is the system partition - /system - kernel and /system together make a complete firmware package.
And you are correct - our bootloaders are fundamentally unlocked, the only code signing enforcement is the custom binary counter. It can be reset either with the jig or with TriangleAway (TriangleAway requires ICS)
Entropy512 said:
"ROM" is an improper name for the firmware flashed to a phone. (the memory in question isn't read-only by any means. In Windows Mobile devices, you had to flash the firmware image all in one go - but on Android, /system contents can be modified on the fly as they're a normal file system.) garyd9 started a little crusade against the term ROM and I try to continue it (but I slip up sometimes).
Kernel contains the most basic low-level hardware drivers for a device. It's a small portion of the firmware for a phone. The remaining portion is the system partition - /system - kernel and /system together make a complete firmware package.
And you are correct - our bootloaders are fundamentally unlocked, the only code signing enforcement is the custom binary counter. It can be reset either with the jig or with TriangleAway (TriangleAway requires ICS)
Click to expand...
Click to collapse
Glad you chimed in. I now feel stupid at my lack of knowledge
I almost think that the issue is that your "unzipping" the zip image files that you are downloading.
Why is it so important that you keep the phone in a reversable mode? Are you planning on returning it or perhaps selling it and do not want it to be known that you have flashed it?
Personally I am not knowledgeable enough to offer much advice, I just read the forums as most and try to put together the peices of information that fit my situation.
The Dev forum is by far the best place to look and get your questions answered and there are a bunch of guides on step by step processes. The only real advice I can give you is to google each term and understand what it is you need and then post your question.
Hello Community!
So I had my Desire for quite long time, december 2010, and I rooted it and installed CM on it. When the CM team announced the CM9 devices I was heartbroken: no update for my sweet desire So a week ago I bought my S3!!! I LOVE IT! I just miss the old CM Yes I like touchwiz and stuff, but CM and rooting is just so much more powerful for a device like that(and desire was horrible with stock lol).
So my actual question is:
Am I still going to use clockworkmod?
Can I brick my phone?
Can I unroot my s3 if I root it?
If I brick the phone, is there any way to unbrick it?
tips and hints?
from nervous me
In order (to the best of my current knowledge)
Yes you will still be using CWM unless you flash EXT4
I believe you can like always but if you read everything twice and follow it to the line you should be safe
As far as I'm aware there is no un-root method yet but there will be
Again I don't think there is un-brick method yet but there will be, but the chances of bricking are so low like I said before if you pay attention you should be fine
Hope this helps.
Rooted my phone few days after i got the phone on may 25th. Been installing and testing Omega Roms for more than 2 weeks. Tested few different kernels and now o/c'd the device to 1800mhz. So far so good.
Have done nand backup (almost everyday one or two backups)
Backup on PC using Kies
EFS backup using
few links to help you get started
For CWM/ROOT etc
http://forum.xda-developers.com/showthread.php?t=1695238
For omega roms
http://forum.xda-developers.com/showthread.php?t=1663656
For o/c kernel
http://forum.xda-developers.com/showthread.php?t=1691401
For must have toolkit for SIII
http://forum.xda-developers.com/showthread.php?t=1703488
You can go to android dev forum for SIII for more info.
Thx for the super fast and helpful replys!
What about warrenty and stuff like that?
I heard about something called TriangleAway, it removes the flash counter to 0. But if the phone is rooted, how can the triangleaway help?
If the phone needs to be repaired, what about that?
Thx again
When you un-root the device you can use triangle away to remove the flash counter so the phone will look like its never been touched it's pretty awesome
SkillfulMmd said:
When you un-root the device you can use triangle away to remove the flash counter so the phone will look like its never been touched it's pretty awesome
Click to expand...
Click to collapse
Correction: You can't unroot the phone and use triangle away but once you use triangle away use MOBILE ODIN (this doesn't add to counter) to flash stock rom then the phone gets unrooted and everything gets back to factory default.
I need advise on whether I should root my GS3 and thinking of flashing CM10.1 or just wait to see if the Sudden Death Syndrome (SDS) passes my device.
Thing is I'm afraid to void my warranty. Not a big deal but a warranty is always good to have. What's your advise on this matter?
Also, total noob question, what would be the easiest way to root and flash CM10.1? It isn't exactly a one click process like jailbreaking an iPhone and this is my first Android powered device so yeah.
What advise u need ?
Got my SIII yesterday open the box used this toolkit http://forum.xda-developers.com/showthread.php?t=1703488 to root and flash CWM and then Omega Rom, All the process took me approx 30 Mins including the Rom DL.
if u want to return the phone for warranty u can always flash the Stock Rom.
Hope i helped.
rkkaranrk said:
What advise u need ?
Got my SIII yesterday open the box used this toolkit http://forum.xda-developers.com/showthread.php?t=1703488 to root and flash CWM and then Omega Rom, All the process took me approx 30 Mins including the Rom DL.
if u want to return the phone for warranty u can always flash the Stock Rom.
Hope i helped.
Click to expand...
Click to collapse
Well rooting and flashing custom rom doesn't seem to be as safe as jailbreaking an iPhone. I can't seem to find threads for CM10.1 and how stable that ROM is. I am still feeling insecure in rooting and all that.
The flashing stock rom is also a bit foreign to me! Where do I get stock rom? and if I root there will be that system modified thing on Samsung phones right? it's all these things that makes me think twice..
Well rooting and flashing custom rom doesn't seem to be as safe as jailbreaking an iPhone. I can't seem to find threads for CM10.1 and how stable that ROM is. I am still feeling insecure in rooting and all that.
The flashing stock rom is also a bit foreign to me! Where do I get stock rom? and if I root there will be that system modified thing on Samsung phones right? it's all these things that makes me think twice..
Read the BASICS before you start .
Flashing and root are not risk free its your choice .
Risk is vastly increased by refusing to read/follow instructions .Millions of safe flashes by XDA members .
http://forum.xda-developers.com/showthread.php?t=1927113
jje
JJEgan said:
Well rooting and flashing custom rom doesn't seem to be as safe as jailbreaking an iPhone. I can't seem to find threads for CM10.1 and how stable that ROM is. I am still feeling insecure in rooting and all that.
The flashing stock rom is also a bit foreign to me! Where do I get stock rom? and if I root there will be that system modified thing on Samsung phones right? it's all these things that makes me think twice..
Read the BASICS before you start .
Flashing and root are not risk free its your choice .
Risk is vastly increased by refusing to read/follow instructions .Millions of safe flashes by XDA members .
http://forum.xda-developers.com/showthread.php?t=1927113
jje
Click to expand...
Click to collapse
I've gotten myself into a bit of a problem now. I used ChainFire's exynos exploit patch a while back and I am unable to get root when trying to use heimdall. I'm on a Mac so that was the first thing that came up. Ideas?
PS. Heimdall says it worked perfectly but when I go into recovery, it's androids recovery with a red triangle thin in the centre. I'm now not rooted, and system says I'm modified. So I'm screwed left and right. No CWM Recovery, no SuperSU, and I'm flat out of ideas. I though turning on USB debugging would help but sadly didn't. I don't even know how to reverse the process to have my system status showing normal too!
Damn this...all because of stupid me patching
ever since i first rooted my s2 2 years ago it's booted up with the I900 on startup. i didn't pay any attention to it then cause i was new to flashing and rooting but i installed Resurrection Remix last night and tonight i'm trying out the Pacman Rom and i noticed its still there. I know i have the i777 at&t version for sure but was curious as to why the new roms aren't fixing the bootup. i don't think it's that big of an issue (or is it??) but yea. anyone know why?
Do you have the yellow triangle too? If so it's because you tripped the counter for installing custom roms. No big deal unless you need warranty which sounds like you'd be out of anyway.
Sent from my GT-p511x
sharonbw said:
Do you have the yellow triangle too? If so it's because you tripped the counter for installing custom roms. No big deal unless you need warranty which sounds like you'd be out of anyway.
Sent from my GT-p511x
Click to expand...
Click to collapse
yea i have the triangle and figured thats why it showed up. i just thought it curious that the model number would be wrong
ok i have another question and i didn't want to make a new thread..
on the pacman 4.3 rom when you go to lock screen settings it lets you choose "system icons" which i like wayy more than the default android icons. where are they stored on the phone? and how do i go about placing them in an easily accessible folder so i can change up my icons other than the lockscreen ones
sil3nt_trill said:
ok i have another question and i didn't want to make a new thread..
on the pacman 4.3 rom when you go to lock screen settings it lets you choose "system icons" which i like wayy more than the default android icons. where are they stored on the phone? and how do i go about placing them in an easily accessible folder so i can change up my icons other than the lockscreen ones
Click to expand...
Click to collapse
You might need to ask this in the pacrom thread (that's a cool feature!)
Re the I9100 logo, it is apparently because at&t was to lazy to make a separatescreen for the I777. Once you've tripped the counter, that's what you get. It bugged me a lot so I got rid of it. I'd have to re-search the threads addressing this (or you can if you care about it.
Sent from my GT-p511x
can't post in developer forums -_-
sharonbw said:
You might need to ask this in the pacrom thread (that's a cool feature!)
Re the I9100 logo, it is apparently because at&t was to lazy to make a separatescreen for the I777. Once you've tripped the counter, that's what you get. It bugged me a lot so I got rid of it. I'd have to re-search the threads addressing this (or you can if you care about it.
Sent from my GT-p511x
Click to expand...
Click to collapse
No it sounds like 2 years ago he used the old Zedomax method of rooting and used an i9100 kernel to do it. My counter is tripped and the ONLY time its ever said i9100 was because of Zedomaxs method which used modded i9100 firmware. Nada to do with ATT as far as i remember. Otherwise all of us custom rom users would still have that screen.
Slavestate said:
No it sounds like 2 years ago he used the old Zedomax method of rooting and used an i9100 kernel to do it. My counter is tripped and the ONLY time its ever said i9100 was because of Zedomaxs method which used modded i9100 firmware. Nada to do with ATT as far as i remember. Otherwise all of us custom rom users would still have that screen.
Click to expand...
Click to collapse
Could be. I thought that using Odin to install anything custom is what tripped the counter and that if you use mobile Odin or flash via cwm you don't trip it. However, I believe I may have installed a zedomax kernel to trip mine (I did it recently when attempting to return to stock - I forget exactly what I did.)
Anyway, I read that the triangle screen from tripping the counter always says I900 even on the I777. Mine did and it totally got on my nerves so I followed instructions to get rid of it. I couldn't use chainfires triangle away so I followed some more complicated instructions. I don't remember the link but I could probably find it - although anyone else probably can too.
Sent from my GT-p511x
sharonbw said:
Could be. I thought that using Odin to install anything custom is what tripped the counter and that if you use mobile Odin or flash via cwm you don't trip it. However, I believe I may have installed a zedomax kernel to trip mine (I did it recently when attempting to return to stock - I forget exactly what I did.)
Anyway, I read that the triangle screen from tripping the counter always says I900 even on the I777. Mine did and it totally got on my nerves so I followed instructions to get rid of it. I couldn't use chainfires triangle away so I followed some more complicated instructions. I don't remember the link but I could probably find it - although anyone else probably can too.
Sent from my GT-p511x
Click to expand...
Click to collapse
^^^
This is correct. Actually, using Odin or Heimdall to install a non-stock kernel is exactly what trips the flash counter, and throws up the warning screen. Using Odin or Heimdall to install a "stock" kernel will also clear the warning screen, but it will not reset the flash counter. To reset the flash counter to zero, you either need to use a USB jig, or use Chainfire's app. The warning screen has nothing to do with whether the non-stock kernel is built for the I777 or the I9100, or whether it was a zedomax kernel. Any custom kernel will produce the exact same results.