BLU R1-HD bootloader unlock script tool, and TWRP install tool.
Download is a zip file, unpack it to somewhere you will remember. Run the dirty-cow-tool.bat // mtk-su-tool.bat
The included files and folders are set to hidden, in effort to keep them safe from accidental delete.
Must have adb+fastboot + drivers installed and setup prior to using tool
Easiest method to install adb + fastboot on windows is with "15 second adb + fastboot install TOOL"
LINK==>ADB+FASTBOOT
It is for windows
In linux :
"sudo apt-get install android-tools-adb"
"sudo apt-get install android-tools-fastboot" Some fastboot commands were missing when i used this one ie "fastboot flashing get_unlock_ability"
"sudo apt-get install fastboot" worked better when I tried. ( i used that command as a check before doing the unlock, so it was needed only for that check)
Using Tool
On Windows?
Unzip the downloaded file to a new folder, open new
folder and click on "dirty-cow-tool.bat". // "mtk-su-tool.bat"
Do the steps in order (1-2-3-4) to be unlocked, then
Step (5) to get to second page where step (1) is root
The rest is optional
On Linux?
Unzip downloaded file to new folder folder .
Open folder. Then open R1-Linux-tool-v2 folder
Open terminal from that folder and type
" . R1-HD-TOOL.sh "
Same order of steps (1,2,3,4) step (5) for extra
Steps (1 on second menu) for superSU root.
Second menu steps (2,3,4,5,6,7,8) are optional.
**Linux Note**
The tool uses "fastboot flashing get_unlock_ability" as one of the methods to check before doing the unlock.
The version of fastboot that installed with "apt-get install android-tools-fastboot" did not recognize
this command. But "apt-get install fastboot" updated some version and then the command was recognized.
******OTHER NOTES****
--- this has been mentioned in the general thread and the modified v17 thread, but It has come up again so I wanted to make note of it.----
--- The newest blu versions (V7.4.2 and V17) Have made changes to "toolbox" and this effects things like "adaway" and "titanium backup"
--- The suggested fix is to install busy-box. I have had success with the version from play store, some prefer to use f-droid version. Either one will do. Install it and open the app. From in the app you need to do an install.
CHANGE LOG
V1:. Initial release : removed
V2:. : fixed typos preventing proper function
V3:.: switch file verification to md5 check instead of "ls-l" comparison.
V4: current version: add extras page, add SU flash, de-bloat script, Added Fm Radio, Added pre-loader roll back
V5: Fixed wrong loop "goto" line that made preloader rollback do "MTK_BLU Debloat v2" instead
V6: Added manual pause to script for mods that need recovery (Extra's 5) . Added redundent recovery flash command .
Few reports of recovery "not Sticking" and needed to run the flash commands manually one by one. Maybe the redundent
flash will make it survive. If still having problem with recovery "staying install" try manually flashing
here is link to the steps needed. FLASH RECOVERY
V7 Improved logs Added line to make batch run as sub-process so if error occurs , will not close
V7.1 : Updated the fm radio install zip and include the needed selinux mode changer app
V8: fixed dependency of needing to be unzipped to location w/o spaces in name. (when used from location with spaces, tool used to fail to push needed files).
.. added more time to allow dirtycow to "spawn" its root shell. Recent testing has shown sometimes it takes longer than the 60 seconds allowed in the script. Now it is looped 3 times.
V9 Added full path to abd push lines for recovery flash files. included fastboot.exe file to address some version issue where user s version would not output text file I coded into script for a verification ( included file is called by script, no need to do anything different with it)
V10: Moved zip file to included folder to help preserve locations when unpacked, added device check before running tool; So tool not used on wrong device, Rearranged order of operations on extra's page. (recovery installed options) Push files while in android before rebooting to recovery( should improve reliability for multiple reports of not automatically installing options for some)
******I have received some reports that some devices are reporting "ro.build.product =R1_HD and not "BLU_R1_HD" like mine, so the added device check is blocking tool from starting If this happens to you , you can make edit to the .bat file like below.
Change this line
Code:
:next_check
find "BLU_R1_HD" "%~dp0workingproduct.txt"
To this
Code:
:next_check
find "R1_HD" "%~dp0workingproduct.txt"
it is line #23
V11: Updated device model verification lines
MTK-SU: Replaced all dirty-cow part with New MTK-SU binary(elf) from @diplomatic
source
Click to expand...
Click to collapse
Credits to @Diplomatic for his work on the Mtk_su that I used used to make this tool work again after Dirty-Cow was patched.
DOWNLOAD LINK
Preferred to use the Downloads tab of this thread.
Archived downloads on android file host also == link
XDA:DevDB Information
R1-HD Dirty-cow Unlock Tool, Tool/Utility for the BLU R1 HD
Contributors
mrmazak, vampirefo for his recovery, lopestom for his recovery, emc2cube for his debloat zips, christianrodher for his dirtycow method,
Source Code: https://github.com/mrmazakblu/DirtyCow-R1_HD
Version Information
Status: Testing
Current Stable Version: V11
Stable Release Date: 2017-04-11
Current Beta Version: MTK-SU
Beta Release Date: 2019-04-14
Created 2017-02-22
Last Updated 2019-04-18
Reserved
Items planed to be addressed in next release:
--Add few more file integrity checks to the extra's page
--Add copy log to clipboard option so it is easier to post log entry if needed-------*********----already-_added to github copy of batch file
--Add a verification step that checks what recovery is installed( to prevent trying to do steps on extra's page with stock recovery)
--Possibly move to a "fastboot boot recovery" instead of "adb reboot recovery" for the same reason as above
--Add wget or similar to the extra's items so initial "TOOL" size is smaller (not that 40-50MB is big, but to some it may be )
--Add additional "selinux mode changer apk" for fm radio install rather than just the note that says it needs to be found.
Reserved
Works great on OEM 6.6, thanks for the tool!
So I got the one-click-root.sh done, maybe. Can some linux users go over it, make sure I didn't do anything stupid? I don't exactly have a device to check it with atm, and I am not pro with scripting, barely novice, so it is a pretty basic conversion of the batch file. Still, it might work . Just would like a few eyes on first.
https://github.com/theredbaron1834/Scripts/blob/master/one-click-root.sh
Also, I looked at dirty-cow-tool.bat. However, wow, more an advanced batch file, and I am not sure what the first half does, so not sure how to convert . However, it seems if anyone does get it, the eqiv of goto for linux is funtions. simple cheatsheet:
Code:
function stuff {
echo "this stuff is run via the function"
{
stuff #goes to stuff and runs function
theredbaron1834 said:
So I got the one-click-root.sh done, maybe. Can some linux users go over it, make sure I didn't do anything stupid? I don't exactly have a device to check it with atm, and I am not pro with scripting, barely novice, so it is a pretty basic conversion of the batch file. Still, it might work . Just would like a few eyes on first.
https://github.com/theredbaron1834/Scripts/blob/master/one-click-root.sh
Also, I looked at dirty-cow-tool.bat. However, wow, more an advanced batch file, and I am not sure what the first half does, so not sure how to convert . However, it seems if anyone does get it, the eqiv of goto for linux is funtions. simple cheatsheet:
Code:
function stuff {
echo "this stuff is run via the function"
{
stuff #goes to stuff and runs function
Click to expand...
Click to collapse
thank you for your input.
As far as the begining of the batch, It is adding a few folders to the "path" variable so help ensure the "adb push" commands find the files it is trying to push. Then it sets some folder "flags" to hidden so that the files the batch needs don't get accidentally moved or changed. Then the large section with mostly "echo" that is to set up the "simulated" G.U.I.
The lines of just "::::::::::" are simply used to help with reading the batch file. i use them to seperate functions. They are not needed.
The lines with only 2 "::" are standard windows comment / remark line entries
The lines with 1 ":" are the beginning line of the loop/ function == the line that "goto *" searches for
Does Works to unlock 7.4.2?
khyr said:
Does Works to unlock 7.4.2?
Click to expand...
Click to collapse
It is supposed to. It is the same base codes used from original script, and that one was confirmed to work. I Do not have first hand use of V7.4.2 so it is only confirmed through other users.
The dirty-cow being used has been patched by google in Dec but blu has not rolled out the patch. So there is no reason for it not to work.
edit:
I have the linux version ready.
-the first step, (ADB Push) is ready. including md5 file checks
-step 2 is ready= running dirty-cow with md5 check before final writing to mmcblk device
-step 3 is ready unlocking bootloader = including check if unlock is done, but need to fix the "unlock_adility" check
I can make to file to compare and grep the line needed, but cannot "sed" the extra information or do a > < comparison
-step 4 is ready .--flash twrp
Finished 90% of tool.
still need to tweek the log feature.
I ran tests on the lop back to menu and test ran
1. push files for dirty-cow and md5 check . then made push fail to verify the check method was valid ==pass
2. run dirty cow commands and md5 verification on resulting file. ==pass
3.unlock bootloader --- I ran it (needed to fake the already unlocked check) it works == pass
4 . flash twrp --installed both version i have, both install fine ===pass
5 extra menus -- ran . install su-----debloat---rebloat--- add fm radio--- preloader roll back =====all pass
(bootloader roll back needs manual intervention to re-enter fastboot during the boot loop that is unavoidable)
6. instruction ====not written yet
7. exit yes it closes == pass
8. logs --- needs completeing
I just loaded this on my OTA updated 7.4.2 device. I would note that the batch file does not actually create the /sdcard/Download folder so you might need to go into the terminal and actually create this on your sdcard... also worth noting that this batch file **requires** an sd card in the device to do any of the loads in the "5" menu.
torchredfrc said:
I just loaded this on my OTA updated 7.4.2 device. I would note that the batch file does not actually create the /sdcard/Download folder so you might need to go into the terminal and actually create this on your sdcard... also worth noting that this batch file **requires** an sd card in the device to do any of the loads in the "5" menu.
Click to expand...
Click to collapse
no it does not.
the /sdcard is the internal memory and the Download folder is already there.
you might be having issues but the folder is already part of normal system
mrmazak said:
no it does not.
the /sdcard is the internal memory and the Download folder is already there.
you might be having issues but the folder is already part of normal system
Click to expand...
Click to collapse
Fair enough, my restore didn't have /sdcard/Download and I made an assumption that /sdcard was my mounted card. Thanks for the insight.
OOPS
found typo on V4 of tool. batch files sets variables for "return", from loop functions. And two returns were set to same label9, so if you had tried to do extra's menu option #8. "ROLL Back Preloader" , instead it was running option # 5. " MTK_BLU Debloat v2"
fixed and still reading and re-reading to search for errors.
This looks bad.
The reason I put together this tool was I felt it was important to make a way to minimize the problems usually associated with android modifications. By making "typo's" a thing of the past, and I found them in my own script.
re-posted V5 combined with linux V2--
torchredfrc said:
I just loaded this on my OTA updated 7.4.2 device. I would note that the batch file does not actually create the /sdcard/Download folder so you might need to go into the terminal and actually create this on your sdcard... also worth noting that this batch file **requires** an sd card in the device to do any of the loads in the "5" menu.
Click to expand...
Click to collapse
I'm a total noob, and I'd like to know how to proceed with the supersu and all the other parts of step 5. Thank you
gabriel986 said:
I'm a total noob, and I'd like to know how to proceed with the supersu and all the other parts of step 5. Thank you
Click to expand...
Click to collapse
Ok. After you have completed upto twrp install. You can do the options on #5. It is all programed and automatic. What is does is put zip files onto the phone and reboots phone into recovery, then recovery installs them.
mrmazak said:
Ok. After you have completed upto twrp install. You can do the options on #5. It is all programed and automatic. What is does is put zip files onto the phone and reboots phone into recovery, then recovery installs them.
Click to expand...
Click to collapse
I get up to the recovery installation, but then I can not access such recovery on the phone, If I turn it on with power+vol up, it takes me to the default factory recovery by blu.
And If I try to the super su step with the phone on, it resets it, and get it to the screen with the dead android, while the script just shows the ADB DETECTED message.
In case it's needed, my R1 HD is running on
BLU_R0010UU_V7.4.2_GENERIC 09-11-2016 13:38
gabriel986 said:
I get up to the recovery installation, but then I can not access such recovery on the phone, If I turn it on with power+vol up, it takes me to the default factory recovery by blu.
And If I try to the super su step with the phone on, it resets it, and get it to the screen with the dead android, while the script just shows the ADB DETECTED message.
Click to expand...
Click to collapse
You missed a step in the process.
As tool finishes the recovery install it comes to a "pause" in the script, you need to hold the volume up button on phone "before" pressing button on pc keyboard to continue.
If phone does a normal reboot at this point then the system will replace the newly installed recovery with the stock one.
Giving you the situation you have now.
This step I cannot control, you must press volume button on phone to get the boot menu, and directly boot into recovery to ensure that the install sticks.
mrmazak said:
You missed a step in the process.
As tool finishes the recovery install it comes to a "pause" in the script, you need to hold the volume up button on phone "before" pressing button on pc keyboard to continue.
If phone does a normal reboot at this point then the system will replace the newly installed recovery with the stock one.
Giving you the situation you have now.
This step I cannot control, you must press volume button on phone to get the boot menu, and directly boot into recovery to ensure that the install sticks.
Click to expand...
Click to collapse
trying again....
for how long should I press the volume up key?
gabriel986 said:
trying again....
for how long should I press the volume up key?
Click to expand...
Click to collapse
When tool says Hold button , keep it held. Then continue the script. Phone should reboot to the boot menu. Then let go of volume
Some phones do not accept the fastboot reboot command, on those phones need to hold power to shut off. Then volume and power together to come on, release power when screen come on
mrmazak said:
When tool says Hold button , keep it held. Then continue the script. Phone should reboot to the boot menu. Then let go of volume
Some phones do not accept the fastboot reboot command, on those phones need to hold power to shut off. Then volume and power together to come on, release power when screen come on
Click to expand...
Click to collapse
ok.. trying again
---------- Post added at 02:00 PM ---------- Previous post was at 01:46 PM ----------
gabriel986 said:
trying again....
for how long should I press the volume up key?
Click to expand...
Click to collapse
it beat me!
I get stuck in that part of the process, If anyone uploads a video to check what i'm doing wrong, I'll be grateful.
I am noob at this, I need to reflash my current version 8.0 Oreo but i never done it, can someone explain me step by step what I must do.
Loco56 said:
I am noob at this, I need to reflash my current version 8.0 Oreo but i never done it, can someone explain me step by step what I must do.
Click to expand...
Click to collapse
I'm assuming you're talking about the original stock rom?
Download the Android SDK Platform-Tools; (I'm assuming you're using Windows)
1. Click -- SDK Platform-Tools for Windows
2. Unzip and put the SDK Platform-Tools for Windows anywhere you like.
https://developer.android.com/studio/releases/platform-tools.html
On the Mi Community forum link below you'll download the Oreo ROM;
Click the link below: Fastboot ROM | 1407M |8ea503201bb0b594e02e5ed2bf6dea09
http://c.mi.com/forum.php?mod=viewthread&tid=657275&extra=page=1
You need an Archive Tool like 7-Zip to extract the rom. Make sure in the 7-Zip options you have tar and tgz checked, so you can extract it.
https://www.7-zip.org/
.tgz is a tar archive with gzip compression added to it. When you click to extract it the first time, you'll now end up with a .tar archive, click to extract it again, and you'll finally have the contents of your rom, in two directories called;
tissot_images_8.1.10_20180110.0000.00_8.0_8ea503201b
tissot_images_8.1.10_8.0
Copy the contents of tissot_images_8.1.10_8.0 to your C: drive. Make sure you copy the contents, not the directory itself to C:
On MIUI forum read the Steps 1, 3, 4, 5 SKIP STEP 2! Be sure to download the Mi Flash Tool, Step 1.
http://en.miui.com/thread-807252-1-1.html
Step 3 on the MIUI forum, place the phone in Fastboot Mode.
Next go to the directory you extracted the Android SDK Platform-Tools, in that window hold down the Shift-key and Right-Click, when the menu pops up, click on Open command window here. Now you have a command prompt open.
1. Type in the command prompt - fastboot.exe devices
If successful you'll see a number displayed in the prompt for your phone.
2. Next you need to unlock the bootloader so type - fastboot.exe oem unlock
Now you're ready to flash it.
Open the Mi Flash Tool, make sure to the right of where it says select you put the path, which is C:\
Now click refresh and it should show the device like the screen shot on the MIUI forum, and then make sure clean all and lock is checked on the bottom right of the Mi Flash Tool.
Now click flash and wait...
Enjoy
Is this rom same
http://en.miui.com/getrom-333.html?m=yes&mobile=2
A Myth said:
http://en.miui.com/getrom-333.html?m=yes&mobile=2
Click to expand...
Click to collapse
Go to both URLs, copy the download links, paste them in Notepad and compare them...
http://c.mi.com/forum.php?mod=viewthread&tid=657275&extra=page=1
First, to clarify, the last time I rooted anything was a Galaxy S3 back in the day. I'm by no means an expert, I just figured I'd help out folks like me that haven't touched all these new tools, well, ever.
Just did this myself earlier today attempted to get Magisk root, but alas, I got stuck in a boot loop. Luckily I had muddled through getting the image first, otherwise I'd still be stuck in said boot loop. I figured I'd post this for anyone else trying to root these things just to make sure you have a backup you can trust (I generally don't trust rando images that folks post online). All of the instructions below are assuming you're on Windows 10 and using PowerShell just because that's the default these days. Without further adieu.
Download ADB/fastboot (on your Windows machine)
I downloaded adb/fastboot from google directly: https://developer.android.com/studio/releases/platform-tools
Just extract and browse to the platform-tools directory in Windows Explorer until you can see adb.exe and a bunch of other tools
Download the latest SP Flash Tool
I just grabbed it from here: https://spflashtools.com/
Please let me know if there's an "official" place to find SP Flash Tool, cause everything surrounding all the download sites seems a bit sus...
Enable USB Debugging (on the tablet)
Go to settings -> About tablet
Tap the Build number 10 times (until debugging mode unlocks)
Hit back and go to System
Click Advanced and then Developer Options
Enable USB Debugger
I also enabled OEM unlocking because the whole point of this is for me to run either AOSP or Lineage someday. I honestly don't know if unlocking the bootloader is needed for dumping your own images, but I highly suspect it's not.
Plug the tablet into your computer
You'll likely see a prompt on your tablet about allowing your computer to debug your tablet. I just checked the box and hit accept so I wouldn't see it again.
Get your scatter file (on your Windows machine)
I tried several things to get the scatter file (I guess this is like a partition table based on the contents I saw) but in the end, by far the easiest way was to just download the scatter file from the file system.
In the Windows Explorer window from before (platform-tools), hold down shift while left clicking and click on Open PowerShell window here
Now type the following to get a shell on your:
.\adb.exe shell
This will get you into the shell environment. Now type the following to verify your scatter file is there:
ls -al /system/data/misc/
In here you should see something like:
-rw-r--r-- 1 root root 13893 2008-12-31 19:00 MT8168_Android_scatter.txt
Now that we have the name, just type exit to get out of the shell
Download the scatter file
.\adb.exe pull /system/data/misc/MT8168_Android_scatter.txt
Open up the scatter file in your favorite text editor (for me, Notepad++)
Now you can see the partition layout, offsets, etc, etc
Dump your image(s) (on your Windows machine)
Now open SP Flash Tool (flash_tool.exe)
On the Download tab, make sure the Download-Agent is MTK_AllInOne_DA.bin
Now click Choose for the Scatter-loading file and browse to the scatter file you just downloaded
This should be in your platform-tools folder unless you moved it
Once the scatter file is loaded, the partition table should fill up with a bunch of partitions
Click on the Readback tab
Click Add
Double-click on the new entry
Navigate to where you want to save your image, and give it a name (in this case I'm starting with boot.img)
Remember how you opened the scatter file in a text editor? Search in the scatter file for boot.img
Make sure the region matches (should be EMMC_USER) between the scatter file and SP Flash Tool
Copy/paste the value for start_addr in the scatter file to Start Address in SP Flash Tool
Copy/paste the value for partition_size in the scatter file to Length in SP Flash Tool
Now do the same thing for recovery.img and any other images you'd like
If you want a full ROM backup, name the file something like ROM_0, then use Start Address of 0x0 and length as the start_addr for the second-to-last entry in the scatter file (in my case, it was 0xc1a80000, just make sure it doesn't start with f's)
Note: I don't know for sure if this is accurate or not, I'm still playing with it, but so far it appears to be. Probably?
Poking around in WwR MTK 2.51, it looks like for this particular device (100011885) I wanted a total dump of 0x73A000000. It looks like this number is derived from the first 8Mb of the EMMC_USER dump, so I'm not sure of an easier way than throwing WwR MTK at it for the moment.
Once you've got all the entries for what you'd like to dump, make sure to disconnect the tablet from your computer and power it off
Now click on Download in SP Flash tool
Once things grey out, then plug the tablet in. After a few seconds, you'll see the images start dumping.
Congrats, you have a boot.img (and whatever other images you wanted). Like I said, from here I tried using Magisk to patch the boot file, but when I flashed it in fastboot, after enabling OEM unlocking in Developer Options, it just kept popping up the initial Onn graphic along with the Orange State warning without getting to the "fancy" Onn graphic and the rest of the boot process. I was able to flash the original boot.img back and it once again booted properly again.
Also, for anyone interested, I've posted my dumped files for the 100011885 in my google drive: https://drive.google.com/drive/folders/17LtLtjKg4JJU9EJdIXPsyNjen0H-ilMX?usp=sharing
Maybe someone will have pity on me and figure out why Magisk isn't working?
Whenever I get a moment, I'll dump my 100003562 as well.
First, thanks a ton for this. I have been trying to pull a full system dump since I bought the tablet and had resorted to single pulls by name(very long and involved) I don't know if this will work for you, but on both of my 7 inch Gen 2 tablets, I just sideloaded Magisk Manager and then opened it (this was after unlocking the tablet) When I first opened MM it just said it needed to download some additional files for my environment. I clicked okay, it downloaded and installed the additional files. Once it rebooted, I open MM again and clicked install Magisk. On the next screen, I clicked direct install and let it do it's thing. After rebooting, root checker showed I had root, but I still can't get it to pass safetyNet. Root access does work as I have installed a few modules and busy box.
Hello everyone !! I recently installed the latest android 13 beta 3.3 on my Samsung Galaxy S20. I wanted to make a guide to show you the installation process. This is a GSI of android 13 ported from the google pixel 5, therefore there are a few things that don't work properly (I will list them below). If you have any questions or issues with installation please don't hesitate to ask and I'll do my best to help you !! Hope you find this guide helpful !!
Issues / Bugs
- No biometrics (No face unlock or fingerprint scannner)
- No always on display (only screen saver available)
- No auto-brightnees
- No sound on notifications
Pre-requisites
- Unlocked bootloader
- TWRP Recovery
YouTube Step by Step Tutorial
Download Installation Files:
2.7 GB folder on MEGA
32 files and 5 subfolders
mega.nz
How to Install Android 13 Beta 3.3 on Samsung S20 Series
1. Turn your phone off
2. Connect your phone to your computer via USB cable
3. Press the "power" and "volume up" buttons at the same time until you see the TWRP logo
4. Once booted into TWRP, click on "Reboot", then click on "Fastboot"
5. Wait for your phone to boot into fastboot mode
6. Go to your computer and download the folder with the necessary installation files linked above.
7. Open the folder that you downloaded and look for the "Platform Tools (Name of your OS)" folder.
8. Look for the "fastboot" file and drag it into a new terminal window
9. Leave a space and type the word "devices"
10. Hit enter
11. If you see a bunch of random numbers followed by the word "fastboot" your computer has recognized your phone
12. Go back to the "Platform Tools (Name of your OS)" folder and once again, drag the "fastboot" file into the terminal
13. Leave a space and type the words "erase system"
14. Hit enter
15. When the process is finished you should see the words "finished" and "total time" in the terminal
16. One last time, drag the "fastboot" file to the terminal
17. Leave a space and type "flash system"
18. Go to the folder that you previously downloaded (the one linked above) and look for the "Pixel 13...Beta3.3.img" file
19. Drag the file over to the command window and hit enter
20. Wait for the file to be flashed (this might take a while)
21. When flashing is finished you will again see the message "finished" and "total time" in the terminal
22. Go back to your phone
23. Click on "Reboot"
24. Click on "System"
25. Wait for your phone to restart with the new ROM
ENJOY !!!!
Great Tutorial There, Did you ever fix the issues from the pixel to s20
also is there a way to find out if my bootloader is unlocked?
Thanks again
R0YB0Y said:
Great Tutorial There, Did you ever fix the issues from the pixel to s20
also is there a way to find out if my bootloader is unlocked?
Thanks again
Click to expand...
Click to collapse
Google or YouTube, cheers
@victoriam8a, this gsi image is installable by twrp, plus gapps and magisk (individual choice), I did it a few days ago my fp was working, bluetooth streaming not working and a few more things, I'm gonna give another try and also try all the work arounds to get things going on android 13, cheers
If you have tried to install Windows 7 on a Surface Pro, or a UEFI-only device., you may have noticed it hangs on "Starting Windows" or gives error 0xc000000d, or you might have seen the following message:
The Surface Pro is a class 3 UEFI device, which means it has no Compatibility Support Module (CSM), which emulates the old BIOS environment. Windows 7 is not compatible with UEFI, which means without CSM, it wouldn't be able to function.
If you had to run Windows 7 on a Surface Pro, the only way would be to enable the Hyper-V feature of Windows 8 and run Windows 7 inside a virtual machine (VM). However, this would limit the resources available and the capabilities such as some of the touch/pen features.
Click to expand...
Click to collapse
However, this article proves that it isn't impossible to achieve this. This tutorial shows you how to install Windows 7 on a Surface Pro. This tutorial is meant for the Surface Pro 1, but could work on any other UEFI-only device, which it should, but not guaranteed.
ISO file link: https://archive.org/details/windows-7-surface-pro-1
INSTRUCTIONS:
1. Boot the USB. This ISO uses a Windows 10 PE, but has a Windows 7 install.wim.
2. Open command prompt by pressing "Shift+F10"
3. Type in setup.exe /noreboot
4. Go through setup normally.
5. On the command prompt, type in "diskpart"
6. Type in the following commands:
sel dis 0
lis par
sel par 1 (where your boot partition is)
assign letter w
exit
7. Open up Notepad, and click "Open" or "Save As". Enable all files to be viewed. Go to W:\EFI\Microsoft\Boot and copy the BCD file and paste it onto the Windows 7 partition.
8. Go back to diskpart by typing "diskpart" in
9. Type in the following commands:
sel dis 0
sel vol w
form quick fs=fat32
exit
10. Go back to Notepad, and click "Open" or "Save As". Enable all files to be viewed. Go to the USB drive, then go to the FlashBootPro folder, then copy the "EFI" folder.
11.Go to W:\ and paste the EFI folder.
12. Go to the Windows 7 partition and cut "BCD".
13. Go to W:\EFI\Microsoft\Boot and paste "BCD" on the folder.
14. Reboot. Setup should continue normally.
NOTE: For some reason, Windows will NOT boot if any USB devices are connected. Any time you boot into 7, you MUST disconnect them, boot into 7, then connect them again. Wifi is integrated but doesn't work. You will need to purchase a separate USB wireless adapter.
MSFN REPOST: https://msfn.org/board/topic/184267...-surface-pro-1-or-any-other-uefi-only-device/
Proof of Windows 7 installed on Surface Pro 1:
bro i can not understand most of it, is there any more specified tutorial somewhere? or can you help me?
Should i use the iso link you gave?
Hi, I follow the guide and everything went good until i got the message:
Could not install shim for VGA BIOS: Unsupported hardware
Can someone help me?
helpinghand200 said:
bro i can not understand most of it, is there any more specified tutorial somewhere? or can you help me?
Click to expand...
Click to collapse
At the last steps, you must replace the files at the hard drive where you installed Windows 7. You can do this by booting another OS, or making a live OS and then replace them on that hard drive from that OS.
HDD = Hard Disk Drive