Database Develop

HOW TO: Webtop 2.3.4 HKTW fix

Tested and works (thanks jnl) I'm posting a link to CG61.img for easy loading extracted from 1FF-olympus_hktw-userdebug-2.3.4-4.5.2A-5_OLH-3-110614-test-keys-Retail-05.sbf
Download moto-fastboot for your os from http://forum.xda-developers.com/showthread.php?t=1138092
CG61.img Link - MD5 = 9151fca5183b85953d7afed83364802a
https://www.rapidshare.com/files/4119742271/CG61.img
Steps I followed on OSX:
Download CG61.img (placed in same directory as moto-fastboot)
Place your device in fastboot mode via the volume-down then volume-up procedure and verify it exists with ./moto-fastboot devices
./moto-fastboot flash webtop CG61.img
./moto-fastboot reboot
You might have to reboot the device 2X after this is complete before the webtop option shows up when docked
----=== NO NEED TO FOLLOW THE BELOW STEPS UNLESS YOU EXTRACT FROM THE SBF ===----
Below is from JNL:
Since I have the lapdock and did not want to revert to Froyo, I thought I'd give a more detailed explanation than the hint I worked from to re-enable webtop (with firefox 4.0.1!):
Download the leaked HK/TW sbf file and the 'sbf_flash' for linux (I did this under 32-bit ubuntu).
use sbf_flash -x 1FF-olympus_hktw...sbf
This will extract a collection of .img files.
Place your device in fastboot mode via the volume-down then volume-up procedure and verify it exists with:
sudo ./moto-fastboot32 devices
Then:
sudo ./moto-fastboot32 flash webtop CG61.img
This will run a 3-step flashing process. Once completed, do:
sudo ./moto-fastboot32 reboot
Voila. Webtop works and actually seems faster.
Hope this helps.

mburlingame said:
Steps I followed:
Download CG61.img
./moto-fastboot devices
./moto-fastboot flash webtop CG61.img
./moto-fastboot reboot
Click to expand...
Click to collapse
actually, just to clarify... is that in cmd on windows you're talking about? Where do we put the CG61.img?

s1mpd1ddy said:
actually, just to clarify... is that in cmd on windows you're talking about? Where do we put the CG61.img?
Click to expand...
Click to collapse
I ran this from OSX using the commands I listed jnl ran it from 32-bit ubuntu it looks like via the commands he posted
I placed the image in the same directory as moto-fastboot

Looking at the commands, it is for Linux. Get a Ubuntu LiveCD, very useful tool to have around.
Sent from my MB860 using XDA App

sifon187 said:
Looking at the commands, it is for Linux. Get a Ubuntu LiveCD, very useful tool to have around.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I am guessing this should work in Windows as well I am currently installing Windows 7 under VMware Fusion on my mac to confirm.
confirmed I could run this from Windows and did not get any errors back so performing this via the windows moto-fastboot should work as expected

Updated CG61.img link from DropBox to RapidShare due to DropBox shutting the link down due to excessive downloads (according to them)

So, I did the 1st step and nothing happened.
Do I have to do the 2nd step? If yes, where I find "sbf_linux" and "1FF-olympus_hktw...sbf"?

brunnogama said:
So, I did the 1st step and nothing happened.
Do I have to do the 2nd step? If yes, where I find "sbf_linux" and "1FF-olympus_hktw...sbf"?
Click to expand...
Click to collapse
You only need to follow the first section (Download the img file and download moto-fastboot for your os)
Are you saying that after you download the img and run moto-fastboot devices you do not see your device listed?
Can you post exactly whats happening when you run moto-fastboot devices then try to load the image on your device via moto-fastboot flash webtop CG61.img (make sure CG61.img is in your moto-fastboot directory)

So, I did everything again, and it´s still doesnt working.
No one errors appears. But when a plug phone on lapdock, doenst show the webtop´s option. when I execute them, appears an error: "This app Webtop.... has stopped unexpctedly..."
My log:

