I was doing a lot websurfing and the phone got hot but didn't think much of it. Then my screen imagine became distorted and a loud noise came out of the speaker. I had never seen it before. I figured the phone crashed. The power button didn't work, so I removed the battery and put it back in. Now the phone can't get past the "Google" screen (which blurs after a few moments). My phone is unlocked and rooted. It's been so long since I've flashed my phone that I don't know if the usb debugging is turned on and here's where my problem lays. I can't get the phone to be recognized by any of my computers. I've tried a bunch of tools, installing different drivers, and Odin. All of them can't see my phone. I can boot into Fastboot and Odin. I can sometimes boot into CWM, and if I do, all I see is "ClockworkMod recovery v5.8.0.2" and no other options. After 15 seconds, the phone will exit CWM and reboot.
Anyone have any ideas on how to fix this?
Can you boot into recovery and maybe full wipe and re flash? Have you tried a backup? Have you tried mounting in recovery? Should be SD or USB mount try that maybe. I'm not a Dev. But I would try all those first. Post back if possible.
Sent from my Galaxy Nexus using xda app-developers app
Man_Utd said:
I've tried a bunch of tools, installing different drivers, and Odin. All of them can't see my phone. I can boot into Fastboot and Odin. I can sometimes boot into CWM, and if I do, all I see is "ClockworkMod recovery v5.8.0.2" and no other options. After 15 seconds, the phone will exit CWM and reboot.
Click to expand...
Click to collapse
Since you can boot into fastboot, then follow this if you want to return to stock immediately and start fresh, or keep this method for later if you want to try some other solutions first. It is your choice
ahmadallica said:
Since you can boot into fastboot, then follow this if you want to return to stock immediately and start fresh, or keep this method for later if you want to try some other solutions first. It is your choice
Click to expand...
Click to collapse
I can boot into fastboot, but it does me no good if I can't get my computer and phone to communicate. This is where my problem lies. I've tried different USB drivers and none of them work.
savagehax said:
Can you boot into recovery and maybe full wipe and re flash? Have you tried a backup? Have you tried mounting in recovery? Should be SD or USB mount try that maybe. I'm not a Dev. But I would try all those first. Post back if possible.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I can boot into CWM, but there is no option to flash or wipe. All I see is one line of text. That's it.
ahmadallica said:
Since you can boot into fastboot, then follow this if you want to return to stock immediately and start fresh, or keep this method for later if you want to try some other solutions first. It is your choice
Click to expand...
Click to collapse
Man_Utd said:
I can boot into fastboot, but it does me no good if I can't get my computer and phone to communicate. This is where my problem lies. I've tried different USB drivers and none of them work.
Click to expand...
Click to collapse
Did you try the "Universal Naked Drivers" linked in ahmadallica's post?
Sent from my Nexus 4 using Tapatalk 2
Man_Utd said:
I can boot into fastboot, but it does me no good if I can't get my computer and phone to communicate. This is where my problem lies. I've tried different USB drivers and none of them work.
Click to expand...
Click to collapse
I think it is bettER to uninstall the drivers you have already, and try another USB port. Did you try that as well?
Download the galaxy Nexus toolkit and that will apply the stock image vai google. You can restore your phone from scratch back to stock.
Sent from my Galaxy Nexus using Tapatalk 2
3rdstring said:
Did you try the "Universal Naked Drivers" linked in ahmadallica's post?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
3rdstring said:
Did you try the "Universal Naked Drivers" linked in ahmadallica's post?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Okay, I figured out why my computer couldn't see the phone. The USB cable was bad. It charged the phone, so I assumed it worked. Tried another cable and now the computer sees the device. Stupid cable!
So, I got going using fastboot but now I have another problem. I can connect to the phone and my computer sees it, but when I try a flash command like "fastboot flash bootloader bootloader.img", I get "Failed (status read failed (Too many links))". I've been doing some reading and see this is not a good thing.
I haven't tried Odin, because I read in another post by efrant, not to use Odin if I'm getting the "Failed (status..."
I probably have a hardware issue, right? Any suggestions?
Thanks to everyone for their input!!!
I tried using fastboot to boot into the latest recovery .img file. Again, all I got was the title "ClockworkMod Recovery Mod 6.0.1.9"
Man_Utd said:
I tried using fastboot to boot into the latest recovery .img file. Again, all I got was the title "ClockworkMod Recovery Mod 6.0.1.9"
Click to expand...
Click to collapse
Try using fastboot to flash TWRP recovery image not CWM.
Download it from here if you have GSM GNex (Maguro), otherwise, just choose your device from the same website
And what about returning to stock using fastboot? You changed the USB cable so seems this should work with you now.
ahmadallica said:
Try using fastboot to flash TWRP recovery image not CWM.
Download it from here if you have GSM GNex (Maguro), otherwise, just choose your device from the same website
And what about returning to stock using fastboot? You changed the USB cable so seems this should work with you now.
Click to expand...
Click to collapse
I just tried TWRP recovery and got "Failed (status read failed (Too many links))".
I also tried using fastboot to return to Android stock rom. That didn't work either.
I think I'm screwed. Man, I didn't even overclock the cpu. :crying:
Man_Utd said:
I just tried TWRP recovery and got "Failed (status read failed (Too many links))".
I also tried using fastboot to return to Android stock rom. That didn't work either.
I think I'm screwed. Man, I didn't even overclock the cpu. :crying:
Click to expand...
Click to collapse
Well, I searched for that error and found this thread. I checked it quickly and there are many suggestions up there to solve the issue like changing the cable, ports, and so on. So please take some time to read through it and try the various solutions so hopefully this error will be solved
I too have had issues with cables. Never that same error but I've had read and write errors. I've resorted to using a 3yr old Motorola Droid power cable because it seems to be built the best. I've also had success using different ports and computers.
Also instead of updating the drivers to the newest try deleting the device out if device manager and rebooting and then installing the device new. That has fixed a "hardware component ID" error I had
Sent from my Nexus 7 using Tapatalk HD
Related
I pulled my phone out of my pocket it and saw that it was on the HTC boot screen. It stayed like the for a while so i shut it down using Power, Volume UP&Down.
I tried to boot again but was freezing at the HTC boot screen.
I booted into recovery and it said it couldnt load /cach/x (command and log and last_log)
Ive tried everything from flashing RUU to new HBOOTS, nothing is working.
Now my laptop keeps saying a USB port is malfunctioning everytime i plug the phone in.
Im two seconds away from smashing this with a sledgehammer.
I was running Aeroevan's Unofficial CM10 Jelly Bean With the v12 Kernel w/ Video Drivers.
Have you tried the pg32img in bootloader?
Sent from my DROID SPYDER using Tapatalk 2
jamminjon82 said:
Have you tried the pg32img in bootloader?
Sent from my DROID SPYDER using Tapatalk 2
Click to expand...
Click to collapse
Yes, when i go to install it, it does a few things.
It p****s the zip
bypasses the bootload
and freezes at boot saying updating and at the bottom is says can not roll back hboot version.
Its been at this screen for about 45 minutes THIS TIME
May have to try one of the methods of bringing it back to stock. There is a good tutorial on rootzwiki. I'll post the link in a sec..
EDIT: Here you go. Follow everything to the T.
http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
Sent from my Incredible 2 using Tapatalk 2
dirtsky said:
May have to try one of the methods of bringing it back to stock. There is a good tutorial on rootzwiki. I'll post the link in a sec..
EDIT: Here you go. Follow everything to the T.
http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
The only issue now is I only have FastBoot Support but no ADB support. I have no idea why but my phone only shows up under fastboot devices and not adb devices. so i have no idea how to use that guide
The Inc 2 ports often go bad. Try wiggling and plugging it in not all the way. Also sometimes had to push on the cable and hold for it to recognize the USB.
________________________________
Easy as 3.1415926536
If your phone can be used via fastboot it should be able to via adb. Like CS said, It might be a bad micro-usb slot. I would try wiggling it to see if that helps. Being able to access fastboot means its not bricked, it just might be a hardware failure.
sjpritch25 said:
If your phone can be used via fastboot it should be able to via adb. Like CS said, It might be a bad micro-usb slot. I would try wiggling it to see if that helps. Being able to access fastboot means its not bricked, it just might be a hardware failure.
Click to expand...
Click to collapse
I did??
Sent from Kangdemnation
CondemnedSoul said:
I did??
Sent from Kangdemnation
Click to expand...
Click to collapse
What happens when you type
adb devices?
what about fastboot devices.
If you can do one you should be able to do the other, but i'm not sure how you have your adb folders setup. Its a weird error. Can you explain your setup some more.
sjpritch25 said:
What happens when you type
adb devices?
what about fastboot devices.
If you can do one you should be able to do the other, but i'm not sure how you have your adb folders setup. Its a weird error. Can you explain your setup some more.
Click to expand...
Click to collapse
When i type in Fastboot device my phone shows up, but when i type in adb devices it doesnt. i set up the android sdk and assorted tools the way i always have because i use them for development in eclipse, but ive never had a problem with adb before.
sjpritch25 said:
What happens when you type
adb devices?
what about fastboot devices.
If you can do one you should be able to do the other, but i'm not sure how you have your adb folders setup. Its a weird error. Can you explain your setup some more.
Click to expand...
Click to collapse
this is what it should look like.
CondemnedSoul said:
I did??
Sent from Kangdemnation
Click to expand...
Click to collapse
Lol I think he had just looked at your contact picture. They look very similar at a glance
If your phone isn't booting past HTC screen it won't usually show up as an adb device.
Are you s-off?
Have you tried the return to stock that I posted?
http://forum.xda-developers.com/showthread.php?t=1599767
This does not change hboot version so you shouldn't get that error but will put un-rooted stock and stock recovery back on your phone. Then you can install custom recovery, flash su bins and be ready to go again...... hopefully
CondemnedSoul said:
If your phone isn't booting past HTC screen it won't usually show up as an adb device.
Are you s-off?
Have you tried the return to stock that I posted?
http://forum.xda-developers.com/showthread.php?t=1599767
This does not change hboot version so you shouldn't get that error but will put un-rooted stock and stock recovery back on your phone. Then you can install custom recovery, flash su bins and be ready to go again...... hopefully
Click to expand...
Click to collapse
Everything i try keeps freezing in the bootloader screen when i go to install any RUU or image file or zip including that PG32IMG thing or whatever.
My phone recognizes it in fastboot but not adb.
I am S-Off. I rooted the phone the day i got it 6 months ago and have flashed a new rom weekly. never had a problem like this before.
dirtsky said:
May have to try one of the methods of bringing it back to stock. There is a good tutorial on rootzwiki. I'll post the link in a sec..
EDIT: Here you go. Follow everything to the T.
http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
The download links in this do not work or else id try that too.
Try it
Try putting a random rom on the Sd of the phone then try and get it to root ClockWork through the volume down method. Wipe and run the other Rom. try it ive been stuck before and it sounds something like this
flydoug9 said:
Try putting a random rom on the Sd of the phone then try and get it to root ClockWork through the volume down method. Wipe and run the other Rom. try it ive been stuck before and it sounds something like this
Click to expand...
Click to collapse
Yes i would try this except ClockWorkMod isnt working when i attempt to boot into it. It starts to load then freezes.
I'm having this very same issue. Turned the phone off Friday night, turned it on Saturday morning to the white HTC screen. Stock RUUs don't do anything.
Sent from my Ally using xda app-developers app
TheValk said:
I'm having this very same issue. Turned the phone off Friday night, turned it on Saturday morning to the white HTC screen. Stock RUUs don't do anything.
Sent from my Ally using xda app-developers app
Click to expand...
Click to collapse
Yeah i've been trying everything. When i install any RUU or anything it keeps getting hung up at recovery and i tried flashing that seperately and that isnt doing anything.
Have you tried doing anything in fast boot like wiping data and cache?
Sent from my Incredible 2 using xda premium
My phone was just downloading a file and now it won't boot past the green HTC logo white screen. The last rom I was using was one of mikroms. I have tried to restore from a backup as well as flashing a new from via recovery. I get an error during installing boot.img- I even get errors when recovery boots up. I posted images of my hbootand recovery. Any help would be greatly appreciated.
Use a newer recovery. I recommend 4EXT recovery touch. Also, you're probably gonna have to flash a new ROM. You also don't need to manually flash the boot.IMG since you're s-off.
Sent from my KangBang'd out vivow
tylerlawhon said:
Use a newer recovery. I recommend 4EXT recovery touch. Also, you're probably gonna have to flash a new ROM. You also don't need to manually flash the boot.IMG since you're s-off.
Sent from my KangBang'd out vivow
Click to expand...
Click to collapse
I already tried installing a new from, what I was saying is that error about installing boot.img happened when it was trying to install the from via recovery. For right now I'm just trying to get the phone to boot up. I don't think a different recovery will make that happen
scottyh73 said:
I already tried installing a new from, what I was saying is that error about installing boot.img happened when it was trying to install the from via recovery. For right now I'm just trying to get the phone to boot up. I don't think a different recovery will make that happen
Click to expand...
Click to collapse
Well considering yours is super outdated, it could be. Older recoveries may not work right all the time. Thus being why they released later versions.
Sent from my KangBang'd out vivow
Dude, even if you don't think a diffrent recovory will help just do it anyway. You can't break your phone anymore than it already is.
Sent from my HTC Incredible 2 using xda app-developers app
Had this happen a while back. Had to run a stock ruu, then reload recovery, then flash super user for root.
Sent from my ADR6350 using xda app-developers app
You're on an old radio, too. Probably the recovery is the culprit, though.
Sent from my vivow using xda app-developers app
Thanks for all of the suggestions guys. I'll try to flash a new recovery tonight and if that doesn't work I'll try updating radios. I'll post back with results. Cheers!
Well Im basically stuck. My computer will not recognize the inc. I have never synced this device up with this computer when it was up and running. Only with my rezound. Either way when the device is connected adb will not recognize the device as well as the computer will not recognie the usb device. Every file i try to push to it in bootloader i get error messages that device was not found. Tried fastboot flashing a new recovery as well as new radios but no luck. Ive also reinstalled htc sync, then removed. Recognizes my rezound no problem
if you have a micro->sd card adapter, place the recovery onto the root of it then go into CWM and install from sdcard, see if that works
JehC said:
if you have a micro->sd card adapter, place the recovery onto the root of it then go into CWM and install from sdcard, see if that works
Click to expand...
Click to collapse
Are you saying to install the new recovery zip, in recovery? I didn't think you could do that, and it didn't work. I've tried flashing new radios but it gets stuck on the very last part of the update and freezes until I take the battery out.
scottyh73 said:
Well Im basically stuck. My computer will not recognize the inc. I have never synced this device up with this computer when it was up and running. Only with my rezound. Either way when the device is connected adb will not recognize the device as well as the computer will not recognie the usb device. Every file i try to push to it in bootloader i get error messages that device was not found. Tried fastboot flashing a new recovery as well as new radios but no luck. Ive also reinstalled htc sync, then removed. Recognizes my rezound no problem
Click to expand...
Click to collapse
It should recognize it in recovery, did you try that it just bootloader
Sent from my Incredible 2 using xda app-developers app
jeremytn86 said:
It should recognize it in recovery, did you try that it just bootloader
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
I only tried in the boot loader. So you're saying connect it to the computer while in recovery, and then run the fast boot flash recovery command?
scottyh73 said:
I only tried in the boot loader. So you're saying connect it to the computer while in recovery, and then run the fast boot flash recovery command?
Click to expand...
Click to collapse
Install drivers, turn phone on by holding down volume plus power, then go into recovery, then plug phone to PC. Should be recognized now.
Sent from my Incredible 2 using xda app-developers app
---------- Post added at 04:04 PM ---------- Previous post was at 04:03 PM ----------
Type adb devices to check afterwards
Sent from my Incredible 2 using xda app-developers app
jeremytn86 said:
Install drivers, turn phone on by holding down volume plus power, then go into recovery, then plug phone to PC. Should be recognized now.
Sent from my Incredible 2 using xda app-developers app
---------- Post added at 04:04 PM ---------- Previous post was at 04:03 PM ----------
Type adb devices to check afterwards
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
The computer does recognize the device when i go into recovery. Then when i run the flash recovery command through adb it says waiting for device. It will not show sending recovery though until i go into bootloader on the device. Then adb shows "okay" and "writing recovery....." It will show this forever until i unplug the device.
Try adb wait for device after that
Sent from my Incredible 2 using xda app-developers app
jeremytn86 said:
Try adb wait for device after that
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
not quite sure exactly what you mean by that...just keep waiting while it says waiting for device while in recovery? I waited about 20 minutes..then tried waiting another 30 minutes while it was saying "writing recovery" while in bootloader
So im pretty sure the device is just done for at this point. I decided to just try to flash the device back to stock with this http://forum.xda-developers.com/showthread.php?t=1599767.. This also just got stuck on the recovery section. Should i just give up? lol
Today my Gnex randomly rebooted, then got stuck rebooting. it now starts gets all the way to the home screen then reboots, then the cycle starts over. I am rooted runny shiney rom. nothing new installed recently and as stated before the phone was running normal the rebooted out of the the blue.
I have cleared cache, davik and done factory wipe, all to no avail.
the text on bottom of my bootloader reads:
Product name-tuna
variant- toro 32gb
hw version-10
bootloader version primemd04
baseband version-i515.fk02 cdma-unknown
carrier info-none
i cant flash the factory image because the phone doesn't stay powered on long enough to stay connected to the computer. apparently when i re flashed and root i forgot to make a back up so i can not restore that way either.
You could try pulling battery put back in and hold volume buttons and power to get into fastboot mode and flash factory image. Maybe you already tried this but maybe not so thought I'd throw my thoughts your way.
Sent from my Galaxy Nexus using xda app-developers app
tshelby73 said:
You could try pulling battery put back in and hold volume buttons and power to get into fastboot mode and flash factory image. Maybe you already tried this but maybe not so thought I'd throw my thoughts your way.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I have tried that but I cant get the factory image save to my phone to flash it. Now is the only time i have missed removable memory
jj69chev said:
I have tried that but I cant get the factory image save to my phone to flash it. Now is the only time i have missed removable memory
Click to expand...
Click to collapse
the phone reboot itself even when it is on bootloader mode? thats really rarely if not impossible
jj69chev said:
I have tried that but I cant get the factory image save to my phone to flash it. Now is the only time i have missed removable memory
Click to expand...
Click to collapse
So you neef help flashing the Factory image? Pm me if you do. I will help
Sent from my Galaxy Nexus using XDA Premium HD app
jj69chev said:
I have tried that but I cant get the factory image save to my phone to flash it. Now is the only time i have missed removable memory
Click to expand...
Click to collapse
You don't put image on phone you flash it using fastboot command from computer.
If you don't know how get with previous poster.
Sent from my Galaxy Nexus using xda app-developers app
andQlimax said:
the phone reboot itself even when it is on bootloader mode? thats really rarely if not impossible
Click to expand...
Click to collapse
No it doesnt reboot when in recovery, but i dont have the factory image save on the device.
tshelby73 said:
You don't put image on phone you flash it using fastboot command from computer.
If you don't know how get with previous poster.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Fastboot gives me the device not found error, I will get with previous poster as well
jj69chev said:
Fastboot gives me the device not found error, I will get with previous poster as well
Click to expand...
Click to collapse
You might not have the right drivers. Have you used fastboot before?
Sent from my Galaxy Nexus using xda app-developers app
tshelby73 said:
You might not have the right drivers. Have you used fastboot before?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I Have the correct drivers, and have used fast boot before. i think i get the error because when i factory reset it, that turns off the debugging mode.
jj69chev said:
I Have the correct drivers, and have used fast boot before. i think i get the error because when i factory reset it, that turns off the debugging mode.
Click to expand...
Click to collapse
Debugging mode is only important when you are trying to use adb while booted into Android. In the bootloader, debugging being on or off doesn't matter. It also doesn't matter in recovery either.
Something is wrong somewhere, drivers are usually the best place to start as it is probably the most common reason why the device doesn't communicate with fastboot. Other things to try are different USB cables and USB ports.
jj69chev said:
I Have the correct drivers, and have used fast boot before. i think i get the error because when i factory reset it, that turns off the debugging mode.
Click to expand...
Click to collapse
Well looks like you know what your doing so looks like you have a major issue beyond my skill level. Sorry i couldn't help. Never tried it but Odin may be a thought. If you can get into recovery you could side load using adb also.
Sent from my Galaxy Nexus using xda app-developers app
cupfulloflol said:
Debugging mode is only important when you are trying to use adb while booted into Android. In the bootloader, debugging being on or off doesn't matter. It also doesn't matter in recovery either.
Something is wrong somewhere, drivers are usually the best place to start as it is probably the most common reason why the device doesn't communicate with fastboot. Other things to try are different USB cables and USB ports.
Click to expand...
Click to collapse
When Fast booting i can not flash radio-cdma... i get an "unknown error" does this mean my cdma radio is shot?
jj69chev said:
When Fast booting i can not flash radio-cdma... i get an "unknown error" does this mean my cdma radio is shot?
Click to expand...
Click to collapse
Have you tried the flash-all it seems to do some formatting that may help but I think it does that later after the radios. Warning it will wipe your phone including sdcard.
Sent from my Galaxy Nexus using xda app-developers app
Have you tried connecting it into download mode, and then flash an odin image through odin? with that method you wont need to actually put the image onto the device but rather odin just copies it over for you while flashing the phone at the same time.
Same issue
My phone started randomly rebooting, and wont stop, it can't get past the lock screen without crashing on me. However i went into recovery, wiped everything, and flashed back to the stock rom ( i was running the shiny 4.3 rom) and the issue is still persistng, anyone know what can be done, or is something possibly wrong with the hardware?
Fahull said:
My phone started randomly rebooting, and wont stop, it can't get past the lock screen without crashing on me. However i went into recovery, wiped everything, and flashed back to the stock rom ( i was running the shiny 4.3 rom) and the issue is still persistng, anyone know what can be done, or is something possibly wrong with the hardware?
Click to expand...
Click to collapse
You found this thread but didn't read it? Seriously? This isn't 1000+ pages.... As suggested: use fastboot to flash the Factory image with the flash-all.bat.
Sent from my Galaxy Nexus using XDA Premium HD app
Fahull said:
My phone started randomly rebooting, and wont stop, it can't get past the lock screen without crashing on me. However i went into recovery, wiped everything, and flashed back to the stock rom ( i was running the shiny 4.3 rom) and the issue is still persistng, anyone know what can be done, or is something possibly wrong with the hardware?
Click to expand...
Click to collapse
I was also running shiney 4.3. I had to get a new phone because nothing I tried helped. I'm no expert but it seems to me that the CDMA radio is toast in mine/
so guys i had just flashed beanstalker and was having a good time liking it suddenly goo.im an app said i had a rom update so i thought cool ill just flash the update well i flashed the update and now im bootlooping fastboot and recovery dont work ive used omap flash it went through without an error but didnt help. nexus toolkit (wugs) didnt help and samsung galaxy nexus toolkit recognized it as adb with a serial but said offline beside it. its showing up as samsung mobile mtp device with an error code of 10 cannot start in device manager also shows up as android adb interface without one. ive tried everything i could think of any help would be realllly appreciated as ive spent some hours now trying to find a way to fix this device
When you say fastboot and recovery don't work, does that mean you can't boot into them? Or that when you tried to use fastboot to flash an image an error occurred?
Have you tried OMAP flash?
cupfulloflol said:
When you say fastboot and recovery don't work, does that mean you can't boot into them? Or that when you tried to use fastboot to flash an image an error occurred?
Have you tried OMAP flash?
Click to expand...
Click to collapse
yeah i cannot boot in them i tried omap flash i mentioned it in op it went off withhout a problem but still bootlooping
gears177 said:
yeah i cannot boot in them i tried omap flash i mentioned it in op it went off withhout a problem but still bootlooping
Click to expand...
Click to collapse
If OMAP flash can't get you back into something that works, then the title of this thread is probably correct.
cupfulloflol said:
If OMAP flash can't get you back into something that works, then the title of this thread is probably correct.
Click to expand...
Click to collapse
damn thats unfortunate i guess its too ebay now to sell it for parts
Take your battery out. Then put it back in and hold volume up and down and power. That should put you into fastboot mode. I am not entirely convinced that your fastboot is completely fried. Its really hard to do on this phone. Especially during a ROM update.
Do you know how to do fastboot without the toolkit?
Sent from my Nexus 7 using XDA Premium 4 mobile app
blackhand1001 said:
Take your battery out. Then put it back in and hold volume up and down and power. That should put you into fastboot mode. I am not entirely convinced that your fastboot is completely fried. Its really hard to do on this phone. Especially during a ROM update.
Do you know how to do fastboot without the toolkit?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yeah volme up right plus power adb is working but it says my phone is offline so thats a no go and ill try with the battery out and see if that works if not im going to make a jig monday and see if it helps im not sure how to push files or anything without the toolkit
nope didnt help is their anyway to delete everything except fast-boot or recovery or perhaps fix adb?
gears177 said:
yeah volme up right plus power adb is working but it says my phone is offline so thats a no go and ill try with the battery out and see if that works if not im going to make a jig monday and see if it helps im not sure how to push files or anything without the toolkit
nope didnt help is their anyway to delete everything except fast-boot or recovery or perhaps fix adb?
Click to expand...
Click to collapse
so im guessing the commands for the fastboot and recovery were messed up as i know its still there i could boot to them before the rom update it must be its not recognizing the volume keys when their being pressed
Can you boot into odin mode?
Sent from my maguro using xda app-developers app
gears177 said:
yeah volme up right plus power adb
Click to expand...
Click to collapse
thats not fastboot.
vol up and down and power
razi914 said:
Can you boot into odin mode?
Sent from my maguro using xda app-developers app
Click to expand...
Click to collapse
how would i get into odin mode? im not sure but most likely i cannot if it involves a button combo
I'll prequel all of this by stating that I am a complete noob to the Android. After reading the stickies to this forum (correct me if I'm wrong), flashing the device sounds promising, but I don't know if that solution is even applicable to my problem. I'm worried I've completely bricked my HTC One X. Any help would be greatly appreciated and here's everything I can tell you about the situation.
The phone is an HTC One X Endeavor. When turned on, it shows the boot screen (HTC-quietly brilliant). Holding the power and the down volume buttons reveals the bootloader menu. The phone is unlocked and the problem occurred after an attempt to root the device. When I plug it into my computer I hear the sound that signals I've connected a new device, but under My Computer it brings up a CD drive, which can't be browsed.
If I pull up the bootloader menu while it is plugged into my laptop, this text comes up on the screen briefly:
checking sd card update
sd checking
failed to open usb master mode
loading pj46img.zip
failed to open usb master mode
please plug off usb
After running through that it just goes to HBOOT. I can still access FASTBOOT and all that, but nothing seems to work. Is there any way to revive my HTC?
Sorry for the noobishness, I've been on an iPhone for the last few years and have only had my HTC for a couple of weeks (love, love Android and never looking back). So I'm really hoping there's a way to recovery my beloved HTC.
se7envirtues said:
I'll prequel all of this by stating that I am a complete noob to the Android. After reading the stickies to this forum (correct me if I'm wrong), flashing the device sounds promising, but I don't know if that solution is even applicable to my problem. I'm worried I've completely bricked my HTC One X. Any help would be greatly appreciated and here's everything I can tell you about the situation.
The phone is an HTC One X Endeavor. When turned on, it shows the boot screen (HTC-quietly brilliant). Holding the power and the down volume buttons reveals the bootloader menu. The phone is unlocked and the problem occurred after an attempt to root the device. When I plug it into my computer I hear the sound that signals I've connected a new device, but under My Computer it brings up a CD drive, which can't be browsed.
If I pull up the bootloader menu while it is plugged into my laptop, this text comes up on the screen briefly:
checking sd card update
sd checking
failed to open usb master mode
loading pj46img.zip
failed to open usb master mode
please plug off usb
After running through that it just goes to HBOOT. I can still access FASTBOOT and all that, but nothing seems to work. Is there any way to revive my HTC?
Sorry for the noobishness, I've been on an iPhone for the last few years and have only had my HTC for a couple of weeks (love, love Android and never looking back). So I'm really hoping there's a way to recovery my beloved HTC.
Click to expand...
Click to collapse
you obviously didn't read enough!
the usb master mode thing is because you have the cable plugged in and nothing to worry about.
follow the steps here, omitting what you have already achieved>>>>>http://forum.xda-developers.com/showthread.php?t=2069904
nogotaclue said:
you obviously didn't read enough!
the usb master mode thing is because you have the cable plugged in and nothing to worry about.
follow the steps here, omitting what you have already achieved>>>>>http://forum.xda-developers.com/showthread.php?t=2069904
Click to expand...
Click to collapse
Always the case, eh? Thanks for pointing me in the right direction, I'll give this a try and come back with the (hopefully successful) results.
When I try to install the HTCDriver.exe nothing happens when I click on the .exe and I have tried this on two separate laptops, one on Windows XP and the other running Windows 7. I also sought out and tried installing HTCDriver_4.2.0.001.exe to the same results. When I click on it, the hourglass appears for a moment then disappears. I've tried running both as Administrator and still nothing. Any suggestions?
Install htc sync instead from the htc site then continue to the next steps
Sent from my HTC One X using XDA Premium 4 mobile app
nogotaclue said:
Install htc sync instead from the htc site then continue to the next steps
Sent from my HTC One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks! I've done this. HTC Sync Manager was already installed so I tried uninstalling it and reinstalling it. This solved the problem. I was able to flash over TWRP and now I am on the screen that lists Install, Backup, Wipe, Restore, etc. BUT my touch screen isn't working and I can't select any of the options. Also tried the volume buttons on the off chance, but that doesn't work either. Grr! Seems to be one problem after another.
~edit~ I tried flashing clockwork over and it says that it can't load /Recoveries/CWM.img and I also should have mentioned sooner that the three buttons at the bottom of my screen do not work. Hoping this doesn't effect the process.
Try flashing philz touch recovery
Sent from my HTC One X using xda app-developers app
Stefan0vic said:
Try flashing philz touch recovery
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I've flashed Philz Touch Recovery using this: http://forum.xda-developers.com/showthread.php?t=1634786
Now when I boot my phone it goes to Philz Touch Recovery. I made a back up just in case. I tried recovering and it just boots back to Philz after turning it off and back on so I'm assuming I'm missing a step here. Using Automated Fastboot I selected "install boot.img" to flash over Philz and then I installed CWM also using the same program. I can access CWM by launching RECOVERY in HBOOT, but uh I am kind of at a loss for what to do next. I think the next step would be to get a stock rom and flash that over, but before I do that I would like to be certain it isn't going to fudge up the phone even more.
Also, thank you all for your assistance and patience! :victory:
~edit~ I was able to install SuperSU.zip if that makes any difference, but again when I turn on the phone it goes straight to Philz and I can access CWM in recovery.
Should I Wipe Data/Factory Reset?
Have you flashed a rom ?
Sent from my HTC One X using XDA Premium 4 mobile app
nogotaclue said:
Have you flashed a rom ?
Sent from my HTC One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I flashed over Philz Touch Recovery and replaced my boot.img. Then installed CWM so basically I am booting up a recovery and there's a recovery in recovery... Yeah. Brilliant thinking (not).
You only have one recovery, when you flash a recovery it replaces the old one automatically. Follow the link and download the latest Odexed stock Rom and boot.img>>>>>http://forum.xda-developers.com/showthread.php?t=1546970
reflash philz recovery then mount usb storage from recovery and copy over the stock Rom you downloaded from the link above.
Go into fastboot and flash the boot.img you just downloaded from the link then back to recovery and install the rom
Sent from my HTC One X using XDA Premium 4 mobile app
nogotaclue said:
You only have one recovery, when you flash a recovery it replaces the old one automatically. Follow the link and download the latest Odexed stock Rom and boot.img>>>>>http://forum.xda-developers.com/showthread.php?t=1546970
reflash philz recovery then mount usb storage from recovery and copy over the stock Rom you downloaded from the link above.
Go into fastboot and flash the boot.img you just downloaded from the link then back to recovery and install the rom
Sent from my HTC One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Could I do the same thing with the ROM found here: http://forum.xda-developers.com/showthread.php?p=23993171? Thanks for the help!
~edit~ VIOLA! Flashing stock fixed the phone. Thank you so much for all of your support and patience. Cheers mate!