yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 4 Developer Discussion (Devs., Only)] blazinandroid1:
Having a problem with the phone disconnects then reconnects to the computer. Everytime I push binary into BIN file.. Once I figure this out. We might have a full root. Its getting this file to be injected into bin.. Its not my computer or the usb cord. so please dont think that..

I used usb 3.0 and 2.0. Nothing. Same problem.
[Galaxy Note 4 Developer Discussion (Devs., Only)] E--Man:
Hi [MENTION=5844563]blazinandroid1[/MENTION],

By any chance are you connecting to your phone from a virtualized environment? If so, I have seen this issue before. Let me know...
[Galaxy Note 4 Developer Discussion (Devs., Only)] Android.Ninja:
[MENTION=4621219]E--Man[/MENTION];

I getting too old & you beat me to the reply, lol. that was my thoughts exactly. I've also experienced this in VM/Virtual Environment.

[MENTION=5844563]blazinandroid1[/MENTION];

Past situation where injecting file to bin; experienced situation where sending from usb 3.0 to 2.0 we experienced the same result. Remedied by sending from 2.0. I did see your comment about the usb however just letting you know our resolution if it helps.

Developers don't need no stinkin' signature!

If I've been able to help you, please hit the "Thanks" button. ;)
[Galaxy Note 4 Developer Discussion (Devs., Only)] m0j0j0j0:
Been a while since I've played with android dev. Had an issue with usb, primarily the front ports on my machine the rear ports seem more effective. Back to my issue. Simply unplugging and plugging the usb back in wasn't working I had to manually force close adb. Then reopen my dev environment or simply restart adb from the command prompt. (In case you face similar issue my 2 cents ...)
[Galaxy Note 4 Developer Discussion (Devs., Only)] Android.Ninja:
It's not always 100% considering the vast amount of motherboards on todays market. However in the majority, most motherboard manufacturers place USB 3.0 at the rear of the board and 2.0 at the front.

A quick look at the differences as indicated on wiki:

The USB 1.x and 2.0 specifications provide a 5 V supply on a single wire to power connected USB devices.

A unit load is defined as 100 mA in USB 2.0, and 150 mA in USB 3.0. A device may draw a maximum of 5 unit loads (500 mA) from a port in USB 2.0; 6 (900 mA) in USB 3.0.

Generally the rear ports have less likelyness to be bumped, jarred, etc during use, therefore they constitute a more stable environment for use. You mentioned having to force close adb. Possibly a null, or hang from a defective port maybe. Not sure if system related or power. Without having more information I'd only be speculating.

Typically the rear ports provide a more secure connection when communicating via adb to device based on my experience.

I mentioned in my prior post to blazinandroid1 that possibly changing to another jack, hence variance in milliamps, may have affect on the sucess of pushing the file. Just my thoughts from my experience if this can be of help.

Developers don't need no stinkin' signature!

If I've been able to help you, please hit the "Thanks" button. ;)
[Galaxy Note 4 Developer Discussion (Devs., Only)] kamycrs:
I have had a very similar problem few weeks ago!Sometimes this could happen due to bad usb adapter/hubcontroller or bad usb headers on your motherboard!

If your problem is similar to what i had, try to get yourself a USB 3.0 PCI-Express Card! they are usually cheap, you could find a good one for under $20 from Newegg/microcenter !!

Hopefully this solves your problem!
[Galaxy Note 4 Developer Discussion (Devs., Only)] blazinandroid1:
Thanks guys.. I will take a look at a few things..

Just a update. I did a order on a few items. Hope to have them by tomorrow. Just heads up. I am not pushing for a unlock bootloader. Just root.

Sent from my SM-N915V using Xparent BlueTapatalk 2
[Galaxy Note 4 Developer Discussion (Devs., Only)] Agamemnus_:
I'm a developer and I know Java. I have an AT&T Note 4. I don't know much about the process to make a root exploit except the basic concept behind a stack buffer overflow exploit.

* Knowledge charity: I could possibly help code if someone were to guide me through the many holes in my knowledge about this.

* Forcing a restart: I do know an interesting way to force the phone to restart if that is any use at all. I don't know if it is anything special. I reported it to Google months ago but I haven't heard anything back from their devs.

