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.
Related
Hello,
I installed the AOKP "adrenalized" ROM yesterday (http://forum.xda-developers.com/showthread.php?t=1884085), and while I initially had a great experience with it, it seems several things have started to go wrong for me.
The most pressing issue is that I can no longer make any phone calls... within the first 12 hours or so of having the ROM, this was not an issue (I received a phone call), but all of a sudden, I no longer have any mobile signal (either 4g or 3g) whatsoever, and if I try to make a call, it says "Mobile network not available." I tried searching online for help with this, but I could not find anything.
The other two issues (these are not as pressing as my inability to make/receive calls) are a persistent error that I have a "Damaged SD card" and I can't access my internal storage when I hook up my phone to my PC. I did find someone else on another phone having an issue with AOKP/damaged sd card, but the fix suggested (editing a file called vold.fstab) did not work (the line to edit in the file was not present in my file).
Sorry for the long post - I am fairly inexperienced when it comes to this stuff, but any help is greatly appreciated.
rocketman13 said:
Hello,
I installed the AOKP "adrenalized" ROM yesterday (http://forum.xda-developers.com/showthread.php?t=1884085), and while I initially had a great experience with it, it seems several things have started to go wrong for me.
The most pressing issue is that I can no longer make any phone calls... within the first 12 hours or so of having the ROM, this was not an issue (I received a phone call), but all of a sudden, I no longer have any mobile signal (either 4g or 3g) whatsoever, and if I try to make a call, it says "Mobile network not available." I tried searching online for help with this, but I could not find anything.
The other two issues (these are not as pressing as my inability to make/receive calls) are a persistent error that I have a "Damaged SD card" and I can't access my internal storage when I hook up my phone to my PC. I did find someone else on another phone having an issue with AOKP/damaged sd card, but the fix suggested (editing a file called vold.fstab) did not work (the line to edit in the file was not present in my file).
Sorry for the long post - I am fairly inexperienced when it comes to this stuff, but any help is greatly appreciated.
Click to expand...
Click to collapse
Need a little bit more info for me to be helpful. S-on or off? Did you verify MD5 before installing? What rom did you come from? Latest firmware? Anything you can provide about your setup would be useful. TBH, it sounds like you had a bad download, so I'd try to re-download and verify MD5 before you install.
iamwalterwhite said:
Need a little bit more info for me to be helpful. S-on or off? Did you verify MD5 before installing? What rom did you come from? Latest firmware? Anything you can provide about your setup would be useful. TBH, it sounds like you had a bad download, so I'd try to re-download and verify MD5 before you install.
Click to expand...
Click to collapse
Thanks for your reply, iamwalterwhite. Here is the relevant information:
S-On
Previous ROM before AOKP: Scott's CleanROM Pro 4.5
Firmware: Android Version 4.0.4
Baseband version: 0.95.00.1118r, 0.95.00.1223r
Unfortunately, I did not check the MD5 before I installed because I thought the risk of not doing it would be low. Apparently, I was wrong! Given that information, do you think it is still worth verifying MD5 and re-installing AOKP? Thanks.
You are still on gb firmware. Flashing the old firmware patch may help.
Sent from my Kindle Fire using Tapatalk 2
pwned3 said:
You are still on gb firmware. Flashing the old firmware patch may help.
Sent from my Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
Wow, really? How can you tell? I thought Android version 4.0.4 was Ice Cream Sandwich, and I vaguely remember flashing a GB firmware patch when I first installed Scott's CleanROM 4.5, but my memory could be a bit fuzzy... should I just reboot to AmonRa recovery and flash it? Thanks for your help!
We can tell based off of your baseband version. Honestly, I think you should re-lock then flash the newest RUU. It will probably clear up your problem. If you'd still like, I can tell you how to check an MD5, but I think it's best if you flash that RUU. It's worth it, our radios have gone through multiple updates since the version that you have.
iamwalterwhite said:
We can tell based off of your baseband version. Honestly, I think you should re-lock then flash the newest RUU. It will probably clear up your problem. If you'd still like, I can tell you how to check an MD5, but I think it's best if you flash that RUU. It's worth it, our radios have gone through multiple updates since the version that you have.
Click to expand...
Click to collapse
Thanks, iamwalterwhite. I did some searching and found the latest RUU for the Rezound as 4.03.605.1 (I found it on Android Police, but I can't post the link since I'm a new user). However, it seems I am supposed to check the MD5 for that file as well.
Assuming that is the latest RUU though, then the steps I'd follow are: download the RUU/verify MD5, name it as PH98IMG.zip in my SDcard root, re-lock my bootloader, and finally reboot to AmonRa recovery to flash this RUU.
Are there any steps I am missing? Thanks again for your help... it is much appreciated.
You need to install in hboot not recovery. Running this will also write over your recovery. I suggest having the newest amon ra downloaded so you can unlock and flash it after the ruu
Sent from my Rezound using Xparent SkyBlue Tapatalk 2
rocketman13 said:
Thanks, iamwalterwhite. I did some searching and found the latest RUU for the Rezound as 4.03.605.1 (I found it on Android Police, but I can't post the link since I'm a new user). However, it seems I am supposed to check the MD5 for that file as well.
Assuming that is the latest RUU though, then the steps I'd follow are: download the RUU/verify MD5, name it as PH98IMG.zip in my SDcard root, re-lock my bootloader, and finally reboot to AmonRa recovery to flash this RUU.
Are there any steps I am missing? Thanks again for your help... it is much appreciated.
Click to expand...
Click to collapse
Have you set up an ADB folder? If so, place the RUU in your adb folder then execute this command in a command prompt:
cd c:\(your adb folder name)
You should then get a screen that looks like this:
c:\(your adb folder name)>
Then type: md5sums (ruu name).zip
Should look like this:
c:\(adb folder name)> md5sums (ruu name).zip
Your steps are mostly correct, however, you must flash the PH98IMG.zip via hboot. In fact, you won't be able to get to your recovery if you boot into your bootloader with the .zip on your sd card.
By the way, don't use the .1 RUU. Follow this link: http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/ This is the .2 (seems like a hopelessly miniscule difference), but it's the most current.
Edit: Since you are s-on, you will need to unlock via HTCDEV after the RUU. Then you can go about installing AR 3.15 the same way as you did before. If you plan on going s-off, you might want to consider doing that before running the RUU. I know it's a lot of information, and a lot to sift through (not to mention the many different ways to do do things) but going s-off makes it much more simple.
iamwalterwhite said:
Have you set up an ADB folder? If so, place the RUU in your adb folder then execute this command in a command prompt:
cd c:\(your adb folder name)
You should then get a screen that looks like this:
c:\(your adb folder name)>
Then type: md5sums (ruu name).zip
Should look like this:
c:\(adb folder name)> md5sums (ruu name).zip
Your steps are mostly correct, however, you must flash the PH98IMG.zip via hboot. In fact, you won't be able to get to your recovery if you boot into your bootloader with the .zip on your sd card.
By the way, don't use the .1 RUU. Follow this link: This is the .2 (seems like a hopelessly miniscule difference), but it's the most current.
Edit: Since you are s-on, you will need to unlock via HTCDEV after the RUU. Then you can go about installing AR 3.15 the same way as you did before. If you plan on going s-off, you might want to consider doing that before running the RUU. I know it's a lot of information, and a lot to sift through (not to mention the many different ways to do do things) but going s-off makes it much more simple.
Click to expand...
Click to collapse
A HUGE thank you to both of you!! I restored my phone to the .2 RUU, and I now have a working phone and proper access to my internal storage. Unfortunately iamwalterwhite, I didn't see your message until after I finished installing the RUU, so I am still on S-On, but I am rooted. Do you know if I could still get to S-Off from this point (i.e. after installing RUU on my phone)?
Also, do you think it is ok to try re-installing the AOKP ROM that previously gave me problems (I verified the MD5), or should I hold off/try another ROM?
Again, thanks to you both, iamwalterwhite and pwned3. I was pretty lost otherwise.
rocketman13 said:
A HUGE thank you to both of you!! I restored my phone to the .2 RUU, and I now have a working phone and proper access to my internal storage. Unfortunately iamwalterwhite, I didn't see your message until after I finished installing the RUU, so I am still on S-On, but I am rooted. Do you know if I could still get to S-Off from this point (i.e. after installing RUU on my phone)?
Also, do you think it is ok to try re-installing the AOKP ROM that previously gave me problems (I verified the MD5), or should I hold off/try another ROM?
Again, thanks to you both, iamwalterwhite and pwned3. I was pretty lost otherwise.
Click to expand...
Click to collapse
Sorry to post again, but I just had an issue arise that has been pestering me for a while. Anytime my GPS is on, my phone shuts off and reboots within a minute or so... I know Rezound folks had this problem a while back due to the Google Maps update, but I've been having this for a while, even when I was on Scott's CleanROM and with fixed Maps. Now that I am on RUU (rooted), I hoped this problem would go away because I use Navigation a lot... but unfortunately, it is still here. I currently have Maps 6.12.0.
Does anyone have any thoughts/suggestions? Thanks.
rocketman13 said:
A HUGE thank you to both of you!! I restored my phone to the .2 RUU, and I now have a working phone and proper access to my internal storage. Unfortunately iamwalterwhite, I didn't see your message until after I finished installing the RUU, so I am still on S-On, but I am rooted. Do you know if I could still get to S-Off from this point (i.e. after installing RUU on my phone)?
Also, do you think it is ok to try re-installing the AOKP ROM that previously gave me problems (I verified the MD5), or should I hold off/try another ROM?
Again, thanks to you both, iamwalterwhite and pwned3. I was pretty lost otherwise.
Click to expand...
Click to collapse
You're welcome, that's why they call this here a community. If I was you, I wouldn't try to s-off right now. The reason I say that is because the juopunutbear method to s-off uses a different hboot (I believe the jbear hboot is .25 while the RUU is .27). That hboot was compatible with the ICS ota pre-global. You may have to wait until they get an update do to it. At this point, you will only have to worry about extracting the boot.img for roms that aren't global based (aokp being an example), but that should be a small annoyance. Much smaller, than say, bricking your phone!
iamwalterwhite said:
You're welcome, that's why they call this here a community. If I was you, I wouldn't try to s-off right now. The reason I say that is because the juopunutbear method to s-off uses a different hboot (I believe the jbear hboot is .25 while the RUU is .27). That hboot was compatible with the ICS ota pre-global. You may have to wait until they get an update do to it. At this point, you will only have to worry about extracting the boot.img for roms that aren't global based (aokp being an example), but that should be a small annoyance. Much smaller, than say, bricking your phone!
Click to expand...
Click to collapse
A number of people have been successful with S-OFF on hboot 2.27 using the .5 ControlBear. There seem to be no issues with it at all.
shrike1978 said:
A number of people have been successful with S-OFF on hboot 2.27 using the .5 ControlBear. There seem to be no issues with it at all.
Click to expand...
Click to collapse
Just found this thread: http://forum.xda-developers.com/showthread.php?t=1883924&page=2 It looks like there have been a few successes wit s-off even after the .2 RUU. Thanks Shrike!
iamwalterwhite said:
Just found this thread: It looks like there have been a few successes wit s-off even after the .2 RUU. Thanks Shrike!
Click to expand...
Click to collapse
Oh man, I'm not sure I'm brave enough to do the infamous "wire trick" just yet... but I will keep that link as a reference once I feel more confident.
Also, sorry to bother you again, but did any of you happen to see my previous post about my GPS:
rocketman13 said:
Sorry to post again, but I just had an issue arise that has been pestering me for a while. Anytime my GPS is on, my phone shuts off and reboots within a minute or so... I know Rezound folks had this problem a while back due to the Google Maps update, but I've been having this for a while, even when I was on Scott's CleanROM and with fixed Maps. Now that I am on RUU (rooted), I hoped this problem would go away because I use Navigation a lot... but unfortunately, it is still here. I currently have Maps 6.12.0.
Does anyone have any thoughts/suggestions? Thanks.
Click to expand...
Click to collapse
As always, thank you very much!!
rocketman13 said:
Oh man, I'm not sure I'm brave enough to do the infamous "wire trick" just yet... but I will keep that link as a reference once I feel more confident.
Also, sorry to bother you again, but did any of you happen to see my previous post about my GPS:
As always, thank you very much!!
Click to expand...
Click to collapse
I saw that post abou GPS, but I'm not familiar with that at all. The only thing that I recall was the problem with the upgrade in google maps. Apophis has a thread over in General where he lists his g-talk (along with some other users). He might be able to help.
iamwalterwhite said:
I saw that post abou GPS, but I'm not familiar with that at all. The only thing that I recall was the problem with the upgrade in google maps. Apophis has a thread over in General where he lists his g-talk (along with some other users). He might be able to help.
Click to expand...
Click to collapse
Ok, great! I'll see if I can ask about the GPS. Thanks for your help!
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
As the title says, I'd like to restore the backup it creates. I have a problem with my phone where it receives zero signal regardless of what rom installed. I have seen a different thread on this problem but there was no clear answer on how to solve it so I'm trying to backtrack my steps. I did the following all at the same time, htc unlock, s-off exploit with Juopunut, and sim unlock using config.dat. They all seemed to work perfectly until I got this problem. I'd ask for support at umlimited.io but when I did they insisted they didn't create the problem and if I persisted in asking how to restore their Juopunut backup I'd be kicked...which was kinda rude, but what are you going to do? Thanks in advance for any help.
what is your radio version? I'd suggest updating to latest radios. or maybe you did something wrong with the sim unlock
EM|NEM said:
what is your radio version? I'd suggest updating to latest radios. or maybe you did something wrong with the sim unlock
Click to expand...
Click to collapse
Didn't even know the radio version could be upgraded/ downgraded. I did a quick search for this but didn't find where to grab a download. Where can I find an update for this? The radio version is 11.25.3504.06_M Also note that this is a GSM phone. So if this is a different incompatible version let me know!
Edit: So, I managed to find some, but when the bootloader trys to flash it it'll give me the message "Model ID incorrect!" This is from the GSM thread...what's going on?
your CID is incompatible. I'd suggest you run an RUU with the latest radios. then flash recovery and then rom.
EM|NEM said:
your CID is incompatible. I'd suggest you run an RUU with the latest radios. then flash recovery and then rom.
Click to expand...
Click to collapse
It's not the CID, I just rewrote it to HTC__001, unless it's expecting something else? It was originally ROGER001 I think.
Edit: I just noticed something, when in fastboot mode the model name is SHOOTER_U, Is there always a underscore there?
hmm not sure about this. If you want to get back to stock you should run the Rogers ICS RUU. see if you get signals back
EM|NEM said:
hmm not sure about this. If you want to get back to stock you should run the Rogers ICS RUU. see if you get signals back
Click to expand...
Click to collapse
Alright, will do. Is there anything I have to do in preparation, relock bootloader, etc?
yes you do need to relock. sorry i forgot to mention that
Well, the RUU update software completely fails. It fails at trying to get the phone to boot into the bootloader and then just pops up a message saying unknown error 155. Anyone know what the hell is going on with my phone?
i think the problem may be your hboot. Try flashing this hboot
http://forum.xda-developers.com/showthread.php?t=1906172
then make sure its locked/relocked then run RUU
Finally got it to install, I had to extract the rom.zip from the .exe and then rename it so that hboot would detect it. Installed fine, but the problem still persists. I have no signal what so ever. Is there no fix for this?
you just installed the rom. u need the radio with it too. Any ways i think some1 else should post in here as im all out of ideas
Does your phone see your sim card? Have you set up your apn's? Can you find a wifi and connect?
Sent from my Evo 3D GSM using Tapatalk 2
Yes, wifi connects, bluetooth connects. I'm pretty sure that the rom.zip is actually everything, it ha s a check list when installing, one of those things was called radio...so I'm pretty sure it installed a new or reinstalled that version. ALso, APNs don't do anything. It's almost like a driver issue or something, the radio just won't get a signal, android doesn't even detect it. When in the options the mobile network toggle is greyed out.
Ok and what rom are you trying to use?
Sent from my Evo 3D GSM using Tapatalk 2
It's the stock ROGERS RUU, I had to extract the ROM.zip file from it because the .exe gave me a unknown error. renaming the .zip to PG86IMG.zip seemed to work. I'm now on stock. The previous roms were nonsense and coolsense. I should also note that originally I tried to install a cdma miui rom that obviously failed.
So your mobile data is still greyed out? Have you tried to find a network through the mobile data settings
Sent from my Evo 3D GSM using Tapatalk 2
---------- Post added at 03:27 PM ---------- Previous post was at 03:20 PM ----------
And count yourself lucky because you could have bricked your phone if you had flashed a cdma firmware package
Sent from my Evo 3D GSM using Tapatalk 2
Yes, it searches for a while, then find a few networks which I'm taking a as a good sign that it even did that, but will not connect at all. When I select one it trys to open a toast error but then is closed immediately after, so I can't even read the error. When I check the network info in the android phone identity it just shows nothing, zero for signal, no network, etc.
Could be sim unlock that did? But I am guessing
Sent from my Evo 3D GSM using Tapatalk 2
Alright, so I've made some progress. I found that this is actually model PG8631000 instead of PG8630000 which is why it failed checks. A quick edit of the android-info.txt in the zip files allows it to flash. No problems with that, flashed new hboots and radios. However, the problem is still there. So finally I found a radio fix program for linux. Booted it up and it appears that my phone won't give any MEID values, they were probably wiped or something. I can't progress because with the wrong values I can completely brick the phone. This makes sense that the phone doesn't have the right values, it feels like the radio works, but has the incorrect values (which is why it finds services but won't connect). Is there any way to restore the MEID?
Edit: Well I'm an idiot, MEID is for CDMA phones. My phone status shows values for the network so that isn't it either....I'm so lost.
Hello friends,
One of my friends has got an HTC Amaze 4G from the US. The phone is already factory sim unlocked. He's given this phone to me because he wanted it to read and write Arabic letters and RTL in general.
I got this phone, what I've already done till I had the problem was, unlocking bootloader -> installing EXT4 -> got a patch from Hasoon2000 (Link to the original thread) -> EXT4 Recovery for wiping cache, dalvik and fixing permissions -> Flashed the Arabic Patch zip -> Wooops! the phone is stuck at the HTC screen.
I've searched the forums for an RUU to get the phone back and fix the soft brick. All what I found were RUUs for different carriers from CA and US (RUU collections thread)
Later on, I relocked the bootloader, downloaded this RUU
PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC _30.66.550L.08D_release_228638_signed.zip
Put it on an Ext SD card, went to fastboot bootloader, it started detecting the ZIP and finished showing this error "Incorrect Phone ID"
Then I downloaded this one (Asian RUU) too after some searching.
PH85IMG_Ruby_hTC_Asia_WWE_1.60.707.3_R_Radio_1.13.550L.13DC_30.69b.550L.101_release_253820_signed.zip
The fastboot detected it but ended up with going back to bootloader main menu without any prompts or errors.
Finally, I am clueless and came here to ask you for your help and suggestions to overcome this problem.
Notes:
-The phone is Factory Sim Unlocked and does not have any names of any carries burnt into it (Unbranded Phone).
-After finishing the process of unlocking bootloader, I saw the list of the languages selectable were English (Singapore), English (Pakistan), and other Asian languages and no US and EU languages were present (That's why I was trying to install the RUU of Asia)
-The phone is on Stock GB 2.3.4, stock kernel, and EXT4 Recovery.
Thanks all
Have you tried restoring a backup. Can you boot into the bootloader and recovery?. If so you just need to figure out why this device is unbranded. I never seen an amaze unbranded unless the digitizer was replaced at some point. Was this phone ics or gingerbread before it was tampered with?
Sent from my VLE_U using xda app-developers app
if by unbranded you mean the phone just has HTC and no other carrier lable on it then its most likely the Canadian version from Wind Mobile or Telus or Mobilicity. and as far as you downloading the RUUs have you renamed them to PH85IMG.zip before trying to flash them in bootloader? another easy way to find out what stock ruu you need is to check your HBOOT version on the boot loader so you can see what stock RUU's are compatible with it
whozilla said:
Have you tried restoring a backup. Can you boot into the bootloader and recovery?. If so you just need to figure out why this device is unbranded. I never seen an amaze unbranded unless the digitizer was replaced at some point. Was this phone ics or gingerbread before it was tampered with?
Sent from my VLE_U using xda app-developers app
Click to expand...
Click to collapse
Unfortunately, I have not taken any backup, as I assumed at first that the process is quite simpler (which is already is). I already ran at much harder work than this one with ios, symbian, bada, and android.
Yes, I can boot into the bootloader and recovery.
I neither know the reason for unbranding the device.
It was Stock Gingerbread 2.3.4
Thank you for your appreciated time and help.
Ninjistix said:
if by unbranded you mean the phone just has HTC and no other carrier lable on it then its most likely the Canadian version from Wind Mobile or Telus or Mobilicity. and as far as you downloading the RUUs have you renamed them to PH85IMG.zip before trying to flash them in bootloader? another easy way to find out what stock ruu you need is to check your HBOOT version on the boot loader so you can see what stock RUU's are compatible with it
Click to expand...
Click to collapse
Yes, I have already renamed RUUs each time before copying them to the SD card.
HBOOT 1.92.0000
eMMC-Boot
Feb 29 2012, 17:06:37
Could you tell me how to know which stock RUUs are compatible with the phone?
Note: I ran across this thread, but I don't actually know whether S-off and SuperCid would help me in my case or not. I don't want to put water into soil
My Cid is the same as his one, HTC_044.
Thank you for your appreciated help and time.
abdozoon said:
Yes, I have already renamed RUUs each time before copying them to the SD card.
HBOOT 1.92.0000
eMMC-Boot
Feb 29 2012, 17:06:37
Could you tell me how to know which stock RUUs are compatible with the phone?
Note: I ran across this thread, but I don't actually know whether S-off and SuperCid would help me in my case or not. I don't want to put water into soil
My Cid is the same as his one, HTC_044.
Thank you for your appreciated help and time.
Click to expand...
Click to collapse
I'd wait for a 2nd opinion to be sure, but the HBOOT looks like mine did on Gingerbread which is a US T-Mobile brand.
I'd also wait to get a working RUU on it before doing S-Off and super cid. But, once you do both, you'll be able to flash any carrier's RUU.
wolf_7669 said:
I'd wait for a 2nd opinion to be sure, but the HBOOT looks like mine did on Gingerbread which is a US T-Mobile brand.
I'd also wait to get a working RUU on it before doing S-Off and super cid. But, once you do both, you'll be able to flash any carrier's RUU.
Click to expand...
Click to collapse
I will try flashing other RUUs till the moment I get a second opinion.
Thank you Wolf.
Just figured out why the Asian RUU did not get flashed in the bootloader, as the package contains 4 bad files (CRC errors); you can see the 4 files in the attached screenshot.
One guy also had those bad crc errors before, Thread.
Therefore, the only solution to my problem is to s-off and supercid to get another RUU from other carriers to work.
The question is, is there anyway to s-off the phone from the bootloader?
Because the JuopunutBear method requires the phone to be on (operating normally), USB Debugging on, and fast boot off from power options.
Hope someone helps me.
Thanks all
EDIT: Just finished downloading the ruu from another mirror, Winrar does not show any errors!
will transfer it to SD, and retry.
wish me luck guys.
UPDATE: The phone is back to life again! Time to backup!
wait you were on GB i would have updated to ICS before trying to flash any custom roms, most roms are designed for android 4.0+ let me see if i can find u a stock GB RUU
---------- Post added at 09:22 AM ---------- Previous post was at 09:16 AM ----------
ohh okay didnt see you had it up and running, this time do an official update to ICS before trying to flash anymore roms, and always remember to do a NANdroid backup before flashing any and all roms, once you update to ICS you should S-OFF your phone and superCID it so this way next time you can restore to stock with any RUU from any carrier, good luck and happy flashing and dont forget to hit that thanks button for ppl that offer help/advice ^^
plz share the link for the Custom ROM
" Just finished downloading the ruu from another mirror, Winrar does not show any errors!"
can u plz share the link where u downloaded it from,i also tried to download it 10-11 times!!every time get a corrupt file,plz i need this file.if u can upload i will be so thankful.
---------- Post added at 02:35 PM ---------- Previous post was at 02:11 PM ----------
abdozoon said:
Just figured out why the Asian RUU did not get flashed in the bootloader, as the package contains 4 bad files (CRC errors); you can see the 4 files in the attached screenshot.
One guy also had those bad crc errors before, Thread
Therefore, the only solution to my problem is to s-off and supercid to get another RUU from other carriers to work.
The question is, is there anyway to s-off the phone from the bootloader?
Because the JuopunutBear method requires the phone to be on (operating normally), USB Debugging on, and fast boot off from power options.
Hope someone helps me.
Thanks all
EDIT: Just finished downloading the ruu from another mirror, Winrar does not show any errors!
will transfer it to SD, and retry.
wish me luck guys.
UPDATE: The phone is back to life again! Time to backup!
Click to expand...
Click to collapse
can u plz share the link where u downloaded it from,i also tried to download it 10-11 times!!every time get a corrupt file,plz i need this file.if u can upload i will be so thankful.
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.