I made a few stupid mistakes with my phone, and now I can't get root back. I was editing the mixer_paths.xml file to try and boost the audio output on the headphone jack, because frankly, the LG G Flex is incredibly quiet for whatever reason. I made a couple of changes to the file and then rebooted. The phone wouldn't reboot. I freaked out for awhile, but then realized I could still get into TWRP. I did, and I flashed dfuses stock rooted ROM. Cool, everything was working fine. The only thing wrong now was that the rom was an older firmware version, and I wanted to be on the newest. So I stupidly took the OTA updates. I know. Big mistake. After that I was going to make a backup in recovery, so I tried to reboot to recovery. Instead of rebooting to recovery, it factory reset my phone. Now stumproot says that my phone is already rooted, and it won't do anything, and SuperSu says that I don't have a su binary installed. Does anyone have any ideas on how I could possibly get root back? Thanks for your time.
I got it working. I was able to downgrade to jelly bean, and then re root the device. How do I now safely get back to kit kat though?
Related
I decided to try out rooting my device using superoneclick on Friday, then I also manually installed the latest OTA update yesterday. And now my device is not happy. Before all this, the thing was solid, has never once crashed or rebooted on me. In the last 24 hours, I've had to remove the battery about 10 times so far, as it has locked up completely. Seems something is off with GPS, as using geo-location related functions from within apps seems to cause this. The bootloader is still locked, and I haven't installed any recovery images or anything like that, just rooted and updated using the update.zip method, but something has not gone well.
So, my question is, how can I restore everything back to how it was? I want stock, 100% unfucked-with everything back in the device. Factory wipe hasn't helped, and hasn't removed root (which surprised me, but seems obvious now I think about it). I have a copy of the Nexus One FRG83 system image (73.9mb) from HTC, but don't know how to install it. Once I install this, I will update using the ota updates, and try root again.
What do I do?
Read my signature.
Rename the the system image to PASSIMG.zip. Boot into the bootloader and it should detect it automatically. Update, restart, done.
Thanks guys/
Hello,
I am using a rooted (stock) G2. I upgraded (via unrooting then re-rooting) to 4.4.2 a while back when it came out. Then, all of a sudden, yesterday, my phone started downloading MUC 6.4.1.5_E02 (which I thought was old by now). Now, it keeps asking me to install it -- which I cannot because, of course, I am rooted. How do I either: (a) just get rid of/disable this update from installing, or (b) should I install it, which would, again, require un-rooting then re-rooting. Is MUC 6.4.1.5_E02 important/cool/necessary? What is it exactly?
My phone is currently using:
Baseband:
VS98024A-M8974A-AAAANAZM-2.0.20046
Kernel:
3.4.0-perf-gdf89a11
[email protected]
Build:
KOT49l.VS98024A
Software ver:
VS98024A
No custom recovery.
Thank you!
daniel178 said:
Hello,
I am using a rooted (stock) G2. I upgraded (via unrooting then re-rooting) to 4.4.2 a while back when it came out. Then, all of a sudden, yesterday, my phone started downloading MUC 6.4.1.5_E02 (which I thought was old by now). Now, it keeps asking me to install it -- which I cannot because, of course, I am rooted. How do I either: (a) just get rid of/disable this update from installing, or (b) should I install it, which would, again, require un-rooting then re-rooting. Is MUC 6.4.1.5_E02 important/cool/necessary? What is it exactly?
My phone is currently using:
Baseband:
VS98024A-M8974A-AAAANAZM-2.0.20046
Kernel:
3.4.0-perf-gdf89a11
[email protected]
Build:
KOT49l.VS98024A
Software ver:
VS98024A
No custom recovery.
Thank you!
Click to expand...
Click to collapse
http://forum.xda-developers.com/verizon-g2/general/how-stop-ota-pop-rooted-device-t2885667
Thanks!
What is the best way to temp un-root? I see an option in SuperSU, but it says "permanent unroot." I want to just temporarily unroot for updating purposes, then go right back. What's the best way to do this?
daniel178 said:
Thanks!
What is the best way to temp un-root? I see an option in SuperSU, but it says "permanent unroot." I want to just temporarily unroot for updating purposes, then go right back. What's the best way to do this?
Click to expand...
Click to collapse
I did not unroot to update and retained root after the update... If you lose root, I heard stump root will root 26a.
Sent from my Xposed G2
my understanding is that if you're rooted with stock recovery then u can take 26a without unrooting, but if you have a custom recovery then you need to flash the updated rom manually or restore stock recovery before taking the ota.
I'm still on 24a tho with no experience with 26a
Sent from Tapatalk using my xposed VZW G2
somnambulator said:
my understanding is that if you're rooted with stock recovery then u can take 26a without unrooting, but if you have a custom recovery then you need to flash the updated rom manually or restore stock recovery before taking the ota.
I'm still on 24a tho with no experience with 26a
Sent from Tapatalk using my xposed VZW G2
Click to expand...
Click to collapse
That is correct.
Help! Accidentally clicked on the update button that popped up and have root
I do have my phone rooted, but as stated above, the update software pop up box kept popping up and I accidentally clicked on the update button. My phone went into the twrp backup screen where I was told the only thing I could do was revert back to a previously saved backup. I tried this and now I can't even get my phone to turn on. If I hold the power and volume down buttons at the same time I just get vibration from the phone but the screen doesn't turn on. When I plug the phone in, it displays the LG start up display and nothing else, it will stay on that display even when I unplug then... So the big question, can I save my phone? I had a buddy do the roots am unaware of how to save it. Thanks for the replies in advance.
Forgive me if this has been asked before. I did search, but I couldn't seem to find an answer to this.
I have a dev edition model. I really want to root, but have been holding off because there are bugs with the current build of Lollipop and I'm kind of hoping Moto will release a 5.02 update soon to kill the memory leak and other issues. That being said, I have really been itching for root.
If I did root, what would I have to do to this phone to update it to the new version? Would I have to completely return to stock and wipe? Or could I ADB sideload? Seems like I was reading that you can't update at all when you're rooted, even if you disable root.
Without any idea how much longer it'll be before the next update, I'm finding it harder and harder to hold off on root, but I don't want to go through hell to get it back to stock and update it.
Thanks for any help and sorry if this has already been asked.
From what I understand, root is fine. It is installing a custom recovery that will stop you from getting the OTA. You can very easily undo root. As a matter if fact, you can pretty easily reinstall the stock recovery also.
diggitydogg said:
From what I understand, root is fine. It is installing a custom recovery that will stop you from getting the OTA. You can very easily undo root. As a matter if fact, you can pretty easily reinstall the stock recovery also.
Click to expand...
Click to collapse
Thanks for the reply.
Most of the time, that's true. I have updated a lot of phones by simply unrooting, applying the update, and rooting again, or using ADB sideload and then just rooting. But from what I have been reading about the Moto X 2014, you have to completely restore it back to stock before doing anything, even if you just use the temp boot method to root.
Is that wrong? I can't seem to find any info that confirms either way.
I've installed custom recovery, how can I reverse it and install the original recovery for update?
One advantage of root is you'll have Titanium Backup, so even if you do have to do a full wipe before applying the update, you could just update it and restore everything back quickly using TiBu. With lollipop, apparently the update file checks for the entire system checksum as a whole instead of each file so any slight modification to the system will mostly require pure stock and this is the same even with the nexus. So yeah, you most likely have to wipe your device before updating. I'd say, wait till Xposed for Lollipop is out, its almost there, once it comes out go ahead and root it, it'll at least be worth the hassle then
If you're rooted with lollipop and want to take an OTA update you can flash stock recovery and the stock system image. At that point you should still have all apps/data and be able to take a OTA update. The recovery and system files should be the exact version you already have and of course anytime you flash realize you could lose data!
Steve-x said:
If you're rooted with lollipop and want to take an OTA update you can flash stock recovery and the stock system image. At that point you should still have all apps/data and be able to take a OTA update. The recovery and system files should be the exact version you already have and of course anytime you flash realize you could lose data!
Click to expand...
Click to collapse
Right. All you need to do is flash the stock /system partition and also the recovery if you replaced it. I don't know why everyone's talking about having to wipe the entire phone with the all the stock images.
Just got a update for my LG G Flex D950 from AT&T. I didn't think twice, and hit update. Now my phone will only go to TWRP. I'm using TWRP v2.8.6.0 any suggestions? All I've done is root it, it has the original ROM it came with.
mine is also soft bricked
I was not rooted and the update installed fine. Just curious what it was....
Edit:
Oh wait this explains everything
(Not really, not at all actually)
http://www.att.com/esupport/softwareUpdateArticle.jsp?sid=KB423840&cv=820
Update summary**
Effective September 17, 2015, AT&T released a software update for the LG G Flex (D950). This update will be available via Firmware Over The Air (FOTA)*using a Wi-Fi connection.****
*
What's changing?
Device security improvements
What to expect after the update**
Although there should be no impacts to settings or data, we recommend that you back up your important files and media prior to upgrading the software.
bryanizmir said:
I was not rooted and the update installed fine. Just curious what it was....
Click to expand...
Click to collapse
My mom, uncle, and I all have the same phone, the only difference is mine is rooted with TWRP, so something with it being rooted, or with TWRP has screwed it up, and I have no idea which it is
try the steps here. scroll down to the terminal commands and that will get you going.
http://www.androidayos.com/2014/10/0...download-mode/
(How to Fix bricked LG G2 stuck in Recovery after taking OTA update
If you have LG G2 rooted and installed with TWRP recovery then suddenly and automatic OTA update came around but then its too late that your phone just stuck in TWRP Recovery. If you bricked your phone after doing an OTA Update with root and TWRP installed and happens that it stuck at recovery. This can be fixed either by installing the official firmware via flashtool using the KDZ file but sometimes your phone can’t boot into Download mode and it won’t connect to the computer, so this could be a very frustrating situation.
Before doing anything else you may first try this, this has been reportedly worked on some LG G2 users at Androidcentral forum and thanks to the folks at XDA-developers for this workaround.
On your TWRP terminal command type this codes.
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Then hit enter and reboot.)
I have the same problem. Rooted/TWRM and soft brick.
I get to terminal window, but no keyboard
tap on select when in terminal
---------- Post added at 05:10 PM ---------- Previous post was at 05:05 PM ----------
That should open the keyboard
I don't have select, I have home, back and the icon that put me in the terminal window from the folders
Do you see this?
Full phone
Sonny beach, trying it now
Got it, now how do I get that software update to go away?
Your phone should keep the update... at least mine did
Mine didn't, in fact it just bricked again, because I accidentally hit the update again
Hi Guys, I have the same problem although I have CWM instead of TWRP. I got the D950 ATT version rooted on stock 4.4.2 and the updated came up on my phone yesterday but I kept on clicking remind me later. Until last night I noticed my phone was booted on CWM and when I tried to reboot, it just went back again to recovery. Also tried restoring from my backup, goes normally and completes but after reboot it just goes back to CWM again. I hope there is someone who can help coz I have pictures and files I need from it...
Those same commands should work. Those are Linux commands for the base system
Texas_Dave said:
Those same commands should work. Those are Linux commands for the base system
Click to expand...
Click to collapse
I guess you are right, although I did it via fastboot it still worked and got all my files back. Thanks for the quick reply. And by the way the update notification is still active, do you think I still have to unroot before installing the update or would it be ok not to unroot and just defrost all the bloatwares that came with the stock OS then accept the update? I am just afraid that it might brick my phone if I went through with it...
I'm still soft bricking twice a day, because they force the update when I'm not looking. If someone has a way to unroot or better get rid of that fota crap, I sure would like to know how
Texas_Dave said:
I'm still soft bricking twice a day, because they force the update when I'm not looking. If someone has a way to unroot or better get rid of that fota crap, I sure would like to know how
Click to expand...
Click to collapse
I just wish IOroot had a way to support the G flex on android 4.4.2 so we do not have to go back to JB just to root. At least from KK we only have to do this new software update, then root the device, install recovery and we are good to go. I guess that would be too much to ask right now on a low activity device like ours. For now all I did to stop the update nag, I froze the software update file from Titanium backup rebooted and now the nag is silenced for a while until we get news that it's ok to do the update on our rooted devices running KK.
OK I got the notification to update today it's MMB29S, I am on K. I am rooted but stock, unlocked using systemless root for root. I've always been rooted and expected it to fail and have to install manually but this time because I'm not rooted like the old way. So i downloaded and went to install to my surprise dead Android with the triangle didn't show but it went to custom recovery screen twrp. I just hit restart because I've never not had a fail and never seen it do this before. Well when it restarted I was not updated and still on K. I also for the life of me can't get it to redo the ota. Tried to clear system service in apps and recheck but nothing.
So my question is since I'm new to systemless root what should I have done when it went to custom recovery? So that way if I can get it to pop up again I can be updated. Thank you in advance for any help and it would be awesome if possible to update this way without having to manually do it.
My best guess, based on what Chainfire replied to me when I asked about OTA, is that because you're somehow rooted the OTA will refuse to install. He said that using the "unroot" function in v2.63 (and I suppose in subsequent versions) he was able to apply the OTA and then just had to re-root.
As to the OTA, I read in the long-distant past that once it's been provided to your device you sort of go to the back of the queue, and even pressing the "check for system update" button has no effect. One day your turn will come again. When it happens, before you press the "install now" button, use the unroot function, reboot, and give it another go.
And I would really appreciate it if you could report back on the success or failure, just so we all know - thanks...
And before I close... your alternative is just to download the full ROM from Google, unzip everything in sight (including the zip within the zip), copy system.img to a convenient folder, and use Fastboot to flash system. After that you'll need to re-root (simple flash) and when you reboot everything will be as it was, apart from the version and security update date. I did it myself to MMB29S a week or so ago.
But my lawyer advises me to advise you to take a full backup first and store it off your device before you do anything to your device - just in case, you know?
I will definitely reply if I get the update again in a few days. If it doesn't I'll probably do it manually. I was just really surprised I hadn't gotten the error, just so used to it. Thank you for the info though.
Correct me if I'm wrong, but to install an OTA don't you need to be completely stock, including recovery?
If I'm not mistaken but since 4.3 (I'm probably wrong) if your rooted (before systemless root) when you try to the ota you will always get the dead Android because rooting changes the system files causing the update when it does is checks to think your system is corrupt.
Also it was really bad when people tried going from 5.x.x to 6.x even doing it manually some of us got bootlooped or when starting the phone up after updating manually saying system is corrupt but still starting up fine. Leaving like me having to completely clear out everything and installing the factory image just to not be corrupt and able to use Android pay.
Systemless root though I've not had a single problem and still able to use AP. And is also the first time in years I've gotten as far as I did with the OTA.
Rbh50815 said:
OK I got the notification to update today it's MMB29S, I am on K. I am rooted but stock, unlocked using systemless root for root. I've always been rooted and expected it to fail and have to install manually but this time because I'm not rooted like the old way. So i downloaded and went to install to my surprise dead Android with the triangle didn't show but it went to custom recovery screen twrp. I just hit restart because I've never not had a fail and never seen it do this before. Well when it restarted I was not updated and still on K. I also for the life of me can't get it to redo the ota. Tried to clear system service in apps and recheck but nothing.
So my question is since I'm new to systemless root what should I have done when it went to custom recovery? So that way if I can get it to pop up again I can be updated. Thank you in advance for any help and it would be awesome if possible to update this way without having to manually do it.
Click to expand...
Click to collapse
These small ota's can be done with boot modifications because they don't include any boot.img changes and if they do then they just blanket overwrite what's already there. The only part that is checked is /system. However TWRP won't ever install an ota update for compatibility reasons. Even if you reflash the stock recovery then you'll fail the ota because when you installed TWRP it protected itself (by modifying /system) from being overwritten by the stock recovery which is what unmodded stock android will always do on boot by default. And there are 2 things the ota verification looks for when updating: 1. It looks for whether /system has been ever mounted as Read/Write. 2. It hash checks the /system, if it finds any mismatch it fails. As for the update not showing up again, the ota checker hides the update after a failure to stop from flooding the download server. If you want to extract the update zip you can look in /cache for the zip. But since you don't have an unmodded /system you might as well just download the newest factory image and manually flash the system.img
You can use Wug NRT, unroot with MMB29S provided in the NRT , then root.