I'm hoping to return my Infinity due to a few issues. I really love it though and want to get another one and hope it doesn't have the issues this one does. Mine is a C06 serial number, built in June. It is rooted, locked and I just today did the OTA.
My question is, can all infinities be rooted? Will the newer builds like the C08 serial numbers give me any problems? If the new Infinity comes with any of the firmware updates that have taken place, will I still be able to root? I have only a few days left in my return period and really want to send this one back and roll the dice on getting one that doesn't have the problems this one does, but not at the cost of being unable to root.
Thanks
If I'm not mistaken the serial number doesn't matter in regards to rooting. It's the updates that patch root vulnerabilities.
I'm not sure if the current root method (Debugfs) will work on the .30 update that just came out, so if you receive an Infinity with that build you might be out of luck. I haven't heard anything about the rootability of the new update yet other than the fact that OTA RootKeeper works.
Sent from my ADR6425LVW using XDA Premium.
Debugfs root works with 4.0.3. Superuser OTA survival didn't work when I upgraded so I had to root again. As SteveG12543 pointed out, the serial number shouldn't make a difference.
Related
A few months ago I rooted my Plus because of Samsung's apparent inability to deliver Jelly Bean to my device. After realizing I have no idea what to do with ROMs, flashing, etc., I figured I'd wait it out until the official update was released. Sure enough it was last month, but I have yet to get a notification saying an update was available.
Will I ever get a notification, or do I have to unroot ( need help on that, though I think I know now )? Additionally, is the update OTA or through KIES?
ProjectShadow316 said:
A few months ago I rooted my Plus because of Samsung's apparent inability to deliver Jelly Bean to my device. After realizing I have no idea what to do with ROMs, flashing, etc., I figured I'd wait it out until the official update was released. Sure enough it was last month, but I have yet to get a notification saying an update was available.
Will I ever get a notification, or do I have to unroot ( need help on that, though I think I know now )? Additionally, is the update OTA or through KIES?
Click to expand...
Click to collapse
Root shouldn't affect update notifications. Though those only notify if an update is rolled out for your own region and/or carrier. Depending if you have the 6200 or 6210 model only certain regions have JB available, however this doesn't stop you from flashing a rom from a different region. I have a canadian 6210 and running the UK/Ireland 4.1.2 with no ill effects to report and it's pretty sweet!
I am on my way out but check the developper threads and there should be a few on flashing the new stock JB roms that are out.
So... I'm about to get a new S6 for Verizon. There's pretty limited info in this thread, but a lot of it seems like a new S6(as of 10/01/2015) isn't rootable/ROMable because of the most recent OTA that I would assume would be on a phone bought now. Is that correct? If not can someone point me to threads that show how to root and get a custom recovery on?
Thanks,
Craig
Correct. You will not be able to root the new s6 unfortunately. You can likely buy one on swappa that hasn't been updated and is running fireflash or whatever.
Sent from my SM-G925V using XDA Free mobile app
.....unless you get lucky and get a phone with OC3 or OE2. Verizon just sent me a replacement S6 (was having major BT issues) and I got lucky enough to get one on OC3. S6 + OE2 + root + greenify = me happy :laugh:
Software out-of-the-box
csh8428 said:
So... I'm about to get a new S6 for Verizon. There's pretty limited info in this thread, but a lot of it seems like a new S6(as of 10/01/2015) isn't rootable/ROMable because of the most recent OTA that I would assume would be on a phone bought now. Is that correct? If not can someone point me to threads that show how to root and get a custom recovery on?
Thanks,
Craig
Click to expand...
Click to collapse
Were you able to get a new S6 from Verizon with either OC3 or OE2, if so which one? I am interested in getting it too, but it's a no go if root is not possible.
NSRacer said:
.....unless you get lucky and get a phone with OC3 or OE2. Verizon just sent me a replacement S6 (was having major BT issues) and I got lucky enough to get one on OC3. S6 + OE2 + root + greenify = me happy :laugh:
Click to expand...
Click to collapse
I'm worried that if I get a new S6 from verizon it will auto-update to 5.1.1 OG5 during the initial setup wizard/process. Can you explain how you stopped yours from updating to OE2 and OG5? Thanks in advance
The device won't auto-update itself without consent from the user. My replacement came with OC3, so I pulled down OE2 (from the web) and pushed that to the phone using ODIN. Once that was done, I applied root which prevents the phone from receiving OTA updates.
NSRacer said:
The device won't auto-update itself without consent from the user. My replacement came with OC3, so I pulled down OE2 (from the web) and pushed that to the phone using ODIN. Once that was done, I applied root which prevents the phone from receiving OTA updates.
Click to expand...
Click to collapse
Thanks for the info! I went in to a verizon the other day and their answers were all over the place; it's amazing how they know so little about the devices they spend all day selling, servicing. They tried to tell me that a mandatory update came out Friday "for all verizon android phones" and the play store wouldn't work if it wasn't updated to it (though they told me also that the user has no choice to reject updates - lol)
NSRacer said:
The device won't auto-update itself without consent from the user. My replacement came with OC3, so I pulled down OE2 (from the web) and pushed that to the phone using ODIN. Once that was done, I applied root which prevents the phone from receiving OTA updates.
Click to expand...
Click to collapse
I got my s6 from someone on swappa and for some reason, once I first booted and was doing initial setup, the phone automatically rebooted into update mode. As soon as it was back up and running, the build version was too new to root and the bootloader version had been updated too. I don't know why it did this for me, I was really tempted to hard reboot while it was in update mode to prevent it because I really wanted to root, but I was even more worried about bricking the phone. I figure maybe the guy who sold it to me had already downloaded the update but did not run it, and after doing a factory reset maybe the phone was somehow set to auto-execute the update...
Anyone else received a software update this morning? I just did, it was like 41mb. Don't see any difference yet but I'm still looking.
It was a security update. Maybe to close possible holes that could have been used for rooting.
veritasaequita said:
Anyone else received a software update this morning? I just did, it was like 41mb. Don't see any difference yet but I'm still looking.
Click to expand...
Click to collapse
What is the date of your security patch level in about phone after updating?
Ss
I did get the update but was told if it was installed it may kill the chances of ever being able to root the device.. So even though it seems hopeless for root right now, i skipped this update.
cr1130 said:
I did get the update but was told if it was installed it may kill the chances of ever being able to root the device.. So even though it seems hopeless for root right now, i skipped this update.
Click to expand...
Click to collapse
LOL the bootloader is locked. So either an exploit is needed in the system ( not impossible one was found on the Verizon s6 and patched a week later) but samsung has gotten really good at not releasing with an exploit or they give us a way to unlock the bootloader
cr1130 said:
I did get the update but was told if it was installed it may kill the chances of ever being able to root the device.. So even though it seems hopeless for root right now, i skipped this update.
Click to expand...
Click to collapse
Chances of root are slim to none unless tmo provides a way to unlock the bootloader. Even if an exploit allowed root to be pushed into system the device would not boot due to kernel checks for system modifications.
i got "b6 " in the last 2 digits on build number
veritasaequita said:
Ss
Click to expand...
Click to collapse
looks like a baseband update ,
muniz_ri said:
Chances of root are slim to none unless tmo provides a way to unlock the bootloader. Even if an exploit allowed root to be pushed into system the device would not boot due to kernel checks for system modifications.
Click to expand...
Click to collapse
So should I update my S7 to the new security update. Does this new update improve performance battery life etc.? The security update is 41.27mb. That is the update that I am getting. So a Root for the T-Mobile S7 is probably never going to happen? If I update to new security update will it prevent bootloader to unlock even more?
passion4tech said:
So should I update my S7 to the new security update. Does this new update improve performance battery life etc.? The security update is 41.27mb. That is the update that I am getting. So a Root for the T-Mobile S7 is probably never going to happen? If I update to new security update will it prevent bootloader to unlock even more?
Click to expand...
Click to collapse
We have seen leaked engineering bootloaders and kernels on other samsung locked bootloader devices recently which have allowed root (albeit not very practical root implementations). That is likely the best chance of getting root on this device, i.e. unlikely.
Hope I am wrong but I would take the security update without hesitation and settle in to the fact that root is probably not going to happen on this device.
muniz_ri said:
Chances of root are slim to none unless tmo provides a way to unlock the bootloader. Even if an exploit allowed root to be pushed into system the device would not boot due to kernel checks for system modifications.
Click to expand...
Click to collapse
muniz_ri said:
We have seen leaked engineering bootloaders and kernels on other samsung locked bootloader devices recently which have allowed root (albeit not very practical root implementations). That is likely the best chance of getting root on this device, i.e. unlikely.
Hope I am wrong but I would take the security update without hesitation and settle in to the fact that root is probably not going to happen on this device.
Click to expand...
Click to collapse
OK I won't hesitate to take the new security update. But can you tell me if the new update 41.27mb improves performance and battery life? Can someone tell me their experience with this new update?
Yes it does improve the battery life. The initial update will some what drain the battery fast. Dont worry just allow it to completely dies then fully charge it. After 2 or 3 charge cycle you wont see a huge dip in battery drain like at the time of initial updates. I was furious at 1st as my phone dies in like an 3 to 4 hours usage as before i can be go a full day of 8-9 hours of heavy usage. Wity a full charge at 5am and dont have to fully charge it until 7pm is very impressive. Thats with web browsing, facebook, youtube and Pandora. fb Messaging
Hey guys... Does anyone know when I should expect my update to Oreo OTA. I don't plan on becoming a beta tester or flashing it myself.
So if anyone has an idea of when Oreo will be pushed out to the masses, I'd appreciate it!
Thanks!
connorhiller said:
Hey guys... Does anyone know when I should expect my update to Oreo OTA. I don't plan on becoming a beta tester or flashing it myself.
So if anyone has an idea of when Oreo will be pushed out to the masses, I'd appreciate it!
Thanks!
Click to expand...
Click to collapse
I'm in the same boat. No one knows yet. There are not even factory images available nor full OTA images on the google site here.
https://developers.google.com/android/images
Until such time as they appear don't sweat it. After they do then you can re-ask your question but you'll probably get it before you can hit send. Someone said they got an OTA on Verizon from 7.1.2 to 8.0 but I'm a little leery of that claim since no one else I've seen has received it.
I believe it was destined for the Aug 21 deadline but some major problems have arisen and I believe it was pulled for further testing. Bluetooth is one of them, random rebooting, stuff like was on some dp4 devices. I also saw some volume control issues too. Yes, I know others haven't had issues and someone will post a link to the factory images on the android site but that doesn't help any of us with locked bootloaders. Besides the fact that I like the background install and being able to use the phone while it's updating. Then a simple reboot and you're done. It'll happen soon but no one knows when yet.
I am in UK and I have already received for Oreo OTA on Google Pixel set.
It can be flashfire updated as well for root purpose.
sitnaing said:
I am in UK and I have already received for Oreo OTA on Google Pixel set.
It can be flashfire updated as well for root purpose.
Click to expand...
Click to collapse
So you were on stock 7.1.2, locked bootloader, not rooted and you received an OTA to 8.0? I'm not sure what you mean by flashfire updated. An OTA installs in the background.
bobby janow said:
So you were on stock 7.1.2, locked bootloader, not rooted and you received an OTA to 8.0? I'm not sure what you mean by flashfire updated. An OTA installs in the background.
Click to expand...
Click to collapse
I am on 7.1.2 unlock bootloader with root.
You should also have received ota update if you are on locked bootloader with no root.
Some of ota roll out dependent on carrier. But if yours is google set, you would be able to receive by now.
sitnaing said:
I am on 7.1.2 unlock bootloader with root.
You should also have received ota update if you are on locked bootloader with no root.
Some of ota roll out dependent on carrier. But if yours is google set, you would be able to receive by now.
Click to expand...
Click to collapse
Well that's a bit of good news. One thing is that on G+ no one has posted the inevitable screenshot of the OTA notification (which are at best annoying but they do it anyway), so it must be rolling out very slowly. The other thing is that once an OTA is released the system images are usually available with the OTA images shortly thereafter. I don't see either of those at this point.
I mean I'm gonna wait and I'm sure it'll be here, but the question is when. I'm on VZW so they might be tweaking some things before the let Google release it. Not sure how that works.
Did yours install in the background and then a reboot to 8.0? How long was the bootup process if you watched it?
For carrier, like you said roll out will take some time. For me, time taken is similar to update and reboot as normal security patch monthly update where it should take longer as this is the whole different version. May be backbone still same but with just UI change and some tweaks.
Today I noticed that OnePlus has the 9.5.7 update on their site, and I was curious if there any drawbacks to using that instead of waiting for the OTA. For context, I keep my phone stock unrooted with the T-Mobile firmware so I'm mostly concerned about being able to get future T-Mobile OTAs. Are there any reasons I should avoid applying the update before the OTA comes?
This may be a moot point, since the T-Mobile firmware doesn't have the easy button to install a local update and I'm too lazy for ADB and all that.
horatiopositronic said:
Today I noticed that OnePlus has the 9.5.7 update on their site, and I was curious if there any drawbacks to using that instead of waiting for the OTA. For context, I keep my phone stock unrooted with the T-Mobile firmware so I'm mostly concerned about being able to get future T-Mobile OTAs. Are there any reasons I should avoid applying the update before the OTA comes?
This may be a moot point, since the T-Mobile firmware doesn't have the easy button to install a local update and I'm too lazy for ADB and all that.
Click to expand...
Click to collapse
My guess is that you should never simply flash an international OTA over a stock TMo OP7p... Otherwise, we probably wouldn't see all the threads in XDA about converting a TMo OP7p to the unlocked OP7p!