I'm trying to install Cyanogen 4.1.99, but I think I screwed up. According to Fingerlickin I need to install cyanogen's recovery image. First, before I even tried this endeavor, I was running Cyanogen 4.11.1 with the EnochXTra theme. I flashed the recovery image as instructed but, when I rebooted (probably where I messed up) I didn't see the usual recovery mode menu, just some triangle with a "!" in it facing a phone/pda (and NO text). Now I can't flash update.zip files. (Yes I tried ALT+S).
Also Fingerlickin pointed me towards fastboot. I know it's the key right now, but I don't know where to go from here. I think I still have root because I have adb running and could "su" without any complaints.
(I decided to start a new thread because the one I was in had a different problem. Also I would search the forum but I don' know what to search for.)
Tactical Fart said:
I'm trying to install Cyanogen 4.1.99, but I think I screwed up. According to Fingerlickin I need to install cyanogen's recovery image. First, before I even tried this endeavor, I was running Cyanogen 4.11.1 with the EnochXTra theme. I flashed the recovery image as instructed but, when I rebooted (probably where I messed up) I didn't see the usual recovery mode menu, just some triangle with a "!" in it facing a phone/pda (and NO text). Now I can't flash update.zip files. (Yes I tried ALT+S).
Also Fingerlickin pointed me towards fastboot. I know it's the key right now, but I don't know where to go from here. I think I still have root because I have adb running and could "su" without any complaints.
(I decided to start a new thread because the one I was in had a different problem. Also I would search the forum but I don' know what to search for.)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=523558
instructions are in the OP. if you can boot into the rom, use
Code:
flash_image recovery /sdcard/cm-recovery-1.4.img
after putting the new recovery on your SD card
if that doesnt work
Code:
fastboot erase recovery
fastboot flash recovery cm-recovery-1.4.img
with fastboot
instructions to set up fastboot
http://forum.xda-developers.com/showthread.php?t=532719
you shouldnt need to flash the SPL if you have HardSPL or DangerSPL already. Just make sure you have the right drivers, and use the 1.6 SDK since its already out
If you have any others questions or need clarification, post here again
When I was in the rom, I used the terminal emulator, and when I tried to use "su" it said "uid 10031 not allowed to su". I tried "flash_image recovery /sdcard/cm-recovery-1.4.img" under adb and that flopped. Under fast boot I get "Error: cannot load 'cm-recovery-1.4.img'.
*Is nervous*
Tactical Fart said:
When I was in the rom, I used the terminal emulator, and when I tried to use "su" it said "uid 10031 not allowed to su". I tried "flash_image recovery /sdcard/cm-recovery-1.4.img" under adb and that flopped. Under fast boot I get "Error: cannot load 'cm-recovery-1.4.img'.
*Is nervous*
Click to expand...
Click to collapse
what spl do you have and is the recovery.img in the folder you are using fastboot from?
david1171 said:
what spl do you have and is the recovery.img in the folder you are using fastboot from?
Click to expand...
Click to collapse
He has the DangerSPL
and do as david said. the cm recovery image must be in the same folder as the fastboot executable
B-man007 said:
He has the DangerSPL
and do as david said. the cm recovery image must be in the same folder as the fastboot executable
Click to expand...
Click to collapse
reading fail, that's what little sleep for the past few days does
i have a android folder on my C:\ drive with fastboot.exe, adb.exe, and the AdbWinApi.dll so that is the folder i use whenever i need fastboot, i keep the adb.exe and AdbWinApi.dll file in my system32 folder so i can use adb easier.
david1171 said:
reading fail, that's what little sleep for the past few days does
i have a android folder on my C:\ drive with fastboot.exe, adb.exe, and the AdbWinApi.dll so that is the folder i use whenever i need fastboot, i keep the adb.exe and AdbWinApi.dll file in my system32 folder so i can use adb easier.
Click to expand...
Click to collapse
O dont worry he didnt mention it in this thread, it was in the other thread.
I do the same thing haha
@Technical Fart
Don't worry to much, your phone is still booting, its not bricked. Just take it slow and read everything carefully. since you got fastboot already set up, the hardest part is over.
Problem Fixed!!! I didn't know that you had to have the image in that same directory that you had the fastboot command in. Thank-you so much! It feels good to be in a cyanogen rom again.
Tactical Fart said:
Problem Fixed!!! I didn't know that you had to have the image in that same directory that you had the fastboot command in. Thank-you so much! It feels good to be in a cyanogen rom again.
Click to expand...
Click to collapse
NP
Can you please put [SOLVED] in the title?
B-man007 said:
NP
Can you please put [SOLVED] in the title?
Click to expand...
Click to collapse
How do I do that?
Tactical Fart said:
How do I do that?
Click to expand...
Click to collapse
select edit, go advanced, edit the title to include [SOLVED]
ADB working...not so much for fastboot
Hey guys,
I can't seem to get fastboot up and running. My adb is running fine but in all my noobishness I don't know how to get the recovery image running using adb. Is there anyway to do it or am I gonna have to figure out how to get the fastboot going?
to get fastboot going, you phone has to be in bootloader, in fastboot usb mode, and you need to be operating from a folder that has the fastboot.exe, adb.exe and the AdbWinApi.dll (for windows at least). then whatever you are wanting to transfer via fastboot needs to be in that folder as well.
I have all of those things in the tools file. Fastboot shows on my phone but when I type fastboot devices it shows nothing. Also, I tried doing the fastboot commands and it said it is waiting for the device.
When I type fastboot shell to get in to su it gives me the option list as if I just typed in fastboot.
Should I redo the whole adb install process?
Ok, tried going another method and downgrading or changing my rom...no go. Looks like it keeps aborting each installation. This is getting really lame really fast.
Edit: I fixed the problem with my fastboot finally. Apparently when I plugged up my phone in fastboot it recognized it as a mass storage device so I had to uninstall those drivers at startup and reinstall the adb drivers. I think I've spent 4 hours total on trying to fix what happened after this rom and sadly enjoyed the challenge.
simplyTravis said:
Ok, tried going another method and downgrading or changing my rom...no go. Looks like it keeps aborting each installation. This is getting really lame really fast.
Edit: I fixed the problem with my fastboot finally. Apparently when I plugged up my phone in fastboot it recognized it as a mass storage device so I had to uninstall those drivers at startup and reinstall the adb drivers. I think I've spent 4 hours total on trying to fix what happened after this rom and sadly enjoyed the challenge.
Click to expand...
Click to collapse
good to see you got the answer yourself
trust me, those long seemingly pointless hours troubleshooting pays off in the long run. you have a better understanding of how everything works
Hi - I have flash_image in the sdk tools folder but when I do:
ad push flash_image /system/bin is says cannot stat no such file or directory.
Please help!
Erris Bueller said:
Hi - I have flash_image in the sdk tools folder but when I do:
ad push flash_image /system/bin is says cannot stat no such file or directory.
Please help!
Click to expand...
Click to collapse
did you mount the /system directory?
from CMD:
adb shell
#mount -a
then try it.
afterwards then
#umount -a
Related
im having some serious issues with my SU.
i tried temporizer's fix with no help.
it started a while ago when i flashed a theme and i could never get it back.
Ive tried EVERYTHING (to my knowledge which is definitely not vast lol) to no avail. and from what temp and a couple others have told me its a problem with cyan recovery 1.3, but now i cant flash to 1.4. im stuck with no SU, no way to flash a new recovery and pretty much half ass phone. ive never had this type of problem since i rooted back in januaryish. any help would be much appreciated.
anon1ski said:
im having some serious issues with my SU.
i tried temporizer's fix with no help.
it started a while ago when i flashed a theme and i could never get it back.
Ive tried EVERYTHING (to my knowledge which is definitely not vast lol) to no avail. and from what temp and a couple others have told me its a problem with cyan recovery 1.3, but now i cant flash to 1.4. im stuck with no SU, no way to flash a new recovery and pretty much half ass phone. ive never had this type of problem since i rooted back in januaryish. any help would be much appreciated.
Click to expand...
Click to collapse
Download cyan's recovery 1.4 to your sdk tools folder, start the phone in fastboot mode [back+power] folder and run:
Code:
fastboot boot cm-recovery-1.4.img
That should boot the recovery image and you can work from there to reflash whatever you want.
sdk tools folder? and that would beeeeeeee?
apparently im not as savvy as i once thought..... lol
anon1ski said:
sdk tools folder? and that would beeeeeeee?
apparently im not as savvy as i once thought..... lol
Click to expand...
Click to collapse
Errr... you don't have the sdk?
You don't use adb...?!
That's like trying to play football with no limbs..
Get yourself rigged up with this:
http://developer.android.com/sdk/1.5_r3/installing.html
btw.. you won't need to set up eclipse or the adt plugin for this, just make sure your environment variables and java paths are set up as per the guide.
well while football WITH limbs does sound much less entertaining, i am normally no where near a computer, and do almost everything right from my phone.... and i mean everything..... i download all my roms, themes, etc. right to my download folder, find em', rename em' flash em' and im good to go. i went on a computer to get the recovery simply because it downloads wrong on my phone and saves as a text file, seems like it does the same on mozilla for some people but i got it in .img form and its on the root of my card, and nothing.
anon1ski said:
well while football WITH limbs does sound much less entertaining, i am normally no where near a computer, and do almost everything right from my phone.... and i mean everything..... i download all my roms, themes, etc. right to my download folder, find em', rename em' flash em' and im good to go. i went on a computer to get the recovery simply because it downloads wrong on my phone and saves as a text file, seems like it does the same on mozilla for some people but i got it in .img form and its on the root of my card, and nothing.
Click to expand...
Click to collapse
I do a lot of stuff from my phone too tbh, Somehow it satisfies my geek cravings more fully.. But adb is massively useful when you're on the pc.. saves a lot of cramped typing on the device keyboard.
Fastboot will be your saviour in this case though, and you're gonna need a proper box to run that on.
i have NO idea what im doing with adb, i just downloaded it and im just starign at my screen like it tried to feed me a cheeseburger.....
anon1ski said:
i have NO idea what im doing with adb, i just downloaded it and im just starign at my screen like it tried to feed me a cheeseburger.....
Click to expand...
Click to collapse
lol.. adb is pretty simple.. a few examples:
Code:
adb push localpath devicepath # push files to your phone eg: adb push c:\update.zip /sdcard
adb pull devicepath localpath # pull files from device
adb shell # basically a terminal running on your device that you control from your pc.. im sure you can figure this out if you do everything from your phone.
adb shell reboot # guess?
adb shell reboot recovery # go straight to recovery without holding any buttons
fastboot should be in the same folder as adb.. you can use it to flash .img files from the pc or just boot the images without flashing them.
how do i run fastboot, adb, etc. in relation to them running processes on my phone.
i downloaded everything. i just dont know how to run it or if i have to run a couple things, have my phone in recovery or fastboot(im guessing).
god. i feel like a moron.
anon1ski said:
how do i run fastboot, adb, etc. in relation to them running processes on my phone.
i downloaded everything. i just dont know how to run it or if i have to run a couple things, have my phone in recovery or fastboot(im guessing).
god. i feel like a moron.
Click to expand...
Click to collapse
Assuming you're on windows, you'll have to install the adb driver first (not the standard android that windows installs automatically, theres a seperate driver in the usb_driver folder of the sdk). You also need to enable usb debugging on your phone.
Follow this guide if you need to:
http://forum.xda-developers.com/showthread.php?t=532719
You can use adb whatever mode your phone is in.. even when its stuck in a bootloop usually. You don't need to be running anything on the phone, the drivers are switched on by init.rc.
Fastboot can only be run with the phone in fastboot mode (surpisingly).
thanka alot man. im gonna give this all a try.
Good luck
ok. got adb running. ran the command you gave me. it brings up 1.4 but doesnt push it to my phone...... can i actually INSTALL 1.4 from fastboot/adb?
nevermind. figured it out. used common sense and just ran fastboot flash recovery recovery.img and it worked. thanks for everything
my super user still wont work.; so apparently it had nothing to do with the recovery..... im going to wipe, reflash cyan 3.9.1. and see if that works.
flashed CM7 RC2 I think month or so ago. Phone's been running fine slow but fine. Today Im texting the gf and look down and see blank wall paper. Reboot teh phone htc screen comes up vibrates then starts over. Cant do **** with this think besides stick down the front of my pants! Ive powered and booted to hboot, fastboot etc., cant get it to go into recovery any help would be greatly appreciated before I have a stroke!
FAIL. This should be in Q+A. Can you start ADB and access the device? Are you s-off? How did you root the phone? What have you tried? What recovery do you have? Can you read? Is the battery full? Did you search?
well since I rooted the phone about 2 [email protected]##ing years ago memory does not serve. S-off dont know does it do that when you flash the rom or install clockworkmod recovery or the several other steps that you follow when you flash the new ROM? If you have to flash it with the image then no that wasn't an option when I loaded this ROM.
ADB automatically starts when the system boots so I don't have to start it, yes its running no I cannot see the device. Battery was about 75% when the screen went blank.
Im going to ignore the can you read and should be in the Q&A comment el duce as this is the place where the experts play and the other 10000 questions about boot looping reside. Does anyone wanna help or just be an a...?
Questions don't belong in the Development section <---please click link and read....moved to general...
TMcGuire17 said:
well since I rooted the phone about 2 [email protected]##ing years ago memory does not serve. S-off dont know does it do that when you flash the rom or install clockworkmod recovery or the several other steps that you follow when you flash the new ROM? If you have to flash it with the image then no that wasn't an option when I loaded this ROM.
ADB automatically starts when the system boots so I don't have to start it, yes its running no I cannot see the device. Battery was about 75% when the screen went blank.
Im going to ignore the can you read and should be in the Q&A comment el duce as this is the place where the experts play and the other 10000 questions about boot looping reside. Does anyone wanna help or just be an ass?
Click to expand...
Click to collapse
I might be an a.., but I am helping, that's why I asked a bunch of questions. You are not s-off, you would know if you were. ADB is a program you use on your computer, not the phone. I asked because you can flash a recovery image using ADB even though the phone won't boot - so my new question here would be do you have ADB on your computer? You should have ADB if you rooted a long time ago, before there were 1-click root methods. I would recommend charging your phone, since many reboots would kill it. Wait til the charging light turns green. Once it's green boot into the bootloader, then access your phone via ADB and see if recognizes the device. If it does we can work from there. As to your BS about posting in dev because it felt better, that's lame as hell, I would have helped in q+a as well, but I would've been less of an ass because you were posting in the correct section. Anyway, charge it up, and reply if you know how to use ADB or not, then we can move on.
EDIT: I just reread your posts, did you say you can boot into your ROM, just not recovery? If so you can also flash a recovery image using terminal emulator. Let me know.
@TMcGuire17
Let’s take the aggression down about 5 notches and remember that when asking for help it is important to post in the correct section. The fact that you want your question answered quickly does not change the fact that this thread has no place in development. XDA is not tech support and while members can be very helpful you should not expect answers from anyone. When you have to search for the answer or figure out a solution…you are able to learn…understand…and then help others…and that is what XDA is about. Calling people names is never acceptable...I have edited your post. I am tempted to close this thread but I will leave it open in the hopes that you find your answer…but any more name calling or bickering and this thread is closed.
@il Duce
Thanks for helping...but next time leave out the "FAIL. This should be in Q+A" and just report the post...it is only going agitate the situation.
Thanks!
krook6023 (mod team)
krook6023 said:
@il Duce
Thanks for helping...but next time leave out the "FAIL. This should be in Q+A" and just report the post...it is only going agitate the situation.
Thanks!
krook6023 (mod team)
Click to expand...
Click to collapse
LOL ok my bad. I get angry. It's the Irish in me.
Well there you have it! Im as Irish as they come any good conversation between Irish is gonna start with either a beer or a fight. Now that intro's are over....I do have adb loaded need to update it. I'll be back later to check it out and see if I can access the device.
Peace
TMcGuire17 said:
Well there you have it! Im as Irish as they come any good conversation between Irish is gonna start with either a beer or a fight. Now that intro's are over....I do have adb loaded need to update it. I'll be back later to check it out and see if I can access the device.
Peace
Click to expand...
Click to collapse
Scotch-Irish actually, red beard to prove it, lol. You shouldn't need to update your adb If you have adb, and on windows, and it's old, try this: open command prompt from your start menu. type "cd C:\android-sdk-windows\tools" (or just copy paste that with no quotes) then type "adb devices" and if it says "random numers phone" like "2222555555 HTC recovery" or whatever, you're good. Report back.
I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running
TMcGuire17 said:
I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running
Click to expand...
Click to collapse
So now does it show your device?
sent from a series of tubes.
No it still wont execute the command
If it does, type "adb shell" enter "su" enter "flash_image recovery /sdcard/nameof yourrecovery.img"
Thanks il Duce. If I get adb running Ill try it and post back.
TMcGuire17 said:
I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running
Click to expand...
Click to collapse
Hey TMcGuire, If you updated to the latest SDK, the new path for ADB is no longer \Tools (unless you moved a bunch of files) Try c:\androidsdk\platform-tools
TMcGuire17 said:
I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running
Click to expand...
Click to collapse
This is not the correct path. Try typing "cd C:\androidsdk\tools" enter, then try "adb devices" OH YEAH and do you know if you had usb debugging on in the phone settings? You may have to run the RUU if you didnt. That can be done from fastboot, but try the other command first, then the flash command.
Edit, platform tools like posted above mine, sorry I dont have the new sdk.
sent from a series of tubes.
Thanks guys. Yes I have the new sdk and I did find the correct directory for the adb. I can run it now but still no device. Im not sure if I had debugging on or not I thought it did but.......ran adb shell device not found. How about a quick tut on fastboot!
so here is where Im at. fastboot lists my device. I've try to flash the rom from fastboot but no go. Tried to copy the ROM renamed update.zip to the sdcard via fastboot then I was gonna run update but it returned: sending '/sdcard' (72819 KB) FAILED (sounds familiar )(remote not allow)
TMcGuire17 said:
Thanks guys. Yes I have the new sdk and I did find the correct directory for the adb. I can run it now but still no device. Im not sure if I had debugging on or not I thought it did but.......ran adb shell device not found. How about a quick tut on fastboot!
Click to expand...
Click to collapse
look here:http://forum.xda-developers.com/showthread.php?t=958968
read the info, I think jasonmaloney put the zip you need near the end of the thread.
Read, tried failed. It wont push anything to the device. Always comes back as failed remote: not allow
I recently purchased an LG Phoenix by At&t, the problem I have is that I cannot leave ClockworkMod Recovery v5.0.2.0
I rooted it, restarted in recovery. and everything worked fine. I then upgraded my firmware, not sure what version though.. I backed up my phone before I upgraded into the new firmware. I then backedup my phone because it rebooted into recovery. Now everytime it boots it goes straight to Clockwork and I cant get out of it. I restored to my previous restore and it still doesn't work. What could I do? Should I install cwr 3? I read that cwr 5 has bugs and is known to brick phones..
Edit: Also the phone without the sd card still boots into clockworkmod menu
I have a ROM(Phoenix ULTIMATE) I'd like to flash but I'm not sure if I should right now considering I'm stuck at this menu.
Info- in my restores It says;
2011-10-04.21.37.48/
2011-10-04.21.56.13/
I'v tried both.
Another edit with potentially important info getting an error stating;
E: bad boot message "recovery"
Sorry If this is a n00b post.. I'm in sort of a rush because I'm moving in a few hours!
Edit; tried flashing the phoenix, didnt work.
installation was aborted
said i needed to switch to Edify scripting, and amend scripting is no longer supported.
What could I flash too to fix this, please help. I don't care if I lose data. Just need my phone back soon.
I have android SDK.
I was reading up on http://developer.android.com/guide/developing/tools/adb.html and http://forum.xda-developers.com/showthread.php?t=517874 here
Would I be-able to push somesort of boot file or firmware to my phone? Or something in that manner?
THIS:
fastboot erase boot
fastboot erase recovery
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
fastboot reboot
Seems to be perfect for what I should try, where could I get the stock imgs for my phone? (p505)
I moved this here temporarily for you to be assisted...after that it will be moved beck to the right forum
Good luck!!
M_T_M said:
I moved this here temporarily for you to be assisted...after that it will be moved beck to the right forum
Good luck!!
Click to expand...
Click to collapse
thanks
Really hope I can get this fixed soon.
Xery said:
I recently purchased an LG Phoenix by At&t, the problem I have is that I cannot leave ClockworkMod Recovery v5.0.2.0
I rooted it, restarted in recovery. and everything worked fine. I then upgraded my firmware, not sure what version though.. I backed up my phone before I upgraded into the new firmware. I then backedup my phone because it rebooted into recovery. Now everytime it boots it goes straight to Clockwork and I cant get out of it. I restored to my previous restore and it still doesn't work. What could I do? Should I install cwr 3? I read that cwr 5 has bugs and is known to brick phones..
Edit: Also the phone without the sd card still boots into clockworkmod menu
I have a ROM(Phoenix ULTIMATE) I'd like to flash but I'm not sure if I should right now considering I'm stuck at this menu.
Info- in my restores It says;
2011-10-04.21.37.48/
2011-10-04.21.56.13/
I'v tried both.
Another edit with potentially important info getting an error stating;
E: bad boot message "recovery"
Sorry If this is a n00b post.. I'm in sort of a rush because I'm moving in a few hours!
Click to expand...
Click to collapse
Are you on Ecliar , Froyo or Gingerbread ? Sorry , I don't know much but I would like to help
Forever living in my Galaxy Ace using XDA App
EmoBoiix3 said:
Are you on Ecliar , Froyo or Gingerbread ? Sorry , I don't know much but I would like to help
Forever living in my Galaxy Ace using XDA App
Click to expand...
Click to collapse
I didn't change anything, everything is stock I got it yesterday. Rooted it today and it's stuck in recovery. So I guess whatever stock is..
Xery said:
I didn't change anything, everything is stock I got it yesterday. Rooted it today and it's stuck in recovery. So I guess whatever stock is..
Click to expand...
Click to collapse
Try adb .
(If you know what it is)
Type these in:
adb shell
su
reboot bootloader
See if it works
Forever living in my Galaxy Ace using XDA App
I don't know what adb is. :c
Could you explain a bit more about it?
Xery said:
I don't know what adb is. :c
Could you explain a bit more about it?
Click to expand...
Click to collapse
Okay then .
Download and install the Android SDK Tools first
Forever living in my Galaxy Ace using XDA App
EmoBoiix3 said:
Okay then .
Download and install the Android SDK Tools first
Forever living in my Galaxy Ace using XDA App
Click to expand...
Click to collapse
OH Android SDK I have that, just updating.. another 30 minutes..
While we wait, could you explain to me what I'd do with it, and just some tips or things I could do?
Xery said:
OH Android SDK I have that, just updating.. another 30 minutes..
While we wait, could you explain to me what I'd do with it, and just some tips or things I could do?
Click to expand...
Click to collapse
If you have platform-tools , everything will be done in a flash
Forever living in my Galaxy Ace using XDA App
EmoBoiix3 said:
If you have platform-tools , everything will be done in a flash
Forever living in my Galaxy Ace using XDA App
Click to expand...
Click to collapse
"Installed Android SDK Platform-tools, revision 7"
Still installing a bunch of other things though..
"Downloading SDK Platform Android 3.2, API 13, revision 1"
Probably won't be done till tomorrow, horrible internet.
Xery said:
"Installed Android SDK Platform-tools, revision 7"
Still installing a bunch of other things though..
"Downloading SDK Platform Android 3.2, API 13, revision 1"
Probably won't be done till tomorrow, horrible internet.
Click to expand...
Click to collapse
All you need now is platform-tools . The rest can be cancelled .
Use cmd (best if used with administrative rights) to navigate to the Android SDK folder , then to platform-tools .
Once you get there , connect your phone through USB then don't touch it .
In cmd , type:
abd shell
su
reboot bootloader
Forever living in my Galaxy Ace using XDA App
EmoBoiix3 said:
All you need now is platform-tools . The rest can be cancelled .
Use cmd (best if used with administrative rights) to navigate to the Android SDK folder , then to platform-tools .
Once you get there , connect your phone through USB then don't touch it .
In cmd , type:
abd shell
su
reboot bootloader
Forever living in my Galaxy Ace using XDA App
Click to expand...
Click to collapse
How would I use the cmd to navigate to the SDK folder?
I see the cmd, I also see a window called Android SDK and AVD manager, What now?
Xery said:
How would I use the cmd to navigate to the SDK folder?
I see the cmd, I also see a window called Android SDK and AVD manager, What now?
Click to expand...
Click to collapse
Do this
Hold start button and R(on desktop)
Run will open
Type cmd in the box and press enter
A black window will open
CD to sdk dir
E.g.
If u installed sdk in C:\sdk
Then do this
cd C:\sdk\platform-tools
Then this
adb shell
reboot bootloader
cdesai said:
Do this
Hold start button and R(on desktop)
Run will open
Type cmd in the box and press enter
A black window will open
CD to sdk dir
E.g.
If u installed sdk in C:\sdk
Then do this
cd C:\sdk\tools
Then this
adb shell
reboot bootloader
Click to expand...
Click to collapse
Follow his instructions .
Forever living in my Galaxy Ace using XDA App
cdesai said:
Do this
Hold start button and R(on desktop)
Run will open
Type cmd in the box and press enter
A black window will open
CD to sdk dir
E.g.
If u installed sdk in C:\sdk
Then do this
cd C:\sdk\tools
Then this
adb shell
reboot bootloader
Click to expand...
Click to collapse
I opened the cmd, I'm not really suer where I installed SDK but I'm pretty sure it was c:\program files\android\android-sdk\tools
That seemed to work, whenever i type adb shell it says abd is not recognized as an internal or external command, program or batch.
I need more detail because I'm a noob. :/
cdesai said:
Do this
Hold start button and R(on desktop)
Run will open
Type cmd in the box and press enter
A black window will open
CD to sdk dir
E.g.
If u installed sdk in C:\sdk
Then do this
cd C:\sdk\tools
Then this
adb shell
reboot bootloader
Click to expand...
Click to collapse
I opened the cmd, I'm not really suer where I installed SDK but I'm pretty sure it was c:\program files\android\android-sdk\tools
That seemed to work, whenever i type adb shell it says abd is not recognized as an internal or external command, program or batch.
I need more detail because I'm a noob. :/
EDIT: GOTIT! got the dir, i typed adb and it says device not found should i connect my phone correct?
Edit: okay,i did that, it just rebooted my phone and it went back into the CWR.. :c wut now?
Are you able to try and boot into bootloader? Try that. Also, try and flash a new ROM in recovery, test to see if it may be the ROM. Don't be afraid to backup again, you can always access the backups based on date.
-How cruel is the golden rule, when the lives we live are all golden plated-
What's bootloader?
I tried to flash my backups before the firmware update and it didn't work, I also can't find any wp505 roms.. I found a few but they wont help in my situation. Do you know any? My rom is stock as I only rooted and got stuck in cwr.
Thanks!
EDIT: I did do that adb shell, reboot bootloader, didnt work.
Xery said:
What's bootloader?
I tried to flash my backups before the firmware update and it didn't work, I also can't find any wp505 roms.. I found a few but they wont help in my situation. Do you know any? My rom is stock as I only rooted and got stuck in cwr.
Thanks!
Click to expand...
Click to collapse
First off, not to lecture you...but you definitely should look into these kind of things before flashing a ROM.
I haven't looked at the ROMs so I'm not sure. But whatever fancies you, it's just to troubleshoot the problem. The problem itself may actually be the recovery. Do you know how to do logcats in ADB? Try and do a logcat and boot up your device while connected to ADB.
So go "adb logcat". This should show you exactly what your device is doing. When it runs and goes straight to recovery paste all that information into a .txt document and upload it onto xda so others can take a look.
I'll try and help more tomorrow but I have to get some rest. Good luck on getting this fixed.
-How cruel is the golden rule, when the lives we live are all golden plated-
Ok here is the skinny. I have the Sprint HTC 1. Currently rooted and running Beanstalk 4.3 and TWRP 2.5 ... I have read, re read, and read again how to update my TWRP to 2.6.3 and have no luck.
I have tried Terminal Emulator
I have tired Goo Manager. It actually down loads the file. Runs through the process. Never reboots or updates
I have tried Fastboot. For what ever reason my computer does not pick up and adb devices. It shows Fastboot USB
Any thoughts. I had some unlock this one for me and throw TWRP on. All my others I have done myself.
I love TWRP..but if I cannot fix...what is the easiest way to put Philz or CWM on instead?
Want to update a ROM to 4.4 Kitkat but cannot with out an updated recovery
jaykspokane said:
Ok here is the skinny. I have the Sprint HTC 1. Currently rooted and running Beanstalk 4.3 and TWRP 2.5 ... I have read, re read, and read again how to update my TWRP to 2.6.3 and have no luck.
I have tried Terminal Emulator
I have tired Goo Manager. It actually down loads the file. Runs through the process. Never reboots or updates
I have tried Fastboot. For what ever reason my computer does not pick up and adb devices. It shows Fastboot USB
Any thoughts. I had some unlock this one for me and throw TWRP on. All my others I have done myself.
I love TWRP..but if I cannot fix...what is the easiest way to put Philz or CWM on instead?
Want to update a ROM to 4.4 Kitkat but cannot with out an updated recovery
Click to expand...
Click to collapse
While in fastbootusb check your drivers
Device not recognized? (If you are using Windows 8.1 this will most likely not work)
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
BD619 said:
While in fastbootusb check your drivers
Device not recognized? (If you are using Windows 8.1 this will most likely not work)
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Click to expand...
Click to collapse
Updated the drives. In Fastboot now. on my cmd prompt c:\user\user wont tried typing and ADB Devices and nothiing
In fastbootusb type fastboot devices
BD619 said:
In fastbootusb type fastboot devices
Click to expand...
Click to collapse
Now I am thinking it it my computer. Just re enstalled the SDK packet. Changed path to all c:/Android-ADB and says not a recognizable internal or external file
At this point I need some sleep. Eyes are going crossed.
jaykspokane said:
Now I am thinking it it my computer. Just re enstalled the SDK packet. Changed path to all c:/Android-ADB and says not a recognizable internal or external file
At this point I need some sleep. Eyes are going crossed.
Click to expand...
Click to collapse
PM me tomorrow and I'll help you out
BD619 said:
PM me tomorrow and I'll help you out
Click to expand...
Click to collapse
Sorry been a crazy new year. Still need help.
So downloaded SDK pack. I have tried ADB shell. Fastboot ... etc etc. When in Fastboot I run ADB Devices and nothing is found. however if i have the phone on it works.
at this point...maybe a new recovery?
jaykspokane said:
Sorry been a crazy new year. Still need help.
So downloaded SDK pack. I have tried ADB shell. Fastboot ... etc etc. When in Fastboot I run ADB Devices and nothing is found. however if i have the phone on it works.
at this point...maybe a new recovery?
Click to expand...
Click to collapse
While in bootloader/fastbootusb type fastboot devices
adb devices =OS and recovery
fastboot devices = bootloader/fastbootusb
BD619 said:
While in bootloader/fastbootusb type fastboot devices
adb devices =OS and recovery
fastboot devices = bootloader/fastbootusb
Click to expand...
Click to collapse
Ok... recognized a device was attached. So type the following
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
and I got error cannot open 'openrecovery-twrp-2.6.3.0-m7wls.img'
This is TWRPS guidelines
Download the above file into your platform-tools dir. Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery recoveryfilename.img
Note that you will need to change the last part to match the name of the file that you just downloaded. This method requires that you have the drivers installed that come with the HTC Sync software that are available here. You will also need adb and fastboot for your computer.
jaykspokane said:
Ok... recognized a device was attached. So type the following
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
and I got error cannot open 'openrecovery-twrp-2.6.3.0-m7wls.img'
This is TWRPS guidelines
Download the above file into your platform-tools dir. Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery recoveryfilename.img
Note that you will need to change the last part to match the name of the file that you just downloaded. This method requires that you have the drivers installed that come with the HTC Sync software that are available here. You will also need adb and fastboot for your computer.
Click to expand...
Click to collapse
Try
fastboot erase cache <enter>
then
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img <enter>
You did install the android sdk right?
BD619 said:
Try
fastboot erase cache <enter>
then
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img <enter>
You did install the android sdk right?
Click to expand...
Click to collapse
I did. Just to make certain the other night...I down loaded the Android SDK pack. i can run ADB and Fastboot. Pulls all the info etc.
Will try erase cache
jaykspokane said:
I did. Just to make certain the other night...I down loaded the Android SDK pack. i can run ADB and Fastboot. Pulls all the info etc.
Will try erase cache
Click to expand...
Click to collapse
What does this mean?
BD619 said:
What does this mean?
Click to expand...
Click to collapse
Sorry. Meant it just lists all the available command for each respectively...lists the commands etc.
So did the erase and still same error.
All my apps and data are backed up on Titanium. How hard would it be to just have a new recovery installed?
jaykspokane said:
Sorry. Meant it just lists all the available command for each respectively...lists the commands etc.
So did the erase and still same error.
All my apps and data are backed up on Titanium. How hard would it be to just have a new recovery installed?
Click to expand...
Click to collapse
Navigate to the platform tools folder
Press shift and right click inside the folder and choose open cmd here
jaykspokane said:
Sorry. Meant it just lists all the available command for each respectively...lists the commands etc.
So did the erase and still same error.
All my apps and data are backed up on Titanium. How hard would it be to just have a new recovery installed?
Click to expand...
Click to collapse
May be a moot point. I am upgrading to a Team Nocturnal_xR1 which is a 4.4 ROM. So far it has been loading and allowed the file on a TWRP 2.5.0.0 version. I still need to upgrade the TWRP version. Right now looks like it may work.
jaykspokane said:
May be a moot point. I am upgrading to a Team Nocturnal_xR1 which is a 4.4 ROM. So far it has been loading and allowed the file on a TWRP 2.5.0.0 version. I still need to upgrade the TWRP version. Right now looks like it may work.
Click to expand...
Click to collapse
back to square one. LOL.
and no opening cmd from there did not work either
Check PM
I had a similar issue where I needed the updated twrp. I ended up using the original AIO toolkit that I used to root the phone/unlock the phone to begin with.
I found the latest version of the AIO (made by Hasoon: http://www.hasoon2000.info/getdownl...obile,ATT,Sprint)/One_All-In-One_Kit_v3.1.rar) and the latest image of TWRP from here: http://teamw.in/twrp_view_all_devices.
After installing hasoon, stick the downloaded image in the data/recoveries folder w/in the folders from the AIO. Next use the "Your Own Recovery" option under the flash a recovery option and choose that image instead. Worked great for me several times. Hopefully it does for you. Let me know if you have question.
BD619 said:
Check PM
Click to expand...
Click to collapse
hey guys i have a brand new TF701T an im desperately trying to install a custom ROM before i get into using it..
IM trying to install the ROM from http://forum.xda-developers.com/showthread.php?t=2608129&page=30
The first step of manually updating to 10.26.1.18 JB3 is done and I'm now stuck on the CWM step.
I have The ROM and recovery IMG downloaded and im unsure what to do next...Ive googled first and cant really figure it out..
sorry for my newb question but if someone can take pity on me and direct me i will forever be in your debt!!
Put FASTBOOT.EXE and RECOVERY.IMG in the same file.. this i can understand
but........
''Right click + shift on the folder they are in and choose open command prompt here
Boot into the Bootloader by either booting with the Power and Volume Down Buttons held down until you get the 3 icons or by typing the following into the command prompt.
Code:
adb reboot bootloader
Then type the following commands to flash the recovery image:
Code:
fastboot flash recovery recovery.img
fastboot reboot-bootloader''
Is where im lost..
please hgelp..anyone
please..anyone?
Are you unlocked?
Which part is it you don't understand? Opening the cmd prompt?
In Win7 & 8 if you hold the shift key and right click you get a contedt menu with the option to open a command prompt here.
You do have fastboot and adb drivers installed right?
Search XDA for adb fastboot tutorial. Thrre are several very good ones..
Have you managed to get the command prompt open?
sbdags said:
Have you managed to get the command prompt open?
Click to expand...
Click to collapse
In my original post i said i understood 'Have recovery.img & fastboot.exe' in the same file but it turns out i didnt even know what the 'fastboot.exe' was!! I thought it was just another name for the ROM.zip..
SO>> The problem was that i didnt know about the whole android SDK/ platforms tools/ ADB pushing Step..:crying:
after i installed android SDK on my computer and saw the fastboot.exe in the platform tools folder, everything made much more sense
I guess for most guys here it is common knowledge...but not for me. The ROM instructions didnt really specify this clearly nor did the CWM's link instructions.
I wasted 2 days trying to do it but WOW it was worth it..your chromi x ROM is amazing! great job! I've also learned a useful skill for the future so no complaints here