Develop Bugs

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

Major problems! Phone completely bricked nothing is fixing! Please help

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

[Q] Signature issues!

Normally I am not one to be in this position. But right now, I am desperate!
I got my HTC ONE 2 days ago. Did Rumrunner. Then I installed TWRP.
Everything went great. I even installed a rom.
Then back to TWRP. but I made the mistake of wiping everything.
Now I am stuck in FastBoot with the following
Tampered
Relocked
OS-1.10.605.10 (1.10.605.8)
I really don't know where to go at this point. Every time I try to FastBoot an RUU, I get a Signature Error!
Can someone out there in out community please help?
I considered myself good at this as I have been flashing for years. But I am in deep trouble now!
I could really use some direction Please?
Thanks!

switch2cingular said:
Normally I am not one to be in this position. But right now, I am desperate!
I got my HTC ONE 2 days ago. Did Rumrunner. Then I installed TWRP.
Everything went great. I even installed a rom.
Then back to TWRP. but I made the mistake of wiping everything.
Now I am stuck in FastBoot with the following
Tampered
Relocked
OS-1.10.605.10 (1.10.605.8)
I really don't know where to go at this point. Every time I try to FastBoot an RUU, I get a Signature Error!
Can someone out there in out community please help?
I considered myself good at this as I have been flashing for years. But I am in deep trouble now!
I could really use some direction Please?
Thanks!
Click to expand...
Click to collapse
Signed RUU showed up here.
Directions on how to flash the RUU are posted below this next instruction:
IMPORTANT: I'm going to link to a RUU restore instruction thread. For your case, STOP after quoted step below succeeds, It may fail a couple of times, just run it again. If you fall out of RUU, get back into RUU and run it again. Once it succeeds, stop. You're now back to stock.
Code:
Fastboot flash zip Rom.zip
:
Here is the thread to instructions, obviously your MD5 will differ. You'll find that MD5 on the NOSROMS site you download the RUU from.
Read it a few times and make sure you understand it. I hope this helps.

RE:
one4thewings said:
Signed RUU showed up here.
Directions on how to flash the RUU are posted below this next instruction:
IMPORTANT: I'm going to link to a RUU restore instruction thread. For your case, STOP after quoted step below succeeds, It may fail a couple of times, just run it again. If you fall out of RUU, get back into RUU and run it again. Once it succeeds, stop. You're now back to stock.
Code:
Fastboot flash zip Rom.zip
:
Here is the thread to instructions, obviously your MD5 will differ. You'll find that MD5 on the NOSROMS site you download the RUU from.
Read it a few times and make sure you understand it. I hope this helps.
Click to expand...
Click to collapse
Just woke up! Had to sleep my depression away!
I am going to do this now. I'll let you know how it goes.
Many Many Thanks!!!!
My PC is running very slow right now. Long story, but I'll get back to you tonight!!!

I tried 3 times with the first file.
Same outcome.
I am downloading the one for the OS .10.
Maybe that will work.
The are 4 different files.
Sent from my SCH-I545 using XDA Premium 4 mobile app

Hook your phone to your pc make sure your on the twrp home screen. Open your adb folder and open your command window.. Now type abd push then drag your rom zip into the command then type /data/media... That's the only way I could get a zip to take. I did the exact same thing as you a week ago.
Edit.. My bad. Missed the part where u are back to locked.

Taking long to download the file I want to try.
Will have to try flashing before work in the am.
Thanks for everyone that is helping. Tomorrow might be a good day!
Sent from my SCH-I545 using XDA Premium 4 mobile app

Awesome!!!!!!!
switch2cingular said:
Taking long to download the file I want to try.
Will have to try flashing before work in the am.
Thanks for everyone that is helping. Tomorrow might be a good day!
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
6:25am..... Back to Stock!!!!!!
Thanks to everyone who helped me get through this!!!!

Install new CM recovery using fastboot

I am attempting to make a Cyanogenmod recovery and need to know if I attempt to flash it in fastboot and it doesn't work, will I be able to flash back my other recovery (TWRP).
Everything compiles correctly and yet the update.zip will not flash over the TWRP recovery, so I am thinking I should try to install it using fastboot. but I don't want a brick!

It looks like I may need a jig (factory cable), due to the device lock implemented to allow computer access. Anybody ever used one? I have access to one, just need to make sure I can get the boot loader to accept fastboot commands.

Have you tried just to boot the recovery image? Using fastboot type : fastboot boot "my_revovery.img"
This loads the recovery in memory but nothing is permanent. I did this for a while before actually flashing twrp. I wouldn't suggest you flash anything until you can get it to boot. Then I would flash using fastboot, I never liked flashing recoveries from within other recoveries
Sent from my LG-V510 using Tapatalk

