When I first time flashed twrp via Odin in Samsung Everthing was ok. But today I don't have computer (It is brocken) and I flashed magisk.zip in twrp in wrong way because twrp flashed as recovery. It cause bootloop but then I flash uninstall.zip and tryied to flash stock recovery in twrp but partitions /boot and /recovery is too small what should I do?
Ok i was using wrong files. Boot.img was from difrent device. How to close thread?
You can report your own post asking to close it.
Related
What is needed to pull the stock recovery image I already dumped the partition correctly I have root running on stock recovery.
I just need to figure out why i cant boot the stock recovery from fastboot
the screen just gets scrambled. But i mean i do have the recovery.img and boot.img pulled from their respective blocks. and dd'd into imgs
Maybe someone could point me in the right direction and we can have a copy of the stock recovery as well. I don't want to
fastboot flash it in case of bricking the recovery partition(Even though it should be a 1-1 copy)
I wanted to boot TWRP rather then flash it to install super su then boot into system to backup recovery partition using flashify. I can boot into TWRP but then I can't do anything after that.
LarryBoyG said:
I wanted to boot TWRP rather then flash it to install super su then boot into system to backup recovery partition using flashify. I can boot into TWRP but then I can't do anything after that.
Click to expand...
Click to collapse
Ill try with flashify i got TWRP to boot using fastboot boot, but i cant get the stock recovery to work. and dont want to flash without making sure. since the stock recovery when i use dd is 16mb
Today, I need to make a Nandroid backup, so I boot my phone to recovery, but it's stuck in a bootload with twrp lgo on the screen.
I tryed many ways to do that (use apps like Quickboot, ROM manager, and do it manual by press buttons ) but it's still freeze on twrp's logo screen.
But before, about a week ago, I maked a Nandroid backup and success without any errors.
My TWRP version is 3.00-0
Can you help to fix that? Pls
Tks for read.
I tryed to reinstall twrp by commands:
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot
and I get an error:
Code:
mismatched partition size
after the second command.
And still no luck :crying:
Tryed to update to newer twrp's vesion but still no luck. :crying:
Flash the 2.8.7.1. But before you do, flash the stock recovery img then flash TWRP 2.8.7.1 instead of the latest TWRP 3.0 . It bugs on our lil' Victara. Good luck hehe
thousandecibels said:
Flash the 2.8.7.1. But before you do, flash the stock recovery img then flash TWRP 2.8.7.1 instead of the latest TWRP 3.0 . It bugs on our lil' Victara. Good luck hehe
Click to expand...
Click to collapse
Where I can find stock recovery img?
I found some files named recovery-5.0-stock.img on
https://www.reddit.com/r/MotoX/comments/37l226/stock_recovery_img_for_moto_x_2014_50/
Can it flash for 6.0.1 ?
Mark2014 said:
Where I can find stock recovery img?
I found some files named recovery-5.0-stock.img on
https://www.reddit.com/r/MotoX/comments/37l226/stock_recovery_img_for_moto_x_2014_50/
Can it flash for 6.0.1 ?
Click to expand...
Click to collapse
You can find the IMG file in the Moto X 2014 lollipop/marshmallow firmware zips available on Mega. Be vary, you need to know exactly what device model you are using(mine is XT1092).
Also I just tried flashing Cyanogen recovery and then flashed TWRP 2.8.7.1 It worked too. I had the same problem day before yesterday with TWRP 3.0.
thousandecibels said:
You can find the IMG file in the Moto X 2014 lollipop/marshmallow firmware zips available on Mega. Be vary, you need to know exactly what device model you are using(mine is XT1092).
Also I just tried flashing Cyanogen recovery and then flashed TWRP 2.8.7.1 It worked too. I had the same problem day before yesterday with TWRP 3.0.
Click to expand...
Click to collapse
Tks so much :good: It works :laugh:
Hi
I recently installed twrp 3.1.0-0 through cmd. I saw a thread about twrp 3.2.1.0-0 so it was a zip file instead of img file so I went to twrp and flashed that zip after that whenever I reboot my phone to system in stays on mi logo forever. Then I flashed a rom .tgz file through mi flash tool. To check I went back to twrp using my pc cmd typing the command "fastboot boot twrp.img" . I was taken to twrp recovery. I did nothing and tried to boot back system again same thing stuck here forever. I had to go through the same flashing process to get my phone back.
you probably need to restart again by flashing a new rom and read carefully howto.
U Can just flash no-verity-opt-encrypt here https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.0.zip
Mahadi14 said:
Hi
I recently installed twrp 3.1.0-0 through cmd. I saw a thread about twrp 3.2.1.0-0 so it was a zip file instead of img file so I went to twrp and flashed that zip after that whenever I reboot my phone to system in stays on mi logo forever. Then I flashed a rom .tgz file through mi flash tool. To check I went back to twrp using my pc cmd typing the command "fastboot boot twrp.img" . I was taken to twrp recovery. I did nothing and tried to boot back system again same thing stuck here forever. I had to go through the same flashing process to get my phone back.
Click to expand...
Click to collapse
if stock recovery is replaced by TWRP then stock rom wont boot.
to boot you need to disable dm-verity in boot.img magisk does this while flashing.
so to boot just flash magisk or dm-verity disabler or lazy flasher
i have flashed via odin about a hundred times by now. today i downloaded the new android 10 update because before i was flashing 9 still.
but updating doesn't help, let me tell you what my problem is. whenever i patch the AP file in magisk manager then flash via odin to my then stocked phone i get rooted but am not able to flash anything to recovery. for example:
FLASHING TWRP from the phone never works and hasn't worked a single time.
u can flash the default twrp from the official app which results in a boot loop.
u can flash the magisk_patched.img (after having put official twrp.img through magisk manager)
by entering this into a SU terminal: # f=/storage/emulated/0/Download/magisk_patched.img; dd if=$f of=/dev/block/sda15 bs=$(stat -c%s $f)
but that also results in a boot loop.
flashing default twrp tar via odin does work however it isn't patched via magisk because that AGAIN doesn't work, not even with odin (for those asking "how do you flash .img through odin" i heard success stories from others that executing tar command in linux just archives the .img and if it's named recovery.img inside the tar archive odin has no problem flashing... this is what i did)
anyway i wanted twrp so i could flash my favorite custom rom onto the device, but i'l have to do with rooted stock rom for now
When a patched boot.img is booted it always enters fastboot mode even if system is targeted. However, if the stock boot.img is patched again, everything works as usual. Any ideas on how to fix this?
Did you type on your pc fastboot reboot as a final step? Maybe you have to repair or reflash the stock rom using miflash and try again (you cant clear cache without twrp) as a way to get the system prepared to Flash a modified boot image
I have the exact same problem. I tried older versions of Magisk, then the Canary build, but nothing helped..
Bilihh said:
When a patched boot.img is booted it always enters fastboot mode even if system is targeted. However, if the stock boot.img is patched again, everything works as usual. Any ideas on how to fix this?
Click to expand...
Click to collapse
Found a solution! It's right here:
How to flash twrp recovery and root redmi note 10s?
I can't install a twrp recovery if I tried A message appears (remote : this partition doesn't exist)
forum.xda-developers.com