Related
I am about to get a Moto X from Verizon and I know it has a locked bootloader
I never dealt with a locked phone in the past and this will be my first moto so I am doing a lot of reading
Correct me if I'm wrong, but I guess the phone will come with 4.2 on it so I'll have two options:
1) Use safestrap and flash 4.4 as a second rom. I am guessing the disadvantage will be loss of disk space for the second rom (maybe other disadvantages, I don't know) but I'll be able to do nandroid backups and flash zips
2) Use the JCase method to root using SlapMyMoto and MotoWpNoMo, etc. (I'll be rooted, but no flashing roms or zips, or nandroid backups)
In that case, which method do you guys really recommend? Do I really need custom roms on this phone since it is almost stock and I can still get xposed to do a lot of the things I'd be interested in with just the root?
If I use the JCase method, do I lose the ability to use safestrap in the future?
Thanks
The moto xs leaving moto maker for Verizon should all be 4.4 at this point. Can't whole heartedly speak to your other questions though.
Sent from my SCH-I925 using Tapatalk
I used to be a flash-o-holic and so far I'm perfectly satisfied with just having root and xposed
sent from my Moto X
I'm rooted, using xposed and gravity box. Very happy with phone. Came from an s3 and have to say I don't miss flashing Roms. Real learning curve for me to root but JCase methods worked perfect and google was my friend through the many steps. Good luck!
Sent from my XT1060 using Tapatalk
SlapMyMoto. You're not gonna want to flash roms on this phone.
Thanks for the replies.
I guess if the phone comes with 4.4 already, I only have the JCase's root option, anyway.
But reading the replies here as well as other threads, I see that most people are pretty content with the stock rom + root + gravitybox/xposed. That's great to know.
I can't wait to get the phone tomorrow
Does Safestrap load 4.4.2 roms now?
aptalca said:
Thanks for the replies.
I guess if the phone comes with 4.4 already, I only have the JCase's root option, anyway.
But reading the replies here as well as other threads, I see that most people are pretty content with the stock rom + root + gravitybox/xposed. That's great to know.
I can't wait to get the phone tomorrow
Click to expand...
Click to collapse
Safestrap works on 4.4 too
But you have to have satestrapped it when you were on the 4.2 bootloader, correct? So if you took an ota or if your phone shipped with 4.4, your bootloader was updated and you can no longer safestrap
My setup: 4.4 ATT Moto X, Rooted (by way of latest jcase method), Locked bootloader, and I'm pretty sure write protection is off (though I don't remember how to check)
What I am wanting to know is how would and should I be able to get to 4.4.2, and get my root back (as I'm not confident any method will be able to "keep" my root safely without screwing something else up)? What's the best way based on my setup, and what files or tools would I need(stock 4.4 or 4.4.2 ROM, a new recovery image, etc)?
Since the root method I used hijacks the recovery, I suppose I technically don't have a functional one (other than it maintaining my root). Do I even need a custom recovery? I don't ever plan to flash anything other than basic stock firmware, though I may toy around with Xposed in the future. Also as a sidenote, im currently using ART instead of Dalvik. If any method or technique might conflict with that (other than Xposed), then let me know to the best of your knowledge.
Write protection will be enabled on 4.4.2. You can have root, but a shutdown or hard reboot will erase the changes you make that are root oriented.
As far as getting to 4.4.2.....tonnes of info already here...multiple threads.
Here's a basic guide...and Google can help too. Read any thread related to 4.4.2 and locked bootloaders.
http://forum.xda-developers.com/showthread.php?t=2603358
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
I am using safestrap on my locked AT&T moto to get 4.4.2 + root + r/w on system - works perfectly.
(I modified the OTA to create a flashable zip that patches stock 4.4 up to 4.4.2, without updating the bootloader. I have an untested 4.4.2 flashable zip, and when the official SBF is released, I'll make another and test it myself.)
...
Sent from my XT1058 using XDA Premium 4 mobile app
kj2112 said:
Write protection will be enabled on 4.4.2. You can have root, but a shutdown or hard reboot will erase the changes you make that are root oriented.
As far as getting to 4.4.2.....tonnes of info already here...multiple threads.
Here's a basic guide...and Google can help too. Read any thread related to 4.4.2 and locked bootloaders.
http://forum.xda-developers.com/showthread.php?t=2603358
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
Honestly i dont even care to have an unlocked bootloader. I just realy need root after I update. Write protection, so far i think, i've only needed for AdAway to work on my phone, though Im sure I have used or applied it else on my device. And thanks for the thread, but I was already subscribed .
Ctrl-Freak said:
I am using safestrap on my locked AT&T moto to get 4.4.2 + root + r/w on system - works perfectly.
(I modified the OTA to create a flashable zip that patches stock 4.4 up to 4.4.2, without updating the bootloader. I have an untested 4.4.2 flashable zip, and when the official SBF is released, I'll make another and test it myself.)
Click to expand...
Click to collapse
While I would like to test that out further for you, I have only one phone lol. I very lightly looked in safestrap sometime ago when I was trying to find how to root previous versions of my phones software. Back then I didn't feel I needed it, as I was and still am trying to keep things simple this time around with my Android device. I'll look into it again and see if needs have changed, but would reeeeeally like to just find a way to get root after updating. Your way does actually sound enticing however.
NameLessThugZero said:
While I would like to test that out further for you, I have only one phone lol. I very lightly looked in safestrap sometime ago when I was trying to find how to root previous versions of my phones software. Back then I didn't feel I needed it, as I was and still am trying to keep things simple this time around with my Android device. I'll look into it again and see if needs have changed, but would reeeeeally like to just find a way to get root after updating. Your way does actually sound enticing however.
Click to expand...
Click to collapse
The only ways to use 4.4.2 Rooted with Write Protection DISABLED is the Safestrap way, or to unlock your bootloader.
Since you have AT&T, Moto doesn't give out the code to unlock your bootloader (Non-Developer Edition Verizon phones are the same way.) so if you really want to unlock your bootloader, see -> http://forum.xda-developers.com/moto-x/general/verizon-moto-maker-bootloader-unlock-t2680651 I know the thread title says VERIZON but it works for ATT users too.
I see, thanks for the explanation, because I certainly wouldn't have know it was for AT&T users too! I'll check them out.
Sent from my XT1058 using XDA Premium 4 mobile app
Ctrl-Freak said:
I am using safestrap on my locked AT&T moto to get 4.4.2 + root + r/w on system - works perfectly.
(I modified the OTA to create a flashable zip that patches stock 4.4 up to 4.4.2, without updating the bootloader. I have an untested 4.4.2 flashable zip, and when the official SBF is released, I'll make another and test it myself.)[/QUOTE
So essentially, I cant just install Safestrap, then update to 4.4.2, correct? I'd need to do what you did, which is to modify the OTA?
Click to expand...
Click to collapse
NameLessThugZero said:
So essentially, I cant just install Safestrap, then update to 4.4.2, correct? I'd need to do what you did, which is to modify the OTA?
Click to expand...
Click to collapse
Right. You want a modified version of the OTA that does not modify your bootloader and will patch /system from 4.4 to 4.4.2. I also manually patched the kernel up to 4.4.2.
And, my experience is that you also have to downgrade to 4.2.2. I don't quite understand why, but I have never been able to upgrade to 4.4.x (neither from the 4.4 leak or the official 4.4 version) without going back to 4.2.2 first. The eclipse ROM instructions, on the other hand, suggest that a safestrap:twrp factory wipe might be enough, but I remember trying that once, and it didn't work. YMMV
I already made a zip to flash a full copy of 4.4.2 (not a patch) that I made from my system dump, but it hasn't been tested. (I'm waiting for the SBF.)
Alright. Well I guess I'll have to wait a bit for someone to come out or prove there's a safer, surer method to update. Moto always did like to make thing like this difficult, heh.
Sent from my XT1058 using XDA Premium 4 mobile app
Im concerned that activating the phone on 12b will force an update to kit kat.
I want to root and rom this thing tonight, then activate once thats completed. Will I run into any issues doing this?
planned to follow this post to do this.
http://forum.xda-developers.com/showthread.php?t=2623527
is there an easier way?
Thanks in advance! Looking forward to being active round here.
You could just refuse the update once you activate, it won't ask again for another hour. You should have plenty of time to root and ROM in that time. But why not OTA update to 24A, root with IOroot25, then use Auto-Rec to flash the JB aboot and recovery. Its just as easy that way. Plus you're updated to the new baseband/tz/Rpm. From there you can flash any of the 24A ROMs. LG based or the new aosp ROMs with 4.4 kernels like Mahdi, PA, or the CM11 build in the VZW development section
JRJ442 said:
You could just refuse the update once you activate, it won't ask again for another hour. You should have plenty of time to root and ROM in that time. But why not OTA update to 24A, root with IOroot25, then use Auto-Rec to flash the JB aboot and recovery. Its just as easy that way. Plus you're updated to the new baseband/tz/Rpm. From there you can flash any of the 24A ROMs. LG based or the new aosp ROMs with 4.4 kernels like Mahdi, PA, or the CM11 build in the VZW development section
Click to expand...
Click to collapse
No real reason. Just out of habit I've avoided OTAs. I thought they might patch something to not allow this on the newest update.
Do you have a link to the Auto-rec? Im not sure what that is and want to read up on it. That does seem like a better option since I'll have the newest radios and such. My search bar has been showing only 50% of the time so I've had difficulty searching.
edit:
Is this auto-rec you were referring to? it is an APK.. I just install this using an APK installer from the market?
http://forum.xda-developers.com/showthread.php?t=2715496
ddurandSGS3 said:
No real reason. Just out of habit I've avoided OTAs. I thought they might patch something to not allow this on the newest update.
Do you have a link to the Auto-rec? Im not sure what that is and want to read up on it. That does seem like a better option since I'll have the newest radios and such. My search bar has been showing only 50% of the time so I've had difficulty searching.
Click to expand...
Click to collapse
Avoiding OTAs is a good habit. I commend you. Samsung taught us that. Lol. We had some issues at first too like Loki being blocked and all. But devs found a workaround. Here's the link for Auto-Rec http://forum.xda-developers.com/showthread.php?t=2715496 I haven't personally used it but know quite a few who have with success.
JRJ442 said:
Avoiding OTAs is a good habit. I commend you. Samsung taught us that. Lol. We had some issues at first too like Loki being blocked and all. But devs found a workaround. Here's the link for Auto-Rec http://forum.xda-developers.com/showthread.php?t=2715496 I haven't personally used it but know quite a few who have with success.
Click to expand...
Click to collapse
Yeah the S3 was a nightmare lol.
switched to the HTC one and it was great but its time to move on. Thanks for all the help. Its nice to be on a device that doesnt use fastboot/adb. I hate using that.
ddurandSGS3 said:
Yeah the S3 was a nightmare lol.
switched to the HTC one and it was great but its time to move on. Thanks for all the help. Its nice to be on a device that doesnt use fastboot/adb. I hate using that.
Click to expand...
Click to collapse
I came from a S3, so I feel your pain. Lol
Rooting 12b and installing recovery, then flashing the 24a bootstack is hella easier and less time consuming in my opinion.
LG G2 ftw
I was in the same boat. Bought two VS980 and one wasn't activated yet due to other person being on vacation. All I did was take out my SIM card and put it in the other phone so it gets passed the activation screen and skip all the Google logins.
It did indicate that KK was available and I just skipped the update since I was on 12B. So my steps were to root with ioroot25, pushed loki_tool using adb, pushed update recovery with the premodified 12B TWRP 2.6.3.3 using adb.
Since I went with XDABBEB modified debloated stock, I copied the bootstack and ROM using MTP. Used adb to boot into recovery and followed the directions indicated on his ROM.
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!
Hi all,
sorry if this question has been asked to death, but I've looked at the majority of guides I can find both here and elsewhere, and some of the information seems contradictory and I want to avoid bricking my device.
As of 2015, how can I root the I9305?
The phone is running Android 4.3.
A couple of people have said Knox was an issue, but I've checked on the phone, and when I go into the Knox app from my app drawer, it gives me a screen asking me to install it, and nothing else, so I'm not too sure if that would be a problem, although I'd rather be safe than sorry.
Again, sorry if this has been asked before, and thanks for any help!
Bumping..
Can anyone just confirm whether the Chainfire method still works, or am I better off going with the Unified android toolkit method?
First you should upgrade to 4.4.4.
For me cf-auto-root-m3-m3zh-gti9305.zip rooting method worked well. Uploaded it with Odin3-v3.07.exe.
Update supersu to get past Knox.
I had issues with cwm so use twrp instead.
openrecovery-twrp-2.8.4.0-f2fs-i9305.tar
Zishan01 said:
Bumping..
Can anyone just confirm whether the Chainfire method still works, or am I better off going with the Unified android toolkit method?
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...305/index-samsung-galaxy-s3-lte-roms-t2206898 hmm ?