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
Related
I'm stuck on the white boot screen after trying to flash Miui onto an otherwise functioning incredible 2. I can however access recovery,hboot, fast boot,and all that other good stuff. I unlocked the bootloader via the HTC dev website, which I now hear was a total mistake. To further screw me over, the universe decided that the phone was no longer fit to be detected by my cmd, so I can't use adb or fast boot either. I'm downloading the ruu to see if I can flash it from the sd card, but have no idea if it will work. Do I need to have the bootloader locked? Also, I don't have s-off. Any help is much appreciated, and thanks in advance.
Sent from my ADR6425LVW using XDA
OK. Look here:http://forum.xda-developers.com/showthread.php?t=1435228
you will have to flash the boot.img, using adb now, with unlocked bootloader.
if you are going to flash a RUU you will need to relock bootloader
OK. Look here:http://forum.xda-developers.com/showthread.php?t=1435228
you will have to flash the boot.img, using adb now, with unlocked bootloader.
if you are going to flash a RUU you will need to relock bootloader
Click to expand...
Click to collapse
He said he can't use fastboot or adb. Can you get into recovery? Try just wiping everything.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Giving it a shot with the ruu,. But yeah I can't get in to adb. Thanks for the responses though. If I try flashing boot.img, where do i get boot.img?
Sent from my ADR6425LVW using XDA
unzip the rom file and look for boot image and put the boot image in sdk tools folder
its all in that link i gave you
VVackDavid said:
I'm stuck on the white boot screen after trying to flash Miui onto an otherwise functioning incredible 2. I can however access recovery,hboot, fast boot,and all that other good stuff. I unlocked the bootloader via the HTC dev website, which I now hear was a total mistake. To further screw me over, the universe decided that the phone was no longer fit to be detected by my cmd, so I can't use adb or fast boot either. I'm downloading the ruu to see if I can flash it from the sd card, but have no idea if it will work. Do I need to have the bootloader locked? Also, I don't have s-off. Any help is much appreciated, and thanks in advance.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
I've been there with my phone. I though I had bricked it. I was able to get it back. Hopefully you have figured out how by now. I found you can only run a stock kernel with the unlocked bootloader. There are only a few rooted roms you can run with the htc unlock. You can run one of them or obtain s-off. To do that you need to relock the boot loader and follow the instructions to down grade the bootloader. Then you can use the root instructions.
Sometimes I think that HTC tricks people into thinking that there phone has been rooted, and that they can flash ROMs. With the unlock just to teach them not to hack there phones. You are definitely not the only person who has fallen into this hole.
Sent from my Incredible 2 using XDA
You can run ROMs with custom kernels just fine, you just need to extract the boot.img and flash it separately through fastboot.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
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
I received an Incredible 2,
*****RELOCKED*******
VIVO_W XB SHIP S-ON RL
HBOOT -0.98.0000
Radio- 1.09.01.0312
eMMC-boot
Jul 18 2011
All that it does is get stuck at the HTC screen.
Things that I have tried.
New Ruus
PG32IMG
The phone is recognized in fastboot,
ADB does not recognize the phone.
I have been going through the forum, and websites for the last 4 hours.
Factory Reset reboots the phone and gives me a security warning.
Recovery does the same.
I also get the USB Not recognized error once the phone comes on. I have installed the HTC drivers, I have also installed HTC Sync and have removed it.
Am I stressing and overlooking something simple? Or, do I need to take this phone out back and lay it to rest.
Thank you in advance
Crush
I don't own this phone but how did this happen? I'm assuming your rooted and unlocked if you got s recovery and stuff. And if your recovery works.. just Mount your SD card and transfer a ROM from your PC and flash one.. make sure you flash the kernel too. That or run the ruu
Sent from my HTC One V using xda app-developers app
XxlemonxX said:
I don't own this phone but how did this happen? I'm assuming your rooted and unlocked if you got s recovery and stuff. And if your recovery works.. just Mount your SD card and transfer a ROM from your PC and flash one.. make sure you flash the kernel too. That or run the ruu
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Thank for replying xxLemonxx
I was given this phone because because it is stuck in the bootloop. Phones come with their own recovery, this isn't a custom recovery. I have tried to run ruus, the error I get is Main version is older. I have also downloaded official stock roms with no luck.
When I hit recovery, the phone reboots back to the bootloader, the recovery never comes up.
CrushRush said:
Thank for replying xxLemonxx
I was given this phone because because it is stuck in the bootloop. Phones come with their own recovery, this isn't a custom recovery. I have tried to run ruus, the error I get is Main version is older. I have also downloaded official stock roms with no luck.
When I hit recovery, the phone reboots back to the bootloader, the recovery never comes up.
Click to expand...
Click to collapse
Ohh so someone messed it up and just gave it to you for free? Or for you to repair? Either way I don't follow the droid inc2 but maybe im sure its rooted if its in a boot loop so try going into fast boot and go into cmd prompt and try to install a recovery. Look up how to install a recovery through CmD Prompt on the Pc. On my phone can't explain all of it. And then just transfer over a ROM probably cm9 and follow the instructions
Unless you want to go back to stock? Not sure if you know about ROMs and kernels?
Sent from my HTC One V using xda app-developers app
XxlemonxX said:
Ohh so someone messed it up and just gave it to you for free? Or for you to repair? Either way I don't follow the droid inc2 but maybe im sure its rooted if its in a boot loop so try going into fast boot and go into cmd prompt and try to install a recovery. Look up how to install a recovery through CmD Prompt on the Pc. On my phone can't explain all of it. And then just transfer over a ROM probably cm9 and follow the instructions
Unless you want to go back to stock? Not sure if you know about ROMs and kernels?
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Thats exactly what happened, it was given to me to me in this condition, and if I can fix it I will get paid for doing so.
Yes, I am familiar with roms, and kernels, I currently use an Evo 4g with Swagged out Stock X 2.0.9.8
Ive also rooted and flash cm7 on plenty of phones, I even have cm7 on my HP Touchpad.
I can't for the life of me figure this out. It has me highly intrigued. I am known for stressing out and overlooking minor small steps, so I wanted get some input from the community.
I currently have fastboot open, I am not entirely familiar with the Incredible 2, but normal case S-on = none rooted from my experience.
it was devunlocked then relocked i believe, from the error message i believe you are not flashing the right ruu, you are trying to flash an older one, you need the newest one, it was released a few months ago if i recall correctly and it was no big update but thats the one you need, search for it and try it it should work. if you are s on you cant flash a older ruu than whats already on it
Sent from my Incredible 2 using xda app-developers app
CrushRush said:
Thats exactly what happened, it was given to me to me in this condition, and if I can fix it I will get paid for doing so.
Yes, I am familiar with roms, and kernels, I currently use an Evo 4g with Swagged out Stock X 2.0.9.8
Ive also rooted and flash cm7 on plenty of phones, I even have cm7 on my HP Touchpad.
I can't for the life of me figure this out. It has me highly intrigued. I am known for stressing out and overlooking minor small steps, so I wanted get some input from the community.
I currently have fastboot open, I am not entirely familiar with the Incredible 2, but normal case S-on = none rooted from my experience.
Click to expand...
Click to collapse
Hboot 98 is compatible with revolutionary root method. I would start there, rooting and s-off with a stock rooted Rom...
Sent from my HTC Incredible 2 using xda premium
Your radio is .0312, so you won't be able to flash an RUU, they're all older. Can you recognize it in fastboot mode? Try unlocking again with HTCdev, then flashing a custom recovery and ROM.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 08:10 PM ---------- Previous post was at 08:08 PM ----------
Macrodroid said:
Hboot 98 is compatible with revolutionary root method. I would start there, rooting and s-off with a stock rooted Rom...
Sent from my HTC Incredible 2 using xda premium
Click to expand...
Click to collapse
Hboot .98 isn't compatible with revolutionary, only .97 is, but that doesn't make a difference anyways because you can't run revolutionary if you can't boot the phone.
Sent from my SCH-I535 using Tapatalk 2
prototype7 said:
Your radio is .0312, so you won't be able to flash an RUU, they're all older. Can you recognize it in fastboot mode? Try unlocking again with HTCdev, then flashing a custom recovery and ROM.
OMG..... As usual... I have been overlooking the obvious path to glory. Thank you. I think I can handle it form here.
That literally took me like 2 minutes.
Click to expand...
Click to collapse
CrushRush said:
prototype7 said:
Your radio is .0312, so you won't be able to flash an RUU, they're all older. Can you recognize it in fastboot mode? Try unlocking again with HTCdev, then flashing a custom recovery and ROM.
Click to expand...
Click to collapse
Are there any roms that you recommend that run smooth on the INC2?
Click to expand...
Click to collapse
I would proceed with s-off because it's so much better than htcdev unlock.
Sent from my ADR6350 using xda app-developers app
Hi guys, I had My HTC one verizon working on CM11 smoothly.
Then cyanogenmod sent out a new update and after reboot, My phone was stuck in the blue circle boot screen.
I can't get adb to recognize my device to push a ROM to the phone for recovery. And from what i understand there is no other way to push a zip to the phone.
Fastboot doesn't flash the zip.
EDIT: For future reference: Find the RUU from this page: Guru flash it via fastboot. It will return phone to stock.
Ignore the rest
I wiped all caches, factory reset, wiped dalvik, and did everthing i could, but after hours of trying I haven't accomplished anything.
I can get into recover (i'm using clockworkmod). Bootloader is unlocked, s-off, rooted.... Don't know what else to say
I can't enable debug mode since I can't even boot, and from what I understand that's why adb won't work... But that doesn't make sense since i don't have a system on it. (i wiped everything)
Do you have a nandroid you can restore?
Sent from my HTC6500LVW using Tapatalk
brymaster5000 said:
Do you have a nandroid you can restore?
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
No i do not. I just went over from the stock sense 5, to cm11.
Once i saw everything working i deleted all backups of any type...
Then forgot to back up before updating to the nightly.
So no, no nandroid.
Do you have fastboot working? If so, I would suggest an ruu.
Sent from my HTC6500LVW using Tapatalk
brymaster5000 said:
Do you have fastboot working? If so, I would suggest an ruu.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Fastboot working.
Explain please.
I saw RUU phrase used in multiple places but can't figure out what it fully means.
Click Here To Win said:
Fastboot working.
Explain please.
I saw RUU phrase used in multiple places but can't figure out what it fully means.
Click to expand...
Click to collapse
Go to the ruu thread: http://forum.xda-developers.com/showthread.php?t=2437436, grab the ruu. Go into fastboot, type fastboot oem rebootRUU...(search before you do though...I'm not100% on phrasing of commands), then when it boots to a black HTC, fastboot flash zip name.zip.
Please search before you do this though...I don't want to give you bad commands. But this should point you in the right direction. Good luck.
Sent from my HTC6500LVW using Tapatalk
brymaster5000 said:
Go to the ruu thread: http://forum.xda-developers.com/showthread.php?t=2437436, grab the ruu. Go into fastboot, type fastboot oem rebootRUU...(search before you do though...I'm not100% on phrasing of commands), then when it boots to a black HTC, fastboot flash zip name.zip.
Please search before you do this though...I don't want to give you bad commands. But this should point you in the right direction. Good luck.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Alright, I will look into this once I get home! I was thinking it was something very difficult and time consuming... Didn't realize it could be so simple.
I'll research it. Let you know how it goes!
brymaster5000 said:
Go to the ruu thread: http://forum.xda-developers.com/showthread.php?t=2437436, grab the ruu. Go into fastboot, type fastboot oem rebootRUU...(search before you do though...I'm not100% on phrasing of commands), then when it boots to a black HTC, fastboot flash zip name.zip.
Please search before you do this though...I don't want to give you bad commands. But this should point you in the right direction. Good luck.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Thanks times a million!
I downloaded the 1.1gb RUU, and installed now I'm back to stock, and will go back to cm11. Working!
Click Here To Win said:
Thanks times a million!
I downloaded the 1.1gb RUU, and installed now I'm back to stock, and will go back to cm11. Working!
Click to expand...
Click to collapse
Glad I could help. The lesson of today's story is to always keep at least one nandroid. ?
Sent from my Ecliptic One.