Database Develop

Help Me Please

I feel I've made a terrible (and stupid) mistake. I decided to unroot my phone from cyanogen roms. I read a how to guide that I guess was outdated because now I have android 1.0 firmware. The guidw was [how to] unroot by tubaking182 (absolutely zero offense to him, not his fault, I'm stupid, etc etc.) So I now have stock version 1.0. There's no check for system updates under about phone in settings so I can't do that. There are file manager apps that I could use to rename the necessary updates into update.zip, but there's no apps available like download crutch so I can download them. I also can't enter recovery. It gives me a triangle with an exclamation inside next to a image of a phone and that's it and I have no idea how to install an update without recovery mode. As I'm sure you've noticed by now, I'm the epitome of newb and feel free to laugh at my failure. I just really need someone to help me and would be eternally grateful. In all likelihood, I'll need step by step instructions on what to do. I know this is a lot to ask and I've really done nothing to earn this help... I really just need assistance. Thank you to anyone who helps me in advance

Not to be an asshole and say "Shoulda Coulda Woulda" but you really should have done your research before embarking on bricking your phone.

ItsAndroidsWorld had many videos on You Tube. Look for ones on how to root, then how to install the death spl, then look for the ones with Super D or FastTest .. as it seems as though they are probably the best roms for everyday use at this point.
I've found that using these videos via You Tube is the easiest way to go.
Good Luck.
^^^ ABOVE POST stolen from another similar thread.

psyko-m1 said:
Not to be an asshole and say "Shoulda Coulda Woulda" but you really should have done your research before embarking on bricking your phone.
Click to expand...
Click to collapse
he didn't brick his phone, don't scare him
To OP: The same happened to me when I was a n00b at this ****.
Dude, google is your friend.
Calm down.

tsk tsk tsk.....Im gonig to say this....WRONG SECTION
but I will be nice as well. just find the updates on google from 1.0 to 1.5 and oh yeah to get back into recovery from the triangle withthe !...alt L...but if you somehow brick ya phone youe fault not mine next time do ya research before you mess with ya phone

Technically speaking he is in a DEFCON 2 "Brick" situation.
Sorry.

psyko-m1 said:
Technically speaking he is in a DEFCON 2 "Brick" situation.
Sorry.
Click to expand...
Click to collapse
Well he's in the wet cement

SeEsAw12 said:
Well he's in the wet cement
Click to expand...
Click to collapse
Or...
You are late for work and have a flat...

click on this http://theunlockr.com/category/howto/android_how_tos/htc-mytouch-3g-magic/:cool:

remove the cool http://theunlockr.com/category/howto/android_how_tos/htc-mytouch-3g-magic/

this website should help you get back on track and you just need to download the nbh file to get it back to cupcake

BUT 0MGAWWZZZ N00BZORZ DO3S 1.0 HAVE A DA SENSE RAOM???
in all seriousness, there's nothing actually wrong with your phone. You completely unrooted it. By following the aforementioned instructions, it'll be easy to reroot and update. What I DO find weird is why you're not getting 1.5 OTA...

although i hate when people post in the wrong section - im in a good mood this morning
http://zenthought.org/content/project/flashrec
not sure if it works in 1.0 - it should as it uses a rather old bug to do so

Easy as pie...just follow the guide in my sig.
=)

To those who say I bricked it, I know that's not the case it still works so I obviously didn't brick it... not that fail thankfully.
To thenameismax, AHA! I did not know about alt+l retrieving text so thank you thank you thank you. I just need to get the necessary updates and copy them to sd card root, rename update.zip/install one at a time... I think lol
Thanks again to all who helped and sorry about the wrong section. When I was rooting, it was in development. I assumed that unrooting would be too and therefore problems with that... further fail.

afiellerddr said:
To those who say I bricked it, I know that's not the case it still works so I obviously didn't brick it... not that fail thankfully.
To thenameismax, AHA! I did not know about alt+l retrieving text so thank you thank you thank you. I just need to get the necessary updates and copy them to sd card root, rename update.zip/install one at a time... I think lol
Thanks again to all who helped and sorry about the wrong section. When I was rooting, it was in development. I assumed that unrooting would be too and therefore problems with that... further fail.
Click to expand...
Click to collapse
yeah man no problem. good luck.

Don't do anything. In a day or two you get an OTA update.
You can force the update like people have mentioned, but as long as you can hold off for a day or two you dont need to.
BTW, at some point you will see the E or 3G icon downloading like crazy and you dont know why. It is downloading the update. Stay away from task killers and in my experience it is good to be around wifi.
Just relax.

Sent Move Request

[Q] Nexus 6 Rooting Help

