Database Users

[Q] Flash counter warrenty

Hey there
Will using TriangleAway to reset the counter and flashing to stock with ODIN definitely mean that service people will not be able to tell the phone has been modified at all?

Its possible there's a hidden counter but what we can't see we can't guard about...
I would also suggest to hard reset(factory reset in options) completely to reset all statuses..

ultramag69 said:
Its possible there's a hidden counter but what we can't see we can't guard about...
I would also suggest to hard reset(factory reset in options) completely to reset all statuses..
Click to expand...
Click to collapse
Also because the s4 does not show a triangle on the download mode screen, Is there any way to check the counter without using triangleaway? and how do they check it in service

yabanize said:
Hey there
Will using TriangleAway to reset the counter and flashing to stock with ODIN definitely mean that service people will not be able to tell the phone has been modified at all?
Click to expand...
Click to collapse
If you simply boot in to "Download mode" the phone will show if you have an official or custom binary.... there is no counter...just says custom or official. ..so just do a firmware flash via odin and then a hard reset (optional) ... then check your binary via download mode...I'm sure it'll be reset to official
Good luck hope this helped

Imgoing to test it
Thanks Bro....
:good::good::good::good:

Also in settings go to About>Status and at the bottom it will show either "Official" or "Custom"... This is the bugger that's hard to change...

anuradhakelum said:
Thanks Bro....
:good::good::good::good:
Click to expand...
Click to collapse
Let us know if it worked )

sadeshmagic said:
If you simply boot in to "Download mode" the phone will show if you have an official or custom binary.... there is no counter...just says custom or official. ..so just do a firmware flash via odin and then a hard reset (optional) ... then check your binary via download mode...I'm sure it'll be reset to official
Good luck hope this helped
Click to expand...
Click to collapse
Im pretty sure there is a counter, It shows up in the triangleaway app

You have to do it this way.
1. Make sure you have a stock Samsung kernel and recovery (triangle away needs it to work on the s4).
- It may be easiest to flash stock firmware and then root again.
2. Once you have stock kernel and recovery and are rooted you can run triangle away. Make sure you follow the instructions carefully as it's a different procedure from older devices.
3. Flash stock firmware that your phone came with. I've discovered the hard way that Samsung service centres match the serial number to the firmware version as another means of checking for software modification.
4. Factory reset.
If you've done everything correctly you'll have official binary/status normal in download mode.
I've done this procedure myself and can confirm it's 100% working.
-- Sent from the mighty Note 2 --

[Q] galaxy s4 gti9505 WAS rooted but cant change status back to normal

hi all, as you can tell, im a noob well, I have a samsung galaxy s4 gti9505 that I rooted with odin WHEN I had a pc, and it just so happens, whenever I root an android, it works but then things start to go wrong like lagging, freezing, drainage of the battery really fast ect. So this time I decided to google how to unroot my phone without a pc to fix my problem. I did that using super su or something which had the unroot option witch I did successfully. But just a few moments ago, I was just checking to see if there were any updates available for my phone because my camera decided to stop working, (well the camera works but when trying to record, a pop-up box appears saying camera failed). So when I tried to update, it said that I cant update because my phone is modified, now as stated above, I am a noob to this subject so please be patient with me trying to comprehend the technical terms use will use hahaha. Can someone please explain to me if it is possible to change the status from custom to normal without the help of a computer? Thanks in advance

help meeh please
Can anyone help?

I don't understand why you want to return back to stock without computer/laptop. In any case following instruction will help you to return your S4 back to stock:
1.First you need to download official firmware for your region from this site: http://www.sammobile.com/firmwares/1/
2. Second upload it to phone with Odin http://www.andromint.com/download-odin-latest-version/
If needed you can also use Triangle away to reset custom flash count.
That's all...
.

Dear all,
I have a similar question.
I've rooted my i9500. I wonder is there any way to roll back my phone like Triangel Away etc. I mean in case of any guarantee situation.

As far as understand, as of now no way to reset.
I hope someone can find a way to reset everyhing to get warranty back.

[email protected] said:
As far as understand, as of now no way to reset.
I hope someone can find a way to reset everyhing to get warranty back.
Click to expand...
Click to collapse
Flash official firmware with Odin PC should do the job. I pretty sure counter will be reset too.

