This was totally my fault but now I'm stuck. Any help would be greatly appreciated.
I just bought 2 nexus 5x phones and planned to install Cyanogenmod 13 on each. I succeeded on the first attempt but this is what happened on the second:
I forgot to re-enable USB debugging after unlocking the bootloader but managed to proceed with installing twrp and vendor.img. When it came time to push (adp push) cm13 to /sdcard, adp gave me this error: "adp: error: connect failed: no devices/emulators found". "fastboot devices" shows that the phone is connected and the recover mode screen shows fastboot mode. (Sorry, can't post a link to the install instructions because this is my first post).
I can get into twrp but trying to boot the phone normally does not work. I get an error saying that the device is corrupted, and then the boot hangs at the weird google animated logo. The screen never shuts off and the animated logo just keeps going around and around.
I can't do a hard reset because I keep ending up at twrp when I try to follow the hard reset instructions.
What should me next steps be?
Thanks.
Solved!
mrevans.info said:
This was totally my fault but now I'm stuck. Any help would be greatly appreciated.
I just bought 2 nexus 5x phones and planned to install Cyanogenmod 13 on each. I succeeded on the first attempt but this is what happened on the second:
I forgot to re-enable USB debugging after unlocking the bootloader but managed to proceed with installing twrp and vendor.img. When it came time to push (adp push) cm13 to /sdcard, adp gave me this error: "adp: error: connect failed: no devices/emulators found". "fastboot devices" shows that the phone is connected and the recover mode screen shows fastboot mode. (Sorry, can't post a link to the install instructions because this is my first post).
I can get into twrp but trying to boot the phone normally does not work. I get an error saying that the device is corrupted, and then the boot hangs at the weird google animated logo. The screen never shuts off and the animated logo just keeps going around and around.
I can't do a hard reset because I keep ending up at twrp when I try to follow the hard reset instructions.
What should me next steps be?
Thanks.
Click to expand...
Click to collapse
As usual, a good night's sleep and some googling helped me find a solution:
I followed the instructions from Google itself to completely reinstall the factory image: developers[dot]google[dot]com/android/nexus/images
Lack of hyperactive kids (the root cause of my initial mistake) allowed me to carefully follow the instructions.
Now my phone is back in its original state - except that I chose the factory image that matches the version of Cyanogenmod I want to install - and I can start the process over.
Related
I have a Nexus 9 Wi-Fi model, my PC runs Windows 8.1, and I am not new to rooting and custom ROMs. I attempted to install the M dev preview to the tablet following the instructions on Google's site. In the process, my console window showed one of the instances of "sending sparse 'system'" had FAILED. Now the device will not boot. It is stuck on the white Google logo splash screen. ADB does not recognize it, although it does appear in Windows Device Manager as "MTP USB Device". When I attempt to turn the device off or reboot it using any combination of power and volume keys, the screen will go blank for a few seconds and then return to the Google logo. I cannot turn the device off.
I've never seen this before, even with a failed flash... it's supposedly just the system partition that failed, anyway. Any ideas how I can break free of this?
EDIT: I ended up locating this post. If I hold the power button down until the screen turns off and then immediately press and hold power+voldn, it will launch the bootloader.
I've no experience with flashing M. But I have a suspicion that you flash of the system.img failed because of an obsolete fastboot on your PC. I'd suggest starting by updating your Android SDK. Then you can try fastboot flashing the M system.img again. Or fastboot flash the stock 5.1.1/factory image to return to stock.
soft bricked is all it is.
Made sure I had the latest Fastboot, ADB
Rebooted into Fastboot
Ran the Flash All batch file and it failed to install the System
I found instructions on flashing manually this from what was post is very common.
You extract all files, flash the boot, reset, and flash all the others.
Do a Google search it was easy enough to find.
hello guys i'm new here...and i have a big problem with my LG D390n ... i don't know what its mean this
the phone don't start up.. i cand do nothing :/ i can't enter in download mode,or recovery mode or anything else
ERROR: boot cerification verify
[1200] -----------------------------------------
[1200]
[1200] Secure booting Error!
[1200] Cause: boot certification verify
[1210]
[1210]------------------------------------------
Please,please i need help,i can't do anything..it freeze when i try to make a factory reset.. :/ i need help please somebody
this is te image with the freeze logo and download mode
i.imgur .com/ YBWSYXd.jpg[/IMG]
i.imgur. com /1fELirH.jpg[/IMG]
LG D390n boot certification verify
hey,
I have the same problems with some additional "perks":
when accessing download mode:
1. DOWNLOAD MODE
loading........
keep holding vol+ until download appears
ERROR: boot certification verify
secure booting error
cause: boot certification verify
2. RECOVERY MODE
It accesses it but then stops on loading screen "factory reset processing..." and i have to take out the battery to turn it off
3. Computer does not recognize it. It recognizes every other phone and I've downloaded all the necessary drivers and c++ updates
4. I have tried: LgMobileTool, lgFlashTool...
And nothing works I've been trying to fix it for a couple of days now and i am slowly giving up on it so I'm asking you guys for a little help on this, does anyone has a clue what can I do with it other then throwing it in the neighbors front yard...
I would appreciate any suggestion or idea.
Black screen, boot error, demi god
You may flash your device using "LG Flash tool 2014" with a firmware for your device.
Search on xda for "LG Flash Tool 2014" and you'll get all the resources you need.
If this does not help, follow the tut posted on the following thread by me.
https://forum.xda-developers.com/android/help/help-bootloop-lg-l70-d320-t3304382#post70962321
Device: Nexus 9 (Wi-Fi), Bootloader Unlocked
Computer: Windows 10 (Bootcamp on a Retina MacBook Pro)
After and unsuccessful attempt to install CM 12.1 on my Nexus 9 (Wi-Fi) using TWRP, I tried using this method to return to stock:
http://forum.xda-developers.com/nexus-9/general/guide-nexus-9-to-stock-guide-unbrick-t2975668/
I thought it had worked perfectly, but the tablet still would not boot. I went back and looked at the command prompt log and realized I had made a grave error: I had flashed everything except for the system image. I re-entered fastboot in an attempt to fix it by flashing the system, but now the tablet will not connect to my computer at all. I have tried to remove and reinstall the ADB drivers, but it doesn't show up at all in Device Manager. I tried booting into recovery via fastboot, but got an image of the android mascot knocked-out with an exclamation point, presumably since I over-wrote it with the method above.
Any ideas on how to restore the fastboot/adb connection with my computer? If I can accomplish that I can presumably just flash the system image and that would restore the stock ROM.
Any insight at all would be much appreciated.
dgindra said:
Device: Nexus 9 (Wi-Fi), Bootloader Unlocked
Computer: Windows 10 (Bootcamp on a Retina MacBook Pro)
After and unsuccessful attempt to install CM 12.1 on my Nexus 9 (Wi-Fi) using TWRP, I tried using this method to return to stock:
http://forum.xda-developers.com/nexus-9/general/guide-nexus-9-to-stock-guide-unbrick-t2975668/
I thought it had worked perfectly, but the tablet still would not boot. I went back and looked at the command prompt log and realized I had made a grave error: I had flashed everything except for the system image. I re-entered fastboot in an attempt to fix it by flashing the system, but now the tablet will not connect to my computer at all. I have tried to remove and reinstall the ADB drivers, but it doesn't show up at all in Device Manager. I tried booting into recovery via fastboot, but got an image of the android mascot knocked-out with an exclamation point, presumably since I over-wrote it with the method above.
Any ideas on how to restore the fastboot/adb connection with my computer? If I can accomplish that I can presumably just flash the system image and that would restore the stock ROM.
Any insight at all would be much appreciated.
Click to expand...
Click to collapse
Hello,
I have reported this thread to be moved to right Q&A section in order to get expertise help.
-Vatsal
Have you ever tried to connect your tablet to another computer?
Turns out I forgot to actually press the button in fastboot that enables the USB connection (I feel even more stupid now). Was able to return to stock, albeit with the "This device is corrupt" message during boot.
dgindra said:
Turns out I forgot to actually press the button in fastboot that enables the USB connection (I feel even more stupid now). Was able to return to stock, albeit with the "This device is corrupt" message during boot.
Click to expand...
Click to collapse
I got the same message yesterday after I returned to stock kernel from a custom one. What I did to get rid of that warning message was to flash all img file(boot, cache, recovery, system, vendor) in MMB29K factory image. (Bootloader is optional) [After that I also performed a factory reset but this step might be unnecessary, do it if the message still exist after flashing stock images] If you don't like that warning you can try these procedures.
Hey Mates!
I've been looking for a solution but cant find any helpful advices.
I have rooted my Motorola G 2 days ago, no problem. As soon as I rebooted it, it wont boot.
these are the errors that occur when I try to boot it
-hab check failed for boot
-failed to verify hab image boot
-failed to validate boot image
Fastboot Reason: Fall-through from normal boot mode
When I try to go to recovery, it says "no command".
Edit: It also says that my device is locked.
Meanwhile I've connected it with my PC and I tried to run the desktop version, but no changes so far.
I'd really need your help
Hi all,
Well, operator error is definitely at fault here... I made a series of mistakes that got me to where I am now. All I intended on doing was repairing my dad's tablet which was running atrociously slowly. I tried to follow some steps, but improvised as I was getting errors and obviously ended up making things a lot worse...
Now tuning on the tablet will directly go to a command line interface with a long series of errors and these are the last 2 lines:
Rich (BB code):
blkD :HardDisk - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0) /HD(14,GPT,80868086-8086-8086-8086-000000000008,0x646828,0x16D47D8)
blkE :BlockDevice - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0)
Press ESC in 1 seconds to skip startup.nsh, any other key to continue.
Shell> _
In this state it cannot be interacted with and won't be detected by my PC over USB.
This happens for normal, recovery and bootloader modes. The only mode that I can access is DNX mode but attempting to boot droidboot will result in the same command line UI described above, including when trying to restore the BIOS using the PC executable (which I assume needs to enter fastboot mode, which it can't do...).
What can I do now? Any way to get anything working in the above screen or through DNX?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp.img when all I have access to on the tablet is DNX mode?
Detailed history below...:
HISTORY
1)
The tablet is a Lenovo Yoga Tab 2 1050F. It was running very slowly to the point where my dad just didn't bother to use it. I thought it would be wise to factory reset it as a first step. There is no option to do so within the Lenovo skin of Android so I started by going into recovery mode and performed a factory reset from there.
After it rebooted, the Android UI would loop back to the language selection after connecting to a WiFi network and I would get "Unfortunately Google Play Services has stopped." error message. It would just loop through the Language Selection > Connect to WiFi network pages over and over.
2)
Having installed CM on my old S3 back in the day, I thought I could go about the same process and flash a gapps ZIP file in recovery mode. That didn't work, I got an error because the zip was unsigned.
I thought I could install TWRP to flash unsigned zips, reinstall Gapps and get the tablet passed the Android UI loop.
3)
I followed this guide on XDA to install an unofficial TWRP (which involved unlocking the bootloader). It didn't work because I couldn't flash over ADB (because the tablet couldn't allow Developer Mode since it was stuck in the Android UI loop). So I flashed as many files as I could in fastboot.
I eventually flashed the TWRP recovery.img but that didn't work : when turning on to Recovery mode it would just go back to the bootloader screen.
4)
I thought I must have screwed up something up so I tried to restore the BIOS using an executable I found but I realized the tablet was already upgraded to Lollipop and the only BIOS restoration exe was for Kitkat. Sure enough it got even worse and I could no longer boot Android.
5)
I still had bootloader and fastboot though so I followed a guide to restore the tablet to the original OS (which ironically I already downloaded before trying to get TWRP but forgot about and didn't unpack). I set up Intel Platform Tools but the flash process didn't work because it went to droidboot and then lost USB connection. On the Intel program it would just stay stuck at 20% Wiping ESP. It would time out twice and then give me a final error message.
6)
So I thought to explore the flash.xml file provided to see if I could do the steps manually. I knew it was stuck at wipe ESP because in droidboot it couldn't get commands from PC. So I went into fastboot and wiped ESP manually myself! Little did I know how foolish this was to do because I was simply unable to flash the provided ESP.img again. Following this I lost access to the bootloader.
7)
I found a guide to restore a bricked 1050F here on XDA but it needs droidboot which now goes to the command line UI described at the top of this post. When attempting to restore the kitkat BIOS again, droidboot is also needed which results in the same cmd UI.
8)
Which leads me to where I am now which is that the tablet doesn't boot to: normal, recovery, bootloader/fastboot or droidboot. Which is why I am now asking for help. What can I do?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp when all I can get access to is DNX mode?
Thanks for reading this far and if you have any more ideas, please let me know, thanks in advance.
Hi, would anyone like to weigh in on this issue?