I have a brand new Note 4 that had the power switch fail after one month.
T-Mobile has sent me a replacement, so I performed the factory reset data wipe on the old one. My next step was to use Odin to re-flash the stock firmware. I was previously running stock KitKat, but had used CF-auto-root.
After selecting the factory reset option from settings, it rebooted into recovery. One of the options is Wipe Data/ Factory Reset, but I can't select it because the power button doesn't work.
Taking the battery out just brings it back to the same place.
There is also a message "dm-verity verification failed" at the bottom of the screen.
The device is not enumerating on USB at all so I can't use ADB, fastboot, or Odin.
How can I escape recovery to complete the data wipe and get into download mode?
Related
A friend of mine with a Google Nexus 4 attempted to root on 4.4:
"The unlocking of the bootloader went without a hitch, and I downloaded the CWM non-touch from here:http://www.clockworkmod.com/rommanager, in the "Nexus 4" row, and "Download Recovery" column, named "6.0.4.3". I placed the file on the desktop, flashed it onto the phone, and booted into it using the volume keys and the power button to select "Recovery mode" on the bootloader screen. From there, I wanted to reboot the phone, so I clicked the first option, the "reboot system now" selection. I received the message "ROM may Flash stock recovery on boot. Fix? THIS CAN NOT BE UNDONE.", and not wanted to do anything to mess up the installation, clicked the "*****Go Back*****" option. And then I received another message saying, "Root access is missing. Root device? THIS CAN NOT BE UNDONE." Again, I clicked the "*****Go Back*****" option, not wanting to mess up the recovery. It suddenly booted into the stock ROM, showing the Google screen with a little unlock symbol at the bottom. Then it moved on to the Kit Kat boot sequence, the one with the 4 different colored circles and all that. I waited for it to boot back into the stock ROM, but it stayed on that screen, a bootloop. I then proceeded to hold the power button to turn it off. I booted it again, and it bootlooped again. So I went back to CWM and wiped the data/factory reset, wiped the cache partition, and went into advanced and wiped the dalvik cache. Then I rebooted it once more, and it bootlooped once again. So now I've turned it off, and am attempting to find a solution to fix this. As a last resort, I can always unroot it and wipe the data again. But I would prefer to not to have to re-unlock and re-flash the phone, unless there is no other option. During this entire period, the phone was connected by USB cable to the computer, up until I wiped the data and caches, where I unplugged it, and allowed it to boot."
*****So overall, after installing CWM, the phone was put into a bootloop. factory reset was done, as well as wiped cache partition and dalvik cache*****
is there a way to get the device rooted, without using the traditional unroot method? I feel as if the error (if any) was simple, therefore there should be a simple solution. Thanks!
Hello All,
Hope you guys are doing well. I'll write in jot notes so I don't end up with an essay.
Bought Nexus 4 16GB in February 2013 from Google Store and have been running stock software since. Never had issues.
Updated from latest Kit Kat OS to Android 5.0.1 OTA yesterday and it installed fine.
Then tried updating to Android 5.1 (also through OTA) right after and encountered the "Error" message with the Android logo on its back during install. Phone is now unable to move past the swirling, coloured balls animation upon rebooting (referred to as a bootloop?).
Based on some websites' recommendations, I went into the recovery mode (hold Power+Volume Down and select from list) and wiped the cache partition (hold Power+Volume Up and select from list), which took a second. Wiped cache several times.
Tried rebooting the system after but I still get stuck on the swirling balls animation.
I'd be fine with using 5.0.1 or even going back to the latest Kit Kat as long as I can actually get my phone working again and not have to factory reset everything through the recovery mode (which, at this point, seems like my only option).
Thanks.
Check my thread, I had the same problem. 5.0.1 was fine but sensors went kaput, yes all of them. Flashed factory image 5.1, endless boot screen. After a day or two of flashing 4.4.4 (sensors were back working okay, wow big surprise), tried flashing 5.1.1 pure stock, same.
I'm back to 4.4.4 after restoring apps and data. Not sure I want to use 5.0.1 due to hte memory leak and other bugs that should be fixed with 5.1. But I'm certain that the factory image of 5.1.x won't boot on the N4.
For your problem, download the factory image, then edit flash-all.bat/sh and remove the -w from the last flash command (-w rewrites /userdata partition). Whether you use 5.0.1 or 4.4.4 is up to you.
PermissionToPanic said:
Hello All,
Hope you guys are doing well. I'll write in jot notes so I don't end up with an essay.
Bought Nexus 4 16GB in February 2013 from Google Store and have been running stock software since. Never had issues.
Updated from latest Kit Kat OS to Android 5.0.1 OTA yesterday and it installed fine.
Then tried updating to Android 5.1 (also through OTA) right after and encountered the "Error" message with the Android logo on its back during install. Phone is now unable to move past the swirling, coloured balls animation upon rebooting (referred to as a bootloop?).
Based on some websites' recommendations, I went into the recovery mode (hold Power+Volume Down and select from list) and wiped the cache partition (hold Power+Volume Up and select from list), which took a second. Wiped cache several times.
Tried rebooting the system after but I still get stuck on the swirling balls animation.
I'd be fine with using 5.0.1 or even going back to the latest Kit Kat as long as I can actually get my phone working again and not have to factory reset everything through the recovery mode (which, at this point, seems like my only option).
Thanks.
Click to expand...
Click to collapse
Try doing this
Let's be clear about how to wipe cache, you can't do it in the bootloader.
Power off
Hold Power and VOL DOWN => bootloader
VOL to select Recovery
Power to enter Recovery.
In stock Recovery "fallen Android" icon, hold POWER and VOL UP => Recovery menu
Now use vol and power buttons to select Wipe cache partition.
My final attempt after doing factory reset/wipe data in stock recovery, using the factory image flash-all.bat and NOT removing the -w switch (so /userdata/ is overwritten as well), the N4 didn't boot after waiting > 30 minutes.
Hope that helps
PermissionToPanic said:
Hello All,
Hope you guys are doing well. I'll write in jot notes so I don't end up with an essay.
Bought Nexus 4 16GB in February 2013 from Google Store and have been running stock software since. Never had issues.
Updated from latest Kit Kat OS to Android 5.0.1 OTA yesterday and it installed fine.
Then tried updating to Android 5.1 (also through OTA) right after and encountered the "Error" message with the Android logo on its back during install. Phone is now unable to move past the swirling, coloured balls animation upon rebooting (referred to as a bootloop?).
Based on some websites' recommendations, I went into the recovery mode (hold Power+Volume Down and select from list) and wiped the cache partition (hold Power+Volume Up and select from list), which took a second. Wiped cache several times.
Tried rebooting the system after but I still get stuck on the swirling balls animation.
I'd be fine with using 5.0.1 or even going back to the latest Kit Kat as long as I can actually get my phone working again and not have to factory reset everything through the recovery mode (which, at this point, seems like my only option).
Thanks.
Click to expand...
Click to collapse
I don't think that the factory reset will solve the problem. Have you tried waiting for 10-15 minutes for the phone to boot up? After OTA's and clearing cache the phone usually takes a while to boot up. If that doesn't work, factory reset using a custom recovery (this will delete your /data folder but not /data/media so your internal storage won't be wiped)
Blacksmith5 said:
.. Let's be clear about how to wipe cache, you can't do it in the bootloader.
Power off
Hold Power and VOL DOWN => bootloader
VOL to select Recovery
Power to enter Recovery.
In stock Recovery "fallen Android" icon, hold POWER and VOL UP => Recovery menu
Now use vol and power buttons to select Wipe cache partition.
My final attempt after doing factory reset/wipe data in stock recovery, using the factory image flash-all.bat and NOT removing the -w switch (so /userdata/ is overwritten as well), the N4 didn't boot after waiting > 30 minutes.
Click to expand...
Click to collapse
My, that text looks familiar....
Bought an Australian model galaxy S4 off ebay which was stuck at Samsung Logo with a hope I can unbrick it.
I have tried to flash with an official firmware twice. ODIN confirmed flashing Passed. But the phone still could not boot pass Samsung logo with model number.
+ Pressed volume up + Home + power button to enter into recovery mode but the phone still stuck at recovery mode with blue text "recovery booting ". Have tried to take battery out and redo few times. . All I can do is go to download mode to flash official firmware again. However I do not want to mess thing up as I have tried twice without success.
Please help me out if you have any idea how to fix it. I am much appreciate.
I am not sure if it will help or not but you can try flashing TWRP via Odin and then boot into that one (maybe recovery is corrupted as well?)
Clear cache / dalvik cache from TWRP and try booting to system again
magnavn76 said:
Bought an Australian model galaxy S4 off ebay which was stuck at Samsung Logo with a hope I can unbrick it.
I have tried to flash with an official firmware twice. ODIN confirmed flashing Passed. But the phone still could not boot pass Samsung logo with model number.
+ Pressed volume up + Home + power button to enter into recovery mode but the phone still stuck at recovery mode with blue text "recovery booting ". Have tried to take battery out and redo few times. . All I can do is go to download mode to flash official firmware again. However I do not want to mess thing up as I have tried twice without success.
Please help me out if you have any idea how to fix it. I am much appreciate.
Click to expand...
Click to collapse
Good idea of @th3cr0w.
I will add: It's important know what firmware had before you start to flash things. I supose you don't know it. What you can do is:
1. Flash TWRP recovery in DOWNLOAD MODE via ODIN unticking "Auto reboot". Take out the battery when the process finish. Wait 30 sec. and push it in again.
2. Boot in TWRP and wipe all (Wipe -> Advanced Wipe -> Select system, data, cache and dalvik cache).
3. Reboot in DOWNLOAD MODE and now yes, flash the firmware you wish via ODIN normally.
Same happens with my Galaxy s3 while ago, Problem was the EMMC chip was corrupted, And the problem was solved after replacing it from a local shop.
Joku1981 said:
Good idea of @th3cr0w.
I will add: It's important know what firmware had before you start to flash things. I supose you don't know it. What you can do is:
1. Flash TWRP recovery in DOWNLOAD MODE via ODIN unticking "Auto reboot". Take out the battery when the process finish. Wait 30 sec. and push it in again.
2. Boot in TWRP and wipe all (Wipe -> Advanced Wipe -> Select system, data, cache and dalvik cache).
3. Reboot in DOWNLOAD MODE and now yes, flash the firmware you wish via ODIN normally.
Click to expand...
Click to collapse
Thanks for your and TH3cr0w's suggestion. I will try it tonight and let you guys know. Hope I will fix it. A quick question before I do, once I install TWRP it is anyway I can remove it and reinstall official receovery?
I am using this firmware:
PDA I9505XXUGNH6
CSC I9505XSAGNH1
i have tried to install TWRP with this file twrp-2.8.6.0-jfltexx.tar 9.9M. However my phone still stuck and can not boot into recovery. up the top of screen i have following messages:
Recovery booting...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Have i done anything wrong? Thanks
What you're seeing is normal, but recovery not installing isn't. I know you don't want to try it again, but flash your stock ROM through Odin. Do it this time with the following changes:
Add a PIT file (easily found on the forum).
Make sure "Re-partition" is selected.
The combination of the PIT file and the re-partition function should wipe the S4's internal storage and partition it properly. If there is no physical damage to the internal storage you should then be able to boot into the device. Otherwise you may have no choice but to have this beast repaired.
Out of the box, remote paired, went straight to update to version 5.1.1, but the cable on my power strip must have come loose during the update and now im stuck at the Google screen.
Ive pressed and held down the bluetooth button on the bottom of the player and got into recovery mode. When it gets to the "No command" portion, I press and hold again to get the options to factory reset the device, but this does not fix the problem and the Nexus Player boots right back to the Google screen. So I wipe the cache, then factory reset, but that fails to work too.
I have OTG USB adapters, is there a way I can copy a stock image to a flash drive and restore the system?
Is there an app that I can install to help restore via USB cable?
Ive read alot of threads, but almost all of them have to do with rooting or flashing to Lollirock, so I dont have any dev tools installed and have only had limited success in using ADB in the past. What am I missing?
SOLUTION!
Got a factory image and unziped it into a folder with fastboot and adb.
https://developers.google.com/android/nexus/images
Followed the steps, but it kept failing. What was I doing wrong?
Well I was using a OTG USB adapter, when I should have been using a normal MicroUSB to USB cable.
Also, I was in the wrong boot mode.
There appears to be two types of recovery mode in which my Nexus Player is detected in Windows/DeviceManager. One is where you press and hold the lone button under the player and apply power, letting go a few seconds into the Google logo. In this initial recovery menu, I have the options to boot normally, boot into recovery, or restart the recovery menu, well I should have stayed there and ran the flash-all script, because when I did do this, it failed initially. Trying a 2nd time worked in restoring my Nexus Player.
The second recovery mode is, from the initial recovery menu, you option to boot into recovery, get the no command error, then pressing and holding the lone button to boot into a menu where you had the option of factory resetting, wipe cache, reboot and apply update from adb. Applying the update from adb allowed my device to get detected in Windows/DeviceManager, but the flash-all script failed. Then tried the sideload command to send a recovery image zip file to the player, but the file transfer would fail about half way through each time. Nexus player would report install aborted.
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