After about 10 tries I still cant get this damn tablet to work with the toolkit. I screwed up while updating and lost root, now I cant get the root toolkit to recognize my device after installing the drivers on any pc (tried win two with 8 and two with 7). I have no clue what to do as I was able to unlock and root it initially but now I cant redo it to get my device back and in working order. This is driving me insane!!!!!!!!! I am using the most recent toolkit, and my tablet is on 4.2.2 unlocked but no longer rooted.
Another satisfied toolkit customer. Did you pay for the privilege? If yes, I suppose you should call their support department during normal business hours.
It's a little surprising. I can see that the behavior of ADB might have changed - when the regular OS is booted. (This is a new security feature of 4.2.2 adb - you need the latest SDK version of the "adb" program)
And if you used the OTA, then the custom recovery was replaced by the 4.2.2 stock recovery, so ADB won't even show up there (stock recoveries don't run the "adbd" daemon).
But I would think that you should be able to use fastboot, even if the bootloader was also upgraded.
So, a couple of questions.
A) Can you get the tab into bootloader mode?
B) Does it show version 4.18 on that screen?
C) Does the recovery appear to have been replaced by a stock recovery?
D) Does your PC (pick one and stick with it) show an Unknown Device, or something else when you plug the tab in whilst it is in bootloader/fastboot mode?
E) From the command line, what happens when you run "fastboot devices" either from the command line or from the toolkit when the device is plugged to the PC and in bootloader/fastboot mode?
Thanks for the fast reply. First of I thought the toolkit was free, since it is posted in many forums and you can download it right from the developers site. Next, I did use the OTA like a moron because I forgot that this was my unlocked and rooted nexus. Now to your questions:
A: I can get it into bootloader
B: The version is 4.18
C: The recovery only shows up with the droid dude and a red !
D: On my Win8 Desktop it shows up under Andriod Phone as 'Android ADB Interface' in device manager
E: in the comand line I get the serial of my tablet
lamboboy732 said:
Thanks for the fast reply. First of I thought the toolkit was free, since it is posted in many forums and you can download it right from the developers site. Next, I did use the OTA like a moron because I forgot that this was my unlocked and rooted nexus. Now to your questions:
A: I can get it into bootloader
B: The version is 4.18
C: The recovery only shows up with the droid dude and a red !
D: On my Win8 Desktop it shows up under Andriod Phone as 'Android ADB Interface' in device manager
E: in the comand line I get the serial of my tablet
Click to expand...
Click to collapse
This
>> E: in the comand line I get the serial of my tablet
is good.
the droid dude is the stock recovery. It actually sounds to me like the OTA succeeded for you - as you are showing both stock recovery and the 4.18 bootloader.
With the tablet in fastboot mode, just flash a custom recovery and you are good to go. You can either use "fastboot flash recovery name-of-recovery-image-file.img", or the equivalent operation in the toolkit.
Then, boot into recovery, and see if
A) the custom recovery appears correctly, and
B) if ADB now shows up either via command line or the toolkit (with the device in custom recovery).
If you got your adb & fastboot tools via installation of the Android SDK, make sure it is updated to the latest version
adb version
should report something like 1.0.31 (iirc)
good luck
Related
So I am having a lot of problems with trying to root my nexus 7. I'm pretty sure it boils down to a driver issue but I'm not sure. I have tried installing the correct drivers over and over again also uninstalling other hardware manufacturers drivers and I cannot get adb to recognize my device when it is shut off and in the boot loader.
When the tablet is on and I have debugging on, adb shows up and is recognized, however my problem is that whenever I reboot into the boot loader I lose adb recognition. So therefore I can't root or do anything else. Fast boot commands work fine its only the issue with adb.
If anyone has any suggestions as to what I can do I would really appreciate it. I don't know if its just a hardware issue or something I am doing wrong on my end.
This is also not my first time manually unlocking/rooting a device
When you initially connect, the device shows up as a "Nexus 7".
When you reboot into the boot loader, the device name changes, and there is no driver for that device.
As far as I could tell, I would have to do the root process under Linux to avoid this issue.
As for me, I just ignored the issue. By the time you reboot the bootloader, you are already rooted.
The only thing you do after the reboot is rename a file. For now I am missing that step...
Yeah I'm using windows xp. When its in boot loader it does change names. I can unlock the bootloader via fastboot but can't do anything with adb. Lol I don't know what else I can do, I'm at a loss.
kevlars9 said:
Yeah I'm using windows xp. When its in boot loader it does change names. I can unlock the bootloader via fastboot but can't do anything with adb. Lol I don't know what else I can do, I'm at a loss.
Click to expand...
Click to collapse
Like I said - I think you are done...
Install a terminal on the Nexus and see what it says to "su". I use one called "terminal emulator". Works fine.
I think fastboot uses adb.
If you connect your Nexus, and type "adb devices" in a command window what does it say?
I believe it says devices attached or something like that. (Not at my computer) but doesn't give me a serial # like I think it should.
If you do not have USB Debugging checked, "adb devices" will just show the List of devices line.
If I set USB debugging on, "adb devices" also shows the Nexus serial number.
If you don't see that, I would double check the device driver you are using.
Under Device Manager, Android Phone, Android Composite ADB Interface it shows:
Driver: Google Inc.
Date: 5/24/2012
Version: 6.0.0.0
Digital Signer: google inc.
Well if I have USB debugging on and tablet on and do adb devices I get the serial # but once I go into boot loader and do adb devices I don't get the serial #.
For device manager I can choose adb interface or adb original interface. I'll have more info when I get out of work and at my computer. Do you have a link to the drivers you used? Or where to find them. Because I have tried a couple of different drivers posted around to no avail.
BTW thanks for helping me out.
I would not use any posted driver - you don't know where that thing has been.
Download the SDK from Google; the correct driver is in there.
Just point the device manager to it when you install drivers.
There are a lot of good descriptions on installing drivers in the other nexus forums
But - again - I think your device driver is fine. You will not be able to talk to the Nexus from ADB after you boot the bootloader
Bootloader has a different device name which ADB can't use under Windows.
Use Linux if you want to do that.
ok, so pretty much what happens is when my tablet is powered on with usb debugging everything is fine and ADB is recognized. Now my problem seems to be when i reboot into the bootloader it seems as though the drivers dont stick and it asks me to install the drivers again and this is where i have had all of my issues. When i type in adb devices in, it just tells me "list of devices attached" and wont let me do anything else (fastboot works). Like i said i was able to unlock my bootloader but i cant flash recovery or do anything else.
When i go into device manage to select the drivers it gives me the option of choosing between adb interface, adb bootloader interface, adb orignal interface and nexus 7 bootloader interface. I have tried all options and nothing seems to work. I have tried multiple usb cords and ports.
If anyone else has any suggestions it would be much appreciated.
I didn't read through everything but your initial problem is adb doesn't work in the bootloader that's where you use fastboot commands either boot into a custom recovery or just boot up normal and make sure debugging is checked.
Try running fastboot devices and see if it shows up. What you need to do is have bootloader unlocked and dismiss the super user zip floating around here pot that on sd card download cwm recovery image floating around boot into bootloader then
fastboot devices
fastboot flash recovery name_of_file.img
fastboot reboot bootloader
select recovery from the menu
Flash the super user zip
Or download a rom that has root and put that on sd card instead of super user zip and after doing the steps above then selecting super user zip select the rom you downloaded and flash. If you're on Linux run sudo first.
Sent from my Galaxy Nexus using xda premium
Delete
After I got my new nexus, I decided to root it. I used mskips toolkit with 4.1 and it worked like a beaut. But I can't for the life of me root 4.1.2.
Checklist:
Downloaded the drivers succesfully
Can enter ADB succesfully. Under device manager it says "Google Nexus 7 ADB interface"
Tried WugFresh's toolkit
Unlocked bootloader
Tried installing custom recovery (see below)
(Checklist to know what I have done, for people to help me and future people with problems)
The reason adding CWM or TWRP doesn't work is because the device can't be rooted. You need to be rooted to change recovery file names, and whenever I boot recovery, I get the dead android and a red ! (stock recovery).
When it sees if busybox is installed, and sends the command, it comes back negative.
I'm having the exact same problem -- generating the same set of error messages as you show at the top of your screen capture. I bought a new Nexus 7 32GB and updated it to 4.1.2 before trying to root it. At the time I hadn't read anything that told me this might be a bad idea. I figured -- update to the latest version then root it. I've tried changing how I have it connected (media or camera), what USB port I connect to, what USB cable I use, which boot options I select -- NOTHING makes a difference. I have gotten my bootloader to unlock, or so it seems, as I've got the unlocked padlock image during boot up. But I'm totally stuck on how to proceed to get root.
lesdense said:
I'm having the exact same problem -- generating the same set of error messages as you show at the top of your screen capture. I bought a new Nexus 7 32GB and updated it to 4.1.2 before trying to root it. At the time I hadn't read anything that told me this might be a bad idea. I figured -- update to the latest version then root it. I've tried changing how I have it connected (media or camera), what USB port I connect to, what USB cable I use, which boot options I select -- NOTHING makes a difference. I have gotten my bootloader to unlock, or so it seems, as I've got the unlocked padlock image during boot up. But I'm totally stuck on how to proceed to get root.
Click to expand...
Click to collapse
When you run wugs toolkit to root, does it reboot your nexus? I have not rooted a 32GB yet but I have done a 16GB on 4.1.2 factory image without any problems.
There is nothing different between rooting an 8/16GB unit versus the 32GB ones. Nor does 4.1.1 or 4.1.2 matter.
I bought a 32GB one a few days ago, upgraded to 4.1.2, and had the bootloader unlocked, custom recovery installed and device rooted in about 5 minutes.
The issues you are having are why I hate these "toolkits". They don't always work properly, and when they fail, the user has no idea what's going on. It's much better for people to actually perform the steps manually so that they understand what's going on behind the scenes. Because when you understand, you can better troubleshoot problems.
Based on the errors, it looks like the toolkit failed to remount /system as writable. As such, it couldn't push the APKs for superuser, nor make the su binary suid root. Which of course would break the rest of the install script.
It's a very simply process and doesn't need a toolkit. Use the android development toolkit tools adb and fastboot.
1) adb reboot bootloader
2) fastboot oem unlock
(select yes on tablet)
3) fastboot reboot-bootloader
(confirm bootloader is unlocked)
4) fastboot erase recovery
5) fastboot flash recovery <recovery.img>
(recovery.img should be a downloaded custom recovery file - CWM or TWRP, your choice).
6) Reboot into recovery
7) adb push <superuser.zip> /sdcard/superuser.zip
(superuser.zip should be whatever recovery flashable 'root' zip you want to use).
8) Using recovery, flash the zip file.
9) Reboot
10) Done.
phonic said:
There is nothing different between rooting an 8/16GB unit versus the 32GB ones. Nor does 4.1.1 or 4.1.2 matter.
I bought a 32GB one a few days ago, upgraded to 4.1.2, and had the bootloader unlocked, custom recovery installed and device rooted in about 5 minutes.
The issues you are having are why I hate these "toolkits". They don't always work properly, and when they fail, the user has no idea what's going on. It's much better for people to actually perform the steps manually so that they understand what's going on behind the scenes. Because when you understand, you can better troubleshoot problems.
Based on the errors, it looks like the toolkit failed to remount /system as writable. As such, it couldn't push the APKs for superuser, nor make the su binary suid root. Which of course would break the rest of the install script.
It's a very simply process and doesn't need a toolkit. Use the android development toolkit tools adb and fastboot.
1) adb reboot bootloader
2) fastboot oem unlock
(select yes on tablet)
3) fastboot reboot-bootloader
(confirm bootloader is unlocked)
4) fastboot erase recovery
5) fastboot flash recovery <recovery.img>
(recovery.img should be a downloaded custom recovery file - CWM or TWRP, your choice).
6) Reboot into recovery
7) adb push <superuser.zip> /sdcard/superuser.zip
(superuser.zip should be whatever recovery flashable 'root' zip you want to use).
8) Using recovery, flash the zip file.
9) Reboot
10) Done.
Click to expand...
Click to collapse
I agree with you, the problem of the tool kits, I experimented two of then
M, is that you are lost when something don't work, I lost hours and hours before understand it and do it by myself for 50 per cent .
Now that everything is good, I am very prudent with theses helpers,:good:
Since upgrading to Windows 8 the toolkit for android and pretty much the drivers are impossible to get working.
It seems that the device has nothing on it, zip, zero. No matter how I try to recover it what ROM it tried to install it didn't work and when I try to access anything via command prompt it can not find the device.
I look at the devices on system manager and there is one listed as unknown device but I do have android phone listed as a device.
It plugs in, makes a sound knowing there is something but its unknown. Tried using the Samsung drivers, no luck there.
I need to do a complete reboot, get the original folders back on but don't know how to get it to recognise and get things going again.
jozkam said:
Since upgrading to Windows 8 the toolkit for android and pretty much the drivers are impossible to get working.
It seems that the device has nothing on it, zip, zero. No matter how I try to recover it what ROM it tried to install it didn't work and when I try to access anything via command prompt it can not find the device.
I look at the devices on system manager and there is one listed as unknown device but I do have android phone listed as a device.
It plugs in, makes a sound knowing there is something but its unknown. Tried using the Samsung drivers, no luck there.
I need to do a complete reboot, get the original folders back on but don't know how to get it to recognise and get things going again.
Click to expand...
Click to collapse
You need to disable driver signing in windows 8 to be able to install drivers for the Nexus.
Done this already, for some strange reason the device listed in Device manager now knows its a adb interface but still listed as a unknown device.
Try getting to look at the Samsung drivers but still no luck.
When you go into the device properties it states the following;-
Windows has stopped this device because it has reported problems. (Code 43)
Windows 8 doesn't seem to work very well with adb/fastboot etc...
Do you have access to another computer that has Windows 7 (or XP, Linux?)?
Thanks for you help guys so far.
I do have a Vista 32bit laptop that I can use. Going to install the Toolkit, drivers etc on there and see how far it goes.
jozkam said:
Thanks for you help guys so far.
I do have a Vista 32bit laptop that I can use. Going to install the Toolkit, drivers etc on there and see how far it goes.
Click to expand...
Click to collapse
I've read where people who are using Win8 and fastboot flashing .img files to get back to stock, it stops/locks up in varying spots...after three hours of messing with it they try another OS (Win7, Linux) and it works within minutes.
Hopefully, Vista works...and I'm sorry you have to resort to Vista!
Well I seen to be getting somewhere but still with strange issues in Device Manager.
It shows Android device with the following devices below.
- Android Composite ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (working properly)
- Google Nexus 7 BootLoader Interface (yellow exclamation mark)
Further down I have Portable Devices with MTP Device listed (yellow exclamation mark).
I have Google Nexus Toolkit installed.
jozkam said:
Well I seen to be getting somewhere but still with strange issues in Device Manager.
It shows Android device with the following devices below.
- Android Composite ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (working properly)
- Google Nexus 7 BootLoader Interface (yellow exclamation mark)
Further down I have Portable Devices with MTP Device listed (yellow exclamation mark).
I have Google Nexus Toolkit installed.
Click to expand...
Click to collapse
Is this from your Vista machine or Win8 machine now?
RMarkwald said:
Is this from your Vista machine or Win8 machine now?
Click to expand...
Click to collapse
Vista machine.
jozkam said:
Vista machine.
Click to expand...
Click to collapse
Strange. Did you install the USB drivers? Maybe download them from Asus, extract them to your Desktop, right click on your N7 in Device Manager and unistall the drivers for your device, then connect your N7 and browse to the location of the downloaded USB drivers....?
Okay following God knows how many windows updates, following restart I can see that the MTP device is now showing as working properly.
When running the toolkit (version 3.2) it shows the device number at the top under ADB mode but not under Fastboot mode.
RMarkwald said:
Strange. Did you install the USB drivers? Maybe download them from Asus, extract them to your Desktop, right click on your N7 in Device Manager and unistall the drivers for your device, then connect your N7 and browse to the location of the downloaded USB drivers....?
Click to expand...
Click to collapse
Remind me which USB drivers?
Okay, puzzling but it appears to be getting somewhere.
In device manager there is one instance of Google Nexus 7 ADB Interface under Android Device and MTP Device under Portable Devices even though it seems to reinstall the same instance of MTP device every 1 minute or so.
I am installing the Samsung drivers however, the same as before when it comes to the Toolkit. The ADB mode list of devices shows correctly, nothing underneath fastboot mode.
What would be the next stage?
I would boot into fastboot, change directory to your Android SDK - Platform Tools directory, and if you type: fastboot devices
does anything show up?
Well, I would reflash stock images completely. Hopefully you have a backup of whatever is/was on your internal sd card because doing this will erase it.
You can get the image from here (note, I am assuming you have the N7 Wifi Only): https://developers.google.com/android/nexus/images#nakasi
Then, you can revert to stock by following this post: http://rootzwiki.com/topic/28544-guide-nexus-7-bootloadersrecoveriesrootback-to-stock/#entry764332
NOTE: Step 10 the file name will be different than shown.
Ok so I have managed to get into the ClockworkMod recovery v6.0.1.9, going with the 'install zip from sideload', used the command adb sideload nakasi-jop40c-factory-6aabb391.tar.
The screen on nexus says:
Restarting adbd...
Finding update package...
E: Cant open /tmp/update.zip
(bad)
Installation aborted.
Sorry about this I am a complete amateur when it comes to this stuff, thanks for the help so far.
UPDATE: - I used the CLEANROM 2.5 zip file and it has now gone back to its original state, YES, thank you so much.
This may have happened when I started to use Paranoid Android, they brought out a beta 5 version, which originally worked but I can't see to get it updated via the 'update recovery' step.
http://forum.xda-developers.com/showthread.php?t=1800268
Thanks once again.
RMarkwald said:
I would boot into fastboot, change directory to your Android SDK - Platform Tools directory, and if you type: fastboot devices
does anything show up?
Well, I would reflash stock images completely. Hopefully you have a backup of whatever is/was on your internal sd card because doing this will erase it.
You can get the image from here (note, I am assuming you have the N7 Wifi Only): https://developers.google.com/android/nexus/images#nakasi
Then, you can revert to stock by following this post: http://rootzwiki.com/topic/28544-guide-nexus-7-bootloadersrecoveriesrootback-to-stock/#entry764332
NOTE: Step 10 the file name will be different than shown.
Click to expand...
Click to collapse
Steps done, back to stock which is great, thanks a lot.
Oh man just when I thought my problems were finished.
One thing I forgot to do was run the superuser zip file to give permissions on the clockworkmod recovery. Even trying to do something with Rom Manager within jellybean itself but it says I need permissions.
How can I reverse back and get the superuser.zip from working? At the moment I can not access recovery, tried using command prompts and Rom Manager but to no avail.
jozkam said:
Oh man just when I thought my problems were finished.
One thing I forgot to do was run the superuser zip file to give permissions on the clockworkmod recovery. Even trying to do something with Rom Manager within jellybean itself but it says I need permissions.
How can I reverse back and get the superuser.zip from working? At the moment I can not access recovery, tried using command prompts and Rom Manager but to no avail.
Click to expand...
Click to collapse
You can boot back into fastboot, and download the latest TWRP Recovery from here: http://teamw.in/project/twrp2/103
They even give you instructions on the command to run type in: fastboot flash recovery <name of recovery file>
Put the .img file in your Android SDK - Platform Tools folder as well.
Type in the flash recovery command, then reboot to recovery.
From there, you can flash the Superuser.zip (I assume you have it?). If not, here it is: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip
You'll also want to make sure that the following files are deleted/removed:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
The reason being is that if they are there, it will reload the stock Android recovery at reboot, which will remove TWRP or CWM if you have flashed those. I would just rename them by putting a .bak on the end of the file names. But to do this, you'll need root first. You may have to: fastboot flash recovery, flash SuperSU zip, reboot, browse to those two locations to verify if those files exist/rename them, fastboot flash recovery again...reboot, and recovery may stick. When I went back to stock and fastboot flashed TWRP, I checked for those files and they weren't there, and recovery stuck just fine.
You're learning the manual way, congratulations! Not too bad is it?!
RMarkwald said:
You can boot back into fastboot, and download the latest TWRP Recovery from here: http://teamw.in/project/twrp2/103
They even give you instructions on the command to run type in: fastboot flash recovery <name of recovery file>
Put the .img file in your Android SDK - Platform Tools folder as well.
Type in the flash recovery command, then reboot to recovery.
From there, you can flash the Superuser.zip (I assume you have it?). If not, here it is: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip
You'll also want to make sure that the following files are deleted/removed:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
The reason being is that if they are there, it will reload the stock Android recovery at reboot, which will remove TWRP or CWM if you have flashed those. I would just rename them by putting a .bak on the end of the file names. But to do this, you'll need root first. You may have to: fastboot flash recovery, flash SuperSU zip, reboot, browse to those two locations to verify if those files exist/rename them, fastboot flash recovery again...reboot, and recovery may stick. When I went back to stock and fastboot flashed TWRP, I checked for those files and they weren't there, and recovery stuck just fine.
You're learning the manual way, congratulations! Not too bad is it?!
Click to expand...
Click to collapse
Wouldn't have got this far without you, really appreciate your help, now its stable with 2.54 Paranoid Android.
:good:
I got an N7 about a month ago on sale and the first thing I did was unlock the bootloader. I decided I was going to use it as a "learning" tablet. (I'm still in learning mode, with aspirations of dipping my toes into development - that's a ways away, though.) I flashed TWRP followed by a couple of roms, and then I decided I was going to test my ability to flash a factory image. So I flashed 4.4 (this was last week before the 4.4.2 images went up). And since I was on the back on the OTA path, I figured, "I have an unlocked bootloader. What's the worst thing that could happen if I took this update?" So I did.
And now I'm confused. If I remember correctly, with 4.2.2 (what it came with out of the box), the bootloader had an option to run in "fastboot mode." In 4.4.2, my options are basically Dead Android screen or (if I power+vol up):
Reboot system now
Apply update from ADB
Wipe data/factory reset
Wipe cache partition
Fastboot stopped recognizing my tablet (adb still works, though not in recovery - I didn't think it was supposed to, so I'm surprised to see it as an option). I know there were issues in the past with the USB drivers on x64 machines, but I've tried on both 32-bit XP and 64-bit Win 7 and both machines will recognize that there is an N7 when booted normally, but say there are issues with the drivers when booted into recovery. I searched and saw people using pdanet as a workaround for installing the USB drivers, but those posts were largely from 2011/2012 timeframe - I have the latest version of Android-SDK and thus the latest (I think) USB drivers, so I'm at a loss. Did Google/Android do away with Fastboot in KitKat? Even so, ADB doesn't recognize my tablet in recovery, so even if I wanted to sideload something I can't - did Asus release newer USB drivers that I should be using?
Any help anyone can provide would be greatly appreciated.
Thanks!
miss_sticks
miss_sticks said:
I have the latest version of Android-SDK and thus the latest (I think) USB drivers, so I'm at a loss. Did Google/Android do away with Fastboot in KitKat?
Click to expand...
Click to collapse
Are you sure to have updated all the drivers for your N7 after update of your SDK?
Weird thing about N7 is that one sometimes needs to re-installi all the drivers after flashing of another firmware. I've flashed a factory image (4.3) via fastboot on two N7s within the same hour. First N7 had 4.2.2 before, After flashing 4.3 on it, I took another N7 with 4.2.0 and- I had to re-install the drivers.
I never had such a situation with Samsung devices.
Just to make sure you're doing proper ADB prompts (I see you can get this far on your own):
Code:
adb
adb devices
[I]List of devices attached
[B]<your device's serial number should now be diplayed here> [/B][/I] device
adb reboot-bootloader
fastboot devices
[I]the following output should be returned at this point
[B]<your device's serial number should now be diplayed here>[/B] [/I] fastboot
If on the place in this code where bold letters are your device serial No doesn't appear, you have a driver problem (it isn't installed properly)
Sorry for posting ADB/fastboot prompts, I don't know which orders have you done.
tetakpatak said:
Just to make sure you're doing proper ADB prompts (I see you can get this far on your own):
Code:
adb
adb devices
[I]List of devices attached
[B]<your device's serial number should now be diplayed here> [/B][/I] device
adb reboot-bootloader
fastboot devices
[I]the following output should be returned at this point
[B]<your device's serial number should now be diplayed here>[/B] [/I] fastboot
If on the place in this code where bold letters are your device serial No doesn't appear, you have a driver problem (it isn't installed properly)
Sorry for posting ADB/fastboot prompts, I don't know which orders have you done.
Click to expand...
Click to collapse
D'oh! Thank you so much for your help! I kept doing "adb reboot recovery" not "adb reboot-bootloader." Once I did that, everything was fine. I'm going to the corner to hang my head in newbie shame now. (But at least I'm now successfully running TWRP again.)
miss_sticks said:
D'oh! Thank you so much for your help! I kept doing "adb reboot recovery" not "adb reboot-bootloader." Once I did that, everything was fine. I'm going to the corner to hang my head in newbie shame now. (But at least I'm now successfully running TWRP again.)
Click to expand...
Click to collapse
OK, cool. Don't be ashamed, one just has to learn it
From that point on, (as you are in fastboot mode) your each prompt must begin with
Code:
fastboot (.....)
instead of "adb"
Don't ask me how this came about but I currently do not have a recovery on my phone.
The phone was running a rooted version of android 4.4.4 (paranoid android I think I had) and when android 5.0 came out I decided to flash it to my phone manually, to do this I used the tools available in android root tool kit. I think I messed it up a bit however as I have no recovery image on the phone.
I am now bored of running stock and want to flash a cyanogenmod ROM onto the phone - hence why I now need a recovery.
I can get my pc to recognise that a fastboot device is connected, but when I try the fastboot flash recovery <recovery.img> command it returns "could not load file". Even though the file is there in the path specified - I'd downloaded CWM recovery.
So I am not sure what I should do, can anyone help me?
I do not have my OEM cable and cannot get the PC to recognise an ADB device is connected, so a solution that gets round this problem would be useful. I'd rather not have to spend money on a new USB cable just for this purpose.
Thanks.
fredcorp6 said:
Don't ask me how this came about but I currently do not have a recovery on my phone.
The phone was running a rooted version of android 4.4.4 (paranoid android I think I had) and when android 5.0 came out I decided to flash it to my phone manually, to do this I used the tools available in android root tool kit. I think I messed it up a bit however as I have no recovery image on the phone.
I am now bored of running stock and want to flash a cyanogenmod ROM onto the phone - hence why I now need a recovery.
I can get my pc to recognise that a fastboot device is connected, but when I try the fastboot flash recovery <recovery.img> command it returns "could not load file". Even though the file is there in the path specified - I'd downloaded CWM recovery.
So I am not sure what I should do, can anyone help me?
I do not have my OEM cable and cannot get the PC to recognise an ADB device is connected, so a solution that gets round this problem would be useful. I'd rather not have to spend money on a new USB cable just for this purpose.
Thanks.
Click to expand...
Click to collapse
I would highly recommend Wug's Nexus Root Toolkit. It can automate any process you need. From what it sounds like it your post, you need to re-install TWRP. With the Nexus Root Toolkit, you can find that option under the "Root" section. Just check the box "Custom Recovery" and press the big "Root" button. Everything is very easy with this program. One thing I would recommend is that you get a very good USB to Micro USB to do this with. That is always the first point of failure in my experience. Good luck!