Related
Hi,
My Nexus One details are as follows:
Model number : Nexus One
Android version : 2.3.4
Baseband version : 32.50.00.32U_5.12.00.08
Kernel version : 2.6.35.7-ge0fb012
[email protected] #1
Build number : GRJ22
Which is the best way for me to update my phone to ICS (Android 4.0). I have read the official message from Google on categorizing Nexus One as "old" and will no more air the updates.
I am not familiar with the MODs and so; eventhough I scanned through the ROM section; I couldn't figure out myself which way should I opt to upgrade my phone.
Thanks to all for reading my request as it might be a thousandth time such a request is coming through. Thanks for your patience and your advise is eagerly awaited.
Jabir
PS: I have never done a "jailbreak" or "rooting" (whatever name is it) on my phone except those Google aired updates.
You are going to have to root--no way around it
I did it the old fashion way and installed sdk/fastboot oem unlock/flash recovery and a rom with super user in it or flash super user
instructions are in Wiki
there are different ways now I am not familiar with, but prefer the sdk method
you will also need to be on hboot 35.0017 to install blasckrose, although some ICS roms have a miniversion that can run on stock hboot
However, I would root and flash some roms like CM7 stable to get use to things. The hboot and ICS is a bit more complicated at first--read the threads carefully before attempting
Start reading.
http://forum.xda-developers.com/showthread.php?t=1366897
ursJAR said:
Hi,
My Nexus One details are as follows:
Model number : Nexus One
Android version : 2.3.4
Baseband version : 32.50.00.32U_5.12.00.08
Kernel version : 2.6.35.7-ge0fb012
[email protected] #1
Build number : GRJ22
Which is the best way for me to update my phone to ICS (Android 4.0). I have read the official message from Google on categorizing Nexus One as "old" and will no more air the updates.
I am not familiar with the MODs and so; eventhough I scanned through the ROM section; I couldn't figure out myself which way should I opt to upgrade my phone.
Thanks to all for reading my request as it might be a thousandth time such a request is coming through. Thanks for your patience and your advise is eagerly awaited.
Jabir
PS: I have never done a "jailbreak" or "rooting" (whatever name is it) on my phone except those Google aired updates.
Click to expand...
Click to collapse
0. Set up ADB correctly.
1. Root.
2. Optional: Unlock the bootloader
3. Optional: Set SecuFlag off, i.e. S-OFF
4. Fastboot flash a custom recovery
5. Fastboot flash blackrose's hboot. Either stock blackrose or the one specifically for ICS (custom partition layout)
6. Download an ICS ROM of your choosing. My pick would be texasice's.
7. Download an A2SD script as the default one is a li'l buggy.
8. Boot into the recovery of your choosing (4EXT or AmonRa preferred)
9. Make a FULL wipe of settings and partitions and wipe cache and dalvik cache.
10. Flash the ROM zip file
11. Flash the A2SD script file
12. Reboot and boot up your phone. Enter a terminal emulator. Type: su
13. Accept the root request and then type a2sd install,
14. Let your phone reboot on its own and then boot it up again,
15. Return to the terminal emulator, type su and then a2sd cachesd and let it reboot once more.
16. Now you're good to go.
Find out all info on your own, I simply tell you what you need to do.
Theshawty said:
0. Set up ADB correctly.
1. Root.
2. Optional: Unlock the bootloader
3. Optional: Set SecuFlag off, i.e. S-OFF
4. Fastboot flash a custom recovery
Click to expand...
Click to collapse
If you are going to be using fastboot to flash a custom recovery, root is not needed and unlocking the bootloader is not Optional. Root is only needed if you are going to flash the recovery through Android with a program like ROM Manager. Also, S-Off also is something we can't officially get with our phones without using the XTC Clip. But for pretty much all things that we need to do with our phones, S-Off is not required due to it being a dev phone.
As a matter of fact, unlocking the bootloader is actually completely optional, and unless you are doing hardcore modding, completely unnecessary - not to mention that it is the definitive method to losing your warranty. Root, on the other hand, is completely reversible and virtually undetectable if you restore to a stock ROM if you ever need warranty service.
I only started modding recently (a month ago) and in that time, I've already moved to ICS and using a custom Blackrose HBOOT. Its fairly easy - you just have to have the ability to read patiently.
Here is what I would advise, being a bit of a noob myself - yet having never had a single hiccup. This is pretty much the fastest way to do it.
1. Enable USB debugging (in settings>applications>development)
2. Download SuperOneClick (Google it, also has USB drivers if necessary)
3. Connect your phone to the computer, and once all drivers are installed, fire up SuperOneClick, hit 'Root' and watch the magic unfold
4. Download ROM Manager from the Market, follow the instructions (Flash recovery>Download a ROM (CM7 recommended))
Once you are familiar with the basics of installing a ROM from ZIP, head over to the Dev forums, and download ICS for stock HBOOT to get you started!
mrhohoha said:
As a matter of fact, unlocking the bootloader is actually completely optional, and unless you are doing hardcore modding, completely unnecessary - not to mention that it is the definitive method to losing your warranty. Root, on the other hand, is completely reversible and virtually undetectable if you restore to a stock ROM if you ever need warranty service.
Click to expand...
Click to collapse
This is true. I was just going off the instructions that Theshawty wrote. In the instructions he included directions to use fastboot. And without replacing the bootloader to Blackrose (which is probably too in depth to do include here), using fastboot would require the bootloader to be unlocked.
bassmadrigal said:
If you are going to be using fastboot to flash a custom recovery, root is not needed and unlocking the bootloader is not Optional. Root is only needed if you are going to flash the recovery through Android with a program like ROM Manager. Also, S-Off also is something we can't officially get with our phones without using the XTC Clip. But for pretty much all things that we need to do with our phones, S-Off is not required due to it being a dev phone.
Click to expand...
Click to collapse
I have S-OFF'd my device and I didn't use anything called XTC Clip?
Yep. Nothing special required for S-OFF. Heck, you can S-OFF in like 20 seconds by just installing Blackrose! And revert to stock S-ON HBOOT whenever you like!
Using Blackrose does not actually make your device S-Off. The upgraded HBOOT just ignores the flag that is set saying the S-On is still there and displays that you are S-Off. And so, essentially you have S-Off when you use blackrose, but that is only because blackrose ignores the actual setting saying the S-On is still in place. The one thing this will not allow is relocking the bootloader, which full S-Off, when acheived with the XTC Clip, will do.
mrhohoha said:
As a matter of fact, unlocking the bootloader is actually completely optional, and unless you are doing hardcore modding, completely unnecessary - not to mention that it is the definitive method to losing your warranty. Root, on the other hand, is completely reversible and virtually undetectable if you restore to a stock ROM if you ever need warranty service.
I only started modding recently (a month ago) and in that time, I've already moved to ICS and using a custom Blackrose HBOOT. Its fairly easy - you just have to have the ability to read patiently.
Here is what I would advise, being a bit of a noob myself - yet having never had a single hiccup. This is pretty much the fastest way to do it.
1. Enable USB debugging (in settings>applications>development)
2. Download SuperOneClick (Google it, also has USB drivers if necessary)
3. Connect your phone to the computer, and once all drivers are installed, fire up SuperOneClick, hit 'Root' and watch the magic unfold
4. Download ROM Manager from the Market, follow the instructions (Flash recovery>Download a ROM (CM7 recommended))
Once you are familiar with the basics of installing a ROM from ZIP, head over to the Dev forums, and download ICS for stock HBOOT to get you started!
Click to expand...
Click to collapse
The SuperOneClick Application just gets not responding when I click the Root button and after these messages on the right pane are shown
* daemon not running . starting it now on port 5037 *
* daemon started successfully *
Please advise..
Make sure you run it with administrator rights (right click to see the option), and verify that USB Debugging is turned on on the phone. If it is turned on, you need to make sure you have the adb drivers installed (different than the standard USB drivers that windows automatically installs).
Hi all. I have read quite a few pages of the s off blacks install guide. Not really getting it. Can someone please give me simple steps to install blackrose?
Please and thank you.
Sent from my Nexus One using xda premium
Blackrose install guide
Sent from my Nexus One using xda premium
hardrockinandroid said:
Blackrose install guide
Sent from my Nexus One using xda premium
Click to expand...
Click to collapse
Black rose thread http://forum.xda-developers.com/showthread.php?t=1270589
I've read that and everything sounds so complicated. I've watched the vid for resizing partition but they don't say anything. Can someone give a step by step for us noobs for resizing partition please?
Sent from my Nexus One using xda premium
do you have all requirements met from br op page
if so, you need to download the latest br from op and extract it to the download folder you just downloaded br to. then open the extracted folder and clickon br.exe
follow instructions inside the command window that opens
then you need to resize partition to ics sizes thru the breditor
What is op page?Yes bootloader unlocked. Rooted. I have the blackrose zip.the adb and fastboot drivers for windows. Don't know what to do now. I put both files on my desktop. Now what?
Sent from my Nexus One using xda premium
OP page is first page of Dev's thread--mmm
Needs read as well as most of thread to get an understanding of this--lots of folks are running into big trouble if they don't understand it first--
If you are rooted and unlocked do you have sdk installed and can you run adb devices and fastboot devices in command window and see phone's serial number? If so you don't need the usb drivers from OP page--
Yes I have ran commands on a my touch4g, a HTC sensation and a g 2x. Do I just do exactly as the YouTube video shows and then flash the blackrose zip after resizing
the partition? Then flash an Ics Rom?
Sent from my Nexus One using xda premium
So this is my first Nexus device. I'm coming from and S4 followed by a Note 3 so I'm kinda used to the samsung environment and don't want to screw anything up. I have a couple of questions.
First, if I root with CF-Auto Root, does the tool wipe all of the current data?
Second, how will rooting the phone affect the OTA updates and their availability?
Third, are the root apps already compatible with 5.0/Nexus 6?
Thank you!
Cf auto root does not remove all data per se, but unlocking your phone will if it is not.. And it's part of the process.
Rooting probably doesn't affect OTAs, and if it does, can easily be undone.
Yes, I haven't found a common root app that isn't compatible.
Dankchild said:
So this is my first Nexus device. I'm coming from and S4 followed by a Note 3 so I'm kinda used to the samsung environment and don't want to screw anything up. I have a couple of questions.
First, if I root with CF-Auto Root, does the tool wipe all of the current data?
Second, how will rooting the phone affect the OTA updates and their availability?
Third, are the root apps already compatible with 5.0/Nexus 6?
Thank you!
Click to expand...
Click to collapse
1. No it does not wipe your data unless your bootloader was locked.
2. It has no effect. You'll be able to accept the OTA and lose root (you can enable a survival script).
3. Yes.
Dankchild said:
So this is my first Nexus device. I'm coming from and S4 followed by a Note 3 so I'm kinda used to the samsung environment and don't want to screw anything up. I have a couple of questions.
First, if I root with CF-Auto Root, does the tool wipe all of the current data?
Second, how will rooting the phone affect the OTA updates and their availability?
Third, are the root apps already compatible with 5.0/Nexus 6?
Thank you!
Click to expand...
Click to collapse
some people here are wrong, will it wipe data? for the first time (when unlocking the OEM) yes. Lollipop now has a different way to check ROOTING, once it detects you modified ANY file in the system core files, it aborts. To work around this, either use a ROM and upgrade via FLASHING (which i do) or use NEXUS ROOT TOOLKIT. Using the toolkit (which is very noob friendly) allows everything to be done by a click. BUT, to upgrade via toolkit, (ota) you need to flash stock which in the toolkit completely wipe system, then unroot, then update, then reroot and flash whatever ROM you want, which would again wipe your device. the way i do it is easier, it requires no wiping and i get to keep my ROM at all times and i get earlier versions (depending on ROM creators) then OTA, i currently have 5.0.2 on my nexus 6, which isnt ven out yet OTA. :fingers-crossed:
TheSkillfulTroll said:
some people here are wrong, will it wipe data? for the first time (when unlocking the OEM) yes. Lollipop now has a different way to check ROOTING, once it detects you modified ANY file in the system core files, it aborts. To work around this, either use a ROM and upgrade via FLASHING (which i do) or use NEXUS ROOT TOOLKIT. Using the toolkit (which is very noob friendly) allows everything to be done by a click. BUT, to upgrade via toolkit, (ota) you need to flash stock which in the toolkit completely wipe system, then unroot, then update, then reroot and flash whatever ROM you want, which would again wipe your device. the way i do it is easier, it requires no wiping and i get to keep my ROM at all times and i get earlier versions (depending on ROM creators) then OTA, i currently have 5.0.2 on my nexus 6, which isnt ven out yet OTA. :fingers-crossed:
Click to expand...
Click to collapse
People modify the OTA zip to remove the abort of installation if any system files are modified/removed. Of course this can lead to problems, but can also be successful most of the times. Depends on what the user modifies.
Nexus Root Toolkits, I highly do not encourage users to use this. As easy as they are, they prevent users from learning about fastboot and adb. They are essential things to learn and relying on a program to do them for you is not good practice especially when it is quite easy to do it manually. If everybody used the toolkit then no body would understand how its done.
The part about custom ROMs, I recommend using custom ROMs. There are many to browse through, it depends on what you're looking for. Its very exciting to look at all the ROMs to select one to try, just to be eager to try another ROM for fun.
You can read more about toolkits @ http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909
Very good read.
zephiK said:
People modify the OTA zip to remove the abort of installation if any system files are modified/removed. Of course this can lead to problems, but can also be successful most of the times. Depends on what the user modifies.
Nexus Root Toolkits, I highly do not encourage users to use this. As easy as they are, they prevent users from learning about fastboot and adb. They are essential things to learn and relying on a program to do them for you is not good practice especially when it is quite easy to do it manually. If everybody used the toolkit then no body would understand how its done.
The part about custom ROMs, I recommend using custom ROMs. There are many to browse through, it depends on what you're looking for. Its very exciting to look at all the ROMs to select one to try, just to be eager to try another ROM for fun.
You can read more about toolkits @ http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909
Very good read.
Click to expand...
Click to collapse
the toolkit helps alot of new comers who have no idea on what to do, sure they can try the manual way, but doing so can end up very bad as its not easy to revert, while the toolkit helps by being able to bring you back from bricks. i started off using the toolkit and now i just use flashify for rom installations, if anything goes wrong (a brick) i just have tbe option to use the toolkit to set me back to pure stock and factory condition.
TheSkillfulTroll said:
the toolkit helps alot of new comers who have no idea on what to do, sure they can try the manual way, but doing so can end up very bad as its not easy to revert, while the toolkit helps by being able to bring you back from bricks. i started off using the toolkit and now i just use flashify for rom installations, if anything goes wrong (a brick) i just have tbe option to use the toolkit to set me back to pure stock and factory condition.
Click to expand...
Click to collapse
Its very easy to do manually, if it was a long and tedious step such as G1 rooting or manually exploiting a phone then a toolkit is reasonable.
For Nexus 6, its as simple as.
1. install drivers & fastboot.
2. bootloader mode (vol down + power)
3. fastboot oem unlock
4. fastboot flash recovery <name-of-recovery>.img
5. flash supersu
A very good sticky guide is posted, http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
And we all know that regardless if you use a Root Toolkit, you MUST read before you do anything.
Toolkit doesn't really help you bring you back from bricks, in fact I would argue that it does the opposite. You're relying on a program to do what you're supposed to do. In my experience of helping people in XDA forums, they've used toolkits and got themselves into bad positions and wasn't sure how to fix their problem or the toolkit soft-bricking their device. They had to learn fastboot / adb to resolve their issue.
Read the dangers of toolkits, they're not as fancy as people view it to be. Its not difficult to do the tasks manually. Very easy to do. I was able to root/unlock my N6 in a minute since I already had the environment set up.
Think of it this way, you have math homework. You can either go input it into the calculator and have the answer. Congrats, you have the answer but did you understand how they got to that step? No not really.
Its imperative for any user on XDA to learn the fastboot/adb step, its not difficult as I've mentioned time and time again. It takes some reading, but it'll save you time because later down the line you'll understand why you did what you did and you can get yourself out of situations instead of going to Q&A and asking for someone help on how to get back to factory or a soft-brick situation.
A snippet from the link above,
The people who are using these scripts aren't learning what is actually happening when they press 1 on their keyboard. Boom, their phone is unlocked, su-binaries and cwm recovery installed. Then, they flash a rom without creating a nandroid. What happens if something goes wrong and they didn't place any safety nets to help them? They post a thread saying their phone is bricked. People take time out of their day to help these people out, but since the user doesn't understand what the helper is talking about, they can't fix it.
Just last weekend I spent 30 minutes replying to a PM with step by step instructions how to flash stock images and including links to files and resources. The person replied back. Instead of fixing his phone himself, he said he "claimed his phone as stolen and will be getting sent a new one lol". WTF?! Not only is that morally wrong, it's also insurance fraud. And we wonder why carriers and OEM's are trying as hard as they can to lock down non-nexus phones.
Please, take the time to learn how to get yourself out of a mess before you are in a mess.
Click to expand...
Click to collapse
If someone can't take a couple minutes out of their time to follow a step-by-step guide then they shouldn't be tinkering with their device.
For information sake (I have already rooted via TK) your post actually does prove a point. For myself and maybe others, would you be willing to P.M me the instructions to do it via ADB/Fastboot just in case , I , myself get screwed over. Thanks Z
Sent from my Nexus 6 using XDA Free mobile app
flash you phone manually you will learn a lot about how the toolkits work.
I find it faster to flash manually than to use a tool kit.
once an OTA is available you can grap the image from the google site and flash the files manually.
There is a way to manually flash you phone and save userdata so you keep all your apps.
One you learn and get a little practice It will be so easy you will be able to flash like it is second nature. (I was a noob that came from iphone and jailbreaking)
I can actually flash the files manually faster that an OTA can update a phone and I type with maybe a total of 6 fingers. because i never took a typing class
zephiK said:
Its very easy to do manually, if it was a long and tedious step such as G1 rooting or manually exploiting a phone then a toolkit is reasonable.
For Nexus 6, its as simple as.
1. install drivers & fastboot.
2. bootloader mode (vol down + power)
3. fastboot oem unlock
4. fastboot flash recovery <name-of-recovery>.img
5. flash supersu
A very good sticky guide is posted, http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
And we all know that regardless if you use a Root Toolkit, you MUST read before you do anything.
Toolkit doesn't really help you bring you back from bricks, in fact I would argue that it does the opposite. You're relying on a program to do what you're supposed to do. In my experience of helping people in XDA forums, they've used toolkits and got themselves into bad positions and wasn't sure how to fix their problem or the toolkit soft-bricking their device. They had to learn fastboot / adb to resolve their issue.
Read the dangers of toolkits, they're not as fancy as people view it to be. Its not difficult to do the tasks manually. Very easy to do. I was able to root/unlock my N6 in a minute since I already had the environment set up.
Think of it this way, you have math homework. You can either go input it into the calculator and have the answer. Congrats, you have the answer but did you understand how they got to that step? No not really.
Its imperative for any user on XDA to learn the fastboot/adb step, its not difficult as I've mentioned time and time again. It takes some reading, but it'll save you time because later down the line you'll understand why you did what you did and you can get yourself out of situations instead of going to Q&A and asking for someone help on how to get back to factory or a soft-brick situation.
A snippet from the link above,
If someone can't take a couple minutes out of their time to follow a step-by-step guide then they shouldn't be tinkering with their device.
Click to expand...
Click to collapse
Can you provide to me instructions on a manual way? Like the other poster said I would like to learn to manually flash OEM unlucks and root and Roms (if possible) thanks Z! P.M ME if you decide to thanks!
Sent from my Nexus 6 using XDA Free mobile app
if you have drivers installed already from first link above then you can follow these steps:
Download the required factory image files to your computer and extract them
1) Create an empty directory. All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory; (it is easier this way)
2) If all you want to do is unlock your bootloader, skip to step 6 in this section.
3) Download the version of Android you want to your new directory. Make sure you are using a nexus 6 image.
4) Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
5) Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
6) Reboot your device into bootloader mode (by turning it off, hold volume down, and press and hold power) and plug it into your computer;
7) Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt. In Ubuntu just cd to the directory.
Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-some-description-number.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-some-description-number.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Optional, but read note. Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot format cache
14) Reboot: fastboot reboot
15) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked.
No you can root or decrypt. Search for directions on the forum or the internet.
I'm not the original writer of these instructions, but I found these helpful to people wanting the step by step instructions.
TheSkillfulTroll said:
Can you provide to me instructions on a manual way? Like the other poster said I would like to learn to manually flash OEM unlucks and root and Roms (if possible) thanks Z! P.M ME if you decide to thanks!
Click to expand...
Click to collapse
Read the first couple of posts of the following threads. The first talks about how to root, and the other, about how to flash the factory images. Very detailed.
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
If someone can't take a couple minutes out of their time to follow a step-by-step guide then they shouldn't be tinkering with their device.
Click to expand...
Click to collapse
How true. I certainly don't want a paper weight...
Larzzzz82 said:
How true. I certainly don't want a paper weight...
Click to expand...
Click to collapse
Exactly, and if they believe that everything is magical and click on a button "yay I rooted, unlocked my bootloader." Sure you saved time by clicking a button rather than following a step-by-step guide which is quite easy, what happens when you encounter a problem like a soft brick? Questions on whether or not you can flash a older radio etc?
A toolkit can't do that for you, by finding out why something works this way will be better in the long run. I don't mind answering questions but what I do mind is when people use toolkits for something that is already so easy. For Samsung and other manufacturers that lock down their bootloaders, I fully understand why toolkits are needed because they are not unlockable via bootloader mode (unless its HTC, OnePlus, and some other exception) and requires a exploit to obtain root access (e.g. Towelroot).
For Nexus devices (and HTC/OnePlus/etc) devices where the company gave you a "fastboot oem unlock." Use it very simple to do. The hardest part is installing a driver and fastboot executable, which if you have a mac you don't even need the driver. Once you do it once, you're set for life on that computer. When I unlocked my N6, I just literally plugged it in... activated the OEM unlock via developer options and went into bootloader mode and typed fastboot oem unlock.
Finished that all in one minute.
zephiK said:
Exactly, and if they believe that everything is magical and click on a button "yay I rooted, unlocked my bootloader." Sure you saved time by clicking a button rather than following a step-by-step guide which is quite easy, what happens when you encounter a problem like a soft brick? Questions on whether or not you can flash a older radio etc?
A toolkit can't do that for you, by finding out why something works this way will be better in the long run. I don't mind answering questions but what I do mind is when people use toolkits for something that is already so easy. For Samsung and other manufacturers that lock down their bootloaders, I fully understand why toolkits are needed because they are not unlockable via bootloader mode (unless its HTC, OnePlus, and some other exception) and requires a exploit to obtain root access (e.g. Towelroot).
For Nexus devices (and HTC/OnePlus/etc) devices where the company gave you a "fastboot oem unlock." Use it very simple to do. The hardest part is installing a driver and fastboot executable, which if you have a mac you don't even need the driver. Once you do it once, you're set for life on that computer. When I unlocked my N6, I just literally plugged it in... activated the OEM unlock via developer options and went into bootloader mode and typed fastboot oem unlock.
Finished that all in one minute.
Click to expand...
Click to collapse
I agree the hardest part for me was on windows trying to get the stupid drivers to work correctly.
Dumped windows for Linux and followed the manual steps i found on XDA and never looked back.
No drivers needed in Linux either.
TheSkillfulTroll said:
some people here are wrong, will it wipe data? for the first time (when unlocking the OEM) yes. Lollipop now has a different way to check ROOTING, once it detects you modified ANY file in the system core files, it aborts. To work around this, either use a ROM and upgrade via FLASHING (which i do) or use NEXUS ROOT TOOLKIT. Using the toolkit (which is very noob friendly) allows everything to be done by a click. BUT, to upgrade via toolkit, (ota) you need to flash stock which in the toolkit completely wipe system, then unroot, then update, then reroot and flash whatever ROM you want, which would again wipe your device. the way i do it is easier, it requires no wiping and i get to keep my ROM at all times and i get earlier versions (depending on ROM creators) then OTA, i currently have 5.0.2 on my nexus 6, which isnt ven out yet OTA. :fingers-crossed:
Click to expand...
Click to collapse
Yes, this is my main concern. Back in my Samsung days, i remember flashing ROMs everyday, but the whole wiping got really annoying. When i got my Nexus 5 i just kept it stock. Now I do want to root to use the double tap to wake and the LED, but i don't want to wipe everytime there's an update. From what I remember, whenever you flash a ROM you have to wipe the phone. So is there a way around having to wipe your phone completely everytime there's an update?
miike1106 said:
Yes, this is my main concern. Back in my Samsung days, i remember flashing ROMs everyday, but the whole wiping got really annoying. When i got my Nexus 5 i just kept it stock. Now I do want to root to use the double tap to wake and the LED, but i don't want to wipe everytime there's an update. From what I remember, whenever you flash a ROM you have to wipe the phone. So is there a way around having to wipe your phone completely everytime there's an update?
Click to expand...
Click to collapse
Say you flashed SimpleAosp which is currently 5.0.2, whenever 5.0.3 comes out you need to Download it on your phone, open flashify and boot into TWRP, in there you need click install then DONT WIPE, find the updated version and flash over the current one, reboot and bam, you have new version and you didn't lose anything. Only do this method if you are transition from the same ROM to a new one, if you decided to go from SimpleAosp to liquidsmooth you need to wipe.
Sent from my Nexus 6 using XDA Free mobile app
TheSkillfulTroll said:
Say you flashed SimpleAosp which is currently 5.0.2, whenever 5.0.3 comes out you need to Download it on your phone, open flashify and boot into TWRP, in there you need click install then DONT WIPE, find the updated version and flash over the current one, reboot and bam, you have new version and you didn't lose anything. Only do this method if you are transition from the same ROM to a new one, if you decided to go from SimpleAosp to liquidsmooth you need to wipe.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Ah ok, this is what i was looking for.
miike1106 said:
Ah ok, this is what i was looking for.
Click to expand...
Click to collapse
Or... You could live dangerously and try a dirty flash first every time... Worst case... You go back and wipe in recovery
miike1106 said:
Yes, this is my main concern. Back in my Samsung days, i remember flashing ROMs everyday, but the whole wiping got really annoying. When i got my Nexus 5 i just kept it stock. Now I do want to root to use the double tap to wake and the LED, but i don't want to wipe everytime there's an update. From what I remember, whenever you flash a ROM you have to wipe the phone. So is there a way around having to wipe your phone completely everytime there's an update?
Click to expand...
Click to collapse
You can dirty flash but this is only the case when you update from the same ROM to a newer update of the version.
When we say wipe, it only wipes the OS not internal storage.
I'm new to android.I'm quite confused about the whole custom Rom installation process.I managed to unlock bootloader and root my phone.I tried to find guides to let me install custom roms on my device.I have a vague idea about the whole process but whenever I look at a ROM release thread, half the information there is beyond me.I would be happy if someone pointed me in the right direction to a complete guide with noob friendly instructions.Also, I would prefer to stay S-On, can someone help me with the whole s-off regarding custom Rom stuff too?
Thanks.
Sent from my HTC One using XDA Free mobile app
Nanda K said:
I'm new to android.I'm quite confused about the whole custom Rom installation process.I managed to unlock bootloader and root my phone.I tried to find guides to let me install custom roms on my device.I have a vague idea about the whole process but whenever I look at a ROM release thread, half the information there is beyond me.I would be happy if someone pointed me in the right direction to a complete guide with noob friendly instructions.Also, I would prefer to stay S-On, can someone help me with the whole s-off regarding custom Rom stuff too?
Thanks.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
You don't need s-off to flash most custom roms. Only some GPE version will require s-off.
Flash twrp 2.8.5.0
boot your phone in recovery mode
plug your phone to your pc
place your rom.zip on your phone storage
in twrp select "install"
choose your rom.zip
swipe to flash
Follow instructions from the rom installer (aroma installer)
reboot
Nanda K said:
I'm new to android.I'm quite confused about the whole custom Rom installation process.I managed to unlock bootloader and root my phone.I tried to find guides to let me install custom roms on my device.I have a vague idea about the whole process but whenever I look at a ROM release thread, half the information there is beyond me.I would be happy if someone pointed me in the right direction to a complete guide with noob friendly instructions.Also, I would prefer to stay S-On, can someone help me with the whole s-off regarding custom Rom stuff too?
Thanks.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Ill be honest. Doing things like this are not meant to be noob friendly.
Take about a week and do lots of reading this way if something goes wrong you will know how to recover.
That's what I'm having trouble with.I cant seem to find any solid reading material for stuff like these.For example, will restoring a nandroid backup really fix problems like bootloops and other errors you may run into while flashing ROMS? Also,how do kernels and ROMs match up? are they independent of each other or do certain ROMs work only when you have a particular kernel installed? will a wrong kernel cause any issues with certain ROMs and I'm seriously scared of bricking my device since the amount you're required to know is quite vast.I used to have an iPhone until the HTC One M7 and I was pretty much an advanced user on the iOS platform.I wouldnt call myself a noob, but I cant call myself an advanced android user either.Atleast not yet.
Nanda K said:
That's what I'm having trouble with.I cant seem to find any solid reading material for stuff like these.For example, will restoring a nandroid backup really fix problems like bootloops and other errors you may run into while flashing ROMS? Also,how do kernels and ROMs match up? are they independent of each other or do certain ROMs work only when you have a particular kernel installed? will a wrong kernel cause any issues with certain ROMs and I'm seriously scared of bricking my device since the amount you're required to know is quite vast.I used to have an iPhone until the HTC One M7 and I was pretty much an advanced user on the iOS platform.I wouldnt call myself a noob, but I cant call myself an advanced android user either.Atleast not yet.
Click to expand...
Click to collapse
Wow yeah you need to do alot of reading then. Now while I mean no insult. Being an advanced user for IOS and jumping to android is like going from first grade and then jumping to the 12th.
Yes depending on the device kernels only work with matching roms. Take the m7 you mentioned. You have 4 kind of kernels. AOSP, AOSP-Caf, Sense and CM
Each has to be paired with a matching rom. IF you flash the wrong one then it can cause a bootloop. Never expect a nandroid to be a fix all. While it will fix things alot of the time it is not an end all to fixing a bad flash. Sometimes you will have to flash things with a bootloader from command line. Depending on your OS on your PC there could also be other issues. So at times you may need a linux based live disc or partition.
Nanda K said:
That's what I'm having trouble with.I cant seem to find any solid reading material for stuff like these.For example, will restoring a nandroid backup really fix problems like bootloops and other errors you may run into while flashing ROMS? Also,how do kernels and ROMs match up? are they independent of each other or do certain ROMs work only when you have a particular kernel installed? will a wrong kernel cause any issues with certain ROMs and I'm seriously scared of bricking my device since the amount you're required to know is quite vast.I used to have an iPhone until the HTC One M7 and I was pretty much an advanced user on the iOS platform.I wouldnt call myself a noob, but I cant call myself an advanced android user either.Atleast not yet.
Click to expand...
Click to collapse
Your in safe hands with this forum....theres not nuch that cannot be solved if you go wrong,however there are a multitude of good videos on you tube .
I found this guys videos very easy to follow https://www.youtube.com/channel/UCKlOmM_eB0nzTNiDFZibSSA
A little out of date now but a good image of what to do,backed up with the knowledge base on this forum its relatively easy!
Once you have a custom recovery make back ups before you do anything,I found buying an OTG cable and USB drive a good way to create lots of back ups ,so if things go wrong you have a good restore point.
Unlikely to brick your device if you keep S-on ,build up your confidence and go S-off when you can...its like xmas everyday once you know how to use the power it brings!
Okay,let me start off simple.My HTC One M7 is on complete stock now.Running Lollipop from HTC.It is an unlocked Hong Kong version.Bootloader unlocked and TWRP recovery flashed.I need a kernel which will enable motion launch gestures as on the one m8 and also functions like sweep2wake etc.Can someone link me to the appropriate kernel to flash?
I know how to flash the kernel, I have trouble choosing the right one.
Sent from my HTC One using XDA Free mobile app
Nanda K said:
Okay,let me start off simple.My HTC One M7 is on complete stock now.Running Lollipop from HTC.It is an unlocked Hong Kong version.Bootloader unlocked and TWRP recovery flashed.I need a kernel which will enable motion launch gestures as on the one m8 and also functions like sweep2wake etc.Can someone link me to the appropriate kernel to flash?
I know how to flash the kernel, I have trouble choosing the right one.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
If you are running stock rom (sense 6) + lollipop and your phone is a M7_UL or M7_U then ElementalX 20.1 should work fine
From one noob to another haha
I really like ViperOne mods, but I haven't used Elements.
alray nailed it -- easiest ROM install.
you need to install TWRP first.
I used the HTC One Toolkit for this, you can find it on XDA. (Sorry new user, I can't post links)
I assume your phone is still unlocked. -- if not, unlock it
Have Debug mode Enabled on your phone. (Settings -> About -> Software information -> More -> Click Build number 10 times)
Settings -> Developer options -> USB Debugging -> Checked
Using HTC One Toolkit, click ADB -> Devices
this will start adb. you might wait a second or 5 for your device to be shown.
Then click the Pull down reboot menu select bootloader, then click Reboot.
-the phone should reboot into the Bootloader.
Select Fastboot, press power button.
Then in HTC One Toolkit, close the adb window and click Fastboot.
Click Devices
-Your device should show in the main HTC One Toolkit window.
Once you see that, Under Label Flash, press ... button and select the TWRP you just downloaded. Then select Partition Recovery, then Flash.
Once complete and successful, reboot the phone into Recovery from the phone's menu.
!! NOTE !! You must reboot into Recovery before starting the ROM. Or it may re-write the Recovery.
Once in Recovery, reboot the phone from within Recovery and let it start normally.
Copy your rom (in .zip format) onto your phone. I make new folder called roms or mods on my phones so I don't lose track of where things are.
Once your Rom is copied to your phone (I suggest ViperOne 8.0.0.0), use ADB again and reboot the phone into recovery.
From TWRP Touch Install
navigate to your folder where your ROM is (zip file)
Click it and install.
I wipe all settings when I install a new ROM.
Good luck!
B
_FBi said:
I used the HTC One Toolkit for this, you can find it on XDA. (Sorry new user, I can't post links)
Using HTC One Toolkit, click ADB -> Devices
Then in HTC One Toolkit
-Your device should show in the main HTC One Toolkit window.
Click to expand...
Click to collapse
And I would highly recommend not using any toolkits but instead take an extra 30 mins to learn how to use adb and fastboot properly so if something bad happens you know how to deal with it.
Most noobs are totally stuck if something is not working as expected when using a toolkit. Wen you took the time learning adb and fastboot you'll know how to deal with most issues when flashing roms/recovery/ruu/frimware/kernel/radio and more. When you did not took any time to learn adb and fastboot and using a toolkit instead, when something unexpected happen, you'll just be stuck there because your little toolkit doesn't have any "I'm screwed, what should I do?" button.
alray said:
And I would highly recommend not using any toolkits but instead take an extra 30 mins to learn how to use adb and fastboot properly so if something bad happens you know how to deal with it.
Most noobs are totally stuck if something is not working as expected when using a toolkit. Wen you took the time learning adb and fastboot you'll know how to deal with most issues when flashing roms/recovery/ruu/frimware/kernel/radio and more. When you did not took any time to learn adb and fastboot and using a toolkit instead, when something unexpected happen, you'll just be stuck there because your little toolkit doesn't have any "I'm screwed, what should I do?" button.
Click to expand...
Click to collapse
I have nothing against using using tools, so long as they're trusted.
Nor is there anything wrong doing it by hand, if not more beneficial.
All in one tools bypass a lot of the understanding.
Alray's first post was right to the point, basic, and a perfect example.
B
I do know how to use adb and command line to do all that.Intact I did not know that there was a toolkit to do this before I read that post
I do have some experience with the HTC wildfire and sensation XL.But they were considerably older devices which I used a long time ago as temporary ones.
The HTC One is my first non iOS device.
Sent from my HTC One using XDA Free mobile app
Hello everyone! I was hoping to root my Nexus 6 with Android 6.0 on board but I can't seem to find any info on the topic, can anyone help me out??
Thanks!
ichigo663 said:
Hello everyone! I was hoping to root my Nexus 6 with Android 6.0 on board but I can't seem to find any info on the topic, can anyone help me out??
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3059493
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
Anything that can be done on a Linux system?
Don't use toolkits on marshmallow.
Download TWRP, fastboot flash it, flash custom kernel, and SuperSu 2.52
Sent from my Nexus 6 running cyosp using Tapatalk
Can any of these be done without a computer. I only have my phone
pitbullmommy45245 said:
Can any of these be done without a computer. I only have my phone
Click to expand...
Click to collapse
No you will need a computer to do this. I would not advise modding your device at all if you do not have access to a PC.
That root kit worked for me on MM and was easy. Why?
Found this http://forum.xda-developers.com/nexus-6/help/root-computer-t3218176
khw1959 said:
That root kit worked for me on MM and was easy. Why?
Found this http://forum.xda-developers.com/nexus-6/help/root-computer-t3218176
Click to expand...
Click to collapse
Dont even get me started on using a kit.
As to why. If something goes wrong you will need a PC to fix it.
khw1959 said:
That root kit worked for me on MM and was easy. Why?
Found this http://forum.xda-developers.com/nexus-6/help/root-computer-t3218176
Click to expand...
Click to collapse
Because if something goes sideways, and eventually it will, youl'll have no clue what it did, and how to fix it.
Nexus phones have open source tools, adb and fastboot, to manipulate them, they are very easy and straightforward to use.
I understand that coming from different phones, that only have hacks and tricks to unlock the bootloader and change the recovery, using tools seems obvious, but with a Nexus it's counterproductive, and makes fixing things so much harder.
Sent from my Nexus 6 running cyosp using Tapatalk
Thank for that insight. I wanted and took the easy/prepared route for unlocking and root of this phone. I was once familiar with manual way when the N2 was unlocked. I got to re-learn again. My last job made me very anal retentive about following instructions, and I think that made the rootkit easy to use. In 3 days I used it when I got with 5.1.1 and yesterday for 6.0. Today I flash Roms to find the one I like.
ichigo663 said:
Anything that can be done on a Linux system?
Click to expand...
Click to collapse
Adb and fastboot work on linux.
Any easy way to root 58r ??
Exqctly like K and N. Flash modified boot.ing, and flash SuperSu.zip in TWRP.
Sent from my Nexus 6 running cyosp using Tapatalk
Why do people keep saying you need a custom kernel??? BTW, used nexus root toolkit on the K build without problems, no luck on R(never had N) but the tool got updated.... However... I would not be using any thing chainfire Su related sinds it got sold out.
ghost010 said:
Why do people keep saying you need a custom kernel??? BTW, used nexus root toolkit on the K build without problems, no luck on R(never had N) but the tool got updated.... However... I would not be using any thing chainfire Su related sinds it got sold out.
Click to expand...
Click to collapse
Because at one time it did require a kernel change to get root.
ghost010 said:
Why do people keep saying you need a custom kernel??? BTW, used nexus root toolkit on the K build without problems, no luck on R(never had N) but the tool got updated.... However... I would not be using any thing chainfire Su related sinds it got sold out.
Click to expand...
Click to collapse
Because you needed a custom boot.img to root 58K too. It will either contain a modified kernel with SELinux set to permissive (I've patched mine by hand, so I know what I'm talking about), or contain an updated sepolicy binary to allow su to work. Also since you said you didn't have red triangle, it means your fstab.shamu was also replaced with one with disabled verity.
So. Don't use rootkits. If you do use rootkits and discover you don't know what's happening, at least please don't keep correcting those who try to help you.
scryan said:
Adb and fastboot work on linux.
Click to expand...
Click to collapse
I was hoping that someone would answer this. Flashing files and rooting on Linux is MUUUUCH easier than Windows. Why? No need for special drivers to recognize your device.
Even better, if you try to run a adb/fastboot command without having them installed, Linux will tell you the actual command for you to type and download/install them...all within the command window.
This might sound confusing, but it is really easy and seamless, in my opinion.
AarSyl said:
I was hoping that someone would answer this. Flashing files and rooting on Linux is MUUUUCH easier than Windows. Why? No need for special drivers to recognize your device.
Even better, if you try to run a adb/fastboot command without having them installed, Linux will tell you the actual command for you to type and download/install them...all within the command window.
This might sound confusing, but it is really easy and seamless, in my opinion.
Click to expand...
Click to collapse
Most of what you said depends on your distro.
On Arch you definitely need to add u-dev rules for the phone to be noticed, and if you dont have them installed and you try to run it, it won't tell you how to download.
But.... If you install via a package manager it will be automatically added to your path
Also, I have NEVER downloaded drivers for my phone in windows, and never needed to.
That's good to know. I should've added that I use Ubuntu as my distro, and I love it.
Hello I just a bought a Nexus 6. When I connected to internet it downloads the system update. When I press install the phone restarts and navigate to twrp recovery Now the problem is the langyage of twrp is I think Korean. So how do I change this?
God, people selling phones and not bothering flashing stock first...
Download Nexus Root Toolkit, do flash stock + unroot and then lock your bootloader.
Nexus Tool Kit *cringe* *throws up in mouth*
Download the latest factory image from here and after extracting it just run "flash-all" and it will put you up to date with the latest factory image. It gives you a clear guide there on how to do it but you can also search on this forum and there are more guides. I strongly advise you take the 5 minutes to learn how to do this rather than rely on a toolkit, for Nexus devices it's inexcusable. This is just an opinion, so don't get mad at me if you rely on one of these toolkit nonsense utilities.
Explain more
Lawstorant said:
God, people selling phones and not bothering flashing stock first...
Download Nexus Root Toolkit, do flash stock + unroot and then lock your bootloader.
Click to expand...
Click to collapse
Can you please it more? Please.