Database Users

how to root a uk version g1 build crc37 ???

hi ive been looking round how to root my g1 and had no conformation if the UK version g1 are different to root than the US.
can some give me some clarification on how to root them.
thanks in advance

i am a us g1 users so i might be incorrect but i believe that you need to use rc9 or a gold card. if it is rc9, the rest of the method is the same just a different .nbh

porkky said:
hi ive been looking round how to root my g1
Click to expand...
Click to collapse
No, you didn't.
http://forum.xda-developers.com/showthread.php?t=442480

Afirejar said:
No, you didn't.
http://forum.xda-developers.com/showthread.php?t=442480
Click to expand...
Click to collapse
Hey I’m having some trouble getting to grips with rooting too; there is quite a lot of information (some of it contradictory or at least inconsistent) for someone new like myself to take in. I consider myself pretty tech savvy but my G1 is uninsured and I’m frankly terrified of bricking it as I’ve got a year left on my contract to pay.
Anyway my point being...the guide your pointing to is specifically tailored to US models as are most guides on the net it’s very hard to find anything definitive about rooting the UK models with regard to SPL and Radio, etc. Also, given that this stuff moves soo quickly (which is an amazing testament to the hard work that all the devs and everyone else involved puts in, thank you!) it’s hard to catch up on everything and understand what exactly to do.

One click root works fine on crc37 uk phones ive rooted a couple now just follow the usual instructions, there's little danger of anything getting bricked if you arent touching radio which you dont need to do to load CM using the one click root app
http://www.ryebrye.com/blog/2009/08/16/android-rooting-in-1-click-in-progress/

seaweeduk said:
One click root works fine on crc37 uk phones ive rooted a couple now just follow the usual instructions, there's little danger of anything getting bricked if you arent touching radio which you dont need to do to load CM using the one click root app
http://www.ryebrye.com/blog/2009/08/16/android-rooting-in-1-click-in-progress/
Click to expand...
Click to collapse
I'm a little confused with all this too.
I've been to that blog and that seems simple enough.
It should work on this right? -
firmware - 1.5
kernel - 2.6.27 [email protected] #1
Build Number - CRC 1
Now, this means by phone is rooted, (Basically giving me sys admin rather than root user?)
Which in turn means I can install custom ROM images? Is there anything else this allows me to do?
And is all this permement? Or will it go back to the original ROM on the hardware when I hard reboot?
Sorry for all the questions, I got my phone today .

That's an original and most up to date UK version, so no you're not rooted. Easiest way is the one-click root, just install, put rom on SD card, run prog, reboot, flash (Read full instructions though).
Having root enables you to have full access, so you can do whatever you like from terminal and applications which require special permissions to run can, some cool stuff can only be done with root.

AdamPI said:
That's an original and most up to date UK version, so no you're not rooted. Easiest way is the one-click root, just install, put rom on SD card, run prog, reboot, flash (Read full instructions though).
Having root enables you to have full access, so you can do whatever you like from terminal and applications which require special permissions to run can, some cool stuff can only be done with root.
Click to expand...
Click to collapse
Thanks for the quick reply and I'm not trying to Hijack the thread, (But the OP will probably want to know this too), once I've rooted and installed the new ROM from the boot menu loader thing, how do I go about formatting my SD card to ex2?
I'm looking at this guide - http://forum.xda-developers.com/showthread.php?t=535232
But in this thread - http://forum.xda-developers.com/showthread.php?t=537204 CM himself says not to install APPS2SD. Can you do the format from inside that ROM or does it do it automatically for you?

Yeah cyanogen roms already contain their own method of app2sd, so trying to use another method on top just screws things up.
All you need to do is partition the card, then when you reboot it will see the partition, move your current stuff over and be good to go.
Follow this guide for partitioning from recovery console: http://forum.xda-developers.com/showthread.php?t=534714

I downgraded from the Official AT&T 2.2 update back to 2.1

