Will dev's now require to have S-OFF to flash their ROM's, Kernels, etc. ?
Or will you guys provide options when flashing based on if you're S-ON/S-OFF?
I have not done the "S-OFF" process on my Rezound yet and don't feel that I really need to do it since I am completely and totally happy with Ineffabilis GB with the last official OTA radios. I am patient enough to wait for the official ICS OTA update plus I'm scared I might brick my phone during the process
S-OFF is only if you need to change radios. If you like the one you got then your phone if went to the ICS leak and had problems then you can go back to GB.
Sent from my CleanRom DE 1.2
DigiDave said:
Will dev's now require to have S-OFF to flash their ROM's, Kernels, etc. ?
Or will you guys provide options when flashing based on if you're S-ON/S-OFF?
I have not done the "S-OFF" process on my Rezound yet and don't feel that I really need to do it since I am completely and totally happy with Ineffabilis GB with the last official OTA radios. I am patient enough to wait for the official ICS OTA update plus I'm scared I might brick my phone during the process
Click to expand...
Click to collapse
Im sure the developer will note on their thread if it will be needed. I highly doubt it will be required unless flashing critical files.
Sent from my Htc Rezound
Follow me on twitter @lmrtech
DigiDave said:
Will dev's now require to have S-OFF to flash their ROM's, Kernels, etc. ?
Or will you guys provide options when flashing based on if you're S-ON/S-OFF?
I have not done the "S-OFF" process on my Rezound yet and don't feel that I really need to do it since I am completely and totally happy with Ineffabilis GB with the last official OTA radios. I am patient enough to wait for the official ICS OTA update plus I'm scared I might brick my phone during the process
Click to expand...
Click to collapse
The only difference could be that you would still have to use the PH98IMG method or use fastboot to flash the appropriate kernel for the ROM instead of just doing it all with the ROM flash.
OLDsJUNKIE said:
The only difference could be that you would still have to use the PH98IMG method or use fastboot to flash the appropriate kernel for the ROM instead of just doing it all with the ROM flash.
Click to expand...
Click to collapse
...and making and restoring backups will include the kernels with s-off.
DigiDave said:
Will dev's now require to have S-OFF to flash their ROM's, Kernels, etc. ?
Or will you guys provide options when flashing based on if you're S-ON/S-OFF?
I have not done the "S-OFF" process on my Rezound yet and don't feel that I really need to do it since I am completely and totally happy with Ineffabilis GB with the last official OTA radios. I am patient enough to wait for the official ICS OTA update plus I'm scared I might brick my phone during the process
Click to expand...
Click to collapse
I hope they require it. The inability to flash boot images via recovery has been a major roadblock for development and there is no reason for it to continue. There is no reason not to S-OFF. If you don't S-OFF your device then you will have to fastboot flash everything or manually create your own PH98IMG files.
con247 said:
I hope they require it. The inability to flash boot images via recovery has been a major roadblock for development and there is no reason for it to continue. There is no reason not to S-OFF. If you don't S-OFF your device then you will have to fastboot flash everything or manually create your own PH98IMG files.
Click to expand...
Click to collapse
Just curious. How has flashing method been a roadblock to development? I'm not trying to be a smartass, I just don't see it.
Related
I am on Clean ROM ICS, with the leak, but want to go back to stock and start the HTC Dev process over for GB. What do I need to do step by step? Is there a guide?
At work, so I don't have much time to search. So if can assist I'd really appreciate it.
Are you on Clean Rom with the old Firmware patch?
drtchocky said:
I am on Clean ROM ICS, with the leak, but want to go back to stock and start the HTC Dev process over for GB. What do I need to do step by step? Is there a guide?
At work, so I don't have much time to search. So if can assist I'd really appreciate it.
Click to expand...
Click to collapse
Are you S-off ? If so did you take their HBoot or still using the stock leak hboot ? If your using their Hboot, then just download the 2.011xxxxxx OTA RUU connect phone and while in bootloader in fastboot run the RUU exe . It will ask you a few prompts .. then flash your phone .
If still on stock leak hboot.. have to relock so from a command prompt type while phone is in fastboot.. type fastboot oem lock . Phone will relock then you can run the RUU from there.
If not S-off and your on the leak , there is no way to go back to RUU GB until you S-off.
I feel kinda dumb.... I am on the first ICS leak... is that what you guys mean? The first thing Scott released with that lengthy procedure to get it running.
drtchocky said:
I feel kinda dumb.... I am on the first ICS leak... is that what you guys mean? The first thing Scott released with that lengthy procedure to get it running.
Click to expand...
Click to collapse
No reason to feel dumb, but if you haven't performed the S-off procedure you can't downgrade using the GB RUU. I think you can just go back to running GB roms though, just need a patch to fix the SD card issue , but you will still have the leak Firmware and Radios.
If I s-off... should I dare try, then downgrading is a real possibility?
drtchocky said:
I feel kinda dumb.... I am on the first ICS leak... is that what you guys mean? The first thing Scott released with that lengthy procedure to get it running.
Click to expand...
Click to collapse
Don't feel dumb dude. I have had my Rezound for a month and on the ICS leak for about 3 weeks. Tried Evita then restored my ICS leak and I am still confused on all the firmwares and patches and whatever else. And somehow I successfully did all that without any problems. It seems every time I read something, it contradicts what I thought beforehand.
Ok I'm all set now, I got everything flashed, but now I sill have question.
I started with the ENG H boot then I wen to the safer hacked one.
I'm looking for ROMS now and they have a PH98IMG file. Is that the kernel or updated firmware? I wouldn't want to flash different firmware right?
also what about the old firmware patch for ICS roms?
http://forum.xda-developers.com/showthread.php?t=1614180
Do I need to be using that as Im still on the GM H boot?
and finally what about mainver errors? since Im s off will that still warn me?
I just want to be careful not to do anything I shouldn't now that most of the safety nets are gone.
Also sorry of my questions are silly, its late at work and I've been starting at this screen all day. Its time to go.
thanks
loki993 said:
Ok I'm all set now, I got everything flashed, but now I sill have question.
I started with the ENG H boot then I wen to the safer hacked one.
I'm looking for ROMS now and they have a PH98IMG file. Is that the kernel or updated firmware? I wouldn't want to flash different firmware right?
also what about the old firmware patch for ICS roms?
http://forum.xda-developers.com/showthread.php?t=1614180
Do I need to be using that as Im still on the GM H boot?
and finally what about mainver errors? since Im s off will that still warn me?
I just want to be careful not to do anything I shouldn't now that most of the safety nets are gone.
Also sorry of my questions are silly, its late at work and I've been starting at this screen all day. Its time to go.
thanks
Click to expand...
Click to collapse
ROMs generally will never have firmware present unless it specifically states otherwise (perhaps somebody will release one after an OTA if there's a new firmware update). Prior to last week, we all had S-ON (well most of us) so all ROMs came with a script that would dump the boot.img (kernel and RAMdisk) into a PH98IMG.zip, then reboot to bootloader so you can flash it.
Use the old firmware patch for ICS ROMs only if you are on HBOOT 2.11 or lower.
I'm not sure about mainver issues... I don't think they matter now... but if you do get that error there's a simple fix thats been around for awhile.
I am on 2.11 so I would need the patch. Is it ok to use even it I'm not on am ics Rom, should I flash it just in case or wait until I need it.
Yeah I was kinda thinking the same thing about the mainver. Not sure either though
Sent from my ADR6425LVW using Tapatalk
loki993 said:
I am on 2.11 so I would need the patch. Is it ok to use even it I'm not on am ics Rom, should I flash it just in case or wait until I need it.
Yeah I was kinda thinking the same thing about the mainver. Not sure either though
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
The patch is apart of the system so you only flash it when you are going to run a ics Rom based on the ics firmware. You already have the patch files in the Rom you are running if its GB. But when you flash a new Rom the system is wiped which is why you need to flash the patch. I hope I explained that ok.
Sent from my HTC Vigor
Thanks for this thread, answered some of my nagging questions
Andro X said:
The patch is apart of the system so you only flash it when you are going to run a ics Rom based on the ics firmware. You already have the patch files in the Rom you are running if its GB. But when you flash a new Rom the system is wiped which is why you need to flash the patch. I hope I explained that ok.
Sent from my HTC Vigor
Click to expand...
Click to collapse
I understand, its ok. You right though dont know what I was thinking, of course the system gets wiped.
Im debating which ROM to run now. I was going to go with one of the BAMFs, but I also would mind a senseless ROM either.
Is it wrong that I actually kinda like Sense, I just wish it didnt bog the phone at times.
Also I thinking its probably best to say on the 2.11 firmware, that way I can still run GB if I want and go to ICS ROMS too if I want with the patch.
I like sense too especially since this is my first HTC phone so its something different for me. I had Motorola's in the past. I'm on GB firmware with the eng hboot and running ics Clean Rom.
Sent from my HTC Vigor
Well Sense is certainly an upgrade for me from TouchWiz....I miss a few things but overall it is better...
I think you would be happy with CleanROM, extremely fast and reliable ICS build. You would never know it wasn't stock.
I have my own silly question...why do I need htcdev unlocked to get s-off. Just rooted and s-offed my of MT4G for the fun of it. Seems like we should be able to s-off without official unlock support
Sent from my ADR6425LVW using xda premium
Geoi1006 said:
I have my own silly question...why do I need htcdev unlocked to get s-off. Just rooted and s-offed my of MT4G for the fun of it. Seems like we should be able to s-off without official unlock support
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Not sure about MT4G, but I don't think the control bear program can access everything it needs on the Rezound without being unlocked. Just a guess mind you .
Geoi1006 said:
I have my own silly question...why do I need htcdev unlocked to get s-off. Just rooted and s-offed my of MT4G for the fun of it. Seems like we should be able to s-off without official unlock support
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
You have to be rooted to acquire s-off. Up until this point you had to be unlocked to acquire root. Now, if you are s-off you can root without unlocking. It's a vicious circle! Lol!
I just haven't gotten to unlock since I don't have home internet access
Sent from my ADR6425LVW using xda premium
Due to WiFi issues on the release day OS, I took the 1.22 OTA and screwed root. I knew it would happen but the fixes outweighed the issues. I waited to see if root would be achieved via Regaw or the like since I didn't want to lose any of my configuration. Now... Sense 4.1 was just too tempting to pass up and since I wasn't rooted anyways, I went for it.
I decided to attempt root and start from scratch anyways as I was having random app issues and some bloat problems.
The root method from HTC Dev worked flawlessly on the new new OTA and I was able to load TWRP and SuperUser via fastboot (instructions can be found by searching as I did).
So now here is the question: where does this leave me as far as flashing ROMs... Obviously I am aware that I am S-On and know those limitations. My issue is if and where any limits may apply now that I am HBOOT 1.19. Will I be stuck with only 2.13 ROMs that we're built based on the new HBOOT or can I flash any Rom based on 2.13 (or even older revisions)? I cant risk bricking so I am asking to be cautious as well as your answers providing any new users coming in with new phones running the latest OTA.
Thanks
Why did HTC update hboot 1.15? Because they discovered an exploit flaw that we could gain S-OFF with, which is FAR better than being on HTC Dumlock. If you are not concerned with obtaining S-OFF via LazyPanda and the like, this should not be a concern.
Also, being on the new hboot means that backwards compatibility to ROMs that are not based on the new OTA could become an issue.
Sent from my LTEVO via XDA Premium
New h boot for you only means that you won't be able to get s-off for a very long time probably since nobody has figured out how to even s-off h boot 1.15 yet. You shouldn't have an issue flashing any rom from my understanding as long as it's through recovery.
Edit : I would listen to Michael on this one regarding ROMs sounds like he knows more lol.
Sent from my EVO using xda app-developers app
natefuhr said:
Due to WiFi issues on the release day OS, I took the 1.22 OTA and screwed root. I knew it would happen but the fixes outweighed the issues. I waited to see if root would be achieved via Regaw or the like since I didn't want to lose any of my configuration. Now... Sense 4.1 was just too tempting to pass up and since I wasn't rooted anyways, I went for it.
I decided to attempt root and start from scratch anyways as I was having random app issues and some bloat problems.
The root method from HTC Dev worked flawlessly on the new new OTA and I was able to load TWRP and SuperUser via fastboot (instructions can be found by searching as I did).
So now here is the question: where does this leave me as far as flashing ROMs... Obviously I am aware that I am S-On and know those limitations. My issue is if and where any limits may apply now that I am HBOOT 1.19. Will I be stuck with only 2.13 ROMs that we're built based on the new HBOOT or can I flash any Rom based on 2.13 (or even older revisions)? I cant risk bricking so I am asking to be cautious as well as your answers providing any new users coming in with new phones running the latest OTA.
Thanks
Click to expand...
Click to collapse
Yes, you will be stuck flashing 2.13 roms with the 2.13 kernel. However, you can use one of the workaround methods (fastboot, flash image gui, twrp dumlock) to flashing an older kernel, and then flash roms based on a previous OTA base.
A ROM doesn't include an HBoot though, so there shouldn't be ROM/HBoot compatibility issues, right?
No, you can flash whatever version of android you want
Rxpert said:
No, you can flash whatever version of android you want
Click to expand...
Click to collapse
I don't think that's quite right (I could be wrong though).
If he wants to flash a JB-based ROM, he will definitely have to flash the boot.img separately via one of the workarounds mentioned.
If he wants to move between Sense-based ROMs, he *might* be OK. But he will not get any tweaks the dev may have made to the kernel included with his respective ROM.
I was referring to the question above me that asked about ROMs interfering with hboots
Having an old ROM on a new hboot won't cause issues.
Naturally, you need to have a working kernel for your ROM. So yes, you'll need to make sure you have the right kernel.
If he goes from any ROM to a ROM on a different base you'll have to install the correct kernel. . But I don't think that's what he was asking
Sent from my EVO using Tapatalk 2
Got it. I thought you were replying in general.
natefuhr said:
Due to WiFi issues on the release day OS, I took the 1.22 OTA and screwed root. I knew it would happen but the fixes outweighed the issues. I waited to see if root would be achieved via Regaw or the like since I didn't want to lose any of my configuration. Now... Sense 4.1 was just too tempting to pass up and since I wasn't rooted anyways, I went for it.
I decided to attempt root and start from scratch anyways as I was having random app issues and some bloat problems.
The root method from HTC Dev worked flawlessly on the new new OTA and I was able to load TWRP and SuperUser via fastboot (instructions can be found by searching as I did).
So now here is the question: where does this leave me as far as flashing ROMs... Obviously I am aware that I am S-On and know those limitations. My issue is if and where any limits may apply now that I am HBOOT 1.19. Will I be stuck with only 2.13 ROMs that we're built based on the new HBOOT or can I flash any Rom based on 2.13 (or even older revisions)? I cant risk bricking so I am asking to be cautious as well as your answers providing any new users coming in with new phones running the latest OTA.
Thanks
Click to expand...
Click to collapse
I'd like to re-root after taking the OTA and I've searched all over for the instructions on how to load TWRP and SuperUser via fastboot, but can't find it. Can you assist?
Thanks
Rxpert said:
I was referring to the question above me that asked about ROMs interfering with hboots
Having an old ROM on a new hboot won't cause issues.
Naturally, you need to have a working kernel for your ROM. So yes, you'll need to make sure you have the right kernel.
If he goes from any ROM to a ROM on a different base you'll have to install the correct kernel. . But I don't think that's what he was asking
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Correct me if I'm wrong, but, a ROM includes a Kernel, so when you flash a ROM you're swapping kernels.
The only kernel incompatibility would be if you flashed a ROM then flashed a Kernel, then you have to be careful.
If anybody is absolutely certain that this isn't the case and not just guessing, let me know and I'll stand corrected.
pbarrett said:
Correct me if I'm wrong, but, a ROM includes a Kernel, so when you flash a ROM you're swapping kernels.
The only kernel incompatibility would be if you flashed a ROM then flashed a Kernel, then you have to be careful.
If anybody is absolutely certain that this isn't the case and not just guessing, let me know and I'll stand corrected.
Click to expand...
Click to collapse
That's true for 1.12, since it allows you to flash kernels through recovery. The newer versions don't. That's the reason for using the fastboot or dumlock workarounds. That being said, I haven't heard anyone confirm yet that these methods still work on 1.19...I'm interested to know.
Sent from my EVO LTE
I've been waiting for s-off forever, then it finally came but long story short gf saw update (hboot 1.15) and accepted and I'm wondering since there's still no s-off, and this is a very silly question but I've never used Dev unlock, is nandroid backup possible in case something does go wrong
om4 said:
I've been waiting for s-off forever, then it finally came but long story short gf saw update (hboot 1.15) and accepted and I'm wondering since there's still no s-off, and this is a very silly question but I've never used Dev unlock, is nandroid backup possible in case something does go wrong
Click to expand...
Click to collapse
From what I can tell... No. You have to run HTC Dev first in order to get to where you can load a recovery program at which point you will have already had to wipe your phone to factory defaults.
It's unfortunate and the main reason I waited so long to unlock this way but as previously stated, Sense 4.1 was too hard to pass on
om4 said:
I've been waiting for s-off forever, then it finally came but long story short gf saw update (hboot 1.15) and accepted and I'm wondering since there's still no s-off, and this is a very silly question but I've never used Dev unlock, is nandroid backup possible in case something does go wrong
Click to expand...
Click to collapse
I am amazed at how many girlfriends have their boyfriend's phone and update things... I'm beginning to think it's the same cover up as when people say, "so I have this friend who... Blah blah blah..."
Sent from my EVO using xda app-developers app
PsiPhiDan said:
I am amazed at how many girlfriends have their boyfriend's phone and update things... I'm beginning to think it's the same cover up as when people say, "so I have this friend who... Blah blah blah..."
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
no, I let her take my phone for the weekend. she went camping with her her family and I dont feel comfortable knowing shes out in the middle of no where without a phone. her phone was disconnected because she lost her job 2 months ago and Im not about to pay $135 on top of my own bill
PsiPhiDan said:
I am amazed at how many girlfriends have their boyfriend's phone and update things... I'm beginning to think it's the same cover up as when people say, "so I have this friend who... Blah blah blah..."
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Hell, I don't even let my girlfriend use my phone unless she asks nicely and I always keep an eye on her.
SoraX64 said:
Hell, I don't even let my girlfriend use my phone unless she asks nicely and I always keep an eye on her.
Click to expand...
Click to collapse
Mine doesn't even know how to use my phone...it's "confusing". IPhone ftw
Sent from my EVO LTE
pbarrett said:
Correct me if I'm wrong, but, a ROM includes a Kernel, so when you flash a ROM you're swapping kernels.
The only kernel incompatibility would be if you flashed a ROM then flashed a Kernel, then you have to be careful.
If anybody is absolutely certain that this isn't the case and not just guessing, let me know and I'll stand corrected.
Click to expand...
Click to collapse
Yes, every ROM includes a kernel.
But Hboot 1.15 and above do not let you flash things to the boot partition in recovery. The kernel goes in the boot partition. So you can't flash kernels normally through recovery.
If your on a sense ROM and flash an AOSP rom, the phone wont boot
If your on an AOSP ROM and flash a sense ROM, the phone wont boot
If your on an old base and flash a new base, the ROM will have issues (if it even boots)
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-wip.html
PsiPhiDan said:
I am amazed at how many girlfriends have their boyfriend's phone and update things... I'm beginning to think it's the same cover up as when people say, "so I have this friend who... Blah blah blah..."
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Next, we are going to hear crap like, "my pet hamster ate my nandroid thumb drive."
Sent from my LTEVO via XDA Premium
Hey guys,
So as the thread title states, I have a rooted DNA with an unlocked bootloader and now S-OFF. I'm wholly new to this whole "forcing" of an OTA upon me (by Verizon?)...so I don't know what the best course of action is. I've already flashed the radio from the OTA and I'm just waiting for an attractive custom ROM to come out before flashing one. In the meantime, what should I do? I saw this thread:
(Mod)[2.15.13] Stop/Remove Verizon OTA V2 2.04.605.2 710RD (http://forum.xda-developers.com/showthread.php?t=2149417)
Idk...I'll do it if I have to...it just seems a bit drastic in what it removes. Is there a safe way to update my firmware/kernel to that of the OTA while keeping my unlocked bootloader/root/s-off? I'm used to Nexus devices so this is all very strange to me...any help would be greatly appreciated, thanks!
mtmjr90 said:
Hey guys,
So as the thread title states, I have a rooted DNA with an unlocked bootloader and now S-OFF. I'm wholly new to this whole "forcing" of an OTA upon me (by Verizon?)...so I don't know what the best course of action is. I've already flashed the radio from the OTA and I'm just waiting for an attractive custom ROM to come out before flashing one. In the meantime, what should I do? I saw this thread:
(Mod)[2.15.13] Stop/Remove Verizon OTA V2 2.04.605.2 710RD (http://forum.xda-developers.com/showthread.php?t=2149417)
Idk...I'll do it if I have to...it just seems a bit drastic in what it removes. Is there a safe way to update my firmware/kernel to that of the OTA while keeping my unlocked bootloader/root/s-off? I'm used to Nexus devices so this is all very strange to me...any help would be greatly appreciated, thanks!
Click to expand...
Click to collapse
Would like to know what to do - I postponed my update to tomorrow, so if no one replies to this thread I am going to follow the other thread.
http://forum.xda-developers.com/showthread.php?t=2152993
According to jcase beaups and Dr_drache and zifnab its OK to take the ota with s-off
And then I'm telling you to do it at your own risk
The OTA from what I've seen (and experienced) does not lock the bootloader and also shouldn't affect the s-off according to those guys
Sent from my Nexus 7 using XDA Premium HD app
.torrented said:
According to jcase beaups and Dr_drache and zifnab its OK to take the ota with s-off
And then I'm telling you to do it at your own risk
The OTA from what I've seen (and experienced) does not lock the bootloader and also shouldn't affect the s-off according to those guys
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Yes, but I think you must be on stock rom and stock recovery. I'm on stock rom but not stock recovery. Can anyone confirm if the steps would be (for someone on stock rom, TWRP, rooted, unlocked, S-OFF):
1. Flash stock recovery
2. Update OTA
3. Flash back TWRP
Or do we need to unlock again between steps 2 and 3 or take any other steps? Or is there a flashable OTA zipped up that will update everything? I don't mind waiting by the way. Not in a huge hurry... Thanks in advance, you guys are awesome.
n8mack33 said:
Yes, but I think you must be on stock rom and stock recovery. I'm on stock rom but not stock recovery. Can anyone confirm if the steps would be (for someone on stock rom, TWRP, rooted, unlocked, S-OFF):
1. Flash stock recovery
2. Update OTA
3. Flash back TWRP
Or do we need to unlock again between steps 2 and 3 or take any other steps? Or is there a flashable OTA zipped up that will update everything? I don't mind waiting by the way. Not in a huge hurry... Thanks in advance, you guys are awesome.
Click to expand...
Click to collapse
should work with stock recovery (you might need the stock kernel too not sure)
If you flash the whole OTA package you'll also need /system to be mostly stock, along with stock recovery and kernel.
Or, you could try what I did and download the OTA from the dev section, remove /system, /boot (kernel), and /recovery updates from it and flash the new zip from RUU mode (fastboot oem rebootRUU). However, this is somewhat involved and not user friendly. Also, if you do this, when you flash it it usually says to "flush the update again", in which case you simply run the fastboot flash zip [file] again (it *might* result in a brick if not done correctly).
Better yet, chances are a dev will put together a firmware package which can be easily flashed with a guide on how to do it. If you aren't confident about flashing the firmware, its best to wait for something like this.
Hm...okay...if I just wait until the day I "deferred" the OTA until, will I be able to defer again (and again, and again, etc)? If so, I can just keep doing that until there's a safe way to flash either the update itself or a custom ROM that interests me.
I just want to add that this whole situation is absurd.
mtmjr90 said:
Hm...okay...if I just wait until the day I "deferred" the OTA until, will I be able to defer again (and again, and again, etc)? If so, I can just keep doing that until there's a safe way to flash either the update itself or a custom ROM that interests me.
I just want to add that this whole situation is absurd.
Click to expand...
Click to collapse
Go to the droid original dev thread and get the notification remover that justin (nitsuj) posted. Dl and flash it via recovery and you won't have to worry about deferring anymore.
I'm just learning that there is a new OTA. Whatever the case, I have not received it yet but am curious as to how I should handle it. This phone still confuses me a bit when it comes to unlocking etc.
Currently I am S-On, Rooted and running Shrike's PAC-Man rom. I kinda been lazy about staying up to date with everything and just got in my routine of flashing new releases.
Now i'm reading about this update and new hboot versions and wondering what I should be doing now. Should I accept the update in my current status or should I be doing something else to update? What about my hboot version, i'm still at 2.25. Should I be updating that myself or just take the OTA to handle it. My apologies if this is a redundant question.
braveally said:
I'm just learning that there is a new OTA. Whatever the case, I have not received it yet but am curious as to how I should handle it. This phone still confuses me a bit when it comes to unlocking etc.
Currently I am S-On, Rooted and running Shrike's PAC-Man rom. I kinda been lazy about staying up to date with everything and just got in my routine of flashing new releases.
Now i'm reading about this update and new hboot versions and wondering what I should be doing now. Should I accept the update in my current status or should I be doing something else to update? What about my hboot version, i'm still at 2.25. Should I be updating that myself or just take the OTA to handle it. My apologies if this is a redundant question.
Click to expand...
Click to collapse
First, the updated wont be pushed to you because you aren't on a sense rom, and i think the AOSP has the OTAkill.apk but i would need to look for it.
Second, the update is a good thing. not only does it have a new hboot but it has new radios, firmware and other goodies for the phone.
if you were to do the update, i wouldnt wait for VZW to push it. there is a zip that is in the development forum that you may flash to get the benefits of the update.
if you go down this route it will make the phone 100% stock. You would have to do the dev unlock with token and flash a recovery to get back to root status.
if you were to do this you also need to back up internal sd card just in case.
EDIT: Here are the steps you would take if you wanted to update the phone.
http://forum.xda-developers.com/showpost.php?p=40831457&postcount=59
credit goes to brenuga give him all the thanks you can.
synisterwolf said:
First, the updated wont be pushed to you because you aren't on a sense rom, and i think the AOSP has the OTAkill.apk but i would need to look for it.
Second, the update is a good thing. not only does it have a new hboot but it has new radios, firmware and other goodies for the phone.
if you were to do the update, i wouldnt wait for VZW to push it. there is a zip that is in the development forum that you may flash to get the benefits of the update.
if you go down this route it will make the phone 100% stock. You would have to do the dev unlock with token and flash a recovery to get back to root status.
if you were to do this you also need to back up internal sd card just in case.
EDIT: Here are the steps you would take if you wanted to update the phone.
http://forum.xda-developers.com/showpost.php?p=40831457&postcount=59
credit goes to brenuga give him all the thanks you can.
Click to expand...
Click to collapse
Thanks and thank you brenuga. That clears things up for me.
Is there a better S-Off method? In S-Off and don't want to lose root again and have to lock the bootloader
Sent from my ADR6425LVW using xda app-developers app
sk8bert12 said:
Is there a better S-Off method? In S-Off and don't want to lose root again and have to lock the bootloader
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Flash this in HBOOT. Only will work for s-off people
http://forum.xda-developers.com/showpost.php?p=40767819&postcount=33
sk8bert12 said:
Is there a better S-Off method? In S-Off and don't want to lose root again and have to lock the bootloader
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
You can be S-OFF and still get the OTA, you just have to be pure stock, or you can flash the files in the thread which Flyhalf posted below.
On my last Rezound, I flashed the updated hboot and radios while already S-OFF, rooted and running Nils' ROM. On my current ROM, I got the OTA downloaded while still pure stock, then unlocked bootloader, flashed Amon Ra, rooted, then got S-OFF. Obviously, if there are any subsequent OTA's, I'll have to wait for a flashable.
Flyhalf205 said:
Flash this in HBOOT. Only will work for s-off people
http://forum.xda-developers.com/showpost.php?p=40767819&postcount=33
Click to expand...
Click to collapse
Thanks for the link/post. But what does this exactly do to an S-Off Rezound? Will this update/install just the HBOOT/Radios?
I'm on Ineffabilis Deus v1.2 ICS 4.0.3. I believe this might have been from the leaked global ruu.
DigiDave said:
Thanks for the link/post. But what does this exactly do to an S-Off Rezound? Will this update/install just the HBOOT/Radios?
I'm on Ineffabilis Deus v1.2 ICS 4.0.3. I believe this might have been from the leaked global ruu.
Click to expand...
Click to collapse
That was from the Global Leak. But the zip will just update firmware such as hboot and radio and few other stuff
I'm s-off. If I flash the latest RUU (whatever it is), then get the new global OTA update, I will retain my s-off-ness, correct? I'll just have to re-root and flash a recovery?
rsage said:
I'm s-off. If I flash the latest RUU (whatever it is), then get the new global OTA update, I will retain my s-off-ness, correct? I'll just have to re-root and flash a recovery?
Click to expand...
Click to collapse
No zip file of any kind will get you back to s-on. you must use fastboot to write to the secure flag. FYI