*TUTORIAL* Install MacOS Monterey on Unsupported MacBooks - macOS

Hi
Here we go again
Lets install Monterey on Unsupported Devices
Disclaimer
I am not responsible if things on your end go downhill
Only use this method if your MacBook is not up to par with Monterey specifications
Prerequisites
MacOS Monterey Bootable USB
16GB USB
( Look at my other posts if you do not have the "Bootable USB" )
​SETUP​​
1. We need to download micropatcher from GitHub.. ( MicroPatcher Download )
2. Plug your boot-able MacOS Monterey USB Drive into the computer
3. Open up mac terminal and type sudo
4. Open up the micropatcher folder and drag and drop the ( Install-SetVars.sh ) file into the terminal and then you need to drag and drop the ( USB with Monterey boot drive ) on the desktop into the terminal and press enter key...
5. Once that finished, go back into the micropatcher folder, find ( Micropatcher.sh ) file, drag and drop into the terminal, and then drag and drop the USB on the desktop into the terminal again and press enter.
6. When that is finished, quit terminal and eject USB, and power off Mac.​
Click to expand...
Click to collapse
INSTALLATION SECTION​​
7. Now we are ready to install, Plug USB into mac, power on, and hold option key while the computer boots up.
8. Select EFI Boot and press enter key... Your Mac will shut down, power on again and press option key again while booting
9. Now select Install MacOS 12 and press enter.
10. Select Language and press arrow key
11. Click on Disk Utility and press continue.
12. Click on view (top left) and select show all devices
13. Now select the drive you want Mac OS 12 to install to and erase with the following parameters
Name- Macintosh HD
Format- APFS
Scheme- GUID Partition Map
Erase and click on done, then close disk utility.
14. Click on Install MacOS 12 and continue... Continue with the installer... Select Macintosh HD and continue...
MacOS Monterey Is being Installed Your Mac will restart Several times
Once Installed, continue with the initial setup until you reach the home screen
15. Now you will need to change the USB Stick name to Install macOS Big Sur
16. Open terminal window and type sudo, then open up USB and drag and drop ( patch-kexts.sh ) file into the terminal, press enter key, and type your password.
17. Once this has finished inside the terminal, YOU HAVE TO RESTART YOUR MAC​
Click to expand...
Click to collapse
We are done here
Till next time
Cheers
​

Really thanks!!!!
Gone try it as soon as I can and let you know how things went!

#mcl said:
Really thanks!!!!
Gone try it as soon as I can and let you know how things went!
Click to expand...
Click to collapse
Ok awesome. Just make sure you follow each step carefully

Ok, will be very careful

Hey!
Finally I decided to upgrade , and I am pretty happy for doing that. Even though I didn't expect this now animations are way faster, and Safari is so much faster. On big sur it lagged so much that I couldn't even use it.
However there is feature that I was hoping to be able to use but got unfortunately discover it just isn't available.
I would really like to have low power mode on my Mac, but it just doesn't appear any where in the OS.
What I found on the web is that it only works on early 2016 models and later.
Would it be possible for you to add a patch so they Mac thinks it's form 2016 so low power mode is available?
I think that way it should work but maybe you have a better idea...

Hey!
So I decided to install macOS Monterey on a 15" MacbookPro with dual graphics(in this case, I have the GT 750M).
I followed the other's guide you made and everything works great.
However as soon as I reboot into the USB, during the boot, the apple logo and progress bar glitches out and become tiny. This persists when I get into Monterey recovery everything is sill tiny.
Anyway I tried to continue and it seems to install the OS, however when it ends the installation, the boot screen never ends, it get stuck and I know the installation is complete because I can hear Macos voiceOver function, saying how to use if I need, but on screen I only see the loading bar and the apple logo. I tried restarting and nothing.
I also return to Big sur and then re do everything, got the same result.
Any help is welcome, and thanks in advance!

#mcl said:
Hey!
So I decided to install macOS Monterey on a 15" MacbookPro with dual graphics(in this case, I have the GT 750M).
I followed the other's guide you made and everything works great.
However as soon as I reboot into the USB, during the boot, the apple logo and progress bar glitches out and become tiny. This persists when I get into Monterey recovery everything is sill tiny.
Anyway I tried to continue and it seems to install the OS, however when it ends the installation, the boot screen never ends, it get stuck and I know the installation is complete because I can hear Macos voiceOver function, saying how to use if I need, but on screen I only see the loading bar and the apple logo. I tried restarting and nothing.
I also return to Big sur and then re do everything, got the same result.
Any help is welcome, and thanks in advance!
Click to expand...
Click to collapse
Well, I got to say I havent seen this happen before... its probably something to do with graphic divers compatability. I will do some research and see if I can find a fix for you.

Nameless Foe said:
Well, I got to say I havent seen this happen before... its probably something to do with graphic divers compatability. I will do some research and see if I can find a fix for you.
Click to expand...
Click to collapse
Ok thanks in advance for your time

#mcl said:
Ok thanks in advance for your time
Click to expand...
Click to collapse
No worries

Hey!
So finally the issue is finally fixed.
I tried to install Monterey using OpenCore legacy pacher and got the same result, however, it turns out I didn't see the warning when installing Monterey on this Mac(11,3). As it turns out when the installation is done you need to reboot in safe mode so the Mac don't use the Nvidia card.
Though, now with the latest version of OpenCore ( 0.4.7), it fixes that issue(on 0.4.6 you would have to reboot on safe mode).
Now when the installation is done it reboots it just and just works out of the box, and it automatically patches the system so you are able to use the Nvidia card without having to do extra steps.
So if anyone is interested in Installing Monterey on an unsupported Mac, visit their webpage, as everything is well documented, easy to follow and has an extensive list of supported devices.