brunnogama said:
So, I did everything again, and it´s still doesnt working.
No one errors appears. But when a plug phone on lapdock, doenst show the webtop´s option. when I execute them, appears an error: "This app Webtop.... has stopped unexpctedly..."
My log:
Click to expand...
Click to collapse
Are you running the HKTW 2.3.4 image? ( Image from the following thread http://forum.xda-developers.com/showpost.php?p=15020775&postcount=2 )

Yes! I do!
It isnt correct?

brunnogama said:
Yes! I do!
It isnt correct?
Click to expand...
Click to collapse
Hmm yes that is correct - Can you tell me what OS you are using? maybe try another USB port I will do an md5 checksum on the file and post it maybe a bad download?
MD5 = 9151fca5183b85953d7afed83364802a

Did everything correct... Pretty damn sure. Phone won't even power up now.
Pull battery, plug back in usb cable, get green light, it goes out. Got it to fire up once with no sim.
F*ck !
EDIT: Dumb ass. Don't know how battery drained like a MF. Powered up in wall jack.

So, I´m using Windows 7 32.
I tried another port, tried new flash and nothing.. I´still having the same error when I execute webtop.
:/

brunnogama said:
So, I´m using Windows 7 32.
I tried another port, tried new flash and nothing.. I´still having the same error when I execute webtop.
:/
Click to expand...
Click to collapse
Hmm I have not been able to duplicate this issue - Can you confirm the MD5 checksum? Has anyone else seen this issue with Windows 7 and trying to flash this?

does this fix multimedia dock too? i dont get clock option when my phone is on the dock.

So, I tried on Ubuntu and doenst change anything. I still havent the webdock.
I have the clock issue too. When I plug on lapdock, the clock doenst fit on horizontal position.

Does this work with hdmi cable without any dock?

xabierd said:
Does this work with hdmi cable without any dock?
Click to expand...
Click to collapse
No this requires the Media Dock or the Laptop dock in order to work

Any chance to get the Debian 0.2.5 Webtop back?
Cheers

[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?

Teclast X80 Pro (E3E6) Dual OS (Win10/Android 5.0): Remove Windows

Hey guys. Sorry to bother you in the X98 section, but since there's no section for the X80 yet and maybe the devices have some similarities, I hope it's ok.
The tablet worked fine, but to remove any possible bloatware under Windows or Android, I reset Windows. Somehow the device must have crashed (low battery?) and now I can't boot to Windows anymore (black screen and / or boot loop). Of course I made no backup / recovery disk. Android still works fine and I still get into BIOS / UEFI.
I tried reinstalling Windows via OTG with USB stick. I got to the point where I can choose a partition. Problem is, there are lots of partitions (Android, recovery, System and so on). I located the Windows partition, formatted / deleted it and tried to reinstall Windows on this partition. Just the exact way I would do it on a PC. Somehow it won't install on this partition. The error message says something about "the partitions are not in the recommended order. Further information for installation on GPT-volumes..." (I don't know the exact English phrasing because everything is in German). I chose "continue anyway". Then I get the message that "the EFI-system is not formatted in NTFS. Format the partition to FAT32 and start install procedure again". I press ok and get back to Windows Setup (Install now).
I also tried different repair and recovery options. One time I got error code 0xC0000034. Funny thing is, Windows still seems to be there because while trying to repair / recover I tried to load some drivers and could see the hard drives and folders under Windows.
I tried downloading the original roms here: http://pan.baidu.com/s/1qYEa8gc
You need a Baidu account for the larger files and after days and days I gave up to create such an account as it seems to work only with a mainland China number. There's an option for oversea mobiles but that's not working. I tried a QQ-account, but Baidu wants to link with it and you need that telephone number again. So apparently there's no way to get the original files that way.
I found some stuff here: http://www.needrom.com/download/teclast-x80-pro-dualboot/ but that's only a tutorial file in Chinese and some flash programms / drivers (also got them from Baidu - smaller files are possible to download without an account).
Long story short: I guess recovering Windows 10 is too much effort, so I want to make the tablet Android only and of course want to use the whole capacity for Android. I found a thread on reddit about removing Windows on the X98: https://www.reddit.com/r/teclast/comments/479eua/teclast_x89_how_to_remove_windows_10/
But I have no idea which partitions are definitely needed for Android and which ones I can safely delete. I found a partition map here: http://wheresmykeyboard.com/2015/08/teclast-x98-air-64gb-dual-boot-default-partition-map/ but that doesn't help me that much because they look different.
Attached you will find a photo of all the partitions on my device. I guess there are some which were created during the failed Windows installation because I had about 20 GB free space and now only 17.7 GB.
So is there anybody out there who knows if it's possible to remove Windows completely and which partitions I have to delete?

Did you ever figure this out? I just bought an X80 Pro and was thinking of doing something similar since I plan on making it an android-only tablet.

Deathgazer said:
Did you ever figure this out? I just bought an X80 Pro and was thinking of doing something similar since I plan on making it an android-only tablet.
Click to expand...
Click to collapse
Hi. Sorry for the late replay. Yes, I figured it out and my X80 Pro is now running Android-only with 32 GB. In the end, it wasn't that hard but a long way to success.

metalaxi said:
Hi. Sorry for the late replay. Yes, I figured it out and my X80 Pro is now running Android-only with 32 GB. In the end, it wasn't that hard but a long way to success.
Click to expand...
Click to collapse
Please do describe how you achieved Android-only with 32 GB memory
Cheers

metalaxi said:
Hi. Sorry for the late replay. Yes, I figured it out and my X80 Pro is now running Android-only with 32 GB. In the end, it wasn't that hard but a long way to success.
Click to expand...
Click to collapse
Yes please tell us how metalaxi , it'll be much appreciated.:good:

Ok, guys. Since some of you are asking how I did it, I'm going to try to explain it. It's kinda embarrassing that I don't remember the exact way but I hope it helps somehow. I used the tutorial from this site: http://techtablets.com/forum/topic/x80-plus-android-os-only/#login
Even though it's supposed to be for the Plus model, it also worked on the Pro. Btw, the guy Alex in that thread is me .
You can download all the files from my Google Drive here: https://drive.google.com/open?id=0BxEFqy4Rt9w_cnh3VG9ySk5sOHM
You need
- Android5.1 Upgrade Tool.rar
- X80 Pro (E3E6)- Dual OS - Android5.1-V1.04 Firmware.rar
- gpt.rar (Credit goes to Allember @techtablets-forum; hope it's ok to spread the file)
First you have to install the flash tool. Unrar the firmware and replace the gpt.bin. Then flash the firmware by checking BLANK.
Problem is that when I did all that, my Windows was already crushed and wasn't working anymore. I can't remember anymore if I erased the Windows partitions or any others beforehand. If you're not interested in Windows anymore, just flash it without changing or erasing any of the partitions. I guess by replacing the gpt-file, you do all that automatically.
I hope this somehow helps you. Feel free to ask for more help.
Have a good night!

metalaxi said:
Ok, guys. Since some of you are asking how I did it, I'm going to try to explain it. It's kinda embarrassing that I don't remember the exact way but I hope it helps somehow. I used the tutorial from this site: http://techtablets.com/forum/topic/x80-plus-android-os-only/#login
Even though it's supposed to be for the Plus model, it also worked on the Pro. Btw, the guy Alex in that thread is me .
You can download all the files from my Google Drive here: https://drive.google.com/open?id=0BxEFqy4Rt9w_cnh3VG9ySk5sOHM
You need
- Android5.1 Upgrade Tool.rar
- X80 Pro (E3E6)- Dual OS - Android5.1-V1.04 Firmware.rar
- gpt.rar (Credit goes to Allember @techtablets-forum; hope it's ok to spread the file)
First you have to install the flash tool. Unrar the firmware and replace the gpt.bin. Then flash the firmware by checking BLANK.
Problem is that when I did all that, my Windows was already crushed and wasn't working anymore. I can't remember anymore if I erased the Windows partitions or any others beforehand. If you're not interested in Windows anymore, just flash it without changing or erasing any of the partitions. I guess by replacing the gpt-file, you do all that automatically.
I hope this somehow helps you. Feel free to ask for more help.
Have a good night!
Click to expand...
Click to collapse
Hi @metalaxi. Do you think its possible to like "reverse" and use the same files to remove Android instead and maintain the Windows 10? Appreciate to hear from you. Thanks!

Do we have to change the gpt before doing what you said in your PDF? Or I have just to follow your PDF?

Hi guys, got mine a few months and want to get rid of the Windows part, but the instructions are insufficient for a joker like me.....
1. Download the firmware, its 4 parts of rar being zipped together
2. flash the firmware HOW?!?!?! I have no Idea...... please give us some closer instructions.

reycharlesconrad said:
Hi @metalaxi. Do you think its possible to like "reverse" and use the same files to remove Android instead and maintain the Windows 10? Appreciate to hear from you. Thanks!
Click to expand...
Click to collapse
Sorry, I can't answer that sufficent enough. As far as I know, you can just delete all partitions except the ones from Windows. Then format the unallocated space and merge it with the one from Windows. No guarantee!

dirkzelf said:
Hi guys, got mine a few months and want to get rid of the Windows part, but the instructions are insufficient for a joker like me.....
1. Download the firmware, its 4 parts of rar being zipped together
2. flash the firmware HOW?!?!?! I have no Idea...... please give us some closer instructions.
Click to expand...
Click to collapse
1. Which 4 parts do you mean?
2. To flash any firmware, you need to install all the upgrade tools:
IntelAndroidDrvSetup1.5.0
iSocUSB-Driver-Setup-1.2.0
PhoneFlashTool_5.3.4.0_internal_win32

metalaxi said:
1. Which 4 parts do you mean?
2. To flash any firmware, you need to install all the upgrade tools:
IntelAndroidDrvSetup1.5.0
iSocUSB-Driver-Setup-1.2.0
PhoneFlashTool_5.3.4.0_internal_win32
Click to expand...
Click to collapse
it's too long ago, so I don't know what I exactly did there, but since there was no reply for a long time, I just took a shot and worked out well, now I have an Android only tablet.
I just got lucky I guess....

partition help
Hi, please help.
I have x80pro e3e8
I managed to erase a complete disk partition.
You are trying to revive again, fail.
installed here:
iSocUSB-Driver-Setup-1.2.0
IntelAndroidDrvSetup1.5.0
PhoneFlashTool_5.3.4.0_internal_win32
downloaded here:
Firmware (20161020_SZ)
Tablet joined and tried to flash.
* failed - failed loadet.efi
Please help. I can not download from Baidu
* If I use phoneFlasTool and flash a blank disc - Create Flash partition and dual boot and replace recovery?
What to do with an empty disc?
Thanks for any advice

It is not so hard. By mine it was only trial and error. Installiert all drivers an go in the bootloader with three Finger method. Go two levels up and go into bootloader. Then connect to PC and look in Intel flashing tool if connection is reconiced correctly. Select the downloaded file and select flash. Thats it. Device will reboot and you are ready to go.

theone0987654321 said:
It is not so hard. By mine it was only trial and error. Installiert all drivers an go in the bootloader with three Finger method. Go two levels up and go into bootloader. Then connect to PC and look in Intel flashing tool if connection is reconiced correctly. Select the downloaded file and select flash. Thats it. Device will reboot and you are ready to go.
Click to expand...
Click to collapse
Thank you for the advice. That's right, I did it was marked. I found a reason. rom file was saved on desktop, and had a long name (as I downloaded it) It must copy the file to C've renamed the firmware. Everything went alright. I downloaded and used the GPT files for resizing disk and now goes all right. Thank you for responding to my question.

hi, I have problem while flashing.
Phone flash tool always gives ERROR
Automatic reboot is not supported on this device, please reboot the device manually
ERROR : [Port 0/1/4] Failed to reboot the device
Click to expand...
Click to collapse
Any idea what to do? I followed all the steps, tried many times, still same problem. And it's not possible to reboot device manually, because then it lose connection with PC

Restock OS Without Android
Hi there.
I have to restock my Device, but the Intel Flash Tool does not recognize my Device.
I cannot boot into Android to turn on USB-Debugging or go into fastboot mode
How do i flash my device without any OS installed?
---------- Post added at 04:03 PM ---------- Previous post was at 03:52 PM ----------
affe2000 said:
Hi there.
I have to restock my Device, but the Intel Flash Tool does not recognize my Device.
I cannot boot into Android to turn on USB-Debugging or go into fastboot mode
How do i flash my device without any OS installed?
Click to expand...
Click to collapse
Ok, got it working... dnx fastboot mode is there

....

hello guys by accident i deleted windows 10, how can i reinstall them? i dont have the windows 10 icon in the dual boot select i only see the android icon

mike mike baby said:
hello guys by accident i deleted windows 10, how can i reinstall them? i dont have the windows 10 icon in the dual boot select i only see the android icon
Click to expand...
Click to collapse
Straightforward if you can obtain a USB stick capable of storing over 7GB (some 8GB sticks may not); USB hub (ideally a powered hub); USB keyboard; OTG cable.
1) Obtain the Windows files of the correct firmware. The procedure outlined here is for E6E9 firmware, but other firmware will be similar. Download the circa 6.5GB E6E9 firmware Windows files from https://yadi.sk/d/XEvRsoiD3Q4vKX or https://mega.nz/#F!I0AXGR5C!YiNFkZL9DIvzepH28qAjEQ (or from appropriate source for your firmware version).
Decompress the downloads as required to obtain six folders and two files.
2) Format the stick to FAT32.
3) Name the stick WINPE (five uppercase characters).
4) Copy the previously mentioned folders and files to the USB stick.
5) Plug USB stick and USB keyboard into hub; plug hub into OTG cable; plug OTG cable into tablet whilst the tablet is off.
6) Turn on tablet and immediately start tapping << Delete >> key on USB keyboard. This should open the UEFI config section prior to Android boot option. If the tablet displays the Android boot option, turn off the tablet, wait a few seconds, then turn on and start tapping << Delete >> key on USB keyboard again.
7) When in UEFI, touch the title menu option of << Save and Exit >> and look in the << Boot Override >> section for the name of your USB stick, then touch the name of your USB stick. The screen will immediately go blank as the tablet starts to boot from the USB stick.
8) After a few minutes, a numerically display of progress will be displayed in a CMD window.
9) After reaching 100% and nearing completion of the overall installation, the tablet will prompt for acceptance, so accept that prompt.
10) The setup will run a few final operations for a few seconds, then automatically reboot.
11) Done.
You will be prompted to complete the OOBE on each Windows boot until you complete OOBE.

