Hi everyone,
I've found the information in these forums to be very helpful and have never posted on anything before, but I have a question that I'm not finding a good answer for.
I successfully unlocked my bootloader and rooted last night and am now running scrosler's CleanROM. However I want to return to stock using the RUU from here:
http://forum.xda-developers.com/showthread.php?t=1338916
When I run the RUU I am getting stuck at the HTC recovery screen, and the windows installer tells me that the RUU is not compatible. I tried extracting the rom.zip, renamed it to PH98IMG.zip, copied it to the SDcard and load it in HBOOT, but it won't work either.
Any ideas? I mainly just want to make sure I have a working method to return to stock just in case I accidentally brick the phone at some point, but otherwise I'm good for now.
You run the ruu from your pc if it's like other htcs
sent from my newly unlocked Rezound
phackney said:
Hi everyone,
I've found the information in these forums to be very helpful and have never posted on anything before, but I have a question that I'm not finding a good answer for.
I successfully unlocked my bootloader and rooted last night and am now running scrosler's CleanROM. However I want to return to stock using the RUU from here:
http://forum.xda-developers.com/showthread.php?t=1338916
When I run the RUU I am getting stuck at the HTC recovery screen, and the windows installer tells me that the RUU is not compatible. I tried extracting the rom.zip, renamed it to PH98IMG.zip, copied it to the SDcard and load it in HBOOT, but it won't work either.
Any ideas? I mainly just want to make sure I have a working method to return to stock just in case I accidentally brick the phone at some point, but otherwise I'm good for now.
Click to expand...
Click to collapse
You need to have a recovery backup. Then you can always go back.
Sent from my Galaxy Tab 10.1
Neither of these answers attempt to address the issue of why the RUU doesn't work.
Have you tried both?
sent from my newly unlocked Rezound
Here's a more specific account of what happens when I run the RUU.
I get the progress bar that says "Sending......." but then after a few seconds I get the following error:
Error [155] unknown error
The ROM Update Utility cannot update your Android phone
Please get the correct ROM Update Utility and try again
I've spent the last hour Googling this error and have found that it is a known error with other HTC devices but can't find any info on the Rezound.
Found this helpful thread for a similar issue with the Desire:
http://forum.xda-developers.com/showthread.php?t=1029401
Tried starting the RUU with the phone already in fastboot but that didn't change anything.
What does it do when you copy the zip to the sd card and run it?
marclile said:
What does it do when you copy the zip to the sd card and run it?
Click to expand...
Click to collapse
I get the little progress bar in the upper right corner of HBOOT that shows it is reading the file, however it doesn't present me with the option to flash it. Instead it just skips to the HBOOT menu.
phackney said:
I get the little progress bar in the upper right corner of HBOOT that shows it is reading the file, however it doesn't present me with the option to flash it. Instead it just skips to the HBOOT menu.
Click to expand...
Click to collapse
Interesting, I wonder if anyone has ran it this ruu successfully
Solved
Figured it out. On a hunch I re-locked the bootloader and tried running the RUU using the Windows installer and it worked. It must be some sort of security check thing. I'll just unlock the bootloader again after it's done flashing. It might be good for someone with more seniority on the forum to make this information more visible in case anyone else runs into this issue.
phackney said:
Figured it out. On a hunch I re-locked the bootloader and tried running the RUU using the Windows installer and it worked. It must be some sort of security check thing. I'll just unlock the bootloader again after it's done flashing. It might be good for someone with more seniority on the forum to make this information more visible in case anyone else runs into this issue.
Click to expand...
Click to collapse
I agree. It probably needs to be added to the post that has the ruu files and it.
Glad you got it working.
Sent from my Galaxy Tab 10.1
marclile said:
I agree. It probably needs to be added to the post that has the ruu files and it.
Click to expand...
Click to collapse
Can you make that happen?
phackney said:
Can you make that happen?
Click to expand...
Click to collapse
i can't change the post but i'll post something in that thread.
Any idea on how to get the phone to relock if "fastboot oem lock" goes to "waiting for device" without responding?
I'm in a similar situation, but I cannot seem to get my phone to relock.
Nevermind. I forgot to get into bootloader mode via adb.
phackney said:
Figured it out. On a hunch I re-locked the bootloader and tried running the RUU using the Windows installer and it worked. It must be some sort of security check thing. I'll just unlock the bootloader again after it's done flashing. It might be good for someone with more seniority on the forum to make this information more visible in case anyone else runs into this issue.
Click to expand...
Click to collapse
Thank you. Had the same error. Felt like an idiot when I read your post. Can't believe I didn't think of that first.
So how do you re-lock? Thanks
Fastboot oem lock
Sent from my ADR6425LVW using XDA
10 characters
Related
Trying to get the RUU to install and not having any luck. I have relocked the bootloader and start the RUU but either it reports and error after erasing the user data or it says it is sending, but there is never any progress. I have let it run for over 30 minutes with no luck. I have tried unlocking and relocking the bootloader with no luck. In fact, now it is always reporting an error and I haven't been able to get it to get to the sending screen.
I originally unlocked/rooted using RegawMOD script. I followed all the instructions and videos on reinstalling the RUU I could find. The RUU I have matches the version number on the phone so I'm guessing I have the correct RUU.
Anyone have any suggestions short of having an "accident" and getting an insurance replacement?
EDIT: I have found that by unlocking the phone again, I can get the phone to boot back up so all is not lost. I am restoring a backup so until I can get this fixed, the phone is still usable.
EDIT 2: Was finally able to get the RUU to run. Not sure what change allowed it to work but I ran it on a different computer that did not have the HTC drivers on already and ran the RUU file from the same directory where the fastboot.exe was located. I seemed to remember reading about someone else having success running RUU from the fastboot location so my guess would be that was the trick.
Drop it off a building.
-Cupper- said:
Drop it off a building.
Click to expand...
Click to collapse
I asked for solutions other than an "accident".
edboston said:
I asked for solutions other than an "accident".
Click to expand...
Click to collapse
Oops misread
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 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!
Hi,
I am new here and this is my first post so forgive me if starting a new thread for this topic was wrong but I found my own situation slightly different from the others here who had the same problem.
I have a gsm unlocked rezound and was trying to get rid of the unknown sim error message at lock screen. I followed the steps mentioned on this thread --> http://forum.xda-developers.com/showthread.php?t=1882355. I rooted the phone, downloaded the apk. Deleted the .odex file and replaced the existing apk with the downloaded one and rebooted. Now, I am stuck at the lock screen with no icons. But for the other people who faced similiar issue, they were able to open the home screen. I can't. I can see pop ups for sms/mail. I get ring when a call comes in but I cant pick. I tried hard reset. Tried booting without sim/sd card. Still no luck. I tried connecting the phone to my pc but now my pc wont recognise the phone when its connected. I can see icon on top of the phone which says USB connected and I also see sync icon, but it will not go any further. I dont know how to get into the phone's menu now.
I may have bitten more than I can chew, silly me :crying:
If you guys can help me in any way, I would appreciate that a lot.
OS : 4.0.3 ICS Running HTC Sense 3.6.
A quick fix:
http://forum.xda-developers.com/showthread.php?t=2017932
Flash my debloater, choosing the Sense option(will be brought to a widget removal screen if you don' use them all) & AOSP lockscreen. Disadvantage to that though, you will have to unlock to see the caller id when it rings.
Snuzzo said:
A quick fix:
http://forum.xda-developers.com/showthread.php?t=2017932
Flash my debloater, choosing the Sense option(will be brought to a widget removal screen if you don' use them all) & AOSP lockscreen. Disadvantage to that though, you will have to unlock to see the caller id when it rings.
Click to expand...
Click to collapse
Thank you for the quick response. I have downloaded the file. I know this sounds stupid but I am a real rookie. I don't know how to do the flashing or how to get to the AOSP lock screen. If you could guide me through the process or maybe give me a link where I can learn it myself, it would be great.
Essentially since you already have rooted, you will(should) also have a custom recovery (TWRP, AmonRa, CWM). Install it as you would a regular rom but without any wipes until after flash of the zip. Dependent on which recovery you will want to look up their FAQ/QnA on how to wipe dalvik/cache.
Once you get inside the script, you will see what I meant by "Choose Sense & AOSP Lockscreen".
Snuzzo said:
Essentially since you already have rooted, you will(should) also have a custom recovery (TWRP, AmonRa, CWM). Install it as you would a regular rom but without any wipes until after flash of the zip. Dependent on which recovery you will want to look up their FAQ/QnA on how to wipe dalvik/cache.
Once you get inside the script, you will see what I meant by "Choose Sense & AOSP Lockscreen".
Click to expand...
Click to collapse
Yes the phone was rooted, but I used a rooting software from google apps from the phone. After I downloaded that app, it rooted the phone and brought in an extra icon. I remember it as SU root something, but I didnt do it from the pc. So I dont have any recovery on the pc. I used to sync the phone with htc sync. Unfortunately, right now, my pc wont recognise the phone. I tried root explorer for android from pc, it wont recognise the device. HTC sync too will not. But my phone seems to know when a USB is connected, it brings the usb icon on top but thats about it. ((
Ok, best suggestion at this point is to follow the instruction in the OP for installing TWRP in the Rezound development section.
Snuzzo said:
Ok, best suggestion at this point is to follow the instruction in the OP for installing TWRP in the Rezound development section.
Click to expand...
Click to collapse
Could you kindly provide me a link to the right topic. Do you think my phone is beyond repair ? Have I bricked it ?
I am running 4.0.3 ICS on Sense 3.6
http://forum.xda-developers.com/showthread.php?t=1902381
You are far FAR from being bricked. Softbricked yes, hardbricked no.
Snuzzo said:
http://forum.xda-developers.com/showthread.php?t=1902381
You are far FAR from being bricked. Softbricked yes, hardbricked no.
Click to expand...
Click to collapse
Thank you for the help buddy. I am glad you said its not. I dont know what I would have done if it had. This is my first android phone and I took it a week back. I was beginning to miss my iPhone . Unfortunately the link you provided wont help me because I have no way of restarting phone other than by removing battery. Even when in fastboot, the pc does not recognise the device even when device shows fastboot usb. I doubt if I can get past step 1 in that link.
I found that I am on Vigor H Boot 2.27.000 and Radio 2.22.10.0803r with S-ON. I tried to turn S-Off after reading and educating myself on android from this forum till now. But even to S-Off, I need to be able to enable USB in debug mode which I am not able to. Any suggestions ?
Device still not fixed
hi,
I took the phone to a couple of places to check if it can be fixed, No one was able to fix it thus far, Any other advice or suggestions to fix this would be great. Any admins/mods have something to add ? Please, I am desperate to fix this phone. Anyway of doing this ?
Have you tried flashing a different rom?
If he's S-on and locked, he can simply flash the latest RUU can't he(just to get the phone working again). From there someone can help him set up adb, and s-off.
Sent from my ADR6425LVW using xda app-developers app
From what they posted, somehow they don't have a custom recovery even though they are rooted?
Can you put a PH98IMG.zip file of a recovery (either Amon Ra or TWRP) on your SD card and flash it in hboot? Then flash a custom ROM the same way from recovery.
You can take the SD card out and mount it on your pc and use your pc to copy over the recovery PH98IMG.zip file.
And oh yeah, I see what Obaterista... was saying. You should be able to flash the latest RUU from hboot. Here's a link for it:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
That's global too, which seems to be what you'll need.
jon7701 said:
Have you tried flashing a different rom?
Click to expand...
Click to collapse
Yes I have vigor, tried AmonRa, that did not work mate. It starts fastboot, gets stuck @ unpacking PH98IMG.diag and then nothing happens.
Obaterista93 said:
If he's S-on and locked, he can simply flash the latest RUU can't he(just to get the phone working again). From there someone can help him set up adb, and s-off.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
The bootloader screen says S-On. On top it says ***Tampered*** and below it ***UNLOCKED***.
feralicious said:
From what they posted, somehow they don't have a custom recovery even though they are rooted?
Can you put a PH98IMG.zip file of a recovery (either Amon Ra or TWRP) on your SD card and flash it in hboot? Then flash a custom ROM the same way from recovery.
You can take the SD card out and mount it on your pc and use your pc to copy over the recovery PH98IMG.zip file.
And oh yeah, I see what Obaterista... was saying. You should be able to flash the latest RUU from hboot. Here's a link for it:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
That's global too, which seems to be what you'll need.
Click to expand...
Click to collapse
Yes I rooted from a tool I found on android market. Noob me. So I do not have a recovery. I had downloaded the PH98IMG.zip and put it in my sd card and tried. The recovery starts and then shows a red exclamation and then nothing happens.
I was just trying different pages for help. Someone has mentioned that I should add the PH98IMG.zip as just PH98IMG and I shud not add the .zip. Thats the only thing left to try. I will post what happens when I do that.
lllR2-D2lll said:
Yes I have vigor, tried AmonRa, that did not work mate. It starts fastboot, gets stuck @ unpacking PH98IMG.diag and then nothing happens.
The bootloader screen says S-On. On top it says ***Tampered*** and below it ***UNLOCKED***.
Yes I rooted from a tool I found on android market. Noob me. So I do not have a recovery. I had downloaded the PH98IMG.zip and put it in my sd card and tried. The recovery starts and then shows a red exclamation and then nothing happens.
I was just trying different pages for help. Someone has mentioned that I should add the PH98IMG.zip as just PH98IMG and I shud not add the .zip. Thats the only thing left to try. I will post what happens when I do that.
Click to expand...
Click to collapse
What you'll have to do is relock your boot loader, flash the RUU and then unlock again. From there you should be able to flash a recovery and flash a rom.
Sent from my ADR6425LVW using xda app-developers app
My phone is also soft bricked. I relocked the phone and now it just sits in hboot and won't do anything no matter if I yet to flash the ruu zip file or use the exe ruu.
Currently
Relocked
Hboot 2.10.0000
Believe I am 4.03.605.2 main version, at least that's what the exe file said.
I'm pulling my hair out just trying to any software installed. Help please!
Sent from my SCH-I535 using xda app-developers app
1967ls2 said:
My phone is also soft bricked. I relocked the phone and now it just sits in hboot and won't do anything no matter if I yet to flash the ruu zip file or use the exe ruu.
Currently
Relocked
Hboot 2.10.0000
Believe I am 4.03.605.2 main version, at least that's what the exe file said.
I'm pulling my hair out just trying to any software installed. Help please!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Are you trying with the stock ROM ? If ure saving stock ROM as PH98IMG.zip, then try PH98IMG without the .zip typed in.
Obaterista93 said:
What you'll have to do is relock your boot loader, flash the RUU and then unlock again. From there you should be able to flash a recovery and flash a rom.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Thanks a tonne. That helped. I am back in the menu now. I am so grateful for ure help. But my problems dont seem to end just yet. Now, my htc sync wont detect the phone. The phone is relocked. I will try unlocking and see if it works, but is that the cause ?
lllR2-D2lll said:
Are you trying with the stock ROM ? If ure saving stock ROM as PH98IMG.zip, then try PH98IMG without the .zip typed in.
Click to expand...
Click to collapse
I'm trying to install any Rom. I find can of it is ics or gb. Nothing will load.
Sent from my SCH-I535 using xda app-developers app
1967ls2 said:
I'm trying to install any Rom. I find can of it is ics or gb. Nothing will load.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I am no expert to give u any suggestions but maybe if you could explain how it got bricked in the first place, someone might be able to give u a better solution mate.
Hello. Never made a thread before and was really hoping I wouldn't have to or would find an answer elsewhere.
Since that didn't work out, here's my problem:
Background: Evo 3d, virgin mobile, unlocked bootloader, s-off, hboot was at 1.50, and I don't remember what the radio was at. I was running CM11 and was quite happy until two days ago when I stopped receiving texts! No clue why, just stopped. Hangouts, etc etc. Called VM and they had no idea why that was happening either. Tried switching roms, reinstalling backups, etc etc. Clean wipes and all. Then I saw someone said they had to [for some reason] reinstall everything stock and then they had messaging back. So that's what I set out to do.
In Between: Used the RUU that I'm fairly certain came with my phone. Everything was good, it erased everything, and "updated system" and signatures. It was almost finished when BAM, popped up with error 152 Image Update Error; right at the very end. Quite disappointing. Tried it multiple times again with the same result. Not sure what to do.
Current: Only screen I can see (looks like shortened bootloader screen) says "***locked***" at the top, hboot 1.57.0000, radio 1.06.00.126, then says openADSP-v02.6.0.2226.00.0217eMMc-boot
Also tried flashing the unlock_code.bin, and while it took it, it changed nothing. One screen I did see very briefly but cannot replicate said that everything was there except system. Not really sure how to take that or what to do. Any and all help would be helpful. As is it sits on the HTC screen with exclamation points in each corner. When unplugged from usb it gives me that above screen. Removing battering and restarting to bootloader still gives the same screen.
Did you run ruu through windows or pg86img.zip?
Sent from my Evo 3D CDMA using xda app-developers app
hossman said:
Did you run ruu through windows or pg86img.zip?
Sent from my Evo 3D CDMA using xda app-developers app
Click to expand...
Click to collapse
Through Windows; the RUU exe.
SammyMak said:
Through Windows; the RUU exe.
Click to expand...
Click to collapse
You can try this
https://www.dropbox.com/s/d4baafpgchgg4ef/ruu-PG86IMG.zip
Put that on the root of your SD card and rename to pg86img.zip
Make sure its the only one there
Boot to boot loader and accept updates
It may reboot itself to bootloader, if it asks to accept again then accept
When its done reboot your phone
Rename or remove the file when done
Hope that helps
Sent from my Evo 3D CDMA using xda app-developers app
So I have my phone working now. I think it was the RUU.exe that I was using. I downloaded a different one from here http://androidruu.com/Shooter/ after much googling. That finally restored it to original VM stock rom etc. I couldn't use your method of placing the zip onto the root of my SD because despite it being there, it wouldn't go through the normal search for the file. I would remove the battery, put it back in, use the button key combo to try and open to bootloader, and it would go but it would be the page with the status and then it would instantly go back to the black screen with HTC logo.
Thank you for your help though!
Also I'm not sure how useful exactly this will be for anyone else, but if you find yourself ruu'd and needing better files...
The hboot ENG 1.04 I got from here: http://forum.xda-developers.com/showthread.php?t=1817513
ALL other downloads of that hboot did not work AT ALL.
I got the updated radio from here: http://androidforums.com/cdma-evo-3d-all-things-root/648902-radios-hboot-firmware-all-downloads.html
The hboots on that site however are stock and most likely won't run the custom roms as well, if at all, as 1.04.
SammyMak said:
I got the updated radio from here: http://androidforums.com/cdma-evo-3d-all-things-root/648902-radios-hboot-firmware-all-downloads.html
But the hboots on the site aren't helpful fyi
Click to expand...
Click to collapse
Hey, that's my thread. Just curious what you mean by the hboots aren't helpful?
If there is a problem I'm unaware of, I'd be happy to know what it is so I can get it squared away.
hossman said:
You can try this
https://www.dropbox.com/s/d4baafpgchgg4ef/ruu-PG86IMG.zip
Put that on the root of your SD card and rename to pg86img.zip
Make sure its the only one there
Boot to boot loader and accept updates
It may reboot itself to bootloader, if it asks to accept again then accept
When its done reboot your phone
Rename or remove the file when done
Hope that helps
Sent from my Evo 3D CDMA using xda app-developers app
Click to expand...
Click to collapse
thank you!
Brian706 said:
Hey, that's my thread. Just curious what you mean by the hboots aren't helpful?
If there is a problem I'm unaware of, I'd be happy to know what it is so I can get it squared away.
Click to expand...
Click to collapse
I must apologize! I seem to have mis stated that; they are helpful with regards to them being the stock hboots. However in my particular case those stock hboots weren't for me. I'll edit that here in a sec, but if I was going back to full stock I'd definitely use your stock VM hboot and it would be helpful in that case. Hope that makes sense, no disrespect meant!
SammyMak said:
I must apologize! I seem to have mis stated that; they are helpful with regards to them being the stock hboots. However in my particular case those stock hboots weren't for me. I'll edit that here in a sec, but if I was going back to full stock I'd definitely use your stock VM hboot and it would be helpful in that case. Hope that makes sense, no disrespect meant!
Click to expand...
Click to collapse
Thanks for clarifying that! I see what you meant now.
No worries, I didn't take offense or think you were disrespectful; I just wanted to make sure the downloads were working properly!
And for the record, the stock hboots will work just fine with custom roms. Hboot 1.50 for example will be compatible with the same selection of roms as JuopunutBear 1.50.5050. The difference is that JuopunutBear is patched and will allow for extra fastboot commands and allow them to be run on a locked bootloader.
The eng 1.04 hboot allows for extra fastboot commands that the stock hboot cannot. But you can boot any rom out there on the stock hboots. I've used stock 1.50 forever on this device.