Database Develop

Problems installing root toolkit drivers.

Am attempting to root my new n7 using:
Nexus-7-root-toolkit-v.1.1
iiuc as I have not put anything on there I don't need to unlock the bootloader. So I proceeded directly to installing the drivers.
I got a message saying that I had an existing Android driver installed (I assume for my sgs2) and a 'hit yes to reinstall, no to keep' message, which is a bit ambiguous. YES seems to lead to further activity. Enabled usb debugging, replugged the n7 and never saw any more activity, wizard or reboot. Hitting OK goes to phone not detected rc=103. Driver appears to uninstall from here.
Not a clue what I'm meant to do from this point, and suggestions welcome.
Ian

I chose yes (to reinstall driver).

ikeny said:
I chose yes (to reinstall driver).
Click to expand...
Click to collapse
I tried that too, but it lead to the 103.
Don't know how to proceed from here.
i

I'm confused. The Nexus Root Toolkit is v1.5 (not 1.1).
http://forum.xda-developers.com/showthread.php?t=1766475
Are you actually using the one click root tool (v1.1)?
http://forum.xda-developers.com/showthread.php?t=1742919
Either way, watch the youtube videos linked on the first post in each thread. It'll help to clarify things.
You have to unlock the boot loader in order to root.

Manually install them, follow the cyanogenmod guide on installing adb drivers.
Sent from my LG-P999 using xda app-developers app

IanWorthington said:
Am attempting to root my new n7 using:
Nexus-7-root-toolkit-v.1.1
iiuc as I have not put anything on there I don't need to unlock the bootloader. So I proceeded directly to installing the drivers.
I got a message saying that I had an existing Android driver installed (I assume for my sgs2) and a 'hit yes to reinstall, no to keep' message, which is a bit ambiguous. YES seems to lead to further activity. Enabled usb debugging, replugged the n7 and never saw any more activity, wizard or reboot. Hitting OK goes to phone not detected rc=103. Driver appears to uninstall from here.
Not a clue what I'm meant to do from this point, and suggestions welcome.
Ian
Click to expand...
Click to collapse
first off download the newest root toolkit from wugfresh 1.52
then if u have problem with the drivers with the toolkit, then stop the toolkit and install pda net on ur pc and it will install the drivers for u! then try unlocking and rooting and it should be alot easier. The only problem i had was with the drivers.

ikeny said:
I'm confused. The Nexus Root Toolkit is v1.5 (not 1.1).
http://forum.xda-developers.com/showthread.php?t=1766475
Are you actually using the one click root tool (v1.1)?
http://forum.xda-developers.com/showthread.php?t=1742919
Either way, watch the youtube videos linked on the first post in each thread. It'll help to clarify things.
You have to unlock the boot loader in order to root.
Click to expand...
Click to collapse
It *is* the one click tool, yes. I'l check out the videos, thanks. The text says the boot loader unlocking was optional, but I'll install the SDK and try that, thanks.
i

IanWorthington said:
It *is* the one click tool, yes. I'l check out the videos, thanks. The text says the boot loader unlocking was optional, but I'll install the SDK and try that, thanks.
i
Click to expand...
Click to collapse
It's only optional for those that already unlocked their boot loader previously.
In you case, you have to do it since yours is locked at the moment.

Needed to change the USB mode then the driver install and rooting worked fine. Wasn't obvious to me at least!
Many thanks.
Ian

ikeny said:
It's only optional for those that already unlocked their boot loader previously.
In you case, you have to do it since yours is locked at the moment.
Click to expand...
Click to collapse
Didn't have to unlock prior to rooting, the one click process did that for me.
i

[SOLVED] Stock 4.2.1 upgrade failed.

I've bought my son and daughter a nexus 7 each for Christmas.
His upgraded over the air fine, hers downloaded the firmware, rebooted and the installation started.
After a couple of minutes the Android fell over with a red exclamation mark.
I've tried forcing the upgrade and the same happened.
Any ideas how to upgrade her nexus 7?
Thanks

Fastboot mode is working ?
Sent from my GT-I9100 using xda premium

I've not tried it.
How do I try it?
Assuming it's ok, does that help with upgrading?
Any issue truing fast boot mode?

Any ideas? Or will it need replacing?

Factory reset and try again
Sent from my Nexus 7

I have the same problem.

