I know you guys have waited FOREVER for somebody to pick this project up.... I have, and today I preset to you...ROOT
WARNNG: THIS DOES USE A CUSTOM KERNEL
Steps:
Unlock bootloader using this TUTORIAL:
http://forum.xda-developers.com/desire-510/help/qa-bootloader-unlock-htc-desire-510-t2911491
DO NOT FLASH RECOVERY FROM THAT THREAD
Grab boot.img from here:
http://goo.gl/AlaZpI
Old Versions:
http://goo.gl/dzQ3Wi
Load boot.img into fastboot folder
run this command:
"fastboot flash boot HTC-Desire-510-64bit-Root.img"
Install SuperSU from Play Store. Select cancel everytime it asks to update. It WON'T work
VigiDroid said:
Okay first things first let's get a couple things straight. SuperSU is the APPLICATION that allows for other applications to gain root access. When you first run SuperSU it will complain that the SU BINARIES are out of date. This is not important. It claims that you need a custom recovery (typically TWRP or CWM) to install the BINARIES, or you can try install it without it. This does not work, but it doesn't matter, since the out dated BINARIES still function correctly.
It is important to identify the difference between those two to avoid confusion though. SuperSU is the APPLICATION that allows root, and SU is the BINARIES which allow SuperSU to have root access.
I had trouble at first, but after a couple of initial reboots, SuperSU functioned correctly and granted root applications access. Once you have rebooted a few times, try download "root access checker" and run it to see if it works.
Click to expand...
Click to collapse
Good job rbheromax
thanks!
Thank you soo much
---------- Post added at 05:59 PM ---------- Previous post was at 05:32 PM ----------
I have started my phone succesfully with this kernel,but no root access (i have installed supersu alredy)
(I dont have recovery on my phone)
Sorry for my english.
I'm not a programmer or expert android but by unpacking the file boot.img, there are necessary files to root
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I only checked to make sure that root could be accessed by shell. I'll upload another version with it having universal access
Sent from my XT1028 using XDA Free mobile app
rbheromax said:
I only checked to make sure that root could be accessed by shell. I'll upload another version with it having universal access
Sent from my XT1028 using XDA Free mobile app
Click to expand...
Click to collapse
Alright,thanks.
this will install su to /system as well as remove write protection
http://tempsend.com/33CE45F61D
rbheromax said:
this will install su to /system as well as remove write protection
http://tempsend.com/33CE45F61D
Click to expand...
Click to collapse
You gave me this file in private message,i have tried it and not worked,i had same problem
Edit: Its say there is no SU Binaries installed and SuperSu not installable......(i use SuperSU Free from google play)
Can anyone post a video which shows the process (and success!) of root the HTC Desire 510 64bit (EU)
Thanks
GianniDarkos said:
Can anyone post a video which shows the process (and success!) of root the HTC Desire 510 64bit (EU)
Thanks
Click to expand...
Click to collapse
Fix for root is coming soon,please be patient.
Ops ok, sorry
(I did not understand, I can not read english well)
http://goo.gl/AlaZpI
link updated in OP
it IS rooted, but you cannot update in-app using SuperSU. for some unknown reason, it wont work
use any other root managing app and you should be ok. try using koush's superuser app
Change Screen Size
Guys,
If you wanna be normaly screen size (not original sh.. screen sizes) than download this apk to your phone:
https://play.google.com/store/apps/details?id=com.nomone.resolution_changer&hl=hu
NOMone Resolution Changer (its free)
Open the app and you see
"Width" "Height" "DPI"
Change Width to 720
Change Height to 1280
Change DPI to 312
and click on apply
Or second way:
Open the app
Click on "Select device template"
and choose Motorola Moto X or Htc One X
Click on apply and you done
If you dont like this sizes,dont worry,apk will restore stock sizes after 10 sec and after 1 minutes too.
Good Luck to all.
rbheromax said:
http://goo.gl/AlaZpI
link updated in OP
it IS rooted, but you cannot update in-app using SuperSU. for some unknown reason, it wont work
use any other root managing app and you should be ok. try using koush's superuser app
Click to expand...
Click to collapse
Have you got a link please. I can't seem to find that one in particular
Burtrum57 said:
Have you got a link please. I can't seem to find that one in particular
Click to expand...
Click to collapse
Check the link in the OP? Hit the big blue download button on it and follow the instructions from the OP. In case you missed it, you have to use FASTBOOT to FLASH the KERNEL. So in other words, use this command: fastboot flash boot HTC-Desire-510-64-Bit-Root.img
VigiDroid said:
Check the link in the OP? Hit the big blue download button on it and follow the instructions from the OP. In case you missed it, you have to use FASTBOOT to FLASH the KERNEL. So in other words, use this command: fastboot flash boot HTC-Desire-510-64-Bit-Root.img
Click to expand...
Click to collapse
I've downloaded the kernal, fastboot flashed it and rebooted the phone and all is going well. Your correct supersu won't install without twrp or cwm. I have busybox installed and it is ok but a couple other apps complain that things aren't right.
Burtrum57 said:
I've downloaded the kernal, fastboot flashed it and rebooted the phone and all is going well. Your correct supersu won't install without twrp or cwm. I have busybox installed and it is ok but a couple other apps complain that things aren't right.
Click to expand...
Click to collapse
Okay first things first let's get a couple things straight. SuperSU is the APPLICATION that allows for other applications to gain root access. When you first run SuperSU it will complain that the SU BINARIES are out of date. This is not important. It claims that you need a custom recovery (typically TWRP or CWM) to install the BINARIES, or you can try install it without it. This does not work, but it doesn't matter, since the out dated BINARIES still function correctly.
It is important to identify the difference between those two to avoid confusion though. SuperSU is the APPLICATION that allows root, and SU is the BINARIES which allow SuperSU to have root access.
I had trouble at first, but after a couple of initial reboots, SuperSU functioned correctly and granted root applications access. Once you have rebooted a few times, try download "root access checker" and run it to see if it works.
You are right. All seems to be correct, I have root access, can copy, delete and move files with no problems. A couple apps do complain but if ignore them all still works well. Thank you so much. It may be a small step but it is a huge leap for what can now be done with this phone
/system/build.prop for Europe
Could someone on a European 510 please post their /system/build.prop file?
adb shell
su
cat /system/build.prop
...and since you're at it, could you post a stock (or not) TWRP backup? I know I am asking a lot, but after all I did help (in a very small way) @rbheromax in achieving root for you guys.
Thanks very much!
Related
So you want the latest Lollipop image for the 2012 Wifi Nexus 7, but no root and no TiBu is holding you back?
You can root the 2012 WiFi Nexus using WUGS Root Tool kit. Get it here -> http://www.wugfresh.com/nrt/
It's real easy to use and it walks you through what you need to do once it's installed. It will download the correct root kernel, boot image, recovery and root.
Once rooted, you can go to Play Store and download the latest TiBu. As of 11/14/2014, it has been updated to work with Lollipop. No need for the Beta version anymore.
It works. I just restored all my users apps from KK with this. Works like a charm. No issues so far.
Here's your Lollipop!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://api.soundcloud.com/tracks/78714022/download?client_id=b45b1aa10f1ac2941910a7f0d10f8e28
4.4.4 ?
Does this work with 4.4.4 ?
Thanks
---------- Post added at 03:01 AM ---------- Previous post was at 02:43 AM ----------
Oops, never mind.
Stuck on 'Searching application data .... ' forever.. :/
I flashed factory images yesterday, so my device is unlocked and I'm attempting to root it.
I've downloaded the cf-auto-root-grouper-nakasi-nexus7.zip, rebooted into bootloader, did fastboot boot the .img, it does its thing and reboots. superSU is there but no binariers :/
I've tried it several times. At one point it kept rebooting to TWRP recovery, so re-flashed boot and system.img, boots up fine, all my stuff is still there along with SuperSU but still no binaries....
Hold on, let me try again with stock recovery.
update: Having TWRP recovery flashed was causing the issue. Reflashed stock recovery in bootloader, rebooted bootloader, booted the auto root image and rebooted. SuperSU is not complaining about missing binary.
Now I'm having difficulties with Busybox. At first it said devices wasn't properly rooted. So I downloaded root checker and it said device is rooted. reopened Busybox, granted it root permissions, hit install and gave me an error about improper root installation.
Tried again and now it's saying "can't verify the integrity of the binary selected to be installed" and requesting i exit and try again.
Great! Root work on Nexus 7 wifi 2012 and android 5.0. Thanks!
Used this method last night and it installed without a hitch but I am very disappointed on how slow, Laggy and darn right unusable 5.0 is. I will wipe and go again to see if it improves but if not I will be happy to stay on KK
Eddster3000 said:
Used this method last night and it installed without a hitch but I am very disappointed on how slow, Laggy and darn right unusable 5.0 is. I will wipe and go again to see if it improves but if not I will be happy to stay on KK
Click to expand...
Click to collapse
I went and did a full wipe and that seems to have helped. Also, after the setup, are you allowing it to reinstall apps from the cloud? That can cause it to be laggy until it's done.
Remember, we are also under ART now. Under Dalvik, applications, after initially installed, would have to be "recompiled" to cache them to the Dalvik cache. This occurred when the app was launched for the first time since being installed.
Under ART, it recompiles the apps once they are installed rather than waiting for them to be launched. So, if you are having a lot of apps being reinstalled, you'll notice it might take longer to install them, and hence, since it recompiles them after install, it could slow down your device, causing it to be laggy.
thanks for the guide, it did install supersu and busybox on my nexus 7 2012 with lollipop, however, titanium backup and others apps that require root aren't working, supersu is prompting to give permission on those but they cannot execute xbin/su command
gnrsenpai said:
thanks for the guide, it did install supersu and busybox on my nexus 7 2012 with lollipop, however, titanium backup and others apps that require root aren't working, supersu is prompting to give permission on those but they cannot execute xbin/su command
Click to expand...
Click to collapse
Did you launch SuperSU after rooting? Also, you to launch Busybox and actually tell it to install.
Did you enable USB debugging in developer options? TiBu won't work without that being enabled.
If you don't see developer options in your settings, then you need to go to the About Tablet section in system settings, and then tap on Build Number seven times.
After that, then the Dev Options will show up and you can enable USB Debugging there.
After that, you'll need to go back into TiBu and then restart it (or reboot).
iBolski said:
Did you launch SuperSU after rooting? Also, you to launch Busybox and actually tell it to install.
Did you enable USB debugging in developer options? TiBu won't work without that being enabled.
If you don't see developer options in your settings, then you need to go to the About Tablet section in system settings, and then tap on Build Number seven times.
After that, then the Dev Options will show up and you can enable USB Debugging there.
After that, you'll need to go back into TiBu and then restart it (or reboot).
Click to expand...
Click to collapse
hello, the first thing i did after flashing lollipop was enabling usb debugging and then rooted with the op's recommended tool, i left it that way untill now, i really don't know what could be the cause.
Sent from my GT-I9300 using Tapatalk
gnrsenpai said:
hello, the first thing i did after flashing lollipop was enabling usb debugging and then rooted with the op's recommended tool, i left it that way untill now, i really don't know what could be the cause.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
After using WUGs toolkit to root, it tells you to first launch SuperSU and then install Busybox and ensure it's installed in /system/xbin. What they mean by that is actually launching the Busybox app and then installing all the links for the commands and such via the app itself. WUGs is just installing the apk itself but that doesn't set up Busybox. You have to actually launch the Busybox app and then tell it to install everything. That's probably why it can't find su.
Supersu just provides a way to prevent rogue apps from gaining root access without your permission. The actual "su" command is installed by Busybox.
Launch the Busybox app, tell it to install and then try again.
iBolski said:
After using WUGs toolkit to root, it tells you to first launch SuperSU and then install Busybox and ensure it's installed in /system/xbin. What they mean by that is actually launching the Busybox app and then installing all the links for the commands and such via the app itself. WUGs is just installing the apk itself but that doesn't set up Busybox. You have to actually launch the Busybox app and then tell it to install everything. That's probably why it can't find su.
Supersu just provides a way to prevent rogue apps from gaining root access without your permission. The actual "su" command is installed by Busybox.
Launch the Busybox app, tell it to install and then try again.
Click to expand...
Click to collapse
yes, i've also did install all the scripts provided by busybox, it's not the first time i've done it, that's why is really strange, maybe busybox is not correctly installing the su script (i marked the xbin folder instead of bin in busybox).
Sent from my GT-I9300 using Tapatalk
gnrsenpai said:
yes, i've also did install all the scripts provided by busybox, it's not the first time i've done it, that's why is really strange, maybe busybox is not correctly installing the su script (i marked the xbin folder instead of bin in busybox).
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Then I'm at a loss. It worked the first the time I did it and then again when I decided to do a full wipe of my device. Not sure what is going on.
You did this via WUGs correct? And, when it asked what device you had, you chose Nexus 7 2012 with the Lollipop image, correct?
Just trying to make sure you didn't miss something.
iBolski said:
Then I'm at a loss. It worked the first the time I did it and then again when I decided to do a full wipe of my device. Not sure what is going on.
You did this via WUGs correct? And, when it asked what device you had, you chose Nexus 7 2012 with the Lollipop image, correct?
Just trying to make sure you didn't miss something.
Click to expand...
Click to collapse
yeah, furthermore i reflashed lollipop twice and redo the process all over again with no luck, nevertheless, thanks for your input ?
Sent from my GT-I9300 using Tapatalk
gnrsenpai said:
yeah, furthermore i reflashed lollipop twice and redo the process all over again with no luck, nevertheless, thanks for your input ?
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Ok. Sorry I couldn't help. Hopefully, you can get it figured out.
You DO have the bootloader unlocked, correct?
iBolski said:
Ok. Sorry I couldn't help. Hopefully, you can get it figured out.
You DO have the bootloader unlocked, correct?
Click to expand...
Click to collapse
indeed, i can see the unlocked padlock when the device boots, before flashing lollipop i had a kitkat custom rom (forgot the name), so i did have to unlock the bootloader. the only thing i'm missing is the su command and i don't see it in the busybox checklist of scripts to install.
Sent from my GT-I9300 using Tapatalk
iBolski said:
After using WUGs toolkit to root, it tells you to first launch SuperSU and then install Busybox and ensure it's installed in /system/xbin. What they mean by that is actually launching the Busybox app and then installing all the links for the commands and such via the app itself. WUGs is just installing the apk itself but that doesn't set up Busybox. You have to actually launch the Busybox app and then tell it to install everything. That's probably why it can't find su.
Supersu just provides a way to prevent rogue apps from gaining root access without your permission. The actual "su" command is installed by Busybox.
Launch the Busybox app, tell it to install and then try again.
Click to expand...
Click to collapse
Wut? No, su is on the system by default. It is REPLACED by the supersu zip, with the supersu.apk to control it in Android.
Busybox has nothing to do with su.
khaytsus said:
Wut? No, su is on the system by default. It is REPLACED by the supersu zip, with the supersu.apk to control it in Android.
Busybox has nothing to do with su.
Click to expand...
Click to collapse
DOH! Don't know what I was saying there. My bad. :silly: Chalk it up to a long night last night with little sleep.
I followed the directions and everything worked. only thing now is that windows doesn't see the nexus7 so i can't copy the tibu backups over...do i need to install any additional drivers?
Storage space
Haven't seen this mentioned anywhere or maybe I'm not searching properly. I have the 16GB model and my storage is now down to 6GB, is there anything I can do to fix that? I used Wugs toolkit to install twrp but I can't find the folder in my internal storage.
Dear Developers
This in to bring to your kind notice that I have MotoG-2014 [2nd Gen] with me.
I recently rooted it successfully using guide given on the XDA forum itself. Post the root, I did checked using Root Checker Basic application about the fact whether I did the process successfully or not.
I did get the message: Congratulations! Root Access is properly installed on this device.
Current Device : XT-1068
Android version: 5.0.2
Once i was done with all this, I tried installing Titanium Backup[Pro version 6.1.0] but post every individual and multiple installs whenever I tried opening the application, it checks for ROOT ACCESS, which I did give every time but here I get a error stating that :
Sorry, I could not acquire root privileges. This application will *not* work! Please verify that your ROM is rooted, and try again.
This attempt was made using the "/system/xbin/su" command.
Now i don't understand why does this happen with Titanium, when Root Checker Basic application shows me Rooted, and I can also install
"Viper4AndroidFX" application which too requires phone to be rooted at the very first place.
I do not wish to reinstall the ROM again, since I did it properly with full clean swipe & cache + data properly cleaned at the first place after i bricked the phone last night.
[ UPDATED POST ]
The problem of Titanium backup arrives only when I am on OS version Lollipop 5.0.2. The titanium despite having root access doesn't surpass the Error on this OS.
I am sure of this statement, since due to some minor issues, I had to revert my Firmware back to STOCK version 4.4.4 and on that i got both the Root access and even the titanium worked perfectly fine.
Last night i re-updated my phone again to Lollipop 5.0.2 and as soon as I tried installing the Titanium Backup, I encountered the same error.
I guess its because of the OS version.
I am in no mood of reverting back to STOCK OS because I love Lollipop UI but how to resolve this Titanium Backup issue.
Can you guys HELP me please. !
Waiting for a response.
Thanks & regards.
Check to make sure you have the Super SU app by Chainfire app installed. When you open Titanium are you getting a notification from Super SU to allow it root access? When you open Super SU app, in Settings is it set to prompt for apps requiring root?
Tel864 said:
Check to make sure you have the Super SU app by Chainfire app installed. When you open Titanium are you getting a notification from Super SU to allow it root access? When you open Super SU app, in Settings is it set to prompt for apps requiring root?
Click to expand...
Click to collapse
Yes Its from Chainfire since, its visible when i open the settings option in the application. Yes if i install titanium and then start it, SuperSu does ask me permission and I clearly do remember that I have always clicked on "GRANT". Still the error is same no matter what I do & no matter how many times I uninstall and reinstall TB.
See the below screenshots just for reference purpose:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Help me please.
Response awaited.
Thanks & regards.
Try installing the free busybox app from Play. When you first run it, you have to let it run through your system and then choose smart install. It may take a couple of minutes for it to finish scanning your system. Reboot after you install.
Tel864 said:
Try installing the free busybox app from Play. When you first run it, you have to let it run through your system and then choose smart install. It may take a couple of minutes for it to finish scanning your system. Reboot after you install.
Click to expand...
Click to collapse
Installed the free busybox application as you told me to do. Here is the supporting screenshot :
This screen (mentioned above) came when I simply installed and started the application, had not restarted the phone yet.
However, when I restarted my phone and then started this application, I get this screen(below) :
Is it still possible since I recheched with Root Checker again and I got this screen :
P.S. - I have ROM TOOLBOX LITE too installed on my phone, and if my memory serves me right, its an application that too requires a ROOT on the device
By any chance Is it a case of "SOFT ROOT " . . ?
I just read about this somewhere while searching for this issue. So I ask & what can be done in this issue. ?
I personally never experienced nor did hear about such kind of a problem. So please HELP. . .
Response awaited.
Thanks & regards
If it were me, I would make sure I had the latest SuperSU zip, boot into TWRP recovery, clear dalvik/cache, flash Super SU again, clear dalvik/cache and reboot.
I would do what @Tel864 posted.
About Titanium: There is a version 7 out (sry no link,forgot where I got it from),Titanium 6 neither worked on my phone after rooting.
Sent from my XT1068 using XDA Free mobile app
Tel864 said:
If it were me, I would make sure I had the latest SuperSU zip, boot into TWRP recovery, clear dalvik/cache, flash Super SU again, clear dalvik/cache and reboot.
Click to expand...
Click to collapse
Ok let me try this way, and if I am not wrong. SuperSu v2.46 is the latest one only since everywhere i see this only.
Hope it helps me. Its weird though to see such kind of an issue cropping up for the first time ever.
Will respond back soon.
UPDATE -
I still see the same errors. Root Checker Basic shows my phone as rooted. TB produces the same error [ as mentioned in previous posts]. Couldn't bypass even after clicking on "GRANT".
Now what should I do, please HELP ME...
Response is more than awaited now.
Thanks & regards
Wolfcity said:
I would do what @Tel864 posted.
About Titanium: There is a version 7 out (sry no link,forgot where I got it from),Titanium 6 neither worked on my phone after rooting.
Sent from my XT1068 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah bro, am too giving it a try for once.
the reason why am still stuck on v6 especially this one is that brother its a pro version which i found here on xda only( though I don't remember as to which thread it was), the day i find another latest version[Pro] for TB, i would start using that.
Yeah then please do have a look, you might find that.
Waiting for response.
Thanks.
Titanium Backup Root access Issue
After upgrading I'm facing same problem in my MOTO E. I Still not find any solution!!
Any1 knows the solution?
I dont have a custom recovery to be able to flash the installation .zip file.
I do have root access, I have tried to manually by push the files to the correct location with correct permissions.
but it results in a bootloop.
I currently trying it on my Meizu mx4 with lollipop 5.0.1.
It used how to work without issues on K.K
Im trying it with the xposed-sdk21-arm-20150430.zip
with Xpossed 3.0 alpha2
Things I have tried.
http://bbs.flyme.cn/thread-245435-1-1.html
http://bbs.flyme.cn/thread-240899-1-1.html
Anyone have any ideas on how to get this working please
Thank you.
Did a quick search and found this:
http://forum.xda-developers.com/meizu-mx/general/mx4-flashing-recovery-t3102402
Hope that helps!
Djlatino said:
Did a quick search and found this:
http://forum.xda-developers.com/meizu-mx/general/mx4-flashing-recovery-t3102402
Hope that helps!
Click to expand...
Click to collapse
I'm not asking for a custom recovery, I know about the situation of meizu and not being open source that way.
I'm asking for a way to install Xposed successfully without a custom recovery by manually pushing the files etc.
But thank you.
If you read that thread, you'll note that in order to flash anything to begin with, you're going to need the recovery emulator "FlashGordon".
http://forum.xda-developers.com/showthread.php?t=2250555
^Spoonfeedin'
Djlatino said:
If you read that thread, you'll note that in order to flash anything to begin with, you're going to need the recovery emulator "FlashGordon".
http://forum.xda-developers.com/showthread.php?t=2250555
^Spoonfeedin'
Click to expand...
Click to collapse
I appreciate the help, I knew a app was about that could flash .zips without recovery, I will try it out.
Unfortunately it didnt work, didnt change any files in /system
punkmonkey1984 said:
I appreciate the help, I knew a app was about that could flash .zips without recovery, I will try it out.
Unfortunately it didnt work, didnt change any files in /system
Click to expand...
Click to collapse
The alternative approach is manually copying and pasting the zip files to the appropriate folders but I don't know what permissions you have to set for each of them besides the standard 664, so I apologize for not finding a solution, but I have a tablet that is pretty much in ter same ballpark as the MX4 so I'll monitor this thread!
Djlatino said:
The alternative approach is manually copying and pasting the zip files to the appropriate folders but I don't know what permissions you have to set for each of them besides the standard 664, so I apologize for not finding a solution, but I have a tablet that is pretty much in ter same ballpark as the MX4 so I'll monitor this thread!
Click to expand...
Click to collapse
I have tried to do that also, its working on the mx4 pro, but that has a different cpu chip.
Watch the video on this thread :http://bbs.flyme.cn/thread-240899-1-1.html
It explains how to copy/paste to the correct places.
Hopefully it works for you.
punkmonkey1984 said:
I have tried to do that also, its working on the mx4 pro, but that has a different cpu chip.
Watch the video on this thread :http://bbs.flyme.cn/thread-240899-1-1.html
It explains how to copy/paste to the correct places.
Hopefully it works for you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Check out flashfire, it seems to be more active than flashgordon.
Thanks for the link btw.
Djlatino said:
http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Check out flashfire, it seems to be more active than flashgordon.
Thanks for the link btw.
Click to expand...
Click to collapse
Seems to have better support, coming from Chainfire etc, but it just results in black screen without progress.
Will keep searching for a solution tomorrow.
Ok, can get it to show installed, but after I reboot it is just resulting in bootloops.
Anyone have a solution!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
punkmonkey1984 said:
Ok, can get it to show installed, but after I reboot it is just resulting in bootloops.
Anyone have a solution!
Click to expand...
Click to collapse
Same, got it installed, but boot loops for days.
Thank you based rovo for the Safe Mode
Djlatino said:
Same, got it installed, but boot loops for days.
Thank you based rovo for the Safe Mode
Click to expand...
Click to collapse
I did manage to get it installed and working without issues.
Follow the guide here: http://bbs.flyme.cn/forum.php?mod=viewthread&tid=254959&page=1&extra=#pid3301122
Files link: http://pan.baidu.com/s/1hq1pPUs
Basic chinese-> English:
1: Extracting installation charm Andrews 5.0 toolkit installation kingroot4.0 Mobile, the phone root, generally a few minutes to resolve.
2: the tmp folder, RE Manager copied to the system root directory, modify ub.sh tick all permissions.
3: Install a terminal emulator, open a terminal emulator to enter expert mode, choose Terminal Emulation, SU checkbox ticked above,
After entering sh /tmp/ub.sh carriage return (later sh space), etc. output stop after a while you can exit the terminal emulator.
4: Install xposed installer.apk, installation charm toolbox, open frame - module check Charm toolbox restart into effect.
I got it installed by wiping my data and trying on a fresh install before doing anything else, hopefully you wont have to do that.
Try removing all xposed related apps/modules before trying and rebooting/ clear catches before.
I used superSU not King user. Ignore charm-toolbox, thats a meizu flyme related module like gravity-box.
Follow the guide, then install xposed installer, mine didnt install, so i pushed in manually to /data/app with correct permissions then rebooted. I think it rebooted first time.
But a couple of times i have had to reboot by holding the power button for 10s because its gone into bootloop when activating new modules, but after it comes back on.
I got it to work another way, but my device is completely different.
What I did was install the installer, but right after I followed these instructions:
n root browser:
go to the /data/data/de.robv.android.xposed.installer/ and create folder "conf" (permissions rwxrwxrwx)
in folder "conf" create the file "jit_reset_offset" (permissions rw-r--r--)
Download Terminal Emulator, install and open it. Then:
type "su"
type "echo 0x98 > /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset"
Reboot the tablet.
Open Xposed Installer, install framework, reboot.
Click to expand...
Click to collapse
I gave that offset a shot and it luckily worked on mine. Unfortunately, the only way of getting the "offset" code is by analyzing some lib file, which I have yet to find out how to do. That being said, you can always try 0x98 a try as it seems to work on many. The default AOSP is 0x78, and some even have it as 184.
This does, however, fix most of the issues with "unsupported" devices out there, that seems to be the solution from rovo all the time.
punkmonkey1984 said:
I did manage to get it installed and working without issues.
Follow the guide here: http://bbs.flyme.cn/forum.php?mod=viewthread&tid=254959&page=1&extra=#pid3301122
Files link: http://pan.baidu.com/s/1hq1pPUs
Basic chinese-> English:
1: Extracting installation charm Andrews 5.0 toolkit installation kingroot4.0 Mobile, the phone root, generally a few minutes to resolve.
2: the tmp folder, RE Manager copied to the system root directory, modify ub.sh tick all permissions.
3: Install a terminal emulator, open a terminal emulator to enter expert mode, choose Terminal Emulation, SU checkbox ticked above,
After entering sh /tmp/ub.sh carriage return (later sh space), etc. output stop after a while you can exit the terminal emulator.
4: Install xposed installer.apk, installation charm toolbox, open frame - module check Charm toolbox restart into effect.
I got it installed by wiping my data and trying on a fresh install before doing anything else, hopefully you wont have to do that.
Try removing all xposed related apps/modules before trying and rebooting/ clear catches before.
I used superSU not King user. Ignore charm-toolbox, thats a meizu flyme related module like gravity-box.
Follow the guide, then install xposed installer, mine didnt install, so i pushed in manually to /data/app with correct permissions then rebooted. I think it rebooted first time.
But a couple of times i have had to reboot by holding the power button for 10s because its gone into bootloop when activating new modules, but after it comes back on.
Click to expand...
Click to collapse
I have installed xposed today by a very similar way that I have made but I am not sure if xposed totally installed.
Do you think that it is really installed?
I also have tried with the method of the chinese forum and the result is the same (basicaly is the same as my procedure).
There is any module to check it is really working? As you see I dont use much xposed
iicc said:
I have installed xposed today by a very similar way that I have made but I am not sure if xposed totally installed.
View attachment 3324770
Do you think that it is really installed?
I also have tried with the method of the chinese forum and the result is the same (basicaly is the same as my procedure).
There is any module to check it is really working? As you see I dont use much xposed
Click to expand...
Click to collapse
Flyme tools still works.
Did you encounter any bootloops?
You could try this one if your having trouble (not tested myself)
http://bbs.flyme.cn/thread-258466-1-1.html
punkmonkey1984 said:
Flyme tools still works.
Did you encounter any bootloops?
You could try this one if your having trouble (not tested myself)
http://bbs.flyme.cn/thread-258466-1-1.html
Click to expand...
Click to collapse
No bootloops so far.
[emoji33] [emoji33] thats the cofface cwm, I thought it didnt worked and the project was abandoned
iicc said:
No bootloops so far.
[emoji33] [emoji33] thats the cofface cwm, I thought it didnt worked and the project was abandoned
Click to expand...
Click to collapse
I'm not sure, I think it's only temporary cwm, I think it reverts back to the stock one after a reboot.
I've seen a few threads about this, but my problem is a little different. I can edit my build.prop and save the changes. however, when I save and exit the text editor and build.prop and go back in, the changes don't stick. I'm on 6.0 with beta superuser 2.51 and elemental 3.0 for what its. anybody have any ideas?
ilanzo82 said:
I've seen a few threads about this, but my problem is a little different. I can edit my build.prop and save the changes. however, when I save and exit the text editor and build.prop and go back in, the changes don't stick. I'm on 6.0 with beta superuser 2.51 and elemental 3.0 for what its. anybody have any ideas?
Click to expand...
Click to collapse
Did you try editing with the ESFile Explorer app? Seems to me I had a similar problem till I used that with my old SGS III
OKAstro said:
Did you try editing with the ESFile Explorer app? Seems to me I had a similar problem till I used that with my old SGS III
Click to expand...
Click to collapse
tried it..."an error occurred when trying to save the file. it will not be saved"
System can't be remounted as rw by default. So boot into a custom recovery, mount system, adb pull build.prop, edit it, adb push it back, reboot.
ilanzo82 said:
tried it..."an error occurred when trying to save the file. it will not be saved"
Click to expand...
Click to collapse
Did you enable root explorer in EsFile Menu?
OKAstro said:
Did you enable root explorer in EsFile Menu?
Click to expand...
Click to collapse
You can't modify anything on system on Marshmallow. Even with root explorer, you can only read it.
istperson said:
You can't modify anything on system on Marshmallow. Even with root explorer, you can only read it.
Click to expand...
Click to collapse
funny, but wrong. i modified my build.prop just fine, among other things in marshmallow. your issue is that you do not have full root.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If all you're doing is editing build.prop, why not just flash custom recovery, mount /system, and make the changes via adb shell?
imnuts said:
If all you're doing is editing build.prop, why not just flash custom recovery, mount /system, and make the changes via adb shell?
Click to expand...
Click to collapse
or.. fix the not having root fully issue instead of putting a band aid on it.
simms22 said:
funny, but wrong. i modified my build.prop just fine, among other things in marshmallow. your issue is that you do not have full root.
Click to expand...
Click to collapse
Or maybe I don't have a custom kernel, and a custom fstab. There's not such thing as full, or less full root. Root is having a working su. Being able to mount system as rw, has nothing to do with su. The stock kernel won't boot if you rooted yout phone, you have to modify it. You can also modify your boot.img to allow mounting system to rw. It's not about how full a root is.
---------- Post added at 11:20 PM ---------- Previous post was at 11:18 PM ----------
simms22 said:
or.. fix the not having root fully issue instead of putting a band aid on it.
Click to expand...
Click to collapse
Then please post a diff here, which files to modify to be able to mount system as rw.
istperson said:
Or maybe I don't have a custom kernel, and a custom fstab. There's not such thing as full, or less full root. Root is having a working su. Being able to mount system as rw, has nothing to do with su. The stock kernel won't boot if you rooted yout phone, you have to modify it. You can also modify your boot.img to allow mounting system to rw. It's not about how full a root is.
---------- Post added at 11:20 PM ---------- Previous post was at 11:18 PM ----------
Then please post a diff here, which files to modify to be able to mount system as rw.
Click to expand...
Click to collapse
honestly, you will have to reflash marshmallow, and use a custom kernel. first time i flashed m and marshmallow, i had the same issue. i reflashed m 3 times and marshmallow twice, then it got "fixed".
---------- Post added at 05:32 PM ---------- Previous post was at 05:27 PM ----------
istperson said:
Or maybe I don't have a custom kernel, and a custom fstab. There's not such thing as full, or less full root. Root is having a working su. Being able to mount system as rw, has nothing to do with su. The stock kernel won't boot if you rooted yout phone, you have to modify it. You can also modify your boot.img to allow mounting system to rw. It's not about how full a root is.
Click to expand...
Click to collapse
ok, whatever you say.
ive been with android since September 2008, and have been through just about every issue that android can have. but all im doing here is im trying to help you out, not me. your full root does not have the ability to write to system. that in itself is not full root. root can exist not being full. its usually an error somewhere that causes it.
---------- Post added at 05:40 PM ---------- Previous post was at 05:32 PM ----------
btw, currently using despair kernel. and to those using fastboot to flash then reflashing twrp and rerooting.. there are a few twrp flashable versions of the factory inage available here as well.
so, i am using a custom kernel...elementalx 3.0. had a feeling i might not have full root access but still not sure why. i can try reflashing 6.0...for the third or 4th time?
ilanzo82 said:
so, i am using a custom kernel...elementalx 3.0. had a feeling i might not have full root access but still not sure why. i can try reflashing 6.0...for the third or 4th time��
Click to expand...
Click to collapse
yea, id try at the very least.
thx for ur help
ilanzo82 said:
thx for ur help
Click to expand...
Click to collapse
theres a twrp flashable stock image and a rom called jdx. jdx is basically stock, but its also twrp flashable. just a thought about making things easier for you, thats all.
simms22 said:
ok, whatever you say.
ive been with android since September 2008, and have been through just about every issue that android can have. but all im doing here is im trying to help you out, not me.
Click to expand...
Click to collapse
Well, you started with:
funny, but wrong.
Click to expand...
Click to collapse
That wasn't really helpful.
It might be funny, but it's definitely not wrong. And neither are you, only you are using some terms inadequately.
Technically stock kernels don't alllow you to root, or to modify system. And as you make your kernel more custom, more things you can allow.
istperson said:
Well, you started with:
That wasn't really helpful.
It might be funny, but it's definitely not wrong. And neither are you, only you are using some terms inadequately.
Technically stock kernels don't alllow you to root, or to modify system. And as you make your kernel more custom, more things you can allow.
Click to expand...
Click to collapse
you are technically right btw, considering how we found to solve the problem, and who whad it and who didnt. setting SElinux to permissive fixes the problem. some kernels set it by default, while others dont.
This worked for me:
1. Installed Busybox and did NOT reboot.
2. Removed the superuser permissions for build.prop editor
3. Opened Build.prop editor and granted superuser permissions
4. Made my changes to build.prop and pressed "SAVE" .... (When prompted to reboot, I waited about 10 seconds to push "reboot").
5.Profited
Im not sure if busybox helped, but it could have. Also, it seems that my superuser has some lag after granting permission (hense the 10 second wait).
note: I use kingroot for my superuser, and not chainfire SU.
Maybe this will help someone
hemanolio said:
This worked for me:
1. Installed Busybox and did NOT reboot.
2. Removed the superuser permissions for build.prop editor
3. Opened Build.prop editor and granted superuser permissions
4. Made my changes to build.prop and pressed "SAVE" .... (When prompted to reboot, I waited about 10 seconds to push "reboot").
5.Profited
Im not sure if busybox helped, but it could have. Also, it seems that my superuser has some lag after granting permission (hense the 10 second wait).
note: I use kingroot for my superuser, and not chainfire SU.
Maybe this will help someone
Click to expand...
Click to collapse
most, not quite all, root oriented apps need busybox in order to work properly
simms22 said:
most, not quite all, root oriented apps need busybox in order to work properly
Click to expand...
Click to collapse
Do you recommend the normal install or the smart install? I can't really find a simplified answer as to why one might be better than the other.
thanks
Please see the posted screenshot image for the problem. I just got a brand new OnePlus 8 Pro today, updated the firmware (it's current and running Android 11), unlocked the bootloader, installed my data, and rooted it. Since there is no TWRP for Android 11 for this device, I had to manually extract the current boot.img and patch it myself with Magisk Manager to root this device.
On the first boot after root, I launched Magisk Manager. The countdown timer was so fast, I did not have a chance to grant Magisk Manager root permissions. Now Magisk Manager is being denied Superuser permissions, and there are no buttons at the bottom of Magisk Manager to set Magisk Hide settings or set what apps are allowed Superuser/root.
I have googled as well as searched this forum for relevant help, and have found nothing helpful (really, I may have missed something, but I did try). How can I reset the apps allowed root permissions so that I can grant Magisk Manager the Superuser permissions it needs to function?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any help is greatly appreciated!
I already tried force stopping Magisk Manager and clearing the storage for Magisk Manager (which did nothing to solve the problem).
https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_Manager_was_denied_superuser_access
Didgeridoohan said:
https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_Manager_was_denied_superuser_access
Click to expand...
Click to collapse
Thank you for the reply. I found this article earlier (or a variant of it), and it does not appear to solve the issue. I don't have two different Magisk Managers installed. I just accidently denied the one Superuser access by not granting it Superuser access quickly enough.
The Magisk app does not need to ask for superuser access. It is the one that grants it... In other words, one way or the other Magisk is looking for a hidden Magisk app with a package name that doesn't match the one you're using.
Try deleting /data/adb/magisk.db. It'll reset everything (including granted superuser requests, etc) and you can reinstall the app and start over.
Didgeridoohan said:
The Magisk app does not need to ask for superuser access. It is the one that grants it... In other words, one way or the other Magisk is looking for a hidden Magisk app with a package name that doesn't match the one you're using.
Try deleting /data/adb/magisk.db. It'll reset everything (including granted superuser requests, etc) and you can reinstall the app and start over.
Click to expand...
Click to collapse
Thank you. This is no longer an issue (I have a new issue that is unrelated to this thread, so I'll search for the solution to it).
chriv said:
Thank you. This is no longer an issue (I have a new issue that is unrelated to this thread, so I'll search for the solution to it).
Click to expand...
Click to collapse
Just out of curiosity, did you solve it be deleting the database file?
Didgeridoohan said:
Just out of curiosity, did you solve it be deleting the database file?
Click to expand...
Click to collapse
I wish I could say, yes, but no. Long story short, I started over from a clean phone install. Unfortunately, (this part is off topic), I accidently upgraded to 11.0.4.4.IN11AA with an OTA after starting over (the version almost nobody has yet), didn't realize it, and patched a stock 11.0.2.2.IN11AA boot.img and flashed it to the boot partition. Magisk and root worked great, but WiFi and phone calls were broken. Now I'm stuck waiting to get the 11.0.4.4.IN11AA full package (Global/NA/US version of 11.0.4.4) to fix everything (by extracting the boot.img from a payload dumper).
So you mean that deleting the database file didn't work, or that you never tried it?
Sorry if I was unclear. I didn't try it. My phone was already in a state where I could not try it (and this no longer applied) before I saw this message. I am very grateful for the assistance/information.
I have the same problem. can you help me?
kas001 said:
I have the same problem. can you help me?
Click to expand...
Click to collapse
Have you already checked to see if this is the cause? https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_Manager_was_denied_superuser_access. It's definitely the best starting point.
Just for anyone else finding this thread having this issue and forgetting they told Magisk to change it's APK name to stay hidden like I did. Look for a second "Settings" app on your phone. That's what Magisk changes itself to.
SparJar said:
Just for anyone else finding this thread having this issue and forgetting they told Magisk to change it's APK name to stay hidden like I did. Look for a second "Settings" app on your phone. That's what Magisk changes itself to.
Click to expand...
Click to collapse
Yeah, I did forgot that I have changed magisk name to "settings" and magisk is working fine right now.
aleep123 said:
Yeah, I did forgot that I have changed magisk name to "settings" and magisk is working fine right now.
Click to expand...
Click to collapse
Can you please explain?
ivanov_16 said:
Can you please explain?
Click to expand...
Click to collapse
There's a setting in the Magisk app where you can rename it with a random package name, to hide it and make the app harder to detect. This will give it a generic Android icon and give it the same "Settings" (previously it would name the repackaged app "Manager").
OK I missed the prompt to grant access to the ADB shell. Where's the settings for all the applications permission grants? So that I can untick the "deny" for ADB shell. I've changed the setting from prompt to grant, and tried again. But the toast just says Shell denied superuser access.
Thanks.
--Chris
EDIT:
OK I just installed a terminal app and nuked
/data/adb/magisk/magisk.db
which allowed me to start the permission process over.
This sure seems like a brutal approach to grant/permission management. It also requires starting the whole process from scratch.
SparJar said:
Just for anyone else finding this thread having this issue and forgetting they told Magisk to change it's APK name to stay hidden like I did. Look for a second "Settings" app on your phone. That's what Magisk changes itself to.
Click to expand...
Click to collapse
You are a superstar!! I have been tearing my hair out for acouple of days now trying to work out why i could not reinstall magisk, this was exactly the solution to the problem i was facing, therefore i give you my gratitude.
I have the same issues after updating to v24.1 how can I Access to delete the duplicate apps of Magisk. It was naming to Settings.
After the 25206
Didgeridoohan said:
So you mean that deleting the database file didn't work, or that you never tried it?
Click to expand...
Click to collapse
I on the other hand tried it. Not sure if it works or not. After the 25206 to 25207 disaster, 25208 is finally normal except it can't hide itself anymore. Any solutions there? Many thanks. F Droid file explorer/Network Signal Guru also lost super user rights. Rootchecker now says it's not properly rooted
I tried deleting /data/adb/magisk/magisk.db with Termux but can't even access it as I get "permission denied" and am still seeing SuperUser and Modules greyed out. Tried sudo, was prompted to install 'tsu' package and it failed as it appears the host no longer exists