Related
Hey folks, i know that for some, unlocking bootloaders and rooting for the first time can be a bit overwhelming, so i put together a video, walking you through step by step. I hope this helps at least 1 of you
The toolkit in this video guide was developed by hasson2000, so big props and thanks go out to him! You can find his toolkit here
To the moderators. hasson2000 has asked that folks request his permission to use his work in posts ect.. So i did ask, but he never responded... So since this is doing no harm and only helping people, i assume you won't mind this posted here If you do want to take it down, i won't fight you on it.
If you folks have any questions, i strongly recommend you go to hasson2000s toolkit thread, linked above, and ask there.
Cheers
Very Helpful
I'm still stuck on waiting for device.
I was going in that Tool thread but I'm not allowed to post there yet.
Sent from my HTCONE using Tapatalk 2
Nice. Thanks much!!
Thank you so much for the vid, I used it to unlock my bootloader and also installed TWRP... It worked a treat
My issue is that I want to flash the 1.29 OTA onto my EE-branded 4G HTC One. I've downloaded this version: OTA_M7_UL_JB_50_HTC_Europe_1.29.401.12-1.28.401.7_release_315849_signedp7vl8dqsvls0h1t0.z ip from this thread: http://forum.xda-developers.com/showthread.php?t=2207874. I have attempted to Flash my own recovery, but am unsure as to which .img file to use and also which option in the bootloader to select. I've searched all throughout these forums, but to no avail
If anyone can help, it would be much appreciated.
Many thanks
any one have any alternative link to the all in one toolkit by hasoon looks like the link is broken?
aaroh said:
any one have any alternative link to the all in one toolkit by hasoon looks like the link is broken?
Click to expand...
Click to collapse
right here
Thanks, this worked like a charm!
This is my first Android phone and reading all of this did seem scary, but watching the video and doing it myself.. pretty easy!
So, there is no way to root this device without unlocking it first? I've also read that after you unlock, you loose some apps & obviously OTA updates......4.2.2 is rumored to be out for this device any time now. Is there anyway to preserve those apps, possibly update phone (even manually) or just root without unlocking?
P05TMAN said:
So, there is no way to root this device without unlocking it first? I've also read that after you unlock, you loose some apps & obviously OTA updates......4.2.2 is rumored to be out for this device any time now. Is there anyway to preserve those apps, possibly update phone (even manually) or just root without unlocking?
Click to expand...
Click to collapse
you won't loose any apps if you unlock, you will lose all of your files though... and you can still receive OTAs is you are unlocked, you just need to have the stock rom and a stock recovery...
Success (relatively painless)
I'd like to add my success story as a hopeful note for other noobs who are sweating it.
I'm a complete noob with recovery and rooting. Luckily I had the distinct advantage of skipping the whole bootloader unlocking sequence, thanks to having the Developer Edition whose bootloader comes unlocked. (I wasn't sure if I should use Hasoon2000's T-Mobile kit, since I'm using a T-mo SIM, or if I should use his generic HTC One M7 kit, so I chose the latter and luckily it was a good choice.)
I studied this video tutorial by TheSmokingAndroid, took notes, watched it again, said a little prayer to the green guy in the sky, watched some more tutorials, read some tutorials, read 50 pages of xda forums, panicked, de-panicked, steeled myself, then watched the video again. Then I dove in.
While not every step had the exact results that TheSmokingAndroid depicted in his video (combination of user error by me and the HTC One apparently being somewhat finicky), while not every step was an exact match, a little persistence and staying calm resulted in full root in about 1/2 an hour once I actually got started, and no major calamities.
So thanks TheSmokingAndroid and thanks Hasoon2000!
(If you're a noob, consider making a small donation like I did to keep these guys going.)
Happy rooting.
matt95 said:
you won't loose any apps if you unlock, you will lose all of your files though... and you can still receive OTAs is you are unlocked, you just need to have the stock rom and a stock recovery...
Click to expand...
Click to collapse
So you won't loose torch and some of the other apps I've read you may lose after unlocking?
Sent from my HTC One using xda app-developers app
P05TMAN said:
So you won't loose torch and some of the other apps I've read you may lose after unlocking?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
no, you won't
TheSmokingAndroid said:
To the moderators. hasson2000 has asked that folks request his permission to use his work in posts ect.. So i did ask, but he never responded... So since this is doing no harm and only helping people, i assume you won't mind this posted here If you do want to take it down, i won't fight you on it.
Click to expand...
Click to collapse
I receive tons of PMs and can forget who I responded to, since I am on my phone majority of the time. Anyone is allowed to make a video using my toolkit. I just do not permit people to repost my work on another site. All official toolkit threads will be on XDA and all the toolkits will be uploaded to ONLY my Dev-Host account. I do not authorize mirrors of my toolkits (since anyone can just repack it with a virus and blame me for it). However, my apologies if I did not get back to you. I usually wake up with 10 - 15 PMs, plus more throughout the day!
Shad0wStorm said:
Very Helpful
Click to expand...
Click to collapse
I used that tool yesterday to root mine. I wish I knew of this video though. The device is finicky when trying to get a root!!
HTC One (China model) htc 802w
Getting into the China model of HTC One (htc 802w) bootloader and recovery.
It should work for any model as well.
factory reset
Hi, I recently unlocked my bootloader and rooted my HTC One and flashed the cyanogen rom. However, I want to now go back to the original software that came with my phone, but I did not backup my phone on twrp recovery. I do not care about my user data, I just want to go back to HTC Sense. Could anyone help me go back to the factory default os reset? Also my phone is from T-mobile if that helps.
I'd personally like to know how to pull the stock recovery image from my device for later use, rather than using someone else's. I've already searched but I'm directed to the stock recovery image already posted here. Isn't there a way to make the image flashable rather than pushing it through with ADB?
TheSmokingAndroid said:
Hey folks, i know that for some, unlocking bootloaders and rooting for the first time can be a bit overwhelming, so i put together a video, walking you through step by step. I hope this helps at least 1 of you
The toolkit in this video guide was developed by hasson2000, so big props and thanks go out to him! You can find his toolkit here
To the moderators. hasson2000 has asked that folks request his permission to use his work in posts ect.. So i did ask, but he never responded... So since this is doing no harm and only helping people, i assume you won't mind this posted here If you do want to take it down, i won't fight you on it.
If you folks have any questions, i strongly recommend you go to hasson2000s toolkit thread, linked above, and ask there.
Cheers
Click to expand...
Click to collapse
beginning of the video you said"the first link in the discriptions" where is that link?!i cant find it.the discription of what?
---------- Post added at 07:40 PM ---------- Previous post was at 07:31 PM ----------
TheSmokingAndroid said:
Hey folks, i know that for some, unlocking bootloaders and rooting for the first time can be a bit overwhelming, so i put together a video, walking you through step by step. I hope this helps at least 1 of you
The toolkit in this video guide was developed by hasson2000, so big props and thanks go out to him! You can find his toolkit here
To the moderators. hasson2000 has asked that folks request his permission to use his work in posts ect.. So i did ask, but he never responded... So since this is doing no harm and only helping people, i assume you won't mind this posted here If you do want to take it down, i won't fight you on it.
If you folks have any questions, i strongly recommend you go to hasson2000s toolkit thread, linked above, and ask there.
Cheers
Click to expand...
Click to collapse
the htc driver i got is 3.0.0.007 not the only in ur video 4.1.0.001.
i just cant find that link where you highlighted the new version in the video which was updated on 4.23.13.
thanks plz help me
What does unlocking the bootloader do?
Is it just for installing custom roms?
i am looking to buy a rogers canada HTC one and i need to use it with Bell mobility.
how can i unlock it? do i need to follow the video and unlock the bootloader? is there anything extra that I need to do?
let me know. thanks
So i brilliantly unlock the bootloader on the moto x and rooted the phone also installed the su and then the real genius part came out and i accidentally wiped the whole fing phone all the sdcard and the entire os and now all i have is a wonderful beautiful white motorola moto x and cant use it oh and to make things really worth it i just open the account with sprint so the phone is only 3 days old. Can someone Please Help me i am at a lost and dont have a clue what to do. I dont know how to reinstall the OS.:crying::crying::crying:
lsl73 said:
So i brilliantly unlock the bootloader on the moto x and rooted the phone also installed the su and then the real genius part came out and i accidentally wiped the whole fing phone all the sdcard and the entire os and now all i have is a wonderful beautiful white motorola moto x and cant use it oh and to make things really worth it i just open the account with sprint so the phone is only 3 days old. Can someone Please Help me i am at a lost and dont have a clue what to do. I dont know how to reinstall the OS.:crying::crying::crying:
Click to expand...
Click to collapse
I am having somewhat the same issues. Someone is helping me out and if I get an easy solution I will be happy to share.
This should help you:
http://forum.xda-developers.com/showthread.php?t=2446515
superaj13 said:
I am having somewhat the same issues. Someone is helping me out and if I get an easy solution I will be happy to share.
Click to expand...
Click to collapse
Thanks i hope you can get yours going as well
fabriciosr said:
This should help you:
http://forum.xda-developers.com/showthread.php?t=2446515
Click to expand...
Click to collapse
The rsd lite cant see my moto x i can only access it thru the fastboot but when i try the rsd way it doesnt see the phone.
Download/find the correct system.img and boot.img for your device, then push/install them via fastboot. You shouldn't need anything else. Recovery, bootloader, and other firmware should be untouched. Only issue is if it's a safestrap device, then I have no clue.
gokart2 said:
Download/find the correct system.img and boot.img for your device, then push/install them via fastboot. You shouldn't need anything else. Recovery, bootloader, and other firmware should be untouched. Only issue is if it's a safestrap device, then I have no clue.
Click to expand...
Click to collapse
Gokart i have tried that i dont think i am doing it wrong i got the system.img and the boot.img from here but just incase i ride the small yellow bus with a helmet on can you please point me to the direction i need to go AGAIN.
try to
fastboot flash system system.img
The obvious thing is make sure you have fastboot set up correctly... Drivers as well.
Make sure all drivers are installed, trust me redlite works with a soft bricked moto x, I found out today, my phone was bootlooping, nandroids failed soi wiped the sdcard and realized at that point I did the noob thing, well it worked like a charm rsdlite
Sent on my Moto X
this is the error i keep getting
lsl73 said:
this is the error i keep getting
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2489249
i would like to thank all you guys for all the advise that was given to help me bring my moto x back to life i finally got it up and running again using the moto x toolkit it seemed like the only thing that would of work in my situation again thank yall so much :victory::victory::victory:
Who unlocks their bootloader but doesn't know what to do when stuff goes bad, like this?
If you read enough to unlock the bootloader, you should have read enough to know what to do here. Coming here frantic without even checking the eleven billion threads already is silly. We have about 12 threads about the new update and similar high number threads about restoring your phone.
Too many repetitive threads for the Moto X on xda. Some people just need to take 5 minutes and look through general or Q&A before they blindly post. Clutter everywhere.
And finally, dude! I do not have any pity for you. I'm on Verizon and cannot unlock my bootloader maybe that's why I just ranted. Nothing personal, just a general consensus of this section as of late...
Sent from my XT1060 using Tapatalk
oh brother i am not mad at you but as a by the way i DID try different ways of trying to load the os back using this site as a guidance before i made this post this post was a last ditch effort before i smash the moto x and use the insurance claim on it i have been a member of this site since 2010 i just didnt create this account
I'm really having one hell of a time figuring out the most correct steps to rooting the verizon model. What I've always done upon attempting to root a new device is read all available information and decide from there. Between XDA, Reddit, Rootz and YouTube, I have no freaking idea which one is the most tried and true. My previous devices (Nexus 4 and Galaxy Nexus) were a walk in the park - even the droid X2 was a little easier to sift through and I faced less risk of very much destroying something. And after reading roughly 50 pages of threads here, I'm chalking most of this up to the device's immaturity. Regardless, there are people who have tried, succeeded and failed.
New folks need to hear what does and doesnt work in the most clear way possible and thats what I'm asking - what works, what doesnt work, what should I not even bother reading?
SlapMyMoto
nhizzat said:
SlapMyMoto
Click to expand...
Click to collapse
This.
Don't ask any questions, just follow the steps to the letter and you will be fine. I'm on a VZW model that I had to downgrade, and kept asking question after question.
You lose stock custom recovery forever, that's the risk on a non-dev-edition.
jl33 said:
I'm really having one hell of a time figuring out the most correct steps to rooting the verizon model. What I've always done upon attempting to root a new device is read all available information and decide from there. Between XDA, Reddit, Rootz and YouTube, I have no freaking idea which one is the most tried and true. My previous devices (Nexus 4 and Galaxy Nexus) were a walk in the park - even the droid X2 was a little easier to sift through and I faced less risk of very much destroying something. And after reading roughly 50 pages of threads here, I'm chalking most of this up to the device's immaturity. Regardless, there are people who have tried, succeeded and failed.
New folks need to hear what does and doesnt work in the most clear way possible and thats what I'm asking - what works, what doesnt work, what should I not even bother reading?
Click to expand...
Click to collapse
I am in the same boat after recently getting a Moto X and coming from a Galaxy Nexus that seemed to have more consensus, or least clearly indicated. It was a bit daunting to trying to start to learn the process again after over 2 years.
User dray has got you covered though regardless of what Moto X you are using and what version of Android you are on. Go here http://forum.xda-developers.com/showthread.php?t=2603358 and thank dray for his efforts.
I recently finished rooting my xt1060 starting at 4.2.2 and could show you what I did if you are in the same boat.
You can't compare a nexus to a device with a boot loader that can't be unlocked. A little research before purchasing would have shown you that its not as easy to root.
If you had a Moto x with an unlockable boot loader...then it would be just as easy as a nexus to root. Same steps in fact. So its not device immaturity ....its the fault of the particular one you bought.
Just saying.
Sent from my Moto X cellular telephone...
kj2112 said:
You can't compare a nexus to a device with a boot loader that can't be unlocked. A little research before purchasing would have shown you that its not as easy to root.
If you had a Moto x with an unlockable boot loader...then it would be just as easy as a nexus to root. Same steps in fact. So its not device immaturity ....its the fault of the particular one you bought.
Just saying.
Sent from my Moto X cellular telephone...
Click to expand...
Click to collapse
slapmymoto
Just saying.
syntrix said:
slapmymoto
Just saying.
Click to expand...
Click to collapse
That's nothing like the unlocked boot loader method...which is the same as the nexus method. And I can see how it intimidates new people.
So maybe quit quoting me with smart ass comments all over this forum and read the opening posts a bit more carefully.
He knows about slap ....its just a chore was his point...compared to flash recovery in fastboot...say yes to fix root.....reboot and done. Lol
Do us both a favor and put me on your ignore list....before this escalates.
Sent from my Moto X cellular telephone...
jl33 said:
I'm really having one hell of a time figuring out the most correct steps to rooting the verizon model. What I've always done upon attempting to root a new device is read all available information and decide from there. Between XDA, Reddit, Rootz and YouTube, I have no freaking idea which one is the most tried and true. My previous devices (Nexus 4 and Galaxy Nexus) were a walk in the park - even the droid X2 was a little easier to sift through and I faced less risk of very much destroying something. And after reading roughly 50 pages of threads here, I'm chalking most of this up to the device's immaturity. Regardless, there are people who have tried, succeeded and failed.
New folks need to hear what does and doesnt work in the most clear way possible and thats what I'm asking - what works, what doesnt work, what should I not even bother reading?
Click to expand...
Click to collapse
here is a complete guide that i made up hope it helps
http://forum.xda-developers.com/showthread.php?t=2603358
syntrix said:
This.
Don't ask any questions, just follow the steps to the letter and you will be fine. I'm on a VZW model that I had to downgrade, and kept asking question after question.
You lose stock custom recovery forever, that's the risk on a non-dev-edition.
Click to expand...
Click to collapse
Slap was one of the first methods I read about but I was then told that if I ignored the WP fix (like some of the guides leave out), Id have to go into recovery, and then reboot just to make changes to /system, which seems ridiculous. Correct me if I'm wrong.
dray_jr said:
here is a complete guide that i made up hope it helps
http://forum.xda-developers.com/showthread.php?t=2603358
Click to expand...
Click to collapse
I appreciate that thank you.
jl33 said:
Slap was one of the first methods I read about but I was then told that if I ignored the WP fix (like some of the guides leave out), Id have to go into recovery, and then reboot just to make changes to /system, which seems ridiculous. Correct me if I'm wrong.
I appreciate that thank you.
Click to expand...
Click to collapse
np at all let me know if you have any issues
I did it with twrp-2.6.3.1-ghost-4.4.img, i flash it in fastboot, enter the recovery, go to reboot/system, select root, reboot and you are rooted, its simple, its work for me in 4.2.2, 4.4 and 4.4.2
---------- Post added at 02:36 AM ---------- Previous post was at 02:34 AM ----------
if you can read spanish (or translate the page)
http://www.htcmania.com/showthread.php?p=12297991#post12297991
here's everything to change modem, recovery, root and even change the bootloader ulnock logo at the start
rivas1981 said:
I did it with twrp-2.6.3.1-ghost-4.4.img, i flash it in fastboot, enter the recovery, go to reboot/system, select root, reboot and you are rooted, its simple, its work for me in 4.2.2, 4.4 and 4.4.2
---------- Post added at 02:36 AM ---------- Previous post was at 02:34 AM ----------
if you can read spanish (or translate the page)
http://www.htcmania.com/showthread.php?p=12297991#post12297991
here's everything to change modem, recovery, root and even change the bootloader ulnock logo at the start
Click to expand...
Click to collapse
Unfortunately, that method is for unlocked bootloaders
Try it anyways you dont loose anything trying
Enviado desde mi XT1058 mediante Tapatalk
rivas1981 said:
Try it anyways you dont loose anything trying
Enviado desde mi XT1058 mediante Tapatalk
Click to expand...
Click to collapse
Guaranteed it won't work . Otherwise no one would ever unlock their boot loaders.
Sent from my Moto X cellular telephone...
syntrix said:
This.You lose stock custom recovery forever, that's the risk on a non-dev-edition.
Click to expand...
Click to collapse
Not forever. And what's a stock custom recovery? The only thing you lose "forever" is write protection if you use MotoPwnNoMo.
jl33 said:
Slap was one of the first methods I read about but I was then told that if I ignored the WP fix (like some of the guides leave out), Id have to go into recovery, and then reboot just to make changes to /system, which seems ridiculous. Correct me if I'm wrong.
Click to expand...
Click to collapse
I don't find it to be ridiculous at all. Rebooting into "recovery" adds maybe a minute to the whole process.
I'd like the same question as OP answered for the 1053 version. It really grinds my gears that there aren't separate forums for the different versions like they did with the variants of every other god damn phone (Galaxy Nexus as an example).
Sent from my XT1053 using XDA Premium 4 mobile app
elpeterson said:
I'd like the same question as OP answered for the 1053 version. It really grinds my gears that there aren't separate forums for the different versions like they did with the variants of every other god damn phone (Galaxy Nexus as an example).
Sent from my XT1053 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Why do they need separate forums? They all use the same root exploit with firmware specific to their model. There isn't enough development to justify separate forums.
Unlocking the bootloader is the same across the board as is rooting a locked bootloader. The only thing that differs in the entire process is the firmware.
nhizzat said:
Why do they need separate forums? They all use the same root exploit with firmware specific to their model. There isn't enough development to justify separate forums.
Unlocking the bootloader is the same across the board as is rooting a locked bootloader. The only thing that differs in the entire process is the firmware.
Click to expand...
Click to collapse
this phone is very simple let me break it down for you
locked bootloader
unlocked bootloader
lock need to use slapmymoto
unlocked and just install TWRP then install SUPERSU via custom recovery.
my guide tells you what phones can unlock there bootloader and what ones can't.
I'm having what I can only describe as the strangest issue I have ever had with Android in the six years I've been using the platform. I have a Motorola Droid 4 running a CM 11 ROM.
This morning, I noticed my phone was very laggy and slower than I could recall it ever being. I haven't made any changes to it in any way recently, so I just assumed that I needed a reboot.
When I was on the train, I tried to open Reddit Is Fun, but it would only load a black screen. I assumed the app must have updated recently and had a bad update, but that wasn't the case. The app hadn't updated recently, and I didn't know why the app wouldn't load.
So I have bitten the bullet after all of the issues that I was having with my phone today and I did an SBF flash of my Droid 4's firmware. I rooted successfully and installed Busy Box, but I am unable to install Safestrap v3.72
I get to the 60/100 point where it is "Running Installation Script" but it never gets beyond that. I have also tried to Uninstall in case one of the several tries worked behind the scenes, but that also gets stuck at 60/100. This allegedly has something to do with Busy Box not being installed, but I have done that for sure.
Update: Just repeated the root process with SafeRoot and that installs Busy Box as part of the process. Completed successfully, and I'm still hanging at 60/100...
What else am I forgetting to do?
ANY HELP ANYONE CAN PROVIDE IS GREATLY APPRECIATED
Hi, thank you for using XDA Assist. Your best bet is to ask in your device's forum here,http://forum.xda-developers.com/droid-4/help
jd1639 said:
Hi, thank you for using XDA Assist. Your best bet is to ask in your device's forum here,http://forum.xda-developers.com/droid-4/help
Click to expand...
Click to collapse
I posted there, but they closed my post because they said I already posted here. This is some Catch-22 ****...
I'm sorry about that. This should be the one that is closed. I'll ask a mod to move this
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.