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)
(Please don't ask me to search the forum--that isn't working right now, it just gives an error.)
Several months ago, I bought a Nexus 6 phone, used from eBay. I have been using it with an AT&T SIM card for several months. However, it is stuck on build MOB30I and patch level "May 1, 2016". I thought that AT&T was simply months behind on updates, but today I learned the real problem: AT&T uses the MMB update tree, whereas my phone is (for some reason) on the MOB update tree. Apparently:
- My phone will not accept AT&T's MMB updates because the phone is on a different update tree
- My phone will not accept MOB updates (from Project Fi or Sprint or whomever) because an AT&T SIM card has been installed.
I tried removing the AT&T SIM card and checking for an update, but got nothing.
How do I switch to an update tree that will actually give me updates? I'd rather not install adb and sideload. In fact, rather than do that, I would instead enroll in the Android Beta program, install Android 7.0 beta, and let Google itself update me to Android 7.0 final when the time comes.
lgmayka said:
(Please don't ask me to search the forum--that isn't working right now, it just gives an error.)
Several months ago, I bought a Nexus 6 phone, used from eBay. I have been using it with an AT&T SIM card for several months. However, it is stuck on build MOB30I and patch level "May 1, 2016". I thought that AT&T was simply months behind on updates, but today I learned the real problem: AT&T uses the MMB update tree, whereas my phone is (for some reason) on the MOB update tree. Apparently:
- My phone will not accept AT&T's MMB updates because the phone is on a different update tree
- My phone will not accept MOB updates (from Project Fi or Sprint or whomever) because an AT&T SIM card has been installed.
I tried removing the AT&T SIM card and checking for an update, but got nothing.
How do I switch to an update tree that will actually give me updates? I'd rather not install adb and sideload. In fact, rather than do that, I would instead enroll in the Android Beta program, install Android 7.0 beta, and let Google itself update me to Android 7.0 final when the time comes.
Click to expand...
Click to collapse
Any reason not to use a Google Factory image? It looks like MMB29V is the most recent.
According to the instructions, installing a "Google Factory Image" would be a lot of risky work, and would erase all my data and apps. I was hoping for something simpler and safer. As I mentioned, joining the Android Beta program actually seems to be the easiest solution, if the current beta (NPD30G) is stable enough.
Frankly, I am surprised that Google/Motorola/AT&T (or any cell phone designer/manufacturer/carrier) allows a working cell phone to get into this state where the phone refuses to accept security updates.
For the Nexūs 6, the beta is quite stable (I didn't update my daily driver until I was sure it was stable on my other devices). You should be fine and back on track with NPD90G.
That's half the fun of owning a Nexus, not waiting for updates. Dl the factory image, unzip it and the zip file inside and flash the system. IMG only and you'll lose nothing but root. If, of course, you are rooted.
http://forum.xda-developers.com/showthread.php?p=59561445/ You may give it a try..... prerooted lite stock rom.
lgmayka said:
According to the instructions, installing a "Google Factory Image" would be a lot of risky work, and would erase all my data and apps. I was hoping for something simpler and safer.
Click to expand...
Click to collapse
As already suggested, just install the system image. The simplest way to do that is via fastboot. Nothing gets erased unless you flash the userdata.img. Using Google's script to flash everything would overwrite the userdata partition.
The version you are on (MMB) is released to provide updates without updating the radio. The MOB release is the same as the equivalent MMB plus the package includes the updated radio. This is a requirement of the carriers who want to approve the radio before it's released.
You will be unable to take any *incremental* OTA if there is any differential between what's on your system partition and what the OTA is expecting. You can not hop over incremental OTA updates. They must be sequentially applied. Therefore, the safest way to get to a known state is with a factory image.
If fastbooting a factory image is unacceptably risky, then maybe an eBay phone wasn't a great choice.
Or, as you say, you go straight to N. If the beta program is still available now that N is released.
stevemw said:
For the Nexūs 6, the beta is quite stable (I didn't update my daily driver until I was sure it was stable on my other devices). You should be fine and back on track with NPD90G.
Click to expand...
Click to collapse
I decided to do this. NPD90G is running well enough for me, and before long Google will release Android 7.0 Final.
Straight to the content, new mirrors appreciated. I will update this thread as soon as a new update comes out.
Links to Odin are from sammobile, and the ADB drivers are on Github. All links are clean and untouched.
Odin 3.11.1
ADB for Windows
===========================
Untouched side loadable update zips downloaded from xdmd.sl.attcompute.com (sideload using ADB):
7.0 branch:
2017 Mar security level Android 7.0 (G920AUCU5EQB8 to G920AUCU6EQC9)
2017 Mar security level Android 7.0 (G920AUCU5DQB3 to G920AUCU6EQC9)
2017 Feb security level Android 7.0 (G920AUCU5EQA8 to G920AUCU5EQB8)
2017 Feb security level Android 7.0 (G920AUCU5DQB3 to G920AUCU5EQB8)
2017 Jan security level Android 7.0 (G920AUCS5DPK5 to G920AUCU5EQA8) | Credit goes to Mohit0144
6.0 branch:
2017 Feb security level Android 6.0.1 (G920AUCS5DPK5 to G920AUCU5DQB3)
2017 Feb secruity level Android 6.0.1 (G920AUCS5DPK3 to G920AUCU5DQB3)
2017 Jan security level Android 6.0.1 (G920AUCS5DPK3 to G920AUCS5DPK5)
2016 Dec security level Android 6.0.1 (G920AUCS5DPK1 to G920AUCS5DPK3)
2016 Nov security level Android 6.0.1 (G920AUCS5DPJ1 to G920AUCS5DPK1)
===========================
Official complete Odin images (flash using Odin):
2016 Oct security level Android 6.0.1 (G920AUCS5DPJ1)
Current update path to most current build:
G920AUCS5DPJ1 (odin flash) -> G920AUCS5DPK1 (sideload) -> G920AUCS5DPK3 (sideload) -> G920AUCS5DPK5 (sideload) -> pre-release G920AUCU5EQA8 (sideload) -> pre-release G920AUCU5EQB8 -> pre-release G920AUCU6EQC9
If you are on a version more recent than DPJ1, you can start from a later sideload update.
Disclaimer: You are responsible for what you do to your phone
How to flash using Odin (will wipe phone):
1. Extract complete firmware
2. Extract Odin software
3. Shutdown phone
4. Press BL, AP, CP, and CSC buttons in-order in Odin and load files, Odin may freeze during this, just wait it out. Don't touch other options
5. Press Volume down, home, and power together to go into download mode
6. Plug in phone to laptop, and press start to flash
How to sideload using ADB (will wipe phone):
1. Install ADB, reboot
2. Using cmd, cd into the folder of the sideload update zip
3. Shutdown phone, press Volume up, home, and power together to go into download mode
4. Select "apply update from adb", use power button to confirm
5. Using the command "adb devices", verify that the phone is detected after plugging in, if it is detected, proceed
6. Type in command "adb sideload SIDELOADZIPNAME"
7. Wait, it takes a bit for the update to work, and the phone may appear frozen during this process.
If confused, see this thread: http://forum.xda-developers.com/att...ating-to-android-6-0-1-g920aucu3cpd6-t3371884
did exactly what u said with the odin and i keep getting a fail...
Billfromnj05 said:
did exactly what u said with the odin and i keep getting a fail...
Click to expand...
Click to collapse
Well, the file is the exact same as that from this thread. And it is working for those people, so not sure why this is happening to you without more details.
Thank you for these updates.
would this fix the reboot issue? clearing cache doesnt help with previous update (oct)
drek_67045 said:
would this fix the reboot issue? clearing cache doesnt help with previous update
(oct)
Click to expand...
Click to collapse
I have absolutely no idea about why your phone is crashing.
Installing an update may fix it, just by virtue of clearing the /data partition and resetting it to stock in the process. But personally I doubt it (unless google fixed a denial of service bug that you were somehow triggering?).
Not really a diagnosis thread, so do you mind creating a new post with USB debugging turned on and logcat output so the community can help?
See here: http://android.wonderhowto.com/how-...ture-logcat-for-detailed-bug-reports-0167774/
drek_67045 said:
would this fix the reboot issue? clearing cache doesnt help with previous update (oct)
Click to expand...
Click to collapse
Not sure as to specifics of your reboot issue, but I had an S6 that started giving me multiple random reboots per day. Luckily I was inside warranty by a couple weeks - it was a hardware issue. Ended up with a new main board, plus a new display since the tech broke the original somehow changing the board.
That's funny. I never got Dec update for my AT&T S6 variant over OTA. I guessing, it's time to sideload it again.
supersmilers said:
That's funny. I never got Dec update for my AT&T S6 variant over OTA. I guessing, it's time to sideload it again.
Click to expand...
Click to collapse
This has not been officially released yet. But it has been sitting on AT&T servers for quite a bit (along with DPK2). The kernel has a build date of Dec 14. My guess is that AT&T is waiting after the holidays to officially release this. It's a fairly small update coming in at 17MB.
Edit: I should note that I am running DPK3 without issue.
sand_bit said:
This has not been officially released yet. But it has been sitting on AT&T servers for quite a bit (along with DPK2). The kernel has a build date of Dec 14. My guess is that AT&T is waiting after the holidays to officially release this. It's a fairly small update coming in at 17MB.
Edit: I should note that I am running DPK3 without issue.
Click to expand...
Click to collapse
Man can you tell me, how do you flash in adb sideload the latest firmwares?, my s6 send me an error
E: Error in /sideload/package.zip
(status 7)
sand_bit said:
This has not been officially released yet. But it has been sitting on AT&T servers for quite a bit (along with DPK2). The kernel has a build date of Dec 14. My guess is that AT&T is waiting after the holidays to officially release this. It's a fairly small update coming in at 17MB.
Edit: I should note that I am running DPK3 without issue.
Click to expand...
Click to collapse
December update has been pushed out OTA. Is PK3.
Sent from my SAMSUNG-SM-G920A using Tapatalk
GilbertoXDA17 said:
Man can you tell me, how do you flash in adb sideload the latest firmwares?, my s6 send me an error
E: Error in /sideload/package.zip
(status 7)
Click to expand...
Click to collapse
Not sure, but probably need to flash this with Odin
worked fine, note of caution.
my att gs6 was on oj9. flashed went through fine initially then an error came up "can't open the serial(com)port" and FAIL in red above the blue part.
however, the phone progress meter kept going and eventually the flash was successful.
My g920a is stuck at g920aucs5dpi1 and on ota it says my software is up to date. I don't know what's happening or is it because I am not using at&t sim? But it's already unlocked.
wiltaf said:
My g920a is stuck at g920aucs5dpi1 and on ota it says my software is up to date. I don't know what's happening or is it because I am not using at&t sim? But it's already unlocked.
Click to expand...
Click to collapse
I would bet that it's because you're not on an AT&T sim. I don't think they feel responsible to update the phone if it's not on their network. Not sure if you can throw someone's sim in there to update it or if you just ODIN flash it to update it.
Edit: You can also try to use Smart Switch to see if it'll pull the update, or try a Samsung Experience at a BestBuy to see if they can push the update.
Thanks. Now my phone is up to date.
This is the only way I can apply updates. For some reason I never get the OTA updates.
Thanks my phone updated to latest.
will my unlocked galaxy s6 become locked if i update using this?
Could someone tell me if the encryption menu items are available on your GS6, and what build you are on?
I encrypted my phone about 2 builds back, and after the December update, upon reboot it no longer asks for my PIN/PW and encryption is no where to be seen in the settings, or at least I (and search) can't find it. I don't want to factory reset to see if it reappears...yet.
If AT$T removed encryption from the device in the next update, I'm going to be real pissed.
Also, I think (at the moment) my battery life is worse on the latest build, but I have been using my phone a little more lately. But last night I went from 100% at 7:05pm to 5% at 11:30pm. 4.5 hours is not way to quick for a battery to die. Wakelock Detector (no root) didn't give much info, and the system menu for battery gave 3 of the top 4 to Android OS, Google Play services, Android System.
TIA
Is this for phones already with root access?
Hey guys,
I'm on a stock Samsung Galaxy S6, SM-G920A, Android Version 6.0.1, Security Patch Level December 1, 2016, Build Number: MMB29K.G920AUCS5DPK3. I have an AT&T Go-Phone account (pre-paid). Do I have to root my phone before following this procedure? I have never tried to root this phone before. I have been researching the topic for a long time and just wanted to make sure I understand everything thoroughly before I pull the trigger. Don't want to trip KNOX or brick my phone. Any help would be much appreciated. Thanks fellas.
Matt
---------- Post added at 11:42 AM ---------- Previous post was at 11:31 AM ----------
Zero4 said:
Could someone tell me if the encryption menu items are available on your GS6, and what build you are on?
I encrypted my phone about 2 builds back, and after the December update, upon reboot it no longer asks for my PIN/PW and encryption is no where to be seen in the settings, or at least I (and search) can't find it. I don't want to factory reset to see if it reappears...yet.
If AT$T removed encryption from the device in the next update, I'm going to be real pissed.
Also, I think (at the moment) my battery life is worse on the latest build, but I have been using my phone a little more lately. But last night I went from 100% at 7:05pm to 5% at 11:30pm. 4.5 hours is not way to quick for a battery to die. Wakelock Detector (no root) didn't give much info, and the system menu for battery gave 3 of the top 4 to Android OS, Google Play services, Android System.
TIA
Click to expand...
Click to collapse
I'm on AT&T Galaxy S6, SM-G920A, Android Version 6.0.1, Build #: MMB29K.G920AUCS5DPK3. My phone is stock, no root. I have the encryption settings and am currently using them. Everything seems to be working fine.
---------- Post added at 06:22 PM ---------- Previous post was at 05:42 PM ----------
mjr4281 said:
Hey guys,
I'm on a stock Samsung Galaxy S6, SM-G920A, Android Version 6.0.1, Security Patch Level December 1, 2016, Build Number: MMB29K.G920AUCS5DPK3. I have an AT&T Go-Phone account (pre-paid). Do I have to root my phone before following this procedure? I have never tried to root this phone before. I have been researching the topic for a long time and just wanted to make sure I understand everything thoroughly before I pull the trigger. Don't want to trip KNOX or brick my phone. Any help would be much appreciated. Thanks fellas.
Matt
---------- Post added at 11:42 AM ---------- Previous post was at 11:31 AM ----------
I'm on AT&T Galaxy S6, SM-G920A, Android Version 6.0.1, Build #: MMB29K.G920AUCS5DPK3. My phone is stock, no root. I have the encryption settings and am currently using them. Everything seems to be working fine.
Click to expand...
Click to collapse
They did change it up though. Whatever you choose as your screen lock i.e., pattern, pin, password, is what will be used for unencryption at start-up. The one thing that doesn't make sense to me is that they now give you an option to use one of these methods or none at all during start-up. I don't see the point in using encryption if you can't password protect it, but I haven't fully researched all the options yet.
After flashing default android 6.0.1 on my s6 active my broadband version is unknown and I have no imei...not sure what to do.
EndSliceofBread said:
After flashing default android 6.0.1 on my s6 active my broadband version is unknown and I have no imei...not sure what to do.
Click to expand...
Click to collapse
Hi u , u can pm for me via zalo : +84974405300 . I can help u .
No
EndSliceofBread said:
After flashing default android 6.0.1 on my s6 active my broadband version is unknown and I have no imei...not sure what to do.
Click to expand...
Click to collapse
I had this exact problem with SM-G890A on 6.0.1. I flashed a stock firmware, and I had no mobile network, sim card wasn't detected, etc. The problem was that my device had the most recent update (from March). I am not an expert, but I believe this update makes it harder for devices to be susceptible to flashes (hence "extra security"). To fix this problem, after flashing a stock firmware, I put my phone in recovery mode (volume up, power, and home) and downloaded ADP, and from there, I was able to download each update after my stock firmware until I reached the update that I was on before I ever flashed. I hope that makes some sense. There is a great post on here with the updates available for download and instructions on how to use ADP. I wish I still had the link, but try searching the updated version that you should be on. Whenever I finished the last update and my phone restarted, I restarted it again in recovery mode and cleared the partition cache. Restarted it again and VIOLA, I finally had service. Feel free to email me if you have any questions. Sorry, I am not great at explaining things. I hope you can resolve this. [email protected]
Fixed and Downgraded
I had this same issue. I was able to fix it by first upgrading back to 7.0 as mentioned above, and then flashing ONLY the BL and AP files of the 6.0.1 firmware using Odin. Worked for me.
U need flash to android 6.0.1 build Pk8.
EndSliceofBread said:
After flashing default android 6.0.1 on my s6 active my broadband version is unknown and I have no imei...not sure what to do.
Click to expand...
Click to collapse
Hey I had the same problem as you and I was panicking. I downgraded to 6.0.1 from 7.0 final version but the SIM/IMEI/Broadband/anything phone related was broken. What happened was the final build of 7.0 upgrades the security of the SIM/IMEI/Broadband and so if you flash any other firmware, it won't work with the newer security and it'll remain unknown. To fix this, you have to upgrade to 7.0 final build again. Just adb sideload all the way back to 7.0 final QD1 and your SIM/IMEI should activate again. I guess ATT/Samsung is preventing us from downgrading just like Apple
Flash the Nougat Odin package.
Hey guys,
suddenly there poped up a system update (B366 OTA) for my NEM-L51, which suprised me, because we haven't got any updates since Nov. 18 (B365),even for L21.
Now there seem to be B366 and B369 available( Jan. 2020), according to: https://pro-teammt.ru/online-firmware-database-ru/?firmware_model=nem-l51&firmware_page=0 and my OTA Updater.
I am quite suprised and wondering what they have to offer, but I can't find any real Patchnotes, the ones linked in the Updater : https://consumer.huawei.com/en/support/bulletin/2019/8/ refere to an "M3 Lite(CPN-L0J)".
So, a quick reminder, check your update, and maybe let me know what changed for you, especially concerning root and magisk.
This update improves system security with Android security patches.
Integrates Android security patches for improved system security. For more information on the security of Huawei EMUI system updates, please visit the official Huawei website: https://consumer.huawei.com/en/support/bulletin/2019/8/
Adds the AppGallery app, offering you more comprehensive app downloads and updates.
1. This update will not erase your personal data, but we recommend that you back up any important data before updating. 2. If you encounter any issues during the update, please call the Huawei customer service hotline or visit a Huawei customer service center for assistance.
Click to expand...
Click to collapse
Hello,
Well, with this update I have lost the USB debugging.
The option comes out. And it can change: on - off, but it really doesn't work. It also does not obey the USB configuration types, so there is no way to recognize it neither the PC nor ADB, and therefore the impossibility of connecting to the PC or doing root.
Sorry my nem-l51c432b130 dont want to find any new update, im on android 6 emui 4.1.2,how can i install the android 7 emui 5 or newer version, i dont even know the last version, thanks for help!
... please write me in private !
Just installed B366, it has the august '19 patches and a few UI Tweaks, there is an App Drawer now, Twin Apps are missing.
My fastboot is working for TWRP (Elite TWRP 3.2.1) and Magisk root (Boot Image Patching Method, https://topjohnwu.github.io/Magisk/install.html )
Had to upgrade through eRecovery after fastbooting the original B365 Recovery.
EDIT: Factory Resets using the TWRP Factory Reset Function break Bluetooth and NFC, only the "fresh" installation has functioning Bluetooth/NFC. Again eRecovery is very useful to get a fresh ROM, now its directly to B366.
Used the HuRUpdater_0.4 (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279 ) to get to B369, nothing new there.
Edit2: The calendar widget is still broken.