Related
I can not get them to work. I've spent hours trying to install the correct drivers and such and one problem after another. FYI I am not a total newb and have searched in vain, but hopefully I missed the answer and someone else is willing to share?
I had same issue before. But I got it done by following this instruction:
http://forum.xda-developers.com/showthread.php?t=910008
Make sure to check out the troubleshooting part. In my case, item #4 fixed my issue. Adb is a much easier way to interact with nc.
Sent from my HTC Desire using Tapatalk
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
Does anyone know an easier way to put clockwork onto my phone? I mean other than (adb).. for some reason it doesn't pick up my phone.. Is there an recovery App coming out soon?
Sent from my LG-P925 using xda premium
make sure you have debugging mode on and that your Windows or Mac proper LG drivers are installed so that the phone is recognized also put CMD in the same folder as platform tools in sdk manager folder vice versa for files needed to be pushed to phone.
I got the drivers from the LG website for my cell, hmmm... ill have to recheck everything else because ADB has never gave me this much trouble
Sent from my LG-P925 using xda premium
I'd be willing to code a one click solution if it would be helpful. Its pretty easy as it is tho
Sent from my LG-P925 using xda premium
I had the same problems. I followed everything step by step and made sure I had the right drivers along with everything I would need with Java. Still no luck. I have the combination of feeling stupid and frustrated. I have rooted and installed custom roms on three different phones before.
A one click solution would be amazing if you could come up with that. I will try the ADB way again later.
Vince
Yes a one click, alot of people would thank you ....and i would be gratefull
Sent from my A500 using xda premium
i agree. ive been trying the adb method all day. for some reason just wont work. im prolly missing something
Try updating all the drivers for adb. It would be helpful for you and it would probably solve your issue.
Sent from my LG Thrill 3D using XDA Premium
Does one click root work for you? If it does, there is nothing wrong with your drivers.
Once you get one click root working, put the recover in the ADB folder that is part of one clock root.... then open that fold, hold shift and right click, select open command prompt, then type in the adb commands from the CWM instructions thread.
LG uses the same drivers for all their Android devices, I used their driver installer app and selected the Verizon LG Fathom since it didn't have the Thrill listed anywhere, have had no problems.
Some reason my comp doesnt do any of this correctly... so much for brand new tech
Does one click root work for you?
If not, you have a driver problem, fix it by downloading LG's driver installer, select Verizon for the carrier and then select the Fathom. If you have a drive issue, and that fails to fix it, try a different USB port... make sure you have your phone in debug mode... can you mount your SD cards?
If one click root does work, then YOU, not your new technology, is doing something wrong. So the question is, what are you doing wrong...
Please answer the question, does one click root work? From there, tell us step by step what you are doing, and we will tell you what needs fixing.
almost done
pjcforpres said:
Does one click root work for you? If it does, there is nothing wrong with your drivers.
Once you get one click root working, put the recover in the ADB folder that is part of one clock root.... then open that fold, hold shift and right click, select open command prompt, then type in the adb commands from the CWM instructions thread.
LG uses the same drivers for all their Android devices, I used their driver installer app and selected the Verizon LG Fathom since it didn't have the Thrill listed anywhere, have had no problems.
Click to expand...
Click to collapse
i put recovery in the adb folder, get all the way through the adb process and it says img can not be found? lol wtf
Did one click root work for you?
installed the fathom drivers, my iphoney 4, or my htc inspire was never this hard to work with
one click is the way i rooted my phone
robertmoore208 said:
one click is the way i rooted my phone
Click to expand...
Click to collapse
Ok, then driver issues isn't a problem, I would take a really close look at your ADB commands, and be sure to wait 30 seconds after each one to let it process.
I would recommend copy pasting the longer commands (right click copy, right click paste, the keyboard shortcuts don't work in command prompt window).
now it says permission denied on first command?
Then you don't have root... run one click root again. I would use it's driver check feature as well before running it.
lol i lost root? wow ok strange... i have superuser
Well... if you get accessed denied you either are typing something wrong, skipping a step, or trying to do something that needs root and you don't have root.
Do you have debug mode turned on? Do you see this active in your phones notification bar? That first line doesn't even need root access, if IIRC.
I just bought an OG droid from this girl on craigslist, and I want to find the easiest way to root it, unlock the bootloader, and install cwm recovery. I'm using a MacBook pro for all of this. If anyone has a direct link, or if anyone can point me in the right direction, it would be most appreciated.
Sent from my Droid using xda premium
Oh, and its on 2.2.2 if that helps anyone.
Sent from my Droid using xda premium
I actually was trying to figure out the same thing for myself last night. What I ended up doing was SBF'ing back to stock, 2.0.x... I can't remember lol.
Download the rooted version of your OS. (Stock was easiest for me to find.) Change the name to update.zip and boot into recovery to apply it. From there I just installed rom manager and flashed CWM through it.
I'd post links, but I looked ALL over the internet and used a bunch of ideas. Also, those sites look bad on my work computers history
EDIT: Found it. This is the website I used most for how to root.
http://www.mydroidworld.com/forums/...-motorola-droid-1-ubuntu-linux-using-mdw.html
Also, this is a ubuntu manual, but you can probably also use it for mac as well.
Noob-to-Noob Help
I believe I used the method posted above, but it took me several tries to figure out what I was doing wrong, because in the YouTube guide videos, they wouldn't include this step.
This *MIGHT* be the same method I used. So I could be wrong. But when you're plugging in your phone to the computer, Turn Debugging on, but do NOT mount your SD card to the computer. That reason alone screwed me over so much because none of the video guides mentioned it. I always did it out of habit.
hAHAha Halo said:
I believe I used the method posted above, but it took me several tries to figure out what I was doing wrong, because in the YouTube guide videos, they wouldn't include this step.
This *MIGHT* be the same method I used. So I could be wrong. But when you're plugging in your phone to the computer, Turn Debugging on, but do NOT mount your SD card to the computer. That reason alone screwed me over so much because none of the video guides mentioned it. I always did it out of habit.
Click to expand...
Click to collapse
I'm pretty sure I kept it mounted, turning debugging on was enough for me. Otherwise you wouldn't be able to push files onto the sd card.
Then again I might have used a different program, I rooted about.. 3 months ago. I think it could have been along the lines of for the first part keep it unmounted, then later mount it.
Something along those lines. Either way, this is the method I used. Once you have all the files you can root/unroot in 5 minutes easy.
Hello,
I have been following a thread in the Developer section, I'm unable to post there.
I could not find an answer?
I want to find out if there will be an issue using the NEXUS 7 TOOLKIT AUTO UPDATE V4.3.4 (SkipSoft.net)
I already have the Android SDK installed, a long story whilst playing about with a cheap Chinese Tablet :crying:
I realised the error of my ways and now have a nice Nexus 7 (4.2.2)
*** Anybody help please?, seeing that I can't post in the appropriate thread ***
Thanks
Dave
Nexus 7 toolkit auto update v4.3.4
NinjaMogglet said:
Hello,
I have been following a thread in the Developer section, I'm unable to post there.
I could not find an answer?
I want to find out if there will be an issue using the NEXUS 7 TOOLKIT AUTO UPDATE V4.3.4 (SkipSoft.net)
I already have the Android SDK installed, a long story whilst playing about with a cheap Chinese Tablet :crying:
I realised the error of my ways and now have a nice Nexus 7 (4.2.2)
*** Anybody help please?, seeing that I can't post in the appropriate thread ***
Thanks
Dave
Click to expand...
Click to collapse
Can anybody help please?,
No problems should arise. Though I don't quite understand your question. Is this right: You want to update/install a toolkit, but you have the Android SDK installed? If that's what you are asking then no, there will be no problems.
Confirmation
Logan_M said:
No problems should arise. Though I don't quite understand your question. Is this right: You want to update/install a toolkit, but you have the Android SDK installed? If that's what you are asking then no, there will be no problems.
Click to expand...
Click to collapse
Hi,
Sorry this is quite new to me.
Yes, I had installed the official Android SDK whilst playing/experimenting with a cheap tablet.
Now I have a Nexus 7, and it is recognised by my WinXP PC alraedy.
I want to unlock & root and found the thread in the developers section, but I'm unable to post there.
I wanted to ensure that I would not encounter problems/conflicts if I installed and used the Nexus 7 toolkit auto update v4.3.4 Tool on the same PC.
Hope this makes sense?
Thanks
NinjaMogglet said:
Hi,
Sorry this is quite new to me.
Yes, I had installed the official Android SDK whilst playing/experimenting with a cheap tablet.
Now I have a Nexus 7, and it is recognised by my WinXP PC alraedy.
I want to unlock & root and found the thread in the developers section, but I'm unable to post there.
I wanted to ensure that I would not encounter problems/conflicts if I installed and used the Nexus 7 toolkit auto update v4.3.4 Tool on the same PC.
Hope this makes sense?
Thanks
Click to expand...
Click to collapse
You already have the SDK, that means you don't need a toolkit....
Sent from my Nexus 7 using Tapatalk HD
Pirateghost said:
You already have the SDK, that means you don't need a toolkit....
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Unfortunately having the SDK does not mean I can actually use it
I got in over my head, hence trying to learn/read about it it on XDA
I found the thread that appeared to offer what I want,
a toolkit that I should be able to use to unlock/root with.
Thanks
But of you have the SDK and the drivers installed you don't need toolkit
Its like 3 commands
you dont have to know how to use the entire SDK, all you need to do is be able to follow directions. every nexus is rooted the exact same way. the only thing the toolkit does is hide the commands. you could take the few minutes to learn these commands
fastboot oem unlock
fastboot flash recovery nameofrecoveryfile.img
reboot to recovery
adb push SuperSU.zip /sdcard/ (or /data/media, whatever)
flash supersu.zip with your custom recovery....
Sent from my Nexus 7 using Tapatalk HD
Pirateghost said:
You already have the SDK, that means you don't need a toolkit....
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Pirateghost said:
But of you have the SDK and the drivers installed you don't need toolkit
Its like 3 commands
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks...
It was the commands I had problems with on my last attempts
I got confused over ADB mode, Fastboot mode ??
I was not sure if they are device specific, given the Toolkits appear to be ??
I just don't want to brick my Nexus
Hence the thought of getting something(Toolkit) that I can just select options, hides the complexity.
Also
The toolkit looked like I could Backup all my Apps/Data, then unlock/root, and then do a Restore.
Thanks
NinjaMogglet said:
Thanks...
It was the commands I had problems with on my last attempts
I got confused over ADB mode, Fastboot mode ??
I was not sure if they are device specific, given the Toolkits appear to be ??
I just don't want to brick my Nexus
Hence the thought of getting something(Toolkit) that I can just select options, hides the complexity.
Also
The toolkit looked like I could Backup all my Apps/Data, then unlock/root, and then do a Restore.
Thanks
Click to expand...
Click to collapse
there are many guides and tutorials on all of these points.
here's the problem with toolkits:
THEY HIDE EVERYTHING FROM YOU
sure, more than likely you will be quite successful in merely rooting and unlocking your device with one....
then there is a pretty high certainty that you will begin experimenting with mods/roms/kernels/etc
at some point during your experimentation you will come across a 'soft-brick' or a bootloop, where all you see is either the google screen or the boot animation looping over and over. how do you get out of that situation? the toolkit didnt show you how, you plug in your trusty toolkit, only to find it doesnt see the device.... PANIC MODE ON!!....great. now you are going to come to XDA and make a damn thread about how you just 'bricked' your device and the world is ending....then you get told how to fix it albeit with some frustrations and complications....the right way, with fastboot and adb
or
you could just learn the damn thing and understand what it is you are doing to your device....then there would never be a situation you could not get out of using fastboot and adb.....
it really isnt complicated, and people around here are just Friggin lazy...its ridiculous.
XDA used to mean something, now its just a pisspot of people wanting their devices to be cool, without wanting to learn anything.
All Understould
Pirateghost said:
there are many guides and tutorials on all of these points.
here's the problem with toolkits:
THEY HIDE EVERYTHING FROM YOU
sure, more than likely you will be quite successful in merely rooting and unlocking your device with one....
then there is a pretty high certainty that you will begin experimenting with mods/roms/kernels/etc
at some point during your experimentation you will come across a 'soft-brick' or a bootloop, where all you see is either the google screen or the boot animation looping over and over. how do you get out of that situation? the toolkit didnt show you how, you plug in your trusty toolkit, only to find it doesnt see the device.... PANIC MODE ON!!....great. now you are going to come to XDA and make a damn thread about how you just 'bricked' your device and the world is ending....then you get told how to fix it albeit with some frustrations and complications....the right way, with fastboot and adb
or
you could just learn the damn thing and understand what it is you are doing to your device....then there would never be a situation you could not get out of using fastboot and adb.....
it really isnt complicated, and people around here are just Friggin lazy...its ridiculous.
XDA used to mean something, now its just a pisspot of people wanting their devices to be cool, without wanting to learn anything.
Click to expand...
Click to collapse
Hi,
All understould, and I couldnt agree more. The challenge, with many things now(on the Web) is finding the right information.
There are oodles, and oodles of sites with rooting information, tips and guides... etc..
I've probably watched a dozen or more "Youtube" vid's on the same subject, and they all have subtle differences..!!
I will look for "Manual" Unlocking and Rooting info for the Nexus.. and see what I find
Thanks...
NinjaMogglet said:
Hi,
All understould, and I couldnt agree more. The challenge, with many things now(on the Web) is finding the right information.
There are oodles, and oodles of sites with rooting information, tips and guides... etc..
I've probably watched a dozen or more "Youtube" vid's on the same subject, and they all have subtle differences..!!
I will look for "Manual" Unlocking and Rooting info for the Nexus.. and see what I find
Thanks...
Click to expand...
Click to collapse
not sure why you need to go anywhere other than right here on XDA....
theres a freakin sticky for it even...
http://forum.xda-developers.com/showthread.php?t=2150661
NinjaMogglet said:
Hi,
All understould, and I couldnt agree more. The challenge, with many things now(on the Web) is finding the right information.
There are oodles, and oodles of sites with rooting information, tips and guides... etc..
I've probably watched a dozen or more "Youtube" vid's on the same subject, and they all have subtle differences..!!
I will look for "Manual" Unlocking and Rooting info for the Nexus.. and see what I find
Thanks...
Click to expand...
Click to collapse
NinjaMogglet has given you all the information needed!
Just go grab the required files and chuck them in your platform-tools directory, run a command prompt and navigate to the directory and then run the said commands.
Still not clear??
smt8544 said:
NinjaMogglet has given you all the information needed!
Just go grab the required files and chuck them in your platform-tools directory, run a command prompt and navigate to the directory and then run the said commands.
Click to expand...
Click to collapse
I thank everybody for the comments...
I have since found other "Manual" methods, none of them are consistent
> Some use ADB commands to do certain things?
> There are references to making the "Recovery Stick", with some mnt, mv commands in ADB/FASTBOOT, it's not clear?
> There is reference to being in the right mode USB Debug Mode, PTP & MTP, but which?
> Install a Busy Box?
> and and ...
Whilst it maybe second nature to some of you folks, to me(others?) it a Black Art at the moment
I will do it, I just don't want to get part way in, and have a problem.
Thanks
NinjaMogglet said:
I thank everybody for the comments...
I have since found other "Manual" methods, none of them are consistent
> Some use ADB commands to do certain things?
> There are references to making the "Recovery Stick", with some mnt, mv commands in ADB/FASTBOOT, it's not clear?
> There is reference to being in the right mode USB Debug Mode, PTP & MTP, but which?
> Install a Busy Box?
> and and ...
Whilst it maybe second nature to some of you folks, to me(others?) it a Black Art at the moment
I will do it, I just don't want to get part way in, and have a problem.
Thanks
Click to expand...
Click to collapse
my previous post literally linked you to the ONLY thing you need....why did you ignore it?
its simple:
ADB can be used while in Custom Recovery or while booted into Android with USB debugging enabled.
Fastboot is used ONLY in fastboot mode
settings within the Android OS dont mean a damn thing in recovery or fastboot....which means it doesnt matter what USB mode you are in, or if debugging is enabled, as long as you are doing things from recovery or fastboot
every nexus device roots and unlocks in the same exact manner. the only difference would be that you need to use a recovery made SPECIFICALLY for that device...thats it
FOLLOW THE GUIDE THAT I ALREADY LINKED YOU TO....it tells you everything you need to do
Thanks
Pirateghost said:
my previous post literally linked you to the ONLY thing you need....why did you ignore it?
its simple:
ADB can be used while in Custom Recovery or while booted into Android with USB debugging enabled.
Fastboot is used ONLY in fastboot mode
settings within the Android OS dont mean a damn thing in recovery or fastboot....which means it doesnt matter what USB mode you are in, or if debugging is enabled, as long as you are doing things from recovery or fastboot
every nexus device roots and unlocks in the same exact manner. the only difference would be that you need to use a recovery made SPECIFICALLY for that device...thats it
FOLLOW THE GUIDE THAT I ALREADY LINKED YOU TO....it tells you everything you need to do
Click to expand...
Click to collapse
Thanks...
I did not ignore your link, I read all the pages.
Especially the one's that pointed out the ommisions, like un-lock first, and some of the key presses.
I will get back to this when I'm bright eyed, not 01:25 in the morning.... Just in case.
Thanks again