Database Develop

Need some help (couple questions)

im a bit new to xda developers. ive scourged the forums all day via search and found no concrete help or answers.
FIRST: i dont know what adb is and because of that, idk why my nandroid backups and restore wont work. it say "push via adb" or something like that
SECOND: i also dont know how to use sdk or whatever it is.
i need a detailed walkthrough of some sorts because the search on this forum sucks and did not help me at all

*COUGH*google search "ADB HOW TO" *COUGH*
look at the results!
took all of 2 seconds dude.....not being able to find info on adb is bs. not trying to be a douche but seriously....

caynelyfe said:
im a bit new to xda developers. ive scourged the forums all day via search and found no concrete help or answers.
FIRST: i dont know what adb is and because of that, idk why my nandroid backups and restore wont work. it say "push via adb" or something like that
SECOND: i also dont know how to use sdk or whatever it is.
i need a detailed walkthrough of some sorts because the search on this forum sucks and did not help me at all
Click to expand...
Click to collapse
http://developer.android.com/guide/developing/tools/adb.html (Google is your friend)
http://androidforums.com/all-things-root-sprint-hero/38911-guide-root-rom-faq-tutorial.html

chfields said:
http://developer.android.com/guide/developing/tools/adb.html (Google is your friend)
http://androidforums.com/all-things-root-sprint-hero/38911-guide-root-rom-faq-tutorial.html
Click to expand...
Click to collapse
beat you to the punch!

nighteyes_wolf said:
beat you to the punch!
Click to expand...
Click to collapse
................................

nighteyes_wolf said:
*COUGH*google search "ADB HOW TO" *COUGH*
look at the results!
took all of 2 seconds dude.....not being able to find info on adb is bs. not trying to be a douche but seriously....
Click to expand...
Click to collapse
thanks smarty pants

caynelyfe said:
Seriously it didnt take for you be a smart ass i just needed help. because when i search, damn near every single page that come up has nothing to do with what im looking for. dismiss yourself man ur not helping. AND THANKS TO THE FELLAS WHO DID
Click to expand...
Click to collapse
Are you using google vvm for voice dictation?

caynelyfe said:
Seriously it didnt take for you be a smart ass i just needed help. because when i search, damn near every single page that come up has nothing to do with what im looking for. dismiss yourself man ur not helping. AND THANKS TO THE FELLAS WHO DID
Click to expand...
Click to collapse
not to highjack the thread, but whats it mean when recovery starts prompting you to exctecute command via adb/sdk? i noticedbmy bluecarebear is TRUELY angry with me, so much hes not wiping my ext or dalvk!
nandroid works, backup and restore
factory data reset works
but wiping doesnt.
help?

Well using the xda search "ADB" the first result is a thread that leads you to
http://forum.xda-developers.com/showthread.php?t=532719
How is that difficult? Everything you need to know about the ADB et al is there
As far as the sdk is concerned, your hero is rooted so it is on your pc already if you followed the traditional process. Otherwise it is there in the link as well.
Seriously I am not trying to be a smart ass but too many people give up before even trying.

sinistermeshes said:
not to highjack the thread, but whats it mean when recovery starts prompting you to exctecute command via adb/sdk? i noticedbmy bluecarebear is TRUELY angry with me, so much hes not wiping my ext or dalvk!
nandroid works, backup and restore
factory data reset works
but wiping doesnt.
help?
Click to expand...
Click to collapse
if you dont use app2sd then ext means nothing, trying to wipe dalvik normally yells at you but it should be alright

sinistermeshes said:
not to highjack the thread, but whats it mean when recovery starts prompting you to exctecute command via adb/sdk? i noticedbmy bluecarebear is TRUELY angry with me, so much hes not wiping my ext or dalvk!
nandroid works, backup and restore
factory data reset works
but wiping doesnt.
help?
Click to expand...
Click to collapse
I would try reflashing your recovery image.
I had trouble with the green one a while back, I changed images a couple times for other reasons. Back on green cb now with no problems since flashing over the problematic image.

also, check out the
"[STICKY WIKI] - [PLEASE READ] - All Current Guides, How to's and THEMES"

nighteyes_wolf said:
also, check out the
"[STICKY WIKI] - [PLEASE READ] - All Current Guides, How to's and THEMES"
Click to expand...
Click to collapse
im not up on most of the geek terminology or whatever it is, in other words the guide here wasnt helpful, but since im rooted, i guess i dont need it(sdk) or whatevr. i still cant figure out why i cant make any nandroid backups or restore currently stored ones

