Database Develop

New update Galaxy S5 Active

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
someone could tell me if I should give this update..?
just come to my active 5...

hdelvalle009 said:
someone could tell me if I should give this update..?
just come to my active 5...
Click to expand...
Click to collapse
I did the update, not sure how big it is or whats different. Still 4.4.2

The question is what well happen to the root if installed.

I'm rooted and the update failed for me. I don't know if it was root that caused it to fail or the fact that I changed my build.prop to reflect SM-G900A. Either way, doesn't seem a big enough deal to me to "fix" it for the update.

I'm using the KoolKit Active variant as my rom (http://forum.xda-developers.com/att...m-koolkit-s5-koolactive-v1-0-0b01-07-t2809957)
I take it trying to perform this update would be a bad idea.

Just updated. New Baseband Version G870AUCU1ANG. Kernel is 3.4.0-2304514. Build Number: KOT49H.G870AUCU1ANG3. Android Version 4.4.2.
I thought this might be 4.4.4. By the way, I lost ROOT when I did this. Will have to see what is needed to restore it.
---------- Post added at 12:18 PM ---------- Previous post was at 12:02 PM ----------
Just tried to re-install Towelroot. No Dice. It says the device isn't supported.....darn.

dbodom said:
Just updated. New Baseband Version G870AUCU1ANG. Kernel is 3.4.0-2304514. Build Number: KOT49H.G870AUCU1ANG3. Android Version 4.4.2.
I thought this might be 4.4.4. By the way, I lost ROOT when I did this. Will have to see what is needed to restore it.
---------- Post added at 12:18 PM ---------- Previous post was at 12:02 PM ----------
Just tried to re-install Towelroot. No Dice. It says the device isn't supported.....darn.
Click to expand...
Click to collapse
the exploit that geohot used for towelroot has now been patched, so if you apply this update you will no longer be able to root your device. unfortunately this was bound to happen, there are a couple of apks to look for the main one to freeze or delete is the localFota.apk (i think thats the correct name) this should prevent the ota from being recieved by your device. if you are running a a custom rom (either mine or nickoftyme's) the OTA should not apply. Technically it shouldnt apply at all if you are rooted in any fashion but apparently AT&T in their infinite wisdom found away to screw with us once again.

Geohot did say that they were going to patch...and now it's happened...
Block those OTA's people...
We may never see root again...so thanks for nothing AT$T....
rotten azzhats...g

So if I turn on wifi will it update automatically? Its been asking since this morning.

The update installed on mine, I lost root as well even though OTA Survival Mode was turned on.
On the brightside Visual Voicemail is fixed but I want my root back.

Slowb00st said:
So if I turn on wifi will it update automatically? Its been asking since this morning.
Click to expand...
Click to collapse
Most likely yes....unless you freeze the "ATT UPDATES" apk by using titanium backup...
You may want to freeze the following as well...
Local fota
Security policy updates
Samsung push service
With those 4 frozen...you should not see an update prompt again...g

UGH... sux.
I was hoping to root my phone tonight. I downloaded Towelroot and can open it but "Install" is not clickable.
I received the ATT update on Friday.

I don't know about anyone else but my update came down the other day and now my wifi sucks. It connects fine, has good strength, but is slower than dirt and loading content (browser and apps) and we have @ a 65Mbps connection.
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app

Like a fool, I allowed the AT&T OTA update in my Galaxy S5 Active. I lost root and towelroot would no longer work as the device was no longer supported. However, I was able to use ODIN to downgrade back to ANE4. Towelroot worked again to root my device and I was able to re-install all of my Xposed modules and most importantly Titanium Backup to freeze the OTA updates.
I did have to do a factory reset after downgrading because my stock email app repeatedly crashed afterward. But all is well with the world once again.

Ocires said:
Like a fool, I allowed the AT&T OTA update in my Galaxy S5 Active. I lost root and towelroot would no longer work as the device was no longer supported. However, I was able to use ODIN to downgrade back to ANE4. Towelroot worked again to root my device and I was able to re-install all of my Xposed modules and most importantly Titanium Backup to freeze the OTA updates.
I did have to do a factory reset after downgrading because my stock email app repeatedly crashed afterward. But all is well with the world once again.
Click to expand...
Click to collapse
Where did you download the ANE4 rom?
Edit: found it! http://rootzwiki.com/topic/202682-how-to-restore-your-att-s5-active/

Ha! I nixed that in the bud before it began. Damned ATT.

first off I'll admit I'm as new as new can be to Android. I got an s5, rooted it in hopes of getting WiFi tethering again (after years of a jailbroke Iphone) and to get rid of the emergency number I kept butt calling. . neither of these worked for me so I went ahead and updated. it said the installation failed twice but my software is now up to date. still rooted. . not sure what is going on. I'll check for the software update again tomorrow

gregsarg said:
Most likely yes....unless you freeze the "ATT UPDATES" apk by using titanium backup...
You may want to freeze the following as well...
Local fota
Security policy updates
Samsung push service
With those 4 frozen...you should not see an update prompt again...g
Click to expand...
Click to collapse
Thanks. I'm thankful I checked here before taking the update.

BuLLitz said:
UGH... sux.
I was hoping to root my phone tonight. I downloaded Towelroot and can open it but "Install" is not clickable.
I received the ATT update on Friday.
Click to expand...
Click to collapse
Late to the party on this reply...but we have a fix...by pushing the stock firmware via Odin....(see above )..
That'll get you to the rootable image and allow you to freeze the update...g

gregsarg said:
Late to the party on this reply...but we have a fix...by pushing the stock firmware via Odin....(see above )..
That'll get you to the rootable image and allow you to freeze the update...g
Click to expand...
Click to collapse
Worked beautifully!
My S5 Active is now not an Active and I am able to access all the apps on Gear Manager.

[Q] Verizon G2 acting crazy after FDR

Hello, and thank you in advance for any support on my issues. I have done some extensive searching regarding my issues but am coming up empty. I consider myself a relative noob and am now facing multiple questions and issues with my phone.
Device Info:
Verizon LG G2
Rooted, stock
Android Version 4.2.2
Software Version VS98011A
I did not personally root my phone - I paid to have it done for me remotely.
I have been using Titanium Backup to freeze or remove applications and bloat.
I also have used the paid version of ROM Manager for when/if I need it - I have never personally flashed a custom ROM or Kernel, etc.
I did personally side load the HotSpotProvision apk to use the Verizon Hotspot feature with my unlimited data and it worked great.
I also have the Verizon versions of the Galaxy S5 and LG G3. I recently did a 4G LTE speed test with all 3 devices and got insane speeds (attached) with the S5 and G5 but not the G2. I tried researching whether KitKat was the reason for being able to access XLTE speeds or not but couldn't find anything definitive there either. So I decided to attempt the Verizon OTA KitKat update for the G2. Here is where my nightmare begins...
To my knowledge, no backup had ever been done to my phone unless it was done when it was rooted. Regardless, I wanted to do one before making any changes to the phone but I have a feeling I was unsuccessful. After more searches on how to perform a backup and trying 6 times with ROM Manager (unsuccessfully), I decided to try the physical key option to launch into Recovery Mode. Based on what I did find online, this method would take you to the FDR screen but not to worry and to continue because it would actually take you to the TWRP home screen. Well, it did not. My phone reset and I lost everything in my gallery, etc. On reboot, I did see that I was still rooted but not able to do the OTA (because I am still rooted, I assume?). I have done 2 more FDRs and now my phone is acting out of it's mind.
Issues:
Touch screen unresponsive or turning off/on all by itself
Contact info not syncing to native messaging app
Previously installed free or purchased apps not reinstalling (although they did after the first FDR)
Can't receive OTA
At this point, I might as well do whatever I need to do to get things working correctly since I'm already reset.
My questions are:
How can I check if I do in fact have, or don't have a backup that I can access?
How do I create a backup so this doesn't happen again?
What do I need to do to get the OTA and will KK allow me to access the XLTE band?
Can I still do a Factory Data Reset and get back to the true "out of the box" version of the phone? If so, how?
I think that's it for now!! Thanks for any help that can be offered. Cheers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Sounds like whoever you paid to root the phone didn't install a recovery or you lost it from applying the KK OTA.
You can install TWRP using Autorec if you're on KK (4.4.2) now.
http://forum.xda-developers.com/showthread.php?t=2715496
Personally I'd start clean to see if it clears up your issues, the touch screen thing sounds more like a hardware problem. If all is well after returning it to stock, re-root it yourself using ioroot/towelroot and install a recovery again and make a back up to save somewhere once you get it set up the way you want it.
http://forum.xda-developers.com/showthread.php?t=2448960

Thank you very much, Matt.
KK never did get installed...I am still on 4.2.2 and every time I try to go back to stock through various methods on this site I get the attached image. I would definitely like to start with the out-of-box device again, OTA KK and re-root but I'm not even having any luck with that either. This whole project began with the thinking that I needed KK to access the XLTE network since I was getting incredible speeds with the G3 and S5...do you know if that is accurate?
mjones73 said:
Sounds like whoever you paid to root the phone didn't install a recovery or you lost it from applying the KK OTA.
You can install TWRP using Autorec if you're on KK (4.4.2) now.
http://forum.xda-developers.com/showthread.php?t=2715496
Personally I'd start clean to see if it clears up your issues, the touch screen thing sounds more like a hardware problem. If all is well after returning it to stock, re-root it yourself using ioroot/towelroot and install a recovery again and make a back up to save somewhere once you get it set up the way you want it.
http://forum.xda-developers.com/showthread.php?t=2448960
Click to expand...
Click to collapse

lantzman said:
Thank you very much, Matt.
KK never did get installed...I am still on 4.2.2 and every time I try to go back to stock through various methods on this site I get the attached image. I would definitely like to start with the out-of-box device again, OTA KK and re-root but I'm not even having any luck with that either. This whole project began with the thinking that I needed KK to access the XLTE network since I was getting incredible speeds with the G3 and S5...do you know if that is accurate?
Click to expand...
Click to collapse
Follow the directions in the return to stock guide provided, see if you can get the phone in download mode...
Install the LG Flash Tool and drivers then try this.
1) Go ahead and put phone in Download mode by VolUp + plug in USB to PC. At this time your computer should install the device, if it hadnt already. Open device manager to check if un der "Ports (Com and LPT)" it shows up as LGE AndroidNet for VZW USB Serial Port (COM##) IF the COM number is anything other than 41, which it probably will be. Right click it in device manager and choose peroperties, then go to port settings tab and click advanced. On the bottom choose COM41 and hit OK. (if you get an error about it being in use I'll write more about that later)
hit ok and all that and close out the properties.
Click to expand...
Click to collapse

OK, I'm on download mode, the computer installed drivers and I changed to COM41. Phone still shows "Firmware Update" screen and 0% on progress. Where do I go from here?
mjones73 said:
Follow the directions in the return to stock guide provided, see if you can get the phone in download mode...
Install the LG Flash Tool and drivers then try this.
Click to expand...
Click to collapse

lantzman said:
OK, I'm on download mode, the computer installed drivers and I changed to COM41. Phone still shows "Firmware Update" screen and 0% on progress. Where do I go from here?
Click to expand...
Click to collapse
Did you unplug and replug in the phone?

I think I got it done. Phone is downloading KK now. This is where I would get the error on the install because I was rooted. Did the process I just go through unroot me?
mjones73 said:
Did you unplug and replug in the phone?
Click to expand...
Click to collapse

OK, it's doing the OTA!
lantzman said:
I think I got it done. Phone is downloading KK now. This is where I would get the error on the install because I was rooted. Did the process I just go through unroot me?
Click to expand...
Click to collapse

lantzman said:
I think I got it done. Phone is downloading KK now. This is where I would get the error on the install because I was rooted. Did the process I just go through unroot me?
Click to expand...
Click to collapse
Yes, returns the phone to out of the box stock basically. Now if you want to re-root, you can use ioroot25 or towelroot.
ioroot25 - http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Once rooted, use autorec to install a recovery (kitkat requires some additional steps besides just flashing a recovery and it does them for you)
http://forum.xda-developers.com/showthread.php?t=2715496
Make sure you grab the vs980 version of autorec.

So I can't create a stock recovery prior to root, correct...so that I can go back to stock from root?
mjones73 said:
Yes, returns the phone to out of the box stock basically. Now if you want to re-root, you can use ioroot25 or towelroot.
ioroot25 - http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Once rooted, use autorec to install a recovery (kitkat requires some additional steps besides just flashing a recovery and it does them for you)
http://forum.xda-developers.com/showthread.php?t=2715496
Make sure you grab the vs980 version of autorec.
Click to expand...
Click to collapse

lantzman said:
So I can't create a stock recovery prior to root, correct...so that I can go back to stock from root?
Click to expand...
Click to collapse
No, you need to root it first if you want to back it up.

OK, so I can root with the Towelroot app and use Autorec for backup. Does it give me TWRP?
mjones73 said:
No, you need to root it first if you want to back it up.
Click to expand...
Click to collapse

and where do I find the process for installing Autorec?
lantzman said:
OK, so I can root with the Towelroot app and use Autorec for backup. Does it give me TWRP?
Click to expand...
Click to collapse

sorry, I was making this way too difficult. I ran Towelroot and Autorec and I believe we are good to go. Now, when would I use Autorec...when I have an issue flashing other ROMs, kernels, etc?
How do you prefer to receive donations? I really appreciate your help...you've been great!

lantzman said:
sorry, I was making this way too difficult. I ran Towelroot and Autorec and I believe we are good to go. Now, when would I use Autorec...when I have an issue flashing other ROMs, kernels, etc?
How do you prefer to receive donations? I really appreciate your help...you've been great!
Click to expand...
Click to collapse
Autorec is a one and done, you can remove it now, it installs TWRP, that's all you need it for. You should now be able to get into recovery using the same sequence you used before if it installed clean for you. Any flashing of rom, kernels, etc would be via TWRP.
One last note, don't install any OTA's while you're rooted.
You don't have to donate anything but if you really want to, just hit the Donate to Me button under my name.

OK, thank you. One last question: it seems the touch screen may be starting to fail. If I needed to unroot or at least show unrooted to turn it in for a warranty replacement, can that be done and if so, how?

lantzman said:
OK, thank you. One last question: it seems the touch screen may be starting to fail. If I needed to unroot or at least show unrooted to turn it in for a warranty replacement, can that be done and if so, how?
Click to expand...
Click to collapse
This will get you back to stock. Make sure you read the first page before you do this...if needed. FYI: Device needs to be off to get into download mode and you should be in download mode before installing the drivers. http://forum.xda-developers.com/showthread.php?t=2448960
Sent from my XDABBEB VS98025A v2.0.0 using XDA free mobile app

Perfect, that's the process I just did from root so I could get the KK OTA. Just wasn't sure if there was an easier way to just show "unrooted" in "about phone" before having them look at it. Love your call sign/avatar. Huge Huge Huge Zeppelin fan here! Ever since hearing "Stairway" in 7th grade! Mght need to see if "LantZeppelin" is available! Thanks again.

All Things Root LG G Flex

As I realize that there are probably a number of threads regarding rooting of the LG G Flex, I wanted to make a simple guide in my own words to sort of give back to the developing community. I will be providing a number of attachments so that you won't have to go searching yourself. Before proceeding with this make any necessary backups and realize that this will void you're warranty and quite possibly brick or screw up you're phone and this is to be done with caution. I am in no way responsible for what might or might not happen.
To be able to install these apps go to Settings, General, Security, and click on Unknown Sources and click Yes.
All of these apps will ask for Root Access and if you have completed Step 2, a window will pop up asking if you want to give these apps Root Access and do so by clicking on Grant.
Step 1: Download Stump Root and use brute force method and give it about 5 to 10 minutes to do it's thing.
Step 2: Once gaining root access go and download SuperSU as you will need this to grant root privileges.
Step 3: Download Freedom Flex as this will let you flash a custom recovery that will work on this device. Choose either ClockworkMod(CWM) or TWRP it is your choice. I recommend CWM.
Step 4: Go and download BusyBox as you will need this to run some apps and click install.
That's it! You now have root access and a custom recovery to allow you to flash such things as custom ROMS, etc..
Credit and applause goes out to the developers of these apps you guys are the real MVP :good:

What is "BRUTE FORCE METHOD"
---------- Post added at 08:52 AM ---------- Previous post was at 08:48 AM ----------
I didn't see a "BRUTE FORCE METHOD" toggle and menu button doesn't open any menu. When I click "GRIND" this is the screen I get.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It says "device is patched, sorry". I'm on T-Mobile D95920S. Flashed back to stock via the lg flash tool and the D95920H.kdz then took the first update to D95920M. Then went into the clock setting and unchecked " use network time". Then changed the date to March 18, 2015. So the next update would prompt me to download. I did then installed then downloaded everything from your links. And STUMP ROOT did not work. Didn't even try to work.

That's a problem I've never seen before maybe it has something to do with going back to stock let me get back to you.
Sent from my AT&T LG G Flex ?

I went back to jellybean and came all the way up through the updates trying it on everyone. Only jellybean 4.2.2 rooted with stumproot. I even read somewhere that you must delete all SuperSU files left over after unrooting and have no signs of it being rooted previously or it might cause it to think its already rooted or fail. I don't know why or how true that is. Bit better safe than sorry.
I can root the D95920M update with towelroot but that's as far as I can get rooted.
I'm gonna extract the update and edit out the last line in the meta-inf folder that reboots the phone after update since it will update using twrp. And then navigate back to TWRP HOME screen and install a SuperSU.zip and also flash my flashable bumped TWRP.ZIP maybe I can gain root again and TWRP before I ever reboot. I'll keep ya filled in on what happens.

Okay, I've tried towel root before on my current phone but it never worked, stump root was the only one click root I got to work.
Sent from my AT&T LG G Flex ?

Is this working with the sprint ls995
sent from omicron persei 8

Hi, followed all the instructions but when I installed freedom flex and clicked Install TWRP, nothing is happening. What am i missing?
Thanks

Click boot to recovery and see
sent from Omicron Persei 8

Yeah exactly boot to recovery, and make sure freedom flex got root privileges
Sent from my AT&T LG G Flex ?

jroiddoes195 said:
Yeah exactly boot to recovery, and make sure freedom flex got root privileges
Sent from my AT&T LG G Flex
Click to expand...
Click to collapse
Hi, I mean to say I installed the Freedom Flex app and pressed Install TWRP and nothing happens. Do I have to download any .zip. If so, which one.
ALso when try to boot to recovery, (i.e. press power and volume down key together), nothing happens, it just gets stuck on LG screen.
Yes, I am rooted and Freedom flex has got root priveleges

Does it say this on the bottom of the app?
Sent from my AT&T LG G Flex ?

Also since you have root I recommend downloading this app called boot droid make sure to give it root access. It will allow you to reboot into recovery easy. https://play.google.com/store/apps/details?id=com.impsycho.bootdroid
Sent from my AT&T LG G Flex ?

Thank you so much. That was the easiest root i have ever done.

You're very welcome!
Sent from my AT&T LG G Flex ?

What rom can I use with an AT&T G Flex after i rooted

not working on rogers d950 with 4.4.2
jroiddoes195 said:
As I realize that there are probably a number of threads regarding rooting of the LG G Flex, I wanted to make a simple guide in my own words to sort of give back to the developing community. I will be providing a number of attachments so that you won't have to go searching yourself. Before proceeding with this make any necessary backups and realize that this will void you're warranty and quite possibly brick or screw up you're phone and this is to be done with caution. I am in no way responsible for what might or might not happen.
To be able to install these apps go to Settings, General, Security, and click on Unknown Sources and click Yes.
All of these apps will ask for Root Access and if you have completed Step 2, a window will pop up asking if you want to give these apps Root Access and do so by clicking on Grant.
Step 1: Download Stump Root and use brute force method and give it about 5 to 10 minutes to do it's thing.
Step 2: Once gaining root access go and download SuperSU as you will need this to grant root privileges.
Step 3: Download Freedom Flex as this will let you flash a custom recovery that will work on this device. Choose either ClockworkMod(CWM) or TWRP it is your choice. I recommend CWM.
Step 4: Go and download BusyBox as you will need this to run some apps and click install.
That's it! You now have root access and a custom recovery to allow you to flash such things as custom ROMS, etc..
Credit and applause goes out to the developers of these apps you guys are the real MVP :good:
Click to expand...
Click to collapse
Unfortunatly even after hard reset says device not supported...

Ls-955 sprint
Working on KitKat 4.4.2 very easy and simple guide. Was
Was non rooted before.
Thanks

LGL23 not working
Just some heads up that this method didnt work for my LGL23.
There is a stump version 1.0 that comes with a file g_flex_rootkit.zip that works for LGL23 on 4.2.2.
If you have a LGL23 from KDDI in Japan you might want to check out my summary of experience.
http://forum.xda-developers.com/showpost.php?p=59585070&postcount=15

Worked on my LS-995 from Sprint, fully updated. Thanks.

GRRRRRRRR OTA Corrupted What in the ???? [Solved]

[Edit 4/4/2015]: Solved: Apparently the previous owner installed a custom kernel (without changing the kernel version) in order to disable encryption. Fixed via unlocking/wiping/rooting/installing a 5.1 ROM from XDA, and setting up my phone again from scratch. Thank you to everyone who posted. See this post for my process.
-------------------------
Original post:
The picture explains all.
http://i.imgur.com/C9GhN3y.jpg

Paul22000 said:
The picture explains all.
http://i.imgur.com/C9GhN3y.jpg
WHAT in the F!!!!!!!!!!!!????????????????
Click to expand...
Click to collapse
This is the second time I've, personally, seen this reported. Was your device purchased from T-Mobile or another source?

Paul22000 said:
The picture explains all.
http://i.imgur.com/C9GhN3y.jpg
WHAT in the F!!!!!!!!!!!!????????????????
Click to expand...
Click to collapse
if you have changed any system files, any at all, then you cant flash the ota, not even if you sideload it.

simms22 said:
if you have changed any system files, any at all, then you cant flash the ota, not even if you sideload it.
Click to expand...
Click to collapse
He couldn't have changed any system files. He's not rooted.
---------- Post added at 02:53 PM ---------- Previous post was at 02:53 PM ----------
Paul22000 said:
The picture explains all.
http://i.imgur.com/C9GhN3y.jpg
WHAT in the F!!!!!!!!!!!!????????????????
Click to expand...
Click to collapse
Which drivers are you using. Are you using mfastboot for sideload. I've heard that works better.

Evolution_Freak said:
This is the second time I've, personally, seen this reported. Was your device purchased from T-Mobile or another source?
Click to expand...
Click to collapse
I purchased it from Amazon in "Like New" and "Perfect condition", which indeed it was. I've been using it for a month now without a single issue whatsoever.
A) What does the above error message mean, and how can I install 5.1 without wiping?
Edit: B) What was the solution for the other case that you saw this?
simms22 said:
if you have changed any system files, any at all, then you cant flash the ota, not even if you sideload it.
Click to expand...
Click to collapse
I have not changed a single thing. Absolutely nothing. How do I install 5.1 without wiping?

