Develop Bugs

[HOW TO] Root only STOCK/No Custom Recovery

Taken FROM http://rootzwiki.com/topic/11732-galaxy-nexus-root-procedure-broken-adb-method-dont-use/
With the big change of YOU WILL BOOT LOOP WAIT FOR ADB TO RESPOND and push all the commands then pull the battery and disconnect your USB cable and reboot normal you should have perm root!
**As always RootzWiki nor myself are responsible if something goes wrong. Root your phone at your own risk with the understanding it will void your warranty and there is always a chance of something going wrong.**
*This method WILL WIPE YOUR DATA*
First download Galaxy Nexus FYA Root Package and extract it to c:\gnexroot (for the purposes of this guide)
Also if you wipe and format remember to re-enable Debug mode before restarting processes listed above.
Method
1. First, navigate to C:\gnexroot and install the Samsung drivers (Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe)
1. If those drivers dont work download pdanet from here http://forum.xda-dev....php?p=19709279 and let pdanet install the drivers for you. Worked for some of us.
2. With the phone turned OFF, hold VOLUME UP + VOLUME DOWN and power the phone on. This will put you in bootloader mode.
3. Navigate again to C:\gnexroot, and hold SHIFT on your keyboard, and right click in the white space. Then, click 'Open command window here'
4. In the command prompt, type:
fastboot oem unlock
You will be prompted to confirm that you wish to unlock the bootloader. You do, of course.
5. Once the bootloader has been unlocked, it's time to boot up the device using the insecure boot.img (ro.secure=0 set in the ramdisk). This essentially means you have permanent root for the duration of this boot session. In order to boot up using that boot image, simply type:
fastboot boot boot.img
Don't expect to see anything wildly different during the boot process - it will boot as normal.
6. Once the phone has booted, in the command prompt window, type the following commands, pressing enter after each line:
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
Again I did NOT write these steps nor did I take credit for this procedure. My goal was to have all this information easy to access here so people don't brick their new device
Edit:
If you get stuck at the google logo and cannot push adb commands, pull the battery and usb cable then reinsert and reboot. If this doesn't work Reboot into recovery and wipe everything and start over.
12/17/2011
If you do a factory restore remember to boot at least once after and re-enable debug mode.

anyone had the issue of not being able to unlock the bootloader?
i ran the command "fastboot oem unlock" and it just sticks at the response: <waiting for device>
but nothing shows on my phone.

aldouse said:
anyone had the issue of not being able to unlock the bootloader?
i ran the command "fastboot oem unlock" and it just sticks at the response: <waiting for device>
but nothing shows on my phone.
Click to expand...
Click to collapse
I would guess your computer is not recognizing the device. Try installing the drivers and connecting the phone to the computer while it is in normal mode not the bootloader. It should install the drivers correctly that way and your computer will then recognize it when you boot into the bootloader and the commands should work.

yea... you are right... it was the samsung drivers not fully loading. re-installed the drivers then doing a windows update showed that there's a new set of samsung drivers on the windows update that needed to be installed. that did the trick.

The superboot method worked just fine for me.
Sent from my Galaxy Nexus using Tapatalk

SomeGuyDude said:
The superboot method worked just fine for me.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
same though I had a bootloop but it did root itself.
Sent from my Galaxy Nexus using Tapatalk

aldouse said:
anyone had the issue of not being able to unlock the bootloader?
i ran the command "fastboot oem unlock" and it just sticks at the response: <waiting for device>
but nothing shows on my phone.
Click to expand...
Click to collapse
You must be in recovery mode. Turn the phone off, press volume up and down as well as power. Keep it there until you're in recovery and then unlock.
Sent from my Galaxy Nexus using Tapatalk

innov8ion said:
You must be in recovery mode. Turn the phone off, press volume up and down as well as power. Keep it there until you're in recovery and then unlock.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Its not recovery mode, but fastboot mode. If you are in recovery fastboot won't be recognized. Looks like he got it fixed by checking his drivers.

can you also use this method for a Verizon Galaxy Nexus???
http://forum.xda-developers.com/showthread.php?t=1392310
is there any difference?

Superboot method actually does the same thing as this method from what I read just one is automatic and one is manual.
Being I didn't see anyone else rooting from Verizon I took the time to figure out a manual method so i can verify each step and figure out issues if I ran in to any. With Superboot its either it works or it doesn't there is no playing with procedures.
This should work for other carriers to, I can only verify it for Verizon though.

