I used this on my SGS2 running an Alpha CM9 ICS build by codeworkx and it reset the binary download counter and removed the triangle on device boot. From what I have seen, the insecure kernel triangle is not an issue on this device (as far as I know). I was just wondering if anyone has tried TriangleAway on this device as here have been a couple alpha dev ICS builds so far, as the application only works on ICS builds.
Should I take the risk if no one else has yet? is it even possible that it could work on our device, apparently it works on a version of the Galaxy Note now, but was only intended to work on the SHS II i9100. I'm not going to risk it if someone believes that it is just not compatible due to differences in hardware, but from what I have read, it is possible to flash some I9100 builds on this device by modifying things. Apparently it does mess with your bootloader, so it could be risky.
Let me know if anyone has any information on this, or any interest.
What's the point of resetting your flash counter anyway? Carriers don't even look at that when you send your device in for warranty. And if you are worried about it, just flash another device's TAR and completely brick the phone. They'll never know
There is no real point, just for the sake of curiosity,
Worked great on my i9100
Felt weird not seeing that triangle that had been there from day 1
Edit: i was on a cm9 alpha from codeworkx too
Sent from my GT-I9100 using XDA
Related
Sorry I am a noob and this may be a dumb question but.. I am trying to root a galaxy S2. I have found the thread about rooting however, this forum won't allow me to post my question there so I am putting it here.
This thread http://forum.xda-developers.com/showthread.php?t=1125414 talks about installing an insecure kernel, then back to the secure kernel and links to another thread with the kernels. The problem is, there are soooooo many kernels to choose from. Which do I choose?
My phone is i9100BKEU I am afraid to attempt this as I don't want to turn my phone into a brick by using the wrong kernels. And, to flash back to the original kernel, this seems even more important to get the right one.
I found the kernels here...
http://forum.xda-developers.com/showthread.php?t=1101671
Can anyone point me to the correct kernel or, an easier method? My phone is new and just arrived from expansis today and has the latest gingerbread on it.
Z4root
I don't own your phone but you could try this: Attachment included
Just install on your phone and run
i have followed this tutorial
http://androidadvices.com/how-to-root-samsung-galaxy-s-2-i9100-tutorial/4/
and my phone rooted without any problems.
I have the KG6 kernel and wasn't able to find it anywhere.
But I installed Lightning Rom (wit different kernel) and it worked fine.
So I think any kernel close to yours should work?
vrekeno said:
I have the KG6 kernel and wasn't able to find it anywhere.
But I installed Lightning Rom (wit different kernel) and it worked fine.
So I think any kernel close to yours should work?
Click to expand...
Click to collapse
That is what I am most afraid of is not having the exact same kernel. I have read that it isn't so important to have the same exact kernel when installing the insecure kernel, but it is more important when your finished and install the secure kernel back.
Are there any experts on this topic that can explain how important it is to install the exact same secure kernel after rooting? How close does it need to be?
I am having the exact same issue. Dunno whether to use a KE7 or a KF1 or even KF3 kernel, because the guys who went to the trouble of creating the insecure kernels for the community (Odia & Chainfire) probably didn't think moronic luddites such as myself would be wanting to use them, so it's not entirely clear.
My firmware:
PDA:KF3
PHONE: KE7
CDC: KF1 (O2I)
If anyone can clear this up for me, a lowly noob, my gratitude will know no bounds.
Well.. This is same tutorial what I tried and that superoneclick always crashes..
But thanks a lot guys, I think I will first try that gingerbreak, unless someone else has better ideas?
Well.. I have KDD and theres even a youtube video of how to root KDD version, but still can't cause the superone click keeps crashing. its so frustrating! I really want root my phone..
Tommihg said:
Well.. This is same tutorial what I tried and that superoneclick always crashes..
But thanks a lot guys, I think I will first try that gingerbreak, unless someone else has better ideas?
Click to expand...
Click to collapse
From what I've read [and I've been researching how to root my phone for the last eight hours without joy], Gingerbreak doesn't work with Galaxy S2. It worked on the pre-production models (that's why there's videos of it on youtube) but any phone that you or I have won't be compatible. The only way around is ODIN & an insecure kernel, but as I and the original poster both noted, figuring out which kernel to use is really confusing for noobs like myself.
Hmm.. well.. I have same problem. Maybe dev. Can help us noobs here?
Sent from my GT-I9100 using XDA App
I just PM'ed Odia, and he was very helpful. The kernel you need is the one listed under PDA in Kies "Firmware Version" info panel. Just download the corresponding kernel and it should work... My only problem is that ODIN3 is now crashing on me! Out of the frying pan...
I have same problem. I think I will first try that gingerbreak, someone else has better ideas?
I have search the infuse threads and cant find anything on this subject. I just got a infuse and im coming from a captivate. My question is, if im on stock froyo do i have to have gingerbread bootloaders to odin flash one of leaked gingerbread builds or can i just odin flash a build straight from froyo? I would appreciate the help.
the last 4 leaks contain bootloaders. also the Rogers based custom kernels have a rainbow fix and work with the froyo bootloaders.
Thanks for the help. I did a little more research and got everything i need. Im used to flashing the hell out of my captivate and i didn't want to jump right in with the infuse and brick it. I was just trying to be cautious. I bricked my captivate the first week i had it and didnt want a repeat of that.
tmease1 said:
Thanks for the help. I did a little more research and got everything i need. Im used to flashing the hell out of my captivate and i didn't want to jump right in with the infuse and brick it. I was just trying to be cautious. I bricked my captivate the first week i had it and didnt want a repeat of that.
Click to expand...
Click to collapse
you wont brick it. maybe get boot loops but this phone is practically unbrickable. the captivate had bricking issues because people like deisgngears thought it was a good idea do flash sbl.bin through cwm and not package it with boot.bin(3button fix). samsung is also responsible because many of the firmwares they leaked contained sbl.bin and not boot.bin(i9010 armani captivate). they also had several bootloader builds that for no apparent reason were not compatible. the infuse doesnt have those factors. also the bootloaders seem to be signed to the device which prevented us from flashing rogers bootloaders. from what i gathered from threads by gtg there may be a bootloader backup system on a spare partition that prevents bad flashes and restores the last bootloaders if the wrong bootloaders get flashed.
That is extremely helpful. I have read that there alot of issues with all of the leaks so i dont know if I will do anything with it or not. I like to flash roms but i also like a stable phone. The way i am ill end up flashing something anyway and just deal with whatever the problem is. Thanks again
I got my wife the Samsung galaxy plus 7 for her birthday today and it's saying that there is an update for it. I'm not sure if its ok to except the update or not, because eventually I would like to get it rooted. Also, I read that in order to get root, you must first update the kies. Sorry for possible a simple question to some, but what are kies?
Thanks,
Sent from my AT100 using Tapatalk
bluezr1 said:
I got my wife the Samsung galaxy plus 7 for her birthday today and it's saying that there is an update for it. I'm not sure if its ok to except the update or not, because eventually I would like to get it rooted. Also, I read that in order to get root, you must first update the kies. Sorry for possible a simple question to some, but what are kies?
Thanks,
Sent from my AT100 using Tapatalk
Click to expand...
Click to collapse
hey it is safer than safe to update it is infact encouraged to update at all times as updates are made to fix manufacturer bugs and/or issues that may be present on the device weather you have noticed them or not they will be present for sure like the SOD issue Screen of death a bug that makes your device shut down and/or reboot randomly with no control...this is a manufacturer bug and an update will be required to remove the issue from the device. so basically you will need to update on the device and with the Samsung kies (kies is a software that you will need to download from Samsung just search it on Google to learn more and to download kies is universal to all devices supplied by Samsung and i would also like to recommend not rooting your device until you are experienced enough to repair any damages you may encounter on the way if you do lol.
the purpose of root is to gain more advanced control of your device and/or install a custom ROM on the device (but we don't have any custom roms as of yet as Samsung will not release the sauce code) if you need any help and i will help you. if this post help you please press thanks button
jmar8124 said:
hey it is safer than safe to update it is infact encouraged to update at all times as updates are made to fix manufacturer bugs and/or issues that may be present on the device weather you have noticed them or not they will be present for sure like the SOD issue Screen of death a bug that makes your device shut down and/or reboot randomly with no control...this is a manufacturer bug and an update will be required to remove the issue from the device. so basically you will need to update on the device and with the Samsung kies (kies is a software that you will need to download from Samsung just search it on Google to learn more and to download kies is universal to all devices supplied by Samsung and i would also like to recommend not rooting your device until you are experienced enough to repair any damages you may encounter on the way if you do lol.
the purpose of root is to gain more advanced control of your device and/or install a custom ROM on the device (but we don't have any custom roms as of yet as Samsung will not release the sauce code) if you need any help and i will help you. if this post help you please press thanks button
Click to expand...
Click to collapse
I've rooted many devices and understand the consequences that comes with it. What I was wondering is, if I except the update will I loose the option of gaining root.
I had this happen to me before when the wife decided (I was still in bed) to accept the update to her evo. So while she had to sit back watching me change rom's, making backups, she was stuck running the stock os for a while. I do understand that at present there aren't any rom's, but I would still like to use TB, ad blocker and everything else that comes with having a rooted device.
Thanks for your reply,
Sent from my PC36100 using Tapatalk
The way that Garyd9 made the root script; by pushing it via recovery in a chroot environment; it should be safe to accept the updates. Unless Samsung changes the base recovery gary9d's method should always work.
bluezr1 said:
I've rooted many devices and understand the consequences that comes with it. What I was wondering is, if I except the update will I loose the option of gaining root.
I had this happen to me before when the wife decided (I was still in bed) to accept the update to her evo. So while she had to sit back watching me change rom's, making backups, she was stuck running the stock os for a while. I do understand that at present there aren't any rom's, but I would still like to use TB, ad blocker and everything else that comes with having a rooted device.
Thanks for your reply,
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
yes you can still get root i have the latest update by kies and i have rooted meany times on the device after messing it up LOL. i would recommend using the root and clock work mod combo its stated not stable but i have used it for moths and have backed up 100s of times and restored lol
Hello all,
I've searched all over XDA and Google, to give me definitive answer about issue i am about to raise, i rooted and put custom roms on all my previous samsung/htc devices, and WAS about to do the same for my Note 3 (its a beastly device, and doesnt need modifications, however it has been a routine for me to root and put custom roms into any devices that i've used)
Now the issue is this:
Yes, i've read about KNOX security system that Samsung has implemented, which would trip a counter and supposedly locked the bootloader of the phone, i've also read that due to the e-fuse that has been implemented, my Note 3 internals could be damaged due to it (?), and also i wouldnt be able to go back to the old version/bootloader as it will be parmanently locked by Samsung if i flash using Odin.
Do take note..that my Note 3 is not under warranty..so if KNOX triggers, it doesnt matter for me , as i wont be going to my local phone shop or official Samsung Officials (there isnt one here in my country) if anything would happen to my device. However i do need to know if its gonna mess with my device due to the e-fuse.
My questions are these..
1) If i root it, using CF's method as i usually do..and will definately put Custom Rom in it...and that will trigger KNOX for sure..will it destroy the internals? say the MOBO..and the phone will be rendered useless and become an expensive paperweight (i dont have warranty, so no replacements)
2) If i use for e.g Omega Rom which released two versions, one, with 4.3 JB and one, with 4.4 KitKat...will i be able to go back and forth for e.g 4.4 to 4.3 as well as jumping to different custom roms with diffrent Android versions?! as i usually do with me previous devices
Thanks and i will definately delete this thread once i'm fully convinced that rooting , putting roms should be avoided or ''Since you dont care about tripping knox, go ahead and do it as ur previous devices'' kinda answer..
Truly Sorry if you guys come across this question already..i've searched for it and come to no avail.. this is my last resort. Thnks XDA and everyone.:good:
qilrfn said:
My questions are these..
1) If i root it, using CF's method as i usually do..and will definately put Custom Rom in it...and that will trigger KNOX for sure..will it destroy the internals? say the MOBO..and the phone will be rendered useless and become an expensive paperweight (i dont have warranty, so no replacements)
2) If i use for e.g Omega Rom which released two versions, one, with 4.3 JB and one, with 4.4 KitKat...will i be able to go back and forth for e.g 4.4 to 4.3 as well as jumping to different custom roms with diffrent Android versions?! as i usually do with me previous devices
Thanks and i will definately delete this thread once i'm fully convinced that rooting , putting roms should be avoided or ''Since you dont care about tripping knox, go ahead and do it as ur previous devices'' kinda answer..
Truly Sorry if you guys come across this question already..i've searched for it and come to no avail.. this is my last resort. Thnks XDA and everyone.:good:
Click to expand...
Click to collapse
Firstly wrong section - should go to Q&A
1) -- Well you can mess up if you don't follow the right methods (not hard)
2) you can only be on one, if you use 4.3 BL you can't use 4.4 and vice versa... once you go to 4.4 you cannot downgrade back to 4.3 unless you have an N900w8
Generally, rooting/custom ROM's won't hurt your device, just make sure you have the right ROM/Kernel and make the proper backups if needed.
Disable Reactivation Lock, and read about backing up your EFS and how to get out of it if it goes mad (which it sometimes does at random)
I think Radicalisto didn't make it clear enough: I'm not aware of tripped Knox flag affecting anything else on the phone except for warranty and inability to use Knox software. Any type of phone issues would probably be due to user error, or loaded software, not the flag itself.
radicalisto said:
Firstly wrong section - should go to Q&A
1) -- Well you can mess up if you don't follow the right methods (not hard)
2) you can only be on one, if you use 4.3 BL you can't use 4.4 and vice versa... once you go to 4.4 you cannot downgrade back to 4.3 unless you have an N900w8
Generally, rooting/custom ROM's won't hurt your device, just make sure you have the right ROM/Kernel and make the proper backups if needed.
Disable Reactivation Lock, and read about backing up your EFS and how to get out of it if it goes mad (which it sometimes does at random)
Click to expand...
Click to collapse
Thanks for answering first of all..will defo hit the thnx button..
for the 1) i always make sure i read the instructions and follow steps..no problem there..
2) this one tho..is a bit weird for me..i was able to do it on my note 2..going back and forth 4.3 to 4.1.2 cus i found the 4.1.2 more stable..i guess for note 3 i cant do that anymore? even if use custom roms to up/downgrade?
thnx for ur time..and will take ur advice next time on posting it at the q and a section (still learning)
ON 4.3 you once you go to MJ7 Bootloader you cannot downgrade -- however you can go to ML and MK bootloaders and go back to MJ7 again.
For some reason Samsung blocked a downgrade to 4.3 from 4.4 (as the Note shipped with 4.3 no logical reason to allow 4.2 imo) - but if you choose to move to 4.4. bootloader do be aware it can be buggy on some devices (NEE region also Hong Kong notes have issues) - If you have a read around you will see the issues people are having and not having with stock 4.4.
There's plenty of ROMs for both bootloaders CM works on both and most of the Stock based ROM dev's have moved up to the newest NB* Bootloader from NA* - I flashed 4.4 day it leaked (the next hour to be precise and I have had no issues)
qilrfn said:
Thanks for answering first of all..will defo hit the thnx button..
for the 1) i always make sure i read the instructions and follow steps..no problem there..
2) this one tho..is a bit weird for me..i was able to do it on my note 2..going back and forth 4.3 to 4.1.2 cus i found the 4.1.2 more stable..i guess for note 3 i cant do that anymore? even if use custom roms to up/downgrade?
thnx for ur time..and will take ur advice next time on posting it at the q and a section (still learning)
Click to expand...
Click to collapse
since note 3 came with 4.3 and currently latest stock is 4.4.2. even if u wanna go back to 4.3 from what i read around it is not possible. There are alot of aosp roms and stock rooted roms with all kinds of kernel build for both stock and aosp. Im sure if u were to follow the instructions given and do it diligently surely nthg goes wrong unless u overclock ur phone too high or flashing stuff which weren't meant for ur specific device then nthg to be afraid of. I sure glad i went ahead and root. Coz to me knox is a totally BS. all down to ur own preference. u like it u root it u use it. best is to keep reading different threads.
Sent from my SM-N9005 using XDA Premium 4 mobile app
radicalisto said:
ON 4.3 you once you go to MJ7 Bootloader you cannot downgrade -- however you can go to ML and MK bootloaders and go back to MJ7 again.
For some reason Samsung blocked a downgrade to 4.3 from 4.4 (as the Note shipped with 4.3 no logical reason to allow 4.2 imo) - but if you choose to move to 4.4. bootloader do be aware it can be buggy on some devices (NEE region also Hong Kong notes have issues) - If you have a read around you will see the issues people are having and not having with stock 4.4.
There's plenty of ROMs for both bootloaders CM works on both and most of the Stock based ROM dev's have moved up to the newest NB* Bootloader from NA* - I flashed 4.4 day it leaked (the next hour to be precise and I have had no issues)
Click to expand...
Click to collapse
Okay..so i would only flash 4.4 roms when Im really really convinced that its time for KitKat..but as of right now, i can only play around with 4.3 roms..ok..understood. You've cleared my doubts man, thanks a bunch and i guess its time to root and flash.
pete4k said:
I think Radicalisto didn't make it clear enough: I'm not aware of tripped Knox flag affecting anything else on the phone except for warranty and inability to use Knox software. Any type of phone issues would probably be due to user error, or loaded software, not the flag itself.
Click to expand...
Click to collapse
I did read somewhere, the e-fuse is like an internal bomb..if i flag it, some sort of ''internal parts destroyer'' would be unleashed and mess up my device. I guess its just a rumour...hopefully.
qilrfn said:
I did read somewhere, the e-fuse is like an internal bomb..if i flag it, some sort of ''internal parts destroyer'' would be unleashed and mess up my device. I guess its just a rumour...hopefully.
Click to expand...
Click to collapse
If it's not humour, there's gonna be a lot of angry Note owners here on XDA -- Some tripped KNOX accidently lol - I wouldn't worry too much in all honesty.
I'm sure using cf root trips knox
Sent from my SM-N9005 using xda app-developers app
An e-fuse is just a silicon bridge on the processor that gets burnt out. Once you burn the bridge it can't revert back.
This is technically damaging the internal hardware BUT this is due to Samsung software doing this so I don't see how they can claim we have damaged the hardware.... There should be no other problems resulting from this....
First of all, many people already claim their phones had Knox flag reset to zero by Samsung service centers. Either they're all lying (why?), there are more than one e-fuse inside and Samsung can simply reset software to ignore burned fuse and check next one, or the whole e-fuse story is made up and not true. Personally I lean towards the last possibility, for 2 reasons: e-fuse is permanent so couldn't be reset and if they're using multiple e-fuses then it is not more secure than encrypted software code and also possibly e-fuse could be defeated from tripping: I believe e-fuse needs higher than normal voltage to be burned out (otherwise it could burn accidentally) and that voltage is probably coming on separate rail, I wonder what would happen if one would either cut this high voltage or short it out, just during flag tripping operations.
Secondly many people tripped their Knox flags already, if there was some side effects, we would know about it already.
Hi all...
OK, so I've rooted and ROMed a few phones in the past, and I generally know what I'm doing. However, I think I may have gotten a little bit overconfident this time and not done enough research...
I had a friend give me one of these phones and I decided that before making it my daily driver, I was going to install CM11. The phone was given to me unrooted with the stock 4.3 ROM. So, I found a guide to root the 4.3 version of the phone w/o triggering the warranty killbit, and that all went well. Once rooted, I decided to use Clockwork ROM Manager to throw CM11 on it. I installed CM and, without giving it a second thought, told it to flash the latest CM recovery (apparently my root method had come with TWRP). When I rebooted, I expected to see the nice recovery screen I was used to, but instead I was informed that I needed to take my phone to the nearest Verizon store and have them restore it (no thanks). I can, however, still get in to the Odin downloader, but this is uncharted territory for me. Assuming everything is OK with my firmware, what is the best/fastest way to recover from this point? I think I understand how Odin works, but I don't know much about it. Can I use Odin to flash the latest TWRP and fix it that way? Would it be better to try and flash completely back to stock and start over? If I'm forced to use Odin anyway, can I just flash CM11 from there? I have no idea what to do...
I would greatly appreciate any guidance anyone of you ROM wizards is willing to part with...
Fix with this:
http://forum.xda-developers.com/showthread.php?t=2586319
Then read all of this, no AOSP on 4.3:
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my HTC6525LVW using Tapatalk