... I'm speechless, or I guess in this case typeless
*edit- +1 On what subliminalurge says in the next post. This stuff is not hard to learn. Either commit yourself to a couple weekends of focused enlightenment or make your peace with the stock setup. Almost any of us would be happy to help... after you take the first couple steps and learn some of the FUNDAMENTALS.
Go to the "GUIDE WIKI" and read read read, when you start becoming familiar with some of the "geek terminology" come back and we'll help connect some of the dots.

caynelyfe said:
im not up on most of the geek terminology or whatever it is, in other words the guide here wasnt helpful, but since im rooted, i guess i dont need it(sdk) or whatevr. i still cant figure out why i cant make any nandroid backups or restore currently stored ones
Click to expand...
Click to collapse
Also not trying to be a smartass, but come on dude. If you're not willing to hit google and learn a little bit, then you are probably already in over your head just with what you've done to your phone so far.
I STRONGLY recommend you find a way to be happy with stock phones. Otherwise, I see a large collection of very expensive paperweights in your future.

[Q] For those of us non-devs - rooting?

So I see from the Development subforum that the Droid 4 hasn't been rooted yet. Correct? Does anyone have a plain english update as to what's going on on that front?
I see there's a bounty on someone's head, or something like that, but that's all I've got.. and I'm not savvy enough to know what to do myself or know what's really happening there. I'd love a one click root method. How far away are we from that functionality?
sorry for the pretty dumb question

tamarw said:
So I see from the Development subforum that the Droid 4 hasn't been rooted yet. Correct? Does anyone have a plain english update as to what's going on on that front?
I see there's a bounty on someone's head, or something like that, but that's all I've got.. and I'm not savvy enough to know what to do myself or know what's really happening there. I'd love a one click root method. How far away are we from that functionality?
sorry for the pretty dumb question
Click to expand...
Click to collapse
Root has been achieved. Just follow the directions here: http://forum.xda-developers.com/showthread.php?t=1492843

kwyrt said:
Root has been achieved. Just follow the directions here: http://forum.xda-developers.com/showthread.php?t=1492843
Click to expand...
Click to collapse
thank you Guess I was just searching for the phrase "root."

tamarw said:
thank you Guess I was just searching for the phrase "root."
Click to expand...
Click to collapse
No problem. Happy rooting. And be careful!

Root was achieved on this device by djrbliss before it was even released actually, but we still do not yet have a full XML.zip of fastboot images to restore with, so it is very dangerous to make any significant mods at this stage.
I have been pushing all my sources very hard to find this file, but so far everyone has come up empty.
Until we have it we are all working without a safety net because signed factory images are needed to restore a soft bricked device.

Stick to rooting your phone, for the time being. You can disable bloatware, and customize the hell out of the stock ROM that's already on there. That should be enough to get you through, for the time being. Don't get me wrong, we're all salivating over a real safety net.
Go with a simple root or safestrap it. I bricked my phone using safestrap.
Root for now, wait for fastboot files.

[Q] Xperia Z [Rooted] Safe To Update?

That might seem like a silly title, but I do have decent reason to ask.
Now, before I start - I have given the forums a nice search. I did check the Wiki. Believe me, XDA's "You're a noob" video gave me enough of a fright to search more thoroughly than I normally would.
Unfortunately, I couldn't find what an answer I was looking for. Either I wasn't broad enough, or I'm among the first to ask.
Even now, I'm not sure if I should be making an entirely new thread, or posting in the 'Ask Any Question' thread.
Either way, since I'm here...
I'm currently running a rooted Xperia Z firmware 4.1.2 with the bootloader locked. I am aware of the most recent firmware update, 4.2.2.
Now, I've only been in the experience of rooting for a little while. The Z is really my first rooted phone, and as such, I haven't got my head wrapped around over what it means to upgrade, or otherwise update a rooted device. Still learning, heh.
Now, I understand that there's a risk - If not a certainty - That if I take the official update, I will lose my root access.
That's all fine and dandy since I'm also aware of DooMLoRD's rootkit update for this software version.
What I'm mostly worried about there though is the fact that the rootkit installs BusyBox.
I already have this installed, and I know it's risky to uninstall it. However, installing it over a current installation sounds like it's going to cause so much unwanted chaos.
So... I really could do with some advise on that.
Also, perhaps this is personal paranoia, but I could do with the reassurance. Taking that update -is- safe enough for my device, considering it's rooted, right? Again, I'd probably lose root access, but is that the only risk?
I'm not gonna end up downloading it and find that the phone won't turn on due to some error caused by the fact that my phone was rooted, am I?
Thanks for reading,
- Sytheriseida