toknitup420 said:
He couldn't have changed any system files. He's not rooted.
---------- Post added at 02:53 PM ---------- Previous post was at 02:53 PM ----------
Which drivers are you using. Are you using mfastboot for sideload. I've heard that works better.
Click to expand...
Click to collapse
Exactly. I haven't changed anything. Recovery is stock as well.
I was using "adb sideload" and I installed the newest drivers straight from Google as of 45 minutes ago. "Adb devices" in recovery was clearly showing my device right before entering the "adb sideload" command.
What is mfastboot? And do you think it will overcome this error?

Paul22000 said:
I purchased it from Amazon in "Like New" and "Perfect condition", which indeed it was. I've been using it for a month now without a single issue whatsoever.
A) What does the above error message mean, and how can I install 5.1 without wiping?
Edit: B) What was the solution for the other case that you saw this?
I have not changed a single thing. Absolutely nothing. How do I install 5.1 without wiping?
Click to expand...
Click to collapse
Here's the link to the other thread:
http://forum.xda-developers.com/showthread.php?t=3069402
What is your current software version? Is it LRX22C or something else? I'm asking because I want to be sure that when you tried to sideload, you used the proper one for the software version you have/want.
---------- Post added at 03:03 PM ---------- Previous post was at 03:02 PM ----------
Also, it is possible that the person who owned it before you made alterations that were not completely removed before you purchased it.

