Does TWRP recovery for the One S (S4) T-Mo require me to flash a seperate boot.img when I flash a rom, say Trickdroid v8.0? I want to flash either CM10 or Trickdroid but I'm not sure if TWRP will automatically access the boot.img in the ROM.zip. Any help would be greatly appreciated:fingers-crossed:
try just flashing the .zip and if it doesn't work then boot back into recovery and wipe then boot into bootloader -> fastboot, extract the files from the .zip on your computer, then flash the boot.img manually through fastboot, then boot into recovery and install the .zip. trial and error. it's how we learn
p.s. i know that cwm recovery automatically flashes the boot.img but twrp might not
What is the correct procedure to update from twrp?
is flashing the ROM in TWRP then flashing twrp.zip then magisk and then kernel a correct way to update the ROM?
is there a tested way?
Tested way is:
1) flash full zip via TWRP and do not reboot
2) flash twrp.zip or you will lose it after reboot
3)reboot to recovery
4) flash magisk and/or kernel
5) reboot to system
6) done
I've been away for about a year so I'm behind on everything right now. I just flashed a factory image to get back to Android 8.1 and set my phone up from scratch. I would like to install TWRP and Magisk but have some questions..
TWRP. Do I just find the latest TWRP for this phone and the process is the same as before? Fastboot flash twrp img and then install TWRP zip?
Magisk: I have never used it before so I'm not to familiar at all. From what I can tell I just download the zip and install via twrp? Is there a specific version I should be looking for for the Pixel on 8.1 or will the latest from the Magisk forum work?
I've searched around and keep seeing random issues so I'm wondering if it's as straight forward as mentioned above. I see posts about people trying to install TWRP and Magisk and bootlooping and stuff like that. Thanks!!
Hello look here for the latest Recovery. https://twrp.me/google/googlepixel.html
Flash the TWRP image over the PC.
fastboot boot recovery TWRP.img
Then Flash it via TWRP. (the zip file on your sdcard).
The device has an A and B Partition. It would Flash on both.
If you Flash an custom Rom you Flash it on A Partition you must Flash TWRP.zip again. Reboot the device. After an reboot to Recovery you on B Partition automatically. Here you can Flash Magisk and other zips like custom Kernel or other.
If you Flash the custom Rom on B Partition you must flash magisk and other stuff on A Partition.
With Magisk 18.0 stable, some people have bootloops when flashing TWRP.
Best thing to do is just boot TWRP img when needed instead of flash the zip, maybe this has been fixed with latest canary builds but it's better boot the image just to be sure
So I'm bootloader unlocked for 10.0.0.1 I'm about to update to 10.0.3.
Everytime I try to flash recovery or boot recovery with twrp it doesn't work.
If I load it via magisk it works sometime but other times causes bootloops.
My biggest issue is booting/flashing twrp and When I flash a custom rom.
It says to flash on A and B. Sometime I can flash to one but when u change to other slot it wolnt flash or it'll show like it's encrypted any help? I've been on basic OS with NoLimits but now I wanna do kernel, rom flashing etc. Help?
If you want to update from .1 to .3 just do this(keeping in mind that you already had twrp and magisk)
Put update.zip in your internal storage
Go to settings>system>updates>local upgrade
Select update and install
Wait to finish but DONT REBOOT
go to magisk and install twrp installer(I use V3.3.1-74)
Then install magisk to inactive slot(after ota)
Reboot and that's it!
You can install custom kernel from twrp or fk kernel or any other app
If you want to install a rom you had to install to both slots(keep in mind that ROMs always be installed on inactive slot)
So make a factory reset(default by twrp wipes data and dalvik)
Install your rom and don't reboot(example if you are on A slot it will be installed to B)
Install twrp installer
Reboot to recovery( this will change slots A to B for example)
Install your rom (slot B to A and you will have your rom in both slots right?)
Again install twrp installer
Reboot to recovery
Flash gapps( if rom don't have it) magisk and kernel I personally recommend to flash after first boot
EDIT:
And another thing, if you get your internal storage encrypted and you can't access your rom,gapps,magisk you can always use adb sideload:
In your platform tools folder put your rom,magisk, etc and in twrp go to advanced>adb sideload and swipe to initiate.
In your command window use this:
adb sideload <nameofyourfile.zip>
Example: adb sideload magisk.zip
This will transfer and install magisk, ROMs and gapps
Sent from my OnePlus7Pro using XDA Labs
Here's the hinge on the rom right? Install on slot in recovery OK good got it. Reboot recovery try to install on other slot there is nothing on phone or its encrypted.
In TWRP I was not able to see System and Vendor Partitions in Wipe Section so like a fool
I flashed twrp image in Super, this put me in bootloop
After this I flashed some files from the fastboot version of Stock ROM in the following manner
https://www.droidwin.com/unbrick-poco-x2-fastboot-commands/
But even after this I am was in Bootloop so to see if it is a TWRP problem due to which I was not able to see System and Vendor Partitions, I installed Orange Fox Recovery.
After installing Orange Fox Recovery R11
I wiped Dalvik / ART Cache
Data
Cache
And flashed the Custom ROM(Evolution X 5.8) but then this happens :
assert failed: update_dynamic_partitions (package_extract_file("dynamic_partitions_op_list"))
Updater Process ended with EROOR :1
Error installing ZIP file "path of the file"
Please help !!!
I heard that orangefox has issues with custom rom. Use Original twrp for custom roms. Hot boot twrp and flash . No need to wipe cache or data before flahsing. But after flash format data.
notathinker said:
In TWRP I was not able to see System and Vendor Partitions in Wipe Section so like a fool
I flashed twrp image in Super, this put me in bootloop
After this I flashed some files from the fastboot version of Stock ROM in the following manner
https://www.droidwin.com/unbrick-poco-x2-fastboot-commands/
But even after this I am was in Bootloop so to see if it is a TWRP problem due to which I was not able to see System and Vendor Partitions, I installed Orange Fox Recovery.
After installing Orange Fox Recovery R11
I wiped Dalvik / ART Cache
Data
Cache
And flashed the Custom ROM(Evolution X 5.8) but then this happens :
assert failed: update_dynamic_partitions (package_extract_file("dynamic_partitions_op_list"))
Updater Process ended with EROOR :1
Error installing ZIP file "path of the file"
Please help !!!
Click to expand...
Click to collapse
I found a copy of OrangeFox that worked for me available here.
OrangeFox-R11.1-Stable-Unofficial-lime.zip
AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
The key was to first flash xiaomi.eu_multi_HMNote94G_HM9T_V12.5.6.0.RJQCNXM_v12-11.zip
reboot the phone and let it fully start (I think this updated the partition tables or something)
Then go back into OrangeFox and flash crDroidAndroid-11.0-20220121-juice-v7.14.zip
By doing this I was able to get the phone to boot into crDroid whilst using OrangeFox without any bootloops or partition size errors like the one I was initially getting "assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list"))"
I think the important step is to let it fully boot after putting on the xiaomi.eu ROM as it must resize partitions or something...
I am having the same problem. I tried to restore an orangefox backup and i ticked the "super" box. After that when i try to flash a rom proccess fails with the exact same message (assert failed: update_dynamic_partitions (package_extract_file("dynamic_partitions_op_list"))). I have flashed three different recoveries (pitchblack, orangefox, lineageos) and tried from every each of them flashing a rom both from the recovery and sideloading. The roms i have tried are: crdroid A12, arrowos A11 & A12, lineageos microg and at last the stock miui for my device. Nothing worked so far. Please if someone has any knowledge or ideas help because i am starting to believe it is irreversible...
Device: Redmi note 9s (curtana)
I finally figured it out. Since I was not able to flash any ROM (including stock miui) from the recovery, neither with sideloading, I had to download Mi Flash tool on my PC and a miui ROM .tgz file, used especially for flashing through Fastboot/Mi Flash. Then I booted my phone on fastboot mode and connected it to PC, opened the MiFlash tool on PC, chose the miui Rom file (you have to extract twice from the original .tgz file to reach to the selectable one, and I also had to put it on Desktop otherwise it could not be reached) and finally flash it.
HomoImpudens said:
I finally figured it out. Since I was not able to flash any ROM (including stock miui) from the recovery, neither with sideloading, I had to download Mi Flash tool on my PC and a miui ROM .tgz file, used especially for flashing through Fastboot/Mi Flash. Then I booted my phone on fastboot mode and connected it to PC, opened the MiFlash tool on PC, chose the miui Rom file (you have to extract twice from the original .tgz file to reach to the selectable one, and I also had to put it on Desktop otherwise it could not be reached) and finally flash it.
Click to expand...
Click to collapse
Yeah, after flashing it with miflash tool your phone runs fine with miui. Were you able to install a custom rom after this? If yes, could you tell what steps did you follow.
If I remember correctly, after that I followed the standard procedure first to flash a custom recovery and then through that a custom rom. Downloaded SDK tools (if I remember the name correctly), opened smartphone on fastboot mode, opened terminal window fom inside SDK tools folder, downloaded a custom recovery, placed it inside SDK folder, rename it "recovery", typed on terminal window: "fastboot flash recovery recovery.img" (again if I remember correctly) and then reboot to recovery. From there install any custom Rom you want.
Orangefox recovery have tick of unmount system and vendor, dont forget to tick them and it will solve your problem
GiGilGilang said:
Orangefox recovery have tick of unmount system and vendor, dont forget to tick them and it will solve your problem
Click to expand...
Click to collapse
Thank you so much. I'm so lucky that I stumbled into your comment, you saved my device!!