I was trying to flash the stock recovery, in order to install the new OTA update. I was in Rom Manager, and hit "boot to recovery". Now it boots to LOGO, tries to boot to recovery then loops back. I can get to the Download mode, but the installed driver is not recognizing. Unidentified device. If I force the driver, it gives me a code 10 error, Could not turn device on in the windows device manager.
Any help would be appreciated.
After trying many things, post 55 saved the day. http://forum.xda-developers .com/showthread.php?t=1195861&page=6
Related
I was upgrading the current Stock rom on my ZTE Nubia Z5s Mini, I went through the recovery mode to load the new rom and got a message saying that the rom installed correctly, I rebooted the device and now its stuck at the MIUI logo or if I try to load the recovery mode I get the Nubia logo just to load back to the miui logo again. I got the rom from the MIUI site its v5.
I've left the phone for over an hour hoping it was just loading up but no change, the phone heats up and even has a charger screen when plugged in.
Anyway to get back into the recovery mode to load the original rom again or any other way of fixing this? help :crying:
I've no idea how to help you with this but I'm bumping the thread because I know how you feel.
Sent from my HUAWEI Y536A1
I'm trying to flush the rom by using adb but with an issue, even thou my device is recognized as Nubia Z5s Mini in device manager it still gives a driver error "these have been installed" and in cmd adb it does not see the device.
Update : Got drivers for install from Clockwordmod website but it will only accept the drivers if I set the phone as a modem in device manager when installing them, still not recognized by adb using CMD.
Solved driver issue and qusb_download issue, ADB drivers are done through all drives in device manager pointing to the Google USB drivers and select adb interface then run CMD from within the Google SDK program folder in platform-tools to read the device.
Now using emmc but need to generate EMMCBLD.HEX & 7x30_msimage.mbn if anyone can help, I can enter adb using recovery mode but blocked from making changes in fastboot mode, currently in download mode which can see a drive H but need the two files to proceed any further.
I was trying to install Cyanogen Mod using the steps on their site(cant post the link because I am under 10 posts)
When i got to these steps 6 and 7 under installing recovery is when my TF201 appears to have become bricked
6. Flash recovery onto your device by entering the following command: fastboot -i 0xb05 flash recovery your_recovery_image.img where the latter part is the name of the file you downloaded.
7. Once the flash completes successfully, reboot the device into recovery to verify the installation.
Note: Some ROMs overwrite recovery at boot time so if you do not plan to immediately boot into recovery to install CyanogenMod, please be aware that this may overwrite your custom recovery with the stock one.
I had just run the command in step 6 and rebooted the device as described in step 7. Now my device cant even reboot. I cant get it into recovery or fastmode because holding the volume and power button does not do anything, the tablet just stays stuck on the boot menu. I had unlocked the tablet with Asus' tool earlier today so I can see the "The Devices is Unlocked." message at the top left. Any help would be much appreciated if it is possible to fix this issue without sending it to ASUS(because they will probably end up charging more than the tablet is worth in repair fees).
Some information: Before all this it was running Stock Jelly Bean 4.1.1
thanks
some more info.
I can see an APX device with a yellow exclamation mark under "Other Devices" in windows Device manager. Fastboot and ADB do no recognize any devices
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.
I Flashed TWRP Recovery onto my Rooted VS880PP Phone, but when I try to boot into it I get Security Error 1003 error message on my screen, and the phone freezes on that screen. If I remove the battery and restart my phone I can boot normally into my rooted Android Lollipop system, but I have no access to Recovery. Also I do have a computer running Windows 10, and ADB Fastboot Installed.. When I connect my phone to the computer ADB recognises the VS880PP Device. I need help getting my phone to boot into recovery. Thanks in advance for any assistance you can provide.
I flashed TWRP to the device successfully, and proceeded to try to install Magisk 19.3 zip. It would begin to do a recovery bootloop. I fixed it using TWRP, and tried using the patched boot img from magisk manager instead. This is where things go wrong. After flashing boot.img, the phone refuses to boot, and asks me to do a factory reset. I did this twice, and the phone continued not to boot. I then tried installing the latest android Q factory image. The flash failed, and the phone stopped showing up when I do fastboot devices or adb devices. It is stuck in the bootloader telling me slot b is not bootable. I have tried different ports, but adb and fastboot are no longer responding.
Take out the battery for 10 sec or more replace, see if you can get back into recovery. Recovery should be TWRP.
You may need to uninstall and reinstall the driver on your computer. IF it is a Win computer should show up in device manager at the top under Android.
https://www.xda-developers.com/how-to-install-custom-rom-android/
or you can do a factory reset which is also a button.
I fixed it by holding down the power and vol up buttons, which allowed me to use fastboot again and fixed everything. Thanks for the help tho>