I get past <adb reboot bootloader> just fine but then when I do a <fastboot oem unlock> it just says "waiting for device" forever. everything is installed but under my drivers it says;
"Android 1.0" drivers not installed.
plz someone help, ive searched all over the net but only found help for HTC phones and 2007 old posts.
edit: I am in "Fastboot mode"

Update the Samsung ADB driver under device manager while you are sitting in the bootloader. I'm bootlooping after pushing the boot.img

got it working, "Note: 1" under this guide fixed it.
http://forum.xda-developers.com/showthread.php?t=1392310
thanks again XDA!!

GOod. Mine is still bootlooping back to the Google screen with a lock on it.
Booted into recovery, formatted. At least i can boot up now.

fatsix said:
GOod. Mine is still bootlooping back to the Google screen with a lock on it.
Booted into recovery, formatted. At least i can boot up now.
Click to expand...
Click to collapse
Sounds like you didn't successfully unlock your bootloader. Have you resolved this?

Done and rooted. Pushing APK's now.
I would recommend doing a full wipe first. I think something got corrupted during the forced wipe when unlocking.
After wiping, I started over. Unlocked and flashed the boot.img. Got a full normal reboot. Flashed it a second time, and it stayed at the google screen and i could connect to it with ADB. Pushed all the commands and rebooted. Works great.
Thank you.

I assume you need to have adb installed before doing this? Or do the command prompts perform from windows?
Sent from my SCH-I500 using Tapatalk

I had it previously installed. If you download the zip. its already in there, just run it right from the directory you unzip it from.

I would like to return my phone to stock. Locked, unrooted, and available for OTAs. Is there a way to do this yet?

craighwk said:
I would like to return my phone to stock. Locked, unrooted, and available for OTAs. Is there a way to do this yet?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1394051
After you complete that Run:
fastboot oem unlock
From the main instructions and simply relock it.

[Video] How to Unlock n Root GNex with Superboot

Credit for the written tutorial goes to sbenson1226
What do I need?
Superboot : DOWNLOAD
Drivers: You will need to install this driver.
The Process:
Download the above files and install the driver. For the driver, it installs Pdanet on both your computer and phone. Follow the directions carefully. Pdanet will be wiped from your phone once you run Superboot. After the driver is installed, feel from to uninstall Pdanet from your computer – the driver will remain.
Extract the contents of Superboot and rename the folder “root.” Place this folder into C:\ (you may be asked for admin privileges).
Power down the phone.
Connect the phone to your computer.
Boot the phone into the bootloader by simultaneously holding Volume Up + Volume Down + Power.
Open up the command prompt in Windows:
Click Start Menu, then in the search bar type: cmd (this will open the command prompt);
Type the following: cd C:/
Then type the following: cd root
The next step will unlock your bootload - this will wipe all data on your device.
Type the following, in the command prompt: fastboot-windows oem unlock
You will receive a warning about unlocking. Use the volume keys to select an option and use the power button to confirm.
Your bootloader will now say: Lock State – Unlocked (near the bottom) as well as “Fastboot Status – Okay”
Now, to root your device, simply double click: install-superboot-windows.bat that you originally placed in the root folder in step 2.
Your phone should reboot on its own.
Be patient while it reboots, and don’t worry – first boot may take up to 5 minutes.
After phone set up, confirm Superuser app in your app tray.
All credit for this tutorial goes to:
Evostance and
Paul O’Brien
Useful root apps:
Busybox
Rom Manager
Titanium Backup
Root Explorer
Questions?
The above method unlocks your bootloader AND roots your device.
You do not need ADB.
This does not put a custom recovery on your phone.
This does not put a custom rom on your phone.
Yes, your phone is still stock.
Yes, you will still receive OTA’s from Google/Verizon.
This only puts Superuser on your phone, you need to install busybox yourself.

Question, when using superboot, is there a way to unroot the root if needed? If so do you have the steps to unroot?
Thanks,
Keith

CDMA problem
I have a brand new Verizon Galaxy nexus. I have the bootloader unlocked but everytime I tried to do the boot.img step it would just stay on the Google screen forever. I did an adb logcat and I could see it failing and looping over and over again.
Any idea what I should try? Could the update to 4.02 have caused this?
Thanks,
Master K

