Hello,
I purchased a used Evo 3D for my wife and while I am familiar with rooting and modding on the Galaxy S3 (my phone) I am not familiar with the Evo 3D. My wife has not been able to get data services on her phone without being on WiFi since buying the phone. She took it to Sprint to get looked at and apparently they said the guy that owned it prior flashed it and flashed something wrong on the device so the radio is messed up. What is the best process to take this phone back to stock modem, firmware, etc.? Or is there a radio I can flash on her phone to make it work? I would greatly appreciate it. Thanks in advance.
Mart1an said:
Hello,
I purchased a used Evo 3D for my wife and while I am familiar with rooting and modding on the Galaxy S3 (my phone) I am not familiar with the Evo 3D. My wife has not been able to get data services on her phone without being on WiFi since buying the phone. She took it to Sprint to get looked at and apparently they said the guy that owned it prior flashed it and flashed something wrong on the device so the radio is messed up. What is the best process to take this phone back to stock modem, firmware, etc.? Or is there a radio I can flash on her phone to make it work? I would greatly appreciate it. Thanks in advance.
Click to expand...
Click to collapse
That depends on what he flashed. Do you get a Virgin Mobile logo when you boot the phone?
You can try my root and S-OFF guide and stop after Step1 if you don't care about root and S-OFF, but if the Virgin Mobile firmware was flashed by the previous owner you will need to go through a separate process to clean that up before the phone will be back to Sprint stock.
ramjet73
ramjet73 said:
That depends on what he flashed. Do you get a Virgin Mobile logo when you boot the phone?
You can try my root and S-OFF guide and stop after Step1 if you don't care about root and S-OFF, but if the Virgin Mobile firmware was flashed by the previous owner you will need to go through a separate process to clean that up before the phone will be back to Sprint stock.
ramjet73
Click to expand...
Click to collapse
No there isn't a virgin mobile sign when powered on. It looks and acts stock and being someone that roots and flashes roms on my phone, I never even thought that this could be the issue.
Mart1an said:
No there isn't a virgin mobile sign when powered on. It looks and acts stock and being someone that roots and flashes roms on my phone, I never even thought that this could be the issue.
Click to expand...
Click to collapse
If you can flash the RUU to get it back to 100% stock and data still doesn't work, then call Sprint and have them do manual provisioning of the data services. Based on what you've said so far, it sounds like voice calls are working OK?
ramjet73
ramjet73 said:
If you can flash the RUU to get it back to 100% stock and data still doesn't work, then call Sprint and have them do manual provisioning of the data services. Based on what you've said so far, it sounds like voice calls are working OK?
ramjet73
Click to expand...
Click to collapse
Yea her voice calls and text messages work. Just apps (and the internet itself) that require data will not work. Is there a certain requirement for going back to stock? From what I am reading, hBoot comes into play and what not. I don't have to deal with hBoot on my phone so I am not familiar with it.
Mart1an said:
Yea her voice calls and text messages work. Just apps (and the internet itself) that require data will not work. Is there a certain requirement for going back to stock? From what I am reading, hBoot comes into play and what not. I don't have to deal with hBoot on my phone so I am not familiar with it.
Click to expand...
Click to collapse
Is the phone rooted now? If so you will need to relock the bootloader, otherwise you can just flash the RUU.exe from Windows. You can check the current status by holding the VolumeDown+Power buttons until the bootloader appears.
It might be worth a call to Sprint to see if they have provisioned the data services properly before doing that. You could even go to the "Settings/System updates" from the main menu and try updating profile and prl from there before calling. The reason I recommended flashing the RUU is because Sprint told you the prior owner had flashed incorrect firmware, but that could be bad information.
ramjet73
ramjet73 said:
Is the phone rooted now? If so you will need to relock the bootloader, otherwise you can just flash the RUU.exe from Windows. You can check the current status by holding the VolumeDown+Power buttons until the bootloader appears.
It might be worth a call to Sprint to see if they have provisioned the data services properly before doing that. You could even go to the "Settings/System updates" from the main menu and try updating profile and prl from there before calling. The reason I recommended flashing the RUU is because Sprint told you the prior owner had flashed incorrect firmware, but that could be bad information.
ramjet73
Click to expand...
Click to collapse
I am flashing the RUU now. Will this put the radio/firmware/etc back to how the phone came? She was never able to update PRL or Profile and that is where the problem originated. We purchased the phone, activated it, and in order to provision it Sprint had us attempt the profile and PRL updates which would both fail. Sprint tech (that physically looked at it) said it had been flashed with a bad radio and that is why the phone would not accept the profile and PRL updates. I am hoping this RUU file will fix everything. I did check and the phone was not rooted (via root checker app) and when I went into the bootloader, it said the phone was s-on.
I just finished flashing the RUU. The kernel, baseband, and build all stayed the same and it still gives me an error when attempting to update the profile or PRL saying that the phone cannot access data services. Do I need to try flashing another radio at this point?
I am completely at a loss here because I found a list of all radios for this phone and she has the only one that has been released for ICS. The baseband on her phone matches the listing for the ICS radio. So I don't see how she has a bad radio. Would the kernel affect it any? Just trying to get this phone working.
Mart1an said:
I just finished flashing the RUU. The kernel, baseband, and build all stayed the same and it still gives me an error when attempting to update the profile or PRL saying that the phone cannot access data services. Do I need to try flashing another radio at this point?
I am completely at a loss here because I found a list of all radios for this phone and she has the only one that has been released for ICS. The baseband on her phone matches the listing for the ICS radio. So I don't see how she has a bad radio. Would the kernel affect it any? Just trying to get this phone working.
Click to expand...
Click to collapse
If you flashed the current RUU she has the correct radio and other firmware, and Sprint can verify that. As I said in my previous post, they may have given you incorrect information, but now that you flashed the RUU and are 100% stock you can all Sprint (*2) and ask them to make sure your data services are provisioned correctly.
ramjet73
ramjet73 said:
If you flashed the current RUU she has the correct radio and other firmware, and Sprint can verify that. As I said in my previous post, they may have given you incorrect information, but now that you flashed the RUU and are 100% stock you can all Sprint (*2) and ask them to make sure your data services are provisioned correctly.
ramjet73
Click to expand...
Click to collapse
She doesn't even have a standard recovery for me to try a radio fix I saw in another post. When I go into recovery there is an error on the bottom of the screen (relating to some sort of file) and it won't let me click on anything. And I can't try to flash the PG86IMG.zip because from what I understand you have to be s-off. When I boot up into the bootloader it is looking for the PG86IMG.zip but says it isn't present. does that matter? How can I get the recovery back if she isn't rooted and she is s-on?
EDIT: The error is "E:Can't open /cache/recovery/command"
Mart1an said:
She doesn't even have a standard recovery for me to try a radio fix I saw in another post. When I go into recovery there is an error on the bottom of the screen (relating to some sort of file) and it won't let me click on anything. And I can't try to flash the PG86IMG.zip because from what I understand you have to be s-off. When I boot up into the bootloader it is looking for the PG86IMG.zip but says it isn't present. does that matter? How can I get the recovery back if she isn't rooted and she is s-on?
EDIT: The error is "E:Can't open /cache/recovery/command"
Click to expand...
Click to collapse
If you flashed the RUU.exe you should have the stock recovery installed and not get errors when you boot into recovery. I honestly can't remember what the stock recovery looks like when you boot into it, but I think it has a triangle or some other graphic in the midde of the screen.
Also, if the RUU.exe completed successfully you should have the correct radio and firmware so there would be no need to flash anything else. Firmware, including radio, can only be updated by flashing an RUU if you are S-ON, since updating it from the bootloader requires S-OFF.
It sounds like your RUU flash may not have been complete if you are getting errors booting into recovery. Can you take a picture using your other phone of the bootloader screen and what you get when you try to boot recovery and post it here as attachments?
ramjet73
ramjet73 said:
If you flashed the RUU.exe you should have the stock recovery installed and not get errors when you boot into recovery. I honestly can't remember what the stock recovery looks like when you boot into it, but I think it has a triangle or some other graphic in the midde of the screen.
Also, if the RUU.exe completed successfully you should have the correct radio and firmware so there would be no need to flash anything else. Firmware, including radio, can only be updated by flashing an RUU if you are S-ON, since updating it from the bootloader requires S-OFF.
It sounds like your RUU flash may not have been complete if you are getting errors booting into recovery. Can you take a picture using your other phone of the bootloader screen and what you get when you try to boot recovery and post it here as attachments?
ramjet73
Click to expand...
Click to collapse
sure give me a second
how do I do that?
Mart1an said:
sure give me a second
how do I do that?
Click to expand...
Click to collapse
Go to "manage attachments" under additional options below the post icons. Click on that and it will allow you to attach the picture you took on your other phone if you hook it to your computer as "USB storage".
ramjet73
Ok. I will look into that today. I gave up last night. It got late and I was getting frustrated. Thank you for your help so far.
Sent from my SPH-L710 using xda premium
Come to find out it is a lot easier on my phone app. Here is a pic. Hope it is big enough. I chose the smaller option for the pic.
Sent from my SPH-L710 using xda premium
Mart1an said:
Come to find out it is a lot easier on my phone app. Here is a pic. Hope it is big enough. I chose the smaller option for the pic.
Click to expand...
Click to collapse
Yup, that's the stock recovery. Not sure why you are getting that error, though.
Your best bet might be to go to the htcdev.com website and get the unlock token and flash it, then flash a custom recovery and see if you can boot from the bootloader into that. That's all included in step 2 of my guide. You don't need to flash SuperSU if you don't want root, but at least you can see if 4EXT recovery will boot without errors.
Here's a thread in the Android Q&A section where someone had the same error on another HTC phone and solved it by flashing a custom recovery. It sounds to me like there might be something wrong with the physical partitions on your phone.
Can you boot into the stock ICS ROM successfully? If so, it might still be worth a call to Sprint to see if they can activate your wife's data services manually.
ramjet73
We have called many times prior to taking her phone to the Sprint store for someone to look at.
Sent from my SPH-L710 using xda premium
Related
I purchased a Rezound from eBay and it's locked with a gesture lock. The seller told me to do a factory reset, which I did a couple of times, and it doesn't reset the phone to the new activation screen. It looks like he rooted the phone at one point. The recovery screen says "Tampered," "Relocked," and "VIGOR PVT SHIP S-ON RL."
My question is, how do I get past the gesture lock? Will rooting and flashing a different rom do the trick? I am obviously a newbie, and likely wouldn't have rooted it and installed a custom rom if I didn't have to, but it seems like I may have to at this point. Thanks!
willievee said:
I purchased a Rezound from eBay and it's locked with a gesture lock. The seller told me to do a factory reset, which I did a couple of times, and it doesn't reset the phone to the new activation screen. It looks like he rooted the phone at one point. The recovery screen says "Tampered," "Relocked," and "VIGOR PVT SHIP S-ON RL."
My question is, how do I get past the gesture lock? Will rooting and flashing a different rom do the trick? I am obviously a newbie, and likely wouldn't have rooted it and installed a custom rom if I didn't have to, but it seems like I may have to at this point. Thanks!
Click to expand...
Click to collapse
Flash a custom recovery and wipe if you want the stock Rom.rooted
Or you can just ruu to stock and it will wipe it
Sent from my ADR6425LVW using Tapatalk 2
Thanks for the advice. I used the Rezound All in One kit and got it working. I'll leave it rooted for now, maybe install ICS on it.
willievee said:
Thanks for the advice. I used the Rezound All in One kit and got it working. I'll leave it rooted for now, maybe install ICS on it.
Click to expand...
Click to collapse
Deff go for ICS, i'd even recommend stepping up to Sense 4 but you might prefer stock
Sense 4.0 still has a few bugs, but 3.6 is golden.
Sent from my Clean ROM DE 1.4 Rezound
willievee said:
I purchased a Rezound from eBay and it's locked with a gesture lock. The seller told me to do a factory reset, which I did a couple of times, and it doesn't reset the phone to the new activation screen. It looks like he rooted the phone at one point. The recovery screen says "Tampered," "Relocked," and "VIGOR PVT SHIP S-ON RL."
My question is, how do I get past the gesture lock? Will rooting and flashing a different rom do the trick? I am obviously a newbie, and likely wouldn't have rooted it and installed a custom rom if I didn't have to, but it seems like I may have to at this point. Thanks!
Click to expand...
Click to collapse
Obviously the first thing that comes to mind is if all it needed was to have a factory reset done why didn't the seller do just that and avoid the hassle? Kinda like when you look at a car and all it needs for the AC to work is a recharge..yeah I've been bit by that one before too.
Glad you got it working..youll enjoy being rooted
Looks like it isn't entirely right. I took it to Verizon to get it activated, and I have data connectivity but cannot call or text at all. The software version is 4.0.3 Android with 3.6 Sense. I am going to try to restore the factory version (from this thread http://forum.xda-developers.com/showthread.php?t=1338916) and hope that does the trick. Otherwise, I guess there's something wrong and I have to return the phone to the seller.
willievee said:
Looks like it isn't entirely right. I took it to Verizon to get it activated, and I have data connectivity but cannot call or text at all. The software version is 4.0.3 Android with 3.6 Sense. I am going to try to restore the factory version (from this thread http://forum.xda-developers.com/showthread.php?t=1338916) and hope that does the trick. Otherwise, I guess there's something wrong and I have to return the phone to the seller.
Click to expand...
Click to collapse
If you haven't done this yet, what is your baseband.
Sent from my ADR6425LVW using xda app-developers app
My baseband is 1.22.10.0421r.
I haven't done anything yet. Currently downloading the RUU.
willievee said:
My baseband is 1.22.10.0421r.
I haven't done anything yet. Currently downloading the RUU.
Click to expand...
Click to collapse
Are you downloading aan ICS ruin?
Sent from my ADR6425LVW using xda app-developers app
I want to restore it to stock, so I'm downloading an official RUU from this thread: http://forum.xda-developers.com/showthread.php?t=1338916&page=12.
(RUU_Vigor_VERIZON_WWE_2.01.605.11_Radio_RS_0.95.00.1123r_3161E_9K_QMR_release_233635_signed.exe)
willievee said:
I want to restore it to stock, so I'm downloading an official RUU from this thread: http://forum.xda-developers.com/showthread.php?t=1338916&page=12.
(RUU_Vigor_VERIZON_WWE_2.01.605.11_Radio_RS_0.95.00.1123r_3161E_9K_QMR_release_233635_signed.exe)
Click to expand...
Click to collapse
You wont be able to run that RUU. You are s-on and cannot go backwards in RUU you can only go forward. Either s-off or you'll need to flash the latest ICS RUU leak.
Sent from my ADR6425LVW using xda app-developers app
Gotcha. Thanks. I'll try to sort out how to download the newest ICS RUU and flash it. I tried to follow these directions: http://forum.xda-developers.com/showthread.php?t=1614366
and downloaded [ICS][2.25][STOCK][5-7]PH98IMG.zip but I wasn't able to flash it. I guess I have to figure out which ICS RUU to download and flash.
I still don't understand why I have data but no call or text capability.
willievee said:
Gotcha. Thanks. I'll try to sort out how to download the newest ICS RUU and flash it. I tried to follow these directions: http://forum.xda-developers.com/showthread.php?t=1614366
and downloaded [ICS][2.25][STOCK][5-7]PH98IMG.zip but I wasn't able to flash it. I guess I have to figure out which ICS RUU to download and flash.
I still don't understand why I have data but no call or text capability.
Click to expand...
Click to collapse
http://multiupload.biz/bdkjtkk1j4zw/PH98IMG_MultiUpload.biz.zip.html
Download that file, rename it PH98IMG.ZIP and make sure it isn't named PH98IMG.ZIP.ZIP and then put that on the root of the actual SD Card. Not the internal memory.
Reboot into hboot, and it will find that file and load it. You will have to chose volume + to accept. It will flash bootloader first, then the radios and rom and such. After this has flashed and booted, delete the PH98IMG.ZIP file from your sd card, and then reboot into hboot and chose factory reset. Let it do its thing, and try a phone call or text on reboot.
should be good to go after this.
I downloaded the file, put it in the root directory of the sd card, and booted into hboot. It says "Loading PH98IMG.zip" for a few minutes, then goes back to the hboot screen. I then powered down, removed SD card, and tried to factory reset. The phone entered the Android system recovery. I rebooted, and the phone seemed exactly the same. I'll retry, maybe I'm doing something wrong.
Update: I've retried a few times, and it just seems that hboot won't load PH98IMG.zip. Might it matter that I'm still at S-ON?
willievee said:
I downloaded the file, put it in the root directory of the sd card, and booted into hboot. It says "Loading PH98IMG.zip" for a few minutes, then goes back to the hboot screen. I then powered down, removed SD card, and tried to factory reset. The phone entered the Android system recovery. I rebooted, and the phone seemed exactly the same. I'll retry, maybe I'm doing something wrong.
Click to expand...
Click to collapse
Try redownloading again might have been a bad download. Remember once the file starts to flash it might shut off and turn on and continue doing its thing just make sure when it's all done every item says "ok" next to it if it does your good to go next just make sure you go into bootloader do a factory reset.
Sent from my Sense4 ICS Rezound
willievee said:
I downloaded the file, put it in the root directory of the sd card, and booted into hboot. It says "Loading PH98IMG.zip" for a few minutes, then goes back to the hboot screen. I then powered down, removed SD card, and tried to factory reset. The phone entered the Android system recovery. I rebooted, and the phone seemed exactly the same. I'll retry, maybe I'm doing something wrong.
Update: I've retried a few times, and it just seems that hboot won't load PH98IMG.zip. Might it matter that I'm still at S-ON?
Click to expand...
Click to collapse
No s-on wouldn't matter. Your bootloader is still locked right?
Sent from my ADR6425LVW using xda app-developers app
I unlocked the bootloader last night. Redownloading the file now.
willievee said:
I unlocked the bootloader last night. Redownloading the file now.
Click to expand...
Click to collapse
Relock the bootloader I believe when S-ON you have to lock it to run the RUU
Sent from my Sense4 ICS Rezound
LakerStar25 said:
Relock the bootloader I believe when S-ON you have to lock it to run the RUU
Sent from my Sense4 ICS Rezound
Click to expand...
Click to collapse
This. It won't run else wise. I didn't think to ask this as you said previously it was locked.
My bad.
Sent from my ADR6425LVW using xda app-developers app
I rooted my evo 4g lte. I was having issues with data today and updating the profile. so I was going to unroot and try it stock. I relocked the bootlader, and somehow my rom image is gone!!!! i cant flash the ruu, it keeps failing error 155. someone please help me
Wrong thread. Need to be posted in q&a
sent from my EVO LTE with it's security flags down.
jrgalioto said:
I rooted my evo 4g lte. I was having issues with data today and updating the profile. so I was going to unroot and try it stock. I relocked the bootlader, and somehow my rom image is gone!!!! i cant flash the ruu, it keeps failing error 155. someone please help me
Click to expand...
Click to collapse
Similar thing happened to me. I have hboot 1.15. I relocked the the phone ran the RUU. Phone booted up normal with the everything stock. I then took the OTA and when it rebooted it was updating then it rebooted and the phone never turned on again. I sent it to HTC for warranty. They will get it tuesday. I'll see how this goes.
Okay guys... Enough with the flaming. If you can help, post! If not, don't. Grow up. It was posted in the wrong section. Use the report button in the upper-right corner of the post and report it.
Now, let me see if I can actually help you.
You're getting this error because you're trying to flash an older RUU on the phone than what's already on there. You'll need to flash the same RUU version or higher. If you took the latest OTA update, there may not be one available yet. I'd suggest you go through the HTCDev unlock again until that RUU makes it to the internet.
Team Nocturnal posted a couple of the older RUU versions.
http://www.androidfilehost.com/main/EVO_4G_LTE_Developers/Team.Nocturnal/RUU/
~co~
closeone said:
Okay guys... Enough with the flaming. If you can help, post! If not, don't. Grow up. It was posted in the wrong section. Use the report button in the upper-right corner of the post and report it.
Now, let me see if I can actually help you.
You're getting this error because you're trying to flash an older RUU on the phone than what's already on there. You'll need to flash the same RUU version or higher. If you took the latest OTA update, there may not be one available yet. I'd suggest you go through the HTCDev unlock again until that RUU makes it to the internet.
Team Nocturnal posted a couple of the older RUU versions.
http://www.androidfilehost.com/main/EVO_4G_LTE_Developers/Team.Nocturnal/RUU/
~co~
Click to expand...
Click to collapse
Here is the issue with that though. When i run the RUU, it says my current image is........nothing. i have tried to flash the newest and the oldest versions.
jrgalioto said:
Here is the issue with that though. When i run the RUU, it says my current image is........nothing. i have tried to flash the newest and the oldest versions.
Click to expand...
Click to collapse
Hi there jrgalioto. Can you do me a favor, and boot into your bootloader for me? I'd like you to check the green text.
What Radio version does it say you have?
Also, if you can connect the phone up to your computer and run the fastboot command (in FASTBOOT USB mode):
Code:
fastboot getvar mainver
What number comes back? (If you can't run the command, don't worry about it)
---
If I might ask, why did you relock the phone?
---
I'm looking into trying to get you a link to a current RUU. One has been posted, but I can't access it because of Filefactory's restrictions. Hopefully somebody will post a mirror to the download soon.
~co~
closeone said:
Hi there jrgalioto. Can you do me a favor, and boot into your bootloader for me? I'd like you to check the green text.
What Radio version does it say you have?
Also, if you can connect the phone up to your computer and run the fastboot command (in FASTBOOT USB mode):
Code:
fastboot getvar mainver
What number comes back? (If you can't run the command, don't worry about it)
---
If I might ask, why did you relock the phone?
---
I'm looking into trying to get you a link to a current RUU. One has been posted, but I can't access it because of Filefactory's restrictions. Hopefully somebody will post a mirror to the download soon.
~co~
Click to expand...
Click to collapse
I relocked because I needed to bring it back to Sprint for service, so I needed to unroot it, because I wasn't receiving data to it. But I got it figured out now. I was able to unlock the bootloader again and my recovery was still there. So i reflashed a custom ROM, so I at least had something on my phone. When I called Sprint, I told them it was not a phone issue, they updated my username in the system, then I was able to ##72786# to get the hands free activation to complete without error 1012. So I am now back in business. However, If I ever do have to unroot again, I will be in the same boat.
jrgalioto said:
I relocked because I needed to bring it back to Sprint for service, so I needed to unroot it, because I wasn't receiving data to it. But I got it figured out now. I was able to unlock the bootloader again and my recovery was still there. So i reflashed a custom ROM, so I at least had something on my phone. When I called Sprint, I told them it was not a phone issue, they updated my username in the system, then I was able to ##72786# to get the hands free activation to complete without error 1012. So I am now back in business. However, If I ever do have to unroot again, I will be in the same boat.
Click to expand...
Click to collapse
For future ref...sprints tep policy covers rooted phones
Of course the first variable that could be the issue in any given situation is the fact that a phone is rooted
Sent from my SPH-L710 using xda app-developers app
00mred00 said:
For future ref...sprints tep policy covers rooted phones
Of course the first variable that could be the issue in any given situation is the fact that a phone is rooted
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
That was the 1st thought I had. What if the root is causing the issue. It, however was not the case. and all is now right with the world, and I am no longer a brick...for now...
jrgalioto said:
That was the 1st thought I had. What if the root is causing the issue. It, however was not the case. and all is now right with the world, and I am no longer a brick...for now...
Click to expand...
Click to collapse
Hi jrgalioto,
I was able to get a link to the new RUU for you. This one should work fine for you.
~co~
Yep...... sprint doesnt care that you're rooted.
I frequently tell them mine is so they dont go messing with things they shouldnt be
OK I just cleaned this thread of a bunch of GARBAGE.
If you don't want to help, post on a blog.
The guy is looking for help.
Seriously .
il Duce said:
OK I just cleaned this thread of a bunch of GARBAGE.
If you don't want to help, post on a blog.
The guy is looking for help.
Seriously .
Click to expand...
Click to collapse
Sorry duce
Sent from the depths of hell
Hey I try to help and I have even written a guide with a ton of info, I even went so far as to write down troubleshooting stuff and they still post the exact same stuff over and over, some times its a bit frustrating. I even gave instructions on what they need to do should they completely ruin the file tree, when have you seen anyone completely destroy the internal memory lol
closeone said:
Hi there jrgalioto. Can you do me a favor, and boot into your bootloader for me? I'd like you to check the green text.
What Radio version does it say you have?
Also, if you can connect the phone up to your computer and run the fastboot command (in FASTBOOT USB mode):
Code:
fastboot getvar mainver
What number comes back? (If you can't run the command, don't worry about it)
---
If I might ask, why did you relock the phone?
---
I'm looking into trying to get you a link to a current RUU. One has been posted, but I can't access it because of Filefactory's restrictions. Hopefully somebody will post a mirror to the download soon.
~co~
Click to expand...
Click to collapse
Any luck on the mirror for the new RUU download? I'm using the latest one I can find and I am stuck and can't get my phone to reboot, shutdown or anything. I can't run fastboot either. all I see is ***Tampered*** unlocked*** ....RUU update fail!
My phone won't respond to the volume down and power button either.
any suggestions?
So I haven't really found anyone with as specific a situation I'm in so I figured I'd make a new thread.
I was running a CM10.1 build from late July, which still had some bugs but was bearable. I upgraded to CM10.2 to try it out, but it was buggier than the CM10.1 build. I saw that the bugs were fixed in the latest build of CM10.1 so I flashed that. Since then I've been stuck in Roaming and can't activate my phone.
Each time I flashed I restored my 100% stock backup (I have a nandroid from the day I got the phone). Every flash was a clean install wiping data/cache/dalvik. Was first roaming when I reverted back to CM10.1, but restoring my backup and even flashing CM10.2 again I'm roaming still.
Basically, once I was roaming, I haven't stopped regardless of ROM.
And I'm sure someone will ask, I have S-off.
How do I go about fixing this?
EDIT: I've tried a clean flash of the same ROM with the sim card removed and tried changing the subscription type after like I've seen in another thread, but this did not work.
Bartikus said:
So I haven't really found anyone with as specific a situation I'm in so I figured I'd make a new thread.
I was running a CM10.1 build from late July, which still had some bugs but was bearable. I upgraded to CM10.2 to try it out, but it was buggier than the CM10.1 build. I saw that the bugs were fixed in the latest build of CM10.1 so I flashed that. Since then I've been stuck in Roaming and can't activate my phone.
Each time I flashed I restored my 100% stock backup (I have a nandroid from the day I got the phone). Every flash was a clean install wiping data/cache/dalvik. Was first roaming when I reverted back to CM10.1, but restoring my backup and even flashing CM10.2 again I'm roaming still.
Basically, once I was roaming, I haven't stopped regardless of ROM.
And I'm sure someone will ask, I have S-off.
How do I go about fixing this?
EDIT: I've tried a clean flash of the same ROM with the sim card removed and tried changing the subscription type after like I've seen in another thread, but this did not work.
Click to expand...
Click to collapse
This happened to me randomly. Only thing that works is RUU back to stock and go through the motions. You won't lose S-OFF, so you can then come back.
hurrrtin said:
This happened to me randomly. Only thing that works is RUU back to stock and go through the motions. You won't lose S-OFF, so you can then come back.
Click to expand...
Click to collapse
I need to RUU all the down to 1.15 correct? Then will I need to Moonshine again?
Bartikus said:
I need to RUU all the down to 1.15 correct? Then will I need to Moonshine again?
Click to expand...
Click to collapse
If you are S-OFF, then yes- RUU back down to 1.15. You won't need to moonshine again.
---------- Post added at 12:18 PM ---------- Previous post was at 12:13 PM ----------
hurrrtin said:
If you are S-OFF, then yes- RUU back down to 1.15. You won't need to moonshine again.
Click to expand...
Click to collapse
It might take a little while for it to change from roaming back to normal. Just give it time after you RUU.
Bartikus said:
So I haven't really found anyone with as specific a situation I'm in so I figured I'd make a new thread.
I was running a CM10.1 build from late July, which still had some bugs but was bearable. I upgraded to CM10.2 to try it out, but it was buggier than the CM10.1 build. I saw that the bugs were fixed in the latest build of CM10.1 so I flashed that. Since then I've been stuck in Roaming and can't activate my phone.
Each time I flashed I restored my 100% stock backup (I have a nandroid from the day I got the phone). Every flash was a clean install wiping data/cache/dalvik. Was first roaming when I reverted back to CM10.1, but restoring my backup and even flashing CM10.2 again I'm roaming still.
Basically, once I was roaming, I haven't stopped regardless of ROM.
And I'm sure someone will ask, I have S-off.
How do I go about fixing this?
EDIT: I've tried a clean flash of the same ROM with the sim card removed and tried changing the subscription type after like I've seen in another thread, but this did not work.
Click to expand...
Click to collapse
I'm having the exact same issue after doing the same thing you did, not sure where to go with it at this point, nothing is working
PhantomApollyon said:
I'm having the exact same issue after doing the same thing you did, not sure where to go with it at this point, nothing is working
Click to expand...
Click to collapse
Did you try to RUU back to 1.15? I just tried running it and it crashed, not sure if it's my computer or what
hurrrtin said:
If you are S-OFF, then yes- RUU back down to 1.15. You won't need to moonshine again.
Click to expand...
Click to collapse
I tried running the RUU from here http://forum.xda-developers.com/showthread.php?t=2017525
I ignored the first part about relocking since I assumed since I have s-off I don't need to, and I immediately tried to run the .exe as admin and it crashed.
UPDATE: I've relocked it now but the RUU still crashes before doing anything.
Bartikus said:
I tried running the RUU from here http://forum.xda-developers.com/showthread.php?t=2017525
I ignored the first part about relocking since I assumed since I have s-off I don't need to, and I immediately tried to run the .exe as admin and it crashed.
UPDATE: I've relocked it now but the RUU still crashes before doing anything.
Click to expand...
Click to collapse
try grabbing the RUU from the blue link in my sig
.torrented said:
try grabbing the RUU from the blue link in my sig
Click to expand...
Click to collapse
Downloading the RUU now. I've also tried flashing the 1.15 hboot and recovery, but they don't seem to have done anything. I'm still on 2.06... I unlocked my phone originally with moonshine, so my bootloader used to say moonshine s-off. now it says tampered/locked so I think hboot worked, but the recovery doesn't seem to have done anything.
UPDATE: The RUU ran it's course. Seems like the file for the other link was just bad (I had downloaded it twice). The phone is attempting to activate now, but it still can't get a signal. I know the signal at my house is usually pretty bad, but leaving it on the window sill usually does the trick. If worse comes to worse, could I at this point return it to Verizon without them knowing what's up?
Bartikus said:
Downloading the RUU now. I've also tried flashing the 1.15 hboot and recovery, but they don't seem to have done anything. I'm still on 2.06... I unlocked my phone originally with moonshine, so my bootloader used to say moonshine s-off. now it says tampered/locked so I think hboot worked, but the recovery doesn't seem to have done anything.
UPDATE: The RUU ran it's course. Seems like the file for the other link was just bad (I had downloaded it twice). The phone is attempting to activate now, but it still can't get a signal. I know the signal at my house is usually pretty bad, but leaving it on the window sill usually does the trick. If worse comes to worse, could I at this point return it to Verizon without them knowing what's up?
Click to expand...
Click to collapse
the point of the 1.15 hboot is so the RUU works... if you want to return to stock to take to vzw I would follow the restore guide, i believe its posted in the regular dev section and not the original dev section
edit* this one right here: http://forum.xda-developers.com/showthread.php?t=2293919
.torrented said:
the point of the 1.15 hboot is so the RUU works... if you want to return to stock to take to vzw I would follow the restore guide, i believe its posted in the regular dev section and not the original dev section
edit* this one right here: http://forum.xda-developers.com/showthread.php?t=2293919
Click to expand...
Click to collapse
Yeah the RUU seemed to work, I just still can't get a signal. Phone says no service and I can't get past the activation screen. I say "seemed" to work because I can't check in settings because I can't get past the activation... but the bootloader looks like stock again, whereas it said tampered before the RUU.
Thank you for the help by the way, I appreciate it.
RUU worked, I'm on 1.15. However, it didn't solve my no service problem. Could this be as trivial as a SIM problem? Is there anything else it might be?
Reset the Phone
Bartikus said:
RUU worked, I'm on 1.15. However, it didn't solve my no service problem. Could this be as trivial as a SIM problem? Is there anything else it might be?
Click to expand...
Click to collapse
After RUU you must Reset the phone from STOCK recovery,
finanandroid said:
After RUU you must Reset the phone from STOCK recovery,
Click to expand...
Click to collapse
Worked like a charm, thanks!
Bartikus said:
Worked like a charm, thanks!
Click to expand...
Click to collapse
U welcome! Glad you finally back on business :good:
finanandroid said:
U welcome! Glad you finally back on business :good:
Click to expand...
Click to collapse
Where can I find the STOCK recovery? I've been going crazy with this stock on roam thing.
RUU to get back to Stock Recovery
chipymunk said:
Where can I find the STOCK recovery? I've been going crazy with this stock on roam thing.
Click to expand...
Click to collapse
In order to recovery or restore the original phone factory setting you have to do RUU and Reset Phone*** is the way to get back
Stock recovery(= reset phone) to work properly. Even if you are on a Stock Rom it has a custom recovery so doing factory reset wont
work to restore the original phone setting.
after RUU you must do a phone reset either from setting>back up & reset or from the bootloader factory reset is the same Stock Recovery.
I read somewhere that flashing this Rom Stock rooted fix a roaming thing so you can give it a shot http://forum.xda-developers.com/showthread.php?t=2471836
Hello, I have the HTC Rezound from Verizon and I need a code to unlock sim card to work on other networks in Europe, if anyone can help I would be happy.
Thank you ...:good:
elvabih said:
Hello, I have the HTC Rezound from Verizon and I need a code to unlock sim card to work on other networks in Europe, if anyone can help I would be happy.
Thank you ...:good:
Click to expand...
Click to collapse
Not to be blunt, but no, you don't need a code... The HTC Rezound, and all recent (last 3-4 years or so) Verizon phones with GSM capability are NOT SIM locked, it was a deal with the FCC and Verizon for use of the 700Mhz spectrum.
To use your Rezound on a local network in Europe, insert the SIM, power up the phone, and go to the Network settings and setup your APN, and in Phone Info set Preferred Network set it to Global, GSM, WCDMA Preferred, or whatever is appropriate for your situation and it should just work.
ok
acejavelin said:
Not to be blunt, but no, you don't need a code... The HTC Rezound, and all recent (last 3-4 years or so) Verizon phones with GSM capability are NOT SIM locked, it was a deal with the FCC and Verizon for use of the 700Mhz spectrum.
To use your Rezound on a local network in Europe, insert the SIM, power up the phone, and go to the Network settings and setup your APN, and in Phone Info set Preferred Network set it to Global, GSM, WCDMA Preferred, or whatever is appropriate for your situation and it should just work.
Click to expand...
Click to collapse
It did not help anything and than again I have a sim locked on the lock screen and can not send sms, I did a lot from this forum but can not seem to solve it though thanks a lot for your help if someone has some idea of a free report
elvabih said:
It did not help anything and than again I have a sim locked on the lock screen and can not send sms, I did a lot from this forum but can not seem to solve it though thanks a lot for your help if someone has some idea of a free report
Click to expand...
Click to collapse
what hboot, radios, and firmware version do you have? You would have to be at 4. something firmware for it to work properly.
acejavelin said:
what hboot, radios, and firmware version do you have? You would have to be at 4. something firmware for it to work properly.
Click to expand...
Click to collapse
andoid version
2.3.4
HTC Sense version
3.5
Software number
2.01.605.11
ERI Version
5
elvabih said:
andoid version
2.3.4
HTC Sense version
3.5
Software number
2.01.605.11
ERI Version
5
Click to expand...
Click to collapse
Yeah, that is really old, even by the Rezounds standards... the Gingerbread firmware does not have the global mode GSM stuff fully enabled, the first ICS release had some functionality, but until the last OTA it wasn't fully working.
You are in a precarious position since most updates have been OTA and require an active Verizon service to get them... You would have to find the RUU for 3.14.605.12 and run it (last full RUU available, it will wipe the phone), then find the OTA zip for 3.14.605.13 and manually load it, followed by 4.5.605.14 which will fully unlock the GSM potential of the phone.
If this is a road you want to go down, I would recommend going S-Off, this would require a customer ROM with an unsecure kernel to do, and at least ICS firmware. Without S-OFF if something goes wrong in the updating procedure you have no way to go back once you get to 3.14.605.12 or higher firmware.
acejavelin said:
Yeah, that is really old, even by the Rezounds standards... the Gingerbread firmware does not have the global mode GSM stuff fully enabled, the first ICS release had some functionality, but until the last OTA it wasn't fully working.
You are in a precarious position since most updates have been OTA and require an active Verizon service to get them... You would have to find the RUU for 3.14.605.12 and run it (last full RUU available, it will wipe the phone), then find the OTA zip for 3.14.605.13 and manually load it, followed by 4.5.605.14 which will fully unlock the GSM potential of the phone.
If this is a road you want to go down, I would recommend going S-Off, this would require a customer ROM with an unsecure kernel to do, and at least ICS firmware. Without S-OFF if something goes wrong in the updating procedure you have no way to go back once you get to 3.14.605.12 or higher firmware.
Click to expand...
Click to collapse
hm S-OFF what it is. the whole process for me is a little complicated had a guide link or something to try if you have help
I've found this
I hope it is ok
https://kickass.so/htc-rezound-s-of...unutbear-infection-2-9-1-how-to-t7770753.html
S-off is
---------- Post added at 02:58 PM ---------- Previous post was at 02:56 PM ----------
That's the old way, but it will work. The easier way is just to get the phone upgraded to Ice Cream Sandwich then get a custom ROM on the phone and use rumrunner S-Off... The real issue right now is your own gingerbread firmware which causes most modern tools to fail.
acejavelin said:
S-off is
---------- Post added at 02:58 PM ---------- Previous post was at 02:56 PM ----------
That's the old way, but it will work. The easier way is just to get the phone upgraded to Ice Cream Sandwich then get a custom ROM on the phone and use rumrunner S-Off... The real issue right now is your own gingerbread firmware which causes most modern tools to fail.
Click to expand...
Click to collapse
have a solution for it
elvabih said:
have a solution for it
Click to expand...
Click to collapse
Is that a question, or a statement?
The "solution" would be to upgrade to 3.14.605.12 via this file: RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe - 604.05 MB
This is a true "RUU" and it is run from your computer, it does a complete re-image of the phone.
This will do a complete wipe of the phone, EVERYTHING will be reset to factory defaults. Once you are on this firmware, you can install the OTA's to get current using this thread's instructions and starting the procedure at Part 2A, Step 5, even though you are not S-OFF yet, this procedure can be followed, just not the "downgrade" portion.
Once you are current, you can flash most custom ROMs and obtain S-OFF. If you are using the Rezound on GSM networks I would recommend staying with a custom ROM though, to minimize MMS issues and the "Unknown SIM" warning.
acejavelin said:
Is that a question, or a statement?
The "solution" would be to upgrade to 3.14.605.12 via this file: RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe - 604.05 MB
This is a true "RUU" and it is run from your computer, it does a complete re-image of the phone.
This will do a complete wipe of the phone, EVERYTHING will be reset to factory defaults. Once you are on this firmware, you can install the OTA's to get current using this thread's instructions and starting the procedure at Part 2A, Step 5, even though you are not S-OFF yet, this procedure can be followed, just not the "downgrade" portion.
Once you are current, you can flash most custom ROMs and obtain S-OFF. If you are using the Rezound on GSM networks I would recommend staying with a custom ROM though, to minimize MMS issues and the "Unknown SIM" warning.
Click to expand...
Click to collapse
I start right away
elvabih said:
I start right away
Click to expand...
Click to collapse
this is not right, every time I try this happen
ERROR [155 ~ 159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
So you run the RUU and follow the directions it gives you and you have a Verizon HTC Rezound model ADR6425?
acejavelin said:
So you run the RUU and follow the directions it gives you and you have a Verizon HTC Rezound model ADR6425?
Click to expand...
Click to collapse
each RUU I started exactly in the order showed the same mistake
and the model is ADR6425LVW
elvabih said:
each RUU I started exactly in the order showed the same mistake
and the model is ADR6425LVW
Click to expand...
Click to collapse
Try this one: https://www.dropbox.com/s/66kpaiyyukjzu0j/RUU_Vigor_VERIZON_WWE_3.14.605.12_PH98IMG.zip?dl=0
rename the file to PH98IMG.zip (be careful of the Windows .zip.zip issue when renaming) and place it on the root of the sd card then boot into Hboot, it should see it and process the archive automatically.
It isn't as clean as the other way, but gets around issues with a bad EXE file since this is all done from the phone, and not a Windows PC.
acejavelin said:
Try this one: https://www.dropbox.com/s/66kpaiyyukjzu0j/RUU_Vigor_VERIZON_WWE_3.14.605.12_PH98IMG.zip?dl=0
rename the file to PH98IMG.zip (be careful of the Windows .zip.zip issue when renaming) and place it on the root of the sd card then boot into Hboot, it should see it and process the archive automatically.
It isn't as clean as the other way, but gets around issues with a bad EXE file since this is all done from the phone, and not a Windows PC.
Click to expand...
Click to collapse
installation aborted
E;Can"t mount /dev/block/mmcblk0p36
elvabih said:
installation aborted
E;Can"t mount /dev/block/mmcblk0p36
Click to expand...
Click to collapse
Umm... yeah... Does this phone boot? /dev/block/mmcblk0p36 is the cache partition... if it can't be mounted you have other issues, is this the only error you receive?
I would find a copy of Amon Ra, not sure if TWRP would work, and boot it with fastboot, then wipe all partitions twice, if any of them can't be wiped or formated, you may have a defective emmc module (the internal storage memory)... Seems quite common these are failing in Rezounds recently, seen at least half-dozen in the last few months, it is not repairable if that is the case.
acejavelin said:
Umm... yeah... Does this phone boot? /dev/block/mmcblk0p36 is the cache partition... if it can't be mounted you have other issues, is this the only error you receive?
I would find a copy of Amon Ra, not sure if TWRP would work, and boot it with fastboot, then wipe all partitions twice, if any of them can't be wiped or formated, you may have a defective emmc module (the internal storage memory)... Seems quite common these are failing in Rezounds recently, seen at least half-dozen in the last few months, it is not repairable if that is the case.
Click to expand...
Click to collapse
delete and format the memory both worked, and only this error with the installation zip file, unless something else now shows only htc phone on the display and can not be on
Try the RUU's again, the one you run from PC first, and if it fails try the ph98img method.
Ok I unlocked my loader, then i think what happend was clockwerk installed its self to the boot partition so i was stuck in a loop. I used One_M8_All-In-One_Kit_v to flash a new recovery lower version at that and now i do have a bootable recovery. Problem is now i didn't backup like a dumb arse my working OS and flashed a bad one or maybe the radio or some crap needed to be done first since it was going from 4.4.2 to 5+. In short all i have is recovery and sideload and every rom i download fails to sideload on the phone side and says sucessful on the pc cmd window. Need help with this please
Darthdiddy said:
Ok I unlocked my loader, then i think what happend was clockwerk installed its self to the boot partition so i was stuck in a loop. I used One_M8_All-In-One_Kit_v to flash a new recovery lower version at that and now i do have a bootable recovery. Problem is now i didn't backup like a dumb arse my working OS and flashed a bad one or maybe the radio or some crap needed to be done first since it was going from 4.4.2 to 5+. In short all i have is recovery and sideload and every rom i download fails to sideload on the phone side and says sucessful on the pc cmd window. Need help with this please
Click to expand...
Click to collapse
Wipe data, cache, dalvik, put the appropriate ROM for your carrier/build on SD card or root of internal storage and flash. All else fails run an RUU, bring you back to 100% stock then you can properly reinstall the custom recovery of your choice.
CavyS said:
Wipe data, cache, dalvik, put the appropriate ROM for your carrier/build on SD card or root of internal storage and flash. All else fails run an RUU, bring you back to 100% stock then you can properly reinstall the custom recovery of your choice.
Click to expand...
Click to collapse
I do the proper wipe before flashing my new rom, i'm under the AT&T HTC One M8 section i believe my phone was only @ 4.4.2 before this and here is the bootloader info is :
***Tampered***
***Unlocked***
M8_UL_CA_ PVT SHIP S-On
HBOOT-3.16.0.0000
RADIO-1.16.21331931.LA11G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Apr 18 2014,16:06:33.22985
Tried cm-12-20150131-NIGHTLY-m8 it fails to flash and its on the sd and internal. SkyDragon M8 Sense Rom installs but doesn't boot (tried 2 versions of this rom 700mb and a 1.6gb), believe i tried a couple other roms in my phones section there's only like 9 of them there. I have the stock RUU but fails to detect the phone and fails i think it's meant to sense a turned on functional phone i don't see any kind of recovery method with the stock ruu. All i want is a rom to work with Straight talk the stock os even being unlocked and rooted with su still shoved the default APN down my throat(I even paid 2.99$ for the SQLlite and deleted all other APNs still won't let me check off a APN profile i created as default) making my signal on ST flakey and couldn't get mms to work just picture txting wasn't working. So i went full on like my old HTC One X but dived head first too fast didn't backup my old OS and didn't know firewater was gone till i was at that step of the procedure and it was too late Oh and using TWRP 2.7.1.0 it's the highest i can use before it won't boot.
Darthdiddy said:
I do the proper wipe before flashing my new rom, i'm under the AT&T HTC One M8 section i believe my phone was only @ 4.4.2 before this and here is the bootloader info is :
***Tampered***
***Unlocked***
M8_UL_CA_ PVT SHIP S-On
HBOOT-3.16.0.0000
RADIO-1.16.21331931.LA11G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Apr 18 2014,16:06:33.22985
Tried cm-12-20150131-NIGHTLY-m8 it fails to flash and its on the sd and internal. SkyDragon M8 Sense Rom installs but doesn't boot (tried 2 versions of this rom 700mb and a 1.6gb), believe i tried a couple other roms in my phones section there's only like 9 of them there. I have the stock RUU but fails to detect the phone and fails i think it's meant to sense a turned on functional phone i don't see any kind of recovery method with the stock ruu. All i want is a rom to work with Straight talk the stock os even being unlocked and rooted with su still shoved the default APN down my throat(I even paid 2.99$ for the SQLlite and deleted all other APNs still won't let me check off a APN profile i created as default) making my signal on ST flakey and couldn't get mms to work just picture txting wasn't working. So i went full on like my old HTC One X but dived head first too fast didn't backup my old OS and didn't know firewater was gone till i was at that step of the procedure and it was too late Oh and using TWRP 2.7.1.0 it's the highest i can use before it won't boot.
Click to expand...
Click to collapse
Boot into fastboot, check device manager (if youre on windows) for any unknown drivers and install them if you can. Then run the RUU I posted here http://forum.xda-developers.com/att-htc-one-m8/help/100-stock-4-4-4-ruu-t3017594 which would update you to 4.4.4.
CavyS said:
Boot into fastboot, check device manager (if youre on windows) for any unknown drivers and install them if you can. Then run the RUU I posted here http://forum.xda-developers.com/att-htc-one-m8/help/100-stock-4-4-4-ruu-t3017594 which would update you to 4.4.4.
Click to expand...
Click to collapse
Ok TY i'll try that soon as it downloads, i did finally get RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2
To see the phone and no progress bar shows up on the phone and the program errors out, i even did a full system wipe before i tried it again still to no avail.
CavyS said:
Boot into fastboot, check device manager (if youre on windows) for any unknown drivers and install them if you can. Then run the RUU I posted here http://forum.xda-developers.com/att-htc-one-m8/help/100-stock-4-4-4-ruu-t3017594 which would update you to 4.4.4.
Click to expand...
Click to collapse
Ok tried that stock ruu and it failed i did finally get the phone running on a badseed rom based on 4.4.2 all seems to be working now except i can't send pictures in texts but regular text, calls, and internet work seems to be a common problem with straight talk. So new problem probably a thread somewhere on here about it i'll take a look, thank you for the help
Darthdiddy said:
Ok tried that stock ruu and it failed i did finally get the phone running on a badseed rom based on 4.4.2 all seems to be working now except i can't send pictures in texts but regular text, calls, and internet work seems to be a common problem with straight talk. So new problem probably a thread somewhere on here about it i'll take a look, thank you for the help
Click to expand...
Click to collapse
You'll have to setup your APN and mms message size settings for straight talk, that should fix the text messaging problems.
CavyS said:
You'll have to setup your APN and mms message size settings for straight talk, that should fix the text messaging problems.
Click to expand...
Click to collapse
No matter what message app i try i can't send pictures or large txts my mms is borked and to make matters worse when i installed this rom i must of removed the stock HTC messaging app so i can't find any settings to set the mms size limits. I'd like to figure out how to put the stock messaging app back on the phone without redoing the whole OS
Using Handcent and hangouts and i see no size limit options within the apps or anywhere in the phone settings. Looked up my phone specifically and where the option/s is supposed to be the said section of options is not even there.
If you've got a stock rom downloaded to your computer or sd card you can unzip it and look in system app folder and find the htc messaging apks. Then just install them as system apps and fix permissions.
Sent from my HTC One_M8 using XDA Free mobile app
Before i try and fix my obvious other problems does anyone know how to fix a bad flash of TWRP? I'm used to just adb command line flashing it and never had a issue before on my HTC One X, but seems it a was bad idea and it landed on boot partition and is causing glitches. is there a stock boot i can flash or what do i need?
Darthdiddy said:
but seems it a was bad idea and it landed on boot partition and is causing glitches.?
Click to expand...
Click to collapse
Why do you think that partition, in particular? If you are talking about boot.img, that gets re-flashed any time your flash a ROM.
Try fastboot erase cache, and flash recovery by fastboot. If Clockwork doesn't work, try TWRP.
If you indeed have some corrupted partition(s), your best bet is to RUU. You are non-specific about what error codes, so its hard to help you troubleshoot why the RUU failed. Try a more updated RUU, such as 2.23.
redpoint73 said:
Why do you think that partition, in particular? If you are talking about boot.img, that gets re-flashed any time your flash a ROM.
Try fastboot erase cache, and flash recovery by fastboot. If Clockwork doesn't work, try TWRP.
If you indeed have some corrupted partition(s), your best bet is to RUU. You are non-specific about what error codes, so its hard to help you troubleshoot why the RUU failed. Try a more updated RUU, such as 2.23.
Click to expand...
Click to collapse
Error 155 Unknown Error it says, do i need to relock the bootloader? I could never find a way to S-Off the device so idk if its that or corrupted partition like you said but all my services on my phone crash constantly. But that's better then aokp_task650_m8_kitkat_5.13.2014 that one won't even make it through setup the services crash so often the badseed rom is the only other rom i found that is actually usable. Oh my RUU is 2.0.16 how can i find the newest one for my HTC One M8?
Darthdiddy said:
Error 155 Unknown Error it says, do i need to relock the bootloader?
Oh my RUU is 2.0.16 how can i find the newest one for my HTC One M8?
Click to expand...
Click to collapse
You always need to relock the bootloader to run RUU with s-on. No exceptions.
Hopefully this will clear up your RUU problem, although the RUU number you just supplied above doesn't make any sense (doesn't correspond to any RUU for this device) Where did you find it, and its not what you referenced in Post #5 above.
CavyS already supplied a link for the "latest" AT&T RUU in Post #4 above. Although be aware, that if you are successful in running the latest RUU, it will render sunshine unable to achieve s-off. I suggest RUU to 1.58 or 2.23 (if you want s-off), as those should still be supported by sunshine.
Darthdiddy said:
I could never find a way to S-Off the device
Click to expand...
Click to collapse
Did you try sunshine? Its the only way to s-off at this time.
redpoint73 said:
You always need to relock the bootloader to run RUU with s-on. No exceptions.
Hopefully this will clear up your RUU problem, although the RUU number you just supplied above doesn't make any sense (doesn't correspond to any RUU for this device) Where did you find it, and its not what you referenced in Post #5 above.
CavyS already supplied a link for the "latest" AT&T RUU in Post #4 above. Although be aware, that if you are successful in running the latest RUU, it will render sunshine unable to achieve s-off. I suggest RUU to 1.58 or 2.23 (if you want s-off), as those should still be supported by sunshine.
Did you try sunshine? Its the only way to s-off at this time.
Click to expand...
Click to collapse
Relocked and flashed the ruu utility version said 2.0.16.2014 and is KK 4.4, idk about sunshine as to reading about people with my phone and it not working so for a 25$ leap of faith not sure what to do about that. My phone is running perfect now in a locked down carrier branded and bloatware way lol. Thanks guys, anyway i can tell if sunshine will work on my phone?
Darthdiddy said:
Relocked and flashed the ruu utility version said 2.0.16.2014 and is KK 4.4
Click to expand...
Click to collapse
I think that is the version of the actual installer software (.exe) not the ROM version it will install on your phone. Kitkat for AT&T would be either 1.58 or 2.23. That number will be in the actual file name of the RUU, so just look there (actually a much longer string of numbers starting with 1.58 or 2.23, but I've abbreviated them for convenience).
Darthdiddy said:
idk about sunshine as to reading about people with my phone and it not working so for a 25$ leap of faith not sure what to do about that. My phone is running perfect now in a locked down carrier branded and bloatware way lol. Thanks guys, anyway i can tell if sunshine will work on my phone?
Click to expand...
Click to collapse
You install the sunshine APK, run it, and sunshine will tell you whether it can s-off the phone or not. You won't be charged unless it can successfully s-off the phone. I haven't heard of any folks here that got charged, and sunshine couldn't s-off the device.
redpoint73 said:
I think that is the version of the actual installer software (.exe) not the ROM version it will install on your phone. Kitkat for AT&T would be either 1.58 or 2.23. That number will be in the actual file name of the RUU, so just look there (actually a much longer string of numbers starting with 1.58 or 2.23, but I've abbreviated them for convenience).
You install the sunshine APK, run it, and sunshine will tell you whether it can s-off the phone or not. You won't be charged unless it can successfully s-off the phone. I haven't heard of any folks here that got charged, and sunshine couldn't s-off the device.
Click to expand...
Click to collapse
Wow thanks for the info! Before i try this can after S-OFF/rooting/SU can i install the unlocked/developer ruu from HTC and get HTC OTA and get away from this bloated carrier branded crap? So much in the forums and i can't find a answer to this question anywhere.