Yes.
...Sent from Zed

XperienceD said:
Yes.
...Sent from Zed
Click to expand...
Click to collapse
... Not particularly helpful, but thanks anyway.

Sytheriseida said:
... Not particularly helpful, but thanks anyway.
Click to expand...
Click to collapse
Sorry, on my Phone. Asking if its safe to update is a bit of a poor question which the short answer is yes. The stickys or existing threads should be the first port of call for most People learning about a new device.
...Sent from Zed

XperienceD said:
Sorry, on my Phone. Asking if its safe to update is a bit of a poor question which the short answer is yes. The stickys or existing threads should be the first port of call for most People learning about a new device.
...Sent from Zed
Click to expand...
Click to collapse
What I mostly meant was if it was safe considering the setup of my phone.
I can understand that it was a poor question - Hence, personal paranoia.
Thanks for tolerating it, heh.
Yeah, I saw the threads regarding such information. But I guess I wanted to be absolutely certain.
That's not a very good excuse, I know. But it's the only one I have.

A bit too paranoid. Just backup your Phone the best you can then go from there, if it goes wrong it's easily sorted by using the flashtool.
...Sent from Zed

XperienceD said:
A bit too paranoid. Just backup your Phone the best you can then go from there, if it goes wrong it's easily sorted by using the flashtool.
...Sent from Zed
Click to expand...
Click to collapse
Perhaps, but BusyBox caused me so much chaos in the past due to a double-installation. I was at the point in which I couldn't get it to connect to the computer to flashtool it to fix the damn thing, so my paranoia is fair. XD

UPDATE.
I went ahead and installed the firmware update. As I thought, I've lost root access. Which is fine.
But BusyBox is still installed, heh. Figures.
So I need to know whether DoomLoRD's rootkit would be safe to use in this case.
Advise?
Thanks.

Just go ahead and update. I was also rooted with bootloader locked, and updated via PC Companion and then used DooMLoRD's kit. No problems at all.

hush66 said:
Just go ahead and update. I was also rooted with bootloader locked, and updated via PC Companion and then used DooMLoRD's kit. No problems at all.
Click to expand...
Click to collapse
I took your word for it, and gave the installer a try.
I guess I didn't have anything to worry about after all. I guess I'm set for a good little while, then.
XperienceD, hush66, thank you very much for your help. You've been beyond calming.
Consider this [Resolved.]

[Q] TA Partition backup on new electronic card

Hi all,
I made a backup of my TA partition some time ago and never took time ti unlock my bootloader.
I had to send my SP for repair, and they changed the "electronic card" (I believe this is the motherboard). The phone was working but it would not charge anymore, so I guess the power circuit was burned.
My question is : will my TA partition backup work on my new hardware ? I don't want to do it again if this is not necessary, I just want to move ahead and unlock my bootloader.
Thanks for your answers !

thewild said:
Hi all,
I made a backup of my TA partition some time ago and never took time ti unlock my bootloader.
I had to send my SP for repair, and they changed the "electronic card" (I believe this is the motherboard). The phone was working but it would not charge anymore, so I guess the power circuit was burned.
My question is : will my TA partition backup work on my new hardware ? I don't want to do it again if this is not necessary, I just want to move ahead and unlock my bootloader.
Thanks for your answers !
Click to expand...
Click to collapse
Why to take risk??bro it doesnt even take 5 min for a TA backup..

thewild said:
Hi all,
I made a backup of my TA partition some time ago and never took time ti unlock my bootloader.
I had to send my SP for repair, and they changed the "electronic card" (I believe this is the motherboard). The phone was working but it would not charge anymore, so I guess the power circuit was burned.
My question is : will my TA partition backup work on my new hardware ? I don't want to do it again if this is not necessary, I just want to move ahead and unlock my bootloader.
Thanks for your answers !
Click to expand...
Click to collapse
I would bet that "DRM" keys contained in a TA partition are unique and different for every device. otherwise, we would know what those keys are, and they would not have their said purpose. however, backing up the TA partition takes about few seconds, don't see why you wouldn't make a new backup and be on the safe side. you know, just in case...

