I'm extremely new to this and this website, sort of. So if any of this is wrong impression already sorry. A few weeks ago I rooted my myTouch_4G_Slide, using s-off. I'm pretty sure that went OK as my phone is still currently rootly rooted. Next I tried using a custom rom, i am not exactly sure what I did wrong but, I cannot boot into recovery and when i go into Hboot I get multiple "no image" popping up. I can't factory reset and when i try to boot into recovery my phone gets stuck at the mt4gs screen and i have to take out the battery. Is there anyway to fix this, easily hopefully.
Sent from my myTouch_4G_Slide using XDA App
You said your phone is s-off and "rootly rooted". I assume you meant "permanently rooted"? Did you use the right version of superuser (2.3.6.3 or above) and clockwork recovery image (4.0.0.9)? You can ignore the "no image" message, I get them all the time and I can still boot into recovery no problem.
I have the right superhero version but i don't think I have the right clockwork. How could I fix it, without having to boot into recovery.
Sent from my myTouch_4G_Slide using XDA App
imjames said:
I'm extremely new to this and this website, sort of. So if any of this is wrong impression already sorry. A few weeks ago I rooted my myTouch_4G_Slide, using s-off. I'm pretty sure that went OK as my phone is still currently rootly rooted. Next I tried using a custom rom, i am not exactly sure what I did wrong but, I cannot boot into recovery and when i go into Hboot I get multiple "no image" popping up. I can't factory reset and when i try to boot into recovery my phone gets stuck at the mt4gs screen and i have to take out the battery. Is there anyway to fix this, easily hopefully.
Sent from my myTouch_4G_Slide using XDA App
Click to expand...
Click to collapse
Sounds like you need to reflash your recovery. Since you can get into fastboot still, this is an easy fix.
Just download the recovery image from here -
http://android.modaco.com/topic/343...e-mytouch-4g-slide-unofficial-modaco-edition/
once downloaded, enter hboot and select fastboot. Once your phone says "fastboot usb" on it enter the following command into fastboot -
Fastboot flash recovery c:/android/tools/recovery.img
The "c:/android/tools/recovery" portion of that command will be variable based on where the downloaded recovery image is contained on your computer.
Id say that has a pretty good chance of fixing your prollem =). Keep me posted
Sent from my myTouch_4G_Slide using xda premium
do i have to have adb to do it, because thats learning in progress
imjames said:
do i have to have adb to do it, because thats learning in progress
Click to expand...
Click to collapse
um, yeah. Fastboot is like ADB, but a different tool included in the SDK. Do you have the SDK? It's relatively simple, let me just break it down to maximize simplicity.
1) If you don't have the SDK, download it (in zip format) here. If you do have the SDK,
2) for simplicity's sake, create a Directory on your computer (the hard drive root) entitled "Android" (so that it's c:\Android).
3) If you didn't previously have the SDK, once it is is downloaded, extract the files.
4) assuming you run windows, navigate to the SDK, there's a subdirectory called "tools". Move that folder into the Android folder you created.
5) Now. take that recovery.img that you downloaded... (if you haven't done so yet, look to the link I provided in my previous post) move IT to the Android folder as well
6) open a command prompt and change the directory to the tools subdirectory of the Android folder (type cd c:android\tools), You'll now see a command prompt beginning with C:\Android\tools
7) make sure your phone is connected to your computer and in fastboot mode (select "fastboot" from the Hboot screen, it'll then say "fastboot usb" on the screen). I"m assuming your drivers are already properly installed since you were able to root your phone.
8) type in the following command into the commmand prompt - "fastboot flash recovery c:\android\recovery.img
That should do it =)
Sorry this took awhile, I am having trouble with the command prompt I can't get it to change
Sent from my myTouch_4G_Slide using XDA App
imjames said:
Sorry this took awhile, I am having trouble with the command prompt I can't get it to change
Sent from my myTouch_4G_Slide using XDA App
Click to expand...
Click to collapse
Because:
AndroidAutobot said:
... (type cd/c:android/tools) ...
Click to expand...
Click to collapse
Should be:
cd c:\android\tools
if you installed the SDK to a folder in your C: drive called android. That's what I did too because it makes life easier.
The rest of AndroidAutobots post is what you need to do, this one command was just typed wrong.
Blue6IX said:
Because:
Should be:
cd c:\android\tools
if you installed the SDK to a folder in your C: drive called android. That's what I did too because it makes life easier.
The rest of AndroidAutobots post is what you need to do, this one command was just typed wrong.
Click to expand...
Click to collapse
Oops lol. I cant believe i did that ha ha. Thanks for spotting that =)
I've corrected all the command lines in that particular post. Should be able to follow it step by step without any trouble now.
Sent from my HTC Doubleshot using xda premium
Related
The usual DISCLAIMER: Use at your own risk!
Fastboot mode usually comes up if something went wrong when trying to flash a recovery image, for example when flashing AmonRa recovery or ClockWorkMod. It happened to me several times so I tried to learn to revive it without reflashing the original firmware. Note: This tutorial works only if recovery is the only one broken. (If the ROM itself is broken, then that's a subject for another tut.) In this case, the most logical thing to do is just reflash the recovery image. So how do you do it in fastboot mode? Here's how:
Symptom
You tried flashing a custom recovery like ClockWorkMod or Thunderg, or you flashed an incorrect ROM, and when you rebooted, it showed this screen:
Code:
fastboot mode started
udc_start()
and the phone stays there. When you plugin the phone to your computer's USB, it is detected and the screen has this display:
Code:
fastboot mode started
udc.start()
-- suspend --
-- reset --
-- portchange --
-- reset --
-- portchange --
You will need
1) Your PC and your USB cable for the phone
2) USB drivers for your phone (use B2C from LG).
3) Android SDK (download from here)
4) Java, required to run the SDK (but right now I am not sure if this is required to run fastboot!)
5) ClockWorkMod or AmonRa Recovery.
Here's what to do
1) Assuming phone is turned on in fastboot mode, plug it in to the USB of your PC. You will know that it is detected if you see the the lines "suspend", "reset" and whatnot on the phone's screen.
2) Extract the recovery image from the zipfile downloaded from step#5 above (e.g. LGp500-recovery-v12.img). Place the image file in the same folder where fastboot.exe is (usually in the tools\ folder in the SDK). For your convenience, rename the img file as recovery.img
3) Fire up your command prompt and cd to the directory where fastboot.exe is located. Then type the following command:
Code:
fastboot erase recovery
Once you get the confirmation that it was successful, type this:
Code:
fastboot flash recovery recovery.img
Once you get the success confirmation, reboot the phone, or you can also type (optional):
Code:
fastboot reboot
The phone will reboot itself, and with any luck you should be able to go back to your same old Android bootscreen. Note that no settings were modified here, so this is extremely useful for those who do not want a clean slate after a fastboot nightmare.
Also, note that if this is successful, you can now boot to recovery with the usual button-combos, thus enabling you to flash ROMs and other recovery zips.
Note: On some SDK versions, fastboot may not be included. For your convenience, I have attached the fastboot binary I got from my downloaded SDK. I have also attached AdbWinApi.dll which some user reported is missing in the SDK. Place the DLL in the same folder where fastboot.exe is located.
Questions, just drop me a line here
thanks dude, its very usefull
Nice tutorial for newbies like me, thanks...
Sent from my LG-P500 using XDA Premium App
We already have a tut like this.
@arvinoids
Good tutorial, but you forgot to say that LG USB drivers are needed and that fastboot.exe must be downloaded before (it's no more included in android SDK)
thanks man
d3s3rt_eagle said:
@arvinoids
Good tutorial, but you forgot to say that LG USB drivers are needed and that fastboot.exe must be downloaded before (it's no more included in android SDK)
thanks man
Click to expand...
Click to collapse
You are right! I should add that here. Also, I got the latest SDK to verify and found fastboot.exe under the "tools" folder. Can tell me which SDK version you downloaded?
Usefull, thank you
Sent from my LG-P500 using XDA Premium App
Kudos to arvinoids.
This will be of great help in times of need.
Sent from my LG-P500 using Tapatalk
arvinoids said:
You are right! I should add that here. Also, I got the latest SDK to verify and found fastboot.exe under the "tools" folder. Can tell me which SDK version you downloaded?
Click to expand...
Click to collapse
I have SDK r10 and cannot found fastboot under tools
So i had to download it from htc's website.
d3s3rt_eagle said:
I have SDK r10 and cannot found fastboot under tools
So i had to download it from htc's website.
Click to expand...
Click to collapse
Wow, that's strange. I have r11 and it is included there. For your convenience, I have attached the fastboot.exe from r11 on the first post. Thanks for trying this out.
i have a question... if we don't see the fastboot line on our breaked phone and we see just stuck at LG Logo and the Recovery is broken too, what we can do?! how we can enter in fastboot mode in this situation?
hey
I run the CMD
executed cd command but the next command
"fastboot erase recovery"
gives the following error ( see the image)
Please help
@arvinoids:- mate your work acted as a GOD to me for now. I solved my above issue by just googling the AdbWinApi.dll, downloading it and putting it in the same directory as the fastboot.exe
Thanks mate
DJoptimus-One said:
@arvinoids:- mate your work acted as a GOD to me for now. I solved my above issue by just googling the AdbWinApi.dll, downloading it and putting it in the same directory as the fastboot.exe
Thanks mate
Click to expand...
Click to collapse
Did rom manager messed up your phone?
Sent from my LG-P500 using Tapatalk
lekhwani said:
Did rom manager messed up your phone?
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
Yes. For the first time.
DJoptimus-One said:
Yes. For the first time.
Click to expand...
Click to collapse
How is your phone now?
Sent from my LG-P500 using Tapatalk
lekhwani said:
How is your phone now?
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
Revived now
DJoptimus-One said:
Revived now
Click to expand...
Click to collapse
Good to hear that. I think this is your 2nd or 3rd day and you came across worst o1 modding scenario and overcame it. Kudos to you.
Sent from my LG-P500 using Tapatalk
AdbWinApi.dll is included in platform-tools
DJoptimus-One said:
@arvinoids:- mate your work acted as a GOD to me for now. I solved my above issue by just googling the AdbWinApi.dll, downloading it and putting it in the same directory as the fastboot.exe
Thanks mate
Click to expand...
Click to collapse
Hi. Sorry I was away for the weekend and just got back. Thanks for reporting this. I just did a search on my desktop and found out that AdbWinApi.dll is included in the platform-tools package. I will add the instructions to download the package from the SDK. I'm glad you were able to revive your phone. Thanks again!
pymebrahimi said:
i have a question... if we don't see the fastboot line on our breaked phone and we see just stuck at LG Logo and the Recovery is broken too, what we can do?! how we can enter in fastboot mode in this situation?
Click to expand...
Click to collapse
I'm afraid your issue may not be a subject for this tutorial. Fastboot mode is activated when the phone's recovery image is broken. May I know how you are sure that the recovery is actually broken?
i have already checked xda for a solution but couldnt find one i even checked google and youtube and still found nothing i am in need help bad. i will even pay someone paypal if they can help me with my phone
i downloaded the matrix rom and i liked it but i wanted to go back to ice cream sandwhich for the day so when i tried to go to recovery it froze on the google screen while trying to get to recovery i kept trying and trying but my recovery wasnt working i couldnt get to it. so i went to titanium back up and clicked un-install all system and data because i thought it was when i restored all system and data from ICS but after i did the uninstall i kept getting a force close alot of things and i got all the way down to one and it was process.android i think and everytime i clicked force close it popped right bacj up instently. so i took out the battery and put it back in and now i cant power on my phone it gets stuck on the matrix screen. can you please help me i can only acces the volume up power button menu.
*solved*
Fastboot OEM lock. Fastboot OEM unlock and start the process all over again. Also wipe everything 3 times.
Including system and boot.
Also double check you're installing all the compatible zips.
Sent from my Nexus S using xda premium
it wont let me do any of that it keeps saying waiting for device then gets stuck on that ive installed pdanet but it keeps giving me a htc sync error =1 and my bootloader and everything was already unlocked i dont know what to do i cant turn my phone on or get to recovery. thats why im paying 100 dollars to anyone who can help me restore my phone and make sure its up and running ive been trying for 2 days now and thats my work phone and everything im stressed
Serious_Beans said:
Fastboot OEM lock. Fastboot OEM unlock and start the process all over again. Also wipe everything 3 times.
Including system and boot.
Also double check you're installing all the compatible zips.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
when i turn on the phone and it keeps trying to load the matrix animation the phone still connects with my computer and says removable disk f but when i try and click on it. it says please insert a disk into removable disk f
Hmm uninstall all the USB drivers and reinstall them
Sent from my Nexus S using xda premium
Serious_Beans said:
Hmm uninstall all the USB drivers and reinstall them
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
at the bottom of my phone screen it says fastboot statud - FAILInvalid command
If you have the SDK installed on your computer. Here is what you need to do in order to get back into recovery.
#1 Boot your phone into bootloader, Vol up and power
-Plug into computer using usb while in fastboot(bootloader) and see if it recognizes it. Type adb devices it should list a serial number for your device.
( My SDK is installed in c:\android\) so you would type something like cd c:\android\tools and hit enter and then type adb devices )
#2 If you have installed sdk and pdanet drivers and your computer still does not see your phone in fastboot is this. Go to the folder where sdk is installed and copy everything excluding the folders that is in the Platform-tools folder into the tools folder. After that download Stock Phone files unzip it into a folder on desktop.
Dont run the script yet, what you have to do is after you unzip the stock look in the folder you just unzipped them in and you should see a file called fastboot, adb, and some other .dll's AdbWinApi.dll and etc move only these 4 files to your sdk tools folder.
#3 Now re open a cmd prompt and go back to c:\android\tools (enter) then type in adb devices and your computer should recognize it this time around.
Then all there is left to do is download the recovery of your choice here's mine Recovery and after you download it rename it recovery. After you rename it move it to sdk tools folder and while still in fastboot(bootloader) type in fastboot flash recovery recovery.img
You should now be able to enter recovery and flash roms again
EDIT #1
If you havent setup SDK here is a wiki guide on how to do so http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Make sure you are using the most up to date drivers and then use ADB to install recovery again. If I'm understanding it right I think that's what you need to try.
Sent from my Supercharged MikG'd up EVO 4g while eatin some Chop Suey.
Hit that thanks button if I managed to help.
Envynet said:
If you have the SDK installed on your computer. Here is what you need to do in order to get back into recovery.
#1 Boot your phone into bootloader, Vol up and power
-Plug into computer using usb while in fastboot(bootloader) and see if it recognizes it. Type adb devices it should list a serial number for your device.
( My SDK is installed in c:\android\) so you would type something like cd c:\android\tools and hit enter and then type adb devices )
#2 If you have installed sdk and pdanet drivers and your computer still does not see your phone in fastboot is this. Go to the folder where sdk is installed and copy everything excluding the folders that is in the Platform-tools folder into the tools folder. After that download Stock Phone files unzip it into a folder on desktop.
Dont run the script yet, what you have to do is after you unzip the stock look in the folder you just unzipped them in and you should see a file called fastboot, adb, and some other .dll's AdbWinApi.dll and etc move only these 4 files to your sdk tools folder.
#3 Now re open a cmd prompt and go back to c:\android\tools (enter) then type in adb devices and your computer should recognize it this time around.
Then all there is left to do is download the recovery of your choice here's mine Recovery and after you download it rename it recovery. After you rename it move it to sdk tools folder and while still in fastboot(bootloader) type in fastboot flash recovery recovery.img
You should now be able to enter recovery and flash roms again
EDIT #1
If you havent setup SDK here is a wiki guide on how to do so http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Click to expand...
Click to collapse
can someone help me threw team viewer and just access my computer threw that and help me that way
Envynet said:
If you have the SDK installed on your computer. Here is what you need to do in order to get back into recovery.
#1 Boot your phone into bootloader, Vol up and power
-Plug into computer using usb while in fastboot(bootloader) and see if it recognizes it. Type adb devices it should list a serial number for your device.
( My SDK is installed in c:\android\) so you would type something like cd c:\android\tools and hit enter and then type adb devices )
#2 If you have installed sdk and pdanet drivers and your computer still does not see your phone in fastboot is this. Go to the folder where sdk is installed and copy everything excluding the folders that is in the Platform-tools folder into the tools folder. After that download Stock Phone files unzip it into a folder on desktop.
Dont run the script yet, what you have to do is after you unzip the stock look in the folder you just unzipped them in and you should see a file called fastboot, adb, and some other .dll's AdbWinApi.dll and etc move only these 4 files to your sdk tools folder.
#3 Now re open a cmd prompt and go back to c:\android\tools (enter) then type in adb devices and your computer should recognize it this time around.
Then all there is left to do is download the recovery of your choice here's mine Recovery and after you download it rename it recovery. After you rename it move it to sdk tools folder and while still in fastboot(bootloader) type in fastboot flash recovery recovery.img
You should now be able to enter recovery and flash roms again
EDIT #1
If you havent setup SDK here is a wiki guide on how to do so http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Click to expand...
Click to collapse
Dang you must have put this up like 2 second before I posted mine lol
Sent from my Supercharged MikG'd up EVO 4g while eatin some Chop Suey.
Hit that thanks button if I managed to help.
Maybe you should just try Odin.
http://forum.xda-developers.com/showthread.php?t=1022481
DL: http://droidangel.blogspot.com/2011/05/odin-multi-downloader-flasher-program.html
Greetz
OP... check your PM inbox.
Why on earth have you posted this thread 6 times? Lol
Sent from my Nexus S using XDA App
scottypeterson said:
Dang you must have put this up like 2 second before I posted mine lol
Sent from my Supercharged MikG'd up EVO 4g while eatin some Chop Suey.
Hit that thanks button if I managed to help.
Click to expand...
Click to collapse
after i type adb it says adb isnt recognized as a internel or external cammand operable program or batch file
Ok I don't know if you tried this already but do this:
1. download the recovery img from here:
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
and put it somewhere on ur computer
2. plug phone into comp
3. boot the phone into the fastboot mode with the android guy
4. fastboot erase recovery
5. fastboot flash recovery ____.img
and if you can boot into recovery now, just wipe data, cache, and dalvik cache and flash the ics rom
see if that helps
mathkid95 said:
Ok I don't know if you tried this already but do this:
1. download the recovery img from here:
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
and put it somewhere on ur computer
2. plug phone into comp
3. boot the phone into the fastboot mode with the android guy
4. fastboot erase recovery
5. fastboot flash recovery ____.img
and if you can boot into recovery now, just wipe data, cache, and dalvik cache and flash the ics rom
see if that helps
Click to expand...
Click to collapse
I suggested this about 7 hours and 3 threads ago.. I think the problem is either he doesn't have the proper drivers or SDK setup properly.
Da_Reaper said:
after i type adb it says adb isnt recognized as a internel or external cammand operable program or batch file
Click to expand...
Click to collapse
This leads me to believe that SDK isn't set up properly. If it's set up correct you should be able to access adb without the phone even connected.
Yes thank you guys i love u all
check your mp , excepted if you found the solution.
$100? Lol
Sent from my Nexus S using XDA App
crump84 said:
I suggested this about 7 hours and 3 threads ago.. I think the problem is either he doesn't have the proper drivers or SDK setup properly.
This leads me to believe that SDK isn't set up properly. If it's set up correct you should be able to access adb without the phone even connected.
Click to expand...
Click to collapse
Yeah excuse me for not reading all 6 threads
Sent from my Nexus S using XDA App
So I have my Xoom unlocked and I am trying to flash the recovery in order to root. I have the recovery in the platform tools folder along with fastboot and all that, and I'm able to get the Xoom into fastboot from adb, but I can't get the recovery to flash. I'm typing the name correct. And I'm putting in 'fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img' without the quotes. Honestly I'm a little bit stumped at this point.
I have had the same issue for the past few days I have also tried the steps here no luck.... http://forum.xda-developers.com/showthread.php?t=1249798
supenova3000 said:
I have had the same issue for the past few days I have also tried the steps here no luck.... http://forum.xda-developers.com/showthread.php?t=1249798
Click to expand...
Click to collapse
I used the same guide. It just makes no sense that I can control the Xoom and unlock it, but I can't flash the darn recovery.
williamthegoat said:
I used the same guide. It just makes no sense that I can control the Xoom and unlock it, but I can't flash the darn recovery.
Click to expand...
Click to collapse
I tried moving the files from the tools folder to platform tools still no luck.. all of this for the I C S flash I'm going to keep working on a solution I will let you know if I have any luck!
So I have the android sdk in c:\ , and in the sdk folder I have everything, and in the platform tools I have my fastboot and recovery. I then use cmd to get into adb, then I put the xoom in fastboot. From there I try to flash the recovery, which always fails. I must be doing something wrong here.
Try downloading the IMG again. Or try out the rogue recovery. I actually like rogue better.
Sent from my MB860 using xda premium
I finally got it. In command I needed to direct it to the platform tools folder and then it flashed just fine. I am now rooted. Now to learn about flashing ICS
Thanks for the responses and help guys
Think you have to be stock to flash to ICS, at least that was the word yesterday.
I gave up trying to root just as I found out about the ICS update.
williamthegoat said:
I finally got it. In command I needed to direct it to the platform tools folder and then it flashed just fine. I am now rooted. Now to learn about flashing ICS
Thanks for the responses and help guys
Click to expand...
Click to collapse
Two simple errors:
1) not opening the command window from the folder where you have fastboot and the image files you're trying to flash; and
2) not realizing that you have hidden file extensions in Windows, and typing ...recovery.img.img
williamthegoat said:
So I have my Xoom unlocked and I am trying to flash the recovery in order to root. I have the recovery in the platform tools folder along with fastboot and all that, and I'm able to get the Xoom into fastboot from adb, but I can't get the recovery to flash. I'm typing the name correct. And I'm putting in 'fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img' without the quotes. Honestly I'm a little bit stumped at this point.
Click to expand...
Click to collapse
I assume that you've set up a path in environment variables to run adb and fastboot from ay directory... and are running the flash command from a folder other than where your .IMG file is located. In order for fastboot to find the file you're trying to flash, you actually have to run your flash command from the folder your file is located...
So, cd\...\platform-tools and then flash
The simplest way I perform all of my operations for this:
I leave everything installed into it's default locations. I download tiamat's CWM image and place it into the platform-tools folder.
For Windows 7, I use Windows PowerShell.
For example: Open Start Menu > Type "power" to search, "Windows PowerShell" should show up. (For me, its default at the top - so I press enter to open it)
Once opened: I type this configuration EXACTLY as is: (Keys in <>)
Code:
cd C:\Pr <TAB><TAB> An <TAB> An <TAB> Pl <TAB><TAB> <ENTER>
This above brings me directly to:
C:\Program Files (x86)\Android\Android-sdk\Platform-tools\
Of course, this will be different depending upon your computer setup. I've nailed this routine to get to the path the quickest.
to use FASTBOOT (XOOM already in fastboot mode):
Code:
./fastboot flash recovery rec<TAB><ENTER>
This auto completes the filename as ./recovery-tiamat-r4c-xxxx.img
Of course, depending on how many files/folders you have, you may have to hit <TAB> multiple times. I have to do it 3 or 4 times to select the recovery image I want.
Auto-complete is a nice thing. "./" is added to command from the working directory.
williamthegoat said:
I finally got it. In command I needed to direct it to the platform tools folder and then it flashed just fine. I am now rooted. Now to learn about flashing ICS
Thanks for the responses and help guys[/QUOTE
Worked for me too!!! Thanks!!!
Click to expand...
Click to collapse
Okay, so I posted about a week ago re: my softkey issue and fortunately that was fixed by returning my phone to stock, however, I followed nexushacks method and when it told to do this:
Step 12. Once you get the Android guy with exclamation mark, hit Volume Up and Power button at the same time until you get blue menus.
Nothing bloody happens. Please don't tell me I have to hold it for something like 60 seconds because I. Will. Rage. Lol.
When I try to go into recovery I get that symbol and can't do anything but batt pull. I'm still unlocked and rooted, to my knowledge.
I downloaded ROM Manager because I wanted to flash a recovery on it but it told me that "An error occurred while attempting to run privileged commands"
It also says this when I open Rom Manager "You must root your phone for ROM Manager to function. Superuser was not found at "/xbin/su" or "/system/xbin/su". Use google blabla"
I'm also in the process of trying a command prompt on windows but it keeps giving me the "waiting for device" or awaiting a responce from device" whatever that message is...
Trying to give as info as possible so someone can help a brother out.
I can't deal with this Stock OEM crap anymore *twitch*
Thanks!
Herp Derp
Okay, I didn't realize it was Press the Power button, then the volume up button.
Silly noobs.
So my question, is there a way to get Clockwork Recovery back on now or do I have to go through the whole "Rooting" process again?
I assume you see a lock symbol while booting. This means you're unlocked. Now you'll just need to use fastboot to flash a custom recovery (namely, CWM). NexusShacks details how to setup and use fastboot and i think they provide TWRP now, feel free to use this or just download CWM from here and flash that .img file instead.
After this, download the latest Superuser-3.0.7-efghi-signed.zip and flash that. Note that on a stock ROM it will flash stock recovery on every boot. To change this, rename /system/etc/install-recovery.sh to something else.
But how do I flash a .img file when I don't have Recovery mode?
Or can I use do that through the OEM Recovery (blue screen)?
You flash it with fastboot. Fastboot is a command line tool to flash various images through the bootloader screen. To enter the bootloader, turn off the device and hold Vol. Up + Power. This is the same place you would've typed "fastboot oem unlock", except to flash the new recovery you'll be typing something along the lines of "fastboot flash recovery recovery.img". NexusSHacks teaches you how to do all of this.
Ah sorry, I still get Fastboot and Bootloader mixed up.
Only problem is that I don't know if my computer is recognizing my device when I plug it in through Bootloader.
As mentioned in my original post
"I'm also in the process of trying a command prompt on windows but it keeps giving me the "waiting for device" or awaiting a response from device" whatever that message is..."
I'm at work now and trying to figure out how to do this using Terminal on my mac.
When I type in "cd /nexussrootICS" it keeps on telling me "no such file or directory"
Do I need to put this file in a specific folder? I got this step working on my PC at home but it told me "Waiting for device" the whole time.
Any thoughts?
I'm not particularly familiar with OS X so forgive anything i say that might be off target.
You need to direct the terminal to the relative OR absolute directory of that folder. A relative directory can be done by "cd ./blah", while an absolute will be done by "cd /blah". This is quite confusing for people who aren't used to command line, but very simple once you've done it a few times.
Easiest way aside from magical OS X shortcuts i don't know about is:
-Unzip the files to a "nexus" folder on the desktop, making sure the adb files are in this nexus folder and not a sub folder
-open terminal
-"cd /user/artist/desktop/nexus" or whatever the FULL PATH to the folder is. You should be able to see this through the folders properties or in the file explorer.
-Now you are in the folder, you can use adb and fastboot by just typing those words
I believe OS X can recognise the device straight away so you shouldn't need to install any drivers - at least my linux distros were like that. Installing drivers on Windows is detailed in the video, too.
Ah!!!! I feel like I'm so bloody close...
Okay that part worked perfectly, I found out how to at least direct Terminal to the right location but now I'm lost again...
It's giving me this
"
USER-iMac:nexus user$ ./fastboot-mac flash recovery-clockwork-5.0.2.0-crespo.img
unknown partition 'recovery-clockwork-5.0.2.0-crespo.img'
error: cannot determine image filename for 'recovery-clockwork-5.0.2.0-crespo.img'
USER-iMac:nexus user$
"
TheArtist8 said:
Ah!!!! I feel like I'm so bloody close...
Okay that part worked perfectly, I found out how to at least direct Terminal to the right location but now I'm lost again...
It's giving me this
"
USER-iMac:nexus user$ ./fastboot-mac flash recovery-clockwork-5.0.2.0-crespo.img
unknown partition 'recovery-clockwork-5.0.2.0-crespo.img'
error: cannot determine image filename for 'recovery-clockwork-5.0.2.0-crespo.img'
USER-iMac:nexus user$
"
Click to expand...
Click to collapse
The command should be
./fastboot-mac flash recovery recovery-clockwork-5.0.2.0-crespo.img
You were missing the recovery flag in the command.
Sent from my Nexus S 4G using Tapatalk 2
Also do "man fastboot-mac" in terminal to show all its options.
Sent from my Nexus S 4G using Tapatalk 2
Son of a... alright ill try after my lunch.
Sent from my Nexus S using XDA
Omfg I love you guys.
Thanks so much
I just got into Recovery mode, now on to Cyber-GR
Rather than dive head first in to a situation I can't get myself out of, I'm going to make sure I have everything I need before I begin. I have not received my Htc One x yet, but assuming it comes with 1.85, I follow these steps.
Device setup (hopefully):
Device: Att Htc One X
Filmware version: 1.85
Step one: Root
Following these steps... Edit: http://forum.xda-developers.com/show....php?t=1709296
Quote from iElvis: DO NOT use the one-click method as this can update you to 2.20 if you goof it up, and then you're stuck until there's a new exploit.
Step two: Unlock bootloader
Following these steps... http://briefmobile.com/how-to-unlock-att-one-x-bootloader (from download link here: http://forum.xda-developers.com/showthread.php?t=1672284)
Step 3: Flashing preferred Rom -NOT INTERNATIONAL VERSIONS OF ROMS-:
I have selected Nocturnal Limited Edition... http://forum.xda-developers.com/showthread.php?t=1816853
Following these steps...
How to Flash
Download Rom.zip and save to phone storage
boot into recovery
wipe system
wipe data if coming from another rom
wipe cache
go to flash rom
select the proper download
follow the options in the Aroma installer
Reboot & Enjoy
Some questions before attempting:
"boot into recovery" Meaning I use Twrp2 (from download link here: http://forum.xda-developers.com/showthread.php?t=1677447)
"Wipe system/data/cache" I assume thats done via recovery (Twrp2) correct?
"go to flash rom, select proper download" I assume thats similar to clockwordmod, where you find the Rom on your sdcard (in this case, phone storage) and select it.
"follow options in the Aroma installer" follow instructions in the installer... simple enough.
Is there anything I missed? Devil's in the details.
Edit (more questions): In the following thread ( http://forum.xda-developers.com/showthread.php?t=1709296) it says "Put su in same directory as ADB. Get to adb command prompt and cd into that directory"
Put su (superuser) in same directory as ADB, means that you put Superuser in the same folder as ADB, right?
and cd into that directory. What does this mean?
A cool username said:
Filmware version: 1.85
Step one: Root
Following these steps... http://briefmobile.com/how-to-root-htc-one-x-att (from download link here: http://forum.xda-developers.com/showthread.php?t=1644167)
Click to expand...
Click to collapse
That's the wrong root procedure for 1.85. You need this one:
http://forum.xda-developers.com/showthread.php?t=1709296
DO NOT use the one-click method as this can update you to 2.20 if you goof it up, and then you're stuck until there's a new exploit.
I tried to do this using that post but found it confusing and had some trouble with it. I prefer onexroot.com. they have a great guide here http://onexroot.com/one-x-root/root-any-htc-one-x-windowsmaclinuxattinternationalone-click-method/ hope this helps!
Sent from my HTC One X using xda premium
A cool username said:
Edit (more questions): In the following thread ( http://forum.xda-developers.com/showthread.php?t=1709296) it says "Put su in same directory as ADB. Get to adb command prompt and cd into that directory"
Put su (superuser) in same directory as ADB, means that you put Superuser in the same folder as ADB, right?
and cd into that directory. What does this mean?
Click to expand...
Click to collapse
cd means change directory. It is a windows command prompt command. So you would type "cd C:\adb" if that was where your adb folder was. Folder and directory can be used interchangeably, although directory is more "correct". We only say folder because GUIs use folders to represent directories.
A cool username said:
Rather than dive head first in to a situation I can't get myself out of, I'm going to make sure I have everything I need before I begin. I have not received my Htc One x yet, but assuming it comes with 1.85, I follow these steps.
Device setup (hopefully):
Device: Att Htc One X
Filmware version: 1.85
Step one: Root
Following these steps... Edit: http://forum.xda-developers.com/show....php?t=1709296
Quote from iElvis: DO NOT use the one-click method as this can update you to 2.20 if you goof it up, and then you're stuck until there's a new exploit.
Step two: Unlock bootloader
Following these steps... http://briefmobile.com/how-to-unlock-att-one-x-bootloader (from download link here: http://forum.xda-developers.com/showthread.php?t=1672284)
Step 3: Flashing preferred Rom -NOT INTERNATIONAL VERSIONS OF ROMS-:
I have selected Nocturnal Limited Edition... http://forum.xda-developers.com/showthread.php?t=1816853
Following these steps...
How to Flash
Download Rom.zip and save to phone storage
boot into recovery
wipe system
wipe data if coming from another rom
wipe cache
go to flash rom
select the proper download
follow the options in the Aroma installer
Reboot & Enjoy
Some questions before attempting:
"boot into recovery" Meaning I use Twrp2 (from download link here: http://forum.xda-developers.com/showthread.php?t=1677447)
"Wipe system/data/cache" I assume thats done via recovery (Twrp2) correct?
"go to flash rom, select proper download" I assume thats similar to clockwordmod, where you find the Rom on your sdcard (in this case, phone storage) and select it.
"follow options in the Aroma installer" follow instructions in the installer... simple enough.
Is there anything I missed? Devil's in the details.
Edit (more questions): In the following thread ( http://forum.xda-developers.com/showthread.php?t=1709296) it says "Put su in same directory as ADB. Get to adb command prompt and cd into that directory"
Put su (superuser) in same directory as ADB, means that you put Superuser in the same folder as ADB, right?
and cd into that directory. What does this mean?
Click to expand...
Click to collapse
Did you end up getting root and unlock bootloader to work?
smartnphone said:
Did you end up getting root and unlock bootloader to work?
Click to expand...
Click to collapse
I'm not trying to be rude, but as stated in my opening post, first paragraph. I don't have my one x yet, I am just making sure I have everything before I get my one x so that way I don't have to worry about it.
Bump. Might get my One X today! (^_^)
Will keep updated on what happens
I really hope you find a rootable one.
gunnyman said:
I really hope you find a rootable one.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1842670
Me too. Me too....
It's 1.85!
Sent from my HTC One X using xda app-developers app
Dang.... I cant get the Spoof-Cid to work. Every time I try it says...
Restarting ADB
Pulling files
Checking files
Couldn't pull files from device. Your device was not altered.
Press any key to continue . . .
I'm rooted (checked with terminal emulator) and usd debugging is ON. Set to charge only. No matter what I try, its not working.
A cool username said:
Dang.... I cant get the Spoof-Cid to work. Every time I try it says...
Restarting ADB
Pulling files
Checking files
Couldn't pull files from device. Your device was not altered.
Press any key to continue . . .
I'm rooted (checked with terminal emulator) and usd debugging is ON. Set to charge only. No matter what I try, its not working.
Click to expand...
Click to collapse
Try rebooting your phone... worked for me!
Sent from my SGH-I777 using Tapatalk 2
C3RGIOSE1 said:
Try rebooting your phone... worked for me!
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
I will reboot.... AS MANY TIMES AS IT TAKES!!! -Determined-
A cool username said:
I will reboot.... AS MANY TIMES AS IT TAKES!!! -Determined-
Click to expand...
Click to collapse
Also make sure you use USB 2.0 and not front ports, but main ones on the back, if using desktop :thumbup:
Sent from my SGH-I777 using Tapatalk 2
C3RGIOSE1 said:
Also make sure you use USB 2.0 and not front ports, but main ones on the back, if using desktop :thumbup:
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
its not working (-_-) i have rebooted 5+ times and it wont do it.
A cool username said:
its not working (-_-) i have rebooted 5+ times and it wont do it.
Click to expand...
Click to collapse
I'm going to do mine Super CID on my X, see how it goes... I'll follow up
Sent from my SGH-I777 using Tapatalk 2
C3RGIOSE1 said:
I'm going to do mine Super CID on my X, see how it goes... I'll follow up
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Thankyou so much. In the meantime I will start from square one and see if that works afterwords
A cool username said:
its not working (-_-) i have rebooted 5+ times and it wont do it.
Click to expand...
Click to collapse
Just did my SuperCID - and successfully unlocked BL....I just followed one-click by kennethpenn... where exactly do you get stuck? USB debugging enabled?
Sent from my SGH-I777 using Tapatalk 2
Step by step what I do.
Rooted: achieved. (checked via terminal emulator)
Next I connect my one x via usb, download the supercid file, extract it, run the file, get to where it wants me to press any button, I press any button, it then says it can't get the files and that my device is unchanged, then it closes out of the file. And that's where I'm stuck.
Any questions? At this point I'm thinking I'm missing something incredibly simple...
Sent from my HTC One X using xda app-developers app
Connect phone to computer. Open command prompt. Type adb devices. Does the phone show up ?