So I've wiped the Dalvik Cache, Data, Internal Storage, and System, but I forgot to flash before rebooting. Now it's stuck in the WARNING BOOTLOADER UNLOCKED screen and everytime I tried resetting to recovery mode it would turn off then turn back on at the same screen. ADB is not detecting the devices also. Is there anything I can do or is it bricked?
the_onlyhope said:
So I've wiped the Dalvik Cache, Data, Internal Storage, and System, but I forgot to flash before rebooting. Now it's stuck in the WARNING BOOTLOADER UNLOCKED screen and everytime I tried resetting to recovery mode it would turn off then turn back on at the same screen. ADB is not detecting the devices also. Is there anything I can do or is it bricked?
Click to expand...
Click to collapse
Boot into bootloader by holding down vol down and power together. The timing can be a little tricky when it is stuck or looping. Hold power until the screen goes dark and it tries to reboot, usually about 8 seconds. Then let go and immediately hit vol down + power together. Hold them until the bootloader screen comes up, should be pretty fast. Might take a few tries to get the technique down with it bootlooping.
From there you can flash firmware directly with fastboot, or boot it into TWRP to flash something from recovery. If TWRP fails to boot for some reason then fastboot flash it again.
It should not be a brick just from wiping everything. Well, just a soft brick anyway.
Thanks!
I was able to get into recovery!!
Related
I gave my old phone Defy Red lens to a friend. He messed around with bootloader and now the OS does not see any internal storage so i can't install any bootloaders.
Can't acces custom bootloader.
I can only acces a recovery mode but my options are limited.
I did a full wipe and cache wipe from the recovery mod but i only managed to get inside os but all data resets everytime and there is no storage as stated before.
Please check attached photos for more information on build etc.
I tried RSD lite but it won't see phone while in recovery mode.
Any help is appreciated.
mmd1990 said:
I gave my old phone Defy Red lens to a friend. He messed around with bootloader and now the OS does not see any internal storage so i can't install any bootloaders.
Can't acces custom bootloader.
I can only acces a recovery mode but my options are limited.
I did a full wipe and cache wipe from the recovery mod but i only managed to get inside os but all data resets everytime and there is no storage as stated before.
Please check attached photos for more information on build etc.
I tried RSD lite but it won't see phone while in recovery mode.
Any help is appreciated.
Click to expand...
Click to collapse
Bootloader is already in the phone, you must be talking about custom recovery. When you reboot your phone, a blue LED will light up. Immediately push volume down, then choose recovery->Teamwin recovery.
To enter bootloader, switch off your phone, then first press volume up then power button, keep them pressed until the screen lights up a little, then let them go. A screen appears, which is the bootloader. This is needed for RSDLite.
About your problem, download AROMA/full wiper zip. Go to custom recovery, then press install and choose the zip. Choose EXT4 and wipe system, data and cache. DO NOT REBOOT. After that, immediately flash a ROM+Gapps.
By the way, when you cleared data and cache in stock recovery (the one in the photo), they were formatted to ext3, which led to those problems.
hotdog125 said:
Bootloader is already in the phone, you must be talking about custom recovery. When you reboot your phone, a blue LED will light up. Immediately push volume down, then choose recovery->Teamwin recovery.
To enter bootloader, switch off your phone, then first press volume up then power button, keep them pressed until the screen lights up a little, then let them go. A screen appears, which is the bootloader. This is needed for RSDLite.
About your problem, download AROMA/full wiper zip. Go to custom recovery, then press install and choose the zip. Choose EXT4 and wipe system, data and cache. DO NOT REBOOT. After that, immediately flash a ROM+Gapps.
By the way, when you cleared data and cache in stock recovery (the one in the photo), they were formatted to ext3, which led to those problems.
Click to expand...
Click to collapse
Thanks, now I can get in teamwin recovery and in bootloader I will try to fix the phone now. Have a nice day!
Hi Folks,
My Yu Yureka phone was stuck in bootloop so i tried to do softbrick. That is flashed the phone in fastboot mode, entered into recovery mode, choose wipe data and factory reset. When it was wiping the data some how in the middle screen went blank and from then the phone does not boot. Pressed Vol up +down + power button and nothing happens. So i belive the entire data on phone including the OS is wiped out. Now how do i install fresh OS into it? Any idea ?
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
LS997 (September 2016 security patch), got to the end of root and couldn't reboot into TWRP recovery. The device is recognized in ADB while in fastboot but when I'm at the secure startup it's unrecognized, like USB debugging is disabled.
https://forum.xda-developers.com/v20/how-to/guide-root-twrp-lg-v20-using-dirtysanta-t3722278
If you've hit secure startup the phone has likely booted into regular Android far enough to replace twrp with stock recovery. Reboot into fastboot and reflash twrp (you can use the newest twrp if you want). Once done flashing unplug from PC and pull the battery. Reinsert the battery then boot into twrp via the factory reset/volume button method: hold volume down, press power until the screen turns on then (still holding vol - ) tap power repeatedly until a prompt to factory reset appears. Approving it twice boots twrp if it's installed, otherwise stock recovery will do the reset.
Once in twrp go to wipe, then format data (type yes to confirm), then go to reboot, then recovery. Once twrp restarts flash your choice of magisk/supersu.
Once one of those two is installed it makes it so twrp won't be replaced.
Phoenix591 said:
If you've hit secure startup the phone has likely booted into regular Android far enough to replace twrp with stock recovery. Reboot into fastboot and reflash twrp (you can use the newest twrp if you want). Once done flashing unplug from PC and pull the battery. Reinsert the battery then boot into twrp via the factory reset/volume button method: hold volume down, press power until the screen turns on then (still holding vol - ) tap power repeatedly until a prompt to factory reset appears. Approving it twice boots twrp if it's installed, otherwise stock recovery will do the reset.
Once in twrp go to wipe, then format data (type yes to confirm), then go to reboot, then recovery. Once twrp restarts flash your choice of magisk/supersu.
Once one of those two is installed it makes it so twrp won't be replaced.
Click to expand...
Click to collapse
Did this, got to the set-up screen (languages, accessibility) and an error ¨com.android.phone has stopped¨ spammed the screen. I tap ¨stop app¨ and the pop-up comes back immediately.
I tried to fix it by factory resetting (in the settings, NOT using the volume down/power button menu OR TWRP) and now I´m stuck in TWRP. Every time I try to reboot to System, it boots to TWRP now.
strapdad said:
Did this, got to the set-up screen (languages, accessibility) and an error ¨com.android.phone has stopped¨ spammed the screen. I tap ¨stop app¨ and the pop-up comes back immediately.
I tried to fix it by factory resetting (in the settings, NOT using the volume down/power button menu OR TWRP) and now I´m stuck in TWRP. Every time I try to reboot to System, it boots to TWRP now.
Click to expand...
Click to collapse
Power down, then boot to twrp using the volume buttons. Use the wipe menu there to do the reset.
Phoenix591 said:
Power down, then boot to twrp using the volume buttons. Use the wipe menu there to do the reset.
Click to expand...
Click to collapse
Wiped it, still get the com.android.phone errors.
Unfortunate, makes doing anything impossible with so many error popups.
strapdad said:
Wiped it, still get the com.android.phone errors.
Unfortunate, makes doing anything impossible with so many error popups.
Click to expand...
Click to collapse
Reflash your variant's official KDZ using [PARTITION DL] with patched LGUP leaving [aboot], [abootbak], [recovery], [recoverybak] partitions unchecked.
- Once the flash finishes & phone reboots, do a battery pull so phone doesn't fully boot (wiping recovery & encrypting data)
- Insert battery again
- While pressing volume down button - reinsert usb cable so it boots into fastboot mode.
- Follow dirtysanta guide for your variant from running step3.bat onwoards (which flashes TWRP back into your otherwise stock phone).
LS997, no official KDZ. Use VS995, but dump everything with LGUP (bar userdata) before hand
OK, so I did something stupid.
I have backups for my device I made by using dd. I decided to try to flash a recovery.img I put together. After flashing it, I erased the cache partition and rebooted it. The issue is, I can't get into fastboot because of it. If I try to access either recovery (holding volume up on boot) or factory mode (holding volume down on boot) it just tries to boot into android. However, android won't boot so it's just stuck on the nook loading logo. As well as that, whenever I hold the power button for a while to power it off, it just reboots. So I need a bit of advice. What should I do from this point? Should I let it die, or should I keep trying to get it to boot into either recovery or factory mode? Maybe I'm not hitting the buttons at the right timing.
Just have to say quickly, I did figure it out. The issue was that I had at some point in that process formatted the cache partition improperly, so Android couldn't boot. The solution was to leave it until it died and plug it in until it was charged up again, and then I was able to get into recovery first try after that (dunno the reasoning behind that, maybe it was continuously trying to reboot because of the fastboot reboot command). In recovery, I tried to reformat cache (which failed) and I turned it off, and then put it back in recovery. That time cache formatted properly and android was able to boot.
Thread closed as user figured it out on their own