Database Develop

[Q] New to Rooting

I'm been searching the Nexus One Q&A section for an answer to my problems, but I couldn't find a solution. I'm running a stock version of 2.3.3 on my phone. It's never been rooted, and I have never rooted a device as well. I'm entirely new to this and have no idea what I'm doing. My device has no warranty but I'm still concerned about it. Again, I have no experience at all.
Also, I don't know if I would want to unlock the bootloader as I could lose everything. If there is a way to retain everything reliably (I don't know if those back-up applications are the most effective) that would be convenient.
So, can anyone help me root my virgin Nexus One?
Thanks for your time,
Tread Fox

Mybackup pro backs up apps and data. After you root you can use titanium backup. Also smsbackup and restore for your SMS :]

Alright, that's re-assuring. But what about actually rooting the phone?

Hmm I can't help with rooting because I have an Evo, just sharing some backup knowledge :/

You can use this threads wiki for the N1 and the stickies here:
http://www.nexusoneforum.net/forum/nexus-one-development-hacking/
You need to read several guides until you get a good idea of what you are doing and why.
Use the apps mentioned above to back up your phone info, once rooted you can do a complete and immediate phone backup of everything, like a full image pc backup.
If you do the one-click method, make sure it is for you OS, you will be limited in some things you can do, like fastboot commands and will be unrooted if you dl OTA's.
Read, Read, Read!!!
Before you flash a rom read the op page carefully and the last 20 pages for tips, info, issues etc.
Ken

This works for 2.3.3?
EDIT: So my only options are to unlock the bootloader or roll back? Which do you recommend?

You probably saw this in XDA wiki for N1:
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials#Root
I would unlock, more options as you get more into flashing and you can't be unrooted by Google OTA's.
This is good guide for the S, but you can glean steps and maybe better understanding for the process. At the bottom in related posts is a root guide. I like the steps, but things like the fastboot and superuser may not be for the N1. However you can find them online. Just an easy to understand guide.
http://jaxov.com/2011/02/install-android-2-3-3-gingerbread-on-nexus-one-manually/

TreadFox said:
This works for 2.3.3?
EDIT: So my only options are to unlock the bootloader or roll back? Which do you recommend?
Click to expand...
Click to collapse
Sorry man, just got your message (phone died on me, and I've been playing with my other toys anyway...)
Yes, your options are to unlock the bootloader or roll back.
Both options will lose all date, so you need to backup either way.
My preference is to unlock the bootloader, but I can understand why people may not want to. Unlocking the bootloader can effect any warranty that's remaining on the phone (the phone has a 1 year warranty, no matter who owns it).

Thanks for all your help guys. Does anyone have a specific guide for rolling back? I don't need or want a custom rom, just setcpu...

Read my signature, execute PASSIMG method with FRG33. if it doesn't work (and sometimes it doesn't) - you're out of luck.

TreadFox said:
Thanks for all your help guys. Does anyone have a specific guide for rolling back? I don't need or want a custom rom, just setcpu...
Click to expand...
Click to collapse
This is how to go back to FRG33: http://forum.xda-developers.com/showpost.php?p=11745519&postcount=21
But if I were you, I would just unlock your bootloader. Makes life easier.

I'll unlock the bootloader. I saw a guide on the nexusoneforums on how to do this. But it's about a year old. Is there anything that's changed?
I'm sorry I'm being indecisive, I'm trying to take suggestions from anybody!

TreadFox said:
I'll unlock the bootloader. I saw a guide on the nexusoneforums on how to do this. But it's about a year old. Is there anything that's changed?
I'm sorry I'm being indecisive, I'm trying to take suggestions from anybody!
Click to expand...
Click to collapse
No, nothing has changed. You need to have the Android SDK set up properly. Then just boot into the bootloader by holding down the trackball while pushing the power button. Then open a command prompt in the directory where the fastboot.exe file is (probably C:\Program Files\Android\android-sdk-windows\tools) then just type: fastboot oem unlock

Follow this to set up the, it's easier (just the first post):
http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html
Sent from my Nexus One using XDA Premium App

I don't know what I'm doing. This is confusing. When I hook up the phone to the pc it says its found new hardware. I'm running XP. What do I do? I think I'm going over my head with this. Also, how do I make sure mybackup will work? I don't want to lose my stuff!

