I just got a prompt for a new OTA update, but being rooted and running a ROM I couldn't install it. It gave no new information about the update such as size or fixes. Anyone else get this? I'm on an OC3 based ROM by the way.
yea i got it
Seanbest said:
I just got a prompt for a new OTA update, but being rooted and running a ROM I couldn't install it. It gave no new information about the update such as size or fixes. Anyone else get this? I'm on an OC3 based ROM by the way.
Click to expand...
Click to collapse
It is the stage fright update
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Will we be able to flash it some other way?
ClearD said:
Will we be able to flash it some other way?
Click to expand...
Click to collapse
I'm sure there will be soon
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Well, on second thought, I just went ahead and let the update run. It completed. Everything appears normal.
I confirm, it is a fix for Stagefright. Baseband version went from I337UCUFNJ4 to I337UCUFNJ5
+ SuperSU is working properly.
Below: Before & After the update
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
New Update Came ..
https://www.att.com/esupport/softwareUpdateArticle.jsp?sid=KB419415&cv=820
ClearD said:
Well, on second thought, I just went ahead and let the update run. It completed. Everything appears normal.
Click to expand...
Click to collapse
Were you rooted with the Flashfire method?
Anytime AT&T or Samsung offer a "security" update FOTA, I cringe. I'm on rooted Lollipop and absolutely have to remain rooted to use Total Recall call recorder (you can't imagine how many times it's saved my ass with baseless promises from AT&T and other utility vendors), so I'm always hesitant to upgrade to any FOTA's that may make it more difficult to either flash a better ROM, or other utilities that it might block. Call me paranoid, but I'm going to hold off and try to find a better solution to threats to my OS. Belarc Security Advisor (Free) is highly respected, and a non-conventional system scan that identifies real threats. Running it yesterday and just now; show no threats. I realize that Stagefright is a threat, but I'm running antivirus software that I trust and keep my phone backed up locally on a regular basis.
billbillw said:
Were you rooted with the Flashfire method?
Click to expand...
Click to collapse
Well, I also let it run. Figured worst case, it would be rejected due to root. It ran, no errors, still on root (using Flashfire method). Stagefright detector now shows my device is safe.
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
nukesnooper said:
Anytime AT&T or Samsung offer a "security" update FOTA, I cringe. I'm on rooted Lollipop and absolutely have to remain rooted to use Total Recall call recorder (you can't imagine how many times it's saved my ass with baseless promises from AT&T and other utility vendors), so I'm always hesitant to upgrade to any FOTA's that may make it more difficult to either flash a better ROM, or other utilities that it might block. Call me paranoid, but I'm going to hold off and try to find a better solution to threats to my OS. Belarc Security Advisor (Free) is highly respected, and a non-conventional system scan that identifies real threats. Running it yesterday and just now; show no threats. I realize that Stagefright is a threat, but I'm running antivirus software that I trust and keep my phone backed up locally on a regular basis.
Click to expand...
Click to collapse
If you're using the Stock AT&T Lolipop, and Flashfire method for rooting, you will be OK to let the update run. It ran with no issues for me and it kept root.
billbillw said:
Well, I also let it run. Figured worst case, it would be rejected due to root. It ran, no errors, still on root (using Flashfire method). Stagefright detector now shows my device is safe.
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
If you're using the Stock AT&T Lolipop, and Flashfire method for rooting, you will be OK to let the update run. It ran with no issues for me and it kept root.
Click to expand...
Click to collapse
That's exactly how I did it. My only concern is that it may install patches that could further restrict future modifications.
I also just completed running Lookout and it found no threats or vulnerabilities. I'm staying where I am until I hear more feedback.
Thanks for your advice. I'll be keeping an eye on it.
It's coming in as a 280mb download, I'm going to see what happens with root (previously used Flashfire)
sim_pl said:
It's coming in as a 280mb download, I'm going to see what happens with root (previously used Flashfire)
Click to expand...
Click to collapse
Please Upload .cfg File For Update My Device .. That OTA File /cache .. Check It And Upload It Please And Check fota Folder
UPDATED POST:
I upgraded with the install stock but "keep root" method, using flashfire...
The update failed at 29%.
I did a factory reset, and it still failed at 29%...
What are my options now?
Update:
I used Flashfire to install the tethering addon... I wonder if that is the culprit.
Installing without thethering... will update with results.
And It's a pain to download that ATT update each time. --- Their servers are SLOW!
Same story here. Update stops and phone reboots about a third of the way through. Defrosted all Samsung/AT&T bloat and tried again. Same story. Bummer.
I rooted my wife's 0C3 with Kingroot and tried to take the update. It failed.
Maybe I should try again since I just used triangle away to get rid of the "custom" nag at boot.
Rockin' a l337 with Goldeneye v49.1 + Wanam Xposed and loving life on AT&T's 4G LTE network
billbillw said:
Were you rooted with the Flashfire method?
Click to expand...
Click to collapse
Yes. Rooted with flashfire, on oc3 bootloader. I ran the update through the normal OTA method, not trying to install it through flashfire. It worked fine and root stayed normal. Verified when titanium backup ran last night on its normal schedule.
Well, it updated fine, using just the straight rooted rom, no additional flashes. No more fails at 29%...
It appears that adding in anything extra, de-bloat, hotspot enable, etc. will cause the update to fail.
/sk
Reinstalled the rooted stock ROM and the update worked fine. Still have root. All is groovy.
Related
Nothing is wrong at this point.
I am following this method to root and unlock my device. (will not be installing any ROMs)
http://forum.xda-developers.com/showthread.php?t=2046439
My question:
I flashed the VRALEC boot chain file. (step 1 in the guide) -- the S3 then rebooted, and I had to decrypt my device.
I was worried that my encryption would have caused a problem.. I am currently decrypting the device just in case.
Do I have to re-flash the VRALEC or simply continue with my now-decrypted device? Is everything a-ok to continue?
Once again.. I forgot I had encryption enabled - I am currently decrypting it before I continue with the guide.
Thanks alot guys..
Solved.. and rooted, with unlocked boot loader. Thanks alot.
EDIT: I'm a noob at this stuff, but can someone give me some advice on how to block Verizon OTA updates?
Before I rooted, VZN wanted to give me a update. Not sure what it was. I post poned it for a few days.. but don't want it to brick my phone when it awakens.
Any suggestions that don't involve a custom ROM ? Thanks again!!
Credrili said:
Solved.. and rooted, with unlocked boot loader. Thanks alot.
EDIT: I'm a noob at this stuff, but can someone give me some advice on how to block Verizon OTA updates?
Before I rooted, VZN wanted to give me a update. Not sure what it was. I post poned it for a few days.. but don't want it to brick my phone when it awakens.
Any suggestions that don't involve a custom ROM ? Thanks again!!
Click to expand...
Click to collapse
If you download Titanium Backup from the Play Store, look for sdm 1.0 and freeze it or uninstall it. Sdm 1.0 will be in red since its a System service.
SlimSnoopOS said:
If you download Titanium Backup from the Play Store, look for sdm 1.0 and freeze it or uninstall it. Sdm 1.0 will be in red since its a System service.
Click to expand...
Click to collapse
Thank you SlimSnoop. I have done this.. while I was searching around, I saw some people also froze "fwupgrade". But I cannot find this.
Do you know if Verizon removed it via a previous OTA?
Thanks again.. I hope this keeps me safe from unexpected updates. (my other OTA was forced by VZN !!)
As far as disabling updates go I would recommend titanium backup, and freezing the update service. "FWUpgrade" as well as "SDM" are the names. You can also uninstall it, but freezing it in Titanium is my recommendation.... This will prevent your phone from pinging OTA updates in the future even when big red pushes them.
SlimSnoopOS said:
If you download Titanium Backup from the Play Store, look for sdm 1.0 and freeze it or uninstall it. Sdm 1.0 will be in red since its a System service.
Click to expand...
Click to collapse
ManiakalSealion said:
As far as disabling updates go I would recommend titanium backup, and freezing the update service. "FWUpgrade" as well as "SDM" are the names. You can also uninstall it, but freezing it in Titanium is my recommendation.... This will prevent your phone from pinging OTA updates in the future even when big red pushes them.
Click to expand...
Click to collapse
Hmm... this is odd, I cannot find "FWUpgrade" in Titanium Pro version. I will keep looking.
EDIT: I'm on Jelly Bean 4.1.1... didn't do anything. Is it perhaps given a different name? Could it be hidden?
EDIT2: Still no luck... from researching, it apparently exists. But I simply can't find it in Titanium.
Any suggestions? Does it go by a another name in Jelly Bean?
Credrili said:
Hmm... this is odd, I cannot find "FWUpgrade" in Titanium Pro version. I will keep looking.
EDIT: I'm on Jelly Bean 4.1.1... didn't do anything. Is it perhaps given a different name? Could it be hidden?
Click to expand...
Click to collapse
It should be there. For your filters, do you have these set as:
Filter by status: all
Filter by type: System
When you look for FWUpgrade, it should be the last item in the F's. If it's not there, it wouldn't be anywhere else cuz I'm on a custom 4.1.1 TW rom with FWUpgrade not frozen and I see it.
SlimSnoopOS said:
It should be there. For your filters, do you have these set as:
Filter by status: all
Filter by type: System
When you look for FWUpgrade, it should be the last item in the F's. If it's not there, it wouldn't be anywhere else cuz I'm on a custom 4.1.1 TW rom with FWUpgrade not frozen and I see it.
Click to expand...
Click to collapse
Hmm... still can't find the bloody thing. I know what you're saying.. it has to be here somewhere. Very weird. I froze SDM successfully, but can't find this last one.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm pretty sure fwupgrade has been updated to allshare cast, did you update it in the play store?
Sent from my SCH-I535 using xda app-developers app
deuce237bblock said:
I'm pretty sure fwupgrade has been updated to allshare cast, did you update it in the play store?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
No I haven't... I believe I disabled all share cast via built in "force disable". Are you saying I should enable it, update it, then freeze it via TB?
Thanks alot, this would explain the mystery. :laugh:
EDIT: What I mean to say is that I DO have All Share Cast, and some others with similar name (Dongle S/W, around 29MB)
EDIT: Ok.. then I suppose this means I must disable anything relating to All Share Cast. What about Kies? I read software can be updated from that as well, but prob only manually. Not sure.
Credrili said:
No I haven't... I believe I disabled all share cast via built in "force disable". Are you saying I should enable it, update it, then freeze it via TB?
Thanks alot, this would explain the mystery. :laugh:
EDIT: What I mean to say is that I DO have All Share Cast, and some others with similar name (Dongle S/W, around 29MB)
EDIT: Ok.. then I suppose this means I must disable anything relating to All Share Cast. What about Kies? I read software can be updated from that as well, but prob only manually. Not sure.
Click to expand...
Click to collapse
I think I blocked off pretty much everything - wow, I should have rooted long ago. Coming from a rooted HTC Dinc, this phone is simply amazing.
I really don't want to lose root at the hand of Verizon though -- I believe I blocked all ShareCast junk and of course the SDM 1.0 service.
Can anyone let me know if this is good to protect from OTA updates? (Used Titanium Freeze method)
Thanks again.
as the title says, I'm looking to see if anybody knows or has been successful in figuring out how to Root the Note Edge.
I was thinking of using CF 910method but wanted to see what others have done before I started experimenting
zz1049 said:
as the title says, I'm looking to see if anybody knows or has been successful in figuring out how to Root the Note Edge.
I was thinking of using CF 910method but wanted to see what others have done before I started experimenting
Click to expand...
Click to collapse
I dont think many have tried yet. Only a few have gotten there device today, the others are waiting for it in the mail, And i believe all of us arent up to bricking rare device lol.
but yea ill wait on the root until there is a way to no trip knox. I like having the option of returning it. (some places check now)
Yeah I thought about it in being a guinea pig. I'm not trying to spend time recovering this thing.
Until then, I look forward to any positive word to root, not necessarily trying to maintain Knox, but that would be amazing.
I plan on trying today and will post an update. I have the tmobile version and will use the note 4 root method.
I read somewhere the tmobile note 4 root method from chainfire works on the tmobile note edge. I'll be trying that method when I get mine on monday from fedex.
---------- Post added at 09:59 AM ---------- Previous post was at 09:55 AM ----------
lreeb1 said:
I plan on trying today and will post an update. I have the tmobile version and will use the note 4 root method.
Click to expand...
Click to collapse
I read somewhere the tmobile note 4 root method from chainfire works on the tmobile edge. I don't see why the note 4 root method wouldnt work, its the same phone just different screen
I just successfully rooted using the t-mobile chainfire. I followed the directions exactly from the T-Mobile Galaxy Note 4 xda page. It's under general and stickied at the top. In Odin it said failed after flashing the chainfire tar but it appears to have worked just fine. I also flashed the twrp linked in the root how-to, then flashed super su in twrp.
I confirmed root by running SuperSu and also running Titanium Backup.
This is the link I followed:
http://forum.xda-developers.com/not...sy-steps-stock-odin-n910tuvu1anih-cf-t2903733
lreeb1 said:
I just successfully rooted using the t-mobile chainfire. I followed the directions exactly from the T-Mobile Galaxy Note 4 xda page. It's under general and stickied at the top. In Odin it said failed after flashing the chainfire tar but it appears to have worked just fine. I also flashed the twrp linked in the root how-to, then flashed super su in twrp.
I confirmed root by running SuperSu and also running Titanium Backup.
This is the link I followed:
http://forum.xda-developers.com/not...sy-steps-stock-odin-n910tuvu1anih-cf-t2903733
Click to expand...
Click to collapse
Hey, which TWRP file did you grab? Same from the link?(openrecovery-twrp-2.8.1.1-trltetmo.img)
What's your build #(N915TUVU1ANJL) ?
I'm thinking about doin this as well.
Yes. I used the one from the link.
lreeb1 said:
Yes. I used the one from the link.
Click to expand...
Click to collapse
You grabbed all the files? No problem even though is a different build #?
leprophotography said:
You grabbed all the files? No problem even though is a different build #?
Click to expand...
Click to collapse
I haven't had any issues. I was concerned when Odin showed failed after flashing the chainfire tar but I went ahead and pulled the battery after giving it a moment, booted back into download mode and flashed the twrp recover. I got all the files from the post I linked above, except for Super Su. Follow at your own risk but things went pretty smoothe for me.
lreeb1 said:
I haven't had any issues. I was concerned when Odin showed failed after flashing the chainfire tar but I went ahead and pulled the battery after giving it a moment, booted back into download mode and flashed the twrp recover. I got all the files from the post I linked above, except for Super Su. Follow at your own risk but things went pretty smoothe for me.
Click to expand...
Click to collapse
Thanks for taking the risk!
I did the same minus installing TWRP Recovery after, as I just want my phone to be stock touchwiz (except for root). But using the N910T root method (CF) Did not produce a successful root, do you think it may have been TWRP that actually made the root work?
DO NOT TRY THIS ROOT!!! THIS DOES NOT WORK!!! This will give you Cache and other problems. I have tried this on 3 T-Mobile Galaxy Edge phones and all of them give the same problem. I had to restore the original firmware on all 3 phones. I also had a friend try this and the same results.
OP, lets see some proof!!!
I think I'll wait for the L update before i root. ***Unless a knowledgeable recognized contributor posts a way*** @Chainfire
anyone else been successful or unsuccessful using this method?, kinda stuck in limbo right now!
I think best bet is to just wait for a 100% method especially on a phone so expensive
Sent from my SM-N915T using XDA Free mobile app
I don't really understand what you mean by Cache and other problems. Could you be more specific? I'm not trying to lead anyone afoul, just simply stating I was successful at using the tmobile note root method without any issues.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I get the unable to mount cache in TWRP. The Note 4 root messes with the file system and does something with the TWRP. Can you be more specific on how you install SU in TWRP? When you reboot from TWRP and it asks you to install SU, is that when you install it?
Has anyone unlocked the tmobile note edge yet for at&t use
tpinfo4 said:
I get the unable to mount cache in TWRP. The Note 4 root messes with the file system and does something with the TWRP. Can you be more specific on how you install SU in TWRP? When you reboot from TWRP and it asks you to install SU, is that when you install it?
Click to expand...
Click to collapse
I flashed the super su zip in TWRP.
http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip
Like I said, I have been using my phone fine since Saturday without issue but I haven't tried to mount the cache so I can't speak to that.
I think there was a misunderstanding on installing SU. I just tried this: Installed TWRP via download mode. Went into recovery and installed the SU file from the link you provided. I rebooted the phone and updated the SU program in the play store. I also installed Titanium. When I clicked on the SU program, it asked to update binary and I clicked "Normal". It came back with a response of "Installation Failed". When I run Titanium, it says "Asking for root rights...." and a popup came from SU that says it has been granted access. It is stuck on the "Asking for roots rights". I also installed Root Checker and it says I do not have root.
Did you update SU from the play store?
lreeb1 said:
I flashed the super su zip in TWRP.
Like I said, I have been using my phone fine since Saturday without issue but I haven't tried to mount the cache so I can't speak to that.
Click to expand...
Click to collapse
---------- Post added at 08:14 PM ---------- Previous post was at 07:53 PM ----------
I also tried the new download from chainfire that has our phone on his list now and same results. I don't believe "lreeb1" has root. When I don't update my SU, it shows I have root to various programs, but the programs all say I don''t have root.
Let me see a screenshot of "Rootchecker"???
I am downloading an update that is 568.3 mb. GO GRAB IT!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Me too!
Manually went to update...
Update finally
AT LAST
Got it!!
5.1.1?
Pump your brakes
If this is the 5.1.1 update and you are rooted and enjoy a custom device. Please understand what this update means before flashing it.
http://forum.xda-developers.com/sprint-galaxy-s6-edge/help/dont-odin-5-1-1-t3136671
wildjeep said:
Pump your brakes
If this is the 5.1.1 update and you are rooted and enjoy a custom device. Please understand what this update means before flashing it.
http://forum.xda-developers.com/sprint-galaxy-s6-edge/help/dont-odin-5-1-1-t3136671
Click to expand...
Click to collapse
You are 100% correct my friend... I hate when people hurry up and jump on the update, then complain non stop they lost root and can't get it back....
Sent from my SM-G925V using Xparent Green Tapatalk 2
Soooperstar said:
5.1.1?
Click to expand...
Click to collapse
+1
If you upgrade to 5.1.1, you will not be able to root at this time
DO NOT ATTEMPT TO ROOT
I have been unsuccessful to go back to OE2 via odin, does someone have the recovery image for 5.1.1
If anyone has taken the update, please report back on whether TWRP and/or Cf autoroot works
Sent from my SM-G925P using Tapatalk
dhonzik said:
If you upgrade to 5.1.1, you will not be able to root at this time
DO NOT ATTEMPT TO ROOT
I have been unsuccessful to go back to OE2 via odin, does someone have the recovery image for 5.1.1
Click to expand...
Click to collapse
This is one of the compilations that has been warned for a few weeks now. It will take some time to achieve a stable Root/Recovery.
So if anyone is satisfied with stock. Unroot and flash away.
Or sit tight and wait for the custom development to catch up to the current stock software :highfive:
I will say, however, the device seems to run much smoother and early signs show battery improvement as well. Obviously it's early but it seems promising. Just wanted to share my stock experience as I chose to not root for the future payment platform
I updated but I am not root
no ram management .
If you take this update, you cannot root for the time being and certainly cannot Safe root (not tripping knox) with PingPoint root. In addition, you cant downgrade kernel, etc.
So the question becomes, what is the best course of action here. Can we PingPong root prior build, then update to OF7 kernel and rom once someone repacks them? Flash with FlashFire and maintain root? Then again, I guess we could accept the OTA and stay stock until CF-Auto Root is updated to work with it.
Either way, I'm holding for a bit here to see what shakes out...
UPDATE: thought about this a second. Sprint doesnt typically lock boot loader like AT&T, verizon. So this locked boot loader is whats preventing people from downgrading kernel once they update right? So this should not be an issue with Sprint if the boot loader is not locked?
Alpine- said:
If you take this update, you cannot root for the time being and certainly cannot Safe root (not tripping knox) with PingPoint root. In addition, you cant downgrade kernel, etc.
So the question becomes, what is the best course of action here. Can we PingPong root prior build, then update to OF7 kernel and rom once someone repacks them? Flash with FlashFire and maintain root? Then again, I guess we could accept the OTA and stay stock until CF-Auto Root is updated to work with it.
Either way, I'm holding for a bit here to see what shakes out...
UPDATE: thought about this a second. Sprint doesnt typically lock boot loader like AT&T, verizon. So this locked boot loader is whats preventing people from downgrading kernel once they update right? So this should not be an issue with Sprint if the boot loader is not locked?
Click to expand...
Click to collapse
Take a look at this thread: http://forum.xda-developers.com/sprint-galaxy-s6-edge/help/dont-odin-5-1-1-t3136671
It is not a looked boot loader that is the problem. T-Mobile solved it so I am sure it will be solved for us very soon.
wildjeep said:
This is one of the compilations that has been warned for a few weeks now. It will take some time to achieve a stable Root/Recovery.
So if anyone is satisfied with stock. Unroot and flash away.
Or sit tight and wait for the custom development to catch up to the current stock software :highfive:
Click to expand...
Click to collapse
Heads up the t-mobile TWRP recovery does get my bricked phone to the recovery, but the buttons do not work. If it did I had a backup I would have tried. Heading to the Sprint Store Tech Center to hopefully get a working phone or a replacement.
dhonzik said:
Heads up the t-mobile TWRP recovery does get my bricked phone to the recovery, but the buttons do not work. If it did I had a backup I would have tried. Heading to the Sprint Store Tech Center to hopefully get a working phone or a replacement.
Click to expand...
Click to collapse
So did the Sprint recovery not work?
How did you brick?
Sprint may not mess with it once the see the wrong recovery
Soooperstar said:
So did the Sprint recovery not work?
How did you brick?
Sprint may not mess with it once the see the wrong recovery
Click to expand...
Click to collapse
It was attempt to see if the CF Auto-Root would work after the update. I went back to other recovery that doesn't open up, if the tech center has the complete firmware maybe it will be to flash it back on. I opened a thread to see if someone can pull the stock recovery from the update. Trying to reflash back to OE2 fails.
dhonzik said:
It was attempt to see if the CF Auto-Root would work after the update. I went back to other recovery that doesn't open up, if the tech center has the complete firmware maybe it will be to flash it back on. I opened a thread to see if someone can pull the stock recovery from the update. Trying to reflash back to OE2 fails.
Click to expand...
Click to collapse
Did you try to Odin our twrp?
Soooperstar said:
Did you try to Odin our twrp?
Click to expand...
Click to collapse
Yes, it was a no go, $75 later I'll have a new phone in a week
I have the zip file if anyone has a way for me to get it posted here for devs to get to work on it.
chetqwerty said:
I have the zip file if anyone has a way for me to get it posted here for devs to get to work on it.
Click to expand...
Click to collapse
Upload it to android file host if you have dev status but if not you can upload it to google drive or any other hosting site.
EDIT: If you can get it uploaded somewhere, I'm sure @muniz_ri wouldn't mind looking at it and since it sounds like it prevents downgrading, we may be able to make a ROM out of it using the OD5 bootloader like what was done with the VZW S4 Lollipop update.
No not a dev, uploaded it to a free service http://www.fileconvoy.com/dfl.php?id=g71d4dc928ae33b36999687091905b660934562bab don't know why eset said it was unsafe, it downloaded fine when i allowed it. so just allow its fine.
Tried another service, FileDropper for those who have a problem
http://www.filedropper.com/update_3
ESET Antivirus didn't have a problem with this one
Shotty the first release @muniz_ri LOL
This is a OC4 to OE1 update.
timeToy said:
This is a OC4 to OE1 update.
Click to expand...
Click to collapse
Someone in another thread said they took the OTA and can't downgrage back to kikkat or lollipop via odin.
Sent from my SM-G900V using XDA Free mobile app
aholeinthewor1d said:
Someone in another thread said they took the OTA and can't downgrage back to kikkat or lollipop via odin.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
I personally have a Dev. Ed. S5, so I don't mind, as long as I don't flash the bootloader (aboot.mbn), so I am still interested in this.
It's been confirmed by muniz_ri that the qfuse counter was updated. If you update to OE1, there's no going back.
Guess i don't care about going back as long as i can have root and tether. I deleted the file from cache just have to get rid of this nagging install update message.
@Dudash
Here is the G900V_OE1_Stock_Rooted_ROM for testing.
For safety reasons it does not include any bootloader, however I expect that it will require the G900V_OD5_Bootloader in order to run.
Warning! Do not flash if you have taken the OE1 ota update and kept root. The ROM may work but there currently is no proven unbrick method, until the OE1 full .tar is available, in case something goes wrong.
Once the OE1 .tar is available we can try repackaging the NCG .tar without the bootloader as a way to downgrade/unbrick and re-root.
muniz_ri said:
@Dudash
Here is the G900V_OE1_Stock_Rooted_ROM for testing.
For safety reasons it does not include any bootloader, however I expect that it will require the G900V_OD5_Bootloader in order to run.
Warning! Do not flash if you have taken the OE1 ota update and kept root. The ROM may work but there currently is no proven unbrick method, until the OE1 full .tar is available, in case something goes wrong.
Once the OE1 .tar is available we can try repackaging the NCG .tar without the bootloader as a way to downgrade/unbrick and re-root.
Click to expand...
Click to collapse
Awesome. Downloading now.
muniz_ri said:
@Dudash
Here is the G900V_OE1_Stock_Rooted_ROM for testing.
For safety reasons it does not include any bootloader, however I expect that it will require the G900V_OD5_Bootloader in order to run.
Warning! Do not flash if you have taken the OE1 ota update and kept root. The ROM may work but there currently is no proven unbrick method, until the OE1 full .tar is available, in case something goes wrong.
Once the OE1 .tar is available we can try repackaging the NCG .tar without the bootloader as a way to downgrade/unbrick and re-root.
Click to expand...
Click to collapse
And here is a deodexed version for testing: G900V_OE1_Stock_Rooted_Deodexed_ROM
muniz_ri said:
And here is a deodexed version for testing: G900V_OE1_Stock_Rooted_Deodexed_ROM
Click to expand...
Click to collapse
I see that you say "if you've taken the ota and kept root" does that mean that you will retain root or is it hit or miss? any reports either way? also, have you done ay tweaks to this? enabled tether or anything besides deodexing? Thanks
I have a dev. ed. and it worked for me, including Advanced Calling, but I also flashed the rest of the firmware from the update file(sbl1.mbn sdi.mbn rpm.mbn and tz.mbn)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
awesome, Thanks !
muniz_ri said:
@Dudash
Here is the G900V_OE1_Stock_Rooted_ROM for testing.
For safety reasons it does not include any bootloader, however I expect that it will require the G900V_OD5_Bootloader in order to run.
Warning! Do not flash if you have taken the OE1 ota update and kept root. The ROM may work but there currently is no proven unbrick method, until the OE1 full .tar is available, in case something goes wrong.
Once the OE1 .tar is available we can try repackaging the NCG .tar without the bootloader as a way to downgrade/unbrick and re-root.
Click to expand...
Click to collapse
muniz_ri said:
And here is a deodexed version for testing: G900V_OE1_Stock_Rooted_Deodexed_ROM
Click to expand...
Click to collapse
Sorry it's taken so long to reply. I was at a party when I replied and downloaded the ROMs and didn't want to test them without having my computer in case of an Odin emergency. lol.
I'll be testing them shortly.
timeToy said:
I have a dev. ed. and it worked for me, including Advanced Calling, but I also flashed the rest of the firmware from the update file(sbl1.mbn sdi.mbn rpm.mbn and tz.mbn)
awesome, Thanks !
Click to expand...
Click to collapse
Thanks, which ROM did you test or both?
muniz_ri said:
Thanks, which ROM did you test or both?
Click to expand...
Click to collapse
I tried Odexed only, I'm not necessarily interested in deodexed until Xposed is more stable in Lollipop and TW. I also modified your script to avoid wiping. All good
timeToy said:
I tried Odexed only, I'm not necessarily interested in deodexed until Xposed is more stable in Lollipop and TW
Click to expand...
Click to collapse
Thanks, created new thread for the ROM's here: http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
---------- Post added at 11:56 PM ---------- Previous post was at 11:24 PM ----------
chetqwerty said:
I see that you say "if you've taken the ota and kept root" does that mean that you will retain root or is it hit or miss? any reports either way? also, have you done ay tweaks to this? enabled tether or anything besides deodexing? Thanks
Click to expand...
Click to collapse
After reviewing the ota zip I have confirmed that it checks for stock /bin/ddexe which is modified when a device is rooted, therefore the official OC4-to-OE1 ota will fail on all rooted devices. I have not seen an OD5-to-OE1 ota update.zip in order to review.
chetqwerty said:
Guess i don't care about going back as long as i can have root and tether. I deleted the file from cache just have to get rid of this nagging install update message.
Click to expand...
Click to collapse
Confirming, if I'm not rooted, there's no way to disable the annoying update nag? I'm on BOC4 and I can't use the phone without the stupid msg popping up!
I'm a bit of a noob, so apologies if this question has an obvious answer:
Does any of this thread mean there's now a way to downgrade or root a non-rooted OE1?
equazcion said:
I'm a bit of a noob, so apologies if this question has an obvious answer:
Does any of this thread mean there's now a way to downgrade or root a non-rooted OE1?
Click to expand...
Click to collapse
No
The latest root method for the Samsung Galaxy S7/S7E (AT&T/T-Mobile/Verizon/Sprint)
Does not void warranty and also does not trip the KNOX counter.
In order to remove root (un-root) you can flash the original firmware in Odin.
Also to answer any further questions the root does work on the latest T-Mobile update for the S7
(G930TUVU3APG1).
This root works on all Marshmallow versions on Android on the T-Mobile S7
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
method
Can you provide us a link to the method that you used to root the device. Also will you make a video tutorial for rooting the sm-g930t?
dantehalo said:
Can you provide us a link to the method that you used to root the device. Also will you make a video tutorial for rooting the sm-g930t?
Click to expand...
Click to collapse
Yes I am planning to make a video tutorial.
Also I used the method provided here (this is Max Lee's website)
And for now here is great video tutorial (also created by Max Lee) The Video
So, this works? I'm reading a lot of comments on the page you linked saying that users are having bootloop issues and issues across the board... Nothing I read in the comments section suggested ANYONE got this to work flawlessly. Are you on the T-Mobile variant of the S7? If so, can you post a video of your phone, with clear root and explain in depth your step by step procedure? I literally just got this phone and don't want to **** up a phone I'm paying on.
Thanks a bunch! All the files are downloaded and ready to go on my PC. Just waiting to confirm this will work.
revulv said:
So, this works? I'm reading a lot of comments on the page you linked saying that users are having bootloop issues and issues across the board... Nothing I read in the comments section suggested ANYONE got this to work flawlessly. Are you on the T-Mobile variant of the S7? If so, can you post a video of your phone, with clear root and explain in depth your step by step procedure? I literally just got this phone and don't want to **** up a phone I'm paying on.
Thanks a bunch! All the files are downloaded and ready to go on my PC. Just waiting to confirm this will work.
Click to expand...
Click to collapse
I apologize for replying so late ... Ive been busy. But this does work 100%, only a backup is required(before root because root will most likely put you in a bootloop and you have to factory reset after)... Hopefully my video will be out before July 30. But, before you root I also want you to be aware that the root uses an eng kernal which is not meant for daily use and causes lag, but you can optimize the phone to work as it did when it was stock.
Month later
Hi KillerClaw,
So it's been a month since your last post. Is this still preferred root for this device? My device encrypted storage upon setup wizard, don't know if i hit something or it did on own. Should I unencrypt before attempting root?
Thank you!
KillerClaw321 said:
I apologize for replying so late ... Ive been busy. But this does work 100%, only a backup is required(before root because root will most likely put you in a bootloop and you have to factory reset after)... Hopefully my video will be out before July 30. But, before you root I also want you to be aware that the root uses an eng kernal which is not meant for daily use and causes lag, but you can optimize the phone to work as it did when it was stock.
Click to expand...
Click to collapse
djdubyah said:
Hi KillerClaw,
So it's been a month since your last post. Is this still preferred root for this device? My device encrypted storage upon setup wizard, don't know if i hit something or it did on own. Should I unencrypt before attempting root?
Thank you!
Click to expand...
Click to collapse
It is the only root method so far. It is not required but you can unencrypt before rooting. Rooting while already encrypted won't cause any harm since /data is encrypted not /system . But I still recommend unencrypting so you don't run into any issues.
Does this work for the latest November 1st update APK1?
Hello, I too would like to know if this is still the current root method and if there have been any changes?
GeorgeNYer and kimber1982: The short answer is "no".
I did try this on my phone, and it acted like it worked (I could get the unlocked padlock with "custom") but I could never actually grant anything root access. That was when it was usable. The first round didn't get stuck in a bootloop. After I figured out that I didn't have root, I wiped the phone and started again, and again didn't get a boot loop, but did a factory reset anyway. After that point, it was too laggy to even try to use. I fought with it for a couple of hours trying to figure out a work around, but got fed up and DLed the APK1 stock firmware from Sammobile, and Odin'd the phone back to stock.
This is the first time I've used an non hacked phone since my iPhone 3G way back when. It feels really weird.
i cant root my sm9307
KillerClaw321 said:
The latest root method for the Samsung Galaxy S7/S7E (AT&T/T-Mobile/Verizon/Sprint)
Does not void warranty and also does not trip the KNOX counter.
In order to remove root (un-root) you can flash the original firmware in Odin.
Also to answer any further questions the root does work on the latest T-Mobile update for the S7
(G930TUVU3APG1).
Click to expand...
Click to collapse
i cant find any evidence that its even possible to root sm930t if there is somebody who can let me in on this big secret please indulge me
seattlestexan said:
GeorgeNYer and kimber1982: The short answer is "no".
I did try this on my phone, and it acted like it worked (I could get the unlocked padlock with "custom") but I could never actually grant anything root access. That was when it was usable. The first round didn't get stuck in a bootloop. After I figured out that I didn't have root, I wiped the phone and started again, and again didn't get a boot loop, but did a factory reset anyway. After that point, it was too laggy to even try to use. I fought with it for a couple of hours trying to figure out a work around, but got fed up and DLed the APK1 stock firmware from Sammobile, and Odin'd the phone back to stock.
This is the first time I've used an non hacked phone since my iPhone 3G way back when. It feels really weird.
Click to expand...
Click to collapse
Did the attempt trip your Knox counter?
GeorgeNYer said:
Did the attempt trip your Knox counter?
Click to expand...
Click to collapse
No, no Knox flags. Technically the engineer boot is official, even if done in a not so official way. Once I flashed back to stock APK1, it looks like it did right out of the box.
Sadly enough.
seattlestexan said:
No, no Knox flags. Technically the engineer boot is official, even if done in a not so official way. Once I flashed back to stock APK1, it looks like it did right out of the box.
Sadly enough.
Click to expand...
Click to collapse
Did you try everything in the video though?
https://youtu.be/GNInTlCpv8E
Sent from my SM-G930T using Tapatalk
---------- Post added at 09:55 PM ---------- Previous post was at 09:52 PM ----------
GeorgeNYer said:
Did you try everything in the video though?
https://youtu.be/GNInTlCpv8E
Sent from my SM-G930T using Tapatalk
Click to expand...
Click to collapse
I would try it myself but I'd hate to start over from scratch, I just wanna know if you tried all that is in the video, if not then I would try
Sent from my SM-G930T using Tapatalk
GeorgeNYer said:
Did you try everything in the video though?
https://youtu.be/GNInTlCpv8E
Sent from my SM-G930T using Tapatalk
Click to expand...
Click to collapse
What I listed is what I was able to do. I'm not certain it ever had root access. When it showed "custom" at boot, I couldn't grant anything root access. When it acted more laggy, like was described, the lag was so bad, it wasn't usable. Mind you, these instructions were written prior to the APK1 firmware that was on my G930T from new.
jveewee said:
i cant find any evidence that its even possible to root sm930t if there is somebody who can let me in on this big secret please indulge me
Click to expand...
Click to collapse
It's smg930t, just search smg930t root max lee
I can confirm that this method does indeed work. You need to be careful and follow the instructions, but it will root your device. You may notice lag after rooting. Just install a kernel tool and set it to on-demand.
troby86 said:
I can confirm that this method does indeed work. You need to be careful and follow the instructions, but it will root your device. You may notice lag after rooting. Just install a kernel tool and set it to on-demand.
Click to expand...
Click to collapse
And Knox counter wasn't tripped??
GeorgeNYer said:
And Knox counter wasn't tripped??
Click to expand...
Click to collapse
Nope.