GearLock - Custom Recovery Replacement for Android-x86

Software GearLock - Custom Recovery Replacement for Android-x86 7.3.15

MrMiy4mo

Well-known member

Attachments

  • Screenshot_2020-06-27-18-26-39.png
    Screenshot_2020-06-27-18-26-39.png
    18.7 KB · Views: 336

AXON

Supreme
Moderator
Blog Author
I'm using Android x86 4.4 r5 now (testing) and I'm trying to install gearlock 6.3 on it,
but it failed when gearlock trying to patch the secondary ramdisk.

do you have a suggestion or maybe a workaround on how to fix this?
I'm sorry if i'm doing something useless here.
Try 6.2, Click on the RELEASES tab to get it. And worth mentioning, I havent tested GL below android murshmellow.
Post automatically merged:

just read *Add PhoenixBR support in the installer, thanks for port this worndeful tool to the other versions, i have some pc that dont support sse 4.2 with 32 bits android, before tried install it and no luck , i wonder if some features can be ported to anbox , i got some games working there but need a maping tool and more, although anbox support and develop is poor , just a caprice lol
What error did you get while installing ?
 

Hunter.1014

New member
VC
18
after installing this gearlock my system is not supercharged. When I supercharged my system that going in 99% and cool down and restart my system. How I can solve this problem.
 

kuro_sk

New member
VC
84
Try 6.2, Click on the RELEASES tab to get it. And worth mentioning, I havent tested GL below android murshmellow.
Post automatically merged:


What error did you get while installing ?
hello:
1|x86_64:/data $ su
x86_64:/data # chmod +x gearlock
x86_64:/data # ./gearlock
Loading ...
tar: exec gunzip: No such file or directory
tar: read error
base64: Broken pipe
tail: xwrite: Broken pipe
screenshot.3.png
i think is only possible modify system files by building a new anbox image , i cant even change hosts file on a rooted image
 

yami

New member
VC
2
hi, please help, im using old phoenix os, version 2.1.1 can i use this gearlock? im tried but stuck at phoenix logo after apply fix unity game
 

bhargavakul

New member
VC
2
please help
stuck here in prime os please help.after partition selection
 

Attachments

  • 15972011474119115077594831518119.jpg
    15972011474119115077594831518119.jpg
    220.3 KB · Views: 346
Last edited:

X22396

New member
VC
12
Hello all, i am total noob hear. Probably know just enough to be dangerous.

I tried to install v6.3 to my BlissOS CarbonROM. My system is uEFI and i have a EFI partition, and an AndroidOS partition.

When i install v6.3 i am getting this error:
20200820_070106.jpg

Something about not detecting ramdisk.img
(Same error if i select 1)

I saw your notes regarding v6.3 and uEFI, so I downloaded v6.2, but getting the same error. (Screenshot from v6.2)

I can see the drive with the Android OS folder, and all the other .img files (data.img, etc...) and there is no ramdisk.img file. Could I just create a dummy file called ramdisk.img? Does it have to be a certain size?

Also,
Up until i run this, my system is very stable, (i know beta builds, etc...) after just running ./gearlock from the terminal, if I later try to reboot, the system starts acting up and eventually have to hard reset to reboot.

In case its an issue with ntfs, I will reinstall BlissOS on ext4 and retry. I will also try another version of Androidx86 OS as well. (but I like that I have Android 10/Q on my PC)

But is there anything else that could be the issue?

Thanks for all your work on this project.
 

AXON

Supreme
Moderator
Blog Author
Hello all, i am total noob hear. Probably know just enough to be dangerous.

I tried to install v6.3 to my BlissOS CarbonROM. My system is uEFI and i have a EFI partition, and an AndroidOS partition.

When i install v6.3 i am getting this error:
View attachment 482
Something about not detecting ramdisk.img
(Same error if i select 1)

I saw your notes regarding v6.3 and uEFI, so I downloaded v6.2, but getting the same error. (Screenshot from v6.2)

I can see the drive with the Android OS folder, and all the other .img files (data.img, etc...) and there is no ramdisk.img file. Could I just create a dummy file called ramdisk.img? Does it have to be a certain size?

Also,
Up until i run this, my system is very stable, (i know beta builds, etc...) after just running ./gearlock from the terminal, if I later try to reboot, the system starts acting up and eventually have to hard reset to reboot.

In case its an issue with ntfs, I will reinstall BlissOS on ext4 and retry. I will also try another version of Androidx86 OS as well. (but I like that I have Android 10/Q on my PC)

But is there anything else that could be the issue?

Thanks for all your work on this project.
Hi, GearLock 6.3 installer had an issue with uEFI systems. There are ongoing public betas for 6.4 at our discord server but it's not released here yet.
Join our discord server from this link https://discord.gg/sJuRqK5 and look at #gdk-discussion channel to get the 6.4 beta. It should work fine on blissOS hopefully.
 

X22396

New member
VC
12
Hi, GearLock 6.3 installer had an issue with uEFI systems. There are ongoing public betas for 6.4 at our discord server but it's not released here yet.
Join our discord server from this link https://discord.gg/sJuRqK5 and look at #gdk-discussion channel to get the 6.4 beta. It should work fine on blissOS hopefully.

Ok, thanks for the Discord invite. I have dl'd v6.4.11, It installed fine. No ramdisk.img error.
20200820_090148.jpg


However, when i boot, recovery option just boots normal, and no GearLock icon for the app. I do see both FX file mgr, and FX TextEditor icons showed up. And system seems stable, no lockup or anything odd.
 

AXON

Supreme
Moderator
Blog Author
Ok, thanks for the Discord invite. I have dl'd v6.4.11, It installed fine. No ramdisk.img error.
View attachment 483

However, when i boot, recovery option just boots normal, and no GearLock icon for the app. I do see both FX file mgr, and FX TextEditor icons showed up. And system seems stable, no lockup or anything odd.
Do you get a terminal screen on pressing ALT+F8 ?
Post automatically merged:

@X22396 by the way, is your blissOS CarbonRom android10 ?
 
Last edited:

X22396

New member
VC
12
Oh well, I couldn't test on android-10 blissOS as it won't boot for me. So can't do much about android 10 for now.

No worries, not critical, get to it when you can. I know ej is working on it as well, he suggested i update you of my issues. Progress is being made. Thanks for all your efforts.
 

Similar threads

Similar threads

Get Connected

Discord Server

New Threads

Top