Hey guys,
I made an account just to post this, however it was all done my G2 so I apologize for poor formatting and/or not completely clear instructions. This issue has kept me up for hours upon hours, and I finally figured out how to fix it. The issue apparently has something to do with the way the Nexus was formatted, prohibiting the update from working. Google/Asus support have been useless regarding the issue which is a very simple fix just requiring the user to reflash the N7 with a stock image. It has been confirmed working by not just me but other people on the reddit nexus 7 board. Here is what I did (copy/pasted from my reddit thread):
---------------------------------------------------------------------------------------------------------------------
There are two methods to fix this, an in depth method, and an easy and quick method. My first time I used the in depth, but I tested this with the easy method too so I'll just post that. I'm on a cell phone so I'm not going into the in depth method - I'm posting this so hopefully the other people like me who got this on Christmas won't have to return it.
----------------
For the quick and easy method, download Wug's toolkit here:
(google this, forums wont let me post links until I reach 10 posts)
Run the driver install guide, making sure to follow the parts about uninstalling previous drivers. Follow this to a T. Next, unlock your bootloader. Its painless and takes seconds. Next, go here and download your Nexus specific update.
(Find this on google developer site, you can google it too - forums wont let me post links - also make sure its 4.2.1)
Click on the "back to stock + unroot" -- we never rooted, but just do this. Select other/browse and browse to the image you downloaded. Flash this. You WILL fail on three files - it says something like recovery.sig failed - it will do it for two other .sig files. This is fine. Let it do its thing. A few minutes later your android will boot up. Log in, and go to settings. Click about tablet. Click on build number like 10 times, until it tells you developer options unlocked. Go into developer options and enable USB debugging. Now, go back to Wugs toolkit and lock the bootloader. There you have it, an updated nexus running stock everything, and locked so your warranty is not void.
----------------------------------------------------------------------------------------------------------------------------
This was a very sloppy guide put together on my cell phone. Any questions just post and I'll do my best to get back to you. Goodluck!

Hi.
Thanks for the reply.
Just wondering if there is an easier way to do this.
I'm not comfortable flashing a new device.
What was the suggestion about fast boot?
Thanks

albert_htc said:
Hi.
Thanks for the reply.
Just wondering if there is an easier way to do this.
I'm not comfortable flashing a new device.
What was the suggestion about fast boot?
Thanks
Click to expand...
Click to collapse
This is definitely the easiest way for you to fix your problems. The risk of your device becoming unusable is practically none. This is the beauty of nexus devices, Google provides official factory reset ROMs for you to flash in these sorts of situations. You can either use Wugs or mskip's tookit as advised to automate the process (fastboot commands used to flash the recovery image, fastboot commands are simply used to flash it to your device) or you can use fastboot to flash it yourself manually (still very easy)
I would 100% do this to fix your device. Don't be scared! This is the official way of fixing a nexus device when it doesn't function.

Thanks.
I'm trying this now.
I've uninstalled all previous drivers, and it's updated to an 'Android Phone -> Android Composite ADB Interface'
I've clicked the Reboot BootLoader Button.. and nothing happens on the tablet.
This was trying with the #3 driver option.
I'm now trying driver #2 !!

Another quick question...
Once all this is done, will I have issues with it in the future, or should this resolve future updates.?

albert_htc said:
Another quick question...
Once all this is done, will I have issues with it in the future, or should this resolve future updates.?
Click to expand...
Click to collapse
I'm not certain about the driver issues because I don't use Wug's toolkit, sorry!
However, when you get this completed, it should solve this problem in the future.

I've had to go with option 1 for the drivers..
but it's done and working
One thing I did have to do after unlocking the boot loader was reset up on the wifi and re enable USB debugging before I could continue.
all sorted thanks

albert_htc said:
Thanks.
I'm trying this now.
I've uninstalled all previous drivers, and it's updated to an 'Android Phone -> Android Composite ADB Interface'
I've clicked the Reboot BootLoader Button.. and nothing happens on the tablet.
This was trying with the #3 driver option.
I'm now trying driver #2 !!
Click to expand...
Click to collapse
Let us know how it comes out and if there's problems, exactly where you're hitting the problem. I will try to help you out and later today I could probably get on team viewer and help you figure the drivers out.
Sent from my Nexus 7 using Tapatalk HD

Hi CharliesTheMan..
It's working. Had to use option 1 for the drivers.. but its updated and working
Thanks

Glad it worked out!
Sent from my Nexus 7 using Tapatalk HD

"Error: device not found" when in Recovery - can't figure it out

Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!

