yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Original Android Development] force70:
There is a sammy repair center in miss now actually. .just found out.

Ill get the address when I get home

Here:

Samsung Service Centre*

MississaugaNow Open*

5985 Rodeo Dr. Unit 8*

Mississauga, ON*

L5R 3X8*

Tel: 1-800-SAMSUNG (726-7864)*

Hours of Operation*

Monday - Friday : 10:00 AM - 6:00 PM*

Saturday : 10:00 AM - 3:00 PM*

Sunday Closed*
[Galaxy Note 3 Original Android Development] kcfong2:
Mounting system as r/w (until adbd insecure is available)

This might help a few...

As chainfire said in the OP: "As this CF-Root does not include a custom kernel, adb shell does not have root access by default"

Once you're in su, enter: mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system

At least for me, this gave me r/w within /system, whereas before, I could not do anything as it was all set as Read Only.

Once CF gets adbd insecure written/modified, the above will become unnecessary...
[Galaxy Note 3 Original Android Development] Ettepetje:
Here a reminder:

Few people have done this test sofar, but a HUGE percentage seem to have this Multi-touch defect.

Please check your device if you plan on Rooting !!!
[Galaxy Note 3 Original Android Development] GhorX:
I don't know where Samsung sits in Canada, I'm from Prague/CZE - so be patient with my English. :)

"fresh" = simply last ROM from sammobile

"repaired" = by Odin from my laptop.

I simply did not notice that you have a Canadian version of the phone.
[Galaxy Note 3 Original Android Development] Moguledyouth:
I tried this myself, I got the "same" results but I believe that was because that gesture in landscape auto activates taking a screenshot and coping it to the clipboard. While I am not sure if this is the correct behavior it would explain why they stop because the screen is being snapshoted during the process.
[Galaxy Note 3 Original Android Development] Ettepetje:
Do you mean a hand/air swipe gesture? I've got all those features disabled. Furthermore half the people I got replies from (here and elsewhere) had zero problems even with more than 5 fingers on the screen, meaning there is an unknown difference between these devices. Sofar a hardware defect seems the likely cause, anything better would be great of course.
[Galaxy Note 3 Original Android Development] shaggyskunk:
Sammobile has released the Stock Firmware for Canada and Rogers here - http://www.sammobile.com/firmwares/
[Galaxy Note 3 Original Android Development] DOMin8or:
sorry

wrong threat, sorry. cant find delete function. [MENTION=465326]admin[/MENTION] please delete. i`m blind? can`t find the delete button. sorry
[Galaxy Note 3 Original Android Development] mkeric1:
what about att version?
[Galaxy Note 3 Original Android Development] shaggyskunk:
Dunno - Ask Sammobile - at&t & Samsung.

And feel free to check on the Sammobile site - As often as you like ;)
[Galaxy Note 3 Original Android Development] mkeric1:
right on

thanks a lot brother
[Galaxy Note 3 Original Android Development] SoreGums:
Thanks for this!

I was freaking out - searched cache, found this, swapped ports and SUCCESS!!! PHEW :angel:

Heart rate returned to normal and blood returned to face, haha

