My phone has been rooted for over a year but today the battery ran out and when I pluged the phone in it just shows the white razer powered by android logo and sits there forever I have been able to boot into fastboot mode but cant get it to show up on adb. I checed that this cable works for adb with another phone. I also tried the "wipe userdata" option but it didn't work. Any ideas on how get out of this?
oops
Download the newest factory image (link) and reflash it.
Related
I flashed to EPE54B via fastboot and in cmd, both sending and writing said "OKAY". The bar on the top right of the phone also completed so I tried to reboot my phone into recovery so that I could flash the new cyanogenmod. Unfortunately, my phone has been stuck on the "X" boot screen (non-animated one with the lock) for an hour now. I have not restarted, removed the battery, unplugged the usb cable, or anything. Also, my computer popped up saying it could not find the drivers for "Qualcomm CDMA Technologies MSM".
Is my phone possibly bricked? Thank you.
iheartn1 said:
I flashed to EPE54B via fastboot and in cmd, both sending and writing said "OKAY". The bar on the top right of the phone also completed so I tried to reboot my phone into recovery so that I could flash the new cyanogenmod. Unfortunately, my phone has been stuck on the "X" boot screen (non-animated one with the lock) for an hour now. I have not restarted, removed the battery, unplugged the usb cable, or anything. Also, my computer popped up saying it could not find the drivers for "Qualcomm CDMA Technologies MSM".
Is my phone possibly bricked? Thank you.
Click to expand...
Click to collapse
no....
reset it (volume down and power button)
restore to your latest nandroid to make sure everything still works right...
now when you try your next flash do a wipe (factory default) first and then try flashing your radio and new rom if you have on
ive had trouble in the past with cyanogen's roms doing the boot loop on the "X screen" in the past so you are not alone... but your most likely error is doing a wipe after your nandroid... then install the new rom... see if that works
So yesterday I went to flash a Kernel and needless to say it didn't work. So just like my Galaxy Nexus, I held down the special key combo and got into the Bootloader, scrolled to Boot Recovery and it went to the Google screen but never went to recovery. I figured it just froze so rebooted into Bootloader and tried again, with the same result. So I tried it again to see if I could even boot normally from the Bootloader and it wouldn't even get past the Google screen doing just a normal boot.
Is anyone else having this issue? May try a full fastboot restore back to stock and re root, but I would like to know if anyone else is having this issue before I move on.
Connect your N7 to a computer via usb and then boot into bootloader and you should be able to get in. It is a known issue that you can't get into recovery unless you send a command via adb or you are connected to a pc via usb.
evonc said:
Connect your N7 to a computer via usb and then boot into bootloader and you should be able to get in. It is a known issue that you can't get into recovery unless you send a command via adb or you are connected to a pc via usb.
Click to expand...
Click to collapse
I just booted to Bootloader, fastbooted my recovery, and without rebooting had no issues just using the Boot Recovery option. Just wandering if anyone else was having this issue.
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.
Hey, I have a Moto X 2014. I'm running a cynanogen mod on it. For some reason the phone is stuck in bootloader mode, then starts up with the cynanogen logo, then just goes back into bootloader and repeats. I've held the power and lower volume key to get into the bootloader menu. I've tried normal, recovery, and factory and nothing seems to work at all. I cant seem to figure out how to get into TWRP, which I think if I can that could solve the problem by wiping some data and flashing a new ROM. Any thoughts or ideas how to fix this? Also, the phone wont show up as registered on my computer when I plug in the USB cord, so an command prompt "adb recovery" isn't an option I think. If you need more specifics please ask! Really dont want to have to get a new phone.
You can try to enter recovery through the PC command 'fastboot reboot recovery'. If that doesn't work, look up how to flash the stock firmware using fastboot.
As the title states, my phone is stuck in a bootloop, and only fastboot works. Trying to go into recovery or rescue mode results in going back to the bootloop instead of actually going to rescue/recovery mode. Any fastboot commands result in `waiting for device` even though it shows the device in `fastboot devices`.
Is there anything I can do to try to get it to work again?
I have gotten it into recovery mode before and was able to factory reset it, however when I plugged it in the phone crashed and went back into a bootloop, and now loading into recovery mode does not work.
Also if it's any help, I previously had the device rooted with magisk, I powered it off and when I powered it back on it went into a bootloop (I did not make any changes like installing/updating magisk plugins prior to shutting it down).
Update to this: I was able to install graphene os via command line.