[OFFICIAL][RECOVERY] OrangeFox Recovery Project [R10.1]

[GuestK00171]

Pie bugs?

I don't know...any progress?

 

[DarthJabba9]

I don't know...any progress?

Nope.

 

[svbarbosa]

Hi @DarthJabba9!

I have been using Orange Fox for the Mi Max 3 intensively since February, flashing several GSIs and doing a lot of backup/restore operations, including internal storage.

But yesterday, when running an internal storage backup, there was a fatal error. I tried one more time and the same error happened again.

The full log is attached. Here is the log section where the error happens:

==> set selinux context: ubject_r:media_rw_data_file:s0:c83,c258,c512,c768
I:addFile '/storage/DCIM/Camera/IMG_20190529_142419.jpg' including root: 1
==> set selinux context: ubject_r:media_rw_data_file:s0:c83,c258,c512,c768
I:addFile '/storage/DCIM/Camera/IMG_20190603_220522_1.jpg' including root: 1
==> set selinux context: ubject_r:media_rw_data_file:s0:c60,c257,c512,c768
I:addFile '/storage/DCIM/100ANDRO' including root: 1
==> set selinux context: ubject_r:media_rw_data_file:s0
I:addFile '/storage/DCIM/.thumbnails' including root: 1
==> set selinux context: ubject_r:media_rw_data_file:s0
I:Closing tar
Splitting thread ID 0 into archive 3
I:addFile '/storage/DCIM/.thumbnails/.thumbdata4-1763508120' including root: 1
==> set selinux context: ubject_r:media_rw_data_file:s0:c512,c768
E:Error writing tar file!
I:Error adding file '/storage/DCIM/.thumbnails/.thumbdata4-1763508120' to '/sdcard1/Fox/BACKUPS/be31c41e/2019-06-05--07-46_AOSiP_GSI_AllParts_PQ3A190505002/storage.ext4.win002'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/sdcard1/Fox/BACKUPS/be31c41e/2019-06-05--07-46_AOSiP_GSI_AllParts_PQ3A190505002/storage.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.

 

[DarthJabba9]

Hi @DarthJabba9!

I have been using Orange Fox for the Mi Max 3 intensively since February, flashing several GSIs and doing a lot of backup/restore operations, including internal storage.

But yesterday, when running an internal storage backup, there was a fatal error. I tried one more time and the same error happened again.

The full log is attached. Here is the log section where the error happens:

This typically can happen when a file is too big, causing the phone to run out of memory. In this case, the file that failed is '/storage/DCIM/.thumbnails/.thumbdata4-1763508120' . What is the size of this file?

 

[svbarbosa]

This typically can happen when a file is too big, causing the phone to run out of memory. In this case, the file that failed is '/storage/DCIM/.thumbnails/.thumbdata4-1763508120' . What is the size of this file?

That was certainly the reason. Unfortunately I ran SD Maid to get rid of junk files and all thumbnails got removed.

The good news is that after the clean up Orange Fox was able to make the Internal Storage backup.

This time I noticed a small bug, that maybe is present in all devices.

The Internal Storage size estimate seems to be including the data partition.

Only the estimate. The total size reported when backup finishes seems to be ok.

Please take a look at the attached screenshots.

 

[DarthJabba9]

That was certainly the reason. Unfortunately I ran SD Maid to get rid of junk files and all thumbnails got removed.....
Please take a look at the attached screenshots.

The moral of the story is to always run SD Maid before any backup (I do that all the time), else your backups are full of nonsense, rather than important stuff. On the issue of partition sizes, let's just say that it is at it is.

 

[SUPERUSER]

The moral of the story is to always run SD Maid before any backup (I do that all the time), else your backups are full of nonsense, rather than important stuff. On the issue of partition sizes, let's just say that it is at it is.

I run a scheduled SD Maid every morning at 4 and end with a hard reboot so I have a clean desk and rebooted when I wake up.
On my old phones it could be risky to schedule a reboot in case it got stuck in a bootlop and you don't get woken up by the alarm but on my mi max 3 I haven't had any random bootloops yet, often I was woken up by my older phones that the whole living room is lit up by the boot animation during the dark winter season

 