TreadFox said:
I don't know what I'm doing. This is confusing. When I hook up the phone to the pc it says its found new hardware. I'm running XP. What do I do? I think I'm going over my head with this. Also, how do I make sure mybackup will work? I don't want to lose my stuff!
Click to expand...
Click to collapse
If you feel like you are in over your head, you probably are, and have not done enough reading. I just looked at danger-rat's post in the link he provided, and it seems quite straight forward, no? He even tells you how to install the drivers. "Step #3" under "To install the drivers" in the first post TELLS you that windows will detect new hardware and will ask you to install a driver. What seems to be the problem?

I did, and nothing happened. At all. I asked for it to download files from usb driver. Nothing happened at all. Is it something I'm doing wrong?
I have the SDK file on my desktop, I have all of the files inside that are needed. When the computer asks me to download the drivers, I re-direct to the usb driver folder located in the SDK which is located on my desktop. The computer claimed installation was successful, but nothing happened. When I try clicking the fastboot.exe in the tools file, it immediately forcecloses. Is it my pc? Is it the file? Is it the phone? I did read the material and so far nothing has helped.

TreadFox said:
I did, and nothing happened. At all. I asked for it to download files from usb driver. Nothing happened at all. Is it something I'm doing wrong?
I have the SDK file on my desktop, I have all of the files inside that are needed. When the computer asks me to download the drivers, I re-direct to the usb driver folder located in the SDK which is located on my desktop. The computer claimed installation was successful, but nothing happened. When I try clicking the fastboot.exe in the tools file, it immediately forcecloses. Is it my pc? Is it the file? Is it the phone? I did read the material and so far nothing has helped.
Click to expand...
Click to collapse
Well, after you have installed the driver that the computer asked you to install. That's just the driver needed to sync your file and stuff on your sd card. The other driver and adb setup is needed to actually access your phone.

So I asked for it to install the wrong files? What files do I install? Because from that guide it said point to usb driver. I'm only following the guide like you all asked, and nothing happened.

You don't launch fastboot by clicking on it windows.
Sent from my Nexus One using XDA App

[Q] How would you root? I'm on day FOUR of unsuccessful attempts

It started here:
http://forum.xda-developers.com/showthread.php?t=2530605
I followed this post.
http://forum.xda-developers.com/showthread.php?t=2509676
Got nowhere because of the puttytel window timeout problem.
Related to this post was this post:
http://forum.xda-developers.com/showthread.php?p=47749358#post47749358
I have an unlocked bootloader on Moto X from sprint. I just need the easiest way to root.
This looked confusing. http://forum.xda-developers.com/showthread.php?t=2536200. Gotta be another way.
Have considered restoring to stock and taking the dang thing back http://atsgadgets.com/how-to-restor...lite-att-t-mobile-sprint-verizon-us-cellular/. So frustrated.
I've offered paypal to those who can do it successfully. I am so burnt out on trying to make this work. This PITA is not worth android. I have a one click jailbroken phone now. And I have successfully rooted and installed custom roms before but this is totally out of hand how complex this is for me. Maybe I'm just remedial but it seems several are having trouble with this model. For open source, this should not be this tough.
/rant. Almost ready to throw in the towel, but still listening.....
Sorry for the multiple posts. Just trying to get some new opinions. HTC Evo 4 g was done in 10 minutes. This has taken 4 days.
:crying:

bullpen7979 said:
I have an unlocked bootloader on Moto X from sprint. I just need the easiest way to root.
This looked confusing. http://forum.xda-developers.com/showthread.php?t=2536200. Gotta be another way.
Have considered restoring to stock and taking the dang thing back http://atsgadgets.com/how-to-restor...lite-att-t-mobile-sprint-verizon-us-cellular/. So frustrated.
I've offered paypal to those who can do it successfully. I am so burnt out on trying to make this work. This PITA is not worth android. I have a one click jailbroken phone now. And I have successfully rooted and installed custom roms before but this is totally out of hand how complex this is for me. Maybe I'm just remedial but it seems several are having trouble with this model. For open source, this should not be this tough.
/rant. Almost ready to throw in the towel, but still listening.....
Sorry for the multiple posts. Just trying to get some new opinions. HTC Evo 4 g was done in 10 minutes. This has taken 4 days.
:crying:
Click to expand...
Click to collapse
Are you on 4.4 and what computer OS are you using?

I am on android version 4.2.2 and windows xp SP 3. thanks for your response, sir.

bullpen7979 said:
I am on android version 4.2.2 and windows xp SP 3. thanks for your response, sir.
Click to expand...
Click to collapse
Here, go into Settings -> About Phone and tell me what your Build Number is (at the very bottom).

Do not put in the cmd window mfastboot, just try fastboot flash recovery twrp 2.6.3.1-ghost-4.4.img. Now also put the recovery image in the same folder as fast boot, I believe its SDK tools folder
Sent on my Moto X