FlagAZ said:
Question, when using superboot, is there a way to unroot the root if needed? If so do you have the steps to unroot?
Thanks,
Keith
Click to expand...
Click to collapse
This is something I would like to know too.

Its been a long while since I've done Android mods haha, If I root and stay on stock rom with CWM recovery, Will I still be able to do the 4.0.3 OTA? or will the recovery not be able to apply the update?

If you have clockworkmod installed with your stock rom. Once you restart the phone it will wipe clockworkmod and install back the stock recovery.
Sent from my Nexus One using xda premium

FlagAZ said:
Question, when using superboot, is there a way to unroot the root if needed? If so do you have the steps to unroot?
Thanks,
Keith
Click to expand...
Click to collapse
Yes you can unroot by flashing the system image... it requires adb check out my channel , I'll try to post the video here asap
Sent from my Galaxy Nexus using XDA App

Master K said:
I have a brand new Verizon Galaxy nexus. I have the bootloader unlocked but everytime I tried to do the boot.img step it would just stay on the Google screen forever. I did an adb logcat and I could see it failing and looping over and over again.
Any idea what I should try? Could the update to 4.02 have caused this?
Thanks,
Master K
Click to expand...
Click to collapse
This process wipes the data.. did you pull USB during the process... either way go into boot loader and lock boot loader by typing OEM lock instead of OEM unlock and try again this time don't pull the USB cable
Sent from my Galaxy Nexus using XDA App

mikeacela said:
Its been a long while since I've done Android mods haha, If I root and stay on stock rom with CWM recovery, Will I still be able to do the 4.0.3 OTA? or will the recovery not be able to apply the update?
Click to expand...
Click to collapse
You will still be able to accept ota
Sent from my Galaxy Nexus using XDA App

owenbeals said:
This process wipes the data.. did you pull USB during the process... either way go into boot loader and lock boot loader by typing OEM lock instead of OEM unlock and try again this time don't pull the USB cable
Click to expand...
Click to collapse
I did not pull the USB. I did it twice so I know the lock unlock sequence fixes the phone.
I did the unlock without issue and then when I do install-superboot-windows.bat the phone reboots, I get the Google with the unlocked padlock and there it sits. Well past 5min. I did an adb logcat and I can see it is stuck in a bootloop so I pull the battery and lock and unlock again. I rebooted and the phone started up as if new. As I said i went through all this twice (never pulling the USB) and the same result.

I followed this guide letter by letter and it worked perfectly. BTW I have the LTE nexus

owenbeals said:
This process wipes the data.. did you pull USB during the process... either way go into boot loader and lock boot loader by typing OEM lock instead of OEM unlock and try again this time don't pull the USB cable
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
never mind

I downloaded both links,
installed the drivers,
made sure the newly files (superboot) where in a file named root on the C:\
rebooted phone in to fastboot, then plugged it into the computer
started command prompt
made sure I was in the C:\root directory
typed in fastboot-windows oem unlock
Alls I get is a massage saying "waiting for device" (yes the device is hooked up to the computer via USB)
the instructions mention pdanet... I never saw that install anywhere so maybe i am missing a step

I can not get the drivers i downloaded from the link to work. It took forever to run the exe and install them, like an hour, and then the install was unsuccesful.

Epicrean said:
Alls I get is a massage saying "waiting for device" (yes the device is hooked up to the computer via USB)
Click to expand...
Click to collapse
Had to boot the phone back in to the bootloader and rerun the install-superboot-windows.bat. Then my phone rebooted right away. Been sitting on the Google screen for a while...past 5 minutes...so hopefully it will go through.
EDIT: Waiting 15 minutes and phone was still stuck on the black screen with the while Google logo. Pulled battery and phone booted and was rooted. Odd....

is it just me or the download link is down as of 12/18/11?

Followed instructions (although I got the driver from elsewhere, so didn't need the PDAnet files).
Installed loads of apps and such. Turned phone off, then on again. After I rebooted though, my phone appears not to be rooted anymore. Superuser doesn't seem to do anything (although it's on the phone) and Root Explorer says it is denied root permissions from Superuser.
Downloaded Superuser fix from the market which says my phone isn't rooted.
If I just type the "install blah de blah" command again (IE, missing out the unlock oem as the bootloader should still be unlocked), then will it wipe my phone? Don't really fancy installing all the apps again.
Will this then be permanently rooted?

