[Q] Help my a701 softbrick, cannot enter adb or fastboot - Acer Iconia A700 and A510

i have unlock root, and install cmw with my a701. first i tried CyanogenMod, after that Evil Purgatory ROM...
after that i tried to back to stock rom. after several day struggling in "assert failed: getprop("ro.product.device")", finally i can pass the error...
but after i run the update.zip, they ask me about flash recovery (i answer yes), and rood device (i answer no), after reboot, the device stuck in iconia tab logo, (after acer, animation, then iconia tab logo). after the i tried to run the recovery, but it always stuck in "recovery verified failed..."
i have no idea how to enter fastboot or adb.
there's nothing i can do to the device right now...
any idea how to enter fastboot or adb, or fix my a701?
please help me, i already search all around xda, cannot find the solution, every solution need to enter adb mode or fastboot mode...

I have the exact same problem now. Has anyone found a solution to this?
Many thanks
EDIT: FIXED! For anyone experiencing a similar problem, I managed to recover mine by powering on, holding Volume + (one dot) and repeatedly switching the rotation lock switch. This gave the messaging wiping user data, and wiping cache, and it rebooted as it should! Good luck.

Related

[Q] Problem After Rooting

Hi All -
I finally broke down and rooted my US wifi Xoom, but I've run into a problem. I followed the instructions for installing the custom recovery and that went fine. I then installed the 'update_US-Xoom-WiFi-3.2.1-HTK75D_stachre_v02.zip' per the instructions.
When I rebooted, the Xoom was stuck in the honeycomb boot animation. I manually rebooted using the vol up / power button and, upon reboot, I got the green "enter your password" screen that I'd normally see after encrypting my device (I didn't encrypt it).
Now, I'm stuck there - I tried reflashing the recovery and the ROM, did a factory reset, etc and I get the same thing. I can't format or mount the 'data' folder in recovery - I suspect that's where the problem is.
Anyone have any suggestions? Thanks!
<UPDATE> Disregard - a quick 'fastboot oem unlock' solved the problem.

[Q] Stuck in bootloop, recover files

