Database Develop

[Guide]Safely root the nexus 5 and keep warranty

I did this with my nexus 5 and I thought It should be useful and handy as well as useful to keep warranty.
I want to thank all the great devs who have made all this things down here and made our devices more useful
+Chainfire​
Osmosis
And the ppl on XDA
THIS IS THE SAFEST AND THE MOST USEFUL WAY OF ROOTING AND UNLOCKING BOOTLOADERS AND STILL KEEPING WARRANTY
FIRST OF ALL FEW THINGS ABOUT NEXUS 5 WE MAY OR MAY NOT KNOW
1:- THERE IS A NEW IMPLEMENTATION LIKE WHAT SAMSUNG DID FROM NOTE 2, S3 AND SOME DEVICES AFTER THAT LIKE THE EFS PARTITION AND FLASH COUNTER THEORIES (THE REASON WHY I HATE SAMSUNG'S PLASTIC ****)
2:- IN NEXUS 5 WE DONT HAVE A SEPERATE PARTITION FOR EFS BUT THE THING IS PUT IN BY GOOGLE. IT CAN ACCIDENTALLY WIPE WHILE FLASHING CUSTOM ROMS, FACTORY IMAGES OR ANY OTHER THING AND MAY RENDER YOUR DEVICE USELESS LEAVING YOU WITH A DEVICE WITH UNKNOW IMEI AND SERIAL NUMBER ( THERE IS ONE CASE OF THIS THING HAPPENING TO A USER ON XDA)
3:- THE BOOTLOADER HAS A HASTAMPER FLAG WHICH WHEN REBOOTING TO BOOTLOADER AND CONNECTED TO THE PC AND RUNNING A COMMAND IN COMMAND PROMPT IN WINDOWS AND TERMINAL IN LINUX AND MAC ( I HATE APPLE)
AND TYPING IN THE COMMAND fastboot oem device-info
Displays this three things:-
Device tamper: [true/false]
Boot loader unlock : [true/false]
Secure boot:[enabled/disabled]
Now we all know the ppl at the manufacturing company [Samsung for gnex/ lg for nexus 4]
Use to see our bootloader status for warranty
Now things and technology have changed and so is the security and policies of companies
So if the device tamper shows true then be aware that the warranty is void of our very own latest Google flagship phone
THINGS THAT WE NEED FOR ROOTING AND BACKING UP RECOVERY, EFS AND CHANGING THE DECIVE TAMPER FLAG TO FALSE
1:adb and fastboot tools for Linux/windows/MAC search it on google to how to setup Adb and fastboot for your respective OS
Also enable development settings by tapping build number in 7 times and enable USB debugging in development settings and don't consider yourself a developer after doing so, it need much more to be a developer in Android
2:-cf-auto-root from
http://forum.xda-developers.com/showthread.php?t=2507211
you will get all the info that the cf-auto-root will wipe all your data and unlock your bootloader, so make a backup of all your data and all those things that you want
Now we have a rooted devices
Now download http://downloads.codefi.re/autoprime/LG/Nexus_5/Nexus_5_Backup_EFS.zip and copy it to the sdcard
2:- now we need to relock the bootloader
This step needs two things
A custom recovery either twrp or Clockworkmod I prefer Twrp over cwm (Twrp is user friendly but when it comes to flashing my favorite ROM Catacalysm, I prefer Cwm )
Download this
http://forum.xda-developers.com/showthread.php?t=2239421 and move it to the internal storage
Done with the recovery. Now copy the recovery in platform-tool in Android-Sdk in window. Or if u are in Linux then copy it to the Home directory not on desktop.
Now open Terminal
And type
sudo apt-get install adb
sudo apt-get install fastboot
This will install adb and fastboot
Now navigate to the folder in which you have saved the recovery
By cd ~/Home
In windows copy the recovery.img to platform tools that is better rather than CD ing
And hold shift and right click and select open command prompt here
Now u are ready for the commands to put in
There are no different commands for windows and Linux but Mac have commands like ./fastboot
So now connect the device The. Computer and start the commands to put in
1st command
adb devices
Accept what pops up on your device
2nd command
adb reboot-bootloader (Linux)
adb reboot bootloader (windows)
./adb reboot-bootloader (Mac)
Now you may know what the command does it will reboot to bootloader
3rd Command
fastboot devices
The serial number show up with device online status
4th command
fastboot oem device-info the one I mentioned previously It above
It will display the device tamper and bootloader info
5th command
Ensure that you have the recovery.img in platform-tools and your command prompt is opened in platform-tools/ you have navigated to the directory in which the recovery is placed
Now type the following command
fastboot boot recovery.img
(Ensure that the downloaded recovery is renamed to recovery.img | if while renaming in windows it may come out like recovery.img.img so just remove the one .IMG )
This won't replace the stock recovery partition
But
Your device will boot into Twrp
Or Cwm only
Here make a system backup Advanced backup will have an option for efs backup just tick all of others except the efs and backup. It will be saved to sdcard and move it to ur PC This will be helpful while Ota updates. If u want you can backup efs also. You can follow this step to recover everything at the time of OTA
4)
Now when u are in the recovery just flash the cwmnexusbooloaderunlock.zip
And Nexus_5_Efs_backup.zip one after the another.
BY THIS PROCESS YOU WILL RELOCK THE BOOTLOADER AND CHANGE THE HASTAMPER TO FALSE. YOU CAN CHECK THAT AGAIN BY THE 4TH COMMAND MENTIONED ABOVE. You will also have a folder in the sdcard with efs1,efs2 and efsflashable.zip named efs_backup transfer / copy this to PC AND FLASH THIS WHENEVER U LOSE THE SERIAL NUMBER AND IMEI
WITH THIS YOU HAVE A ROOTED DEVICE WITH A BOOTLOADER LOCKED AND WARRANTY INTACT
Now download 3 apps from play store
Flashify
Bootunlocker
Use flashify to backup current recovery and kernel
And bootunlocker to unlock the bootloader without tampering the
Hastamper flags and without wiping data and u can relock with the same u can verify it by my favorite command
Optional :-
Use tasker and its plugins and follow every tutorial about tasker
Actions that I use are like call recording , wave to take call, and activating voice while incoming call when in silent mode.
I also use xposed framework
Gravitybox, AppsOpsXposed, Google search Api , smoother system progress bars.
ROMS AND KERNELS I USE ARE
OMNIROM:- BEING A CONTRIBUTOR
CATACALYSM:- Favorite
Might come with my own ROM in the future
KERNELS:-
BRICKED, FRANCO AND ELEMENTAL X
I MAY ALSO COME UP WITH A KERNEL OF MY OWN NAMED PRIME KERNEL IN JANUARY
BACKUP APPS:-
GO BACKUP
TITANIUM BACKUP
THIS WILL BE USEFUL WHEN U RETURN TO STOCK WITH TWRP U CAN USE THEM TO GET YOUR APPS AND GET THE OTA WITHOUT LOOSING THE DATA
KUDO AND THANKS TO ALL THE DEVELOPERS AND PEOPLE AND ALL THE BEST WITH ROOTING AND DONT MESS UP YOUR DEVICE AND
FOLLOW THE COMMAND PROPERLY I HAVE DONE THIS MANY A TIMES DO IT PROPERLY I AM NOT RESPONSIBLE IF YOU GO WRONG AND MESS UP YOUR DEVICE
The EFS BACKUP SCRIPT IS NOT MY CREATION AND NOT THE SCRIPT THAT RELOCKS THE BOOTLOADER
OSMOSIS MADE THE CWM UNLOCK BOOTLOADER SCRIPT AND SORRY THE PERSON WHO MADE THE EFS BACKUP SCRIPT I AM REALLY SORRY I DONT REMEMBER YOUR NAME THANKS TO ALL OF YOU GUYS
ALL THE BEST 
Sent from my Nexus 5 using XDA Premium 4 mobile app