Mittaa said:
Flash official firmware with Odin PC should do the job. I pretty sure counter will be reset too.
Click to expand...
Click to collapse
I will try.
First i will unroot phone than flash original firmware with Odin as you say.
If it works, i will add ss here.
Thanks

[email protected] said:
I will try.
First i will unroot phone than flash original firmware with Odin as you say.
If it works, i will add ss here.
Thanks
Click to expand...
Click to collapse
You don't need to un-root before flash ... you will for sure lose root anyway

romrak said:
I don't understand why you want to return back to stock without computer/laptop. In any case following instruction will help you to return your S4 back to stock:
1.First you need to download official firmware for your region from this site: http://www.sammobile.com/firmwares/1/
2. Second upload it to phone with Odin http://www.andromint.com/download-odin-latest-version/
If needed you can also use Triangle away to reset custom flash count.
That's all...
.
Click to expand...
Click to collapse
Is there any way i can download at more than 200KB's?
http://puu.sh/4YTbL.png
Cause the captcha for the rom download on the link says it's wrong even when i type it right..

I must do something wrong here, because it's not working for me.
I followed the instructions and device still says it is modified and it will not check for updates from samsung.
What is my next step?
Procedure so far:
Gained root acces with ODIN
I did not flash a custom rom.
Used Triangle away to reset counter (counter checked 0 afterwards)
Flashed Galaxy stock firmware downloaded from internet (PHN-I9505XXUDMHB-20130922121848.zip unpacked this once) with ODIN
Furthermore, regarding KNOX reading:
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X1
(I suppose the latter means Samsung still is able to see I did something)
Would a hard reset solve this issue do you think?

Bug in kitkat 4.4.2 in SMG7102 INS Grand 2 [solved]

hi friend i am facing some bug in my device after kitkat update g4 and i thought it get fix in next version but not in nh3 too. Bug are in home lock screen walpaer dnt get change in ripple effect
And while using sim 2 only by disabling sim 1 and req ussd code and make a call it says mobile network nt availble.
have ur facing similar problem like it plese do share.
Get Fixed link : http://forum.xda-developers.com/gal...tkat-4-4-2-smg7102-ins-grand-2-t2851126/page2

Bro try clearing cache in recovery mode.
Even if the problem exits try reinstalling the Firmware using odin

First thing try interchanging the sims and later try factory reset and finally if none works Flash the firrmware

Rahul10 said:
Bro try clearing cache in recovery mode.
Even if the problem exits try reinstalling the Firmware using odin
Click to expand...
Click to collapse
Ok i done it .but no any workd ?

Sanjuujosephh said:
First thing try interchanging the sims and later try factory reset and finally if none works Flash the firrmware
Click to expand...
Click to collapse
I done no any change.. any one facing problem like this?

abilash10 said:
I done no any change.. any one facing problem like this?
Click to expand...
Click to collapse
Try reinstalling the Firmware or try factory resting....

ok bro
Rahul10 said:
Try reinstalling the Firmware or try factory resting....
Click to expand...
Click to collapse
ok bro.. and how may i reset that count ?? how much time it unroot and root ?make it to zero.

abilash10 said:
ok bro.. and how may i reset that count ?? how much time it unroot and root ?make it to zero.
Click to expand...
Click to collapse
Sry bro i didn't get you.?

Rahul10 said:
Sry bro i didn't get you.?
Click to expand...
Click to collapse
I mean how may i get my warranty back by making binary zero? Triangle away is aplicable?

abilash10 said:
I mean how may i get my warranty back by making binary zero? Triangle away is aplicable?
Click to expand...
Click to collapse
You don't need to use Triangle Away now... You must press three buttons (home + power + volume DOWN) until a screen with a triangle shows, you press volume up to continue, then plug in your phone via USB (Of course to your PC) after the "Downloading..." screen appears.
Assuming you already have all drivers and stuff to listen from your USB connection, you then have to open Odin program to flash the firmware file you used to install KitKat. That's how you re-install your firmware.
-------------------------------------------------------------------------------
To reset cache partition, you hold down home, power and volume UP this time, this is for entering recovery mode, when you see the blue "Recovery botting" at the top you can release all buttons now, then you go down to "Reset cache partition" and make sure you don't select "Factory reset" if you see a long list of "No no no no no no" then you're in the wrong area, and you MUST go back again.

