Related
I've seen and answered this question quite a few times so I thought I'd just write down the procedure once so everyone can find it.
So you want the latest OTA and want it rooted but you have no idea how to get there? I can help.
Prior to yesterday I was running rooted stock with TWRP recovery. The OTA failed of course.
In order to install it and root I did the following.
1) install rooted stock image via odin (found at http://forum.xda-developers.com/showthread.php?t=1739426) This re-nstalled stock recovery.
2) install and run voodoo ota root keeper from the play store to preserve root.
3) took OTA download and let it install
4) ran voodoo OTA rootkeeper to restore root again
5) Install goo manager from play store
6) install twrp via goo manager
7) made a rooted stock nandroid backup.
The above procedure didn't wipe any of my data or settings because I came from rooted stock to begin with. I just used odin to restore the recovery and missing bloatware..
Hope this helps
Do you have the clockworkmkd recovery file I need to flash through odin? Does this mean I don't have to use adb?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Mastermachetier said:
Do you have the clockworkmkd recovery file I need to flash through odin? Does this mean I don't have to use adb?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I didn't use ADB. I used twrp for my recovery, but you can install rom manager and cwm recovery with it instead of goo manager and twrp.
I lost my root when i did the update...
can you give step by step on how to root again after the update and install the google universal search?
thanks...
Flashed the rooted stock image via Odin, update failed at 27%. Any ideas?
No idea. Just reporting on what worked for me.
Tlo218 said:
Flashed the rooted stock image via Odin, update failed at 27%. Any ideas?
Click to expand...
Click to collapse
If you've disabled or uninstalled stock at&t and Sammy apps (like Flipboard, clocks, etc.) the update will fail. You need to enable/reinstall stock apps.
Hi, I used Voodoo Root Keeper to regain root. However, in my device status it is now saying modified instead of normal. How can I fix that?
You can't. Don't worry about it.
one028 said:
I lost my root when i did the update...
can you give step by step on how to root again after the update and install the google universal search?
thanks...
Click to expand...
Click to collapse
That's beyond the scope of my original post.
knarfl1 said:
If you've disabled or uninstalled stock at&t and Sammy apps (like Flipboard, clocks, etc.) the update will fail. You need to enable/reinstall stock apps.
Click to expand...
Click to collapse
It looked like reflashing the rooted stock rom did reinstall the bloat I removed.
gunnyman said:
I've seen and answered this question quite a few times so I thought I'd just write down the procedure once so everyone can find it.
So you want the latest OTA and want it rooted but you have no idea how to get there? I can help.
Prior to yesterday I was running rooted stock with TWRP recovery. The OTA failed of course.
In order to install it and root I did the following.
1) install rooted stock image via odin (found at http://forum.xda-developers.com/showthread.php?t=1739426) This re-nstalled stock recovery.
2) install and run voodoo ota root keeper from the play store to preserve root.
3) took OTA download and let it install
4) ran voodoo OTA rootkeeper to restore root again
5) Install goo manager from play store
6) install twrp via goo manager
7) made a rooted stock nandroid backup.
The above procedure didn't wipe any of my data or settings because I came from rooted stock to begin with. I just used odin to restore the recovery and missing bloatware..
Hope this helps
Click to expand...
Click to collapse
worked fine for me
There's a much easier method to get root back after the update.
Flash CWM/TWRP
Flash the file I attached below.
Install Busybox from market
Reboot
Done deal
It does work. I tested earlier today from G1 stock unrooted. Pulled and installed the update, flashed CWM. Flashed the attached file, busybox download and profit. Then used gooomanager to change to TWRP
Here's the original site I read about this method way back when...
http://www.theandroidsoul.com/easy-guide-root-att-galaxy-s3/
Gunny's method does work, just giving another option
OP guides worked for me. Thanks
I like the new keyboard, less errors.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Thanks for the info just would rather have a CMW flashable with root
I just want to say thank you I really appreciate your help and the time you put in to provide this info it worked like a charm and I really appreciate the help
I didn't loose root
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
z45123 said:
I just want to say thank you I really appreciate your help and the time you put in to provide this info it worked like a charm and I really appreciate the help
Click to expand...
Click to collapse
You're welcome.
So does this work if I lost root during the process?
There's a much easier method to get root back after the update.
Flash CWM/TWRP
Flash the file I attached below.
Install Busybox from market
Reboot
Done deal
It does work. I tested earlier today from G1 stock unrooted. Pulled and installed the update, flashed CWM. Flashed the attached file, busybox download and profit. Then used gooomanager to change to TWRP
dahlem said:
So does this work if I lost root during the process?
There's a much easier method to get root back after the update.
Flash CWM/TWRP
Flash the file I attached below.
Install Busybox from market
Reboot
Done deal
It does work. I tested earlier today from G1 stock unrooted. Pulled and installed the update, flashed CWM. Flashed the attached file, busybox download and profit. Then used gooomanager to change to TWRP
Click to expand...
Click to collapse
Yes, it does work. Get a custom recovery back (CWM) and flash the file I attached in my earlier post. Saves the time from flashing a stock rooted ROM and going from there as a starting point.
As title.
I always rooted my gnex using an unsecure boot image.
Now I can boot with an unsecure boot image, I can push/chmod su, superuser and daemonsu using adb but than what should I do?
What should I do to root the phone?
Thanks.
sblantipodi said:
As title.
I always rooted my gnex using an unsecure boot image.
Now I can boot with an unsecure boot image, I can push/chmod su, superuser and daemonsu using adb but than what should I do?
What should I do to root the phone?
Thanks.
Click to expand...
Click to collapse
You can either flash the SuperSU .zip by Chainfire in a custom recovery or you can take the .zip apart and do it manually. Push all of the files in the .zip to the corresponding locations on your phone and look at the updater-script to see if you need to do any other commands. Root in 4.3 is different and Chainfire's method basically uses a script to enable it at every boot. I have not read about any other superusers working for 4.3, though I could have missed it.
mwalt2 said:
You can either flash the SuperSU .zip by Chainfire in a custom recovery or you can take the .zip apart and do it manually. Push all of the files in the .zip to the corresponding locations on your phone and look at the updater-script to see if you need to do any other commands. Root in 4.3 is different and Chainfire's method basically uses a script to enable it at every boot. I have not read about any other superusers working for 4.3, though I could have missed it.
Click to expand...
Click to collapse
is there a way to undo this process once done?
sblantipodi said:
is there a way to undo this process once done?
Click to expand...
Click to collapse
Naturally, backtrack your steps.
beekay201 said:
Naturally, backtrack your steps.
Click to expand...
Click to collapse
Can I safely remove all the files copied from the zip ?
sblantipodi said:
Can I safely remove all the files copied from the zip ?
Click to expand...
Click to collapse
Yes.. Restoring whatever in the process..if you modified anything that was there already.
Galaxy Nexus 4.3 NO ROOT w/ SuperSU_1.51.zip
Ok XDA - you're my only hope. I've completely lost root after flashing the last two PA releases. I just flashed the most recent (dirty), flashed GApps, rebooted, Flashed SuperSU_1.51/zip, Wiped Dalvik/cache in TWRP, rebooted, SuperSU says no binary installed, please manually root. Losing my mind here, need to get rooted again, could someone lend me some backup?
innerspace said:
Ok XDA - you're my only hope. I've completely lost root after flashing the last two PA releases. I just flashed the most recent (dirty), flashed GApps, rebooted, Flashed SuperSU_1.51/zip, Wiped Dalvik/cache in TWRP, rebooted, SuperSU says no binary installed, please manually root. Losing my mind here, need to get rooted again, could someone lend me some backup?
Click to expand...
Click to collapse
Did you manage to solve this problem?
I've got the same problem now...(There is no SU Library installed... This is a problem!)
Previously I had root but SU Library wouldn't update, ChainFire told me to re-root which caused me to lose root completely, tried again to root, without any luck.
Stuck without Root
AMKhatri said:
Did you manage to solve this problem?
I've got the same problem now...(There is no SU Library installed... This is a problem!)
Previously I had root but SU Library wouldn't update, ChainFire told me to re-root which caused me to lose root completely, tried again to root, without any luck.
Stuck without Root
Click to expand...
Click to collapse
download the most current supersu.zip and flash it in recovery.
if you're using a toolkit (i bet you are) STOP IT.
Zepius said:
download the most current supersu.zip and flash it in recovery.
about 2 minutes prior to your reply, I updated the "Toolkit" along with all the other items (supersu, img, etc..)
And after that, my device is rooted again.
Although, the main reason I started all of this was to update my device's build further, but it seems the OTA update is now gone... I'll have to wait for it appear again and see how it goes...
Zepius said:
I'll keep that in mind...
if you're using a toolkit (i bet you are) STOP IT.
Click to expand...
Click to collapse
Thanks for the reply!
Much appreciated!
Click to expand...
Click to collapse
AMKhatri said:
Did you manage to solve this problem?
I've got the same problem now...(There is no SU Library installed... This is a problem!)
Previously I had root but SU Library wouldn't update, ChainFire told me to re-root which caused me to lose root completely, tried again to root, without any luck.
Stuck without Root
Click to expand...
Click to collapse
I did, though I'm fuzzy on how exactly, and no, no toolkits here. IIRC I ended up wiping, updating recovery, and then manually flashing, but I had to do it multiple times to get root to stick. Sorry I don't have any better info to provide, glad to hear a) I wasn't the only one who experienced this problem, and b) you got your root back.
It seems there would be a problem in flashing normal downloaded SU and have to go through the long process of flashing systemless SU after which have to upgrade it.
Is it normal for you guys too?
How come 1+3 bricks after installing normal SU?
b.t.w. personal note: thanks to one of the oneplus rep that was in the euro tour in Rome the TWRP recovery fix worked (sorry forgot your name ). Really appreciate the chat and help out!
No, i downloaded normal su (SuperSU) and then flashed it through TWRP. I don't know which su you are using, but there are loads of us who have installed SuperSU without an issue.
nemexs said:
It seems there would be a problem in flashing normal downloaded SU and have to go through the long process of flashing systemless SU after which have to upgrade it.
Is it normal for you guys too?
How come 1+3 bricks after installing normal SU?
b.t.w. personal note: thanks to one of the oneplus rep that was in the euro tour in Rome the TWRP recovery fix worked (sorry forgot your name ). Really appreciate the chat and help out!
Click to expand...
Click to collapse
You may have the wrong flashable, flashing supersu on the OP3 for me is very quick and painless. Make sure you have the latest from chainfire's website v2.76 at the time of me posting this. : http://download.chainfire.eu/supersu-stable
PS: regular supersu is both systemless and "normal" root it makes a decision during installation determining whether your device can support normal root and if not then it does a systemless boot.img patch.
StykerB said:
You may have the wrong flashable, flashing supersu on the OP3 for me is very quick and painless. Make sure you have the latest from chainfire's website v2.76 at the time of me posting this. : http://download.chainfire.eu/supersu-stable
Click to expand...
Click to collapse
You beat me to pointing him to it. If I can add, there's a dedicated SuperSU thread to seek help if SuperSU causes an issue:
http://forum.xda-developers.com/showthread.php?t=1538053
Highly unlikely but just in case. If you are not sure, there are sufficient number of toolkits out there that can simplify the job for you.
@tropicanapure @StykerB
Have tried them the only way I can flash SU is downloading @ahmed_radaideh 's oneplus3 toolkit and then flashing his SU. Tried the normal version and the problem seems to be present (brick), yes chainfire's su. If I don't want to do full wipe I'd have wipe system and just reflash stock and then systemless su
nemexs said:
@tropicanapure @StykerB
Have tried them the only way I can flash SU is downloading @ahmed_radaideh 's oneplus3 toolkit and then flashing his SU. Tried the normal version and the problem seems to be present (brick), yes chainfire's su. If I don't want to do full wipe I'd have wipe system and just reflash stock and then systemless su
Click to expand...
Click to collapse
Then you may want to check the process y you are using for this.
If I can ask what exactly are you trying to fix? Do you already have SuperSU installed? And you are trying to move to systemless?
Or are you unable to install SuperSU itself? If yes, then you may want to post to the SuperSU thread too.
tropicanapure said:
Then you may want to check the process y you are using for this.
If I can ask what exactly are you trying to fix? Do you already have SuperSU installed? And you are trying to move to systemless?
Or are you unable to install SuperSU itself? If yes, then you may want to post to the SuperSU thread too.
Click to expand...
Click to collapse
I had no problem in installing it systemless, however just wanted to see if everyone else had to go through the same process. It seems not, now I'm trying to find out how come I can't install normally.
nemexs said:
I had no problem in installing it systemless, however just wanted to see if everyone else had to go through the same process. It seems not, now I'm trying to find out how come I can't install normally.
Click to expand...
Click to collapse
You still haven't mentioned the process you use[emoji6]
The process most commonly used via TWRP is to download the zip from the link above and flash it. That's all there is to it.
tropicanapure said:
You still haven't mentioned the process you use[emoji6]
The process most commonly used via TWRP is to download the zip from the link above and flash it. That's all there is to it.
Click to expand...
Click to collapse
my bad, yes I use twrp method 3.0.2 the most recent one, flash stock rom and then flash su
nemexs said:
my bad, yes I use twrp method 3.0.2 the most recent one, flash stock rom and then flash su
Click to expand...
Click to collapse
Assuming your bootloader is already unlocked beforehand, the straight answer to your question is yes, that's how most of us do it.
No problem with flashing SU whatsoever,
and i rather not to use any toolkit to flash either recovery or anything,
fastboot for recovery and recovery for anything else,
Simple, straight and safe
otonieru said:
No problem with flashing SU whatsoever,
and i rather not to use any toolkit to flash either recovery or anything,
fastboot for recovery and recovery for anything else,
Simple, straight and safe
Click to expand...
Click to collapse
doesn't work for me.
If this is the last ever update, then i guess its time to finally root it in order to get support. Any help?
mcmikechan123 said:
If this is the last ever update, then i guess its time to finally root it in order to get support. Any help?
Click to expand...
Click to collapse
Flash MESA's complete 30G rom here.
https://forum.xda-developers.com/showpost.php?p=72931940&postcount=98
When the flash is complete, flash magisk before rebooting.
You'll be on the latest 30G build, with root. Additionally, you can use TWRPs file manager to delete the "recovery-from-boot.p" file to ensure twrp is not overwritten by stock recovery.
Good day, I take the answer to ask if this kdz is made with flashtool 2014 or which tool.
Will I be able to install fullmics later?
Thank you very much.
Pelau76 said:
Good day, I take the answer to ask if this kdz is made with flashtool 2014 or which tool.
Will I be able to install fullmics later?
Thank you very much.
Click to expand...
Click to collapse
Its a zip you flash in twrp. As long as you keep root and twrp recovery you can switch to fullmics no problem. If you need to obtain root, flash 30D or below with flash tool, root with kingroot and flash twrp
Ok. Thanks
help
i have lg g3 D851 firmware v30e
how can i root it and get v30g and root + twrp
and can i get twrp without root ?
daliyoos said:
i have lg g3 D851 firmware v30e
how can i root it and get v30g and root + twrp
and can i get twrp without root ?
Click to expand...
Click to collapse
You cant root 30e. You have to downgrade to 30D or lower with lg flash tool (https://forum.xda-developers.com/tm...g3-d851-t-mobile-downgrading-rooting-t3608851), then root, install twrp, then flash the 30g zip and reroot before rebooting.
billard412 said:
You cant root 30e. You have to downgrade to 30D or lower with lg flash tool (https://forum.xda-developers.com/tm...g3-d851-t-mobile-downgrading-rooting-t3608851), then root, install twrp, then flash the 30g zip and reroot before rebooting.
Click to expand...
Click to collapse
when i flash the 30g zip can i root using root using magisk ? or root with supersu zip?
daliyoos said:
when i flash the 30g zip can i root using root using magisk ? or root with supersu zip?
Click to expand...
Click to collapse
Id use magisk. Supersu gives me trouble.
billard412 said:
Id use magisk. Supersu gives me trouble.
Click to expand...
Click to collapse
Mmm i preferred supersu, what's happen if i use supersu instead of magisck what kind of troubles are you talking sir
Bootlop for example
mtkmanjaro said:
Mmm i preferred supersu, what's happen if i use supersu instead of magisck what kind of troubles are you talking sir
Bootlop for example
Click to expand...
Click to collapse
Just didnt work on reboot. Never caused a bootloop that i can remember. Also causes half my apps not to function since it doesn't give the option to hide root. Magisk just functioned better imo. Was just a suggestion. If you wanna use supersu, more power to u. Do a backup first
billard412 said:
Just didnt work on reboot. Never caused a bootloop that i can remember. Also causes half my apps not to function since it doesn't give the option to hide root. Magisk just functioned better imo. Was just a suggestion. If you wanna use supersu, more power to u. Do a backup first
Click to expand...
Click to collapse
Ok thanks dude, i think we needs to patch kernel in order to use super Su. I remember some one patch the kernel in 30 e firmware and super Su works well
I did his method successfully and everything came out perfect. thank you very much.
Magisk suggests to me to update to 14.0, there is some recommendation of not to realize it by the doubts.
billard412 said:
Flash MESA's complete 30G rom here.
https://forum.xda-developers.com/showpost.php?p=72931940&postcount=98
When the flash is complete, flash magisk before rebooting.
You'll be on the latest 30G build, with root. Additionally, you can use TWRPs file manager to delete the "recovery-from-boot.p" file to ensure twrp is not overwritten by stock recovery.
Click to expand...
Click to collapse
ive never rooted and flashed anything before, this is my 1st time so everything is new to me. idk what magisk & twrp is, can you explain. also how do i do what you instructed?
I keep having this problem. I just tried both KINGROOT and CF-AUTO ROOT.
After doing this whole process through ODIN. I then try to flash the latest TWRP from their website : dl.twrp.me/jfltetmo/twrp-3.2.0-0-jfltetmo.img.tar.html
Then after that finishes, I try to boot into recovery and it gives me the message: recovery is not seandroid enforcing and just sits there.
I have a tmobile s4.
and I also checked if I am indeed rooted by using an app from the play store to check root and it shows Im rooted.
Any help would be great.
Root isn't needed to flash a twrp.
Tried flashing the latest stock rom and twrp without rooting the phone?
audit13 said:
Root isn't needed to flash a twrp.
Tried flashing the latest stock rom and twrp without rooting the phone?
Click to expand...
Click to collapse
Yup didn't work after trying it all the only thing that did work was SkipSoft Unified Android Toolkit and it was the easiest thing I ever used.
Krappa420 said:
Yup didn't work after trying it all the only thing that did work was SkipSoft Unified Android Toolkit and it was the easiest thing I ever used.
Click to expand...
Click to collapse
I have the exact problem, can you kindly explain in details how you went about it? I already downloaded SkipSoft.
Same issues here, buddy.
I tried to work on solving it out for approximately 8 hours and still no sign of success. Tried to reflash stock OS back on the phone via ODIN and it went successful. Tried CF-Auto-root file and it went through successful. But when it only came to the TWRP file, it went successful onto flashing on ODIN's side, but now something is interfering with the boot up process onto TWRP now. Hopefully there's a alternative towards this issue, since i've been wanting to reflash a Nougat OS onto the device.
Edit: I give credit to @Krappa420 for the mention of "SkipSoft Unified Android Toolkit" because i just installed the program on my laptop now and it went successful. But since i already had other materials pre-installed, some others with ODIN and ADB installed can just download this TWRP version here: https://dl.twrp.me/jfltexx/twrp-2.7.0.0-jfltexx.img.html
Edit #2: Seems that the TWRP version is too old to flash some of the newer OS's, such as nougat itself. Will find a way to update TWRP without breaking the boot up process, like the past attempts
Edit #3: After fiddling with TWRP versions 2.7.0.0 and up, i managed to get it capped up to 3.1.1 any future versions will most likely not work, so you're capped at 3.1.1 Here's the link for flashing it with ODIN: https://dl.twrp.me/jfltexx/twrp-3.1.1-0-jfltexx.img.tar.html
So you twrp 3.1.1 and it will work right
I having the same issue
Thank you
so do i need to install cf-auto root first or the twrp 3.11
what are the steps to install
Thank you for helping a disabled veteran
timj3371 said:
so do i need to install cf-auto root first or the twrp 3.11
what are the steps to install
Thank you for helping a disabled veteran
Click to expand...
Click to collapse
It wouldn't really matter what order you're using.
You can use CF-Auto-Root to root it for you while you have stock recovery still, and after you can flash to TWRP and use a custom recovery afterwards
Or you can flash TWRP first and flash a SuperSU zip file afterwards and it'll give you root while maintaining to have TWRP installed.
But to sum it up, it wouldn't matter what order you choose. Help yourself
Trwp
What version of twrp I need to use
Thank you
timj3371 said:
What version of twrp I need to use
Thank you
Click to expand...
Click to collapse
TWRP version 3.1.1
Thank you for the help I have lineage installed. Wow so fast. How ever when trying to root it I get a error says binary occupied. If I uninstall I get no root available. How do I install root ? Thank you so much
A disabled veteran
timj3371 said:
Thank you for the help I have lineage installed. Wow so fast. How ever when trying to root it I get a error says binary occupied. If I uninstall I get no root available. How do I install root ? Thank you so much
A disabled veteran
Click to expand...
Click to collapse
Before anything, try to install the SuperSU app over on the play store, if it says you're not rooted, you may have to restart the whole process within TWRP and reflash the SuperSU Zip file.
Thank you
Says the binary is occupied in su
Where do I find su zip
Should I use the chain fire auto zip
Thanks
timj3371 said:
Says the binary is occupied in su
Where do I find su zip
Should I use the chain fire auto zip
Thanks
Click to expand...
Click to collapse
Try this one: https://download.chainfire.eu/696/supersu/
If it keeps on persisting, I'll have to find another way
I tried that file and it just sits in booting. I left it be then reinstated the ROM. Still no root its OK tight not to have root
Thank you
timj3371 said:
I tried that file and it just sits in booting. I left it be then reinstated the ROM. Still no root its OK tight not to have root
Thank you
Click to expand...
Click to collapse
Yeah try to re-flash the ROM again but this time flash magisk through TWRP since SuperSU is being trippy on your S4
Thank you for the help
Dummy me I found out from reading other forums you have to go in to tools and enable root after going in to recovery and flash the root file in the extra section.
Every thing works
Thank you so much
Disabled veteran