My Device SM-N9005
[Galaxy Note 3 Original Android Development] Ettepetje:
I have updated the testing procedure to detect the Multi-touch defect (see also the link in Chainfire's opening post).

A procedure to check whether you have the multitouch defect: (UPDATED on October 11th)

1. Download and run a multitouch testing app of good reputation (I tried both MultiTouch Test and MultiTouch Tester).

2. Put 2 (or more) fingers on the screen of your Note 3 in a horizontal line in landscape mode.

3. Move the fingers slightly about, trying to have both (all) in a straight horizontal line (still in landscape).

4. After only a bit of trying one (or more) detected fingers should disappear (become undetected) or ghost touch detections should appear.

In my case with only 2 fingers on the screen I can get the second one in an 'unstable' flickering state very easily. Also, with a little effort I can have 2 fingers on the screen with one detected, 3 fingers on the screen with none detected, etc.
[Galaxy Note 3 Original Android Development] les_garten:
Hey, you should start a separate thread on this with maybe a poll of people who did the test.

This thread does not seem to be the right place for this.

That's not why I'm posting this, I'm not the posting police!

I'm just interested in how prevalent this problem is, we seems to have some "issues" with the note 3

If you could post the link here I would like to subscribe to it.

A separate well worded title for your thread would get you more visibility as well.
[Galaxy Note 3 Original Android Development] SoreGums:
I installed CF-Auto-Root-hlte-hltexx-smn9005.zip

I have the SuperSU app on my apps screen.

I installed clocksync

and when I run it and sync the time, SuperSU pops up and I grant the action.

then I get the prompt in the notification bar

and the clocksync doesn't set the time, it is the same offset, never gets closer to zero.

Do I need to do something extra??

My Device

Model: SM-N9005

Baseband: N9005XXUBMI6

Build: JSS15J.N9005XXUBMI7

AP: N9005XXUBMI7

CP: N9005XXUBMI6

CSC: N9005OLBBMI3

Odin Mode

Product Name: SM-N9005

Current Binary: Custom

System Status: Custom

Reactivation Lock: Off

Knox Kernel Lock: 0x0

Know Warranty Void: 0x1

Qualcomm Secureboot: Enable (CSB)

RP SWREV: S1, T1, R1, A1, P1

Write Protection: Enable

So I factory reset and wiped data and wiped cache.

then installed clocksync again and same issue as above.

i don't have a proper root then...
[Galaxy Note 3 Original Android Development] MohJee:
Go to settings then security. Uncheck box next to verify apps and set security to normal. Reboot and see if it helps.
[Galaxy Note 3 Original Android Development] Ettepetje:
Is this a good title: Severe Multitouch problem on many Note 3's (Updated test procedure included) ? ;)

But thanks for the suggestions, the link I refered to in my latest post was clearly not very evident. You can find a link to my first relevant post in Chainfire's opening post, first paragraph. My first post here also contains a link to the previously mentioned topic.
[Galaxy Note 3 Original Android Development] jdogg4000:
I am also getting this error after rooting. I tried restoring my backups using Titanium Backup but now anytime i try to run one of them i get this error. Is there a solution to this yet? Anyone else getting this error?
[Galaxy Note 3 Original Android Development] Smiley1987:
i've just rooted and all is working fine :D but i'm still getting the nag screen to update every 3 hours via OTA - i'm guessing the update won't work so how can i get rid of the reminder?

Thanks
[Galaxy Note 3 Original Android Development] SoreGums:
Hmm didn't work.

However i installed busybox from play store just fine.

and i was able to "adb shell su" just fine too.

perhaps it is a SELinux thing.

This tool works, it adds root - just some apps are still blocked, perhaps the fix for Titanium is simply adjusting SELinux configs?
[Galaxy Note 3 Original Android Development] Smiley1987:
Figured this out in case anyone else is having the same issues - froze software update v*_1308_*_1 in titanium :) :)
[Galaxy Note 3 Original Android Development] Marinaxs:
need help

i deinstall supersu by mistake..

so i run auto-root again but supersu said su-file is not installed.

What can i do???

Thanks for help!
[Galaxy Note 3 Original Android Development] les_garten:
Why do you want Clocksync, just curious.

The Cell Phone providers use either a Stratum one or Two Clock source.

The time shown on your phone is accurate to the second . So is the one on Directv or your cable company box.

Other than installing a Stratum 2 or 3 clock on your own, you can't get more accurate than the good Ol' time on your phone. You're getting Satelite/GPS time now. This phone is not like your PC. It already get's it's time from the Network. I have some experience in Network clocks.

---------- Post added at 01:38 PM ---------- Previous post was at 01:36 PM ----------