abilash10 said:
I mean how may i get my warranty back by making binary zero? Triangle away is aplicable?
Click to expand...
Click to collapse
Our Grand 2 doesn't have a KNOX WARRANTY VOID bit. Don't worry.
But this will be important if rooting a S4 or a Note 3 or above.

WaseemAlkurdi said:
Our Grand 2 doesn't have a KNOX WARRANTY VOID bit. Don't worry.
But this will be important if rooting a S4 or a Note 3 or above.
Click to expand...
Click to collapse
Ok thks for this.

WaseemAlkurdi said:
Our Grand 2 doesn't have a KNOX WARRANTY VOID bit. Don't worry.
But this will be important if rooting a S4 or a Note 3 or above.
Click to expand...
Click to collapse
Then why does we have this in our device?
And why do we have to disable knox during the root process

Rahul10 said:
Then why does we have this in our device?
And why do we have to disable knox during the root process
Click to expand...
Click to collapse
hi friend yes in our device there is no any warranty void count.. it is in s4 .s4 mini note 3 etc.. rom ..

Bug get fixed in new nh6

bug fixed in nh6
Finally bug get fixed in nh6

Rahul10 said:
Then why does we have this in our device?
And why do we have to disable knox during the root process
Click to expand...
Click to collapse
Because it shows annoying notifications saying:
Unauthorized changes have been made. Reboot to undo them.
Nothing happens after a reboot.
KNOX*.apk are the ones responsible for this.

Need help on unfamiliar error screen. Image provided.

Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
UPDATE <21_03_2015><16_54_09_524>____________________________________________________________
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Before flashing
first_flash_no_pit
first_boot_after_first_flash
Second_flash_no_pit
3rd_flash_with_pit

I think that this error appears when a ROM isn't flashed properly to the device. So a possible solution might be a factory reset in recovery and a clean ROM flash with Odin. You just need to download a ROM for your device model - SM-N9005 from sammobile or samsung-updates.

3XTR3M1ST said:
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
Click to expand...
Click to collapse
Download an official firmware from sammobile and use odin to flash. It's all on their site
Sent from my SM-N9005 using XDA Free mobile app

Is Odin a entirely different piece of software to kies?
Also would you this to be soft brick and reason to demand for compensation from the seller?

intervall said:
I think that this error appears when a ROM isn't flashed properly to the device. So a possible solution might be a factory reset in recovery and a clean ROM flash with Odin. You just need to download a ROM for your device model - SM-N9005 from sammobile or samsung-updates.
Click to expand...
Click to collapse
Yes this appears when a rom isn't flashed properly, Or the user has manually soft bricked the device.
st3chn0 said:
Download an official firmware from sammobile and use odin to flash. It's all on their site
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
I wouldn't take this advice as you bought a phone that is soft bricked with knox tripped (0x1)
try and return it before you attempt to fix it.
3XTR3M1ST said:
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
Click to expand...
Click to collapse
3XTR3M1ST said:
Is Odin a entirely different piece of software to kies?
Also would you this to be soft brick and reason to demand for compensation from the seller?
Click to expand...
Click to collapse
It looks like your knox is 0x1 and the system status is 'custom' but i can't really tell as the quality of the pictures isn't good enough.
This means that the phone has been used before and rooted, then a wrong flash or simply just deleting a few system files so it doesn't boot to get that screen to show up instead.
If there is nothing wrong with the hardware, Odin should fix this easily.. but i wouldn't trust it as your imei could of been changed.. many things could of been tampered with.
Also you mention that kies doesn't detect the phone properly, only sometimes. This could be your pc but it is likely a hardware problem with the phone judging by how you recieved it with knox tripped (0x1).
As it has been sold in this condition i can only assume that it has been tampered with. Why else would the seller sell a soft bricked device ?
Was it advertised as new or used?
Return it and get your money back as soon as possible is all i can suggest, good luck.