@Lucky Armpit
When you are in recovery, at the adb sideload screen, unplug your N6 and plug it in again.

Lucky Armpit said:
Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!
Click to expand...
Click to collapse
Use Wugs toolkit to install drivers. It has a great step by step set-up to make sure it works and it tests everything so you know it works..

cam30era said:
@Lucky Armpit
When you are in recovery, at the adb sideload screen, unplug your N6 and plug it in again.
Click to expand...
Click to collapse
Hi cam30era, I tried that but it didn't help. I didn't try it after using Wug's toolkit so it's worth another shot.
Xplicit84 said:
Use Wugs toolkit to install drivers. It has a great step by step set-up to make sure it works and it tests everything so you know it works..
Click to expand...
Click to collapse
Hi Xplicit84, I used the Wugs toolkit provided in the NRT to install the proper drivers (it worked fantastic, by the way... mad props to Wug). That didn't help unfortunately.

try a different usb port
goto the device manager in windows and see if everything is good (no ! by a device)

apristel said:
try a different usb port
goto the device manager in windows and see if everything is good (no ! by a device)
Click to expand...
Click to collapse
Hi apristel, yup, tried that too, as I had read that perhaps there may be an issue with USB 3.0 ports. I don't think I have USB 3.0 ports (my laptop is a 2012-era Alienware M17x R3) but I tried a different port for the sake of doing it and it didn't make a difference.

Where did you get the 5.1 .zip file? Give us the exact name of the file because the 5.1 VZW .zip file that has been posted here that ends with .xml.zip is not designed for an adb sideload command. I.e., not designed to be flashed in recovery at all.

teddyearp said:
Where did you get the 5.1 .zip file? Give us the exact name of the file because the 5.1 VZW .zip file that has been posted here that ends with .xml.zip is not designed for an adb sideload command. I.e., not designed to be flashed in recovery at all.
Click to expand...
Click to collapse
Hi teddyearp, I downloaded it from a link on Droid-Life. I don't remember the exact name of the file because I renamed it to something much shorter, but here's where I got it from -
http://www.droid-life.com/2015/03/1...s-for-nexus-devices-4-5-6-7-9-10/#more-163271
Edit - Here's the direct link (the one I used) - http://android.clients.google.com/p...ed-shamu-ota-LMY47D-from-LRX22C-fullradio.zip

Lucky Armpit said:
Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!
Click to expand...
Click to collapse
Any luck, having the same problem and it's driving me nuts.

Mongo23ny said:
Any luck, having the same problem and it's driving me nuts.
Click to expand...
Click to collapse
Are you selecting "apply update from ADB" in recovery and then hitting power?
Then: adb sideload <filename of update.zip>
?

apristel said:
Are you selecting "apply update from ADB" in recovery and then hitting power?
Then: adb sideload <filename of update.zip>
?
Click to expand...
Click to collapse
Yes, as soon as boots into recovery it completely disappears from device manager. If I run the command after apply update from adb it says device not found.

Mongo23ny said:
Yes, as soon as boots into recovery it completely disappears from device manager. If I run the command after apply update from adb it says device not found.
Click to expand...
Click to collapse
Most likely a driver issue. I can remote in and check it out if you want using teamviewer

Go through the driver setup in wug again, pay close attention when you are deleting any old drivers..... delete anything that says google nexus or android... I had to do it twice.... put the phone into adb side load mode... check device manager again.. make sure you dont have a ? by android device... I did... update the driver from wug ( also I hid the sdk driver folder by renaming it so windows didn't try to pick up the driver from there again... once installed bingo!

apristel said:
Most likely a driver issue. I can remote in and check it out if you want using teamviewer
Click to expand...
Click to collapse
When I run the command reboot bootloader, no problem. But when it is in recovery I watched it disappear from device manager.
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Gage_Hero said:
Go through the driver setup in wug again, pay close attention when you are deleting any old drivers..... delete anything that says google nexus or android... I had to do it twice.... put the phone into adb side load mode... check device manager again.. make sure you dont have a ? by android device... I did... update the driver from wug ( also I hid the sdk driver folder by renaming it so windows didn't try to pick up the driver from there again... once installed bingo!
Click to expand...
Click to collapse
I used CF auto root to unlock the bootloader and root. I do have the NRT on my computer though.

Mongo23ny said:
When I run the command reboot bootloader, no problem. But when it is in recovery I watched it disappear from device manager.
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
I used CF auto root to unlock the bootloader and root. I do have the NRT on my computer though.
Click to expand...
Click to collapse
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)

apristel said:
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)
Click to expand...
Click to collapse
How do I install it properly? I got rid of some old drivers as well

