So I finally cracked down and went S-Off today. Though I had been having the sim issues. Given that I'm S-Off, is there any way to apply the update without overly screwing myself and having to fully re-do my phone? How would you go about it?
?
Sent from my HTC6435LVW using Tapatalk 2
Just flash a Rom based on 2.06
Sent from my HTC6435LVW using xda app-developers app
Just flashing a Rom will not update the firmware. You can either flash the full ruu or just the radios from a radio thread and that will do it. It will not mess s-off up but if you have the eng hboot it will overwrite it so you will have to reflash it
hkbladelawhk said:
So I finally cracked down and went S-Off today. Though I had been having the sim issues. Given that I'm S-Off, is there any way to apply the update without overly screwing myself and having to fully re-do my phone? How would you go about it?
Click to expand...
Click to collapse
In the s-off thread grab the firmware.zip and flash it. It will update your firmware to 2.06 without messing with s off. Do keep in mind this will replace your kernel recovery and hboot .
You will still be soff, so when finished reflash eng hboot if you desire, reflash TWRP AND flash a new kernel if nedded.
sent via electromagnetic radiation.
---------- Post added at 09:34 AM ---------- Previous post was at 09:29 AM ----------
Kirk and big are both wrong. Radio's are just that....radio's, not firmware. Same for the Rom.
You update your windows/linux software. But you may not have updated your system's bios firmware
sent via electromagnetic radiation.
At minimum he can flash the new radio, if he still has the problem then he can flash the new kernel.
There is no ruu for 2.04 or 2.06.
So I updated the radio, changed roms to NOS M7, and changed my kernel to Beastmode. Besides experiencing a 1-2% more increase in batt drop/hour, I just had the SIM issue again. Bah. My Otterbox is gonna hate me for removing it again lol
Updating the Radio =/= to updating the firmware afaik. I too would like a guide on how to do this firmware update since the Sim Card thing is a pain.
Budwise said:
Updating the Radio =/= to updating the firmware afaik. I too would like a guide on how to do this firmware update since the Sim Card thing is a pain.
Click to expand...
Click to collapse
I keep getting mixed answers on this one. I've heard updating the radio does it, and I've heard I have to roll all the way back then push back forward...Do we have anything more concrete? Confirmed my radio is up to date.
Updating the Radio =/= to updating the firmware afaik. I too would like a guide on how to do this firmware update since the Sim Card thing is a pain.
Click to expand...
Click to collapse
Updating the radio pretty much does it. The rest of the stuff is just things like the stock recovery, hboot, kernel, and a few other things.
Sent from my HTC6435LVW using xda app-developers app
I had a lot of SIM issues even after updating radios. I did what I posted above and havent had it since.
sent via electromagnetic radiation.
ibsk8 said:
I had a lot of SIM issues even after updating radios. I did what I posted above and havent had it since.
sent via electromagnetic radiation.
Click to expand...
Click to collapse
Did this. I flashed new radio. Then Rom. Then beastmode kernel. I've had the SIM issue twice today. Seriously wtf.
http://forum.xda-developers.com/showthread.php?t=2236633&highlight=radio << Flashed from this thread.
orangechoochoo said:
At minimum he can flash the new radio, if he still has the problem then he can flash the new kernel.
There is no ruu for 2.04 or 2.06.
Click to expand...
Click to collapse
Which new kernel are we talking about? Isn't the 5.9 beastmode a build off the new kernel?
hkbladelawhk said:
Which new kernel are we talking about? Isn't the 5.9 beastmode a build off the new kernel?
Click to expand...
Click to collapse
No, it's built off of 2.04 since there is no source for 2.06
Sent from my HTC6435LVW using xda app-developers app
I've been having the same issue with the SIM card. I've been asking around and they say it's not the radio that needs to be updated, it's the phone. i've tried new kernels, different firmware, ROMs etc. Still having the issue, with no SIM card found.
Putting it into airplane mode is getting really old.
I think I will need to turn S-OFF back to S-ON, before I take it back into verizon, though. So that's my next task.
Hmm. That's not really an option for me. My phones old. Guess I have to either find the new kernel (anyone running it?) or wait till the src comes out for the devs to work on. Its an odd bug.
Sent from my HTC6435LVW using Tapatalk 2
Did you flash the pl8xxxx.zip from the s-off thread like I suggested? Or did you simply flash the radio's again from the thread you posted?
If you didn't do what I suggested what's the point in asking questions if you're not going to try the solutions.
Your response leads me to believe you flashed only the radio's again.
sent via electromagnetic radiation.
ibsk8 said:
Did you flash the pl8xxxx.zip from the s-off thread like I suggested? Or did you simply flash the radio's again from the thread you posted?
If you didn't do what I suggested what's the point in asking questions if you're not going to try the solutions.
Your response leads me to believe you flashed only the radio's again.
sent via electromagnetic radiation.
Click to expand...
Click to collapse
I didn't flash anything yet. I wanted to wait for a response for clarification. I will try what you said.
Isn't the signed firmware in that post the same we flashed to get the error to get S-Off? I'm just reflashing? Wouldn't that throw the same error?
Sent from my GT-P3113 using Tapatalk 2
hkbladelawhk said:
I didn't flash anything yet. I wanted to wait for a response for clarification. I will try what you said.
Isn't the signed firmware in that post the same we flashed to get the error to get S-Off? I'm just reflashing? Wouldn't that throw the same error?
Sent from my GT-P3113 using Tapatalk 2
Click to expand...
Click to collapse
It spit the 92 error because we weren't s-off. You may need to flash it twice.
After flashing it you will get all the updated firmware. It will give you a tampered message in the stock hboot. It will also restore stock recovery.
When finished boot back to android 'fastboot reboot'
Then 'adb reboot recovery'
Then fastboot rebootRUU, flash the eng hboot.
Your tampered message will disappear , fastboot flash recovery xxxx
Reboot and see if you get the SIM error.
No guarantee it will fix it, I also disabled the fastboot option in the power settings .
sent via electromagnetic radiation.
ibsk8 said:
It spit the 92 error because we weren't s-off. You may need to flash it twice.
After flashing it you will get all the updated firmware. It will give you a tampered message in the stock hboot. It will also restore stock recovery.
When finished boot back to android 'fastboot reboot'
Then 'adb reboot recovery'
Then fastboot rebootRUU, flash the eng hboot.
Your tampered message will disappear , fastboot flash recovery xxxx
Reboot and see if you get the SIM error.
No guarantee it will fix it, I also disabled the fastboot option in the power settings .
sent via electromagnetic radiation.
Click to expand...
Click to collapse
Done! Let's see where it goes!
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.
Whenever I try to flash a ROM I always get "main version older". I'm on the stock, rooted gingerbread ROM right now with an unlocked bootloader and if I try to flash any ROM whether it's a gingerbread or ICS ROM I always get the same message when the phone reboots to the bootloader to flash the kernel.
What can I do about this?
After I first unlocked my phone I tried to install an ICS rom then I installed a gingerbread rom after and I never saw that message once. Then I started seeing it so I went back to stock to see if that would fix my issue but it hasn't.
Helper
It mostly mean your htc rezound is on a newer main version of software you going to need to downgrade by changing the number here a link to help you do this and take out the older message that come up http://forum.xda-developers.com/showthread.php?t=1467099
So, theoretically, if I take it all the way back down to 1.00.000.0 I could be able to flash anything because whatever I flash will always be greater than the main version.
skatingrocker17 said:
So, theoretically, if I take it all the way back down to 1.00.000.0 I could be able to flash anything because whatever I flash will always be greater than the main version.
Click to expand...
Click to collapse
Until you flash something that updates your mainver lol.
Sent from my ADR6425LVW using XDA Premium.
Which a lot of roms and kernels do. Its a very annoying issue.
If the main versions are the same will it still throw the same error?
Nope. Only when the mainver is older.
Sent from my ADR6425LVW using xda premium
Well it works. Anyone have any idea how I keep getting stuck at the HTC screen when I flash some roms (ICS ones mostly). I've never made it past the HTC screen with CleanRom and now I'm on the new Bamf ICS 0.5 rom and I'm sitting here stuck again. The kernel flashed successfully in the bootloader so I'm not sure why I keep getting stuck.
file
use's something that can read your sdcard and add this file here http://www.mediafire.com/?9b9pr48t498ru1g to you sdcard then go into bootloader and let fastboot do it thing
cflo360 said:
use's something that can read your sdcard and add this file here http://www.mediafire.com/?9b9pr48t498ru1g to you sdcard then go into bootloader and let fastboot do it thing
Click to expand...
Click to collapse
Well I tried it out on both Bamf and CleanRom and the results were no different... still stuck at the HTC start screen unfortunately.
Helper
use this to get recovery overclock or the other recovery mean http://www.mediafire.com/?zk4ooxyonsgnaj5add overclock to the htc then go to your sdcard and add http://files.themikmik.com/new2/Ineffabilis-Deus_v1.0.1-Odex.zip and PH98IMG.zip (http://db.tt/d9503t4R) for bootloader now when all this is placed and done hit the boot to recovery on the program i showed you and your in overclock once there i want you to wip everything once done go to zip file and look for Ineffabilis-Deus_v1.0.1-Odex.zip click and once it finish installing go to bootloader and install PH98IMG.zip so when your done ....hopefully it work
I'm sending you a PM, I think I know what's wrong.
Sent from my ADR6425LVW using Tapatalk
CharliesTheMan said:
I'm sending you a PM, I think I know what's wrong.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Replied.
...Gingerbread roms aren't working either. I have flashed 1 ICS rom and 2 Gingerbread roms in the past but for some reason now, I can't flash anything.
I'm wondering if flashing the stock RUU and relocking, then unlocking again and reflashing Amon Ra would fix the issue. After I originally unlocked was the only time I could ever successfully flash anything.
Don't see how locking and re-unlocking would make a difference.
krelvinaz said:
Don't see how locking and re-unlocking would make a difference.
Click to expand...
Click to collapse
Flashing the RUU requires relocking.
Sent from my Rezound via Tapatalk
krelvinaz said:
Don't see how locking and re-unlocking would make a difference.
Click to expand...
Click to collapse
I'm running out of options.
Here is the radio from the leak on 5/2 for those of you who would like to try it.
http://www.mediafire.com/?93i6ppvasdpetet
MD5: cd59d504b81aa2ac7e8aaf5f5fd017d4
As has been stated, these radios are not updated from the 3.11 RUU leak. If you are already on that RUU you will not see a difference.
If you flash to the 3.13 RUU then you will most likely see an improvement due to the following files in the RUU being updated:
Boot.img
hboot
initramfs
Aside from those those the RUU appears to be pretty much exactly the same as the 3.11 release.
Warning: I am not responsible for any damage you do to your phone. Flashing radios can leave your phone inoperable if something goes wrong.
Installation:
REQUIRES S-OFF
1. Rename zip to PH98IMG.zip and put it on an SD card.
2. Unplug any USB cables from your phone, Open the phone, and remove the battery.
3. Insert the SD card with the zip file on it into your phone and reinsert your battery.
4. Hold down the VOL-DOWN and POWER buttons until your phone turns on and enters hboot.
5. Hboot will scan for the file. Once it finds it, press the VOL-UP key to flash.
6. Wait for the process to complete.
7. Press power once hboot prompts you.
8. Enjoy the speed (hopefully)
I am seeing a vast improvement running the 3.13 RUU with this radio. I have not tried it in other ROM or RUU versions.
On 3.13 RUU I am getting 10+mb down / 2+mb up in my lead paint coated apartment.
On 3.11 RUU I was lucky to even get an LTE signal.
Please check out superchilpil's post if you want the whole leak: http://forum.xda-developers.com/showthread.php?t=1614366
Have a link?
jefffeely said:
Here is the radio from the leak on 5/2 for those of you who would like to try it.
I am seeing a vast improvement running the 3.13 RUU with this radio. I have not tried it in other settings.
Click to expand...
Click to collapse
a link would help and maybe noob instructions
Changing radios in the passed caused 4G issues. So be warned!!
Yeah, but folks were going back to GB right?
jefffeely said:
Here is the radio from the leak on 5/2 for those of you who would like to try it.
I am seeing a vast improvement running the 3.13 RUU with this radio. I have not tried it in other settings.
Click to expand...
Click to collapse
Can ya share a ruu link?
Sent from my ADR6425LVW using xda premium
My thread has the new leak with the hboot and radios, I've upgraded from the gb firmware with no issues
If you do try it and encounter issues I've attatched the stock recovery, use it and factory reset
The hboot doesnt have the extra fastboot commands so if you need them then down flash it
Sent from my ADR6425LVW using Tapatalk 2
Irieone said:
Have a link?
Click to expand...
Click to collapse
I has talent.
Flyhalf205 said:
Changing radios in the passed caused 4G issues. So be warned!!
Click to expand...
Click to collapse
Flashing the entire 3.13 ICS leak RUU fixed the radio issues I was having. I hadn't had a good connection since the original stock.
Definitely have no idea how the new radios will work with other builds though.
Do we need to be s-off for this? Or can we just set this up as a ph98img?
Sent from my ADR6425LVW using Tapatalk 2
nhugh406 said:
Do we need to be s-off for this? Or can we just set this up as a ph98img?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
s-off
Ahh. Ty sirs!
Sent from my ADR6425LVW using Tapatalk 2
so this will work with this right?
http://www.scottsroms.com/downloads.php?do=file&id=111
Is this the full radio set now?
When 1st posted it mentioned that it lacked the lte piece.
QBall45 said:
Is this the full radio set now?
When 1st posted it mentioned that it lacked the lte piece.
Click to expand...
Click to collapse
Yup it is the whole thing now.
Can you post the MD5 for the download. I always check. Not checking is like not using protection.
jm700wx said:
Can you post the MD5 for the download. I always check. Not checking is like not using protection.
Click to expand...
Click to collapse
cd59d504b81aa2ac7e8aaf5f5fd017d4 there ya go.
Thank You Sir!!! Time to flash!!!
I don't think that it has been mentioned yet being that radio flashing is a new thing for the Rezound. But on the Dinc one way that people were able to brick their devices was flashing the same radio on top of itself. What would happen is someone would flash their PH*.zip file, then not delete it off the root of the SD Card and then the next time they went in to their bootloader it would still be there and prompt them to update. They would say Yes and then get bricked.
Not sure if that is the same for the Rezound, but I would hate to hear about someone bricking their phone because of this. So remember to immediately remove your PH98IMG.zip after flashing your radios guys.
Let me know if y'all experience data issues
Sent from my ADR6425LVW using Tapatalk 2
So I decided to flash the new 4.xx firmware (don't know the rest of the numbers off the top of my head) and I flashed clean rom DE 1.4. Yes I did flash the new rom that was provided but I need the battery life that clean rom offers.
The phone randomly reboots. On maps usually but sometimes on other things. Even just sitting there it will reboot. I have un-installed the map updates as well.
I am S-Off running the newest firmware on 2.27.
Any idea what may be causing these rebooted? Can it be clean roms capability to mesh with this new firmware?
Thanks in advance.
996
Sent from my ADR6425LVW using xda app-developers app
I'm not overly familiar with CleanRom but it would be my guess it was based off one of the previous to global leaks. Therefore it would have an older kernel that is causing the Maps issue to resurface. There are only a couple of ROMs that have been based on the post global release.
Sent from my ADR6425LVW using xda app-developers app
Maps latest update causes reboots on the rezound. Try uninstalling
Sent from my ADR6425LVW using Tapatalk 2
if you are going to use DE 1.4 you need to flash the older kernel from .10 or .12
i ran into this problem too on a friends device.
I will give it a go. (flashing the older kernel)
now time to find it.
CleanRom DE should have came with a kernel already, did you flash it new or restore it? Are you s-off?
I flashed it new. And yes I am S-Off.
This was my process:
Flash the global update.
Flash the new recovery.
Flash clean rom DE 1.4.
Still getting reboots.
996 said:
I flashed it new. And yes I am S-Off.
This was my process:
Flash the global update.
Flash the new recovery.
Flash clean rom DE 1.4.
Still getting reboots.
Click to expand...
Click to collapse
What's the current kernel version showing in Settings, About phone?
Check the CleanRom zip to see if it's got a PH98IMG.zip file in it, if so, flash that via the bootloader to get the right kernel.
As mentioned above, the latest updates to Maps is causing reboot issues also.
I will check and do that.
I will also let you know how it goes. Thanks you.
Sent from my ADR6425LVW using xda app-developers app
mjones73 said:
What's the
Check the CleanRom zip to see if it's got a PH98IMG.zip file in it, if so, flash that via the bootloader to get the right kernel.
As mentioned above, the latest updates to Maps is causing reboot issues also.
Click to expand...
Click to collapse
Couldn't find a PH98IMG.zip file in it. I even tried flashing the 3.13 one and it just wouldn't do it via bootloader.
It is my opinion that you should use a ROM that is intended and recommended for your version of the operating system.
So reinstall 4.03.605.2 ruu zip file.
Install it twice in a row and boot up normally.
Then pick a ROM which is recommended for use with 4.03.605.2
Scott is no longer making Cleanroms for the rezound. Pick something else, or perhaps try enjoying the stock experience.
Regards,
Howard
P.S. 4.03.605.2 changed every category of firmware and software in the phone. The mismatching you are trying to do is begging for trouble. and you have trouble.
HowardZ said:
It is my opinion that you should use a ROM that is intended and recommended for your version of the operating system.
So reinstall 4.03.605.2 ruu zip file.
Install it twice in a row and boot up normally.
Then pick a ROM which is recommended for use with 4.03.605.2
Scott is no longer making Cleanroms for the rezound. Pick something else, or perhaps try enjoying the stock experience.
Regards,
Howard
P.S. 4.03.605.2 changed every category of firmware and software in the phone. The mismatching you are trying to do is begging for trouble. and you have trouble.
Click to expand...
Click to collapse
Why would you need to run the RUU yet again, he's already updated his firmware/radios/etc...
---------- Post added at 12:24 AM ---------- Previous post was at 12:20 AM ----------
996 said:
Couldn't find a PH98IMG.zip file in it. I even tried flashing the 3.13 one and it just wouldn't do it via bootloader.
Click to expand...
Click to collapse
Flashing the 3.13 what?
If you look at the CleanRom DE 1.4 thread, the kernel gets installed automatically if you're s-off, in the event you're s-on, it's here in PH98IMG.zip form for flashing via the bootloader - http://www.myandroidfiles.com/Downloads/Rezound/3.14.605.5/PH98IMG.zip
I will try that ASAP and keep you posted. Thank you!
996
Sent from my ADR6425LVW using xda app-developers app
I have an HTC rezound that was unlocked and rooted by HTC dev method. It has the 2.28.0000 hboot and every ruu I find and try to use tells me hboot failed because mine is to new. I have searched for 2 days on this subject and the reason I am returning to stock is because I can't get into diag mode to flash to cricket. When I enter ##diag it says no network. ##program does nothing either. If anyone could point me in the right direction it would be appreciated.
Sent from my Galaxy Nexus using xda app-developers app
jhr5474 said:
I have an HTC rezound that was unlocked and rooted by HTC dev method. It has the 2.28.0000 hboot and every ruu I find and try to use tells me hboot failed because mine is to new. I have searched for 2 days on this subject and the reason I am returning to stock is because I can't get into diag mode to flash to cricket. When I enter ##diag it says no network. ##program does nothing either. If anyone could point me in the right direction it would be appreciated.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
All ruu's posted here dont work....pm me...i have all the needed files...and i'll guide you through this....your big error that your doing is your going to need to relock the bootloader before doing anything...leaving it unlocked will cause a soft brick
I already relocked the bootloader and it still failed. I am not a total noob flashed lots of radios, hboots, built sense ROMs. This one has me stumped though.
Sent from my Galaxy Nexus using xda app-developers app
jhr5474 said:
I already relocked the bootloader and it still failed. I am not a total noob flashed lots of radios, hboots, built sense ROMs. This one has me stumped though.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
ok an ruu is an exe file not a zip....again i have the files if needed and can show you how...also what you may not be doing whille running the ruu is placing the phone in bootloader then press the fastboot tab...once it says fastboot usb then run the ruu.exe
He is S-ON guys.
jhr5474 said:
I already relocked the bootloader and it still failed. I am not a total noob flashed lots of radios, hboots, built sense ROMs. This one has me stumped though.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
and yes you must be s-off to do this thanks @Flyhalf205
REV3NT3CH said:
and yes you must be s-off to do this thanks @Flyhalf205
Click to expand...
Click to collapse
So, the OP cannot do the full RUU thing.
Can't he just do a factory reset and then boot to one of the custom recoveries and re-flash the latest OTA?
cheers,
john
No op's links have broken software...I have the needed files on my dropbox and media fire account...and no all factory reset does is wipe all data and setting for ROM...and may cause custom ROMs to not boot...ota is only achievable if on stock ROM and there is an update...however I have all those proper files too
Sent from my R3D D347H 4.3 using xda app-developers app
Got it.
One last question, though, since I'm not that savvy...
REV3NT3CH said:
ota is only achievable if on stock ROM and there is an update...
Click to expand...
Click to collapse
...I didn't upgrade to the latest OTA from a previous OTA---I was on the Global Leak---and I installed the ROM found here with absolutely no problems after manually upgrading the firmware to the latest, which is what the OP is on. Fwiw, that ROM still appears to be available via the link in Post 1 of that thread.
cheers,
john
jrredho said:
Got it.
One last question, though, since I'm not that savvy...
...I didn't upgrade to the latest OTA from a previous OTA---I was on the Global Leak---and I installed the ROM found here with absolutely no problems after manually upgrading the firmware to the latest, which is what the OP is on. Fwiw, that ROM still appears to be available via the link in Post 1 of that thread.
cheers,
john
Click to expand...
Click to collapse
that isnt a pure stock ota bud...thats a rom made with includes from it and rooted
This might sound stupid, but your objective here really is to get stockish, correct? With your HBoot you could use this ROM:
http://forum.xda-developers.com/showthread.php?t=2260154
Just make sure to flash boot.img afterwards via fastboot. This is as close to pure stock (only root added) as you can get without S-Off or other trickery. It should suffice for the requirements of the OP.
Sent from my Nexus 4 using XDA Premium 4 mobile app
I've been trying to deal with this problem over in the liquidsmooth thread, but it's clear now that my problems are not related specifically to the rom and that thread isn't really the place for it.
I've lost all cell connectivity. Calls, texts, data, everything. The liquid rom had been working for me for over a week. I've reverted to previous roms both with new flashes and using restore files. I've tried a different recovery. Every time, it acts like I don't have a sim card.
I was suspecting that my sim might be bad, but back on the liquidsmooth thread, it was suggested that I need to RUU back to stock and start over. I'd be willing to do that except the only way suggested was really complicated. I'm S-on and it included ubuntu and the wire trick to get s-off, which I'm hesitant to do. I searched and found another thread with instructions to run an RUU while still s-on, and it seems like it would have worked except that my hboot is newer than the RUU used, and I've been unable to find a newer one.
I tried flashing the stock rom above and flashing the stock recovery that I had from when I first rooted several months ago. It still thinks I don't have a sim card, but otherwise it booted fine until I re-locked to bootloader. Then it wouldn't boot anymore. I guess it still knows that those versions of hboot, the recovery, and the rom don't quite go together.
Is there an RUU that will work with hboot 2.28 to "un-root" my phone without downloading a second operating system and performing surgery on my phone? Are the correct stock rom and recovery out there that I can flash and re-lock? Is there a way to know if that is actually the problem if if it is just my sim card? Are there any other ideas to get my phone functioning again?
Please help!
vigor pvt ship s-on rl
hboot-2.28.0000
radio-2.23.10.0123r/2.23.1.124r
OpenDsp-v1.4.6.0.7708.00.0507
eMMC-boot
Sep 20 2012,17:40:22
There is no RUU for your hboot, need to s-off...
If your SIM is bad, get a new one from Verizon.
Also, is the battery cover on?
Sent from my ADR6425LVW using Tapatalk
mjones73 said:
There is no RUU for your hboot, need to s-off...
If your SIM is bad, get a new one from Verizon.
Also, is the battery cover on?
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
On that note... Are using a stock battery cover? Some aftermarket ones are questionable at best. Also, try another SIM, Verizon will replace it free.
Sent from my Nexus 4 using XDA Premium 4 mobile app
acejavelin said:
On that note... Are using a stock battery cover? Some aftermarket ones are questionable at best. Also, try another SIM, Verizon will replace it free.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried using a friend's good sim card and it didn't work. Yes, I'm using the stock battery cover. I guess I'll have to do s-off so I can RUU back to stock.
Ugh . . . This has become so much more than I ever intended to get myself into
amschmid said:
I tried using a friend's good sim card and it didn't work. Yes, I'm using the stock battery cover. I guess I'll have to do s-off so I can RUU back to stock.
Ugh . . . This has become so much more than I ever intended to get myself into
Click to expand...
Click to collapse
You didn't answer my question, is it on the phone while you're testing your connection. Dumb question I know, antenna's are in it though and I've caught people leaving it off and not getting a signal then wondering why...
mjones73 said:
You didn't answer my question, is it on the phone while you're testing your connection. Dumb question I know, antenna's are in it though and I've caught people leaving it off and not getting a signal then wondering why...
Click to expand...
Click to collapse
Sorry, I missed that part of the question. We did it pretty quick, but I think I did put the battery cover. Also, it's not just getting no signal, there is an icon in the notification bar and a big message on the lock screen says I have no sim card at all. That has never happened before, even with the battery cover off. As I look back I realize I failed to mention that important detail. I guess it still couldn't hurt to try a brand new sim card before taking the plunge into s-off. Even if that isn't the problem, at least I'll know for sure, and as you pointed out, its easy and free.