Related
Hi all, proper random but i went out about a month ago now, got in a proper mess and randomly woke up with someones phone in my pocket, its a samsung galaxy s i9000, wasnt sure whether it was a mates or not so announced it on my facebook seeing if they would come forward, but no one has, so i must have found it, im not the type to steel, promise! i have an iphone 4 so ive taken it me being a complete w*nker and taking it from someone as an option. i was thinking may as well try and put it to use rather than just chucking it, its on a 3 network, but its not got sim lock, its phone locked, just asking for a password to get into it, ive spent an hour or so trying to find out if theres a way but havent yet come across a way, if there is one. Help would be appreciated
I have the same phone dude its simple,search threw here (in the i9000 section ,first you'll need to root it with Odin,after you have root go to market and download Samsung galaxy unlock and follow the steps and your done.
*very important once your rooted make a copy of your efs folder(contains your imei number)it can/will change depending on if you flash roms.*
Good luck
Sent from my GT-P6210 using Tapatalk 2
Since I did not spend much time unrooted or on the stock ROM, I have a few questions:
If you trip Knox by rooting does it actually block anything in Android, or is it just a nag on the boot/odin screen?
I know there is a private mode and so forth, does private mode break as soon as you trip Knox?
If you go back to completely stock does anything that is broken begin to work again, and only leave you with the nag screen on boot?
Basically I am interested in what exactly tripping Knox does other than just incrementing the counter in Download Mode.
miked63017 said:
Since I did not spend much time unrooted or on the stock ROM, I have a few questions:
If you trip Knox by rooting does it actually block anything in Android, or is it just a nag on the boot/odin screen?
I know there is a private mode and so forth, does private mode break as soon as you trip Knox?
If you go back to completely stock does anything that is broken begin to work again, and only leave you with the nag screen on boot?
Basically I am interested in what exactly tripping Knox does other than just incrementing the counter in Download Mode.
Click to expand...
Click to collapse
Well, on the S3 it prevented using the Samsung All-Share Cast Hub unless you went back to stock and reset the flash counter. Even worse, as far as I know nobody has managed to work around that. Though nobody has any idea why Samsung checks the flash counter and blocks wifi screen mirroring if the Knox flag is tripped.
1. OTA's will never come through the same way again. The NEW Knox is implemented even more now into Lollipop. You will always be able to use Kies after removing root and restoring the original recovery image, but trying to OTA will come up short after it's downloaded from the server. I even tried OTA Snatcher. I finally went ahead and took Garwyn's tar ball, then TDunham's DeOdex.
2. Sprint doesn't care as far as warranty work is concerned. Only one guy at the store even knows what root is. BestBuy LOVES root and they know Rompnit's work on MOAR. The tech played with my phone back on NE5 2.2 for like 15 minutes.
3. Towelroots are no more. Not even the "Wrong Kernel" trick for 4.4.4.
4. It operates normal when put back to a factory setting. No apps crash because of root, although I am NOT sure of the Allshare issue.
5. Those private mode and S-health issues are no more. You DO still have to do the Sd Card trick to get media RW capabilities.
For Lollipop, it's worth it. Especially if you stay on an Odexed version. MAN it's blazing fast. I don't know what else to say, Mike. You know more about these phones than I do.
nl3142 said:
Well, on the S3 it prevented using the Samsung All-Share Cast Hub unless you went back to stock and reset the flash counter. Even worse, as far as I know nobody has managed to work around that. Though nobody has any idea why Samsung checks the flash counter and blocks wifi screen mirroring if the Knox flag is tripped.
Click to expand...
Click to collapse
jpgranger said:
1. OTA's will never come through the same way again. The NEW Knox is implemented even more now into Lollipop. You will always be able to use Kies after removing root and restoring the original recovery image, but trying to OTA will come up short after it's downloaded from the server. I even tried OTA Snatcher. I finally went ahead and took Garwyn's tar ball, then TDunham's DeOdex.
2. Sprint doesn't care as far as warranty work is concerned. Only one guy at the store even knows what root is. BestBuy LOVES root and they know Rompnit's work on MOAR. The tech played with my phone back on NE5 2.2 for like 15 minutes.
3. Towelroots are no more. Not even the "Wrong Kernel" trick for 4.4.4.
4. It operates normal when put back to a factory setting. No apps crash because of root, although I am NOT sure of the Allshare issue.
5. Those private mode and S-health issues are no more. You DO still have to do the Sd Card trick to get media RW capabilities.
For Lollipop, it's worth it. Especially if you stay on an Odexed version. MAN it's blazing fast. I don't know what else to say, Mike. You know more about these phones than I do.
Click to expand...
Click to collapse
Well the real reason for me asking is because I have slowly been trying to learn assembly, specifically on the arm platform. So the other day I dropped aboot.mbn in IDA and disassembled it, AFAIK aboot is what provides the phone side interface for Odin(Download Mode). I found a few instructions that look interesting, basically they say this:
Code:
if knoxCounter == 0
then
do barely anything and display a zero indicating your warranty is fine
else
do a bunch of stuff and display a 1 indicating your warranty is void
Obviously that isnt the code word for word lol
So my thought was to change the ==(equals(BEQ)) to !=(not equals(BNE)), which could at least in theory make everything that comes after the bootloader think Knox is fine because the bootloader skipped a big chunk of instructions that would have taken place if it saw you tripped it, and instead ran the function that runs when its not tripped.
So I made my change in a hex editor to a temporary file, disassembled it in IDA as well, everything looked legit. I went to flash it in odin by injecting it into a valid OA6 tarball and got Auth failed message. My first thought was our BL is unlocked why am I not allowed to flash it? So I rebooted and flashed it to the proper partition using dd, rebooted to download mode and nothing. After rebooting I then dumped the aboot partition with dd, opened it up in a hex editor and its like my change had never been made? This is about as far as I went and left it alone at this point.
So I am on the fence as to whether or not I should even bother pursuing this any further. At first my thoughts were - I don't like the fact that my own device nags me about warranty so I want to change it. But now its more like - WTF Samsung and Sprint, I though my BL was unlocked, what if I want to plop Linux on this device after I am done using it as a phone?
I don't know if anybody has any knowledge as to why I can't flash my custom aboot partition, maybe there is some signature validation along the way, even though our BL is supposedly unlocked? I thought the sig checks only happened on locked phones.
Its great to be able to browse the code on a theoretical level, but I really want to flash it and play . The other half of me thinks its not worth wasting your time on it, go practice arm assembly on your raspberry pi.
Have you consulted Chainfire? There's a thread floating around where he mentioned the exact same thing. Of course, I think Sammy knew this going into development. And Knox looks different on Lollipop.
Hi Everyone,
I remember back when I had the Note 2. You could reset the counter that gets triggered in Download Mode. Does the Galaxy S7 have a similar counter once I root the phone and install custom ROMS? And is there a way to reset it?
I'm getting the SM-G930F from my brother today. And I'm looking forward to it, but rooting the phone & using Xposed Framework & AdAway are priorities for me on any phone. It has two years warranty, so if anything happens to the phone I want to be able to return it.
Also after 1 year I can upgrade the phone to whatever I want on his plan, so I'll likely get the Galaxy S8. Would be great if someone can answer me today before I root it.
I'm going to use CF Autoroot, then install the latest TWRP. Do a full backup using TWRP. Copy that to the PC, before I start experimenting with different ROMS & mods.
Also another quick question, why do I not see any Android 7 stock Android ROMS or CM based ROMS around? That's surprising. Are the developers waiting for Google to release the source code? When is that expected?
Thanks in advance for all the replies.
Blackfyre said:
Hi Everyone,
I remember back when I had the Note 2. You could reset the counter that gets triggered in Download Mode. Does the Galaxy S7 have a similar counter once I root the phone and install custom ROMS? And is there a way to reset it?
I'm getting the SM-G930F from my brother today. And I'm looking forward to it, but rooting the phone & using Xposed Framework & AdAway are priorities for me on any phone. It has two years warranty, so if anything happens to the phone I want to be able to return it.
Also after 1 year I can upgrade the phone to whatever I want on his plan, so I'll likely get the Galaxy S8. Would be great if someone can answer me today before I root it.
I'm going to use CF Autoroot, then install the latest TWRP. Do a full backup using TWRP. Copy that to the PC, before I start experimenting with different ROMS & mods.
Also another quick question, why do I not see any Android 7 stock Android ROMS or CM based ROMS around? That's surprising. Are the developers waiting for Google to release the source code? When is that expected?
Thanks in advance for all the replies.
Click to expand...
Click to collapse
Installing other custom ROM will trigger know and you will lose warranty. I don't see any reason to install custom ROM at least at the moment. There is a root method that claims to not trigger knox but I haven't tried it.
Sent from my SM-G930F using Tapatalk
Try the root method that people relate that doesn't trigger knox..
And there's a few roms to nougat, no custom kernel for now.
Enviado do meu SM-G930F através de Tapatalk
Any root method for the G930F will trip KNOX and void warranty (Afaik it is other models that can be rooted without tripping, unless I've missed something lately)
Flashing anything custom will also trip KNOX
There is no way to reset the KNOX counter
If you trip it, that is permanent
If knox is tripped, will they also refuse to do any hardware repairs? For example, after 2 months my home button doesn't work anymore.
destz0r said:
If knox is tripped, will they also refuse to do any hardware repairs? For example, after 2 months my home button doesn't work anymore.
Click to expand...
Click to collapse
All, warranty is warranty, it will be refused
In some cases people get lucky and Samsung repair anyway, maybe because they didn't check, but if KNOX is tripped, all repairs will cost you money with no warranty
destz0r said:
If knox is tripped, will they also refuse to do any hardware repairs? For example, after 2 months my home button doesn't work anymore.
Click to expand...
Click to collapse
In Europe, Samsung has to repair the equipment even with Knox tripped, as long as it was not root that damaged the hardware.
I had to send my phone to Samsung, because i screwed up the phone with Xposed and Samsung repaired it without charging anything.
Hansoliv said:
In Europe, Samsung has to repair the equipment even with Knox tripped, as long as it was not root that damaged the hardware.
I had to send my phone to Samsung, because i screwed up the phone with Xposed and Samsung repaired it without charging anything.
Click to expand...
Click to collapse
Thanks alot!
Hansoliv said:
In Europe, Samsung has to repair the equipment even with Knox tripped, as long as it was not root that damaged the hardware.
I had to send my phone to Samsung, because i screwed up the phone with Xposed and Samsung repaired it without charging anything.
Click to expand...
Click to collapse
This has been the discussion since my S5 days, they don't often honour it even in Europe, even quoting the piece of law stating they have to
Only a lucky few get it done without a problem
*Detection* said:
This has been the discussion since my S5 days, they don't often honour it even in Europe, even quoting the piece of law stating they have to
Only a lucky few get it done without a problem
Click to expand...
Click to collapse
Oops, looks like i got lucky.
Will not try and root again so soon.
Alright, so I've done some research on this subject.
Most root or ROMs will "Fry the knox circuit." Basically, what that is, is a secure, totally private fuse that your phone has, which is like 2 nanometers small chip in you phone's mother board. It's an absolutely tiny fuse that protects the ADMIN section of you phone. Currently most, if all known methods, of root will trip it. So, as stupid as it sounds, I'd say "Buy a USB killer." Which is a USB device meant to test protection circuits. And if you phone is already dead to some point, if they can't power it up, they may just say "**** it" and do a warranty replacement.
Otherwise, unless they can tell, they'll just swap it for a preowned model if they can't tell you ****ed with it.
Honestly, if you have insurance on it, smash it with a hammer. If not, say it started smoking while charging and make sure it won't charge, Apple is scared ****less towards possible fire damage and samsung just had that Note 7 thing
Hi I've been rooting phones for over 10 years now but the past couple of devices I haven't due to it tripping knox etc but I miss a few things with root and looking for peoples opinions
I love having adaway and been able to fully uninstall apps I don't use
Is there much of an improvement on battery life as I have the exynos version :crying:
Also an app i haven't had chance to use is viper4android is it as good as people say and does it actually boot volume on bluetooth audio without distorting etc as that would be my main use for it
Also what exactly does tripping know destroy? I've read it affects Samsung pay and Samsung pass is there anything else
And has anyone had problems selling there device afterwards from tripping know (mainly in the uk) as I change devices quite a bit and sell them on lol
Thanks
You can use adguard if you don't want to root. I haven't bothered rooting anything for a few years now. It doesn't deliver any additional must have features i can't live without, unlike it used to.
Same boat, rooting for decades. Yet it seems a bit too immature this time on this device.
Also got the exynos junk (Iknew before getting it, but free phone from work).
I decided to go without for now.
Same here - decided to go on without root. The features I miss are - firewall (need to try knox firewall though), direct time sync (minor), some console commands to manage files, titanium backup - this is a major issue, so I can't backup OTP apps etc.
Don't root your device since that requires you unlocking bootloader to root and doing that triggers knock safety thing so it destroys knox permanently and then apps such as Samsung pay, samsung pass, secret folder, encryption and few more that requires knox to work will be unavailable, since knox chip is no longer functioning. Also warranty would be voided if you got 2 years warranty.
So if you plan to use samsung pay or any of other apps later on then avoid rooting and touching bootloader.
Jake.S said:
Don't root your device since that requires you unlocking bootloader to root and doing that triggers knock safety thing so it destroys knox permanently and then apps such as Samsung pay, samsung pass, secret folder, encryption and few more that requires knox to work will be unavailable, since knox chip is no longer functioning. Also warranty would be voided if you got 2 years warranty.
So if you plan to use samsung pay or any of other apps later on then avoid rooting and touching bootloader.
Click to expand...
Click to collapse
i dont know about usa and other countries, but in europe ur warranty won't be void if knox is tripped (afaik)
Still can't do without root unless there a way to block ads while using a vpn of my choice and control a firewall. Have my Note two days now after waiting 3 weeks for it to ship from Hong Kong and first thing I did was to root.
destz0r said:
i dont know about usa and other countries, but in europe ur warranty won't be void if knox is tripped (afaik)
Click to expand...
Click to collapse
Well actually to get it tripped requires bootloader unlock for root and that would void your warranty in Europe. So id knox says 0x0 it also voids warranty
Only those that care about Samsung's proprietary Knox and it's associated bloat should worry about knox being tripped. Only thing I'd probably care about is 3rd party banking apps that might not work with patch hide. If that still works or not unsure.
rooting my n9860 asap. finally just got the oem option to show up. last phone i had was a note 8 not unlockable...and had to keep it for too long, wanting root the entire time. so i'm not missing the chance to do it now. why? to try custom rom, get all bloats/google/samsung apps off the phone and stop looking at system settings that i cannot change(top reason), learn about android / do some dev on it, test root apps made by community(2nd best reason), get a recovery installed, nethunter, call recording, toolbox, run my fav firewall. probably more reasons that im not thinking about right now
mgagnequebec said:
rooting my n9860 asap. finally just got the oem option to show up. last phone i had was a note 8 not unlockable...and had to keep it for too long, wanting root the entire time. so i'm not missing the chance to do it now. why? to try custom rom, get all bloats/google/samsung apps off the phone and stop looking at system settings that i cannot change(top reason), learn about android / do some dev on it, test root apps made by community(2nd best reason), get a recovery installed, nethunter, call recording, toolbox, run my fav firewall. probably more reasons that im not thinking about right now
Click to expand...
Click to collapse
im considering rooting my N9810, but im wondering if I will still receive OTA updates then? or do i have to manually flash the update with each ota?
destz0r said:
im considering rooting my N9810, but im wondering if I will still receive OTA updates then? or do i have to manually flash the update with each ota?
Click to expand...
Click to collapse
You wont get OTA after rooting, since rooting requires you to unlock bootloader so then OTA won't work. Also KNOX won't function permanently once this is done too.
So think if you going to use samsung apps like samsung pay and such then avoid touching bootloader and rooting.
mgagnequebec said:
rooting my n9860 asap. finally just got the oem option to show up. last phone i had was a note 8 not unlockable...and had to keep it for too long, wanting root the entire time. so i'm not missing the chance to do it now. why? to try custom rom, get all bloats/google/samsung apps off the phone and stop looking at system settings that i cannot change(top reason), learn about android / do some dev on it, test root apps made by community(2nd best reason), get a recovery installed, nethunter, call recording, toolbox, run my fav firewall. probably more reasons that im not thinking about right now
Click to expand...
Click to collapse
Is one of them being able to tether (hot spot) without the carrier detecting it
cenwesi said:
Is one of them being able to tether (hot spot) without the carrier detecting it
Click to expand...
Click to collapse
I doubt it but I never tried it before tbh. I guess i should say that i might not be a good example to follow when it comes to updates. i almost never do them. because it always was a compromise one have to make if wanting to root. at least from my experience. like, keep your firmware version low or you loose the ability to root. but gain security patches. i chose my side of the fence long ago hehe
I have Samsung pass that appears and then refuses to work because it says my phone is rooted.
I have put custom rom one I android 9 and because of bugs I returned to combination android 8 for my samsung a520w because it is the phones best option.
I am stuck with samsung pass and Knox that hampers and returns to try to fill passwords but then stops midway to tell me phone is rooted.
I have tried all sorts of ways but none work.
I tried to fix it by changing samsung pass to samsung.jpk instead of apk and flushing the cache while trying to make like new but cannot change name without root access.
Is there any way to return my phone to it's original state since I have never rooted it.
Did you unlock the bootloader?
If so you blew the efuse.
The only way to reverse this is to replace the mobo.
Sounds like you've triggered the Knox efuse by unlocking the bootloader and installing a custom ROM. Nothing to do about that...
I changed the rom different ones and everything worked fine for samsung pass in the one ui rom posted online here, the Korean one I from this thread that I installed, but to many bugs, and it thought my phone was a A7, but everything worked like new, just too many bugs, so i side loaded the old rom which has all samsung pass, it's a combined rom with and for my phone a520w.
What do you mean by mobo?
Do you mean new phone...
But i know that since i managed to get it all normal for the one I, me and that it can be fixed.
We even tried magisk and ended up with frp block, had to redo allover, tried also to delete samsung pass which cannot since do not have root access, so there must be some solution for this,
But you are right about boot lock, but how come it is saying rooted when I never rooted.
Ever since I put lineage 18.1, it is like samsung did not like me putting on a custom rom.
blackhawk said:
Did you unlock the bootloader?
If so you blew the efuse.
The only way to reverse this is to replace the mobo.
Click to expand...
Click to collapse
Claudejoel1967 said:
I changed the rom different ones and everything worked fine for samsung pass in the one ui rom posted online here, the Korean one I from this thread that I installed, but to many bugs, and it thought my phone was a A7, but everything worked like new, just too many bugs, so i side loaded the old rom which has all samsung pass, it's a combined rom with and for my phone a520w.
What do you mean by mobo?
Do you mean new phone...
But i know that since i managed to get it all normal for the one I, me and that it can be fixed.
We even tried magisk and ended up with frp block, had to redo allover, tried also to delete samsung pass which cannot since do not have root access, so there must be some solution for this,
But you are right about boot lock, but how come it is saying rooted when I never rooted.
Ever since I put lineage 18.1, it is like samsung did not like me putting on a custom rom.
Click to expand...
Click to collapse
Motherboard ie mobo
The efuse is in one of the chipsets on the mobo.
Probably a BGA* one that's not easy to replace and Samsung doesn't even supply that chipset as best I know. Yeah...
One of the reasons I keep my Samsung's stock.
*Ball Grid Array, all the contracts are on the bottom of the chipset completely hidden by the chipset when mounted/reflow soldered. Some like the CPU on PC mobos can be removed as it is help in place by a physical mounting system.
The reflow variant is directly soldered on using precision placed solder paste that is then precisely heated to allow it to reflow.
I had the same problem, but remained with 8 combo , because of all the bugs from other versions since android 11 makes the phone slower.
I wonder if I should change phones since I am so used to my a520w...
Really too bad there is not a reset for knox and pass, if you fixed yours let me know pls...