Related
Good evening. I am new to HTC phones (and unlocked phones in general). I am having trouble flashing a kernel using a PH98IMG.zip file. When it goes in the bootloader I get an error that says "Main Version Older Update Failed." I am able to flash a boot.img via Fastboot, but I am receiving wifi errors. Does anyone have any ideas?
Thanks in advance.
Chris
CHRIS42060 said:
Good evening. I am new to HTC phones (and unlocked phones in general). I am having trouble flashing a kernel using a PH98IMG.zip file. When it goes in the bootloader I get an error that says "Main Version Older Update Failed." I am able to flash a boot.img via Fastboot, but I am receiving wifi errors. Does anyone have any ideas?
Thanks in advance.
Chris
Click to expand...
Click to collapse
What kernel are you trying to flash?
Sent from my ADR6425LVW using XDA App
How weird that someone else would post the same issue I'm having, when I've flashed several kernels in the past few days with no problems.
At some point, I've flashed every Sense-based kernel in the Rezound dev section. And now, for some strange reason, I'm getting the error described above.
Any ideas?
Thanks,
The Beeb
I'm going to guess you flashed the leak? If you did here is another thread to check out http://forum.xda-developers.com/showthread.php?t=1446273
sent from my newly unlocked Rezound
nosympathy said:
What kernel are you trying to flash?
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
I think I have tried just about every stock kernel, and gotta the error.
pwned3 said:
I'm going to guess you flashed the leak? If you did here is another thread to check out http://forum.xda-developers.com/showthread.php?t=1446273
sent from my newly unlocked Rezound
Click to expand...
Click to collapse
No I never flashed the leak. Do you think that fixed would work? Well guess I should say if it doesn't work do you think it will cause any harm to the phone's system?
Thanks again.
Sent from my ADR6425LVW using Tapatalk
CHRIS42060 said:
I think I have tried just about every stock kernel, and gotta the error.
No I never flashed the leak. Do you think that fixed would work? Well guess I should say if it doesn't work do you think it will cause any harm to the phone's system?
Thanks again.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Try flashing the kernel in fastboot.
I am having the same issue now also after I flash the BAMF's latest ROM. Their update log says they updated to the new base, and after that I can't to flash anything in hboot anymore. I can still ADB push the boot.img but no flashing. I also tried to revert to complete stock by flashing the RUU and get the same thing. It's says my system is newer and won't flash.
jskolm said:
I am having the same issue now also after I flash the BAMF's latest ROM. Their update log says they updated to the new base, and after that I can't to flash anything in hboot anymore. I can still ADB push the boot.img but no flashing. I also tried to revert to complete stock by flashing the RUU and get the same thing. It's says my system is newer and won't flash.
Click to expand...
Click to collapse
So you can't fastboot flash boot <boot.img> from your PC??
MrSmith317 said:
So you can't fastboot flash boot <boot.img> from your PC??
Click to expand...
Click to collapse
Sorry, yes, I can do that.
That's the only way that I can push a boot.img now. I know the kernel devs have a way to flash their kernel in recovery then automatically push you into hboot to flash the PH98IMG.zip file with the boot.img inside it. Flashing anything in fastboot now results in the error message above except for the BAMF ROM.
Having the same problem after updating to bamf cubed 102.
My main version sig updated when I flashed the leaked kernel. fastboot should always work, and would have saved me from the dumb mistake had i flashed in fastboot to begin with.
But my guess is that somehow u flashed a PH98IMG.zip file that was the leaked kernel.
I'm not sure how to find out what version the sig thinks it is running but since I know what the leak was, I can edit the .txt file in the PH98IMG.zip and make it work, like said in the thread.
Well this sucks! It definitely started when I flashed the new bamf cubed rom. So does this mean I can never flash a boot.img unless I do it with fastboot and a pc? So I cant just put the file on my sdcard and reboot into fastboot? Can this be fixed? Thanks!!!!
maniac2k said:
Well this sucks! It definitely started when I flashed the new bamf cubed rom. So does this mean I can never flash a boot.img unless I do it with fastboot and a pc? So I cant just put the file on my sdcard and reboot into fastboot? Can this be fixed? Thanks!!!!
Click to expand...
Click to collapse
The same issue also started for me when I flashed BAMF Cubed. Looks like dsb mention on the BAMF Cubed Rom thread that with S-On we can't easily change the base that was changed this with update. Looks like we will be using Fastboot until more developers use the newer version. Glad to know its not something I managed to screw up lol.
http://forum.xda-developers.com/showthread.php?t=1443328&page=5
Thanks a lot for all of the help everyone.
You might be able to replace the android-info.txt in the PH98IMG.zip with the one from dsb's kernel, making the hboot think you're not flashing backwards. Not positive if that works though.
skourg3 said:
You might be able to replace the android-info.txt in the PH98IMG.zip with the one from dsb's kernel, making the hboot think you're not flashing backwards. Not positive if that works though.
Click to expand...
Click to collapse
This does work, but you have to pull the file from his cube1.02 ROM not from his kernel.
jskolm said:
This does work, but you have to pull the file from his cube1.02 ROM not from his kernel.
Click to expand...
Click to collapse
How exactly is this done?
**** someone needs to tell dsb or whoever to put it back to the old version. If your mainver gets updated, you can't run RUUs. So you could be stuck with a brick until we get the official ICS RUU
con247 said:
**** someone needs to tell dsb or whoever to put it back to the old version. If your mainver gets updated, you can't run RUUs. So you could be stuck with a brick until we get the official ICS RUU
Click to expand...
Click to collapse
YEP! I can't RUU back to stock at this point... it's ok... I will deal with it until we get an official ICS RUU, but it's just a bummer incase something does actually go wrong with my Rezound.
con247 said:
**** someone needs to tell dsb or whoever to put it back to the old version. If your mainver gets updated, you can't run RUUs. So you could be stuck with a brick until we get the official ICS RUU
Click to expand...
Click to collapse
my main sig updated, and it is far from a brick..
Infact it's not a very big deal at all, it's something that should be avoided by all costs I absolutely 100% agree with that.
but the phone will still be able to use RUU's, the update will be ICS anyway..
This is confirmed by jcase.
I completely agree with stopping this from happening to anyone else. But no need to scare them by saying your phone is a brick because the sig updated.
How exactly do you consider the phone to be a brick anyway? JW, not trying to be an a-hole by any means here.
the only problem is the need to change the PB98IMG.zip .txt file and cant use an RUU until we get an OTA, ICS will be the next OTA update anyway.
---------- Post added at 01:45 PM ---------- Previous post was at 01:43 PM ----------
jskolm said:
YEP! I can't RUU back to stock at this point... it's ok... I will deal with it until we get an official ICS RUU, but it's just a bummer incase something does actually go wrong with my Rezound.
Click to expand...
Click to collapse
Just Curious, what do you need the RUU for?
do you use Stock ROM?
also, can't you just pull the rom.zip from ruu then rename to PB98IMG.zip and replace the.txt?
andybones said:
my main sig updated, and it is far from a brick..
Infact it's not a very big deal at all, it's something that should be avoided by all costs I absolutely 100% agree with that.
but the phone will still be able to use RUU's, the update will be ICS anyway..
This is confirmed by jcase.
I completely agree with stopping this from happening to anyone else. But no need to scare them by saying your phone is a brick because the sig updated.
How exactly do you consider the phone to be a brick anyway? JW, not trying to be an a-hole by any means here.
the only problem is the need to change the PB98IMG.zip .txt file and cant use an RUU until we get an OTA, ICS will be the next OTA update anyway.
---------- Post added at 01:45 PM ---------- Previous post was at 01:43 PM ----------
Just Curious, what do you need the RUU for?
do you use Stock ROM?
also, can't you just pull the rom.zip from ruu then rename to PB98IMG.zip and replace the.txt?
Click to expand...
Click to collapse
Agreed that it's FAR from bricked, but it's just more of an annoyance. You can't use the easy flash script that all the kernel devs and ROM devs are using now. You have to manually update the .txt file yourself inoder to be able to flash it. (Or adb push it from a computer)
And yes you are correct about the RUU, you can probably just replace the txt file in it with the moded version (I didn't think of trying that even though I am doing that will the kernels that I have download from here).
I was only trying to RUU to see if it would undo what was done... just for ease of use for me. I like to browse these forums from tapatalk and download a new kernel when it's released (hasn't been for a while, come on devs ) and test it out. I can't do that now without a computer. So I was just trying to undo that is all.
Before I begin, I've read through a lot of threads on different forums and have yet to find a solution (that's working for me.)
I could never get my device to S-OFF so simply dropped the task. Not in too big of a rush right now. That being said, I'd like to go back to GB for a bit just to try a few things out.
I never flashed the ICS firmware, therefor I've had to use the old firmware patches. So, I tried running the RUU for GB and it only encountered error after error and my phone stayed at the black HTC screen. Any ideas?
Phone works just fine, just rebooted while I was typing this post and went straight into my ROM.
Only way I found is S-off'd, I had to go back to GB after ICS since it came on the phone I bought and needed to return it. Everyone told me I had to S-Off then RUU
If s on make sure you relock bootloader, then you should be able to run the gb ruu for whichever version you were on.
Sent from my Rezound
Downgrading radios when s-on could very well hard brick your phone. I strongly recommend that you s-off first.
Sent from my ADR6425LVW using Tapatalk 2
Abu-7abash said:
Downgrading radios when s-on could very well hard brick your phone. I strongly recommend that you s-off first.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
You can't downgrade with s on....
Sent from my Rezound
ericsignals said:
If s on make sure you relock bootloader, then you should be able to run the gb ruu for whichever version you were on.
Sent from my Rezound
Click to expand...
Click to collapse
ericsignals said:
You can't downgrade with s on....
Sent from my Rezound
Click to expand...
Click to collapse
Are you even the same guy?
Sent from my ADR6425LVW using Tapatalk 2
Pick a Gingerbread based rom and flash. Try out Chingy's Ineffabilis gingerbread.
Chyrux said:
I never flashed the ICS firmware, therefor I've had to use the old firmware patches.
Click to expand...
Click to collapse
Wish you guys would read.
Abu-7abash said:
Are you even the same guy?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
If you never ran an ics ruu you still were on gb firmware....so you can run a gb ruu. When you run the same ruu that's not downgrading....sheesh :rolleyes . And its probably the easiest way to get back to a working phone if you are lost and don't really know what you are doing.
Sent from my Rezound
ericsignals said:
If s on make sure you relock bootloader, then you should be able to run the gb ruu for whichever version you were on.
Sent from my Rezound
Click to expand...
Click to collapse
Tried that. RUU said "Could not update your phone at this time."
I came from stock GB originally in...April. Is there a specific RUU for that?
I've never used RUU's before so I'm lost.
aaand now, I'm pretty sure my phone is a brick. It's re-locked now, can't go into recovery, won't boot into ROM.
Chyrux said:
aaand now, I'm pretty sure my phone is a brick. It's re-locked now, can't go into recovery, won't boot into ROM.
Click to expand...
Click to collapse
Still only a soft brick. Would suggest trying the other of the two GB RUU .exe version packages if you only tried one of them, just a suggestion until someone else can help you and diagnose.
http://forum.xda-developers.com/showthread.php?p=19756694
Chyrux said:
aaand now, I'm pretty sure my phone is a brick. It's re-locked now, can't go into recovery, won't boot into ROM.
Click to expand...
Click to collapse
If you can get to hboot It's not bricked. Which ruu were you trying
pwned3 said:
If you can get to hboot It's not bricked. Which ruu were you trying
Click to expand...
Click to collapse
RUU_Vigor_VERIZON_WWE_2.01.605.11_Radio_RS_0.95.00.1123r_3161E_9K_QMR_release_233635_signed
Try running that one again. It should work. You have to run it twice anyway
pwned3 said:
Try running that one again. It should work. You have to run it twice anyway
Click to expand...
Click to collapse
Tried. It's stuck on the "Verifying the information on your PDA Phone...Please wait..." screen.
EDIT: Nevermind, went into Fastboot, working now. Let you know how it goes. Thanks for the help so far.
I'm getting a bootloader version error. An ICS RUU should fix this, right? Granted, I know that means I can't go back until I S-Off, but I'd rather that than have a soft bricked phone
I am in the same boat - S-ON. I flashed Scott's ICS Rooted Stock Rom, along with the GB Patch. I downloaded the PH98IMG.zip and HBOOT doesn't recognize it. Trying the exe may resolve this?
Issue resolved thanks to dsb in the IRC channel. For some reason, I thought I had to throw the unlock.bin on my SD card to unlock.
And to the guy above me, try pushing it through adb. Extract the ROM, find the boot.img, throw it into your ADB directory.
adb reboot bootloader
(make sure you're in fastboot USB)
fastboot flash boot boot.img
Chyrux said:
Issue resolved thanks to dsb in the IRC channel. For some reason, I thought I had to throw the unlock.bin on my SD card to unlock.
And to the guy above me, try pushing it through adb. Extract the ROM, find the boot.img, throw it into your ADB directory.
adb reboot bootloader
(make sure you're in fastboot USB)
fastboot flash boot boot.img
Click to expand...
Click to collapse
Hate to ask you this, but would you mind giving me a step by step on what you did to get back to GB?
Thanks -Kim
print.logic said:
Hate to ask you this, but would you mind giving me a step by step on what you did to get back to GB?
Thanks -Kim
Click to expand...
Click to collapse
With the new leak out, I haven't. However, I can still help.
Make sure there is no P98IMG file on your SD card.
1. Download the mainver fix from this post http://forum.xda-developers.com/showpost.php?p=23169557&postcount=4
2. Drop GB ROM of your choice onto SD card.
3. Flash the fix in recovery and reboot into bootloader.
4. Relock your phone by going into adb and typing in fastboot oem lock
5. Run GB RUU of your choice.
6. Use the HTCDev unlock on your bootloader
7. Download a recovery and push it to your phone by typing in fastboot flash recovery recovery.img
8. Boot into recovery, flash ROM, enjoy.
I've been (at least trying to) patiently wait for Deck to post full install instructions for CM10 but the CM10 op is still bare as bones. Has anyone else posted an install guide or instructions yet?
I'm currently rooted with RegawMod and running MeanRom 2.1 and it's really terribly laggy and frustrating, I can't wait any longer for CM10. Do I need S-off to install CM10 or do I just wipe, flash, and go?
Thanks for any help or links!
If you are on hboot 1.15 or higher you have to fast boot flash the kernel.
Other than that its just like a normal aosp install. Wipe flash rom flash gapps.
Its been my daily for 3 weeks.
Sent from my EVO using Tapatalk 2
You don't need s-off. You will however have to flash the boot IMG separately by using fastboot or the app flash image GUI and a full wipe is definitely required. There is a helpful thread in Q&A called "don't panic" that will answer all your questions
Good luck
Sent from my EVO using xda app-developers app
corcgaigh said:
You don't need s-off. You will however have to flash the boot IMG separately by using fastboot or the app flash image GUI and a full wipe is definitely required. There is a helpful thread in Q&A called "don't panic" that will answer all your questions
Good luck
Click to expand...
Click to collapse
Dont use flash image gui unless you know how to do it manually through fastboot. You are just asking for issues
Instructions:
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-a.html
Rxpert said:
If you are on hboot 1.15 or higher you have to fast boot flash the kernel.
Other than that its just like a normal aosp install. Wipe flash rom flash gapps.
Click to expand...
Click to collapse
I'm on hboot 1.12, so does that mean I can just flash normally?
edit - From what I can tell from reading, hboot 1.12 doesn't have the same restrictions that 1.15+ do, so I think I'm OK but I would like verification.
Thanks for the help everyone.
Yes hboot 1.12 allows for access to the boot partition
Also luuuuucckkyyyyyy...
EdhyMonker said:
I'm on hboot 1.12, so does that mean I can just flash normally?
edit - From what I can tell from reading, hboot 1.12 doesn't have the same restrictions that 1.15+ do, so I think I'm OK but I would like verification.
Thanks for the help everyone.
Click to expand...
Click to collapse
If you are on Hboot 1.12 I'd strongly suggest looking into getting S-OFF. Theres really no reason not to.
Up to you though, its not required
Bit off topic, anyone check to see if you can push a new splash, right now I'm too lazy to start my PC just to fastboot one measly splash
Rxpert said:
If you are on Hboot 1.12 I'd strongly suggest looking into getting S-OFF. Theres really no reason not to.
Up to you though, its not required
Click to expand...
Click to collapse
The S-OFF guide was way over my head so I just let it be. If there's not a real good reason for doing it, and I can still run CM10, then I'd rather not.
It allows you to directly flash new firmware like radios to fix any problems a device might be having. If you have Son and want the latest firmware you have to revert back to stock and accept ota, then unlock reflash recovery and reflash custom ROM or rooted stock, you could also just flash root installer if you want to just root stock
om4 said:
It allows you to directly flash new firmware like radios to fix any problems a device might be having. If you have Son and want the latest firmware you have to revert back to stock and accept ota, then unlock reflash recovery and reflash custom ROM or rooted stock, you could also just flash root installer if you want to just root stock
Click to expand...
Click to collapse
No, S-ON people with 1.12 H-boot can flash radios and firmware from recovery. They can do whatever they please in recovery just like S-OFF. S-OFF users can flash things from bootloader and even change the appearance of their h-boot to read S-ON and **locked** even though they are S-OFF
To the OP, this is the best rooting guide I've seen. It really explains everything step by step. http://androidforums.com/evo-4g-lte...panda-s-htc-dev-ltevo-root-dummies-guide.html Its recommended to have Linux at least bootable, because in the small chance the phone gets bricked... the unbricker program requires linux.
I ran it in windows before the unbricker was available, no issues here
You basically just hook the phone up to it and run the program like you do for most other root programs. All 1-click
Ah yeah forgot to mention that, most everyone is on 1.15 or 1.19 sorry
om4 said:
Ah yeah forgot to mention that, most everyone is on 1.15 or 1.19 sorry
Click to expand...
Click to collapse
Alright, I got S-Off using Lazy Panda and it went better than expected!
Do I need to flash updated firmware / radios separately from CM10, or does CM10 include latest firmware?
Sorry to ask dumb questions, but I do hope this thread will also be a good resource for others like me.
You don't have to flash any firmware updates. There are a few users with issues although they may be related to the ROM update and not necessarily the firmware included. I haven't really checked since I'm s on. If you want to update the radios there's an update zip here somewhere, be sure to read through everything carefully. Radios are more risky then every day flashing
Alright everyone now I need some help!
I flashed CM10 after s-off, was on stocked 1.13 rooted rom.
Now when CM10 boots up I am faced with a phone activation screen. It says something like "you will not be able to place calls or access the mobile network until the device is activated". I am unable to make calls or receive calls or access the internet. I have tried reflashing cm10 and the problem persists.
In the mean time, I will try flashing a nand backup and see where that gets me. I appreciate any and all help, and I have found no posts in the CM10 thread with a similar issue.
Update: I wiped and restored a back-up, MeanRom 2.1. Upon boot, hands-free activation ran and activated the phone and downloaded a PRL update. Everything is working fine now. Not sure if I should try CM10 again or what? Any advice?
EdhyMonker said:
Alright everyone now I need some help!
I flashed CM10 after s-off, was on stocked 1.13 rooted rom.
Now when CM10 boots up I am faced with a phone activation screen. It says something like "you will not be able to place calls or access the mobile network until the device is activated". I am unable to make calls or receive calls or access the internet. I have tried reflashing cm10 and the problem persists.
In the mean time, I will try flashing a nand backup and see where that gets me. I appreciate any and all help, and I have found no posts in the CM10 thread with a similar issue.
Update: I wiped and restored a back-up, MeanRom 2.1. Upon boot, hands-free activation ran and activated the phone and downloaded a PRL update. Everything is working fine now. Not sure if I should try CM10 again or what? Any advice?
Click to expand...
Click to collapse
ive only ever seen this issue with cyanogenmod and the old htc vogues, still great phones for what they were
EdhyMonker said:
Alright, I got S-Off using Lazy Panda and it went better than expected!
Do I need to flash updated firmware / radios separately from CM10, or does CM10 include latest firmware?
Sorry to ask dumb questions, but I do hope this thread will also be a good resource for others like me.
Click to expand...
Click to collapse
Yes, you should be flashing the upgraded firmware. You'll see the full firmware as the very first downloadable link. Flash that
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Rename the file to "PJ75IMG.zip", place on root of SD card, and boot into HBOOT to flash. Check the md5 to make sure its right. With radios you want to make sure its the correct file.
Welcome to S-OFF my friend
Rxpert said:
Yes, you should be flashing the upgraded firmware. You'll see the full firmware as the very first downloadable link. Flash that
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Rename the file to "PJ75IMG.zip", place on root of SD card, and boot into HBOOT to flash. Check the md5 to make sure its right. With radios you want to make sure its the correct file.
Welcome to S-OFF my friend
Click to expand...
Click to collapse
Thanks, but I tried this and it says "no image or wrong image" when trying to flash the PJ75IMG.zip file.
Did you type in PJ75IMG.zip or PJ75IMG and kept it a zip file...you should do the 2nd.
joebarkho said:
Did you type in PJ75IMG.zip or PJ75IMG and kept it a zip file...you should do the 2nd.
Click to expand...
Click to collapse
I thought that might've been the issue so I tried it both ways, didn't work either way. I'll take another shot at it tomorrow.
Hey all, just received a replacement rezound under warranty due to the charge port being all muffed up, and of coarse the first thing was unlock via htcdev which worked fine.
Here is the issue.. when trying to flash amonra via fastboot or PH98IMG.zip in bootloader it won't flash. For fastboot it says "unknown error" and as a PH file in bootloader it says "parsing..." for a few seconds then disappears without flashing anything. I've re-downloaded and checked md5's and still get the same errors.
My last rezound was s-off and that whole process was quick and painless and I don't understand why the same procedure I used on my last rezound isn't working now.
Any help would be greatly appreciated.
zac41189 said:
Hey all, just received a replacement rezound under warranty due to the charge port being all muffed up, and of coarse the first thing was unlock via htcdev which worked fine.
Here is the issue.. when trying to flash amonra via fastboot or PH98IMG.zip in bootloader it won't flash. For fastboot it says "unknown error" and as a PH file in bootloader it says "parsing..." for a few seconds then disappears without flashing anything. I've re-downloaded and checked md5's and still get the same errors.
My last rezound was s-off and that whole process was quick and painless and I don't understand why the same procedure I used on my last rezound isn't working now.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
What firmware is on the device?
hgoldner said:
what firmware is on the device?
Click to expand...
Click to collapse
ota 3.14.605.12 710rd.
Can you flash in fastboot usb? (And, to be perfectly clear to avoid a dumb question, does hboot reflect that you are unlocked?)
hgoldner said:
Can you flash in fastboot usb? (And, to be perfectly clear to avoid a dumb question, does hboot reflect that you are unlocked?)
Click to expand...
Click to collapse
indeed *** unlocked *** is displayed at the top on hboot. and ive tried "fastboot flash recovery (nameofrecovery.img) with nameofrecovery changed to what i have it saved as and no luck. even tried relocking and ruuing too just to make sure it wasnt the software messing everything up.
Can't remember but can you try to S-OFF first? (It's been so long, but I can't remember whether you have a custom recovery already on).
Ah, one other stupid thing.... have you tried a different sdcard?
hgoldner said:
Can't remember but can you try to S-OFF first? (It's been so long, but I can't remember whether you have a custom recovery already on).
Ah, one other stupid thing.... have you tried a different sdcard?
Click to expand...
Click to collapse
I was thinking about the sd card being the issue but it installed an ruu via ph98img.zip perfectly fine bit its worth a shot. And on unlimited.io's site they say you need to be completely stock with root and as far as I know amonra is the only way to root on a stock ruu. I managed to s-off tho after using hasoon's tool to flash amonra. I'm now completely stock again after ruuing back to gb then accepting ota
so I'll try flashing amonra again and report back. Thank you for your help!
Sent from my ADR6425LVW using xda premium
You can install any custom recovery and use it to flash SuperUser. The root option in Amon Ra doesn't usually work by itself anyway.
shrike1978 said:
You can install any custom recovery and use it to flash SuperUser. The root option in Amon Ra doesn't usually work by itself anyway.
Click to expand...
Click to collapse
Oh ok thats good to know actually. just cant seem to install any custom recoveries lol. i chose to install amon ra 3.15 with hasoons tool and for some reason i have 3.06 installed.. dont know how or why but i do. tried to install 3.15 with his toolkit again and got the stupid error again. i dont know what to do at this point lol. never had this problem with the last rezound. i am s-off now but do not have the recovery i want installed.
should i try ruu'ing again and start fresh?
and for what its worth i do have the jb hboot installed just to see if that was the issue. had to use fastboot commands to install it so i dont think thats the issue. i think its the download for amonra 3.15 i have. if anyone has a personal copy of 3.15 that is confirmed working and is willing to share it itd be greatly appreciated.
To use the fastboot commands you must be unlocked. With the parsing error. That will sometimes happen if you have a file called "update.zip" on your sdcard. Try seeing if you have one of those files. If your HBOOT does say s-off. Flash the GB RUU. Just so you can verify everything has changed. and then restart with the ICS RUU then flash a recovery. This time not with that tool.
Flyhalf205 said:
To use the fastboot commands you must be unlocked. With the parsing error. That will sometimes happen if you have a file called "update.zip" on your sdcard. Try seeing if you have one of those files. If your HBOOT does say s-off. Flash the GB RUU. Just so you can verify everything has changed. and then restart with the ICS RUU then flash a recovery. This time not with that tool.
Click to expand...
Click to collapse
Thank you for the response. i tested to see if i really did have s-off by doing just that. ruu'd back to gb without a hitch. then accepted the ota. so im thinking ill just ruu the ota (3.14.605.12) and see what happens. and im with you on not using the tool again. ive heard really good things about it but never used it personally until today. my old method worked well i just didn't know what else to do at that point lol
zac41189 said:
Thank you for the response. i tested to see if i really did have s-off by doing just that. ruu'd back to gb without a hitch. then accepted the ota. so im thinking ill just ruu the ota (3.14.605.12) and see what happens. and im with you on not using the tool again. ive heard really good things about it but never used it personally until today. my old method worked well i just didn't know what else to do at that point lol
Click to expand...
Click to collapse
To s-off you got to do the wire trick. But RUU then don't use the tool. lol Lets us now if it works out.
Flyhalf205 said:
To s-off you got to do the wire trick. But RUU then don't use the tool. lol Lets us now if it works out.
Click to expand...
Click to collapse
Yupp s-off'd with no issues. Just want amonra lol. Ruu'd to OTA and am waiting for my battery to charge up enough to flash via hboot. The amonra thread has a PH98IMG.zip but I think that one was the 3.06 version. Dunno. Will report back.
Sent from my ADR6425LVW using xda premium
zac41189 said:
Yupp s-off'd with no issues. Just want amonra lol. Ruu'd to OTA and am waiting for my battery to charge up enough to flash via hboot. The amonra thread has a PH98IMG.zip but I think that one was the 3.06 version. Dunno. Will report back.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
I'm not trying to be a jerk or whatever but have you read the bottom of the AmonRA OP? It has a link to 3.15 I am pretty sure.
Curious. Why you want AR so bad? We have 2 other fully functional recoveries. lol
Flyhalf205 said:
I'm not trying to be a jerk or whatever but have you read the bottom of the AmonRA OP? It has a link to 3.15 I am pretty sure.
Curious. Why you want AR so bad? We have 2 other fully functional recoveries. lol
Click to expand...
Click to collapse
The ph98img.zip in that post is 3.06. I just got really used to it lol. I have twrp 2.3.2.3 downloaded for a couple weeks now.. might as well try it out lol.
Sent from my ADR6425LVW using xda premium
zac41189 said:
The ph98img.zip in that post is 3.06. I just got really used to it lol. I have twrp 2.3.2.3 downloaded for a couple weeks now.. might as well try it out lol.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Since you're on the OTA ICS firmware, you should definitely NOT be running Amon Ra 3.06. You need to be on 3.15. If the md5's match what's on your sdcard and what's on the OP at that thread, it shouldn't be a bad download, but just in case, I loaded it up on my Dropbox and you can try the one here.
As far as alternate recoveries, while I was very impressed with TWRP, it is incapable of wiping boot, so that's a nonstarter. Admittedly, if Flyhalf solved that issue, I'd switch to it. As far as CWM Touch, that has issues with reading sdcard2, as of the last time I checked, or at least with respect to its interaction with various ROMs and their features. For me at least, having tried all of the Rezound recoveries, Amon Ra is my preferred choice.
just push AR manually instead of using the tool:
Unzip the file from the link listed below onto the root of the C drive on your PC, and it should create a folder called Android on the root of C.
1) open a cmd prompt and type " cd c:\Android " without quotes
2) boot to fastboot and make sure your USB is plugged into the pc and phone
3) type " fastboot flash recovery recovery.img " without the quotes
This should push the AR 3.15 to your device. I included AR 3.15 in the Android folder below.
the folder contains a txt file of a few other handy commands that i use. that txt file is for reference only
https://www.dropbox.com/s/aycfqc37tvkhbdl/Android12-14-2012_22+21+19.rar
I ended up flashing twrp and it worked great. Like a previous poster said if it could wipe boot it would be perfect. But it got the job done and am up and running again. Thank you all for your help!
Sent from my Rezound using xda premium
Glad everything worked out for ya. Wiping boot can cause a lot of problems just sayin. So I debating on putting it back into TWRP. Just ask snuzzo in his kernel thread
So I'm currently on Flyhalf's CM10.1 (S-ON), and I checked the recommended firmware/radios for the ROM and realized I'm outdated. It calls for Hboot 2.26 and radio 2.23.10.0123r, 2.23.10.0124r. but I'm on 2.25 and 1.22.10.0421r/1.22.10.0424r. I just updated to the latest version of the rom and I keep getting random bootlooping as well as the rom being way more unstable than the previous build I was on for about 4 months.
So, I'm trying to use Wildhorse's guide to updating firmware through RUU in hopes that it will solve my problems and it just plain isn't working. I've put the RUU in my external SD as PH98IMG, waited for my battery to charge to 90%, shut off the phone, pulled the battery, then gone into Hboot to flash it but I keep getting "No Image or Wrong Image" and it just goes back to the main Hboot screen every single time. Can anyone explain to me why this is happening even though I'm following everybody's directions exactly? I've been searching through the forums for about 2 hours now and I can't get an answer.
I'm still kind of new to HTC devices and how they work, so if anyone could help me figure this out I'd be very thankful.
BrahManty said:
So I'm currently on Flyhalf's CM10.1 (S-ON), and I checked the recommended firmware/radios for the ROM and realized I'm outdated. It calls for Hboot 2.26 and radio 2.23.10.0123r, 2.23.10.0124r. but I'm on 2.25 and 1.22.10.0421r/1.22.10.0424r. I just updated to the latest version of the rom and I keep getting random bootlooping as well as the rom being way more unstable than the previous build I was on for about 4 months.
So, I'm trying to use Wildhorse's guide to updating firmware through RUU in hopes that it will solve my problems and it just plain isn't working. I've put the RUU in my external SD as PH98IMG, waited for my battery to charge to 90%, shut off the phone, pulled the battery, then gone into Hboot to flash it but I keep getting "No Image or Wrong Image" and it just goes back to the main Hboot screen every single time. Can anyone explain to me why this is happening even though I'm following everybody's directions exactly? I've been searching through the forums for about 2 hours now and I can't get an answer.
I'm still kind of new to HTC devices and how they work, so if anyone could help me figure this out I'd be very thankful.
Click to expand...
Click to collapse
You are on a leaked firmware, the currently available RUUs are all older than that, and you can't go back when you are S-ON. You need to S-OFF then you can RUU back to 3.14.605.12 and then OTA back up to the current 4.5.605.14
acejavelin said:
You are on a leaked firmware, the currently available RUUs are all older than that, and you can't go back when you are S-ON. You need to S-OFF then you can RUU back to 3.14.605.12 and then OTA back up to the current 4.5.605.14
Click to expand...
Click to collapse
Okay, I was really hoping that wasn't the case. I hate to ask for more help, but I don't really understand how I'm supposed to get S-Off when I need to be on the stock RUU to do it, and I can't get on the stock RUU because I need to be S-Off to do so...
I hope I'm not stuck this way. Technically I'm on all the same software as I was yesterday, but now I'm getting random reboots all the time as well as bootloops that either go on for ten minutes or never end. I was on a build of CM10.1 from may with Amon Ra recovery, then tried to flash the newest TWRP that requires the new firmware (didn't realize I was on older firmware) and it bricked my phone. So I put on an older CWM recovery, tried to backup and it froze in the middle of every backup it tried to make. Put on an old TWRP, backups worked, so I flashed the newest version of CM10.1 (again not knowing I didn't have newest firmware) and that's when the bootlooping/rebooting started. I recovered to the old version of CM10.1 and the issue didn't go away, so now I'm just trying to figure out what I can do to get my phone in a usable state again.
BrahManty said:
Okay, I was really hoping that wasn't the case. I hate to ask for more help, but I don't really understand how I'm supposed to get S-Off when I need to be on the stock RUU to do it, and I can't get on the stock RUU because I need to be S-Off to do so...
I hope I'm not stuck this way. Technically I'm on all the same software as I was yesterday, but now I'm getting random reboots all the time as well as bootloops that either go on for ten minutes or never end. I was on a build of CM10.1 from may with Amon Ra recovery, then tried to flash the newest TWRP that requires the new firmware (didn't realize I was on older firmware) and it bricked my phone. So I put on an older CWM recovery, tried to backup and it froze in the middle of every backup it tried to make. Put on an old TWRP, backups worked, so I flashed the newest version of CM10.1 (again not knowing I didn't have newest firmware) and that's when the bootlooping/rebooting started. I recovered to the old version of CM10.1 and the issue didn't go away, so now I'm just trying to figure out what I can do to get my phone in a usable state again.
Click to expand...
Click to collapse
Hey, wait a sec... :laugh:
My bad, I just double checked, and with that Hboot/radio combination you are on stock ICS firmware already! Just RUU version 3.14.605.12, that should work without issues if done correctly and you should be back to pure ICS and can then allow the OTA to upgrade you in a few steps to 4.5.605.14
acejavelin said:
Hey, wait a sec... :laugh:
My bad, I just double checked, and with that Hboot/radio combination you are on stock ICS firmware already! Just RUU version 3.14.605.12, that should work without issues if done correctly and you should be back to pure ICS and can then allow the OTA to upgrade you in a few steps to 4.5.605.14
Click to expand...
Click to collapse
Oh, thank god. Hahah. I didn't remember ever flashing any leaked firmware before, so I was kind of confused there. I figured I may have done it somewhere in the unlocking/rooting process and just couldnt remember. Okay, thanks again for the help. RUU's have always confused me with the way they work. I should be stable in no time hopefully.
And now I'm having more issues... I can't use the Rom Updater because somethings wrong with my usb connection. I can plug it in and transfer files and such, but trying to use any ADB commands results in "Device not found" and the Rom Updater says it can't connect to my device either. My HTC Drivers are up to date, so I'm not sure why this is happening. Is there any way I can just get the PH98IMG.zip for 3.14.605.12 instead of having to use the RUU?
Not really sure what you are trying to run, I didn't think there was a 3.14.605.12 executable RUU, but use this page and instructions and grab the file: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Remember you will need to RELOCK the bootloader if I am not mistaken it is possible to hard brick if you don't!
Then copy to external SD card, name the file PH98IMG.zip (beware of the Windows "double zip" issue), verify MD5 on the SDcard, then reboot into hboot and go. Do it twice!!! Let it boot up and sit for about 10 minutes to calm down, then remove the PH98IMG.zip file from the SD card. Everything should be smooth sailing from there...
You should then be S-ON, completely stock. You will need to unlock again to do anything more
acejavelin said:
Not really sure what you are trying to run, I didn't think there was a 3.14.605.12 executable RUU, but use this page and instructions and grab the file: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Remember you will need to RELOCK the bootloader if I am not mistaken it is possible to hard brick if you don't!
Then copy to external SD card, name the file PH98IMG.zip (beware of the Windows "double zip" issue), verify MD5 on the SDcard, then reboot into hboot and go. Do it twice!!! Let it boot up and sit for about 10 minutes to calm down, then remove the PH98IMG.zip file from the SD card. Everything should be smooth sailing from there...
You should then be S-ON, completely stock. You will need to unlock again to do anything more
Click to expand...
Click to collapse
Strange, re-locking the bootloader was all I needed to get the RUU to update in my bootloader. No one else said to do that in any of the instructions, but I did it and immediately it started updating with the PH98IMG that I was originally trying to flash (from here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331).
I'm back to stock now, but firmware is 4.03.605.2, not 4.03.605.14. Is that going to be an issue or can I go right ahead with re-unlocking the bootloader and flashing recovery/roms?
BrahManty said:
Strange, re-locking the bootloader was all I needed to get the RUU to update in my bootloader. No one else said to do that in any of the instructions, but I did it and immediately it started updating with the PH98IMG that I was originally trying to flash (from here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331).
I'm back to stock now, but firmware is 4.03.605.2, not 4.03.605.14. Is that going to be an issue or can I go right ahead with re-unlocking the bootloader and flashing recovery/roms?
Click to expand...
Click to collapse
Well, I have some good news and bad news...
Bad news is you are now on a leaked firmware and will have to S-OFF to go up or down in versions unless a full RUU is released for the current OTA of 4.5.605.14...
Good news is you are the global leak, and you can use the JuopunutBear S-OFF exploit from http://unlimited.io/index.htm just as if you were on the original ICS release. Also, you can S-OFF and use most ROMs and recoveries as you are now on a global mode firmware.
acejavelin said:
Well, I have some good news and bad news...
Bad news is you are now on a leaked firmware and will have to S-OFF to go up or down in versions unless a full RUU is released for the current OTA of 4.5.605.14...
Good news is you are the global leak, and you can use the JuopunutBear S-OFF exploit from http://unlimited.io/index.htm just as if you were on the original ICS release. Also, you can S-OFF and use most ROMs and recoveries as you are now on a global mode firmware.
Click to expand...
Click to collapse
Lol, all right, I would have tried to get the right firmware on there but my phone got so buggy that it wouldn't even boot into the rom anymore. So I couldn't get it on the SD card and I had to make do with what I had on there. At this point, I'm just glad the phone is usable again and I might leave it stock for a while. Thank you so much for all your help, I couldn't have figured this out without you!
BrahManty said:
Lol, all right, I would have tried to get the right firmware on there but my phone got so buggy that it wouldn't even boot into the rom anymore. So I couldn't get it on the SD card and I had to make do with what I had on there. At this point, I'm just glad the phone is usable again and I might leave it stock for a while. Thank you so much for all your help, I couldn't have figured this out without you!
Click to expand...
Click to collapse
Cool, glad you got it working.
That firmware is actually pretty decent and rock solid stable, you shouldn't have any more software related issues... Plus you can root/ROM like normal from that version, the radios may be slightler lower than most recommended versions, but they should work fine. If you do decide to go the ROM route again, I would suggest going S-OFF before starting, it will just make it easier in the long run.
Hey, just wanted to ask some questions as a follow-up since this seems to be the most relevant (and active) thread to my issue:
Long story short, got a new (to me) Rezound. It was running CM10, from the forthnightly thread. New SIM card from Verizon and I was getting data, but the no mobile network found error. After reading the threads I could find on the error, went with the suggestion of a wipe and so I did. A few too many beers while reading thru the forums, and I did the wipe a bit too thoroughly. Now I have a no OS found, and instead of thinking I know what I'm doing I'd like to ask to make sure I understand this correctly.
Currently, the phone is S-OFF, with TWRP 2.5.0.0. It's saying I'm not rooted, but then again no OS to be rooted. The dump from my bootloader is as follows:
*** TAMPERED ***
*** LOCKED ***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Sep 20 2012, 17:40:22
Click to expand...
Click to collapse
After checking this thread and this one here it looks like the following applies:
* I can just run the regular RUU (executable) to load a stock image without having to revert back to S-ON first.
* I will have to re-unlock the bootloader thru htcdev after RUUing
* I'll need to reinstall TWRP
Is this right? Am I missing anything?
JoeKamel said:
Hey, just wanted to ask some questions as a follow-up since this seems to be the most relevant (and active) thread to my issue:
Long story short, got a new (to me) Rezound. It was running CM10, from the forthnightly thread. New SIM card from Verizon and I was getting data, but the no mobile network found error. After reading the threads I could find on the error, went with the suggestion of a wipe and so I did. A few too many beers while reading thru the forums, and I did the wipe a bit too thoroughly. Now I have a no OS found, and instead of thinking I know what I'm doing I'd like to ask to make sure I understand this correctly.
Currently, the phone is S-OFF, with TWRP 2.5.0.0. It's saying I'm not rooted, but then again no OS to be rooted. The dump from my bootloader is as follows:
After checking this thread and this one here it looks like the following applies:
* I can just run the regular RUU (executable) to load a stock image without having to revert back to S-ON first.
* I will have to re-unlock the bootloader thru htcdev after RUUing
* I'll need to reinstall TWRP
Is this right? Am I missing anything?
Click to expand...
Click to collapse
You should be able to just boot into twrp and flash a rom
Sent from my ADR6425LVW using xda premium
izzaeroth said:
You should be able to just boot into twrp and flash a rom
Click to expand...
Click to collapse
Okay, that's good to know. For now though, if I just wanted to get my phone working, make sure there's not a SIM issue and such I could go back to a stock image without worrying? I just would rather do a lot more reading and make sure I understand what I'm doing before I try to put a rom on and screw things up further.
JoeKamel said:
Okay, that's good to know. For now though, if I just wanted to get my phone working, make sure there's not a SIM issue and such I could go back to a stock image without worrying? I just would rather do a lot more reading and make sure I understand what I'm doing before I try to put a rom on and screw things up further.
Click to expand...
Click to collapse
No doubt its good to be cautious when you are s-off. If you are just wanting plain jane stock then you could just flash a ruu from boot loader.
Sent from my ADR6425LVW using xda premium
izzaeroth said:
No doubt its good to be cautious when you are s-off. If you are just wanting plain jane stock then you could just flash a ruu from boot loader.
Click to expand...
Click to collapse
Okay, so if I go with the image here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331
Would I still need to relock the bootloader since I'm S-OFF or can I just flash that from TWRP and go from there?
JoeKamel said:
Okay, so if I go with the image here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331
Would I still need to relock the bootloader since I'm S-OFF or can I just flash that from TWRP and go from there?
Click to expand...
Click to collapse
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Sent from my ADR6425LVW using xda premium
izzaeroth said:
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Click to expand...
Click to collapse
Recovery as in HBoot or TWRP? Because I still have TWRP. I can get the windows executable RUU for ICS if need be.
JoeKamel said:
Recovery as in HBoot or TWRP? Because I still have TWRP. I can get the windows executable RUU for ICS if need be.
Click to expand...
Click to collapse
Recovery = twrp
Sent from my ADR6425LVW using xda premium
izzaeroth said:
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
S-off is S-off... installing a RUU wont change that, it may set you back to 'Locked", but you are S-off so it doesn't matter, you can stay locked&s-off and its no different than unlocked/S-off.
If you are going back to stock and are S-off I would use the Global Mode Leak (4.3.605.2) available on AndroidPolice and flash in Hboot... rename file to PH98IMG.zip and place in root of SD card (how it gets there is a irrelevant) then reboot into Hboot, confirm and wait.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app