yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] Matt07211:
Can you help? I just want to examine the boot.img and su.img from the value edition to see what I am doing wrong/missing for root to work on lollipop on the normal edition of this phone.

Can you please use TWRP and just backup the boot.img (boot partition). Then using a root explorer (or using the file explorer in TWRP) go-to the /data and look for a file called su.img. Then can you please zip these two files and post then to me please, as I would like to examine them to see what I am doing wrong.

This would really help. So anyone who has a rooted value edition can you please post it to here or PM me the files.
[Miscellaneous Android Development] kniederberger:
Hi Matt. Here's the boot image and su.bin file off my Xcover3 VE. I just pulled the boot image files from a full backup I made on Friday. Let me know if this doesn't work and I'll do a backup of just boot instead.

Kevin.
[Miscellaneous Android Development] Matt07211:
Thanks really appreciate it, wasn't sure if you where ever gonna replie.
[Miscellaneous Android Development] kniederberger:
Yeah, sorry about the delay. Was trying to upload it from my phone but it kept timing out so couldn't get it to upload. Did it from a PC and it went fine.
[Miscellaneous Android Development] Matt07211:
Okay cool, sorry for the trouble I caused you ;)
[Miscellaneous Android Development] Matt07211:
Guys, just would like to say that I have finally made a step foward into lollipop root, thanks to [MENTION=7794695]kniederberger[/MENTION] providing his boot.img from the Value edition, I was able to fix up my mistakes that I was doing.

As seen in the below image, the su.img, which plays a vital role for systemless root, is know mounted under /su. Sadly when going into SuperSu app, it's unable to detect root, boot one more problem is out of the way now which is good. It's getting late, so I'm gonna continue this tomrrow/wensday/Friday. [MENTION=5716433]proguru[/MENTION] and [MENTION=7770482]akuhak[/MENTION] I am slowly getting there ; )
[Miscellaneous Android Development] kniederberger:
Well done Matt. Glad I could be of assistance and hopefully you'll get there soon.

I hope your exams went well too.
[Miscellaneous Android Development] Sonof8Bits:
Awesome! I find myself checking this thread almost daily so I made an account just to say: keep up the good work! :good: I'll be amongst the first to root this phone once you get it working. Can't wait to start de-bloating and make Tasker profiles/tasks that require root.
[Miscellaneous Android Development] Matt07211:
Sorry, its been so slow for a while, I had my HSC exams which are the biggest/most important exams I have taken, as they produce my ATAR mark, which is needed for University. Combine that with learning how all this works from Scratch and me only being limited to mobile internet (why I haven't downloaded and compiled twrp, but i belive that flashing SuperSu still wouldn't work as the normal edition (not the Value edition) has a eccentric boot.img compared to a majority of current Android devices, which is why we needed tools specifically written for our device by [MENTION=7770482]akuhak[/MENTION].) has slowed the overall progress down alot.

But since exams are over (and high school as well) I am able to devote more time to this inbetween work and my day to day life.