bullpen7979 said:
I am on android version 4.2.2 and windows xp SP 3. thanks for your response, sir.
Click to expand...
Click to collapse
The method that you thought was confusing, is the one you should use. If I have time, I could try helping you with it.

ALU0506, the build number is 13.9.0Q2.X-116-MX-17-57-1. Thanks everyone for your help.

I have downloaded the files mentioned in the thread. Thats as far as i have gotten. If you have time to help, that would be great. I mean like over the top great

bullpen7979 said:
I have downloaded the files mentioned in the thread. Thats as far as i have gotten. If you have time to help, that would be great. I mean like over the top great
Click to expand...
Click to collapse
I can try helping over gtalk.

bullpen7979 said:
I have downloaded the files mentioned in the thread. Thats as far as i have gotten. If you have time to help, that would be great. I mean like over the top great
Click to expand...
Click to collapse
Plug in your phone and put it into fastboot by typing adb reboot bootloader then type fastboot devices does it show that you are connected?

I will try that as soon as I can and get back to you. I have two computers one at my hotel and one here. I'm not sure I have the ADB tools on my netbook
Sent from my XT1056 using xda app-developers app

bullpen7979 said:
I will try that as soon as I can and get back to you. I have two computers one at my hotel and one here. I'm not sure I have the ADB tools on my netbook
Sent from my XT1056 using xda app-developers app
Click to expand...
Click to collapse
if you are still looking for help i can help you get this done on gtalk as well. send me a pm with your username. it will take virtually no time at all

jayboyyyy said:
if you are still looking for help i can help you get this done on gtalk as well. send me a pm with your username. it will take virtually no time at all
Click to expand...
Click to collapse
especially since he already unlocked the bootloader. Just flash recovery, then flash supersu.zip.

aooga said:
especially since he already unlocked the bootloader. Just flash recovery, then flash supersu.zip.
Click to expand...
Click to collapse
ya during his four days of misery, he could have just read for 1 hour on the stuff so it would seem confusing anymore and then he would have had a rooted phone. But either way, his problem is solvable with a few simple instructions.

OK Jay/Aooga.
Finally back from work.
Plug in your phone and put it into fastboot by typing adb reboot bootloader then type fastboot devices does it show that you are connected?
open cmd window, typed adb reboot bootloader, and got:
T063202TFL and fastboot, and then a prompt.

OK Jay/Aooga.
Finally back from work.
Plug in your phone and put it into fastboot by typing adb reboot bootloader then type fastboot devices does it show that you are connected?
open cmd window, typed adb reboot bootloader, and got:
T063202TFL and fastboot, and then a prompt.
Phone is in fastboot mode with white, yellow green text.
Device is unlocked. Status code 3.
Battery OK Charging
Transfer mode USB connected.
It looked as though I had to be able to accept the 4.4 kitkat OTA in order to get this done. but when i went to the usual spot to look for system updates it said there were none available.
Anyhow, I am super grateful for your help. Sorry to be such a remedial doofus

Looks like we can wait till tomorrow. Or today. Or whatever timeline it is.

adb and rooting issues

so i am trying to root using this io method i believe it is called i thought i had adb installed but it seems as though it is not. i have tried using a few methods here on xda none seem to work restarted pc several times as well as phone run adb devices and my devices isn't there in fact i got invalid command or whatever. ran the root tool same thing happend yes i am usb debugging enabled, ethernet mode. does anyone have a good guide to get adb to install correctly on windows 8.1 nothing

Bfitz26 said:
so i am trying to root using this io method i believe it is called i thought i had adb installed but it seems as though it is not. i have tried using a few methods here on xda none seem to work restarted pc several times as well as phone run adb devices and my devices isn't there in fact i got invalid command or whatever. ran the root tool same thing happend yes i am usb debugging enabled, ethernet mode. does anyone have a good guide to get adb to install correctly on windows 8.1 nothing
Click to expand...
Click to collapse
ok well i got adb working showed device but when i run root script it says push any key to continue i click it and it says not a valid command or something and exits? not sure what the deal is here a little frustrating i am a bit confused why i haven't seen this talked about any where?

Bfitz26 said:
ok well i got adb working showed device but when i run root script it says push any key to continue i click it and it says not a valid command or something and exits? not sure what the deal is here a little frustrating i am a bit confused why i haven't seen this talked about any where?
Click to expand...
Click to collapse
What exactly did it say?

