Related
First of all I have a 16gb n7 currently on 4.2.1 JOP40D. It's unlock/rooted on STOCK rom.
First off I have tried installing the OTA update and would get an error everytime.
Then I tried installing CWM and manually pushing the update nakasi update and it still threw an error:
Verifying current system..
assert failed: apply_patch_check ("/system/build.prop", 38f7593c2ff2fa85a147 etc...)
E: Error in /sdcard/0/6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
(status 7)
Installation abborted.
So from googling/searching that I have figured that there is something not "stock" about my build.prop. I had edited it to get rid of the NAV bar but after re-editing it back to stock, it would still throw the same error.
So first I tried reflashing 4.2.1 ... threw the same error
Now I'm trying to get the build prop out of the JOP40D update but when I look in the files it is called "build.prop.p" ... I'm not sure what that last .p is about? Also when opening it there are just about 2 lines of chinese characters... Soooo this is where I'm stuck... I need to know how to extract a proper build prop from 4.2.1 or I need someone to post a stock 4.2.1 build prop.. thanks..
edit: before people suggest I have tried redownloading both the JOP40D and JPQ39 files
edit2: I am on a mac so flashing to stock from fastboot / abd isn't really an option
The checksum performed requires the file to be exactly identical to the original.
No extra spaces, identical line termination schemes et cetera - identical byte-for-byte. That means including characters you can not see in an editor.
You can certainly copy the original to a folder side-by with your hand-edited version and run any checksum on the both of them to see if you got it right, but it is probably easier to just copy the original into place.
Simply put, the only reason that check continues to fail is because the file you have there is NOT identical to the original.
good luck
canadianrider said:
edit2: I am on a mac so flashing to stock from fastboot / abd isn't really an option
Click to expand...
Click to collapse
since when does fastboot or adb not work on a mac????
http://developer.android.com/sdk/index.html
hint: they have the package for mac...download it and follow the directions to run fastboot/adb commands...its easier than you think
canadianrider said:
Now I'm trying to get the build prop out of the JOP40D update but when I look in the files it is called "build.prop.p" ... I'm not sure what that last .p is about?
Click to expand...
Click to collapse
That is a *patch* file. It is used to perform binary patching of the original file - it is neither the original nor the replacement for the original.
You need to dig the original build.prop out of the 4.2.1 factory distro, or your own nandroid backups ( you do make backups, right?) The 4.2.1 distros are no longer online from Google, but oldblue910 has your butt covered with his randomphantasmagoria (sp?) site. Check for the link in the OTA post by oldblue910 over in the dev forum.
http://www.randomphantasmagoria.com <--- choose nakasi or nakasig links on rhs of page as appropriate
the easiest option would be to fastboot
system.img
and
boot.img
from the 4.2.2 images google provides...
bftb0 said:
That is a *patch* file. It is used to perform binary patching of the original file - it is neither the original nor the replacement for the original.
You need to dig the original build.prop out of the 4.2.1 factory distro, or your own nandroid backups ( you do make backups, right?) The 4.2.1 distros are no longer online from Google, but oldblue910 has your butt covered with his randomphantasmagoria (sp?) site. Check for the link in the OTA post by oldblue910 over in the dev forum.
http://www.randomphantasmagoria.com <--- choose nakasi or nakasig links on rhs of page as appropriate
Click to expand...
Click to collapse
Thank you! That's what I was looking for.
I did make a backup .... many moons ago.. then the hard drive on my windows pc died. And there went my backups..
Pirateghost said:
since when does fastboot or adb not work on a mac????
http://developer.android.com/sdk/index.html
hint: they have the package for mac...download it and follow the directions to run fastboot/adb commands...its easier than you think
Click to expand...
Click to collapse
Yeah I looked that up after I posted this.. Now to figure out how to use ADB and Fastboot.
Pirateghost said:
the easiest option would be to fastboot
system.img
and
boot.img
from the 4.2.2 images google provides...
Click to expand...
Click to collapse
Not sure how to do that... I've been looking at the thread for putting the n7 back to stock with adb/fastboot .. haven't looked too closely yet (just sat down) but I don't want to relock the bootloader so im not sure if that applies to me. Is there a thread on how to flash firmware with ADB?
Cheers
canadianrider said:
Thank you! That's what I was looking for.
I did make a backup .... many moons ago.. then the hard drive on my windows pc died. And there went my backups..
Yeah I looked that up after I posted this.. Now to figure out how to use ADB and Fastboot.
Not sure how to do that... I've been looking at the thread for putting the n7 back to stock with adb/fastboot .. haven't looked too closely yet (just sat down) but I don't want to relock the bootloader so im not sure if that applies to me. Is there a thread on how to flash firmware with ADB?
Cheers
Click to expand...
Click to collapse
running adb and fastboot commands DO NOT require you to relock the bootloader
its simple. once you have your fastboot executables set up on your computer its literally as simple as putting the device in fastboot mode, and running:
fastboot flash system nameofsystem.img
fastboot flash boot nameofboot.img
Pirateghost said:
running adb and fastboot commands DO NOT require you to relock the bootloader
its simple. once you have your fastboot executables set up on your computer its literally as simple as putting the device in fastboot mode, and running:
fastboot flash system nameofsystem.img
fastboot flash boot nameofboot.img
Click to expand...
Click to collapse
No no I know it does not require you to relock the bootloader.. I just assumed the method used in the one thread I was talking about would relock the bootloader.. I'm just talking out of my ass here though.. I'll start reading on how to use fastboot soon.
If anyone has any good idiot proof guides I'd appreciate it.
follow GOOGLE's directions for setting up fastboot and adb.
it is literally 2 commands
fastboot flash system nameofsystemimgfile.img
fastboot flash boot nameofbootimgfile.img
while the device is in fastboot mode....its not complicated. download the files you need and get started. in the amount of time you have waited on a reply, you could have already had it done. you dont have to learn every command, you just need to 'install' fastboot and adb and put the files in the proper place.
https://developers.google.com/android/nexus/images
http://bit.ly/158k5Wr
ah hah! after a bit of reading and fumbling around with fastboot I did it! thanks for all the help guys. my blood pressure can go down now..
canadianrider said:
ah hah! after a bit of reading and fumbling around with fastboot I did it! thanks for all the help guys. my blood pressure can go down now..
Click to expand...
Click to collapse
see? it wasnt really that complicated.
Pirateghost said:
see? it wasnt really that complicated.
Click to expand...
Click to collapse
no it wasn't... but it was a little more complicated because there's no "this is how you flash on a mac" thread ... I just had to compile different parts from different threads.
canadianrider said:
no it wasn't... but it was a little more complicated because there's no "this is how you flash on a mac" thread ... I just had to compile different parts from different threads.
Click to expand...
Click to collapse
i provided a lmgtfy link, that had many threads listed on setting it up on a mac.
all nexus devices are the same in respect to fastboot/adb
any thread you find for n7, galaxy nexus, nexus4....pretty much universal
Ok, now just came across another issue.. I'm on 4.2.2 and all is well, but now I want to root.
And now adb is saying that my device is offline? I've tried restarting the device. Checking and unchecking USB debugging. Unplugging and plugging it back in but nothing? ... I've read on windows machines it might be a driver issue but with mac's we don't have to install drivers.
ADB worked perfectly fine before the update...
Has anyone made a version of the 4.2.2 update that can be installed even for those of us with modified system/app files? The only way I could get the last two updates was to hunt down this specific version of the update files.
canadianrider said:
Ok, now just came across another issue.. I'm on 4.2.2 and all is well, but now I want to root.
And now adb is saying that my device is offline? I've tried restarting the device. Checking and unchecking USB debugging. Unplugging and plugging it back in but nothing? ... I've read on windows machines it might be a driver issue but with mac's we don't have to install drivers.
ADB worked perfectly fine before the update...
Click to expand...
Click to collapse
What version of adb are you using? (command: "adb version")
With 4.2.2 you should see a pop-up on the tablet asking you to accept the device (PC/Mac) with the RSA fingerprint yadda-yadda-yadda... If you don't hit the accept/OK button within 2-3 seconds, adb will report the device offline ... even if you eventually press the OK/accept message in the popup on the tablet.
Try restarting the adb server on the Mac and be ready to press the button on the popup (make sure screen on tab is unlocked)
Code:
adb kill-server
adb devices
gavingt said:
Has anyone made a version of the 4.2.2 update that can be installed even for those of us with modified system/app files? The only way I could get the last two updates was to hunt down this specific version of the update files.
Click to expand...
Click to collapse
Pirate posted a link of the full 4.2.2 ROM that can be installed with fastboot.
bftb0 said:
What version of adb are you using? (command: "adb version")
With 4.2.2 you should see a pop-up on the tablet asking you to accept the device (PC/Mac) with the RSA fingerprint yadda-yadda-yadda... If you don't hit the accept/OK button within 2-3 seconds, adb will report the device offline ... even if you eventually press the OK/accept message in the popup on the tablet.
Try restarting the adb server on the Mac and be ready to press the button on the popup (make sure screen on tab is unlocked)
Code:
adb kill-server
adb devices
Click to expand...
Click to collapse
Android Debug Bridge version 1.0.29
No pop up on the tablet
Ah nevermind.. I'm just reading on the ADB website that you need version 1.0.31 or higher with 4.2.2 .... thanks for the heads up!
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 flashed a 4.4 stock rom on my 2012 32g N7, and unfortunately, didn't notice until too late that it was also overwriting my custom recovery with the stock. Also, in the flashing process I received an error while flashing GAPPS. When I first booted the tablet, everything was fine except for no GAPPS, but I figured it would be simple to just download an APK or two and load them - well, when I tried that with several play store APKs I got "cannot open file" error.
I have now resorted to ADB to "sideload" the apks (and a custom recovery) to the tablet. At first I had trouble with the drivers, but I have followed numerous tutorials and have a solid grasp of how ADB works now. (more on that later)
I also tried WUG's toolkit, but no matter what I tried (or how many drivers I un/installed) I could never get past the "no fastboot device" error.
I used a second version of the ADB from another XDA thread, and was finally able to get my PC at the command prompt to communicate with the N7, and recognize it with "ADB devices" - the result was "<serial> sideload". This is of course when I have the tablet in the stock recovery "adb sideload" mode.
I about yelled for joy, when after six hours of rebooting and tutorials, I was able to get "adb sideload update.zip" to load, but the joy was short lived - as it consistently hangs at "sending: 'sideload' 53%"
I have tried several different zips, of varying names. and even some APK's (which hang at 78%)
Any assistance which can be offered to get this N7 functional again would be greatly appreciated!
SOLVED
I was using a company computer, for which I did not have administrator rights......
I just face palmed so hard I gave myself a well deserved concussion.
Notable said:
I was using a company computer, for which I did not have administrator rights......
I just face palmed so hard I gave myself a well deserved concussion.
Click to expand...
Click to collapse
If you're flashing the stock KitKat, you shouldn't need to flash a separate gapps package. Aside from making sure you have UAC control, make sure you update boot to 4.23, if you haven't already done so. Flashing 4.4 is easy, as long as you don't make the mistake of ever owning another An droid device and plugging it in to your pc... Dealing with missing/conflicting Windows drivers might require a vacation day and a fist-full of xanax,
Sent from my Nexus 7 using Tapatalk
Everything I found on this says volume + and power, which kicks me into download mode, not fastboot.
I've gone into adb and typed adb reboot bootloader, but that just restarts the phone and turns in on like normal.
I google the how to enter fastboot mode on LG G2 and can find plenty of post about being stuck in fastboot, but nothing on how to get into fastboot in the first place.
Found a tutorial here about setting up and using fastboot and thought I was set until I got to the part about "and using fastback", where it just says:
Make sure you have android debugging turned on in your phone (not really needed for fastboot but you do need for ADB), plug it into your computer and boot into fastboot mode...
I felt like watching "Much ado about nothing" when Denzel says; "The learned constable is too cunning to be understood"
Any direction is appreciated.
Hmm, I may have written that guide... Just checked and yeah should have been more clear I'll change that up. It should have read the USB debugging was needed for adb (not for fastboot) so when you can issue
adb reboot bootloader
But after that I did mention to check device specific forum for answers on how to get into fastboot/bootloader and being I've never held an lg g2 I took a quick look around.
Unfortunately the only way that I found that people said works every time is to wipe recovery to get into bootloader mode as the recovery you guys currently have disables something due to a patch getting custom recoveries to work
So yeah, I would advice to speak with someone knowledgeable about your specific device before you just wipe recovery
Out of curiosity, is there something specific you need to do with fastboot or are you just curious about your phone?
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Out of curiosity, is there something specific you need to do with fastboot or are you just curious about your phone?
Click to expand...
Click to collapse
the current thing I've been trying to straighten out is that despite being rooted and installing TWRP, I can't install ROMS. I tried CM 11 and Hellfire so that I could put kitkat on, but gave the following:
Error executing updater binary zip.
One of the answers I found said that I had to go back to TWRP 2.3 (I'm using 2.6) and I believe that's where the whole bootloader thing came into play, because it was the way to 'downgrade' -
So then I found Philz touch 6 (as I understand it a mode of CM 11), but here he talked about fastboot and lokifying items. Here's the link:
http://forum.xda-developers.com/showthread.php?t=2554053
In the end it still comes back to the "can't load ROMs" issue. Just want a completely stripped down Kitkat that I can add the stuff I want without the bloatware.
Thanks in advance.(and the thanks button was hit on your reply)
For KitKat you should need a newer recovery with SELinux support which I believe is 2.6.x and newer for twrp, 2.3 I doubt would work if there even is one for your phone
But yes fastboot is often the best way to change recoveries but not the only way.
If there is a flashable.zip you could install new recovery from old
If your current ROM supports the flash image binary you can use a terminal emulator
You can use adb to install
Or even apps from the market
I would look for the latest recovery for your device, twrp, cwm, shouldn't matter so long as its new and then find what way works best changing for your phone.
The update-binary issue is often a sign that you need to change recoveries
Unfortunately without having your device I don't know if I can give you the best answers but feel free to ask
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Unfortunately without having your device I don't know if I can give you the best answers but feel free to ask
Best of luck!
Click to expand...
Click to collapse
Thanks again. I have adb and the script for loading TWRP 2.6.xx. I unrooted and rerooted the phone, because I wasn't sure how to replace the recovery... Now I think I realize that I could just find another recovery image and place it in the same file as the loki flash and that will flash it (At least that's what I understand at present).
If that's the case, then downloading the Philz touch 6 would work... but not wanting to brick it, I'm still asking and reading.
Hello Guys.
I am having a similar issue. I have a new ROM that will not run because of a faulty lg set up wizard that always force closes and I can not get passed it and a nandroid that for some reason is corrupted. So. This fastboot seems to be a dead end it looks like a quick learning curve of ADB is the only viable answer. I have installed all SDK Manager with ADB Tools and also the required Jarva JDK and LG drivers. The phone is turned on (at the beginning of the faulty setup wizard) In CMD my device is found when typing in 'adb devices' So. I am already to push a new ROM over to the phone.
Do either of you guys know the adb command?
Help would be appreciated.
Thanks
You can't actually flash a new ROM with adb, but you can either push it phone with adb and then flash in recovery. Or if your recovery has an option for adb sideload then use this.
Also setup wizard crashing is usually the fault of wrong gapps or not wiping before flashing a rom
Sent from my Nexus 4 using XDA Premium 4 mobile app
I found that the best way was to load flashify, that did the trick so I could start trying out ROMs... so no on to the next step - finding a 4.4.2 stripped down stock and the LG stuff I actually like.... thanks again.
demkantor said:
You can't actually flash a new ROM with adb, but you can either push it phone with adb and then flash in recovery. Or if your recovery has an option for adb sideload then use this.
Also setup wizard crashing is usually the fault of wrong gapps or not wiping before flashing a rom
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply!
I know it's not possible to flash a ROM via ADB. I have everything set up, ADB etc, etc. My phone is turned on and adb is seeing it but I can not work out the command to push. Every time I try to push I just get a long list of ADB instructions (I think they are) but nothing gets pushed. I have read lots of instructions on how to make the command but I still must be doing something wrong.
Here are my parameters;-
adb push/C:\Users\dene\Desktop/cm-11-20140210-SNAPSHOT-M3-d802.zip/sdcard
Am I missing some spaces I am not aware of? Are all my slashes the right way round and in the right places? Is my 'sdcard' destination designation correct seeing as there is only internal storage on the G2?
Another problem I am having is that ADB has no problem seeing my sevice EXCEPT when I boot in to recovery (TWRP). When in recovery I lose coms between my device and pc. Hence I can no do TWRP ADB side load (I have tried). I have all the correct LG drivers loaded. Except MTP keeps failing to install? Any ideas?
Not to be mardy about it or hassle you but I am fairly house bound and live out in the country and really require my mobile phone. I have spent many hours trying to figure this out. Any help with the above would be much appreciated?
PS. I did a very thorough wipe, I always do. The gapps are built in to this ROM!
Thanks
dodge3003 said:
Thanks for the reply!
I know it's not possible to flash a ROM via ADB. I have everything set up, ADB etc, etc. My phone is turned on and adb is seeing it but I can not work out the command to push. Every time I try to push I just get a long list of ADB instructions (I think they are) but nothing gets pushed. I have read lots of instructions on how to make the command but I still must be doing something wrong.
Here are my parameters;-
adb push/C:\Users\dene\Desktop/cm-11-20140210-SNAPSHOT-M3-d802.zip/sdcard
Am I missing some spaces I am not aware of? Are all my slashes the right way round and in the right places? Is my 'sdcard' destination designation correct seeing as there is only internal storage on the G2?
Another problem I am having is that ADB has no problem seeing my sevice EXCEPT when I boot in to recovery (TWRP). When in recovery I lose coms between my device and pc. Hence I can no do TWRP ADB side load (I have tried). I have all the correct LG drivers loaded. Except MTP keeps failing to install? Any ideas?
Not to be mardy about it or hassle you but I am fairly house bound and live out in the country and really require my mobile phone. I have spent many hours trying to figure this out. Any help with the above would be much appreciated?
PS. I did a very thorough wipe, I always do. The gapps are built in to this ROM!
Thanks
Click to expand...
Click to collapse
I HAVE SOLVED THE ISSUE! Thanks for your assistance mate but in the end I just went back to stock using this amazing thread:-
http://forum.xda-developers.com/showthread.php?t=2432476
in conjunction with this amazing video;-
http://www.youtube.com/watch?v=IixQjo_hyz8
So! I am now un rooted and back to stock. Time to start the rooting ana ROMing all over again.lol
Thanks
Glad to here!
You need a space after push
But it usually easier not to enter the location of a file while pushing so cd to the directory first like
cd C:\Users.....
Then once there adb push /nameoffile /locationonphone
But if you don't want to cd, I see you have widows, depending on version you can just right click in the folder your file is located and choose open cmd here
Sent from my Nexus 7 using XDA Premium 4 mobile app
Need Help
As I thought I bought LG G2 D-802, but it was D-800 and I accidentally install the lollipop of D802 and now it's in bootlap.... I can only get into fastboot and whenever I try to flash .img of D-800 or D-802 it just stuck at "writing .img"
What to do to unbrick the phone and bring it back to live. I tired the adb and fastboot cmd method on windows 10 and windows 7 but no success. It's just stuck at writing .img file.
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