Awesome, just sub'd your thread and picked up my N3 this morning. Can't wait to check this out.
[Galaxy Note 3 Original Android Development] AGx-07_162:
Hoping someone will be able to help me.

I've followed the instructions but didn't get very far. I get as far as booting into download mode and connecting my phone to the PC via USB. However, ODIN is not detecting my phone. When I boot into Android I can transfer files to and from no problem and I've even installed Kies 3. Any clues?

Edit: I'm using the USB 3.0 cable that came with the device.

---------- Post added at 08:27 PM ---------- Previous post was at 07:34 PM ----------

Figured it out.
[Galaxy Note 3 Original Android Development] digittante:
I used MultiTouch Test on my T-Mo N3 (previously rooted, now firmware restored-to-stock *BMI7). It persistently detected up to 5 fingers in motion simultaneously with no ghosting or vanishing traces.

Seems to be fine.
[Galaxy Note 3 Original Android Development] boaz65:
Thanks for the tip, but mine seems to be fine as well!
[Galaxy Note 3 Original Android Development] digittante:
Just following up to report that I've done a firmware-restore to *BMI7 via Kies with the following results:

Counter - 0

Binary - Samsung Official

System - Official

Knox Warranty Void - 0x1

OTA - Works "Your device is up to date."

About Device / Status - Reports 'Official'

Device Encryption - Works using both 'fast mode' and 'full mode'

ExchangeServerSecurity - Works once device encryption is complete

Knox reports that the phone has been modified, and therefore Knox can't be used. No problem as I hadn't intended to use it anyway.

I'm still interested in rooting so I can de-activate/remove bloatware (mostly to improve battery life and reduce CarrierIQ tracking). Will continue experimenting when I have the time. Happy to report also that replacing the TouchWiz launcher doesn't interfere with S-Pen functionality. I know TouchWiz is more than the launcher, but I really prefer Apex.

All in all, very happy with the device. It passes the 'skinny jeans' test better than the N2 did...
[Galaxy Note 3 Original Android Development] claudioita:
How to put OTA update N9005XXUBMJ1 on rooted phone+region unlock (now with N9005XXUBMI6)?
[Galaxy Note 3 Original Android Development] cfchong:
try uninstalling knox and see if u still have the problem.

i can't test as i have already uninstalled knox. i don't have your problem.
[Galaxy Note 3 Original Android Development] bobbyphoenix:
Two things stand out. One is more of a question: Where is the hardware damage?

Two is this: "The KNOX status depends on the eFUSE technology and the KNOX code gets re-written once you flash a custom kernel or root the Note 3. You can not restore the KNOX code to stock value

as of now

and with the re-written code visible, Samsung is entitled to void the warranty of your device."

Give it time. That's all that is needed.
[Galaxy Note 3 Original Android Development] Heatshiver:
[MENTION=2463812]bobbyphoenix[/MENTION] - I think it is not a point of hardware damage but of Samsung finding ways to save money on support, while still giving great support.

It's funny, that was the same thing I read with the same afterthought.
[Galaxy Note 3 Original Android Development] bobbyphoenix:
Yeah, I agree. Now here is a thought. What if you are still under the warranty, and your phone won't turn on at all? Like a hard brick? That happened to my GSII, and I sent it in to Samsung "for repairs if possible", and what they did was completely replaced the insides. Motherboard and all, and sent it back with no charge to me. I guess they couldn't get it to boot either, and filed it under system malfunction or something because when I got it back the note said "Replaced MSB" or something like that. When I researched it that referred to the whole motherboard. RIght before it died I did have it rooted, and running CM. When I turned it on it had stock ICS on it, and at the time ICS just came out for it, so it was like a whole new phone. I know it wasn't because the phone itself had markings on it from me, and they were still there when I got it back.

