HoneyBadgerRy
Newbie
My nexus 7 is stuck in bootloop, apparently usb debugging isn't set (and it cant be because of bootloop) and in recovery mode all i get is an android with his hood open displaying a ! in a triangle.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
I did everything like you said untill the point where I ran the batch file (flash all.bat) and command prompt said waiting for device, I suspect this to be a driver error (though I have no idea), I am running windows 7 64bit (ultimate) and ran the universal adb drivers. Any advice?Well, TWRP in and of itself is not going to allow you to re-flash the factory image--you need fastboot for that.
So, here's how to get fastboot:
- download our mini-SDK if you don't have the fastboot utility already:
- see this post for details, but you basically want to extract it's contents to a folder on your PC, start-up a Windows Command Prompt window, and cd (change directory) to the folder where the fastboot.exe file lives
Note, before looking at the notes/instructions below, have a peek at this thread first:
the notes below should reinforce the info in that thread
To flash the most current factory image for your device
- download the 6.0.1 MMB29K factory image for your device:Again, you don't need this now, but here it is for later:
https://dl.google.com/dl/android/aosp/razor-mmb29k-factory-a39e7047.tgz- extract the contents of that archive to a folder on your PC and navigate (cd) to the folder where the flash-all.bat file lives
(it'll be a large download, as I'm sure you already know; this is from the Nexus Factory Images page)
- use Windows Explorer to copy the fastboot.exe file (referenced earlier) into the same folder where the flash-all.bat file lives
- assuming your device is in fastboot/bootloader mode and you have the fastboot.exe file in the same folder as the flash-all.bat file and your current directory is where these two files live, then you should be able to run the flash-all.bat file to start the restoration process
After you do the above, rooting will be a breeze...
You can get TWRP for your device from here (again, not relevant for re-flashing a factory image):
- download https://dl.twrp.me/flo/twrp-2.8.7.0-flo.img
- copy that twrp-2.8.7.0-flo.img into the same folder where your fastboot.exe file live
- like I indicated, that's not really useful at this point, but at least you'll have it
- if you want to flash that custom recovery image to your device, do this:
- put your device into fastboot/bootloader mode
- type fastboot flash recovery twrp-2.8.7.0-flo.img
- use the hardware buttons in bootloader mode to start your newly-flashed recovery
For when it's time to re-root, download this file from Chainfire's site:
I did everything like you said untill the point where I ran the batch file (flash all.bat) and command prompt said waiting for device, I suspect this to be a driver error (though I have no idea), I am running windows 7 64bit (ultimate) and ran the universal adb drivers. Any advice?
Would a Ubuntu live CD do any help? If not I can probably find enough PC parts laying around to build a Linux compatible PC (not sure if I have any nvidia GPUs, and Linux hates amd drivers).Well, the Driver Software Installation window shows that the drivers were not successfully installed, so it's not a surprise that you're seeing "waiting for device" in the other window you have displayed.
You'll need to find and install some USB drivers for your PC that will allow a "fastboot devices" command to return something other than "waiting for device".
Unfortunately, that's the bane of using Windows with Android--the USB drivers .
Ok so I followed those steps and have a functional device, but I still cant get fastboot to work on windows. I ended up cd'ing onto a folder on my desktop with the fastboot files and stock rom. I then ran these commands:Ah, you should be able to start up a terminal session, cd to the download folder (make sure you've put the fastboot-linux file in the same folder) that contains the flash-all.sh script), and invoke the flash-all.sh script.
You should probably rename the fastboot-linux file to just "fastboot" so that the flash-all.sh script still work.
Additionally, adding the download folder to your PATH variable would also be a good idea
Something like this (don't type the purple text in parens, obviously ) :
$ cd downloads/workdir (or whatever the name of the folder is where you put all the files)
$ mv -i fastboot-linux fastboot (rename the fastboot utility so the script works)
$ set PATH=$PATH:downloads/workdir (add download location to the PATH environment variable)
$ sudo ./flash-all.sh (invoke the flash-all.sh script)
If you have issues with the above, then examine the flash-all.sh script and manually invoke each of the fastboot commands, in order, and prefixed with the sudo ./ string (you don't need to prefix the sleep commands):
$ cat flash-all.sh (display the contents of this file)
Carefully examine the contents of the above and use that as a template to copy and paste those fastboot commands and prefix them with the sudo ./ string:
$ sudo ./fastboot flash bootloader bootloader-flo-flo-04.05.img
$ sudo ./fastboot reboot-bootloader
$ sleep 5
$ sudo ./fastboot -w update image-razor-mmb29k.zip
Make sense?
edit: updated with exact commands from the flash-all.sh script
Ok so I followed those steps and have a functional device, but I still cant get fastboot to work on windows. I ended up cd'ing onto a folder on my desktop with the fastboot files and stock rom. I then ran these commands:
$ sudo fastboot flash bootloader bootloader-flo-flo-04.05.img
$ sudo fastboot reboot-bootloader
$ sleep 5
$ sudo fastboot -w update image-razor-mmb29k.zip
Now I'm running vanilla marsh mellow and vanilla recovery. I have TWRP in the same folder, what commands would I have to run to install TWRP? I tried sudo fastboot flash (TWRP's file name) and as of typing this I think what was missing was the word recovery... I'll be back with results.
Sorry, but I got really busy, The link you provided me is an md5 file, so I am going to try and find it myself.Yeah, it's the versions of Chainfire's UPDATE-SuperSU-v2.46.zip and before that were created for non-6.x versions of Android that are not compatible with 6.x.
The boot loops are likely caused by the app_process32/64 file(s) that get's replaced during the rooting process and that are not compatible with 6.x.
It's not obvious that NRT automatically uses the most current (still beta) rooting packages or if you can specify one of the new ones yourself.
Anyway, I just realized that this thread was also still in the general rooting area--I've now moved it to the N7 (2013) root area.
Ryan, any update on your device's status for us?
Sorry, but I got really busy, The link you provided me is an md5 file, so I am going to try and find it myself.
Edit: Found File, installed TWRP, I should be fine from here, nothing I haven't done before. However, I need to start a new thread for flashing a custom rom to my phone, and would like if you could help me make sure I don't mess it up. (its kinda a messed up deal).