Unable to mount Touchpad USB to PC after installing Android 4.4.4

I am unable to mount the USB to my PC using after installing Android 4.4.4 on my Touchpad. Was able to do so with WebOS. How can I connect my Touchpad using a usb cable to my PC? PC is a Gateway Notebook running Windows 7 Starter version.

1sharpguy said:
I am unable to mount the USB to my PC using after installing Android 4.4.4 on my Touchpad. Was able to do so with WebOS. How can I connect my Touchpad using a usb cable to my PC? PC is a Gateway Notebook running Windows 7 Starter version.
Click to expand...
Click to collapse
Which rom and build of Android 4.4.4 are you currently using?
Try this:
Plug the tablet into the PC with the USB cable. Go to settings/storage/ click the 3 dots in the upper right/USB computer connection.
Switch from Media device to Camera, see if windows detects and installs drivers. Then set it back to media device.

Still no luck with mounting Touchpad
Hello Roland...
Thank you for your help and informative response. I am still unable to mount my device (Touchpad) to my PC (Windows 7). I have described below what I have tried to do so far.
Which rom and build of Android 4.4.4 are you currently using?
I used the downloads from [ROM GUIDE] How to Install Android 7.x.x Nougat builds on the HP TouchPad
734 posts
Thanks: 1,157
By RolandDeschain79, Recognized Contributor on 3rd December 2016, 06:30 PM
Download Android 4.4.4 Kitkat install files(Rom, Gapps, Recovery):
Rom:cm-11-20161219-NIGHTLY-MLQ-tenderloin.zip
Recovery:TWRP-jcs-dm-tenderloin-20140612b.zip
Gapps:gapps-444-base-20160602-1-signed.zip
After switching from Media Device (MTP) to Camera (PTP), Windows was able to detect my device (TouchPad) and install the drivers. Despite the information displayed in Android Settings for USB Connections (Camera (PTP) lets you transfer photos using software, and transfer any files computers don't support MTP), I was only able to transfer photos/pictures. When I switched back to Media Device (MTP) file transfer, Windows could not detect my device. Instead, when I looked in device manager, Windows sees my device as a Samsung Android phone (which I have) and not a Touchpad.
I have attached a screen shot of the driver files in the submenu Android Composite ADB Interface. I even ran and update. All files were current with latest updates. Thus, for some reason Windows is seeing my Touchpad as a Samsung Android phone and not a Touchpad.
Any suggestions? I am unable to transfer backed up files or upgrade to Naugot 7.1 without being able to mount device.
Thanks! Jay

1sharpguy said:
Hello Roland...
Thank you for your help and informative response. I am still unable to mount my device (Touchpad) to my PC (Windows 7). I have described below what I have tried to do so far.
Which rom and build of Android 4.4.4 are you currently using?
I used the downloads from [ROM GUIDE] How to Install Android 7.x.x Nougat builds on the HP TouchPad
734 posts
Thanks: 1,157
By RolandDeschain79, Recognized Contributor on 3rd December 2016, 06:30 PM
Download Android 4.4.4 Kitkat install files(Rom, Gapps, Recovery):
Rom:cm-11-20161219-NIGHTLY-MLQ-tenderloin.zip
Recovery:TWRP-jcs-dm-tenderloin-20140612b.zip
Gapps:gapps-444-base-20160602-1-signed.zip
After switching from Media Device (MTP) to Camera (PTP), Windows was able to detect my device (TouchPad) and install the drivers. Despite the information displayed in Android Settings for USB Connections (Camera (PTP) lets you transfer photos using software, and transfer any files computers don't support MTP), I was only able to transfer photos/pictures. When I switched back to Media Device (MTP) file transfer, Windows could not detect my device. Instead, when I looked in device manager, Windows sees my device as a Samsung Android phone (which I have) and not a Touchpad.
I have attached a screen shot of the driver files in the submenu Android Composite ADB Interface. I even ran and update. All files were current with latest updates. Thus, for some reason Windows is seeing my Touchpad as a Samsung Android phone and not a Touchpad.
Any suggestions? I am unable to transfer backed up files or upgrade to Naugot 7.1 without being able to mount device.
Thanks! Jay
Click to expand...
Click to collapse
Hi have you tried rebooting both the tablet and the PC, sometimes thats necessary. You might also try running the universal novacom installer again now that the tablet is detected here. I tested plugging in the tablet with the rom you're currently using on a virgin windows 10 setup and it worked fine, unfortunately I don't have a windows 7 system to test.
If nothing works you can always transfer the backed up files over the WiFi with a free app WiFi file transfer here
That should take care of your files if you're looking to upgrade with Nougat.
Hope this helps :fingers-crossed:

Yes...tried running Universal Novacom Installer a couple of different times without success (unable to USB mount Touchpad). Device Manager on PC allows me to uninstall Android Composite ADB Interface. Was thinking I might try that and see if I can get Windows to USB mount Touchpad and then search for compatible drivers. If that doesn't work, will try using Wifi Transfer as you suggest. Hopefully, that will get the Nougat files and backed up files transferred over to Touchpad.
Thank you for your help. Will post again when I know something more.
J

1sharpguy said:
Yes...tried running Universal Novacom Installer a couple of different times without success (unable to USB mount Touchpad). Device Manager on PC allows me to uninstall Android Composite ADB Interface. Was thinking I might try that and see if I can get Windows to USB mount Touchpad and then search for compatible drivers. If that doesn't work, will try using Wifi Transfer as you suggest. Hopefully, that will get the Nougat files and backed up files transferred over to Touchpad.
Thank you for your help. Will post again when I know something more.
J
Click to expand...
Click to collapse
No problem, I've got one more thing for you to try. Found this in an older post of mine from 2012, back when I was using windows 7. Give it a try, you can always use the WiFi transfer app but it might take a while to complete. Good luck:good:
Note: Windows users may need to do the following in order to attach the Touchpad with the USB cable.
1. Go into Device manager. You will see "MTP USB Device" under portable devices.
2. Right Click it and select update driver software
3. Select Browse my computer for driver software
4. Select Let me pick from a list of device drivers on my computer
5. Select USB Mass Storage Device then click next

Finally!! I was able to get Windows to install the MTP drivers using the method you proposed in your last reply. Took a bit of monkeying around with. Not exactly sure what I did, but it worked. Was able to transfer backed up files and Nougat files to Touchpad. Soooo...went through steps install Nougat. Everything seem to load fine. However, got an error message at boot for Evervolv and am unable to load Nougat. Error message is as follows...
Selected: 'boot Evervolv'
Loading '/boot/uImage.Evervolv'...Ok
Checking uImage...Invalid size
BOOT FAILED!
Press SELECT to continue
I presume what it means by press SELECT to continue is to press the home key. When I do so, it takes me into the boot menu moboot 0.3.8
boot TWRP
boot webOS
boot Evervolv
boot webOS Recovery
reboot
shutdown
When I try to boot again in Evervolv, I get the same error message over again.
What do you think?

Oh yeah (full disclosure)...one more thing. In step 10 of your Rom Guide it says "-Select the System partition and swipe to wipe." I did this, but repeated it four different times because I didn't realize I had to touch the little home icon at the bottom of the page to return to the install button on the main menu. Not sure whether it would have had any effect on the install, but the error was a invalid size of uImage so wondering if by swiping to wipe the system partition so many times that I messed something up. That was the only thing I did that was different from your video and Rom Guide.

1sharpguy said:
Finally!! I was able to get Windows to install the MTP drivers using the method you proposed in your last reply. Took a bit of monkeying around with. Not exactly sure what I did, but it worked. Was able to transfer backed up files and Nougat files to Touchpad. Soooo...went through steps install Nougat. Everything seem to load fine. However, got an error message at boot for Evervolv and am unable to load Nougat. Error message is as follows...
Selected: 'boot Evervolv'
Loading '/boot/uImage.Evervolv'...Ok
Checking uImage...Invalid size
BOOT FAILED!
Press SELECT to continue
I presume what it means by press SELECT to continue is to press the home key. When I do so, it takes me into the boot menu moboot 0.3.8
boot TWRP
boot webOS
boot Evervolv
boot webOS Recovery
reboot
shutdown
When I try to boot again in Evervolv, I get the same error message over again.
What do you think?
Click to expand...
Click to collapse
I'ts probably just a corrupt download, I've read this complaint before. Redownload the Nougat files and reinstall the recovery, rom and gapps.
1sharpguy said:
Oh yeah (full disclosure)...one more thing. In step 10 of your Rom Guide it says "-Select the System partition and swipe to wipe." I did this, but repeated it four different times because I didn't realize I had to touch the little home icon at the bottom of the page to return to the install button on the main menu. Not sure whether it would have had any effect on the install, but the error was a invalid size of uImage so wondering if by swiping to wipe the system partition so many times that I messed something up. That was the only thing I did that was different from your video and Rom Guide.
Click to expand...
Click to collapse
Wiping a blank partition won't hurt the tablet, its just a bad download. Right under swipe to wipe its says go back to main menu... I could add click the home button to return to the main menu, if you think that would help. This is why I have both a video and a written guide, I'd recommend using both resources simultaneously.
Edit: I double checked the video and I tell you to press the home button and return to the main menu here
10)Reboot into TWRP recovery 3.0.3.0, Flash the Android 7.1 Rom and Gapps
-Once in the new TWRP 3.0.3.0 go to the Wipe menu and select Advanced Wipe.
-Select the System partition and swipe to wipe.
-go back to the main menu and select Install, locate the download folder on the left menu
-select and install the 7.1 Rom and the Gapps package then reboot.
Note: The first boot to android 7.1 can take sometime, Wait for it...

That was it. Corrupt download. After downloading Nougat again and reinstalling, eventually Android 7.1 booted and is now loaded. Yeeees!!! The bad news is that Nougat on my device is very unstable and sloooow. I was more impressed with Android KitKat. If something doesn't change with 7.1, I will probably revert back to KitKat. After having gone through this exercise, I feel more empowered (confident) to make such changes. Although frustrating at times, succeeding in switching out WebOS for Android was a great learning experience and a big deal for me (I never do these kind of things). For someone with virtually no skills or experience in this kind of thing, it was well worth it to give it a go. I just hated the thought of seeing this TouchPad turn into a boat anchor. Couldn't have done it without you Roland. Your video and instructions (along with followup support to the forum) was invaluable. Although I am feeling nostalgic for WebOS (I really liked that operating system. Wish it had made it.), it has been fun to breath new life into these HP TouchPads with Android.
I'm sorry you seemed to misunderstand my point from my previous thread about repeatedly wiping the system files. I was not being critical of your video or instructions, but rather trying to give as much information to you and the forum to try and understand why I was unable to get Nougat to boot. You have done a great job with conveying the steps for loading Android on TouchPads. You deserve a huge :good: for your trouble. Thanks again for all your input and helping me get her sorted out. Good on ya mate!!

1sharpguy said:
That was it. Corrupt download. After downloading Nougat again and reinstalling, eventually Android 7.1 booted and is now loaded. Yeeees!!! The bad news is that Nougat on my device is very unstable and sloooow. I was more impressed with Android KitKat. If something doesn't change with 7.1, I will probably revert back to KitKat. After having gone through this exercise, I feel more empowered (confident) to make such changes. Although frustrating at times, succeeding in switching out WebOS for Android was a great learning experience and a big deal for me (I never do these kind of things). For someone with virtually no skills or experience in this kind of thing, it was well worth it to give it a go. I just hated the thought of seeing this TouchPad turn into a boat anchor. Couldn't have done it without you Roland. Your video and instructions (along with followup support to the forum) was invaluable. Although I am feeling nostalgic for WebOS (I really liked that operating system. Wish it had made it.), it has been fun to breath new life into these HP TouchPads with Android.
I'm sorry you seemed to misunderstand my point from my previous thread about repeatedly wiping the system files. I was not being critical of your video or instructions, but rather trying to give as much information to you and the forum to try and understand why I was unable to get Nougat to boot. You have done a great job with conveying the steps for loading Android on TouchPads. You deserve a huge :good: for your trouble. Thanks again for all your input and helping me get her sorted out. Good on ya mate!!
Click to expand...
Click to collapse
Congratulations are in order for getting this all done, i'm happy to hear the experience has empowered you with confidence and knowledge. I appreciate the feedback, my guide is aimed at users with little to no experience who just want to keep their HP TouchPad going.
No apology needed I just take my guides seriously and i'm always looking to improve them or fix mistakes. You'll see below I've added portions of this conversations to my troubleshooting section to help other users here. I'm just glad I didn't mess up that step in the video cause you can't fix those, a forum post is much easier to edit.
Nougat is still being worked on but as with any new version of android there will be bugs. Shumashs has an overclocked kernel that can boost the performance of the Evervolv nougat rom. However I highly recommend CM11 for users just looking for a stable and reliable setup. I'm happy we could save your tablet, enjoy it and check back sometime to see how Nougat is coming along.
Edits from my install guide:
Help I get this Error message after installing the Evervolv Nougat rom
Selected: 'boot Evervolv'
Loading '/boot/uImage.Evervolv'...Ok
Checking uImage...Invalid size
BOOT FAILED!
Press SELECT to continue
Solution
-You've downloaded a corrupt file, delete it and re-download the Nougat files.
-Repeat step 10 of the guide, flash the Rom and Gapps package from TWRP recovery.
Can't mount USB drive with CM11 and Windows 7
-Plug the HP TouchPad into your PC with the USB cable
-Go into Device manager. You will see "MTP USB Device" under portable devices.
-Right Click it and select update driver software
-Select Browse my computer for driver software
-Select Let me pick from a list of device drivers on my computer
-Select USB Mass Storage Device then click next to install the driver
10)Reboot into TWRP recovery 3.0.3.0, Flash the Android 7.1 Rom and Gapps
-Once in the new TWRP 3.0.3.0 go to the Wipe menu and select Advanced Wipe.
-Select the System partition and swipe to wipe.
-Click on the TWRP home button(bottom middle) to return to the main menu.
-Select Install, locate the download folder on the left menu.
-Select and install the 7.1 Rom and the Gapps package then reboot.
-After choosing to install the rom click the button to add additional zips, add the gapps package and put a check beside reboot when complete.
Note: The first boot to android 7.1 can take sometime, Wait for it...