I used the info on this page: *android.modaco.com/content/htc-desire-desire-modaco-com/310873/possible-hboot-downgrade/* it didn't downgrade the hboot, but that might be something to work on.
CHANGE STEP 3.4. "change it to 1.15.405.1" don't do that, change the "2.20.502.1" in the misc.img from your aria to 1.25.502.2
Oh and you'll need either a Temp root, or a Shell root for adb

I have done this and can confirm that this works
Thanks mate!

I just noticed the Aria got 2.2 finally, albiet through this silly sync method.... It's my wifes phone, I'm sure she's not going to be happy to have to hard reset it.. wth.
Anyway, so why are you guys going back to 2.1? I am surprised not to see more discussion on 2.2 in this forum, but I don't frequent it much since I don't own the Aria myself.

khaytsus said:
I just noticed the Aria got 2.2 finally, albiet through this silly sync method.... It's my wifes phone, I'm sure she's not going to be happy to have to hard reset it.. wth.
Anyway, so why are you guys going back to 2.1? I am surprised not to see more discussion on 2.2 in this forum, but I don't frequent it much since I don't own the Aria myself.
Click to expand...
Click to collapse
I went back to 2.1 because the 2.2.2 version that AT&T released was extremely slow, and my touchscreen would become unresponsive.

andrewishcool95 said:
I used the info on this page: *android.modaco.com/content/htc-desire-desire-modaco-com/310873/possible-hboot-downgrade/* it didn't downgrade the hboot, but that might be something to work on.
CHANGE STEP 3.4. "change it to 1.15.405.1" don't do that, change the "2.20.502.1" in the misc.img from your aria to 1.25.502.2
Oh and you'll need either a Temp root, or a Shell root for adb
Click to expand...
Click to collapse
How do you get a temp root or shell root with the new HBoot still in-place? If temp root is possible, then can't you install clockworkmod and get permaroot?

Gene Poole said:
How do you get a temp root or shell root with the new HBoot still in-place? If temp root is possible, then can't you install clockworkmod and get permaroot?
Click to expand...
Click to collapse
I got a shell root from super one click root (forum.xda-developers.com/showthread.php?t=803682)
after I downgraded to 2.1 I got z4root to get a temp root.

andrewishcool95 said:
I got a shell root from super one click root (forum.xda-developers.com/showthread.php?t=803682)
after I downgraded to 2.1 I got z4root to get a temp root.
Click to expand...
Click to collapse
I'm also very curious about this.

Sounds like the first steps to rooting and downgrading. I'm curious to see if any developers catch this
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

I've been reading up on this and the skinny is that the HBOOT image controls the S-ON and S-OFF flags of the NAND RAM in the device. Even with a temp root shell, you can't write to a partition with its S-ON flag set. This normally includes all the partitions on the phone except the data partition, so trying to root the device requires some sort of interaction with the HBOOT image to turn off the S-ON flag for the recovery and system partitions to properly root a phone.
In short, if and until someone hacks hboot_liberty_7227_1.02.0000_101104, your phone is unrootable.

Gene Poole said:
I've been reading up on this and the skinny is that the HBOOT image controls the S-ON and S-OFF flags of the NAND RAM in the device. Even with a temp root shell, you can't write to a partition with its S-ON flag set. This normally includes all the partitions on the phone except the data partition, so trying to root the device requires some sort of interaction with the HBOOT image to turn off the S-ON flag for the recovery and system partitions to properly root a phone.
In short, if and until someone hacks hboot_liberty_7227_1.02.0000_101104, your phone is unrootable.
Click to expand...
Click to collapse
Help me out, I may be thinking in the wrong direction, but I've been dealing with my nook which is why I thought of this.
Is there not a way to write an hboot to an sd-card or connect via usb at start to make the aria think that the sd-card or the usb connection is the corrected hboot, thus being able to modify?

FroztIkon said:
Help me out, I may be thinking in the wrong direction, but I've been dealing with my nook which is why I thought of this.
Is there not a way to write an hboot to an sd-card or connect via usb at start to make the aria think that the sd-card or the usb connection is the corrected hboot, thus being able to modify?
Click to expand...
Click to collapse
There may be. When I first got my Aria, the rooting procedure involved an HTC signed update that you fooled the hboot into partially loading, then swapped the sdcard with the root package. It involved some complex timing issues where you had to run adb in a loop and plug/unplug the usb cable at appropriate times.
I've been searching the net for that procedure and I can't seem to find the right search terms, or I'm just not looking in the right places or something, but I know that's how I did my Aria before there was an unrevoked plug-n-root.

I have the procedure u are looking for i think...let me know if this is what u were after because i have an archive of saved documents I have copied from forums in the past...GOOD LUCK!
well apparently i haven't posted enough to put the links up in the post

PM me if you want the process...

xerotix said:
PM me if you want the process...
Click to expand...
Click to collapse
May I have a copy of said process? Currently the only way is to buy a very expensive hardware called XClip. I have managed to get the updated 2.2.2 Stock ROM rooted but not deodex or EXT3 FOR ap2sd trying to play with some files from another source to get hboot s off.

econcep said:
May I have a copy of said process? Currently the only way is to buy a very expensive hardware called XClip. I have managed to get the updated 2.2.2 Stock ROM rooted but not deodex or EXT3 FOR ap2sd trying to play with some files from another source to get hboot s off.
Click to expand...
Click to collapse
That process does not work with the new HBOOT. That's why unrevoked doesn't work. Having root access does not unlock NAND.
Currently, the only way known is via hardware tools.

It works. I managed a work around for 2.2.2 update
Hey everyone I am in the second phase of testing my work around with the new HTC Aria update from ATT. I managed to load the update and keep my phone rooted. I am now in the setup mode with no bootloop.
Running into a couple of issues with the new radio but I believe I know how to fix that as well. Keep you all posted and once all bugs worked out I will post my findings and HOPEFULLY MY ROOTED ROM.ZIP with instructions.
IF AT FIRST YOU DON'T SUCCEED.....TRY TRY TRY and TRY I did and I am 99% there.

econcep said:
Hey everyone I am in the second phase of testing my work around with the new HTC Aria update from ATT. I managed to load the update and keep my phone rooted. I am now in the setup mode with no bootloop.
Running into a couple of issues with the new radio but I believe I know how to fix that as well. Keep you all posted and once all bugs worked out I will post my findings and HOPEFULLY MY ROOTED ROM.ZIP with instructions.
IF AT FIRST YOU DON'T SUCCEED.....TRY TRY TRY and TRY I did and I am 99% there.
Click to expand...
Click to collapse
This might be the wrong thread. Did you manage to get around the HBOOT issue with the 2.2 update? If not, then you've just done the same thing I did the day after this release was out:
http://forum.xda-developers.com/showthread.php?t=970272

Gene Poole said:
This might be the wrong thread. Did you manage to get around the HBOOT issue with the 2.2 update? If not, then you've just done the same thing I did the day after this release was out:
http://forum.xda-developers.com/showthread.php?t=970272
Click to expand...
Click to collapse
You are right this might be the wrong thread. But I managed a work around with the new update 2.2.2 and the HBOOT 1.0X. As soon as I can confirm without a doubt that it works and will be able to repeat the process successfully with my husband's ARIA (unfortunately we love hacking things and tend to buy multiple devices) I will be more than happy to share the results.
Again, my apologies if it's the wrong thread.

econcep said:
You are right this might be the wrong thread. But I managed a work around with the new update 2.2.2 and the HBOOT 1.0X. As soon as I can confirm without a doubt that it works and will be able to repeat the process successfully with my husband's ARIA (unfortunately we love hacking things and tend to buy multiple devices) I will be more than happy to share the results.
Again, my apologies if it's the wrong thread.
Click to expand...
Click to collapse
Perhaps I misread (or we're talking past each other). You do have, in fact, HBOOT 1.02.0000 on your Aria, and managed to write to the system partition?

Yes & No. I'm stuck on couple of things. First the will temporary give me root access but then it locks up saying I don't have busybox. I'm rooted but no s-off. I also noticed when I reboot into recovery I go into CWM 2.5.0.1 but other times it boots into CWM 2.5.0.7. When that happens I loose my unknown source in settings>application. Again, if this is the wrong thread, I really am sorry.
I googled alpharev and some others who have worked on rooting. Found some cached pages from Jan when they were testing to root/s-off the Aria. Basing my work on that and couple of other devices that are similar to the Aria.

[q] delete this?

Ok people, this is not my first post, although it says it is. I used to be on here and a few other sites as ldawg214. I've done some things but alas I quit for awhile and can't remember my old password (so if any mods can help me there that would be cool.) But the reason for this post is that I'm trying to get a custom rom on my mytouch 4g with 2.3.4 Gingerbread. I know I need to downgrade to froyo using adb but the files fre3vo and misc_version_01 are just blank data files. I don't know if they are supposed to be like that but everything I've searched for on this is at least 3 years old. I've gone ahead and tried adb but it always just tells me the the file or directory doesn't exist. Does anyone know if this method still works?
http://forum.xda-developers.com/showthread.php?t=1178912
Starting to feel like this is impossible and I know what I'm doing lol.

luda214 said:
Ok people, this is not my first post, although it says it is. I used to be on here and a few other sites as ldawg214. I've done some things but alas I quit for awhile and can't remember my old password (so if any mods can help me there that would be cool.) But the reason for this post is that I'm trying to get a custom rom on my mytouch 4g with 2.3.4 Gingerbread. I know I need to downgrade to froyo using adb but the files fre3vo and misc_version_01 are just blank data files. I don't know if they are supposed to be like that but everything I've searched for on this is at least 3 years old. I've gone ahead and tried adb but it always just tells me the the file or directory doesn't exist. Does anyone know if this method still works?
http://forum.xda-developers.com/showthread.php?t=1178912
Starting to feel like this is impossible and I know what I'm doing lol.
Click to expand...
Click to collapse
Haven't rooted a glacier in a while. But I'll try to help you. Here's a link to the rooting process. I've always used gfree. If you need any files let me know and I'll upload them.
http://wiki.cyanogenmod.org/w/Install_CM_for_glacier#Rooting_the_HTC_Glacier

Thank you so much but it turns out I was just missing a few steps (as usual) lol. So I am now perm rooted with s=off. I think that's all I have to do and now I can flash a custom rom. That's what I'm on my way to do now. Thank you again.

luda214 said:
Thank you so much but it turns out I was just missing a few steps (as usual) lol. So I am now perm rooted with s=off. I think that's all I have to do and now I can flash a custom rom. That's what I'm on my way to do now. Thank you again.
Click to expand...
Click to collapse
Okay, I think this can be deleted. I've got s off and installed sabsa_prime and so far it's working great. If anyone sees this though, after all that root checker basic says that the phone doesn't have root access.........WHAT??? How is that possible?

Download Unsuccessful MSG - KK to N910VVRU1BOAF

I'm trying to root, then unlock my Retail phone. I heard it can be done on BOAF 5.0.1. I downgraded my phone to KK ANJ5 (details on what steps I took, here)
I actually did a Factory Data Wipe twice before beginning, although the instructions said I only needed to do it once (doing it twice shouldn't hurt).
When I tap the System Updates button, it appears to start downloading, then after a few minutes, I'll get an error message saying "Download Unsuccessful". I've done this several times. Why is this happening now? I've cleared everything. Could Verizon have pulled the update? Can I install the two files manually? If so, please point me to the right direction. Thanks.

Flash N910VVRU2BOG5_StockRestore.tar.md5 using Odin. It will upgrade you and you will be able to convert your phone to developer mode using the steps in the thread.

Sizzlechest said:
Flash N910VVRU2BOG5_StockRestore.tar.md5 using Odin. It will upgrade you and you will be able to convert your phone to developer mode using the steps in the thread.
Click to expand...
Click to collapse
I took the latest safe upgrade, I think it's BP1 or something like that., to 5.1.1. THAT worked.

So basically we have to be on 5.1.1 ??
Sent from my SM-N910V using XDA Premium HD app

rrjskj said:
So basically we have to be on 5.1.1 ??
Sent from my SM-N910V using XDA Premium HD app
Click to expand...
Click to collapse
I'm just saying that's what for sure worked for me. KK didn't work at all. I don't know if you "have to" be on it or not.

JOSHSKORN said:
I'm just saying that's what for sure worked for me. KK didn't work at all. I don't know if you "have to" be on it or not.
Click to expand...
Click to collapse
I might give it a whirl if fix doesn't come soon. In the meantime could u point me in the right direction for the safe upgrade files and what Odin version ?? Thanks in advance.
Sent from my SM-N910V using XDA Premium HD app

http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
read everything!

Rom-Addict said:
http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
read everything!
Click to expand...
Click to collapse
Already did it I appreciated.
Sent from my SM-N910V using XDA Premium HD app

I've had it work on boaf, bpa, bog5. kk wouldn't work for me. using king root 4.0,.all unlocks (n4.n4.bin. n4.fix) worked for me. bpa (5.1.1)required the emotion kernel to boot. also returned my original Cid to use kies to restore all apps & data, then odined back again, unlocked, rooted ect. be patient

Rom-Addict said:
http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
read everything!
Click to expand...
Click to collapse
What confused me and a few other people in that thread is that you NEED to flash that kernel before the SuperSU linked there if you want to root 5.1.1 firmware. I thought it was just if you had taken the OTA 5.1.1.

Sizzlechest said:
What confused me and a few other people in that thread is that you NEED to flash that kernel before the SuperSU linked there if you want to root 5.1.1 firmware. I thought it was just if you had taken the OTA 5.1.1.
Click to expand...
Click to collapse
This is what I did (I think). Kinda hard to remember everything. For more information, read through the HOWTO thread. I think I started posting at about page 9.
went ahead and did the safe upgrade via Odin
Swapped out my MicroSD card for a different one I had laying around
Unlocked my phone
Powered Down (If I could, or remove the battery)
Removed the MicroSD card (otherwise it would boot loop)
Connected to My Computer
Boot to Download Mode (DOWN ARROW+HOME+POWER BUTTON)
Flashed TWRP using Odin
Reinserted the original MicroSD Card (Different SD card than what was used during the unlock process, the same one I was using prior to unlocking)
Booted into TWRP (UP ARROW+HOME+POWER BUTTON)
It prompted me to install SuperUser, so I did, it caused a bootloop, so I pulled my battery.
Removed MicroSD Card, plugged it into my computer and put SuperSU.zip and a kernel (See this post) zip file on it, re-inserted the MicroSD into my phone
Booted to TWRP (UP ARROW+HOME+POWER BUTTON)
Flashed the two files I'd just put on my MicroSD (Not sure if a reboot is required or if they could be done at the same time, I rebooted each time)
I did not clear cache/dalvik. Not sure if that was necessary.
This is all what got me to where I'm at, now.

JOSHSKORN said:
This is what I did (I think). Kinda hard to remember everything. For more information, read through the HOWTO thread. I think I started posting at about page 9.
...
This is all what got me to where I'm at, now.
Click to expand...
Click to collapse
For 5.0.1, you don't need to flash a new kernel, so that's why it works. If you want to upgrade to N910VVRU2BPA1:
Download N910VVRU2BPA1_StockRestore.tar.md5.7z and uncompress with 7-zip.
Flash with Odin.
Reboot phone back into Download Mode and flash TWRP with Odin.
Copy MultiSystem-Kernel_LP-5.1.1.zip and BETA-SuperSU-v2.67-20160203160253-TruncatedBoot-Fix.zip to the phone's internal memory. (Include xposed-v75-sdk21-arm-arter97-snapdragon.zip if you want XPosed.)
Reboot to recovery and flash all three in the above order.
Wipe cache and Davlik cache. Reboot to system.

Sizzlechest said:
Flash N910VVRU2BOG5_StockRestore.tar.md5 using Odin. It will upgrade you and you will be able to convert your phone to developer mode using the steps in the thread.
Click to expand...
Click to collapse
I'm on 4.4.4 is this what I need to do a lot of other people are having the problem of getting the commands to work on 4.4.4 and are asking the question of do we need to upgrade some aren't getting answered and some are being told different things I'm sorry for asking but I need to know so I can unlock my bootloader thank you

Jimmy8 said:
I'm on 4.4.4 is this what I need to do a lot of other people are having the problem of getting the commands to work on 4.4.4 and are asking the question of do we need to upgrade some aren't getting answered and some are being told different things I'm sorry for asking but I need to know so I can unlock my bootloader thank you
Click to expand...
Click to collapse
There seems to be a bug in the detection routine on the program that changes the bootloader to developer when run on 4.4.4. If you want to follow the original directions, upgrade (first) to a 5.0.1 firmware since that is known to work with the unlocker and no new kernel needs to be flashed. If you get it to work for 5.0.1, then you can always upgrade to 5.1.1 or flash another rom.
If you want to try to go straight to 5.1.1 by flashing through Odin, you can try it. I'm almost positive you could downgrade to 5.0.1 if that doesn't work. (If you take the software upgrade through Verizon, you will have problems downgrading AFAIK.)

Sizzlechest said:
There seems to be a bug in the detection routine on the program that changes the bootloader to developer when run on 4.4.4. If you want to follow the original directions, upgrade (first) to a 5.0.1 firmware since that is known to work with the unlocker and no new kernel needs to be flashed. If you get it to work for 5.0.1, then you can always upgrade to 5.1.1 or flash another rom.
If you want to try to go straight to 5.1.1 by flashing through Odin, you can try it. I'm almost positive you could downgrade to 5.0.1 if that doesn't work. (If you take the software upgrade through Verizon, you will have problems downgrading AFAIK.)
Click to expand...
Click to collapse
Thanks I just upgraded through Verizon to 5.0.1 and I'll give that a try and see if it works if not I'll safe upgrade to 5.1.1 thanks

Jimmy8 said:
I'm on 4.4.4 is this what I need to do a lot of other people are having the problem of getting the commands to work on 4.4.4 and are asking the question of do we need to upgrade some aren't getting answered and some are being told different things I'm sorry for asking but I need to know so I can unlock my bootloader thank you
Click to expand...
Click to collapse
If that doesn't work, I recommend you rollback to 4.4.4 (you should be able to if you're on BOAF), then take the safe upgrade to BP1. Once you do that, you should be good to go. That is, I wasn't able to convert to developer mode on KK, but after taking the safe upgrade, I was. Maybe it had to do with the BOAF bootloader, and if that's the case, "maybe' you're ok doing it as is. Good luck. I'm sure you'll be back if it doesn't work, but if it DOES work, can you report back? In fact, I also have a thread in Q&A titled Root Survey. Please post there as well ONLY if you were able to successfully convert. I wanted to compile a list of users that were able to convert, where they were before they started, what worked, what didn't, and so far, all what I'm seeing is, is that starting from KK doesn't work, although we were told all along to keep KK. I also heard one user said that he had taken all OTAs to 5..1.1., still made the conversion process work, BUT, his phone was a developer phone to begin with but he accidentally locked it with a Retail ROM. I'm kind of a noob, myself, but from what I do know, I don't recommend taking any OTAs anyway past BOAF, otherwise the conversion "might not" happen, but there are a lot of people who have taken all OTAs so we'll see what happens with them.

JOSHSKORN said:
If that doesn't work, I recommend you rollback to 4.4.4 (you should be able to if you're on BOAF), then take the safe upgrade to BP1. Once you do that, you should be good to go. That is, I wasn't able to convert to developer mode on KK, but after taking the safe upgrade, I was. Maybe it had to do with the BOAF bootloader, and if that's the case, "maybe' you're ok doing it as is. Good luck. I'm sure you'll be back if it doesn't work, but if it DOES work, can you report back? In fact, I also have a thread in Q&A titled Root Survey. Please post there as well ONLY if you were able to successfully convert. I wanted to compile a list of users that were able to convert, where they were before they started, what worked, what didn't, and so far, all what I'm seeing is, is that starting from KK doesn't work, although we were told all along to keep KK. I also heard one user said that he had taken all OTAs to 5..1.1., still made the conversion process work, BUT, his phone was a developer phone to begin with but he accidentally locked it with a Retail ROM. I'm kind of a noob, myself, but from what I do know, I don't recommend taking any OTAs anyway past BOAF, otherwise the conversion "might not" happen, but there are a lot of people who have taken all OTAs so we'll see what happens with them.
Click to expand...
Click to collapse
I can't even get king root to root it constantly reboots my phone during rooting process I've tried different versions and it doesn't matter do you have any suggestions or point me in the direction to roll back to 4.4.4 I've been out of the game for a while so I've forgotten a lot of stuff on how to do this thank for all your help so far

Jimmy8 said:
I can't even get king root to root it constantly reboots my phone during rooting process I've tried different versions and it doesn't matter do you have any suggestions or point me in the direction to roll back to 4.4.4 I've been out of the game for a while so I've forgotten a lot of stuff on how to do this thank for all your help so far
Click to expand...
Click to collapse
Believe me, I'm with you right there, as well, been out of the game for so long. Thanks Verizon Retail locking. Anyway....
Where are you right now? Your Android version/Build Number.

joshskorn said:
believe me, i'm with you right there, as well, been out of the game for so long. Thanks verizon retail locking. Anyway....
Where are you right now? Your android version/build number.
Click to expand...
Click to collapse
5.0.1 / n910vvru1boaf

Should I root my 6P?

Hi!
A month ago I bought a second-hand Nexus 6P and I ordered a silver casing because the black color that brought didn't like to me.
When I opened it and change the housing the guarantee was logically lost, and now I wondered if it was worth to root it because I don't lose anything.
I don't want to change the ROM. I'd like flashing MODs to improve sound quality or increase the audio output voltage (I don't know if that's possible).
The problem is that I don't know how to do it with my laptop, which has Windows 10. I have always done on Windows 7 and I know the drivers on Windows 10 are a mess. Also, I don't know how to do things like flashing firmware or RRU through ADB and fastboot so, should I root it?
I would appreciate your help.
Thank you!

MortalPizza said:
Hi!
A month ago I bought a second-hand Nexus 6P and I ordered a silver casing because the black color that brought didn't like to me.
When I opened it and change the housing the guarantee was logically lost, and now I wondered if it was worth to root it because I don't lose anything.
I don't want to change the ROM. I'd like flashing MODs to improve sound quality or increase the audio output voltage (I don't know if that's possible).
The problem is that I don't know how to do it with my laptop, which has Windows 10. I have always done on Windows 7 and I know the drivers on Windows 10 are a mess. Also, I don't know how to do things like flashing firmware or RRU through ADB and fastboot so, should I root it?
I would appreciate your help.
Thank you!
Click to expand...
Click to collapse
You don't lose your warranty when rooting Nexus devices anyway, so even if you hadn't opened your device up it wouldn't have had a problem. There's no mess with drivers on the Windows 10, really. Extract ADB and Fastboot from the Android SDK and follow one of the many guides available in the general section. It's easy enough to unlock and root the device and/or change the firmware too if you had to. Just read the available guides.

Quasar said:
You don't lose your warranty when rooting Nexus devices anyway, so even if you hadn't opened your device up it wouldn't have had a problem. There's no mess with drivers on the Windows 10, really. Extract ADB and Fastboot from the Android SDK and follow one of the many guides available in the general section. It's easy enough to unlock and root the device and/or change the firmware too if you had to. Just read the available guides.
Click to expand...
Click to collapse
Exactly! It's very simple. I did have issues with the drivers on my Windows 10 computer but it was a matter of uninstalling and reinstalling them.
Sent from my Nexus 6P using Tapatalk

MortalPizza said:
Hi!
A month ago I bought a second-hand Nexus 6P and I ordered a silver casing because the black color that brought didn't like to me.
When I opened it and change the housing the guarantee was logically lost, and now I wondered if it was worth to root it because I don't lose anything.
I don't want to change the ROM. I'd like flashing MODs to improve sound quality or increase the audio output voltage (I don't know if that's possible).
The problem is that I don't know how to do it with my laptop, which has Windows 10. I have always done on Windows 7 and I know the drivers on Windows 10 are a mess. Also, I don't know how to do things like flashing firmware or RRU through ADB and fastboot so, should I root it?
I would appreciate your help.
Thank you!
Click to expand...
Click to collapse
You have nothing to lose, so why not?! Take a look at my guide, it should have everything you need:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

Thank you for your replies @Quasar @GallardosEggrollShop and @heisenberg! Now I have only two questions:
1. System updates by Google support other recoveries apart from Android original recovery (I'd like to install TWRP)?
2. When I unlock the bootloader I'll lose all my data (factory reset)?
Thank you!

MortalPizza said:
Thank you for your replies @Quasar @GallardosEggrollShop and @heisenberg! Now I have only two questions:
1. System updates by Google support other recoveries apart from Android original recovery (I'd like to install TWRP)?
2. When I unlock the bootloader I'll lose all my data (factory reset)?
Thank you!
Click to expand...
Click to collapse
1. No, other recoveries cannot flash OTA updates. You can't apply an OTA if you're rooted anyway, you need to flash the factory images to update.
2. Yes, unlocking the bootloader completely wipes the device so back up your personal data (photos etc) first.

Plus, in my opinion... It's a Nexus, why would you buy a Nexus if you weren't going to root it? At least to see whats out there and you can always go back to stock if you wish.

Nexus + XDA = Happy Flashing!

Heisenberg said:
1. No, other recoveries cannot flash OTA updates. You can't apply an OTA if you're rooted anyway, you need to flash the factory images to update.
2. Yes, unlocking the bootloader completely wipes the device so back up your personal data (photos etc) first.
Click to expand...
Click to collapse
Ok, im going to root my 6P finally, thank you all! Before the start, I want to solve a couple of questions and then I'll root it!
1. How can I update the Nexus stock ROM when I have TWRP? (Firmware, security updates or major updates like Nougat)
2. It's true that when my bootloader is unlocked, every time I boot the phone a message saying that my bootloader has been unlocked appears? In that case, Is it possible to remove permanently?
3. Is necessary make S-OFF like the HTC phones? I've never had a different phone of HTC, this is my first phone that's not an HTC.
Thanks!

MortalPizza said:
Ok, im going to root my 6P finally, thank you all! Before the start, I want to solve a couple of questions and then I'll root it!
1. How can I update the Nexus stock ROM when I have TWRP? (Firmware, security updates or major updates like Nougat)
2. It's true that when my bootloader is unlocked, every time I boot the phone a message saying that my bootloader has been unlocked appears? In that case, Is it possible to remove permanently?
3. Is necessary make S-OFF like the HTC phones? I've never had a different phone of HTC, this is my first phone that's not an HTC.
Thanks!
Click to expand...
Click to collapse
1. I already answered this question in the post you quoted, you flash the factory images. It's all in my guide that I linked you to earlier.
2. Yes you will have a warning message, and no you can't remove it.
3. S-off is specific to HTC so no need to worry about that.

I have only one question.
Is it completely necessary to flash regularly new hboot or firmware versions or I can use a non-stock rom with no worries about that?

MortalPizza said:
I have only one question.
Is it completely necessary to flash regularly new hboot or firmware versions or I can use a non-stock rom with no worries about that?
Click to expand...
Click to collapse
No such thing as hboot, that's only HTC. You need to make sure your bootloader and radio are up to date, and you need to make sure you flash the correct vendor image to suit the ROM.

Heisenberg said:
No such thing as hboot, that's only HTC. You need to make sure your bootloader and radio are up to date, and you need to make sure you flash the correct vendor image to suit the ROM.
Click to expand...
Click to collapse
Thank you VERY much! I am so lost since I don't have an HTC for first time and it's so good that the only two things I have to keep up to date were bootloader and radio. Only two questions, and sorry for being that heavy ?:
How can I get the latest bootloader and radio (a thread in XDA or something)?
How can I flash them? Will I lose my data every time I need to update them?
Thank you!

MortalPizza said:
Thank you VERY much! I am so lost since I don't have an HTC for first time and it's so good that the only two things I have to keep up to date were bootloader and radio. Only two questions, and sorry for being that heavy ?:
How can I get the latest bootloader and radio (a thread in XDA or something)?
How can I flash them? Will I lose my data every time I need to update them?
Thank you!
Click to expand...
Click to collapse
Have you read my guide that I've mentioned a few times? There are instructions for flashing the bootloader/radio/vendor there. Look in the section for flashing the factory images but only flash those specific files. And my index contains downloads for the factory images, which is where you can get the files you need.
http://forum.xda-developers.com/nexus-6p/general/index-huawei-nexus-6p-t3213583

Heisenberg said:
Have you read my guide that I've mentioned a few times? There are instructions for flashing the bootloader/radio/vendor there. Look in the section for flashing the factory images but only flash those specific files. And my index contains downloads for the factory images, which is where you can get the files you need.
http://forum.xda-developers.com/nexus-6p/general/index-huawei-nexus-6p-t3213583
Click to expand...
Click to collapse
Yes! I've read it and I have my PC ready to root my device but I'm so insecure and I need to have things clearly before I start to make things.
Thank you, again, for your help. And I hope this is my last question:
Now that I know that the things I need to keep up to date are bootloader, vendor and radio, and in your guide you say that flashing a factory image I'll lose all my data, will it happens to me when i update one of those things (only vendor/bootloader/radio)?
Thanks!

MortalPizza said:
Yes! I've read it and I have my PC ready to root my device but I'm so insecure and I need to have things clearly before I start to make things.
Thank you, again, for your help. And I hope this is my last question:
Now that I know that the things I need to keep up to date are bootloader, vendor and radio, and in your guide you say that flashing a factory image I'll lose all my data, will it happens to me when i update one of those things (only vendor/bootloader/radio)?
Thanks!
Click to expand...
Click to collapse
Flashing the factory images only wipes your data if you:
A) Flash the userdata.img
B) Format userdata
Neither of those are necessary for you so you're fine.

Rooting? Darn yes! :good:
The Nexus line is so sweet for easy rooting and also for returning to complete stock if so desired.
I have used Heisenberg's extensive thread many times...it's the best thread on XDA bar none! :highfive: