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
Related
I'd like to flash my Vivid with the new Rum Float ROM and from what I gather; now that a RUU is available it should be fairly easy. I.bought the phone last Thursday and haven't had a chance to grab a SD card. I just want to make sure that I fully understand the process involved. I've read a number of posts here at XDA and elsewhere but I still have a few questions to make sure my knowledge is solid and I don't end up with an HTC paperweight! A) Will the Android market will have a record of what I have already dl'd so I can dl it again? B) Is using the RUU executable fairly simple? Should I do the BL UL before I restore?(I would like root, so I'm assuming that this is one of the first steps!) C) Is it a simple follow the instructions sort of thing with the RUU? D) Will "frigid's" "supertool" method to get root work in this instance or do I need to use CWM? E) I'm using an AT&T Vivid could somebody give me a simple step by step(not in detail, but if you could that would be great!) Such as "1- Do BL UL, 2- Run supertool for root, 3 - Run RUU, etc, etc, etc
Also there appears to be a sense and a NONSense version of the ROM, are they both included in the RUU exe file? And for the NONSense version will there be any difference in stability, performance, you acceleration, etc?
Thanks for any info in advanced!
-MeeGz-
MeeGz said:
I'd like to flash my Vivid with the new Rum Float ROM and from what I gather; now that a RUU is available it should be fairly easy. I.bought the phone last Thursday and haven't had a chance to grab a SD card. I just want to make sure that I fully understand the process involved. I've read a number of posts here at XDA and elsewhere but I still have a few questions to make sure my knowledge is solid and I don't end up with an HTC paperweight! A) Will the Android market will have a record of what I have already dl'd so I can dl it again? B) Is using the RUU executable fairly simple? Should I do the BL UL before I restore?(I would like root, so I'm assuming that this is one of the first steps!) C) Is it a simple follow the instructions sort of thing with the RUU? D) Will "frigid's" "supertool" method to get root work in this instance or do I need to use CWM? E) I'm using an AT&T Vivid could somebody give me a simple step by step(not in detail, but if you could that would be great!) Such as "1- Do BL UL, 2- Run supertool for root, 3 - Run RUU, etc, etc, etc
Also there appears to be a sense and a NONSense version of the ROM, are they both included in the RUU exe file? And for the NONSense version will there be any difference in stability, performance, you acceleration, etc?
Thanks for any info in advanced!
-MeeGz-
Click to expand...
Click to collapse
The RUU DOES NOT CONTAIN MY ROM. It is an official tool used by HTC for upgrading and returning to stock.
Android market will keep tabs on purchased apps. It will not keep track of free apps.
You need an sdcard to keep safe.
The RUU is easy to run. Its just an exe. Follow the on-screen prompts.
I don't know what you are trying to restore but it would appear you have your terminology and methods all mixed up.
RUU will get you a stock ics. And it will wipe your apps and settings. It will act like a phone you just pulled out of the box with ics.
In order to run rum float (or any aftermarket rom) you need to unlock your bootloader. Rooting has nothing to do with it. Unlock bl then flash recovery on then flash rom and kernel.
Your steps as you perceive them are slightly off. I don't recommend you do anything to your phone right now.
After you complete the RUU you'd have to go to htc.dev and unlock your bootloader. After you can fastboot flash a recovery and CWM with root. After that's complete you can flash a rom of your choice. I'd get familiar with using fastboot commands in ADB (command prompt). I guess you can use the supertool to root but it isn't necessary really a matter of preference. Check out the superguide. Maybe PG or someone can update it with specific steps if you are using the RUU but the process is the same. It starts with the unlocking the bootloader. Definitely pick up an SD card!
Thanks for the quick replies and the clarification. I think I get it now, I would do the following to get to a rooted custom ICS Rom: Unlock the boot loader, root and run titanium backup to save my apps(using an ad card), run the RUU and get to stock HTC ics, copy ROM to sd card, re-root, download and run CWM, root again and restore apps with titanium backup, enjoy!
The only things that may be a bit off in that process is running the RUU as I don't need that to just flash a custom ROM, assuming said ROM includes the ICS kernel. If did have to use the RUU would I have to re-root to run cwm? Also the actual ROM itself is installed from HBoot, correct?
Sorry if these sound like dumb questions, I'm just new at this. I really appreciate the replies. I'm sure I will pick this up fairly quickly as I have years of linux & OS X command line experience and am well versed with c. It's just kind of information overload on this board as there is such a wealth and variety of info here!
Thanks again,
-MeeGz-
So you can run the ruu.exe even if you are rooted, unlocked bootloader, on att stock? Or do you have have to relock bootloader to proceed with the ruu?
Sent from my HTC PH39100 using XDA
RUU is for stock roms IIRC. If you are rooted and already unlocked I'd use the original method PG and Thecubed created.
back on my computer for a little better explanation.
the RUU or the methods that thecubed and i have laid out will get you the necessary HBOOT/RADIO/etc that you will need to flash a custom ICS rom
either method will get you the same thing....an updated HBOOT and ICS
if you run the bootloader unlock tool from htcdev, YOU WILL LOSE ALL YOUR SETTINGS! it will wipe the device like its brand new......do NOT include this in your dreams of getting backups prior to flashing a custom rom....
please just read through the posts and understand what is going on.
in order for ICS to happen on your vivid you need the new HBOOT, Radio, and various other components that the RUU/PH39IMG contain
there are 3 different roads you can follow to get there, the EASIEST being just run the RUU (WHICH WILL ALSO WIPE SETTINGS!), afterwards, reboot to bootloader, unlock bootloader, reboot to fastboot, fastboot flash the boot.img and the recovery.img of your choice on (limited on boot.img's at the moment, better use the one from the rom), reboot to recovery and flash the rom
the other methods imply you understand somewhat how the process works.
relock bootloader (if unlocked), run PH39IMG install, unlock bootloader, fastboot flash recovery and boot.img, reboot to recovery and flash rom.....
if you wrap your head around HOW it works, its all really simple....so the first step is understanding HOW it works, not blindly following some tutorial or walkthrough.
please try to LEARN and UNDERSTAND what it is you are doing....
PS. you have involved ROOTING too many times in your post...... the rom is already ROOTED, you dont have to ROOT to unlock, flash rom or anything....ROOTING is only applicable INSIDE the booted OPERATING SYSTEM, and has nothing to do with recovery/bootloader
i feel i need to apologize to the board here.
frustrations were not directed at the OP of this thread, just in general....
i have been inundated with PM's and seeing the same barrage of questions for the last few days on the forum....
i can understand everyone's excitement...hell i was excited to get this too.
but you all need to read, and try to take it all in before attempting anything. sometimes those of us that understand whats going on, dont explain in a whole lot of detail, because we take the knowledge for granted, and assume if you are on this site, you are here to learn. it is frustrating to see the same questions pop up on nearly an hourly basis...
all i ask is that you take forth the effort to learn how these tools of ours work and understand that a lot of us working on things like this rely on you guys to assist each other in the process. that leaves us more time to deal with what we need to deal with and try and fix and squash bugs/processes/etc.
in return i apologize if i seem on edge the last couple of days...its because i am. if you can imagine one question multiplied by a hundred.....and having people freaking out about them 'bricking'.....after being warned its possible, but unlikely. i think most of these 'bricks' are salvageable and just require someone that understands how they work.
sorry to seem like an ass, but mainly its because i am an ass, and i have a hard time being nice most of the time.
Thanks pirateghost. I understand how to do the other methods but wanted to use something less complicated with less risk for user error. I read and read everything that is posted on the forums. I try not to ask a question unless I am not understanding what has been posted. Thanks for your patience and understanding.
Sent from my HTC PH39100 using XDA
PG, so im pretty sure i "bricked" it lol. im not upset as it was entirely my fault, just wondering if there is any way to get this mother to turn on? i know that when i plug it into the computer it recognizes it but not as anything i have seen lol..if i can find the correct drivers can this be reversed?
Thanks
Thanks to PG for everything and the instructions. I thought I had bricked my phone, but theCube was able to help me on IRC, which is where I suggest anybody go for real-time assistance.
This could off all been avoided with step by step Detail instruction. Why? Well example , I don't follow this forum at all never had an HTC phone but my wife's phone the vivid. All my phone has been Nexus and the galaxy line from Samsung, things over there are a bit different. All I did was flash the ph.img and then after not seen the device reboot I wipe/factory reset and all when to hell from there. Couldn't unlock the bootloader or reboot the phone. How could this happen? Assuming that people should know the basic is wrong. I'm not in any way blaming anyone I did this own my on risk but at the same time I'm super mad had to buy a new phone. As developer you should eliminate all threats and post a details instructions step by step with do's and don't before posting firmwares.
Sent from my Galaxy Nexus using xda premium
Dxtra said:
As developer you should eliminate all threats and post a details instructions step by step with do's and don't before posting firmwares
Click to expand...
Click to collapse
As a user, you should understand the risks/benefits of the things you download. The devs are under no obligation to keep you from bricking your phone, and to be fair, most everything is covered in the Superguide and the various ROM threads. Even if someone were to post a file called NOT_A_VIRUS.EXE and you downloaded it and it wiped your computer when you ran it, the responsibility is squarely on your shoulders.
As far as I remember, there is no dev/user contract and they're not getting paid for any of this.
Dxtra said:
As developer you should eliminate all threats and post a details instructions step by step with do's and don't before posting firmwares.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
oh?
am i being paid to do a job here?
i gave instructions based on how *I* got it to work and duplicated the procedure several times. so its MY responsibility to try and find a way to brick my phone for you?
an RUU cant brick your phone.....however, being a retard can.
this is the type of attitude i would expect my boss to have, if i screwed up a project....but alas, i am here out of my own free will.....
if this is how you feel, then you should get the F off this site.
formicae said:
As a user, you should understand the risks/benefits of the things you download. The devs are under no obligation to keep you from bricking your phone, and to be fair, most everything is covered in the Superguide and the various ROM threads. Even if someone were to post a file called NOT_A_VIRUS.EXE and you downloaded it and it wiped your computer when you ran it, the responsibility is squarely on your shoulders.
As far as I remember, there is no dev/user contract and they're not getting paid for any of this.
Click to expand...
Click to collapse
I totally 100% agree with you. If you HAVE taken the time to read and are still a bit confused, ask! For me I'm not even a week into this platform and I WILL NOT do anything that I don't entirely understand. The problem with android, if you could even call it a problem, is that there is such a huge variety of handsets and a big variety methods for doing this, that, and the other thing. It basically results in a non-linear process to get from point A to point B. It's imperative to understand the basic proceedures. If you were here since the G1, great, you've been able to.follow things from the start. I've used iOS for years, and I still love it btw.(only jailbroken of course!) I'll probably buy an iPad 3! The software is integrated with the hardware amazingly well, battery life is phenomenal, and ONCE JAILBROKEN, iOS is an excellent platform. Sure the "spec numbers" may not be as high but it boils down to.performance. That has always been great for me, obviously battery life is exceptional on apple devices as well. I'm hoping with a rooted ICS Rom there won't be cpu-time hogging processes and ill be able to adjust other things accordingly to get somewhat better battery life. I really wish each OEM would take the time to optimize the SW that they're using to the HW that they're selling. B/C from what I've seen the "Nexus" devices generally perform extremely well, even.against higher spec'd devices. So far I'm loving Android and my Vivid. I love the freedom that I get even on a non-rooted device! It's an excellent platform. Flexible, dynamic, and personal. Customization is there from the get-go. There are a million different things that one could do, even while staying un-rooted. The only reason that I've waited so long to get on board with android is ibwas waiting for it to grow and mature, if I could have a device that tri-booted Android, iOS, and WebOS I'd be a very happy person. I love using multiple platforms.
PG - I'm sorry if I bothered you, thanks for the great info though!
I think knowledge-wise I'm at a point where I'm not going to brick my phone. Wish me luck!
Pirateghost said:
oh?
am i being paid to do a job here?
i gave instructions based on how *I* got it to work and duplicated the procedure several times. so its MY responsibility to try and find a way to brick my phone for you?
an RUU cant brick your phone.....however, being a retard can.
this is the type of attitude i would expect my boss to have, if i screwed up a project....but alas, i am here out of my own free will.....
if this is how you feel, then you should get the F off this site.
Click to expand...
Click to collapse
Seriously if that is how you feel do get the f*ck off this site please. The devs in all mobile hacking communities are unpaid and do it for fun. You sir are a prime example of WHY THEY LEAVE!!! IF YOU DON'T KNOW AND HAVE READ, ASK, DON'T BE A ****!!!
Dxtra said:
This could off all been avoided with step by step Detail instruction. Why? Well example , I don't follow this forum at all never had an HTC phone but my wife's phone the vivid. All my phone has been Nexus and the galaxy line from Samsung, things over there are a bit different. All I did was flash the ph.img and then after not seen the device reboot I wipe/factory reset and all when to hell from there. Couldn't unlock the bootloader or reboot the phone. How could this happen? Assuming that people should know the basic is wrong. I'm not in any way blaming anyone I did this own my on risk but at the same time I'm super mad had to buy a new phone. As developer you should eliminate all threats and post a details instructions step by step with do's and don't before posting firmwares.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
REALLY? You want the UNNPAID DEV'S TO REMOVE ALL THREATS?!?!?! FROM WHAT IS BASICALLY OSS AND A FIRMWARE THAT SOMEBODY DL'D? REALLY? These guys take a FW and cook it into a ROM for FREE and just b/c you didn't take the time to understand it you're gonna put it on them? WTF?!?!?!?
i'll make him a deal. next time we get a hold of something like this, i will let him figure out how to get it on his phone....i don't have to share how...
Dxtra said:
This could off all been avoided with step by step Detail instruction. Why? Well example , I don't follow this forum at all never had an HTC phone but my wife's phone the vivid. All my phone has been Nexus and the galaxy line from Samsung, things over there are a bit different. All I did was flash the ph.img and then after not seen the device reboot I wipe/factory reset and all when to hell from there. Couldn't unlock the bootloader or reboot the phone. How could this happen? Assuming that people should know the basic is wrong. I'm not in any way blaming anyone I did this own my on risk but at the same time I'm super mad had to buy a new phone. As developer you should eliminate all threats and post a details instructions step by step with do's and don't before posting firmwares.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
You know, its users like you that get Devs frustrated and not want to share the work that they have accomplished. XDA is a site for Devs, its not a WalMart that people can stop by and expect to be spoonfed and be on their merry way. Pirateghost is a very talented Dev who wanted to share something with this community, and instead of saying "thank you" you decide to look a the glass as half empty instead of half full and EXPECT MORE from him?
Reading your post, it tells me that you dont frequent the HTC forums at all, and instead of reading up, you just decided to flash. Just because it didnt go as smoothly as you thought it would is NO REASON to tell a Dev that they needed to do more. That part lays on you.
Next time you decide to tell a Dev that "they need to do more" I think you need to do more reading so it prevents you from having to buy a new phone. If it dosent make sense to you or you dont think theres enough documentation/step-by-step instructions YOU HAVE THE POWER TO SAY NO AND NOT FLASH IT.
Uh, there's a reason every single solitary dev puts a disclaimer on their ROM threads. Their work, if directions are not followed to the letter can turn your device into a +/- 200$ paperweight. I've been lurking around these forums for a hot minute, rarely post ( not an ounce of dev skill being the main reason), and really, when's the last time a dev didn't post at least semi detailed instructions to go along with his/her OP.
@pirateghost- bought a vivid literally 12 hours ago, got home, saw your thread, FOLLOWED THE DIRECTIONS CAREFULLY, and now have ICS on my device. Just wanted to say thanks.
And now for the most epic noob question of all time. Wth is RUU? I'm very familiar with flashing roms, cam, tibu, etc from my days on the sgsII SR forums. So most if not all HTC terminology is new to me.
Sent from my HTC PH39100 using xda premium
So I see from the Development subforum that the Droid 4 hasn't been rooted yet. Correct? Does anyone have a plain english update as to what's going on on that front?
I see there's a bounty on someone's head, or something like that, but that's all I've got.. and I'm not savvy enough to know what to do myself or know what's really happening there. I'd love a one click root method. How far away are we from that functionality?
sorry for the pretty dumb question
tamarw said:
So I see from the Development subforum that the Droid 4 hasn't been rooted yet. Correct? Does anyone have a plain english update as to what's going on on that front?
I see there's a bounty on someone's head, or something like that, but that's all I've got.. and I'm not savvy enough to know what to do myself or know what's really happening there. I'd love a one click root method. How far away are we from that functionality?
sorry for the pretty dumb question
Click to expand...
Click to collapse
Root has been achieved. Just follow the directions here: http://forum.xda-developers.com/showthread.php?t=1492843
kwyrt said:
Root has been achieved. Just follow the directions here: http://forum.xda-developers.com/showthread.php?t=1492843
Click to expand...
Click to collapse
thank you Guess I was just searching for the phrase "root."
tamarw said:
thank you Guess I was just searching for the phrase "root."
Click to expand...
Click to collapse
No problem. Happy rooting. And be careful!
Root was achieved on this device by djrbliss before it was even released actually, but we still do not yet have a full XML.zip of fastboot images to restore with, so it is very dangerous to make any significant mods at this stage.
I have been pushing all my sources very hard to find this file, but so far everyone has come up empty.
Until we have it we are all working without a safety net because signed factory images are needed to restore a soft bricked device.
Stick to rooting your phone, for the time being. You can disable bloatware, and customize the hell out of the stock ROM that's already on there. That should be enough to get you through, for the time being. Don't get me wrong, we're all salivating over a real safety net.
Go with a simple root or safestrap it. I bricked my phone using safestrap.
Root for now, wait for fastboot files.
Hi everyone. I'm new to the forum; this is my first post.
I have an M7 on a stock HTC/AT&T ROM running Lollipop 5.0.2 with Sense 6.0.
I would like to root the device so that I can do things like eliminate ads, remove bloatware, run more advanced software, etc., but I do not want to loose things like Beats Audio/Boom Sound. So I'm thinking I just want to stick with the stock AT&T/HTC M7 ROM.
I have seen reference to the Sunshine App, but unless someone can tell me it does something absolutely magical for the one-use $25 payment they expect, I'm fine doing it the free way. I got the impression about Sunshine that it doesn't actually get you all the way to root. If it got me all the way and saved my data/apps, too, I'd be all over it.
Can someone please give me the full path of steps I need to go through to get this done? I'm not a dumb guy. Pretty computer savvy, actually, but there is a lot of jargon and intermediate steps that seem to be involved in all of this. Some of the videos I'm seeing are quite dated at this point, and I have to wonder if they are relevant to an AT&T M7 on Lollipop a this point. But I thrive on step-by-step tutorials, so if you guys point me to the right videos or written tutorials, I should be fine.
Any suggestion on the best way to backup my device would be appreciated, too. I understand I'm going to get all my data and programs wiped somewhere along the path.
Thank you!
djMot said:
Hi everyone. I'm new to the forum; this is my first post.
I have an M7 on a stock HTC/AT&T ROM running Lollipop 5.0.2 with Sense 6.0.
I would like to root the device so that I can do things like eliminate ads, remove bloatware, run more advanced software, etc., but I do not want to loose things like Beats Audio/Boom Sound. So I'm thinking I just want to stick with the stock AT&T/HTC M7 ROM.
I have seen reference to the Sunshine App, but unless someone can tell me it does something absolutely magical for the one-use $25 payment they expect, I'm fine doing it the free way. I got the impression about Sunshine that it doesn't actually get you all the way to root. If it got me all the way and saved my data/apps, too, I'd be all over it.
Can someone please give me the full path of steps I need to go through to get this done? I'm not a dumb guy. Pretty computer savvy, actually, but there is a lot of jargon and intermediate steps that seem to be involved in all of this. Some of the videos I'm seeing are quite dated at this point, and I have to wonder if they are relevant to an AT&T M7 on Lollipop a this point. But I thrive on step-by-step tutorials, so if you guys point me to the right videos or written tutorials, I should be fine.
Any suggestion on the best way to backup my device would be appreciated, too. I understand I'm going to get all my data and programs wiped somewhere along the path.
Thank you!
Click to expand...
Click to collapse
just posted this for someone else
Flash TWRP 2.8.5.0
fastboot flash recovery openrecovery-twrp-2.8.5.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
/ enter recovery
Exit recovery choose yes to Root
when the phone boots up go to the SuperSU Icon in the app drawer
it will ask to update / choose TWRP
after it reboots your rooted
clsA said:
just posted this for someone else
Flash TWRP 2.8.5.0
fastboot flash recovery openrecovery-twrp-2.8.5.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
/ enter recovery
Exit recovery choose yes to Root
when the phone boots up go to the SuperSU Icon in the app drawer
it will ask to update / choose TWRP
after it reboots your rooted
Click to expand...
Click to collapse
Thanks, but I think you are making a few too many assumptions that I understand what your saying.
I don't think I can just flash twrp before unlocking the bootloader, am I right? And I have no clue how to flash twrp, how to set up to do that, and what to have where. I can do the steps if I know what they are. So I really am looking for a pretty explicit set of steps. You've given me some steps, yes, and thank you for that(!!), but I think you're coming from a position of already knowing exactly what you are doing and all the ramifications of each and every step you would take, so by the time it gets to me it just sounds like the cliffs notes and I'm still wondering what the novel is about.
And, yes, I get that some of you here answer these kinds of noobie questions a lot, and it just gets tedious repeating yourselves. Unfortunately for us noobies who come looking to the experts for the straight-up how-to, the responses all seem like "just do this, do that" without any discussion of how to do this and how to do that. I've read several "how do I root my phone" threads here, but the answers all seem just a little to Greekish to me, and to others too I would imagine. The video tutorials here were recorded back when the M7 was brand new and there's no indication at all whether updates along the way to present day have altered the process, or whether there is a safer, better way after all this time. I have no idea if they are relevant today.
I get that I'm asking a lot for such an old device, but I would really appreciate a little of a tutorial approach.
Thanks very much.
djMot said:
Thanks, but I think you are making a few too many assumptions that I understand what your saying.
I don't think I can just flash twrp before unlocking the bootloader, am I right? And I have no clue how to flash twrp, how to set up to do that, and what to have where. I can do the steps if I know what they are. So I really am looking for a pretty explicit set of steps. You've given me some steps, yes, and thank you for that(!!), but I think you're coming from a position of already knowing exactly what you are doing and all the ramifications of each and every step you would take, so by the time it gets to me it just sounds like the cliffs notes and I'm still wondering what the novel is about.
And, yes, I get that some of you here answer these kinds of noobie questions a lot, and it just gets tedious repeating yourselves. Unfortunately for us noobies who come looking to the experts for the straight-up how-to, the responses all seem like "just do this, do that" without any discussion of how to do this and how to do that. I've read several "how do I root my phone" threads here, but the answers all seem just a little to Greekish to me, and to others too I would imagine. The video tutorials here were recorded back when the M7 was brand new and there's no indication at all whether updates along the way to present day have altered the process, or whether there is a safer, better way after all this time. I have no idea if they are relevant today.
I get that I'm asking a lot for such an old device, but I would really appreciate a little of a tutorial approach.
Thanks very much.
Click to expand...
Click to collapse
Yeah, that's not going to happen
Read the FAQ >> http://forum.xda-developers.com/showthread.php?t=2228274
and the So you came at XDA-Developers to find help
If your still stuck after that then ask questions.
Hint: I described all the steps in post 2 above
djMot said:
Thanks, but I think you are making a few too many assumptions that I understand what your saying.
I don't think I can just flash twrp before unlocking the bootloader, am I right? And I have no clue how to flash twrp, how to set up to do that, and what to have where. I can do the steps if I know what they are. So I really am looking for a pretty explicit set of steps. You've given me some steps, yes, and thank you for that(!!), but I think you're coming from a position of already knowing exactly what you are doing and all the ramifications of each and every step you would take, so by the time it gets to me it just sounds like the cliffs notes and I'm still wondering what the novel is about.
And, yes, I get that some of you here answer these kinds of noobie questions a lot, and it just gets tedious repeating yourselves. Unfortunately for us noobies who come looking to the experts for the straight-up how-to, the responses all seem like "just do this, do that" without any discussion of how to do this and how to do that. I've read several "how do I root my phone" threads here, but the answers all seem just a little to Greekish to me, and to others too I would imagine. The video tutorials here were recorded back when the M7 was brand new and there's no indication at all whether updates along the way to present day have altered the process, or whether there is a safer, better way after all this time. I have no idea if they are relevant today.
I get that I'm asking a lot for such an old device, but I would really appreciate a little of a tutorial approach.
Thanks very much.
Click to expand...
Click to collapse
Hi,
I know its 2019, four years since you posted this request, but I just pulled my HTC One M7 AT&T after 3 years and had the exact same query and needed a way to ensure that steps mentioned in posts like these in 2015 are still relevant/applicable on our device running Android 5.0.2 with HTC Sense 6.
I was looking to have a device specific tutorial to finally make the plunge to install a custom ROM (someone ported Android 10 to this device!) , but remember there being some complexities back in the day to do this on our device. Were you able to get around this? Look forward to your response.
Thanks & regards,
Deepesh
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?
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.