Database Develop

Oneplus 3T stuck in boot animation after root attempt

I have a stock Oneplus 3T, updated to 4.1.3. I wanted root access to allow Cerberus more control.
So I followed the Oneplus 3T root guide by "Theunlockr" .com
I downloaded:
TWRP v3.1.0-1-oneplus3t.img
SuperSU v2.78 SR5
No-Verity opt encript v5.1​
I followed the instructions as closely as I could, I installed the TWRP and cleared the phone (that booted normally),
Then I went to flash SuperSU and No-Verify, cleared the cache, restarted and my phone, and It didn't boot, the red dot logo animation would just play on a loop, I left it for an hour because it did warn me that it would take a while.
When I was satisfied that it wasn't going to start, I restarted it a couple of time, no-dice.
I also tried flashing a more up-to-date SuperSU. (v2.79), still didn't work.
So, now I've gotten myself further stuck, I flashed the stock recovery back onto the phone and decided i wanted to flash the Open Beta 5 OS.
But now when I go into recovery (stock), I can't connect to ADB properly.
I click " Install from ADB " - I've been using this, but it only seems to allow Sideload, but If I try to sideload it, it tells me it can't read the ROM.
So I changed ADB versions to the ones from mfastbootv2.
and now it says "error: protocol fault (no status)",
I can't use the push command because it just says "Error: closed"
So I'm kinda stuck for what I can do from this point forward to get my phone working again...
Android Debug Bridge version 1.0.31
Any suggestions?
Thanks for your time
Evan

There's so many different builds of SuperSU that it's getting hard to keep track of which one works. I know that flashing an older version does tend to cause endless boot animation. SuperSU 2.79 should work, though you'll likely need to dirty flash OOS again before flashing it.
I've also found ADB to be rather finicky in recovery. My advice is to use an USB OTG adapter and load any files that you need on a flash drive. Afterwards, follow these steps:
1) Boot into fastboot and flash TWRP again using your PC and fastboot commands
2) Download whatever version of OOS you want (stable or open beta) and somehow load it onto your phone, whether through ADB or USB OTG
3) Boot into TWRP and flash the OS that you've downloaded, wipe cache/Dalvik. You can clean flash if you want, though dirty flashing should suffice in this situation.
4) Flash either SuperSU v2.79, or Magisk v12.0. Both Magisk and SuperSU will root your phone, I just prefer Magisk due to its extra capabilities and more straight-forward development.
5) Reboot, the rebooting process shouldn't take more than a few minutes.
Using a flash drive also has other benefits, you can save nandroids directly onto it through TWRP. This both saves space in internal storage and keeps the backups safe in the event that your phone gets inadvertently wiped from any unforeseen incidents.
Additional notes:
-You don't need to flash the no-verity.zip if you flash either SuperSU or Magisk, both of them contains the necessary scripts

Fantastic!
Thanks a ton, that solved my issues completely.

TWRP stuck in splash screen.

Hi everyone, when I install the TWRP using the flashable zip installer and then boot into TWRP it gets stuck in the TWRP logo and when I flash from fastboot it works fine, but I need to install it from flashable zip because I TWRP the I have to start with the partition slot A that also has the custom rom, I can't always change slot partitions every time I have to do operations with the TWRP.

I would also like to note that using the twrp-installer-jasmine_sprout-3.2.3.zip results in the recovery mode sitting on the TWRP logo even if it was a successful install.
I'm hoping someone can find a fix to this soon.

XRed_CubeX said:
Hi everyone, when I install the TWRP using the flashable zip installer and then boot into TWRP it gets stuck in the TWRP logo and when I flash from fastboot it works fine, but I need to install it from flashable zip because I TWRP the I have to start with the partition slot A that also has the custom rom, I can't always change slot partitions every time I have to do operations with the TWRP.
Click to expand...
Click to collapse
Do you flash the rom before the twrp zip?

