Samsung just put out a new update and the oreo rooting method listed on here fails at odin. Im wanting to root because i found some interesting things in the phone info app under secret codes. one of them was unlock kernel and a few others i wanted to check out but it seems its blocked so i need root to bypass the block. anyone know of how root can be achieved in this new update? THANKS
bjf189 said:
Samsung just put out a new update and the oreo rooting method listed on here fails at odin. Im wanting to root because i found some interesting things in the phone info app under secret codes. one of them was unlock kernel and a few others i wanted to check out but it seems its blocked so i need root to bypass the block. anyone know of how root can be achieved in this new update? THANKS
Click to expand...
Click to collapse
They blocked root on that update so you are now stuck on a non rootable device. Sorry
stang5litre said:
They blocked root on that update so you are now stuck on a non rootable device. Sorry
Click to expand...
Click to collapse
It's fine. I was gonna be rooted only for a short time just to check those things out. It sucks not having root but I'd rather not deal with the lag from the boot image if it worked on this update that is. Maybe someone will crack this update in time cause nothings unhackable.
So is downgrading possible still or does this update block downgrading to? I haven't tried yet but if you have then save me some time
bjf189 said:
It's fine. I was gonna be rooted only for a short time just to check those things out. It sucks not having root but I'd rather not deal with the lag from the boot image if it worked on this update that is. Maybe someone will crack this update in time cause nothings unhackable.
So is downgrading possible still or does this update block downgrading to? I haven't tried yet but if you have then save me some time
Click to expand...
Click to collapse
Yes, blocks downgrading, but you should be able to flash any other updated carrier firmware and the U version
stang5litre said:
They blocked root on that update so you are now stuck on a non rootable device. Sorry
Click to expand...
Click to collapse
lvpre said:
Yes, blocks downgrading, but you should be able to flash any other updated carrier firmware and the U version
Click to expand...
Click to collapse
What difference would it make flashing other carrier firmware over this one?
bjf189 said:
What difference would it make flashing other carrier firmware over this one?
Click to expand...
Click to collapse
The U firmware would remove the Verizon bloatware. For example, if you left Verizon and went to T-Mobile...the U firmware of T-Mobile firmware could be installed to get the full bands for LTE coverage available. But if you are on Verizon and happy, probably not worth the trouble.
Related
New firmware T700ZSU1ANL1 and T800ZSU1ANL1 (Hong Kong both).*
Can i install these in europeans tablets?
Thanks
Any ideas?
I have installed it on the US WiFi only version, so I don't see it being a problem, if it doesn't install you can always Odin back to your stock rom... if you have a 3/4g type tablet then you may want to not flash it..... I'm digging the new kernel personally.
Itchiee said:
I have installed it on the US WiFi only version, so I don't see it being a problem, if it doesn't install you can always Odin back to your stock rom... if you have a 3/4g type tablet then you may want to not flash it..... I'm digging the new kernel personally.
Click to expand...
Click to collapse
Thanks
I have installed it in european firmware, portuguese one to be exact (FNAB), no issues at all.
Zootopia said:
I have installed it in european firmware, portuguese one to be exact (FNAB), no issues at all.
Click to expand...
Click to collapse
I installed, thanks, no issues.
Tavocampana said:
I installed, thanks, no issues.
Click to expand...
Click to collapse
Can anyone confirm that flashing update from a different region manually via Odin on an unrooted device will have exactly the same result as if it was an official OTA update (apart maybe from overwriting /data).
So there should be no problem getting OTA Lollipop when it eventually arrives? And apps which check if device is rooted like the banking and TV ones(Barclays, Sky Go etc) should be seeing 100% official unrooted OS?
Restorer said:
Can anyone confirm that flashing update from a different region manually via Odin on an unrooted device will have exactly the same result as if it was an official OTA update (apart maybe from overwriting /data).
So there should be no problem getting OTA Lollipop when it eventually arrives? And apps which check if device is rooted like the banking and TV ones(Barclays, Sky Go etc) should be seeing 100% official unrooted OS?
Click to expand...
Click to collapse
Theres an app calplled root cloak to hide root from apps. I dont really care on being on stock rom just to get ota lollipop. There would most liekly be a custom rooted lollipop rom when lollipop is out.
DUHAsianSKILLZ said:
Theres an app calped root cloak to hide root from apps. I dont really care on being on stock rom just to get ota lollipop. There would most liekly be a custom rooted lollipop rom when lollipop is out.
Click to expand...
Click to collapse
Unfortunately none of the cloaking apps work on Sky Go or Barclays and other banking apps. Neither does RootCloak or RootCloak Plus Xposed mods .
That is why I asked the question. Not really bothered if it just means losing OTAs - provided everything else is still 100% official unrooted after Odin upgrade of UK tab with HK firmware. That's why I ask will this be the case?
Restorer said:
Can anyone confirm that flashing update from a different region manually via Odin on an unrooted device will have exactly the same result as if it was an official OTA update (apart maybe from overwriting /data).
So there should be no problem getting OTA Lollipop when it eventually arrives? And apps which check if device is rooted like the banking and TV ones(Barclays, Sky Go etc) should be seeing 100% official unrooted OS?
Click to expand...
Click to collapse
I do not know.
My intention when the Lollipop version is released is to repeat the procedure and flash via Odin. I live in Argentina and here things come too late.
Tavocampana said:
I do not know.
My intention when the Lollipop version is released is to repeat the procedure and flash via Odin. I live in Argentina and here things come too late.
Click to expand...
Click to collapse
Yeah, I'd do that too. But these apps are too important to me to risk losing them so I will probably just chicken out and wait for the OTA. Thing is, if the update works, I can't see any reason why the root-checking apps would be able to tell except if they were spotting non-UK codes. I do know their checks are a lot more sophisticated than looking only for the presence of SU and busybox. They for sure examine parts of the kernel and the DRM files as well.
My logic tells me that if the apps don't work with the HK firmware then all I need do is to flash back to the official UK XXU1 version. That's why I am just asking is anyone knows of any other differences that might be exposed using the Odin method to update?
Hi,
i'm currently on firmware 51.1.3.0 and i got my FT just lying around here and want to use it.
So my question is, should i upgrade to the latest firmware and just use it or be patient until a root for my version is released because of the efuse stuff?
Is anyone working on a new root method atm?
Raptor270 said:
Hi,
i'm currently on firmware 51.1.3.0 and i got my FT just lying around here and want to use it.
So my question is, should i upgrade to the latest firmware and just use it or be patient until a root for my version is released because of the efuse stuff?
Is anyone working on a new root method atm?
Click to expand...
Click to collapse
I doubt anyone is working on rooting newer firmware, cause they already have their firmware rooted so I doubt they have interest in rooting the newer firmware. Not trying to speak for any devs that have worked on these devices, but that seems to be the way it goes, they have already accomplished their goal of rooting the device so if newer unrootable firmware gets released its not really a problem for them. I am predicting right now that unless a new firmware with major updates gets released that requires you to have stock firmware to update then no newer firmwares will ever get root. I could be wrong, but I doubt it so its really up to you.
porkenhimer said:
I doubt anyone is working on rooting newer firmware ...
Click to expand...
Click to collapse
I have no doubt somebody is working on it. These are self-challenged, self-motivated people. And Amazon threw down the gauntlet.
As to Raptor's first question, you have it. Why not use it?
cant block updates on my router and dont want to update past the fuse update... -.-
After taking the APH1 update on my phone, I can no longer downgrade to PG5, and I also can't flash the PG9 U firmware. I don't know what Samsung/Verizon did, but it's ridiculous.
I'm now stuck on the APH1 firmware and can't get on the U firmware at all.
I haven't tried rooting, but there is no Odin firmware for APH1 yet, so I'm not going to try until there is, so that if I mess up my phone I can fix it.
FoxyDrew said:
After taking the APH1 update on my phone, I can no longer downgrade to PG5, and I also can't flash the PG9 U firmware. I don't know what Samsung/Verizon did, but it's ridiculous.
I'm now stuck on the APH1 firmware and can't get on the U firmware at all.
I haven't tried rooting, but there is no Odin firmware for APH1 yet, so I'm not going to try until there is, so that if I mess up my phone I can fix it.
Click to expand...
Click to collapse
It probably incremented the bootloader. I upgraded to it because I am just losing interest in root all together. Somebody will chime in with a more technical explanation.
DarkMidnight said:
It probably incremented the bootloader. I upgraded to it because I am just losing interest in root all together. Somebody will chime in with a more technical explanation.
Click to expand...
Click to collapse
Agreed. For some reason I just don't really care about rooting the S7. Maybe I've just rooted too many phones and lost interest.
nynativ said:
Agreed. For some reason I just don't really care about rooting the S7. Maybe I've just rooted too many phones and lost interest.
Click to expand...
Click to collapse
For me a lot of it is this is not the most conventional root, not very stable for me and battery life suffered a lot compared to stock, and flashing U firmware has not been very cooperative for me.
So thoughts.... I am on the latest U firmware on my 930V. Should I consider flashing back to the stock Verizon rom? Everything is working great. I do plan on jumping ship from Verizon in the next year or so. I am blown away at how well this phone runs stock and only flashed the U in preparation to take it to another carrier afterwards. Is this a bad idea?
Tried to live with root, but the battery and stability was horrible. Now, I am using the engboot to do any data back up or restore tasks in TiBU then flashing the AP again to unroot. Data is maintained, but now I have to live with ads. I use adguard, by it feel like it hurts battery life. Will try and quantify that soon.
Being able to count on my phone to make a call and hold a charge is too important to me. Rooting the phone to set it up after a reset saves me time. Unfortunately, rooting with our current method is too prohibitive for daily use.
nynativ said:
Agreed. For some reason I just don't really care about rooting the S7. Maybe I've just rooted too many phones and lost interest.
Click to expand...
Click to collapse
Same here.
I have a 930U that I use on Verizon. I use the 930V firmware because I like having visual Voicemail. I have rooted 3 different times and gone back to stock everytime. I suppose it because of the engineering kernel but root with the S7 is just not stable. The battery life sucks and you have to do so many things to fix the lag it has just become not worth it. Also the 2 latest updates from Verizon have been good on battery. I do like not having Verizon logos all over my phone.
nrage23 said:
I have a 930U that I use on Verizon. I use the 930V firmware because I like having visual Voicemail. I have rooted 3 different times and gone back to stock everytime. I suppose it because of the engineering kernel but root with the S7 is just not stable. The battery life sucks and you have to do so many things to fix the lag it has just become not worth it. Also the 2 latest updates from Verizon have been good on battery. I do like not having Verizon logos all over my phone.
Click to expand...
Click to collapse
Give stang5liter rom a whirl. Been on it since it was released and have no issues besides nearby devices not working for me.
craazy82013 said:
Give stang5liter rom a whirl. Been on it since it was released and have no issues besides nearby devices not working for me.
Click to expand...
Click to collapse
Been using the same ROM for almost a week with xposed and everything is fine. I feel great without seeing the ads again. haha! BTW, I didn't try the nearby devices so no comment on that.
I have the G930V and am running APH1 with root no problems. The lag was horrendous but after changing the CPU governor to "interactive" on BOTH CPU's (little and BIG) it's been running smooth. I'll run like this for a bit... but stang5liter looks like it will be my next move.
Has anyone with ph1 tried flashing another rom such as stang5litre?
dBunny said:
I have the G930V and am running APH1 with root no problems. The lag was horrendous but after changing the CPU governor to "interactive" on BOTH CPU's (little and BIG) it's been running smooth. I'll run like this for a bit... but stang5liter looks like it will be my next move.
Click to expand...
Click to collapse
So how did you root if you can't downgrade like the OP stated?
craazy82013 said:
Has anyone with ph1 tried flashing another rom such as stang5litre?
Click to expand...
Click to collapse
Yes it works just fine.
bart77 said:
So how did you root if you can't downgrade like the OP stated?
Click to expand...
Click to collapse
PH1 doesn't break root. You just can't downgrade to older firmware's or flash any U firmware's. PH1 is still completely rootable.
So you can't Odin flash back to a stock image if you get in trouble or want to unroot. I guess I'll stay on PG5 for now.
I'm not rooted now, but was able to disable system update notifications using
https://play.google.com/store/apps/details?id=com.hecorat.packagedisabler
By disabling:
System updates (com.samsung.sdm)
System updates (com.samsung.sdmviewer)
and securitylogagent
FoxyDrew said:
PH1 doesn't break root. You just can't downgrade to older firmware's or flash any U firmware's. PH1 is still completely rootable.
Click to expand...
Click to collapse
Thanks @FoxyDrew for clarifying that... and I agree.
I used the following GUIDE to root APH1 on my S7 Flat: http://forum.xda-developers.com/verizon-s7-edge/how-to/verizon-root-knox-t3410624
Im somewhat confused. Your saying you cant downgrade from ph1. Are you talking only with odin? Reason i ask is stang5litre rom is APE1. And as was stated a few posts up, this rom can be flashed on rooted APH1. Which would take you back to APE1. Therefor downgradable? Any help is appreciated.
craazy82013 said:
Im somewhat confused. Your saying you cant downgrade from ph1. Are you talking only with odin? Reason i ask is stang5litre rom is APE1. And as was stated a few posts up, this rom can be flashed on rooted APH1. Which would take you back to APE1. Therefor downgradable? Any help is appreciated.
Click to expand...
Click to collapse
Ph1 upgrades the boot image therefore you cannot Odin flash back to stock pe1 which is the older boot image.
You can still root and flash stang5litre which is the pe1 rom, but you still have the ph1 boot image.
Sent from my VS987 using XDA-Developers mobile app
bart77 said:
Ph1 upgrades the boot image therefore you cannot Odin flash back to stock pe1 which is the older boot image.
You can still root and flash stang5litre which is the pe1 rom, but you still have the ph1 boot image. So if something goes wrong, you have no means of recovery back to stock since there is no ph1 stock Odin image.
Sent from my VS987 using XDA-Developers mobile app
Click to expand...
Click to collapse
The ph1 image is available at this link (http://updato.com/firmware-archive-select-model?record=78F84FCD811E11E69B2DFA163EE8F90B). I have flashed with these files and they work perfect.
Seems bootloader was uograded to version 3. So may be possible to flash between tmo and vzw and vice versa. Both now have v3 bootloader.
I just got another monthly update for my AT&T Note 5 labeled N920AUCS4CPL1 with the December 1, 2016 security patch included. I can't find anything else on this update but again, it looks like another security update - - NOT Android 7.0+
@mattern1974, did you take a screenshot or something? What does the about device screen say?
itskapil said:
@mattern1974, did you take a screenshot or something? What does the about device screen say?
Click to expand...
Click to collapse
Here you go!
Second screen shot
mattern1974 said:
Second screen shot
Click to expand...
Click to collapse
mattern1974 said:
Here you go!
Click to expand...
Click to collapse
Thanks man!
mattern1974 said:
Here you go!
Click to expand...
Click to collapse
How did you change your background
MusicHelps said:
How did you change your background
Click to expand...
Click to collapse
Themes in the settings.
Edit: I also use Nova Launcher since I like the speed and customization over the stock Touchjizz.
Can someone please post a link for adb push or odin files, so we can update our n920a as we are not in USA?
Thx.
Wow---this update is KILLING my battery. Google play services is running in the background like crazy. I've lost 10% in 2 HRS with little use where as before the update I would have lost 10% by 2 PM---UGH! Anyone else having this problem?
I updated to PK1 the day I got my phone (last week Monday).
The battery life for me has been superb (since I flashed through ODIN and started setting it up from scratch).
I want to get PL1 (for peace of mind), but I don't have an AT&T SIM card, so I'm waiting for a complete file that I can flash through ODIN.
I don't want anymore updates because I'm almost out of equipment contract now and I want to hack my Note 5. I wasn't aggressive about this until recently but somehow I had auto update on. So my phone started the download but I rebooted it and stuck it in the microwave.. (panic style) Then I tried to downgrade to 5.11 using the PH4 and the PH2 firmwares in succession but PH4 soft bricked me. Then I tried flashing N920AUCS4CPK1. and I got success. Wiped it all back to November 2016 security patch. (I dunno if this works after it installs, I have a sinking feeling it will not work.. There is no firmware available with Dec 2016 security patch that I'm aware so no way to recover if I'm correct in assuming the bootloader is blocking me from downgrades)
Edit: I want stress that fact that my phone never said Dec 2016 security patch, during all this it was still Nov 2016 patch
droidvoider said:
if I'm correct in assuming the bootloader is blocking me from downgrades)
Click to expand...
Click to collapse
With AT&T bootloaders, I thought that was always the case.
You WILL take the update when Nougat arrives. I'm eager to know when that will be. I have no intention of rooting my device to trip Knox.
batuhur said:
Can someone please post a link for adb push or odin files, so we can update our n920a as we are not in USA?
Thx.
Click to expand...
Click to collapse
Here S4CPK1 - to- S4CPL1 -
norbarb said:
Here S4CPK1 - to- S4CPL1 -
Click to expand...
Click to collapse
Thank you very much
Updating now
I find another update from S4CPL1 to S4CQA1 I think this is January security update but AT&T did not released yet. If someone whan to try it is ADB sideload or from sd-card. Remember if you go for it will erase your data. So backup your phone first.
norbarb said:
I find another update from S4CPL1 to S4CQA1 I think this is January security update but AT&T did not released yet. If someone whan to try it is ADB sideload or from sd-card. Remember if you go for it will erase your data. So backup your phone first.
Click to expand...
Click to collapse
Why don't you try it and let us know?
mattern1974 said:
Why don't you try it and let us know?
Click to expand...
Click to collapse
I don't have Note 5
It seems I'll have to wait unit the next big update is released. I have the N920A, but AT&T is not my carrier so I can't get that OTA. I'm currently on PK1. My device is stock and unrooted since I have no intention of tripping knox at the moment.
Anonymously_Unknown said:
My device is stock and unrooted since I have no intention of tripping knox at the moment.
Click to expand...
Click to collapse
With a locked bootloader, it will probably stay unrooted. I don't know of a root for it, would be nice if there was one. I think 5.01 bootlaoder got unlocked... But I keep looking...
Anonymously_Unknown said:
It seems I'll have to wait unit the next big update is released. I have the N920A, but AT&T is not my carrier so I can't get that OTA. I'm currently on PK1. My device is stock and unrooted since I have no intention of tripping knox at the moment.
Click to expand...
Click to collapse
Check the file to norbarb post, and send to your phone via ADB, you can search in google how can you send ota by adb, its easy. Send OTA via adb donesnt affect knox, its install manually OTA.
Hi. Im new here so please help me.
I have a Moto Z Play XT1635-02 on 7.0 with the 1st May Patch installed.
I unlocked the bootloader to root this device.
I rooted with this:
https://forum.xda-developers.com/moto-z-play/how-to/correct-rooting-moto-z-play-feb-17-t3560268
Now i want to go back to stock firmware to accept the OTA i just recieved for 7.1.1.
My main query is that, i have RETGB device and its on build number NPN25.137-24.3
I can't find any firmware for RETGB software channel.
I did find the OTA for this, which i have downloaded through the moto ota link generator tool by erfanoabdi.
Now, can any one guide me on how to restore stock without messing up my device?
I have downloaded two retail firmwares:
1)XT1635-02_ADDISON_7.0_NPNS25.137-24-1-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
2)XT1635-02_ADDISON_7.0_NPNS25.137-24-1-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Is it safe to flash any of these on my May patched device or should i somehow find the may patched firmware?
Waiting for your kind replies! :')
sheri.khan said:
Hi. Im new here so please help me.
I have a Moto Z Play XT1635-02 on 7.0 with the 1st May Patch installed.
I unlocked the bootloader to root this device.
I rooted with this:
https://forum.xda-developers.com/moto-z-play/how-to/correct-rooting-moto-z-play-feb-17-t3560268
Now i want to go back to stock firmware to accept the OTA i just recieved for 7.1.1.
My main query is that, i have RETGB device and its on build number NPN25.137-24.3
I can't find any firmware for RETGB software channel.
I did find the OTA for this, which i have downloaded through the moto ota link generator tool by erfanoabdi.
Now, can any one guide me on how to restore stock without messing up my device?
I have downloaded two retail firmwares:
1)XT1635-02_ADDISON_7.0_NPNS25.137-24-1-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
2)XT1635-02_ADDISON_7.0_NPNS25.137-24-1-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Is it safe to flash any of these on my May patched device or should i somehow find the may patched firmware?
Waiting for your kind replies! :')
Click to expand...
Click to collapse
Just flash the below link and you will be on 7.1.1, and yes it is that simple.
https://forum.xda-developers.com/moto-z-play/development/rom-single-dual-sim-t3620551
Jimi Mack said:
Just flash the below link and you will be on 7.1.1, and yes it is that simple.
https://forum.xda-developers.com/moto-z-play/development/rom-single-dual-sim-t3620551
Click to expand...
Click to collapse
Thank you!
I should flash this through TWRP?
Also after flashing this, the future OTA updates(If any) will be installed without any problems on my retgb channel?
sheri.khan said:
Thank you!
I should flash this through TWRP?
Also after flashing this, the future OTA updates(If any) will be installed without any problems on my retgb channel?
Click to expand...
Click to collapse
Yes on TWRP no on future updates.. being there is not official release for you. Plus the next major update if it happens would not be till O is released which we would not see till way after the new year.
Once you unlock bootloader and root, no going back...
Jimi Mack said:
Yes on TWRP no on future updates.. being there is not official release for you. Plus the next major update if it happens would not be till O is released which we would not see till way after the new year.
Once you unlock bootloader and root, no going back...
Click to expand...
Click to collapse
Thanks brother.
I don't seem to get why the RETGB firmware isn't released.
I literally can't find anyone except i guess two or just 3 people who have the same software channel.
Thanks again!
On the Verizon blackberry priv, there was a way to install the ROM with no Verizon bloatware, no rooting or anything.
Same with my T-Mobile s7 edge, is there something for the Verizon moto z play?
jzamalot said:
On the Verizon blackberry priv, there was a way to install the ROM with no Verizon bloatware, no rooting or anything.
Same with my T-Mobile s7 edge, is there something for the Verizon moto z play?
Click to expand...
Click to collapse
I don't think that its possible with the Verizon MZP.
There's no access for anyone to unlock its bootloader as of yet.
So there's no development for it either.
But who knows? Don't lose the hope! :'D
sheri.khan said:
I don't think that its possible with the Verizon MZP.
There's no access for anyone to unlock its bootloader as of yet.
So there's no development for it either.
But who knows? Don't lose the hope! :'D
Click to expand...
Click to collapse
Thanks, just wondering because the blackberry priv bootloader was also never unlocked or ever rooted