1. If its possible for him to return to the seller then yes but he can't to samsung. Due to knox being tripped. If he does its just basically a 50/50 chance
2. This nothing to do with soft brick. Such thing as a soft brick doesn't really exist.
3. Using odin to flash any official firmware. Is not bad advice.
Sent from my SM-N9005 using XDA Free mobile app

celderic said:
Yes this appears when a rom isn't flashed properly, Or the user has manually soft bricked the device.
I wouldn't take this advice as you bought a phone that is soft bricked with knox tripped (0x1)
try and return it before you attempt to fix it.
It looks like your knox is 0x1 and the system status is 'custom' but i can't really tell as the quality of the pictures isn't good enough.
This means that the phone has been used before and rooted, then a wrong flash or simply just deleting a few system files so it doesn't boot to get that screen to show up instead.
If there is nothing wrong with the hardware, Odin should fix this easily.. but i wouldn't trust it as your imei could of been changed.. many things could of been tampered with.
Also you mention that kies doesn't detect the phone properly, only sometimes. This could be your pc but it is likely a hardware problem with the phone judging by how you recieved it with knox tripped (0x1).
As it has been sold in this condition i can only assume that it has been tampered with. Why else would the seller sell a soft bricked device ?
Was it advertised as new or used?
Return it and get your money back as soon as possible is all i can suggest, good luck.
Click to expand...
Click to collapse
The seller is not responding to my questions, so I think the next best bet to attempt and fix it myself. Am I right to think that flashing an official firmware is the best option? What could go wrong if the imei have been changed?
Also, you just got me curious about the knox thing. Where do you suggest I look at for a comprehensive elaboration of the error codes?
http://postimg.org/image/rorg1p21n/

Flashing firmwate from sammobile will not trigger knox so as suggested earlier download and flash a firmware for your phone

st3chn0 said:
2. This nothing to do with soft brick. Such thing as a soft brick doesn't really exist.
Click to expand...
Click to collapse
This is a softbrick, if the hardware is fine then you should be able to fix it in 10mins by flashing a stock rom, but as the seller has sold it in this state then i assume it is softbricked for a reason so you can't test the device for example.
cryostasis25 said:
Flashing firmwate from sammobile will not trigger knox so as suggested earlier download and flash a firmware for your phone
Click to expand...
Click to collapse
But his knox is already tripped.. he bought a phone with knox 0x1 that's why i suggested returning it.
3XTR3M1ST said:
The seller is not responding to my questions, so I think the next best bet to attempt and fix it myself. Am I right to think that flashing an official firmware is the best option? What could go wrong if the imei have been changed?
Also, you just got me curious about the knox thing. Where do you suggest I look at for a comprehensive elaboration of the error codes?
http://postimg.org/image/rorg1p21n/
Click to expand...
Click to collapse
If the seller is not responding, then it points to them tampering with the device before selling it. Where did you buy it from, i would ring your bank as soon as possible.
Download the latest n9005 rom from sammobile and flash it through odin if you want to try and fix it, shouldn't really matter what csc as your knox is already tripped anyway so you can't recieve OTA updates or warranty from samsung anymore, mine is a BTU device but i have used many XEO roms.
If the phone isn't connecting to the computer properly like you say, then it's probably best to leave it. As this could result in the connection failing when it is flashing the bootloader or something. But if it works fine, then there should be no problems.
Here is something you could try, start up odin (i use v3.09), close all processes relating to kies, boot the device into download mode, that screen you provided pictures of. Plug the phone in and wait a few minutes to check the connection is stable, move the cable around to make sure the socket and cable are okay. You will see it come up on the top left in odin after windows has installed the drivers.
If this all works fine then flashing a stock rom should fix the device if the hardware is okay.

Just a quick question. From what site did you buy the phone and how did you pay for the phone?
Sent from my SM-N9005 using XDA Free mobile app

Where is a reliable source to download the official firmwares? I cant find it on the samsung site.
Tried http://www.samsungupdate.com/how-to/download-firmware but the file sizes are different on either filehost mirrors and it seems shady.

www.sammobile.com/firmwares/

I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Before flashing
first_flash_no_pit
first_boot_after_first_flash
Second_flash_no_pit
3rd_flash_with_pit