Mohhamad Rehan said:
2:- now we need to relock the bootloader
This step needs two things
A custom recovery either twrp or Clockworkmod I prefer Twrp over cwm (Twrp is user friendly but when it comes to flashing my favorite ROM Catacalysm, I prefer Cwm )
Download this
http://forum.xda-developers.com/showthread.php?t=2507211 and move it to the internal storage
Click to expand...
Click to collapse
This links to Chainfire's Auto-Root thread. Is that correct?

Yes but its not the download page its the thread just follow it properly and read it
Sent from my Nexus 5 using XDA Premium 4 mobile app

Oops sorry I will edit
Sent from my Nexus 5 using XDA Premium 4 mobile app

OP UPDATED
Sent from my Nexus 5 using XDA Premium 4 mobile app

Super. I already rooted and such but I didn't even consider relocking the bootloader and resetting the tamper flag.
Great guide.

Nexus Tool Kit can do all this for you no need to do this on your own by typing in commands, just saying.

OK does wugfresh and skipsoft relock and changes the hastamper flags to false there is a difference in toolkits and actual guides I wrote this because I did not want any thanks but I just wanted to share what I did. I don't have any harsh feelings towards toolkit but after sometime they make you lazy and you won't learn. Just Read the whole thread and tell me if its useful or not. I am a Linux user so I don't use toolkits
Sent from my Nexus 5 using XDA Premium 4 mobile app

