Related
So I got the 217 OTA release today on my D4. Anyone else? Seems good so far.
--Randall
randallman said:
So I got the 217 OTA release today on my D4. Anyone else? Seems good so far.
--Randall
Click to expand...
Click to collapse
It is not available on mine yet.
I got the email, but never got the update. My phone died around lunch and I didn't have a charger until after 5p. I'm wondering if I missed a window.
640k said:
I got the email, but never got the update. My phone died around lunch and I didn't have a charger until after 5p. I'm wondering if I missed a window.
Click to expand...
Click to collapse
Yeah, I never asked to be on a soak test or anything... so I dunno if I was just randomly chosen or if it was released today... I suppose it doesn't really matter. Either way, it's pretty nice I guess A bit late given the fact that JB is the 'new hotness' now
randallman said:
Yeah, I never asked to be on a soak test or anything... so I dunno if I was just randomly chosen or if it was released today... I suppose it doesn't really matter. Either way, it's pretty nice I guess A bit late given the fact that JB is the 'new hotness' now
Click to expand...
Click to collapse
JB doesn't really mean anything. it's an incremental update and I'd be willing to bet some devs whip together a ROM with it included. There's still a chance we'll get it officially for our phone. A SLIGHT chance, but because its only an incremental update, with no new real requirements, it's a decent possibility.
Moto originally committed to 18 months of updates. We basically have until late next year to get it. By then, Klondike will be out and everyone will hate.
I got the update for mine but didnt do it. Mainly because I am rooted and wanted to see if I can first. Only thing I did was root so I can use wifi teather. I left everything else alone. I used to put diff roms in my original droid and got sick of setting it up again.
Were you rooted when you did the update? If so did was there any issues?
prowler9 said:
I got the update for mine but didnt do it. Mainly because I am rooted and wanted to see if I can first. Only thing I did was root so I can use wifi teather. I left everything else alone. I used to put diff roms in my original droid and got sick of setting it up again.
Were you rooted when you did the update? If so did was there any issues?
Click to expand...
Click to collapse
I'm not the OP, but I was rooted using the MotoFail exploit and the update applied without issue. I did have to re-acquire root with Razr's Edge, however, but that was painless.
prowler9 said:
I got the update for mine but didnt do it. Mainly because I am rooted and wanted to see if I can first. Only thing I did was root so I can use wifi teather. I left everything else alone. I used to put diff roms in my original droid and got sick of setting it up again.
Were you rooted when you did the update? If so did was there any issues?
Click to expand...
Click to collapse
I am rooted... I used OTA Rootkeeper to backup and restore root afterwards. I made sure to update the su binary as well from the superuser application as I had read some horror stories about people who lost root and couldn't get it back due to outdated superuser.apk and/or su binaries.
Additionally, my first attempt to install failed... I believe it was because I had added lines to loadpreinstalls.sh and mount_ext3.sh in /system/bin to ensure that the 'adb always root' local.prop file and the su binary was copied back into /data/ and /system/bin respectively every time I booted in case I lost root somehow. I had to remove the extra lines and then start over.
--Randall
Historically, how long before the update is widespread? My phone doesn't see it yet.
Folks, just an FYI.
The full XML.zip of fastboot images for this build has already been released in the development section by Skrillaz_CZ.
This not only means that you dont have to wait for the update at all, but also that we have the best safeguard against any mishaps from modding and flashing possible. You can recover your phone to the current release build no matter what happens using RSD Lite or the fastboot binary and ADB.
Incredibly quick work by Skrillax_CZ to pull this off their server right away like this!
randallman said:
So I got the 217 OTA release today on my D4. Anyone else? Seems good so far.
--Randall
Click to expand...
Click to collapse
Was this a previously owned device? An eBay or other like new used device?
Sent from my DROID4
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
First item, this is a question so it should belong in the question and answer threads! Secondly look here http://forum.xda-developers.com/showthread.php?t=2466191
Sent on my Moto X
Sorry, and thanks! I'll probably give this a shot, make that camera work a little better...
You can always install the SafeStrap ROM here. That's what I did.
http://forum.xda-developers.com/showthread.php?t=2484908
[Rom] [VZW] SafeStrap 139.12.57
Sent from my Moto X
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
This method makes it so SafeStrap is no longer available though, right? If that's not the case then... Don't know what I've been waiting for!
Sent from my Moto X
mercado79 said:
This method makes it so SafeStrap is no longer available though, right? If that's not the case then... Don't know what I've been waiting for!
Sent from my Moto X
Click to expand...
Click to collapse
I searched around and can't really find an answer to that. I don't use SafeStrap so I have no idea. I'd assume you can try the method I posted and try using SafeStrap after. If that doesn't work then just RSD back to pre-update and hang on to SafeStrap until it's figured out. No guarantees if it'd work / break stuff, though. You'd be the guinea pig for that one.
dymmeh said:
I searched around and can't really find an answer to that. I don't use SafeStrap so I have no idea. I'd assume you can try the method I posted and try using SafeStrap after. If that doesn't work then just RSD back to pre-update and hang on to SafeStrap until it's figured out. No guarantees if it'd work / break stuff, though. You'd be the guinea pig for that one.
Click to expand...
Click to collapse
@jcase Any chance you can answer this for us? Just cause someone was able to keep root (the one shot kind you mentioned), does that mean that using RSD is still on the table?
Sent from my Moto X
mercado79 said:
@jcase Any chance you can answer this for us? Just cause someone was able to keep root (the one shot kind you mentioned), does that mean that using RSD is still on the table?
Sent from my Moto X
Click to expand...
Click to collapse
If you take the OTA you dont have wY to revert to old stock Motorola block the reverts already and @jcase already said that he will be back for root in this device till 4.3 is out
Sent from my XT1060 using Tapatalk
juancaperez2000 said:
If you take the OTA you dont have wY to revert to old stock Motorola block the reverts already and @jcase already said that he will be back for root in this device till 4.3 is out
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
That's what I thought too. Thanks.
MikeyNick said:
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
Click to expand...
Click to collapse
For sure have I just updated my Moto X the other day on VZW and kept root. Here is a link to the process on how to do it
http://forum.xda-developers.com/showthread.php?t=2466191
will2live said:
For sure have I just updated my Moto X the other day on VZW and kept root. Here is a link to the process on how to do it
http://forum.xda-developers.com/showthread.php?t=2466191
Click to expand...
Click to collapse
I think that's not up for debate. The issue is that even though you kept root, you're now blocked from using safestrap or ever gaining root again in the future (once another ota comes through). The update has now patched root going forward and it sounds like you won't be able to keep it after this update.
MikeyNick said:
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
Click to expand...
Click to collapse
mercado79 said:
I think that's not up for debate. The issue is that even though you kept root, you're now blocked from using safestrap or ever gaining root again in the future (once another ota comes through). The update has now patched root going forward and it sounds like you won't be able to keep it after this update.
Click to expand...
Click to collapse
Safestrap i know about and dont care about as i dont use it. As for moving forward with root I'll be surprised if that is the case but I wont disagree either. It is very possible they patch something to actually block root down the road. From my understanding tho currently the patch is blocking ppl to root the update not keeping root if the process is followed correctly. My guess is odds are it will be the same on the next OTA just like we had to do on the original Razr line to keep root until the bootloader was unlocked. However if the next OTA is 4.3 tha tcould all change for sure as anything is possible. Even so when that time comes I'll just unlock mine. I do have a Dev edition i just haven't unlocked with it being brand new and not wanting to void warranty yet to make sure hardware is cool but i do want root so i went the long route for now is all.
dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
So I installed PwnMyMoto, SuperSU and OTA Root Keeper, then decided not to root. I installed the Verizon update and boom, I'm rooted. Is that what you're saying is needed? I was surprised that root apps all work fine for me, I really didn't do anything but install those apks before I installed the camera update!
boardrx182 said:
So I installed PwnMyMoto, SuperSU and OTA Root Keeper, then decided not to root. I installed the Verizon update and boom, I'm rooted. Is that what you're saying is needed? I was surprised that root apps all work fine for me, I really didn't do anything but install those apks before I installed the camera update!
Click to expand...
Click to collapse
As long as you had PwnMyMoto and never ran it / not rooted you were good to go. SuperSU could be installed before or after. I dont think OTA Root Keeper was needed at all. PwnMyMoto runs after a reboot so once you installed the OTA and rebooted it did its rooting magic automatically for you. Glad it all worked out for you
dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
dymmeh said:
As long as you had PwnMyMoto and never ran it / not rooted you were good to go. SuperSU could be installed before or after. I dont think OTA Root Keeper was needed at all. PwnMyMoto runs after a reboot so once you installed the OTA and rebooted it did its rooting magic automatically for you. Glad it all worked out for you
Click to expand...
Click to collapse
That's awesome, didn't realize that would happen automatically. I completely expected that I'd have to complete the entire root process steps that were outlined in an earlier post if I wanted root. Thanks for the reply.
will2live said:
Safestrap i know about and dont care about as i dont use it. As for moving forward with root I'll be surprised if that is the case but I wont disagree either. It is very possible they patch something to actually block root down the road. From my understanding tho currently the patch is blocking ppl to root the update not keeping root if the process is followed correctly. My guess is odds are it will be the same on the next OTA just like we had to do on the original Razr line to keep root until the bootloader was unlocked. However if the next OTA is 4.3 tha tcould all change for sure as anything is possible. Even so when that time comes I'll just unlock mine. I do have a Dev edition i just haven't unlocked with it being brand new and not wanting to void warranty yet to make sure hardware is cool but i do want root so i went the long route for now is all.
Click to expand...
Click to collapse
people who have moto employee friends say they are moving to 4.3 next. Also, there may be a work around for you to keep root with the next release, but because people who aren't on dev phones that must be sure they can retain root would not have used this method (as it is a one chance type of method). so it is more likely that any new workarounds that people come up with will be for those that still have the ability to downgrade to original stock firmware. Also, SS is nice because it gives you the ability to run the phone just like you normally would but you can create complete backups of the device so you don't have to set everything up all over again if you screw something up with your phone. Even if you don't use SS for flashing roms it is still useful for back ups.
jayboyyyy said:
people who have moto employee friends say they are moving to 4.3 next. Also, there may be a work around for you to keep root with the next release, but because people who aren't on dev phones that must be sure they can retain root would not have used this method (as it is a one chance type of method). so it is more likely that any new workarounds that people come up with will be for those that still have the ability to downgrade to original stock firmware. Also, SS is nice because it gives you the ability to run the phone just like you normally would but you can create complete backups of the device so you don't have to set everything up all over again if you screw something up with your phone. Even if you don't use SS for flashing roms it is still useful for back ups.
Click to expand...
Click to collapse
I have my Moto contacts and yes they are moving to 4.3 next last i was told when I asked. As for downgrading stock software that isn't going to happen once updated as you can't go backwards. Moto devices have been that way going back to the original Droid Razr. Its few and far between where you could actually go backwards after an OTA. So unless you mean stock of the current build installed then ppl will have issues for sure. That said if ppl OTA and have root now but for whatever reason need to use the new fastboot file that was just posted they will in fact be SOL for gaining root. This is exactly why I refuse to buy consumer units from the carrier besides a few other reason I wont go into. My theory is simple we want to mess with device buy an unlockable one or be ready to suffer/wait for an exploit after an OTA hits.
As far as root moving forward what process you talking about tho? There is 2 ways to do it. The one posted right above your post in this thread, or the link I posted above. If the info in this thread was used yes there may be an issue because of the patch. However I will be very surprised to see ppl not be able to keep root if they updated using the process in the link I posted above. Besides having to fastboot the boot.img to recovery in that process its the same way original Droid Razr owners had to update to be able to keep root if there was no root process for the OTA being pushed. Moving forward my guess is there will be an issue once 4.3 hits tho. I'm not sure you will be able to use the old kernel from 4.2.2 to overwrite recovery and boot the 4.3 /system so you can restore root and pull the actual 4.3 boot.img so that can be used for the recovery highjack. Bottom line is only time will tell at this point as you never know what Moto/Google will do with the next update.
Agreed on SS for backups even if not flashing ROMs, but personally i just dont mess with my device enough to worry about a full back i guess. For apps/settings I just use MyBackup PRO. I've also have an app a buddy made that creates a full XML if i wanted to use it. In the old days I use to make alot of backups for ROM flashing when I used SS. Guess in my old age I've just got lazy and dont worry about it that much anymore. I really hose the device I'll just swap to one of my others til i get back to fixing the messed up one.
will2live said:
I have my Moto contacts and yes they are moving to 4.3 next last i was told when I asked. As for downgrading stock software that isn't going to happen once updated as you can't go backwards. Moto devices have been that way going back to the original Droid Razr. Its few and far between where you could actually go backwards after an OTA. So unless you mean stock of the current build installed then ppl will have issues for sure. That said if ppl OTA and have root now but for whatever reason need to use the new fastboot file that was just posted they will in fact be SOL for gaining root. This is exactly why I refuse to buy consumer units from the carrier besides a few other reason I wont go into. My theory is simple we want to mess with device buy an unlockable one or be ready to suffer/wait for an exploit after an OTA hits.
As far as root moving forward what process you talking about tho? There is 2 ways to do it. The one posted right above your post in this thread, or the link I posted above. If the info in this thread was used yes there may be an issue because of the patch. However I will be very surprised to see ppl not be able to keep root if they updated using the process in the link I posted above. Besides having to fastboot the boot.img to recovery in that process its the same way original Droid Razr owners had to update to be able to keep root if there was no root process for the OTA being pushed. Moving forward my guess is there will be an issue once 4.3 hits tho. I'm not sure you will be able to use the old kernel from 4.2.2 to overwrite recovery and boot the 4.3 /system so you can restore root and pull the actual 4.3 boot.img so that can be used for the recovery highjack. Bottom line is only time will tell at this point as you never know what Moto/Google will do with the next update.
Agreed on SS for backups even if not flashing ROMs, but personally i just dont mess with my device enough to worry about a full back i guess. For apps/settings I just use MyBackup PRO. I've also have an app a buddy made that creates a full XML if i wanted to use it. In the old days I use to make alot of backups for ROM flashing when I used SS. Guess in my old age I've just got lazy and dont worry about it that much anymore. I really hose the device I'll just swap to one of my others til i get back to fixing the messed up one.
Click to expand...
Click to collapse
3 ways to maintain root are the one in the thread, SS, and the one you posted. The one you posted actually allows you to flash the original stock firmware on the phone because the BL was never touched thus the security (keeping you from downgrading) was never installed. That was what I was referring to when I said those that must make sure they will retain root in the future would not have done the install pwnmymmoto without running then take ota then run pwnmymoto. As you said those people will be screwed if the next root requires you to flash back to original stock or use part of the pwnmymoto exploit that will only be accessible to those that got the OTA with SS or the link you posted. I don't toy with my phone as much as I used to especially this one, but bypasing exchange security is pretty essential for me. I don't want an encrypted device with mandatory pin. I never lose my phone and I would know within minutes of losing it if i ever did so I could shut it down remotely.
And I'm not sure about the new kernel situation either. This is why I wanted to make sure I could go back to original firmware as I see that being our best bet to retain root through 4.3, assuming jcase doesn't release another exploit for it to get some cash.
jayboyyyy said:
3 ways to maintain root are the one in the thread, SS, and the one you posted. The one you posted actually allows you to flash the original stock firmware on the phone because the BL was never touched thus the security (keeping you from downgrading) was never installed. That was what I was referring to when I said those that must make sure they will retain root in the future would not have done the install pwnmymmoto without running then take ota then run pwnmymoto. As you said those people will be screwed if the next root requires you to flash back to original stock or use part of the pwnmymoto exploit that will only be accessible to those that got the OTA with SS or the link you posted. I don't toy with my phone as much as I used to especially this one, but bypasing exchange security is pretty essential for me. I don't want an encrypted device with mandatory pin. I never lose my phone and I would know within minutes of losing it if i ever did so I could shut it down remotely.
And I'm not sure about the new kernel situation either. This is why I wanted to make sure I could go back to original firmware as I see that being our best bet to retain root through 4.3, assuming jcase doesn't release another exploit for it to get some cash.
Click to expand...
Click to collapse
Gotchya, makes total sense now what you are saying. I think there is just confusion at times when talking about root & OTA because of different ways to do it in a case like this device. Being a Moto guy for so long tho i'm use to all the BS they throw at us.....lol. That said that is why i posted the link I did. Imho it's a bad plan to update using the other method of installing pwnmymoto and not running it first before taking the OTA. Doing the process to protect root before updating is a much safer bet atm imo. Sure its a little more work but at the end of the day you dont have to be worried as much moving forward. Only concern I have still for doing it the longer way is if that process will work when they push out 4.3. It had alot of changes in it so lord only knows what will be up for keeping root. And really in my case its no concern but for all the folks with consumer version it is still a concern i think for the time being
**Make certain that your reactivation lock in security settings is off before beginning this process**
1. Take the NG3 OTA update.
2. Download and install Towelroot-v3.apk(this version does not require internet access).
3. Place your phone into "Download Mode" (press and hold the Home, Volume Down, and Power keys until the phone powers on and displays warning screen, then press Volume Up key) and flash the G870A_NE4_Stock_Kernel using Odin's PDA slot(AP in Odin v3.09+).
4. Open the Towelroot app from your app drawer and press "Make it Rain" to root your device.
5. Power off then boot into "Download Mode" again and flash the G870A_NG3_Stock_Kernel also in Odin's PDA slot(AP in Odin v3.09+).
6. Download SuperSu to manage root access. Done!
Troubleshooting:
1. If the NG3 OTA update fails consider flashing the G870AUCU1ANE4_Full_Odin.tar to return to stock then take the NG3 OTA update, (or place the G870A_NE4toNG3_OTA.zip onto your ext-sdcard and sideload from stock recovery). Once updated to NG3 continue to Step 2 above.
2. The most common cause of an Odin flash failure is a bad usb port or cable. Please check before reporting a failure.
Notes:
1. After flashing the NE4 kernel your phone may run a little wonky and towelroot may not root on the first try. If that happens reboot and try towelroot once again. Once rooted and after flashing the NG3 kernel your phone will once again run like a champ!
2. The above process will not affect your User Data or Knox Warranty Flag.
Credits:
@lordmorphous - Tester
Gonna try this... Thanks! :beer:
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
Yes this worked. Thank you very much.......
Are we going to trip Knox using the method above ???
Just wanna be sure about this. ...g
gregsarg said:
Are we going to trip Knox using the method above ???
Just wanna be sure about this. ...g
Click to expand...
Click to collapse
Nope.
Does anyone have a list of the benefits of updating to NG3?
I just rooted my new phone on NE4 and I want to know whether it's worth taking the time.
Thanks for the How-to! Worked great for me!
Any benefits on ng3 over stock?
Root possible for 'straight out-of-the-box' G870AUCU1ANG3???
I've looked and looked around the forums here and have come to the conclusion that the AT&T S 5 I recently picked up is, sadly, unable to be rooted. Does anyone here know if this is true? As the title suggests, my phone seems to have come loaded with G870AUCU1ANG3. Is it possible that it came with the previous iteration (NE4, I think??) and I didn't avoid an update, thus meaning I can flash the earlier version? Can I even tell whether it's possible to 'revert' to NE4 (or whatever it would be)? Is any of this even possible without having been previously rooted, or am I wasting my time searching this out? Naive but earnest questions... sorry if I'm in the wrong place here. I promise, I poked around the site for a few days in search of clarity before posting.
papayajelly said:
I've looked and looked around the forums here and have come to the conclusion that the AT&T S 5 I recently picked up is, sadly, unable to be rooted. Does anyone here know if this is true? As the title suggests, my phone seems to have come loaded with G870AUCU1ANG3. Is it possible that it came with the previous iteration (NE4, I think??) and I didn't avoid an update, thus meaning I can flash the earlier version? Can I even tell whether it's possible to 'revert' to NE4 (or whatever it would be)? Is any of this even possible without having been previously rooted, or am I wasting my time searching this out? Naive but earnest questions... sorry if I'm in the wrong place here. I promise, I poked around the site for a few days in search of clarity before posting.
Click to expand...
Click to collapse
There shouldn't be any reason why you can't follow the instructions in the 1st post of this thread starting with step 2.
I've been searching for a while and can't find anything about using this root method and then being able to install safestrap. Has anyone been successful in doing this? Do I need to downgrade before and does anybody have the downgrade file? FYI Just bought my phone last night and was successful in rooting.
rescuedad said:
I've been searching for a while and can't find anything about using this root method and then being able to install safestrap. Has anyone been successful in doing this? Do I need to downgrade before and does anybody have the downgrade file? FYI Just bought my phone last night and was successful in rooting.
Click to expand...
Click to collapse
Never mind, I figured it out. If you have the active you need to downgrade the kernel to NE4 like you do if you need root. Then you install Safestrap 3.75. I'm doing a Nandroid backup as I type. I'm going to re-flash the NG3 stock kernel when I'm done and hopefully that will be fine.
If it bricks, I can always take it back since I blocked the knox counter... BTW I'm on At&T
I downgraded to the NE4 to root. Along with others here I have to ask, what are, if any, benefits to upgrading the kernel?
panthersdzynes said:
I downgraded to the NE4 to root. Along with others here I have to ask, what are, if any, benefits to upgrading the kernel?
Click to expand...
Click to collapse
Not sure I understand the question but I will take a shot......typically the kernel, modules, and non-hlos.bin have to match or else you may experience issues such as no wifi, lag, etc. The NE4 and NG3 kernel and modules may be similar enough that you will not experience issues immediately but they may develop later unless you reflash the NG3 kernel to match your modules and non-hlos.
muniz_ri said:
Not sure I understand the question but I will take a shot......typically the kernel, modules, and non-hlos.bin have to match or else you may experience issues such as no wifi, lag, etc. The NE4 and NG3 kernel and modules may be similar enough that you will not experience issues immediately but they may develop later unless you reflash the NG3 kernel to match your modules and non-hlos.
Click to expand...
Click to collapse
I see. Thank you, that answers my question.
THanks XDA
Been away along time. Had iphones for the last 6 years. Use to go here all the time in the Kaiser days (Att Tilt) if any of you remember. I see XDA has still been kicking ass while I've been gone! Glad to be back and Thank You everyone especially first poster for the guide to root my Att GS5 Active.
THANK YOU
Working perfectly. ..thank you. ..g
There was a small update released today. Can someone that is rooted grab it from their fota/cache folder and send to me so that I can update this guide? Thanks.
WORKED! AWESOME!
Now... I have installed SuperSU. Was that left out of the first post?
Also, if I do not flash the NG3 Stock Kernel back afterwards, will I experience funkiness?
Thanks again!
It seems that I have root for...most...intents and purposes, but not when it come to things like xposed or next app so fix. Now I'm running 1.4.4.B.0.37 On Xperia Z1s. Rooted using flash tool, note... Does seem to freeze at the reboot part when it tries to install busybox so I manually install from marke. I had root for awhile then saw on xda that you could "proper" root by updating threw ota. Tried and failed multiple times. I have a screenshot of the error from xposed. Any help greatly appreciated.
imageshack.com/a/img538/7642/7kC97V.png
Figured Out
Well, i never gave up and figured out the problem. Even though i had the newest version through OTA, it did me no good to revert back to last version since thats the version you have to "proper" root. Sooo, i downgraded...again...to stock (C6916_14.2.C.0.159_TMobile.ftf) then rooted and it worked. doing installs and checking as i type but so far viper4android and xposed are g2g. now to upgrade to next version (C6916_14.4.B.0.37_T-Mobile.ftf) for "proper" root. thanks and glad if i could help others with same problem. I think i will post a guide for z1s so others (seems to be alot of us) can have noob friendly guide. :highfive:
starting my guide...
I am starting my guide and wanted to know if there should be a specific area i should post it? Is the correct place here in the Q&A area? or in the Development area?
Please i try to root my device G920A with of3 by using srsroot.exe the program tell me root done but after that the device restart and appear it's not rooted ... please any one can solve my problem ....i'm search about this problem but without any solation
smart19900 said:
Please i try to root my device G920A with of3 by using srsroot.exe the program tell me root done but after that the device restart and appear it's not rooted ... please any one can solve my problem ....i'm search about this problem but without any solation
Click to expand...
Click to collapse
there is no known root method for OF3 and later firmware. There is also no known way to roll Back To earlier firmware if you arrived at OF3 via OTA updates.
Sent from my SAMSUNG-SM-G920A using Tapatalk
dandrumheller said:
there is no known root method for OF3 and later firmware. There is also no known way to roll Back To earlier firmware if you arrived at OF3 via OTA updates.
Sent from my SAMSUNG-SM-G920A using Tapatalk
Click to expand...
Click to collapse
"OF3 via OTA updates" stupidly I updated a bestbuy I suppose this doesn't make a difference? Also is there a link where we can keep updated on 0f3 root?
shawn2323 said:
"OF3 via OTA updates" stupidly I updated a bestbuy I suppose this doesn't make a difference? Also is there a link where we can keep updated on 0f3 root?
Click to expand...
Click to collapse
No, if you reached OF3 via official updates without prior root, you're committed. No known way of rolling back and no current root.
Just monitor the general and development subforums here - if a new root exploit is found it will be big news around here. However, I personally don't expect to ever see root for 5.x. MAYBE if/when we get MM something might materialize, but there is very little đeveloper interest left in this variant because it's so locked down. Plus we're now half way through its life cycle. I'm certainly not counting on it.
Sent from my XT1526 using Tapatalk
I've been lurking around this week. I saw devs in GSMHosting talking (here and here) about [KERNEL] UniKernel v8-0002 COH9 [G920 /925] being compatible to G920A.
Can anyone confirm this?
Thanks
shichemt said:
I've been lurking around this week. I saw devs in GSMHosting talking (here and here) about [KERNEL] UniKernel v8-0002 COH9 [G920 /925] being compatible to G920A.
Can anyone confirm this?
Thanks
Click to expand...
Click to collapse
Those methods appears to require either a downgrade to 5.0.2. Which, as indicated, triggered an sboot error, or flashing unikernel, which is not possible on the 920a due to locked bootloader. Unless something has changed recently (which would have likely been well publicised here) neither of these proposed methods appear to work.
While it's possible unikernel is compatible with 920a, we have no way to flash it.
Sent from my XT1526 using Tapatalk