Related
I have issues with my Samsung galaxy mini s5 g800f
I can fix them I just need to root my device..Help? .
I can't use a pc. I tried king root 4.5 and iroot.
Kingroot went to 60% and failed. I tried several times.
How can I root without a pc only app ?
Help?
Cause atm my kitkat is seriously buggy only works on gsm. Need new rom. Need rooting.
First time i use KINGROOT..I had to try 5 to 6 times..usually that the solution..I'm using CYANOGEN MOD 12 on my Samsung s3..with marshmallow os ..I added kingroot to give supersu app access to OS..
Sent from my SPH-L710 using Tapatalk
I have kitkat 4.4.2. I tried ten times it didn't work. I need to add a cm12 rom cause this is not letting me connect to network via 3g or 4g proper buggy n weird. Any other method without using a computer? Pls
Kingroot wont work unless you find a way to remove knox and some other related knox apps : )
Which apk is there for g800f to remove know and what's the disadvantages of this?
I have an n910t running 5.1.1., dok2. I tried rooting several times with chainfire for 5.1.1. through Odin. It goes through the process okay (or at least it seems to), and appears to work at first, but then I lose it. Root Checker verifies root, as does SuperSU, but after a few minutes it's gone. Ive installed Titanium Backup, AdAway, and AdBlock. For the most part, they don't recognize root. If they do (it takes a long time to recognize) they lose it shortly thereafter. Rebooting doesn't help. I have no idea what I'm doing wrong. Anyone have any ideas??
Just looked now. For one example, SuperSU acknowledges AdAway, but when I try to fire up AdAway, it won't work, saying it doesn't have access.
Did you install twrp and did it ask after you booted to twrp if you wanted to root the device.. if so this was a no no.. your already rooted twrp just get a little confused with the new kernels... you must remove root and reinstall supersu and when it ask when you load twrp do not root but reboot do not swipe... unless there is an easier way this worked for me...
I had the same or a similar problem. I didn't lose root completely but at times various apps were unable to gain root (after previously getting it successfully). The phone would freeze while Titanium or Root Explorer for example were waiting fruitlessly for root to be granted. It was haphazard. One time the app would work and next time it wouldn't, or another wouldn't.
Finally it got so frustrating that I installed my favorite rom on it (Tekhd). Now all is stable. I was hoping to keep it stock rooted until mm came out but I couldn't figure out what was going on so I blew it away. I had twrp on it too and would always be prompted "root not detected" but if I allowed it to install SuperSu it would loop.
Sent from my SM-N910T3 using XDA-Developers mobile app
Thanks for the replies. I tried to install twrp once, but it kept freezing. Then I tried without it. Similar behavior outcomes either way.
I'm leaning toward just swapping out ROMS as this is very annoying. Isn't that a dangerous thing to attempt if root is so unstable though?
Eric618 said:
Thanks for the replies. I tried to install twrp once, but it kept freezing. Then I tried without it. Similar behavior outcomes either way.
I'm leaning toward just swapping out ROMS as this is very annoying. Isn't that a dangerous thing to attempt if root is so unstable though?
Click to expand...
Click to collapse
you need to odin the firmware for your phone and then restart fresh
without root twrp won't install rom you will get error..
Thanks. I did start fresh with stock firmware. Tried three times. Same result each time. I just reflashed to stock this morning. I'm actually using my old GS3 until I can figure this out. I'm on AT&T's network. I bought the T-Mobile variant just so I could root and possibly test drive a few custom ROMs. I'm ticked that even root has been elusive so far!
Any other suggestions?
Eric618 said:
Thanks. I did start fresh with stock firmware. Tried three times. Same result each time. I just reflashed to stock this morning. I'm actually using my old GS3 until I can figure this out. I'm on AT&T's network. I bought the T-Mobile variant just so I could root and possibly test drive a few custom ROMs. I'm ticked that even root has been elusive so far!
Any other suggestions?
Click to expand...
Click to collapse
Make sure your using a none corrupt download and when flashing root and twrp never let the phone restart to android screen... after you root and cf autoroot reboots hold down the buttons to boot into download mode and flash twrp.. make sure to get the .tar for 3.0 twrp.. if you need it i can post and once in DL mode flash twrp and then again do not boot the phone fully boot to twrp before and make backup if needed and when it ask after your done in twrp if you wanna root do not root in twrp... if this does not work i'm not sure what else it could be ... i have rooted my note 4 five times in the last month tring different things and it has happan one time to me and i had to odin firmware...
Thanks! I'll give that a try when I get home today.
S5Sickness said:
Make sure your using a none corrupt download and when flashing root and twrp never let the phone restart to android screen... after you root and cf autoroot reboots hold down the buttons to boot into download mode and flash twrp.. make sure to get the .tar for 3.0 twrp.. if you need it i can post and once in DL mode flash twrp and then again do not boot the phone fully boot to twrp before and make backup if needed and when it ask after your done in twrp if you wanna root do not root in twrp... if this does not work i'm not sure what else it could be ... i have rooted my note 4 five times in the last month tring different things and it has happan one time to me and i had to odin firmware...
Click to expand...
Click to collapse
You rock!! It seems that took care of it. I went through the process last night, but wanted to wait a bit to see if any issues surfaced. So far, it's been perfect. Thank you!!
Eric618 said:
You rock!! It seems that took care of it. I went through the process last night, but wanted to wait a bit to see if any issues surfaced. So far, it's been perfect. Thank you!!
Click to expand...
Click to collapse
Your Welcome...
Eric618 said:
I have an n910t running 5.1.1., dok2. I tried rooting several times with chainfire for 5.1.1. through Odin. It goes through the process okay (or at least it seems to), and appears to work at first, but then I lose it. Root Checker verifies root, as does SuperSU, but after a few minutes it's gone. Ive installed Titanium Backup, AdAway, and AdBlock. For the most part, they don't recognize root. If they do (it takes a long time to recognize) they lose it shortly thereafter. Rebooting doesn't help. I have no idea what I'm doing wrong. Anyone have any ideas??
Click to expand...
Click to collapse
Or as is the case with some roms, if an app takes to long to get supersu permission, especially after a reboot, all u have to do is open the supersu app then open the app u want root for.
Sent from my SM-G935F using XDA-Developers mobile app
marseillesw said:
Or as is the case with some roms, if an app takes to long to get supersu permission, especially after a reboot, all u have to do is open the supersu app then open the app u want root for.
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
I had tried that. It was very sluggish, and would frequently drop root access altogether. Since following S5Sickness's advice it's been solid, however.
https://tapatalk.com/shareLink?url=...share_tid=2997946&share_fid=3793&share_type=t
[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - GALAXY NOTE 4 - Drivers, Root, Recovery + MORE
Sent from my SM-N910T3 using XDA-Developers mobile app
Hi.
I have a rooted G3 D855 running 5.0
I want to install snapchat, but have been unable to do so.
Here's what I have tried so far:
- using rootcloak to hide snapchat, and xposedbridge/xposedbridge.jar in commands and keywords
- logging into snapchat on a non-rooted Note 5 running 6.0, using Titanium Backup to transfer the app state to my phone. The app works for 3 seconds and then proceeds to log me out.
- i can't uninstall xposed framework without having to do it via recovery, since that's how i was able to install it in the first place and in the app itself the uninstall button is greyed out
my thinking is that the latest version of snapchat has workarounds implemented for the workarounds, and i really havent found a solution so far.
Any help would be appreciated.
edit: not using Snapprefs
No. U have to uninstall xposed. Then install snapchat, connect. And stay connect. Never disconnect.
Flash xposed and snapchat still works.
I did that and it works
Sent From my SM-N920C using Pink Hello Kitty Tapatalk ?
Can you walk me through the process of uninstalling safely?
I m not sûre cause we have different phone. But what version did u install ?What exactly the Package name pleaz
Sent From my SM-N920C using Pink Hello Kitty Tapatalk ?
It's been happening for a long time now.
You have flash xposed uninstaller package file which can be found on the same topic.
If you don't have recovery to flash, simply use some other software to flash it manually like FlashFire.
1) Download xposeduninstaller.zip
2) Flash it using recovery or FlashFire.
3) Reboot
4) Login
5) Reflash xposed framework
6) Reboot and all done.
I'd advice you to use Systemless Xposed which you can simply enable and disable anytime without having to go through all this trouble.
Sent from my D6503 using XDA-Developers mobile app
What about me, I only have root and still can't connect to snapchat
same here
Install safety net helper, if the check fails you won't be able to log in.
Sent from my Nexus 6P using XDA Labs
Now that many 5C models have the emui 5.0/nougat update, has anyone tried rooting it yet? Also is it still the case that Xposed is still not available for nougat??
yeah theres no android N xposed even abdroid 8 is coming already... i dont see point on rooting without xposed since theres no root adblock apps.
I like to install sound mods and I use lucky patcher to remove ads and get in-app stuff, freedom app as well. They all need root. Just downloaded open kirin twrp for emui 5.0. It's been deleted from xda posts but seek and ye shall find. I also have the revolution recovery twrp for nougat but although it worked for emui 5 beta, apparently it doesn't with the proper release. I downloaded superuser for emui 5.0/nougat so now I'm going to do various backups and give rooting a go.
usually there comes bug fix OTA in few weeks after android version updte, i wait till device is discontinued updates and root thn
thelous said:
usually there comes bug fix OTA in few weeks after android version updte, i wait till device is discontinued updates and root thn
Click to expand...
Click to collapse
Okay, so I was just about to root but then I see your post but can u explain in more detail please why it's better to wait for final ota. And do you know for sure if/when there will be more OTA bug fixes??
iantechie1979 said:
Okay, so I was just about to root but then I see your post but can u explain in more detail please why it's better to wait for final ota. And do you know for sure if/when there will be more OTA bug fixes??
Click to expand...
Click to collapse
waiting for official ota is good to be sure that region is correct so youre able to make calls and text, but NEM-L21 has only one region so it doesnt matter if you use official OTA or use proxy method.
Okay so I have successfully rooted my phone by flashing super user zip file through twrp! Damn shame Xposed framework is not available for nougat though but at least I can install sound mods and can use lucky patcher to get rid of ads in apps and use freedom to get free inapp stuff. Also I use root essentials and L speed app. Beggars can't be choosers :angel:
Sent from my NEM-L51 using XDA Labs
iantechie1979 said:
Okay so I have successfully rooted my phone by flashing super user zip file through twrp! Damn shame Xposed framework is not available for nougat though but at least I can install sound mods and can use lucky patcher to get rid of ads in apps and use freedom to get free inapp stuff. Also I use root essentials and L speed app. Beggars can't be choosers :angel:
Sent from my NEM-L51 using XDA Labs
Click to expand...
Click to collapse
Which TWRP and SU.zip versions did you use? And you're on B350/351 right?
SkaldfraNorden said:
Which TWRP and SU.zip versions did you use? And you're on B350/351 right?
Click to expand...
Click to collapse
I'll post the files soon.I'm on B350.
Sent from my NEM-L51 using XDA Labs
SkaldfraNorden said:
Which TWRP and SU.zip versions did you use? And you're on B350/351 right?
Click to expand...
Click to collapse
I found this : https://forum.xda-developers.com/huawei-p9lite/development/twrp-t3588356
I just tried it. Both the unofficial TWRP and the modded SuperSU seem to work so far.
Yes I think we used the same files and installation. OpenKirinHi6250 twrp and superuser.zip for emui 5.0. :good:
Sent from my NEM-L51 using XDA Labs
iantechie1979 said:
Yes I think we used the same files and installation. OpenKirinHi6250 twrp and superuser.zip for emui 5.0. :good:
Sent from my NEM-L51 using XDA Labs
Click to expand...
Click to collapse
Seems to work fine so far. But I really have no idea why this TWRP works while the official doesn't. Same about this modded SuperSU.
Zarou said:
Seems to work fine so far. But I really have no idea why this TWRP works while the official doesn't. Same about this modded SuperSU.
Click to expand...
Click to collapse
Have you or anyone else had any problems installing busy box? I tried installing busy box pro(sterricson app) and it would not install. I tried all 4 paths to install to but it failed every time. So I installed busy box pro(jrummy app) and after running a script in the app to mount read/write I was able to install successfully. Just to make sure I install to su/bin, su/xbin, system/bin and system/xbin. I ran a root/busy box checker app.and it says both installed correctly...
Sent from my NEM-L51 using XDA Labs
iantechie1979 said:
Have you or anyone else had any problems installing busy box? I tried installing busy box pro(sterricson app) and it would not install. I tried all 4 paths to install to but it failed every time. So I installed busy box pro(jrummy app) and after running a script in the app to mount read/write I was able to install successfully. Just to make sure I install to su/bin, su/xbin, system/bin and system/xbin. I ran a root/busy box checker app.and it says both installed correctly...
Sent from my NEM-L51 using XDA Labs
Click to expand...
Click to collapse
I use the busybox installer app by meefik (because it's free software) and it works fine.
Thanks Zarou and iantechie1979, I was looking for working TWRP since days.
TWRP and SuperSu worked for me too (Honor 5C NEM-L51 version B350).
snyfear said:
Thanks Zarou and iantechie1979, I was looking for working TWRP since days.
TWRP and SuperSu worked for me too (Honor 5C NEM-L51 version B350).
Click to expand...
Click to collapse
Be careful though, I and some other user noticed that restoring backups from this TWRP will result in a phone with no sound at all. I don't know if this is fixable, factory reset don't put it back to normal.
Other than that, this TWRP seemed, but I can say for sure. In any case, DO NOT RESTORE BACKUPS from this TWRP.
I haven't had any issues using Magisk until today.
I upgraded from Android 7.0 to 8.1 (I wanted to be able to use Swift Installer), now that it's been released for my device.
After flashing Magisk, the phone isn't detecting my SIM, and there's a constant error message that pops up, but it's so fast that I never have the chance to see what it actually says.
Is there a fix for this?
Samsung Galaxy J3 (SM-J327U).
17.3 was working perfectly fine on the phone running 7.0. It's broken with 8.1.
I doubt that it is a Magisk error. It is either your SIM card going bad or an issue your system.
Sent from my SM-G900V using Tapatalk
Kaliaila said:
I doubt that it is a Magisk error. It is either your SIM card going bad or an issue your system.
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
It's not a system issue nor a SIM issue. It's ONLY after flashing Magisk on 8.1. It doesn't occur on 7.0, it doesn't occur on 7.0 with Magisk flashed, and it doesn't occur on 8.1 without Magisk flashed. It's the combination of Magisk and 8.1.
Everything works fine using any other combination with Magisk, or just stock ROMs alone.
The IMEI, etc, is showing UNKNOWN after I flash Magisk on 8.1.
Are you using stock or a different rom?
Sent from my SM-G900V using Tapatalk
Kaliaila said:
Are you using stock or a different rom?
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
I'm using stock both with and without Magisk flashed. I don't use custom ROMs.
I source my firmware from Updato.
Well, just know that on other phones and different Roms that have had that exact problem, it would occur sporadically with and without Magisk being installed. In most cases it was a bug in the rom and not Magisk.
I personally do not know how it could be caused by Magisk.
Sent from my SM-G900V using Tapatalk
Kaliaila said:
Well, just know that on other phones and different Roms that have had that exact problem, it would occur sporadically with and without Magisk being installed. In most cases it was a bug in the rom and not Magisk.
I personally do not know how it could be caused by Magisk.
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
It's not possible to revert to 7.0 without a backup is it?
I would wait and see if anyone else replies first, but I think there are ways but they are not necessarily simple.
You would probably be better off asking that in a forum for your specific phone.
Sent from my SM-G900V using Tapatalk
Had the same issue, no Magisk installed. I dropped my phone a few times. Noticed sim card warning a few boot ups later. So I opened up the back and took out card and put it in again. No problem.
Same issue here. After flash Magisk 17.1 or 17.3, system doesn't detect SIM card. Android 7.1.2, MTK6580 soc. Works relatively well with the Magisk 16, however there is always the message "emergency call only" and I must manually change radio frequency. So yes, Magisk affects radio operation on some devices.
In another device with Snapdragon, no issues related.