Evolution_Freak said:
Here's the link to the other thread:
http://forum.xda-developers.com/showthread.php?t=3069402
What is your current software version? Is it LRX22C or something else? I'm asking because I want to be sure that when you tried to sideload, you used the proper one for the software version you have/want.
---------- Post added at 03:03 PM ---------- Previous post was at 03:02 PM ----------
Also, it is possible that the person who owned it before you made alterations that were not completely removed before you purchased it.
Click to expand...
Click to collapse
Yes LRX22C. I used this one: LRX22C to LMY47M for T-Mobile http://android.clients.google.com/p...ed-shamu-ota-LMY47M-from-LRX22C-fullradio.zip
How can I investigate to see what the first owner changed? I don't want to wipe and find out it still doesn't work. And just for my knowledge, I do want to find out exactly what is the cause or changed files.

can always flash the factory img via fastboot, while the device is in its bootloader.

I wonder if this might partly be related to having a T-Mobile SIM and being purchased from Amazon - because the OTA is controlled by the carrier but perhaps they still have an IMEI check during the process. It seems unlikely, but my only guess at this time.
It's also possible that the prior owner unlocked, rooted, changed something and then unrooted+relocked, but seems a low probability.
A good test might be to remove the SIM, factory wipe and then bootup to see if the current Google OTA (to 5.1 "D") happens during the impending setup. But, you don't want to wipe at this time . . . btw, I took both the OTA and did a fastboot process - the latter process was easy, just took some time to do safely.
- ooofest