owenbeals said:
What do I need?
Superboot : DOWNLOAD
Drivers: You will need to install this driver.
The Process:
Download the above files and install the driver. For the driver, it installs Pdanet on both your computer and phone. Follow the directions carefully. Pdanet will be wiped from your phone once you run Superboot. After the driver is installed, feel from to uninstall Pdanet from your computer – the driver will remain.
Extract the contents of Superboot and rename the folder “root.” Place this folder into C:\ (you may be asked for admin privileges).
Power down the phone.
Connect the phone to your computer.
Boot the phone into the bootloader by simultaneously holding Volume Up + Volume Down + Power.
Open up the command prompt in Windows:
Click Start Menu, then in the search bar type: cmd (this will open the command prompt);
Type the following: cd C:/
Then type the following: cd root
The next step will unlock your bootload - this will wipe all data on your device.
Type the following, in the command prompt: fastboot-windows oem unlock
You will receive a warning about unlocking. Use the volume keys to select an option and use the power button to confirm.
Your bootloader will now say: Lock State – Unlocked (near the bottom) as well as “Fastboot Status – Okay”
Now, to root your device, simply double click: install-superboot-windows.bat that you originally placed in the root folder in step 2.
Your phone should reboot on its own.
Be patient while it reboots, and don’t worry – first boot may take up to 5 minutes.
After phone set up, confirm Superuser app in your app tray.
All credit for this tutorial goes to:
Evostance and
Paul O’Brien
Useful root apps:
Busybox
Rom Manager
Titanium Backup
Root Explorer
Questions?
The above method unlocks your bootloader AND roots your device.
You do not need ADB.
This does not put a custom recovery on your phone.
This does not put a custom rom on your phone.
Yes, your phone is still stock.
Yes, you will still receive OTA’s from Google/Verizon.
This only puts Superuser on your phone, you need to install busybox yourself.
Click to expand...
Click to collapse
Hmmm, this tutorial looks strikingly similar to the one I created at DroidForums. A little credit would be nice - or please completely rewrite it. Thanks.
Sent from my Galaxy Nexus using XDA App

The driver failed to install on my phone...when I reboot into my bootloader it looks a bit different from in the video. Mine just has an android and it says start above it. The oem unlock command fails to do anything as well.
Why is nothing ever simple?
Does your phone need to be connected when you install the samsung drivers on it? Or does it install these drivers after booting into the bootloader?
When I install the samsung drivers on my computer with the phone connected, it says the following:
Android phone: No drivers found
Samsung Mobile USB Composite Device: Ready to use
Samsung Mobile MTP Device: Failed
Samsung Android ADB Interface: Ready to use
When I hold the volume buttons and power it on now, it just goes straight to the google logo...not even getting the android logo with the start option anymore. I think I might have accidentally uninstalled the ADB drivers in my device manager because I saw 2 copies and thought I installed it twice...

Try the PDA net application on your comp, it will properly install the Samsung drivers so you can adb
Sent from my Galaxy Nexus using xda premium

[HOW TO][CDMA] Manually Root Galaxy Nexus

>>GUIDE<<
This guide will work to root the stock ROM. None of that automated stuff where you don't know what's going on. This guide will explain it step by step and you will actually know what's going on when you root a ROM
If you want to boot into a recovery image, simple use:
fastboot boot recovery.img
Note: You'll have to find the correct recovery.img file for your phone!!

Ok i unlocked the bootloader but when I input step 2 It says error: device not found? Everything worked normally?? What gives?

