Related
i have an infuse 4g that is rooted
downloaded modded e3 and installed but when i go through and change the old recovery and paste the new it dont show the old and the new files
then when i run cwm it down loads i go into reboot into recovery
it says failed to verify whole-file signature
signature verification failed
installation aborted
is this due to the two files not being there
or am i doing somthing wrong
http://www.youtube.com/watch?v=PkMo8rBehHg
follow those instructions exactly, making sure to adjust the permissions of the recovery file at the end.
download ROM manager, go to "flash clockworkmod recovery" and choose plain galaxys i9000.
then boot into recovery (probably blue), select reinstall packages 2 times, and you should be in green cwm recovery (if you boot into green the first time, ignore the reinstall packages step).
i did all that about 10 times still dont work i think i am missing somthing
---------- Post added at 10:23 PM ---------- Previous post was at 10:10 PM ----------
tryed all that to the letter still dont show the to recovery files and still gets the failure to install i dont know what to do now
ive tryed every thing i could find and none of it dont work
---------- Post added at 10:33 PM ---------- Previous post was at 10:23 PM ----------
i gave a thanks anyway but i still cant get it to work
that is just the luck i have i prob got the only phone in the world that cant get a new rom on it
I GIVE UP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Are you remembering to switch to R/W mode before tring to write the 3e recovery?
Try updating busybox.... Confirm you have system as r/w when replacing recovery....
Sent from my Samsung Infuse 4G - 1.6ghz
tryed that
i tryed everthing you guys said but still will not load packages and fails
could it be my phone that is causing this
Go here and download the "3e Recovery w/o signature verification"
http://forum.xda-developers.com/showthread.php?t=1091465
Replace your recovery with this one. Reboot into recovery. You'll still need to reinstall packages once or twice., but only only the first boot into recovery.
Did you extract the new recovery before pasting? I'm sure you did but figured id ask.
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
I realize this may be a little late, but make sure you have the newest version of root explorer installed if that's what you're using. I downloaded an old version for free from a friend of mine, and it wouldn't work correctly when it came to the copy/pasting of the recovery file part of the instructions. Downloaded the newest one from market and it all worked perfectly.
Ok, I am on FP5, I guess I lost CWM, can I just flash Imnuts CWM With odin?, and how can I root it?
jorge3687 said:
Ok, I am on FP5, I guess I lost CWM, can I just flash Imnuts CWM With odin?, and how can I root it?
Click to expand...
Click to collapse
*sigh* look around...
Sent from my SCH-I510 using xda premium
jorge3687 said:
Ok, I am on FP5, I guess I lost CWM, can I just flash Imnuts CWM With odin?, and how can I root it?
Click to expand...
Click to collapse
Here you gotaken from my thread)
5. How to root a pure stock FP1 and make CWM stick after reboot - Turn off your phone, use ODIN to flash CWM (0302 blue latest version - http://imnuts.net/zU2jkn) with "reboot" option unchecked,
After completed, disconnect the usb cable, pull the battery, reinstall battery, hold down volume up+home+power to boot into cwm,
(if you failed to boot into cwm and your phone boot up you have to redo the process). Now flash Super user package zip (Superuser-3.0.7-efgh-signed.zip - and su-bin-3.0.3.2-efghi-signed.zip (both can be download from here (look for Gingerbread) : http://androidsu.com/superuser/
Reboot phone. Use Root explore (or Root browser lite or ES file explorer) go to /system/ect/install-recovery.sh script, tab on mount R/W button (upper top). Long press on the script and in the popup menu, select permission, unchecked all permission then save the file.
Shutdown phone, re-Odin cwm again, once done reboot, now cwm should stick. Once phone came up, to verify root on your phone, you can download "root checker basic" from the Market. If you have issue, download "superuser update fixer" app from the market and run it.(no reboot required). That's it.
Wow great help with links and everything thanks a lot
Sent from my SCH-I510 using xda premium
Just to add to this very helpfull Post, this are the problems I run into and how I fixed them so that if anyone comes up with the same issues, you have the solution:
1. Flashing CWM with odin was failing, I changed usb port, I rebooted the computer, and the problem was that I was doing it without the battery, as soon as I put the battery in the phone and tried odin, it was succesfull, so, what I think is that there is not enough power to the phone just using the usb cable and that is why it was failing to flash.
2. after I flashed superuser and su-bin files, rebooted the phone, but as soon as my phone was on, and connected to the internet, for some reason, the phone automatically downloaded and updated this two files, so I could not change the recovery sh script, my solution, disabled data, reflash cwm, and the root files, then I was able to change the permissions of the file.
I AM NOW ROOTED!!!! thanks buhohitr
ok, now I lost root, for some reason, I installed titanium backup and the app told me the phone is not rooted, I used the superuser update fixer and it says that it cannot fix the root, that I need to download and uptaded update.zip, what can I do?
jorge3687 said:
ok, now I lost root, for some reason, I installed titanium backup and the app told me the phone is not rooted, I used the superuser update fixer and it says that it cannot fix the root, that I need to download and uptaded update.zip, what can I do?
Click to expand...
Click to collapse
Again, please look around...
Sent from my SCH-I510 using xda premium
jorge3687 said:
ok, now I lost root, for some reason, I installed titanium backup and the app told me the phone is not rooted, I used the superuser update fixer and it says that it cannot fix the root, that I need to download and uptaded update.zip, what can I do?
Click to expand...
Click to collapse
Did you mount /system before you flash the superuser zip? if not boot into cwm, mount, then flash superuser zip file.
Edit: Also verify that you do have root by other methods, I heard the current of Titanium backup having issue.
buhohitr said:
Did you mount /system before you flash the superuser zip? if not boot into cwm, mount, then flash superuser zip file.
Edit: Also verify that you do have root by other methods, I heard the current of Titanium backup having issue.
Click to expand...
Click to collapse
There were some problems with the instructions: the steps you gave me were to install legacy super user files, which gave me temporary root only, and yes I mounted system in CWM, also the original thread has some confusing directions, such as downloading the whole package for ARM, and then stating to get the legacy 3.0.7-efghi signed, which is a contradiction, it is one or the other.
this is what I did and all works perfect:
1. download this two files and put them on your sd card http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
http://downloads.androidsu.com/superuser/su-bin-3.0.3.2-efghi-signed.zip
3. MOUNT /SYSTEM in CWM and flash the two files
4. Reboot and verify root with root checker basic, this is all you have to do!!!
jorge3687 said:
There were some problems with the instructions: the steps you gave me were to install legacy super user files, which gave me temporary root only, and yes I mounted system in CWM, also the original thread has some confusing directions, such as downloading the whole package for ARM, and then stating to get the legacy 3.0.7-efghi signed, which is a contradiction, it is one or the other.
this is what I did and all works perfect:
1. download this two files and put them on your sd card http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
http://downloads.androidsu.com/superuser/su-bin-3.0.3.2-efghi-signed.zip
3. MOUNT /SYSTEM in CWM and flash the two files
4. Reboot and verify root with root checker basic, this is all you have to do!!!
Click to expand...
Click to collapse
Nice! glad you got it working.
I have the same question. I don't really know how to root. I've always just flashed an already rooted rom via Odin. I don't truly know how to root on my own.
---------- Post added at 02:22 AM ---------- Previous post was at 02:02 AM ----------
yourbrokenoven said:
I have the same question. I don't really know how to root. I've always just flashed an already rooted rom via Odin. I don't truly know how to root on my own.
Click to expand...
Click to collapse
I see all the replies with answers now. Don't know why they weren't there before.
yourbrokenoven said:
I have the same question. I don't really know how to root. I've always just flashed an already rooted rom via Odin. I don't truly know how to root on my own.
---------- Post added at 02:22 AM ---------- Previous post was at 02:02 AM ----------
I see all the replies with answers now. Don't know why they weren't there before.
Click to expand...
Click to collapse
well, since I could not get help from the experts, I just did it myself and wrote the process for other people to make it easier.
Okay, this method only gives me root temporarily. Once I reboot again, I no longer have root. Going back into recovery... Clockwork mod is gone! Back to stock recovery!
Any ideas? Can't find anything helpful on the forums via search.
Sigh... http://forum.xda-developers.com/showthread.php?t=1832040
Sent from my SCH-I510 using xda premium
read back the first posts, there is the solution
[QUOTE=yourbrokenoven;31313626]Okay, this method only gives me root temporarily. Once I reboot again, I no longer have root. Going back into recovery... Clockwork mod is gone! Back to stock recovery!
Any ideas? Can't find anything helpful on the forums via search.[/QUOTE]
jorge3687 said:
read back the first posts, there is the solution
[QUOTE=yourbrokenoven;31313626]Okay, this method only gives me root temporarily. Once I reboot again, I no longer have root. Going back into recovery... Clockwork mod is gone! Back to stock recovery!
Any ideas? Can't find anything helpful on the forums via search.
Click to expand...
Click to collapse
[/QUOTE]
I had already tried the above without success. CWM was overwritten each time. There was another file to delete as well somewhere in system/ect which was also supposed to prevent recovery overwriting,mbut that solution proved just as fruitless.
I got itt working through trial and error, though. As it turns out, recovery actually UNmounts system after you flash a single file, so you must REmount after each if you are flashing multiple files. I do not see this "feature" explained anywhere. Maybe this is something fundamental about Linux which has escaped me over the years of android phone ownership.
Thank you for trying to help me even though.
It unmounts for safety reasons, and it's done by the package itself, not the recovery by default. You don't want power to be pulled from a filesystem in unix when it's mounted. The real issue isn't the unmount, but the mount itself seems wonky on this phone, so depending on how the CWM package is written, there's a good chance it won't be successful when it tries to mount the filesystems. It's better to mount them yourself if you're working with a package that wasn't specifically written with this phone in mind, and you even need to mount on some that are.
This thread will help you to update and root android version 1.4.2 on your galaxy tab 2 (P5110 only).
This solution requires access to a PC running Windows.
This procedure was tested on stock 4.1.2 ROM and may not work on other versions.
WARNING:
I am not responsible for bricking your device, using this thread is at your own risk!
Requirements:
- Odin (download)
- Latest galaxy tab 2 android firmware (download)
- Clockworkmod (download)
- SuperSU v1.10 (download)
- Samsung usb drivers (download)
Process
Step 1:
Copy SuperSU v1.10 to the root of your SDcard.
Install the Samsung USB drivers.
Step 2:
Make sure Samsung KIES is not running on your computer!
Step 3:
Make sure your tablet is not connected to your computer or another power supply.
Shut down your tablet and turn it on holding both power and volume up (right) button pushed.
After some seconds you'll see a yellow triangle, push volume down now.
Step 4:
Connect your tablet to the computer and start Odin.
When Odin is succesfully connected you should see a orange box lighting up. (in Odin)
Step 5:
Extract P5110XXCMA2_P5110OXXCMA4_SMO.zip to a place you can find it.
In odin, click on PDA and select the tar.md5 file you just extracted.
Step 6:
Click on start and let Odin flash your tablet.
Step 7:
When flashing is complete your tablet should restart, turn it off again and repeat step 3.
When you're in download mode again click on PDA in odin and select GT-P5110_ClockworkMod-Recovery_6.0.1.0.tar.
Step 8:
Click on start and let odin flash clockworkmod on your tablet.
Step 9:
When flashing is complete your tablet will restart once again, turn it off again.
Start your tablet by pushing volume down and power at the same time (not volume up)
Step 10:
Once you are in recovery, use volume button (UP/DOWN/LEFT OR RIGHT) to move around and POWER button to select an option.
Select install zip from sdcard. Choose SuperSU v1.10 file you already copied to root of sdcard.
Step 11:
Once you're done flashing you can go back to the main page of clockwork recovery and clear cache.
When that is finished you can reboot your system
That's it!
Your device has been updated to version 4.1.2 of android and rooted with superuser.
WARNING: Do not install ROM Manager until developer says app will support Tab2 10.1 < Posting this because someone bricked their Tab2.
In addition, ROM Toolbox may not work properly (1 crash reported).
Click to expand...
Click to collapse
I recommend doing a full backup of android in clockworkmod recovery (use step 9 to get into clockworkmod recovery)
This is one of the first tutorials I've ever made, and I made it in a limited amount of time.
Iff you have any feedback please leave a reply, also leave a reply iff your flash was succesfull
Have Fun!
~ Archcry
does the system status change's when the custom recovery is changed ? to cwm?
if does change, how can i remove it?
try to flash Superuser 3.1.3 gives message
E:failed to verify whole-file signature
E:signature verification failed
What features has 4.1.2?
Sent from my GT-I9100 using xda premium
Hi guys, I have a problem with Recovery in My Samsung Galaxy Tab 2 10.1 GT-P5110.
I have installed ClockworkMod Recovery Version 5.5.0.4 from this thread http://forum.xda-developers.com/showthread.php?t=1657056
When I go to that recovery I dont have "install from SD card" etc.
I have:
- reboot system now
- apply update from external storage
- wipe data/factory reset
- wipe cache partition
- apply update from cache
Click to expand...
Click to collapse
I have been trying install root using "apply update from external storage" but it is not working.
I've tried instal new recovery 6.0.1.0 (through Odin) from this thread but nothing is change. All the time I have old ver. 5.5.0.4 of recovery.
Can you tell my guys how to change recovery for new one ?
P.S. Sorry for my English
pawel30w said:
Hi guys, I have a problem with Recovery in My Samsung Galaxy Tab 2 10.1 GT-P5110.
I have installed ClockworkMod Recovery Version 5.5.0.4 from this thread http://forum.xda-developers.com/showthread.php?t=1657056
When I go to that recovery I dont have "install from SD card" etc.
I have:
I have been trying install root using "apply update from external storage" but it is not working.
I've tried instal new recovery 6.0.1.0 (through Odin) from this thread but nothing is change. All the time I have old ver. 5.5.0.4 of recovery.
Can you tell my guys how to change recovery for new one ?
P.S. Sorry for my English
Click to expand...
Click to collapse
You can install the update above, it will reset your recovery to default.
That way you'll be able to flash the new recovery
Thread changes: I deleted superuser and added supersu, this way root will work.
Hi,
Thanks for the tutorial.
We bought 2 Tab 2 10.1's yesterday (It's our wedding anniversary on Monday these where the gifts we bought each other) and after spenging last night flashing PA, CM and PACMAN I settled on a stock rom.
All the others just don't have the right feel..... Where is the Sotmax rom when you need it... :laugh:
Any way so my tablet had root and a custom rom installed already (and a back up) and was stock after flashing.
For the mrs I just followed this and all went according to plan.
Only thing I can say is the link you have to teamhacksung.org is broken.
I did also flash philz touch straight after this.
archcry said:
You can install the update above, it will reset your recovery to default.
That way you'll be able to flash the new recovery
Thread changes: I deleted superuser and added supersu, this way root will work.
Click to expand...
Click to collapse
Hi Archcry...
Firstable thanks for your post-.....
I've followed all the steps of your post until the step that we are suppose to install the supersu....i tried everything but it's impossible to install it!! Trought google play...it's giving me a binary error....on the recoverymod...when i goo to install zip/external sdcard and i select the spsu, all the otpions are "NO" and its says that it's not possible....
Can u help me plz?
regards
There should be an option called "yes".
did you try scrolling down a bit?
I used the exact same method on my P5110 and it worked like a charm.
~ Archcry
Thread added to the Index Thread.
How do i get this odin file for rooting the tab 2?
Latest galaxy tab 2 android firmware (download) is a super slow link. Anyone got a faster one?
For those who need the download links here they are, they all work!
Clockworkmod
UPDATE-SuperSU-v1.34.zip instead of v1.10
Samsung_USB_Driver
Odin
Latest galaxy tab 2 android firmware
tommeke19 said:
For those who need the download links here they are, they all work!
Clockworkmod
UPDATE-SuperSU-v1.34.zip instead of v1.10
Samsung_USB_Driver
Odin
Latest galaxy tab 2 android firmware
Click to expand...
Click to collapse
samsung usb driver is bad link
anyone got a working one?
I think that, if Kies is installed on your pc, you dont need to install samsung usb drivers again...
I've updated my Tab 2 to 4.2.2 but am largely unimpressed so wanted to use this method to root and then install a custom ROM.
If I use the Android firmware from the link above, will I be back on the older version of Android (which doesn't bother me), or do I need to follow all them steps above but use the 4.2.2 rom from somewhere?
Anyone?
Wow, no love. Was wondering the same thing. ^
Can I use this method with stock JB 4.2.2?
Pagecoma said:
Can I use this method with stock JB 4.2.2?
Click to expand...
Click to collapse
No. There's a different root method for 4.2.2. Android-Andi posted a root method for that firmware in the development section. It's in here somewhere...
Sent from my VS980 4G using XDA Premium 4 mobile app
---------- Post added at 07:49 AM ---------- Previous post was at 07:43 AM ----------
Here's the method I used...
http://forum.xda-developers.com/showthread.php?t=2535083
Read through everything and it should work like a charm!
Sent from my VS980 4G using XDA Premium 4 mobile app
When I open up superSU, it says:
There is no SU binary installed, and super SU cannot install it.
If you just upgraded to android 4.3, you need to manually re-root.
If I turn the Nexus on in recovery mode, it still says it's unlocked.
So at this point, is there anything I can do to restore root status without factory resetting? I made a backup with titanium backup but it was a while ago so I would rather not use it if there is another way.
I've read somewhere that rooting it should mean OTA updates should no longer work but somehow, it still went through and I updated it without thinking too much.
Download the supersu zip file and flash it in recovery.
http://download.chainfire.eu/371/SuperSU/UPDATE-SuperSU-v1.85.zip
This will throw me back into rooted mode while keeping my phone as is?
BruceHsiang said:
This will throw me back into rooted mode while keeping my phone as is?
Click to expand...
Click to collapse
this will update the binaries and restore root. no data will be lost or formatted. simply flash the zip in twrp or cwm.
xBeerdroiDx said:
this will update the binaries and restore root. no data will be lost or formatted. simply flash the zip in twrp or cwm.
Click to expand...
Click to collapse
I don't have twrp or cwm installed yet. Which one is generally simpler/easier to install/use?
So I installed goomanager and tried to install twrp, but it all goes back to the same problem which was that I am now not in root mode anymore.
Also what do you mean by flashing the zip? Which options am I supposed to use?
BruceHsiang said:
I don't have twrp or cwm installed yet. Which one is generally simpler/easier to install/use?
Click to expand...
Click to collapse
I've been using TWRP with no problem and it's been awhile since I've used CWM. I've never used a toolkit or flashify but with adb it would probably take a couple minutes max to flash either one.
---------- Post added at 10:49 PM ---------- Previous post was at 10:46 PM ----------
BruceHsiang said:
So I installed goomanager and tried to install twrp, but it all goes back to the same problem which was that I am now not in root mode anymore.
Also what do you mean by flashing the zip? Which options am I supposed to use?
Click to expand...
Click to collapse
Choose "Install" in recovery, with either TWRP or CWM is flashing the zip.
wantabe said:
I've been using TWRP with no problem and it's been awhile since I've used CWM. I've never used a toolkit or flashify but with adb it would probably take a couple minutes max to flash either one.
---------- Post added at 10:49 PM ---------- Previous post was at 10:46 PM ----------
Choose "Install" in recovery, with either TWRP or CWM is flashing the zip.
Click to expand...
Click to collapse
Problem is, I didn't install twrp when I had root access before, and now when I try to use it, it says I need root to use it.
Can I flash the zip using adb in the fastboot recovery menu?
What should I do from here?
BruceHsiang said:
Problem is, I didn't install twrp when I had root access before, and now when I try to use it, it says I need root to use it.
Can I flash the zip using adb in the fastboot recovery menu?
What should I do from here?
Click to expand...
Click to collapse
Sorry I've never done that. I guess you could adb push superuser.apk to the system but you still need the binary wherever that goes. Honestly I would just flash TWRP using adb and use TWRP to flash the SuperSu zip.
---------- Post added at 11:11 PM ---------- Previous post was at 11:10 PM ----------
Do you have adb already working?
Not yet, I just saw it as an option while reading around.
How would I install twrp with that image file?
All tutorials I've found said I needed root to install it in the first place.
BruceHsiang said:
Not yet, I just saw it as an option while reading around.
How would I install twrp with that image file?
All tutorials I've found said I needed root to install it in the first place.
Click to expand...
Click to collapse
No.You do not need root to install a custom recovery. You need an unlocked bootloader. How did you get root in the first place? You must have used a toolkit of some kind? Use it again? I've only every used adb so I can't help with any toolkits but lots of people use them, I guess!
Download the latest TWRP or CWM recovery. Put it in the same folder as your adb and fastboot files. Open a command prompt and type adb reboot bootloader(you have to make sure developer settings are enabled and USB debugging is checked). Then flash recovery using fastboot by typing fastboot flash recovery name_of_file.img and then you can flash the supersu zip file.
Sent from my Nexus 5 using Tapatalk
Exactly! I'm thinking he doesn't have adb setup yet.
---------- Post added at 11:36 PM ---------- Previous post was at 11:28 PM ----------
This is a pretty decent video on how to setup adb, not the newest video out there probably but it should work!
I used chainfires autocf root file from here
http://forum.xda-developers.com/showthread.php?t=2507211
and followed a youtube tutorial.
When I try adb devices it shows my serial number followed by sideload.
I've tried sideloading both twrp and the superSU.zip, and they fail to verify and the installation aborts =\
I've had the OPO for over a year, and just now had the need to root it. An OTA happened to come in the next day, and the update process didn't work as I expected. So I'd like to know if I did something wrong, a random problem occurred, or this is the way it's supposed to work.
Until a couple days ago, the OPO was stock + all OTAs that had been released. I unlocked the bootloader, installed TWRP recovery, and installed SuperSU. All that went as expected. When the OTA notification arrived the next day, I tried to install it with "Update Cyanogen recovery" still unchecked (because original reports with CM 11S said you could keep your custom recovery with an OTA).
When I tried to install the update, the phone just rebooted to TWRP and the update was not stored anywhere on /sdcard. I then checked "Update Cyanogen recovery" and tried to install the OTA again. It did not install, and TWRP was still my recovery. Several repeats of this had no different result.
Then I flashed the stock CM recovery with fastboot. After verifying I had the CM recovery, I installed the OTA again, and it failed again, reboting to recovery and doing nothing else. Then I downloaded the incremental update and tried to flash that via CM recovery, and that failed too. I checked the file /System/build.opt, and line "ro.build.version.incremental" said 49d90510ef, which meant I should have been able to install the cm-bacon-49d90510ef-to-d91bf047f5-signed.zip file. But it failed and said the current build number was not as expected. The number it gave me was not anything that made sense looking at the list of recent incremental updates.
So at that point I bailed out and installed via recovery the full flashable zip file, and that worked.
If this is what I have to do each time, it's certainly doable, but I don't think this is how it's supposed to go. I'm surprised the OTA didn't work with the custom recovery installed, and I'm even more surprised that the incremental installation failed. Maybe trying to install the OTA without updating the CM recovery messed things up, but that doesn't seem likely either. When the next OTA comes out, I'll see if any of these troubles are repeated. But I'd like to know how the OTA was supposed to work after installing a custom recovery.
I am still yet to figure this one out also, my friend I'm sure with time someone will respond who had better experience with this; just be patient
Have you been able to root yet? I can't seem to be able to on the new incremental yet.
@MidnightJava
Looks like I'm not the only one with this problem.
I'm trying to find now the link for Cyanogen Recovery flashable to see it that fix the OTAs
Check the CyanogenMod website, @distante
vince.lupe said:
Have you been able to root yet? I can't seem to be able to on the new incremental yet.
@MidnightJava
Click to expand...
Click to collapse
After installing the latest CM 12.1 ROM, I had to re-flash SuperSU. After doing that, root access is working fine. If you're having trouble rooting after installing the incremental, then my experience is perhaps not applIcable—since I was not able to do an incremental installation and had to re-flash the entire ROM.
distante said:
Looks like I'm not the only one with this problem.
I'm trying to find now the link for Cyanogen Recovery flashable to see it that fix the OTAs
Click to expand...
Click to collapse
This thread with Cyanogen mirrors and info has exactly what you need.
MidnightJava said:
After installing the latest CM 12.1 ROM, I had to re-flash SuperSU. After doing that, root access is working fine. If you're having trouble rooting after installing the incremental, then my experience is perhaps not applIcable—since I was not able to do an incremental installation and had to re-flash the entire ROM.
Click to expand...
Click to collapse
I had to completely re-flash stock 3JL full also, but this time root doesn't work. Tried to use WugFresh's Bacon Root Toolkit - didn't work - then, I tried to flash SuperSu via TWRP recovery (after unlocking bootloader), and that didn't work either? In other words, I have bootloader unlock, custom recovery installed, but no root :/
vince.lupe said:
I had to completely re-flash stock 3JL full also, but this time root doesn't work. Tried to use WugFresh's Bacon Root Toolkit - didn't work - then, I tried to flash SuperSu via TWRP recovery (after unlocking bootloader), and that didn't work either? In other words, I have bootloader unlock, custom recovery installed, but no root :/
Click to expand...
Click to collapse
What happens when you try to root? Does it seem successful, but then you don't actually have root access? Or do you get some failure indication when you flash SuperSU? I've rooted a few phones in the last few years, but I'm far from an expert. Hopefully someone else will jump in with some idea of what went wrong. Shooting somewhat in the dark, I'd say look at the version of SuperSU and make sure it's the latest and the right one for the ROM, look at read-write permissions on your storage (if you can, you may need root access to check it properly). Of course wiping cache is always a good step, and if nothing else works, maybe factory reset, re-lock the bootloader, and then unlock and flash custom recovery again, and see if root can be successful then.
Once on custom recovery ( TWRP ) OTAs will NOT not install, unless you revert back to CM stock recovery. If you don't want to do that, wait for a signed flashable version to come out, which is normally 1-2 days after. Everytime you flash an update you will have to reinstall TWRP and SuperSU.
---------- Post added at 03:31 PM ---------- Previous post was at 03:25 PM ----------
vince.lupe said:
I had to completely re-flash stock 3JL full also, but this time root doesn't work. Tried to use WugFresh's Bacon Root Toolkit - didn't work - then, I tried to flash SuperSu via TWRP recovery (after unlocking bootloader), and that didn't work either? In other words, I have bootloader unlock, custom recovery installed, but no root :/
Click to expand...
Click to collapse
Did you guys remove the " Update Cyanogen recovery" in Dev options and "respect CM root settings " In SuperSU settings ?
Cholerabob said:
Once on custom recovery ( TWRP ) OTAs will NOT not install, unless you revert back to CM stock recovery. If you don't want to do that, wait for a signed flashable version to come out, which is normally 1-2 days after. Everytime you flash an update you will have to reinstall TWRP and SuperSU.
Click to expand...
Click to collapse
I figured that was the case when it failed. What seems anomalous in my case is that even after reverting to the stock recovery and verifying that it was installed, OTAs would not succeed. I didn't know about the "respect CM root settings " In SuperSU settings that you mentioned. Maybe that was the problem? Either that or the fact that I tried to install the OTA first with the custom recovery. Certainly the fact that the incremental installation reported I was at a different build number than what was listed in /System/build.opts indicates something was out of whack on my phone.
Temporarily reverting to the stock recovery and installing the OTA, then going back to custom recovery, seems a bit simpler than flashing the signed zip file and then re-installing recovery and SuperSU, but either way is not too bad. But being an engineer, I always have to find the optimum path and understand why things don't work the way I thought they should.
MidnightJava said:
What happens when you try to root? Does it seem successful, but then you don't actually have root access? Or do you get some failure indication when you flash SuperSU? I've rooted a few phones in the last few years, but I'm far from an expert. Hopefully someone else will jump in with some idea of what went wrong. Shooting somewhat in the dark, I'd say look at the version of SuperSU and make sure it's the latest and the right one for the ROM, look at read-write permissions on your storage (if you can, you may need root access to check it properly). Of course wiping cache is always a good step, and if nothing else works, maybe factory reset, re-lock the bootloader, and then unlock and flash custom recovery again, and see if root can be successful then.
Click to expand...
Click to collapse
It just tells me that I don't have access :/ Everything flashes perfectly fine, but then when I boot up and try to access root, it tells me that I don't have access. I've tried everything already :/
---------- Post added at 06:51 PM ---------- Previous post was at 06:47 PM ----------
Cholerabob said:
Did you guys remove the " Update Cyanogen recovery" in Dev options and "respect CM root settings " In SuperSU settings ?
Click to expand...
Click to collapse
I did do both :/
MidnightJava said:
I figured that was the case when it failed. What seems anomalous in my case is that even after reverting to the stock recovery and verifying that it was installed, OTAs would not succeed. I didn't know about the "respect CM root settings " In SuperSU settings that you mentioned. Maybe that was the problem? Either that or the fact that I tried to install the OTA first with the custom recovery. Certainly the fact that the incremental installation reported I was at a different build number than what was listed in /System/build.opts indicates something was out of whack on my phone.
Temporarily reverting to the stock recovery and installing the OTA, then going back to custom recovery, seems a bit simpler than flashing the signed zip file and then re-installing recovery and SuperSU, but either way is not too bad. But being an engineer, I always have to find the optimum path and understand why things don't work the way I thought they should.
Click to expand...
Click to collapse
Not really since the signed zip file come with superSU, after the install it will ask you if you want to install superSU automatically, and TWRP will too when you start your TWRP app on your phone after reboot. But to each his own
---------- Post added at 08:22 PM ---------- Previous post was at 08:19 PM ----------
vince.lupe said:
It just tells me that I don't have access :/ Everything flashes perfectly fine, but then when I boot up and try to access root, it tells me that I don't have access. I've tried everything already :/
---------- Post added at 06:51 PM ---------- Previous post was at 06:47 PM ----------
I did do both :/
Click to expand...
Click to collapse
Is your bootloader unlocked ? Reinstalled superSU ? Did you check with the fastboot command ? If you don't know how, look at Heisenberg's guide.
Cholerabob said:
Not really since the signed zip file come with superSU, after the install it will ask you if you want to install superSU automatically, and TWRP will too when you start your TWRP app on your phone after reboot. But to each his own
---------- Post added at 08:22 PM ---------- Previous post was at 08:19 PM ----------
Is your bootloader unlocked ? Reinstalled superSU ? Did you check with the fastboot command ? If you don't know how, look at Heisenberg's guide.
Click to expand...
Click to collapse
Yes, bootloader is unlocked and SuperSu was reinstalled :/