So long story short, if the Note 3 is rooted, and all the right things are tripped to show it was "custom", and somehow it gets hard bricked, I guess it would be covered since there is no way to get it to turn on to check for tampering. Hmmm.
[Galaxy Note 3 Original Android Development] Heatshiver:
Seems like it would work. I guess the only other way to ensure they would cover whatever happens is to find a method to purposefully "break" the phone so that it would be impossible for them to discern if it was done by phone or person. Of course, that would be considered quite shady and frowned upon this XDA community.

They should just go the way of Oppo and let people do what they want with it. I can't wait until the Galaxy J comes out and everyone gets pissed they bought a S4, maybe then the backlash Samsung incurs will get them to realize they need to be for the people, not against them.
[Galaxy Note 3 Original Android Development] Gvaz:
Also waiting on the SM-N900V version for Verizon.
[Galaxy Note 3 Original Android Development] RavenY2K3:
This is a reply I got from Samsung when I quizzed them about it

Customer reference number:*2114189183*

Please quote your customer reference number when contacting Samsung*

Email response ID:*2117743171*

Dear "RavenY2K3"*

Thank you for contacting Samsung Customer Support.*

I’m sorry my colleague was not clearer when contacting you last. I can understand your concern as you just want information on your warranty.*

Regarding your query, yes this would still void our warranty because modifying the software could lead to hardware failures as well.*

For example if you changed some of the coding for the processor clock speed then this could destroy the processor in your Note 3 and this is why rooting your device would void the warranty.*

If there is anything else we can help with, please let us know.*

Our Customer Support Team love feedback! Share your thoughts on this response by completing the survey at the bottom of this page.*

Kind regards,*

Tommy*

Online Support Team*

SAMSUNG Customer Support Centre*
[Galaxy Note 3 Original Android Development] SoKoOLz:
Yeah what I did is to go back to stock and ota then root again.
[Galaxy Note 3 Original Android Development] Swanseatom:
Getting a fail on recovery when trying this with latest BMJ3 BTU FW.

Anyone else experienced this?
[Galaxy Note 3 Original Android Development] neoKushan:
Did you turn off the reactivation lock?
[Galaxy Note 3 Original Android Development] tossero:
[MENTION=631273]Chainfire[/MENTION] Thank you , I really appreciate what you're doing for this community !:highfive:

Confirmation number: 43A42015ST786992E
[Galaxy Note 3 Original Android Development] pxdx:
Any idea why my boot loader doesn't mention anything about Knox? Screen shot attached.

Does it mean that I don't have that obligation and it's unlocked?

I'm using the international version of Note 3 in India.

Catch me on Twitter [MENTION=4326940]pxdx[/MENTION]

Indian Android Users Group - http://IAUG.in now Free
[Galaxy Note 3 Original Android Development] grypho:
+1 I have the same situation here, does it mean that we can root with cf freely without having to worry about Knox?
[Galaxy Note 3 Original Android Development] iandoug:
I've been wondering the same thing ... it looks like my (SM-N900) Knox is not installed, just a link/stub to download and install it. So I'm wondering if we go via CF-Autoroot, if Knox will install without objections or not ... perhaps we would ALSO need to first remove the external SD card?

Advice from the experts gratefully received :) ... I'm avoiding rooting until such time as there is more clarity about this.

thanks, Ian
[Galaxy Note 3 Original Android Development] B01070:
+1... same here...
[Galaxy Note 3 Original Android Development] pxdx:
Let's wait to hear from [MENTION=631273]Chainfire[/MENTION] and other experts..

Catch me on Twitter [MENTION=4326940]pxdx[/MENTION]

Indian Android Users Group - http://IAUG.in

Sent via 'Tapatalk' for Android now Free
[Galaxy Note 3 Original Android Development] SoreGums:
I had to use it on i9100 to get GPS fix quicker - plus it was an app that I knew that used root that was simple to check that I was rooted.

ALSO it is a visual way to verify the time is in sync "trusting and hoping" don't really gel that well with me, I like to see :)

