Hi all,
I have a rooted oneplus X with CM13 installed together with cyanogenmod recovery.
I update CM nightly build through the cyanogen update utility and then my phone would not boot.
I can boot to recovery mode and my phone is detected as unauthorized.
I can boot in fastboot mode but the device is not detected (I checked I had the correct drivers).
I then tried to sideload Oneplus ROM and CM13 ROM but it stops during the process. (device is recognized by adb as sideload).
Any ideas of what I could try ?
After a few hours I solved the issue by disabling windows 10 driver signature verification and selecting manually the Oneplus X USB driver. I was then able to flash TWRP in fastboot mode.
Related
I was upgrading the current Stock rom on my ZTE Nubia Z5s Mini, I went through the recovery mode to load the new rom and got a message saying that the rom installed correctly, I rebooted the device and now its stuck at the MIUI logo or if I try to load the recovery mode I get the Nubia logo just to load back to the miui logo again. I got the rom from the MIUI site its v5.
I've left the phone for over an hour hoping it was just loading up but no change, the phone heats up and even has a charger screen when plugged in.
Anyway to get back into the recovery mode to load the original rom again or any other way of fixing this? help :crying:
I've no idea how to help you with this but I'm bumping the thread because I know how you feel.
Sent from my HUAWEI Y536A1
I'm trying to flush the rom by using adb but with an issue, even thou my device is recognized as Nubia Z5s Mini in device manager it still gives a driver error "these have been installed" and in cmd adb it does not see the device.
Update : Got drivers for install from Clockwordmod website but it will only accept the drivers if I set the phone as a modem in device manager when installing them, still not recognized by adb using CMD.
Solved driver issue and qusb_download issue, ADB drivers are done through all drives in device manager pointing to the Google USB drivers and select adb interface then run CMD from within the Google SDK program folder in platform-tools to read the device.
Now using emmc but need to generate EMMCBLD.HEX & 7x30_msimage.mbn if anyone can help, I can enter adb using recovery mode but blocked from making changes in fastboot mode, currently in download mode which can see a drive H but need the two files to proceed any further.
I was on Unofficial CM13 by SultanXDA!
For further update it requires OOS 3.1.3 Firmware, so I flashed OOS 3.1.3 pure!
It comes with its stock recovery i.e. I need to flash TWRP for same!
I had drivers and minimal adb-n-fastboot installed already and also $adb devices detects my device!
So, when i connect device with fastboot mode to flash TWRP it detects my Android bootloder device (according to device manager | win10) but
Code:
fastboot device
<waiting for device>
doesn't work and stuck there only!
If you can boot into OS could root with KingRoot and flash recovery with app like Rashr or Flashify.
Are you tried this process with other versions of Windows (lower than window 10)?
Windows 10 have some drivers problem.
Is your opx boot?
If Android Emulator program (Bluestack, Andy etc) is installed on your computer, you should remove it. And try again...
yuv93 said:
Are you tried this process with other versions of Windows (lower than window 10)?
Windows 10 have some drivers problem.
Is your opx boot?
Click to expand...
Click to collapse
Although I'm not the OP I had the same problem.
Used my older Laptop with Win7 and I was able to find my opx in fastboot mode thanks for saving my life <3
Nagesh_Noddy said:
I was on Unofficial CM13 by SultanXDA!
For further update it requires OOS 3.1.3 Firmware, so I flashed OOS 3.1.3 pure!
It comes with its stock recovery i.e. I need to flash TWRP for same!
I had drivers and minimal adb-n-fastboot installed already and also $adb devices detects my device!
So, when i connect device with fastboot mode to flash TWRP it detects my Android bootloder device (according to device manager | win10) but
doesn't work and stuck there only!
Click to expand...
Click to collapse
had the same on ubuntu, my solution may also work for your problem .. run the console as admin and see if it detects your device! if not you probably need to install oneplus drivers
regards,
OD
Hello to everyone.
I hope somebody to help me, last night i tried to update mi Lineage OS 16 (from erfanoabdi).
My device is unlocked bootloader, and i used the rom from nightly build (2018-21-09), it works fine and everything, the issue becomes when i look what was avaible a new update, so downloaded and install the new rom.
I do full wipe, after that i install the new rom, at this point everything its working fine, but after that when i changed the partition slot from A to B.
When i started to install the gapps they closed because it says what i am running Android 8.0, but its a mistake so i think that reboot the phone without install the gapps. So the phone starts well, so i decide again to boot into recovery (TWRP) to install the missing gapps.
When the device reboot in fastboot and i chosee the recovery option, the surprise was that TWRP was reemplaced by the stock recovery, and when i tried to flash the TWRP.img my device wont appear in fastboot mode, stays finding device and Windows wont recognized my phone.
I think the rom still no have usb adb support, so i cant flash TWRP
My device its unlocked and i was running the rom (but another nightly) .. without issues for a week ago... until i flashed this one
Now i have Lineage OS without GAPPS, without USB mode... Like the update from OPW 27 or 28 idk remember.
Its possible to fix? or my phone its ****ed, or there is one form to installl the gapps from anoter form?
Thanks for read this i hope somebody can help me.
My device its a XT1900-4 in Android 9.0 without google apps, only have the essencial apps like phone dialer , sms, the very very essencials app. Like an phone from 2008 jhaha
i offer some pay.
Update:
I attach some information photos from the Rom that im running:
(System Running) fine thanks
https://ibb.co/bXC7ye
(ADB is switched on, but no appears nothing)
https://ibb.co/exGpBz
(I tried with everyone of the opcions
https://ibb.co/ekv5jK
and this is my currently fastboot:
AP Fastboot Flash Mode (Secure)
BL: MBM-3.0-uefi-641a15b-180224
Baseband: M660_7042.27.01.74R PAYTON_LATAM_CUST
Product/Variant: payton xt1900-4 32GB P4
CPU: SDM630 1.0 (6)
Console [NULL]: null
Tools Mode Config: DISABLED
POWER OK
flashing_unlocked
Software status: Official
Transfer Mode: USB Connected
At this point my windows so says to my device is Error in a request for the USB device descriptor.
i tried last_usb_google driver.
Motorola Device manager 2.5.4
Minimal adb fastboot 1.4.2
and nothing works fine.
In my recovery appears this:
Android Recovery
motorola/payton/payton
8.0.0/OPW27.57.25-6-10/12
user/release-keys
Use volume to...etc and then i used the (Apply update from adb)
says:
Supported API: 3
Stopping adbd. . .
Now send the package you want to apply to the device with "adb sideload <filename>"
Help me pls:crying:
UPDATE :
Hello to everyone.
I hope somebody to help me, last night i tried to update mi Lineage OS 16 (from erfanoabdi).
My device is unlocked bootloader, and i used the rom from nightly build (2018-21-09), it works fine and everything, the issue becomes when i look what was avaible a new update, so downloaded and install the new rom.
I do full wipe, after that i install the new rom, at this point everything its working fine, but after that when i changed the partition slot from A to B.
When i started to install the gapps they closed because it says what i am running Android 8.0, but its a mistake so i think that reboot the phone without install the gapps. So the phone starts well, so i decide again to boot into recovery (TWRP) to install the missing gapps.
When the device reboot in fastboot and i chosee the recovery option, the surprise was that TWRP was reemplaced by the stock recovery, and when i tried to flash the TWRP.img my device wont appear in fastboot mode, stays finding device and Windows wont recognized my phone.
I think the rom still no have usb adb support, so i cant flash TWRP
My device its unlocked and i was running the rom (but another nightly) .. without issues for a week ago... until i flashed this one
Now i have Lineage OS without GAPPS, without USB mode... Like the update from OPW 27 or 28 idk remember.
Thanks for read this i hope somebody can help me.
My device its a XT1900-4 in Android 9.0 without google apps, only have the essencial apps like phone dialer , sms, the very very essencials app. Like an phone from 2008 jhaha
i offer some pay.
Update:
I attach some information photos from the Rom that im running:
(System Running) fine thanks
https://ibb.co/bXC7ye
(ADB is switched on, but no appears nothing)
https://ibb.co/exGpBz
(I tried with everyone of the opcions
https://ibb.co/ekv5jK
and this is my currently fastboot:
AP Fastboot Flash Mode (Secure)
BL: MBM-3.0-uefi-641a15b-180224
Baseband: M660_7042.27.01.74R PAYTON_LATAM_CUST
Product/Variant: payton xt1900-4 32GB P4
CPU: SDM630 1.0 (6)
Console [NULL]: null
Tools Mode Config: DISABLED
POWER OK
flashing_unlocked
Software status: Official
Transfer Mode: USB Connected
At this point my windows so says to my device is Error in a request for the USB device descriptor.
i tried last_usb_google driver.
Motorola Device manager 2.5.4
Minimal adb fastboot 1.4.2
and nothing works fine.
In my recovery appears this:
Android Recovery
motorola/payton/payton
8.0.0/OPW27.57.25-6-10/12
user/release-keys
Use volume to...etc and then i used the (Apply update from adb)
says:
Supported API: 3
Stopping adbd. . .
Now send the package you want to apply to the device with "adb sideload <filename>"
I tried to navigate in the device with the terminal app, so i put this command in terminal to make ADB run
command adbd, and this appears on terminal:
adbd E 10-04 23:01:31 3819 3819 adbd_auth.cpp183] Failed to get adbd socket: success
adbd E 10-04 23:01:31 3819 3819 adbd_auth.cpp183] Failed to get adbd socket: success
i try to run command logcat.txt, but terminal cant move to sdcard.
i try to adb over network and that connect but can´t do anything because stuck on <waiting device>, i look the blankflash but
didn´t works to me, and in the configurations usb settings looks greyed so cant switch between then.
when i run the command ls i saw this files:
init.usb.configfs.rc
init.usb.rc
init.recovery.qcom.usb.rc
maybe there is my problem? Thanks for read, thanks to @erfanoabdi he works very hard to make this possible, i hope somebody can
help me.
Anyone??
I have LineageOS 16.0 installed on my OnePlusOne
I used MutiROM before, uninstalled it, but MultiROM Recovery is still installed.
Today I downloaded update for LineageOS but I got "Updater process ended with ERROR: 7"
Now I can't boot to OS because it boots straight to recovery.
The solution is to flash normal recovery and then flash LineageOS zip (I stopped using MultiROM because I had these issues before)
But I can't transfer Recovery.img to my OnePlus One.
While I'm in Recovery, neither MTP or ADB are working and there's no option to enable them.
And while I'm in Fastboot, PC can't see any fastboot devices.
It's not the PC's fault because it can recognize my Xiaomi Redmi Note 7 in both ADB and Fastboot mode.
So basically I need a way to transfer Recovery.img from PC to phone.
-I can access only TWRP and Fastboot.
-I can't do anything over USB cable.
-OnePlus One doesn't have microSD card slot so I can't do it that way.
-And I tried plugging in USB OTG drive and phone can't recognize it. It won't even send the power to OTG drive.
Is there any other way that I haven't tried yet?
I have Redmi note note 5 pro and I rooted my device successfully on the version miui 11.0.3.0 with twrp recovery
and after root my device is unable to connect with any pc and laptop (tried everything from trying on multiple pc to buying new usb cables)
But It doesn't bothered me so I did nothing about it...but yesterday I tried to update my device to version miui 11.0.5.0 using full recovery rom but due to that my root access is gone with installing stock recovery .
And now every time when I try to enter into fastboot mode, it is not detecting my device (I've tried installing fastboot adb drivers and once again tried changing usb cable but it still not detecting).
Please help me I only want to install any custom recovery which help me root my device
Device - Redmi Note 5 pro
Android version - 9
Miui version - 11.0.5.0
USB debugging is on
bootloader is unlocked