Develop Bugs

SuperSU won't install through TWRP

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...

Slot A doesnt work?

my phone still works on slot B but Slot A just reboots straight to twrp and ive tried to factory reset it to factory and fastbooting the boot.img again

Veid71 said:
my phone still works on slot B but Slot A just reboots straight to twrp and ive tried to factory reset it to factory and fastbooting the boot.img again
Click to expand...
Click to collapse
Unless your setup to dual boot you can only boot your active slot

mac796 said:
Unless your setup to dual boot you can only boot your active slot
Click to expand...
Click to collapse
is there a way to change the active slot? i was trying to install magisk and trying to fix slot A and now slot B wont start up. so now neither of them will turn on, Slot A just bootloops and slot B just turns to twrp now

Known problem with magisk. Just use su, but use old sr3. New beta is killing twrp

I would honestly do a flash-all.bat of the latest factory image separately to both slots a & b to clear any risidual problems that might currently exist and then start over with whatever flashing you want to do from there. I'm assuming you know you need to use the unofficial build of Magisk on the Pixel because the official version does not work. Unofficial Magisk apparently has its own dedicated thread now but used to be hosted in the Paranoid Android rom thread. You could probably go to either place to find out what the latest version of Unofficial Magisk is that is stable and people are using without problems. If you want to pass Safety Net with root you can't do it with SU. If that doesn't matter you can use SU like the previous poster suggested but people are using Unofficial Magisk on the Pixel without issues --you just need to use the right version and the version of Magisk Manager that is compatible with it.

Yep did the same.
Flashall.bat on active slot.
Then set the other one as active via fastboot
Than flashall.bat again
Was the only help for me.

mikaole said:
Yep did the same.
Flashall.bat on active slot.
Then set the other one as active via fastboot
Than flashall.bat again
Was the only help for me.
Click to expand...
Click to collapse
Yeah I figured out the issue was that I did a factory reset but I didn't reflash the ROM so I guess it didn't know what to boot into? But as soon as I flashed the ROM it worked also where can I get sr3? I've looked on the su thread but it doesn't have a link for it for some reason

December update breaks magisk?

Hi all,
I've updated my 3xl to the december update like usual, flash-all.bat without -w. Afterwards, it boots fine, and in settings it clearly states that I'm running the December security patch.
However, when I boot into twrp (not installed) and flash magisk, android boots to just before asking my SIM PIN, says "Shutting Down", then reboots and gives me the message "Can't load Android System. Your data may be corrupt." etc. inside stock recovery.
Did the December update somehow break magisk? Anyone gotten it to work? I'd rather not do a factory reset if it's not needed.

Works fine for me.

Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions

Working fine for me as well.

I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app

You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.

mikepopo99 said:
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Click to expand...
Click to collapse
jd1639 said:
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
TonikJDK said:
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
Click to expand...
Click to collapse
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?

RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Flash the stock boot.img to both slots.
Reboot and check it.
Copy the Magisk zip to your phone.
Fastboot boot the TWRP img file, don't install it.
Use TWRP to install the Magisk zip, and you are done.

RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.

sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!

RogerXIII said:
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
Click to expand...
Click to collapse
Good deal. That is why I always keep a copy of the Magisk uninstaller on the phone itself. As long as I can get to BL/temp TWRP .img, the worst I am out is the time it takes me to reconfigure Magisk.

RogerXIII said:
However, when I boot into twrp (not installed)
Click to expand...
Click to collapse
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1

Shaftamle said:
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Click to expand...
Click to collapse
The TWRP image from the official website, and then simply fastboot boot twrp.img

RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
Ok cool. Wasn't sure if there was an app like fashify or something.
Fire Hound 8.1

sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
you are godsend my friend.

Touz604 said:
you are godsend my friend.
Click to expand...
Click to collapse
Glad you got it figured out.

RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".

bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
You ca't yet.

bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
Thread is from 2018

I am gonna check the official TWRP website for the workable TWRP for my Pixel 3 till I see your post
wangdaning said:
Thread is from 2018
Click to expand...
Click to collapse

custom roms do not boot up