simms22 said:
can always flash the factory img via fastboot, while the device is in its bootloader.
Click to expand...
Click to collapse
This would also be my suggestion. However there is no factory image for LMY47M so you would have to use LRX22C and then apply the "M" version again via sideload.

ooofest said:
I wonder if this might partly be related to having a T-Mobile SIM and being purchased from Amazon - because the OTA is controlled by the carrier but perhaps they still have an IMEI check during the process. It seems unlikely, but my only guess at this time.
A good test might be to remove the SIM, factory wipe and then bootup to see if the current Google OTA (to 5.1 "D") happens during the impending setup. But, you don't want to wipe at this time, so I suppose checking to ensure you have the correct image for sideloading is your next step (per Evolution_Freak).
- ooofest
Click to expand...
Click to collapse
na.. you could buy a n6 from verizon, put in a tmobile sim, and get the update(for tmo). updates are related to your sim card, not to where you bought the n6. the ota is still controlled by google, not the carrier.

ooofest said:
I wonder if this might partly be related to having a T-Mobile SIM and being purchased from Amazon - because the OTA is controlled by the carrier but perhaps they still have an IMEI check during the process. It seems unlikely, but my only guess at this time.
It's also possible that the prior owner unlocked, rooted, changed something and then unrooted+relocked, but seems a low probability.
A good test might be to remove the SIM, factory wipe and then bootup to see if the current Google OTA (to 5.1 "D") happens during the impending setup. But, you don't want to wipe at this time . . . btw, I took both the OTA and did a fastboot process - the latter process was easy, just took some time to do safely.
- ooofest
Click to expand...
Click to collapse
I'm also wondering if this is a possibility. If you check the other thread I linked, the user was on T-Mobile with a Google play purchased device.

