[International / GSM] few questions about rooting

xinn3r · Dec 9, 2011

Hi, I'm really new to this rooting thing, here's a few questions
1. I already set up all the adb and fastboot, used command prompt, and entered "fastboot.exe devices", it shows my device, but when I entered "adb remount" it says device not found?
2. If I factory reset the phone, will I unroot it? If not, if I flash the stock ROM provided by Google, will I unroot it?

scary alien · Dec 9, 2011

xinn3r said:
Hi, I'm really new to this rooting thing, here's a few questions
1. I already set up all the adb and fastboot, used command prompt, and entered "fastboot.exe devices", it shows my device, but when I entered "adb remount" it says device not found?
2. If I factory reset the phone, will I unroot it? If not, if I flash the stock ROM provided by Google, will I unroot it?

xinn3r,

1. Do you have USB debugging enabled? If not, adb won't respond to such a request.

2. No, the root binaries (su and Superuser.apk) are not removed (nor is custom recovery when/if you ever install that) when you do a factory reset. Yes, if you flash a stock ROM, that will put you back to square one, unrooted

.

Cheers!

xinn3r · Dec 9, 2011

scary alien said:
xinn3r,

1. Do you have USB debugging enabled? If so, adb won't respond to such a request.

2. No, the root binaries (su and Superuser.apk) are not removed (nor is custom recovery when/if you ever install that) when you do a factory reset. Yes, if you flash a stock ROM, that will put you back to square one, unrooted .

Cheers!

Yes, I do have it enabled, that's why I'm so frustrated, I did everything by the book. I can use fastboot but not adb, any ideas why?

scary alien · Dec 9, 2011

xinn3r said:
Yes, I do have it enabled, that's why I'm so frustrated, I did everything by the book. I can use fastboot but not adb, any ideas why?

Try downloading and installing some of the adb USB drivers listed at the bottom of the first post of this thread:

http://androidforums.com/galaxy-nexus-all-things-root/452146-how-root-samsung-galaxy-nexus.html

(and let us know if this was the fix you--that will help others).

Cheers!

xinn3r · Dec 9, 2011

scary alien said:
Try downloading and installing some of the adb USB drivers listed at the bottom of the first post of this thread:

http://androidforums.com/galaxy-nexus-all-things-root/452146-how-root-samsung-galaxy-nexus.html

(and let us know if this was the fix you--that will help others).

Cheers!

OK this is wierd, so I updated my Samsung drivers, (was 1.4.6 , downloaded the 1.4.8)
the I entered "adb remount", it worked, daemon started successfully, but then, "error: device not found" showed up again, I attached a screenshot so you can take a look

scary alien · Dec 9, 2011

xinn3r said:
OK this is wierd, so I updated my Samsung drivers, (was 1.4.6 , downloaded the 1.4.8)
the I entered "adb remount", it worked, daemon started successfully, but then, "error: device not found" showed up again, I attached a screenshot so you can take a look

Well, the "daemon started successfully" only indicates that the adb daemon on your PC was restarted successfully.

It doesn't look like any of the adb commands worked in your screenshot...

Dunno, you could try disconnecting and reconnectiong, etc. I don't have my GNex (yet--grrr), so I can't tell you what combo works for my.

Check the USB drivers at the bottom of the first post of the how-to guide for some adb driver options. One of them should work (I've gathered them from various threads I've read).

Good luck and let us know.

xinn3r · Dec 10, 2011

scary alien said:
Well, the "daemon started successfully" only indicates that the adb daemon on your PC was restarted successfully.

It doesn't look like any of the adb commands worked in your screenshot...

Dunno, you could try disconnecting and reconnectiong, etc. I don't have my GNex (yet--grrr), so I can't tell you what combo works for my.

Check the USB drivers at the bottom of the first post of the how-to guide for some adb driver options. One of them should work (I've gathered them from various threads I've read).

Good luck and let us know.

Well, before, it didn't even write "daemon started successfully", usually it just said device not found, this time it's written started successfully, but again... device not found.. sigh... what am I doing wrong I wonder

EDIT: OK, so I checked, and as it turns out "adb devices" works while not in fastboot mode (in normal mode)
but when I go to fastboot mode (power + VOL up + VOL down), it can't detect the device, what I'm doing wrong?

scary alien · Dec 10, 2011

xinn3r said:
Well, before, it didn't even write "daemon started successfully", usually it just said device not found, this time it's written started successfully, but again... device not found.. sigh... what am I doing wrong I wonder

Well, it won't report "daemon started successfully" if its already running from a prior invocation (you can force it to restart by doing an "adb kill-server" and then issuing another adb command...the adb client will see that the adb daemon is not running and will simply restart it).