schalmers said:
Have you tried just to boot the recovery image? Using fastboot type : fastboot boot "my_revovery.img"
This loads the recovery in memory but nothing is permanent. I did this for a while before actually flashing twrp. I wouldn't suggest you flash anything until you can get it to boot. Then I would flash using fastboot, I never liked flashing recoveries from within other recoveries
Sent from my LG-V510 using Tapatalk
Click to expand...
Click to collapse
Cool! didn't know I could do that with a recovery. What I found out just a few moments ago is that I could flash the recovery and then when/if it didn't work, I could reboot the phone then get back into fastboot mode and reinstall the old recovery. I like your way better! Thank you.

Any progress on getting the CM recover to boot using fastboot?
Sent from my LG-V510 using Tapatalk

schalmers said:
Any progress on getting the CM recover to boot using fastboot?
Sent from my LG-V510 using Tapatalk
Click to expand...
Click to collapse
I will succeed! Attempt number 82, no not really, well, maybe. Lol.
everything compiles properly and when I do a fastboot boot, all I get is the Google screen, then nothing. I think that I'm going to try an earlier version of Java As I am using the latest version possible for the compilation process and apparently the earlier version works, and I'm not sure that this one does even though it should!
So, that will be my next step and I won't be giving up anytime soon.

Good luck with your efforts, I hope you succeed. I would like to learn more about developing but have never tried. What is the guide you are using for CM?
Sent from my LG-V510 using Tapatalk

schalmers said:
Good luck with your efforts, I hope you succeed. I would like to learn more about developing but have never tried. What is the guide you are using for CM?
Sent from my LG-V510 using Tapatalk
Click to expand...
Click to collapse
Everything from the cm site. Links are on my other distro but you can search for how to build cyanogenmod recovery to get started.
Right now I'm back on the kernel working on battery savings.
I switch back and forth occasionally.

Volte/Advanced calling fix

Here's a fairly simple fix to a lingering issue that affected the VZW m9. The fix came about during a discussion with the repair efforts @beaups made on one of the many phones that either end up without service or dead in his hands. Guess you could say this was a lemons to lemonade moment. The key to this was the realization that unlike the m8, the stock recovery on the m9 forward NO LONGER resets the golden nv radion settings. This process will do just that....
Remove volte from account. (If already enabled).
Then latest ruu and factory reset
Run this fastboot commands while booted to the white bootloader screen. For the HTC 10 remove the _ from the modem name.
fastboot erase modem_st1
fastboot erase modem_st2
Then reboot and try volte activation.

Thanks for this, will be testing out once i have the chance to go through the process.

Hey gang-
Just wanted to drop a note that i'm moving on. As such, I have requested my threads to be closed as I won't be around to support them much anymore. Any download links (if applicable) will also be removed shortly as well.
Thanks and peace out.

@dottat thanks for reopening the thread and I know you don't offer much support but could you shed some light on the details on how to remove Volte from your account and if you can flash custom ruu vs going back to stock and flashing stock ruu with stock recovery.
Sent using Tapatalk

I did the steps and I get "We encountered a problem activating Advanced Calling 1.0. Please try again later." Any ideas @dottat?
EDIT: Went to my account and enabled it on VZW. Rebooted my device and it was enabled on my device. Awesome!

Flyhalf205 said:
I did the steps and I get "We encountered a problem activating Advanced Calling 1.0. Please try again later." Any ideas @dottat?
EDIT: Went to my account and enabled it on VZW. Rebooted my device and it was enabled on my device. Awesome!
Click to expand...
Click to collapse
How did you deactivate it? Did you flash custom ruu or stock
Sent using Tapatalk

Tommydorns said:
How did you deactivate it? Did you flash custom ruu or stock
Sent using Tapatalk
Click to expand...
Click to collapse
I deactivated using the MyVerizon app. Once loaded up just turn deactivate the feature.

Flyhalf205 said:
I deactivated using the MyVerizon app. Once loaded up just turn deactivate the feature.
Click to expand...
Click to collapse
OK. Thank you what about the ruu which one did you flash? Are you using the new venom rom
Sent using Tapatalk

Tommydorns said:
@dottat thanks for reopening the thread and I know you don't offer much support but could you shed some light on the details on how to remove Volte from your account and if you can flash custom ruu vs going back to stock and flashing stock ruu with stock recovery.
Sent using Tapatalk
Click to expand...
Click to collapse
The basic premise of this fix has nothing to do with stock recovery. It's actually about doing what stock recovery USED to do for us. It used to reset nv radio info by wiping the modems during a factory reset. It no longer does so manually wiping them does the same thing. You probably could do it without RUU'ing as long as you know you are on vzw firmware/radios only.