Mongo23ny said:
How do I install it properly? I got rid of some old drivers as well
Click to expand...
Click to collapse
Well you can just change them in the device manager.
I'm willing to use team viewer and show you how. (you'd see everything i do) It's hard to write it out for me right now..just had hand surgery this morning and my hand is still completely numb. If you want to download this and run it http://download.teamviewer.com/download/TeamViewerQS_en.exe
PM me the id and password and i'll connect up and show ya. Just so you know, it'd be a one time thing connecting, your password changes everytime and you'd have to have that running to connect. I own a computer repair store and use it frequently.

apristel said:
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)
Click to expand...
Click to collapse
I'm thinking that's the problem for me too, but I don't understand what I'm missing. When I ran Wug, I removed anything and everything that had the word "Google" next to it. Wug installed the drivers (had to do option #2 before I got no errors at all) and it reports that everything is hunky-dory. But as Mongo23ny said, that's exactly what happens... when it's at the boot menu it's in Device Manager but the moment I select Recovery it disappears.

Lucky Armpit said:
I'm thinking that's the problem for me too, but I don't understand what I'm missing. When I ran Wug, I removed anything and everything that had the word "Google" next to it. Wug installed the drivers (had to do option #2 before I got no errors at all) and it reports that everything is hunky-dory. But as Mongo23ny said, that's exactly what happens... when it's at the boot menu it's in Device Manager but the moment I select Recovery it disappears.
Click to expand...
Click to collapse
I can try to fix your drivers too, just follow the link i posted for him and send me the info. I don't have stock recovery on my phone to replicate your issue.

apristel said:
I can try to fix your drivers too, just follow the link i posted for him and send me the info. I don't have stock recovery on my phone to replicate your issue.
Click to expand...
Click to collapse
PM sent. Thanks

[Q] How to unlock bootloader on 6.0 Stock

Hi,
So today I bought a Nexus 6. I straight away updated to 6.0, forgetting that I should have unlocked the bootloader! So now I wan to know if I can unlock the bootloader on stock! I really want root so thanks in advance to those who are able to help!!!
Regards

Yep, install the Android SDK (or just the tools adb and fastboot). If on windows install the driver, connect your phone, and type
fastboot flashing unlock
But this will erase everything on your device.

istperson said:
Yep, install the Android SDK (or just the tools adb and fastboot). If on windows install the driver, connect your phone, and type
fastboot flashing unlock
But this will erase everything on your device.
Click to expand...
Click to collapse
Before typing that command be sure to go into Developer options and enable both USB debugging and OEM unlocking.
Sent from my P01MA using Tapatalk

wtherrell said:
Before typing that command be sure to go into Developer options and enable both USB debugging and OEM unlocking.
Sent from my P01MA using Tapatalk
Click to expand...
Click to collapse
Yes, sorry, I left that part out.
Also read a lot about rooting marshmallow, it's not that simple as it was with Lollipop. You need a modified boot.img with either a custom kernel, or with modified sepolicies file, before you root it, otherwise it will just stop booting.

You could always use Nexus Root Toolkit. It worked for me no problem.

I wouldn't recommend. It still does not substitite for reading about it before rooting, and if you read enough that you know what it's doing, then you know enough to do it yourself.
Remember, rootkits only work until the next update for marshmallow, then you have to wait until it's developer updates it, otherwise it'll softbrick the phone, and you'll have to undo it.
People come here constanly asking what's wrong with MRA58R? Because the rootkit worked perfectly with MRA58K, and now it displays a red triangle and won't boot.
So if you search xda for red triangle, you'll find also solutions that will actually make rootkits obsolete.
Sent from my Nexus 6 running cyosp using Tapatalk

istperson said:
I wouldn't recommend. It still does not substitite for reading about it before rooting, and if you read enough that you know what it's doing, then you know enough to do it yourself.
Remember, rootkits only work until the next update for marshmallow, then you have to wait until it's developer updates it, otherwise it'll softbrick the phone, and you'll have to undo it.
People come here constanly asking what's wrong with MRA58R? Because the rootkit worked perfectly with MRA58K, and now it displays a red triangle and won't boot.
So if you search xda for red triangle, you'll find also solutions that will actually make rootkits obsolete.
Sent from my Nexus 6 running cyosp using Tapatalk
Click to expand...
Click to collapse
Toolkits are not recommended especialy for newbies, just learn a few simple adb/fastboot commands and stay in control all the way

bootloop with locked bootloader

Hello
So I recently brought a second hand nexus 6 for cheap since it was described as bootlooping and the owner couldn't fix it. I already have a fully working nexus 6 so decided to get this as a potential source for spares assuming I couldn't get it working to be used as a 2nd phone. Having received it today, I found that when turned on, it would get stuck at the white "google" screen and go no further than that. I can access the bootloader and the stock recovery. The bootloader is locked and since the "allow oem unlock" option has been added to lollipop (which I had not even heard of till looking into why I couldn't unlock this device), I can't seem to unlock it, so i'm at a loss. So far i've tried;
-unlocking the bootloader using fastboot oem unlock
-fastboot format cache/data (both saying the BL needs to be unlocked, even though people have said they've managed with it locked)
-flashing roms via fastboot (that obviously didn't work)
-using the "apply update from adb" option to install a stock zip from google (error "signature verification failed")
-same as above, but with custom roms (gave the error "failed to verify whole-file signature")
-same as above again ,but with the OTA of the next android version, in the hope I could continue flashing these till I reached a major one and then it would work (came back saying "system partition has unexpected contents)
-making a nandroid of my working phone, and making a bootable zip of that ("signature verification failed")
I've basically reached a point now where I imagine it's probably not ever gonna work and i'm gonna have to give up, but I figured requesting here can't hurt and I don't wanna give up knowing that something could work, I just never found out about it. I also can't help but think that given I have a working nexus 6, there must be something I can do with that to make the new one work (the only idea I had was the nandroid of it, but there may be something else)
Cheers
Cameron

That phone is not pining for the fjords. It's an ex-phone.

istperson said:
That phone is not pining for the fjords. It's an ex-phone.
Click to expand...
Click to collapse
What do you mean by "pining for the fjords"?
I wondered, is it possible to use wugfresh to push system files to the device (while removing old ones) making it seem to have a clean system partition, then try the ota again via adb sideload. Even if i took the system files from my functioning nexus. The faulty one is on lmy47z at the moment.

call-of-monst3r said:
What do you mean by "pining for the fjords"?
I wondered, is it possible to use wugfresh to push system files to the device (while removing old ones) making it seem to have a clean system partition, then try the ota again via adb sideload. Even if i took the system files from my functioning nexus. The faulty one is on lmy47z at the moment.
Click to expand...
Click to collapse
http://www.google.com/search?q=pining for the fjords
And, I'm sorry, but no, you can't do more with toolkits than with adb and fastboot. Toolkits are just front-ends for those two tools.
You have already tried everything possible, and since the bootloader is locked and you can't boot into Android to enable unlocking, all you have is just spare parts. I'm sorry.

istperson said:
And, I'm sorry, but no, you can't do more with toolkits than with adb and fastboot. Toolkits are just front-ends for those two tools.
You have already tried everything possible, and since the bootloader is locked and you can't boot into Android to enable unlocking, all you have is just spare parts. I'm sorry.
Click to expand...
Click to collapse
Thanks for the help, I've never heard of that phrase before and I thought i had heard them all given what my mums like
When the phone is in recovery, when the update via adb is selected, the phone is detected as an adb sideload device when "adb devices" is entered. Can I push/pull system files when it's detected as sideload? Because I noticed wugfresh supports pushing/pulling of files between the device and pc, but I wasn't sure if it could do system files when the device is detected as sideload
Thanks for the help, i would really like to make it work, and given its not exactly a device I rely on, I'm happy to spend more time working on it and trying more unusual/new ideas
Cameron

call-of-monst3r said:
Thanks for the help, I've never heard of that phrase before and I thought i had heard them all given what my mums like
When the phone is in recovery, when the update via adb is selected, the phone is detected as an adb sideload device when "adb devices" is entered. Can I push/pull system files when it's detected as sideload? Because I noticed wugfresh supports pushing/pulling of files between the device and pc, but I wasn't sure if it could do system files when the device is detected as sideload
Thanks for the help, i would really like to make it work, and given its not exactly a device I rely on, I'm happy to spend more time working on it and trying more unusual/new ideas
Cameron
Click to expand...
Click to collapse
Here it is how sideload works. But as I understood it's only for updates on working phones:
http://www.androidcentral.com/how-manually-upgrade-your-nexus#slide5