Related
First I want to apologize for the double post (post in General)
I used odin to get froyo on the Captivate. That worked fine. When I try and root 2.2, the phone froze and now it won't get out of recovery mode. I have tried every combination I can think of to reboot the phone short of throwing it down the street, but I cannot get out of recovery mode. I am also unable to use the power button (ok key?) to select anything. I can use the volume keys fine for up and down.
One of the errors says:
"(Unknown error: 0) ensure_root_path_unmounted++
ensure_root_path_unmounted (/mnt/internal_sd)
ensure_root_path_unmounted ret 0
unmount(/mnt/internal_sd) attempt 1 (unknown error: 0)
Install default apk-files. finished.
Mind you, I have already tried to put the rooted 2.2 files on the sd card, but still to no avail. Any suggestions? I am really hoping this phone isn't rooted.
So you have a european firmware? Which one is it?
Sent from my phone so excuse the spelling errors
I just fixed it. Reinstalled the firmware with Odin and it's working fine now. Thank you.
dude how did you do that.. I have the same friggin issue and I can't fix it. I'm stuck in recovery mode all the time, as soon as I plug the phone in to charge, or plug it in the computer via usb, or push the power button, the damn thing goes into recovery mode and stays there. I can use the volume buttons to navigate up and down through the options and if I hold the power botton down long enough the phone will turn off and back on again. But if I press the power button once (as in select an option) it doesn't do anything. I tried every single option out there to get into download mode with the battery out and usb in and volume buttons then put bat in....etc nothing works. I need to get into download mode
anyone?................
anyone that is messing with flashing firmwares on their phone needs to learn basic ADB skills.
use the following command in adb:
adb reboot
it will get you out of recovery mode
Pirateghost said:
anyone that is messing with flashing firmwares on their phone needs to learn basic ADB skills.
use the following command in adb:
adb reboot
it will get you out of recovery mode
Click to expand...
Click to collapse
What he said. Plus, I have had it happen sometimes that no matter what I always reboot into recovery. At that point I just adb reboot download and re-flash.
ok thanks. I know I said I have tried everything before but I wasn't completely truthful. I did try ADB though, but I don't think I was doing it right. I downloaded the SDK thing and started a command prompt from "start menue, accessories, and command prompt" but when I type the command "adb reboot download" nothing happens and the command prompt disappears. I don't have much experience with ADB, is there anyway you can give step by step instructions on how to do this? I would very much appreciate it.
Thanks
I found this thread on here "http://forum.xda-developers.com/showthread.php?t=517874" but still didn't help me much. Everytime I type cd c:\Android or any other command I get The system cannot find the path specified.
Here's what I do. After you download the sdk. There is a folder called tools. I copy that to c:
Then opencommand prompt and type,
C:
CD tools
adb reboot
Or, adb reboot download
Of course make sure your phone is connected via USB.
Sent from my SAMSUNG-SGH-I897 using XDA App
thanks I'll try that when I get home. I think this might take care of the problem, because I did keep the folder on the desktop and did not move it to C: folder. Although when I plug in the phone via USB, I still can't establish connection between phone and computer, but I will let you know how it goes after I get home tonight. and I did find some stuff about ADB through google so I might be able to do something with it tonight.
Thanks for the help though
Download odin one click, remove the battery, open odin, replace battery, hold down both volume buttons, and plug the usb cable in. That should get you to download mode unless your 3-button doesn't work.
bobbylx said:
Here's what I do. After you download the sdk. There is a folder called tools. I copy that to c:
Then opencommand prompt and type,
C:
CD tools
adb reboot
Or, adb reboot download
Of course make sure your phone is connected via USB.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Hi, so I did all that heres a copy and paste of what I did and results I got
"Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Shahed>cd c:\
c:\>cd c:\android-sdk-windows
c:\android-sdk-windows>tools
'tools' is not recognized as an internal or external command,
operable program or batch file.
c:\android-sdk-windows>cd tools
c:\android-sdk-windows\tools>adb reboot download
error: device not found
c:\android-sdk-windows\tools>"
I guess it can't be done because the device is not initiated to begin with
jatkins09 said:
Download odin one click, remove the battery, open odin, replace battery, hold down both volume buttons, and plug the usb cable in. That should get you to download mode unless your 3-button doesn't work.
Click to expand...
Click to collapse
tried that still nothing.. keeps saying waiting for device
drhusamali said:
tried that still nothing.. keeps saying waiting for device
Click to expand...
Click to collapse
Find the tools folder in the SDK you dowloaded and extracted, I found a shortcut to it scroll over the tools folder, hold the shift key and right click on the tools folder then choose open command window here.
When the command window opens type the command ADB shell then hit enter, then type adb reboot download then hit enter with your phone plugged into pc. This always works for me. You can always change the path by moving the folder directly to your c drive but this will work for you for now.
Pirateghost said:
anyone that is messing with flashing firmwares on their phone needs to learn basic ADB skills.
use the following command in adb:
adb reboot
it will get you out of recovery mode
Click to expand...
Click to collapse
This has saved my azz a few times.....Learn to use adb mode from PC inDEEED!!!!
Adb recovery adb download ....on and on.....
Hi guys, I have a problem.
I want to flash my N1 with the Cyanogenmod, but I have a problem with Bootloader unlocking. I do exactly what here is written (in the N1 guide from wiki.cyanogenmod), but when I open CMD (win XP) and write "fastboot oem unlock", it just doesn't works, but "adb devices" works and shows my phone. What can I do ? Any ideas ?
You need to boot into bootloader to work with fastboot. And if "adb devices" shows your phone - you obviously didn't boot.
adb reboot bootloader
Click to expand...
Click to collapse
Also, for a more comprehensive guide, please read the Wiki.
Code:
C:\fastboot>fastboot oem unlock
'fastboot' is not recognized as a
operable program or batch file.
This is what it shows in bootloader mode.
P.S. I have already re-installed my drivers. I have to notice that when I try to reinstall the drivers (in fastboot mode), they always auto-install themselves and when I try to update them, they say that there isn't newer version.
Fastboot executable isn't in the same directory as ADB executable, and isn't in the path you're executing it from (which is C:\fastboot).
Check, what is the actual executable you're trying to run, and if you have one. It might be called fastboot-windows.exe, if you didn't get it from downloading the Android SDK.
There is a executable file named "fastboot-windows.exe", but when I try to run it, it just open and close for 1 second. Any ideas ?
I thought the message would be clear by now... Oh well.
Open command prompt.
Run:
fastboot-windows oem unlock
Click to expand...
Click to collapse
I think It's done but my computer shows this message (see attached) 5 mins and I don't know it's ready or not ? Could I turn on the phone ? (Sry for the easy questions but I'm a real noob, because that's my 1st Android phone.)
The "too many links" message doesn't look good.
Reboot your computer.
Reboot the phone.
Use different USB port in your computer.
Ok well if you want my input try "fastboot devices" this should return your S/N (starting with "HT") if it gives you the same error then I would reinstall the SDK.
Hey all. I was reading about the stock Google edition RUU 4.4 that's posted here. However, the directions say to manually install via fastboot. I tried with TWRP instead because I am having trouble with the command prompt but when I try to install the RUU via twrp it immediately says failed. Is there a way to do it via twrp? Thank you all
Just follow the instructions. If there was an easier way it would have been posted.
Sent from my HTC O'ne-xus
Take a hint and don't do it.
I know it can be frustrated, but that's one of those things where you REALLY need fastboot setup and working before installing the Rom. If something weird happens where you're in a bootloop or something, you need access to working fastboot. If you can't get it working I'll help you get it figured out.
But tell us exactly what's not working and we can probably help.
One tip is if you're using Windows 7, open the command prompt by holding shift while right clicking in the blank white folder space where your fastboot.exe file is located on the computer.
Shift + Right Click will pop up a menu where you choose "Open Command Window Here"
That puts you right to the step of typing the command, because cd (change directory to path of fastboot file) isn't needed since you started in the correct folder.
When you run the command, like "fastboot devices" as a test, take a screenshot of the cmd window after you run it so we can see exactly what it's doing and advise from there.
If you're own Windows 8 you'll need to disable driver signing, which I find the steps for by googling "Windows 8 how to disable driver signing"
Also if there's USB 2.0 ports on your computer use them instead of 3.0. And the main USB port usually works best, such as on the back of a motherboard instead of the front case in a desktop tower.
Sent from my HTC One using Tapatalk
When I normally plug my htc one into my laptop that is running win 8.1 64 bit. It shows that my phone is connected and opens files for me to view What is on my phone. When I'm in boot loader and I plug it in (I'm trying to unlock it to root) I hear the notification sound that the phone is connected to computer but the file box doesn't open showing me what's on the phone. Is this normal? If so, how do I open cmd prompt to type in OEM command and what should the command initially say before I type my oem command? Thanks for any help you can give.
dcm1200 said:
When I normally plug my htc one into my laptop that is running win 8.1 64 bit. It shows that my phone is connected and opens files for me to view What is on my phone. When I'm in boot loader and I plug it in (I'm trying to unlock it to root) I hear the notification sound that the phone is connected to computer but the file box doesn't open showing me what's on the phone. Is this normal? If so, how do I open cmd prompt to type in OEM command and what should the command initially say before I type my oem command? Thanks for any help you can give.
Click to expand...
Click to collapse
You will not see you data in bootloader mode. What is your bootloader version? You will not be able to send fastboot commands using windows 8.1 with hboot 1.44.
open the cmd prompt from your adb/fastboot.exe folder and type
Code:
fastboot devices
and see if the device is recognized by your computer
and go see those video guide here: http://forum.xda-developers.com/htc-one#root
Be sure to use the latest htc drivers and latest android sdk (abd/fastboot)
And again, you will not be able to use fastboot with a win8.1 computer if your bootloader is 1.44
dcm1200 said:
When I normally plug my htc one into my laptop that is running win 8.1 64 bit. It shows that my phone is connected and opens files for me to view What is on my phone. When I'm in boot loader and I plug it in (I'm trying to unlock it to root) I hear the notification sound that the phone is connected to computer but the file box doesn't open showing me what's on the phone. Is this normal? If so, how do I open cmd prompt to type in OEM command and what should the command initially say before I type my oem command? Thanks for any help you can give.
Click to expand...
Click to collapse
Sorry mate but I will not troubleshoot via PM because its too much confusing and other members can't help you if you send me pm. Keep posting here it will be much easier. Hope you understand
QUOTE=alray;50379334]Sorry mate but I will not troubleshoot via PM because its too much confusing and other members can't help you if you send me pm. Keep posting here it will be much easier. Hope you understand [/QUOTE
But after flashing twrp recovery and copying supersu to internal storage I erased cache in cms before going into recovery mode then unzipped supersu and rebooted phone. I opened super su and said that there is no binary file or that it is not working. I also dl'ed a root checker and it said that I'm not rooted. Any ideas on what to do now?
dcm1200 said:
QUOTE=alray;50379334]Sorry mate but I will not troubleshoot via PM because its too much confusing and other members can't help you if you send me pm. Keep posting here it will be much easier. Hope you understand [/QUOTE
But after flashing twrp recovery and copying supersu to internal storage I erased cache in cms before going into recovery mode then unzipped supersu and rebooted phone. I opened super su and said that there is no binary file or that it is not working. I also dl'ed a root checker and it said that I'm not rooted. Any ideas on what to do now?
Click to expand...
Click to collapse
install superSU.zip the same as you install a rom in recovery
clsA said:
install superSU.zip the same as you install a rom in recovery
Click to expand...
Click to collapse
Please pardon my ignorance but I'm new to this. How? Is it the same basic way that I flashed twrp to my phone?
I've been struggling for a week with this.
Trying to unlock the bootloader but whenever I get to the stage of using command prompt I get this message;
'fastboot' is not recognized as an internal or external command,
operable program or batch file
The PC just will not recognise the phone when in fastboot mode although it does when not.
Windows 7
Android 4.3
HTC Sense Version 5.5
Software number 3.62.401.1
HTC SDK API Level 5.65
USB Debugging ticked
Fast boot deticked
HTC cable used
Latest drivers installed
Any help would be appreciated, the only previous experince I have is rooting a Galaxy note and tablet with no trouble whatsoever.
tj
tjpearson said:
I've been struggling for a week with this.
Trying to unlock the bootloader but whenever I get to the stage of using command prompt I get this message;
'fastboot' is not recognized as an internal or external command,
operable program or batch file
The PC just will not recognise the phone when in fastboot mode although it does when not.
Windows 7
Android 4.3
HTC Sense Version 5.5
Software number 3.62.401.1
HTC SDK API Level 5.65
USB Debugging ticked
Fast boot deticked
HTC cable used
Latest drivers installed
Any help would be appreciated, the only previous experince I have is rooting a Galaxy note and tablet with no trouble whatsoever.
tj
Click to expand...
Click to collapse
Do you have fastboot.exe on your computer? It looks like CMD isn't finding fastboot.exe 1-because you don't have it 2- because you have not started your cmd prompt from your fastboot.exe folder
can you post a screenshot of your cmd prompt when you get this error?
ADB Installer
Installed ADB Installer and now been able to copy and been able to submit my token.
Recieved email reply with unlock code and it came as a VLC icon, still put this onto my phone but now get message 'unable to open bin file'
Got one step further but now unable to open file.
Below is the message I get:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\tjpearson>fastboot flash unlocktoken Unlock_code.bin
error: cannot open 'Unlock_code.bin'
C:\Users\tjpearson>
Your help is very much appreciated but my wife fails to understand my pannick and she thinks out tea is more important so may not get back to you straight away.
tj
tjpearson said:
Installed ADB Installer and now been able to copy and been able to submit my token.
Recieved email reply with unlock code and it came as a VLC icon, still put this onto my phone but now get message 'unable to open bin file'
Got one step further but now unable to open file.
Below is the message I get:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\tjpearson>fastboot flash unlocktoken Unlock_code.bin
error: cannot open 'Unlock_code.bin'
C:\Users\tjpearson>
Your help is very much appreciated but my wife fails to understand my pannick and she thinks out tea is more important so may not get back to you straight away.
tj
Click to expand...
Click to collapse
Think you need to open the command prompt in the adb folder, and also have the unlock_code.bin in that same folder.
mb_guy said:
Think you need to open the command prompt in the adb folder, and also have the unlock_code.bin in that same folder.
Click to expand...
Click to collapse
OK, I'll try this tomorrow, thanks for the help.
Originally Posted by mb_guy
Think you need to open the command prompt in the adb folder, and also have the unlock_code.bin in that same folder.
Click to expand...
Click to collapse
OK, I'll try this tomorrow, thanks for the help.
Click to expand...
Click to collapse
Like mb_guy said, you MUST place the bin file in the same folder where adb and fastboot are. Every time you want to flash a file to your phone it must be in that folder, otherwise fastboot won't find it and it will output you that error (can't open file). That rule apply to recovery, unlock code, rom, kernel, ruu, firmware etc etc.
Sent from my HTC One using xda app-developers app
alray said:
Like mb_guy said, you MUST place the bin file in the same folder where adb and fastboot are. Every time you want to flash a file to your phone it must be in that folder, otherwise fastboot won't find it and it will output you that error (can't open file). That rule apply to recovery, unlock code, rom, kernel, ruu, firmware etc etc.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help because at least I've now been able to unlock bootloader.
My problem now is 'fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img' command line and yet again I'm getting error unable to open as below;
C:\Users\tjpearson>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
error: cannot open 'openrecovery-twrp-2.6.3.0-m7.img'
Even placing zip on root of phone and in adb folder still no joy.
tj
tjpearson said:
Thanks for the help because at least I've now been able to unlock bootloader.
My problem now is 'fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img' command line and yet again I'm getting error unable to open as below;
C:\Users\tjpearson>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
error: cannot open 'openrecovery-twrp-2.6.3.0-m7.img'
Even placing zip on root of phone and in adb folder still no joy.
tj
Click to expand...
Click to collapse
''error: cannot open'' is caused because fastboot don't find the file. Is the recovery file you are trying to flash is named exactly <openrecovery-twrp-2.6.3.0-m7.img> ?
Btw I'll recommend you to flash twrp 2.6.3.3 not 2.6.3.0 as you could have issur flashing newer 4.4 rom
Code:
fastboot flash recovery <name_of_file.img>
fastboot erase cache
fastboot reboot-bootloader
alray said:
''error: cannot open'' is caused because fastboot don't find the file. Is the recovery file you are trying to flash is named exactly <openrecovery-twrp-2.6.3.0-m7.img> ?
Btw I'll recommend you to flash twrp 2.6.3.3 not 2.6.3.0 as you could have issur flashing newer 4.4 rom
Code:
fastboot flash recovery <name_of_file.img>
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Yes, named exactly the same.
It's driving me mad, if the bootloader is now unlocked is there an easier way to flash twrp and then root.
Whats the best way to check adb is actually communicating with the phone
tj
tjpearson said:
Yes, named exactly the same.
It's driving me mad, if the bootloader is now unlocked is there an easier way to flash twrp and then root.
Whats the best way to check adb is actually communicating with the phone
tj
Click to expand...
Click to collapse
Do you have a Sprint phone ? and can you post a screen shot of your adb / fastboot folder containing the files or at least post your results for dir
open command prompt from your adb / fastboot folder (shift+right click - command prompt here)
type
adb devices
your device SN will be here
type
adb reboot bootloader
you should be in fastboot usb
type
fastboot devices
again your serial no should be here
type dir
you should see the contains of the folder your in
now
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
if error change the twrp name to match the one in the dir command above
clsA said:
Do you have a Sprint phone ? and can you post a screen shot of your adb / fastboot folder containing the files or at least post your results for dir
open command prompt from your adb / fastboot folder (shift+right click - command prompt here)
type
adb devices
your device SN will be here
type
adb reboot bootloader
you should be in fastboot usb
type
fastboot devices
again your serial no should be here
type dir
you should see the contains of the folder your in
now
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
if error change the twrp name to match the one in the dir command above
Click to expand...
Click to collapse
I seem to have a problem adb detecting the connected phone, I'll unistall and start again and if I can then get back to you later I'd appreciate it very much.
The phone is UK on 02 Android 4.4 HTC Sense version 5.5
tj
tjpearson said:
I seem to have a problem adb detecting the connected phone, I'll unistall and start again and if I can then get back to you later I'd appreciate it very much.
The phone is UK on 02 Android 4.4 HTC Sense version 5.5
tj
Click to expand...
Click to collapse
can you check my guide under faq #2, if that solves it
Well, think I'll give up with rooting my HTC One, I have never had so much trouble routing a divice as this. My bootloader is now unlocked and that's about as far as I get.
My phone seems to have been detected once through adb that then allowed me to run unlock token but everything else just fails.
In one last attempt I've attached image of ADB folder and below is result from command line.
It must be my age because evertybing seems so complex nowadays
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
error: cannot load 'openrecovery-twrp-2.6.3.3-m7.img': No error
C:\Android>
tjpearson said:
Well, think I'll give up with rooting my HTC One, I have never had so much trouble routing a divice as this. My bootloader is now unlocked and that's about as far as I get.
My phone seems to have been detected once through adb that then allowed me to run unlock token but everything else just fails.
In one last attempt I've attached image of ADB folder and below is result from command line.
It must be my age because evertybing seems so complex nowadays
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
error: cannot load 'openrecovery-twrp-2.6.3.3-m7.img': No error
C:\Android>
Click to expand...
Click to collapse
cannot load = MyFileNameIsWrong
and from the screenshot you posted the filename is: openrecovery-twrp-2.6.3.3-m7.img.img <- yes, double extension, next time do a "dir" in command prompt to see your filenames, not in Windows Explorer.
d -darrrrr
nkk71 said:
cannot load = MyFileNameIsWrong
and from the screenshot you posted the filename is: openrecovery-twrp-2.6.3.3-m7.img.img <- yes, double extension, next time do a "dir" in command prompt to see your filenames, not in Windows Explorer.
Click to expand...
Click to collapse
I love you nkk71, I really can't tell you how much I love you but I do !!!!! :victory:
Did what you said and fumbled through flashing twrp and then adding superuser after to the phones root, did recovery again and installed superuser via twrp and bingo, rooted and confirmed.
Been struggling 2 weeks with this and non stop all weekend, my wife wants a divorce but I don't care cos I'M ROOTED !!
Thanks so much for all the help, nice one :good:
tj
tjpearson said:
I love you nkk71, I really can't tell you how much I love you but I do !!!!! :victory:
Did what you said and fumbled through flashing twrp and then adding superuser after to the phones root, did recovery again and installed superuser via twrp and bingo, rooted and confirmed.
Been struggling 2 weeks with this and non stop all weekend, my wife wants a divorce but I don't care cos I'M ROOTED !!
Thanks so much for all the help, nice one :good:
tj
Click to expand...
Click to collapse
Lol
Now that the phone is good, go spend some time with your better half!!!
No guides on xda, on "how to return my marriage to stock"
Put the phone on the charger or something, and spend time with your significant other.
Sent from my HTC One using Tapatalk
One last question
nkk71,
Can I uninstall Superuser now and install SuperSU instead cos I've already purchased that when had the Note rooted or will it cause me more time away from the mrs with issues.
tj
tjpearson said:
nkk71,
Can I uninstall Superuser now and install SuperSU instead cos I've already purchased that when had the Note rooted or will it cause me more time away from the mrs with issues.
tj
Click to expand...
Click to collapse
Shouldn't be a problem, use the flashable zip from the thread: http://forum.xda-developers.com/showthread.php?t=1538053
Yeah , sorted.
Thanks again for all your help.
tj