Hello.
Apologies in advance is this is re-hashing old/well-covered ground.
Firstly, the Kernel is great - thanks!
The issue I have been experiencing recently, though, relates to permissions. Ever since performing an update last week, I have been unable to access the app; instead, I am faced with a message, reading: "You need root permissions to operate this application. Exit and try again."
So, I have tried this. I have also tried uninstalling and reinstalling, and tweaking some of the security settings. Nothing.
Again, apologies if this is posted in the wrong place.
Hope someone can assist. I'm a relative novice, so please be kind.
Thanks.
Perkin.
warbeck said:
Hello.
Apologies in advance is this is re-hashing old/well-covered ground.
Firstly, the Kernel is great - thanks!
The issue I have been experiencing recently, though, relates to permissions. Ever since performing an update last week, I have been unable to access the app; instead, I am faced with a message, reading: "You need root permissions to operate this application. Exit and try again."
So, I have tried this. I have also tried uninstalling and reinstalling, and tweaking some of the security settings. Nothing.
Again, apologies if this is posted in the wrong place.
Hope someone can assist. I'm a relative novice, so please be kind.
Thanks.
Perkin.
Click to expand...
Click to collapse
Are you using SuperUser or SuperSU?
I think there is a solution. Can you try to go to SuperUser or SuperSU on your phone and make sure Franco's app is recognized to accept root access. Also try to click on Franco's app and click 'forget', exit SuperSu or SuperUser and go to the application. It should prompt you to accept root access. Accept it and see how it goes from there. Make sure SuperSu or SuperUser is updated.
obvious question.. are you sure that you have root? you dont need root to flash and run a custom kernel, only to control root apps. also, are you using superuser or supersu? flash this in your custom recovery, it should fix your problem http://download.chainfire.eu/314/SuperSU/UPDATE-SuperSU-v1.20.zip
Related
I use the 1 click root program to root my droid x. then i got an ota update and the root stop work... i click the unroot and the phone restart...phone came back on but still have superuser on it....i try to reroot it say done but none of the rooted apps are working...it never ask superuser to allow...If i open the superuser app it never have anything in it...Could someone help me out to get my phone rooted and apps to working..Thanks
sdgills said:
I use the 1 click root program to root my droid x. then i got an ota update and the root stop work... i click the unroot and the phone restart...phone came back on but still have superuser on it....i try to reroot it say done but none of the rooted apps are working...it never ask superuser to allow...If i open the superuser app it never have anything in it...Could someone help me out to get my phone rooted and apps to working..Thanks
Click to expand...
Click to collapse
The superuser.apk just doesnt remove when you unroot. Nothing is working as you didnt re-root.
If you want root again, simply root it again and you will be good.
I rerooted it over and over and still didn't w
ork.
Follow the manual rooting process and it will work. I promise.
Same thing happened to me but I had mine re-rooted within 5 minutes.
I NEVER trust those one click apps unless they come from UnrEVOked.
i have try different ways and still didnt work...could someone please help...
Honestly brother, you are giving people nothing to work with. You just say it didn't work. The manual root method will work, so as stated above use that. If you are saying you did use that method, then please describe where it is failing and what things look like. Post the link to the manual method that you have used, there are a few, which did you try, what steps did you follow?
Also, what do you mean it doesn't work/ You said you went into the superuser app and nothing is there. Well, I am confused as nothing is supposed to be there. The app does nothing when you click into it. It only goes into effect when you download and install a program that needs root. (an example is root explorer) When you install that app, it will open up superuser and ask for root permission and you can click to remember, etc and give it access. Explain what you mean by its not working......Unless you have apps that already have supervisor privs
i went to youtube....... when i type in the command ./exploid[/B it say denied.....Ok when i download rooted apps and try to open the apps superuser never come up for i can click allow....none of my rooted app ask for root permission. When i use the one click root process it say my phone have been rooted...
Follow the ROOT instructions in this post and in the links on that post.
http://forum.xda-developers.com/showthread.php?t=732411&highlight=root
sdgills said:
i went to youtube....... when i type in the command ./exploid[/B it say denied.....Ok when i download rooted apps and try to open the apps superuser never come up for i can click allow....none of my rooted app ask for root permission. When i use the one click root process it say my phone have been rooted...
Click to expand...
Click to collapse
You might have to try the . Exploid command a few times before it will prompt you for the password, TRY AGAIN! I had to run that command several times before it showed the password prompt.
when i get to the step i got to type ./exploid it keep sayin permission denied...I have try over and over still not working..can someone please help...
sdgills said:
when i get to the step i got to type ./exploid it keep sayin permission denied...I have try over and over still not working..can someone please help...
Click to expand...
Click to collapse
OK, I am going to try and help but only if you post what you have done, what you are following, etc. You cant make a blanket statement and expect people to know where you are at.
What files are you using, are you using the root that I linked you too? How are you typing things in? Dont put the "" around the commands like its typed, just type.
Did you in fact set up ADB correctly? When you push in step 2, what happens? When you go to adb shell after that, what happens, when you change directory's to sqlite_stmt_journal in step 4 what happens? etc.
If you want help man, you gotta be specific. This is why you are not getting a lot of replies.
Hi all,
I'm using the latest build of quarx cm10 image, 20130110.
I've got an app that only runs on unrotted devices (Excitor DME).
In the past I was able to use SuperOneClick 2.3.3 to unroot my defy again after having installed an update. Now however it stopped working, but it's dependened on the quarx image. In older images that functioned smoothly, now it just stops.
Superoneclick now also hands out a warning: "Automatic version check failed. Is your OS version 2.0 or higher?"
Now I'm not dependend on SuperOneClick, it was just a simple tool I used. If there's another way I can unroot my Defy, I'd be glad to learn from you.
Nevertheless I attached the window output from SuperOneClick to this post.
Thanks for your help in advance
Alex
Hi,
could someone please just point me to the right direction?
Maybe I've overseen the obvious but please give me a hint on how to solve this.
thanks a lot!
nightmare devil said:
Hi,
could someone please just point me to the right direction?
Maybe I've overseen the obvious but please give me a hint on how to solve this.
thanks a lot!
Click to expand...
Click to collapse
I dunno if superoneclick can manage with custom ROM. You can try one of the apps which can do the root/unroot from inside but I am not shure if work.
pgreed said:
I dunno if superoneclick can manage with custom ROM. You can try one of the apps which can do the root/unroot from inside but I am not shure if work.
Click to expand...
Click to collapse
If someone's interested in it, the solution for me was to use the "SuperSU" app. Installed it, removed root access inside the app, uninstalled the app and that's it. DME is now working as expected.
Also tried "Hide my root" but this didn't help at all.
Cheers!
nightmare devil said:
If someone's interested in it, the solution for me was to use the "SuperSU" app. Installed it, removed root access inside the app, uninstalled the app and that's it. DME is now working as expected.
Also tried "Hide my root" but this didn't help at all.
Cheers!
Click to expand...
Click to collapse
Hi I've tried using SuperSU and it didn't worked.
I've also made sure that the Kernel I was using doesn't re-root the device on boot.
DME is still detecting root access
I'm using cyanogenmod 9.1
Which rom are you using ?
Can please someone else help on bypass dme excitor root detection?
Thanks in advance!
Hi I'm using Quarx' latest CM10 image (http://forum.xda-developers.com/showthread.php?t=1768702)
I installed Super SU and in the propertys I found an option (sorry, unsure what it was called exactly) to uninstall root. I hit that option and it also uninstalled Super SU. Finally, DME didn't recognize any sort of root any more.
See if you can find that option as well and use it the way described. If it's not working for you, it might be something within the kernel/mod/image you're using. Maybe you should give Quarx mod a try, it's working quite well! :fingers-crossed:
Hey Guys,
I recently bought a Nexus 7 from ebay. The guy I bought it from had put Paranoid Android 3 on it. I am cimplete noob and do not know how to root or flash.
I just did something which I dont know how to correct.
GooManager kept telling me there was an update which when tapped on, would bring me to the .zip file i was supposed to dl.
I recently went into GooManager and denied permissions and then quickly re enabled them in supersu but now when ever I get the update prompt it brings me to the GooManager home screen with a message that says "GooManager has been granted super user permissions for an inactive shell"
What did I do wrong and do you have any idea how I can:
1. Fix this error
2. Go about updating the Nexus 7 to the newest version of paranoid
3. Can Someone link me to the full instructions on how to get the newest paranoid 3 on my nexus 4?
Thanks a ton
Josh
Josh5321 said:
I recently went into GooManager and denied permissions and then quickly re enabled them in supersu but now when ever I get the update prompt it brings me to the GooManager home screen with a message that says "GooManager has been granted super user permissions for an inactive shell"
What did I do wrong and do you have any idea how I can:
1. Fix this error
2. Go about updating the Nexus 7 to the newest version of paranoid
3. Can Someone link me to the full instructions on how to get the newest paranoid 3 on my nexus 4?
Thanks a ton
Josh
Click to expand...
Click to collapse
1. there is no error
2. launch goomanager, hit check for updates, when it alerts you, let it down load and flash
3. go to the nexus 4 forum, there is a thread dedicated to Paranoid Android there.
Pirateghost said:
1. there is no error
2. launch goomanager, hit check for updates, when it alerts you, let it down load and flash
3. go to the nexus 4 forum, there is a thread dedicated to Paranoid Android there.
Click to expand...
Click to collapse
but in the past when I would click on the update notification it brought me straight to the download file. now it just brings me to the goomanager main screen.
reboot the device and try again. or you can go in and clear out all data and cache for goomanager in your settings/apps/goomanager page
I did a reboot and then cleared data and cashe and the notification just vanishes when tapped. Not sure how this happened. Can anyone link me to the latest PA 3 link to dl. ill just do it manually and maybe it will correct itself in the future.
Josh5321 said:
I did a reboot and then cleared data and cashe and the notification just vanishes when tapped. Not sure how this happened. Can anyone link me to the latest PA 3 link to dl. ill just do it manually and maybe it will correct itself in the future.
Click to expand...
Click to collapse
open the NEXUS 7 ORIGINAL DEVELOPMENT FORUMS and download yourself, or open GOOMANAGER and BROWSE COMPATIBLE ROMS...
I have an associated question: does GooManager require the separate SuperSU app to be installed?
My device (a Motorola Xoom) is supposedly rooted, but SuperSU fails to install and GooManager can't get root permission. It's frustratingly difficult to tell (on this device at least) if there's proper root access - one checker app tells me the tablet is rooted, others say it isn't.
TyneBridges said:
I have an associated question: does GooManager require the separate SuperSU app to be installed?
My device (a Motorola Xoom) is supposedly rooted, but SuperSU fails to install and GooManager can't get root permission. It's frustratingly difficult to tell (on this device at least) if there's proper root access - one checker app tells me the tablet is rooted, others say it isn't.
Click to expand...
Click to collapse
Hi, TyneBridges...
Well, I've never used GooManager myself... but the apps description on PlayStore certainly suggests you do need to be rooted to be use it.
You're a long way from the Motorola Xoom forums (wherever they may be)... but try, from PlayStore, running some app that requires root... like Titanium backup, or perhaps better, Android Terminal emulator (by Jack Palevich)... run it, and type...
Code:
su
If you're NOT rooted, you should see something like this...
Code:
$su
su: not found
$
-------------------------------------------------------
One last thought that's just occurred to me.... you may actually already BE rooted (ie., have the SU binary installed in /system/bin or /system/xbin or wherever)... but you may be just missing the SuperSU app itself (and which 'manages' the apps you grant root to). This is has happened to me, several times, when re-rooting... for reasons which remain a mystery.
But you can download it from PlayStore, here...
https://play.google.com/store/apps/details?id=eu.chainfire.supersu
If you have some root SU binary installed, then Chainfire's SuperSU app should detect it... and either replace it, or update it.
Anyway... just some thoughts.
I really have no idea what other technical issues/problems there might be rooting a Motorola Xoom. And so you should hunt out the XDA forum for your specific device for more information... I'd be very surprised if there wasn't one.
Good luck.
Rgrds,
Ged.
GedBlake said:
Hi, TyneBridges...
...
One last thought that's just occurred to me.... you may actually already BE rooted (ie., have the SU binary installed in /system/bin or /system/xbin or wherever)... but you may be just missing the SuperSU app itself (and which 'manages' the apps you grant root to). This is has happened to me, several times, when re-rooting... for reasons which remain a mystery.
But you can download it from PlayStore, here...
...
Click to expand...
Click to collapse
Thanks for the reply. You imply that the SuperSU app *is* needed but that's the one that I've tried, and failed, to install. It just keeps telling me that the binary needs to be updated then, when I accept that, a pause and "Installing" followed by "Installation failed". I've tried the terminal program you suggest
su
Gives:
Permission denied
...so it appears that the tablet is not correctly rooted, but I don't know what the problem is.
--
John
TyneBridges said:
Thanks for the reply. You imply that the SuperSU app *is* needed but that's the one that I've tried, and failed, to install. It just keeps telling me that the binary needs to be updated then, when I accept that, a pause and "Installing" followed by "Installation failed". I've tried the terminal program you suggest
su
Gives:
Permission denied
...so it appears that the tablet is not correctly rooted, but I don't know what the problem is.
--
John
Click to expand...
Click to collapse
Hi, again John...
I'm afraid I'm a bit out of my depth with the Motorola Xoom... I know absolutely nothing about it. Sorry.
Here's where you should really be asking...
http://forum.xda-developers.com/motorola-xoom
...if anybody can solve your problem, then that's where you're likely to find them.
----------------------------------------------
If you can install a Custom Recovery like TWRP or CWM on your device, then it **SHOULD** (theoretically) just be a case of flashing Chainfire's UPDATE-SuperSU-v1.94, via that Custom Recovery.
On Nexus devices, you use FASTBOOT to flash a Custom Recovery.... on Samsung Devices, you need something called Odin to do likewise.
Once you have a Custom Recovery installed, rooting should be a piece of cake.
Problem is, I have absolutely no idea how to get such a Custom Recovery installed on a Xoom.
Do a bit of research... XDA is a vast repository of considerably more knowledgeable people than myself... and somebody is likely to know something.
Good luck.
Rgrds,
Ged.
Someone tell me what it is. I wanna keeo root, lol, dont feel like going through all that
From online research, It's just to fix some bugs and a slight performance increase. I don't know if it will break root because I'm not rooted
Sent from my C6916 using XDA Premium HD app
I do have root, so I can report. I just installed it and am going through the rebooting process now. Notes:
* My custom boot animation did not change. This looks promising so far.
* "Android is upgrading..." message. Now to sit and wait as 139 apps get optimized.
* None of my XPosed modules kicked in, nor did DashClock load as my lockscreen widget. Hmm. That's less promising.
* SuperSU launches. Auto-start items are triggering Toast for being enabled with elevated permissions. This looks better.
* Checking XPosed. Says inactive. Updating and rebooting.
* Everything looks good. All my XPosed modules trigger. Root still active.
I can't find anything immediately apparent as present in the update, but the fact that it doesn't break root is good enough for me right now.
mariussilverwolf said:
I do have root, so I can report. I just installed it and am going through the rebooting process now. Notes:
* My custom boot animation did not change. This looks promising so far.
* "Android is upgrading..." message. Now to sit and wait as 139 apps get optimized.
* None of my XPosed modules kicked in, nor did DashClock load as my lockscreen widget. Hmm. That's less promising.
* SuperSU launches. Auto-start items are triggering Toast for being enabled with elevated permissions. This looks better.
* Checking XPosed. Says inactive. Updating and rebooting.
* Everything looks good. All my XPosed modules trigger. Root still active.
I can't find anything immediately apparent as present in the update, but the fact that it doesn't break root is good enough for me right now.
Click to expand...
Click to collapse
I had a similar experience, except that Xposed is still not active. It constantly says "The latest version of Xposed is currently not active." I have completely uninstalled/reinstalled to no avail.
Everything else requiring root is working, however.
TrunkleBob said:
I had a similar experience, except that Xposed is still not active. It constantly says "The latest version of Xposed is currently not active." I have completely uninstalled/reinstalled to no avail.
Everything else requiring root is working, however.
Click to expand...
Click to collapse
I had that happen recently; after SuperSU updated it wasn't properly prompting for XPosed to gain access. I had to change SuperSU settings to allow the prompt to generate and be on top of any window and clear out the XPosed settings within. On the next open, all the prompts generated and I was able to grant access again.
mariussilverwolf said:
I had that happen recently; after SuperSU updated it wasn't properly prompting for XPosed to gain access. I had to change SuperSU settings to allow the prompt to generate and be on top of any window and clear out the XPosed settings within. On the next open, all the prompts generated and I was able to grant access again.
Click to expand...
Click to collapse
How did you install it easily, i keep getting could not be verified
mariussilverwolf said:
I had that happen recently; after SuperSU updated it wasn't properly prompting for XPosed to gain access. I had to change SuperSU settings to allow the prompt to generate and be on top of any window and clear out the XPosed settings within. On the next open, all the prompts generated and I was able to grant access again.
Click to expand...
Click to collapse
I just did all that and got SuperSU to re-prompt. Xposed still says it is not active.
I just noticed something else weird; as mentioned before, any other apps that require root are working, but in Root Explorer, if I hit Mount R/W, nothing happens. I don't get an error, but it also doesn't re-mount.
I suspect these errors may be related, because in Xposed I can no longer install by writing directly to /system, I have to use the recovery method. So su is working, but enabling read/write on /system is not.
anyway to decompile this update to see what files are there?
im getting could not be verified as well, trying via sony update center on PC, im rooting with xposed as well
arghhh before i was able to use root-cloak on the sony update app and download updates... seems i cant do that anymore. how did you get to install while rooted? @mariussilverwolf ?
same here... "cant be verified"
so basically no go on the update.
im rooted. i have dual recovery.
c6916
any possibility of a tft file to use for updating?
I have a T-Mobile Sony Xperia Z1s. I updated without really thinking about it. I suppose it was a dumb move. It's an updated Kernel version apparently. My current kernel version is:
Code:
3.4.0-perf-gf96f13d-00907-gaee6e5a
[email protected] #1
Thu Oct 9 09:14:33 2014
So what I guess that means, is that the exploit that enabled us to root Xperia devices previously, has been patched. I had my SuperSU Pro setting for "Survival Mode", ticked "on", and I was able to maintain root. However, I suspect, that if I factory reset my Xperia Z1s that this new firmware would not be rootable, as I bet this is just considered a "security patch". I would have really been pissed if I had lost root because of some crappy OTA update. SuperSU Pro to the rescue.
I rooted my phone using the "simple" rooting method that had come out after "Towelroot", It was called "Easy Root Tool"? anyway, it was a pretty easy process.
Edit: I found the thread again: http://forum.xda-developers.com/showthread.php?t=2784900 But I'm too chicken to try and factory reset and re-root my phone, because I'd hate to not have root.
chriscosta77 said:
I have a T-Mobile Sony Xperia Z1s. I updated without really thinking about it. I suppose it was a dumb move. It's an updated Kernel version apparently. My current kernel version is:
Code:
3.4.0-perf-gf96f13d-00907-gaee6e5a
[email protected] #1
Thu Oct 9 09:14:33 2014
So what I guess that means, is that the exploit that enabled us to root Xperia devices previously, has been patched. I had my SuperSU Pro setting for "Survival Mode", ticked "on", and I was able to maintain root. However, I suspect, that if I factory reset my Xperia Z1s that this new firmware would not be rootable, as I bet this is just considered a "security patch". I would have really been pissed if I had lost root because of some crappy OTA update. SuperSU Pro to the rescue.
I rooted my phone using the "simple" rooting method that had come out after "Towelroot", It was called "Easy Root Tool"? anyway, it was a pretty easy process.
Edit: I found the thread again: http://forum.xda-developers.com/showthread.php?t=2784900 But I'm too chicken to try and factory reset and re-root my phone, because I'd hate to not have root.
Click to expand...
Click to collapse
It is broken, on latest minor ota through pc companion update, not restore, and trying to root with easy root but it isn't working
---------- Post added at 03:40 PM ---------- Previous post was at 03:34 PM ----------
nickcaper said:
same here... "cant be verified"
so basically no go on the update.
im rooted. i have dual recovery.
c6916
any possibility of a tft file to use for updating?
Click to expand...
Click to collapse
I just used my cousin's phone as a tester, it breaks root, haven't tested with supersu pro yet with survival mode
i swear, its like these companies dont want us to use the devices the way we want. A simple thing like root and they make it so hard, even impossible on some models. These companies should know by now that there is a niche which desires freedom like rooting.
if i wanted a frggin phone that didnt have root or a locked os or bootloader id get a dam iphone.
im seriously NOT buying another phone from a store.
ill make sure i get something i can work with the way i want. its already stupid expensive as it is just out the box all locked up and full of bloat wear.
it takes a stupid amount of time and effort just to make these devices do what we want.
which is something that i shoulda got when i paid for it..
looks like i wont be updating sh.... t till i know i can use my device freely.. the way i want.
Unrelated to the root conversation, I'm stock, but my data is acting a bit weird since the update. Did this update change the radios?
Sent from my C6916 using XDA Free mobile app
4.4.4 root
Im new to xda and i just wanted to know is there a root for the sony xperia Z1S that works with android 4.4.4 kit kat? I just recently got the phone and i didnt root it before updating it
Your question.
Johann Broseph said:
Im new to xda and i just wanted to know is there a root for the sony xperia Z1S that works with android 4.4.4 kit kat? I just recently got the phone and i didnt root it before updating it
Click to expand...
Click to collapse
Please just use the search feature, you can easily find the root method. The root method is even on the first page of this topic.
For reference (since my root access remained post update) here's what I have enabled in SuperSU settings:
* Enable SuperUser
* Show Notifications
* Auto-refresh apps and logs tab
* Enable su during boot
* Mount namespace separation
* Trust system user
* Enable permission warning
* Enable Pro
As I mentioned in a previous thread, root was obtained using towelroot on 4.4.4. I haven't run into any issues with root-check invalidating any installs since. The OTA installed without any error messages. I can inject audio into /system/media/notifications and I can create new folders on the root directory that remain after reboot. Maybe I got lucky? I hope by sharing this that other people can duplicate my findings and we can find a way for everybody to maintain a working root solution after this update.
TrunkleBob said:
I just did all that and got SuperSU to re-prompt. Xposed still says it is not active.
I just noticed something else weird; as mentioned before, any other apps that require root are working, but in Root Explorer, if I hit Mount R/W, nothing happens. I don't get an error, but it also doesn't re-mount.
I suspect these errors may be related, because in Xposed I can no longer install by writing directly to /system, I have to use the recovery method. So su is working, but enabling read/write on /system is not.
Click to expand...
Click to collapse
I've been doing some digging and discovered I'm missing a file. Following the original directions for rooting, I created a script and have Script Manager executing it at startup.
The first command is:
Code:
su -c "/system/xbin/kill_ric.sh"
This fails because that file does not exist on my phone. Anyway to get that back?
I had a huge problem with this yesterday and long story short, you cannot use the easy root method if this update is applied. I had to use the flash tool to get the last ftf files and start over from scratch. Avoid this if you can.
I don't really care to update but is there anyway to get the notification of the failed verification off my notification tab? I'm OCD about keeping my notification list clear...
gqukyo said:
I don't really care to update but is there anyway to get the notification of the failed verification off my notification tab? I'm OCD about keeping my notification list clear...
Click to expand...
Click to collapse
only way to get the notification off is to go into settins then look for apps then look for update center. click on it and click on the clear cache. only problem now is. you will need an app like sd maid or something that stops that app from starting automatically when the phone turns on. this is what i do.. it works... you wont get anymore notifications unless you manually make it check.... i use sd maid...
Before I start, my current setup is
Model # Z012DC, Buildnumber: 20.20.1703.38-201704010(Latest update) and rooted successfully using https://forum.xda-developers.com/zenfone-3/how-to/twrp-recovery-3-0-2-root-zenfone-3-t3569926. (I have 3-1-0 TWRP instead of 3-0-2, and used lazy flasher instead of no verify). Bootloader was unlocked via official bootloader unlocker.
Some apps do not work for some reason post root. For example, I use root explorer but when it loads, it just shows blank and after a short while it says it's not responding and I have to close it. The apps I have is genuine and purchased from google play.
Quite a few apps that read/write files in certain scenarios seem to freeze/crash the app after the app is opened.
I have done factory reset to make sure there weren't any other unknown variables.
Coincidentally, if I run root explorer or any other app I have problems with right after a factory reset(pre-root) the app loads up successfully and works just fine(though it shows that certain sections can't be accessed because it needs to be rooted but this is normal.) but it stops working after the root.
I'm trying to figure out if there's something wrong with the actual root process itself, or if there's some issues in regards to the latest firmware or something else entirely.
Any suggestions/inputs are welcome.
I had the same issue with root explorer, but I corrected it by factory resetting and re-installing root from this thread https://forum.xda-developers.com/showthread.php?t=3569926. Maybe it has to do with you using lazy flasher and not following the guide. Worth a shot?
Edit: I jinxed it, latest update caused the same issue again. You're probably right, we need a root v2 method
Install BusyBox and it works again. I installed it from the thread but it didn't work until I installed it from an app on the market
Confirmed. Installing busybox from app store fixed it. For reference the busybox version is 1.26.2.
Thanks!