Windows 10 Razer phone 2 driver problem.

Hello everybody I was able to unlock the bootloader but when I put the phone in bootloader mode it doesn't even see the phone on the computer I've tried going to platform tools and command prompt and did ADB devices and it won't see it. it won't even see it in fastboot. I've tried the driver installation guide but it doesn't work. Can someone please help me? I am running Windows 10 64-bit on a Acer nitro 5

raver445 said:
Hello everybody I was able to unlock the bootloader but when I put the phone in bootloader mode it doesn't even see the phone on the computer I've tried going to platform tools and command prompt and did ADB devices and it won't see it. it won't even see it in fastboot. I've tried the driver installation guide but it doesn't work. Can someone please help me? I am running Windows 10 64-bit on a Acer nitro 5
Click to expand...
Click to collapse
I had this issue myself when I tried unlocking. It seems when you type fastboot, CMD keeps using an older version. You will need to directly call /fastboot.exe, wherever the full path is, and have your Razer in bootloader mode (it took me an hour to figure out I already had it in bootloader mode), and hopefully it will find it.
TLDR: Make sure adb and fastboot are being executed from their actual paths and that they are the latest.
Also USB debugging is on? Did you check the notifications?

Yes usb debug mode is on...

Johnjobs13 said:
I had this issue myself when I tried unlocking. It seems when you type fastboot, CMD keeps using an older version. You will need to directly call /fastboot.exe, wherever the full path is, and have your Razer in bootloader mode (it took me an hour to figure out I already had it in bootloader mode), and hopefully it will find it.
TLDR: Make sure adb and fastboot are being executed from their actual paths and that they are the latest.
Also USB debugging is on? Did you check the notifications?
Click to expand...
Click to collapse
I have even tried updating the drivers and it keeps saying it can't update it even if I use the manual update settings