hi there,
i used crDroidAndroid-8.1-20180606-riva-v4.3 but there were color problems i didnt know 2 fix so i decided 2 flash a new rom resp. a newer version but no custom rom boots up.
when it tries 2 boot is freezes at the boot screen, then screen switches off and nothing happens. i can go 2 fastboot and recovery.
sometimes it boots up but after a few seconds it freezes 2.
i tried different roms and recoveries but nothing works.
i foolishly wiped internal storage once but then i flashed the stock rom again which boots up. then i unlocked the bootloader and flashed a custom recovery and a rom again but the same error is there (no booting up)
anyone got a solution for this problem? no unbricking suggestions plz
edit: im in the wrong thread i think. i wanted 2 post it in "Guides, News, & Discussion". cant delete it. sry for that

logs
so i managed 2 create logs while booting up.
1) https://pastebin.com/cgrX2DA1
2) https://pastebin.com/r7DmcN46
3) https://pastebin.com/0pwXyuys
4) https://pastebin.com/S41FG2SQ
1) is 1st part of the log while booting with no success to boot into the os.
2) is 2nd part of the log while booting with no success to boot into the os.
3) is 1st part of the log while booting with successful boot into the os.
4) is 2nd part of the log while booting with successful boot into the os.
i also tried 2 log "cat /proc/last_kmsg > /sdcard/last_kernel_message_log.txt"
and "dmesg > /sdcard/kernel_boot_log.txt" via terminal in linux but it only sais file or directory not found.
i hope sum1 can give me sum help now.

so i did this https://en.miui.com/thread-3921604-1-1.html but it doesnt help. as i expected.
any1? i can post more information if necessary. just say which and perhaps how ;D

cmon guys. i can impossibly b the only 1 who faces this problem.
i dont think its a hardware thing cause stock rom and android 7.1.2 (viper os) work. maybe a vendor problem? could flash another vendor img solve this problem? can sum1 send me his?
i got sum more logs after flashing rr 7.0:
logcat 1st part: https://pastebin.com/EBZAgbhF
logcat 2nd part: https://pastebin.com/qaMFrvxi
dmesg: https://pastebin.com/Gg8bYkJy
cheers

Fastboot flash latest miui 10 stable using mi flash tool and use the rom after setting up. Then flash custom recovery and do a full wipe.
This works for most cases.

NaAnBcEhEuL9A8K7 said:
Fastboot flash latest miui 10 stable using mi flash tool and use the rom after setting up. Then flash custom recovery and do a full wipe.
This works for most cases.
Click to expand...
Click to collapse
thx for ur answer but i tried this already. does not work on android 8 and 9 roms

daemonicvs said:
thx for ur answer but i tried this already. does not work on android 8 and 9 roms
Click to expand...
Click to collapse
Well it worked for me.
Which custom rom you want to use?

well, it doesnt matter 2 me. the main thing is that it works =D rr, aex, crdroid..

daemonicvs said:
well, it doesnt matter 2 me. the main thing is that it works =D rr, aex, crdroid..
Click to expand...
Click to collapse
Crdroid is my choice because aex and rr are very early builds. I like pixel experience but the devs not updating it so crdroid or havoc os.
Like i said use Xiaomi flash tool and flash miui 10 stable via fastboot method(there are 3 options in the bottom select flash all instead of flash and lock to avoid unlocking the bootloader again), don't flash anything else, setup and use the phone, flash recovery wipe all and format, install rom, don't flash gapps yet, boot into rom and see if its fixed.
Use vendor based recovery, if using batik recovery you have to flash batik recovery again after format.
This is my solution.