When an application is installed which has a <provider> and an android:authorities in the <provider> that has an empty string, not only will the application crash on load, but any initialization of updates or installs (after the download) will immediately restart the phone. The installs will never complete. The initial malicious/buggy application must be uninstalled in order for this problem to disappear.

* Testing help: I could also help with testing if needed. I'm on the Freenode IRC network under the "Agamemnus" nick.

Regarding the disconnections, I sometimes have this problem as well. I have a bat file that I run on startup. Maybe it will help. This can also be done to reset a "dead" connection, I think. This is probably elementary but...

adb devices
adb kill-server
adb -e reboot
[Galaxy Note 4 Developer Discussion (Devs., Only)] jasonstackhouse:
Yeah if you need help testing let me know, I have two of each computer running different versions of Linux, OS and WIndows. I have delt with USB issue in the past and to be honest this could be a variety of issuses that if so will just drag this out for weeks. That said if you have a program I can test on, I will, and I will brick and or brake my phone trying for you. I want nothing in return, I want no recognition, I just want to help you get what your about to get.
[Galaxy Note 4 Developer Discussion (Devs., Only)] Surge1223:
So I've read back and what's all this USB business? Is this just a shot in the dark or is there some solid reasoning behind it?
[Galaxy Note 4 Developer Discussion (Devs., Only)] m0j0j0j0:
No, doubtful. Someone said they had promise but had connection issues. I responded with a brief example of my previous experience if USB issues I've had I think everyone just gets a bit too excited. I imagine whoever was working on the exploit would have solved the connection issue by now if it was just a simple USB connections issue.

---------- Post added at 04:40 AM ---------- Previous post was at 04:32 AM ----------

I don't believe this individual was facing the issues many of us mentioned including myself... I'd be willing to duplicate his process for him if necessary as I'm sure many of us would! even provide remote access for him to setup a dev environment to test the idea with my pc.
[Galaxy Note 4 Developer Discussion (Devs., Only)] blazinandroid1:
Guys. We didn't fly away. I just have some family stuff to take care of first. Sorry if I caused any problems.

Sent from my SM-N915V using Xparent BlueTapatalk 2
[Galaxy Note 4 Developer Discussion (Devs., Only)] Android.Ninja:
[MENTION=5844563]blazinandroid1[/MENTION];

If you'll give me some information on what you have tried, currently trying, & where you're at on trying to achieve root, I'll be glad to assist. The more developers we've got working on root, then better the odds are that we'll achieve it. From what I've read so far, all other developers have abandoned this project. I've never been one to give up on something. I welcome the challenge. Send me a pm and let me know something.

Developers don't need no stinkin' signature!

If I've been able to help you, please hit the "Thanks" button. ;)

---------- Post added at 01:47 PM ---------- Previous post was at 01:03 PM ----------

Update on progress:

I've been researching in depth the adb/communication process of the LG devices specifically how they utilize "fastboot" for the modification/overwriting of system files. I've also done the same with the Turbo, & the Note 4 with Odin. The bridge of communication at a specifically given point, is the missing link in the ability to overwrite system files. How does this apply to the Note 4? By understanding the communication process, I'm getting closer to being able to modify system files on the Note 4 resulting in eventual root. Any developers that can provide any additional information or help for this project, I'm sure would be greatly appreciated by the Note 4 community.

Developers don't need no stinkin' signature!

If I've been able to help you, please hit the "Thanks" button. ;)
[Galaxy Note 4 Developer Discussion (Devs., Only)] pattonsj:
I'm sure someone has thought of this but is there a chance that [MENTION=4229979]djrbliss[/MENTION] might be able to shed some light on the communication part of this? I know he's busy but he usually makes short work of this stuff.
[Galaxy Note 4 Developer Discussion (Devs., Only)] blazinandroid1:
Dan hasn't been on here since July.. It won't be to long. We will have root..

Sent from my SM-N915V using Xparent BlueTapatalk 2
[Galaxy Note 4 Developer Discussion (Devs., Only)] blazinandroid1:
Verizon Samsung

-Note Edge

-S5 (Lollipop)