I just want you to ask mskip and the wugfresh toolkit creater that does their toolkits changes hastamper flags to false after unlocking the bootloader
Sent from my Nexus 5 using XDA Premium 4 mobile app

Deleted

egofreak said:
Deleted
Click to expand...
Click to collapse
What deleted
Sent from my Nexus 5 using XDA Premium 4 mobile app

Have there been any reports of Google / LG not honouring the warranty due to this flag? My first N5 went back to LG on a warranty swap with just a regular bootloader relock. Haven't heard a complaint yet.
Sent from my Nexus 5 using Tapatalk

cmstlist said:
Have there been any reports of Google / LG not honouring the warranty due to this flag? My first N5 went back to LG on a warranty swap with just a regular bootloader relock. Haven't heard a complaint yet.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Well there may or may not be any smart customer service agents there but maybe we sometimes don't have luck so we can have a problem then my guide just for help but it may or may not be helpful but I think is worth it and its main moto is to unlock and relock the bootloader without loosing data and messing up the temper flag and backing up the efs

cmstlist said:
Have there been any reports of Google / LG not honouring the warranty due to this flag? My first N5 went back to LG on a warranty swap with just a regular bootloader relock. Haven't heard a complaint yet.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Sent mine back with standard boot loader lock as well, we'll see how this turns out. Had no idea Google was flagging now.

mr mystery said:
Sent mine back with standard boot loader lock as well, we'll see how this turns out. Had no idea Google was flagging now.
Click to expand...
Click to collapse
mr mystery said:
Sent mine back with standard boot loader lock as well, we'll see how this turns out. Had no idea Google was flagging now.
Click to expand...
Click to collapse
So can u give us an update regarding ur device
Sent from my Nexus 5 using XDA Premium 4 mobile app

I sent mine back with a standard bootloader relock. A few days ago I phoned Google to verify that everything is in order. They said yes, the case is closed. I did not ask about bootloaders and they did not indicate any red flags.

Mohhamad Rehan said:
So can u give us an update regarding ur device
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Once I know I'll update, the returned device was signed for yesterday evening, not sure how long the process takes after that.

HASTAMPER switch possibly remnant from G2 as they are similar device.

Mohhamad Rehan said:
Download this
http://forum.xda-developers.com/showthread.php?t=2239421 and move it to the internal storage
Click to expand...
Click to collapse
Which of these files I have to download? Screenshot

eXtreme117y said:
Which of these files I have to download?
Click to expand...
Click to collapse
cwm-Nexus.BootUnlocker.zip

Root error

