Yet another way to unbrick your r1! - Restore backup method
Closed this issue · 17 comments
I had tried following This is how I unbricked my Rabbit from "Your Dev... to no avail.
So instead I used mtk client, as suggested by several users on the rabbitude discord server, and did the following.
-
Download and unzip an
r1 backupprovided by jadentha. (Edit: link removed use the new one in the readme) -
Run mtk client from the command line using
python mtk.py wl "path\to\backup" --serialportYou can try using the mtk client GUI but in my testing I couldn't get the r1 to connect. Also, if you have issues with slow write speeds (in my case 0.09mb/s) follow this issue. -
Sit back and relax as your r1 is reset back to stock. This could take 20 minutes up to a few hours.
20 minutes up to a few hours...Are you kidding me?
Got back my really "bricked" and I meant "really bricked" device (using the steps/procedures I've explained in my previous post) in just 5 minutes! And the thing is...no matter what I messed up with my device..I can still bring it back to life.
If this can be of any help...I did not use mtk...didn't work for me. I've used the repo r1_escape-main and followed the instructions with "my added touch" and got my device working.
Good luck
It depends if you have a c to c cable that is usb 3.1 which is the cable I used It took like 10 minutes for me but if you have a usb to usb c Cable that is usb 2.0 it will take longer
That may be a dump straight from my device. PLEASE ensure you exclude restore of:
- proinfo
- frp
- protect1
- protect2
- nvdata
- nvram
- nvcfg
These partitions may contain some serials from my unit, you wouldn't want more than one device reporting the same IMEI to your local network or even the same serial to rabbit servers :)
What are you talking about your unit?
What are you talking about your unit?
If this is a mirror (or the same file) as the one i shared with a few users from discord to help them unbrick, it will contain partitions from my unit. Regardless of whether this is my dump or not, as long as these partitions aren't in the zip, you should be fine. If they are, please exclude them when restoring.
That is a dump from me
- Run mtk client from the command line using
python mtk.py wl "path\to\backup" --serialportYou can try using the mtk client GUI but in my testing I couldn't get the r1 to connect. Also, if you have issues with slow write speeds (in my case 0.09mb/s) follow this issue.
Regarding this, on Windows, only serialport mode works without UsbDk. The GUI client does not accept serialport, instead wants libusb (with UsbDk on Windows). On linux, you should be able to do this just fine with GUI.
That is a dump from me
That's perfect then! If you have a better mirror (one that won't get taken down from too many hits), I'd be happy to add the restore instructions with it in my readme.
What about proton drive?
What about proton drive?
That should work, yes
I deleted all the files you said had serials
Added as of: 014e617.
Closing issue. Thank you again!
Your welcome
You might want to close it #1
Done
Just a quick question...by "restoring stock" do you mean restoring the original Rabbit sh...OS?
Who wants to do that?
The Android 13 version is SO much better!
Working with my new "updated" device every single day! Lots of fun!
And I can confirm, be carefull from where you are downloading the R1_Backup.
This one : https://drive.google.com/file/d/1bNOXWickKPgK1KhpIPZ4geoA4Ng36c-G/view
includes everything that you shouldn't be using according to Jadentha (like his personnal serial #/id and such)
proinfo
frp
protect1
protect2
nvdata
nvram
nvcfg
The only "good" one is from https://drive.proton.me/urls/RWFQD4W9Z0#0xrCC1B5fq1u
More info here
014e617
Good night