[Q] Nexus 7 2013 LTE reroot doesn't work, tried everything. - Android Q&A, Help & Troubleshooting

Backstory:
So, I have a 32GB LTE Nexus 7 that I rooted as fast as I got it under 4.3 and flashed custom recovery because I thought I would go CM like I always do.
But I actually didn't need anything else than root and CM tends to have a sucky cellular connection. So I used it and used it and was happy.
But there was a 4.3.x update that I installed that obviously broke root and OTA rootkeeper didn't help. I tried to reroot it (because I'm lazy) with wugfresh's rootkit.
It didn't work, just like it didn't manually over ADB, so I gave up and tried again when the KitKat OTA hit.
Now it worked again and I was happy.
But behold I installed the 4.4.2 update and root is gone again and I can't get it back.
Well, I tried pretty much everything: Flashing SuperSU with Wugfresh root toolkit, tried flashing CWMR over TWRP manually and then manually flash superSUv1.86 via fastboot, flashing stock recovery then wugfresh-flash superuser by koush. Everything to no avail, I still am not rooted.
So what can I do? Now I have superuser installed but no root and when I use SuperSU I don't have root and can't seem to find the app.
I would really need some help please 

Related

[Q] Do I have Root or Not on MJ4????

So I've been really confused about all this MJ4 updating and such lately. My Note 3 was running a stock rooted M15. But I wanted to get these new fixes for the call quality in MJ4.
So here is what I did......
I downloaded MJ4 tar and Kernel from the Samsung updates site. I installed via Odin 3.07. It apparently updated my phone to MJ4 according to the "About Device" screen on my phone. However I was still having bad audio issues. So I ran "Root Checker" back to back 3 times while I was at work this evening and of course it said I didn't have root. So i then tried to installed the MJ4 update again via the "Updates" menu on my phone and it said I couldn't because my phone was modified.
So when I got home, I reran that tar and kernel again, with same result. So then I stared hunting around the forum for answers. I ran across a thread that said there were two ways to restore root: 1.)Install TWRP via Odin, Use a nanadroid back up and restore the rom from the M15 backup but without reinstalling the modem or 2.)install TWRP via Odin, disconnect my phone reboot into TWRP and then Flash the ChainFire SU 1.65 zip.
Well I couldnt do method 1.) because I forgot to do a nandroid before performing the update (I know....Idiot). So I tried option 2.) after rerunning the tar and kernel again. Then I tried to install Freeza's [ROM|StockRooted] 11/6/13 Sprint TouchWiz Jelly Bean 4.3 (N900PVPUBMJ4) Odex/DeOdex which of course failed.
So I then rebooted to recovery again and wiped dalvik and cache. Then rebooted my device in order to be disappointed. So I ran "Root Checker" again and low and behold , it says my device is rooted. So confused,. I ran it again and it say's I'm rooted. So I open Titanium Backup to see if I get a error and I dont. It acts as if I'm rooted.
Now key things to remember in the process:
When I initially updated to M15 I used a rooted stock version of the M15 firmware.
I NEVER wiped anything (dalvik, cache, data or system) before flashing. Also none of my data, apps, internal or external storage were wiped in this process. So all of my apps are installed and running. To answer the first question, Yes...Knox is still saying I have 0x1 void warranty.
So am I really rooted or is my system just fooled into thinking I'm rooted and how do I find out?
ANY IDEAS?
Is superuser installed? If it is just try a new app that requires root, if it asks form permission and you can grant it then you are rooted. Personally I would reflash MJ4 tar from odin. Run cf auto root from Odin and you will be on stock rooted MJ4. If you want to flash a custom ROM then flash twrp from Odin and you can then flash a ROM through twrp. Bonsai ROM is working great, freeza's stock MJ4 ROM had a couple minor issues which are ironed out with Bonsai.
SGS4 Sent
ifly4vamerica said:
Is superuser installed? If it is just try a new app that requires root, if it asks form permission and you can grant it then you are rooted. Personally I would reflash MJ4 tar from odin. Run cf auto root from Odin and you will be on stock rooted MJ4. If you want to flash a custom ROM then flash twrp from Odin and you can then flash a ROM through twrp. Bonsai ROM is working great, freeza's stock MJ4 ROM had a couple minor issues which are ironed out with Bonsai.
SGS4 Sent
Click to expand...
Click to collapse
Thanks for the reply bro. Yeah I was thinking to try the whole thing over again. I heard people were not able to root MJ4 with CF Autoroot right now. I just flashed a couple of mods and they worked. I also gave Superusers permission to two apps and they are working.
shaun0207 said:
Thanks for the reply bro. Yeah I was thinking to try the whole thing over again. I heard people were not able to root MJ4 with CF Autoroot right now. I just flashed a couple of mods and they worked. I also gave Superusers permission to two apps and they are working.
Click to expand...
Click to collapse
You should be good to go then. As long as you are happy with the ROM you have etc I wouldn't mess with it. If you do go back to stock there is always kingoroot, people seems to have good luck with that.
Note 3 or Gear Sent

