Hey guys. I got my grouper yesterday, I'm hoping for a warm welcome
The first thing I did when I took it out of the box was fire it up, unlocked and rooted. When I rooted, I flashed SuperSU flashable. I also flashed CWM touch. After that I flashed SmoothROM 4.4, and I was solid. I installed all of my usual apps, then went to do what I call debloating, (Looking for apps I don't use such as voicedialer.apk, and deleting them) using root browser (/system/app). I noticed it wouldn't delete, then tried another app that requires root permissions. Nothing. I got suspicious, then re-downloaded root checker. "Sorry! You're device does not have proper root access!" What happened? Is this just me, or is this a widespread problem with this ROM? I'd like to keep this ROM if possible. Is there a way to re-root my device (more or less)? Thanks, a response or any help would be very much appreciated.
Also, sorry if this is in the wrong section, forums are so damn confusing. Mods, feel free to move this to the right spot if it ends up being the wrong spot.
Re: Lost root after flashing SmoothROM 4.4
Solved. It was SuperSU. Remove it, then switch to superuser instead.
Sent from my Nexus 7 using xda premium
Related
Hello everyone,
I've been looking around the forum but I haven't been able to find an answer to this. Right now I have a rooted Samsung Galaxy S4 from Verizon (I rooted it using this method: http://forum.xda-developers.com/showthread.php?t=2290798). The device is currently fully rooted with the original ROM in place (I have not installed ANY custom ROM's ever). I am looking to return the phone to the store tonight but when I unroot through SuperSU and then do a factory wipe (through the settings tab not through any special program) I get the "Custom" message upon booting up again. I have tried rooting/unrooting a number of times with no success. My current position is as follows: I am rooted using the aforementioned method, I have not installed a custom ROM so I assume that I am on the stock ROM, I have installed SuperSU and TriangleAway (TriangleAway says that I have a 0 flash counter). If anyone has any advice I would greatly appreciate it as I might need to return the S4 to the store within the next 2 hours to get my refund. Thanks in advance for any information you can provide and I apologize for the quickness of my request.
Truncated link for the root method
It looks like the forum truncated my link. Here is the full address for the root method I used: http://forum.xda-developers.com/showthread.php?t=2290798 . Thanks again!
What I would do is go to the Android Development forum and download Sextape's one click restore for MDC. It will wipe everything from the internal card and reset you back to MDC. Take the OTA to MDL if you wish.
Here's the link: http://forum.xda-developers.com/showthread.php?t=2258827
Pretty sure it will wipe out any custom indications. I've used the one-click methods for years on the E4GT and here on the S4. Very convenient.
I just went through the same thing. What I did is triangle away, defrost any system apps that maybe frozen disable supersu, reboot, and wallah "official". I repeated these steps twice as the first time it did not take.
P.s. when I ran a frozen system app filter in TB I saw an app called sys scope that was frozen and I don't recall ever freezing that app. Hell, i don't even know what it does but I defrosted it anyway
and all is well
Sent from my SPH-L720 using xda premium
Triangle away doesn't work for MF9 just yet I believe, but it did for MDC. Can always Odin back there, then run triangle away. Ughh, i hate trips to the sprint store
Sent from my SPH-L720 using Tapatalk 2
I apologize in advance if this has been answered or if I have inadvertently offended. I did watch the video and have developed OSes for 30 years. I also have searched all over this site and the web for resolution and am making no progress, so I'm asking the 'oracle'
Got an ATT S4 (I337) a week ago - it was running UCUAMDL. I rooted it using Motochopper and was happily using Titanium Pro etc. I get notified of OTA update. OTA update downloads (357MB) yet fails during install at 30% consistsently.
I figure it is unhappy with my root - I unrooted and cannot remember which way I did it - I seem to recall SuperSU I was using did not have the built-in 'unroot' support so I grabbed the stock image and used ODIN to flash it.I also may have manually uninstalled the 'normal' way the SU app - I suspect this may be my real problem.
After flashing stock ROM for UCUAMDL phone was no longer rooted, did not say custom etc, and took the OTA upgrade just fine. This was for UCUAMF3 which did add App 2 SD support - BTW this update used another 1G of storage compared to UCUAMDL, and I could not recover the 1G by moving apps either, making it virtually worthless as far as adding support for apps in SD, lol.
The problem is now I cannot seem to get the device rooted again. Motochopper fails when installing su.apk. I suspect I have screwed the pooch - what do I need to do to get this thing rooted again?
Is it typical for an OTA update to fail 'because' the device is rooted?
Any advice is much appreciated.
You can't root mf3. You never should have taken the update if you want to be rooted. Cross your fingers that someone finds a way to root the update but I'm not sure you should hold your breath.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
So is doing a stockrom restore back to MDL an option? Then just root that with Motochopper? And disable OTA updates till its figured out?
The real joke here is that to get their built in app-to-sd functionality they give you an update that hogs up another 1GB!
Nope. Can't go back. Just gotta wait it out. Cheers
Just curious if you don't mind - WHY can't you go back? (Ready for the explanation based on perms and su etc, lol) Or flash stock ROM and factory reset etc?
TheKog said:
Just curious if you don't mind - WHY can't you go back? (Ready for the explanation based on perms and su etc, lol) Or flash stock ROM and factory reset etc?
Click to expand...
Click to collapse
A qfuse is blown when you take the update. It won't let you odin or anything else to go back to an earlier firmware.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
For the first time I did an OTA while rooted. I upgraded to 4.3 and now I've lost the following:
SuperSU dowsn't work
Busybox does't work
Can't run bootloader or recovery
My system still shows as a rooted system upon boot. When I connect to my pc and run wugfresh's toolkit, it fails to find adb. I have verified that the driver is installed correctly and debugging mode is on. I can't unlock, root or even return to stock. I do remember seing a thread about a similar issue quite some time ago but I have been unable to find ut. Any help will be greatly appreciated.
Btw, it has just a plain root, no custom roms installed.
Thanks in advance.
stator said:
For the first time I did an OTA while rooted. I upgraded to 4.3 and now I've lost the following:
SuperSU dowsn't work
Busybox does't work
Can't run bootloader or recovery
My system still shows as a rooted system upon boot. When I connect to my pc and run wugfresh's toolkit, it fails to find adb. I have verified that the driver is installed correctly and debugging mode is on. I can't unlock, root or even return to stock. I do remember seing a thread about a similar issue quite some time ago but I have been unable to find ut. Any help will be greatly appreciated.
Btw, it has just a plain root, no custom roms installed.
Thanks in advance.
Click to expand...
Click to collapse
Hi, stator...
Your post isn't quite clear... does the device boot normally? If so, you should have no problems booting into the bootloader.
But first download the latest UPDATE-SuperSU-v1.51.zip to your Nexus 7.
Shutdown the Nexus as normal. Then press and hold the VOL down button... whilst continuing to hold, press the POWER ON button.
This should boot you into the bootloader (in fastboot mode).
From there, and from your PC, Fastboot flash a custom recovery... (Chainfire recommends TWRP)... with the line...
Code:
fastboot flash recovery recovery.img
Where recovery.img is the name of your custom recovery. I usually just rename it to 'recovery.img' (without quotes) anyway - makes for less typing at the command prompt.
Ensure you get the correct recovery for your device....
TWRP for Nexus 7 Wi-Fi ('Grouper') or TWRP for Nexus 7 3G ('Tilapia')
Although a new version of TWRP is now available (2.6), I had some weird issues with this... particularly when copying Nandroid backups off of my Nexus 7 to my PC. Random 'permission denied' messages would crop up running an ADB PULL command... copying via MTP didn't fair much better either. TWRP 2.5 works without problems though, and it's the version I would recommend.
Anyway... back on topic...
Upon completion of flashing TWRP, boot into that recovery (whilst still in the bootloader)... and select INSTALL... navigate to the folder where you downloaded Chainfires SU root updater (usually, the 'download' folder)... and SWIPE to confirm.
Reboot as normal... you should now be rooted. This can be confirmed by any one of the numerous Root Checker apps available in Playstore.
I haven't experimented with busybox... if you mean this version, I haven't installed it, and nor am I going to... at least not for a while.
My Nexus 7 is still in the process of being rebuilt from the ground up, after having fastboot flashed the factory image, necessitating a full wipe (I was running a custom ROM/Kernel combo before)... so I'm taking this slowly, re-installing apps carefully.
It seems that some apps that worked fine under 4.2.2 are broken under 4.3. MX Player and Adobe Flash Player to name a couple.... but QuickPic and Titanium have now been fixed and work fine under 4.3. I'm under no illusions that Adobe Flash Player will be fixed anytime soon... it's been technically deprecated by Adobe for a while anyway.
Anyway... good luck... and hope you get root sorted.
Rgrds,
Ged.
I am having problems with Busybox as well even though i did not take the OTA. I flashed CleanRom, and Faux kernel.
Just fyi
Sent from my Nexus 7 using xda premium
First and foremost I would like to apologize for taking so long to reply. Real life had me out of town and I didn't have my tablet with me. I tried the advice given but it didn't work at first. It took multiple attempts but I finally got my tablet back to stock. I guess my Nexus 7 didn't agree with the 4.3
OTA while rooted. I can now unlock, root, and even change roms once again. I don't know for sure what was causing the problem but it's all good now. Also, I was always able to use my tablet during my little crisis. I was just unable to unroot or even flash a new rom. Thanks again for all the help.
You could have hit thanks, a guy wrote you a gigantic step-by-step instructions just to help you out
Sent from my LG-P920 using xda app-developers app
shevich said:
You could have hit thanks, a guy wrote you a gigantic step-by-step instructions just to help you out
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
I sincerely hope this is a joke. I most definitely said thanks. I even apologized for taking so long to reply. Please try to be constructive or don't bother to post. I've been frequenting this site for quite sometime although I've never posted or even joined until recently. This community has been extremely helpful. The last thing that is needed is another troll. Thank you.
He was talking about using the thanks button.
Sent from my Galaxy Nexus
I rooted successfully some time back using motochopper and regularily use tibu, root explorer etc, so know I have root, but each time I turn the screen on get this message: "Error! No root access or incompatible devise". It goes awat after a few moments but is in the way and very annoying.
I have searched xda as best I can and googled, but am not finding anything on this message. Has anyone else got this message too? Can it be fixed?
Thanks,
Dan
Sent from my SAMSUNG-SGH-I497
what device, what rom, what anything, hard to help, when you do not provide the info...
Sorry, I don't have a fix for you.
I went through a root hell similar to that. This was a few months ago. I googled all over and tried everything and never could fix it.
Ended up having to Odin back to stock.
Re-root & install recovery.
Then flash another rooted ROM.
You might try installing SuperSU though. See if that taking over for Superuser will resolve your issue. I doubt it though. I tried it on mine and still had weird issues.
Root worked great in some apps and not at all in others.
Like I said. I ODIN'd back to stock.
OK, here are the details.
SGS4 32 gig ATT i337 UCUAMDL stock out of the box rooted with this "error - no root found incompatable devise," which persists after flashing ShoStock 2.2 I337UCUAMF3 with baseband I337 UCUAMDL and 3.4.0 Jebo Kernel v1.5. Though I actually do have root and use many apps like tibu, triangle away, root explorer, etc. They all work fine. Just this pause and error message most times I activate the screen. After a bit the error message goes away, but its1 tough to do anything while it's still up.
I don't recall having this error message before restoring/unrooting my first SGS4 to stock and exchanging it for 32 gig version. It too had AMDL.
Certainly don't hold myself out to be an expert, but have been rooting / flashing for 3 years with Captivate, SGS2 and now SGS4. Been going nuts tring to find something on the issue by searching, so was glad to see CZ Eddie had a similar problem and fruitless search...and that was resolved by flash back to stock and rerooting.
Yes, BTW, I do have SuperSU installed.
Curious if there are any explanations or other solutions.
Thanks,
Dan
Sent from my SAMSUNG-SGH-I497
I did a full wipe of data, cache and dalvik, restored with Titanium Backup and problem seems to be gone. So far so good.
Sent from my SAMSUNG-SGH-I497 using Tapatalk 4
I noticed on two occasions, that this error returned coincidentally when I reinstalled or unfroze an app called Touchscreen Tune. After uninstalling or freezing that app, problrm does not recur. Has not recurred for several months now. And I remain on same stock rooted rom as previously. Not sure if there was an incompatability with touchscreen tune or if this was all coincidental. Think ill reinstall touchscreen tune and see what happens.
Sent from my SAMSUNG-SGH-I497 using XDA Premium 4 mobile app
Snap Link said:
I noticed on two occasions, that this error returned coincidentally when I reinstalled or unfroze an app called Touchscreen Tune. After uninstalling or freezing that app, problrm does not recur. Has not recurred for several months now. And I have been remained rooted on several versions of ShoStock International rom. Not sure if there was an incompatability with touchscreen tune or if this was all coincidental. Think ill reinstall touchscreen tune and see what happens.
Sent from my SAMSUNG-SGH-I497 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I497 using XDA Premium 4 mobile app
Yep, Touchsceen Tune appears to be the culprit. Had same problem with Tab2 earlier too. Which after reading description in the market, it was tested on SGS2, but no mention of SGS4 . And explixitly states not compatable with Tab2. That's unfortunate as was a great enhancement to my SGS2 and Tab7500. But, maybe there are other similar apps to choose from. Anyhow, seem to have identified the problem.
Sent from my SAMSUNG-SGH-I497 using XDA Premium 4 mobile app
Hello,
I own a S4 I337M I had it rooted and then proceed to install CM 10.1.3 I had no problems then. Yesterday I got a notification that CM 10.2 was available after I installed it using OTA I lost the ability to turn on the wifi and the 3g.
I had CDW so I wiped my phone and reinstalled 10.2, when I opened titanium it suggested me to try superSU I installed it but when I opened it I got an error saying something about the binary files.
I chose to flash the binary files and now I cannot access to CDW and it seems like I lost root, everything else seems to work good but I would like to have my phone rooted if this cannot be achieved on CM 10.2 I would like to install CDW and go back to 10.1.3.
I tried to root my phone again using ODIN like the first time but it didn't work.
Do you know if there's a way to regain root access or at least to install CDW again?
Thanks in advance.
Never mind.
I was able to put back CDW with Odin and restore the backup of CM 10.1.3.
Sent from my SGH-I337M using xda app-developers app
mahzarasua said:
Hello,
I own a S4 I337M I had it rooted and then proceed to install CM 10.1.3 I had no problems then. Yesterday I got a notification that CM 10.2 was available after I installed it using OTA I lost the ability to turn on the wifi and the 3g.
I had CDW so I wiped my phone and reinstalled 10.2, when I opened titanium it suggested me to try superSU I installed it but when I opened it I got an error saying something about the binary files.
I chose to flash the binary files and now I cannot access to CDW and it seems like I lost root, everything else seems to work good but I would like to have my phone rooted if this cannot be achieved on CM 10.2 I would like to install CDW and go back to 10.1.3.
I tried to root my phone again using ODIN like the first time but it didn't work.
Do you know if there's a way to regain root access or at least to install CDW again?
Thanks in advance.
Click to expand...
Click to collapse
Check my thread http://forum.xda-developers.com/showthread.php?t=2682115 .Download superuser zip from the first post and flash it .
Cheers , you got root access again .
Click :thumbup: button if I helped .
Sent from my GT-S7562 using XDA Premium 4 mobile app