I was wondering if anyone found a way to take ota after rooting. I have always had rooted devices and always ended up on custom roms. For now I would like to stay on the official rom and debloat a bit. Any ideas?
Pretty sure you can just flash back to stock and take ota, then re root. You normally need stock recovery to take ota, and be unrooted
Sent from my XT1056 using xda app-developers app
I can't believe i didnt think of that after I did the same thing with the S4. Thx for shining some light into my clouded mind lol
Root
I rooted yesterday night. Will I be able to odin back to official and receive OTA updates?
roadrunnrr said:
I rooted yesterday night. Will I be able to odin back to official and receive OTA updates?
Click to expand...
Click to collapse
I tried this and update still wouldn't let me download the OTA.
Unless someone comes out with a way to revert the knox flag (which is said to be a perm flag) it won't ever be possible to be true factory again as all OTA's will now check for the tamper.
I think someone mentioned though you can manually install it, just the downloader/OTA wouldn't work.
If manually still wasn't possible I'm sure someone could remove the check from the update and you still get it that way but officially through Samsung you currently are probably stuck.
Ideally someone finds a way to reset the so called, perma flag.
If not the alternative might be finding a way to root the phone without flagging it, but in those cases it won't help those already flagged.
I know on HTC they had a similar type of flag, though didn't use it to check for update status. They flagged as Tampered or Re-locked for example.
However after some time we found how to reset those in some magical hidden area to blind write too (not talking about those that cheated to hide it via bootloader image edits)
At this point it's a wait and see game...
I hope someone finds fast though, I am stock and really want to get this bloat off my phone lol
I tried it myself now... Rooted and i couldnt even check for updates. Unrooted but device status was still custom. I had to go into the stock recovery and wipe everything and then Odin stock firmware to be able to check for updates
Sent from my SM-G900P using XDA Premium 4 mobile app
roadrunnrr said:
I tried it myself now... Rooted and i couldnt even check for updates. Unrooted but device status was still custom. I had to go into the stock recovery and wipe everything and then Odin stock firmware to be able to check for updates
Click to expand...
Click to collapse
When I tried this the update check still failed stating that I had a custom ROM.
Just checked for updates and it went through
Sent from my SM-G900P using XDA Premium 4 mobile app
roadrunnrr said:
Just checked for updates and it went through
Sent from my SM-G900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Were you rooted then un-rooted?? Can you post the OTA file from your cache??
Yeah... Rooted then grabbed the whole factory md5 and restored that did it. Let me know where I can find the OTA and I'll post it. But I'm unrooted now so I don't know if it will work
Sent from my SM-G900P using XDA Premium 4 mobile app
roadrunnrr said:
Yeah... Rooted then grabbed the whole factory md5 and restored that did it.
Click to expand...
Click to collapse
Nice, Otherwise seems like a bad strategy on Samsung's part if they don't allow people who unroot and odin back to stock to take OTA's.. Why would a manufacture not want to offer a path back to stock for security updates and the chance to get a user back on a bloated rom full of there paid ad apps. Each time users do this there is a small percentage that won't either be able to re-root due to updates stopping the root method or just out of hassle. I understand the warranty flag but not why you wouldn't offer a path back to stock unless they are just being short sighted in an attempt to penalize people who root which won't have much effect..
I'd post the OTA like I said but I'm unrooted now.
Sent from my SM-G900P using XDA Premium 4 mobile app
roadrunnrr said:
I'd post the OTA like I said but I'm unrooted now.
Sent from my SM-G900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So root!!
Still waiting to find out if I'll be able to get back to official and then check for updates after this update and root
Sent from my SM-G900P using XDA Premium 4 mobile app
roadrunnrr said:
Still waiting to find out if I'll be able to get back to official and then check for updates after this update and root
Click to expand...
Click to collapse
I can't seem to do it. Once I rooted and tripped the Knox flag bit the Update check won't let me download. But the error message says that I can still download and install updates using Kies.
I just fixed it. The problem is not the Knox flag but rather the fact that Custom was showing in Download mode instead of Official. I had to flash twice without my SDcard inserted to get to Official. Once I got to Official the update started to download.
rooted?
roadrunnrr said:
Still waiting to find out if I'll be able to get back to official and then check for updates after this update and root
Sent from my SM-G900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
so what does it matter if a phone is rooted or not in terms of an OTA update from a phone that has already received it?....wouldn't you just upload it and apply it? shouldn't matter at all whether phone is rooted or not when you're updating the file received from an already received OTA phone update. It's just the acquisition of the update that's blocked, not the install. At least until the 5SS you could always just grab a copy of the OTA update and install.
dk2463 said:
so what does it matter if a phone is rooted or not in terms of an OTA update from a phone that has already received it?....wouldn't you just upload it and apply it? shouldn't matter at all whether phone is rooted or not when you're updating the file received from an already received OTA phone update. It's just the acquisition of the update that's blocked, not the install. At least until the 5SS you could always just grab a copy of the OTA update and install.
Click to expand...
Click to collapse
No if you were completely stock and just root ...with stock recovery and no missing system files it could be done. ...it now has to say official for the ota to finish ....no other way
Sent from my SM-G900P using Xparent BlueTapatalk 2
share the love
but again, once a non-rooted phone receives the OTA update, you just pull the update from the phone and share it and even rooted phones can update...that's my point...am shocked no one is sharing their "received" OTA update
Epix4G said:
No if you were completely stock and just root ...with stock recovery and no missing system files it could be done. ...it now has to say official for the ota to finish ....no other way
Sent from my SM-G900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Patience.. I guess..
dk2463 said:
but again, once a non-rooted phone receives the OTA update, you just pull the update from the phone and share it and even rooted phones can update...that's my point...am shocked no one is sharing their "received" OTA update
Click to expand...
Click to collapse
I gotta agree.. Most of my previous device OTA's were always dumped within hours of release really surprised this hasn't been yet. This is my first Samsung phone and I have liked the device but kinda disappointed in the XDA turnout so far. I am always appreciative of those who are here but I just thought with how popular the Galaxy line was there would be more dev support from day 1 but there hasn't been much so far. I know it's early and being CDMA/Sprint really limits us but seems like all my previous HTC devices on Sprint and the current M8 are getting way more action.. Oh well, but sure makes a jump to T-Mobile for the new Oneplus One Cyanogen phone sound tempting haha..
And thanks again to all those who are here and contributing!!!
Related
I searched through the rooting thread, but that only said it was ok to root the phone after installing the latest update from verizon. Now that my phone is rooted, can I still apply the updates verizon pushes down?
oakdog8 said:
I searched through the rooting thread, but that only said it was ok to root the phone after installing the latest update from verizon. Now that my phone is rooted, can I still apply the updates verizon pushes down?
Click to expand...
Click to collapse
No no no NO!
You will lose root.
Sent from my ADR6400L using XDA Premium App
You wouldnt even get the updates Verizon pushes. You could manually flash the RUU's and you would loose root or you could just wait until the ROM you use starts basing their future versions off of the updates which wont lose root.
If you look on the TB forum sites you will usually be able to find the update for rooted phones to if you are not using a custom ROM.
I was laying in bed (with food poisoning) trying to get some sleep, when I noticed my phone vibrated and randomly rebooted.
After it booted up to the Andy firmware update image, and finally to the home screen with the update message I knew I was screwed.
THIS WAS A FORCED UPDATE BY VERIZON. I NEVER ACCEPTED OR DECLINED ANYTHING (re: food poisoning)!
You WILL lose root, on device app searching (Apple legal bs), and probably your unlock!
The perfect end to a perfect night! THANKS Verizon! /sarcasm
mcduck$ said:
I was laying in bed (with food poisoning) trying to get some sleep, when I noticed my phone vibrated and randomly rebooted.
After it booted up to the Andy firmware update image, and finally to the home screen with the update message I knew I was screwed.
THIS WAS A FORCED UPDATE BY VERIZON. I NEVER ACCEPTED OR DECLINED ANYTHING (re: food poisoning)!
You WILL lose root, on device app searching (Apple legal bs), and probably your unlock!
The perfect end to a perfect night! THANKS Verizon! /sarcasm
Click to expand...
Click to collapse
What ROM were you running? It should have disable OTA's thats why I ask.
Brian Gove said:
What ROM were you running? It should have disable OTA's thats why I ask.
Click to expand...
Click to collapse
The title says rooted stock.
I was runing the stock touchwiz rom (with the VRGL2 or 1 baseband) rooted, stock recovery, and the bootloader unlocked.
I just checked the EZ unlocker app and it claims that the bootloader is still unlocked. I have no way of verifying this, but if true, I'm only half screwed until somebody finds a root method for the new firmware.
If/when that happens I'll be more than happy to flash away from Verizon's bs nonsense.
Grrr...
mcduck$ said:
I was runing the stock touchwiz rom (with the VRGL2 or 1 baseband) rooted, stock recovery, and the bootloader unlocked.
I just checked the EZ unlocker app and it claims that the bootloader is still unlocked. I have no way of verifying this, but if true, I'm only half screwed until somebody finds a root method for the new firmware.
If/when that happens I'll be more than happy to flash away from Verizon's bs nonsense.
Grrr...
Click to expand...
Click to collapse
Did you try re-rooting using current methods?
mcduck$ said:
I was runing the stock touchwiz rom (with the VRGL2 or 1 baseband) rooted, stock recovery, and the bootloader unlocked.
I just checked the EZ unlocker app and it claims that the bootloader is still unlocked. I have no way of verifying this, but if true, I'm only half screwed until somebody finds a root method for the new firmware.
If/when that happens I'll be more than happy to flash away from Verizon's bs nonsense.
Grrr...
Click to expand...
Click to collapse
Wow rooted stock with stock recovery. Why not custom recovery? That probably the reason the update went through. Still ridiculous though, don't get me wrong. I'm guessing you weren't doing a lot of flashing.
Sent from my Nexus 7 using Tapatalk 2
Zalithian said:
Did you try re-rooting using current methods?
Click to expand...
Click to collapse
Negative. I currently feel like crap (see OP) and don't feel like messing with my Windows laptop to try it.
Do you think there's any chance I could brick my phone when I attempt it? Or is it simply a will work/won't work thing?
mcduck$ said:
Negative. I currently feel like crap (see OP) and don't feel like messing with my Windows laptop to try it.
Do you think there's any chance I could brick my phone when I attempt it? Or is it simply a will work/won't work thing?
Click to expand...
Click to collapse
Pretty sure it will just work or fail, but I'd wait for confirmation from someone else first - better safe than sorry.
Can you supply your new Baseband Version number?
I just froze sdm 1.0. I went to the software update and it crashed. I so let's hope that stops the update...
Sent from Land Line using pay phone
epikos said:
Can you supply your new Baseband Version number?
Click to expand...
Click to collapse
I535VRLG7
epikos said:
Can you supply your new Baseband Version number?
Click to expand...
Click to collapse
marcucci217 said:
Wow rooted stock with stock recovery. Why not custom recovery? That probably the reason the update went through. Still ridiculous though, don't get me wrong. I'm guessing you weren't doing a lot of flashing.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I was going to play around with flashing different roms eventually, but after upgrading from a decrepit half working ICS flashed Droid X I was just happy to have fully working phone again. Unfortunately I was under the false impression that the jerks at Verizon would have given me the option to accept their so-called upgrade.
Didn't they already remove local search on Verizon? My phone came that way. Of course I didn't stay on stock once we were freed...
rooting with the rootdebugfs tool should still work!
I woke up to a failed update message. Ran the update again to see why it failed and it fails because it reboots into custom recovery. Rooted, unlocked, stock. Just have some apps disabled or frozen.
Can anyone point out where the in the directory the downloaded update zip would go to?
I didn't get an update message but I did check for one it was available for me. So I ticked ok and it downloaded but failed to update as expected because of the custom recovery I have in place.
But I can't find where the zip file download to.
I wanted to try and see if Chainfire's Mobile ODIN Pro would root the updated zip as it claims.
Cache>fota>update zip...you'll see it
sent from my freed beast...&ikiller
Yes my laziness allowed verizon to update both of my SGS3 to I535VRLG7. I hope I can reroot when I get a chance later.
I was running stock root on both devices.
Sent from my SCH-I535 using xda premium
Successful OTA Flash using Mobile Odin Pro and Kept Root/Unlocked Status
Hulk0069 said:
Cache>fota>update zip...you'll see it
sent from my freed beast...&ikiller
Click to expand...
Click to collapse
Thanks, running a backup now before I try Mobile ODIN Pro. Will update this post:
Edit: Ok, it seems I have a successful flash using Mobile ODIN Pro.
Mobile Odin Pro gave me some Warnings in advance before continuing the Flash.
1) EverRoot may need to remove Google Maps during the flash to free up some space... yadda yadda..
2) The Modem Image on your device does not match the signature check....yadda yadda..
3) 5 out of 499 system files do not match the signature checks in the OTA zip... yadda yadda..
NOTE: I disabled signature checks on both warnings before proceeding.
But you do that AT YOUR OWN RISK!!
From what I gather, Mobile Odin made its own OTA zip from the target file before flashing it
I"ve uploaded some screen shots.
IMPORTANT!
PLEASE RUN A BACK UP before attempting anything risky like this.
ALSO! and VERY IMPORTANT!!
If you are using CWM as your recovery PLEASE PLEASE PLEASE check the size of your backup before proceeding with the update.
It seems CWM is not working properly on my SGSIII because the backup file sizes were only about 22 MB's large.. and thats is SO NOT GOOD!!
I went into GooManager and Flashed TWRP over CWM and ran a backup via TWRP and checked the file size to be in the range of 2.34GB's and thats what it should be (IMO). The only thing that bugs me about both recoveries is the date is 1979-12-31.. and thats definately wrong..
Anyways, my way of checking for root after an OTA is to run Titanium Backup because it always asks for SuperUser Rights before loading.
So all is well with that and checking to see if the Bootloader on my device was still Unlocked with EZ-Unlock said it still was..
Thats all I can think for now..
Hulk0069 said:
Cache>fota>update zip...you'll see it
sent from my freed beast...&ikiller
Click to expand...
Click to collapse
Stock rooted & it tried & failed 2x to do the update and there is nothing in /fota/
I still have root
Second attempt it booted into recovery & I just restarted as it had a fail error
Just pulled in a new update on my s3 so let's pray it's the fix for mobile data. Will post up build number when finished. Build is I535VRBMF1 android 4.1.2 and was a pretty small update.
Is there multiwindow?
Sent from my SCH-I535 using xda app-developers app
Oh good.. That sounds like a new update. Hopefully that means InvisibleK will package a new AIO with the new modem/rpm/sbls for us.
Sent from my SCH-I535 using xda app-developers app
Multi Window is still there.
Currently not being productive on my S3.
---------- Post added at 12:23 AM ---------- Previous post was at 12:18 AM ----------
Build number I535VRBMF1
Currently not being productive on my S3.
http://www.droid-life.com/2013/06/1...hopefully-this-addresses-connectivity-issues/
Sent from my SCH-I535 using Tapatalk 2
Can anyone post the update file?
Sent from my SCH-I535 using xda app-developers app
bricked my phone
So I am pretty new to the community and have only rooted my phone for use of ARliberator. I recently took the MD3 OTA and the signal was crap, now I get the new update this am MF3 and it bricked my phone with the message "system software not authorized by vzw take to store" blah blah. I tried this using voodoo root keeper with out un-rooting first.
Guessing my only option is to flash back in odin mode or is there some recovery that I can try? I have everything backed up with titanium pro. how would I reload all of that after I flash?
Chadashcroft22 said:
...and was a pretty small update.
Click to expand...
Click to collapse
How small ? The previous update that they pulled was just under 130mb as I recall. This one should be very close to the same size unless it's a firmware update only and the "premium suite" will come later.
jdrama12 said:
So I am pretty new to the community and have only rooted my phone for use of ARliberator. I recently took the MD3 OTA and the signal was crap, now I get the new update this am MF3 and it bricked my phone with the message "system software not authorized by vzw take to store" blah blah. I tried this using voodoo root keeper with out un-rooting first.
Guessing my only option is to flash back in odin mode or is there some recovery that I can try? I have everything backed up with titanium pro. how would I reload all of that after I flash?
Click to expand...
Click to collapse
ODIN back to stock OEM , then take all the updates before rooting again. Make a full backup in recovery before using Titanium Backup to restore. Restoring Apps + data with TB can cause issues.
DigitalMD said:
ODIN back to stock OEM , then take all the updates before rooting again. Make a full backup in recovery before using Titanium Backup to restore. Restoring Apps + data with TB can cause issues.
Click to expand...
Click to collapse
So after trying about 5 times my phone booted back up and is working. The update did not go through but my phone is working as it was before. I dont know why the recovery wouldnt boot at first unless it was the update blocking it for a few minutes.
Might have made the rookie mistake since I didnt do the temp un-root with voodoo, but I was trying to be innovative and see if it worked with out it like it did with the MD3 OTA.
Thanks for everyones help on here, teaching a noob like me new tricks.
just updated and kept root...data is appears fixed, thank god
Sent from my Barnes & Noble Nook HD using xda premium
rsswga said:
just updated and kept root...data is appears fixed, thank god
Sent from my Barnes & Noble Nook HD using xda premium
Click to expand...
Click to collapse
Can you give some more details on this? Did you use voodoo root keeper and how did you do it?
I am weary of trying again since it bricked my phone for about 10 minutes.
Updated: I535VRBMF1
I can actually send text messages again...! Cant wait to test 4G in areas it was disabled with the mb3 update.
i used rootkeeper and ezrecovery, flashed to stock recovery and then updated
lost root and had to reroot and unlock bootloader again...............just restarted phone
all good now with mf1
jdrama12 said:
Can you give some more details on this? Did you use voodoo root keeper and how did you do it?
I am weary of trying again since it bricked my phone for about 10 minutes.
Click to expand...
Click to collapse
rsswga said:
i used rootkeeper and ezrecovery, flashed to stock recovery and then updated
lost root and had to reroot and unlock bootloader again...............just restarted phone
all good now with mf1
Click to expand...
Click to collapse
Many thanks. I just was trying to do it with voodoo with out any flashing like I was able to for MD3 however I have tried it twice and it has not worked. I will do have to try the flashing method sometime after work.
Thanks for the help.
Any way I can remove twrp so I can take the update?
Sent from my SCH-I535 using xda app-developers app
jdrama12 said:
Many thanks. I just was trying to do it with voodoo with out any flashing like I was able to for MD3 however I have tried it twice and it has not worked. I will do have to try the flashing method sometime after work.
Thanks for the help.
Click to expand...
Click to collapse
I tried just temp unrooting with voodokeeper, downloading and installing the update, and it worked and the phone loaded up phone and I was able to turn root back on with Voodkeeper no problem. I have two S3s, one is a mistake I made in getting a phone for a now ex that was supposed to pay their share of the bill, etc and didn't and I took the phone back. That's the one I experiment stuff with and tried it there with no problems. I'm afraid to do it without ODINing etc though on the phone I always use. The ex's phone never seems to have any problems with updates and re-rooting though.
something stSettem
kidqwik said:
I tried just temp unrooting with voodokeeper, downloading and installing the update, and it worked and the phone loaded up phone and I was able to turn root back on with Voodkeeper no problem. I have two S3s, one is a mistake I made in getting a phone for a now ex that was supposed to pay their share of the bill, etc and didn't and I took the phone back. That's the one I experiment stuff with and tried it there with no problems. I'm afraid to do it without ODINing etc though on the phone I always use. The ex's phone never seems to have any problems with updates and re-rooting though.
Click to expand...
Click to collapse
Glad to hear that method worked for you. I just tried it again and I get to right after it shuts off and get past the Samsung screen with RECOVERY in the top left in blue, to the yellow triangle saying "you have unauthorized VZW software...turn off device and take to store..." with SECURE:KERNEL in red in the top left...i think thats what it says.
Guessing flash method is all that will work for me, owell.
Thanks again.
Go to odin flash valrec or whatever it is then flash clockwork mod...flash the superuserfix that's used to root and unlock the bootloader...
sent from a violated Vzw Galaxy s3
rsswga said:
Go to odin flash valrec or whatever it is then flash clockwork mod...flash the superuserfix that's used to root and unlock the bootloader...
sent from a violated Vzw Galaxy s3
Click to expand...
Click to collapse
Thanks, just not sure how it got locked on me unless MD3 did that. I will try that later when I am not at work though.
I am running stock 4.1.2 rooted and froze SDM 1.0 with titanium backup to avoid the constant update reminders.
I am now curious can I accept the updates and keep root somehow?
Is something like OTA root keeper worthwhile?
You can still root but cannot unlock the bootloader. I'd recommend reading the 4.3 sticky thread before taking the ota even if you want to stay stock.
Sent from my d2lte using XDA Premium 4 mobile app
dpeeps74 said:
You can still root but cannot unlock the bootloader. I'd recommend reading the 4.3 sticky thread before taking the ota even if you want to stay stock.
Sent from my d2lte using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Are you saying that because of the 4.3 issues?
I would rather not mess with the phone but I just got a gear 2 neo and it will not connect. I think this is because of the older android version. The specs on the gear software say it requires 4.2 or higher
scottfarcuz said:
Are you saying that because of the 4.3 issues?
I would rather not mess with the phone but I just got a gear 2 neo and it will not connect. I think this is because of the older android version. The specs on the gear software say it requires 4.2 or higher
Click to expand...
Click to collapse
Ya you need 4.3.
So you have options, since you're have a galaxy gear you're probably going to be running stock TouchWiz, so I would just take the upgrade.
You can root later, but the gear would never work with aosp anyway. Safestrap can make your phone run pretty well with a TouchWiz custom rom if you eventually decide you want one.
Or you can load a custom TouchWiz 4.3 rom right now and see if it connects, then you wouldn't lock your phone down permanently.
Sent from my HTC6525LVW using Tapatalk
Id like to go with a custom rom but don't have a clue what I'm doing.
Thanks for the help
scottfarcuz said:
Id like to go with a custom rom but don't have a clue what I'm doing.
Thanks for the help
Click to expand...
Click to collapse
OK then read the sticky threads in the development section, everything there has guides available for rooting and installing roms, then ask more questions if you have them.
Make sure you're reading the older sticky thread, not the 4.3 one.
Sent from my HTC6525LVW using Tapatalk
I've been unable to even get the OTA to work. It downloads then fails on install.
I have reset the flash counter but thought that was all that would be required to repair/delete before running the OTA update.
Does anyone have a suggestion?
Just to clarify the phone is currently rooted (casual method) on 4.1.2. I never touched the rom or bootloader after rooting i just installed titanium backup and froze all the bloat. Id like to get the OTA even if i lose root.
I reset the flash counter with triangle away and did a batch unfreeze with titanium backup.The OTA downloads then fails on install.
You would probably need to unfreeze everything for the update to work, at least thats what I have heard.
Sent from my SCH-I535 using Tapatalk
scottfarcuz said:
I've been unable to even get the OTA to work. It downloads then fails on install.
I have reset the flash counter but thought that was all that would be required to repair/delete before running the OTA update.
Does anyone have a suggestion?
Just to clarify the phone is currently rooted (casual method) on 4.1.2. I never touched the rom or bootloader after rooting i just installed titanium backup and froze all the bloat. Id like to get the OTA even if i lose root.
I reset the flash counter with triangle away and did a batch unfreeze with titanium backup.The OTA downloads then fails on install.
Click to expand...
Click to collapse
Use this thread to Odin flash 4.3. It's the exact same as taking the Ota.
http://forum.xda-developers.com/showthread.php?t=2586319
I'm sure you already know what taking the update entails, just be absolutely sure it's what you want to do before you flash it. There's no going back.
Sent from my HTC6525LVW using Tapatalk
IF you take the PD1 update you won't be able to revert to previous bootloaders. (EDITED)--> You can revert after all. I think I had repartition checked when I started this thread.
Sleepycloud said:
IF you take the PD1 update you won't be able to revert to previous bootloaders. It contains nothing interesting except security enhancements. It is only 28mb and does nothing good for us modders.
Click to expand...
Click to collapse
****. I went to the Sprint store to get a sim card for my new Note 5 and the **** must have taken the OTA. Can i still root using the method in the MM Deodexed thread?
SantinoInc said:
****. I went to the Sprint store to get a sim card for my new Note 5 and the **** must have taken the OTA. Can i still root using the method in the MM Deodexed thread?
Click to expand...
Click to collapse
not yet c9nfirmed
Sent from my SM-N920P using XDA Premium HD app
SantinoInc said:
****. I went to the Sprint store to get a sim card for my new Note 5 and the **** must have taken the OTA. Can i still root using the method in the MM Deodexed thread?
Click to expand...
Click to collapse
If you are stuck as you are I might request for am exchange
Sent from my SM-N920P using XDA-Developers mobile app
I would definitely complain.
Sent from my SM-N920P using XDA-Developers mobile app
Does it kill the reboot hack for hotspot?
its not rootable at this time
Sent from my SM-N920P using XDA Premium HD app
pbedard said:
its not rootable at this time
Sent from my SM-N920P using XDA Premium HD app
Click to expand...
Click to collapse
This guy confirmed he could root with PD1 update, anyone else tried PD1 root ?
SantinoInc said:
I took PD1 update as well and i was able to root w/o a problem. I have no idea why it's not going through for you. Maybe try Chainfire method?
Sent from my SM-N920P using XDA-Developers mobile app
Click to expand...
Click to collapse
su660ics said:
This guy confirmed he could root with PD1 update, anyone else tried PD1 root ?
Click to expand...
Click to collapse
Does it has new radio? Let me know.
You can download to previous bootloaders if you take the OTA to PD1. I'm not rooted and had a problem with my bluetooth on PD1. I didn't wanna lose my hotspot mod so I wanted to downgrade to OK3 and then take the OTAs to PC3 and then PD1. Here are the steps I used:
1. If on PD1 reboot to Recovery and wipe factory reset however many times you see fit. I only did it once.
2. Reboot to Download Mode and flash PC3 tar file via Odin
3. Once phone reboots to Welcome Screen power phone off by pressing and holding Power button
4. Reboot to Download Mode and flash OK3 via Odin
5. Once phone reboots it will sit at splash screen
6. Reboot to Recovery and wipe Factory Reset however many times you see fit. I did this once.
7. Let phone reboot and Profit
Thanks for the info
Sent from my SM-N920P using Tapatalk
travisw0204 said:
You can download to previous bootloaders if you take the OTA to PD1. I'm not rooted and had a problem with my bluetooth on PD1. I didn't wanna lose my hotspot mod so I wanted to downgrade to OK3 and then take the OTAs to PC3 and then PD1. Here are the steps I used:
1. If on PD1 reboot to Recovery and wipe factory reset however many times you see fit. I only did it once.
2. Reboot to Download Mode and flash PC3 tar file via Odin
3. Once phone reboots to Welcome Screen power phone off by pressing and holding Power button
4. Reboot to Download Mode and flash OK3 via Odin
5. Once phone reboots it will sit at splash screen
6. Reboot to Recovery and wipe Factory Reset however many times you see fit. I did this once.
7. Let phone reboot and Profit
Click to expand...
Click to collapse
Hey travis, i just want to make sure I'm following prior to making any mistakes. So, if my phone is neither rooted or unlocked bootloader, in other words, stock, i would be able to follow your instructions and down grade to 5.1.1 if i have the pd1 version? Thanks
Supermario777 said:
Hey travis, i just want to make sure I'm following prior to making any mistakes. So, if my phone is neither rooted or unlocked bootloader, in other words, stock, i would be able to follow your instructions and down grade to 5.1.1 if i have the pd1 version? Thanks
Click to expand...
Click to collapse
If I can downgrade on Verizons supposedly locked bootloaders, then you should be able to do it with Sprint because they're not as tough on the bootloader locking like Verizon is.
ok so is anyone sure if pd1 is rootable. i been meaning to take the plunge so do i have to downgrade first?? and... how come the 1st post says cannot be downgraded? all other posts ive searched have had little to no info.... thanks
juvenile43 said:
ok so is anyone sure if pd1 is rootable. i been meaning to take the plunge so do i have to downgrade first?? and... how come the 1st post says cannot be downgraded? all other posts ive searched have had little to no info.... thanks
Click to expand...
Click to collapse
I'd like to know as well. I'm sick of seeing this dumb update icon and message. I'm stock and haven't rooted yet (still deciding on Samsung Pay) but might want to at some point.
Im on PD1 on my unrooted, never been rooted Note 5. Ill test it for everybody. Gimme an hour and ill be back with good info.
Sent from my SM-N920P using XDA-Developers mobile app
Sleepycloud said:
Im on PD1 on my unrooted, never been rooted Note 5. Ill test it for everybody. Gimme an hour and ill be back with good info.
Sent from my SM-N920P using XDA-Developers mobile app
Click to expand...
Click to collapse
...
Sent from my SM-N920P using XDA-Developers mobile app
rayraycarter4 said:
...
Sent from my SM-N920P using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes. I just checked the downgrade from PD1 to PC3. It was just fine. So i checked the downfrade to OI6 and had no problems with it either. I think i had repartition checked when i started this thread. That is the only logical explanation. Yes... you can down grade afterall. I stand corrected in myself. One thing to note is that after the downgrade you have to factory reset in recovery, or it just keeps bootlooping.
Sent from my SM-N920P using XDA-Developers mobile app
Sleepycloud said:
Yes. I just checked the downgrade from PD1 to PC3. It was just fine. So i checked the downfrade to OI6 and had no problems with it either. I think i had repartition checked when i started this thread. That is the only logical explanation. Yes... you can down grade afterall. I stand corrected in myself. One thing to note is that after the downgrade you have to factory reset in recovery, or it just keeps bootlooping.
Sent from my SM-N920P using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for your confirmation. Good to learn that I can downgrade anytime I feel like
Sleepycloud said:
IF you take the PD1 update you won't be able to revert to previous bootloaders. It contains nothing interesting except security enhancements. It is only 28mb and does nothing good for us modders.
Click to expand...
Click to collapse
I see nothing wrong with this update.
I just rooted and is working with t-mobile network.