Related
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?
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
Hey guys, havent been on the forums in awhile, my buddy has an HTC One Max that he wanted to root/rom, we've had some trouble, was up to the new ROM however it wasn't getting service from sprint, pretty much wanted to go back to stock and just not worry about any of this, i have read through some of the RUU threads and such but im having a good amount of trouble. Could i get some help? i am able to send commands to the phone but cant get into anything else, keeps going to fastboot when phone is restart. believe it is locked in fastboot. Let me know any info you need.
I think you have re-locked your phone as of now. If you have re-locked it you need to run the RUU or flash the ROM.zip via hboot. you can find the RUU in couple of threads now..
while attempting to flash the RUU i continue to get the error FAILED (remote: 12 signature verify fail) Everything else seems to go fine until i get to that point.
asnpdirtezw said:
while attempting to flash the RUU i continue to get the error FAILED (remote: 12 signature verify fail) Everything else seems to go fine until i get to that point.
Click to expand...
Click to collapse
As pradeepvizz said you need to make sure your bootloader is Locked/Re-Locked to run the RUU it would also be good measure to have a stock Recovery installed.
DeadPhoenix said:
As pradeepvizz said you need to make sure your bootloader is Locked/Re-Locked to run the RUU it would also be good measure to have a stock Recovery installed.
Click to expand...
Click to collapse
I was sure to re-lock the unit, dont think i had flashed over a stock recovery now that i think about it, ill try that and get back to you.
asnpdirtezw said:
while attempting to flash the RUU i continue to get the error FAILED (remote: 12 signature verify fail) Everything else seems to go fine until i get to that point.
Click to expand...
Click to collapse
Do you mean you tried to flash it via command prompt on the PC?
That is correct, i managed to unlock it again so i could attempt to flash the stock recovery and see if i could flash the RUU that way but it keeps giving me an error.
asnpdirtezw said:
That is correct, i managed to unlock it again so i could attempt to flash the stock recovery and see if i could flash the RUU that way but it keeps giving me an error.
Click to expand...
Click to collapse
Weird because because I ruu the other day. But I'm also unlocked and soff
Sent from my HTC6600LVW using XDA Premium 4 mobile app
asnpdirtezw said:
That is correct, i managed to unlock it again so i could attempt to flash the stock recovery and see if i could flash the RUU that way but it keeps giving me an error.
Click to expand...
Click to collapse
well since you are unlocked again, i would suggest to go ahead and install an Custom ROM. I know you had problems with Sprint when you did if the first time, but do try again with the following checks
1. Make sure you get the proper ROM for your phone - i assume your phone is from Sprint and so download the Sprint variant and not the international or anything else.
2. Use TWRP recovery for flashing the ROM. we have had users reporting similar issues when CWM was used.
These are the steps i took to get the Kit Kat update.
I couldnt get the update OTA like most people and i was completely stock.
So if you are in a similar position these steps may help.
DO AT YOUR OWN RISK!
1. Unlock your bootloader and get root access. I did by following these instructions from this video.
Credits goes to sakitech.
https://www.youtube.com/watch?v=kJYAS2KN17Y&feature=youtu.be
2. Gain S-OFF by following these instructions from this video.
Credits goes to sakitech.
https://www.youtube.com/watch?v=NeFwsqU4YL4
3. After you have completed these steps successfully head over to @clsA thread and download the AT&T 4.4.2 OTAPkg.zip and the
stock Recovery_Cingular_US_3.17.502.3.img. Link to the thread http://forum.xda-developers.com/showthread.php?t=2659374
4. Place the downloaded .zip on the root your phone storage.
5. follow the steps in @clsA post and flash Recovery_Cingular_US_3.17.502.3.img via fastboot.
6. Navigate to recovery from fastboot on your HTC ONE. If you see "Mount SDCard failed" ignore it. goto to phone storage and locate the update.zip and flash it.
Click to expand...
Click to collapse
this worked for me, it should also work for anyone else.
ALL CREDITS goes to the creator of the video - sakitech and Senior Member here on xda clsA
Click to expand...
Click to collapse
r3al_0g said:
These are the steps i took to get the Kit Kat update.
I couldnt get the update OTA like most people and i was completely stock.
So if you are in a similar position these steps may help.
DO AT YOUR OWN RISK!
this worked for me, it should also work for anyone else.
Click to expand...
Click to collapse
So am I the only person who went into settings and Clicked AT&T update and got the 4.4.2 update that way. I have never had a phone in all my life tell me an update was ready. I always had to check manually about once or twice a week out of boredom. Did the same with my ONE last week and sure enough there was an update and it downloaded and installed fine.
Solarenemy68 said:
So am I the only person who went into settings and Clicked AT&T update and got the 4.4.2 update that way. I have never had a phone in all my life tell me an update was ready. I always had to check manually about once or twice a week out of boredom. Did the same with my ONE last week and sure enough there was an update and it downloaded and installed fine.
Click to expand...
Click to collapse
i have been clicking the check for update link at least 10 times a day since the update was released and i didnt get it ota i had to do it manually
If you're stock, you should be able to get the update just by changing the date. I brought my phone back to stock (3.17.502.3) then just kept hitting Software Update. If it didn't update, advance the date and try again. After a few date changes, the update was offered.
chp said:
If you're stock, you should be able to get the update just by changing the date. I brought my phone back to stock (3.17.502.3) then just kept hitting Software Update. If it didn't update, advance the date and try again. After a few date changes, the update was offered.
Click to expand...
Click to collapse
ok thanks for the info.. ill add it to the post if its not a prob
r3al_0g said:
These are the steps i took to get the Kit Kat update.
I couldnt get the update OTA like most people and i was completely stock.
So if you are in a similar position these steps may help.
DO AT YOUR OWN RISK!
this worked for me, it should also work for anyone else.
Click to expand...
Click to collapse
Will it work if you are running a custom recovery like TWRP?
ExcelonGT said:
Will it work if you are running a custom recovery like TWRP?
Click to expand...
Click to collapse
Custom recovery won't work.. U will have to b on stock 4.3 and S-OFF with stock recovery thats mentioned above..
Sent from my LG-D801 using Tapatalk
r3al_0g said:
Custom recovery won't work.. U will have to b on stock 4.3 and S-OFF with stock recovery thats mentioned above..
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
Anyone know if there are issues with S-Off and rooting since the update? I am 100% stock, non rooted, never installed a rom. Its been stock since the day I got it. I planned on getting the AT&T update to 4.4.2, rooting, making an update then testing some roms.
I know with other phones the update screwed some things up so I didn't know if rooting/s-off were an issue since the update.
Thanks ll!
Edit:
nevermind...found it: http://forum.xda-developers.com/showthread.php?t=2663122
So what exactly do we need to get OTA?
Stock recovery, android 4.3, locked bootloader?
I have all that, and still not finding an OTA update. Manually looking for the update, and I'm just not getting it.
lettuceman44 said:
So what exactly do we need to get OTA?
Stock recovery, android 4.3, locked bootloader?
I have all that, and still not finding an OTA update. Manually looking for the update, and I'm just not getting it.
Click to expand...
Click to collapse
unlocked bootloader, stock 4.3 and s-off, stock recovery.. download the ota place it on ur phone reboot into recovery and flash it.. that worked for me
r3al_0g said:
unlocked bootloader, stock 4.3 and s-off, stock recovery.. download the ota place it on ur phone reboot into recovery and flash it.. that worked for me
Click to expand...
Click to collapse
Oh, I meant from at&t over the air. I feel like I'm missing something, so trying to find out what the ota requirements are.
I can't flash it yet, I only have a windows 8.1 computer with usb 3.0 ports. Fastboot doesn't work.
lettuceman44 said:
Oh, I meant from at&t over the air. I feel like I'm missing something, so trying to find out what the ota requirements are.
I can't flash it yet, I only have a windows 8.1 computer with usb 3.0 ports. Fastboot doesn't work.
Click to expand...
Click to collapse
@chp recommend advancing your date and try and see if the update comes through. Try it a few times and see if it will work for you also
Sent from my LG-D801 using Tapatalk
Tried that with no luck. Had to do a factory reset because I went to far, and my OTA check was in -300 hours.
You guys are forgetting that to be able to update the OTA, you need to have an ACTIVE at&t sim card inserted to your phone. I think this is the reason for all the confusion around since not everybody lives in the US
Downgrade to 4.3
OK, so I was able to upgrade but now I messed it up trying to patch default.xml. :crying:
I am trying to revert to the 4.3 with RRU but I get error 155.
I am S-Off, HBOOT 1.56.
I tried with bootloader re-locked, unlocked, locked. I tried with stock recovery and with ClockWM recovery both locked and unlocked.
I also tried to re-apply the patch with stock recover but it fails verification...
Any ideas how do I go back or fix this?
Thanks
Adrian
Tutorial
How to Update HTC One AT&T android 4.4.2 and root:
http://forum.xda-developers.com/show...79356166999787
Gabe09196 said:
You guys are forgetting that to be able to update the OTA, you need to have an ACTIVE at&t sim card inserted to your phone. I think this is the reason for all the confusion around since not everybody lives in the US
Click to expand...
Click to collapse
i kinda figured n yea im not from the US so this was the only method that worked for me
agoyeneche said:
OK, so I was able to upgrade but now I messed it up trying to patch default.xml. :crying:
I am trying to revert to the 4.3 with RRU but I get error 155.
I am S-Off, HBOOT 1.56.
I tried with bootloader re-locked, unlocked, locked. I tried with stock recovery and with ClockWM recovery both locked and unlocked.
I also tried to re-apply the patch with stock recover but it fails verification...
Any ideas how do I go back or fix this?
Thanks
Adrian
Click to expand...
Click to collapse
The BEST way to make sure that you can run the RUU, whether it be the ATT version, or the Dev Edition is to make sure you downgrade the HBOOT to 1.44. You will never see than error again. No problems at all. Why on Earth though would you want the ATT version, when you can Dev it, and take the 4.4.2 OTA with no carrier BS?
hack14u said:
The BEST way to make sure that you can run the RUU, whether it be the ATT version, or the Dev Edition is to make sure you downgrade the HBOOT to 1.44. You will never see than error again. No problems at all. Why on Earth though would you want the ATT version, when you can Dev it, and take the 4.4.2 OTA with no carrier BS?
Click to expand...
Click to collapse
Thank you.
Actually that is what I did. After downgrading HBoot I was able to use the RRU.
Unfortunately I use my phone for work with Mobileiron and will flag it to IT if I'm rooted. I have tried a couple of workaround so but did not work very well. Every time I try to monkey with it IT starts getting emails every 30 min saying my device is not compliant and I am rooted.... So my best solution is to unlock boot loader and flash mods there. Which got me into this trouble....
I can't navigate to the recovery after I flashed Recovery_Cingular_US_3.17.502.3.img to install the OTA. I've tried going to recovery mode and then pressing Power + Vol. Up to no avail. Any help?
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.