My father device suddenly decided to get stuck right after boot with the above error message.
I tried reboot into safe mode but got the same result.
I tried to connect it to my PC using abd(after installing drivers), but for some reason adb didn't recognize the device (fastboot however did find it).
Any ideas before doing hard reset?!
Related
Hi
As many people here i've encountred a problem with fota while being using a rooted ROM (g.lewarne ROM)
Now my phone is bricked. I can't go into recovery nor Download mode. I only have the LG logo for moments with error: secure booting error!
cause: boot certification verify
When i plug my phone it is not recognized in the hardware manager. I've already installed Drivers.
All i have in the hardware manager is a new hard under name QHSUSB_BULK that needs driver.
I have just one hope to get my phone alive, by reconizing it again by my computer, then maybe i can go under download mode.
I've tried everything but nothing could work without download mode.
PS: I've made a hard reset, which was maybe a silly decision.
By the way, after installing the OTA my phone went into CWM Recovery, it was detectable by adb, i used adb to reinstall TWRP, then i used command
"adb reboot download" instead of "adb reboot recovery", then i had never seen the CWM recovery again, only the mentioned above error.
After few seconds my phone screen goes black but the phone is still on since i can see light at the corners of the phone.
and it is not reachable by adb.
It makes me crazy now.
once i plug it to the computer it gives me plenty drives to format and one drive with only one folder inside called image, only readable, with many files inside.
Could you please help me to get my phone alive?:crying:
I recently bought a refurbished 2012 Nexus 7 on 4.2. The only things that I have done on the phone are entering my Google account details and downloading a single app (papyrus). I then clicked to install the automatically downloaded software update (it downloaded 4.3), and after restarting the tablet was stuck on the Nexus X boot animation forever. Factory reset/cache wipes do not help.
I found drivers for the phone to be recognized while showing the X, and I found drivers for the phone to be recognized after selecting the a "apply update from ADB" option from stock recovery. However Windows does not recognize the phone at all in recovery mode before selecting that option. Nothing changes in the device manager when plugged/unplugged. Windows doesn't attempt to install anything. It's as if I unplugged the cord once it enters recovery from the bootloader. I assume USB debugging is off, because it would be at the default setting. I tried using the Flash Stock + Unroot option in the Nexus Root Toolkit with the Soft-Bricked/Bootloop setting in, but that fails in both normal recovery (with the device unnoticed) and sideload mode. I'm guessing that debugging needs to be on for this?
Does anyone have any suggestions for other things to try? I have no way of knowing what the original owner may or may not have done, and this was the first time that I restarted the device, so I have no way to know if the problem was caused by the OTA or not.
EDIT: It looks like I made the situation worse. I attempted running the Flash Stock + Unroot option from the bootloader. I am not sure what happened, but now the device starts at the Google page with green start in an arrow. I have the bootloader options, and start and recovery options give me a "booting failed" message in the top left and just stay on the google page. Restarting the bootloader gives me the normal bootloader android image and the options have the same effects.
For anyone who runs into this problem, I seem to have at least temporarily solved it.
I followed the advice here to manually flash the factory image. I am now back to where I was when I bought the phone, and I will immediately enable debugging and test it's ability to restart, connect in recovery mode, etc now.
EDIT: It can restart normally (with the unlocked logo), but it is still completely unrecognized in recovery unless I choose the sideload option like before. Should I return the tablet?
wioneo said:
For anyone who runs into this problem, I seem to have at least temporarily solved it.
I followed the advice here to manually flash the factory image. I am now back to where I was when I bought the phone, and I will immediately enable debugging and test it's ability to restart, connect in recovery mode, etc now.
EDIT: It can restart normally (with the unlocked logo), but it is still completely unrecognized in recovery unless I choose the sideload option like before. Should I return the tablet?
Click to expand...
Click to collapse
still have a problem?
Wrong drivers, try other USB ports. Had that happen with another tablet. Only recognized in adb side load with galaxy nexus driver loading, possibly from universal adb drivers... Switched to a port on the other side and correct drivers finally worked.
Sent from my Le Pan TC1020 using Tapatalk
norwoodesteel said:
still have a problem?
Click to expand...
Click to collapse
As far as I know, no. I was never able to get the device is to be detected by my computer while in stock recovery mode, however it was detected after I flashed ClockworkMod Recovery. So I still have no idea what was causing that problem, but it is no longer relevant.
I'm on a rooted I337 that has been factory reset and under normal boot originally told me that normal boot has failed and was stuck with downloading.... but now tells me to select recovery mode in Kies also Download mode is still accessible. Before the crash I was working with a towelrooted 4.4.2. The problem is that nothing I do allows my computer to recognize it, It tells me that the device has malfunctioned and can't be identified. I've changed usb ports and cords and uninstalled/reinstalled drivers. Kies and Odin don't recognize it, but when I took it to a phone repair shop they were able to push a file that changed the normal boot error to what it is now, he gave it back to me to mess with and I could fix it if I could connect to it. Any help with this would be amazing
Thanks in advance
My I337 just got soft bricked earlier today, I made changes to my build.prop file to make it appear to be a Nexus 5, and rebooted just fine. I initially made a backup of the stock build.prop, so I decided to revert back to the stock file. when I rebooted, it gets frozen after the samsung screen and vibrates on any button press. I can boot into download and recovery mode, but I am unable to access the device via adb or kies.
Hello all,
Yesterday I saw in my nexus 4 all applications were getting crashed, so I tried to restart my phone. When I turned it back on, it got stuck in the boot animation. I cancelled the boot, and tried to boot it from the BootLauncher and in Recovery mode. Nothing worked. I tried booting it up last night and its been doing so since. Over 10 hours! What do I do? What is happening?
Its bootloop issues. I tried to install nexus root tool kit but it says "ADB device was not found". I tried my all ways to install drivers but device not getting detected to Nexus Root Toolkit.
My goal is to configure my device so that adb can communicate with it when its on (with USB debugging enabled) and also so that fastboot can communicate with it when its in bootloader mode.
Any help would be sure appreciated
Thanks!
Wipe Data or check your adb setup
Your emmc chip might be bad
Sent from my Nexus 4
Hi there,
Since the upgrade to Nougat 7.1.1, my Yoga Tab 3 plus (YT-X703F) is showing the following error "unfortunately system ui has stopped" each time I plugged the usb charger. The screen stay black until I disconnect the usb cable. So far, I tried without success
1) Factory reset via the reinitiation menu - Error still present after reinitiation
2) Boot into the recovery console - Not working. The bootloader hang and does not initiate the recovery console. I can restart the tablet into the normal mode after the battery pull method or via fastboot reboot command. The recovery console has been either erased or corrupted in the upgrade process.
3) ADB and Fastboot - not working. I cannot authorise the device since the screen is lock into black as above and both tools return the tablet status as unauthorized (adb devices or fastboot devices).
4) Boot in safe mode. Error is still present. I cannot access the tablet when charging and/or plug to a computer via USB.
Any help would be appreciated...