I have noticed the N9005 is super quick to lock onto GPS - so I probably won't use that much.
[Galaxy Note 3 Original Android Development] B01070:
I confirm that rooting SM-N900 (Indian Model) using CF-Auto-Root does not trigger KNOX status in download mode (it does not have the status in Download mode)...

Though it changed the CURRENT BINARY & SYSTEM STATUS to CUSTOM....
[Galaxy Note 3 Original Android Development] pxdx:
Wow.. Please a screen shot..

And please now check if it changes to Samsung Official once Stock ROM is flashed..

Also if Triangle Away can be used to remove the Custom Binary count..

Catch me on Twitter [MENTION=4326940]pxdx[/MENTION]

Indian Android Users Group - http://IAUG.in

Sent via 'Tapatalk' for Android now Free
[Galaxy Note 3 Original Android Development] grypho:
Or maybe your can try using xposed to change it, it would be easier.
[Galaxy Note 3 Original Android Development] pxdx:
Xposed wouldn't change it in Bootloader. It only spoofs it in Settings..

This is how Originally both Bootloader look like and differ:

Exynos Version:*https://app.box.com/s/m8dkz0lpmy9ue6t339cc

Snapdragon Version:*https://app.box.com/s/hify4oqmaesm3dvvyf3o

Catch me on Twitter [MENTION=4326940]pxdx[/MENTION]

Indian Android Users Group - http://IAUG.in

Sent via 'Tapatalk' for Android now Free
[Galaxy Note 3 Original Android Development] B01070:
I flashed STOCK and everything went back... FYI Please...
[Galaxy Note 3 Original Android Development] pxdx:
Great.... (y)

So now the boot loader doesn't have any Custom Binary count too?? Means we don't even need Triangle Away?? And both changes back to Official and Samsung Official..

If you have the screenshot of bootloader after flashing CF Root and after flashing Stock ROM again, it will be verrryyyy helpful.. Just 2 pics please..

Thanks once again for all the efforts and risks you took for so many other users out here..

Catch me on Twitter [MENTION=4326940]pxdx[/MENTION]

Indian Android Users Group - http://IAUG.in

Sent via 'Tapatalk' for Android now Free
[Galaxy Note 3 Original Android Development] B01070:
Sorry Mate... I didnt take the screenshot before rooting again... But I confirm that everything goes to official...

EDIT: I guess Triangle away for Note 3 is still not available... Tried with Version 3.10 but unable to do so...

So the only option is flash with official firmware...
[Galaxy Note 3 Original Android Development] pxdx:
No problems. Does it mention Custom Binary Count as 1 now even after flashing Stock ROM?

Catch me on Twitter [MENTION=4326940]pxdx[/MENTION]

Indian Android Users Group - http://IAUG.in

Sent via 'Tapatalk' for Android now Free
[Galaxy Note 3 Original Android Development] Yohng:
I'm now sure that we don't have this Knox bit on Exynos model SM-N900.

Here is my Triangle Away screenshot.
[Galaxy Note 3 Original Android Development] B01070:
It says as "2" now... I guess may be because I have rooted twice...
[Galaxy Note 3 Original Android Development] pxdx:
So can you reset it back to 0 using Triangle Away?

If it doesn't, I think we will need help from [MENTION=631273]Chainfire[/MENTION] to update Triangle Away to work at least for Exynos users.

Catch me on Twitter [MENTION=4326940]pxdx[/MENTION]

Indian Android Users Group - http://IAUG.in

Sent via 'Tapatalk' for Android now Free
[Galaxy Note 3 Original Android Development] Yohng:
Yes pxdx, that is what I mean.

I cannot reset with triangle away, and we need help from Chainfire. But he wrote on G+, that it is not possible.