I just received my Nexus 6 that I bought from Best Buy yesterday and have got it activated today.
I really want to root and try flashing my first rom. I have been reading thread after thread trying to learn and understand what it takes to root a Nexus 6, flash a rom, and what the proper way to do it is. Spent at least 5 hours reading threads and I have been so confused as to what to do.
First, I have read that you should do the ADB way to unlock, root, flash etc. (Nexus 6 all in one Beginners Guide) because using a toolkit will make flashing roms more trouble than its worth.
Next, I have read repeatedly that the method used when the Nexus 6 first came out is still a valid and perfectly fine way to unlock, root, flash, etc , but then I have found in another thread that in order to root it you will need to flash a custom kernal of some sort so i'm unsure what I need to do.
The Nexus 6 All-in-One Beginners Guide seems pretty straightforward and easy, however this is my first time flashing anything and rooting a Nexus device so i'm unsure what I should trust.
Thanks in advance for anyone willing to help give this newbie some advice.
Any help is appreciated, I am just frustrated with trying to find a current method of unlocking, rooting, flashing, etc because nearly every thread I have read is dated back to when the device first came out and I usually am able to learn visually very easily but many videos for the N6 on youtube are from when the N6 came out, dating back 6-9 months ago.
So again, any help would be greatly appreciated because I am getting a bit frustrated with sorting out all the information and learning what I can trust so I don't damage my phone beyond repair.
Thank you again for reading and giving advice if you choose to and I apologize if this sounded like a rant. I just really need some help understanding what to do. Thank you.
If anyone is able to clear up my confusion on the issues I brought up, thank you.

1. Use Wugs to unlock and root
(Sure knowing how to adb is important, but just do that)
2. Wugs will install a custom recovery - you flash roms in said recovery.
3. Apps I recommend you get after obtaining root:
(Some paid, some free)
SuperSU Pro (paid)
Buaybox Pro (paid)
Root Explorer (paid)
Titanium Backup (paid/free)
Then you'll have a pretty good start at supporting the devs, while having a good file/folder control app, and a way to protect yourself against data loss - with a simple way of reverting back to a previous build should you dislike a rom.
Keep reading. You're off to a gold start but I learn more and more every day. Never underestimate the value of reading everything prior to flashing/modifying it just might save you a headache when your phone inevitably bootloops for a silly reason.

iRub1Out said:
1. Use Wugs to unlock and root
(Sure knowing how to adb is important, but just do that)
2. Wugs will install a custom recovery - you flash roms in said recovery.
3. Apps I recommend you get after obtaining root:
(Some paid, some free)
SuperSU Pro (paid)
Buaybox Pro (paid)
Root Explorer (paid)
Titanium Backup (paid/free)
Then you'll have a pretty good start at supporting the devs, while having a good file/folder control app, and a way to protect yourself against data loss - with a simple way of reverting back to a previous build should you dislike a rom.
Keep reading. You're off to a gold start but I learn more and more every day. Never underestimate the value of reading everything prior to flashing/modifying it just might save you a headache when your phone inevitably bootloops for a silly reason.
Click to expand...
Click to collapse
Thank you for your advice. May I ask the difference of doing it with a Toolkit rather than the ADB way ? It just seems that one is easier than the other.
May I ask the pros and cons of doing it the Toolkit way and the ADB way ?

Iandrew124 said:
Thank you for your advice. May I ask the difference of doing it with a Toolkit rather than the ADB way ? It just seems that one is easier than the other.
May I ask the pros and cons of doing it the Toolkit way and the ADB way ?
Click to expand...
Click to collapse
The adb way teaches you how to do it at the base level - this method would allow you to pull files/folders without the phone booting, or flash individual partitions without having to flash a whole image - there's a LOT of reasons to know and understand adb, and you eventually should, as it could save your phone when all else fails.... It has its benefits, but for simplicity's sake - for now - just use Wugs.
Using toolkits in effect gives you a crutch. With this crutch you then are forced to depend on this crutch for future needs. What happens when you get a update or different phone that Wugs doesn't work with or do what you need to do? THATS where adb understanding would come in handy.
I NEVER recommend people use toolkits exclusively as this can and WILL eventually lead to major issues that the user is now at step 1 of the learning process all over again - or - are forced to wait for toolkits to be made to do something as simple as obtain root. That's annoying.
In this case, I hope you will make yourself more familiar with adb when you can, use it, try it out, understand what it does and what it's for - but just to get you up and running you can use the kit, just don't expect it to be that easy every time because, I promise you, it won't be and at some point adb will be the only option you have. You don't want to have to be in a panic situation when that knowledge could have saved you.
That's just how I like to help people learn this stuff. Start off slow just so they can do what they want to do - but heavily stress the importance of HOW that toolkit works - because its doing what you need to learn how to do - it just does it all for you.
Don't rely on that crutch - it won't always be there.

Iandrew124 said:
. . .
May I ask the pros and cons of doing it the Toolkit way and the ADB way ?
Click to expand...
Click to collapse
Manual flashing has the advantage that you controls the 'speed of the process. Because you have to enter commands one by one.
Toolkits use scripts instead of commands. And you have a choice from many options.
You won't be fast enough to stop when using a wrong option/script.
The post of irub1out is a good method.
After point 1. wait a day and go on with reading and posting.

