Major problems! Phone completely bricked nothing is fixing! Please help - Verizon Droid Incredible 2

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

Related

Trying to recovery partially bricked phone

Okay, so a friend asks me to fix her Dinc... here's the story.
When I first got the dinc, it only powered up into FASTBOOT (HBOOT 0.92, Radio 2.15). The volume and power buttons don't work. She said it crashed when she FC a program to get more memory.
I tried to flash the phone using pb31img.zip on a newly formatted (fat32) sdcard. It scans the card and errors with older version.
Next I try to flash with RUU. That was successful and I can boot into the phone... in safe mode. In addition, if I shut down the phone and power up again, I get stuck in FASTBOOT and have to redo the RUU.
Okay, I figured with the phone booting into Froyo, all is not lost. I tried to use unrevoked to get root and poke around. That failed with error asking if firmware is too new.
I try to install z4root... that doesn't work either since safe mode seems to mean only default system programs work (I can install, but can't run). Probably why unrevoked failed also.
I'm starting to think it is a hardware issue since the RUU should have fixed everything.
Any ideas???
Thanks.
Go to this website and follow the steps to exit safe mode and see if that solves your problem.... let me know?
http://www.myvusers.com/forums/htc-...e-safe-mode-htc-droid-incredible-adr6300.html
Sent from my Incredible using XDA App
When it takes you back to hboot and it loads the ruu and it asks to update say no and it should ask if you want to reboot.... if it don't highlight fastboot tap the power button and it will take you to a menu scroll down till you hit reboot device and tap power button and it should reboot....
Sent from my Incredible using XDA App
Shuts down and then goes back into fastboot.
newtoroot said:
Go to this website and follow the steps to exit safe mode and see if that solves your problem.... let me know?
link deleted
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Woz2000 said:
Shuts down and then goes back into fastboot.
Click to expand...
Click to collapse
Did you try rebooting from fastboot instead of using the ruu again
Sent from my Incredible using XDA App
When it boots and goes into fastboot, none of the buttons are responsive. I have to pull battery.
newtoroot said:
When it takes you back to hboot and it loads the ruu and it asks to update say no and it should ask if you want to reboot.... if it don't highlight fastboot tap the power button and it will take you to a menu scroll down till you hit reboot device and tap power button and it should reboot....
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
As I mentioned, none of the buttons in fastboot seems to work, so I can't reboot, just a battery pull. Interestingly, when I have the pb31img there, it scans and tells me its an older version, but then the buttons work... reboots back into fastboot.
I'm thinking of trying the revert to 2.1 and go from there... is it safe to flash over the latest Froyo RUU with 2.15 radio with the following?
RUU_IncredibleC_Verizon_WWE_1.22.605.2_Radio_1.00.03.04.06_hboot_0.79_release_161494_NoDriver_0514.exe
Thanks for all the help so far!
Woz2000 said:
As I mentioned, none of the buttons in fastboot seems to work, so I can't reboot, just a battery pull. Interestingly, when I have the pb31img there, it scans and tells me its an older version, but then the buttons work... reboots back into fastboot.
I'm thinking of trying the revert to 2.1 and go from there... is it safe to flash over the latest Froyo RUU with 2.15 radio with the following?
RUU_IncredibleC_Verizon_WWE_1.22.605.2_Radio_1.00.03.04.06_hboot_0.79_release_161494_NoDriver_0514.exe
Thanks for all the help so far!
Click to expand...
Click to collapse
Try this ruu first this is one I had to use once so I know it works..... rename it PB31IMG.zip like always ill check with you in a bit.... if that don't help I know a another guy that might be more help....
If I helped at all hit the thanks button
http://db.tt/8YWjgVF
Sent from my Incredible using XDA App
Downloading now... but I'll probably hit the sack soon. Not getting enough sleep is not good on the day job!!!
Thanks again.
newtoroot said:
Try this ruu first this is one I had to use once so I know it works..... rename it PB31IMG.zip like always ill check with you in a bit.... if that don't help I know a another guy that might be more help....
If I helped at all hit the thanks button
link deleted (I can't post with links)
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Woz2000 said:
Downloading now... but I'll probably hit the sack soon. Not getting enough sleep is not good on the day job!!!
Thanks again.
Click to expand...
Click to collapse
No prob
Sent from my Incredible using XDA App
Can't get the fastboot to recognize any pb31img.zip file now... it only worked when I first got the dead phone. Now that I have flashed with RUU, the fastboot won't recognize the pb31img file.
I'm going to have to try to manually flash or root using adb... trying to get all the files now.
newtoroot said:
Try this ruu first this is one I had to use once so I know it works..... rename it PB31IMG.zip like always ill check with you in a bit.... if that don't help I know a another guy that might be more help....
If I helped at all hit the thanks button
http://db.tt/8YWjgVF
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Does it still say s-off at the top
Sent from my Incredible using XDA App
It's always been s-on... could never get root, so couldn't get s-off, otherwise I would try flashing recovery and custom ROMS or poking around with Titanium and rebuilding apps from another dinc.
newtoroot said:
Does it still say s-off at the top
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Woz2000 said:
It's always been s-on... could never get root, so couldn't get s-off, otherwise I would try flashing recovery and custom ROMS or poking around with Titanium and rebuilding apps from another dinc.
Click to expand...
Click to collapse
I say your best bet is to try and get root and s-off..... have you tried asking for help from Doug piston in incredible forums he has a lot of knowledge on these types of problems its alittle over my head sorry I couldn't be any more help
Sent from my Incredible using XDA App
I'll give him a try later after my last attempt at manually rooting through adb.
Thanks.
newtoroot said:
I say your best bet is to try and get root and s-off..... have you tried asking for help from Doug piston in incredible forums he has a lot of knowledge on these types of problems its alittle over my head sorry I couldn't be any more help
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Any luck Woz?
Yes, Doug gave me a bunch of roms to flash. Nothing worked. The last step we did before I took a break was to get into recovery using adb. Then I wiped cache and data. That didn't seem to work. Flashed another rom using recovery. Nada.
I put the phone down for a few hours. Then I decided to crack it open to see if it was a refurb (cheap label makes me suspicious). Nothing unusual inside, I put it back together and powered on... the thing booted normally... everything worked.
Doug suspects it was the data/cache wipe, I don't know. I think it was the bug that got let out when I cracked it open.
Woz2000 said:
Yes, Doug gave me a bunch of roms to flash. Nothing worked. The last step we did before I took a break was to get into recovery using adb. Then I wiped cache and data. That didn't seem to work. Flashed another rom using recovery. Nada.
I put the phone down for a few hours. Then I decided to crack it open to see if it was a refurb (cheap label makes me suspicious). Nothing unusual inside, I put it back together and powered on... the thing booted normally... everything worked.
Doug suspects it was the data/cache wipe, I don't know. I think it was the bug that got let out when I cracked it open.
Click to expand...
Click to collapse
Hey bro just noticed that you took my advice and asked Doug for help glad your up and going......
Sent from my Incredible using XDA App

Bricked or not bricked?

I had an issue with my phone a couple of weeks ago where I'm only able to the bootloader screen and the fastboot screen. Fortunately, I got a replacement EVO 3 days later but I'm still trying to get my old phone up and running. But after trying everything I can find, still nothing.
So my question is, when do I say that the phone is officially bricked?
Sent from my PC36100 using Tapatalk
If you can get to the bootloader screen, then you be able to flash an image to get you phone working again.
Sent from my Decked Out HTC EVO with Tapatalk!
dwelder said:
If you can get to the bootloader screen, then you be able to flash an image to get you phone working again.
Sent from my Decked Out HTC EVO with Tapatalk!
Click to expand...
Click to collapse
Believe me, I've tried everything, from using amon ra PC36IMG.zip in the bootloader. It updates successfully then still no recovery.
I've tried the ruu via bootloader, it updates successfully. It still bootloops continually.
I ran Football's recent 4.54 ruu in fastboot successfully and still nothing.
Everything I try, it continues to bootloop.
Sent from my PC36100 using Tapatalk
Were you using CM7 before your phone started bootlooping?
Concordium said:
Were you using CM7 before your phone started bootlooping?
Click to expand...
Click to collapse
10/14 miui with tiamat 4.1 sbc.
Sent from my PC36100 using Tapatalk
andygu3 said:
10/14 miui with tiamat 4.1 sbc.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Well CM7 is the ROM typically being run when phones enter the bootloop of death. However, I've heard that there have been a couple of MIUI ROMs that have entered the bootloop of death as well. If you've flash a recovery and still cant enter it and tried to fully unroot then you might have to take it to Sprint. I'd make sure that you're fully unrooted before doing so. I would also recommend removing your SD card so that they cant try to deny you based on rooting the phone. Just a precaution.
andygu3 said:
Believe me, I've tried everything, from using amon ra PC36IMG.zip in the bootloader. It updates successfully then still no recovery.
I've tried the ruu via bootloader, it updates successfully. It still bootloops continually.
I ran Football's recent 4.54 ruu in fastboot successfully and still nothing.
Everything I try, it continues to bootloop.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Have you tried flashing the images via fastboot?
Concordium said:
Well CM7 is the ROM typically being run when phones enter the bootloop of death. However, I've heard that there have been a couple of MIUI ROMs that have entered the bootloop of death as well. If you've flash a recovery and still cant enter it and tried to fully unroot then you might have to take it to Sprint. I'd make sure that you're fully unrooted before doing so. I would also recommend removing your SD card so that they cant try to deny you based on rooting the phone. Just a precaution.
Click to expand...
Click to collapse
Fortunately, I already got a new phone but the reason I didn't take it into Sprint was because it still was S-off. Since I can't get to recovery, how would I get s-on?
And now that I ran stock ruu's, is it a possibility that the PC36IMG.zip's won't be recognized anymore?
I'd love to get this phone running again and let my 7 year play some games on it but I'm afraid I may be sol!!
Sent from my PC36100 using Tapatalk
teh roxxorz said:
Have you tried flashing the images via fastboot?
Click to expand...
Click to collapse
Please elaborate! Not sure what to flash in fastboot?
Sent from my PC36100 using Tapatalk
andygu3 said:
Please elaborate! Not sure what to flash in fastboot?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Well you said you tried flashing via PC36IMG, and it 'worked' but it didn't stick, i.e it didn't 'work'. What you can do is extract the boot.img from the rom / ruu, place it in your adb tools folder. Then boot the phone to the bootloader, select fastboot, connect to your pc via usb cable, open up command prompt, navigate to you adb tools folder and type:
fastboot flash boot boot.img
fastboot reboot
That will flash the boot image to the correct partition, then reboot the phone, and see if it boots up.
andygu3 said:
Fortunately, I already got a new phone but the reason I didn't take it into Sprint was because it still was S-off. Since I can't get to recovery, how would I get s-on?
And now that I ran stock ruu's, is it a possibility that the PC36IMG.zip's won't be recognized anymore?
I'd love to get this phone running again and let my 7 year play some games on it but I'm afraid I may be sol!!
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Here you go
http://forum.xda-developers.com/showpost.php?p=18399552&postcount=2
teh roxxorz said:
Well you said you tried flashing via PC36IMG, and it 'worked' but it didn't stick, i.e it didn't 'work'. What you can do is extract the boot.img from the rom / ruu, place it in your adb tools folder. Then boot the phone to the bootloader, select fastboot, connect to your pc via usb cable, open up command prompt, navigate to you adb tools folder and type:
fastboot flash boot boot.img
fastboot reboot
That will flash the boot image to the correct partition, then reboot the phone, and see if it boots up.
Click to expand...
Click to collapse
Thanks for the info! I will give this a go.
I keep reading that the NV got corrupted some how, is there any way to correct this or flash something in fastboot?
Again thanks for your input, much appreciated!
Sent from my PC36100 using Tapatalk
andygu3 said:
Thanks for the info! I will give this a go.
I keep reading that the NV got corrupted some how, is there any way to correct this or flash something in fastboot?
Again thanks for your input, much appreciated!
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
No problem.
And if the NV is corrupted, its toast. It was a flaw with the evo when you bought it, and now its decide to tap out. At that point you'd have to take it to sprint, as the NV is part of flash memory and its locked.
Concordium said:
Here you go
http://forum.xda-developers.com/showpost.php?p=18399552&postcount=2
Click to expand...
Click to collapse
Thanks for this, hopefully if I can't get the boot.img working from ruu, I will do this!
Sent from my PC36100 using Tapatalk
andygu3 said:
Thanks for this, hopefully if I can't get the boot.img working from ruu, I will do this!
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Oh crap I forgot you were the one having the issue with the boot.img. If you can't get that to work then the post I gave you will most likely not work either. It's worth a try....but I doubt it.
teh roxxorz said:
No problem.
And if the NV is corrupted, its toast. It was a flaw with the evo when you bought it, and now its decide to tap out. At that point you'd have to take it to sprint, as the NV is part of flash memory and its locked.
Click to expand...
Click to collapse
Well sh**, that's a downer! If this is the case, I'm definitely sol! But hopefully I can get something out of the phone but I seriously doubt it!
Thanks guys for your input, again much appreciated. I will report back if I have any breakthrough!!
Sent from my PC36100 using Tapatalk
Im having the same issue
bootloop and the phone was using CM7. I was able to get to boot loader menu but can not get to recovery.
Tried to add recovery image no dice...now the phone will only charge and not boot
teh roxxorz said:
Well you said you tried flashing via PC36IMG, and it 'worked' but it didn't stick, i.e it didn't 'work'. What you can do is extract the boot.img from the rom / ruu, place it in your adb tools folder. Then boot the phone to the bootloader, select fastboot, connect to your pc via usb cable, open up command prompt, navigate to you adb tools folder and type:
fastboot flash boot boot.img
fastboot reboot
That will flash the boot image to the correct partition, then reboot the phone, and see if it boots up.
Click to expand...
Click to collapse
No luck!
I know someone posted the EVO Brick_fix, I believe cutthroat but since no PC36IMG.ZIP is being recognized on my sdcard. I may officially say my phone is toast.
Any other suggestions are welcome!
Sent from my PC36100 using Tapatalk
Is this normal? I can run any stock ruu and my hboot changes! I was on 2.16 but I ran the froyo ruu and now I'm back to 2.10
Any thoughts?
Sent from my PC36100 using Tapatalk
andygu3 said:
Is this normal? I can run any stock ruu and my hboot changes! I was on 2.16 but I ran the froyo ruu and now I'm back to 2.10
Any thoughts?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Did you unbrick your EVO
I tried to use unbrick method and now phone will not boot at all
It just stays at black screen and vibrates once after pressing the power button

bricked?

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

[Q] Bricked GNex?

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

Gnex constant reboot

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/

Categories

Resources