Evolution_Freak said:
This would also be my suggestion. However there is no factory image for LMY47M so you would have to use LRX22C and then apply the "M" version again via sideload.
Click to expand...
Click to collapse
Can you link me to the proper method for doing this? Will this cause a wipe?

simms22 said:
na.. you could buy a n6 from verizon, put in a tmobile sim, and get the update(for tmo). updates are related to your sim card, not to where you bought the n6. the ota is still controlled by google, not the carrier.
Click to expand...
Click to collapse
Maybe it's a terminology thing for me, then: Google controls their OTA (at "D" for the Nexus 6 right now, it appears), but the Verizon SIM was apparently holding my phone back from getting an update notification. So, I think you said the same thing and maybe I didn't express myself clearly before.
However, doesn't the T-Mobile OTA put their enabled phones at 5.1 "M"?
- ooofest

ooofest said:
Maybe it's a terminology thing for me, then: Google controls their OTA (at "D" for the Nexus 6 right now, it appears), but the Verizon SIM was apparently holding my phone back from getting an update notification. So, I think you said the same thing and maybe I didn't express myself clearly before.
However, doesn't the T-Mobile OTA put their enabled phones at 5.1 "M"?
- ooofest
Click to expand...
Click to collapse
m is "supposedly" for tmobile devices, but it seems as any of the updates work on any carrier. right now im on the 47I version, while on tmobile, while volte is working on my device properly. i was on m last week though
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