adb is not used in the rooting process. fastboot is used to unlock the bootloader and then flash a custom recovery.
It's a really simple process after installing fastboot.
1. fastboot oem unlock
2. fastboot flash recovery recovery.img
3. Put SuperSU flashable zip on sdcard
4. Boot into recovery and flash that zip
There really shouldn't be any need to use a toolkit and if you do it manually, you KNOW your computer is configured properly so if you need it for recovery purposes later and something is not working, you know it's not the computer that is the issue.
Use the toolkit for other things once you've done the unlock and flash manually by all means. But NEVER use the toolkit first. This is a recipe for disaster.
Although the previous posts stress the importance of learning manually, they kind of miss part of the point as to why and I bet 90% of our experienced users here will agree with me...NO SHORTCUTS FIRST TIME.
If you need more info on fastboot, there's an adb and fastboot thread in general > sticky roll-up thread.

I concur with @danarama. We spend half our time in this forum trying to fix mistakes made with toolkit.

really, if the user doesnt have the proper knowledge to make the simple choices given in the toolkit, they are not going to choose the right files to do it manually.
so it makes no difference really, other than the person gaining the knowledge to understand exactly what they are doing, which i agree with,
but regardless of what any user might claim, the toolkit doesnt make mistakes. it executes the same commands you would use manually via a script based on your choices.
there is no margin of error other than the users input.

j
bweN diorD said:
really, if the user doesnt have the proper knowledge to make the simple choices given in the toolkit, they are not going to choose the right files to do it manually.
so it makes no difference really, other than the person gaining the knowledge to understand exactly what they are doing, which i agree with,
but regardless of what any user might claim, the toolkit doesnt make mistakes. it executes the same commands you would use manually via a script based on your choices.
there is no margin of error other than the users input.
Click to expand...
Click to collapse
first off, toolkits DO occasionally make mistakes, it has been proven, so dont argue with that. sure, its not always, but it happens. secondly, the user choosing files.. ok, if you do it the right way, there are only two files you need. and the user doesnt have a choice to pick them. they are the twrp recovery, and supersu. the user has to go find them, not pick out of a list. and witj my time on the n6 since last November, not one person picked the wrong files to root their phones. again, its because they arent given a choice.

bweN diorD said:
it makes no difference really, other than the person gaining the knowledge to understand exactly what they are doing
Click to expand...
Click to collapse
...and to ensure fastboot is Working, as I mentioned in my post. So it does make a difference.

a person gaining knowledge to understand what they are doing is by far the most important thing that can happen. thats something thatll never happen with a root toolkit.

Iv'e had several good flashes and some bad using the exact same files and same options during testing and playing. Worst button/option to even be available to noobs is the lock after flash or even a relock button at all. Remove that option and you are pretty much safe from hard brick. Then only have to come back and ask us to walk through fastboot when the flash goes belly up. Need an audit on how many times we have seen this exact scenario.

prdog1 said:
Iv'e had several good flashes and some bad using the exact same files and same options during testing and playing. Worst button/option to even be available to noobs is the lock after flash or even a relock button at all. Remove that option and you are pretty much safe from hard brick. Then only have to come back and ask us to walk through fastboot when the flash goes belly up. Need an audit on how many times we have seen this exact scenario.
Click to expand...
Click to collapse
That's another good point.. When 5.1 came out and locking the bootloader after flash, if it didn't boot, it would be a brick.. Toolkits would do this after a flash and brick phones.. You have to wait until the toolkit is updated before using it safely.

simms22 said:
j
first off, toolkits DO occasionally make mistakes, it has been proven, so dont argue with that. sure, its not always, but it happens. secondly, the user choosing files.. ok, if you do it the right way, there are only two files you need. and the user doesnt have a choice to pick them. they are the twrp recovery, and supersu. the user has to go find them, not pick out of a list. and witj my time on the n6 since last November, not one person picked the wrong files to root their phones. again, its because they arent given a choice.
Click to expand...
Click to collapse
i sir, will argue with whatever i wish.
in the year i maintained a toolkit for the last moto i had, 20k+ downloads, not one user accused the toolkit of flashing something it wasnt supposed to. the code is fairly simple, one option points to a command and file (simply put), etc. etc.
is it possible some one in a million error happened, doubtful but ok.
my comment was more directed at the previous poster who said something about spending 1/2 his time helping users with toolkit problems.
thats very unlikely, unless the toolkit coding is done very poorly.
---------- Post added at 12:27 PM ---------- Previous post was at 12:25 PM ----------
danarama said:
...and to ensure fastboot is Working, as I mentioned in my post. So it does make a difference.
Click to expand...
Click to collapse
how about you quote the rest of my sentence next time, where i agreed with your logic on that.
unless your intentionally trying to start an argument? cause thats what it looks like.

