Hey, I just got a Nexus 7 16GB, yesterday. I'm familiar with CWM, Nandroids, flashing, etc...
I don't have ADB installed and am hoping to get opinions on the toolkits I've seen. Are they a good way to go, to obtain root and get in a position to flash ROMs. And which one would you maybe suggest? I'm running Win XP.
I want to run this kernel: http://www.derkernel.com/jb-seven.php (Trinity Seven)
I'd like suggestions on which ROM to run. Something stable, barebones and running 4.2. AOKP would be nice.
Thanks for hearing me out. Excited to get off of stock. :good:
T679noob said:
Hey, I just got a Nexus 7 16GB, yesterday. I'm familiar with CWM, Nandroids, flashing, etc...
I don't have ADB installed and am hoping to get opinions on the toolkits I've seen. Are they a good way to go, to obtain root and get in a position to flash ROMs. And which one would you maybe suggest? I'm running Win XP.
I want to run this kernel: http://www.derkernel.com/jb-seven.php (Trinity Seven)
I'd like suggestions on which ROM to run. Something stable, barebones and running 4.2. AOKP would be nice.
Thanks for hearing me out. Excited to get off of stock. :good:
Click to expand...
Click to collapse
If you are already familiar with CWM, flashing, etc., then don't use a toolkit. You don't need one. Use adb and fastboot to unlock the bootloader, flash a custom recovery of your choice and the superuser zip you prefer. You could do it in a few minutes. There are multiple guides if you require assistance. It's a Nexus, so there are no tricks - it's simple and straightforward.
Once you get the custom recovery installed, you can then flash your kernel.
I prefer stock on mine. I've had a 16GB, 32GB and now I have a 32/3G. While I do replace boot/kernel with more enhanced ones, I prefer the stock image. But if you want to try out various ROMs, that's up to you and your preferences. Just make sure it's 4.2 compliant.
Congrats, the N7 is awesome.
phonic said:
If you are already familiar with CWM, flashing, etc., then don't use a toolkit. You don't need one. Use adb and fastboot to unlock the bootloader, flash a custom recovery of your choice and the superuser zip you prefer. You could do it in a few minutes. There are multiple guides if you require assistance. It's a Nexus, so there are no tricks - it's simple and straightforward.
Once you get the custom recovery installed, you can then flash your kernel.
I prefer stock on mine. I've had a 16GB, 32GB and now I have a 32/3G. While I do replace boot/kernel with more enhanced ones, I prefer the stock image. But if you want to try out various ROMs, that's up to you and your preferences. Just make sure it's 4.2 compliant.
Congrats, the N7 is awesome.
Click to expand...
Click to collapse
Well, I can't even get the USB drivers to work lmao off to bed. Frustrated and delirious =D
I used http://www.ibtimes.co.uk/articles/4...ndroid42-jop40c-jellybean-ota-cwmrecovery.htm as a guide, but really have no idea what to do with these drivers. Toolkit isn't even working right to install them.
T679noob said:
Well, I can't even get the USB drivers to work lmao off to bed. Frustrated and delirious =D
I used http://www.ibtimes.co.uk/articles/4...ndroid42-jop40c-jellybean-ota-cwmrecovery.htm as a guide, but really have no idea what to do with these drivers. Toolkit isn't even working right to install them.
Click to expand...
Click to collapse
What operating system and version are you on
nba1341 said:
What operating system and version are you on
Click to expand...
Click to collapse
Windows XP 2002 Service Pack 3
If you mean Android, it's 4.2 (JOP40C)
Whenever I choose the folder containing the drivers, when trying to update in device manager, it won't let me select the folder.
OK so I got the drivers installed. Appears it wasn't working because I had the floppy drive checked. Now I still don't see the device in My Computer and I have the yellow exclamation point on MTP, in device manager. I read that you need WMP 11, which I have. Not sure where to go from here.
T679noob said:
Whenever I choose the folder containing the drivers, when trying to update in device manager, it won't let me select the folder.
Click to expand...
Click to collapse
Try PDAnet for drivers also make sure usb debuging is enable on the nexus
flicnflack said:
Try PDAnet for drivers also make sure usb debuging is enable on the nexus
Click to expand...
Click to collapse
I was actually just getting on to say that turning OFF usb debugging now shows my device in my computer
Now I can't get ADB to work. This is a little ridiculous. Gonna change to a Win 7 PC, I guess.
I would strongly suggest you spend a week just using the device before you consider putting a new rom on it.
You will have no basis for comparison unless you know what you are starting with.
rmm200 said:
I would strongly suggest you spend a week just using the device before you consider putting a new rom on it.
You will have no basis for comparison unless you know what you are starting with.
Click to expand...
Click to collapse
Yeah, I'm actually going to stay on stock for the time being, but I want to flash the OC kernel. Noticing a little more game lag than expected.
T679noob said:
Windows XP 2002 Service Pack 3
If you mean Android, it's 4.2 (JOP40C)
Click to expand...
Click to collapse
I can never understand why someone with the latest gadget would insist on trying to make it work on such an antiquated PC.:silly:
Miami_Son said:
I can never understand why someone with the latest gadget would insist on trying to make it work on such an antiquated PC.:silly:
Click to expand...
Click to collapse
While I personally run Linux on most of my computers, I honestly prefer to use WinXP if I need to run Windows.
First, I like the GUI. It's straight, simple and to the point. It's also widely considered to be Microsoft's best OS. The corporate market continues to use it a lot, and went ballistic when MS decided to end-of-life it. Also, on the rare occasions when I use Windows personally, it's usually because I need to run some app or connect to some device that is picky. And when that happens, I've found XP to be the most supported version around. In fact, I run it in a VM because a DVR system we use at the front gate of our HOA, which requires some specialized software, won't run on Vista or 7.
And in regards to the Android SDK, I imagine it's much easier to get running on that platform as well.
I'm unlocked, rooted, with a custom recovery. Thanks to anyone who had input.
Miami_Son said:
I can never understand why someone with the latest gadget would insist on trying to make it work on such an antiquated PC.:silly:
Click to expand...
Click to collapse
Thanks for your help. I dunno what I'd do without you.
phonic said:
It's also widely considered to be Microsoft's best OS.
Click to expand...
Click to collapse
By whom? I've been using W7 since Beta and RC1 and have had few issues with it (Vista is another story). On the rare occasion something won't run on it there is compatibility mode. The point of my post was that if you insist on using an OS that is now 3 iterations behind the most current version and you are having an issue with a newer device that wasn't really designed for that OS, then expect to have issues with driver support, compatibility and general operation. I just thought it was interesting (funny, actually) that in a forum where so many members are hell-bent on getting the latest greatest version of Android on their devices someone would still be using XP on their PC.:silly:
Related
so i am new to android and i decided " hey why don't i try to root my nexus" so i tried and i cant get any father that checking if the computer can see my device which it cant for some reason. so i went online i figured out that i don't have the usb driver for android. so after that i tried to down load then and i even installed them and restarted my computer and it still wont work. so if any one can help me with my problem it would be greatly appreciated.
On Home Screen, press menu>settings>applications>development and make sure USB debugging is checked.
What OS you running?
Specs would help, where did you get your drivers? What other software have you tried?
i turned on the debugging and it still hasnt worked
i am running xp. i downloaded the android sdk from here
developer.android.com
i just want to put the modaco desire rom on my phone that my onl reason for wanting to root. i really like the sense ui
I am having a similar problem, so i might as well use this thread instead of creating a new one.
I have a dual boot computer, win7 and fedora, both have SDK. I unlocked my nexus one with windows, as i noticed the commands were considerably easier, or at least they don't work when i plug the linux ones into fedora.
Last night i was going to push the undervolt kernel so i plugged my n1 while in win7, It instantly came up complaining about drivers, which i had already installed and had previously worked, i went to re-install them, and windows says they are up to date, but still no luck recognising the device (Debugging mode is definately on)
So i switched to fedora, no driver pop ups obviously, but when i try to push the kernel through, it does not recognise the device.
In the bootloader it says "fastboot usb" while plugged in.
I can't pinpoint when it stopped working, but the last time i used fastboot was to put the RA recovery, since then i flashed CM 5.0.2, CM 5.0.3.1, the desire rom, and used a nandroid restore to get back to 5.0.3.1
Anyone got any ideas? Without fastboot i am pretty much restricted to flashing .zip files from the recovery.
yeah i cant even unlock mine its so frustrating
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
drbrendin said:
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
I tried all day too like a gazillion times.... and wonder does everyone have driver issues? I tried with my XP computer and windows 7, no go, then I read posts people having the same issue, then they just post " nevermind got it" and didn't even write what they did to get it.......
Click to expand...
Click to collapse
not everyone is a dev
Ok, I have my Nexus One set up so I can use with via Windows 7 (desktop) or Ubuntu (Laptop).
The Linux part is a bit more involved, but since everyone is running Windows (unless I missed something), I will work there.
First of all, your phone needs to be in Dev mode (which was covered earlier).
With the phone UNPLUGGED from the PC, uninstall any previous SDK installs you have and be sure to remove the directory.
Then, install the SDK found here: SDK
Install this SDK and let it complete the install, which will include downloading for a bit. You need to do this since the SDK package above does NOT include the right drivers!!!
Once this has been completed, plug your phone into the computer via USB. Your computer will find a new device, however, it cannot locate the drivers for it. Browse and point the installer to:
DRIVE:\PATH_TO_android-sdk-windows\usb_driver
Don't go any further than this!!
Now, let it do it's thing and you should have a new device in the device manager called:
Android Phone
...|_Android Composite ADB Interface
Now, go to the command prompt and change to the following directory:
DRIVE:\PATH_TO_android-sdk-windows\tools
There, you will find adb.exe
Type:
adb devices
and you should see:
List of devices attached
HT019P801614 device
If not, something got screwed up and would need to dig further to help ya.
Ok ill give this a try once get home from school
nexus one root.
Ok assuming that you have the android sdk installed correctly, try rooting your phone via the superboot method. The first link below has a full detailed guide for rooting the nexus one and I believe has all of the device drivers for those who have not been able to get them running well. If you still have trouble getting the drivers working checkout the second link. Anyone who is relatively new to working with the sdk and is not familiar with working the commands check out the third link. Read the entire thread! it is very helpful.
1) http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
2) http://forum.xda-developers.com/showthread.php?t=613217
3) http://forum.xda-developers.com/showthread.php?t=619153
If you have any questions PM me on xda. I'll try and help in anyway, it took my like two days to actually root my nexus, I wasnt familiar with using ADB and Fastboot to root.
One thing I know I was having problems with since I came from the G1 was that the new SDK has to actually be installed via an .exe now. I was used to it all being in a zip so I kept trying to load up what I thought were the right USB drivers, but they were actually the 1.6 drivers I already had. So make sure to run the .exe that comes with the SDK.
ok so while i was downloading the sdk a notification came up that said that it could not rename the directory. is this bad?
i am having an issue with installing the right driver as well. my computer keeps installing the nexus one as a "mass storage device". i have uninstalled and reinstalled a few times but no luck. i have the phone set to debug mode, using XP btw. any help would be appreciated.
Alright guys, this post is just for reference and ease. I've been using xda ever since I got my old HTC Hero a year and a half ago. Now I have the EVO and xda has been nothing but helpful to me. I've decided to make this post to try to help anyone that might not know much about android so I will make this a simple, easy to understand post tutorial.
HTC EVO 4G 2.3 Gingerbread root tutorial:
(Step 1) Power down your phone and take the battery out. Printed on the phone under the battery is a serial number. It is on the bottom line and usually starts with the letters: HT then a series of numbers and letters. Write this code down for you will need it later.
(Step 2) Download superuser from this link: http://www.mediafire.com/?q3ujsx1m4uq1662.
(Step 3) Download the HTC drivers from this link: http://api.viglink.com/api/click?fo...=HTC Drivers&jsonp=vglnk_jsonp_13139469417033
(Step 4) Plug your phone to your computer and put the phone in disk drive mode. Now put the superuser .zip on the sdcard and change the mode to charge only.
(Step 5) Put the phone in usb debugging mode. Do this by: home>menu>settings>applications>development>usb debugging.
Also, enable fastboot. Do this by: home>menu>settings>applications>fastboot.
(Step 6) Got to: http://revolutionary.io/ Go down to the downloads section and select either windows or linux. (depending on your machine) Allow the file to download and proceed to the beta key generation.
(Step 7) Select your operating system (windows or linux) and your device and hboot version.
If you are unsure of your hboot version you can check by powering down your phone and holding volume down and the power button (make sure fastboot is turned off before doing this. just make sure to enable it again once you have checked and have the phone powered back up.)
Now enter your serial key (the code you got from under the battery.) select generate key and it will give you a beta key.
Make sure to keep the window open.
(Step 8) Extract the revolutionary.zip and run revolutionary. It should recognize your device and then ask for the beta key. Enter the beta key it gave you, remember it is case sensitive.
(Step 9) Revolutionary will now work its magic. Let it do its thing and DO NOT interrupt it. It may seem like it is frozen but it sometimes just takes a few minutes.
(Step10) After it gets done with all of its operations, revolutionary will ask if you want it to connect to the internet and download the recovery. type the letter "y" and hit enter. It will do it and then reboot.
(Step11) Now you need to flash the superuser .zip. Disable fastboot and and usb debugging and power down the device. Hold volume down and power at the same time until you get the hboot menu. It may check for an image and shouldn't find one. Just let it do its thing. Volume down and select recovery. It will reboot into recover. Now just volume down to install .zip then select choose .zip from sdcard and choose the su 2.3.6.3 efgh signed.zip and select yes. It will flash it. When it is done just reboot.
Congratulations. You are now rooted with superuser and s-off and have full root access.
Thank you, xda. I am grateful for this forum of great and helpful people, without you guys my android life would would be simply mediocre.
Edit: If you need to learn how to flash roms, here is my guide!!: http://forum.xda-developers.com/showthread.php?t=1230610
Nicely done but may I suggest 1 thing to some people that I have noticed in going thru the root thread in development. I think you should also download a rooted version of the rom http://forum.xda-developers.com/showthread.php?t=830153 and flash this right away or in lieu of flashing the root files. I have seen some people have issues running certain things with the root zip file provided.
Also I think the first thing that should be done prior to rebooting is Nandroid(ing) your present rom for safe keeping.
Yeah that makes sense. I haven't had any problems whatsoever with my way after doing it three different times with three different evos, but, nevertheless, I appreciate your input and if you have seen this problem then thank you for bringing it to the attention of the viewers of this thread.
This is by far the easiest Root I've done to date (granted I've only rooted by Hero and my Evo), but still. Gotta love simplicity.
Thank you for posting this! Now I have a few questions I am hoping someone could answer.
The first: Will this process wipe my phone?
And the second: Our home computer is a Mac. Since this isn't available for Mac computers at the moment, I have an older laptop running windows vista that I am trying it on. I tried to install the HTC drivers but it keeps popping up with a window asking if I want to repair it or remove it. What is this error? There isn't an option to just install it. What should I do to make it work?
Thank you for any help anyone can offer.
rocket999 said:
Thank you for posting this! Now I have a few questions I am hoping someone could answer.
The first: Will this process wipe my phone?
And the second: Our home computer is a Mac. Since this isn't available for Mac computers at the moment, I have an older laptop running windows vista that I am trying it on. I tried to install the HTC drivers but it keeps popping up with a window asking if I want to repair it or remove it. What is this error? There isn't an option to just install it. What should I do to make it work?
Thank you for any help anyone can offer.
Click to expand...
Click to collapse
The file is a simple exe file and should only install not sure whats that about and also it will not wipe out anything. But you do need to do a backup of your apps. My suggestion would be Titanium Backup or MyBackup
HOnestly people this root is incredibly easy to sit here and double triple guess your self with this particular procedure is unnecessary. Just follow direction to the letter at the original development thread or here and it will be done if 3 minutes. No risk at all IMO.... If you are still worried I would be happy to help out just PM me
rocket999 said:
Thank you for posting this! Now I have a few questions I am hoping someone could answer.
The first: Will this process wipe my phone?
And the second: Our home computer is a Mac. Since this isn't available for Mac computers at the moment, I have an older laptop running windows vista that I am trying it on. I tried to install the HTC drivers but it keeps popping up with a window asking if I want to repair it or remove it. What is this error? There isn't an option to just install it. What should I do to make it work?
Thank you for any help anyone can offer.
Click to expand...
Click to collapse
No, the rooting process does not get rid of any user information. It simply unlocks the bootloader for your phone. As for the drivers, what Windows OS are you using? I found it far easier to install the drivers on Windows 7 than XP.
ceng7904 said:
Yeah that makes sense. I haven't had any problems whatsoever with my way after doing it three different times with three different evos, but, nevertheless, I appreciate your input and if you have seen this problem then thank you for bringing it to the attention of the viewers of this thread.
Click to expand...
Click to collapse
In reality after you get s-off on your bootloader you can flash another rom. You only flash the su zip if you want to have your present rom rooted.
rocket999 said:
Thank you for posting this! Now I have a few questions I am hoping someone could answer.
The first: Will this process wipe my phone?
And the second: Our home computer is a Mac. Since this isn't available for Mac computers at the moment, I have an older laptop running windows vista that I am trying it on. I tried to install the HTC drivers but it keeps popping up with a window asking if I want to repair it or remove it. What is this error? There isn't an option to just install it. What should I do to make it work?
Thank you for any help anyone can offer.[/QUO
Nope. No data loss will occur. The drivers sometimes are interfered with by other programs so what I suggest is disabling your antivirus and uninstall anything you have on your computer that has to do with htc. Just keep the drivers and get rid of stuff like htc sync and pdanet.
Click to expand...
Click to collapse
playya said:
In reality after you get s-off on your bootloader you can flash another rom. You only flash the su zip if you want to have your present rom rooted.
Click to expand...
Click to collapse
This is true.
Evilsj said:
No, the rooting process does not get rid of any user information. It simply unlocks the bootloader for your phone. As for the drivers, what Windows OS are you using? I found it far easier to install the drivers on Windows 7 than XP.
Click to expand...
Click to collapse
Ok thanks. I just wanted to be sure. The computer is Windows Vista. Will the drivers still work on it?
rocket999 said:
Thank you for posting this! Now I have a few questions I am hoping someone could answer.
The first: Will this process wipe my phone?
And the second: Our home computer is a Mac. Since this isn't available for Mac computers at the moment, I have an older laptop running windows vista that I am trying it on. I tried to install the HTC drivers but it keeps popping up with a window asking if I want to repair it or remove it. What is this error? There isn't an option to just install it. What should I do to make it work?
Thank you for any help anyone can offer.
Click to expand...
Click to collapse
Nope. No data loss will occur. The drivers sometimes are interfered with by other programs so what I suggest is disabling your antivirus and uninstall anything you have on your computer that has to do with htc. Just keep the drivers and get rid of stuff like htc sync and pdanet.
Whoops! I got the HTC stuff to install and now it is in the process of rooting. I figured out right after I edited this post. Thank you for all the help!
rocket999 said:
Whoops! I got the HTC stuff to install and now it is in the process of rooting. I figured out right after I edited this post. Thank you for all the help!
Click to expand...
Click to collapse
Ok. Great! Hit the thanks button if it helped!
Hey nice post I just have one question how do you install the htc drivers
aksharpatel417 said:
Hey nice post I just have one question how do you install the htc drivers
Click to expand...
Click to collapse
Just go to the link I provided and download. Then install
Do I need to have my phone plugged in or anything like that
aksharpatel417 said:
Do I need to have my phone plugged in or anything like that
Click to expand...
Click to collapse
This is a bit redundant. I really don't understand what you mean but if you just follow the directions completely and entirely then it will work perfectly. Just plug it in when the directions call for it.
aksharpatel417 said:
Do I need to have my phone plugged in or anything like that
Click to expand...
Click to collapse
Stop over thinking it.... Its ok its really as simple as it sounds... Relax follow each step and you will be fine... Your questions sound like your worried and if you are the steps after you root will drive you crazy. Especially changing kernels, flashing radios or roms....
I am beyond frustrated... just as title says... I consider myself to be smart with computers but this damn computer will not recognize this tablet... could it have to do w/ the rom i have installed? I have downloaded the drivers from acer directly 3 times and uninstalled/installed SEVERAL times... rebooted the cpu several times...
seems as if no matter what i do i cant get it to be seen by the computer... any ideas?
Powell730 said:
I am beyond frustrated... just as title says... I consider myself to be smart with computers but this damn computer will not recognize this tablet... could it have to do w/ the rom i have installed? I have downloaded the drivers from acer directly 3 times and uninstalled/installed SEVERAL times... rebooted the cpu several times...
seems as if no matter what i do i cant get it to be seen by the computer... any ideas?
Click to expand...
Click to collapse
Not an issue with the rom. Shouldn't be anyhow. I might suspect the following;
1. Your USB cable?
2. When you installed drivers, "right" mouse click and select "run as administrator".
3. If your Acer drivers still won't install, Through Device Manager Install them manually. Don't let it search the PC.
4. If that doesn't work, get the Google USB Drivers from here;
http://developer.android.com/sdk/win-usb.html
Extract to your PC. Again, install manually from Device manager (if you get a compatibility warning, ignore it)
thank you for the response.. i got so frustrated that i just installed the stock un rooted full package from the dev section of 3.1.. then updated to 3.2 and 3.2.1 and then for some reason my tablet wouldnt update after that... just kept telling me my system was up to date.. BS!!! i just downloaded the update from the same thread and decrypted and then manually installed... still confused as to why my tablet was telling me i was up to take when i was only on 3.2.1... anyway.. ill look into rooting stock ics tomorrow.. thanks again... oh and btw my computer recognized the tablet after i was no longer rooted and running stock.
Powell730 said:
thank you for the response.. i got so frustrated that i just installed the stock un rooted full package from the dev section of 3.1.. then updated to 3.2 and 3.2.1 and then for some reason my tablet wouldnt update after that... just kept telling me my system was up to date.. BS!!! i just downloaded the update from the same thread and decrypted and then manually installed... still confused as to why my tablet was telling me i was up to take when i was only on 3.2.1... anyway.. ill look into rooting stock ics tomorrow.. thanks again... oh and btw my computer recognized the tablet after i was no longer rooted and running stock.
Click to expand...
Click to collapse
Stranger things have happened. Believe me Technically, a rom "can" be guilty of USB issues, but the ICS releases out right now don't have these issues. Usually you find these on initial Beta releases.
You have to be a little careful when going back to stock. Acer put a stop to the ICS updates for awhile after they found the update process was bricking tablets. And, not all regions got updates before they stopped the program after a couple of days.
I would guess it tells you you;re up to date, as there is no ICS for it yet till they resume the program. Just a guess.
As far as I know, for the 500, they were supposed to resume ICS updates on the 27th May. Last I heard anyhow.
That's because it's Windows 7, lol.
MikeyCriggz said:
That's because it's Windows 7, lol.
Click to expand...
Click to collapse
And????
Actually, I have less issues on windows7. Yeah, you sometimes have to use "run as administrator". So I am not sure what your point is. Technically.
@MD i didnt know they stopped the release ? Win 7 doesnt cause these issues , sorry , for those of you wanting to do more with your android stick with Win 7 , its alot easier than running it through Linux! I use both!
Hi, now most people here are smart with this type of thing soooo i wanted to ask you how i can root the nexus 7 running 4.2.2. I tried to use the wugfresh NRT but when I was installing drivers a problem occurred. Instead of having ADB drivers or something like that I had ADB Composite drivers installed even though i followed the guide completely and I have tried several times to correct this but i havent found a solution. Also i attempted to carry on the rooting process but it said i did not have the correct drivers installed and etc. So can someone give me a fool proof way of getting the right drivers for this thing so i can root so i can finally install some kernels and use the sixaxis controller app! sorry for the essay and all help is appreciated
hrsedJe Something
Use the THE GOOGLE NEXUS 7 TOOLKIT at : http://forum.xda-developers.com/showthread.php?t=1809195 and then use the files from here : http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650 and then start the tool and root. easiest solution I know.
If 4.2.2 doesn't show up in the device list, pick 4.2.1, worked fine for me.
How about instead on relying on a tool you know nothing about, you learn how your device works and how to root it manually? This way you aren't stuck dealing with problems like this in the first place.
I could understand the need/desire/etc. for special tools/kits on some branded and locked down devices. But the N7 is as open as it gets. If you have the SDK installed on your computer and a flashable SU zip, you could have your device unlocked and rooted in about 2 minutes.
phonic said:
How about instead on relying on a tool you know nothing about, you learn how your device works and how to root it manually? This way you aren't stuck dealing with problems like this in the first place.
I could understand the need/desire/etc. for special tools/kits on some branded and locked down devices. But the N7 is as open as it gets. If you have the SDK installed on your computer and a flashable SU zip, you could have your device unlocked and rooted in about 2 minutes.
Click to expand...
Click to collapse
Because:
a) It's not necessary.
b) I have been rooting using the manual way, like you described, on every Android phone I've had for the past few years. And every single time I forget how to do it. I always have to look up what I'm doing to refresh my memory.
Spending 2 hours on something won't make you a master, and unless you plan on consistently refreshing your memory and playing around with your phone (when most JUST want root), then there's no ****ing reason to manually learn how to do it.
Kaaji1359 said:
Because:
a) It's not necessary.
b) I have been rooting using the manual way, like you described, on every Android phone I've had for the past few years. And every single time I forget how to do it. I always have to look up what I'm doing to refresh my memory.
Spending 2 hours on something won't make you a master, and unless you plan on consistently refreshing your memory and playing around with your phone (when most JUST want root), then there's no ****ing reason to manually learn how to do it.
Click to expand...
Click to collapse
Dude, most commands for doing stuff on the N7 manually are four words. It really isn't a lot to remember. Also I don't think you understand the purpose of this site/forum.
..That being said.
Use Wug's toolkit and update the adb files in its install directory. Then just use the 4.2.1 settings if 4.2.2 doesn't show.
Here is a post with the files: http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650
sucks that the toolkit is only for windows, sucky windows
Kaaji1359 said:
Because:
a) It's not necessary.
b) I have been rooting using the manual way, like you described, on every Android phone I've had for the past few years. And every single time I forget how to do it. I always have to look up what I'm doing to refresh my memory.
Spending 2 hours on something won't make you a master, and unless you plan on consistently refreshing your memory and playing around with your phone (when most JUST want root), then there's no ****ing reason to manually learn how to do it.
Click to expand...
Click to collapse
There is a big difference between memorizing commands and actually understanding what they mean. Your post made it very clear that in the "years" you've been doing it, you never possessed the latter.
It is not a complicated process. Unlock bootloader, run custom recovery, flash su zip. Voila. In the amount of time it took you to make your original post you could have been done. If it takes you two hours then you are doing something seriously wrong.
This is a developer forum geared towards people who want to learn how things work, not just look for quick one click tools, and then get upset when things don't work out for them using said tools and people tell them to spend some time educating themselves. If people here spent more time actually learning instead of relying on quick fixes, then we would have to deal with hundreds of posts complaining on how OTA updates were failing because of asserts every time a new one came out.
And your last sentence makes no sense. Obviously there is a reason isn't there?
Sent from my Nexus 7 3G using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2019519
had the same problems
Just google fastboot files for n7, get sdk and pack files AND the recovery into the sdk tool folder.
Shift+right click -> start command here
Fastboot flash recovery recovery.img
Start tab abd sideload the SU.zip (google superuser)
Flash
Done ))
Did it yesterday no issues!
phonic said:
There is a big difference between memorizing commands and actually understanding what they mean. Your post made it very clear that in the "years" you've been doing it, you never possessed the latter.
It is not a complicated process. Unlock bootloader, run custom recovery, flash su zip. Voila. In the amount of time it took you to make your original post you could have been done. If it takes you two hours then you are doing something seriously wrong.
This is a developer forum geared towards people who want to learn how things work, not just look for quick one click tools, and then get upset when things don't work out for them using said tools and people tell them to spend some time educating themselves. If people here spent more time actually learning instead of relying on quick fixes, then we would have to deal with hundreds of posts complaining on how OTA updates were failing because of asserts every time a new one came out.
And your last sentence makes no sense. Obviously there is a reason isn't there?
Sent from my Nexus 7 3G using Tapatalk
Click to expand...
Click to collapse
Well said phonic. I prefer the manual way as well. It is always good to know what you are doing, but knowing how it works and learning something is always better.
I would much rather learn something than to have someone do it for me. If ever I need help and ask someone, they say I'll do it for you I say no, please show me how to do it!
Sent from my Nexus 7 using Tapatalk 2
kidujp said:
Use the THE GOOGLE NEXUS 7 TOOLKIT at : http://forum.xda-developers.com/showthread.php?t=1809195 and then use the files from here : http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650 and then start the tool and root. easiest solution I know.
If 4.2.2 doesn't show up in the device list, pick 4.2.1, worked fine for me.
Click to expand...
Click to collapse
You may receive an error message "ABD" is offline, in this case download the latest Android SDK manager and upgrade all USB drivers before using the toolkit again.
Sent from my Nexus 7 using xda app-developers app
phonic said:
How about instead on relying on a tool you know nothing about, you learn how your device works and how to root it manually? This way you aren't stuck dealing with problems like this in the first place.
I could understand the need/desire/etc. for special tools/kits on some branded and locked down devices. But the N7 is as open as it gets. If you have the SDK installed on your computer and a flashable SU zip, you could have your device unlocked and rooted in about 2 minutes.
Click to expand...
Click to collapse
Never ceases to amaze me how many pretentious pricks use XDA.... Reminds me of Apple snobs.
command line is the way to go
command line is the way to go m8!!
cheers,
geek endangered
Hey guys,
Right now I'm on a custom GPe rom (i9505G). I need to get back to Touchwiz.
You're probably wondering ... why...? Well, last night I bought a Fitbit Flex, and it's supported by GS4 (wireless syncing), http://www.fitbit.com/devices. Could it be because I'm on a custom rom?
Any feedback is appreciated.
Thanks,
gameriot
Yes, it doesn't work because you're on a custom Rom. Fitbit doesn't support it. You can flash the stock firmware in Odin.
Those fitbit's only work on stock or stock-based roms. There's some good ones in the Android Development section. Cheers
jd1639 said:
Yes, it doesn't work because you're on a custom Rom. Fitbit doesn't support it. You can flash the stock firmware in Odin.
Click to expand...
Click to collapse
I have a Mac, so I can't get Odin.
xBeerdroiDx said:
Those fitbit's only work on stock or stock-based roms. There's some good ones in the Android Development section. Cheers
Click to expand...
Click to collapse
I'll check it out. Could you link it?
gameriot said:
I have a Mac, so I can't get Odin.
I'll check it out. Could you link it?
Click to expand...
Click to collapse
Best Touchwiz-based ROM, in my opinion, right here:
http://forum.xda-developers.com/showthread.php?t=2313469
gameriot said:
I have a Mac, so I can't get Odin. I'll check it out. Could you link it?
Click to expand...
Click to collapse
#1. The TW rom that I find best for me is Shostock2.1 It's already very mature, stable and zero issues.
Here's the link if you want another option:
http://forum.xda-developers.com/showthread.php?t=2305752
#2. As to the Mac and no Odin thing. . . . I use a Mac (a couple of them, actually) and found that Heimdal can be made to work, but some folks feel it is not as user friendly/easy to use as Odin. (Btw, you should not need a custom driver to use Heimdal -its a mac and should see your phone w/o driver issues!)
I have used it, but maybe it's just my experience, there have been sometimes when you have everything set up correctly, Heimdal still seems to choke, or just not complete the task (or see the tar file that you want to use!).
Anyway, the newer versions seem better, please check out the current version of Heimdal and the Heimdal front end package?
Here is a Heimdal link in case you want to check: http://www.glassechidna.com.au/products/heimdall/.
The site should have instructions on how to get your file -the stock image or rom image that you want to load and make sure it's the right one and also that its in a form Heimdal can use. . .
Also, here is another very good, informative thread of someone's experience restoring his i337 using Heimdal! It might be helpful (and it is just a few posts down from yours
http://forum.xda-developers.com/show....php?t=2374441
#3. But even on a MAC you CAN use Odin! Odin generally works well and if Heimdal seems to complicated or you can't get it working, then you could open your options up significantly if you can either:
(1) use bootcamp and boot into a windows OS, or
(2) use Parallels/VM Ware Fusion and use windows in a virtual window.
Bootcamp is 100% windows running on your mac and is rock-solid, while the VM machine approach also is mature and pretty good, if occasionally temperamental...
If you can do this, then you can use Odin and work on phone with all the tools that most folks here have and use to good effect.
Good Luck!
markbc01 said:
#1. The TW rom that I find best for me is Shostock2.1 It's already very mature, stable and zero issues.
Here's the link if you want another option:
http://forum.xda-developers.com/showthread.php?t=2305752
#2. As to the Mac and no Odin thing. . . . I use a Mac (a couple of them, actually) and found that Heimdal can be made to work, but some folks feel it is not as user friendly/easy to use as Odin. (Btw, you should not need a custom driver to use Heimdal -its a mac and should see your phone w/o driver issues!)
I have used it, but maybe it's just my experience, there have been sometimes when you have everything set up correctly, Heimdal still seems to choke, or just not complete the task (or see the tar file that you want to use!).
Anyway, the newer versions seem better, please check out the current version of Heimdal and the Heimdal front end package?
Here is a Heimdal link in case you want to check: http://www.glassechidna.com.au/products/heimdall/.
The site should have instructions on how to get your file -the stock image or rom image that you want to load and make sure it's the right one and also that its in a form Heimdal can use. . .
Also, here is another very good, informative thread of someone's experience restoring his i337 using Heimdal! It might be helpful (and it is just a few posts down from yours
http://forum.xda-developers.com/show....php?t=2374441
#3. But even on a MAC you CAN use Odin! Odin generally works well and if Heimdal seems to complicated or you can't get it working, then you could open your options up significantly if you can either:
(1) use bootcamp and boot into a windows OS, or
(2) use Parallels/VM Ware Fusion and use windows in a virtual window.
Bootcamp is 100% windows running on your mac and is rock-solid, while the VM machine approach also is mature and pretty good, if occasionally temperamental...
If you can do this, then you can use Odin and work on phone with all the tools that most folks here have and use to good effect.
Good Luck!
Click to expand...
Click to collapse
I already tried hiemdall. It kept coming up with error whatever I did. Also my TWRP keeps failing when I'm trying to flash. I'm trying goomanager.
Sent from my GT-I9505G using Tapatalk 4
gameriot said:
I already tried hiemdall. It kept coming up with error whatever I did. Also my TWRP keeps failing when I'm trying to flash. I'm trying goomanager.
Sent from my GT-I9505G using Tapatalk 4
Click to expand...
Click to collapse
OK, I have been there! If Heimdall does not work, then:
a) find a windows machine for a while or
b) use your machine with bootcamp (if you're on a MBP) or
c) use your machine but install/open a virtual desktop (Parallels or VMware Fusion) to get a windows or linux environment.
Please BE CAREFUL when using goomanager (or Rom Manager, for that matter). These apps are useful, but they also are prone to suddenly creating havoc on the phone - usually when least expected . I have used both -but only very carefully and for limited functions. (I recently used GM to update my TWRP to the latest (I think 2.6?) -no issue --so try that at least!)
But for loading roms, initially loading recoveries or the like it is better to use the "manual" processes that we have available here.
Good Luck!
markbc01 said:
OK, I have been there! If Heimdall does not work, then:
a) find a windows machine for a while or
b) use your machine with bootcamp (if you're on a MBP) or
c) use your machine but install/open a virtual desktop (Parallels or VMware Fusion) to get a windows or linux environment.
Please BE CAREFUL when using goomanager (or Rom Manager, for that matter). These apps are useful, but they also are prone to suddenly creating havoc on the phone - usually when least expected . I have used both -but only very carefully and for limited functions. (I recently used GM to update my TWRP to the latest (I think 2.6?) -no issue --so try that at least!)
But for loading roms, initially loading recoveries or the like it is better to use the "manual" processes that we have available here.
Good Luck!
Click to expand...
Click to collapse
Thanks for the help. I got Touchwiz on my phone and got the sync to work but I just hate Touchwiz and went back by restoring my nandroid. Can't wait till they get Bluetooth 4.0 on custom roms, then it'll work.
Sent from my GT-I9505G using Tapatalk 4
Great..and if you still need a TW Rom, you still can switch launchers to Nova or something like that...
Then you hardly see the Samsung footprint...yet have the TW needed for the device..
Sent from my SAMSUNG-SGH-I337 using XDA Premium HD app