Tommydorns said:
OK. Thank you what about the ruu which one did you flash? Are you using the new venom rom
Sent using Tapatalk
Click to expand...
Click to collapse
I used the only one that is available right now. I use my own stock rom.

dottat said:
The basic premise of this fix has nothing to do with stock recovery. It's actually about doing what stock recovery USED to do for us. It used to reset nv radio info by wiping the modems during a factory reset. It no longer does so manually wiping them does the same thing. You probably could do it without RUU'ing as long as you know you are on vzw firmware/radios only.
Click to expand...
Click to collapse
Thank you for the clarification. I thought I had to go back to stock rom, that's why I thought stock recovery. So as long as I have Verizon firmware / radios I can those fast boot flash those commands on Viper 5.0 after removing HD voice from my plan than reactive it after the commands ...
Sent using Tapatalk

Tommydorns said:
Thank you for the clarification. I thought I had to go back to stock rom, that's why I thought stock recovery. So as long as I have Verizon firmware / radios I can those fast boot flash those commands on Viper 5.0 after removing HD voice from my plan than reactive it after the commands ...
Sent using Tapatalk
Click to expand...
Click to collapse
Can't hurt it...

dottat said:
Can't hurt it...
Click to expand...
Click to collapse
OK... After setting up adb and fastboot, deactivating HD voice, putting the phone in Download Mode, making sure fastboot works by testing the reboot command. I tried those commands and it's basically saying that "erase" is not a valid command for modem_st1 and modem_st2 in CMD. Rebooted and reactivated HD voice on plan and phone and trying and it's saying I don't have a Verizon SIM on the phone, (It was saying this before) so I reboot to get data working again. I'm still on Viper 5.0. I did flash the Marshmellow RUU before flashing 4.3 back in February. Could I have lost a radio or something. @hallstevenson did you ever try it and get it to work?
Sent using Tapatalk

Tommydorns said:
OK... After setting up adb and fastboot, deactivating HD voice, putting the phone in Download Mode, making sure fastboot works by testing the reboot command. I tried those commands and it's basically saying that "erase" is not a valid command for modem_st1 and modem_st2 in CMD. Rebooted and reactivated HD voice on plan and phone and trying and it's saying I don't have a Verizon SIM on the phone, (It was saying this before) so I reboot to get data working again. I'm still on Viper 5.0. I did flash the Marshmellow RUU before flashing 4.3 back in February. Could I have lost a radio or something. @hallstevenson did you ever try it and get it to work?
Sent using Tapatalk
Click to expand...
Click to collapse
Take away the _ on the modem name
Sent from my HTC6545LVW using Tapatalk

dottat said:
Take away the _ on the modem name
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Thank you for the help.. It's keeps telling me failure, erase st1 is not supported. It will also say partition table does not exist. Ive verified I do have the corrected radio and firmware. I've tried both commands with modemst1 and modem_st1 with the same failure message in CMD.
Sent using Tapatalk

Tommydorns said:
Thank you for the help.. It's keeps telling me failure, erase st1 is not supported. It will also say partition table does not exist. Ive verified I do have the corrected radio and firmware. I've tried both commands with modemst1 and modem_st1 with the same failure message in CMD.
Sent using Tapatalk
Click to expand...
Click to collapse
In bootloader or download mode?
Sent from my HTC6545LVW using Tapatalk

Both. It doesn't have a fastboot where it says fastboot mode like on previous devices so I take it you use download mode. So I tried it in both. fastboot reboot command works in both modes.
Sent using Tapatalk

Tommydorns said:
Both. It doesn't have a fastboot where it says fastboot mode like on previous devices so I take it you use download mode. So I tried it in both. fastboot reboot command works in both modes.
Sent using Tapatalk
Click to expand...
Click to collapse
You are doing it wrong.
Sent from my HTC6545LVW using Tapatalk

Oh Ok, what am I doing wrong? I would love to get this to work. Thank you for your help.
Sent using Tapatalk

dottat said:
You are doing it wrong.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
OK, these are my steps, USB debugging enabled on Dev Options. Disabled HD Voice from My Verizon go into bootloader hook phone to PC type in CMD Those commands it says FAILED (remote: Partition modest 2 erase not supported) I've also typed in fastboot oem rebootRUU which it takes me to a blank screen HTC logo on it and gives me a warning then I typed those commands still same Failed message in CMD. Is there something I'm missing. Haven't had anybody come out and say they were successful. Only thing I haven't done it go all to stock RUU bit I have the latest radios and firmware so I don't know
Sent using Tapatalk