bweN diorD said:
how about you quote the rest of my sentence next time, where i agreed with your logic on that.
Click to expand...
Click to collapse
Because the rest of your sentence was nothing to do with what I wanted to say and you didn't agree with my logic at all. In fact your sentence (even complete) suggests that what I had said wouldn't even factor in to anything.
bweN diorD said:
unless your intentionally trying to start an argument? cause thats what it looks like.
Click to expand...
Click to collapse
I'm 35 years old. I've got better things to do than try to create arguments in Internet forums. I was expanding on your sentence on something you missed. Kick yourself for the omission, not me for pointing it out.
Don't be so bloody confrontational. You're coming off as a petulant child, as does everyone who starts a sentence "how about" without trying to understand what they're talking about first.

bweN diorD said:
i sir, will argue with whatever i wish.
in the year i maintained a toolkit for the last moto i had, 20k+ downloads, not one user accused the toolkit of flashing something it wasnt supposed to. the code is fairly simple, one option points to a command and file (simply put), etc. etc.
is it possible some one in a million error happened, doubtful but ok.
my comment was more directed at the previous poster who said something about spending 1/2 his time helping users with toolkit problems.
thats very unlikely, unless the toolkit coding is done very poorly.
Click to expand...
Click to collapse
if i can get someone that will make a toolkit that does what it does, and goes through every step explaining the process of what its doing and how to do it manually, id be a happy man. seriously.

danarama said:
Because the rest of your sentence was nothing to do with what I wanted to say and you didn't agree with my logic at all. In fact your sentence (even complete) suggests that what I had said wouldn't even factor in to anything.
I'm 35 years old. I've got better things to do than try to create arguments in Internet forums. I was expanding on your sentence on something you missed. Kick yourself for the omission, not me for pointing it out.
Don't be so bloody confrontational. You're coming off as a petulant child, as does everyone who starts a sentence "how about" without trying to understand what they're talking about first.
Click to expand...
Click to collapse
funny, it looks like i am agreeing with the manual logic...
other than the person gaining the knowledge to understand exactly what they are doing, which i agree with,
Click to expand...
Click to collapse

simms22 said:
if i can get someone that will make a toolkit that does what it does, and goes through every step explaining the process of what its doing and how to do it manually, id be a happy man. seriously.
Click to expand...
Click to collapse
I honestly considered making that in the past.
---------- Post added at 05:44 PM ---------- Previous post was at 05:37 PM ----------
bweN diorD said:
funny, it looks like i am agreeing with the manual logic...
Click to expand...
Click to collapse
That's not what we're talking about. I never said you didn't agree with the "manual logic"
Please re-read my post. I think you've misunderstood what I said. Let me know if you'd like me to explain what were talking about afterwards if you still dont understand

Tbh, not using toolkits comes down to this:
Its the easiest ****ing thing ever to do with out one. If you need one, you have a major gap in your understanding... And you need to fix that first. Well you don't "need" to unfortunately, but acquiring root access is taking over being the admin for your device. If you are choosing to do that, you should probably understand the basic tools.

I am in approximately the same position as the OP with a brand new Nexus 6 and I have a question. Should I take any OTA updates that are available before starting the unlock bootloader and rooting process?

Still waiting for Marshmallow...

I still haven't received the OTA and Marshmallow update, and am starting to wonder if something is wrong with my device.
I'm in England, my N6 is unlocked, my SIM is "3".
Is anyone else here still waiting for Marshmallow? Or can anyone offer any advice, please?

Unlocked and 100% stock?

danarama said:
Unlocked and 100% stock?
Click to expand...
Click to collapse
I'm sorry, I don't understand your response. The answer to my question was not mentioned in the opening posts of the thread I posted in, which is why I posted!! Are you saying I missed a thread? In which case my apologies, and I would be grateful to know which thread that is. Otherwise I don't understand what you're trying to tell me.

AidanBell said:
I'm sorry, I don't understand your response. The answer to my question was not mentioned in the opening posts of the thread I posted in, which is why I posted!! Are you saying I missed a thread? In which case my apologies, and I would be grateful to know which thread that is. Otherwise I don't understand what you're trying to tell me.
Click to expand...
Click to collapse
You said your phone was unlocked. I am asking if it is 100% stock? Stock means unmodified.

danarama said:
You said your phone was unlocked. I am asking if it is 100% stock? Stock means unmodified.
Click to expand...
Click to collapse
I do apologise. Your signature about XDA mantras was so huge that I actually missed your question above it!!
The answer is yes, it's 100% stock, unmodified. The only thing that may be pertinent is that I'm on the Marshmallow developers preview. I've had all three previews; numbers two and three came across over the air perfectly. There's just no sign now of the official build.

AidanBell said:
I do apologise. Your signature about XDA mantras was so huge that I actually missed your question above it!!
The answer is yes, it's 100% stock, unmodified. The only thing that may be pertinent is that I'm on the Marshmallow developers preview. I've had all three previews; numbers two and three came across over the air perfectly. There's just no sign now of the official build.
Click to expand...
Click to collapse
Preview doesn't get official build OTA's
You'll have to flash the stock system and boot.img of the official build

