After I rooted my A500, I wanted a clean slate to work with, but when I tried factory resetting, everything stayed exactly the same as if the factory reset wouldn't complete. I tried wiping through ROM manager as well again with no results. I went into terminal emulator and gained superuser permissions, then typed in 'wipe' and it gave me the option to wipe the system or something else. Long story short, I typed in to wipe the system and everything went to hell. I got force close notifications one right after the other, my tablet popups starting coming up in different languages, and then the tablet shut off. When I went to reboot it, it stopped at the Acer logo screen. I had CWM recovery installed or so I thought (I had it installed through ROM manager but I can't boot into recovery or anything now). When I boot with the power button and Vol- it says:
Erasing Cache before SD update...
SD update cmd: recovery
--update_package=SDCARD: update.zip
Booting recovery kernal image
Recovery verified failed...
I've tried booting with the power button and Vol+ and flipping the rotation lock and after clearing the Userdata and Cache and rebooting, it sticks on the logo screen. I've read countless forums both here and elsewhere about downloading an update.zip to the SD card and letting the update run its course but nothing happens. I have no recovery access, no fastboot access, no CPUID, no nandroid backup, and no way to push files to the tab except through the external SD card.
The computer will recognize the device as an MTP device when plugged in via USB, but the drivers won't install. I've manually installed drivers from the Acer website and multiple third parties with no luck.
I really have no other ideas so I thought I'd come to you guys. Literally any help whatsoever would be appreciated so thanks in advance
Related
Hey
Today I was on Team Win Recovery Project v2.21 and I wanted to flash a new mod in however half way, I accidentally click on reboot now.
I already - Factory reset my device
- Wiped Dalvik Cache Directories
then tried to flash in one of my rom i was flashing in but I got an error then clear dalvik cache directories again. After I tried to reflash my rom but it failed again.After this I accidentally reboot my device and now it is stuck on a screen with "Reboot.." as the title. I can not restart the my nexus 7, touch any keys given (home and back). When I press/hold power, it comes up with a look.
I am wondering if there any way to fix this problem
Maybe try this...
http://forum.xda-developers.com/showthread.php?t=1781250
Or use this program...
http://forum.xda-developers.com/showthread.php?t=1766475
Lockable said:
Hey
Today I was on Team Win Recovery Project v2.21 and I wanted to flash a new mod in however half way, I accidentally click on reboot now.
I already - Factory reset my device
- Wiped Dalvik Cache Directories
then tried to flash in one of my rom i was flashing in but I got an error then clear dalvik cache directories again. After I tried to reflash my rom but it failed again.After this I accidentally reboot my device and now it is stuck on a screen with "Reboot.." as the title. I can not restart the my nexus 7, touch any keys given (home and back). When I press/hold power, it comes up with a look.
I am wondering if there any way to fix this problem
Click to expand...
Click to collapse
Reboot into bootloader (hold power to turn off, as soon as it does hold vol down)
Install the android sdk if you haven't. Download a recovery image from clockworkmod.com, put the image in your /platform-tools folder. Open a command Window there
Fastboot flash recovery xxxx.img
Fastboot boot xxxx.img
Dl a rom
Put it in your platofrm-tools folder
Adb push romxxx.zip /sdcard/Download
Flash the ROM in recovery
Reboot
Sent from my Google Nexus 7 using Tapatalk 2
When I turn on my tablet now, it automatically open up ClockworkMod Recovery. I am able to properly install a rom (wipe all data then install rom from sd) but when i reboot my device it goes back into clockwordmod recovery. Any idea how to bypass automatically booting straight into recovery mood and booting into flashboot?
EDIT
i am unable to push new roms in
mis-post, my bad.
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!
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.
Hi,
I had CM12 installed on my Mojo - but wifi kept dropping out so I decided I wanted to flash the stock rom as discussed in these threads. I wiped everything except the external sd card which had the stock zip on it (data, internal, dalvick etc)
I tried to flash the stock rom and nothing happened past the MD5 message (it was stuck on the flash) - so I pulled out the power cable and now when I try and reboot the Mojo I get nothing but a black screen. I've tried connecting with USB 2.0, but adb does not pick up any device (on adb devices command). Any hope for a recovery of this one??
I've managed to get into the boot screen but I get a simple message saying "....driver not found.. Booting OS" and it's permanently stuck on this message
TWRP is there but where??
Msr Blobby said:
Hi,
I had CM12 installed on my Mojo - but wifi kept dropping out so I decided I wanted to flash the stock rom as discussed in these threads. I wiped everything except the external sd card which had the stock zip on it (data, internal, dalvick etc)
I tried to flash the stock rom and nothing happened past the MD5 message (it was stuck on the flash) - so I pulled out the power cable and now when I try and reboot the Mojo I get nothing but a black screen. I've tried connecting with USB 2.0, but adb does not pick up any device (on adb devices command). Any hope for a recovery of this one??
Click to expand...
Click to collapse
I can't seem to get it to boot into TWRP - even though I know it is on there, as it was there after I did the wipe!
Hey,
Very strange query but here goes. Rooted phone a while back and installed CM13 along with recovery. Was trying to update TWRP{ by downloading .img from their website, went to flashing, selected the file and hit recovery. Said it was succesful so attempted to reboot. Plugged in to charge and was charging but when I tried to switch it on, it was stuck in Cyanogen Bootloop (blue alien stayed on the screen for 10+ minutes). Tried rebooting to recovery by hitting power + volume down and instead of booting to TWRP, it takes me to a Cyanogen recovery screen where I see the following options:
Cyanogen Recovery.
- Reboot system now
- Apply update
- - -apply from ADB
- - -choose from emulated
- Factory reset
- - -system reset
- - -full factory reset
- - -wipe cache
- Advanced
- - -reboot recovery
- - -reboot to bootloader
- - -Wipe system partition
- - -view recovery logs
Here's what I tried as troubleshooting. Tried to do a system reset, factory reset and wiped cache and tried to restart my phone but no luck. Still stuck in boot loop with CM logo. Tried to reboot to bootloader but the screen is stuck with the 1+ logo for about 5 mins so gave up on that.
Basically, right now I can't access anything on the phone, can't find any way to reinstall a ROM and when I plug it into my Macbook, it is not recognised. So I'm screwed sideways. I had TWRP recovery set up so I have no clue how this happened but can anyone please help me with this.
If data isn't at risk try the Qualcomm recovery tool one the oneplus forum it's by nammand bhal (definitely butchered the name) but all data is lost and resets the phone to out of box conditions locked bootloader and Oos 2.2.1 so this is often a last measure (tool is Windows but may have Mac variant and the file is quite big)
My suggestion is to try to boot to bootloader again and flash TWRP
hmm mac book I don't have much experience with those
If you have a Windows pc you can use adb or on Mac if it has it. Also when it come to being found by a computer in recovery it should but again don't have a mac
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
AJay27 said:
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
Click to expand...
Click to collapse
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
justicesourglide said:
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
Click to expand...
Click to collapse
Actually I don't think the issue was with the Macbook since I have unlocked, flashed custom recoveries and sideloaded ROMs on several devices including OP2, OP3, Nexus 5, etc on mine. It might have been some accidental flashing error, which unfortunately ended up bricking your device.