Related
Credit goes to eugene373 and attn1. These are mostly their instructions, but I did change, clarify, and add a few steps. If you can't get any of the other methods working, try this one.
Prerequisites...
Note: If you're in Linux, you only need to do Step 4, Step 6, and Step 7.
Step 0.
Download and install HTC Sync: http://www.htc.com/us/support/aria-att/downloads/
Step 1.
Download and unzip the Android SDK: http://developer.android.com/sdk/index.html
Step 2.
Go into the folder where you unzipped the Android SDK and open "SDK Setup.exe".
If you aren't greeted with a failed to fetch URL error, proceed to Step 3. If you did receive this error, go to Settings in the "Choose Packages to Install" window and check "Force https;//... sources to be fetched using http://..."
Close and re-open "SDK Setup.exe".
Step 3.
When the "Choose Packages to Install" window pops up, make sure the package "Usb Driver package, revision x" is checked. You can uncheck everything else. Click Install. After it downloads and installs, close "Android SDK and AVD Manager".
Step 4.
With your device unplugged from your computer, go to Settings > Application > Development on your device and turn on USB Debugging.
Step 5.
Now plug your device in to your computer. This is just to make sure the USB drivers are installed.
Once they are installed, unplug your device and turn it off.
Step 6.
This step is optional, but it may prevent an error later on in the process. If you've never formatted your SD card from a computer, remove it from the phone and format it in Windows or OSX with an external card reader. Then place the formatted card back in your phone, but leave the phone off.
Step 7.
Download the updated Root.zip from eugene373's guide: Root the Slide & Other HTC Devices*6/15/2010* How-To Updated 6/29/2010
Now let's get started...
Step 0.
Unzip Root.zip
Step 1.
Place the contents ("update.zip", "ota.zip", and "loop") into the Android SDK tools folder.
Step 2.
Open Command Prompt or Terminal and CD to the SDK tools directory.
Step 3.
Power on your device into the bootloader by holding the "Volume Down" key and simultaneously pressing Power.
Once you're in the bootloader, wait about 30 seconds until some diagnostic checking is done.
Press "Volume Down" to highlight Recovery, but do not push Power to execute just yet.
Step 4.
Now run your loop file from the prompt (either type "loop" in Windows or "./loop.sh" in Linux) (refer to ice3186's post for Mac instructions)
Note: The loop does nothing but show you the connection status of your phone. It's not technically required, but we'll use it in this guide.
Step 5.
Once the loop is running in your prompt, get ready to connect the phone to the computer with the USB cable, but don't connect one end quite yet. With Recovery still highlighted on your phone, you will need to push the Power button and then immediately plug in the other end of the USB cord.
Step 6.
After a few seconds, you should see your device listed in the loop.
Step 7.
Unplug the USB cable from the bottom of your phone and plug it back in. You probably don't need to do this, but let's be safe. Wait for your device to show up in the loop again. Hit CTRL-C to terminate the loop.
Step 8.
You should see a triangle/exclaimation over a phone graphic.
Hold the "Volume Up" key (note it's Volume UP this time) and simultaneously press Power.
After the menu comes up, use the volume and power buttons to select and run update.zip. (This will fail, but we already know that! Select it anyway.)
Step 9.
Paste the following command into your prompt and press Enter.
adb push ota.zip /sdcard/update.zip (*OSX users add a ./ in front of all terminal commands please)
Step 10.
This is very important!! Have this next command ready in your prompt before running update.zip again!!
This is the command. Paste it into your prompt, but DO NOT press Enter yet.
adb push update.zip /sdcard
Step 11.
Run update.zip and as soon as you see a faint progress bar appear behind the text at the bottom of the screen, push Enter to execute the command in your prompt.
Step 12.
If successful, you should see Clockwork Recovery and you now have Su and Superuser.apk installed! You can now reboot your phone into the OS to verify. If unsuccessful, repeat steps 11 and 12.
Step 13.
This step is optional, but it will save you the pain of going through all of these steps again in the future.
Unrevoked team: Recovery reflash tool (updated - Now for Aria/Liberty!)
I think some trouble shooting comments should be mentioned, so I'll just write a few things I noticed while rooting my device (for 7 frustration filled hours).
If you cannot see your device show up in 'adb devices' in recovery, boot into the OS normally and see if it shows up. If it does not, then it's a safe bet that you have one of two problems - you do not have all the drivers installed, or you do not have 'usb debugging' enabled. This can be enabled in 'settings->applications->development->usb debugging'. To avoid driver issues, it's highly recommended that you do this process in linux or osx.
If, on the other hand, your phone DOES show up in Android but not in recovery, or if it just blips on the screen for a second (when running the loop) as an offline device, then it might be the formatting of your sd card. Do NOT format your sd card from your phone or within Android. The ONLY time I managed to get the phone to show up in recovery without disappearing immediately was by removing the sd card, formatting it in windows or osx with an external card reader, copying the files over (new rom or rooting files), and then replacing it in the phone while the phone is off. After putting the card back in your phone, try the procedure again - go to the bootloader->hboot->recovery (while the cable is unplugged), then press the power button and immediately after plug the cable in (usually works when you plug the cable in about .2-.5 seconds later). If it does not show up at all, reboot the phone and try again, but do NOT let it boot back to Android. You can get back in to the bootloader by waiting until the 'HTC quietly brilliant' screen shows up and typing 'adb reboot bootloader' with the usb cable attached.
It took me a really long time to figure that out. I don't think the type of sd card matters so much as the formatting of it. I actually used the 2gb card that came with the phone, and it worked almost every single time after I reformatted the card.
Also, if you manage to get it working and root the phone, do yourself a huge favor and install the custom Unrevoked recovery image mentioned in the original rooting thread, so you never have to deal with this nonsense ever again.
Also also, if you get to the step where you do 'adb push ota.zip /sdcard/update.zip' and you get an error:0, installation aborted message, you did something wrong. The problem is that you aren't actually supposed to flash ota.zip. What you're supposed to do is push ota.zip to your phone as update.zip, and leave it there. Don't touch anything else. What you will do after that is type 'adb push update.zip /sdcard/update.zip' in the command prompt (WITHOUT hitting enter yet, just get ready to). You will then select 'sdcard:update.zip' and press power and IMMEDIATELY AFTER pressing power, you will press enter on the command prompt to execute your adb push command. What this does is causes recovery to read the ota.zip file you uploaded and recognize it as a legit update, but you replace it with update.zip before it actually gets extracted (if your timing is good). So recovery reads the signature of ota.zip, but actually extracts the stuff in update.zip and runs that instead.
Hope that helps with some common problems I observed. Good luck, dudes.
okay so I think I the only one using a Mac in this rooting process. A few things I have learned and may already be known but I thought I would clarify.
1.) to get a loop to run on the mac i had to re-write the file loop.bat
this is the code that works for me and how to do it.
a.) rename the file to end in .sh not .bat the way it came
b.) open the file with TextEdit
c.) delete all of the text in it and write this in there
Code:
while [ "0" ]
do
{
./adb devices
}
done
d.) save the file back in the sdk/tools folder
e.) in terminal the command once you cd to the folder is ./loop.sh
2.) i have yet to be successful in the attempt to root so anyone knowing anything to help would be appreciated! But i am still cracking i think i am going to wear out the plug before i am done though.
it should be pointed out that the loop does nothing except tell you if you have a connection or not. When you plug in the usb port, it will respond after a few seconds, or it won't. Try again.
gtg465x said:
Credit goes to eugene373 and attn1. These are mostly their instructions, but I did change, clarify, and add a few steps. If you can't get any of the other methods working, try this one.
Prerequisites...
Step 0.
Download and install HTC Sync: http://www.htc.com/us/support/aria-att/downloads/
Step 1.
Download and unzip the Android SDK: http://developer.android.com/sdk/index.html
Step 2.
Go into the folder where you unzipped the Android SDK and open "SDK Setup.exe"
When the "Choose Packages to Install" window pops up, make sure the package "Usb Driver package, revision x" is checked. You can uncheck everything else. Click Install. After it downloads and installs, close "Android SDK and AVD Manager".
Step 3.
With your device unplugged from your computer, go to Settings > Application > Development on your device and turn on USB Debugging.
Step 4.
Now plug your device in to your computer. This is just to make sure the USB drivers are installed.
Once they are installed, unplug your device and turn it off.
Step 5.
Download Root.zip from eugene373's guide: http://forum.xda-developers.com/showpost.php?p=6820344&postcount=1
Now let's get into it...
Step 0.
Unzip Root.zip
Step 1.
Place the contents ("update.zip", "ota.zip", and "loop") into the Android SDK tools folder.
Step 2.
Open Command Prompt or Terminal and CD to the SDK tools directory.
Step 3.
Power on your device into the bootloader by holding down the "Volume Down" key and simultaneously pressing Power.
Once you're in the bootloader, wait about 30 seconds, until some diagnostic checking is done.
Press "Volume Down" to highlight Recovery, but do not push Power to execute just yet.
Step 4.
Now run your loop file from the prompt (either type "loop" in Windows or "./loop.sh" in a *nix like) ( ./ Is used For OSX )
Step 5.
Once the loop is running in your prompt, get ready to connect the phone to the computer with the USB cable, but don't connect one end quite yet. With Recovery still highlighted on your phone, you will need to push the Power button and then immediately plug in the other end of the USB cord.
Step 6.
After a few seconds, you should see your device listed in the loop.
Step 7.
Unplug your USB cable from the bottom of your phone and plug it back in. You probably don't need to do this, but let's be safe. Wait for your device to show up in the loop again. Hit CTRL-C to terminate the loop.
Step 8.
You should see a triangle/exclaimation over a phone graphic.
Hold down the "Volume Up" key (note it's Volume UP this time) and simultaneously press Power.
After the menu comes up, use the volume and power buttons to select and run update.zip. (This will fail, but we already know that! Select it anyway.)
Step 9.
Paste the following command into your prompt and press Enter.
adb push ota.zip /sdcard/update.zip (*OSX users add a ./ in front of all terminal commands please.)
Step 11.
This is very important!! Have this next command ready in your prompt before running update.zip again!!
This is the command. Paste it into your prompt, but DO NOT press Enter yet.
adb push update.zip /sdcard
step 12.
Run update.zip and as soon as you see a faint progress bar appear behind the text at the bottom of the screen, push Enter to execute the command in your prompt.
Step 13.
If successful, you should see Clockwork Recovery and you now have Su & Superuser.apk installed! You can now reboot your phone into the OS to verify.
If unsuccessful, repeat steps 11 & 12.
Click to expand...
Click to collapse
This isn't complete - this just gets you to clockwork and you haven't installed anything yet. You need to add steps to add root acces or flash a rom that is rooted. Also, make sure to reference the unrevoked tool to install Clockwork after root so this whole ordeal can be avoided next time.
Yes! The secret was formatting the sd card outside of the phone. I am now rooted and liberated! Thanks for plugging along with all the advice guys!
modest_mandroid said:
I think some trouble shooting comments should be mentioned, so I'll just write a few things I noticed while rooting my device (for 7 frustration filled hours).
If you cannot see your device show up in 'adb devices' in recovery, boot into the OS normally and see if it shows up. If it does not, then it's a safe bet that you have one of two problems - you do not have all the drivers installed, or you do not have 'usb debugging' enabled. This can be enabled in 'settings->applications->development->usb debugging'. To avoid driver issues, it's highly recommended that you do this process in linux or osx.
If, on the other hand, your phone DOES show up in Android but not in recovery, or if it just blips on the screen for a second (when running the loop) as an offline device, then it might be the formatting of your sd card. Do NOT format your sd card from your phone or within Android. The ONLY time I managed to get the phone to show up in recovery without disappearing immediately was by removing the sd card, formatting it in windows or osx with an external card reader, copying the files over (new rom or rooting files), and then replacing it in the phone while the phone is off. After putting the card back in your phone, try the procedure again - go to the bootloader->hboot->recovery (while the cable is unplugged), then press the power button and immediately after plug the cable in (usually works when you plug the cable in about .2-.5 seconds later). If it does not show up at all, reboot the phone and try again, but do NOT let it boot back to Android. You can get back in to the bootloader by waiting until the 'HTC quietly brilliant' screen shows up and typing 'adb reboot bootloader' with the usb cable attached.
It took me a really long time to figure that out. I don't think the type of sd card matters so much as the formatting of it. I actually used the 2gb card that came with the phone, and it worked almost every single time after I reformatted the card.
Also, if you manage to get it working and root the phone, do yourself a huge favor and install the custom Unrevoked recovery image mentioned in the original rooting thread, so you never have to deal with this nonsense ever again.
Also also, if you get to the step where you do 'adb push ota.zip /sdcard/update.zip' and you get an error:0, installation aborted message, you did something wrong. The problem is that you aren't actually supposed to flash ota.zip. What you're supposed to do is push ota.zip to your phone as update.zip, and leave it there. Don't touch anything else. What you will do after that is type 'adb push update.zip /sdcard/update.zip' in the command prompt (WITHOUT hitting enter yet, just get ready to). You will then select 'sdcard:update.zip' and press power and IMMEDIATELY AFTER pressing power, you will press enter on the command prompt to execute your adb push command. What this does is causes recovery to read the ota.zip file you uploaded and recognize it as a legit update, but you replace it with update.zip before it actually gets extracted (if your timing is good). So recovery reads the signature of ota.zip, but actually extracts the stuff in update.zip and runs that instead.
Hope that helps with some common problems I observed. Good luck, dudes.
Click to expand...
Click to collapse
Really good tips. I hope you don't mind - I am going to link to this to my original thread.
Troubleshooting Tip on Prerequisite Step 2: If you're working behind a firewall, router, or proxy server, you're going to have to configure SDK Setup to use an open port on that device, in order to download updates.
I won't go through the exact steps here, but if SDK setup is hanging, this is the most likely culprit.
Regards,
Corporate Dog
Corporate Dog said:
Troubleshooting Tip on Prerequisite Step 2: If you're working behind a firewall, router, or proxy server, you're going to have to configure SDK Setup to use an open port on that device, in order to download updates.
I won't go through the exact steps here, but if SDK setup is hanging, this is the most likely culprit.
Regards,
Corporate Dog
Click to expand...
Click to collapse
get a copy of linux livecd and then you don't have to actually set up the SDK or worry about any drivers.
attn1 said:
This isn't complete - this just gets you to clockwork and you having installed anything yet. You need to add steps to root or flash a rom that is rooted. Also, make sure to reference the unrevoked tool to install Clockwork after root so this whole ordeal can be avoided next time.
Click to expand...
Click to collapse
If you made it to clockwork using this method then you're rooted. Check eugene's updated instructions. Look at the 6/29/2010 update on his original post... http://forum.xda-developers.com/showpost.php?p=6820344&postcount=1
I will add a reference to the unrevoked tool.
modest_mandroid said:
If, on the other hand, your phone DOES show up in Android but not in recovery, or if it just blips on the screen for a second (when running the loop) as an offline device, then it might be the formatting of your sd card. Do NOT format your sd card from your phone or within Android. The ONLY time I managed to get the phone to show up in recovery without disappearing immediately was by removing the sd card, formatting it in windows or osx with an external card reader, copying the files over (new rom or rooting files), and then replacing it in the phone while the phone is off. After putting the card back in your phone, try the procedure again - go to the bootloader->hboot->recovery (while the cable is unplugged), then press the power button and immediately after plug the cable in (usually works when you plug the cable in about .2-.5 seconds later). If it does not show up at all, reboot the phone and try again, but do NOT let it boot back to Android. You can get back in to the bootloader by waiting until the 'HTC quietly brilliant' screen shows up and typing 'adb reboot bootloader' with the usb cable attached.
It took me a really long time to figure that out. I don't think the type of sd card matters so much as the formatting of it. I actually used the 2gb card that came with the phone, and it worked almost every single time after I reformatted the card.
Click to expand...
Click to collapse
Excellent troubleshooting tips. I added a note about formatting your SD card to the prerequisites.
ice3186 said:
okay so I think I the only one using a Mac in this rooting process. A few things I have learned and may already be known but I thought I would clarify.
1.) to get a loop to run on the mac i had to re-write the file loop.bat
this is the code that works for me and how to do it.
a.) rename the file to end in .sh not .bat the way it came
b.) open the file with TextEdit
c.) delete all of the text in it and write this in there
Code:
while [ "0" ]
do
{
./adb devices
}
done
d.) save the file back in the sdk/tools folder
e.) in terminal the command once you cd to the folder is ./loop.sh
2.) i have yet to be successful in the attempt to root so anyone knowing anything to help would be appreciated! But i am still cracking i think i am going to wear out the plug before i am done though.
Click to expand...
Click to collapse
Thanks. Added a reference to your post.
attn1 said:
it should be pointed out that the loop does nothing except tell you if you have a connection or not. When you plug in the usb port, it will respond after a few seconds, or it won't. Try again.
Click to expand...
Click to collapse
Noted in the original post.
Corporate Dog said:
Troubleshooting Tip on Prerequisite Step 2: If you're working behind a firewall, router, or proxy server, you're going to have to configure SDK Setup to use an open port on that device, in order to download updates.
I won't go through the exact steps here, but if SDK setup is hanging, this is the most likely culprit.
Regards,
Corporate Dog
Click to expand...
Click to collapse
Thanks. Added the workaround.
attn1 said:
get a copy of linux livecd and then you don't have to actually set up the SDK or worry about any drivers.
Click to expand...
Click to collapse
Thanks. Added a note to the top of the prerequisites.
gtg465x said:
Step 12.
If successful, you should see Clockwork Recovery and you now have Su and Superuser.apk installed! You can now reboot your phone into the OS to verify. If unsuccessful, repeat steps 11 and 12.
Step 13.
This step is optional, but it will save you the pain of going through all of these steps again in the future.
Unrevoked team: Recovery reflash tool (updated - Now for Aria/Liberty!)
Click to expand...
Click to collapse
In no way, shape or form are you done after set 12.
You need to do more than just get into Clockwork. That alone doesn't root the phone.
gtg465x said:
If you made it to clockwork using this method then you're rooted. Check eugene's updated instructions. Look at the 6/29/2010 update on his original post... http://forum.xda-developers.com/showpost.php?p=6820344&postcount=1
I will add a reference to the unrevoked tool.
Click to expand...
Click to collapse
My mistake. He not only updated his instructions, he updated his update.zip. That should do it.
Good job!
I was just wondering If I have device issues after it is rooted, is it possible to remove the root and flash everything back to factory defaults for warranty purposes like the windows phones or is it once the warranty is gone it is gone?
steezee said:
I was just wondering If I have device issues after it is rooted, is it possible to remove the root and flash everything back to factory defaults for warranty purposes like the windows phones or is it once the warranty is gone it is gone?
Click to expand...
Click to collapse
Dunno if you can reflash the stock recovery again if you replaced it with clockwork, but you can definitely flash the stock ATT rom again. You can download it from HTC's site: http://member.america.htc.com/download/Web_materials/Manual/HTC_Aria_ATT/HTCAriaOriginalShipROM.exe
Banging my head on the wall. Got it to detect device once on loop. Never again after that. Phone shows up in device manager. Formatted 8gb and 2 gb cards several times.
urge growing. ... want to . . break.. . . .. . .random objects. . .
attn1 said:
My mistake. He not only updated his instructions, he updated his update.zip. That should do it.
Good job!
Click to expand...
Click to collapse
Sorry, I should have mentioned that he updated his update.zip.
You guys are right , there are missing step in the tutorial to fully root Aria.
after i get in to the clockwork from the step above. i have to install the custom rom that can be found in the forum.
when i try to install "Unrevoked team: Recovery reflash tool (updated - Now for Aria/Liberty!) " . the process goes throught but the recovery is still the same HTC blue color recovery screen.
so before you insert your sd card into the phone after you format the sd card. remember to copy the rooted rom into the sd card so when you successfully get into the clockwork. you want to install the rom then your aria is rooted with superuser icon on the application.
after then you do the "Unrevoked team: Recovery reflash tool (updated - Now for Aria/Liberty!) step .
There are no steps missing from the first post. I rooted my Aria using that method. Just make sure you have the latest Root.zip from eugene's thread. He updated it the other day and if you try to use the older version of Root.zip with this method it will not work.
What you are doing is installing a custom rom, which is fine, but it's not required to root the Aria.
i was trying to get the clockwork to install and it only work after i load the liberated_aria_b003_signed.zip
before i load liberated_aria_b003_signed.zip , it still give me the default HTC recovery screen.
after i load liberated_aria_b003_signed.zip and install "Unrevoked team: Recovery reflash tool (updated - Now for Aria/Liberty!) " . i get the clockwork screen as the recovery screen .
i still can't get the side loading to show after i follow the step from here
•COMMON:
•Enable USB debugging (settings > applications > development > USB Debugging)
•adb remount
•adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
Linux/OS X:
•echo "update secure set value = 1 where name = 'install_non_market_apps';"|sqlite3 settings.db
WINDOWS:
•echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
COMMON:
•adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
•Reboot phone and sideloading works. (thanks to fluffyarmada)
.
Ok so I've been looking around all over google and XDA for the correct way to install the usb drivers for adb and fastboot from sdk manager(r11) and there are no updated guides out there for the latest r11 sdk program... so here is my quick guide just to clearify how this is done on (Windows Vista/7) PC with Sdk r11!!!
Install Java and SDK
First Install Java jre, jdk... http://www.oracle.com/technetwork/java/javase/downloads/index.html
install programs and restart if required...
Now go visit the SDK site and download latest version (r11).zip... http://developer.android.com/sdk/index.html
Now unzip file directly to C: drive.. and rename folder to 'android'..
open 'android' folder and run 'sdkmanager.exe' install updates and packages than restart if neccessary..
ADB Driver install...
Now go to your device and enable 'usb debugging' located in settings>applications>development...
Now plug device into computer via usb and DO NOT mount device (storage) to computer!!
Now press START button on computer desktop..
Right-click on 'computer' and select properties..
Now select 'Device Manager' on upper left corner of newly opened window..
Look for device named 'Android' and open selection.. right click on under-link and select 'install drivers' or 'update drivers'...
Now select browse and go to this location than press ok..
C:/(sdk folder)/extras/google/usb_drivers
Now should say driver has been installed correctly..
Test method: Open CMD
cd/
cd (sdk folder)/platform-tools
adb devices
Should see device and number pop-up...
(ADB is located in Platform-tools folder now along with 2 .dll files needed for fastboot to work)
Fastboot Drivers Install
First powe off device, than power on holding (Back+Power)
Now plug usb cable from computer into device..
Do same exact method as 'ADB Driver Install' method..
(Fastboot drivers are located in same folder as ADB drivers)
Now to run fastboot mode in cmd prompt enter this..
cd C://
cd (sdk folder)/platform-tools
Should see device and number pop-up...
Alt method is to copy the 2 .dll files located in 'platform-tools' folder and paste them into 'tools' folder, than fast boot will run correctly off this in cmd prompt...
cd/
cd android/tools
fastboot devices
Should see device and number pop-up...
Also you could just go to ..
C:/android/extras/google in 'windows explorer'
and move the 'usb_drivers' folder to root of sdk folder (android) so then all the older guides out there for installing the drivers would actually kinda make sense.. lol
if i missed anything please feel free to add a comment!!
Edited for brevity: I'm setting up a Galaxy Tab 10.1 Retail with a W7 64 machine.
I completed the ADB section of your guide just fine and went to the Fastboot section. It says to power on using back+power. When I hold power+down volume (only option?) I end up in CWM Recovery.
Should I just power on normally and finish the guide or is there something else I should do?
Thanks for the guide btw
MarcAntonyy said:
Edited for brevity: I'm setting up a Galaxy Tab 10.1 Retail with a W7 64 machine.
I completed the ADB section of your guide just fine and went to the Fastboot section. It says to power on using back+power. When I hold power+down volume (only option?) I end up in CWM Recovery.
Should I just power on normally and finish the guide or is there something else I should do?
Thanks for the guide btw
Click to expand...
Click to collapse
well to install the fastboot driver you need to be in fastboot mode on your device... for the G1 it is back+power...
Ok, I tried it again and I left out a detail (sry). When I power on with pwr+left vol it gives me two icons. One is an Android in a box, which takes me to recovery. The other is an icon that says 'Downloading'.
This time I went to it and now I'm at a screen which says
ODIN3 Download Mode
(Protocal v2)
Reason: Force Key
Secure Mode: Nonsecure
Check Signature: Check
Waiting USB Cable.....
Click to expand...
Click to collapse
And then it has a big Android in the middle of the screen with
Downloading.....
Do Not Turn Off Target!!
Click to expand...
Click to collapse
written under it.
Ok, I hooked up the USB and went through the steps and typed in the first two commands and am now in CMD at:
C:\Android\platform-tools>
But when I type in the "..\tools\fastboot.exe devices" command it says its not recognized as an internal or external command, operable program, or bath file
Btw, after I connected the USB, I got an additional line of text under "Waiting for USB" that says "===> Connected! Press the [Start] of Odin3!!"
***Update
Ok, so I copied the .dll files into Tools and ran CMD again and this time I at least did not get that error message, but it displayed no output at all, other than to begin another prompt at:
C:\Android\Tools
And that's where I'm at now.
wel uhhmmm this guide is for the G1... lol im not really sure what downloading mode is... if that is your version of fastboot than just follow the B. Instructions for the ADB driver install... the directions are the same exact for both..
Heh. Yeah its all good. I was able to install CWM and Root it, but I would like to get ADB/Fastboot working. Thanks for your help and patience with me
yeah no problem.. sorry if i couldnt help but the only thing i know is how to get it workin on G1 lol
i see many people on the G1 thread with sdk, adb and fastboot issues... FOLLOW THIS GUIDE!!! It is instructions for latest sdk Vr11... i promise this helps..
Thanks for the guide. Been trying to get ADB up & running on Vista with no success. I'll give this a try.
no problem.. sorry if i dont answer questions right away but send me a pm or comment on here and i will try to help as soon as possible!!!
ldrifta said:
no problem.. sorry if i dont answer questions right away but send me a pm or comment on here and i will try to help as soon as possible!!!
Click to expand...
Click to collapse
i do all waht you said but i can t see the number of my device i just got
did you manually install the drivers?
adb is acceses in platform-tools directory and fasboot is in tools directory.. the drivers for each are located in extras/google/usb_drivers
ldrifta said:
did you manually install the drivers?
adb is acceses in platform-tools directory and fasboot is in tools directory.. the drivers for each are located in extras/google/usb_drivers
Click to expand...
Click to collapse
Hi,
I have the same problem:
I manually install the drivers choosen located in extras/google/usb_drivers on device manager
then it say cash: "windows did fond no driver for your device.
I tried with XP SP3, Vista, Seven: always same problem
What is your device, this guide is for the dream but the same steps can be used for other devices, but you need the proper drivers for your device
Sent from my Nexus 4 using XDA Premium 4 mobile app
My Transformer informed me of an OTA update, which I tried to perform. It stuck on the boot screen and wouldn't go any further. I managed to wipe it and get it going again by switching off and pressing power and volume down, so I rebuilt it and it again wanted to do the update - with the same result.
I tried side-loading the update and again, it froze, so I downloaded and ran NVFLASHTF and now I can't get anything on the display whatsoever. All I can do is connect it to my PC and it makes the familiar connection sound and I can get to the SD card, but nothing else.
I need someone to show me what to do step-by-step as if I was completely stupid (which I obviously am!).
Please help if you can.
TIA
the nvflash sticky in the dev section includes a youtube video.
although the most likely reason your nvflash didn't work, is you extracted the files in the wrong place. make sure they are in the same place as the download.bat file.
Sent from my Transformer TF101 using Tapatalk
I have all the nvflash files in the same folder as extracted from the .zip file. I even have Prime 1.6 in the folder.
All I seem to be able to do is press the power button and either Up-vol or down-vol (or both) and the computer disconnects and immediately reconnects. When I run the download.bat file, it seems to run and complete the formatting and then download something and the dos box disappears at that stage. The tablet is showing the following...
Entering NvFlash recovery mode / Nv3p Server
Chip Uid: 027c100040a0b2d7
Click to expand...
Click to collapse
That is the only thing I can get to display - and, of course, it stays like this until I try to reboot again.
copy and paste what you get when you run the batch file into here...once it finishes
Pretty sure the tf should reboot on its own if done right.
Did you also check the md5sum of the downloaded files?
I followed these instructions..worked perfectly
http://tabletroms.com/forums/transf...ock-3-1-stock-3-2-recovery-roms.html#post9968
The Dos box disappears when it finishes so I can't paste it here and yes, I checked the files. In fact, I tried it on three different PCs (W7 64-bit, W7 32-bit and XP Pro 32-bit), all without success.
Have you plugged it straight to power and switch it on?
Yes - no difference.
I think you need nvflash experts help.
Only thing i can think of is the old adb way to transfer a blob file...
Or...
Open a command prompt and go to the directory with the batch file and then run it ..dont double click but just type it in the dos window.. once it finishes it shouldn't close the window and you can see what happens.
maybe try a different usb port, I have 4 ports on the front of my pc but for some reason only ONE port works when i try to nvflash,also have problems if I use a hub or extend the cable in any way
Malandro2011 said:
I think you need nvflash experts help.
Only thing i can think of is the old adb way to transfer a blob file...
Or...
Open a command prompt and go to the directory with the batch file and then run it ..dont double click but just type it in the dos window.. once it finishes it shouldn't close the window and you can see what happens.
Click to expand...
Click to collapse
Ok, the second option got me a little bit of info. Bootloader.bin is installing but it is telling me that the file 'recovery.img' is not found.
you can prevent the dos window from closing by starting the command via command line.
start > run > cmd (enter)
dir c:\where\nvflash\is\located (enter)
download.bat (enter)
OK, it's official - I'm an idiot!
I had downloaded the nvflash version of Prime 1.6 but hadn't extracted the files! I now have a working version of Prime 1.6 and am restoring the data as I type.
Thanks for all your help, especially the suggestion of running download from a dos prompt, which let me see where I was going wrong.
Excellent!
Glad it's all sorted
I recently downloaded an ICS-based, Cynagen 9 ROM. It was making my Infuse very hot, so I decided to restore back to my previous ROM (Ethereal). I've tried Odin (can't get COM## to appear on it) and Heimdall (installed drivers, new version of Java, still doesn't recognize device). I don't want to pay to have it fixed again, so does anyone have any suggestions as to how I can fix myself? I have a blue CWM. Thanks.
GAPY427 said:
I recently downloaded an ICS-based, Cynagen 9 ROM. It was making my Infuse very hot, so I decided to restore back to my previous ROM (Ethereal). I've tried Odin (can't get COM## to appear on it) and Heimdall (installed drivers, new version of Java, still doesn't recognize device). I don't want to pay to have it fixed again, so does anyone have any suggestions as to how I can fix myself? I have a blue CWM. Thanks.
Click to expand...
Click to collapse
I flash a gb rom in blue cwm to get....red cwm, then flash a gb ROM again...
Have you tried diff usb port & cable....pc?
bigjoe2675 said:
I flash a gb rom in blue cwm to get....red cwm, then flash a gb ROM again...
Have you tried diff usb port & cable....pc?
Click to expand...
Click to collapse
I tried to reflash Ethereal ROM but it doesn't work. Oh, hell, I may just get GSIII on Verizon and call it a day.
GAPY427 said:
I tried to reflash Ethereal ROM but it doesn't work. Oh, hell, I may just get GSIII on Verizon and call it a day.
Click to expand...
Click to collapse
way to throw in the towel...some don't have that option...but XDA is learning experience, not for the towel tossers...
but if you require and want it we can provide it for you any and some assistance.
if you no longer require the thread you can click that triangle to the right of your op...and tell mods to close this thread..
thx
Sounds like if you would do a battery pull and get to download mode you could odin or heimdall back but if ya wanna toss money away to upgrade that's cool too
Sent from my SGH-I997 using xda premium
dawsndev said:
Sounds like if you would do a battery pull and get to download mode you could odin or heimdall back but if ya wanna toss money away to upgrade that's cool too
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
That's it -- I tried Odin and Heimdall but they didn't work. I downloaded the drivers several times, but both programs couldn't recognize my device. I couldn't see the COM## in Odin when I plugged in my Infuse.
bigjoe2675 said:
way to throw in the towel...some don't have that option...but XDA is learning experience, not for the towel tossers...
but if you require and want it we can provide it for you any and some assistance.
if you no longer require the thread you can click that triangle to the right of your op...and tell mods to close this thread..
thx
Click to expand...
Click to collapse
I want to fix my Infuse, but it becomes frustrating when you try these programs (Odin, etc.) and it isn't successful. I can't reboot my phone into anything right now (a new ROM, a restore, etc). It's stuck in the blue recovery.
to get COM## Try using a different usb plug. That has always been my fix for that issue
TheDSMjuggalo said:
to get COM## Try using a different usb plug. That has always been my fix for that issue
Click to expand...
Click to collapse
can I get in bluerecovery?
Sent from my SGH-I997 using xda premium
bradman117 said:
can I get in bluerecovery?
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
using a different usb port is for odin. download and flash the modded 3e rom found here: http://forum.xda-developers.com/showthread.php?t=1092021
Then flash over the rom you wanted thru the recovery
GAPY427 said:
I want to fix my Infuse, but it becomes frustrating when you try these programs (Odin, etc.) and it isn't successful. I can't reboot my phone into anything right now (a new ROM, a restore, etc). It's stuck in the blue recovery.
Click to expand...
Click to collapse
Since you're stuck in recovery and can't get Heimdall or Odin to work, you'll need to use adb to do what I'm about to explain. So, let me know if you need a tutorial on using adb. You can use adb to push items to /sdcard/ while in CWM recovery. Using adb, put the rom that you want on the internal sdcard and put Zen Arcade's Infusion-Z kernel zip there as well. Get the kernel here:
http://forum.xda-developers.com/showthread.php?p=25724526
Then, use the install from zip feature in CWM recovery to flash Zen's kernel to the phone. After the kernel flash, unplug the USB cable and shut the phone off by holding down the power button (it won't boot into anything yet). Then hold the power button and two volume buttons. When the Samsung logo appears, release the power button and keep holding the volume buttons until you are in red recovery. Go to mounts and storage and format system, data, and cache. Then, go back to flash your rom and then reboot. If you're still wanting to throw in the towel, mail it to me and I'll do it for you.
Sent from my SGH-I997 using Tapatalk 2
TheDSMjuggalo said:
to get COM## Try using a different usb plug. That has always been my fix for that issue
Click to expand...
Click to collapse
I've tried that several times. My device is not recognized by Odin.
jscott30 said:
Since you're stuck in recovery and can't get Heimdall or Odin to work, you'll need to use adb to do what I'm about to explain. So, let me know if you need a tutorial on using adb. You can use adb to push items to /sdcard/ while in CWM recovery. Using adb, put the rom that you want on the internal sdcard and put Zen Arcade's Infusion-Z kernel zip there as well. Get the kernel here:
http://forum.xda-developers.com/showthread.php?p=25724526
Then, use the install from zip feature in CWM recovery to flash Zen's kernel to the phone. After the kernel flash, unplug the USB cable and shut the phone off by holding down the power button (it won't boot into anything yet). Then hold the power button and two volume buttons. When the Samsung logo appears, release the power button and keep holding the volume buttons until you are in red recovery. Go to mounts and storage and format system, data, and cache. Then, go back to flash your rom and then reboot. If you're still wanting to throw in the towel, mail it to me and I'll do it for you.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I'll need a tutorial on adb.
GAPY427 said:
Yes, I'll need a tutorial on adb.
Click to expand...
Click to collapse
I've put together a package with all that you'll need for adb. Use these instructions to move the files that I mentioned in my earlier post.
First, let's make sure that we are on the same page with drivers, since you have had trouble with both Heimdall and Odin.
1.) Unplug USB cable.
2.) In the Windows Control Panel, go to "Programs and Features" or "Add/Remove Programs" and uninstall any instances of Samsung Kies and SAMSUNG USB Driver for Mobile Phones.
3.) Download and install THIS version of SAMSUNG USB Driver for Mobile Phones.
4.) After installing the driver, plug in USB cable, and give Windows a moment to setup the driver. When your connection is ready, a USB cable with a check beside it should appear in the Windows system tray.
You can give Odin another try, and it should work for you now with the new driver, or you can move forward with using adb to do what you need.
1.) Download and unzip THIS adb package.
2.) Browse to the folder containing adb.exe. Hold down shift and right click with the mouse; then choose "Open command window here".
3.) Make sure that you are in CWM recovery, and in the Windows command prompt, type
Code:
adb devices
If all is working correctly, your device should appear in the list.
4.) Place any files that you want to move to the device in the same folder as adb.exe.
5.) Then do this for each file: Type the command below, but replace fullfilename with the full name of the file.
Code:
adb push [I]fullfilename[/I] /sdcard/
When the transfer finishes, you should be able to access the items on your internal sd card. From here you can follow the instructions that I gave in the earlier post.
jscott30 said:
I've put together a package with all that you'll need for adb. Use these instructions to move the files that I mentioned in my earlier post.
First, let's make sure that we are on the same page with drivers, since you have had trouble with both Heimdall and Odin.
1.) Unplug USB cable.
2.) In the Windows Control Panel, go to "Programs and Features" or "Add/Remove Programs" and uninstall any instances of Samsung Kies and SAMSUNG USB Driver for Mobile Phones.
3.) Download and install THIS version of SAMSUNG USB Driver for Mobile Phones.
4.) After installing the driver, plug in USB cable, and give Windows a moment to setup the driver. When your connection is ready, a USB cable with a check beside it should appear in the Windows system tray.
You can give Odin another try, and it should work for you now with the new driver, or you can move forward with using adb to do what you need.
1.) Download and unzip THIS adb package.
2.) Browse to the folder containing adb.exe. Hold down shift and right click with the mouse; then choose "Open command window here".
3.) Make sure that you are in CWM recovery, and in the Windows command prompt, type
Code:
adb devices
If all is working correctly, your device should appear in the list.
4.) Place any files that you want to move to the device in the same folder as adb.exe.
5.) Then do this for each file: Type the command below, but replace fullfilename with the full name of the file.
Code:
adb push [I]fullfilename[/I] /sdcard/
When the transfer finishes, you should be able to access the items on your internal sd card. From here you can follow the instructions that I gave in the earlier post.
Click to expand...
Click to collapse
Followed your instructions. Removed SAMSUNG drivers. Installed drivers in your instructions. Odin did not work. Tried the other method and I receive this message in the Cmd window: 'adb' is not recognized as an internal or external command, operable program or batch file.
GAPY427 said:
Followed your instructions. Removed SAMSUNG drivers. Installed drivers in your instructions. Odin did not work. Tried the other method and I receive this message in the Cmd window: 'adb' is not recognized as an internal or external command, operable program or batch file.
Click to expand...
Click to collapse
You have to be in the exact directory as adb.exe or you'll continue to get that error. Go to the exact folder, hold shift and right click the mouse in that folder window. Choose "Open command window here".
Good luck, and enjoy the holiday.
Sent from my SGH-I997 using Tapatalk 2
jscott30 said:
You have to be in the exact directory as adb.exe or you'll continue to get that error. Go to the exact folder, hold shift and right click the mouse in that folder window. Choose "Open command window here".
Good luck, and enjoy the holiday.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Not working. I'm stuck either in blue recovery or a Galaxy S cyanogen(mod) screen.
GAPY427 said:
Not working. I'm stuck either in blue recovery or a Galaxy S cyanogen(mod) screen.
Click to expand...
Click to collapse
Anyone taking time to help you is going to need more to go on than "Not working." I already know that you're in blue recovery. What's the latest on using adb to push a kernel with red recovery to your device so we can get you back to Gingerbread?
Sent from my SGH-I997 using Tapatalk 2
jscott30 said:
Anyone taking time to help you is going to need more to go on than "Not working." I already know that you're in blue recovery. What's the latest on using adb to push a kernel with red recovery to your device so we can get you back to Gingerbread?
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
I tried pushing a kernel through adb but I didn't see it on my sd card. There were also 4 different choices of kernels (Core A, Core B, etc.). I tried to push A & B but saw neither of them on recovery.
GAPY427 said:
I tried pushing a kernel through adb but I didn't see it on my sd card. There were also 4 different choices of kernels (Core A, Core B, etc.). I tried to push A & B but saw neither of them on recovery.
Click to expand...
Click to collapse
Did you see the transfer in progress in the command line? If so, and if the transfer finished, it's on there. I wonder if you're looking on your external sd card instead of the internal.
Sent from my SGH-I997 using Tapatalk 2
---------- Post added at 08:59 PM ---------- Previous post was at 08:54 PM ----------
Alright, in blue recovery, go to "install zip from sdcard".
Then, go to "choose zip from sdcard". Do you see the items that you pushed with adb listed there? Don't choose "choose zip from internal sdcard". Despite what that sounds like, it's your external sdcard.
This was done on a stock rom (works for 4.4)
I unlocked my bootloader first
http://forum.xda-developers.com/showthread.php?t=2363025&page=1
(you need to do the driver part for adb) (Windows 8 may need to change the "Samsung device", and set the driver to be "Android Bootloader Interface")
if you get a "error: device not found" your drivers are not setup, or you didn't accept the cert on the phone.
Thanks broodplank1337
Download root from
http://download.chainfire.eu/supersu
or for more info read here
http://forum.xda-developers.com/showthread.php?t=1538053
and put it in "C:\adb\sdk\platform-tools" (this is my adb.exe folder)
Download the "Samsung Galaxy S4 (i9505) / Download Recovery" from below
http://www.clockworkmod.com/rommanager
save the recovery-clockwork-6.0.4.4-jfltexx.img to the folder "C:\adb\sdk\platform-tools"
Now open up a command prompt (I did this as "run as administrator")
type "cd C:\adb\sdk\platform-tools" (or what ever the directory you extract your files)
enter this command
adb reboot bootloader <enter>
(or hold vol+/- while booting)
Once in bootloader,
In the command prompt type:
fastboot boot recovery-clockwork-6.0.4.4-jfltexx.img (this takes 1min to load after the file is sent)
This will boot into ClockworkMod
goto "install zip"
goto "install zip from sideload"
in the cmd type
adb sideload UPDATE-SuperSU-v1.80.zip
This sends to the phone and write to the phones Rom.
Now reboot, if asked, select no about the stock recovery overwriting the phone
when you boot into the OS download SuperSu from the market
and we have root without ODIN on a I9505G
I disappear alot and i DON'T read everyone's post
I update this when i need re-root
Sorry for the errors in this post
1. I still receive OTA Update with this root (I had to "clear data" on the "Google Service Framework" and then check for updates).
2. As long as you don't flash a different recover it should allow you to apply new updates. The first time i applied a update it failed half way though it. My phone booted but i could install any apps. It only worked after i put the recovery back and re-updated.
3. Once you have root you can flash a recovery using DD in the shell (backup the recovery first) read "[HOWTO] dump your rom"
Good job on writing this for the i9505g users ^^. I'm glad my root zip worked! hehe
:3
Good one! :good:
btw....
Download ClockworkMod 6.0.3.3 NORMAL from below
http://forum.xda-developers.com/show...light=recovery
aka Miustone_CWM_flash-NORMAL.zip
extract the recovery.img to the folder "C:\adb\sdk\platform-tools"
Click to expand...
Click to collapse
your link is not working... this LINK here is working
hey thanks!!
will give it a try tonight!
Will this work on 4.3?
Sent from my GT-I9505G using xda premium
Attempting to do this and for the life of me I can not get adb sideload to work correctly.
when my device is booted I can see it with adb however when I boot into recovery adb doesn't see the device. I have tried unplugging/plugging the cable on my phone.
I want to get this working so that I can root my device and make a backup of my stock images since I just got the 4.3 OTA. When I first got the phone I managed to flash TWRP on it and then put the SU file on the internal memory and flash it from there but I want to get a backup of the stock recovery before going that route in case there is a 4.4 update at a later point.
So could anyone please tell me what I am doing wrong. When my phone is in recovery my computer sees it but adb doesn't.
I am using windows 7 and (I believe) the latest tools from google. I got them right after I got the GES4 so they are at most a month old.
ChaoticUnreality said:
when my device is booted I can see it with adb however when I boot into recovery adb doesn't see the device. I have tried unplugging/plugging the cable on my phone.
Click to expand...
Click to collapse
Try re-installing the USB drivers while in recovery mode.
Start --> Control Panel --> Device Manager, then find and right-click the "SAMSUNG" or "MSM..." unrecognized device with the yellow exclamation point, choose "Update Driver Software" option, then "Browse my computer", then "Let me pick from a list of device drivers on my computer", then if presented with a list of categories select "All devices", then click "Have Disk..." button, and point to the same place where you downloaded the drivers. Pick "SAMSUNG Mobile USB Composite Device" and click Next. It may complain about the driver not being digitally signed, select "Install anyway."
Chahk said:
Try re-installing the USB drivers while in recovery mode.
Start --> Control Panel --> Device Manager, then find and right-click the "SAMSUNG" or "MSM..." unrecognized device with the yellow exclamation point, choose "Update Driver Software" option, then "Browse my computer", then "Let me pick from a list of device drivers on my computer", then if presented with a list of categories select "All devices", then click "Have Disk..." button, and point to the same place where you downloaded the drivers. Pick "SAMSUNG Mobile USB Composite Device" and click Next. It may complain about the driver not being digitally signed, select "Install anyway."
Click to expand...
Click to collapse
I'll have to try that when I get home. thanks.
ChaoticUnreality said:
I'll have to try that when I get home. thanks.
Click to expand...
Click to collapse
Another quick trick that has worked for me in the past is to simply plug the cable into a different USB port on the computer. Does the same thing as the other suggestion without going through the extra steps. Either way should resolve your problem.
Finally got a chance to try this worked perfectly once I changed USB ports and redid the drivers. Thanks
Great write-up
This was my first ever root on my first ever Android device. It went well.
There were a couple things confusing about the post, I just want to make sure I did things correctly.
]Link to Brood's unlocking the bootloader - Was that just to get the USB drivers installed? I didn't use that Clockworkmod or root.zip file
Not selecting yes on final reboot - With so many "no's", I thought it best to not say yes. Does that mean that if there's another OTA update, root will be lost and have to be redone?
Besides that, the biggest issue was getting good USB drivers. Visiting the Samsung site shows zero downloads for the i9505G phone, so I ended up getting the drivers from "phones-usb-drivers.blogspot.com" (can't post links yet), search Google for "free-download-samsung-gt-i9505g-galaxy", it should be a top hit. The actual download was from Samsung, and that got the drivers working for regular operation and the bootloader.
However, I couldn't find drivers that worked for the sideload of the SuperSU. Ended up having to add entries to the Google USB driver (android_winusb.inf) with the VID and PID values. Here's what I added to the x64 section, in case it helps someone else out:
Code:
;Samsung i9505G (GAA attempt to get adb drivers working)
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&MI_01
At that point when it booted into CWM recovery, I installed the drivers and was able to complete.
Now the happy owner of SuperSU running phone. Thanks again warwolfx0
I hope no one minds, but, I automated this.
<see new version later in thread>
Download that, extract it to a folder, install Koush's universal ADB driver in the ADB_USB folder, and then execute the run.bat and follow instructions.
Credits:
warwolfx0 for the OP
Koush for the universal ADB driver found here: https://github.com/koush/UniversalAdbDriver
warwolfx0 said:
Now reboot, if asked, select no about the stock recovery overwriting the phone
and we have root without ODIN on a I9505G
Click to expand...
Click to collapse
Sorry for what might be a stupid question, but I was not 100% sure based on how you word this.
So, if we follow your method, will we leave stock google recovery intact? I.e. we aren't overwriting it with cwm recovery? If so, that would be nice. All my other rooted devices I've installed custom recovery, but it would be nice to leave this one 100% stock except for the rooting.
Thanks.
Correct.
Etched in blood by a katana
Chahk said:
Try re-installing the USB drivers while in recovery mode.
Start --> Control Panel --> Device Manager, then find and right-click the "SAMSUNG" or "MSM..." unrecognized device with the yellow exclamation point, choose "Update Driver Software" option, then "Browse my computer", then "Let me pick from a list of device drivers on my computer", then if presented with a list of categories select "All devices", then click "Have Disk..." button, and point to the same place where you downloaded the drivers. Pick "SAMSUNG Mobile USB Composite Device" and click Next. It may complain about the driver not being digitally signed, select "Install anyway."
Click to expand...
Click to collapse
I had the same problem but was able to get it working by following the above instructions but then selecting “SAMSUNG Android Phone,” followed by “SAMSUNG Android ADB Interface." (I didn't have an option for "SAMSUNG Mobile USB Composite Device.")
I just rooted my phone following these instructions and it all worked great. Does anyone know if a phone that's been rooted like this will be able to accept and install an OTA update?
Thanks, Alan
carrot34 said:
I just rooted my phone following these instructions and it all worked great. Does anyone know if a phone that's been rooted like this will be able to accept and install an OTA update?
Thanks, Alan
Click to expand...
Click to collapse
Yes.
carrot34 said:
I just rooted my phone following these instructions and it all worked great. Does anyone know if a phone that's been rooted like this will be able to accept and install an OTA update?
Thanks, Alan
Click to expand...
Click to collapse
SamuriHL said:
Yes.
Click to expand...
Click to collapse
I don't have the 9505G yet (couple more days!), but there was a similar issue/discussion on the Nexus 7 board recently, and it was determined that if you were using SuperSU versions prior to 1.55 (which just came out in like the last 24 hours), the root would indeed block OTA's (because of an immutable system flag which was being inadvertently/unnecessarily set by the root process).
Discussion here.
But again, SuperSU 1.55 which just came out fixes the problem, so OTA's will indeed work again. So if you ever get stuck with an OTA, make sure to update SuperSU to latest first.
This is all assuming that the same issue would have presented itself on 9505G, which I would think it might. If not, then ignore this post.
Apparently we also have a device specific Odin flashable auto-root file.
The link below goes to ChainFire's website. The zip includes a version of odin.
http://download.chainfire.eu/348/CF-Root/CF-Auto-Root/CF-Auto-Root-jgedlte-jgedlteue-gti9505g.zip
occupational_hazard said:
Apparently we also have a device specific Odin flashable auto-root file.
The link below goes to ChainFire's website. The zip includes a version of odin.
http://download.chainfire.eu/348/CF-Root/CF-Auto-Root/CF-Auto-Root-jgedlte-jgedlteue-gti9505g.zip
Click to expand...
Click to collapse
We do. I got to test it yesterday and it works great. Restores the proper stock recovery when finished.
Sent from my Xoom using Tapatalk 4