danarama said:
Preview doesn't get official build OTA's
You'll have to flash the stock system and boot.img of the official build
Click to expand...
Click to collapse
Oh, I never knew that. Thank you very much.

This is a pig for me, then, as I don't have much experience in flashing and was hoping very much not to have too. However, that appears to be my only option, therefore can anyone please point me in the direction of a step-by-step guide for flashing Marshmallow onto a Nexus 6 (including making sure I choose the right version in the first place!)?

AidanBell said:
This is a pig for me, then, as I don't have much experience in flashing and was hoping very much not to have too. However, that appears to be my only option, therefore can anyone please point me in the direction of a step-by-step guide for flashing Marshmallow onto a Nexus 6 (including making sure I choose the right version in the first place!)?
Click to expand...
Click to collapse
The same way you got the dev preview on there I guess.
See the first post at http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 In step 5, use Method 2

AidanBell said:
This is a pig for me, then, as I don't have much experience in flashing and was hoping very much not to have too. However, that appears to be my only option, therefore can anyone please point me in the direction of a step-by-step guide for flashing Marshmallow onto a Nexus 6 (including making sure I choose the right version in the first place!)?
Click to expand...
Click to collapse
Did you actually buy your phone with M Preview?

AidanBell said:
This is a pig for me, then, as I don't have much experience in flashing and was hoping very much not to have too. However, that appears to be my only option, therefore can anyone please point me in the direction of a step-by-step guide for flashing Marshmallow onto a Nexus 6 (including making sure I choose the right version in the first place!)?
Click to expand...
Click to collapse
Just fastboot flash the system and boot images.
Go to Nexus 6 General > Sticky roll-up thread > adb and fastboot. What is it?
This will tell you how to set up fastboot and what it is (and how to use it.). Then flash the system.img and boot.img

AidanBell said:
I'm sorry, I don't understand your response. The answer to my question was not mentioned in the opening posts of the thread I posted in, which is why I posted!! Are you saying I missed a thread? In which case my apologies, and I would be grateful to know which thread that is. Otherwise I don't understand what you're trying to tell me.
Click to expand...
Click to collapse
Nah, that's his big sig, The message is one line, the sig is many lines and huge font

aiiee said:
Nah, that's his big sig, The message is one line, the sig is many lines and huge font
Click to expand...
Click to collapse
Huge for a good reason

danarama said:
Huge for a good reason
Click to expand...
Click to collapse

Many thanks for the help and comments, guys.
Yes, I bought the phone from the Phones Show Chat forum. So it was the previous owner who flashed the first preview build, not me.
I guess I have no choice, then, but to have a go at flashing the official build.
I'm not a complete newbie or an idiot, I'm confident that I can do it, but I would have preferred a step-by-step guide that doesn't presume any prior knowledge or experience. The one recommended by Jj14 still assumes a little too much for my liking. If I step a single foot off the correct path, I'll have no idea how to recover. If anyone can recommend another, safer, version I'd be most grateful.

AidanBell said:
I'm not a complete newbie or an idiot, I'm confident that I can do it, but I would have preferred a step-by-step guide that doesn't presume any prior knowledge or experience. The one recommended by Jj14 still assumes a little too much for my liking. If I step a single foot off the correct path, I'll have no idea how to recover. If anyone can recommend another, safer, version I'd be most grateful.
Click to expand...
Click to collapse
You can find the factory images here: https://developers.google.com/android/nexus/images?hl=en#shamu
There are the instructions how to flash it, but ignore the last step of locking the bootloader. If something goes wrong, and can't boot it, you can have a nice brick in your hands.
Save all your data! The flashing process will wipe it completely.
There's not magic needed, just fastboot. Turn your phone off, press down and power, until the "Fastboot flash mode" screen comes up. Then follow the instructions.
A couple of things explained:
1. The bootloader for the M preview and MRA58K were the same, but the MRA58N one might be new. I didn't try it.
2. if you unpack the "flash all" zip file, you can do the flashing by hand yourself, you can skip userdata if you don't want your device fully wiped, but then you must do a factory reset.
And if something is not clear, please feel free to ask anything. It's better to be sure than being modest and have a nice brick.
Edit: The bootloaders are the same bit for bit as the preview.
And the three official packages 58k, 58n, and 58r have the same radios.
58n is the security patch it is noted in the AOSP source too, and nobody knows what 58r is, but it can be for Verizon. But I'm not sure.

Continued thanks.
Still very nervous and somewhat out of my depth, but here goes nothing.
And ... fell at the first hurdle!
Can someone please tell me which version I need; "MRA58K", "MRA58N" or "MRA58R"?

Always the newest. MRA58K was the first Marshmallow factory image. MRA58N is the 1st November securty update, and so far nobody knows what 58R is. People are guessing here:
http://forum.xda-developers.com/nexus-6/help/mra58r-build-t3242328

