Hi everybody, i am really sorry about my english i hope you guys can understand what i am trying to say.
a few mounths ago i rooted my Htc one m8 using the AIO toolkit. I flashed it with the TWRP 2.7.0.2 recovery.
Last week i wanted to update my Htc and found a guide how to update but i messed up. It said something like that I have to remove the root then install a file they had on their site on my phone.( I can't say which guide it was because i don't have the pc i used last week to do this.)
After i did that my Htc got stuck in a bootloop- I can access the Fastboot menu but when i choose Recovery or Factory reset option my phone just reboots but doesnt get past the HTC logo.
I am trying fixing it with the AIO toolkit but an error message shows up saying "device not found" or
"waiting for device" my pc is on windows vista an recognizes my phone- I installed the right drivers and on the fastboot menu it says "fastboot usb" highlighted in red.
I am a really noob at this so have you guys any idea how I can fix this? Why do i get the message "device not found" , when my pc recognized my phone and all the drivers are installed?
And also my pc is in safe mod with network because i get a blue screen when booting the normal way-
Do you think thats why i get the error message " device not found"?
Related
Hi,
I have an issue with a Nexus S i9023 of a friend
I installed the latest stock ICS CF_YAKJU_IMM76D some months ago and everything was fine.
I broke the glass of the screen and it was substitued: after a couple of months, the phone entered in a bootloop.
I tried to access recovery but was impossible, I could get to Fastboot and Download mode but choosing recovery from the first started bootlop again.
I flashed a latest CWM in fastboot via adb but no joy.
On top of that, handset behaviour is strange because only 1 on 20 times it is recognized by the PC as a Samsung device, in all other cases it is a "unknown device".
I remove all drivers from Windows and reinstalled the naked version, but again only sometimes I get it... I found out I need to have connected another handset (my HTC currently...) to have it recognized!
Now I can enter in download mode using the USB jig and I can see it from Odin, but if I use the
CF_YAKJU_IMM76D_full.tar
I get "verify image ipbl (fail)" on the handset.
If I use
CF_YAKJU_IMM76D_nowipe_nobootloaders_norecovery.tar
I get an "invalid volume size"
Do I have an hardware issue here? Some partition/internal memory with failure?
What else can I try to flash via Odin?
Obviously now after the fail I can't even get fastboot...
I also tried Unbrickable resurrector under Linux but it doesn't recognize the handset when I connect it.
Any suggestion? :crying:
SergioBigred said:
Any suggestion? :crying:
Click to expand...
Click to collapse
Ok, update. Using this thread I was able to flash via Odin 1.82 the 2.3.4
However I am still in a bootloop and I can't get fastboot but not recovery... and in fastboot I can't via USB the handset because it says "usb device not recognized"
A few days ago my phone started acting weird as it would not boot beyond the initial Google screen. It was random behavior as sometimes it would boot normally but sometimes i would have to do a battery pull. Its a rooted phone which was running Cyanogen 7.
I tried booting into recovery to find that it was not mounting the SDcard and always shows the message "error mounting SDcard". After reading on some forums that it could be a CWM issue i was able to flash a new CWM (one which was more stable) as well as Cyanogen 9 but the problem still persisted.
The situation now is that i cannot get it to even connect to my laptop since the ADB drivers are not being installed on my Win8 even after unchecking the "check for signed drivers" option in Win8. Without the phone being recognized i cannot flash anything to the device.
I suspect there may be something with the hardware, as sometimes the phone does not even power on. Any help on this would be appreciated as my phone is just lying there. Which is provoking me to buy an S3
When you plug it into your computer does it show up in device manager at all? Also I don't know win8 as well as win7, idk if they kept device manager in there...
Wafflcopterz said:
When you plug it into your computer does it show up in device manager at all? Also I don't know win8 as well as win7, idk if they kept device manager in there...
Click to expand...
Click to collapse
it shows as Android 1.0 but as i was trying to revert to stock rom and cwm using the Nexus Toolkit i removed any and all device drivers that had been previously installed as instructed by the guide in the toolkit.
I used was always able to see Android 1.0 while in bootloader but if i went into recovery it showed "Nexus" in the device manager, yet the recovery gave the message "unable to mount sdcard"
eddyed911 said:
it shows as Android 1.0 but as i was trying to revert to stock rom and cwm using the Nexus Toolkit i removed any and all device drivers that had been previously installed as instructed by the guide in the toolkit.
I used was always able to see Android 1.0 while in bootloader but if i went into recovery it showed "Nexus" in the device manager, yet the recovery gave the message "unable to mount sdcard"
Click to expand...
Click to collapse
do the fastboot command to flash stock
Cascabreu said:
do the fastboot command to flash stock
Click to expand...
Click to collapse
it cant find the device..just shows "waiting for device" nothing happens after that have to CTRL+C out of it. Here is what i think is going on and anyone is welcome to input their comments:
1. Windows 8 is probably not allowing the Samsung drivers to be installed which is why the phone always shows "!" next to it in the device manager
2. Once i am able to get the drivers in there i should be able to flash a new recovery since the one i currently have CWM 5.0.2.0 is causing the sdcard not to mount and i always get the "error mounting sdcard" when i try the mounts and storage
3. Once that is fixed i think i should be able to flash a new ROM
eddyed911 said:
it cant find the device..just shows "waiting for device" nothing happens after that have to CTRL+C out of it. Here is what i think is going on and anyone is welcome to input their comments:
1. Windows 8 is probably not allowing the Samsung drivers to be installed which is why the phone always shows "!" next to it in the device manager
2. Once i am able to get the drivers in there i should be able to flash a new recovery since the one i currently have CWM 5.0.2.0 is causing the sdcard not to mount and i always get the "error mounting sdcard" when i try the mounts and storage
3. Once that is fixed i think i should be able to flash a new ROM
Click to expand...
Click to collapse
i use windows 8 and everything works, dont use samsung drivers use google ones.
check this thread made by me and try again:
http://forum.xda-developers.com/showthread.php?t=1901617
I think its your laptop not having the right drivers. I don't have a Nexus device right now (not sure why I'm posting here), but I think it's supposed to say something else beside "Android 1.0", which tends to mean the driver isn't correct. I wouldn't discount using Windows 8 as an issues.
But I have similar issues in the past with multiple Android drivers conflicting. When you remove drivers from the Device Manager, make sure to also check the box telling it to delete the files from the system as well.
Then use the Google USB driver, links in my signature.
Hello to all.
My first post was about One mini with unlocked bootloader and failed system. Situation changed so I describe all "story" wondering that sb clever would tell me what to do now...
At the beginning, I visited some "specialist", who applied me a fantasy about bootloader rebuilding and took cash for nothing. Because thay said that tried to flash European ROM on device bought in USA with ATT brand and S ON (look attach) I had to learn a little to do anything by myself.
First of all I flashed TWRP Recovery using AllinOne. First CMD window replied "device not found" but second one responded that Recovery was flashed succesfully. In fact TWRP run. And it was all.
Than I tried to do anything by ADB. Drivers were installed correctly but any command form adb responded "device not found"
Device manager showed QHSUSB DLOAD when connected not powered one mini. (Yes I know what it means)
Sideload in TWRP was not working too.
Flashing wih USB OTG mounted under TWRP was not working too.
Newest RUU_M4_UL_K44_SENSE60_MR_Cingular_US_4.13.502.3_ from htc site (.htc.com / us / support / htc-one-mini-att / news / ) was showing connection error at the beginngin but was detecting system version and suggested update. Always failed after reboot.
Today I tried to flash RUU.zip (ver same as installed on my bricked one mini). AllinOne asked about Bootloader lock so I relocked bootloader. Flashing failed so I started mentioned newest original RUU from HTC. Bootloader was rebooted and procedure started. (with unlocked bootloader it failed at this moment) Unfortunaelly it stopped at 95% with comunicate "signature error".
Cell restarted, htc logo appeared ("by android" sign was added) and device manager detected HTC device and mass memory. Unfortunetelly system havent boot up and now manager shows only "not recognized device" but QHSUSB DLOAD not appeared again
What would you advice to do now? Try to update again? When you check Fastboot reply at CMD screenshot than it seems to be ALMOST updated. But still sth is wrong
I read RUU log and edited fonts colour to make it more readable.
I can see that all time ADB has a problem with "adb devices" command and it asks fastboot (i coloured it on pink).
Later it flash two almost 400MB each zip files but after second one gives signature fail. If Update comes from HTC and almost all update was correct what may it mean now?
I attach
1 image with bootloader details when bought broken
2 image of ADB fastboot report after 95% Update to 4.13.502
3 log from Updater
Hello everyone.
Just to get it out of the way, I am very inexperienced with android products. At the moment, I'm having trouble getting my HTC One X (at&t) version to turn on. It all started when I decided to update the android version from 4.1. something to 4.2.2. I went to this site, the HTC website (www . htc . com / us/support/htc-one-x-att/news/) and downloaded the executable file and ran it . Once installation was done a message popped up on my computer stating an error occurred. I look at the phone and it shows the HTC splash screen for a few seconds and it shuts off and immediately turns back on with the HTC splash screen again, a bootloop. I then found out that I can restore the device by entering fastboot and selecting the factory restore option. This didn't restore the device but just entered the bootloop process again. I entered fastboot mode again and this time I selected the recovery option which also failed. I hook up the phone with USB 2.0 to the computer to transfer a stock ROM but computer doesn't recognize the phone anymore ( the computer did at first recognize the phone during installation of 4.2.2). After various attempts to get the phone to be recognized by computer, I gave up and called it quits and decided to power it off through the fastboot option. And now I can't even turn on the phone at all. I plug it to the computer to see if that will prompt the phone to turn on but all that does is charge the battery. The computer does recognize that something is connected to it but fails to recognize the phone.
Is there anything I can do to get this phone working again? I would much appreciate any help with this.
Ok guys I managed to get the phone to turn on again, buts its still in bootloop. Once the phone turns on, the computer notices that the phone is connected and tries to install the drivers but fails as soon as the phone restarts. Essentially the computer is unable to finish installing the proper drivers in time. The driver that its trying to install is "HTC MTP Device".
Put the phone into bootloader mode and run the RUU executable again.
Transmitted via Bacon
Ok its finally working. Thanks for the help!
Today I got a message that I could update my telephone. So downloaded it, restarted and just near the end of the update install it gave an error.
I tried to restart but didn't get past the boot screen. I can get into the selection menu of recovery mode/ factory mode.
But when I choose factory mode I don' t get past the boot screen and in recovery mode I get a "dead android with: no command" and there is nothing I can do. (I wiped the cache etc. but nothing helped) (ALPS.KK1.MP3.V1)
And I can' t apply an update from ADB because when I connect it to my PC (windows 10) I get the message its not recognized.
Device manager gives this error: Unknown USB device (Device Descriptor Request Failed) Error Code 43.
If I connect my telephone via USB using ubuntu (15.10) it isn' t recognized at all not even when i check with the lsusb command.
I hope someone has an idea to steer me on the right way!
solved
Well.. seems like trying a different cable, trying many usb drivers and reading a bit better also helps! So if you read this and have the same problem: keep trying/ searching/ reading!