Side note: When I loaded LastPass I had a warning saying my device is rooted, interesting. But SuperSu still says it isn't. Might trying the system version of SuperSu tomrrow after work.
[Miscellaneous Android Development] Matt07211:
I had a quick try of the su.img you have me (ot of course won't work as the files are compiled for a different phone), and quickly tried the su command in terminal emulator, I got a su request, it of course doesn't work, but does point out that I'm heading in the right direction and that this should be done and sorted out very soon.
[Miscellaneous Android Development] abtogen:
Thank you for the work on this phone, Matt!

If you get succesful rooting Lollipop, I will send you money for this.
[Miscellaneous Android Development] Matt07211:
I accidentally delete the content in this post by accident, instead of another post. So just ignore this and move on with your life.
[Miscellaneous Android Development] Matt07211:
I am honestly stuck (I'll have to try a system superuser), I'll just lay out what I have done here and see if anyone here can give opinions.

So far I have got:

- A custom boot.img booting (Ramdisk and/or custom kernel)

- Have made the necessary modifications need to my ramdisk (patching supolicy, and some lines into the already present files, making /system noatime etc. How it's done on the SuperSu.zip script). I have also comapred it to the Value edition boot.img (once it's been modified by SuperSu) so its correct.

- An able to move stuff within /system by running a script at boot (so a new boot.img each time I want to change the script) this allows placing of files without "root" privlages.

But it seems I have trouble with the su.img. I have also modelled the content of the SuperSu.zip script and the su.img provided by a rooted value edition. When I run

cat /proc/cpuinfo

I get this output

Processor : ARMv8 Processor rev 2 (v8l)
processor : 0
processor : 1
processor : 2
processor : 3
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 half thumb fastmult edsp tls vfp vfpv3 vfpv4 neon idiva idivt
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 2

Hardware : PXA1908
Revision : 0007

Implies a 64 bit CPU, which is backed up by when building a kernel, as you use a tool chain designed to build ARM64, BUT it looks like the system is 32 bit I have tried both the su.img provided to me from the Value edition, which allows me a su prompt, which nothing happens after accepting, and then I tried using ARM64 files, becuse I think they are the correct and hopefully should have worked. They didnt, so I am at a position of somewhat granting so permission but not actually achieving it, and I am somewhat sure of what the problem is (su.img) but not the solution on how to fix it.

I'm definitely tempted to ask chainfire in his thread for help.'
[Miscellaneous Android Development] akuhak:
Ive compiled custom kernel. In fact I don't know what actually have to be done with kernel config so i didn't change anything inside - just compile it. Here it is http://rgho.st/8m2NKjMGd
[Miscellaneous Android Development] Matt07211:
I've have got the phone booting a custom kernel in the past (thanks to proguru compiling it for me). But if you can compile a kernel, can you try and compile TWRP? Should be pretty easy, as you can basebit off the kitkat and value edition TWRP, becuse all I belive needs to be done is compile it under the lollipop branch.

I am just stuck at what to do (I've got about one more idea to try (system install instead of systemless).

And the other thing I'm confused on is what format the binarys should be in, when you enter the command

cat /proc/cpuinfo

I get the info that it's a 64 bit CPU (ARM64) but running a 32 bit instruction set. The kernel of course need a to be 64 bit, but as for the binarys I believe they should be 32 bit (ARM), this is future proven by my images either up the posts (I can get a pompt, but after clicking grant, it hangs). So I am really confused on what executables to use.

I'll write up a guide on how to modify the boot.img in a couple of days, so other people can try for them selves.

Note: The usually differences between your kernel config and the stock is the anti root features disabled, TIMA security features disabled, the retail stock flag disabled l, debug symbols enabled and different kernel compile machine/name name.

To compare just use the ikconfig script in the kernels source (Scripts/Tools section), run it against a stock boot.img and compare text (diff) against the defconfig/.config files.

Edit: Here's the kernel compiled by proguru, and I can verify that it runs on the xcover 3, it's stock like yours (I haven't tried your kernel akuhak). https://www.dropbox.com/s/283a47nfgyhduzv/Image.gz?dl=0

Edit 2: I'm an IDIOT, after you posting about the kernel, i realised why it would hang when trying to grant root privlages, it was becuse i forogt to adapt my command to use the custom kernel instead of the stock one (which has anti-root enables (which stops the changing of UID to 0 (root))). So I am gonna try again later tonight with the custom kernel. Hope it works :fingers-crossed:
[Miscellaneous Android Development] Matt07211:
I've finally got root, yay. Took some effort to get around some security to grab a few files from the system that where needed, as well as the fact that I was confused on what format the binarys where needed for the phone, but enough of that, time for some proof of lollipop root. Yay. [MENTION=7770482]akuhak[/MENTION] [MENTION=5716433]proguru[/MENTION]

Notes: After all that effort root works, with a stock kernel, a modified ramdisk (and a script that runs at boot needed to get some files onto data without having "root" access (chainfires Su)) and an su.img.

Thanks to [MENTION=7794695]kniederberger[/MENTION] for providing the value edition version of the files, as it really helped, and without it this probably wouldn't of happended.

Also thanks to [MENTION=7770482]akuhak[/MENTION] for creating/modifing the tools necessary for the modification of or picky boot.img

Give me about half an hour to create a clean boot.img, package and upload the files and create the necessary install instructions.
[Miscellaneous Android Development] Sonof8Bits:
You LEGEND! :D
[Miscellaneous Android Development] Matt07211:
No problem, sorry for the longggggg wait, I had major exams, then my formal and After Party, add onto that, that I started from Scratch (almost no knowledge of how android works) as well as only my phone internet. With that all mixed togther it took me a lot time to learn and get around security features. But I'm glad I did it.

I just about to see if I can enable "compatability" more and so apps like ES File explorer and there hardcode su paths can work with systemless root. Note: this can wait untill tomorrow morning for me as I am tired.
[Miscellaneous Android Development] Sonof8Bits:
Without your efforts there would've been nothing, so no need to apologize for living your life. Looking forward to rooting this, in my opinion, great device and liberating it from the Google/Samsung bloat. Not to mention the amount of Tasker/Secure Settings automation I'm gonna unleash on it, hahah! :laugh:
[Miscellaneous Android Development] Matt07211:
I'm glad someone gonna enjoy what i have put my effort into :)

Edit: OP has been updated with relevant info and files needed for rooting the lollipop version of this phone. [MENTION=7848003]Sonof8Bits[/MENTION] have a go and report back on your success :)

Night guys, it's hitting 1am where I am and I am tired, so I'm a gonna go to sleep, any questions can wait till tomorrow.
[Miscellaneous Android Development] Matt07211:
If anyone is able to post if they had succes in rooting lollipop with my method then that would be great
[Miscellaneous Android Development] Sonof8Bits:
I didn't have the time to try it out yet. I have to download and install adb on someone else's laptop since I don't have a windows machine.

I do have a few questions.

- Any chance this won't work depending on the country it was purchased in?

- How real is the chance of bricking?

Thanks for all the work you've put in, I'll probably try it out sunday.
[Miscellaneous Android Development] Matt07211:
Okay, cool.

It shouldn't matter what country your phone is in, as I don't think that would affect boot. (Being in a different country will affect system though, but this doesn't touch that).

To summarise, the way the file is created allows for Odin to run a saftey check, If it fails, then it won't flash, so redownload the file and try again.

If it flashes, but doesn't work, it is simple and easy to fix without loss of data.

So it will either work, and if it fails you won't lose any data and the fix is as simple as flashing a stock boot.img
[Miscellaneous Android Development] Sonof8Bits:
Great! I'm familiar with Odin so that doesn't sound scary to me. Thanks! :good:
[Miscellaneous Android Development] Sonof8Bits:
[MENTION=6318002]Matt07211[/MENTION] You did it mate! It works. SuperSU is on my device, it asks me for permission if an application needs root and the root operations work.

Note: The build-in security app nags me about "unauthorised actions" and asks me to restart to undo it. I ignored it and carried on. After rebooting some more I still had root, so no problem there. Any way to get rid of that?
[Miscellaneous Android Development] Matt07211:
Great, thanks for verifying.

Now, as for the security app message your talking about, I've only ever had that once, when I flashed a custom kernel that was compiled by proguru for test. I merely rebooted and flashed an older version of my boot.img (still custom) and that error never showed up again. Since then I have dishes custom boot.img's (even with custom kernels) and have not had that image show up.

So you can either re-flash the kernel via Odin, or flash stock, and then flash the kernel back again.

Other then that, try going into the app and cleary/turning off any settings that look like the cause. Or clear the app data.
[Miscellaneous Android Development] proguru:
[MENTION=6318002]Matt07211[/MENTION] Thank you and congratulations on the successfully rooting the xCover3!

Maybe I will also try flashing this at some time. So, rooting won't reset the device and no need to reinstall everything?
[Miscellaneous Android Development] Matt07211:
Yep, correct on every account. The device won't reset, and no data loss, and no need to reinstall everything. If it where then the device in typing from now would happen been wiped numerous times, but it hasn't its still like it been since I've got it.

Edit: I wouldn't mind trying arise sound mod (http://xdaforums.com/android/software/r-s-e-sound-systems-auditory-research-t3379709/) But I've gotta backup my phone before hand.
[Miscellaneous Android Development] Sonof8Bits:
I tried clearing the cache, didn't do the trick. There's no setting involved. Could it hurt to remove the app? It's "Smart Manager". I don't know about the reflagging and flashing things but I'll look into it.

Here's some things I've noticed, if you want/need such data:

- Secure Settings doesn't recognize that the device is rooted. I guess that has to do with the 'systemless' thing I keep reading about?

- There's a folder of pre-installed apps in /preload/Common_app/ that remains read-only for some reason. Weird huh?

Never mind, had to tick remount in FX file explorer. My bad..

So far the biggest challenge is finding all the apps I want to get rid of. Various Samsung/Google apps are not in /system/app it seems.

It won't reset anything. Go on and try it!
[Miscellaneous Android Development] Nosfay:
Hi,

I'll give a try but first, I need to know if my data will be erased?

Thanks you anyway for your work :D

Edit : didnt see tha last post, so I'll try right now
[Miscellaneous Android Development] Matt07211:
Sorry, auto correct got me, it was meant to be "reflash" not "reflag", ive changed the above post to fix it.

Don't know about removing smart manager, have a Google, backup the phone and try, report your results (probably try this after trying to reflash the boot.img)

Reason why it secure sttings won't work is becuse it had a hard coded path to the su file. But with systemless root, the placement of the file is different, therefor the app is unable to find it. ES File Explorer Pro has the same problem, SuperSu has a comparability mode which should fix this, I'm planning to try and implement that tonight. So id you can wait a few more days, that problem should be fixed.

As you can see in my screenshot, preload is its own separate partition. So your probably can try the remount command and remounting it as read/write.

Note: This is a storage are for the app, it's not the app it's self, the app (if you want to uninstall) will be in the /data area of the phone. So I recommend to leave this alone, as it won't give you any more space anyway.
[Miscellaneous Android Development] Matt07211:
No data will be lost.You will be fine to flash this via Odin.
[Miscellaneous Android Development] Sonof8Bits:
But of course! :) Thanks for everything so far.
[Miscellaneous Android Development] Nosfay:
Thank you! And it was pretty easy to do it :o
[Miscellaneous Android Development] Matt07211:
No problems, I did all the hard lifting to get it working, so it would be easier for everyone else :)
[Miscellaneous Android Development] Sonof8Bits:
Hi everyone, just reporting on some things here. Feel free to ignore this message.

- Power Toggles asks for root.

- Tasker asks for root.

- Secure Settings doesn't (will be fixed by Matt later)

- More "junk" apps can be found in /system/priv-app/

- If you also get those annoying "Unauthorized actions have been detected" notifications after removing bloatware simply remove SecurityLogAgent.apk* and possibly Smart Manager**. I already removed the latter before I removed SecurityLogAgent so I can't be sure right now if that's needed.

*Do make a backup of apps before you delete them.

** Removing Smart Manager means you lose app optimisation, the battery saving feature Samsung has implemented. The battery screen in settings changes to the usage screen.
[Miscellaneous Android Development] Matt07211:
Even with an tasker, and an older version of android (2.3.6), it took some effort to get the grant root prompt to show up for the app.

Be careful when deleting apps from /system/priv-app/

I'll have a look into the pesky warning and updated OP as necessary. As I've stated in another post, I've only ever had that warning once. Also did your smart manager look like this in the screenshots below?

If anyone has the app still installed and getting the warning, tell me so I can debug this problem.
[Miscellaneous Android Development] Sonof8Bits:
That's the one!
[Miscellaneous Android Development] Matt07211:
I meant, did it say "device security" "deactivated"?
[Miscellaneous Android Development] Sonof8Bits:
Yes. Never activated anything knox or security related since I was hoping we'd get root someday and didn't want Samsung to prevent me from trying, heheh!

I just got Tasker to ask for root access by issuing a 'run shell' command and ticking "use root".
[Miscellaneous Android Development] Matt07211:
Cool, that eliminates one thing for me. Also, glad you got tasker to get root.
[Miscellaneous Android Development] JonHue:
Hi,

i just rooted my Xcover3. Thanks a lot!

I got the Security Warnings every few minutes since rooting.

I attached some Screenshots for you.

(Sorry that they are in german but i think that shouldn´t be a problem.)

How can I deactivate the SmartManager?

Thanks for your Work!

Edit:

I´ve never used something like Knox...

The Phone also was rooted before with Kitkat.
[Miscellaneous Android Development] Matt07211:
Can you try flashing the boot.img again, or can you try this http://xdaforums.com/showpost.php?p=67829724&postcount=7

Please report back if it works ot not. You also can try what Sonof8bits did, and just remove the app fully (if it's annoying you enough.)
[Miscellaneous Android Development] ascottt:
Hi guys, I do feel love for what you've done, lots of thanks :)

Btw, I get stuck at 2), cmd returns "no such file or directory", I put the unzipped files into the folder where adb.exe is stored, but nothing happened, same error again. What should I do?
[Miscellaneous Android Development] Matt07211:
Folder layout should be like this.

FOLDER WITH ADB INSIDE

- ADB.exe

- su.img

- Superuser.apk

Note: the above folders should all be in the same directory. NOT in sub folders.

Also make sure you've typed out everything correct (or copy the code)
[Miscellaneous Android Development] ascottt:
Nope :rolleyes:

adb.exe is in C:\adb\adb.exe, together with AdbWinApi.dll, AdbWinUsbApi.dll and fastboot.dll. So, I copied in that folder (C:\adb) su.img and Superuser.apk and removed the two .dlls, but when I paste the code above, an error pops out sayng that AdbWinApi.dll is missing. Should I put the .dlls somewhere else to get recognized by adb without making trouble for the main purpose?
[Miscellaneous Android Development] Matt07211:
I recommended you start fresh, and you shouldn't of have deleted the .dll's.

Start fresh.

You then should have adb.exe and other miscellaneous files. Then copy su.img and Superuser.apk. making sure not to have them in a sub folder.
[Miscellaneous Android Development] Sonof8Bits:
I had the folder with su.img on the desktop. If you type out the full path to the file it'll also work. And if, like me, you're too lazy to type that out just drag and drop the su.img in the cmd command line after typing "dab push". It'll look something like this:

adb push "/path/to/folder/of/su.img" /data/local/tmp

Edit: Since I used windows it looked more like "c:/path/to/folder/of/su.img"
[Miscellaneous Android Development] ascottt:
Thank you, after some tries it works ;) Since I'm at work it took a bit to set adb and everything on mac, but now I'm stuck again because Jodin3 doesn't recognize my phone (heimdall-mac.dmg, no mountable file system), but I'll do it on my own win once back home. I'll update this post asap, thanks guys!
[Miscellaneous Android Development] Devhost97:
Video Guide - How to Root Xcover 3 VE - SM-G389F

https://www.youtube.com/watch?v=kf27dCER-OA
[Miscellaneous Android Development] Matt07211:
So you've managed to get the files onto the phone correct? Now your just tyring to flash the boot.img, correct?? But the Mac program isn't working.

Keeping going and goodluck.

If anyone can watch and verify this as a good video tutorial (I cant watch it as I don't have much mobile data at the moment) I'll add it into OP (with credits). Or it'll have to wait until I can get acces to Wi-Fi. (Tuesday, maybe?)

Other then that, thanks for making a video tutorial, helpful for people who prefer to learn visually.
[Miscellaneous Android Development] ascottt:
Edit1: after loads of googling, I realized that I had to install first heimdall 1.4.1-unofficial (on which is built Jodin3 I guess) then run Jodin3 which eventually recognized my phone. Btw, it asks me for the PIT file (never happened with Odin on win). So far I think I'll give up until I get home and try with the original Odin (the alert about PIT on Odin scares me since forever :D)
[Miscellaneous Android Development] ascottt:
All good, original win Odin didn't ask for pit, it recognized it itself, then SU needed to be updated and work is done! Tested quickly an airplane mode flow on automate and it works, I'm so happy I can have fun again with xposed and stuff, thanks a lot guys!

PS: I apologize for such a messy load of questions and edits, I'm an enthusiast whole noob about coding and stuff.
[Miscellaneous Android Development] Matt07211:
No problem that's how we all learn, make mistakes, try and fix it, ask questions. Sorry that I wasn't able to be of help though. I have only used odin, and haven't had the chance/need to use heimdall in Linux (It the Mac variation )
[Miscellaneous Android Development] Matt07211:
Edit: I've been holding off on xposed until I can backup(nandroid) my phone. This is the same reason why I haven't tried arise yet.

If anyone waiting for the compatability fix for su, I'll try something out tonight.

Edit: Sorry, seem like it double posted, I am doing it from mobile, my mistake.
[Miscellaneous Android Development] ascottt:
I disagree, you, and the other gyus out there as well, made a great work, I can never think of doing something like this, you were helpful from the beginning! About smart manager, I simply removed it with link2sd as well as all bloatware, but the security alert still kept popping out, so I deleted "security log agent" the same way, probably getting rid of that agent was enough but it was too late for smart manager :rolleyes: