Related
Hi all, I'm considering purchasing an ATT G2 but don't want to if I'm going to have trouble rooting it. The TWRP thread says this:
YOU MUST ALREADY BE ROOTED! follow This guide to do so if you arent. BE AWARE THAT THIS ROOTING METHOD ONLY WORKS BEFORE TAKING THE OTA. IF YOU ARE UPDATED AND UNABLE TO ROOT, FOR NOW THE ONLY WAY IS TO FLASH BACK TO STOCK AND ROOT BEFORE THE OTA, THEN TAKE THE OTA, THEN INSTALL TWRP
Does this mean that the root method won't work out of the box, and I'll need to follow the process of restoring the stock pre-OTA image first? I am reading about a lot of troubles with this process, failed drivers, incorrect system image, etc. Can I feel confident this will work or is it a mixed bag?
I took the OTA after I got my G2 and then rooted with IORoot just fine. I even had to flash to stock (long story) using the 11A (OTA) files and re-rooted with IORoot. Then installed TWRP via flashify, after which I installed CleanROM....no probs here ?
simon_lefisch said:
I took the OTA after I got my G2 and then rooted with IORoot just fine. I even had to flash to stock (long story) using the 11A (OTA) files and re-rooted with IORoot. Then installed TWRP via flashify, after which I installed CleanROM....no probs here ?
Click to expand...
Click to collapse
So the initial root worked just fine after OTA without returning to stock? Great...thanks.
Yes. I'm on the Verizon variant, but again I bought my G2 took the OTA and rooted fine.
---------- Post added at 10:16 AM ---------- Previous post was at 10:14 AM ----------
Btw, after you root, download SuperSU from play store to replace the super user app that is used in the root method.
I have CWM installed, but I am running stock, no root. I got the 5.0.2 update today and told it to apply. Didn't pay close enough attention on reboot, was asked something about applying something in recover and don't remember if I said yes or no, then prompted for adding root (both of those were in CWM Recovery) and I know I said no to root. After the reboot I was still running 4.4.4.
So I guess I am ready to just manually download and install. Can anyone help me make sure which thread I should be looking at for instructions? I just feel like I have looked at everything and am not confident I am doing the right things. Can I just download the image linked in the Stock OTA URLs thread, then install from recovery?
Installed CWM without Root? :/
Sent from my SM-N9005
Posting at the top now:
Ok. For whatever reason (me not knownig 100% what I'm doing) I have upgraded to 10k and lost TWRP and Root.
After trying to downgrade to 10j I am not able to root following the recowvery method. I just keep getting 100 different errors.
10j also seems buggy as hell - getting constant "app has crashed" errors in rapid succession.
I am going to upgrade to 10k and leave without root for now.
Any bounties for 10k Root methods yet?
ANSWERED:
Currently on 10d firmware on my tmo v20. Should I bother with updating to 10j and trying to manually root? Do the updates really make any difference? If this is recommended, and someone knows a good walk through (I have read pages and pages and haven't made sense of it) I would forever appreciate it!!
It sounds like you are saying that you are already rooted and on 10d. If so, I suggest you just follow the directions in this thread to get to 10k while retaining root: https://forum.xda-developers.com/v20/how-to/h918-twrp-flashable-stock-firmwares-t3619671
If you are not already rooted, here's what you should do (IMHO):
Unlock the bootloader. This will force a factory reset, so make sure you have everything backed up. If you need to backup app data without root, use Helium from the app store. It requires a computer program, too.
Root the phone and install TWRP.
Use this to upgrade to 10k while retaining root: https://forum.xda-developers.com/v20/how-to/h918-twrp-flashable-stock-firmwares-t3619671
Profit.
Yeah, I am currently rooted on 10d.
My overall question is do I NEED to update to 10j? Is there any advantage, or am I ok just leaving it on 10d?
teads said:
Yeah, I am currently rooted on 10d.
My overall question is do I NEED to update to 10j? Is there any advantage, or am I ok just leaving it on 10d?
Click to expand...
Click to collapse
Honestly every update you get enhancements and bug fixes but IMO is up you can flash
This is the latest 10k : https://forum.xda-developers.com/v2...-firmwares-t3619671/post72673450#post72673450
Bootloader and Modem: https://forum.xda-developers.com/v20/development/firmware-twrp-flashable-bootloader-modem-t3547268
Ok. For whatever reason (me not knownig 100% what I'm doing) I have upgraded to 10k and lost TWRP and Root.
After trying to downgrade to 10j I am not able to root following the recowvery method. I just keep getting 100 different errors.
10j also seems buggy as hell - getting constant "app has crashed" errors in rapid succession.
I am going to upgrade to 10k and leave without root for now.
Any bounties for 10k Root methods yet?
teads said:
Ok. For whatever reason (me not knownig 100% what I'm doing) I have upgraded to 10k and lost TWRP and Root.
After trying to downgrade to 10j I am not able to root following the recowvery method. I just keep getting 100 different errors.
10j also seems buggy as hell - getting constant "app has crashed" errors in rapid succession.
I am going to upgrade to 10k and leave without root for now.
Any bounties for 10k Root methods yet?
Click to expand...
Click to collapse
No need to root 10k. Downgrade to 10j. Reroot 10j and install TWRP. Use the 10k upgrade THROUGH TWRP! That was your mistake. You didn't upgrade through TWRP.
Take a deep breath and start over.
I did upgrade through twrp. Didn't work.
teads said:
I did upgrade through twrp. Didn't work.
Click to expand...
Click to collapse
If you upgraded withTWRP, then you should STILL have TWRP, so you can install 10k and SuperSU through TWRP.
Sizzlechest said:
If you upgraded withTWRP, then you should STILL have TWRP, so you can install 10k and SuperSU through TWRP.
Click to expand...
Click to collapse
When I did, I read somewhere that I had to do something special in order to NOT lose TWRP, I hadn't done anything. I just upgraded through TWRP. When the device booted, I no longer had root, so I put it into adb and did ADB REBOOT RECOVERY. It launched into the red triangle android screen - where it should have been TWRP.
I did NOT have TWRP
Ok, I am now downgraded to 10j, and rooted with TWRP.
this thread: https://forum.xda-developers.com/v20/how-to/h918-twrp-flashable-stock-firmwares-t3619671
??
When I downloaded the zip and installed it in TWRP using install it seemed to have wiped TWRP from the phone.
"flash necessary partition images with the exception of recovery (to keep TWRP) from the KDZ
rename /system/recovery-from-boot.p to /system/recovery-from-boot.bak to prevent stock recovery from being installed on boot
wipes dalvik-cache and cache"
What do I rename, and where?? I don't see any files or any directories anything close to the referenced in the .zip provided
EDIT: I think I have it now... Android is upgrading
Hi, I have a european S8+ fully rooted and with TWRP.
Everything's working great so far but I read somewhere that I won't receive further OTA updates.
Can I install them manually with TWRP?
If yes, 3 questions:
1. Where can I get them?
2. Do I need every single update or are the newest update always containing the older updates as well?
3. Do I lose root or TWRP after installing an update?
I've rooted with Magisk by the way.
Typically if you're rooted and modified the system partition (BusyBox or twrp or whatever) the update will not install in stock recovery. Usually you have to unroot reinstall stock recovery and flash ota. There's toolkits out that can do that. Or you can just find an awesome rom like a rooted debloated rom thats just recently updated and just flash that. Or you can what till somebody snags the ota update location then posts that.
Although TWRP is *supposed* to be lokied, it turns out that all the 3.x versions are not properly lokied. This has been reported in the last couple of pages of this thread, and it's been reported in their bug tracker (although they seem to be ignoring it for now).
One of the users in that xda thread was kind enough to loki a few TWRP releases, but the latest one he did was v3.1.1.0, and he hasn't done any more since.
Can someone else be kind enough to Loki the latest version of TWRP for jflteatt, located here? (Preferably both IMG and TAR, so people can use it with whichever installation method they prefer/need)
My guide tells you how to Loki CWM recovery, it should work the same for TWRP (should is the keyword here).
https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
StoneyJSG said:
My guide tells you how to Loki CWM recovery, it should work the same for TWRP (should is the keyword here).
https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
Click to expand...
Click to collapse
Thank you. However, the method described requires root.
I had root on CyanogenMod 11, but ever since I flashed LineageOS 14.1, I haven't been able to root my phone without bricking it - so this method won't work for me.
How are you on lineage OS without having root? You need root to install a custom recovery which then in turn allows a custom ROM. I know lineage OS hides or does sometimes with superSU, so it might be hiding root as well (unless I am thinking of Oct OS).
Your phone is probably rooted, use the root checker app from the play store to check. If by chance somehow it's not, then use towel root, king root, one click root, safe root, CF auto root, or kingo root to root it. If all else fails you might have to ODIN back to stock, then root, then install the latest TWRP then Loki it using my guide then install lineage OS.
StoneyJSG said:
How are you on lineage OS without having root? You need root to install a custom recovery which then in turn allows a custom ROM. I know lineage OS hides or does sometimes with superSU, so it might be hiding root as well (unless I am thinking of Oct OS).
Your phone is probably rooted, use the root checker app from the play store to check. If by chance somehow it's not, then use towel root, king root, one click root, or kingo root to root it.
Click to expand...
Click to collapse
No, my phone is definitely not rooted. It *previously* had root under CyanogenMod 11. That's how I had a custom recovery installed. So I was able to use TWRP to flash LineageOS 14.1 just fine. However, here are the results of my trying to root this phone under LOS 14.1:
1. Magisk: Bricked on Samsung Logo.
2. SuperSU (normal systemless): Not installed properly. Seems to fail on patching the boot image.
3. SuperSU (system mode): Bricked on Lineage boot screen.
4. LineageOS addonsu: Installs fine, but doesn't seem to do anything. I still don't have root.
I've tried posting about this in a few places on xda, but so far, I haven't had any luck.
So *maybe* if I revert back to an older version of Android, I might be able to get a working root. But in order to be recent, it's looking like I have little choice but to finally retire this phone and get something newer. Which is unfortunate, because there's nothing wrong with the phone hardware-wise.
Perhaps I'll try one of the other root options you mentioned and hope it doesn't brick my phone as well.
That's really odd that you have a custom recovery and ROM without root. You might have to ODIN back to stock Android 4.2.2 jelly bean using the MDL firmware .tar file. Can you revert back to a TWRP that is Loki?
StoneyJSG said:
That's really odd that you have a custom recovery and ROM without root. You might have to ODIN back to stock Android 4.2.2 jelly bean using the MDL firmware .tar file. Can you revert back to a TWRP that is Loki?
Click to expand...
Click to collapse
I have a Lokied version of TWRP (3.1.1.0), which is working fine. But with all of the problems I've been having trying to get root, I was wondering if perhaps a newer version of TWRP might make the difference. That's why I was trying to get a Lokied version of the latest TWRP.
Ah so you're trying to gain root by flashing TWRP. No idea why lineage OS removed root, unless the people who made it built it that way. The only thing I can think of is either try all the root apps I mentioned before and if that doesn't work then ODIN back to MDL stock and use towel root to root. If lineage OS is anything like Oct OS, you will have to root using a root .zip file.
I wish I could be more help, but I haven't ever used lineage OS before due to liking touchwiz. I run golden eye ROM on my at&t Loki phone.
StoneyJSG said:
My guide tells you how to Loki CWM recovery, it should work the same for TWRP (should is the keyword here).
https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
Click to expand...
Click to collapse
Unfortunately it does not work:
Code:
1|[email protected]:/data/local/tmp # ./loki_flash recovery twrp.img
[+] loki_flash v1.1
[-] Input file is not a Loki image.
1|[email protected]:/data/local/tmp #
jabulon said:
Unfortunately it does not work:
Code:
1|[email protected]:/data/local/tmp # ./loki_flash recovery twrp.img
[+] loki_flash v1.1
[-] Input file is not a Loki image.
1|[email protected]:/data/local/tmp #
Click to expand...
Click to collapse
Thanks for trying it! It's now confirmed my guide is only for CWM recovery.
Not sure if you've already searched it out, but HERE is my thread with the latest Loki patched twrp. I lokied jfltexx 3.2.3-0 which works on the i337 (ATT) s4.
There's also this:
https://forum.xda-developers.com/galaxy-s4-att/general/lokid-jfltexx-twrp-att-vzw-s4-t3869503
StoneyJSG said:
There's also this:
https://forum.xda-developers.com/galaxy-s4-att/general/lokid-jfltexx-twrp-att-vzw-s4-t3869503
Click to expand...
Click to collapse
Your link IS my link from the post directly above yours
Oh crap haha so it is. Oops brain fart there, my fault.
StoneyJSG said:
Oh crap haha so it is. Oops brain fart there, my fault.
Click to expand...
Click to collapse
You're good ? I had it in a separate post, and I just created that thread the other day to give it a permanent home more easily found.