I found this excellent step-by-step guide, and followed it carefully. Result ... I now have official Marshmallow.
http://www.digitaltrends.com/mobile/how-to-install-android-factory-image
So, I recommend that page to anyone else who, like me, needs a guiding hand. And I thank very much everyone in this thread for your help and encouragement.
Cheers,
Aidan

I'm stuck on LVY48I ( 5.1.1 )
don't know why it's too long to get the update !!
My Nexus totally stock.

not really a noob, but still confused anyway... need a little help from my friends...

Project Fi Nexus 6 rooted here on 5.1.1 LVY48E
I keep getting a notice that a system update has been downloaded (29.1) megs..a tad annoying
Would like to run the update, but can't because of TWRP... Also would like to try 6.0 if it is out, just don't want to lose root, and or have to have my phone reset...
I have Wug's nexus root toolkit too
How do I update to the latest L and or/ M???
Looking for some friendly advice....
Thanks!

Forgot to mention that I have tried flashing the update manually to no avail..
Drumrjoe

You can't update your rooted phone with Ota update, only way is to flash the factory image, download latest Nexus 6 factory image from Google and flash it with the tool kit, if you don't know how to flash a factory image, you should see the main thread

And I believe , given the need for a modified boot when rooting Marshmallow, you lose the OTA anyway, no?

aiiee said:
And I believe , given the need for a modified boot when rooting Marshmallow, you lose the OTA anyway, no?
Click to expand...
Click to collapse
Thanks for the help! Been using the toolkit to try and flash stock + unroot...
It doesn't seem to be working for me... First tried to update to last version of lollipop.. runs the batch updater after downloading the factory image and extracting.. batch window closes after awhile I wait after no change to phone or toolkit and nothing has changed on phone... tried this with marshmallow too... same thing....
At a loss..

drumrjoe said:
Thanks for the help! Been using the toolkit to try and flash stock + unroot...
It doesn't seem to be working for me... First tried to update to last version of lollipop.. runs the batch updater after downloading the factory image and extracting.. batch window closes after awhile I wait after no change to phone or toolkit and nothing has changed on phone... tried this with marshmallow too... same thing....
At a loss..
Click to expand...
Click to collapse
Just do it manually using fastboot. Or since you have TWRP, find a pre-rooted rom.zip you can flash from there.

Lately half the threads are about a toolkit not working. There should be a sticky about this: Don't use toolkits on Nexus phones! Those who don't feel secure enough to enter three lines in a command line/terminal really shouldn't use toolkits either. It gives a feeling of false security for a price of being totally at loss if anything goes wrong. And things do go wrong.

istperson said:
Lately half the threads are about a toolkit not working. There should be a sticky about this: Don't use toolkits on Nexus phones! Those who don't feel secure enough to enter three lines in a command line/terminal really shouldn't use toolkits either. It gives a feeling of false security for a price of being totally at loss if anything goes wrong. And things do go wrong.
Click to expand...
Click to collapse
We try to advise people not to use rootkits or kits of any kind. It does nothing but hinder their efforts if something goes wrong. In the end it is people being lazy and then bricks happen and they have no idea what to do.

zelendel said:
We try to advise people not to use rootkits or kits of any kind. It does nothing but hinder their efforts if something goes wrong. In the end it is people being lazy and then bricks happen and they have no idea what to do.
Click to expand...
Click to collapse
I think many of us here agree with that. To avoid bashing, we have to say "use them if you like, but learn to use fastboot manually first". But all the work we collectively put in to that as a majority is easily undone when just one person replies "use a toolkit". It almost always ends up in a debate that is so long that when it reaches it's conclusion, the OP ended up using a toolkit anyway.,

danarama said:
I think many of us here agree with that. To avoid bashing, we have to say "use them if you like, but learn to use fastboot manually first". But all the work we collectively put in to that as a majority is easily undone when just one person replies "use a toolkit". It almost always ends up in a debate that is so long that when it reaches it's conclusion, the OP ended up using a toolkit anyway.,
Click to expand...
Click to collapse
I know. All we can do is advise and the lazy will still be lazy and then end up with issues. This is why you will see people post about issues and then the min they mention they have used a root kit all replies stop. There are many of us that refuse to help people that have used a root kit. It shows they should not be messing around with their devices if they dont have the time to learn to do things properly.

Duly noted -
But seriously, thanks for the info.. will be figuring this out!
Best all
DJ

Update-
Sincere thanks to all that replied.. Did not know that the toolkit's were a nono-
I did use the command line to manually update and all is well. I am on LVY48I now and rooted.. Next is to reinstall the latest xposed for 5.1.1.
Also, tried finding a stock pre-rooted marshmallow, but didn't really have any luck with that... any pointers or links?
TIA