I found a workaround instead of using the zip package.
1. Get the current partition you are using:
Code:
fastboot getvar current-slot
2. Choose which partition you want to install to( in this case I'm using B, but you can use A if you like ) and flash the latest TWRP IMG file:
Code:
fastboot flash boot_b twrp-3.2.3-0-jasmine_sprout.img
3. Set the current partition to the one you just flashed:
Code:
fastboot set_active b

Yes but then to go to TWRP to do something I can't always use a PC and from fastboot change slots. I took so long to install Magisk.

I had to dump the boot partition, modify it with magisk manager and flash it with the TWRP, it doesn't seem like anything to dump but to me it was difficult because I don't have root at the beginning.

If I flash the TWRP in the boot partition in the resurrection remix slot, I lose the chance to start the custon rom

Fixed, after the 3000th time I flashed, then the TWRP starts up, I don't know how not to ask me why but now I try to hypothesize 2 solutions:
1) We have to stay for a while with the custom rom, then later when you will try to flash the zip, the TWRP will start.
2) You need to have both Magisk and TWRP installed in the boot in order to start the TWRP flashed from zip without problems.
These solutions do not know if they are like this or I am confusing myself, so it happened to me.
If in doubt, hoping for an update does not hurt, maybe the TWRP will start immediately with no problems in the future.

Help flashing custom firmware

Hi, fellows,
High need urgently help!
I was on stock Pie with all critical unlock, bootloader unlock and root too ... So I decide to change to a costume firmware.
Now I'm on twrp-installer-3.3.0-0-jasmine_sprout.zip with all the partitions decrypted and when I tried to flash a custom firmware like Havoc OS v2.4 or Pixel Experience ... Happen this error.
Step 1/2
Error applying update: 7 (ErrorCode:: kInstallDeviceOpenError)
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Havoc-OS-v2.4-20190502-jasmine_sprout-Official.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
Anyone can help me?
Thanks

nnexuss said:
Hi, fellows,
High need urgently help!
I was on stock Pie with all critical unlock, bootloader unlock and root too ... So I decide to change to a costume firmware.
Now I'm on twrp-installer-3.3.0-0-jasmine_sprout.zip with all the partitions decrypted and when I tried to flash a custom firmware like Havoc OS v2.4 or Pixel Experience ... Happen this error.
Anyone can help me?
Thanks
Click to expand...
Click to collapse
Try to use twrp 3.2.3 and follow this guide:
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375

mma_1494 said:
Try to use twrp 3.2.3 and follow this guide:
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Click to expand...
Click to collapse
I already tried this version but not the guide...
I'll try when I arrived at home

nnexuss said:
Hi, fellows,
High need urgently help!
I was on stock Pie with all critical unlock, bootloader unlock and root too ... So I decide to change to a costume firmware.
Now I'm on twrp-installer-3.3.0-0-jasmine_sprout.zip with all the partitions decrypted and when I tried to flash a custom firmware like Havoc OS v2.4 or Pixel Experience ... Happen this error.
Anyone can help me?
Thanks
Click to expand...
Click to collapse
Their is only one way to recover your phone just follow this step
1. Flash stock firmware(stock rom) vie fastboot using MI Flasher
this is bring back you phone and if you want to install custom rom then follow this
1. boot twrp
2. wipe all the data from slot A and B partition(internal storage as per you choice )
3. boot to slot B and copy past the custom rom file in slot B
4. flash that rom and boot to slot B and then flash Gaaps and other staff you want
5. reboot and enjoy.
NOTE: changing the slot require reboot twrp in simple words every time you change the slot you have to reboot the phone and boot again to twrp..
i hope this will work for you..:good:
If you don't have stock flash file then try from step 2. see whether it will work or not otherwise follow from beginning.

facing the same issue
i tried the same and getting the same error. even the twrp3.2.3.0 never worked while tried to flash that one more than 20 times, after flashing 3.2.3.0 my phone either boots normally or it gets completely power off. and if i try to boot into recovery using volume keys and power key , it boots in stock recovery. please help

