Just got the OTA update for nougat, every time I go to install it my phone crashes and switches off.
Anyone else having this problem?
Also, how to I flash stock recovery, I think it's to do with that STUPID twrp recovery that doesn't even work.
Megacamz said:
Just got the OTA update for nougat, every time I go to install it my phone crashes and switches off.
Anyone else having this problem?
Also, how to I flash stock recovery, I think it's to do with that STUPID twrp recovery that doesn't even work.
Click to expand...
Click to collapse
You need to flash back stock recovery. You can NOT update OTA updates when you have TWRP, it will crash, just what happened to you.
Use SPFT and flash back stock recovery for the current rom you are on. You can extract it from the scatter file. (If you don't know what that is, GOOGLE IT!!!!!!!!!!!!!!!!!!!!!!)
Btw I would avoid the update for now. It's buggy to say the least and you will loose fast charging.
Yea this OTA still needs improvement. Fast charging gone, fingerprint STILL not working, battery drain. Practically, latest Marshmallow is better then this OTA.I regret upgrading. If you gonna need downgrade use SPFT, their is a simple guide in umi community.
I did install iit and now I can not phone out or receive a call on Bluetooth phone Buzzzes loudly and the net work closes out, I use the bluetooth because of my hearing aids as the volume of the UMI super isn't very loud. I don't know how to fix this short of resetting back to origional except that way I loose all my info and have to start again. waiting for an answer.
Related
What's currently happening is my phone will boot and work normally except it appears the radio is not working then after 60-120 seconds freeze for a second then reboot. Wifi does work but I just see an x for the cell network signal and if I take out the SIM I get no notification. Curiously if I'm using the camera it seems to delay the rebooting by a few minutes.
I've tried http://forum.xda-developers.com/showthread.php?t=2432476 LG G2 Stock Firmware (Go Back to Stock) to no success, I was able to flash, it removed TWRP but I get the same symptoms anyway.
I've tried flashing the Rogers modem and this did not make a difference.
When I noticed this problem was when I was installing/testing some xposed modules, although it seems strange that they could break the phone in this way.
I've run out of ideas and although my phone isn't bricked per say it's near useless if it's going to reboot every minute or two. The phone doesn't reboot if I leave it in download mode or TWRP so this makes me think there's some hope.
Assuming it's not against the rules I'll PayPal anyone who comes up with the fix $50 CAD because right now I'm hooped.
Did you download and try flashing the exposed disabler zip file?
Sent from my LG-D803 using XDA Premium 4 mobile app
Of course there is hope!
All you gotta do is just download this ROM...
http://forum.xda-developers.com/showthread.php?t=2451592
Download it with your PC, then connect your phone to the PC to transfer the file.
The TWRP and flash it and that should fix it all.
Good luck
Do you have a gmail widget on your lockscreen? (Was worth a shot since others have reported varying issues with gmail widgets on the lockscreen).
I lost my recovery when I tried to go back to stock, and I can't seem to install any apps. I'm trying "upgrade recovery" from the LG Mobile Support Tool to see if that works. Otherwise I guess I have to find out how to root and flash a recovery entirely over ADB
I was able to restore the stock recovery and factory reset but that still didn't resolve the issue. Can someone provide a /system/ partition dump of a d803? I'm assuming there's something broken in there but I don't think flashing a ROM will solve that since flashing stock didn't seem to.
mrsocksfox said:
I was able to restore the stock recovery and factory reset but that still didn't resolve the issue. Can someone provide a /system/ partition dump of a d803? I'm assuming there's something broken in there but I don't think flashing a ROM will solve that since flashing stock didn't seem to.
Click to expand...
Click to collapse
If flashing to stock didn't work then your phone may as well be defective...
crzykiller said:
If flashing to stock didn't work then your phone may as well be defective...
Click to expand...
Click to collapse
It's not a paperweight yet, I can adb. I rooted it through adb I'm just not sure what the xposed module broke. It has to be something that persists across flashing stock but I don't have anything to compare against.
EFS. Flash or push your backed up EFS.
Steamer86 said:
EFS. Flash or push your backed up EFS.
Click to expand...
Click to collapse
I don't have one. I made a backup in TWRP but ended up losing it when trying to fix things :silly:. I believe I can still see my IMEI if that's any sign of things not being completely ****ed.
Hi I have LG G2 D802 . My problem is that my phone hangs a lot . I did hard reset but problem didnt go. After hard reset i tried to install custom built rom but still same problem. Then I re installed lolipop 5.0.2 still the same problem .. now
i have downgraded to kitkat and again same problem .. Even now when it hangs It turn off completely like it got bricked or something but it work some time and again after some use it hang.. now i have hardreset my device and putted on standby mood but phone was working fine after some use phone hanged again . I dont understand what is the problem with my LG G2
I am having the exact same problem on stock 4.4.2 with my D803. I have random reboots every few minutes. I suspect it is a hardware issue since the problem persisted even after returning to stock using kdz. Unfortunately, I don't have an EFS backup.
I have tried multiple other ROMS (CM12.1, DU, Cloudy 3.2 and 3.3) and all are even less usable than stock (reboots while I am doing the initial setup).
Any suggestions? I don't know what else to try and am ready to buy a new phone now as this G2 is basically unusable... I'd greatly appreciate any help.
mrsocksfox said:
It's not a paperweight yet, I can adb. I rooted it through adb I'm just not sure what the xposed module broke. It has to be something that persists across flashing stock but I don't have anything to compare against.
Click to expand...
Click to collapse
If you have restored it to stock ....... and you still have the problem, u may have a short somewhere in the phone. The only thing that remains the same is the hardware .... u have changed the software
Hello. I had gotten this Note 4 phone which had a custom recovery installed on it but the rom seemed to be official, on 5.1
The first thing I did was go to samfirmware and flash a 6.0.1 rom, it went fine, phone was working properly. Then I got greedy and wanted to test a Note 7 ported rom. Flashed TWRP recovery and from within I flashed RamROM http://forum.xda-developers.com/note-4/snapdragon-dev/rom-sm-n910g-ramrom-t3400349 , I downloaded the one from post#2 , the N910F one that my phone is and after it flashed to ROM it simply stopped working. My phone no longer booted, was booting me directly into Download mode with emmc read error. I kept trying to flash the stock rom which I previously flashed and it would fail.
Afterwords I used Smart Switch to reinitialize the phone, writing my phones S/N and that failed as well but at least that made my phone boot into a different recovery where it said to connect to Kies. Once again I used Smart Switch and this time it was successful 100%. My phone even booted into the OS and was working, however, while using it, after 10 minutes the phone restarted into Download mode with emmc read error.
So all in all the phone is functional but it starts to lag and restart. Now I'm kinda stuck again since I've tried to flash the firmware I got from Samfirmware through Odin, it succeded but it just doesn't boot, it goes to Recovery, tries to apply an update and I get an error.
Is there anything I can do? I can't believe the emmc could've broken just from trying to flash that custom rom, especially that afterwards I was even able to boot into the phone.
Thanks for reading and I appreciate the help.
engwee said:
Hello. I had gotten this Note 4 phone which had a custom recovery installed on it but the rom seemed to be official, on 5.1
The first thing I did was go to samfirmware and flash a 6.0.1 rom, it went fine, phone was working properly. Then I got greedy and wanted to test a Note 7 ported rom. Flashed TWRP recovery and from within I flashed RamROM http://forum.xda-developers.com/note-4/snapdragon-dev/rom-sm-n910g-ramrom-t3400349 , I downloaded the one from post#2 , the N910F one that my phone is and after it flashed to ROM it simply stopped working. My phone no longer booted, was booting me directly into Download mode with emmc read error. I kept trying to flash the stock rom which I previously flashed and it would fail.
Afterwords I used Smart Switch to reinitialize the phone, writing my phones S/N and that failed as well but at least that made my phone boot into a different recovery where it said to connect to Kies. Once again I used Smart Switch and this time it was successful 100%. My phone even booted into the OS and was working, however, while using it, after 10 minutes the phone restarted into Download mode with emmc read error.
So all in all the phone is functional but it starts to lag and restart. Now I'm kinda stuck again since I've tried to flash the firmware I got from Samfirmware through Odin, it succeded but it just doesn't boot, it goes to Recovery, tries to apply an update and I get an error.
Is there anything I can do? I can't believe the emmc could've broken just from trying to flash that custom rom, especially that afterwards I was even able to boot into the phone.
Thanks for reading and I appreciate the help.
Click to expand...
Click to collapse
read this - http://forum.xda-developers.com/note-4/help/note-4-issues-t3453048
there are links to more threads related to your issue.
Short version though:
it is dying. install wake lock application, add it to start up and set settings to #4.
accept the fact that your phone will eat the battery faster and one day WILL die completely
Thanks for your response. Regarding the Wake lock application, I'm starting to look into it, I asume I'll have to be rooted. I'll try to recover it again using Smart Switch and then I can only hope I can install TWRP and still have it functional.
Previously when I was able to get it working with Smart Switch, entering the recovery messed everything up. It said it was applying an update and that got stuck.
engwee said:
Thanks for your response. Regarding the Wake lock application, I'm starting to look into it, I asume I'll have to be rooted. I'll try to recover it again using Smart Switch and then I can only hope I can install TWRP and still have it functional.
Previously when I was able to get it working with Smart Switch, entering the recovery messed everything up. It said it was applying an update and that got stuck.
Click to expand...
Click to collapse
no need to be rooted, just download, install and set it to autostart
I'll try it if I somehow manage to get the phone working again, Smart Switch just fails now midway through.
golden_m said:
no need to be rooted, just download, install and set it to autostart
Click to expand...
Click to collapse
Is this the app you're talking about? https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en
What exactly does it do?
I managed to restore it eventually with Smart Switch, it took quite a few tries, then I switched to my Macbook when I saw the app was available on it too and the 3rd try succeded. I only did it because I saw the 2nd try had the % much higher than the first.
engwee said:
Is this the app you're talking about? https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en
What exactly does it do?
I managed to restore it eventually with Smart Switch, it took quite a few tries, then I switched to my Macbook when I saw the app was available on it too and the 3rd try succeded. I only did it because I saw the 2nd try had the % much higher than the first.
Click to expand...
Click to collapse
yes, that is the app.
i've read it does not allow your phone to go to sleep mode.
drains the battery faster, but this is the only way to keep note 4 working without swapping its motherboard...
I have a question, my gf recently bought a note 4 and we may swap our phones and if we do, i'll flash CM and tinker with it because i find this phone very interesting, just a question, does this bug affect the N910C (exynos) model? Do i have something to worry about? Because the phone is warrianty protected and if it's the case, i don't want to break it. I hope someone will shed some light on this
I received an update push from Motorolla that installed Nougat. After that, my phone would crash every 3-10 minutes. I did all the troubleshooting I could find online. I contacted support and they wanted me to spend $150 to get it "refurbished." Of course, it sure seems like a software problem, so that wouldn't help me anyways...
I turned to custom. After rooting, installing SuperSU and TWRP, I couldn't get several versions of AICP or Lineage to ever boot (stuck on loading screens). I also tried all the advice from this thread.
I went back and installed the stock Rom using f2fs , and the phone would get to the "hello moto" part of the boot up, then crash and reboot. I tried again using EXT4, and it worked, but just like before I ever begun, my phone was crashing every 3-10 minutes. However, the first crash wasn't until after I made a phone call, and my phone had been crash free for about 20 minutes before that call.
I'm a I.T. guy, but I'm not a "phone" guy. But it seems to me that there must be some other software that was modified during the update that is causing the problems that isn't part of ROMs. Something in the Kernal, or a driver folder or something?
Also, is there a way to get crash reports? So maybe if I at least go back to the default ROM and wait for it to crash, I have some info to work with?
Any help is greatly appreciated, thanks!
Flash full stock 6.0x for your model/region.
Important:
Without bootloader, gpt. Don't try locking BL.
Links you can find in my signature.
Try normal boot and after success any custom.
You cannot allow any ota update after it.
Some customs are only for Nougat modem/radio - don't flash it. @Kaivian
Ok, I got most of that, except I don't know what gpt refers to and am not getting any hits on search.
My signature - flashing stock - without bootloader & gpt.
So, I installed a 6.0 stock ROM and got tons of errors. I tried a 2nd time, still got tons of errors. Needless to say, stock 6.0 didn't boot. I decided, "The heck with it" and tried installing Lineage 7.1 again... and it worked! It finally booted up entirely. However, now I get a "Sim card missing" notification. Can I just reinstall part of something... like the modem? so I can keep this "working" lineage boot? Or am I starting over yet again?
Repeat
from
fastboot flash modem ...
to
...fsg.
dzidexx said:
Repeat
from
fastboot flash modem ...
to
...fsg.
Click to expand...
Click to collapse
This caused it to not boot.
I went back to 6.0 and turned off auto-updates. I'll try again sometime when I have time. I did like the custom rom a lot, just couldn't use it as a phone xD
Same thing as the OP of this thread: https://forum.xda-developers.com/moto-g4-plus/help/bootloop-to-twrp-ota-update-t3667456
Late last night I saw that there was an update available and, given that I've only rooted my phone, security updates are important, and it's a mere ~15 minutes download + install time tops I went for it.
I absolutely cannot seem to get the update to install via the OTA channel - it downloads just fine but when I attempt to install it it boots into TWRP and once there the only way to leave is via Bootloader > Start (System just reboots into TWRP) and upon reaching Android I'm told that the update was unsuccessful.
I now have two problems:
1. I don't like having notifications that I can't do anything about. Assuming that this OTA is going to nag me for eternity that's definitely going to become an annoyance - but I'd prefer the update vs blocking the notification (again, IF it nags)
2. Every time I restart my phone (or it crashes) I now have to deal with TWRP. It's not a major annoyance. It's at most 8 extra seconds added to my boot time and I don't restart my phone more than 3 times a week. But it IS butt-ache inducing.
Edit: Forgot to add that I came across this and downloaded it https://forum.xda-developers.com/moto-e4/how-to/boost-mobile-ota-t3763851 My E4 is a 1766 and is also from Boost Mobile (Sprint) so I imagine they're the same update. Point is, can I install this with TWRP successfully or would that do nothing / make things worse?
travistyse said:
Same thing as the OP of this thread: https://forum.xda-developers.com/moto-g4-plus/help/bootloop-to-twrp-ota-update-t3667456
Late last night I saw that there was an update available and, given that I've only rooted my phone, security updates are important, and it's a mere ~15 minutes download + install time tops I went for it.
I absolutely cannot seem to get the update to install via the OTA channel - it downloads just fine but when I attempt to install it it boots into TWRP and once there the only way to leave is via Bootloader > Start (System just reboots into TWRP) and upon reaching Android I'm told that the update was unsuccessful.
I now have two problems:
1. I don't like having notifications that I can't do anything about. Assuming that this OTA is going to nag me for eternity that's definitely going to become an annoyance - but I'd prefer the update vs blocking the notification (again, IF it nags)
2. Every time I restart my phone (or it crashes) I now have to deal with TWRP. It's not a major annoyance. It's at most 8 extra seconds added to my boot time and I don't restart my phone more than 3 times a week. But it IS butt-ache inducing.
Edit: Forgot to add that I came across this and downloaded it https://forum.xda-developers.com/moto-e4/how-to/boost-mobile-ota-t3763851 My E4 is a 1766 and is also from Boost Mobile (Sprint) so I imagine they're the same update. Point is, can I install this with TWRP successfully or would that do nothing / make things worse?
Click to expand...
Click to collapse
You cannot install it with twrp on a rooted device. You would have to modify the updater script in it for that. And remove a bunch of assert props. And hope your system isn't modified too much.
So no, you can't. You have to flash back to stock, (the version you're on now) then install it. Or just sit tight, there is someone working on a partition updater, and a twrp flashable rom with the update included.
Once you root and install twrp, ota updates ain't gonna happen. How do you not know this
If you need a solution for the recovery Loop issue you're going to have to give me a minute to find the link it can be fixed.
It's a problem if TWRP when you format data not wiping something properly
this should help a recovery loop. Only if your issue is, every reboot it goes right to twrp. Then you have to reboot bootloader and select start. Easy fix.
madbat99 said:
You cannot install it with twrp on a rooted device. You would have to modify the updater script in it for that. And remove a bunch of assert props. And hope your system isn't modified too much.
So no, you can't. You have to flash back to stock, (the version you're on now) then install it. Or just sit tight, there is someone working on a partition updater, and a twrp flashable rom with the update included.
Once you root and install twrp, ota updates ain't gonna happen. How do you not know this
If you need a solution for the recovery Loop issue you're going to have to give me a minute to find the link it can be fixed.
It's a problem if TWRP when you format data not wiping something properly
this should help a recovery loop. Only if your issue is, every reboot it goes right to twrp. Then you have to reboot bootloader and select start. Easy fix.
Click to expand...
Click to collapse
Thank you! And, frankly, because I never stick to stock. I always flash Cyanogenmod or LineageOS pretty much first thing when I get a phone. This time there wasn't a build available that seemed stable enough (Late November) but I still needed Root. I'm used to getting updates from both LOS and CM OTA so I figured the only thing preventing official OTA updates from working was that the build was entirely different. My assumption in this case was that I was still running the stock ROM that came with the device AND they were offering an OTA via notification so the phone must be eligible to receive it. >-> My bad.
travistyse said:
Thank you! And, frankly, because I never stick to stock. I always flash Cyanogenmod or LineageOS pretty much first thing when I get a phone. This time there wasn't a build available that seemed stable enough (Late November) but I still needed Root. I'm used to getting updates from both LOS and CM OTA so I figured the only thing preventing official OTA updates from working was that the build was entirely different. My assumption in this case was that I was still running the stock ROM that came with the device AND they were offering an OTA via notification so the phone must be eligible to receive it. >-> My bad.
Click to expand...
Click to collapse
The ota has a bunch of checks in it. If anything fails the checks, ota fails. When you root, there are system changes, boot.img changes, etc. All of which cause the ota to fail. Of course lineage and cm didn't have such strict checks in their update zips because they expect us to root and modify system. Manufacturers do not.
Hello,
I want to know if it is possible to root the stock rom, and keep OTA.
Actually, my objective is to use screen mirroring (miracast), and I heard rooted devices can achieve that by changing build.prop. I didn't want to switch from stock rom, since I like it and like updating OTA.
Maybe if I adb boot twrp and install supersu, but keep regular revovery, I can still get OTA?
If there's another solution to screen mirroring, I'd be glad to know, too.
Thanks in advance!
I've tried to root stock rom and keep the system unmodified through Magisk. For whatever reason OTA always fails even though I have stock recovery, supposedly unmodified system, and rolling back to stock boot image prior to trying the OTA.
The only thing that works is to flash the stock firmware and then taking OTA. The only problem is that the stock firmware is tough to come by, but I read that someone got their hands on the latest 93-10 firmware image. So that's good.
I've since moved onto Pixel Experience 8.1 rom without any regrets. The camera works really well and battery is nearly up to par with stock Nougat.
No, unfortunately these things still modify the the system and boot partition and the upgrade script knows it and causes the update to fail. We don't know exactly everything the OTA update scripts check (it's not just a simple text file) but it is obviously something that it knows you are rooted even when nothing else does. :/
You must be completely stock to take an OTA update... the only exception is your bootloader lock state doesn't matter at this time, we do know that it is capable of detecting that as well.
I have done that and I got Bootloop! So don't Try!
else
https://forum.xda-developers.com/g5-plus/how-to/guide-complex-ota-update-magisk-rooted-t3688175