I have the Verizon Pixel XL and can now toggle the oem unlock switch in developers settings. Annoyed with the "grey out" I have done several things to make the switch useable. Well... Something worked. Now it's time to figure out what did the trick.
Solved. Using a root file explorer, got to /data/system/users/ 0.xml Open it up and edit it to reflect no restrictions. Or clone mine, might wanna remove my name though.. One requirement for this to work, all testing shows it will not work on stock kernel. Not sure if its a selinux issue or not but the modified ElementalX I made does boot up permissive and removes forceencryption. And using it Confirmed working..
I am decrypted and running permissive. All done through kernel editing. Not sure that made a difference or not but did notice any changes beforehand.
So you added the supercid through the kernel editing?
blueyes said:
I am decrypted and running permissive. All done through kernel editing. Not sure that made a difference or not but did notice any changes beforehand.
Click to expand...
Click to collapse
Sorry to be a bit off-topic but do you plan to document how you did the decrypt and permissive mode anywhere?
I'm guessing one of the unlock properties is what did it. I think something on the phone is recognizing it as a VZW model and is setting one of the properties to 0 and graying it out. I'll do some digging this weekend
dualityim said:
Sorry to be a bit off-topic but do you plan to document how you did the decrypt and permissive mode anywhere?
Click to expand...
Click to collapse
To decrypt you must fastboot format userdata. Flash a kernel the does NOT force encryption. Don't know if any are available so I edited the radial my self , on both kernel and boot-to-root images. To run permissive you simply add androidboot.selinux=permissive. I can upload the edited images later if your unfamiliar with modifications
jjayzx said:
So you added the supercid through the kernel editing?
Click to expand...
Click to collapse
Just added it to the kernel cmdline
blueyes said:
Just added it to the kernel cmdline
Click to expand...
Click to collapse
Thanks. I'll be back in a moment.
Update: It didn't work that way. Trying something a little different.
Update 2: Managed to change cid but still 0 for unlock support and grey. Going to try 1 more thing.
jjayzx said:
Thanks. I'll be back in a moment.
Update: It didn't work that way. Trying something a little different.
Update 2: Managed to change cid but still 0 for unlock support and grey. Going to try 1 more thing.
Click to expand...
Click to collapse
The kernel cmdline has to be edited before flashing. Try adding the persist.sys.oem_unlock... Line. Before run su , then set enforce 0
Why is being able to toggle it a big deal? If your unlocked then why does that matter ?
Rootuser3.0 said:
Why is being able to toggle it a big deal? If your unlocked then why does that matter ?
Click to expand...
Click to collapse
Who said it was a big deal. I clearly stated in op that it annoyed me. If you've got nothing positive to say then don't say anything.
blueyes said:
Who said it was a big deal. I clearly stated in op that it annoyed me. If you've got nothing positive to say then don't say anything.
Click to expand...
Click to collapse
And it's not just about being greyed out. I can now lock my bootloader and unlock it without any exploits. Simply using fastboot. Which sir, I do find to be a nice feature...
blueyes said:
Who said it was a big deal. I clearly stated in op that it annoyed me. If you've got nothing positive to say then don't say anything.
Click to expand...
Click to collapse
I never said you said" it was a big deal" I said that. Go kick rocks
I lost my ability of changing the cid but then i remembered it was after i had did the supercid. So when i put them both back my cid is now changed but my unlock support is still 0. I tried adding persist to default.prop but it didn't take or i did it wrong.
blueyes said:
To decrypt you must fastboot format userdata. Flash a kernel the does NOT force encryption. Don't know if any are available so I edited the radial my self , on both kernel and boot-to-root images. To run permissive you simply add androidboot.selinux=permissive. I can upload the edited images later if your unfamiliar with modifications
Click to expand...
Click to collapse
Did you do the kernel command on the phone? How do I edit default. Prop? I feel like that's where the transformation takes place since it's not editable like the build prop
jjayzx said:
I lost my ability of changing the cid but then i remembered it was after i had did the supercid. So when i put them both back my cid is now changed but my unlock support is still 0. I tried adding persist to default.prop but it didn't take or i did it wrong.
Click to expand...
Click to collapse
Did you add the line persist.sys.oem_unlock_supported=1.
Persists seems to be equivalent to a system override
Rootuser3.0 said:
I never said you said" it was a big deal" I said that. Go kick rocks
Click to expand...
Click to collapse
Go troll somewhere else.
blueyes said:
Did you add the line persist.sys.oem_unlock_supported=1.
Persists seems to be equivalent to a system override
Click to expand...
Click to collapse
Here's my build.prop
https://www.dropbox.com/s/bxgrk7ug66jiuz1/logs.zip?dl=0
cam30era said:
Use Android Image Kitchen > http://forum.xda-developers.com/showthread.php?t=2073775
Click to expand...
Click to collapse
Ok thank you and is this done through terminal or pc
cam30era said:
There are Windows and Linux versions (which I use). There's also a mobile version, but I've never used it.. Read @osm0sis thread. Very helpful.
Click to expand...
Click to collapse
That may be over my head as far as my abilities and I hate to create a new brick
Related
AMAZON is at it again with update 13.3.2.2_user_322095220
i think we have a snitch for amazon in this forum and im pretty sure i know who it is!!!!!!
he always acts like he is going to do things to help other and then never comes through with the files and stuff that he says he is going to make for everyone and his brother just do happens to work for them!!!
http://dl.xda-developers.com/attach.../5/7/1/9/5/Screenshot_2014-03-29-09-58-38.png
Seriously... snitch? Wats the change log?
adix82 said:
Seriously... snitch? Wats the change log?
Click to expand...
Click to collapse
i would not doubt it
i dont know the change log
but i have seen two users report the 13.2.2.2 update
it could not be anything more than to mess up the work around that people have been getting away with by updating the build.prop
because when i try to change the build.prop to 14.3.2.2_user_322095220 in all the right places and try to save it the way i did before using root explorer it saves as 0 kb and is blank when i look at it.so i delete it and change the build.prop.bak file that is created when changing the build.prop back to build.prop because i am afraid to reboot with the blank one in fear of a brick
jjrizzelcincy said:
i would not doubt it
i dont know the change log
but i have seen to users report the 13.2.2.2 update
it could not be anything more than to mess up the work around that people have been getting away with by updating the build.prop
Click to expand...
Click to collapse
Would it be possible to post the build.prop file?
Thanks in advance...
sw01 said:
Would it be possible to post the build.prop file?
Thanks in advance...
Click to expand...
Click to collapse
i did not get updated.
i have mine in airplane mode
jjrizzelcincy said:
i did not get updated.
i have mine in airplane mode
Click to expand...
Click to collapse
Never mind, got the update file...Thanks!
sw01 said:
Never mind, got the update file...Thanks!
Click to expand...
Click to collapse
where did you find the file ?
jjrizzelcincy said:
where did you find the file ?
Click to expand...
Click to collapse
Go to Amazon download site and get the old link, substitute new version info...
sw01 said:
Go to Amazon download site and get the old link, substitute new version info...
Click to expand...
Click to collapse
i tried that by changing the build.prop but it would not let me it was just saving as a blank
jjrizzelcincy said:
i tried that by changing the build.prop but it would not let me it was just saving as a blank
Click to expand...
Click to collapse
Google "hdx 8.9 download"
Find the Amazon page that lets you manually download the updates
The download link points to 14.3.2.1..
Copy that link into a new browser window and edit it in two places
this is for 8.9 obviously
sw01 said:
Google "hdx 8.9 download"
Find the Amazon page that lets you manually download the updates
The download link points to 14.3.2.1..
Copy that link into a new browser window and edit it in two places
this is for 8.9 obviously
Click to expand...
Click to collapse
This Amazon page linked the download below: https://www.amazon.com/gp/help/customer/display.html?nodeId=201357220
https://s3.amazonaws.com/kindle-fire-updates/update-kindle-14.3.2.1_user_321093620.bin
What Changed?
Wonder what changed... the recovery, kernel(s) and system apps all appear to be the same. There must be some critical bugs that had to be urgently patched with this latest update coming so quick on the tail of the 13.3.2.1 update.
[Edit]Upon closer inspection, looks like there are some noticeable changes in the following apps:
WhisperlinkSdk.apk
WhisperplayActivityView.apk
WhisperplayCDSSettings.apk
WhisperplayCore.apk
WhisperplayQCSource.apk
com.amazon.communication.apk
com.amazon.tcomm.apk
[/Edit]
THANLS
I've updated 13.3.2.2, somehow opened when the machine is updated immediately so!!
I wonder if it would be possible to insert the SU binaries in this new update and then manually install it without breaking the signature
I just did a manual "Check Update" on my HDX 7 and it said no new updates, but only has 13.3.2.1.
I did sniff the traffic from the Kindle during this check and found that it contacted "softwareupdates.amazon.com" - which I now blocked in my router for what its worth.
Captured packets attached just in case they're useful.
Well crap. Blocking the server as above on my home LAN did stop the update from ever happening but I forgot to turn WiFi off at School and what do you know, 13.2.2 snuck right on in in a matter of minutes
Cevyn said:
Well crap. Blocking the server as above on my home LAN did stop the update from ever happening but I forgot to turn WiFi off at School and what do you know, 13.2.2 snuck right on in in a matter of minutes
Click to expand...
Click to collapse
Sucks.
evilgrin98 said:
Sucks.
Click to expand...
Click to collapse
Couple questions...
1. Once I stay out of the Stock rom it shouldn't update. Am I right on that?
2. If I have a rom slot with Fire OS loaded to it and in use. Can I turn on wifi and it not update?
3. I have the AOSP rom in as lot. Can I turn on wifi in this without fear of update?
Reckerr said:
Couple questions...
1. Once I stay out of the Stock rom it shouldn't update. Am I right on that?
2. If I have a rom slot with Fire OS loaded to it and in use. Can I turn on wifi and it not update?
3. I have the AOSP rom in as lot. Can I turn on wifi in this without fear of update?
Click to expand...
Click to collapse
install safestrap on both stock and rom slot one
so it will not be able to fully update it will bootloop back to safestrap according to GSLEON3
Update the hosts file on the kindle to point to localhost(127.0.0.1) or something. That might, or might not offer some help on WiFi you don't control. You'll need to still have root to do this of course.
Hi all,
I made this small update script because sometime when you try a rom and use a backup to restore the previous one the authentification get broken, so this script will just remove all locks and allow you to start your phone without any data lost.
I'm not responsible if something is going wrong.
Flash using any twrp will probably work.
great. will try
thanks!
animehq said:
Hi all,
I made this small update script because sometime when you try a rom and use a backup to restore the previous one the authentification get broken, so this script will just remove all locks and allow you to start your phone without any data lost.
I'm not responsible if something is going wrong.
Flash using any twrp will probably work.
Click to expand...
Click to collapse
well we can delete gatekeeper files manually from the TWRP file manager, and everything is fine, no data lost.
Great will try
c_/\/\_k said:
well we can delete gatekeeper files manually from the TWRP file manager, and everything is fine, no data lost.
Click to expand...
Click to collapse
Yep probably, but for most of people here it's safer to use a script than let them find the files manualy.
And maybe faster
animehq said:
Yep probably, but for most of people here it's safer to use a script than let them find the files manualy.
And maybe faster
Click to expand...
Click to collapse
you deserve compliment for your work , but it takes only one file to delete to remove passwords or lock. and its neither lengthy nor unsafe, i have seen your script, it deletes to many things.. which is not required i think. And your updater script has spelling mistakes too bro..
Does it also removes the mi account? Device locked because mi account think the device is stolen.
c_/\/\_k said:
you deserve compliment for your work , but it takes only one file to delete to remove passwords or lock. and its neither lengthy nor unsafe, i have seen your script, it deletes to many things.. which is not required i think. And your updater script has spelling mistakes too bro..
Click to expand...
Click to collapse
Which file do you think is the only one to delete?
Rohit DK said:
Does it also removes the mi account? Device locked because mi account think the device is stolen.
Click to expand...
Click to collapse
Nop sorry and there is no easy way to do it as far i know.
Bogeyof said:
Which file do you think is the only one to delete?
Click to expand...
Click to collapse
If its patternlock, then its gatekeeper.pattern.key, if its password then its gatekeeper.password.key, you can delete both.
Successful Using RX & Deletion of /data/validity/template.db
Doesn't work for me! Ran rx from recovery, wiped caches, & rebooted. Typed in backup password, unlocked (same as b4). Went to the Settings for fingerprint this time it constantly rejects any attempt saying too many incorrect pls wait. Prior it wouldn't take fingerprint or password.
Any suggestions for this?
PS: Would be nice to list what each file does /is for. I am also an advanced user...
After running This Rx use (root) X-plore/etc F. M. Then DELETE:
[*W/Rx SUCCESS*] /data/validity/template.db [*W/Rx SUCCESS*]
Reboot. Type in Previously Used BackUp Password. Go to Fingerprint Settings & setup new fingerprint & backup password!
[*MIA*] data/system/users/0/settings_fingerprint.xml [*MIA*] Could not find this file, so I assume not needed.
This was done on Stock Base Marshmallow ROM N915 (Note Edge).
BTW Thanks for RX & Could You Please add the above file to RX?
Hello everyone. Does anyone know how to set MTP automatically every time i plug my phone in? I tried in developer options but it only works one time & want it permanently. I am running the latest NBD90X Nougat Build.
Any help would be appreciated
Leeum said:
Hello everyone. Does anyone know how to set MTP automatically every time i plug my phone in? I tried in developer options but it only works one time & want it permanently. I am running the latest NBD90X Nougat Build.
Any help would be appreciated
Click to expand...
Click to collapse
You can't. It's a security measure, so others can't get all your files if you leave your phone on your desk, without first having to unlock your phone. But you can build your AOSP rom with a different default value.
istperson said:
You can't. It's a security measure, so others can't get all your files if you leave your phone on your desk, without first having to unlock your phone. But you can build your AOSP rom with a different default value.
Click to expand...
Click to collapse
Thanks, What do i have to do in order to disable this security feature if possible
Leeum said:
Thanks, What do i have to do in order to disable this security feature if possible
Click to expand...
Click to collapse
I've found it! It's in /frameworks/base/services/usb/java/com/android/server/usb/UsbDeviceManager.java
mUsbDataUnlocked always gets false when you disconnect it from the computer. If it's set to true, then it uses your preferred setting, otherwise it's set to USB charging.
istperson said:
I've found it! It's in /frameworks/base/services/usb/java/com/android/server/usb/UsbDeviceManager.java
mUsbDataUnlocked always gets false when you disconnect it from the computer. If it's set to true, then it uses your preferred setting, otherwise it's set to USB charging.
Click to expand...
Click to collapse
I'm in root browser and i can' seem to find /frameworks/base/services/usb/java/com/android/server/usb/UsbDeviceManager.java
Only folder with frameworks is in /system folder but still can't find base folder
Leeum said:
I'm in root browser and i can' seem to find /frameworks/base/services/usb/java/com/android/server/usb/UsbDeviceManager.java
Only folder with frameworks is in /system folder but still can't find base folder
Click to expand...
Click to collapse
Sorry, I wasn't more clear on this. You have to build your own AOSP, and this is the source file you have to modify.
istperson said:
Sorry, I wasn't more clear on this. You have to build your own AOSP, and this is the source file you have to modify.
Click to expand...
Click to collapse
Ahh i see. I will try look into this. Thank you tons for your help
Since Android O implements a mechanism for us to "overlay" frameworks values via OMS, I thought maybe we could leverage that to find a way to disable the OEM unlock check that block Verizon Pixels from unlocking the bootloader.
For science, let's do an experiment If this works, then great, we have a bootloader unlock method for our Verizon brethren. If not, at least the APK is easy to uninstall.
Before proceeding, be advised that any experiments performed here may result in unforeseen consequences. By proceeding, you agree that neither I nor anyone else will be held responsible for said consequences, and that this will solely be at your own risk. Since this experiment applies only to Verizon phones, assume all warranties are null and void.
Prerequisites:
- Verizon Pixel/Pixel 2/XL
- Android OS updated to 8.1.0
- USB debugging enabled on the phone
- ADB installed and properly configured on your PC
- USB-C to USB-A cable (unless you have a USB C port on your PC, then you can use a C-to-C cable instead)
How to enable the experiment:
Download the attached APK
Sideload the APK
Open Command Prompt/PowerShell/Terminal, and type in "adb shell"
Type in "cmd overlay list" and hit enter
Confirm that "[ ] com.pixeloembypass" is in the list
Type in "cmd overlay enable com.pixeloembypass", and hit enter
Reboot the phone
Go into Developer Options to see if "OEM unlocking" can now be toggled on. If so, congratulations!
If "OEM unlocking" is able to be enabled, do so, and reboot the phone into fastboot mode. Unlock as per directions on the factory images site.
NOTE: As usual, if bootloader is unlocked/relocked, a factory reset will be performed.
How to uninstall the experiment:
Open Command Prompt/PowerShell/Terminal, and type in "adb shell"
Type in "cmd overlay list" and hit enter
Confirm that "[x] com.pixeloembypass" is in the list
Type in "cmd overlay disable com.pixeloembypass", and hit enter
Go into Settings->Apps, and uninstall "Pixel OEM Bypass"
Reboot the phone
This is amazing! Will try it here in about an hour and report back
Maybe tell these guys. They've been at it for a while. You might even get the bounty.
https://forum.xda-developers.com/pixel-2-xl/how-to/temp-root-bounty-verizon-users-t3710652
TBH I have serious doubts about this working im inclined to believe this is just an overlay to make the toggle look visible but doesn't actually toggle anything when u try to push the toggle..I'll try it out in a few minutes
Sent from my iPhone using Tapatalk
djkinetic said:
TBH I have serious doubts about this working im inclined to believe this is just an overlay to make the toggle look visible but doesn't actually toggle anything when u try to push the toggle..I'll try it out in a few minutes
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
So? Come on dj! Lol
Sent from my Pixel 2 using XDA-Developers Legacy app
djkinetic said:
TBH I have serious doubts about this working im inclined to believe this is just an overlay to make the toggle look visible but doesn't actually toggle anything when u try to push the toggle..I'll try it out in a few minutes
Click to expand...
Click to collapse
have more faith.. john mccain posted it after all
Hope it works
Sent from my Pixel 2 XL using Tapatalk
PresidentMcCain said:
Since Android O implements a mechanism for us to "overlay" frameworks values via OMS, I thought maybe we could leverage that to find a way to disable the OEM unlock check that block Verizon Pixels from unlocking the bootloader.
For science, let's do an experiment If this works, then great, we have a bootloader unlock method for our Verizon brethren. If not, at least the APK is easy to uninstall.
Before proceeding, be advised that any experiments performed here may result in unforeseen consequences. By proceeding, you agree that neither I nor anyone else will be held responsible for said consequences, and that this will solely be at your own risk. Since this experiment applies only to Verizon phones, assume all warranties are null and void.
Prerequisites:
- Verizon Pixel/Pixel 2/XL
- Android OS updated to 8.1.0
- USB debugging enabled on the phone
- ADB installed and properly configured on your PC
- USB-C to USB-A cable (unless you have a USB C port on your PC, then you can use a C-to-C cable instead)
Click to expand...
Click to collapse
Have you tested this? Also what is all included in this APK? My concern is just installing random APK files that are added to a forum. Sorry, I am not trying to be a Debbie downer.
Edit:
I downloaded it on my phone just to see what permissions is calls for and it doesn't open the file.
Didn't work for me. Any tips to try?
thompatry said:
Have you tested this? Also what is all included in this APK? My concern is just installing random APK files that are added to a forum. Sorry I am not trying to be a Debbie downer.
Click to expand...
Click to collapse
u can decompile the apk lol.. pretty sure its just an overlay thats suppose to "ungrey" the oem unlock switch to allow u to toggle it.. had afew ppl trying it.. first report it didnt do anything
elliwigy said:
u can decompile the apk lol.. pretty sure its just an overlay thats suppose to "ungrey" the oem unlock switch to allow u to toggle it.. had afew ppl trying it.. first report it didnt do anything
Click to expand...
Click to collapse
Ehh I am just lazy to decompile it. Just tell everyone what's inside of it from the get go and move on from there.
I figure it wouldn't work but hey, worth the try.
thompatry said:
Ehh I am just lazy to decompile it. Just tell everyone what's inside of it from the get go and move on from there.
I figure it wouldn't work but hey, worth the try.
Click to expand...
Click to collapse
i understand lol.. when im lazy i just use a file browser n view as an archive lol
collinjames said:
Didn't work for me. Any tips to try?
Click to expand...
Click to collapse
Only thing I can think of is, after step 6, do this:
Code:
cmd overlay disable android.auto_generated_rro__
And then reboot.
To revert, just re-enable it and reboot.
If it still doesn't work, then I'm afraid the experiment failed
thompatry said:
Have you tested this? Also what is all included in this APK? My concern is just installing random APK files that are added to a forum. Sorry, I am not trying to be a Debbie downer.
Click to expand...
Click to collapse
That's okay, it's completely understandable. I agree - typically, you wouldn't want to install a random APK built by a stranger.
I wish I could test it myself, but both my Pixels are from the Google Store, and shelling out $650+ for a test device for a shot-in-the-dark experiment doesn't sound like very responsible spending.
Tried on my P2XL device and no luck..
nelsonTituaAa said:
Tried on my P2XL device and no luck..
Click to expand...
Click to collapse
Thanks for volunteering...have you gave this a try?
PresidentMcCain said:
Only thing I can think of is, after step 6, do this:
Code:
cmd overlay disable android.auto_generated_rro__
And then reboot.
To revert, just re-enable it and reboot.
If it still doesn't work, then I'm afraid the experiment failed
Click to expand...
Click to collapse
nelsonTituaAa said:
oops.. no haha.. will try again
Click to expand...
Click to collapse
PresidentMcCain said:
Thanks for volunteering...have you gave this a try?
Click to expand...
Click to collapse
tried it and still no luck.
PresidentMcCain said:
Only thing I can think of is, after step 6, do this:
Code:
cmd overlay disable android.auto_generated_rro__
And then reboot.
To revert, just re-enable it and reboot.
If it still doesn't work, then I'm afraid the experiment failed
Click to expand...
Click to collapse
Tried the command and doesn't seem like it disable android.auto_generated_rro__ on the overlay list.
tried this plus added recommendation and no luck. Verizon Pixel, 8.1
Anybody tried this on a Verizon Pixel 2? I'm willing to give it a shot, but would need a little more detail on the procedure if anyone is willing to help out.
So, as has probably been spotted in various places, Google dropped an Android Q GSI here recently.
One thing it requires (which breaks because Huawei, of course) is AVB support. Looks like init is unable to find the vbmeta image to verify and so it throws it's hands up with a "screw you, I'm going home".
Fortunately, this is relatively easy to work around - I have it booting on a Mate 9 that's been upgraded to EMUI 9, and I wouldn't be surprised if others have the same issue.
In any case, if this might be the reason why you're not booting, copy the attached file into /system/lib64 using TWRP or something.
There's other things broken on it - but that'll get it booting at least.
EDIT:
Link to patched Q GSI (GMS arm64 QPP2.190228.021):
https://drive.google.com/open?id=1dnEKJbjoiGhHuL6BLM8qXXyBFOKkE1bD
The only thing changed from the Google distributed image is the replacement of /system/lib64/libfs_mgr.so.
I will give that a try..
What are you doing for the selinux deniels?
Great, where did you install twrp as ramdisk partition in emui 9 doesn't exist anymore?
THE MAXIMUM POWER said:
Great, where did you install twrp as ramdisk partition in emui 9 doesn't exist anymore?
Click to expand...
Click to collapse
You still have the recovery partition, which can be used to flash twrp??
What works/doesn't work for you?
MishaalRahman said:
What works/doesn't work for you?
Click to expand...
Click to collapse
In the bit of playing I did, wifi to unsecured networks works, secured does nothing. Most of the apps included seem to work - but I didn't get too far into playing with it.
Can't say anything about cellular, as the device I loaded it on has a dud modem. It does read imei 1 successfully, though, so it might work on another device.
deepsrd said:
I will give that a try..
What are you doing for the selinux deniels?
Click to expand...
Click to collapse
Nothing yet. Just made sure the lib I posted was in the right place with proper permissions.
Doesn't seem to work on the Huawei Mate 10 Pro.
MishaalRahman said:
Doesn't seem to work on the Huawei Mate 10 Pro.
Click to expand...
Click to collapse
Hmm. I've heard mixed reports.
I've only tried it on the one device - MHA-AL00, EMUI 9.0.1.150 base. I figured it might be relevant to other people since there were a fair number of people on the main website post commenting on problems with AVB, which led me to that workaround.
I installed it with twrp over adb:
adb push libfs_mgr.so /tmp
adb shell
mkdir /system_root
mount -t ext4 /dev/block/bootdevice/by-name/system /system_root
cat /tmp/libfs_mgr.so > /system_root/system/lib64/libfs_mgr.so
reboot
On reboot, after a long wait (seems to take a minute to get to boot animation, that's Huawei for you), it came up to the welcome screen.
Edit - changed cp / chmod / chcon to cat, as it doesn't replace the file, keeping it's previous permissions & security label.
I think it will be better if you make a Q IMG that include the fixes
THE MAXIMUM POWER said:
I think it will be better if you make a Q IMG that include the fixes
Click to expand...
Click to collapse
Check the first post, I've added a link to the patched image.
irony_delerium said:
Check the first post, I've added a link to the patched image.
Click to expand...
Click to collapse
And now it actually booted on the Mate 10 Pro. Nice!
Does it work on devices other than huawei?
AsusZenFone3Deluxe said:
Does it work on devices other than huawei?
Click to expand...
Click to collapse
There's no reason for it not to. All that the patch I applied does is make it so that Android doesn't go looking for vbmeta information, so if that's the reason it fails to boot elsewhere this might allow it to work. If the image from Google already works, or it otherwise gets to the Android boot animation, this build won't do anything for you.
It booted on my MediaPad M5 but with no wifi, it stuck at "saved" but never mind, i just wanted to see the Q 2 beta, your fix might work as well with other unbootable roms like Pixel experience.
I really appreciate your work
THE MAXIMUM POWER said:
It booted on my MediaPad M5 but with no wifi, it stuck at "saved" but never mind, i just wanted to see the Q 2 beta, your fix might work as well with other unbootable roms like Pixel experience.
I really appreciate your work
Click to expand...
Click to collapse
Yeah, I've only been able to connect to unsecured networks. Pretty sure that's HAL changes in Q to blame.
irony_delerium said:
Yeah, I've only been able to connect to unsecured networks. Pretty sure that's HAL changes in Q to blame.
Click to expand...
Click to collapse
Ohh, thank you for the hint, btw any way to install your mod through fastboot mode as MediaPad M5 doesn't have a good TWRP?
Thank you in advance
THE MAXIMUM POWER said:
Ohh, thank you for the hint, btw any way to install your mod through fastboot mode as MediaPad M5 doesn't have a good TWRP?
Thank you in advance
Click to expand...
Click to collapse
I don't know about using it on Pie builds - init on Q is dynamically linked, on Pie it's a static binary, so you'd have to patch /init to make that change. Whether it would help or not, I don't know.
MishaalRahman said:
And now it actually booted on the Mate 10 Pro. Nice!
Click to expand...
Click to collapse
Did you have to do any other than what's instructed? Id like to take it for a spin.
Also, unrelated, what's with some of our "avatars" are green while others yellow?
I'm pretty sure @fullofhell was looking for an actual bootable build, and not just hear say.
culiacanazo said:
Did you have to do any other than what's instructed? Id like to take it for a spin.
Also, unrelated, what's with some of our "avatars" are green while others yellow?
I'm pretty sure @fullofhell was looking for an actual bootable build, and not just hear say.
Click to expand...
Click to collapse
Haha yeah Bro i tried this yesterday thanks tho