TheOriginalKyle said:
What exactly did it say?
Click to expand...
Click to collapse
thanks anyway i got it so my questions at this point are: our bootloader is locked on 12b right and is that just stopping us from kernels? last time i remember a locked bootloader you needed a safestrap to flash anything so i am a bit baffled. 2 best way to get custom recovcery what is the best least issues and most compatiable, i have seen some failed efs partitions causing bricks and can we flash any rom placed here in the developement section on any softwasre version with any recovery.thanks for any and all help anyone can give. i have searched the forums just keep getting mixed awnsers to my questions just want to make sure i am doing the right thing.

Bfitz26 said:
thanks anyway i got it so my questions at this point are: our bootloader is locked on 12b right and is that just stopping us from kernels? last time i remember a locked bootloader you needed a safestrap to flash anything so i am a bit baffled. 2 best way to get custom recovcery what is the best least issues and most compatiable, i have seen some failed efs partitions causing bricks and can we flash any rom placed here in the developement section on any softwasre version with any recovery.thanks for any and all help anyone can give. i have searched the forums just keep getting mixed awnsers to my questions just want to make sure i am doing the right thing.
Click to expand...
Click to collapse
1. I believe our bootloader is locked, I don't think safe strap is necessary just make a backup before you flash anything too risky
2. For the custom recovery this method seems to work the best http://forum.xda-developers.com/showthread.php?t=2449670 it also explains #1 better. You can also flash Clockwork Recovery the difference is mainly personal preference. To get the latest TWRP on you'll need to flash the .img then when it's all set up flash the .zip.
3. For the failed efs partitions here's a link to back that up (I had no idea that was a problem). http://forum.xda-developers.com/showthread.php?t=2451390 I only used this when I flashed a different radio, also the only brick that I know of is with FreeGee on 12b but that's the lazy way and who knows maybe he fixed it.
4. ROM's will usually tell you what is compatible and what isn't, if you have the latest TWRP or CRP you should be fine on 12b just read the instructions and scan the comments for issues.
Glad I could help

Thanks!
Sent from my VS980 4G using Tapatalk

[Q] HELP! Wiped system files now can't boot up the phone (says no OS installed)

Sorry but I'm a total rookie here. I first started screwing around with my stock Nexus 6 by rooting. Then somehow I ended up with TWRP installed (or whatever) on my phone. Today I received notification that 5.0.1 OTA was available and when I click install it just went into TWRP and wouldn't let me install the update. For some reason I messed with TWRP and erased everything. Now I'm stuck with a brick.
Oh an to boot I can't get Android SDK running on my computer because of JVM or something.
Can anyone help? I just want to go back to out of the box stock and start over if that's possible. No TWRP or rooting necessary for me after this episode.
Thanks so much in advance for the assistance (please use small words and short sentences). Yes, I've tried searching like crazy and can't find anything that just step by step instructs me how to get back to stock.

ssbmg said:
Sorry but I'm a total rookie here. I first started screwing around with my stock Nexus 6 by rooting. Then somehow I ended up with TWRP installed (or whatever) on my phone. Today I received notification that 5.0.1 OTA was available and when I click install it just went into TWRP and wouldn't let me install the update. For some reason I messed with TWRP and erased everything. Now I'm stuck with a brick.
Oh an to boot I can't get Android SDK running on my computer because of JVM or something.
Can anyone help? I just want to go back to out of the box stock and start over if that's possible. No TWRP or rooting necessary for me after this episode.
Thanks so much in advance for the assistance (please use small words and short sentences). Yes, I've tried searching like crazy and can't find anything that just step by step instructs me how to get back to stock.
Click to expand...
Click to collapse
Try wugfresh's nexus toolkit 2.0.search xda and download to your pc.

Sorry I should've mentioned - I'm on a Mac, not a PC.

Nevermind - fixed by using the one click toolkit in reverse to re-lock bootloader. All good and back to factory.
Mods - delete this useless post if you want.

ssbmg said:
Sorry I should've mentioned - I'm on a Mac, not a PC.
Click to expand...
Click to collapse
This thread show "bail you out..."
For Future reference, having access to a PC when you have an Android phone that you are rooting is somewhat warranted if no one develops the MAC stuff... I have both and although I prefer my MAC, having a PC sometimes is essential. The Thread has links to follow if you are a MAC user.
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
:good:

mahst68 said:
This thread show "bail you out..."
For Future reference, having access to a PC when you have an Android phone that you are rooting is somewhat warranted if no one develops the MAC stuff... I have both and although I prefer my MAC, having a PC sometimes is essential. The Thread has links to follow if you are a MAC user.
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
:good:
Click to expand...
Click to collapse
Can use fastboot and adb on a mac to either push a rom.zip to recovery and flash or to flash factory images

Android 6.0 Root..?

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.