-
Notifications
You must be signed in to change notification settings - Fork 5
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.
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
Rumors of devices still getting ufs wiped? #1
Comments
Don't try, you will erase ufs, the device in the picture has turned brick |
I wouldn't doubt it. It doesn't look like much in this one has changed compared to the Pixel3XLDev repo. There are things I have heard that can be why the ufs is being bricked, such as the ufsstor.sys driver in the Windows install.wim causing the ufs to wipe, or that removing a line in the dsdt can fix it. I want someone who is willing to test removing the ufsstor.sys driver and trying to install windows using edk2 on the pixel 3. Also, maybe something that could work in theory is trying to boot from usb after getting usb working, or we could try using some windows pe script that can load a desktop environment, because windows pe works perfectly fine. |
Heya, I've got a pixel 3 XL that I'm willing to use for test purposes! Lemme know if you're interested! |
Hey, I have not tried this repo yet, but that is because I don't have my Pixel 3 yet, and I have been told about devices still getting bricked using edk2 ports for the Pixel 3. Is there some issue that you might know of that causes these devices to be ufs wiped? If so, how can we fix it? I don't want to get my Pixel 3 and brick it due to a driver issue or bug.
Thanks in advance!
The text was updated successfully, but these errors were encountered: