search

RabbitHoleEscapeR1 / r1_escape

256 stars 20 forks source link

Recovery Mode #29

Open Genericusername12345678 opened 1 week ago

Genericusername12345678 commented 1 week ago

I'm trying to root my r1 and I need to get into recovery mode to do so. Does anybody know how to enter recovery mode with the scroll wheel? Thanks for reading btw.

M4cs commented 1 week ago

Use fastboot to get into recovery

Genericusername12345678 commented 1 week ago

Thanks, I'll try to get into fastboot.

Davis8483 commented 1 week ago

Let me know how it goes, I accidentally bricked my device while trying to install twrp to get root access

Genericusername12345678 commented 1 week ago

Same here actually. Now I’m stuck in a boot loop. Happy to hear any ideas

On Wed, Jun 26, 2024 at 6:08 PM Noah Davis @.***> wrote:

Let me know how it goes, I accidentally bricked my device while trying to install twrp to get root access

— Reply to this email directly, view it on GitHub https://github.com/RabbitHoleEscapeR1/r1_escape/issues/29#issuecomment-2192704078, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJONHSXJLIG6JMPYJZZBVN3ZJM3XBAVCNFSM6AAAAABJ4X35DCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJSG4YDIMBXHA . You are receiving this because you authored the thread.Message ID: @.***>

AgentFabulous commented 1 week ago

Thanks, I'll try to get into fastboot.

You need to get to fastboot using mtkbootcmd.py as per the script, then just issue fastboot reboot-recovery. If you're not able to enter recovery after that, there may be an issue with your boot (recovery-in-boot) image

Genericusername12345678 commented 6 days ago

i'm pretty sure it's a problem with the boot.img file. I tried to flash a twrp image and when i tried to reboot i was stuck in a boot loop. I think my best bet is to get the original image on the boot partition somehow.

libidae commented 4 days ago

Without running "adb root" first, if you shell into the r1 and run su the prompt changes to a pretty #. You already have (shell) root and an unlocked bootloader. You can patch boot_a with Magisk to manage su access across apps, which after installing on your boot partition allows systemless operation.

What you're talking about is a custom recovery. You need that if you're switching roms a lot, or have another reason which precludes a pc to flash (eg, broken port). The only thing you're really missing is Nandroid backups, but dd and pull for the individual partitions is just as good imho. I wouldn't mess with the PITs. You also need the custom recovery to be heavily modified for each model of phone. While you can get TWRP installed on the r1, it lacks most functionality (and will guarantee you an unstable device). If you really need a custom recovery try adb boot first (idk if it's allowed though).

The r1 is an A/B system - the recovery partition is the bootloader. So when you flash a custom recovery to it, it needs to include the stuff that makes everything run. Flashing direct wipes your kernel and tree. You also would have needed to flash both partitions (A&B) with the image for it to work.

Assuming you didn't write a new PIT it should be easy to recover your r1 though. Charge it up, then use the SIM button to cut power. When you plug it into a pc running fastboot the r1 boots into fastboot mode. Just restore the stock ROM, or if you can get a boot.img and are feeing lucky you can flash that instead (to both A&B). Going back to stock is safer though.