I thought I had to be root to backup the TA ? So I have to first root, backup TA, unlock bootloader, re-root...
I think I'll do it, but I'm a bit lazy and I don't like to make unnecessary stuff.

thewild said:
I thought I had to be root to backup the TA ? So I have to first root, backup TA, unlock bootloader, re-root...
I think I'll do it, but I'm a bit lazy and I don't like to make unnecessary stuff.
Click to expand...
Click to collapse
DUDE?! RTFM! You made a whole UNNECESESSARY thread on this forum. :silly::silly::silly::silly:

Robin>Hood said:
DUDE?! RTFM! You made a whole UNNECESESSARY thread on this forum. :silly::silly::silly::silly:
Click to expand...
Click to collapse
What do you mean ? Maybe YOU should RTFM ?
Quote from http://forum.xda-developers.com/showthread.php?t=2292598 (backup TA 9.9) :
Q: Do I need root for this?
A: Yes, you do need root for this to work. I would advice to use @DooMLoRD's excellent Easy Rooting Toolkit for this, when not already rooted.
So yes, there are a lot of steps to backup the TA. Since I'm on .254, rooting is not just one click away, I have to flash kernel, root, reflash kernel.
If someone told me "your backup is fine because the key is linked to that stuff or that stuff and not to the motherboard, so go ahead" I would have avoided unnecessary hastle AND many people would have learned something in the process, like what the TA partition keys are linked to.
Nothing unnecessary, except maybe for your post, right ?

thewild said:
What do you mean ? Maybe YOU should RTFM ?
Click to expand...
Click to collapse
Dude THINK!
The post you link to says to ASK questions about backup TA in that thread, I believe it even has been answered before. :victory:
If you would have used your brain logic would have told you the encryption is unique, you can't just copy the TA partition of one device to another come on, its so simple.
Besides that? Why even bother to unlock the bootloader if you dont want to go through the hassle of installing new / other roms? You know what this website is about? Not about being lazy and stupid but about being inventive and curious. And of course people need to share their information, like I said before, people should take the time to READ, not be LAZY.
So don't be lazy. There's enough fat people in the world Enjoy your phone!:highfive:

Okay guys.. As members, both should know better.
First of all. If you go to this thread: http://forum.xda-developers.com/showthread.php?t=2292598 and read a bit you would know that making a TA backup is VERY IMPORTANT TO DO!
Also read a bit futher. Root is required to use this tool..
And a extra detail YOU CAN NOT I REPEAT CAN NOT USE THE TA BACKUP OF SOMEONE ELSE TO RESTORE YOURS BECAUSE IT WILL HARD BRICK YOUR DEVICE
As stated in the Q&A of that thread:
DevShaft said:
\
Q: Can I use someone else's backup?
A: No, this will hard-brick your device.
Click to expand...
Click to collapse
It is important to read the entire OP/thread to prevent this kind of questions Also read the replies.. They can answer questions for you
Also as an answer to your question:
NO you have an entire new internal system so the files are diffrent. If you havent unlock your bootloader yet make a backup first before doing so and remove the one you already have. I think you will hardbrick your device when you restore your TA backup from before the repair

I know better ^^

OK take it easy guys, it was a simple question meant to have a simple answer.
I should have asked my question in the "backup TA" thread, that's true, but I don't think it was a stupid question.
mrjraider said:
Also as an answer to your question:
NO you have an entire new internal system so the files are diffrent. If you havent unlock your bootloader yet make a backup first before doing so and remove the one you already have. I think you will hardbrick your device when you restore your TA backup from before the repair
Click to expand...
Click to collapse
Thanks, that's the answer I was looking for.
I know TA partitions are unique, the question was whether an electronic card replacement necessarily meant a new TA partition. Does it mean everything changed, from IMEI to hardware keys ? Well, the answer seems to be "yes", but I don't think it was SO obvious.
Thanks again for the answer.

Yes a new motherboard means also a new IMEI..

New N6 shipped with developer build?

Just bought a brand new N6 and its not downloading any ota's, still on 5.0. The build is LNX07M which is a developer build and apparently will not download any ota's. Has anyone heard of this? Did a quick Google search and there is hardly anything about this build.
I have no access to a computer, am I stuck on this build and 5.0?

