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
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.
I have an Evo 3D with HBoot 1.5, S-On, HTC Unlocked, running the latest 4ext recovery.
The short story:
I can't get any ICS roms running. They all boot, then get to the lock screen, then reboot. No problems anywhere else. If I recover (to my fresh rom), or flash a different GB rom, all works fine.
Longer version:
I currently use fresh rom, and just updated to the latest software by relocking, running the RUU, then seeing if there are any newer OTA. (there wasn't). Re-unlocked via HTC, then flashed twrp, rooted, installed 4ext, then started flashing ICS roms without success. I had tried to run them on the previous firmware, but ran into the same issue.
If it matters: I'm on a mac. I have a PC, but I prefer this. I've already got it set up for fastboot, adb and everything... I see the downgrade instructions, but I'm just a little hesitant to brick my device. Same with the j-bear...
X219c said:
I have an Evo 3D with HBoot 1.5, S-On, HTC Unlocked, running the latest 4ext recovery.
The short story:
I can't get any ICS roms running. They all boot, then get to the lock screen, then reboot. No problems anywhere else. If I recover (to my fresh rom), or flash a different GB rom, all works fine.
Longer version:
I currently use fresh rom, and just updated to the latest software by relocking, running the RUU, then seeing if there are any newer OTA. (there wasn't). Re-unlocked via HTC, then flashed twrp, rooted, installed 4ext, then started flashing ICS roms without success. I had tried to run them on the previous firmware, but ran into the same issue.
If it matters: I'm on a mac. I have a PC, but I prefer this. I've already got it set up for fastboot, adb and everything... I see the downgrade instructions, but I'm just a little hesitant to brick my device. Same with the j-bear...
Click to expand...
Click to collapse
The fix thread was removed (C. Goodman). You can try using Chad's HTC Leak RLS1 kernel with the ICS rom.
Wipe > Flash ICS Rom > Flash Rls1Leak kernel
G.Newton said:
The fix thread was removed (C. Goodman). You can try using Chad's HTC Leak RLS1 kernel with the ICS rom.
Wipe > Flash ICS Rom > Flash Rls1Leak kernel
Click to expand...
Click to collapse
This is the only way to avoid bootloader on 1.5 without getting s-off
Thanks for the quick reply...
So, are there any currently available kernels that fix this, since Chad's been gone for a little bit?
X219c said:
Thanks for the quick reply...
So, are there any currently available kernels that fix this, since Chad's been gone for a little bit?
Click to expand...
Click to collapse
You can find Chad's stuff on infectedrom.com.
Sent from my PG86100 using Tapatalk 2
coal686 said:
You can find Chad's stuff on infectedrom.com.
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
heres the link to the kernels and all of chads stuff androidfilehost.com/main/EVO_3D_Developers/.chad.goodman/
joecrusher said:
heres the link to the kernels and all of chads stuff androidfilehost.com/main/EVO_3D_Developers/.chad.goodman/
Click to expand...
Click to collapse
He used to be insistent that you register through infectedrom.com, but maybe not anymore.
So im stuck. Most ROMs are now rebased using the latest firmware update 2.13, im still on 1.22 stock rooted custom recovery TWRP. When i try to update OTA it takes me to my recovery....?? what do i do, i tried the RUU but that failed as expected because im rooted, right? I can't flash the update.zip cause im not s-off, and apparently the hboot version i have wont work on panda. any suggestions?
Never accept an OTA while rooted. Never.
And dont unroot to accept an OTA.
If you are on h-boot 1.15 you are stuck on the current radio and firmware. You can still flash the newer ROMS. (FASTBOOT FLASH THE NEW KERNEL!!!)
If you are on 1.12 you can flash whatever you'd like
yes im on hboot 1.15, what do u mean flash the new kernel? i was reading for example on meanrom that you have to fastboot flash the kernel separately, after the ROM, is this what u mean?
acontreras said:
yes im on hboot 1.15, what do u mean flash the new kernel? i was reading for example on meanrom that you have to fastboot flash the kernel separately, after the ROM, is this what u mean?
Click to expand...
Click to collapse
Exactly. http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-a.html
Oh! i see! luckily i am comfortable with fastboot. one more question since we are here...flashing the rom will be the same through recovery, but is it better to use the internal storage or external storage to flash from? or does it even matter..
acontreras said:
Oh! i see! luckily i am comfortable with fastboot. one more question since we are here...flashing the rom will be the same through recovery, but is it better to use the internal storage or external storage to flash from? or does it even matter..
Click to expand...
Click to collapse
always place rom on external. if you superwipe before a flash you will erase rom on internal.
what should we use for internal then? i at least use it for my nands..is that bad?
acontreras said:
So im stuck. Most ROMs are now rebased using the latest firmware update 2.13, im still on 1.22 stock rooted custom recovery TWRP. When i try to update OTA it takes me to my recovery....?? what do i do, i tried the RUU but that failed as expected because im rooted, right? I can't flash the update.zip cause im not s-off, and apparently the hboot version i have wont work on panda. any suggestions?
Click to expand...
Click to collapse
I have s off on my phone but my wife wanted root and the latest software. Here's what I did. She was on 1.22 I didn't unroot as it was pointless.
1 relock bootloader using (fastboot oem lock)
2 download latest ruu with new ota and run it. Your firmware and base rom will be updated.
3 unlock bootloader again using htcdev.
4 use fastboot again to re flash twrp
5 use twrp to re flash supersu
If you don't understand the process research it. That's how I figured it out. There are plenty of instructions on xda.
Sent from my Amazon Kindle Fire using Tapatalk 2
---------- Post added at 09:05 PM ---------- Previous post was at 08:43 PM ----------
acontreras said:
So im stuck. Most ROMs are now rebased using the latest firmware update 2.13, im still on 1.22 stock rooted custom recovery TWRP. When i try to update OTA it takes me to my recovery....?? what do i do, i tried the RUU but that failed as expected because im rooted, right? I can't flash the update.zip cause im not s-off, and apparently the hboot version i have wont work on panda. any suggestions?
Click to expand...
Click to collapse
Keep in mind the process I just outlined will put you back to bone stock. If you don't own titanium backup or my backup pro you will lose all your apps. Once you're on the new base you can flash any of the new sense roms like meanrom
There's a lot of little details I didn't cover. I'll leave that up to you. Just suffice it to say, you can do all upgrades with htcdev that you can do with s off. It just takes longer and it's a bit more complicated than having s off.
Sent from my EVO using Tapatalk 2
baknblack said:
I have s off on my phone but my wife wanted root and the latest software. Here's what I did. She was on 1.22 I didn't unroot as it was pointless.
1 relock bootloader using (fastboot oem lock)
2 download latest ruu with new ota and run it. Your firmware and base rom will be updated.
3 unlock bootloader again using htcdev.
4 use fastboot again to re flash twrp
5 use twrp to re flash supersu
If you don't understand the process research it. That's how I figured it out. There are plenty of instructions on xda.
Sent from my Amazon Kindle Fire using Tapatalk 2
---------- Post added at 09:05 PM ---------- Previous post was at 08:43 PM ----------
Keep in mind the process I just outlined will put you back to bone stock. If you don't own titanium backup or my backup pro you will lose all your apps. Once you're on the new base you can flash any of the new sense roms like meanrom
There's a lot of little details I didn't cover. I'll leave that up to you. Just suffice it to say, you can do all upgrades with htcdev that you can do with s off. It just takes longer and it's a bit more complicated than having s off.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
for sure bro thanks! thats the part that sucks is having to do it the long way but hey, its an adventure in itself. what i did was flash a version of meanrom for my base and then flashed a more recent one, then fastboot the kernel, and bada bing bada boom, it is successfully stable. now if i flash another rom will i have to reflash the kernel in the zip?
acontreras said:
for sure bro thanks! thats the part that sucks is having to do it the long way but hey, its an adventure in itself. what i did was flash a version of meanrom for my base and then flashed a more recent one, then fastboot the kernel, and bada bing bada boom, it is successfully stable. now if i flash another rom will i have to reflash the kernel in the zip?
Click to expand...
Click to collapse
don't think so as long as it's the same base with the stock kernel.
What I told you will get you the new radios etc if ya want em. my guess is the phone will run fine with the older radios but it's just a guess
acontreras said:
what should we use for internal then? i at least use it for my nands..is that bad?
Click to expand...
Click to collapse
yes. what if rom your flashing wipes? then you loose all your nandroid backups. i backup mine to external sd.
I've been scouring the internet for the last week trying to find a solution, but nothing has worked so far. I'm curious to know if anyone has been able to downgrade his/her software to 3.14.605.12 from the global leak (4.03.605.2) with S-ON. I've tried flashing through fastboot, recovery, flashing a patch to downgrade the main version number, flashing a custom rom first, and anything else I could find in the forums, but everything has failed. I'm trying to avoid going S-OFF. Is there any possible way to make this happen? Thanks.
ps - Sorry in advance if I somehow missed the thread where this has already been discussed at great length.
It isn't possible to downgrade with out being s-off.
Sent from my ADR6425LVW using Xparent Skyblue Tapatalk 2
Just out of curiosity, why are you trying to downgrade? I'm s-on and on the global leak as well.
terrible battery life and random reboots.
yo
Unless you just don't want to do it, S-0ff is really pretty
easy and has many benefits. If you read and re-read the
instructions, you'll find the steps manageable and a nice reward
for your efforts.
m2hartman said:
terrible battery life and random reboots.
Click to expand...
Click to collapse
Hm... well I don't have random reboots and I don't feel I have terrible battery life, but that can be subjective I guess. But I never have wifi on so I'm on 4G all the time, don't turn off bluetooth, don't have much syncing lately.
Have you tried all the settings tips for better battery life?
Are you tweaking your kernel and causing the reboots from that?
feralicious said:
Hm... well I don't have random reboots and I don't feel I have terrible battery life, but that can be subjective I guess. But I never have wifi on so I'm on 4G all the time, don't turn off bluetooth, don't have much syncing lately.
Have you tried all the settings tips for better battery life?
Are you tweaking your kernel and causing the reboots from that?
Click to expand...
Click to collapse
I ran the global update completely stock with amon ra and superuser installed. The only tweak I made to the software was to disable some bloat. I keep just about everything off (including 4g), and never turn up my brightness past 50%. I can get about two days of use like that with my thunderbolt (stock battery). I only really rooted to abuse 4g tethering at my house; I'm not exactly glued to my phone during the day. I updated my rezound because the auto-rotate setting kept crashing sense on 3.14.605.12. I guess it's entirely possibly I bought the worst rezound ever. I guess I'll just have to wait and see if they release another official build higher than 4.03.605.2.
Anyone want to buy a rezound? Works great! Like new!
Only advise I can give you. Fastboot flash the stock recovery, do a factory reset. Then flash your custom recovery and reflash your rom. No wipes needed while in custom recovery. Careful though, this will wipe your internal SD.
Snuzzo said:
Only advise I can give you. Fastboot flash the stock recovery, do a factory reset. Then flash your custom recovery and reflash your rom. No wipes needed while in custom recovery. Careful though, this will wipe your internal SD.
Click to expand...
Click to collapse
I am trying to accomplish the same deal. I want the newest radios from the latest OTA, but I'm stuck on the last Global leak with S-ON.
From what I understand, I have to:
1. Relock my bootloader (not entirely sure how)
2. Flash the latest RUU (all i can find is an .exe file, while all the instructions i find tell me to rename the file to PH98IMG.zip and i'm pretty sure it doesn't work like that with the .exe)
3. Install custom recovery and then re-root.
Can anyone please clarify the procedures? Do I have to reflash stock recovery at anytime during this process? If so, where can I find that file?
Thanks for your help!
Which RUU do you want to run? I've seen the 3.14.605.12 as an .exe and the global as a PH98IMG. You won't be able to run the .12 since you have already upgraded to the global and you are s-on.
The only way for you to get the OTA radios is to s-off since you can't downgrade. I wouldn't worry about it unless you are having bad signal or battery life as the OP. If you are, then follow Snuzzo's instructions to clear everything and start with a fresh install of the ROM (or global RUU if you want stock).
@Blazin
can't be accompliahed without going through the s off procedure first.
Sent from my ADR6425LVW using Xparent Green Tapatalk 2
Snuzzo said:
@Blazin
can't be accompliahed without going through the s off procedure first.
Sent from my ADR6425LVW using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
I'm on Neo's Infection 2.3 and I get pretty crappy battery life with the global radios. Neo recommends using the latest radios if you're experiencing poor battery performance.
I guess it's time to find a piece of wire and re-read the S-OFF instructions. I came from a Incredible and we didnt have to short our phone out to achieve S-OFF.
Thanks for your help guys.
My Plan of Attack
Tomorrow's my first day off in a while so I'll hopefully have time to do all this.
Before I start, I want to make sure I've got everything in order.
Goal: Downgrade from Global RUU with S-On to latest ICS RUU with S-Off
1. Relock my bootloader
2. Re-flash global RUU
3. S-Off
4. Flash latest ICS RUU
5. Unlock, install recovery, root
Does that sound right?
You have to root the global ruu and as a precaution, back up your internal/external SD contents along with your daily apps. Once you're s off you don't have to unlock if you flash a patched hboot.
5) flash patched hboot , flash recovery, choose a ROM or flash ota ruu + root + install latest busybox.
Sent from my Nexus 7 using Tapatalk HD
Snuzzo said:
You have to root the global ruu and as a precaution, back up your internal/external SD contents along with your daily apps. Once you're s off you don't have to unlock if you flash a patched hboot.
5) flash patched hboot , flash recovery, choose a ROM or flash ota ruu + root + install latest busybox.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
When I flashed the global RUU, i used Hansoon's all in one toolkit to unlock and root. Can I use that to root the RUU before S-OFF and in step 5?
I've never had to flash a patched HBOOT before. Should I just use the one provided by the Juopunut team?
Use theirs and you wouldn't have been able to flash before. As far as rooting its as easy as flashing the CWM-SuperSU flash able zip. Remember tho you have to be cautious when doing the ICS ruu, it will prompt for you to take an ota.
Sent from my Nexus 7 using Tapatalk HD
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!