Database Users

Wiped system in Terminal Emulator and now Iconia Tab won't boot

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

OP2 soft bricked, can't access recovery, not recognized by laptop

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.

Phone is (soft?) bricked.

My phone is a6000 plus variant and was running on CM 12.1 update 19 prior to getting bricked. I have flashed the same ROM before, however, this time I ended up flashing it twice-the second flash without clearing cache, data and the like and on top of the same ROM.
The problem is that the phone is not booting into recovery (just showing the lenovo logo).
It is however booting into fast boot mode. (Hold power key for reboot).
Now, I would just use adb to flash the phone but with cyanogenmod 12.1 with no update, the device is not showing in adb. (The USB worked fine before this, however I had USB connected during flashing and noticed that CM 12.1 with no update would not be detected on my PC.)
The phone is alive and well just not being detected in adb. Every time I connect the device to my PC via USB, the drivers install but fail.
I tried updating the drivers with device manager but error 10 is showing.
If I remove the battery the phone shuts down, until I power it up again, which results in the lenovo android logo on the screen.
What are my options in such a case?

Timeline of events:
I boot my phone into twrp with adb and flash CM 12.1 no update.
I see that the PC adb is not working and drivers fail to install.
I boot the phone into recovery using advanced recovery and notice that in twrp recovery the adb devices detect my phone.
I flash a queue of CM 12.1, update 20 and super user zip.
I recall that I had forgotten to clear data, cache and the like and end up dirty flashing.
I reboot the phone thinking it will fix it but the device just boots up the android and lenovo logo.
Furthermore, the device is not being detected in adb and drivers fail to install.

AsCi1 said:
I boot my phone into twrp with adb and flash CM 12.1 no update.
I see that the PC adb is not working and drivers fail to install.
I boot the phone into recovery using advanced recovery and notice that in twrp recovery the adb devices detect my phone.
I flash a queue of CM 12.1, update 20 and super user zip.
I recall that I had forgotten to clear data, cache and the like and end up dirty flashing.
I reboot the phone thinking it will fix it but the device just boots up the android and lenovo logo.
Furthermore, the device is not being detected in adb and drivers fail to install.
Click to expand...
Click to collapse
First of all remove your sd card and use a sd card reader or put it in another phone.
Then on the other phone/PC download a stock CM12 or 13 ROM and Gapps.
Save the ROM on the sd card.
Put the sd card on your phone and go to recovery
Wipe everything except SD CARD and then flast the ROM and GApps

[HELP] Moto g5 Plus doesn't install any rom, including a stock rom, what can I do?

Hi, guys
My Moto G5 plus keeps in a bootloop, i think. Recently i tried to install a TWRP, i got it, but, when i start, came across a screen written "no command', i tried to install all stock roms, but always returned to "no command" screen.
I even tried to install a custom rom,but my OTG cable not recognizes, i tried move to internal storage and i can't move it, i tried whith sd card too, recognize the file, but not install too
I can access the recovery mode, but something seems to have happened to the internal storage
What can I do?
Thanks in advance,
Diogo

DiogoSJ12 said:
Hi, guys
My Moto G5 plus keeps in a bootloop, i think. Recently i tried to install a TWRP, i got it, but, when i start, came across a screen written "no command', i tried to install all stock roms, but always returned to "no command" screen.
I even tried to install a custom rom,but my OTG cable not recognizes, i tried move to internal storage and i can't move it, i tried whith sd card too, recognize the file, but not install too
I can access the recovery mode, but something seems to have happened to the internal storage
What can I do?
Thanks in advance,
Diogo
Click to expand...
Click to collapse
The no command screen is the stock recovery. You need to press and hold power and volume down to access the options. And you cannot flash twrp unless you have your bootloader unlocked.
Incase you were on stock and flashed twrp and then rebooted without flashing verity and decrypt then you just need to flash twrp again via fastboot.

Phone bricked after installing LinageOS 17.1 - System UI Crashing

