yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Mega] azpatterson3:
Thanks for looking and trying to help but our situation is dealing with AT&T's locked bootloader. It's something AT&T is starting to do with their new phones.
[Samsung Galaxy Mega] Hashcode:
Can someone run this cmd from adb shell:

cat /sys/class/graphics/fb0/name

thanks
[Samsung Galaxy Mega] latinohot:
i would but i couldn't get it to find my phone in adb
[Samsung Galaxy Mega] pcstable:
msmfb43_80801 (from terminal on device, not adb...)
[Samsung Galaxy Mega] Hashcode:
Thanks
[Samsung Galaxy Mega] Gilly Monster:
I have an extra phone to play with

Long story short the old lady and I got new phones about a month ago, she got the Mega and I got the Moto X. She was trying to give her mother the Mega and she wound up not wanting it over a game, she had picked up an LGG2 and so I have an extra phone now that she likes her LGG2. I been following Hashcode for sometime (Droid head FTW) and I am certain he can get this done. Now I think it's my time to help out alongside. I see the root and such is out for this phone already and I would like to see Safestrap ported to this here soon. What all is available to use and test. I am not afraid to test somethings out. Esp since I have been here lurking and not posting updates.
[Samsung Galaxy Mega] azpatterson3:
Gilly Monster

To date, there have been 3 experimental builds of safestrap. The first put my phone into bootloop. The next two builds of safestrap install but phone boots normally afterwords and stays stuck on samsung splash screen when trying to reboot to recovery from safestrap. Last build was about over a week ago. So we wait and see if hashcode needs more phone information or if he comes back with a new build or tweak. Since its the holidays, he is probably enjoying time with family.
[Samsung Galaxy Mega] captemo:
Any news?
[Samsung Galaxy Mega] azpatterson3:
No word on my end. I sent a pm to hashcode a couple of days ago. Haven't heard anything yet. I know he has a few projects going on so hopefully he will let us know at some point.
[Samsung Galaxy Mega] captemo:
I know these guys are busy, honestly, I dont know where they find the time. People have families and need down time. I am always amazed. Just checking in.
[Samsung Galaxy Mega] dparrothead1:
Deleted.
[Samsung Galaxy Mega] azpatterson3:
Exactly. I sent you a pm.
[Samsung Galaxy Mega] captemo:
As Fat Albert used to say, "HEY, HEY, HEY"!

and an old Marvin Gaye song," Whats goin on?"
[Samsung Galaxy Mega] azpatterson3:
Hashcode is looking for more info to help him out with test builds. Unfortunately they aren't producing the info he needs. Still a work in progress.
[Samsung Galaxy Mega] Christogq:
I will again be offering nudes of myself. Could be a good luck charm.
[Samsung Galaxy Mega] dparrothead1:
Come on, Man!!!! We want to get this thing going....not scare him off!!!!!:D:D:D
[Samsung Galaxy Mega] starmaster10:
Or a heart attack. .:D

Sent from my SGH-I527M Mega 6.3
[Samsung Galaxy Mega] azpatterson3:
Anybody have adb working on their computer with mega and willing to run a non working test build of safestrap and produce a log. Let me know and I can send test build and instructions. This safestrap will not brick your phone and can be uninstalled... I have done it a few times.
[Samsung Galaxy Mega] fixit35:
I have adb working pm files and i will be glad to help out
[Samsung Galaxy Mega] azpatterson3:
Awesome! I sent you a pm.
[Samsung Galaxy Mega] Hashcode:
Hrm.. so from the kernel log:

