[Q] How to hard brick phone so that knox isn't visible? - Note Edge Q&A, Help & Troubleshooting

I promise this is not a troll post.
Can you flash something through odin/or do something which makes the phone unbootable thereby hiding the knox status and getting warranty?

Fry it
Cut a old power cord its Red & Black wires !
Cross connect it 2 a battery & problem solved

A little non destructive method. Wouldn't that leave a burning smell near the battery points.?
I've heard that you could flash an s6 or note 5 modem or something.

I believe flashing S6/Note 5 modem will just screw your EFS or get your phone temporarily stuck in a bootloop which can be easily solved by re-flashing the Stock ROM.
However, you'll still have access to download mode which clearly shows the KNOX status.
Just curious, why do you want to give the phone in for warranty?

murtaza02 said:
I believe flashing S6/Note 5 modem will just screw your EFS or get your phone temporarily stuck in a bootloop which can be easily solved by re-flashing the Stock ROM.
However, you'll still have access to download mode which clearly shows the KNOX status.
Just curious, why do you want to give the phone in for warranty?
Click to expand...
Click to collapse
Right now i don't need. I'm preparing for a time when i might need.

Related

my phone don´t turn on! PLEASE HELP ME! T.T

PLEASE HELP ME!
I WAS TRYING MODIFY JPA ROM, I DELETED SOME APPS (MAPS, WIDGETS...) AND I TRIED TO INSTALL IT. I ENTERED IN DOWNLOAD MODE AND INSTALLED IT BUT ODIN SAYS ME: Big partition size!! AND IT NOT CHARGE, AND I DISCONNECT THE BATTERY FOR INSTALL THE NORMAL ROM, BUT MY PHONE NOW DON´T TURN ON! I CAN´T ENTER IN DOWNLOAD MODE, IN RECOVERY....
PLEASE HELP ME! T.T
Looks bad, didn't you remove boot.bin and sbl.bin when flashing? Did you try to remove battery, wait one minute, replace battery and turn on using the three button combo? If this does not help you bricked your phone and have to take it to a service center. But don't tell em what you did, just claim it went off and does not turn back on... they will reflash it using their jig box and the phone will work again.
ok, a lot of thanks! I going to try remove the battery and turn on the phone...
No, I don´t remove the boot.bin and nothing, only removed some apps from factoryfs.rfs and changed the android.policy.odex from framework...=(
To bad, you should always remove the bootloader files to avoid the risk of bricking. Looks like the flash stoped during bootloader replacement...
And I can do now? T.T
Your phone is bricked... =/
It happen to me too! I was modifying an JPX ROM file, by removing files from tar and add files from other roms...
Don't try to do this, never! I send my phone back to Samsung, to use the 1 year warranty, i told him my phone was charging and never turns on later it...
Now, after 28 days (Brazil), i have my phone back with a new motherboard.
Samsung says: "Phone don't power on, waiting OS bootloader and imei, nand memory lost..."
I tried all techinics to solve: warm phone with hair dryer, "unbricker" with 301K resistor, keys combination and many other, but take no effects, cause my "custom rom" was modified, and we can't do this just removing a file and add others, make a new tar file doesn't works too.
Use the Samsung warranty! If you have...
Belive me, it has not much to do with modifying the rom, it can happen also if you flash a bootloader with unmodified rom, we had some cases like this on German forum also...
Then? What I can say in Vodafone, when this evening I´m going to the shop?
Explain me slowsly, because I dont understand English very well!
Pulchinelli said:
Use the Samsung warranty! If you have...
Click to expand...
Click to collapse
But my phone was rooted, my warranty work?
THANKS!
fersago said:
But my phone was rooted, my warranty work?
THANKS!
Click to expand...
Click to collapse
Thats why you should not tell em what happened. If it don't boot they wont see it was rooted

Phone radio dead?

So about 30 minutes ago my phone stopped being connected to any kind of cellular service. I've got the triangle with red crossed circle and both debug menu via the dialer and system settings show that there's no received signal period. Tried reflashing the ROM I had loaded to no avail. Was rooted and unlocked so I may be out of my warranty unless I can relock it/unroot it.
Anyone ever seen this before or could point me in the right direction to something I may have missed?
Thanks in advance,
CMNDR
You said "tried reflashing the ROM I had loaded" - what about flashing stock, or even using RSD to flash completely stock?
If you are officially unlocked, I'm sure your serial number is in moto's database - so even if you relocked/unrooted it, the device's warranty (manufacturer, mind you) is still voided...
Note I said manufacturer. Not sure what Sprint would do......
arrrghhh said:
You said "tried reflashing the ROM I had loaded" - what about flashing stock, or even using RSD to flash completely stock?
If you are officially unlocked, I'm sure your serial number is in moto's database - so even if you relocked/unrooted it, the device's warranty (manufacturer, mind you) is still voided...
Note I said manufacturer. Not sure what Sprint would do......
Click to expand...
Click to collapse
I just finished the slowest download of my life (~30KB/s) for the stock zip to flash from RSD Lite, going to do that in the next few minutes. If I remember correctly I might have the device listed under a BestBuy Mobile protection plan, though I haven't looked into what that has for fine print.
CMNDR said:
I just finished the slowest download of my life (~30KB/s) for the stock zip to flash from RSD Lite, going to do that in the next few minutes. If I remember correctly I might have the device listed under a BestBuy Mobile protection plan, though I haven't looked into what that has for fine print.
Click to expand...
Click to collapse
So flashing back stock with RSD seemed to do the trick as I have data and cell connection again.
I found this post http://forum.xda-developers.com/showthread.php?t=2202291 to be most helpful in locating the files to use in RSD.
Will wait a bit before rerooting and adding custom recovery just to make sure it wasn't a hardware issue. Still no idea how my modem file got corrupted though, as the phone was inactive at the time of the loss.

bricked s8+ trying to root

ive tried to root my s8+ following the step by step guide but now its a brick
i have never rooted before and tried it for the first time, everything seemed to be going correctly until i pressed wipe and swiped to confirm, i got error message unable to mount storage, now i have a continuous loop of samsung s8 logo
i have tried connecting to odin again and no joy.
is there any hope or is it for the bin ?
gutted
What model do you have? If it's a Snapdragon, they are locked down tight and not rootable. You may have just made a drink coaster....
i have model SM-955F
Download the stock ROM and download mode should be reachable, where you can then flash it
Pedroc1999 said:
Download the stock ROM and download mode should be reachable, where you can then flash it
Click to expand...
Click to collapse
i need more information if possible ? i have no idea how to do it, its my first and probably last attempt at rooting
It's probably not binned, don't worry. Can you get into Download mode again?
- Press and hold the Bixby, Volume down and Power buttons together until you see anything on screen.
- When you see a warning screen, hit Volume Down to continue to download mode.
GibMcFragger said:
What model do you have? If it's a Snapdragon, they are locked down tight and not rootable. You may have just made a drink coaster....
Click to expand...
Click to collapse
Come on man, if you had a snapdragon version, you can't root or even get that far.
yes i can get into the screen where it says downloading do not turn off
It does look like it's the usual snapdragon variant, yeah. You need the Exynos version for its unlocked bootloader, if you want root and whatnot.
Honestly unless you have specific reasons for root, you probably don't need it.
I was pleasantly surprised at how much I don't miss it so far, but I can't speak for everyone else. I know Brava27 wouldn't dare.
Edit: Okay good. So the Stock ROM is basically the factory image always intended for your phone, from Samsung. You just have to find and download that, then flash it as usual via Odin.
PLEASE triple check around and do your research on whether this link provides you the right one, but here is a first-hit I found when searching for a stock rom for your model. https://forum.xda-developers.com/galaxy-s8/how-to/sm-g955f-stock-odin-firmware-t3585022
brilliant thank you i will give it a try
does it unroot it also if i flash it back to stock and put knox back to normal or is that history now ?
That's right, it's completely stock, so it'd be like you got the phone fresh. It'll be unrooted if you get it working.
So that said, ensure your SIM is in the phone before you set it up, or it'll reset on you again when you insert it later.
I'm not sure what Knox's status would be and if the e-fuse has triggered... you'll know when you're powering on the device, I think. It's no real matter, unless you're concerned about warranty. In which case, you were going to stop caring about that right after attempting to root anyway.
I'm still not certain on what firmware file you want. Might want to search around for something that matches your carrier.
once you root knox is triggered forever, no way to use samsung pay or samsung health in stock not rooted firmware.
galarond said:
once you root knox is triggered forever, no way to use samsung pay or samsung health in stock not rooted firmware.
Click to expand...
Click to collapse
can you use them on rooted devices with knox triggered ?
No, I was not able to use Samsung Pay on my Note 5 after I tripped knox. It does some sort of security check on start-up of the app.
The bigger question is whether it "rooted" yet or not. With some luck, the e-fuse has not triggered yet and it's a clean device still.
widget2k13 said:
can you use them on rooted devices with knox triggered ?
Click to expand...
Click to collapse
yes with custom roms can be done or with some build.prop mods too.
So the snapdragon version is not rootable? Damn, I didn't know that.
woohoo somehow and i have no idea how i managed to get it working again and its rooted
couple of things though now its rooted
i have a security notice always popping up saying there is a problem with my phone and it needs repaired, how do i stop that ?
i found a post about changing a 1 to a 0 to get s health working but when i edit it and try to save it i get error read only file unable to save.
the main reason i wanted it rooted was to stop the annoying heads up display so i installed the noheadsup app which said it installed but i cannot see it on my phone anywhere to change the settings
also the battery drain , normally overnight it uses about 5% battery, last night 32% overnight
apart from that it all seems to be working as normal thanks to the help from people on here
widget2k13 said:
woohoo somehow and i have no idea how i managed to get it working again and its rooted
couple of things though now its rooted
i have a security notice always popping up saying there is a problem with my phone and it needs repaired, how do i stop that ?
i found a post about changing a 1 to a 0 to get s health working but when i edit it and try to save it i get error read only file unable to save.
the main reason i wanted it rooted was to stop the annoying heads up display so i installed the noheadsup app which said it installed but i cannot see it on my phone anywhere to change the settings
also the battery drain , normally overnight it uses about 5% battery, last night 32% overnight
apart from that it all seems to be working as normal thanks to the help from people on here
Click to expand...
Click to collapse
For the "Security notice" try this:
root explorer go to /system/app/SecurityLogAgent delete folder
For "S-Health" to work, follow this:
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-s-health-devices-knox-t3543306
Good luck.
Totaly different sittuation but I think I have this right from what you say in this thread.
That Knox being tripped cant be reversed? and that Knox is a fuse so it cant be bypassed with otg cable backup?

Samsung Galaxy S6 still not recognized by ODIN even after replacing charging port?

Originally, my galaxy S6 began to stop fast charging, and began charging extremely slowly. I bought a wireless charger, and it seemed to work fine. However I logged in to my Snapchat account on a different phone while I was trying to find a charger for the Galaxy. Since my phone is rooted, I was locked out of re-signing into my account on snapchat on the Galaxy S6. So to get into Snapchat I thought I could unroot it by using the Super SU app, but now my phone is stuck in a boot loop. I'm trying to reflash original firmware in ODIN but every time I plug my phone in I get "USB device not recognized" and nothing shows up in ODIN. I just took it to a repair shop and they replaced the charging port for me, and I still get this error. Is this a software thing or did the shop screw me over and my port is still broken (I looked at the port inside and it looks brand new. Maybe they messed up the installation?) I don' think it's FRP Lock, since in ODIN mode it says "FRP LOCK: OFF"
In ODIN Mode i'm given this:
ODIM MODE
PRODUCT NAME: SM-G920T
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: OFF
Secure Download: Enabled
KNOX WARRANTY VOID: 1 (0x030c)
RP SWREV: B:4 K:3 S:3
And Volume Up + Home + Power gives me:
KERNEL REV. CHECK FAIL. DEVICE:3 BINARY:2
Is it charging when connected to a wall plug?
G920Fuser said:
Is it charging when connected to a wall plug?
Click to expand...
Click to collapse
Yes, but still very slowly.
Ayyfries said:
Yes, but still very slowly.
Click to expand...
Click to collapse
If I were you I'd give it to another good technician and tell them everything from start to bottom and let them handle it.
G920Fuser said:
If I were you I'd give it to another good technician and tell them everything from start to bottom and let them handle it.
Click to expand...
Click to collapse
Yeah, just did that. Hopefully he just reassembled it incorrectly the first time.
Ayyfries said:
RP SWREV: B:4 K:3 S:3
And Volume Up + Home + Power gives me:
KERNEL REV. CHECK FAIL. DEVICE:3 BINARY:2
Click to expand...
Click to collapse
Correct me if I am wrong, but you are trying to flash a version of kernel that is older than the one currently on the phone, and I have never heard of a successfull downgrade.
Why dont you try emergency initialization through Smart Switch, with sn of the phone, it will flash latest official fw version for that phone.
Afterwards you can root it again, because it will prolly be stuck on logo with official fw.
In case u need help with Smart Switch, i made instructions, so you can check threads created by me in my profile.
When you finally manage to have an operating sw on the phone, you can access USB settings by dialing *#0808#, try changing settings there, but remember original one in case its needed.
brenner650 said:
Correct me if I am wrong, but you are trying to flash a version of kernel that is older than the one currently on the phone, and I have never heard of a successfull downgrade.
Why dont you try emergency initialization through Smart Switch, with sn of the phone, it will flash latest official fw version for that phone.
Afterwards you can root it again, because it will prolly be stuck on logo with official fw.
In case u need help with Smart Switch, i made instructions, so you can check threads created by me in my profile.
When you finally manage to have an operating sw on the phone, you can access USB settings by dialing *#0808#, try changing settings there, but remember original one in case its needed.
Click to expand...
Click to collapse
I just got my phone back from the repair shop today. Even after replacing the charging port twice, It still is not recognized by the PC. Even when using your method of emergency initialization through smart switch, when I come the part where I have to put my phone into download mode and connect it to the PC It is still not recognized.
Restore your phone to factory settings using Samsung smartswitch.. download link is located in the sidebar on the right, download the windows version and follow the prompts.
This should revert your entire phone to the stock experience across the board, rom, kernel, bootloader, modem the whole package.. if it's a software issue causing your problem this will fix it.
fOmey said:
Restore your phone to factory settings using Samsung smartswitch.. download link is located in the sidebar on the right, download the windows version and follow the prompts.
This should revert your entire phone to the stock experience across the board, rom, kernel, bootloader, modem the whole package.. if it's a software issue causing your problem this will fix it.
Click to expand...
Click to collapse
Unless it's a real hard brick , but I hope not.
BaTarrY said:
Unless it's a real hard brick , but I hope not.
Click to expand...
Click to collapse
The beauty of android is its extremely difficult for the end user to "brick" their device.. 9/10 it's as simple as flashing stock firmware to resolve any "bricks".
The problem his having is most likely related to his boot.img, supersu asks if you want to "restore a backup".. I'm guessing he said yes, now his stuck in a boot loop.. it's actually a very common problem. I believe I have been in this situation once before.. To be honest I reject any option's to restore any backups that supersu prompt me to from that moment on, never had any issues since.
This issue can easily be solved by restoring a TWRP backup (kernel specifically) or even flashing a new compatible kernel entirely.. however I highly doubt he has any backups otherwise I'm sure he would of tried this already.
However if he does have a kernel zip currently on his device I highly recommend flashing it before restoring using a stock firmware. Otherwise booting into recovery mode is always a option, throw a kernel zip on the SDCARD, flash that and it should resolve this problem. ODIN is another option.. by doing this they may be able to save user data as a factory restore will result in all data being wiped in the process... however this particular user doesnt seem very experienced otherwise I'm sure he would of tried the following already so flashing stock firmware I think is the best option, fool/full proof method.

SDS?

I got a s6 that bootloops after the Samsung logo. I tried Odin flash firmware but failed after writing nand. Then used emergency recovery through their official application. It failed a bunch of times but succeeded in the end (after 10 retries or so). However the phone still bootloops even after a successful restore. And advice on anything else I can try?
Jo The Veteran said:
I got a s6 that bootloops after the Samsung logo. I tried Odin flash firmware but failed after writing nand. Then used emergency recovery through their official application. It failed a bunch of times but succeeded in the end (after 10 retries or so). However the phone still bootloops even after a successful restore. And advice on anything else I can try?
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s6/help/galaxy-s6-bricked-t3671754/post73762467
Try like that... With latest Odin, drivers and stock FW downloaded via SamFirm. If there are some errors with writing NAND - hardware issue (probably eMMC like in 95% cases). Something happened with phone before, some heavier falls or something?
rifek4 said:
https://forum.xda-developers.com/galaxy-s6/help/galaxy-s6-bricked-t3671754/post73762467
Try like that... With latest Odin, drivers and stock FW downloaded via SamFirm. If there are some errors with writing NAND - hardware issue (probably eMMC like in 95% cases). Something happened with phone before, some heavier falls or something?
Click to expand...
Click to collapse
Yeah, that was the first thing I tried that gave me the NAND error. And yes, the bootloops started happening at random after the phone fell and broke the digitizer as well, after a while the bootloop became permanent. I suspected a broken connection in the NAND bga, but what threw my hypothesis away was that it actually finished the emergency restore from Smart Switch. I guess that doesn't mess with the boot sector at all, and only restores the android OS. Oh well worth a shot, now I've got another expensive hi-tech brick.
Anyone buying those by any chance? Just checking.
Jo The Veteran said:
Yeah, that was the first thing I tried that gave me the NAND error. And yes, the bootloops started happening at random after the phone fell and broke the digitizer as well, after a while the bootloop became permanent. I suspected a broken connection in the NAND bga, but what threw my hypothesis away was that it actually finished the emergency restore from Smart Switch. I guess that doesn't mess with the boot sector at all, and only restores the android OS. Oh well worth a shot, now I've got another expensive hi-tech brick.
Anyone buying those by any chance? Just checking.
Click to expand...
Click to collapse
Some S6 are really sensitive like one fall down and broken eMMC. Repair is even more unprofitable than a completly broken display
EDIT:
Or if you know how to do it, you can change all motherboard your self if you found someone in you area or eBay or something like that, but be sure is from good source so 100% working and not from stolen phone Sometimes can buy for 40-60€.

Categories

Resources