Related
Hi All,
Im on the Official ICS ROM INDIA...4.0.3 DDLP4
Yesterday, when i checked kies, there was an update waiting (No Update on OTA). The downloading of firmware was taking ages to download(3.2mbps connection) and after about 70 percent the downloading stopped and Kies said "Connection stopped"....
Any body who has downloaded the F/W can you please post the change log (If you find any).. I mainly wanna know, if the laggness of the lock screen and slowness to open contact's and capturing pics has been rectified.
Ramith123
Ah glad that i have company.sad at the same time!! Even i have the same problem after the 7mb OTA update. The andriod process closes often and hangs the phone.The phone was literally unusable. Hence i tried to install custom gingerbread rom on it. Now its almost completely bricked.How irresponsible is samsung to roll these things out without testing it thoroughly.
***PLEASE DON'T INSTALL THE 7MB ICS OTA UPDATE***
hopefully we can save some.
I also tried to update through OTA but it was failed and message popped up that do update through Kies. Now I got update through Kies and my firmware changed from DDLP4 to DDLPA. However I lost Root.
I also received the update notification. Downloaded the 7.8 mb update within a minute and asked for reboot. Everything worked fine and nothing special noticed. It just changed the build no. from IML74K.DDLPA to IML74K.DDLP8
dushy4 said:
I also received the update notification. Downloaded the 7.8 mb update within a minute and asked for reboot. Everything worked fine and nothing special noticed. It just changed the build no. from IML74K.DDLPA to IML74K.DDLP8
Click to expand...
Click to collapse
you mean LP8 to LPA? check your kernel version date. if it shows 12 June then fine, else your kernel has not been updated.
Hey guys basically its stability update. my phone feels much smoother now. i updated OTA via wifi, i also faced update not installed issue and i found out the problem, basically we all root our device that means we change SU binaries so when updating phone OTA it checks for those binaries and if these binaries are not official OTA update get aborted. i solved this problem like this,
1) I have downloaded STOCK LP8 firmware from samobile.com when it released
2) As my phone is rooted my SU binaries are changed so OTA update is aborted.
3) So FLASHED Stock rom LP8 from PC ODIN which kept my all DATA, APPS intact i just lost my root and some mods like 15toggles status bar and so..
4)then i started updating my phone using S/W update in settings, its 7.85MB file.
5)In few minutes my phone is updated to LPA
6)Now i again rooted my phone and my all data apps are intact and mob is much improved in stability.
Hope this will help you guys.
anjath said:
you mean LP8 to LPA? check your kernel version date. if it shows 12 June then fine, else your kernel has not been updated.
Click to expand...
Click to collapse
It still shows 12 may,,, But i read in some other thread that kernel was not updated in this update.
dushy4 said:
It still shows 12 may,,, But i read in some other thread that kernel was not updated in this update.
Click to expand...
Click to collapse
kernel is definitely updated in LPA. just flash LPA ROM file using Odin.
I also agree with what mullarameez has pointed out. rooting might be the reason for kernel being skipped. because if u flash LPA with odin you will lose root and hence get the new kernel.
Is there a way to update Kernel without flashing the whole 650 mb rom?
with all the issues in ICS, i think it would be safest if you would flash using the whole LPA ROM. I know its a pain to download but worth it in the end.
OMG! just a 7Mb update took 2hrs to download.. Hmmmm...
My main prob was with Lock screen, camera and contacts.. Noting has been resolved on this new Update!!!
what is the issue? is it lag?
This is confusing..
I have everything stock on my phone..All updates done OTA since i bought the phone..Not rooted..
Still the kernel says 12 May after the 7mb update..Why?? Although the deep sleep issue (sore point for me) seems to have been resolved after this update...
PS: The build info after *#1234# says 12 June, if that matters..
yes, almost all the users who updated OTA have the same issue. you may flash the new LPA using PC Odin from doc's post (anyways you're not rooted so no problem)
Hi all, yesterday i got an ota notification for 5.1 on my N7 2012 mobile version, but coz i rooted before, the update was not successful. I tried to make a search in the internet for the download but strangely, there is no image uploaded for nakasig over there. Now i already did a full clean install on 5.0.2, and tried to push Check for update many times, but no ota ever happened again. How can i get it back? Anyone knows it, pls let me know. Many thanks!
Also in exactly the same boat. Fresh install of 5.0.2 on N7 2012, rooted. OTA update to 5.1 fails every time. Any advice?
The OTA will fail if you use a custom recovery (twrp or cwm). If you fastboot flash the stock recovery image, the OTA should work. The factory image is available for the wifi version, so you could update to 5.1 using it with fastboot. I don't know if the mobile factory image version has been released, but if not, it should be soon.
Hello everyone.
I`ve got rooted Nexus 6 with Franco kernel. From time to time it shows system security updates, which I install`s. But I notices on my android security patch level stops on January 2016 and still want to install February updates. Everytime N6 tries to install February updates. Does anybody know whats going on? Maybe it`s because I locked with security password on my twrp? After rebooting twrp show`s and I really dont know are updates installed well. I quess not. Can someone help?
And another question, does this android security updates will remove my root?
Shantarien said:
And another question, does this android security updates will remove my root?
Click to expand...
Click to collapse
Security updates will not work; unless the device is completely stock.
You should look at installing the OTA from this page - instructions are provided. If you want to retain the kernel,TWRP & and root you'll have to re-flash them when you're finished.
https://developers.google.com/android/nexus/ota
If you're unencrypted (I'm not - I prefer the security to an extra 10 minutes of battery life) do some reading first - I'm not sure how the OTA works with an unencrypted device. Maybe other members can advise both of us on this point.
Thx for answer`s.
Correct me if I wrong, but I`ve got stock rom, but with Franco kernel, and root, but it`s still stock, right? Does this could be a reason? All my data are encrypted, so maybe this could be a reason ( however after every update reboot I decrypt`s my data), I`ll switch off encrypting my N6 and try again update it.
----------EDIT------------
Guess, NLBeev was right. I can`t make an OTA update when my N6 is rooted, only manually method. I really afraid of this manually updates, because of losing something from my phone, or even brick it.
fear is something that xda can not help you with. itll happen through out life, in many situations. the only thing that you can do is deal with it and move on.
I manually update mine every update and have yet to have an issue.
I f you're encrypted (good!) then my earlier concern is irrelevant. Sideload the newest OTA at the link I gave you. I've done it now several times with two Nexus 5s and a Nexus 6. It's quick and simple and doesn't touch your data.
But I still always take a TWRP backup first and copy it to my laptop. Can't be too careful...
Once again thanks for help! I`ll try install them manually, as fast as I make backup by twrp.
Ach, I forgot, last question, which update should I download? I`ve got January system security updates, so should I download every single one by one? Or just last one (July 6.0.1 (MOB30O))?
Regards!
By "manually' do you mean extracting the separate components (system, radio, boot...)? I strongly recommend the OTA sideload method. Fast and simple, with no data loss.
You need only do it once. Download the MOB30O OTA and sideload it. Then if you want you can flash TWRP and root.
Greetings, I have a Project Fi Android One X4. Two days ago I went back to Project Fi Oreo stock after being rooted in order to receive the OTA. I received the January, February, and March security updates. But once I attempt to get the April one with 8.1, the system says I am up to date. I attempted to sideload the April OTA but got the message many get about not being able to mount. I know that these updates are not rolled out all at once, but I see many here in the forum already got it. Is there any way I can force the OTA? Thanks in advance for the help!
I'm pretty much in the same boat. I had to manually flash the full 8.0 firmware after being stuck on Dec security update. Received Jan, Feb and March updates OTA without a problem. Got notification that 8.1 April was available. Phone would download the OTA but fail halfway through the installation. Did this about a dozen times. Now phone says up to date but still on March 8.0.
Probably have to wait for the full firmware file to be released and manually flash again. Sucks. Never could get ADB sideload or update from SD card to work either.
jfalls63 said:
I'm pretty much in the same boat. I had to manually flash the full 8.0 firmware after being stuck on Dec security update. Received Jan, Feb and March updates OTA without a problem. Got notification that 8.1 April was available. Phone would download the OTA but fail halfway through the installation. Did this about a dozen times. Now phone says up to date but still on March 8.0.
Probably have to wait for the full firmware file to be released and manually flash again. Sucks. Never could get ADB sideload or update from SD card to work either.
Click to expand...
Click to collapse
Same issue for me. The ADB sideload/SD card problem doesn't make sense.
Same here. OTA update fails during step 3. Side loading doesn't work. I reflashed 8.0 and took all three security updates again just fine. Now I'm not even offered the OTA for 8.1.
I have a theory that it was pulled due to errors.
ptn107 said:
Same here. OTA update fails during step 3. Side loading doesn't work. I reflashed 8.0 and took all three security updates again just fine. Now I'm not even offered the OTA for 8.1.
I have a theory that it was pulled due to errors.
Click to expand...
Click to collapse
You think the 8.1 update was pulled due to errors? I was offered the update on my stock (locked and unrooted) Project Fi X4 a week ago, and my wife's got it on Friday (3 days ago). The update process was quick and went through without issues. The phones themselves seem to be operating normally.
rczrider said:
You think the 8.1 update was pulled due to errors? I was offered the update on my stock (locked and unrooted) Project Fi X4 a week ago, and my wife's got it on Friday (3 days ago). The update process was quick and went through without issues. The phones themselves seem to be operating normally.
Click to expand...
Click to collapse
Have you tried MTP or ADB (with lockscreen enabled), cause this would be the first confirmed case I've seen of it working properly on 8.1 update.
Thanks for all the responses! I see that I am not the only one with this issue. I think that like jfalls63 said, of we don't get the update in the coming days we will have to wait for the full firmware release. It is not convenient since I want to root and wanted to do it in 8.1, but there is not much we can do about it if we cannot find an alternative.
QWZR II said:
Have you tried MTP or ADB (with lockscreen enabled), cause this would be the first confirmed case I've seen of it working properly on 8.1 update.
Click to expand...
Click to collapse
You're right; I haven't had any reason to do either since the update and it wasn't until after I posted that I saw another thread mentioning this issue. Sure enough, same is true for me.
Still, the update was pushed to one of our phones only a couple of days ago, so if they pulled it, it's only been within the last 72 hours or so.
I'm experiencing a similar thing (https://forum.xda-developers.com/moto-x4/help/oreo-8-1-update-stuck-loop-t3788293), so this seems to be a prevalent problem.
When I have time, I'll go through the Moto forums and see if anyone has any helpful information.
I'm on Fi and I received the 8.1 update just fine. I haven't unlocked my bootloader yet to root it, but otherwise I'm on the gravy train. Once they release a full sized firmware I plan to reflash to get my space back, and then root.
The only solution i've found to get the OTA to work (verified by others as well as my self)
Reboot after each fail and try again - if you watch the screen the % complete will increase each time before fail, eventually ending in a successful upgrade! (At which time your phone is now more secure than ever - USB file transfer won't work with a lock screen pin/pattern/fingerprint.
Hello, i had Dec 5 OTA + Magisk rooted device.
i tried to update but it said failed. so i uninstalled magisk and restored to stock boot.img but still saying update failed.
someone said to relock bootloader. i tried to relock bootloader and my data got erased.
even after that i tried to update OTA and im still getting failed update.
i dont know what to do now. can anyone please help me.
i have the same problem
help us please
after doing a bit of searching i fixed it.
i simply flashed my device with Stock Rom 10.0.0.2 using Mi Flash Tool. (there are plenty of youtube tutorials).
after that my device installed the OTA updaet without any error.
after that i rooted my device with Magisk. [patched_boot is already been posted on this forum]
so far, haven't come across any problem. Just not satisfied with the volume update. i had a magisk module for low volume fix which worked better.
What's really needed is full images from Xiaomi, so we can start flashing them manually without worrying about OTAs
See how well the DAISY thread is being maintained https://forum.xda-developers.com/mi-a2-lite/how-to/ota-v9-6-4-0-odlmiff-t3823913
.
Another repost with the same issue.
Follow this and this
I have flashed the V10.0.13.0.PDLMIXM (and locked back oem) but I still have the google update problem... from June to September 2019 :/... any idea?