csdaytona said:
Just bought a brand new N6 and its not downloading any ota's, still on 5.0. The build is LNX07M which is a developer build and apparently will not download any ota's. Has anyone heard of this? Did a quick Google search and there is hardly anything about this build.
I have no access to a computer, am I stuck on this build and 5.0?
Click to expand...
Click to collapse
no access at all?

simms22 said:
no access at all?
Click to expand...
Click to collapse
Not at the moment. What will I need to do?
This is my first nexus device and the last phone I rooted/flashed was the G1 way back in the day.
I was excited to get my phone today so this kind of sucks....

csdaytona said:
Not at the moment. What will I need to do?
This is my first nexus device and the last phone I rooted/flashed was the G1 way back in the day.
I was excited to get my phone today so this kind of sucks....
Click to expand...
Click to collapse
ohh.. that sucks. i remember my g1
i have a way that will probably work out fine, but this way is highly looked down upon on xda. would you be willing to try? btw, im one of those that would look down on this way, unless in certain situations..

simms22 said:
ohh.. that sucks. i remember my g1
i have a way that will probably work out fine, but this way is highly looked down upon on xda. would you be willing to try? btw, im one of those that would look down on this way, unless in certain situations..
Click to expand...
Click to collapse
OK what is it and why is it frowned upon?

csdaytona said:
OK what is it and why is it frowned upon?
Click to expand...
Click to collapse
because its not "proper", and normally isnt used properly. but ill explaine to you the proper way. you can try an app called kingsroot. you csnt get it at the play store, youll have to search google for it. after you install it, then run it, youll have root. but, youre not done yet. you will want to download the latest twrp recovery for the nexus 6 with your phone and keep it there. then you will unstall flashify from the play store. you will now use flashify to flash the twrp recovery. now, last thing, to get your bootloader unlocked. you will install any bootloader unlock apps, like boot unlocker or similar(that might delete everything from your phone), then youre done. ive never tried this on a nexus, but have on other devices, just so you know.

simms22 said:
because its not "proper", and normally isnt used properly. but ill explaine to you the proper way. you can try an app called kingsroot. you csnt get it at the play store, youll have to search google for it. after you install it, then run it, youll have root. but, youre not done yet. you will want to download the latest twrp recovery for the nexus 6 with your phone and keep it there. then you will unstall flashify from the play store. you will now use flashify to flash the twrp recovery. now, last thing, to get your bootloader unlocked. you will install any bootloader unlock apps, like boot unlocker or similar(that might delete everything from your phone), then youre done. ive never tried this on a nexus, but have on other devices, just so you know.
Click to expand...
Click to collapse
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Btw, thanks for helping me out.

csdaytona said:
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Btw, thanks for helping me out.
Click to expand...
Click to collapse
If you can get to a computer, download this: https://dl.google.com/dl/android/aosp/shamu-mra58k-factory-5b07088c.tgz
It's the Marshmallow (6.0) factory image for the Nexus 6. Run the batch file inside and it'll flash your phone. Note that this WILL wipe it.
Here's the actual Google-supplied information on it: https://developers.google.com/android/nexus/images?hl=en

|Jason8| said:
If you can get to a computer, download this: https://dl.google.com/dl/android/aosp/shamu-mra58k-factory-5b07088c.tgz
It's the Marshmallow (6.0) factory image for the Nexus 6. Run the batch file inside and it'll flash your phone. Note that this WILL wipe it.
Here's the actual Google-supplied information on it: https://developers.google.com/android/nexus/images?hl=en
Click to expand...
Click to collapse
First time doing this, but it's OK to jump straight to 6.0?

csdaytona said:
First time doing this, but it's OK to jump straight to 6.0?
Click to expand...
Click to collapse
It'll be fine. It's the complete system image, so it doesn't matter what you're on currently. Note that you will have to install all sorts of extra crap to get the Android SDK installed and working and the proper drivers, but it's not that hard, just gigs of downloads when everything is all said and done.
Like I said, it WILL wipe your phone completely.

csdaytona said:
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Btw, thanks for helping me out.
Click to expand...
Click to collapse
if you can get to a computer..
you can unlock your bootloader with "fastboot oem unlock"
then fastboot flash twrp recovery
then flash a custom kernel wiyh the latest supersu in your new recovery.
and then boot up with root, an unlocked bootloader, and a custom recovery