<7>[ 2.368808] safestrapmenu: unhandled page fault (11) at 0x00000000, code 0x017
<1>[ 2.368808] pgd = df0e4000
<1>[ 2.368869] [00000000] *pgd=a547f831, *pte=00000000, *ppte=00000000
<4>[ 2.369082]
<4>[ 2.369082] Pid: 266, comm: safestrapmenu
<4>[ 2.369082] CPU: 1 Tainted: G W (3.4.0-2052936 #1)
<4>[ 2.369082] PC is at 0x2c748
<4>[ 2.369113] LR is at 0x8529
<4>[ 2.369113] pc : [<0002c748>] lr : [<00008529>] psr: 200f0010
<4>[ 2.369113] sp : beb69d44 ip : 0004a48c fp : beb69dec
<4>[ 2.369113] r10: 00000000 r9 : 000080d4 r8 : 6474e552
<4>[ 2.369113] r7 : 000470c0 r6 : 00000002 r5 : 00000001 r4 : 0004724c
<4>[ 2.369143] r3 : 00000000 r2 : 00383fc0 r1 : 00000000 r0 : 00000000
<4>[ 2.369143] Flags: nzCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
<4>[ 2.369143] Control: 10c5787d Table: a54e406a DAC: 00000015
<4>[ 2.369174] [<c0013fdc>] (unwind_backtrace+0x0/0x11c) from [<c0015ee4>] (__do_user_fault+0x110/0x15c)
<4>[ 2.369174] [<c0015ee4>] (__do_user_fault+0x110/0x15c) from [<c0016150>] (do_page_fault+0x220/0x260)
<4>[ 2.369204] [<c0016150>] (do_page_fault+0x220/0x260) from [<c0008510>] (do_DataAbort+0x134/0x1a8)
<4>[ 2.369204] [<c0008510>] (do_DataAbort+0x134/0x1a8) from [<c000e234>] (__dabt_usr+0x34/0x40)
<4>[ 2.369204] Exception stack(0xdf0ddfb0 to 0xdf0ddff8)
<4>[ 2.369235] dfa0: 00000000 00000000 00383fc0 00000000
<4>[ 2.369235] dfc0: 0004724c 00000001 00000002 000470c0 6474e552 000080d4 00000000 beb69dec
<4>[ 2.369235] dfe0: 0004a48c beb69d44 00008529 0002c748 200f0010 ffffffff

Apparently, I'm accessing memory in a bad way on the Mega. This is not a normal error that i see.

I'll have to think about how to best debug this.
[Samsung Galaxy Mega] Hashcode:
So I probably need someone to hang out on IRC with me for a bit and run some test binaries to see where this is blowing up.

server: irc.freenode.net

channel: #safestrap
[Samsung Galaxy Mega] azpatterson3:
I was on irc.freenode with hashcode for quite awhile today and was running some shell commands through adb for him. Something I wasn't able to do was to get the info he would need during the boot or shortly after boot starts (while the splash screen is going or as soon as possible). if anyone wants to give it s shot the adb command is

adb shell su -c "cat /proc/kmsg" > kmsg.txt

Ctrl-C to stop.

This could help him a lot.

Just throwing it out there.
[Samsung Galaxy Mega] latinohot:
So as it stands right now we can't even get lokidoki like we had the galaxy s4?
[Samsung Galaxy Mega] azpatterson3:
Certainly wroth looking at. I have been focused on safestrap for the past couple of months. Seems like we've hit a roadblock. I would certainly encourage someone to contact the loki dev and see. Maybe start a new thread.

Edit... I think the reasoni didn't look more at loki because they didn't have it for the Note 3 and I was guessing our bootloader setup was like theirs. When in fact,or bootloader may be more like the s4... Don't know? ?

Sent from my SAMSUNG-SGH-I527
[Samsung Galaxy Mega] azpatterson3:
Delete
[Samsung Galaxy Mega] latinohot:
I'll send a pm to the loki chef, hopefully we can get something going, having a moded system ui is not the same as having a whole new rom.
[Samsung Galaxy Mega] stinkeye22:
Hey, I dont know a whole lot, I'm way better at searching. Thought I would post this because this because of the way we obtained root. It has a link to a tester app but the results are in Japanese (they apparently just found this new trojan). KINGO is mentioned in comments on the post, not in the post itself. So I'm not trying to start a scare, just thought it would be worth sharing. https://plus.google.com/113517319477420052449/posts/RientmuCJLd
[Samsung Galaxy Mega] jzsidebott:
Please dont post the same information in multiple threads. This has already been talked about and it has been ruled safe to use Kingo.
[Samsung Galaxy Mega] stinkeye22:
"Ruled safe"? Not that I am talking poorly of Kingo but I didnt realize there was a governing body for rooting methods. And I posted those at the same time, not to disparage kingo but because people in the original g+ had mentioned it & I was anxious. Thanks for the info though :)
[Samsung Galaxy Mega] fire6water:
Hello I'm interested in this subject can you play a link to the g+ account I can follow to be up to date on. He subject.? Thank
[Samsung Galaxy Mega] azpatterson3:
I don't use Google+. Not sure how to do what you're requesting. I would recommend subscribing to thread with email notifications.

