For those who haven't rooted and have received the new OTA or updated manually via LG Bridge, have you seen or read of any changes from the update? Of course, other than them patching out the Dirty Santa exploit we've used for root. Speaking of which... (sidebar) manufacturer pushing out exploit patches shortly after root being achieved on a device sounds very Note7-nostalgic to me.
So far root has been a disaster for non devs. Bricks and other problems with stuff not working. I wouldn't root this phone yet, it is not like a Samsung where you can just easily fix everything with Odin. That said, I will not accept an OTA update if all it does is patch the root method. They had better have some useful things like camera focusing faster, battery lasting more than 3 hours, etc. for me to update.
Root is fine and everything world perfect. At least for h918.
hotstocks said:
So far root has been a disaster for non devs. Bricks and other problems with stuff not working. I wouldn't root this phone yet, it is not like a Samsung where you can just easily fix everything with Odin. That said, I will not accept an OTA update if all it does is patch the root method. They had better have some useful things like camera focusing faster, battery lasting more than 3 hours, etc. for me to update.
Click to expand...
Click to collapse
Quite honestly I've only seen a couple of people who have hard bricked their devices - mainly just either one who used the dirtysanta on a phone that was not listed as compatible and the dev of dirtysanta when testing out reverting back to stock per request by users.
Rooting/Unlocking this phone has significantly increased battery and performance especially after installing Tilde88's ROM. Sure for the others who have variants outside of T-Mobile (like me), we have the static boot screen, but considering how minimal the impact is - it's well worth it. To each their own, but I would not say rooting is a disaster for this phone.
Nougat is still really new. Only a handful of phones support it. Hell, if you look at the Pixel forums, I've seen many more bricks there than over here.
twistedvip said:
Quite honestly I've only seen a couple of people who have hard bricked their devices - mainly just either one who used the dirtysanta on a phone that was not listed as compatible and the dev of dirtysanta when testing out reverting back to stock per request by users.
Rooting/Unlocking this phone has significantly increased battery and performance especially after installing Tilde88's ROM. Sure for the others who have variants outside of T-Mobile (like me), we have the static boot screen, but considering how minimal the impact is - it's well worth it. To each their own, but I would not say rooting is a disaster for this phone.
Nougat is still really new. Only a handful of phones support it. Hell, if you look at the Pixel forums, I've seen many more bricks there than over here.
Click to expand...
Click to collapse
I agree with @twistedvip. Definitely not a disaster. I am on @OvrDriVE 's ROM coming from stock rooted h918 and the phone is definitely faster with better battery life. Everything works. Couldn't be happier.
twistedvip said:
Quite honestly I've only seen a couple of people who have hard bricked their devices - mainly just either one who used the dirtysanta on a phone that was not listed as compatible and the dev of dirtysanta when testing out reverting back to stock per request by users.
Rooting/Unlocking this phone has significantly increased battery and performance especially after installing Tilde88's ROM. Sure for the others who have variants outside of T-Mobile (like me), we have the static boot screen, but considering how minimal the impact is - it's well worth it. To each their own, but I would not say rooting is a disaster for this phone.
Nougat is still really new. Only a handful of phones support it. Hell, if you look at the Pixel forums, I've seen many more bricks there than over here.
Click to expand...
Click to collapse
I do have a T-mobile. Is Tilde88's ROM a stock rom with just some tweaks or not Noughat? Also is there a program like Odin that you can flash back to non-rooted whenever you want? Say I want to play PokemonGo, well you can't if rooted. So with Samsung phones you just have supersu unroot, play, and then odin flash root back. It literally takes 1 minutes and nothing ever goes wrong. Is there a program like Odin to do that? If not, then LG phones really aren't ready to be rooted and unrooted to use Android Pay, PokemonGo, and all the other software that you can't use when rooted. And don't get me wrong, I have had and rooted every Samsung phone since the S3. But this is my first LG, and I just don't see an easy way to do things like via Odin. Hell even if you brick a Samsung you can usually just Odin flash stock rom and be back to new. How do you do this with LG?
Unfortunately LG doesn't provide as powerful of a tool as Odin is. They have LG bridge and Uppercut (I believe those are the two names) where you can flash TOTs and KDZ files to be able to restore back to stock completely and flash updates. I believe currently we dont have any way to flash TOT files though and thus are stuck. But for T-Mobile users, you should be able to simply relock your phone and go right back to stock very easily.
As for switching back between root and stock - using this dualboot-patcher you might be able to do what you're looking to do. Just know the root method used is dependent upon the dirtycow exploit. T-Mobiles 10i update has the Dec 5 security update which fixed that exploit. I don't know much about the dualbooting though so it may not be what you're looking for after all.
Too bad lg bridge keeps returning unable to download update error.
Sent from my LG-H918 using XDA Premium HD app
It worked for me but it took forever. Also it failed mid way and I had to pull out the battery, disconnect and reconnect the phone but then it updating without any problems.
The only thing I noticed so far is that it brings the Android security patch up to December 1st, so it's not completely useless.
hotstocks said:
I do have a T-mobile. Is Tilde88's ROM a stock rom with just some tweaks or not Noughat? Also is there a program like Odin that you can flash back to non-rooted whenever you want? Say I want to play PokemonGo, well you can't if rooted. So with Samsung phones you just have supersu unroot, play, and then odin flash root back. It literally takes 1 minutes and nothing ever goes wrong. Is there a program like Odin to do that? If not, then LG phones really aren't ready to be rooted and unrooted to use Android Pay, PokemonGo, and all the other software that you can't use when rooted. And don't get me wrong, I have had and rooted every Samsung phone since the S3. But this is my first LG, and I just don't see an easy way to do things like via Odin. Hell even if you brick a Samsung you can usually just Odin flash stock rom and be back to new. How do you do this with LG?
Click to expand...
Click to collapse
First off, if you don't know about something, you should probably keep your opinions to your self. It took me the ability to read, and twenty minutes to unlock the bootloader and root my LG-H918 (T-Mobile) then when I had to take it back I flashed the stock odexed rom, unrooted, and locked the bootloader in about 20 minutes as well... I'm no developer, but I'm smart enough to read instructions, comprehend them, and follow them to get a desired result... And if you can recover from a brick... Ever, then you aren't hard bricked. Hard bricked means your device is dead, and unrecognizable by any means, or unrecoverable. You are referring to a soft brick. Please learn what you are talking about before posting.
"sometimes it is better to keep one's mouth shut and be thought a fool, than to open it and remove all doubt"
Sent from my LG-H918 using Tapatalk
ZDeuce2 said:
First off, if you don't know about something, you should probably keep your opinions to your self. It took me the ability to read, and twenty minutes to unlock the bootloader and root my LG-H918 (T-Mobile) then when I had to take it back I flashed the stock odexed rom, unrooted, and locked the bootloader in about 20 minutes as well... I'm no developer, but I'm smart enough to read instructions, comprehend them, and follow them to get a desired result... And if you can recover from a brick... Ever, then you aren't hard bricked. Hard bricked means your device is dead, and unrecognizable by any means, or unrecoverable. You are referring to a soft brick. Please learn what you are talking about before posting.
"sometimes it is better to keep one's mouth shut and be thought a fool, than to open it and remove all doubt"
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
Think what you want, but I am also not a dev, but a techie guy. To me it is irrelevant if you have a soft brick if you don't have the tools and knowledge to recover it, which 99.99% of LG V20 users DON'T HAVE. So your soft bricked LG V20 might as well be a hard brick. My point is that 90% of regular Joes can use Odin and recover easily from a soft brick, on the LG V20, NOT SO MUCH. If you think finding LG's cryptic flashing software, learning ADB, and whatever else is needed is something that most users can do, you are greatly mistaken. Sure, one day there might be freely available, easy to use LG V20 flashing software similiar to Odin, but right now there isn't yet. I've rooted and flashed HTCs and Samsungs never with issues, but this LG is a far more complicated beast. I am not saying it can't be done, I am saying that most people can't do it or recover if there is a mistake. Just sayin don't mess with it if you are a newb yet, until there is more mature flashing software.
ZDeuce2 said:
when I had to take it back I flashed the stock odexed rom, unrooted, and locked the bootloader in about 20 minutes as well...
Click to expand...
Click to collapse
what are your steps to return to stock?
Flash stock odexed rom using TWRP
Unrooted - is this a step?
Did you have to flash stock recovery before locking the bootloader?
MidtownHD said:
what are your steps to return to stock?
Flash stock odexed rom using TWRP
Unrooted - is this a step?
Did you have to flash stock recovery before locking the bootloader?
Click to expand...
Click to collapse
I think they took that update out coz everyone is having trouble updating.
I really want to update, there's many bugs right now but I don't want to lose my root
hotstocks said:
Think what you want, but I am also not a dev, but a techie guy. To me it is irrelevant if you have a soft brick if you don't have the tools and knowledge to recover it, which 99.99% of LG V20 users DON'T HAVE. So your soft bricked LG V20 might as well be a hard brick. My point is that 90% of regular Joes can use Odin and recover easily from a soft brick, on the LG V20, NOT SO MUCH. If you think finding LG's cryptic flashing software, learning ADB, and whatever else is needed is something that most users can do, you are greatly mistaken. Sure, one day there might be freely available, easy to use LG V20 flashing software similiar to Odin, but right now there isn't yet. I've rooted and flashed HTCs and Samsungs never with issues, but this LG is a far more complicated beast. I am not saying it can't be done, I am saying that most people can't do it or recover if there is a mistake. Just sayin don't mess with it if you are a newb yet, until there is more mature flashing software.
Click to expand...
Click to collapse
Speak for yourself, you are definitely in the minority, most of us know how to do these things or we wouldn't be here doing them... And I could care less if you want to call it a pb&j, it's still a soft brick...
Sent from my LG-H918 using Tapatalk
---------- Post added at 03:12 PM ---------- Previous post was at 03:07 PM ----------
MidtownHD said:
what are your steps to return to stock?
Flash stock odexed rom using TWRP
Unrooted - is this a step?
Did you have to flash stock recovery before locking the bootloader?
Click to expand...
Click to collapse
Remove root in SuperSU app. And I did not change recovery, just relocked the bootloader
Sent from my LG-H918 using Tapatalk
---------- Post added at 03:14 PM ---------- Previous post was at 03:12 PM ----------
wing_addict_usa said:
I really want to update, there's many bugs right now but I don't want to lose my root
Click to expand...
Click to collapse
NATF's latest rom is the update... On LGH918
Sent from my LG-H918 using Tapatalk
ZDeuce2 said:
Remove root in SuperSU app. And I did not change recovery, just relocked the bootloader
Click to expand...
Click to collapse
What happens after you re-lock the bootloader? does it work well with TWRP installed? or does it replace it automatically with the stock one? and everything becomes "stock"?
MidtownHD said:
What happens after you re-lock the bootloader? does it work well with TWRP installed? or does it replace it automatically with the stock one? and everything becomes "stock"?
Click to expand...
Click to collapse
Honestly, I went back as stock as possible to see if it fixed my speaker distortion problem, (it did not) but just left it that way and locked it before I returned it just so the can't be check for corruption screen didn't appear, it still worked fine, but I never checked whether the stock bootloader overwrote twrp. The corruption screen went away which is what I was trying for.
Sent from my LG-H918 using Tapatalk
Has anyone been able to capture the URL or the zip for the update?
MidtownHD said:
what are your steps to return to stock?
Flash stock odexed rom using TWRP
Unrooted - is this a step?
Did you have to flash stock recovery before locking the bootloader?
Click to expand...
Click to collapse
So if I may join in I flashed a back up and I can't get into my device is there a tool I can't get into recovery for some reason
Sent from my Nexus 6P using Tapatalk
ZDeuce2 said:
Speak for yourself, you are definitely in the minority, most of us know how to do these things or we wouldn't be here doing them... And I could care less if you want to call it a pb&j, it's still a soft brick...
Sent from my LG-H918 using Tapatalk
---------- Post added at 03:12 PM ---------- Previous post was at 03:07 PM ----------
Remove root in SuperSU app. And I did not change recovery, just relocked the bootloader
Sent from my LG-H918 using Tapatalk
---------- Post added at 03:14 PM ---------- Previous post was at 03:12 PM ----------
NATF's latest rom is the update... On LGH918
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
This says M https://forum.xda-developers.com/v20/development/rom-natf-1-00-test-5-debloated-stock-t3509750
Related
Okay... now that I have everyone's attention...
Here is the deal... in between a series of insane work trips my Mom comes over and says she just bought a new One X, and can I set it up for her.
I am pretty comfortable with this stuff, or at least following directions , but I am seriously pressed for time.
I started reading last night and think I have a pretty good handle on what and where, but want to confirm I am on the right path...
Phone is currently on 4.0.3 with version 1.85.502.3
I have zero plans to load custom ROMs on this since all my Mom needs is stability, but I want to root so that I can get in TiBu, clean out the bloat, setup a backup schedule and so on.
I have read a couple of comments that the 2.2 software gives better battery life and a few other improvements, so would not mind putting that on.
I have not gotten any OTA update notifications since I turned the phone on.
What is my best path?
Can I simply root the device using these instructions http://briefmobile.com/how-to-root-htc-one-x-att and then install the rooted stock 2.2 here http://forum.xda-developers.com/showthread.php?t=1812459
Sorry for the dummy questions, but I am leaving for another work trip tomorrow AM and was hoping to get this done, although to be perfectly honest it is not as if she wont have a working phone, but if I can do this all up front then I can let her play around with it, customize etc and not have to redo it all when I get back.
THANKS for your help!
post pics and I'll help.
bloodrain954 said:
post pics and I'll help.
Click to expand...
Click to collapse
Of my mom? classy!
Did you copy paste the title from brazzers.com clips?
Sent from my One X using xda premium
I would defo flash CleanROM 4.5 stand for her.
lazarat said:
Did you copy paste the title from brazzers.com clips?
Sent from my One X using xda premium
Click to expand...
Click to collapse
I guess I should have known better... felt bad posting noobish questions I can figure out if I spend a bunch of time reading, but really short on time right now, so figured I would try to be funny and hopefully generate more views and quicker responses.
For what it is worth my Mom is 67... I am not 17 and this is not a MILF scenario...
thcue said:
I would defo flash CleanROM 4.5 stand for her.
Click to expand...
Click to collapse
Right... I don't want to flash custom... stick with stock... I have no time to update customs or to act as tech support when things inevitably go wrong with a custom.
dcdivenut said:
Right... I don't want to flash custom... stick with stock... I have no time to update customs or to act as tech support when things inevitably go wrong with a custom.
Click to expand...
Click to collapse
Believe me man you would want to how much bloat and crap that att throws on the phone. Might as well give her something worth having the rom is very stable and would never have to fix it for her.
Also after you install TWRP for her (the recovery) Make sure to make a nano backup of her stock image then flash with CleanROM and make one of that to. So if she ever has a issue she is just one click away from a new phone.:good:
dcdivenut said:
Right... I don't want to flash custom... stick with stock... I have no time to update customs or to act as tech support when things inevitably go wrong with a custom.
Click to expand...
Click to collapse
I think the problem is that if you're going to root anyway, you've already made it so she can't stay current on the "official" path.
I've found CleanROM to be far more stable than AT&T's PoS.
dcdivenut said:
Of my mom? classy!
Click to expand...
Click to collapse
just replying as per title
bloodrain954 said:
post pics and I'll help.
Click to expand...
Click to collapse
Lmao!!
Sent from my One X using xda app-developers app
I must.. refrain from Googling sexy old ladies and relying to the tread must resist the urge.... :angel:
dcdivenut said:
this is not a MILF scenario...
Click to expand...
Click to collapse
Dont make it then
Sent from my One X using xda premium
thebobmannh said:
I think the problem is that if you're going to root anyway, you've already made it so she can't stay current on the "official" path.
I've found CleanROM to be far more stable than AT&T's PoS.
Click to expand...
Click to collapse
+1000.
You'll never know it isn't stock sense/att except that all the apps which, if she clicks them she'll get charged additional usage for, are gone.
FWIW, ATT's OTA isn't anything special. My phone was three months old and was still running 1.73. Never succeeded in an OTA update.
So, CleanROM 4.5 was a huge improvement.
I would say that, if she is not totally interested in Modding, that she should either leave it with all stock ,or switch to CleanROM. I am running CleanROM because I like the stock feel, although I have modded a few things. I also liked the removale of bloatware. I feel that the best place for rooting your One X is on onexroot.com. just make sure you choose the right ROM and root method depending on your model, such as international AT&T, or Rodgers. Hope this helps!
dcdivenut said:
Okay... now that I have everyone's attention...
Here is the deal... in between a series of insane work trips my Mom comes over and says she just bought a new One X, and can I set it up for her.
I am pretty comfortable with this stuff, or at least following directions , but I am seriously pressed for time.
I started reading last night and think I have a pretty good handle on what and where, but want to confirm I am on the right path...
Phone is currently on 4.0.3 with version 1.85.502.3
I have zero plans to load custom ROMs on this since all my Mom needs is stability, but I want to root so that I can get in TiBu, clean out the bloat, setup a backup schedule and so on.
I have read a couple of comments that the 2.2 software gives better battery life and a few other improvements, so would not mind putting that on.
I have not gotten any OTA update notifications since I turned the phone on.
What is my best path?
Can I simply root the device using these instructions http://briefmobile.com/how-to-root-htc-one-x-att and then install the rooted stock 2.2 here http://forum.xda-developers.com/showthread.php?t=1812459
Sorry for the dummy questions, but I am leaving for another work trip tomorrow AM and was hoping to get this done, although to be perfectly honest it is not as if she wont have a working phone, but if I can do this all up front then I can let her play around with it, customize etc and not have to redo it all when I get back.
THANKS for your help!
Click to expand...
Click to collapse
2.20 breaks root if you go with the stock RUU. So you are going to be unlocking the bootloader and going off the "official" path anyway. Which means you will have to periodically update your mother's phone anyways and she will software warranty.
I would go with one of three options:
1. Root/Unlock and flash CleanROM 4.5 (you will have to update her phone every so often and she loses software warranty)
2. Root, stay with 1.85 and de-bloat (don't really recommended because of multitask issue)
3. Don't root, leave phone stock and stay on the official path (if you don't have the time to maintain your mother's phone go with this)
Actually, if you root &unlock bootloader now, flash a custom recovery, you can manually update the firmware to 2.2x, flash back your stock recovery and relock it you have a fully updated, stock device that you can always go back and unlock if u want to later.
Sent from my SPH-L710 using xda premium
Butters619 said:
2.20 breaks root if you go with the stock RUU. So you are going to be unlocking the bootloader and going off the "official" path anyway. Which means you will have to periodically update your mother's phone anyways and she will software warranty.
I would go with one of three options:
1. Root/Unlock and flash CleanROM 4.5 (you will have to update her phone every so often and she loses software warranty)
2. Root, stay with 1.85 and de-bloat (don't really recommended because of multitask issue)
3. Don't root, leave phone stock and stay on the official path (if you don't have the time to maintain your mother's phone go with this)
Click to expand...
Click to collapse
True that for root on 2.20, you will need to unlock the bootloader anyway, so you may as well go ahead and root, SuperCID and unlock bootloader.
A 4th option would be to flash a stock rooted 2.20, 2.23, or 2.29 ROM (after unlocking the bootloader). Honestly, the 2.2X stock ROMs are quite good, and you won't really need to update the phone much after that; really mostly if you just want to.
Personally, I would suggest either leaving as-is on 1.85, and root and debloat; or unlock the bootloader and flash either a rooted stock 2.2X ROM, or custom ROM that does not divert too much from stock 2.2X (like CleanROM).
Updating to 2.20 the "official" way is just robbing yourself of any other options, until (if and when) a root method is found for 2.20. Personally recommend you stay away from that.
---------- Post added at 03:59 PM ---------- Previous post was at 03:48 PM ----------
dcdivenut said:
I have zero plans to load custom ROMs on this since all my Mom needs is stability,
Click to expand...
Click to collapse
Custom ROMs have a huge variation in their stability. Sure, ROMs which are AOSP have some things broken, and ones based on the leading edge (Jellybean) have issues too, since they are ports, do not fully support our hardware, etc.
But many of the ROMs you will see in Development are based stock ROMs, with bloat removed, performance tweaks, and some features added, without any real drastic changes. CleanROM, King Cobra among others actually run smoother and more stable than stock. Don't knock all custom ROMs, especially since you haven't even tried any on this device.
CleanROM 4.5 is better than stock. It's the best rom I have ever flashed on any device ever.
So I had a Galaxy S1 Captivate for about 2 year and my wife has a Fascinate and I rooted/flashed them both like it was my job for the last couple years. I never once hard bricked either and for the most part knew what I was doing. I have a couple home made jigs so DL mode or (soft bricks) were never an issue. My question to you guys is I'm trying to gauge how difficult/risky is it to root and rom the GS3 (Verizon model specifically). The reason I'm wondering this info is because I personally don't own my GS3, it is property of my company and I don't want to chance bricking or not being able to easily flash back to stock unless it has gotten easier or less risky since the original Galaxy lineup. I mean if you had 2.3 bootloaders on your GS1 and you had access to a jig, there was pretty much a 0% chance of hard bricking unless you do something really stupid. Sorry for rambling on!
jayjr1105 said:
So I had a Galaxy S1 Captivate for about 2 year and my wife has a Fascinate and I rooted/flashed them both like it was my job for the last couple years. I never once hard bricked either and for the most part knew what I was doing. I have a couple home made jigs so DL mode or (soft bricks) were never an issue. My question to you guys is I'm trying to gauge how difficult/risky is it to root and rom the GS3 (Verizon model specifically). The reason I'm wondering this info is because I personally don't own my GS3, it is property of my company and I don't want to chance bricking or not being able to easily flash back to stock unless it has gotten easier or less risky since the original Galaxy lineup. I mean if you had 2.3 bootloaders on your GS1 and you had access to a jig, there was pretty much a 0% chance of hard bricking unless you do something really stupid. Sorry for rambling on!
Click to expand...
Click to collapse
I came from the Fascinate and this phone is just as easy to flash. Just make sure you read the OP and only flash things made for the US versions and you'll be fine. If something gets hosed, you can always odin back. Here is a great guide to get you started.
http://forum.xda-developers.com/showthread.php?t=1762709
Sent from my SCH-I535 using xda app-developers app
Deliquified said:
I came from the Fascinate and this phone is just as easy to flash. Just make sure you read the OP and only flash things made for the US versions and you'll be fine. If something gets hosed, you can always odin back. Here is a great guide to get you started.
http://forum.xda-developers.com/showthread.php?t=1762709
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I haven't checked that link out yet but how easy is it to go back to the Verizon stock ROM if need be?
Does the ROM procedure go something like this?...
Power Off, DL mode with jig, ODIN a CWM or Kernel package with CWM, mount SD, drag and drop ROM, Flash, win?
well...
well the good news is that you don't have to flash a custom rom for root. I just rooted and unlocked my phone while still running the stock rom. =) i'd post my tutorial but I'm a new member and I have 8 more posts to do before I can post in development.
eorly420 said:
well the good news is that you don't have to flash a custom rom for root. I just rooted and unlocked my phone while still running the stock rom. =) i'd post my tutorial but I'm a new member and I have 8 more posts to do before I can post in development.
Click to expand...
Click to collapse
There is already an in depth tutorial for that as well as one for those who have the recent OTA.
http://forum.xda-developers.com/showthread.php?t=2046439
The above link is those with the jelly bean OTA.
http://forum.xda-developers.com/showthread.php?t=1762709
This above is the in depth guide I was talking about. It was posted on 7/10/12. So there is no need for another tutorial unless you found a new way to do it. If you are talking about RootDebugFS then there is a tutorial for that here as well as the SuperSU version here as well.
I also came from a fascinate which was super easy to flash. As long as you read up on your homework this phone is cake to flash.
You shouldn't have many problems. If you need help, PM me. I'm glad to help.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
So I'm wondering one last thing. I hear about a "flash counter" on the GS3... anything I need to be really careful about to not trip this "counter"? Will Verizon void the warranty if tripped?
Thanks again guys!
Also, I'm going to be using this phone a lot for work and I ported my old personal number to Google Voice so this will be my personal phone as well, so I need the phone to be pretty solid and stable, should I be looking to flash Original ROMs or from the regular development section?
jayjr1105 said:
So I'm wondering one last thing. I hear about a "flash counter" on the GS3... anything I need to be really careful about to not trip this "counter"? Will Verizon void the warranty if tripped?
Thanks again guys!
Also, I'm going to be using this phone a lot for work and I ported my old personal number to Google Voice so this will be my personal phone as well, so I need the phone to be pretty solid and stable, should I be looking to flash Original ROMs or from the regular development section?
Click to expand...
Click to collapse
Once your rooted, you can download Triangle Away from the App Store and that will restore the counter to 0.
lvgdgts said:
Once your rooted, you can download Triangle Away from the App Store and that will restore the counter to 0.
Click to expand...
Click to collapse
Thanks! Do you need to run the app every time you flash or just right before you would need to take it in to Verizon for warranty/service?
jayjr1105 said:
Thanks! Do you need to run the app every time you flash or just right before you would need to take it in to Verizon for warranty/service?
Click to expand...
Click to collapse
If you unlock bootloader before you flash recovery you will not trip flash counter. If counter is tripped must use Triangle Away while still on stock rom. That being said flash counter does not affect anything except warranty and requires you to Odin stock root, run triangle Away then Odin full stock so best to fix as soon as you root and unlock to avoid extra work at time of return to Verizon.
prdog1 said:
If you unlock bootloader before you flash recovery you will not trip flash counter. If counter is tripped must use Triangle Away while still on stock rom. That being said flash counter does not affect anything except warranty and requires you to Odin stock root, run triangle Away then Odin full stock so best to fix as soon as you root and unlock to avoid extra work at time of return to Verizon.
Click to expand...
Click to collapse
Is there a way to just see if you tripped the flash counter without Triangle Away?
Ok, so I finally got my replacement phone from Verizon after the last one's power IC crashed. Anyway, I'm eager to get it back to normal. I first unlocked, rooted, and flashed CM 10.1 within recovery with this thread: http://forum.xda-developers.com/showthread.php?t=2046439 For some reason, I didn't see the "Disable recovery flash" when I rebooted to the system. Anyway, CM10.1 boot looped. Re-flashing from recovery didn't work, so I followed this thread: http://forum.xda-developers.com/showthread.php?t=1840030 I struggled with that, but I finally managed to get to the last step where it flashes "stock.vzw_root66.tar" That failed for whatever reason, so I couldn't move on. Then I did a whole bunch of things, so I can't really remember. I think one point I might have actually flashed something in the bootloader part of ODIN when it was supposed to be in the PDA part (that didn't really seem to have an affect on anything after that though for whatever reason). My phone had VRBMB1 and 4.12 when I first got the device and I didn't accept the latest OTA update. I try flashing a bootloader and then a recovery image like this: http://rootzwiki.com/topic/29256-tutorial-rootrecoverybootloader-unlockicsjb-verizon-galaxy-s-iii/ and this http://www.w0lfdroid.com/2013/04/how-to-lockunlock-bootloader-for.html but the dumb "System software not autorized by Verizon Wireless has been found on your phone" keeps popping up whenever I go into recovery (I flash CWM). I can go into ODIN and flash stuff, but I'm currently blocked by that Verizon message. In the end, I would like an unlocked bootloader, with root, and CM 10.1. From there I can TB to my old device. Any help would be greatly appreciated. Thank you!
LOL
Ya Im wondering if your screwed or if your phone got verizon analed ?????
He can't even remember what he did to the phone and you are wondering if Verizon screwed him???
Just ODIN back to OEM ROM stock unrooted and start over and be sure to follow root and unlock steps precisely.
Make sure you are following a thread which matches the OEM version you are using.
You may need to follow a " return to stock unrooted" thread.
Thanks for your reply. Could you give me a thread that could take me through that experience? Also, what does OEM version mean? Thanks again.
OEM means Original Equipment Manufacturer, aka whatever comes with said item unmodified. In this case, stock, unrooted, locked firmware.
http://forum.xda-developers.com/showthread.php?t=2334876
Pm this guy. He has the latest firmware in Odin (PDA slot only for clarification) flashable format.
Flash that, and you'll be stock. If you want to unlock and flash again, I'll find you the guide and break it down for you when I get home. However I'd advise you to do some more reading before you go crack flashing again in the hopes of saving you headaches and prolonging your devices' longevity.
Sent from my SCH-I605 using xda app-developers app
---------- Post added 11th July 2013 at 12:05 AM ---------- Previous post was 10th July 2013 at 11:19 PM ----------
zerofighter1 said:
OEM means Original Equipment Manufacturer, aka whatever comes with said item unmodified. In this case, stock, unrooted, locked firmware.
http://forum.xda-developers.com/showthread.php?t=2334876
Pm this guy. He has the latest firmware in Odin (PDA slot only for clarification) flashable format.
Flash that, and you'll be stock. If you want to unlock and flash again, I'll find you the guide and break it down for you when I get home. However I'd advise you to do some more reading before you go crack flashing again in the hopes of saving you headaches and prolonging your devices' longevity.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1974114
This guide should get you back to rooted/unlocked/recovery. If you have any questions, post them here and I'll do what I can to guide you through the process. Good luck.
I managed to get back to stock. From there I unlocked and rooted. After that, I try to flash Cyanogenmod CM 10.1.1 from recovery, but it bootloops again. I'm not sure what is causes that bootloop. Thanks.
Dillon610 said:
I managed to get back to stock. From there I unlocked and rooted. After that, I try to flash Cyanogenmod CM 10.1.1 from recovery, but it bootloops again. I'm not sure what is causes that bootloop. Thanks.
Click to expand...
Click to collapse
Are you wiping data?
I just did before you said that. I *finally* (after countless hours) have everything the way I want it. Thank you so much everybody for the help!
Ok, yesterday morning my MAXX received the KitKat update. Brainlessly, I clicked upgrade. This put me into the oh so famous bootloop.
During one of the boot loops, I managed to unroot with Voodoo.
Then in fastboot, I had the brilliant (aka, incredibly stupid) idea of flashing an old recovery. I had thought it was the one from 4.2.2 but sadly, it was from the previous version.
This had the appearance of working as it then booted to KitKat upgrade, which after a couple minutes failed.
Now I'm completely stuck in fastboot mode. I can't flash the 4.2.2 recovery. I haven't tried anything else. FXZ back to 12.15.15 doesn't work. Gives the GPT failure.
So...my belief, based only on googling around, is that I need to wait for the FXZ for KitKat. Does that sound right?
Any other ideas?
Thank you in advance!!!!!!!!!!
killboredom said:
Ok, yesterday morning my MAXX received the KitKat update. Brainlessly, I clicked upgrade. This put me into the oh so famous bootloop.
During one of the boot loops, I managed to unroot with Voodoo.
Then in fastboot, I had the brilliant (aka, incredibly stupid) idea of flashing an old recovery. I had thought it was the one from 4.2.2 but sadly, it was from the previous version.
This had the appearance of working as it then booted to KitKat upgrade, which after a couple minutes failed.
Now I'm completely stuck in fastboot mode. I can't flash the 4.2.2 recovery. I haven't tried anything else. FXZ back to 12.15.15 doesn't work. Gives the GPT failure.
So...my belief, based only on googling around, is that I need to wait for the FXZ for KitKat. Does that sound right?
Any other ideas?
Thank you in advance!!!!!!!!!!
Click to expand...
Click to collapse
I think that's right. It's ridiculous that by locking things down and preventing us from unlocking bootloader Verizon actually causes bricks of this nature to occur. If you had an unlocked bootloader you'd be 100% fine right now.
Sent from my Nexus 7
There is a way. I posted in previous forum.
Use fastboot
Fastboot wipe cache
Fastboot wipe user data
Try this if not pm me and I will help you out one on one
That should fix your issue
Sent from my XT1080 using xda app-developers app
phositadc said:
I think that's right. It's ridiculous that by locking things down and preventing us from unlocking bootloader Verizon actually causes bricks of this nature to occur. If you had an unlocked bootloader you'd be 100% fine right now.
Sent from my Nexus 7
Click to expand...
Click to collapse
If he hadn't brute forced a root method and messed with his phone he'd be 100% fine too
codito said:
If he hadn't brute forced a root method and messed with his phone he'd be 100% fine too
Click to expand...
Click to collapse
Ha...well there is that But what fun would that be?
The sad part is that the manufacturers could care less about giving us an unlocked bootloader. Android is a great ecosystem to play with and learn with and improve with. It's the carriers that are so paranoid about taking any tiny dent in their enormous profits that want to keep us locked out. So shame on them.
But, to be fair, I know the risks of the world we live in and this is my first brick in four Android phones, so I'm fine with it.
codito said:
If he hadn't brute forced a root method and messed with his phone he'd be 100% fine too
Click to expand...
Click to collapse
My point was merely that it's somewhat ironic that, by trying to prevent bricks by locking bootloaders, Verizon actually causes some bricks that would be avoided with an unlocked bootloader.
Not saying anything about whether what he was doing is right or wrong, or whether Verizon prevents more bricks than it causes.
Sent from my Nexus 7
Edit: but you've got to wonder. Are you more likely to brick using one of these crazy complicated methods we have to use to get around Verizon security? Or using fastboot OEM unlock + flash superuser. I bet per hundred rooted phones, less Nexus's (and other unlockable phones) are bricked than phones that are tightly locked down. Pure speculation of course.
killboredom said:
Ok, yesterday morning my MAXX received the KitKat update. Brainlessly, I clicked upgrade. This put me into the oh so famous bootloop.
During one of the boot loops, I managed to unroot with Voodoo.
Then in fastboot, I had the brilliant (aka, incredibly stupid) idea of flashing an old recovery. I had thought it was the one from 4.2.2 but sadly, it was from the previous version.
This had the appearance of working as it then booted to KitKat upgrade, which after a couple minutes failed.
Now I'm completely stuck in fastboot mode. I can't flash the 4.2.2 recovery. I haven't tried anything else. FXZ back to 12.15.15 doesn't work. Gives the GPT failure.
So...my belief, based only on googling around, is that I need to wait for the FXZ for KitKat. Does that sound right?
Any other ideas?
Thank you in advance!!!!!!!!!!
Click to expand...
Click to collapse
It sounds like you're actually stuck partially on JB, partially on KK, hence why you're bootlooping. I had a very similar issue when I tried to install the KK update through update.zip .......... after a couple hours, I finally got it back up and running.
My method - use the Method 2 Manual flash steps I posted in Dev section here - http://forum.xda-developers.com/showthread.php?t=2580060
Let me know if it works. I had problems at first, but that should cover it. Getting system to flash was actually the hardest part
I have spent the last week researching how to proceed with updating my Verizon Galaxy S3, but haven't found a clear concise answer pertaining to my current scenario. I thought a thread with a definitive answer would help others in my same boat save alot of time.
The last time I updated my phone was with a stock rooted MB1 rom with CWM 6023 recovery and 3.0.31-861013 kernel (2/14/13) and unlocked bootloader. Knowing that nothing good has ever come from taking OTA updates, I then removed the OTA Certs. I've kept my fingers crossed with the releases of ML1, MF1, and ND3 hoping that they would be better than MB1 but public opinion of the downsides has kept me from updating to any of these previous versions.
Now I'm DYING to update to Kit Kat and a better modem/radio than what I currently have. I've had really really poor experiences with a variety of handsets over the last 4 years using custom roms like AOSP, Cyanogen, etc. Therefore, I typically like to run a stock rooted version of whatever the current rom at the time is and remove some of the bloat myself or often there will be bloatware free stock roms for various handsets floating around so those are what I gravitate toward. More often than not custom roms have too many bugs (ie, camera not working or mms failures, etc) for production use.
So that being said, what would be the best course of action for someone such as myself to get on NE1 (or a really, really, really solid KitKat with NO bugs) and keep an unlocked bootloader for future flexibility. And, more importantly be able to update the modem/radio without locking the bootloader (as I've read some have found their bootloader locked after modem update)?
Any advice would be greatly appreciated.
Muleguy said:
I have spent the last week researching how to proceed with updating my Verizon Galaxy S3, but haven't found a clear concise answer pertaining to my current scenario. I thought a thread with a definitive answer would help others in my same boat save alot of time.
The last time I updated my phone was with a stock rooted MB1 rom with CWM 6023 recovery and 3.0.31-861013 kernel (2/14/13) and unlocked bootloader. Knowing that nothing good has ever come from taking OTA updates, I then removed the OTA Certs. I've kept my fingers crossed with the releases of ML1, MF1, and ND3 hoping that they would be better than MB1 but public opinion of the downsides has kept me from updating to any of these previous versions.
Now I'm DYING to update to Kit Kat and a better modem/radio than what I currently have. I've had really really poor experiences with a variety of handsets over the last 4 years using custom roms like AOSP, Cyanogen, etc. Therefore, I typically like to run a stock rooted version of whatever the current rom at the time is and remove some of the bloat myself or often there will be bloatware free stock roms for various handsets floating around so those are what I gravitate toward. More often than not custom roms have too many bugs (ie, camera not working or mms failures, etc) for production use.
So that being said, what would be the best course of action for someone such as myself to get on NE1 (or a really, really, really solid KitKat with NO bugs) and keep an unlocked bootloader for future flexibility. And, more importantly be able to update the modem/radio without locking the bootloader (as I've read some have found their bootloader locked after modem update)?
Any advice would be greatly appreciated.
Click to expand...
Click to collapse
Unfortunately, the ML1 update locked the bootloader and that hasn't changed with NC1 or NE1 (as far as we know). MF1 is the latest update I know of that still has the option for an unlocked bootloader. I've never used custom ROMs (but would very much like to) but I am currently on NE1 so I can't. Granted, I will say that Kitkat is a good update and things are running well. HOWEVER, from someone who would LOVE to have that option for an unlocked bootloader, I would personally discourage updates that would lock your bootloader. But the choice is yours.
Quick question (to someone with a little more expertise), If you were still on an update BEFORE MF1, and you had the option to download it OTA, could you extract the update.zip from /cache/fota like we did for the Kitkat update and distribute it so people could then flash it with Odin (and get unlocked bootloaders)? Or am I missing some flaw with that plan?
Muleguy said:
I have spent the last week researching how to proceed with updating my Verizon Galaxy S3, but haven't found a clear concise answer pertaining to my current scenario. I thought a thread with a definitive answer would help others in my same boat save alot of time.
The last time I updated my phone was with a stock rooted MB1 rom with CWM 6023 recovery and 3.0.31-861013 kernel (2/14/13) and unlocked bootloader. Knowing that nothing good has ever come from taking OTA updates, I then removed the OTA Certs. I've kept my fingers crossed with the releases of ML1, MF1, and ND3 hoping that they would be better than MB1 but public opinion of the downsides has kept me from updating to any of these previous versions.
Now I'm DYING to update to Kit Kat and a better modem/radio than what I currently have. I've had really really poor experiences with a variety of handsets over the last 4 years using custom roms like AOSP, Cyanogen, etc. Therefore, I typically like to run a stock rooted version of whatever the current rom at the time is and remove some of the bloat myself or often there will be bloatware free stock roms for various handsets floating around so those are what I gravitate toward. More often than not custom roms have too many bugs (ie, camera not working or mms failures, etc) for production use.
So that being said, what would be the best course of action for someone such as myself to get on NE1 (or a really, really, really solid KitKat with NO bugs) and keep an unlocked bootloader for future flexibility. And, more importantly be able to update the modem/radio without locking the bootloader (as I've read some have found their bootloader locked after modem update)?
Any advice would be greatly appreciated.
Click to expand...
Click to collapse
You are basically going to have to wait until a dev puts out a stock, rooted, knoxless ROM based on NE1. I've never heard of a modem flash locking a bootloader. Modern has nothing to do with the bootloader. Anyone who said this happened to them most likely flashed the firmware or full factory tar instead of the modem file by accident.
Sent from the Shark Tank using XDA Premium 4 mobile app
---------- Post added at 10:26 AM ---------- Previous post was at 10:23 AM ----------
JacobManning17 said:
Unfortunately, the ML1 update locked the bootloader and that hasn't changed with NC1 or NE1 (as far as we know). MF1 is the latest update I know of that still has the option for an unlocked bootloader. I've never used custom ROMs (but would very much like to) but I am currently on NE1 so I can't. Granted, I will say that Kitkat is a good update and things are running well. HOWEVER, from someone who would LOVE to have that option for an unlocked bootloader, I would personally discourage updates that would lock your bootloader. But the choice is yours.
Quick question (to someone with a little more expertise), If you were still on an update BEFORE MF1, and you had the option to download it OTA, could you extract the update.zip from /cache/fota like we did for the Kitkat update and distribute it so people could then flash it with Odin (and get unlocked bootloaders)? Or am I missing some flaw with that plan?
Click to expand...
Click to collapse
Flashing that update.zip file through ODIN before a dev had a chance to remove Knox and the locked down bootloader would be the same exact thing as accepting the OTA. You would then be locked down.
Sent from the Shark Tank using XDA Premium 4 mobile app
landshark68 said:
You are basically going to have to wait until a dev puts out a stock, rooted, knoxless ROM based on NE1. I've never heard of a modem flash locking a bootloader. Modern has nothing to do with the bootloader. Anyone who said this happened to them most likely flashed the firmware or full factory tar instead of the modem file by accident.
Sent from the Shark Tank using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I ran across a thread on here just this morning where someone was trying to update just the modem and ended up with a locked bootloader. The replies suggested that Samsung may have slipped something in with the modem file this go around. That's why I included it in this question. I will have to try to find the link to the other thread when I have more time later.
Muleguy said:
I ran across a thread on here just this morning where someone was trying to update just the modem and ended up with a locked bootloader. The replies suggested that Samsung may have slipped something in with the modem file this go around. That's why I included it in this question. I will have to try to find the link to the other thread when I have more time later.
Click to expand...
Click to collapse
You might be referring to this post in the general section. I am still unsure how they managed to do this if they downloaded the 20 MB VRUCML1 modem from our S3 forum. There is only one person whom I know to have extracted it and that is Invisiblek. Not a single other person before this user has mentioned having their bootloader locked from installing the VRUCML1 modem in CWM or TWRP. I really did not understand what they were trying to say so I just kept the convo moving in a different direction.
landshark68 said:
Flashing that update.zip file through ODIN before a dev had a chance to remove Knox and the locked down bootloader would be the same exact thing as accepting the OTA. You would then be locked down.
Sent from the Shark Tank using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm on ML1 unlocked bootloader/rooted from here
http://forum.xda-developers.com/showthread.php?t=2591895
If I flash NE1 via ODIN will it wipe my phone resulting in a clean NE1 with locked bootloader or will it be a non-destructive upgrade to fully stock/locked NE1?
lexluthor said:
I'm on ML1 unlocked bootloader/rooted from here
http://forum.xda-developers.com/showthread.php?t=2591895
If I flash NE1 via ODIN will it wipe my phone resulting in a clean NE1 with locked bootloader or will it be a non-destructive upgrade to fully stock/locked NE1?
Click to expand...
Click to collapse
Not sure whether the tar file you can download from sammobile will wipe your phone, but the tar file provided by open1your1eyes0 in the below linked thread will not wipe your phone. Either way, you will be on locked down NE1. Read the disclaimer at the top of the OP in open1your1eyes0's thread:
http://forum.xda-developers.com/showthread.php?t=2795659
landshark68 said:
Not sure whether the tar file you can download from sammobile will wipe your phone, but the tar file provided by openyoureyes1 in the below linked thread will not wipe your phone. Either way, you will be on locked down NE1. Read the disclaimer at the top of the OP in openyoureyes1's thread:
http://forum.xda-developers.com/showthread.php?t=2795659
Click to expand...
Click to collapse
I don't care if I'm locked going forward. So if I flash that, after I'll still have all my apps and appdata and be on NE1, locked? And then I can root with towelroot?
lexluthor said:
I don't care if I'm locked going forward. So if I flash that, after I'll still have all my apps and appdata and be on NE1, locked? And then I can root with towelroot?
Click to expand...
Click to collapse
I believe that is correct. I thought I saw a few people in the 4.4.2 update thread post that towelroot worked on NE1. May want to read the last few pages of that thread just to make sure about towelroot.
lexluthor said:
I don't care if I'm locked going forward. So if I flash that, after I'll still have all my apps and appdata and be on NE1, locked? And then I can root with towelroot?
Click to expand...
Click to collapse
That is correct. Towelroot works just fine with NE1
Sent from my SCH-I535 using XDA Premium 4 mobile app
landshark68 said:
I believe that is correct. I thought I saw a few people in the 4.4.2 update thread post that towelroot worked on NE1. May want to read the last few pages of that thread just to make sure about towelroot.
Click to expand...
Click to collapse
So far, looking ok. I flashed via ODIN and now it's at Android is upgrading and it's optimizing 502 apps, so looks like the apps are still there.
Hopefully towelroot works fine and then I can tweak my system settings back, install xposed and I'm good to go.
---------- Post added at 09:17 PM ---------- Previous post was at 08:25 PM ----------
lexluthor said:
So far, looking ok. I flashed via ODIN and now it's at Android is upgrading and it's optimizing 502 apps, so looks like the apps are still there.
Hopefully towelroot works fine and then I can tweak my system settings back, install xposed and I'm good to go.
Click to expand...
Click to collapse
All went great. It took a good half hour after the upgrade for the CPU to stop being pegged at 100% and have the phone be responsive again.
Very easy, it kept all of my applications and settings and I didn't really need to do much other than towelroot and re-install xposed.
I'm due for an upgrade soon anyhow, so I didn't really want to go through a lot of work getting to Kitkat.
Towel root not working any longer. Keep getting unsupported device with NE1 .. Ugh ..