Database Users

Oneplus One with fastboot and TWRP functioning, but can't get a ROM working

I really need help, I have tried the following, having TWRP V2.8.5.1 functioning and Fastboot also.
- Through TWRP, tried connecting the PC so I can Flash a ROM from there, but I can't seem to be able to connect the One to my PC so it will let me transfer files through cmd with adb push. My computer is a windows 10 OS with Samsung drivers and Android SDK full installed, still can't get it to work.
- Through Fastboot tried flashing cm-11-20141008-SNAPSHOT-M11-bacon.zip downloaded from Cyanogenmod page and using Oneplus One Toolkit 2.0, even though the Toolkit says the files are there, still phone continues to show 1+ logo and then rebooting.
Please I need some help.
Cheers. and thank you.

Why adb push when you can just copy the file over using a file manager (or a command prompt if you insist) and then flash from the internal storage?

I'm having the same issue but in my case I can boot into recovery or other stuff IF I HAVE THE USB PLUGGED IN
Maybe you can check and and let me know, if I found a solution I'll tell you, hoping the same from you please.

http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 this could help.

Sideload issue

Hiya. I managed to unlock bootloader/install twrp and root and went to see if i can put it back to stock.
When i try and sideload the stock firmware, my pc wont recognize adb while it's in sideload mode but it does in normal state.
I also get these errors (see pics)
I have tried installing all the drivers/changed usb ports but now i have no clue what it can be.
Any help please?
Thanks
PS. Using Windows 10

I'm having the exact same issue and I'm also really interested in a solution for this. Also tried uninstalling and reinstalling the drivers and switched USB Ports. The device gets detected without any problems in fastboot mode but as soon as I switch to Sideload Mode in stock recovery, Win 10 shows me this error and doesn't detect my device for sideloading.
Temporarily I could flash TWRP and sideload the zip via TWRP and cmd but I would also like to be able doing it without TWRP again.
Thanks in advance.

Can't anybody help us?

Just download the latest Android Studio software it contains the last ADB driver, i had the same issues after installing reboot, and ADB sideload will work !
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378

Cant flash stock firmware on it and doesnt stay in media protocol

Hello. Well as the title says im having these issues. The main one is that im not able to flash anything on it using adb. I get a failed message. Everything was working fine until i flashed oreo on it 8.1. I was able to flash oreo with no issues but then once in oreo i couldnt flash twrp or another firmware at all and every time i connect it to a pc it stays on charging only and have to manually put it on media transfer. Could this be a software or hardware issue?
If i want to downgrade I just have to flash everything using adb right?

Has anyone had this issue?

The only time I have issues like yours is when my platform-tools folder gets wonky....so I just download the latest from Google and replace them all with the new ones. Maybe you have done this already but it doesn't hurt to try. Hope it helps

did you enabled developer settings and enabled usb debugging? and is your bootloader unlocked? I have no problems here on 8.1

notstevek said:
did you enabled developer settings and enabled usb debugging? and is your bootloader unlocked? I have no problems here on 8.1
Click to expand...
Click to collapse
I would do that and also make sure platrorm tools and drivers are up to date. Also check your usb ports on PC. Sometimes I have problems with one port but another works fine. Currently I have none of my ports work except one and only with a usb splitter weird right? Anyway check all those things and give it another try.

mojorisin7178 said:
I would do that and also make sure platrorm tools and drivers are up to date. Also check your usb ports on PC. Sometimes I have problems with one port but another works fine. Currently I have none of my ports work except one and only with a usb splitter weird right? Anyway check all those things and give it another try.
Click to expand...
Click to collapse
well it was actually my usb ports.. two of them just didnt work with fastboot but they worked fine with everything else like usb hubs, flash drives, etc... Althoguh I still got the problem when plugging it I have to change the setting on the phone for file transfer. Does it happen all the time in oreo? I havent gone back to nougat and try it out but when I was in nougat it was working just fine.
Another Issue I have is that I keep flashing twrp on it but everytime I restart the phone twrp gets delete and Im left with the regular recovery. Im trying with oreo 8.1

