Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Not able to install via custom recovery #131

Closed
errwnd opened this issue Sep 6, 2022 · 7 comments · Fixed by #133
Closed

Not able to install via custom recovery #131

errwnd opened this issue Sep 6, 2022 · 7 comments · Fixed by #133
Assignees
@chenxiaolong
Labels
bug Bug in BCR itself

Comments

@errwnd
Copy link

errwnd commented Sep 6, 2022

Ofox recovery; Derpfest rom 12L. Flashing the zip is not working.
@chenxiaolong
Copy link
Owner

Please grab the recovery log with adb pull /tmp/recovery.log after attempting to flash the zip and upload it here.

@errwnd
Copy link
Author

errwnd commented Sep 6, 2022

Installing ZIP file '/sdcard/Download/BCR-1.19-release.zip'
Unmounting Super...
I:Unmounting main partitions...
I:Update binary zip
I:Extracting updater binary 'META-INF/com/google/android/update-binary'
Detecting Current Package
I:Zip does not contain SELinux file_contexts file in its root.
/tmp/updater: line 37: /data/adb/magisk/util_functions.sh: No such file or directory
/tmp/updater: line 39: install_module: command not found
Updater process ended with ERROR: 127
I:OrangeFox: installed standard zip: /sdcard/Download/BCR-1.19-release.zip
I:flash_zip: installer code = 0
Error installing ZIP file '/sdcard/Download/BCR-1.19-release.zip'
Updating partition details...
I:Data backup size is 7780MB, free: 83242MB.
I:Can't probe device /data/media/0
...done
I:Set page: 'flash_done'
I:operation_end - status=1

@chenxiaolong
Copy link
Owner

Thanks for the logs! Can you post a link to the custom recovery you're using?

Right now, BCR checks if /sbin/recovery exists to determine whether to do a direct install or a Magisk install. It seems that your custom recovery doesn't have /sbin/recovery, so it's incorrectly trying to install as a Magisk module.

@chenxiaolong chenxiaolong self-assigned this Sep 6, 2022
@chenxiaolong chenxiaolong added the bug Bug in BCR itself label Sep 6, 2022
@errwnd
Copy link
Author

errwnd commented Sep 7, 2022

Hi , here is the link to the chat in telegram
https://t.me/realme7ProOfficial/503587
And here is the link from the post
https://drive.google.com/drive/folders/12sWsNYlBKGrY3Txf82zO9hBjjXAJv_HX?usp=sharing

chenxiaolong added a commit that referenced this issue Sep 7, 2022
@chenxiaolong
update-binary: Also perform a direct install if /system/bin/recovery …
f122fcf 
…exists

Fixes: #131

Signed-off-by: Andrew Gunnerson <[email protected]>
@chenxiaolong chenxiaolong mentioned this issue Sep 7, 2022
Merged
@chenxiaolong
Copy link
Owner

chenxiaolong commented Sep 7, 2022 •
edited
Loading

Thanks for the links. Looks like that recovery image uses /system/bin/recovery.

Can you give this debug build a try? (If it still doesn't work, please grab the /tmp/recovery.log again)
BCR-1.19.r5.gf122fcf-debug.zip

@errwnd
Copy link
Author

errwnd commented Sep 8, 2022

Hello, Thanks for the build. This one works perfectly. 😁

@chenxiaolong
Copy link
Owner

Great! I'll release version 1.20 tomorrow with the fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chenxiaolong chenxiaolong

Labels
bug Bug in BCR itself
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

update-binary: Also perform a direct install if /system/bin/recovery exists chenxiaolong/BCR
2 participants
@chenxiaolong @errwnd