I was going to install an ICS Sense ROM on my Rezound, but i just got a message that the OTA is downloading.
I'm rooted. I'm going to do S-Off soon as I can.
Should I get S-Off before installing the OTA?
Will the OTA break root?
Will the OTA break S-Off?
Are there advantages to using an ICS Sense ROM instead of the OTA? Vice versa?
Thanks!
I would s-off before you accept ota. It will not effect s-off. Installing an ics Rom wild give you better performance as well as better battery life
Sent from my ADR6425LVW using Tapatalk 2
I was in your exact position so I can help out here.
Note that before you accept the OTA you will need to flash the stock GB recovery, as that's how the OTA installs. Without it the OTA will fail. Also make sure you're 'locked' if you don't end up S-OFFing before the OTA. The S-OFF procedure automatically "locks" your bootloader even though you of course have full access.
I S-OFF'd before OTA just because the S-OFF method has been known to work with GB firmware. Others have reported the .5 ControlBear version on the unlimited.io website also works with the .22 OTA release so that's your call. IMO yes do it before, but it will likely work either way.
-Root will definitely break. Easy to fix: you just google Superuser and flash the latest ARM version.
-The OTA will not break S-OFF. HOWEVER, it will completely overwrite your "modded" hboot with its own secured version. To fix this, grab the ICS hboot from the unlimited.io website and flash it. This is necessary if you want to flash a custom recovery again.
-OTA advantages: support from VZW and probably *slightly* less bugs than a custom ROM. However you of course have to deal with the bloat. It's your call.
Ok, first step...
Where do I get the stock GB recovery?
And i guess i have to "flash" using my computer, not from within Amon?
So, all of the "flashing" you're talking about had to take place using my computer, not from within Amon?
Sorry I'm such a noob.
Anyone? I can't find the stock GB recovery for the Rezound... Anyone know where I can get it?
And do I flash it the same way I flashed AR recovery?
bloodymurderlive said:
Anyone? I can't find the stock GB recovery for the Rezound... Anyone know where I can get it?
And do I flash it the same way I flashed AR recovery?
Click to expand...
Click to collapse
http://www.mediafire.com/?wb21d2gdurui2c6
This is from a write up Scotty did a while back. It's worked for me in the past.
Rename to PH98IMG.zip and place on root of SD card and flash in hboot.
Or extract the recovery.img from that zip and flash in fastboot with the command fastboot flash recovery recovery.img
Thanks!
And now to get root back once I install the ICS OTA...
Do I simply flash the latest Superuser the same way that I flashed the recovery? ie: Do I rename it PH98IMG.zip and flash it in hboot?
You guys are awesome...
bloodymurderlive said:
Thanks!
And now to get root back once I install the ICS OTA...
Do I simply flash the latest Superuser the same way that I flashed the recovery? ie: Do I rename it PH98IMG.zip and flash it in hboot?
You guys are awesome...
Click to expand...
Click to collapse
The superuser zip you would flash in recovery not hboot. After you do the ota update you might have to re flash your recovery first though
Sent from my ADR6425LVW using xda app-developers app
Gottcha... So now I'm confused because the link for superSU in Scotty's n00b-friendly guide takes me here: http://forum.xda-developers.com/showthread.php?t=1538053
And the only link for superSU is to the Android market... How do I get the zip for superSU so that I can flash it in recovery?
bloodymurderlive said:
How do I get the zip for superSU so that I can flash it in recovery?
Click to expand...
Click to collapse
It's right there as CWM SuperSU v0.94
Thanks... It's confusing because it says CWM in the name, but I suppose that really just means you can install it with a custom recovery, not necessarily CWM.
CWM really screwed up charging on my phone before, so I was leary of it.
Got it rooted and ready to go now. Thanks!
Related
So to update firmware first fastboot oem lock and then flash the newest RUU then unlock again. Is this correct?
Exactly
Sent from my PG86100 using XDA App
squiggs95 said:
So to update firmware first fastboot oem lock and then flash the newest RUU then unlock again. Is this correct?
Click to expand...
Click to collapse
Or you can flash a stock recovery without relocking/flashing RUU and take the update if you are on stock ROM.
Why does everyone think you have to rearm your bootloader for updates?
Remember we have an unlocked bootloader which is signed by HTC you don't need to relock for anything, the signatures contained in it are valid
The only thing you have to make sure to receive the ota is to be fully stock, doesn't matter if rooted or not, and that you have stock recovery and all the bloatware that came with the phone, otherwise the update will fail.
Note : if your rooted you will loose root after the update.
Sent from my PG86100 using Tapatalk
i am confused...sorry
i also am on 1.5 s-off, what are the proper steps to follow
thanks ive always gotten so much help here
tammyjustin said:
i am confused...sorry
i also am on 1.5 s-off, what are the proper steps to follow
thanks ive always gotten so much help here
Click to expand...
Click to collapse
IF you are 1.5 S-OFF then its business as usual. Flash the ROM from custom recovery like traditionally you would and you should be good.
Most of us have Hboot 1.5 S-ON, this method involves flashing the Kernel first (however you want to flash: fastboot or Flash GUI) and then flashing the ROM via custom recovery.
im sorry i mistyped, im s-on, and i do know how to flash roms i was wondering the proper steps to update to the newest firmware. i have read many instructions about it but im a moron and got confused along the way
again thanks
Where can i download a stock recovery image?
squiggs95 said:
Where can i download a stock recovery image?
Click to expand...
Click to collapse
Extract the recovery.img file from a RUU/ROM.zip file.
And then fastboot flash recovery recovery.img or rename it to PG86IMG.ZIP and run it like an ruu?
If that's the case, can you just run the last Sprint ruu then do update? Or will the ruu not overwrite recovery and kernel? Trying to figure this out to without messing up the phone. I am also running with 1.5 s-on.
Sent from my Touchpad using Tapatalk
I flashed the leaked ICS and am presently on a ROM based on RUU_3.11.605.22. I have Amon Ra recovery.
I would like to get to a condition where I am running Ginger Bread and the phone is as close as possible to a stock 2.01.605.11, is not rooted, (or does not appear to be rooted) and has the stock recovery. I also want to end up "RELOCKED" and not showing the word "TAMPERED".
I understand that I cannot flash the older 2.01.605.11 RUU. But would you be so kind as to explain the senescence of events that I would have to go through to reach the "quasi-stock" state?
I have read several threads, but they all seem to describe how to get "back to stock" from an ICS ROM that pre-dates the latest RUU leak.
first install stock rooted gb rom and kernel then install stock recovery then relock.
to get and install the stock rooted gb rom and kernel, go here
http://www.scottsroms.com/downloads.php?do=file&id=100
kernel is included in the rom so no need to worry, just do what the installation says..
to get stock recovery go here
http://db.tt/tw5m33ZG
then fastboot oem lock through adb
qudwis said:
first install stock rooted gb rom and kernel then install stock recovery then relock.
to get and install the stock rooted gb rom and kernel, go here
http://www.scottsroms.com/downloads.php?do=file&id=100
Click to expand...
Click to collapse
The CleanRom you linked, says that it has all the Verizon Bloat removed. I was looking for something WITH all the bloat and as close to stock as possible. Thanks for the link on the stock recovery tho.
Try here - http://www.scottsroms.com/downloads.php?do=cat&id=11
If you did the RUU leak install and you update your hboot, etc, you'll need the SD patch that Scott put out also.
Just wait for S=Off to come out soon it will allow you to go back to stock with out the lock to be tampered with Plus is was safer then doing this even thow HTC Rezound can't be brick is still better to wait for s=off
Thank you! Do I need to flash only the WWE-vigor or that *and* the boot image? Also, when do I flash the GB fix? Right after the first flash? or is a reboot required in between?
Sent from my ADR6425LVW using XDA
cflo360 said:
Just wait for S=Off to come out soon it will allow you to go back to stock with out the lock to be tampered with Plus is was safer then doing this even thow HTC Rezound can't be brick is still better to wait for s=off
Click to expand...
Click to collapse
Why can't it be bricked, I'm pretty sure I could brick one right now pulling the battery while flashing the new radio
Sent from my ADR6425LVW using XDA
nukeboyt said:
Thank you! Do I need to flash only the WWE-vigor or that *and* the boot image? Also, when do I flash the GB fix? Right after the first flash? or is a reboot required in between?
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
boot image is the kernel so yes, you need to flash the rom and the boot image.
once installed you may install the fix right away, but i would suggest one boot.
download this one. it's rooted, but has all the bloats.
http://www.scottsroms.com/downloads.php?do=file&id=76
also download this as well this the boot image in the rom is wrong and this is the right one.
http://www.scottsroms.com/downloads.php?do=file&id=77
unzip the rom then change the boot image with the bottom one then re-zip then flash..
2 Questions:
1) by doing this, is it going back to the original radio?
2) will this be going back to the state even before the GB OTA update?
Thanks in advance.
cm0803o2 said:
2 Questions:
1) by doing this, is it going back to the original radio?
2) will this be going back to the state even before the GB OTA update?
Thanks in advance.
Click to expand...
Click to collapse
1. still leaked ota (3.11.605.22) radio
2. latest ota (2.01.605.11) state
OK. So far, so good. I'm back on the GB ROM (VIGOR - WWE 2.01.605.11 - THANKS SCOTT!) I plan on re-locking the phone and re-installing a stock recovery. Which order should I do two things in? Also, how do I delete the superuser app? It does not appear to be delete-able from the applications menu. Thank you.
When you are on rooted Rom you will have superuser are you trying to make a claim or something ?
Sent from my ADR6425LVW using XDA
You can use es file explore with root and go into your system files to delete it but I don't see why you would want to.
Sent from my ADR6425LVW using XDA
nukeboyt said:
OK. So far, so good. I'm back on the GB ROM (VIGOR - WWE 2.01.605.11 - THANKS SCOTT!) I plan on re-locking the phone and re-installing a stock recovery. Which order should I do two things in? Also, how do I delete the superuser app? It does not appear to be delete-able from the applications menu. Thank you.
Click to expand...
Click to collapse
I've followed all of everyone's steps above which are great... but now after relocking my bootloader, I can no longer boot back into a rom. It just constantly reboots back into the HBoot screen.
Can anyone help please??
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
The main question is the title - Should you S-off before or after the OTA?
I have seen people around the forums (via a few searches) say that it is likely a good idea to perform S-off before OTA because we didn't know for sure if the OTA would close the S-off exploit. Now that the OTA is a known quantity, is that still the best route?
My device is:
Stock rom and firmware (2.01.605.11)
Unlocked
AmonRA 3.15 recovery
Rooted
I'm a little nervous about doing S-off, but I figure it will be really handy to have it once its done, and I understand it really is no big deal. My end goal is to run the Venom rom and then move to AOKP/CM9 once they have most of the bugs worked out. Would my best course of action be to S-Off, run the firmware updater, reinstall recovery (probably TWRP, seems like that is the most popular one at the moment), then flash my rom of choice? Will I need to re-root if I switch to a different recovery?
UPDATE:
S-off is done and was no big deal, I got it on my third try. I selected to not install the jb_hboot during the process, since I'm doing RUU next.
The 3.14.605.12 RUU (from android police) was as simple as could be, I renamed the file to PH98IMG.zip and dumped it into my sd card, once I rebooted into the bootloader it was automatic from there
I got stuck on the "flash juopunut Bear hboot" part, I am using Hasoon2000's HTC Rezound ALL-In-One Kit and S-Off Toolkit. I thought I could just flash the hboot from this and be done... I learned that unless you have the jb_hboot (the latest vigor hboot from unlimited.io) installed you can't use ADB commands (which the toolkits use). The solution was very simple. I just renamed the jb_hboot to PH98IMG.zip, rebooted into the bootloader and it was installed.
TWRP v. 2.20 flashed, for some reason my phone doesn't charge while plugged in and booted into this recovery. I guess I need to make sure I have a nice charge if I want to do anything major.
Installed ViperRez rom 1.03, now I'm toying around with it
Originally Posted by AshtonTS
Originally Posted by YTHero
My device is:
Stock rom and firmware (2.01.605.11)
Unlocked
AmonRA 3.15 recovery
Rooted
I want to run a custom (like ViperRez or CM9) ICS rom with the OTA (3.14.605.12) updated firmware.
So my process will be:
S-Off -> flash Hboot/radio/firmware files from 3.14.605.12 -> flash juopunut Bear hboot -> flash TWRP -> Flash ICS rom
Is my plan correct in that I should flash juopunutBear hboot after I flash the Hboot/radio/firmware files from 3.14.605.12? If so why?
Is there anything else that I should do in between these steps that I haven't identified? Am I taking any unnecessary risks by doing it this way?
Click to expand...
Click to collapse
Yeah, flash the RUU, then the JBear hboot, then TWRP/Amon Ra, then a Rom
Click to expand...
Click to collapse
I would do it beforehand. Once you are s-off, you can flash the latest firmware without installing the whole RUU also.
But it limits from getting the actual ota which I love to see
Sent from my ADR6425LVW using xda app-developers app
I would do it before and then after you S-Off run through this PH98IMG RUU. From talks, this is the OTA.
http://forum.xda-developers.com/showthread.php?t=1810931
Then flash the patched 2.25.2525 JB hboot from http://unlimited.io/hboot-downloads/
EDIT:
Alternatively you could S-Off, flash latest radios and patched hboot, then flash a rom of your choosing based on 605.10 or 605.12.
I'm still going to wait to see if we can get s-off on ics before updating today as I don't have the wire to currently do the exploit.
Sent from my ADR6425LVW using xda app-developers app
All I am saying is this. Why wait for the OTA when their are already roms based off 605.10, barely anything changed from it to 605.12. Also, S-Off will stick as long as you make it stick.
why wait for the ota when the ota was leaked?
YTHero said:
The main question is the title - Should you S-off before or after the OTA?
I have seen people around the forums (via a few searches) say that it is likely a good idea to perform S-off before OTA because we didn't know for sure if the OTA would close the S-off exploit. Now that the OTA is a known quantity, is that still the best route?
My device is:
Stock rom and firmware (2.01.605.11)
Unlocked
AmonRA 3.15 recovery
Rooted
I'm a little nervous about doing S-off, but I figure it will be really handy to have it once its done, and I understand it really is no big deal. My end goal is to run the Venom rom and then move to AOKP/CM9 once they have most of the bugs worked out. Would my best course of action be to S-Off, run the firmware updater, reinstall recovery (probably TWRP, seems like that is the most popular one at the moment), then flash my rom of choice? Will I need to re-root if I switch to a different recovery?
Click to expand...
Click to collapse
You are on Gingerbread firmware, that's the first thing to recognize. There's lots of development tools that were designed AFTER the Gingerbread firmware (2.xx is GB; 3.xx is ICS). In fact Amon Ra 3.15 was the version done after the ICS leak (because mount points were changed).
So you can (and probably should) do the S-OFF using the GB version over at Juopunut's site and then either wait for the ICS OTA to come to your phone or flash it in bootloader as a PH98IMG.ZIP (the RUU is available via Android Police, 3.14.605.12 is the "official" ICS, and I'm pretty sure its here on XDA but I don't remember the thread.)
If you don't want to wait for the OTA, it doesn't matter whether you are S-ON or S-OFF, you'll still have to flash the RUU in hboot. Both will completely wipe your phone, and the S-OFF process will wipe your CARD so use a different card before you do it!
Finally, to reiterate what's all over by now: the "official" update, 3.14.605.12 is only marginally different than the unofficial leak that's been out since May, 3.14.605.10, and the radios, kernel and hboot are all the same.
hgoldner said:
So you can (and probably should) do the S-OFF using the GB version over at Juopunut's site and then either wait for the ICS OTA to come to your phone or flash it in bootloader as a PH98IMG.ZIP (the RUU is available via Android Police, 3.14.605.12 is the "official" ICS, and I'm pretty sure its here on XDA but I don't remember the thread.)
If you don't want to wait for the OTA, it doesn't matter whether you are S-ON or S-OFF, you'll still have to flash the RUU in hboot. Both will completely wipe your phone, and the S-OFF process will wipe your CARD so use a different card before you do it!
Click to expand...
Click to collapse
I recieved the OTA today from Verizon, but deferred to take until I figured out what I want to do. If I understand what you are saying:
S-Off -> OTA -> install TWRP -> then Flash ViperRez or whatever rom
Taking the OTA seems like the easiest and most straight forward way of upgrading to ICS radios/hboot. Will I need to do anything else before or following the OTA? I feel like somewhere I read that I will need to patch the hboot because I will be S-off.
YTHero said:
I recieved the OTA today from Verizon, but deferred to take until I figured out what I want to do. If I understand what you are saying:
S-Off -> OTA -> install TWRP -> then Flash ViperRez or whatever rom
Taking the OTA seems like the easiest and most straight forward way of upgrading to ICS radios/hboot. Will I need to do anything else before or following the OTA? I feel like somewhere I read that I will need to patch the hboot because I will be S-off.
Click to expand...
Click to collapse
After you s off, flash juopunutBears hboot it should be on his website
Sent from my ADR6425LVW using xda app-developers app
Squirrel1620 said:
After you s off, flash juopunutBears hboot it should be on his website
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I'm trying to understand this post
http://forum.xda-developers.com/showpost.php?p=29715514&postcount=51
and this thread
http://forum.xda-developers.com/showthread.php?t=1614366
superchilpil said:
New firmware patch huh?
This is simply for those upgrading to ICS firmware on a GB rom Or and ICS rom that had the gingerbread patch flashed over it
Whats the difference between the stock Hboots and the JB/ENG Hboots?
Simply, These Hboots have fastboot commands enabled WITHOUT unlocking the bootloader
I suggest if you use fastboot alot to use these hboots
Click to expand...
Click to collapse
I'm just trying to figure out if I will have to reflash the juopunutBears hboot after I flash the Hboot/radio/firmware files from 3.14.605.12
So will it be:
S-Off -> Hboot/radio/firmware files from 3.14.605.12 -> juopunut Bear hboot ->install TWRP -> then Flash ViperRez or whatever ICS rom
YTHero said:
So will it be:
S-Off -> Hboot/radio/firmware files from 3.14.605.12 -> juopunut Bear hboot ->install TWRP -> then Flash ViperRez or whatever ICS rom
Click to expand...
Click to collapse
You got it right on.
Sent from my ADR6425LVW using xda app-developers app
Every rom I flash keeps screwing up and camera never opens up. I'm wanting to do the newest update but I haven't seen much about a root method for it. Is there an easier way to do it? I'm S-ON hboot 1.15.
So you want the ota?
om4 said:
So you want the ota?
Click to expand...
Click to collapse
yes, I don't care about s-off or cm10 fastboot flashing or anything to do with new hboot problems..
It's best to flash the stock rom and recovery for 1.15 and relock bootloader, then accept the ota and if you want to flash roms again just unlock and flash twrp then you can go back to flashing roms again
om4 said:
It's best to flash the stock rom and recovery for 1.15 and relock bootloader, then accept the ota and if you want to flash roms again just unlock and flash twrp then you can go back to flashing roms again
Click to expand...
Click to collapse
How would I do that? I'm pretty new to rooting and don't know how to do anything.
What is your current set up
om4 said:
What is your current set up
Click to expand...
Click to collapse
s-on hboot 1.15 im on rejuvenated 2.2
Subscribed to this thread because I may be wanting to unroot, update, then re-root soon.
Flash a stick rom, the 1.22 base I believe. Put the phone in fastboot and flash the original recovery image with adb
Camera doesn't work, wifi won't turn on, battery isn't charging. I'm waiting patiently till the note II is available.
om4 said:
Flash a stick rom, the 1.22 base I believe. Put the phone in fastboot and flash the original recovery image with adb
Click to expand...
Click to collapse
Can you dumb it down a lot more? I'm really confused on what to do.
I found this -> http://forum.xda-developers.com/showthread.php?t=1766628 is this right?