Johnjobs13 said:
I had this issue myself when I tried unlocking. It seems when you type fastboot, CMD keeps using an older version. You will need to directly call /fastboot.exe, wherever the full path is, and have your Razer in bootloader mode (it took me an hour to figure out I already had it in bootloader mode), and hopefully it will find it.
TLDR: Make sure adb and fastboot are being executed from their actual paths and that they are the latest.
Also USB debugging is on? Did you check the notifications?
Click to expand...
Click to collapse
How can I get the drivers installed then? It's driving me crazy.

raver445 said:
How can I get the drivers installed then? It's driving me crazy.
Click to expand...
Click to collapse
I vaguely recall having the same issue, and fixed it by going into the Device Manager and installing a different driver for the phone. I can't remember exactly which one it was (I want to say it said something about fastboot). This was after booting into fastboot of course, since Windows uses a different driver for when it's in fastboot vs when it's booted normally.

Heres what I did:
1) Download https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip
2) Extract to a folder in your desktop.
3) Go into the folder and look for android_winusb.inf
4) Right click it and choose install.
5) Press the windows button and X at the same time and choose device manager.
6) Plug the phone in and find the device in the device manager. It could be in a couple different device trees, so you'll have to find it.
7) Right click and choose update driver. Choose browse, then browse again, and find the folder on your desktop with the drivers. choose that same .inf file from earlier.
8) You'll have 3 different options. I've always had success with the ADB Composite driver.