I hope, he was speaking about SD800, and did not take on consideration Exynos version...
[Galaxy Note 3 Original Android Development] B01070:
As I see it, that is not possible...
[Galaxy Note 3 Original Android Development] pxdx:
Yes hope so as he himself owns a Snapdragon Version. Waiting for further development then before rooting..

EDIT: Even Sammobile has published that [MENTION=631273]Chainfire[/MENTION] shall support Triangle Away for Note III soon.. *fingers crossed*

Catch me on Twitter [MENTION=4326940]pxdx[/MENTION]

Indian Android Users Group - http://IAUG.in

Sent via 'Tapatalk' for Android now Free
[Galaxy Note 3 Original Android Development] try:
Can you run the Knox app after rooting & then flash stock firmware?

My friend cannot. It say failed to register or something...

TIA,

sent from my mobile
[Galaxy Note 3 Original Android Development] avicohh:
I though there is knox sucurity also in the n900 model, but ut seems there isn't yet.

I look in the download mode and there is no knox void or something lke taht,

Device model: N900.

AP: N900XXUBMI5

CP: N900XXUBMI2

CSC: N900OJVBMI1

I flashed now CF-Auto Root

here is the picture after flashing,

Somebody here have knox in N900?
[Galaxy Note 3 Original Android Development] boaz65:
I'm no where near as knowledgeable as you guys here but does the Knox only become a factor after you actually install it? It is listed on my n900p but I was certain to tell the Sprint rep when I bought it to not activate Knox during setup. My phone has the link to download and install but I haven't done so. Could the cf root be performed without an indication in Knox because it isn't actually installed yet on my phone?
[Galaxy Note 3 Original Android Development] B01070:
Yes... You can install CF root in your device... If KNOX is not installed in ur device, u have no issues in rooting...
[Galaxy Note 3 Original Android Development] pxdx:
Now if you flash Stock Firmware back, it will change to Official and Samsung Official again.

However, if you check Custom Binary Count via App like Triangle Away, it will show as 1 and keep increasing everytime you flash something other than Stock Firmware.

Catch me on Twitter [MENTION=4326940]pxdx[/MENTION]

Indian Android Users Group - http://IAUG.in

Sent via 'Tapatalk' for Android now Free

---------- Post added at 08:15 PM ---------- Previous post was at 08:14 PM ----------

If your version is Snapdragon, it will void your Warranty forever. You can try only on Exynos method..

Catch me on Twitter [MENTION=4326940]pxdx[/MENTION]

Indian Android Users Group - http://IAUG.in

Sent via 'Tapatalk' for Android now Free
[Galaxy Note 3 Original Android Development] avicohh:
Thanks man.
[Galaxy Note 3 Original Android Development] boaz65:
Thank you for your reply
[Galaxy Note 3 Original Android Development] shaggyskunk:
"Forever" is relative - in the world of Android ;)
[Galaxy Note 3 Original Android Development] grypho:
So the only thing that is missing is the flash counter thing...
[Galaxy Note 3 Original Android Development] powder02:
I am not really new to Rooting but usually use CWM mode so this is new to me. When i flash it this what i get and am unable to flash any ROM or even make a backup. Is this how it is supposed to be or is something messed up here? I have tried rooting it back to stock and rerooting it but still the same thing.
[Galaxy Note 3 Original Android Development] pxdx:
This looks like Stock recovery and not CWM..

Catch me on Twitter [MENTION=4326940]pxdx[/MENTION]

Indian Android Users Group - http://IAUG.in

Sent via 'Tapatalk' for Android now Free
[Galaxy Note 3 Original Android Development] powder02:
That is what i get when i flash the CF Auto Root
[Galaxy Note 3 Original Android Development] PG101:
And that's how it is meant to be.. you can odin flash the CWM..
[Galaxy Note 3 Original Android Development] maidangisme:
That's Stock recovery, you need to Flash CWM http://xdaforums.com/showthread.php?t=2454079 download the one with your phone version and flash it with Odin :good: