Related
Hey guys,
Wonder if you can all help me,
Im not new to Rooting, but i have never come across this error before, ive searched accross XDA and Google, but cannot for the life of me find a fix, found a couple of things about deleting a registry file, and installed the One drivers which i had downloaded from here. I Do not have HTC Sync installed.
When device is powered up normally and connected to USB it as fine. When i reboot the Device into fastboot and connect it, i get a Error saying USB Device not recognised.
When i goto device manager, its shows up as My One under HTC, but has a Yellow '!' in a triangle, when i click on properties it states a code 10 Device Fails To Start error.
Please help as this is really frustrating me... Ive tried everything! And i really dont want to re-set my whole laptop as i will lose ALOT of data!
Like i said, im not new to this, as been doing this since the days of the HTC HD2...Am i missing something? Having a thick moment?
Running Windows 8.1.
If anyone really knows what this could be and could possibly fix, let me know as have team viewer and would gladly let you connect to me to help me out (Donation for your time aswell)
Thanks in Advance!
Really simple mate, windows 8.1 isnt compatible with fastboot drivers for now. Only adb is working atm. So dont be scared, your phone have no problem, its only because you updated to 8.1
Sent from my HTC One using xda app-developers app
Edit: there is a possible fix if your computer is based on intel chipset usb 3.0. Just google something like Windows 8.1 fastboot fix. Otherwise I think you will need to wait or simply use another computer with win7 or 8.0 or maybe dual boot win7 or even boot win7 with a vm?
Edit 2: search the forum, there is a "how to" force win7 fastboot drivers installation on win8.
Perfect buddy worked a Treat! Thankyou so much! I was getting so frustrated haha!
Didnt know it was a problem with Windows, so just needed to change the search terms, do'h!
For all those that has the problem in the future, a link for the fix!
Clicky!
Mods, this can now be closed, fixed!
fastboot for windows 8.1 over linux and this is my option to work fastboot on win 8.1
load wubi (windows ubuntu installer) over the link http://wiki.ubuntuusers.de/Wubi
than install ubuntu, on harddrive C:// and reboot your Pc
Now you have a linux in your current system, you can remove ubuntu (linux) in Programms & feautures list in windows.
now reboot reboot the system and isntall in ubuntu fastboot.
you musst give in the terminal sudo apt-get fastboot
and now you can flash your bootloader in linux.
but you musst sudo bevor you type fastboot flash type sudo fastboot flash boot boot.img
adb is working to on linux
i love wubi <3
you say it is easy
gooogle wubi (windows ubuntu installer)
tried running ubuntu in a virtual machine still no go guess the vm needs the windows driver to see the damn usb ports ffs
anyone know if for sure it will work if i actually install ubuntu to a partition?
Sony vaio 13 i7-4500u so only got usb3 ports and small hard drive didnt wanna dual boot really
Hi all.
I'm trying to S-Off my HTC first, but I can't get the phone to connect to ADB while in debug mode. It connects to ADB fine while in recovery mode, but apparently it needs to be in debug mode for moonshine to work. The phone is unlocked and rooted and I installed the HTC drivers. In the device manager it comes up as an Android device in recovery mode, but as a portable storage device in debug mode.
Can anyone tell me what I'm doing wrong?
nikpmr said:
Hi all.
I'm trying to S-Off my HTC first, but I can't get the phone to connect to ADB while in debug mode. It connects to ADB fine while in recovery mode, but apparently it needs to be in debug mode for moonshine to work. The phone is unlocked and rooted and I installed the HTC drivers. In the device manager it comes up as an Android device in recovery mode, but as a portable storage device in debug mode.
Can anyone tell me what I'm doing wrong?
Click to expand...
Click to collapse
Does it show up when typing adb devices in the command prompt?
Thanks for the reply.
No, not unless the phone is in recovery mode. Fastboot works as well. However when the phone is on and in debug mode I get nothing.
nikpmr said:
Thanks for the reply.
No, not unless the phone is in recovery mode. Fastboot works as well. However when the phone is on and in debug mode I get nothing.
Click to expand...
Click to collapse
Hmmm sounds like what happened to me once it was a frustrating situation but all that was needed was an update to the ADB drivers for the device. Sadly I'm away from my computer right now so it'll be a while until I can actually whip something up to help you, sorry
Try to force ADB to redetect with adb kill-server.
abrahammmmmmm_ said:
Hmmm sounds like what happened to me once it was a frustrating situation but all that was needed was an update to the ADB drivers for the device. Sadly I'm away from my computer right now so it'll be a while until I can actually whip something up to help you, sorry
Click to expand...
Click to collapse
Okay, let me know when you have some time. Thanks again!
I tried the kill-server command to no avail. The computer just plain doesn't recognize it as an Android device. I will try on my Linux computer and see if that makes any difference.
nikpmr said:
Okay, let me know when you have some time. Thanks again!
I tried the kill-server command to no avail. The computer just plain doesn't recognize it as an Android device. I will try on my Linux computer and see if that makes any difference.
Click to expand...
Click to collapse
Is your computer windows 7, 8 x32 or x64bit? I can probably do it today if you've got a windows 7 x64bit computer since I wont have to do much looking
I'm running win 7 64 bit. Thanks again for your help!
nikpmr said:
I'm running win 7 64 bit. Thanks again for your help!
Click to expand...
Click to collapse
NOTE THAT YOUR PHONE SHOULD NOT BE CONNECTED DURING THIS PROCESS
I already searched & set up the update folder so you don't have to do all the dirty work d:\
Ok Well I'm just going to make this quick and not really got through the basics like how to unzip things because if you don't know how to do that you probably shouldn't be trying to get s-off on your phone anyway so I'll just assume you already know how.
Step 1. open control panel select hardware and sound and open Device Manager with the administrative logo one the side.
Step 2. Near the top or somewhere on this list there's supposed to be a drop down that reads "adb devices, adb android, adb, android, adb drivers etc. Mine shows Android USB Devices it actually just varies based on computer I can't really go to the specifics of it but I'm sure you can find it.
Step 3. Select that dropdown menu and right click whatever shows (there should only be one thing) and then select Update Driver Software and choose the option that says Browse my computer for driver software and locate the htc drivers folder which should already be unzipped, select the whole folder and have the option to include subfolders checked. click next or whatever it says to finish
Step 3 Now you must remove your device from the Portable Devices dropdown menu to ensure all drivers are detected for the phone, to do this right click on HTC First and just select remove, wait until it's done. and now just reconnect your device and let all the drivers install and it should now be done!
Make sure you look at the screenshots I attached to make sure you don't accidentally remove or update something else also because that's where the drivers folder is an i'm pretty sure you'll need that
A reboot of the computer is recommended btw
Ask questions if you have any
View attachment 2459140
View attachment HTC_drivers_Win7_x64.zip
View attachment 2459141
Wow, that's quite explanatory, thank you! Unfortunately I only see the category ADB Devices when the phone is connected and in recovery mode, and I only see the category Portable Devices when the phone is connected, booted, and in debug mode. (Neither of these categories are visible when the phone is disconnected from the computer.) I did however try installing the drivers you gave me with the phone connected and in recovery mode, but to no avail; after the phone boots ADB Devices disappears and Portable Devices appears. Uninstalling Portable Devices doesn't help either; it just reinstalls when I reconnect the phone.
I am trying to get the category ADB Devices to appear in the Device manager when the phone is turned on and in debug mode so that I can use ADB while the phone is booted.
Got it working. I had to go to device manager > portable devices > HTC First and replace the driver with Generic USB Composite Device Driver.
Boom. Everything working. Weird.
nikpmr said:
Got it working. I had to go to device manager > portable devices > HTC First and replace the driver with Generic USB Composite Device Driver.
Boom. Everything working. Weird.
Click to expand...
Click to collapse
How exactly did you replace the HTC First driver with the Generic USB Composite Device Driver?
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.
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!
1) get boot.img
from https://forum.xda-developers.com/t/...stock-roms-for-nord-ce.4296379/#post-85427971
a) install oxygen updater on phone
b) from oxygen updater settings turn on advanced mode
c) download OTA
2) move OTA to computer
adb pull /storage/self/primary/f90ffdf825051bb90cbec201868c32b4ae6ac6ec.zip .
3) from https://github.com/vm03/payload_dumper
a) download zip and install payload_dumper
b) Maybe need to install protobuf and bsdiff4
pip install protobuf
pip install bsdiff4
c) extract the boot.img
in the directory with payload_dumper.py
python3 payload_dumper.py <path_to>/payload.bin
Points 4,5 and 6 are from https://www.getdroidtips.com/root-oneplus-nord-ce-5g/
4) push magisk apk to phone
adb push Magisk-v23.0.apk /storage/self/primary
5) install Magisk and patch boot.img
6) download the patched image
adb pull /storage/emulated/0/Download/magisk_patched-23000_XARHP.img .
7) test image
adb reboot bootloader
fastboot boot boot.img
8) if the image work install magisk
on step 7) I get
fastboot boot magisk_patched-23000_D2y0e.img
< waiting for any device >
On another device (oneplus 7T) the fastboot command works fine, so I guess my tools work well.
How can I solve this?
(I run the platform-tools on linux, fastboot version 31.0.3-7562133)
tomlens said:
on step 7) I get
fastboot boot magisk_patched-23000_D2y0e.img
< waiting for any device >
On another device (oneplus 7T) the fastboot command works fine, so I guess my tools work well.
How can I solve this?
(I run the platform-tools on linux, fastboot version 31.0.3-7562133)
Click to expand...
Click to collapse
Did you boot your device in bootloader?
Easiest way to do that is with cmd and following command:
adb reboot bootloader
tomlens said:
on step 7) I get
fastboot boot magisk_patched-23000_D2y0e.img
< waiting for any device >
On another device (oneplus 7T) the fastboot command works fine, so I guess my tools work well.
How can I solve this?
(I run the platform-tools on linux, fastboot version 31.0.3-7562133)
Click to expand...
Click to collapse
That means your phone is missing device drivers, thereby your OS not recognizing the device when it's in bootloader mode. It is easy if a similar situation happened with Windows, but unfortunately, I don't know how to do the same in Linux.
Sony make.belive said:
Did you boot your device in bootloader?
Easiest way to do that is with cmd and following command:
adb reboot bootloader
Click to expand...
Click to collapse
Yes I did.
theincognito said:
That means your phone is missing device drivers, thereby your OS not recognizing the device when it's in bootloader mode. It is easy if a similar situation happened with Windows, but unfortunately, I don't know how to do the same in Linux.
Click to expand...
Click to collapse
Does the phone provide devices drivers? I'd expect the OS providing it. Anyway, I'll give it a try on Windows.
tomlens said:
Does the phone provide devices drivers? I'd expect the OS providing it. Anyway, I'll give it a try on Windows.
Click to expand...
Click to collapse
Again, don't know about Linux, but for Windows, yes. It does provide drivers. The first time I connected 8T on my Windows PC, it automatically showed an OnePlus drivers image, mounted like a disc. I used that for installing all the drivers (except EDL drivers). For EDL, you need Qualcomm drivers, which I got separately from the MSM thread (just check out any MSM thread of OP8/9 series).
PS: Unless you are planning to use the MSM tool for restoring the phone, you really don't need the EDL drivers.
theincognito said:
Again, don't know about Linux, but for Windows, yes. It does provide drivers. The first time I connected 8T on my Windows PC, it automatically showed an OnePlus drivers image, mounted like a disc. I used that for installing all the drivers (except EDL drivers). For EDL, you need Qualcomm drivers, which I got separately from the MSM thread (just check out any MSM thread of OP8/9 series).
PS: Unless you are planning to use the MSM tool for restoring the phone, you really don't need the EDL drivers.
Click to expand...
Click to collapse
I successfully unlocked the bootloader using Windows 10 now. I installed the android sdk platform tools and run into the same behavior as on linux. Connecting the Nord CE device in fastboot mode popped up a new device in device manager. The device driver was missing. I installed the driver after installing oneplus usb drivers for windows that I found in a OnePlus-USB-Drivers.zip on the internet (I'd rather download it from oneplus, but they do not offer anything like that). After that the fastboot oem unlock command worked as expected.
Usually oneplus devices provide the windows drivers in a separate partition that pops up on usb connection. But not on my Nord CE.
Wondered if i could request some assistance.....mines in recovery mode at the moment. Just managed to get twrp on there - ive found a few guides that have suggested flashing the individual compoments (which i tried) but got stuck half way down when some of the components would not flash due to being protected. As ive got TWRP on there i can now see that ive got 0mb for various areas including the storage...is there anyway i can format the storage from fastboot to give myself some space to load on a zip image and then flash from there?
ComfySofa said:
Wondered if i could request some assistance.....mines in recovery mode at the moment. Just managed to get twrp on there - ive found a few guides that have suggested flashing the individual compoments (which i tried) but got stuck half way down when some of the components would not flash due to being protected. As ive got TWRP on there i can now see that ive got 0mb for various areas including the storage...is there anyway i can format the storage from fastboot to give myself some space to load on a zip image and then flash from there?
Click to expand...
Click to collapse
The "TWRP" published here is incomplete and didn't help when it comes to reburning the ROM.
After a lot of research and experimentation, I think this is the best, safest and easiest way to recover from bricks.
JamboFE said:
The "TWRP" published here is incomplete and didn't help when it comes to reburning the ROM.
After a lot of research and experimentation, I think this is the best, safest and easiest way to recover from bricks.
Click to expand...
Click to collapse
Brilliant - thanks very much - ill reflash the original recovery and try again...!