You might also try rebooting your PC, too...I've read where that helped some folks.

Things you might try:

- rebooting
- different USB port on your PC
- different USB cable
- different USB drivers
- making sure USB debugging is enabled
- a different computer (Macs and Linux systems don't have these adb USB issues)

By the way, just to be clear, your phone is booted in Android, right? You can't use adb except when Android is booted (with USB debugging on) or when you've got a custom recover installed (that supports adb).

Hope that helps.

Cheers!

xinn3r · Dec 10, 2011

scary alien said:
Well, it won't report "daemon started successfully" if its already running from a prior invocation (you can force it to restart by doing an "adb kill-server" and then issuing another adb command...the adb client will see that the adb daemon is not running and will simply restart it).

You might also try rebooting your PC, too...I've read where that helped some folks.

Things you might try:

- rebooting
- different USB port on your PC
- different USB cable
- different USB drivers
- making sure USB debugging is enabled
- a different computer (Macs and Linux systems don't have these adb USB issues)

By the way, just to be clear, your phone is booted in Android, right? You can't use adb except when Android is booted (with USB debugging on) or when you've got a custom recover installed (that supports adb).

Hope that helps.

Cheers!

Yes, it's a galaxy nexus, so it's 100% Android. I should just boot into fastboot and I should be able to use adb right?

scary alien · Dec 10, 2011

xinn3r said:
Yes, it's a galaxy nexus, so it's 100% Android. I should just boot into fastboot and I should be able to use adb right?

Well, my question about Android had to do about when you were trying to use adb.

adb can only be used when you've booted up your phone normally and you have USB debugging enabled. You can also use adb when you phone is booted in a custom recovery (like ClockworkMod).

You can't used adb when your phone is in fastboot mode (that's for fastboot, of course).

I was just trying to make sure you weren't attempting to communicate to your phone using adb while you were in fastboot mode.

teddyearp · Dec 10, 2011

+1 ^^^ above.

Adb doesn't work while the phone is booted in bootloader (fastboot) mode. In recovery or regular os yes.

xinn3r · Dec 10, 2011

scary alien said:
Well, my question about Android had to do about when you were trying to use adb.

adb can only be used when you've booted up your phone normally and you have USB debugging enabled. You can also use adb when you phone is booted in a custom recovery (like ClockworkMod).

You can't used adb when your phone is in fastboot mode (that's for fastboot, of course).

I was just trying to make sure you weren't attempting to communicate to your phone using adb while you were in fastboot mode.

Ahhh.... it's my bad... I used adb while I was in fastboot....
OK, I can use adb in normal OS mode...

OK, last questions
1. What command should I use for flashing stock image that I downloaded from the Google website?
2. I read that being rooted, you can still recieve an OTA update, because I didn't flash any costum ROM, but I still haven't got the volume bug fix update yet, is it because of my country? I live in China

teddyearp · Dec 11, 2011

AS I don't have the phone yet either, I am only speculating. I would think you could take the file and transfer it to your phone, the tricky part is where. On the Moto A855, it was on the sdcard, so if the Nexus has an area of memory called sdcard, then try putting it there. Then plug into your computer and run this command:

adb reboot recovery

Your phone should boot into recovery and then you can find the 'apply update' selection there.

Again, this is from my experience with the A855, your mileage may vary.

good luck

scary alien · Dec 11, 2011

xinn3r said:
Ahhh.... it's my bad... I used adb while I was in fastboot....
OK, I can use adb in normal OS mode...

OK, last questions
1. What command should I use for flashing stock image that I downloaded from the Google website?
2. I read that being rooted, you can still recieve an OTA update, because I didn't flash any costum ROM, but I still haven't got the volume bug fix update yet, is it because of my country? I live in China

xinn3r,

Glad you got the adb issue sorted-out

.

First, a little warning for others that might read this: you need to be sure that you have and only use the proper stock recovery images for your device! The ones I reference below are for the GSM version; there will be others published for the VZW LTE version at some point in time, but you'd be well-advised to make sure you are flashing the correct files for your device. You've been warned.

1. You are referencing this file yakju-itl41f-factory-192e5c67.tgz downloaded from here: Factory Images for Nexus Devices - Google Support for Nexus Phones and Flagship Devices - Google Code, right?

This is the "Factory Images "yakju" for Galaxy Nexus "maguro" (GSM/HSPA+)" image which I believe contains the volume-key fix.

Code:

Google direct download
	source: 	[url=http://code.google.com/android/nexus/images.html]Factory Images for Nexus Devices - Google Support for Nexus Phones and Flagship Devices - Google Code[/url]
	download:	yakju-itl41f-factory-192e5c67.tgz
	File size:	193,303,863 (bytes)
	MD5 checksum:	7702b2a806b9efcb781838668e9f3415

		contains:	[COLOR="blue"]image-yakju-itl41f.zip[/COLOR]
		File size:	189,165,717 (bytes)
		MD5 checksum: 	[COLOR="red"]c1b3a2a4998e13908e347de649247ca4[/COLOR]

This same stock GSM recovery image is also referenced and available in this thread on XDA: [ROM] Official Factory Image ITL41F - xda-developers. That thread references a itl41f.zip file which also contains the same image-yakju-itl41f.zip

This itl41f.zip file also contains tools to help you install and re-flash the stock GSM image:

Code:

[ROM] Official Factory Image ITL41F with installation script:
	source:		[url=http://forum.xda-developers.com/showthread.php?t=1373995][ROM] Official Factory Image ITL41F - xda-developers[/url]
	download:	itl41f.zip
	File size:	193,618,825 itl41f.zip (bytes)
	MD5 checksum:	6a867ec721763538441da92292717520

		contains:	[COLOR="blue"]image-yakju-itl41f.zip[/COLOR]
		File size:	189,165,717 (bytes)
		MD5 checksum: 	[COLOR="Red"]c1b3a2a4998e13908e347de649247ca4[/COLOR]

	here are the contents of the [COLOR="Blue"]flash-windows.bat[/COLOR] file:

		fastboot-windows flash bootloader bootloader-maguro-primekj10.img
		fastboot-windows reboot-bootloader
		fastboot-windows flash radio radio-maguro-i9250xxkk1.img
		fastboot-windows reboot-bootloader
		fastboot-windows -w update image-yakju-itl41f.zip

As you can see, the image-yakju-itl41f.zip is identical to the one from the published direct Google download area.

2. For your second question, if you are rooted but you don't remove, modify, or freeze any system apps, then yes, you should still receive your OTA updates just fine.

Hope that helps.

Cheers!

dockmaster · Dec 11, 2011

Whats the difference between using your phone as a mobile hot spot(which I gather VZW, knows your doing) and rooting your phone and having wireless tether (which I assume VZW cant detect). Thats the only thing stopping me from getting a Nexus when ever there released. I need to wireless tether. I refuse to pay for MHS cause I'm unlimited data. Will a root program include a wireless tether program? Other than that, stock is fine!!

scary alien · Dec 11, 2011

dockmaster said:
Whats the difference between using your phone as a mobile hot spot(which I gather VZW, knows your doing) and rooting your phone and having wireless tether (which I assume VZW cant detect). Thats the only thing stopping me from getting a Nexus when ever there released. I need to wireless tether. I refuse to pay for MHS cause I'm unlimited data. Will a root program include a wireless tether program? Other than that, stock is fine!!

Well, the bad news is that VZW most likely can detect if you are using wireless tethering (there's a whole host of ways that they can do this). Unlimited data really has nothing to do with whether or not you can or should be able to use a wireless (or even wired) tethering app. There are countless threads here at AF where this has been "discussed" (quotes intentional, LOL, that's being kind in some cases

[i.e., where mods have stepped in and closed threads, etc.]).

I would encourage you to reference this thead: http://androidforums.com/verizon/455585-verizons-official-tethering-policy.html

I know that's not much consolation, but I hope that helps some.

Cheers!

dockmaster · Dec 11, 2011

scary alien said:
Well, the bad news is that VZW most likely can detect if you are using wireless tethering (there's a whole host of ways that they can do this). Unlimited data really has nothing to do with whether or not you can or should be able to use a wireless (or even wired) tethering app. There are countless threads here at AF where this has been "discussed" (quotes intentional, LOL, that's being kind in some cases [i.e., where mods have stepped in and closed threads, etc.]).

I would encourage you to reference this thead: http://androidforums.com/verizon/455585-verizons-official-tethering-policy.html

I know that's not much consolation, but I hope that helps some.

Cheers!

I have my eris rooted and use wireless tethering and have never heard from VZW, so I guess they either dont care or dont know. I also use PDAnet and I'm pretty sure they dont see that either. Guess I need to go to XDA..dont want to get anyone in trouble!! Thanks for the comeback!!

scary alien · Dec 11, 2011

dockmaster said:
I have my eris rooted and use wireless tethering and have never heard from VZW, so I guess they either dont care or dont know. I also use PDAnet and I'm pretty sure they dont see that either. Guess I need to go to XDA..dont want to get anyone in trouble!! Thanks for the comeback!!

I apologize if I came across as unsympathetic, which I really am not.

Its just that AF wants to be careful about this topic and there really has been so much of it already discussed. The new terms-of-service threads were recently populated in the carrier areas and we've been encouraged to direct folks there.

xinn3r · Dec 12, 2011

Yes, I got the image from there, I checked, it is the right one, all I need to know is what command should I use, like fastboot devices, or adb remount/shell, something like that

scary alien · Dec 12, 2011

xinn3r said:
Yes, I got the image from there, I checked, it is the right one, all I need to know is what command should I use, like fastboot devices, or adb remount/shell, something like that

xinn3r,

Did you see my post #14 above? The file that's available from XDA has a script (flash-windows.bat) that will issue the commands for you. I also showed the commands (i.e., the contents of that file, too)--i.e., the parts in red below if you wanted to execute them manually (after extracting the contents of the file, of course):

Code:

[ROM] Official Factory Image ITL41F with installation script:
	source:		[ROM] Official Factory Image ITL41F - xda-developers
	download:	itl41f.zip
	File size:	193,618,825 itl41f.zip (bytes)
	MD5 checksum:	6a867ec721763538441da92292717520

		contains:	image-yakju-itl41f.zip
		File size:	189,165,717 (bytes)
		MD5 checksum: 	c1b3a2a4998e13908e347de649247ca4

	here are the contents of the flash-windows.bat file:

		[COLOR="Red"]fastboot-windows flash bootloader bootloader-maguro-primekj10.img
		fastboot-windows reboot-bootloader
		fastboot-windows flash radio radio-maguro-i9250xxkk1.img
		fastboot-windows reboot-bootloader
		fastboot-windows -w update image-yakju-itl41f.zip[/COLOR]

Cheers!

xinn3r · Dec 13, 2011

I wonder why I'm still not getting the volume bug fix update, any idea why?

And many of my apps can't be downloaded because it says the galaxy nexus is incompatible, will this be a problem or are they working on a fix?

scary alien · Dec 13, 2011

xinn3r said:
I wonder why I'm still not getting the volume bug fix update, any idea why?

And many of my apps can't be downloaded because it says the galaxy nexus is incompatible, will this be a problem or are they working on a fix?

Not sure about the volume bug OTA or how/when it will be pushed-out (or if it already has been). Pretty sure one of the stock recovery images has the volume bug fix in it already, so I'm not sure what the deal is...(are you actually seeing the volume bug issue?).

Re. the apps question, that's undoubtedly due to Ice Cream Sandwich... I noticed when Honeycomb came out and I got my Xoom, that app that I wrote were not available on the Market for me. I pretty sure that this was not due to the Android O/S compatibility, since each app should be able to run on 1.5 and higher, but probably due to screen / display resolution properties. I'm still working on changing my apps to include support for hi-res devices...so, I'm betting that that's probably what you are seeing, too.

Cheers!

xinn3r · Dec 14, 2011

scary alien said:
Not sure about the volume bug OTA or how/when it will be pushed-out (or if it already has been). Pretty sure one of the stock recovery images has the volume bug fix in it already, so I'm not sure what the deal is...(are you actually seeing the volume bug issue?).

Re. the apps question, that's undoubtedly due to Ice Cream Sandwich... I noticed when Honeycomb came out and I got my Xoom, that app that I wrote were not available on the Market for me. I pretty sure that this was not due to the Android O/S compatibility, since each app should be able to run on 1.5 and higher, but probably due to screen / display resolution properties. I'm still working on changing my apps to include support for hi-res devices...so, I'm betting that that's probably what you are seeing, too.

Cheers!

I'm not seeing any volume bug, but I'm just concerned that in the future I won't be getting major OTA updates and need to download and re-flash the newest stock image

Yes, I read that somewhere in the forums too, guess we just need to wait for the developers to remedy this

another question if you don't mind:
I found out that there's a part of the partitioned space that acts like a SD card, so if I restore that partition will still be there, but if I re-flash my phone, EVERYTHING will be gone, am I right?

scary alien · Dec 14, 2011

xinn3r said:
I found out that there's a part of the partitioned space that acts like a SD card, so if I restore that partition will still be there, but if I re-flash my phone, EVERYTHING will be gone, am I right?

I believe so, but don't know that for sure (I might test this for my device).

You are exactly right, the "SD card" is actually just a part of another partition.

At this time, I'm going to assume that is true for my device

[better to be safe than sorry, eh?].

xinn3r · Dec 16, 2011

scary alien, I just read another thread that said if I got ClockWorkMod Recovery installed I can't get an OTA update, is this true? Because I do have CWM installed

[International / GSM] few questions about rooting

Member

not really so scary

Member

not really so scary

Member

Attachments

not really so scary

Member

not really so scary

Member

not really so scary

Android Expert

Member

Android Expert

not really so scary

Well-Known Member

not really so scary

Well-Known Member

not really so scary

Member

not really so scary

Member

not really so scary

Member

not really so scary

Member