|Jason8| said:
It'll be fine. It's the complete system image, so it doesn't matter what you're on currently. Note that you will have to install all sorts of extra crap to get the Android SDK installed and working and the proper drivers, but it's not that hard, just gigs of downloads when everything is all said and done.
Like I said, it WILL wipe your phone completely.
Click to expand...
Click to collapse
Not worried about wiping the phone, I've literally only had it for a few hours and nothing is loaded on it.
Would be possible to just install an ota to get me on the right upgrade path? I'm just trying to do the quickest and easiest method possible.

csdaytona said:
Not worried about wiping the phone, I've literally only had it for a few hours and nothing is loaded on it.
Would be possible to just install an ota to get me on the right upgrade path? I'm just trying to do the quickest and easiest method possible.
Click to expand...
Click to collapse
If it's not grabbing an OTA, not sure what else you can do, short of downloading all the OTAs and flashing via recovery. But no guarantee that'll work as you're on a development build... There probably isn't an OTA to go from your development build to a release build.

csdaytona said:
I have no access to a computer, am I stuck on this build and 5.0?
Click to expand...
Click to collapse
simms22 said:
no access at all?
Click to expand...
Click to collapse
csdaytona said:
Not at the moment.
Click to expand...
Click to collapse
csdaytona said:
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Click to expand...
Click to collapse
Dude, come on... I know this is the Q&A section, and were supposed to be nicer here... But this lazyness is bull****.
You act like using a computer is impossible, then as soon as it takes some work.... You can get at one the next day?
Stop expecting to be spoon fed and at least try to learn something fist. There are a TON of write ups on how to do this. You spend how much money on a phone, and now you don't care to educate yourself on it?
Instead of expecting other to do all the work for you, read through the stickied index thread in the general section
http://forum.xda-developers.com/nexus-6/general/nexus-6-index-thread-t3229412
It has a newbie guide that literally holds your hand through the whole process. Post 2 has info on "how to flash factory images", use method 2 as method 1 in that thread will not work with the MM factory image.
Nice people have already spend a lot of time and effort documenting these things for you, as they are common questions. People like Simms and the other posters in this thread answer questions and offer support for free out of the kindness of their heart... Don't create extra work for them by ignoring all the effort already put out by other members, expecting it all to be regurgitated to you.
|Jason8| said:
If it's not grabbing an OTA, not sure what else you can do, short of downloading all the OTAs and flashing via recovery. But no guarantee that'll work as you're on a development build... There probably isn't an OTA to go from your development build to a release build.
Click to expand...
Click to collapse
Fastboot, as described in the threads mentioned above, will completely overwrite the pertinent partitions, regardless of what was there... dev build or not. No need to flash and apply countless incremental updates. Google provides not only full system images, but the information to use them on their web page...

|Jason8| said:
If it's not grabbing an OTA, not sure what else you can do, short of downloading all the OTAs and flashing via recovery. But no guarantee that'll work as you're on a development build... There probably isn't an OTA to go from your development build to a release build.
Click to expand...
Click to collapse
Gotcha. I'll try to flash 6.0 tomorrow. Wish me luck.
Thanks for the help!

scryan said:
Fastboot, as described in the threads mentioned above, will completely overwrite the pertinent partitions, regardless of what was there... dev build or not. No need to flash and apply countless incremental updates. Google provides not only full system images, but the information to use them on their web page...
Click to expand...
Click to collapse
I linked him to that already. No need to be a **** about it. He was looking for an easy way to do it now, when he doesn't have a computer. **** got crazy, so he asked if it would be easier with a computer, which the answer is yes.
Wouldn't you be excited as **** if you had a new phone? Wouldn't you want to get it up and running as quickly as possible? Well... now he's gotta wait until he has a computer. Obviously installing an OTA and doing the incremental updates would be easier, which is what he was looking for. Since that's not an option, we laid out other ways to go about doing it. So he's getting to a computer tomorrow.
---------- Post added at 09:51 PM ---------- Previous post was at 09:50 PM ----------
csdaytona said:
Gotcha. I'll try to flash 6.0 tomorrow. Wish me luck.
Thanks for the help!
Click to expand...
Click to collapse
No problem man. I wish you luck!
If you do plan on modding it/rooting it/romming it in the future, DEFINITELY unlock your bootloader before you set up the phone or that'll wipe it, too.

