So I tried to load a ROM to get 4.4.2 and upon start up I got stuck on the new Boot screen. I'm pretty sure I bricked it, I tried clearing cache and dalvik cache and system (with TWRP) after I had no luck there. Now upon start up I get stuck on the HTC boot screen. Is there anyway I can fix this, I pretty much define the word newbie on this stuff so any step by step help is really appreciated
As a follow up I also get a message when trying to do anything from recovery that says ' No OS Installed! Are you sure you wish to ____?' and the phone is no longer recognised by my pc (I have all relevant drivers)although the pc acknowledges that there is something in the usb port
iClueless said:
As a follow up I also get a message when trying to do anything from recovery that says ' No OS Installed! Are you sure you wish to ____?' and the phone is no longer recognised by my pc (I have all relevant drivers)although the pc acknowledges that there is something in the usb port
Click to expand...
Click to collapse
Are you using Windows 8/8.1 ?
Had the problem, too and found a fix for it... Install Win7 or something older
The Thing with "No OS installed"... have u got a unlocked Bootloader? :/
Related
Hi Everyone, after i read a lot about rooting i'm trying to do so...
I Downgraded my legend from 2.05 to 1.31, then I followed modaco instruction, installing adb, creating a goldcard, doing step 1.
All works perfect...
After step1-windows.bat, the Legend return to the fastboot screen. I changed my SDcard(the Goldcard) with another one (Not Goldcard)and rebooting the phone in fastboot mode. Here i entered the Bootloader, and using vol down i entered recovery mode (The screen with the black phone with a triangle and a !). then i run step2-windows.bat but i'm stuck with a lot of errors... and still remaining on the recovery mode without the wipe selection (i tried the optic trackball but nothin happens still no wipe selection)... What can possibly be? I use Windows 7 64 bit, maybe is this the problem?
the problem is daemon not running (with consequence trying to restart it), and daemon still not runningerror:cannot connect to daemon....
if needed i can post the windows terminal...
Thxs a lot in advance
Had the same problem in win7x64 when I rooted my legend. I eventually did step2 in linux running in virtualbox (you could use a linux liveCD too). I suspect some driver issues, but never investigated further.
Probably driver issues, Installing HTC Sync might fix the problem.
Hi
i got same broblem then i used the "recovery-clockwork-legend"
it will do the same thing as without connecting to the USB
it is being explained under topic "Fake-flash by Koush, launching recovery without a PC" in this forum
please follow the same step in this topic
" forum.xda-developers.com/showthread.php?t=698404 "
"please make sure that u have save the both the rom that u want to flash it and the update.zip files to ur micro SD card"
Thanks and best of luck
Try to go into taskmanager and kill htcUPC, and then try step2 again, that worked for me
Solved using linux ubuntu 10.10 althought i think i can solved too with buusing suggestion... i thought too that it was a conflict on some HTC driver part but didn't know what to kill...
Howewer strange things continue to happen... recovery-linux.sh (or recovery-windows.bat) didn't work... so i managed to relaunch step2 to install the new ROM... all works accordingly then... and now i have azure on my legend...
Thank you Everyone! I Mean IT!
to solve this problem, between step 1 and 2, type on a console "adb kill-server" and then write step2-windows or step2-linux, etc.
I don't really know what I messed up but my computer doesn't recognize my phone any more.
After flashing Ultimate 8.2 beta and Ultimate 8.2 it just doesn't work.
What could I have done the mass storage is working with everyone except me.
I included some pictures. I'd appreciate getting helped.
banttu said:
I solved my problem here's the steps.
1. make sure that you have a rom on your sd-card to flash (just in case)
2. do a nandroid backup trough CWM
3. factory reset your phone, reboot
4. uninstall the phones drivers from the computer. unless you have a computer which doesn't have them installed
5. Connect your phone into computer and let it install the sd-card drivers
6. remove the mass storage from your computer safely
7. install the samsung galaxy s drivers for your computer
8. plug your phone into the computer. now it should be recognized and you'll be able to flash to stock if you want via Odin
Click to expand...
Click to collapse
banttu said:
I don't really know what I messed up but my computer doesn't recognize my phone any more.
After flashing Ultimate 8.2 beta and Ultimate 8.2 it just doesn't work.
What could I have done the mass storage is working with everyone except me.
I included some pictures. I'd appreciate getting helped.
Click to expand...
Click to collapse
try uninstalling the drivers for your phone on the pc.
factory reset your phone.
Does it recognise in odin when in download mode?
The same issue. I have Ultibread 1.4 and wanted to flash the JVK but windows keep disabling it. Can't find the device either in normal state or in download state. Odin also didn't recognize it
I'm on win7 x86
Did a factory reset - still the same
I tried different cables and PC's - no luck Anyone !! Any idea?
nightrave said:
I tried different cables and PC's - no luck Anyone !! Any idea?
Click to expand...
Click to collapse
I solved my problem here's the steps.
1. make sure that you have a rom on your sd-card to flash (just in case)
2. do a nandroid backup trough CWM
3. factory reset your phone, reboot
4. uninstall the phones drivers from the computer. unless you have a computer which doesn't have them installed
5. Connect your phone into computer and let it install the sd-card drivers
6. remove the mass storage from your computer safely
7. install the samsung galaxy s drivers for your computer
8. plug your phone into the computer. now it should be recognized and you'll be able to flash to stock if you want via Odin
Didn't help in my case. I did the backup and wipe/factory reset the phone. Enabled the debugging mode, removed kies and all the drivers, rebooted the phone and the pc, connected the phone to pc and had the same message Any idea where I could got it wrong?
P.S. ANd the phone is now extreeeemly laggy and unresponsive
Well this is brilliant! I have made it even worse. I thought thought, that maybe the kernel is the cause of the issue, downloaded the SGS KErnel flasher and flashed the CF-Root-XW_OXX_JV1-v1.3-BusyBox-1.17.1. After the reboot the phone is stuck at the GalaxyS logo and is not booting. I can get into the recovery and the Download mode but the phone is still not being recognized and when I try now to wipe/data or do a factory reset I get loads of red errors Please tell me that I didn't brick it yet
nightrave said:
Well this is brilliant! I have made it even worse. I thought thought, that maybe the kernel is the cause of the issue, downloaded the SGS KErnel flasher and flashed the CF-Root-XW_OXX_JV1-v1.3-BusyBox-1.17.1. After the reboot the phone is stuck at the GalaxyS logo and is not booting. I can get into the recovery and the Download mode but the phone is still not being recognized and when I try now to wipe/data or do a factory reset I get loads of red errors Please tell me that I didn't brick it yet
Click to expand...
Click to collapse
Do you have a rom on your sd-card? Flash it trough recovery.
Or doesn't recovery even recognize your sd-card?
banttu said:
Do you have a rom on your sd-card? Flash it trough recovery.
Or doesn't recovery even recognize your sd-card?
Click to expand...
Click to collapse
I have forgot to put it on ( ARghhh! My stupidity is amazing.
When I go into recovery I get lots of:
e:failed to mount /cache
and
e:Can't open /Cache
nightrave said:
I have forgot to put it on ( ARghhh! My stupidity is amazing.
When I go into recovery I get lots of:
e:failed to mount /cache
and
e:Can't open /Cache
Click to expand...
Click to collapse
And I guess that there's no nandroid backup either?
Though they didn't work in my case.
banttu said:
And I guess that there's no nandroid backup either?
Though they didn't work in my case.
Click to expand...
Click to collapse
It was in the previous kernel. But in the last one I've flashed there is no restore/backup functionality, although the backup might be actually be on the sd card
nightrave said:
It was in the previous kernel. But in the last one I've flashed there is no restore/backup functionality, although the backup might be actually be on the sd card
Click to expand...
Click to collapse
Well, there seems to be only a one solution.
You have to uninstall the phones drivers, and install them again.
Then plug your to your computer in download mode and it'll install rest of the drivers.
Then Odin should be able to recognize your phone and your good to flash stock.
But you really, really have to uninstall the drivers
Well I did it before. I uninstalled all related to samsung from the add/remove programs. Rebooted the pc and still getting this error. In the properties of the device in the device manager I have "unknown device". I don't have any drivers on the pc as far as I see. I install the drivers from here. Connect the device again and get the same error
nightrave said:
Well I did it before. I uninstalled all related to samsung from the add/remove programs. Rebooted the pc and still getting this error. In the properties of the device in the device manager I have "unknown device". I don't have any drivers on the pc as far as I see. I install the drivers from here. Connect the device again and get the same error
Click to expand...
Click to collapse
Hmm.. I did change the computer.. Maybe you should put the drivers on a flash drive and go to your friends computer to flash.
The thing is that he does not have the drivers installed before either.
Don't know why it worked for me but... it worked.
I am going to try the last thing - I have a System backup from the time I definitely didn't have them on the PC and see if this helps....
Nope.... Didn't help.... I am completely desperate. Maybe anyone would have another magical solution?
Guys! ANy idea? Plzzzzz. I'd do anything to get it back to life
Me too i get "unknown device" when attached with usb in download mode...ive been trying to get it back workin for a week now...tried everything...which means i can't flash it to gingerbread
Anyone got any ideas ?
I have tried different PC's and it's the same. Is there maybe a way to reset the device somehow?
nightrave said:
I have tried different PC's and it's the same. Is there maybe a way to reset the device somehow?
Click to expand...
Click to collapse
Hi!
I have a similar problem.
For few days, I cannot connect my SGS to my Notebook.
I have windows 7 x64 installed, and it has never had any problems with connections.
Now, I don't know why, but I cannot connect it.
I tried to connect it to another computer, which has windows 7 x86.
And it was succesfull!
Now, it seems, that I don't have a hardware issue, but I cannot imagne, how I could solve this problem.
I already tried these:
- remove drivers/programs
- tried other USB slots
- downloaded newer USB driver for x64
- removed USB drivers (all of them)
- unplugged my notebook for over 5 minutes (also removed the battery)
Every time I plug my SGS to my PC only this message appears:
"unknown device" - or something similar, because I have a hungarian windows 7.
Sorry about my english.
Has anyone any idea?
Thx for advance
Hi guys.
I'm really in need of some big help. I tried to update my phone today (HTC One with OneDroid), because it said there would be a new stable (!) version. So I installed it, but then after rebooting the device, the message "Unfortunately, the process com.android.phone has stopped." pops up. I can press "OK", but it just appears again, and again, and again. I already had this bug a few times, but I was able to solve it with flashing the rom again.
To the main problem: My PC won't recognize the phone, I'm not able to load a new ROM on the sd card. Fastboot USB also doesn't seem to work. Also, my SIM-Card doesn't seem to work, obviously there must a connection between the error message and this failure.
How can I make it visible on my PC (WIN 7 btw.) so I can load a new ROM on the phone or how can I make the error disappear?
Versions:
OneDroid CM11-20140405-SNAPSHOT-M5-m7
TeamWin Recovery
HTC undlocked via HTC Dev.
Already tried factory reset, bug still existing, so I guess it's because of the actually unstable ROM. How can I make my PC recognize the phone?
Thanks in advance!
Did you take a nandroid backup in TWRP before flashing the new rom/update?
If you can boot normally your pc wont recognize your phone, thus not being able to copy another rom zip, then do it via adb sideload.
aightbit said:
Hi guys.
I'm really in need of some big help. I tried to update my phone today (HTC One with OneDroid), because it said there would be a new stable (!) version. So I installed it, but then after rebooting the device, the message "Unfortunately, the process com.android.phone has stopped." pops up. I can press "OK", but it just appears again, and again, and again. I already had this bug a few times, but I was able to solve it with flashing the rom again.
To the main problem: My PC won't recognize the phone, I'm not able to load a new ROM on the sd card. Fastboot USB also doesn't seem to work. Also, my SIM-Card doesn't seem to work, obviously there must a connection between the error message and this failure.
How can I make it visible on my PC (WIN 7 btw.) so I can load a new ROM on the phone or how can I make the error disappear?
Versions:
OneDroid CM11-20140405-SNAPSHOT-M5-m7
TeamWin Recovery
HTC undlocked via HTC Dev.
Already tried factory reset, bug still existing, so I guess it's because of the actually unstable ROM. How can I make my PC recognize the phone?
Thanks in advance!
Click to expand...
Click to collapse
See FAQ 2 in @nkk71 guide to help get your pc talking to device
http://forum.xda-developers.com/showthread.php?t=2541082
mb_guy said:
See FAQ 2 in @nkk71 guide to help get your pc talking to device
http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
Thanks, trying to get it fixed now again.
windieboss said:
Did you take a nandroid backup in TWRP before flashing the new rom/update?
If you can boot normally your pc wont recognize your phone, thus not being able to copy another rom zip, then do it via adb sideload.
Click to expand...
Click to collapse
Unfortunately not, no backup made. Thanks for the tip with adb sideload.
Fixed it, thanks for the tips! :good:
Help me please! I have an htc one m7 AT&T. My device is still s-on, I can access recovery (twrp), but my phone cannot be identified in adb sideload. I am on hboot 1.55.0000. My computer is also bricked so I can't do much unless I drive to my parents. When I went there to use their PC, I installed all the latest htc drivers (even tried some older ones), android sdk and Java SE. I was on a windows 7 64 bit PC. Trust me I've done a sideload before and everything was set up properly. The phone is recognized in fast boot, but not in recovery. The phone has no os on it and recovery says it is no longer rooted. What can I do from here? I am thinking perhaps mounting from usb otg. Will this work? Is there a fast boot command that could be of assistance? I am completely stuck and could really use some help. I don't care what I have to do just explain it to me and I'll love you forever. There is nothing on my internal memory anymore it was wiped somehow. If you need any other info I'll happily provide it for you. Anything involving using a PC or Mac (I have access to both platforms at my parents) will have to wait until I can get out there again. I can't afford a new phone right now and this iPhone im using sucks lol. Thanks In advance for any help.
Anyone... anyone? Please help me.
Justkevin09 said:
Anyone... anyone? Please help me.
Click to expand...
Click to collapse
Are you still needing help with this? Your problem appears to be driver related or possibly a problem with you recovery version.
Which recovery are you using (name and version please) to check if it's a driver problem boot to recovery and connect to a Windows pc. Open the device manager and check what the device is listed as. It should be "MY HTC".
Now I'm running windows 10, I have TWRP v. 2.7.1.1. Like I said previously the computer is not detecting the device at all. I literally have no idea what to do. My new PC doesn't recognize it in fastboot either :/
what is status ur bootloader?
if locked or relocked then
1. install latest htc syn manager
2. run RUU.exe
[EDIT: It's all good now... A stupid mistake of mine]
Ok, everything was fine... I was on PE and everything was normal. Then I wanted to try something out and cleared everything in TWRP and rebooted to fastboot, because I needed a different version of TWRP...
But once in fastboot and connected to my PC adb couldn't detect my device (list of devices attached is empty), so I can't flash twrp -> I can't do anything! I'm simply stuck in fastboot...
After a bit of googling i found out that I somehow had the wrong drivers installed, so I went into device manager and it showed some kind of "kedacom usb drivers". I tried every tutorial that is on the internet, but nothing worked. In the end I somehow got it changed to the regular "Android device -> Android ADB Interface"(how it used to- and should be?) from those "kedacom usb drivers" and I thought I found the solution, but it still doesn't recognize my device in adb I also tried the MiFlash tool - same thing
Is it possible that my mistake was not enabling usb-debugging beforehand and can I somehow get out of fastboot?
I would be so grateful if anyone was able to help me
Moischen said:
Ok, everything was fine... I was on PE and everything was normal. Then I wanted to try something out and cleared everything in TWRP and rebooted to fastboot, because I needed a different version of TWRP...
But once in fastboot and connected to my PC adb couldn't detect my device (list of devices attached is empty), so I can't flash twrp -> I can't do anything! I'm simply stuck in fastboot...
After a bit of googling i found out that I somehow had the wrong drivers installed, so I went into device manager and it showed some kind of "kedacom usb drivers". I tried every tutorial that is on the internet, but nothing worked. In the end I somehow got it changed to the regular "Android device -> Android ADB Interface"(how it used to- and should be?) from those "kedacom usb drivers" and I thought I found the solution, but it still doesn't recognize my device in adb I also tried the MiFlash tool - same thing
Is it possible that my mistake was not enabling usb-debugging beforehand and can I somehow get out of fastboot?
I would be so grateful if anyone was able to help me
Click to expand...
Click to collapse
what the
why dint u just save the new twrp to internal, boot to twrp, flash the new twrp image as recovery m thats it reboot to twrp and it will be the new one you flashed.
you dint have to wipe anything or use pc
Mooatreides said:
what the
why dint u just save the new twrp to internal, boot to twrp, flash the new twrp image as recovery m thats it reboot to twrp and it will be the new one you flashed.
you dint have to wipe anything or use pc
Click to expand...
Click to collapse
Yeah, good question... But it's too late for that now
Try another pc
emprazol said:
Try another pc
Click to expand...
Click to collapse
same thing
Manually install adb driver
Moischen said:
same thing
Click to expand...
Click to collapse
One time, I had such an issue with drivers, what I did is use a free VM machine software on Windows to install a Linux distro (or you could dual boot it), and from Linux it worked to detect my device.
On the other hand, there are really probably easier ways to fix your issue, but who knows, it may help and does not take too long.