Mine its ok now... i don´t know whats happen but suddenly it flash withou any problem.
See if it helps...
Make sure you're running a proper working Recovery
Flashing instructions:
Dirty flash (assuming you have rom on slot A):
1. Download all required files and place them to internal memory (ROM, twrp installer, gapps, magisk, ..)
2. Boot twrp to slot B and flash ROM and twrp installer
3. Reboot twrp to slot A and flash gapps (optional magisk)
4. Now reboot to system
Clean flash (assuming you have rom on slot A):
1. Download all required files and place them to internal memory (ROM, twrp installer, gapps, magisk, ..)
2. Boot twrp to A slot and wipe everything except for internal
3. Reboot twrp to B slot and flash ROM and twrp installer
4. Reboot twrp to slot A and flash gapps (optional magisk)
5. Now reboot to system
If you are coming from stock:
1. Download latest TWRP installer and image
2. Open cmd and type fastboot boot twrp.img (change twrp to its actual name)
3. You should be on slot A in twrp, if not change it and reboot to bootloader and repeat step 2.
4. Format data
5. Now follow instruction for clean flash
Click to expand...
Click to collapse
Credits: Fullbustah

I have this issue and none of the steps worked.
I got my device 2 days back and it was in Oreo. I tried to update to pie but the update keep failing. I unlocked the phone and flash latest official fastboot rom using mi_flash and installed magisk using this guide:
https://forum.xda-developers.com/mi-a2/how-to/unlock-bootloader-n-root-magisk-easy-t3856800
Everything went smooth.
Today I tried to go further and instal PE rom using this guide:
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Everything goes smooth until I boot to TWRP and try to flash the rom. It gave the error posted by OP. I have tried the following things since:
1. Try another two roms, same issue
2. Flash stock Pie using mi_flash then temp boot to TWRP latest version from 'a' partition, wipe everything, then boot from 'b' partition, wipe everything, try to flash. Same issue.
3. Install TWRP (it installed without any issue), reboot to installed TWRP, flash rom, same issue.
4. Try to flash with 'a' as active. Same issue.
5. All other possible combos (i think) of the above. In all cases everything goes as expected until I try to flash the rom.
Currently I have flashed the factory image back. Any help will be greatly appreciated.

OFP file needed urgently for CN version

DOES ANYONE HAVE THE OFP file for chinese rom?
Here is my situation:
1. changed recovery to orangefox successfully through bootloader
2. rooted with magisk 20.3 successfully
3. tried to install viper4android root version did not work as went in to bootloop. uninstalled and back to normal.
4. tried to install viper4android non root version through orange fox recovery. Phone now keeps loading into bootloader
5. used uninstaller.zip to uninstall non root viper driver, still i keep going back to bootloader. however i am still able to boot into recovery.
6. device undetectable in bootloader mode and cannot execute adb commands anymore.
Pls. help if any solution without formatting data etc and resetting the phone as I do not want to do manual backup and restore. However if that is the only solution, then no choice but would like to see if can be sorted without this.
Edit: Someone else under Paranoid Rom was having same issue and they fixed by flashing Vendor. I did the same now i am stuck at yellow realme logo.
Edit: couldnt find a way to reboot into the original ROM so had to install from beginning at least was able to backup due to OrangeFox recovery.

naveed5700 said:
DOES ANYONE HAVE THE OFP file for chinese rom?
Here is my situation:
1. changed recovery to orangefox successfully through bootloader
2. rooted with magisk 20.3 successfully
3. tried to install viper4android root version did not work as went in to bootloop. uninstalled and back to normal.
4. tried to install viper4android non root version through orange fox recovery. Phone now keeps loading into bootloader
5. used uninstaller.zip to uninstall non root viper driver, still i keep going back to bootloader. however i am still able to boot into recovery.
6. device undetectable in bootloader mode and cannot execute adb commands anymore.
Pls. help if any solution without formatting data etc and resetting the phone as I do not want to do manual backup and restore. However if that is the only solution, then no choice but would like to see if can be sorted without this.
Edit: Someone else under Paranoid Rom was having same issue and they fixed by flashing Vendor. I did the same now i am stuck at yellow realme logo.
Edit: couldnt find a way to reboot into the original ROM so had to install from beginning at least was able to backup due to OrangeFox recovery.
Click to expand...
Click to collapse
I need that file too. Can anyone help me to have this?

Rooting Moto G6 with PPS29-118-15-11. What versions of noverity, twrp, magisk to use?

