ok so I was an original GS III owner (I preordered, used the original root66, waited for the unlocked bootloader, etc.)
I just rx'ed a 2nd replacement because the power button fell off my first replacement (my 1st gsIII had a faulty modem).
This one came preloaded with the 2nd OTA (VRALHE)
I was wondering the correct method to go about setting it up...
1.) odin the original root66 VRALF and continue in the same way I did with my original one (dd a TWRP and the insecure bootloader)?
2.) I could follow the directions in section 1 here: http://forum.xda-developers.com/showthread.php?t=1762709
and odin a pre-rooted VRBLJ1. It then says I can just go ahead and add a custom recovery (it mentions the EZ app but I'd rather just dd. then do the insecure aboot the same way)
3.) I could follow the directions here: http://forum.xda-developers.com/showthread.php?t=1974114
it mentions ODINing the VRBLJ1 leak and then ODINing a custom recovery but the recoveries INCLUDE "VRBLJ1 Bootchain." Why?
according to Invisiblek (http://rootzwiki.com/topic/29256-ro...-unlock-sch-i535-d2vzwverizon-galaxy-s-iii/):
What the locked bootloader prevents us from doing is flashing, via odin, a custom recovery or kernel. What we can do however, is revert to an older (semi-insecure) bootchain which we have acquired, flash our custom recovery, and then continue on from our freshly flashed custom recovery by flashing an unlocked bootloader and anything else we want.
Kernels from the newer OTA's prevent us from doing this process. We'll need to flash a kernel too...
Click to expand...
Click to collapse
he mentions flashing the VRALEC and then later (after flashing the VRALF2 kernel and a custom recovery) the VRALF2 bootchain. His explanation makes sense, but the other threads say to use the VRBLJ1 bootchain. why all the conflicting info?
Also, as I wrote this I used the rootDebugFS thing on my freshly rx'ed VRALHE. i then dd'ed a recovery and the insecure aboot. Everything is working fine. So what's all the fuss about? and will I encounter problems if I try to odin anything, like invisiblek said?
Thanks
preusstang said:
ok so I was an original GS III owner (I preordered, used the original root66, waited for the unlocked bootloader, etc.)
I just rx'ed a 2nd replacement because the power button fell off my first replacement (my 1st gsIII had a faulty modem).
This one came preloaded with the 2nd OTA (VRALHE)
I was wondering the correct method to go about setting it up...
1.) odin the original root66 VRALF and continue in the same way I did with my original one (dd a TWRP and the insecure bootloader)?
2.) I could follow the directions in section 1 here: http://forum.xda-developers.com/showthread.php?t=1762709
and odin a pre-rooted VRBLJ1. It then says I can just go ahead and add a custom recovery (it mentions the EZ app but I'd rather just dd. then do the insecure aboot the same way)
3.) I could follow the directions here: http://forum.xda-developers.com/showthread.php?t=1974114
it mentions ODINing the VRBLJ1 leak and then ODINing a custom recovery but the recoveries INCLUDE "VRBLJ1 Bootchain." Why?
according to Invisiblek (http://rootzwiki.com/topic/29256-ro...-unlock-sch-i535-d2vzwverizon-galaxy-s-iii/):
he mentions flashing the VRALEC and then later (after flashing the VRALF2 kernel and a custom recovery) the VRALF2 bootchain. His explanation makes sense, but the other threads say to use the VRBLJ1 bootchain. why all the conflicting info?
Also, as I wrote this I used the rootDebugFS thing on my freshly rx'ed VRALHE. i then dd'ed a recovery and the insecure aboot. Everything is working fine. So what's all the fuss about? and will I encounter problems if I try to odin anything, like invisiblek said?
Thanks
Click to expand...
Click to collapse
I'm assuming since VRBLJ1 is the newest JB leak then it uses the newer boot chain. The only reason you would need that boot chain to unlock the bootloader is if you used Odin to flash the newest VZW JB leak onto your phone. Then you would need it to unlock the VRBLJ1 JB leak. If you are are any of the ICS stock ROMs and want to unlock you can use the old way of doing it. The post you are reading from invisiblek is old, it was when we were on the VRALFW stock ROM.
Now I have no clue why you would want to use Odin to flash the newest JB leak when you can do it by downloading the version of the ROM made to be flashed with TWRP or CWM. I would love to have a dev or someone knowledgeable about these things to chime in and tell us if there is any benefit to using Odin to update to the newest JB leak or if there is no difference between having the JB leak or one of the OTA's on your phone before you flash a ROM.
Sent from one of the many Anthropomorphic Personalities on the Disc
shangrila500 said:
I'm assuming since VRBLJ1 is the newest JB leak then it uses the newer boot chain. The only reason you would need that boot chain to unlock the bootloader is if you used Odin to flash the newest VZW JB leak onto your phone. Then you would need it to unlock the VRBLJ1 JB leak. If you are are any of the ICS stock ROMs and want to unlock you can use the old way of doing it. The post you are reading from invisiblek is old, it was when we were on the VRALFW stock ROM.
Now I have no clue why you would want to use Odin to flash the newest JB leak when you can do it by downloading the version of the ROM made to be flashed with TWRP or CWM. I would love to have a dev or someone knowledgeable about these things to chime in and tell us if there is any benefit to using Odin to update to the newest JB leak or if there is no difference between having the JB leak or one of the OTA's on your phone before you flash a ROM.
Sent from one of the many Anthropomorphic Personalities on the Disc
Click to expand...
Click to collapse
Its just another way of basically doing the same thing. If your already rooted and have cwm recovery, then flashing a J1 rom via cwm or twrp recovery is by far the easiest method. Now if your stock and unrooted, it would be easier to odin root66 J1 , then unlock and get cwm recovery via the ez unlock/recovery apps. This is why I have 2 different methods in my guide...I also chose to not flash bootchains unless its a last resort because they can perma brick a device if something goes wrong. Also I like to use methods that dont trip the flash counter, makes for one less thing to do if the device ever needs to be returned.
droidstyle said:
Its just another way of basically doing the same thing. If your already rooted and have cwm recovery, then flashing a J1 rom via cwm or twrp recovery is by far the easiest method. Now if your stock and unrooted, it would be easier to odin root66 J1 , then unlock and get cwm recovery via the ez unlock/recovery apps. This is why I have 2 different methods in my guide...I also chose to not flash bootchains unless its a last resort because they can perma brick a device if something goes wrong. Also I like to use methods that dont trip the flash counter, makes for one less thing to do if the device ever needs to be returned.
Click to expand...
Click to collapse
Gotcha, that's been bothering me for a few days. I remember when I was flashing on my RAZR that the stock OTA was the base for everything and if you didn't have the latest OTA some of the ROMs wouldn't run on your phone until you updated and some of the older ROMs wouldn't work until they had been updated to work on the newest OTA or leak. The ROMs were just overlays and usually only added a little bit of added performance or functionality.
Would updating to the latest OTA via Odin add any benefits like it did on the RAZR ? I know the RAZR wasn't unlocked and we weren't flashing ROMs like we do on the GS3 but.....
Sent from one of the many Anthropomorphic Personalities on the Disc
no not on samsung devices...you can go from f2 to the latest with no issues.
droidstyle said:
no not on samsung devices...you can go from f2 to the latest with no issues.
Click to expand...
Click to collapse
No I get that, I was meaning are there any positive side effects from using the newest JB leak as your base ROM before flashing a new one. Like flashing the new JB leak via Odin, then unlocking and flashing a new ROM on top of it. Will there be any benefits like there were on the RAZR or when we flash in custom recoveries does it completely do away with the stock ROM that was on the system partition and replace it with whatever we flash? I know on the RAZR you would use the ROM you were on as a base you flash whatever else you wanted and there were benefits to having a certain OTA as your base before you flashed. I don't think I'm doing a very good job of phrasing my question, I apologize for that. Its just a hard question to put into words.
Sent from one of the many Anthropomorphic Personalities on the Disc
shangrila500 said:
No I get that, I was meaning are there any positive side effects from using the newest JB leak as your base ROM before flashing a new one. Like flashing the new JB leak via Odin, then unlocking and flashing a new ROM on top of it. Will there be any benefits like there were on the RAZR or when we flash in custom recoveries does it completely do away with the stock ROM that was on the system partition and replace it with whatever we flash? I know on the RAZR you would use the ROM you were on as a base you flash whatever else you wanted and there were benefits to having a certain OTA as your base before you flashed. I don't think I'm doing a very good job of phrasing my question, I apologize for that. Its just a hard question to put into words.
Sent from one of the many Anthropomorphic Personalities on the Disc
Click to expand...
Click to collapse
no not on samsung devices...the reason you needed to do that on the moto device is because of the locked bootloader. meaning you couldnt replace the kernel, so you had to ota to the latest, then root , recovery, and flash rom. since our device is fully unlocked, we dont have to worry about this. most if not all roms for d2vzw are packaged with a kernel. so it does not matter what current base your on, flashing a rom will overwrite it.
droidstyle said:
no not on samsung devices...the reason you needed to do that on the moto device is because of the locked bootloader. meaning you couldnt replace the kernel, so you had to ota to the latest, then root , recovery, and flash rom. since our device is fully unlocked, we dont have to worry about this. most if not all roms for d2vzw are packaged with a kernel. so it does not matter what current base your on, flashing a rom will overwrite it.
Click to expand...
Click to collapse
That's what I thought. I was just wanting a little clarification on that. Thanks man!!!
Sent from one of the many Anthropomorphic Personalities of the Disc
Related
Several months ago I purchased a NS4G on Craigslist. I wanted to use it as an iPod touch without the data. It came rooted with SuperUser. The phone keeps prompting me to OTA to 2.3.7 (it's currently on 2.3.5) I used Gingerbreak to unroot and it worked, SuperUser is now gone. However, ClockWorkMod Recovery is still present and 2.3.7 won't install. The phone reboots, goes to about 1/3 of the progress bar, and then fails. I just want to get the phone on completely stock 2.3.7, in preparation for the coming 4.0 OTA.
Hopefully the solution doesn't involve flashing a custom ROM, I've never done that before. Thanks!!
No need to get it OTA, you can just flash the stock ICS ROM found in the stickies of the development forum of this phone. Of course follow instructions closely.
Sent from my Nexus S using xda premium
But I'm selling it and need it to be completely 100% original and stock, which is what the buyer requested..
You want to use fastboot to flash a stock recovery. Peter Alfonso has them all listed on his site.
Thanks. I'm really not familiar with fastboot, and is there any way you could give me a link with instructions or the files I need? My build number is GRJ90.
And if there's anyway for me to avoid a rooted stock ROM, that'd be great. Just pure stock 2.3.7.
The stock image on Rom manager has the recovery bootloader included.
Flash a stock gb rom from cwm. You will find a list of them in either general or android development threads, not sure which. Completely stock, unrooted and as far as I remember the stock recovery is included. If not then the person will never know anyway as if someone doesn't want any non stock features then they won't know how to get to recovery anyway.
Actually I don't think they have stock recovery. Just flash the stock rom and then fastboot flash the stock recovery like was mentioned above. All you need to type is:
Fastboot flash recovery xxxxx.img
Xxxxx.img is the name of the image file you download.
Don't cheat the buyer...Tell him exactly what he's buying...And that you returned thedevice back to stock again.It's just not worth it.
I am currently on CleanRom 2.1 with the G7 radio. I'm looking to flash to CleanRom 2.5 and I want to start off with a G7 base.
I am planning on flashing back to stock using Adam Lange's linked rom here,
Can I flash using cwm (his instructions link to odin)?
I plan on the following
1) re-lock the bootloader
2) Boot to cwm and wipe/clear caches
3) flash the kernel he links to
4) flash the rom he links to
5) flash the G1 radio.
At that point I presume I am back in a condition to take the OTA.
I also see another set of back to stock instructions from droidstyle here. He has a different link to the stock rom (also odin instructions). I presume his method includes the kernel with the rom.
I've gotten by without odin to this point and would like to keep it that way (one less program / interface to deal with.)
It's been rebuilt already on the G7 base as of 9/25. Flash away.......
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
No those are odin packages. Also those are the F2 bases which was used when the phone was first sold. Follow droidstyles instructions as he explains it very easy. Short as i can be, lock the bootloader, shutdown and then start up in download mode, open odin and plug your phone into your computer, click on pda and browse to the stock file you downloaded and click start. Then do a factory wipe and do a update once you boot into your phone to upgrade to the current G7.
You are fine doing a OTA from the F2 base so flashing to a G1 modem do a OTA isnt needed
In short no you will have to use odin. You will not be able to use CWM to flash those img files
Sent from my SCH-I535 using xda app-developers app
annoyingduck said:
It's been rebuilt already on the G7 base as of 9/25. Flash away.......
Click to expand...
Click to collapse
Even though it isn't necessary, Scott and one other poster are making a case for getting the G7 base with the OTA before flashing. I would much rather just go from 2.1 to 2.5 without the hassle of going via the OTA.
If I skip the OTA, I'll just have to come to peace with that nagging ... "would my performance / battery life really be better if..."
x714x said:
No those are odin packages. Also those are the F2 bases which was used when the phone was first sold. Follow droidstyles instructions as he explains it very easy. Short as i can be, lock the bootloader, shutdown and then start up in download mode, open odin and plug your phone into your computer, click on pda and browse to the stock file you downloaded and click start. Then do a factory wipe and do a update once you boot into your phone to upgrade to the current G7.
You are fine doing a OTA from the F2 base so flashing to a G1 modem do a OTA isnt needed
In short no you will have to use odin. You will not be able to use CWM to flash those img files
Click to expand...
Click to collapse
Thanks for the confirmation on odin - I was afraid of that. I surprised someone hasn't made a stock image to use with cwm. And thanks for clarity on not having to go to the G1 modem.
Odin isnt hard at all to use and doesnt take all that long, roughly 8 mins for me. Do you have to use odin?, no. You can just flash a stock kernel then just use cwm to install 2.5. But the lastest G7 kernel isnt available to flash as i remember yet. I would recommend you odin to stock then take the ota, root, unlock, flash recovery, flash 2.5
Sent from my SCH-I535 using xda app-developers app
x714x said:
Odin isnt hard at all to use and doesnt take all that long, roughly 8 mins for me. Do you have to use odin?, no. You can just flash a stock kernel then just use cwm to install 2.5. But the lastest G7 kernel isnt available to flash as i remember yet. I would recommend you odin to stock then take the ota, root, unlock, flash recovery, flash 2.5
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
That is my plan. The time consuming part is just downloading all the components (slow connection) and getting familiar with Odin. But that is just a one time thing. I've managed to avoid it this far... but now I am familiar enough with all the steps that it's no big deal. I might even have to stop calling myself a noob.
x714x said:
Odin isnt hard at all to use and doesnt take all that long, roughly 8 mins for me. Do you have to use odin?, no. You can just flash a stock kernel then just use cwm to install 2.5. But the lastest G7 kernel isnt available to flash as i remember yet. I would recommend you odin to stock then take the ota, root, unlock, flash recovery, flash 2.5
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
This!
Hello there.
I am running a stock, rooted, most recent TW 4.1.2. I had TWRP recovery and from what I remember, unlocked the bootloader.
After trying difference ROMS both TW and AOSP based, I decided that I would stick with the stock ROM, but rooted to add functionality, especially WIFI tethering.
I would like to get to Stock Rooted 4.3 TW so that I can (hopefully) use tethering. I attempted to take the OTA after flashing a stock recovery image, but the install failed.
I have several questions I hope the members here can assist me with:
1. Do you have to lock the bootloader prior to taking the OTA? I do realize that there is no way to unlock the bootloader on 4.3 as of the moment.
2. Is there a consensus that it is possible to root after taking the OTA via Safe Strap? I have been doing some reading on the forums, and some members indicate that it has worked for them.
3. Has anybody been able to get tethering to work after taking the OTA and rooting?
Thanks in advance! Happy holidays...
banditsw said:
Hello there.
I am running a stock, rooted, most recent TW 4.1.2. I had TWRP recovery and from what I remember, unlocked the bootloader.
After trying difference ROMS both TW and AOSP based, I decided that I would stick with the stock ROM, but rooted to add functionality, especially WIFI tethering.
I would like to get to Stock Rooted 4.3 TW so that I can (hopefully) use tethering. I attempted to take the OTA after flashing a stock recovery image, but the install failed.
I have several questions I hope the members here can assist me with:
1. Do you have to lock the bootloader prior to taking the OTA? I do realize that there is no way to unlock the bootloader on 4.3 as of the moment.
2. Is there a consensus that it is possible to root after taking the OTA via Safe Strap? I have been doing some reading on the forums, and some members indicate that it has worked for them.
3. Has anybody been able to get tethering to work after taking the OTA and rooting?
Thanks in advance! Happy holidays...
Click to expand...
Click to collapse
Lock the bootloader using ez lock 1.2
Best bet is a clean Odin flash and use this NO WIPE file MB1 image #1 http://forum.xda-developers.com/showthread.php?t=1974114 then do system update to MF1 and then again for 4.3
Saferoot works (I'm currently using it without any issues) http://forum.xda-developers.com/showthread.php?t=2565758
I'm on share everything plan so tethering is included
But just remember, if you do OTA the 4.3 your phone will be locked down with NO chance of ever installing a custom recovery or unlocking the bootloader and no more custom ROMs
Hope this helps
yepyep14u2know said:
Lock the bootloader using ez lock 1.2
Best bet is a clean Odin flash and use this NO WIPE file MB1 image #1 http://forum.xda-developers.com/showthread.php?t=1974114 then do system update to MF1 and then again for 4.3
Saferoot works (I'm currently using it without any issues) http://forum.xda-developers.com/showthread.php?t=2565758
I'm on share everything plan so tethering is included
But just remember, if you do OTA the 4.3 your phone will be locked down with NO chance of ever installing a custom recovery or unlocking the bootloader and no more custom ROMs
Hope this helps
Click to expand...
Click to collapse
Thanks for the reply. I tried to take the OTA update after flashing the stock recovery via EZ-Recovery app, and locking the bootloader via EZ-lock 1.2 per your advice, but the install failed. Did you ODIN back to stock?
I guess I will ODIN flash the image you reference, and do the OTA update that way. I used to flash all sorts of ROMS, but at this point, I just want a fully functioning rom. The developers do amazing work, that being said.
Thanks again.
banditsw said:
Thanks for the reply. I tried to take the OTA update after flashing the stock recovery via EZ-Recovery app, and locking the bootloader via EZ-lock 1.2 per your advice, but the install failed. Did you ODIN back to stock?
I guess I will ODIN flash the image you reference, and do the OTA update that way. I used to flash all sorts of ROMS, but at this point, I just want a fully functioning rom. The developers do amazing work, that being said.
Thanks again.
Click to expand...
Click to collapse
Yeah I had the same problems you're encountering. Those are the steps I took, so just follow those steps and ODIN MB1 no wipe, then system update to MF1 and then system update again to ML1, and you'll keep all your settings, contacts, apps, etc.
banditsw said:
Thanks for the reply. I tried to take the OTA update after flashing the stock recovery via EZ-Recovery app, and locking the bootloader via EZ-lock 1.2 per your advice, but the install failed. Did you ODIN back to stock?
I guess I will ODIN flash the image you reference, and do the OTA update that way. I used to flash all sorts of ROMS, but at this point, I just want a fully functioning rom. The developers do amazing work, that being said.
Thanks again.
Click to expand...
Click to collapse
Just be warned, that once you take the 4.3 OTA, you cannot ever, never go back or flash custom ROMs. you are stuck there.
DigitalMD said:
Just be warned, that once you take the 4.3 OTA, you cannot ever, never go back or flash custom ROMs. you are stuck there.
Click to expand...
Click to collapse
You can't say that for sure. All you can say that there is a 99.999999999% chance that you will never be able to unlock your bootloader again.
Running a custom ROM/recovery would be attainable with a locked bootloader with something like safestrap.
DigitalMD said:
Just be warned, that once you take the 4.3 OTA, you cannot ever, never go back or flash custom ROMs. you are stuck there.
Click to expand...
Click to collapse
I appreciate that fact. Maybe it will be a good thing, because I was a flashaholic. Maybe it will force me to do other things other than flash ROMS LOL.
banditsw said:
I appreciate that fact. Maybe it will be a good thing, because I was a flashaholic. Maybe it will force me to do other things other than flash ROMS LOL.
Click to expand...
Click to collapse
Well don't even try after the update or else you will be like me with a hopefully temporary bricked phone.
yepyep14u2know said:
Lock the bootloader using ez lock 1.2
Best bet is a clean Odin flash and use this NO WIPE file MB1 image #1 http://forum.xda-developers.com/showthread.php?t=1974114 then do system update to MF1 and then again for 4.3
Saferoot works (I'm currently using it without any issues) http://forum.xda-developers.com/showthread.php?t=2565758
I'm on share everything plan so tethering is included
But just remember, if you do OTA the 4.3 your phone will be locked down with NO chance of ever installing a custom recovery or unlocking the bootloader and no more custom ROMs
Hope this helps
Click to expand...
Click to collapse
I have tried downloading the MB1 image since this morning....having problems with downloading it...anyone have the file to download? Thanks.
EDIT: I guess the server had issues yesterday. Was able to download last night.
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.