Has anyone noticed that if you use the ES File Explorer app you can access all the files that you would be able to access if you had root access. I wonder if anyone has looked into that to try to find a root method.
You can't modify them, an exploit has to be found in the bootloader code to bypass the lock to root.
TechNyne66 said:
You can't modify them, an exploit has to be found in the bootloader code to bypass the lock to root.
Click to expand...
Click to collapse
I am able to open them and modify them. I haven't saved any of the modifications for fear of the unknown results
schultz915 said:
I am able to open them and modify them. I haven't saved any of the modifications for fear of the unknown results
Click to expand...
Click to collapse
Saving will result in an unknown error due to the lack of root. Will not work.
By
TechNyne66 said:
You can't modify them, an exploit has to be found in the bootloader code to bypass the lock to root.
Click to expand...
Click to collapse
TechNyne66 said:
Saving will result in an unknown error due to the lack of root. Will not work.
Click to expand...
Click to collapse
Is there a way to use this minimal access to developers a root?
By no means, it has nothing to do with an exploit to achieve root. It's like any root app ..........it only works if your rooted. The root partition and /system are not read protected. So pretty much any non rooted file app can read those partitions. They cannot however read /data, /cache, /sbin, etc. We all wish it was that simple.
Related
is there any chance to get premission to modify files on SDcard???
i have got excel files and i can;t save it after modyfing - "premission deneid" ....
i use 4.4 KK
HERE
https://play.google.com/store/apps/details?id=nextapp.sdfix
i don;t have root on phone ...
1krzys said:
i don;t have root on phone ...
Click to expand...
Click to collapse
You need to root your phone.
The best guide is this: http://forum.xda-developers.com/showthread.php?t=2642081
Then, you can backup your DRM keys, and unlock your bootloadear (the backup is for relocking it, and "restore" your warranty )
I didn´t want to unlock the bootloader... so only rooted the phone. Then, installed SDFix, Xposed, and System app uninstaller... and then this phone became even better
I saw a video of someone using kingroot on their verizon galaxy note 4 and they were rooted. That person was running kitkat when i tried it on my note 4 running lollipop nothing happened. Should i downgrade or wss the video fake. Is it possible to downgrade using a mac.
madchainsawer said:
I saw a video of someone using kingroot on their verizon galaxy note 4 and they were rooted. That person was running kitkat when i tried it on my note 4 running lollipop nothing happened. Should i downgrade or wss the video fake. Is it possible to downgrade using a mac.
Click to expand...
Click to collapse
Search is your Friend ....
As far as i Know it doesnt work on lollipop & only works for KitKat. it doesnt work for mine on Lollipop. Also its not a Perm Root, Root is lost upon reboot
Search the Form there is a bunch more info on it
Yup, only works on kitkat and it's temporary only.
The devs are working on a permanent solution. I personally have held off with trying king root because I don't trust it.
I am downgrading and i am going to attempt kingroot because i wanna get rid of bloatware and i never turn my phone off unless i really need to.
Sent from my SM-N910V using XDA Free mobile app
I believe there is a debloater that's been out for lollipop that doesn't need root.
I also think I've read that even if you don't reboot, over time or after messing with certain parts of the system, you'll lose root.
Debloater doesn't remove bloatware, only disables it.
Kingroot has been reported to cause random reboots, which is why I haven't tried it in spite of the fact that I rarely if ever reboot my phone either.
Also, something I've come to wonder... What good would deleting bloatware be if those no custom ROM with reworked partitions? We wouldn't be gaining any space from the ROM partition (where system apps are stored) But we can already delete all the updates for system apps (since they go in internal storage instead of overwriting the original app in ROM storage). At least this is the way I've come to understand it from using Titanium Backup on my old devices.
I didn't think king root was actually rooting your main system rom? Thought that was why you had to use multisystem and from that point you would install the rooted kitkat rom, etc..
But if kingroot does root the factory system, then you could simply root with kingroot remove the bloatware then it wouldn't matter if you lost root after a reboot. Correct?
I am not sure but i am trying to downgrade my note 4 right now and i hope it doesnt brick
Sent from my SM-N910V using XDA Free mobile app
I looked that up on xda and kit kat doesnt need root lollipop does
Sent from my SM-N910V using XDA Free mobile app
I was wondering if I went through this temp root path and modified my hosts file as well as using "SDFix: KitKat Writable SD" to give me write access to sd. Would they stay that way modified host file and write access if I hard rebooted and removed king root or SU after doing those things originally with root permissions?
sent from my SM-N910A
No they won't
drewcam888 said:
No they won't
Click to expand...
Click to collapse
Is this reply to my post regarding hosts file and sd write?
sent from my SM-N910A
amsgh said:
Is this reply to my post regarding hosts file and sd write?
sent from my SM-N910A
Click to expand...
Click to collapse
Yes it is a response to you. Write protection takes over on a reboot
drewcam888 said:
Yes it is a response to you. Write protection takes over on a reboot
Click to expand...
Click to collapse
Ok thanks. Does that also mean that the hosts file reverts?
sent from my SM-P600 RLS5.0
Everything reverts back to original
madchainsawer said:
I am not sure but i am trying to downgrade my note 4 right now and i hope it doesnt brick
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
Were you able to downgrade? Root and remove bloatware?
Sent from my SM-N910T
ubigred said:
Were you able to downgrade? Root and remove bloatware?
Sent from my SM-N910T
Click to expand...
Click to collapse
You can downgrade to NJ5 4.4 rom and get temporary root with King root, if you're on OAF. However, if you took the OTA upgrade to OF1 or above, you cannot downgrade. You stuck with LL with no way to root.
buhohitr said:
You can downgrade to NJ5 4.4 rom and get temporary root with King root, if you're on OAF. However, if you took the OTA upgrade to OF1 or above, you cannot downgrade. You stuck with LL with no way to root.
Click to expand...
Click to collapse
Damn I'm on OG5. I really can't downgrade?
Sent from my SM-N910T
I dont think kingroot is root at all.
I dont understand the term "temporary root"
Even if its temporary, changes it makes to the system should be permanent yet they go back to normal.
I tried using system app uninstaller and it said "succeeded "
I tried to use AdAway and it said "successful"
I even opened up the system/hosts file to confirm the change was made, yet after reboot everything went back to stock.
Not only that, but kingroot comes with FULL SCREEN ads that pop when you exit application that requested root access, and they are annoying playing videos and eat up your data.
I think kingroot creates virtual root environment inside RAM. Changes made inside RAM do not apply to device storage. Nothing is changed to say the very least but allot of garbage and spyware is added.
Even after uninstalling the app, its service is left behind and you gotta remove thru "Settings/applications/All"
Smart Chinese should have put their knowledge into cracking the locked bootloader instead of creating fake trash like this.
droidx2.3.3 said:
Yup, only works on kitkat and it's temporary only.
The devs are working on a permanent solution. I personally have held off with trying king root because I don't trust it.
Click to expand...
Click to collapse
I was playing with my buddy's note4 (sm-n910v) this evening and I used Kingroot's Purify app. After running it, I went through every option and it finally gave me a link to the Kingroot.net download (XDA's wouldn't parse for me).
I installed Kingroot and ran it... fail.
Rebooted
Ran Purify again, followed by Kingroot.... Root Successful!
Ran RootChecker..... haha... tripped the knox.... auto reboot. (Note to self... don't run RootChecker)
Ran Kingroot.... much faster root success this time!
Verified root by turning on the root explorer in ES File Explorer's options.... Root was asked for and granted.
Instead of removing the bloatware using ES File, I opted to give the Purify app another try in hope of getting root to stick.
That's when I came Purify's 'Debloater' app.... It started ok, so, I handed my buddy his phone and told him."Better get some while the getting is good!".... He had about 30 apps checked when I stopped him and suggested he make a back up before he does anymore!
Apps uninstalled successfully and my buddy rebooted (ok...I guess we're done).
After reboot.. root was gone but, so were the 30+ apps!
Long story short.... Getting root is possible... You just have to get root when you need it and be decisive in your actions.... Remember anything that trips the knox and try to avoid it!... Work Purify and Kingroot back and forth like a couple of wedges... I think I was close to getting root to stick permanently but, my buddy had to go home and he took all the toys with him
I guess the next step is getting rid of, disabling or re-configuring the knox.... So, please read up on the knox system change detect-o-matic before trying to uninstall it... Do it right and you'll be a champ!
But... if you automate it for everyone with a small program and you'll reach 'Hero' status for sure!
Oh yeah.... That Note4 was running Lollipop 5.1.0 (or 5.0.1?... I didn't pay much attention)
Hope that helps
<8^)
P.S. Sorry if I posted incorrectly ... I'll get it right one of these days!
I found the A1's camera pretty good sometimes, but the stock camera is quite useless, and no other 3rd party app seemed to be able to make good use of the camera.
Is there any way to get a good camera app, perhaps the Google camera, or the Samsung note 8 camera app?
U can't, u have to edit the build prop to enable camera HAL either it would not work.
Roykooiman said:
U can't, u have to edit the build prop to enable camera HAL either it would not work.
Click to expand...
Click to collapse
In that case, how would you suggest on improving the camera? The camera hardware is itself quite capable, but the software is not upto the mark.
leroyjd123 said:
In that case, how would you suggest on improving the camera? The camera hardware is itself quite capable, but the software is not upto the mark.
Click to expand...
Click to collapse
The answer is root lol, why u don't want to root it?
There is actually no root required for editing build.prop. You unlock the bootloader, then you can boot (not flash) the TWRP and mount system with W permissions. Pull the build.prop file, edit it and push it back to its place. Then you need to set the permissions of the file through the shell. As the last thing you can relock the bootloader and have the edited build.prop file without having the root.
Google it and you will find the guide.
I tested it myself. It works.
maross said:
There is actually no root required for editing build.prop. You unlock the bootloader, then you can boot (not flash) the TWRP and mount system with W permissions. Pull the build.prop file, edit it and push it back to its place. Then you need to set the permissions of the file through the shell. As the last thing you can relock the bootloader and have the edited build.prop file without having the root.
Google it and you will find the guide.
I tested it myself. It works.
Click to expand...
Click to collapse
Hi, can you post the guide that you are used for A1, because in google are many variants
mqdjo said:
Hi, can you post the guide that you are used for A1, because in google are many variants
Click to expand...
Click to collapse
Safer option is to use a Magisk module which does exactly the thing but without having to add the lines into build.prop manually and setting the permissions etc
maross said:
There is actually no root required for editing build.prop. You unlock the bootloader, then you can boot (not flash) the TWRP and mount system with W permissions. Pull the build.prop file, edit it and push it back to its place. Then you need to set the permissions of the file through the shell. As the last thing you can relock the bootloader and have the edited build.prop file without having the root.
Google it and you will find the guide.
I tested it myself. It works.
Click to expand...
Click to collapse
What about OTA after that?
mqdjo said:
Hi, can you post the guide that you are used for A1, because in google are many variants
Click to expand...
Click to collapse
Google "how to edit build.prop without root mi a1" and pick the guide posted on themefoxx website. I am not allowed to post external links [yet].
---------- Post added at 07:10 PM ---------- Previous post was at 07:07 PM ----------
nitroax said:
What about OTA after that?
Click to expand...
Click to collapse
Does not work. After downloading the proposed update I get installation error at the very beginning. Maybe after restoring the build.prop file the same way as I modified it, it might work.
Once you mount the system as read/write, you can't apply OTA. This is why it's better to use Magisk instead of altering system files directly.
maross said:
There is actually no root required for editing build.prop. You unlock the bootloader, then you can boot (not flash) the TWRP and mount system with W permissions. Pull the build.prop file, edit it and push it back to its place. Then you need to set the permissions of the file through the shell. As the last thing you can relock the bootloader and have the edited build.prop file without having the root.
Google it and you will find the guide.
I tested it myself. It works.
Click to expand...
Click to collapse
Hey there!
I just joined XDA for the sole purpose of finding this tutorial that I have seen floating around the web lately. But unfortunately, every website has a different version of how exactly this should be done. Do you know where I can find the exact steps to take in order to edit the build.prop without having to root my phone and without losing the OTA updates?
Cheers!
adrflg said:
Hey there!
I just joined XDA for the sole purpose of finding this tutorial that I have seen floating around the web lately. But unfortunately, every website has a different version of how exactly this should be done. Do you know where I can find the exact steps to take in order to edit the build.prop without having to root my phone and without losing the OTA updates?
Cheers!
Click to expand...
Click to collapse
If u edit build.prop means u will break OTA. 100%
just root guys using magisk safetynet pass through.
under magisk hide , chose the apps if you face issue against root, it will open
Rajeev said:
If u edit build.prop means u will break OTA. 100%
Click to expand...
Click to collapse
adrflg said:
Hey there!
I just joined XDA for the sole purpose of finding this tutorial that I have seen floating around the web lately. But unfortunately, every website has a different version of how exactly this should be done. Do you know where I can find the exact steps to take in order to edit the build.prop without having to root my phone and without losing the OTA updates?
Cheers!
Click to expand...
Click to collapse
Hi,
Rajeev is right. You can edit the build.prop this way. And it is going to work. But you are gonna loose OTA, because you need to mount system with write privileges through TWRP in order to modify system file.
Is it possible to unlock the bootloader, root, make some minor modifications (activation of camera api, copying fm radio apk to system folder, etc), unroot, and finally relock (flashing stock boot.img before, of course) ?
I want to have it unrooted because of bank payments, banks apps and streaming TV apps, but I would like to have proper camera and fm radio... Is it possible??
no
erunamor said:
Is it possible to unlock the bootloader, root, make some minor modifications (activation of camera api, copying fm radio apk to system folder, etc), unroot, and finally relock (flashing stock boot.img before, of course) ?
I want to have it unrooted because of bank payments, banks apps and streaming TV apps, but I would like to have proper camera and fm radio... Is it possible??
Click to expand...
Click to collapse
Not possible
erunamor said:
Is it possible to unlock the bootloader, root, make some minor modifications (activation of camera api, copying fm radio apk to system folder, etc), unroot, and finally relock (flashing stock boot.img before, of course) ?
I want to have it unrooted because of bank payments, banks apps and streaming TV apps, but I would like to have proper camera and fm radio... Is it possible??
Click to expand...
Click to collapse
How about rooting the phone with Magisk and use Magisk Hide to hide root from those apps?
Htf do you think miui camera is useless. I am a photographer. And find it quit usefull and makes full use dual lens. Have you even tried HHT? Never compare two different apps. HDR+ is google's algorithm. You won't get in miui camera. HHT is miui's thing. You won't get in Gcam. Anyways HDR+ is not mandatory, you can get it from any post processing app.
yashgumaste said:
Htf do you think miui camera is useless. I am a photographer. And find it quit usefull and makes full use dual lens. Have you even tried HHT? Never compare two different apps. HDR+ is google's algorithm. You won't get in miui camera. HHT is miui's thing. You won't get in Gcam. Anyways HDR+ is not mandatory, you can get it from any post processing app.
Click to expand...
Click to collapse
A1 camera is superb in Day light only. It can't beat Google Camera in very low light. Everyone trying Google Camera here for getting Selfie Portrait mods. That not available in A1 camera .. I am not a photographer. But i can tell as a normal user in low light Google Camera perform really better than A1 camera. May be some 3rd party apps can do that but someone loves Google Camera
I doubt this is really anything exciting but I installed MiXplorer, opened it up and I was able to browse around the root file system. Not sure why or if this is news to anyone but thought it was interesting.
bnevets27 said:
I doubt this is really anything exciting but I installed MiXplorer, opened it up and I was able to browse around the root file system. Not sure why or if this is news to anyone but thought it was interesting.
Click to expand...
Click to collapse
Can you edit anything?
Root Explorer browser does the same, but without actual root you can't edit system files.
ChazzMatt said:
Root Explorer browser does the same, but without actual root you can't edit system files.
Click to expand...
Click to collapse
Thanks!
I have an interesting idea, but I don't have enough technical skills to implement it.
I noticed that edload mode can brush all partitions without BL unlocked. So i`m think, if i can modify init_boot.img and package it into the flashing package, can I bypass the BL lock and forcibly flash root into the device?
If that available, I can own rooted devices without data loss, fingerprint also does not appear abnormal.
No. Root require a patched boot.img, so you have to get access to other partition.
To do this the unlocked bootloader is needed.
CrazyMoney said:
modify init_boot.img and package it into the flashing package
Click to expand...
Click to collapse
AFAIK this won't work because this image needs to be signed. If we can patch init_boot.img, sign it, flash it and also flash signature of this file, we might be able to relock bootloader. Try with caution: unless there's good instruction for EDL unbricking, you might end up with a bricked device without any free way to fix it.
zSyntex said:
No. Root require a patched boot.img, so you have to get access to other partition.
To do this the unlocked bootloader is needed.
Click to expand...
Click to collapse
I remember Andriod 13 need patch init_boot.img instead of boot.img. And edload mode doesen`t need anything because that used a underlying layer.
aaa.bbb111222 said:
AFAIK this won't work because this image needs to be signed. If we can patch init_boot.img, sign it, flash it and also flash signature of this file, we might be able to relock bootloader. Try with caution: unless there's good instruction for EDL unbricking, you might end up with a bricked device without any free way to fix it.
Click to expand...
Click to collapse
I think you are right. But in the past, I can make fake signature in the past, just don`t know how to deal now.
CrazyMoney said:
I think you are right. But in the past, I can make fake signature in the past, just don`t know how to deal now.
Click to expand...
Click to collapse
From the past a lot of things had changed.
Now you need to unlock the BL to get root in the correct and safe way.
zSyntex said:
From the past a lot of things had changed.
Now you need to unlock the BL to get root in the correct and safe way.
Click to expand...
Click to collapse
Maybe, but everything only by trying can step foreward. Isn`t it?
I'm just sharing my ideas, not necessarily implementing them, just discussing a possibility.