Sent from my SAMSUNG-SGH-I527
[Samsung Galaxy Mega] torreon901:
still not cmw or twrp?? how sad this is... i wish i culd help but dont have the knlowledge it takes.. i still with my mega because of the screen size but ystrday my wife got her lg optimums pro and i now remember how good is to do ANYTHING you want to your phone.
[Samsung Galaxy Mega] captemo:
Just checking in
[Samsung Galaxy Mega] azpatterson3:
Had been about a week since I last talked with hashcode. Said he had to look at the kernel because of a frame buffer issue. He said our megas are different then other Samsung phones.... So, just waiting to see if he gets back with us while we hope for a breakthrough.

Sent from my SAMSUNG-SGH-I527
[Samsung Galaxy Mega] captemo:
Seems like we can always count on you for a quick update. Appreciate that. Wish there was more I could do. Not that edumacated.
[Samsung Galaxy Mega] mrmead2:
Thanks for the update
[Samsung Galaxy Mega] deadpigeons:
im willing to do some light testing. I read the forums a lot but don't post much. just bought this phone. already rooted.
[Samsung Galaxy Mega] mrmead2:
Well....the wait is over for me ....im moving on to the note 3....thx for the company and anticipation. ..hope safestrap comes soon for you all.
[Samsung Galaxy Mega] azpatterson3:
Yeah. Understandable.

I haven't heard anything in awhile, even after a couple of pms, so this may be dead.

I'm keeping my Mega because I can customize it enough to keep me happy.

Sent from my SAMSUNG-SGH-I527
[Samsung Galaxy Mega] captemo:
they got the safety strap for Note 3 right? If they got it there, then it should be do-able, no?
[Samsung Galaxy Mega] azpatterson3:
Unfortunatley, it is more complicated than we thought. Our Megas have a different frame buffer than every other galaxy phone using safestrap, so it is a kernel issue and takes more work. Not sure if it is worth it to Hashcode to pursue this. I haven't heard "no", but I also haven't heard anything in awhile. I really appreciate all the time he did put in to this and give him big props for that!! He is still "The Man" and understand if our less than popular phone is not a good use of his time and resources at this moment. Very few Devs even looked our way, so I just want to give a "Thanks" to Hashcode.

Peace
[Samsung Galaxy Mega] latinohot:
Yeah, I never got a reply from the dev that broke S4 bootloader so we're the only nuts who like our oversized yet underestimated Mega
[Samsung Galaxy Mega] deadpigeons:
atleast there an xposed app out there for us :)
[Samsung Galaxy Mega] latinohot:
You don't say.

I have my status bar moded, with center clock different colors for the status bar icons
[Samsung Galaxy Mega] Whit3y:
But ... But .... But i want 4.4 .... i want my carbon rom back :(
[Samsung Galaxy Mega] Grarak:
That's also the reason why I cannot get multirom to work. But this might be helpful for hashcode:

When I plug in the charger and the phone is powered off, multirom appears.
[Samsung Galaxy Mega] caguas56:
Progress

No progress on Safestrap for the Mega yet??????
[Samsung Galaxy Mega] captemo:
Going to sleep here.

I have re rooted, but most xposed mods still dont work for me. I dont get I
[Samsung Galaxy Mega] kmt5150:
I've been working on this friggin thing for 3 months and still no go. I couldnt get past modem flash in odin but I still have the pit file if anyone needs it. I do know that Online Nandroid Backup can make a TWRP or CWM backup, even though we can't flash the backup (making it useless atm). I may move on to the Note 3 or something better (and with more customization options, 4.4.249 etc)
[Samsung Galaxy Mega] caguas56:
I purchased a Note 3 but went back to the Mega because of the screen size. rooted the note but will keep both phones until some Valiant Armor Knight comes to the rescue!!!!!!!!!
[Samsung Galaxy Mega] pcstable:
Dude, I feel your pain!!! I finally set my I527 aside (its an expensive charger for my spare battery for now), and got an M819N. No locked bootloader, no KNOX, rocking twrp, cm11, slimkat, beanstalk, mokee (currently) or aosp.

Absolutely LOVE the M819N, this is what all Mega 6.3's should be like.

I'll sell the I527 eventually. As an aside, if Samsung's new phones ALL have locked bootloaders and KNOX from now on (which looks to be the case), then I'm DONE with them!!!!!!

Meh...
[Samsung Galaxy Mega] kmt5150:
We need to find a way to port this non knox rom and config over to the sgh-i527.. if anyone needs help, I have important specs and block addresses if you need them to compile a flashable rom.

We first need to remove write protection from the firmware...
[Samsung Galaxy Mega] captemo:
anything from Mr. Hashcode???
[Samsung Galaxy Mega] azpatterson3:
Zip... zilch... nada.

Sent from my SAMSUNG-SGH-I527
[Samsung Galaxy Mega] azpatterson3:
Saw hashcode tweet today he will be going back to safestrap work next week. Still could happen but we have been down this road before. Hashcode is awesome and I know he will give it his best shot. We are still on his list. Too bad our phone has thrown him a curve ball.

Sent from my SAMSUNG-SGH-I527
[Samsung Galaxy Mega] dparrothead1:
Still have my fingers crossed, Alex!!! I got a new toy to play with... Tab3 8.0. I am running SlimKat, and it's a nice device.
[Samsung Galaxy Mega] captemo:
I noticed something in the tweet image you provided and it has further intensified my curiosity.

what was his response?? "its a shame that 4.3 wont display correctly" ???

curious because I was comparing phones on ATT website for a possible trade of equipment with them. I comparing the Mega to the LG FLex I noticed ATT website states the Mega is running 4.3. Samsung website states OS is 4.2.2. my phone shows 4.2.2. nobody at ATT can explain to me why website states 4.3 and keeps saying my software is up to date.

what is everybody elses running and would that minor difference affect Hashcodes success with safety strap???

im just a dullard with some curiosity. so please don't hassle me about a stupid question. im bored here
[Samsung Galaxy Mega] azpatterson3:
captemo

I don't think that is what he is referring to. He said it was a frame buffer issue he was having with our phones that is different than other galaxy models like note and s. Hope he can figure it out.

Edit.... I'm on 4.2.2. Pretty sure all ATT megas are on 4.2.2.

Sent from my SAMSUNG-SGH-I527
[Samsung Galaxy Mega] jzsidebott:
The website is wrong. I tried to reach out and have it corrected, but dont know who to contact. the phone is only on 4.2.2
[Samsung Galaxy Mega] caguas56:
Lending my mega!

I am willing to lend my Mega to Mr. Hashcode if he needs it so this damned phone can be broken already!!!. Does he need one?. Let me know if he does!!!!!!!!!!. I'm tired of waiting already. :(
[Samsung Galaxy Mega] azpatterson3:
I forwarded your generous offer to hashcode.

Sent from my SAMSUNG-SGH-I527
[Samsung Galaxy Mega] caguas56:
Nothing new yet??????????
[Samsung Galaxy Mega] captemo:
Patience young one......
[Samsung Galaxy Mega] azpatterson3:
No. Still haven't heard anything. I've taken the philosophy of "If he can do it, it will be done. If he can't, I know he tried but am still happy with my phone". So we just wait and see.

Sent from my SAMSUNG-SGH-I527
[Samsung Galaxy Mega] dparrothead1:
Damn!!! Everytime I see this thread pop to the top, I get all excited and think maybe......just maybe!!! Sigh.....
[Samsung Galaxy Mega] captemo:
Same here. Just need to exercise some more patience and wisdom, ok forget the wisdom.
[Samsung Galaxy Mega] Frezi Evan:
what you want to testing here ?
[Samsung Galaxy Mega] tinfox:
for the love oF ALL HUMANITY!!!!!!!!!!!!!!!!!!!!!!!!!!!!! :silly:
[Samsung Galaxy Mega] Frezi Evan:
If you want to testing anything then you can need [MENTION=1317597]riddik[/MENTION] for testing anything.. You can contact him..:good:

Yes.. Love for all Humanity..
[Samsung Galaxy Mega] Frezi Evan:
what are you willing to that ? :mad:
[Samsung Galaxy Mega] captemo:
I dont understand ???
[Samsung Galaxy Mega] Frezi Evan:
:p:mad:
[Samsung Galaxy Mega] tinfox:
Will this work for the mega (527)? http://xdaforums.com/showthread.php?t=2498850
[Samsung Galaxy Mega] azpatterson3:
I believe early on that Bigfau had tried everything. We went a long time without even having firmware to flash in case of boot loops. After we got root with kingo and an odin flashable firmware, I am not sure if anybody bothered looking at this again.

Short answer..... ?????
[Samsung Galaxy Mega] Frezi Evan:
Yes it works for it..
[Samsung Galaxy Mega] captemo:
Lets clarify a bit.........will it work for AT&T i527?
[Samsung Galaxy Mega] tinfox:
Steve Kondik said it was trivial to unlock to bootloader, only that it would trip Knox and void the warranty. If I don't care about the warranty is it possible then to unlock it. I can't take it anymore!!!!!!!!!!
[Samsung Galaxy Mega] captemo:
Little bump here
[Samsung Galaxy Mega] yomarjosue:
recovery for i527 att

Recovery from mega i527 ?

​
[Samsung Galaxy Mega] hopsin4444:
Did someone figure it out? Att i527?

Sent from my sgh-i527 with xda premium 4

HOPSIN-KAT KEYBOARDS IS NOW UP AND RUNNING CHECK EM OUT OVER AT THE CANDY SHOP!

http://xdaforums.com/showthread.php?p=52221912
[Samsung Galaxy Mega] captemo:
Not that I know of, I just gave the thread a bump the other day. AZ is usually good about giving an update, even if there isnt one.
[Samsung Galaxy Mega] hopsin4444:
Ahh gotcha

Sent from my sgh-i527 with xda premium 4

HOPSIN-KAT KEYBOARDS IS NOW UP AND RUNNING CHECK EM OUT OVER AT THE CANDY SHOP!

http://xdaforums.com/showthread.php?p=52221912
[Samsung Galaxy Mega] caguas56:
Willing to lend my mega!

I say it again, any developer who wants to tweak with the bootloader I'll lend my mega to it PLEASE SOMEONE!!!!!!!!!!!!!!!!!!!!!
[Samsung Galaxy Mega] hopsin4444:
I'm working on it

Sent from my sgh-i527 with xda premium 4

HOPSIN-KAT KEYBOARDS IS NOW UP AND RUNNING CHECK EM OUT OVER AT THE CANDY SHOP!

http://xdaforums.com/showthread.php?p=52221912
[Samsung Galaxy Mega] caguas56:
I found your new thread and following you. Keep it up!!!!!!!.
[Samsung Galaxy Mega] hopsin4444:
Thanks man I am

Sent from my sgh-i527 with xda premium 4

HOPSIN-KAT KEYBOARDS IS NOW UP AND RUNNING CHECK EM OUT OVER AT THE CANDY SHOP!

http://xdaforums.com/showthread.php?p=52221912
[Samsung Galaxy Mega] azpatterson3:
Sorry for the lack of updates. I haven't heard from hashcode since he tweeted about doing more safestrap work a few weeks ago. I sent him a pm that we even had a loaner unit for him if that would help but got no response. Not sure what, if anything, is going on.

Sent from my SAMSUNG-SGH-I527
[Samsung Galaxy Mega] Mustang350:
I'll throw $75 to the first person that unlocks the loader and links to a custom Rom ^^
[Samsung Galaxy Mega] kingflex:
please

Ok guys, someone please get us a recovery on this awesome phone!!!!
[Samsung Galaxy Mega] caguas56:
hosin4444 is already working on one. Look for his thread in the development section. I gave him my Mega so he can work on it.
[Samsung Galaxy Mega] icemikesr2:
att won

I think this phone is locked down too tight. I think we outta say att finally gets the last laugh. Nobody seems to support this phone at all no devs are helping at all. Such a great phone too. Should have got a note 3.
[Samsung Galaxy Mega] hopsin4444:
At&t gets no laughs at all you just wait there good buddy ;) ;) got something coming out for everyone in the next few days
[Samsung Galaxy Mega] azpatterson3:
As OP of this thread, I am ready to let it die. Please head over to hopsin4444's thread. He had done some great work. Thanks hopsin4444! And thanks hashcode for your early work on this project.

