Related
Hello everyone,
I'm facing a very odd issue. I recently installed 7.1.2 from factory image and decided to also install TWRP in order to install a few modifications.
I was able to install the new kernel that allows Android pay to work with unlocked bootloader just fine.
However, I can't install SuperSU for some reason. I'm installing the zip file from TWRP just fine, however when I go searching for the app it's not there, and even if I install it from Google play it's telling me the system is not rooted.
I tried even downgrading a version of TWRP and SuperSU and still no go.
Anyone have any idea what is going on?
Thanks!
wireaudio said:
Hello everyone,
I'm facing a very odd issue. I recently installed 7.1.2 from factory image and decided to also install TWRP in order to install a few modifications.
I was able to install the new kernel that allows Android pay to work with unlocked bootloader just fine.
However, I can't install SuperSU for some reason. I'm installing the zip file from TWRP just fine, however when I go searching for the app it's not there, and even if I install it from Google play it's telling me the system is not rooted.
I tried even downgrading a version of TWRP and SuperSU and still no go.
Anyone have any idea what is going on?
Thanks!
Click to expand...
Click to collapse
Are you flashing su2.79sr3 ?
Make sure your using this one. Is the newest
Correct, I am flashing the newest and also tried previous version well, still no go!
wireaudio said:
Correct, I am flashing the newest and also tried previous version well, still no go!
Click to expand...
Click to collapse
Hello,
I'd try reflashing stock boot.img from your 7.1.2 factory image.
The fastboot boot TWRP.img and install TWRP zip.
Install SuperSU: https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
Reboot to system. From here you should have superSU installed.
Reboot to TWRP and install custom kernel zip.
Hopefully it will work...
Good luck...
I will try that, in that order, but before i do, can someone give me a brief explanation on what slot A and slot B are and what they do? I have a feeling it may have something to do with this. I looked for answers on the forums and I wasn't able to find a clear answer.
wireaudio said:
I will try that, in that order, but before i do, can someone give me a brief explanation on what slot A and slot B are and what they do? I have a feeling it may have something to do with this. I looked for answers on the forums and I wasn't able to find a clear answer.
Click to expand...
Click to collapse
Hello, it's right here: https://www.xda-developers.com/exclusive-dual-boot-may-be-possible-on-pixel-phones/
I also see you posting in another thread. I'm going to answer your question here, so all Infos remain in the same place...
wireaudio said:
I basically installed the factory image without the -w flag, turn booted in TWRP (without flashing TWRP) and installed kernel, then flashed super SU then rebooted. Didn't work so I rebooted in TWRP and flashed TWRP and then flashed SuperSU. Note that I had SuperSU installed in 7.1.1 so I assumed it would overwrite. It didn't work so I uninstalled old SuperSU and re-flashed SuperSU 2.79. it still didn't work so I downgraded SuperSU and TWRP one release and reinstalled. Still no go. And that's where I'm at.
---------- Post added at 09:18 AM ---------- Previous post was at 08:47 AM ----------
Better question is, how do we select what slot stuff gets installed in? It doesn't seem to be clear, more like a game of chance!
Click to expand...
Click to collapse
Your explanation in the other post and this one are different. Just try in the order from my previous post...
For your information, you can choose the active slot. It's not "like a game of chance". Just use the proper command:
fastboot --set-active=a
Or
fastboot --set-active=b
Good luck...
Hi,
Googled a while and looked around in the forum but did not find anyone with the exact same issue as me so here goes.
Maybe someone could tell me where exactly I am doing wrong.
I have a LG Nexus 5X, latest Oreo 8.1 official update.
I want to install a custom kernel to improve performance and/or battery life.
Never rooted or anything like that so I googled around to know what to do.
So I unlocked the bootloader and flashed the latest TWRP custom recovery (v3.2.1-0).
The first strange thing unlike what I kept reading in tutorials and forums is that, although I did reboot directly into recovery after flashing TWRP, and completed flashing TWRP using its interface, I was never able to reboot into TWRP unless I flashed it again. As if TWRP could not avoid being overridden by the stock recovery. So to get back to TWRP I always have to:
reboot into the bootloader: adb reboot bootloader
flash TWRP: flash recovery twrp-3.2.1-0-bullhead.img
reboot bootloader: fastboot reboot
immediately start into to bootloader (power + vol down)
choose 'Recovery Mode' from there
Which seemed odd, that TWRP wouldn't 'stick', although I was not root yet.
Which gets me to the second part. All I wanted was to root my phone.
So after not finding a consistent way to do it - it seemed every website I visited gave me slightly different instructions to do so, I took the chance and did the following:
download latest SuperSU flashable zip file (v2.82) and copy it to internal storage
go through the process I describe in the list above to get into TWRP
install SuperSU zip file (via Install TWRP option, logs seemed ok, warned me it would take a while to boot again)
reboot, wait until it boots
But the phone got stuck in the boot screen - OS does not start to load - for at least half an hour.
Luckily, probably because the OS did not load, TWRP was not overridden and so I have access to it.
My main problem at this point is that, as a newbie on this, I am not sure what can I do in TWRP to try to restore the OS.
I have tried to restore a Nandroid backup I performed before all this, and also tried to Wipe Data / Cache and Dalvik.
Both did not work - OS still won't load.
What can I do at this point? Wipe System partition? Wouldn't that delete my Nandroid backup?
Maybe 'sideload' (not sure if the right term) an official google image for my Nexus?
Sorry again if questions like this can be easily found around the forum, but from the threads I checked I did not bump into the exact same scenario...
Thank you in advance
So in the meantime I have wiped system partition, no success either.
Ended up restoring my Nandroid backup and sideloading the latest OTA from Google, which successfully restored my phone.
Of course TWRP was overridden once again.
So back to the start: can anybody help me out on the best way to permanently flash TWRP and root the phone?
Thanks!
Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)
jbaumert said:
Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)
Click to expand...
Click to collapse
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?
disacrol said:
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?
Click to expand...
Click to collapse
Here's the guide stickied that should walk you through the TWRP install. https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
As for Magisk. There is a whole forum dedicated to it - https://forum.xda-developers.com/apps/magisk - Short story install the latest stable version (16.0) and call it good. I haven't had any issues with recent kernel builds including Franco, EX, etc.... One thing to keep in mind is that Magisk always gets flashed after the kernel install as it does some patching of the boot.img as part of its process.
jbaumert said:
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
Click to expand...
Click to collapse
Yes, flash, not boot.
Thanks a bunch for all your help. I didn't meant to be lazy to start by reading sticked topics, but it's so much new information for a newbie that I didn't exactly know where to start. Thanks again for sharing the links.
I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Click to expand...
Click to collapse
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..
disacrol said:
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..
Click to expand...
Click to collapse
What version of super su are you using? Use 2.82 SR 3 or 5
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
What version of super su are you using? Use 2.82 SR 3 or 5
Click to expand...
Click to collapse
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.
disacrol said:
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.
Click to expand...
Click to collapse
3 or 5 work on Oreo. I'm not sure about stable. I don't use it.
Sent from my [device_name] using XDA-Developers Legacy app
SR5 worked like a charm. I just wish there was a compatibility matrix somewhere in their website to avoid so many forum threads and misinformation on the subject and avoid all the hustle. The whole process is dead simple but it took me days and tailored help from you guys to figure this one out.
Thanks again to all of you for your assistance.
i had that issue with a nex 6 and flashing supersu fixed it. when i got a 6p i tried the same and get stuck on the boot logo and had to sideload factory firmware to get back to go. i have a 5x on the way maybe i will try magisk.
so after i flash twrp reboot the bootloader, i open twrp and flash supersu sr5 and all is well, no more disappearing act for twrp and no more stuck on the "google"?
Please point me to the right thread if there is one.
Since upgraded to Android Pie and TWRP 3.23, my 5T got very slow boot mainly because it stuck at splash screen (the one has powered by android) for about 2min every boots/reboots. I tried restoring to stock recovery, it does boot normally.
This slow boot happens on all Pie updates including 9.0.5 with twrp 3.3.0. Any solution?
same here, waITING FOR SOLUTION
fitzpete said:
same here, waITING FOR SOLUTION
Click to expand...
Click to collapse
using Blue Spark 9.100 version no any kind of booting problem here.
Already using TWRP 3.3.0-x blu_spark v9.100, also try blu_spark r165-oos, still the same.
It will boots normally only with stock recovery.
semson said:
Already using TWRP 3.3.0-x blu_spark v9.100, also try blu_spark r165-oos, still the same.
It will boots normally only with stock recovery.
Click to expand...
Click to collapse
What about 'Magisk incl. modules'?
same here.
too slow to boot for both normal boot and recovery boot.
not sure if it a magisk related or not.
nicorvienne said:
What about 'Magisk incl. modules'?
Click to expand...
Click to collapse
I've two modules activated: magisk manager for recovery mode & oneplus 5t camera library fix (for gcam). complete removal of them doesnt help anything, still slow boot.
semson said:
I've two modules activated: magisk manager for recovery mode & oneplus 5t camera library fix (for gcam). complete removal of them doesnt help anything, still slow boot.
Click to expand...
Click to collapse
try - MagiskManager > uninstall > restore images > reboot TWRP > wipe cache > flash ROM > wipe > flash Magisk > reboot
Alright I tried it. after restored the image TWRP is gone, reboot and it is already stock recovery; booting is fine as it is stock recovery. Anyway I re-flashed OOS 9.0.5 with stock recovery, after 1st boot to system I installed TWRP via fastboot, booting slows down as it was,,, nothing's changed.
The only thing I didn't try to wiping data, I cannot afford losing everything and I don't' believe it matters as I have perfectly fine booting on stock recovery.
semson said:
Alright I tried it. after restored the image TWRP is gone, reboot and it is already stock recovery; booting is fine as it is stock recovery. Anyway I re-flashed OOS 9.0.5 with stock recovery, after 1st boot to system I installed TWRP via fastboot, booting slows down as it was,,, nothing's changed.
The only thing I didn't try to wiping data, I cannot afford losing everything and I don't' believe it matters as I have perfectly fine booting on stock recovery.
Click to expand...
Click to collapse
this behavior is existing with Magisk 18.1 as well with 19.1?
Yes same slow boot on magisk 18. I doubt if it is related, with twrp it boots slow already even magisk is not installed.
i have this issue too. running the latest codework twrp. not sure if this caused it to slow down because it wasn't this slow before the update.
I've always removed the 'compatibility.zip' from the OOS PIE ROMS, that way I was able to keep the Oreo version of TWRP installed;
twrp-3.2.3-x_blu_spark_v9.85_treble-op5_op5t.img
This is also nice, in case some people decide they don't like PIE and want to easily revert back.
I've never had any issues like this.
DoR3M3 said:
I've always removed the 'compatibility.zip' from the OOS PIE ROMS, that way I was able to keep the Oreo version of TWRP installed;
twrp-3.2.3-x_blu_spark_v9.85_treble-op5_op5t.img
This is also nice, in case some people decide they don't like PIE and want to easily revert back.
I've never had any issues like this.
Click to expand...
Click to collapse
I'll try to rollback to 3.2.3 version and see how it goes.
Thanks for the suggestion.
---------- Post added at 09:12 AM ---------- Previous post was at 08:30 AM ----------
Unfortunately.
Rollback to 3.2.3 with both version (codeworkx, blu_spark)
still slow to boot.
i have this issue too.
---------- Post added at 09:39 AM ---------- Previous post was at 09:36 AM ----------
aillez said:
I'll try to rollback to 3.2.3 version and see how it goes.
Thanks for the suggestion.
---------- Post added at 09:12 AM ---------- Previous post was at 08:30 AM ----------
Unfortunately.
Rollback to 3.2.3 with both version (codeworkx, blu_spark)
still slow to boot.
Click to expand...
Click to collapse
how is stiuation?
CanKartaL84 said:
i have this issue too.
---------- Post added at 09:39 AM ---------- Previous post was at 09:36 AM ----------
how is stiuation?
Click to expand...
Click to collapse
same as before. around 2 minutes to reboot.
If anyone still having this issue, I found it links to encryption of Dual Apps zone. "Format Data" from TWRP and this issue gone, do backup before proceeding and you will lose everything.
semson said:
If anyone still having this issue, I found it links to encryption of Dual Apps zone. "Format Data" from TWRP and this issue gone, do backup before proceeding and you will lose everything.
Click to expand...
Click to collapse
Do we have a new solution rather than formatting data now in year 2020?
I use stock recovery and official miui global rom in my phone along with magisk root. Everytime a new update comes i restore stock images from magisk, then apply the update, then again boot into twrp (just boot), flash the magisk and done. That way i maintain the stock recovery, OS, and root as well.
Yesterday i got the official Pie update from Xiaomi, i restored the stock images from magisk, updated to Pie. But now if i try to boot into twrp to flash magisk, it asks for decryption password. My phone is encrypted, from past one year twrp used to work completely fine after i entered the password (encrypted with lock screen pw) but now it says decryption failed. I have tried everything-
1. Removing the lock screen and encryption altogether.
2. Changing the encryption/lock screen pw to pattern/pin/password
But no luck, it says decryption failed. I'm unable to boot into twrp.
Also one weird thing, if i set pattern encryption pw, it asks for alphanumeric pw in twrp decryption screen. And vice versa. I've tried many twrp versions including the latest one. HELP!
Solved by using OrangeFox Recovery (OrangeFox-R9.0-2-whyred-MIUI-Pie.zip) from https://sourceforge.net/projects/orangefox/files/whyred/
Magisk works along with full encryption with lock screen password
Reboot took me to system reboot
avguser23 said:
Also updating twrp works same way
Click to expand...
Click to collapse
Reboot took me to system reboot and phone's stock recovery opened when I went to recovery mode
---------- Post added at 04:48 PM ---------- Previous post was at 04:26 PM ----------
akhu5 said:
Solved by using OrangeFox Recovery (OrangeFox-R9.0-2-whyred-MIUI-Pie.zip) from
Magisk works along with full encryption with lock screen password
Click to expand...
Click to collapse
Also, it would be really helpful, if you told me the steps and precaution to install orangefox, I am wishing to flash pixel experience and use Gcam. But I seem to be stuck in recovery flashing.
Binish Joshi said:
Reboot took me to system reboot and phone's stock recovery opened when I went to recovery mode
---------- Post added at 04:48 PM ---------- Previous post was at 04:26 PM ----------
Also, it would be really helpful, if you told me the steps and precaution to install orangefox, I am wishing to flash pixel experience and use Gcam. But I seem to be stuck in recovery flashing.
Click to expand...
Click to collapse
Cause orange didn't restart into recovery mode and booted into system.
akhu5 said:
Also one weird thing, if i set pattern encryption pw, it asks for alphanumeric pw in twrp decryption screen. And vice versa. I've tried many twrp versions including the latest one. HELP!
Click to expand...
Click to collapse
The dots translate into numbers in the following pattern:
1 2 3
4 5 6
7 8 9
Please note that this is what I read somewhere else when searching for my solution to the original problem (Can't decrypt Pie storage using password from Oreo).
arcanemachine said:
The dots translate into numbers in the following pattern:
1 2 3
4 5 6
7 8 9
Please note that this is what I read somewhere else when searching for my solution to the original problem (Can't decrypt Pie storage using password from Oreo).
Click to expand...
Click to collapse
This didn't work in my case, the only thing that worked was orangefox
Got problem with encryption in TWRP on brand new Mi Max 3 with Pie. I started with twrp-3.2.3-0-nitrogen, which ask about a pass after instalation. In this thread I found so OrangeFox Recovery should solve problem, but - this recovery is in .zip file to flash from recovery, which I did not have... In desperation I flashed twrp-3.3.1-0-nitrogen, and this
works!!
If it can, how? I'm having bootloop issues trying to do that. Thank you.
Bootloop in logo S9
RpRAUC said:
Bootloop in logo S9
Click to expand...
Click to collapse
follow up
Piereligio said:
If it can, how? I'm having bootloop issues trying to do that. Thank you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s9/how-to/one-ui-2-beta-rooting-installing-twrp-t4012961
https://forum.xda-developers.com/ga...rooting-installing-twrp-t4012961/post81084623
The patched kernel contained here was the solution for me
S9 ROOT
I did it.I flashed twrp format data and and installed SoldierR9312 mod. lock screen,samsung account and magisk root all work
http://www.renovate-ice.com/soldier9312/#stable_g96x-q
viktorvlahov11 said:
I did it.I flashed twrp format data and and installed SoldierR9312 mod. lock screen,samsung account and magisk root all work
http://www.renovate-ice.com/soldier9312/#stable_g96x-q
Click to expand...
Click to collapse
This worked great, thanks. Only issue I met was that I couldn't see the OEM unlock switch, so it didn't let me to flash TWRP from Odin (even though it was already unlocked), giving me "only official released binaries are allowed to be flashed(recovery)" error.
The solution for that was following these steps: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
EDIT: no wait, maybe it's bootlooping.
EDIT2: yes it is. I'm using italian carrier, you?
EDIT3: at the end I created a custom boot.img by using Magisk and I flashed it. In this way I kept encryption and stock recovery, but this doesn't give me write permissions in /system. But I do have root.
it stucks for me on the samsung logo
aidenpearce296 said:
it stucks for me on the samsung logo
Click to expand...
Click to collapse
Try flashing the twrp flashable firmware it may fix your problem
---------- Post added at 08:41 AM ---------- Previous post was at 08:37 AM ----------
viktorvlahov11 said:
Try flashing the twrp flashable firmware it may fix your problem
Click to expand...
Click to collapse
Piereligio said:
This worked great, thanks. Only issue I met was that I couldn't see the OEM unlock switch, so it didn't let me to flash TWRP from Odin (even though it was already unlocked), giving me "only official released binaries are allowed to be flashed(recovery)" error.
The solution for that was following these steps: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
EDIT: no wait, maybe it's bootlooping.
EDIT2: yes it is. I'm using italian carrier, you?
EDIT3: at the end I created a custom boot.img by using Magisk and I flashed it. In this way I kept encryption and stock recovery, but this doesn't give me write permissions in /system. But I do have root.
Click to expand...
Click to collapse
I got it to work on a Bulgarian unlocked model
Maybe try flashing the twrp flashable firmware after the mod
omg it was so easy!
after you flashed twrp and formated data you just have to flash magisk and that's it
viktorvlahov11 said:
omg it was so easy!
after you flashed twrp and formated data you just have to flash magisk and that's it
Click to expand...
Click to collapse
I done that, but still stuck on SAMSUNG logo, no boot loop or what. I was waiting 10min, nothing happened.
Any advice?
Hi there,
after having tried different methods to root my S9, which has updated to Android 10 One UI 2.0 this morning, maybe the solution that finally worked for me will help you too.
First I tried to root just like in Pie, as found on the net: flashed TWRP 3.2.3 via Odin, then flashed Magisk with TWRP plus this no-verity-opt-encrypt. Got stuck in bootloop, tried different no-verity/dm-verity versions, Magisk 18.x and Magisk 20.1. Nothing worked, got stuck again every time i rebootet the system again.
Then, after realising that I CANT get back to Android 9 (old rom wasnt Odin flashable anymore, phone didnt boot, BSoD), I first downloaded the new stock rom and bootloader as zip, got it from here:
https://forum.xda-developers.com/showpost.php?p=81615561&postcount=1830.
You have to check if that fits with your version / phone. Once downloaded, I copied both onto my SD card. So now I was able to install at least the new clean stock rom. Oh, and now I used the TWRP version 3.3.1.
Then I found this:
https://forum.xda-developers.com/galaxy-s9/development/root-s9plus-exynos-android10-t4065343
At first I tried to root without the SoLdieR9312's mod, only with MAGISK 20.3 and no-verity. Stuck again, it only bootet to download mode, nothing else. So flashed again the clean stock rom, and after first not keeping the right order (I suppose) I finally followed EXACTLY the instructions 1 - 4 in above manual including SoLdieR9312's mod (I highly recommend first a complete Wipe, format data, and then flash the clean new Rom with Android 10 and bootloader from above link).
Now, to save you the time I spent today: once your phone is bootet (and succesfully rooted via Magisk 20.3, which will happen automatically due to the SoLdieR9312's mod), DONT LET MAGISK UPDATE TO VERSION 20.4!!!! Magisk Manager asks you to update, but when I did update to 20.4, everything fell apart again, it only bootet to download mode.
Now I seem to have it stable and running with 20.3 and the [email protected]. I rebootet 5 times so far just for the sake of it, and it works fine and rootet.
If I can be of further help, please let me know. I spent the last 12 hours on this matter, so dont hesitate.
Greetz from me minus a bunch of nerves
PS: After I wrote the above, I deleted the Knox family in the rootet system, and then it collapsed again and, after BSoD, it only rebootet into download mode. I can not exclude the possibility, that this might have been the reason for some system breakdowns before, as I had to re-do the wipe-clean-install-then-root-then-customize worksteps aroung 8 times yesterday before it was stable as it is now. Now I´ll leave Knox on it, though that itches me a bit. But I´m exhausted for now
PPS: IMPORTANT when I try to create a PIN or a pattern for the lock screen, phone reboots to SIM card PIN screen and then keeps rebooting and rebooting. It looks like there are some interferences with root and PIN / security. I did NOT create a Samsung account, only a google one, cause in the beginning i suspected it might have been a Sam acct problem (I constantly couldnt log into it on the phone). Turns out that might not have been the case, rather a prob between root and setting a lock screen security.