I want to be sure my DS can receive and install the imminent (?) ota ICS from HTC. Still a bit of a noob so read a lot of stuff on here and other forums (mainly non DS) but haven't really found definitive answers for the 'half rooted' device i.e. bootloader unlocked via htcdev, cwm flashed, s-on.
Main concerns are:
losing root
ota will not install because of /system/app and framework mismatch (after a few UOT mods) - boot animation and sound have also been changed in /system/customise/resource, also bloatware removed
ota issues with cwm installed
Originally first thing I did immediately after flashing cwm was a nandroid backup so that's available to me, which really only leaves the cwm and ota compatability question.
Is Rootkeeper an option or should I root from scratch again after ota?
If I receive notification of the ota availability, then restore from original backup (and maybe relock bootloader with htcdev?) will I then have lost the chance to install the ota?
A lot of questions and ifs, I know, I just don't want to screw up the chance to try the official ICS before going for a custom rom. Thanks in advance.
Hboot 2.00.0002
Android 2.3.5
Sense 3.0
Stock rom/kernel/radio
Sorry, I'm pretty sure HTC Dev unlocked devices can't get OTA updates. I'm completely sure devices with CWM can't (you need stock HTC recovery). Since you already have a custom recovery, it would be better to get a custom ROM, much fastr and tweaked
As shrome99 said..
To get the OTA update you will need to have STOCK recovery, and a relocked bootloader to get the OTA.
__________________
This assumes you are 100% stock on the operating side.
foX2delta said:
As shrome99 said..
To get the OTA update you will need to have STOCK recovery, and a relocked bootloader to get the OTA.
__________________
This assumes you are 100% stock on the operating side.
Click to expand...
Click to collapse
I got OTA updates with both an unlocked bootloader and custom recovery. It's true the update won't install till you're back on stock recovery but the locked bootloader isn't necessary. I was however updating from Stock Sense 2.1
Warning: do not install it if you get a OTA message if rooted!
It will lead to the dreaded red triangle screen. Your best bet is to just install CWM/4EXT then when the new update comes, install the ICS prerooted ROM by Adidas.
Sent from my HTC Desire S using xda premium
The "dreaded" triangle screen is just the stock recovery.
Jack_R1 said:
The "dreaded" triangle screen is just the stock recovery.
Click to expand...
Click to collapse
That won't boot back to your ROM therefore you are stuck.
No root/s-off, therefore you can't do much about it. (Unless you get the RUU to run)
And for the average user, this is difficult for them to understand. Hence it has picked up its name as the 'dreaded triangle screen' over several different HTC device threads.
Sent from my HTC Desire S using xda premium
Cheers for the input.. did a bit more snooping and (if and when I get the ota shout).. I think I can go back with original nandroid to pre-root, before superuser went in. Then I'll give Android Recovery Manager (Sensation Android Development forum) a lash, just to see if I can flash back the stock recovery img.
If any nice ota comes my way which won't take then I'll try htcdev to relock the bootloader and give it another lash!
Think (hope) it'll work.. couldn't find a stock img anywhere yet so I'm hoping it's included in the above manager.. was going to try tonight but, typical, my connection went..
'Your best bet is to just install CWM/4EXT then when the new update comes, install the ICS prerooted ROM by Adidas.'
I have cwm, not sure why I would wait for the update then install a custom ics rom..
You must install stock recovery to install OTA update.OTA won't install, if you have custom recovery or S-off.But I recommend to install ROM, using zip or RUU.
From htcdev:
(after unlocking bootloader) Some content on your device may also be invalidated and cannot be accessed any more because of invalid DRM security keys. This includes content that you may have purchased through a 3rd party vendor and through HTC. Furthermore, although you will still be able to receive updates to your device via FOTA (“firmware over the air”), we do not guarantee that updating your device via FOTA will not render your device unusable.
That answers the question re the bootloader but I'm struggling to find the stock recovery img to flash.
I suppose I can extract and then flash it, possibly from this: RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed.exe, even though my device is 2.10.161.3 (161 is Vodafone). The radio is the same as mine which is irrelevant anyway, right?
I know it would be easier to install the RUU but after hours of research I would really like to be able to nail this so I have the option of reverting back to VF stock, as I still have 18 months warranty left.
Can anyone can confirm if I'm on the right track pls?
I suppose, if you haven't GoldCard or SuperCID recovery won't flash(signature verify failed).Download Zip/exe of your ROM , and flash that recovery.After that you might be able to install FOTA.No guarantee it will work.
scandron said:
I suppose, if you haven't GoldCard or SuperCID recovery won't flash(signature verify failed).Download Zip/exe of your ROM , and flash that recovery.After that you might be able to install FOTA.No guarantee it will work.
Click to expand...
Click to collapse
It will flash, because his bootloader is unlocked.
He won't need a goldcard cause he is flashing a voda RUU recover, future I don't think it will even come into play when using fastboot to flash it.
However I suggest EVERYONE who is a little unsure make a goldcard.
Thanks all, trying to get a gold card now just to be sure.. however just intend to extract and flash the recovery img from the ruu, once I can be sure I have the right one.. the stock recovery in HTC devices is generic, no?
i also have a doubt.
what i wanted to know is that will i still be able to update my device OTA if i have unlocked the bootloader, rooted my device but havent installed a custom recovery?my device is rooted nothing more than that. and after relocking my bootloader (i dont mind loosing root) will i be able to update OTA?
sorry for being irrelevant but i didnt want to start a new thread for a doubt of this magnitude.
See post #10
Related
Some months ago I followed guides here to SuperCID, s-off and install a custom ROM. The past few days my touch screen has become unresponsive, at first this was fixed by reflashing the ROM, but now, nothing will fix it, and the touch screen is completely unresponsive. So it seems I will have to return it to the shop to send off for repair. Of course I don't want them to have any reason to say it was the custom ROM that has caused it, warranty void blah blah so need to restore it to stock.
So far I have re-flashed with a stock ROM and changed the CID to what it was, and s-on. I can't remember whether I changed the MID, currently it is PG58*****, though I believe it should be PG5813001, and I'm not sure how to go about changing this (or if it needs changing, will they look into that?)
Another thing I'm unsure of, I downloaded the ROM from here: http://forum.xda-developers.com/showthread.php?t=1074559 I don't know if these ROMs are rooted or not? Is there any way to tell? Or is it a safe assumption they are not?
And finally, hboot, before flashing the stock ROM, this was 1.17, now it is 1.18. Is there anything in here that might suggest the phone has been tinkered with in ways they don't like? I just want to make sure I have covered everything so they don't immediately refuse to repair. If I have missed anything else please let me know.
Thanks.
Edit: I've also read about flashing stock recovery, though this may be included in the the stock ROM RUU I used, can someone confirm?
None of the 130 viewers have any advice on this one?
HB489 said:
Some months ago I followed guides here to SuperCID, s-off and install a custom ROM. The past few days my touch screen has become unresponsive, at first this was fixed by reflashing the ROM, but now, nothing will fix it, and the touch screen is completely unresponsive. So it seems I will have to return it to the shop to send off for repair. Of course I don't want them to have any reason to say it was the custom ROM that has caused it, warranty void blah blah so need to restore it to stock.
So far I have re-flashed with a stock ROM and changed the CID to what it was, and s-on. I can't remember whether I changed the MID, currently it is PG58*****, though I believe it should be PG5813001, and I'm not sure how to go about changing this (or if it needs changing, will they look into that?)
Another thing I'm unsure of, I downloaded the ROM from here: http://forum.xda-developers.com/showthread.php?t=1074559 I don't know if these ROMs are rooted or not? Is there any way to tell? Or is it a safe assumption they are not?
And finally, hboot, before flashing the stock ROM, this was 1.17, now it is 1.18. Is there anything in here that might suggest the phone has been tinkered with in ways they don't like? I just want to make sure I have covered everything so they don't immediately refuse to repair. If I have missed anything else please let me know.
Thanks.
Edit: I've also read about flashing stock recovery, though this may be included in the the stock ROM RUU I used, can someone confirm?
Click to expand...
Click to collapse
To Flash stock recovery read 2 in HERE I believe these ROMs are not rooted, to check just look for SuperSU or Superuser app, if it is not installed you are not rooted. Don't worry at all they'll never find out you rooted your phone, usually they never check. Read THIS guide it has the answer to all your questions regarding revert to stock
elvisypi said:
To Flash stock recovery read 2 in HERE I believe these ROMs are not rooted, to check just look for SuperSU or Superuser app, if it is not installed you are not rooted. Don't worry at all they'll never find out you rooted your phone, usually they never check. Read THIS guide it has the answer to all your questions regarding revert to stock
Click to expand...
Click to collapse
Thanks, though unfortunately I can't check what apps are installed due to the touch screen being unresponsive. But if that's not something they'll look into then fair enough.
The second thread doesn't quite answer everything (whether the ROMs are rooted for example), however, the first thread details extracting stock recovery from an RUU, so I guess that means I don't need to worry about that as it would have been flashed with the ROM.
One other thing - do they require the SD card to be sent also? Is there anything on there that should be removed? Any data relating to apps that use root privileges might raise an eyebrow; is it safe to do a reformat of the SD card? I'm not sure how much is on there that is vital the system.
Thanks for your answer.
HB489 said:
Thanks, though unfortunately I can't check what apps are installed due to the touch screen being unresponsive. But if that's not something they'll look into then fair enough.
The second thread doesn't quite answer everything (whether the ROMs are rooted for example), however, the first thread details extracting stock recovery from an RUU, so I guess that means I don't need to worry about that as it would have been flashed with the ROM.
One other thing - do they require the SD card to be sent also? Is there anything on there that should be removed? Any data relating to apps that use root privileges might raise an eyebrow; is it safe to do a reformat of the SD card? I'm not sure how much is on there that is vital the system.
Thanks for your answer.
Click to expand...
Click to collapse
No the ROMs in the second post are not rooted they are stock. The whole point of the post is to restore stock( read 3. RUU to restore stock). Stock recovery is smth else from stock ROM. You also need stock recovery to install OTA updates from google. Use Android Recovery Manager to download and install your stock recovery. Than in fastboot the stock recovery.img. I can't assure you that they won't notice you were rooted, but they usually don't. Keep in mind that when you unlocked your bootloader you accepted to void your warranty, and your serial number is in HTCs website. (theoretically) you can never be sure they won't discover you, but practically installing stock ROM, stock recovery, locking bootloader and getting back to s-on is enough to not get spotted
And you can format the SD Card if you want, you made a fresh install so there shouldn't be any files regarding it, just the files from the old system, but do a backup first just in case
elvisypi said:
No the ROMs in the second post are not rooted they are stock. The whole point of the post is to restore stock( read 3. RUU to restore stock). Stock recovery is smth else from stock ROM. You also need stock recovery to install OTA updates from google. Use Android Recovery Manager to download and install your stock recovery. Than in fastboot the stock recovery.img. I can't assure you that they won't notice you were rooted, but they usually don't. Keep in mind that when you unlocked your bootloader you accepted to void your warranty, and your serial number is in HTCs website. (theoretically) you can never be sure they won't discover you, but practically installing stock ROM, stock recovery, locking bootloader and getting back to s-on is enough to not get spotted
And you can format the SD Card if you want, you made a fresh install so there shouldn't be any files regarding it, just the files from the old system, but do a backup first just in case
Click to expand...
Click to collapse
Thanks again. If I recall correctly I used revolutionary, not HTC dev so I don't think they'll have my imei? Android recovery manager doesn't have the correct version for my phone, but further down the post it another method is extracting the recovery from the RUU, which is why I assumed stock recovery would have been installed when I flashed the RUU. I guess there is no harm in manually flashing the recovery to be sure though.
HB489 said:
Thanks again. If I recall correctly I used revolutionary, not HTC dev so I don't think they'll have my imei? Android recovery manager doesn't have the correct version for my phone, but further down the post it another method is extracting the recovery from the RUU, which is why I assumed stock recovery would have been installed when I flashed the RUU. I guess there is no harm in manually flashing the recovery to be sure though.
Click to expand...
Click to collapse
No HTCdev is not a recovery, it's the only way of unlocking your bootloader, which you have done for sure. But don't worry I assure you they don't go so deep. There's nothing wrong in flashing manually the recovery. Good luck
After two weeks of forum crawling and surviving 2 soft-bricking incidents, I've finally decided to reach out for help from the experts :crying:
Currently I have an ATT HOX, unlocked/rooted/SuperCID - running stock ICS (4.0.4).
My goal is to get JB on it and then flash to Blade ROM (I tried flashing to Blade with ICS - OOPS!)
Even though the info is on the forums - it's not all together in a streamlined format for me to follow - I feel I could get lost and screw it up (again)
From what I gathered from reading - here is what I "think" I need to do from my current phone state:
1. Facepalm S-Off
2. Install OTA Rootkeeper then backup root
3. Flash stock recovery
4. Re-Lock Bootloader
5. Flash OTA ATT JB.zip using stock recovery
6. Unlock Bootloader
7. Flash TWRP
8. Restore backup root with OTA RK
9. Flash Blade ROM
Can someone please check my thinking and make sure I'm not missing something?
Or any recommendation of an easier process? I feel I'm going to get lost somewhere in those steps and end up in Oz.
Or maybe a recommendation on an awesome ICS Rom? (so I can avoid confusing myself)
I'm terrified of another 3AM morning and a bricked-out HOX.
Thanks in advance!
Do you mean this rom: http://forum.xda-developers.com/showthread.php?t=2134328?
Because that's a rom for the quad-core Tegra One X. If you've been doing that, it's no wonder you got bricked.
You don't need OTA Rootkeeper. You can just flash a rooted rom.
2 major points:
1) As already mentioned, Blade is not for our phone, its for the quad core One X. Stay within this forum section. If you are looking at any XDA thread that just says "HTC One X" (no mention of "AT&T, Rogers" etc.) near the top of the screen, you are in the wrong section. Stick to the forum section that mentions AT&T. Flashing a ROM for the quad core version won't work, and might also hard brick your phone.
2) Aside from S-Off which is a good idea) you don't need to mess with any of the stuff you mentioned (Rootkeeper, stock recovery, OTA zip) in order to flash a JB based custom ROM if you are already bootloader unlocked and have TWRP. With S-off, just flash the ROM. If S-on, just flash the ROM, then flash the boot.img with fastboot (if hboot 1.14 or higher).
I'm not sure how you got the notion that you need to do all these other steps (maybe some process for the quad core forum?).
redpoint73 said:
I'm not sure how you got the notion that you need to do all these other steps (maybe some process for the quad core forum?).
Click to expand...
Click to collapse
<---- desperate noob
...and I also came from the original Samsung Vibrant. With that phone, I also had the idea that I could only use a ROM based of the current android version. Hence the carry over of thought from that side.
I can't believe I lost sleep over the simplicity of it all.
But.... just to make sure I understand this correctly - Even if I have ICS currently installed, I can flash a JB based ROM without issues?
Thanks a ton guys!
razorc03 said:
But.... just to make sure I understand this correctly - Even if I have ICS currently installed, I can flash a JB based ROM without issues?
Click to expand...
Click to collapse
Correct you can flash it.
But some people have been having issues on JB coming from older firmware. If you have problems later, then ruu'ing and updating is warranted. Right now it's overkill.
iElvis said:
Correct you can flash it.
But some people have been having issues on JB coming from older firmware. If you have problems later, then ruu'ing and updating is warranted. Right now it's overkill.
Click to expand...
Click to collapse
Would I be able to RUU to a stock JB? Or would I have to start from stock ICS again?
razorc03 said:
Would I be able to RUU to a stock JB? Or would I have to start from stock ICS again?
Click to expand...
Click to collapse
There are no JB ruu's as far as I know. But you can run the 2.20 ruu and then flash the 3.18 ota, then unlock again and reflash everything. That's what I did. Whole process took about half an hour and wasn't complicated. Just be sure you're s-off.
iElvis said:
There are no JB ruu's as far as I know. But you can run the 2.20 ruu and then flash the 3.18 ota, then unlock again and reflash everything. That's what I did. Whole process took about half an hour and wasn't complicated. Just be sure you're s-off.
Click to expand...
Click to collapse
Thanks for the info. But I need to bug you again.:angel:
A few questions about the ruu method. After you ruu, does that remove root, lock bootloader, and goes back to s-on?
And since I love numbered steps, here is how I am viewing it with my inexperienced understanding with question marks:
1. Check for S-off
2. Lock bootloader? (I guess not with S-off)
3. Run ruu 2.20 exe
4. Flash 3.18 ota
5. Rerun superCID (X-Factor xploit)?
6. Unlock bootloader
7. Flash TWRP
8. Flash ROM (Assuming S-off wasn't changed during the ruu)
I would love to be at your confidence level to run it it 30 minutes. One day I guess....
Before you run a ruu, you have to relock. When you run it, it wipes your entire phone and returns it to stock-out-of-the-box (except for s-off). So you need to back up anything you want to keep.
Here's a corrected list:
1. S-off
2. Relock in fastboot
3. Run ruu
4. Copy OTA update.zip to internal storage
5. Flash in stock recovery
6. Unlock
7. Flash custom recovery
8. Flash rooted rom
None of this affects s-off. AFAIK, the only way to be s-on again is manually change it in fastboot.
I wouldn't do all this unless you have a reason to, as there are spots in here where you can get tripped up if you're a complete noob.
iElvis said:
Before you run a ruu, you have to relock. When you run it, it wipes your entire phone and returns it to stock-out-of-the-box (except for s-off). So you need to back up anything you want to keep.
Here's a corrected list:
1. S-off
2. Relock in fastboot
3. Run ruu
4. Copy OTA update.zip to internal storage
5. Flash in stock recovery
6. Unlock
7. Flash custom recovery
8. Flash rooted rom
None of this affects s-off. AFAIK, the only way to be s-on again is manually change it in fastboot.
I wouldn't do all this unless you have a reason to, as there are spots in here where you can get tripped up if you're a complete noob.
Click to expand...
Click to collapse
Thanks for the checklist! It makes me feel safer to know an exit strategy so I don't panic if/when stuff goes bad.
I noticed you didn't list a step to re-root through custom recovery after step 7. Is the previous root still in place?
razorc03 said:
...and I also came from the original Samsung Vibrant. With that phone, I also had the idea that I could only use a ROM based of the current android version. Hence the carry over of thought from that side.
Click to expand...
Click to collapse
This varies completely by device, and firmware versions. Never assume that something you learned on another Android device applies to a different device.
razorc03 said:
I noticed you didn't list a step to re-root through custom recovery after step 7. Is the previous root still in place?
Click to expand...
Click to collapse
No, it's that once you're unlocked, you can re-root just by flashing a rooted rom.
So the official OTA Jellybean update has been out for awhile now, but I'm just now trying to get to the bottom of my issue. My issue being that my OTA update downloaded but didn't install. Please note that, 1. I am an amateur with roms and such, and 2. My phone is rooted.
I have opened the OTA zip file with the Rom Manager's Rom Pre-installation, but I am lost on what to do from there. I figure there is a way I can install this update on my phone manually.
One more thing, I have tried flashing a rom before, but there was an error and I had to restore to my stock rom.
Attachment is a screenshot of the Rom Pre-installation screen.
Sent from my HTC One X using xda app-developers app
I would suggest not using Rom Manager for anything. Flash it in recovery. Plus that looks like an old version.
Sent from my Evita
If you have custom recovery installed, OTA will fail. OTA is looking for stock recovery to perform the install. If it doesn't find it, it stops.
Unlocked bootloader may also cause OTA to fail, can't remember.
timmaaa said:
I would suggest not using Rom Manager for anything. Flash it in recovery. Plus that looks like an old version.
Sent from my Evita
Click to expand...
Click to collapse
As I said, previously, I have had issues with flashing roms. But according to Rom Manager, it says the zip I have is a "Rom addon". Should that give me a different result than flashing a rom?
redpoint73 said:
If you have custom recovery installed, OTA will fail. OTA is looking for stock recovery to perform the install. If it doesn't find it, it stops.
Unlocked bootloader may also cause OTA to fail, can't remember.
Click to expand...
Click to collapse
Well, that's the cause of the issue. I have TWRP installed, and I have an unlocked bootloader.
caskla said:
As I said, previously, I have had issues with flashing roms. But according to Rom Manager, it says the zip I have is a "Rom addon". Should that give me a different result than flashing a rom?
Click to expand...
Click to collapse
ROM Manager is for flashing custom ROMs, and in the case of the "addons" for custom mods packaged as flashable zips. I would not expect it to install official OTAs.
What "issues" have you had with flashing ROMs? If you are rooted and bootloader unlocked, I wouldn't typically recommend to install OTAs at all. Install a custom ROM or stock rooted (if you want a stock type ROM), otherwise, why did you unlock in the first place?
Also, if you are SuperCID (probably the case since you are rooted) and S-on, you are lucky the OTA didn't install. It would have bricked the phone. Same thing if you try to RUU. If you really want to return to stock, you either need to change back to the proper AT&T CID, or S-off, then run the RUU.
Hi all,
I apologize if this has been answered before, but I had trouble finding it here. I am currently rooted on a stock backup, but I am running a custom recovery. I am not sure where to find the stock recovery image for my device. I am using the HTC One M8 through Verizon, and I know that the new firmware update is coming out soon, and I'd like to be able to just OTA update my phone so that I can reflash a custom recovery and install the newest VenomROM. I have flashed a custom recovery before (obviously), but I didn't know if it mattered which firmware base you are running. I read somewhere that the recovery is totally separate from the OS, and it is meant to be an alternative to booting into the OS in case of a problem, but I want to be sure. If there is a specific recovery I need to use and someone here knows where I can find it, that'd be great. I found the collection of stock recoveries, but I'm having trouble figuring out which one I need to use. Any and all help is appreciated, thanks.
EDIT: My CID is VZW__001
My VERSION-MAIN is nothing. There's is just nothing next to this label.
I tried locating it on the collection of stock recoveries, but couldn't find it. I'm not sure why this is.
It takes more than stock recovery to take the OTA. The /system has to be essentially stock. Some mods (e. g. enabling powersave) may also csuse the OTA install to fail. There is a thread with a pseudo RUU. You ought to be able to get stock recovery there.
My name is Harold and I'm a flashaholic....
hgoldner said:
It takes more than stock recovery to take the OTA. The /system has to be essentially stock. Some mods (e. g. enabling powersave) may also csuse the OTA install to fail. There is a thread with a pseudo RUU. You ought to be able to get stock recovery there.
My name is Harold and I'm a flashaholic....
Click to expand...
Click to collapse
Hi there,
I actually just used the psuedo RUU tool (I assume this is the one you are talking about? http://forum.xda-developers.com/showthread.php?t=2727831)
I just finished using this tool, but when I went to check the recovery, all I get is a big red triangle with an exclamation point in the middle. Nothing else. So, I'm guessing that recovery didn't flash properly? But I'm honestly not completely sure. I would screenshot it, but I can't do that. Any help is appreciated.
EDIT: I found out that pressing volume up and power gives more options. I assume I am all good to go now? I am still rooted, and I'm not sure if that is a problem. I am stock, s-off and rooted, but I don't have any mods installed.
You can't do anything in stock recovery except take an OTA, assuming everything else is stock. You can't do Nandroids, flash zips, etc. Looks like you have stock recovery.
My name is Harold and I'm a flashaholic....
hgoldner said:
You can't do anything in stock recovery except take an OTA, assuming everything else is stock. You can't do Nandroids, flash zips, etc. Looks like you have stock recovery.
My name is Harold and I'm a flashaholic....
Click to expand...
Click to collapse
Yeah I just figured out how the more options appear. I assume I'm good to go for the OTA now? I've got stock recovery, running a stock backup, s-off and I'm still rooted, but I think those are not a problem. I am not running any mods.
ChuckFinley1992 said:
Yeah I just figured out how the more options appear. I assume I'm good to go for the OTA now? I've got stock recovery, running a stock backup, s-off and I'm still rooted, but I think those are not a problem. I am not running any mods.
Click to expand...
Click to collapse
You should be good to go. A cautionary note, however, is that if you are rooted (even if S-OFF), it's not always advisable to take the OTA because frequently OTA's plug exploits used to secure root, etc. There was a definite difference between the original stock Verizon M8 ROM releated 3/25/14 and the minor update which followed, and some were unable (myself included) to secure stable root and/or S-OFF with weaksauce, having to acquire a license to Sunshine instead.
I intend to stick on my custom ROM and recovery and trust the developers to massage the OTA once it's out and have, literally within days if not hours, an updated ROM/firmware zip file that will more than adequately fit the bill.
hgoldner said:
You should be good to go. A cautionary note, however, is that if you are rooted (even if S-OFF), it's not always advisable to take the OTA because frequently OTA's plug exploits used to secure root, etc. There was a definite difference between the original stock Verizon M8 ROM releated 3/25/14 and the minor update which followed, and some were unable (myself included) to secure stable root and/or S-OFF with weaksauce, having to acquire a license to Sunshine instead.
I intend to stick on my custom ROM and recovery and trust the developers to massage the OTA once it's out and have, literally within days if not hours, an updated ROM/firmware zip file that will more than adequately fit the bill.
Click to expand...
Click to collapse
That does sound pretty appealing. I've never flashed firmware before though, and I wouldn't want to mess anything up. I remember seeing on the VenomROM firmware section, the easiest way to flash new firmware is to just grab the OTA update. The other way involved using some other program that I have not used before. I am overestimating how difficult installing new firmware is?
ChuckFinley1992 said:
That does sound pretty appealing. I've never flashed firmware before though, and I wouldn't want to mess anything up. I remember seeing on the VenomROM firmware section, the easiest way to flash new firmware is to just grab the OTA update. The other way involved using some other program that I have not used before. I am overestimating how difficult installing new firmware is?
Click to expand...
Click to collapse
Firmware (splash screen, radios, hboot, recovery) are "flashed" with an S-OFF handset via fastboot from the bootloader, while connected to PC. I believe (again, based upon the RUU thread I mentioned previously which you seem to have found) that it may also be possible to flash from hboot using an update.zip file (I think the M8 file is called PB06IMG.zip, but don't hold me to that --- every phone has its own such file format/name.)
ROMs and mods are typically flashed via recovery.
hgoldner said:
Firmware (splash screen, radios, hboot, recovery) are "flashed" with an S-OFF handset via fastboot from the bootloader, while connected to PC. I believe (again, based upon the RUU thread I mentioned previously which you seem to have found) that it may also be possible to flash from hboot using an update.zip file (I think the M8 file is called PB06IMG.zip, but don't hold me to that --- every phone has its own such file format/name.)
ROMs and mods are typically flashed via recovery.
Click to expand...
Click to collapse
Okay, I may look into that. I've only seen an RUU flashed via hboot, so I'd have to look into it. At the very least though, I'd imagine someone will post the instructions on how to flash the firmware when it comes out.
Thanks so much for your help!
hgoldner said:
I intend to stick on my custom ROM and recovery and trust the developers to massage the OTA once it's out and have, literally within days if not hours, an updated ROM/firmware zip file that will more than adequately fit the bill.
Click to expand...
Click to collapse
+100 for this!
I am reading dozens of posts in all kinds of threads of people just dying to take that OTA...
Why???
I would not touch that new firmware with a 100 foot pole until the devs have figured out what it breaks!!!
I predict a flood of posts in the line of:
"I flashed back to stock to take the OTA and now weaksauce is not working - how do I get root back?"
What's the hurry?????
I currently have S-Off and have it rooted through Weaksauce and SuperSu I believe. I have flashed ROMs through TWRP but did not like them, so I recovered back into my 4.4.2 stock. If I update to 4.4.4 by Verizon's OTA, will I lose my root and S-Off?
kinda a noob but...
steezy123 said:
I currently have S-Off and have it rooted through Weaksauce and SuperSu I believe. I have flashed ROMs through TWRP but did not like them, so I recovered back into my 4.4.2 stock. If I update to 4.4.4 by Verizon's OTA, will I lose my root and S-Off?
Click to expand...
Click to collapse
I'm not a hundred percent but I think the only way you lose it is if it upgrades the boot.img search for tigers posts because from the way it sounded to me if you flashed back to stock you'd have all ready lost your s-off.... Unless you've flashed one of the stock with the boot.img and recovery img removed. If so I'm pretty sure your good for the firmware upgrade if it'll ota without stock (or forged) boot.img file... Anyway man I'm slightly baked and never been accused of being smart enough to remember **** I read two weeks ago so search "tigerstown" posts and threads and read man and when you understand all a bit better than me then come message me and we'll discuss it a bit so it'll stick to my head a lil longer than last time man. Hope my rambleing might have shed some light on the subject or at least pointed you to the posts that know lol goodluck
The only way to "lose" s-off is to issue the fastboot command to set that flag which many smart people would never advise you do anyway. Nothing we are talking about here will do that automatically.
If you're s-off and on a custom Rom of any sort, I would recommend updating the firmware through tigerstown's method the previous poster referred to. If you're going to the trouble to flash everything necessary to take the ota, you may as well just flash his file and be done.
If you prefer stock, I would recommend you flash a stock-based Rom like CleanRom or NuSense. They come pre-rooted with some bloat removed and just a few tweaks added like write-protection removed, init-d support, etc.
If you really insist on running pure stock with root then you should at least root properly by uninstalling weak sauce and flashing the su binaries in recovery.
cntryby429 said:
The only way to "lose" s-off is to issue the fastboot command to set that flag which many smart people would never advise you do anyway. Nothing we are talking about here will do that automatically.
If you're s-off and on a custom Rom of any sort, I would recommend updating the firmware through tigerstown's method the previous poster referred to. If you're going to the trouble to flash everything necessary to take the ota, you may as well just flash his file and be done.
If you prefer stock, I would recommend you flash a stock-based Rom like CleanRom or NuSense. They come pre-rooted with some bloat removed and just a few tweaks added like write-protection removed, init-d support, etc.
If you really insist on running pure stock with root then you should at least root properly by uninstalling weak sauce and flashing the su binaries in recovery.
Click to expand...
Click to collapse
Thanks for all help, I'll start readin up. Just one question: let's say I update my firmware to 4.4.4 from Verizon's OTA, will I be able to flash this clean rom via TWRP? http://forum.xda-developers.com/showthread.php?t=2732877
The only reason I ask is because it says the user must be running 4.4.4 firmware to flash the rom and the only way I know how to get 4.4.4 is from Verizon's OTA
You can get everything you need from Verizon's 4.4.4 release by flashing the no boot no recovery file from the tigerstown thread mentioned earlier. It's the first file listed in his op. The rest of the ota contains the recovery (which you don't want since you need your custom recovery to flash custom ROMs) and the boot.img/kernel (which you don't need since every room comes with a kernel). It's not wrong till go back to stock to take an ota, it's just unnecessarily difficult when people like tigerstown make it so easy for us to accomplish the same thing.