Related
My Captivate is 100% factory, never rooted, never flashed, etc. Some day I will want root and will want to unlock it.
Should I do these things today, prior to Froyo or will it really matter?
I've read about rooting and saving a copy of the folder containing the lock files. Should I do this today?
Will the official Froyo be just as easy to root and to unlock the phone?
Did I post this in the wrong forum? Should it be in General?
There is already a couple roms built on the upcoming froyo. My point is the devs know how to root and enable sideloading. Does not matter, although most custom roms are already more advanced then the froyo being released
if you're planning on unlocking, I suggest doing it before Froyo. Froyo introduced some tricks to prevent finding the unlock code on the phone, so the current method requires you to replace your EFS files with "blank" ones that have the potential for trashing your IMEI/connection (though EXTREMELY unlikely, but very troublesome)
If you root you may not be able to update. Unlocking is not rooting. Unlocking should survive an update, rooting will not. I wouldn't do anything to the phone prior to the Foryo update. If something goes wrong you can blame AT$T/Samsung and get a replacement. If something goes wrong because of something you did before the update, you'll be SOL.
I have been waiting for a few weeks for an OTA update from 3.195 to a major version, and finally this update has arrived today (v3.223). But some things have caught my attention:
First: update size is about 0.1 Mb, and Update Center says that "a computer is required". In other words, it forces me to use PC Companion. But I don't want to lose root (I'm on locked bootloader), so I want/need to update through OTA and cross my fingers so that black79one method will still works.
Second: I was waiting this update to confirm if CWM has impact on the update itself, as others have supposedly reported before (but no one confirmed).
Surprisingly, after remove CWM and reboot the device, no OTA update is available! So CWM apparently has impact over OTA updates. Now I can only wait for a new update notification, and if this update will be a full update "Over The Air".
EDIT: A few hours later the update is still available, same result: 0.1 Mb and "a computer is required" (of course this time without CWM). Just waiting for a truly and fully OTA update to 3.223 (or whichever version).
More stuff to conclude this little interesting thread about updates and recoveries:
Checking the option to allow updates automatically in the Update Center settings triggers the update to be downloaded by trully OTA. But after 20 minutes waiting, the download progress bar remains empty. Looking at the wifi icon, it displays activity, then pause, then activity again, and so on.
Then I remembered that root blocks OTA updates (dammed memory...) so I had unroot my device but this does not change nothing: 0.1 Mb 3.223 update and progress bar remaining empty.
So I started to play with some things:
Flash a clean 3.195 tft with flashtool and force an update search, same result as earlier. CWM is evidently out of scene now.
Flash a clean 1.303 tft with flashtool and force an update search, with some interesting result: an update is available, but for 3.195 firmware (not latest 3.223). After update to the first, a new update search attempt offers no version to update. Anyway I'm sure that if this happened it would be the 0.1 Mb update along with the now famous SAME ****ING RESULT AS ALWAYS.
At this point is clear to me that 3.223 versión is not a fully and truly OTA update, but is still pending to prove if CWM allows such update kind. So I tried this:
Flash a clean 1.303 tft with flashtool and force an update search, download the update, follow the black79one method to root, install CWM and finally done the update. Result: device is restarted, then the update begins but a few seconds later it's interrupted. Remove CWM with my removal tool does not help (same result).
So INSTALL CWM DOES NOT ALLOW OTA UPDATES ANYMORE. I think the recovery partition is overrided at some point and the only way to lead back the OTA functionality is recover the original recovery (amazing pun ). I tried some minimal flashtool flashing (only fotakernel.sin and loader.sin) but does not help.
For the moment my work ends here. If anyone could give ideas they will be welcome.
Why not just bite the bullet and flash the 223 ftf and have done with it? If you are happy to flash stuff already, then
there seems little reason to worry about either a) bricking your 'phone or b) having to send it back because of a).
You've already taken various steps with your 'phone, be brave!
Unless I am missing something, which I may well be, I am fairly new to all this, but in truth I did all sorts to my new
Xperia T without too much worry, it's okay.
davidmarco said:
More stuff to conclude this little interesting thread about updates and recoveries:
Checking the option to allow updates automatically in the Update Center settings triggers the update to be downloaded by trully OTA. But after 20 minutes waiting, the download progress bar remains empty. Looking at the wifi icon, it displays activity, then pause, then activity again, and so on.
Then I remembered that root blocks OTA updates (dammed memory...) so I had unroot my device but this does not change nothing: 0.1 Mb 3.223 update and progress bar remaining empty.
So I started to play with some things:
Flash a clean 3.195 tft with flashtool and force an update search, same result as earlier. CWM is evidently out of scene now.
Flash a clean 1.303 tft with flashtool and force an update search, with some interesting result: an update is available, but for 3.195 firmware (not latest 3.223). After update to the first, a new update search attempt offers no version to update. Anyway I'm sure that if this happened it would be the 0.1 Mb update along with the now famous SAME ****ING RESULT AS ALWAYS.
At this point is clear to me that 3.223 versión is not a fully and truly OTA update, but is still pending to prove if CWM allows such update kind. So I tried this:
Flash a clean 1.303 tft with flashtool and force an update search, download the update, follow the black79one method to root, install CWM and finally done the update. Result: device is restarted, then the update begins but a few seconds later it's interrupted. Remove CWM with my removal tool does not help (same result).
So INSTALL CWM DOES NOT ALLOW OTA UPDATES ANYMORE. I think the recovery partition is overrided at some point and the only way to lead back the OTA functionality is recover the original recovery (amazing pun ). I tried some minimal flashtool flashing (only fotakernel.sin and loader.sin) but does not help.
For the moment my work ends here. If anyone could give ideas they will be welcome.
Click to expand...
Click to collapse
TheGSL said:
Why not just bite the bullet and flash the 223 ftf and have done with it? If you are happy to flash stuff already, then
there seems little reason to worry about either a) bricking your 'phone or b) having to send it back because of a).
You've already taken various steps with your 'phone, be brave!
Click to expand...
Click to collapse
Because I don't want to lose root, and both 195 and 223 tft's are not rootable at this time if you are in locked bootloader.
I know there is a workaround, flashing a rooted 223 firmware through CWM, but the intention of this thread was to demonstrate if CWM allows OTA update, nothing more. Now that it is demonstrated, such intention is how to fully revert CWM.
Okay, I understand that, but I guess I should of been clearer above too, in that, does it matter that much about unlocking your bootloader?
Is it because you want to protect your warranty? If that is the reason I understand your concerns, it is just as I say, perhaps foolishly, I
unlocked mine and rooted my T almost as soon as I got it, without really knowing 100 percent what I was doing! (true) but understanding
why I wanted to have root access (mainly at the moment to uninstall dross like Facebook and Twitter that are pre-installed and to be
able to decide what apps do what on my 'phone) - I understood the risks and took them, as have many people, and lived to tell the
tale.
I do not have the technical know how to help with the cwm query, sorry.
davidmarco said:
Because I don't want to lose root, and both 195 and 223 tft's are not rootable at this time if you are in locked bootloader.
I know there is a workaround, flashing a rooted 223 firmware through CWM, but the intention of this thread was to demonstrate if CWM allows OTA update, nothing more. Now that it is demonstrated, such intention is how to fully revert CWM.
Click to expand...
Click to collapse
TheGSL said:
Okay, I understand that, but I guess I should of been clearer above too, in that, does it matter that much about unlocking your bootloader?
Is it because you want to protect your warranty? If that is the reason I understand your concerns, it is just as I say, perhaps foolishly, I
unlocked mine and rooted my T almost as soon as I got it, without really knowing 100 percent what I was doing! (true) but understanding
why I wanted to have root access (mainly at the moment to uninstall dross like Facebook and Twitter that are pre-installed and to be
able to decide what apps do what on my 'phone) - I understood the risks and took them, as have many people, and lived to tell the
tale.
I do not have the technical know how to help with the cwm query, sorry.
Click to expand...
Click to collapse
Don't worry mate, everyone is welcome to this discussion and their opinions will be very appreciated
Is not a matter of fear, I contacted with Sony technical support in Spain a few days after to bought my phone (they unlock your bootloader with no cost if you can provide a valid sim unlock code) but they misbehaved to me: the carrier never came to pick up the device, and when I sent a new email to show my annoyance and request a new pick up they simply didn't response me. After that, I decided to not send my phone and live with locked bootloader.
So I actually don't have the S5, or any Samsung device for that matter, but a friend of mine does, and really wants to root their phone. I had no idea the AT&T S5 was so secure, but it's pretty interesting too. I've been researching for over 15 hours. I may not have been able to root his phone, but I think I have learned a couple things and maybe some possible root methods.
1.) Since using ODIN to downgrade would soft brick the phone, would it be possible to download the stock Lollipop update onto a computer, give the update super user access, replace the recovery with a custom one, or unlock the bootloader from the computer, then flash it through ODIN?
2.) Intercept any sort of OTA update, then alter it to flash a custom recovery or unlock bootloader? I don't know how you would go around this though.
3.) If someone hasn't taken the OTA update that patched the Stagefright exploit, could someone purposely use the exploit to allow installation of a custom recovery or even to unlock the bootloader since the Stagefright bug has super user access (or so I've heard).
Also, I'm sorry if these are stupid ideas. I know close to nothing about Samsung so everything I'm basing this off of is what I've read in the past 15 hours.
jsmithfms said:
So I actually don't have the S5, or any Samsung device for that matter, but a friend of mine does, and really wants to root their phone. I had no idea the AT&T S5 was so secure, but it's pretty interesting too. I've been researching for over 15 hours. I may not have been able to root his phone, but I think I have learned a couple things and maybe some possible root methods.
1.) Since using ODIN to downgrade would soft brick the phone, would it be possible to download the stock Lollipop update onto a computer, give the update super user access, replace the recovery with a custom one, or unlock the bootloader from the computer, then flash it through ODIN?
2.) Intercept any sort of OTA update, then alter it to flash a custom recovery or unlock bootloader? I don't know how you would go around this though.
3.) If someone hasn't taken the OTA update that patched the Stagefright exploit, could someone purposely use the exploit to allow installation of a custom recovery or even to unlock the bootloader since the Stagefright bug has super user access (or so I've heard).
Also, I'm sorry if these are stupid ideas. I know close to nothing about Samsung so everything I'm basing this off of is what I've read in the past 15 hours.
Click to expand...
Click to collapse
The issue is that AT&T (and Verizon) use an encrypted signature key to verify they are the correct unaltered files as well as the means to unlock the bootloader to allow the OTA. Without that key, the tasks you mention are near impossible. They are not stupid ideas at all..just very difficult with all the security checks included.
KennyG123 said:
The issue is that AT&T (and Verizon) use an encrypted signature key to verify they are the correct unaltered files as well as the means to unlock the bootloader to allow the OTA. Without that key, the tasks you mention are near impossible. They are not stupid ideas at all..just very difficult with all the security checks included.
Click to expand...
Click to collapse
Crap... well does anyone know how that encyption key is generated? Like, could I theoretically get an algorithm from a ROM?
Honestly for the time being I wouldn't bother with ROMS for that Device and carrier at the moment. Especially being that its someone elses device. Towelroot should be a good start. If Im not mistaken I don't think its supposed to trip knox.
Sent from my HTCEVODesign4G using XDA Free mobile app
jsmithfms said:
Crap... well does anyone know how that encyption key is generated? Like, could I theoretically get an algorithm from a ROM?
Click to expand...
Click to collapse
This is the riddle of the Sphinx my friend. I am sure the super devs have tried their best so far to crack it. It has been an ongoing effort to make phones more and more secure, not against the amateur developers and rooters, but against the hackers. These smartphones are now our personal computers, diaries, personal assistants, financial operator, and more. They basically are a person's (and business's) life. AT&T and Verizon have taken the big steps to appeal to the Exchange clients, corporate, government and military contracts. Even the general public want to know their phone is secure. This is what keeps me stuck on the Sprint network.
Have you tried Kingroot?
I successfully rooted my wife's AT&T S4 on OC3 lollipop (supposedly unrootable) with the desktop version. Mobile version didn't work but desktop did without a hiccup. Maybe it'll work on the S5.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Rockin' a l337 with Goldeneye v49.1 + Wanam Xposed and loving life on AT&T's 4G LTE network
S5 on lollipop has a new nasty boot loader.... it was a miracle on its own that they ever came up with safestrap to duck the boot loader on earlier versions of android
So in the process of developing a rooted OG5, I locked myself out with the new bootloader.
Details, for those interested: I wanted to get everything (kernel, bootloader, etc) on OF1, since it's the easiest way to patch things, and I have only been on OF1 system + modem. So I made a OF1 flashable package including everything except system, which I left as a stock not-cleaned odexed rooted build I through together. Well it flashed fine, but upon boot it recognized that the system was of the old SYS_MAGIC value (1 as compared to 2), so.... yeah. It wouldn't let me boot. I should've thought ahead, so it's my fault, but...
Okay, so what I would want for someone on my rooted OF1 (if lower, move up to my OF1, not the official!) to try something that may work, but probably not. At the very end of the stock OF1 (and OG5) update package it updates that SYS_MAGIC value to 2, so you can't go down to anything 1 (OE2, OC3, etc). But if we're rooted maybe we could use FlashFire to flash a custom made package that ONLY includes this magic updater. command This would leave the system on my rooted OF1, but allow booting when flashing everything else (kernel, bootloader, etc). It's a two step process, though, because if it works (ONLY if it does, which you'll know) you'll need to flash all that other stuff right away/after.
I have packages ready, but I won't post them here because this is gray territory... It won't break anything permanently, but there's always a slim chance you'd have to flash a full OF1 package, losing root. so If you're okay with that, message me. Mine as well try, since there isn't anything else I can do anymore...
So now you are not rooted anymore???
Did you get any takers yet?
Looking like all hope is lost for 5.1.1 root. Thanks for trying @trailblazer101
trailblazer101 said:
So in the process of developing a rooted OG5, I locked myself out with the new bootloader.
Details, for those interested: I wanted to get everything (kernel, bootloader, etc) on OF1, since it's the easiest way to patch things, and I have only been on OF1 system + modem. So I made a OF1 flashable package including everything except system, which I left as a stock not-cleaned odexed rooted build I through together. Well it flashed fine, but upon boot it recognized that the system was of the old SYS_MAGIC value (1 as compared to 2), so.... yeah. It wouldn't let me boot. I should've thought ahead, so it's my fault, but...
Okay, so what I would want for someone on my rooted OF1 (if lower, move up to my OF1, not the official!) to try something that may work, but probably not. At the very end of the stock OF1 (and OG5) update package it updates that SYS_MAGIC value to 2, so you can't go down to anything 1 (OE2, OC3, etc). But if we're rooted maybe we could use FlashFire to flash a custom made package that ONLY includes this magic updater. command This would leave the system on my rooted OF1, but allow booting when flashing everything else (kernel, bootloader, etc). It's a two step process, though, because if it works (ONLY if it does, which you'll know) you'll need to flash all that other stuff right away/after.
I have packages ready, but I won't post them here because this is gray territory... It won't break anything permanently, but there's always a slim chance you'd have to flash a full OF1 package, losing root. so If you're okay with that, message me. Mine as well try, since there isn't anything else I can do anymore...
Click to expand...
Click to collapse
Actually, I have been thinking about this myself and I agree with your observations...
In addition to... I think its a vendor partition that holds this info and it can surely be changed some how. I noticed it the same way you did however, I used a "loaner" device from VZW. I thought I had power button issues but nothing a good cleaning with Canned air cant fix. So I sent the "loaner" back (which BTW could not boot because of all the testing I did) and just let the process go. However, now that I have seen your post (which I agree with) you either
A. Solidified my thought process
B. Guessed and theorized for 7 days with a loaner phone lol, like I did...
Either way... I think we are both looking at this the same. And I think it has to do with the kernel build date. I will tear down the boot.img tomorrow and see what I can figure out.
scrosler said:
Actually, I have been thinking about this myself and I agree with your observations...
In addition to... I think its a vendor partition that holds this info and it can surely be changed some how. I noticed it the same way you did however, I used a "loaner" device from VZW. I thought I had power button issues but nothing a good cleaning with Canned air cant fix. So I sent the "loaner" back (which BTW could not boot because of all the testing I did) and just let the process go. However, now that I have seen your post (which I agree with) you either
A. Solidified my thought process
B. Guessed and theorized for 7 days with a loaner phone lol, like I did...
Either way... I think we are both looking at this the same. And I think it has to do with the kernel build date. I will tear down the boot.img tomorrow and see what I can figure out.
Click to expand...
Click to collapse
i currently have a vzw s6 on og5 that ill be sending back.. unfortunately it wont help the cause..
i figured it would not work but worth a shot.. hopefully someone willing to sacrifice root potentially will take the dive :-/..
you guys are more experienced with android than i am for sure!
Extreme Syndicate L
elliwigy said:
i currently have a vzw s6 on og5 that ill be sending back.. unfortunately it wont help the cause..
i figured it would not work but worth a shot.. hopefully someone willing to sacrifice root potentially will take the dive :-/..
you guys are more experienced with android than i am for sure!
Extreme Syndicate L
Click to expand...
Click to collapse
I'm considering getting rid of s6 edge in the next couple of days. If my plan comes through I will test your theory prior to selling my phone
Sent from my SM-G925V using Xparent Green Tapatalk 2
trailblazer101 said:
So in the process of developing a rooted OG5, I locked myself out with the new bootloader.
Details, for those interested: I wanted to get everything (kernel, bootloader, etc) on OF1, since it's the easiest way to patch things, and I have only been on OF1 system + modem. So I made a OF1 flashable package including everything except system, which I left as a stock not-cleaned odexed rooted build I through together. Well it flashed fine, but upon boot it recognized that the system was of the old SYS_MAGIC value (1 as compared to 2), so.... yeah. It wouldn't let me boot. I should've thought ahead, so it's my fault, but...
Okay, so what I would want for someone on my rooted OF1 (if lower, move up to my OF1, not the official!) to try something that may work, but probably not. At the very end of the stock OF1 (and OG5) update package it updates that SYS_MAGIC value to 2, so you can't go down to anything 1 (OE2, OC3, etc). But if we're rooted maybe we could use FlashFire to flash a custom made package that ONLY includes this magic updater. command This would leave the system on my rooted OF1, but allow booting when flashing everything else (kernel, bootloader, etc). It's a two step process, though, because if it works (ONLY if it does, which you'll know) you'll need to flash all that other stuff right away/after.
I have packages ready, but I won't post them here because this is gray territory... It won't break anything permanently, but there's always a slim chance you'd have to flash a full OF1 package, losing root. so If you're okay with that, message me. Mine as well try, since there isn't anything else I can do anymore...
Click to expand...
Click to collapse
I'd be happy to test this out; I don't mind losing root if it comes to that.
Let me know what needs done and I'll try to help out also...
Sent from my SM-G925V using Tapatalk
pm sent trailblazer, lmk
PM'd. Willing to take the plunge!
I'm on OG5, so I wouldn't be much help..
Have you guys heard any news? Unfortunately, I am pretty close to being done with using the old software version and the bugs it comes with, just to retain root.
It's really nice to have, but with (hopefully) Samsung Pay around the corner, I'm likely going to be throwing in the towel since it will require a software update.
haven't heard anything from OP
I'm pretty sure no one is working on rooting this device for OF1 and above anymore.
Sent from my SM-G925V using Tapatalk
its not a matter if anyone is working on root for of1 since roots are typically exploits in the android os so new root methods are typically based on OS... for example, if root is done for android 5.1 it might work on OG5 5.1 for us..
known exploits for 5.0 were patched in OFx firmwares so new exploits need to be found in general.
Sent from my SM-G925V using XDA Free mobile app
Would love to know if this worked. I really want to update to 5.1.1 and see how it is for myself but don't want to lose the ability to downgrade again. I may end up just doing it anyways though so I might as well test this in the process. I've been seeing that no one's gotten a response though
Sent from my SM-G920V using XDA Free mobile app
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