simms22 said:
m is "supposedly" for tmobile devices, but it seems as any of the updates work on any carrier. right now im on the 47I version, while on tmobile, while volte is working on my device properly. i was on m last week though
Click to expand...
Click to collapse
Yeah, I had "D" (via no-SIM+factory reset OTA) before E (via fastboot) on Verizon with the same general capabilities.
I was just wondering out loud if these supposedly carrier-specific updates might actually be installing to phones on their respective networks via OTA, because the T-Mobile Nexus 6 page seems to imply that their subscribers get "M". In that case, that might lend further credence to the idea that OTAs are more particular, based on your SIM (at the very least), but maybe there's other criteria at this time, too (like, white-listed IMEI).
- ooofest

Paul22000 said:
Can you link me to the proper method for doing this? Will this cause a wipe?
Click to expand...
Click to collapse
Yes, installing a factory image requires unlocking the bootloader which wipes your device. There's a thread in the general forum that explains all of this.
---------- Post added at 03:41 PM ---------- Previous post was at 03:38 PM ----------
Based on the info that @simms22 provided above, I would suggest first trying to sideload LRX22C to LMY47I first. If it fails again, then I would suggest the factory image route.

Paul22000 said:
Can you link me to the proper method for doing this? Will this cause a wipe?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=59853083&postcount=6

thacounty said:
http://forum.xda-developers.com/showpost.php?p=59853083&postcount=6
Click to expand...
Click to collapse
The user in this thread requesting help has a locked bootloader and is stock. Using fastboot to flash the images separately is not an option at this point because he doesn't want to wipe to unlock.

Droid Turbo (XT1254) autoiniroot problem

Hey.
I have a Droid Turbo XT1254 with bootloader locked (I am planning to unlock soon).
Recently, I stumbled across the thread and saw that someone had made rooting MCG25.251-5-5 possible and it made me want to try it out.
Anyways, I downloaded all the files (magisk and autoinitroot) and was able to root my phone just fine.
I tried giving Super user permission to some apps, and it worked flawlessly. I then tried to install Magisk module but oddly enough it failed.
It gave me an error that magisk was not properly installed. Also the SafetyNet check failed.
I decided to uninstall root, factory reset my device and root the device again.
Now the thing is that when I booted back into fastboot and ran the command that was meant to uninstall the root, it failed.
Obviously, I made sure that I was typing the correct command, I didn't even miss the "" marks. But it still didn't work.
It only gave me an error that the command 'confirm' doesn't exist.
I tried running the autoinit script and I booted just fine.
But the problem is that magisk isn't working properly and I'm unable to uninstall the autoinit root.
Any help will be greatly appreciated.
Also, Im using minimal adb and fast boot setup. Not sure if that's what causing the uninstall to fail or not.
TL; DR: Magisk doesn't work properly after doing the autoinitroot and I'm unable to uninstall the root by using the command that was mentioned in the original post.
Thanks for taking the time to read it