Hello.
Today my oneplus one was suddenly stuck in bootloop. This happened in the middle of the day when I rebooted my phone. My phone was running the latest update that came OTA (stock lollipop). Whenever I boot my phone it starts loading and suddenly a Chrome (browser) window appears for 1 second and tries to load a website. Afterwards my lock screen pop ups for 1 seconds and it starts to reboot. During the lockscreen I tried to unlock my phone as soon as possible, but it just reboots. (Any ideas about this weird problem?)
I CAN boot it in recovery mode by holding volume-down button and power button.
I CAN boot it in fastboot mode by holding volume-up button and power button.
Perhaps a factory reset will do the trick, but I don't have a backup of my files (because this happened so suddenly without me trying to flash/customize my phone). My first priority is recovering my files, because most solutions will end up in me losing every file. Unfortunately I've found little possibility to do this during the bootloop problem. I've tried to flash TWRP because it could make backups of my phone. I tried it through ADB/Fastboot, but it failed because my device is not unlocked (I can't go to settings and put my phone in developer mode and debugging mode). So I've read somewhere that unlocking my phone (bootloader?) through ADB will wipe my phone, which is exactly what I don't want.
Also I've tried this: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
But It also failed because my device was not unlocked.
Did I miss some steps somewhere or did I read something wrong?
Hopefully anybody has an idea to either fix the bootloop without losing my data, or finding a way to recover my files before wiping the phone.
Thank you.
RightHanded said:
Hello.
Today my oneplus one was suddenly stuck in bootloop. This happened in the middle of the day when I rebooted my phone. My phone was running the latest update that came OTA (stock lollipop). Whenever I boot my phone it starts loading and suddenly a Chrome (browser) window appears for 1 second and tries to load a website. Afterwards my lock screen pop ups for 1 seconds and it starts to reboot. During the lockscreen I tried to unlock my phone as soon as possible, but it just reboots. (Any ideas about this weird problem?)
I CAN boot it in recovery mode by holding volume-down button and power button.
I CAN boot it in fastboot mode by holding volume-up button and power button.
Perhaps a factory reset will do the trick, but I don't have a backup of my files (because this happened so suddenly without me trying to flash/customize my phone). My first priority is recovering my files, because most solutions will end up in me losing every file. Unfortunately I've found little possibility to do this during the bootloop problem. I've tried to flash TWRP because it could make backups of my phone. I tried it through ADB/Fastboot, but it failed because my device is not unlocked (I can't go to settings and put my phone in developer mode and debugging mode). So I've read somewhere that unlocking my phone (bootloader?) through ADB will wipe my phone, which is exactly what I don't want.
Also I've tried this: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
But It also failed because my device was not unlocked.
Did I miss some steps somewhere or did I read something wrong?
Hopefully anybody has an idea to either fix the bootloop without losing my data, or finding a way to recover my files before wiping the phone.
Thank you.
Click to expand...
Click to collapse
Unfortunately you might be stuck in a catch-22 situation here. In order to access the files you'd need to unlock the bootloader, but in doing so you'd lose those files. Without usb debugging already enabled I can't see a way out of this.
Decided to unlock the bootloader through ADB. (bye bye data)
After I've unlocked it, I've tried installing TWRP.
Some minor problems occured but I can finally boot into TWRP through volume-down button + power button.
I've decided to download the stock ROM i've found on the OPO forums.
Couldn't acces my phone through normal methods, so I had to use ADB to push the files into my phone.
Installing the file through TWRP, wiped cache/dalvik and installed super user before rebooting.
After rebooting my phone is stuck on the boot screen now. (This also happened before I installed TWRP on my phone)
I've also tried this method: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Also no succes. I'm stuck in the bootscreen where it says 'cyanogen'.
EDIT: Managed to fix it eventually through: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061 (part 2) writing the command in TWRP.
Phone finally boots normally again.
RightHanded said:
Decided to unlock the bootloader through ADB. (bye bye data)
After I've unlocked it, I've tried installing TWRP.
Some minor problems occured but I can finally boot into TWRP through volume-down button + power button.
I've decided to download the stock ROM i've found on the OPO forums.
Couldn't acces my phone through normal methods, so I had to use ADB to push the files into my phone.
Installing the file through TWRP, wiped cache/dalvik and installed super user before rebooting.
After rebooting my phone is stuck on the boot screen now. (This also happened before I installed TWRP on my phone)
I've also tried this method: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Also no succes. I'm stuck in the bootscreen where it says 'cyanogen'.
Any other way to fix this problem?
Click to expand...
Click to collapse
Exactly what did you flash? Full filename please. No errors occurred?
Heisenberg said:
Exactly what did you flash? Full filename please. No errors occurred?
Click to expand...
Click to collapse
Hopefully the stock cyanogen OS.
First I've tried to flash cyanogenmod 12 through TWRP (file is found here: https://forums.oneplus.net/threads/cm12s-yng1tas17l-installation-guide-review-change-log.304615/)
Afterwards I was still stuck in bootscreen, so I've looked for another solution.
Which made me find this guide: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
After flashing this file (probably the same thing) the problem still remained.
Eventually after multiple wipes/factory resets (which did not solve the problem) I've entered the command in TWRP and after reboot it finally worked again.
So I basically flashed my phone twice, once through TWRPS and the other through the batch file (perhaps ADB?).
Also no errors occured which stopped the flashing and commands. Did have to reinstall TWRP and reboot instantly in it by holding the volume down button multiple times. This doesnt happen anymore though.
Only had to install google apps for CM12 (gapps), for which I used TWRP in recovery mode.
Currently reinstalling most apps on my phone and no problems yet.

[Completed] [GT-N7000] Stuck in manufacturer Logo, unable to enter recovery can enter download.

Is my device soft bricked?
I flashed PhilZ-cwm6-XXLTA-ATL-5.15.0.tar which worked, then I started up the phone and tried to flash CWM 6.0.4.3 touch using ROMManager, the process was a "success" but after the reboot attempt the phone was unable to boot OS nor is it able to go to Recovery mod. I am still able to enter download mod.
I tried flashing PhilZ-cwm6-XXLTA-ATL-5.15.0.tar again, but it didn't work. I can detect my phone in ADB devices and in Odin3. I am currently searching for a stock ROM for my device.
If anyone has experienced this before and knows the result already, could you tell me whether my device is lost or I can revive it somehow? Thanks in advance.
EDIT: My phone doesn't seem to go into recovery, stuck at manufacturer Logo(Not restarting); but in ADB devices I can see it in recovery mod and can see its contents in adb devices.
Solved: It booted normally after deleting update.img and cache via ADB.
Thread completed as user already founded the solution.
Thread closed

