Related
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
Ok, so, first off, yes, as I keep being told by the forums I read, I am a noob. I understand, and respect that. That's not the issue.
So, I have followed the guide that's found here, and I have the Clockwork mod installed, as when I turn on my phone, and press down, it says I have it.
I -had- my phone rooted in the past, and then -finally- the official 4.0.4 update came out. I upgraded from my old rooted image to the new image, and figured I'd wait to see if someone would post instructions on how to update this version, unless I am doing something wrong.
I am sure that I am, or I missed something somewhere. Again, I have -no- idea what I am talking about. I don't claim I do.
So... I try to install Superuser-3.2-RC2 -and- RC3-ARM-signed.zip, as I was advised that may work via pressing power+down, I get this:
E:failed to verify whole-file signature
E:signature verification failed!
I am not sure what I am doing wrong. I copied the file over to the root of the SD card, and all that jazz.
So, is someone ready to point out the error in my method, or more likely, tell me I am an idiot?
-Haz
Hazarath said:
Ok, so, first off, yes, as I keep being told by the forums I read, I am a noob. I understand, and respect that. That's not the issue.
So, I have followed the guide that's found here, and I have the Clockwork mod installed, as when I turn on my phone, and press down, it says I have it.
I -had- my phone rooted in the past, and then -finally- the official 4.0.4 update came out. I upgraded from my old rooted image to the new image, and figured I'd wait to see if someone would post instructions on how to update this version, unless I am doing something wrong.
I am sure that I am, or I missed something somewhere. Again, I have -no- idea what I am talking about. I don't claim I do.
So... I try to install Superuser-3.2-RC2 -and- RC3-ARM-signed.zip, as I was advised that may work via pressing power+down, I get this:
E:failed to verify whole-file signature
E:signature verification failed!
I am not sure what I am doing wrong. I copied the file over to the root of the SD card, and all that jazz.
So, is someone ready to point out the error in my method, or more likely, tell me I am an idiot?
-Haz
Click to expand...
Click to collapse
First time I hear of a Captivate Glide!? I *guess* they use the same firmware.
I'm not sure if superoneclick works for ICS but you could look into that.
EDIT: Look below.
I don't really want to give you any advice because I've never used the captivate glide and I would advise against using any software in this forum. There is a forum for the glide though which would probably be the best place to get your answer. I would link you to it but I'm on my phone at the moment.
The phones are similar but still different enough that rooting methods and custom kernels probably won't work the same.
Sent from my SGH-I897 using xda app-developers app
m1batt1 said:
I don't really want to give you any advice because I've never used the captivate glide and I would advise against using any software in this forum. There is a forum for the glide though which would probably be the best place to get your answer. I would link you to it but I'm on my phone at the moment.
The phones are similar but still different enough that rooting methods and custom kernels probably won't work the same.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
Ah good point, though it was only a deviation of the captivate.
BWolf56 said:
Ah good point, though it was only a deviation of the captivate.
Click to expand...
Click to collapse
True but the fact that it has a slide out keyboard concerns me. Any software not made for it would probably render the keyboard unusable.
Sent from my SGH-I897 using xda app-developers app
m1batt1 said:
True but the fact that it has a slide out keyboard concerns me. Any software not made for it would probably render the keyboard unusable.
Click to expand...
Click to collapse
See, things like that is why I posted to start with... I know I am a noob, and I think I ran into a unique situation, so, that's why I posted... I would of just used good 'ol Google, but, I really just prefer to keep it on here... seeing as the guide here is well done, and I think I could trust it.
..that, and I am a bit afraid of some answers I may get elsewhere.
Anywho, any ideas how to get SU to work around this? I remember reading somewhere that there's an option to allow un-signed roms to load.. is that doable here, or better yet, advisable? I.E., might brick something? I love this phone, after all. Just... hate the bloatware that made it's return. x.x
-Haz
Hazarath said:
See, things like that is why I posted to start with... I know I am a noob, and I think I ran into a unique situation, so, that's why I posted... I would of just used good 'ol Google, but, I really just prefer to keep it on here... seeing as the guide here is well done, and I think I could trust it.
..that, and I am a bit afraid of some answers I may get elsewhere.
Anywho, any ideas how to get SU to work around this? I remember reading somewhere that there's an option to allow un-signed roms to load.. is that doable here, or better yet, advisable? I.E., might brick something? I love this phone, after all. Just... hate the bloatware that made it's return. x.x
-Haz
Click to expand...
Click to collapse
There is, the thing is that it'S different from phone to phone so you'll only get a real answer over on the Glide side :/
Hazarath,
Here is a good place to start...http://forum.xda-developers.com/showthread.php?p=25355727
Sent from my SAMSUNG-SGH-I777 using xda premium
4-2ndtwin said:
Hazarath,
Here is a good place to start...http://forum.xda-developers.com/showthread.php?p=25355727
Click to expand...
Click to collapse
I followed the instructions from that guide to root the phone, that's where I get that error. It won't accept an un-signed ROM.
..and, I was gonna post on the forum posts that would help with this more directly, but, this is my 3rd post; not allowed to pose in Dev forums yet.
-Haz
UPDATE:
Someone earlier suggested I run Super One Click, I think... well, I run it, and I tell it to 'Root' It says 'Missing driver! Install?' I click 'Yes' A pop up comes up, 'No more data' then another, and I click yes, same thing. Just tossing that in there...
-Haz
Hazarath said:
UPDATE:
Someone earlier suggested I run Super One Click, I think... well, I run it, and I tell it to 'Root' It says 'Missing driver! Install?' I click 'Yes' A pop up comes up, 'No more data' then another, and I click yes, same thing. Just tossing that in there...
-Haz
Click to expand...
Click to collapse
Did you check if it was ICS compatible?
BWolf56 said:
Did you check if it was ICS compatible?
Click to expand...
Click to collapse
I am not sure... prolly not. Ah, well, back to square one... any other ideas?
-Haz
Hold it, hold it, slow down.
First of all, the Captivate and Captivate Glide have nothing in common besides their name. Different SoC, different NAND, different screen, different board layout. NOTHING is interoperable between them short of, well, flashing tools like Odin.
The Glide has its own section. Come join us, we're fun people and we just got CM10.1 a few weeks ago!
-E- Also, for the Glide you install ClockworkMod first, THEN root. That's just SOP for devices that ship with the bootloader already unlocked.
same problem
Im having the same problem with error codes when i try to use superuser
Has anyone found a solution?
I have the at&t model and factory unlocked if it helps
Mike-88 said:
Im having the same problem with error codes when i try to use superuser
Has anyone found a solution?
I have the at&t model and factory unlocked if it helps
Click to expand...
Click to collapse
If you have a Glide, you're in the wrong section.
If you have a Captivate though, be more clear about your issue. What error do you get? What steps did you take? Followed any guide?
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.]
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.
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