im not sure if this is related to the Lineage installation but after installing it and restoring it back to stock OS my phone will randomly stop charging. further the other day battery % was stuck at 89% for like 15 minutes which i found strange, i immediately rebooted and it gave me a different number. cannot install samsung updates either, every time i tap the manual installation setting it says my OS was modified in a non-authorized manner
phone is a Samsung J3 2016 (J320-FN). thanks
idklol123 said:
im not sure if this is related to the Lineage installation but after installing it and restoring it back to stock OS my phone will randomly stop charging. further the other day battery % was stuck at 89% for like 15 minutes which i found strange, i immediately rebooted and it gave me a different number. cannot install samsung updates either, every time i tap the manual installation setting it says my OS was modified in a non-authorized manner
phone is a Samsung J3 2016 (J320-FN). thanks
Click to expand...
Click to collapse
You can't apply stock updates on devices that are rooted or have TWRP installed. It requires stock recovery and an unmodified system partition. If you're rooted, remove root, if you have TWRP, you need to flash back to stock recovery.
Or
Do a Google search for:
"Return to stock (your model number)"
Then after restoring to full stock, you can then try applying the stock update, then reinstall TWRP after the update is finished(if you still want TWRP installed).
Sent from my LGL84VL using Tapatalk
Related
This is getting frustrating!
Once a full uk rom became available I did a full, clean install using Mobile Odin to retain root. When I check status immediately the report is 'official'. Now the problems begin. I have tried a restore from Titanium Backup, a manual install of all my apps one by one and also just letting Google Play do its stuff, and after each sometimes within a couple of hours, this last time I managed overnight, my status is reported as 'custom'.
Any ideas as to what is causing this please?
Which status you're talking from? The one in the settings? That happens sooner or later when the Note is rooted, the systems seems to check this from time to time and set the status to "Custom". But why bothering, it does not harm. Even OTA do work with that.
The status custom in Odin download mode is a different store (but it remains official as long as not recovery or other non-Samsung flash is done).
Yes, the one in settings. Once the status changes to custom if I tap 'software update' then do a check I get a message saying my device has been modified so updates unavailable.
Then you did anything else, my status there is also custom, but I was offered the latest OTA without problems. Nevertheless, I downloaded the latest update from sammobile and flashed it with Mobile Odin. So I don't care about that status.
You are rooted ??
If so run Triangle away to reset rom counter .
Flash stock rom via Odin then factory reset should put device to normal status .
Root can interfere with or prevent OTA use Kies and reroot .
jje
Why so complicate?
Get the update/rom from sammobile or here, use Mobile Odin and flash the update on the tablet. With the pro version, the tablet remains rooted and everything is fine. Mobile Odin is an excellent tool and worth the few bucks to get the pro version.
Odp: [Q] 'custom' status with official rom
I have the same problem. I tryied to install script sd2internalsd and Iinstall busybox and i think that orogram change my status to custom. Now - my note cant take an update.
I try use Triangal away but das not work. Any idea?
tapnięte z mojego Note'a 10.1 3G
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
tomisalunatic said:
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
Click to expand...
Click to collapse
Try putting twrp back on and flashing stock Lollipop Rom. http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 You can also try aosp, cm12.1 or any other lollipop ROM.
The Lollipop OTA is very picky, I believe any modifications to the stock firmware will cause the update to fail. You will need to have a completely stock system for the OTA to install successfully. Find the correct KitKat firmware for your phone and flash it then try upgrading.
Hi.
I'm having a similar problem with te OTA being picky (topic here).
Is there a stock firmware "file map" so that we can check manually what is wrong and erase/add needed files ?
Maybe this could be done by checking a flashable stock rom ?
Thanks a lot guys.
EDIT : Found a solution here http://forum.xda-developers.com/mot...osing-apps-t2979971/post57658072#post57658072.
Worked perfectly !
OP, I am in the same situation. I did the same as you, and got the same results. Have you managed to solve it? It would be nice if you tell what you decide to do and what's the outcome. Thanks!
tomisalunatic said:
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
Click to expand...
Click to collapse
Update to 5.1 success..... erm, well it's all relative
Eventually managed to update my XT1039 to 5.1 via ota.
Started with a fully charged phone and flashed 4.4.4 stock firmware (http://forum.xda-developers.com/moto-g/4g-development/xt1039-moto-g-4g-stock-firmware-kxb21-t2805619).
Once completed, powered up phone and signed into google play then updated the motorola update services app.
DO NOT install a custom recovery or root yet or the update will fail!
Start the update by going into settings/about phone/system updates.
After first boot into 5.1, do a factory reset.
To root once the upgrade is completed, download cf autoroot (http://forum.xda-developers.com/moto-g/4g-development/root-xt1039-cf-auto-root-peregrine-t2942406) and unzip to a folder on your pc. Open a command prompt and change directory to this folder. Powerup handset in bootloader mode (hold vol down while switching on), connect USB and run 'root-windows.bat' from the command prompt.
So far I'm hugely disappointed in the update as I use WiFi tethering alot and it appears to be a massive fail. I know it wasn't 100% in 4.4.4 or CM12 5.1 with both reqiuring an occasional reboot, but in 5.1, something's just not right and it's basically unusable (could it be updated radio or something?). Fortunately, USB tethering appears flawless.
Another obsrvation seems to be abscence of a + appearing in the HSPA signal indicator, I seem to be getting just the H appearing regardless.
Also no more bluetooth visibilty timeout setting.
After installing CWM 6.0.5.0, I got gliches with the display in recovery mode but it works.
Now after I have it rooted, ad free and de-bloated, fixed the power on logo and installed CWM 6.0.5.0, I'll stick with it for a while to just to see how the battery lasts.
In hindsight I should've stuck with CM12 5.1.
I am asking for help if anybody here can spare the time. I had my J700P Virgin Mobile rooted and xpose installed. I had notification that I had missed at least one update and wanted to go back to original firmware. I flashed back to original version of firmware no problem and the phone took the update. After the update I was unable to get wifi working again so I tried to reflash the original firmware. Phone flashed fine but when trying to reboot the phone is stuck in bootloop. I have reflashed the original firmware and the new updated firmware several times, tried to restore 3 TWRP backups, everything I can think of and all bootloop. I get the bootup screen - galaxy J7 then it goes to the samsung screen then to the Virgin Mobile screen then loops over and over. Every so many loops it goes to android starting up screen optimizing various numbers of apks, usually 1 of 1. I can do pretty much anything needed, use odin, access adb ect. Any other info needed please let me know. I am at the end of my knowledge on what to do-----HELP!!!!!!! Thanks.
kjslabber said:
I am asking for help if anybody here can spare the time. I had my J700P Virgin Mobile rooted and xpose installed. I had notification that I had missed at least one update and wanted to go back to original firmware. I flashed back to original version of firmware no problem and the phone took the update. After the update I was unable to get wifi working again so I tried to reflash the original firmware. Phone flashed fine but when trying to reboot the phone is stuck in bootloop. I have reflashed the original firmware and the new updated firmware several times, tried to restore 3 TWRP backups, everything I can think of and all bootloop. I get the bootup screen - galaxy J7 then it goes to the samsung screen then to the Virgin Mobile screen then loops over and over. Every so many loops it goes to android starting up screen optimizing various numbers of apks, usually 1 of 1. I can do pretty much anything needed, use odin, access adb ect. Any other info needed please let me know. I am at the end of my knowledge on what to do-----HELP!!!!!!! Thanks.
Click to expand...
Click to collapse
restoring a twrp backup breaks the phone. go here http://forum.xda-developers.com/galaxy-j7/development/twrp-3-0-2-0-beta-j700p-2016-fixed-t3485766 and follow the steps for fixing your efs. then you could flash stock rom again.
Bootloop fix
That did the trick!!!!!!!!!!!!!! You are the wizard of the day. Thanks from the bottom of my heart. I'm trying everyday to learn because I like to tinker with these expensive toys. You saved me a lot of scouring over endless piles of info.
I have hear a S7 wich hangs on white samsung boot logo.
The device is stock, no root and no custom rom.
The problems started on a failed update, it started to hang during use.
I made a backup and then tried to reset it, sadly i came no further then this boot logo after it crashed again.
I decided to enter recovery mode, when entering recovery each time i get a blue install screen of an update and each times it fails with an error.
Then i did a wipe cache and rebooted, same result, it stops at boot logo
Then i did a wipe/format factory reset (from recovery) and reboot, here also it hangs on samsung logo
Also it reports the following:
fail to open recovery cause no such file or directory
I even let the phone boot for 8 hours on the logo, it gets really hot but it does not go pass the samsung boot logo
When booting and the phone is connected by USB to my laptop i get messages that android rom is prepared and 1 later it is installed, but that is it, no booting etc.
I then entered download mode and used ODIN, downloaded the latest stock rom and try to flash it.
But here also i get each try a FAILED on the boot, even when i do no enter BL i get a FAILED, so only AP it fails also.
I tried now about 5 different stock rom versions and they all fail.
Have really no idea how to fix this, as mentioned the phone is fully stock, so stock bootloader, stock rom etc.
Anyone any idea how to get this phone up and running again?
B3rt said:
I have hear a S7 wich hangs on white samsung boot logo.
The device is stock, no root and no custom rom.
The problems started on a failed update, it started to hang during use.
I made a backup and then tried to reset it, sadly i came no further then this boot logo after it crashed again.
I decided to enter recovery mode, when entering recovery each time i get a blue install screen of an update and each times it fails with an error.
Then i did a wipe cache and rebooted, same result, it stops at boot logo
Then i did a wipe/format factory reset (from recovery) and reboot, here also it hangs on samsung logo
Also it reports the following:
fail to open recovery cause no such file or directory
I even let the phone boot for 8 hours on the logo, it gets really hot but it does not go pass the samsung boot logo
When booting and the phone is connected by USB to my laptop i get messages that android rom is prepared and 1 later it is installed, but that is it, no booting etc.
I then entered download mode and used ODIN, downloaded the latest stock rom and try to flash it.
But here also i get each try a FAILED on the boot, even when i do no enter BL i get a FAILED, so only AP it fails also.
I tried now about 5 different stock rom versions and they all fail.
Have really no idea how to fix this, as mentioned the phone is fully stock, so stock bootloader, stock rom etc.
Anyone any idea how to get this phone up and running again?
Click to expand...
Click to collapse
What country are you in?
What network were you using?
What firmware was on your phone nougat or Oreo?
What firmware are you trying to flash?
What version of Odin are you using?
cooltt said:
What country are you in?
What network were you using?
What firmware was on your phone nougat or Oreo?
What firmware are you trying to flash?
What version of Odin are you using?
Click to expand...
Click to collapse
Living in The Netherlands
The phone is free, not network limited but was last used on T-Mobile
I am not 100% sure, i believe Android 8
i tried: DNL-G930FXXU3ESA3-20190131134911 and EUR-G930FXXS4ESAE-20190218105256 and DNL-G930FXXU2DRC1-20180402094302 and BTU-G930FXXU1DPLT-20170117160813 and G930FXXU1DQAN_G930FFTM1DQAD_FTM
Tried Odin3_v3.12.3 and Odin3-v3.13.1
B3rt said:
Living in The Netherlands
The phone is free, not network limited but was last used on T-Mobile
I am not 100% sure, i believe Android 8
i tried: DNL-G930FXXU3ESA3-20190131134911 and EUR-G930FXXS4ESAE-20190218105256 and DNL-G930FXXU2DRC1-20180402094302 and BTU-G930FXXU1DPLT-20170117160813 and G930FXXU1DQAN_G930FFTM1DQAD_FTM
Tried Odin3_v3.12.3 and Odin3-v3.13.1
Click to expand...
Click to collapse
Your trying to flash old versions of the firmware, once the boot loader is updated you can't go back.
This is the latest version of T Mobile for the Netherlands (TNL), it's always best to try the firmware you were on first [url]https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/TNL/download/G930FXXU3ESA3/255865/[/URL]
If that doesn't work this is the latest version of Unbranded BTU [url]https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/BTU/download/G930FXXS4ESAE/257466/[/URL]
Also use Odin 13. Put all files in correct slots and use CSC not HOME_CSC
As far as i could see these are all android 8 and 1 android 7 firmwares, so they are not that old.
Believe the latest one is from January this year, i know the last time the phone was updated was last October, after that all updates failed to install OTA
The link you gave me is exactly the same version i used only without the branding, so i already used the latest one.
I tried to be sure the download from the link you given but with those download speeds (15kb) it is almost impossible to download these firmware's, i am not gonna take a subscription to for 1 time fast downloading and also i do not want to risk that i paid for a fast download it fails again....
So if someone has a download link which i can use and try an other firmware please feel free to share it.
BTW i used the last Odin3-v3.13.1 version, i cannot find a newer one.
B3rt said:
As far as i could see these are all android 8 and 1 android 7 firmwares, so they are not that old.
Believe the latest one is from January this year, i know the last time the phone was updated was last October, after that all updates failed to install OTA
The link you gave me is exactly the same version i used only without the branding, so i already used the latest one.
I tried to be sure the download from the link you given but with those download speeds (15kb) it is almost impossible to download these firmware's, i am not gonna take a subscription to for 1 time fast downloading and also i do not want to risk that i paid for a fast download it fails again....
So if someone has a download link which i can use and try an other firmware please feel free to share it.
BTW i used the last Odin3-v3.13.1 version, i cannot find a newer one.
Click to expand...
Click to collapse
Ok well you can listen to me or not.
None of the firmwares you are using are for your device, PHN is Netherlands and the BTU you are using BTU-G930FXXU1DPLT is on a U1 boot loader, BTU is now on S4 which is 3 versions above U1.
The reason you only download from Sammobile or updato.com is because the firmware is correct, reliable and not full of virus/spyware. You can also download direct from Samsung severs with SamFirm Tool.
Hello! I have had my One plus 7 pro international running for months now, rooted, following this guide https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368. I had the OTA update notification for quite some time now, but I ignored it because I was lazy. A few weeks ago my phone must have auto updated however, as I started noticing banner ads again that adaway usually blocked, and I have had a few other minor issues like GPS taking longer to connect or find where I am, wifi disconnects, and google not understanding what it usually does. Phone still works just fine, just minor issues I didn't really experience before.
I would like to completely reset the phone to clean it up, and re root and setup TWRP again, but im not sure how to safely do that since my phone was updated improperly (automatically). I have magisk still installed, but the modules dont seem to be working properly. Rebooting to recovery will reboot me to one plus recovery instead of twrp. When I restart is still says my boot loader is unlocked, and some apps (like chase mobile app) still say my phone is rooted. Oxygen updater says im up to date on OxygenOS 10.0.3.gm21aa.
What would be the best option for me to clean everything up, get my root modules working again, and have the phone fully up to date and stable? Any information would be greatly appreciated.
follow the same steps you followed first time. Boot to TWRP flash magisk, No need to factory reset. Flash twrp again if you want and reboot to system