I tried to install LineageOS on my N7. When I tried to perform a factory reset, the system went into an erasing state, but it stays there fore-ever. It is not rebooting completely, but the erasing animation is restarted every x seconds.
I am not able to enter recovery / bootloader. All combinations with power + volumeUP / volumeDOWN don't do anything. After the Google logo is continues to the Erase situation.
So I am not able to enter fastboot.
But I am also not able to use ADB. The device is recognised, but unauthorized.
Has anyone an idea how to proceed?
i had the same problem, and i think that your device is hard bricked. i recently replaced the motherboard with a new one and solved the problem!
Related
Hello:
Q: How to boot in recovery mode (factory reset) without power button?
My Nexus 4 was running fine on Android 5.1.1 with broken power and volume buttons for months. After a while using Kingroot and a power button manager (root required), it got stuck in a bootloop (4 color balls are rotating). Since I have the USB Debugging activated in the developer option already, I am trying to "boot to recovery" via the usb cable from my PC. However, all the adb commands (adb devices, etc.) shows that the device is unauthorised (I had never authorized my PC before). Is it possible to somehow get to the "recovery boot" at my situation? (I've tried everything, adb and sdk are the latest versions ...)
Can anyone help me to do a factory reset or anything to bring the phone back to life?
PS: I would have replace the power and volume buttons but some of the phone screws are broken so I cannot take it fully apart).
Update
I somehow managed to short circuit the power button and the volume down button and got to the "recovery mode".
However, I cannot confirm the recovery mode since I don't have a power button. adb was able to detect my device when it was in a bootloop (although it was unauthorized) but adb don't detect the device now that it is in the recovery mode.
Is there anyways to confirm the recovery mode (and do the factory reset)?
You can erase userdata and cache from fastboot using fastboot commands.
Fix the power button
After performed wipe cache and firmware update with "Swift&Fast Slim B160 aio" ROM, the phone reboot and stuck at waiting for booting... ==> wait for 3 hours and still show the same as BOOTING.
Performed the factory reset by press Volume Up and Power, the Factory Reset is now stuck at 99%
Please help to the the phone back in working condition.
Resolved yet?
Possible idea
You can probably still load TWRP. Press and hold volume down + power at the same time to load fastboot mode.
ROM Flashing
Obtain a ROM of your choice, and note the location on your computer.
reboot your device into fastboot mode via one of the following options.
1. adb reboot bootloader (requires USB debugging to be turned on).
or...... power off the device then back on with 'vol up' + power button.
Wipe your device.
2. fastboot -w
Update your ROM.
3. fastboot update </path/to/your/RomFile.zip>
Your phone will update and automatically reboot into the new ROM. Try another ROM if Swift & Fast Slim isn't working. Your file could be corrupted.
did u get things fixed?
Hi,
I did a TWRP wipe (everything checked) to prepare for a restore to stock, but my device is now stuck at the very first "Google" screen with the pad lock icon at the bottom. How do I get it to boot?
goister said:
Hi,
I did a TWRP wipe (everything checked) to prepare for a restore to stock, but my device is now stuck at the very first "Google" screen with the pad lock icon at the bottom. How do I get it to boot?
Click to expand...
Click to collapse
So since everything was checked, that means you wiped the system partition. The device will not boot if you do that unless you flash a factory image via fastboot or new ROM via TWRP
OK, I thought wiping /system would just bring it back to factory state. 2 questions now
1. How do I get to recovery when it's always stuck at the Google screen with no adb access? Would I have to wait for the battery to run out (hence turn off), charge it for a while, then use the buttons to boot to recovery, or is there a faster way?
2. I am actually trying to revert to stock ROM (downloaded at https://developers.google.com/android/images#angler) by following step 10 of the Heisenburg guide (https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928) which advises me to use fastboot to flash the individual images. In my case, how do I boot to fastboot?
OK, so I managed to boot to the bootloader and run the following commands as per the Heisenberg guide (using the stock MTC20L firmware)
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash cache C:\angler\images\cache.img
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
Everything was successful, and I did a fastboot reboot after that.
However, my device still doesn't boot up. This time. It's boot loops for a few times before turning off.
I tried booting up to bootloader with power/vol-. Curiously, I can now only do this when cable is connected. If cable is disconnected, the orange LED just blinks once when power button is pressed, and nothing happens. Once cable is connected, then I'm able to boot up to bootloader with the button combination. I then retried the flash process again, but still no go. I noticed after fastboot reboot that the orange LED blinked a few times before rebooting and boot looping.
Kinda stuck now, any ideas?
Try booting into recovery and doing a factory reset. I've had that happen to me a few times after flashing factory images and a wipe in recovery always fixed it.
Just for future information: if at any time the device is stuck in a bootloop you can get it to robot into recovery by holding the power and volume down buttons for 10 seconds, or get it to boot into bootloader by holding power and volume up buttons for 10 seconds.
Face_Plant said:
Try booting into recovery and doing a factory reset. I've had that happen to me a few times after flashing factory images and a wipe in recovery always fixed it.
Just for future information: if at any time the device is stuck in a bootloop you can get it to robot into recovery by holding the power and volume down buttons for 10 seconds, or get it to boot into bootloader by holding power and volume up buttons for 10 seconds.
Click to expand...
Click to collapse
Thanks. Booting into stock recovery shows an exclamation sign with "no command", since I don't have TWRP anymore. Would I need to first flash TWRP before I can do a factory reset?
I just tried flashing to the same sock firmware as before the problem happened (7.1.2 N2G47W) but still same problem. I notice that after the Google logo disappears and the screen goes blank, the orange LED blinks 10 times before rebooting.
Edit: Tried factory resetting in stock recovery (by holding down power button and pressing vol+), the rebooting after factory reset. Still getting a boot loop.
OK I solved the problem. Apparently if you reboot after the flash, you need to disconnect the USB cable, else it will boot loop.
OK I solved the problem. Apparently if you reboot after the flash, you need to disconnect the USB cable, else it will boot loop.
goister said:
OK I solved the problem. Apparently if you reboot after the flash, you need to disconnect the USB cable, else it will boot loop.
Click to expand...
Click to collapse
brother help me! i am facing same issue
first little info abt my device.
my device was running on android nougat with twrp recovery installed but the device was not rooted.
so get back to stock and install oreo I followed every step given on http://www.androidexplained.com/nexus-6p-revert-stock/ but somehow my phone is stuck at bootloop with no recovery installed.
Please help me here.
As per the Heisenberg guide, if you don't install root (SuperSU or Magisk), TWRP won't stick, so you'll go back to stock recovery.
For me, simply unplugging the USB cable after rebooting after a flash solved my problem. For some reason, if the cable is connected during reboot, it would boot loop.
brother, somehow I managed to install twrp. but everytime I touch it 2-3 times the phone gets switched off.
then it keeps rebooting to 'Google' logo.
can you tell me what should I do now?
@goister Hi how you manage to get to recovery when it's always stuck at the Google screen with no adb access. Please I am stuck there
tommast said:
@goister Hi how you manage to get to recovery when it's always stuck at the Google screen with no adb access. Please I am stuck there
Click to expand...
Click to collapse
hi, did youmanage to solve this problem? I am aving the exct same problem. Disconnecting the ucb isnt working for me
"your device software cannot be checked for corruption" after installing twrp, help!!
Hello, as title says, following oem unlock procedure, i flashed twrp using fasboot however i could never boot it and now when i try to go to fastboot mode and/or reboot, i see this message "your device software cannot be checked for corruption[...] please lock bootloader"!! Dunno what to do? Please help!
Easy: do absolutely nothing, this is intended behaviour. Unlocking the bootloader leads to the displaying of this message on boot up. Just LG's way of saying continue at your own risk.
Ok so they're even more annoying than samsung..! Anyway, my problem is : how do i enter TWRP..? I flashed again, successfully.. Then i dunno how to enter it!
"The stock recovery appears but you have to select the factory reset option and it will boot into TWRP" i read this. Well it's wrong. Doing so just launch the factory reset!
This video https://www.youtube.com/watch?v=MR4DTgTxhGI shows phone reboots to TWRP after entering "fastboot reboot" (once recovery was flash) : here it just reboots normally!
"Finally Type “fastboot boot TWRP-Recovery-filename.img” to boot your LG G6 into TWRP Recovery" well i thought about that and tried it :
D:\Android\ADB&Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.901s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.925s
I'm very disapointed so far, i expected the G6 to be easier to handle the S7 but it's a pain even before i start using it.. Hell!!
It seems to me that you didn't boot into twrp immediately after flashing it via fastboot. Afaik it's important that you don't boot into OS after flashing, otherwise twrp will be overwritten with stock recovery. I had the same problem when I did the procedure.
The only way I got it to work was booting into twrp via button combo immediately after flash (you know - keep pushing power and vol- until Lg G6 logo appears, release only power and immediately push it again, keep 'em pushed until factory reset, confirm twice and it should boot into twrp). Once you've booted into twrp directly after flashing, it should stick.
grushnickij said:
It seems to me that you didn't boot into twrp immediately after flashing it via fastboot. Afaik it's important that you don't boot into OS after flashing, otherwise twrp will be overwritten with stock recovery. I had the same problem when I did the procedure.
The only way I got it to work was booting into twrp via button combo immediately after flash (you know - keep pushing power and vol- until Lg G6 logo appears, release only power and immediately push it again, keep 'em pushed until factory reset, confirm twice and it should boot into twrp). Once you've booted into twrp directly after flashing, it should stick.
Click to expand...
Click to collapse
After doing this, for TWRP to stick, you have to flash a custom rom, or delete the system/bin/install-recovery.sh to prevent stock recovery overtwrite
I was tinkering with my Z500m after a factory reset seemed to cause issues. As I could not boot into recovery I ended up, stupidly it now seems, running "fastboot erase cache", which led to a boot loop on the Asus splash page. I then thought I could do a factory reset through fastboot by erasing system, data and cache (I may have read this somewhere in xda), but this resulted in the tablet booting just to Asus splash and then straight to the 'dead android' with the red triangle and exclamation. This flashes every few seconds. All combinations of post, vol up, vol down, result in nothing, and I cannot get it to boot to fastboot or recovery, let alone a normal boot. If I connect it to my pc, there is a beep from the pc suggesting it is not totally bricked.
I have scoured this site and other useful web sites, but can find no solution. Does anyone have anything to suggest?
Hello, have you found a solution for this problem ?