I flashed latest 6.0 image on toolkit and pulled usb before fully booted. Now everything force close cant boot and usb debug not enabled. I tried flash all bat and adb but hangs at waiting for device. How do i get my phone recognized on adb? UPDATE was able to wipe data in stock recovery and no more FC
cell2011 said:
I flashed latest 6.0 image on toolkit and pulled usb before fully booted. Now everything force close cant boot and usb debug not enabled. I tried flash all bat and adb but hangs at waiting for device. How do i get my phone recognized on adb? UPDATE was able to wipe data in stock recovery and no more FC
Click to expand...
Click to collapse
well, if it wont boot, how is everything force closing? anyways, you do not flash a factory image with adb, you use fastboot while you are in the bootloader. adb is for everything else.
Related
Hi,
I was on 5.0, running stock recovery and rooted. Today, installed TWRP for 5.0 on my device. I tried to flash the droid command center widget on my phone usng twrp, and it failed. I also hit the fix permissions option. After that the phone does not boot up, simply flashes the unlocked bootloader sign and shows the moto boot animation for a second or two before shutting down.
I can boot into recovery, and the computer detects the phone. But adb doesn't detect the device. I have the 1092 5.0 OTA on my computer and saved it on the phone in an attempt to flash it thru TWRP, but that failed with the message shown in the img attached. I also tried flashing stock 4.4.4, but that gave an error "Updating partition details" failed.
Can someone help me get back into my phone? :crying: ADB doesn't seem to be detecting my phone, else I'd have tried to install a rom via fastboot.
I have multi-tool v4.1 installed, would I be able to flash a rom (stock unrooted and full wipe is perfectly fine too) via that considering adb does not detect my phone, but the computer does?
Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
oldcynic said:
Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Click to expand...
Click to collapse
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?
HAXTREME said:
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?
Click to expand...
Click to collapse
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.
oldcynic said:
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.
Click to expand...
Click to collapse
Ah yes. For some reason, my fastboot file had gotten deleted from the folder and so the command didn't run. Everything went smooth once I noticed that. Had to downgrade to 4.4.4., but w/e. Thanks @oldcynic
Last night I was running 5.0 Lollipop GPE on my unlocked Telus HTC One M7, when I got a notification for an OTA update to 5.1 . I let it download and install, it booted up and then ran through Optimizing Apps. When it finished, the phone rebooted - and then got stuck in this loop. I can either boot the phone and it starts Optimizing Apps (again) or I can get to the bootloader screen. Entering Recovery mode (then holding power and volume up) doesn't do anything- just leads me back into this loop.
Figured I need to flash the phone now, but cannot get it to show up when I run adb devices (just an empty list). I'm not sure if the phone isn't in USB debugging mode or there is something else going on here. I've tried both Mac and PC with several drivers, multiple usb cables, and any other potential solution google came up with. It obviously worked in the past in order to flash 5.0 GPE, but doesn't work now and not sure what has changed.
Any suggestions on getting out of this mess? Can I somehow flash it without being able to boot? Thanks!
Revolution_09 said:
Last night I was running 5.0 Lollipop GPE on my unlocked Telus HTC One M7, when I got a notification for an OTA update to 5.1 . I let it download and install, it booted up and then ran through Optimizing Apps. When it finished, the phone rebooted - and then got stuck in this loop. I can either boot the phone and it starts Optimizing Apps (again) or I can get to the bootloader screen. Entering Recovery mode (then holding power and volume up) doesn't do anything- just leads me back into this loop.
Figured I need to flash the phone now, but cannot get it to show up when I run adb devices (just an empty list). I'm not sure if the phone isn't in USB debugging mode or there is something else going on here. I've tried both Mac and PC with several drivers, multiple usb cables, and any other potential solution google came up with. It obviously worked in the past in order to flash 5.0 GPE, but doesn't work now and not sure what has changed.
Any suggestions on getting out of this mess? Can I somehow flash it without being able to boot? Thanks!
Click to expand...
Click to collapse
use fastboot commands, usb debug is only to enable adb when the os is booted.
Code:
fastboot devices
alray said:
use fastboot commands, usb debug is only to enable adb when the os is booted.
Code:
fastboot devices
Click to expand...
Click to collapse
Thank you! Everything else went smoothly and I've flashed 5.1 now.
I updated my oneplus and i got the TWRP decryption message, so i formatted it back to the stock format.
now all the phone does is boot into the bootloader but gets stuck on the boot screen of Blu Spark 3.1.1
my computer wont recognize it while its in the bootloader or while its stuck trying to boot in twrp
is there anything i can do or is my phone screwed at this point? i see a lot of threads that would answer parts of my issue but nothing that covers this as a whole. id rather ask for help now while there may be some hope.
nickhawkjones said:
my computer wont recognize it while its in the bootloader or while its stuck trying to boot in twrp
Click to expand...
Click to collapse
So no response to fastboot commands, while in bootloader-fastboot mode?
Are you sure you installed the right drivers for your pc? If all else fails, you can do this.
This is how I fixed my phone when i was stuck at a black screen. You can also try a different usb cord or port. Check device manager and see if it recognizes it when its plugged in. hope this helps!
https://www.youtube.com/watch?v=BvfA5WrVDQM
can you boot into fastboot? if your phone can boot to fastboot mode..just flash stock recovery image..then flash rom via adb shell (better flash the stock rom). if it works you can reinstall the custom recovery image or something. dont forget to erase everything via stock recovery..
I'm stuck at an issue that I've never seen before and need some assistance. I flashed invictrix 8.1.0 not to long ago and then installed an updated version of the rom through the rom's updater. It went through the automated flashing of the updated version and now I'm stuck in a recovery that seems to be stock, but it's not the stock version I am accustomed to seeing. I can not do anything in this recovery. I have used adb to do things before, but now adb and fastboot seem to get stuck at waiting for device errors or error:device not found even though adb devices and fastboot devices brings up the phone being connected. I now can no longer boot into the phone as I did a hard reset while my phone was operational.
Have you tried booting straight into fastboot mode by holding down Power+Vol Up until it reboots? And then see if you can use fastboot on your PC to flash TWRP again.
Also, all those error messages. Did you at some point reformat the cache partition as f2fs? It's supposed to be ext4..
I can boot into fastboot. The computer recognizes the phone through fastboot devices and adb devices. However, issuing a command through fastboot results in a waiting for device message. Maybe I need to find a more suitable adb. The one I’ve been using is the 15 second adb that only installs the google driver and the adb. I never formatted anything. I’m not sure what to do at this point.
I would use an unbrick guide and start from scratch.
Is there one you'd recommend ? I'm using this one :
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Yes, I also used it in the past and everything was ok.
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:
I have a Nokia 7 plus which is also a A/B device. I have observed many times that the fastboot mode isn't detected by the pc. Sometimes when I have a bootloop during experimentation, I force reboot into bootloader mode but it's not recognised. I reboot into recovery and select "reboot to bootloader", and this time it's recognised. Maybe these issues are related to A/B system, I'm not sure.
I think you should have the Motorola device manager installed if you're working on Windows. It contains the necessary drivers. I can't remember if it contains adb and fastboot executable files, but if it does then try using them (launching command prompt from there).
Broadcasted from Zeta Reticuli
Gravemind2015 said:
I have a Nokia 7 plus which is also a A/B device. I have observed many times that the fastboot mode isn't detected by the pc. Sometimes when I have a bootloop during experimentation, I force reboot into bootloader mode but it's not recognised. I reboot into recovery and select "reboot to bootloader", and this time it's recognised. Maybe these issues are related to A/B system, I'm not sure.
I think you should have the Motorola device manager installed if you're working on Windows. It contains the necessary drivers. I can't remember if it contains adb and fastboot executable files, but if it does then try using them (launching command prompt from there).
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
thanks for quicky reply, but i tried that and it doesnt work for me... :c
the motorola device manager its installed correctly, but i think the usb in the Android 9 it´s no working on running s.o and even in fastboot.
vmmiguel said:
thanks for quicky reply, but i tried that and it doesnt work for me... :c
the motorola device manager its installed correctly, but i think the usb in the Android 9 it´s no working on running s.o and even in fastboot.
Click to expand...
Click to collapse
My windows cmputer says that my device doesnt works properly, i read all night about this and i think when i some point i made wipe /system so i delete the twrp and the rom doesnt have usb adb i think so hahaha, i think now my x4 will stuck on only aosp 9.0 without g services :crying::crying::crying:
id start with a flash all of the latest stock firmware to clean it up. then start over
edufur said:
id start with a flash all of the latest stock firmware to clean it up. then start over
Click to expand...
Click to collapse
I tried but i have only stock recovey, and the usb adb it's not working, i think that i need to flash stock rom from stock recovery, but i dont know...
vmmiguel said:
I tried but i have only stock recovey, and the usb adb it's not working, i think that i need to flash stock rom from stock recovery, but i dont know...
Click to expand...
Click to collapse
You have to flash stock rom from fastboot. Try removing "fastboot erase userdata" from script flash-all.
Comby_sk said:
You have to flash stock rom from fastboot. Try removing "fastboot erase userdata" from script flash-all.
Click to expand...
Click to collapse
Hello Buddy, i tried that but doesnt work, recently i discover that my usb default mode is gray so i think i cant switch beetwen the usb option, and i tried ADB over network, in terminal emulator to run adbd service but it crash :c
@erfanoabdiadbi plz you cant help me, i really i was enjoying you excelent deveploment, but now in stuck in this without essencial apps like whatsapp, my smartphone works like only phone without been smart jajaja:crying::good:
Anyone?
vmmiguel said:
Anyone?
Click to expand...
Click to collapse
Read through this thread carefully...
https://forum.xda-developers.com/moto-x4/development/rom-lineage-16-0-developer-preview-t3849699
I have more or less the same problem.
I am stuck in LineageOS 15.1 and for some reason Windows does not recognize my phone (it does with other x4 phone from a friend).
I also don't have GApps installed and also don't have root access. Since I can't connect my phone, I can't root or flash some custom recovery.
I really need some help.