Related
Ok so when i try to use rom manager, it says i need flash clockworkmod recovery. So i click on it n it says confirm model n i do, then it says "an error occurred while attempting to run privileged commands." Wat am i doing wrong?? Thanks.
Are you rooted? That's usually a good sign that you aren't.
Sent from my EVO from the Apple Store.
yea i went thro all the steps to root n in titanium backup it says root access is OK. so im confused now.
Make sure you have the latest version of Super User Permissions (2.2.2): http://forum.xda-developers.com/showthread.php?t=682828
When I got that error, it was because I hadn't told SUP to allow ROM Manager quick enough, and RM had timed out on the permission request.
ok so how do i get this onto my phone, i apologize, this is my first android phone.
tarheelsmj12001 said:
ok so how do i get this onto my phone, i apologize, this is my first android phone.
Click to expand...
Click to collapse
Just go ahead and download the zip file su-2.2.2-ef-signed.zip from that thread I linked to. Plug your USB cable into your phone and computer, and either go to Notifications, tap on Chareg Only, and then change it to Disk Drive and press done, then open My Computer (or if on Mac/Linux, double-click the drive on your desktop) and copy the ZIP file directly to SD card, or use ADB to push the file by first turning on USB debugging if it isn't already (Settings>Applications>Development>USB debugging) then open Command Prompt (Terminal on Mac/Linux), go to wherever you have ADB located (usually the Tools folder of the Android SDK) and use this command:
Code:
WINDOWS: adb push *path to ZIP*\su-2.2.2-ef-signed.zip /sdcard/
MAC/LINUX: ./adb puh *path to ZIP*/su-2.2.2-ef-signed.zip /sdcard/
If you used the ADB method: Go ahead and just use the command "adb reboot recovery" (or "./adb reboot recovery" if on Mac/Linux) to reboot into your Recovery. If you used USB Mass Storage, power off your phone, then hold down the Volume Down button, then continue holding Volume Down while holding the Power button. You will then see the bootloader screen (white screen with three skateboarding Androids at the bottom) and can let go of the buttons as soon as you do. Press Volume-Down to highlight "RECOVERY", and then the Power button to select it. Next you'll see the words "HTC EVO 4G" on a white screen (like a normal boot-up) followed shortly after your Recovery image.
Next, use Volume Up/Down to move your selection up/down and use the Power button to select "Install ZIP from SD Card" (or something along those lines). You should have one option for "install update.zip" and one for "Choose ZIP from SD card" (again, or something similar). Choose the latter of the two, and then use Volume Up/Down to select su-2.2.2-ef-signed.zip, and Power to select. Wait a few moments until you're told that the installation was successful, and then select to reboot the phone.
You should then be able to boot into Android, and have the Super User Permissions app installed! Whenever you try to run something which needs root, you'll get a pop-up asking for permission. Go ahead and launch ROM Manager, and you'll get the pop-up, make sure "Remember" is checked, and then press allow. If ROM Manager still complains that it didn't get permissions, re-launch it, and it should work fine.
drmacinyasha said:
Just go ahead and download the zip file su-2.2.2-ef-signed.zip from that thread I linked to. Plug your USB cable into your phone and computer, and either go to Notifications, tap on Chareg Only, and then change it to Disk Drive and press done, then open My Computer (or if on Mac/Linux, double-click the drive on your desktop) and copy the ZIP file directly to SD card, or use ADB to push the file by first turning on USB debugging if it isn't already (Settings>Applications>Development>USB debugging) then open Command Prompt (Terminal on Mac/Linux), go to wherever you have ADB located (usually the Tools folder of the Android SDK) and use this command:
Code:
WINDOWS: adb push *path to ZIP*\su-2.2.2-ef-signed.zip /sdcard/
MAC/LINUX: ./adb puh *path to ZIP*/su-2.2.2-ef-signed.zip /sdcard/
If you used the ADB method: Go ahead and just use the command "adb reboot recovery" (or "./adb reboot recovery" if on Mac/Linux) to reboot into your Recovery. If you used USB Mass Storage, power off your phone, then hold down the Volume Down button, then continue holding Volume Down while holding the Power button. You will then see the bootloader screen (white screen with three skateboarding Androids at the bottom) and can let go of the buttons as soon as you do. Press Volume-Down to highlight "RECOVERY", and then the Power button to select it. Next you'll see the words "HTC EVO 4G" on a white screen (like a normal boot-up) followed shortly after your Recovery image.
Next, use Volume Up/Down to move your selection up/down and use the Power button to select "Install ZIP from SD Card" (or something along those lines). You should have one option for "install update.zip" and one for "Choose ZIP from SD card" (again, or something similar). Choose the latter of the two, and then use Volume Up/Down to select su-2.2.2-ef-signed.zip, and Power to select. Wait a few moments until you're told that the installation was successful, and then select to reboot the phone.
You should then be able to boot into Android, and have the Super User Permissions app installed! Whenever you try to run something which needs root, you'll get a pop-up asking for permission. Go ahead and launch ROM Manager, and you'll get the pop-up, make sure "Remember" is checked, and then press allow. If ROM Manager still complains that it didn't get permissions, re-launch it, and it should work fine.
Click to expand...
Click to collapse
Damn i appreciate ur help n giving me the steps. Just one question, how do i get my command prompt to go to where my ADB is located, its stuck on C:\documents and settings. Thanks again for ur help n sorry for my stupidity.
When i go into my recovery n click on apply sdcard:update.zip, it says failed to open /sdcard/update.zip ( no such file or directory). Wat am i doin wrong??
tarheelsmj12001 said:
When i go into my recovery n click on apply sdcard:update.zip, it says failed to open /sdcard/update.zip ( no such file or directory). Wat am i doin wrong??
Click to expand...
Click to collapse
dont click that one, click the one that says install zip file or something, not update .zip
skittlesV1 said:
dont click that one, click the one that says install zip file or something, not update .zip
Click to expand...
Click to collapse
hmmm i dont have that option
skittlesV1 said:
dont click that one, click the one that says install zip file or something, not update .zip
Click to expand...
Click to collapse
Correct. There's usually two options, one of them being to choose to look for a ZIP file, and the other is sdcard:update.zip. You want to have it look for the ZIP file, and select it off of your card's root directory.
Oh, and to change what directory your command prompt is in, use "cd *path*" which is both for Windows, Mac, and Linux.
yea i dont have that option, only have the one to update.
What Recovery are you using? Perhaps your first step should be to get a better recovery image.
If u don't mind telling me how to do that then ill try n get a better one. N i have no idea which one i have.
Sent from my PC36100 using XDA App
Alright, at the top or bottom of your recovery mode's screen, it will usually tell you what recovery you have (ClockworkMod, Amon Ra, etc.).
To flash a new one, connect your computer and phone, and open up command prompt. Change to wherever you have ADB, and get ready for some fun.
First up, download recovery-RA-evo-v1.7.0.1.img (Amon_Ra's Recovery). Boot your phone into Fastboot by either using "adb reboot bootloader" or turn off you're phone, and turn it back on by holding Volume Down and Power. You'll get the white screen with the skating Androids again. Go ahead and select FASTBOOT. Now, in your command prompt/terminal, use this command:
Code:
fastboot devices
It should acknowledge that fastboot can see your phone. If not, try rebooting again. Once it sees your phone, use this command to flash the recovery:
Code:
fastboot flash recovery *path to file*\recovery-RA-evo-v1.7.0.1.img
Give it some time, and it should succeed. Then go on your phone, select bootloader, and then recovery. You should then boot into RA Recovery 1.7.0.1. Select "Flash zip from sdcard" and select the su-2.2.2-ef-signed.zip file. Give it a bit to do its thing, and then when it's all done, select "Reboot system now"
drmacinyasha said:
Alright, at the top or bottom of your recovery mode's screen, it will usually tell you what recovery you have (ClockworkMod, Amon Ra, etc.).
To flash a new one, connect your computer and phone, and open up command prompt. Change to wherever you have ADB, and get ready for some fun.
First up, download recovery-RA-evo-v1.7.0.1.img (Amon_Ra's Recovery). Boot your phone into Fastboot by either using "adb reboot bootloader" or turn off you're phone, and turn it back on by holding Volume Down and Power. You'll get the white screen with the skating Androids again. Go ahead and select FASTBOOT. Now, in your command prompt/terminal, use this command:
Code:
fastboot devices
It should acknowledge that fastboot can see your phone. If not, try rebooting again. Once it sees your phone, use this command to flash the recovery:
Code:
fastboot flash recovery *path to file*\recovery-RA-evo-v1.7.0.1.img
Give it some time, and it should succeed. Then go on your phone, select bootloader, and then recovery. You should then boot into RA Recovery 1.7.0.1. Select "Flash zip from sdcard" and select the su-2.2.2-ef-signed.zip file. Give it a bit to do its thing, and then when it's all done, select "Reboot system now"
Click to expand...
Click to collapse
Ok so i downloaded the recovery image. Where i get confused is when u say open the the command prompt and change to where i have ADB. So i go to start, run, n then type command?? N i dont understand when u said how to change what directory the command prompt is in, idk wat "cd *path*" means.
Where do you have ADB or the Android SDK?
To open command prompt, go to Start>Run and type cmd then hit enter. Then use the command cd (path to Android SDK)\tools\, so for example, I have my Android SDK in "C:\Program Files (x86)\Android SDK" so I would use cd C:\Program Files (x86)\Android SDK\tools\.
tarheelsmj12001 said:
Damn i appreciate ur help n giving me the steps. Just one question, how do i get my command prompt to go to where my ADB is located, its stuck on C:\documents and settings. Thanks again for ur help n sorry for my stupidity.
Click to expand...
Click to collapse
Dude it's not stupidity. This is the steepest part of the learning curve and there is actually not an easy answer. This drove me nuts when I first started to learn. But it's really fun once you figure it out.
First, follow the steps here: http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
That will give you the SDK folder on your computer. I recommend that you extract the files directly onto the C: drive. That will give you the following path: C:\android-sdk-windows\tools (that will make more sense once you actually follow those steps.
Then, open a Command Prompt on your computer. If you use windows, it's under the Accessories folder on the Start menu. You obviously know this from your earlier post.
Then type the following:
Code:
cd C:\android-sdk-windows\tools
That should bring you to that folder. Everything you ever do that is "ADB" is done from this folder. That means that you actually need to put pertinent files into the "tools" folder there.
Once you are there type the following:
Code:
adb devices
If a long number shows up, then it sees your phone. There you go. If the above doesn't work, it might mean that you have to do another really annoying b.s. maneuver to your computer. Not worth mentioning if you don't have to do it. So just reply if this doesn't work and you can take it from there as far as troubleshooting.
Having said all that, the easiest way to install the new su zip file is to just put it on the your SD card, reboot into recovery, and choose install from SD card, and just choose it.
I would just like to thank u guys so much for ur help n def ur patience. I followed the steps u guys gave me n it worked flawlessly. Im so damn happy now lol, ive been trying to do this for sometime now. Now its time to get some ROMs on this bad boy. Once again, thank u very much guys for ur help, its nice to see ppl helping each other out on here so much.
tarheelsmj12001 said:
I would just like to thank u guys so much for ur help n def ur patience. I followed the steps u guys gave me n it worked flawlessly. Im so damn happy now lol, ive been trying to do this for sometime now. Now its time to get some ROMs on this bad boy. Once again, thank u very much guys for ur help, its nice to see ppl helping each other out on here so much.
Click to expand...
Click to collapse
You're more than welcome, just make sure to hang onto ADB and the Android SDK folders, and where they're are, as they'll be necessary for almost any ROM, upgrade, unlock, etc.!
Hi, I am afraid I brick my Galaxy Nexus (Rooted)
Cause:
I think I wrongly delete some system files in Clockworkmod.
Symptoms:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
2. Press Volume + and - key, I can successfully enter recovery mode.
3.Press Volume - key, I can successfully enter Download mode.
4. I do not have any Stock Rom file (or other Rom file) in the mobile memory.
Urgently need your expertise and help.
Many Thanks
(I am not an expert, so would you mind teach me step by step if you got the solution)
Thanks!!!!
So you cannot boot the phone at all past the Google splash screen? LTE or GSM?
Or does the phone boot fine, but you just can't get into ClockworkMod Recovery?
cbs2002 said:
Hi, I am afraid I brick my Galaxy Nexus (Rooted)
Cause:
I think I wrongly delete some system files in Clockworkmod.
Symptoms:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
2. Press Volume + and - key, I can successfully enter recovery mode.
3.Press Volume - key, I can successfully enter Download mode.
4. I do not have any Stock Rom file (or other Rom file) in the mobile memory.
Urgently need your expertise and help.
Many Thanks
(I am not an expert, so would you mind teach me step by step if you got the solution)
Thanks!!!!
Click to expand...
Click to collapse
The key piece of information for your symptom is in this line:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
The other lines do help provide background as to the other modes such as recovery and download working properly, which indicates the issue is not *serious*.
The symptom you state, where the device does not boot past the boot logo, usually means the device is not able to boot the kernel or boot past the kernel. The boot logo appears while the kernel is being loaded on the device. Generally, after the boot logo and kernel finish loading a boot animation appears which indicates the kernel has usually handed off to the Android OS to continue booting.
My approach would be to load a completely stock ROM in order to restore a working kernel and ROM to the device. I generally perform this step as a baseline to get everything back in working order.
In many instances the ROM is dependent on the kernel. Your situation requires at least a kernel to be loaded and in order to prevent any further issues, it would be best to load a ROM dependent on the kernel being loaded.
A simple way would be to grab the stock factory images from Google's site and load those back onto the device.
Another simple way would be to grab a stock ROM and flash the .zip through CWM in recovery mode.
Hope that helps!
Since you're rooted I'm going to assume you have ADB and the necessary drivers installed.
1.) Download a ROM. It doesn't have to be stock, you can choose any of the ROMs from the development section for your device. Most of the ROMs are packaged with a kernel already.
2.) Save this ROM file to the same folder where you have ADB installed.
3.) Boot your phone into CWM recovery and plug it into your computer.
4.) Use ADB to push the ROM zip file to your phone (/data/media). For example:
Code:
c:\gnex\>adb push rom.zip /data/media/rom.zip
5.) Use CWM to wipe data, cache, and davlik-cache
6.) Install zip from sdcard and flash the rom.zip.
RMarkwald said:
So you cannot boot the phone at all past the Google splash screen? LTE or GSM?
Or does the phone boot fine, but you just can't get into ClockworkMod Recovery?
Click to expand...
Click to collapse
1. I am using GSM
2. Whenever I turn on my mobile, the 'Google' and 'Unlock' logo appears and then freeze, with no more respond at all
* I definitely mess up some system files, but don't know how to restore it because my PC do not recognize my mobile.
Thanks
I am seeing more and more of these threads about "bricked" nexus's is this an issue with how new the phone is or people not following instructions properly as they are too eager to root their phones?
All else fails flash back to stock and count yourself lucky.
To silow,
Thanks for your advice, but fail
1. I put adb.exe, adbwinapi.dll and fastboot.exe (3 files) under my PC C drive (i.e. C
2. I also put a stock Rom (rename as rom.zip) under C drive (i.e. C
3. Boot phone into CWM recovery and plug it into computer.
4. Use cmd command and type c:\gnex\>adb push rom.zip /data/media/rom.zip
5. It fails , It say "Access Denied" (in Chinese, but I translate it into English here)
6. How do I use ADB (it is a ADB.exe file, When I double click it, it only flash up a few page very fast and nothing happen)
Please assist!
To Joeykrim,
I agree that
"Another simple way would be to grab a stock ROM and flash the .zip through CWM in recovery mode."
But how? (according to my symptoms)
The command I gave you was just an example. I didn't spell out the exact details because I thought that you would know how to do it considering you rooted the phone.
If you put the adb.exe and AdbWinApi.dll file in your C: drive, make sure you copy the ROM file to your C: drive too. In the follow example I'm going to use "ROM.zip" but use the name of the ROM file that you downloaded. Also I am assuming you are on Windows XP.
1.) Boot your phone into CWM recovery and then plug it in.
2.) Go to your Start Menu and choose Run. Then type in "cmd" without quotes and hit enter to open a command prompt.
3.) Enter:
Code:
cd c:\
4.) Enter the following to make sure ADB can see your phone:
Code:
adb devices
You should see something similiar to this to confirm ADB can see your device:
List of devices attached
019B756F0C018012 device
5.) Enter the following command to copy the ROM file to your phone. Remember to replace ROM.zip with whatever the name of the ROM file is:
Code:
adb push ROM.zip /data/media/ROM.zip
6.) Use CWM to wipe data, cache, and davlik-cache
7.) Install zip from sdcard and flash the rom.zip.
To Silow,
You have been very helpful, but I fail.
"You should see something similiar to this to confirm ADB can see your device:
List of devices attached"
There is NO device number shown after the phrase 'List of devices attached'
To recap:
a) Phone is already plugged in my PC, under the Clockworkmod Recovery 5.5.0.2
b) adb.exe and AdbWinApi.dll file are under C: drive directly
c) Also type cmd in 'Run', a black Dos window shown C:\windows\system32\cmd.exe
d) c:\>adb devices
List of devices attached
(But no device number show up, it cannot recognize my mobile)
Pls don't give up on me!
: )
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot (edit: wrong!)
Sounds like your ADB USB drivers are not correctly installed. While the phone is under CWM, when you plug it in is your computer attempting to install drivers for a new device?
Download these bare ADB Interface drivers.ADB USB Drivers
Go into Device Manager on your computer and check the device list for any unknown devices or "?" devices. If you need to update those drivers by pointing them to the drivers you downloaded and extracted from that link above.
When the ADB Interface drivers are correctly installed you should see Android Phone listed under under your Device Manager when it's plugged in with CWM recovery loaded.
---------- Post added at 02:36 PM ---------- Previous post was at 02:35 PM ----------
cancerouspete said:
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot
Click to expand...
Click to collapse
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
silow said:
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
Click to expand...
Click to collapse
edit: i did appear to have one missing driver, my mistake. it was listed in device manager as "unknown - full"
its funny cause i never had to use adb from cwm before, never noticed
cbs2002 said:
d) c:\>adb devices
List of devices attached
(But no device number show up, it cannot recognize my mobile)
Click to expand...
Click to collapse
This symptom generally occurs from not having loaded the drivers for the hardware. As with the majority of hardware devices when being connected to a Windows machine, the drivers need to be loaded. Sometimes these are automatically loaded and other times they have to be manual loaded.
As an alternative and for future reference, the android-sdk package contains general USB drives which usually work for Google Nexus devices.
Generally, as this providers a *cleaner* install, best practice as recommended by Google is to download the whole android-sdk .zip and then from the installer download/install the pieces needed, such as platform-tools (containing adb) and USB drivers as opposed to extracting out the adb.exe and .dll file and installing manually.
cancerouspete said:
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot
Click to expand...
Click to collapse
silow said:
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
Click to expand...
Click to collapse
Agreed. To add greater clarification so there is no confusion: adb can't be used from the bootloader.
The /sbin/adbd daemon on the device is only loaded while in normal android boot mode or in recovery mode as called by the init.rc (or on some older devices, recovery.rc) file in the boot process.
Bootloader mode will only work with fastboot while it is in fastboot usb mode.
On some devices, the bootloader has a separate menu for fastboot and on other devices, the fastboot mode is directly entered when entering the bootloader.
Hope that helps clarify!
To silow (and all other helpers)
1. I fail
2. The ADB USB drivers in my PC should be fine as in Device Manager , I can see Android Phone with Android Composite ADB Interface. (No exclamation mark)
3. On the other hand, whenever I plug my mobile into PC, I can see "Unknown-Full"
4. In DOS, when I first type "adb devices" it shows
* daemon not running. starting it now on port 5037*
*daemon started successfully *
List of devices attached
(but NO device number shown!)
5. When I enter adb devices second time, it shows
List of devices attached (No device number shown)
Thank you so much , but it is Hong Kong time (my place) at 0511 am , I didn't sleep all night and I am very tired.
If you don't mind (especially big helper Silow), please give me email so that I capture screen picture and show you in detail (hope it may help)
my email is
[email protected]
I need to sleep now, I will check my email and see you guys or come back this Forum later (several hours later, as I really need some sleep right now)
Pls don't give up on me as this is an expensive mobile. I think the hardware is fine, just need to figure out a way to unbrick it.
Thanks, and see you!
What you need to do is right click on "Unknown-Full" and click on "Update Driver...". Then choose "Install from a list or specific location". Make sure "Search for the best driver in these locations." is checked and "Include this location in the search:" is check. Click on the Browse button and browse to where you extracted the driver files from the link I posted above. Click Next and this should install the correct drivers for you. Afterwards try "adb devices" again to see if ADB now reconizes your device.
To Silow,
Fail.
1. Already installed the drivers you gave me (and there is no 'Exclamation' Mark) in Device manager
2. Situation is the same , Cannot recognize my mobile (i.e. no Device No. after entering adb devices)
3. "List of devices attached" shown in DOS video but without any number.
No other method?
My mobile is really 'bricked' to death?
To Silow and all,
Something important
1. When choose 'install zip from sd card' under CWM, a list of old folder names remains
(e..g gameloft, DCIM, Pictures, etc). That means almost all old files, folders are STILL in my mobile!
2. I have already use the funcion 'Wipe data/factory reset', 'wipe cache partition', ' Wipe Dalvik Cache'
Perhaps my CWM has problem?
What happens when you update drivers for Unknown-Full?
Boot into fastboot and see if your computer recognizes the phone by checking device manager. The key here is to get your computer to see the phone either in fastboot or CWM.
Perhaps try another cable, USB port, or new computer.
The goal is to get Android Phone ADB Composite Interface to show up in device manager either in Fastboot or CWM. Without that done you cannot use Fastboot to flash nor ADB to push a zip file to the phone.
Sent from my Galaxy Nexus using XDA App
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
Problem!!!!
I am a galaxy nexus user. I downloaded the latest version update zip(4.2-beta 3). Then i access in the recovery and choose the "choose zip from sdcard", then i install the latest zip what i download before, but the the error occurred "no file_contexts". Then my phone keep access in the recovery, i cant access the rom. What can i do!? Please someone help me!!!!!! I am the beginner of this area!!!!!!! pls help me
someone said "Prepare your previous worked rom zip file, adb & fastboot app and drivers. Place all in one folder, ex. C:/adb. Connect the phone to computer while in recovery. Open CMD, point to your adb application folder. Then type "C:/adb" (without mark), then "adb devices", cmd will detect your phone. If it says XXXX online, then you can continue. Still in CMD C:/adb, type "adb push romname.zip \sdcard\0". After that, check your phone for copied rom."
is it work?
It looks like you're trying to install ParanoidAndroid, but tell us, do you even have a custom recovery (CWM/TWRP/PhilZ) yet? And is it up to date enough to flash 4.4.x ROMs?
Sent from Google Nexus 4 @ CM11
when it keeps on accessing recovery follow this
for a beginner the perfect place to start
http://galaxynexusroot.com/galaxy-n...galaxy-nexus-gsm-to-android-4-0-4-ota-imm76i/
http://galaxynexusroot.com/galaxy-n...iversal-guidegsmverizonsprintwindowslinuxmac/
folow the guide and flash a stock factory image then a custom recovery then ur fav rom or kernel through custom recovery..
for latest factory image go to https://developers.google.com/android/nexus/images
Hi all,
maybe a very silly question, but when I followed the instructions on https://wiki.cyanogenmod.org/w/Install_CM_for_amami, one of the steps is to open a cmd and type: fastboot getvar version. And well, when I do that and press enter, it says that: fastboot is not recognized as an internal or external command, program or batch file.
The phone is in fastboot mode (a blue light is on), and i have installed sdk and jdk 8u60 on my computer, which runs on windows 7.
Also my computer says that the device driver program is installed.
By the way, when installing jdk, it said I should enter "javac -version" in cmd, but that gave the same notification, howver jdk is installed on my computer.
Who can help me out?
Thanks in advance,
John
Joheee said:
Hi all,
maybe a very silly question, but when I followed the instructions on https://wiki.cyanogenmod.org/w/Install_CM_for_amami, one of the steps is to open a cmd and type: fastbood getvar version. And well, when I do that and press enter, it says that: fastboot is not recognized as an internal or external command, program or batch file.
The phone is in fastboot mode (a blue light is on), and i have installed sdk and jdk 8u60 on my computer, which runs on windows 7.
Also my computer says that the device driver program is installed.
By the way, when installing jdk, it said I should enter "javac -version" in cmd, but that gave the same notification, howver jdk is installed on my computer.
Who can help me out?
Thanks in advance,
John
Click to expand...
Click to collapse
Probably just a typo, but you wrote 'fastbood' in your post. Computer definitely won't recognize that. If you are spelling it right, either 1) you're in the wrong directly in terminal, (cd /(wherever adb is installed), or 2) adb package didn't install correctly, (reinstall). While you're testing it, you can just type 'fastboot', and you should get a list of command options, showing that it is installed.
Sorry yes fastbood was a typo. But what do you mean with: you're in the wrong directly in terminal, (cd /(wherever adb is installed).
A terminal is the same as a command prompt right?
And to reinstall adb package, i would have to delete the platform-tools right? And when i click on delete package, it asks if Im sure about it, bacause it can not be undone.
When you open command prompt, you're 'in a directory', usually in Windows, it's C:/(user)/desktop, or something. You need to get to the directory where adb is. If you installed it with defaults, it's probably C:/adb. If so, once you open command prompt, type 'cd /adb', and hit 'enter'. Then you'll be 'in the right directory'. If adb installed somewhere else, you'll have to find out where, then type 'cd /(whatever)/(whatever)/adb.
I still did not get it working. I deleted the whole android studio package and intalled the sdk tools only now, and installed platform tools in it and tried it all again.
My initial goal was to enter 'fastboot getvar version' in commandprompt. What I tried thus far:
This page (https://wiki.cyanogenmod.org/w/Doc:_adb_intro#Popular_adb_commands) said I should paste ;<path-to-sdk>/platform-tools behind the word Path in Environment variables so I did.
When I open commandprompt it already gives automatically: C:\Users\BTO>
When I just type adb there and hit enter, it says it is not recognized. When I hit cd /adb it says it can't find the given path. (why should I type adb at all by the way, and not fastboot getvar version?)
When I do first 'cd /' it gives C:\> and then adb it also says it can't find the given path.
When I hit C:\>Program Files (x86)\Android\android-sdk\adb it says it can't find the given path.
Deletion of the ;<path-to-sdk>/platform-tools behind Path in the Environment variables does not help.
Thanks for helping me!
Joheee said:
I still did not get it working. I deleted the whole android studio package and intalled the sdk tools only now, and installed platform tools in it and tried it all again.
My initial goal was to enter 'fastboot getvar version' in commandprompt. What I tried thus far:
This page (https://wiki.cyanogenmod.org/w/Doc:_adb_intro#Popular_adb_commands) said I should paste ;<path-to-sdk>/platform-tools behind the word Path in Environment variables so I did.
When I open commandprompt it already gives automatically: C:\Users\BTO>
When I just type adb there and hit enter, it says it is not recognized. When I hit cd /adb it says it can't find the given path. (why should I type adb at all by the way, and not fastboot getvar version?)
When I do first 'cd /' it gives C:\> and then adb it also says it can't find the given path.
When I hit C:\>Program Files (x86)\Android\android-sdk\adb it says it can't find the given path.
Deletion of the ;<path-to-sdk>/platform-tools behind Path in the Environment variables does not help.
Thanks for helping me!
Click to expand...
Click to collapse
First thing you have to do is find out where on your PC the adb files are. The computer won't recognize anything you type with fastboot, adb, etc., unless you're in that directory. I believe adding the environmental variable path is supposed to make that easier, but obviously it's not working out for you, so I would just skip that and find out where the files are, then you can just use 'cd', and go there. It should be easy to do a search in Explorer if you can't find it.
Thank you that you keep helping me.
I worked already 6 hours on it now in total and did not really get any step further. I found the adress of the adb files (the maps were hidden).
I found this page on internet: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
So I followed those steps very precize, I installed the google usb driver in sdk.
Because the commandprompt still did not recognize the device (list of devices did not give any results) I was trying to force installation of the driver on my phone, but that is the step I now got stuck on. When I try to install it in fastboot mode (my device is then called S1Boot Fastboot) it says it can't find any drivers for my device (while I selected the right folder and clicked next??) and the same case when it's just turned on.
Still when I run fastboot getvar version it says <waiting for device>...
The https://wiki.cyanogenmod.org/w/Doc:_fastboot_intro page gives some poor troubleshooting info about this error. When I hit fastboot devices in the right directory it does not even give the waiting for device error. Changing usb ports does not help either.
Maybe it's something with the 'elevated privileges', I dont't know what they mean with that. But I have Administrator rights.
Joheee said:
Thank you that you keep helping me.
I worked already 6 hours on it now in total and did not really get any step further. I found the adress of the adb files (the maps were hidden).
I found this page on internet: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
So I followed those steps very precize, I installed the google usb driver in sdk.
Because the commandprompt still did not recognize the device (list of devices did not give any results) I was trying to force installation of the driver on my phone, but that is the step I now got stuck on. When I try to install it in fastboot mode (my device is then called S1Boot Fastboot) it says it can't find any drivers for my device (while I selected the right folder and clicked next??) and the same case when it's just turned on.
Still when I run fastboot getvar version it says <waiting for device>...
The https://wiki.cyanogenmod.org/w/Doc:_fastboot_intro page gives some poor troubleshooting info about this error. When I hit fastboot devices in the right directory it does not even give the waiting for device error. Changing usb ports does not help either.
Maybe it's something with the 'elevated privileges', I dont't know what they mean with that. But I have Administrator rights.
Click to expand...
Click to collapse
Can you tell me what directory on your PC the adb files are located? As far as drivers, best bet is usually PC companion, or Flashtool.
Hi,
I found some time again. I have installed PC companion, but it doesn't show me how to install drivers. It says the software is up to date.
The location of the driver is C:\Users\BTO\AppData\Local\Android\sdk\extras\google\usb_driver
The location of the ADB files is C:\Users\BTO\AppData\Local\Android\sdk\platform-tools
Thanks
Joheee said:
Hi,
I found some time again. I have installed PC companion, but it doesn't show me how to install drivers. It says the software is up to date.
The location of the driver is C:\Users\BTO\AppData\Local\Android\sdk\extras\google\usb_driver
The location of the ADB files is C:\Users\BTO\AppData\Local\Android\sdk\platform-tools
Thanks
Click to expand...
Click to collapse
If PC Companion is giving you that msg, you might be OK w/ drivers. With that being the location of your adb files, you would open command prompt, and type - cd \Users\BTO\AppData\Local\Android\sdk\platform-tools\adb - then you'll be 'in' the right directory, (just to make sure, look in the 'adb' folder and see if fastboot exe is in there). Your command prompt should show - C:\Users\BTO\AppData\Local\Android\sdk\platform-tools\adb. Then type 'fastboot', and you should get output of command options.
If all goes well and you want to make it easier in the future, just move the whole 'adb' folder to C drive root. Then you'll only have to type 'cd \adb'.
Or you could just open a window in the correct directory, hold right shift button on keyboard and click right mouse button and select "open command prompt here "
Easy peezy
I already found how to fill in the commandprompt from the link from my post of 27 september (you can also go to the map, and shift+rightclick > open command here, then you can misspell anything). But the problem is it doesn't recognize my device. When I go to the right directory and fill in:
fastboot devices > nothing at all
fastboot device > <waiting for device>
fastboot getvar version > <waiting for device>
fastboot > a lot of stuff
adb devices > list of devices (but no items show up)
adb device > a lot of stuff
But to repeat a previous post: "Because the commandprompt still did not recognize the device (list of devices did not give any results) I was trying to force installation of the driver on my phone, but that is the step I now got stuck on. When I try to install it in fastboot mode (my device is then called S1Boot Fastboot in device manager) it says it can't find any drivers for my device (while I selected the right folder and clicked next??) and the same is the case when it's just turned on."
Joheee said:
I already found how to fill in the commandprompt from the link from my post of 27 september (you can also go to the map, and shift+rightclick > open command here, then you can misspell anything). But the problem is it doesn't recognize my device. When I go to the right directory and fill in:
fastboot devices > nothing at all
fastboot device > <waiting for device>
fastboot getvar version > <waiting for device>
fastboot > a lot of stuff
adb devices > list of devices (but no items show up)
adb device > a lot of stuff
But to repeat a previous post: "Because the commandprompt still did not recognize the device (list of devices did not give any results) I was trying to force installation of the driver on my phone, but that is the step I now got stuck on. When I try to install it in fastboot mode (my device is then called S1Boot Fastboot in device manager) it says it can't find any drivers for my device (while I selected the right folder and clicked next??) and the same is the case when it's just turned on."
Click to expand...
Click to collapse
Sorry i missed that... How about Flashtool driver installer? If you DL Flashtool, there's an exe in the 'drivers' folder that will install for you.
Hey you might be using windows 10,8,8.1 if so follow this guide http://forum.xda-developers.com/xperia-u/issues/guide-how-to-install-fastboot-xperia-t2170114
All The Best
Finally getting somewhere, flashtool worked, so fastboot getvar version and all stuff gave some answers.
I extracted the CM11 files, but when I enter fastboot flash boot boot.img in the platform tools directory, it says error: cannot load boot.img.
The CM11 map is in downloads, is is going wrong there? Or something else. The phone is in fastboot mode.
Joheee said:
Finally getting somewhere, flashtool worked, so fastboot getvar version and all stuff gave some answers.
I extracted the CM11 files, but when I enter fastboot flash boot boot.img in the platform tools directory, it says error: cannot load boot.img.
The CM11 map is in downloads, is is going wrong there? Or something else. The phone is in fastboot mode.
Click to expand...
Click to collapse
Try different files. Here's a boot IMG that I've used successfully - https://mega.nz/#!Jh0DETBQ!E-9WTlINpfq5r3PIiKaIXRId7ar8g3c8YHTJha1N6LM - and try this for recovery - https://mega.nz/#!E4UQwIoZ!UFpur2wY3tIAU7SdjuEg5fUA6N4BAVwX_TeK_CFpTyo
Use 'fastoot devices' before flashing to confirm connection.
That didn't work either. I downloaded the files of your links (btw I wouldn't also know what to do with the recovery file), so they are in my Downloads map of my laptop (can I just leave it there?). Then I wrote in the platform tools directory 'fastboot devices' and it gave an answer. When I filled in 'fastboot flash boot boot.img' it said it cannot load boot.img
And maybe I'm getting it wrong, but the size of the CM11 download is 262.87 MB (I took the first snapshot in this list: https://download.cyanogenmod.org/?device=amami), and the size of that boot.img is just 12.1 MB, so I think that that single .img can never be enough for the whole installation of CM11 though?
Joheee said:
That didn't work either. I downloaded the files of your links (btw I wouldn't also know what to do with the recovery file), so they are in my Downloads map of my laptop (can I just leave it there?). Then I wrote in the platform tools directory 'fastboot devices' and it gave an answer. When I filled in 'fastboot flash boot boot.img' it said it cannot load boot.img
And maybe I'm getting it wrong, but the size of the CM11 download is 262.87 MB (I took the first snapshot in this list: https://download.cyanogenmod.org/?device=amami), and the size of that boot.img is just 12.1 MB, so I think that that single .img can never be enough for the whole installation of CM11 though?
Click to expand...
Click to collapse
The boot and recovery files will just enable you to get into recovery. You'll need a ROM file to put a ROM on your phone. There are many to choose from in the 'android development', and 'original android development' threads. To flash with fastboot, put the boot.img and recovery.img files on your PC in the same directory as your adb files, (fastboot, etc). Then type 'fastboot flash boot boot.img', and when that's done, type 'fastboot flash recovery recovery.img, (make sure yor files are named 'boot.img, and 'recovery.img'). Then you can reboot into recovery. Once you download your ROM file, you want it to be on your SD card in the phone. When you get into recovery, you go to your ROM file and install.
Ok so I did this: "To flash with fastboot, put the boot.img and recovery.img files on your PC in the same directory as your adb files, (fastboot, etc). Then type 'fastboot flash boot boot.img', and when that's done, type 'fastboot flash recovery recovery.img, (make sure yor files are named 'boot.img, and 'recovery.img')."
Then I typed fastboot reboot, and it gave: rebooting... with total time 0.008 seconds, and I hit a couple of typed volume down (it said volume rockers on the how-to-wiki, so i guess it doesnt matter up or down) and then the screen turned black (but it's on), and the notification light is off. Battery was 80%, but phone is getting quite warm.
Furthermore, in 'my computer' the phone is not present. So I can not put the download (the CM11 folder of 262.87MB) on the sdcard. When looking into device manager, it could find it at portable devices but with a yellow exclamation mark, with as reason the device does not start (code 10). PC companion also said there is a mistake in the connection between the phone and the computer and advises me to get the phone off the computer and restart it. Good idea?
Update, it's now already over 1,5 hours on the blue 'waving' startscreen, and getting quite hot even. So it is stuck.
Joheee said:
Ok so I did this: "To flash with fastboot, put the boot.img and recovery.img files on your PC in the same directory as your adb files, (fastboot, etc). Then type 'fastboot flash boot boot.img', and when that's done, type 'fastboot flash recovery recovery.img, (make sure yor files are named 'boot.img, and 'recovery.img')."
Then I typed fastboot reboot, and it gave: rebooting... with total time 0.008 seconds, and I hit a couple of typed volume down (it said volume rockers on the how-to-wiki, so i guess it doesnt matter up or down) and then the screen turned black (but it's on), and the notification light is off. Battery was 80%, but phone is getting quite warm.
Furthermore, in 'my computer' the phone is not present. So I can not put the download (the CM11 folder of 262.87MB) on the sdcard. When looking into device manager, it could find it at portable devices but with a yellow exclamation mark, with as reason the device does not start (code 10). PC companion also said there is a mistake in the connection between the phone and the computer and advises me to get the phone off the computer and restart it. Good idea?
Update, it's now already over 40 minutes on the blue 'waving' startscreen, and getting quite hot even.
Click to expand...
Click to collapse
If your phone is stock, it won't boot with the new IMG you flashed. That's also why the computer doesn't recognize it. You can copy your ROM onto the SD card with your computer, using a card reader or adapter. Just flash both IMGs, then unplug, then turn it on, and hit vol up when you see purple. Make sure you type flash 'boot' for the boot, and flash 'recovery' for the recovery, not 'boot' for both. Also, if you want, there are custom IMG files with recovery on xda for stock ROM that you could flash the same way, if you just want to use your stock.
---------- Post added at 04:54 PM ---------- Previous post was at 04:47 PM ----------
Joheee said:
Ok so I did this: "To flash with fastboot, put the boot.img and recovery.img files on your PC in the same directory as your adb files, (fastboot, etc). Then type 'fastboot flash boot boot.img', and when that's done, type 'fastboot flash recovery recovery.img, (make sure yor files are named 'boot.img, and 'recovery.img')."
Then I typed fastboot reboot, and it gave: rebooting... with total time 0.008 seconds, and I hit a couple of typed volume down (it said volume rockers on the how-to-wiki, so i guess it doesnt matter up or down) and then the screen turned black (but it's on), and the notification light is off. Battery was 80%, but phone is getting quite warm.
Furthermore, in 'my computer' the phone is not present. So I can not put the download (the CM11 folder of 262.87MB) on the sdcard. When looking into device manager, it could find it at portable devices but with a yellow exclamation mark, with as reason the device does not start (code 10). PC companion also said there is a mistake in the connection between the phone and the computer and advises me to get the phone off the computer and restart it. Good idea?
Update, it's now already over 1,5 hours on the blue 'waving' startscreen, and getting quite hot even. So it is stuck.
Click to expand...
Click to collapse
Try this for stock - https://mega.nz/#!k0cTUQbS!5XUZhTEK4xBKVBSeO83TEHE3xs9JEpvxt3g1Sc8tVH8