Bootloop on TWRP

Hello guys
I have a big problem with my TF700t. I have looking similar topics and answers for my problem but didn't find.
Around month ago I wanted to flash new ROM and then in TWRP I ve got "Unable to mount cache". I tryied to make format data but it didn't help. But now I can not event get into bootloader. My device is starting from bootloop on TWRP ( to be specific on flash screen) and stays at it. I can not get into TWRP in any way. Even after battery was down and recharing it - still the same. Also I am not even able to turn device off. But It is recognized in computer but adb not see TF700.
And I am or I was on TWRP 2.8.0.1
Can You have any idea what I could do to fix it ?
Thank You in advance
maciumpek said:
Hello guys
I have a big problem with my TF700t. I have looking similar topics and answers for my problem but didn't find.
Around month ago I wanted to flash new ROM and then in TWRP I ve got "Unable to mount cache". I tryied to make format data but it didn't help. But now I can not event get into bootloader. My device is starting from bootloop on TWRP ( to be specific on flash screen) and stays at it. I can not get into TWRP in any way. Even after battery was down and recharing it - still the same. Also I am not even able to turn device off. But It is recognized in computer but adb not see TF700.
And I am or I was on TWRP 2.8.0.1
Can You have any idea what I could do to fix it ?
Thank You in advance
Click to expand...
Click to collapse
You have to kick your tablet back into the bootloader and you best bet for that is to use bootit.ko that we have thanks to _that.
Follow this: http://forum.xda-developers.com/transformer-tf300t/help/guide-t2854495
Yes, that's a guide for the TF300 but this works just fine on the 700 too.
After you are back in the bootloader it's up to you if you follow lj's guide and fastboot flash the Asus stock blob and start from scratch or reflash your recovery and use that to format your cache and data partitions.
If you decide to flash the stock blob you'll have to get the latest firmware for your SKU from here: https://www.asus.com/support/Download/28/1/0/11/fq2B3oq64av1O95u/8/
But you should be able to fix it without that once you have a working recovery and fastboot again.
Hi,
I have similar problem. My Tablet Stuck on blinking TWRP. When i power on my tablet, after asus logo it goes to " 4 Penguins images" then Twrp tlinking "TEAMWIN" logo.
Power + Volume Down buttons do not work. My problem is that my Asus TF700t could not be detected by PC, I have tried on several laptops with windows and linux, i`ve also tried two cables, but nothing - thread: http://forum.xda-developers.com/transformer-tf300t/help/guide-t2854495/page8 is not helping me. Any ideas?

Device stuck in boot loop with no access to twrp or usb debugging

Hello everyone, I was wondering if anyone might be able to provide some assistance to help me solve my problem here. Basically I was attempting to flash havoc os to my oneplus 7 pro and I think I wiped both the a/b partitions by accident as now it’s stuck in boot loop.
basically it will constantly boot loop where it goes to the unlocked boot loader warning and then reboots. If I attempt to boot to recovery, it will flash with the twrp screen for 1-2 seconds and then reboot. Will boot to fast boot mode but cannot enable usb debugging.. any help would be greatly appreciated, and If anyone needs me to clarify anything I will do my best but its been a week or two since it happened and I can’t seem to find a working solution anywhere. Thank you.
I know this is an older post, but as a thought, when you go to the fastboot menu, if you wait, does it reboot there too?
If so, I think this may be your power button acting up. I had that problem with my phone. I could boot to fastboot or recovery, but couldn't stay in them long enough to do anything. First time it happened, I took the phone apart and disconnected the power button and I was able to get it to boot up successfully. Next time it happened, I just hit the power button multiple times until it started booting up properly.
If this is not the case for you, I would try to fastboot boot the latest version of TWRP rather than from the recovery process (holding down buttons and hoping it boots). I've read that on some devices (with older versions of TWRP), it was recommended to fastboot TWRP rather than flash for better compatibility.

Categories

Resources