Related
Hi guys, I know there are a number of guides out there, but I found that a lot of people are running in to the bootloop issue by using certain methods to root (ie the "ADB Method").
So what is the current safest/best method to root?
Code:
fastboot oem unlock
fastboot flash recovery clockworkmodrecovery.img
(reboot recovery)
adb push su.zip /sdcard/
(reboot recovery)
(flash su.zip in recovery)
Don't bother with any of the one-click methods or anything like that. The hardest part is making sure you get your adb drivers set up correctly, and then you're good to go.
This is about as easy and safe as it gets-
lots of options to do what you need, including removing root.. Just install it and take a look around without hooking your phone up so you dont accidently do some damage.
http://forum.xda-developers.com/showthread.php?t=1400871
Thanks,
J
What codesplice said in post #2.
Thanks for the replies! Will try codesplice's method, is there a link/thread for the latest Samsung drivers? Is using Universal Naked Driver ok?
P.S there doesn't seem to be a way to rep/thank posts
qubic333 said:
Thanks for the replies! Will try codesplice's method, is there a link/thread for the latest Samsung drivers? Is using Universal Naked Driver ok?
P.S there doesn't seem to be a way to rep/thank posts
Click to expand...
Click to collapse
Yes those drivers will work. Make sure you boot your device into fastboot mode by hold both volume up and volume down an press the power button, then plug into you computer and install the drivers.
Then, when you unlock, don't forget that it will wipe your data/settings.
Sent from my Galaxy Nexus using Tapatalk
Personally I used the one-click method. I found this easy enough but you need to really pay attention when you use it or you won't understand what to do...
I did it the 'proper' way with my previous phone and I found it difficult but once you know what to do, you could easily do it again.
If this is your first time rooting a phone, I would do it the way that codesplice says, if not, take the easy route!
I just started the rooting process, and I actually didn't have to manually install any drivers.
I set my phone to fastboot mode, plugged it in and they installed automatically and fastboot recognized my phone (shows serial number in cmd when I launch fastboot.exe). Is this normal? or should I uninstall the drivers and manually install them?
Note: My device manager shows:
Android device
|__Android ADB Interface
Got root
I think windows now installs all the right drivers automatically..
qubic333 said:
Got root
I think windows now installs all the right drivers automatically..
Click to expand...
Click to collapse
It's supposed to, it just doesn't always work. Glad to hear you got Mission Accomplished though - and I hope you learned just a wee bit about the process along the way. Being at least familiar with fastboot and adb will help you significantly if you run into problems down the road.
codesplice said:
It's supposed to, it just doesn't always work. Glad to hear you got Mission Accomplished though - and I hope you learned just a wee bit about the process along the way. Being at least familiar with fastboot and adb will help you significantly if you run into problems down the road.
Click to expand...
Click to collapse
This was my first attempt at rooting and I'm glad it went smooth, I'm not a complete noob as I do have some Linux background, but I'm completely new to the smartphone thing so my knowledge of apps and ROMs and how they integrate in the device is very limited.
Thanks for the help guys, much appreciated! Great community you have hear
Hi all,
My OTA update kept failing so I attempted a manual update to 4.04.
I missed updating the boot.img file. I did the system, recovery and radio then relocked the bootloader.
When I turn it on, it stays on the google splash screen. When I go into bootloader mode and try recovery mode, I get the red triangle. My computer does not seem to be recognizing the phone, I get the error: device not found.
Is there something I might try?
Thanks in advance
AV8ing said:
Hi all,
My OTA update kept failing so I attempted a manual update to 4.04.
I missed updating the boot.img file. I did the system, recovery and radio then relocked the bootloader.
When I turn it on, it stays on the google splash screen. When I go into bootloader mode and try recovery mode, I get the red triangle. My computer does not seem to be recognizing the phone, I get the error: device not found.
Is there something I might try?
Thanks in advance
Click to expand...
Click to collapse
In fastboot mode (obviously), unlock the bootloader, flash the boot image, and leave the bootloader unlocked. Done.
Thanks for the quick repy efrant! A big question is how do I unlock the bootloader if my computer doesn't recognize the phone. I am getting "device not found" so I seem to be unable to unlock the bootloader in the first place.
AV8ing said:
Thanks for the quick repy efrant! A big question is how do I unlock the bootloader if my computer doesn't recognize the phone. I am getting "device not found" so I seem to be unable to unlock the bootloader in the first place.
Click to expand...
Click to collapse
So your GNex is booted in fastboot mode and your computer does not recognize it? If this is the case, it is likely a driver issue, and you should re-install.
It is normal that your GNex is not recognized by your computer when booted not in fastboot mode, when you can't boot.
efrant said:
So your GNex is booted in fastboot mode and your computer does not recognize it? If this is the case, it is likely a driver issue, and you should re-install.
It is normal that your GNex is not recognized by your computer when booted not in fastboot mode, when you can't boot.
Click to expand...
Click to collapse
Hey efrant ^^ I'll sort it out ^^ (if you don't mind)
Dude, chec my sig, all the drivers and tutorials needed, can be found in the Win8 thread.
Follow that tut. then the phone should be recognized. Then erase the phone With:
Code:
fastboot erase system
fastboot erase boot
fastboot erase recovery
This ensures, that the flash is successful. If you don't erase first, it's likely, that the phone won't correctly write the files.
Then flash the files, with these codes:
Code:
fastboot flash boot (Always do this first) <Fille directory\file name.img>
fastboot flash system <Fille directory\file name.img>
fastboot flash recovery <Fille directory\file name.img>
DO NOT ERASE/FLASH userdata!! Do that, and you WILL lose ALL of your data!
If you want, I can help you, with tamviewer. I've helped a few people, this way It has always worked
Normally it does recognize the phone, but it doesn't seem to since I messed this up. I will try to re-install the drivers to see if that works. It is in fastboot mode, I hear the tone from the computer that something has connected when I reboot the fastboot, but it doesn't get recognized.
AV8ing said:
Normally it does recognize the phone, but it doesn't seem to since I messed this up. I will try to re-install the drivers to see if that works. It is in fastboot mode, I hear the tone from the computer that something has connected when I reboot the fastboot, but it doesn't get recognized.
Click to expand...
Click to collapse
Go into the dev manager, and look for: Android 1.0
If you see that, then Update devuice drivers -> Select from a list -> Samsung ADB Interface
That should do the trick
Thanks much, familyguy59. I'll try this now.
AV8ing said:
Thanks much, familyguy59. I'll try this now.
Click to expand...
Click to collapse
No prob. That's what some of us, have made to a "quest" Instead of flaming n00bs, help them, and make sure, they find their place, in this community
Thanks so much efrant and familyguy59! There were a couple of bumps in the road, but I flogged my way through them. I thought I had bricked my phone for sure. Once again, thanks so much.
AV8ing said:
Thanks so much efrant and familyguy59! There were a couple of bumps in the road, but I flogged my way through them. I thought I had bricked my phone for sure. Once again, thanks so much.
Click to expand...
Click to collapse
No prob, dude! That's what we're here for
familyguy59 said:
No prob. That's what some of us, have made to a "quest" Instead of flaming n00bs, help them, and make sure, they find their place, in this community
Click to expand...
Click to collapse
+1 to this guy XD
Sent from my Galaxy Nexus using XDA
jzero88 said:
+1 to this guy XD
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
And the "xD" was neccessary... in what way? ^^ It is true, though.
If you aren't feeling the same, then it's your thing. I'm here, to help others, and help them understand, what, what features do, and what is needed, to do what....
Was trying to get my Gnex back to factory trying every way possible to use adb and could get the files to find their way to my phone. So finally i said hell with it and Second try fails and i unplug it to try and turn it back on and i get a screen with a phone and computer and a yellow triangle in the middle of both. Will not boot into anything. But when i plug it into my computer it will make the noise that something is plugged in and i try odin again and i can see the blue bar on my phone like its trying to download something to it, So i dont know where to go from here. Any way in hell i could take it to Verizon and have them do a factory reset? Any help would be appreciated.
Can you get into fastboot ? And do you have drivers installed?
Sent from my GNexus
ray3andrei said:
Can you get into fastboot ? And do you have drivers installed?
Sent from my GNexus
Click to expand...
Click to collapse
To be honest i lack the knowledge of knowing everything unless i am following a guide on how to do things. So if i plug my phone in and here the sound it makes to connect and pull up a command prompt i type in adb fastboot and it brings up this long list of commands. Is this what you are talking about?
aaronstrong1988 said:
To be honest i lack the knowledge of knowing everything unless i am following a guide on how to do things. So if i plug my phone in and here the sound it makes to connect and pull up a command prompt i type in adb fastboot and it brings up this long list of commands. Is this what you are talking about?
Click to expand...
Click to collapse
Type adb devies and see if anything comes back.
drake90001 said:
Type adb devies and see if anything comes back.
Click to expand...
Click to collapse
yes list of devices came back so that works
aaronstrong1988 said:
yes list of devices came back so that works
Click to expand...
Click to collapse
What device names came back? Did it actually list any serial numbers?
drake90001 said:
What device names came back? Did it actually list any serial numbers?
Click to expand...
Click to collapse
after i typed in adb devices it came back with
*daemon not running. starting in now on port 5037*
*daemon started successfully*
List of devices attached
and thats all
Then your device is not recognized by adb. So it's not working. If it was it would've shown a serial #.
063_XOBX said:
Then your device is not recognized by adb. So it's not working. If it was it would've shown a serial #.
Click to expand...
Click to collapse
how do i get it to show my serial number?
aaronstrong1988 said:
how do i get it to show my serial number?
Click to expand...
Click to collapse
You install the correct driver
Sent from my Galaxy Nexus using Tapatalk 2
Use the Galaxy Nexus tool. It is fantastic.
It installs all drivers and really is helpful and straight forward.
Sent from my Galaxy Nexus using xda premium
Yupp, unfortunately the drivers are probably the hardest part.. I never managed to get them working on first try...
Anyhow, download the latest Android sdk and have it download the Usb Drivers section if you didn't already. Then try installing those drivers. Remember you have to reboot your pc after each try (trust me, there will be multiple tries) otherwise it won't work.
Once you got the drivers installed get back to us. And don't panic, your phone's fine.
Sent from my Galaxy Nexus
Lazer Bear said:
Yupp, unfortunately the drivers are probably the hardest part.. I never managed to get them working on first try...
Anyhow, download the latest Android sdk and have it download the Usb Drivers section if you didn't already. Then try installing those drivers. Remember you have to reboot your pc after each try (trust me, there will be multiple tries) otherwise it won't work.
Once you got the drivers installed get back to us. And don't panic, your phone's fine.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
i hope so i will uninstall sdk and try it all over
OK so I am using windows 8.1; have searched everywhere and tried just about everything imaginable but I still cant get fastboot to work with my HTC One. The phone is recognized fine when I type adb devices on the main screen, however, when I boot into fastboot the phone is simply not recognized by Windows any longer. I get the message USB DEVICE NOT RECOGNIZED. I am currently looking to update my HBOOT which is 1.54.0000 and was under the impression that I need to do a fastboot flash to do this. I am currently running Viper Rom 5.8.
I am desperate here and am willing to make a donation to the person who solves my issue.
MightyChigger said:
OK so I am using windows 8.1; have searched everywhere and tried just about everything imaginable but I still cant get fastboot to work with my HTC One. The phone is recognized fine when I type adb devices on the main screen, however, when I boot into fastboot the phone is simply not recognized by Windows any longer. I get the message USB DEVICE NOT RECOGNIZED. I am currently looking to update my HBOOT which is 1.54.0000 and was under the impression that I need to do a fastboot flash to do this. I am currently running Viper Rom 5.8.
I am desperate here and am willing to make a donation to the person who solves my issue.
Click to expand...
Click to collapse
You need a Windows 7 pc.
Chilidog said:
You need a Windows 7 pc.
Click to expand...
Click to collapse
Come on. There are other choices.
Download Ubuntu. You can run it from an installation medium without actually installing it.
Chilidog said:
You need a Windows 7 pc.
Click to expand...
Click to collapse
well unfortunately for me, I dont have one... can this be done on Windows 8.1?
jpradley said:
Come on. There are other choices.
Download Ubuntu. You can run it from an installation medium without actually installing it.
Click to expand...
Click to collapse
Don't know anything about Ubuntu....would probably create more issues trying to figure this out. One way or another, I need to get fastboot working on my machine right??
MightyChigger said:
Don't know anything about Ubuntu....would probably create more issues trying to figure this out. One way or another, I need to get fastboot working on my machine right??
Click to expand...
Click to collapse
After sending to HTC to have the camera sensor fixed I could no longer get fastboot to work and I had to suffer with stock for a couple of months. I finally resolved this by updating sdk having read recent Windows 7 updates could be the culprit, maybe it was a usb driver update, but was still having issues.I read to try turning usb debug off and on which in the end may have been all that was required. Finally back to S-off running Viper 6.1 which team Viper deserves major props on for a brilliant job. BTW I'm on Windows 7 Ultimate with usb 3 ports only.
Go here and watch the first video: http://forum.xda-developers.com/showthread.php?t=2703585
Hi guys, I want to upgrade to android L now but i have to upgrade to the new bootloader. I am very unfamiliar with fastboot so I could do with some help.
I have downloaded the zip with everything I need in it. I know there are a few things I need to do before I can upgrade, i just dont know what these things are
I did just try it without doing anything (plugging in my tablet, booting to fastboot and opening the batch file but it just came up with "Waiting for device")
Im pretty sure its something to do with the drivers but currently I am clueless.
PS I made this thread because it was instructed for me to not ask for help on the thread for the rom and Im pretty sure a lot of other people are having the same problem as me. Any help would be appreciated, thanks for your time
I believe first thing you need to do is unlock your bootloader , I just did that.. now im not sure where to go after that but first video in this thread and toolkit helps alot plus it helps you get your drivers setup.. I had issues with 8.1 x64 so I switched to a windows 7 computer and it worked perfectly
Oh yeah I forgot to mention. I am already rooted and the boot loader is unlocked. I used the wugfresh toolkit and set up the drivers again to how I think they should be and when it went through the testing procedure, it fully connected to the device, rebooted it into fast mode and then turned it back on again.
It just doesn't respond to the batch file that was in the zip
I have the same problem. I run the .bat file, and it just hangs on waiting for device. My bootloader is unlocked, and I have a custom ROM on my device. I put it into fastboot mode too, and it won't recognize it.
Did you try running the bat file as administrator? Or try a different usb port?
jstn76rs said:
Did you try running the bat file as administrator? Or try a different usb port?
Click to expand...
Click to collapse
Actually I didn't. That might be worth trying. Cheers
EDIT: Well that kind of worked, but it just came up with "fastboot is not a recognised internal/external command". Any ideas now?
Just look here and use twrp:
http://forum.xda-developers.com/nex...shable-factory-image-zips-android-5-t2939599/
James_Feltham said:
Actually I didn't. That might be worth trying. Cheers
EDIT: Well that kind of worked, but it just came up with "fastboot is not a recognised internal/external command". Any ideas now?
Click to expand...
Click to collapse
you need to run the command from adb installed folder, these exe's comes with android SDK.
James_Feltham said:
Hi guys, I want to upgrade to android L now but i have to upgrade to the new bootloader. I am very unfamiliar with fastboot so I could do with some help.
I have downloaded the zip with everything I need in it. I know there are a few things I need to do before I can upgrade, i just dont know what these things are
I did just try it without doing anything (plugging in my tablet, booting to fastboot and opening the batch file but it just came up with "Waiting for device")
Im pretty sure its something to do with the drivers but currently I am clueless.
PS I made this thread because it was instructed for me to not ask for help on the thread for the rom and Im pretty sure a lot of other people are having the same problem as me. Any help would be appreciated, thanks for your time
Click to expand...
Click to collapse
What version of Windows are you running?? 8.1 is troublesome for drivers. I've had better results from Windows 7
With the nexus 7 you will want to install the kit from http://forum.xda-developers.com/nex...wugs-nexus-root-toolkit-v1-9-3-nexus-t2940401
this is the easy way to get adb fastboot and some other utilities
you can then go to the wugfresh development/data directory
open a cmd window
boot your n7 to the bootloader ( Power + Vol Down)
connect it to your computer.
in the command window
type fastboot devices
look for your nexus serial number ( should show on the bootloader screen on the nexus)
if you don't get a device showing... you will have to re-do your drivers installation......
try using the Wugfresh tool kit.
if you do see your device
use the windows bat file in the Bootloader update from Scrosler's thread.