so I'm in twrp 3.2.3-0 and using custom roms without flashing that decrypt.zip and i want to update my twrp what to do?
and if i want to update, can i flash the img file via twrp?
Download higher twrp.img file and flash via exsisting twrp in recovery partision ,your recivery will be updated.
Related
After manually flashing files to upgrade to 6.0.1, I flashed TWRP 2.8.7.0. But I am not able to flash supersu from sdcard because when I browse to the folder, it looks empty.
Anyone has any idea why this is happening?
if you have not formatted userdata after you flashed the recovery img in fastboot that would be one reason, the other reason could be if you used a pin/pattern/password for your phone. if you disable that or format the userdata in fastboot then you should be able to see it.
TWRP 2.8.7.0 didnt support decryption, and that may be why you cant
starting with 2.8.7.1 and now 2.8.7.2 it does support decryption.
Please download 2.8.7.2 and flash that and report back, bet ya its going to work fine after that.
MPAI said:
After manually flashing files to upgrade to 6.0.1, I flashed TWRP 2.8.7.0. But I am not able to flash supersu from sdcard because when I browse to the folder, it looks empty.
Anyone has any idea why this is happening?
Click to expand...
Click to collapse
You're using an outdated version of TWRP, it can't decrypt your storage. Update to the latest version and it'll be fine.
I wanna go to the RR MM version ROM for Zenfone 5, but fewmsome days before I decide to do it, my microusb got some kind of bug, anyway, it doesn't connect to pc (I tried everything). So, in the tutorial says to flash the new recovery made by them, but i don't have how to connect it on pc to flash the new TWRP recovery, but I have a funcional system working (the stock .87 version from asus) and I want to know if there's a way that I can flash the recovery without using pc (once that my microusb jack is f*kd). I saw in other forum that "recovery.img" is inside the /factory partition, so apps like Flashify cannot read and write on it. Just droidboot can do that. So this is what I want to know, of there's a way to flash the recovery trough the booted Android and if I can make a script to Droidboot run. (Of course, all of them without pc). Or even if I can flash RRMM on my current twrp version (2.8.7.0)
Thanks xda.
Try to flash it via TWRP 2.8.7.0
"Error flashing image, no partition specified".
Twrp actually doesn't show any partitions to install the image.
MarconiGRF said:
"Error flashing image, no partition specified".
Twrp actually doesn't show any partitions to install the image.
Click to expand...
Click to collapse
I provided flashable zip for my RR MM rom. So you shoudl just choose zip archvie with rom to flash it.
It is not a image.
tank0412 said:
I provided flashable zip for my RR MM rom. So you shoudl just choose zip archvie with rom to flash it.
It is not a image.
Click to expand...
Click to collapse
Oh, I read your post again, i'll try to flash with twrp 2.8.7.0
Sucessful installing ROM, really fast and battery management. Thx
So I recently downloaded the RR Marshmallow custom rom , and when I flash the rom the twrp just re opens / restarts . help plz ? and also how can I flash .img files (kernels)?
Connect phone to computer and use Odin to flash TWRP, after that boot to TWRP wipe data and install custom rom.
You can use Odin or TWRP to flash img file.
Hi guys,
At the moment we don't have many custom ROMs for 6T but we have quite a few custom kernels to play with.
Let's say we are on latest OSS, regards with Magisk and having TWRP. And with custom Kernel.
Correct way to go back to stock kernel and flash different custom kernel would be:
Boot to TWRP.
Flash Stock boot.img
Reboot to TWRP again
Flash TWRP zip
Reflash Magisk
Reboot to System.
Done.
Am I correct? Or do we have to reflash full OTA?
wangdak said:
Hi guys,
At the moment we don't have many custom ROMs for 6T but we have quite a few custom kernels to play with.
Let's say we are on latest OSS, regards with Magisk and having TWRP. And with custom Kernel.
Correct way to go back to stock kernel and flash different custom kernel would be:
Boot to TWRP.
Flash Stock boot.img
Reboot to TWRP again
Flash TWRP zip
Reflash Magisk
Reboot to System.
Done.
Am I correct? Or do we have to reflash full OTA?
Click to expand...
Click to collapse
Boot to TWRP.
Flash Stock boot.img
Flash twrp zip
Reboot to TWRP again
Reflash Magisk
Reboot to System.
Done.
indian84 said:
Boot to TWRP.
Flash Stock boot.img
Flash twrp zip
Reboot to TWRP again
Reflash Magisk
Reboot to System.
Done.
Click to expand...
Click to collapse
Is it okay to flash img files in TWRP? I was told that it is meant just for zip files. Fastboot for img files.
devilrulz4ever said:
Is it okay to flash img files in TWRP? I was told that it is meant just for zip files. Fastboot for img files.
Click to expand...
Click to collapse
As long as you flash correct image to correct slot, it should not be an issue..
devilrulz4ever said:
Is it okay to flash img files in TWRP? I was told that it is meant just for zip files. Fastboot for img files.
Click to expand...
Click to collapse
Since years
my preference is to use EXKM and flash through there. my process
need:
stock boot for whatever your running, in my case .11 boot.img
whatever kernel you want to flash
1. in exkm, flash the stock boot.img, don't reboot
2. then flash your kernel of choice, don't reboot
3. in magisk manager, flash magisk, and use direct patch, then reboot
once it reboots, your g2g
Hi everybody,
I have a OP 6T McLaren, Oxygen 9.0.12 and I tried to uninstall Magisk 18.1 and update to Magisk 18.2 canary and something went wrong. After flashing I got the following error:
!Unable to unpack boot image
---
Updater process ended with ERROR: 1
Error installing zip file `/sdcard/Download/magisk-uninstaller.zip
The same error when I try to flash any Magisk version.
Phone doesn`t boot into system now. I can fastboot into TWRP and access files and folders.
Thank you very much in advance for your help.
Flash the magisk uninstaller then reboot. Then flash magisk.
I can't flash magisk uninstaller or magisk. It gives me the above error.
Even if I flash twrp installer in temp twrp it installs without error but after reboot it boots only in bootloader.
What can I do now to get the system working again?
-flash stock boot.img (where do I get file for McLaren 9.0.12?
-use MSMdownloadtool from here?
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
flash this ota via temp twrp?
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
Try
Reflash OOS 9.0.12
Flash twrp
Reboot recovery
Flash magisk
Reboot system
Backup your data
Sent from my OnePlus6T using XDA Labs
Mclaren uses the same stock restore image.
I've been there format data .my friend let's his SD card encrypt or get errors on top of letting twrp (wrong version won't decrypt data either) if you do that reboot in system make sure adb is on and oem and auto updates are off
use different twrp the test build works better I had problems with orginal TWRP too
Solved!
All I had to do was flashing stock boot.img to boot_A and boot_B. Now It's working again...
Thank you very much for your help.
kika1992 said:
Solved!
All I had to do was flashing stock boot.img to boot_A and boot_B. Now It's working again...
Thank you very much for your help.
Click to expand...
Click to collapse
Ah.. Stuck in exactly same situation. Did you unzip the stock rom and flash boot.img through fastboot? Or did you take any different steps?
Niks.
Yes, unzip and flash both files via fastboot.
Just a note.
When installing Magisk and TWRP; I always install Magisk in one slot and reboot. I then use a partition backup tool to grab the stock boot image.
I then flash the stock boot image so the phone is completely stock again.
At this point I go through the TWRP and Magisk install the normal way.
I do this so I can always flash back to stock.
I also don't care about retaining TWRP or root.
I just start all over. It takes a few minutes but I don't usually have issues.
I also local install the same ROM to both slots before I install anything.
This way the opposite slot will always boot with the same version of the ROM.