I'm rooted in the stock Touchwiz but I want to install the Lollipop AOSP ROM. How can I unlock the bootloader and install that ROM?
theycallmeryan said:
I'm rooted in the stock Touchwiz but I want to install the Lollipop AOSP ROM. How can I unlock the bootloader and install that ROM?
Click to expand...
Click to collapse
Sorry, the Verizon, and AT&T variants of the Galaxy S4 bootloaders cannot be unlocked at the moment. For the time being it will be impossible for us to install Lollipop until the official firmware release by Samsung. However, if you have a older S4 it *may* have the loki vulnerability which let's you bypass the locked bootloader. Check your About Phone and see if your running MDB or MDL.
NighthawkXL said:
Sorry, the Verizon, and AT&T variants of the Galaxy S4 bootloaders cannot be unlocked at the moment. For the time being it will be impossible for us to install Lollipop until the official firmware release by Samsung. However, if you have a older S4 it *may* have the loki vulnerability which let's you bypass the locked bootloader. Check your About Phone and see if your running MDB or MDL.
Click to expand...
Click to collapse
Here's a picture of my about phone screen. Do I have any hope?
i.imgur.co m/9ACW5Qr.png
Sorry, can't post links yet.
theycallmeryan said:
Here's a picture of my about phone screen. Do I have any hope?.
Click to expand...
Click to collapse
No dice for running Lollipop ROM's yet, however you should able to install Safestrap 3.75 and use custom 4.4.2 (and a few 4.4.4) TouchWiz-based ROM's that are floating around the forum. Poke around the threads in both the AT&T and Verizon subforums to find more information.
NighthawkXL said:
No dice for running Lollipop ROM's yet, however you should able to install Safestrap 3.75 and use custom 4.4.2 (and a few 4.4.4) TouchWiz-based ROM's that are floating around the forum. Poke around the threads in both the AT&T and Verizon subforums to find more information.
Click to expand...
Click to collapse
Damn it, I wanted to ditch TouchWiz and try Lollipop. Been thinking of switching to iPhone and I wanted to see if Lollipop was worth sticking around for.
Hi,
I don't mean to bump old threads, but I was just wondering is it still not possible to unlock the bootloader on the the s3 i535 using android 4.4.2?
I just haven't seen any recent threads........
Any help is appreciated.
ChanManDCLXVI said:
I don't mean to bump old threads, but I was just wondering is it still not possible to unlock the bootloader on the the s3 i535 using android 4.4.2?
I just haven't seen any recent threads........
Click to expand...
Click to collapse
Considering you're in the S4 forum, you're also unlikely to see any S3 threads in the future.
I'll bump this thread again since it applies. I'm on 4.4.2 NK1 can I unlock this bootloader? Should I just take the Lolipop update that keeps asking me to push through? What is my best step from here, I don't want to get stuck on something I hate.
Are there any better choices? I hate using ROM slots etc.
Thank you,
Related
I'm currently on a Galaxy S3, but I have an S4 coming in on Friday.
I saw a thread for rooting the S4, but do I need to unlock the bootloader like I did in the S3 to install a rom?
Basically, where is the thread that has all the info I need to root, unlock, and install a custom recovery for the S4?
I have one for the S3, but can't find it for the S4.
GlitchMob said:
I'm currently on a Galaxy S3, but I have an S4 coming in on Friday.
I saw a thread for rooting the S4, but do I need to unlock the bootloader like I did in the S3 to install a rom?
Basically, where is the thread that has all the info I need to root, unlock, and install a custom recovery for the S4?
I have one for the S3, but can't find it for the S4.
Click to expand...
Click to collapse
you cant find thread? How hard did you look? There is a stickie can't be missed in the general section.
BTW, the bootloader is locked for all versions of firmware since mdk.
only option is safetrap.
decaturbob said:
you cant find thread? How hard did you look? There is a stickie can't be missed in the general section.
BTW, the bootloader is locked for all versions of firmware since mdk.
only option is safetrap.
Click to expand...
Click to collapse
Okay maybe my understanding on the purpose of unlocking the bootloader is incorrect.
I thought the bootloader has to be unlocked in order to install a custom rom?
On my S3 if the bootloader wasn't unlocked the phone would brick.
Safestrap is a custom recovery so how is that relevant to bootloader? I can't seem to draw the connection.
Thanks!
GlitchMob said:
Okay maybe my understanding on the purpose of unlocking the bootloader is incorrect.
I thought the bootloader has to be unlocked in order to install a custom rom?
On my S3 if the bootloader wasn't unlocked the phone would brick.
Safestrap is a custom recovery so how is that relevant to bootloader? I can't seem to draw the connection.
Thanks!
Click to expand...
Click to collapse
plenty of threads here to read to educate yourself.
S4 bootloader is locked since mdk firmware. MDK had an exploit that Loki process allowed custom recovery
safestrap uses an exploit to work around it so its the only custom recovery for the locked bootloader.
Each subsequent firmware release locks the bootloader and exploits down further. Anyone taking the next round of kit kat OTA's will likely loose root as well.
GlitchMob said:
I'm currently on a Galaxy S3, but I have an S4 coming in on Friday.
I saw a thread for rooting the S4, but do I need to unlock the bootloader like I did in the S3 to install a rom?
Basically, where is the thread that has all the info I need to root, unlock, and install a custom recovery for the S4?
I have one for the S3, but can't find it for the S4.
Click to expand...
Click to collapse
More then likely the device you get will come with the new baseband MJ7 or MK2. You need to check this before you start messing with anything. That said the bootloader is locked up tight and you will be very limited with what you can do with it. You can root, and install safestrap(a custom recovery by Hashcode that bypasses the bootloader). This will allow you to install certain touchwiz based roms but you have to be sure they are compatible with safestrap.
Root for 4.3 baseband:
http://forum.xda-developers.com/showthread.php?t=2565758
Safestrap:
http://forum.xda-developers.com/showthread.php?t=2441441
Both these links are in the android devlopment section. It is very difficult with this device because there are multiple root methods and recovery methods depending on baseband version. If by some chance you get the phone and the baseband is MDK, DO NOT UPDATE!!!! This will allow you to install loki'ed recovery and flash any rom you want. Chances are that won"t happen though. Good luck
decaturbob said:
you cant find thread? How hard did you look? There is a stickie can't be missed in the general section.
BTW, the bootloader is locked for all versions of firmware since mdk.
only option is safetrap.
Click to expand...
Click to collapse
decaturbob said:
plenty of threads here to read to educate yourself.
S4 bootloader is locked since mdk firmware. MDK had an exploit that Loki process allowed custom recovery
safestrap uses an exploit to work around it so its the only custom recovery for the locked bootloader.
Each subsequent firmware release locks the bootloader and exploits down further. Anyone taking the next round of kit kat OTA's will likely loose root as well.
Click to expand...
Click to collapse
I understand that I need to look into it, but the way things are organized is different. I've been on an S3 for almost two years now and the forums in the S4 are just overwhelming with information that is scattered. Here is an example of what I was hoping for when I came to the S4 section.
http://forum.xda-developers.com/showthread.php?t=1762709
onemeila said:
More then likely the device you get will come with the new baseband MJ7 or MK2. You need to check this before you start messing with anything. That said the bootloader is locked up tight and you will be very limited with what you can do with it. You can root, and install safestrap(a custom recovery by Hashcode that bypasses the bootloader). This will allow you to install certain touchwiz based roms but you have to be sure they are compatible with safestrap.
Root for 4.3 baseband:
http://forum.xda-developers.com/showthread.php?t=2565758
Safestrap:
http://forum.xda-developers.com/showthread.php?t=2441441
Both these links are in the android devlopment section. It is very difficult with this device because there are multiple root methods and recovery methods depending on baseband version. If by some chance you get the phone and the baseband is MDK, DO NOT UPDATE!!!! This will allow you to install loki'ed recovery and flash any rom you want. Chances are that won"t happen though. Good luck
Click to expand...
Click to collapse
Thank you. This is the response I was looking for. As you said there are many stipulations with each baseband. This is something I am not used to coming for an S3, which is far simpler to deal with. Thanks again!
GlitchMob said:
Thank you. This is the response I was looking for. As you said there are many stipulations with each baseband. This is something I am not used to coming for an S3, which is far simpler to deal with. Thanks again!
Click to expand...
Click to collapse
The difference isn't in the baseband, it's in the bootloader. You can run a newer baseband than your bootloader, for example, especially if you have the MDK bootloader.
Since you're starting from stock, the baseband and the bootloader revisions are the same and can be found from Settings/More/About phone.
Before you flash anything, please read the what you need to know thread in the General section. Also, there's my thread in this forum.
The S4 is more complicated than the S3 largely because Samsung has really locked it down much more effectively than the S3. Consequently, there's lots of ways to go wrong. Reading first can save you a lot of grief.
k1mu said:
The difference isn't in the baseband, it's in the bootloader. You can run a newer baseband than your bootloader, for example, especially if you have the MDK bootloader.
Since you're starting from stock, the baseband and the bootloader revisions are the same and can be found from Settings/More/About phone.
Before you flash anything, please read the what you need to know thread in the General section. Also, there's my thread in this forum.
The S4 is more complicated than the S3 largely because Samsung has really locked it down much more effectively than the S3. Consequently, there's lots of ways to go wrong. Reading first can save you a lot of grief.
Click to expand...
Click to collapse
One more question. Is there a way to flash the s4 back to stock? I'll find the info on how, but going into the whole rooting and coming phase it would be nice to know that I could flash back to stock with odin. As I have with my s3.
GlitchMob said:
One more question. Is there a way to flash the s4 back to stock? I'll find the info on how, but going into the whole rooting and coming phase it would be nice to know that I could flash back to stock with odin. As I have with my s3.
Click to expand...
Click to collapse
Yes. Read the second link in my reply above - it tells you how to identify what build you're on and has links to the downloadable Odin images for each build.
k1mu said:
Yes. Read the second link in my reply above - it tells you how to identify what build you're on and has links to the downloadable Odin images for each build.
Click to expand...
Click to collapse
Thanks for your help. Turns out I'm on MJ7. I'm going to let this puppy charge while I hit the gym. I'll root it and see what rom I can install later tonight. Thanks again!! :victory:
GlitchMob said:
Thanks for your help. Turns out I'm on MJ7. I'm going to let this puppy charge while I hit the gym. I'll root it and see what rom I can install later tonight. Thanks again!! :victory:
Click to expand...
Click to collapse
Mind as well update to mk2. You can do the same as mj7 but are most up to date. Just my 2 pennies. Btw I'm on bonestock 2.1 in SS romslot 1.
Sent from my SCH-I545 using xda app-developers app
Slowbalt said:
Mind as well update to mk2. You can do the same as mj7 but are most up to date. Just my 2 pennies. Btw I'm on bonestock 2.1 in SS romslot 1.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Is there a noticeable difference? If its the same, why upgrade?
I am coming from a similar situation as you. I cracked my screen on my S3 and Asurion replaced it with an S4, which I received on Monday. I thought that I was going to be able to load SlimKat and pick up where I left off, but no.
The posts that k1mu linked are a great starting point. A few of my thoughts that I came to realize this week. These are my ways of looking at it and may not be totally correct.
The bootloader is locked and there isn't a total unlock (yet). Safestrap allows you to crack the door open a little and reach your arm in to grab a few things.
You will need to stick with ROMs that work with the TouchWiz kernel. The post that k1mu referenced has a link to compatible ROMs. You will not be able to load SlimKat, CM, Carbon, etc. Basically any ROM you choose will have TW underneath. Some of the ROMs will try to look like an ASOP, but it is still a TW base.
Safestrap will allow you to create ROM slots where you can try out the ROM to see if you like it. I am still trying to decide what I want to use. Currently I have Hyperdrive as the leader. Everything that I do continues to work. The Eclipse ROM looks good but it is not quite there yet, but he is working on a build in the next couple days. Here is a link to their website with more up to date status. Eclipse . I also looked at the Foxhound ROM and it is good also. For me support and future upgrades are the most important. I am starting to think that i will embrace TW instead of trying to cover it up and will go with Hyperdrive.
If you use TiBu, read this post, especially with Hyperdrive http://forum.xda-developers.com/showthread.php?t=2653044.
The other realization that hit me was that while Safestrap can create partitions for loading different ROMs, each one is restricted to a maximum of a 3GB /data partition. When I tried to restore all of my apps this was quickly used up. It isn't supported by Safestrap to flash to the stock location, but it can and has been done. Since Safestrap isn't doing a flash there are more risks and I think that this should probably be kept to a minimum. This is where you want to test all the candidate ROMs first and then decide which one to use and then flash to the stock location. Obviously this could cause problems with the phone and would use ODIN as a fallback. Unless something get totally hosed and then you are out of a phone.
One thing that I realized a long time ago is that when you change devices you may want to do everything exactly the way it was before. On the phone or even when looking for information. But in most cases it is better to change your processes or work flow to work with the new device than it is to change the device to work in your previous work flow.
Hello,
I have a Galaxy S4 Developers Edition (SCH-I545, running Android 4.2.2), Baseband version YUAMDK. I would like to install Kitkat on it. The problem is that I cant seem to find clear instrcutions on what I need to do to install a different ROM on it. Can some one please help. Also as a side question, where can I find the stock samsung kitkat ROM for our phone.
Thank you
Amir
silver7x said:
Hello,
I have a Galaxy S4 Developers Edition (SCH-I545, running Android 4.2.2), Baseband version YUAMDK. I would like to install Kitkat on it. The problem is that I cant seem to find clear instrcutions on what I need to do to install a different ROM on it. Can some one please help. Also as a side question, where can I find the stock samsung kitkat ROM for our phone.
Thank you
Amir
Click to expand...
Click to collapse
KitKat hasn't been released on Verizon yet.
riker147 said:
KitKat hasn't been released on Verizon yet.
Click to expand...
Click to collapse
Thank you, is the process for being able to to load another ROM... all the ones I have seen are not for the Developers edition.
Thanks again.
silver7x said:
Thank you, is the process for being able to to load another ROM... all the ones I have seen are not for the Developers edition.
Thanks again.
Click to expand...
Click to collapse
You have a Developer Edition S4, you can flash just about any ROM you want on it...it has an unlocked bootloader. Not sure what recovery you have, but you'll need a custom recovery like TWRP (I recommend 2.5.0.2) or PhilZ. Either one of those can be found in this forum. The one thing you don't want to do is take an Over The Air Update from Verizon...or anywhere else for that matter. Your in good shape for flashing just about anything as long as you don't change/replace your bootloader. I haven't seen any ROMs on this forum that touches the bootloader. There are a number of good ROMs available. Just follow the Developer's installation instructions. If you're looking for a really good TW ROM I recommend trying Eclipse 3.0.
silver7x said:
Hello,
I have a Galaxy S4 Developers Edition (SCH-I545, running Android 4.2.2), Baseband version YUAMDK. I would like to install Kitkat on it. The problem is that I cant seem to find clear instrcutions on what I need to do to install a different ROM on it. Can some one please help. Also as a side question, where can I find the stock samsung kitkat ROM for our phone.
Thank you
Amir
Click to expand...
Click to collapse
Here is a good thread for you to read. It probably answers a lot of your questions: http://forum.xda-developers.com/showthread.php?t=2578569
Just keep in mind there is no factory image for the dev edition Gs4, (each developer edition device supposedly has a slightly different aboot) this is why no ota updates from big red.
I dont know how to do it but get some advice on how to back up your factory firmware before going to far. If this is even possible without a custom recovery????
Don't make the mistake I made and get a soft brick and have to flash a consumer version of mdk. My bootloader is now locked but at least I am still mdk with custom recovery and flashing capability.
Sent from my SCH-I545 using xda app-developers app
Will the process link below work on a rooted/safestraped VZW Galaxy S4 (currently running Hyperdrive)? It describes putting CM12 (Lollipop) on the GS4. I'm thinking not but want to check with the wise people on the forum.
http://www.gizbot.com/mobile/how-in...n-samsung-galaxy-s4-10-easy-steps-020694.html
thanks
kylo77 said:
Will the process link below work on a rooted/safestraped VZW Galaxy S4 (currently running Hyperdrive)? It describes putting CM12 (Lollipop) on the GS4. I'm thinking not but want to check with the wise people on the forum.
http://www.gizbot.com/mobile/how-in...n-samsung-galaxy-s4-10-easy-steps-020694.html
thanks
Click to expand...
Click to collapse
No this will not work you need a custom recovery Safestrap WILL NOT WORk with this.
kylo77 said:
Will the process link below work on a rooted/safestraped VZW Galaxy S4 (currently running Hyperdrive)? It describes putting CM12 (Lollipop) on the GS4. I'm thinking not but want to check with the wise people on the forum.
http://www.gizbot.com/mobile/how-in...n-samsung-galaxy-s4-10-easy-steps-020694.html
thanks
Click to expand...
Click to collapse
Until we get Kexec to run on the GS4, you will not be able to. Unless you have an unlocked bootloader and/or haven't upgraded to 4.2+ yet then you can do it right now.
I'm helping my friend install CyanogenMod 12 on his S4 (jfltevzw). We've rooted it and we're currently doing a full backup through Safestrap in case anything happens. Once that's finished, I'm unsure as to what we should do. CyanogenMod's wiki has installation instructions for the Verizon S4, but it says in big bold letters to not attempt this if on a ROM newer than I545VRUAMDK. He's on the latest version that Samsung/Verizon have pushed out, which is I545VRUFNK1. Is there an alternate way to install CyanogenMod on top of the newer stock ROM, or is it not possible?
vaindil said:
I'm helping my friend install CyanogenMod 12 on his S4 (jfltevzw). We've rooted it and we're currently doing a full backup through Safestrap in case anything happens. Once that's finished, I'm unsure as to what we should do. CyanogenMod's wiki has installation instructions for the Verizon S4, but it says in big bold letters to not attempt this if on a ROM newer than I545VRUAMDK. He's on the latest version that Samsung/Verizon have pushed out, which is I545VRUFNK1. Is there an alternate way to install CyanogenMod on top of the newer stock ROM, or is it not possible?
Click to expand...
Click to collapse
its not possible. ONLY mdk builds will work.
Raymondlikesroot said:
its not possible. ONLY mdk builds will work.
Click to expand...
Click to collapse
Dang, so there's absolutely nothing whatsoever that can be done? The page says you can't downgrade, but is anything at all possible now that he's beyond the MDK build? He really wants to make the switch and is fine with doing a complete wipe or whatever is necessary.
EDIT: I've been trying to read up on the VZW S4 and why this isn't possible, but I don't quite get it. Reading other threads it seems like the reason is because the bootloader is locked, but that can't be the case if he was able to install Safestrap. I'm coming from a Nexus 5 where everything is incredibly simple, so I apologize for my ignorance. (I don't mean to say you're wrong or anything as I have no idea myself, I just don't understand why it doesn't work on newer ROMs.)
vaindil said:
Dang, so there's absolutely nothing whatsoever that can be done? The page says you can't downgrade, but is anything at all possible now that he's beyond the MDK build? He really wants to make the switch and is fine with doing a complete wipe or whatever is necessary.
EDIT: I've been trying to read up on the VZW S4 and why this isn't possible, but I don't quite get it. Reading other threads it seems like the reason is because the bootloader is locked, but that can't be the case if he was able to install Safestrap. I'm coming from a Nexus 5 where everything is incredibly simple, so I apologize for my ignorance. (I don't mean to say you're wrong or anything as I have no idea myself, I just don't understand why it doesn't work on newer ROMs.)
Click to expand...
Click to collapse
The reason we use Safestrap as opposed to twrp is because the bootloader is locked.
Surge1223 said:
The reason we use Safestrap as opposed to twrp is because the bootloader is locked.
Click to expand...
Click to collapse
Oh, okay. Really unfortunate that this isn't possible now. So he's just stuck with TouchWiz and can't do anything about it?
vaindil said:
Oh, okay. Really unfortunate that this isn't possible now. So he's just stuck with TouchWiz and can't do anything about it?
Click to expand...
Click to collapse
Yep
Sent from my my Lollipopped S4
vaindil said:
Oh, okay. Really unfortunate that this isn't possible now. So he's just stuck with TouchWiz and can't do anything about it?
Click to expand...
Click to collapse
you can install hyperdrive rom
its not lolipop but its worlds better then stock ...
also there is a chance of getting the 5.01 GPE edition rom running when Samsung releases the lolipop update for the vz s4
that would at least give us a working lolipop kernel to use with the gpe rombase
and hey you never know there could be a exploite in the lolipop rom/kernel that lets us get kexec working
Basically safestrap loads after the kernel but early enough to replace point to a different root for the system. So we can load what ever system we want... But are stuck with the kernel the phone booted. If the system is based on the stock kernel this is fine... But when it starts making calls to custom kernel stuff you will have trouble.
So Cyanogenmod only provides the GUI? I've installed CM on two B&N tablets and I've been asked to root a new Verizon Samsung Galaxy S4. I've assumed that, because it's new, it will have I545VRUFNK1 4.4.2. I rooted my VSG s3 years ago to 4.3 and there was no going back on that one. It looks like it's the same with VSG s4. So, if CM provides only the GUI, then a rooted VSG s4 can still access Google Apps? What is the concern with with TW based ROMs? Is it the recovery/backup feature or only being stuck with the VSG s4 GUI?
Raymondlikesroot said:
its not possible. ONLY mdk builds will work.
Click to expand...
Click to collapse
This explains why I bricked my phone when I tried to flash CM12...
ryant35 said:
This explains why I bricked my phone when I tried to flash CM12...
Click to expand...
Click to collapse
haha yeah, that could maybe potentially probably be the issue. Just maybe.
Couldn't you ODIN back to an older baseband version and then try to flash CM12?
Lockett said:
Couldn't you ODIN back to an older baseband version and then try to flash CM12?
Click to expand...
Click to collapse
Nope, in order to get CM, you'll need to be on MDK. Samsung prevents downgrading.
btw. the baseband version doesn't matter much. Its the bootloader version that is the toughie.
Boo! I just picked up my S4 yesterday after a 5 month run of using Windows Phone so I'm trying to figure this phone out. I'm on NK1 and trying to figure out how to root now.
vaindil where did you find a VRUFNK1 compatible version of Safestrip?
Yesterday Verizon posted information about the lollipop update 5.0.1.
I'm assuming that the current 5.73 SafeStrap will not work with the stock 5.0.1 firmware. Do any devs have an idea how to load Roms onto the s4 after the update? Or do we assume that anyone not running an MDK bootloader is stuck in 4.4.x based or with the stock 5.0.1 TW?
mkglitzman said:
Yesterday Verizon posted information about the lollipop update 5.0.1.
I'm assuming that the current 5.73 SafeStrap will not work with the stock 5.0.1 firmware. Do any devs have an idea how to load Roms onto the s4 after the update? Or do we assume that anyone not running an MDK bootloader is stuck in 4.4.x based or with the stock 5.0.1 TW?
Click to expand...
Click to collapse
I would say wait and see. I have been seeing other updates to 5.0 also updating the bootloader. Maybe a new exploit in there? I would wait to take the update until either A: It is confirmed that SS will/will not work or B: they find a new exploit to use.
Currently, there is no new exploits for lollipop, and there is no rooting method to lollipop. If you REALLY want lollipop, I suggest you flash NC5 and then use software update to update all the way to lollipop.
mcbeat257 said:
Currently, there is no new exploits for lollipop, and there is no rooting method to lollipop. If you REALLY want lollipop, I suggest you flash NC5 and then use software update to update all the way to lollipop.
Click to expand...
Click to collapse
Waiting on a boot.img so we can get the 5.01 GPE rom to run under safestrap ...
I gotta say, they did update the recovery modules, and the boot modules too. The only downside is that they did not implement certain features that the galaxy s5 right now has, but overall probably the best update yet. Plus it is pretty smooth.
mcbeat257 said:
I gotta say, they did update the recovery modules, and the boot modules too. The only downside is that they did not implement certain features that the galaxy s5 right now has, but overall probably the best update yet. Plus it is pretty smooth.
Click to expand...
Click to collapse
touchwizz is still crap tho
I can agree with that. I updated this morning. I'm disappointed that the s5 camera and the favorites in messenger didn't make it into the update, but I can't complain. It's still lollipop.
Sent from my SCH-I545 using XDA Free mobile app
I presume that this update loses (unpaid) WiFi tether?
Currently on rooted NG6 with tether modules on VZW unlimited. Keeping tether is the only mandatory feature for me.
Wait?
There are guides out there to upgrade and keep root.i would advise using one of those.
If you upgrade to the OTA OC1 you will be on another locked boot loader with no way to downgrade back to Kitkat if you don't like it.
Currently as it stands, there's no root for OTA OC1. There's also no Safestrap that will work with it and no way to Odin back to nc5 once you do the OTA upgrade.
Development Forums are for developers to share their work and post their Roms and Mods.
Questions belong in the Q&A section.
Thread has been moved to correct section, please pay attention to XDA rules.
.
Tw.5