|Jason8| said:
Wouldn't you be excited as **** if you had a new phone? Wouldn't you want to get it up and running as quickly as possible? Well... now he's gotta wait until he has a computer. Obviously installing an OTA and doing the incremental updates would be easier, which is what he was looking for. Since that's not an option, we laid out other ways to go about doing it. So he's getting to a computer tomorrow.
Click to expand...
Click to collapse
You act like I was born with a nexus 6... It was a new phone to me too. I was so excited I read as much as I could on it, thanking the people who were so gracious to spend their personal time writing guides so I could understand the process well enough to be comfortable with my phone and help others here.

scryan said:
Dude, come on... I know this is the Q&A section, and were supposed to be nicer here... But this lazyness is bull****.
You act like using a computer is impossible, then as soon as it takes some work.... You can get at one the next day?
Stop expecting to be spoon fed and at least try to learn something fist. There are a TON of write ups on how to do this. You spend how much money on a phone, and now you don't care to educate yourself on it?
Instead of expecting other to do all the work for you, read through the stickied index thread in the general section
http://forum.xda-developers.com/nexus-6/general/nexus-6-index-thread-t3229412
It has a newbie guide that literally holds your hand through the whole process. Post 2 has info on "how to flash factory images", use method 2 as method 1 in that thread will not work with the MM factory image.
Nice people have already spend a lot of time and effort documenting these things for you, as they are common questions. People like Simms and the other posters in this thread answer questions and offer support for free out of the kindness of their heart... Don't create extra work for them by ignoring all the effort already put out by other members, expecting it all to be regurgitated to you.
Fastboot, as described in the threads mentioned above, will completely overwrite the pertinent partitions, regardless of what was there... dev build or not. No need to flash and apply countless incremental updates. Google provides not only full system images, but the information to use them on their web page...
Click to expand...
Click to collapse
i have absolutely no computer nor laptop access, so i completely understand(understood) his side as well.

scryan said:
You act like I was born with a nexus 6... It was a new phone to me too. I was so excited I read as much as I could on it, thanking the people who were so gracious to spend their personal time writing guides so I could understand the process well enough to be comfortable with my phone and help others here.
Click to expand...
Click to collapse
He googled his build number and didn't get many hits on it. So he's asking if there's a way to get it up and running tonight without a computer. Seems valid to me. You jump into the thread offering no help at all and start talking **** about the guy. That's the exact opposite of what you're saying you strive to do. I don't get it.

simms22 said:
i have absolutely no computer nor laptop access, so i completely understand(understood) his side as well.
Click to expand...
Click to collapse
At that point its a legitamate question. This is a very different situation that is not well covered here, and requires a unique solution not many would come up with.
But "I absolutely have no computer nor laptop access" is pretty different then "I can access one TOMORROW. Sheesh, having something 1 day away is pretty far from it not being a possibility.
And I think you would agree it would be a significantly better idea to wait that day then to proceed with the method you gave (not that it was bad of you to give it... but you tried to differentiate and he held out to avoid being told to do it the hard way)
|Jason8| said:
He googled his build number and didn't get many hits on it. So he's asking if there's a way to get it up and running tonight without a computer. Seems valid to me. You jump into the thread offering no help at all and start talking **** about the guy. That's the exact opposite of what you're saying you strive to do. I don't get it.
Click to expand...
Click to collapse
We are told time and time again that their are no bad questions. Truth is there are more bad questions then good ones.
Him asking about a build that provides few google hits is very legitimate.
Him asking about doing it without a computer because he doesn't have one is legitimate.
It only becomes an issue when he doesn't get the answer he wants, and all of a sudden he does have computer access.
And given that he is going to proceed in a computer... It becomes nothing more then "How do I update my phone?", which is VERY well documented.
I not only gave him the link to the information he needed, AND even corrected the information pointing out that the flashall script fails and that he would need to use the second method listed in the instructions I linked him to (since I know he will likely have limited time to fail and figure out whats wrong)
"That's the exact opposite of what you're saying you strive to do. I don't get it."
Then let me explain.
Would you skip your homework, ignore your textbook, then show up to class asking your teacher to explain it again? We are here to help... but how or why should I care more about it then he does? With no attempt made to learn, how much should I care to teach him?
Its a pretty big **** you to all those who have spend countless hours documenting this stuff to help new people to ignore their work and tell someone to do it again.