kp432 said:
Ok i unlocked the bootloader but when I input step 2 It says error: device not found? Everything worked normally?? What gives?
Click to expand...
Click to collapse
Make sure you have the correct drivers installed and you have USB debugging enabled.
If you are on Win 7 x64, hook up your phone to your computer, boot into the bootloader, and check out Device Manager (right click My Computer, Properties, Device Manager).
If you see in "Other Devices" a device called Android 1.0 (I can't remember off the top of my head), right click it, update drivers. Tell Windows you want to browse for the drivers, click to see the list of drivers you already have installed, and scroll down to find the Samsung Android Phone or whatever it's called.

kp432 said:
Ok i unlocked the bootloader but when I input step 2 It says error: device not found? Everything worked normally?? What gives?
Click to expand...
Click to collapse
your drivers probably arent installed properly. download PDA net and use it on your computer and it should install the drivers for you

Can't gain root after unlocking bootloader
xx

kp432 said:
Ok i unlocked the bootloader but when I input step 2 It says error: device not found? Everything worked normally?? What gives?
Click to expand...
Click to collapse
Same here. And I did install PDAnet prior to attemping this so that I would have the correct drivers.

I have tried this on 2 different computers and I keep getting the same error. When I try to do "adb root" it will start daemon and then it will fail.
It keeps saying "Error: Device Not Found"

same error as everyone else..
"adbd cannot run as root in production builds"
I noticed my bootloader says unlocked...is that good?

DenzelChurchill said:
Hey guys,
I can't seem to boot straight into boot.cdma.img. Soon after this command, the phone boots (doesn't make it to the ROM boot animation), then reboots, then goes into the ROM. When I try "adb root" I get the "production" error message. I have a Verizon CDMA/LTE Galaxy Nexus and I'm connecting it to Mac OS X. Thoughts?
Detailed explanation below for those curious...
Thanks everyone!
1. Boot phone into bootloader
2. Terminal: fastboot oem unlock (say yes to prompt, then return to bootloader)
3. Terminal: fastboot boot.cdma.img
4. Phone reboots, but doesn't make it to the ROM boot animation before it reboots again (I know this because it goes black for a second and vibrates slightly)
5. Phone boots into stock ROM, where I quickly dismiss all prompts and move to the settings menu to enable USB debugging
6. Terminal: adb root (Error message: "adbd cannot run as root in production builds")
7. I confirm that I don't have root by loading up Superuser and attempting to update binaries, where I'm told that it has failed the "Gain root..." step.
EDIT: Added phone / computer details.
Click to expand...
Click to collapse
remember, that command is supposed to be
fastboot boot boot.cmda.img

xx

hello I have unlocked the boot loader and rooted, installed cwm, my only problem is I do not have any 4g connectivity , I checked to see if its on lte cdma it is , powered off phone , battery pull ,reboot phone 4g shows up but will not stay connected. dont know if this has anything to do with root or what but my t-bolt has had 4g all day and nexus is right beside it. any ideas, thanks

Seaman24 said:
hello I have unlocked the boot loader and rooted, installed cwm, my only problem is I do not have any 4g connectivity , I checked to see if its on lte cdma it is , powered off phone , battery pull ,reboot phone 4g shows up but will not stay connected. dont know if this has anything to do with root or what but my t-bolt has had 4g all day and nexus is right beside it. any ideas, thanks
Click to expand...
Click to collapse
I know their network was down from around 6am EST to Noon EST. And last night on some cities on the west coast.
I actually lost 3g data for that time as well.

