I have a droid maxx on 12.15.15 update and rooted it using the telnet and adb way. I kept cancelling the last ota update becasue I wanted to make sure root was available. Anyway this morning i aciddently hit install now ;( It didn't install but now its stuck in boot loop. It powers up fine, but after everything loads a bout a minute later it says Power off...Shutting down.. and restarts and keeps boot looping. I've rooted all my other fons, but this is getting tricky. How can I fix this?? I don't mind installing ota if there is root availalble, but I just need my fon fixed! I'm on vacation 1400mi from home, but fortunately I have my old fon along. Any help would be greatly appreciated!
droidrepair said:
I have a droid maxx on 12.15.15 update and rooted it using the telnet and adb way. I kept cancelling the last ota update becasue I wanted to make sure root was available. Anyway this morning i aciddently hit install now ;( It didn't install but now its stuck in boot loop. It powers up fine, but after everything loads a bout a minute later it says Power off...Shutting down.. and restarts and keeps boot looping. I've rooted all my other fons, but this is getting tricky. How can I fix this?? I don't mind installing ota if there is root availalble, but I just need my fon fixed! I'm on vacation 1400mi from home, but fortunately I have my old fon along. Any help would be greatly appreciated!
Click to expand...
Click to collapse
You are bootlooping because the root method used on this phone removes the stock recovery, thus the phone keeps trying, and failing, to install the update. As far as I'm aware the only way you can get out of the bootloop is to boot into fastboot and re-flash stock 12.15.15 (luckily because the 4.4 update has not installed on your device you will be able to keep your lower firmware, and thus re-root). However I am not 100% sure this is the only solution, and this would wipe your phone as well. I recommend waiting for more responses or looking around for a possible other solution if you prefer to try to not wipe your phone....
Yachter99 said:
You are bootlooping because the root method used on this phone removes the stock recovery, thus the phone keeps trying, and failing, to install the update. As far as I'm aware the only way you can get out of the bootloop is to boot into fastboot and re-flash stock 12.15.15 (luckily because the 4.4 update has not installed on your device you will be able to keep your lower firmware, and thus re-root). However I am not 100% sure this is the only solution, and this would wipe your phone as well. I recommend waiting for more responses or looking around for a possible other solution if you prefer to try to not wipe your phone....
Click to expand...
Click to collapse
I haven't had time to look around and find the thread, but I was able to find a thread that allowed me to FXZ using fastboot to restore 12.15.15 and restore everything, leaving your data intact. Worked like a charm when I was stuck in the bootloop. So, it's doable.
@droidrepair do you have titanium back up installed and are you booting into the os even if momentarily?
Sent from my KitKat Ultra
Bump, this problem is an exact replica of what I am currently experiencing. You do get to boot into the OS for a little while, but after about (maybe) 1/2 a minute, it says powering off and reboots.
sangar66 said:
Bump, this problem is an exact replica of what I am currently experiencing. You do get to boot into the OS for a little while, but after about (maybe) 1/2 a minute, it says powering off and reboots.
Click to expand...
Click to collapse
OK. Do you have titanium back up?
Sent from my KitKat Ultra
Caseyk621 said:
OK. Do you have titanium back up?
Sent from my KitKat Ultra
Click to expand...
Click to collapse
Yes, but it was only to delete bloatware, there is no actual backup of what's on my phone. Additionally, I don't really care about recovering lost data, I just want to bring my phone to a working state.
sangar66 said:
Yes, but it was only to delete bloatware, there is no actual backup of what's on my phone. Additionally, I don't really care about recovering lost data, I just want to bring my phone to a working state.
Click to expand...
Click to collapse
That's ok. When you get to your os quickly go into titanium back find apk MotorolaOTA and freeze it. That should stop your bootloop. If it doesn't you may need to freeze an app called updater. Lemme know how it works out.
Sent from my KitKat Ultra
Caseyk621 said:
That's ok. When you get to your os quickly go into titanium back find apk MotorolaOTA and freeze it. That should stop your bootloop. If it doesn't you may need to freeze an app called updater. Lemme know how it works out.
Sent from my KitKat Ultra
Click to expand...
Click to collapse
I don't have the donate version of Titanium Backup, so I can't freeze things. Should I uninstall OTA?
sangar66 said:
I don't have the donate version of Titanium Backup, so I can't freeze things. Should I uninstall OTA?
Click to expand...
Click to collapse
Don't think that it would hurt your situation. Give it a try.
Sent from my KitKat Ultra
Caseyk621 said:
Don't think that it would hurt your situation. Give it a try.
Sent from my KitKat Ultra
Click to expand...
Click to collapse
I don't have time to uninstall, but I was able to get a telnet connection which I can use to find the process to kill (the update process), but I don't have permission to actually do so.
sangar66 said:
I don't have time to uninstall, but I was able to get a telnet connection which I can use to find the process to kill (the update process), but I don't have permission to actually do so.
Click to expand...
Click to collapse
Use House of Moto then to go back to stock. Use 12.15.15 fxz
Sent from my KitKat Ultra
no, i don't have ti backup. Fon is stock except for root.
Caseyk621 said:
Use House of Moto then to go back to stock. Use 12.15.15 fxz
^^^this^^^^
droidrepair said:
no, i don't have ti backup. Fon is stock except for root.
Click to expand...
Click to collapse
Sent from my KitKat Ultra
Click to expand...
Click to collapse
Ok i used houseofmoto 2 and fastboot and so far seems to be working fine! Thanks SamuraiHL and all!
Now i don't have root tho. I assume i'll be able to re root using telnet, etc? Or should i install ota and then root, or is that not possible yet?
droidrepair said:
Ok i used houseofmoto 2 and fastboot and so far seems to be working fine! Thanks SamuraiHL and all!
Now i don't have root tho. I assume i'll be able to re root using telnet, etc? Or should i install ota and then root, or is that not possible yet?
Click to expand...
Click to collapse
Don't take 4.4 OTA as there is no way to root it. You need to start the process on rooted 4.2.2 using the slapmymoto process nicely outlined here.
http://forum.xda-developers.com/showthread.php?t=2616104
[GUIDE V1.6][ROOT][4.2.2 TO 4.4] XT1080/M (Requires Rooted 4.2.2) 01/20/14
Sent from my KitKat Ultra
I rooted using https://docs.google.com/file/d/0B67RS0BDBp_iaVFhZDd2dmtaTFE/edit
do I need to use the method you show to do 4.4 ota?
Caseyk621 said:
Don't take 4.4 OTA as there is no way to root it. You need to start the process on rooted 4.2.2 using the slapmymoto process nicely outlined here.
http://forum.xda-developers.com/showthread.php?t=2616104
[GUIDE V1.6][ROOT][4.2.2 TO 4.4] XT1080/M (Requires Rooted 4.2.2) 01/20/14
Sent from my KitKat Ultra
Click to expand...
Click to collapse
droidrepair said:
I rooted using https://docs.google.com/file/d/0B67RS0BDBp_iaVFhZDd2dmtaTFE/edit
do I need to use the method you show to do 4.4 ota?
Click to expand...
Click to collapse
That's correct. You have 4.2.2 rooted now you can move on to start the rooting process for 4.4.
Sent from my KitKat Ultra
wow. It takes a lotta work to keep these things rooted and updated! oh well, educational i guess. Is there a stable 4.4 ota or is this just the one from dec that got pulled?
droidrepair said:
wow. It takes a lotta work to keep these things rooted and updated! oh well, educational i guess. Is there a stable 4.4 ota or is this just the one from dec that got pulled?
Click to expand...
Click to collapse
Yeah it does! They (vzw) re-released it in January. Its stable. Just follow instructions to a t and you'll be OK. Plenty of help around here as well.
Sent from my KitKat Ultra
Related
So I've rooted (the day it came out, so before the first update) and can't update anymore. It'll fail when attempting and reboot me. It wouldn't be an issue but I don't like getting popup reminders about the update. I've searched around but haven't found this issue and am hoping I don't have to reflash the stock rom to update again, I'd also like to keep all my stuff you know. Hopefully someone knows a solution. Sorry if this is dumb
iamheero said:
So I've rooted (the day it came out, so before the first update) and can't update anymore. It'll fail when attempting and reboot me. It wouldn't be an issue but I don't like getting popup reminders about the update. I've searched around but haven't found this issue and am hoping I don't have to reflash the stock rom to update again, I'd also like to keep all my stuff you know. Hopefully someone knows a solution. Sorry if this is dumb
Click to expand...
Click to collapse
Unroot, install update, reroot.
How to Unroot:
Thanks shabbypenguin for posting this.
You can manually unroot your Droid by using a root file manager program (such as root explorer) and mountsystem as R/W. Then delete the following:
/system/app/Superuser.apk
/system/bin/su
and if it has it
/system/xbin/su
EdwardN said:
Unroot, install update, reroot.
How to Unroot:
Thanks shabbypenguin for posting this.
You can manually unroot your Droid by using a root file manager program (such as root explorer) and mountsystem as R/W. Then delete the following:
/system/app/Superuser.apk
/system/bin/su
and if it has it
/system/xbin/su
Click to expand...
Click to collapse
Thanks! Unfortunately, it still fails about 10% of the way through the update. Since JB just came out I'll have to just flash to stock completely and try updating legitimately, then rooting it again, I guess.
iamheero said:
Thanks! Unfortunately, it still fails about 10% of the way through the update. Since JB just came out I'll have to just flash to stock completely and try updating legitimately, then rooting it again, I guess.
Click to expand...
Click to collapse
You may have solved this problem already but did you try using voodoo root keeper? It's a pretty straight forward way of backing up the root, unrooting to install the update, then rerooting when the update is installed.
Sent from my DROID RAZR HD using Tapatalk 2
Were you successful?
iamheero said:
Thanks! Unfortunately, it still fails about 10% of the way through the update. Since JB just came out I'll have to just flash to stock completely and try updating legitimately, then rooting it again, I guess.
Click to expand...
Click to collapse
I'm running into the same problem. Did the flash back to stock and subsequent update to JB work for you? If so, were can I download the stock OS?
mmettlen said:
I'm running into the same problem. Did the flash back to stock and subsequent update to JB work for you? If so, were can I download the stock OS?
Click to expand...
Click to collapse
Hey there, I had the same problem. Rooted, unrooted, frozen, deleted, restored, couldn't get anything to get JB to work. Eventually just gave up and flashed to stock. Used the amazing Utility presented here
just make sure to gain root access before going to the JB update. there is no present method for getting root on fresh phone with JB update.
Ok so one day my phone is all nice and dandy, rooted as a tree, and then I go to Advence Freeze an app, and Rom Toolbox Pro tells me I no longer have root access. So I go into Titanium backup and it says the same thing. For total verification, I go to Terminal Emulator, and the "su" command gives me a "not granted" response. So while I had root yesterday, for some reason I don't have it today. The thing I'm worried about most is that I did absolutely nothing in the meantime. The phone hadn't restarted in 3 days so that wasn't it. And all I did before it unrooted itself iis use the Inkpad Notepad app, and the Boat Browser app. I didn't touch a single thing that could possibly mess something up. Root hasn't always been very "observable" on my phone. After about a week after rooting it, Superuser stopped asking me if I wanted to allow or deny new apps. But all my root apps still worked. I run no special rom, just stock 4.1.2. I have SafeStrap Bootloader installed for backups as well. I downloaded Motochopper to try to reroot my phone just a few minutes ago and the exploit ran flawlessly. No errors whatsoever. When it booted up, still no root access. To be more specific, Voodoo OTA Root Keeper tells me the device is rooted, but without root access. I also have a root backup made with that program. Can someone please tell me how to fix this because the thought of a "normal" phone is making me depressed :crying:.
Try updating your SU and see if that does anything.
RikRong said:
Try updating your SU and see if that does anything.
Click to expand...
Click to collapse
The only way I could think of doing that is from the superuser app (if you mean update the binaries) and I already tried. It fails at "gettingroot access".
miapuffia said:
The only way I could think of doing that is from the superuser app (if you mean update the binaries) and I already tried. It fails at "gettingroot access".
Click to expand...
Click to collapse
Yeah, that's what I meant. Hmmm...
RikRong said:
Yeah, that's what I meant. Hmmm...
Click to expand...
Click to collapse
Perhaps I could backup my data using SafeStrap TWRP, download stock rooted 4.3 (which I wanted since it came out), install it to rom slot 2 using SafeStrap, and then restore my data! Where's my nobel prize? lol Would that work?
miapuffia said:
Perhaps I could backup my data using SafeStrap TWRP, download stock rooted 4.3 (which I wanted since it came out), install it to rom slot 2 using SafeStrap, and then restore my data! Where's my nobel prize? lol Would that work?
Click to expand...
Click to collapse
There is no stock 4.3 ROM for us. The highest stock version would be 4.1.2. You can get CM10.2 that is vanilla AOSP, but I don't know if it would boot on SS.
RikRong said:
There is no stock 4.3 ROM for us. The highest stock version would be 4.1.2. You can get CM10.2 that is vanilla AOSP, but I don't know if it would boot on SS.
Click to expand...
Click to collapse
I see. That's why my rooted 4.3 search came up.blank. I don't mind trying CM. I tried to SS install it previously but it failed (kinda). But now that I think about it I definitely installed the wrong version. As long as I can restore my data to CM I don't mind trying it. Can I get 4.1.2, root it, and then restore data? But wait, I know my bro has 4.3 rooted he used temp unroot -> update -> restore root. Can I do that? In case you didn't notice I'm new to this :/
I just got an email from Motorola offering me to test out the new version of Android for the Ultra, Maxx, and Mini.
That means such will be pushed to the general users within a few days or possibly a week.
From my past experience with such updates, the #1 change is to close any loopholes being used to root the devices. Therefore, I have very little interest in ever updating the O/S now that I do have root.
Is there a way I can stop my phone from checking, and installing, such updates? Such would including blocking the nag popups.
hmm...soak test for camera update possibly? I haven't gotten anything yet for mine...hopefully someone can make this flashable for SS and we'll be fine..
On the maxx hd there was an app that you freeze that made it not download updates.
Sent from my XT1080m using xda-developers app.
This thread talks about how to do it for the Moto X (which is basically the same thing, right?).
http://forum.xda-developers.com/showthread.php?t=2466191
I read through the instructions, and everything seems straight forward until it gets to the part about flashing stock recovery and such.
Will this method work for the MAXX? If so, where do we find the .img files we would need?
It use to be to "freeze" BlurUpdater_VZW.apk and Upgrader.apk. But I don't see those apps, nor any app with a similar name, in /systems/apps.
WaltA said:
It use to be to "freeze" BlurUpdater_VZW.apk and Upgrader.apk. But I don't see those apps, nor any app with a similar name, in /systems/apps.
Click to expand...
Click to collapse
So if all I needed root for was for the entitlement hack (and I've heard that survives the new OTA) could I just accept this OTA knowing that I will lose root? Or will it not install?
Your right in system/app I do not see an updater.apk, but in Titanium backup I do see one to freeze? That should work to stop updates, it did in the past.
WaltA said:
It use to be to "freeze" BlurUpdater_VZW.apk and Upgrader.apk. But I don't see those apps, nor any app with a similar name, in /systems/apps.
Click to expand...
Click to collapse
if youve removed any system apps from the device..the update will fail automatically
dano1282 said:
if youve removed any system apps from the device..the update will fail automatically
Click to expand...
Click to collapse
All I've done was pwnmymoto for root, the entitlement hack, and disable a bunch of apps. can I accept the OTA?
redddog said:
All I've done was pwnmymoto for root, the entitlement hack, and disable a bunch of apps. can I accept the OTA?
Click to expand...
Click to collapse
yes..but root most likely won't survive..youll have to rsd back to stock...download pwnmymoto. install it but don't run it... accept the ota and then the phone will reboot and it should be rooted...should be LOL
Freezing updater . apk doesn't stop the prompts to update.
Sent from my XT1080m using Tapatalk
jfriend33 said:
Freezing updater . apk doesn't stop the prompts to update.
Click to expand...
Click to collapse
Did you freeze MotorolaOTA in addition to Updater?
dano1282 said:
yes..but root most likely won't survive..youll have to rsd back to stock...download pwnmymoto. install it but don't run it... accept the ota and then the phone will reboot and it should be rooted...should be LOL
Click to expand...
Click to collapse
So this is NOT true?
Seems as if I would accept OTA, I'm looking at the business end of a bootloop?
WaltA said:
Did you freeze MotorolaOTA in addition to Updater?
Click to expand...
Click to collapse
No. I assume I'd have to use titanium backup to freeze the MotorolaOTA app?
Sent from my XT1080m using Tapatalk
jfriend33 said:
No. I assume I'd have to use titanium backup to freeze the MotorolaOTA app?
Click to expand...
Click to collapse
I did, to freeze both (Updater and MotorolaOTA).
WaltA said:
I did, to freeze both (Updater and MotorolaOTA).
Click to expand...
Click to collapse
I did this and it stopped the download (I'm rooted and down have time today with messing around with unbricking a bootlooping phone).
I'm glad I happened to look at my phone on my way home from work because it appears that this update just inflicts itself on the phone without any real chance to decline it (at 2am when most people are sleeping).
My Maxx installed the update this morning and has been stuck in a constant reboot cycle ever since. It will boot long enough for me to go in and check on the update (which states that the "Install is deferred") then simply reboots again and again. There is also a code 252 on the software install screen.
Can anyone help me get out of the reboot cycle? My phone is rooted with the entitlement check set to 0, other than that completely stock.
cmarshack said:
My Maxx installed the update this morning and has been stuck in a constant reboot cycle ever since. It will boot long enough for me to go in and check on the update (which states that the "Install is deferred") then simply reboots again and again. There is also a code 252 on the software install screen.
Can anyone help me get out of the reboot cycle? My phone is rooted with the entitlement check set to 0, other than that completely stock.
Click to expand...
Click to collapse
I'm in the EXACT same boat as you. Hoping someone has a solution to this.
cmarshack said:
My Maxx installed the update this morning and has been stuck in a constant reboot cycle ever since. It will boot long enough for me to go in and check on the update (which states that the "Install is deferred") then simply reboots again and again. There is also a code 252 on the software install screen.
Can anyone help me get out of the reboot cycle? My phone is rooted with the entitlement check set to 0, other than that completely stock.
Click to expand...
Click to collapse
You were probably rooted and thus lost your recovery from pwnmymoto. You need to fxz back to stock.
Sent from my XT1080m using Tapatalk
jfriend33 said:
You were probably rooted and thus lost your recovery from pwnmymoto. You need to fxz back to stock.
Sent from my XT1080m using Tapatalk
Click to expand...
Click to collapse
What is the process for "fat back to stock?"
does anyone know what the new I535VRUCNC1 has to offer over the ML1 update?
esjames said:
does anyone know what the new I535VRUCNC1 has to offer over the ML1 update?
Click to expand...
Click to collapse
Literally one thing: http://www.verizonwireless.com/dam/support/pdf/system_update/galaxy_s3-4.30.14.pdf
Well, then. Thats a worthy update lol
esjames said:
Well, then. Thats a worthy update lol
Click to expand...
Click to collapse
by all means, if you're traveling to Canada then update away haha
Lmao wow. That's the most pitiful update ever. Seriously, couldn't they have waited until there was something more substantial and then included Canadian roaming in THAT update. As always though, Verizon is dumber than a bag of hammers...
Sent from my iPhone using Tapatalk
Might be worthwhile to extract the modem package and see if the SMS bug is rectified.
wow
i was so sure this was a KK upgrade. been looking around for how to retain root if you take it. thanks for the info!
Hey guys, I have a question about this update,
My friend has the S3 for whom I safe- rooted, debloated and whatnot. Now that this update came, my friend tried to update but to no avail. She is adamant about the fact that Verizon definitely has something important hidden in the update, despite me trying to tell her otherwise, and figured that she couldn't install the update because she was rooted.
Naturally, I fully unroot her entire phone, uninstall root-only apps, and try the update, but it doesn't work. When the phone reboots for installation, the installation bar loads for a bit,hangs, then just says "error" and does not update.
Anyone know what the problem could be? Normally I wouldn't care so much, but if Android 4.4 is actually coming to the S3 then I don't want her not to have it, and I can already tell it's not going to work if this update doesn't either.
Thank you so much in advance.
EddieK23 said:
Hey guys, I have a question about this update,
My friend has the S3 for whom I safe- rooted, debloated and whatnot. Now that this update came, my friend tried to update but to no avail. She is adamant about the fact that Verizon definitely has something important hidden in the update, despite me trying to tell her otherwise, and figured that she couldn't install the update because she was rooted.
Naturally, I fully unroot her entire phone, uninstall root-only apps, and try the update, but it doesn't work. When the phone reboots for installation, the installation bar loads for a bit,hangs, then just says "error" and does not update.
Anyone know what the problem could be? Normally I wouldn't care so much, but if Android 4.4 is actually coming to the S3 then I don't want her not to have it, and I can already tell it's not going to work if this update doesn't either.
Thank you so much in advance.
Click to expand...
Click to collapse
Some of the bloatware you removed likely had to be present on the phone in order for the update to take place. Unless you are sure someone is never going to go back to stock without flashing an ODIN tar image and wiping their phone clean, best to just freeze bloatware with Titanium Backup. That way you can just unfreeze it in order to go back to full stock. Unless you have a list of the bloatware you removed and can somehow sideload them back in, you will unfortunately have to flash her phone to full stock VRUCML1 and wipe it clean.
landshark68 said:
Some of the bloatware you removed likely had to be present on the phone in order for the update to take place. Unless you are sure someone is never going to go back to stock without flashing an ODIN tar image and wiping their phone clean, best to just freeze bloatware with Titanium Backup. That way you can just unfreeze it in order to go back to full stock. Unless you have a list of the bloatware you removed and can somehow sideload them back in, you will unfortunately have to flash her phone to full stock VRUCML1 and wipe it clean.
Click to expand...
Click to collapse
Ah, I see, next time I'm around her I'll re-root it and backup all her stuff with titanium backup, flash the VRUCML1 and factory reset, then restore everything and see if it works.
Strangely enough, when the same update for my Verizon Note 2 came out, I was able to update while rooted even though I unsinatalled theexact same system apps I did on her phone. How strange.
Nonetheless, thank you so much.
I have a question for you all. I took the OTA update for 4.3 when it came out but after that I rooted my gs3 Verizon phone again successfully. Now I also took this last update and now lost root on my phone. I tried to reroot the phone but it fails now. There error I get on safestrap is something about the addresses not being able to be found. Can anyone help me reroot my phone so my apps like titanium will work again?
Thanks
Joe R said:
I have a question for you all. I took the OTA update for 4.3 when it came out but after that I rooted my gs3 Verizon phone again successfully. Now I also took this last update and now lost root on my phone. I tried to reroot the phone but it fails now. There error I get on safestrap is something about the addresses not being able to be found. Can anyone help me reroot my phone so my apps like titanium will work again?
Thanks
Click to expand...
Click to collapse
U gotta Odin back to 4.3 ML1 .. The latest update unroots your fone. And can not be rooted.
Sent from my SCH-I535 using Tapatalk
Ok thanks. I will try to find an ML1 download.
Sent from my Samsung Galaxy S III using Tapatalk
Ok, since I'm not doing the update, how do I get rid of this nagging reminder popping up that I need to update?
pnuker said:
Ok, since I'm not doing the update, how do I get rid of this nagging reminder popping up that I need to update?
Click to expand...
Click to collapse
See here: http://forum.xda-developers.com/showthread.php?t=
Sent from my SCH-I535 using Tapatalk 4
Maintained root
twistedillutions said:
U gotta Odin back to 4.3 ML1 .. The latest update unroots your fone. And can not be rooted.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I was able to maintain root on the OTA update by having OTA Survival Mode checked on SuperSU.
SlimSnoopOS said:
See here: http://forum.xda-developers.com/showthread.php?t=
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Looks like the link is broken. I searched the forum and came up empty. Anyone know what the link should've been or how to disable this junk?
smalco44 said:
Looks like the link is broken. I searched the forum and came up empty. Anyone know what the link should've been or how to disable this junk?
Click to expand...
Click to collapse
Apparently I need a refresher on how to properly copy and paste Here's the link again: http://forum.xda-developers.com/showthread.php?p=52515244#post52515244
I have not yet updated to this new patch yet, am I still able to install saferoot as directed on the thread for it or do I need to do something special first?
Hey guys,
So I just got the G3 last week, and an update rolled out from AT&T. Me being the idiot I am thought it was the Lollipop update so I updated it. Turns out, it was just 10f.
Then when I looked for ways to root the G3, all the methods required the software to be on 10d, not f.
What should I do?
Any help is much appreciated.
Use the bruteforce method in Stump root.
see: http://forum.xda-developers.com/lg-g3/help/att-d85010f-update-stump-root-t2953063
You are certain it'll work for 10f?
sympathizer said:
You are certain it'll work for 10f?
Click to expand...
Click to collapse
100%. I rooted on 10f using stump.
In addition, if you plan on rooting a device and you know there is an update, please wait to install the update until you know a root method is found.
aybarrap1 said:
100%. I rooted on 10f using stump.
In addition, if you plan on rooting a device and you know there is an update, please wait to install the update until you know a root method is found.
Click to expand...
Click to collapse
Will do.
Thanks a lot!
Not rooting
sympathizer said:
Will do.
Thanks a lot!
Click to expand...
Click to collapse
I too am trying to root d850 10f with bruteforce on stumproot...mine will not do it though, keeps saying device is not supported after about 7 minutes of trying. Any ideas? (Yes, i know, shouldnt have installed the darn update), but i keep seeing people rooting 10f no problem with stump, although mine wont.
esanger22 said:
I too am trying to root d850 10f with bruteforce on stumproot...mine will not do it though, keeps saying device is not supported after about 7 minutes of trying. Any ideas? (Yes, i know, shouldnt have installed the darn update), but i keep seeing people rooting 10f no problem with stump, although mine wont.
Click to expand...
Click to collapse
You can always flash back to the older version 10d in the return to stock thread.
Sent from my LG-D850 using XDA Premium HD app
Intub8 said:
You can always flash back to the older version 10d in the return to stock thread.
Sent from my LG-D850 using XDA Premium HD app
Click to expand...
Click to collapse
This is what I would do. It is possible you got a bad OTA as well. Did you factory reset after the OTA? I have seen many cases on forums where a factory reset takes care of many issues after an OTA.
Sent from my LG-D850 using Tapatalk
esanger22 said:
I too am trying to root d850 10f with bruteforce on stumproot...mine will not do it though, keeps saying device is not supported after about 7 minutes of trying. Any ideas? (Yes, i know, shouldnt have installed the darn update), but i keep seeing people rooting 10f no problem with stump, although mine wont.
Click to expand...
Click to collapse
I don't know man, do you have the correct app installed? Mine went through smoothly in less than 5 minutes.
I just did this - now i am trying to bump the device. So my memory is relatively fresh
Reboot for fresh start - Run Stump - it will say device not supported - try brute force - let it run - takes 5 - 7 and maybe 10 min after which it says "reboot" device - then go ahead and reboot device. Run stump again - it should say device is rooted. Next download "root checker" it will say rooted. Ofcourse if this all does not go thru - you can downgrade to a previous firmware and it'll go easier - however that's more labor intensive and you'll not be able to back up the current ROM with all your apps and setup.
Well, I ended up having to flash back to 10d as mentioned by many of you. This fixed the problem!
esanger22 said:
Well, I ended up having to flash back to 10d as mentioned by many of you. This fixed the problem!
Click to expand...
Click to collapse
Good to hear and I do not think you are missing much going back. At least I have found no difference. Just freeze "Software Update" to prevent nagging OTA update notifications.
aybarrap1 said:
Good to hear and I do not think you are missing much going back. At least I have found no difference. Just freeze "Software Update" to prevent nagging OTA update notifications.
Click to expand...
Click to collapse
I actually installed CM12...its friggin awesome.
I can report no issues here with Stumproot on 10f and I've restored back to stock multiple times.
Sounds like something was just messed up on my phone, everyone else was able to use it!
perhaps this
http://forum.xda-developers.com/att-lg-g3/development/rom-stock-rooted-att-odexed-d85010f-t2945873
works nicely, no muss, no fuss
If i revert to 10D do i have to use the BUMP method after root? Or just get TWRP/CWM Recovery like good ole days? I just don't care to have the BUMP bypass that is why I am asking.
I have the ATT G3 10F.