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
Ok so I flashed the cm10 rom today and used CMD to add the boot.img for cm10 but now I want to go back to Viperrom. I flashed the original boot.img using cmd again but I got stuck in a boot loop (kind of) what I mean by that is that if I flash cm10 from the recovery It works fine but I can't flash any other rom without triggering the bootloop so how do I fix this? I can still access both the bootloader and the recovery and I don't want to go back to stock, just to ics roms. Thank you!
Just clear system, cache and userdata and flash viper ROM in recovery, reboot to bootloader then flash the boot.img from the viper ROM zip file.
Generally you get bootloops and such when on the wrong boot.img.
frdd said:
Just clear system, cache and userdata and flash viper ROM in recovery, reboot to bootloader then flash the boot.img from the viper ROM zip file.
Generally you get bootloops and such when on the wrong boot.img.
Click to expand...
Click to collapse
Thanks, so do you have to flash the img of every rom you want to use?
After flashing TWRP 3.1.0.0 from USB-OTG to my XT1039 the phone boots to TWRP and not into system.
The "funny" thing is that if i keep my USB-OTG stick connected after hitting reboot the system boots. It gets even funnier. If i disconnect the stick the phones goes blank (or powers off) immediately. I checked the stick, there are no partitions, besides the storage partition i created.
Does anyone have an idea what i did wrong to achieve this strange behaviour?
EDIT:
Looks like i flashed recovery.img to boot partition. After manually chosing to install boot.img to recovery partition the system boots, but setup assistant crashes. Seems i'm going to have a long night...
Looks like a complete reinstall is necessary, and if you have to use a flashable ZIP instead of just the recovery image to install the recovery, then do that. In the meantime, try installing the boot.img and recovery.img to the correct partitions.
Got it to work, but only after flashing boot.img to recovery partition and wipe all partitions. When i flash to boot.img, reboot takes me to recovery. When i flash to recovery, system boots, but to get to recovery again i have to flash recovery.img to boot via adb.
All in all very strange and i have no idea what i can do in order to make boot and recovery work side by side.
Guys pls I need your help, is there anyway to restore my phone. Its stuck in boot logo after mistakenly formatting system. I've searched Google and found out that I can flash system.IMG back to my phone using fastboot, but I can't do that cos am scared. There are more IMG files like boot.IMG, user data.IMG and so on my stock ROM zip file. I can no longer boot to edl and cwm is always showing Installation aborted. I use a vivo y913.
Am a new here pls any help???
scaryguadian said:
Guys pls I need your help, is there anyway to restore my phone. Its stuck in boot logo after mistakenly formatting system. I've searched Google and found out that I can flash system.IMG back to my phone using fastboot, but I can't do that cos am scared. There are more IMG files like boot.IMG, user data.IMG and so on my stock ROM zip file. I can no longer boot to edl and cwm is always showing Installation aborted. I use a vivo y913.
Am a new here pls any help???
Click to expand...
Click to collapse
Flash system.img or whole stock rom in a fastboot mode.
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!!