NaAnBcEhEuL9A8K7 said:
Crdroid is my choice because aex and rr are very early builds. I like pixel experience but the devs not updating it so crdroid or havoc os.
Like i said use Xiaomi flash tool and flash miui 10 stable via fastboot method(there are 3 options in the bottom select flash all instead of flash and lock to avoid unlocking the bootloader again), don't flash anything else, setup and use the phone, flash recovery wipe all and format, install rom, don't flash gapps yet, boot into rom and see if its fixed.
Use vendor based recovery, if using batik recovery you have to flash batik recovery again after format.
This is my solution.
Click to expand...
Click to collapse
i did it several times before but 2 b safe i did it again like that:
i flashed riva_global_images_V10.1.1.0.NCKMIFI_20181029.0000.00_7.1_global_f444c158ed.tgz using XIAOMI-TOOL-MiFlash-for-Linux-by-IceMan-master. im on linux mint 18.3. i have 4 options:
flash_all_lock.sh
flash_all_lock_crc.sh
flash_all_except_data_storage.sh
flash_all.sh
i chose flash_all.sh
i booted into the stock rom and set it up, enabled dev options and adb.
then i switched it off, went into bootloader, flashed twrp-3.2.3-0-riva.img via fastboot.
after that i entered twrp, flashed OrangeFox-R8.3-riva.zip and rebooted into recovery
i wiped everything except external sd and usb otg (i dont have these)
after a reboot intorecovery i formatted data then rebooted in recovery
i flahed crDroidAndroid-9.0-20181002-riva-v5.0.zip
then reboot into system
no success as i expected! wtf is wrong wtf. this cant b true!
but thank u very much for ur efforts! perhaps i would try 2 restore a vendor img from sum1 which rom does work. i know its a great demand but could u send me urs? ;D i dont know if there r sum personal info..
best regards

Don't give up there might be a solution.
Pray to God for some help.
:good:
---------- Post added at 01:23 PM ---------- Previous post was at 12:59 PM ----------
Currently I am using Xiaomi.eu beta rom. You can check their website for all the features. Its smooth, stable and can update without needing to got the recovery:victory:
This should work for you because unlike other roms this is based on miui for riva. That means you will get updates till Xiaomi ditches support for riva.
I recommend you use this rom over the global rom until you fix the problem with your phone.
Some things missing:
Choice of region is limited( India is not available)
There is no custom kernel available for miui oreo as of now.
Magisk safetynet not passed
If you're going flash this rom you need to be on latest global beta fastboot rom and need a recovery that supports oreo base.
I use batik recovery base oreo.

yes. i cant b the only 1 facing this problem...!? really. i cant!
thx anyway

daemonicvs said:
yes. i cant b the only 1 facing this problem...!? really. i cant!
thx anyway
Click to expand...
Click to collapse
Maybe you can be the only one facing this problem.
Try joing telegram community maybe your problem will get fixed from there.

NaAnBcEhEuL9A8K7 said:
Maybe you can be the only one facing this problem.
Try joing telegram community maybe your problem will get fixed from there.
Click to expand...
Click to collapse
theres no difference between my device and yours... everybody must have this problem ;/

daemonicvs said:
theres no difference between my device and yours... everybody must have this problem ;/
Click to expand...
Click to collapse
Did you try edl method?

NaAnBcEhEuL9A8K7 said:
Did you try edl method?
Click to expand...
Click to collapse
yes. i could flash the stock rom this way but the problem is not solved this way

daemonicvs said:
yes. i could flash the stock rom this way but the problem is not solved this way
Click to expand...
Click to collapse
At least you have to try.

I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.

Eddyb299 said:
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Click to expand...
Click to collapse
Did you flash lazy flasher?

Eddyb299 said:
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Click to expand...
Click to collapse
dont u have 2 wait 2 weeks or so till bootloader is unlocked?
what exactly do u mean with won't boot up? bootloop? or stuck at boot logo?
after flashing a custom recovery, did u boot directly into the system or did u try 2 boot into recovery? sometimes the stock recovery overwrites the custom 1 when stock rom boots up
my problem is solved. i remembered that i made a full nandroid backup with twrp before i flashed a new rom and the problem appeared. so i restored everything i backed up with twrp (incl cust) and voila, rom booted up. and i can wipe system and data and flash every rom i wanna and it still boots up \o/
i really could have tried it earlier but i didnt think of this untill yesterday ;D
well, thx for ur efforts anyway buddy @NaAnBcEhEuL9A8K7
cheers

slow boot on Android Pie with twrp

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?