-Note 4

We received root. (There is a few bugs behind it.) Which where working out. Hope to have the app done by this weekend for you guys.

Bugs- redeem freezes

- and longer boot up time

Att members please hang tight for a few extra days. Yours is coming..

Update. Please don't inbox me asking me. That you want be a tester. Its only open for devs. Thanks.

Please do not ask about bootloader unlock. That will never happen.
[Galaxy Note 4 Developer Discussion (Devs., Only)] hsbadr:
That's great! Once you post a rooting method for these devices, I'll release MultiSystem (initially introduced here). It's a workaround that is much more than just a recovery solution & will support almost all locked/unlocked Android devices with ROOT access.
[Galaxy Note 4 Developer Discussion (Devs., Only)] jayharper08:
Thread has been cleaned. Once again, this thread is for the development purposes only.

We understand you happy, but the rules still remain for this thread. We have provided other threads to show your appreciation and happiness.

Please stay within the rules of this thread. Thank you.

Edit: Also, as stated by [MENTION=5844563]blazinandroid1[/MENTION], DO NOT pm him and harass him about this. Developers only right now. It's coming and harassing him is only going to delay any further progress.
[Galaxy Note 4 Developer Discussion (Devs., Only)] Venom0642:
Request sent.

Running On New Deadly Venom Note 4 v1.2
[Galaxy Note 4 Developer Discussion (Devs., Only)] hsbadr:
[WARNING] Do NOT TAKE LP OTA !

VZW will be pushing LRX22C.N910VVRU1BOAF LP 5.0 update for Note 4 very soon. Don't take the OTA untill it's confirmed to be rootable !

​

Source: http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-note-4-4-2-15.pdf

On a side note, Im waiting for [MENTION=5844563]blazinandroid1[/MENTION] to send me more info about his rooting method to test it & work with him on fixes for the bugs he mentioned (all credits goes to him anyway). It's quite frustrating to see skeptical comments flying around. It's none of our buisiness to confirm or deny it right now (just patiently wait for release!) or calling April fools prank!! All of us will benefit root access across many Samsung devices when released & if you doubt it, just leave it for moderators to do what's appropriate.

I'll confirm the current status of [MENTION=5844563]blazinandroid1[/MENTION] 's rooting method when he sends me the files.
[Galaxy Note 4 Developer Discussion (Devs., Only)] blazinandroid1:
It will be OK if they take the update. I have root on s5 lollipop also.

Sent from my SM-N915V using Xparent BlueTapatalk 2
[Galaxy Note 4 Developer Discussion (Devs., Only)] ZPaul2Fresh8:
I'm curious, what exploits were used on this? Really skeptical of something on lollipop so soon after weeks of nothing on 4.4.4 even with a PoC...

Video of proof please. You seem to always have these "almost had it" posts so you'll have to excuse my skepticism.
[Galaxy Note 4 Developer Discussion (Devs., Only)] hsbadr:
I see. However, VZW does strange security complications with updates. So, I'd rather prefer to test it on Note 4 LP before letting users take it. For example, the leaked LP OTA for LG-G3 has had rooting problems even though SuperSU files were survived the OTA. We had to use a new rooting method. Another example, S5 can downgrade after many updates while Note 3 4.4.2- images have been blacklisted with 4.4.4 OTA.

I agree that you know better about your method, but I feel it's safer to test it on the real thing 1st.
[Galaxy Note 4 Developer Discussion (Devs., Only)] gatesjunior:
[MENTION=5844563]blazinandroid1[/MENTION] :

So, I am going to take the neutral ground on this. I think to put everyone's mind to rest, just shoot a small video of the bootup and rootchecker and maybe an adb shell and su command. I can understand if you do not want to extend the testing to other developers in fear of someone doing the wrong thing with it or taking credit for your work. Just put this to "bed" and provide that small evidence and I think everyone will quit doubting you.

As a developer I can understand the reluctance to release anything until you have it solid.
[Galaxy Note 4 Developer Discussion (Devs., Only)] jayharper08:
OK. Last chance. Not trying to be a jerk here, but this is a developers only thread. I will start TEMP BANNING if I need to. Everyone always talks about how XDA is full of trolls and developers can not work in peace anymore in their threads. We have set this up, so that they can work in peace. This is not a Q&A thread, this is the serious development thread. I'm tired of cleaning it and will be forced take measures I do not want to.

