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.
Related
I have searched a lot on google and xda and havn't found an answer to my issue. Either I'm searching for the wrong thing or I have a very unique problem.
My basic problem is on two Nabi 2's I can't access the bootloader in order to be able to fastboot TWRP (or any other recovery). It just perpetually hangs.
Both tablets boot just fine. Both tablets are on 1.9.37. Both tablets can be factory wiped via the stock recovery.
Both tablets were rooted via TWRP 2.3.3.0 a few years ago in order to install gapps. I wanted to be able to upgrade the tablets to JB when it came out so I used Nabilablite to "return to stock". I followed all of the prompts and it appeared as though everything worked as desired. I downloaded the OTA update told it to install and never looked at the version again...I just assumed it installed. Handed the tablets back to the kids and everyone was happy. Apparently all I did was flash the stock recovery because they are still rooted and have gapps after several factory resets.
Now (a year later) I have realized I was a dufas and didn't actually effect the change I wanted.
If I hold Vol+ & Pwr buttons it loads to the recovery/boot menu with "boot normally" "fastboot protocol" "recovery kernal" and "forced recovery". If I boot normal, the tablet works fine but I can't update via OTA.
If I choose fastboot protocol it just hangs...for ever...HOW DO I FIX THIS!?!?!
If I choose recovery kernal it loads the stock recovery but still wont install any update OTA or otherwise, even from the sd card.
If I choose forced recovery nothing happens, it also appears to just hang.
If I hold Vol- & Pwr button the nabi logo flashes then the device turns off.
If I hold Vol+ & Vol- & Pwr buttons it appears to be the same as just Vol+ & Pwr.
With the tablet on and fully booted I can see it via ADB. I tried using the adb restart bootloader. The tablet reboots but then just hangs never actually loading the boot loader...
I found http://forum.xda-developers.com/showthread.php?t=2587543. But aicjofs mentions seeing a bootloader issue once before.
Usually when it hangs at the Nabi logo it means you don't have the USB cable plugged in or that the fastboot driver is not installed.(Check device manager and see if fastboot driver is installed/no exclimation point). If that's not the issue then it's the bootloader which I have only seen one person have that issue. Depending on which OTA's you have ran there was an update to a Jellybean bootloader so it's possible. That can be fixed with nvflash or placing the bootloader blob in the staging partition.
Also you can always get recovery back without fastboot in Android by dd'ing the recovery over.
For example if the recovery image is on the internal SD
dd if=/data/media/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
Click to expand...
Click to collapse
I have NO idea what dd'ing the recover over is...
Thank you for any help fixing this.
P.S. I have a 3rd tablet that I also used TWRP 2.3.3.0 on to root and install gapps with. I did NOT use nabilablite on that tablet to return to stock. Yesturday I used fastboot to flash TWRP 2.6(something) to flash a JB OTA update which worked fine. It was also able to download and install every other OTA update all the way to the most recent KK with no problems...
najman9 said:
I have searched a lot on google and xda and havn't found an answer to my issue. Either I'm searching for the wrong thing or I have a very unique problem.
My basic problem is on two Nabi 2's I can't access the bootloader in order to be able to fastboot TWRP (or any other recovery). It just perpetually hangs.
Both tablets boot just fine. Both tablets are on 1.9.37. Both tablets can be factory wiped via the stock recovery.
Both tablets were rooted via TWRP 2.3.3.0 a few years ago in order to install gapps. I wanted to be able to upgrade the tablets to JB when it came out so I used Nabilablite to "return to stock". I followed all of the prompts and it appeared as though everything worked as desired. I downloaded the OTA update told it to install and never looked at the version again...I just assumed it installed. Handed the tablets back to the kids and everyone was happy. Apparently all I did was flash the stock recovery because they are still rooted and have gapps after several factory resets.
Now (a year later) I have realized I was a dufas and didn't actually effect the change I wanted.
If I hold Vol+ & Pwr buttons it loads to the recovery/boot menu with "boot normally" "fastboot protocol" "recovery kernal" and "forced recovery". If I boot normal, the tablet works fine but I can't update via OTA.
If I choose fastboot protocol it just hangs...for ever...HOW DO I FIX THIS!?!?!
If I choose recovery kernal it loads the stock recovery but still wont install any update OTA or otherwise, even from the sd card.
If I choose forced recovery nothing happens, it also appears to just hang.
If I hold Vol- & Pwr button the nabi logo flashes then the device turns off.
If I hold Vol+ & Vol- & Pwr buttons it appears to be the same as just Vol+ & Pwr.
With the tablet on and fully booted I can see it via ADB. I tried using the adb restart bootloader. The tablet reboots but then just hangs never actually loading the boot loader...
I found http://forum.xda-developers.com/showthread.php?t=2587543. But aicjofs mentions seeing a bootloader issue once before.
I have NO idea what dd'ing the recover over is...
Thank you for any help fixing this.
P.S. I have a 3rd tablet that I also used TWRP 2.3.3.0 on to root and install gapps with. I did NOT use nabilablite on that tablet to return to stock. Yesturday I used fastboot to flash TWRP 2.6(something) to flash a JB OTA update which worked fine. It was also able to download and install every other OTA update all the way to the most recent KK with no problems...
Click to expand...
Click to collapse
EDIT: OOOPPS. I didn't see this was in the XDA Assist section. I'm not suppose to answer questions(I was just searching for Nabi questions and didn't notice this was XDA assist), dedicated XDAers just point you in the right direction in this section. Please ask the question again in the Nabi2 section and I'l come help you. http://forum.xda-developers.com/nabi-2
This might help answer some questions http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
If it just hangs at fastboot protocol then the USB connection isn't good or fastboot driver isn't installed most of the time. Can you verify fastboot shows up in device manager?(I know the 3rd tabet worked OK) .
Nabilabite doesn't do anything that should change the bootloader, and fastboot should still work as it did before.
dd'ing recovery over means that you use the root access you have in Android to flash the recovery partition instead of using fastboot. IT's just another way of getting the TWRP recovery on the tablet.
The stock recovery won't install the OTA because when you added Gapps it changed some fies and the OTA sees those files as invalid and will fail.
Forced recovery always looks blank screen. It's waiting for you to give it a bootloader to run(beyond the scope here).
You should be able to get back on track once you have TWRP loaded. It's one of 3 things. Bad USB connection, fastboot driver not installed right, bootloader damage. Check the first 2 issues despite the fact the 3rd tablet had no such problems.
One of the XDA smart guys fixed my error of posting this in the wrong section.
I'm running Windows 7 Ultimate and have installed and re-installed the drivers several times. When the tablet's are fully booted ADB has a good connection and sucessfully sends the command to reboot. So I don't believe there is a driver or USB cable error...
When the tablets hang on the fastboot protocol my computer makes the usb connecting noise but fails to install the drivers...
When I hit forced recovery I hear the unrecognized USB device sound...
These two things make me think I don't have the proper drivers installed...but I don't understand how the driver's work when the tablet is booted but not when trying to access the boot loader.
It appears as though I'm going to have to try the dd method if you are able to point me in that direction please.
EDIT: Now I'm thinking I really DON'T have the fastboot drivers installed. I just plugged the 2nd tablet that hands on the fastboot menu and fastboot failed. I also booted the tablet completly, the adb driver's installed correctly but the fastboot driver's did not...I have installed the 64 bit driver's included with nabilablite. I can't find any actual other downloads. The 15 second ADB installer didn't change anything...
najman9 said:
One of the XDA smart guys fixed my error of posting this in the wrong section.
I'm running Windows 7 Ultimate and have installed and re-installed the drivers several times. When the tablet's are fully booted ADB has a good connection and sucessfully sends the command to reboot. So I don't believe there is a driver or USB cable error...
When the tablets hang on the fastboot protocol my computer makes the usb connecting noise but fails to install the drivers...
When I hit forced recovery I hear the unrecognized USB device sound...
These two things make me think I don't have the proper drivers installed...but I don't understand how the driver's work when the tablet is booted but not when trying to access the boot loader.
It appears as though I'm going to have to try the dd method if you are able to point me in that direction please.
EDIT: Now I'm thinking I really DON'T have the fastboot drivers installed. I just plugged the 2nd tablet that hands on the fastboot menu and fastboot failed. I also booted the tablet completly, the adb driver's installed correctly but the fastboot driver's did not...I have installed the 64 bit driver's included with nabilablite. I can't find any actual other downloads. The 15 second ADB installer didn't change anything...
Click to expand...
Click to collapse
Uninstall those nablablite and try this one. http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
Or look at the other options in section 4 here http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
So I am no stranger too rooting, but i managed to do something wrong when dirty flashing a rom update.
Gapps no longer works, my device is un-rooted and the 'gapps stopped working' notification pops up every 1 second, making my device unusuable.
I'm using the Amazon Fire 7" running SlimLP. To be clear, this was all working at a point.
I could boot TWRP and fix this with a backup I made, but here's the problem: Fastboot commands isn't working.
I can use ADB and boot into fastboot mode, but once there my commands have no effect and the Windows 7 CMD just displays <waiting for device>.
Also, my stock recovery seems to be deleted so I have no recovery whatsoever.
I have all the correct drivers and used the google sdk drivers to no effect. Also, in device manager my device shows up as 'Android Bootloader interface' and shows: This device cannot start. (Code 10).
So to Sumarise
My device needs a backup flashed
Fastboot commands are unresponsive
I have no root.
I have all the drivers installed
I am using a 2015 Kindle fire 7"
With a windows 7 64 bit laptop
Please help!!!
Thanks in advance
If you need any more info, drop me to a comment and I will get back to you ASAP, I'm desperate!
I can use flashfire, and Im open to any workarounds.
amaramar2000 said:
So I am no stranger too rooting, but i managed to do something wrong when dirty flashing a rom update.
Gapps no longer works, my device is un-rooted and the 'gapps stopped working' notification pops up every 1 second, making my device unusuable.
I'm using the Amazon Fire 7" running SlimLP. To be clear, this was all working at a point.
I could boot TWRP and fix this with a backup I made, but here's the problem: Fastboot commands isn't working.
I can use ADB and boot into fastboot mode, but once there my commands have no effect and the Windows 7 CMD just displays <waiting for device>.
Also, my stock recovery seems to be deleted so I have no recovery whatsoever.
I have all the correct drivers and used the google sdk drivers to no effect. Also, in device manager my device shows up as 'Android Bootloader interface' and shows: This device cannot start. (Code 10).
So to Sumarise
My device needs a backup flashed
Fastboot commands are unresponsive
I have no root.
I have all the drivers installed
I am using a 2015 Kindle fire 7"
With a windows 7 64 bit laptop
Please help!!!
Thanks in advance
If you need any more info, drop me to a comment and I will get back to you ASAP, I'm desperate!
I can use flashfire, and Im open to any workarounds.
Click to expand...
Click to collapse
Please don't cross-post; found this exact text in three different threads. My earlier response here. Others have basically said the same thing. You're done.
I've searched around but haven't found anything on this. I want to root my phone to get more out of it and all, but It's not going so well.
My phone is a Huawei Honor 7 running Android 6.0, I'm using stock since I bricked my phone (I backed up anything important which were some apps and my contacts and such), so I have that which I can import.
I've followed different tutorials with no success in getting TWRP onto my phone, I got it unlocked but I can't get any further.
This is what I've tried for it:
Boot phone into Fastboot and have it connected wia USB to computer.
Checked if it shows up in "fastboot devices", which it does.
Did "fastboot flash recovery TWRP.img", which it says went OKAY, but then when after rebooting it, and getting it into recovery mode, it just boots into the default Huawei eRecovery, and not TWRP.
I've tried different TWRP images, some who said it were for the Honor7 as well, but with no luck, it just won't boot into it.
I hope that's all the needed information, if need anything else just ask.
mikkel1156 said:
I've searched around but haven't found anything on this. I want to root my phone to get more out of it and all, but It's not going so well.
My phone is a Huawei Honor 7 running Android 6.0, I'm using stock since I bricked my phone (I backed up anything important which were some apps and my contacts and such), so I have that which I can import.
I've followed different tutorials with no success in getting TWRP onto my phone, I got it unlocked but I can't get any further.
This is what I've tried for it:
Boot phone into Fastboot and have it connected wia USB to computer.
Checked if it shows up in "fastboot devices", which it does.
Did "fastboot flash recovery TWRP.img", which it says went OKAY, but then when after rebooting it, and getting it into recovery mode, it just boots into the default Huawei eRecovery, and not TWRP.
I've tried different TWRP images, some who said it were for the Honor7 as well, but with no luck, it just won't boot into it.
I hope that's all the needed information, if need anything else just ask.
Click to expand...
Click to collapse
If you want to get into recovery you have to unplug your phone from PC. You can use "ADB reboot recovery" command if you're connected and running system.
Sent from PLK-TL01H
mikkel1156 said:
I've searched around but haven't found anything on this. I want to root my phone to get more out of it and all, but It's not going so well.
My phone is a Huawei Honor 7 running Android 6.0, I'm using stock since I bricked my phone (I backed up anything important which were some apps and my contacts and such), so I have that which I can import.
I've followed different tutorials with no success in getting TWRP onto my phone, I got it unlocked but I can't get any further.
This is what I've tried for it:
Boot phone into Fastboot and have it connected wia USB to computer.
Checked if it shows up in "fastboot devices", which it does.
Did "fastboot flash recovery TWRP.img", which it says went OKAY, but then when after rebooting it, and getting it into recovery mode, it just boots into the default Huawei eRecovery, and not TWRP.
I've tried different TWRP images, some who said it were for the Honor7 as well, but with no luck, it just won't boot into it.
I hope that's all the needed information, if need anything else just ask.
Click to expand...
Click to collapse
+1 the phone must not be connected to the pc when you try to reboot in recovery mode
Also you can use the MultiTool to install Twrp and reboiot to recovery from this tool
Thanks a lot guys! I'm able to boot into TWRP now.
Now I only got to fix my SuperSU problem, it makes me stuck where it says honor, which is loading screen really.
Tried different versions of the BETA-SuperSU (using the betas because got one from tutorai ladn read that they support Android 6.0), but as said simply stuck and don't know if it actually rooted my phone.
Hello, XDA-Members,
long story short, I tried to flash CM-13 on my Honor 5X(KIW-L21 B340). Well, that didn't work and the phone always booted into TWRP. So I flashed FlymeOS because I couldn't flash the stock rom anymore(No matter why.).
It worked perfectly, and I were able to use my phone. After restarting my phone it booted back into TWRP, tried to wipe and all that stuff and even re-flashed Flyme OS, but still booted into TWRP. I was so UPSET that I deciced to flash the original RECOVERY.img for my Honor 5X. Well and from there I made it worse.
Windows and Linux don't recognize my phone. Windows just shows an empty E:\ drive. Reinstalled Google USB drivers, reinstalled driver etc. Didn't work. Now, when I start my phone it boots into the honor 5x recovery. I got these options available:
- Reboot system now
- Wipe data/factory reset
- Wipe cache partition
So, well. I can't install a rom anymore. As well when trying to connect my phone to ADB it won't work either. ADB doesn't recognize my phone. I made a big bull****, tbh. Installed HI-Care as well, but it doesn't get recognized either. I can also boot into Huawei eRecovery, connect to my wifi because it says it can download the stock rom. Guess what, it always said failed so I'm not able to do this either.
I'm really stuck. Anybody got an idea? Thanks in advance!
dunios said:
Hello, XDA-Members,
long story short, I tried to flash CM-13 on my Honor 5X(KIW-L21 B340). Well, that didn't work and the phone always booted into TWRP. So I flashed FlymeOS because I couldn't flash the stock rom anymore(No matter why.).
It worked perfectly, and I were able to use my phone. After restarting my phone it booted back into TWRP, tried to wipe and all that stuff and even re-flashed Flyme OS, but still booted into TWRP. I was so UPSET that I deciced to flash the original RECOVERY.img for my Honor 5X. Well and from there I made it worse.
Windows and Linux don't recognize my phone. Windows just shows an empty E:\ drive. Reinstalled Google USB drivers, reinstalled driver etc. Didn't work. Now, when I start my phone it boots into the honor 5x recovery. I got these options available:
- Reboot system now
- Wipe data/factory reset
- Wipe cache partition
So, well. I can't install a rom anymore. As well when trying to connect my phone to ADB it won't work either. ADB doesn't recognize my phone. I made a big bull****, tbh. Installed HI-Care as well, but it doesn't get recognized either. I can also boot into Huawei eRecovery, connect to my wifi because it says it can download the stock rom. Guess what, it always said failed so I'm not able to do this either.
I'm really stuck. Anybody got an idea? Thanks in advance!
Click to expand...
Click to collapse
Shut down the phone
plug the phone into your windows PC
hold volume down + power to enter the bootloader
from windows open the command prompt - type fastboot devices hit enter (your phone serial number will display)
type fastboot flash recovery TWRP.img (be sure to use this TWRP and it's named TWRP.img and in the same folder as fastboot)
after the file is flashed successfully hold power + volume up + volume down
after 5 seconds let go of power and continue to hold the volume buttons until TWRP boots
From TWRP you can now copy the CM13.zip and Gapps.zip to your phone and wipe/factory reset - then install them one by one
be sure their are no errors .. if you see errors choose reboot recovery and try the flash again until it succeeds.
first boot of cm13 will take some time, be patient
Thanks,
I recovered my phone. Awesome!
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?