Project Fi MOTO x4
anybody know to to unsecure flashboot flashmode?
installed TWRP/Root
reverted to stock
downloaded OTA up to March 1st
adb doesnt work in recovery to update OTA manually
Flashed Payton_fi 8.0.0 again
updated to March 1st Again
now adb commands wont work but fastboot commands do however AP Mode is Secure.
Locked/Unclocked bootloader
Shut off lockscreen
turned ADB on/off in dev settings
turned OEM unlock on and off in dev
tried fastboot commands to set AP Mode (clear cache, set mode, etc...)
Still locked AP Mode Secure.
even ran flash stock via fastboot but almost all comands fail.
tried with 2 different pcs so ive definitly messed up something in the bootloader
azazelcrey said:
Project Fi MOTO x4
anybody know to to unsecure flashboot flashmode?
installed TWRP/Root
reverted to stock
downloaded OTA up to March 1st
adb doesnt work in recovery to update OTA manually
Flashed Payton_fi 8.0.0 again
updated to March 1st Again
now adb commands wont work but fastboot commands do however AP Mode is Secure.
Locked/Unclocked bootloader
Shut off lockscreen
turned ADB on/off in dev settings
turned OEM unlock on and off in dev
tried fastboot commands to set AP Mode (clear cache, set mode, etc...)
Still locked AP Mode Secure.
even ran flash stock via fastboot but almost all comands fail.
tried with 2 different pcs so ive definitly messed up something in the bootloader
Click to expand...
Click to collapse
(next day)
Got this to flash without errors payton_fi-user 8.0.0 OPWS27.57-25-6-10 10
While installing the 8.1 OTA Blur_Version.28.11.15.payton_fi.google_fi.en.US.zip (through recovery) it starts but reaches 0.0%
At least its trying to install.
Dd you ever recover from this? I am in that same bootloader mode, and am unable to flash anything.... I let Lineage OS 15.1 do an OTA update, and when rebooting after installation was complete, I ended up here...
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 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.
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.
I installed Evolution X rom 4.7 on my Mi A2 device with twrp and also installed magisk.Then I flashed Agni Kernel for performance after some days.When the update of evolution x came I decided to update it via dirty flashing the zip file.Then the device booted and the kernel was reverted back to evo-x main kernel.But then I realized that twrp recovery and root permission are completely gone after the boot.Still I ran the device for some time and after some day I had to reset my pc in which adb,fastboot etc. were previously installed.But now when I connect the phone with pc on fastboot mode,it doesn't show my device's name.And now I cannot manually install the adb drivers of the phone.I thought factory resetting evolution x will solve it but it did't.Now my phone has no recovey,and no os .I also tried to use MiFlash to flash stock rom but the device disappears from the list after selecting flash.I cannot find any solution for this device.Please help me.
(When I unlocked bootloader for the first time I used fastboot flashing unlock and unlock_critical both)
i think u use adm cpu cause this happens mostly there nly ...dw just flash a good and stable firmware via otg and this should fix this
IrazShahriar said:
I installed Evolution X rom 4.7 on my Mi A2 device with twrp and also installed magisk.Then I flashed Agni Kernel for performance after some days.When the update of evolution x came I decided to update it via dirty flashing the zip file.Then the device booted and the kernel was reverted back to evo-x main kernel.But then I realized that twrp recovery and root permission are completely gone after the boot.Still I ran the device for some time and after some day I had to reset my pc in which adb,fastboot etc. were previously installed.But now when I connect the phone with pc on fastboot mode,it doesn't show my device's name.And now I cannot manually install the adb drivers of the phone.I thought factory resetting evolution x will solve it but it did't.Now my phone has no recovey,and no os .I also tried to use MiFlash to flash stock rom but the device disappears from the list after selecting flash.I cannot find any solution for this device.Please help me.
(When I unlocked bootloader for the first time I used fastboot flashing unlock and unlock_critical both)
Click to expand...
Click to collapse
If you have another Android phone and an otg adapter use bugjaeger app and use adb and fastboot in that device instead of your pc
IrazShahriar said:
I installed Evolution X rom 4.7 on my Mi A2 device with twrp and also installed magisk.Then I flashed Agni Kernel for performance after some days.When the update of evolution x came I decided to update it via dirty flashing the zip file.Then the device booted and the kernel was reverted back to evo-x main kernel.But then I realized that twrp recovery and root permission are completely gone after the boot.Still I ran the device for some time and after some day I had to reset my pc in which adb,fastboot etc. were previously installed.But now when I connect the phone with pc on fastboot mode,it doesn't show my device's name.And now I cannot manually install the adb drivers of the phone.I thought factory resetting evolution x will solve it but it did't.Now my phone has no recovey,and no os .I also tried to use MiFlash to flash stock rom but the device disappears from the list after selecting flash.I cannot find any solution for this device.Please help me.
(When I unlocked bootloader for the first time I used fastboot flashing unlock and unlock_critical both)
Click to expand...
Click to collapse
I had a same issue today, i tried to install Android 12 into my device witch was a success, but then the rom keeps reboot. Then I booted into fastboot mode, then i realised the icon of the fastboot has changed and the other roms also keeps crashing. After I tried to restore the original firmware, but it was went wrong, after the flasher installed the system_b the phone restarted, and wont start booting up, then I was put the device into fastboot mode and the pc didn't recognised my phone.
Solution: I dissasembled my phone and i tried to boot my phone to edl mode this video helped me a lot. He forgot to mention, when you short this 2 pins in the motherboard you need to connect the battery AND hold the power button as well to enter edl mode. After you need to install the Qualcomm edl driver then you can install your firmware with MiFlash