DuringSummer said:
Hey.
I have a Droid Turbo XT1254 with bootloader locked (I am planning to unlock soon).
Recently, I stumbled across the thread and saw that someone had made rooting MCG25.251-5-5 possible and it made me want to try it out.
Anyways, I downloaded all the files (magisk and autoinitroot) and was able to root my phone just fine.
I tried giving Super user permission to some apps, and it worked flawlessly. I then tried to install Magisk module but oddly enough it failed.
It gave me an error that magisk was not properly installed. Also the SafetyNet check failed.
I decided to uninstall root, factory reset my device and root the device again.
Now the thing is that when I booted back into fastboot and ran the command that was meant to uninstall the root, it failed.
Obviously, I made sure that I was typing the correct command, I didn't even miss the "" marks. But it still didn't work.
It only gave me an error that the command 'confirm' doesn't exist.
I tried running the autoinit script and I booted just fine.
But the problem is that magisk isn't working properly and I'm unable to uninstall the autoinit root.
Any help will be greatly appreciated.
Also, Im using minimal adb and fast boot setup. Not sure if that's what causing the uninstall to fail or not.
TL; DR: Magisk doesn't work properly after doing the autoinitroot and I'm unable to uninstall the root by using the command that was mentioned in the original post.
Thanks for taking the time to read it
Click to expand...
Click to collapse
1) why are you waiting to unlock your bootloader? Temp root is unstable and won't give you what you want.
2) of course Magisk won't work until you unlock your bootloader. Why would you think otherwise? On Motorola phones you have to unlock the bootloader to make changes like permanent root, install custom recovery, etc. Magisk just hides that.
3) you SAY you typed the correct command but after having a back-and-forth for two days over three pages with someone else who claimed the same thing and was WRONG, I'm skeptical.
Type exactly what you think is the correct command. Don't copy and paste anything. Actually type it out.
Better yet, post screenshot. That's how we proved to the other guy he was not reading what we had written.
"Oh, I didn't know."
Yes he did. It was in post #2, the very FIRST reply in the thread, which I wrote. And I told him over and over to go re-read that post!

Thanks for replying.
The answer to the first question is that I don't have $$$ right now. Will do it next month or so.
#2: Hahah. I did read that thread, and I'm pretty sure I'm not making that mistake, In any case I'll attach screenshots.

This is the screenshot. This time I tried specifying the directory to the fastboot.exe that came with autoinitroot, still no luck. Same error comes up regardless of whether I specify the directory or just use normal fastboot the came with minimal ADB.
And yes. I did it while I was in fastboot mode.
For some reason the app won't let me upload screenshot. Here is the link instead
http://i.imgur.com/Y5L5kvw.png

ChazzMatt said:
1) why are you waiting to unlock your bootloader? Temp root is unstable and won't give you what you want.
2) of course Magisk won't work until you unlock your bootloader. Why would you think otherwise? On Motorola phones you have to unlock the bootloader to make changes like permanent root, install custom recovery, etc. Magisk just hides that.
3) you SAY you typed the correct command but after having a back-and-forth for two days over three pages with someone else who claimed the same thing and was WRONG, I'm skeptical.
Type exactly what you think is the correct command. Don't copy and paste anything. Actually type it out.
Better yet, post screenshot. That's how we proved to the other guy he was not reading what we had written.
"Oh, I didn't know."
Yes he did. It was in post #2, the very FIRST reply in the thread, which I wrote. And I told him over and over to go re-read that post!
Click to expand...
Click to collapse
Yeah but in the original thread by autoprime, users have posted that they managed to install modules like "xposed systemless" etc. No reason it shouldn't work on mine.
Edit: Furthermore, autoptime himself mentioned that we can use custom magisk script to avoid boot loop, as far as I understand that's only possible when magisk recognizes modules.
Thing is that I have root, I can even use apps like titanium backup and whatnot. I can't use the script he mentioned unless magisk allows me to install something.

DuringSummer said:
This is the screenshot. This time I tried specifying the directory to the fastboot.exe that came with autoinitroot, still no luck. Same error comes up regardless of whether I specify the directory or just use normal fastboot the came with minimal ADB.
And yes. I did it while I was in fastboot mode.
For some reason the app won't let me upload screenshot. Here is the link instead
http://i.imgur.com/Y5L5kvw.png
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Your screenshot shows you typed "confirm". That's not the right command. It's "config".
fastboot oem config fsg-id ""

ChazzMatt said:
Your screenshot shows you typed "confirm". That's not the right command. It's "config".
fastboot oem config fsg-id ""
Click to expand...
Click to collapse
Oh. Hell. I feel stupid. I kinda copied from one the comments in OP. Will update brb.

Still doesn't work. This time it gave me error (bootloader) something-suffixes: false.
Etc etc. Will post screenshot.
EDIT: It WORKED. I placed the autoinitroot to desktop and changed the directory along with folder names. Ran the command, seems to have worked. Thanks anyways.
Probably had something to do with really long directory name. Idk.

