I s offed with the ICS leaked firmware and want to downgrade to the gb radios. I have seen lots of posts saying different things and would like someone with experience doing this to tell me what you did and in what order
Sent from my ADR6425LVW using Tapatalk 2
pmania said:
I s offed with the ICS leaked firmware and want to downgrade to the gb radios. I have seen lots of posts saying different things and would like someone with experience doing this to tell me what you did and in what order
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
If your S-off and on Juopunut bear's modified Hboot, you can just download the exe. version of the GB ota found in this thread http://forum.xda-developers.com/showthread.php?t=1338916 . Just be aware that once you run it you will be completely stock again including locked bootloader. If you still want to preserve your locked status I would flash this hboot in this thread..http://forum.xda-developers.com/showthread.php?t=1618140
Now, you will still be locked but able to run fastboot commands without unlocking. Now, you have to flash Amon recovery found here..http://www.mediafire.com/?l9dgzvvsdku7g3c This is the recovery that works for GB firmware. If you upgrade back to leaked ICS then you will have to flash 3.15.
Prior to flashing Amon Ra recovery.. you may watch to do a factory reset in hte stock recovery to prevent any possible data connection issues. Once you did that and now have flashed Amon ra.. you can either flash a rooted rom to get root back or to go to developer menu in Amon ra and install SU there.
Remember if you now flash GB based roms you don't need any patches, but if you flash ICS roms you will need this patch here.. http://forum.xda-developers.com/showthread.php?t=1508118
It will be the old firmware patch you want to download.
After all this you should be set !
???
mjh68 said:
Remember if you now flash GB based roms you don't need any patches, but if you flash ICS roms you will need this patch here.. http://forum.xda-developers.com/showthread.php?t=1508118
Click to expand...
Click to collapse
Why is the 'old firmware patch' necessary when moving from GB to ICS; is something not getting properly overwritten when using a PHxxxxx.zip instead of a full RUU?
jdmba said:
Why is the 'old firmware patch' necessary when moving from GB to ICS; is something not getting properly overwritten when using a PHxxxxx.zip instead of a full RUU?
Click to expand...
Click to collapse
I am talking about if he stays on Gingerbread firmware , but wants to run ICS roms. Then he would need to flash the old firmware patch so his SD card mounts properly.
Yes, I get that ...
Yes, I understand why people need a patch after running the PHxxxx.zip
I am asking why the PHxxxx.zip leaves that a necessary step. What is missing from the PHxxxx.zip that requires this to be done.
I suspect when VZW releases their RUU, such a step will not be necessary (i.e., it will properly update the firmware). So I am trying to get to the bottom of why the PHxxxx.zip does not properly update the firmware.
mjh68 said:
If your S-off and on Juopunut bear's modified Hboot, you can just download the exe. version of the GB ota found in this thread http://forum.xda-developers.com/showthread.php?t=1338916 . Just be aware that once you run it you will be completely stock again including locked bootloader. If you still want to preserve your locked status I would flash this hboot in this thread..http://forum.xda-developers.com/showthread.php?t=1618140
Now, you will still be locked but able to run fastboot commands without unlocking. Now, you have to flash Amon recovery found here..http://www.mediafire.com/?l9dgzvvsdku7g3c This is the recovery that works for GB firmware. If you upgrade back to leaked ICS then you will have to flash 3.15.
Prior to flashing Amon Ra recovery.. you may watch to do a factory reset in hte stock recovery to prevent any possible data connection issues. Once you did that and now have flashed Amon ra.. you can either flash a rooted rom to get root back or to go to developer menu in Amon ra and install SU there.
Click to expand...
Click to collapse
Very useful information mjh. Two points/questions:
1. If the OP doesn't need to use fastboot commands, they can simply flash a PH98IMG.zip of the AmonRA recovery. They can be found in the Amon Ra thread. That way they still get custom recovery without having to change away from the stock HBoot. (I did this earlier today.)
2. Does the factory reset need to be done in AmonRa or bootloader?
---------- Post added at 05:05 PM ---------- Previous post was at 04:57 PM ----------
jdmba said:
Yes, I understand why people need a patch after running the PHxxxx.zip
I am asking why the PHxxxx.zip leaves that a necessary step. What is missing from the PHxxxx.zip that requires this to be done.
I suspect when VZW releases their RUU, such a step will not be necessary (i.e., it will properly update the firmware). So I am trying to get to the bottom of why the PHxxxx.zip does not properly update the firmware.
Click to expand...
Click to collapse
I'm not sure I follow what you're asking about here. mjh doesn't mention running the PHxxxx.zip at all. If you're S-OFF, you don't need to, as the boot image will already be installed properly in recovery.
If you're S-ON, then you have to run the PH98IMG.zip in bootloader after installing a ROM like CleanROM 4.4. That's for installing the boot image, and more or less the same PH98IMG.zip that is included in the upgrades.
The firmware fix is not a PH98IMG.zip and can be flashed in recovery, regardless of S-ON. If I understand correctly, the latest ICS firmware changes around some of the mount points (and probably other things), and thus the ICS ROMs assume those new mount points. Running the firmware patch just updates the system files to point to the right place given the old firmware. (Please correct me if I'm wrong.) As it's not normally needed (ICS ROM assumes ICS firmware), there's no reason it would be included in the PH98IMG.zip that has the boot image. Plus it's probably a different command than what the boot image flashes -- I'm not sure the bootloader can do more complex control flows like that.
destro158 said:
I'm not sure the bootloader can do more complex control flows like that.
Click to expand...
Click to collapse
Which is the basis of my question ... that a RUU will be able to properly handle the issue and the PHxxxx.zip cannot.
Thanks for trying to answer. Perhaps your last sentence is my answer.
jdmba said:
Which is the basis of my question ... that a RUU will be able to properly handle the issue and the PHxxxx.zip cannot.
Thanks for trying to answer. Perhaps your last sentence is my answer.
Click to expand...
Click to collapse
An RUU will put you on the proper firmware for the ROM you are installing. It doesn't have to deal with the issue of you possibly running a different firmware than what the ROM was built for because it will just install the right firmware.
Almost There
destro158 said:
An RUU will put you on the proper firmware for the ROM you are installing. It doesn't have to deal with the issue of you possibly running a different firmware than what the ROM was built for because it will just install the right firmware.
Click to expand...
Click to collapse
Thanks ... we are getting SUPER close to the answer to my question. I guess the final nail would be .... 'why does the PHxxxxx.zip not do that'
jdmba said:
Thanks ... we are getting SUPER close to the answer to my question. I guess the final nail would be .... 'why does the PHxxxxx.zip not do that'
Click to expand...
Click to collapse
The PH98IMG.zip does fix that. You only need the patch if you're running an ICS Rom (anything based on 3.xx firmware) while still on GB firmware (2.xx and below)
Sent from my ADR6425LVW using XDA
scubasteve85 said:
The PH98IMG.zip does fix that. You only need the patch if you're running an ICS Rom (anything based on 3.xx firmware) while still on GB firmware (2.xx and below)
Click to expand...
Click to collapse
Is there a PH which will also push the ICS firmware at the same time?
jdmba said:
Is there a PH which will also push the ICS firmware at the same time?
Click to expand...
Click to collapse
Yes. The RUU (or whatever you want to call it) just leaked is a PH98IMG.zip that will do the full hboot, firmware, radio, and Rom upgrade and is installed in the bootloader.
Sent from my ADR6425LVW using XDA
Related
Hello all, I've been a long time lurker around here, and I first want to thank all the devs for all their hard work in making this such a great device. In anticipation of a fully working ICS build in the near future, is there anything I need to do before flashing an ICS ROM? I'm currently running CM7 with HBOOT 0.57 with S-On. Do I need to get S-off in order to flash ICS, or can I just flash it as I would any new Gingerbread ROM? Also, what other, if any, benefit is there to obtaining S-off?
you are using CM7 but with S-On? i thought before rooting the phone, we need to s-off the first?
lokodoe said:
you are using CM7 but with S-On? i thought before rooting the phone, we need to s-off the first?
Click to expand...
Click to collapse
Rooting does not require to remove security (s-off).
S-off allows you to flash recoveries, hboots, radios via fastboot, which I think is classed as being safer than via recovery.
It also allows you write access to system while android is booted.
lokodoe said:
you are using CM7 but with S-On? i thought before rooting the phone, we need to s-off the first?
Click to expand...
Click to collapse
I originally had the old version of Froyo (or was it Eclair?) that came with the phone. This was before an update that made S-on prevent the installation of CWM. Back then, I was able to use the Unrevoked method to root and install clockwork recovery. I can't remember all the details, but needless to say, S-on with HBOOT 0.57 back then did not prevent root, CWM, or the flashing of ROMs, and possibly kernels. I've flashed new CM7 ROMs up to one that was stable and after the gps was fixed, so everything works fine. I believe I'm running CM nightly 184.
This is why I'm wondering if the installation process if different for CM9 than for CM7. I don't know if S-On will interfere with the new version of android.
Edit: Here is the thread for unrevoked that I followed way back when. http://forum.xda-developers.com/showthread.php?t=788737
DanGeorges said:
Rooting does not require to remove security (s-off).
S-off allows you to flash recoveries, hboots, radios via fastboot, which I think is classed as being safer than via recovery.
It also allows you write access to system while android is booted.
Click to expand...
Click to collapse
Sorry for my noobishness, but does this mean I can still flash an ICS ROM through my usual way in recovery? I remember reading somewhere that the flashing process for ICS is slightly different than Gingerbread ROMs. Also, I don't really care about being able to write to the system directory unless that has some advantage that I am unaware of.
Goodbye_Alltel said:
Sorry for my noobishness, but does this mean I can still flash an ICS ROM through my usual way in recovery? I remember reading somewhere that the flashing process for ICS is slightly different than Gingerbread ROMs. Also, I don't really care about being able to write to the system directory unless that has some advantage that I am unaware of.
Click to expand...
Click to collapse
Yes - you should be able to flash ICS without s-off.
DanGeorges said:
Yes - you should be able to flash ICS without s-off.
Click to expand...
Click to collapse
Alright. Thanks for clearing that up. I'll of course be sure to make a full backup and wipe everything before flashing ICS (I'm holding out until gps and camera are fixed because I use both quite freqently).
I'm brand new to this phone and the rezound section on xda. I bought two of these phones yesterday and have both of them S=OFF at the moment. (Last night's fun)
In hboot they say "locked" even though S=OFF on both devices. I'd like to install an ICS ROM, but I'm not really sure what I need to install first before installing the ROM so it doesn't get all messed up.
I remember installing/flashing something on my Sensation to get ICS running on that device, but I'm just a little confused with the steps in the Development section because I'm new here.
Help?
you need to flash a modified Hboot for whichever firmware u are on
http://forum.xda-developers.com/showthread.php?t=1641670
yojoe600 said:
you need to flash a modified Hboot for whichever firmware u are on
Click to expand...
Click to collapse
Software Number: 2.01.605.11
Does it matter which one?
graymonkey44 said:
http://forum.xda-developers.com/showthread.php?t=1641670
Click to expand...
Click to collapse
I spent last night reading that.
yes if you are on GB you need the eng Hboot if you are on ICS firmware you need the jhboot from the s-off method
yojoe600 said:
yes if you are on GB you need the eng Hboot if you are on ICS firmware you need the jhboot from the s-off method
Click to expand...
Click to collapse
HBOOT 2.11.0000
I flashed the hboot after jhboot and I'm not sure if this is the right one for ICS?
android Version: 2.3.4
I would suggest running the latest RUU and then installing whichever ICS ROM you want.
woah wait what
what are you guys saying?
I was stock,GB,rooted, SOFF.
my hboot said 's-off' and '***LOCKED***'.
you don't need to do anything special, you are s-off!
just get the 600mb ph98img.zip from the latest leak and drop it on your SD card.
it'll have to flash twice (first reboot after boot/recovery is flashed, then it does the rest the second time through)
that's how i went to the leak, still locked and s-off. and it runs great!
thatsricci said:
woah wait what
what are you guys saying?
I was stock,GB,rooted, SOFF.
my hboot said 's-off' and '***LOCKED***'.
you don't need to do anything special, you are s-off!
just get the 600mb ph98img.zip from the latest leak and drop it on your SD card.
it'll have to flash twice (first reboot after boot/recovery is flashed, then it does the rest the second time through)
that's how i went to the leak, still locked and s-off. and it runs great!
Click to expand...
Click to collapse
Which one is the latest leak? I'm really not trying to be a moron.
thatsricci said:
woah wait what
what are you guys saying?
I was stock,GB,rooted, SOFF.
my hboot said 's-off' and '***LOCKED***'.
you don't need to do anything special, you are s-off!
just get the 600mb ph98img.zip from the latest leak and drop it on your SD card.
it'll have to flash twice (first reboot after boot/recovery is flashed, then it does the rest the second time through)
that's how i went to the leak, still locked and s-off. and it runs great!
Click to expand...
Click to collapse
So its just that simple for those of us SOFF and GB?
1) Put the PHxxxx.zip image on the SD
2) Boot it into HBoot twice (not flashing via recovery)
3) Flash over our favorite ICS Rom
No patches, no nothing? Is this right?
There are like 10 files in this link.
http://forum.xda-developers.com/showthread.php?t=1365654
I have S=OFF, I'm running GB, with the stock ROM and all the specs I told you. I'm not exactly clear on which one I need to install before installing a ICS ROM.
Do I install an ENG hboot... Do I install a ICS RUU file or a GB one? I'm assuming the bigger the number the newer RUU?
I'm not sure when you say about rom... i'm flashing the 600mb leak file from yesterday (5/7/2012) : http://forum.xda-developers.com/showthread.php?t=1641249
it has the radios, boot, recovery, kernel, rom, everything. I just did it all, like an OTA upgrade.
thatsricci said:
I'm not sure when you say about rom... i'm flashing the 600mb leak file from yesterday (5/7/2012) : http://forum.xda-developers.com/showthread.php?t=1641249
it has the radios, boot, recovery, kernel, rom, everything. I just did it all, like an OTA upgrade.
Click to expand...
Click to collapse
I want to Install the RUU file then a modded ROM (Clean ROM ICS)
If I install the ROM before flashing the RUU won't it bootloop?
jdmba said:
So its just that simple for those of us SOFF and GB?
1) Put the PHxxxx.zip image on the SD
2) Boot it into HBoot twice (not flashing via recovery)
3) Flash over our favorite ICS Rom
No patches, no nothing? Is this right?
Click to expand...
Click to collapse
Is this all that all I have to do?
2Noob4U said:
I want to Install the RUU file then a modded ROM (Clean ROM ICS)
If I install the ROM before flashing the RUU won't it bootloop?
Click to expand...
Click to collapse
I'm not sure... I didn't have any trouble going straight to the leaked RUU from yesterday. I have not flashed any custom roms.
thatsricci said:
I'm not sure... I didn't have any trouble going straight to the leaked RUU from yesterday. I have not flashed any custom roms.
Click to expand...
Click to collapse
Is there something wrong with the Custom ROMs? (Please Developers don't stone me)
I just came from a device with tons of custom ROMs that were way better than anything stock and would install a kernel and everything through recovery when you were installing the ROM...
I'm just not used to the process yet with this device.
I don't think there's anything wrong with them.
I just haven't taken the plunge yet, still researching.... regardless, Once you're fully up to date on the latest RUU, going to a custom rom based on it will be a piece of cake. But i'm not sure the developers have updated their roms to all the latest leaks, in which case, check with the rom you're trying to upgrade to - I'm not certain they all include new kernels/radios...etc. like the leaked ICS does.
thatsricci said:
I don't think there's anything wrong with them.
I just haven't taken the plunge yet, still researching.... regardless, Once you're fully up to date on the latest RUU, going to a custom rom based on it will be a piece of cake. But i'm not sure the developers have updated their roms to all the latest leaks, in which case, check with the rom you're trying to upgrade to - I'm not certain they all include new kernels/radios...etc. like the leaked ICS does.
Click to expand...
Click to collapse
Okay. Can I wifi tether with the new RUU link you gave me?
2Noob4U said:
Okay. Can I wifi tether with the new RUU link you gave me?
Click to expand...
Click to collapse
Great question, let me test that right now.
Edit: seems to not work straight up with the one from the market. i'll check a different .apk that I have here, i know the custom roms use their own .apk's usually.
as i recall from doing this on GB, you gotta configure it right, and then it'll work. But you DO need root, so after you RUU, install AmonRA 3.15, and run the su/superuser install from the recovery menu.
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 (at least trying to) patiently wait for Deck to post full install instructions for CM10 but the CM10 op is still bare as bones. Has anyone else posted an install guide or instructions yet?
I'm currently rooted with RegawMod and running MeanRom 2.1 and it's really terribly laggy and frustrating, I can't wait any longer for CM10. Do I need S-off to install CM10 or do I just wipe, flash, and go?
Thanks for any help or links!
If you are on hboot 1.15 or higher you have to fast boot flash the kernel.
Other than that its just like a normal aosp install. Wipe flash rom flash gapps.
Its been my daily for 3 weeks.
Sent from my EVO using Tapatalk 2
You don't need s-off. You will however have to flash the boot IMG separately by using fastboot or the app flash image GUI and a full wipe is definitely required. There is a helpful thread in Q&A called "don't panic" that will answer all your questions
Good luck
Sent from my EVO using xda app-developers app
corcgaigh said:
You don't need s-off. You will however have to flash the boot IMG separately by using fastboot or the app flash image GUI and a full wipe is definitely required. There is a helpful thread in Q&A called "don't panic" that will answer all your questions
Good luck
Click to expand...
Click to collapse
Dont use flash image gui unless you know how to do it manually through fastboot. You are just asking for issues
Instructions:
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-a.html
Rxpert said:
If you are on hboot 1.15 or higher you have to fast boot flash the kernel.
Other than that its just like a normal aosp install. Wipe flash rom flash gapps.
Click to expand...
Click to collapse
I'm on hboot 1.12, so does that mean I can just flash normally?
edit - From what I can tell from reading, hboot 1.12 doesn't have the same restrictions that 1.15+ do, so I think I'm OK but I would like verification.
Thanks for the help everyone.
Yes hboot 1.12 allows for access to the boot partition
Also luuuuucckkyyyyyy...
EdhyMonker said:
I'm on hboot 1.12, so does that mean I can just flash normally?
edit - From what I can tell from reading, hboot 1.12 doesn't have the same restrictions that 1.15+ do, so I think I'm OK but I would like verification.
Thanks for the help everyone.
Click to expand...
Click to collapse
If you are on Hboot 1.12 I'd strongly suggest looking into getting S-OFF. Theres really no reason not to.
Up to you though, its not required
Bit off topic, anyone check to see if you can push a new splash, right now I'm too lazy to start my PC just to fastboot one measly splash
Rxpert said:
If you are on Hboot 1.12 I'd strongly suggest looking into getting S-OFF. Theres really no reason not to.
Up to you though, its not required
Click to expand...
Click to collapse
The S-OFF guide was way over my head so I just let it be. If there's not a real good reason for doing it, and I can still run CM10, then I'd rather not.
It allows you to directly flash new firmware like radios to fix any problems a device might be having. If you have Son and want the latest firmware you have to revert back to stock and accept ota, then unlock reflash recovery and reflash custom ROM or rooted stock, you could also just flash root installer if you want to just root stock
om4 said:
It allows you to directly flash new firmware like radios to fix any problems a device might be having. If you have Son and want the latest firmware you have to revert back to stock and accept ota, then unlock reflash recovery and reflash custom ROM or rooted stock, you could also just flash root installer if you want to just root stock
Click to expand...
Click to collapse
No, S-ON people with 1.12 H-boot can flash radios and firmware from recovery. They can do whatever they please in recovery just like S-OFF. S-OFF users can flash things from bootloader and even change the appearance of their h-boot to read S-ON and **locked** even though they are S-OFF
To the OP, this is the best rooting guide I've seen. It really explains everything step by step. http://androidforums.com/evo-4g-lte...panda-s-htc-dev-ltevo-root-dummies-guide.html Its recommended to have Linux at least bootable, because in the small chance the phone gets bricked... the unbricker program requires linux.
I ran it in windows before the unbricker was available, no issues here
You basically just hook the phone up to it and run the program like you do for most other root programs. All 1-click
Ah yeah forgot to mention that, most everyone is on 1.15 or 1.19 sorry
om4 said:
Ah yeah forgot to mention that, most everyone is on 1.15 or 1.19 sorry
Click to expand...
Click to collapse
Alright, I got S-Off using Lazy Panda and it went better than expected!
Do I need to flash updated firmware / radios separately from CM10, or does CM10 include latest firmware?
Sorry to ask dumb questions, but I do hope this thread will also be a good resource for others like me.
You don't have to flash any firmware updates. There are a few users with issues although they may be related to the ROM update and not necessarily the firmware included. I haven't really checked since I'm s on. If you want to update the radios there's an update zip here somewhere, be sure to read through everything carefully. Radios are more risky then every day flashing
Alright everyone now I need some help!
I flashed CM10 after s-off, was on stocked 1.13 rooted rom.
Now when CM10 boots up I am faced with a phone activation screen. It says something like "you will not be able to place calls or access the mobile network until the device is activated". I am unable to make calls or receive calls or access the internet. I have tried reflashing cm10 and the problem persists.
In the mean time, I will try flashing a nand backup and see where that gets me. I appreciate any and all help, and I have found no posts in the CM10 thread with a similar issue.
Update: I wiped and restored a back-up, MeanRom 2.1. Upon boot, hands-free activation ran and activated the phone and downloaded a PRL update. Everything is working fine now. Not sure if I should try CM10 again or what? Any advice?
EdhyMonker said:
Alright everyone now I need some help!
I flashed CM10 after s-off, was on stocked 1.13 rooted rom.
Now when CM10 boots up I am faced with a phone activation screen. It says something like "you will not be able to place calls or access the mobile network until the device is activated". I am unable to make calls or receive calls or access the internet. I have tried reflashing cm10 and the problem persists.
In the mean time, I will try flashing a nand backup and see where that gets me. I appreciate any and all help, and I have found no posts in the CM10 thread with a similar issue.
Update: I wiped and restored a back-up, MeanRom 2.1. Upon boot, hands-free activation ran and activated the phone and downloaded a PRL update. Everything is working fine now. Not sure if I should try CM10 again or what? Any advice?
Click to expand...
Click to collapse
ive only ever seen this issue with cyanogenmod and the old htc vogues, still great phones for what they were
EdhyMonker said:
Alright, I got S-Off using Lazy Panda and it went better than expected!
Do I need to flash updated firmware / radios separately from CM10, or does CM10 include latest firmware?
Sorry to ask dumb questions, but I do hope this thread will also be a good resource for others like me.
Click to expand...
Click to collapse
Yes, you should be flashing the upgraded firmware. You'll see the full firmware as the very first downloadable link. Flash that
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Rename the file to "PJ75IMG.zip", place on root of SD card, and boot into HBOOT to flash. Check the md5 to make sure its right. With radios you want to make sure its the correct file.
Welcome to S-OFF my friend
Rxpert said:
Yes, you should be flashing the upgraded firmware. You'll see the full firmware as the very first downloadable link. Flash that
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Rename the file to "PJ75IMG.zip", place on root of SD card, and boot into HBOOT to flash. Check the md5 to make sure its right. With radios you want to make sure its the correct file.
Welcome to S-OFF my friend
Click to expand...
Click to collapse
Thanks, but I tried this and it says "no image or wrong image" when trying to flash the PJ75IMG.zip file.
Did you type in PJ75IMG.zip or PJ75IMG and kept it a zip file...you should do the 2nd.
joebarkho said:
Did you type in PJ75IMG.zip or PJ75IMG and kept it a zip file...you should do the 2nd.
Click to expand...
Click to collapse
I thought that might've been the issue so I tried it both ways, didn't work either way. I'll take another shot at it tomorrow.
I'd like to update to the new Stock ROM with Goodies- Questions....
1. Hotspot work on this ROM?
2. What firmware/Radio do I need for this or does any of that get updated automatically?
3. Is there a walk through instruction/video for this update...from such an old ROM?
I have:
Hboot 1.12.0000
S-on
Radio 1.02.12.0427
TWRP 2.1.8
Well to start you need to decide if you want to s- off or not. If you don't i believe you can update firmware with the 1.12 hboot.
I'd update the firmware in consecutive order from where you are now. You want the firmware zips without the hboot img
Then you can flash the new rom you want.
I would follow the directions for s- off personally. It makes things alot easier
Sent from my EVO using xda premium
NaterTots said:
Well to start you need to decide if you want to s- off or not. If you don't i believe you can update firmware with the 1.12 hboot.
I'd update the firmware in consecutive order from where you are now. You want the firmware zips without the hboot img
Then you can flash the new rom you want.
I would follow the directions for s- off personally. It makes things alot easier
Sent from my EVO using xda premium
Click to expand...
Click to collapse
If I turn the device into s-off, then I can use TWRP to update from zip files right?
I read that I don't want to jump firmware to the latest or I could brick the device. So I thought the process might look like this.
PLEASE CORRECT ME IF I'M WRONG:
1. LazyPanda ( http://forum.xda-developers.com/showthread.php?t=1737123 )
to "s-off" the device
2. Run zip for 2.13.651.1 OTA (which one though?)
....Reboot THEN
run zip for 3.16.651.3 OTA
So I don't brick it
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
3. Install Stock ROM with Goodies...
Am I missing something?
What about the radio (comes with the firmware?)? What's the deal with the boot.img or not (I don't see the firmware WITHOUT boot.img included)?
Lazy panda is not technically supported anymore, so not sure how much luck you'll have there, but I would say run the 3.15 RUU, then s-off with dirty racun .
Stock with goodies is using the 3.16 base, so once you're s-off you can update to that firmware/radio version via the bootloader...assuming you're coming from 3.15. Just make sure to flash the 3.16 zip without the tp img, or your touch screen won't work with any other base.
http://forum.xda-developers.com/showthread.php?t=1704612
Sent from my EVO LTE
premo15 said:
Lazy panda is not technically supported anymore, so not sure how much luck you'll have there, but I would say run the 3.15 RUU, then s-off with dirty racun .
Stock with goodies is using the 3.16 base, so once you're s-off you can update to that firmware/radio version via the bootloader...assuming you're coming from 3.15. Just make sure to flash the 3.16 zip without the tp img, or your touch screen won't work with any other base.
http://forum.xda-developers.com/showthread.php?t=1704612
Sent from my EVO LTE
Click to expand...
Click to collapse
OK. let me revise then
1. S-off through RUU 3.15, then use Dirty Racun
2. Then update through TWRP (do I need a specific version or do I HAVE to use the Hboot?) to 3.15, then reboot and change to 3.16 (without tp.img in it)
3. install new ROM stock with goodies 3.16
Do I have it now?
(sigh...my Sprint Epic 4G first gen, and my wife's Galaxy Note 2 are SOOO much less complicated than HTC stuff)
ZenInsight said:
OK. let me revise then
1. S-off through RUU 3.15, then use Dirty Racun
2. Then update through TWRP (do I need a specific version or do I HAVE to use the Hboot?) to 3.15, then reboot and change to 3.16 (without tp.img in it)
3. install new ROM stock with goodies 3.16
Do I have it now?
(sigh...my Sprint Epic 4G first gen, and my wife's Galaxy Note 2 are SOOO much less complicated than HTC stuff)
Click to expand...
Click to collapse
That's what I was saying in another thread. With samsung phones you just flash and reboot. With these HTC phones you have to update this downgrade that just to flash a rom. I came from a one X and you had to flash the boot.img every time you wanted to flash a rom/kernel/modem.
Sent from my SAMSUNG-SGH-I717
No. Dont s-off then run dirty racun. S-off is what dirty racun does. He's saying Use RUU to get to 3.15, THEN use dirty racun (as per their instructions).
Then STAY at 3.15. Uncles you wanna use a 3.16 sense ROM (which is no different than a 3.15 ROM). If you S-off and update to 3.16 firmware AND flash the 3.16 touch panel image (tp.IMG), you will not be able to use any ROMs that aren't sense 3.16. I would suggest leaving your firmware where it is, and try the ROM you want. Generally, you DO NOT need current firmware to run a current ROM. The two are mutually exclusive (firmware and ROM). I always rock old radios. Newer isn't always better.
From my Evo LTE, yup.
1. S-OFF with DirtyRacun (doesn't really matter which RUU you choose)
2. Install custom recovery through fastboot (latest TWRP should be fine, depending on the ROM you choose - you might need 2.4.0.0 or older if flashing a ROM with an outdated update binary)
3. Flash ROM of your choice.
4. Update to latest firmware using most recent zip from firmware thread (this is done through the bootloader, not recovery)
5. Profit.
I feel pretty stupid with how confusing this is.
So
1. Use dirty Racun to go to s-off
2. I already have TWRP 2.1.8 for installing zip updates (Can I leave that version or do I need to change it?),,,
3. Install 3,15 firmware (or install 3.16 but without the tp img or my touchscreen in recovery will be busted.
Also, once I go to 3.16 I can only use 3.16 ROMS in the future.
4. Install any ROM which automatically changes me to the latest radio (is that true?).
I want this one:
http://forum.xda-developers.com/showthread.php?t=1701117
but does that mean I HAVE to have 3.16 firmware to use a 3.16 ROM? Or can I just leave it at 3.15?
ZenInsight said:
I feel pretty stupid with how confusing this is.
So
1. Use dirty Racun to go to s-off
2. I already have TWRP 2.1.8 for installing zip updates (Can I leave that version or do I need to change it?),,,
3. Install 3,15 firmware (or install 3.16 but without the tp img or my touchscreen in recovery will be busted.
Also, once I go to 3.16 I can only use 3.16 ROMS in the future.
4. Install any ROM which automatically changes me to the latest radio (is that true?).
I want this one:
http://forum.xda-developers.com/showthread.php?t=1701117
but does that mean I HAVE to have 3.16 firmware to use a 3.16 ROM? Or can I just leave it at 3.15?
Click to expand...
Click to collapse
2. The S-OFF process involved flashing an RUU, which will replace TWRP with the stock recovery. So like I said, you will need to flash TWRP. Since I don't know if flex has updated the update binary in that ROM, I would flash TWRP 2.4.0.0.
3. Just flash the 3.16 firmware. I've taken out anything that would be of concern, so you can flash whatever ROMs you want.
4. Radio is part of the firmware.
Captain_Throwback said:
2. The S-OFF process involved flashing an RUU, which will replace TWRP with the stock recovery. So like I said, you will need to flash TWRP. Since I don't know if flex has updated the update binary in that ROM, I would flash TWRP 2.4.0.0.
3. Just flash the 3.16 firmware. I've taken out anything that would be of concern, so you can flash whatever ROMs you want.
4. Radio is part of the firmware.
Click to expand...
Click to collapse
Ok. I get it. I lose TWRP once I "s-off", so I have to put it back on.
Just flash 3.16...it doesn't matter anymore about the touchscreen, that's been fixed.
Radio is included in the 3.16 firmware, not the ROM.
Flash the Stock with goodies...and I'll be fine.
Phew.... I hope this is right.
Do not flash 3.16 firmware if you haven't already flashed 3.15 first. Will brick.
From my Evo LTE, yup.
scottspa74 said:
Do not flash 3.16 firmware if you haven't already flashed 3.15 first. Will brick.
From my Evo LTE, yup.
Click to expand...
Click to collapse
No, it won't. Otherwise I would've said so. You obviously haven't been reading the firmware thread .
scottspa74 said:
Do not flash 3.16 firmware if you haven't already flashed 3.15 first. Will brick.
From my Evo LTE, yup.
Click to expand...
Click to collapse
Funny you say that since 3.15 firmware was causing soft bricks with older hboots. The only problem with the latest update is that aosp roms are stuck with out touch screen support for now.
Captain_Throwback said:
No, it won't. Otherwise I would've said so. You obviously haven't been reading the firmware thread .
Click to expand...
Click to collapse
Alright. Guess I missed something. Last time I was in there , if you didn't do 3.15 prior to 3.16 you were hosed.
But I did see the firmware haus dropped that it was said would be OK regardless of 3.15 or not. Just hadn't seen anyone try it.
Definitely listen to Cap'n. He's the man when it comes to firmwares and radios.
From my Evo LTE, yup.
Okay, I wish I had read this before I did what I just did. My device seems to be bricked
Was running 1.22.651.3 and MeanROM-ICS-v65 and went to update things to JB. Updated using PJ75IMG_3.16.651.3_firmware in HBOOT and now the screen won't turn on and none of the LEDs light up when plugged in. The device manager shows QHSUSB_DLOAD when it's plugged into the PC.
Any way to unbrick this?
(insert obligatory "I feel like an idiot for not doing more reading on here ahead of time" statement)
Trioculus said:
Okay, I wish I had read this before I did what I just did. My device seems to be bricked
Was running 1.22.651.3 and MeanROM-ICS-v65 and went to update things to JB. Updated using PJ75IMG_3.16.651.3_firmware in HBOOT and now the screen won't turn on and none of the LEDs light up when plugged in. The device manager shows QHSUSB_DLOAD when it's plugged into the PC.
Any way to unbrick this?
(insert obligatory "I feel like an idiot for not doing more reading on here ahead of time" statement)
Click to expand...
Click to collapse
Did you not download the most recent firmware from my thread? Because there's no way it should've bricked you. I personally updated from 1.22 firmware up to 3.16 with no issues, and someone else updated from 1.13 firmware up to 3.16. What exact file did you use?
EDIT: I just looked, and I don't even have a file available with that name in my thread (anymore). The only one I have is this, which is the extended firmware which eliminates the bricking issue. Sounds like you had an old download.
Captain_Throwback said:
What exact file did you use?
Click to expand...
Click to collapse
I used the one linked to from the wiki page: http://d-h.st/9L9 PJ75IMG_3.16.651.3_firmware.zip
Any way to fix this? Thanks for your help
Trioculus said:
I used the one linked to from the wiki page: http://d-h.st/9L9 PJ75IMG_3.16.651.3_firmware.zip
Any way to fix this? Thanks for your help
Click to expand...
Click to collapse
Ouch. I'll have to update the Wiki. I'll be sure to mention it to Haus.
And no, your device is bricked. Time to get a replacement.
EDIT: Wiki updated with proper link.
Captain_Throwback said:
Ouch. I'll have to update the Wiki. I'll be sure to mention it to Haus.
And no, your device is bricked. Time to get a replacement.
EDIT: Wiki updated with proper link.
Click to expand...
Click to collapse
ouch..That sucks, man.