Here is the link

http://xdaforums.com/showthread.php?t=2739011

Sent from my SAMSUNG-SGH-I527
[Samsung Galaxy Mega] hopsin4444:
Build will be up today thanks [MENTION=4127455]azpatterson3[/MENTION]
[Samsung Galaxy Mega] BoiBundy:
Thank you!!!

I'm new to the mega (I527)forums but ive been watching closely for a while. Its like waiting for christmas day all over again ^_^

Hopsin, you are the man!! Thank you
[Samsung Galaxy Mega] hopsin4444:
Recovery and knoxoff is up!
[Samsung Galaxy Mega] BoiBundy:
Recovery and knoxoff Fail!!!

I did everything in the exact order as the Op says for the twrp + knoxoff recovery and it fails everytime:crying:

Any suggestions would be much appreciated:confused:
[Samsung Galaxy Mega] hopsin4444:
I put the wrong file up earlier I apologize for that try it again I have 2 confirmed flashes
[Samsung Galaxy Mega] suhas2000:
I'm getting the same message "Fail" :(
[Samsung Galaxy Mega] hopsin4444:
Really? Please message me in the thread
[Samsung Galaxy Mega] crampus:
Worked for me on the third go I had to completely reopen Odin and redownload the file
[Samsung Galaxy Mega] BoiBundy:
I would love to message in the Development section but i do not have enough posts:(
[Samsung Galaxy Mega] hopsin4444:
What is your stock build #

Sent from my i527 with Xda premium mobile 4 app

---------- Post added at 12:54 PM ---------- Previous post was at 12:53 PM ----------

What is your stock build as well?

Sent from my i527 with Xda premium mobile 4 app

---------- Post added at 12:59 PM ---------- Previous post was at 12:54 PM ----------

Your using a i9205 galaxy? Not a i527

Sent from my i527 with Xda premium mobile 4 app
[Samsung Galaxy Mega] suhas2000:
I don't have enough messages either... Do you think it has anything to do with how much battery one has left with? Mine is at 39% I'm going to wait till it gets to at least 50% and try again.
[Samsung Galaxy Mega] BoiBundy:
Stock Build #

my build is JDQ39.I527UCUAMK2

Hope that helps!
[Samsung Galaxy Mega] crampus:
No I have both

Sent from my Sgh-I527 with Xda premium mobile 4 app
[Samsung Galaxy Mega] BoiBundy:
I know for a fact its not the battery, my batter was at 85% when i started:silly:
[Samsung Galaxy Mega] hopsin4444:
Ya it would have nothing to do with the battery I'm sorry guys give me a few to figure out what the deal here is cause my other 2 confirmation are running the same 4.2.2 build and it worked flawlessly
[Samsung Galaxy Mega] suhas2000:
Oh, btw I'm running stock, rooted 4.2.2 on i527, and given 4 tries. But i'm thankful and patient that you're trying :)
[Samsung Galaxy Mega] BoiBundy:
Odin back to stock!

I Odin'ed back to stock and rerooted with kingo and followed you process step by step and still FAIL!

Thanks for the Hardwork!:o
[Windows RT General] wiedster:
Hi,

I recently bought a Dell XPS 10 Windows RT Tab. Yesterday I Player around with some of the Desktop Settings to make it More Touch Friedly. Today I returned to my normal Desktop Computer to find these Settings now on my regular Desktop as well. How can i Prevent that?

I use the same account on both machines.
[Windows RT General] cx1:
In 8.1: Charms > Settings > SkyDrive > Sync settings
[Galaxy Note 3 Q&A, Help & Troubleshooting] jaythenut:
Hi guys trying to help a guy out on xda his got 900j and want to root, i have looked everywhere trying to find out how but no joy

It's really peeing me off so i thought i would put it out there

Thanks
[Galaxy Note 3 Q&A, Help & Troubleshooting] hashan4u:
N900j rooting

How can i root n900j scl 22 handset, please reply :confused:
[Galaxy Note 3 Q&A, Help & Troubleshooting] xdaoxs:
Search scl22 root unlock or sim unlock on the forums brother/sister. If you still cant see any links let us know.
[Galaxy Note 3 Q&A, Help & Troubleshooting] jony45:
how to root and sim unlock scl22

hi hello there

i did a search for "scl22 root unlock or sim unlock"

but still can find it , can you guide me/us/ links or what ever is usefull.

i need to root it without triggering the knox counter, and sim unlock it .

if any one can help , will be more then happy

best regards
[Galaxy Note 3 Q&A, Help & Troubleshooting] xdaoxs:
Ok the links I used were as follows:

http://xdaforums.com/showthread.php?t=2564695

Download the files from romup and have a go and post your results and thanks. Im sure you wont have a prob except its locked down to AU so u cant use another chip in it. Waiting for someone to reslease a calculator or method to unlock the sim as AU have another code that it unknown.

BTW the above method takes your KNOX counter up a notch. There may be another way to keep know counter down but not sure if it works with this Japanese model. Good luck!