DenzelChurchill said:
Hey guys,
1. Boot phone into bootloader
2. Terminal: fastboot oem unlock (say yes to prompt, then return to bootloader)
3. Terminal: fastboot boot boot.cdma.img
4. Phone reboots, but doesn't make it to the ROM boot animation before it reboots again (I know this because it goes black for a second and vibrates slightly)
5. Phone boots into stock ROM, where I quickly dismiss all prompts and move to the settings menu to enable USB debugging
6. Terminal: adb root (Error message: "adbd cannot run as root in production builds")
7. I confirm that I don't have root by loading up Superuser and attempting to update binaries, where I'm told that it has failed the "Gain root..." step.
Click to expand...
Click to collapse
I had the exact same problem where the phone reboots before it loads into boot.cdma.img, followed by the "production builds" error (as in your steps 4-6)
What worked was going back to bootloader, and running "fastboot boot boot.cdma.img" again
It loaded very quickly. When i ran "adb root" it actually said that the device was already rooted or something similar. The proceeding steps went very smoothly.
Hope this helps
---------- Post added 22nd December 2011 at 12:05 AM ---------- Previous post was 21st December 2011 at 11:59 PM ----------
aznxk3vi17 said:
Make sure you have the correct drivers installed and you have USB debugging enabled.
If you are on Win 7 x64, hook up your phone to your computer, boot into the bootloader, and check out Device Manager (right click My Computer, Properties, Device Manager).
If you see in "Other Devices" a device called Android 1.0 (I can't remember off the top of my head), right click it, update drivers. Tell Windows you want to browse for the drivers, click to see the list of drivers you already have installed, and scroll down to find the Samsung Android Phone or whatever it's called.
Click to expand...
Click to collapse
I can confirm this. You need to be in bootloader to see the device driver error. It will show a Android 1.0 with an exclamation mark over it. I believe the device is a labeled as a storage drive or something similar (its not under "Android Phone")
Follow the above instructions to apply the SAMSUNG drivers

Just wanted to say thanks for this. I am fairly new to this but this seemed a lot less complicated.
Just one thing, I couldn't figure out why I couldn't run the adb root command until reading some more and finding that I had to enable USB debugging then reboot again. Hope that helps someone.
Thanks again all.
Also, how do you unroot the phone after using this method?

How to do on mac
I am new to doing this on Mac. I know that it is kind of the same but what is different when I am doing this on a Mac as apposed to a PC?

numbskill said:
I had the exact same problem where the phone reboots before it loads into boot.cdma.img, followed by the "production builds" error (as in your steps 4-6)
What worked was going back to bootloader, and running "fastboot boot boot.cdma.img" again
It loaded very quickly. When i ran "adb root" it actually said that the device was already rooted or something similar. The proceeding steps went very smoothly.
Hope this helps
Click to expand...
Click to collapse
any idea why this happens? I rooted 3 phones with this method. The first one went smoothly. The second two went through the reboots. In one case, I actually loaded an odin to get it back to the boot animation, otherwise I was stuck on the unlocked Google screen. Would be nice to know what I might be doing before I root someone else's phone.

xx

Does following this guide erase your phone? When it says boot the CDMA.img, I'm thinking it's going to replace the already installed image with a stock version that has root.
Or am I completely missing the mark here? I read what the guide wrote, but it doesn't really say if it's going to replace my stock image or what's going to happen.

BUMP?
The file linked on that thread is 404'd. Also, does this work on 4.0.4? I want to root but learn at the same time so I want to avoid using the toolkit. Does the toolkit work on 4.0.4? Thanks.

i ran into a little problem idk what it is this is the first time i run into this problem. i enter the first command prompt into terminal i think its
./fastboot-mac oem unlock and all it says is:
./fastboot-mac: operation not permitted
i don't know what I'm doing wrong help??

Stuck in an infinite loop

Model: GT-I9250T
Original Android version 4.04.
Root method: Gained root without having to unlock or overwrite the vanilla boot-loader and used OTA RootKeeper to backup su.
Long story short: My phone recently updated to 4.2.1 OTA. I restored root using OTA RootKeeper without issue. However when I went to restore The LBE Privacy app service, it caused my Nexus to enter a loop the moment it finishes booting and the lock screen appears.
Behavior:
After booting to the lock screen, the screen flashes and goes black then gets back to desktop and starts all over again in a loop. Once it does that about 3 or 4 times, it'll eventually get to a totally black screen except for the Android robot guy lying down with his belly open and an exclamation mark coming out. It'll then sit like that for about a minute and then the phone will reboot from scratch and the whole process repeats.
Apparently i'm not the only one either: url = badappreviews.com/apps/23315
From the linked site it looks like someone fixed it by using clockworkmod. However I don't see how that's possible as there is no way to enable usb debugging or copy any files to the sdcard as you can't boot the phone properly in the first place. I also noticed that I can no longer get into fastboot using the volume up and power button. However I can get into Odin mode.
Any ideas???

Install CWM or TWRP, wipe it clean, mount sdcard from there or adb sideload a ROM.
Sent from my Galaxy Nexus using Tapatalk 2

iLeopard said:
Install CWM or TWRP, wipe it clean, mount sdcard from there or adb sideload a ROM.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
But how do I do that if I can't get usb debugging or get it connected to a computer or fastboot as mentioned?
Edit: nvm, looks like i am able to get into fastboot after all.Now here's hoping I can install it without having usb debugging enabled.

.DCCXVIII said:
But how do I do that if I can't get usb debugging or get it connected to a computer or fastboot as mentioned?
Edit: nvm, looks like i am able to get into fastboot after all.Now here's hoping I can install it without having usb debugging enabled.
Click to expand...
Click to collapse
Just flash the android stock image through adb and go from there. You don't need debugging access when you're in fast boot
Have I helped? Don't forget to make love to that "Thanks" button!

Download stock images and flash em via fastboot, but you will lose everything. Its the freshest start you can get.
Sent from my Nexus Prime

Seriously, do you need to 'enable debugging' to be able to use adb in recovery?? It's a completely different and independent partition.
And fastboot doesn't need any enabling at all.
So, boot to recovery
mounts and storage
mount sd card
open up a DOS box (or terminal if you're on a mac or linux)
<path to adb>/adb shell
...
profit
The ... is where you go and uninstall the app/service, like the example you found mentioned above.
Usually this would be removing a .apk from either /system/app or /data/app

Thanks for all the help, however i am unable to get the adb drivers installed. I tried both Samsung's and Google's and they both fail (Windows doesn't even recongise a driver even after pointing it to: \sdk\extras\google\usb_driver. Anyone got any other sources for a working driver? Win7 64bit.
Edit: Managed to connect it using the pdanet drivers. Then proceeded to try to load CWM using: "fastboot flash recovery *file name*.img", but just got an error: "FAILED (remote: invalid argument)". I noticed that on my fastboot menu, it says lock state: Locked. Is this why it's failing? The boot loader is still locked? Because I tried "fastboot oem unlock" and that didn't work: "FAILED (unknown status code)".
Edit: Looks like my phone just needed a reboot. Because once I did, I was able to use the fastboot oem unlock command with success! However, before I proceed with unlocking the bootloader, can someone please confirm for me that I need to do so in order to install CWM? Many thanks.

Yes, but unless you have a play store gnex, this will probably wipe your phone anyway.
Sent from my brain using telepathy

m.is.for.michael said:
Yes, but unless you have a play store gnex, this will probably wipe your phone anyway.
Sent from my brain using telepathy
Click to expand...
Click to collapse
OK, i've managed to successfully unlock the bootloader, flash CWM and used the "fix permissions" function. I lost all my data/apps etc but I now have a working phone! Many thanks to all that helped!

[Q] Trouble with flashing new recovery

Hey everyone,
Alright so I have been trying to root my phone for the past 4 hours. I have unlocked it and flashed a custom recovery using adb. Or at least I thought I did. I tried flashing the clockworks recovery and when I would reboot it into the recovery, I would get an icon of a phone and an exclimation point. I assumed a bricked the phone and freaked out. A minute later the phone rebooted out of recovery and works fine afterwards. So I assume that the problem is the recovery. Something went wrong and I am not sure what.
Here are the steps I followed:
I was fine up until step four when I was trying to flash superuser.
No idea what to do from here.
HTC Unlocked = Bootloader is unlocked?
Not to take away from the OP, but i created a guide for a guy here at work and thought others might benefit from it.
Unlock Bootloader and Root
Unlocking your bootloader will wipe all data from your phone. Meaning you will loose everything make a backup.
Step 1: ADB Installation Instructions. NOTE:You must have ADB installed on your PC even if you use method 2b to unlock the bootloader. You will need adb to install recovery in Step 4.
1. Go to http://developer.android.com/sdk/index.html and download the sdk.
2. Follow installation instructions found here. Note: This is not a forum for this device DO NOT do anything but the adb installation on your system.
Step 2a: Download software from HTC to allow your bootloader to be unlocked.
1. Go to http://www.htcdev.com/
2. Login to the website. NOTE: Register for an account if you haven’t already. You must provide a valid email address.
3. Select “All Other Supported Models” from the drop down list and click “Begin Unlock Bootloader”
4. Follow online instructions.
1. SuperUser http://androidfiles.org/securekey.ph.../superuser.zip - Copy this file you phone. Special thanks to jmztaylor his link.
2. Recovery of your choice TWRP Recovery http://forum.xda-developers.com/show....php?t=2161702 or CWM Recovery http://forum.xda-developers.com/show....php?t=2161706. Put this file in the ADB Tools folder. NOTE: You must type the name of this file perfectly when using adb to flash it in step 4.
Step 4: Using ADB to install recovery
1. Open command prompt ( shift + right click, then choose “Open command window here”) and type “ADB devices” you should see you phone listed, if you do not start over at Step 1. NOTE: Phone must be plugged in and USB Debugging must be checked in settings.
2. Type “ADB flash recovery recovery.img” without the quotes. NOTE: the red is actually the title of the recovery file that you copied in step 3. If it’s different substitute your files name instead.
3. Once complete type “ABD reboot recovery”.
4. You should at this point backup your device
5. Once you create a backup, Choose install and navigate to the SuperUser file you put on your phone in Step 3.
6. If all goes well you are now rooted. Select reboot system to restart phone.
There is some very good information here but its spread out pretty thin. Guides IMHO are very usefull to fill the gap between devs/powerusers and the newbs.Most people that come here have a hard time with the things we take for granted such as adb commands, or adb its self (most will be setting it up for the first time). I tried my best to put it in a knowledge base that everyone can understand if for some reason you do not understand what i was trying to say please ask. I don't own this phone, just helped a friend root his, but if you need to get ahold of me pm me. I'll get back to you as soon as possible.
Any help? Just trying to get rid of the bloatware -_-

Did you copy superuser to your phone? And are you sure you are using the correct file location for adb in the command prompt? You must make sure you are and that all files you want to flash are also in the same folder as adb. Please respond if you have superuser on your phone and if you are positive you are using the correct adb folder location for the command prompt. I'm not the best at this however, I read up a lot on it just to root my phone. Took me 4 hours about as well, but that was before the recoverys came out. I suggest trying to flash twrp recovery, it's a bit buggy (for me) but I find it easier to use.
Sent from my HTC One VX using xda app-developers app

Code:
ADB flash recovery recovery.img
that is your problem to start with its not "ADB flash"
boot your phone into bootloader with usb connected to PC, Phone should read "fastboot"
Go the your adb directory in command prompt.
ex.
Code:
C:\PcUser\Master\Androidsdk\adb\
Make sure all drivers are installed, from CMD prompt window type "fastboot devices" to check your phone is showing.
if you see your device then you can type
fastboot flash recovery [drag your recovery image into cmd window] and hit enter and it should flash
once recovery is flashed you can either "fastboot Reboot" or on the phone use the Vol rockers to navigate to menu and hit bootloader then from there choose recovery

Hi,
I have the same issue about 2 days, I install TWRP Recovery and all it's ok, and flash in fastboot mode with adb like ilostchild tolds You.

It seems that I met the same problem.
My issue is the phone only boot into CMW mode, although I tried to restart it many times. When connect to usb cable, lappy did not recognize the phone so I can use adb command.
Please help me.

I can't make ADB recognize the device, I already installed the SDK the HTC Sync program but the device appears either as "My HTC" or "Android 1.0" and won't appear under "adb devices", any help? I have been googling for 3 days for a solution but I haven't found anything so far.

zeratos said:
I can't make ADB recognize the device, I already installed the SDK the HTC Sync program but the device appears either as "My HTC" or "Android 1.0" and won't appear under "adb devices", any help? I have been googling for 3 days for a solution but I haven't found anything so far.
Click to expand...
Click to collapse
Try using another computer!!! Install all neded drivers, searxh google and let windows automaticly install some. Connect via fastboot and it should say
Fastboot usb.
Also....dont search for adb devices, just enter commands starting with fastboot like... Fastboot install recovery cwmrecovery.img

spooky_ghosty said:
Try using another computer!!! Install all neded drivers, searxh google and let windows automaticly install some. Connect via fastboot and it should say
Fastboot usb.
Also....dont search for adb devices, just enter commands starting with fastboot like... Fastboot install recovery cwmrecovery.img
Click to expand...
Click to collapse
I already tried all those things you mentioned, I have been looking for 3 days for a solution for this problem on google without any luck, the device doesn't recognize any command either and I already set up a virtual machine and tried on that machine as well. u_u

Uninstall HTC sync then try adb devices be possitive you are using the correct location for adb. Usb debugging MUST be on as well. Copy paste the commands into the prompt to make sure you are entering them right. Be sure you have the downloaded files in the same folder you are using with adb.

Johann12911 said:
Uninstall HTC sync then try adb devices be possitive you are using the correct location for adb. Usb debugging MUST be on as well. Copy paste the commands into the prompt to make sure you are entering them right. Be sure you have the downloaded files in the same folder you are using with adb.
Click to expand...
Click to collapse
Already tried uninstalling HTC Sync, after that I deleted every trace of it. USB Debugging WAS ON before the phone crashed but I can't activate it now because the phone keeps looping between reboots.

Try to flash it via htc sync. Download the update and rewrite everything!
Sent from my HTC One VX using xda app-developers app