Hello, I've been wanting to root my HTC One for a while and now I actually sat down and began searching for guides etc and I went on htconeroot.com and used their guide but whenever I try to even finish the first step, I get the message "adb unable to connect for backup"
this makes 0 sense to my mind as I've never really tried modifying things in batch before, I just want to root it so I can use the google rom
relevant information: stock android 4.3 sense 5.5, using pc with w8
guide I used but didn't work due to bat message: htconeroot.com/ htc-one-root/how-to-root-htc-one-windowsmaclinux
edit: testing with hasoon200 toolkit I can't get past token ID cause it says error device offline

nickiallstr said:
Hello, I've been wanting to root my HTC One for a while and now I actually sat down and began searching for guides etc and I went on htconeroot.com and used their guide but whenever I try to even finish the first step, I get the message "adb unable to connect for backup"
this makes 0 sense to my mind as I've never really tried modifying things in batch before, I just want to root it so I can use the google rom
relevant information: stock android 4.3 sense 5.5, using pc with w8
guide I used but didn't work due to bat message: htconeroot.com/ htc-one-root/how-to-root-htc-one-windowsmaclinux
edit: testing with hasoon200 toolkit I can't get past token ID cause it says error device offline
Click to expand...
Click to collapse
Did you tried the official XDA method? Very easy.
http://forum.xda-developers.com/htc-one#root

Im also having problems with rooting. I unlocked my bootloader, instaled twrp and even installed the viper rom. After going back to my recovery of the original rom, Im having problems with root, cant install any rom and when i try to re root it, console shows me error:device offline. I updated all of the drivers. I used All in one kit by hasoon2000 for everything. Any ideas anyone?

ketto said:
Im also having problems with rooting. I unlocked my bootloader, instaled twrp and even installed the viper rom. After going back to my recovery of the original rom, Im having problems with root, cant install any rom and when i try to re root it, console shows me error:device offline. I updated all of the drivers. I used All in one kit by hasoon2000 for everything. Any ideas anyone?
Click to expand...
Click to collapse
download and install from recovery
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip

Tnx, Ill try that

bootloop with locked bootloader

