Related
So I bought this i537 used a while back, the previous owned never registered it with samsung but I did when I bought it so I do have a warranty on it. I know it was previously rooted then unrooted before I bought it but I don't know if it ever had a custom rom on it. I rooted the phone with activeroot (still on 4.2.2 stock rom) and have since unrooted it with superSU.
I am having problems with the touchscreen and samsung has confirmed warranty coverage and gave me a shipping label but I want to be totally sure it a-ok before I send it in.
When I boot into odin mode there is no KNOX status, is that normal for this device? Did 4.2.2 not come with knox on this device?
Also the status says custom? When the phone WAS rooted it said official ??? seems bass ackwards.
Also, I would like to reload stock 4.2.2 via ODIN just to make sure everything is kosher before sending it it, would this void my warranty?
My phone is also sim unlocked, i imagine this is okay as far as warranty goes? Would reflashing with ODIN break my sim unlock?
Thanks so much!
CaseyR22 said:
So I bought this i537 used a while back, the previous owned never registered it with samsung but I did when I bought it so I do have a warranty on it. I know it was previously rooted then unrooted before I bought it but I don't know if it ever had a custom rom on it. I have rooted the phone with activeroot (still on 4.2.2 stock rom).
When I boot into odin mode there is no KNOX status, is that normal for this device? Did 4.2.2 not come with knox on this device?
Also, I would like to reload stock 4.2.2 via ODIN just to make sure everything is kosher before sending it it, would this void my warranty?
My phone is also sim unlocked, i imagine this is okay as far as warranty goes? Would reflashing with ODIN break my sim unlock?
Thanks so much!
Click to expand...
Click to collapse
Let's start from the top:
This phone came with MF2 (4.2.2), which was then immediately updated to MF3 (4.2.2). Both of these versions came with Knox enabled. If he just rooted then he probably didn't trip the Knox flag, but there could have been other things he did or tried to do that did trip the flag.
If it is indeed the i537, I can guarantee he did not flash a custom ROM. The i537 has a locked bootloader which means no custom recovery and no custom ROMs. However there is the ability to use TouchWiz-based ROMs, if you want to learn more about this and how it works read about SafeStrap.
We do not have official 4.2.2 stock firmware available to flash. We have a pre-release of 4.2.2, a pre-release of 4.3, official 4.3, and an OTA to go from 4.3 to 4.4.2. You can read more about the different firmwares in the i537 Firmware Thread.
Flashing firmware with Odin will erase your SIM unlock, but you can either enter the unlock code again or there are other methods that can be used. I'm not familiar with SIM unlocking so you'll have to do a little searching.
You never mentioned what you're sending the phone in for. I would try flashing the MF1 firmware first to see if it's a software issue. If it's a hardware issue then unfortunately you'll have to send it in.
Devo7v said:
Let's start from the top:
This phone came with MF2 (4.2.2), which was then immediately updated to MF3 (4.2.2). Both of these versions came with Knox enabled. If he just rooted then he probably didn't trip the Knox flag, but there could have been other things he did or tried to do that did trip the flag.
If it is indeed the i537, I can guarantee he did not flash a custom ROM. The i537 has a locked bootloader which means no custom recovery and no custom ROMs. However there is the ability to use TouchWiz-based ROMs, if you want to learn more about this and how it works read about SafeStrap.
We do not have official 4.2.2 stock firmware available to flash. We have a pre-release of 4.2.2, a pre-release of 4.3, official 4.3, and an OTA to go from 4.3 to 4.4.2. You can read more about the different firmwares in the i537 Firmware Thread.
Flashing firmware with Odin will erase your SIM unlock, but you can either enter the unlock code again or there are other methods that can be used. I'm not familiar with SIM unlocking so you'll have to do a little searching.
You never mentioned what you're sending the phone in for. I would try flashing the MF1 firmware first to see if it's a software issue. If it's a hardware issue then unfortunately you'll have to send it in.
Click to expand...
Click to collapse
Thank you for the quick response. I edited the first post to add more details but you must've already quoted me before I hit send.
Basically the problem is the screen will randomly detect 1, 3 or 5 nonexistent touches across the center of the screen (confirmed by enabling "show touches" in the developer options). While this is happening the touchscreen becomes unusable, rebooting several times will eventually fix it but the problem comes back randomly, sometime within a couple minutes and sometimes after several hours.
I did confirm my device is running MF3 and it is absolutely a i537. I'm using the phone on straight talk not ATT so I have not received any OTA updates beyond this point.
So,anyhow I understand I can fix the device status:custom with triangleaway but I don't understand why there is no KNOX counter in ODIN mode and how this may effect my warranty.
Also, if I did ODIN to 4.3 or 4.4 would this trip the knox counter? (Assuming it isnt tripped already).
Thanks for your input, truly appreciated!
CaseyR22 said:
Thank you for the quick response. I edited the first post to add more details but you must've already quoted me before I hit send.
Basically the problem is the screen will randomly detect 1, 3 or 5 nonexistent touches across the center of the screen (confirmed by enabling "show touches" in the developer options). While this is happening the touchscreen becomes unusable, rebooting several times will eventually fix it but the problem comes back randomly, sometime within a couple minutes and sometimes after several hours.
I did confirm my device is running MF3 and it is absolutely a i537. I'm using the phone on straight talk not ATT so I have not received any OTA updates beyond this point.
So,anyhow I understand I can fix the device status:custom with triangleaway but I don't understand why there is no KNOX counter in ODIN mode and how this may effect my warranty.
Also, if I did ODIN to 4.3 or 4.4 would this trip the knox counter? (Assuming it isnt tripped already).
Thanks for your input, truly appreciated!
Click to expand...
Click to collapse
It sounds like it might be a software issue so it would be worth it to try to flash the official 4.3 firmware. Flashing official firmware shouldn't trip the Know flag, but I'm not really an expert on Knox. I have read that Knox being tripped doesn't affect warranty repairs.
Devo7v said:
It sounds like it might be a software issue so it would be worth it to try to flash the official 4.3 firmware. Flashing official firmware shouldn't trip the Know flag, but I'm not really an expert on Knox. I have read that Knox being tripped doesn't affect warranty repairs.
Click to expand...
Click to collapse
Thanks, I went ahead and flashed 4.3 via ODIN and the KNOX status is showing 0x0 so that is a good sign. Has only been about a half hour so I cant say whether or not the touchscreen issue is fixed yet but I will post back and update what happens after a day or so.
Another plus is the update finally got rid of that god awful default font on 4.2 (changing the system font wouldn't change the fontface for plain text in the browser).
Quick update in case anyone is having a similar problem with "phantom touches" in the future.
After flashing to 4.3 the touchscreen problems have continued so i do believe it is a hardware problem that will require disassembly to fix.
Also the phone keeps trying to download the OTA update to 4.4 but I've heard bad things about the update so far so I've left my wifi turned off.
Going to be stuck using a windows 8 phone for a week or while my phone is out for warranty repair.
There is an app in the play store called phone info. There it tells you your knox status without root or being in download mode.
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
One final update in case anybody runs into similar problems in the future. Samsung confirmed it was a hardware problem and fixed the phone 100% free of charge under warranty.
It appears they replaced everything which is pretty awesome because I now have a brand new digitizer and bezel without a single scratch or scuff on them. Also my usb port cover flap was feeling pretty worn/sloppy so now thats new and even the USB port itself looks brand new which tells me the motherboard was replaced. I can tell they peeled the old serial/IMEI sticker off the old phone and stuck it on this one.
Surprisingly they didn't update it to 4.4 while it was there which kind of sucks because I'm nervous about doing it myself after reading horror stories on the forums.
Anyway I'm very pleased with Samsung's support!
On the G900A shipped from AT&T we have a locked bootloader, and there is no known existing workaround to unlock it correct?
So given that, root was achieved , then safestrap was developed so we can currently flash roms that use the stock bootloader and kernel image, however we can customize the OS as long as the kernel and loader are untouched.
If the bootloader stays locked, what is known regarding safestrap and lollipop?
Can we still rollback the stock kernel to achieve root, then roll forward and keep it?
If that is the case, then when the stock AT&T lollipop is released, some level of ROM development can occur?
I am confused somewhat by all the discussions surrounding this, and didn't see any threads to discuss it specifically.
wmunn said:
On the G900A shipped from AT&T we have a locked bootloader, and there is no known existing workaround to unlock it correct?
So given that, root was achieved , then safestrap was developed so we can currently flash roms that use the stock bootloader and kernel image, however we can customize the OS as long as the kernel and loader are untouched.
If the bootloader stays locked, what is known regarding safestrap and lollipop?
Can we still rollback the stock kernel to achieve root, then roll forward and keep it?
If that is the case, then when the stock AT&T lollipop is released, some level of ROM development can occur?
I am confused somewhat by all the discussions surrounding this, and didn't see any threads to discuss it specifically.
Click to expand...
Click to collapse
No, if you update to lollipop then your ability to have a rooted phone will be lost. The bootloader hasnt changed since the phone was released which is the reason we have been able to rollback the rom. This was a loophole in the original firmware of the s5. When lollipop comes out then it will be a completely different bootloader and will be locked and you will not be able to roll back to kk bootloader. The loophole for this has been patched and there probably wont be another way to root the phone after lollipop considering the guy that found the loophole is now working for googles security team. Bottom line is if you want root then you cant have lollipop.
Sent from my SM-G900A using XDA Free mobile app
miller1821 said:
No, if you update to lollipop then your ability to have a rooted phone will be lost. The bootloader hasnt changed since the phone was released which is the reason we have been able to rollback the rom. This was a loophole in the original firmware of the s5. When lollipop comes out then it will be a completely different bootloader and will be locked and you will not be able to roll back to kk bootloader. The loophole for this has been patched and there probably wont be another way to root the phone after lollipop considering the guy that found the loophole is now working for googles security team. Bottom line is if you want root then you cant have lollipop.
Sent from my SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
How does this affect our device when it gets the lollipop update?
http://www.xda-developers.com/android/supersu-beta-lollipop-root-stock-kernel/
wmunn said:
On the G900A shipped from AT&T we have a locked bootloader, and there is no known existing workaround to unlock it correct?
So given that, root was achieved , then safestrap was developed so we can currently flash roms that use the stock bootloader and kernel image, however we can customize the OS as long as the kernel and loader are untouched.
If the bootloader stays locked, what is known regarding safestrap and lollipop?
Can we still rollback the stock kernel to achieve root, then roll forward and keep it?
If that is the case, then when the stock AT&T lollipop is released, some level of ROM development can occur?
I am confused somewhat by all the discussions surrounding this, and didn't see any threads to discuss it specifically.
Click to expand...
Click to collapse
Thanks to chainfire the chances of updating to 5.0 while keeping root seems more doable at this point.
However, based on recent samsung updates for other devices, safestrap may stop functioning after the update as it continues its slow death.
Once again, if having root access is important to you, do no not take the 5.0 update when released until some of us have a chance to evaluate it.
Since I am running dynamic Kat on stock slot right now, I should be safe from updates for now right?
Waiting to see what happens with all this. I did back up my stock rom to an SD card, so I can restore and unroot etc... to get an update if I choose to later.
muniz_ri said:
Thanks to chainfire the chances of updating to 5.0 while keeping root seems more doable at this point.
However, based on recent samsung updates for other devices, safestrap may stop functioning after the update as it continues its slow death.
Once again, if having root access is important to you, do no not take the 5.0 update when released until some of us have a chance to evaluate it.
Click to expand...
Click to collapse
was looking for a post like this. well maybe we might get 5.1 in the next few weeks or sooner so i am sure you will give it a try and a good look and hopefully you will have success in attaining root and a good SS. seems like u da man for this...:good::good:
as for 5.1 or a custom rom...well whose to say what that will bring...
will be waiting to see what happens. will check back here when it comes out. i watch for it everyday and as usual, thank you for all your great work!
miller1821 said:
No, if you update to lollipop then your ability to have a rooted phone will be lost. The bootloader hasnt changed since the phone was released which is the reason we have been able to rollback the rom. This was a loophole in the original firmware of the s5. When lollipop comes out then it will be a completely different bootloader and will be locked and you will not be able to roll back to kk bootloader. The loophole for this has been patched and there probably wont be another way to root the phone after lollipop considering the guy that found the loophole is now working for googles security team. Bottom line is if you want root then you cant have lollipop.
Sent from my SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
Not necessarily, just because (if) the S5 gets 5.0 does not mean the ability to root will be lost just go check out the Verizon S5 forums you'll see they have a method for rooting with 5.0 that in theory should work for us as well. again it is recomended to remain on a 4.4.x rom until this has been fully evaluated.
wmunn said:
On the G900A shipped from AT&T we have a locked bootloader, and there is no known existing workaround to unlock it correct?
So given that, root was achieved , then safestrap was developed so we can currently flash roms that use the stock bootloader and kernel image, however we can customize the OS as long as the kernel and loader are untouched.
If the bootloader stays locked, what is known regarding safestrap and lollipop?
Can we still rollback the stock kernel to achieve root, then roll forward and keep it?
If that is the case, then when the stock AT&T lollipop is released, some level of ROM development can occur?
I am confused somewhat by all the discussions surrounding this, and didn't see any threads to discuss it specifically.
Click to expand...
Click to collapse
My suggestion would be not to take any updates until the root capabilities have been evaluated.
As always, research goes a long way towards alleviating fears and stopping panic attacks before they happen. be patient there are great devs here give them time to work
Well, I stopped using the S5 and switched to a oneplus one, happily running CM12 nightlies now
the att gs5 doesn't seem like it's getting any updates..
wmunn said:
Well, I stopped using the S5 and switched to a oneplus one, happily running CM12 nightlies now
Click to expand...
Click to collapse
How are you liking it? I'm seriously thinking about doing the same thing.
I have a coworker that just got the Lollipop update for his Note 3 so that means it will be coming to the S5 very soon!
There is a pre-rooted lollipop update on droid views "http://www.droidviews.com/install-rooted-lollipop-on-att-galaxy-s5-sm-g900a/" . I have updated already and it runs smoothly. The only thing is after you run the update it can take anywhere from 5 to 20 minutes to reboot so just hang tight.
silentscreamz said:
There is a pre-rooted lollipop update on droid views "http://www.droidviews.com/install-rooted-lollipop-on-att-galaxy-s5-sm-g900a/" . I have updated already and it runs smoothly. The only thing is after you run the update it can take anywhere from 5 to 20 minutes to reboot so just hang tight.
Click to expand...
Click to collapse
I used that method as well. Sure, it worked for me, but I came from Dynamic Kat, a well debloated stock rom. Due to this, after installing the update using this method, the built-in apps restore function could not complete due to having all of the useless bloatware back, taking up the extra space I was free to use in Dynamic Kat. Even removing the apps that are safe to remove via Titanium Backup doesn't help because the space is reserved for them. I've also already moved every app that it will allow to move to SD card. I've removed unneeded apps. I've gone through my internal storage to remove any unneeded files.
I've removed most of the apps listed here
This doesn't give me the Bluetooth tether that I used to us for my Gear 1(Running Null Rom). I'd look for an app to cover this but... I can't install anything because I've got no space to do so... I hope a good debloat method comes along soon. I still have root, so I'm hopeful.
Yea, bloatware is ridiculous for this phone. Have you tried the Alliance rom, that is what I run and it's not to bad for bloatware but I have only managed to get 5.6 running. Going to try version 8 today sometime. If you like to customize that is an awesome rom.
Hi folks, new to the S5 forums on here as I just upgraded from my trusty S3 on AT&T. I'm still on the stock 4.4.2 firmware, NG3 build, and I'm wondering if I should just root from here using TowelRoot method or take the 4.4.4 OTA and root from there.
Root your 4.4.2, then use the update while saving root to lollipop and skip 4.4.4 all together.
SoCalHTCFuze said:
Root your 4.4.2, then use the update while saving root to lollipop and skip 4.4.4 all together.
Click to expand...
Click to collapse
I tried to root using TowelRoot but it said device not supported. I'll do some research though. Havent even had the phone 5 hours yet.
MetalHead66 said:
I tried to root using TowelRoot but it said device not supported. I'll do some research though. Havent even had the phone 5 hours yet.
Click to expand...
Click to collapse
You gotta downgrade theres a post on here just type it in the search bar. Pretty easy process
Yes. Follow the 4.4.2 how to root thread, it says that bit still works.
OK thanks a bunch. Getting ready to do that now.
---------- Post added at 03:27 AM ---------- Previous post was at 02:53 AM ----------
Well that was quite easy and I'm a happy camper now! Just had to flash nd3 kernel with odin in order for TR to work then flash my ng3 kernel. So nice to be able to use TiBu. Helium wouldnt install all my apps. Now I can start freezing and uninstalling all the bloatware!
I recently upgraded my phone to an AT&T S5 (I decided I didn't like the S6 specs). Currently, the phone is 100% stock, unrooted. I know that previous Samsung phones had problems with OTA updates when they were rooted. Now, with the possibility that the Lollipop OTA is coming soon, I'm hesitant to root until the OTA comes out. Here are my questions:
1. Should I wait to root until after the OTA hits the streets, or is there a strategy to root and still safely apply the OTA?
2. I don't want to be one of the first to get the OTA since it may be buggy. Is there a way to delay the OTA if I'm not rooted?
So, nobody has any thoughts about this?
I can't tell you what you should do but I can tell you what I would do. I would root now, load Titanium backup, and wait for 5.0 to come out. With TBU I freeze the OTA so it's not pushed without my permission. Additionally TBU will backup everything going forward so I can easily move up and restore my apps.
I believe the current process to root will work so be patient.
woody1 said:
So, nobody has any thoughts about this?
Click to expand...
Click to collapse
I wouldn't even take the OTA. Lots of issues with it. I am pretty sure LP will be the same.
I rooted mine, installed SafeStrap, and installed the XDK ROM, which eliminates all updates. My phone works great, does everything I want it to. Don't need problematic upgrades to downgrade my system.
cmerlyn said:
I wouldn't even take the OTA. Lots of issues with it. I am pretty sure LP will be the same.
I rooted mine, installed SafeStrap, and installed the XDK ROM, which eliminates all updates. My phone works great, does everything I want it to. Don't need problematic upgrades to downgrade my system.
Click to expand...
Click to collapse
Thanks to both of you for your suggestions. I think I'm going to go ahead and root and stay on the stock rom for a while. If the OTA shows up soon and looks worthwhile, I'll give it a try. Otherwise, I'll install SafeStrap and try a custom ROM.
Sure. Here's an easy answer: if you search for S5 AT&T and lolipop, you'll find lots of things that will say that AT&T will be taking its SWEET time putting an ota upgrade for lolipop out.
It is available from Samsung thru Kies, and I think I am personally going to take a new rom, and try and upgrade and unlock this piece of junque (and I upgraded from a Galaxy SII! )
Sigh
Have n901t. Rooted it after being talked into 5.0.1 by Tmobile rep trying to improve it. No good. So went back down to KitKat and rooted that. Obviously I cannot receive ota update for 5.1.1 now. Do I just get the stock file and flash with the phone as it currently is? Or should I flash KitKat back to it's un rooted state before updating phone? Am still a novice in the taking control of your smart phone world and would rather not brick something if it can be easily avoided. Thank you.
KDawgEnigma said:
Have n901t. Rooted it after being talked into 5.0.1 by Tmobile rep trying to improve it. No good. So went back down to KitKat and rooted that. Obviously I cannot receive ota update for 5.1.1 now. Do I just get the stock file and flash with the phone as it currently is? Or should I flash KitKat back to it's un rooted state before updating phone? Am still a novice in the taking control of your smart phone world and would rather not brick something if it can be easily avoided. Thank you.
Click to expand...
Click to collapse
You could get the official software and use odin to install it but there are a couple of things you need to be aware off. First once you upgrade to 5.1.1 you cannot downgrade back to kit kat and you will be stuck on that version, secondly in order to achieve root you might need to install a custom kernel before rooting. For that last part I would suggest you hit the forums since there a couple of posts about rooting this new version.
don't know if I am ready to start messing with kernals yet. Am patient. New root will show itself before we know it. Did the update through Odin. So far smooth sailing. Tested Simpsons tapped out since with 5.0.1 it lagged so bad it was unplayable. Still not as smooth as it was on KitKat but can still play it at least. Haven't tinkered with anything else yet.
Personally I'm waiting it out. I don't like not being able to go back, and I've had 0 luck with 5+.. So I'll wait until someone "fixes" it, if ever.
So I've been out of the Android Phone loop for a while and was just wondering if there were any general tips or things to know about the Z3C? Any essential apps or features?
I've not updated to Marshmallow yet (running 5.1.1) and I don't really feel the need to, If I'm not mistaken it makes the root process a bit more fiddly, though the non-removable notification is somewhat annoying. Can it be turned off?
Quick question on root too, which I assume can only be achieved through unlocking the bootloader. Will it void my warranty with Sony? Given the issues with cracked screens and phones not really being waterproof, I'm not sure if it's actually worth doing.
I've got the Phone through Vodafone, is there anyway to remove the SIM lock myself?
I've been through the Stickies and whilst they contain useful information that'll surely come in handy later, the FAQ section is pretty limited, so I figured I'd ask here
Thanks in advance
UndisputedGuy said:
So I've been out of the Android Phone loop for a while and was just wondering if there were any general tips or things to know about the Z3C? Any essential apps or features?
I've not updated to Marshmallow yet (running 5.1.1) and I don't really feel the need to, If I'm not mistaken it makes the root process a bit more fiddly, though the non-removable notification is somewhat annoying. Can it be turned off?
Quick question on root too, which I assume can only be achieved through unlocking the bootloader. Will it void my warranty with Sony? Given the issues with cracked screens and phones not really being waterproof, I'm not sure if it's actually worth doing.
I've got the Phone through Vodafone, is there anyway to remove the SIM lock myself?
I've been through the Stickies and whilst they contain useful information that'll surely come in handy later, the FAQ section is pretty limited, so I figured I'd ask here
Thanks in advance
Click to expand...
Click to collapse
You don't need to unlock the bootloader to be able to root your phone. A good place to start is the thread on how to back up your TA partition and rooting (don't be tempted by Kingroot)
Unless you want a custom CM rom I wouldn't bother trying to unlock your bootloader, it disables features on the phone, starting with breaking the camera.
This thread about going from a rooted phone back to stock is interesting. I'd say you don't need to root your phone, but it gets a lot more interesting when you do.
The top app for if you get root is Titanium Backup, it lets you control individual apps, 'freezing' them so they stop working, but not actually uninstalling them. Great for getting rid of all the bloatware that comes with phone providers (like Sim Lock), or even manufacturers. It also lets you back up an app and all the associated data that goes with it, so if you wipe you phone to change the rom, you can put all the apps back and the state they were in at the touch of a button. There's lots of other cool root apps, but TA is my favourite.
As long as you stick to stock then you can't go wrong, don't be afraid to play, there's plenty of people on the thread here to give you a hand.
SLIM 5 is a good stock 5.1.1 rom with lots of cool tweeks and doesn't mean you have to unlock your bootloader.
Edit: Rooting your phone doesn't void your warranty. But if you face any problems with your phone that means it's going back to the service centre, just put a stock build back on (no root) and do a factory reset. That way they cannot complain about the software config. They will do a factory reset anyway, before they send it back, along with an update to the latest rom. So be prepared and take everything off your phone beforehand.
Man, that's pretty much all the information I need in one post. Thanks a bunch man, I'll read through the links in some more detail.
I did see that Rooting guide earlier, but given how it mentioned using Flashtool and DRM Keys, I thought it'd surely void my warranty so didn't have a proper look.
SLIM also seems like a good shout, though I'm assuming I'd lose access to Sony's OTA updates if I were to flash it and there doesn't seem to be a Marshmallow version yet. Actually, that said, would I even have access to OTA updates if I stay stock but rooted?
Thanks again
UndisputedGuy said:
Man, that's pretty much all the information I need in one post. Thanks a bunch man, I'll read through the links in some more detail.
I did see that Rooting guide earlier, but given how it mentioned using Flashtool and DRM Keys, I thought it'd surely void my warranty so didn't have a proper look.
SLIM also seems like a good shout, though I'm assuming I'd lose access to Sony's OTA updates if I were to flash it and there doesn't seem to be a Marshmallow version yet. Actually, that said, would I even have access to OTA updates if I stay stock but rooted?
Thanks again
Click to expand...
Click to collapse
Marshmallow has only been out a few weeks, so it's still full of bugs and problems at the moment. I would stick to 5.1.1. for at least another month, or until 6.1 reaches the Z3c.
No, if you install a custom rom then you wont get Sony OTA updates, but most rom developers base their builds on the latest firmware releases anyway, usually adopting a new release within one or two weeks.
Slim 5 is possibly the best stock Lollipop build there is and there will be no more updates for Lollopop now. There is a Slim MM build, but even though Wajk has been working his magic, it still has several bugs that need to be ironed out. If you are going down the MM route, don't be tempted by Concept or Beta, that need you to unlock your bootloader to root. Stick with a pre-rooted stock or a customised stock with root built in.
Appreciate the assistance, going to go ahead and root now and then perhaps try out SLIM 5. Some of the MEGA links seemed to be down so I just grabbed a Global FTF, couldn't seem to find an unbranded UK one.
I shouldn't have updated immediately once I got the phone
UndisputedGuy said:
Appreciate the assistance, going to go ahead and root now and then perhaps try out SLIM 5. Some of the MEGA links seemed to be down so I just grabbed a Global FTF, couldn't seem to find an unbranded UK one.
I shouldn't have updated immediately once I got the phone
Click to expand...
Click to collapse
For the purposes of downgrading so you can root, it really doesn't matter which build you choose.
Didgesteve said:
For the purposes of downgrading so you can root, it really doesn't matter which build you choose.
Click to expand...
Click to collapse
Just a quick question, at Step 26 could I just use SLIM 5? Seems much more convenient if that's the case.
Oh, and using OTA updates is going to lose me my root now, right?
UndisputedGuy said:
Just a quick question, at Step 26 could I just use SLIM 5? Seems much more convenient if that's the case.
Oh, and using OTA updates is going to lose me my root now, right?
Click to expand...
Click to collapse
Yes, once you have recovery you can download Slim onto your phone and flash that. Don't forget to update SuperSU from the playstore.
No, you wont get any OTA updates with a custom stock, but Slim is up to date with the most recent Lollipop build.
Sony PC Companion will not update your phone either once you have a custom rom on. If you flash stock and then connect it, it will push MM onto it. But you will loose root and there's no easy way to get it working.
Stick with 5.1.1. for another month, wait for 6.1 to come out, and then possibly a couple of weeks after that Wajik will have made an incredible MM rom to flash, that will be as up to date as they come, then just flash that in exactly the same way.
Edit: Once you start to follow a developers thread, they announce updates to roms almost as quick as the Sony release, so don't worry that it will get out of date, just make sure to subscribe to the thread where your rom comes from. Slim 5 for example releases an OTA update, to move from 4.9 to 5, it's a lot smaller than the entire rom and only has updates, but flashes the same way.
Can only thank you again, successfully rooted and got recovery. Not sure how much I'm really fond of SLIM, just had a very brief mess around but something felt a bit off about the Launcher and the icons even after messing with the settings. It was only very brief though, perhaps there's more useful stuff there.
Might go simply stock/rooted but given there isn't a simple .zip for it it's a bit long winded
Thanks for all your help here, this is pretty much the ideal state I wanted my phone to be in upon receiving it, had no idea unlocking the bootloader wouldn't be necessary. Guys like you help make this site in my opinion, I half just expected a couple of snide answers telling me to just read the forum
Think I will be moving back to stock, just a question on the front though
Am I going to have to build my own pre rooted image (steps 27-32) each time there's an OTA update and I want rooted stock?
Sorry, hopefully that's the last thing from me
Sent from my D5803 using XDA-Developers mobile app
UndisputedGuy said:
Think I will be moving back to stock, just a question on the front though
Am I going to have to build my own pre rooted image (steps 27-32) each time there's an OTA update and I want rooted stock?
Sorry, hopefully that's the last thing from me
Sent from my D5803 using XDA-Developers mobile app
Click to expand...
Click to collapse
There are several 'stock' options, that are flashable zips
Pre-Rooted Firmwares-Recovery-SuperSU, although you need to click on 'older files'
Or another stock thread here
But by now you should be able to start finding these threads on your own
Yeah, I've time to have a proper look through now so will do that. I saw the thread earlier, but didn't seem to notice a pre rooted .zip for the latest 5.1.1 firmware in the OP. There was one in the comments though, thanks once again