drumrjoe said:
Update-
Sincere thanks to all that replied.. Did not know that the toolkit's were a nono-
I did use the command line to manually update and all is well. I am on LVY48I now and rooted.. Next is to reinstall the latest xposed for 5.1.1.
Also, tried finding a stock pre-rooted marshmallow, but didn't really have any luck with that... any pointers or links?
TIA
Click to expand...
Click to collapse
Not 100% sure of this but I believe that Marshmallow will not achieve root without some modification. At least I couldn't

Take down the chainfire root process for lolllipop!

Someone has to do something about this. Beginners like myself are bricking their phones every day and getting frustrated. Sure there is a fix but with how hard this is to learn for beginners its really frustrating.
Edit: This was meant to try to help beginners understand that the chainfire root method is for Lollipop and not for Marshmallow. I do not believe this should be taken down, just labeled for Lollipop so beginners don't soft brick their phones using this guide on a phone with Marshmallow.

Clay said:
Someone has to do something about this. Beginners like myself are bricking their phones every day and getting frustrated. Sure there is a fix but with how hard this is to learn for beginners its really frustrating.
Click to expand...
Click to collapse
root process for lollipop..
unlock your bootloader
fastboot flash twrp recovery
flash supersu via your new recovery
reboot and youll have root.
how hard is that? if its too hard, id suggest doing some reading about the process first, its all over google.

There's a new post every day about someone following the root process for lollipop when they have Marshmallow. I am far from computer illiterate and from the number of posts on this I think it speaks for itself.
At least label it more obviously that it's for lollipop.

I used chainfires root method and personally I don't see how anyone that's got a brain could screw this up. All ya gotta do is read and read then read some more. It's not hard people's . Chainfires method is about as simple as it can get. @Chainfire is a genius I hope he doesn't see this post, hell I'm embarrassed for him.
Sent from my HTC6600LVW using Tapatalk

the difference bwtween lollipop and marshmallow is that you also have to flash a custom kernel in twrp right before you flash supersu. besides that, its identicle.

I'm agree with you if you're talking about Android M. It's really crazy.
But as far as I remember, there was no notable obstacle on LP version root.
Unlock bootloader. Flash recovery and flash supersu....any other step?
If they are not familiar with adb, I guess they may face trouble. Actually the problem occurs from the start at downloading adb tool(platform_tools on SDK) with that sucking google tool.
..However, if they are, they shouldn't do root. It's too risky if they don't even know the basics.

So the instructions for how to root lollipop should be removed because some people don't take the time to read everything and confirm which version of Android they have on their phone?

PielunA said:
I'm agree with you if you're talking about Android M. It's really crazy.
But as far as I remember, there was no notable obstacle on LP version root.
Unlock bootloader. Flash recovery and flash supersu....any other step?
If they are not familiar with adb, I guess they may face trouble. Actually the problem occurs from the start at downloading adb tool(platform_tools on SDK) with that sucking google tool.
..However, if they are, they shouldn't do root. It's too risky if they don't even know the basics.
Click to expand...
Click to collapse
actually, wrong. if you have issues with adb, thats nice, but adb has NOTHING to with rooting a nexus device. rooting uses fastboot, not adb.
---------- Post added at 01:01 PM ---------- Previous post was at 12:59 PM ----------
Rodeojones said:
So the instructions for how to root lollipop should be removed because some people don't take the time to read everything and confirm which version of Android they have on their phone?
Click to expand...
Click to collapse
removed, no. it should stay to show the history of rooting, among other things. but people should edicate themselves before ever rooting their devices. stupid people isnt an excuse to get rid of our history.

simms22 said:
actually, wrong. if you have issues with adb, thats nice, but adb has NOTHING to with rooting a nexus device. rooting uses fastboot, not adb.
---------- Post added at 01:01 PM ---------- Previous post was at 12:59 PM ----------
removed, no. it should stay to shiw the history of rooring, among other things. but people should edicate themselves before ever rooting their devices. stupid people isnt an excuse to get rid of our history.
Click to expand...
Click to collapse
Ah.. you're right. Fastboot flash and unlock, right. I was talking about Android SDK(platform-tools) but it seems that I mistaked it, since I'm with adb console window for pulling something now(..)

PielunA said:
Ah.. you're right. Fastboot flash and unlock, right. I was talking about Android SDK(platform-tools) but it seems that I mistaked it, since I'm with adb console window for pulling something now(..)
Click to expand...
Click to collapse
thats alright.. seems as most accidentally say adb instead of fastboot, which isnt a big deal. unless youre a new user and keep trying to use adb to root.

Hey just trying to help the beginners. Take a look at this thread and tell me where it mentions its for lollipop.
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Or where it mentions its not for Marshmallow. I'll save you the trouble. Nowhere.
I don't deserve all the ignorant remarks here. Uncalled for.
Some of you are right, taking it down is not the right path, but mentioning what version of Android its for is the right path.

