Hello folks,
after performing a more or less accidental factory reset I lost my SuperSU app (I am rooted and have TWRP 2.6.3.0 installed).To update the SU binary I need to boot into recovery. This seems somehow difficult on the LG 8.3, everybody seems to use Flashify (or similar apps) for that. But they do not work without SuperSU. Catch22.
The ultimate goal is to install CM11, but I am unsure how to proceed. How about this:
1) Reflash TWRP 2.6.3.0
2) Update to TWRP 2.6.3.2 using the Flashable zip v2.6.3.2 from here
3) Then flash CM11 using TWRP
Does that sound right? Thanks, Alex
hunibu said:
Hello folks,
after performing a more or less accidental factory reset I lost my SuperSU app (I am rooted and have TWRP 2.6.3.0 installed).To update the SU binary I need to boot into recovery. This seems somehow difficult on the LG 8.3, everybody seems to use Flashify (or similar apps) for that. But they do not work without SuperSU. Catch22.
The ultimate goal is to install CM11, but I am unsure how to proceed. How about this:
1) Reflash TWRP 2.6.3.0
2) Update to TWRP 2.6.3.2 using the Flashable zip v2.6.3.2 from here
3) Then flash CM11 using TWRP
Does that sound right? Thanks, Alex
Click to expand...
Click to collapse
Run the root process again. It should lay down SuperSU or SuperUser again (forget which one is actually used).
hunibu said:
Hello folks,
after performing a more or less accidental factory reset I lost my SuperSU app (I am rooted and have TWRP 2.6.3.0 installed).To update the SU binary I need to boot into recovery. This seems somehow difficult on the LG 8.3, everybody seems to use Flashify (or similar apps) for that. But they do not work without SuperSU. Catch22.
The ultimate goal is to install CM11, but I am unsure how to proceed. How about this:
1) Reflash TWRP 2.6.3.0
2) Update to TWRP 2.6.3.2 using the Flashable zip v2.6.3.2 from here
3) Then flash CM11 using TWRP
Does that sound right? Thanks, Alex
Click to expand...
Click to collapse
you cant flash a custom rom using 2.6.3.0 twrp. Update to version 2.6.3.2 as you said and install cm11
cbb77 said:
Run the root process again. It should lay down SuperSU or SuperUser again (forget which one is actually used).
Click to expand...
Click to collapse
Thanks, repeating the root process worked
Related
I am unlocked and trying to root Android 5.0.1. I have TWRP installed as recovery and I install SuperSU from a zip through TWRP, but when I check SuperSU in Android it says no SU binaries are installed. What am I doing wrong?
djr83 said:
I am unlocked and trying to root Android 5.0.1. I have TWRP installed as recovery and I install SuperSU from a zip through TWRP, but when I check SuperSU in Android it says no SU binaries are installed. What am I doing wrong?
Click to expand...
Click to collapse
Try to change recovery. For example, Philz Recovery.
vetalorlov said:
Try to change recovery. For example, Philz Recovery.
Click to expand...
Click to collapse
Tried PhilZ, same result.
I really need some help here, please... I can't find anything useful when googling either.
Guys here's the thing. Android N on my N5X. When trying to install TWRP 3.0.2.2 through Nexus Root Toolkit it first boots up the recovery then when I reboot to system and back there is no TWRP. But it remains there when I use the Root button which roots and installs custom recovery. So when I have root I have TWRP. Can't I have TWRP without root I wonder?
Suren Manukyan said:
Guys here's the thing. Android N on my N5X. When trying to install TWRP 3.0.2.2 through Nexus Root Toolkit it first boots up the recovery then when I reboot to system and back there is no TWRP. But it remains there when I use the Root button which roots and installs custom recovery. So when I have root I have TWRP. Can't I have TWRP without root I wonder?
Click to expand...
Click to collapse
Doesnt the toolkit have a check box to install a script or whatever to patch the system so the recovery wont be over written? Mine has it in flash recovery option!
I'm experiencing this issue as well. I tried to install TWRP after installing that October security updates. I wonder if there's something in the update that is preventing TWRP from installing?
hilla_killa said:
Doesnt the toolkit have a check box to install a script or whatever to patch the system so the recovery wont be over written? Mine has it in flash recovery option!
Click to expand...
Click to collapse
It has something called perm.flash.recovery.zipor something which is described to do the thing you said but the problem is when the phone gets the" flash perm.flash.recovery.zip" it does nothing. It does nothing even when I try to flash it manually when I get the "trial" TWRP which disappears after rebooting.
Had the same problem. I solved it by using the old fashioned way, with fastboot commands found on the TWRP page: https://twrp.me/devices/lgnexus5x.html
Of course, I used the last image: twrp-3.0.2-2-bullhead.img
Hello everyone, I am using OOS 4.1.6 on my new 3T, however I am unable to get root even though I have already tried with latest TWRP, magisk 12, and SuperSU 2.82. Nothing worked everytime I've got not rooted on root checker.
Please describe in steps what you did.
AcidNoteZ said:
Please describe in steps what you did.
Click to expand...
Click to collapse
Hi,
We unclocked the bootloader, then we did flash with twrp 3.1.0 and installed SU 2.82.
After doing all this, the phone was not restarting.
mittal.bti said:
Hi,
We unclocked the bootloader, then we did flash with twrp 3.1.0 and installed SU 2.82.
After doing all this, the phone was not restarting.
Click to expand...
Click to collapse
Well first of all, format your whole phone over TWRP. (System too, but make sure you have the full Oxygen OS zip on a computer.)
After formating all partitions, move the full OOS zip and Magisk 12.0 on your phone. Flash the OOS zip, restart your recovery and flash Magisk after it.
That worked 100% for me all the time.
If you still need assistance with that, we can setup Teamviewer so I can guide you through this.
mittal.bti said:
Hi,
We unclocked the bootloader, then we did flash with twrp 3.1.0 and installed SU 2.82.
After doing all this, the phone was not restarting.
Click to expand...
Click to collapse
Same here! The phone freezes in boot animation screen. Even the animation stopped!
Guessing it's about the f2fs file system. I used to have a situation like this with Oneplus 2. My step was to format data and cache partitions back to ext4, and that worked.
Using 3t now, still not rooted. Don't want to start over after bootloader unlocking
Sent from my ONEPLUS A3003 using Tapatalk
I had the same problem and was solved with twrp 3.0.4-1 and SuperSU-v2.82.
AcidNoteZ said:
Well first of all, format your whole phone over TWRP. (System too, but make sure you have the full Oxygen OS zip on a computer.)
After formating all partitions, move the full OOS zip and Magisk 12.0 on your phone. Flash the OOS zip, restart your recovery and flash Magisk after it.
That worked 100% for me all the time.
If you still need assistance with that, we can setup Teamviewer so I can guide you through this.
Click to expand...
Click to collapse
Should I flash whole os using twrp. Or should I flash Via adb sideload?
ajsonofgod said:
Should I flash whole os using twrp. Or should I flash Via adb sideload?
Click to expand...
Click to collapse
If you still want root, twrp, if dont flash it over adb
AcidNoteZ said:
If you still want root, twrp, if dont flash it over adb
Click to expand...
Click to collapse
Ok, I will try and update here then.
I'd say wipe everything possible in TWRP except for system partition, then boot the system and then eventually flash some kind of a root package - either Magisk or SuperSU. I always do it that way and it works. I am not really sure but otherwise it might have something to do with the data encryption.
Use following and you should be all set (just did it 2 days ago):
1st Flash Stock Recovery (go back to stock - https://forums.oneplus.net/threads/...-3-3t-and-go-back-completely-to-stock.456232/
Flash TWRP after you achieve STOCK OS 4.1.6.
Use this TWRP version for now (there is some issue with 3.1.1-2 i saw on forums):
twrp-3.1.1-0-oneplus3t.img
To Root just use Magisk-v13.3.zip (IMO way better than SuperSu + has MagiskHide for AndroidPay/Snapchat/SafetyNet checks):
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
That is it, done!
Showbiz81 said:
I had the same problem and was solved with twrp 3.0.4-1 and SuperSU-v2.82.
Click to expand...
Click to collapse
Thanks you are a life saver
I had the same problem and was solved with twrp 3.0.4-1 and Magisk-v13.3
Hi!
I'm currently using flash rom and kernel. As I've always done so, I like to flash TWRP and then SuperSU to enjoy the little tweaks offered by root.
Since the last 8.1 update, I'm facing a few issues that in my opinion are correlated.
First, flashing TWRP works well, but it seems not to be systemless, i.e. when I reboot my device the proper way, TWRP disappears.
Secondly, when I try to flash the latest stable SuperSU zip through my working TWRP (it's a one shot...), the process gives me no error, but then on the first boot, I get stuck on the huge Google logo... The only thing I can do is re-flashing boot.img but obviously the SuperSU app didn't install...
What should I do? Install a beta SuperSU version? Try Magisk (honestly, I don't really like it...)
Thanks for your help and patience!
azertguigui said:
Hi!
I'm currently using flash rom and kernel. As I've always done so, I like to flash TWRP and then SuperSU to enjoy the little tweaks offered by root.
Since the last 8.1 update, I'm facing a few issues that in my opinion are correlated.
First, flashing TWRP works well, but it seems not to be systemless, i.e. when I reboot my device the proper way, TWRP disappears.
Secondly, when I try to flash the latest stable SuperSU zip through my working TWRP (it's a one shot...), the process gives me no error, but then on the first boot, I get stuck on the huge Google logo... The only thing I can do is re-flashing boot.img but obviously the SuperSU app didn't install...
What should I do? Install a beta SuperSU version? Try Magisk (honestly, I don't really like it...)
Thanks for your help and patience!
Click to expand...
Click to collapse
Do this, first boot twrp, don't flash it. Once booted flash SU 2.82 SR5. Then boot back into the bootloader from twrp and flash twrp. Works for me.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Do this, first boot twrp, don't flash it. Once booted flash SU 2.82 SR5. Then boot back into the bootloader from twrp and flash twrp. Works for me.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Huge thanks for this!!! I was having the exact same problem (boot hangs at Google logo) and this resolved it!
I noticed that afterwards in the apps drawer I could not find any SuperSU, but doing adb shell and then invoking su worked, so I then just installed the supersu app from the play store to handle prompts (it seems without the app, root is enabled silently and doesn't seem like that great of an idea).
-----------EDIT------------
After installing the app from play store, DO NOT allow it to update the supersu binaries! I ran into bootloop again after that, and had to re-flash SR5 again. Seems like that's the magical version to use!
You're right about having super su update. I had the same problem.
Edit, I just checked and I'm actually using SR3. SuperSu then updated those binaries without a problem.
Hi, thanks for the answers. What do you guys mean by 'booting twrp without flashing it'? What's the fastboot command?
azertguigui said:
Hi, thanks for the answers. What do you guys mean by 'booting twrp without flashing it'? What's the fastboot command?
Click to expand...
Click to collapse
fastboot boot (drag and drop twrp.img file here)
Sent from my Nexus 5X using Tapatalk
Well for the record, I did the following
Code:
fastboot boot twrp-3.2.1-0-bullhead
Then, I installed SuperSU downloaded here. I went back to fastboot and used
Code:
fastboot flash twrp-3.2.1-0-bullhead
but I still got stuck on the Google logo, meaning that my boot was corrupted or something... I then flashed the original Google boot.img
Code:
fastboot flash boot.img
and re-did the process of flashing SuperSU but I wisely chose to find a SR5 version of the file. I didn't flash TWRP after that and my phone booted normally with supersu.apk installed in it and the root privileges granted ... I don't know if I should try flashing TWRP again since my phone is working fine right now, but thanks anyway for the tip of booting to TWRP and not flashing it directly!
Hi all!
I'm with the 9.2.2.0 Global.
I have the original recovery, just supersu flash with a temporary TWRP (boot instead of flash).
Update a few months ago, when the update came out, to version 9.2.3.0, and I was not able to reboot from TWRP to root the system again, so I went back to version 9.2.2.0.
Is there a method to root easily if I update now?
Do you think I'll have problems with version 9.5.3.0 again ?!
Thank you very much!
You can root this version by supersu.zip 2.82 (don't use supersu.zip SR2.82)! Flash it over recovery.
bahuy2003 said:
You can root this version by supersu.zip 2.82 (don't use supersu.zip SR2.82)! Flash it over recovery.
Click to expand...
Click to collapse
The problem is not in sueprsu flash.
I have the problem to booting the TWRP after updating.
Does BOOT, but can not mount any partition, and any change becomes a soft brick.
Don't use SuperSU, use latest beta Magisk instead.
And whats the problem if you flash TWRP 3.2.1-0 ?