Hello forum, I have been trying to root my motorola G6..
After much struggle, getting stuck in a boot loop and other issues I finally have restored stock roms and now have build PPS29-118-15-11 installed. So at least the phone works again My bootloader is unlocked.
But I still want to root it.
I think I understand the procedure well enough, but I am unsure of the correct/best versions I need for the ROMS/boot, Magisk, and TWRP.
ROMS/boot:
I found a youtube with instructions for updating Android v9
But I haven't tried it as this recommends a boot img:
OPS27.104-15-10_no-verity_boot.img
OPS27.104-15-10_no-verity_boot.img | by dejello for Moto G6
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I am reluctant to use the above as it looks to be a downgrade from my current version 29-118-15-11.
Also, I thought that the filename prefix "O" indicated oreo instead of "P" for pie? So would this be a version 8 file?
TWRP:
Similarly, I am not sure if I am using the right, or best TWRP version. I currently have twrp-v3.2.3-ali.img
I flash this (with fastboot) and it works but shortly after I encounter the "no command" error (when booting to recovery) and I have to redo it. I am NOT overwriting it with a stock recovery.img.
I have also run into the "encryption password" problem, where I am unable to provide one to decrypt the data partition. So I can't backup the data with twrp (something I really would like to do).
Magisk
I have Magisk-23-0.zip
But I saw a post from brunogroa that recommends installing Magisk 19 and updating it to 23 later. Is this something that is required or can I just install v23?
So, I am looking for the correct versions for ROM, Magisk and TWRP to use, given that I have installed PPS29-118-15-11
Any assistance will be greatly appreciated.

Well I finally have it I think. I noticed a comment in
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide. by djello
"(you may not need a modified boot image for Magisk)"
When using PIE instead of OREO.
Being an optimist, I gave it a try and it worked... I installed Magisk and was able to verify root access using the Root Checker Basic App. Kept stock boot img.
This is probably not too amazing for the old hands but us newbies need a break every now and them
So in the end, all I had to do was:
(0) Unlock bootloader
(1) Install stock PPS29-118-15-11
Done earlier with another version of twrp.
Install TWRP 3.5.2
(2) fastboot flash recovery twrp-3.5.2_9-0-ali.img
(3) Use twrp to install Magisk
adb push Magisk-v23-0.zip /tmp
Boot phone into recovery and use twrp to install Magisk
(4) Boot the phone into System and verify Magisk is there and use Root Checker App to confirm I am now rooted.
Issues:
I noticed that a security update for
PPS29-118-15-11-5 failed to apply.
The phone boots into recovery mode and asks for the decrypt password. I don't know the password to decrypt data and how to proceed from here.
I suspect that if I flash the stock recovery img the security update might work. If anyone knows please comment ; I will research this also and maybe just try it.

pdpantages said:
Well I finally have it I think. I noticed a comment in
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide. by djello
"(you may not need a modified boot image for Magisk)"
When using PIE instead of OREO.
Being an optimist, I gave it a try and it worked... I installed Magisk and was able to verify root access using the Root Checker Basic App. Kept stock boot img.
This is probably not too amazing for the old hands but us newbies need a break every now and them
So in the end, all I had to do was:
(0) Unlock bootloader
(1) Install stock PPS29-118-15-11
Done earlier with another version of twrp.
Install TWRP 3.5.2
(2) fastboot flash recovery twrp-3.5.2_9-0-ali.img
(3) Use twrp to install Magisk
adb push Magisk-v23-0.zip /tmp
Boot phone into recovery and use twrp to install Magisk
(4) Boot the phone into System and verify Magisk is there and use Root Checker App to confirm I am now rooted.
Issues:
I noticed that a security update for
PPS29-118-15-11-5 failed to apply.
The phone boots into recovery mode and asks for the decrypt password. I don't know the password to decrypt data and how to proceed from here.
I suspect that if I flash the stock recovery img the security update might work. If anyone knows please comment ; I will research this also and maybe just try it.
Click to expand...
Click to collapse
I am stuck in a similar position.

SOLVED IT!!! Followed all of the steps that you posted except I installed Magisk with the patch method because I couldn't get the zip file to push onto the device. Kept getting a read only error, maybe because it wasn't rooted?
Anyway, I am rooted now!!!