I tried to run flashtool with windows 8.1. But it doesn't work, any driver work. Even with windows 8. I don't know what to do. I olne have pc with windows 8 and windows 8.1. I need some help.
Maybe try the drivers from my signature.
Sent from note, a phone like never before
You can Use the search for answer's mate
http://forum.xda-developers.com/sitesearch.php?q=Drivers to xperia x10 in windows 8.1
I tried
doodownunda said:
You can Use the search for answer's mate
http://forum.xda-developers.com/sitesearch.php?q=Drivers to xperia x10 in windows 8.1
Click to expand...
Click to collapse
Well I tried, but i can't find any solution.
doodownunda said:
You can Use the search for answer's mate
http://forum.xda-developers.com/sitesearch.php?q=Drivers to xperia x10 in windows 8.1
Click to expand...
Click to collapse
Hi friend, it doens't work either.
I tried to updated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thisangels said:
I tried to run flashtool with windows 8.1. But it doesn't work, any driver work. Even with windows 8. I don't know what to do. I olne have pc with windows 8 and windows 8.1. I need some help.
Click to expand...
Click to collapse
This is very weird i have drivers issue in Windows XP Pro but the same device works flawless in Windows 8.1 Pro
Here is the link to the post that shows Flash Tool in Windows 8.1 Pro 32bit working fine.
http://forum.xda-developers.com/showpost.php?p=47736661&postcount=3
ronaksworld said:
This is very weird i have drivers issue in Windows XP Pro but the same device works flawless in Windows 8.1 Pro
Here is the link to the post that shows Flash Tool in Windows 8.1 Pro 32bit working fine.
http://forum.xda-developers.com/showpost.php?p=47736661&postcount=3
Click to expand...
Click to collapse
Well, I'm think the problem is that I use Windows 8.1 Single Language 64 bits. As you see in the next picture
thisangels said:
Well, I'm think the problem is that I use Windows 8.1 Single Language 64 bits. As you see in the next picture
Click to expand...
Click to collapse
I guess the problem must be with the 64bit of Win 8.1 as i didnt have any problem in 32bit 8.1 and win xp i get the same problem as u have in win8.1 x64 :silly:
Drivers i found that is being used by Xperia x10i are as fallow:
-------------------------------------------------
Android Composite ADB Interface
-------------------------------------------------
Drivers Provider : Google, Inc
Driver Date: 06-12-2010
Driver Version: 4.0.0.0
Digital Signer: JRD COMMUNICATION (SHENZHEN) LTD
---------------------------------------------------
SEMC File-CD Gadget USB Device
---------------------------------------------------
Drivers Provider : Microsoft
Driver Date: 21-06-2006
Driver Version: 6.3.9600.16384
Digital Signer: Microsfot Windows
-------------------------------------------------------------------
Microsoft Device Association Root Enumerator
-------------------------------------------------------------------
Drivers Provider :Microsoft
Driver Date: 21-06-2006
Driver Version: 6.3.9600.16384
Digital Signer: Microsoft Windows
-----------------------------------------------------------
Plug & Play Software Device Enumerator
-----------------------------------------------------------
UMBus Root Bus Enumerator
-----------------------------------------------------------
At last but not the least the one you looking for is below i have even attached the image when my phone was plugged to the computer and powerd off getting charged.
-------------------------------------------------------------------
Sony sa0102 ADB Interface Driver
-------------------------------------------------------------------
Drivers Provider : Sony
Driver Date: 07-03-2012
Driver Version: 2.0.10.30011
Digital Signer: Microsoft Windows Hardware Compatibility Publisher
-----------------------------------------------------------
ronaksworld said:
I guess the problem must be with the 64bit of Win 8.1 as i didnt have any problem in 32bit 8.1 and win xp i get the same problem as u have in win8.1 x64 :silly:
Drivers i found that is being used by Xperia x10i are as fallow:
-------------------------------------------------
Android Composite ADB Interface
-------------------------------------------------
Drivers Provider : Google, Inc
Driver Date: 06-12-2010
Driver Version: 4.0.0.0
Digital Signer: JRD COMMUNICATION (SHENZHEN) LTD
---------------------------------------------------
SEMC File-CD Gadget USB Device
---------------------------------------------------
Drivers Provider : Microsoft
Driver Date: 21-06-2006
Driver Version: 6.3.9600.16384
Digital Signer: Microsfot Windows
-------------------------------------------------------------------
Microsoft Device Association Root Enumerator
-------------------------------------------------------------------
Drivers Provider :Microsoft
Driver Date: 21-06-2006
Driver Version: 6.3.9600.16384
Digital Signer: Microsoft Windows
-----------------------------------------------------------
Plug & Play Software Device Enumerator
-----------------------------------------------------------
UMBus Root Bus Enumerator
-----------------------------------------------------------
At last but not the least the one you looking for is below i have even attached the image when my phone was plugged to the computer and powerd off getting charged.
-------------------------------------------------------------------
Sony sa0102 ADB Interface Driver
-------------------------------------------------------------------
Drivers Provider : Sony
Driver Date: 07-03-2012
Driver Version: 2.0.10.30011
Digital Signer: Microsoft Windows Hardware Compatibility Publisher
-----------------------------------------------------------
Click to expand...
Click to collapse
Well I don't know what to do. I'm going to look for a pc with windows 7. Thanks.
sir,maybe you can try this update for windows 8.1
link>>>>support.microsoft.com/kb/2917929
Tested working on windows 8.1 Enterprise N x86
ENJOY FLASHING....:good:
thisangels said:
I tried to run flashtool with windows 8.1. But it doesn't work, any driver work. Even with windows 8. I don't know what to do. I olne have pc with windows 8 and windows 8.1. I need some help.
Click to expand...
Click to collapse
Try to disable driver signature enforcement. This works for me in windows 8.1
Here are the steps
1. Access the charm bar or press window key + I
2. Click Change PC settings
3. Click Update and Recovery
4. Click Recovery
5. Click Restart Now on Advanced Startup
6. Click Troubleshoot
7. Click Advanced Options
8. Click Restart on Startup Settings
9. Press F7 (to disable driver signature enforcement.
After the pc restart, flashtool should be working with your device. Hope this helps. Good Luck!
Related
- Download Cloudyfa_ProphetTOOLS
- Extract the zip file, you'll have VistaDRIVER + VistaRUU
- Enter BootLoader
- Plug in your USB cable
- Right-click on Computer, chose Properties
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- On the top left conner, chose Device Manager
- Right-click on Microsoft USB Sync (or something similar in Mobile devices), chose Update Driver Software
- Then follow my mark on these pictures:
Done !!!
From now on, you can use the new tool (VistaRUU) to upgrade your device in Vista instead of old RUU files!
Note: The new RUU can work in Windows XP and Windows 7 as well. So people using XP, Win7 can update your tool if you like
For Vista 64 users, use this driver instead: Vista64_DRIVER
Remember to disable Driver Signing Enforcement (google for it)!
:-O
If this is working, u're my new idol man^^
Edit: can't use driver under vista x64 =(
x64 Vista and Win7 driver!
Thank you so much Cloudyfa. Your Method is working fine fo me.
vaothien said:
Thank you so much Cloudyfa. Your Method is working fine fo me.
Click to expand...
Click to collapse
of course . I have test it too a week ago.
Great Job from Cloudyfa. Like always.
Cloudyfa said:
That driver is for Vista32 You should try this! (I've not tested it yet)
Click to expand...
Click to collapse
Not working =(
Isn't recognized as a Win64 driver
ice8lue said:
Not working =(
Isn't recognized as a Win64 driver
Click to expand...
Click to collapse
Vista64 has strong security, you must disable driver signing enforcement to install the driver. You should search google to do that (i think it's easy for you as you chose to use Vista64 instead of Vista32 )
I did, but it doesn't work
Bagaimana mengupdate ROM HTC Prophet di Windows VISTA
Cloudyfa, I translated it into Indonesian languange
Langkah - langkah mengupdate ROM HTC Prophet dengan Windows Vista :
Download Cloudyfa_Prophet TOOLS
Extrak Zip file. Didalamnya kamu akan lihat VistaDRIVER + VistaRUU Folder
Masuk ke Mode BootLoader
Sambungkan device kamu dengan USB cable ke PC
Klik kanan di Computer, lalu pilih Properties
Dibagian kiri pilih Device Manager
Klik kanan di Microsoft USB Sync (atau juga mungkin Mobile devices), lalu pilih Update Driver Software
Lalu ikuti petunjuk melalui gambar berikut ini :
Selesai !!!
Mulai sekarang kamu bisa mengunakan (VistaRUU) untuk mengupdate device kamu di Vista ( dites pada VISTA 32 Bit) dengan RUU yang terbaru ini.
Catatan:RUU yang baru bekerja dengan baik di Windows XP juga. Jadi orang yang mengunakan Windows XP juga bisa mengupdate dengan RUU terbaru ini
All Credit for this Tools go to Cloudyfa
Is there any one test it on windows 7 beta build 7000? Can it work? Thanks
h2_viethoang said:
Is there any one test it on windows 7 beta build 7000? Can it work? Thanks
Click to expand...
Click to collapse
Opp, I have tested myself, this tool works well on Windows 7 Ultimate build 7000. Thanks for great tool.
ice8lue said:
I did, but it doesn't work
Click to expand...
Click to collapse
My friend tested it with his Vista64, it works for him, you should check all steps again!
varanusvincent said:
Cloudyfa, I translated it into Indonesian languange
Click to expand...
Click to collapse
Nice job, friend
h2_viethoang said:
Opp, I have tested myself, this tool works well on Windows 7 Ultimate build 7000. Thanks for great tool.
Click to expand...
Click to collapse
You're welcome!
h2_viethoang said:
Opp, I have tested myself, this tool works well on Windows 7 Ultimate build 7000. Thanks for great tool.
Click to expand...
Click to collapse
just tested on windows 7 ultimate build 7000 64bit with the vista64 driver even with teh driver signing enforcement being turn off the driver refuse to work it seems like it lack alot of files compare to the driver download from windows update...
Hi there.
Device Driver is not working with Vista X64 SP2 (Driver signing disabled)
The Devicemanager marks the Device with a yellow triangle with an exclamation mark inside.
The Driver details tell me that the Driver is damaged or not found (Code 39).
Regards,
Petros
Too bad that I've upgraded to Asus P535 .
I'll try it on my old prophet - hope it works on Vista x64.
Thanks you.
Hi everyone out there!
I have eagerly awaited a way to flash my Prophet under Vista!
I haven't dared to flash, I've just read all the wiki's and fourum posts so far.
The problem is as follows:
I don't have the Mobile Devices node in my device manager as it's shown in the guide.
Therefore I can't install the vista driver that I need.
I've fetched the installation for "Center for windows mobile units" and installed this.
First I thought that the missing node in device manager was because of missing syncronisation between my Prophet and my home computer but that was not the case.
Any suggestions out there!?
Please help!
Ohamn said:
The problem is as follows:
I don't have the Mobile Devices node in my device manager as it's shown in the guide.
Therefore I can't install the vista driver that I need.
Click to expand...
Click to collapse
Turn your mobile into bootloader (3 color screen) and plugin the USB Cable, wait a minutes and the Mobile device node will show in the Device manager.
hi Cloudyfa, thanks for this tutorial.
i've done your steps. looks like it can connect when i open romupdateutilityG3. now i want to install dioxda's rom, how do i do that with this? do i copy the contents of the 'rom' folder to vistaRUU folder?
h2_viethoang said:
Turn your mobile into bootloader (3 color screen) and plugin the USB Cable, wait a minutes and the Mobile device node will show in the Device manager.
Click to expand...
Click to collapse
Is there any way to exit boot loader mode once I have updated the drivers or do I have to flash my Prophet to exit boot loader!?
// Ohamn
Ohamn said:
Is there any way to exit boot loader mode once I have updated the drivers or do I have to flash my Prophet to exit boot loader!?
// Ohamn
Click to expand...
Click to collapse
Soft reset
Do you want a single file flashing tool?
Here it is!!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Update to version 2.1
- some bugs fixed
Update to version 2.2
-removed command line console
-added my own style console
-many optimizations
Update to version 2.3
-fixed ocazional bugs with exit button
-deny posibility to change settings when upgrade are running
Update to version 2.4.5
-Added warning and stop upgrade if hardSPL fail.
Update to version 2.5
-Added Tooltips and shorcut to Device Manager(to check correct prophet driver install during flash).
Update to version 2.6.5
-Added Menu on mouse right click to application dialog.
-Added minimize to try feature
-Added automatic check of prophet drivers installation feature.
-final version!
-no future update!
0. Copy the nk.nbf file in the same folder with this flashing tool
1. Select your phone type G3 or G4.
2. If you use windows Vista or Windows 7 check the Vista option.
3. If you have already HardSPL your phone please uncheck the HSPL option.
4. Press Start Button to start ROM Flashing.
For Vista or Windows7 you need to replace the drivers with corect one from attached files. It works for bouth operation systems.
If you have the 64-bit edition of Windows you must disable digital driver signing before you continue on! To do this, restart your computer. After the initial BIOS screen but before the Windows bootup splash screen, spam press F8 until you see a Windows menu. If you do not get a menu and end up in Windows you pressed F8 at the wrong time. Try it again until you get the menu. In the menu select Disable Driver Signature Enforcement or Disable Digital Driver Signing (depending on your version of Windows). Windows will finish booting up and you can continue on.
More info about drivers installation here...
You don't need any other file to flash the ROM!!!!!!!!!
Sounds good! Will test it and if it's working good, I'll add it to my own ROMs!
Thanks for this i will test this asap
Please some feedback.
Thanks!
Nice...
Good idea to make it simpler...
Thanks much bikertibi for your sharing
bikertibi said:
For Vista or Windows7 you need to replace the drivers with corect one from attached files. It works for bouth operation systems.
Click to expand...
Click to collapse
I'm using win7 and just installing Windows Mobile Device Center. Which driver should I replace ?
me_devilgrey said:
I'm using win7 and just installing Windows Mobile Device Center. Which driver should I replace ?
Click to expand...
Click to collapse
After the hardSPL is done windows search for new drivers on the net. If you have an internet connection a bed drivers are installed. You must replace this driver and I remember the name is "PocketPC USB". The driver is the same in case of three color booting
bikertibi said:
After the hardSPL is done windows search for new drivers on the net. If you have an internet connection a bed drivers are installed. You must replace this driver and I remember the name is "PocketPC USB". The driver is the same in case of three color booting
Click to expand...
Click to collapse
Cool.. i'm trying to flash dopod 818 but still not sure since i upgraded to win 7, now i guess i'll try WM6.5 Build 23003 WWE bikertibi edition too. Thx..
me_devilgrey said:
Cool.. i'm trying to flash dopod 818 but still not sure since i upgraded to win 7, now i guess i'll try WM6.5 Build 23003 WWE bikertibi edition too. Thx..
Click to expand...
Click to collapse
I tested win 7 for flashing and works great....
working fine with WM6.5 Build 23003 WWE bikertibi edition flashing with win 7. Great job!
bikertibi said:
For Vista or Windows7 you need to replace the drivers with corect one from attached files. It works for bouth operation systems.
Click to expand...
Click to collapse
What do you mean by "to replace"? Simply to overwrite the driver files on the disk with the files from archive? I have Vista with already installed and running Mobility center. I tried to update the driver by pointing to the new drivers - system says I heve the latest drivers... I tried to install new drivers by clicking the inf files - got the message that it can't be installed in sucha a way...
Looks it is nice tool, but my knowledge probably is not enought..
Thanks in advance.
ZRimaZ said:
What do you mean by "to replace"? Simply to overwrite the driver files on the disk with the files from archive? I have Vista with already installed and running Mobility center. I tried to update the driver by pointing to the new drivers - system says I heve the latest drivers... I tried to install new drivers by clicking the inf files - got the message that it can't be installed in sucha a way...
Looks it is nice tool, but my knowledge probably is not enought..
Thanks in advance.
Click to expand...
Click to collapse
You have to make an upgrade to the already installed drivers by selecting the upgrade option in the hardware manager. After that you must select "manual pick" and "I have location" to point to the working driver. Remember that you need to replace only the driver active in the upgrading process (in the tree color state or after hard SPL)
Great job, thanks.
Gran trabajo, gracias.
Update first post
Update to version 2.1. Fixed some bugs..
Am having problems when flashing some times it works some times it wont the problem is after hardspl and the Device has white screen the update software comes up good but every time it trys to seach for the version of the os on my Devive it scans but then i get error cant continue phone not connected after hardspl active sync dont detect the phone anymore thats noumal right? its saying Not Connected after hardspl with white screen why wont it update? and yes i tryed both versions still the same problem please help thanks
lyndel4 said:
Am having problems when flashing some times it works some times it wont the problem is after hardspl and the Device has white screen the update software comes up good but every time it trys to seach for the version of the os on my Devive it scans but then i get error cant continue phone not connected after hardspl active sync dont detect the phone anymore thats noumal right? its saying Not Connected after hardspl with white screen why wont it update? and yes i tryed both versions still the same problem please help thanks
Click to expand...
Click to collapse
Is normal to disconnect activesync after hardspl because it change the phone state to update drivers. Sometime if you don't have finished the activesync connections steps, after hardspl, the updating program repport imposibility to connect. Don't worry. Exit updating program without close the "Update Prophet" program and make again all steps for upgrading (select g3 or g4 model always, if it is already selected too, select hspl option) and start a new upgrading, ignore copy warning with "cancel". Normaly the update process will start again and report corrected connection for upgrade.
Thanks al try that but after that error active sync wont find it and the update software aswell so i always have to reset my device first then flash but yes al keep on trying I suspect it must be a software thats interupting the upgrade maybe i should close down all my programs first before upgrade to prevent this problem the only program i got is IM Clients and Firefox browser plus Windows Defender al try it and let you know because those applications could be interupting the update process. Thanks again
bikertibi, does this work like Lazy Tool too?
clustered said:
bikertibi, does this work like Lazy Tool too?
Click to expand...
Click to collapse
For me i find its just like lazy tool only it has a GUI lazy tool is only command line DOS so use it I get no problems
I ran v2.1 on Windows7 x64 (b7100) with installed Vista64_DRIVER.
Signing drivers was turned off, test mode (for OS) was turned on.
But unsuccessfull: RUU still crash.
See details in this screenshot:
http://s1.sendpic.ru/111214.jpeg.html
BTW, is it significant that "sleep4.exe" is "not compatible" or not?
Because I think that there is something wrong with Vista64_DRIVER driver.
Any solutions?
Hi everyone,
It seems like windows 8.1(pro preview) has some problems with the fastboot/flashmode (pc dosent recognise the phone) so we can not flash any kernel or ftf.
If anyone knows the fix for this,then please tell me
Thank you.
#include <std_disclaimer.h>
/*
* I have searched but no proper solution is found,which is actually applicable to 8.1
* I have google usb driver,flashtool,pc companion,sus,jre,jdk installed(environment variable set)
* I have installed fastboot flashmode drivers for xpeia devices they are properly installed(driver signature enforcement disabled)
* But still the winodws does not recognise usb when trying to connect in fastboot/flashmode
*/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i too searched lots of threads in xda and pages in google ... no solution so i stop flashing kernels and trying new roms because i don't wanna reinstall win 7 on my pc
deepakpunjabi said:
Hi everyone,
It seems like windows 8.1(pro preview) has some problems with the fastboot/flashmode (pc dosent recognise the phone) so we can not flash any kernel or ftf.
If anyone knows the fix for this,then please tell me
Thank you.
#include <std_disclaimer.h>
/*
* I have searched but no proper solution is found,which is actually applicable to 8.1
* I have google usb driver,flashtool,pc companion,sus,jre,jdk installed(environment variable set)
* I have installed fastboot flashmode drivers for xpeia devices they are properly installed(driver signature enforcement disabled)
* But still the winodws does not recognise usb when trying to connect in fastboot/flashmode
*/
Click to expand...
Click to collapse
For now back to windows oryginal not beta etc
deccen90 said:
i too searched lots of threads in xda and pages in google ... no solution so i stop flashing kernels and trying new roms because i don't wanna reinstall win 7 on my pc
Click to expand...
Click to collapse
seriously :angel:
i am also on jelly dream 5.0 from long time because of this reason
i am not gonna reformat to w8..may be i ll flash from my friends laptop
deepakpunjabi said:
seriously :angel:
i am also on jelly dream 5.0 from long time because of this reason
i am not gonna reformat to w8..may be i ll flash from my friends laptop
Click to expand...
Click to collapse
Almost 45 days I'm on xperia revelation hd and lupus kernel now I'm trying anzumi rom
try to change the usb driver, i don't have the link sorry but it work for me
something like change the windows usb driver to intel usb driver...
try to search on htc section...
Sent from my Xperia Neo V using CM10
XII KAITO said:
try to change the usb driver, i don't have the link sorry but it work for me
something like change the windows usb driver to intel usb driver...
try to search on htc section...
Sent from my Xperia Neo V using CM10
Click to expand...
Click to collapse
you mean it works on 8.1 preview?
deepakpunjabi said:
you mean it works on 8.1 preview?
Click to expand...
Click to collapse
Sorry for late reply
I'm not sure about if it works on 8.1...
The solution :
http://forum.xda-developers.com/showthread.php?t=2256359
XII KAITO said:
Sorry for late reply
The solution :
http://forum.xda-developers.com/showthread.php?t=2256359
Click to expand...
Click to collapse
it won't work it's only for win8 not for win 8.1 blue... we must wait for official win 8.1 after that we can expect drivers availability or comparability
But I thought it just driver's problem, so I just give a suggest
Anyway @deepakpunjabi you can try it as well
BTW @deccen90 is this shared on Neo V section? If not mind me or you to share this?
XII KAITO said:
But I thought it just driver's problem, so I just give a suggest
Anyway @deepakpunjabi you can try it as well
BTW @deccen90 is this shared on Neo V section? If not mind me or you to share this?
Click to expand...
Click to collapse
It's supposed for u.. Your correct it's driver problem, we need official 8.1 for working
mine same problem with windows 8.1 and flashtool
usb driver installed successfully but:
xperia Ion power off and volume down + plug = windows cannot recognize device.... => cannot flash tft
turned on and flashtool log: root access denied (SU still allows uninstall master, root browser, greenify... ) => cannot flash kernel
XII KAITO said:
But I thought it just driver's problem, so I just give a suggest
Anyway @deepakpunjabi you can try it as well
BTW @deccen90 is this shared on Neo V section? If not mind me or you to share this?
Click to expand...
Click to collapse
i know there is solution for pc/laptops having usb 3.0 ports
but unfortunately my pc dosent have usb 3.0 port
deccen90 said:
It's supposed for u.. Your correct it's driver problem, we need official 8.1 for working
Click to expand...
Click to collapse
thats right..in preview pack..microsoft has not installed all the drivers
so we have to either downgrade to windows 8 or wait untill 8.1 officially arrives(which is supposed to be october)
Xperia neo V not recognized in Official Windows 8.1 Pro RTM
deepakpunjabi said:
thats right..in preview pack..microsoft has not installed all the drivers
so we have to either downgrade to windows 8 or wait untill 8.1 officially arrives(which is supposed to be october)
Click to expand...
Click to collapse
Im running Official windows 8.1 Pro RTM but i still have same problem with my xperia neo v being not recognized i also disabled driver signature and installed SUS and PC companion, flash tool and also generic USB ADB but still same problem exist.. thankfully i have dual boot windows 7 :laugh: on my PC. Way back when im using the official Windows 8 Pro i dont have problems with android USB drivers like fastboot and ADB..
microchip88 said:
Im running Official windows 8.1 Pro RTM but i still have same problem with my xperia neo v being not recognized i also disabled driver signature and installed SUS and PC companion, flash tool and also generic USB ADB but still same problem exist.. thankfully i have dual boot windows 7 :laugh: on my PC. Way back when im using the official Windows 8 Pro i dont have problems with android USB drivers like fastboot and ADB..
Click to expand...
Click to collapse
Official 8.1 ??? yet to be released ... Dual boot is also good option
deccen90 said:
Official 8.1 ??? yet to be released ... Dual boot is also good option
Click to expand...
Click to collapse
Official version already leak bro
[URL=http://imageshack.us/photo/my-images/11/0fb8.png/]
Uploaded with ImageShack.us[/URL]
Wow could you provide key... In pm or link
microchip88 said:
Official version already leak bro
[URL=http://imageshack.us/photo/my-images/11/0fb8.png/]
Uploaded with ImageShack.us[/URL]
Click to expand...
Click to collapse
leaked versions are also beta!
i think official release will have all the drivers!!
till then..ICS rox! /sarcasm
deepakpunjabi said:
leaked versions are also beta!
i think official release will have all the drivers!!
till then..ICS rox! /sarcasm
Click to expand...
Click to collapse
haha this is not beta Build bro.. just accept the reality :good:
like many, i am getting this error. i have a built PC with a Ryzen 7 2700X. I think there might be a BIOS setting to enable TPM, but I haven't checked yet. Anyone else run into this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is the link to the Windows 11 compatibility checker:
Meet Windows 11: The Newest Windows Version
Meet Windows 11, the newest Windows version from Microsoft. Upgrade your PC to Windows 11, or explore which devices come equipped with its versatile features.
www.microsoft.com
Maybe you need to enable it on the BIOS. UEFI or Legacy?
Just run tpm.msc and it should give you status of TPM. If your PC supports it and it's in disabled state you can enable it from BIOS as earlier post suggests
Not sure which MBD you have but it's in the BIOS for sure. I had to search to find it on my ASUS MBD.
I'm excited to try windows 11 but my machine is very old i7-4720 and don't have TPM 2.0, i know there is workaround, when i saw the UI and android app via amazon store will be available later, i'm very excited.
Is there anyone try windows 11 without TPM 2.0 with just modified registry in set up installer? (without replace dll or install.wim/esd)
Windows 11 installed fine on my cheap HP desktop.
sd_shadow said:
Windows 11 installed fine on my cheap HP desktop.
View attachment 5350975
Click to expand...
Click to collapse
What processor does your desktop have? I have an Intel i5 7th Gen and the PC Health Check says I'm not compatible....
I am using ryzen 5 2500u based netbook and it supports tpm 2.0 (checked using tpm.msc) but still compatibility checker says cannot run w11
Did you try WhyNotWin11? It says exactly what is missing based on the official release. Download it from here.
Cheers.
svetius said:
like many, i am getting this error. i have a built PC with a Ryzen 7 2700X. I think there might be a BIOS setting to enable TPM, but I haven't checked yet. Anyone else run into this?
View attachment 5350745
this is the link to the Windows 11 compatibility checker:
Meet Windows 11: The Newest Windows Version
Meet Windows 11, the newest Windows version from Microsoft. Upgrade your PC to Windows 11, or explore which devices come equipped with its versatile features.
www.microsoft.com
Click to expand...
Click to collapse
You need to enable fTPM in BIOS. It's somewhere in Security or Advanced section in your BIOS. I had to do the same with 3600.
Not all CPUs are compatible with that, and not all the manufacturers give the option to enable TPM. Lets bypass it, shall we? Create a new txt file anywhere on your pc and open it. After that, add the following lines:
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\Setup\LabConfig] “BypassTPMCheck”=dword:00000001 “BypassSecureBootCheck”=dword:00000001
Save the file, and then rename it, just remove the "txt" and replace it with "reg". Open the file and BOOM. The setup should work.
22naresn said:
What processor does your desktop have? I have an Intel i5 7th Gen and the PC Health Check says I'm not compatible....
Click to expand...
Click to collapse
Processor Intel(R) Core(TM) i3-7100 CPU @ 3.90GHz 3.90 GHz
Installed RAM 8.00 GB (7.90 GB usable)
22naresn said:
Did you try WhyNotWin11? It says exactly what is missing based on the official release. Download it from here.
Cheers.
Click to expand...
Click to collapse
I used that too to check compatibility.
Yea I've seen that, it came up after it ran a check to see if I can upgrade and said my puter wasn't able to get Win 11....
Funny thing is I'm already running Windows 11 so not sure how to explain that....
1: Create your own installation media
2: The steps necessary to remove the "Secure Boot" and "TPM 2.0" requirements error when attempting to install Windows 11
3: Obtain the newest available Windows 10 ISO from Micro$0ft;
Already have made your Windows 11 USB Installer using Rufus;
Mount Windows 10 ISO;
Find and locate the folder named Sources on the mounted ISO;
Copy all of the files in the Sources folder of the mounted ISO except for install.wim/install.esd;
Navigate to the Windows 11 bootable USB Installer that you have previously created in your File Manager;
Open the Sources folder on the Windows 11 bootable USB Installer;
Paste the previously copied contents/files from the Sources folder on the mounted Win 10 ISO to the Sources folder of the Windows 11 bootable USB Installer, and make sure to replace the files present in the Windows 11 USB Installer Sources folder;
Boot from Windows 11 USB Installer;
Profit from not having the requirements of Secure Boot and TPM 2.0 being enabled in place.
For more deatils hereis detailed tutorial. Link.
Interesting. Has anyone actually tried this method with success?
I'll give it a try
I remember very similar pains when Windows 10 first released. I think everything will be fine for the most part as long as your machine can run Windows 10. Not much is different between the two.
Thank you thank you thank you I thought I was screwed too I've got an old optiplex 790 with a Intel i5 4 series and I just booted all I did was change the registry through the BIOS on the front end during the install which means I made the ISO file for USB UEFI boot I got the error saying that my machine hardware was not suitable for Windows 11 so I hit shift and F10 to command prompt and entered notepad because I already copied the registry into a text document that's accessible from the file menu in the notepad never done that before and that was pretty cool..copied it and then went back to the command prompt and went to the regedit.exe... copy what I had on the the text document into the actual local registry and then started the install process all over and Golden... I had to actually download the ISO file from Android host file of all places checksum good worked out everything's even better when I can beat the status quo
svetius said:
Interesting. Has anyone actually tried this method with success?
Click to expand...
Click to collapse
I am using it through leaked win 11 iso
My dear users,
As soon as I ran TronScript (r/tronscript) with the auto restart option, I received a message stating that Windows could not boot. After loading Hiren's Boot CD into my Ventoy drive, it now says "Your PC could not start properly" with error code 0x0000001.
The following are the contents of my Ventoy drive:
A boot CD for Hiren is included,
This is HP.
Windows 11 Installation media.
I would appreciate any help you could provide to fix my computer as soon as possible.
woodalexa7878 said:
My dear users,
As soon as I ran TronScript (r/tronscript) with the auto restart option, I received a message stating that Windows could not boot. After loading Hiren's Boot CD into my Ventoy drive, it now says "Your PC could not start properly" with error code 0x0000001.
The following are the contents of my Ventoy drive:
A boot CD for Hiren is included,
This is HP.
Windows 11 Installation media.
I would appreciate any help you could provide to fix my computer as soon as possible.
Click to expand...
Click to collapse
Run Startup Repair from a recovery disc. If you do not have a recovery disc, you can use installation media.
By means of RUFUS create a bootable USB-stick containing the Windows version / edition you want to have installed and boot from USB-stick created to install it.
Since you have Ventoy, you could try booting from the Hiren live CD and try to download a fresh copy of Win11 over wayback (if your pc has nothing of important in it), even tho firsthand it could be better to get another spare usb stick and flash Ventoy on it all over again and then paste the win11 iso file over the brand new usb stick.
In case there's personal data you'd like to save over the C:/ drive, using any linux live usb iso could be of help on mounting the partition and save whatever you could find on another removable media.
Wondering why Hiren’s BootCD PE (Preinstallation Environment) should get used: it's based on Windows 10 PE x64. There are no official updates after November 2012.
xXx yYy said:
Wondering why Hiren’s BootCD PE (Preinstallation Environment) should get used: it's based on Windows 10 PE x64. There are no official updates after November 2012.
Click to expand...
Click to collapse
2021 ..
https://www.hirensbootcd.org/files/HBCD_PE_x64.iso
xXx yYy said:
Wondering why Hiren’s BootCD PE (Preinstallation Environment) should get used: it's based on Windows 10 PE x64. There are no official updates after November 2012.
Click to expand...
Click to collapse
If that won't go (also, disregarding the whole update cycle...i'm sure 2012 wasn't even the date of release for win10, let alone a forked version), then a linux live usb iso should directly be of help.
Updates, EOLs versions, and whatever stay out of the question since here it's about restoring a pc to it's former state.
Since it's all a matter to use the ruined machine's specs as a host for running a live iso and grab a win11 iso off the internet and drag it on another usb flash drive (with Ventoy installed aswell):
then what matters is that the machine gets saved and that win11 gets restored back.
IMO it never does make sense to make use of a Windows Recovery Environment ( WinRE ) - what Hiren's PE by nature is - to repair a corrupted Windows OS, because user most times doesn't know 1. what the error code reported by Windows means - as that's the case here, and 2. what 3rd-party app of those dozens that came bundled with Hiren's PE ( see here: https://www.hirensbootcd.org/hbcd-v120/ ) lastly to use to fix the given problem : Re-installing Windows OS from the scratch is the only time-saving method I know of to immediately have a properly running Windows machine. And this is correctly done by a Windows Preinstallation Environment ( WinPE ) what supports these features
Batch files and scripts, including support for Windows Script Host (WSH), and ActiveX Data Objects (ADO), and optional support for PowerShell.
Applications, including Win32 application programming interfaces (APIs) and optional support for HTML Applications (HTA).
Drivers, including a generic set of drivers that can run networking, graphics, and mass storage devices.
Image capturing and servicing, including Deployment Image Servicing and Management (DISM).
Networking, including connecting to file servers using TCP/IP and NetBIOS over TCP/IP via LAN.
Storage, including NTFS, DiskPart, and BCDBoot.
Security tools, including optional support for BitLocker and the Trusted Platform Module (TPM), Secure Boot, and other tools.
Hyper-V, including VHD files, mouse integration, mass storage and network drivers that allow Windows PE to run in a hypervisor.
and more aren't in fact needed.
Better going straight to the point and reinstall win11 fresh (like i mentioned before) since the message given by OP's machine just went:
"Your PC could not start properly"
Since OP did mention it has a "Windows 11 Installation media" inside their Ventoy stick, they could try to solve it that way by doing the whole booting process again.
If the Installation Media won't go, then it's better taking a win11 .iso on the go (of course, again, using a spare usb. Would spare making this message longer).
Xploit Machine said:
2021 ..
https://www.hirensbootcd.org/files/HBCD_PE_x64.iso
Click to expand...
Click to collapse
As I can see the versions 2012 and/or 2021 - you linked to - differ only in amount of bundled 3rd-party progs ( mostly freeware ). But this wasn't the point.
Hello,
As soon as I also ran TronScript (r/tronscript) with the auto restart option, I received a message stating that Windows could not boot. After loading Hiren's Boot CD into my Ventoy drive, it now says "Your PC could not start properly" with error code 0x00001.
Error code 0x00001 ( 0x0000001 ? ) usually occurs when Windows PC users attempt to update or install a Windows OS on their devices. Make use of the Windows built-in System File Checker function to deal with your issue.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}