When i root my S7 Edge, how to get OTA updates?
Is there any page to download it?
You can't get ota updates with root, you have to go into the dev section and basically download a rom with the current updates already installed.
crack00r said:
When i root my S7 Edge, how to get OTA updates?
Is there any page to download it?
Click to expand...
Click to collapse
1. You can't get OTA updates if you are rooted.
2. You have to flash the correct firmware via ODIN if you are rooted. One page to download the firmwares is this ONE.
crack00r said:
When i root my S7 Edge, how to get OTA updates?
Is there any page to download it?
Click to expand...
Click to collapse
never trust an OTA update it will just patch your FW and in time your device will become too slow,I always used this site to download and install the latest full updates using Odin.
http://www.sammobile.com/firmwares/database/SM-G935F/
http://www.sammobile.com/firmwares/
I installed TRWP and rooted my S7 Edge. What happens if I download the new stock rom from sammobile.com and flash it using TWRP or ODIN? Will I loose all apps/settings and will the phone still be rooted?
hagba said:
never trust an OTA update it will just patch your FW and in time your device will become too slow,I always used this site to download and install the latest full updates using Odin.
http://www.sammobile.com/firmwares/database/SM-G935F/
http://www.sammobile.com/firmwares/
Click to expand...
Click to collapse
I don't understand this. Isn't OTA full updates and flashes firmware, ROM and everything to newest versions?
Sent from my A0001 using Tapatalk
MrMooselover said:
I installed TRWP and rooted my S7 Edge. What happens if I download the new stock rom from sammobile.com and flash it using TWRP or ODIN? Will I loose all apps/settings and will the phone still be rooted?
Click to expand...
Click to collapse
If somebody would like to answer this guy, I'd be the happiest.
I'm wondering the same thing. Though I get by with Titanium Backup for now (even though I don't trust it that much anymore, it just swallowed all my backups when I moved the files through the app, I had to reinstall evything by hand, and I lost most of my SMS/MMS).
Actually you can get OTA updates when you are rooted there is option in xTouchWiz Module when you have Xposed installed that changes the device status from Custom to Official and for me it worked and then i can install the update using flashfire. But i dont know if it works you too
jark99 said:
I don't understand this. Isn't OTA full updates and flashes firmware, ROM and everything to newest versions?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
OTA is a Over the air package.
Contains just the nessesery code to patch the current firmware.
You cannot flash a OTA, Simple.
What you can do, is what others have advised. Download the full Firmware and flash away.
There is two ways to do this. Flash everything and have the device wipe all data.
Flash the necessary files for odin with a patched csc file (This will avoid any data being wiped)
Second method:
Flashfire.
You can download the whole firmware package from Sammy (Link the guys posted above)
Then use flashfire to flash these packages straight on the device.
You will retain all Data and Settings etc. You can also replace bootloader
and then flash TWRP again after.
(If i have used flashfire since i have had the device. I have updated Dirty (Dirty is when i dont wipe and keep all Data)
I have done this around 5 times, and noticed my device starting to become slow at responding.
Today i installed the latest Firmware with a Full wipe. (Its advisable once in a while)
Iradj said:
Actually you can get OTA updates when you are rooted there is option in xTouchWiz Module when you have Xposed installed that changes the device status from Custom to Official and for me it worked and then i can install the update using flashfire. But i dont know if it works you too
Click to expand...
Click to collapse
Can you explain how you did it i have all installed flashfire, xtouchwiz, ota how do i flash it where is the file?
tonyafc said:
Can you explain how you did it i have all installed flashfire, xtouchwiz, ota how do i flash it where is the file?
Click to expand...
Click to collapse
Its Simple in XTouchWiz go to Security Hacks and then tick the Box "Fake System Status" Now close XTouchWiz and go to Settings and Status, now it should be Official and Thats it. You can download your OTAs but obviously you can't install it, Open Flashfire go to Flash Zip or OTA.... Done.
{
"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"
}
Your OTAs should be saved in DATA -> FOTA
Iradj said:
Its Simple in XTouchWiz go to Security Hacks and then tick the Box "Fake System Status" Now close XTouchWiz and go to Settings and Status, now it should be Official and Thats it. You can download your OTAs but obviously you can't install it, Open Flashfire go to Flash Zip or OTA.... Done.
Your OTAs should be saved in DATA -> FOTA
Click to expand...
Click to collapse
Thanks for replying done all above couldn't locate the file in data but found it in cache but the file has corupted in brackets?
tonyafc said:
Thanks for replying done all above couldn't locate the file in data but found it in cache but the file has corupted in brackets?
Click to expand...
Click to collapse
Yeah, I tested it myself and there is now chance to flash the update.zip from the fota folder. It did what is recommended: Just flash the whole firmware with the home_csc.
GerasVille said:
Yeah, I tested it myself and there is now chance to flash the update.zip from the fota folder. It did what is recommended: Just flash the whole firmware with the home_csc.
Click to expand...
Click to collapse
I did that with the last update i got it from sammobile but it wiped my phone
tonyafc said:
I did that with the last update i got it from sammobile but it wiped my phone
Click to expand...
Click to collapse
Really? Even with the home_csc file? Did the device ask you for a pin or something or did it just a wipe after flashing?
GerasVille said:
Really? Even with the home_csc file? Did the device ask you for a pin or something or did it just a wipe after flashing?
Click to expand...
Click to collapse
No pin i downloaded file from sammobile and got 6 files using odin i put them all in labelled boxes and it wiped my phone there was another csc file
TWRP (NO ROOT) and Official Firmware with OTA updates possible (S7 EDGE 935FD)
Hey, If I am posting here irrelevant, please guide me to the best Thread where I should post it.
I recently installed Resurrection Remix rom on s7 edge. Them ram was good, however, camera wasn't working with stock rom as well as open camera and candy camera apps. It was just showing blank screen when I open any camera app. I reinstalled the stock rom via Smart Switch.
I require a few solutions:
1. How can I get my camera working with Resurrection Remix? Is there anyone who had the same problem?
2. Can I install TWRP to have custom recovery with official rom? And while having TWRP (without root), would I be able to have OTA?
3. How can I use smart switch backup via any other app or software to get it into my phone (which is installed with custom rom) because custom rom do not catch smart switch.
Thanks!
crack00r said:
When i root my S7 Edge, how to get OTA updates?
Is there any page to download it?
Click to expand...
Click to collapse
Give it a try
https://forum.xda-developers.com/ga...dates-root-t3837898/post77519099#post77519099
Related
Here's the new update that came out today - XNPH25R. This has the assert junk removed so you can flash it in TWRP.
NOTHING has been changed in this other than the ability to flash it in TWRP.
Reboot to recovery, flash .zip. Reboot to system. Nothing fancy required. *Flash SuperSU if you want root access.
https://www.4shared.com/download/4UoLVwKIce/cm-bacon-XNPH25R_fix.zip?lgfp=3000
I'm getting binary update script error by flashing with TWRP
I flashed the stock OTA in TWRP right from my phone. Go to Developer settings adn uncheck the update CM recovery setting and OTA will flash in TWRP. I kept root. I'm not sure if the 4.4 update will kill root, but I doubt it. Thanks for providing the zip!
With the option to update CM recovery via OTAs does that mean we can take OTAs with TWRP installed?
Hey Guys Can I flash this zip file through CWM ???? Please suggest...........
Update = flashed the official cm-11.0-XNPH22R-bacon-signed file & then received the OTA & it's installed successfully even with CWM install.
iamacronym said:
With the option to update CM recovery via OTAs does that mean we can take OTAs with TWRP installed?
Click to expand...
Click to collapse
I think you have to disable that option in developer settings menu, if you want to be able to flash the OTA with TWRP.
Works for me
Updated it using TWRP but once booted it tells me there's an udpate, over and over... update in TWRP seems to work (no fails, only message is "radio image updated")
I flashed the file and when I reboot i´m still on XNPH22R and it also does prompt for the update. I flashed it on twrp, everything seemed ok
Flashed the file with both TWRP and Philz, no error but the Rom version is still 22R !
Can someone post the stock recovery img please?
ToRvaLDs said:
Flashed the file with both TWRP and Philz, no error but the Rom version is still 22R !
Can someone post the stock recovery img please?
Click to expand...
Click to collapse
Yeah I get the same issue where it shows as the flashing being successful,but reboots back to 22R.
housry23 said:
I flashed the stock OTA in TWRP right from my phone. Go to Developer settings adn uncheck the update CM recovery setting and OTA will flash in TWRP. I kept root. I'm not sure if the 4.4 update will kill root, but I doubt it. Thanks for providing the zip!
Click to expand...
Click to collapse
Which folder was the OTA located in? Is it the cache one at root level?
Sent from N5 or OPO
truckroot said:
Which folder was the OTA located in? Is it the cache one?
Sent from N5 or OPO
Click to expand...
Click to collapse
I couldn't tell you. I got a notification that an update was available, tapped install and it booted into twrp and installed the update. I had to reinstall xposed but kept root and twrp.
Sent from my OnePlus One
housry23 said:
I couldn't tell you. I got a notification that an update was available, tapped install and it booted into twrp and installed the update. I had to reinstall xposed but kept root and twrp.
Sent from my OnePlus One
Click to expand...
Click to collapse
OK thx. Wasn't sure if u had to navigate to a certain folder when twrp booted up. Stock OTAs in a custom recovery is new territory for me.
Sent from N5 or OPO
truckroot said:
OK thx. Wasn't sure if u had to navigate to a certain folder when twrp booted up. Stock OTAs in a custom recovery is new territory for me.
Sent from N5 or OPO
Click to expand...
Click to collapse
I would say it's new territory for all of us. I do have the option to update cm recovery unchecked in developer settings.
Sent from my OnePlus One
housry23 said:
I would say it's new territory for all of us. I do have the option to update cm recovery unchecked in developer settings.
Sent from my OnePlus One
Click to expand...
Click to collapse
True. I have that unchecked and also had the system update apk frozen just out of habit.
Leave it to CM to allow OTAs to be installed thru twrp/cwm. Living this phone more and more each day.
Sent from N5 or OPO
Is it supposed to be about 23.55 mb only? Everytime i flash nothing changes...
Sent from my One using XDA Free mobile app
truckroot said:
Which folder was the OTA located in? Is it the cache one at root level?
Sent from N5 or OPO
Click to expand...
Click to collapse
The downloaded OTA is located in \cache and can be flashed trough TWPR. Unfortunately I get an error of missing apks in \system due to deleting some of them (CM File Manager, PrintSpooler, ...).
I'll try to throw them back to \system and retry flashing.
Nope nope nope, doesn't work. He says blabla build.prop because of changed DPI, but it gave me an error on executing the update binary anyway.
{
"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"
}
This is what happens when you try to flash the original OTA .zip in TWRP. When flashing the provided zip in OP I don't get an error but like everybody said it doesn't update to 25.
fiz:ik said:
Nope nope nope, doesn't work. He says blabla build.prop because of changed DPI, but it gave me an error on executing the update binary anyway.
Click to expand...
Click to collapse
Someone has the original build.prop? We can try to restore it and update.
ToRvaLDs said:
Someone has the original build.prop? We can try to restore it and update.
Click to expand...
Click to collapse
I've got it. Do you need? Texdroider DPI makes an backup of the original build.prop. I restored it and the issue is solved but nevertheless the update binary can't be executed.
Flashed CWM over TWRP: with CWM same problem. I restored original build.prop and it's still complaining about in the build prop.
Okay, seems that my backup of build.prop isn't the stock build.prop but an updated version with DPI of 380, damn. Can anyone upload the original one?
Can you upload the original build.prop please? Are you sure that the old file has the correct cm revision?
Inviato dal mio One utilizzando Tapatalk
I just happened to do a software check, and it is downloading a new version. Any ideas? I was already on Lollipop.
Milkman00 said:
I just happened to do a software check, and it is downloading a new version. Any ideas? I was already on Lollipop.
Click to expand...
Click to collapse
More than likely security update for stagefright vulnerability. S5 got theirs a week or so ago.
pre4speed said:
More than likely security update for stagefright vulnerability. S5 got theirs a week or so ago.
Click to expand...
Click to collapse
400 megs for Stagefright? That seems pretty big.
OC2
{
"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"
}
Milkman00 said:
400 megs for Stagefright? That seems pretty big.
Click to expand...
Click to collapse
Yeah it was 380 for the S5 too.
Thanks for the info. This was the only site that had ANY information about the update.
I'm on Lollipop, but Rooted. Will this update take away root by any chance?
My question exactly!
sibenj said:
I'm on Lollipop, but Rooted. Will this update take away root by any chance?
Click to expand...
Click to collapse
Typically these updates do remove root. Best to wait until someone has a root method figured out for the new update.
sibenj said:
I'm on Lollipop, but Rooted. Will this update take away root by any chance?
Click to expand...
Click to collapse
I just updated via the OTA method on AT&T. Rebooted twice. I still have root (verified by Root Checker). Here's my About page:
Here's the root checker pic:
I now have OC2. Update OTA with confidence!
I originally rooted OC1 (Lollipop) by following the Root/OC1 method.
EDIT: I just checked for stagefright vulnerability (via Stagefright detector). It reports that my device is NOT VULNERABLE. Nice.
I took the chance because this site has helped me in sooo many ways. It's the least I could do. Thanks everyone.
I'm rooted and my update failed at 26%
Sent from my SAMSUNG-SM-N900A using Tapatalk
Update failed for me at 25% too. I'm rooted OC1.
Does this update do more than just fix the stagefright exploit?
If not, then kmokhtar already posted a flashable update fix for stagefright which works great.
Could you post a link to that? I have been unable to find it via xda search, google search, browsing in note 3 forums...
Why is this 'update' 5.0? I could have sworn it was just up to 5.1.1
KestrelX said:
Could you post a link to that? I have been unable to find it via xda search, google search, browsing in note 3 forums...
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...stagefright-vulnerability-fix-note-3-t3175087
Can confirm that the update worked for me on rooted OC1, now shows OC2 and I retained full root on my phone.
ATT Ota file
https://mega.nz/#!TdE02KwJ!m4pkNivN9q2ZB7hGuXFiq872UoB8D-F-QpiPVX4sWI0
mine worked I am still rooted no problems no failure
peterson65 said:
mine worked I am still rooted no problems no failure
Click to expand...
Click to collapse
Those like me who have installed modded apps like S6 and have mixed in deodexed files, the OTA will fail. the OTA installer MD5 checks the system files and if any fail it will abort the Update. Any deodexed system files will also abort the Update
How to updated to OC2 if your OTA failed
1. Download and unzip and copy this Folder to OC1 stock root backup to your TWRP backup folder,
\TWRP\BACKUPS\0b70b440\N900A_OC1_Lollipop_Stock_Rooted_Backup
2. Copy OC1 kernel recovery installer to your sdcard SM-N900A_N900AUCUEOC1_KERNEL_Recovery-Flashable.zip
*** You can also go ahead and copy Safestrap-HLTEATT-NC2-3.75-B03[1].apk and NC2 Flasher to your sdcard ***
3 Download the OC2 OTA 2400258.cfg
rename the 2400258.cfg OC2 to 2400258.zip and copy to your sdcard
4 Install the OC1 backup,
N900A_OC1_Lollipop_Stock_Rooted_Backup.zip
5. Install OC1 Kernel
SM-N900A_N900AUCUEOC1_KERNEL_Recovery-Flashable.zip
6. (I did a factory wipe , but Warning you will loose UserData settings and Apps you installed) You might try without but if you had a custom SystemUI and Touchwiz as I did it might FC because you have setting in Userdata pertaining to the Custom apps that you will over write with the OC1 backup.
7. Select Reboot and then select Recovery to boot to stock recovery and install as a update from external storage. mine installed with no issues.
8. To get safe strap back working Download and copy Safestrap-HLTEATT-NC2-3.75-B03[1].apk to sdcard (if you have not done yet)
9. Download and copy NC2 Flasher by benwaffle
10. Install Safestrap-HLTEATT-NC2-3.75-B03, run app and install recovery ( do not press reboot to recovery, it will only take you to stock recovery)
11. Install NC2 Flasher app and then use it to boot to recovery.
12. Do a backup of your new OC2
Now you can customized and do what you want
Small update to build SU4TL-49. Not Marshmallow. Claims "security patches and improved network performance."
How to Update with an Unlocked Bootloader
The update will only work if you have a 100% unmodified stock rom and recovery menu. If you're on CF's rom and you want to update to the latest version of that, see his page for details on how to do that.
1. Backup all data. Just in case. Definitely do this if you're coming from CM13 or RR. I don't remember if the OTA wipes your data or not.
2. Download this SU4TL-44 100% stock flashable zip here: http://forum.xda-developers.com/droid-turbo/development/rom-su4tl-44-100-stock-t3320815
3. Download the SU4TL-44 stock recovery menu here: https://mega.nz/#!L1AkQD4T!qoZIlLa-wuUBLMEi_gE574meiHd6Pehb34a-x3Gb-V8
4. Boot into TWRP.
5. Flash the file you downloaded in step 2 by selecting Install and browsing to the file.
6. In TWRP, select Install, followed by install image, and select the recovery image that you downloaded in step 3. Tell it to flash it to recovery, and flash it.
7. If you're coming from CM13 or RR, do a factory reset in TWRP. If you're coming from a modified stock rom, I still recommend this, but it's not mandatory.
8. Reboot to recovery to confirm that you see the stock recovery menu (a dead android with the words "no command").
9. Boot the phone normally.
10. The OTA update should appear. Take it and let it do its thing.
You now have a 100% stock, bootloader still unlocked, SU4TL-49 phone. If you want TWRP back so you can start flashing stuff again, keep reading.
11. Download and install Sunshine from here: http://theroot.ninja/
12. Download your preferred version of TWRP. The current stable version is here: https://dl.twrp.me/quark/. If you want baybutcher27's modded version that includes lots of handy additional features, you can get that here: http://forum.xda-developers.com/showpost.php?p=66877208&postcount=116
13. Download Flashify from the play store.
14. Open Sunshine and follow the instructions until it gains temp root. Disregard the message that says it isn't compatible with SU4TL-49.
15. Open Flashify, select Recovery Image, then browse to the version of TWRP that you downloaded in step 11. Flash it.
16. Reboot to recovery. You should see TWRP's lovely smiling face staring back at you.
How to Install the SU4TL-49 Modem Only
1. [HIGHLY RECOMMENDED] Flash the modded TWRP I mentioned earlier, select backup, backup only your modem.
2. Flash Computerfreek274's modem package that you can get here: https://www.androidfilehost.com/?fid=24545070682210570
3. If you have GPS or other modem-related issues, try flashing this to fix them: https://www.androidfilehost.com/?fid=24531035584725320
4. If you decide you don't like the new modem, restore the backup you made in step 1.
Troubleshooting
Issue: You followed all of the steps, but you still get an error when you try to take the OTA.
Solution: Backup your data and perform a factory reset using the stock recovery menu. You can do this by rebooting to recovery like you do when you want to boot TWRP, and when you see the "no command" screen, hold the power button and press volume up. Then select factory reset and do it.
silly question.
I am with bootloader unlocked and rooted, with stock rom.
My XT1254 show that an update is available .xxxx.49
May I update the smartphone, by itself (no TWRP, that I have installed )
Will it relock my bootloader?
lukappaseidue said:
silly question.
I am with bootloader unlocked and rooted, with stock rom.
My XT1254 show that an update is available .xxxx.49
May I update the smartphone, by itself (no TWRP, that I have installed )
Will it relock my bootloader?
Click to expand...
Click to collapse
He just said it won't lock your bootloader
lukappaseidue said:
silly question.
I am with bootloader unlocked and rooted, with stock rom.
My XT1254 show that an update is available .xxxx.49
May I update the smartphone, by itself (no TWRP, that I have installed )
Will it relock my bootloader?
Click to expand...
Click to collapse
Taking the update is perfectly safe as long as you are unlocked. However, if you are rooted, the update will fail. You must first flash a completely unmodified stock rom.
This will take you back to full stock: http://forum.xda-developers.com/droid-turbo/development/rom-su4tl-44-100-stock-t3320815
Thank you. I think it is worth waiting for MM, or full updated rom
grazie
Original Motorola DROID Turbo receives a security update from Verizon
http://www.phonearena.com/news/Orig...ceives-a-security-update-from-Verizon_id81089
Original Motorola DROID Turbo receives a security update from Verizon
3 May 2016, 18:19, by Alan F.
We hate to take all of the fun out of your life, but if you happen to own the Motorola DROID Turbo and you receive the update from Verizon that is heading your way, the phone is not receiving Android 6.0. Better that we shoot down all hopes now before you start believing that the new files contain the latest Android build.
The update brings the latest Android security software to the DROID Turbo and it also adds improvements to call performance. Just because this is the OG Turbo doesn't make it totally irrelevant. Verizon still offers the device as a mid-range handset priced at $480.
Verizon suggests that after receiving the notification that your Turbo has received the update, you make sure that the phone is connected to a Wi-Fi network or a strong Verizon cellular signal before starting the updating process. Also, your battery should be fully charged before you start the update.
On Motorola's support page, it says that the Motorola DROID Turbo is still slated to receive Android 6.0 "pending partner support." Which means that if you still own this phone, you need to keep pushing Verizon to support an update to Android 6.0.
Click to expand...
Click to collapse
Whose done this and any difference?
Sent from my XT1254 using XDA-Developers mobile app
This update appeared to have disabled VoLTE.
molanjami said:
This update appeared to have disabled VoLTE.
Click to expand...
Click to collapse
VoLTE still working fine for me.
Sent from my XT1254 using XDA-Developers mobile app
Haha maybe they finally properly patched stagefright. Someone should check that.
My guess is security patch = patched exploit that sunshine uses, mayyyybe patched stagefright if Moto could be bothered to find a dev with absolutely nothing else to do.
Did a restore of the modem backup provided, rebooted phone and everything working as it should. sadly didnt improve my signal any, but thats what happens living in the boonies.
Flashed it on Resurrection Remix 5.6.8 05/08 build
It went fine for me but I backed up my SU44 Modem to be safe, and I wanna remind everyone to do the same, its always wise to be safe
TheSt33v said:
Haha maybe they finally properly patched stagefright. Someone should check that.
My guess is security patch = patched exploit that sunshine uses, mayyyybe patched stagefright if Moto could be bothered to find a dev with absolutely nothing else to do.
Click to expand...
Click to collapse
I ran Stagefright Detector after the update and it reported CVE-2015-6602 as a vulnerability.
Sent from my Droid Turbo using Tapatalk
helobubba88 said:
I ran Stagefright Detector after the update and it reported CVE-2015-6602 as a vulnerability.
Click to expand...
Click to collapse
Wow. Now that's lazy.
TheSt33v said:
Haha maybe they finally properly patched stagefright. Someone should check that.
My guess is security patch = patched exploit that sunshine uses, mayyyybe patched stagefright if Moto could be bothered to find a dev with absolutely nothing else to do.
Click to expand...
Click to collapse
{
"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"
}
Sent from my XT1254 using XDA-Developers mobile app
Nitefire77 said:
Did a restore of the modem backup provided, rebooted phone and everything working as it should. sadly didnt improve my signal any, but thats what happens living in the boonies.
Flashed it on Resurrection Remix 5.6.8 05/08 build
It went fine for me but I backed up my SU44 Modem to be safe, and I wanna remind everyone to do the same, its always wise to be safe
Click to expand...
Click to collapse
did you just flash the zip with the modded twrp or is there a special procedure. mine keeps failing
quantum tao said:
did you just flash the zip with the modded twrp or is there a special procedure. mine keeps failing
Click to expand...
Click to collapse
Extract the zip to /sdcard/TWRP/backups/[your phone's serial number]. Then boot twrp, select restore, and restore the backup.
quantum tao said:
did you just flash the zip with the modded twrp or is there a special procedure. mine keeps failing
Click to expand...
Click to collapse
^What St33vo said. Just restore modem from the extracted zip in your twrp folder. Keep it in the Sut49 folder once unzipped so you can select it under restore.
You don't need to wipe caches or anything. Just restore and reboot
TheSt33v said:
Extract the zip to /sdcard/TWRP/backups/[your phone's serial number]. Then boot twrp, select restore, and restore the backup.
Click to expand...
Click to collapse
Nitefire77 said:
^What St33vo said. Just restore modem from the extracted zip in your twrp folder. Keep it in the Sut49 folder once unzipped so you can select it under restore.
You don't need to wipe caches or anything. Just restore and reboot
Click to expand...
Click to collapse
thanks, that worked. i guess i'm too tired to do simple file operations. i thought it was an installable zip.
lukappaseidue said:
Thank you. I think it is worth waiting for MM, or full updated rom
grazie
Click to expand...
Click to collapse
Seen VZ update the razr hd to close a unlock and never released another update again. Still hoping this is not the case.
BBB
add two
Sent from my XT1254 using Tapatalk
realbbb said:
Seen VZ update the razr hd to close a unlock and never released another update again. Still hoping this is not the case.
BBB
add two
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Well very shortly before this update was released, people were talking about getting soak test invites. If the soak test was for this update, that's the shortest soak test in human history, and why would you need a soak test for such a tiny update? I'm still hopeful that we'll see a marshmallow soak leak relatively soon.
I just got a 250 MBs update on my galaxy note 4 N910t.
{
"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"
}
Sent from my SM-N910T using Tapatalk
http://www.sammobile.com/2016/10/23...nance-update-for-the-galaxy-note-4-in-europe/
I took the plunge. It's a lot less buggy and battery drain is not near as bad. I almost sold this thing.
Rootable?
Cf auto root?
Sent from my SM-N910T using Tapatalk
ubigred said:
Rootable?
Cf auto root?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Systemless root works fine for me.
Uploading the tar to AFH will update the other thread.
DeeXii said:
Uploading the tar to AFH will update the other thread.
Click to expand...
Click to collapse
did u upload Oct MM security patch firmware upfate I wanna flash it on my t910w8 Canadian.....waiting for it thanks
MDHACK said:
Systemless root works fine for me.
Click to expand...
Click to collapse
Would you please give a quick description of the process/tools you used to accomplish this so that others may duplicate your success?
Also, what recovery are you using?
Thank you.
Fat Rat Bastard said:
Would you please give a quick description of the process/tools you used to accomplish this so that others may duplicate your success?
Also, what recovery are you using?
Thank you.
Click to expand...
Click to collapse
1. Update through OTA or flash Odin files.
2. Flash TWRP through Odin.
3. Flash latest Chainfire's SuperSu Systemless root on TWRP.
4. Enjoy!
https://www.androidfilehost.com/?fid=385035244224387215
Has anyone ever updated while they had an app like EZ Package Disabler installed with the apps disabled? I updated this morning and forgot to enable the apps before the update. It's working fine right now, just wondering if there would be a problem since the app says to enable apps before doing an update.
I just tried to flash TWRP using Odin. After restarting the phone, I went to android recovery mode instead of TWRP. What did I do wrong there? Please help!
buidoitieutu said:
I just tried to flash TWRP using Odin. After restarting the phone, I went to android recovery mode instead of TWRP. What did I do wrong there? Please help!
Click to expand...
Click to collapse
After flashing twrp dont let the device reboot. The stock recover overwrites twrp. In odin uncheck reboot then after the twrp install you have to boot to recovery Vol+ home and power..
buidoitieutu said:
I just tried to flash TWRP using Odin. After restarting the phone, I went to android recovery mode instead of TWRP. What did I do wrong there? Please help!
Click to expand...
Click to collapse
In Odin, visit Options tab, and uncheck Auto Reboot before Starting.
j21098 said:
Has anyone ever updated while they had an app like EZ Package Disabler installed with the apps disabled? I updated this morning and forgot to enable the apps before the update. It's working fine right now, just wondering if there would be a problem since the app says to enable apps before doing an update.
Click to expand...
Click to collapse
I freeze my apps using Titanium Backup, and I have never activated them before an update
Hi everyone, I installed this and issue arised, my system settings went to default rather than my customized settings.
But started to realize that my quick charge isn't working anymore (at least doesn't show a notification saying the fast charge is connected) and also no more vibrations for my touch light keys (back and switching apps buttons) when I touch them.
Pretty annoying, anyone has these issues and know how to fix these? Thanks
MDHACK said:
1. Update through OTA or flash Odin files.
2. Flash TWRP through Odin.
3. Flash latest Chainfire's SuperSu Systemless root on TWRP.
4. Enjoy!
Click to expand...
Click to collapse
I am using same firmware, but can't seems to root it using Systemless root on TWRP and Auto CF root... Any step by step guide on how you did it?
Anyone who has Android 6 on the N910T, could you please see if they have the language PORTUGUESE BRAZIL?
I cant get an 'adb shell' on the device. It says "error: device unauthorized. Please check the confirmation dialog on your device"
When I go to about phone in my settings then update, I get a message that says IN2025_11.C.11 is ready to be downloaded and installed. When I click download and install it fills up the bar about 10% then crashes and says it was unable to be installed. Anyone have any advice or the update I can download to take care of it locally?
{
"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 installed it on mine today. So far so good, but I haven't been using it a bunch.
mkennedy455 said:
I installed it on mine today. So far so good, but I haven't been using it a bunch.
Click to expand...
Click to collapse
Did yours update normally? Did you have to local upgrade?
I just did the ota through system update in settings.. I read on here that there was an update so I manually checked and it showed up so installed it and it worked I was on open beta 1 Android 12 not rooted used incremental update. I used oxygen updater to install the beta I was on before. I'm a little confused because I thought I had to factory reset to go back to stable builds. Is this actually a stable build now or is it still a beta?
mkennedy455 said:
I just did the ota through system update in settings.. I read on here that there was an update so I manually checked and it showed up so installed it and it worked I was on open beta 1 Android 12 not rooted used incremental update. I used oxygen updater to install the beta I was on before. I'm a little confused because I thought I had to factory reset to go back to stable builds. Is this actually a stable build now or is it still a beta? View attachment 5565839
Click to expand...
Click to collapse
As far as I know its a stable but its only being rolled out to the beta users at the moment. I could be wrong
mkennedy455 said:
I just did the ota through system update in settings.. I read on here that there was an update so I manually checked and it showed up so installed it and it worked I was on open beta 1 Android 12 not rooted used incremental update. I used oxygen updater to install the beta I was on before. I'm a little confused because I thought I had to factory reset to go back to stable builds. Is this actually a stable build now or is it still a beta? View attachment 5565839
Click to expand...
Click to collapse
Idk why mine wont let me update through updates even tho it shows it there
it simply because you're rooted.. it's already known from a long time.
there're 2 way if you wanna update from OTA:
1. simple uninstall magisk, and restore image. then do update. then back install magisk again
2. localupdate again C.10 and because you're now lose root, then you should be able to update fine
dewa5227 said:
it simply because you're rooted.. it's already known from a long time.
there're 2 way if you wanna update from OTA:
1. simple uninstall magisk, and restore image. then do update. then back install magisk again
2. localupdate again C.10 and because you're now lose root, then you should be able to update fine
Click to expand...
Click to collapse
Oh alright. How would I install magisk again since I wont be able to patch ota?
dewa5227 said:
it simply because you're rooted.. it's already known from a long time.
there're 2 way if you wanna update from OTA:
1. simple uninstall magisk, and restore image. then do update. then back install magisk again
2. localupdate again C.10 and because you're now lose root, then you should be able to update fine
Click to expand...
Click to collapse
Did what you said, it updated. Rebooted. Then after a reboot again my phone only boots into recovery now....
H411UCIN093NIC said:
Did what you said, it updated. Rebooted. Then after a reboot again my phone only boots into recovery now....
Click to expand...
Click to collapse
what step that you actually do ?
If you like to do an OTA;
Go to Magisk, uninstall Magisk - restore Image
Download and Install the OTA but DONT reboot
Go to Magisk, install magisk to inactive slot after ota
Reboot
xtcislove said:
If you like to do an OTA;
Go to Magisk, uninstall Magisk - restore Image
Download and Install the OTA but DONT reboot
Go to Magisk, install magisk to inactive slot after ota
Reboot
Click to expand...
Click to collapse
Thank you
H411UCIN093NIC said:
Did what you said, it updated. Rebooted. Then after a reboot again my phone only boots into recovery now....
Click to expand...
Click to collapse
Try to change slot via fastboot
xtcislove said:
Try to change slot via fastboot
Click to expand...
Click to collapse
Yea I tried that. I had to use msm tool loose all data then start from scratch apply all updates then I was able to do what you said and it worked. I'm on the latest A12 with root but unfortunately I lost all data in the meantime.
Installing magisk in an inactive slot will result in a softbrick.
Maruli said:
Installing magisk in an inactive slot will result in a softbrick.
Click to expand...
Click to collapse
So lets say I am on the latest Android 11 stable build and I want to flash the C11 stable Android 12 build (full zip, not incremental) and keep root and data. Is there a way to do that?
Previously as others have said, we restore images in Magisk. Install the OTA, then direct install Magisk, then to inactive slot, reboot, and all is well. Does this no longer work? Can someone please give a full explanation of their understanding?
xgerryx said:
So lets say I am on the latest Android 11 stable build and I want to flash the C11 stable Android 12 build (full zip, not incremental) and keep root and data. Is there a way to do that?
Previously as others have said, we restore images in Magisk. Install the OTA, then direct install Magisk, then to inactive slot, reboot, and all is well. Does this no longer work? Can someone please give a full explanation of their understanding?
Click to expand...
Click to collapse
Do you have the IN2021 version? Because NA/global doesn't have a full ROM yet. I can only confirm what the guy above me has experienced - installing magisk (v24.3) into the updated slot will result in a softbrick. Without that step it's working fine (I managed to switch slots in fastboot and redo the update from previous slot again).
It seems like the boot.img from the IN2021 C11 ROM does work with the IN2025 software, since I couldn't extract the incremental OTA and patch the boot.img. That actually saved my phone and I almost used MSM tool.
Maybe it's different if you update from A11 to A12 - I updated from OB1 C10 to C11 and magisk messes something up in the process.
Maruli said:
Do you have the IN2021 version? Because NA/global doesn't have a full ROM yet. I can only confirm what the guy above me has experienced - installing magisk (v24.3) into the updated slot will result in a softbrick. Without that step it's working fine (I managed to switch slots in fastboot and redo the update from previous slot again).
It seems like the boot.img from the IN2021 C11 ROM does work with the IN2025 software, since I couldn't extract the incremental OTA and patch the boot.img. That actually saved my phone and I almost used MSM tool.
Maybe it's different if you update from A11 to A12 - I updated from OB1 C10 to C11 and magisk messes something up in the process.
Click to expand...
Click to collapse
Thanks, that helps a lot. I think I'm going to wait until the dust settles because I need my phone available for work. I can't be stuck in a bootloop for 3 hours trying to fix it.
I tried to extract the BOOT.IMG from the OTA file, trying many tools without success, although in the log of one of the extraction tools it told me that the boot had 100MB, in the output only a boot.img appeared with 0MB