Thanks for the news. When this guide was uploaded, this was the one of the earliest ways to get Monterey on unsupported devices

Related

Windows 7 & HTC Drivers Issue

Hi
I have tried the dummies guide concerning updating the HTC USB drivers but had a couple of issues:
1. If I press F8 during the boot process I get an abreviated version of the bois setup which has no selection for turning off digital signing of drivers. I have an ASUS motherboard so to enter the bois I press the DEL key. Whilst in the bios I can see no option for turning off the digital signing. The instructions in the thread simply don't work.
I have done some searching and found web pages that explain how to enter the command window, paste 2 or 3 lines of text to turn off digital signing and put W7 64 bit into a sort of test mode. I have done that and have "Test Mode Windows 7600" in the bottom right corner of my Desktop. I still can't install the HTC USB driver as it brings up an error due to being not signed.
Without installing the new driver I cant change my ROM. There must be others in the same boat having changed to Windows 7. Please help.
Ok a few things:
I'm on windows 7 x64 build 7600, I'm having NO problems, just connect your device in windows let it connect with active sync
Then de-connect your blacktsone, shut it down, and hold volume down button then press start up, it will now start in bootloader mode
Now re-connect and wait for it to get installed by your pc!
If you really DO need htc drivers
Go into your bios
Turn of any quick booting AND turn off full logog display
When windows is starting AFTER the bootscreen you'll get a screen with some sort of TABLE in it with all your hardware and all they're IRQ's
at THIS moment when you see this table press f8
Then you get a boot menu
and you can follow your guide with turning off the signed drivers etcetera!
Great Greet Giblet
wow dude, treat me like the idiot I am. Step by step please.
"Then de-connect your blacktsone" - i guess you mean take out the USB cable?
I wait for it to get re-installed but nothing happens whilst in bootloader and the word serial stays at the bottom of the screen
OMG
Oh my god, I am really frustrated becuase I managed to get it to work with your help but I don't know how. I must have tried everything 10 times without luck then all of a sudden it worked.
If only I knew what I was doing wrong I could pass it along to the next poor sap.
Thanks for your help.
H
Some options to get a new ROM on your device:
Alternative Option: Run ROM from storage card (this requires HSPL on your device)
- Connect your phone to your pc with the usb cable
- Choose Disk Drive option on your phone when presented with the choice.
- Extract the downloaded rar and if not called BLACIMG.nbh rename the romfile to that (ruusigned.nbh is commonly used so rename when so)
- Copy the BLACIMG.nbh to your phone's storage card via Windows Explorer where it should show up as an removable harddrive.
- Disconnect your phone from the pc once copy has finished.
- Shut down your phone.
- Press Volume Down (left top of phone) and keep it pressed while pressing the Start button (on top of phone) once.
- The bootloader (red,green,blue,white screen) will now start, it will detect the new rom file and ask you if you want to update your current one.
- Confirm and follow instructions on screen
Done.
As for your unsigned drivers i can offer some tips:
- Press F8 after you have seen all your hard drives recognized in the bios bootup screen but before you see the Windows Logo.
- F8 might be set as a bootselector menu by your motherboard manufacturer, if this gets in the way of trying the get to the F8 options from Windows you can disable it in your BIOS (to enter press del)
- If you have Windows 7 Ultimate you are entitled to XP-Mode which is basically a built in virtual machine of Windows XP within Windows 7, some people have been succesfull connection their phone to that XP installation and were able to update via it.
Hope this helps. together with the previous poster's comment you should come a long way, good luck.
Heefy said:
Oh my god, I am really frustrated becuase I managed to get it to work with your help but I don't know how. I must have tried everything 10 times without luck then all of a sudden it worked.
If only I knew what I was doing wrong I could pass it along to the next poor sap.
Thanks for your help.
H
Click to expand...
Click to collapse
Oh lol, guess you just managed, grats on that. for future you could try the alternative option i posted, works garanteed irregardless of operation system.
Solution found, thread closed
In future try posting such queries in the Dummies guide: updating HTC USB Sync Drivers thread. Thats what its there for