th3cavalry said:
Heres what I did:
1) Download https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip
2) Extract to a folder in your desktop.
3) Go into the folder and look for android_winusb.inf
4) Right click it and choose install.
5) Press the windows button and X at the same time and choose device manager.
6) Plug the phone in and find the device in the device manager. It could be in a couple different device trees, so you'll have to find it.
7) Right click and choose update driver. Choose browse, then browse again, and find the folder on your desktop with the drivers. choose that same .inf file from earlier.
8) You'll have 3 different options. I've always had success with the ADB Composite driver.
Click to expand...
Click to collapse
I have just rebooted my computer I'll see how it works in just a moment but I don't know if it's going to see it or not. it is still not seeing it.

Gamesoul Master said:
I vaguely recall having the same issue, and fixed it by going into the Device Manager and installing a different driver for the phone. I can't remember exactly which one it was (I want to say it said something about fastboot). This was after booting into fastboot of course, since Windows uses a different driver for when it's in fastboot vs when it's booted normally.
Click to expand...
Click to collapse
So what can I do to fix this? It's driving me insane.

raver445 said:
So what can I do to fix this? It's driving me insane.
Click to expand...
Click to collapse
im having the exact same issue doing what everyone says and nothing i need to lock my bootloader to send back to razer for warranty im pulling my hair out
---------- Post added at 11:18 PM ---------- Previous post was at 11:14 PM ----------
unless this is correct the phone comes up as samsung android phone and under the tab is android adb interface?

