Related
Hey Guys, I am stuck in Hboot. I tried downgrading with the RUU. I click on the volume up to update when it restarted I got an error. Now I am stuck in Hboot with s-on. Can anyone help. thanks
AD
Wish I new how to help u
Sent from my ThunderBolt using XDA App
jadsru1 said:
Hey Guys, I am stuck in Hboot. I tried downgrading with the RUU. I click on the volume up to update when it restarted I got an error. Now I am stuck in Hboot with s-on. Can anyone help. thanks
AD
Click to expand...
Click to collapse
You cannot downgrade with S-on, flash the MR1
Try to dl the ruu again on your computer. Check the md5sum after its done. Pull the SD card from your phone and user a card reader to put the new file on it (delete the old first obviously) then try again
Sent from my ADR6400L using XDA App
how exactly do you check the md5sum? lol
jyabor91 said:
how exactly do you check the md5sum? lol
Click to expand...
Click to collapse
http://www.softpedia.com/get/System/File-Management/MD5-Checker.shtml
You should always make sure the checksums match before flashing anything sensitive to your phone.
Did no one read what i said? Im pretty sure you cant downgrade with S-ON.. correct me if im wrong
xander0306 said:
Try to dl the ruu again on your computer. Check the md5sum after its done. Pull the SD card from your phone and user a card reader to put the new file on it (delete the old first obviously) then try again
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
I tried that. After checking the file The phone went straight to Hboot again. not sure what to do at this point. Yes S-on, I wasn't aware I wasn't supposed to do that. Sorry.
jadsru1 said:
I tried that. After checking the file The phone went straight to Hboot again. not sure what to do at this point. Yes S-on, I wasn't aware I wasn't supposed to do that. Sorry.
Click to expand...
Click to collapse
What rom were u on? Are you rooted? What did u do to get stuck in hboot? Did you ever try to get s off?
Sent from my ADR6400L using XDA Premium App
Hey I had a similar issue with my phone, first question does it give you a error on the Hboot screen saying security error? secondly it sounds like and correct me if I am wrong but it sounds like you probably had root and then used a full signed ruu to downgrade and if you did thats why your stuck at the moment. If that is what you did I am pretty sure you can recover from that so not all is lost. I am unclear on the exact steps your going to need to do to recover because the issue like the previous post says is that you cannot downgrade and if you flashed the mr1 ruu there is no newer version to flash to that is actually signed. Your next step is to go to the forum for thunderbolts in the general section and find the live chat (should be the first sticky), you want to talk to either Jcase or Adrenaline as they are best prepared with the knowledge to recover your device. I hope this helps at least get you pointed in the right direction.
balopez said:
Hey I had a similar issue with my phone, first question does it give you a error on the Hboot screen saying security error? secondly it sounds like and correct me if I am wrong but it sounds like you probably had root and then used a full signed ruu to downgrade and if you did thats why your stuck at the moment. If that is what you did I am pretty sure you can recover from that so not all is lost. I am unclear on the exact steps your going to need to do to recover because the issue like the previous post says is that you cannot downgrade and if you flashed the mr1 ruu there is no newer version to flash to that is actually signed. Your next step is to go to the forum for thunderbolts in the general section and find the live chat (should be the first sticky), you want to talk to either Jcase or Adrenaline as they are best prepared with the knowledge to recover your device. I hope this helps at least get you pointed in the right direction.
Click to expand...
Click to collapse
That's exactly what I did. I am getting a pink "security warning" on the Hboot screen as well.
To recap...I was running Tesla 1.7 upgraded to GB then tried downgrading by doing a complete reversion, using the MR1 custom ruu (like in the sticky)...that's where I got stuck. thanks for the help.
Bad download? Do you have a microsd reader? Load a fresh download and try again.
Sent from my ADR6400L using XDA App
WTF MATES!
Ok, so I probably should have done more research but I went to google and searched BY DATE for the most CURRENT INFO on rooting the phone. I got this site: http://www.goodandevo.net/2011/11/state-of-the-htc-evo-root-world-november-2011.html
I went by the HTC unlock method because the first link (revolutionary) didn't have my HBOOT version. Now, I'm suffering because of it because my fastboot doesn't come up any more. I get the message "Update Failed! Main Version is older!" So I went to this thread: http://forum.xda-developers.com/showthread.php?t=1239821
...and followed those instructions and...nothing worked. Is there any fix to this? Any help would be appreciated and sorry for being.... yes, a noob.
1- This is the wrong section
2- could you provide more info on your phone like what hboot version u have
If u are more specific you may have better luck...
Sent from my PG86100 using Tapatalk
Do you have a file called [PG86IMG.zip] still in the root of your SD card? It sounds like maybe you have an older update file that the phone wont use because you upgraded to the newest via the HTC Tool.
thank you very much, that's what it was. i removed the file and it worked
petrafan007 said:
thank you very much, that's what it was. i removed the file and it worked
Click to expand...
Click to collapse
Hit the thanks button as well.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
@petrafan007:
i am getting the same error
main version is old
what should i do
you wrote "thank you very much, that's what it was. i removed the file and it worked"
which file you removed i have done alot of research and i did everything according to the tutorial but this error msg comes please help me out
i have hboot 1.49.0009 i want to go to 1.49.0007
early reply is appreciated as i want to get it done at the earliest
amarsidhu said:
@petrafan007:
i am getting the same error
main version is old
what should i do
you wrote "thank you very much, that's what it was. i removed the file and it worked"
which file you removed i have done alot of research and i did everything according to the tutorial but this error msg comes please help me out
i have hboot 1.49.0009 i want to go to 1.49.0007
early reply is appreciated as i want to get it done at the earliest
Click to expand...
Click to collapse
If you mount your sdcard you should see one named PG86IMG.zip, you'll need to rename or delete it.
you mean to say i have to use another custom rom instead of the one i am using
PG86IMG
i am not being able to find the solution for this prob. i have done almost everything but still the same error pops up all the time. did it several time. first of all i am not being able to get the mmcblk0p31.img file.
i almost checked all the tutorials but no use i am still not being able to figure out that where i am going wrong.
---------- Post added at 05:36 AM ---------- Previous post was at 05:35 AM ----------
although ma phone is rooted and i have loaded the wifi tether titanium backup also but how to get the s-off done
hi , i try ti change my hboot 1.49.0018 to 1.49.0007 but in last stap when i try to flash PG86IMG.zip it says , main version is older!
please help
Wrong thread, sorry for posting.
raidraid said:
hi , i try ti change my hboot 1.49.0018 to 1.49.0007 but in last stap when i try to flash PG86IMG.zip it says , main version is older!
please help
Click to expand...
Click to collapse
If GSM is anything like CDMA, you're S-On and because the file you're trying is older it will not let you flash it. Good luck.
Sent from the 3Dimension.
ok but now it not start .
The reason you're getting stuck is because the bootloader automatically tries to load PG86IMG.zip if it exists on the sd card, the quick and dirty way around this is to remove the SD card, boot the phone up and but the card back when the phone has booted up.
"the main version is older" problem is due to the fact that before updating the timestamps on the hboot in the PG86IMG.zip(1.49.0007) and your current hboot (1.49.0009 or 1.49.0018) are compared, and as it turns out 1.49.0007 is the oldest of the bunch, so it gets rejected.
to get around the above mentioned problem (for the GSM version at least) follow the instructions in this thread http://forum.xda-developers.com/showthread.php?t=1471246 it basically changes the timestamp/versionID of the 1.49.0007 to trick the phone into downgrading.
The problem:
-My evo 3d keeps restarting at random times and when it restarts it sometimes dies during the booting up process, and i have to put in a new battery because when it boots up with the old battery it just says its at 10% or less.
this has happened a lot. PLEASE HELP
The specs:
Hboot 1.4
rom: http://forum.xda-developers.com/showthread.php?t=1620318 (Newts one)
please help. this is really irritating me.
I had the very same problem (on RC3). I later remembered that I just upgraded the radio to the latest version. Downgrading back to the radio in the 1.13 RUU (v0530) resolved the issue. My battery life dropped tremendously on the new radio as well.
On a side note, have you tried other ROMs since then? If it's happening in all ROMs it could be an issue there as well.
thefsfempire said:
I had the very same problem (on RC3). I later remembered that I just upgraded the radio to the latest version. Downgrading back to the radio in the 1.13 RUU (v0530) resolved the issue. My battery life dropped tremendously on the new radio as well.
On a side note, have you tried other ROMs since then? If it's happening in all ROMs it could be an issue there as well.
Click to expand...
Click to collapse
it has also done it on Meanrom 4.3,
where do i find the radio you placed that fixed the issue?
jlopez512 said:
it has also done it on Meanrom 4.3,
where do i find the radio you placed that fixed the issue?
Click to expand...
Click to collapse
Here: http://forum.xda-developers.com/showthread.php?t=1193101
Under downloads you'll see this: From the 1.13.651.7 OTA/RUU. Click the CDMA link (for 0.97.10.0530). Place this file on the root of your SD card (must be PG86IMG.zip - case sensitive!) and power on phone into bootloader mode (vol down + power). It'll verify and ask you to flash.
Be very careful doing this because you can potentially brick your phone if you don't know what you're doing. There are more detailed instructions at the thread at the beginning of this post. Post back here if you have any issues so I can help you out!
Good luck!
EDIT: If you have access to a computer, follow the "How To Flash" instructions at the link so you can verify the MD5 to make sure the download isn't corrupted.
thefsfempire said:
Here: http://forum.xda-developers.com/showthread.php?t=1193101
Under downloads you'll see this: From the 1.13.651.7 OTA/RUU. Click the CDMA link (for 0.97.10.0530). Place this file on the root of your SD card (must be PG86IMG.zip - case sensitive!) and power on phone into bootloader mode (vol down + power). It'll verify and ask you to flash.
Be very careful doing this because you can potentially brick your phone if you don't know what you're doing. There are more detailed instructions at the thread at the beginning of this post. Post back here if you have any issues so I can help you out!
Good luck!
EDIT: If you have access to a computer, follow the "How To Flash" instructions at the link so you can verify the MD5 to make sure the download isn't corrupted.
Click to expand...
Click to collapse
i have the current radio 0.97.00.0518, flashing this will be safe, right?
also, will it erase my phone data?
The radio version you have is from RUU 1.11 which is one of the oldest ones for this device. I'm curious to know how it's still there unless you've never done an OTA/Hboot downgrade.
It will not erase your handset, only updates the radio software which is a completely separate part of your phone. Just follow the instructions and read through them a few times. I've upgraded/downgraded my radio several times following those instructions.
thefsfempire said:
The radio version you have is from RUU 1.11 which is one of the oldest ones for this device. I'm curious to know how it's still there unless you've never done an OTA/Hboot downgrade.
It will not erase your handset, only updates the radio software which is a completely separate part of your phone. Just follow the instructions and read through them a few times. I've upgraded/downgraded my radio several times following those instructions.
Click to expand...
Click to collapse
my phone was hboot 1.3 when i got it so i used Revolutionary.io method lol
i hope this works, thank you so much!!
jlopez512 said:
my phone was hboot 1.3 when i got it so i used Revolutionary.io method lol
i hope this works, thank you so much!!
Click to expand...
Click to collapse
Good luck to you! Like I said, if you have an issue let me know! *Thread subscribed
thefsfempire said:
Good luck to you! Like I said, if you have an issue let me know! *Thread subscribed
Click to expand...
Click to collapse
my phone just restarted :/
jlopez512 said:
my phone just restarted :/
Click to expand...
Click to collapse
If it restarted after the radio update: flash the 2.17 RUU then downgrade hboot to 1.4 -OR- flash the 2.17 zip and remove the hboot file.
If it restarted during the radio update: (this is bad). The problem could be with a faulty battery. But that is the least of your problems now.
I'll get the link the 2.17 downloads for you. just a sec..
EDIT#1: Here is a link to the PG86IMG.zip for 2.17 containing the latest software and firmware. Delete the HBOOT file from the zip using WinRAR, 7Zip, etc. and rename zip file to PG86IMG.zip, move to root of SD and flash.
http://goo.im/stock/shooter/ruu/PG8...216_NV_NV_spcs_1.42_release_233304_signed.zip
EDIT#2: Here is the link to the actual RUU (run in Windows then do HBOOT downgrade): http://goo.im/stock/shooter/ruu/RUU...216_NV_NV_spcs_1.42_release_233304_signed.exe
---------- Post added at 09:08 PM ---------- Previous post was at 08:43 PM ----------
Just found this while helping someone else. Freeza posted an all-in-one firmware update package for those on Hboot 1.4. This updates you to all the firmware from the 2.17 package without losing root or S-OFF. This does NOT flash a ROM, just updates the firmware.
http://forum.xda-developers.com/showpost.php?p=21374142&postcount=131
thefsfempire said:
If it restarted after the radio update: flash the 2.17 RUU then downgrade hboot to 1.4 -OR- flash the 2.17 zip and remove the hboot file.
If it restarted during the radio update: (this is bad). The problem could be with a faulty battery. But that is the least of your problems now.
I'll get the link the 2.17 downloads for you. just a sec..
EDIT#1: Here is a link to the PG86IMG.zip for 2.17 containing the latest software and firmware. Delete the HBOOT file from the zip using WinRAR, 7Zip, etc. and rename zip file to PG86IMG.zip, move to root of SD and flash.
http://goo.im/stock/shooter/ruu/PG8...216_NV_NV_spcs_1.42_release_233304_signed.zip
EDIT#2: Here is the link to the actual RUU (run in Windows then do HBOOT downgrade): http://goo.im/stock/shooter/ruu/RUU...216_NV_NV_spcs_1.42_release_233304_signed.exe
---------- Post added at 09:08 PM ---------- Previous post was at 08:43 PM ----------
Just found this while helping someone else. Freeza posted an all-in-one firmware update package for those on Hboot 1.4. This updates you to all the firmware from the 2.17 package without losing root or S-OFF. This does NOT flash a ROM, just updates the firmware.
http://forum.xda-developers.com/showpost.php?p=21374142&postcount=131
Click to expand...
Click to collapse
i have another issue. my internet. i used to get error code 67, called sprint, and they refreshed my line and stuff. when i try to turn it on it goes as follows from the settings; "Turning on.." then after a few seconds it says "disconnected"
Ok where are you at right now? Are you still S-OFF? Are you on stock RUU or are you on Newts?
thefsfempire said:
Ok where are you at right now? Are you still S-OFF? Are you on stock RUU or are you on Newts?
Click to expand...
Click to collapse
Same, Newts, S-off
by the way, i flashed what you told me from the second edit. hasnt restarted since :')
I had a similar issue that turned out to be a hardware problem. Had to have sprint get me a new phone. The restarts kept happening more often and the phone was slightly hot. Then it just wouldn't turn on anymore.
Sent from my PG86100 using XDA
jlopez512 said:
Same, Newts, S-off
by the way, i flashed what you told me from the second edit. hasnt restarted since :')
Click to expand...
Click to collapse
Glad to hear your restarts have stopped. As far as internet, that was a known issue with earlier kernels. I have Chad's RLS5 kernel; PM me if you'd like it. It fixes lots of issues with WiFi, 3G connectivity, animations, etc.
Sometimes the random reboots are a hardware problem or a radio problem. I used to get them every once in a while but they stopped ever since I updated the radio and firmware to the 2.17 Fw. Freeza had posted an all-in-one radio/fw update that removed the hboot that could possibly work..
Sent from my PG86100 using XDA
thefsfempire said:
Glad to hear your restarts have stopped. As far as internet, that was a known issue with earlier kernels. I have Chad's RLS5 kernel; PM me if you'd like it. It fixes lots of issues with WiFi, 3G connectivity, animations, etc.
Click to expand...
Click to collapse
yeah sure, hopefully that is all it just needs
mreyesems said:
Sometimes the random reboots are a hardware problem or a radio problem. I used to get them every once in a while but they stopped ever since I updated the radio and firmware to the 2.17 Fw. Freeza had posted an all-in-one radio/fw update that removed the hboot that could possibly work..
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
isn't it the same one form page one, edit two?
I had this problem and the solution was much simpler -- pull your memory card out and see if the reboots stop.
If that's the problem, back up the card to a computer and long format it.
mreyesems said:
Sometimes the random reboots are a hardware problem or a radio problem. I used to get them every once in a while but they stopped ever since I updated the radio and firmware to the 2.17 Fw. Freeza had posted an all-in-one radio/fw update that removed the hboot that could possibly work..
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
I was also having issues with random reboots on my phone. These seemed to only be occurring while the phone was asleep (in my pocket, on a desk, etc...). I had somewhere on the order of 7-8 reboots in a 48 hour period. I also flashed the all-in-one radio/fw update that Freeza posted, and have had zero reboots while sleeping in the 72 hours since. I highly recommend flashing this all-in-one update if you are having issues with reboots while sleeping.
Ok so I got my phone s-off recently and was trying to flash the Team PkmN - Venasaur Rom v3.2.0. So after doing that i noticed that it would crash like every 5 minutes and I could never get any sound. I flashed the gingerbread patch and now it works fine. Now the question is my internal and external memory will not read but it was doing fine be fore I used the patch. So this makes me thing I'm running the Ginger bread firmware and not the 3.14 leak. But when I S-off'd it i used the 3.14 software because i thought that is what I had had because it was what was installed on my phone. So Is there any way to tell exactly what my phone is running. I have it S-off with hboot 2.21 and the PkmN rom installed. And also i saw a post on the S-off thread that had instructions to fix the internal and external memory will that work for me?
Sorry for the long post and thanks for the help.
Re-run the 3.14 ruu and reflash the rom
I have tried reflashing the ruu but for some reason every one that i download won't install and when i try and open it on the pc they all say they are invalid. and after trying to do the meomry fixes my phone will no longer connect to my network (So i have no service)....any advice for that? Or am I just screwed?
you can't run it as an .exe (Because it's not a real ruu)
it's a zip file, you must rename it to ph98img.zip and put it on your sd card and flash it from the bootloader... these instructions are all over the download links...
READ UP!
you're totally not screwed... all the info you need is here via search... but if you get antsy, join us on IRC and someone will be around to help out realtime.
I am well aware that it is a zip file and when i try and open the zip it tells me it is a invalid file on the computer. And how would one go about joining this IRC?
I'm on the IRC but could you maybe point me in the right direction for my problem on here? I've tried searching but since i don't really know what the problem is i don't know what to search.
....OK I'm an idiot apparently you have to put the back on the phone for it to work.....
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!