How to FORCE stop phone from showing up as USB drives in Recovery, still no root :(

Okay I don't know if this will help anyone, but I figured out how to stop Windows from detecting the phone as two USB drives when the phone goes into Recovery mode, and to make it show up as Android Composite ADB device.
I do NOT have HTC installed, rather, I'm using the USB 3 drivers that come down through the SDK, so I'm not sure how to do this if you are using the HTC Sync drivers intead.
At any rate, start with the phone off and disconnected. Open the Device Manager. Boot with your prefered method into Recovery mode, then connect the phone. It should detect as USB Mass Storage Device under Universal Serial Bus Controllers. Right click on USB Mass Storage Device and click Uninstall and then OK. Once this is done, disconnect the phone (you can leave it running in Recovery).
Open My Computer and navigate to C:\Windows\inf. Copy the files usbstor.inf and usbstor.pnf to your desktop or wherever, it doesn't matter, just make sure you put them somewhere you can get them later. Then delete them from the C:\Windows\inf folder. These are the drivers that Windows automatically uses for USB storage devices.
Ok, now bring Device Manager back to the foreground and plug the phone back in in Recovery. It should show up as Android Phone with an exclamation mark. If Device Wizard pops up cancel out of it. Now right click on the Android Phone and click update driver. Click Browse my computer for driver software. Click Let me pick from a list... Click Android Phone and Next. Click Have Disk. Browse to your SDK folder into the USB Drivers folder and you should see android_winusb.inf, select that then click OK. You should now have a list of three items to select, this part I am not sure if there is a 'right' or a 'wrong' but I go with Android Composite ADB Interface.
Select that or whichever one you think and this is what it will install as. Bingo, now whenever you connect the phone into Recovery or boot into Recovery with it already connect it correctly detects as the Composite ADB Interface or whichever you selected, but does NOT show up as any USB drives.
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
At any rate, to get everything back to normal as far as your computer being able to use USB storage devices just copy those two files back to the inf folder before you connect them and you should be fine.
bast525 said:
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
.
Click to expand...
Click to collapse
Format it LONG Fat32, 1024k allocation, name it TEST, put PB31IMG.zip (downgrade ROM) on it, power on into bootloader holding volume down until you get to volume up to start upgrade, run the downgrade from Bootloader, then immediately reboot with holding the track button switch into Fastboot menu, power to Bootloader, let the card check run, decline upgrade this time, run your loop.bat or loop.sh if you like linux, power the phone into recovery boot, and prepare yourself to be happy--I think that will work. The whole trick is get a card/format that forces recovery into an ADB-available mode.
Or you could try what I've done 7 times and achieved ADB Shell 7 times...
1. Turn the phone off.
2. Start running Loop.bat
3. Unplug USB cable.
4. Turn device on in Fastboot by holding in the optical joystick and power.
5. Plug USB in.
6. Hit power button once to get to HBOOT.
7. Wait two seconds for it to do it's thing.
8. Pull off the back of the phone.
9. Hit Vol - to Recovery then hit power.
10. Immediately after doing this continuously push the sd card in and out (about every .5 - .75 seconds)
11. ?????
12. Profit
@DigitalDementia--
How is what you said relevant in this thread?
bast525 said:
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
Click to expand...
Click to collapse
drtrmiller said:
@DigitalDementia--
How is what you said relevant in this thread?
Click to expand...
Click to collapse
Pretty positive it had everything to do with that section of the first post, he said he still couldn't achieve root I attempted to help him. Why don't you explain to me exactly what it doesn't have to do with this thread?
rynosaur said:
Format it LONG Fat32, 1024k allocation, name it TEST, put PB31IMG.zip (downgrade ROM) on it, power on into bootloader holding volume down until you get to volume up to start upgrade, run the downgrade from Bootloader, then immediately reboot with holding the track button switch into Fastboot menu, power to Bootloader, let the card check run, decline upgrade this time, run your loop.bat or loop.sh if you like linux, power the phone into recovery boot, and prepare yourself to be happy--I think that will work. The whole trick is get a card/format that forces recovery into an ADB-available mode.
Click to expand...
Click to collapse
The real bummer here - and I should have known better, really - is that this wipes your phone.
I suppose it should be obvious, but take it from someone who's pretty new to Android phones and just wiped their entire phone after following your steps: Please add a warning to your original post.
It's late, I'm tired and irritated, but I'm sort of bummed to know I went from hero to zero in trying to enter shell (again) during recovery all in an effort to get proper perm. root. Sort of ****ty to know that I just lost everything.
still no root
I'm sorry, I shouldn't have assumed people knew an IMG flash from bootloader wipes user data. Believe me, that's not the only time you'll wipe if you keep modding
-------------------------------------Sent via the XDA Tapatalk App
USB drives are ok in recovery
When I am in recovery with adb and working correctly it still shows the 2 USB drives so this is normal and ok, what you have done is fool yourself into thinking that your phone is in correct mode but it really is not, this is why it still does not work, sorry.
rynosaur said:
I'm sorry, I shouldn't have assumed people knew an IMG flash from bootloader wipes user data. Believe me, that's not the only time you'll wipe if you keep modding
-------------------------------------Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Now that I've scorched the earth, I'm hitting this thing hard with every trick I can think of to get the shell in recovery again.
Thankfully, I at least have my app list on appbrain.
After researching around the different forums, I think this maybe my issue. I will have to make this attempt when I get home.
This is what I posted on a different forum. I am not sure if this is a similar experience you were having:
So, for a little a bit I was having issues with finding and modding the usb.inf file. I got that finally resolved... Now as I go to one of the first parts of the procedure, executing the adb shell command. Well at first it said the 2 lines, about the daemon and whatever the second line was. Anyways, the third line did not say "no device found" it went straight to a shell prompt "$" . The instructions made a point in the instructions for it to say " no device found" .
I went ahead with the rest of the instructions. No Luck. And I did both methods. A co-worker of mine told to run adb devices to see if my phone is recognized. I will also make that attempt tonight.
I wanted to know if any of you had some insight. I made sure I was in the right directory.
I will make another attempt on a different machine tonight.
Thanks. Oh yeah, I do have some UNIX experience if that makes a difference.
I had the same problem, used this method here
addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
Click to expand...
Click to collapse
Seemed to help me with the dumb usb mass storage devices whilst in recovery
I don't know how I missed this thread earlier though, It had been a problem for me for days!
kentoe said:
I had the same problem, used this method here
Seemed to help me with the dumb usb mass storage devices whilst in recovery
I don't know how I missed this thread earlier though, It had been a problem for me for days!
Click to expand...
Click to collapse
I rooted in Windows, rather than linux, simply because I like the look of MejDam's procedure better than the linux script posted here on XDA--and his windows procedure is accompanied by his YouTube video
Long story short: I had ADB Composite Device AND the two storage volumes mounted together, as I got shell, and did the other steps in recovery. NB: they were mounted as Generic Storage Volumes, not writeable partitions. The stock recovery on DI does not allow host to mount either partions, although I'd like to see if
Code:
mount /dev/block/mmcblk0p1
worked for the SDcard on the sdcard, cuz then it would be a cinch to mount sdcard/emnc partition into host OS--windows, linux, Atari 2600, etc Worth a try.
Anyhow, my conclusion: a bad driver setup could be a barrier to catching adb shell, but it is certain not the prevailing problem for most, IMHO.
Was wondering if bast525(the creator of the thread) was ever able to adb shell while in recovery, and if so what did you do thanks.
Heh, I wish.... I've tried just about every method posted on these forums, and five different SD cards from Sandisk, PNY, and Kingston. The only thing I haven't tried is rolling back to the pre OTA update, because I don't want to wipe the phone at this point.

[GUIDE]How to install Windows 7 retail via USB drive

Hey people. Think you have seen a thread like this before? Well, that's because you have. But THIS thread is different! For two reasons:
1-It's written in GOOD English. No offense folks, but spell checking is really not that hard.
and
2-It deals with EVERYTHING you need to do to get Windows 7 retail up and running on the Shift.
If you see something that needs to be changed/corrected/updated then please feel free to let me know!
HOW-TO INSTALL WINDOWS 7 RETAIL VIA USB ON THE HTC SHIFT X9000 SERIES
Now, before we begin, this guide assumes a few things:
1-that you are using a RETAIL or RTM copy of Windows 7. This guide WILL NOT work with beta or RC versions of Windows 7 OR versions that are N-lited, stripped or altered in anyway. You MUST be using a retail image, either made from a disc you own or from other sources. Please note that we at XDA do not support piracy and suggest that you buy a legal copy of Windows.
2-That you are using a GSM version of the Shift, IE the X9500 or X9501. While these instructions will work with the CDMA version of the Shift, I personally do not have one so I cannot confirm if/how the CDMA radio works using this installation method.
3-That your version of Windows 7 ISN'T Home Basic. While Home Basic will work, it doesn't support touchscreens. I personally installed Ultimate, as the requirements are the same no matter what version you use.
To install you will need:
1-A Shift(duh!)
2-A copy of Windows 7 RTM or a retail disc
3-A USB drive that is 4GB or greater, but no larger than 32GB for Windows
4-A USB drive(any size really) for the storage of HTC drivers for post installation
5-Some time on your hands
6-Either another PC with a CD drive or a USB CD drive
Now onto the good stuff!
1-Let's begin. Insert your Windows 7 DVD into your CD drive. If you are using an ISO image, skip to step 4.
2-Make a folder on your desktop called Windows 7.
3-Copy ALL the files from your Windows 7 DVD into the folder you just made. Be patient as this process will take some time, especially if you are doing this on your Shift.
4-While the files are copying(or after they are done, whatever) go ahead and insert your USB drive into a free port.
5-Open "My Computer" and locate your USB drive. Right click on it and select "Format". Click the menu which says-"File System" and select "NTFS" from the options. Then click Format and let it finish. It should take just a few moments.
6-Once your USB drive has been formatted, open a command prompt and type the following command:
BOOTSECT.EXE /NT60 H:
Where "H" is your the letter of your USB drive.
7-Your USB drive should now be ready to use!
8-Insert your USB drive into your Shift's USB port, press the power button and repeatedly press F10 as it starts to be brought to the Boot Menu and select your USB drive and hit enter.
9-Windows should begin loading setup information now. It should take around 5-ish minutes to get to the graphical part of the installer.
10-When you are presented with the graphical portion, select your country and whatnot, then a username and such, and when it asks you if you want to Upgrade or Custom install, select Custom.
11-You will now need to format your Shift's harddrive. Select the partition that is displayed and select "Format". PLEASE NOTE THAT THIS WILL DELETE WINDOWS VISTA FROM YOUR SHIFT. YOU CANNOT RECOVER ANYTHING THAT IS DELETED. Your recovery partition however is not touched in anyway, so if Windows 7 doesn't work for you, you can reinstall the stock Vista from the recovery partition.
12-Once it is finished formatting, select that partition to install to and continue on with the installation.
13-When it finishes you SHOULD be presented with the Windows 7 desktop. And that's about it. No WiFi. No sound. Pretty much nothing. Now, you DID download the drivers and put them on another USB drive right? Right? GOOD!
14-Insert your USB drive and let Windows install it. Now, ALL of the drivers that we are about to install MUST be installed in the same fashion as I am about to describe. Right click each one and select properties. Click the compatability tab and select the option to have the installer run in compatibility mode for Windows Vista. This MUST be done or the drivers WILL NOT install.
15-Once you have done that, go ahead and install the following drivers. Don't worry about the other ones for right now. Install them IN THIS ORDER OR ELSE THEY WILL NOT WORK:
1-Vista Intel Chipset driver
2-Vista ECD
3-HTC Touchscreen
4-HTC ShagCTRL
5-Marvel SDIO WiFi
After you have installed those 4 drivers, restart your Shift.
16-Once your Shift has restarted, go ahead and press the Comm. Manager button. Shift Control Center should pop-up and your WiFi card should begin installing. If it doesn't, click on the button for WiFi and make it say "ON" and it should then start installing.
17-Once your WiFi card is succesfully installed, click Start->Windows Update.
18-Click on "Check for updates" on the left hand side and let Windows do it's thing. It should find 60-ish updates for download, around 6 of which are drivers for your various devices such as sound and Bluetooth and the like. Don't worry, your screen resolution WILL get better!
19-After Windows has installed updates..you are pretty much done! EVERYTHING should now be working in Windows 7!
20-ENJOY 3(!) HOURS OF STOCK BATTERY LIFE ON YOUR SHIFT RUNNING WINDOWS 7!
That's about it folks. I worked for 2 days straight to devise this method for installing Windows 7 on my Shift, and it couldn't work any better. If you find a mistake, or have a suggestion please let me know!
Great!
I´ll move it to [REF] Guides | Tutorials | FAQs | Stickies | Read here before posting thread located here:
http://forum.xda-developers.com/showthread.php?t=772017
it went fine till step 16, the Comm. Manager button doesnt open anything, however the wifi works ok.
please tell me how does the Comm. Manager work
and now it just wont boot, it gives a blue screen and tells me theres an error, and automatically shut down.
What error does it give you? Are you ABSOLUTELY SURE that you are using a GENUINE untouched OEM RTM copy? This process ONLY WORKS with the legal untouched OEM RTM. If you are trying this with some kinda downloaded ISO it WILL fail and bluescreen on you. It must be build 7600 or higher. Comm. Manager just works for me under 7 following these instructions.
Hi! Thank you for the guide, everything is fine! The only thing doesn't work is the touchscreen. I've installed the touchscreen drivers in compatibility mode Windows Vista SP2 and as Administrator. Do you have any idea?
EDIT: Solved! I reinstalled the driver for the 8th time and it worked!

[Guide] Absolute Newbie's Guide to Rooting a Streak 7 that has Stock Honeycomb

Obviously this guide owes a huge bunch of thanks to "TheManii", "Giveen" and other folks who can't be named on this forum. I have tested this on both a Streak 7 WiFi and a Streak 7 4G. In both cases they had the Stock Honeycomb already on them. So if you are coming from some other version of Android you may wish to reconsider
1) Download the Fastboot+ADB.zip file for Clockwork Mod 5.0.2.7 from the XDA Developers thread (http://forum.xda-developers.com/showthread.php?t=1334487)
2) Download the Clockwork mod 5.0.2.7 file from the XDA Developers thread (http://forum.xda-developers.com/showthread.php?t=1334487)
3) Go into Settings->Applications and turn on "Run Applications from Unknown Sources"
4) Go to Development Settings and select "USB Debugging"
5) Unpack the Fastboot+ADB file into a directory on your computer where you can find it again
6) Attach the Streak to your PC, and copy the "Drivers.zip" file from the root directory of the Streak (/sdcard) to the same directory where you unpacked the Fastboot file
7) Turn off your Streak after you have copied this file, and disconnect it from the PC
8) Unpack the drivers.zip file and find the "Setup.MSI" file. Execute this file to install the drivers you will need
9) Put your Streak into Fastboot mode - i.e. turn it off, then turn it on by pressing the Power button while holding the Vol DOWN (-) at the same time. This can take up to 20 seconds
10) You will get some red text followed by a white line saying something about Fastboot USB downloading is active
11) Connect the streak to the PC now, and it should install an Android ADB driver. Depending on what you have already setup you may get some drivers installed successfully, and some not. In general if you've been following this guide, you'll be ok
12) Open a command line for the folder where you have fastboot and your recovery image (ClockWorkMod) - in windows navigate to the folder, and hold the shift key while right clicking
13) On the command line type the following:
fastboot -i 0x413C flash recovery recovery.img (where recovery.img is the ClockworkMod or other recovery file)
14) On the command line type the following:
fastboot -i 0x413C reboot
15) Your device should now reboot
16) To get it to reboot into CWM, turn the Streak off, and then turn it on again while holding the Power Button and Volume UP (+) at the same time. This may take up to 30 seconds
From here you would follow the normal CWM options to install just the root files (Superuser7 for one example) or install a custom ROM.
It turns out steps 9 - 15 are also a great way to fix the problem when your Streak comes up and starts asking for a Password when you never setup a password. For some reason installing one of the custom ROMS also installs a version of CWM that is not as recent as the 5 series, which can lead to issues with the signature verification (i.e. when things go "boom", Android sees the partition as encrypted rather than just "locked"). So steps 9 - 15 allow you to put in a later CWM which does a proper wipe, and you're back in business. Have to reinstall apps, but the data is left alone.
Just in case I'm not the only one who has run into this
Ok, I used this guide to modify my Dell Streak 7 wifi. After I was done my screen kept flickering and I put it back to stock thanks to AndroidOVERALL putting together a post on how to complete the restore.
I have searched about the screen flickering but didn't find a resolution. Maybe I missed it, but it seemed that others had the same issue and it was either a hardware problem, the brightness was adjusted, or auto rotate was disabled. I tried adjusting the brightness settings and many other settings but the issue was not resolved until I returned everything to stock.
I have a Dell streak 7 wifi, US version with Honeycomb.
Please point me in the right direction if this issue has been resolved and I missed it. If not any suggestions?
Did you load a custom ROM after following these steps, or did you just reboot aft getting CWM installed. Usually the flickering comes from an issue with the video driver (so can be software if a bad driver, or hardware if it's only marginally in spec).
For any one who gets to the end of the steps and now can boot in go CWM but doesn't know what to do about getting rooted.
Very very Simple.
Download Superuser7.zip
http://www.tablet-cables.com/streak/tools/root/Superuser7.zip
Have your Streak booted normally and USB cable hooked up.
Move to the internal Memory Superuser7.zip
power off device
Power back on using Vol UP & Power Button
Select 2. Software upgrade via update.pkg on SD card and press power
CWM will load.
Select install zip from sd card and power to enter.
select Choose zip from internal sd card and power.
use Vol UP to go backwards to your files and select Superuser7.zip and hit power
move down to YES - Install Superuser7.zip and hit power
thats it. its rooted.
goto ++++++++ Go Back+++++++
and reboot system now
and let it reboot.
Not necessary, but I'd suggest running Superuser and hitting the Knob icon top right (settings) and scrolling down and updating Super User.
Hope this helps someone who may not know where to get Superuser7 and what to do after following the great guide above.
thanks!
nothing sucks worse than a bad download -- happend TWICE! (dayum!)
got rewt?
Help?
I am trying to Flash superuser.zip after installing the clockwork.
But I keep getting the following screen. I do not have exterior sd card installed.
What can I do?
blastedmax said:
I am trying to Flash superuser.zip after installing the clockwork.
But I keep getting the following screen. I do not have exterior sd card installed.
What can I do?
Click to expand...
Click to collapse
It's saying that it is looking for an SD Card and not finding it, so that certainly makes sense. However, it sounds like it is looking for "update.pkg" rather than "superuser.zip", so is it possible you accidentally selected the "Update" option in CWM rather than the option to select a file?
He doesnt have clockwork mod installed, you must have CWM installed to flash zips
OK, I have a new Streak 7 t-mobile with HC 3.2. I plug it to the pc running xp sp3, and it needs drivers for MTP and Streak7. I pointed to the Fastboot+ADB folder I extracted for the Streak7 driver and it installed Android ADB Interface. Pointing there for MTP fails to find a driver. I can't get to the internal SD to get the drivers.zip because my computer won't recognize the Streak until the MTP driver is installed. After installing an MTP driver from the net, I can see the internal and external SD. I copied everything to a single folder labelled STREAK in c:\ and unplug the Streak from the pc. I put the Streak into fastboot mode (Volume - & Power), wait about 10 seconds, then plug it into the usb port. The computer see the Fastboot device and needs a driver. I point it to the STREAK folder (former Fastboot+ADB) but it didn't find a driver it liked. I tried to install manually, but there is no Android 1.0 or Android ABD Interface devices in my list. I do see Android USB Devices, but it is empty when I click on it. ANYBODY else get this, and how do I move forward? I followed the guide to the letter, and appreciate all the work & effort you guys put into making these root methods available. The Streak7 is a cool little device, but I think it will be cooler once I root it. I have rooted my Epic 4g and the wife's Evo 4g on this same computer, and I do have the Android SDK installed (even though I don't know how to use it).
OK, so I used all the same files I have here and was able to successfully get Clockwork flashed & gain root. I dunno why the xp machines don't like these files. I tried 3 other xp laptops before getting to my wife's Windows 7 laptop, which worked just as described in the very well-written guides. #MindBottling!
I cannot even find the drivers.zip in step6. WIN7x64 and a brand new tmobile streak 7. where is this thing? I looked through all the folders and subfolders.
Drivers.zip is in the main directory of the Streak. Open up ES File Manager or a similar program and you should see it. To get it to your PC, attach the Streak via USB and let it mount as external storage (default behavior I believe).
In my main directory on on my streak, using ES file explorer, i cant seem to find that file. I see acct, cache, config, d, ....etc folders, i scroll down, i see default.prop, init, init_recovery.rc, ...... var files, but i dont see drivers.zip. help I need to get honeycomb so I can use skype front facing camera, cause I understand froyo 2.2 can only use the back camera w skype.
Since this should be a common file for all SD7 units, can someone please email that file to me so i can get past step 6. [email protected]
cidand1 said:
In my main directory on on my streak, using ES file explorer, i cant seem to find that file. I see acct, cache, config, d, ....etc folders, i scroll down, i see default.prop, init, init_recovery.rc, ...... var files, but i dont see drivers.zip. help I need to get honeycomb so I can use skype front facing camera, cause I understand froyo 2.2 can only use the back camera w skype.
Click to expand...
Click to collapse
From this I gather your Streak did not ship with Honeycomb. That would explain why you didn't find the file as that is something that I gather Dell added when they changed how they shipped it later on. I am not sure what the redistribution rules are for the file, which is why I haven't posted it myself.
That said, I also can't guarantee this process will work for someone starting with Froyo. I do know there may be an issue with which version of CWM you can use in that case. As such, you may want to check one of the other guides to be sure.
EwanG said:
From this I gather your Streak did not ship with Honeycomb. That would explain why you didn't find the file as that is something that I gather Dell added when they changed how they shipped it later on. I am not sure what the redistribution rules are for the file, which is why I haven't posted it myself.
Click to expand...
Click to collapse
Explain please? Shouldn't drivers be present no matter how it's shipped? Mine came with Froyo with drivers, I OTA'd to HC and I still have them.
Ya I bought this from dell directly about 3 weeks ago. From what I have been reading on XDA, mine is definitely different. Its a tmobile streak 7.
Android 2.2.2
Kernel : 2.6.32.9
OEM ver: GLUNB1A133633
Build : 15420
Another thing I noticed is that even trying to load CWmod through fastboot, my computer does not recognize the DS7 in fastboot mode. The drivers in the fastboot+ADB zip file dont work on my computer as fastboot drivers (or maybe I should try another CPU). My cpu is an AMD 64; running win7 pro 64; i need some serious help.
I think I bricked!
Ok I followed the directions from here to root my tablet.
http://www.cesgeekbook.com/2011/12/root-dell-streak-7-with-honeycomb-32.html
All went well! Everything worked and I was rooted! did the Superuser7. Clockwork came up and installed. All went right! So I was pleased. I figured I would later than put on a ROM cause it was late. Well was going to do so and tried to go into clockwork via ROM manager. Didn't work! Kept rebooting! So I figured I would try the pother way "Press Power and +" then click to Install from SD Card to go into Clockwork. That didn't work either! Then Now it won't reboot at all! I can get into fastboot and I can get into the bootloader. But that's it! I tried to do a Factory Reset and nothing! it just stays on the Dell boot screen. Anyway to fix the problem? If so, please give me step by step directions on how to do it.
Use of ROM Manager is generally discouraged due to unknowns about how the package will work with other ROMs. It also isn't clear to me which version of CWM you were using.
If you can get into fastboot, then you should still be able to use ADB, and I would suggest trying to reinstall CWM as indicated in the first message of this thread. That way at least you should be at a known good spot for us to try and help you get a custom ROM installed.
EwanG said:
Use of ROM Manager is generally discouraged due to unknowns about how the package will work with other ROMs. It also isn't clear to me which version of CWM you were using.
If you can get into fastboot, then you should still be able to use ADB, and I would suggest trying to reinstall CWM as indicated in the first message of this thread. That way at least you should be at a known good spot for us to try and help you get a custom ROM installed.
Click to expand...
Click to collapse
Didn't know about the Rom Manager issue. I guess it's only good to use on cell phones? Anyway, I am trying again, but the problem is my laptop is now not reading the tablet when in fastboot mode. I have followed all the step again. Including reinstalling the drivers. But since it's not reading the tablet. I can not reinstall CWM. The version I installed was the one from the 1st page. It's a fairly simple thing to do. But just need to get the device to be read by my laptop.
I have contacted Dell and explained to them the problem. They did say that I can return it to get it fixed. but still kind of hoping I can do it from home.
Marvelous0ne said:
Anyway, I am trying again, but the problem is my laptop is now not reading the tablet when in fastboot mode. I have followed all the step again. Including reinstalling the drivers.
Click to expand...
Click to collapse
Not sure what you mean when you say the laptop is not reading the tablet in fastboot mode. When in fastboot it should NOT show up as attached storage. The best way to tell if it is "really" seeing the Streak 7 is in step 13 - which uses an id rather than a device name so that it should work even if the tablet isn't fully identified. If you try to perform step 13 while in fastboot, what message are you getting?

[GUIDE] Installing Windows 10 Technical Preview on the HTC Shift

Windows 10 Windows Technical Preview is available for more than a week. Since i have an extra old 40gb hdd for the shift, i decided to give it a try, and i can say that it works perfectly well. Everything works including touchscreen, wifi, bluetooth, modem, etc.
However installing the drivers may be a little tricky. Here are the steps:
1. Download Windows Technical Preview from microsoft website (download the x86 version)
2. Extract the .iso file to a usb stick (i used power iso to do that)
3. Plug the stick to the shift and boot from it
4. Follow on screen instruction to install windows
5. When done copy the drivers for the shift (you have the download link bellow the video ) to a stick
6. First install "VistaECDrvV" in compatibility with windows vista (right click on the file - properties - compatibilty tab- run this program in compatibility mode for: - select windows vista (service pack 2) !! do that for all of the drivers) - restart later
7. Install "TouchScreen"
After installing touch screen driver the touch should work - give a restart
8. Install "Synaptics MicroPad" - restart later
9. Install "shagctrl" ignore the Microsoft .NET Framework missing error - restart later
10. Install "Marvell Wifi driver" - restart later
11. Press the Win+R key combination and type msconfig in the run box and hit enter - switch over to the boot tab, and click on the Safe Boot check box - select minimal -apply -ok - restart
13. With windows booted in safe mode navigate to C:\Windows\System32\drivers right click on "sdbus.sys" -> properties -> security -> advanced -> owner TrustedInstaller click on change -> in the field labelled "enter the object name" type your username -> ok -> apply -> ok -> now back on security tab edit permissions -> click on users -> check all boxes from "permissions for users" tab on allow -> apply -> yes -> ok. Now delete "sdbus.sys"
14. Copy the "sdbus.sys" from the archive that i attached here to C:\Windows\System32\drivers
15. Press the Win+R key combination againg and type msconfig in the run box and hit enter - switch over to the boot tab, and unthick the Safe Boot check box - apply -ok - restart
16. You should have wifi working now - If you cannot find any wifi networks, as it was in my case, go to device manager - right click on the "Marvell sd8686 Wireless LAN SDIO Adapter" (the one without the exclamation mark if you have two) - properties - advanced - from the property box select 802.11D support - on the value box value box select enable. Your wifi should work ok now.
17. Install the "sherry driver 1.3" for the best performance of the video card.
18. That's it! enjoy
What i like most about windows 10 is that it have a "card view" of the running apps just like maemo 5 on noka n900, or the blackberry 10 os. Overall it runs a little better than windows 7 and similar with windows 8.1.
Maybe i will install it as a replacement for windows 8.1 update 1 on the main 120 gb hdd
Here is a small video to see how it runs:
Download HTC X9500 DRIVERS
ryu1 said:
Windows 10 Windows Technical Preview is available for more than a week. Since i have an extra old 40gb hdd for the shift, i decided to give it a try, and i can say that it works perfectly well. Everything works including touchscreen, wifi, bluetooth, modem, etc.
However installing the drivers may be a little tricky. Here are the steps:
1. Download Windows Technical Preview from microsoft website (download the x86 version)
2. Extract the .iso file to a usb stick (i used power iso to do that)
3. Plug the stick to the shift and boot from it
4. Follow on screen instruction to install windows
5. When done copy the drivers for the shift (you can find them on this forum) to a stick
6. First install "VistaECDrvV" in compatibility with windows vista (right click on the file - properties - compatibilty tab- run this program in compatibility mode for: - select windows vista (service pack 2) !! do that for all of the drivers) - restart later
7. Install "TouchScreen"
After installing touch screen driver the touch should work - give a restart
8. Install "Synaptics MicroPad" - restart later
9. Install "shagctrl" ignore the Microsoft .NET Framework missing error - restart later
10. Install "Marvell Wifi driver" - restart later
11. Press the Win+R key combination and type msconfig in the run box and hit enter - switch over to the boot tab, and click on the Safe Boot check box - select minimal -apply -ok - restart
13. With windows booted in safe mode navigate to C:\Windows\System32\drivers and delete "sdbus.sys" and "dumpsd.sys"
14. Press the Win+R key combination againg and type msconfig in the run box and hit enter - switch over to the boot tab, and unthick the Safe Boot check box - apply -ok - restart
15. When booted in normal mode copy the files from the "wififix" archive, that i attached to C:\Windows\System32\drivers and restart
16. You should have wifi working now - If you cannot find any wifi networks, as it was in my case, go to device manager - right click on the "Marvell sd8686 Wireless LAN SDIO Adapter" (the one without the exclamation mark if you have two) - properties - advanced - from the property box select 802.11D support - on the value box value box select enable. Your wifi should work ok now.
17. Install the "sherry driver 1.3" for the best performance of the video card. Search it on google.
18. That's it! enjoy
What i like most about windows 10 is that it have a "card view" of the running apps just like maemo 5 on noka n900, or the blackberry 10 os. Overall it runs a little better than windows 7 and similar with windows 8.1.
Maybe i will install it as a replacement for windows 8.1 update 1 on the main 120 gb hdd
Here is a small video to see how it runs:
Click to expand...
Click to collapse
Thanks alot, I am going to install it now
http://www.mediafire.com/download/c9g6a23223zr3sk/sherry1.3.2betaGMEGSE.rar
Excellent how-to. Clear and precise.
For those who want to perform it: taking a look at ryu1's comment in Post#14 is crucial!
You bring shift to future.
Also an interesting Video- as i see you've only 1GB RAM installed, and nevertheless your Shift runs pretty fast-
faster than mine with 2GB and Win7U.
Network connection, connection to SnapVue... i'm really amazed.
How long does it take to boot, and what about GPS?
Think i'll create a new partition on my 128GB SSD and run Win10 from there.
How large do you think should it be?
B-44 said:
Excellent how-to. Clear and precise.
You bring shift to future.
Also an interesting Video- as i see you've only 1GB RAM installed, and nevertheless your Shift runs pretty fast-
faster than mine with 2GB and Win7U.
Network connection, connection to SnapVue... i'm really amazed.
How long does it take to boot, and what about GPS?
Think i'll create a new partition on my 128GB SSD and run Win10 from there.
How large do you think should it be?
Click to expand...
Click to collapse
Well, i'm sure gps work ok (at least on the windows mobile side) but didn't tested on the windows 10 side.
For booting, i'm sure it take less than 1 minute, but don't know the exact time.
If you want to make a partition for win10, that should be at least 10 gb.
It would be really nice to see how it will run on your shift with 2gb of ram.
Please post the result if you install it
Made 20GB... had been frequently suggested for win8
Now taking a look if I've got a spare usb stick.
Maybe I'm missing something here. On my X9500 I can't get by the error about the 800 MHz processor. Maybe you are on a different model?
Same thing occured with win8 if i recall right... early releases worked fine, and later ones also came up with this problem. (It may have been with BenQ MID S6 instead Shift, I'll try to find out.)
Don't know if there had been some workaround.
As MS is continuously working on it, it may depend on the releases' date.
Mine dates october 20th, but i won't be able to test until next weekend.
If ryu1 doesn't have another idea, it may be useful to share the release he uses.
The processor should always be the same.
edit: Post#86
http://forum.xda-developers.com/showthread.php?t=1264742&page=9
What error are you talking about? i installed windows 8, then 8.1 and now 10 but never got any error about cpu.
Are you sure you didn't download the 64 bit version?
Win 10 Technical Preview lists as a requirement:
Processor: 1 gigahertz (GHz) or faster
Error complained about lower specification.
It was the 32-bit version.
"error" may be the wrong word.
The problem had been discussed in the thread i have linked above.
Again: it may be interesting to know the date of release.
ryu1 said:
What error are you talking about? i installed windows 8, then 8.1 and now 10 but never got any error about cpu.
Are you sure you didn't download the 64 bit version?
Click to expand...
Click to collapse
Maybe i've got it...
in your how-to you say "Plug the stick to the Shift and boot from it".
You mean plug it in, start your shift, enter boot options and select usb stick to boot from, right?
I had prepared my usb stick with powerISO, plugged it in, opened my stick in devicemanager and doubleclicked "Install".
And ran into "your device won't be able to run Win10 because of less than 1GHz".
Maybe this was my mistake, and i won't have this problem when booting from stick.
Will report asap.
That's it..
Just do what daddy told us
(And DON'T use windows installer.)
I haven't finished installation completely,
but right now i must say speed is amazing!
As some drivers are automatically installed to volume "C" i think i'll switch the names of C and X
(the partition i'm installing to), reinstall all drivers and then switch back.
edit: obsolete, win has done it by itself
Sorry for the delay, but i am very bussy these days. Anyway the installation mus be done by booting from usb stick, not via installer.
I have allready installed windows 10 on the main hdd instead of windows 8.1. There are a few things i forgot to mention on the first post, when booting into safe mode to delete the "dumpsd" and "sdbus" files you'll need permission to delete them. Just follow this instructions to change the permission: http://www.askvg.com/guide-how-to-take-ownership-permission-of-a-file-or-folder-manually-in-windows/
That's what i just was about to ask you, as i am stuck at this point...
Will try later and report
Tomorrow.
edit: Think you should for your own sake update your initial post, concerning boot process and rightsmanagement.
Further visitors won't follow the whole thread and'll bomb you with questions.
B-44 said:
"error" may be the wrong word.
The problem had been discussed in the thread i have linked above.
Again: it may be interesting to know the date of release.
Click to expand...
Click to collapse
Oh, by error I meant I received an error message when trying to do the install the way I had tried it. I will read the new information posted here, thanks all.
Finished installation yesterday, everything was fine, quick'n'clean when suddenly wifi stopped working.
Marvell shows error code 10 and winupdate seems to have installed a different adapter.
SD adapter same error.
Had a similar experience when i installed win7, but there i already had a restore point to return to,
and since then everything was fine.
Will make a clean reinstallation, and after adding the wififix disable wifi to avoid possible system updates
and create a basic restore point i can return to each time winupdate kills something.
Preview build 9879
Anyone managed to get the latest build to work. Mine gives a message that my display resolution is too low and stops the upgrade.
Shame really as this works very well on the Shift, and with rumours that win 10 could be free it would have been a good o/s for this computer.
Please post code 0f builtversion.
Build 9860

Categories

Resources