celphtitled885 said:
im having the exact same issue doing what everyone says and nothing i need to lock my bootloader to send back to razer for warranty im pulling my hair out
---------- Post added at 11:18 PM ---------- Previous post was at 11:14 PM ----------
unless this is correct the phone comes up as samsung android phone and under the tab is android adb interface?
Click to expand...
Click to collapse
After I update it the software drivers for the computer it says Razer phone 2 but it doesn't work right. I tried doing one of those scripts to reflash to stock software and it doesn't do Jack squat it sits there waiting for device.

use samsungs usb driver installer and change adb driver to Samsung's version in device manager. should see fastboot device now .

celphtitled885 said:
im having the exact same issue doing what everyone says and nothing i need to lock my bootloader to send back to razer for warranty im pulling my hair out
---------- Post added at 11:18 PM ---------- Previous post was at 11:14 PM ----------
unless this is correct the phone comes up as samsung android phone and under the tab is android adb interface?
Click to expand...
Click to collapse
i got it to work for the fastboot devices ...but still unable to relock it

has anyone figured this out yet im havin the exact same problem i go into bootloader and it shows android with caution sysmlo in device manager will no find device in fastboot mode period

ghost9640 said:
has anyone figured this out yet im havin the exact same problem i go into bootloader and it shows android with caution sysmlo in device manager will no find device in fastboot mode period
Click to expand...
Click to collapse
Copied from another thread.....
This is the biggest problem most people have if you don't do this part here below.
https://s3.amazonaws.com/cheryl-fact...on_Windows.pdf
You can use this tool as well to setup adb and fastboot with the correct cord it works well ?
https://forum.xda-developers.com/and...ndows-t3999445