From the twrp website
"Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
fastboot flash recovery twrp.img
fastboot reboot
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
hth

Im having some weird issues. First I cant keep twrp on oreo, no matter what version of twrp I use it always gets deleted. Second, when going back to nougat twrp stays installed but I cant boot into the system what combo would you suggest?

Help updating

A friend of mine rooted my phone for me a while back. He's no longer around and I'm still pretty unfamiliar with the process without using twrp. I'm not sure what method he used. I was going to try flashing a stock os via adb but adb doesn't detect my phone. I'm sure it's a driver issue but I can't seem to fix the problem. I also have trouble transferring files with a USB cable. My computer sees the phone but as far as opening it to explore or transfer files, it doesn't work. I downloaded drivers from a link I saw in another thread on xda and installed some file with a weird format and that didn't fix the problem.
Can somebody please point me in the right direction?

First of all, I'd suggest you to try with a different cable. The one shipped with the RP2 is optimized for power and might cause issues when using it for data trasfer.
Secondly, generally speaking you should install adb platform tools (I don't remember installing specific drivers for the adb, to be honest). You probably want to install the google usb driver as well for the fastboot as well.
If you confirm that those solution do not provide a solution to you, we might look at other causes.
Once everything is workin, you can proceed to update (since you have root permissions, I am assuming you see the OTA but you don't know how to proceed). The procedure that I followed is this:
1. Download razer factory images for mr1
1. perform a nand backup with TWRP
3. extract the factory images somewhere, open the "flash_all.bat/.sh":
3.1. make the fastboot variable point to the actual fastboot executable (if you are not familiar with relative paths, use full path and it will work seamlessly)
3.2 remove/comment the line
Code:
fastboot erase userdata
4. run the script
5. reboot your phone and perform the OTA update
6. install arter12 kernel
7. In magisk installer download the zip and flash it with TWRP

So I've been troubleshooting for the past few hours. I'm familiar with the process that needs to be done. The issue I'm running into now is a driver issue. I deleted the Google driver and installed a Samsung driver just for laughs. I can view my phone and transfer files now flawlessly. But it still isn't detected by adb. I was just going to wipe my phone and reflash the stock rom with adb fastboot. I wonder if there's a way to flash the stock rom with the Razer bootloader until I figure out what's going on with adb?

The google drivers are for fastboot (bootloader), not adb. For adb I just let windows do the automatic install (I'm sorry, I just assumed you are using windows, tell me if that is not the case).
Keeping the assumption that you are using windows, try to uninstall all driver (both from installed apps and from installed driver. For the second step you will need to show in device manager, all hidden devices and uninstall all of them).
Reboot windows and reconnect phone, I'd expect it to be automatically recognized as Razer Phone 2.
As per bootloader, in W10 sometimes it's a pain in the ass installing the drivers as you might need to manually install them.

PC fastboot recognition issue

Today i tried to install a custom ROM update which caused a softbrick and now my device is stuck at the logo. I naturally decided to flash a stock rom in order to solve this. I went ahead and downloaded a MIUI 11 global stable one, next was rebooting into fastboot and connect it to my PC...
...When i rebooted my phone into fastboot, my PC didn't recognize the device at all. Device Manager says "USB Unknown Device (Device Descriptor Request Failed)". I verified the USB port and cable works properly with another phone, i installed USB drivers and ADB/fastboot ones, still nothing.
Is there anything I'm missing? I'm not very adept at these topics, I previously flashed mine into a PE custom ROM purely by following tutorials mindlessly.

Try the app "Xiaomi ADB/Fastboot Tools", this has the option to flash stock ROMs. The USB drivers that I have installed on my computer are "minimal ADB Fastboot 1.4.3".
You could also solve the problem with the tool "MiFlash Pro".