Clay said:
Hey just trying to help the beginners. Take a look at this thread and tell me where it mentions its for lollipop.
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Or where it mentions its not for Marshmallow. I'll save you the trouble. Nowhere.
I don't deserve all the ignorant remarks here. Uncalled for.
Some of you are right, taking it down is not the right path, but mentioning what version of Android its for is the right path.
Click to expand...
Click to collapse
then you have to think when it was written.. before marshmallow. before marshmallow, rooting was exactly the same for any nexus, all the way back to the nexus one. they had no idea that marshmallow would change things. what we can do as people is inform others of the changes.

Look at it from a beginners standpoint, which this site is always going to have plenty of. For them to know all that you mentioned is asking a lot. I am no longer going to bicker with everyone in this thread. Just wanted to help the beginners and share my view point as a beginner. I have learned a lot and appreciate all those that contribute to this site. Looking forward to rooting my phone and trying out some roms. Have a good day all.

Clay said:
Someone has to do something about this. Beginners like myself are bricking their phones every day and getting frustrated.
Click to expand...
Click to collapse
I can imagine your disappointment or frustration. But I can't agree with this post.
New things or methods do not need to work immediately for 100%. It is a process of creating, trial and error. And make things better every time. Stopping this process is fortunately impossible, but it should be also wrong. Because it's a free choice for everyone to be a part of it or not.

simms22 said:
then you have to think when it was written.. before marshmallow. before marshmallow, rooting was exactly the same for any nexus, all the way back to the nexus one. they had no idea that marshmallow would change things. what we can do as people is inform others of the changes.
Click to expand...
Click to collapse
NLBeev said:
I can imagine your disappointment or frustration. But I can't agree with this post.
New things or methods do not need to work immediately for 100%. It is a process of creating, trial and error. And make things better every time. Stopping this process is fortunately impossible, but it should be also wrong. Because it's a free choice for everyone to be a part of it or not.
Click to expand...
Click to collapse
So you believe that labeling a root method with the version of Android it works for and which version the method knowingly soft bricks you phone is not a good idea? Brilliant.

Clay said:
So you believe that labeling a root method with the version of Android it works for and which version the method knowingly soft bricks you phone is not a good idea? Brilliant.
Click to expand...
Click to collapse
well, if you root marshmallow the way you root any other nexus before marshmallow, it wont soft brick the device, it just wont gain root. i guess a soft brick is possible, but thats an easy fix. if it hard bricked devices, then thats a different story. but a soft brick can happen in a typical day of modding your device, and learning to fix a soft brick should be done before ever rooting your device.

Clay said:
Someone has to do something about this. Beginners like myself are bricking their phones every day and getting frustrated. Sure there is a fix but with how hard this is to learn for beginners its really frustrating.
Edit: This was meant to try to help beginners understand that the chainfire root method is for Lollipop and not for Marshmallow. I do not believe this should be taken down, just labeled for Lollipop so beginners don't soft brick their phones using this guide on a phone with Marshmallow.
Click to expand...
Click to collapse
Just read. Seriously. The last 10-20 pages of that thread are non-stop warnings and info, repeated over and over and over and over.
When you follow a guide, check the date, check the versions applicable, and read recent commentary for up-to-date information. If that is two hard, XDA DEVELOPERS is too hard for you...
Lets not encourage people to rampantly flash anything unless it has flashing red warnings... That is the wrong mentality. People should learn enough to understand what they are doing, not just be encouraged to follow the flashing red arrows.
We have the guide that we have, because it was the last one someone took the time to write, or because no one has written one the matches it since. All the information is in it... Even if you maybe have to read more then one post.
If you don't make something better, you have little right to complain. Its open source community development. We only have the things people made for us.

how i see any android mods or ways you do things.. if its 1 month or older, i assume that its out of date first. if no newer ways exist, then i try it. but i always make a backup in my recovery first, just in case. things move by within android relatively fast, so one month old can easily be out of date.

OK everyone. I get it. I am a beginner and should have gained complete knowledge of everything rooting and Android before starting this process.
I started this thread to try to help beginners that seem to, on a daily basis, use the chainfire root method on Marshmallow and soft brick their phones. Nothing more, nothing less. If having interest in helping these guys out before they go down the wrong road is wrong then tell me what is right. I am walking away from this thread as nothing good will come of it.

Clay said:
OK everyone. I get it. I am a beginner and should have gained complete knowledge of everything rooting and Android before starting this process.
I started this thread to try to help beginners that seem to, on a daily basis, use the chainfire root method on Marshmallow and soft brick their phones. Nothing more, nothing less. If having interest in helping these guys out before they go down the wrong road is wrong then tell me what is right. I am walking away from this thread as nothing good will come of it.
Click to expand...
Click to collapse
theres much good that has come from this thread already!
anyways, i learned all that i could learn before i ever first rooted(to an extreme maybe). i started with android two weeks before the g1 ever was released(got mine two weeks early). at the time, nobody knew anything about android. so, we all learned along the way. before rooting, i became the leader in the biggest android forums(at the time). only about 6 months after, i rooted my g1, before any legit root method ever existed. we learned, and we taught.. before any real methods existed. now that there are real methods, they change constantly as well, so we keep on learning and teaching