3XTR3M1ST said:
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Click to expand...
Click to collapse
1. Try flashing the new bootloader and modem first: http://forum.xda-developers.com/galaxy-note-3/general/odin-flashable-lollipop-bootloader-t3058101
2. If flashing modem and bootloader succeeded, try flashing the whole firmware again.
From what I learned from this http://forum.xda-developers.com/showthread.php?p=47287747#post47287747 thread, "invalid ext4 image" errors occur when bootloader is wrong.
Actually, do you have any info with what firmware was this phone last? I think I might have encountered another thread (don't remember it, though) which says that these exact problems occur when trying to upgrade from Jelly Bean 4.3 to Lollipop directly.

sirobelec said:
1. Try flashing the new bootloader and modem first: http://forum.xda-developers.com/galaxy-note-3/general/odin-flashable-lollipop-bootloader-t3058101
2. If flashing modem and bootloader succeeded, try flashing the whole firmware again.
From what I learned from this http://forum.xda-developers.com/showthread.php?p=47287747#post47287747 thread, "invalid ext4 image" errors occur when bootloader is wrong.
Actually, do you have any info with what firmware was this phone last? I think I might have encountered another thread (don't remember it, though) which says that these exact problems occur when trying to upgrade from Jelly Bean 4.3 to Lollipop directly.
Click to expand...
Click to collapse
Thanks for the suggestion. I'll give it a try after a little more research.
I have no idea what the phone was before, or what the seller did to it since he's just not responding anymore.

So I tried flashing the new bootloader as suggested, it seem to have worked to some extent, but then I screw it up again by pulling out the cable before seeing "PASS!". What now?
http://forum.xda-developers.com/showpost.php?p=59616074&postcount=16 said:
iketil said:
Hi the file size should be 58 041 KB
From what I can see from you ODIN log, ODIN has "done its thing"
If you did not uncheck the auto reboot tab, the phone should now be rebooting.
And bootloader and Modem should be updated when its booted up.
Are you still stuck at the "Samsung GALAXY Note3 SM-9005" screen ?
Click to expand...
Click to collapse
I'm still stuck on the "Samsung GALAXY Note3 SM-9005" screen. However I do think that the "hlte_lollipop_bootloader_modem.tar.md5" has "done its thing". I was previously unable to get to the recovery, but I was able to get to this <3e>recovery after flashing.
Also managed to see some logs of "i'm not sure what it is" before the phone went blank. I presume its due to battery going flat.
Later, I tried putting TWRP on it. Starting with "twrp-2.8.3.0-hlte-4.3.img.tar". But being a novice odin user I mistakenly unpluged the phone when odin is showing "RESET!". Then I tried going into recovery using VOLUP+HOME+POWER, and got this screen instead. I'm not sure if removing the phone before "PASS!" in odin could have caused this? Subsequently I tried flashing "twrp-2.7.0.3-hlte-4.3.img.tar" and
"twrp-2.7.2.0-hlte-4.3.img.tar", which resulted in the same error screen about SEANDROID.
I also noticed it increased my KNOX counter?
This is before and after.
Next I tried flashing ""hlte_lollipop_bootloader_modem.tar.md5" again hoping it would fix it. It didnt work. Silly me, this flash does not have a recovery image in it does it?
Anyway, now I dont have a working recover and is still stuck on the "Samsung GALAXY Note3 SM-9005". Thankfully odin mode still work. What should I do next? Please see this thread below for a little background to my problem. Thank you.
http://forum.xda-developers.com/galaxy-note-3/general/help-unfamiliar-error-screen-image-t3059227
Click to expand...
Click to collapse

HORRY SHET!!
I think my phone is asian! I just flashed the latest taiwan firmware released (N9005ZSUGOC3_N9005OZSGOC3_BRI) after flashing the new bootloader and everything works now!
I'm not sure what actually made it work since this is the first taiwan firmware I tried (its all XEO and BOB previously), but big thanks to everyone who helped!

[Q] Confused about my specific device

Heya guys,
I've read through so many websites and forum posts but always when I think I have found the right thing for me, the model number, baseband version and/or build number varies...
All I want to do is root my phone. If there's a safe way to do this without tripping that KNOX whatever, that would be great but not even the most important to me.
And if it is possible I would also like to get Android 4.4.4 installed. Strangely, my phone says it is up to date (4.4.2) but I'm seeing people having 4.4.4 on theirs...
If there's something like a pack to get both, the update and the root, that would be mint!
Either way, I would be very thankful if someone could point me to a place where my exact device could get its appropriate files.
Model number: GT-I9301I
Baseband version: I9301IXXUANF2
Build number: KOT49H.I9301IXCUANJ4

you have the gt-i9301i so latest version for your device is 4.4.2 , but 4.4.4 is available for dual sim variant gt-i9300i you can root it i'll post the link below and navigate through the android devloppement section and find a rom that suits you then install it
link for root : http://forum.xda-developers.com/gal...overy-t-r-p-samsung-galaxy-s3-neo-gt-t2906840

Heya, thanks for the answer!
Ah, so there's also a dual sim variant. Mean that only they get the 4.4.4 update
So, on that link you gave me... do I need that stuff in the first post or is it enough for me to load and process the stuff in the second post (under 2nd Method I guess?)?

you choose which method you want to use then you're good to go

Yeah, but lets say I choose that "2nd Method ( Odin method )" - do I ALSO need that stuff from the first post (TWRP) or is that not needed then?

no just from 2nd post (odin mode)

Maximus0415 said:
no just from 2nd post (odin mode)
Click to expand...
Click to collapse
Wuaaah, when I go into download mode, it says "Product Name: GT-i9300i"
Now which one is right? O_O
Also, are you sure the second post stuff is all I need? It looks like all I'm getting there is a new recovery, it doesn't say anything about root...?

Ego_Bizarro said:
Wuaaah, when I go into download mode, it says "Product Name: GT-i9300i"
Now which one is right? O_O
Also, are you sure the second post stuff is all I need? It looks like all I'm getting there is a new recovery, it doesn't say anything about root...?
Click to expand...
Click to collapse
look dude download recovery.tar and the 2 zips supersu and knox removal then put them in your phone then put recovery.tar on odin then got to download mode on your phone then plug it to your computer then click start after it's done boot in recovery (lock key + home key + volume up key ) then flash the two zips and you're done mate

Maximus0415 said:
look dude download recovery.tar and the 2 zips supersu and knox removal then put them in your phone then put recovery.tar on odin then got to download mode on your phone then plug it to your computer then click start after it's done boot in recovery (lock key + home key + volume up key ) then flash the two zips and you're done mate
Click to expand...
Click to collapse
So I do need the two zips from the first post, you didn't say that before
I'm still confused, though, about the download mode telling me my device is a GT-i9300i. Is that just a bug or something?

Check about device

TotalErikas said:
Check about device
Click to expand...
Click to collapse
Yeah, there it says "GT-I9301I", that's why I'm confused. I don't know which is right.

Ego_Bizarro said:
Yeah, there it says "GT-I9301I", that's why I'm confused. I don't know which is right.
Click to expand...
Click to collapse
You have the i9301i then. Trust me.

Alright, thanks! I'll try this then... I hope there won't be any brickage O_O

Yay, everything worked as it should.
Since I applied the KNOX removal, is it also necessary to use TriangleAway?

Ego_Bizarro said:
Yay, everything worked as it should.
Since I applied the KNOX removal, is it also necessary to use TriangleAway?
Click to expand...
Click to collapse
No . I personally rooted my device with cf auto root. After I launched the SuperSU it removed KNOX

Hm, I think you misunderstood my question. KNOX seems to be removed already.
But there's still that other thing with the yellow triangle (years ago, one needed 'Triangle Away' to remove it), right? Or has Samsung given up on that when they introduced KNOX?

Ego_Bizarro said:
Hm, I think you misunderstood my question. KNOX seems to be removed already.
But there's still that other thing with the yellow triangle (years ago, one needed 'Triangle Away' to remove it), right? Or has Samsung given up on that when they introduced KNOX?
Click to expand...
Click to collapse
Yeah, considering I have never heard about it, it probably doesn't exist anymore.