LOST ROOT

Phone has been fine, rooted with cwm5.5. This is wifey phone so I keep messing with it at a minimum. At some point I noticed it no longer has root. It runs stock 4.1.2. With a couple of root apps - such as AdAway-which is no longer working and has error message "Either subinary could not be found or you did not allow root permissions for AdAway"
Superuser app has this error "There are currently no superuser app policies." then "Superuser binary must be updated" attempting to update results to error "There was an error installing superuser. "
I rooted the phone again with the same CWM ver. file. attempted to flash superuser but it errored and aborted installation. I rebooted and installed rom manager so that I could update CWM. That errored out as well. Root verifier confirms there's no root on the phone. I have installed busy box but it has the same error message no root access.
I thought to root with CWM ver 6.0.4.6 but installation aborted. I tried TWRP but it aborted as well. Only CWM 5.5 works which my normal routed is then to flash superuser, install rom manager and then have it update to CWM to ver 6.xx. But his time none of these is working. How do I regain root?
jayinc11 said:
Phone has been fine, rooted with cwm5.5. This is wifey phone so I keep messing with it at a minimum. At some point I noticed it no longer has root. It runs stock 4.1.2. With a couple of root apps - such as AdAway-which is no longer working and has error message "Either subinary could not be found or you did not allow root permissions for AdAway"
Superuser app has this error "There are currently no superuser app policies." then "Superuser binary must be updated" attempting to update results to error "There was an error installing superuser. "
I rooted the phone again with the same CWM ver. file. attempted to flash superuser but it errored and aborted installation. I rebooted and installed rom manager so that I could update CWM. That errored out as well. Root verifier confirms there's no root on the phone. I have installed busy box but it has the same error message no root access.
I thought to root with CWM ver 6.0.4.6 but installation aborted. I tried TWRP but it aborted as well. Only CWM 5.5 works which my normal routed is then to flash superuser, install rom manager and then have it update to CWM to ver 6.xx. But his time none of these is working. How do I regain root?
Click to expand...
Click to collapse
have you tried flashing another ROM? rumor has it that custom roms contain and are pre rooted.
captemo said:
have you tried flashing another ROM? rumor has it that custom roms contain and are pre rooted.
Click to expand...
Click to collapse
Initially I had actually, but camcorder issues, modems with sporty service ... we a deal breaker. Si I just restored it to stock with kies to avoid more lip. Only thing I did was root the stock so I could install a few apps such as AdAway. I don't plan to do stock on this unless I can get get rooted stock rom.
jayinc11 said:
Initially I had actually, but camcorder issues, modems with sporty service ... we a deal breaker. Si I just restored it to stock with kies to avoid more lip. Only thing I did was root the stock so I could install a few apps such as AdAway. I don't plan to do stock on this unless I can get get rooted stock rom.
Click to expand...
Click to collapse
When I rooted my phone I was wary of using methods that would have me going through either download mode or having to install a custom recovery (which eventually became pointless since I had to do both to flash roms anways lol) but at the beginning I was trying to use something simple.. while googling I stumbled upon this http://www.kingoapp.com/ and rooted from there.. it's like a one-click root kind of thing and seems to keep the root working regardless.. maybe you wanna check it out and see if it helps, in case you loose your root again. If you wanna run your phone stock but rooted, at least after doing the restoration via keys you'll keep the stock samsung recovery.
Hope it helps!
wavv.drama said:
When I rooted my phone I was wary of using methods that would have me going through either download mode or having to install a custom recovery (which eventually became pointless since I had to do both to flash roms anways lol) but at the beginning I was trying to use something simple.. while googling I stumbled upon this http://www.kingoapp.com/ and rooted from there.. it's like a one-click root kind of thing and seems to keep the root working regardless.. maybe you wanna check it out and see if it helps, in case you loose your root again. If you wanna run your phone stock but rooted, at least after doing the restoration via keys you'll keep the stock samsung recovery.
Hope it helps!
Click to expand...
Click to collapse
Thanx for that link/suggestion. I didn't see Note i717 listed under supported devices. Did you if this app supports rooting the i717?
jayinc11 said:
Thanx for that link/suggestion. I didn't see Note i717 listed under supported devices. Did you if this app supports rooting the i717?
Click to expand...
Click to collapse
I know, it doesn't show our device, but I kind of went with the home page "root all devices" statement they had and it worked perfectly fine. I did the same with my sister's Note 2 t0ltetmo which is in fact a canadian Videotron phone I gave her and worked fine too. I do not believe that that Note 2 is in the list either, but it still worked
wavv.drama said:
I know, it doesn't show our device, but I kind of went with the home page "root all devices" statement they had and it worked perfectly fine. I did the same with my sister's Note 2 t0ltetmo which is in fact a canadian Videotron phone I gave her and worked fine too. I do not believe that that Note 2 is in the list either, but it still worked
Click to expand...
Click to collapse
Hey it worked some - I decided to test it on my old Captivate. The only thing is it doesn't install CWM/TWRP or similar. So I cannot install a custom ROM. Is it not supposed to install a custom recovery? If not how do I do that having rooted with Kingoapp?
Thanx again for suggesting this app.
jayinc11 said:
Hey it worked some - I decided to test it on my old Captivate. The only thing is it doesn't install CWM/TWRP or similar. So I cannot install a custom ROM. Is it not supposed to install a custom recovery? If not how do I do that having rooted with Kingoapp?
Thanx again for suggesting this app.
Click to expand...
Click to collapse
My pleasure, and glad to hear it worked! And no, lol, sorry. The app only roots your phone, but it does not install a recovery. The good thing about it is that at least you can run stock and use any rooted apps, like I do with my Asus HD7 (for which, unfortunately I haven't found either a custom recovery or a custom ROM to flash, so I run it stock but mess around with root apps)
However..
I looked into this Galaxy Captive thread: http://forum.xda-developers.com/showthread.php?t=2547997 and didn't find a recovery itself that could be downloadble.
So while googling I stumbled upon this: http://true-android.blogspot.ca/2013/10/how-to-install-custom-recovery-in-most.html.
I my english is good enough to understand, it would seem as if the goomanager app allows u to install recoveries directly from your phone, so you could maybe try if you wish.. If u do, please let us know how it worked, as I'm sure others also would benefit from this.
If you want a CWM recovery for either the Note i717, the Note2 T889 or the S2 T989 let me know and I'll upload them, as those are the only ones I have ATM.
Cheers!

[Q] Tried to Root w/ TWRP, didn't work.

So I Tried to root my newly acquired I717, using this method
"How To: Root AT&T Galaxy Note i717 Jelly Bean 4.1.2 " on You Tube by mooneyb123
I tried on my macbook but I wouldn't recognize the note in Jodin. So I used my Fiances pc.
I had to install keis as the video did not mention that., But it did instal TWRP, which is awesome, But when I tried to instal the CWM-SuperuserSU-v0.94 file nothing happens, it appears to work fine and says successful but when I reboot and check for Root its not rooted.
I've tried this 4 times now.
I don't know what to do next
I want to root to get rid of the ATT bloatware, and possibly overclock. I might try a stable rom like padawan later but I mainly just want to root. Is their any way to do it with TWRP? or am I going to have to go another route?
Also can I odin CWM on or do I need to wipe the device to factory first. The main thing is I don't want to brick it as I am using the phone daily.
I tried what I thought would be the "easiest" looking way to root, but since it didn't work, I need some advice.
How do i get it back to stock recovery If its not rootable? I am running 4.1.2.
I did upgrade soon after I got the device but am wondering If I could have rooted it easier on the original version of android.
Any advice is greatly appreciated.
Thanks.
is their any way I can do it with

need help rooting

hey,
so my mum just bought a desire 601. Before, I had given her my old rooted phone with all my customizations that she has now grown accustomed to, so she wants me to root her new phone and make it look exactly the same.
When she gave it to me to root earlier today, it was brand new. I unlocked the bootloader, and flashed the custom recovery (I went with Philz), but I can't seem to get root. I flashed the latest 2.40 from chainfire's site, but I keep getting the "No binary installed" error. The zip always flashes successfully. Root checker says I have no root.
I just want to keep the ROM stock since its my mom's phone. I showed her insertcoin running on my M7, but she likes sense 5.5, and insertcoin only provides sense 6. So I just want to root the stock ROM and move on.
EDIT: hey, is there an RUU anywhere for this phone? because I can't seem to backup with either philz or twrp, just says cant mount cache and system partitions... wanna be extra careful not to mess anything up
EDIT: Been messing with this all day, no response from anyone here on XDA, went ahead and installed insertcoin. Failed. tried again. success. no idea why. STILL don't have root. Tried superSU and superUser with full wipes. WTF. help?
EDIT: well, thanks for your help XDA, but I managed to finally get it. found some obscure program for windows called Kingo root, and it worked first run. I never looked at windows utilities, always just rooted manually, but whatever, its done now.

[Fire HD 6] Downgrade to 4.5.3 to root, went back to 5.3.1 and lost TWRP

Hi guys,
first of all I want to salut everybody here as I am completely new to the Android world and that's indeed the best resource online. Thanks for that.
Now my big problem. As from the title, I downgrade my Fire HD 6 (4th gen) to 4.5.3 with adb sideload to root it with kingroot and everything went fine. I have then installed TWRP and everything went fine. I have then used TWRP to go back to 5.3.1 and I lost root and recovery. I managed to gain my root privileges back but as for the recovery not a chance. I tried to install TWRP again with dd from adb shell (as I can su) but once again nothing. Checking with fastback getval all, I do have a locked bootload:
Is this the reason why TWRP doesn't run anymore?
If yes, how can I unlock it back?
Is this what's meant with boot loader loop?
Thank you all in advance!
Edit 1:
maybe cuber.py may help but I can't find this file.
Edit 2:
ok found the tools here https://forum.xda-developers.com/kindle-fire-hdx/development/tools-create-unlock-img-fix-boot-img-t3050689
Edit 3:
I tried with cuber.py but the tool can't sign the img because it's not ANDROID. That's what it says. Now I am really stuck. Help please!
LM
I was in the exact same situation, so maybe I can offer some insight. I also have an HD 6 running 5.3.1 that I have downgraded to get root then upgraded a few times. Let me say that I am still learning too, and am by no means an expert but I can try to help.
As far as losing root, i'm not sure as that never happened to me. Did you flash the most up-to date SuperSu with TWRP or did you just answer yes when TWRP prompted you if you wanted root privileges? Flashing a SuperSu through TWRP will give you the SuperSu icon on your home screen once you upgrade back to 5.3.1, whereas just letting TWRP grant root access won't. You will still have root, but without the icon there's no direct control over it (at least not that I could find) so it's still there, just hidden.
My TWRP also replaced by the stock recovery upon updating back to 5.3.1. As far as I know, this is unavoidable. I believe it's as you suspect and is due to the 5.3.1 bootloader being locked. This would also explain why the process for rooting 5.3.1 is so involved as opposed to just using something like Kingroot. I also don't think there's anyone still doing active development on the HD 6 / HD 7.
If you really want to have both root and TWRP, you could try downgrading to an older OS that still has the feel of 5.3.1. I'm not sure about any other versions, but 5.1.1 is rootable via Kingroot (which should mean that it has an unlocked bootloader) and has the same exact UI as 5.3.1. So if you're feeling adventurous try downgrading to 4.5.3, installing TWRP, and upgrading to 5.1.1 instead of 5.3.1 (just be sure to block automatic updates!) and see if TWRP is still active. If so, root with Kingroot and you're good. If you still don't have TWRP, at least you're no worse off than you were.
If you do try this, please post your results here. I might try this myself. I am currently running stock. As I said, I went through the process a few times. For some reason SuperSu was causing erratic behavior in some of my apps and when I tried to switch my SU app to kingroot I lost root completely. I really didn't care about root enough to repeat the whole process again, but if I could keep TWRP it might be worth it. Anyway, good luck.
P.S. You may need to try rooting with Kingroot several times for it to work. I know for a fact that it can root 5.1.1 since I've done it on my own HD 6 when I was running 5.1.1. I'm not sure why it fails, but keep trying and eventually it will get root access. You may have to try 6 or 7 times but eventually it will work.
I went back and re-read this thread more carefully:https://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 and it turns out that TWRP doesn't play well with any 5.X.X bootloaders. Oh well, I was kind of hoping my idea would work. It turns out that you can use TWRP on your current rooted 5.3.1, but only on a temporary basis. Refer to the above thread post #2 for instructions. Basically, you put the correct 5.3.1 bootloader on your device then run AutoTWRP which will flash 4.5.3 bootloaders and TWRP for you. Reboot into recovery and you have your TWRP. You can then do whatever you want. The downside is that since you are running a 4.5.3 bootloader you can't get back into your OS, only TWRP. And once you flash your 5.3.1 bootloader to get back into your OS, TWRP no longer works. I know it's a pain in the arse having to connect to a PC and run a batch file every time you need to use TWRP, but at least it's a sort of workaround.

Categories

Resources