RabbitHoleEscapeR1 / r1_escape

256 stars 20 forks source link

Need help with recovery #38

Open cmd-1bZ opened 6 days ago

cmd-1bZ commented 6 days ago

everytime i type the command in python mtk.py wl "path\to\backup" --serialport Either mtk has a syntax error or its the path

can anyone help me so I can recover

All help Appreciated ty

thededman commented 6 days ago

I don't think that works. I've been trying all night, and I believe I have bricked mine. I am going up on eBay selling mine as a dead rabbit. I wanted to restore to Factory as well.

cmd-1bZ commented 5 days ago

My r1 just wont turn on this is after i flashed it so i think its dead

potsogold commented 5 days ago

i got this to work and is currently reflashing the entire r1 backup to my device as we speak. it's taking a long time though, but it is working.

step1: download the r1 backup file from the new readme update in "r1_escape" and extract it to desktop https://drive.proton.me/urls/RWFQD4W9Z0#0xrCC1B5fq1u

step 2: download the standalone mtkclient https://github.com/bkerler/mtkclient extract to desktop

step 3: open mtkclient-main folder, right click and open the file in terminal

step 4: regarding 'python mtk.py wl "path\to\backup" --serialport', you need to copy and paste the path of the r1backup folder into where it says "path to backup"

step 5: connect rabbit, then run the command with the correct path to r1 backup inserted with quotation marks: py mtk.py wl "C:\Users\matt\OneDrive\Desktop\r1 backup" --serialport

SmallMothStudio commented 4 days ago

I keep running into this error: ModuleNotFoundError: No module named 'colorama' right on line 19

potsogold commented 4 days ago

also, during my reflash, there is a file sspm_b.bin in r1 backup that is taking an estimated 67 hours to apply, and the file is only 1mb. im not sure why this is, but i stopped the flash and restarted, and its still happening. so painfully slow. going to attempt to do so without the file to see what happens lol..

Coyoteejim commented 4 days ago

I keep running into this error: ModuleNotFoundError: No module named 'colorama'

right on line 19

You have to install any missing packages like colorama. Some of them will require you to uninstall then reinstall, or reinstall using sudo (if on Linux).

I kept rerunning the r1.sh script and checking every error message for missing packages. Only when all the packages are recognized you can then go through the 'plug/unplug' prompts.

libidae commented 4 days ago

It's a typo in the instructions with mtk. There is no mtk.py file, it's just mtk in the mtkclient folder. Use the same command but without the py.

Slow flash is usually from \r1_escape-main\mtkclient\mtkclient\Library\DA\xflash\xflash_lib.py having a tiny value for send_param. I use 0x80100, it's faster than the port but doesn't cause any issues. If you've already started just ctrl-c and restart, the difference is 0.1mbps vs 15mbps. It's on line 162 btw.

The script should install all the tools it needs, but it installs in a venv. Just keep retrying until they're installed.

I think it's unlikely that you've killed your r1 even if you only vaguely followed some of the instructions. It takes some real effort to brick them. If you use the SIM button to power off completely it will boot into fastboot mode when you plug it in. It looks dead bc of the black screen (fastboot isn't fastbootd). Leave it off and charging for an hour or two before fixing it.

cmd-1bZ commented 4 days ago

after it stopped turning on i did try press the reset but didnt notice a difference then i charged it too but nothing

libidae commented 4 days ago

The button isn't a reset, it cuts the power and stops the r1 as gracelessly as possible. If you see anything on the screen after that you missed the button and it's still looping. You want to charge it first, then cut the power with that switch ready for fastboot. Once it's connected confirm that it switched on and has entered fastboot by requesting "fastboot devices."