I have an HTC One XL(Evita, At&t)? I purchased it from a third party. The device is rooted and unlocked.
My phone's battery died. Once I went home to recharge it, the device was unable to get past the white HTC quietly brilliant screen. I would reboot it by pressing the volume down button + power button to reboot it and factory reset it. However, it continued to do this action. Then, I chose to reboot it under some setting. After I rebooted it, the device went to a "teamwins" screen. I erased everything, including the rom. Once I did this, it re-booted the device and continued to be on the same screen. Since this action happened, I connected it to my Windows 7 PC. I noticed that my HTC could not be identified as an external hard drive, it was identified as a CD rom drive.
I tried to fix this problem by looking at other forums containing this topic. Here is what I tried:
- I tried to go to HTC support. I downloaded the current system, and tried to use it. When I tried to use it, it kept saying error.
- I uninstalled the driver and tried to re-install it, it came back as a CD rom drive.
- I restarted my computer, pressed f8, and put disable driver signature.
- The driver re-installed as a CD rom drive.
Can anybody help me identify my problem, and a solution for it?!? Thank you so much
You need to relock the boot loader before running an ruu.
Fastboot oem lock
Did you do a reset in the boot loader or recovery? If you did it in the boot loader you just corrupted the sdcard and need to reformat that
Sent from my HTC One X-
absolutelygrim said:
You need to relock the boot loader before running an ruu.
Fastboot oem lock
Did you do a reset in the boot loader or recovery? If you did it in the boot loader you just corrupted the sdcard and need to reformat that
Sent from my HTC One X-
Click to expand...
Click to collapse
How do you relock the bootleader, do fastboom oem lock, adnd reformat the sd card?
I resetted in both, I believe. I haven't touched my phone in over a week
samoyedpuppy said:
How do you relock the bootleader, do fastboom oem lock, adnd reformat the sd card?
I resetted in both, I believe. I haven't touched my phone in over a week
Click to expand...
Click to collapse
Do a quick Google search for 'fastboot files'
Extract somewhere like C:\
Open command prompt
cd C:\fastboot
fastboot oem lock
Don't format the SDcard
Sent from my HTC One X-
And when you wiped system in recovery your phone had no Rom to boot up into so that's why you couldn't...search fastboot and learn a bit on it like grim said and than in fastboot do the command he said to lock your bl than run the ruu
absolutelygrim said:
Do a quick Google search for 'fastboot files'
Extract somewhere like C:\
Open command prompt
cd C:\fastboot
fastboot oem lock
Don't format the SDcard
Sent from my HTC One X-
Click to expand...
Click to collapse
Should I connect the phone turned off or on?
Also, when I type in the command without the phone, I get: 'not reecognized as an internal or external command, operable program or batch file'
bump
bump
samoyedpuppy said:
Also, when I type in the command without the phone, I get: 'not reecognized as an internal or external command, operable program or batch file'
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://www.dropbox.com/sh/vdmnx14u1pkn4s8/vDVJJI44XW/fastboot2.jpg
Related
hello there, i am trying to root my htc one x+
But while typing "fastboot oem get_identifier_token" to unlock the bootloader, i get the response "waiting for device" forever!
on the phone,it is showing "fastboot usb" and also the cell is being detected on normally being connected to the pc!
I even checked the device manager, all the drivers are proper, no exclamation mark near the htc device.
I downloaded the fastboot files from htcdev and ran it. Also downloaded and installed Android SDK as mentioned on htcdev.Also downloaded AdbWinApi.dll and Adb.exe from here:
http://adbshell.com/download/download-adb-for-windows.html
Placed all of them in a separate folder &ran the above command.
Also i copied adbwinapi.dll and adbwinusb.dll in win\system32 just in case.
i also ran the adb.exe
Also turned off the fastboot option on the device
Also restarted the pc and left it overnight just in case....
I have no idea what's going wrong! Any help!
quantum94 said:
hello there, i am trying to root my htc one x+
But while typing "fastboot oem get_identifier_token" to unlock the bootloader, i get the response "waiting for device" forever!
on the phone,it is showing "fastboot usb" and also the cell is being detected on normally being connected to the pc!
I even checked the device manager, all the drivers are proper, no exclamation mark near the htc device.
I downloaded the fastboot files from htcdev and ran it. Also downloaded and installed Android SDK as mentioned on htcdev.Also downloaded AdbWinApi.dll and Adb.exe from here:
http://adbshell.com/download/download-adb-for-windows.html
Placed all of them in a separate folder &ran the above command.
Also i copied adbwinapi.dll and adbwinusb.dll in win\system32 just in case.
i also ran the adb.exe
Also turned off the fastboot option on the device
Also restarted the pc and left it overnight just in case....
I have no idea what's going wrong! Any help!
Click to expand...
Click to collapse
Hello first run
Code:
fastboot devices
if you can see your device the procceed with your command. If you can't see it something is wrong with the fastboot configuration.
root-expert said:
Hello first run
Code:
fastboot devices
if you can see your device the procceed with your command. If you can't see it something is wrong with the fastboot configuration.
Click to expand...
Click to collapse
nopes...on typing "fastboot code", it redirects me to the current directory:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
what to do?
Are you sure you are in fastboot mode?
root-expert said:
Are you sure you are in fastboot mode?
Click to expand...
Click to collapse
pretty sure...u can see the pic at:
What now!? :crying:
quantum94 said:
pretty sure...u can see the pic at:
What now!? :crying:
Click to expand...
Click to collapse
First of all download and install the official andorid sdk from google and then try to run fasyboot from there.
Follow these instruction to install the complete sdk tools.
If this doesn't help try reinstalling your device drivers.
root-expert said:
First of all download and install the official andorid sdk from google and then try to run fasyboot from there.
Follow these instruction to install the complete sdk tools.
If this doesn't help try reinstalling your device drivers.
Click to expand...
Click to collapse
sorry for the late reply....
I tried the same thing on different pc and it worked!
But i have another problem!
I installed cm11 nightly for my on my x plus from here:
http://get.cm/get/qG0
After that my imei has gone blank along with the baseband version.
I did a bit of research and found that by using ruu, u can get the imei back.
So for that i needed turn my s-on to s-off by the foll commands:
adb reboot
if i am not mistaken, while the phone is rebooting i am supposed to put the 2nd command:
adb wait-for-device push firewater /data/local/tmp
The problem here that I think is the phone reboots so fast that i guess the command fails to execute and i get an error saying :
error protocol fault (no status)
So, how to turn off fastboot or quickboot in cm11? There is absolutely no option in the phone. I tried battery settings,power settings, everything!
is there a way to disable fastboot/quickboot in bootloader mode?
plz help!
Hey there,
I´ve received my used Oppo today and couldn´t do stuff with it so I decided to flash it with CM13 and after some more things I did, I couldn´t restore my backups properly anymore (why I find odd and this has never happened to me before). Then I decided to switch back to ColorOS 2 following the instructions on oppoforums.com. Somehow I think that when I finished step 4: To make a clean install please select "Wipe data and cache", press "Yes" when it's done. my entire internal storage was wiped :-/ instead of wiiping data and cache it turned off and on and so on....it didn´t boot into ColorOS so I went with booting into TWRP again. There I found that I can only see some folders of Interal Storage
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(open in new tab). I managed to adb-move the file "cm-13.0-20160311-NIGHTLY-r7plus.zip" into /sdcard and tried to install it from there which it apparently does successfully
.
When I click reboot -> system it still boots into TWRP everytime :crying:
How can I boot into an OS again? My computer recognizes my phone and I have adb access.
hmm... try use msm download tool
I have the same issue couple of days before... do this
Download Stock Recovery.
Boot in to fastboot
and flash stock recovery using this command fastboot flash recovery stock.img
After flash use command fastboot reboot
if you see wiping data and gone black screen then follow this....
Use this command. fastboot boot stockrecovery.img
now you can boot to stock recovery and you will see fully loaded wiping bar and it shoul reboot the phone. Now its done.
Power of the phone by press and hold. And boot to recovery asusal u do...flash the rom.
for qurey whatsapp me +919790397283
sriszone said:
I have the same issue couple of days before... do this
Download Stock Recovery.
Boot in to fastboot
and flash stock recovery using this command fastboot flash recovery stock.img
After flash use command fastboot reboot
if you see wiping data and gone black screen then follow this....
Use this command. fastboot boot stockrecovery.img
now you can boot to stock recovery and you will see fully loaded wiping bar and it shoul reboot the phone. Now its done.
Power of the phone by press and hold. And boot to recovery asusal u do...flash the rom.
for qurey whatsapp me +919790397283
Click to expand...
Click to collapse
Thanks, this actuually did it for me! I tried adb sideload, but that didn´t work.
https://goo.gl/photos/vSRMhRjyxr4MW8CA7
No ... Dont side load.
Just boot to twrp. Not flash.
Go to Fastboot. and boot . use this command. fastboot boot twrp.img
then you can mount internal storage.
Hello
so after filming for 5 seconds underwater my z3's screen turned black and turned off permanently. though it seems to still turn on normally
after unsuccessful replacements and search on the internet the logical explanation was that the gpu is dead
so now i want to recover the data (photos, videos, music) i have on the internal memory
the device is locked by pattern lock so i can't access it when i plug it (it just detects the device)
i want to know if flashing will remove the lock without clearing my data
and if so how can i do it with a dead screen
best regards
I can think some ways of doing data recovery...
1: Safe method if you have recovery!
you can do a soft reset by pressing the button on the side of the sd card/sim tray.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Press it till it vibrates for a second time, this time it will shut down.
After this, you can turn on your phone and enter recovery (if you have a custom rom or kernel), in this mode you can fetch your files from the internal storage by connecting it via usb to your computer.
2: Use as last resort and confirm the internal storage wiping before doing anything...
Unlock bootloader (I cant remember if it does erase the internal storage partition or not) to install a custom kernel that has recovery.
3: Probably the second safest but it's needs searching the tools if you don't know how to use adb.
If you do have USB Debugging enabled in the phone, you can try to fetch files by using adb in your computer.
Open a CMD in the directory where adb.exe is located and write this code
adb.exe pull /sdcard/ c:/sdcardbackup/
Click to expand...
Click to collapse
It will fetch your files from internal storage to a folder called sdcardbackup on your C:/ drive
Hope this can help you!
If you're going with flashtool, you need to wipe the data partition called userdata since there is where the config is stored but it also wipes the internal storage
hello thanks for the reply
1. tried no luck
2. bootloader is already unlocked and phone is rooted
3. i remember unlocking usb debugging (always do on android) so i will try this, i'll keep you updated on the results
best regards
update :
for whatever reason the phone isn't authorized anymore and i can't access it. anything i can do about it
mm.salem said:
hello thanks for the reply
1. tried no luck
2. bootloader is already unlocked and phone is rooted
3. i remember unlocking usb debugging (always do on android) so i will try this, i'll keep you updated on the results
best regards
update :
for whatever reason the phone isn't authorized anymore and i can't access it. anything i can do about it
Click to expand...
Click to collapse
Hi, as your bootloader is already unlocked try to continue with 2.
If you haven't installed a custom kernel try to install a kernel like EliteKernel, you can find it here in the forums.
Use flashtools and flash boot.img via fastboot mode on your phone, that way you will have a recovery working.
update
flashed Z3FotaTWRPV5.img into it and got it to boot to recovery
i just got my pictures including the picture that killed my gpu (ironic)
anyway thanks for the help... can i edit this to solved?
my phone has been running pure nexus with su since jan and today my phone decided to bootloop
i tried putting my phone into fastboot mode and pushing twrp.img through ADB, but the phone bootloops before it even receives the complete file (remote: flash write failure)
so then i tried getting the factory image through google and selecting the flash-all.bat, but the same thing happens, the phone bootloops
aznpiggy said:
my phone has been running pure nexus with su since jan and today my phone decided to bootloop
i tried putting my phone into fastboot mode and pushing twrp.img through ADB, but the phone bootloops before it even receives the complete file (remote: flash write failure)
so then i tried getting the factory image through google and selecting the flash-all.bat, but the same thing happens, the phone bootloops
Click to expand...
Click to collapse
Try unzip the factory image and flash imgs separately, follow this guide where it says "What to Do If the Script Doesn’t Work" (below the middle of the page), so you should have finished each step before it bootloops again.
TENN3R said:
Try unzip the factory image and flash imgs separately, follow this guide where it says "What to Do If the Script Doesn’t Work" (below the middle of the page), so you should have finished each step before it bootloops again.
Click to expand...
Click to collapse
ill try tomorrow but i dont think there is enough time to push a single file before the phone bootloops itself
theres literally a three second window
Also, have you tried just wipe? Maybe there is a system error, and if you wipe from adb first it'll fix itself (just type "fastboot -w" and press enter)
TENN3R said:
Also, have you tried just wipe? Maybe there is a system error, and if you wipe from adb first it'll fix itself (just type "fastboot -w" and press enter)
Click to expand...
Click to collapse
i tried doing what you mentioned but it keeps failing
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bump
edit:
Code:
BL: N/A
Basebands: N/A
Product/Variant: sailfish-US-PVT
Serial Number FA6BN0300789
CPU: MSM8996SG-AB 0x10001
UFS: 128GB Toshiba
DRAM: 1096MB Hynix LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: PRODUCTION
Device is UNLOCKED
ive tried wiping my phone and reinstalling the factory images but i get an error message (bootloader is unlocked and adb/fastboot are up-to-date)
is my memory corrupted? if it is, could i lock the bootloader and send it out under the manufacturers warranty?
editedit:
i contacted google and they said theyd be willing make an exception and help me, but i need to ask my carrier to help me unroot the device first. i dont think it can be unrooted it if i cant even flash the factory images onto it, let alone wiping the device (-w).
what did u do before your phone like this ？
almightysiman said:
what did u do before your phone like this ？
Click to expand...
Click to collapse
i was was watching youtube full screen and when i tried to swipe up to browse more videos, the phone shut off
aznpiggy said:
i was was watching youtube full screen and when i tried to swipe up to browse more videos, the phone shut off
Click to expand...
Click to collapse
bad luck.
in brief:
the data should be there on the phone, so there's hope it should be easier to recover than deleted data but i run out of ideas how to get adb to find and pull it... maybe a more advanced user has better knowledge (better commands or tools)
adb devices and fastboot devices communicate with phone, so i have all drivers installed, i can only tackle with it via usb from windows 7 based computer
the detailed story:
i have a huawei g620s-L01, stuck in bootloop (just loading huawei logo forever or until battery empty but does not restart) and also "volume down" button does nothing... the bootloader is locked and huawei seems to have stopped providing unlock codes...the touch works but is shattered so i was told repair the button is not an option...
i can boot it into recovery mode using "volume up + power" but i can't use the recovery menu due to the dead "volume down"
from recovery menu i can only "reboot system now" but that re-enters the bootloop,
also i get bootloop if i try to boot into download mode via adb command
i can use some adb commands (i say some because some return errors, others say i don't have permissions)
i can boot into fastboot via adb command too...i can not find my dcim folder or any data folder to use the pull commnad, i tried the generic commands to pull sdcrd or dcim or all files with *.jpg
the user data is not accesible, i could browse some system directories but they did not contain my files via cd commands
i found some threads saying maybe i need mount or root commands
but trying to mount partitions or access su via adb also gives errors
su is not found, i do remember there was a su when android was working on the devices but is useless if i can't find/access it
i found the factory rom and some tools to try to restore rom to the phone due to claims that same rom might find my data, but the tools failed to start due to locked bootloader
i also tried several versions of full android sdk (old and new) trying to find "monitor or file browser" tools but the menu is not there...perhaps it will not activate those tools when device is in fastboot/recovery modes
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i also found a 3rd party full android browser but can't connect with it either
also recovery softs are useless, they need a working android to try to recover anything...some recovery softs claimed they can fix bootloop but don't support my device
free tools that try to unlock bootloader also failed
so at this point i am running out of things to try
this is what i figured so far: i can see my data but can't touch it
i seem to have 4 partitions on the device:
1 is called sdcard but has nothing accesible on it, could be the feature for external card
2 is called ext , total size is 711,49mb , used 124,98 and available 586,5
3 is called system , total size 1,64 gb, used 1,23gb, available 418,1mb
4 is called data, total size 3,96gb, used 3,75gb, available 218,16mb
clearly the data partition is still keeping my data
i can not see my installed apps, so i guess they are also on that partition
i can see some system apps, namely 49 out of 146
so i'm guessing the issue is with one application, likely system app since i can't see them all
the phone may be partly rooted, the android may have some rooted features but the adb on it is not rooted
so i can not use the adb root command to get to my data
and i can not try to flash recovery or rom or custom boot img from adb due to bootloader locked and asking for unknown code