Hello
So I recently brought a second hand nexus 6 for cheap since it was described as bootlooping and the owner couldn't fix it. I already have a fully working nexus 6 so decided to get this as a potential source for spares assuming I couldn't get it working to be used as a 2nd phone. Having received it today, I found that when turned on, it would get stuck at the white "google" screen and go no further than that. I can access the bootloader and the stock recovery. The bootloader is locked and since the "allow oem unlock" option has been added to lollipop (which I had not even heard of till looking into why I couldn't unlock this device), I can't seem to unlock it, so i'm at a loss. So far i've tried;
-unlocking the bootloader using fastboot oem unlock
-fastboot format cache/data (both saying the BL needs to be unlocked, even though people have said they've managed with it locked)
-flashing roms via fastboot (that obviously didn't work)
-using the "apply update from adb" option to install a stock zip from google (error "signature verification failed")
-same as above, but with custom roms (gave the error "failed to verify whole-file signature")
-same as above again ,but with the OTA of the next android version, in the hope I could continue flashing these till I reached a major one and then it would work (came back saying "system partition has unexpected contents)
-making a nandroid of my working phone, and making a bootable zip of that ("signature verification failed")
I've basically reached a point now where I imagine it's probably not ever gonna work and i'm gonna have to give up, but I figured requesting here can't hurt and I don't wanna give up knowing that something could work, I just never found out about it. I also can't help but think that given I have a working nexus 6, there must be something I can do with that to make the new one work (the only idea I had was the nandroid of it, but there may be something else)
Cheers
Cameron

That phone is not pining for the fjords. It's an ex-phone.

istperson said:
That phone is not pining for the fjords. It's an ex-phone.
Click to expand...
Click to collapse
What do you mean by "pining for the fjords"?
I wondered, is it possible to use wugfresh to push system files to the device (while removing old ones) making it seem to have a clean system partition, then try the ota again via adb sideload. Even if i took the system files from my functioning nexus. The faulty one is on lmy47z at the moment.

call-of-monst3r said:
What do you mean by "pining for the fjords"?
I wondered, is it possible to use wugfresh to push system files to the device (while removing old ones) making it seem to have a clean system partition, then try the ota again via adb sideload. Even if i took the system files from my functioning nexus. The faulty one is on lmy47z at the moment.
Click to expand...
Click to collapse
http://www.google.com/search?q=pining for the fjords
And, I'm sorry, but no, you can't do more with toolkits than with adb and fastboot. Toolkits are just front-ends for those two tools.
You have already tried everything possible, and since the bootloader is locked and you can't boot into Android to enable unlocking, all you have is just spare parts. I'm sorry.

istperson said:
And, I'm sorry, but no, you can't do more with toolkits than with adb and fastboot. Toolkits are just front-ends for those two tools.
You have already tried everything possible, and since the bootloader is locked and you can't boot into Android to enable unlocking, all you have is just spare parts. I'm sorry.
Click to expand...
Click to collapse
Thanks for the help, I've never heard of that phrase before and I thought i had heard them all given what my mums like
When the phone is in recovery, when the update via adb is selected, the phone is detected as an adb sideload device when "adb devices" is entered. Can I push/pull system files when it's detected as sideload? Because I noticed wugfresh supports pushing/pulling of files between the device and pc, but I wasn't sure if it could do system files when the device is detected as sideload
Thanks for the help, i would really like to make it work, and given its not exactly a device I rely on, I'm happy to spend more time working on it and trying more unusual/new ideas
Cameron

call-of-monst3r said:
Thanks for the help, I've never heard of that phrase before and I thought i had heard them all given what my mums like
When the phone is in recovery, when the update via adb is selected, the phone is detected as an adb sideload device when "adb devices" is entered. Can I push/pull system files when it's detected as sideload? Because I noticed wugfresh supports pushing/pulling of files between the device and pc, but I wasn't sure if it could do system files when the device is detected as sideload
Thanks for the help, i would really like to make it work, and given its not exactly a device I rely on, I'm happy to spend more time working on it and trying more unusual/new ideas
Cameron
Click to expand...
Click to collapse
Here it is how sideload works. But as I understood it's only for updates on working phones:
http://www.androidcentral.com/how-manually-upgrade-your-nexus#slide5

Trying to root using NRT and getting errors

I am getting an error message of 'ADB recovery device not found'. Gone through all of the suggested steps and still getting the same error. Any help please?

'ADB recovery device not found'or just 'device not found'?
It sounds like a driver problem. What are "all the suggested steps"? Do you mean the walkthrough of setting up PC drivers?
But why use NRT for something as simple as root? Once you have your drivers properly installed, you can use ADB to reboot into TWRP recovery (either permanently or temporarily) and in TWRP install SuperSU v2.68. Simple.

dahawthorne said:
'ADB recovery device not found'or just 'device not found'?
It sounds like a driver problem. What are "all the suggested steps"? Do you mean the walkthrough of setting up PC drivers?
But why use NRT for something as simple as root? Once you have your drivers properly installed, you can use ADB to reboot into TWRP recovery (either permanently or temporarily) and in TWRP install SuperSU v2.68. Simple.
Click to expand...
Click to collapse
Been through the process of installing the drivers, followed it word for word twice. ADB recovery device not found is the message that comes up.
How do I use ADB? Do I have to install/download twrp and SuperSU?
Sent from my Nexus 6 using XDA Free mobile app

You can do nothing in NRT or manually until you resolve your driver problems. Have you enabled OEM unlock in Settings? Enable Developer options & USB debugging? Is your device unlocked? If it is, when you reboot the first screen will show a small unlocked padlock.
There's too little information to give any proper answers. Tell us what you've done since you took the device out of the box.

dahawthorne said:
You can do nothing in NRT or manually until you resolve your driver problems. Have you enabled OEM unlock in Settings? Enable Developer options & USB debugging? Is your device unlocked? If it is, when you reboot the first screen will show a small unlocked padlock.
There's too little information to give any proper answers. Tell us what you've done since you took the device out of the box.
Click to expand...
Click to collapse
I was previously rooted until last week. Unrooted to try and make my bank app work. OEM unlocked and USB debugging checked. Last time I rooted I used this process and worked fine.
Sent from my Nexus 6 using XDA Free mobile app

Same laptop/computer? No OS changes that might have disabled drivers?
Please just reply inline without repeating this answer - I've just written it, so I know what it says and I don't need to read it again. Same advice for all users unless there's a long and convoluted thread where the backward reference isn't clear - in simple straightforward threads like this one there's no value in copying the entire message that you're replying to...

It's a company laptop that had a policy installed recently that prevents exe files. That's all, only other difference is the phone is now on the February security update.
Sent from my Nexus 6 using XDA Free mobile app

If I installed NRT on my company laptop I'd be fired immediately and walked off the premises. I don't know how we can help you - if your laptop is locked down with company security policies then that's likely to be the reason.
So my only suggestion is - use another laptop.

They are cool with it.
I will ask for the recent policy to be removed and see if that fixes it. Appreciate your time, thanks.
Sent from my Nexus 6 using XDA Free mobile app

Nexus 6 not updating

I just got a n6 today, and its running on 5.1.1. The marshmallow update came a long time ago so i thought it would update, but it showed that phone is up to date. Why is this so and how do i update?

entermetallica said:
I just got a n6 today, and its running on 5.1.1. The marshmallow update came a long time ago so i thought it would update, but it showed that phone is up to date. Why is this so and how do i update?
Click to expand...
Click to collapse
First of all congrats on the new phone. I'm on AT&T and updates came too slow for me. I chose to flash a system image to get upgraded to marshmallow and now we can download ota's directly from Google to keep up to date. Cutting out the need to wait for our updates to be made available from the carriers. Edit: to be clear you have to flash the ota's as well.
I believe others have removed sim card to try to get ota via wifi. I think. Anyway good luck.
Sent from my SM-T700 using Tapatalk

If you just got it today, good! Don't waste your time setting it up. Remove your SIM card and download the newest factory image "MOB30I" from here for the Nexus 6 (Shamu)
Just follow the instructions and you will be on the latest software. Then you should get OTA's normally from here on out. If you do it the Google recommended way it will wipe the phone so that's why I said don't set it up. If you already set it up it's going to be harder but you can manually flash the radio, bootloader, boot (kernel), and system with retaining your data but it's more hassle than it's worth.

Dopamin3 said:
If you just got it today, good! Don't waste your time setting it up. Remove your SIM card and download the newest factory image "MOB30I" from here for the Nexus 6 (Shamu)
Just follow the instructions and you will be on the latest software. Then you should get OTA's normally from here on out. If you do it the Google recommended way it will wipe the phone so that's why I said don't set it up. If you already set it up it's going to be harder but you can manually flash the radio, bootloader, boot (kernel), and system with retaining your data but it's more hassle than it's worth.
Click to expand...
Click to collapse
Thank you for your help, Im trying to flash it as it says on the website, but my device is not recognized after I type adb reboot bootloader. The phone shows up in adb devices but not in fastboot.

entermetallica said:
Thank you for your help, Im trying to flash it as it says on the website, but my device is not recognized after I type adb reboot bootloader. The phone shows up in adb devices but not in fastboot.
Click to expand...
Click to collapse
Assuming you're using Windows, if you look in device manager do you see anything either with a red x or yellow exclamation mark? If so you are missing the driver. This thread has the driver zip and briefly explains how to install it via device manager. Once you get the driver installed it should work fine.
And I can't remember if you need to or not to flash the stock images, but you might need to unlock your bootloader. Tap the build number a bunch of times and you will have access to developer options, and there you might need to check "Allow OEM unlocking" or something like that. Again I'm not 100% sure if that's necessary or not. I've ran my bootloader unlocked since day 1 and haven't looked back.

The bootloader does need to be unlocked to flash anything at all, except for a Google-signed OTA image.

Thanks for the help, ive done it. I had to boot into fastboot, and then install drivers from device manager
Sent from my Nexus 6 using XDA-Developers mobile app