Hi,
Today I tried to install LinageOS 17.1 on my Huawei P10 lite (at start, still completely Stock Rom).
Unlocked bootloader following procedure in https://forum.xda-developers.com/p10-lite/how-to/p10-lite-bootloader-unlock-june-2020-t4113315, worked great.
Installed TWRP following https://forum.xda-developers.com/p10-lite/development/recovery-twrp-huawei-p10-lite-t3953890 ; also here, no problem.
Then I tried installing LinageOS following this thread https://forum.xda-developers.com/p10-lite/development/rom-lineageos-17-1-huawei-p10-lite-t4064115 . Here I ended up with the Linage OS System UI that constantly crashes, restarts, crashes again etc.
This problem is mentioned in the same thread but none of the solutions seems to work for me.
I tried to downgrade the TWRP to the older 3.3.1 and then redo the entire installation procedure => No success
Then I tried wiping and formatting all the caches/data that was mentioned during the thread + re-executing the entire installation procedure => Still no success.
Can anyone help me?
What could also be relevant:
In TWRP I cannot seem to copy data to the device, whenever I try to do that via the File Manager (I am using Linux Mint 20) I can see the device and its internal storage but transferring data is horribly slow (it would take 5 hours 45 minutes to transfer a 3 MB file) or just fail. I also tried this in a (virtualized) Windows 10 installation with the same results.
When earlier today (before having installed LinageOS) I tried to transfer files, it worked very well. Also, I tried it with multiple USB cables just in case it might have been a faulty cable.
Pushing a file via adb push doesn't work as the device shows up as "unauthorized". The installation of the patches (magisk, los_patches_warsaw, opengapps etc.) I did using ADB Sideload which seemed to work nicely as well - really making me thing that the USB transfer issue is not hardware-related...
Furthermore, I know this is a noob question but anyway: the procedure says "flash los_patches_warsaw.zip". How exactly should this be done? Copying the file to the internal storage from a PC (which I cannot do, see above) and installing it via TWRP Install? Flash via Fastboot (to what destination)?
Tx in advance!

I've had this issue as well, what I did was disabled dm-verity and forceencrypt using https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 after flashing system in fastboot and then I flashed los_patches_warsaw.zip from SD Card (MTP is broken in older twrp, use 3.4.0, also try this at your own risk).

Thanks. I solved it in another way meanwhile.
I reinstalled the stock recovery (which I was able to do by choosing the E-Recovery option in the "your device's bootloader has been unlocked" screen after startup. It reinstalled the stock recovery and ROM.
After that I installed the image from OpenKirin (it didn't need TWRP - even more, only the stock recovery is supported if using OpenKirin), and then it worked like a charm.
Just one thing, I cannot find how to update the OpenKirin installation except for flashing it via Fastboot (no option to auto-update). I wonder if it is even possible?

Bart80TR said:
Thanks. I solved it in another way meanwhile.
I reinstalled the stock recovery (which I was able to do by choosing the E-Recovery option in the "your device's bootloader has been unlocked" screen after startup. It reinstalled the stock recovery and ROM.
After that I installed the image from OpenKirin (it didn't need TWRP - even more, only the stock recovery is supported if using OpenKirin), and then it worked like a charm.
Just one thing, I cannot find how to update the OpenKirin installation except for flashing it via Fastboot (no option to auto-update). I wonder if it is even possible?
Click to expand...
Click to collapse
I think it's only possible by dirty flashing it, also a little correction for my last post, I meant internal storage not micro SD card.

it's a shame the original LOS 17.1 thread is closed.
My experience with WAS-AL00 (china version) on macOS:
After I flash LOS 17.1 ROM, "fastboot reboot recovery" doesn't reboot the device into recovery. Then I unplug the phone, and reboot into system, I came across system UI crashing constantly. After managing to get through to the main screen. Plug the phone, "adb reboot recovery", then flash los_patches_warsaw from microsd card (you need to copy the file to a microsd card and insert it into the phone). Then reboot system, this time the screen is black. only long press power button show three options "power off", "restart", and another one i don't remember. @KinteLiX 's method didn't work for me.
Then I tried stock recovery with openKirin (worked), Twrp 3.4.0.0 with openKirin (also worked, even though they state that only stock recovery works with their ROMs).
Last I tried twrp 3.4.0.0 with AOSP 10 from @DarkJoker360. It works.
Note: after flash the ROM, power off the phone, and long press three buttons volume up, volume down and power at the same time, and you will boot into twrp. If it shows update fail, then reboot and try to get into erecovery and wipe data/factory reset and then power off, long press three buttons simultaneously and you will be able to boot into twrp, if not, wipe data/factory reset again in erecovery (I accidentally found out about this. before this I was unable to boot into twrp after flashing any ROM, "fastboot reboot recovery" doesn't work). then do as the thread shows.
update: making a call doesn't work with AOSP 10 on my device.

The system crashing should come from the integratet AOD overlay....there should be a solution to solve that issue but i didnt rember the correct way how to. Just search in the p10 lite forum here on XDA.