Related
I just got a new LGG2 from Verizon upon receiving it i updated the new firmware to 25B ioroot isn't compatible any ideas how i can get root on this phone
Frankiejay said:
I just got a new LGG2 from Verizon upon receiving it i updated the new firmware to 25B ioroot isn't compatible any ideas how i can get root on this phone
Click to expand...
Click to collapse
Wait until it supports it..
Frankiejay said:
I just got a new LGG2 from Verizon upon receiving it i updated the new firmware to 25B ioroot isn't compatible any ideas how i can get root on this phone
Click to expand...
Click to collapse
If you have rooted 24A with a stock recovery, you can take the OTA and retain root..
Ok so I figured I'd ask here instead of making a new thread since it's sort of relevant. Hope not to thread jack. I have a vs980 rooted on 24a with stock rom and twrp. My phone tried to update to 25b yesterday and I canceled it by switching from WiFi to 4g. 2 questions I have are can I take the update and stay the same or not yet since I have twrp? And 2 it started downloading automatically, if I can't take the update is there a way to keep it from downloading again? Thanks in advance.
Okspeed3 said:
Ok so I figured I'd ask here instead of making a new thread since it's sort of relevant. Hope not to thread jack. I have a vs980 rooted on 24a with stock rom and twrp. My phone tried to update to 25b yesterday and I canceled it by switching from WiFi to 4g. 2 questions I have are can I take the update and stay the same or not yet since I have twrp? And 2 it started downloading automatically, if I can't take the update is there a way to keep it from downloading again? Thanks in advance.
Click to expand...
Click to collapse
1) It won't install without the factory recovery.
2) You have to remove/disable/freeze the updater app to stop it from prompting you. (I don't remember the exact name of it)
So there really isn't any harm in letting it download since it won't install without factory recovery? I'll check the apps I have frozen again I thought I froze it, but maybe not. Thanks. Do you know if it's simply called system updates?
Software Update is the app name people are freezing using Titanium, don't know what the .apk is, I have a debloated rom currently. You should be able to find and rename the .apk for Software Update to stop it.
I've been using ultimate backup lite and I have a system update app I could freeze just wanted to make sure it was the right one. Tried to post a picture, but I don't have enough seniority.
is ioroot still the best rooting tool?
Also when I take 25 will I have to reinstall twrp?
Sent from Tapatalk using my xposed VZW G2
mjones73 said:
If you have rooted 24A with a stock recovery, you can take the OTA and retain root..
Click to expand...
Click to collapse
Did you do this personally? I have stock rooted 24A now. I am using xposed and other root apps. Will the OTA effect any of that?
ijustintouch said:
Did you do this personally? I have stock rooted 24A now. I am using xposed and other root apps. Will the OTA effect any of that?
Click to expand...
Click to collapse
Just repeating what someone said in the other update thread...
http://forum.xda-developers.com/verizon-g2/general/25b-coming-t2874367
I used LGD950AT-01-V20b-310-410-MAR-22-2014+0.tot and LGUP_8974.dll with LG flash tool to get to D95020B. I couldn't find the newest firmware. So I have 2 Lg D950's. One with the D95020B and the newer one with D95020F. I used stump-1.2.0.apk to brute force the root then installed Freedom Flex. Used TWRP From Freedom Flex. Rebooted phone with newest firmware and did a full system backup. I then took older model that would not allow me to do OTA updates and did the same process. I then placed all files on to pc and switched between the two phones. Rebooted with Freedom Flex and did a full system restore. Now I'm up to date and both phones still have root and SU. Not sure how to upload my back up files from the newest version for anyone or not sure if anyone wants it. Please let me know.
I have the rooted D95010C. Would this jump me up from 4.2.2 to 4.4.2?
mja2027 said:
I used LGD950AT-01-V20b-310-410-MAR-22-2014+0.tot and LGUP_8974.dll with LG flash tool to get to D95020B. I couldn't find the newest firmware. So I have 2 Lg D950's. One with the D95020B and the newer one with D95020F. I used stump-1.2.0.apk to brute force the root then installed Freedom Flex. Used TWRP From Freedom Flex. Rebooted phone with newest firmware and did a full system backup. I then took older model that would not allow me to do OTA updates and did the same process. I then placed all files on to pc and switched between the two phones. Rebooted with Freedom Flex and did a full system restore. Now I'm up to date and both phones still have root and SU. Not sure how to upload my back up files from the newest version for anyone or not sure if anyone wants it. Please let me know.
Click to expand...
Click to collapse
Hello do you still have d95020f backup?
Anyone know if we'll be able to keep root one the lollipop ota comes out on the 10th? If not will a prerooted IMG become available? I do like lollipop but I like having WiFi tether and v4a is awesome. Anyone have an idea what will happen taking the ota while rooted.
Sent from my Nexus 7 using XDA Free mobile app
graymonkey44 said:
Anyone know if we'll be able to keep root one the lollipop ota comes out on the 10th? If not will a prerooted IMG become available? I do like lollipop but I like having WiFi tether and v4a is awesome. Anyone have an idea what will happen taking the ota while rooted.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
If you take the OTA, it will replace your rooted image with one that does not have root, and you will lose it. It will also update your bootloader and likely patch whatever exploit that mofo uses, rendering it useless. You will be stuck with a rootless, locked down lollipop for the foreseeable future. Should you decide not to take the OTA, there is a chance that you will be able to flash a rooted lollipop image and get the best of both worlds. Easy choice in my opinion. Computerfreak (the guy who makes the awesome modded images in the development forum) has said that he will support a rooted lollipop image assuming that it is compatible with mofo.
graymonkey44 said:
Anyone know if we'll be able to keep root one the lollipop ota comes out on the 10th? If not will a prerooted IMG become available? I do like lollipop but I like having WiFi tether and v4a is awesome. Anyone have an idea what will happen taking the ota while rooted.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
You won't be able to get update with a modded device, it'll show up but not flash.
Sent from my XT1254 using XDA Free mobile app
With kingeoot you will be able to get root but of course it will be temporary
meanmug said:
You won't be able to get update with a modded device, it'll show up but not flash.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
I've read reports that you can use moforoot to flash an unmodified image and set the firmware status back to unmodified. That may allow you to take the OTA. Or it may not. Even if it doesn't, you should still be able to update it via PC and Motorola's update software. But again, why would you want to?
does this image have the kernel included. i thought that was the big difference between kitkat and lollipop is the kernel change. if we cannot overwrite the kernel than what kinds of lollipop image would we be getting? i may be completely misunderstanding this
johnbravado said:
does this image have the kernel included. i thought that was the big difference between kitkat and lollipop is the kernel change. if we cannot overwrite the kernel than what kinds of lollipop image would we be getting? i may be completely misunderstanding this
Click to expand...
Click to collapse
What image are you referring to? If you're talking about the hypothetical image that I mentioned, I was talking about the stock KitKat image. Once you flash a stock, unrooted KitKat image using mofo, it removes the system modified status, which theoretically means you can then OTA to lollipop. But, as I mentioned before, there's a 99.9999% chance that this OTA will update the bootloader and patch the mofo exploit, which means you would lose mofo functionality permanently.
If you're referring to a hypothetical rooted lollipop image that we could flash with mofo, I'm fairly sure that the kernel resides in the system partition, which is the partition that mofo flashes, therefore we shouldn't have any issues flashing a new kernel.
Disclaimer: I'm not a developer. My education is limited to tinkering and Google University.
Until the update is available, nobody knows anything for sure. This is all just speculation, as nobody has the update yet!
Most likely you won't be able to take the update without first reverting to the stock image. I did that when I got a screen replacement
Whether MOFO will work after the update, nobody knows. Someone will have to be the guinea pig.
Personally I would not attempt to install any OTA update unless you don't mind that you will likely lose root and may not be able to get it back.
Once the update is available, and someone is able to dump an image of it and modify it to be rooted, then we will be able to see if MOFO can still be used to flash it to the phone.
PittAussie said:
Until the update is available, nobody knows anything for sure. This is all just speculation, as nobody has the update yet!
Most likely you won't be able to take the update without first reverting to the stock image. I did that when I got a screen replacement
Whether MOFO will work after the update, nobody knows. Someone will have to be the guinea pig.
Personally I would not attempt to install any OTA update unless you don't mind that you will likely lose root and may not be able to get it back.
Once the update is available, and someone is able to dump an image of it and modify it to be rooted, then we will be able to see if MOFO can still be used to flash it to the phone.
Click to expand...
Click to collapse
mofo WILL NOT work once the lollipop update is applied, and you will not be able to downgrade. The only chance is if you are able to update just the kernel(boot)(using fastboot) and system image(using mofo) from the stock image, and not the bootloader
so, this may be perposterously dumb, but how possible would flashing a boot.img be using Flashify? It made a stock backup just fine. Maybe it is a dumb question bc i dont think it would stick on reboot, but thought id ask.
edit: okay...somewhere along the way flashify stopped working. i do still have my backup, though.
edit 2: a titanium backup restore revealed version 1.8.4 is what i used that worked.
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.
I currently have an LG-D415 running KitKat 4.4.2 that's rooted. I've never had a need to upgrade to Lollipop 5.0 until now. I just bought a new truck that has Android Auto which requires 5.0. My phone has been giving me a message that there's a system update available for quite a while now but I have been reluctant to do it because my phone is rooted and I'm not sure what would happen. Should I just let it do the update or do I need to unroot the phone first. It's been so long I'm not even sure what method I used to root the phone.
If you have rooted phone i recomend you installing latest twrp recovery and flashing lollipop ROM for lg l90d415. the stock ROM van ne found on t
his site
OTA update will fail if device is rooted. If you want to keep root enabled, then follow lgl90 suggestion. If you remove root to update it may work but you will have to root again. A backup is always a good move.
I'm kind of a novice at this so I'm looking for the most painless method of getting Lollipop. I'm not sure I'm comfortable installing twrp and flashing the rom. Also, I've read the bootloader needs to be unlocked which it isn't. Can I use SuperSu to unroot, let the OTA update do its thing and then reroot?
the bootloader is unlocke by deafult on lg l90d415 all you habe to do is download flashify app from play store download the latest twrp for d415 and wipe system,dalvikcache and cache the flash te lollipop stock tom by going to install and chouse the rom file where you have downloaded it inernal or external sd card and the swipe to flash the firsr boot will take maximaly 5-10 minuts .. lollipop is waaay diferent than the kitkat thats why will take to boot longer
So I unrooted the phone downloaded the OTA update and tried installing it. It made it halfway through then the phone restarted without completing the update. The phone is still at 4.4.2 and I no longer get any message to update. When I check for updates it thinks its up to date. When I tried manually updating using the LG Mobile Support Tool it initially said an update was available then changed to the phone is up to date. Why does it think the phone is up to date when obviously it's not?
zippster1 said:
So I unrooted the phone downloaded the OTA update and tried installing it. It made it halfway through then the phone restarted without completing the update. The phone is still at 4.4.2 and I no longer get any message to update. When I check for updates it thinks its up to date. When I tried manually updating using the LG Mobile Support Tool it initially said an update was available then changed to the phone is up to date. Why does it think the phone is up to date when obviously it's not?
Click to expand...
Click to collapse
HI i told you what is the best solution to update your phone.. you could successfuly hard brick your phone(why did it not update well you didnt had enough of battery life) do what i told you so the best solution is to download the official lollipop rom for lg l90 d415 its same stock rom from lg but it comes pre rooted and all of that good stuff
lgl90 said:
HI i told you what is the best solution to update your phone.. you could successfuly hard brick your phone(why did it not update well you didnt had enough of battery life) do what i told you so the best solution is to download the official lollipop rom for lg l90 d415 its same stock rom from lg but it comes pre rooted and all of that good stuff
Click to expand...
Click to collapse
zagreb - as I stated I'm a novice so I chose the path that I thought would be the easiest. My phone was fully charged so I do not believe that was the reason for the update not completing. Is there a thread or link you know of that provides a step by step (from beginning to end) tutorial of what you're proposing. Thanks for your help.