Related
Background information:
Bought the AT&T version when it came out right away
Got root the first time it was released
Updated root when next update came out ( Didn't know if I need to )
OTA has been Frozen since I got the phone
Is it safe for me? Should I go back to the first version and then update?
Trust me I've read the posts and since I know there have been some issues on the Verizon side I wasn't sure if that was something that was effecting AT&T too. If some one could please give me an explain of that to it would be extremely helpful as I like to know my **** so I can help others.
Thanks
Icon000 said:
Background information:
Bought the AT&T version when it came out right away
Got root the first time it was released
Updated root when next update came out ( Didn't know if I need to )
OTA has been Frozen since I got the phone
Is it safe for me? Should I go back to the first version and then update?
Trust me I've read the posts and since I know there have been some issues on the Verizon side I wasn't sure if that was something that was effecting AT&T too. If some one could please give me an explain of that to it would be extremely helpful as I like to know my **** so I can help others.
Thanks
Click to expand...
Click to collapse
Flash back to stock via RSDLite. Let it boot up. Get your gmail setup.
When the prompt comes up, DL the .54 update. Install.
Root with jcase's new root method.
Or you could just install safestrap. Install a ROM with the camera update and not worry about it until kitkat comes around.
Sent from non rooted motoX :'(
I'm not really interested in updating to another Rom unless it has the touchless controls or something really interesting. Touchless Controls is one of the main reasons I got this phone next to battery life.
Is Safestrap finally settled down? I feel like last time I check there were still messages about bugs and other issues?
matt99017d said:
Flash back to stock via RSDLite. Let it boot up. Get your gmail setup.
When the prompt comes up, DL the .54 update. Install.
Root with jcase's new root method.
Or you could just install safestrap. Install a ROM with the camera update and not worry about it until kitkat comes around.
Sent from non rooted motoX :'(
Click to expand...
Click to collapse
Icon000 said:
I'm not really interested in updating to another Rom unless it has the touchless controls or something really interesting. Touchless Controls is one of the main reasons I got this phone next to battery life.
Is Safestrap finally settled down? I feel like last time I check there were still messages about bugs and other issues?
Click to expand...
Click to collapse
the only rom out for SS that i am aware of is just a ported tmobile rom for vzw phones that has the update built in. Basically it is just the OTA stock rom running on SS. This is what I am using currently. Not sure if it flashable for ATT phones, but I'm sure there is some workaround there. Or maybe the OP on that thread can make a ATT one if you asked him. SS is stable as of now. Haven't had any new updates to it because no one is having any problems currently (at least with moto x devices).
For your question pertaining to options for taking the OTA. There are 4 methods now.
1. SS method described above
2. use the thread called something like "keep root through the OTA." It basically takes the ota without updating the BL so you can still downgrade to your stock original FW that you are on now. It's the same thing as the SS method because SS also does not udpate the BL, but you won't be using SS for this method obviously.
3. you can flash recovery.img (and system.img if you need to) or just RSD, then install pwnmymoto without running it, then take the ota and pwnmymoto will root the phone automatically after the ota is taken. you won't be able to downgrade your FW anymore with this method.
4. you can just take the ota (also must flash or use rsd to take it obviously) and then use jcase's rockmymoto root exploit. This uses adb commands and telnet stuff. Not too difficult but if you are unfamiliar with all of that then it will take at least some reading. There is also a thread out there for windows users that simplifies it pretty well.
For future Kit kat root. it is still up in the air what will happen with that. I chose to use SS because it was easy. quick. and allows me to make nandroids. I also like knowing that I can still flash to original stock FW in case that might be necessarry for getting root on kit kat. This seems less likely now that jcase created a root method for the OTA that is out, but I'm still just playing it safe personally, even if it might be pointless now.
**Make certain that your reactivation lock in security settings is off before beginning this process**
1. Take the NG3 OTA update.
2. Download and install Towelroot-v3.apk(this version does not require internet access).
3. Place your phone into "Download Mode" (press and hold the Home, Volume Down, and Power keys until the phone powers on and displays warning screen, then press Volume Up key) and flash the G870A_NE4_Stock_Kernel using Odin's PDA slot(AP in Odin v3.09+).
4. Open the Towelroot app from your app drawer and press "Make it Rain" to root your device.
5. Power off then boot into "Download Mode" again and flash the G870A_NG3_Stock_Kernel also in Odin's PDA slot(AP in Odin v3.09+).
6. Download SuperSu to manage root access. Done!
Troubleshooting:
1. If the NG3 OTA update fails consider flashing the G870AUCU1ANE4_Full_Odin.tar to return to stock then take the NG3 OTA update, (or place the G870A_NE4toNG3_OTA.zip onto your ext-sdcard and sideload from stock recovery). Once updated to NG3 continue to Step 2 above.
2. The most common cause of an Odin flash failure is a bad usb port or cable. Please check before reporting a failure.
Notes:
1. After flashing the NE4 kernel your phone may run a little wonky and towelroot may not root on the first try. If that happens reboot and try towelroot once again. Once rooted and after flashing the NG3 kernel your phone will once again run like a champ!
2. The above process will not affect your User Data or Knox Warranty Flag.
Credits:
@lordmorphous - Tester
Gonna try this... Thanks! :beer:
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
Yes this worked. Thank you very much.......
Are we going to trip Knox using the method above ???
Just wanna be sure about this. ...g
gregsarg said:
Are we going to trip Knox using the method above ???
Just wanna be sure about this. ...g
Click to expand...
Click to collapse
Nope.
Does anyone have a list of the benefits of updating to NG3?
I just rooted my new phone on NE4 and I want to know whether it's worth taking the time.
Thanks for the How-to! Worked great for me!
Any benefits on ng3 over stock?
Root possible for 'straight out-of-the-box' G870AUCU1ANG3???
I've looked and looked around the forums here and have come to the conclusion that the AT&T S 5 I recently picked up is, sadly, unable to be rooted. Does anyone here know if this is true? As the title suggests, my phone seems to have come loaded with G870AUCU1ANG3. Is it possible that it came with the previous iteration (NE4, I think??) and I didn't avoid an update, thus meaning I can flash the earlier version? Can I even tell whether it's possible to 'revert' to NE4 (or whatever it would be)? Is any of this even possible without having been previously rooted, or am I wasting my time searching this out? Naive but earnest questions... sorry if I'm in the wrong place here. I promise, I poked around the site for a few days in search of clarity before posting.
papayajelly said:
I've looked and looked around the forums here and have come to the conclusion that the AT&T S 5 I recently picked up is, sadly, unable to be rooted. Does anyone here know if this is true? As the title suggests, my phone seems to have come loaded with G870AUCU1ANG3. Is it possible that it came with the previous iteration (NE4, I think??) and I didn't avoid an update, thus meaning I can flash the earlier version? Can I even tell whether it's possible to 'revert' to NE4 (or whatever it would be)? Is any of this even possible without having been previously rooted, or am I wasting my time searching this out? Naive but earnest questions... sorry if I'm in the wrong place here. I promise, I poked around the site for a few days in search of clarity before posting.
Click to expand...
Click to collapse
There shouldn't be any reason why you can't follow the instructions in the 1st post of this thread starting with step 2.
I've been searching for a while and can't find anything about using this root method and then being able to install safestrap. Has anyone been successful in doing this? Do I need to downgrade before and does anybody have the downgrade file? FYI Just bought my phone last night and was successful in rooting.
rescuedad said:
I've been searching for a while and can't find anything about using this root method and then being able to install safestrap. Has anyone been successful in doing this? Do I need to downgrade before and does anybody have the downgrade file? FYI Just bought my phone last night and was successful in rooting.
Click to expand...
Click to collapse
Never mind, I figured it out. If you have the active you need to downgrade the kernel to NE4 like you do if you need root. Then you install Safestrap 3.75. I'm doing a Nandroid backup as I type. I'm going to re-flash the NG3 stock kernel when I'm done and hopefully that will be fine.
If it bricks, I can always take it back since I blocked the knox counter... BTW I'm on At&T
I downgraded to the NE4 to root. Along with others here I have to ask, what are, if any, benefits to upgrading the kernel?
panthersdzynes said:
I downgraded to the NE4 to root. Along with others here I have to ask, what are, if any, benefits to upgrading the kernel?
Click to expand...
Click to collapse
Not sure I understand the question but I will take a shot......typically the kernel, modules, and non-hlos.bin have to match or else you may experience issues such as no wifi, lag, etc. The NE4 and NG3 kernel and modules may be similar enough that you will not experience issues immediately but they may develop later unless you reflash the NG3 kernel to match your modules and non-hlos.
muniz_ri said:
Not sure I understand the question but I will take a shot......typically the kernel, modules, and non-hlos.bin have to match or else you may experience issues such as no wifi, lag, etc. The NE4 and NG3 kernel and modules may be similar enough that you will not experience issues immediately but they may develop later unless you reflash the NG3 kernel to match your modules and non-hlos.
Click to expand...
Click to collapse
I see. Thank you, that answers my question.
THanks XDA
Been away along time. Had iphones for the last 6 years. Use to go here all the time in the Kaiser days (Att Tilt) if any of you remember. I see XDA has still been kicking ass while I've been gone! Glad to be back and Thank You everyone especially first poster for the guide to root my Att GS5 Active.
THANK YOU
Working perfectly. ..thank you. ..g
There was a small update released today. Can someone that is rooted grab it from their fota/cache folder and send to me so that I can update this guide? Thanks.
WORKED! AWESOME!
Now... I have installed SuperSU. Was that left out of the first post?
Also, if I do not flash the NG3 Stock Kernel back afterwards, will I experience funkiness?
Thanks again!
I have had my G2 for about a year. I had rooted it and never took an update after 11A. I was happy with the way my phone worked and read some of the stories where people were not happy with KitKat.
Unfortunately, the touch went out on my screen and I had to get a replacement. I successfully flashed my old one back to stock and removed root w/out a problem.
Now my problem is this:
The new phone came with 25B. I understand there is no way to root this version. The phone is already wanting me to update to 26A. What I would like to do is rollback someway, root, then take updates. I can already see my phone signal is not as strong as it used to be.
My questions are:
1. Can I rollback to an earlier version and root via one of the IORoot options? (TOT it like I did my old phone)
2. What version would I need to rollback to to accomplish this.
3. Could someone point to the correct thread to do this?
4. Finally, I see it seems to be ok to take factory updates if you are rooted only. I am not interested in custom roms. I use Titanium Backup to freeze bloatware and would like like to be able to use it again. I have quite a bit I need to restore.
I have done some searching but it seems the G2 section has changed a lot since I was last here. I do appreciate any help and/or pitfalls you can warn me about. I do have the LG Flash Tool 1.8 installed and am familiar with how to install the needed TOT file.
Thanks....
Oaklands said:
I have had my G2 for about a year. I had rooted it and never took an update after 11A. I was happy with the way my phone worked and read some of the stories where people were not happy with KitKat.
Unfortunately, the touch went out on my screen and I had to get a replacement. I successfully flashed my old one back to stock and removed root w/out a problem.
Now my problem is this:
The new phone came with 25B. I understand there is no way to root this version. The phone is already wanting me to update to 26A. What I would like to do is rollback someway, root, then take updates. I can already see my phone signal is not as strong as it used to be.
My questions are:
1. Can I rollback to an earlier version and root via one of the IORoot options? (TOT it like I did my old phone)
2. What version would I need to rollback to to accomplish this.
3. Could someone point to the correct thread to do this?
4. Finally, I see it seems to be ok to take factory updates if you are rooted only. I am not interested in custom roms. I use Titanium Backup to freeze bloatware and would like like to be able to use it again. I have quite a bit I need to restore.
I have done some searching but it seems the G2 section has changed a lot since I was last here. I do appreciate any help and/or pitfalls you can warn me about. I do have the LG Flash Tool 1.8 installed and am familiar with how to install the needed TOT file.
Thanks....
Click to expand...
Click to collapse
You can kdz or tot back and root from there. Root sticks through 25b but not 26a update.
Thank you. I will go ahead and update to the 25b then.
Hi, First off, I'm super rusty in the custom rom and kernell scene so explain things as easily as you can please.
Now, I have a moto x XT1053, the unlocked variant that they sold on the moto website that came with a net10 chip.
The thing is that I obviously unlocked the bootloader and installed the TWRP recovery. I have (almost) stock android and by that I mean stock with Xposed. I want to know if any of you guys could point me in the right direction, I mean, do I install the OTA update or do I return my phone to stock, and if it's the later, How do I return my phone to stock to do a proper OTA update?
Thanks in advance!
I have the same phone and was in pretty much your situation, including being rusty in flashing roms, kernels and such. I went with the OTA and am very glad I did. My subjective impression is that it's faster and at least as stable.
I thought my phone was close-to-stock, as I had removed some stuff (Xposed, notably) a while back to receive the 4.4.2 OTA. But the new Lollipop OTA wouldn't install, so I took the bull by the horns and flashed stock system.img that I got from Motorola's official firmware repository. I had to request access, and it took about 12 hours for that to come through.
After I downloaded the firmware zip file, I unpacked it and located the system.img file. Search on Google or this forum for the way to flash an img file to your phone, if you've forgotten (as I had). When I have time later today, I'll try to post a link to some clear instructions. I don't want to try to tell you from memory, as this is something I do about once or twice year since I got a Moto X (I tinkered a *whole* lot more when I had an HTC Sensation, but I've decided that if I want to keep my wife, I'd better stop playing with my mobile phone.)
I did this at the advice of a Motorola technician, who said the "most definitive way to return to unroot" was to flash stock system.img for 4.4.4. (I was part of last week's U.S. soak test, so Moto techs were handling questions from people like me who were wrestling with the OTA.)
I had worried that I might lose apps and data by flashing system.img, but I didn't lose a thing. I *did*, though, lose root, and I haven't re-rooted yet. Before I root, I'm waiting for the stock Lollipop 5.1 firmware to be made available on the Motorola repository so that I can have a backup of stock recovery.img.
Meanwhile, I'm enjoying Lollipop, which is like having a new phone.
varxx said:
I have the same phone and was in pretty much your situation, including being rusty in flashing roms, kernels and such. I went with the OTA and am very glad I did. My subjective impression is that it's faster and at least as stable.
I thought my phone was close-to-stock, as I had removed some stuff (Xposed, notably) a while back to receive the 4.4.2 OTA. But the new Lollipop OTA wouldn't install, so I took the bull by the horns and flashed stock system.img that I got from Motorola's official firmware repository. I had to request access, and it took about 12 hours for that to come through.
After I downloaded the firmware zip file, I unpacked it and located the system.img file. Search on Google or this forum for the way to flash an img file to your phone, if you've forgotten (as I had). When I have time later today, I'll try to post a link to some clear instructions. I don't want to try to tell you from memory, as this is something I do about once or twice year since I got a Moto X (I tinkered a *whole* lot more when I had an HTC Sensation, but I've decided that if I want to keep my wife, I'd better stop playing with my mobile phone.)
I did this at the advice of a Motorola technician, who said the "most definitive way to return to unroot" was to flash stock system.img for 4.4.4. (I was part of last week's U.S. soak test, so Moto techs were handling questions from people like me who were wrestling with the OTA.)
I had worried that I might lose apps and data by flashing system.img, but I didn't lose a thing. I *did*, though, lose root, and I haven't re-rooted yet. Before I root, I'm waiting for the stock Lollipop 5.1 firmware to be made available on the Motorola repository so that I can have a backup of stock recovery.img.
Meanwhile, I'm enjoying Lollipop, which is like having a new phone.
Click to expand...
Click to collapse
So, should I:
Delete GravityBox and Xposed
Install the .img file found within the zip for the Moto X dev Edition
Then I'll be able to install the OTA withouth losing data?
mundofeliz said:
So, should I:
Delete GravityBox and Xposed
Install the .img file found within the zip for the Moto X dev Edition
Then I'll be able to install the OTA withouth losing data?
Click to expand...
Click to collapse
The sequence you describe worked for me, assuming "deleting" GravityBox and Xposed is the preferred way of removing them. I can't remember.
The .img file to flash is system.img. You need to know how to get to fast boot/bootloader mode and perform the flash, of course.
If your experience is like mine, after receiving and installing the OTA, you'll have Lollipop without having lost any apps or data.
But you may want to wait for someone whose more up on this procedure to weigh in. When I updated, I proceeded as if I might lose all my apps and data, so I was pleasantly surprised.
BTW, I've since re-rooted, and I haven't had any problems. It's reassuring that the 5.1 ROM image is now available officially from Moto and elsewhere (info courtesy of dtg7: http://forum.xda-developers.com/showpost.php?p=61800775&postcount=11).
I'll do a Nandroid just in case. I'll do the steps above too, since all I've done is unlock bootloader, root and xposed I think this'll work for me. Kinda did only that originally for that reason but that was sooooo long ago. And also because the Moto X is such an amazing phone to begin with, I never saw the need to install other roms. Did you flash just the system.img, the recovery.img or both? I requested the firmware from moto and they approved but in the meantime I also downloaded the original too from filefactory, the exact same firmware I'm running (without modifications I mean.
mundofeliz said:
I'll do a Nandroid just in case. I'll do the steps above too, since all I've done is unlock bootloader, root and xposed I think this'll work for me. Kinda did only that originally for that reason but that was sooooo long ago. And also because the Moto X is such an amazing phone to begin with, I never saw the need to install other roms. Did you flash just the system.img, the recovery.img or both? I requested the firmware from moto and they approved but in the meantime I also downloaded the original too from filefactory, the exact same firmware I'm running (without modifications I mean.
Click to expand...
Click to collapse
IIRC, you'll need to do the Nandroid backup before you unroot, right?
I just flashed system.img. Won't that effectively restore the stock recovery? EDIT: According to the readme.txt file bundled in the stock ROM's zip file, recovery.img is flashed separately from system.img, so system.img will *not* restore the stock recovery.
I always feel safer running official firmware from Moto. For one thing, the labeling on the Moto dl site is very explicit, so you know exactly what you're getting.
I agree that the Moto X is a cool enough phone with a stock ROM that there's little need for custom ROMs. I was a flash-aholic when I had an HTC Sensation. But the Moto X pretty much has everything I need. Under KitKat, I did use XPosed to kill the Google search box, but otherwise I've been happy with the stock ROMs.
Oh, and I usually eventually run a custom recovery (TWRP) so I'll have more boot options. But I don't see that as essential now. I find I'm actually using my phone more than tweaking it, which is a change from previous phones.
Hi All,
When I soft-bricked (long night and stupid choices of tweaking system files), I was unable to boot. Stuck at the Asus logo, at times not even the Asus logo would show. I took a few days but I finally figured it out.
After numerous methods tried and numerous failed attempts, I have narrowed down a successful process for recovering, downgrading and installing Lollipop. Please keep in mind that all cases are unique and this may not work for everyone. The zip folder contains all the tools and firmware builds needed to recover, downgrade, update your tablet.
Please note that this method was only tested on the non-LTE version of the tablet. This method may work if you substitute the firmware files. You can find links to these in the zip.
Another Note. To unbrick, follow the downgrade process. This should unbrick you.
By Clicking Download you agree that I in no way take any responsibility, liability either legally, morally, financially or any other way you could blame me for what you do or these applications do to your tablet or the opposite end of the spectrum, the amount of success to expect. This is at your own risk. I am only providing what I did to resolve my issue in hopes that it may help others.
IMPORTANT: You will lose all you data on the internal memory.
If you agree to the above please feel free to Download (1.87GB)
Key to Download:
!lZ51WKctjkd2v_mUGYz-TacrIResxm45yO5Ztl7k9-I
MD5 Hash
0722035687A42E0F3201147AAF238160
SHA-512 Hash to 100% verify it hasn't been tampered with since MD5 can be easily broken
FBF9C0B7CD88ABAB91B85C2E21B7694FD035D9E92ECE2FC54C6839C07D3FCDB1FAF9FE532920D9B63091412CE13DA9F50F507CC55B7206F516F8DFC8BC021DB5
A lot can go wrong if you don't know what you are doing. If you don't know what you are doing, stop to ask in a forum. You look dumber making a mistake by assuming than asking the most basic of question. So please don't feel embarrassed to ask what may seem obvious or simple. There is also a FAQ below which I will update as needed.
Unfortunately I have to throw this in here:Questions regarding the LTE version will not be answered as I do not have this device.
Huge Credit goes to 4pda members for creating some of these tools that helped me create this all in one zip.
FAQ
Q: Will this void my warranty?
Absolutely
Q: Can you upload only certain files? I don't want to download the large 1.87GB zip.
Sorry, I don't have time to dig through and upload specific folders/files on an individual basis. Someone else however may do so if you ask nicely.
Q: Do I have to install Lollipop or Xposed**?
No, once you are on KitKat, you can stay on KitKat. **Do not install xposed unless you are on Lollipop, won't work anyway since the KitKat image isn't rooted.
Q: Can I take OTA updates?
A: I would advise against it and it will most likely not work or corrupt the device. You should disable/freeze (do not remove) the FOTA Update apk and update apks to make sure you don't receive them by accident.
Q: Can I use this method to install a non-rooted Lollipop firmware image?
A: Untested. Since you can't take the OTA anyway, root shouldn't hurt anything. Just open the SuperSU APK and set it to Deny All if root makes you paranoid.
Q: Will this work for the LTE version?
A: As it is zipped, no. The tools however should work. When I was researching the tools seemed to be device unbiased (except for the firmware). Included in the zip are the original links I used for research. There you can find the LTE version of the firmware images.
Q: Can I share this on other forums?
Sure, just please be sure to keep the zip unmodified and not take credit. The guys on 4pda took a lot of time developing and posting these tools. It took me some time as well to create instructions and gather the required files.
Reserved.
For what I don't know, but just in case.
Successfully downloaded. Thx for the work.
Hello SyCoREAPER, where did you get the firmware and recovery files? I was thinking of using your method for ME176C but I don't have the necessary files. If you can provide some links on where you obtained the files I will search from there. Thanks
NoblyUntruthful said:
Hello SyCoREAPER, where did you get the firmware and recovery files? I was thinking of using your method for ME176C but I don't have the necessary files. If you can provide some links on where you obtained the files I will search from there. Thanks
Click to expand...
Click to collapse
I was debating answering or not. If you bothered reading the above or downloading the files you'd see where they came from.
will give this a go when mine arrives in next day or two
just one question...
is this on the VERY LATEST LP firmware???
Hello. The key to download is not workin. I enter the key exectly as u have it and when I hit OK, it keeps popin back up askin for it again. Is there something I'm doin wrong?
Thank you !
Thank you !!! I've just bought this model ME572c a few days ago. My tablet was bricked (black screen) after OTA update to WW_V12.14.1.12. I've managed to flash with your instructions, but when i try again to OTA update to WW_V12.14.1.12, just after finishing the update, tablet reboots and remains with black screen. I ve tryed to update from SD card (with official firmware and your lollipop firmware) and the same thing happens. Do you have any ideea why is this happening. Thank you very much !!
File download link?
Hello,
Came across this thread as I was planning to revive my old ME572C (5.0.1, getting laggy). Download links no longer work. Any chance you'd reupload the files?
Thanks!