Hi - I know this problem has probably been covered many times, so forgive me :angel: if I'm "boiling my cabbages twice", as my mum always says.
About a year or so ago I installed Android Revolution on my HTC One X - it took me a while to figure out what to do, and how to do it, but I eventually got there and it worked fine Anyway, i was reading an article the other day about how good the Cyanogen ROM was so decided to give it ago. Silly me
After many hours of hair pulling and cursing I've hit a brick wall, and could really do with some simple advice in plain English. I think I may have well and truly screwed up. I downloaded the Cyanogen ROM and flashed it, but kept getting the 'boot loop' logo. I still had a recovery file on my phone from when I installed Android Revolution, and this allowed me to reboot into Jelly Bean 4.1.1 (I think). Now, somehow, that file has gone and all I can do now is get the Cyanogen boot loop, or the Team Win Recovery Project menu. I can boot into the HTC menu (whatever it's called) by pressing the power and volume down button, but that's about it. My partner tells me "that'll teach you for messing"
Please, is there somebody out there that could possibly talk me through a simple, idiots guide for idiots method of getting my phone working again? :fingers-crossed:
Many, many thanks in advance
:crying:
Tichier said:
Hi - I know this problem has probably been covered many times, so forgive me :angel: if I'm "boiling my cabbages twice", as my mum always says.
About a year or so ago I installed Android Revolution on my HTC One X - it took me a while to figure out what to do, and how to do it, but I eventually got there and it worked fine Anyway, i was reading an article the other day about how good the Cyanogen ROM was so decided to give it ago. Silly me
After many hours of hair pulling and cursing I've hit a brick wall, and could really do with some simple advice in plain English. I think I may have well and truly screwed up. I downloaded the Cyanogen ROM and flashed it, but kept getting the 'boot loop' logo. I still had a recovery file on my phone from when I installed Android Revolution, and this allowed me to reboot into Jelly Bean 4.1.1 (I think). Now, somehow, that file has gone and all I can do now is get the Cyanogen boot loop, or the Team Win Recovery Project menu. I can boot into the HTC menu (whatever it's called) by pressing the power and volume down button, but that's about it. My partner tells me "that'll teach you for messing"
Please, is there somebody out there that could possibly talk me through a simple, idiots guide for idiots method of getting my phone working again? :fingers-crossed:
Many, many thanks in advance
:crying:
Click to expand...
Click to collapse
Post the result from command fastboot getvar all and delete your S/N and IMEI from the info.
Thant said:
Post the result from command fastboot getvar all and delete your S/N and IMEI from the info.
Click to expand...
Click to collapse
Thanks for replying - that's one of my problems: my PC won't recognise the phone when it's connected. If I boot into the Team Win Recovery Project I can mount the USB storage and view files and transfer them from PC to phone and vice-versa, but I can't start the command prompt. It seems the boot menu on the HTC doesn't recognise the internal storage/USB
Tichier said:
Thanks for replying - that's one of my problems: my PC won't recognise the phone when it's connected. If I boot into the Team Win Recovery Project I can mount the USB storage and view files and transfer them from PC to phone and vice-versa, but I can't start the command prompt. It seems the boot menu on the HTC doesn't recognise the internal storage/USB
Click to expand...
Click to collapse
Just go in bootloader choice FASTBOOTand connect the phone to computer and you will see FASTBOOT USB and then start CMD and run the command
Thant said:
Just go in bootloader choice FASTBOOTand connect the phone to computer and you will see FASTBOOT USB and then start CMD and run the command
Click to expand...
Click to collapse
But I've tried that - I can see FASTBOOT USB - but it's not picked up on the laptop. I've tried different cables and USB ports. Shouldn't I be able to see the phone listed under My Computer? How do I start the command prompt (I've entered 'cmd' under the start menu on the PC)
Thanks again
Tichier said:
But I've tried that - I can see FASTBOOT USB - but it's not picked up on the laptop. I've tried different cables and USB ports. Shouldn't I be able to see the phone listed under My Computer? How do I start the command prompt (I've entered 'cmd' under the start menu on the PC)
Thanks again
Click to expand...
Click to collapse
are you have fastboot files and adb. If yes go to this folder where is the files and press shift + right button on the mouse on emty space in the folder and choice open comand window here after this run the command
Thant said:
are you have fastboot files and adb. If yes go to this folder where is the files and press shift + right button on the mouse on emty space in the folder and choice open comand window here after this run the command
Click to expand...
Click to collapse
When I boot my phone into the 'Fastboot' menu and select Hboot it comes up with 'Failed to open master USB mode' and then goes back to the previous screen. Doing this it does not show up on 'My Computer' on my Laptop.
By rebooting into TWRP I can see the phone as a 'Removable disk' on my laptop, and when I right click on the drive I can see the folders .android_secure, data, showme, nero_sync, Albums, Android, dcim, Download, LOST.DIR, mobile, My Documents, Notifications, Pictures, ROM's (which I created), TWRP and a file called 'nmdsdcid.
If I shift+right click here for the CMD prompt, E:\>fastboot getvar all it returns with "'fastboot' is not recognised as an internal or external command, operable program or batch file"
Once again, many thanks for your time
Tichier said:
When I boot my phone into the 'Fastboot' menu and select Hboot it comes up with 'Failed to open master USB mode' and then goes back to the previous screen. Doing this it does not show up on 'My Computer' on my Laptop.
By rebooting into TWRP I can see the phone as a 'Removable disk' on my laptop, and when I right click on the drive I can see the folders .android_secure, data, showme, nero_sync, Albums, Android, dcim, Download, LOST.DIR, mobile, My Documents, Notifications, Pictures, ROM's (which I created), TWRP and a file called 'nmdsdcid.
If I shift+right click here for the CMD prompt, E:\>fastboot getvar all it returns with "'fastboot' is not recognised as an internal or external command, operable program or batch file"
Once again, many thanks for your time
Click to expand...
Click to collapse
Now do exactly what I write you. Disconect the phone from USB. Start the phone in bootloader and with the buttons volume up and down navigate to fastboot and press POWER button onse. you will see your phon will change HBOOT with FASTBOOT after this connect the phone to the computer with USB cable and you will see FASTBOOT USB after this run the command. When you go in bootloader your phone must NOT TO BE CONNECTED to the computer
Thant said:
Now do exactly what I write you. Disconect the phone from USB. Start the phone in bootloader and with the buttons volume up and down navigate to fastboot and press POWER button onse. you will see your phon will change HBOOT with FASTBOOT after this connect the phone to the computer with USB cable and you will see FASTBOOT USB after this run the command. When you go in bootloader your phone must NOT TO BE CONNECTED to the computer
Click to expand...
Click to collapse
Thanks for your reply - I have done exactly what you said, but the phone isn't recognised in 'My Computer' but I can see it under device manager. When I connect it with the USB cables the laptop makes a noise as if it is identifying it. On the phone it says what I said earlier about failing to open master USB, and then goes back to the Hboot menu and the laptop beeps to say the phone has been disconnected
Once again, thank you very much for your time and advice
Tichier said:
Thanks for your reply - I have done exactly what you said, but the phone isn't recognised in 'My Computer' but I can see it under device manager. When I connect it with the USB cables the laptop makes a noise as if it is identifying it. On the phone it says what I said earlier about failing to open master USB, and then goes back to the Hboot menu and the laptop beeps to say the phone has been disconnected
Once again, thank you very much for your time and advice
Click to expand...
Click to collapse
Have you installed HTC drivers (HTC Sync Manager) ?
65455355 2
androidDany said:
Have you installed HTC drivers (HTC Sync Manager) ?
Click to expand...
Click to collapse
Yes, I have. To me it seems like something is either missing or corrupt
Tichier said:
Yes, I have. To me it seems like something is either missing or corrupt
Click to expand...
Click to collapse
When you choice Fastboot in bootloader and you connect the phone to the computer and hi beep are you see FASTBOOT USB on the phone? You must to navigate to fastboot option on your phone and press the power button.
Thant said:
When you choice Fastboot in bootloader and you connect the phone to the computer and hi beep are you see FASTBOOT USB on the phone? You must to navigate to fastboot option on your phone and press the power button.
Click to expand...
Click to collapse
Yes - I've posted a video of what happens here (I hope the link works)....
https://drive.google.com/file/d/0B5SD3cvIx7ZTcDNFVDZvNmpIcjdtYnk2VUpjd084NGg1aWJB/edit?usp=sharing
Thank you
Tichier said:
Yes - I've posted a video of what happens here (I hope the link works)....
https://drive.google.com/file/d/0B5SD3cvIx7ZTcDNFVDZvNmpIcjdtYnk2VUpjd084NGg1aWJB/edit?usp=sharing
Thank you
Click to expand...
Click to collapse
Now you hear sound on the computer the pc recognise the phone nou when you see fastboot USB navigate to folder where is your fastboot.exe and adb.exe and open CMD there let say C:\fastboot\ you will see this in CMD after this must to write the command fastboot getvar all must look like this C:\fastboot\fastboot getvar all and you will see the information on the display copy and paste here
Same Problem
I have the same problem after updating from CM 10.1 to 10.2 from settings. I had this problem earlier and fastboot solved it, but this time around I can't boot into recovery by pressing the power and volume down button, it just keeps on restarting. I think there's a chance there's something wrong with the volume down button. Help please. :'(
Edit: So I pressed REALLY hard on the key and it worked. Flashed the boot.img by putting it into the zip folder BootUpdate_by_hestheone64. Still stuck in the loop. :/
Thant said:
Now you hear sound on the computer the pc recognise the phone nou when you see fastboot USB navigate to folder where is your fastboot.exe and adb.exe and open CMD there let say C:\fastboot\ you will see this in CMD after this must to write the command fastboot getvar all must look like this C:\fastboot\fastboot getvar all and you will see the information on the display copy and paste here
Click to expand...
Click to collapse
The fastboot file I have located, but I can't run it - I can't find the adb.exe - This is where I believe the problem is as I mentioned earlier (about something being missing or corrupt)
Many thanks again
Tichier said:
The fastboot file I have located, but I can't run it - I can't find the adb.exe - This is where I believe the problem is as I mentioned earlier (about something being missing or corrupt)
Many thanks again
Click to expand...
Click to collapse
download this ZIP and extract in C:\fastboot\
androidDany said:
Have you installed HTC drivers (HTC Sync Manager) ?
Click to expand...
Click to collapse
Yes, I have - and that doesn't identify my phone either. I'm pulling my hair out! The only way my laptop identifies my phone is when I boot into the Team Win Recovery Project, but then it's listed in My Computer as a drive
Tichier said:
Yes, I have - and that doesn't identify my phone either. I'm pulling my hair out! The only way my laptop identifies my phone is when I boot into the Team Win Recovery Project, but then it's listed in My Computer as a drive
Click to expand...
Click to collapse
are you try with my zip and fastboot?
Thant said:
download this ZIP and extract in C:\fastboot\
Click to expand...
Click to collapse
I've done that, and it works. I can go into that folder and right click+shift to start the cmd file and it runs. But I still can't get the laptop to identify the phone when it's connected. Except when it's connected by the Team Win Recovery Project
Many thanks again
Related
okay ... a new question and also soo weird....
I want that my 2 PC´s recognize my device when its in bootloader mode
1º pc recognizes it well and its running UBUNTU.
2ºmy sister´s PC RUNNING WIN7 doesn´t recognize my DHD into bootloader mode.. but if i look the screen of the device the device automatically was changed his status to "HBOOT USB PLUG" but here is the problem:
When windoze7 detects and recognizes my device It issues a sound, but when I connect my DHD it issues different other one, that is to say detects it but it does not recognize her, then the usb mode I cannot use it
but if i boot my dhd and put her in debugging mode and run adb parameters windoze recognizes the device perfectly...
i am not an experienced user in windows
and i don´t know whats the problem. its strange..
any advise?thx in advance
Between you and the stickman you've had every problem going!!
Have you installed HTC Sync onto your sister's PC?
Why haven't you converted her to Ubuntu?
Mr_JMM said:
Between you and the stickman you've had every problem going!!
Have you installed HTC Sync onto your sister's PC?
Why haven't you converted her to Ubuntu?
Click to expand...
Click to collapse
lololol we have a lot of problems Especially with windows i hate it
but she is afraid of not being able to handle it if I am not in house (SHE HAS ANOTHER DHD) in addition she likes the Microsoft OFFICE. LOL (and not open office)
Yes i had installed htc sync drivers, and sdk working well in usb debugging mode with the DHD turned on
Get to the stage you were at before:
fastboot
connect phone to PC
Phone says HBOOT USB PLUG
Using the Android-sdk shell
type
Code:
fastboot devices
Do you get a response?
Mr_JMM said:
Get to the stage you were at before:
fastboot
connect phone to PC
Phone says HBOOT USB PLUG
Using the Android-sdk shell
type
Code:
fastboot devices
Do you get a response?
Click to expand...
Click to collapse
yes i tried in fastboot mode but only says "list of attached devices" and nothing more... there aren´t devices in the list..
and if i write adb shell""" says ""not devices found"" logically
SERGI.3210 said:
yes i tried in fastboot mode but only says "list of attached devices" and nothing more... there aren´t devices in the list..
and if i write adb shell""" says ""not devices found"" logically
Click to expand...
Click to collapse
the problem appears into fastboot and into bootloader
ok in fastboot mode into sdk shell write fastboot devices and shows me a message:
"unable to initialize the aplication because ADBWINAPI.DLL not found
Ok, try this:
Create an Ubuntu live CD.... you can see where I'm going with that one.
Sorry buddy, will need to wait for some other poor sap that uses Windoze to pop along.
There was an old thread I read once and someone solved it by going to device manager and updating drivers or something for the "android device". <<-- Re your new post
Other than that, usual suggestion is try a different USB socket (different side of PC).
Mr_JMM said:
Ok, try this:
Create an Ubuntu live CD.... you can see where I'm going with that one.
Sorry buddy, will need to wait for some other poor sap that uses Windoze to pop along.
There was an old thread I read once and someone solved it by going to device manager and updating drivers or something for the "android device". <<-- Re your new post
Other than that, usual suggestion is try a different USB socket (different side of PC).
Click to expand...
Click to collapse
ok tried another socket but the PC says to me :LOL
good idea mate... if i create aN ubuntu root/live cd i can try with the konsole
windoze please... burn in the ****ing hell
edit:with ubuntu works well again
.........................................................................................
spike_14 said:
.........................................................................................
Click to expand...
Click to collapse
good apreciation to the forum mate... LOL
okay... in advance thank´s again to my friend Mr_JMM for help me again (pressing your thank´s button AGAIN lol)
i solved my problem with "winfuck"7 (windows for microsoft´s friends)
ok when i was tried to input a fastboot code the CMD (shell) of windows returned me:
"unable to initialize the program because ADBWINAPI.DLL does not exist...
well i browsed for this file and its a library file for adb.exe commands.
under my experience fastboot parameters shouldn´t be afeccted by the ausence of this file but when i was downloaded it (a zip file with adbwinapi.exe, adbwinusbapi.dll and adb.exe) and i have put it in the folder "tools" of the sdk (Rightly where it shelters fastboot.exe) VOILÀ!!!!
i tried to enter:
"fastboot devices"
and returned to my
"HT.........."
also i tried to rebbot the device from fastboot with
"fastboot reboot" and WORKS WELL!!!!
END OF THIS THREAD.... SOLVED!!!!!!!!!!
Hello friends,
How to get into fastboot to relock the bootloader, if my volume button is dead? By dead, I mean the ribbon has been ripped off of the mobo (it was soldered onto mobo).
Since I'm a brand-new noob, the only way I know of and have done is to get into fastboot mode and lock it back up like what I did when I unlocked it. Any other way to lock it, ideally within the Android OS? Since my volume buttons are completely dead, I doubt that I can get into any "mode" other than OS right now..
TIA!
adb reboot bootloader.
I've seen that command in a post from search earlier, but there was no response after that post.
Would you explain the procedure? I am afraid that I might do anything wrong on top of these disasters i've gone thru with this phone
I also saw another line during earlier search: "if they don't know how to setup an adb command, they probably shouldn't unlock their phones"... Looks like I've done what I shouldn't..?
I would say doing whatever ripped the volume button cable out was what you shouldn't have been doing If you unlocked the phone you have the software you used to unlock, right? What software/guide did you use/follow? Are you using Windows/Linux/Mac? The only way to get to the bootloader w/o the volume buttons (afaik) is to use adb via usb. If you provide more details I can try to help you.
cswithxda said:
I've seen that command in a post from search earlier, but there was no response after that post.
Would you explain the procedure?
Click to expand...
Click to collapse
Once you're in adb reboot bootloader, do fastboot oem lock. Opposite of how you unlocked it in the first place
cswithxda said:
I've seen that command in a post from search earlier, but there was no response after that post.
Would you explain the procedure? I am afraid that I might do anything wrong on top of these disasters i've gone thru with this phone
Click to expand...
Click to collapse
navigate your cmd line to the folder with adb and fastboot in it. Hook the phone up to the computer and type:
Code:
adb reboot bootloader
which will make your phone reboot into the bootloader mode. You can then proceed with what you need to do.
I also saw another line during earlier search: "if they don't know how to setup an adb command, they probably shouldn't unlock their phones"... Looks like I've done what I shouldn't..?
Click to expand...
Click to collapse
I agree with whoever said that. This is another example of people messing with things before reading and learning how they work.
Thanks for your help guys!
btw, anyone found xdadevelopers to load extremely slower in Firefox when compared to Chrome? (just offtopic)
Anyway, I unlocked the bootloader when I was switching to yakju cmd and this folder called "fastboot-and-adb" in which there is both adb.exe and fastboot.exe. I used command "fastboot unlock bootloader" or something alike.
I'll do some more search and learn. Don't want you guys to think of me as a lazy bone who unlocked their bootloader using 1-click toolkit
p.s. edit: in my other thread, someone suggested using quickboot app.
Thanks for your replies guys!
martonikaj said:
navigate your cmd line to the folder with adb and fastboot in it. Hook the phone up to the computer and type:
Code:
adb reboot bootloader
which will make your phone reboot into the bootloader mode. You can then proceed with what you need to do.
I agree with whoever said that. This is another example of people messing with things before reading and learning how they work.
Click to expand...
Click to collapse
Somehow it says device not found
I do have proper driver (Naked Driver Beta 0.5 by 1wayjonny) that my phone was able to be recognized under bootloader at the time when I could actually get into bootloader. My phone is also being recognized as media device now... I have also turning usb debug on...
Try adb remount
The ad devices
This should list the serial number
Then all commands should work
Sent from my Galaxy Nexus using xda premium
cswithxda said:
Somehow it says device not found
I do have proper driver (Naked Driver Beta 0.5 by 1wayjonny) that my phone was able to be recognized under bootloader at the time when I could actually get into bootloader. My phone is also being recognized as media device now... I have also turning usb debug on...
Click to expand...
Click to collapse
You need to turn USB debugging on, and then type "adb devices" and see if it shows up. It may not using the Naked Driver; I had to install the full Samsung USB driver package before ADB would see my Galaxy Nexus.
If it does show up, then you type "adb reboot-bootloader" and it should boot into fastboot. Then just type "fastboot oem lock" and it will wipe the storage partitions and restore the bootloader lock.
Thanks for the help at late night guys. I finally got into the bootloader, thru a mac tho Kinda ironic that I am a supporter of Windows, well, at least a firm user of Windows.
Tried adb remount, it still says device not found
synaesthetic said:
You need to turn USB debugging on, and then type "adb devices" and see if it shows up. It may not using the Naked Driver; I had to install the full Samsung USB driver package before ADB would see my Galaxy Nexus.
If it does show up, then you type "adb reboot-bootloader" and it should boot into fastboot. Then just type "fastboot oem lock" and it will wipe the storage partitions and restore the bootloader lock.
Click to expand...
Click to collapse
I believe that you quoted my "I have turned USB debug on" ;p
Gave up on trying Windows drivers. When I was flashing the Yakju, I tried Samsung full driver, and it didn't work on my machine, i.e., the phone can't be detected in bootloader mode, while the beta 0.5 driver worked. So I decided not to mess with it anymore.
It looks like when the phone is not under bootloader, windows recognize it fine as MTP devices and install proper samsung driver from the internet directly. This allows me to open it up in explorer to browse files and such, but the phone won't show up under adb devices somehow.
Looks like MTP device (when the phone is in Android OS) and the fastboot mode use two kinds of drivers. This is just my assumption, though.
Anyway, finally got into bootloader now with Mac, and it's pretty funny I have to do everything thru command as the volume rockers are dead
And most importantly, thank you guys for your help!
Just another update
It's real funny now that the bootloader is locked, I can't unlock it again cuz I don't have the volume button working, so I couldn't choose YES on the phone.
I'm not trying to unlock it again, but just to confirm if there's really no work around, in case I encounter this situation again in the future
Lucky that locking the bootloader won't erase everything, or I won't be able to flash a ROM with it locked... :cold sweating:
hi everyone, i'm trying to install CM9 on my LT15i, i've tried using the CM wiki instructions and both the following guides...
androidauthority.com/xperia-arc-lt15i-root-android-4-0-ics-80265/
and
androidforums.com/rezound-all-things-root/506466-scottys-noob-friendly-root-guide-start-finish.html
the phone is already fully unlocked and has CM 7.2.0 anzu installed. i've tried simply using the clockwork recovery mod bootloader to wipe the phone and install CM 9.0.0, but on reboot the phone gets past the boot logo then just shows a black screen, so i assumed i needed to flash an appropriate ROM for CM9; this is where my problem begins.
every forum i've read about this process says i must enable usb debugging (done) and "disable fastboot" under settings>power, i do not have a "power" option in my settings and cannot find anything related to fastboot on the phone; although i'm not sure this is the problem. when android is running normally and i attempt to list devices with adb.exe on windows, it successfully returns the phone's serial number. when i shut the phone down, hold the menu button and plug in the usb cable, fastboot mode appears to work correctly as the LED comes on blue and "android adb device" appears in the windows device manager (i've tried installing the arc usb/adb drivers from various sources, they all seem to work correctly). but when i attempt to list devices after restarting in fastboot mode, adb.exe says it cannot find any device. fastboot.exe has not communicated with the device whatsoever, but i assumed i might need to get the adb.exe usb daemon/server running correctly first for this to work.
i did this process once already when i installed CM7, it was successful the first time and everything went smoothly. from what i recall i just did exactly as described above and fastboot.exe was able to find the device no problem. but that was a number of months ago, hopefully i'm just missing some obvious step.
cheers
WookieInHeat said:
every forum i've read about this process says i must enable usb debugging (done) and "disable fastboot" under settings>power, i do not have a "power" option in my settings and cannot find anything related to fastboot on the phone;
Click to expand...
Click to collapse
There is no such thing. And USB debugging is only required if you want to root stock ROM, every other action can be done without it.
WookieInHeat said:
although i'm not sure this is the problem. when android is running normally and i attempt to list devices with adb.exe on windows, it successfully returns the phone's serial number. when i shut the phone down, hold the menu button and plug in the usb cable, fastboot mode appears to work correctly as the LED comes on blue and "android adb device" appears in the windows device manager (i've tried installing the arc usb/adb drivers from various sources, they all seem to work correctly). but when i attempt to list devices after restarting in fastboot mode, adb.exe says it cannot find any device. fastboot.exe has not communicated with the device whatsoever, but i assumed i might need to get the adb.exe usb daemon/server running correctly first for this to work.
i did this process once already when i installed CM7, it was successful the first time and everything went smoothly. from what i recall i just did exactly as described above and fastboot.exe was able to find the device no problem. but that was a number of months ago, hopefully i'm just missing some obvious step.
cheers
Click to expand...
Click to collapse
Drivers, drivers, drivers.
If your phone is in fastboot mode, make sure drivers are installed. Proper drivers.
You do not need ADB server for installing a kernel.
Just open up Command Prompt and install the kernel with command
Code:
fastboot flash boot boot.img
.
Assuming boot.img is in the same folder as fastboot.exe.
Someguyfromhell said:
Drivers, drivers, drivers.
If your phone is in fastboot mode, make sure drivers are installed. Proper drivers.
Click to expand...
Click to collapse
thanks for the reply someguyfromhell. i've tried every "android adb interface" driver under the sun for the S1 fast boot device that appears in the windows device manager when i put the phone in fastboot. when i try to send any command with fastboot.exe it just hangs at "waiting for device", i've fiddled with this stuff every which way and just cannot get fastboot.exe to see the phone. i've tried switching up the usb ports on this computer, but haven't had the opportunity to try a second computer. you've let me know i'm going in the right direction at least, if i have the same results on a second machine i'll pursue the issue further.
thanks again
wookie
WookieInHeat said:
thanks for the reply someguyfromhell. i've tried every "android adb interface" driver under the sun for the S1 fast boot device that appears in the windows device manager when i put the phone in fastboot. when i try to send any command with fastboot.exe it just hangs at "waiting for device", i've fiddled with this stuff every which way and just cannot get fastboot.exe to see the phone. i've tried switching up the usb ports on this computer, but haven't had the opportunity to try a second computer. you've let me know i'm going in the right direction at least, if i have the same results on a second machine i'll pursue the issue further.
thanks again
wookie
Click to expand...
Click to collapse
You need to unlock bootloader, if you want to install CM ROM. Arc S can only have bootloader unlocked via official method, there you can also download the correct driver which you need.
http://unlockbootloader.sonymobile.com/
Someguyfromhell said:
You need to unlock bootloader, if you want to install CM ROM. Arc S can only have bootloader unlocked via official method, there you can also download the correct driver which you need.
the bootloader is already unlocked, as i said, the phone has CM7 on it currently.
Click to expand...
Click to collapse
As stated, I cant acess usb debugging.. I've already connect my phone to pc but it just only show charging.. I also cant copy file to my pc.. what is the problem here? :crying::crying::crying:
panha510 said:
As stated, I cant acess usb debugging.. I've already connect my phone to pc but it just only show charging.. I also cant copy file to my pc.. what is the problem here? :crying::crying::crying:
Click to expand...
Click to collapse
HTC manager also wont recognize my phone..
panha510 said:
HTC manager also wont recognize my phone..
Click to expand...
Click to collapse
It was written so many times on XDA Forums, that your question is quite a surprise:
Open Settings, then go to phone details (where u can see kernel, Android-version etc) then just tap your Build number enough times until you're developer! Then enable USB Debugging...
bratusm said:
It was written so many times on XDA Forums, that your question is quite a surprise:
Open Settings, then go to phone details (where u can see kernel, Android-version etc) then just tap your Build number enough times until you're developer! Then enable USB Debugging...
Click to expand...
Click to collapse
I've already know that, it is when I plugged my phone into the computer, the battery indicator is charging, but the USB connection never happens.
panha510 said:
I've already know that, it is when I plugged my phone into the computer, the battery indicator is charging, but the USB connection never happens.
Click to expand...
Click to collapse
System? Win XXX, Linux...
HTC Drivers?
bratusm said:
System? Win XXX, Linux...
HTC Drivers?
Click to expand...
Click to collapse
windows 7, i already installed the htc driver..
If you can't access it, go into your settings app on your phone
Open Developer Options and click the checkbox that says
Code:
USB Debugging
If it still doesn't work, install HTC Sync Manager (if not installed already)
Restart your phone into the bootloader (by holding [Vol Down] + pressing [Power] for a second, still holding [Vol Down]
Select 'Fastboot' at the menu that shows up
Plug in your phone, ignore HTC Sync Manager, open a command prompt (admin) by hitting [WIN] + [X], then select
Code:
Command Prompt (Admin)
Once you have done that, cd to your directory of the adb and fastboot executables, like this:
Code:
cd "C:/[your directory]/"
Then
Code:
adb devices
If adb detects that the service isn't running, it'll start it then search for your device. If it finds it, you're set to use the fastboot commands for whatever you want
Good luck guys!
Wondering if any of you guys can advise me - having strange problems with fastboot (windows 8.1 and Zenfone 2 ze550ml). Wanted to flash the pre-rooted image to my device so downloaded it and extracted to the flashtools folder and renamed system.img then hooked up my phone. Checked adb drivers were installed and adb devices command returns a code string, so assumed all was good to go with flashing. However, on entering any fastboot command it just sits at "waiting for device". Tried manually starting the phone in fastboot and then connecting it, and this did enable me to execute fastboot commands (reboot or reboot-bootloader work). However, fastboot flash system system.img just results in a message about file size and then "failed to load system.img"
kanagawaben said:
Wondering if any of you guys can advise me - having strange problems with fastboot (windows 8.1 and Zenfone 2 ze550ml). Wanted to flash the pre-rooted image to my device so downloaded it and extracted to the flashtools folder and renamed system.img then hooked up my phone. Checked adb drivers were installed and adb devices command returns a code string, so assumed all was good to go with flashing. However, on entering any fastboot command it just sits at "waiting for device". Tried manually starting the phone in fastboot and then connecting it, and this did enable me to execute fastboot commands (reboot or reboot-bootloader work). However, fastboot flash system system.img just results in a message about file size and then "failed to load system.img"
Click to expand...
Click to collapse
You need to rename the system image to system.img and put it where the fastboot file is. It's looking for it but can't find it.
No, don't think that is my problem - as I said I extracted it to the flashtools folder, so it is already where the fastboot file is. And anyway, though I'd like to solve the problem of flashing the system.img, I am kind of more interested in why I can't get past "waiting for device" without first manually entering the fastboot mode.
Cause Windows sucks. I'm on Linux and no issues. Maybe someone on Windows can chip in?
I can easily do a quick ubuntu install and try it that way if you think it might work better. At the weekend maybe. Could you give me some pointers on how to do it in linux if I do? Would be much appreciated!
kanagawaben said:
No, don't think that is my problem - as I said I extracted it to the flashtools folder, so it is already where the fastboot file is. And anyway, though I'd like to solve the problem of flashing the system.img, I am kind of more interested in why I can't get past "waiting for device" without first manually entering the fastboot mode.
Click to expand...
Click to collapse
I have encountered that problem with the "waiting for device" while I was flashing pre root rom.
Try the cmd adb devices
Then it will list the device connected to the computer...if it says not authorized, then you need to check the phone which is turned on and a pop up window with the RSA key and tap on trust this computer or something..
Then repeat adb devices and it should say allow or something..then it will allow you to flash.
(double check the commands online, I might missed something)
Nah, don't blame Windows... I flashed mine with Windows 10 and worked wonders.
Also... could it be that PC isn't USB 3.0? Perhaps system.img transfer is stopped somewhere during the copying phase?
Thanks, but actually the first time I tried it I did the adb devices command and authorised my pc on the phone. When I connect and do adb devices now it shows the string of numbers code for the device. However, still can't get past "waiting for device"
My pc has both usb 3 and usb 2 ports. Tried on all of them and with various different cables including the asus issued ones, all to no avail.
Can u post a pic of your flashtool folder?
Sent from my Nexus 7
Here is a snap of my platform-tools folder and cmd window
Did you manage to find a solution to this?
I updated the zenfone 2 via OTA to the latest system update.
Ive read and downloaded all relevant files to install the pre root img from the correct sources.
Now when I hold power + vol up. I can see the droid on its back. I choose the RECOVERY option and press power button to select.
When phone reboots it goes to droid icon and says installing system upgrade.................then error appears! No recovery mode!
All the correct drivers are installed into Windows 7, the phone asks me to allow RSA key connection to laptop.
Ive tried the flash tool installer 1.0.7 with phone connected and system img (renamed) and still nothing.
Anyone got any ideas?
Ive factory reset twice in a row and allowed debugging.
Ive placed the (renamed) system.img into the fastboot folder and tried the open command with line ' fastboot flash system system.img' and the reply is usually unable to read system.img or device waiting.
Ive installed the latest android sdk develppment kit and still unable to root using this pre root image.
Im familiar with android and how to follow instructions on rooting, but this zenfone 2 is mind boggling.
Thanks for reading. I know its someone else post. I didnt want to start a fresh post with the same dilemma.
Any advice on whats going wrong would be appreciated.
tsam19 said:
When phone reboots it goes to droid icon and says installing system upgrade.................then error appears! No recovery mode!
Click to expand...
Click to collapse
Hit power and vol up again, just really quickly. Don't hold it, just press and let go. Sometimes it takes several attempts.
hkdmjack, yes your right managed to do it at last.
Cheers
Hi guys, I am facing quite a difficult problem at the moment.
My friend has "accidentally" attempted to use an Asus Zenfone 5 rooting method to root his zenfone 2 550ML.
When I received it to take a look at it, I instantly noticed that I could not get into fast boot (or droidboot). I expected to see usual droid with text on the left side and also expected to be able to select from a number of options using the volume keys (i have some past experience), but instead am met with this solid usb logo. One like this: h ttp://zenfo ne-blog-forum.2 8820.n7.nabble.c om/file/n4 5/P_20140728_051139 .jpg (remove spaces)
I did some research, and found that there were many "bricked" zenfone 5's which were stuck on this usb logo, however this zenfone 2 can start up normally and be used throughout the day normally. Only when I try to enter fast boot, by either ADB commands or by power + volume up, I cannot get past the usb logo.
I have linked up the ZenFone to my computer, and confirmed that ADB devices correctly lists the device (I have usb debugging enabled), however, when I try to go to fast boot and am met with the usb logo, my computer does register and detect the phone, however, under device manager it has a yellow triangle with the device named "" MOOREFIELD". When the ZenFone 2 is in this usb logo state, I cannot access any fast boot commands. I am quite stumped at the moment.
Any help please? By the way, I use a windows 8.1 computer with usb 3 ports. However, I have tested using different cables, and on a windows 7 laptop with usb 2 ports, still to no avail. Should I try and update the firmware using Asus' software? Or is there a better solution?
Thanks
Edit: My friend claims that he did not see at any point in time, the flashing on the zenfone 2 start. He was faced with a "<waiting for devices>" or something similar message, telling me that the phone was not fully in fast boot yet. If I can get it into fast boot, I am sure I can reflash the custom stock onto the phone, and most issues will be resolved.
same error
i have the same error by my zenfone2 after update
please help
amohammadiazar said:
i have the same error by my zenfone2 after update
please help
Click to expand...
Click to collapse
Could you specify which update you did? From your computer? Or via Asus update on ur phone?
pkvk9122 said:
Could you specify which update you did? From your computer? Or via Asus update on ur phone?
Click to expand...
Click to collapse
my orginal firmware is CN and i wanted to change to WW mode i tried by pc .... now when i conect phone t pc it want moorefeild driver for conection and i dont have those ,,
Whenever I try to flash system.img it gets stuck on "writing 'system'..." and just hangs there. I have left it for over half an hour and it still didn't work. Does anyone know a solution to this problem?
Hey guys,
So after a while without any responses, I headed over to Asus customer service to receive a very unhelpful reply.
I gave up hope of finding an answer online and so I decided to take a leap of faith by updating the firmware via the Asus Update app on the phone.
I upgraded from 2.14 to 2.15 and miraculously fastboot seemed to have restored itself. I am not sure whether or not every single update restores fastboot, or whether the update to 2.15 does, but I'm glad that it has been fixed.
My previous problems of being unable to detect fast boot devices has been resolved. Hopefully others who have experienced the same issue can find this post helpful.