[DarthJabba9]

I run a scheduled SD Maid every morning at 4 and end with a hard reboot so I have a clean desk and rebooted when I wake up.

:good:

 

[DarthJabba9]

Testers for R10

Hi guys

Nothing much is getting done for this device because there are no testers (and we don't have the device). So, I am looking for testers. If anyone wishes to help test R10 betas, please let me know by PM.

Requirements:
1. Courage
2. Prompt tests and full reports submitted, plus logs
3. The technical ability to recover your device if it gets bricked.

PS: please note that, if we get no testers, then development for the device will simply cease.

Thanks.

 

[WinterR]

Hi guys

Nothing much is getting done for this device because there are no testers (and we don't have the device). So, I am looking for testers. If anyone wishes to help test R10 betas, please let me know by PM.

Requirements:
1. Courage
2. Prompt tests and full reports submitted, plus logs
3. The technical ability to recover your device if it gets bricked.

PS: please note that, if we get no testers, then development for the device will simply cease.

Thanks.

How horrible can the bricks be?

 

[DarthJabba9]

How horrible can the bricks be?

If the supposed "brick" is simply that the recovery doesn't boot (eg, hangs at the Mi logo, or at the Fox logo), or doesn't decrypt encrypted data, then it is nothing that can't be cured by flashing a working recovery via fastboot (or with an app like flashify). If you can "hotboot" in fastboot mode (ie, by running "fastboot boot <recovery_img>") then "de-bricking" will simply consist of restarting the phone with the power button.

If the brick comes from flashing a ROM, or magisk or whatever, and the phone doesn't boot to the ROM, then the worst that can happen is that you might need to do a clean flash of the ROM, with a working version of the recovery (or, at very worst, flash a fastboot MIUI ROM). The last is the worst possible scenario - and it is a most unlikely scenario. But with technology, one has to be prepared for anything. So, better backup everything first.

 

[WinterR]

If the supposed "brick" is simply that the recovery doesn't boot (eg, hangs at the Mi logo, or at the Fox logo), or doesn't decrypt encrypted data, then it is nothing that can't be cured by flashing a working recovery via fastboot (or with an app like flashify). If you can "hotboot" in fastboot mode (ie, by running "fastboot boot <recovery_img>") then "de-bricking" will simply consist of restarting the phone with the power button.

If the brick comes from flashing a ROM, or magisk or whatever, and the phone doesn't boot to the ROM, then the worst that can happen is that you might need to do a clean flash of the ROM, with a working version of the recovery (or, at very worst, flash a fastboot MIUI ROM). The last is the worst possible scenario - and it is a most unlikely scenario. But with technology, one has to be prepared for anything. So, better backup everything first.

Well that doesn't sound horrible xD
So i could test the recovery.

 

[DarthJabba9]

Well that doesn't sound horrible xD
So i could test the recovery.

Please see your PM.

 

[svbarbosa]

Hi guys

Nothing much is getting done for this device because there are no testers (and we don't have the device). So, I am looking for testers. If anyone wishes to help test R10 betas, please let me know by PM.

Requirements:
1. Courage
2. Prompt tests and full reports submitted, plus logs
3. The technical ability to recover your device if it gets bricked.

PS: please note that, if we get no testers, then development for the device will simply cease.

Thanks.

Count me in!

 

[DarthJabba9]

Count me in!

:good: Please see your PM.

 

[svbarbosa]

Content moved to PM.

 

[svbarbosa]

Content moved to PM.

 

[svbarbosa]

Content moved to PM.

 

[svbarbosa]

Well, i finally took the leap of faith and made a full backup / restore, with all partitions, including Internal Storage and persist.

My phone is working fine. Backup / restore was a success with r10. :victory:

@DarthJabba9, do you want me to post the logs?

 

[DarthJabba9]

Well, i finally took the leap of faith and made a full backup / restore, with all partitions, including Internal Storage and persist.

My phone is working fine. Backup / restore was a success with r10. :victory:

@DarthJabba9, do you want me to post the logs?

Excellent! Thanks. Can you please send the logs to me by PM?