DuringSummer said:
Yeah but in the original thread by autoprime, users have posted that they managed to install modules like "xposed systemless" etc. No reason it shouldn't work on mine.
Click to expand...
Click to collapse
Show me examples of that with Motorola phones.
I also have extensive experience with LG phones, and many of those (like LG G2 and LG G3) do not need bootloader unlock to root and install custom recovery. Whereas, Motorola phones require unlocked bootloader.
---------- Post added at 03:27 PM ---------- Previous post was at 03:21 PM ----------
DuringSummer said:
Still doesn't work. This time it gave me error (bootloader) something-suffixes: false.
Etc etc. Will post screenshot.
EDIT: It WORKED. I placed the autoinitroot to desktop and changed the directory along with folder names. Ran the command, seems to have worked. Thanks anyways.
Probably had something to do with really long directory name. Idk.
Click to expand...
Click to collapse
Yes, the suffixes errors are normal. Only by rebooting do you see if it worked.

ChazzMatt said:
Show me examples of that with Motorola phones.
I also have extensive experience with LG phones, and many of those (like LG G2 and LG G3) do not need bootloader unlock to root and install custom recovery. Whereas, Motorola phones require unlocked bootloader.
Click to expand...
Click to collapse
http://i.imgur.com/u06AaAV.png
http://i.imgur.com/7AHc5Bk.png
He explicitly mentioned that about bootloader locked Moto. Also the tool only works on Moto so.

DuringSummer said:
http://i.imgur.com/u06AaAV.png
http://i.imgur.com/7AHc5Bk.png
He explicitly mentioned that about bootloader locked Moto. Also the tool only works on Moto so.
Click to expand...
Click to collapse
Well, I know he was wrong about one thing. When the phone reboots it doesn't just boot into a stock system. Instead it bootloops and gets hung on the Moto logo. It never finishes booting until you run that end temp root command in fastboot.
Go to the thread and ask him how to do what he describes.... He is an expert and knows a lot more than me.
But also remember if your phone reboots in any way while you are away from your computer with fastboot installation, your phone will be totally useless until you get back to your computer and temp re-root or run that end temp root command.

ChazzMatt said:
Well, I know he was wrong about one thing. When the phone reboots it doesn't just boot into a stock system. Instead it bootloops and gets hung on the Moto logo. It never finishes booting until you run that end temp root command.
Click to expand...
Click to collapse
Oh that. What he meant was that if you place the custom magisk script in the right folder it will avoid boot loop and will boot into stock system, from there you'll have to use autoinitroot tool from pc again to re-root it, the script is handy if you're going somewhere and won't have access to pc. In which case, even if your phone gets turned off or reboots, it won't bootloop like crazy and you get access to stock system. Though you won't have root until you run autoroot script again from PC.
Also, it does provides full root. The only downside is that it isn't permanent. So as long as you're careful and don't mess with system and only use systemless modifications using magisk, you're safe. In worst case scenarios you'll only have to run the unroot command and factory reset to go back to 100% stock.
It's useful for those who can't get their bootloader unlocked.
Sadly, In my case magisk isn't working properly. That's why I'll factory reset and try again. Hopefully it'll work then.
Also do you by any chance know how and where to place custom scripts of magisk? Will be doing that after factory reset.
Also you helped a lot. Thanks, mate

DuringSummer said:
Oh that. What he meant was that if you place the custom magisk script in the right folder it will avoid boot loop and will boot into stock system, from there you'll have to use autoinitroot tool from pc again to re-root it, the script is handy if you're going somewhere and won't have access to pc. In which case, even if your phone gets turned off or reboots, it won't bootloop like crazy and you get access to stock system. Though you won't have root until you run autoroot script again from PC.
Also, it does provides full root. The only downside is that it isn't permanent. So as long as you're careful and don't mess with system and only use systemless modifications using magisk, you're safe. In worst case scenarios you'll only have to run the unroot command and factory reset to go back to 100% stock.
It's useful for those who can't get their bootloader unlocked.
Sadly, In my case magisk isn't working properly. That's why I'll factory reset and try again. Hopefully it'll work then.
Also do you by any chance know how and where to place custom scripts of magisk? Will be doing that after factory reset.
Also you helped a lot. Thanks, mate
Click to expand...
Click to collapse
His post #2 seems to talk about folders.

ChazzMatt said:
His post #2 seems to talk about folders.
Click to expand...
Click to collapse
Yeah. Saw that. Couldn't find those folders. Checked both root and normal storage.
Thanks anyway.

The whole temp root thing is really just a way to proceed with the bootloader unlock. to use temp root on any daily driver just seems like more trouble than its worth. Hurry up and find 25 bucks!!!
My opinion is that for the work that these guys do its a small price to pay and was money well spent

bigmatt503 said:
The whole temp root thing is really just a way to proceed with the bootloader unlock. to use temp root on any daily driver just seems like more trouble than its worth. Hurry up and find 25 bucks!!!
My opinion is that for the work that these guys do its a small price to pay and was money well spent
Click to expand...
Click to collapse
Actually, I don't have any problem paying 25 bucks. The thing is that I'm planning to buy a new phone. Seems really pointless spending 25$ on something that I'll replace in a few months. At first I thought that I should get it unlocked, however, this phone is 3 years old. I decided that I should upgrade to current technology.

ChazzMatt said:
Show me examples of that with Motorola phones.
I also have extensive experience with LG phones, and many of those (like LG G2 and LG G3) do not need bootloader unlock to root and install custom recovery. Whereas, Motorola phones require unlocked bootloader.
---------- Post added at 03:27 PM ---------- Previous post was at 03:21 PM ----------
Yes, the suffixes errors are normal. Only by rebooting do you see if it worked.
Click to expand...
Click to collapse
Caution thread jacking...... since you are very familiar with LG phones. What are the chances of the verizon g6 ever getting root?
Sent from my VS988 using XDA-Developers Legacy app