Twrp for the qin f21

Phones Qin F21 Pro
1

@sh7411usa I saw you have some experience with twrp and the qin f21 here and here, and you spoke about some of the problems and confusions I have but I don’t fully understand what you meant

Here is what I have experiened: I flashed boot_a.img from the 1.1.1 ROM, NOT boot2… (Was I supposed to? What’s the diff… It says to fix the storage path to /sdcard on the 1.1.1 XDA guide, don’t get it…)

I booted into twrp, and now when I try to reboot to system it bootloops to twrp…

Also I saw there is some difference btwn 3/32 and 4/64… I have a 3/32… did I flash the wrong thing?

2

To clarify from the OP: I took the boot_a.IMG from the XDA 1.1.1 zip file, and it works fine…(Besides for not booting to system, kn"l)

I now see that it says in the after you flash 1.1.1 to flash a boot2.IMG, and the mitmachim one for 3/32 which I didn’t do.

Sorry if I’m not being clear, dont know how to explain better

3

I would love to assist. Can you clarify:

  1. What you were trying to accomplish.

  2. What you did.

  3. What undesirable behavior you are experiencing as a result. (I got the bootlooping part. But the first two points are unclear)

It would also be helpful if you indicated what “generation” your device is (v1, v2, etc.) and if it is a 32 or 64 gb.

4

Ye sure

Basically I replaced some system apks (see this thread) and tried using twrp to fix. It didn’t work and @ars18 suggested a fix that I wasn’t able to try yet, but I will as soon as I can. Now I’m just interested in the twrp in general

I have a v1 3/32 with 6.1.3 ROM. I downloaded the zip for 1.1.1 from xda, and took the boot_a.img that gets flashed with spflash, not realizing that in the XDA guide it said to flash a different boot afterward.

I tboot into twrp and tries fixing (see my post linked above) and now it just bootloops into twrp whenever I reboot to system (kinda like what u said about the cat s22)

5

Try reflashing boot that came with 6.1.3. We know this one worked with your device. If the issue persists after that, we’ll take it from there.

6

Actually, I take that back. It seems from this conversation that you corrupted your system partition.

Actually, no sheychis. Over there, we had a useless recovery - it did not have rw permission over the system partition. Over here we are discussing a perfectly healthy recovery and a corrupted system. Most likely android boot sends you to recovery because it fails to boot into system, it detects something wrong and wants you to recover the system partition. I will echo the advice you received in that conversation: Reflash the system partition.

And, Rabbosai: The big mussar haschil here is… ALWAYS MAKE A BACKUP BEFORE YOU MESS WITH THE SYSTEM. “Because afterwards is too late.” ( - Uncle Moishy)

1 Like
7

Yea that’s what im gonna do,

I was mainly wondering about the different twrps on XDA, which to use

Why do I have to back up system if its available online?

8

You do not have to backup your system. You have to back up your data. Your data is currently inaccessible. While we all hope you recover successfully, on the tzad that you are not matzliach, you would have been happy to have made a back up.

1 Like