Jay

Senior Moderator
[Galaxy Note 4 Developer Discussion (Devs., Only)] Surge1223:
Okay... that doesn't mean that it will work on Note 4 when it gets the lollipop ota. This is bad advice. So many things are different, hardware, kernel version, firmware.

PSA

Don't take the Lollipop OTA
[Galaxy Note 4 Developer Discussion (Devs., Only)] hsbadr:
To add to this... You can take the OTA ONLY under one or more of the following conditions:

You don't care about root access !!!

It's confirmed that you can downgrade to KK

It's confirmed that you can gain root access on this specific update.

UPDATE: It has been confirmed that you can downgrade from LP to KK. So, take the OTA if you wish & wait for a rooting method to get released for either KK or LP.

Unfortunately, I've not recieved any files from [MENTION=5844563]blazinandroid1[/MENTION] yet :confused: So, I'd recommend to keep working on other directions/methods until hopefully something come out !
[Galaxy Note 4 Developer Discussion (Devs., Only)] KennyG123:
Hi all!

I would like to remind everyone why XDA set these sections up once more. These sections are for developers to collaborate on worthwhile development projects. This is the place to discuss methods, theories and attempts to solve problems like root. Be very weary of anyone popping in and claiming a solution to the thread's purpose without discussing the method. This is not what this section is for. In the past we have had members come on to this site with these claims leading people on...remember Anthony? This is not to say that someone cannot attain root but this subforum is not the place to post claims without a developer's discussion of the method. If root was truly obtained and it is buggy, what better thing to do for the community than post the work so others can work on it too to complete it? No disrespect to anyone posting claims but please provide some information to help spread the knowledge and allow others to also work on the project and for everyone reading to learn.

So please...no one else jump up yelling "Bingo!" Let's get development flowing again on the best development forum on the planet!

And one final reminder...if you are not of developer grade discussion, do not post here. Keep it in General subforum threads. Infractions/bans will now take place.

Thank you all!
[Galaxy Note 4 Developer Discussion (Devs., Only)] AtariDroid:
Recovery logs?

I'm going out on a limb here. I have limited experience with adb, terminal emulators, have toyed around and rooted with numerous tools since the droid 1 days. I'm just a senior member, not a developer, please mods don't nail me.

Anyhow, I have what I *hope is useful info, new to me, hopefully not common knowledge.

Since I have updated to lollipop, I decided to go into recovery and wipe cache. Volup, home, power, I get the Android, says installing system update. Then into recovery. It says #Manual Mode# at the bottom. Up above is Enable/Disable CP logging, and View Recovery Logs. There are 5 logs in there containing everything the phone has done during the update process I assume, and also mentions verifying and succeeding signatures. In between there seem to be keys?? :D

Hoping I'm right and this helps. I can share pictures if needed,although I'm guessing any of our phones that have updated without wiping everything do the same.
[Galaxy Note 4 Developer Discussion (Devs., Only)] blazinandroid1:
Alright guys. Update.. I gave all my root tools to a Dev. To finish up the work. I don't have time to work on this anymore. I am sorry if I caused any conflict. Work has been crazy and the time I do have. I spend with my family. Having twin infant boys. Really eats up the clock. I will still be working with that person. Until we get root..

Update. I will not give info on what Dev I used. Due to people like to fluid messenger box. Asking questions. I learned the hard way.

This will be my last message in here.

Sent from my SM-N915V using Xparent BlueTapatalk 2
[Galaxy Note 4 Developer Discussion (Devs., Only)] Xak:
A serious question. What dev did you give your work to to finish up. We would all like to know. . The dev continuing your work should be mentioned so we are not left out in the blue. You should also tell the new dev on this project to update his progress as well. No one has also yet to see any sort of progress. If you handed your work to a known developer maybe he can shed some light on the situation.

