I went back to ZUI to do a super clean install of AEX 6.6. I hence had to unlock the bootloader and flash TWRP before I could flash AEX. Things went fine, everything works. However, when I try to boot into recovery, I end up in what I can only guess to be a ZUI recovery.
I am 100% sure that I had TWRP on the device because that is how I installed AEX.
I just booted instead of installing it, my fault.
Related
Today I have faced a strange situation, I installed TWRP (after unlocking the bootloader) on my OP3 as soon as I received the device then I flashed custom ROM by @Grarak http://forum.xda-developers.com/oneplus-3/development/rom-unofficial-cyanogenmod-13-t3399089.
After using for some days I decided to give Oxygen OS another try, so I wiped the cache,data,system and Flashed full OTA provided by @namanbhalla https://forums.oneplus.net/threads/...ficial-oxygen-os-roms-and-ota-updates.450783/
Every thing went smooth but after starting up I wasn't able to goto twrp, for some strange reason twrp was automatically replaced with stock recovery. OK, I decided to reflash twrp, but bang! after so many flashing I wasn't able to boot into twrp, still there was stock recovery.
Solution:
1) fastboot oem unlock (re run even if it says already unlocked)
2) fastboot flash recovery twrp-3.0.2-0-oneplus3.img
now TWRP is installed.
I not Android Developer and cant guarantee above will work and wont harm your device. Try at your own risk.
that is all not needed, i have had this happen to me multiple times reflashing Stock and Stock recovery replaces TWRP, all u have to do is boot up to fastboot mode and flash TWRP, do not reboot, use Power + Vol + and when the Unlocked bootloader screen comes up press the VOL key and click recovery and TWRP is back. no need to do the unlock bootloader again, unless u unchecked it, just make sure it is checked when flashing the Stock rom again or u can just use flashify if u rooted stock before the recovery got replaced somehow, i have even had this happen on FreedomOS 3.2.1
... with respects to recovery and flashing. Just picked up this one about 2 hours ago. I used the unified tool kit, am rooted and running RR... But I can only boot into CM recovery. Any attempts to flash (using toolkit to boot to TWRP) SuperSU, or ARISE, or whatever, don't do anything.
What's the trick
Well usually you got to flash the rom, flash twrp. Then reboot back to twrp, for flashing extra packages. Usually after ROM + TWRP, I like booting into OS and setting things up and then going to twrp to flash root.
But your problem is very simple to solve. Just flash twrp recovery from bootloader using "fastboot boot ' twrp image name ' ". Then reflash the rom and twrp. Then boot into the os. Then go back into twrp to root and flash arise sounds or what not. I am running RR with no issues and arise sounds is working no issues.
Thank you. I'm booting into TWRP now just fine, but flashing SuperSU and ARISE don't work,.. Or at least, the apps don't show up as they should
edit: update
used the supersu SR3 version and now everything is normal
cheers
I wiped the phone clean and tried to flash the new version of AEX But, it showed Error 7.
Tried looking for fix for Error 7 on internet, it didn't work for AEX5.6, 5.5, 5.4.
5.3 installs normally.
But felt like needed something new.
Went on the forums to find Xtended ROM. Flashed it.
After flashing it tried flashing Nano GAPPS.. Didn't work.
Tried to system reboot and thought I can later work it out.
ROM is all fine... But, later when I got to recovery mode.
(Problem begins)
I realised I lost TWRP.
And the recovery that's there wouldn't allow me to flash anything.
It looks more like CWM recovery but with less options.
It doesn't even have a advanced wipe!
Now I'm stuck with a non rooted phone, without Google bare minimum functionalities.
Am I alone? Help me out!
UKWZ7 said:
I wiped the phone clean and tried to flash the new version of AEX But, it showed Error 7.
Tried looking for fix for Error 7 on internet, it didn't work for AEX5.6, 5.5, 5.4.
5.3 installs normally.
But felt like needed something new.
Went on the forums to find Xtended ROM. Flashed it.
After flashing it tried flashing Nano GAPPS.. Didn't work.
Tried to system reboot and thought I can later work it out.
ROM is all fine... But, later when I got to recovery mode.
(Problem begins)
I realised I lost TWRP.
And the recovery that's there wouldn't allow me to flash anything.
It looks more like CWM recovery but with less options.
It doesn't even have a advanced wipe!
Now I'm stuck with a non rooted phone, without Google bare minimum functionalities.
Am I alone? Help me out!
Click to expand...
Click to collapse
For aex issue did you flash factory2vendor zip before flashing rom?
You will have to install twrp image using PC. Like the first time you did when you were unlocking bootloader
Flash zui using qfil or miflash.
If bootloader is unlocked still. You can directly flash twrp.
If not first unlock your bootloader and then flash twrp.
For treble rom like aex5.5 you need to flash factory2vendor.zip and then flash twrp with treble support.
For info on flashing and link visit aex5.5 rom page.
Hey everyone. Tried to flash a custom ROM for the first (and maybe last time) on the Mi5s from China Stable V10.2 to Lineage OS16. I think i did everything correctly at first
Unlocked the bootloader with Mi Unlock, put the SDK tools into ADB folder, flashed TWRP with command prompt, made a backup, wiped data, disabled force encryption, MAGISK root, flashed Mi5s firmware (although I could only find Oreo), LOS16 (Pie), and OpenGApps
I did all of that and got stuck on the LOS boot animation. Then I wiped data + cache partitions and tried again (didn't work). I quit trying with LOS but instead tried to flash the MIUI Global Stable recovery ROM with TWRP, also only made it to the boot animation. I then did a factory wipe on TWRP and tried to restore my backup but now it would only boot to the fastboot (not even trying to load the ROM)....... I can still access TWRP so maybe I'm not so screwed but what do I do? I just want a functioning device and don't mind if I go back to China Stable although advice on trying to flash a custom ROM would be appreciated. Thanks!
Hey you!
So I am back using my Pixel 2 XL and I want to root it, but I am having a lot of trouble doing so... Things I have tried:
First time I just tried installing the zip from magisk, after that my phone was stuck in an endless boot loop, nothing to do there...
I have done as this guide says:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
So this is where I am right now:
Flashed the newest factory image "10.0.0 (QQ3A.200605.001, Jun 2020)" by running the "flash-all.bat", booted it up and everything was working.
Downloaded the newest twrp "twrp-3.3.0-0-taimen.img" and loaded it using fastboot.
Installed "twrp-pixel2-installer-taimen-3.3.0-0.zip" and rebooted into recovery.
Wiped userdata, installed AOSiP 10, rebooted into recovery and installed opengapps.
Booted up the rom and checked that everything was working.
Installed Magisk manager and copied over the boot.img file from the factory zip and did the "patch img" thing.
Rebooted into fastboot and did "fastboot flash boot patched_boot.img"
Now I can boot up the rom but... My touchscreen isnt working? power and volume buttons works just fine, twrp has the same problem after I install it with the zip (it works fine when booting it up from fastboot)
I tried installing the stock boot.img but that didnt change anything.
Another thing is that on slot B is the stock rom and on slot A is the AOSiP rom, is this normal? I don't know how the slot thingy works is it just like partitions?? The stock rom on slot B is working just fine.
-Hapse
Update:
I ran the "flash-all.bat" on both slots and booted up twrp using fastboot and installed the magisk zip (not the img) before installing the manager, I then installed the manager once I booted up the rom. So I guess it's stock with root for now...
hapse said:
Hey you!
So I am back using my Pixel 2 XL and I want to root it, but I am having a lot of trouble doing so... Things I have tried:
First time I just tried installing the zip from magisk, after that my phone was stuck in an endless boot loop, nothing to do there...
I have done as this guide says:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
So this is where I am right now:
Flashed the newest factory image "10.0.0 (QQ3A.200605.001, Jun 2020)" by running the "flash-all.bat", booted it up and everything was working.
Downloaded the newest twrp "twrp-3.3.0-0-taimen.img" and loaded it using fastboot.
Installed "twrp-pixel2-installer-taimen-3.3.0-0.zip" and rebooted into recovery.
Wiped userdata, installed AOSiP 10, rebooted into recovery and installed opengapps.
Booted up the rom and checked that everything was working.
Installed Magisk manager and copied over the boot.img file from the factory zip and did the "patch img" thing.
Rebooted into fastboot and did "fastboot flash boot patched_boot.img"
Now I can boot up the rom but... My touchscreen isnt working? power and volume buttons works just fine, twrp has the same problem after I install it with the zip (it works fine when booting it up from fastboot)
I tried installing the stock boot.img but that didnt change anything.
Another thing is that on slot B is the stock rom and on slot A is the AOSiP rom, is this normal? I don't know how the slot thingy works is it just like partitions?? The stock rom on slot B is working just fine.
-Hapse
Click to expand...
Click to collapse
When you are on stock and you flash a custom rom, the custom rom will be flashed to the opposite slot of the stock rom. So yes, it is normal to have stock rom on 1 slot and the custom rom on the other.
Lughnasadh said:
When you are on stock and you flash a custom rom, the custom rom will be flashed to the opposite slot of the stock rom. So yes, it is normal to have stock rom on 1 slot and the custom rom on the other.
Click to expand...
Click to collapse
Ah I see, thank you