got it
JDBarlow said:
Copied from another thread.....
This is the biggest problem most people have if you don't do this part here below.
https://s3.amazonaws.com/cheryl-fact...on_Windows.pdf
You can use this tool as well to setup adb and fastboot with the correct cord it works well
https://forum.xda-developers.com/and...ndows-t3999445
Click to expand...
Click to collapse
my laptop was not seeing the device my pc is, now im trying to flash arter97 kinda stuck but thx bud

The CPU AMD and windows 10 has an issues with fasboot driver everytime that you put command in fastboot the screen changes and starts displaying following message "Press any key to shutdown" waiting for devices or stuck on fastboot "sending system ...123,456kb. No need to find any cable to fix this just install windows 7 and flashing step by step then the problem will be solved

decode2533 said:
The CPU AMD and windows 10 has an issues with fasboot driver everytime that you put command in fastboot the screen changes and starts displaying following message "Press any key to shutdown" waiting for devices or stuck on fastboot "sending system ...123,456kb. No need to find any cable to fix this just install windows 7 and flashing step by step then the problem will be solved
Click to expand...
Click to collapse
Lol okay..that's about as random as "hey anybody reading this thinking about getting an S20 Ultra or one of the others"
I am....

I had the same problem. I never could get it to work in Windows. Luckily, however, I have an Ubuntu dual boot on my system, so I installed ADB & Fastboot on linux, put the phone in download mode, plugged it in, and it showed up without issue. This won't help for everybody, but if you have a linux machine, or a you can install a dual boot, it'll get you where you need to be. And it's a lot easier than Windows. You might be able to do a USB pass through, to a VM, but I haven't tested it. It could be worth a shot, if you don't have any other options.

Hi All,
Thought I would post this on here for you all, might help someone else like it did me.
What ImperialMe said is correct and I was able to do both my Razor 1 and 2 using it.
imperialme said:
I had the same problem. I never could get it to work in Windows. Luckily, however, I have an Ubuntu dual boot on my system, so I installed ADB & Fastboot on linux, put the phone in download mode, plugged it in, and it showed up without issue. This won't help for everybody, but if you have a linux machine, or a you can install a dual boot, it'll get you where you need to be. And it's a lot easier than Windows. You might be able to do a USB pass through, to a VM, but I haven't tested it. It could be worth a shot, if you don't have any other options.
Click to expand...
Click to collapse
The easy method is to download the Ubuntu Image for Windows (ubuntu.com/download/desktop)
Once you have it, burn it to USB using Rufus (rufus.ie)
Boot into the USB on your PC and when prompted just run as is, no need to install.
Once running, open a terminal window and with internet access and run the following:
Code:
sudo add-apt-repository universe && sudo apt-get update
Now run:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
When promoted press Y and enter
Now run:
Code:
sudo adb start-server
Connect your phone, turned on and on the home screen for example. Run the following
Code:
sudo adb devices
You should see your device listed as unauthorised and get a prompt for ADB access on the mobile phone.
run it again to confirm its authorised and then enter:
Code:
adb reboot bootloader
Once rebooted, use the menu to select boot into fastboot on the phone
Now back to the terminal window, enter:
Code:
Fastboot devices
You should now see your device listed and commands should work as expected.
If you need to copy anything over to the temporary USB OS then use another USB drive and copy them to it before you boot the OS.
I tried this in a VM and VMWare and HyperV both failed as the drivers they use are still Windows based and failed. Only a full OS worked.
Hope this helps someone else!