Anyways thanks for your work everyone appreciates it even without proof. You still give us hope that someone is working in it. Besides hackers hack into the government if they can root this device whats the difference. Point being nothing is hack proof.
[Galaxy Note 4 Developer Discussion (Devs., Only)] Venom0642:
I pmed you last week please sent me a pm with the tools so i can take a look on it see if i get better luck Thanks.

Edited : Also might want to sent to [MENTION=3178012]gatesjunior[/MENTION] , [MENTION=3758230]cstayton[/MENTION] the more Devs get involved the better chances we can get it rooted.

Running On New Deadly Venom Note 4 v1.2
[Galaxy Note 4 Developer Discussion (Devs., Only)] heXacode:
Also sent a PM to work with another angle into this in case the PoC and CVEs theory fails once I get a test run going eventually.
[Galaxy Note 4 Developer Discussion (Devs., Only)] blazinandroid1:
Blank
[Galaxy Note 4 Developer Discussion (Devs., Only)] veteranmina:
Moderators please do not delete this, it's a honest question for dev's from a Computer Tech.

I've been poking around on adb for the past few days, and happened to run across setprop/getprop. The getprop grabs the list from build.prop as needed, and setprop accepts the command to change the build.prop but does not have any actual affect (I take it in the background is it denying it). Now my idea was to see if there is a way to add in "ro.secure = 0" (and whatever else needed changed) which would enable root at adb shell, if this could happen then we'd have full root access through adb.

The reason I'm bringing this up, is I know others are attempting to get root through the surfaceflinger. My question is, is there a chance we can use known CVE's to possibly pass the command for setprop/getprop through to write in the build.prop.

Sorry if this is not possible, I am not too knowledgable with programming but I do like poking my head through it from time to time.
[Galaxy Note 4 Developer Discussion (Devs., Only)] hsbadr:
Developer Discussion

Folks,

TBH, there's no ROOT method available YET & based on what I posted here, there's no clear idea about security bypass, mounting /system rw, or correctly injecting SU binary. Developers should continue working on other ways & ignore any attempts to hijack the thread without sharing TECHNICAL info for discussions (even if there's WIP).

This section is designed for Developers Only DISCUSSION.
[Galaxy Note 4 Developer Discussion (Devs., Only)] cstayton:
In order for ro.secure=0 to work as well as the other settings it need to be in the default.prop not build.prop and since we have locked BL we can't write to default.prop
[Galaxy Note 4 Developer Discussion (Devs., Only)] Surge1223:
So all qseecom commands have to go through the libQSEEComAPI.so library, from reversing this library I can see the register listener and send_modified_cmd are symbols of this library. So I looked through the commands to register a listener and it seems by default it registers two libraries.

1. libdrmfs.so

2. libdrm.so

But it has to accept other listeners as long you register them with the qseecom library. So the logic here is to register a listener and then use printk/logcat to see what uid that listener will have and see what can be done from there. I have gotten as far as registering a library but am still investigating. So idk where I'm going with this but thought it might be beneficial for others to start reversing/understanding the proprietary libQSEEComAPI.so library.
[Galaxy Note 4 Developer Discussion (Devs., Only)] drivel2787:
What tools? Would be beneficial for those wanting to contribute.
[Galaxy Note 4 Developer Discussion (Devs., Only)] Surge1223:
Ida, readelf, objdump really whatever. As for the screenshot, I compiled gcc, java, git, etc for my phone so that's why I have that output from readelf there
[Galaxy Note 4 Developer Discussion (Devs., Only)] Hotdizzle:
Trying to help (unlocked # codes on device)

I apologize in advance if I'm posting useless info here.

I have access to all these codes on my particular retail device (they were unlocked on my device by a Samsung tech):

http://www.softwaresenior.com/blog/57-samsung-galaxy-secret-code.

If any of the information gained from these (ie. system dump, etc.) can be helpful, let me know.
[Galaxy Note 4 Developer Discussion (Devs., Only)] Surge1223:
You have hidden carrier unlocked? Hmm weird I guess you could turn seclog log on and set debugging to high in the dump menu (##9900) then restart the phone and go back into the dump menu (##9900) and select the option to save the kernel log to sdcard. That will tell us what happens at early boot, but then again I guess we could have gotten that info from people with dev edition devices.