Okay, I bought a Nexus 10 off someone, and they had already rooted the device. Bootloader is unlocked and whatnot. That's where my problems start. I can not for the life of me get fastboot or adb to see this thing.
Here's my info:
Google Nexus 10 (Samsung)
ClockworkMod Recovery 6.0.4.3
Bootloader Version: MANTALJ12a
Windows 8.1 Pro x64
Full Android SDK
Samsung drivers installed (I rooted my Galaxy Nexus without issue).
USB has a direct connection
Before I decided to format and try to install a stock .zip, I could access the tablet as a media (That's how I got the .zip on the device).
Steps to how I got here:
Flashed Cyanogenmod 10.2 or whatever. Didn't want JB, wanted Lollipop.
Pushed the (what I thought was correct) .zip to /sdcard
Booted into recovery
Formatted /system, /cache, /data, /factory
Reflashed the .zip
Failed. Miserably.
I named the .zip as something simple and just overwrote it. I wouldn't have this issue if it wasn't for that. I know I did a bad there.
But still, nothing I can do will get fastboot/adb to see the device. It makes the sounds that it's connected when I plug it in. I'm using an elevated prompt as well, but it will not pull the device. How do I get myself out of this hole? If I could push a new .zip to somewhere on /sdcard I could at least use the recovery to reflash.
Wrong device ? [emoji14]
Khaon said:
Wrong device ? [emoji14]
Click to expand...
Click to collapse
No, I was going to put it in the general help thread, may be better here since this may not be a simple question (Please prove me wrong).
Some additional things I've tried:
The NExus Root Toolkit. Removing all drivers etc. Still getting to fastboot by PWR+ VOL+ + VOL-.
Still nothing. Should I go to my wife's computer and try it there? I might do that anyways.
gothmog1065 said:
Some additional things I've tried:
The NExus Root Toolkit. Removing all drivers etc. Still getting to fastboot by PWR+ VOL+ + VOL-.
Still nothing. Should I go to my wife's computer and try it there? I might do that anyways.
Click to expand...
Click to collapse
You don't have access to have os then? How did you push your zip if you don't have access to adb?
I have seen people who couldn't get adb and fastboot working on their windows and switching to another computer solved the issues.
Ok, make sure to make a full clean of your drivers. Wug toolkit explain how to. Then install proper samsung driver and this
If it is not a hardware's problem, you should have access to fastboot & adb. You might try on another computer if possible. A clean one would be the best (i.e. never used any droid devices, etc.).
Another workaround would be to use and otg cable and an usb drive with any zip of your liking.
Another one, I had an issue long time ago, similar, I had to flash through odin in downloading mode to fix my problems.
BUT did you really deleted /factory partition? It contains various proprietary files needed for the device to work. Well concerns more devices with imei and stuff to allow 3g connection and co. Might have no incidence tho on your device's behavior.
Khaon said:
You don't have access to have os then? How did you push your zip if you don't have access to adb?
Click to expand...
Click to collapse
Sorry if I wasn't clear on this, I have 100% access to my computer. I have the Android SDK installed, and adb/fastboot commands working in command prompt. They're just not seeing the tablet.
Ok, make sure to make a full clean of your drivers. Wug toolkit explain how to. Then install proper samsung driver and this
Click to expand...
Click to collapse
Yeah, that's one of the steps I did. Followed the Wug toolkit and removed everything. Still not seeing the tablet.
If it is not a hardware's problem, you should have access to fastboot & adb. You might try on another computer if possible. A clean one would be the best (i.e. never used any droid devices, etc.).
Click to expand...
Click to collapse
Yeah, seems to be doing the same on my wife's computer (Win 7 HP, never had my phone/tablet hooked to it). I get adb/fastboot loaded and working in the command prompt, and it registers when I plug in, but neither command will "see" the tablet.
Another workaround would be to use and otg cable and an usb drive with any zip of your liking.
Another one, I had an issue long time ago, similar, I had to flash through odin in downloading mode to fix my problems.
BUT did you really deleted /factory partition? It contains various proprietary files needed for the device to work. Well concerns more devices with imei and stuff to allow 3g connection and co. Might have no incidence tho on your device's behavior.
Click to expand...
Click to collapse
It's a Wifi tablet, no cellular data and IMEI etc.
edit: As a side note, I've been thinking about reformatting my computer, though it'll be a huge pain to get it back to here as I've got to go from 7 - 8.0 - 8.1 on the upgrade paths to get it back here again.
gothmog1065 said:
Sorry if I wasn't clear on this, I have 100% access to my computer. I have the Android SDK installed, and adb/fastboot commands working in command prompt. They're just not seeing the tablet.
Click to expand...
Click to collapse
From my own experience, having similar issue with the windows drivers for adb, but eventually I fixed it. I really doubt you are screwed.
adb version output ? 1.0.32 is latest.
Yeah, that's one of the steps I did. Followed the Wug toolkit and removed everything. Still not seeing the tablet.
Click to expand...
Click to collapse
Installed universal adb drivers? Nothing shows up in the device manager?
Yeah, seems to be doing the same on my wife's computer (Win 7 HP, never had my phone/tablet hooked to it). I get adb/fastboot loaded and working in the command prompt, and it registers when I plug in, but neither command will "see" the tablet.
Click to expand...
Click to collapse
You might try odin.
Usb mtp doesn’t work from recovery?
Khaon said:
From my own experience, having similar issue with the windows drivers for adb, but eventually I fixed it. I really doubt you are screwed.
adb version output ? 1.0.32 is latest.
Installed universal adb drivers? Nothing shows up in the device manager?
?
Click to expand...
Click to collapse
Android Debug Bridge version 1.0.32, yep latest.
I just feel like I'm missing something, maybe something stupid. HOWEVER, I'm now getting my nexus 10 to show up in device manager with a ? on it. Already tried the direct Samsung drivers, the universal drivers in the Wug toolkit.
gothmog1065 said:
Android Debug Bridge version 1.0.32, yep latest.
I just feel like I'm missing something, maybe something stupid. HOWEVER, I'm now getting my nexus 10 to show up in device manager with a ? on it. Already tried the direct Samsung drivers, the universal drivers in the Wug toolkit.
Click to expand...
Click to collapse
Did you deleted all samsung vendor, etc from the usb program, you know what i am talking about?
You can force to install drivers from device maanger, don't remember how, when installing manually, you must do some step , install from floppy or file, get inf files or so, you will get a prompt telling you it might be harmfull and it will force installation. Might be the solution?
The culprit is definitely software-sided.
Does the mount internal storage (mtp) work?
Would this be easier in Linux? I could pop open my Ubuntu VM and do this if it'd be easier?
Beyond that, are you telling me to try and install the drivers from the driver files created by the Samsung vendor .exe?
I have tried to 'mount USB storage' from recovery, but it doesn't seem to do anything. /system /cache /data /factory are all mounted ATM and nothing is showing.
You've already got more advanced advice than I can offer but when I tried to update to 5.0.1 from 4.4.4, I couldn't get my windows computer to see my device. I was trying the adb fastboot but it I couldn't get it to work.
Wug's toolkit got it all straightened out (http://forum.xda-developers.com/showthread.php?t=2015467)[*]. There was an option on his interface that asked whether the device was working properly or not (a!most missed it as a choice). Checked that box and it went through much of the process I had done (installing adb, updating drivers etc). Long story short, it worked.
Where did you see this option? The only thing I see is the Soft Brick/Bootloop option where it will install the factory again. Was it that or somewhere else?
I swear to the Android droid that I tried that before. That seems to be doing what needs to be done, holy crap thanks!
e: I would like to know, however, why fastboot/adp wouldn't work but this would without doing any of the other stuff?
gothmog1065 said:
Where did you see this option? The only thing I see is the Soft Brick/Bootloop option where it will install the factory again. Was it that or somewhere else?
I swear to the Android droid that I tried that before. That seems to be doing what needs to be done, holy crap thanks!
e: I would like to know, however, why fastboot/adp wouldn't work but this would without doing any of the other stuff?
Click to expand...
Click to collapse
You're right. I confused the heading but choosing that option got my computer and my Nexus "talking." After installing the factory image I think you can then push a cusom ROM to you Nexus (http://forums.androidcentral.com/go...acks/264619-wugs-nexus-toolkit-questions.html).
gothmog1065 said:
Where did you see this option? The only thing I see is the Soft Brick/Bootloop option where it will install the factory again. Was it that or somewhere else?
I swear to the Android droid that I tried that before. That seems to be doing what needs to be done, holy crap thanks!
e: I would like to know, however, why fastboot/adp wouldn't work but this would without doing any of the other stuff?
Click to expand...
Click to collapse
Problem solved ? I always had less issues with fastboot and adb on Linux you can install a ppa that install for you adb and fastboot
Hovewer if you are using 2.8.2.0 you will need 1.0.32 and the ppa includes 1.0.31 so only adb sideload fails.
Sent from my nexus 10
Related
so i am new to android and i decided " hey why don't i try to root my nexus" so i tried and i cant get any father that checking if the computer can see my device which it cant for some reason. so i went online i figured out that i don't have the usb driver for android. so after that i tried to down load then and i even installed them and restarted my computer and it still wont work. so if any one can help me with my problem it would be greatly appreciated.
On Home Screen, press menu>settings>applications>development and make sure USB debugging is checked.
What OS you running?
Specs would help, where did you get your drivers? What other software have you tried?
i turned on the debugging and it still hasnt worked
i am running xp. i downloaded the android sdk from here
developer.android.com
i just want to put the modaco desire rom on my phone that my onl reason for wanting to root. i really like the sense ui
I am having a similar problem, so i might as well use this thread instead of creating a new one.
I have a dual boot computer, win7 and fedora, both have SDK. I unlocked my nexus one with windows, as i noticed the commands were considerably easier, or at least they don't work when i plug the linux ones into fedora.
Last night i was going to push the undervolt kernel so i plugged my n1 while in win7, It instantly came up complaining about drivers, which i had already installed and had previously worked, i went to re-install them, and windows says they are up to date, but still no luck recognising the device (Debugging mode is definately on)
So i switched to fedora, no driver pop ups obviously, but when i try to push the kernel through, it does not recognise the device.
In the bootloader it says "fastboot usb" while plugged in.
I can't pinpoint when it stopped working, but the last time i used fastboot was to put the RA recovery, since then i flashed CM 5.0.2, CM 5.0.3.1, the desire rom, and used a nandroid restore to get back to 5.0.3.1
Anyone got any ideas? Without fastboot i am pretty much restricted to flashing .zip files from the recovery.
yeah i cant even unlock mine its so frustrating
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
drbrendin said:
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
I tried all day too like a gazillion times.... and wonder does everyone have driver issues? I tried with my XP computer and windows 7, no go, then I read posts people having the same issue, then they just post " nevermind got it" and didn't even write what they did to get it.......
Click to expand...
Click to collapse
not everyone is a dev
Ok, I have my Nexus One set up so I can use with via Windows 7 (desktop) or Ubuntu (Laptop).
The Linux part is a bit more involved, but since everyone is running Windows (unless I missed something), I will work there.
First of all, your phone needs to be in Dev mode (which was covered earlier).
With the phone UNPLUGGED from the PC, uninstall any previous SDK installs you have and be sure to remove the directory.
Then, install the SDK found here: SDK
Install this SDK and let it complete the install, which will include downloading for a bit. You need to do this since the SDK package above does NOT include the right drivers!!!
Once this has been completed, plug your phone into the computer via USB. Your computer will find a new device, however, it cannot locate the drivers for it. Browse and point the installer to:
DRIVE:\PATH_TO_android-sdk-windows\usb_driver
Don't go any further than this!!
Now, let it do it's thing and you should have a new device in the device manager called:
Android Phone
...|_Android Composite ADB Interface
Now, go to the command prompt and change to the following directory:
DRIVE:\PATH_TO_android-sdk-windows\tools
There, you will find adb.exe
Type:
adb devices
and you should see:
List of devices attached
HT019P801614 device
If not, something got screwed up and would need to dig further to help ya.
Ok ill give this a try once get home from school
nexus one root.
Ok assuming that you have the android sdk installed correctly, try rooting your phone via the superboot method. The first link below has a full detailed guide for rooting the nexus one and I believe has all of the device drivers for those who have not been able to get them running well. If you still have trouble getting the drivers working checkout the second link. Anyone who is relatively new to working with the sdk and is not familiar with working the commands check out the third link. Read the entire thread! it is very helpful.
1) http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
2) http://forum.xda-developers.com/showthread.php?t=613217
3) http://forum.xda-developers.com/showthread.php?t=619153
If you have any questions PM me on xda. I'll try and help in anyway, it took my like two days to actually root my nexus, I wasnt familiar with using ADB and Fastboot to root.
One thing I know I was having problems with since I came from the G1 was that the new SDK has to actually be installed via an .exe now. I was used to it all being in a zip so I kept trying to load up what I thought were the right USB drivers, but they were actually the 1.6 drivers I already had. So make sure to run the .exe that comes with the SDK.
ok so while i was downloading the sdk a notification came up that said that it could not rename the directory. is this bad?
i am having an issue with installing the right driver as well. my computer keeps installing the nexus one as a "mass storage device". i have uninstalled and reinstalled a few times but no luck. i have the phone set to debug mode, using XP btw. any help would be appreciated.
Im trying to root my nexus 7 what exactly am i supposed to do to achieve that?
i got this error adb offline and it's screwing with the rooting process
i upgraded to 4.2.2 yesterday help me achieve rootness
also am i suppose to unlock my nexus before rooting it.:victory:
Hello there, have you unlocked your bootloader?
Also have you installed the correct drivers?
And is USB debugging mode enabled on your nexus?
how to do that?
compty said:
Hello there, have you unlocked your bootloader?
Also have you installed the correct drivers?
And is USB debugging mode enabled on your nexus?
Click to expand...
Click to collapse
how to unlock bootloader 4.2.2?
yes usb debugging is enabled
I assume you are using Google Nexus 7 Toolkit?
If so there should be an option which says unlock bootloader.
google toolkit error trying to unlock
compty said:
I assume you are using Google Nexus 7 Toolkit?
If so there should be an option which says unlock bootloader.
Click to expand...
Click to collapse
Oh yeah sorry about that however when I try to unlock the error adb devices offline comes also it can't find adb anywhere even when my nexus is on normally
Same problem
leo9252 said:
Oh yeah sorry about that however when I try to unlock the error adb devices offline comes also it can't find adb anywhere even when my nexus is on normally
Click to expand...
Click to collapse
I feel your pain as I too am having the same problem. I am posting on here so I can easily follow your post. I will tell you also that I think it has something to do with 4.2.2 but not positive at this point. I have rooted a Nexus One, HTC Dream, SGH679, so I do have some experience with this. I have changed ports, cables, started and stopped the service, rebooted the tablet, toggled the debugging just keep getting the offline. When I plug my phone in and use it, it sees it and it works fine, then when I plug the tablet back in it go back to offline. I even removed all the drivers on the computer just so it would get confused with the phone driver and still no luck. I think the driver is fine tho because it says it is in device manager, and I can transfer files back and forth from my tablet to my computer. Don't loose heart tho I think the answer is out there and I will keep working on it, and checking back to see if anyone else has had success.
Have you tried updating the data files in NexusRootToolkit?
http://forum.xda-developers.com/showthread.php?p=37955981#post37955981
further problems
sicameron32 said:
I feel your pain as I too am having the same problem. I am posting on here so I can easily follow your post. I will tell you also that I think it has something to do with 4.2.2 but not positive at this point. I have rooted a Nexus One, HTC Dream, SGH679, so I do have some experience with this. I have changed ports, cables, started and stopped the service, rebooted the tablet, toggled the debugging just keep getting the offline. When I plug my phone in and use it, it sees it and it works fine, then when I plug the tablet back in it go back to offline. I even removed all the drivers on the computer just so it would get confused with the phone driver and still no luck. I think the driver is fine tho because it says it is in device manager, and I can transfer files back and forth from my tablet to my computer. Don't loose heart tho I think the answer is out there and I will keep working on it, and checking back to see if anyone else has had success.
Click to expand...
Click to collapse
So I was going to do it the old fasion way by following this guide
http://forum.xda-developers.com/showthread.php?t=2150661
I didn't quite get step four because the nexus 7 doesn't have an SDcard, but I copied the zip to the root of the device.
When I did step 7 the device did not go to Fastboot, it didn't go anywhere other than a black screen. I think I have a faulty unit, or the holding of the volume buttons with the power is really not the way to get to fastboot, either way I am looking at a brick right now. Any thoughts will be welcome. I messed around with it for 10 min now and got the device to re-boot. Not sure if I should try the fast boot option again.
Are you on Windows 8 by any chance?
Because I couldn't get it to work on Windows 8 and had to use Windows 7.
You must update adb command from here:
http://forum.xda-developers.com/showthread.php?t=1766475&page=251
JB 4.2.2 is asking for debugging PC white list, please enable and allow it when prompt. Check here.
http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/
I got exactly the same problem and now it works for me.
everyone i got it working! adb offline fixed
It took me a while but I finally fixed it! Here's what I did I went crazy and searched all over the web with the keywords adb offline nexus 7 4.2.2 I then found a website that related to my issue it said to update SDK manager so I downloaded the manager then found android 4.2 next downloaded all that was under the 4.2 package and next downloaded the extra packages next thing I knew I plugged in my nexus and on it on the screen it told to choose yes or no on USB debugging and that's all you have to do to fix the problem of the adb offline bullstuff. I hope you guys will be able to understand what I'm writing to you. I also use windows 7 for this.
leo9252 said:
It took me a while but I finally fixed it! Here's what I did I went crazy and searched all over the web with the keywords adb offline nexus 7 4.2.2 I then found a website that related to my issue it said to update SDK manager so I downloaded the manager then found android 4.2 next downloaded all that was under the 4.2 package and next downloaded the extra packages next thing I knew I plugged in my nexus and on it on the screen it told to choose yes or no on USB debugging and that's all you have to do to fix the problem of the adb offline bullstuff. I hope you guys will be able to understand what I'm writing to you. I also use windows 7 for this.
Click to expand...
Click to collapse
It won't let me download and install anything from the 4.2 list...did you do anything else?
myleb said:
You must update adb command from here:
http://forum.xda-developers.com/showthread.php?t=1766475&page=251
JB 4.2.2 is asking for debugging PC white list, please enable and allow it when prompt. Check here.
http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/
I got exactly the same problem and now it works for me.
Click to expand...
Click to collapse
FWIW, here is my experience:
PC: Win7 Pro x64 SP1 - SDK platform-tools 16.0.1 - SDK Tools 21.1 - ADB v 1.0.31
N7: JDQ39 Stock *
( *OK, i diddled default.prop in my boot image to set "ro.secure =0". I don't know if that could make a difference or not )
The Nexus 7 asks for confirmation of inbound adb sessions for every new adb server invocation on the client PC.
When it does ask for credentials, you have to get to the on-screen display pretty quickly - a couple of seconds at most. If you don't the device will be reported as "offline" by the first invocation of
adb devices
If you accept the connection, the next time you run "adb devices", the status is back to normal (reports "device" instead of "offline").
You can test this out yourself - just iterate in a loop these three commands:
adb devices
adb devices
adb kill-server
Nothing that can't be understood by someone who knows what is going on; but I suppose that all the toolkits are running adb underneath the hood, so it is certainly possible to get tripped up when using a toolkit if you aren't Jhonny-on-the-Spot when that dialog pops up on the tablet.
Also, for the adventuresome:
I note that the new stock JDQ39 (4.2.2) ramdisk has a new line in the default.prop that was not in JOP40D (4.2.1) :
Code:
ro.adb.secure=1
I suppose that could be toggled off if you have a favorite kernel/ramdisk setup and you don't want to be bothered by this stuff. But it does mean unpacking/repacking your boot images.
cheers
I'm having the same problem. Never recognizes an ADB device. When it does it shows my serial number followed by "offline."
Any ideas? I'm ready to return this thing.
---------- Post added at 08:28 PM ---------- Previous post was at 08:16 PM ----------
Out of curiousity what driver are you using and how are you installing it?
Also where is your device coming up in the device manager?
I've tried so many things that I think I'm getting off track. Sadly my motorola phones were much easier to root.
how come you cant?
LucentBirch said:
It won't let me download and install anything from the 4.2 list...did you do anything else?
Click to expand...
Click to collapse
How come you can't download and install from the SDK manager?
That's how my problem got fixed.
Worked
jibdev said:
Have you tried updating the data files in NexusRootToolkit?
http://forum.xda-developers.com/showthread.php?p=37955981#post37955981
Click to expand...
Click to collapse
Thank you.... this worked first time go! So happy!
Thanks to all involved.... This is by far the most useful forum for phones.
you're welcome
sicameron32 said:
Thank you.... this worked first time go! So happy!
Thanks to all involved.... This is by far the most useful forum for phones.
Click to expand...
Click to collapse
I knew someone would find this useful.
:laugh::good:
leo9252 said:
I knew someone would find this useful.
:laugh::good:
Click to expand...
Click to collapse
The sad thing is I have no idea what finally got it to work. Maybe just an extra reboot I had forgotten at some point. I do know however that I had to add a few extra lines (hardware ID) to the .inf file in the usb driver. Not sure which did the trick. I also used a combo of the toolkit to unlock and the manual method to root. Also I am unable to boot my device into the bootloader/fastboot via windows and rather have to manually (physically) shut down the device and enter the bootloader via the physical buttons. Probably an issue with the windows drivers again, but at least I have full functionality once in fastboot.
Only thing is now I can't get access to the storage via windows. And there's no way in hell I want to change the ADB drivers without knowing which finally worked for me. I'm thinking though that this is an entirely different device in device manager (I'm obviously not that knowledgeable).
Also I'm kinda annoyed by the unlocked padlock symbol on startup. I suppose that should be a welcome sign of achievement after spending all day trying to unlock/root, especially for such an unlearned person as myself.
did you clear this issue?
leo9252 said:
Im trying to root my nexus 7 what exactly am i supposed to do to achieve that?
i got this error adb offline and it's screwing with the rooting process
i upgraded to 4.2.2 yesterday help me achieve rootness
also am i suppose to unlock my nexus before rooting it.:victory:
Click to expand...
Click to collapse
if not, pls gimme a mesg.
cause I'm a noob, I cannot use link here. :crying:
This issue is included in 4.2.2, and ADB is disabled by default for security.
I tested on my Nexus 4, 4.2.2 running. :fingers-crossed:
Okey. So to summarise: there is this new security feature in android 4.2. that makes the device show a popup if you want to allow the connected computer to use the adb = debugging bridge. But for this to work, you need to have the newest adb binary, which needs to print 1.0.31 when you run "adb version"
(found that info here --> http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/ )
Under linux when you try to do it the old-school google-recommended way and download the huge "adt-bundle-linux-x86_64-20130219" and use the "android" tool to find new updates to the platform tools, it will tell you you already got the latest version which is rev 16.0.2 which contains an adb binary which will print version 1.0.26 which will not work with this new android 4.2.2 security feature.
So after searching for a linux adb 1.0.31 binary, I found it here:
https://github.com/mozilla/r2d2b2g/commit/2eefcc05366173ca51635da8f542fd8473ba0fea -->
https://ftp.mozilla.org/pub/mozilla.org/labs/r2d2b2g/adb-1.0.31-linux.zip
with that binary I finally can use adb on my nexus 7 again.
Earlier, I did a wipe of my tablet and wanted to install a ROM through recovery, but using the mount function from TWRP is a no-go.
When I click the Mount button, it takes me to a list of which directories to mount, but nothing else. In the lists of available drives under Computer, my tablet is not listed.
What do?
Unfortunately, I don't know how to push through ADB or do an ADB sideload, so if anyone can walk me through that process, I'd be forever grateful.
Update: Got adb to work, but I can't get my PC to recognize that my device is plugged in.
I know for a fact that the problem lies on the device side rather than the PC side, so how do I fanangle my N7 to get recognized by my comp?
Did you really flashed correct twrp version for your n7?
So, I just did a crash course on how to use ADB and just flashed to stock.
Hopefully, I'll have no problems afterward.
Hexm.xx said:
So, I just did a crash course on how to use ADB and just flashed to stock.
Hopefully, I'll have no problems afterward.
Click to expand...
Click to collapse
Otherwise try to get the drivers installed manually just search Google for Nexus 7 fastboot drivers and here is a little help for you installing Roms like ubuntu (touch): http://forum.xda-developers.com/showthread.php?p=46823947#post46823947
I've been trying to sideload the lollipop ota since yesterday and after 10 hours of failing, I've finally got it running. The problems I got during the period including adb driver errors, recovery errors, and my USB ports problem.
Here are some tips for the other if facing a lot of problem sideloading the lollipop ota zip.
-Use Windows if possible. I tried using Ubuntu but adb won't work correctly. Even sometimes it works, fastboot fails. Use Windows and install the drivers needed namely Google USB Driver. It can be found on Android official website.
-Plug your device directly to the motherboard. Etc. back USB port. My desktop defective front USB ports caused me the most time as Windows/Ubuntu won't work correctly with them. Windows shows USB malfunction.
-Custom recoveries won't work. I tried twrp and cwm. They won't work. They show incompatible build fingerprint/user release keys. Flash stock recovery. I tried wugfresh but can't figure out how to use it so I have it up and flash with adb in Windows. Of course you need to install the drivers properly.
-If adb/fastboot can't detect device in os/bootloader/sideload/recovery/whatever mode, most probably drivers aren't installed correctly. Google the problem and you'll find solutions to it. It's out there and you can find it.
-Check the index thread in the general forum for useful tools/image/utilities
-Sideloading is quite easy if you have drivers installed correctly assuming you have no hardware problems (defective USB port)
Those are most of the problems I faced when trying to sideload ota. Hope this helps those who are facing same problem as me.
ImjuzCY said:
I've been trying to sideload the lollipop ota since yesterday and after 10 hours of failing, I've finally got it running. The problems I got during the period including adb driver errors, recovery errors, and my USB ports problem.
Here are some tips for the other if facing a lot of problem sideloading the lollipop ota zip.
-Use Windows if possible. I tried using Ubuntu but adb won't work correctly. Even sometimes it works, fastboot fails. Use Windows and install the drivers needed namely Google USB Driver. It can be found on Android official website.
-Plug your device directly to the motherboard. Etc. back USB port. My desktop defective front USB ports caused me the most time as Windows/Ubuntu won't work correctly with them. Windows shows USB malfunction.
-Custom recoveries won't work. I tried twrp and cwm. They won't work. They show incompatible build fingerprint/user release keys. Flash stock recovery. I tried wugfresh but can't figure out how to use it so I have it up and flash with adb in Windows. Of course you need to install the drivers properly.
-If adb/fastboot can't detect device in os/bootloader/sideload/recovery/whatever mode, most probably drivers aren't installed correctly. Google the problem and you'll find solutions to it. It's out there and you can find it.
-Check the index thread in the general forum for useful tools/image/utilities
-Sideloading is quite easy if you have drivers installed correctly assuming you have no hardware problems (defective USB port)
Those are most of the problems I faced when trying to sideload ota. Hope this helps those who are facing same problem as me.
Click to expand...
Click to collapse
Sounds like you need you need to save what every data you can if you can through recovery to maybe an OTG adapter.. Then go ahead and Completely WIPE your Nexus. Follow the instructions and download the Android Lolipop LRX31P image, and all the other files needed to properly root your device.. Flash to Stock+Unroot, then once finished reboot and put in your email and settings, download all your backed up apps.. Then once finished, then go back to the Nexus Toolkit by Wugsfresh, and use the tool to root the device, it will put your device into Booloader/Fastboot, and let it do its thing.. Make sure you have USB debugging selected..
If you have a custom kernel on your current rom, it will not sideload.. if you made any changes, if its rooted it will not OTA.. You need to flash to Stock Android 5.0 and go through the motions.... I was on Carbon Rom 4.4.4, and went through the paces, and gave me no issue.. It just takes about 5 or so mins at first boot.. So if it seems to hang.. don't worry.. Just let it do its thing, put in your email info and there you go.. The tool is dummy proof.. even if you soft brick the device, you can use the Advanced Utilities while manually booting into Fastboot/Bootloader mode..
Edit: also make sure you have the correct ADB drivers.. The took kit has those drivers, just follow the instructions, and you should have ADB, or you can flash manually through fast boot if you select your device as soft bricked.. I had the same problem when I first tried to side load an OTA..
Good luck
Zaphodspeaks said:
Sounds like you need you need to save what every data you can if you can through recovery to maybe an OTG adapter.. Then go ahead and Completely WIPE your Nexus. Follow the instructions and download the Android Lolipop LRX31P image, and all the other files needed to properly root your device.. Flash to Stock+Unroot, then once finished reboot and put in your email and settings, download all your backed up apps.. Then once finished, then go back to the Nexus Toolkit by Wugsfresh, and use the tool to root the device, it will put your device into Booloader/Fastboot, and let it do its thing.. Make sure you have USB debugging selected..
If you have a custom kernel on your current rom, it will not sideload.. if you made any changes, if its rooted it will not OTA.. You need to flash to Stock Android 5.0 and go through the motions.... I was on Carbon Rom 4.4.4, and went through the paces, and gave me no issue.. It just takes about 5 or so mins at first boot.. So if it seems to hang.. don't worry.. Just let it do its thing, put in your email info and there you go.. The tool is dummy proof.. even if you soft brick the device, you can use the Advanced Utilities while manually booting into Fastboot/Bootloader mode..
Edit: also make sure you have the correct ADB drivers.. The took kit has those drivers, just follow the instructions, and you should have ADB, or you can flash manually through fast boot if you select your device as soft bricked.. I had the same problem when I first tried to side load an OTA..
Good luck
Click to expand...
Click to collapse
Oops you misunderstood my post. I've done sideloading 5.0 and its running now before i post this thread. This thread i created is meant to give help to those who need it. Everythings running good for me right now. I successfully flashed stock recovery through adb and after that sideloading ran smoothly. Those problem written above is those problems i faced during it and now i already solved the problem and 5.0 is already running without full wipe. Thanks anyway
ImjuzCY said:
Oops you misunderstood my post. I've done sideloading 5.0 and its running now before i post this thread. This thread i created is meant to give help to those who need it. Everythings running good for me right now. I successfully flashed stock recovery through adb and after that sideloading ran smoothly. Those problem written above is those problems i faced during it and now i already solved the problem and 5.0 is already running without full wipe. Thanks anyway
Click to expand...
Click to collapse
Because of how Lolipop handles file location, I recommend doing a complete factory reset/wipe..
But if its working for you.. Thats alright.. But Android 5.0 handles the SDcard Location in a different area.. Something to do with the multiple profile ability I believe.
Zaphodspeaks said:
Because of how Lolipop handles file location, I recommend doing a complete factory reset/wipe..
But if its working for you.. Thats alright.. But Android 5.0 handles the SDcard Location in a different area.. Something to do with the multiple profile ability I believe.
Click to expand...
Click to collapse
You mean internal storage? I dont think nexus devices have an external microsd slot. Thanks for the suggestion anyway. I will do a factory reset if problems starts to bug me.
ImjuzCY said:
You mean internal storage? I dont think nexus devices have an external microsd slot. Thanks for the suggestion anyway. I will do a factory reset if problems starts to bug me.
Click to expand...
Click to collapse
Yes internal storage.. and yes a factory reset would correct that problem..
That just defeats the whole sideload thing, where you could just do a Titanium backup first, restore Data only when needed. Just install the factory image, and restore the Titanium back up... not the app, but the Data becaus the app will crash.. Its the easiest way to save your settings in your Launcher and your apps..
Its too much trouble to sideload when your rooted, with a custom Kernel.... you wasted 10 hours, when it could of taken less than 10 mins
Zaphodspeaks said:
Yes internal storage.. and yes a factory reset would correct that problem..
That just defeats the whole sideload thing, where you could just do a Titanium backup first, restore Data only when needed. Just install the factory image, and restore the Titanium back up... not the app, but the Data becaus the app will crash.. Its the easiest way to save your settings in your Launcher and your apps..
Its too much trouble to sideload when your rooted, with a custom Kernel.... you wasted 10 hours, when it could of taken less than 10 mins
Click to expand...
Click to collapse
Luckily i was using stock kernel. Ive disabled root beforehand and the problems i faced was all on the pc side. Evrything should be easy if my pc doesnt show so much problems. And i like to take challenges so i chose to sideload haha
I started this thread: (https://forum.xda-developers.com/axon-7/help/help-loss-root-twrp-t3781054)
a while back and ended up never solving my issue, eventually giving up and living with an unrooted phone.
Anyhow I've been trying again to get to the bottom of the issue and after another day of fruitless research here I am hoping to bring it back to your attention.
Does anyone around here regularly use a mac to perform adb commands? I'd love to get some help trying to get fastboot working again.
Should I just give up and find a Windows computer to do this?
Thanks for reading
alajoy said:
I started this thread: (https://forum.xda-developers.com/axon-7/help/help-loss-root-twrp-t3781054)
a while back and ended up never solving my issue, eventually giving up and living with an unrooted phone.
Anyhow I've been trying again to get to the bottom of the issue and after another day of fruitless research here I am hoping to bring it back to your attention.
Does anyone around here regularly use a mac to perform adb commands? I'd love to get some help trying to get fastboot working again.
Should I just give up and find a Windows computer to do this?
Thanks for reading
Click to expand...
Click to collapse
That guy was horribly wrong and sorry you had to live with an unrooted phone for so long. But in newer versions of Nougat (i think B32 or B35) they removed fastboot and you could not boot into it. I have a way of being able to install TWRP here without fastboot (assuming you're on an Oreo bootstack, otherwise you can do almost everything in that thread except use a TWRP for Nougat instead). I haven't tried this, but if you have stock recovery, try downgrading to Nougat B19 by using an official SD card update and using apply update from SD card in stock recovery. Haven't found an official SD card update for you but I've only done a little bit of searching.
edit: ive only found B19 Nougat full image , but here: https://mega.nz/#F!kYtRAJjJ!5tD1zPpo0nw2tJwhANA9pQ!tNsQhD5Y
download A2017U-7.1.1-B19-Full-326200B1901A2017UV1.1.0B19.zip and extract it and put update.zip in your sd card. boot into stock recovery and use apply update from sd card and select it. hopefully it works and it will downgrade
Teet1 said:
That guy was horribly wrong and sorry you had to live with an unrooted phone for so long. But in newer versions of Nougat (i think B32 or B35) they removed fastboot and you could not boot into it. I have a way of being able to install TWRP here without fastboot (assuming you're on an Oreo bootstack, otherwise you can do almost everything in that thread except use a TWRP for Nougat instead). I haven't tried this, but if you have stock recovery, try downgrading to Nougat B19 by using an official SD card update and using apply update from SD card in stock recovery. Haven't found an official SD card update for you but I've only done a little bit of searching.
edit: ive only found B19 Nougat full image , but here: https://mega.nz/#F!kYtRAJjJ!5tD1zPpo0nw2tJwhANA9pQ!tNsQhD5Y
download A2017U-7.1.1-B19-Full-326200B1901A2017UV1.1.0B19.zip and extract it and put update.zip in your sd card. boot into stock recovery and use apply update from sd card and select it. hopefully it works and it will downgrade
Click to expand...
Click to collapse
Thank you so much for responding.
So I finally went out and bought an sd card yesterday to try this and I am having no luck.
I tried unzipping the file, but it just creates a duplicate zip file so I simply tried installing the whole package.
Wether I try and install via sd card or via sideload/adb I get the same "installation aborted" message.
This is so frustrating. All I want is to root again! I'm trying to get this phone to last me as long as I can before replacing it.
Doing this all on a Mac, fyi. Not sure if that changes things. Since we're not using EDL or Axon7toolkit I assumed it doesn't matter, but there is a lot that I don't know.
Thanks for any help that you're able to provide!
alajoy said:
Thank you so much for responding.
So I finally went out and bought an sd card yesterday to try this and I am having no luck.
I tried unzipping the file, but it just creates a duplicate zip file so I simply tried installing the whole package.
Wether I try and install via sd card or via sideload/adb I get the same "installation aborted" message.
This is so frustrating. All I want is to root again! I'm trying to get this phone to last me as long as I can before replacing it.
Doing this all on a Mac, fyi. Not sure if that changes things. Since we're not using EDL or Axon7toolkit I assumed it doesn't matter, but there is a lot that I don't know.
Thanks for any help that you're able to provide!
Click to expand...
Click to collapse
If it's saying that error then it's probably not letting you downgrade.
Also this might be slightly more difficult since you're in a Mac. Can you get access to a windows machine at all? This is why I hate macs
Teet1 said:
If it's saying that error then it's probably not letting you downgrade.
Also this might be slightly more difficult since you're in a Mac. Can you get access to a windows machine at all? This is why I hate macs
Click to expand...
Click to collapse
So what would be the reason that it wouldn't let me downgrade?
I've always used a mac and always managed to find an answer. Sure, toolkits don't work, but using fastboot and adb and doing it that way always has. Now suddenly no fastboot and I'm screwed... I don't really have access to a windows pc.
I just find it hard to believe that it's simply not possible on a mac.
alajoy said:
So what would be the reason that it wouldn't let me downgrade?
I've always used a mac and always managed to find an answer. Sure, toolkits don't work, but using fastboot and adb and doing it that way always has. Now suddenly no fastboot and I'm screwed... I don't really have access to a windows pc.
I just find it hard to believe that it's simply not possible on a mac.
Click to expand...
Click to collapse
Yeah fastboot screen was removed in newer versions. But that's at a software level of the phone. On your computer, the adb and fastboot commands are universal. It's usable on Mac, Linux and windows. The tools used for the phone like miflash or axon7tool are made for windows though and you kinda need those to fix bricked phones. There's a way to force push the twrp image into the recovery partition via adb but I don't know what the name of the recovery partition is
@alajoy: You can give yourself access to a fake Windows on your Mac. It's called a virtual machine. VirtualBox is one free software that can do this. Pretty easy to use, you install a virtualized Windows that you can boot into. Then you can run all Windows-based tools out there. It's also easy to share a USB port with the VM. Then flashing tools can access it. I run Linux as my main OS on a Sager gaming laptop, this is how I flash my A7 and Samsung phones. It just works, and reliably. I do also have a real Windows 10 installed on a partition on the same PC, but that is only for gaming and I never, ever allow it to connect to the Internet.
@Teet1: The literal name of the recovery partition is exactly that, recovery. And that is what most Android devices call it, regardless of manufacturer. It doesn't matter whether it is TWRP or ZTE stock recovery, the name is the same. It can be accessed via the paths:
/dev/block/platform/soc/624000.ufshc/by-name/recovery
/dev/block/bootdevice/by-name/recovery
/dev/block/sde14
On other devices the path may be different (but the 2nd example above will work for most), but the name is usually the same.
AnonVendetta said:
@alajoy: You can give yourself access to a fake Windows on your Mac. It's called a virtual machine. VirtualBox is one free software that can do this. Pretty easy to use, you install a virtualized Windows that you can boot into. Then you can run all Windows-based tools out there. It's also easy to share a USB port with the VM. Then flashing tools can access it. I run Linux as my main OS on a Sager gaming laptop, this is how I flash my A7 and Samsung phones. It just works, and reliably. I do also have a real Windows 10 installed on a partition on the same PC, but that is only for gaming and I never, ever allow it to connect to the Internet.
@Teet1: The literal name of the recovery partition is exactly that, recovery. And that is what most Android devices call it, regardless of manufacturer. It doesn't matter whether it is TWRP or ZTE stock recovery, the name is the same. It can be accessed via the paths:
/dev/block/platform/soc/624000.ufshc/by-name/recovery
/dev/block/bootdevice/by-name/recovery
/dev/block/sde14
On other devices the path may be different (but the 2nd example above will work for most), but the name is usually the same.
Click to expand...
Click to collapse
By name i meant the path, are you sure that's the path for our device? I tried that once and it was not that. Either way he is able to do it
@Teet1: Yeah, I'm sure, but not on all 3 paths. /dev/sde14 may be correct or not, depending on firmware/boot stack that is installed (or the presence of a vendor partition, which might change the paths). But the other 2 should be as I listed.
Just open a root file manager and see for yourself. I use Total Commander, which also shows symbolic links (the one with "bootdevice" in the path is really just a symlink to 624000.ufshc). Getting the recovery path from the example with "bootdevice" in the name should also work on almost any device running Android, and will generally point to the recovery partition. You can see the paths in TWRP too, but TWRP doesn't show symlink (but you should be able to see them if you use the right commands in any terminal, like TWRP's terminal).